Discipline v0.2 (BETA) — boot snippet

01This project follows the AI-Native Code Discipline.

02The language-neutral corpus lives in this package:

• 03the guiding layer (spec/00-MANIFESTO.xml, spec/01-PATTERN-CARD-FORMAT.xml, spec/02-EXECUTABLE-SCAFFOLDS.xml),
• the operating playbooks (spec/03-RAID-PLAYBOOK.xml campaigns, spec/04-SWEEP-PLAYBOOK.xml the standing sweep, spec/05-CAMPAIGN-FORM.xml the campaign paper trail, spec/06-WAL-CONVENTION.xml session-durable state — optional but preferred),
• the mechanism specs under spec/mechanisms/ (ENGINE-CONFORM, PROP-014 specmap, BROWNFIELD-PROTOCOL, LEDGER-INTENT — the units spec://org.vibevm.ai-native/core-ai-native/… tags cite),
• and spec/appendix/.

04The concrete per-language cards/ and the runnable checkers ship in each language stack, not here.

05Do not read it all at boot — the Discipline's own delivery rule is minimal sufficiency:

• 06load a card's Band-3 ops block only when its trigger fires;
• open a playbook when you run its procedure.

07The two laws that always apply:

1. 08Idiomatic inside the file, engineered around the file. Code surface stays ordinary and in-distribution; all added strictness lives in types, contracts, metadata, and the verification loop.
2. Explanation capital must be runnable capital. Prose that could be a checker, doctest, or typed API is a WISH until it becomes one.

09Card registry: the active language stack's spec/cards/INDEX.md (trigger → card; the nine executable scaffolds A–I in their per-language shape).

10Cross-cutting sweeps follow 03-RAID-PLAYBOOK.xml.

11A rule with no checker is a WISH; a deviation with no reason is a defect (#[spec(deviates, reason)]).