Delivery index

This is the entry point for the Brainforge delivery system.

The delivery model is organized around:

  1. Standards — the floor
  2. Checkpoints — how the floor is enforced
  3. Roles — how Head of Delivery, CSO, SL, and ICs participate
  4. Lifecycle / systems of record — how work moves and how truth is maintained
  5. Tools and SOPs — how the team executes consistently
  6. Analogies — teaching layer, not policy

Start here by question

What is the standard?

What are the checkpoints?

How does work move from SOW to execution?

What does my role own?

How does Head of Delivery govern the system?

What tools and SOPs support the work?

What analogies explain the model?


Folder map

FolderPurpose
00-head-of-delivery/Governance, standards-setting, escalation, rollout, KPI layer
01-roles-and-responsibilities/Shared role model and role-specific accountability
02-meetings-and-cadence/Checkpoints and forcing functions
03-project-lifecycle/SOW plan execution re-gate lifecycle
04-standards-and-sops/Shared floor, communication doctrine, PM doctrine, detailed standards
05-tools-and-skills/Practical tools, skills, and workflows
operating-tool/Operating.app: delivery-facing agent workflow and case notes
06-reference/Analogies, archives, and supporting reference material

Suggested reading order

For new team members or for anyone resetting on the operating model:

  1. 04-standards-and-sops/consolidated-delivery-standards.md
  2. 02-meetings-and-cadence/meeting-catalog.md
  3. 03-project-lifecycle/README.md
  4. 01-roles-and-responsibilities/README.md
  5. Your role-specific folder

By role


Platform note

The HTML operating model page is a presentation layer, not the canonical source of truth:


Analogy note

Analogies are used throughout the delivery system as teaching tools. Policy remains literal. When in doubt, the markdown docs in knowledge/delivery/ are the source of truth.


Last updated: 2026-04-06