This release bundle shows what the web frontend chapter put in place around November 2025.

• If you only care about where we are today, use the chapter state page.
• If you care about how we got here, you are in the right place.

Quick Lane if this is what you looking for:

Open chapter stateOpen steward roster

What this release was about

This tag collects the first small slice of chapter ops for the web frontend chapter:

• making it clear who owns what in ops
• watching two simple health checks
• handling cloud access blocks in the open

Pages in this release

These are the main docs that belong to this release.

• Casual vs Operation meeting defaults
  operatelive

  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.

• Cloud access blocks
  mitigatelive

  Simple template for handling cloud access blocks in the open instead of hacking around them.

• Frontend charter
  navigatelive

  What the frontend chapter is for, what it is not for, and when to bring something here instead of to your squad.

• Learn overview
  learnlive

  Two health checks only; no dashboard here.

• Mitigate overview
  mitigatelive

  Where we park the ugly stuff: blocks, exceptions, and how we decide what to do about them.

• Navigate overview
  navigatelive

  Quick routes for the platform; keep nav small and clear.

• Operate overview
  operatelive

  Small set of ops pages in play for this platform.

• Ops contract · platform baseline
  operatelive

  Guardrails and receipts for changing Northbook as a platform.

• Signals roster
  learnlive

  The two health checks we watch—roster freshness and whether people leave sessions knowing their next step.

• Steward roster
  operatelive

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

Decisions behind this release

No decisions have been attached to this release yet.

As we add more decisions or pages to this tag, they should show up here.

For auditors and ops

This page is built from frontmatter fields like:

• release_tag: site-v2025.11
• decision_id, guardrail_id, leading_metric, lagging_metric

If something looks wrong in this bundle, fix the frontmatter on the underlying pages and rebuild. This view should never be edited by hand once automation is in place.