// Turn capsule invariants and boundary crossings into executable contracts. Use after creating a concept capsule, or when invariants need to be enforced in code. Covers preconditions, postconditions, constructor validation, domain types, and contract tests.
| name | contract |
| description | Turn capsule invariants and boundary crossings into executable contracts. Use after creating a concept capsule, or when invariants need to be enforced in code. Covers preconditions, postconditions, constructor validation, domain types, and contract tests. |
| argument-hint | [invariants to enforce, or 'audit' to check current coverage] |
Turn capsule invariants into executable contracts: domain types that prevent invalid states, validation at boundaries, and tests that prove enforcement. Operationalizes "design by contract" (Meyer) and "parse, don't validate."
Invariants to enforce (or audit to check current coverage): $ARGUMENTS
Preconditions:
/pragma:capsule first./pragma:card + /pragma:slice first.Also read: the capsule (glossary + invariants), recent cards (boundary crossings), and existing source code.
For each capsule invariant, determine current enforcement status:
| Invariant | Enforcement | Location | Evidence |
|---|---|---|---|
| [from capsule] | Type system / Constructor / Test / None | [file:line or "missing"] | [test name or "none"] |
Enforcement levels (best → worst): Type system (invalid states unrepresentable) → Constructor/validator (checked at entry points) → Test (at least a check somewhere) → None (fix this).
For each public entry point in scope:
Module: [name]
Function: [name]
Preconditions: [what must be true on entry]
Postconditions: [what must be true on exit]
Errors: [what can go wrong and how it's signaled]
Use glossary terms. No clear pre/postconditions → design smell, module may need splitting.
One invariant at a time. Prioritize "None" first, then upgrade "Test" → "Constructor" → "Type system":
Keep tests green throughout. Do not change behavior — only tighten enforcement.
Write or update docs/contracts.md with:
Run full verification harness. All checks must pass. Contract extraction must not change behavior.
Commit: Contract: enforce [invariant] at [boundary]
/pragma:card./pragma:contract passes, or back to /pragma:card + /pragma:sliceState: governance, Next: /pragma:consult (or the explicitly recommended next step), Loop: /pragma:consult (default unless user explicitly continues directly)Read and write a Petri net (SDCPN) document by Automerge URL. Use when creating, editing, or querying Petri nets — adding or removing places, transitions, arcs, color types, differential equations, and parameters.
Create and maintain an Assumption Ledger — a persistent record of assumptions, their confidence, and validation status. Use when starting a new slice, resuming work in a new context window, or when implicit assumptions risk causing drift. Tracks requirements, architecture, and implementation assumptions.
Create or update a concept capsule — the conceptual anchor for a project or feature area. Use before writing code on a new project or feature, or when terms and boundaries feel unclear. Defines glossary, invariants, happy-path scenario, and non-goals.
Write a tracer-bullet card — a precise specification for one thin end-to-end slice of work. Use when scoping a new slice, defining what to build next, or breaking a feature into provable increments. Covers target behavior, boundary crossings, risks, and definition of done.
Create characterization tests (Golden Master) for existing code so you can refactor or replace safely. Use before refactoring, strangler-replacing, or modifying code with unclear behavior. Captures observable behavior with a minimal harness, producing tests, fixtures, and a coverage report.
Methodology triage consultant for tracer-bullet development. Use when unsure which pragma skill to run next, when starting a new project, or when the current approach feels stuck. Interviews the user, assesses state, and recommends the next pragma skill.