a69eb7e587
Implements all 5 phases of Foundary Studio backend:
Phase 1: Chat Persistence (8 API endpoints)
- Conversations and messages with proper cascading deletes
- PostgreSQL schema with auto-update triggers
- Full CRUD operations with structured logging
Phase 2: Blueprint Entity (5 API endpoints)
- JSONB spec storage with GIN indexes
- Flexible structured data for project specifications
- Version-controlled blueprint management
Phase 3: Architect Service (3 API endpoints)
- Conversational AI orchestration with Claude
- Multi-turn dialogue with context building
- Blueprint spec extraction from conversations
Phase 4: Work Queue Integration
- Verified existing endpoint compatibility
Phase 5: Structured Questions (6 API endpoints)
- Four question types: text, choice, multichoice, yesno
- Answer validation with proper constraints
- Conversation-linked Q&A flow
Architecture:
- Textbook hexagonal architecture (domain → port → adapter → service → handler)
- Zero external dependencies in domain layer
- Consistent error handling with proper wrapping
- Auth scopes on all routes (projects:read, projects:execute)
- Structured logging with operation context and duration tracking
- NULL-safe DTO converters throughout
Database:
- 3 new migrations (019, 020, 021)
- UUIDs for all primary keys
- Proper foreign key constraints with ON DELETE CASCADE
- Optimized indexes including partial index for unanswered questions
- Auto-update triggers for timestamps
OpenAPI Documentation:
- Complete API documentation under 'Foundary' tag
- 22 new endpoints documented with examples
- Request/response schemas for all operations
Logging Improvements:
- Added operation field to all service logs
- Added duration_ms tracking for performance monitoring
- Log response_length instead of full response content
- Consistent use of logging field constants
- Execute-then-log pattern for delete operations
Files: 32 changed, 2800+ lines added
- 7 domain models
- 3 database migrations
- 3 port interfaces
- 3 postgres adapters
- 4 services (conversation, blueprint, question, architect)
- 4 handlers with DTOs
- OpenAPI documentation
- Integration in main.go
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
32 lines
964 B
Go
32 lines
964 B
Go
package domain
|
|
|
|
import "time"
|
|
|
|
// QuestionID is a strongly-typed identifier for questions.
|
|
type QuestionID string
|
|
|
|
// QuestionType represents different types of questions.
|
|
type QuestionType string
|
|
|
|
const (
|
|
QuestionTypeText QuestionType = "text"
|
|
QuestionTypeChoice QuestionType = "choice" // Single choice
|
|
QuestionTypeMultiChoice QuestionType = "multichoice" // Multiple choices
|
|
QuestionTypeYesNo QuestionType = "yesno"
|
|
)
|
|
|
|
// Question represents a structured question in the architect flow.
|
|
type Question struct {
|
|
ID QuestionID
|
|
ConversationID ConversationID
|
|
ProjectID string
|
|
Type QuestionType
|
|
Text string
|
|
Choices []string // For choice/multichoice types
|
|
Answer *string // User's text answer
|
|
AnswerChoices []string // For multichoice type
|
|
Metadata map[string]string // Additional context
|
|
CreatedAt time.Time
|
|
AnsweredAt *time.Time
|
|
}
|