| CC‑A.6.1 (Stack declaration). | A conforming boundary description SHALL identify Signature, Mechanism, actual-occurrence, consequence/evidence, and Publication placements. A dated Work claim SHALL remain separate from any application result, production, change, delivery/transfer, evidence, or acceptance claim selected through A.15.1:4.6. | Prevents one “work and evidence” layer from recreating intrinsic outputs. |
| CC‑A.6.2 (Square discipline). | A conforming boundary description SHALL classify each atomic claim by its own modality and adjudication position. Every permission-looking claim SHALL cite one selected A6-AW-* row and that row’s direct object; the selected subject pattern or kind of direct object alone never sets the quadrant. | Makes one actionable choice replace repeated permission catalogues. |
| CC‑A.6.5 (Actual-occurrence, description, and carrier separation). | An E-* claim SHALL identify the exact actual occurrence or evaluated finding under its subject pattern and SHALL NOT infer Work merely because change or a carrier exists. Any carrier used for reliance SHALL enter the exact evidence relation. | Preserves non-Work change and blocks carrier-as-effect errors. |
| CC‑A.6.6 (Viewpoint accountability). | Every published MVPK face use SHALL identify the selected episteme and bounded reader/use. When U.View membership or viewpoint identity is used, the face SHALL identify the exact viewpointRef. U.View membership still requires E.17.0 conformance. Normative face content MUST cite canonical L/A/D/E claims by ID or canonical location and name their direct objects; meaning-preserving prose may explain them. Face content MUST NOT introduce a new commitment or any new object or claim selected through A6-AW-*. | Preserves viewpoint discipline without letting a publication face create governance or permission claims. |
| CC‑A.6.6a (MVPK face‑kind discipline). | A publication that claims MVPK alignment MUST use E.17’s declared publication-face kind values: publication face/form and interop publication form. PlainView, TechCard, InteropCard, and AssuranceLane are face designators, with profiles selected under E.17. A publication MUST NOT mint additional MVPK face kinds. Local “cards” may exist only as headings or sections inside the selected faces. | Aligns with MVPK and publication-face or publication-form discipline; prevents new‑face drift. |
| CC‑A.6.7 (Contract unpacking). | When ambiguity in “contract”, “guarantee”, “permission”, or “promise” language changes interpretation or use, a conforming text SHOULD use only the live A.6.C questions for the object split and A.6.B:8.4.1 for classification. Promise content, instituting speech-act Work, commitment or grant, dated performed Work, application/result binding, production, delivery/transfer, evidence, and acceptance MUST remain independently optional objects under their subject patterns. | Stops agency attribution and result/output rebundling. |
| CC-A6-CAUSAL-DEONTIC-SPLIT (Causal/deontic split). | When causal support and authority wording share a sentence, a conforming description SHALL use C.28 for the causal-use question and route each permission-looking claim to one A6-AW-* row. Neither result creates the other. | Prevents causal evidence from becoming hidden authority. |
| CC-A.6.9 (Authority-wording split). | Before authority-looking wording guides work or reliance, a conforming description SHALL select one A6-AW-* row per atomic permission claim and cite that row’s source and direct object. | Prevents a visible word from becoming authority or evidence. |