B.3.5:9.2 - Normative rules (MUST/SHALL clauses for thinking‑and‑writing)
S‑1 (Working-Model first). Authors SHALL state each covered direct relation claim in Working-Model form. Assurance accounts remain below that public layer. Electing this profile adds branch-specific trace and mode obligations; it is not a precondition for direct use.
S‑2 (Alias declaration).
If a Working‑Model relation follows a known general principle, the author SHOULD declare tv:AliasOf <Principle>, thereby making the intended use‑pattern explicit for reviewers and future readers. (This improves comparability without introducing extra formality.)
S‑3 (Grounding by mode).
For every relation instance covered by an elected B.3.5 profile, the author MUST set validationMode and follow the corresponding grounding stance:
-
S‑3.a
postulate. For a branch that permits it, the author may omit constructive grounding, state the working scope, and give the empirical cues that would challenge the claim. -
S‑3.b
inferential. For a branch that permits it, the author gives a short reasoned chain from admitted statements that a peer can follow. -
S‑3.c
axiomatic. The author links the assertion to the current C.2.1 trace episteme required by its branch. A competent peer can recover the exact participants, direct relation occurrence, applicable rule, and identity or reidentification conditions. The account supports inspection; it creates none of those facts. -
S‑3.d Structural parthood. A covered
ComponentOf,PortionOf, orAspectOfassertion requiresvalidationMode=axiomaticand the applicable current C.13 construction account;postulateis not available. -
S‑3.e Collection belonging. A covered belongs-to assertion uses the rule defined for that collection and requires
validationMode=axiomaticand one current C.13settrace. The trace reports already established belonging and collection identity. A logical argument or evidence object may support the inclusion decision separately, but neither substitutes for the elected set trace, turns belonging into parthood, or prohibits a separately grounded part claim.
S-4 (Relation-kind sense-making).
-
For structural
ComponentOf,PortionOf, andAspectOfclaims, the elected profile requires the applicable current construction account andvalidationMode=axiomatic. -
For collection belonging, the elected profile requires one current
C.13 settrace andvalidationMode=axiomatic. The collection’s own rule still decides whether the occurrence obtains. -
For other epistemic or constitutive links, constructive grounding remains optional and the branch may prefer inferential or postulate reasoning with empirical cues.
S‑5 (Order and time do not establish parthood). Execution order, parallelism or interval inclusion alone SHALL NOT establish a part-whole relation. State Method composition under B.1.5 and temporal facts under C.27; use B.1.4 when those recovered relations must be aggregated. Independently established A.15.1 Work-part relations and A.14 proper-phase relations for unchanged non-Work carriers remain admissible under their own rules.
S‑6 (Unidirectional dependence). CT2R‑LOG may consume Compose‑CAL and KD‑CAL conceptually; it SHALL NOT redefine them. Meaning flows downward only (Kernel → Extension → Context → Instance).
S‑7 (Register discipline).
When naming principles in tv:AliasOf, authors SHOULD use Tech/Plain twin labels where available and obey minimal‑generality and rewrite rules (LEX‑BUNDLE), so that aliases are recognisable across contexts of meaning.
S‑8 (No tool talk). Core prose MUST NOT introduce CI/CD terms, file formats, APIs, or machine‑oriented notations in place of concepts. If examples are needed, they MAY be plain‑language narratives or domain vignettes. (This pattern is conceptual by Standard.)