Use this when you are changing how the chapter runs—state, stewards, signals, or blockers. Everything else waits.

• Casual vs Operation meeting defaults

  How we tell a casual chat from an ops session, plus the default 1:1 pattern we fall back to when nothing else is agreed.

• Ops contract · platform baseline

  Guardrails and receipts for changing Northbook as a platform.

• Steward roster

  Who is currently on point for scope, signals and exceptions, plus how fast they aim to respond.

What is live in Operate

• Chapter state — the current snapshot and what to read before ops time.
  → Open chapter state
• Steward roster — owners for scope, signals, and exceptions plus backups.
  → Open steward roster
• Signals roster — the two health checks (roster freshness, clear next step).
  → Open signals roster
• Cloud-access stub — log and handle serious access blocks.
  → Open cloud-access stub

If you are changing the system itself

The ops contract explains guardrails, exceptions, and receipts for this platform slice.
Read it when you are working on Northbook, not just using it.
→ Open ops contract

If something breaks in Operate, open a PR or note and tag the steward roster contact; log blockers as exceptions.