Phase Track O / O0 — Freeze Normie custody funnel (Thinking freeze)

Status: Reviewed → pass (O0-r3). O0 Thinking is spec-only and now frozen; no product UI, no account glue, and no live consumer ok init land in this phase. The Track O / O1 Auto build ({step}b) is cleared to implement product contracts only as scoped below. Do not re-derive this contract during the Auto build.

phase: TRACK-O-O0
outputs:
- id: track-o-o0-normie-custody-funnel
  path: docs/archive/phases/PHASE-TRACK-O-O0-NORMIE-CUSTODY-FUNNEL.md
  frozen: true
frozen_inputs:
- id: kit-spec-regimes
  path: docs/OVERSEER-KIT-SPEC.md#4
- id: kit-spec-cli
  path: docs/OVERSEER-KIT-SPEC.md#5
- id: freeze-ceremony
  path: docs/OVERSEER-KIT-SPEC.md#6
- id: kit-boundary
  path: AGENTS.md
- id: k6-pilot-matrix
  path: docs/archive/phases/PHASE-K6-PILOT-INSTALL-MATRIX.md
- id: k7-dogfood-guardrail
  path: docs/archive/phases/PHASE-K7-MUSE-GIT-MIRROR-DOGFOOD.md
- id: k6-scooling-runbook
  path: docs/consumers/scooling/OVERSEER-SETUP.md
- id: consumer-adapter-pattern
  path: docs/CONSUMER-ADAPTER-PATTERN.md
- id: track-q-desktop-runbook
  path: docs/TRACK-Q-DESKTOP-OPERATOR-RUNBOOK.md
- id: test-tiers
  path: policy/test-tiers.yaml
- id: decision-tiers
  path: policy/tiers.yaml
- id: roadmap-track-o-rows
  path: docs/ROADMAP.md
review_stamp:
  reviewed_at: '2026-07-13T19:44:54Z'
  verdict: pass
  reviewer_mode: agent
  reviewer_model: thinking-high
  reviewer_provider: local
  kit_version: 0.1.0
  artifact_digest: sha256:642076c9a7dc341cc69f5d214342c4d65233c0c6c61a300d7825b1d3e9337961

Downstream edge: the Track O / O1 Normie custody product-contracts Auto build treats this document as ground truth without re-deriving it (SPEC §6 mandatory reviewed freeze). Later product UX in Scooling or Knowtation may implement wizards against this contract, but those product repos are not cleared to invent kit regimes, CLI semantics, or MuseHub-only baseline features from this freeze. Track Q desktop remains an operator UI surface; it does not reopen this onboarding scope.

Review record (§6.2): every freeze-review finding MUST cite file+line per SPEC §6; uncited findings are invalid and are discarded. Fixes applied during the loop are Tier 1 (feature branch); merge to main is Tier 3 and is never part of this loop.

§O0.0 — Simple summary

People who are not developers still want ownership of what they produce with AI: notes, plans, decisions, and memory that follow them across chatbots. Overseer Kit already provides regimes, living docs, and the ok CLI. What they need next is a clear product path: create a personal space (Muse-first preferred, no Git required to start), optionally add GitHub backup later (kit upgrade ceremony deferred to O2), and optionally bind a Knowtation vault — without teaching bare git or bridge scripts.

Technical summary: freeze Track O as an onboarding contract that composes the existing three regimes (muse-only, git-only, muse+git-mirror) with consumer product UX. The kit remains rule-holder + CLI; products own signup wizards that call ok init, governance-sync, and (later) mirror under the hood. Baseline governance stays fully usable without Muse, without Scooling, and without Knowtation.

§O0.1 — Scope

In scope (freeze only — this phase writes no code):

• Track O identity vs K6 consumer pilots vs Track Q desktop (§O0.2).
• Normie path stages and allowed regime transitions (§O0.3), including deferred Stage 3 ceremony (§O0.3.3).
• Custody-identity definition (§O0.4).
• Boundary table: kit vs Scooling vs Knowtation vs MuseHub (§O0.5).
• Explicit non-requirements / rejection table (§O0.6).
• O1 Auto deliverable list — product contracts only (§O0.7).
• Seven-tier matrix O1 must satisfy (§O0.8).
• Hard stops + tier linkage (§O0.9).
• Close-out rules after freeze pass (§O0.10).

Out of scope (explicit non-goals — prevent creep):

• Any signup UI, account creation, OAuth, or marketplace plugin in overseer-kit.
• Live consumer ok init on Scooling, Knowtation, or any named production tree (operator-gated; unchanged from K6).
• New VCS regimes beyond the frozen three in SPEC §4.
• New core CLI subcommands in O0 or O1 (products wrap existing ok surfaces).
• Engine rewrite of adapters, footprint, honesty, or Track Q app server.
• Making Scooling, Knowtation, MuseHub, Cursor, or Track Q desktop mandatory to use the kit.
• MuseHub-only baseline features (K7 frozen guardrail).
• Tier-3 merge, staging push, or live capability flips — this freeze never authorizes them.
• Storing vault bytes, Knowtation credentials, or GitHub tokens inside the kit.

§O0.2 — Track identity (frozen)

Frozen one-liner: Track O is the custody onboarding contract for personal AI work; it is not a fourth VCS regime, not a vault, and not a Scooling dependency.

§O0.3 — Normie stages (frozen)

Stage 1 — Start
  Preferred: create personal space under muse-only (no Git required).
  Also fully supported: git-only (K7 baseline — no Muse required).
  Product may wrap: ok init (+ regime selection) for a new or empty tree.

Stage 2 — Work
  Living docs (ROADMAP + HANDOVER) + paste-ready prompts into any chatbot.
  Product may hide ok governance-sync / status behind UX; kit CLI remains authority.
  Cursor rules/skills are optional boosters, never required.

Stage 3 — Optional GitHub backup
  Allowed transition: muse-only → muse+git-mirror (existing adapters + SD-14 bridge).
  Kit automated upgrade ceremony: deferred (§O0.3.3); products must not ship one-click yet.
  Never required to start; never invent a push-to-main shortcut.

Stage 4 — Optional Knowtation bind
  Bind a Knowtation vault root to the same custody identity (§O0.4).
  Knowtation owns vault bytes + bind UX; kit does not become the vault.

§O0.3.1 — Allowed regime transitions (frozen)

Products must not invent a fourth regime string or a silent dual-write outside the adapter interface.

§O0.3.2 — Dev / operator path (informative, not replaced)

Terminal + cli/ok + K6/K7 runbooks remain the operator path. Normie stages use the same adapters and commands behind a simpler product shell. Track Q may later surface Stage 2 status for operators; it does not replace Stage 1–4 product ownership.

§O0.3.3 — Stage 3 kit upgrade ceremony (frozen — deferred)

§O0.3.1 declares that muse-only → muse+git-mirror is an allowed transition. It does not authorize O1 (or any product) to invent the kit mechanism.

§O0.4 — Custody identity (frozen)

Custody identity for Track O means the durable association of:

1. One repo working tree (personal space),
2. That tree's .overseer/config.yaml (regime + doc paths),
3. The VCS history selected by the regime (Muse and/or Git),
4. Optionally, a Knowtation vault root bound by the product to that same tree.

O1 must not invent a kit-side identity registry, SSO, or cross-product account table.

§O0.5 — Boundary table (frozen)

Frozen guardrail (K7): no core governance feature may be MuseHub-only. Every baseline capability (init / sync / status, drift, footprint, templates, policy, freeze review, governance-sync) remains fully functional on git-only.

Frozen product rule: a Scooling account is not required to use Overseer Kit. Scooling is an optional entry product, not a kit dependency.

§O0.6 — Rejection table (frozen)

§O0.7 — O1 Auto deliverables (product contracts only)

After this freeze is stamped pass, Track O / O1 may ship only the following kit-side artifacts:

1. Normative product contract document at the exact path docs/TRACK-O-NORMIE-CUSTODY-PRODUCT-CONTRACT.md that restates Stages 1–4, §O0.3.3 deferred Stage 3 ceremony, the boundary table, and the rejection table for product implementers — no redesign of §O0.3–§O0.6.
2. Consumer cross-links:
   • Update docs/consumers/scooling/OVERSEER-SETUP.md to point at Track O stages as the normie path (keeping live init operator-gated).
   • Create docs/consumers/knowtation/OVERSEER-SETUP.md as a kit-side stub (regime note + Track O Stage 4 pointer + hard stop: no live Knowtation ok init in O1). Full Knowtation pilot parity remains a later operator/K6-style phase.
3. Docs integrity harness under tests/ (required). An optional thin validator under tools/ may factor the same checks, but the harness alone is sufficient for O1.
4. Seven-tier tests for the harness (and validator if shipped) per §O0.8.
5. ROADMAP + HANDOVER sync marking O1 DONE only after /build-verification-review → pass.

O1 must not ship: signup UI, account APIs, OAuth, marketplace plugins, new CLI subcommands, regime adapter changes, Stage 3 automated upgrade ceremony, live consumer installs, or vault storage.

If a later phase needs product UI inside a consumer repo, that work lives in the consumer and consumes this contract — it is not O1 kit scope.

§O0.8 — Seven-tier test matrix (O1 Auto build must satisfy)

The O1 Auto build ships all seven tiers green locally before DONE (policy/test-tiers.yaml). Skipping a tier is forbidden. The docs integrity harness under tests/ is the mandatory surface; a tools/ validator is optional and, if present, must be covered by the same tiers.

§O0.9 — Hard stops + tier linkage (frozen)

This freeze does not gate merge, staging, or live flips by itself. Consuming this artifact for a Tier-3 action still requires separate operator authorization (SPEC §6.4).

§O0.10 — Definition of Done (Thinking) + close-out

O0 Thinking DoD:

• [x] This document reviewed → pass via /freeze-review-loop + ok review --freeze
• [x] frozen: true + non-empty review_stamp filled by the CLI
• [x] ROADMAP Track O / O0 → DONE (Thinking); Track O / O1 Auto row queued against this contract
• [x] Handover NEXT flips to O1 with valid Model: Auto + paste-ready fence (KH1 H7/H8)
• [x] No product UI code landed in the Thinking phase
• [x] No Tier-3 merge performed as part of freeze

Close-out sequence (execute only when O0 freeze marked DONE):

1. Freeze-review pass recorded in the Review record table; stamp written by ok review --freeze.
2. ROADMAP: Track O / O0 → DONE; add Track O / O1 (Auto, TODO) product-contracts build.
3. Exploration backlog row Track O / O-onboard: replace Sketch/Boundary with Promoted → Track O / O0 (freeze) + O1 (Auto product contracts); Stage 3 ceremony deferred to later Thinking (O2).
4. Handover NEXT → Track O / O1 Auto with paste-ready prompt.
5. Governance sync: docs/ROADMAP.md + docs/OVERSEER-HANDOVER.md updated together (SD-17).

Cross-references

• docs/OVERSEER-KIT-SPEC.md §4 regimes, §5 CLI, §6 freeze ceremony, §8 migration
• docs/archive/phases/PHASE-K6-PILOT-INSTALL-MATRIX.md — operator (dev) install path
• docs/archive/phases/PHASE-K7-MUSE-GIT-MIRROR-DOGFOOD.md — MuseHub-optional guardrail + bridge
• docs/MIGRATE-EXISTING-REPO.md — operator day-to-day
• docs/consumers/scooling/OVERSEER-SETUP.md — first consumer; points normies to Track O
• docs/CONSUMER-ADAPTER-PATTERN.md — kit vs consumer ownership
• docs/TRACK-Q-DESKTOP-OPERATOR-RUNBOOK.md — operator UI surfaces (not Stage 1 signup)
• docs/ROADMAP.md — Track O / O0 row + exploration backlog
• policy/test-tiers.yaml — seven-tier requirement
• policy/tiers.yaml — Tier 1/2/3 authority