ForgeSDLC
Navigate
Home
Discover ForgeSDLC (101)
Practice (201)
Master (301)

The ForgeSDLC Manifesto

We are entering an era where AI agents write code, generate tests, scaffold infrastructure, and draft documentation. The bottleneck has shifted from production to decision-making.

Traditional methodologies optimized for a world where humans were the only producers. ForgeSDLC optimizes for a world where humans are decision-makers and AI is a production partner.

What we value

Decision velocity over process compliance. Every ceremony, every artifact, every metric must earn its place by improving the speed or quality of decisions. If it doesn't — remove it.

Embedded knowledge over external documentation. The methodology lives in the repository, not in a wiki that nobody reads. Blueprints put the body of knowledge where the work happens.

Ceremony-driven checkpoints over continuous status tracking. Versona challenges happen at decision points — not on a calendar. When the work demands a quality gate, the gate appears. When it doesn't, there is no ceremony.

Lean identity over parallel tracking. A Spark is a task. A task is a Spark. One identity, one source of truth, one WBS hierarchy. No shadow tracking systems.

Automated journals over manual reporting. Decisions are logged. Progress is derived from commits, completions, and ceremony outcomes. Nobody writes a status report.

What this means in practice

  1. Your repo is your methodology. Blueprints live as a submodule. Policies, templates, and bodies of knowledge are version-controlled alongside code.

  2. Ceremonies have purpose. Every Versona challenge applies a specific discipline's knowledge to a specific decision. No "sync meetings."

  3. AI agents are first-class participants. They execute Sparks, they surface information for Versonas, they maintain the Charge view. The methodology accounts for their strengths and limitations.

  4. Process weight is minimized. The 17 Forge Principles act as a constitutional check — any process addition must justify its cost against the waste it prevents.

  5. Quality is built in, not inspected in. Discipline blueprints encode quality criteria directly. When a Versona is invoked, the relevant quality gates are present automatically.