# Compass ingestion — 2026-05-10

Source: `toby/strategy/compass.md` (created in watched folder this run).

## What changed on the dashboard
Updated `toby/00-state-of-the-project.md` to defer to the compass as the authoritative strategic anchor. Specifically:

1. **TL;DR** — added a sentence summarizing compass v0.1's three sharpenings (reliability promoted to anchor #1, cloud-sync demoted to table stakes, calm sharpened to calm-by-ambient-surfacing, persistence codified as a 10× axiom).
2. **New section "Strategic anchor (Compass)"** placed right after TL;DR. Lists vision, brand promise, the 4 axioms, 5 anchors (with the at-risk flag on anchor #1), anti-promises, and audience anchors. Each line cites `toby/strategy/compass.md`.
3. **Immediate next steps** — reliability triage item explicitly tagged "Anchor #1 protection" and now cites both v3 delta and compass. The "Chrome 133 vs. Toby" comparison page item now carries a framing constraint: do NOT lean on cloud-sync (compass anchor #2 says it's now table stakes).
4. **Roadmap** — reliability framed as upstream of everything per compass; CWS narrative-repair sprint flagged to check against compass anti-promises before publishing; positioning page leans on axioms 1/2/3 not cloud sync.
5. **Phase / Milestone progress** — added a line: "Product Compass v0.1 — SHIPPED to wiki 2026-05-10".
6. **Recent shipments** — top entry now the compass publication.
7. **Key decisions to date** — promoted the persistence-as-activation entry to cite compass axiom 3; added three new explicit decisions: calm axis sharpened, cloud-account relegated, reliability promoted.
8. **Open questions** — added: (a) free-tier collaboration limits vs. anchor #4 tension before gating experiment ships, (b) compass references a "bets.md" with unspecified path — confirm and link. Removed the "calm as a defensible axis" question — it is now resolved by compass axiom 2 and recorded as a decision instead.
9. **Doc index** — added compass and personas as peer documents.

## What I did NOT do
- Did not modify `toby/strategy/compass.md` (out of scope per soul + rules — that folder is owned by whoever wrote the compass; my sub-folder is the state-of-project view, not the strategy authoring surface).
- Did not delete anything from the dashboard. Stale items remain flagged in "Open questions" for operator review.
- Did not touch any codebase file.

## Open follow-ups for the human
- Confirm location of `bets.md` referenced from compass anchor #4 and axis discussion. Likely either `product/strategy/bets.md` or a new file pending creation.
- Decide free-tier collaboration limit policy before role-based-gating experiment ships; this is a direct compass anchor #4 tension.
- Optional: consider moving this dashboard from `toby/00-state-of-the-project.md` to `toby/state-of-project/dashboard.md` per agent rules — currently kept in place to avoid breaking existing links.