RapierCraftStudios / ForgeDock

What it does

• One lane per issue, many in parallel. forgedock orchestrate schedules a batch from the issues' Depends on #N lines, runs up to K lanes at once, and recovers the mechanical failures itself (CI red, merge conflicts, engine errors). It asks yo
• Durable. Each lane records its state on the issue and in a crash-safe run log. Kill it, restart it, or lose the session: it resumes from what GitHub says, and two lanes never own the same issue.
• Checked, not trusted. Each change is held to a contract frozen before implementation. It must pass a separate review (which blocks on unimplemented requirements and regressions) and CI. On paths you mark as risky, the full contract-conforma
• GitHub is the memory. Findings, decisions and trajectories are written as structured comments that later lanes read. Nothing lives only in a chat window.