Scooling — consumer boundary (public stub)
Scooling is an optional product runtime that may consume Overseer Kit for
governance. It is an optional entry into the ecosystem and is never
required for kit custody, ok init, or baseline GitHub regimes.
What the kit owns vs what Scooling owns
| Layer | Kit | Scooling |
|---|---|---|
Regimes / ok CLI / footprint |
Owns | Consumes |
| Living docs content | Templates only | Consumer tree |
| Multi-agent product runtime | — | Consumer-owned (not vendored by the kit) |
Hard stop — live install is operator-gated
Live ok init / ok sync against a Scooling production tree is operator-gated
(Tier 3 against the consumer). This stub does not authorize merges, staging
pushes, or live capability flips.
Track O product contract: docs/TRACK-O-NORMIE-CUSTODY-PRODUCT-CONTRACT.md.
Stage 3 kit ceremony (optional GitHub deepen): ok upgrade-regime against freeze
PHASE-TRACK-O-O2-STAGE3-UPGRADE-CEREMONY (docs/archive/phases/PHASE-TRACK-O-O2-STAGE3-UPGRADE-CEREMONY.md).
Migrate / fixture path: docs/MIGRATE-EXISTING-REPO.md and
tests/fixtures/pilot/config-scooling.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.
Adversarial freeze
When honesty.adversarial_freeze is suggest or require, author freeze pass does not clear
Auto until a different-chat attack review records adversarial_freeze (or suggest skip).
See docs/ADVERSARIAL-FREEZE-REVIEW.md. The key is absent in consumer init templates (derived
default); kit dogfood sets suggest explicitly.