C.29:9 - Conformance Checklist

Use this checklist after constructing or delimiting the result in :4.1. Its conditions concern the actual correspondence, consequence and receiving use; a completed form alone does not satisfy them.

ID	Requirement	Purpose
`CC-C29-0 Use condition`	Use C.29 only when a mathematical object, formalism, family, learned representation, or simulation object is used for explanation, decision, prediction, publication, comparison, assurance input, bridge, or reusable transfer, or when a stable problem needs a first candidate lens that could change the next lens-use action.	Keeps local analogies lightweight.
`CC-C29-1 Mathematical move before record`	State the question, choose a concrete object, establish its correspondence and losses, and derive or delimit the consequence before selecting the sufficient record under :4.4.	Keeps recording subordinate to the mathematical work.
`CC-C29-1a Computational construction`	When the mathematical result needs a computational construction, use C.29.2 to obtain the procedure, its interpretation, the argument supporting its claimed result and the relevant cost estimate.	Lets the reader construct or locate the missing computation.
`CC-C29-1b Realization correspondence`	When the result depends on an unsettled execution correspondence, use C.29.3 to connect preparation, system operations and readout and establish the required result relation.	Lets the reader use or repair the proposed execution.
`CC-C29-2 Named mathematical object`	A mathematical phrase affecting explanation, decision, prediction, publication, comparison, assurance input, bridge, or reusable transfer names a concrete `CandidateMathObject`, not a prestige family label.	Blocks prestige vocabulary.
`CC-C29-2a Intervention preservation`	If `LensMappingMode` is abstraction, quotient, coarse-graining, macro-model, or simulation and causal use is being claimed, state whether intervention and counterfactual structure is preserved, approximated, or not claimed, then apply `C.28` for causal-use question and verdict.	Prevents causal abstraction laundering.
`CC-C29-3 Lens mapping mode`	State the `C.29`-local lens mapping mode and the concrete correspondence. If bridge semantics are claimed, apply `F.9`.	Makes the correspondence and any needed semantic Bridge explicit.
`CC-C29-4 Preserved structure`	State what structure the lens preserves. When the result uses a transferred operation, establish the needed preservation through C.29.1. When it uses a representative, establish that the choice leaves the required answer unchanged.	Makes the claimed preservation usable in the inference.
`CC-C29-5 Lost structure`	State which source distinctions or operations do not transfer. If none needed for this use are lost, explain their preservation through C.29.1 and distinguish any additional receiving objects from represented source objects.	Supports lossless embeddings as well as lossy representations.
`CC-C29-6 Invariants exposed`	Name invariants, obstructions, fixed points, symmetries, conservation laws, dualities, distinctions, or diagnostic boundaries.	Makes the lens usefulness visible.
`CC-C29-6a First-principles family recovery`	When a first-principles lens-family row from `C.29:4.2b` is used for claim-bearing lens use, recover the concrete `CandidateMathObject` for the candidate family, preserved structure, lost structure, visible payoff, lens-use boundary value, and stop condition or neighboring-pattern application for that family.	Prevents family names such as boundary, cohomology, symmetry, variational, RG, diagonal, composition, probability, information, or structural-information compression from replacing actual MathLensUse recovery.
`CC-C29-6b Bounded-observer structural-information lens`	When MDL, epiplexity, compression, graph information, or description-recoverability changes the next lens-use action, recover `TargetPhenomenon`, source episteme or trace, bounded observer, candidate measure or code, mapping mode, preserved and lost selected structure, visible payoff, observation or postulate boundary, source-return condition, lens-use boundary value, and stop condition.	Makes the selected structure, observer and use limit recoverable.
`CC-C29-6c Architecture-local lens descriptions`	When `MLU.Description@RGArchitecture`, `MLU.Description@MultilevelLearningFrustration`, or another architecture-local lens description is used for claim-bearing lens use, recover declared scope or scale window, candidate mathematical object, mapping mode, preserved structure, lost structure, source-return condition, next lens-use action, and stop condition; apply the neighboring patterns that define or constrain architecture, scale-preference, measurement, evidence, assurance, selected-set, and decision claims.	Makes scope, lost structure and source return explicit.
`CC-C29-7 Lens-bounded prediction or distinction`	State the actual consequence or obstruction, its premises and the use selected under :4.4. For phenomenon prediction or consequential reliance, supply the required applicability and validation account.	Makes the result and its reliance boundary inspectable.
`CC-C29-8 State, observation, and evidence separation`	If state, observation, probe, readout, or evidence is being claimed, apply `A.3.3`, `A.19`, `C.16`, or `A.10` as needed.	Prevents passive-read and dashboard mistakes.
`CC-C29-8a Receiving use`	When the lens result contributes to a separately governed question, identify that question and follow :4.4.6’s receiving action.	Connects the lens result to its receiving use.
`CC-C29-9 Scale window`	If scale, universality, knees, exponents, or coarse-graining are being claimed, declare the scale range and use `C.18.1` for scale-law adequacy, `C.19.1` for general method scale preference, and `C.31.ASAP` for architecture scale preference when the respective claim is made.	Prevents universalization.
`CC-C29-9a Temporal use boundary`	If the claim being made is about forecast, rate, trajectory, rhythm, recovery, convergence, stabilization, speed, temporal window, or rate-change as sufficient for a use, cite `C.27` or state that temporal adequacy is not being claimed.	Prevents mathematical prediction cues from replacing temporal-claim adequacy.
`CC-C29-10 Rival lens discipline`	Start with the principal rival or ordinary fallback; broaden only when the actual selection or superiority question requires it. Name the comparison criterion, cost, reader, scale window or receiving pattern that makes the claim testable.	Keeps the comparison proportionate to the intended use.
`CC-C29-10a Validation regime`	Apply :4.4’s reliance rule and :4.5a. Phenomenon-model reliance requires validation regime, evaluation slice, uncertainty/approximation, failure case, applicability and any output-change condition. A conditional derivation states its assumptions and loss without claiming empirical adequacy.	Matches validation cost to the actual reliance.
`CC-C29-10b Source-use relation`	If a source changes C.29 declared lens use, name its `SourceUseRelation` with source material reference, declared C.29 output or lens-use boundary, source-use disposition, source-currentness or supersession condition, and output-change condition. Include a blocked source-prestige overread only when it passes F.19’s plausible-reader test.	Separates the source-use relation from source-use disposition and makes its governing slots recoverable.
`CC-C29-10c Source-currentness and return condition`	If source material, source-use family, source-use decision, or a neighboring subject pattern changes the declared lens-use boundary for this output, state `SourceReturnCondition?` or `OutputChangeCondition?` and narrow, demote, replace, retire, or block the claim-bearing use.	Keeps SoTA currentness and neighboring-pattern currentness tied to the declared C.29 output rather than to source prestige or process evidence.
`CC-C29-11 LensUseBoundaryValue`	Label `LensUseBoundaryValue` as analogy-only prompt, diagnosticOnly, formal derivation, simulation, empirical fit, accepted domain theory, SoTA-echo candidate, or mechanized proof, with a matching declared-use boundary.	Prevents evidence laundering.
`CC-C29-12 No ontology smuggling`	Do not import source-domain ontology without separate proof or evidence and subject pattern.
`CC-C29-13 Stop condition`	State the condition for narrowing, stopping, returning to source material, or applying a neighboring pattern.	Makes closure locally visible.
`CC-C29-14 Bridge discipline`	Cross-context mathematical transfer cites `F.9` when semantic correspondence between local senses is needed; Bridge and C.29 fields agree without duplicate writing.	Keeps semantics bounded.
`CC-C29-15 Causal-use discipline`	Causal-use claims apply `C.28`; C.29 cannot carry a causal-use verdict by itself.	Blocks causal laundering.
`CC-C29-16 Assurance discipline`	Assurance, release, reliability, and engineering-justification claims apply their direct subject patterns: `A.10` for evidence reliance, `B.3` only for an actual named assurance claim, the direct domain pattern for the release, reliability, or engineering-justification result, and relevant G patterns for their claims.	Prevents elegance from raising assurance directly.
`CC-C29-17 Meaning recovery`	If wording obscures the object, claim or participants needed for the current lens use, rewrite it so the reader can identify them and take the next lens-use action. Use `C.2.P` only when an unresolved epistemic distinction still prevents selecting or using the relevant pattern. If the meaning cannot be recovered, state the unresolved point and stop the dependent use. Keep ordinary wording when it already supplies the needed meaning.	Makes the statement and its next use recoverable.
`CC-C29-18 Plain and Tech balance`	A Plain sentence can remain when it aids recognition; if it makes ontology, evidence, causal, assurance, bridge, gate, work, decision, or use-boundary commitment, that commitment is recovered through the Tech fields or neighboring pattern.	Preserves didactic usefulness without shadow semantics.
`CC-C29-20 Repair failed conditions`	For each failed required condition, apply :4.5b and state the resulting repair, narrowed use, return or stop.	Makes the next corrective action or stop explicit.