Atticus
Pick the shortest Atticus exit first.
- Primary job: Atticus is still the governance gate for trust, scope, ownership, and public-exposure decisions before those changes become shipped facts.
- Route split: This district still sorts readers first, then exits toward Decisions, Policies, Integration, or Architecture depending on what is actually unclear.
- Best use: Open this page when you need the current governance contract and the shortest safe next click before implementation or coordination keeps moving.
Reader orientation
Start with the decision framework
Use Decision Framework when the work paused at Atticus and you need the fast answer to what kind of ruling happened and what it changes about the next move.
Best when the immediate question is whether the work stays local, needs a governance ruling, or should be rerouted before delivery continues.
Stop once you can name the ruling shape, the ownership implication, and whether the work should keep moving locally.
Reader orientation
Use this page when you need the shortest path to the Atticus ruling shape, the durable policy boundary, or the handoff pattern before implementation continues.
What changed recently
Compact updates that help a reader place this agent in the current network story.
- May 23·District landing now uses the shared Atlas first-stop grammar so readers can choose rulings, policy boundaries, handoff shape, or trust-model context before scanning the whole page.
- May 21·Decision, policy, and integration detail routes were refreshed onto the shared Atlas grammar with clearer governance boundaries and no runbook leakage.
- Apr 9·District first framed the practical reader question: when do I need Atticus in the loop?
- Mar 31·District content clarified the Atticus vs Almanac split so governance and doc stewardship no longer blur together.
Governance boundary, knowledge health, and where ownership stops
It slows down scope, trust, authority, and exposure changes before they quietly become implementation facts.
The Almanac lens keeps shared explanations current so the network does not keep making decisions from stale documentation.
Atticus can turn meetings into shared memory and structured notes, but the teams that act on those notes still own the downstream delivery decisions.
It can clarify the path, challenge scope, and preserve the audit trail, but it should not quietly become the doer for other agents or charters.
Keep Atticus's five charters separate
Network health and alignment review. Compass reads recurring friction, stewardship gaps, and places where the operating model may be drifting.
Cadence cron, weekly governance/alignment review plus manual review
Documentation stewardship. Almanac checks explanations against current evidence before shared knowledge is refreshed or republished.
Cadence cron, twice daily shared-doc refresh
Meeting-intelligence and memory pipeline. Ledger records context and turns raw meeting capture into structured notes the rest of the network can use.
Cadence webhook from Fellow with 15-minute poll fallback
Founder-knowledge lens. Anthology mines real founder work — reviews, refactors, meetings, and decisions — into a source-backed, queryable index for the Founders OS.
Per-teammate growth-coaching lens. Coach prepares check-ins, reflects patterns, and answers ask-anything over Slack DM, grounded in each person's own check-in history.
Cadence reactive — Slack DM routed by per-user bindings (pilot: Antony)