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, read Cogitave's flow-based ways of working and its ADR-0025 choice of flow over Scrum as one org's answer, 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 your 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 a development-process standard exists to kill.
- Read Cogitave's flow-based ways of working as one org's answer: 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 that 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.
Prerequisites
- Completion of "Work the request lifecycle", the earlier module in this path - this module assumes you already know the seven lifecycle stages and the Definition of Done.
- Basic familiarity with Git, trunk-based development, and continuous integration.
Units
- 01Introduction4 min
- 02The Day 1 operating model6 min
- 03Flow-based ways of working7 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Reliability and SRE Reason about a service's reliability targets the way an SRE discipline does - set an SLO from the user's journey, compute the error budget it buys, and operate the service against that budget with burn-rate alerts, sustainable on-call, a toil cap, and the freeze that stops shipping when the budget runs out.
- Respond to incidents Walk the incident-response flow end to end - detection, severity declaration, single-commander roles, containment through a runbook, communication, recovery, and the blameless postmortem - and see how business continuity and disaster recovery extend the same discipline to a region loss or a destructive event.
- Run agentic operations Explain what agentic operations means - agents running an estate unattended inside rails - state the draft-vs-act rule that decides when an agent acts unattended versus when it stops for a human, and study Cogitave's own fleet of scheduled and operations agents as the worked example of the fleet you would build.