For now, Northbook is a small pilot focused on the frontend chapter.
It is here to help you answer two questions:
- Where does my question or change belong?
- Who should I talk to or what should I read next?
There is no full playbook behind this page yet on purpose.
We only expose the pieces that are already in use.
Expected Takeaway: you leave knowing whether you should look at the chapter state or at who owns what next.
Quick links for the web frontend pilot
- 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.
- Cloud access blocks
Simple template for handling cloud access blocks in the open instead of hacking around them.
- Frontend charter
What the frontend chapter is for, what it is not for, and when to bring something here instead of to your squad.
- Learn overview
Two health checks only; no dashboard here.
- Mitigate overview
Where we park the ugly stuff: blocks, exceptions, and how we decide what to do about them.
- Navigate overview
Quick routes for the platform; keep nav small and clear.
- Operate overview
Small set of ops pages in play for this platform.
- Ops contract · platform baseline
Guardrails and receipts for changing Northbook as a platform.
If you want to see where the chapter stands
Open the chapter state page:
- see what the current pilot covers
- see which ops pages are actively in play
- use it as a quick briefing before a chapter ops session
If you want to know who owns what
Open the steward roster:
- see who looks after scope, signals, and exceptions
- see who is backup and how fast they’re expected to respond
If this still feels unclear
If you reached this page and still feel lost, treat that as useful feedback.
Raise it in the next chapter ops session or with whoever shared Northbook with you so we can adjust this entrance.