#Working-Model Relations & Grounding (CT2R-LOG)

B.3.5 · Stable · Pattern · Part B - Trans-disciplinary Reasoning Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Status: Stable Type: Pattern

At a glance. Use B.3.5 when a human-facing structural relation or a collection's own belongs-to relation has been selected for an additional assurance account without exposing constructive machinery as the public vocabulary.

Use this when. Use this assurance profile only when a publication choice or named current requirement elects it for a direct relation claim. State the readable relation first. After election, structural parthood and collection belonging follow separate trace and validationMode obligations. The trace reports independently grounded facts for inspection; it creates neither the relation occurrence nor the entity it describes.

What goes wrong if missed. The readable relation and its assurance account collapse: authors either lose usable relation sentences, treat collection belonging as parthood, prohibit separately grounded parthood by label, or make a trace look like the cause of the claim.

What this buys. Working-Model relations stay readable, while an elected assurance branch supplies the right inspectable account without changing the direct relation kind.

Not this pattern when. Not this pattern when a direct relation claim is sufficient and no publication choice or current requirement elects this assurance profile. Also not this pattern when the current question is how to construct the trace (C.13), which mereology relation kind is intended (A.14), whether a whole must be reidentified (B.2), or whether a candidate name deserves durable U-kindhood (E.24.UK).

One‑line summary. CT2R-LOG keeps ComponentOf, ordinary belongs-to sentences, PortionOf, and AspectOf readable while respecting their different relation kinds. When this assurance profile is elected, structural parthood uses its applicable construction account; collection belonging uses a current C.13 set trace. Neither branch changes what makes the direct relation obtain, and neither trace decides whether a separate part relation is possible.

Provide a single, human-facing family of Working-Model relations as the public relation layer, with explicit hooks for (G) grounding and (R) reliability, without exposing constructor jargon or overloading day-to-day authors.

#Relations

#Content

#Intent

Provide a single, human-facing family of Working-Model relations as the public relation layer, with explicit hooks for (G) grounding and (R) reliability, without exposing constructor jargon or overloading day-to-day authors.

What you get (manager/engineer view). The same relations you already know (e.g., ComponentOf) remain the public relation vocabulary.

What changes when the profile is elected (auditor/ontologist view).

• Each covered published edge carries two additional commitments:

  1. tv:groundedBy → points to the support required by the relation's branch: the applicable sum or slice trace for structural parthood, one current C.13 set trace for the collection's belongs-to relation, or an admissible argument or evidence object for another permitted claim.
  2. validationMode ∈ {axiomatic, inferential, postulate} → declares how the author justifies the assertion.

The pattern that defines the relation still decides when it obtains. CT2R-LOG records the public alias, the branch-specific support link, and the declared assurance posture; Lang-CHR supplies the labels.

#Problem Frame

B.3.5 exists where a readable Working-Model relation must remain usable by practitioners while assurance readers still need a grounding relation and declared validation stance. The EntityOfConcern is not a notation, trace file, or tool output. It is the relation-use discipline that keeps the public relation layer and assurance grounding layer distinct.

#Problem

Working-Model relations such as ComponentOf and an ordinary belongs-to sentence are easy to use but not self-justifying. Their declarations alone do not show which participants and occurrences obtain, which rule defines the relation, or what identifies the whole or collection. Conversely, exposing construction traces everywhere makes the graph unreadable to non-specialists.

We need: a stable public relation layer for relations and, where this profile is elected, a required, reconstructible grounding channel plus a visible validation intent that downstream assurance can reason about. The direct relation layer does not depend on electing the profile.

#Forces

• Two audiences, one dial. Project managers want one relation family and stable views; assurance readers want an inspectable construction account with explicit direct facts and identity conditions.
• Parsimony constraint. The Kernel stays minimal; construction is outside the Kernel.
• Unification inside FPF. We already unify external vocabularies; the same discipline is applied internally so patterns that publish structural claims can reuse one three-form construction-account discipline and one readable relation façade without making that account a second ontology.

#Solution (thumbnail)

CT2R‑LOG introduces a two‑link discipline and a validation flag around each canonical edge:

1. Alias link (concept‑level). Working-Model relations (e.g., ut:ComponentOf) are the public names for their exact direct relation principles. tv:AliasOf may point from the public relation kind to that principle for comparison and reuse; the alias defines neither an occurrence nor a whole.

2. Grounding link (assurance level). Each relation assertion covered by this elected profile carries tv:groundedBy according to its direct relation kind:

   • Structural parthood (ComponentOf, PortionOf, or AspectOf) requires one current C.2.1 construction-trace episteme in the applicable sum or slice form and validationMode=axiomatic. postulate is not available for this branch.
   • Collection belonging under the collection's own rule requires one current C.2.1 C.13 set trace and validationMode=axiomatic. The trace reports the collection, the entity, the already established relation, the rule for belonging, and the identity conditions. It does not make the entity a constructive part, make belonging obtain, or prove that separately grounded parthood is impossible.
   • Other epistemic or constitutive edges may use an admissible evidence object or logical argument under validationMode ∈ {inferential, postulate} when no constructive trace is appropriate.

3. Validation flag (author intent). Every relation or aggregation rule covered by this profile carries tv:validationMode with one of:

   • postulate — pragmatic working claim backed by observations;
   • inferential — reasoned consequence with a followable argument; or
   • axiomatic — one inspectable construction account is the declared assurance basis.

The direct branch above selects which modes and grounding targets are allowed. The flag is an assurance posture, not a species of world-side relation and not an identity or timelessness guarantee.

F–G–R alignment. F (the published relation claim): :PumpA ut:ComponentOf :Skid12. G (its inspectable grounding account): the assertion links to :trace_Γm_sum_456, a C.2.1 episteme about the exact direct construction facts. Assurance posture: tv:validationMode=axiomatic is the author's declaration. B.3.3 assesses the actual grounding for the receiving claim and use; a level is published only through an applicable justified profile. The declaration does not alter formality or establish empirical adequacy.

#Structural CT2R Typing-Grounding Unfolding Structure Block

When a constructive trace, working-model relation, and target kind or logical representation must be carried together across contexts, use this block or cite an equivalent A.22.CGUS specialization. The block is useful when the reader must see the passage from constructional material to a typed or logical claim without treating a readable relation label as proof.

StructuralCT2RTypingGroundingUnfoldingStructureBlock:
  unfoldingStructureRef: current StructuralCT2RTypingGroundingUnfoldingStructure record
  workingModelOrConstructiveRepresentationRef:
  targetKindOrLogicalRepresentationRef:
  bridgeRef?:
  constructiveTraceRef?:
  preservedStructure:
  lostOrCollapsedStructure:
  CL_or_CLk:
  admissibleReuse:
  blockedSubstitution:
  evidenceOrProofLinkageRef?:

unfoldingStructureRef names the current local structure record. StructuralCT2RTypingGroundingUnfoldingStructure is a local [A.22.CGUS](/generated/patterns/A.22.CGUS) U.Structure specialization whose block is governed by B.3.5 only for structural construction-to-typed/logical projection; the A.22-level relation to that narrower specialization, when needed, is specializedStructureRef? on the generic CGUS record. It is not a root U-kind, proof, empirical evidence, work plan, decision, or general ontology-return structure. [C.13](/generated/patterns/C.13) contributes constructive-trace loci; [C.3](/generated/patterns/C.3) contributes kind intent, extent, subkind, and bridge loci; neither creates separate authority for this block.

When an inadequate working account requires general diagnostic recovery of the exact subject construction, use [A.7.1](/generated/patterns/A.7.1). That return may stop at a direct relation, system-role assignment, state or capability, Work occurrence, holon recognition, or the pattern for another subject without opening this structural CT2R specialization.

workingModelOrConstructiveRepresentationRef names the relation, trace, model, or representation being carried. targetKindOrLogicalRepresentationRef names the typed or logical target. bridgeRef and CL_or_CLk are mandatory when cross-context or kind-level movement is current. preservedStructure and lostOrCollapsedStructure state what survives the passage and what the published relation no longer carries. Evidence linkage remains with B.3 evidence and assurance subject patterns; proof linkage remains with the proof or mathematical subject pattern that is current. The unfolding block only makes the structure of the passage inspectable.

#Vocabulary & notation (normative)

• Working-Model relations (front‑stage). ut:ComponentOf, ut:PortionOf, and ut:AspectOf are publication-grade structural relations under their direct A.14 rules. A collection uses the belongs-to predicate defined by the pattern for that collection; FPF has no public generic ut:MemberOf relation. Belonging is not a sub-property of ut:PartOf, ut:StructPartOf, or ut:EpiPartOf, but the same entities may separately stand in a constructive part relation when its own rule and all six A.1 matters pass.

• Alias principle (lexical). tv:AliasOf links a public relation type to the exact direct relation principle whose reading it carries (for example, ComponentOf points to the direct structural-component principle). The alias supports comparison; it neither defines an occurrence nor says that a sum expression produced the relation.

• Grounding (per‑edge). When this profile is elected for structural parthood, tv:groundedBy points to the applicable current C.2.1 construction trace and validationMode=axiomatic. When elected for collection belonging, it points to one current C.13 set trace under the collection's own rule and also uses validationMode=axiomatic. Other epistemic or constitutive claims may use a logical argument or evidence object under their permitted mode. Every target supports replay of the assertion's basis; it creates neither the direct occurrence nor entity identity.

• Trace family. Γ_m.sum, Γ_m.set, and Γ_m.slice are the C.13 forms used by the covered branches. sum and slice report structural-parthood constructions; set reports an already grounded collection and the belongs-to occurrences established under its own rule. No form creates the facts it reports, and no temporal or workflow form is added.

• Validation flag. tv:validationMode ∈ {postulate, inferential, axiomatic} is required on every claim covered by this elected profile. Structural parthood and collection belonging use axiomatic with their branch-specific current trace. A direct relation outside the profile has no B.3.5 field obligation.

#Archetypal Grounding - Running example

Story. A refinery team publishes :PumpA ut:ComponentOf :Skid12.

• Publication — Working-Model relation layer. They publish one assertion using the Working-Model relation ComponentOf and declare its U.Formality (typically F≈F3, controlled narrative). Only the Working-Model relation is visible to readers.

• Constructive grounding (Γₘ). In the background, the published assertion links to :trace_Γₘ_sum_456, a C.2.1 episteme that names the exact pump and skid, the direct fastening, coupling, enclosure, terminal, flange, and seal occurrences that obtain, the applicable skid assembly rule, and the skid reidentification rule. An auditor replays that account to inspect the assertion's basis. The same listed parts under a different assembly can form another whole, while a permitted pump replacement can preserve Skid12; the direct relations and reidentification rule, not the trace or input list, decide.

• Assurance stance & R-lane. Because the assertion is linked to the construction account required by its elected branch, authors set tv:validationMode=axiomatic. The account makes the relation's basis inspectable; the declaration does not strengthen that relation, fix identity or make it timeless. B.3.3 considers the actual grounding and its currentness for the receiving claim and use.

• Contrast (epistemic). When the same team asserts :MassFlowRepresentation RepresentationOf :FlowModel, they declare validationMode=postulate and attach a calibration dataset instead of a Γₘ trace. Judge that empirical basis for the claimed representation and receiving use; the declared mode alone does not establish lower confidence. Under B.3.4, a changed configuration, calibration qualification or other relevant premise can reopen the claim. The dataset's age alone does not defeat still-applicable support.

Result: one visible relation for engineers, a grounding reference and a validation-mode declaration for reviewers.

Collection case — Fleet North. First publish the ordinary sentence: “Vehicle 12 belongs to Fleet North under its registration rule.” Under that rule, the occurrence begins when Fleet North accepts the vehicle's registration, ends on withdrawal or transfer, and a later accepted registration begins another occurrence. If no current publication choice or requirement elects this profile, the direct sentence is sufficient and the author stops.

Here the fleet publication elects the profile. It links the assertion to one current C.13 Γ_m.set trace that names Fleet North and its identity rule, Vehicle 12, the obtaining registration occurrence, the registration rule, and its ending and recurrence conditions; it declares validationMode=axiomatic. If a vehicle enters or leaves the fleet, or the rule changes, the earlier trace remains an account of its earlier state but is not current support for the later assertion. The register and trace report the relation; neither creates it. They prove neither ComponentOf nor that a separately grounded constructive part relation is impossible.

#Author Standard (at a glance)

When you add or import a relation edge:

1. Pick a Working-Model relation sentence such as “Impeller ComponentOf Pump” or “Vehicle 12 belongs to Fleet North under its registration rule”; avoid raw ut:PartOf unless you are drafting meta-level axioms. If no current publication choice or requirement elects CT2R-LOG, publish that direct claim and stop.

2. When CT2R-LOG is elected, attach tv:groundedBy:

   • Structural parthood → the applicable current construction trace and validationMode=axiomatic.
   • Collection belonging under the collection's own rule → one current C.13 set trace and validationMode=axiomatic.
   • Another permitted epistemic or constitutive claim → the branch's logical argument or evidence object and allowed mode.

3. Declare the selected tv:validationMode for every covered claim.

What managers see: nothing new in the graph picture. What auditors get: a reliable trail from every edge covered by the elected profile back to its inspectable construction or evidence account.

#Compatibility & cross‑references

• B.3.2 (LOG‑use). CT2R‑LOG supplies the places to hang proofs/evidence that B.3.2 formalizes.
• B.3.3 (Assurance subtypes and levels). The declared validationMode and actual tv:groundedBy account contribute only what they establish for the receiving assurance claim. They do not compute a universal L0–L2 progression; a published level requires an applicable justified profile.
• B.3.4 (Evidence ageing and currentness). A relation assertion, its construction-trace episteme, and the warrants or evidence used for it retain their own editions and currentness. validationMode=axiomatic does not freeze a trace or make described world-side facts timeless; changed participants, relations, rules, or identity conditions require direct reinspection.

#Rule‑set — CT2R‑LOG (conceptual, human‑first)

Intent (one line). Make Working-Model relations the canonical relation vocabulary for authors, while providing a clean, purpose-selected bridge to assurance through aliasing and grounding semantics; the bridge is required only for the published assertions covered by an elected B.3.5 profile or named current requirement.

#Vocabulary and meanings in this pattern

• Working-Model relation. A human-oriented direct relation statement using a public name such as ut:ComponentOf, ut:PortionOf, or ut:AspectOf, or an ordinary sentence such as “this edition belongs to this product series.” It is the canonical public layer for readers; the direct pattern keeps the relation meaning fixed.

• Assurance Layer. Three complementary grounding modes an author MAY attach:

  • Constructive grounding: an inspectable account in one of the three C.13 forms (Γ_m.sum | Γ_m.set | Γ_m.slice). It names independently grounded participants, direct relation occurrences, the applicable construction rule, and identity or reidentification conditions. No formal notation is required, and the account does not create the relation it reports.
  • Logical grounding: a reasoned chain (think KD‑CAL style arguments) that shows why the relation follows from stated premises.
  • Mapping grounding: a relation-label alignment that shows the domain label truly denotes the intended Working-Model relation (Kind-CAL / Lang-CHR stance). These three grounding modes are complementary, not exclusive.

• Empirical Validation. How a published relation meets reality (observations, calibration scenarios). It lives beside, not inside, the relation. (See B.3 family.)

• Grounding vocabulary (tv:).

  • tv:AliasOf — declares that a Working‑Model relation is the canonical projection of a more general pattern (its “principle of use”).
  • tv:groundedBy — points to the author's grounding account (Constructive, Logical, or Mapping, as applicable). When a construction trace is recorded, it is a C.2.1 episteme with its own edition and currentness. The tv: namespace is part of the Core conceptual lexicon; it is notation‑agnostic and tool‑agnostic.

• tv:validationMode ∈ {postulate, inferential, axiomatic}. A declaration by the author of the confidence stance for a relation instance: postulate — a pragmatic working claim; inferential — a reasoned consequence; axiomatic — the author declares that a constructive account is the assurance basis for this assertion. The mode does not classify the world-side relation and guarantees neither identity nor timelessness.

Authoring note. This pattern defines meanings, not formats. The words above SHALL be used consistently and without reference to any specific notations or execution environments (Guard‑Rails: Notational Independence).

#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, or AspectOf assertion requires validationMode=axiomatic and the applicable current C.13 construction account; postulate is not available.

• S‑3.e Collection belonging. A covered belongs-to assertion uses the rule defined for that collection and requires validationMode=axiomatic and one current C.13 set trace. 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, and AspectOf claims, the elected profile requires the applicable current construction account and validationMode=axiomatic.

• For collection belonging, the elected profile requires one current C.13 set trace and validationMode=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 are not mereology). Authors SHALL NOT encode execution order, parallelism, or temporal slicing as part‑whole. Such concerns belong to Γ_method and Γ_time families and SHOULD appear as method/time statements adjacent to, not inside, Working‑Model structure. (This prevents conceptual leakage between planes.)

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.)

#Scope & Non‑Goals (to keep the plane clean)

• In scope. Canonical publication of relations for humans; alias‑to‑principle clarity; conceptual grounding stories; author‑declared validationMode; separation of structure vs order/time.

• Out of scope. Any machinery that executes checks; any binding to specific notations; any process/workflow mechanics; any discussion of file formats. (Those belong to tooling publications, pedagogy publications, and companion records; they SHALL NOT be imported by the Conceptual Core.)

• Edge placements. When a claim is chiefly about naming fit across Contexts, prefer Mapping grounding (Kind-CAL/Lang‑CHR stance). When it is chiefly about why it follows, prefer Logical grounding. When it is about what the whole is, from its parts, prefer Constructive grounding. (Authors MAY combine them.)

#Author’s working moves (micro‑playbook, notation‑free)

M‑1. State the relation in Working‑Model form (e.g., “Impeller ComponentOf Pump”). M‑2. If a publication choice or named current requirement elects this profile, pick validationMode; otherwise keep the direct relation claim and stop:

• For a permitted exploratory claim, choose postulate and state scope plus challenge cues.
• For a permitted conclusion from known statements, choose inferential and list the short argument.
• For structural parthood covered by the profile, choose axiomatic and link the applicable current construction account.
• For collection belonging covered by the profile, choose axiomatic and link one current C.13 set trace that reports the already established relation under the collection's own rule.

M‑3. Add tv:AliasOf only when a named direct relation principle helps reviewers recognize the intended reading; do not alias the relation to a constructor result. M‑4. Keep order/time adjacent, not embedded: if you need “assembled in two parallel lines”, write that as a method/time statement next to the structure, not as a part‑of edge. M‑5. Stop when the selected readable relation and remaining non-use boundary are clear and, if this profile is elected, its validation mode and required current support are recoverable without guessing.

#Bias-Annotation (auditable, human-first)

The purpose of this section is to make typical cognitive slips visible and name the counter-moves an author or assurance reader should apply in thought—not with tools. These biases are generic; the remedies point to neighboring FPF guard-rails and patterns.

Reader reminder. Bias audit is a reading aid. It never licenses tooling talk in Core; use the guard‑rails in Part E to keep semantics primacy and unidirectional dependence of layers.

#Conformance Checklist (normative, author-facing)

The following obligations regulate how to think and write CT2R content. They are notation‑agnostic and purely conceptual.

#Common Anti-Patterns and How to Avoid Them

#Consequences (benefits, trade-offs, mitigations)

Benefits

• Cognitive clarity for authors and readers. Working-Model relations remain canonical while assurance accounts stay beneath them. Every claim covered by the elected profile carries only its branch-specific support account; ordinary direct claims remain lightweight. CT2R preserves a path to higher assurance while keeping collection belonging distinct from constructive parthood and order and time outside structure.
• Use-specific assurance without tooling commitments. Teams choose the grounding that the relation's elected branch and receiving claim require. The declared modes distinguish justification postures; they are not an ascending scale of empirical confidence.
• Explicit fit management. Treating edge‑fit (CL) as a first‑class concern prevents silent over‑confidence: weak mappings visibly cap reliability of composed claims.
• Cleaner separation of concerns. Distinguishing collections from compositions and keeping sequence/time in Γ_method and Γ_time prevents recurrent category errors and preserves Γ‑algebra reviewability.

Trade‑offs & mitigations

• Extra prose discipline. Declaring validationMode and writing a short grounding narrative (when axiomatic) adds authoring effort. Mitigation: reuse local templates; keep narratives concise and Γ_m‑oriented by idea rather than notation.
• Insufficient grounding for the receiving use. An empirical or logical account can omit a premise or fail to satisfy the elected branch. Use B.3.3 to identify that gap and the worthwhile repair; retain sufficient support without demanding a more formal mode merely for its label.
• Perceived conservatism. Acknowledging weak fit (CL) may lower effective reliability of otherwise strong parts. Mitigation: treat CL as a guide to improvement (reconcile terms, align units, verify declared links) rather than a punishment.

One‑line takeaway for managers. CT2R lets you talk in natural, domain‑meaningful relations while preserving a clear, optional path to formal grounding and empirical checking—so confidence can grow deliberately without dragging your model into tooling or syntax.

#Rationale (informative)

14.1 Why canonical‑first? CT2R-LOG treats the human-readable, task-appropriate relation (e.g., ut:ComponentOf) as the canonical publication form because that is what engineers and managers actually use to reason, decide, and communicate. The formal layers ground that form; they do not replace it. This is consistent with the authoring Standard in Part E (pattern template and style guide), which privileges clarity, purpose and didactics over premature formalism in the body text. Authors write for people first, then point to the kind of assurance they are invoking.

14.2 Why two tv: links—and why concept‑only? tv:AliasOf and tv:groundedBy name conceptual bridges from a public Working-Model relation to its direct principle and assurance account. They mandate no notation. They keep authors explicit about the relation reading, the support being invoked, and when that support must be current, without letting an alias, trace, or mode define the world-side occurrence.

14.3 Why a triad of validationMode? The triad {postulate, inferential, axiomatic} distinguishes permitted justification postures, not stages of formality or increasing confidence. The direct relation kind and elected profile determine which posture and support are appropriate for the receiving claim and use. A sufficient calibration account in a branch permitting postulate needs no mode promotion; an elected structural-parthood or collection-belonging claim still requires its respective current construction trace. Where a load-bearing claim needs stronger proof or an empirical check, select that contribution for the assurance gap it can resolve, not to advance through the three labels. The mode declaration changes neither the canonical relation nor the strength of its support.

14.4 Why keep order/time out of mereology? CT2R‑LOG aligns with A.14’s firewall: structure (parthood) is distinct from order and temporal coverage. The former is published as ut:StructPartOf sub‑relations; the latter live in Γ_method / Γ_time and must not be smuggled into part‑trees. This separation avoids classic modelling failures (temporal smearing, pseudo‑components for quantities) and keeps reasoning crisp across the Γ‑family.

14.5 Why point to Γ_m.sum | set | slice (Compose‑CAL) for constructive grounding? The three C.13 forms—sum, set, slice—are sufficient to report the recurring construction accounts for integrated assemblies, collections, and aspects without expanding the kernel. They are not identity functions. A truthful account carries exact participants, direct relation occurrences, the applicable rule, and identity or reidentification conditions: the same inputs under another assembly can form another whole, while a permitted replacement can preserve one whole.

14.6 Why mental obligations rather than process mandates? Part E requires that patterns define or constrain thinking and authoring; enforcement and automation, if any, are external concerns. CT2R-LOG therefore states obligations as self-contained cognitive checks: for a claim within an elected profile, declare a permitted mode and supply the support required by that branch; use the respective current trace for structural parthood or collection belonging; keep order/time in their places. The requirements concern the claim's justification, not attainment of an axiomatic strength level. This keeps the core specification evergreen and tool-agnostic, as required.

#SoTA-Echoing

The assurance profile uses the three contributions below.

At comparable correctness and currentness, always exposing the heavier account costs more to write and read, while a bare direct sentence cannot meet an elected assurance need. B.3.5 therefore starts with one readable relation and adds one branch-specific account only when the publication elects the profile. The cost is that the relation assertion and its support must be checked for currentness separately.

Reopen only the affected source row and rule if A.14 changes the construction/belonging decision, a later ISO 15026-2 edition changes assurance-case structure or maintenance, or newer model-based-engineering evidence demonstrates a lower-effort way to retain direct meaning, declared posture, traceability, and independent currentness. A changed member, rule, trace, or evidence item instead reopens the affected assertion; it does not by itself reopen this architecture.

#Relations

Builds on

• A.14 Advanced Mereology — supplies direct structural relations and the discipline for collection belonging under each collection's own rule and separately grounded parthood; B.3.5 adds only the assurance branch elected for the relation.
• A.11 Ontological Parsimony (C‑5) — constructive grounding lives in a calculus; the kernel remains minimal.
• B.1 Universal Γ — shared invariants and the placement of order/time in their respective Γ‑flavours.
• Part E authoring rules — canonical pattern template and notational independence, which CT2R‑LOG explicitly follows.

Coordinates with

• Compose-CAL (Γ_m) and C.13 — supply current construction accounts for structural parthood and the set account for elected assurance of collection belonging. Each trace reports facts whose meanings and conditions come from the pattern that defines the relation.
• A.22.CGUS / StructuralCT2RTypingGroundingUnfoldingStructureBlock — provides the local structural CT2R unfolding block when a constructive trace, working-model relation, target kind or logical representation, bridge, preserved structure, and loss must be inspected together; A.7.1 is the pattern for general diagnostic return to a subject construction.
• KD‑CAL — provides the logical shoulder (inferential justification) when authors pick validationMode = inferential.
• Kind-CAL / Lang-CHR — provide the mapping shoulder (kind and relation-label alignment) governing alias policies without altering Working-Model relations.

Constrained by

• Notational Independence (E.5.2) — CT2R‑LOG refuses to prescribe formats, keeping all obligations conceptual.

Specialises / feeds

• B.3.1–B.3.4 — supplies the publication discipline (Working-Model relations, declared relation kind and validationMode; F per C.2.3 where relevant) that B.3’s trust calculus expects; interacts with ageing and assurance-level assessments without changing the relations themselves.

Non‑relations No introduction of order/time — CT2R‑LOG does not define SerialStepOf / ParallelFactorOf / temporal phases; use B.1.5 for Method-order claims, A.14 and B.1.4 for same-carrier temporal phases and their aggregation, and A.15.1 for Work parts and occurrences.

#B.3.5:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)