Conformance: executable anti-collapse suite for Fundamental refusal boundaries

[zachshallbetter]

Parent: #1111
Depends on: #1112
Related: #1114

Goal

Turn the research program's recurring refusal boundaries into a dedicated negative-conformance suite so later implementation cannot silently collapse neighboring concepts that are intentionally distinct.

This is not a new ontology. It is a test wall over boundaries already supported or proposed.

Initial invariant set

At minimum test:

• world/state != projection;
• projection != coupling/mutation;
• relationship/association != force/causation;
• capability != permission;
• operation exposure != operation authority;
• candidate != claim != evidence;
• evidence != inference != argument;
• evaluation != qualification != promotion;
• information != decision != enforcement != evidence;
• closure/resolution != desirability/approval;
• history admissibility != history evaluation;
• constraint != objective;
• actual/reconstructed/counterfactual history remain distinct;
• agent-readable != agent-writable;
• unknown/unresolved never silently maps to satisfied/permitted;
• authority cannot establish an unsettled external fact merely by deciding it;
• diagnostics/observation do not perturb the world they report.

Shape

Each boundary gets:

• source/decision id;
• positive fixture for legitimate composition;
• negative fixture that attempts the forbidden collapse;
• expected failure code;
• owning contract/layer;
• maturity/provenance status.

Where the boundary is not yet implemented, mark pending-contract rather than faking a passing test.

Guardrails

• Do not test slogans. Each fixture must exercise actual code or an explicit schema validator.
• not applicable is a valid result where a boundary belongs only to an experimental lane.
• A passing fixture written specifically around the implementation is implementation evidence, not independent validation.

Acceptance

• Machine-readable registry of refusal-boundary tests.
• Existing shipped/experimental boundaries have executable negative tests.
• New [epic] World substrate vNext — protocol convergence + history-space #1111 child contracts add their negative controls to the same suite before promotion.
• CI can fail on a newly introduced conceptual collapse without claiming that the suite validates the theory externally.