<aside>
✅
Lifecycle: Active / 1.0 / A0 · Scope: global-working-memory · Mode: READ_ONLY / DETECT_REPORT · write_authorization: NONE
</aside>
Activation boundary
- Activation authorizes read-only reconciliation and fail-visible reporting.
- It does not authorize automatic repair, projection rewrite, registry self-mutation, authority cutover, or repository mutation.
- GitHub remains live repository execution truth when available.
- Notion remains authoritative migrated project memory until governed cutover.
- Drive remains runtime/control-plane and
drive_shadow according to declared authority.
Repository-unavailable continuity fallback
The existing pre-repository Notion + Drive AIOS path is retained as a continuity backup. It is not a second execution-truth authority.
- Trigger only when GitHub repository access or the GitHub connector needed for the current claim is unavailable.
- Repository-dependent freshness becomes
UNAVAILABLE or UNKNOWN, never synthetic FRESH.
- Repository writes, exact-HEAD claims, merge authorization, and repository-derived current-state promotion are blocked while the repository cannot be verified.
- Existing Notion/Drive workflows may continue only within their own declared authority and provenance boundaries.
- When GitHub access returns, re-fetch
main, run reconciliation, resolve any drift visibly, then exit degraded continuity mode.
Evidence
TEMPORAL_PROJECTION_EVENT_FIXTURE_01 — Promoted Prototype
DESIRED_STATE_DRIFT_GOVERNANCE_FIXTURE_01 — Promoted Prototype