โ† forge

PlatinumForge: the agentic council SDLC prototype

An AI-driven software development pipeline where 8 agents collaborate, challenge each other, and won't let anything ship until it's actually ready.

โŒฅ repo
What it is

PlatinumForge is a developer-facing agentic SDLC platform. You describe what you want to build. Eight AI agents with distinct roles โ€” designer, challenger, builder, enforcer, stress tester โ€” work through it together, gate every stage, and produce traceable, tested, buildable code.

This is not Forge Studio. Forge Studio is the end-user app builder. PlatinumForge is the developer pipeline prototype โ€” pure agentic SDLC from idea to shipped code.

Most AI coding tools work alone. You paste a prompt, you get some code back, you hope it's right. PlatinumForge works differently: a council of eight agents with different jobs, who disagree with each other, and who have to reach consensus before anything moves forward.

The idea is that good software development is already a collaborative process with different kinds of thinking โ€” the person who expands ideas, the person who pokes holes in them, the person who actually builds it, the person who refuses to let unsafe things through. PlatinumForge makes that explicit, and automates it.

Nothing ships until the council agrees it's ready.

The Design Council โ€” 8 agents

ฮจPsi โ€” General DesignerBalanced, helpful, opinionated. Keeps the overall design coherent.
โ˜€๏ธApollo โ€” The ExpanderWild ideas, lateral thinking, "what if?" Pushes the scope of what's possible.
๐Ÿ”ฅPrometheus โ€” The ChallengerProbes assumptions, finds gaps, asks the uncomfortable questions.
โš’๏ธHephaestus โ€” The BuilderData structures, patterns, architecture. Makes it actually buildable.
โš–๏ธThemis โ€” The EnforcerBlocks non-compliant changes. Rules are rules. Constraints are constraints.
๐Ÿ Hestia โ€” The ExplorerEnriches concepts, splits compound ideas into manageable pieces.
โšกZeus โ€” The ArbiterResolves disagreements, overrides vetoes when the council is stuck.
๐Ÿ”จThor โ€” The Stress TesterChaos engineering, performance, security. Breaks things before they ship.

After each pipeline stage, all 8 agents review the output. Each votes APPROVE, CONCERN, or VETO. Concerns are logged and addressed. Vetoes block progress until resolved. Zeus can override a veto, but only once everything else has been heard.

The 9-stage pipeline

๐ŸŒฑ Seed  โ†’  ๐Ÿ’ก Expansion  โ†’  โš–๏ธ ConstraintForge  โ†’  ๐ŸŽญ BehaviourForge  โ†’  ๐Ÿ—๏ธ ShapeForge  โ†’  ๐Ÿงช BuildForge  โ†’  โš’๏ธ GenerateForge  โ†’  โœ“ Validate  โ†’  ๐Ÿš€ Ship
๐ŸŒฑ SeedYou describe what you want to build. Rough intent is fine here.
๐Ÿ’ก ExpansionApollo and the council expand the idea into concrete concepts, candidate features, and open questions.
โš–๏ธ ConstraintForgeEvery constraint is identified and given a unique ID (C001, C002โ€ฆ). These trace through everything that follows.
๐ŸŽญ BehaviourForgeAcceptance criteria and expected behaviours are defined before any architecture is decided.
๐Ÿ—๏ธ ShapeForgeHephaestus shapes the data model, interfaces, and architecture. The council reviews and gates.
๐Ÿงช BuildForgeTests are written first. All tests. Before a single line of production code exists.
โš’๏ธ GenerateForgeThe LLM plans a file manifest, then generates interfaces, services, controllers, and models to pass the tests.
โœ“ ValidateGenerates the .csproj, runs dotnet build, launches the app, health-checks it. If it doesn't build and run, it goes back.
๐Ÿš€ ShipTraceable, constraint-linked, tested, built, and signed off by the council. Now it can ship.

What makes it different

  • Constraint traceability โ€” every constraint (C001, C002โ€ฆ) is referenced in acceptance criteria, architecture decisions, generated tests, and code comments. You can always trace why something exists.
  • Tests before code โ€” BuildForge writes all tests before GenerateForge writes a single line of implementation. The tests define what "done" means.
  • Council review gates โ€” the pipeline cannot move forward if an agent vetoes. This is not optional. It is the mechanism.
  • 12 quality sliders โ€” performance, security, readability, and 9 more. These shape every generation decision throughout the pipeline.
  • End-to-end in one file โ€” the entire platform is one Program.cs, ~6500 lines. No ASP.NET. Raw HttpListener. Roslyn in-memory compilation. SSE for real-time updates. Monaco editor for code review.
Nothing behaves, exists, or ships without traceable constraint lineage.

How it relates to Forge Studio

PlatinumForge and Forge Studio share the same origin โ€” the idea that AI should understand intent and turn it into something real. But they target different people doing different things.

PlatinumForge is for developers. You're building software. You want a structured, traceable, agent-driven pipeline that produces tested, buildable code. The output is code and a build.

Forge Studio is for end users who want a running business application, not a codebase. They describe what they want to do, the AI coaches them into a proper business definition, and Forge generates and runs the application from it. No developer required for the boilerplate.

PlatinumForge is the prototype that proved the agentic pipeline concept. Forge Studio is where that concept meets the end user.

View on GitHub โ†’ Forge Studio โ†’ The origin story โ†’