Basic Workflow

The Forgexa follows a structured pipeline for converting requirements into deployed code.

Lifecycle Overview

Requirement → Analysis → Plan → Execution → Gate Review → Merge

1. Requirement Submission

Users submit requirements in natural language. The system supports:

• Free-text descriptions
• Acceptance criteria
• Priority levels (critical, high, medium, low)
• Attachments and references

2. AI Analysis

When you click Analyze, the AI:

1. Parses the requirement into structured fields
2. Identifies functional/non-functional requirements
3. Generates acceptance criteria
4. Estimates complexity and suggests work items
5. Creates a structured specification

3. Plan Generation

After requirement approval, a Plan is generated containing:

• Work Items — discrete tasks on the Kanban board
• Execution Nodes — pipeline stages (design, coding, testing, review)
• Dependencies — task ordering and prerequisites

4. Execution

Upon plan approval:

1. An Execution Graph is created
2. The Orchestrator polls for ready nodes (dependencies satisfied)
3. Nodes are dispatched to available Runtime Daemons
4. Daemons execute AI agents in isolated workspaces
5. Results are reported back to the server

5. Test-Fix Loop

For coding nodes, the system automatically:

1. Runs the project's test suite
2. If tests fail → re-invokes the AI agent with failure context
3. Loops up to 5 iterations until tests pass
4. Records all iterations in the execution log

6. Quality Gate

After execution, a Gate Score is calculated across 7 dimensions:

Dimension	Weight	Source
Test Pass Rate	25%	Automated test results
Test Coverage	15%	Code coverage tools
Static Check	15%	Lint + type check
Security	20%	Security scan results
Diff Risk	10%	High-risk file change detection
AI Review	5%	AI code review score
Requirement Coverage	10%	Supplementary requirements implemented

Based on the weighted score:

• ≥ 85: Auto-merge (configurable)
• 60–84: Requires human review
• < 60: Blocked — needs rework

7. Merge

Approved changes are merged into the project's default branch via auto-created pull requests.

Work Item States

todo → in_progress → in_review → done
                ↘ cancelled

Execution Node States

pending → in_progress → completed
                      → failed → (retry) → pending
                      → cancelled