Forge principles
Forge is anchored by four core principles for AI-native delivery (shape before speed, flow over ceremony, AI-first, human-gated, make gains compound). Full narrative: Four core principles on the blog.
The sections below spell out execution principles (how work moves) and lean tenets (how to keep the methodology lightweight). Together they implement those four ideas in practice. Any new ceremony, artifact, or metric must earn its place by improving decision quality or waste removal — not by habit or compliance theater.
The list below matches the canonical breakdown in the Forge methodology blueprint. For vocabulary (Sparks, Versonas, Charge, …), start with What is ForgeSDLC?.
Core execution principles
- Refine before you commit. Ore must become Ingot before execution.
- Keep work small enough to challenge. Sparks make learning fast and waste visible.
- AI strengthens thinking; humans own judgment. Versonas challenge, not decide.
- Decisions deserve memory. The Ember Log captures why.
- Release on evidence, not optimism. The Assay Gate makes release discipline explicit.
- Paused is not failed. Banked is a strategic choice with preserved context.
- Standard process stays standard. Forge adds precision inside ceremonies, not alternatives.
- Scale by trust, not by process weight. Same vocabulary solo through enterprise.
Lean tenets
Forge must never add more ceremony than it removes waste:
- One hierarchy, one set of IDs. Sparks are existing Tasks with Forge semantics layered on — do not duplicate the WBS.
- Collapse levels when they already fit. If refinement already produces ready Stories, those are Ingots. No extra ceremony.
- Log decisions, not narration. Two lines explaining why beat two pages of session recap.
- Automate the journal. If logging feels like overhead, fix the tooling.
- Versonas at decision points, not everywhere. Before costly commitments, not as bureaucracy.
- Charge is a view, not a board. Label or filter, not a separate tracking surface.
- Scale formality to risk. Solo: self-assessment checklist. Enterprise: gate meeting.
- Defer tooling until volume demands it. Start with journal + git; add dashboards later.
- No shadow rituals. Use standard Forge ceremony names (refinement, planning, daily sync, review, retro, release readiness) and add Forge mechanics inside—do not invent parallel standing meetings for the same intent (duplicate syncs, duplicate retros, or “process” meetings outside the methodology).
Where to go next
- Four core principles (blog) — trade-offs for AI-native delivery.
- Forge SDLC overview — methodology narrative and scaling model in Blueprints.
- Forge foundation (201) — how Forge fits SDLC phases and roles.
- The ForgeSDLC Manifesto — values and practice.