matrixscroll: Instructions file for Claude Code

Prose rules

Read these rules before editing user-facing text. The style supplement defines terminology. The ssx360-prose skill provides additional guidance.

Run Vale before editing and again before publishing. The linter checks prose patterns. Source review and workflow tests establish whether the claims and instructions are supported.

Voice and structure

Use active voice, sentence-case headings and present tense. Address the reader directly in instructions. Name a concrete command, field, version, date or source in each paragraph.

Use periods, commas or parentheses instead of em dashes and en-dash separators. Use a hyphen for numeric ranges. Keep negative parallelism to one deliberate instance per page. Retired AP2 mandate-chain slogans stay retired.

Prohibited wording

Avoid these words and phrases in public copy:

seamless, seamlessly, cutting-edge, robust, game-changer, unleash, elevate,
next-gen, revolutionize, delve, tapestry, leverage, harness, empower,
state-of-the-art, best-in-class, world-class, paradigm shift, supercharge,
frictionless, turnkey, holistic, synergy, bleeding-edge, military-grade,
bulletproof, future-proof, in today's landscape, the future of, deep dive,
rapidly evolving, it is important to note that, it should be noted that,
in order to, utilize, prior to

Gold standard

The gold-standard policy governs protocol, crypto, verification, gates and public claims. Preserve the required code-owner review and source-traceable evidence.

Do not land AI-generated or AI-altered bytes as authority in the verified core: vectors, ACVP fixtures, TLA+ models, schemas and SPEC. Digest-pin provenance. No AI system decides a technical conclusion.

Preserve fail-closed CONSISTENT, INDETERMINATE and INCONSISTENT verdicts with exit codes 0, 1 and 2. No silent pass on missing evidence. Do not claim an extracted Lean 4 or F* verifier until it exists in the tree.