Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:25:10 UTC

A.6.RSIR:12 - Relations

Use F.19 for the whole-span reading with the compact cues in E.10:0.2. Apply E.10.ROLE once to bare claim-bearing role. Apply RSIR afterward only if one concrete direct-relation, declaration, interface, operation, or representation question remains; all other recovered branches use their direct rules and leave RSIR closed. E.10.ARCH describes both entries in the shared restoration architecture.

A.6.5 defines complete declaration-local SlotSpec = <SlotKind, ValueKind, refMode> content inside one RelationSignature and, only when a compatible SlotSpec is current, participant-designation typing. C.2.1 supplies the assertion or description episteme’s identity rule, while the direct claim rule supplies predicate, polarity, and use. An ordinary assertion may designate actual participants directly without reusable declaration.

Apply A.6.P for relation precision restoration after the recovered object is a relation or relation-bearing claim.

A.6.0 defines U.Signature; A.6.1 defines operation argument and result declaration content plus the rules for any independently identified application and declaration-local binding; E.20 supplies mechanism-introduction rules. A.6.1 admits no public OperationApplication U-kind or universal input/output/result relation, and its result binding alone establishes none of production, a produced entity, a result episteme, evidence, or work.

A.2, A.2.1, A.2.2, A.2.5, A.2.7, A.15, and Part F system-role-description and naming patterns define or constrain local system-role kinds, direct system-role assignments, capability, SystemRoleAssignmentStateRelation, SystemRoleKindRelationStructure, system-role–Method–Work alignment, and durable system-role-kind names.

Apply A.6.M, A.6.F, A.6.A, A.3.4.P, E.18, C.30, C.30.ASV, C.30.AD, or C.30.TFS-REL for the corresponding module-interface, functional, affordance, transformation, transformation-flow, architecture-of, structural-view, or architecture-description question.

Apply C.2.1 for episteme identity and content, E.24.PUB for publication availability and occurrence identity, and E.17 for a needed reader-facing form of an accepted account. Use C.2.P.DR, A.10, B.3, G.6, F.10 or C.28 for the corresponding declarative representation, evidence, assurance, provenance, status or causal-use question; the direct claim rule still supplies the predicate, polarity or use asserted through that content.