Handbook
Forge — deep-dive package (blueprint)
Purpose: Prescriptive operating detail for teams running Forge alongside this blueprint: roles, foundation fit (tracking + ceremonies C1–C6 + archetypes), ceremonies with inputs/outputs/participants, process maps…
Executive summary + diagram: https://forgesdlc.com/methodology-overview.html
| Chapter | File | Contents |
|---|---|---|
| Foundation & fit | Forge — connection to the SDLC foundation | SDLC A–F mapping, tracking spine, ceremony intents C1–C6, role archetypes |
| Roles | Forge — roles (prescriptive) | Owner/Implementer, hat-switching protocol, Versonas as virtual personas (not org roles), scaling tiers |
| Ceremonies (prescriptive) | Forge — ceremonies & events (prescriptive) | Each ceremony: inputs, outputs, agenda, participants, timebox |
| Meeting model | Forge — meeting model (operational) | Delivery modes (human-only / hybrid / Versona-assisted), meeting matrix, refinement vs planning, per-meeting fields, accountability, drift |
| Artifacts & decisions | Forge — artifact and decision model | Minimum artifact set, artifact matrix vs meetings/PDLC/SDLC, canonical names, Ember Log / ADR / directive boundaries, lightweight Markdown schemas |
| Process & flows | Forge — major processes & flow maps | State model, work unit hierarchy, iteration lifecycle, KS diagram templates |
| Naming reference | Forge & planning — naming reference | Forge terms, meanings, meetings vs ceremonies vs Versona sessions, seven-phase benchmark vs P1–P6, source file paths |
| Concept map | ForgeSDLC — concept map and term-collision register | Canonical concept matrix (lifecycles, owners, artifacts, meetings) and term-collision register |
| Product → delivery IPE | Product creation → delivery — industry, Forge, and PMI-style map | PDLC/SDLC phases: industry + Forge + Inputs–Process–Outputs + example Sparks |
| Bridge | Forge ↔ SDLC ↔ PDLC bridge | How Forge connects to PDLC P1–P6 and SDLC A–F |
| Versonas | Versonas — discipline-focused virtual personas | Discipline virtual personas: contract, templates, bridge-awareness — layout: generic at versona/ root; other templates under versona/catalog/ |
| Discipline exploration spike | Discipline exploration spike — lifecycle and anchors | Time-boxed learning spikes: anchors, open/close, roadmap/WBS handoffs (vs Forge Spark) |
| Daily operations | Daily operations | Charge, Ember Log, day journal: templates and scripts |
| Product planning | Product planning | PoC/MVP/Phased planning, Product Spark hierarchy, Ore pipeline |
| Product Manager agent | Product Manager — Forge orchestrating agent | Product strategy orchestrator, product bootstrap flow, first Charge template |
| Setup & adoption | Setup & adoption | Questionnaire, scaffold script, configuration template |
| Scripts | scripts/README.md |
Shell scripts for Charge, Ember Log, journal, and status |
Key references:
- Spark = Task: Spark occupies the Task level in any existing WBS hierarchy. No parallel namespace — enrich, don't duplicate. See process-and-flows.md § Spark = Task and foundation-connection.md § tracking spine.
- Lean tenets: Forge must never add more ceremony than it removes waste. See forge.md § Lean tenets and foundation-connection.md § anti-patterns.
Related blueprint: Roles & archetypes · Ceremony foundation · Methodology bridge · Forge ceremonies fork · Agentic SDLC · Agentic coding standards · Disciplines hub