Knowtation — consumer boundary (public stub)

Knowtation is a sister product (personal knowledge / vault). It may optionally bind as Track O Stage 4. The kit does not store vault bytes.

Regime note

Any frozen regime from SPEC §4 may apply (muse-only, git-only, muse+git-mirror). Muse is never required for kit baseline.

Track O pointer

Normie custody stages (Start → Work → optional GitHub backup → optional Knowtation bind): docs/TRACK-O-NORMIE-CUSTODY-PRODUCT-CONTRACT.md.

Stage 3 ceremony: ok upgrade-regime / PHASE-TRACK-O-O2-STAGE3-UPGRADE-CEREMONY (docs/archive/phases/PHASE-TRACK-O-O2-STAGE3-UPGRADE-CEREMONY.md).

Hard stop — no live Knowtation ok init from this stub

Live install against a Knowtation production tree is operator-gated (Tier 3). This stub does not authorize:

• Live ok init / ok sync on a Knowtation checkout
• Vault credentials or absolute machine vault paths in kit docs
• Kit-hosted vault storage

What the kit owns vs what Knowtation owns

Migrate / fixture path: docs/MIGRATE-EXISTING-REPO.md and tests/fixtures/pilot/config-knowtation.yaml.

Print NEXT on closeout

After any update to the living handover and/or roadmap, print the paste-ready fence via ok next (or ok governance-sync --print-next) so the operator’s next chat paste matches disk — not an open tab. See docs/PRINT-NEXT.md.

Independent second reviewer

The kit records and gates a second-chat verdict before Auto DONE when ISR is enabled; it does not run another model. See docs/INDEPENDENT-SECOND-REVIEWER.md.