Overview
Dream Foundry implements a competitive agent architecture where multiple AI approaches compete to fulfill a founder’s vision. The system orchestrates the entire lifecycle from idea intake to production deployment.System Flow
The architecture follows a linear pipeline with five distinct phases:Core Data Models
IdeaBrief
Captures the founder’s initial vision and constraints:Candidate
Represents each competing implementation approach:Objective
Defines measurable goals with weighted importance:Bias weights create a 3x/2x/1x multiplier system. High (H) objectives get 3x weight, Medium (M) get 2x, and Low (L) get 1x in final scoring.
ForgeResult
Contains complete execution and scoring data:Integration Points
Daytona
The Forge Phase
- Create isolated workspace per candidate
- Execute build commands in sandbox
- Run test suites
- Capture execution metrics
- Cleanup workspaces after scoring
Sentry
The Forge Phase
- Initialize per-candidate project
- Capture errors during build/test
- Track performance metrics
- Export issues for reliability scoring
CodeRabbit
Polishing Phase
- Submit top 3 candidates for review
- Parse improvement suggestions
- Apply automated fixes
- Verify improvements with re-testing
ElevenLabs
Showcase Phase
- Generate voice narration for:
- Engineering walkthrough
- Marketing pitch
- Executive summary
- Output: MP3 files for various audiences
Agent Communication
Agents communicate via message passing (in-memory for hackathon, scalable to Redis/Kafka):Configuration
All system tunables are centralized inconfig.yaml:
Execution Modes
The Forge supports two execution modes:Local Mode
Runs candidates as subprocesses on the host machine. Fast for development, but no isolation.
Data Flow Example
Here’s how data flows through the system for a typical run:Idea Capture
Founder submits: “I want a bot that posts AI events to Discord weekly”System creates IdeaBrief with objectives and constraints
Candidate Generation
Factory generates 5 candidates:
- Alpha (Speed Demon)
- Beta (Perfectionist)
- Gamma (Insider)
- Delta (Crasher)
- Epsilon (Hallucinator)
Forge Execution
Each candidate runs in Daytona sandbox:
- Sentry captures errors (Delta crashes)
- Performance metrics collected
- Artifacts generated (Discord posts)
Scoring
Candidates scored on:
- Success (20%): Did it run without errors?
- Quality (60%): Does output meet requirements?
- Speed (20%): How fast did it execute?
The architecture prioritizes transparency and measurability. Every decision point has clear, objective criteria that can be audited and improved.
Next Steps
Five Phases
Deep dive into each phase of the Dream Foundry pipeline
Scoring System
Learn how candidates are evaluated and ranked