Skip to content
🧭
Atticus detail route

Decision Framework

Use this page when your real question is why work slows down at the governance gate, what Atticus is actually deciding, and what each ruling changes about the next move.
Validated · Oct 6, 2026The 2026-09-29 charter-family census pass revalidated this framing against the registry mirror: the section below now teaches all five Atticus charters the district's Explore census already renders (Anthology and Coach join the original lens trio), and the proof still matches the governance-first district contract and the phone-first Policies / Handoff / Trust exits.
Start here on phone

Keep the ruling shape here, then jump sideways as soon as the missing question changes.

PoliciesJump here when the missing answer is the durable Atticus boundary.HandoffJump here when Atticus already belongs in the loop and the missing answer is the handoff shape.TrustJump here when the question is broader than Atticus and needs the wider trust model.
Ruling shape

Start with the outcome categories

Most readers arrived because the work paused here. Answer that question first: did the change stay local, require a ruling, or need a different owner before more delivery work continues?

Use the decision shape, not a memorized phrase

Think of Atticus as a classifier for scope and trust boundaries. This is the quick answer layer before the rest of the governance model.
Question
The change stays inside an existing lane and does not move risk.
Start with
Expect a local proceed path.
Why
Atticus exists to slow down scope, policy, and trust-boundary changes, not to re-approve every routine improvement.
Examples: focused bug fixes, copy cleanup, test coverage, and narrow refactors inside the owning agent or charter.
Question
The change adds scope, moves authority, or crosses a policy boundary.
Start with
Atticus classifies it before delivery continues.
Why
The governance gate keeps network behavior aligned when the next step would otherwise rely on assumptions about risk or permission.
Examples: new public surfaces, infrastructure changes, approval-sensitive publishing, or cross-agent scope shifts.
Question
The proposal is unclear, mis-scoped, or asks the wrong owner to decide.
Start with
Expect redirect or denial with guidance.
Why
Atticus should narrow the path or reroute ownership before a team burns time building the wrong thing.
The useful output is the clarified next move, not just a generic “no.”
Current Saffron framing

Keep Atticus's five charters separate

Atticus is easier to navigate when readers do not collapse its five charters — Compass, Almanac, Ledger, Anthology, and Coach — into one generic governance blob.
Compass

Compass is the network health reviewer lens. It surfaces alignment gaps, recurring coordination issues, and places where the system may be drifting from its intended operating shape.

Atticus · cron
Use this mental model when the concern is network-level health or repeated friction, not one specific delivery decision.
Almanac

Almanac is the documentation stewardship lens. It keeps shared knowledge current so Atlas, QMD, and other readers do not act on stale explanations.

Knowledge lens
Observation-before-action matters here: Almanac verifies claims against live evidence before it publishes or freshens shared knowledge.
Ledger

Ledger is the meeting-intelligence lens. It turns raw meeting capture into structured notes and shared memory without making Atticus the owner of every downstream decision.

Pipeline lens
Think publishing and synthesis, not project ownership. Ledger records and routes context; it does not replace the teams that act on it.
Anthology

Anthology is the founder-knowledge lens. It mines real founder work — reviews, refactors, meetings, and decisions — into a source-backed, queryable index for the Founders OS.

Founder-knowledge lens
Use this mental model when the question is how Jake and Derek actually work; the index stays source-backed so advice carries founder context without a founder in the room.
Coach

Coach is the per-teammate growth-coaching lens. It prepares check-ins, reflects patterns, and answers ask-anything over Slack DM, grounded in each person's own check-in history.

Atticus · Slack DM
Use this mental model when the concern is one person's growth arc — Coach reacts to the person in the DM rather than owning a delivery lane.
What Atticus governs

Governance boundary, not delivery ownership

Atticus can narrow the path, require a ruling, or preserve the audit trail. It is not the doer for other agents' work, and it should not turn Atlas into a runbook for live commands.

Continue through the Atticus cluster

Governance Policies

Open the durable rule set behind the Atticus rulings described on this page.

Open Governance Policies
Integration Guide

See when Atticus enters the loop and how Atlas frames that handoff without turning into a command manual.

Open Integration Guide
Coordination Patterns

Zoom back out to the wider handoff model once the Atticus-specific gate is clear.

Open Coordination Patterns