Operate from Day 1
Describe the Day 1 operating model - the pinned inner loop and the flow-based outer loop - state the parity contract that keeps the inner loop honest, name Cogitave's flow-based ways of working and why ADR-0025 chose it over Scrum, and explain why the human gate stays an exception inside the flow.
Units5
Duration24 min
Levelintermediate
By the end of this module, you'll be able to:
- Describe the Day 1 operating model: a pinned, reproducible inner loop (mise, just, trunk-based delivery, preview environments) composed with a flow-based outer loop, both specified from the estate's first day rather than added after launch.
- State the parity contract that keeps the inner loop honest - lefthook commands == CI commands == just targets - and explain why drift between them is the bug development-process exists to kill.
- Name Cogitave's flow-based ways of working: WIP-limited continuous flow (Kanban-style) as the base method plus Shape-Up-style betting for larger bets, with the request-lifecycle Request as the unit that flows, and say why ADR-0025 rejected Scrum for this team.
- Explain what a WIP limit protects in an agent-heavy flow, why the human gate stays an exception rather than a routine checkpoint, and how DORA and flow metrics measure the system honestly without becoming a target.