Unified OS — Monthly Reset

SSOT is not just real-time. It is Index → Review → Track hygiene so the canon stays true over time.

daily = execute weekly = score / flag drift monthly = OS reset quarterly = promote yearly = growth model

SSOT = 3 loops (not just sync)

Index — material lands in gospel / intel / os-pins / archives. Unindexed = didn't happen for the system.
Review — weekly flag drift; monthly back-index modifies the pin. Index without review = junk drawer.
Track — owner + date + status. Untracked truth decays into zombies.

The unify (simple)

Canon — FisherOS Master is source of truth (not each agent's memory).
Monthly pin — fisher-os-YYYY-MM.json — freeze for 30 days.
Fan-out — regenerate Claude handoff + Manus brief + gospel/pages from the pin.
Mesh/Clay — monthly iMazing dump into archives (encryption = indexing hygiene, not API fantasy).

Reset ritual (45 min · 1st of month)

INDEX — gospel/intel + iMazing Mesh/Clay → archives/mesh-clay-YYYY-MM/
REVIEW — diff pin vs reality; wins/kills/tools/priorities
TRACK — close or escalate zombies
PIN — ship fisher-os-YYYY-MM
FAN-OUT — Claude · Manus · pages
LOCK — no canon edits until next reset

Why this beats “unify the AIs”

Shared memory APIs mutate daily → you forget the plan.
Monthly pin = one cognitive load; same day as Mesh backup.
Pattern already works: Agexa attribution Claude↔Jarvis handoff.
Growth model stays yearly; OS monthly until canonized → then quarterly.

Links

Canon: https://jarviscooks.com/p/fisher-os-master Cadence: https://jarviscooks.com/p/fisher-os Gospel: imessage-bridge/data/gospel/unified-os-monthly-reset.json