PRISM v2.0.2 released

[Ronkupper]

PRISM v2.0.2 ships §4.12 Atomic-prompt self-containment, codifying that dispatched envelope text must carry inline operational definitions for PRISM-native shorthand (M-codes, SP-codes, monitor names, claim IDs) at first use within the envelope.

Why. A Cowork-as-orchestration diagnostic run (Round 6, 2026-05-03) surfaced a vendor-side prompt-construction failure: when an executing vendor with strong competing priors for the same shorthand receives bare codes, it pattern-matches to its strongest training-distribution prior rather than to the PRISM definition. Gemini DR did this 3/3 times in a single dispatch wave. Inline-expanded definitions in the same wave produced correct convergence across all vendors.

Surface.

• New §4.12 with rule, example, rationale, scope, and an optional glossary-block template.
• Cross-references added in §4.1 (Content rule), §4.11 (Self-containment), and §9 intro (Dispatched-text note).
• Mandatory at first use within an envelope; subsequent uses bare. Glossary block remains operator-discretion.
• Future PRISM-native shorthand additions inherit the rule — §4.12's scope set is illustrative, not exhaustive.

Compatibility. Backwards-compatible. Existing v2.0.1 prompt-pack templates not invalidated; they execute correctly when dispatched to vendors without competing priors. Retrofit to inline-expansion is optional hardening.

Note. PRISM.md now uses named cross-references throughout (§{namespace.slug} form), migrated earlier today. v2.0.2's new cross-refs follow the new convention.

Release: https://github.com/Ronkupper/PRISM/releases/tag/v2.0.2