| CC-A15.4-1 (One attempted use; proportionate prerequisite account) | Before an appearance guides work or reliance, a conforming use names one exact attempted use and every independently required object. An ordinary one-prerequisite case may use the six-line plain note and stop. A structured case uses one RequiredPositionEntries row per direct object; every row supplies SubjectPatternLocator, the exact direct-object kind, native project-side ref, required posture and currentness, and dependency on the attempted use. It never stores comma-separated patterns, kinds, or refs or coerces them into a generic U.EntityRef list. If a required prerequisite is absent or fails its posture, AllowedUseNow stays at the safe narrowed use. | Keeps the ordinary path light and every structured prerequisite under the rule or test that defines it. |
| CC-A15.4-2 (P2W publication use boundary) | A principle scheme, functional diagram, scenario, screen, or explanation that exposes a P2W chain guides only the A.15 work or planning kind selected by the project use: method-family selection, selected method, U.WorkPlan, dated U.Work, work-result record, or result measurement. Claims outside that selected use require their own relation or result and source relation named by value. | Keeps P2W publication use tied to the work use under repair instead of turning publication form into project authority. |
| CC-A15.4-3 (Lowering and refresh) | When a required relation or result, its SubjectPatternLocator, source-currentness relation, revocation relation, affected Work target, relying context, or time window cannot be recovered, the disposition is orientation, source-finding, contested use, bounded reversible probe, repair request, or blocked unsupported claim. The note states the return or refresh condition for the first failed prerequisite; a structured use keeps independently required currentness, decision, evidence, state, copied-source, generated-source, and publication objects in separate rows. | Keeps A.15.4 useful without admitting a repair relation or generic source kind. |
| CC-A15.4-4 (Exact reopening judgment) | Naming is only the first recovery step. Before AllowedUseNow permits the attempted use, follow every typed ref and verify that its relation obtains or its result says pass or ready under the criterion defined for it, is current, covers the beneficiary, action, target, scope, and window, and has any evidence-use, source-currentness, or other source relation required by this reliance. A relevant PermissionNormConflictFinding@Context has its own row and current A.2.8.PER disposition; an unresolved or norm-selecting result blocks the affected use but does not make a separately obtaining grant cease. Any separately required A.21 gate decision is current, and any separately required A.15.5 work-entry-readiness result says ready under its exact criterion and remains inside its reliance window. A named, recorded, but revoked or mismatched grant keeps the use blocked. | Prevents explicit records and green displays from substituting for current world-side or institutional conditions. |
| CC-A15.4-5 (Register source is not the effect) | A register-backed reliance keeps the register-entry episteme, its publication relation, constitutive rule, authorized entry-producing Work, actual exercised Work or evaluation Work when current, direct relation/finding, and evidence/currentness relation separate. For every asserted Work, identify the actual performer from the performance facts and independently recover its A.13 core basis; A.15.1 independently admits the dated occurrence. Add F.6 only when the result must also identify the assignment under which that Work was performed; a failed check leaves the Work intact. The entry is authoritative source only for the exact claim or effect covered by the named rule. Inscription establishes none of them. | Prevents record-as-world and record-as-Work overread. |