| CC‑B1.3.1 | Inputs to Γ_epist MUST be U.Episteme holons; ComponentOf is forbidden; use ConstituentOf, UsageOf, or ReferenceTo for their different claims; use a collection’s own belongs-to predicate only for collections. | Prevent category errors. |
| CC‑B1.3.2 | Provenance and SCR MUST be preserved in the aggregate; dropping sources or methods is non‑conformant. | Enforce Evidence Graph Referring. |
| CC‑B1.3.3 | Any aggregate R MUST follow the justified input meanings, scales, support dependencies, and receiving model. No default min, max, or F-to-R conversion is supplied; absent a common model, retain a bounded synthesis and separate support. | Prevent unsupported assurance and preserve useful non-aggregate results. |
| CC-B1.3.4 | Contrary evidence MUST remain visible. An established scope or interpretation difference may separate claims; an unresolved conflict must qualify, narrow, or defeat the affected conclusion. Use B.2 only for a separately grounded whole-reidentification question. | Keep the practical effect of disagreement visible. |
| CC‑B1.3.5 | Every U.Episteme serving as an input to Γ_epist MUST declare its mode (axiomatic or postulative). An aggregate holon’s mode MUST be postulative if any of its constituents is postulative. | Prevent category errors in reliability calculation. |
| CC-B1.3.6 | A cross-context meaning use names explicit mappings, exact source and receiving F.17 cells, an obtaining F.9 Bridge, a separate bounded-use claim and permitted loss, and any reliance result the fold consumes. CL alone never grants the use. | Make semantic crossing inspectable. |
| CC-B1.3.7 | An order-dependent conclusion MUST meet PO-SYN-ORDER and B.1.4:4. If an episteme history matters, exact C.2.1 endpoint identities and any obtaining EpistemeEditionRelation MUST be named; any proper restriction or B.1.4/Γ_time aggregation MUST cite only already recovered temporal relations. | Preserve order, identity, continuity, and temporal integrity. |
| CC-B1.3.8 | Keep design-time synthesis, target-scheme compilation, one actual operation application and its returned value, dated Work, performer and any relied-on assignment, production or first existence, publication, carrier, release, and acceptance separately governed. | Preserve semantic and practical boundaries. |