FORGE Stage-Gated Execution
FORGE (Factory-Optimized Release Gate Execution) is SO1’s stage-gated execution model that ensures quality, traceability, and consistency across all agent outputs.Overview
Every agent operates within a specific FORGE stage, with explicit entry gates (prerequisites) and exit gates (deliverables).Figure 1 — FORGE Stage-Gated Pipeline. Each stage has explicit entry and exit gates enforced by the FORGE Gatekeeper. The primary agent assigned to each stage is shown below the pipeline. No stage transition occurs until all exit-gate criteria are satisfied.
Trace ID Requirement Rationale Test Case SO1-FORGE-001Every stage transition shall be validated by the FORGE Gatekeeper before proceeding Prevents incomplete deliverables from propagating to downstream stages TC-SO1-FORGE-001SO1-FORGE-002Entry and exit gates shall be declared in each agent’s YAML frontmatter Enables automated compliance checking and VTM population TC-SO1-FORGE-002SO1-FORGE-003Each gate crossing shall produce a decision record in ADR format Maintains a traceable audit trail of all stage transitions TC-SO1-FORGE-003
Stage Details
- Stage 0: Planning
- Stage 1: Design
- Stage 2: Implementation
- Stage 3: Documentation
- Stage 4: Validation
- Stage 5: Deployment
Purpose
Requirement analysis, task decomposition, and agent selection.Primary Agent
Factory OrchestratorEntry Gate
- User request received
- Context sufficient for parsing
Exit Gate
- Requirements parsed and documented
- Tasks broken down into atomic units
- Agents assigned to each task
- Execution order determined
Decision Record Example
Cross-Cutting Agents
Some agents operate across all stages:| Agent | Role | Triggers |
|---|---|---|
| FORGE Gatekeeper | Validates stage transitions | Every gate crossing |
| Incident Commander | Orchestrates incident response | P1/P2 incidents |
| Triage Responder | Initial assessment | Alert triggered |
Gate Configuration
Each agent defines gates in its YAML frontmatter:Gate Validation
The FORGE Gatekeeper validates all gate crossings:- Pre-validation: Check entry gates are satisfied
- Execution: Agent performs work
- Post-validation: Verify exit gates are met
- VTM Update: Record in Verification & Traceability Matrix
Validation Command
Decision Records
All significant decisions are logged in ADR format:Example Decision Trail
VTM: Verification & Traceability Matrix
The VTM is the source of truth for agent validation:| Agent | Stage | Entry Gates | Exit Gates | Status |
|---|---|---|---|---|
| Factory Orchestrator | 0 | 2 | 4 | ✅ Pass |
| Workflow Architect | 2 | 4 | 5 | ✅ Pass |
| Mintlify Author | 5 | 4 | 4 | ✅ Pass |
Stage Coverage
| Stage | Name | Agent Count | Coverage |
|---|---|---|---|
| 0 | Planning | 1 | ✅ Complete |
| 1 | Design | 1 | ✅ Complete |
| 2 | Implementation | 4 | ✅ Complete |
| 3 | Documentation | 6 | ✅ Complete |
| 4 | Validation | 2 | ✅ Complete |
| 5 | Deployment | 4 | ✅ Complete |
| Cross-cutting | All | 3 | ✅ Complete |
Related Documentation
Veritas Integration
How agents consume and produce prompts
Agent Catalog
Browse all 20 agents