Cluster A.IV.A - Signature Stack & Boundary Discipline (A.6.)*
Preface node
heading:cluster-a-iv-a-signature-stack-boundary-discipline-a-6:14222
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
Signature Stack: Classify and Place Boundary Claims
Type: Architectural (A) Status: Stable Normativity: Mixed (normative only where explicitly marked; claim-classification semantics live normatively in A.6.B) Builds on: A.6.B for claim classification, A.6.0 and A.6.1 for declaration boundaries, A.7 for subject/description/carrier distinctions, and E.17.0/E.17 for view membership and publication.
Local terminology: “Signature Stack”, “Boundary Discipline Matrix”, and “Claim Register” name authoring aids. L/A/D/E classify statements; they are not MVPK face designators or pattern IDs.
Governing classification. A.6.B defines the Boundary Norm Square, its quadrant conditions and cross-quadrant dependencies. This overview maps those claims to declaration, consequence/evidence and publication positions.
Use this pattern when. Use A.6 when a boundary package, API, protocol, contract, compliance statement, SLO/SLA, connector, interface, or publication boundary mixes definitions, admissibility predicates, duties, evidence, and work effects into one account.
What this buys. The project gets an L/A/D/E-classified claim set with source references and stack placement. Material dependencies name the source claim by ID or canonical location, so work, reliance, evidence, commitment, and gate uses can return to their subject patterns; publication faces cite the same claims.
Use as much classification structure as the work or reliance claim needs. Split a statement when different claim kinds, governing bases, participants or consequences would otherwise remain ambiguous. Ordinary atomic prose can suffice. Keep existing stable claim references; use a Claim Register when it helps maintain the references needed for reuse, publication or reliance. Modifiers that leave one coherent claim need no separate entries.
Typical neighboring subject patterns and authority-reference repairs. A.6.B for the quadrant semantics, A.6.C for contract unpacking, A.6.P, C.16.Q, or A.6.A for lexical repair, and E.17 faces for audience-specific publication of the same decomposed claim set.
Common neighboring-pattern mistakes. For cue preservation or an early unresolved cue, use A.16 or A.16.1; if a qualified relation, quality term, or action invitation is itself being repaired, apply A.6.P, C.16.Q, or A.6.A; if duties, commitments, promise content, work effects, and evidence are being mixed into one contract sentence, split them through A.6.B and A.6.C rather than writing another undifferentiated contract paragraph.
Causal and authority claims. In “deploy because it would reduce harm”, C.28 determines what the causal evidence supports; A.6.B separately classifies the boundary claims. Select an A6-AW-* row for each permission-looking claim. Causal support alone leaves permission, duty and gate claims to their own bases.
Authority-word branch (subordinate boundary-claim stress case). When “approved”, “allowed”, “authorized”, “permitted”, or similar wording matters to action or reliance, choose one row by the claim being made—not by the visible word. These A6-AW-* labels are local claim-routing IDs, not new kinds.
Concrete API/credential case. The observation that a dashboard badge displays “API-7 approved for production” is an A6-AW-SOURCE claim. A separate claim that a current grant permits a beneficiary to deploy the API belongs under A6-AW-NORM-GRANT; establishing it requires a current grant instituted by a named policy-valid act for that beneficiary and deployment action. Classify the entry predicate or actual admission decision separately under A6-AW-GATE. Claim A6-AW-EXERCISE only when a dated deployment Work occurrence matches that grant.
When agreement-like wording leaves an ambiguity that changes interpretation or use, use A.6.C to separate promise content, the instituting speech act, governance, Work, consequence, and evidence. For “recommended”, use A.16/A.6.A for a cue, A6-AW-GATE for an entry criterion, or A.2.8 only for recommendation-as-duty. Before action or reliance, return to the governing claim. Use A.15.4 while appearance hides the required prerequisite; use A.15 when the question is enactment alignment.
Credential and register use. Recover issuer, holder, verifier, status and currentness where they change the claim. A displayed register entry may have institutional force under its governing rule; in that case identify the object created or changed under the corresponding A6-AW-* row. Use A.2.4 for a first evidence-use or status-use classification and A.10 when a replayable source-to-use account is needed, rather than treating every display as an evidence relation.
Conflicting-source boundary. When a classified boundary claim disagrees with its governing source or a display, resolve the source order, decision source, freshness policy and supersession rule. Until then, keep cue use or source-finding available. For a conflicting or missing source, allow a bounded reversible probe only on its own adequate basis and with a stated stopping condition, without relying on the unsupported claim.
Boundary and source repair assignment. If the split exposes a missing claim or source, give the claim ID or canonical location, or the selected A6-AW-* branch to the identified boundary or source maintainer. Keep cue use or source-finding available. A bounded reversible probe needs its own adequate basis; the missing source blocks the unsupported Work or reliance use.
Recurring ambiguity. When a misleading boundary statement repeatedly causes the same ambiguity, repair its source and affected displays. Recover the L/A/D/E claims and their references so each reader need not reconstruct the same missing distinction.
For an incident-learning use, record the displayed phrase, intended Work or reliance use, unsupported claim or effect, missing or ambiguous L/A/D/E claim ID or canonical location, required source, plausible overread, safe disposition and upstream repair. Retain source, currentness and supersession references only where they change that case.
Conventions: The key words MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, and SHALL are interpreted as in RFC 2119/8174 only when written in capitals.
Statement identifiers (recommended): Adopt the quadrant‑prefixed ID scheme from A.6.B:0 for classifiable statements:
L-* (law or definition), A-* (admissibility gate), D-* (deontic or commitment), E-* (effect or evidence).
Other sections and faces SHOULD cite the canonical claim ID or location. Face prose may explain or faithfully paraphrase the claim without creating another specification.
Stable IDs are useful when a duty or evidence claim refers to an entry predicate. Use the Claim Register in A.6.B:7 when it helps maintain those references across faces.
Non-collision note (informative): The A-* prefix here is “Admissibility”, not Part‑A numbering and not MVPK’s AssuranceLane face designator. If this is a readability hazard in your program, prefer an explicit G-* (“Gate”) local convention while keeping the quadrant name “Admissibility”.
Admissibility-predicate distinction (informative): An A-* claim is an admission predicate for a named action or application under its governing rule inside the L/A/D/E-classified boundary claim set. It is not an A.21 GateDecisionResult, GateCheckApplicationResult, optional GateCheckRef, optional DecisionLog, or proof that a gate passed. An A-* claim may name conditions consumed by a later A.21 profile application; actual passage is a separate E-* claim about the GateDecisionResult. An A.20 ConstraintValidity witness remains separate from the predicate, each check application, and the gate result.
Claim Register (informative, recommended). When a Claim Register is useful, use the mini-record in A.6.B:7. It can record stack placement (Signature, Admission, Norms, and Evidence) and the face designators that cite each claim. Add viewRef/viewpointRef only when the corresponding episteme identities matter. Mechanical checks can test ID resolution and exact text copying; inspect meaning for paraphrase drift.
Problem frame
At an API, protocol, hardware connector, organizational interface or published model, a reader needs to distinguish the declaration from the conditions of use and what occurred. FPF supplies these contributions:
U.Signatureas a public, law‑governed declaration (with Vocabulary, Laws, Applicability).U.Mechanismas a reusable operation declaration with OperationAlgebra, LawSet, AdmissibilityConditions and Applicability.- Multi-view describing through E.17.0
MultiViewDescribing, plus separate E.17 publication discipline for selected epistemes, face uses, forms, and carriers. - Recover each claim's EntityOfConcern separately from its claim-bearing Description episteme and any publication carrier. The concern may itself be an episteme or carrier; its position does not establish agency, Work, evidence, or a decision.
A boundary account can blend these claims into one contract paragraph. Then a signature can acquire an unstated entry gate, a mathematical invariant can be read as a duty, or an effect can be asserted without its basis.
Connect the contributions in two steps:
- Distinguish declaration layers from claims about occurrences and their consequences or evidence, and from publication uses.
- Classify each boundary claim through A.6.B and place it where its governing content can be maintained and reused.
Terminology note (informative): In this pattern:
- Layer names a position in the account: Signature, Admission, governance, consequence/evidence or Publication. Actual occurrences remain the subjects of claims rather than parts of their description.
- View (
U.View) is the same C.2.1 episteme individual when E.17.0 conformance to at least one exact viewpoint episteme obtains; it is not a projection operation, publication file, or document. - Viewpoint (
U.Viewpoint) is the same C.2.1 episteme individual when the fixed E.17.0 viewpoint-convention conditions obtain; its accountability use does not replace those membership conditions. - Face (MVPK sense) is a publication form for a bounded reader/use.
PlainView,TechCard,InteropCard, andAssuranceLaneare face designators, not additionalpublication-face kindvalues. A face may expose an episteme that independently hasU.Viewmembership; the form, rendering and carrier remain separate from that episteme.
Problem
The following confusions change the interpretation or use of a boundary claim:
-
Laws vs admissibility. Authors encode runtime gate predicates as “laws”, or write invariants using RFC‑style deontic verbs, blurring “what is true or defined” with “what is allowed to be applied”. FPF separates these: admission predicates use the canonical source of their governing rule, including A.6.1 for mechanism applications; they do not belong in
U.Signature.Laws. Common mistake #0 — Applicability ≠ Admissibility (informative): SignatureApplicabilityscopes declared admissible use and bounded context; it is not a runtime entry gate. A mechanism's runtime entry predicates belong inU.Mechanism.AdmissibilityConditionsasA-*. Such a predicate may consume the direct object selected by oneA6-AW-*row as input, but it neither creates that object nor proves gate passage. A generic prescription states what one policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence. A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8U.Commitment. Either branch can reference theA-*gate by ID or canonical location without becoming the gate. -
Admissibility vs deontics.
MUST,SHOULD,MAY, and authority-looking words do not reveal whether a statement is a duty, oneA6-AW-*permission branch, or an entry predicate. Classify the claim by its job; neither the word, selected subject pattern, nor kind of direct object decides the quadrant. -
Contract talk category errors. If “the interface promises…” leaves a consequential ambiguity about the claim or its participant, use A.6.C to recover it before treating the wording as an agency error. Use A.2.3 for promise content, A.2.9 for the instituting speech-act Work, A.2.8 and A.2.8.PER for the commitment or grant, and A.15.1 only to identify the dated Work occurrence. An application result, production, delivery/transfer, acceptance, and evidence use each follows its own row in
A.15.1:4.6and is omitted when that claim is absent. F.18 only names recovered terms when durable naming is current. -
Effect claims without an actual occurrence. A description, diagram, log or metric can state or support an effect claim. Establish the actual occurrence under its subject pattern. Use the Work conditions in 4.1 when a dated Work is claimed; natural, spontaneous or formal change can use A.3.4 without a Work claim. Name any observation used as evidence and obtain the support needed by the receiving use through A.6.B:5.4.
These confusions can defeat substitution behind a stable signature: an implementation change may unexpectedly alter a hidden gate, duty or evidence requirement. Make each applicable constraint recoverable under its own claim.
Forces
Solution — A stack + a classification matrix
Why “stack”: what is stacked, and what “higher and lower” means
The Signature Stack orders reusable boundary declarations and the more use-specific claims that depend on them. Its purpose is to allow a realization or evidence arrangement to change while preserving the declarations and constraints that its use still requires. “Higher” and “lower” name this relation:
- Higher in the stack = closer to public, reusable boundary intent.
- Lower in the stack = closer to execution, implementation, and evidence (what is done and observed).
The first four positions below classify boundary claims; the final two distinguish their actual subjects and publication uses:
-
Signature layer (L: laws or definitions).
U.Signatureprovides the stable declarative boundary: Vocabulary + Laws + Applicability, without runtime gate predicates. -
Admission layer (A: entry and application conditions). State when a named action or application is admitted under its governing rule. Mechanism applications use
U.Mechanism.AdmissibilityConditions; A.21 gates use the applicable profile rule.U.MechanismspecializesU.Signaturethrough the operation declarations, LawSet, AdmissibilityConditions and Applicability governed by A.6.1. Its admission predicates remain declaration content. Evidence-interface declarations and transport details keep their own claim classification; use A.10 when a replayable source-to-use account is needed, and name carrier-producing Work only when that occurrence is claimed.Audit and AssuranceLane: a boundary's local Audit and observability section states its evidence-interface declarations: carrier classes and required fields, correlation keys, and exposure interface.
Mechanism.AuditObservabilitybelow is a local publication-section locator, not an A.6.1 content component.Prescriptions or claims about individual duties concerning retention, access or enforcement are D-claims. A general prescription remains a claim-bearing episteme; a claim about one obtaining individual duty cites the exact A.2.8
U.Commitment, its actual bearer, and its direct predicate. A system-role kind or assignment may be an applicability ground but is neither bearer nor commitment.An MVPK AssuranceLane is a publication face for auditors that explains how to adjudicate the evidence interface. Under CC-A.6.6, the
AssuranceLaneface references those evidence-interface declarations and relevant claim IDs or canonical locations; its explanation preserves their semantics. -
Deontic layer (D: duties, commitments, and grants). Put here a general prescription or a claim about an exact individual duty, recommendation-as-duty, prohibition, commitment, or
A6-AW-NORM-GRANT. For an individual duty, cite the exact A.2.8U.Commitment, actual bearer, constitutive rule, required instituting basis, and direct predicate. Test any responsibility claim separately through its domain predicate or return the missing governor. OtherA6-AW-*claims keep their own placement. Reference relatedL-*,A-*, orE-*claims by ID or canonical location rather than duplicating their constraints. -
Observable-effects and evidence layer (E: Work-Effects & Evidence). Each E claim names the actual occurrence or evaluated finding under its subject pattern and the observation/evidence basis needed by its receiving use. The subject may be Work under the conditions below, or a natural, spontaneous or formal change. When the publication uses separate sections, place the claim in Evidence-and-carriers; it may also be presented in an
AssuranceLane. -
Actual occurrences and realizations (outside the description stack). Substitutable realizations are exercised through dated Work only when each actual performer has its A.13 core and A.15.1 independently admits the occurrence. Add F.6 only when the receiving description also consumes precise assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 alone does not overturn independently admitted Work. If the attribution finding questions a premise consumed by Work admission, recheck that premise and the dependent claims.
Work may participate in change, production, speech-act effect, evaluation, or evidence production, but each relation or claim must be established under the pattern that defines or constrains it. A.3 and A.3.4 also admit natural, spontaneous, and formal transformations without a performer, assignment, Method, or Work occurrence.
-
Publication faces. MVPK selects exact epistemes and publication forms for audience-specific face uses. A selected episteme has
U.Viewmembership only when E.17.0 conformance to the exact viewpoint episteme obtains; any A.6.3 source-to-receiving construction remains separate. The face designator, publication occurrence, form, rendering, and carrier are not theU.View.
When specifying evidence carriers and correlation rules, traces/spans, logs/log records and metric time series provide examples of carrier schemas and join keys. Choose the forms needed by the evidence claim.
AssuranceLane skeleton (informative)
An MVPK AssuranceLane is a publication face that teaches a specific audience how to adjudicate E-* claims against the relevant evidence carriers, including those produced in Work. It cites the boundary's evidence-interface declarations and explains them without changing their semantics.
Minimal content (suggested):
- Scope: boundaryRef, version; viewRef and viewpointRef when view or viewpoint identity matters.
- Carrier inventory: carrier-class and carrier-schema refs (A.7 Carrier) + where to obtain them.
- E‑claim map: a table keyed by
E-*ID with: measurement conditions, carrierRef(s), join and correlation keys, and a reference to the canonicalE-*text that defines pass or fail criteria. - Operational policies: references to relevant
D-*duties (retention, access control, exposure), without redefining them. - Limitations: sampling, redaction, missing signals, expected false negatives and false positives.
An AssuranceLane explains adjudication. Add a new boundary claim to its governing source before using it in that face; a permission-looking claim needs its selected A6-AW-* object and basis.
Example (conceptual; uses view/viewpoint identity and the additional hypothetical header case in §4.2):
The absence condition also covers a request that was not rejected. A claim of complete coverage requires the relevant request population to be accounted for separately from individual query joins.
Default placements (quadrant → stack layer / section):
- L → Signature.Laws (and, where appropriate, mechanism‑local semantic laws; never runtime gates)
- A → the canonical source of the governing admission rule; use
Mechanism.AdmissibilityConditionsfor mechanism applications and the applicable profile rule for A.21 gates - D → generic prescriptions, individual duties or commitments, recommendations-as-duty, prohibitions, and
A6-AW-NORM-GRANTclaims at their A.2.8 or A.2.8.PER subject pattern - E → actual occurrences, evaluated findings, and evidence claims, including
A6-AW-EXERCISE,A6-AW-WEAK,A6-AW-CONFLICT, andA6-AW-SOURCEwhen those claims are current
Related subject rules (informative):
- A.6.1 ↔ A‑quadrant:
U.Mechanism.AdmissibilityConditionsis the canonical source forA-*admission predicates of mechanism applications. - A.10 / B.3 ↔ E‑quadrant: when an
E-*claim needs a replayable source-to-use account, recover its A.10 evidence-provenance path and bounded use. A missing required path narrows or blocks only the unsupported use. Open B.3 only for a named assurance claim about an exact target and assurance use. - A.2.3 and F.12 ↔ D/E separation: a
U.PromiseContentstates the promised outcome and acceptance criteria; F.12 evaluates fulfilment using Work evidence. A general duty remains normative content, while an obtaining individual duty is one A.2.8U.Commitmentborne by an actual System or other admitted party. Any system-role kind or assignment used to establish applicability stays separate.D-*claims referenceA-*andE-*claims by ID or canonical location when needed.
This placement supports change through the dependencies:
- A realization, audit format or transport mechanism can change while the boundary declarations remain valid, provided their applicable constraints are still satisfied.
- A changed declaration requires reconsidering the uses that depend on it and communicating any consequential compatibility or version change.
Boundary Discipline Matrix: classify by A.6.B (the Boundary Norm Square)
A.6.B defines the matrix and cross-quadrant reference rules. Use the following summary to classify a claim and the examples to distinguish a source clause from added case assumptions.
The matrix distinguishes four jobs in a boundary account: defining meaning, declaring admission conditions, stating normative content or a deontic position, and reporting occurrences or evidence. Classify the claim by that job, then recover the conditions that settle it under A.6.B.
A declared admission predicate and its evaluation have separate jobs: the predicate is A; a particular evaluation result is E. D includes both generic normative content and a claim about an individually obtaining duty or grant, with different grounds for each. These distinctions let the same subject appear in several connected claims. The selected A6-AW-* row supplies the corresponding permission-word distinction. Actual evaluation or observation does not require inventing Work for a non-Work change.
Operational summary (quadrant → canonical claim layer in the stack):
- L (Laws & Definitions) →
Signature.Laws(truth‑conditional semantics, in‑description) - A (Admissibility & Gates) → the canonical source of the governing admission rule:
Mechanism.AdmissibilityConditionsfor mechanism applications; the applicable profile rule for A.21 gates. A predicate may consume an exact grant or finding selected byA.6.B:8.4.1, but it neither creates nor resolves that object. - D (Deontics) → generic-prescription or individual-duty A.2.8 claims and
A6-AW-NORM-GRANT - E (Work-Effects & Evidence) → actual-occurrence, evaluated-finding, and evidence claims, including the applicable E-side
A6-AW-*row
Atomicity rule:
If a sentence mixes logical jobs, for example “MUST” plus a gate predicate plus an effect claim, it is not classifiable as a single statement. Per A.6.B, split it into atomic claims so each one has exactly one quadrant and, ideally, an identifier you can reference.
Micro‑template: Atomize → Classify → Place → Identify EntityOfConcern → Register when useful
- Split when needed: separate claims that perform different logical jobs.
- Assign each claim to exactly one quadrant (L/A/D/E) using the matrix.
- Place each claim in its canonical claim layer; use a separate section or publication form when the receiving use needs it.
- Anchor A.7: name what each claim is about, separately from the episteme carrying it. Add publication and carrier relations when they change interpretation. For permission-looking wording, bind the direct object and participants required by the selected
A6-AW-*row; the selected subject pattern or kind of direct object never supplies the quadrant. - Register when useful: add the atomic claim to the Claim Register if used. Downstream faces cite the claim by ID or canonical location and preserve its meaning in any explanation.
If a Work or reliance claim lacks its required source, narrow it to what the available source supports or hold the dependent use. A local or reversible use may proceed on its own adequate grounds once its stopping condition is stated.
Informative example: mixed → atomic.
Before (mixed, not classifiable yet): “Clients MUST include header X; otherwise the request is invalid and the system logs NotAdmissible.”
Recovered source clauses:
- “Clients MUST include header
X.” - “If a request lacks header
X, the request is invalid.” - “If a request lacks header
X, the system logsNotAdmissible.”
Recover the intended invalidity/admissibility meaning before fully classifying the second clause. The third clause states a generic logging rule; it reports no particular observed request.
Additional hypothetical illustration. Suppose a separate boundary policy defines invalidity here as failure of the entry condition below and adds an implementer duty to the quoted Clients duty. Also suppose the observation stated in E-OBS-1 occurred in this hypothetical case:
A-AC-1(Quadrant A, Mechanism.AdmissibilityConditions):hasHeader(req, "X")is a necessary entry condition.D-CL-1(Quadrant D, Norms-and-commitments): “Client implementers MUST include headerXin each request to this boundary (A-AC-1).”E-OBS-1(Quadrant E, Evidence-and-carriers): “For the selected requestreqlacking headerX(A-AC-1), the system loggedNotAdmissible; the observer recovered itsAuditLogEntry{code="NotAdmissible"}in the audit stream.” The carrier schema is an additional illustrative choice. Logging depends on the absence ofX, including when the request was not rejected.
Informative example: guarantee, SLA, measurement and enforcement.
Before (mixed contract prose): “The service guarantees 99.9% availability per calendar month and MUST keep p95 latency under 200ms; breaches are penalized; operators SHALL alert on violations.”
Recovered source clauses:
- “The service guarantees 99.9% availability per calendar month.”
- “The service MUST keep p95 latency under 200ms.”
- “Breaches are penalized.”
- “Operators SHALL alert on violations.”
Recover the guarantee's meaning and bearer, the measurement and acceptance basis, and the breach trigger, penalty and applicable parties. Use A.6.C for the unresolved contract meanings and A.6.B to classify the resulting atoms. The split alone does not settle them.
Additional hypothetical illustration. Suppose a separate policy identifies Provider and the service being measured, states the exclusions and workload
W, defines the availability and latency metrics, and sets the two criteria evaluated below. In addition to the quoted alert duty, it requires paging within 5 minutes. The following E-claims assume that the stated evaluations and observation occurred in this hypothetical case; the alert observation concerns a separate violation case.
D-SLA-1(Quadrant D, Commitments and SLA): “Provider SHALL meet the availability and latency criteria evaluated byE-SLA-AVAIL-1andE-SLA-LAT-1under the stated exclusions.”E-SLA-AVAIL-1(Quadrant E, Evidence-and-carriers): “The evaluation of the observed calendar monthTreportedavailability ≥ 0.999, with measurements recorded in carrierUptimeProbeSeriesfrom viewpointVP.ExternalMonitor.”E-SLA-LAT-1(Quadrant E, Evidence-and-carriers): “The evaluation under workloadWreportedlatency_p95 < 200ms, with measurements recorded in carrierLatencyMetricSeriesfrom viewpointVP.Client.”D-OPS-ALERT-1(Quadrant D, Ops duty): “Operators MUST page on breach of the criteria evaluated byE-SLA-AVAIL-1orE-SLA-LAT-1within 5 minutes (additional policy).”E-ALERT-1(Quadrant E, Evidence-and-carriers): “In the separate violation case, the operator's page was observed in carrierAlertEvent{ruleId,firedAt,target}and can be joined viaincidentId.”These added policy and observation premises do not resolve the original guarantee, duty bearer or penalty clause.
See A.6.B:4–A.6.B:6 for the normative square, quadrant form constraints, and explicit cross‑quadrant link patterns (notably: D→A, E→A, D→E, and A/E→L).
Authority-wording split examples
These examples are informative. They separate authority wording from the evidence, assurance, commitment, gate-passage, or Work claim being made.
Before (mixed): "This API is approved for production use and guarantees safe rollback."
Recovered source clauses:
- “This API is approved for production use.”
- “This API guarantees safe rollback.”
Recover the approval's direct object and ground under the applicable A6-AW-* row, and the rollback subject and safety predicate. Both source claims remain unresolved until that meaning is supplied.
Additional hypothetical illustration. Assume supplied signature vocabulary defines the API operation and rollback terms; a separate boundary policy gives the request-admission predicate, policy window and exclusions. For E-API-1, additionally assume that a named evaluation of an independently identified rollback occurrence reported success under a stated success criterion and observation basis:
L-API-1(Quadrant L): the API operation and rollback terms are defined in the supplied signature vocabulary.A-API-1(Quadrant A): a request is admissible only under the named subject, action, object, context, and policy-version predicate.D-API-1(Quadrant D): the provider policy prescribes maintaining or enforcingA-API-1under the named window and exclusions. If the claim is instead that one actual provider or operator bears this duty, cite its separately instituted A.2.8 commitment.E-API-1(Quadrant E): the named evaluation reported rollback success under its stated success criterion. Possible evidence inputs include the named work traces, audit records, or metrics. A gate decision carrier may support the gate-passage claim; rollback execution needs its own occurrence and evidence basis.
In this additional case, A-API-1 applies A6-AW-GATE. The observation of the approval badge is an A6-AW-SOURCE claim; any further approval claim needs separate classification and grounds. The original production approval and safe-rollback guarantee remain unresolved. A success result alone does not establish the unspecified safety claim.
For a filled grant/exercise/evidence case and its near-misses, use A.6.B:8.4.5.4. It applies A6-AW-NORM-GRANT, A6-AW-EXERCISE, and the separate A.10 evidence claim by value.
Then:
- if appearance hides the prerequisite for action or reliance, enter
A.15.4; useA.15for enactment alignment; - if evidence, currentness, or provenance is live, attach the
A.10evidence relation; - if a named assurance claim is current, use
B.3for its exact target claim, argument, bounded assurance use andAssuranceResult; otherwise keep trust, readiness, compliance or release questions with their direct patterns; - if an actual gate decision or passage is asserted, classify it as a separate E claim and cite the exact A.21
GateDecisionResult, bounded action, applicableGateProfileapplication, complete requiredGateCheckApplicationResultset,decisionValue, action consequence, scope/window, and recheck condition; use a shortGateCheckRefonly for a selected publication structure and aDecisionLogonly when audit or reuse is current; - if a flow witness or constraint witness is asserted, cite
A.20ConstraintValiditystatus or witness; - if a permission-looking claim is asserted, use the selected
A6-AW-*row and its subject pattern; an entry predicate orGateDecisionResultdoes not substitute for another row; - if release, deployment, rollback, or execution Work is asserted, cite the exact A.15.1 dated occurrence; then use only the applicable
A.15.1:4.6row for an application result, A.15.PROD production branch, delivery/transfer relation, evaluation/acceptance relation, or A.10 evidence path. None is an intrinsic Work field; - if the phrase is only an action invitation or cue, keep it in
A.6.A,A.16, orA.16.1according to the current kind.
Policy engines, credentials, registers, provenance, and attestations can supply policy decisions, source claims, currentness, or evidence. Classify the observation of a visible permit, badge or registry value under A6-AW-SOURCE. Classify any further claim by what it asserts and check the required grounds for its named direct object and participants.
View membership needs exact viewpoint conformance
MultiViewDescribing makes the candidate episteme and exact viewpoint episteme explicit. The candidate has U.View membership only when E.17.0 conformance obtains. A projection or query may participate in an A.6.3 construction, but that construction does not establish membership. MVPK separately uses publication face designators (PlainView, TechCard, InteropCard, AssuranceLane) and their E.17 profiles. E.17:5.2 specifies the declared publication-face kind values.
The stack therefore requires:
- Every published face use identifies the selected episteme and its separate reader/use declaration. Name the exact viewpoint episteme through
U.ViewpointRefwhenU.Viewmembership or viewpoint identity is used; name the publication occurrence, form, and carrier when those identities change publication or reliance. The face designator is not any of those objects. - Calling the selected episteme a
U.Viewrequires E.17.0 conformance; a face label, viewpoint reference, projection history, or publication does not establish it. - Per E.17 (“no new semantics”), a face MUST NOT introduce a new semantic commitment or any new object or claim selected through
A6-AW-*. A face MAY add informative explanation, examples, and cross-references that preserve the source claims. Normative face prose cites the canonical L/A/D/E claim ID or location and direct object; it may faithfully paraphrase the claim. Add any new boundary claim to its canonical source before publishing it on a face. Use verbatim text when exactness is critical or disputed. - Per E.17 and publication-face and publication-form discipline (face‑kind closure), a publication package that claims MVPK alignment MUST NOT introduce additional MVPK face kinds (e.g., “EvidenceCard”, “NormsCard”) as if they were first‑class kinds; if you need local headings, keep them as sections within the selected faces.
Recover the separate claims in contract wording
When “the API contract” leaves a consequential ambiguity, use A.6.C to ask only the live questions: what was promised, what was said or instituted, what governance position obtains, and what happened. Use A.15.1:4.6 to separate any dated Work from the result, production, delivery/transfer, evidence, or acceptance claims made. Clear wording, including a semantic guarantee or recoverable ordinary metonymy, needs no unpacking record.
- Promise content (promise content;
U.PromiseContent, A.2.3): what is promised to be made available to eligible consumers — a promise, not execution (U.Work). - Utterance and publication: identify what is stated and published in the boundary descriptions or faces. Identify any actual speech-act Work under A.2.9 when that occurrence or its instituting effect is claimed; publication alone does not establish such an act.
- Commitment (individual deontic relation;
U.Commitment, A.2.8): whether one actual admitted System or other party is obligated, recommended-as-duty, or prohibited from doing something under an exact constitutive rule and required instituting basis. A system-role kind or assignment may help satisfy that rule's applicability conditions; neither is the duty bearer or the commitment relation. A commitment does not establish responsibility, which needs its own direct domain predicate or a missing-governor result. - Permission-looking claim: do not make
Permissiona bundle part or quadrant. Select oneA6-AW-*row for each atomic claim and cite its direct object. - Performed Work (
A.15.1): identify the dated occurrence, performer, Method, time and containing System using the conditions in 4.1. Precise assignment-bound attribution is the separate F.6 claim when needed; its absence or failure does not revoke the Work. - Result or consequence (
A.15.1:4.6dispatch): only when current, name the exact A.6.1 application/result binding or subject-specificWorkResultRelation, A.15.PROD production branch, A.3.4 change, evaluation result, delivery/transfer relation, or acceptance relation. - Evidence (
A.10): only when a receiving use relies on one of those claims, name the claim-bound evidence path and carrier.
In A.6 terms:
- The signature supplies the boundary's declared vocabulary, laws and applicability; it is not itself a promiser or obligor (A.7).
- Deontic claims use A.2.8 for generic prescriptions or separately obtaining individual duties and commitments, and
A6-AW-NORM-GRANTfor the current norm/grant branch. Other permission-looking claims keep the placement and object named by their selected row. - Classify each atomic operational “guarantee” claim as L (truth-conditional law), A (entry predicate), D (generic prescription, individual commitment, or current grant), or E (actual exercise, evaluated result, work effect, or measured property with evidence).
Optional-object example. SVC-DEPLOY-1 states promise content. Admitted system ReleaseManager-4 performs SA-4711 : U.SpeechAct under ReleaseManager-4@ReleaseShift; the exact policy may institute COM-4711 : U.Commitment or PER-4711 : GrantedPermissionRelation@Context. Later admitted system Operator-7 performs DeployRun-4711 : U.Work under its covering assignment.
If the application returns ReleaseArtifact-4711, cite the exact A.6.1 result binding or an already governed WorkResultRelation; if that artifact is delivered, cite a separately obtaining transfer relation defined by its subject pattern; if acceptance is claimed, cite the criterion, evaluation result, and acceptance relation; identify dated evaluation Work only when the claim depends on that occurrence.
An A.10 path may support whichever one of those claims is relied on. Omit every absent object: the Work can occur without a result, delivery, acceptance, or evidence-use claim.
Use A.6.C — Contract Unpacking for Boundaries for the expanded account and the same A.15.1:4.6 dispatch.
Where statements go (classification examples)
Informative. Classification examples for learning the discipline; they do not add requirements beyond A.6:7.
The table below uses near‑everyday spec phrases. The same visible words appear in different quadrants depending on what they do.
The A.7 primary layer field below identifies the claim's EntityOfConcern, with its kind when needed; it is not a layer selected from the quadrant. The concern may itself be a Description episteme or publication carrier and remains separate from the episteme carrying the claim.
Notes:
- The classification is not just about modal verbs. “Shall” can be D (a duty) or A (a gate behavior). “Guarantees” can be D (a commitment) or E (a measured property). The matrix forces disambiguation.
- If a sentence combines a duty with an entry condition, split it into (A) a gate predicate (
A-*) and (D) either a general prescription or a claim about one exactU.Commitmentborne by an actual System or other admitted party (D-*referencing the gate by ID or canonical location). When observability matters, add an E claim only on a separate actual observation or result basis. A requirement to produce or retain logs is D; an expectation or plan supplies no actual E result. A system-role kind or assignment may establish applicability only through an independently obtaining rule; neither bears the duty. - When something needs to be enforceable but is mathematical, prefer predicate blocks rather than deontic language in the L/A blocks, per E.8’s deontics vs admissibility guidance.
Classification sanity rules (informative, concept-level)
These are writing diagnostics, not tool requirements.
- An RFC keyword is used as an obligation operator inside a Definition, invariant or admissibility predicate → separate the D obligation from the L/A claim; write the definition or entry condition as a predicate.
E-*with no exact actual occurrence or evaluated predicate, or with a carrier but no evidence relation for the claimed use → incomplete effect/evidence claim. Ground Work through A.15.1 only when it obtains; otherwise use A.3/A.3.4 or the exact interaction or causal-use pattern. A carrier supports the claim but does not create the effect.D-*that re-states anA-*/L-*predicate instead of citing its ID or canonical location → drift risk (prefer “MUST satisfyA-…”).- A face introduces new L/A/D/E content not present in the canonical claim set → view-fork. Recover the direct object and classify the new claim—duty/commitment/grant in D; exercise/evaluated finding/evidence in E; gate in A—then add it to its canonical source before face publication. Informative commentary may explain existing claims without adding boundary semantics.
- “The system or service SHALL …” where the phrase does not name a direct behavior claim, general prescription, or exact individual commitment with its actual bearer and constitutive basis → unresolved subject and modality. Recover the System or other party, state an actual
E-*behavior claim separately only when its basis is supplied, and state either the normative content or the direct A.2.8 commitment. A service label, system-role kind, or assignment proves none of these claims.
Use the claim dependencies to judge a boundary change
Start with the receiving use: which clients, operations and observations must continue to work, under which conditions? Read the existing boundary claims and the proposed change against that use. The stack makes the different constraints findable; compatibility depends on their content and connections.
- Recover what the receiver relies on. Include the meaning of inputs and results, admitted inputs, relevant interaction order and state changes. Add a duty, grant or evidence requirement when this use depends on it. Preserve the conditions and exceptions attached to each claim.
- Identify what changes. Distinguish changing a definition, an admission condition, normative content, an implementation or an observation method. A change can affect several of these. Use the claim references to follow the consequences to the receiving use, including an A predicate that consumes a current D grant or E finding under A.6.B:6.4.
- Compare the old and proposed behavior in that use. For a replacement offered to existing clients, determine whether previously admitted inputs remain admitted and whether the results, interactions and state changes still satisfy the old claims. When representations differ, state the correspondence used for this comparison. A stronger entry condition can exclude an old valid call; a weaker result condition can remove a property its client needs. Preserving a protocol or mutable state also requires its own sequence or history conditions.
- Establish the affected claims on their own grounds. A declaration comparison can establish a conditional compatibility argument. Claims about an actual implementation, obtained grant, observed result or retained evidence need their corresponding grounds. A changed telemetry format can leave the operation semantics intact while breaking the auditor's ability to check a result.
- Choose and communicate the continuation. Preserve the old boundary, adapt the receiver or supply an adapter with a justified correspondence, or expose a changed contract and its affected uses. Reuse unaffected claims and evidence while their conditions hold. Keep an unresolved compatibility premise explicit.
Use the smallest description that carries these dependencies. For one operation whose meaning and use are already clear, its existing preconditions, postconditions and invariants can supply the comparison. A protocol specification can carry the interaction constraints; a policy and its evaluation interface can carry an authorization decision. Add the L/A/D/E organization where connected semantic, admission, governance and evidence claims otherwise obscure what a change affects. The labels organize those claims; the relevant contract, protocol, policy or subject Method supplies the preservation test.
Archetypal Grounding
Informative. Worked examples for learning the L/A/D/E claim-classification discipline; they do not add requirements beyond A.6:7.
Apply the same classification to different boundary subjects
The two cases below distinguish declaration, admissibility, governance and actual effect or evidence claims. Classification determines where a claim belongs; its subject pattern determines whether the claimed object or relation obtains. Keep that object distinct from the episteme stating the claim and its publication carrier.
Payment-processing System and its API boundary
System: the payment-processing System supplying the “Payment Authorize” service.
-
Signature layer (A.6.0).
- Vocabulary:
PaymentRequest,AuthDecision,MerchantId,Money, etc. - Laws: e.g., “If decision is APPROVED then reservedAmount = requestedAmount” (truth‑conditional).
- Applicability: bounded context “Payments Authorization”.
- Vocabulary:
-
Mechanism layer (A.6.1).
- Admissibility gate: request is admissible iff
tokenValid ∧ merchantActive ∧ amountWithinLimit. - Boundary transport details: HTTP headers and idempotency-key carriage. Declare canonical currency-conversion operations under A.6.1.
- The local Audit and observability section specifies required evidence carriers (e.g.,
AuthorizationRecordevent, log entry) and their fields, correlation IDs and retention class. Retention prescriptions and claims about individual retention duties remain in D.
- Admissibility gate: request is admissible iff
-
Actual occurrence and work layer.
- The payment-handling occurrence is
U.Workonly when its actual performer first has the A.13 core and A.15.1 independently admits the occurrence from its Method, time, containing System, and other required direct facts. If this payment account also asks under which assignment the performer acted, add F.6 through the same obtaining A.13 assignment; missing or failed attribution leaves the payment Work intact. - The ledger reservation change, event emission, timer transition, or retry effect is a separate actual-occurrence claim under A.3/A.3.4 or its interaction or causal-use pattern. Check each effect separately: knowing that the payment Work occurred does not show that the ledger changed, an event was emitted, or a retry happened.
- Traces, logs, and metrics enter an A.10 evidence path for the effect being relied on; carrier presence creates neither Work nor change.
- The payment-handling occurrence is
-
Publication faces (MVPK).
- PlainView: narrative for stakeholders (what the service promise is, in plain terms).
- TechCard: signature or mechanism details (types, error codes, version policy, admissibility predicate refs).
- InteropCard: machine‑exchange oriented boundary details (canonical field names, schema refs, transport bindings).
- AssuranceLane: evidence bindings (which carriers exist, how to adjudicate
E-*claims, retention and access duties by reference).
Effects-and-handlers analogy. In this software example, the signature exposes the operation interface. A.6.1 governs declared operation semantics and the separate realization relation; the realizing entity supplies the concrete handler implementation. An effect interface can have handlers with different behavior. For a substitutable realization here, compare that behavior with the declared operation meanings and applicable constraints.
Classification example:
- “A request is admissible iff
tokenValid ∧ merchantActive ∧ amountWithinLimit” belongs in Quadrant A (the declared admissibility gate). - “Clients MUST include Idempotency-Key” is a D prescription. If an admission rule also requires that header, reference that rule’s predicate; the three-condition predicate above does not include it. An obtaining individual
U.Commitmentadditionally needs the actual bearer, constitutive rule, instituting basis and direct predicate under A.2.8. - “System emits AuthorizationRecord” is ambiguous between a generic emission rule and an actual event report. Only the actual-event reading belongs in E, with its occurrence basis supplied; the wording alone does not choose that reading.
Changing this API. Suppose the proposed replacement keeps the fields and the three-condition admission predicate above, but changes APPROVED to mean only that a request was queued. Apply §4.7 to an existing client that relies on the stated reservation law. That law is no longer met at the response, so preserving the message type is insufficient for this replacement. Keeping APPROVED for an actual reservation preserves this claim; introducing PENDING requires an explicit protocol and changed client handling. Other compatibility conditions remain to be checked.
Alternatively, suppose the replacement adds hasHeader(Idempotency-Key) to the admission predicate. The existing D prescription already requires that header, but the old A predicate admits requests without it. For clients promised the old admitted-input set, the added condition is a restriction. For a use explicitly limited to requests that already carry the header, this restriction excludes no additional input. The compatibility conclusion therefore names the receiving population. Changing only the AuthorizationRecord schema instead returns to its consumers and evidence links; it need not change either the reservation law or admission rule.
Published evaluation protocol
Episteme: A published “Model Evaluation Protocol” for a safety‑critical classifier.
-
Signature layer: names operations such as
Evaluate(model, dataset) → Reportand states metric definitions (AUROC, calibration error) as Laws. A.6.1 governs the corresponding operation declaration and its argument/result meanings. -
Mechanism layer: the entry predicate requires the declared dataset/license condition, measurement-environment constraints and pinned seeds. Classify a separate institutional permission claim under its own
A6-AW-*branch when one is made. -
Deontics and commitments: the protocol may prescribe that reviewers use dataset vX.Y and that authors publish MVPK faces and cite the measurement environment. If an organisation has an individual review-SLA duty, identify that actual admitted System or other A.2.8 party as bearer and establish the direct
U.Commitmentpredicate. Any system-role classification or assignment remains a separate possible applicability ground. -
Effects and evidence: the dated evaluation run is a Work occurrence only when A.15.1 grounds it; its result episteme, any model or dataset change, and the report publication remain separate. Report files, logs, hashes, and trace IDs support the selected claims through A.10 but create none of those occurrences or results.
Non-Work E contrast. A seedling's spontaneous first-leaf unfolding can be an actual A.3.4 transformation with no performer, assignment, method, or Work occurrence. Measurements may support that change claim through A.10; neither the observation work nor its carrier becomes the change.
-
Multi‑view (MVPK face designators):
- PlainView for decision makers: what this protocol means for assurance.
- TechCard for engineers: metric definitions named by value, admissibility predicates, and a clearly marked Norms-and-commitments section (D‑claims) for governance.
- InteropCard for exchange-oriented consumers: conceptual field names, anchors, and schema references.
- AssuranceLane for auditors: evidence map (which carriers support which occurrence claims) and adjudication steps keyed by
E-*IDs.
This protocol description connects metric definitions with conditions for an evaluation and interpretation of its report. The signature stack keeps those claims available to their different uses.
Bias-Annotation
- Explicit classification can make a small repair needlessly elaborate. Use a register or additional publication face only when the receiving work needs it.
- Software examples can suggest that all effects are Work. The seedling case keeps non-Work change available, while each actual Work claim retains its own admission conditions.
- An audit-oriented description can emphasize carriers over what happened. Establish the occurrence or finding and then the evidence relation needed for reliance.
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Rationale
A boundary account can contain different claims, including:
- definitions and laws about operations or other mathematical objects;
- admissibility conditions for the selected operation;
- prescriptions, commitments or grants under their governing rules; and
- actual occurrences and evidence (effects may arise through Work, natural or spontaneous transformation, formal change, or another directly governed interaction, and evidence supports but does not create them).
Mixing these claims makes it harder to distinguish a semantic boundary change from an implementation change, and to test each claim against its own rule and evidence.
Reusable declarations constrain their realizations, while observations and evaluated results can expose a reason to revise those declarations. Keep the dependence and the reason for revision distinct. The classification follows what each claim says rather than its visible word, such as “must”, “guarantee”, “valid” or “allowed”.
SoTA-Echoing
Informative. The sources below supply distinct techniques for declaration, substitution, interaction and observation. The L/A/D/E organization is FPF's authoring choice for keeping their boundary claims and dependencies recoverable. Historical foundations retain their stated scope; current documentation is identified where used.
-
Algebraic effects and handlers / effect systems. Leijen (2017) and Hillerström and Lindley (2018) distinguish declared operations, effect typing and handler semantics. A common interface permits different handlers, so behavior preservation needs the operation's semantic contract. OCaml 5.4, §12.24 also distinguishes runtime protocol enforcement from static effect safety. A.6 uses the declaration/realization distinction; provider duties and SLA claims require their separate FPF grounds.
-
Contracts and behavioral substitution. Meyer, Applying “Design by Contract” (1992), pp. 40–42 and 46–49, develops preconditions, postconditions, invariants and optional runtime monitoring. Liskov and Wing, A Behavioral Notion of Subtyping (1994), §§1–2 and 5.2, adds preservation of invariant and history properties under a stated abstraction. These historical foundations supply concrete preservation questions for §4.7. Their formal conclusions apply under their computational assumptions; an API replacement also needs its interaction and receiving-use conditions.
-
Session types for protocol boundaries. Scalas and Yoshida (2019) connects global protocols, participant types and process properties under explicit conditions. Hou, Yoshida and Kuhn (2026) revisits the association and liveness reasoning. This helps compare changed message order, choice and retry behavior. Safety, deadlock-freedom and liveness have different conditions; a protocol theorem supplies only its stated property. A.6 separately locates admission, duties and actual-result claims.
-
Categorical optics, lenses, and bidirectional transformations. Lenses supply useful construction expressions with coherence laws. FPF uses that lesson only for explicit A.6.3 construction or C.29 representation: a projection expression, publication face, and
U.Viewremain different objects, while any cross-context reuse stays explicit. -
Views and viewpoints. ISO/IEC/IEEE 42010:2022, particularly its concepts in §5, distinguishes an architecture, its description, viewpoints, views and correspondences. That supports organizing an API description around concerns and relating its parts. FPF's stack and face rules are additional choices. Query and projection operations can construct candidate epistemes and make omissions inspectable; E.17.0 supplies the separate FPF test against the exact viewpoint episteme.
-
DDD bounded contexts and microservice contract-language practice. Architecture practice keeps meaning local and makes crossings explicit. A.6’s stack and L/A/D/E claim-classification discipline provide a placement scheme for what belongs to the context boundary claim set, what belongs at the entry gate, what belongs to governance duties, and what belongs to observability evidence.
-
Observability as evidence discipline. OpenTelemetry Trace API and Trace SDK distinguish span identity, recording and export; sampling or dropped records can limit available observations. The Metrics Data Model makes aggregation explicit. These are current specification contributions, not proof of a payment result. Google SRE, Monitoring Distributed Systems (2016) supplies a historical practical distinction between a successful transport response and correct service content. A.10 connects the chosen observations to the claim and use; retention and exposure prescriptions belong to their own D claims.
-
Zero Trust, dynamic authorization, and policy as code. Authorization practice separates policy, API, or schema text from a decision over subject, requested policy operation or work class, affected resource or work target, context, policy or gate version, decision source, and evidence. Cedar's authorization semantics separates a request's principal, action, resource and context from policies and entity data, policy evaluation, and the combined
AlloworDenyresponse with diagnostics. The historical architecture in NIST SP 800-207 (2020), §2.1 and §3 also distinguishes the policy decision from administration and enforcement, using policy and observable state as inputs. An institutional grant used by an FPF gate retains its own obtaining conditions. A.6 keeps the corresponding L/A/D/E claims connected; use A.15.4 when appearance leaves an action prerequisite unrecovered, and A.15 for enactment alignment. -
Relation-based authorization and consistent evaluation. The historical Zanzibar design, described by Pang et al. (2019), §§2.1–2.3 and 2.4.4, combines relation tuples with configured rules to determine effective permissions. Its access checks use a consistent snapshot constrained by the relevant content version. This supplies a concrete reason to recover the decision's inputs and currentness conditions when reusing an authorization result after an access relation or protected content changes. The relation definitions, stored tuples, evaluation and returned decision make different contributions to that judgement.
-
Markov blankets and active inference as probabilistic boundary views only after restoration. Markov-blanket thinking can help pick observables and diagnose boundary-condition failures, but the source phrase must be restored before it carries an A.6 boundary claim. It may name accepted local Markov dynamics, a mathematical or probabilistic lens, a holon delimitation or crossing relation, an interface, an interface module, a physical component, a boundary description, or an agency-threshold claim. A.6 uses the phrase only after the boundary claim set is recovered; it does not replace deontics, invariants, admissibility gates, or the subject pattern of the physical or mathematical claim.
Relations
- Uses A.6.B as the classification authority:
A.6.B:8.4.1selects the job of permission wording. A.6 maps the resulting atomic claim to the stack; it does not put everyA.2.8.PERobject in D. The filled case inA.6.B:8.4.5.4demonstrates this classification. - Coordinates actual effects without merging them: Use A.15.1 only to identify a grounded dated Work occurrence; use A.3.4 for an independently identified actual transformation, including spontaneous or formal change with no Work; state each interaction, causal, production, speech-act, evaluation, evidence, or result claim through its applicable predicate and pattern. A description or carrier alone creates none of them.
- Constrains signature writing: Reinforces A.6.0 separation of Laws vs operational gates (AdmissibilityConditions live in mechanisms).
- Constrains mechanism writing: Uses A.6.1 for OperationAlgebra, LawSet, AdmissibilityConditions and Applicability; local transport and evidence-interface sections retain their own claim classification.
- Requires EntityOfConcern and Description-episteme / publication-carrier discipline: Uses A.7 to prevent category mistakes; ties evidence to evidence carriers and publication faces to descriptions.
- Coordinates
U.View,U.Viewpoint, and publication use: E.17.0 governs viewpoint and view membership; MVPK selects exact epistemes, viewpoints, face uses, and publication forms; A.6.3 governs only optional source-to-receiving construction. - Unpacks “contract” talk: When boundary ambiguity changes interpretation or use, A.6.C applies A.2.3, A.2.8, A.2.8.PER, and A.2.9 to keep promise content, speech act, commitment or grant explicit; use A.15.1 only to identify dated Work, and its §4.6 dispatch requires the exact subject predicate for each application-result, production, change, delivery/transfer, evidence, or acceptance claim.
- Uses relation-specific declaration disciplines: use A.6.5 when an already recovered direct relation needs reusable participant typing. Use A.6.6 when basedness wording hides the dependent, base or direct predicate; stop at the ordinary assertion when it answers the receiving question.
- Coordinates with
C.28 CausalUse-CAL: When boundary prose uses causal-use evidence or a causal-use verdict to justify deployment, release, duty, commitment, or admissibility, A.6 splits the boundary sentence whileC.28carries the causal-use question,CausalityLadderRung, estimand, support basis, support verdict, and supported and unsupported causal uses. - Coordinates work and consequences:
A.15.1supplies only a datedU.Workoccurrence. Its §4.6 table routes an application/result binding, production, change, evaluation result, evidence use, delivery/transfer, and acceptance to separate subject patterns.A.15,A.10,B.3,A.21, andA.20govern the enactment-alignment, evidence, assurance, gate, or constraint claim when current.
Quantum-like boundary-claim classification note
Use A.6 first for ordinary boundary, interface, API, protocol, contract, connector, publication-face, and observability-evidence wording. Quantum-like boundary prose is supported only when the boundary text needs a probe, order, frame, export, or state-reading distinction that ordinary boundary patterns would otherwise erase.
Action classification:
- Identify the boundary sentence and name the boundary object in ordinary A.6 terms.
- Name the actual participants and any channel or carrier required by the boundary relation or operation separately.
- Apply the applicable ordinary FPF patterns to the ordinary boundary content: A.6, A.6.B, F.9, A.15, C.16, or C.25.
- If the boundary text uses a coarsened representation to claim preserved action, intervention, manipulation, explanation, or preserved structure across representation scales, state the causal-abstraction or approximate-causal-abstraction mapping before retaining QL wording.
- Ask whether the boundary act is being used as a passive read or unjustified lossless-transfer reading while changing the represented state, export validity, or viability decision.
- If yes, apply
C.26.1only to that remaining residual question; keep the ordinary boundary pattern active. - If no, keep the text in the ordinary boundary, bridge, work, measurement, or quality pattern and remove QL wording.
Minimum boundary discipline before a quantum-like boundary reading:
Useful outputs:
- an L/A/D/E-classified boundary claim set when ordinary A.6 is enough;
- an F.9 Bridge and separate bounded-use claim when the export question concerns two exact local senses and the Bridge predicate obtains; add a Bridge Card only when durable packaging is useful;
- a C.26.1 probe-coupled boundary note only when the boundary act changes the represented state in a decision-relevant way;
- a relation repair using
A.6.Pwhen coupling words become reusable relation candidates, plusF.18only when the recovered relation term itself needs durable naming.
A.6:End
Recognition Signatures: Find the Defining Episteme for a Description
Type: Architectural pattern Status: Stable Normativity: Normative unless marked informative
Problem frame
Use this when an encountered description leaves it unclear which defining account to inspect. A boundary clause, method note, interface excerpt or pattern opening can identify a useful next reading if its purpose, applicability and defining source are recoverable.
First useful move. State what the encountered description is for and identify its defining U.Episteme, using definitionEpistemeRef when a reference is needed. Include an exclusion or rejected neighboring reading only when it changes recognition or use under §4.1.
This gives the reader a description to inspect before broader comparison or a decision to apply its contents. A summary or excerpt can guide that choice, while its source reference allows the reader to check the defining account.
Reuse an already adequate identification. If the question instead concerns full boundary-claim classification, publication/view conditions, the Method’s semantics, cross-pattern selection or durable naming, use the pattern for that question.
Problem
A missing or ambiguous recognition cue can leave the following questions unresolved:
- One reader finds a boundary, method, interface, or pattern-local opening but cannot tell whether it is the right description to inspect.
- An encountered carrier or public projection is misread as the defining
U.Episteme. - Recognition cues drift into description semantics, workflow hints, graph metaphors, or lexical aliases that belong elsewhere.
- Pattern-entry navigation is asked to identify the encountered description before the reader can begin pattern-language comparison.
Forces
Solution
Recognition-cue discipline
A recognition cue makes the description, its purpose and relevant applicability conditions recoverable, with a reference to its defining account. Identify the encountered carrier or projection when that distinction affects recognition.
Reject a nearby reading or wrong defining U.Episteme only when it passes F.19's
grounded-guard test: the rejected reading has an independent local ground, is
plausible for the intended reader, and changes truth, understanding, selection,
safety, stop, reliance, or action. Use the
smallest clear correction; do not invent an alternative to fill the cue shape.
Here "description-recognition signature" is a lower-case authoring and reading
discipline, not by itself a typed U.Signature or a new formal kind. A typed
declaration requires the applicable neighboring pattern's explicit conditions.
The encountered carrier or projection may help recognition; it does not become authoritative merely by being encountered.
Point to the defining U.Episteme through the available publication. Identify the E.24.PUB publication occurrence separately when its identity changes which definition or use is available. The publication and its carrier keep their own identities.
A.6.RSIG does not govern:
- general information architecture or search UX;
- documentation layout or publication-face selection;
- pattern-entry discoverability across a pattern language;
- the full semantics of the description itself;
- lexical repair, alias acceptance, or naming governance as such;
- graph ontology, workflow sequencing, or runtime route semantics.
Two-level description-recognition shape
Reader-visible minimum. Ordinary prose is sufficient when it makes these values recoverable:
- what this description is for;
- when it applies;
- any exclusion that changes recognition or use;
- which definitionEpistemeRef applies;
- what nearby false reading or wrong defining
U.Epistemeto reject, when the grounded-guard condition in §4.1 holds.
Expanded questions when needed. Use the following questions when the shorter cue leaves a consequential recognition ambiguity unresolved. Existing prose can carry the answers; a separate form is optional.
Use the exclusion and false-neighbor fields only when the grounded-guard condition in §4.1 holds. The viewpoint field names the reader’s perspective; identify a formal U.Viewpoint episteme only when that separate relation matters.
The questions help distinguish the encountered description and its defining account from their publication or carrier when those differences affect the choice.
Minimal local repair and review sequence
Use this sequence when authoring or reviewing one recognition-signature repair:
- Name the encountered description and the reader’s question.
- Name the encountered carrier or projection if confusing it with authority is a live risk.
- State the applicability and any exclusion needed to choose the description.
- Name the defining
U.Epistemeto inspect first. - When the grounded-guard condition in §4.1 holds, name the nearby false
description or wrong defining
U.Epistemeto reject. - State the useful next inspection or the missing basis that prevents it.
- If that stop cannot be stated without A.6.B claim routing, publication-face law,
lexical repair, or cross-pattern comparison, apply the appropriate neighboring pattern instead of
stretching
A.6.RSIG.
The result is the recognition statement, its defining source reference and the useful next inspection or limitation. Include a false-neighbor correction only under §4.1.
Common uses
The same recognition question occurs in several settings:
- boundary-description recognition: can one reader recover what one boundary-presented description is for before the reader needs to classify its claims as L/A/D/E;
- method-description applicability recognition: can one reader recover whether one method description is the right description to inspect, reject, or compare for the reader's question;
- interface/access-description recognition: can one reader recover the right access or interface description without confusing it with promise, execution, or downstream effect semantics;
- pattern-local recognition-signature case: can one reader recover one pattern opening as the right first description to inspect before broader pattern-language comparison begins.
Neighbor boundaries
- use
A.6.Bwhen the reader needs to classify the boundary claims asL/A/D/E; E.17.0tests viewpoint/view membership;E.17publishes reader-facing forms of an already accepted engineering account; useE.24.PUBwhen publication occurrence, form, or carrier identity affects the recognition use;E.10.D2recovers description-episteme and specification-use distinctions; useE.10cues withinF.19for wording,A.6.Pfor under-specified direct relations, andF.18for durable naming and its collision checks;C.16.Qrepairs overloaded recognition or discoverability quality wording;C.25applies when the quality-family claim depends on several differently typed contributors; a single-Characteristic claim stays with its direct Characteristic pattern;- the relevant authoritative pattern body governs pattern semantics when the encountered description is one pattern-local opening.
The four-part split for pattern-local recognition is:
When a neighboring pattern is needed
If the task requires a quality claim, typed signature declaration, reusable description, or publication-face rule, use the neighboring pattern that governs that object or claim, including its evidence requirements. The recognition cue alone does not establish that result.
Archetypal grounding
System-side worked recognition repair: boundary-presented description
Draft cue:
"The system shall reject invalid requests."
Why the cue is not enough yet:
- the reader cannot tell whether they are reading one law, admissibility gate, duty, work effect, or evidence statement;
- one summary page or local paraphrase can be mistaken for the governing boundary description;
- a reviewer can start arguing full semantics before identifying which description to inspect.
Recognition repair:
First recover the defining description; the cue alone leaves its boundary claim unresolved. For the worked branch below, suppose inspection of that defining episteme establishes a request-admissibility condition. If the source instead prescribes a duty or states another boundary claim, recognize that content and apply its corresponding entry.
description_seen= one boundary-presented admissibility description.encountered_carrier_or_projection= one clause or excerpt where the description is seen.reader_viewpoint= the perspective of a practitioner or reviewer deciding whether this is the right boundary description to inspect first.applies_to= requests presented at the boundary under the declared admissibility conditions.excludes= downstream effect claims, duty allocation, or evidence claims not stated by this description.definitionEpistemeRef= the governing boundary description, not one local paraphrase or summary note.nearby_false_description_or_wrong_definition_episteme= an evidence/work claim or a different routed-quadrant statement mistaken for the governing admissibility description.first_admissible_entry_stop_or_reroute= the reader can now say "this is the admissibility description to inspect first"; if the reader needs to classify the boundary claims, inspectA.6.B.
System-side anti-case: interface/access description over-read as promise
Draft cue:
"
POST /deploytriggers deployment."
Plausible but wrong first reading:
- the reader treats deployment initiation as a guarantee of successful completion or of the whole deployment result.
Recognition repair:
description_seen= one interface/access description.encountered_carrier_or_projection= one API excerpt or endpoint note.applies_to= request accessibility, invocation form, and the stated deployment initiation under the conditions in the defining description.excludes= success, completion, rollout, or downstream effect guarantees not present in the access description itself.definitionEpistemeRef= the defining episteme for the access description; inspect the specification or pattern governing downstream effect separately if that question is current.first_admissible_entry_stop_or_reroute= "this is the access description to inspect first: it describes invocation ofPOST /deployand deployment initiation, not guaranteed successful completion."
Episteme-side worked recognition repair: method-description applicability
Draft cue:
"Use pairwise comparison."
Why the cue is not enough yet:
- the reader cannot tell whether the note applies to ranking alternatives, selecting one option, shaping a shortlist, or comparing method families;
- the method note can be mistaken for the defining
U.Epistemeof selection semantics; - a team can prematurely choose
C.11orG.5before identifying what the pairwise comparison is to determine.
Recognition repair:
With only the cue, first ask what the pairwise comparison is intended to determine. For the worked branch below, suppose the defining episteme supplies comparison under a declared comparator but no selection or publication rule. If the source also defines selection, recover and use that contribution.
description_seen= one method-description applicability note.encountered_carrier_or_projection= one method-description note, pattern excerpt, or review comment that mentions pairwise comparison.applies_to= comparison under a declared comparator set or characteristic family.excludes= selection or publication rules absent from this defining description. Apply the governing pattern if either result is needed.definitionEpistemeRef= the defining comparison or Method-description episteme identified from the source, which this short cue does not supply.nearby_false_description_or_wrong_definition_episteme= selection/publication doctrine treated as if the method note had already settled it.first_admissible_entry_stop_or_reroute= inspect the identified comparison description. Its applicability and any subsequent selection need their own conditions established.
Bias-Annotation
A familiar label can attract the reader to the wrong account. The boundary, access and pairwise-comparison cases show why recognizing the subject and recovering the defining source must work together. A cue that already does this needs no additional form, alias or classification.
Conformance checklist
- CC-RSIG-1 First-contact only. The pattern governs recognition of the right description, not the full semantics of that description.
- CC-RSIG-2 Carrier/definition-episteme split. A conforming description-recognition signature
distinguishes
description_seen, encountered carrier or projection, definingU.Episteme, and projection role when those distinctions affect recognition or use. The encountered carrier or projection may help recognition, but it does not become authoritative merely by being encountered. - CC-RSIG-3 Neighbor boundaries explicit. The text states the conditions under which the recognition question calls for each relevant neighboring pattern in §4.4; use only the patterns that govern the current questions.
- CC-RSIG-4 No kind inflation. An ordinary recognition cue is not by itself a
typed
U.Signature; a task requiring a typed declaration uses the applicable neighboring pattern under §4.5. - CC-RSIG-5 Recoverable cue. For a consequential recognition use, keep the description’s purpose, applicability, defining source and next inspection recoverable. Include viewpoint, carrier/projection distinctions, exclusions or a false-neighbor correction when they change the reading under §4.1.
- CC-RSIG-6 No alias minting. Query cues and ordinary phrasing do not by
themselves establish a naming settlement or Bridge. Use
F.18for naming settlement andF.9for a Bridge, each under its own conditions.
Common Anti-Patterns and How to Avoid Them
- Recognition-as-semantics. The opening tries to define the whole description instead of making the right description recoverable. Repair by shrinking back to first-contact discrimination.
- Carrier-as-authority. A local excerpt, public projection, or retrieved
fragment is treated as the defining
U.Episteme. Repair by naming the encountered carrier or projection and the definingU.Epistemeseparately. - Boundary-routing collapse. A boundary-description cue tries to absorb
L/A/D/E-classified claim structure. Repair by classifying the boundary claims under
A.6.B. - Pattern-language collapse. Pattern-entry comparison is written as if it
were just another description cue. Repair by routing cross-pattern selection
to
E.11. - Signature inflation. Any recurring cue is treated as one typed signature
object. Repair by keeping
description-recognition signaturelower-case unless one explicit promotion is justified.
Consequences
A reader can identify the relevant defining account while leaving its full semantics, applicability judgment and any subsequent selection to the work that needs them.
The cost is recovering enough purpose, conditions and source identity to make that choice. Use the expanded questions only when the ordinary cue leaves a consequential ambiguity.
Rationale
A recognition cue lets a reader choose what to inspect from the description’s stated purpose and conditions. The source reference then makes that first estimate checkable against the defining account. If the account does not support the cue, revise the cue or keep the choice unresolved; a recognizable label alone cannot settle the discrepancy. An adequate cue can finish this first-reading task without deciding whether the full Method is applicable or effective.
The same construction works for a boundary clause, an interface description or a Method note because each connects an encountered expression to a defining account and a bounded reading decision. Their domain meanings remain different. This shared relation explains the common questions without turning recognition into one universal entry or semantics pattern.
SoTA-Echoing
The following sources contribute to cue economy, recoverable definition and bounded expectations. Their contributions apply to the recognition question; the defining subject account supplies its substantive semantics.
Relations
- Builds on:
A.6,A.6.P,F.18,E.10 - Does not specialise:
A.6.0/U.Signature; it uses "signature" only in the lower-case cue-pattern sense unless an explicit neighbouring pattern promotes the structure into a typed declaration. - Neighbors:
A.6.B,A.6.C,E.17.0,E.17,E.10.D2,C.25,C.16.Q - Supports:
E.11as the pattern-language application above this neutral substrate
A.6.RSIG:End
A.6.B — Boundary Norm Square (Laws / Admissibility / Deontics / Work‑Effects)
Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) Placement: Part A → A.6.B (matrix module; referenced by A.6 cluster overview) Builds on: E.8 (authoring template), A.6.0 (
U.Signature), A.6.1 (U.Mechanism), A.6.3 (EntityOfConcern-preserving episteme construction), E.17.0/E.17 (MVPK + “no new semantics” faces), A.7 (EntityOfConcern and Description-episteme boundary; specification-use and publication-carrier distinction), A.2.3 (promise content when contract language is current), A.2.8 (U.Commitment), A.2.8.PER (subject pattern selected by the permission-word branch), A.2.9 (U.SpeechAct), E.10.D2 (EntityOfConcern and Description-episteme boundary; specification-use and refinement discipline), E.10 publication face, form, unit, and carrier discipline Purpose (one line): Provide a canonical four-way classification of boundary statements (L/A/D/E), rules for writing each quadrant, and rules for explicit cross‑quadrant references to support later boundary evolution and audit.
Use this when. Use A.6.B when boundary wording mixes definitions, runtime entry conditions, generic prescriptions, individual duties or grants, actual work or evaluation results, and evidence.
First useful move. Identify what the reader needs to decide or understand about the boundary. Use §4.4 to select the claims and grounds needed for that answer; split mixed claims, classify their jobs, and name consequential dependencies by ID or canonical location.
What changes in practice. Laws, gates, governance, and work-and-evidence claims can change without silently changing one another; publication faces reuse the canonical claims instead of restating them.
Ordinary non-use boundary. A one-off local sentence with one recoverable logical job needs the correct quadrant, but it does not need a Claim Register or a separate publication form. Add those only when reuse, decision, audit, or cross-face citation needs them; §6.1 requires any material dependency to name the claim by ID or canonical location.
A.6.B:0 — Conventions
Keywords. The key words MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, and SHALL have their RFC 2119/8174 meanings only when capitalized as shown.
Quadrant labels. This pattern uses the classification labels L / A / D / E as statement quadrants:
- L — Laws & Definitions
- A — Admissibility & Gates
- D — Deontics & Commitments
- E — Work‑Effects & Evidence
These labels are claim-classification labels for statements, not MVPK face designators and not pattern identifiers.
Statement identifiers (recommended). Classifiable statements SHOULD be given stable IDs with a quadrant prefix: L-*, A-*, D-*, E-*. Other sections and views SHOULD reference these IDs or the canonical claim locations. A faithful explanation may accompany the reference under §6.1.
Non-collision note (informative). The A-* prefix here is “Admissibility”, not Part-A numbering and not MVPK’s AssuranceLane face designator. If this is a readability hazard in your program, prefer an explicit G-* (“Gate”) local convention while keeping the quadrant name “Admissibility”. Also avoid introducing single-letter mnemonics for MVPK face designators inside this cluster; spell face designators in full to reduce collisions.
Atomic claim. An atomic claim is a sentence (or bullet) that performs exactly one logical role and is classifiable under exactly one quadrant. If a sentence mixes roles, it is not atomic and MUST be split before it can be classified.
Claim job and adjudication basis. A quadrant identifies what a boundary claim contributes. Its adjudication basis states how that claim can be settled. Definitions and declared entry predicates are both description content. Generic normative content is recovered from its source; an individual duty or grant requires its actual constitutive basis. An occurrence or evaluated-result claim requires the facts specified by its subject predicate.
Deontic claims. Writing a D-* claim records either generic normative content or a claim about an individual duty, commitment, or grant. When the wording is about permission, use the permission-word branch in §8.4.1 to recover the object, what makes it obtain, and the evidence needed before reliance. The instituting act and any compliance finding have their separate claims.
Modality. Preserve whether a sentence defines, prescribes, permits, hypothesizes or reports. Use that meaning together with the claim's job under §4; a modal word alone leaves the classification unresolved.
A.6.B:1 — Problem frame
Boundary descriptions routinely mix four distinct claim families: definitions are written as obligations, runtime gates are hidden inside laws, governance talk is assigned to “the interface”, and operational-result “guarantees” are asserted without the actual Work, evaluation, or observation needed to settle them. This makes substitution unclear and leaves apparent auditability without claims that can be adjudicated.
The classification connects the strata already distinguished in FPF: Signature and Mechanism; the EntityOfConcern, claim-bearing episteme and carrier; and views under viewpoints. It lets a reader identify each claim, how it is settled and which other claims its use depends on.
A.6.B:2 — Problem
When authors cannot reliably answer two questions—
- “What does this claim contribute: meaning, an admission condition, normative content or a deontic position, or an occurrence/evidence account?”
- “What grounds are needed to settle this claim?”
—then boundary statements drift across layers, faces fork semantics, and “compliance” becomes a matter of interpretation rather than a property that can be checked.
A boundary needs a minimal, stable classification that:
- classifies every atomic statement into a unique quadrant, and
- requires any cross‑quadrant dependencies to be explicitly referenced.
A.6.B:3 — Forces
Solution — the Boundary Norm Square
Four claim jobs and their grounds
The Boundary Norm Square distinguishes four jobs in a boundary account. A definition can remain fixed while a gate changes; a duty can obtain while its bearer fails to perform it. An earlier observation may still be valid evidence when a changed admission condition leads to refusal. Establish the observation’s fitness for the new check, then apply that condition to decide admission. Keeping those claims distinct makes their dependencies available for a change or audit decision.
Classify what the sentence asserts, then establish its grounds. For example, a declared entry predicate belongs in A and the result of applying it to one request belongs in E. A claim that a grant currently permits an action belongs in D; the instituting act, an evaluation of that grant and an actual exercise of it have their own E claims. The predicate definition and the individual claims remain description content, with different subjects and adjudication conditions.
A.6.B:4.2 — The square
Clarification (classify the claim by its job, not by its subject pattern).
- Classify the atomic claim by what its sentence states and by the conditions that let a reader decide it.
- The pattern governing the referenced object supplies its predicate and obtaining conditions; it does not choose the claim's quadrant.
- When permission wording is present, use the single permission-word branch in §8.4.1. It separates the possible jobs of that wording without inventing a common “permission result” kind.
Normative rule (single quadrant). Each atomic boundary claim MUST be assigned exactly one job under L/A/D/E. Recover an unresolved meaning before assigning it. A condition or reference within one coherent claim does not by itself add another asserted claim.
Normative rule (mixed claims). A conforming boundary text SHALL separate independently asserted claims with different jobs. For example, a duty to enforce an entry rule and a report of one enforcement result have separate D and E claims referring to the A rule. Preserve the logical connection when splitting the wording.
A.6.B:4.3 — Canonical placements in the Signature Stack
The quadrants have canonical placements in the boundary stack:
- L → Signature layer:
U.Signature.Laws(and mechanism‑local semantic laws if present). - A → Admission layer: keep the condition in its governing rule's canonical source. Mechanism applications use
U.Mechanism.AdmissibilityConditions; A.21 gates use the applicable profile rule. - D → Deontics & Commitments layer: atomic claims about a generic prescription or about one separately obtaining individual duty, recommendation-as-duty, prohibition, or commitment. When permission wording is live, §8.4.1 decides whether its claim also belongs here.
- E → Work-Effects & Evidence layer: truth-conditional claims whose satisfaction requires actual work, evaluation, observation, or produced carriers.
A publication face MUST NOT introduce new semantic claims outside this L/A/D/E-classified claim set. E.17 (MVPK) enforces this rule for publication faces and their selected profiles.
Develop a boundary explanation for its receiving use
Start with the boundary passage, its available sources and the reader's question. The square helps recover what each claim contributes and what would settle it. The explanation connects the claims needed for the reader to interpret, use or change that boundary.
1. Recover the question and the claims already made. Establish which understanding or decision the text must support. Interpreting a metric, deciding whether a request may enter and determining whether a duty was fulfilled need different answers. Recover the draft's asserted content, modality and scope. If a word such as guarantees leaves the intended assertion open, use A.6.C:4.3 with the author or source to resolve that meaning. Keep a consequential unresolved meaning explicit until its source is available.
2. Establish the grounds of the answer. Split independently asserted jobs and classify them through §§4.1–4.3. Use the detailed procedure and conditional permission-word branch in §8.4.1 where needed. Recover the definition for a meaning claim, the declared predicate for an entry condition, the normative or constitutive basis for a duty or grant, and the facts for an occurrence or finding. Preserve the source's conditions and qualifications. A missing ground requires a targeted return to the source or the responsible practice. If the work calls for a new rule or commitment, develop and establish it through its governing practice before treating it as current boundary content.
3. Select the claims and detail on which the reader's answer depends. Work backward from that answer. A reported measurement needs its quantity, population, conditions and interpretation; judging fulfilment of a commitment additionally needs that commitment and its comparison rule. Follow such dependencies until the remaining premises are supplied by the text or by references the intended reader can obtain and understand. Use §6 for their relations. Include a detail when changing it could change the answer, when it explains why a step follows, or when the reader needs it to perform the stated use. A complete four-quadrant account is warranted when the question crosses all four jobs. Keep other valid claims in their canonical sources for their own uses.
4. Compose the explanation around that reasoning. State the answer in the reader's working terms, connect its supporting claims, and make the conditions that limit its use recoverable. Place a definition beside the claim that needs it and an observation beside the inference it supports. IDs or canonical locations preserve material dependencies under §6.1; the accompanying explanation supplies their meaning for this reader. Use a Claim Register or separate Tech and Plain forms when the reuse or publication conditions call for them. Selection and recomposition preserve the source claims; a new semantic constraint first needs its own canonical claim.
5. Return the text to the reader's work. Follow the intended interpretation or decision using the explanation. Identify any consequential premise the reader would have to invent, obtain that premise or state the precise unresolved question, and revise the affected connection. Consider a relevant change of condition: show which claim must be reconsidered and which grounds remain usable. Stop when the text supports the assigned understanding or decision with its limits. A later question can require a different selection from the same canonical claims.
The cases in §8.4 show these authoring choices. Their claims about latency, coaxiality and project entry are the material being explained; the reusable operation is selecting and connecting that material for a reader's question.
A.6.B:5 — Quadrant specifications
The following normative specifications state what each quadrant is for, how it is written, and what it must not contain.
A.6.B:5.1 — Quadrant L: Laws & Definitions
Intent. State truth‑conditional content: definitions, invariants, typing and well-formedness constraints, equational laws.
Adjudication. In‑description: can be checked by inspection, proof, type validation, or model reasoning.
Canonical form. Definition: / Invariant: / predicate‑style constraints using “is / iff / for all”.
Prohibitions.
- An
L-*statement MUST NOT contain RFC deontic keywords (MUST, SHALL, SHOULD, or MAY) as operators inside the law or definition itself. - An
L-*statement MUST NOT encode runtime gate predicates (those areA-*). - An
L-*statement MUST NOT assert evidence availability or measurement outcomes (those areE-*).
A.7 EntityOfConcern binding. Identify what the L-* definition, invariant,
or typing rule concerns, separately from the episteme carrying the claim. Its
EntityOfConcern need not itself be a description and may be Work.
Typical dependence. A-* and E-* claims may reference L-* IDs or canonical locations for vocabulary, metric definitions, and invariants needed for interpretation.
A.6.B:5.2 — Quadrant A: Admissibility & Gates
Intent. Specify when a named action or application is admissible under its governing rule: for example, runtime entry predicates, validity gates, and applicability checks that require context or execution environment. An A-* predicate may consume a separately established result as one input, but it does not create or settle that result. If the sentence uses permission wording, choose its job with the branch in §8.4.1.
Applicability and admissibility. Signature Applicability scopes intended use and bounded context; a mechanism's runtime entry predicates belong in U.Mechanism.AdmissibilityConditions as A-*. If prose says “clients must satisfy the applicability”, first recover whether it means the declared scope or an entry condition. State the generic D-* prescription, or the independently instituted individual duty, separately and reference the condition it requires. Classify that condition as A-* only when it is an entry predicate.
Adjudication. Inspect the declared entry rule and its inputs to establish the A claim. Evaluate that predicate at the named action's entry or stated application point to obtain a particular satisfaction or gate-decision result; report that result separately in E.
Canonical form. Predicate style, e.g.:
- “A request is admissible iff …”
admissible(x) iff P(x)(conceptual form; no particular syntax is required)
Prohibitions.
- An
A-*statement MUST NOT be placed inU.Signature.Laws. - An
A-*statement MUST NOT use RFC deontic keywords as if it were an agent obligation. (It is a gate predicate, not a duty.) - An
A-*statement MUST NOT claim that evidence exists (that isE-*) or that someone must enforce the gate (that isD-*).
A.7 EntityOfConcern binding. An A-* claim concerns the admission predicate
for a named action or application, not a client's duty to comply with it.
Keep that predicate distinct from the episteme carrying the claim.
Required references. If an A-* predicate relies on defined terms or invariants, it SHOULD reference the relevant L-* IDs or canonical locations (or at minimum the signature that defines them).
A.6.B:5.3 — Quadrant D: Deontics & Commitments
Intent. State one atomic deontic claim. A generic prescription states what one policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence. A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8 U.Commitment. When a sentence sounds permissive, use §8.4.1; only its Grant or norm row enters D. Writing the D-* sentence alone neither institutes a relation nor establishes compliance.
Adjudication. For a generic prescription, inspect the normative source, its applicable rule content, scope, and current edition. For an individual duty, apply A.2.8 to the separately obtaining commitment and its actual basis. The wording alone establishes neither obtaining nor compliance.
Canonical form. First choose the route. A generic D claim names the normative episteme and the rule content being stated, without inventing an individual bearer.
An individual-duty D claim names the actual bearer and U.Commitment; a system-role kind or assignment may be a rule ground but is neither bearer nor duty.
A responsibility claim uses an admitted domain responsibility predicate and its actual participants, or returns its missing governor. A permissive-looking word does not by itself select D; use §8.4.1 for the grant route.
Examples:
- Generic: “
APIEntryPolicy-v4requires covered clients to satisfyA-….” No individual commitment is asserted. - Individual: “Actual bearer
ClientIntegrator-Ahas commitmentCOM-17to satisfyA-….”
Canonical assertion (recommended; lintable). Use a CommitmentAssertion only when an individual-duty claim must be reused or audited. It concerns one separately obtaining U.Commitment and makes explicit:
entityOfConcernRef, resolving to oneU.Commitmentoccurrence, and theD-*claim ID;- exactly one actual bearer branch:
dutyBearerSystemRefordutyBearerPartyRef; - non-empty
dutyReferentRefsand any actual counterparties; - the A.2.8
DeonticModalityToken, scope, and validity window; - the current constitutive policy, individualizing rule, and actual instituting basis required by that rule; and
- evidence-claim or carrier references only when the receiving reliance or adjudication needs them.
The assertion states and supports a claim about the relation. Fields, publication or evidence have a constitutive role only when the identified rule requires that contribution and its subject pattern's test is satisfied.
Prohibitions.
-
A generic
D-*statement MUST NOT invent an individual bearer or commitment; name its normative source and rule content.An individual-duty
D-*statement MUST NOT use “the system, service, interface, or specification” as a vague subject; name the actual duty-bearing system or separately governed party andU.Commitment, with an assignment only when the constitutive rule uses it as a ground.Use
A.6.Cwhen ambiguity in promise, utterance, approval, guarantee, or agreement-like boundary wording changes the claim's interpretation or use. -
A
D-*statement MUST NOT give a referencedL-*orA-*predicate a different meaning. It MUST reference that predicate by ID or canonical location when its meaning depends on it; a faithful explanation may accompany the reference. -
A
D-*statement MUST NOT represent a duty, commitment, or grant as a law or assert that writing the claim alone makes it obtain.
A.7 EntityOfConcern binding. A generic D-* claim episteme concerns the normative rule content it states. An individual D-* claim concerns the duty, commitment, or grant named by its content and does not substitute for that object. When permission wording is live, the branch in §8.4.1 names the subject pattern and the obtaining or non-obtaining test.
Required references.
- If a
D-*claim states a prescription or duty to comply with a gate, it MUST reference the relevantA-*ID(s) or canonical location(s). - If a
D-*statement is meant to be auditable, it SHOULD reference theE-*claim(s) that provide evidence and the carrier classes involved.
A.6.B:5.4 — Quadrant E: Work‑Effects & Evidence
Intent. State an actual occurrence, evaluated finding, observed condition or evidence-support claim. Settle it from the actual work, evaluation, observation, or carrier conditions required by its predicate.
Adjudication. From actual work, evaluation or observation under the claim’s subject predicate. A record can support that judgment through its evidence relation; its presence alone does not settle the claim.
Canonical form. Write the ordinary result first, then make recoverable only what settles it:
- the predicate and object that the claim concerns;
- the participants, work or evaluation occurrence, scope/window, comparison frame, and other conditions required by that predicate; and
- the evidence or source-use relation when the receiving use needs that support; identify the supporting carrier only when carrier identity matters to that use. A carrier may support the claim but does not create the work, effect, or finding.
When permission wording is current, use the branch in §8.4.1 for the occurrence or finding, its failure test, predicate, and subject-pattern locator; do not repeat that subject-question catalogue here.
Prohibitions.
-
E-*statements SHOULD NOT use RFC deontic keywords; they report adjudicable results rather than obligations. -
An
E-*statement MUST NOT hide a gate predicate; gate predicates areA-*. -
For a claim about a particular dated Work, first recover each actual performer through A.13 and let A.15.1 independently admit the Work. Ordinary metonymy is usable when the capable performer remains recoverable; an interface, record or publication does not supply a performer merely by being named.
Add an A.2.1 assignment reference and F.6 only when this claim or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer. Missing or failed F.6 alone does not overturn independently admitted Work.
If the attribution finding questions a premise consumed by Work admission, recheck that premise and the dependent claims. If a duty or commitment is also claimed, express it separately in
D-*.
A.7 EntityOfConcern binding. An E-* claim episteme concerns the work effect, evaluated finding, evidence relation, or carrier condition named by its predicate. A record or carrier is a separate object and becomes the concern only when its existence or condition is itself the claim.
Required references.
- If the result depends on an entry predicate, the
E-*statement SHOULD reference the relevantA-*claim. If it depends on an actual gate decision, reference the separateE-*claim about that A.21 decision result. - If another object is needed to settle the predicate, reference that object's subject pattern without importing its quadrant.
- If evidence is used for reliance, recover the independently established support or evidence-use relation and its basis. Use A.2.4 for the first evidence-use or status-use classification; use A.10 when the source-to-use account must remain replayable, and G.6 when an addressable provenance path is needed. Carrier presence alone is not support.
A.6.B:6 — Cross‑quadrant link discipline
The square also makes dependencies between claims inspectable. A material dependency MUST be explicit by claim ID or canonical location.
A.6.B:6.1 — Explicit reference rule
If a claim’s meaning materially depends on another L/A/D/E-classified claim, that dependency MUST be represented as an explicit reference to its ID or canonical location. A faithful restatement may explain the referenced content; it does not define an alternative rule.
A reader can then follow the explanation back to its governing claim and reconsider dependent uses when that claim changes.
A.6.B:6.2 — Canonical cross‑quadrant dependency patterns
These patterns are valid (and common). The square becomes operational when these links are used systematically.
(D → A) Prescription-or-duty-to-gate linkage
When governance says that a gate must be satisfied or enforced:
- generic
D-*: “Policy-Prequires covered subjects to satisfy or enforceA-*”; or - individual
D-*: “Actual bearerShas commitmentCto satisfy or enforceA-*.”
This separates what is admissible (A) from generic normative content and any separately instituted individual duty (D). If responsibility is also claimed, state its admitted direct domain predicate or missing governor rather than inferring it from the duty.
(E → A) Evidence-for-gate linkage
When a claim reports actual observability of a gate decision:
E-*: “For the stated rejection or acceptance due toA-*, carrierCwas produced or observed under conditions …”
This separates gate semantics (A) from the actual observation or result (E). A prescription to produce or retain a carrier belongs in D; an expectation or plan alone supplies no actual E result.
(D → E) Prescription-or-duty-to-evidence linkage
When governance prescribes evidence production, retention, exposure, or a
measured property and a separate E-* claim states the related result:
- generic
D-*: “Policy-Prequires covered subjects to retain or expose carrier classCused byE-*…”; or - individual
D-*: “Actual bearerShas commitmentCMTto meet the criterion evaluated byE-*under the stated exclusions …”
This separates a generic prescription or individual duty (D) from its adjudication (E).
(A/E → L) Semantic grounding linkage
When a gate predicate or measurement relies on definitions or invariants:
A-*/E-*referencesL-*that define terms or metrics.
This prevents “metric drift” and “definition drift” across views.
(D → L) Governance-to-definition linkage
When a generic prescription or individual obligation relies on precise term or metric meanings:
D-*referencesL-*that define the terms or metrics it uses.
This keeps governance text from accidentally redefining semantics in prose.
(A → D/E) Normative or evaluated input to a gate
When entry depends on a current grant or a separately established finding, reference that D or E claim and state how its subject enters the predicate. For example, A-CAL-01 in §8.4.5.4 requires the grant stated by D-CAL-01 to cover the plan and time, together with the required conflict finding. The grant, finding and entry decision retain their own obtaining conditions. A changed input reopens the admission evaluation that consumed it.
A.6.B:6.3 — The “triangle decomposition” for mixed sentences
Normative rule (decomposition). A conforming boundary text SHALL decompose any mixed sentence into its claim jobs. Recover the predicate and modality of an observability clause before assigning its quadrant. The triangle applies when the source states all three:
- A: admissibility predicate (
A-*) - D: generic prescription or individual-duty claim referencing the gate (
D-* → A-*) - E: actual observation or result referencing the gate, with carriers when needed (
E-* → A-*)
Keep a prescription or individually instituted duty to produce evidence in D. Preserve an expectation or plan as such; leave the actual E result absent until its basis exists. This repairs mixed validity, authorization, compliance, audit, and security claims without adding an unsupported third claim.
A.6.B:6.4 — Ground each dependency
Reusable laws retain their declared meaning, while an admission predicate can consume a normative position or an evaluated result. For each material link, state what it supplies: meaning, an input condition, an evaluation target or evidence support. Settle each depended-on claim under its own rule.
These are cross-quadrant restrictions. They do not prohibit same-quadrant
references, such as L-* → L-* or E-* → E-*.
Normative rule (dependency grounds).
L-*claims MUST NOT depend on or referenceA-*,D-*, orE-*claims (except for purely informative notes marked informative).- An
A-*claim MAY reference aD-*claim for the normative content, duty or grant used by its entry predicate, and anE-*claim for a separately established finding or observation. It MUST identify the input and required scope or currentness under §5.2; deciding that entry is permitted requires the predicate to be satisfied.A-*may referenceL-*for defined terms or invariants. - An
E-*claim MAY reference aD-*claim as its evidence target or to identify the norm, duty, or grant used by its evaluation. TheE-*result MUST satisfy its own predicate and the actual-work, evaluation, or observation requirements of §5.4; theD-*claim alone establishes no result or compliance. (E-*may also referenceA-*for conditioning andL-*for metric or term meanings.) D-*claims MAY referenceL-*,A-*, andE-*claims when needed, and SHOULD do so by ID or canonical location rather than restating content.
Rationale (informative). The L restriction keeps the reusable definition or law independent of a particular gate application, deontic claim or observation. Expose a varying policy or state as a declared parameter; bind it where the condition or claim uses it.
A and D may refer to one another for different reasons: a duty can require enforcing a gate, while that gate consumes a separately obtaining grant. Examine those reasons rather than treating every reference as one ordering relation. A grant justified only by a gate result that itself assumes that grant would leave both claims ungrounded.
Evidence and results may report on normative claims or evaluate conduct against them under their own predicates.
A.6.B:7 — Mini-register: Claim Register (informative, recommended)
A Claim Register is a drift‑control device that lists every classifiable statement verbatim with classification metadata. It is not a new meaning authority.
Guidance (informative):
- The Statement cell should contain the normative text as authored (copied by value), not a paraphrase.
- Canonical location should point to the one place the statement “lives” (e.g.,
Signature.Laws,Mechanism.AdmissibilityConditions,TechCard.NormsCommitments,Evidence.Carriers), so other faces can cite its ID or canonical location. - Stack layer should be one of
{Signature, Admission, Norms-and-commitments, Evidence-and-carriers}to make classification auditable. - A.7 primary layer identifies the claim's EntityOfConcern, with its kind when needed. The concern may itself be a Description episteme or publication carrier; it remains distinct from the episteme carrying the claim.
- viewRef and viewpointRef are used when the corresponding view or viewpoint identity matters under E.17;
U.Viewmembership requires E.17.0 conformance. - Use References for explicit cross‑quadrant links: for example, which
D-*states a requirement or individual duty to enforce whichA-*predicate, whichE-*reports the result or evidence used to adjudicate which commitment, and whichL-*defines a metric used byE-*. Add external standards or policies where applicable.
Archetypal Grounding (Tell–Show–Show)
Informative. Examples for learning the square; they do not add requirements beyond A.6.B:10.
Tell (universal rule)
Decomposing every normative statement into atomic claims, classifying each under exactly one quadrant of the Boundary Norm Square, and expressing cross‑quadrant dependencies by claim ID or canonical location rather than paraphrase supports later boundary evolution and audit.
Show #1: Effect signature vs handler (post‑2015 effect systems)
An effect interface declares operations; handlers supply computation behavior. To describe a deployed service using that interface, recover the additional semantic, admission, normative and observation claims that its use needs:
- L: defines the operation vocabulary and the semantic laws required of this service's realizations.
- A: defines when the operation is admissible (runtime guard predicates).
- D: states who must enforce guards and what the provider commits to (operator and implementer duties; SLAs).
- E: ties “what happened” to observable carriers (traces, logs, metrics, and events) so commitments can be adjudicated.
The square prevents accidentally writing handler obligations as laws or treating observability as a definition.
Show #2: ML evaluation protocol boundary (reproducibility discipline)
A published “evaluation protocol” boundary (common in modern ML governance) benefits from classification:
-
L: metric definitions and invariants (e.g., what counts as AUROC; data partition invariants).
-
A: admissibility gates (dataset usage-term constraints; pinned environment constraints; seed policy).
-
D: checker and author duties (publish required faces; use declared dataset version; retention duties for run evidence carriers).
-
E: admitted system
EvaluationRunner-AperformedMLProtocolEvaluation-T1 : U.WorkoverModel-M1,Dataset-D7, the pinned environment and seed policy, and evaluation windowT; the application of the AUROC metric defined by the L claim returnedAUROCResult-T1withmeasuredAUROC=0.91.When a checker, gate, or audit decision needs a replayable source-to-use account for that result, an A.10 evidence-provenance path links it to carriers
RunLog-T1,DatasetHash-D7,EvaluationReport-R1, andTraceSet-T1.
The square keeps “must use dataset vX” (D) separate from “evaluation is admissible iff dataset usage terms match” (A), and both separate from “MLProtocolEvaluation-T1 returned AUROCResult-T1(measuredAUROC=0.91)” (E). The report and log carriers may support reliance on that result; producing a carrier is not the measured result.
A.6.B:8.4 — Worked Rewrite Kit (informative, recommended)
Informative. These cases apply the authoring method in §4.4 and the rules for atomicity, L/A/D/E classification, explicit references, triangle decomposition and grounded dependencies. Use the case whose receiving question matches the present work.
Goal
For the receiving question established in §4.4, recover the meaning of a boundary sentence that mixes “laws / gates / duties / evidence” and produce:
- atomic L/A/D/E-classified claims,
- explicit references by claim ID or canonical location,
- a readable recomposition (separate Tech and Plain forms when their readers need them).
Micro-procedure (Atomize → Classify → Triangle → Link → Bind References → Recompose)
Use this procedure to recover and express the claims selected through §4.4. The permission-word branch below supplies the detailed distinctions when permissive wording matters to that answer.
Step 1 — Atomize. Split mixed prose into atomic claims; each must classify to exactly one quadrant.
Step 2 — Classify (L/A/D/E).
- L if the claim is truth‑conditional and adjudicable in‑description (inspection, proof or type validation, or model reasoning over declared assumptions): definitions, invariants, typing and well-formedness constraints.
Guardrails:
L-*MUST NOT (i) use RFC deontic keywords as operators, (ii) encode runtime entry predicates (those areA-*), or (iii) assert evidence existence or measurement outcomes (those areE-*). - A if it declares a gate predicate: when a named action or application is admitted under its governing rule (“admissible iff …”). State the condition as a predicate; a duty to satisfy or enforce it is a separate D claim.
Guardrails:
A-*SHOULD be written in predicate form and MUST NOT (i) use RFC deontic keywords as if it were an agent obligation, (ii) claim that evidence carriers exist (that isE-*), or (iii) assign responsibility or enforcement (that isD-*). (Do not confuse this withSignature.Applicability: applicability scopes intended meaning and intended use; it is not a runtime entry gate.) - D if the atomic statement states either a generic prescription or an individual duty, recommendation-as-duty, prohibition, or commitment. A permissive sentence enters D only through the Grant or norm row below. Guardrails: a generic claim names the normative episteme and applicable rule content without inventing an individual relation. An individual-duty claim names its actual bearer and separately obtaining A.2.8 commitment. A grant claim instead follows the participant and ground test in the Grant or norm row. A system-role kind or assignment may be a rule ground but is neither bearer nor deontic relation. Writing a claim alone does not make its object obtain.
- E if it reports an actual occurrence, evaluated finding, observed condition or evidence support under §5.4. A claim stating the normative content or obtaining duty or grant itself follows D; an evaluation or occurrence concerning it has its separate E claim.
Predicate-specific minimum: name the
E-*predicate and object, then the actual work, evaluation, or observation, scope/window, comparison frame, and other settling conditions that this predicate needs. Add an evidence or source-use relation when the receiving use needs that support; identify a carrier, schema, viewpoint or consumer only when that item matters to the use. Guardrails:E-*SHOULD NOT use RFC deontic keywords and MUST NOT hide a gate predicate (that isA-*). A reference toD-*follows §6.4: identify the evidence target or normative evaluation input, then establish the E result under its own predicate. (If the source sentence is “Role SHALL measure, retain, or expose …”, first decide whether it is a generic prescription about a system-role kind or a claim about one actual bearer. Classify either as D, but assert an individual commitment only on the second route.)
Step 3 — Triangle decomposition. Recover the observability clause's predicate and modality under §6.3. Use the A/D/E triangle only when the source states an entry condition, a generic prescription or individual duty, and an actual observation or result:
- A: the condition for the named action or application to be admitted,
- D → A: which policy prescribes keeping or enforcing the predicate, or which actual bearer has that separately instituted duty; any responsibility relation is stated separately under its direct domain predicate
- E → A: the actual observation or result and, when needed, the evidence or traces used to adjudicate the predicate.
A requirement to produce or retain evidence stays in D. Preserve an expectation or plan without inventing an actual E result.
Permission-word branch (use only when the sentence sounds permissive). Choose the row by the job the sentence performs, not by the word may, approved, authorized, or permitted.
Choose one row. If one sentence answers two questions, split it before classification. If the sentence is not permission-like, do not use this branch. The branch classifies claims and selects existing subject patterns; it creates no permission result umbrella. Use the filled case in §8.4.5.4 when a concrete model is needed; point back to that case rather than adding another pattern list.
Guideline. Keep the gate predicate separate from the observations and results used to evaluate it. Write the predicate in A-*; state an actual observation or result in E-* and reference the gate when the result concerns its application (E → A).
An A-* predicate may consume a separately established result under §5.2; express a material dependency by reference under §6.1. That reference does not establish the result or a gate decision.
Step 4 — Link by ID or canonical location. Apply the cross-quadrant restrictions in §6.4, including its informative-note exception for L references to A/D/E. Same-quadrant references remain available.
Common link motifs (informative). Boundary rewrites use D→A, E→A, D→E, A/E→L, and D→L; A→D/E supplies a stated gate input, while E→D identifies an evidence target or normative evaluation input under §6.4.
Step 5 — Bind references (minimal A.7 discipline).
-
Place L claims in
Signature.Laws(and mechanism-local semantic laws if present). Keep A claims in the canonical source of their governing admission rule: mechanism applications useMechanism.AdmissibilityConditions; A.21 gates use the applicable profile rule. -
Bind a generic D claim to its normative episteme and applicable rule content.
Bind an individual-duty D claim to its actual duty-bearing System or separately governed party and
U.Commitment; cite an assignment only when the constitutive rule uses it as a ground.State responsibility and authority, when claimed, through their own admitted direct relations or missing governors. Prefer ID or canonical-location references rather than restating
L-*orA-*content. -
Bind each E claim first to its predicate/object and to the actual work, evaluation, observation, scope/window, comparison frame, and other conditions that settle that predicate. Add a carrier/schema, evidence or source-use relation, viewpoint, and consumer only when a receiving reliance decision depends on them; a claim about a carrier's own existence or condition names the carrier as its object.
Optional drift-control. Add each L/A/D/E-classified claim verbatim to a Claim Register row (A.6.B:7) with its canonical location and references when this helps maintain faithful faces.
Step 6 — Recompose into readable text. Select the source claims and supporting detail needed for the receiving question under §4.4. Include only the claim classes present in the source. Use separate Tech and Plain forms when their readers need them; both may also serve as a teaching aid.
- Tech recomposition: a short L/A/D/E-classified claim bundle listing the present claims and their ID or canonical-location references.
- Plain recomposition: a one-paragraph narrative that summarizes the bundle and cites its claims (no new semantics). If you need a new constraint, add a new atomic L/A/D/E-classified claim to the canonical source before publishing it in Plain.
Anti-pattern (quick)
- AP-1 Unestablished operational-result guarantees. An asserted operational
result lacks the actual Work, evaluation, or observation needed to settle it.
If the guarantee's L/A/D/E meaning is ambiguous, use
A.6.C:4.3to recover it. - AP-2 Unresolved duty bearer. “The API promises” is used for an individual duty without a recoverable bearer and independently obtaining commitment; use A.6.C when the intended meaning remains ambiguous.
- AP-3 Gate-as-evidence. Treating the gate predicate (A) as if it were an observation (E).
- AP-4 Gate-as-law. Entry predicates as signature “laws or definitions” (L) instead of
A-*. - AP-5 Unresolved qualifier. “Fast”, “secure”, “approved” or “aligned” leaves the relevant predicate, criterion or relation unrecoverable.
- AP-6 Paraphrase drift. Restating L/A content in D or E with changed meaning (instead of citing by ID or canonical location).
- AP-7 Deontics in predicates. RFC keywords (“MUST, SHALL, and related RFC keywords”) used as operators inside
L-*orA-*predicates (should beD-*that referencesL-*/A-*). - AP-8 View-fork semantics. Recomposition/face text introduces new
L/A/D/Emeaning not present in the L/A/D/E-classified claim set (violates “no new semantics” discipline). - AP-9 Applicability-as-gate. Using
Signature.Applicability(intended use) as a substitute forA-*runtime admission predicates.
Example 1 — Software engineering (SLO-ish API latency)
Draft sentence (non-conformant)
“This API guarantees p95 latency < 200ms.”
Atomize + Classify (L/A/D/E)
The draft leaves open whether guarantees states a target, an obtaining duty or an observed result. The author first recovers the receiving question: the service reader wants to know what the dated evaluation established about latency.
Recover the measurement definition, admitted operating envelope, actual evaluation and evidence support from the named sources. These are additional premises of this constructed case; the draft alone leaves them unresolved.
Explain the dated measurement. Under steps 2–3 of §4.4, the observed value requires its computation meaning, operating conditions and actual basis. The author therefore selects these claims:
L-API-01 (Definition).
p95_latency(window W, population P, unit U, method M) is defined as … (formal measurement definition).
(Lives in Signature.Laws or a referenced measurement definition pack.)
A-API-01 (Gate predicate: admissibility).
In this expanded case, the evaluation mechanism admits assessment of “p95 < 200ms” only under its declared load profile, deployment region, sampling method and window. Its entry predicate is:
AdmissibleLatencyClaim := (region=US) ∧ (concurrency≤X) ∧ (payload≤Y) ∧ (W=5m) ∧ (M=HDRHistogram@v…) ∧ (P=requests that match filter F)
(References L-API-01 for definition.)
E-API-01 (Evidence / carriers).
For LatencyEvaluation-T1 over Γ_time=[t1..t2], carriers TraceBatch-T1, Histogram-H1, DashboardSnapshot-D1, and SamplingConfiguration-S1 were produced or observed under the operating and sampling conditions in A-API-01, using the metric and computation definition in L-API-01. An A.10 evidence-provenance path links those carriers to LatencyEvaluation-T1 and its LatencyResult-T1.
(References A-API-01 and L-API-01 for the operating conditions and metric definition.)
E-API-02 (Observed value claim).
For interval Γ_time = [t1..t2] under conditions pinned to A-API-01 and using carriers in E-API-01, LatencyEvaluation-T1 produced LatencyResult-T1 with observed p95_latency = 173ms (computed per L-API-01).
(References A-API-01, L-API-01 and E-API-01.)
Return to the measurement question. The author writes: “During [t1..t2], the observed p95 latency was 173ms under the operating and sampling conditions in A-API-01, using the definition in L-API-01 and the evaluation evidence in E-API-01 (E-API-02).”
This connects the value to the conditions under which the reader can interpret it. The endpoint declaration and duty bearers do not change this bounded measurement answer. If the reader asks about another region or sampling method, return to the applicability of A-API-01 and the basis of the corresponding evaluation.
Changed question: explain the service assurance arrangement. The reader now needs the interface being covered, who owes the latency performance, who must publish incident notes and how the supporting evidence remains available. The author recovers the declared interface and the separately obtaining commitments. Those premises select the following additional claims; their inclusion follows the new question:
L-API-02 (Interface signature). The API endpoints and parameters are as declared (including parameter passing discipline / units). (Signature-level structure.)
D-API-01 (Commitment).
Admitted service-maintaining system ServiceOperations-A is the duty bearer of separately obtaining LatencyCommitment-API-01 : U.Commitment; under that commitment it SHALL meet p95_latency < 200ms when A-API-01 holds, adjudicated per L-API-01 using the carriers and observation conditions in E-API-01.
(References L-API-01 and A-API-01 by ID; does not restate them.)
D-API-02 (Operational duty).
Admitted operations system SRE-A is the duty bearer of separately obtaining IncidentNoteCommitment-API-02 : U.Commitment; it SHALL publish incident notes when LatencyCommitment-API-01 is violated and SHALL avoid claiming compliance outside A-API-01.
(References D-API-01 and A-API-01 by ID.)
D-API-03 (Duty-to-evidence linkage).
Admitted telemetry-maintaining system TelemetryOperations-A is the duty bearer of separately obtaining TelemetryRetentionCommitment-API-03 : U.Commitment; it SHALL retain or expose the carriers referenced in E-API-01 for the audit window required by policy.
(References E-API-01 by ID.)
Triangle decomposition
For that assurance question, the author uses §6 to connect the declared condition, the duties and the observations. Each link explains one dependency of the assurance account:
- A-API-01 is “the predicate”.
- D-API-01 → A-API-01 states the commitment under the gate or envelope.
- E-API-01 → A-API-01 binds adjudication (carriers used to decide the gate or commitment).
- D-API-03 → E-API-01 expresses retention and exposure obligations for those carriers.
Readable recomposition
The broader assurance question uses the following selection. The earlier measurement answer remains sufficient for its narrower question. A changed commitment requires reconsidering the duty and compliance conclusion while retaining an applicable measurement and its grounds.
Tech recomposition (L/A/D/E-classified claim bundle, short):
L-API-02identifies the covered API endpoints and parameters.L-API-01defines p95 latency computation.A-API-01specifies when the latency claim is admissible.D-API-01states the commitment under that envelope.E-API-01lists adjudicable carriers and conditions used to adjudicateA-API-01.D-API-02states the operational incident-note duties.D-API-03states the retention and exposure duties for carriers inE-API-01.E-API-02reports observed performance underA-API-01forΓ_time=[t1..t2].
Plain recomposition (one paragraph, readable):
“For the API endpoints and parameters declared in L-API-02, the latency target uses the p95 definition in L-API-01, and the mechanism admits its evaluation only under operating envelope A-API-01. ServiceOperations-A has the latency duty stated in D-API-01. Adjudication uses the telemetry carriers listed in E-API-01; TelemetryOperations-A has the retention duty in D-API-03, and SRE-A has the incident-note duty in D-API-02. Under that envelope, the observed p95 over Γ_time=[t1..t2] was 173ms (E-API-02).”
Example 2 — Mechanical engineering (fit / coaxiality)
Draft sentence (non-conformant)
“This fit ensures coaxiality.”
Atomize + Classify
First recover which assertion ensures is meant to express. In this constructed case, a reader initially needs to interpret the geometric requirement at the shaft–bushing boundary. The author obtains the declared datum, tolerance and measurement convention, then uses steps 2–3 of §4.4 to select the two definitions that make that requirement interpretable:
L-FIT-01 (Definition).
coaxiality is defined relative to a declared base axis and measurement method (datum scheme, instrument, tolerance zone).
(Truth-conditional: “what it means”.)
L-FIT-02 (Interface and boundary structure). The boundary relation involves shaft, bushing, datum axis, tolerance class, temperature window, assembly procedure class. (Signature-level arity recovery / slots.)
Return to the interpretation question. The author writes: “Interpret the coaxiality requirement for the shaft–bushing boundary using its declared datum scheme, measurement method and tolerance zone (L-FIT-01), with the participants and applicable temperature and assembly conditions in L-FIT-02.” The reader can now locate what the geometric requirement means. A measured claim about a particular lot needs a further answer.
Changed question: determine what was established for lot L123. The author obtains the evaluation rule and the dated measurement facts. The admissible process envelope and actual evaluation connect the geometric meaning to this lot. Their source recovery supplies the next three claims:
A-FIT-01 (Gate predicate). In this expanded case, the evaluation mechanism admits assessment of the coaxiality claim only when manufacturing and assembly satisfy the declared process envelope: material batch, temperature window, tool calibration validity, surface finish class and alignment procedure version. (Gate predicate; can be checked using evidence, but is not itself evidence.)
E-FIT-01 (Evidence carriers).
For CoaxialityEvaluation-L123 over lot L123 and Γ_time=[t1..t2], carriers CMMReport-L123, CalibrationCertificate-C7, AssemblyLog-L123, TemperatureTrace-L123, and DatumSchemePin-D4 were produced or observed. An A.10 evidence-provenance path links those carriers to CoaxialityEvaluation-L123 and its CoaxialityResult-L123.
(References A-FIT-01 and L-FIT-01; avoids RFC deontics.)
E-FIT-02 (Observed).
For lot L123 and window Γ_time=[t1..t2], under conditions pinned to A-FIT-01 and using carriers in E-FIT-01, CoaxialityEvaluation-L123 produced CoaxialityResult-L123: measured coaxiality was within tolerance zone T (interpreted per L-FIT-01).
(References A-FIT-01, L-FIT-01, and E-FIT-01.)
The resulting account states: “For lot L123 during [t1..t2], the evaluation under A-FIT-01 found coaxiality within tolerance zone T, interpreted through L-FIT-01 and supported by the carriers in E-FIT-01 (E-FIT-02).”
If the datum scheme changes, the author reopens the interpretation and fitness of the measurement for that scheme. The earlier finding retains its stated datum and conditions.
Further question: explain the production and evidence duties. A reader arranging release and later reliance also needs to know who is bound to maintain the process envelope and retain its evidence. Recovering the separately obtaining commitments supplies these additional claims:
D-FIT-01 (Duty).
Admitted production-engineering system ProcessEngineer-A is the duty bearer of separately obtaining ProcessEnvelopeCommitment-FIT-01 : U.Commitment; it SHALL ensure A-FIT-01 holds for the production lot and SHALL not release the lot for use when A-FIT-01 is false.
(References A-FIT-01.)
D-FIT-02 (Duty-to-evidence linkage).
Admitted quality-engineering system QualityEngineer-A is the duty bearer of separately obtaining FitEvidenceRetentionCommitment-02 : U.Commitment; it SHALL retain or expose the carriers referenced in E-FIT-01 for the production lot.
(References E-FIT-01 by ID.)
Readable recomposition
For this broader question the author connects the definition, admissibility, duties and observation. This selection lets the reader distinguish what the lot evaluation established from what each duty requires.
Tech bundle:
- Meaning of coaxiality:
L-FIT-01. - Boundary arity and participants:
L-FIT-02. - When the claim is admissible:
A-FIT-01. - Who has the process-envelope duty:
ProcessEngineer-AunderD-FIT-01. - What we observe and keep as carriers:
E-FIT-01and measured outcomeE-FIT-02(with retention dutyD-FIT-02).
Plain paragraph:
“In this expanded case, ‘ensures coaxiality’ is made precise by fixing the definition and datum scheme (L-FIT-01) and by making the boundary participants explicit (L-FIT-02). The mechanism admits this coaxiality evaluation only under the declared manufacturing and assembly envelope (A-FIT-01). ProcessEngineer-A has the process-envelope duty stated in D-FIT-01. QualityEngineer-A has the evidence-retention duty in D-FIT-02. Compliance is adjudicated using the measurement and process carriers listed in E-FIT-01; for lot L123 over Γ_time=[t1..t2], the observed coaxiality was within tolerance E-FIT-02.”
Example 3 — Management (project “approved or aligned”)
Draft sentence (non-conformant)
“The project is approved.”
Atomize + Classify
With only the draft, ask which approval is claimed and which subsequent action the reader needs to decide. Here the question is whether the project may start execution. Recover the sponsor-approval definition, entry predicate, four actual check-application results and evidence path from the named sources. These additional premises let the author connect the prerequisite meanings to a current entry decision.
The separately obtaining coordinator duty is needed for the broader question of who is bound to maintain this arrangement; it is also supplied in the constructed case below.
L-PRJ-01 (Definition).
For this case, the project-entry policy defines RequiredProjectApproval(project) as sponsor sign-off on the identified project. Risk-review completion, budget availability and staffing are separate prerequisites.
A-PRJ-01 (Gate predicate: stage entry).
For starting execution work, ExecutionAdmissible(project) holds iff RequiredProjectApproval(project) and the required prerequisites are satisfied: risk review completed, budget line exists and key roles staffed.
(This is the “may start work” entry predicate; it references L-PRJ-01 for what counts as approvals. If “approved” is meant as permission rather than gate evidence, use the permission-word branch in §8.4.1. An approval registry entry or evidence carrier alone remains source/display evidence and is not a grant.)
D-PRJ-01 (Duty).
Admitted project-coordination system ProjectCoordinator-A is the duty bearer of separately obtaining ProjectEntryCommitment-PRJ-01 : U.Commitment; it SHALL not initiate execution unless A-PRJ-01 holds, SHALL keep the approval registry current, and SHALL retain or expose the evidence carriers referenced in E-PRJ-02.
(References A-PRJ-01 and E-PRJ-02 by ID.)
E-PRJ-01 (Gate decision result).
At Γ_time=snapshot(t), ProjectEntryGateResult-P-t : GateDecisionResult has gateRef=ProjectEntryGate-P, decisionSubjectRef=ProjectEntryClaim-P-t, boundedActionRef=StartExecution-P, and profileApplicationRef=ProjectEntryProfileApplication-P-t.
That application of ProjectEntryProfile-v3 uses the complete required set {ApprovalCheck-P-t, RiskReviewCheck-P-t, BudgetCheck-P-t, StaffingCheck-P-t} : GateCheckApplicationResult[]; each application reports its checked subject and criterion, has sourceOutcome=satisfied, and maps to pass.
The result records decisionValue=pass, action consequence “start StartExecution-P within the admitted project-entry window”, the project-entry scope and window, and recheck on any changed approval, risk-review, budget, staffing, profile, scope, or window.
(This E-* result applies the inputs named by A-PRJ-01; it is neither the A-* predicate nor performed execution Work.)
E-PRJ-02 (Evidence for reliance).
For reliance on E-PRJ-01, the observed carrier set is {DecisionRecord-R7, MeetingMinutes-M3, BudgetLine-B4, StaffingAssignments-S2, GateChecklistSnapshot-G9}. An A.10 evidence-provenance path links those carriers to the four GateCheckApplicationResult values and ProjectEntryGateResult-P-t. GateChecklistSnapshot-G9 displays the result; its presence alone establishes neither a check result nor the gate decision.
(References A-PRJ-01 and E-PRJ-01; avoids RFC deontics.)
Readable recomposition
Answer the entry question. The author uses L-PRJ-01 and A-PRJ-01 to interpret the prerequisites, E-PRJ-01 for the decision and E-PRJ-02 for the support needed before reliance.
The answer is: “At snapshot t, the project-entry decision is pass, allowing StartExecution-P within the stated window (E-PRJ-01, supported by E-PRJ-02). Recheck when a prerequisite or the decision's profile, scope or window changes.”
A changed budget check returns the reader to the affected admission decision. The definition of sponsor approval remains usable.
Explain the wider arrangement when requested. Adding D-PRJ-01 answers who has the project-entry and registry-maintenance duties. The following recomposition addresses that wider question:
Tech bundle:
- The required sponsor approval is defined by
L-PRJ-01; risk review, budget and staffing remain separate prerequisites. - “May start execution” is a gate predicate:
A-PRJ-01. ProjectCoordinator-A's project-entry duty:D-PRJ-01.- The A.21 gate result is
E-PRJ-01; its bounded A.10 evidence support isE-PRJ-02.
Plain paragraph:
“In this expanded case, the required sponsor approval has the meaning defined in L-PRJ-01. Together with the separate risk-review, budget and staffing prerequisites, it supplies the inputs to the entry predicate A-PRJ-01. ProjectCoordinator-A has the project-entry and registry-maintenance duties stated in D-PRJ-01. At snapshot t, the current A.21 profile application maps every required check-application result to pass; E-PRJ-01 records decisionValue=pass with the action consequence ‘start StartExecution-P within the stated window’, and E-PRJ-02 supplies the evidence path for reliance on that result.”
Filled permission case (each sentence classified)
Apply §4.4 to each receiving question in this case. To explain the current grant, connect its instituting basis E-CAL-01 to D-CAL-01. For an entry decision, also recover the entry predicate and the actual decision with its applicable inputs. A question about whether the technician used the grant selects E-CAL-02–03; later compliance and renewed entry require their own findings below. The detailed permission branch in §8.4.1 explains these selections. Preserve the distinct claims so a later question can use its own grounds.
E-CAL-01 (Instituting communicative Work). Admitted system MaintenanceCoordinator-A performed dated CalibrationGrantAct-17 : U.SpeechAct under MaintenanceCoordinator-A@DayShift; that obtaining assignment has the system as holder and covers the act. In this filled case, CalibrationGrantPolicy-v4 does not require a separate authority relation, so none is asserted. The assignment supplies no authority and performs no act. CalibrationGrantAct-17 satisfies the policy in PlantCalibrationContext and is the instituting Work.
A policy variant that does require grant authority must cite one obtaining authority relation under its direct predicate or stop at missing-governor[grant authority].
D-CAL-01 (Grant position). MaintenanceCalibrationGrant-17 : GrantedPermissionRelation@Context, instituted by CalibrationGrantAct-17—the speech act stated in E-CAL-01—permits beneficiary MaintenanceTechnicianSystemRole to run CalibrationProcedure-v3 in Zone 8 during ServiceWindow-17. CalibrationGrantPolicy-v4 remains current, the grant covers that system-role kind, procedure, zone, and window, and no valid revocation or supersession has ended this occurrence; this D-* claim records the grant but does not institute it.
A-CAL-01 (Gate predicate). CalibrationEntryAdmissible(plan, checkTime) holds only if MaintenanceCalibrationGrant-17 is current for the plan's beneficiary, action, zone, and time and no applicable permission/norm conflict finding is unresolved. The predicate takes those inputs; it creates neither the grant, a conflict result, nor an actual gate decision.
E-CAL-02 (Actual Work and actor). Through its A.13 core, admitted system Tech-17 is the performer for this case under obtaining assignment Tech-17@Shift-B, whose holder is Tech-17 and whose extent covers the early part of ServiceWindow-17. A.15.1 independently admits dated CalibrationWork-17B : U.Work from that performer, its Method, extent, and containing-System facts.
Because this filled case expressly claims precise assignment-bound attribution, F.6 separately relates CalibrationWork-17B to that same assignment. The assignment neither acts nor identifies the performer.
If F.6 is not established, the under-assignment claim remains unresolved; if the relation is shown not to obtain, that claim is refuted. Neither alone overturns the independently admitted Work. If the attribution finding questions a premise consumed by Work admission, recheck that premise and the dependent claims.
E-CAL-03 (Optional exercise claim). Because this case asks whether the grant was used, CalibrationExercise-17B : PermissionExerciseRelation@Context connects CalibrationWork-17B to MaintenanceCalibrationGrant-17: the Work instantiates CalibrationProcedure-v3; Tech-17@Shift-B is an assignment occurrence whose declared species uses MaintenanceTechnicianSystemRoleKindDomain as its assigned-kind domain, and the occurrence supplies MaintenanceTechnicianSystemRole as the value admitted by that domain; and the Work occurs in Zone 8 within ServiceWindow-17 while the grant is current. If the action or beneficiary test failed, this exercise relation would not obtain.
D-CAL-02 (Exercise non-use boundary). The authoring rule says to add E-CAL-03 only when the reader needs to know whether the grant was exercised; otherwise stop with the separately named grant and Work. This is a generic prescription for boundary text, not a claim that one author bears an individual U.Commitment.
E-CAL-04 (Later non-violation finding). Through its A.13 core, admitted system ComplianceEvaluator-4 is the performer under obtaining assignment ComplianceEvaluator-4@QualityShift. A.15.1 independently admits dated CalibrationComplianceEvaluation-17B : U.Work; because this finding expressly preserves precise assignment-bound attribution, F.6 separately relates that Work to the same assignment.
The Work checked CalibrationWork-17B against current PlantCalibrationNormativeFrame-17, complete enough for this technician, procedure, zone, and evaluation window, and returned CalibrationNonViolation-17B : NonViolationFinding@Context(result=nonViolating). A stale or insufficient frame would return unresolved.
If F.6 is not established, the attribution remains unresolved; if the relation is shown not to obtain, that attribution claim is refuted. Missing or failed attribution alone does not overturn independently admitted Work or an independently established evaluation result. If the attribution finding questions a premise used for Work admission or the evaluation, recheck that premise and the dependent claims.
E-CAL-05 (Evidence for reliance). An A.10 evidence-provenance path links the CalibrationNonViolation-17B finding to CalibrationComplianceEvaluation-17B, ComplianceEvaluator-4@QualityShift, CalibrationRunLog-17B, the log's source and currentness relations, and the bounded audit context. The path supports reliance on the finding; the log, assignment, and path do not perform the evaluation or create its result.
E-CAL-06 (Unresolved conflict). After CalibrationWork-17B and its evaluation, Zone8EntryProhibition-17 becomes current for the same beneficiary, action, zone, and the remaining service window, including the calibration action specified by CalibrationWorkPlan-17C; no applicable rule selects an outcome and no authorized dated decision Work with a current resolution result exists. CalibrationConflict-17 : PermissionNormConflictFinding@Context therefore remains unresolved.
E-CAL-07 (Source/display fact). SignedGrantRecord-17 and GreenPermitTile-17 are visible carriers in this case; their presence is an observed source/display claim only.
E-CAL-08 (Gate decision result). At the later entry check, CalibrationEntryResult-17C : GateDecisionResult has gateRef=CalibrationEntryGate-17, decisionSubjectRef=CalibrationWorkPlan-17C, boundedActionRef=StartCalibrationProcedure-v3-in-Zone8-17C, and profileApplicationRef=CalibrationEntryProfileApplication-17C.
The current profile application uses the complete required set {CalibrationGrantCurrentCheck-17C, CalibrationConflictResolvedCheck-17C} : GateCheckApplicationResult[]: the current-grant application maps to pass, while the CalibrationConflict-17=unresolved source outcome maps to block.
The result records decisionValue=block, action consequence “hold CalibrationWorkPlan-17C outside entry”, the remaining Zone 8 service scope and window, and recheck when the grant, conflict result, profile, scope, or window changes. It neither resolves the conflict nor revokes MaintenanceCalibrationGrant-17.
L-CAL-01 (Tempting wrong classification, rejected). “The visible permit is D, so the grant exists, the Work exercised it, and the Work was non-violating” is not one atomic claim and is false as a classification shortcut. The carrier observation is E-CAL-07; the grant, exercise, evaluation finding, and E-CAL-08 gate result remain the separately classified claims above.
A compact recomposition aid
Select the source claims needed for the receiving question through §4.4. Cite claim IDs or canonical locations. For a measurement account, connect the value to its definition, conditions and actual basis; for an entry answer, connect the entry rule to its evaluated inputs and current decision. Use the broader forms below when the question also needs the normative arrangement and its evidence. Use separate Tech and Plain forms when their readers need them.
Tech register
“This boundary claim is defined by L-… and applies only under A-…. D-… states either the generic prescription or the separately instituted duty of [actual bearer]. E-… states the observed or evaluated result for
Γ_time=…; add its evidence support when the receiving use needs it.”
Plain register
“We mean [short label] in the sense of L-…, and use it only when A-… holds. D-… either states what the named policy requires or, when an individual duty was separately instituted, names its actual bearer. E-… states the observed or evaluated result for the declared interval; add its evidence support when the receiving use needs it. If responsibility is also claimed, cite its direct relation separately.”
A.6.B:9 — Bias‑Annotation
Scope: Universal for boundary descriptions.
- Arch bias: favors explicit separation and explicit references; mitigated by allowing narrative faces while keeping commitments classified and referenced by ID or canonical location.
- Gov bias: makes actual duty bearers and duties explicit (D) and auditability explicit (E); mitigated by keeping evidence conceptual and carrier-referenced rather than tool-specific. Responsibility, when claimed, remains a separate direct relation.
- Ontological and epistemic bias: distinguishes the EntityOfConcern, claim-bearing episteme and carrier, and requires the actual basis for work, evaluation or observation claims. Cross-quadrant references preserve their connections in a readable account.
A.6.B:10 — Conformance Checklist
Common Anti‑Patterns and How to Avoid Them
A.6.B:12 — Consequences
A.6.B:13 — Rationale
Boundary changes need different comparisons. Changing an admission condition affects which applications can enter; changing a normative rule affects what is required or granted; changing an implementation can affect the result while leaving both declarations intact. The four claim jobs keep these questions and their connections recoverable. A.6:4.7 explains how to use them for a change decision.
The classification is an authoring convention, with one job assigned to each atomic claim. Modality and adjudication help recover that job, but neither supplies a two-way partition of every claim. In particular, A predicates are declarations, and an individual D claim requires actual constitutive grounds. The practical benefit comes from exposing the different grounds and preserving their dependencies across uses and publication faces.
For a small boundary, ordinary atomic prose and its existing contract or policy can be sufficient. Claim IDs, a register and additional faces earn their cost when several uses need to refer to the same content or follow a consequential change. Keep the direct subject conditions available in either form.
A.6.B:14 — Source contributions
A.6:11 gives the source contributions and their limits. Effects and handlers distinguish declared operations from handler semantics; contract and behavioral-subtyping work supplies preservation questions; session types supply protocol-specific conditions. ISO/IEC/IEEE 42010 supports concern-oriented descriptions and correspondences. OpenTelemetry and SRE distinguish the observations available from the service property being examined; Cedar gives an explicit rule-evaluation and decision construction.
FPF uses these contributions to organize boundary claims. The four jobs, their FPF placements and §6.4's dependency rules are the construction explained here. In particular, provider duties require their governing normative source or individual instituting basis, and replayable evidence-provenance accounts use A.10. A source's typing or telemetry guarantees retain their own stated scope.
A.6.B:15 — Relations
- Used by A.6 and A.6.C: supplies the canonical matrix and cross-quadrant link discipline. Both consumers classify each atomic claim by predicate and adjudication, keep the claim episteme separate from its EntityOfConcern, and use the §8.4.1 branch only when permission wording is live.
- Constrains A.6.0 (
U.Signature): enforces thatL-*laws are truth‑conditional and do not include admissibility predicates. - Constrains A.6.1 (
U.Mechanism): places admissibility inAdmissibilityConditions(A-*) and classifies actual results and evidence claims asE-*, adding carrier references when their use requires them. - Requires A.7: identifies each claim's EntityOfConcern separately from the episteme carrying it. The concern may itself be a Description episteme or publication carrier.
- Interacts with MVPK/E.17: faces are projections that cite L/A/D/E-classified claims and introduce no new semantics. When the permission-word branch is selected, its row names the subject pattern and obtaining or failure test; A.6.B only classifies the statement, and wording or a carrier alone does not make the referenced object obtain.
Probe-coupled boundary claim classification
When boundary text says that an interaction changes the state represented by its output, identify the interaction, the changed state, and the receiving use, then classify the atomic claims through the same L/A/D/E square. Such interactions may include asking a question, measuring or intervening through a metric, reading a dashboard, conducting a workshop, exporting through a Bridge, or making an API read.
Action classification:
- Copy the boundary sentence being used for a decision.
- Split it into its atomic claims before judging it, retaining only the classes present in the source: definition or law, runtime admissibility, generic prescription, individual duty or grant, work effect or evaluated result, and any separate evidence-support claim.
- Give each atomic claim its quadrant and any identifier required by a later reference.
- Apply
A.6.Pwhen a relation or its participants remain unclear; useF.18only when recovered terms need durable names. Use §5.4's evidence-use route for needed support,B.3for a named assurance question,C.16for measurement, andF.9for a Bridge question. UseC.26.1for the residual probe-coupled question only when the interaction participates in the represented state and its output is being used as a passive read or export despite that decision-relevant effect. - Use a Claim Register when the claim set needs persistent reuse, dispute resolution or cross-face citation; otherwise keep the atomic prose.
For a local working note, atomize the sentence mentally and write one or more atomic L/A/D/E-classified sentences, preserving every source claim. One sentence suffices only when one logical job remains. Use the Claim Register when the claim set must survive reuse or dispute.
Useful outputs:
- a Claim Register when persistent reuse, dispute resolution or cross-face citation needs it;
- one or more atomic L/A/D/E-classified sentences preserving every source claim for a local working note;
- an ordinary A.6.B L/A/D/E-classified claim set when no probe-coupled state-reading question remains;
- the
C.26.1:4.2decision and finish result for a residual probe-coupled question that meets the activation condition above; - the evidence-support, assurance, measurement, or Bridge result or continuation
required by
A.10,B.3,C.16, orF.9for the corresponding current question.
Identify the interaction and its receiving use, split and classify the claims,
then apply the C.26.1 activation condition above to any remaining question.
A.6.B:End
A.6.C — Contract Unpacking for Boundaries
Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) Placement: Part A → A.6 Signature Stack & Boundary Discipline Builds on: A.6 (stack + classification intent), A.6.B (L/A/D/E), A.6.P:4.11a (service/access subject-pattern recovery), A.7 (EntityOfConcern, Description episteme, and carrier separation), A.2.3 (
U.PromiseContent), A.2.8 (U.Commitment), A.2.8.PER (strong/weak permission, exercise, and conflict), A.2.9 (U.SpeechAct), A.15.1 (U.Work), A.10 and B.3 (evidence and assurance use), E.10 (L-SERVandLEX-BUNDLE), E.17 (MVPK “no new semantics” faces), F.12 (service acceptance and evidence discipline) Naming boundary: F.18 may provide durable names for recovered terms when naming is current; it does not define or constrain the promise-content, speech-act, commitment, permission, work, evidence, or boundary ontology. Vocabulary boundary: “Contract”, “SLA” and “guarantee” are Plain-level source cues. The four questions unpack their meaning without defining a newContractkind. Purpose (one line): Resolve the meaning of boundary contract language and decide what the governing terms and acts of the participants settle. Use the A.6.B Claim Register when the receiving use needs a record under §4.5.
Use this when. Use A.6.C when words such as contract, promise, guarantee, SLA, or interface agreement leave a consequential ambiguity about what was promised, instituted, governed, performed, produced, delivered, accepted, or evidenced. Also use it when several clear statements and acts have to be connected to decide whether an order is complete or who still owes work.
First useful move. For a wording problem, rewrite the relevant assertion to identify its subject, predicate, operands and governing source. Keep the participants, values and conditions on which the assertion depends. For a decision about an order, begin with the undertaking in force and the facts that could change the recipient's decision. Use the corresponding questions in §4.1.
What changes in practice. Familiar contract language can remain in Plain prose while technical and normative claims become classifiable under A.6.B and adjudicable through their direct sources.
Ordinary non-use boundary. Clear local contract wording with no consequential ambiguity needs no unpacking record. A one-off repair may end in the repaired atomic prose; create or extend the Claim Register only when stable reuse, decision, audit, dispute, or cross-face projection needs it.
A.6.C:1 — Problem frame
Boundary descriptions frequently use “contract” as shorthand for “the thing that governs the interaction”. That shorthand collapses four practical questions and the separately governed objects needed to answer them:
- What was promised? — the promise content, if any,
- What was said, published, or instituted? — the speech-act Work, descriptions, publication occurrences/forms/carriers, and any separately governed institutional effect,
- What governance or permission-looking claim exists? — the one atomic norm, grant, gate, exercise, evaluation, conflict, or source claim selected by its job,
- What happened, what followed, and what supports reliance? — dated Work, each separate result or delivery claim, and each evidence claim.
When these questions are answered with one undifferentiated object or row, authors can conflate a semantic guarantee with an undertaking, attribute a dated act to its description instead of its performer, encode runtime gates as if they were internal laws, or treat observability as a property of text rather than of carriers and work. A.6 and A.6.B already provide an L/A/D/E claim-classification discipline for boundary claims, but “contract” language remains a recurring entry point for category mistakes.
Service-cluster note (modularity + lexicon). When contract wording appears alongside service, service provider, server, SLA, SLO, or service-level and a relied-on boundary use hides a concrete subject or relation, recover that hidden choice through A.6.P:4.11a while asking the four questions below. Mere co-occurrence does not trigger recovery, and clear, quoted, historical, illustrative, or harmless ordinary wording remains usable. U.PromiseContent is written as promise content, never as bare “service”.
A.6.C makes contract-language usable inside the A.6 stack by providing a canonical unpacking that can be applied to APIs, hardware interfaces, protocols, and socio-technical boundaries.
Non‑goals (to preserve modularity). A.6.C does not:
- define “legal contract” doctrine (offer, acceptance, consideration, jurisdictional enforceability, etc.);
- resolve conflicts across scales or contexts: keep the current grant or prohibition as its own D claim, classify the conflict finding as E through A.6
A6-AW-CONFLICT, and use the mediation predicate and assertion only when mediation is current; - redefine the core meanings of
U.PromiseContent,U.Work,U.SpeechAct,U.Commitment, or theA.2.8.PERresults—it only makes “contract talk” classifiable into those objects or claims. - redefine quadrant semantics (
L/A/D/E) or cross‑quadrant reference rules; those are defined normatively in A.6.B.
A.6.C:2 — Problem
How can an author write (or repair) contract-language so that:
- Act and commitment claims name compatible participants, without mistaking an interface description for the actual interface or its bearer,
- Governance claims are distinguishable from permission-looking gate, exercise, evaluation, conflict, and source claims by the job of each atomic statement rather than by A.2.8.PER membership,
- Operational “guarantees” become adjudicable by recovering the claim, the facts its predicate requires, and the grounds for any receiving reliance; the answer may be a supported result or an unresolved claim with its missing basis,
- Multi-view publication (MVPK faces) does not create a parallel contract object or another canonical claim set by paraphrase drift?
A.6.C:3 — Forces
A.6.C:4 — Solution
Use the four questions to recover the claims made, then classify them through A.6.B. In interpreting a passage, preserve the relations it actually asserts. In deciding what an order has settled, establish the additional connections needed for the decision from the governing terms and the evidence.
A.6.C:4.1 — Four questions for contract-like boundary wording
When unpacking contract-like wording or deciding what the terms and acts together establish, ask the questions that bear on that use. A question may yield zero, one, or several atomic claims. Add corresponding rows only when stable reuse, decision, audit, dispute, or cross-face projection needs the Claim Register; the question itself is not a bundle part or direct-object kind.
-
What was promised?
- The promised value or effect (the promise content) in the intended scope.
- In FPF terms (A.2.3),
U.PromiseContentis promise content, distinct from an execution event or an obtaining individual commitment. - Prose head rule (normative). When referring to
U.PromiseContentin normative prose, authors SHALL use the head phrase promise content (or service offering clause or service promise clause) and SHALL NOT rely on the bare head noun service. If the surrounding text also talks about endpoints, systems, and operations, apply A.6.P:4.11a only when the current relied-on use hides which concrete subject or relation is meant; examples include a service access point, service delivery system, or service-delivery Work occurrence. Mere proximity to those words creates no additional claim or recovery duty. - Recommendation: when commitments, gates, evidence, or MVPK faces need stable citation of the promise content, give it a stable local ID (e.g.,
SVC-*) to prevent paraphrase drift. - Claim-classification discipline: keep meanings and definitions of the promised behavior in L. A generic prescription about that behavior is a separate D claim about its normative source and applicable rule content. If an actual System or separately governed party has that duty, state a separate D claim about the
U.Commitment, plus anyA-*andE-*references needed by that claim.
-
What was said, published, or instituted?
-
Speech-act Work: when the passage asserts a particular communicative act, apply A.2.9 to establish its
U.SpeechAct <: U.Workoccurrence. An ordinary source attribution or publication reference can suffice when no such occurrence claim is needed. -
Description/publication: identify the utterance episteme and any publication occurrence, form, rendering or carrier whose identity changes the current claim or use.
-
A speech act may institute or update a commitment or strong grant only when the context policy recognizes that act type and the subject pattern's obtaining conditions are met.
-
Published utterance descriptions can carry L/A/D/E-classified claims. Identify any actual speech act and institutional effect separately under their subject rules.
-
World-side obtaining rule (normative). The predicates defined in A.2.8 and the cited context policy decide whether a commitment obtains; the predicate defined in A.2.8.PER together with that policy decides whether a strong grant obtains.
For a commitment, use the actual instituting basis required by its constitutive rule: the current A.2.9 path uses an actual
U.SpeechAct; another basis requires a subject pattern that admits it and gives its occurrence rule. A strong grant requires the actual instituting speech act under A.2.8.PER.Preserve the participants, scope/window, current policy, and any revocation or supersession conditions. A Claim Register row, utterance description, publication, carrier, or identifier creates or proves neither relation by itself.
For a commitment, a cited fact is constitutive only when the identified rule makes that fact current and the pattern for that subject supplies its test. Publication or approval may establish a publication/status relation only through that relation's predicate and obtaining facts.
-
Representation and reliance rule (normative). The model MAY assert or rely on a commitment or grant only through a separate atomic claim that identifies the
U.CommitmentorGrantedPermissionRelation@Contextoccurrence and cites its predicate,SubjectPatternLocator, participants, scope/window, and the currentness or evidence required by that use.For a commitment, cite the rule-required actual instituting basis and policy; for a strong grant, cite the actual instituting speech act and policy.
Never infer the relation from
Publish/Approvewording, a document, carrier, or completed-looking record alone.
-
-
What governance or permission-looking claim exists?
-
A generic prescription states what one policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence.
A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8
U.Commitment. Here the normative episteme may be a contract, SLA, protocol, or policy, and the generic claim also states where its rule applies. -
When the model asserts or relies on an individual obligation, recommendation-as-duty, or prohibition, write a separate atomic D claim whose direct object is that separately obtaining
U.Commitment. -
For permission-looking wording, select one A.6
A6-AW-*row. OnlyA6-AW-NORM-GRANTenters D. WithinA6-AW-GATE, an admission predicate for a named action or application enters A and an actual A.21GateDecisionResultenters E; split them into separate atomic claims when both are present. Exercise, weak evaluation, conflict, and observed-source claims enter E when their closing facts are present. Classification under A.2.8.PER alone selects no quadrant. -
Individual-commitment checklist (use only for the individual branch):
- identify one
U.Commitmentoccurrence and the separate D-claim orCommitmentAssertionabout it; - select exactly one actual bearer branch: an admitted
U.Systemor separately governed party; - name non-empty duty referents, any actual counterparties, normalized modality, scope, and validity window;
- cite the current constitutive policy, its individualizing rule, and the actual instituting basis required by that rule;
- cite a system-role assignment only when that rule uses the assignment as an applicability ground—the assignment is neither bearer nor duty; and
- add evidence-claim or carrier references only when the receiving reliance or adjudication needs them.
- identify one
-
Permission-branch pointer: cite the selected
A6-AW-*row, its A.2.8.PER object when applicable, and that atomic claim's quadrant. Preserve the object's own schema, participants, and references; do not reuse the commitment checklist. -
A commitment is not “the spec text”: an utterance description carries the statement, while
U.Commitmentis the separately obtaining relation described by that statement (A.7 and A.2.8).
-
-
What happened, what followed, and what supports reliance?
-
Work: For one dated
W : U.Work, recover each actual performer through A.13 and let A.15.1 independently admit the occurrence from that performer, enacted Method, extent, and containing System.Add an A.2.1 assignment reference and F.6 only when this account or a receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer.
Missing or failed F.6 alone leaves independently admitted Work intact. If the same finding questions a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent claims.
-
Result or consequence: only when the sentence asks for one, select the matching
A.15.1:4.6row—an A.6.1 application/result binding or independently obtainingWorkResultRelation, A.15.PROD production branch, A.3.4 change, evaluation result, subject-specific delivery/transfer relation, or acceptance relation. An absent row stays absent. -
Evidence: for a current evidence-use claim, name the supporting episteme, target claim and conditions required by its direct rule; use A.2.4 for first-use classification. Make the grounds required by any receiving reliance recoverable. Use A.10 when source recovery, provenance, currentness or bounded reliance must remain replayable; identify carriers and observation conditions when they affect the claim or its use.
-
Decide what the commission has settled. Start with the decision someone needs to make. A buyer may be deciding whether to close an order. A supplier may need to know whether a correction is still due. Work from the request, the terms that took effect and the available records. If a counteroffer changed the deliverable, establish whether and when the parties adopted it. An unanswered request can be all that happened.
For each condition on the next action, find what establishes it. For an owed action or result, identify who undertook to do or supply what for whom. Ask whether the same acceptable result could be produced another way and whether anyone is owed that particular performance in its own right. A supplier may commission an expert opinion to prepare its response. The customer may require the opinion as a condition of acceptance, or may have ordered the consultation itself. Look for the term or accepted change establishing each connection. A completed check may enable a later decision by the customer. It settles acceptance itself only if the agreement gives it that effect. Trace any promises between supplier and expert on their own terms. The supplier's need for the opinion can coexist with either customer arrangement. When the composition of the performed Work matters, B.1.5.EW:4.2 distinguishes a constituent action from work that supplies a result used by another. Follow each undertaking only as far as the receiving decision requires.
Establish what counts as delivery and what counts as acceptance. Producing an item, declaring it ready, delivering it, a user learning of it, and a party accepting it can happen at different times. One notice can declare completion in one undertaking and supply the entire deliverable in another. An earlier decision can settle today's inquiry when it covers the result, recipient and conditions now at issue. If the order calls for a fresh decision, establish that it took place. If the order makes receipt at an agreed repository sufficient for acceptance, a receipt identifying the required item and deposit can settle both delivery and acceptance. An order can make acceptance effective on deposit while allowing later objections. Acceptance then holds from deposit and the right to object continues for the stated period. If acceptance instead takes effect at the end of the period unless someone objects, establish that the period elapsed and that no qualifying objection was made. An earlier decision can settle acceptance if the terms also authorise that route.
Determine how the applicable rule combines the contributions. An authorised representative can accept for several recipients. A board's rule may require a quorum and a specified number of votes in favour. A clerk can record the decision the board reached. An order can instead require distinct assents, compatible parts, or a separate delivery to each recipient. Establish the scope of the mandate, the relevant acts and the connection between them that the rule requires. The records may cover different parts or editions when the rule recognises the correspondence. For a conclusion about a class of orders, show why the rule and the combination apply throughout that class, and which facts each order must supply.
Apply the terms to the facts that can be established. If every history consistent with the terms and evidence gives the same answer, and at least one such history is possible, give that answer. If records conflict, check which record governs or whether independent grounds settle the decision. When the conflict remains unresolved and the other grounds do not suffice, leave that conclusion open. If different histories would give different answers, or the conflict prevents a conclusion, identify the fact needed, where to obtain it and when the recipient needs it. A recorded refusal or a missed binding deadline can rule out one route to acceptance. A negative conclusion for the whole order requires grounds covering every route the agreement allows for the date in question. A missing receipt can leave delivery open. An adverse assessment can itself complete an order for an assessment. Determine separately whether correction, payment or further service is due under the corresponding undertaking.
For example, an archive orders a finding aid for two reading rooms. Its acceptance rule requires each room to approve the entries retained for it and both sets to use the same index. The east room accepts its entries in draft 6. The west room accepts its entries in draft 7. Either approval can establish a local decision. Both can establish acceptance of the combined aid if the retained entries are the approved ones and the two sets use the same index, as the order requires. An edit to the index that breaks this condition defeats that combination. If the order instead delegates acceptance of the entire aid to the head archivist, that officer's qualifying decision suffices. The same two room approvals then answer a different question.
A.6.C:4.2 — Classification recipe into A.6.B (L/A/D/E)
After unpacking, classify each atomic statement using the Boundary Norm Square as defined normatively in A.6.B (quadrant semantics + form constraints + cross‑quadrant reference discipline). A.6.C does not redefine L/A/D/E; it applies them to contract-language as follows:
- Promise content and conditions → classify by the claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
L-*in signature laws and definitions). - Recover what “eligible”, “covered” or “valid iff” means. A definition or declared scope remains L; an admission predicate for a named action or application is A; a finding that a particular case meets the conditions is E. A duty concerning those conditions is a separate D claim.
- Put meanings, invariants, and metric definitions for what is promised in L (
- Governance and permission-looking claims → claim-specific quadrant.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
U.Commitmentunder A.2.8; do not use a completed record as the relation. - For authority-looking wording, select one A.6
A6-AW-*row: norm/grant → D, admission predicate → A, and an actual A.21GateDecisionResult, exercise, evaluated finding/conflict, or source observation → E. Split a predicate and an actual gate result into separate atomic claims. Cite the A.2.8.PER object only where that row requires it; the selected subject pattern or kind of direct object does not choose the sentence's quadrant. - If a generic prescription or individual duty requires satisfying or enforcing a gate, its
D-*claim MUST reference the relevantA-*claim by ID or canonical location (D→A). - If reliance on either D branch needs evidence, cite the relevant
E-*claim or evidence-use relation (D→E); for the individual branch, aCommitmentAssertionmay carry that reference.
- Put a generic contract, SLA, protocol, or policy prescription in D as a claim about its normative source and applicable rule content. Put an individual-duty claim in D only when it cites a separately obtaining
- Performed Work → E (did it happen?).
- Result or consequence → E when current (what else happened?).
- Use the one applicable
A.15.1:4.6predicate and subject assertion for the returned value, production, change, evaluation result, delivery/transfer, or acceptance claim; cite the pattern that defines or constrains that claim.
- Use the one applicable
- Evidence → E when relied on (how can the claim be used?).
- State the target claim and the independently established evidence-use or other direct support relation, including its polarity and limits. Use A.2.4 for first-use classification and A.10 when a replayable source-to-use account is needed. Keep the grounds required by the receiving use; identify carriers and observation conditions when they affect that claim or use.
Keyword placement rule (canonical claim set).
Within the canonical L-, A-, D- or E-classified claim set, BCP-14 keywords are statement operators. Classify the claim through A.6.B: a generic prescription or an independently instituted duty, recommendation-as-duty or prohibition enters D. When MAY, OPTIONAL or authority-looking wording is ambiguous, use the A.6 A6-AW-* branch. If its object or meaning remains unresolved, retain it as bounded source wording with that uncertainty; marking it informative does not settle the claim.
A.6.C:4.3 — “Guarantee” disambiguation
When “guarantee” leaves a consequential ambiguity, use the applicable distinction below:
- Semantic guarantee → L (“by definition or invariant”).
- Admission guarantee → A (“this action or application is admissible iff …”).
- Governance guarantee → D (“provider commits or implementer must”).
- Operational claim → E (an actual occurrence, condition or result under its subject predicate). Name Work, evaluation or observation when the claim depends on it. Retain an unresolved claim when required grounds are missing; report a negative result only when the grounds establish it. Qualify evidence support for the receiving use under §4.1, question 4.
If none fits, recover the remaining meaning before classifying it. Mark an aspiration as such only when that is what the source expresses; otherwise keep the unresolved wording and the missing meaning visible.
A.6.C:4.4 — MVPK faces are not second contracts
The atomic claims for one boundary use have one canonical source; use the A.6.B Claim Register when §4.5 calls for it. Publication faces present those claims for a bounded reader and use under E.17:
- Faces may select, summarize, and render claims for audiences. A selected episteme's
U.Viewmembership separately requires E.17.0 conformance to a viewpoint. - Faces must not add a new boundary claim; they project the existing classified claims.
- Any face-level decision-relevant or normative-looking statement SHOULD cite the underlying claim ID(s) or canonical location(s). A new boundary claim MUST be added to its canonical source before publication on a face. Informative commentary may explain source claims without adding boundary semantics.
Keyword rule (faces).
Each face sentence containing a BCP-14 keyword MUST cite its existing classified claim ID or canonical location and direct object. Duty/recommendation/prohibition and current-grant projections cite their D claim; a gate projection cites its A claim; exercise or evaluated-finding projections cite their E claim. Use the selected A.6 A6-AW-* row for permission-looking wording.
A face-level keyword creates no object or quadrant. If the boundary claim is not traceable, put it in its canonical source before publishing it on the face; informative commentary is limited to explanation that adds no boundary semantics. To avoid keyword-evasion, equivalent deontic phrasings (e.g., “is required to…”, “is prohibited from…”) SHOULD follow the same claim-reference discipline even when no BCP-14 keyword is present.
Projection may be paraphrased for audience fit, but it MUST NOT change the deontic or semantic claim; if exactness is critical or disputed, use verbatim.
A.6.C:4.5 — A.6.B Claim Register additions (recommended)
When stable reuse, decision, audit, dispute, or cross-face projection needs a record, use the A.6.B Claim Register (IDs, statements, quadrant, and canonical location). A one-off local repair ends with the repaired atomic prose. When the register is needed, add only the current A.6.C fields below without creating another record or ontology kind:
-
bundleId(optional local ID grouping atomic claims discussed together) -
questionRef(optional pointerQ1,Q2,Q3, orQ4to the four questions above; it selects no kind, subject predicate, or quadrant) -
directObjectDesignation: useU.RelationRefconstrained to the relation family for a relation occurrence, the applicableU.EpistemeReffor a whole episteme, or the admitted reference kind for another independently identified entity.When one claim inside an episteme is the direct object, use
C.2.1 ClaimAddress: episteme-edition reference plus intrinsic claim identity declared by that edition's ClaimGraph.The entity-reference branches designate independently identified objects; the claim branch designates content inside the named edition. Neither carries the designated content.
-
directObjectPatternLocator(the pattern-description locator for the ClaimGraph that defines or constrains that direct object; it asserts no ownership relation) -
faceRefs(optional mapping fromPlainView,TechCard,InteropCard, orAssuranceLaneto where this same claim is rendered)
Each row uses the A.6.B fields for one statement, claim ID, quadrant, and canonical location. Do not create a second boundary-language record or a Permission, Utterance, WorkEvidence, or result-or-evidence umbrella kind.
A.6.C:5 — Archetypal Grounding (Tell–Show–Show)
A.6.C:5.1 — Tell
When boundary contract-language leaves a consequential ambiguity, recover the claim and referent, then answer only the live questions below. Keep ordinary metonymy when its capable participant and relation are locally recoverable; a literal act or individual commitment needs that participant and the governing conditions.
- What was promised? State the promise-content claim if one exists.
- What was said, published, or instituted? Identify only the asserted speech act, description/publication objects and institutional effects, under the conditions in §4.1.
- What governance or permission-looking claim exists? State either a generic D prescription with its normative source and applicability, an individual D claim about an obtaining commitment with its actual bearer and institution basis, or the selected
A6-AW-*claim in its own quadrant. State responsibility separately under its admitted domain predicate or return its missing governor. - What happened, what followed, and what supports reliance? State dated Work, each current result/change/delivery/acceptance claim, and each current evidence-use or reliance claim separately; omit absent claims.
When acceptance or the work still due depends on how undertakings, conditions or acts fit together, use §4.1 to establish the required connection. This includes one order with several required acts. Identify what was accepted and what remains open or due.
When those answers need stable reuse, decision, audit, dispute, or cross-face projection, write them in the one A.6.B Claim Register: one atomic statement, direct object, subject assertion, non-semantic pattern locator, and quadrant per row. Otherwise stop with the repaired atomic prose. Faces cite reused claim IDs or canonical locations; they do not create another bundle record.
A.6.C:5.2 — Show (System archetypes)
(A) Software API boundary
Draft wording:
“The Payments API guarantees idempotency. Clients must provide Idempotency-Key. We log all requests. Availability is 99.9%.”
Source clauses and additional illustrative premises:
Preserve “We log all requests”; the draft supplies no particular logging Work or observation basis. “Availability is 99.9%” does not say whether 99.9% is a target, a promised bound, or an observed value; that meaning remains unresolved.
For the extended case below, assume the PaymentsAPI description/publication, definitions of idempotency and key uniqueness, a gate policy with an additional key-validity condition, and a generic provider-side idempotency prescription. These are additional case premises, not atoms recovered from the draft. The source's client requirement remains to provide Idempotency-Key.
-
Description/publication: signature or mechanism publication for
PaymentsAPI(MVPK faces: TechCard, InteropCard). -
L: define idempotency and the uniqueness semantics of
Idempotency-Key. (“Idempotent” is a semantic property, not a duty.) -
A: admissibility predicate: request is admissible iff
Idempotency-Keyis present and valid. (Gate belongs to mechanism.) -
D: the API policy generically requires covered clients to provide
Idempotency-Key. In this extended case it also states a provider-side idempotency prescription. No individual commitment follows from those clauses alone. If the case claims thatClientIntegrator-AorProviderSystem-Abears one of those duties, cite that bearer's separately instituted A.2.8 commitment. (Responsibility, if claimed, needs its own direct relation.) -
E — additional hypothetical evaluation: suppose admitted system
PaymentsAvailabilityEvaluator-AperformedAvailabilityEvaluation-Payments-T1 : U.Workover the Payments API request population and windowTusing the availability metric stipulated for this evaluation.A.6.1 application
PaymentsAvailabilityApplication-T1has result bindingavailabilityResult -> AvailabilityResult-Payments-T1; that C.2.1 result episteme statesobservedAvailability=99.9%forT.When the SLA decision relies on this result, an A.10 path links it to the request-log and measurement carriers used. This hypothetical observation does not select the meaning of the draft's unlabeled 99.9%.
(B) Hardware interface boundary
Draft wording: “The connector guarantees safe operation. Devices must not exceed 20V. Negotiation must succeed before power is applied.”
Source requirements and additional illustrative premises:
The draft leaves open whether “Devices must not exceed 20V” is a device-behavior constraint or an obligation on a capable bearer, and it does not identify the safe-operation predicate. Preserve the 20V upper bound and the requirement that negotiation succeed before power is applied. The additional gate and test below do not resolve the bearer or safety choices.
-
Description/publication — additional case premise: assume a published interface spec supplying the pinout, electrical ranges, handshake procedure, and the test declaration used below.
-
L: electrical invariants and allowable ranges are definitions and invariants (truth-conditional).
-
A — additional gate premise: suppose the interface specification makes power delivery admissible only after the handshake state reaches an agreed mode.
-
Requirement awaiting classification: retain “Devices must not exceed 20V”; recover its constraint or duty-bearer reading before assigning it to L or D. The negotiation-before-power requirement remains distinct from the additional gate predicate.
-
E — additional hypothetical test: suppose admitted system
HardwareTestSystem-AperformedConnectorSafetyEvaluation-T1 : U.WorkoverConnector-C1under the declared method, load, and temperature window.A.6.1 application
ConnectorSafetyApplication-T1has result bindingsafetyResult -> ConnectorSafetyResult-T1; that C.2.1 result episteme statesmaximumObservedVoltage=19.8V,handshakeState=agreed-before-power, andConnectorSafetyCriterion-v3=satisfiedfor those conditions.When relied on, an A.10 path links this result to
TestReport-C1-T1,VoltageTrace-C1-T1, andNegotiationLog-C1-T1carriers.In this hypothetical test, 19.8V is below the retained 20V upper bound. The separately given criterion result does not by itself settle the draft's unspecified safe-operation claim.
(B-PER) Compact permission replay (only when the permission branch is live)
Situation: “ReleaseAuthoritySystem, acting as release grantor under assignment ReleaseGrantor-A, approved DeploymentAgent-A, acting under assignment Operator-A, to deploy Release-4711 after preflight.”
Unpack + classify:
-
Promise content (optional):
SVC-RELEASE-4711states which release artifact eligible consumers are promised. -
Speech-act Work:
ReleaseGrantorAssignmentis a declaredU.SystemRoleAssignmentspecies. OccurrenceReleaseGrantor-Ahas admitted SystemReleaseAuthoritySystemas holder and the local release-grantor kind as assigned-kind value. That System performs datedApproveoccurrenceSA-4711under the assignment.The assignment supplies only the holder and assigned-kind facts used by the policy. Any authority required by
ReleaseGrantPolicymust obtain independently.Under the applicable policy,
SA-4711institutes—not merely publishes—grant occurrencePER-4711only if the A.2.8.PER obtaining conditions hold. -
D — current grant (
A6-AW-NORM-GRANT):ReleaseOperatorAssignmentis another declared species. OccurrenceOperator-Ahas admitted SystemDeploymentAgent-Aas holder and covers this window. The grant's beneficiary participant cites that occurrence, and its permitted-action participant isU.EpistemeRef(Deploy-Release-4711).This Claim Register row uses
U.RelationRef(PER-4711), constrained toGrantedPermissionRelation@Context, as itsdirectObjectDesignation.SA-4711, the two assignments, policy, context, scope, and window remain grounds or qualifiers.The model may use this D claim only while the A.2.8.PER conditions make
PER-4711obtain and the row cites the named occurrence, act, and policy. -
E — weak evaluation alternative (
A6-AW-WEAK): if the basis establishes only current absence of prohibition in a sufficiently complete frame, recordNonProhibitionFinding@Context; do not promote it to a strong grant or place it in D. -
A — independent entry predicate (
A6-AW-GATE): “deployment is admissible iffPER-4711currently obtains and preflight is green” is anA-*predicate. It may consume the grant as one condition but is neither the grant nor proof of gate passage. If an actual gate decision is also asserted, record its A.21GateDecisionResult, bounded action, applicable profile application, complete required check-application result set, decision value, and consequence as a separate E claim. -
E — actual Work and exercise (
A6-AW-EXERCISE): A.13 first recovers admitted SystemDeploymentAgent-Aas the performer through obtaining assignment occurrenceOperator-Aof declared speciesReleaseOperatorAssignment; A.15.1 independently admits datedU.WorkoccurrenceDeployRun-4711. Because this permission-exercise branch expressly consumes precise assignment-bound attribution, F.6 then relates that already admitted Work through the same assignment and checks holder equality and coverage.The Work must instantiate the action specification inside the grant's scope and window. Only then may
PermissionExerciseRelation@ContextbindWorkRef(DeployRun-4711)toU.RelationRef(PER-4711), constrained toGrantedPermissionRelation@Context. The assignment contributes the beneficiary and attribution facts consumed here.Missing or failed F.6 alone leaves independently admitted Work intact but blocks this attribution-dependent exercise branch. If the same finding questions a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent claims. Planned work, the approval wording, and preflight alone are not exercise.
-
E — optional result or delivery: if
DeployRun-4711returnsReleaseArtifact-4711, cite the A.6.1 result binding or an already governed subject-specificWorkResultRelation; if that artifact is transferred, cite the independently obtaining delivery/transfer relation defined by its subject pattern. -
E — evidence (optional): an A.10 path may link the grant, Work, exercise, result, or delivery claim to its current carriers for one bounded reliance use.
A.6.C:5.3 — Show (Episteme archetypes)
(C) Multiparty protocol boundary (behavioural and session-type motif)
Draft wording: “The protocol guarantees progress. Participants must follow the sequence.”
Source clauses and additional illustrative premises:
The progress guarantee needs its semantic or operational meaning. For the illustrative case below, assume the published protocol description and the trace-admissibility criteria; the named trace evaluation is an additional hypothetical case.
-
Description/publication: protocol description (could be a type spec or protocol spec plus explanatory views).
-
L — when the guarantee is semantic: the progress property is a law over the protocol model (truth-conditional, within the theory).
-
A — additional entry-condition premise: suppose a session-entry mechanism uses the declared trace criteria to determine whether an interaction may enter the session. Its entry predicate is A; the trace-validity definition remains L and an actual conformance verdict is E.
-
D: the protocol description generically requires covered participants to follow the stated sequence. It asserts no individual commitment occurrence.
-
E — additional hypothetical trace evaluation, not inferred from the progress guarantee: suppose admitted system
ProtocolConformanceEvaluator-AperformedProtocolConformanceRun-T1 : U.Workover bounded interactionTrace-42.A.6.1 application
ProtocolConformanceApplication-T1has result bindingconformanceResult -> ProtocolConformanceResult-T1; that C.2.1 result episteme statesconformanceVerdict=passandobservedTerminalState=completedunderProtocolConformanceCriterion-v5.For a disputed interaction, an A.10 path links this result to
MessageTrace-42,ConformanceRunRecord-T1, andProtocolAuditRecord-42carriers.
(D) Socio-technical “SLA + audit trail” boundary
Draft wording: “Provider shall respond within 4 hours for Severity‑1 incidents. Only Severity‑1 is covered. Evidence is provided by ticket logs.”
Unpack + classify:
-
Promise content (service promise clause, when present): a responsiveness promise for a defined incident class and window is separate from the SLA's generic prescription.
-
Description/publication: SLA publication (and its views for different audiences).
-
Scope from the source: the promise covers only Severity-1 incidents. This coverage restriction becomes an A claim only when a separately defined admission rule uses it as an entry or continuation condition for a named action or application.
-
D: the SLA clause generically requires the covered Provider to respond within 4 hours for Severity-1 incidents; only Severity-1 is covered. Claim that actual provider
ProviderSystem-Abears the four-hour duty only after the SLA's individualizing rule and required actual basis establish one A.2.8 commitment; otherwise keep the clause generic. -
Evidence source clause: the draft names ticket logs as evidence; it supplies no measured response interval.
-
E — additional hypothetical response evaluation: suppose admitted system
SLAEvaluator-AperformedResponseEvaluation-Ticket-17 : U.Workover Severity-1 ticketTicket-17under the declared clock and measurement method.A.6.1 application
ResponseMeasurementApplication-Ticket-17has result bindingresponseIntervalResult -> ResponseIntervalResult-Ticket-17; that C.2.1 result episteme statesobservedResponseInterval=3h42mandwithinFourHourTarget=true.When the SLA decision relies on this result, an A.10 path links it to ticket, response-timestamp, clock-source, and severity-classification carriers. The four-hour requirement is from the source;
3h42mis the additional hypothetical observation.
A.6.C:6 — Bias-Annotation
- Gov bias: prefers explicit accountability and adjudication hooks; increases clarity but adds authoring overhead.
- Arch bias: optimises evolvability by preventing hidden coupling across stack layers.
- Ontological and Epistemic bias: enforces EntityOfConcern, Description episteme, and carrier separation; requires compatible participants for literal agency claims without rejecting recoverable interface metonymy.
- Prag bias: accepts that “contract” is common vocabulary; offers a disciplined rewrite rather than prohibition.
- Did bias: aims to be teachable via repeated unpacking examples across boundary types.
A.6.C:7 — Conformance Checklist
A boundary description conforms to A.6.C iff it satisfies all items below:
-
CC‑A.6.C‑1 (Four questions, atomic answers). When contract-like wording leaves a consequential ambiguity, the text SHALL answer only the applicable four-question branches with atomic claims. Each asserted object and its subject predicate SHALL remain separately recoverable. Classify each claim through A.6.B and identify the defining pattern when its rules govern that claim. Where a conclusion about an order depends on several undertakings or acts, the account states which connection the governing terms require and the grounds for applying it, or identifies the connection that remains open.
-
CC‑A.6.C‑2 (No agency to epistemes). When a dated act or individual commitment is claimed, the text MUST identify its capable actual participant and MUST NOT substitute an API/interface label, description, publication carrier, kind, or assignment for that participant's basis. Ordinary metonymy may remain when its participant and relation are locally recoverable.
A generic prescription SHALL name its normative source and applicable content without inventing an individual bearer.
An individual duty or commitment SHALL name its actual bearer and separately obtaining
U.Commitment; an assignment may appear only as an instituting rule's applicability ground. -
CC‑A.6.C‑3 (Classify contract-language statements via A.6.B). When contract-language leaves a consequential ambiguity, its unpacked statements SHALL be atomic L/A/D/E claims. In that unpacking, permission-looking wording SHALL select one A.6
A6-AW-*row; A.2.8.PER membership alone MUST NOT set the quadrant. -
CC‑A.6.C‑4 (Promise content ≠ Work discipline). A statement about one dated Work SHALL name the A.15.1 occurrence. A result, production, change, delivery/transfer, evidence or acceptance statement SHALL use its own direct object and shall not be inferred merely from Work. Promise-content language remains about
U.PromiseContent. When service or access-like wording occurs in a relied-on boundary claim, recommendation, decision, gate, assurance, publication, or reuse and hides the concrete subject, participant, predicate, kind, permission, Work occurrence, or next subject question, the text SHALL recover that hidden choice through E.10 L-SERV and A.6.P:4.11a, then state the assertion under the recovered predicate with its pattern locator. Quoted, historical, illustrative, and harmless ordinary wording remains outside this recovery rule; an actualU.PromiseContentreferent still uses the head phrase promise content, not bare service. -
CC‑A.6.C‑5 (Evidence hook for operational guarantees). When a “guarantee” expresses an operational claim, the text SHALL state the E claim’s predicate, object, relevant scope or window, and what establishes it or remains missing. Name Work, evaluation or observation when the claim depends on it. If required grounds are missing, retain the claim as unresolved; report a negative result only when the grounds establish it.
For evidence use, the text SHALL keep the grounds required by receiving reliance recoverable under §4.1, question 4; use A.10 when a replayable account is needed and identify carriers or observation conditions when they affect the claim or use.
-
CC‑A.6.C‑6 (No second contracts via faces). MVPK faces MUST NOT add new boundary claims; they publish only the existing canonical L/A/D/E claims under E.17. Informative commentary may explain those claims without adding boundary semantics. An asserted
U.Viewseparately requires E.17.0 conformance. -
CC‑A.6.C‑7 (RFC‑keyword discipline inside faces). Each MVPK face sentence containing a BCP-14 keyword MUST cite its classified claim ID or canonical location, direct object, and selected
A6-AW-*row when permission-looking. Only norm/grant claims cite D; gate claims cite A; exercise and evaluated findings cite E. -
CC‑A.6.C‑8 (Obtaining is not representation). A
PublishorApproveutterance, a document, carrier, or record does not by itself institute or prove aU.CommitmentorGrantedPermissionRelation@Context. The obtaining predicate and cited context policy decide whether the relation obtains.A Claim Register row may assert or support reliance on it only when the row names the occurrence, predicate,
SubjectPatternLocator, participants, scope/window, and current evidence required by that use.For a commitment, the row cites its rule-required actual instituting basis and policy; for a strong grant, it cites the actual instituting speech act and policy. The row alone does not create the relation.
When the grant occurrence is the row's direct object,
directObjectDesignationSHALL be aU.RelationRefconstrained toGrantedPermissionRelation@Context; an entity reference,ClaimAddress, display label, or arbitrary identifier cannot fill that branch.
A.6.C:8 — Common Anti-Patterns and How to Avoid Them
A.6.C:9 — Consequences
Benefits
- Category mistakes become systematically repairable.
- Generic prescriptions remain usable without invented occurrences, while individual commitments remain distinguishable and adjudicable through their actual bearer, rule, instituting basis, scope, validity, and any evidence needed for reliance.
- Boundaries remain evolvable: laws, gates, governance, and evidence can evolve with controlled coupling.
Trade-offs and mitigations
- Unpacking and connecting claims takes time. Stop when the wording is clear for its use or the available facts settle the receiving decision. Keep a Claim Register entry when stable reuse, decision, audit, dispute or cross-face projection calls for it.
- Some stakeholders prefer “one sentence contract”; mitigated by MVPK faces that present curated projections while keeping the underlying claim set coherent.
A.6.C:10 — Rationale
FPF already distinguishes signatures, mechanisms, dated Work, separately identified results or consequences, and evidence use. When contract-language collapses them, the author asks what happened, what separate result or delivery is claimed, and what evidence supports the reliance use.
F.18 may supply durable names for recovered terms, but it does not provide the ontology. A.6.C keeps promise content, speech act, commitment or grant, dated Work, application/result binding, production, change, delivery/transfer, evidence, and acceptance distinct and independently optional. This keeps contract language classifiable under A.6.B without turning A.15.1 into a semantic source of result or delivery.
A.6.C:11 — Source contributions
The following sources contribute distinct disciplines to boundary interpretation.
-
Dietz and Mulder distinguish production from the acts that request, promise, declare and accept a product. They connect several transactions for one order through the results each requires. In FPF, the terms governing a particular order determine what counts as its acceptance. Enterprise Ontology, second edition, ch. 8, §§8.2.5–8.2.7
-
BCP 14 (RFC 2119 and RFC 8174) supplies the interpretation of capitalized requirement keywords. A.6.B separately classifies the claim; the visible keyword alone does not establish its object or whether an individual relation obtains.
-
Behavioural and session types describe typed interactions, including safety and progress properties. These support the distinction between model properties, admission conditions, implementer obligations and actual trace results.
-
Algebraic effects, handlers and effect systems distinguish declared operations from their handling. This is a useful analogy for declaration versus actual application; a result, production, delivery, evidence use or acceptance requires its own relation.
-
ISO/IEC/IEEE 42010:2022 viewpoint discipline supplies conventions for descriptions under viewpoints. E.17.0 tests a selected episteme's
U.Viewconformance, while A.6.3 governs any separately claimed construction. A.6.C keeps the boundary claims traceable across ordinary E.17 publication faces.
A.6.C:12 — Relations
-
Uses and is used by
- Uses A.6.B for L/A/D/E claim classification, atomicity, and cross-quadrant reference discipline.
- Used by A.6 cluster conformance (“contract unpacking”) as the detailed, reusable form of that discipline.
- Complements A.6.S (signature engineering): contract unpacking is a common constructor step when turning prose boundaries into publishable signatures.
- Coordinates with A.6.P families: when “contract or guarantee” wording in a boundary use still leaves a consequential ambiguity after RPR, apply A.6.C to that ambiguity. (A.6.C is not a specialization of A.6.P; A.6.P is relation‑precision, A.6.C is boundary‑contract disambiguation.)
-
Coordinates with
- A.7 (EntityOfConcern, Description episteme, and carrier) for correct placement of evidence claims.
- A.15.1 for the dated Work occurrence and its §4.6 dispatch to application/result, production, change, evaluation, evidence, delivery/transfer, and acceptance patterns.
- F.12 (service acceptance) for structuring how promise-level commitments connect to evidence and acceptance windows.
- E.17 MVPK “no new semantics” rule to prevent publication faces from becoming new contracts.
- A.2.8.PER for the permission-side direct objects; A.6
A6-AW-*and A.6.B classify each atomic claim without treating pattern selection as its quadrant.
A.6.C:End
Relation Obtaining and Individuation: Distinguish Occurrences When Needed
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Problem frame
Plain name. Relation occurrence.
Primary EntityOfConcern. One obtaining relation occurrence of an admitted relation kind, when a receiving use needs to reidentify it or distinguish it from another occurrence.
Primary working reader. An engineer who has stated a direct relation and must decide whether that sentence suffices or a receiving use needs explicit occurrence identity.
Working concern and viewpoint. Preserve the readable direct relation assertion. Add explicit occurrence identity when reidentification, comparison or another dependent use needs it, keeping the world-side occurrence distinct from its description, designation and representation.
Use this when. Use this pattern when a receiving use needs to reidentify one obtaining relation occurrence, distinguish it from another or use that occurrence as a participant or argument. A report that only needs to say Robot-7 is assigned as inspector through InspectionAssignment-17 can keep that direct sentence and stop. A history distinguishing two MaintenanceInspectionAssignment episodes with the same Robot-7 and InspectorSystemRole needs the identity branch. So does a dependent relation that requires one already distinguished occurrence as its participant; a second episode need not already have occurred.
First useful move. State the direct relation and participants using the subject pattern's meanings and obtaining predicate. Apply that test to the relevant facts or constituting history and state the supported result. Ask whether the receiving use needs to reidentify or distinguish this occurrence. If not, keep the direct sentence and stop; otherwise apply the identity and receiving-use steps in section 4.2.
What goes wrong if missed. An epistemic, designation, or representation-side object is treated as what creates the relation it is meant to describe or designate. Repeated assignments with the same participants then collapse into one. At the opposite extreme, every ordinary relational sentence is expanded into a relation-occurrence description episteme even though later work does not need to distinguish occurrences.
What this buys. Engineers can report a current relation in ordinary prose without opening unused apparatus. When history, comparison, evaluation, or another direct relation must distinguish repeated occurrences, a system can apply the domain identity rule while assertions, descriptions, designations, representations, and publication occurrences retain their own identities.
Not this pattern when. If the wording leaves the direct relation or participants unclear, use A.6.P or A.6.RSIR. If the defining content does not supply participant meanings, applicability and the obtaining predicate, recover that content first. When case facts do not establish obtaining, keep the claim and its polarity or uncertainty under its direct semantics; an assertion alone supplies no occurrence to individuate. Forecasts, scenarios, counterfactuals and permissions retain their own claim families. Use A.10 or the current evaluation for a separate reliance judgement. For reusable declaration SlotSpecs use A.6.5. When the direct sentence already suffices for the receiving use, stop there.
Problem
When a later engineering use needs one obtaining relation occurrence to remain distinguishable from another, descriptions often state five different claim contents as if one assertion or identifier established them all. The claims have this dependency order; the order does not turn them into five project-time decisions:
- the direct relation obtains for the named participants, those participants jointly satisfy its semantic predicate, one occurrence therefore exists, and the direct identity rule governs its reidentification and distinction from another occurrence;
- FPF ontology settlement already admits occurrences of that relation kind under
U.Relation; the direct pattern states the relation-specific participant meanings, obtaining condition, and occurrence-identity rule, while a compatibleRelationSignatureepisteme declares corresponding SlotSpecs for reusable descriptions; - a system performing explicit-individuation work applies the admitted identity rule so the named receiving use can recoverably distinguish one occurrence; a separate relation-occurrence description episteme is produced only when the selected receiver needs that description;
- an identifier designates that already recoverable occurrence under a reference scheme;
- the selected receiving object is either an episteme whose content designates that occurrence, another direct relation that has the occurrence as a participant, or an assertion episteme whose content states that one A.6.1 operation application binds the occurrence as its actual argument value under one named
ArgumentDeclaration.
The later claim contents do not make the earlier relation obtain. Root U.Relation admission is a corpus ontology decision governed by E.24.UK. A.6.REL supplies the common occurrence discipline, while each direct relation pattern supplies the relation-specific participant meanings, obtaining condition, and occurrence-identity rule used as the admission witness. Project work does not repeat that classification decision.
A system performing explicit-individuation work applies the direct identity rule so one existing occurrence is recoverably distinguishable for the current use; that work neither creates the occurrence nor by itself requires a separate description episteme.
A system performing naming work may subsequently associate a designator with the occurrence, and a receiving episteme may subsequently contain a reference that designates it.
Relation-heavy work often begins from a table row, graph edge, identifier, or reified statement. An engineer can then mistake the represented row, edge, identifier, or reifier identity for world-side relation identity. Applying this method permits use of relation-occurrence identity without reversing representation and ontology and without forcing a relation-occurrence description episteme into every readable sentence.
Forces
Solution
Local relation-occurrence mantra. State the direct relation. Ask whether the receiving use needs occurrence identity. If no, stop. If yes, apply the direct identity rule and add only the receiving object that use needs.
Use A.22.CGUS when a receiving use needs a reusable constraint-governed unfolding structure for these continuations and stops.
Apply the relation-object architecture discipline
Relation-object architecture discipline names the rule set in this subsection. Conforming prose keeps the objects around one direct relation distinct, names the direct relation between adjacent objects, and uses a recoverable name for each current object. A.6.5 specializes only the SlotSpec part of this rule set.
Short use rule. State the world-side relation and its actual participants first. Add another named object from the relation-object architecture only when the current receiving use depends on that object, and state its direct relation to the object already in view. The tables below help select that additional object and relation; they are not a mandatory form for ordinary relation prose.
The world-side relation comes first. An actual relation participant is one U.Entity participating in one obtaining relation occurrence under one relation-participant meaning. Participation leaves the entity under its independently governed intrinsic kind. A relation occurrence is the obtaining U.Relation occurrence itself. The direct relation obtains when the actual participants satisfy the obtaining predicate; the occurrence-identity rule provides the criteria for reidentification, continuity, and distinction from another occurrence. Signatures, assertions, names, references, and representations retain their separate identities.
World-side objects
The phrase actual relation participant therefore never replaces the entity's own name. It says how that entity participates in this occurrence. Likewise, the readable sentence Robot-7 is assigned as inspector through InspectionAssignment-17 can state the direct assignment without first creating a relation-occurrence description episteme.
Relation-kind settlement
The relation kind is a classificatory distinction over relation occurrences. Every admitted direct or derived relation kind has one direct subject settlement that states relation-participant meanings, an obtaining predicate, applicability, and an occurrence-identity rule as semantic and rule content. A derived kind additionally names its base-definition and substrate dependencies. Ordinary use may omit explicit individuation when no receiver needs it; that omission does not mean the identity rule is absent. World-side entities participate according to the settlement while retaining their own kinds.
Public name. U.Relation denotes the admitted root occurrence kind. A direct relation kind keeps its own governed name, participant meanings, obtaining predicate and occurrence-identity rule.
The named card supplies the root name used by E.24.UK and F.18:
In the world-side relation, the actual entities participate directly under the relation-participant meanings. When assertions and descriptions need typed reuse, a reusable declaration episteme declares those meanings without becoming the world-side relation.
Reusable declaration episteme
SlotKind, ValueKind, and refMode answer different questions. SlotKind identifies the declaration component locally. ValueKind is the independently governed kind of the actual relation participant. refMode states how a receiving episteme designates that participant. Together they specify one declaration component; world-side entities and occurrences keep their independently governed identities.
Claim and description epistemes
A receiving episteme contains a relation-participant designation in a content position corresponding to one declared SlotSpec. A concrete representation may carry that designation in a field, but the field keeps its source name and corresponds to the declaration-local SlotKind only through an explicit declaration or representation correspondence. Reusing the SlotKind spelling for convenience does not identify the field, SlotKind, designation, or participant.
The designation denotes the actual participant; the participant remains a U.Entity, the obtaining occurrence remains a U.Relation, and the receiving episteme keeps its own C.2.1 identity.
Naming, reference, and representation
A source-specific term remains the name of its source-side object until an explicit correspondence is stated. That correspondence never identifies a source representation element with the represented FPF object. Representation preservation stays with the selected representation or representation-transition pattern; C.29 governs a declared mathematical-lens use. Structural equivalence goes to C.34, and cross-context sameness goes to A.6.9.
Use the subject pattern for the current object
For an actual Work claim, recover the acting System through the applicable Work conditions. Relation occurrences obtain; epistemes carry declarations, assertions and descriptions; names and references stand in designation relations. Ordinary metonymy may remain when the capable participant and its relation are recoverable.
Name only the minimum current object
The relation-object architecture organizes the distinct objects that may become current. For each relation sentence, select only the object needed by the current use. Stable relation-kind semantics belong once in the direct relation pattern or ontic. A reusable declaration belongs once in its RelationSignature. A durable name belongs once in its F.18 naming settlement. Later prose names the object current for its use and cites the subject pattern for already established neighboring objects.
In recognition text, prefer the readable direct relation sentence. Put the reusable declaration, occurrence-identity rule, naming settlement, or representation correspondence in nearby Tech or assurance text governed by its direct pattern, and refer to it when another declared use depends on it. Precision comes from recoverable subject patterns and explicit relations between adjacent objects, not from repeating the complete architecture.
This rule keeps elaboration additive. Each new receiving use introduces only the object on which that use depends and the object's direct relation to an already recoverable object. When the use stops at the world-side relation, the prose adds no signature, occurrence-description, naming, or representation apparatus.
Apply the receiving-use test
Here receiving use is ordinary wording. First state the readable relation and ask what later work must distinguish. If occurrence identity is needed, name the receiving object: an assertion or description episteme under C.2.1, a direct relation that uses the occurrence as a world-side participant, or an assertion episteme stating that one already identified operation application binds the occurrence as the actual value of a named A.6.1 argument. Any acting system, enacted method, and performed work remain separately governed.
-
Name the direct relation kind and participants in a readable sentence. Use only the direct relation-participant meanings, obtaining predicate, and applicability needed to state that sentence accurately; do not yet require a
RelationSignature, SlotSpecs, occurrence designator, representation correspondence, or the complete occurrence-identity rule. -
Immediately ask: Does the receiving use need to reidentify this occurrence or distinguish it from another, including another episode with the same participants?
-
Apply the contrast. A current report that needs only the relation sentence answers no. A history distinguishing repeated episodes answers yes. A later comparison that must establish that two reports concern the same occurrence, or a dependent relation that takes this occurrence as a participant, also answers yes.
-
If no, keep the readable direct sentence and stop this pattern. Do not create a relation-occurrence description episteme for completeness.
-
If yes, recover the participant meanings, applicability, and obtaining predicate from the subject pattern. Inspect the relevant world facts or constituting history in the current case and judge whether they satisfy that test. Only when the current-case facts satisfy the predicate is there an obtaining occurrence to individuate. Otherwise keep the result as a
C.2.1claim under the direct predicate; useA.6.Ponly while the predicate or participants remain unclear. A claim-bearing episteme records the claim family and polarity; evidence and reliance stay with their direct governors. -
Recover and apply the subject pattern's same-versus-new-occurrence rule. Explicitly individuate one occurrence; assign an identifier only when stable reference is needed.
-
Only now name the receiving object and subject pattern, then use the corresponding branch:
- Designate the occurrence in a receiving assertion or description episteme;
- for a receiving direct relation, verify its obtaining with that occurrence as a participant;
- or, for an already identified operation application, verify the named A.6.1
ArgumentDeclaration, designation rule, ValueKind, cardinality, and binding predicate before an assertion episteme states that the occurrence is its actual bound argument value.
Occurrence existence depends on the direct relation obtaining. Reidentification and distinction from another occurrence depend on the direct identity rule. Explicit individuation depends on a named receiving use. Identifier assignment and reference use depend on an already recoverable occurrence. None of the later moves makes the earlier relation obtain.
Select an identity rule that survives repetition
Use participant-determined identity only when the direct ontology establishes that two distinct occurrences of this relation kind cannot have the same participant identities. The RelationSignature SlotSpecs declare how assertion or description episteme content designates those participants.
SlotKinds identify declaration components; database-row and representation keys identify representation elements. Neither function supplies the world-side occurrence-identity rule; apply any constitutive-participant contribution declared by that rule.
When the same participants can enter more than one occurrence, the direct pattern declares the discriminator that exists in that domain:
When a relation occurrence is a constructed result under its direct construction rule, recover each constructing U.System through A.13 and let A.15.1 independently admit the performed construction Work.
Add F.6 only when the occurrence-identity explanation or a later receiving claim expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 establishes that Work-assignment link and identifies neither the assignment nor the performer. A short explanation may omit an unused assignment identifier.
Missing or failed attribution alone leaves independently admitted construction Work intact; if the same finding defeats a consumed admission premise, recheck that premise and its dependent conclusions under A.15.1.
Also recover the enacted constructor Method, input entities, and the identity contribution of that Work occurrence.
An installed-part relation is a hypothetical candidate here: installation Work may distinguish its occurrences only after an accepted pattern for that relation declares the participant meanings, obtaining predicate, applicability, and constitutive identity contribution. Until then, do not infer an installed-part occurrence from the Work, row, drawing, assertion, designation, or representation.
A changed episteme contributes to occurrence identity only when that episteme itself is a constitutive participant under the direct identity rule. A changed publication occurrence contributes only when that publication occurrence is itself a constitutive participant under the same rule. A system merely learning about the relation, describing it, or publishing an episteme about it changes no world-side occurrence.
Separate occurrence, assertion, reifier, relator, description, and publication
A relational assertion is an episteme whose content affirms or denies the direct obtaining predicate for the designated participants. Keep forecasts, scenarios, counterfactuals, permissions, and other claim families under their direct governors. Record supported, refuted, or unresolved reliance separately under A.10 or the receiving evaluation. The assertion and its reliance posture can be revised or superseded while the world-side relation remains unchanged.
A reifier is a representation-side term or node. A system may use it to represent statements about a proposition, assertion episteme, or relation-occurrence description episteme. Its presence does not make the direct relation obtain and is not a world-side occurrence-identity rule.
A direct material-relation ontology may identify a relator: a dependent material truth-maker through which its participants stand in the relation. Introduce one only when that ontology identifies the relator, its dependence relations to the participants, and its occurrence-identity rule. Do not generalize that relator to relation kinds whose direct ontology does not provide those three settlements.
An episteme can describe a relation occurrence. A second episteme can describe the first episteme.
Under a publication-relation occurrence, a selected episteme edition is available to the declared audience and use. If an information carrier is current, E.17 governs its publication-kit use and E.24.PUB governs publication; carrier identity replaces neither episteme identity nor relation-occurrence identity. None of these objects replaces the direct occurrence-identity rule.
Use one relation occurrence as a participant of another
Before asserting or relying on one relation occurrence as another relation's participant, identify the first occurrence under its direct identity rule. The receiving direct pattern states a participant meaning whose admitted kind includes U.Relation or the specific relation kind. For typed reuse, its RelationSignature declares the corresponding SlotSpec.
In the world-side receiving relation, the occurrence itself is the participant; the designation in an assertion or description denotes it under the applicable reference rule. Individuation establishes what the assertion refers to; it does not make the world-side participation begin.
Ordinary typed participation applies here. The first occurrence keeps its kind, participants, obtaining condition, and identity. The receiving relation keeps its participant meanings, obtaining condition, and identity rule; the receiving RelationSignature keeps its SlotSpecs. The reference used by an assertion belongs to neither world-side occurrence.
Keep ordinary relation use lightweight
The direct relation pattern states the shared participant meanings, obtaining predicate, applicability, and identity rule once; later uses cite only what their branch consumes.
The alternatives below show semantic dependencies within demand-driven progressive elaboration. They share one readable direct relation. The receiving occurrence branch follows a positive distinguishability decision and the direct identity rule, while the RelationSignature branch remains independent and opens only for typed reuse.
This diagram shows the stop decision and optional increases in explicitness. Its indentation records one dependency: description, identifier assignment, occurrence participation, and later designation require a recoverable occurrence after the same-versus-new-occurrence rule.
Keep world-side change separate from episteme editions
Whenever current wording or work says that a relation occurrence, claim, reusable declaration, name, reference, description, or publication "changed," first name which object changed and apply that object's own continuity, identity, revision, or edition rule. This selection does not require an A.10 evidence relation:
A relation occurrence has identity under its direct rule; a temporally extended occurrence also has temporal history under that rule. Revising an episteme about an occurrence does not by itself establish a change in that occurrence.
Check whether the changed episteme or performed Work is constitutive under the direct rule. Current case facts or constituting history must separately satisfy the direct continuation, cessation, or same-versus-new-occurrence rule. Another edition of an assertion, signature, or description episteme, or another publication occurrence, therefore does not by itself entail a new relation occurrence.
Use A.10 only for a separate evidence-based reliance question. Determine world-side continuation, cessation, or a new occurrence from current-case facts or constituting history under the direct identity rule.
Archetypal Grounding
Repeated occurrence of one direct system-role-assignment species
Start with Robot-7 is assigned as inspector through InspectionAssignment-17 and trace only the objects needed by the current use.
-
World-side participants and occurrence.
Robot-7remains an admittedU.System;InspectorSystemRoleremains one local C.3 kind.InspectionAssignment-17is an occurrence of directly declaredMaintenanceInspectionAssignment <: U.SystemRoleAssignment.Robot-7participates as the holder system andInspectorSystemRoleas the assigned local system-role kind. Those two values are the complete participant set of this direct species. -
Direct settlement. A.2.1 supplies the species' participant meanings, direct predicate, applicability, and same-versus-new-occurrence rule. The occurrence continues while that predicate obtains without interruption for the same complete participant set. A demonstrated predicate-false gap ends it; later resumption starts another occurrence. An evidence gap by itself does neither.
-
Reusable declaration. For typed reuse, the
MaintenanceInspectionAssignmentRelationSignaturecontainsHolderSystemSlot : U.System / U.EntityRefand the declaration-localAssignedSystemRoleKindSlotwithMaintenanceSystemRoleKindDomainas ValueKind andByValueas refMode. InInspectionAssignment-17,InspectorSystemRoleis the assigned-kind participant value. A stronger direct species adds only its identity-bearing participants.assignmentIntervalremains assertion or occurrence-description content, not another participant SlotSpec. -
Assertion and participant designations. An
InspectionAssignmentAssertioncarries designations corresponding to the species' declared SlotSpecs and states the currently knownassignmentIntervalseparately. Its claim may say thatRobot-7is currently assigned as inspector throughInspectionAssignment-17. If the receiving use needs only that current report, keep the assertion and stop without adding a separate occurrence-description episteme. -
Occurrence identity, designator, and reference. Suppose two episodes of the same direct species have the same complete participant values but occur in inspection shifts separated by a demonstrated predicate-false period. To prepare a history or Work-attribution claim that must distinguish the episodes, a practitioner applies the A.2.1 continuity rule, distinguishes the second occurrence, and assigns a designator only if stable reference is needed. A roster-row identifier, copied field set, taxonomy edition, reference scheme, or reused source key cannot collapse or split the two episodes.
-
Representation. A roster row or diagram edge may represent the assignment assertion or an occurrence-description episteme. A roster row's fields and key retain their representation-side meanings; the source elements of a diagram edge retain their representation-side meanings.
An explicit declaration or representation correspondence relates a source field to the SlotKind and the carried value or reference to the participant designation; using the same spelling for field and SlotKind is optional and establishes no identity. Representation identity does not replace the A.2.1 occurrence rule.
The practical payoff is visible at each stop. In a current staffing report, keep the readable direct sentence. For typed reuse, consult the existing declaration. When history or Work attribution must distinguish a repeated episode, apply the A.2.1 continuity rule and distinguish that episode; assign a designator only if stable reference is needed.
Hypothetical installed-part boundary
Bearing_B isPartOf Pump_P may be a readable source claim, but current A.14 does not supply an InstalledPart relation kind, installed-part participant meanings, an installed-part obtaining predicate, or its same-versus-new-occurrence rule. Names such as InstalledPartRelationSignature, InstalledPartSlot, and AssemblyWholeSlot are therefore hypothetical candidates, not current declarations. Do not use them to claim conformance or an individuated installed-part occurrence.
An installed-part identity judgement needs a direct subject pattern that supplies those meanings, obtaining conditions and identity rule. A.6.REL supplies none of them. Keep the physical entities, installation Work and proposed part-relation claim identifiable, and stop before claiming an individuated installed-part occurrence. Add a description, designator or representation only when the receiving use needs it.
Formal reduced case
The expression 3 < 5 is assertion content written in a mathematical notation. Under the referenced arithmetic structure, the values three and five satisfy the less-than predicate. The expression is not thereby a relation occurrence. No receiving use in this case needs the obtaining less-than relation occurrence explicitly individuated under U.Relation, so the engineer stops at the assertion. A graph edge or RDF reifier introduced by tooling remains a representation of the proposition or assertion and is not an occurrence-identity rule in the formal subject domain.
Relation occurrence as a participant
C.22.PFR has one actual-condition relation occurrence and one problem-criterion-applicability relation occurrence as world-side participants. Each is individuated under its own direct identity rule. The PFR direct pattern states those two participant meanings, its obtaining condition, and its identity rule; the PFR RelationSignature episteme declares the corresponding SlotSpecs. A PFR assertion designates the two occurrences according to those SlotSpecs. PFR is a direct relation, not an episteme whose content merely groups two assertions.
Description and publication recursion through the relation-object architecture
Let R1 be the already individuated second MaintenanceInspectionAssignment occurrence from 5.1.
- An assignment-occurrence description episteme
E1hasR1as its EntityOfConcern. In the reusable C.2.1EpistemeConstitutionRelationSignature, the declaration-local SlotKindEntityOfConcernSlotnames the entity-of-concern participant meaning. In a card representation ofE1, the source fieldentityOfConcernRefcorresponds to that SlotKind only through a declared representation correspondence; itsU.EntityRefvalue is the participant designation that resolves toR1. Neither spelling nor containment identifies the field, SlotKind, designation, or occurrence. - A second episteme
E2contains the result of evaluation work concerning the adequacy ofE1. Its EntityOfConcern isE1, notR1. A field in a reusable card or other representation may carry aU.EntityRefdesignatingE1; it corresponds toEntityOfConcernSlotonly through a declared representation correspondence. The two epistemes therefore have different EntitiesOfConcern and retain separate C.2.1 identities:E1describesR1, whileE2evaluates the adequacy ofE1. - Under a publication-relation occurrence, the current edition of
E1is available to a declared audience and use. The selected episteme edition is an actual participant of that publication relation under the publication pattern's participant meaning. The publication form and its representation elements retain their own kinds and correspond to the published episteme only through the declared publication and representation relations.
A system performing revision work can establish another edition of E1 or E2; a system performing publication work can establish another publication-relation occurrence for a selected edition.
R1 continues or ceases only as the A.2.1 obtaining predicate and occurrence-identity rule determine from the assignment facts. This recursive case preserves the distinction: a description episteme can itself become the actual participant or EntityOfConcern of another relation without becoming the relation occurrence it describes.
Bias-Annotation
This pattern has an individuation bias because it serves receiving uses that need relation identity. The stop rule prevents that bias from turning every direct relation into an explicit relation-occurrence description episteme.
The admitted system-role-assignment case can over-emphasize participant identities and temporal continuity. Another direct relation may instead use constituting Work or another world-side discriminator, but only when its own accepted pattern states that contribution. The hypothetical installed-part boundary demonstrates why A.6.REL must not invent that rule.
Engineers can easily picture relation instances through data-model examples. When a representation must distinguish an obtaining occurrence, first apply the subject pattern's obtaining test to the relevant case facts or constituting history, then apply its occurrence-identity rule. A system introduces a database row, graph edge, reifier, or other representation for that declared use only after those steps.
Representing an assertion or another claim family does not by itself require an obtaining relation occurrence or explicit individuation.
Conformance Checklist
- Across the subject pattern and the current use, the relation kind, relation-participant meanings, relation obtaining predicate, actual relation participants, applicability, relation occurrence-identity rule, and any currently needed
RelationSignatureSlotSpecs are recoverable. An ordinary relation sentence remains complete without repeating that settlement. - The text does not conflate relation obtaining, predicate satisfaction, root-kind admission, explicit-individuation work, identifier assignment, and reference use.
- Root
U.Relationadmission is governed byE.24.UKfrom the commonA.6.RELdiscipline and the relation-specific witness supplied by each direct relation pattern; project use does not repeat the admission decision. - After the readable direct relation, ask whether the receiving use needs to reidentify this occurrence or distinguish it from another. A simple current report can stop; a history, same-occurrence comparison or dependent relation can require the identity branch.
- Apply the subject pattern's obtaining test to the relevant case facts or constituting history and state the supported result. Assertion polarity or an evidence/reliance result supplies no occurrence merely by its form; any constitutive contribution must satisfy the direct rule in section 4.3.
- Every admitted direct or derived relation kind has a direct governing settlement that declares its occurrence-identity rule; ordinary omission of explicit individuation or an occurrence designator does not count as absence of that rule.
- Participant-determined identity is used only when the direct ontology establishes that the same participant identities cannot recur in distinct occurrences of that relation kind.
- When the same participants can recur, the direct pattern declares the domain discriminator; maximal continuous obtaining interval and constituting work are possible choices only when that pattern includes them in the occurrence-identity rule.
- When construction is constitutive, the constructing system, input entities, performed construction work, and identity contribution are named; representation creation is not substituted for construction.
- Each object in the relation-object architecture is reidentified under its subject pattern and connected to adjacent objects only by the direct relations stated in section 4.1.
- Before asserting or relying on a relation occurrence as another relation's participant, identify it under its direct rule. The receiving assertion's reference remains distinct from that world-side participant.
- When the receiving use needs occurrence identity, apply the direct same-versus-new-occurrence rule without first creating a
RelationSignature. Follow section 4.2 and add a designator or reference only when stable reference is needed. - Another episteme edition, publication occurrence, name association, or reference use does not by itself establish another world-side relation occurrence. Apply the direct occurrence-identity rule to the current case facts or constituting history; use A.10 only for a separate evidence-based reliance judgment.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits. A.6.REL supplies no universal truth-maker, occurrence-identity discriminator, or representation form; for each direct relation, use the truth and occurrence-identity conditions in its defining pattern, and for the selected representation, use the form in its representation pattern.
In a direct species under U.SystemRoleAssignment, A.2.1 uses uninterrupted predicate obtaining and a demonstrated false gap to distinguish repeated episodes for history or Work attribution. In the formal reduced case, 3 < 5 remains assertion content and needs no explicitly individuated relation occurrence. In C.22.PFR, the actual-condition and criterion-applicability relation occurrences are already individuated under their own direct rules before PFR uses them as participants.
Each assertion remains a claim-bearing episteme.
Costs. The receiving use must recover and apply the direct relation kind's identity rule. Determine whether participant identity, temporal extent, constituting Work or another domain discriminator supplies the needed reidentification or distinction. A data schema that used row identity as ontology may need to expose the domain identity it hid.
Limits. A.6.REL does not decide whether a direct relation obtains, define every relation kind, or prescribe a storage model. It does not supply evidence, comparison, publication, forecast, scenario, counterfactual, permission, or temporal semantics governed by neighboring patterns. It also does not turn assertion polarity, a separately governed claim family, or a reliance posture into an obtaining occurrence.
Rationale
Applying this method lets an engineer use occurrence identity without equating ontology with documentation. A direct relation can obtain for its participants before an FPF episteme states a sentence about it.
The actual relation participants, considered under their participant meanings, satisfy the semantic predicate within the direct relation pattern's declared applicability and temporal conditions. An assertion is an episteme whose content affirms or denies that predicate under its direct claim family. A.10 or the receiving evaluation separately governs supported, refuted, or unresolved reliance. Explicit-individuation work is performed by a system for a named receiving use. An identifier only enables later reference.
Keeping those objects and moves distinct prevents semio-bias in which an episteme is mistaken for the world-side relation.
The identity rule belongs to the direct relation pattern because the direct ontology determines whether participant identities suffice. The same complete participant set can stand in two occurrences of one A.2.1 direct species when a demonstrated predicate-false gap separates them. The same component and whole may belong to distinct part-relation episodes only if their accepted subject pattern declares the relevant discriminator; A.6.REL supplies none. Conversely, an ordinary formal order assertion may need no explicit occurrence object in project work. A universal key would be too weak for repetition and too heavy for ordinary use.
Assertion, description, and signature epistemes can have editions; a system performing publication work can establish another publication-relation occurrence for a selected edition.
A relation occurrence instead begins, continues, or ceases under its direct rule; when a system applying that rule distinguishes another occurrence, the other occurrence has its own identity. Keeping episteme edition change, publication occurrence, and relation occurrence continuity separate makes repair local and prevents publication history from masquerading as world history.
SoTA-Echoing
Ontological SoTA and constructional sources
This pattern uses these sources to constrain its account of occurrence existence and identity. They provide ontological comparisons, not notation selection.
Representation and implementation stress tests
This pattern uses these sources to test whether the selected ontological distinctions can be represented and used. They do not determine what relation occurrences exist or how they are identified.
Relations
A.6.0declares RelationSignature participant SlotSpecs and restates the direct predicate, applicability, and identity rule for reuse without making the relation obtain.A.6.5separates world-side participants from RelationSignature SlotKinds and from participant designations in assertions or descriptions.A.6.Pgoverns restoration of hidden direct relations and participants before occurrence identity is attempted.A.6.RCDgoverns the residual case in which participants are known but no current direct relation closes the named receiving claim; any admitted derived or primitive relation kind must include its own direct subject settlement and identity rule.A.6.RSIRgoverns selection among a direct relation, relation-participant meaning, declaration SlotSpec,RelationSignature, and another interface object when wording is ambiguous.- Use
A.2.1to state directU.SystemRoleAssignmentspecies, predicate obtaining, and occurrence identity, andF.6for later attribution to performed Work. A.14and direct mereology patterns define or constrain only the part-relation kinds and part-whole changes they declare; A.6.REL adds no installed-part settlement.A.15.1governs work occurrence identity and readable links to separately governed participation, change, operation-result, production, evaluation, delivery, and acceptance claims.C.2.1governs assertions and descriptions about relation obtaining, predicate satisfaction, and occurrences;E.24.PUBgoverns publication availability and occurrence identity; useE.17when an accepted account needs a reader-facing publication form.C.22.PFRsupplies a worked case with two explicitly individuated relation occurrences participating in one dependent evaluative relation.C.29governs a declared mathematical-lens use, including use of a graph, tuple, or database representation as such a lens for relation structure.E.24governs ontic settlement andE.24.UKgoverns rootU.Relationadmission.A.6.RELsupplies the common occurrence discipline, and each direct relation pattern supplies the relation-specific witness.E.24.CDsupplies the candidate-detection rule only after the prerequisite subject results are recoverable; it does not replace the direct occurrence-identity rule.F.18governs durable names and identifier use after the relation kind and occurrence identity are settled.
A.6.REL:End
U.Signature - Reusable Law-Governed Declaration Episteme
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Pattern kind. Ontic declaration pattern.
Builds on. A.7 for strict distinction, C.2.1 for episteme identity, C.3 for kinds, A.2.6 for claim scope, and A.6.5 for relation-slot discipline.
Coordinates with. A.6.REL for relation occurrences, A.6.1 for mechanisms, C.29 for mathematical-lens use, E.24.UK for durable U-kind admission, and E.24.PUB for publication.
Problem frame
An engineer has a vocabulary and a set of laws that need to remain stable across several dependent epistemes, such as model epistemes, method descriptions, and patterns. For example, a physical-modeling team needs one stable declaration of connector variables and conservation laws; a clinical team may need one stable definition of a dose-response predicate and its applicability without assuming that a dose-response relation kind has been admitted; and a formal-methods team needs one stable declaration of terms, inference forms, and invariants.
Use this pattern only when the thing being written or reused is itself a reusable declaration. A description, rule, policy, work plan, or specification does not qualify merely because it contains terms or constraints that recur elsewhere.
Before opening declaration fields, ask:
What subject does this declaration cover? What values or results does it speak about? Which terms and laws may another use rely on? Where do those laws apply?
In FPF terms, the declaration is about one independently governed EntityOfConcern; SubjectKind and RangedValueKind name its declared subject and value range; ResultKind is added when a distinct result kind is current; and Vocabulary, Laws, and Applicability answer the remaining three questions.
U.Signature is the episteme that carries this declaration. For a relation kind, use RelationSignature. For a mechanism family or formal calculus, use the corresponding A.6.1 or FormalSubstrate declaration. A.3.1 gives the identity of a repeatable method. To define a kind of methods or judge whether a method meets its criterion, use C.3 and C.3.2.
Primary working reader and concern. The reader is an engineer who authors or reuses a declaration and needs stable meaning, applicability, and typed reuse without authoring declaration or occurrence-identity apparatus beyond what the current use needs.
For the lightest useful declaration, name that subject through SubjectKind and RangedValueKind, add ResultKind when the result has another kind, and state Vocabulary, Laws, and Applicability. Add SliceSet and ExtentRule only when the same declared kind can have different members at different U.ContextSlice values and one named reuse needs that difference. Add A.6.5 SlotSpecs that declare the direct relation's participant meanings only inside a reusable RelationSignature; add operation argument and result declarations under A.6.1 when a mechanism declaration needs them. Add dependency declarations only when another signature relies on provided names or laws.
What goes wrong if this pattern is missed: content about later realization, evaluation, and publication accumulates inside the declaration. A later user cannot tell which names and laws are reusable, where they apply, or whether a changed implementation has changed the declaration.
What this buys: one identifiable declaration can be reused while later realizations and uses change under their own subject patterns.
Do not use this pattern merely to state that a direct relation obtains or that one work occurrence produced a result. State that claim directly. A maintenance work plan may reuse the words connector and conservation law while scheduling tasks; it remains a work plan unless its own claim content performs the reusable declaration job above. Construct a signature only when reusable declaration content is the current object.
Problem
FPF uses a signature when the episteme itself performs the reusable declaration job above: it identifies the declared subject and value or result range, supplies terms and laws another use may rely on, and says where those laws apply. Current non-exhaustive declaration families include theory or A.3.3 U.Dynamics epistemes, mechanism or A.19.SelectorMechanism declarations, method-kind declarations, formal substrates, and direct relation-kind declarations. Without an ontic definition of the declaration episteme:
- the signature is confused with the entity it describes;
- a relation declaration is confused with an obtaining relation occurrence;
- applicability is reduced to an unexplained context label;
- every declaration is forced into one rigid table-shaped publication form, even when a readable sentence is enough;
- imported names and exported names remain implicit, so dependent declarations cannot be replayed safely.
The central problem is failure to keep the declaration episteme, its declared subject, the subject's occurrences, and later uses of the declaration as different objects.
Forces
Solution
Use U.Signature as the dependent durable U-kind for a reusable law-governed declaration episteme. Identify the episteme through its content, EntityOfConcernRef, and effective ReferenceScheme. Let the declaration state its vocabulary, laws, and applicability. Keep the declared subject and every later realization under their direct kinds and relations.
Local signature mantra. Name the subject and value or result range. State the reusable terms, laws and applicability. Add participant declarations, operation parameters, slice-dependent membership or dependencies when a receiving use needs them. Distinguish the declared rules from applications, evaluations, Work and publication.
In FPF terms, the subject is identified by EntityOfConcernRef; SubjectKind, RangedValueKind, and optional ResultKind state the declared subject and range; and Vocabulary, Laws, and Applicability state the reusable terms, regularities, and use boundary. Add A.6.5 SlotSpecs only when a reusable RelationSignature must preserve the same participant meanings and types. Add A.6.1 operation arguments or results only for a current mechanism declaration. Add SliceSet and ExtentRule only when the same declared kind can have different members at selected context slices. Declare a dependency only when another signature relies on imported or provided names or laws.
If the named reuse still works without an optional addition, leave that addition out.
Mechanism implementations and realizations remain under A.6.1, evaluations under their direct evaluation patterns, work under A.15.1, and publication under E.24.PUB.
The mantra is Plain recall wording. When a receiving question concerns available continuations and their conditions, use A.22.CGUS's ordinary branch. Continue to formal qualification only when a named later use needs structure identity or replayable results; then identify the A.22 structure, its local loci and at least two potential continuations under the selected relations and constraints.
Admit and identify U.Signature
U.Signature is a same-individual dependent durable U-kind under U.Episteme. C.2.1 first identifies one episteme through one EpistemeConstitutionRelation by its complete claim content, independently governed EntityOfConcern, and effective ReferenceScheme. The claim graph and reference scheme are epistemic constituents; the EntityOfConcern is not. A.6.0 adds a stable membership condition and practitioner-facing declaration use to that already identified individual. It adds no second constitution relation, identity discriminator, assembly, composition rule, or holon test.
An already identified episteme is a U.Signature exactly when, under its effective ReferenceScheme, its complete identity-bearing claim content carries a reusable law-governed declaration about its EntityOfConcern and includes all of the following with substantive meaning:
- direct
SubjectKindandRangedValueKinddeclarations that identify the declared subject and value range; Vocabularythat supplies the designators needed to reuse the declaration;Lawsthat state the reusable predicates, equations, invariants, closure conditions, or other declared regularities;Applicabilitythat bounds where those claims are used;ResultKind,SliceSet,ExtentRule, and dependency, import, or provided-name declarations only when those distinctions are current for the declaration.
Resolve the complete interpreted claim content and operative rules under C.2.1:4.1.1; C.2.1:4.1.2 supplies NonemptyClaimContent and EpistemeInterpretationScheme when a typed consumer needs those ranges. Signature membership additionally requires the substantive declaration content above. Judge that complete content, not a selected subset or the presence of field names.
A minimal directly authored signature may carry the declaration content required by the A.6.0 membership predicate in one claim graph without citing any smaller episteme.
A signature may instead cite separately identified source or dependency epistemes, provided its own claim graph names the dependency relation and the declaration meaning thereby reused. Those source epistemes remain separate individuals connected through their governing dependency, source-use, edition, or other direct relations; they are not components assembled into the signature, and their citation alone does not establish signature membership.
E.24.UK governs the one-time public admission of the dependent kind.
In project work, authoring a new declaration candidate, or revising a declaration so that its claim content, EntityOfConcern, or effective ReferenceScheme changes, yields a resulting C.2.1 discriminator triple. When the one EpistemeConstitutionRelation for that triple obtains, C.2.1 identifies the resulting episteme; A.6.0 then judges whether that already identified individual satisfies the U.Signature membership predicate, without adding a second constitution occurrence or identity discriminator.
An optional separately reviewable membership judgment is another classification-assertion episteme whose EntityOfConcern is the candidate. For citation, comparison, reuse, or membership judgment with unchanged C.2.1 discriminators, the candidate episteme and its constitution occurrence remain the same.
The signature keeps the C.2.1 identity of the same episteme. Two designations resolve to that same individual only while the complete claim content, EntityOfConcern, and effective ReferenceScheme are unchanged. Changing any discriminator identifies another U.Episteme; call that new individual a U.Signature only if it independently satisfies the membership predicate above. State an edition, refinement, or supersession relation only when its own direct predicate obtains.
The declared subject remains the independently governed EntityOfConcern, not the signature. A realization of the declaration remains under its direct pattern. A description whose EntityOfConcern is the signature is another episteme.
Publication occurrence, independently identified expression, any selected reusable publication form, physical or digital carrier, and representations remain separate objects and relations under their direct patterns; publication or visible form establishes neither identity nor membership.
G.11 currentness and every later work or use likewise remain neighboring judgments and relations rather than signature identity components.
Write the minimum declaration content
The four content groups are semantic components, not a mandatory visual table. A publication form may present them as paragraphs, a table, formal declarations, or another representation. A publication occurrence makes a selected episteme edition available through that form without changing its content.
SubjectKind and RangedValueKind are declaration-content components. C.3 governs the declared kinds; E.24.UK governs public U-kind admission. A.2.6 supplies addressable U.ContextSlice values; C.3.2 governs the membership judgment and any optional materialized KindExtension representation.
SliceSet is not a generic space, time interval, numeric or result range, or changing dataset. ExtentRule tells how the declared kind's members are determined at one named slice.
A time selector may be part of a U.ContextSlice; a value or result range stays in RangedValueKind or ResultKind; changing data stays with its subject pattern; and a claim-bearing mathematical set representation opens C.29 only for a mathematical-lens use. Leave both fields out unless membership of the same declared kind can differ across the named slices.
Applicability and meaning remain distinct. The effective ReferenceScheme is part of episteme identity. The U.ClaimScope delimits use; when current for the declaration, a relevant time interval, selected CHR:ReferencePlane, or selected BoundedModelUseStructure : U.Structure further delimits or organizes applicability. Retain both the effective ReferenceScheme and U.ClaimScope when adding these applicability qualifiers.
Use RelationSignature for reusable relation declaration
RelationSignature is the relation-facing use of one U.Signature. It is not a second U-kind.
Its EntityOfConcernRef identifies one already admitted direct relation kind. If A.6.RCD settles a derived relation kind, that kind counts here only after its direct subject settlement states the participant meanings, exact base-definition and named-substrate dependencies, obtaining and applicability laws, and a direct occurrence-identity rule.
The derivation or predicate definition may be cited as a dependency, but a predicate-definition episteme whose EntityOfConcern is the reusable predicate definition rather than the admitted relation kind is not a RelationSignature.
A RelationSignature declares:
- the relation-kind designator;
- one
SlotSpecfor each world-side participant meaning that needs reusable typed declaration; - the direct pattern's obtaining predicate and declared laws, restated for reuse without claiming that the predicate is satisfied;
- applicability of those claims;
- the occurrence-identity rule supplied by the direct relation pattern, restated for reuse without applying it to any occurrence;
- for an admitted derived relation kind, the exact base relation definitions, named substrate and authorized derivation operation, and applicability dependencies already established by the direct subject settlement.
The direct relation pattern remains authoritative for when the relation obtains and how an individuated occurrence keeps identity. The signature declares those rules for reuse.
A direct relation may obtain before anyone writes a signature. Ordinary prose may therefore stop at:
During Shift-17, Robot-7 is assigned as inspector through InspectionAssignment-17.
This is an A.2.1 assertion about an occurrence of declared species MaintenanceInspectionAssignment under U.SystemRoleAssignment. Apply the species' declared predicate and occurrence-identity rule under A.2.1. The occurrence has Robot-7 as holder, InspectorSystemRole as assigned-kind value, and only the values required for any other declared participants. When several patterns must reuse those participant meanings, predicate, and identity rule, the species' RelationSignature becomes useful for typed assertions and F.6 attribution. When another claim must refer to this assignment episode, use A.6.REL for explicit individuation.
Declare participant meanings and operation parameters under different specializations
For each world-side participant meaning whose reusable declaration is current, a RelationSignature declares one A.6.5 SlotSpec. The following code sketch is a compact representation of that declaration:
Use A.6.5 to declare these participant meanings. In the simple MaintenanceInspectionAssignment species, use HolderSystemSlot and one declaration-local AssignedSystemRoleKindSlot with MaintenanceSystemRoleKindDomain as its ValueKind and ByValue as its refMode. In InspectionAssignment-17, InspectorSystemRole is the assigned-kind participant value.
A stronger species adds only a participant that changes its predicate or occurrence identity. Taxonomy episteme, reference scheme, interval description, and generic context may interpret an assertion but are not generic world-side assignment participants. Do not force SlotSpecs into a one-off assertion that has no receiving typed use.
A formal or mechanism declaration may instead need named operation arguments and a result. A.6.1 governs that OperationAlgebra. A representation may use a mathematical operand order, product, function, or tuple. A.6.3.RT governs a same-EntityOfConcern representation transition; C.29 governs only a mathematical-lens use.
Those operation parameters do not become RelationSignature SlotSpecs or SlotKinds merely because the same notation uses angle brackets or numbered arguments. When a relation claim consumes a mathematical representation, state an explicit correspondence between the representation's operands and the independently declared SlotSpecs.
Declare dependencies
Open a SignatureManifest only after this test. Add an import when removing one named provider would leave this declaration unable to interpret a required non-local term or unable to replay one of its stated laws; name the provider and the exact required term or law.
Add a provide entry when this declaration introduces a named term or law and one named dependent declaration relies on it. A background citation, similar vocabulary, shared publication, list membership, or convenient replay order is not a dependency.
The SignatureManifest heading co-locates entries with three functions: id is an identity-neutral display designator; signatureRef and its optional .edition pin form a governed reference to an already recoverable signature episteme; and imports and provides may carry or represent dependency and name-or-law introduction claims in the signature's claim content.
The SignatureManifest section may carry entries with these functions:
A change confined to the spelling of id or the serialization of signatureRef preserves episteme identity only when the reference still resolves to the same episteme and its claim content, EntityOfConcern, and effective ReferenceScheme remain unchanged.
Changing signatureRef.edition selects another already recoverable edition; it does not by itself establish an edition relation, historical continuity, or U.Signature membership for the referent. If a C.2.1 identity discriminator changes, A.6.0:4.10 governs the resulting identity.
Use these dependency-manifest predicates:
- SM-1 Term-and-law resolution. Every required non-local term or exact law claim resolves under the effective reference scheme to the one named provider declaration that supplies it.
- SM-2 No redeclaration and legal direction. A provided term or law is not also supplied by a transitive import under the same effective reference scheme, and the claimed provider-to-consumer direction matches the predicate of the dependency or source-use relation rather than a drawn arrow or list order.
- SM-3 Imports, replay order and cycles. Explicit
importsMUST form an acyclic graph and respect E.5.3's dependency direction. A cycle in those imports violates that rule and also prevents a one-pass provider-to-consumer replay. Recover the claims responsible for the cycle before repairing the declaration; do not silently delete an edge or invent an order. Other semantic relations retain their own governing predicates: the imports restriction is not a verdict on every possible relation cycle. Keep the graph representation and ordering separate from the semantic claims; use C.29 only for a mathematical-lens use. - SM-4 Export boundary. A dependent declaration relies on provided names and cited laws, not on private publication layout or implementation detail.
The remove-the-provider test above identifies a candidate dependency. State the dependency or source-use relation only after its direct predicate is satisfied for the named provider, consumer, term or law, and use. A citation, manifest entry, list membership, or replay result can support an assertion about that relation.
A provider or provider-edition change may require resolution, replay, or currentness review; it changes the consumer signature's identity only when the consumer's own claim content, EntityOfConcern, or effective reference scheme changes.
A governed reference to a separately identified object is not an exported vocabulary name merely because that reference appears in the signature.
Specialize declaration use without minting another root kind
A signature profile is a constrained use of the same U.Signature kind. The profile states which content is current and which neighboring patterns define or constrain later use.
profile = FormalSubstrate. Declare vocabulary and terms, inference kinds, formal laws, applicability, and the declaration dependencies carried in the signature's claim content. A.6.1 separately governs OperationAlgebra, operation designators, typed argument and result positions, admission conditions, application, and realization. An A.6.1 declaration may cite the FormalSubstrate signature. When a mathematical object is selected as a lens for another entity, C.29 governs the lens-use claim.
profile = PrincipleFrame. Write the postulates and invariants, then name the observable distinction each one requires: what must be observed or compared to tell whether the frame's claim holds. Cite a separately identified characteristic or measurement declaration when it is needed to state or check that distinction; units, scales, CHR:ReferencePlane values, comparators, and normalizations remain under A.17, A.18, C.16, CHR, A.19.CPM, and A.19.UNM.
If the text decides whether a proposed operation application, run, or gate may proceed, move that decision to A.6.1 or the direct evaluation and gate pattern, including A.21/C.11 where applicable. A PrincipleFrame may state what a decision must respect, but it is not that admission decision.
For ordinary reuse, apply the frame's Applicability and the direct subject rules for any reference-plane or model-use-structure question.
When the receiving claim needs a semantic relation between two local senses whose interpretation bases differ, first recover the two F.17 local senses; cite an F.9 Bridge only if its direct predicate obtains and state the bounded-use claim, direction, preservation, loss, and any required reliance separately. Cited declarations remain independently identified objects, not extra PrincipleFrame identity components.
State a relation between two signatures directly as refinement, conservative extension, equivalence, or another independently governed relation only when that relation's own predicate obtains.
Before using the refinement label, compare all three reusable content duties: Vocabulary, Laws, and Applicability. Name the terms preserved, added, or removed; the laws preserved, strengthened, or changed; and whether the population, time, CHR:ReferencePlane, and claim scope stay the same, narrow, or widen. An unexplained applicability widening fails the refinement claim; use another direct relation whose predicate explicitly permits the widening instead of hiding it under refinement. Use a C.29 morphism only when a mathematical structure-preservation claim is current.
Rule-content actual-use predicate declaration
RuleContentBasisFindingDefinition@R7 is one ordinary U.Signature for two reusable predicates over claim content. Its EntityOfConcern is the reusable predicate definition; both SubjectKind and RangedValueKind are NonemptyClaimContent under C.2.1:4.1.2. No distinct result kind is current because an ordinary C.2.1 assertion states whether a predicate obtains. The declaration is not a RelationSignature: dependentContent and baseContent are semantic parameters, not world-side relation participants or A.6.5 SlotSpecs.
The C.2.1 range criterion identifies eligible semantic inputs; it establishes neither actual use nor candidate sufficiency. This range declaration leaves an earlier exact episteme-edition pin at its original source. Before reusing an earlier assertion with the present declaration, compare its exact dependent and base values, interpretation and applicable predicate law; carry forward only the conclusion that this comparison supports. The names R7 and R8 alone do not identify an unchanged declaration episteme or transfer acceptance.
Its vocabulary includes SelectedRuleContentSubgraphDesignation@RuleContentBasisFindingDefinition-R7, derivedUsingRuleContent@RuleContentBasisFindingDefinition-R7, and evaluatedAgainstRuleContent@RuleContentBasisFindingDefinition-R7. The designation resolves one exact nonempty base subgraph selected for one identified use. RuleContentDerivationProfile@R7, RuleContentEvaluationProfile@R7, and RuleContentBasisFamilyAlgebra@R7 are named subgraphs of this signature's ClaimGraph.
The derivation predicate obtains only when an identified derivation claim used exact baseContent as a formal premise under a declared inference rule or application to produce exact dependentContent.
The evaluation predicate obtains only when an identified criterion-selection claim selected exact baseContent for one exact bounded evaluation claim concerning dependentContent.
Definition, constraint, applicability, consultation, citation, influence, provenance, evidence, evaluation Work, result, sufficiency, assurance, reliance, authority, and publication establish neither predicate by themselves.
An assertion names the exact actual-use claim identity and bounded receiving use, and adds scope, temporal policy, scheme interpretation, Bridge/loss, or source/witness qualifications only when each independently changes that assertion. A changed subject, content, mode, use, actual-use claim, scope extension, time policy, or interpreted endpoint identifies a successor assertion under C.2.1 rather than mutating every use of this reusable definition.
R7 is a changed-law successor of historical RuleContentBasisFindingDefinition@R6, not identity-continuous reuse. The C.2.1 succession assertion names predecessor, successor, changeClass = reusable-law-change, the changed law set—formal-premise/criterion-selection truth split, owner-claim removal, per-question analysis separation, independent candidate axes, pairwise compatibility, temporal-policy identity, and non-permissive reliance—and inheritedAcceptanceOrUse = none. A dependency pin selects R6 or R7 explicitly; a pin change reopens dependants rather than silently retargeting them.
Candidate-basis establishment and family disposition
RuleContentBasisFindingDefinition@R8 is a changed-law successor of R7. It preserves R7's two actual-use predicate tests and adds the following laws to its named RuleContentBasisFamilyAlgebra@R8 subgraph.
Candidate sufficiency is a separate operation: it asks whether a basis can support the exact derivation or bounded evaluation under named rules, not whether that basis was actually used.
Existing R7 actual-use assertions retain their exact definition and use pins. R8 inherits no acceptance, actual use or reliance merely from succession.
For one analysis question and temporal cell under E.4.PFR §3.6, take a finite candidate universe V and its supported open/closed state. Each candidate is a finite nonempty conjunctive set of semantic-base subgraphs.
The receiving contract fixes which axes are required before evaluation. Exactness, applicability and sufficiency are always required; acceptance and witness join that conjunction only when the receiving contract requires them. Each axis has an independently supported true/false result or remains unknown.
Sufficiency. In derive mode, the named inference rules derive the exact dependent proposition from the candidate basis with no undeclared premises. In evaluate mode, the basis supplies the criteria and facts required by the named evaluation rule to obtain its bounded result. That result may be negative: a supported failing evaluation does not make its basis insufficient. These laws neither establish derivedUsingRuleContent nor evaluatedAgainstRuleContent without their separate actual-use facts.
Establishment. A candidate is established iff all required axes are true. It is decisively defeated iff at least one required axis is false, even when another is unknown. Otherwise its establishment remains unresolved.
Minimality is an additional result: a candidate is inclusion-minimal when no proper sub-basis in the stated comparison domain is sufficient under the same rules. Unknown or false optional minimality does not remove an established candidate. A request for a minimal family qualifies that additional answer separately.
Let F contain all and only established candidates. Keep independently sufficient alternatives even when a required overlapping pair has incompatible consequences. A required pair is one whose compatibility can change the cell disposition or named receiver action; its result is compatible, established incompatible, or unresolved. Apply conflict precedence, then exactly one row:
An unknown axis on an already defeated candidate is not unresolved establishment. With fewer than two established candidates, no required pair exists and the all-compatible pair condition is vacuously true. The supported needed-content claim retains its reconsideration condition. A closed empty universe alone proves no missing need. Without a named receiving analysis need, take E.4.PFR's no-analysis exit before this operation.
R8's succession claim names R7, R8, changeClass = reusable-law-change, the added sufficiency/required-axis/conjunction/minimality/partition laws and inheritedAcceptanceOrUse = none. A dependency pin chooses the exact definition edition; R8 does not retarget R7 consumers. The result remains a non-permissive analysis assertion under C.2.1.
Keep declaration, realization, and use under their direct patterns
The rows name the direct patterns that define or constrain these common adjacent objects and claims.
Add explicit objects only for a named receiving use
Make three decisions by naming the next sentence, comparison, tool, or declaration that must work:
- State the direct relation and stop. Use this branch when the task only asks whether one direct relation's predicate holds for its participants under its subject pattern's conditions. State the affirmative or negative claim under that pattern, or a governed modal claim when that family is current. For example,
During Shift-17, Robot-7 is assigned as inspector through InspectionAssignment-17is a complete current A.2.1 assertion when the directMaintenanceInspectionAssignmentpredicate holds. Add an A.10 or receiving-evaluation reliance judgment only when the task separately asks whether to rely on the assertion. - Share one declaration. Reuse or author a signature when the receiving use needs reusable participant meanings, vocabulary, laws or applicability. The declaration can be useful before a second consumer appears. For example, a staffing assertion and an F.6 Work-attribution consumer can cite the
MaintenanceInspectionAssignmentRelationSignaturewhen both need itsHolderSystemSlot, declaration-localAssignedSystemRoleKindSlotwithMaintenanceSystemRoleKindDomainas ValueKind andByValueas refMode, any species-specific participants and the direct predicate. InInspectionAssignment-17,InspectorSystemRoleis the assigned-kind participant value. Repeating the wordassignedalone creates no declaration need. C.2.1 identifies an authored episteme through its claim content, EntityOfConcern and effective reference scheme; A.6.0 then judges signature membership. - Distinguish one occurrence. Open occurrence identity only when a later claim must refer to that same occurrence, compare or qualify it, track its beginning, continuation, cessation, or change, or use it as a participant of another relation. For example, F.6 work attribution must cite the covering assignment episode, and a staffing history that compares Shift-17 with a later reassignment must apply A.2.1's uninterrupted-obtaining same-versus-new-occurrence rule. A roster-row identifier that merely designates an assertion identifies neither the assignment occurrence nor a new occurrence; use F.18 only after A.2.1 has distinguished the occurrence to which a reference should resolve.
These are the receiving-use thresholds. They concern three different objects and are not stages that construct a relation or episteme from need.
The stop is observable: the target direct assertion, shared declaration for the named consumers, or occurrence-referencing claim can be written without another unresolved object. That target motivates authoring, selection, reuse, or explicit individuation.
Apply C.2.1 to episteme identity and the direct relation pattern to occurrence identity. Selecting or reusing an unchanged episteme leaves its identity unchanged.
When entries, branches, returns, or stops form one reusable structure, apply A.22.CGUS's formal qualification branch only after the A.22 identity, local locus bindings, selected relations and constraints, and potential continuations are recoverable.
Recover formal-substrate and PrincipleFrame uses by direct governing relation
The same independently identified formal object or episteme can participate in these different uses while retaining its own identity and kind. State the applicable declaration, dependency, operation, lens, or carry-through relation for the receiving use.
For a PrincipleFrame, write one postulate or invariant together with the observable difference that would count for or against it. Cite a characteristic, measurement, unit, scale, reference plane, comparator, or normalization declaration only when that declaration is needed to state or check that difference; an informative citation is not a dependency.
Do not put an operation-admission, run-acceptance, or gate-passage verdict into the frame.
For ordinary reuse, apply the frame's Applicability and the direct subject rules for any reference-plane or model-use-structure question.
If the receiving claim needs a semantic relation between two local senses whose interpretation bases differ, recover the two F.17 local senses and test the direct F.9 predicate; cite a Bridge only when it obtains, state preservation and loss in a separate bounded-use claim, and establish any required reliance before use.
A cited declaration may be superseded, or an independently obtaining dependency relation may cease or be replaced, without retroactively changing the PrincipleFrame's identity.
Changing the PrincipleFrame's own citation or dependency claim changes its claim content and therefore identifies another episteme; the same follows when its EntityOfConcern or effective reference scheme changes. Any edition, refinement, or supersession relation between the two epistemes must independently obtain and must pass the Vocabulary-Laws-Applicability comparison above.
Change the object that changed
Apply C.2.1 first. Every U.Episteme is identified by its complete interpreted claim content (ClaimGraph), one EntityOfConcern, and its effective interpretation rules (ReferenceScheme). Changing any member of this mandatory triple identifies another episteme. That episteme is a U.Signature only when it independently satisfies A.6.0 membership. A changed discriminator, SignatureId, or signatureRef.edition value does not by itself establish signature membership or historical continuity.
A change to imports or provides changes the consumer signature's identity only when it changes that signature's own claim content. A changed provider or provider edition can instead leave the consumer episteme unchanged while requiring the named dependency or source-use assertion, resolution result, replay result, or currentness judgment to be reconsidered.
A changed later use does not change the signature unless the change alters one of its C.2.1 identity discriminators. For example, a new mechanism realization remains a new realization, and a new publication layout remains a new publication form.
Recover the particular relation being claimed between two different epistemes. For historical continuation, test EpistemeEditionRelation under C.2.1. For model refinement or abstraction, compare the interpreted assertions under B.5.MR. Supersession or another relation needs its own predicate and grounds. Revision work, shared title, changed identifier, citation, or sequence alone establishes none of these relations.
When a once-current signature becomes stale while its identity remains recoverable, G.11 governs currentness and selection among recoverable editions.
Reopen declaration authoring when a proposed change affects the signature's claim content, EntityOfConcern, effective reference scheme, declared dependency, Vocabulary, Laws, Applicability, or the boundary of a FormalSubstrate, PrincipleFrame, or other admitted profile. The revised claim-bearing candidate is another C.2.1 episteme; A.6.0 judges its signature membership again, and any edition, refinement, or supersession relation remains a separate claim under its direct governor. Also reopen the affected declaration element when current problem-owning-domain or formal-method SoTA changes the term, inference form, law shape, applicability condition, or realization boundary being declared.
When a governed kind name, SubjectKind, RangedValueKind, SlotKind, RefKind, or exported term is renamed, apply F.19 to the changed wording; use E.10 for unresolved lexical questions and F.18 for durable naming. Accept the rename only when a cold reader can still recover the same FPF kind, declaration use, and practical action; otherwise keep the old name or return the naming defect.
Do not revise the signature merely because a realization, work occurrence, measurement, Bridge use, evidence-use relation, publication, provider currentness, or G.11 selection changed. Update that neighboring object under its subject pattern, and reopen the signature only if its own claim or dependency content must change.
Archetypal Grounding
Physical modeling: connector-equation FormalSubstrate
A multi-domain modeling team repeatedly uses one connector-and-equation calculus. The EntityOfConcernRef of its U.Signature(profile=FormalSubstrate) identifies that calculus. SubjectKind names the modeled connector declarations governed by the calculus, and RangedValueKind names its well-formed terms and equations. Vocabulary names the potential and flow variables. Its inference and equation laws say how a selected connection assertion yields potential equality and the zero-sum flow equation. Applicability states the modeling assumptions and selected CHR:ReferencePlane. If those terms or laws cannot be interpreted or replayed without a named quantity declaration, the manifest names that provider and the exact imported term or law; otherwise a background citation stays outside the dependency manifest.
The sentence ModeledPort_A is connected to ModeledPort_B is a separate model-side connection assertion. If repeated typed connection claims require a RelationSignature, first recover or admit the modeled-connection relation kind, its two connectable-port participant meanings, direct predicate, qualifier laws, Applicability, and occurrence-identity rule; only then may that relation declaration cite this FormalSubstrate when the dependency test passes. A generated equation set and a connector diagram are later result and representation epistemes, not either declaration; use A.6.1 for operations, A.15.1 for Work, and E.24.PUB for publication. Govern each representation and its declared correspondence through the applicable representation pattern, including A.6.3.RT for a same-EntityOfConcern representation transition. Open C.29 only for a mathematical-lens use.
Practical payoff: engineers can compare the connector vocabulary and equation laws across tools.
Clinical work: dose-response claim before relation-kind admission
A clinician needs the ordinary claim: During PatientEpisode_8472, Intervention_5mg was associated with OutcomeChange_BPminus10 over ObservationWindow_Days0to28 under the stated dosing and population conditions. No current direct pattern in this corpus governs a DoseResponseRelationKind. For this use, A.6.RCD therefore keeps the sentence as a local compound claim in one C.2.1 episteme; repeated clinical uses may justify a reusable predicate-definition episteme, but neither result is a RelationSignature or a relation occurrence.
The local predicate treats the named patient episode, intervention, outcome change, and observation window as its inputs. ObservationWindow_Days0to28 answers how long this patient's outcome change is aggregated for this assertion. The claim's or reusable definition's Applicability instead states the population, dosing protocol and conditions, and the time and claim scope in which the rule is used. Do not repeat the patient window as Applicability unless a separate applicability claim uses that same interval.
Before any RelationSignature can be published, the missing-governor result must name the candidate relation kind, these participant meanings, the direct predicate, Applicability, occurrence-identity rule, and a standalone clinical domain governor; E.24/E.24.UK must admit the result.
A selected assay-result episteme may support or refute the compound assertion. Use A.2.4/A.10 to qualify that evidence use and any intended reliance. When an assay result changes, reassess whether it supports or refutes the same bounded assertion; that assessment may stay the same, change, or be unresolved. The reusable predicate definition remains unchanged. A changed outcome meaning, population, dosing condition, or declared applicability changes the definition's claim content and C.2.1 identity.
Practical payoff: clinicians and analysts can write and compare the bounded claim now, reuse a settled predicate definition when repetition warrants it, and keep patient episodes, evidence epistemes, and evidence-use claims distinct.
Learning: criterion declaration and evidence use
During AssessmentInterval_2026Q2, learner Learner_17 correctly diagnoses cavitation in PumpCase_A and PumpCase_B and selects the stated corrective action. A separate observation episteme, PerformanceObservation_17A, states what was observed. After applying the reusable declaration Criterion_PumpCavitationDiagnosis_v3, assessor Assessor_4 makes the separate competence-assertion episteme CompetenceAssertion_17_Q2: Learner_17 met Criterion_PumpCavitationDiagnosis_v3 for diagnosing cavitation and selecting the stated corrective action in PumpCase_A and PumpCase_B during AssessmentInterval_2026Q2.
Criterion_PumpCavitationDiagnosis_v3 is the reusable declaration governed here. Its EntityOfConcernRef identifies the pump-cavitation diagnosis criterion; SubjectKind names assessed pump-cavitation diagnostic performances and RangedValueKind names the results meets and does not meet. Vocabulary defines the cases, diagnosis, and corrective action; Laws say which observable response earns either result; Applicability limits the equipment family, task form, and assessment method. No current direct pattern supplies DemonstratedCompetenceRelationKind, so this case asserts neither that relation signature nor a world-side demonstrated-competence occurrence.
For this bounded assessment use, the direct A.2.4/A.10 evidence-use relation names PerformanceObservation_17A as EvidenceEpisteme, the quoted competence claim as EvidenceTargetClaim, the two specified cases as EvidenceClaimScope, supports as EvidencePolarity, and AssessmentInterval_2026Q2 as EvidenceRelevanceWindow. Its A.10 evidence-provenance path identifies the observation work, method, carrier, and assessor's relying context. That relation supports reliance on this competence claim; it does not authorize course progression. A self-report without that observation path, a performance on another task, or a performance outside the named interval does not by itself establish this bounded claim.
Changing the publication form or making another publication occurrence for the unchanged criterion or competence assertion changes neither episteme. Changing the criterion's Vocabulary, Laws, or Applicability changes its claim content and identifies another declaration episteme; any edition or continuity relation must separately obtain. A new performance observation or assessor claim likewise identifies separate evidence or claim content rather than changing the criterion declaration.
Practical payoff: two assessors or curriculum tools can reuse the same declared criterion and its performance-and-result meanings while making separately identified competence claims about separately observed performances.
Formal work: length-indexed zero-vector operation
An engineer declares the reusable operation zeroVector(n) in ordinary language: give it a natural number n; it returns a vector of n real-valued entries, every one zero. In the A.6.1 OperationDeclaration, argument lengthIndex means the requested component count and has ValueKind NaturalNumber. Result zeroVectorResult means the returned zero vector and has the indexed result family FiniteVector(RealScalar, n). The application predicate says that one application binds one n and returns that vector. The dependency law states length(zeroVector(n)) = n, and the zero law states that every indexed entry equals scalar zero. Applicability limits this declaration to finite vectors over the declared RealScalar field.
The declaration imports the exact type-former FiniteVector(RealScalar, n) and its length-index law from FormalSubstrate signature FiniteVectorSubstrate_v2. Remove that provider and neither the result declaration can be interpreted nor the length law replayed, so this is a declaration dependency rather than a background citation. The operation argument and result remain A.6.1 declarations; they are not A.6.5 relation SlotSpecs.
A Lean representation may write the result as Vector Real n. A proof-carrying record representation may write entries: List Real together with lengthProof: entries.length = n.
Because both represent the same operation declaration and no mathematical lens changes the next comparison action, A.6.3.RT alone governs this representation transition. It preserves the result-length index and the all-zero law. Lean binder order, implicit elaboration, record field order, and the location of the length proof are representation-local and need not survive. Stop here: no C.29 result is needed.
If a later comparison uses a named free-module lens to decide algebraic reuse, that changed lens use opens C.29 and must separately state the preserved addition and scalar action and the lost coordinate or layout detail. State a blocked inference only when it passes F.19:4's full guard test.
Practical payoff: formal-methods engineers can fill and inspect the dependent A.6.1 declaration, test its FormalSubstrate dependency, and compare representations.
PrincipleFrame: heat-flow balance
A thermal-modeling team writes a PrincipleFrame for a selected system boundary and interval. Under the explicit assumption that heat is the only net energy transfer, net heat transferred across that boundary during the interval equals the change in stored energy. The frame distinguishes inward and outward transfer. It cites the heat-flow characteristics, units, selected CHR:ReferencePlane and measurement declaration needed to check the balance; Applicability states the modeled systems and conditions under which this assumption and balance hold.
A comparison result may show that the residual is below the chosen tolerance. The comparator and tolerance remain under their direct comparison and measurement patterns; operation admission remains under A.6.1, and a gate-passage verdict remains under A.21/C.11. If a laboratory measurement sense is proposed for use in a plant-model sense, resolve both F.17 local senses and apply F.9. Cite a Bridge only when its predicate obtains; state the bounded use and any preservation or loss of sign convention, unit, and boundary interpretation separately.
Practical payoff: the physical principle remains reusable while the measurement setup, comparator, run decision, and cross-scheme transport can change or fail independently.
Reduced ordinary-use case
The sentence During Shift-17, Robot-7 is assigned as inspector through InspectionAssignment-17 is enough for a task that only reports whether the direct MaintenanceInspectionAssignment predicate holds for its participants during that episode. Stop there.
If a staffing assertion and an F.6 Work-attribution consumer must reuse the same participant meanings and assignment laws, cite that direct species' existing RelationSignature.
If later Work attribution or history must distinguish this assignment from a later reassignment, apply A.2.1's direct occurrence-identity rule and refer to the distinguished episode.
A roster-row id that merely points to the assertion opens neither branch. Each result is complete for its stated task; the shorter result is not an incomplete signature.
Bias-Annotation
Scope declaration: Universal across FPF-governed domains.
- Gov. Favors making the direct governor of declaration membership, declared content, and neighboring claims inspectable, together with explicit dependencies. Counter-risk: declaration administration can grow beyond reuse value. Mitigation: add
SignatureManifestonly for dependency. - Arch. Favors a small declaration core with direct neighboring patterns. Counter-risk: the signature becomes a central container. Mitigation: keep realization, work, evaluation, and publication with their direct patterns.
- Onto-Epist. Favors separation of declaration, subject, occurrence, assertion and representation. Counter-risk: excessive explicitness. Mitigation: keep the direct assertion unless the receiving use needs reusable declaration content or explicit occurrence identity.
- Prag. Favors reusable named SlotSpecs and laws. Counter-risk: one-off work becomes formal paperwork. Mitigation: ordinary direct sentences remain sufficient.
- Did. Favors the four content groups and local mantra. Counter-risk: readers treat the mnemonic order as a required execution order. Mitigation: use A.22.CGUS for a question about continuation conditions; actual execution remains a separate Work or Transformation claim.
- Context transport. Interpret the signature's claims under the effective
ReferenceSchemeand use them within their stated scope. Counter-risk: the same label in another context is treated as equivalent or safely substitutable. Mitigation: when a proposed reuse relates two F.17 local senses, test the direct F.9 predicate and cite a Bridge only when it obtains; state direction, rule, tolerated loss, and polarity in a separate bounded-use claim. Without the needed semantic relation and use claim, do not transport the claim by label alone. - Comparability. Two declarations do not become comparable because both expose numbers. Counter-risk: numeric appearance hides incompatible characteristics, measurement procedures, units, scales, comparators, or normalization. Mitigation: apply the current A.17/A.18/C.16 characteristic, measurement, and unit-and-scale patterns and A.19.CPM/A.19.UNM comparison and normalization patterns as the case requires, then state the resulting comparison boundary; keep their detailed legality and result-shape rules with those subject patterns.
- Register. Make technical declaration blocks and worked cases readable for their intended use. Counter-risk: a technically correct block remains unusable without private decoding. Mitigation: apply F.19's connected reading and local revalidation. Unpack decisive FPF terms or add an ordinary explanation only when needed to recover the claim or action and its relevant result; preserve the governed object, subject pattern, admissible use, and practical action.
Each worked declaration has its own C.2.1 identity, which remains independent of its publication form.
Conformance Checklist
- Declaration object. The text identifies one
U.Signatureepisteme and oneEntityOfConcernRef. - Identity. Content, EntityOfConcern, and effective
ReferenceSchemeremain recoverable. - Minimum content.
SubjectKindandRangedValueKind, together with Vocabulary, Laws, and Applicability, carry semantic content rather than empty publication rows.ResultKind,SliceSet, andExtentRuleappear only when their declared distinctions are current. - Optional slice-dependent membership.
SliceSetnames the addressableU.ContextSlicevalues to inspect andExtentRuledeterminesExtension(SubjectKind, slice)only when the same declared kind can have different members across those slices; neither field stands for a generic interval, range, changing dataset, or set representation. - Vocabulary boundary. A declared token is not treated as durable U-kind admission without E.24.UK and its direct pattern.
- Relation declaration. A
RelationSignatureidentifies one already admitted direct relation kind. An admitted derived relation kind has direct subject settlement for participant meanings, base-definition and named-substrate dependencies, obtaining, applicability, and occurrence identity. A predicate-definition episteme is not treated as thatRelationSignature, and the declaration does not assert an occurrence. Every worked case that uses aRelationSignaturealso names the already admitted relation kind, direct governor and predicate, participant meanings, Applicability, occurrence-identity rule, and one ordinary affirmative or negative assertion. A hypothetical domain-local relation kind is labelled and fully settled before the example uses it. - Direct relation-pattern governance. The direct relation pattern defines or constrains obtaining and occurrence identity.
- Typed-declaration boundary. Reused participant meanings are declared inside a
RelationSignatureby A.6.5 SlotSpecs with SlotKind, ValueKind, and refMode. Operation arguments and results remain A.6.1 declaration content. Mathematical operands and field order remain representation-side under A.6.3.RT; C.29 opens only when a named mathematical lens changes the declared lens use or next comparison action. An operand-to-participant correspondence is stated only for an already governed relation claim. - Semantic locality. Meaning uses the effective reference scheme; applicability uses the claim scope and only qualifiers current for the declaration, such as a relevant time interval, selected
CHR:ReferencePlane, or current model-use structure. - Dependency truth. Every import names the provider and exact term or law without which interpretation or law replay fails; every provide entry names a dependent declaration that relies on the introduced term or law. Citations and list order do not qualify. SM-1 through SM-4 hold, including E.5.3 acyclicity for explicit imports. A cycle in another semantic relation is judged under that relation's own governor.
- Realization boundary. Mechanism behavior and admission conditions remain with A.6.1.
- Progressive elaboration. A direct assertion suffices when the task only asks whether the predicate holds. A signature opens when a receiving use needs reusable declaration content. Occurrence identity opens for same-occurrence reference, comparison, qualification, history/change or relation participation. A log or assertion identifier alone opens none of them.
- CGUS boundary. Use the ordinary branch to clarify continuation conditions; continue to formal qualification only when a named later use needs structure identity or replayable results, using the structure and continuation conditions stated in §4.
- Profile boundary. FormalSubstrate and PrincipleFrame remain profiles of
U.Signaturerather than new root kinds. A PrincipleFrame names its postulates and the observable distinctions needed to check them, leaves operation and gate admission with their subject patterns, and uses F.9 for a relation between two F.17 local senses, citing a Bridge only when its direct predicate obtains. - Changed object. Changed claim content carried by the ClaimGraph, EntityOfConcern, or effective reference scheme identifies another episteme. Judge A.6.0 membership for that episteme independently, and assert edition, refinement, supersession, or another relation only when its own predicate obtains. A changed use, identifier, publication form, carrier, provider currentness, or G.11 refresh state does none of those things by itself.
- F.19 self-application and reader use. Apply F.19 by value to every materially changed technical declaration, mantra, checklist instruction, and worked case; revalidate the changed span with its meaning-dependent neighbours. The cold intended reader must be able to recover the same governed object, subject pattern, admissible use, and practical claim or action, including any result that changes that use. Keep ordinary technical wording when it already carries the needed distinctions; unpack terms or add an explanation only when recovery needs it. Use E.10:11 item 16 when the value-substitution question is selected. State a nearby non-use or contrasting case only when F.19:4's full guard test warrants it. A
Plainlabel without that reader-visible recovery does not pass. - Case-level witness. Each worked case names its EntityOfConcern, the direct pattern that defines or constrains the claim being made, and what the practitioner can now write, decide, or inspect. State the nearest category error it rejects only when F.19:4's full guard test warrants that contrast. A domain label or the presence of several case headings is not evidence of cross-domain fit.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits.
- Reusable declarations receive one stable episteme identity.
RelationSignatureepistemes can expose named typed SlotSpecs without forcing every relation occurrence into a record.- Meaning becomes inspectable through the reference scheme; applicability becomes inspectable through the claim scope plus any current time interval, selected
CHR:ReferencePlane, or selected model-use structure. - In physical-modeling practice, an author can reuse one connector-equation FormalSubstrate while keeping a modeled connection assertion, generated equations, and a diagram separate from that declaration.
- In clinical practice, an author can write the bounded patient-episode, intervention, and outcome assertion now, relate an assay-result episteme to that claim through A.2.4/A.10, and defer a
RelationSignatureuntil a direct clinical relation governor exists. - A changed realization, observation, evidence-use relation, or publication can be repaired independently when the declaration's own claim content, EntityOfConcern, and effective reference scheme remain unchanged.
Costs and trade-offs.
- Before choosing a form, determine which result the receiving use needs: a direct assertion, reusable declaration or explicit occurrence identity. These are different contributions; a second consumer or repeated episode is not a universal prerequisite.
- Authors must recover the declared subject and effective reference scheme; a familiar label is not enough.
- A
RelationSignaturecase also requires an already admitted relation kind, direct governor and predicate, participant meanings, Applicability, occurrence-identity rule, and an ordinary assertion. Without that settlement, the author keeps a local claim, predicate definition, or missing-governor blocker instead of inventing SlotSpecs. - Typed reuse adds authoring effort for A.6.5 relation SlotSpecs or A.6.1 operation declarations, plus A.6.0 dependency declarations only when another signature relies on named terms or laws.
- A change to claim content, EntityOfConcern, or effective reference scheme identifies another episteme even when the publication looks identical; authors must separately judge
U.Signaturemembership and any claimed edition, refinement, or supersession relation.
Rationale
The ontic is needed because the same reusable declaration is cited across work occurrences, publication occurrences, and representations. Treating it as only a table-shaped publication form loses identity; treating it as the declared world-side object collapses episteme and EntityOfConcern.
The declaration components answer four different engineering questions. SubjectKind, RangedValueKind, and optional ResultKind identify the declared subject and value or result range.
When slice-dependent membership is current, SliceSet names the addressable context slices and ExtentRule says how the members of the same declared kind are determined at one slice.
Vocabulary supplies reusable names and, for a RelationSignature, named participant SlotSpecs; A.6.1 supplies operation arguments and results for a mechanism declaration.
Laws state the reusable regularities. Applicability states where those regularities are used. Their conceptual separation is stable even when publication layout changes.
RelationSignature is a use of U.Signature because it has the same episteme identity and content duties. Introducing a second root kind would duplicate those duties while leaving obtaining and occurrence identity with direct relation patterns anyway.
A practitioner can begin with a readable relation sentence and add a reusable declaration when reuse creates value.
SoTA-Echoing
Sources:
- JuliaHub, Dyad 3.2 documentation; Modelica Association, Connectors and Connections as historical lineage.
- Lean project, Inductive Types and Structures.
- TypeDB,
relatesstatement. - W3C, SHACL 1.2 Core.
- Almeida, Guizzardi, Sales, and Fonseca, gUFO: A Gentle Foundational Ontology for Semantic Web Knowledge Graphs.
FPF's constructive ontology, C.2.1 episteme identity, A.6.5 relation-slot discipline, A.6.1 operation declaration, and direct relation patterns remain authoritative for the solution.
Relations
- Builds on: A.7, C.2.1, C.3, A.2.6, and A.6.5.
- Governs: reusable
U.Signaturedeclaration epistemes, includingRelationSignatureuse and the FormalSubstrate and PrincipleFrame profiles. - Constrained by: F.19 for the register and usability of materially changed technical declaration blocks, the mantra, checklist instructions, and worked cases. The local result must let the cold intended reader recover the claim or action, decisive governed terms, and practical use; add an ordinary explanation only when needed for that recovery. Use E.10's compact route and rules for unresolved lexical questions.
- Coordinates with: A.6.REL for relation occurrence, A.6.RCD for needed-claim derivation and relation-kind settlement before declaration, A.6.1 for mechanism declaration and realization, A.3.1 for methods, A.15.1 for work, F.9 for explicit bridge use, A.17, A.18, C.16, A.19.CPM, and A.19.UNM for characteristic, scale, comparison, and normalization questions, C.29 for mathematical-lens use, and E.24.UK for durable U-kind admission.
- Described and published through: C.2.1, E.17, and E.24.PUB.
- Evolves with: G.11 for currentness and explicit direct relations between signature editions.
- Used by: C.22 task signatures for A.6.0 declaration identity and content; a changed C.22 discriminator identifies another episteme and establishes an edition only when the direct continuity predicate obtains. Also used by A.19.CPM comparison declarations, A.19.SelectorMechanism selection declarations, C.29 and E.18.1 when their current claim requires a FormalSubstrate declaration, and any pattern that needs reusable vocabulary, laws, applicability, or relation SlotSpecs. Specialized operation declarations remain under A.6.1 rather than A.6.0.
A.6.0:End
U.Mechanism - Reusable Law-Governed Operation Declaration
Status: Stable
Pattern kind. Ontic declaration pattern.
Builds on. A.6.0 for signature identity and content, C.2.1 for episteme identity, and A.2.6 for claim scope.
Problem frame
An engineer needs a reusable declaration of operations, their typed argument and result positions, the laws they preserve, and the conditions under which an operation is admitted. The declared operation family may be used for physical modeling, clinical calculation, selection, normalization, or another named engineering use.
Use this pattern when the working question is:
What operation family is being declared, which laws govern it, and under which claim scope, time and mechanism conditions may its operations be used, including a selected
CHR:ReferencePlanewhen that distinction is current?
Primary governed object. One claim-bearing episteme being identified as U.Mechanism. Inside that episteme's C.2.1 identity, its EntityOfConcernRef identifies the declared operation family. U.Mechanism is a dependent durable U-kind governed through the U.Signature identity and content settlement; it adds operation and admission semantics to the reusable declaration.
The episteme and the declared operation family remain distinct: the episteme carries the declaration, while EntityOfConcernRef identifies the family.
Primary working reader and concern. The reader is an engineer who needs to reuse or compare an operation declaration without confusing it with the method that uses it, the entity that realizes it, the work that evaluates it, or a publication that presents it.
The first useful move is to name the declared operation family, its SubjectKind, and its family-level RangedValueKind, then state its OperationAlgebra, LawSet, AdmissibilityConditions, and Applicability. Add a family-level ResultKind only when one distinct result kind is current.
For each reused operation, point to the argument or result meaning that carries the SubjectKind, RangedValueKind, or ResultKind meaning, then declare every additional argument and result meaning and ValueKind. Also state the operation's ApplicationPredicate, ApplicationExtentRule, and ApplicationIdentityRule. ApplicationExtentRule maps the facts at one independently grounded application locus to the semantically relevant boundary or interval over which that operation's predicate obtains; it is not the signature-level ExtentRule that determines kind membership at a selected context slice.
Open an actual operation-application binding only when one application has been independently identified and a downstream claim says which value that application used or returned.
Add a dependency manifest only when removing one named provider term or law would make this declaration uninterpretable or prevent law replay; shared wording or a background citation is not a dependency.
What goes wrong if this pattern is missed: implementation behavior, method instructions, evaluation outcomes, and publication metadata enter the declaration as if they were operation laws. A later user cannot tell whether the declaration changed, one realization failed, or only the evidence became stale.
What this buys: the declaration can remain stable while methods, realizers, evaluations, descriptions, and publications evolve under their own patterns.
Do not use this pattern merely because prose contains words such as mechanism, algorithm, process, or workflow. Recover the current object first. Use A.3.1 when the current object is a semantic way of doing, A.15.1 when it is performed work, and the direct system or episteme pattern when it is a physical assembly or a model description.
Problem
FPF needs reusable operation declarations for scope, normalization, selection, comparison, physical modeling, and other domains. Without a common definition of this kind of declaration:
- an operation name does not reveal its typed arguments or result;
- declared laws are mixed with admission predicates and evaluation outcomes;
- applicability is hidden behind an unexplained context label;
- a realization is confused with the declaration it realizes;
- mathematical notation or imperative prose is overread as an executable sequence;
- descriptions, publications, methods, and dated work acquire mechanism identity by proximity.
Make the distinctions below explicit as the receiving use requires.
Forces
Solution
Use U.Mechanism as the dependent durable U-kind for a reusable law-governed operation declaration episteme. Identify it through C.2.1. Put operation vocabulary, typed argument and result declarations, application rules, laws, admission conditions, and applicability in its content.
Keep each actual application and binding, realizing entity and realization occurrence, method, Work, evaluation, evidence, description, representation, and publication as its own object or relation. Section 4.7 handles each question under the pattern that can identify it.
Local mechanism mantra. Name the operation family and subject. Declare arguments, results, application rules, laws, admission conditions, and applicability. Bind actual values only in one independently identified application. State a realization relation only when a named realizer satisfies its predicate. Keep method, work, evidence, description, and publication separate.
This mantra is Plain recall wording. Its imperatives summarize the distinctions; any prescribed order of performed work belongs to the direct method-description or work-plan pattern.
When a receiving question concerns available continuations and their conditions, use A.22.CGUS's ordinary branch. Continue to formal qualification only when a named later use needs structure identity or replayable results; then identify the A.22 structure, its local loci and at least two potential continuations under the selected relations and constraints. A post-qualification presentation may show one traversal as a separate DemonstrativeUnfoldingSlice@Context.
Admit and identify U.Mechanism
U.Mechanism is a dependent durable U-kind governed through U.Signature and therefore through U.Episteme. Its identity is:
The dependence reuses the U.Signature identity settlement and subject pattern. It is not parthood and does not make U.Mechanism a root beside U.Episteme.
Use this early object-and-relation guide:
A machine part does not become U.Mechanism by being called a mechanism. For example, a pump assembly remains a U.System; this pattern defines or constrains a reusable operation declaration to which a realizing entity may be related while retaining its direct kind.
State mechanism content
The following is a conceptual content outline, not a mandatory record or publication layout.
The content components have distinct jobs:
Choose the three headline fields before listing operation positions. In plain terms: name the common kind of thing this operation family is about in SubjectKind, and name the common value domain over which the family ranges in RangedValueKind. Add ResultKind only when one distinct family-level result kind is current.
For every operation, point to the argument or result meaning that realizes each current family-level declaration; extra arguments and results keep their own ValueKinds. A collection or reference wrapper likewise keeps its own ValueKind and must state how it refers to or contains the family-level kind.
If the operations do not share one truthful subject-and-range pair, do not hide that fact in a union, Any, or an input or output list: split the declaration or stop. If several result kinds are only operation-local, omit the singular family-level ResultKind and keep them in their ResultDeclarations.
OperationDeclaration, ArgumentDeclaration, and ResultDeclaration name parts of the declaration content. A bindingDesignationRule says whether a binding carries the value itself or one governed reference that resolves to it; a stored token or compatible reference does not establish a binding. An operation index may be derived from the operation designators for retrieval, but it is not another semantic content group.
A.6.5 SlotSpecs declare participant meanings only inside a RelationSignature for an already governed direct relation kind. A.6.1 argument and result declarations govern the named values of an operation application. Mathematical operand order remains representation-local. Use A.6.3.RT for a same-EntityOfConcern representation transition and C.29 only for a mathematical-lens use; state a correspondence when the representation must preserve the independently declared operation meanings.
Keep neighboring facts outside mechanism identity-bearing content. Cite an F.9 Bridge only when two SchemeSenseCell values are being related across semantic contexts and its predicate obtains. Cite an actual application binding only when the downstream claim asserts which value the application used or returned. Evaluation, subject participation, evidence use, and realization each require their own obtaining predicate.
A new neighboring occurrence or binding does not change U.Mechanism identity unless it reveals changed semantic content.
A stable designator can refer to a mechanism episteme; file path, publication state, release label, and layout do not enter episteme identity merely because a tool stores them beside the content.
State meaning and applicability without a generic context slot
Meaning and applicability answer different questions:
- the effective
ReferenceSchemedetermines how the declaration content is interpreted; U.ClaimScopespecifies the conditions under which the use claim applies. Identify the entities and relations the claim concerns separately. To use the claim in one case, test itsU.ContextSlicefor membership in that scope.- the applicability interval states when that use is claimed;
- the selected
CHR:ReferencePlanestates the world, conceptual, or epistemic referent mode when that distinction is current; - mechanism-specific conditions state assumptions that affect operation admission;
- optional
modelUseStructureRef : SelectedStructureReferencecites one selectedBoundedModelUseStructureonly when its relations delimit or change mechanism use.
Do not replace these values with one generic context field. Do not add modelUseStructureRef merely to preserve an old context column.
When one proposed receiving use spans different local senses, take these steps.
First, use F.9 only to test the SchemeSenseCell correspondence and identify an obtaining Bridge.
Second, state a separate current C.2.1 claim about whether that Bridge suits this use, in this direction, under this correspondence rule, and within this loss tolerance; give the claim affirmative or negative polarity.
Third, choose the reliance branch from the consequence of the proposed use:
- for ordinary reliance with no actual assurance claim, use A.10. Name the evidence-provenance relation, bounded use, window and reopen or stop condition; proceed only with
RelianceDisposition=pass. State an unsupported stronger use only when F.19's independent-ground, plausible-reader and contribution tests require that guard; - when an actual named assurance claim about this use is current, use B.3 and require its result for that same bounded assurance use. Whether a direct domain rule requires the assurance claim or it is otherwise current, identify it independently under B.3.
A.6.1 AdmissibilityConditions decide whether the proposed operation application is admitted. Its actual application and bindings remain under A.6.1, while dated Work remains under A.15.1; the Bridge, bounded-use claim, and reliance result retain only their own predicates and results.
For example, let BridgeDoseTerms-7 be the obtaining F.9 Bridge between cells WardDoseValueCell and ProtocolDoseValueCell under its BridgePredicateProfile. The separate C.2.1 claim for reusing the protocol mechanism in the ward-to-protocol prescribing direction is negative because the use rule cannot meet the ward's zero tolerance for changing the dose unit or scale. That reuse stops before reliance.
It also stops when the bounded-use claim is absent, when A.10 does not return RelianceDisposition=pass for an ordinary bounded use, or, when an actual named assurance claim is current, when B.3 has no AssuranceResult for the same use with disposition=supported-for-use.
None of those outcomes makes the Bridge cease to obtain or makes an operation application admitted or actual.
A changed effective ReferenceScheme identifies another mechanism episteme through C.2.1. A changed selected CHR:ReferencePlane reopens the CHR assertion; a changed BoundedModelUseStructure requires A.1.1/A.22 assertions.
If the project also claims that a plane transition or model-use change relation occurred, name its admitted predicate and participants or stop that claim.
For any comparison or change relation claimed, name its source and target objects, the comparison or relation asserted, and the meaning or structure it preserves and loses. Any reliability claim, including its Formality and Guarantee, remains under its direct reliability relation.
Use A.19 and the applicable measurement and scale patterns for numeric comparison or aggregation. Identify the permitted operations and any order they require before use, make units compatible where the operation requires it, and identify the governing scalarization relation for a reduction to one score.
Separate laws, admission, evaluation, and evidence
LawSet states regularities of the declared operations. AdmissibilityConditions decide whether one proposed application may proceed under current values and declared conditions. If a mechanism uses admit, degrade, or abstain, those are declared application dispositions with declared effects; they are not automatically the operation's result algebra.
A recognition-evaluation operation declares the finite result-value domain true | false | unknown. It returns true when its governed bound argument values determine that the candidate satisfies the selected world-side criterion, false when they determine that the candidate fails it, and unknown when missing evidence or an unavailable dependency prevents either determination. Here unknown means that the governed values determined neither satisfaction nor failure; the application may still be admitted and occur. Candidate status and any receiving-work disposition remain separately governed.
World-side satisfaction or failure follows the direct criterion and candidate facts whether or not the project can currently determine them. Measurements, evidence, and assurance may support or warrant claims about those facts or about the returned judgment.
If an evidence or interpretation-basis episteme is also a declared operation argument, its actual binding relates the application to that episteme as used under the declared argument meaning. Criterion satisfaction, evidence support or warrant, and candidate identity remain independently governed.
A separately materialized evaluation-result or classification-assertion episteme remains under C.2.1. Its claim content may state the returned value, while evidence and assurance relations govern support or warrant and G.11 governs edition currentness. For this three-valued operation, neither the separately materialized episteme nor its currentness is the returned value itself.
Thus a mechanism realization may obtain while current evidence is insufficient to rely on it, and an evaluation may return a value without changing mechanism identity.
Bind one actual operation application
Use the readable direct forms first:
An application is an occurrence of the ApplicationPredicate declared for operation O. Its declaration supplies the identity and extent rules, including the relevant application locus and boundary: for example, one physical cycle, one calculation invocation from call to return, or one comparison act from selected operands to returned judgment. Use the domain facts that delimit the application.
The phrase operation application admits no universal application relation kind or work record. A trace identifier may designate the occurrence, but storage convention alone supplies no identity rule.
If the declaration lacks the predicate, extent rule or identity rule needed at the receiving claim's granularity, leave that application claim unestablished and name the missing rule; a method name, plan row, log or nearby result cannot supply it by proximity.
An operation-application binding is an occurrence of one declaration-local binding predicate under that application. Its direct participants are the application occurrence and the bound entity or value. The mechanism episteme and the named argument or result declaration govern the predicate; they are not substituted for the actual value.
An argument binding obtains only when the value participates in P under the declared argument meaning, resolves under the binding designation rule, satisfies the declared ValueKind and cardinality, and lies within P's governed extent.
A result binding obtains only when P returns that value under the declared result meaning; type compatibility, a planned filling, a method-description field, a stored reference, or a matching token establishes neither binding.
One binding occurrence is identified by <exactApplicationOccurrence, exactMechanismEpisteme, operationDesignator, argumentOrResultDesignator, exactBoundValue, maximalContinuousBindingExtent>. The extent lies within the application extent; a result-binding extent cannot begin before that result is returned. Repeated applications remain distinct through their independently governed application identities, and the same value bound under two declaration-local meanings yields two distinct bindings. A declaration may state a different cardinality or binding-continuity rule only when that semantics is part of the operation declaration.
The controlled phrase operation-application binding names only this family of declaration-local binding occurrences. Public work-participant, input, output, result, evidence, and production relations remain with their direct patterns. A result binding relates the application to the value it returned. Production or entity-identity inception, a result episteme, and later reliance each require their own governing claims.
Treat a claim about dated Work separately from the application and its bindings. When that Work claim is current, recover each performer under A.13 and establish Work admission under A.15.1. Use F.6 through the same obtaining A.13 assignment only when this account or its receiving use needs precise assignment-bound attribution. Missing or failed F.6 alone leaves independently admitted Work intact; recheck an admission premise only when the same finding questions it.
Any additional enactment, participation, resource-use, continuity or Work-mereology claim needs its own obtaining predicate. For the claimed participation at the required granularity, distinguish a missing subject-relation or declaration-local binding rule, a known predicate failure and missing case facts.
State realization as a direct relation
Use the readable direct form first:
The relation has these positions when typed reuse needs them:
The realization predicate obtains when the realizing entity provides the declared operations and preserves the declared laws for admitted uses in the stated scope and interval.
A refined mechanism declaration may narrow Applicability or strengthen laws or admission conditions only with the preserved and changed semantic content stated explicitly. The realizing entity realizes the mechanism episteme named in the relation. Any refinement or edition relation is a separate claim under its direct predicate.
If a claimed realization relaxes a declared law, bypasses an admission condition, or relies on undeclared operation meanings, return to the realization predicate. State that the relation does not obtain when that predicate is known false; leave the claim unresolved when required meanings or case facts are unavailable.
The non-derived participants are the declared mechanism, realizing entity, and realization scope. When a later use needs one occurrence distinguished from another, its direct identity is <declaredMechanism, realizingEntity, realizationScope, maximalContinuousRealizationInterval>. The interval is derived as the maximal continuous interval over which the realization predicate obtains. A new evaluation window or a gap in available evidence does not split the occurrence; demonstrated cessation followed by later realization does.
Ordinary use stops at the readable sentence. If another claim must refer to or compare one realization occurrence, the direct relation pattern and A.6.REL govern explicit occurrence identity. Evidence, evaluation, application, and binding occurrences remain supporting or use-side neighbors rather than realization participants.
Keep mechanism, application, method, work, and description questions separate
One project concern can need several linked values. Recover each by its working question:
A MethodDescription may cite a mechanism declaration; that citation alone establishes no Method-selection result. When a selection result is claimed, establish it under its direct rule. If an actual A.6.1 application supplies the result, its declared selector operation and obtaining result or SelectionSlot binding identify the selected Method. A direct constraint relation may separately constrain the Method. An operation may take or return a U.Method only under its declared argument or result meaning; an actual binding must satisfy that meaning.
Planned assignment and actual enactsMethod remain separate claims. For a dated Work that uses the application, apply the A.13/A.15.1 conditions and conditional same-assignment F.6 in §4.5. Add resource use, affected referents, continuity and consequences only when asserted and independently established.
State comparison claims among mechanism declarations
State a mechanism-declaration comparison only when its predicate is defined and the case facts satisfy it. A relation label alone admits neither a relation kind nor an occurrence.
These rows test declaration content; they do not admit a relation kind or occurrence.
If the corpus already admits the comparison relation, use its direct pattern. If one case-specific comparison claim is enough, use A.6.RCD disposition 2 only after its claim subject, constructor, endpoint facts, and preservation facts are recoverable; otherwise preserve the applicable A.6.RCD result, distinguishing missing case information from a missing governor or derivation substrate and from a factually unsupported claim.
When the same predicate must be reused across cases, apply A.6.RCD's reusable predicate-definition branch.
If a downstream use instead needs comparison occurrences with their own identity and no relation kind has been admitted, return missing-governor[mechanism-comparison-occurrence]; a label such as refinement or the adjective direct does not fill that gap.
In every branch, identify the endpoint mechanism epistemes, their effective ReferenceScheme values, claim scope, comparison predicate, and preserved and changed semantic content. Changed C.2.1 identity discriminators identify another episteme. If historical continuation matters to the comparison or receiving use, test the separate EpistemeEditionRelation(earlierMechanismEpisteme, laterMechanismEpisteme) under C.2.1. The two endpoint epistemes remain distinct participants; refinement, extension, equivalence, a shared name, or a later date establishes neither that relation nor one continuing episteme.
Continuing revision and replacement contrast. FixtureSelectionMechanism-R2 has changed claim content relative to FixtureSelectionMechanism-R1, so it is another episteme whose declaration content qualifies it as a mechanism. In the continuing branch, the source use and continuity rule identify which claim, EntityOfConcern and scheme features must be preserved or may change; the case facts satisfy that rule. Revision Work, Method, provenance and change facts can support this test. The obtaining EpistemeEditionRelation(FixtureSelectionMechanism-R1, FixtureSelectionMechanism-R2) lets G.11 follow the lineage.
A proposed application or realization of R2 must satisfy R2's own laws and applicability; an R1 realization supplies no automatic R2 result. Existing claims pinned to R1 keep their referent, and only uses affected by the proposed change require reconsideration.
In the replacement branch, FixtureSelectionMechanism-Alt1 has another C.2.1 identity and no obtaining edition relation to R1. Assess Alt1 under its own applicability and comparison predicate; neither R1 currentness nor realization transfers merely from the replacement.
transport is not a generic A.6.1 mechanism relation. If the current question is cross-context SchemeSenseCell correspondence, identify the two F.17 cells, test the direct F.9 predicate, and cite a Bridge only when it obtains; infer neither mechanism identity nor equivalence from it. A changed effective reference scheme identifies another episteme; changed CHR:ReferencePlane or model-use organization requires its subject pattern. Compare mechanism content only after those endpoints and relations have been recovered.
When a quotient, product, categorical morphism or similar construction serves as a mathematical lens, C.29 governs that use and its preserved and lost structure. A formal construction or notation in its own subject domain retains that domain's rules; its mere presence does not establish a lens use, application, binding, realization occurrence or mechanism kind.
Keep description, representation, and publication separate
U.Mechanism is already an episteme. A second episteme that explains, summarizes, or compares it is a C.2.1 meta-description whose EntityOfConcernRef identifies the mechanism episteme. A diagram, equation set, program, or table is a representation governed by A.6.3 and A.6.3.RT when representation transition matters.
An E.24.PUB publication occurrence makes one selected episteme edition available for its declared audience and use. An independently identified physical or digital carrier bears the expression under PublicationExpressionBearingRelation. When that expression conforms to a selected reusable publication form, it also witnesses PublicationFormBearingRelation; the same expression must witness any form-mediated expression claim used with it to establish availability.
A grouping of several mechanism epistemes and realizations may be selected as a U.Structure or shown through a U.View when that structure or view is current.
Use progressive explicitness
Choose the explicitness needed by the current question:
- A direct sentence names one operation and its condition clearly enough for present work.
- A
U.Signatureis identified when reusable vocabulary, laws, or applicability matter. - A
U.Mechanismis identified when reusable operation and admission semantics matter. - One application and its argument or result bindings are identified only when a downstream claim asserts that the application occurred or that one value participated or was returned.
- A mechanism-realization relation occurrence is explicitly individuated only when another claim relies on that occurrence identity.
These conditions govern different objects. If the receiving question concerns available continuations and their conditions, use the ordinary branch of A.22.CGUS. Continue to formal qualification only when the receiving use needs structure identity or replayable results.
Change the object that changed
When content, EntityOfConcernRef or effective ReferenceScheme changes, C.2.1 identifies the resulting episteme. Judge its U.Signature and U.Mechanism membership from its own declaration content. A changed operation, argument or result declaration, application predicate, identity or extent rule, law, admission predicate, applicability claim or dependency changes episteme identity when its semantic content changes.
Call that later episteme an edition of an earlier mechanism only when the C.2.1 EpistemeEditionRelation obtains. G.11 may then follow the lineage, while a use of the later declaration must satisfy its own conditions. Without an established edition relation, assess the later declaration independently; leave historical continuation unresolved when the needed facts are missing. A shared label, refinement claim, later publication or changed filename alone supplies no continuity.
Treat a new application or binding, new realizer, failed evaluation, new evidence item, changed Work occurrence, returned value, or new publication as a change to that neighboring object and its affected relation. Reconsider the mechanism declaration only when the change overturns relied-on mechanism-content semantics.
Use E.20 when introducing a new mechanism declaration or changing the governing assignment of mechanism semantics. Use G.11 when the question is currentness, freshness, selection of a continuing later episteme, or decay of a relied-on declaration or cited source episteme.
Archetypal Grounding
Physical modeling: thermal connector operations
A physical-modeling team repeatedly uses a thermal connector operation family. The mechanism episteme declares named temperature and heat-flow argument and result meanings with their ValueKinds, connection operations, equality and conservation laws, application identity and extent rules, and admission conditions for unit compatibility and steady-state conduction. Applicability names a U.ClaimScope over the modeled systems, the use interval, selected CHR:ReferencePlane = conceptual for these model-side connector claims, and the steady-state conduction condition; a component port is a modeled participant or locus, not a CHR:ReferencePlane value.
One equation-based model can realize that declaration for simulation use. The model remains distinct from the physical heater and pipe systems it represents. Solver Work, validation measurements and a connection diagram retain their own Work, measurement, evidence-use and representation relations.
Practical payoff: another model can be compared against the same operation and law declaration without treating equation order, solver choice, or a diagram as mechanism identity.
Clinical work: dose-adjustment operations
A clinical team declares a dose-adjustment mechanism over one common patient subject and one common dose-value domain. The headline fields and the heterogeneous operation positions connect as follows; every named ValueKind must already resolve under the effective reference scheme.
Admission conditions state which measurements and qualification intervals make one calculation admissible. Applicability names the patient-population U.ClaimScope, qualification interval, selected CHR:ReferencePlane (normally world for the patient-side use claim), and clinical conditions under which the declaration is used.
A claim-bearing clinical-protocol episteme is a U.MethodDescription only when it describes one admitted U.Method and satisfies A.3.2; its publication form and carrier remain separate.
One clinician's treatment occurrence is work only when the A.15.1 occurrence basis obtains. Laboratory measurement values may be bound as arguments of one admitted calculation application, while the measurement and evidence relations that warrant their use remain separate.
The dose-range result binding relates the application to the range it returned. A prescription and any materialized result episteme require their own governing claims.
Practical payoff: protocol presentation, one treatment occurrence, and the declared calculation laws can change independently.
Manufacturing: fixture selection
A machining team declares a fixture-selection mechanism. Its operations filter candidate fixtures, compare admissible loading envelopes, and return a non-dominated candidate set. Laws preserve units and the partial order over constraints. The admission predicate evaluates true only when current workpiece geometry, machine envelope, and measurement qualification interval are available.
The machinist's setup method and the dated setup work remain separate. A fixture is a system. A selector implementation may realize the mechanism for a stated scope and interval.
Positive realization in plain terms. FixtureSelectorRuntime-12-E3 realizes mechanism episteme FixtureSelectionMechanism-E3 for Cell7FixtureSelection-Q3 during [2026-07-01T08:00Z, 2026-07-19T14:32Z). During that interval the independently identified runtime provided filterCandidates, compareLoadingEnvelopes, and returnNonDominatedSet; every admitted use required current workpiece geometry, the current machine envelope, and a current measurement-qualification interval; and its results preserved the declared unit and constraint-partial-order laws.
If a later claim needs this positive realization occurrence, its identity is <FixtureSelectionMechanism-E3, FixtureSelectorRuntime-12-E3, Cell7FixtureSelection-Q3, [2026-07-01T08:00Z, 2026-07-19T14:32Z)>. The interval is derived, not a fourth writable participant.
Runtime contrast. FixtureSelectorRuntime-12-FastPath-E4 : U.System exposes the same three operation names but accepts a loading-envelope comparison when MeasurementQualificationCurrent is false. It therefore bypasses one declared admission condition and does not realize FixtureSelectionMechanism-E3 for that scope, even if its returned candidate set happens to match E3 in one run.
A missing audit-log segment for E3 instead reopens evidence and warrant under A.10. Without demonstrated cessation or bypass, that gap does not make the world-side realization predicate false or split its occurrence, although the project may have to withhold its positive assertion until warrant recovers. Demonstrated cessation followed by later restored conformity would create a later maximal-continuous realization occurrence.
Practical payoff: the team can replace the implementation while preserving the declared partial-order law, and reject a look-alike implementation that fails the declaration's conditions.
FPF scope and normalization declarations
A.2.6 scope operations and A.19 normalization operations may use the U.Mechanism declaration shape when their direct patterns need reusable operations, laws, admission conditions, and typed results. A.2.6 and A.19 retain their domain semantics. A.6.1 supplies the declaration and realization distinctions; it does not redefine scope or comparison.
Practical payoff: A.2.6 and A.19 remain the governing loci for scope and normalization meaning while reusing the mechanism declaration form.
Publication operations
E.24.PUB may cite a mechanism declaration for operations that assemble, validate, and expose a publication package. The mechanism episteme declares those operations, laws, and admission conditions. The dated publication work, resulting publication use, information carrier, evidence, and currentness relations remain with their direct patterns.
Practical payoff: the declaration captures reusable publication-operation semantics while the released package and carrier retain their direct kinds.
Reduced ordinary use
An engineer states, "this conversion is admitted only for values in the calibrated interval." No later claim reuses an operation family, compares declarations, identifies an actual application, or refers to a realization occurrence. The direct sentence and its governing characteristic and measurement patterns are enough. No mechanism episteme is opened.
Recognition evaluation: Pump #37
A project repeatedly evaluates the A.1 holon-recognition criterion. In ordinary language, one bounded evaluation act applies the selected criterion to Pump #37 and returns true, false, or unknown.
For this replay, resolving HolonRecognitionMechanism-E1_Ref under its effective reference scheme returns mechanism episteme HolonRecognitionMechanism-E1; neither label nor suffix establishes an edition relation. That episteme has SubjectKind = U.Entity, RangedValueKind = RecognitionJudgmentValue, no separate ResultKind, and operation recognizeAdmittedHolonCandidate.
RecognitionJudgmentValue is one local finite U.Kind under C.3, used here as the operation's RangedValueKind; its membership rule admits exactly true, false, and unknown. It is an operation-local kind, not a public U-kind or universal claim-status algebra. Candidate facts, evidence status, episteme-currentness values, and receiving-work dispositions use their direct kinds. The argument and result rows are A.6.1 declarations, not A.6.5 SlotSpecs.
For this mechanism episteme, the declaration-local designation, cardinality, and binding predicates are:
These predicate names are local to HolonRecognitionMechanism-E1; they do not admit public binding relation kinds. Pump_37_Ref can be type-correct without a binding: the candidate predicate is current only when the application uses its resolved referent under the candidate meaning. The same rule applies to each argument, and a result predicate is current only after the application returns that value.
For this mechanism episteme, ApplicationPredicate(P) holds only when bounded evaluation act P fixes exactly one value for every required argument above, applies recognizeAdmittedHolonCandidate from HolonRecognitionMechanism-E1, and returns exactly one RecognitionJudgmentValue. Its ApplicationExtentRule sets the maximal extent from the moment all required argument bindings are fixed and evaluation begins through the terminal judgment return.
Its ApplicationIdentityRule reidentifies one application by <HolonRecognitionMechanism-E1, recognizeAdmittedHolonCandidate, independently grounded evaluation-act locus, maximal application extent>. A later invocation is another application even with the same bound values. A trace token or reused work label can designate an act but cannot merge the two.
For the worked case, Pump37RecognitionApplication-2026-07-21T100000Z designates the evaluation act that began at 10:00:00 and returned at 10:00:04. It used Pump_37_Ref -> Pump_37 : U.Entity, admitted kind U.System, A1-Holons-Criterion-E1_Ref, Pump37-Construction-Facts-E1_Ref, Pump37-Reidentification-Rule-E1_Ref, and Pump37-Interpretation-Basis-E1_Ref. The six argument-binding predicates have maximal continuous extents from 10:00:00 through the terminal return.
A required fastening-relation fact could not be resolved during this act, so the bound values could determine neither satisfaction nor failure. The act returned unknown; the extent of recognitionJudgmentReturned(Pump37RecognitionApplication-2026-07-21T100000Z, unknown) is the terminal return event at 10:00:04 and does not begin earlier.
The application did occur; Pump #37's world-side satisfaction or failure did not change; and unknown is not an admission refusal.
If the project also claims dated classification Work, recover each performer under A.13 and establish Work admission under A.15.1. Use F.6 through the same obtaining A.13 assignment only when this claim or its receiving use needs precise assignment-bound attribution. Missing or failed F.6 alone leaves independently admitted Work intact; recheck an admission premise only when the same finding questions it.
The candidate application binding above can establish Pump #37's participation in the application; add a separate work-to-candidate or resource-use claim only when its declared predicate obtains, and add workContinuityPolicyRef only when an identity or segmentation question needs it.
Any materialized classification-assertion or evaluation-result episteme remains under C.2.1. Evidence and assurance support or warrant its claim content through their own relations, and G.11 tests edition currentness. The result binding relates this application to the judgment it returned. Work and episteme identity, evidence and warrant, world-side criterion satisfaction, and B.2 whole reidentification each remain independently governed.
Practical payoff: another evaluation can reuse the same typed operation while binding another candidate or basis, and evidence loss can change the returned value to unknown without rewriting the candidate or criterion.
Bias-Annotation
Scope declaration: Universal across FPF-governed domains.
- Gov. Favors one direct governing declaration for operation meaning. Counter-risk: every operation becomes a mechanism card. Mitigation: choose the explicitness needed by the current question.
- Arch. Favors separate declaration, realization, method, work, and publication relations. Counter-risk: too many linked objects. Mitigation: make an object's identity or a relation's obtaining explicit only when the current assertion or receiving use needs it.
- Onto-Epist. Favors
U.Mechanismas declaration episteme and preserves the direct kind of its subject and realizer. Counter-risk: the familiar word mechanism is overread as a machine part. Mitigation: the early object-and-relation guide and heterogeneous cases expose the distinction. - Prag. Favors explicit argument and result declarations, application rules, laws, admission conditions, and applicability. Counter-risk: formal apparatus outruns value. Mitigation: ordinary direct statements remain admissible, and an actual binding opens only when a downstream claim asserts which value participated or was returned.
- Did. Favors a short mantra and concrete cases. Counter-risk: readers treat imperative recall as execution order. Mitigation: use A.22.CGUS for a question about continuation conditions, and keep actual Work or Transformation separate.
Conformance Checklist
- Mechanism episteme. One
U.Mechanismepisteme and itsEntityOfConcernRefare recoverable. - Identity. Content, EntityOfConcern, and effective
ReferenceSchemeremain recoverable. - Signature dependence and family-level anchors. The mechanism uses A.6.0 signature content and adds operation and admission semantics without becoming a second root beside
U.Episteme. One truthful family-levelSubjectKindandRangedValueKindpair is connected to the argument or result meanings that realize those declarations; optionalResultKindis present only for one distinct family-level result kind. Additional operation-local ValueKinds remain local. If no common pair exists, split the declaration or stop instead of using a union or generic input or output list. - Typed operation declarations. Every reused operation has declaration-local argument and result meanings, ValueKinds, binding designation rules, and semantic cardinalities when needed. None is an A.6.5 SlotSpec.
- Application semantics. Every claimed application has an application predicate, identity rule, extent rule, and recoverable occurrence boundary.
- Actual bindings. Every claimed actual argument or returned result has an obtaining declaration-local binding with the application and bound value; type compatibility, description, plan, record, or token match is insufficient.
- Binding identity. The application, mechanism episteme, operation designator, argument or result designator, bound value, and maximal continuous binding extent distinguish the binding occurrence.
- Recognition result. A recognition-evaluation declaration uses
true | false | unknownwith the A.1 meanings;unknownrecords that the governed evaluation determined neither satisfaction nor failure. The application and candidate facts remain separately governed; candidate state, evidence status, episteme currentness, and receiving-work disposition use their direct kinds. - Law and admission split. Reusable laws, proposed-application admission predicates, and the operation's own returned value remain distinct.
- Applicability.
U.ClaimScope, time, selectedCHR:ReferencePlanewhen current, and mechanism-specific conditions replace generic context wording. - Optional structure. A model-use structure is cited only when its selected relations delimit or change the receiving mechanism use; it does not replace the effective reference scheme or claim scope.
- Dependency truth. SignatureManifest content names actual imported and provided terms or laws when interpretation or law replay depends on them; apply A.6.0's dependency predicates.
- Realization relation. A realizer keeps its direct kind; the direct relation declares its participants, obtaining predicate, and maximal-continuous-interval identity rule.
- Evaluation and evidence boundary. Evidence availability can change evaluation or warrant without changing world-side satisfaction; an argument binding establishes use, not truth or warrant.
- Method and work boundary. Method, method description, work plan, dated work, actual application, and binding remain separately identifiable. A.6.1 defines neither dated-work identity nor work mereology.
- Result boundary. A result binding relates the application to the value it returned. Production or entity-identity inception uses A.15.PROD; a materialized result episteme uses C.2.1.
- Mechanism comparison claims. Every refinement, conservative-extension, or equivalence claim names endpoint mechanism epistemes, reference schemes, scope, predicate, and preserved and changed content. Historical continuation is stated only through a separately obtaining C.2.1
EpistemeEditionRelation; a comparison or shared label supplies none. The claim uses an already admitted direct relation, the applicable A.6.RCD branch, or the missing-governor stop. Generic mechanismtransportis absent; cross-contextSchemeSenseCellcorrespondence requires F.9. - Mathematical-lens boundary. C.29 governs use of a mathematical object as a lens with selected preserved and lost structure. Mathematical notation or operand order alone does not open that use; a same-EntityOfConcern representation transition uses A.6.3.RT.
- Progressive explicitness. One-off direct use is not forced into a mechanism declaration or application-binding apparatus.
- CGUS boundary. Use the ordinary branch for a question about continuation conditions; continue to formal qualification only when a named later use needs structure identity or replayable results. Mnemonic imperatives remain recall wording.
- Changed object. Declaration, application, binding, realization, evaluation, evidence, work, representation, and publication changes return to the object that changed.
Common Failure Modes and Repairs
Consequences
Benefits.
- Mechanism declarations can remain stable while realizers and work change.
- Physical, clinical, manufacturing, epistemic, and software cases use one declaration discipline without one domain becoming the default ontology.
- Admission, evaluation, and evidence claims become independently inspectable.
- Independently governed cross-reference-scheme, cross-
CHR:ReferencePlane, and cross-model-use comparisons expose preserved and lost meaning without one generic transport relation. - A reader can stop at a direct sentence when durable mechanism identity has no receiving use.
Costs and trade-offs.
- Authors recover the declared subject, effective reference scheme, and applicability rather than relying on one context label.
- A realization claim may need a separate relation and evidence-use statement.
- Mechanism comparison may require explicit mappings among operation argument and result declarations and a C.29 lens.
- Some familiar single-score or implicit-latest practices become unusable until their scale, scorer, or time policy is stated.
Rationale
U.Mechanism earns a dependent durable name because many later patterns rely on one reusable declaration of operations, laws, admission predicates, and applicability. Treating that declaration as only a table format loses identity. Treating it as the realizing system or method makes every implementation change look like a law change.
The declaration uses the U.Signature identity and content settlement because its reusable vocabulary, laws, applicability, and dependencies have the same episteme discipline. It remains a separate dependent U-kind because operation algebra and admission semantics create recurring action-facing claims that an ordinary signature does not govern. This dependence does not assert a C.3 subkind relation by itself.
The actual application and each binding are separate because the stable declaration can be reused with different actual values, and the same value can participate under different declaration-local meanings. Application and binding predicates, extents, and identities distinguish actual participation from a plan, description, reference, compatible type, or result record and keep work-input and work-result relations domain-specific.
The realization relation is separate because several entities can realize the same declaration and one entity can realize it only for a bounded scope and interval. Evidence can change without changing that world-side or semantic relation. This keeps mechanism evolution local and makes failure diagnosis practical.
The practitioner begins with the operation question and adds typed content when reuse needs it. The mantra summarizes these distinctions. A.22.CGUS can clarify continuation conditions; formal qualification is conditional on a later use needing structure identity or replayable results. An enabled continuation, a Work occurrence and an actual Transformation remain separate.
SoTA-Echoing
Relations
- Builds on: A.6.0, C.2.1, and A.2.6.
- Governs: reusable
U.Mechanismdeclaration epistemes, their mechanism-specific content, declaration-local application and binding semantics, operation applications and bindings when current, and direct realization claims. - Coordinates with: A.6.REL for occurrence identity; A.6.RCD for compound comparison claims and missing-relation stops; A.6.5 for RelationSignature SlotSpec discipline; C.3 for operation ValueKinds; A.1 for recognition criteria; A.3.1 and A.3.2 for Method and Method description; A.15.2 and A.15.1 for planned and performed Work; C.2.1 for mechanism epistemes, editions, result epistemes, and bounded Bridge-use claims; A.19 for comparison; F.9 for cross-scheme sense correspondence; A.10 for ordinary reliance; B.3 only for an actual named assurance claim; CHR for selected reference planes; A.1.1 and A.22 for selected model-use structure; C.29 for mathematical-lens use; E.20 for introduction; E.24.PUB for publication; A.22.CGUS for potential-continuation structure and case results; and G.11 for currentness.
- Described and published through: C.2.1, A.6.3, A.6.3.RT, and E.24.PUB.
- Uses for precision restoration: E.10, E.10.ARCH, and F.18 after the current object and relation positions have been recovered.
Transformation-flow use
When an E.18.1 question concerns a mechanism, use A.6.1 to obtain the needed declaration, application, binding or realization result, or its stop. Return that result or stop to the receiving decision or use; select any further question from what remains needed there. Method selection, performed Work, evaluation and evidence, and gate passage retain their direct governors.
When selected relations and applied constraints connect signature, mechanism, method, Work, and evaluation constituents into one independently identified A.22 structure with local loci and at least two potential continuations, apply A.22.CGUS to that structure. A presentation of one traversal through a qualified CGUS is a separate demonstrative slice. The local mechanism mantra remains Plain mnemonic wording unless that wider structure qualifies and the later presentation is about it.
Claim dispositions and return conditions
For a U.Mechanism identification, state that its defining predicate is not satisfied when a required condition is known false; leave the identification unresolved when the text cannot recover a declared operation family, typed argument and result meanings, application rules, laws, admission conditions, and Applicability.
For an actual application or binding, retain the §4.5 missing-governor blocker when a required declaration-local predicate, extent rule, or identity rule is absent. When those rules are present, state any known predicate failure or the missing participants and case facts that leave the claim unresolved.
A realization does not obtain when the entity fails to preserve a declared law for admitted use; leave the realization claim unresolved when its required scope, interval, or case facts cannot be recovered.
Return to the smallest changed object:
- changed content, EntityOfConcern or effective reference scheme identifies another C.2.1 episteme; judge its mechanism membership from the new content and historical continuation through the separate edition predicate. Missing continuity facts leave that claim unresolved, while assessment of the declaration can proceed independently;
- cross-context
SchemeSenseCellcorrespondence requires F.9; a selectedCHR:ReferencePlanechange requires CHR, and a model-use-structure change requires A.1.1/A.22. An asserted transition or use relation must name its predicate and participants or stop; none becomes a generic mechanism-transport claim; - an application or binding returns to its declaration-local predicate, extent, and identity rules; if a required rule is absent for the claimed actual use at its required granularity, retain the missing-governor blocker rather than widen A.6.1 into a universal work-participant relation;
- realizer capability or realization scope returns to the direct realization relation;
- evaluation and evidence currentness require their predicates and G.11 when currentness is the claim;
- method and work changes require A.3.1, A.15.2, or A.15.1;
- representation and publication changes require A.6.3, A.6.3.RT, or E.24.PUB;
- a changed governing-definition assignment requires E.20.
A.6.1:End
Effect-Free Episteme Morphing: Laws for Mathematical Relations Between Epistemes
Status: Stable Type: Definitional pattern
One-line summary. Effect-free episteme morphing (EFEM) is a local mathematical discipline for law-constrained arrows between epistemes. It compares what the source and receiving epistemes say, what they concern, and the schemes that make their claims interpretable, then states the allowed ClaimGraph difference. If its rule needs grounding, representation, conformance, or another separately obtaining relation, it names and reads that occurrence without changing it. The declaration, arrow, use claim, operation application, and performed Work remain distinct.
Use this pattern when a project needs to state and reuse a law-constrained mathematical relation between two epistemes while keeping that arrow distinct from a claim that it suits one use, an operation application, publication, and performed Work.
First useful move. Identify the two endpoint epistemes, compare their claim content, EntitiesOfConcern and effective schemes, then state the arrow rule and laws required by the receiving use. A direct wording comparison or publication rendering can remain under its own pattern when no such mathematical relation is needed.
What goes wrong if missed. A view, retargeting, refinement, representation change, publication rendering, mechanism application, or work occurrence is treated as the same operation, so the project can no longer tell whether the EntityOfConcern changed or only the episteme changed.
What this buys. EFEM gives one law-constrained episteme-to-episteme morphism discipline with explicit preserve/retarget mode, boundaries among actual values, declaration-local participant meanings, and references, plus conservativity and composition conditions.
Builds on.
- A.6.0
U.Signaturefor subject, vocabulary, laws, and applicability. - A.6.1
U.Mechanism. - A.6.5 for declaration-local SlotSpecs.
- C.2.1 for
U.Epistemeidentity and direct constitution, empirical-grounding, and edition relations. - E.10.D2 for the EntityOfConcern, Description-episteme, describing-use, and specification-use boundary.
- C.3 plus F.9 for kind-level and cross-local reasoning.
Used by. A.6.3 epistemic viewing; A.6.4 EntityOfConcern retargeting; E.17.0 multi-view describing; E.17 (MVPK); and E.18 structural reinterpretation over transformation-flow structure.
EntityOfConcern change-mode discipline. EFEM classifies each arrow as preserve or retarget by comparing the C.2.1 EntitiesOfConcern resolved from its endpoint references.
Object settlement. EFEM and EpMorphism are local mathematical classes defined here in the selected formal substrate, not admitted durable U-kinds. U.Episteme is reused from C.2.1. An A.6.0 FormalSubstrate signature that declares EFEM vocabulary and laws is a separate episteme; one arrow, one use-specific assertion about that arrow, any operation application, performed Work, and publication remain separate objects under their direct governors.
Problem frame
FPF repeatedly needs to relate one episteme to another, often alongside a separately described operation that produced the receiving episteme:
- turning an informal method description into a more formal specification;
- projecting a large system description into a smaller “for‑safety‑officer” view;
- re‑expressing the same behavioural model in a different calculus or notation;
- relating an analysis about one subsystem to an analysis about another; use A.6.4 for a claimed receiving use and for judging a current case against its bounded-use assertion.
All of these can be described by episteme-to-episteme mathematical arrows. The arrow relates epistemes and states its laws; it does not itself change an episteme, measure, execute, or actuate. Any operation application and Work remain separate.
Without one reusable local discipline for such arrows:
- each family (KD‑CAL, E.18, MVPK, discipline packs) reinvents its own notion of “projection”, “reinterpretation”, or “refinement”;
- laws about which parts of the source and receiving epistemes may differ, and which grounding or reference-plane facts their rules read and compare, fragment across the spec;
- cross‑family reasoning (e.g. “this E.18 structural reinterpretation is a retargeting, not a view”) becomes brittle and ad‑hoc.
Problem
Without EFEM:
-
No single place for “effect‑free” discipline. The laws for mathematical relations between epistemes are otherwise scattered or implicit; any operation application remains separate.
-
Endpoint EntityOfConcern identity or difference is unclear. Some arrow families have endpoint epistemes about the same EntityOfConcern; others have endpoints about independently different entities. Without a common
EntityOfConcernChangeModeclassification, a relation that looks like a representation change can hide a different receiving EntityOfConcern. -
No functorial backbone. To compose arrows from MVPK, KD-CAL or E.18, the receiving use needs compatible identity, composition, purity, conservativity and formal-domain conditions. Any repeat law must also be stated for the arrow family.
-
Slot/Ref confusion. C.2.1 identifies an episteme through claim content, one EntityOfConcern, and one effective ReferenceScheme. A.6.5 SlotSpecs apply only inside a reusable relation declaration. Laws for projection or retargeting that rely on unnamed fields or tuple positions therefore hide which parts of the source and receiving epistemes are being compared and which separately obtaining facts the rule reads.
The result: engineers and tool builders can no longer tell whether a mathematical relation keeps the same EntityOfConcern, identifies a different receiving one, or merely accompanies an operation. For a receiving-use claim about an arrow whose endpoints concern different entities, state the separate A.6.4 bounded-use assertion. When judging a current case, compare its facts with that assertion.
Forces
-
Epistemic purity vs operational power. Effect-free episteme arrows are useful because their laws can be reasoned about algebraically and composed. If a use needs I/O, solver calls, measurements, or another effect, describe the needed activity separately. Identify any actual A.6.1 application when its declaration applies and any
U.Workonly under its independent admission conditions. -
Preserve vs retarget. A viewing arrow has endpoint epistemes with the same EntityOfConcern; a retargeting arrow has independently different ones. For a claimed receiving use, a separate A.6.4 bounded-use assertion states the invariant, visible loss, receiving use, conditions, and affirmative or negative polarity. When a current case is judged, compare its facts with that assertion and report
satisfies,fails, orcannot decide. -
Conservativity vs usefulness. EFEM should be conservative: no new commitments about the EntityOfConcern beyond what the identified source ClaimGraphs and admitted facts license under the named schemes. The receiving ClaimGraph may factor, aggregate, normalize, or re-express source content and may use a different representation when the loss and interpretation rule are explicit. Any operation or Work that produces that receiving episteme remains separate.
-
Locality vs reference planes and Bridges. Interpret each ClaimGraph through its episteme's effective ReferenceScheme (C.2.1). When a use relates two source-local senses, test the direct F.9 predicate and cite a Bridge only when it obtains; state the bounded-use claim and any reliance separately. When a use crosses a ReferencePlane, cite its applicable plane relation. EFEM cannot hide either relation inside a “pure” content rewrite, and a local-sense or plane difference alone creates neither one.
-
EntityOfConcern, Description episteme and specification use. The EntityOfConcern is distinct from a Description episteme about it; the EntityOfConcern itself may be
U.Epistemewhen an episteme is under concern....Descriptionnames a Description episteme, and...Specnames one admitted for specification use only when its claims are checkable and the named harness or validation relation can test them. EFEM compares what the two epistemes say, what they concern, and their effective schemes; it states what remains the same and what differs. When grounding or a describing-use viewpoint matters, name the relation occurrence or use qualification on each side and compare its facts. Any change to that occurrence follows its direct relation pattern; viewpoint selection and conformance require their own claims (A.7, E.10.D2).
Solution — define one local arrow discipline
Informal definition
Definition. An effect-free episteme morphism is a local mathematical arrow
f : X -> Ybetween two epistemes. Under its selected formal substrate, it states how claim content, the EntityOfConcern, and the effective interpretation rules of each episteme, and any representation languages needed for this comparison correspond. Its content is this mathematical relation and its laws. Any Work, mechanism application, or episteme creation is a separate fact under its direct governor.
This is a local mathematical class defined here in the selected formal substrate, not an admitted durable U-kind. The pattern keeps the short name EFEM for that class. A reusable A.6.0 FormalSubstrate signature may declare its vocabulary and P0-P5 laws, but that signature episteme is not the class and is not one arrow.
An arrow in this class:
- has domain and codomain epistemes identified under C.2.1;
- is effect-free: no Work, mechanism application, system change, or carrier mutation follows from the arrow;
- states the conservativity rule it claims;
- obeys the declared identity and composition laws; and
- is classified locally by
EntityOfConcernChangeModeaspreserveorretarget.
Within the selected formal substrate, one arrow is identified by its domain, codomain, arrow rule or designator, and declared formal equivalence. Two arrows can have the same endpoints and still be different. Changing a claim about whether the same arrow is suitable for another use does not reidentify the arrow.
The ordinary FPF objects remain separate:
fis the local mathematical arrow;- the A.6.0 FormalSubstrate signature is a C.2.1 episteme declaring reusable vocabulary and laws for the arrow family;
- a C.2.1 bounded-use assertion
qaboutfis another episteme; its ClaimGraph states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity; - a current-case judgement separately compares facts with
qand returnssatisfies,fails, orcannot decide; - an operation application and any Work that computes, authors, or changes an episteme are identified only when they occur.
The A.6.3 viewing branch has endpoint epistemes about the same EntityOfConcern. The A.6.4 retargeting branch has endpoints about independently different entities. A receiving-use claim adds the separate bounded-use assertion q; a judgement about a current case tests its facts against q.
When the endpoint epistemes serve as models, use B.5.MR for a refinement or abstraction claim. Recover the assertions and admitted answers at each endpoint, and establish the interpretation used to compare them. More formal or checkable wording alone does not establish that one model is more concrete.
Direct signature components (A.6.0 alignment)
When a receiving use needs a reusable formal declaration, an A.6.0 U.Signature(profile=FormalSubstrate) episteme may declare this local arrow family. Its direct declaration components are:
SubjectKind here is a type inside the selected formal substrate, not a durable FPF U-kind. Add SliceSet and ExtentRule only if one declared local type has slice-varying membership; do not use them to hide a use-specific suitability claim.
Vocabulary.
U.Episteme— the domain and codomain values.EpMorphism— the local formal type of arrows in the selected substrate.EntityOfConcernChangeMode = {preserve, retarget}— a local two-value classification of one arrow, derived from its resolved endpoint EntitiesOfConcern rather than a durable U-kind or aU.Characteristic.Ep— the selected category whose objects are the admitted epistemes and whose arrows are the admittedEpMorphismvalues. Call it a category only when it contains the required identities and is closed under every declared composition.EoCBase— the endpoint-only thin category used to compare EntityOfConcern identity. Its objects are the independently resolved EntitiesOfConcern represented in the substrate. Between every ordered pair of admitted objectsA,Bit has one formal endpoint arrowu_{A,B};u_{A,A}is the identity, and composition follows endpoints. These arrows are not independently meaningful domain or world-side relations.dom(f)andcod(f)— the endpoint epistemes;id_Xandcompose(g,f)— the declared identity and composition operations.α : Ep -> EoCBase— the declared mapping on objects and arrows.α(X)is X's EntityOfConcern afterentityOfConcernRef(X)resolves it. Forf : X -> Y,α(f)is the unique endpoint arrowu_{α(X),α(Y)}. It deliberately forgets f's arrow rule; different Ep arrows with the same endpoint EntitiesOfConcern therefore have the same image.
For each arrow, recover the C.2.1 identity values of X and Y and state which identity-bearing values or ClaimGraph parts are preserved or differ. If the arrow rule uses a neighboring relation, name its predicate and participants on each side and state which endpoint facts it reads or compares.
Equal or different endpoint profiles do not mean that the arrow changed a relation occurrence or made it obtain or cease; any relation change and producing application or Work remain under their direct patterns.
SubjectRef remains only a legacy source projection; resolve it to the episteme and EntityOfConcern.
A claim that f is suitable for one use is a separate C.2.1 bounded-use assertion q; a current-case judgement separately tests facts against it.
A.6.1 governs the application occurrence and its argument and result bindings when those facts are current; the applicable system and Work patterns govern the performing system and performed Work.
The A.6.0 signature and the mathematical arrow f : X -> Y remain the reusable declaration and relation.
Laws and applicability. P0-P5 below govern the local arrow class. A.6.5 SlotSpecs enter only when a reusable direct-relation declaration is current; they are not fields of X, Y, or f.
Laws P0–P5 (normative)
All laws below test membership in the local EFEM arrow class under the selected formal substrate. They do not assert membership in a durable U-kind.
P0 — Typed episteme, endpoint-value, and relation-read profile (C.2.1-grounded)
For any arrow f : X→Y presented as an effect-free episteme morphism:
-
Typed epistemes.
XandYare epistemes of declared kindsK_X, K_Y : U.EpistemeKind, each identified under C.2.1 by claim content, one EntityOfConcern, and one effective ReferenceScheme. Grounding and representation relations are added only when current; a viewpoint selected for a named describing use remains outside episteme identity. -
Value and use projection. For each episteme
E—and separately for a named describing use when one is current—EFEM laws may refer to:content(E)— E's identity-bearing claim content recovered under C.2.1:4.1.1;entityOfConcernRef(E) : U.EntityRef— designates E's EntityOfConcern;selectedViewpointRef?(use) : U.ViewpointRef— only when the named describing use selects one viewpoint; this is not a component of E's identity;referenceScheme(E)— the effective designation and interpretation rules recovered for E under C.2.1:4.1.1;representationLanguageRef?(use, endpoint, expression) : U.EntityRef— its referent must satisfy RepresentationLanguage under E.5.2.L:4.3. When the comparison needs the language selected for an expression, identify the endpoint, the expression used there and the conventions selected in this use. A single episteme can be expressed in several languages. Resolve the reference with the applicable binding. C.29 governs any mathematical-lens use.- a separately current neighboring fact — name the
EpistemeEditionRelation, A.10 evidence or provenance relation, or other governed predicate and its participants when the arrow family reads or compares it; do not collect these facts in a generic projection. If E asserts such a fact, that assertion is already part ofcontent(E).
Content, EntityOfConcern and effective interpretation rules are recovered from the episteme at the endpoint. A describing use can select a viewpoint. If the law uses the language of an expression, resolve it for the expression and endpoint selected in that use. Establish each further relation on its own grounds. The arrow family's declared endpoint kinds and predicates determine admissibility. If its law additionally classifies content or scheme candidates for substitution, recover that classification's own domain and criterion; endpoint membership supplies no general constituent ValueKind. C.2.1:4.2.1 governs that stronger typed use.
When grounding matters, name the grounding relation, its grounding holon, and the claims it covers; grounding is not another component of episteme identity.
-
Derived
EntityOfConcernChangeModeand subtype restriction. Each admitted arrow receives its mode from its resolved endpoint EntitiesOfConcern:entityOfConcernChangeMode(f) = preservewhen X and Y concern the same entity; a current grounding relation remains a separately governed fact;entityOfConcernChangeMode(f) = retargetwhen X and Y concern independently different entities. Any claim thatfsupports one receiving use is a separate A.6.4 bounded-use assertionq; its ClaimGraph states the invariant, visible loss, receiving use, conditions, and affirmative or negative polarity. A current-case judgement separately tests the facts.
The parent EFEM class contains both modes. A named species or subtype may admit only one mode, but that restriction does not by itself make the subtype closed under composition. Classify each composite again from its final endpoints under P3.
-
Legacy SubjectRef and describing-use discipline. For Description epistemes, including those admitted for specification use, resolve legacy
subjectRef(E)to E and its EntityOfConcern. State which endpoint claim content, EntityOfConcern, and effective scheme are preserved or differ. When grounding or a selected describing-use viewpoint matters, name the occurrence or use qualification on each side and state which facts the rule reads or compares. Any occurrence change follows its direct relation pattern, while viewpoint selection and conformance remain separately claimed.
P1 — Effect-free arrow, separate execution
The mathematical statement f : X -> Y records only the arrow and its laws. A claim that a system computed, authored, stored, transmitted, or published Y requires the corresponding application, Work, result, or publication facts separately.
When a system measures, simulates, translates, normalizes, fits, or otherwise produces or changes an episteme, identify separately:
- the A.6.1 operation application and its argument and result bindings, when that declaration is current;
- the system and any performed Work;
- the affected or newly constituted episteme and its C.2.1 identity facts; and
- any production, evidence, publication, or reliance relation that obtains under its own direct governor.
The same arrow can relate already existing epistemes, or be used in several separately identified applications. Conversely, two applications do not become the same because they use the same arrow. When a result or production relation is current, identify its separately governed application and result facts.
P2 — Claim conservativity (no unlicensed commitments)
Let content_X = content(X) and content_Y = content(Y), with their effective ReferenceSchemes and EntitiesOfConcern. Interpret each ClaimGraph through its effective scheme. Name any additional source episteme, current fact, grounding relation, or scheme correspondence that the arrow rule admits; an entity or label by itself is not a claim premise. Then:
Every assertion in
content_Ymust be recoverable as a logical consequence, conservative re-expression, selection, or declared aggregation of the identified source ClaimGraphs and admitted facts under the named schemes. This includes assertions about an episteme's edition, source, status, witness, provenance, or evidence. Calling an assertion metadata does not exempt it from P2.
An EFEM arrow may omit claims or conservatively reorganize and re-express them. It may not introduce an unsupported atomic commitment, silently widen claim scope, or cross a ReferencePlane without the relation required for that move.
A separately obtaining edition, provenance, evidence, or status relation remains outside episteme identity. If the arrow family compares such a relation across X and Y, name the predicate and participants on each side. The arrow records that comparison; it does not create or update the relation. If Y asserts the relation, that assertion is identity-bearing content_Y and must pass the same source-to-result trace as every other assertion.
Where entityOfConcernChangeMode(f) = retarget, the arrow declaration states its formal cross-entity correspondence; it does not itself establish conservativity for a receiving use. For a claimed receiving use, a separate A.6.4 bounded-use assertion q states the invariant, visible loss, receiving use, conditions, and polarity. When judging a current case, test its facts against q.
An ordinary time-to-frequency representation of the same signal instead routes through A.6.3.RT; apply C.29 when the case also makes a mathematical-lens-use claim. A Fourier relation enters a retargeting case only after C.2.1 independently identifies a different receiving EntityOfConcern.
P3 — Category structure and EntityOfConcern mapping
Use this law only after the selected FormalSubstrate declares both categories and the mapping below. Ep has admitted epistemes as objects and admitted EFEM arrows as arrows. It is a category only when it contains the required identities and every composite of admitted arrows with a matching middle episteme. If that closure is absent, keep the individual arrows and do not claim this category or functor.
EoCBase is the endpoint-only thin category over the resolved EntitiesOfConcern represented in the substrate. For every admitted pair A,B, it contains one formal arrow u_{A,B}. Its only endomorphism at A is u_{A,A}=id_A, and compose(u_{B,C},u_{A,B})=u_{A,C}. This formal arrow records only endpoint identity or difference; it is not an F.9 Bridge, a domain relation, or a claim that any world-side relation obtains.
On objects, α(X) is the EntityOfConcern resolved through entityOfConcernRef(X); the reference is only the means of resolution. For f : X -> Y, α(f)=u_{α(X),α(Y)}.
Thus a preserve-mode arrow maps to the base identity even when f is not an identity arrow in Ep, while a retarget-mode arrow maps to the unique formal arrow between its different endpoint entities. α intentionally forgets the rule that distinguishes two Ep arrows with the same endpoint entities.
Practitioner check. Point to X, Y, and f; resolve both EntitiesOfConcern; and identify the resulting endpoint arrow. For a proposed composition, point to the middle episteme and the admitted composite, then check P0-P2 for that composite. If the family lacks a required identity or composite, use its individual arrows without claiming the category or functor. No extra proof or record is required unless the receiving use calls for one.
-
Identities. For each admitted episteme X, Ep contains
id_X : X -> X. For everyf : X -> Y:id_Xpreserves the episteme's claim content, EntityOfConcern, effective ReferenceScheme, and every other declared episteme value. A viewpoint selected for one named describing use remains a separate use qualification. -
Composition. For admitted
f : X -> Yandg : Y -> Z, Ep contains an admittedh = compose(g,f) : X -> Z; h must satisfy P0-P2. It also satisfies:The α equation is replayable from endpoints. For a retargeting round trip from entity A through B back to A, both sides are the unique base endomorphism
u_{A,A}=id_A; this says nothing about inverse world-side relations or identical Ep arrow rules. The composite haspreservemode when X and Z concern the same entity andretargetmode when they concern different entities.A preserve-only or retarget-only subtype is not thereby closed under parent composition. A composite remains in that subtype only when its final mode and all additional subtype laws match; otherwise it remains an EFEM arrow in the parent class. When a receiving-use claim is made, a separate
qstates the final-use invariant, accumulated visible loss, receiving use, conditions, and polarity; a separate current-case judgement tests the final facts. -
Composition across endpoint conventions. If the selected expressions use different representation languages, or their epistemes have different effective interpretation rules, name the correspondence used by each route under its direct governor and state the equality or declared equivalence that makes the two routes agree. A.6.3.RT governs a same-EntityOfConcern representation transition; C.29 governs any mathematical-lens use. To assert either relation, establish its participants and conditions. Use
natural,oplax, or similar terminology only when the substrate supplies the mappings and comparison structure required by that term and the claimed laws are established by a proof or an applicable formal check. Otherwise state the required two-route agreement in ordinary language. Any witness episteme remains separately identified.
P4 — Arrow and repeat boundary
The common EFEM model treats f : X -> Y as one arrow with endpoints, an arrow rule or designator, and declared formal equivalence. It does not treat every arrow as a function that can be evaluated on an object, and it makes no claim that a separately declared operation is deterministic.
A concrete substrate may add an evaluation operation only after declaring its argument kind, result kind, and relation to these arrows; that extra operation is not part of the common EFEM laws.
No universal idempotence follows. A normalization or another endomorphism f : X -> X may separately claim a repeat law such as compose(f,f) ≃ f only when composition is defined on the declared domain, ≃ is the substrate's stated equivalence, and a working fixture or proof supplies the witness. This mathematical repeat claim is not evidence that an operation was executed twice.
P5 — Formal domain and separate use conditions
Each arrow family states the formal domain in which its laws apply:
- the allowed kinds of the two endpoint EntitiesOfConcern;
- any grounding relations or endpoint facts that the arrow rule reads;
- any restriction the law places on the endpoints’ effective interpretation rules and any correspondence it uses under the governor of that relation. State which pairs of representation languages are admissible when the law compares the languages of the selected expressions.
- any ClaimScope constraint required by the arrow law itself.
If X or Y lies outside that domain, the arrow is not a member of this local family. This is distinct from an operation application being admitted or rejected.
When a receiving-use claim is made, a use-specific scope, operating condition, or selected viewpoint enters q only when it changes the invariant, visible loss, receiving use, or conditions; q carries affirmative or negative polarity, and a separate current-case judgement tests facts against it. Changing either does not reidentify the arrow.
When the use also relates two F.17 local senses and the F.9 predicate obtains, cite that Bridge and a separate bounded-use claim. When it crosses a ReferencePlane, cite the applicable plane relation. A claim about performed transport follows P1's separate application and Work conditions. Different labels, contexts, schemes, planes or operating conditions alone create none of these relations.
Archetypal Grounding (Tell–Show–Show)
The examples below show how EFEM is intended to be used across the EntityOfConcern and Description-episteme boundary, specification use, and Viewpoint/MVPK publication lanes.
Conservative arrow to an episteme used as a specification: SpecifyDescEpSpecDesc
Context. You have a U.MethodDescription for a safety check and want a more formal description of the same Method for a named specification use, with checkable constraints or test-harness obligations. Before calling the relation conservative, identify the claims that already support those constraints.
Shape.
- Domain: episteme
X : U.MethodDescriptionwithentityOfConcernRef(X) : U.MethodRef, its complete contentcontent_D = content(X), and effective rulesscheme_D = referenceScheme(X); when the named engineering validation use selects viewpoint P, identify that selection separately. - Codomain: episteme Y concerning the same Method and admitted for the named specification use, with
content_S = content(Y)andscheme_S = referenceScheme(Y). Recover whether the effective rules stay the same or change; writing an existing rule more explicitly does not itself change it. If the same named validation use continues, it preserves its selected viewpoint P separately.
The suffixes D and S distinguish these endpoint values. They declare no constituent kinds. Judge endpoint admissibility under the relevant description and specification-use criteria, compare complete identity under C.2.1, and test P2 separately. A checkable new requirement can satisfy the receiving specification-use conditions while changing the episteme and failing conservativity.
Specify_DescEp_SpecDesc is a species of EFEM only when all of these hold:
entityOfConcernChangeMode(Specify_DescEp_SpecDesc) = preserve. The shared Method establishes endpoint EntityOfConcern equality; the Method entity itself is not a logical premise.- P1 — effect-free: it is the declared arrow between the two epistemes; any operation application that produces Y is separate.
- P2 — conservative: every assertion in Y, including behavioral claims, constraints, and test obligations, traces to claims in X, an additional named source episteme, or an independently current fact under its named relation and effective scheme.
- P3-P5 — category structure and scope: the declared arrows compose only when their endpoints and P3 mappings agree. P5 includes the named engineering scope, operating conditions, effective scheme, or selected viewpoint in the formal domain only insofar as the arrow law depends on them. Keep separately any such condition or viewpoint that changes the named validation or receiving-use claim.
If an author chooses a new threshold, acceptance condition, harness obligation, or other commitment not supported by that basis, Y has been strengthened and the proposed arrow fails P2. Identify the new assertion in Y's changed ClaimGraph. When an application or Work accounts for that strengthening, identify that occurrence and the direct production relation separately. The new assertion remains outside the conservative arrow; the application, Work, and production relation account for its origin.
Keeping episteme identity, describing use, and production separate matches A.7 and E.10.D2. Under C.2.1, each Description episteme is identified by its complete claim content, its own EntityOfConcern reference, and its effective ReferenceScheme; any describing use or production relation is separately identified.
Specify_DescEp_SpecDesc is an optional EFEM species under the conditions above. E.10.D2 governs the receiving specification use; the declared arrow relates the two independently identified epistemes. If the endpoints serve as models, B.5.MR separately tests a refinement or abstraction claim.
Internal normalisation of a View (species of EFEM, entityOfConcernChangeMode = preserve)
Context. In MVPK you compute an engineering view V of a system description; you then normalise the view (sort, factor, put equations into normal form) without changing what it says.
Let X = V_raw, Y = V_norm. For this example, assume each episteme independently satisfies E.17.0's U.View membership condition. The two views have the same:
entityOfConcernRef(X) = entityOfConcernRef(Y)(same system);- when grounding is current, the same grounding occurrence and grounding holon are found on both sides; this is an endpoint comparison, not a change made by
NormalizeView; - any viewpoint selected by the named normalization use is the same P for X and Y; this selection is outside episteme identity;
- The source and receiving expressions selected for this comparison use the same representation language. Establish this by resolving each language reference under its applicable binding. One episteme may supply both endpoints and still be expressed in two different languages. Equal reference spellings alone do not establish equality of the two languages.
The EFEM NormalizeView : X→Y:
- has
entityOfConcernChangeMode(NormalizeView) = preserve; - has a source-to-receiving ClaimGraph difference consisting only of the declared normalization. If an
EpistemeEditionRelationor another neighboring relation matters, name its predicate and participants on each side and compare the endpoint facts;NormalizeViewdoes not change that occurrence. An assertion such as “normalised at edition E” is part of Y's ClaimGraph and must pass P2; - is effect-free. A repeat check uses the next normalization arrow
n_Y : Y -> Zunder the fixed scheme and normalization rules. It must establishZ = Yunder C.2.1 andcompose(n_Y, NormalizeView) ≃ NormalizeViewunder the substrate's declared arrow equivalence, with a fixture or proof. In the identity fixture, the rule leaves already normalized Y unchanged and usesn_Y = id_Y; P3 then givescompose(n_Y, NormalizeView) = NormalizeView. The arrowNormalizeView : X -> Yis self-composable only when X = Y (P3-P4); - is conservative (P2): no new claims, only re‑expression.
MVPK can reuse the EFEM laws for these normalization arrows. Claim the relevant category and functor only when their mappings, identity laws and composition conditions are established under P3 and the selected MVPK profile.
Retargeting sketch (entityOfConcernChangeMode = retarget)
Context. For this E.18 retargeting sketch, take the physical assembly S₁ and functional network S₂ as independently identified, different entities. The source episteme concerns S₁; the receiving episteme concerns S₂.
Inside EFEM, this becomes a species with entityOfConcernChangeMode = retarget:
- the source episteme describes the physical assembly
S₁; - the receiving episteme describes the independently identified functional network
S₂; - one arrow
rrelates the two endpoint epistemes under its declared formal rule; for a claimed receiving use, a separate A.6.4 assertionqstates the invariant, visible loss, bounded receiving use, conditions, and polarity; when a current case is judged, its facts are tested againstq; - P2 checks only the formal consequence relation declared for
r; when a current case is judged, the ordinary judgement tests its facts againstq, and A.20 enters only when that proposition is an internal constraint.
The details belong to A.6.4 and E.18; EFEM provides the generic discipline.
Worked endpoint-value and relation-read profile (engineering SystemDescription episteme kind)
(informative)
To make the C.2.1 value and EFEM law discipline concrete, consider an engineering episteme of a dependent system-description kind whose EntityOfConcern is one U.System:
This table names the three values that identify an episteme; it is not a RelationSignature or SlotSpec table. C.2.1:4.2.1 supplies EntityOfConcernSlot when a receiving use needs a designation of kind U.EntityRef that resolves to a U.Entity. A claim-content or scheme comparison uses the values above; additional typed substitution needs its own independently governed range and SlotSpec.
An EFEM species states how the endpoint values compare. If its rule uses a selected viewpoint, empirical-grounding relation, or representation relation, it names the occurrence or use qualification separately and reads or compares the endpoint facts without changing the occurrence.
Two typical EFEM species over this kind are:
-
Specify_DescEp_SpecDesc_Sys : SystemDescription → SystemSpec— anEntityOfConcernChangeMode = preservespecies that:- relates independently identified source and receiving epistemes with the same EntityOfConcern, makes their effective ReferenceSchemes explicit, and cites any separately obtaining empirical-grounding relation or viewpoint selection only when the formal relation depends on it;
- satisfies P2 only when every claim in the receiving specification is recoverable from source ClaimGraphs or independently current facts under named relations and schemes; the unchanged EntityOfConcern is an endpoint identity condition, not a proposition or additional premise;
- satisfies C.2.1:7.1 by declaring its endpoint-value comparison, named relation-read profile, and change mode.
-
Normalize_EngView— a family of view-normalisation EFEM arrowsn_X : X -> YbetweenU.Viewepistemes (again withEntityOfConcernChangeMode = preserve) that:- states how the formal relation uses the three C.2.1 identity values and makes the source-to-receiving ClaimGraph difference explicit; any difference between separately obtaining endpoint facts that it compares is named by the predicate and participants, and any normalization application remains separate;
- is effect-free. A repeat claim identifies the next arrow
n_Y : Y -> Zunder the same rules, establishesZ = Yunder C.2.1, and witnessescompose(n_Y, n_X) ≃ n_Xunder the declared arrow equivalence, as in §5.2; - is conservative (P2): every assertion in Y is recoverable from the identified source ClaimGraphs and admitted facts under the declared schemes, including any assertion about edition, provenance, or evidence.
Concrete A.6.3/A.6.4/E.17.* patterns for engineering description and specification-use idioms state explicitly, under C.2.1:7.1 and CC-EFEM.*, which of the three C.2.1 endpoint values remain the same or differ and which separately obtaining relation occurrences their arrow rules read or compare.
Bias-Annotation
-
Episteme-first, world-second. EFEM relates epistemes as mathematical objects. For a claim about actual measurement or execution, identify the capable system, the A.6.1 application when its declaration applies, any independently admitted Work, and any resulting episteme or obtaining production relation separately.
-
Actual values, not unnamed fields. Laws name the claim content, EntityOfConcern, and effective ReferenceScheme they use and keep empirical grounding, representation, view conformance, and describing-use viewpoint selection separate. A SlotKind is mentioned only when the reusable relation declaration is current.
-
Arrow domain and use-local semantics. EFEM names the formal domain of each arrow family. When a receiving-use claim is made, a separate
qcarries the receiving-use invariant, visible loss, conditions, and polarity; a current-case judgement separately tests the facts. Scope, operating conditions, and selected viewpoint enter only when they change that proposition or judgement. An obtaining semantic Bridge between two local senses, a ReferencePlane relation, and any transport application remain separately identified; no implicit cross-local or cross-plane EFEM is permitted. -
EntityOfConcern, Description episteme and specification use. Keep the EntityOfConcern distinct from the Description episteme, and identify any specification use separately. C.2.1 identifies each Description episteme directly; any authoring, measurement, observation, model, source-use, representation, or refinement relation is stated only when it is current. A.6.2:5.1 gives an optional conservative arrow to an episteme admitted for specification use. The arrow must satisfy its own laws; any application that produces the receiving episteme remains separate. A comparison of endpoint models by refinement or abstraction uses B.5.MR.
Conformance Checklist (normative)
Common Anti-Patterns and How to Avoid Them
Consequences
-
Single place for episteme‑to‑episteme laws. Effect-free arrow families used across KD‑CAL, MVPK, E.18, and discipline packs can reuse one local law set instead of re-inventing it. Each application and use claim remains separate.
-
Separation from mechanisms & work. For actual measurement, execution, or simulation, identify the capable system, any A.6.1 application whose declaration applies, and any independently admitted
U.Work; identify any resulting episteme and obtaining production relation separately. EFEM remains effect-free and compositional. Any semantic correspondence, temporal qualification, evidence, or reliance claim remains under its own pattern. -
Stable backbone for Viewing & Retargeting. A.6.3 and A.6.4 do not need to repeat P0–P5; they specialise EFEM with additional constraints (preserve/retarget). Other patterns (e.g. MultiViewDescribing, MVPK, E.18 structural reinterpretation) can depend on EFEM as a stable base.
-
Value-and-relation clarity. By requiring each EFEM species to compare the three C.2.1 identity values and name the separately obtaining relations its rule reads, the pattern keeps an EntityOfConcern, a declaration-local SlotKind, and a reference to the entity distinct. Equal or different endpoint relation facts are a comparison result, not an effect of the arrow.
-
Didactic projection. When a didactic expression–meaning–subject triangle is useful, use the C.2.1:5 projection: expression maps to selected representation elements and any publication carrier; meaning is the ClaimGraph interpreted under its effective ReferenceScheme; subject is the EntityOfConcern. Keep any material empirical grounding, representation correspondence, reference, and viewpoint selection for a named describing use separately identified, rather than adding triangle slots.
Rationale
Why a separate EFEM pattern (A.6.2) instead of folding into A.6.1 or C.2.1?
- A.6.1 defines Mechanism declarations and their separately identified applications, including operational guards and time conditions. A.6.2 instead defines a local mathematical arrow class. Any semantic Bridge, plane relation, transport application, or Work remains under its direct pattern.
- C.2.1 fixes episteme identity through claim content, EntityOfConcern, and effective ReferenceScheme and keeps neighboring direct relations separate, but does not define morphisms. EFEM is a morphism-level pattern over those values and relations.
This split mirrors how A.6.0 separates a declaration from what later uses it: C.2.1 says what an episteme is; A.6.2 states the laws of a local episteme-to-episteme arrow family; A.6.1 and A.15 govern any application and Work.
Why insist on EntityOfConcernChangeMode?
Because a relation can look like a view even though its endpoint epistemes concern different entities—for example, component assembly and function bundle. Declaring preserve versus retarget exposes that endpoint distinction. It does not make the arrow fit for a use. The separate A.6.4 bounded-use assertion and current-case judgement determine whether the arrow supports the named receiving use.
Why name actual values and relation reads instead of informal fields?
FPF distinguishes actual participants and their references from the declaration-local SlotKinds used in a reusable RelationSignature. Reusing that distinction here:
- aligns episteme morphisms with the framework's direct-relation architecture;
- enables checks that an EFEM species compared only the three declared endpoint values, read only the named neighboring occurrences, and left any relation change to its direct pattern and producing application or Work;
- avoids minting another generic parameter, field, or relation-role vocabulary.
SoTA-Echoing
Practice question. How can reusable transformation definitions and composition remain separate from execution and correctness evidence, and which repeat laws do they support?
Relations
-
Specialises / is specialised by.
- Builds on A.6.0
U.Signaturefor direct subject, range, optional result, slice, and extent components together with Vocabulary, Laws, and Applicability; coordinates with A.6.1U.Mechanismwithout making mechanism application part of EFEM. - Specialized by the A.6.3 EntityOfConcern-preserving viewing branch and the A.6.4 EntityOfConcern-retargeting branch.
- Builds on A.6.0
-
Constrained by. A.6.5 declaration-local SlotSpec discipline; C.2.1 episteme constitution and any separately current empirical-grounding or edition relation; E.10.D2 for the EntityOfConcern, Description-episteme, describing-use, and specification-use boundary; Part F for local-sense or ReferencePlane relations; and E.10 for naming discipline.
-
Consumed by. E.17.0
U.MultiViewDescribing(families of Description epistemes, including Description epistemes admitted for specification use, under Viewpoints); E.17 (MVPK — publication of source-backed faces, with a separate A.6.3 construction when another receiving episteme is constructed and an optional morphism-publication profile); E.18 (structural reinterpretation and other transformation-flow relations over epistemes); KD‑CAL/LOG‑CAL rules that reason about episteme transforms categorically.
A.6.2:End
Episteme viewing - EntityOfConcern-preserving episteme construction
Status: Stable
Use this when. You need to derive a smaller, reorganized, or differently expressed body of claims from existing claims while keeping the same thing under discussion. In FPF terms, the source and result are independently identifiable epistemes with the same EntityOfConcern. The result may select, reorganize, normalize, translate, or combine claims from the named sources, but it must not add a claim those sources do not support.
First useful result. Write one source-to-result statement. For example:
Under the declared viewing rule, the claims in result Y are licensed by X together with any additional named sources and admitted facts required by that rule. X and Y are about the same named thing. Y keeps [named claims], omits [named claims], and adds no claim unsupported by those premises.
Then name or show the rule that selects, rewrites, or combines the claims. Do not call the construction an A.6.3 viewing unless X and Y can be identified separately and this rule can be inspected.
What this does not decide. A.6.3 says how Y is licensed by named sources about the same thing. It neither proves the claims true nor makes Y a U.View; use E.17.0 for view membership. Use A.15.1 for the work that produced Y, A.15.PROD if first constitution matters, and E.24.PUB for publication, but only when those separate facts matter.
Builds on: A.6.0 direct declaration structure; A.6.2 effect-free episteme morphing; C.2.1 episteme identity; E.17.0 viewpoint conformance and view membership; A.6.3.CR conservative retextualization; A.6.3.RT representation transition; A.6.4 retargeting; C.29 mathematical-lens use; A.13 Work basis; A.15.1 work; A.15.PROD local work/change/entity-identity-inception claims.
Used by: E.17 publication-face construction, E.17.0 multi-view describing, E.18 transformation-flow descriptions, and domain patterns that derive a smaller or differently expressed episteme from one or more source epistemes.
Problem frame
Engineering work often needs a different body of claims about the same thing. Examples include a safety-focused slice of a system description, a normalized technical card, a conservative translation between notations, or a coverage view built from requirements and design epistemes plus stated correspondence claims.
Several neighboring facts can all be true but are not the same fact:
- X and Y are identified as C.2.1 epistemes;
- a declared viewing rule licenses Y's claims from X and any additional named sources or admitted facts it requires;
- X and Y have the same EntityOfConcern;
- Y makes no stronger claims than the identified sources license;
- Y conforms to a viewpoint and is therefore a
U.View; - a system performed work that first constituted Y;
- Y was later published through a form and carrier.
Ordinary use may need only items 1 through 4. The remaining claims are opened independently.
Problem
How can a project state how X and any additional named sources or admitted facts license Y under a viewing rule while making clear what was preserved, what was lost, and why Y adds no unsupported claim?
Keep that construction separate from the work that produced Y, any publication of Y, and any separate check that Y qualifies as a U.View.
Without this distinction, a query execution is treated as view membership, a generated file is treated as the episteme, a new claim is treated as a formatting change, or an EntityOfConcern change is treated as a same-entity projection.
Forces
Solution
Local mantra. Identify X and Y. Hold their EntityOfConcern fixed. State the conservative construction and admitted loss. Add correspondence dependencies when used. Test U.View membership separately under E.17.0 only when the receiving use needs that membership.
Identify both epistemes independently
Before declaring a viewing, recover for each of X and Y under C.2.1:
- claim content;
- EntityOfConcern;
- effective interpretation rules, identified under C.2.1:4.1.1 (
ReferenceScheme).
X and Y are separate epistemes whenever one of those identity discriminators differs. A filename, table, diagram, query result, viewpointRef, or publication form is not a substitute for either identity.
If the supposed receiving item has no recoverable claim content or EntityOfConcern, stop: the receiving episteme has not been identified. If the EntityOfConcern differs, use A.6.4 retargeting rather than A.6.3.
Declare the viewing construction
A.6.3 viewing is a preserve-mode specialization of A.6.2's local effect-free arrow class, subject to the viewing construction and laws below. In the selected formal substrate, one viewing arrow is written v : X -> Y and has source episteme X and receiving episteme Y.
The reusable A.6.0 declaration describes the admitted local arrow family, rather than turning one arrow or endpoint pair into a kind:
EpMorphism is a local mathematical type in the selected substrate, not a durable FPF U-kind. The arrow records the declared construction from X to Y. Section 4.6 separately governs an account of its execution.
A viewing declaration states:
- X and Y;
- that
EntityOfConcern(X)=EntityOfConcern(Y); - the claim-content construction from X and any additional named sources to Y;
- how the source and receiving reference schemes are related;
- preserved claim components, admitted omissions or losses, and prohibited strengthening;
- applicability conditions and any fixed configuration needed for replay.
A separate assertion says whether this arrow supports one named receiving use and states any use-specific loss or conditions. If the current use needs an account of a query, rewrite, model, or other method being applied, identify that application and any admitted Work separately; v : X -> Y alone does not assert that they occurred.
Apply the same-EntityOfConcern and conservativity laws
For every admitted v : X -> Y:
- Same EntityOfConcern. X and Y designate the same EntityOfConcern. Similar labels, bridge claims, or one shared project do not establish this equality.
- No unsupported strengthening. Every claim in Y is recoverable as a consequence, conservative re-expression, or explicitly admitted aggregation of claims in the identified sources under the declared reference and representation semantics. This includes claims about the EntityOfConcern and any asserted correspondence, evidence or evaluation facts.
- Declared loss. Every omitted concern or claim family that affects receiving use is named, together with the condition under which the loss is admitted.
- Reference discipline. A changed effective reference scheme is explicit. If the change alters available operations or representation semantics, use A.6.3.RT; apply C.29 when the transition uses a declared mathematical lens. Do not call such a change formatting.
- No hidden retargeting. Subsystem-to-system, method-to-work, model-to-modeled-system, or episteme-to-publication changes are not same-EntityOfConcern viewing.
For a lightweight check, take each claim in Y—or each group covered by one rule—and point to the source claims and the selection, rewriting or aggregation rule that licenses it. Mark omitted claim groups. If support cannot be established, leave that claim's admissibility in the viewing unresolved; if the rule demonstrably introduces an unsupported claim, the proposed construction fails the viewing law. A structural or domain check used as an approximation states what it cannot establish. Add a proof when disagreement, risk or the receiving use requires one.
Truth of source claims is a separate evaluation. Conservativity says what Y is licensed to claim from the sources; it does not establish that those claims are true in the world or adequate for a decision.
Keep optional viewpoint selection and view membership separate
For the current use of receiving episteme Y, name the describing use and viewpoint P only when that selection changes what the receiver reads or checks. Keep Y, its EntityOfConcern, the use, and P distinct. Selecting P is outside C.2.1 identity and does not make E.17.0 conformance obtain.
After Y is identified, apply E.17.0 only when the current use needs U.View membership:
Directly authored Y can qualify as a view without establishing an A.6.3 source-to-Y construction. Conversely, a valid A.6.3 construction can yield Y that fails P's concern-coverage or semantic-form rules and therefore is not a view under P.
Distinguish direct and correspondence-mediated construction
Direct viewing. Y is constructed from X and fixed configuration only. The declaration names the claim selection or rewriting rule and any loss. No generic correspondence object is required.
Correspondence-mediated viewing. Y depends on several source epistemes or on relations between their claim-bearing contents. Recover each direct correspondence, realization, trace, equivalence, or consistency relation under its governing pattern before using it. Then identify the C.2.1 episteme that states or describes those relations if the construction must cite it.
Plain correspondence model may name that claim-bearing episteme. It is not a public U.CorrespondenceModel kind. A graph edge or table cell may state or support a correspondence claim; its presence does not establish that the relation obtains. Judge the content and any evidence under the relation's governor and A.10. If a needed relation lacks a governor, return the missing-relation blocker or use A.6.RCD.
The viewing declaration cites the source epistemes and correspondence claims on which Y depends. If Y asserts facts about a correspondence episteme, evidence, or evaluation result, those assertions belong to Y's claim content and follow C.2.1's identity rule. The cited objects remain independently identified, and the assertions still require the support specified by the viewing law.
Keep mathematical construction, work, production, and publication distinct
Describe querying, rewriting, modeling or rendering in ordinary practitioner terms. When the account claims a dated U.Work occurrence, establish its A.13 basis and A.15.1 admission; identify the system that performed the work and the method it used. The source epistemes, parameters, tools, and receiving entities participate only through their direct relations or A.6.1 operation bindings.
If that work first constitutes episteme Y and the identity-inception claim matters, A.15.PROD governs the local work/change/identity claim. Neither work nor inception establishes conservativity or E.17.0 conformance.
If Y is made available, E.24.PUB separately identifies the publication occurrence, expression, any selected reusable publication form, and independently identified carrier whose state or realization yields that expression. Publication neither creates the A.6.3 construction nor grants U.View membership.
Preserve composition and replay
The selected formal substrate supplies the identities, admitted compositions, and arrow equivalence. For fixed source epistemes, rules, reference semantics, correspondence dependencies, and configuration:
- identity viewing preserves the same C.2.1 episteme;
- composing
f : X -> Ywithg : Y -> Zgives the admitted compositecompose(g,f) : X -> Zunder A.6.2 P3; - if a separately declared construction operation is deterministic, replay with the same admitted inputs yields the same receiving C.2.1 identity discriminators;
- random seeds, model editions, external service state, or timing that can change Y are explicit inputs to the work or declaration;
- a normalization repeat claim identifies
n_X : X -> Yand the next arrown_Y : Y -> Z, establishesZ = Yunder C.2.1, and witnessescompose(n_Y,n_X) ≃ n_Xunder the declared arrow equivalence. OneX -> Yarrow is self-composable only when X = Y.
A composition requires the middle episteme to match. A claim that two routes yield the same receiving episteme requires equality of all three C.2.1 identity discriminators; representation equivalence alone does not establish that identity. The repeat claim requires a fixture or proof under A.6.2 P4.
Stop at the lightest sufficient statement
For ordinary use, this can be enough:
Safety summary Y is conservatively constructed from plant description X; both concern Plant-7; Y omits maintenance-cost claims and introduces no safety claim not recoverable from X.
Add a reusable declaration, explicit mathematical arrow, correspondence episteme, evaluation result, work occurrence, production claim, or publication objects only when a named receiving work or decision depends on that object.
Worked cases
Safety-focused system description
X is a system-description episteme about plant S. Y is a smaller episteme about the same S containing only safety-critical functions, hazards, and mitigations recoverable from X. The viewing declaration names the filter and omitted claim families. A.6.3 construction obtains. Y becomes a U.View only after safety viewpoint P is resolved and EpistemeViewpointConformanceRelation(Y,P) obtains.
Directly authored view
Architecture episteme E is authored directly against maintainability viewpoint P and passes E.17.0 conformance. E is a U.View on that basis; no source-to-E viewing claim is needed for this result. A mathematical viewing relation may be established separately, including identity viewing on E. Any claim that the authoring used a source needs its own historical basis; the mathematical arrow does not supply it.
Query result that fails conformance
Query Q constructs Y from source X while preserving the same system and making only licensed claims. Y omits one concern required by viewpoint P. A.6.3 construction is valid; E.17.0 conformance fails, so Y is not a view under P.
Normalized publication card
X and Y are separately identified epistemes about morphism f. Y reorders claims and normalizes names without changing their interpretation. NormalizeTechCard : X -> Y is a direct viewing. For a repeat claim under the same scheme and normalization rules, identify the next normalization arrow n_Y : Y -> Z; establish Z = Y under C.2.1 and compose(n_Y, NormalizeTechCard) ≃ NormalizeTechCard under the substrate's declared arrow equivalence, with a fixture or proof.
A later publication occurrence makes Y available through a TechCard form. Y is called U.View only if it conforms to the publication viewpoint; the form and carrier remain separate.
Cross-model coverage
Requirements episteme R and design episteme D concern system S. Realization relations connect requirements to design elements. A correspondence assertion episteme states those occurrences.
Receiving episteme Y selects only requirements with an obtaining realization relation. A.6.3 records the correspondence-mediated construction from the sources to Y; the assertion episteme and matrix representation remain separate from the realization occurrences.
Retargeting boundary
X concerns pump P-14. A proposed Y concerns the whole cooling skid. Even if every Y claim is derived from X plus neighboring descriptions, A.6.3 does not apply because the EntityOfConcern changed. If declaring a retargeting arrow, use A.6.4. For a claimed receiving use, separately state its invariant, visible loss, use conditions and affirmative or negative proposition; assess that proposition against case facts when a current-case judgement is needed.
Consequences
Rationale and SoTA-Echoing
Conformance checklist
- X and Y each have recoverable C.2.1 identity.
- X and Y have the same EntityOfConcern; otherwise the route is A.6.4.
- The declaration states the claim construction, reference semantics, applicability, preserved content, and admitted loss.
- Every claim in Y has the support required by the viewing law, including any claim about a correspondence, evidence or evaluation result.
- Every correspondence-mediated dependency resolves to source epistemes and governed direct relations.
U.Viewis asserted only after independent E.17.0 conformance.- A viewpoint selected for a named describing use is not used as membership evidence and does not enter X or Y identity.
- Systems, tools, work, parameters, and production claims are recovered separately when construction work matters.
- Publication occurrence, form, carrier, and rendering remain separate from X, Y, and v.
- Composition and declared loss satisfy their laws; any deterministic replay claim is tested under its stated conditions.
- Ordinary use stops without materializing objects the next work or decision does not need.
Relations
- A.6.0 supplies the direct declaration structure used in A.6.3:4.2.
- A.6.2 supplies the effect-free morphism and composition discipline.
- C.2.1 identifies source and receiving epistemes.
- E.17.0 alone governs
U.Viewpoint, conformance, andU.Viewmembership. - A.6.3.CR governs conservative textual re-expression when wording and organization are the main change.
- A.6.3.RT governs same-EntityOfConcern representation transition with explicit recoverability and loss.
- A.6.4 governs a changed EntityOfConcern.
- C.29 governs a declared mathematical-lens use of the construction or correspondence, including a diagram used for that mathematical claim.
- A.13 supplies the basis for an explicit dated Work claim; A.15.1 and A.15.PROD govern its admission and any local entity-identity-inception or completion claim.
- E.24.PUB governs publication occurrence, form, and carrier.
- Use A.6.RCD when a needed correspondence relation lacks a governed expression.
A.6.3:End
Controlled Semantic Coarsening: Shorten an Account for a Bounded Use
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Placement. Controlled Semantic Coarsening helps a practitioner make and bound a shorter account. Its exact branch is a specialization under A.6.3 U.EpistemicViewing for construction c : X -> Y, where source episteme X and receiving coarsened episteme Y concern the same EntityOfConcern and Y is admissible only for a narrower use under declared loss and return.
Builds on. C.2.1 for episteme identity and A.6.3 for the same-EntityOfConcern construction c : X -> Y.
Problem frame
Practical entry; identity when material. For ordinary shortening, begin with the source passage or account, its present reader and use, and the distinctions that use still needs. Write the shorter candidate directly, then compare it with the source: the candidate must neither lose a distinction needed for that use nor add or strengthen anything the source does not support. Record any loss, the use boundary, and the condition for going back. This local, reversible result does not by itself assert an A.6.3 construction.
When the result must travel independently or endpoint or construction identity matters to the receiving use, identify source episteme X, receiving episteme Y, and c : X -> Y. Exact CSC remains a same-EntityOfConcern construction; a changed EntityOfConcern requires A.6.4.
Use this when. You need to shorten a text or another account without losing the distinctions needed for its present use or saying more than the source supports—for example, a summary, redacted disclosure, or dashboard account whose omissions must remain visible and bounded. If the task is only layout, carrier, extraction, or authoring, use E.24.PUB, A.7, or E.8 as appropriate. Identify the episteme endpoints under §4.3 when their identity matters.
What goes wrong if missed. A helpful summary hides a qualifier or distinction needed by its current reader, or adds or strengthens a claim beyond source support. A reader may then rely on the summary for a decision that needs the omitted information. In an exact case, mistaking the publication or representation for its claim-bearing episteme also leaves the endpoint unidentified.
What this buys. The practitioner reaches a useful shorter candidate before optional formal apparatus, while the comparison still exposes required distinctions, controlled loss, prohibited strengthening, non-admissible use, and return. When endpoint or construction identity becomes material, reuse that comparison to establish the endpoint and construction account.
State the use limit and return through the distinction that was lost or weakened, or the additional support the proposed use requires. Apply F.19:4 when deciding whether an explicit warning or denied downstream use helps the intended reader. A positive narrower-use statement may already make the boundary clear; the underlying admissibility condition remains in force.
Not this pattern when. Use A.6.3.CR for ordinary rewording with no narrower-use or controlled-loss question; A.6.3.RT when the receiving operation depends on a change of representation language or reasoning medium; E.17.EFP for explanation fidelity; E.17.ID.CR for comparison; F.9 for a Bridge and its separately stated bounded-use claim; F.9.1 only for a separate stance note about such a claim; A.6.4 for a changed EntityOfConcern; A.15 for work; and A.20/A.21 for a constraint or gate claim.
Problem
FPF often needs a coarsened form of a source-bearing side: a manager summary, a redacted disclosure note, a dashboard tile, a lookup surrogate, a workshop simplification, or a didactic compression. The coarsened form can be valuable, but it becomes dangerous when readers forget that its admissible use is narrower than the source-bearing side.
A coarsened rendering stays usable under these conditions:
- the source-bearing side retains the fuller claim scope and remains directly reopenable;
- the coarsened rendering has declared concrete loss or reduced recoverability;
- the coarsened rendering makes only the narrower use admissible;
- a use requiring a lost distinction or additional support is not admissible from the coarsened rendering alone;
- such a use reopens the source-bearing side or uses the pattern that supplies the needed definition, constraint, test, method, evidence rule, or
authoritySourceRefrelation.
Without a named pattern for that relation, neighboring patterns repeat partial coarsening rules locally. The repetition hides the shared constraint and makes it too easy for coarsened renderings to travel as if they were the source-bearing side.
Forces
Solution
Begin with direct semantic compression. Name the present reader or use, point to the source passage or account, list the distinctions that use needs, write the shorter candidate, and compare candidate with source. Make clear what survived, what was omitted, weakened, aggregated, redacted, or made harder to recover, and what the candidate added or strengthened without support in the source; then make the supported use and return condition clear. Apply F.19:4 to any explicit excluded-use statement.
The ordinary result is the shorter candidate and its directly reachable source; the surrounding text may already make the use, loss, and return clear. Use §4.1 only when a separate comparison record helps the receiving use.
The ordinary result is provisional: it can support the named local, reversible use while the source remains adjacent or directly linked, but it does not yet assert an exact CSC relation or make the candidate independently transferable.
When endpoint or construction identity changes interpretation, comparison, migration, conflict, publication, reuse, or reliance, identify A.6.3 construction c : X -> Y. X and Y are then independently constituted C.2.1 epistemes about the same EntityOfConcern. State the claim-content rule from X and any named additional source epistemes to Y, the relation between their effective reference schemes, preserved claims, controlled loss, prohibited strengthening, applicability, narrower admissible use, and return.
Use these Plain terms with that progressive boundary:
- Source-bearing side means the source passage or account used in the ordinary comparison. In the exact branch it resolves to source episteme
X; an open corpus or record neighborhood is inadmissible, and a selected source pack or set can itself beXonly if it independently has claim content, EntityOfConcern, and effective reference scheme. - Coarsened rendering means the shorter candidate offered for the named use. In the exact branch it resolves to receiving coarsened episteme
Y. A visible summary, page, tile, publication form, or carrier may express or exposeY; it is notYmerely by readability. - Present or narrower admissible use means the practical use for which the candidate is being made, such as orientation, retrieval, bounded disclosure, workshop framing, or preliminary triage. In the exact branch this becomes the explicitly bounded use of
Y. - Non-admissible downstream use means the use the candidate or
Ydoes not make admissible alone, such as approval, audit closure, release gate, work plan, equivalence, bridge/substitution, accountability finding, or canonical technical claim. - Return trigger means the condition that requires the source, local re-expansion,
X, a source relation, or the pattern that supplies the needed definition, constraint, test, or method. - Exact reuse or reliance case means a coarsening result that must travel independently or whose endpoint or construction identity matters to the receiving use.
Producing an ordinary candidate does not require a Work record. When the current claim needs the history of coarsening, use A.13 to establish each performer's agential basis and A.15.1 to admit the dated Work independently, including at least one Method followed. Add F.6 only if that use must also state under which assignment the Work was performed. Name a separate capability claim, an additional enacted Method, source-use or A.6.1 bindings, and any A.15.PROD inception claim only when the receiving claim depends on them. Establish conservativity or controlled loss through the source-to-candidate comparison.
E.24.PUB identifies a publication occurrence that makes one selected episteme edition available to a declared audience for a bounded use through one independently identified expression and the state or realization of its independently identified carrier. Any selected reusable publication form constrains that expression separately. Plain published episteme names the episteme in that contingent publication use. Establish X, Y, c, and their admissible use under the CSC rules above.
Ordinary mini-card
Use this optional six-row aid when the receiving use needs an inspectable comparison. For ordinary use, keep only the smallest comparison that makes the shorter candidate useful; its values may remain in the source, candidate, and surrounding text.
When a card is useful, keep it inline with the adjacent or directly linked source and candidate.
If no required distinction was lost, no claim was added or strengthened beyond what the source licenses, the non-use boundary is clear, and the return remains cheap, stop. Do not create another durable coarsening object or an identity dossier solely for local orientation.
If the candidate must travel independently or the content identity changes the receiving use, carry the already recovered source, candidate, use, loss, and return into the exact branch instead of starting a second account.
First check
Before using the shorter candidate, ask:
- Is the present reader or use explicit, and are the distinctions needed for that use named before shortening?
- Can the source passage or account be reached directly, and does the candidate preserve every named distinction?
- Are all omissions and weakenings identified, and is every candidate claim supported by the source rather than added or strengthened by fluent prose—for example a number, classification, temporal statement, approval status, causal claim, modal claim, or authority claim?
- Are the supported use and any required source return clear, with any explicit exclusion justified under F.19:4?
- Are the source material, candidate content, publication occurrence, form, carrier, Work, evidence, assurance, authority, and gate claim kept separate whenever one of those distinctions is current?
This first check tests only source-to-candidate fidelity; it establishes neither that the source claims are true nor that the source or candidate is adequate for a later decision. If any answer is no, revise the candidate or return to the source. Use A.6.3.CR when no controlled-loss or narrower-use issue remains, A.6.3.RT when the receiving operation depends on a change of representation language or reasoning medium, A.6.4 when the EntityOfConcern changes, and E.8, A.7, or E.24.PUB when the live object is authoring, extraction/carrier behavior, or publication. Resume a blocked use only after the required repair is complete and verified.
Ordinary vs exact reuse or reliance account
Ordinary cases should remain light. A short orientation summary, redacted partner note, workshop simplification, or lookup handle needs only the source-to-candidate comparison while the source remains directly available and no stronger use is attempted. The six-row form is optional.
Open the exact branch only when independent reuse, dispute, reliance, citation, cross-scheme interpretation, policy, bridge, work, gate, privacy, engineering justification, or assurance makes identity material. Then:
- identify source episteme
Xand receiving coarsened epistemeYby claim content, EntityOfConcern, and effective interpretation rules (ReferenceScheme); - confirm that both concern the same EntityOfConcern;
- state
c : X -> Y, including claim construction, endpoint-scheme relation, preservation, controlled loss, prohibited strengthening, applicability, narrower admissible use, and return; and - keep any source set, model, graph, state representation, evidence set, publication occurrence, form, carrier, Work, viewpoint, representation, and grounding facts separate and add only those needed by the receiving use.
The exact account below inherits the E.17:5.1e local-field rule. Use its entries as review aids for one exact reuse or reliance case. Apply the defining subject pattern to establish any additional FPF object, relation, or source-reference claim made with those entries.
Keep only entries that change the current use or next action:
sourceEpistemeRef,receivingCoarsenedEpistemeRef, andviewingConstructionRefOrStatementfirst; separately identify anyPublicationUnit, publication occurrence, publication face or form, interop publication form, or carrier that exposes either endpoint;coarsenedRenderingPublicationUnitIfAnyonly when onePublicationUnitis distinct from the publication, disclosure note, dashboard tile, orinterop publication formon which it appears;- one source-relation reference,
projectSourceRecordRef, or privileged reopen path, with any cited pattern named for the concrete definition, constraint, test, method, or source relation it supplies, so a coarsened rendering cannot reset its own provenance; - optional
coarseningBranchonly when it selects one additional branch-specific rule inA.6.3.CSC:4.4; ordinary direct semantic compression remains unlabelled; - every concrete lost or weakened distinction, with several recorded when several coexist; no single loss tag may substitute for this account;
recoverabilityAfterCoarseningonly when the proposed use needs recovery, stating the recovery requirements and selected next move underA.6.3.CSC:4.5;- at least one kept claim or distinction bundle, one coarsened or dropped bundle, and one reopen-only bundle when the case is disputed or later cited;
- an exact
E.17:5.1bliteral in a local field permitted byE.17:5.1eonly when that source-relation status changes the next bounded use; CSC keeps no local paraphrase catalog; - uncertainty or abstention state when branch interpretation, preserved distinctions, source pin, or named narrower use cannot yet be stated stably;
- the independent-verification question when downstream testing, assurance, gate, or external reliance appears;
audienceOverReadRisk, plus a light reader-reliance or user-evidence check when readers may mistake the coarsened rendering for authority it does not carry; and- whether local re-expansion is enough or the proposed use still requires return to
X, a source relation, anauthoritySourceRef, or the pattern that supplies the needed definition, constraint, test, method, evidence rule, or gate rule.
The concrete narrower-use boundary and return trigger govern the current use and are stated once. Name an excluded use only when that explanation passes F.19:4's guard test; keep the underlying admissibility condition in force.
Optional branch rules and named-use discipline
Ordinary direct semantic compression needs no coarseningBranch: state its concrete narrower-use boundary and return directly. In an exact case, the optional branch cue is used only when it selects one of the additional rules below. It is non-exhaustive, grants no authority, and does not replace concrete loss or use; aggregation is not a catch-all name for a summary.
A branch cue changes only the additional rule named in its row. Scheme difference, publication adjacency, citation, independent reuse, or high stakes alone selects none of these branches and proves no correspondence or authority.
Concrete loss, recoverability, and anti-overread
Name every concrete distinction omitted, weakened, aggregated, redacted, narrowed in scope, made harder to recover, or lost through representation change. Several losses can coexist and all decision-relevant ones remain visible. Redaction and aggregation describe how a loss arose; neither substitutes for the lost qualifier, uncertainty, alternative, evidence path, relation, scope, trace, or inspection possibility. No loss tag is required when the concrete account already changes every relevant decision. If a publication-facing case also needs an E.17 source-relation status, use the exact literal source-loss-declared; that literal says that loss was declared and does not say what was lost.
Recoverability and admissible use remain separate. Use the choices below only when the proposed use needs a lost distinction; otherwise retain the sufficient bounded result. Name every required recovery, then read the rows in order for that proposed use. Keep all unmet requirements visible even when one of them determines the next move.
The four rows distinguish mutually exclusive recovery conditions for the proposed use; they are not a strength scale. A recoverable candidate is not automatically admissible for downstream use, and a blocked use is not repaired merely by saying the source might exist.
A coarsening chain may not reset provenance. For X -> Y1 -> Y2, identify all three epistemes and both constructions, carry forward every earlier loss and uncertainty, and state only the added loss at the second step. If that cannot be done, return to X.
Neighboring-pattern boundaries
Neighboring guidance may cite CSC when controlled loss, narrower use, and source return become the primary question. CSC does not replace the concrete definitions, tests, methods, evidence rules, work rules, or gate rules used by those other questions.
Well-formedness constraints
Well-formedness constraint CSC-WF-0 (ordinary bounded use). An ordinary local candidate is usable only while its source is adjacent or directly linked, the present use and must-retain distinctions are explicit, any loss and anything added or strengthened beyond source support are visible together with the supported-use boundary, and return remains cheap. This provisional comparison asserts neither exact endpoint identity nor an independently transferable CSC construction.
Well-formedness constraint CSC-WF-1 (exact controlled-coarsening construction). An exact or independently reused CSC account is well formed only when it identifies X, Y, and c : X -> Y; the same EntityOfConcern; one declared narrower admissible use; controlled loss; and one visible return to X, established source relations, or the pattern that supplies the needed definition, constraint, test, or method. Identify the claim-bearing whole under C.2.1; a model, graph, state representation or selected set qualifies only when it satisfies those conditions. Keep its publication, form and carrier separate. An open corpus, folder, topic or search cluster alone does not identify either endpoint.
Well-formedness constraint CSC-WF-2 (no authority upgrade). A coarsened rendering does not gain evidence, bridge, work, approval, gate, or adjudication authority by repetition, fluency, audience convenience, citation, or publication on a more visible publication face or channel.
Well-formedness constraint CSC-WF-3 (source path continuity). A coarsening chain remains well formed only while original source episteme, every intermediate receiving/source episteme, every declared construction, accumulated loss, uncertainty state, and return remain recoverable.
Archetypal Grounding
Tell. Controlled semantic coarsening begins by comparing a shorter candidate with its source for the present use: it must neither lose a needed distinction nor add or strengthen anything the source does not support, while any loss, non-use, and return remain visible. When the result must travel independently or endpoint or construction identity matters to the receiving use, the exact account is c : X -> Y under same EntityOfConcern, declared loss, narrower use, prohibited strengthening, and return.
Show (System). Incident episteme IR-42-X contains trace, confidence-band, and alternative-branch claims. Orientation episteme IR-42-Manager-Y carries a controlled subset. Use a dashboard tile exposing Y for planning orientation. For release approval, audit closure, causal justification, or a Work order, return to X and apply the evidence, Work, or gate rule that governs that use; for an authority-looking claim, select the matching A.6 A6-AW-* row and follow its direct subject pattern.
Show (Episteme). Research-review episteme ResearchReview-X is used to construct retrieval episteme RiskHandle-Y. The visible handle is a form. Use it only to retrieve X; consult X for the evidence, alternatives, and source relations omitted from Y.
Worked slices
Direct text shortening (ordinary form). The source paragraph says: Release only after a current smoke-test pass; rollback must remain available; a designated approver must approve any exception. The deployment guide then gives six implementation details not needed by the current planner. The practitioner marks the three decision conditions as must-retain and writes: Release only after a current smoke-test pass; keep rollback available; every exception needs approval by a designated approver. Comparison records the omitted implementation details, confirms that the candidate adds or strengthens no unsupported claim, keeps the stated preconditions separate from claims that they have been met or that release is approved, and points back to the paragraph on dispute or independent reuse.
A variant that keeps all three conditions but adds therefore release is approved is rejected at the same comparison: the source states preconditions and an exception rule, not current approval status.
The faithful candidate remains with its linked source, and the invented-status variant is discarded; the local comparison needs no separate card or C.2.1 dossier. If the faithful candidate will be cited in a release decision, the exact branch identifies X, Y, and c and adds only the source, work, evidence, gate, or assurance relations that decision needs.
Manager orientation summary. Source episteme IR-42-X states trace, confidence-band, alternative-branch, and incident claims about incident IR-42 under its effective incident-analysis scheme. Coarsened episteme IR-42-Manager-Y states the narrower cache-failover orientation claim about the same incident under its effective briefing scheme. ManagerCoarsening : X -> Y preserves the leading-concern claim, drops confidence bands and alternatives, and returns to X. A dashboard tile and its carrier expose Y.
Redacted partner note. Source episteme IncidentDisclosure-X and receiving episteme PartnerDisclosure-Y concern the same incident. Their declared coarsening omits actor identity and trace path for bounded disclosure, preserves coordination claims, and returns to X or the authority destination. The note form, redaction layout, and carrier are not either episteme.
Redacted functional-description publication. Source episteme FunctionalArchitecture-X states flow relations, method-selection limits, work-plan prerequisites, result-measurement requirements, and two exception claims about one system. Partner episteme FunctionalPartner-Y concerns the same system; PartnerFunctionalCoarsening : X -> Y preserves the main flow claim, removes exceptions and measurement detail, permits bounded coordination orientation, and returns to X. A partner table and carrier expose Y through E.24.PUB.
Coarsened narrative briefing. Source episteme ArchitectureCandidates-X states three candidate, two trade-off, and one unresolved-constraint claims about one system. Briefing episteme CandidateBriefing-Y concerns the same system. NAR supplies the narrative-ordering account; CSC supplies the declared omission of alternatives, orientation-only use, and return to X. The briefing form is neither endpoint.
Exceptional interop-facing simplification. Source episteme ExchangeComparison-X states the bounded source-local claims and comparison or Bridge dependencies. Orientation episteme ExchangeGloss-Y states the narrower broader-than gloss about the same comparison EntityOfConcern. InteropCoarsening : X -> Y does not establish equivalence, projection, substitution, or a Bridge; establish the operative relation and support its bounded use under its governing pattern, or return to X. When the claim needs a Bridge between local senses with different interpretation bases, use F.9 and a separate bounded-use claim. An F.9.1 stance note may explain that claim but cannot replace it.
Bad fit: hidden work authority. Deployment may proceed; see summary S-3. The sentence claims permission to deploy on the basis of a summary. Select the matching A.6 A6-AW-* row for that permission assertion and follow its direct subject pattern; use the applicable A.15 pattern if a Work plan or Work is also claimed. Before relying on that deployment-permission claim, recover its governing source and the facts required by its direct predicate.
Bias-Annotation
Scope: Universal for source-to-rendering relations that claim controlled semantic coarsening inside FPF.
This pattern favors Prag and Did by reaching a useful shorter candidate through direct comparison before optional identity work. It also favors Gov and Arch by keeping a proposed use that needs lost distinctions or additional support dependent on the required source return or neighboring contribution. The mitigation for over-formalization is the ordinary source-to-candidate comparison, with a mini-card only when useful: exact endpoints, construction, Work, publication, evidence, and assurance open only when the receiving use makes them material.
Conformance and counterexample replay
A check is retained only if it changes the next admissible use, blocks a concrete overclaim, or preserves the source-return path.
CSC-Core
Exact reuse or reliance conditions
Counterexample replay
Common Anti-Patterns and How to Avoid Them
Consequences
Rationale
Controlled coarsening is useful because FPF work often needs cheap readable forms. It is risky because those forms often travel farther than their admissible use. The pattern therefore begins with direct source/candidate comparison; it makes retained distinctions, loss, non-use, and return explicit enough for the present task, then opens endpoint, source, work, evidence, publication, or assurance relations only when a stronger receiving use needs them.
This pattern is narrower than a general simplification pattern. It applies only when the coarsened rendering remains tied to a source-bearing side and has a declared narrower use and return condition.
Keep source episteme X recoverable when using or further coarsening Y. Identify each endpoint by its claim content, EntityOfConcern and effective reference scheme; state publication and representation relations separately when they matter. If admissibility is missing, complete the required source or admissibility repair before resuming the blocked use.
SoTA-Echoing: Adopted Or Adapted Invariants And Rejected Shortcuts
SoTA alignment rule. Read each row here as source idea -> local FPF invariant -> practical local test -> popular shortcut rejected.
Purpose. This section justifies the pattern's safeguards. It is not an additional operational checklist. The Solution, conformance checks, worked slices, and Relations explain how to apply the pattern.
Positive SoTA use. Use CSC when a coarsened readable rendering is still worth using in project work, but only for a narrower admissible use and without assuming that the rendering carries the source-bearing side's admissibility.
The practical implication is the same across these traditions: coarsened readable publication faces or renderings are valuable, but their admissible use depends on source relation, relation kind, any validation evidence required by the declared use, audience, and reopen path. The worked slices in A.6.3.CSC:5.1 are the nearest recovery loci for those SoTA rows.
Semantic-web boundary. In the W3C row, Data on the Web, SHACL, and DCAT describe publication metadata, provenance, validation, cataloging, and interoperability. For an operative equivalence or substitution claim, establish the relation and support its bounded use under the pattern that governs that relation; apply F.9 when it is a Bridge between local senses with different interpretation bases.
Relations
- Specializes:
A.6.3 U.EpistemicViewingas same-EntityOfConcern controlled-loss constructionc : X -> Ybetween independently constituted epistemes. - Coordinates with:
A.6.3.CR,A.6.3.RT,A.6.3.NAR,E.17.EFP,E.17.ID.CR, F.9 for the Bridge and bounded-use claim, F.9.1 for an optional stance note about that claim,A.15,A.6.4,A.20, andA.21. - Entry relation: open CSC when a shorter candidate needs an explicit account of needed distinctions, any loss, anything added or strengthened beyond source support, the supported-use boundary and source return.
Yandcare required only when the result travels independently or their identity changes the receiving use; a readable form alone establishes neither. - Concrete contribution: CSC is a
specialization under A.6.3that supplies the controlled-loss, narrower-use, non-use, and source-return account. UseF.19:4to express a use boundary without adding unsupported warnings.
Boundary with quantum-like state-representation coarsening
For a less detailed account of a model, state representation, or evidence set, use the ordinary source-to-candidate comparison and first check at A.6.3.CSC:4.1-4.2. They already require that the candidate neither lose a distinction needed for the present use nor add or strengthen anything the source does not support. A dashboard row, partner-safe page, diagram, or coarse display may expose claim-bearing content through a publication form and carrier; readability alone does not identify an episteme.
C.26 becomes current only when a named quantum-like cue remains material after that ordinary CSC comparison—for example incompatible probes, contextual probability, an instrument-like update, an open-information-system update rule, or no faithful-enough export for the declared use. Without such a surviving cue, stay in CSC.
If the coarsened candidate claims to preserve action, intervention, manipulation, explanation, or cross-abstraction structure, state the correspondence or causal-abstraction relation before relying on that claim. C.26 may supply the additional quantum-like state-representation account only when the surviving cue requires it; CSC continues to supply the loss, unsupported-addition, narrower-use, non-use, and return boundary.
Independent reuse, formalization, empirical comparison, high stakes, or comparative performance can raise CSC identity or evidence demands. None of them opens C.26 by itself: a named quantum-like residue must remain. Do not add QL wording or apparatus to ordinary summary, anonymization, diagramming, audience adaptation, or controlled coarsening.
C.29 mathematical-lens use relation
When controlled semantic coarsening depends on mathematical abstraction, quotienting, coarse-graining, or a learned coarse representation,
A.6.3.CSCstill supplies the source-return condition, narrowed admissible use, non-admissible downstream claim, and coarsened-rendering account. Apply the current output-choice discipline atC.29:4.4and its authoritative output set atC.29:4.4.1; accept the result selected there, including a no-lens or neighboring-pattern outcome, instead of copying its output literals here. When C.29 selects a mathematical-lens result, it supports only the adequacy of the mathematical abstraction or coarse-graining lens for the stated use. It does not make the coarsened rendering a bridge, replacement source, evidence record, or causal-use admissibility.
A.6.3.CSC:End
ConservativeRetextualization: EntityOfConcern-Preserving Textual Re-Expression
Type: Specialization pattern Status: Stable Normativity: Normative
Problem frame
Use this pattern when available source claims about the same EntityOfConcern need another textual form, such as a report, summary, translation or filtered restatement. The receiving claims must remain supported by the identified sources under A.6.3.
Primary governed case. One textual re-expression of already available source claims whose resolved EntityOfConcern remains the same. The source and receiving epistemes concern that entity; the textual rendering expresses the receiving claims.
First useful move. Identify the source claims and resulting text, compare their meaning, and state any omission or loss that affects the intended use. If preservation is doubtful, name the missing basis or defect; repair it within CR when possible, or use the pattern for the changed claim.
What goes wrong if missed. A summary, translation, or manager-readable rewrite is treated as harmless editing after it has started hiding explanation work, bridge work, changed authority relation, or a narrower admissible use.
What this buys. A same-entity textual rewrite with visible source-relation tether and omission or loss notes, and a repair or next-pattern route when conservativity fails.
Ordinary use. A short source-to-result statement can suffice when the source relation, material omissions and intended use remain recoverable.
Fuller review. Add the information needed when a dispute, risk or intended reliance cannot be settled from that short statement. External citation, cross-context use or a release decision may make preservation, correspondence or use conditions material; they do not by themselves require every field in §4.3.
Use a neighboring pattern when explanation is primary (ExplanationFaithfulnessProfile), the intended operation depends on changing the representation language or reasoning medium (RepresentationTransition), the EntityOfConcern changes (A.6.4), or the work makes a comparative-review claim (E.17.ID.CR). F.9 governs an asserted semantic Bridge or its bounded use; F.9.1 supplies an optional stance note. A coarsened rendering whose loss requires a narrower use and return to the source is governed by A.6.3.CSC Controlled Semantic Coarsening.
Problem
Without a dedicated pattern for conservative textual re-expression:
- report, summary, translation, and filtered rewrite cases are handled ad hoc;
- authors treat textual simplification as if it were automatically conservative;
- the boundary to explanation-facing renderings stays blurry;
- correspondence-mediated rewrites are not distinguished from direct rewrites;
- subsequent users cannot tell whether the result remains a supported restatement or adds interpretation.
Forces
- Same entity, different wording. Readers need different textual forms without reopening the EntityOfConcern.
- Compression vs loss visibility. Shorter or plainer forms are often useful, but omissions and source-loss modes that affect interpretation or intended use must stay visible.
- Direct vs correspondence-mediated rewrites. Some rewrites use one source episteme; others depend on claims about relations among sources.
- Restatement vs another construction. Explanation, a material representation change and retargeting need their own conditions even when their outputs include text.
- Publication discipline. Admissible MVPK faces and publication renderings matter for textual rewrites.
Solution — entityOfConcernRef-preserving textual re-expression under A.6.3
Informal definition
ConservativeRetextualizationspecializes A.6.3 viewing for textual re-expression about the same EntityOfConcern.It preserves the EntityOfConcern resolved by each side's
entityOfConcernRefunder that side's effective ReferenceScheme, keeps the transform effect-free, and allows only claim-preserving or explicitly loss-declared rewriting of already available content.It may change register, ordering, textual density, language, emphasis or local wording. Its receiving assertions remain subject to A.6.3 conservativity. Separately asserted Bridge, reliance, authorization, Work, evidence or decision claims need their own grounds.
Here, entityOfConcernRef-preserving means that resolved-entity equality, not identical reference spelling. Keep a material reference or scheme change explicit under A.6.3:4.3.
Local working vocabulary
Use these local terms when distinguishing the source and rendering:
- Source slice = the already available pinned or otherwise reviewable textual content being restated.
- Published slice = the resulting textual rendering that remains under entityOfConcernRef-preserving discipline.
- Ordinary case = a reviewable same-entity rewrite where a short account keeps the source tether, omission notes, and neighboring-pattern conditions readable.
- Case needing fuller review = a case whose material preservation, correspondence or intended-use question requires more support than the short account supplies.
sourceSlice and publishedSlice are local review labels for the source textual slice and resulting textual rendering in one rewrite case. A publishedSlice remains a rendering label.
When one selected U.Episteme is made available, E.24.PUB identifies its audience and bounded-use declarations, the expression and carrier, and the obtaining EpistemePublicationRelation. When a reusable publication form is selected, establish that expression's conformance to its rules. Form-mediated expression and bearing claims use the same expression as witness. The slice label establishes neither a publication kind nor another episteme identity.
For example, a short restatement shared in a text file can identify the receiving episteme, audience, use, text and file without choosing a reusable form. If the receiving use requires a specified report form, the text must also satisfy that form's rules. The source tether, omission notes and conservative-rewrite conditions apply in both cases.
These local review labels follow the E.17:5.1e local-field rule.
Scope and exclusions
In scope
- entityOfConcernRef-preserving report rewrite;
- entityOfConcernRef-preserving summary;
- entityOfConcernRef-preserving translation between natural-language textual forms;
- declared filtering or foregrounding of already-present claims in textual form.
- correspondence-mediated textual synthesis in which every receiving claim is supported by the named sources and admitted correspondence claims.
Out of scope
- a difference between the EntityOfConcern values resolved by the source and receiving references, including a hidden change of EntityOfConcern (
A.6.4); - explanation-facing renderings whose main purpose is explanatory rendering rather than same-entity rewrite (
ExplanationFaithfulnessProfile); - a change of representation language or reasoning medium that makes a materially different operation possible, including aligning entries written in the same language for comparison (
RepresentationTransition); - comparison, abductive-prompt, ranking, recommendation, bridge-mediated, substitution, or action-selection work that introduces new claims rather than restating available ones.
Reader guidance
Use this pattern when the EntityOfConcern stays fixed and textual restatement remains the primary move.
- If the main change is explanatory, apply ExplanationFaithfulnessProfile.
- If the intended operation depends on a change of representation language or reasoning medium, apply RepresentationTransition.
- If the EntityOfConcern changes, apply A.6.4.
What the user checks first
Start with the preservation question:
- Is the published result still about the same EntityOfConcern?
- Does the reader need a clearer restatement, an explanation, or an expression in which a different operation becomes practical? When the last need calls for a change of representation language or reasoning medium, use A.6.3.RT.
- Can the reader see what was omitted, softened, or foregrounded?
- If several sources or correspondence claims contribute, can each receiving claim be traced to those sources and the rule that licenses it?
- Is the source merely pointed at, was it actually used, are the rewritten claims recoverable from it, and is the result admissible for the intended use?
- If any answer is doubtful, is the problem a missing source or condition, a repairable preservation defect, or a changed claim needing another pattern?
If omissions, softening, or filtering are admissible only because the published result is coarsened, tied to narrower admissible use, non-admissible for downstream use, and tied to source-bearing return, the case has crossed out of ordinary conservative retextualization even if the prose still looks like a summary. Use A.6.3.CSC Controlled Semantic Coarsening for that source-to-rendering relation.
Here, source-bearing return means returning to the source-bearing content. First identify any missing source or condition and repair and recheck a preservation defect within CR when the intended restatement can be restored.
A changed-claim exit applies when the attempted claim becomes explanation, representation shift, retargeting, gate, evidence, Work, assurance, or Bridge use: name that claim and use the pattern that defines, constrains, or tests it. Resolve the predicate or defining ClaimGraph only when the current claim or a named later use depends on that rule edition. A coarsened textual slice may need both source-bearing return and a changed-claim exit.
Only after these questions are answered does a fuller review record usually become worth writing.
Working-model first; explicit review record only when the case needs fuller review
Follow E.14’s working-model-first discipline: an ordinary report, summary, or translation keeps the source claims, preserved meaning and material omissions recoverable. When a changed claim needs another pattern, name that claim and its route. Put only the support needed for the current review or reliance question beneath that account.
Ordinary case (default). For everyday entityOfConcernRef-preserving rewrites, it is usually enough that the text or its surrounding publication keeps explicit:
- which source
U.Epistemeclaims are being re-expressed; - that the EntityOfConcern resolved by each side's
entityOfConcernRefremains the same; - whether the case is direct or correspondence-mediated when that is not obvious;
- what omissions or source-loss modes matter for the reader;
- any changed claim needing another pattern, when that question arises.
Explicit review record (when fuller review is needed). Include or inherit the fields needed to inspect the material preservation, correspondence, source-use or downstream-use question. Assurance, policy and cross-context cases often make such questions consequential. The record may inherit pattern ids and pinned metadata instead of restating them inline. Select only the applicable groups:
- transform relation (
patternSpecializationRef = A.6.3 specialization,relationFunctionClaimRef,sourcePublicationOrRecordForm,targetPublicationOrRecordForm,changeTargetRef); - preservation context (
entityOfConcernPolicy = preserve,boundedContextPolicy,viewpointPolicy,referenceSchemePolicyfor the episteme’s effective interpretation,representationLanguagePolicyfor the language of expression,groundingPolicy,referencePlanePolicy); - claim and publication discipline (
claimPolicy,claimScopePolicy,publicationScopePolicy,reliabilityTransportPolicy,pinningPolicy,provenancePolicy,lossProfile); - continuity and bridge discipline (
claimContinuityClass,microtheoryContinuityClass,onticContinuityClass,bridgeRequirement,conservativityWitness); - downstream and admissibility discipline (
worldContactPolicy,evidencePolicy,gatePolicy,workCrossing,upstreamPatternLocator,downstreamPatternLocator,admissibleFaces,admissiblePublicationRenderings,compositionRule,reopenCondition); - naming and presentation discipline (
publicNamePolicy).
Use the selected fields to expose the source claims, preserved meaning and conditions on which the receiving use depends.
Ordinary admissibility defaults
Default admissibility for ordinary entityOfConcernRef-preserving textual cases:
- primary admissible faces are
PlainViewandTechCard; - bounded report-only use is admissible when source pins, provenance, loss notes, and entityOfConcernRef-preserving conservativity remain visible;
InteropCarduse is admissible only when the governing publication-face source explicitly permits source-pinned, text-preserving export without added semantics;AssuranceLaneor gate-bearing use is not default and requires governing publication-face policy plus source-pinned conservativity without hidden strengthening.
Direct and correspondence-mediated profiles
Direct ConservativeRetextualization
- source slice and published slice are textual re-expressions of one source episteme;
- no
CorrespondenceModelRefis needed; - the short account identifies the source and any material loss or provenance condition.
CorrespondenceConservativeRetextualization
- the receiving text depends on claims about governed relations among epistemes or views concerning the same EntityOfConcern;
- identify those relations and the supporting claims; when a reference to their describing episteme is needed, local
CorrespondenceModelRefdesignates that episteme under A.6.3:4.5, without introducing a U-kind; - every receiving assertion remains supported by the named sources and admitted correspondence claims, with the same EntityOfConcern and declared material loss.
Cross-language translation is not automatically direct. If the translation depends on declared correspondence, reference-scheme mediation, or bounded equivalence notes, it must be treated as correspondence-mediated.
Recurring same-entity textual moves
Examples of textual moves that can preserve the same EntityOfConcern include:
- Register shift — a technical statement is rewritten into plainer engineer-manager prose without changing what is being said about the same entity.
- Summary or filtered restatement — a source note is shortened or focused on one declared slice, with omissions stated.
- Cross-language restatement — the same source claim is restated in another natural language while the same source tether and same-entity line remain explicit.
- Correspondence-mediated textual synthesis — one text combines supported claims through identified relations among the sources; any separate Bridge or substitution claim keeps its own conditions.
Each example remains under A.6.3 only while the same-entity and conservativity laws hold.
Shared conservative retextualization rule bundle
Preservation rule
A case under ConservativeRetextualization preserves the same resolved EntityOfConcern, the declared bounded context and support from the identified available source claims while changing wording, register, language, ordering, or density. Keep conditions on claim scope, publication scope, pins, provenance, grounding and ontic scaffold recoverable where they affect interpretation or intended use. State whether the case is Direct or Correspondence when that distinction is not already obvious.
Loss and reliability rule
State omissions, foregrounding and source-loss modes that affect interpretation or intended use. A reliability assessment may remain source-bounded or be explicitly downgraded; clearer prose alone does not warrant a higher assessment.
Authority and changed-claim boundary
A case reviewed under this pattern stays about the same entity and remains an episteme-to-episteme textual rewrite. It does not establish explanation faithfulness, an F.9 Bridge or bounded-use suitability, retargeting, current reliance, authorization, or actual receiving use. If the rewrite becomes explanatory, Bridge-bearing, gate-bearing, or world-facing, state the attempted claim and use the pattern that defines, constrains, or tests it.
Use F.9 for a semantic Bridge between two F.17 local senses or a proposed bounded use of that Bridge. Take a current reliance question to triggered A.10 or B.3 and authorization to the pattern that directly constrains the receiving act.
For an asserted occurrence, first recover the object or occurrence under its direct obtaining or admission rule, then cite the evidence on which the assertion relies. A dated Work claim needs A.13 and independent A.15.1 admission; add F.6 only for precise assignment-bound attribution. Do not create those records when their branches are not live.
Composition and reopen rule
For deterministic replay or composition, use A.6.3:4.7. To claim that a further normalization leaves the result unchanged, identify the first and next rewrite arrows, establish the same resulting episteme and the required composite equivalence, and supply a fixture or proof. Different rewrite orders may yield different results. Reopen the affected claims when a needed source, correspondence witness, provenance, publication-form condition or preservation basis is no longer recoverable. Revalidate them when such a dependency changes materially, even if it remains explicit; unaffected claims retain their grounds. E.17:5.1b–c supplies the applicable reopen conditions.
Correspondence and its receiving use
A correspondence claim used by the rewrite and a claim that the result suits a receiving use are separate. Apply §4.5.c to any Bridge, reliance, authorization or actual-occurrence claim needed by that use; the existence of correspondence alone settles none of them.
Local conservativity witness for borderline textual cases
For borderline textual rewrites, the user treats the case as conservative only while each point below remains visibly preserved or its loss is declared and admissible for the stated use. A missing basis or repairable defect follows the repair route in §4.2.b; a changed claim or use follows the pattern that defines, constrains, or tests it.
- Modality and force. A rewrite may not silently turn possibility, uncertainty, permission, obligation, recommendation, decision status, bounded scope, temporal window, or hypothesis language into a wider commitment.
- Caveats and qualifications. A rewrite may not quietly remove conditions, exception notes, uncertainty markers, or temporal qualifiers that still matter for interpreting the same source.
- Reliability assessment. Cleaner prose, better ordering, or manager-facing polish may not silently raise confidence, warrant claim, or readiness for action.
- Bridge and receiving-use boundary. Same-entity textual fluency may not establish a semantic Bridge between local senses, bounded-use suitability, current reliance, authorization, or a comparative-review occurrence. Open only the F.9, A.10 or B.3, authorization, or occurrence branch that the later use needs; recover an asserted occurrence under its direct obtaining or admission rule.
- Alternative preservation. A rewrite may not collapse open alternatives, rival hypotheses, or declared plurality into one apparently settled interpretation unless the loss is stated and still admissible under this pattern.
This witness is local to ConservativeRetextualization. It does not replace the broader conservativity invariants of A.6.3; it makes them inspectable for textual rewrites where fluent prose can otherwise hide strengthening.
Archetypal Grounding
Same-EntityOfConcern report rewrite
Source note slice. Service S exceeded the latency threshold in the evening batch window. Trace T-44 and dashboard pin D-17 show the spike. Two low-confidence hypotheses remain open.
Published report slice. Evening-batch latency for Service S exceeded the threshold. Source pins: Trace T-44, Dashboard D-17. Low-confidence hypotheses are omitted here and remain in the pinned source note.
This is an admissible direct ConservativeRetextualization because the EntityOfConcern stays fixed, the report remains textual, and the omission is stated. In ordinary internal use, this often needs only source pins plus visible omission notes rather than a full explicit review record.
Ordinary inherited-pin summary
Pinned source cluster. In this example, N-14 is the source note in §5.1; N-14, trace T-44, and dashboard card D-17 are already published together under one incident review bundle.
Published stand-up slice. Evening-batch latency exceeded the threshold for Service S. See N-14 / T-44 / D-17 for the pinned source cluster.
For reporting the threshold exceedance, this short slice may inherit the published pins and omit the separate hypotheses because it asserts no cause. A causal decision would need the hypotheses and their qualifications from N-14. The source remains reachable to the reader.
Benign omission that stays ordinary
Source note slice. Service S exceeded the latency threshold in the evening batch window. Trace T-44 and dashboard pin D-17 show the spike. The note also lists two low-confidence hypotheses for separate investigation.
Published stand-up slice. Evening-batch latency for Service S exceeded the threshold. Source pins: T-44, D-17. Low-confidence hypotheses are omitted from this stand-up note and remain in the pinned source.
This stays ordinary ConservativeRetextualization because the omission is declared, the same EntityOfConcern remains visible, and no separate narrower admissible use, non-admissible downstream use, or source-bearing return is needed to justify the omission. Ordinary omission alone is not controlled semantic coarsening.
Functional-description textual summary
Source note slice. The principle scheme says: choose method family MF-2 for small-batch mixing when material X remains below threshold T; selected method M-2 still requires work plan WP-17 and result measurement RM-4.
Published summary slice. For small-batch mixing, choose method family MF-2 when material X remains below T. Selected method M-2 still requires work plan WP-17 and result measurement RM-4.
This remains ConservativeRetextualization because it restates the source's selection rule and preserves its planning and measurement requirements. The summary supports interpretation and source-finding. Keep WP-17 and RM-4 recoverable whenever they affect the stated interpretation, decision or performance; actual use must satisfy the applicable requirements.
A shorter summary used only to select a method family may omit requirements for performing the selected method when that omission does not mislead the reader about the summary's scope or make M-2 appear ready for execution.
If material loss is admissible only with a narrower use and return to the source, use A.6.3.CSC Controlled Semantic Coarsening with that narrower admissible use, forbidden stronger use, and source-bearing return. For stronger use, apply the governing requirement to the current facts; the CSC label or a reference alone does not satisfy it.
Generated-summary source-relation variant
A generated summary follows the same source, EntityOfConcern and conservativity conditions as any other rewrite. A model-produced paragraph over an inspection or method-selection note is not an explanation merely because it was generated. Restated claims, material omissions and use conditions must be recoverable. Use the distinctions below when a source-use or support question affects reuse, citation or reliance.
When the generated-summary case needs shared vocabulary, use only the E.17:5.1b source-relation or bounded-use distinction that changes the present use. Keep claim recoverability from the source separate from admissibility for that use, and an unknown relation separate from one known absent. The same source governs independent-verification claims and reopen conditions.
The summary may expose or cite the source slice it restates. It does not become that source slice by fluency, brevity, translation, layout, generated form, or reuse. If the needed source content, governing requirement, or case relation is missing, a repair request or source-gap note is only prospective: it neither establishes earlier source use nor supplies the missing claim support or use condition.
If the generated summary is source-pointer-only, merely plausible, claim-widened, or carrying added linkage, do not treat it as a conservative source-equivalent summary. For source-finding or orientation, retain only the justified pointer and separate any unsupported or new proposition from the source-backed account. Repair the claim against the source, or apply A.6.3.CSC, ExplanationFaithfulnessProfile, RepresentationTransition, E.17.ID.CR, A.15, A.10, or another pattern that defines, constrains, or tests the claim. An orientation or coarsening label alone does not make an unsupported claim source-faithful.
Same-EntityOfConcern rewrite via declared correspondence
Source design slice. Cooling loop CL-2 preserves safe temperature margins during standard operating demand.
Source safety slice. Cooling loop CL-2 maintains the temperature condition required for hazard-control claim HC-7 during standard operating demand.
Published joint-review slice. For standard operating demand, Cooling loop CL-2 is described in both the design and safety views as maintaining the required temperature condition. This summary relies on CorrespondenceModel CM-12 and does not add claims beyond that declared overlap.
The synthesis remains in this pattern only while its source relation is explicit and every receiving claim is supported by the design slice, safety slice or admitted correspondence claims. CM-12 names the episteme stating that correspondence; its label alone supplies no witness. Add the review detail needed to establish the claimed overlap.
Cross-language re-expression without hidden bridge work
Source slice. The backup controller stays in passive watch mode until the primary loop fails two consecutive heartbeat checks.
Published slice. Резервный контроллер остаётся в режиме пассивного наблюдения, пока основной контур не провалит две последовательные проверки heartbeat.
English reader gloss (comprehension aid only). The backup controller remains in passive observation mode until the primary loop fails two consecutive heartbeat checks.
Russian пока … не uses a negative particle where English until the primary loop fails has none. In both versions the backup continues to watch until the primary has failed two checks in a row. Omitting the second failure or reversing the condition changes the event up to which passive watching is required. The gloss helps an English-only reader follow this difference. It is a comprehension aid, not a second source or verification of the Russian translation. A conservativity claim still requires suitable language competence or other evidence for the same-claim, same-EntityOfConcern, and hidden-bridge tests.
This remains in ConservativeRetextualization only if the translation is tethered to the same source claim, preserves the same EntityOfConcern, and adds no claim beyond the source. Apply F.9 only when a semantic Bridge between local senses or a proposed bounded use of that Bridge is claimed.
Boundary to controlled coarsening
Source slice. Vendor bulletin VB-7 requires rollback when pressure drift exceeds 2.5%, and it keeps two equipment-specific exceptions in the pinned annex.
Published coarsened slice. Pressure drift above 2.5% is a warning condition in the bulletin. Check the pinned bulletin and annex before treating the note as rollback guidance.
This does not remain ordinary ConservativeRetextualization. The coarsened slice drops equipment-specific exceptions and remains only an orientation warning: it is not an executable rollback command. It is admissible only through narrower admissible use, non-admissible downstream use, and source-bearing return to the bulletin. Once that narrower-use boundary becomes primary, the case leaves ordinary same-entity rewrite and must use A.6.3.CSC Controlled Semantic Coarsening.
Boundary to explanation-facing renderings
A text is rewritten not mainly to restate the same source, but to explain why it matters, simplify reasoning for a learner, or narrate a mechanism. That move should leave ConservativeRetextualization and be reviewed under ExplanationFaithfulnessProfile.
Boundary to representation transition
A reader can need the same events aligned by component to compare recurrences. The event descriptions can stay in the same language while their arrangement makes that comparison practical. A change of representation language can also make an operation possible. Use RepresentationTransition when that change is the point of the work.
Bias-Annotation
This pattern biases toward same-entity conservativity and away from explanation or retargeting inflation. The main mitigation is to repair a preservation defect within CR when possible and apply ExplanationFaithfulnessProfile, RepresentationTransition, A.6.4, or the pattern that defines, constrains, or tests the changed claim or use when it requires leaving same-entity textual restatement.
Conformance Checklist
- CC-CR-1 — Same EntityOfConcern remains explicit.
The EntityOfConcern values independently resolved by the source and receiving
entityOfConcernRefvalues are equal. - CC-CR-2 — Textual re-expression remains the right family. The intended use is served by a textual restatement. Check whether the reader instead needs an explanation or an operation made possible by a change of representation language or reasoning medium.
- CC-CR-3 — Material loss, provenance, pinning, and reliability conditions remain recoverable. The case makes conditions that affect interpretation or intended use recoverable from the text, its surrounding publication, or the source references on which that use depends.
- CC-CR-4 — Direct or correspondence-mediated construction is identifiable. The source relations make the profile recoverable; state and justify the distinction explicitly when it is not obvious.
- CC-CR-5 — Correspondence witness is named where needed.
If correspondence-mediated, identify the relations and supporting claims; use
CorrespondenceModelRefwhen their describing episteme must be cited. - CC-CR-6 — Local conservativity witness remains satisfied. The reviewed case does not silently widen modality, remove caveats, raise reliability assessment, add an F.9 Bridge or bounded-use suitability claim, establish current reliance or authorization, claim that receiving use occurred, or collapse declared alternatives beyond stated loss notes.
- CC-CR-7 — A missing condition, preservation defect, or changed claim is explicit on failure.
If the case fails a check, name the missing source or condition, the repairable preservation defect, or the changed claim. Repair and recheck within CR when the intended restatement can be restored. For a different claim or use, name the pattern to use next (
ExplanationFaithfulnessProfile,RepresentationTransition,A.6.4,B.5.2, or another applicable pattern). - CC-CR-8 — Working-model first remains intact. Ordinary same-entity rewrites stay lightweight; fuller explicit review records carry the fields needed for cases requiring fuller review.
Common Anti-Patterns and How to Avoid Them
Consequences
- Readers can inspect the connection between the source claims and the rewritten text.
- Direct and correspondence-mediated variants stay visibly separated.
- Loss, provenance, and reliability conditions that affect interpretation or intended use remain recoverable.
- Ordinary working-model use stays lightweight, while cases needing fuller review get the additional record content their risk and use warrant.
- The pattern remains bounded by
A.6.3,A.6.4, explanation-facing work, and representation-shift work.
Rationale
Conservativity depends on what the text commits the reader to, not on shared vocabulary alone. Recovering the source claim and its modality, conditions and alternatives makes a changed commitment visible. That comparison guides a local repair: restore a lost condition, declare an admissible omission, or separate a new claim for its own justification. Direct and correspondence-mediated cases use the same test, with the latter also depending on the identified relations among sources.
Source contributions and limits
The source lines below inform different parts of textual preservation. The same-EntityOfConcern and episteme-identity rules are FPF conditions; they are not supplied by a citation alone.
For source recoverability, independent-verification claims and reopening, use the distinction needed from E.17:5.1b. E.17:5.1c supplies shared use-boundary terms and E.17:5.1d selects the primary boundary. Those rules apply here to same-entity textual restatement.
Relations
- Builds on:
A.6.3,A.6.2,A.7,E.10.D2,E.17.0,E.17,F.9,F.18,E.10 - Coordinates with:
ExplanationFaithfulnessProfile,RepresentationTransition,E.17.ID.CR ComparativeReviewUnit,A.6.4,B.5.2,A.15 - Failed conservativity: name the missing source or condition, repair and recheck a preservation defect within CR when possible, or apply the pattern for the changed claim or use. Retargeting uses
A.6.4, abductive work usesB.5.2, and action or work claims use the applicableA.15pattern; explanation, representation change, and other live claims keep their own routes. - Boundary notes: explanation-facing cases apply
ExplanationFaithfulnessProfile; changes of representation language or reasoning medium material to the operation applyRepresentationTransition; bounded comparative review cases applyE.17.ID.CR ComparativeReviewUnit; EntityOfConcern changes applyA.6.4.
A.6.3.CR:End
Representation Transition: Change Representation of the Same EntityOfConcern
Type: Specialization pattern Status: Stable Normativity: Normative
Problem frame
Use this pattern when changing the representation language or the reasoning medium helps someone inspect, compare or calculate using the same material. A table shown in time order and the same table aligned by component can use one language while supporting different comparisons. Exporting the chosen table to another file can leave both the language and the reasoning medium unchanged.
Start with the content that must survive and the action the new representation should support. The source can be givens, constraints and a partial construction while the answer is still unknown. Construct the target representation in the chosen medium. Compare it with the source and state what was preserved, foregrounded, rearranged, lost or newly suggested. Exact episteme identities are not prerequisites for this ordinary first result.
Plain starting vocabulary:
First useful move. Name the content that must survive and the intended user action, choose the representation, make it, and compare it with the source. State the material preservation, loss and use conditions in a compact note. Add a rejected use or return condition only when it changes what the reader should do.
What goes wrong if missed. A cleaner table, diagram, notation, or decoded rendering is treated as harmless formatting after it has hidden uncertainty, changed the concern, imported a new relation, weakened recoverability, or invited a stronger action than the source supports.
What this buys. Users gain a representation suited to their task while preservation, reasoning affordances, loss, unsupported strengthening, and source return stay visible.
Ordinary use. For inspection, comparison, source-finding, technical discussion, or reversible planning preparation, the target representation and compact note are normally enough.
Exact claim identity. Open the episteme-construction branch when a receiving use depends on exact claim identity or an explicit preservation construction. Independent citation, a consequential scheme crossing, disputed support or a decode-mediated claim can create that need. Recover source episteme X, receiving episteme Y and viewing construction v : X -> Y, together with the source claims and relations on which v depends, and the scheme relation, loss/recoverability or assurance needed by that use.
Later-specific occurrence. Open RepresentationTransitionRelation@Context only when actual representation-transformation Work and the six participants defined in §4.1.b are themselves material. An exact v : X -> Y does not imply that occurrence.
Not this pattern when. Use A.6.3.CR for faithful restatement or translation when the receiver needs the same claims in other words or another language, A.6.3.NAR when reader-useful narrative ordering is primary, E.17.EFP when explanation adequacy is primary, A.6.4 when the EntityOfConcern changes, A.7 for carrier work or extraction that has not yet constituted a receiving episteme, and A.6.3.CSC when a narrower-use coarsened receiving episteme is primary.
Problem
Common failures:
- teams treat text-to-table, table-to-diagram, and notation shifts as harmless formatting;
- changes in reasoning medium and recoverability remain implicit;
- a visible edge, row, geometry, or decoder output silently imports claims that the source did not make;
- latent or distributed representations tempt users to treat feature geometry as ontology-by-default;
- users cannot tell when the case has become retargeting, explanation, narrative ordering, carrier work, bridge use, or controlled coarsening; and
- exact endpoint, occurrence, Work, publication, and assurance records are demanded before an ordinary useful target representation exists.
Forces
- Same concern, different reasoning medium. Teams need representations suited to different tasks without silently changing what the claims concern.
- Legibility vs recoverability. A clearer target helps only if users can recover the source content and distinctions needed by the declared use.
- Useful foregrounding vs unsupported strengthening. Tables, diagrams, notation, and interactive views can expose structure while also making added links look source-given.
- Representation change vs ontology change. New notation or geometry can make structure visible; visibility does not establish world-side structure or a new EntityOfConcern.
- Progressive exactness. Ordinary conversions should stay easy, while externally relied-on or decode-mediated cases retain exact identity, source dependencies, loss, and evidence discipline.
- Recoverability before decode ambition. Directly inspectable cases establish the normal entry; latent cases need explicit decoding access and evidence for their use.
Solution — preserve practical content across a representation change
Ordinary representation move
Produce the useful target first:
- Name the user action the new representation should help: compare, inspect, traverse, calculate, communicate or replay. Identify the user's familiarity with the notation when that changes what they can do with it.
- Point to the source material. Recover the givens, constraints and partial construction, including the claims, commitments, uncertainty and source references that must survive. Keep unknowns identifiable as unknowns.
- Choose a target representation and a medium in which the user can perform the intended operation. When the target is an expression in a representation language, identify the formation and interpretation conventions it needs. A familiar notation may suffice. For a physical arrangement or a learned representation, establish how the user can obtain a reading or make a comparison and what warrants using it for this inquiry.
- Make the smallest target that supports the action. Arrange its parts so they can be used together: for example, keep a shared element recognizable in two groupings, or align a sequence of signs with a temporal reference. Explain any meaning-bearing mark, position or timing whose interpretation is not already clear from the selected conventions. A.6.3.RT.OE develops this construction when the expression's parts must be prepared for the intended operation.
- Compare target and source. Mark what is preserved and foregrounded; what is rearranged, omitted or harder to recover; and which visible links or interpretations were added by the representation.
- Try the intended operation when a short trial can decide whether the representation is useful. Apply the relevant mathematical, physical or other subject Method. Use the result to judge or repair the representation.
- State the representation and reasoning-medium delta only as far as it changes use or blocks a likely overread.
- State the supported use. Add a non-admissible use or return condition when a source limitation, representation feature, observed misunderstanding or applicable risk gives a plausible reader a consequential reason to need it. Name the return destination when return is required.
The first result is the target representation and its representation note. When work with the representation establishes a new claim, its construction, observation or argument supplies the grounds for that claim. Attribute preserved claims to the original givens and newly established claims to the work that supports them, even when both concern the same entity.
Choose another representation language when the current language cannot express a distinction that matters to the work. Developing new signs or formation rules is notational design. A.6.0 supports a reusable vocabulary and its laws, and A.6.1 the declaration of operations. Use the chosen conventions to construct the expression.
The following questions can guide a compact note; retain only entries needed to interpret or use the target:
Exact episteme-construction branch
Open this branch when the receiving use depends on exact claim identity or an explicit preservation construction, as described in §1. The need comes from that use, not merely from a target being generated, cited or displayed independently.
Then establish the A.6.3 construction v : X -> Y:
- identify source episteme
Xand receiving epistemeYindependently under C.2.1 by claim content, EntityOfConcern, and effectiveReferenceScheme; - require the same EntityOfConcern; a changed concern requires A.6.4;
- state how claims in
Xand any named additional source epistemes construct the claims inY; - compare the effective interpretation rules of
XandY, including the case in which they agree. State what the construction preserves, foregrounds or loses, what remains recoverable, where strengthening is prohibited and when the user should return to the source. - cite the grounds for each correspondence relation on which
vdepends. When reproducing the operation requires a particular expression, identify the expression actually used at each relevant endpoint and its representation language or decoding conditions. A change of expression can matter even ifXandYhave the same effective rules.
Identify X and Y from their claim content, EntityOfConcern and effective schemes. A model or decoded output can supply an endpoint if those C.2.1 conditions are established; its label, visible form or carrier does not establish them. When an endpoint cannot yet be identified, retain the useful rendering or candidate carrier without asserting the exact construction.
Apply C.2.1:4.1.1 to the boundary between effective semantic rules and expression conventions. Rewriting signs through an already interpreted equivalence can preserve the same rules and episteme. Changing a designation meaning, operator rule, qualification, domain or interpreted dependency changes the effective scheme even if one selected answer is preserved.
An exact v performs no Work and is not a relation occurrence. A system may perform representation-transformation Work under A.15.1; methods, source-use relations, A.6.1 bindings, and any A.15.PROD inception claim remain separate. E.17.0 independently decides viewpoint conformance and dependent U.View membership. E.24.PUB independently identifies publication occurrence, form, carrier, audience, and bounded use. Completing the exact construction does not itself authorize reliance.
Later-specific six-participant occurrence
Use RepresentationTransitionRelation@Context only when the transition occurrence is itself needed and all six participants plus Work are present. The suffix @Context retrieves one independently selected A.1.1 BoundedModelUseStructure : U.Structure; it introduces no generic context kind or description-context field.
The six SlotSpecs and their direction define the RelationSignature. X and Y concern the same entity. The subject of the source rules-description episteme is the effective interpretation rules of X. The subject of the receiving rules-description episteme is the effective interpretation rules of Y. Each description has its own claims and its own effective interpretation rules. To fill a description slot, supply the episteme with that subject. A language reference identifies a language. A rules-description slot takes an episteme. A manual whose subject is the equipment may mention the table rules without supplying the required description episteme.
A positive occurrence obtains only when all of the following hold together:
- all six participants resolve, and the
BoundedModelUseStructurewas independently selected because its model-use organization changes this transition use; - A.13 identifies the performer, and A.15.1 independently admits the dated representation-transformation Work. If the current use also needs to say exactly which assignment covered that Work, F.6 checks that separate relation against the same A.13 assignment; F.6 identifies neither performer nor assignment, and a missing or failed attribution alone does not overturn independently admitted Work. If the finding also invalidates a premise consumed by A.13 or A.15.1, recheck that premise and the claims that depend on it. The Work uses all six participant values collectively through its governed inputs, result, references, A.6.1 bindings, or a combination of these;
- exact
v : X -> Ystates claim construction, endpoint-scheme relation, same EntityOfConcern, preservation, loss or recoverability, prohibited strengthening, applicability, use, and return; and - every depended-on correspondence is a separately governed relation or claim.
Work, performer, assignment, method, operation application, source-use relations, and any inception claim are not seventh participants or identity discriminators. Work alone proves neither v nor the occurrence. Conversely, an inspectable v without the selected model-use structure and Work remains an ordinary exact construction.
The occurrence is participant-determined by the six-participant tuple. Changing any participant identifies another occurrence. A repeat Work episode, evidence change, publication, form, carrier, layout, transition-description edition, or C.29 output does not reidentify an unchanged tuple. A changed C.2.1 discriminator of X or Y first identifies another episteme and therefore another tuple.
Transition description and source-relation epistemes
For a durable description of an obtaining occurrence, first establish that occurrence. Identify its description episteme under C.2.1 by claim content about the six-participant occurrence, that occurrence as EntityOfConcern and the description's effective ReferenceScheme. Editing the claim graph creates another description episteme without changing the occurrence.
A description may record the following comparisons. When the receiver needs to reproduce an operation on particular expressions, identify the expressions and their language bindings or the applicable decoding conditions. The six participants in §4.1.b identify the occurrence.
At least one of loss and recoverability is explicit; both are explicit when distinctions are lost and a recovery route is claimed.
When the use needs a separate reference-bearing episteme about a source relation, identify it by its C.2.1 triple: claims about that relation, the relation as EntityOfConcern and an effective scheme. Include the relation kind, signature or defining pattern only as needed to recover the claim used by v. A claim cited within a broader source episteme can remain there; identify that source and claim without requiring a second relation-description episteme. Citation alone does not establish that the relation obtains.
Publication may expose X, Y, the occurrence, or its description; forms, carriers, C.29 representations, and publication occurrences substitute for none of them.
Progressive use and local vocabulary
Use three levels, without copying one level's burden into another:
- Ordinary target: target representation plus compact note.
- Exact construction: add
X,Y,v, endpoint schemes, source dependencies, and claim-level loss/return when the receiving use triggers them. - Actual transition occurrence: add the six-participant relation, Work, and optional occurrence-description episteme only when that historical relation is itself material.
Use detailed vocabulary only when it changes the next representation decision or blocks a concrete overclaim:
- semiotic mode — the meaning-bearing relation doing the main work, such as structural likeness, trace, conventional code, model-mediated correspondence, or decode-mediated recovery;
- factor delta — the representation-factor change material to review;
- source dependencies of
v— the identified source claims and relations on which the construction depends, including which are needed jointly for each part of it and any required precedence between those parts. This dependency structure can branch or join; - source-return references — links or other locators used to reopen source material for omitted detail or a changed question;
- decode-mediated case — a case whose receiving interpretation depends on a declared decoding or access relation;
- actionability shift — an apparent change in what users think they can do, which is not work authority, gate status, or permission; and
- recoverability evidence — evidence that omitted content can be recovered well enough for the declared use.
State the actual use, loss, evidence, and return once. Use A.10 or B.3 only when a specific evidence or assurance claim is current.
Direct and correspondence-mediated constructions
In a direct exact construction, Y is constructed from X and fixed declared configuration. State the claim construction, endpoint-scheme relation, same EntityOfConcern, preservation, loss/recoverability, prohibited strengthening, applicability, use, and return; no generic correspondence object is required.
In a correspondence-mediated exact construction, Y depends on additional source epistemes or governed relations among their claim-bearing contents. Recover each needed relation and the source claims used by v. A table, model or graph may carry those claims and their grounds; its presence or a scheme difference alone does not establish that the relation obtains. Cite a separate relation-description episteme only when the construction needs one.
Both profiles retain the same EntityOfConcern. A correspondence by itself establishes neither an F.9 Bridge nor any substitution, comparative-review, evidence, or publication claim. Add C.29 only for a current mathematical modeling or reasoning use.
Recurring moves and useful deltas
Recurring move shapes include tabulation, diagramming, structured-notation shift, and a same-EntityOfConcern correspondence-mediated representation shift.
In ordinary language, say what changed and why it helps: “the table foregrounds row comparison”, “the diagram foregrounds dependency shape”, or “the notation foregrounds explicit argument positions”. Add salience, topology, actionability, calibration, interactivity, or semiotic-mode detail only when it materially changes use or misuse risk.
Preservation, loss, decode, and composition
Preservation and conservativity
The ordinary move preserves the practical content named for the use. The exact branch compares two independently constituted epistemes concerning the same entity. Establish what readers can recover under the effective interpretation rules of each endpoint and what the new expression lets them do.
Check for unsupported strengthening when a target:
- upgrades a source-visible relation into dependency theory or another relation not present in the source;
- turns geometry, notation, embedding proximity, or decoder output into ontology-by-default;
- adds a Bridge, substitution, comparative, mechanism, temporal, or control claim that the source does not state and that has not been independently established under its governing pattern;
- collapses source alternatives, uncertainty, or bounded scope into one wider commitment; or
- treats decode-mediated recovery as direct givenness.
Check each target-side connective against the source or same-EntityOfConcern correspondence. A clearer, more structured, or more formal target does not establish a broader reliability claim.
Loss and recoverability
State which distinctions, inspection possibilities, uncertainty cues, or local qualifiers are lost, foregrounded, rearranged, or harder to recover. The target may remain useful under a reliability claim bounded by the source or with an explicitly narrowed admissible use. If the target is admissible only for a declared narrower use with source return, A.6.3.CSC is primary.
If the target omits a condition, establish how the recipient is to interpret the omission. An extract that says nothing about joint operation may leave the reader to consult the source. A replacement model that expressly permits the settings of two controllers to be chosen independently can admit a combination the source ruled out, even when each controller still has exactly the same settings. Compare the permitted combinations for the same inquiry under B.5.MR. For a strict abstraction, establish a feasible source answer, show that every source answer remains permitted and identify an additional answer permitted by the replacement. When the target provides no answer to that inquiry, report the limit of the extract's use.
Decode-mediated entry
A latent or decode-mediated case stays bounded until it has source material for the same concern, a decoding or access relation, recoverability evidence for the intended use, and a supported use. State any needed user action, excluded use or source-return condition under §4.1. When exact reliance is claimed, recover source episteme X, receiving episteme Y, construction v, and the source dependencies of v defined in §4.2.
A latent region, embedding, probe result, decoded rendering or publication may help locate the case. To use an episteme endpoint, recover its C.2.1 identity rather than inferring it from a label or readable output. Missing recovery evidence leaves the affected use exploratory, report-only or unavailable, according to what the remaining grounds support.
Composition and reopen rule
A normalization repeat claim follows A.6.3:4.7: identify the first and next arrows, the same resulting episteme and composite equivalence, with a fixture or proof. Different orders of representation shifts may yield different results. For an ordered sequence, compare each source and target and carry forward earlier loss. Keep the content under test, scheme change, preserved or withdrawn commitments, loss/recovery and remaining action recoverable at each step.
Reopen the affected account when source content, endpoint identity, recovery assumptions, pins or provenance, correspondence or counter-witness disposition, primary semiotic mode, intended publication or receiving use, or accumulated loss changes. A changed EntityOfConcern requires A.6.4; a changed target-side claim uses the pattern that defines that claim.
Boundary triggers
Archetypal grounding
Ordinary same-concern text-to-table move
Source slice. Service S showed three recurring latency spikes in the evening batch window. Trace T-44 and dashboard pin D-17 concern the same service and time window.
Target table. These are recurring latency spikes.
The first result needs no endpoint dossier. The note says the service, window, count, recurrence, and pins can be inspected together; those claims survive; prose order is lost; no causal or severity claim is added; use is inspection; and any question about an omitted qualifier or causality returns to the source note and traces.
An independently cited target includes the recurrence caption. When the receiving use needs the exact preservation construction, identify source episteme LatencyFinding-X and receiving episteme LatencyTable-Y. Both concern Service-S-during-W under effective schemes ServiceTelemetryScheme-4 and TabularTelemetryScheme-2. TabulateLatency : LatencyFinding-X -> LatencyTable-Y is the exact construction; it states claim construction, endpoint-scheme relation, same EntityOfConcern, preservation, omission and recoverability, prohibited strengthening, applicability, inspection-only use, and return to the source note and traces. The visible table form and file carrier are not Y.
A diagram used in a geometric construction
A.6.3.RT.OE:5.1 develops the equilateral-triangle construction on a nonzero segment AB in the Euclidean plane. It keeps the same segments available as radii of two constructed circles and as sides of the triangle. The radius equalities can then be combined in the geometric argument.
For the RT use, the source consists of the construction instructions and intermediate geometric relations. The representation note preserves the circle constructions and segment identities, names joint inspection as the gain, and returns to the subject premises if an intersection or equality is disputed. Geometry supplies the construction and justified conclusion; drawing measurements are not proof premises. The construction and drawing can develop together.
Syllables against a hand-cycle reference
A.6.3.RT.OE:5.3 prepares given syllable-duration assignments against a learned three-beat hand cycle with four pulses per beat. Arithmetic and rhythmic composition determine the six-pulse preparation and the phrase's ending at the third cycle boundary.
RT's representation note retains duration assignments, pulse constancy and cycle position, identifies coordination with the hand reference as the gain, and returns to those conditions when the ending no longer aligns. The utterance and gestures can both represent rhythmic content and realize rhythm. Fluency or learning requires observation when either is the question.
Positive later-specific table-to-diagram occurrence
For this identity-and-obtaining illustration, take the stated endpoint, scheme, model-use, Work and binding facts as hypothetical givens. The source table, receiving diagram and omitted qualifiers are not shown, so this case does not replay their preservation comparison.
Source episteme CoolingLoopRelationTable-X and receiving episteme CoolingLoopDependencyDiagram-Y state the same two connection claims about CoolingLoop-7 under effective schemes TabularPlantScheme-5 and DirectedDiagramPlantScheme-3. Y is a candidate episteme, not automatically a U.View.
The epistemes TabularPlantInterpretationRulesDescription-5 and DirectedDiagramPlantInterpretationRulesDescription-3 identify the rules for reading the table and diagram respectively. Each describes the effective interpretation at one endpoint. Independently selected CoolingLoopReviewModelUseStructure satisfies A.1.1 because its model-use organization changes this review.
A.13 identifies PlantModelingTool-2 as the performer through the covering assignment. A.15.1 independently admits dated CoolingLoopDiagrammingWork-18. Because this example states precise assignment-bound attribution, its direct case fact says that the Work was performed under the same A.13 assignment, so the F.6 check is positive. If that direct fact were missing, attribution would remain unresolved. If the facts refuted an F.6 condition, that attribution would fail. Neither outcome alone overturns the independent Work admission. A finding that also invalidates a premise consumed by A.13 or A.15.1 reopens that premise and the dependent claims.
The Work's A.6.1 bindings use all six participants. DiagramCoolingLoop : X -> Y is the exact construction; it states claim construction, endpoint-scheme relation, same EntityOfConcern, preserved connection claims, omitted table qualifiers and their recoverability, prohibited strengthening, applicability, topology-inspection use, and return to X.
Only then does this occurrence obtain:
Its transition-description episteme cites the Work, construction, source relations, omitted qualifiers, topology-inspection use, blocked control-timing/work-order inference, and return to X. Rows become directed edges; pairwise lookup becomes topology inspection; each edge links back to its source-table relation. Publication, diagram form, and SVG carrier remain separate. Y is a U.View only if E.17.0 conformance independently obtains.
Correspondence-mediated text-to-table shift
Source prose. In the safety view, CL-2 maintains the required temperature condition during standard operating demand.
Target row.
CM-12 is an additional illustrative correspondence reference, not content recovered from the source quotation. Until its relation kind, endpoints and obtaining basis are supplied, this row does not establish a correspondence-mediated exact construction.
When the receiving use needs an exact construction, identify X, Y and v : X -> Y, establish the same EntityOfConcern and recover the grounds for each relied-on correspondence. A row or record can state or support such a claim; it is distinct from the correspondence occurrence.
Same-concern diagram-to-structured-notation shift
Source diagram. CoolingLoop -> Sensor A; CoolingLoop -> Valve B
Target notation. dependsOn(CoolingLoop, SensorA) and dependsOn(CoolingLoop, ValveB)
This remains RT when the notation carries the same two source connection claims and adds no dependency theory. If dependsOn has stronger semantics than the source arrows, that added claim must be removed or separately established.
Functional-description diagram, table, or screen shift
A source description says that a mixing cell transfers liquid from Tank A through heat exchanger H-2 to reactor R-4, while keeping instrumentation and control claims outside. A target table foregrounds the transfer path. This remains RT only while the same functional slice is represented without adding performed-work order, module structure, evidence, gate passage, or control architecture.
Explanatory diagram order is not physical time or Work order unless the source states that temporal claim. OCR or parsing that merely extracts pixels, text, or layout starts with A.7. If omitting exceptions, confidence bands, or source distinctions makes the target admissible only for a narrower use, use A.6.3.CSC.
Boundary to textual rewrite
A prose note is shortened, reordered, or translated but remains in the same textual regime. Use A.6.3.CR.
Boundary to explanation-facing rendering
A representation is changed mainly to teach or explain an existing face. Use E.17.EFP for that explanatory work. Use RT as well when a change of representation language or reasoning medium independently enables an operation the reader needs.
Boundary to bridge-bearing comparison
A local reliability note about Pump P-2 becomes a comparison claiming operational equivalence with Unit U-7 in another plant. That is not merely representation change. Keep any local representation delta in RT. Under F.9, first resolve the two F.17 SchemeSenseCell values and test that a Bridge obtains; then state the separate C.2.1 bounded-use claim for this equivalence or substitution use.
Boundary to carrier work
A table is exported as CSV and dashboard PNG after the table structure and the reading of its entries have been chosen. The later activity produces the CSV and PNG carriers by formatting, exporting, packaging, or rendering the already chosen representation; it is not another RT merely because the visible form changed.
Boundary to coarsened dashboard view
An incident worksheet carries three causal branches, two confidence bands, and an open ambiguity; a dashboard tile foregrounds only cache-failover evidence. If the tile is useful only under a declared narrower use and explicit return to the worksheet, A.6.3.CSC is primary. Its retained evidence can cue inspection of the cache-failover branch; the tile alone leaves the three-branch causal comparison unresolved.
Boundary to structure-to-narrative rendering
Source structure. Architecture candidate C-2 has module split M, data-custody constraint D, placement constraint P, and unresolved latency versus maintainability trade-off T.
Unsupported narrative. The team first tried to preserve M, then found that D forced P, so C-2 accepts latency residual T to preserve maintainability.
This adds an earlier attempt by the team, a discovery with the claim that D forced P, and a decision resolving the source's still-unresolved trade-off.
Source-faithful reader ordering. To examine C-2, first consider module split M, then data-custody constraint D and placement constraint P; finally consider the unresolved latency-versus-maintainability trade-off T.
The source-faithful alternative orders the selected structures into a reader path; “first”, “then”, and “finally” describe that reading order, not a history of design Work. Apply A.6.3.NAR for ordering, connective account, preservation/loss, use, and source return. Use RT as well if a change of representation language or reasoning medium contributes an operation beyond the ordering of the account.
Guarded decode-mediated rendering
Probe run P-8 is tied to model-state log M-12 and evaluation bundle EV-4. If their source material concerns one independently identified failure episode, a decoded rendering may suggest a cluster corresponding to that episode. Until the decoding/access relation and recoverability evidence support the stronger use, keep the result exploratory and report-only. A readable output may express an episteme, but an exact endpoint still requires its C.2.1 identity; a latent region or feature-cluster label does not supply it.
Bias-Annotation
Conformance and counterexample replay
Ordinary and exact checks
- CC-RT-1 — Useful ordinary entry. A user can recover the source content, choose a representation and a medium that support the next action, make the target, and compare it with the source before supplying exact endpoint identities. Givens, unknowns and a partial construction can support this first result.
- CC-RT-2 — Same concern and right family. The target still concerns the same thing; the intended operation depends on a change of representation language or reasoning medium rather than wording, narrative, explanation, carrier work, retargeting, bridge use, or controlled coarsening.
- CC-RT-3 — Delta and source comparison. Preserved and foregrounded content, rearrangement, loss, recoverability, and apparent links not licensed by the source are visible.
- CC-RT-4 — Use and return. The supported use is clear. Any excluded use or source-return requirement follows §4.1's grounded plausible-reader and consequence test.
- CC-RT-5 — Progressive burden. Detailed factors, semiotic mode, decode evidence, exact identities, Work, publication, evidence, and assurance appear only when each changes use or blocks a likely error.
- CC-RT-6 — Exact endpoints when triggered.
XandYare independently identified C.2.1 epistemes with the same EntityOfConcern and effective schemes. Their model, display, output or carrier labels alone do not establish those identities. - CC-RT-7 — Exact construction.
v : X -> Ystates claim construction, endpoint-scheme relation, same EntityOfConcern, preservation, loss/recovery, prohibited strengthening, applicability, use, and return. - CC-RT-8 — Exact dependencies and neighbors. Correspondence dependencies obtain independently; C.29 representation, E.17.0 View membership, grounding, publication, evidence, assurance, bridge, gate, and receiving Work remain separate.
- CC-RT-9 — Later-specific occurrence only at its trigger. A positive
RepresentationTransitionRelation@Contexthas the A.1.1 model-use structure, preserved concern,X,Y, one episteme describing the effective interpretation rules ofXand one describing those ofY, and Work satisfying §4.1.b. - CC-RT-10 — Occurrence, Work, and description stay distinct. The participant tuple identifies the occurrence; Work and production claims remain separate; the transition-description episteme has the occurrence as EntityOfConcern and its own C.2.1 identity.
- CC-RT-11 — Occurrence identity. Only a changed participant reidentifies the occurrence; repeat Work, evidence, publication, layout, carrier, description edition, or C.29 output does not.
- CC-RT-12 — Reuse is local. When the source or target, delta, dependency, loss, use, evidence, or return changes, reopen only the affected part of the account.
- CC-RT-13 — Construction and subject result. The target representation supports the named operation. For an expression, identify the conventions used to form and interpret it. For a physical or learned representation, establish the correspondence or checked means of reading it that the inference needs. Try the operation when the trial can decide usefulness. A new conclusion keeps its grounds in the subject work that established it.
Counterexample replay
Common Anti-Patterns and How to Avoid Them
Consequences
- Ordinary users can obtain a useful target representation without a six-participant record.
- Representation and reasoning-medium changes become explicit.
- Exact same-EntityOfConcern, scheme, source dependencies, loss, and occurrence identity remain available for consequential use.
- Recoverability and decode dependence become reviewable instead of hiding behind cleaner output.
- Work, View membership, publication, evidence, assurance, bridge, and ontology claims remain separate.
Costs and trade-offs:
- Authors must compare source and target instead of judging only appearance.
- Reliance-facing use adds exact identity and evidence work proportionate to the receiver.
- Some attractive targets remain orientation-only or exploratory because source return or recovery is weak.
Rationale
The representation, its construction and an actual transition answer different questions. Comparing source and target establishes the preservation account needed for a use. An exact v : X -> Y states that construction between identified epistemes. The six-participant relation additionally connects the selected model-use structure, preserved concern, endpoints and scheme descriptions under the actual-Work conditions in §4.1.b. A user who only needs a comparison table can stop at the sufficient ordinary account.
An expression can help obtain a result by keeping relevant parts available for joint inspection or manipulation. This benefit depends on its arrangement, the permitted operations and the user's preparation. Comparing the expression with its source protects the givens while the subject Method develops the construction or argument. E.5.2 keeps the meaning portable when another notation is used; portability leaves the effort and available reasoning operations to be compared.
SoTA-Echoing
Practice question. How can a practitioner change a representation so that it supports the next operation while retaining the source distinctions on which that operation depends?
Selected answer and alternative. Adopt comparison directed by the receiving use: identify the source and target meanings, make the target, inspect the relations the use needs, and expose loss and return. Adapt operative-expression construction to the same comparison. A serious default is conversion followed by a syntax, format-conformance or readability check. That default is sufficient for a carrier-only change when an established semantic contract already covers the required preservation. It is insufficient when the conversion can change the represented claim.
Compare the answers with the same source, target, reader preparation and requested operation. For example, A then (B or C) and (A then B) or C use the same labels and can both be well formed. Checking the represented dependency finds that only the first requires A before either continuation. The comparison in §4.1 asks the reader to inspect that dependency; a format or readability check can leave it unexamined. The selected answer spends effort on the distinction that changes the next action. It accepts that additional comparison cost rather than promising a cheaper conversion. Reuse an applicable semantic-preservation result when one already answers the receiving question.
Preparing an operative expression adds a second useful choice. In §5.1.a, keeping the same segments identifiable as radii and triangle sides supports the geometric argument; in §5.1.b, coordinating syllables with the hand cycle supports the rhythmic construction. A polished copy with those relationships hard to recover can preserve individual labels while remaining unsuitable for the operation. The cases justify trying the intended operation when that trial can decide usefulness, with its subject rules and preparation stated. They do not rank one medium above all others.
How the choice shapes RT. Section 4.1 combines target construction with source comparison and a conditional trial of the intended operation. Section 4.3 states the source and target semantics for a stronger preservation claim; §4.5 exposes loss and decoding assumptions. CC-RT-1 and CC-RT-13 check these moves, and §5 shows their use. This choice rejects syntax, visual appeal or decoder fluency as sufficient evidence of semantic preservation. Technical translation or causal-intervention claims require the semantics and tests appropriate to those claims; the ordinary comparison in §4.1 remains available when the practitioner needs none of them.
Reopen this choice if a target accepted by this procedure loses a dependency, timing relation or uncertainty distinction needed by the declared use; if a changed decoding assumption defeats the claimed recovery; or if an alternative preserves those distinctions and supports the same operation with less preparation or comparison effort. Revisit the affected branch and source comparison.
The domain studies support the named comparisons within their stated tasks and evidence. RT adopts their source-comparison questions and adapts the burden to the receiving use; it leaves the subject's construction, intervention, learning and reliance claims to their own methods.
Relations
- Builds on:
A.6.3andA.6.2for effect-free source-to-receiving construction; C.2.1 for endpoint and description identity; A.1.1 for the later-specific model-use structure; A.13 for actual-performer identification; A.15.1 for independent dated-Work admission; F.6 only for current precise assignment-bound attribution; C.2.7 and E.10.D2 when representation factors or semiotic mode are material. - Operative-expression construction: A.6.3.RT.OE prepares an expression under available conventions so the next operation can be performed. Use its result in the ordinary representation move of :4.1.
- Coordinates with: A.6.3.CR, A.6.3.NAR, A.6.3.CSC, E.17.EFP, E.17.ID.CR, A.6.4, A.7, F.9, B.5.2.0, B.5.2, A.15, E.18, A.20, A.21, A.10, B.3, C.27, A.3.3, C.26, and C.29 at the specific boundaries named above.
- Keeps separate: Work and method; E.17.0 View membership; E.24.PUB publication occurrence, form, carrier, audience, and use; grounding; bridge; evidence; assurance; gate; temporal, dynamics, and transformation-flow claims.
- Boundary: RT contributes preservation, representation/reasoning delta, loss/recovery, use, and return. It does not let a table, diagram, notation, model display, decoded output, publication, form, or carrier substitute for an exact episteme or authorize a stronger claim.
Boundary with quantum-like state-representation shortcuts
Use RT when the primary move is the same-concern shift from one state representation to another: state vector to typed description, fuller model to quantized record, or one notation to another. Start with the ordinary representation note: content to survive, shortcut representation, loss, use, and return.
Add the following only when the shortcut's claim requires it:
- source and receiving schemes and the same EntityOfConcern;
- representation-factor, reasoning-medium, salience, topology, actionability, calibration, or interaction delta that matters;
- decoding relation and recovery evidence;
- causal- or approximate-causal-abstraction mapping when action, intervention, manipulation, or cross-abstraction structure is claimed; and
- the C.26 cue and bounded use when a quantum-like state-representation claim is current.
For a shortcut with the declared QL cue, apply C.26:12b to the receiving use. A conditional comparison or explanation under the same assumptions can retain its sufficient account. Prediction, model adoption or a comparative-performance claim needs the applicable adequacy account; reuse existing support and obtain only the missing contribution. Reuse or formal notation alone does not require a fuller record. Do not describe ordinary compression, low-bit implementation, diagramming, or representation learning as quantum-like without a claim-bearing formal cue.
C.29 mathematical-lens use relation
When RT imports a contested or claim-bearing mathematical lens, RT still carries source/target schemes, same-EntityOfConcern construction, preservation, loss, and return. Cite the applicable C.29 output only for adequacy of that mathematical lens. C.29 neither replaces the RT account nor broadens it into bridge, evidence, or causal authority.
A.6.3.RT:End
Construct an Operative Expression
Type: Method pattern Status: Stable Normativity: Normative
Problem frame
Use this pattern when the available content and notation do not yet give the practitioner an expression with which to perform the needed operation. A diagram contains the right objects but obscures their shared parts. An instruction groups alternatives differently from the work it should guide. A rhythmic phrase has known durations but its entry against a recurring cycle is hard to follow. Two reports may suggest a difficulty before the practitioner has obtained the distinction or question needed to investigate it.
An operative expression is an expression prepared for a specified use: calculating, comparing, inferring, constructing or coordinating an action. Its signs can be written, drawn, spoken or gestural. The selected representation language supplies their formation and interpretation rules; the subject Method supplies the operation to perform.
First useful move. Select one attainable operation, even provisionally, then identify the parts of the content that must be examined together. When the final question is unknown, compare two available cases or separate their observed events; use what this attempt reveals to develop that question. To compare the sides of a constructed triangle, keep each segment recognizable both as a triangle side and as a radius of the circle used to construct it.
The result is a usable expression and the interpretation needed for its next use. A representation change can also need A.6.3.RT's comparison with the source. Any new subject result obtained while using the expression has its own construction or argument.
The examples require their stated geometric, grammatical or rhythmic conventions. Use an existing expression directly when the intended operation is already straightforward. Choose another representation language when the available one cannot express a needed distinction. Designing new notation rules or learning a subject operation remains separate work when either is missing.
Problem
Content can be present while its useful relations remain difficult to recover. A reader may have to remember a shared quantity across distant expressions, infer a grouping that the inscription does not specify, or coordinate a sequence without a common reference.
Making the expression visually tidy can preserve that difficulty. Changing its arrangement can also suggest a relation that the source never supplied: equality through aligned marks, precedence through left-to-right position, or simultaneous action through matching rows.
The task is to prepare the expression so that the needed operation can be carried out under its conventions, while retaining the content and qualifications that the operation uses.
Forces
Solution
Recover the next operation, prepare its participating parts under an available representation language, arrange them around the relation the operation needs, and try that operation. Use its success or failure to keep or repair the expression.
Recover the operation → identify participating parts → expose their relation → check interpretation → perform the operation → retain the usable expression.
Construction and use may alternate. A partial expression can be sufficient to obtain the next part; a finished result need not exist before the expression is made.
Recover the operation and the available content
State what the practitioner should do with the expression and what result would count as useful. “Understand the diagram” is insufficient when the work is to compare two paths, substitute a quantity, identify a shared prerequisite or enter a phrase at the right time.
Recover the givens, constraints, unknowns and partial construction used by that operation. Keep their status visible when it matters: a given equality, a provisional correspondence and a result just derived support different next steps.
Use the subject Method to recover an absent operation or premise. B.5.RC and B.5.RA can help recover a construction or argument. An expression can expose the missing contribution and provide a useful stopping point.
Let a partial expression help obtain the question
Sometimes the available material reveals a difficulty before it supplies a definite question. Start with an attainable operation on that material: place two reports together, arrange events by their stated times, separate an observation from its interpretation, or compare a proposed outcome with what is available. State what this attempt could distinguish. A provisional operation can be selected while the final inquiry remains open.
Try the operation and inspect what its expression lets you see. An unanswered position can expose a missing observation. Two incompatible interpretations can reveal a conflated question. A row that cannot accommodate a second attempt can reveal that the chosen unit was too coarse. Change the arrangement when the available material warrants that change; obtain a missing contribution when rearrangement cannot supply it.
Give the discovered distinction a meaning in the subject work. If "duration" covers receipt-to-result time in one report and equipment occupation in another, separate their endpoints before calculating a difference. The new labels become useful through those definitions and the observed events. A visually convincing pattern alone does not supply a causal explanation.
Use the result to continue, revise the question or stop at the missing basis. B.5.QD and C.40.CD develop the next question when the expression's result changes what must be obtained. Preserve the earlier material that still has a supported interpretation. Replacing the first question does not require rewriting observations to fit the new one.
The construction can stop with a useful distinction or an explicit question. Before a later operation consumes its unresolved part as a fact, supply the missing premise or withhold that dependent result.
Give recurring parts a stable interpretation
Identify which elements must remain recognizable across the expression. Use the selected language's names, positions, types, units, binding rules or temporal references to keep them connected.
When one part belongs to different groupings, retain its identity through the change of grouping. A line can be examined as a circle's radius and then as a triangle's side. A quantity can appear in two equations whose combination depends on it denoting the same value under the same conditions.
When similar marks denote different parts, distinguish them before combining their relations. For a formula with a bound variable and a free variable, preserve the binding scopes when renaming. For a repeated rhythmic sign, its position can distinguish occurrences even when the syllable is unchanged.
Use the amount of labeling the operation needs. Reuse familiar conventions; explain a local convention at its first consequential use.
A table also needs an interpretation for its rows and columns. A row may represent a case or relation with several participants, rather than one object. A column can ask for an object, quantity, condition or judgement. Explain what its entries denote and which combinations are meaningful before relying on alignment.
For example, suppose a local BenchKind admits physical test benches already identified as U.System individuals. A column headed "Bench" asks which of those benches a job used. The entry B7 designates a bench; it is not the name of the domain kind.
BenchKind is a classification distinction, hence an individual of U.Kind under C.3.1, while B7 is classified by that distinction. These upper-kind, domain-kind and particular-object claims answer different questions. A table of kinds could instead contain BenchKind itself; it would need a different column interpretation.
Use those distinctions to catch a mismatch. Placing BenchKind in the job's Bench position would name a classifying distinction when the operation needs the used bench. Placing a duration there supplies a different kind of value. A "30" in an occupation-duration column still needs its unit and interval meaning. Domain membership and the relation to this job require their own grounds; a heading or a successful spreadsheet entry does not establish them.
Retain such annotations where the distinction changes inference, comparison or transfer. Familiar domain wording can be enough for an experienced reader. A computational validator can enforce the declared checks only when its implemented rules match this interpretation.
Arrange the parts around the needed relation
Choose the arrangement from the operation:
An arrangement can reveal several possible analyses. Keep the one needed now available without destroying another analysis required by the next operation. The Euclidean case below uses the same segments in two radius comparisons and then in the triangle.
A useful relation may require an intermediate expression. Expand a shorthand, introduce a temporary name or separate a compound into parts when that makes the operation executable. Keep the rule relating the intermediate form to its source.
Check what the arrangement says
Read the prepared expression using the selected conventions. Compare its participating parts, grouping, ordering and reference with the source content.
Pay attention to a relation conveyed by position, enclosure, adjacency, repetition or timing. State its meaning when the convention does not already supply it. An arrow can mean implication, temporal order, a permitted transition or material flow; use the relation needed by this expression.
When a plausible alternative interpretation would change the operation, test a small case that distinguishes it from the intended reading. In :5.2, the continuation C distinguishes two groupings because one requires A first and the other permits C on its own. The test exposes a change in permitted work that a list of retained letters would miss.
When the expression is used as a replacement for another, A.6.3.RT compares the content carried between them. A coarsened or partial expression may still be useful for the selected operation; retain a way to recover a distinction that a later use needs.
Perform the operation and repair the expression
Use the subject Method to perform the intended operation on the prepared expression. Inspect the transition: which parts were selected, how they were combined and what result followed.
If the operation cannot be followed, locate what is missing. The expression may hide a shared part, omit a scope delimiter or lack a stable reference. Repair that contribution. If the notation lacks a required distinction, return to selection or design of the representation language. If the subject inference or construction lacks a premise or operation, return to that Method.
Keep a new conclusion with the construction or argument that establishes it. A diagram can make the argument possible while the argument still supplies the conclusion's justification. Drawing scale, apparent symmetry or a coincident mark supports a subject claim only through the applicable rules.
An inspectable worked operation shows how the expression is used under the stated conventions. It does not establish another recipient's fluent execution, learning or transfer. When those results or explanation quality are the question, select the corresponding assessment. Use C.2.8 for a recipient's recoverable structure and the relevant Explanation Design or learning Method for the needed change.
Return the expression for its next use
Keep the expression, the conventions that another user needs and the relation to the content from which it was prepared. Include a changed assumption, omission or unresolved interpretation where it can alter the next operation.
The next use can continue the construction, communicate the result or apply it in another situation. Reopen the expression when that use requires a relation it no longer makes available. Stop preparing it when it supports the present operation adequately.
Archetypal Grounding
Keep a segment available in different geometric groupings
The subject task is to construct an equilateral triangle on a nonzero segment AB in the Euclidean plane. The geometric Method permits a circle centered at A through B, another centered at B through A, an intersection C and the joins AC and BC. The subject premises and construction justify those objects, including the intersection.
Prepare a diagram in which the same A, B and C retain their labels and the segments can be examined in these groupings:
Keep the shared segment visible while moving between the first two groupings. AB and BA denote the same undirected segment; their lengths are equal. The subject argument can therefore combine the radius equalities and conclude that the triangle's three sides are equal.
The expression's contribution is the jointly usable arrangement of those parts. Geometry supplies the constructions, radius property and equality reasoning. Measuring the drawing is unnecessary for that argument. If a later construction needs one of these segments extended, retain the point labels and the circle relations that justify its earlier length.
This develops Macbeth's analysis of Euclid I.1.
Preserve a shared prerequisite in a grouped instruction
A working convention uses “then” for ordered performance and “or” for choosing one continuation. The intended content is: perform A, then choose B or C.
Prepare:
A then (B or C).
The parentheses make B or C the second contribution. The allowed completed sequences are A followed by B and A followed by C.
Compare the alternative grouping:
(A then B) or C.
Under the same convention, it permits A followed by B or C on its own. The letters and operation words are unchanged, but the expression no longer requires A before C. A reader following C without A exposes the difference.
Retain the first grouping when A is a common prerequisite. For example, if A establishes the coordinate reference used by either subsequent construction, the second grouping permits a construction without that reference. The repair changes grouping; it requires no new vocabulary or new domain Method.
If the original work instead permits C independently, the second expression is appropriate. The source work determines that choice.
Coordinate a phrase with a recurring hand cycle
Use a learned solkattu convention in which syllables express a rhythmic phrase and hand gestures mark its cycle positions. The cycle has three beats, each containing four pulses, marked by clap, little finger and ring finger. The pulse remains constant.
The content to express is four successive ta ki ṭa groups with four, three, two and one pulses per syllable. Their durations are:
The phrase occupies 30 pulses. The twelve-pulse cycle supplies the recurring reference. To finish at a cycle boundary, rhythmic composition selects a six-pulse preparation: 6 + 30 = 36, or three cycles. The preparation can be voiced as ta ki ṭa with two pulses per syllable.
Prepare the vocal sequence against the continuing hand cycle. The phrase starts six pulses after the cycle origin and ends at the third boundary. Preserve the pulse and duration assignments through the changes of syllable rate. Merely placing four identical syllable groups on a page would leave those assignments unavailable.
The resulting expression coordinates two learned channels: phrase syllables and hand-cycle reference. Arithmetic and rhythmic composition determine the entry and ending. A performer can use that expression to produce the phrase; the utterance and gestures can both represent the content and realize rhythm.
For a performer who needs to locate the cycle boundaries inside this phrase, add these cues to the same pulse reference:
The duration labels retain the whole phrase. These additional cues expose the positions needed for its coordination; use the compact labels alone when that relationship is already available to the performer.
This case adapts Nelson's exercise 7. Reuse the pulse alignment when phrase and cycle change tempo together. Recompute it when a syllable duration in pulses, the cycle's pulse division or the phrase's entry relative to the cycle changes. A performer's fluency remains a question for performance.
Discover which duration an investigation needs
A practitioner receives two reports: job Q41 took 55 minutes, whereas Q42 took 30. The present difficulty is an apparent slowdown. The available messages name receipt and usable-result times; a bench log names occupation intervals. The final explanation is unknown.
Start by placing the reported durations together:
This expression makes a numerical comparison easy but does not establish what the durations measure. Return to the messages and log. They supply the events below:
A row identifies one job; the occupation entry is an interval for that job. All times use the same day's clock and time basis. Aligning those events permits two different calculations. Q41 has 55 minutes from receipt to result, comprising 25 minutes before bench occupation and 30 minutes of occupation. Q42 has 30 minutes to its result and 30 minutes of occupation. The two jobs differ in the former duration but not the latter.
The useful question changes: what accounts for Q41's pre-occupation interval, and is that interval consequential for the receiving work? The observations do not establish its cause. Buying a faster bench would be an unsupported remedy on this evidence. The expression has produced a useful distinction before supplying an explanation.
Now Q43 is received at 13:00. Its first occupation, 13:00–13:30, produces an unusable result; its second, 13:50–14:20, produces the usable result. A single occupation interval per job would lose this construction. Retain one job with its two attempts:
The row now identifies an attempt of a job. Receipt and usable-result events remain associated with Q43 as a whole. Time to the usable result is 80 minutes; total bench occupation is 60; the interval between attempts is 20. The unsuccessful first attempt counts toward occupation even though it did not supply the required result.
The representation changed because the subject history required another distinction. Q41/Q42's earlier observations and calculations remain valid. The practitioner can now ask about repetition, the gap between attempts or the receiving deadline; the corresponding subject inquiry supplies the needed causal or decision grounds.
These small tables are worked expressions for comparing the cases. If the log already provides the interpreted events and calculation, its existing view can be sufficient. A later transfer that separates a row from its job needs the return that recovers that relation. Retain the distinction in B.5.WN when it should support a future line of thought; ending the local investigation does not require a permanent note collection.
Bias-Annotation
This pattern concerns expression construction for a stated operation under available conventions. It assumes that subject operations and notation rules can be obtained. It does not supply the full practice of notation invention, mathematical proof, composition or instruction.
The cases favor expressions whose participating parts can be inspected directly or followed in time. Very large constructions can need abstraction, tooling or several coordinated representations. Reader preparation and the operation govern whether the added structure helps.
Conformance Checklist
- CC-RT.OE-1 - Working operation. The expression is prepared for a stated operation and useful result.
- CC-RT.OE-2 - Source and interpretation. The participating content and selected conventions can be recovered.
- CC-RT.OE-3 - Shared parts and scope. Identity, grouping, binding and references preserve the relations used by the operation.
- CC-RT.OE-4 - Meaning-bearing arrangement. Position, order and timing have the interpretation required by the use.
- CC-RT.OE-5 - Executable use. The intended operation can be followed, or the missing contribution and its consequence are identified.
- CC-RT.OE-6 - Result status. A newly obtained subject result retains its construction or argument.
- CC-RT.OE-7 - Useful return. The expression and necessary qualifications support the next use.
Common Anti-Patterns and How to Avoid Them
Consequences
The practitioner can prepare expressions that make the next operation possible and can repair them when the work exposes a missing relation. A partial construction becomes usable before the whole result is finished.
The gain depends on the selected operation, conventions and preparation. An expression adequate for one step can need revision for a later comparison, extension or recipient.
Architectural Rationale
Reasoning and construction can proceed through expressions. A common part can join relations from different groupings; a delimiter can preserve a permitted operation; a temporal reference can coordinate signs in action. These contributions explain why semantic content and the means of using it belong in the same design question.
A.6.3.RT governs carrying content through a representation change. This Method develops the construction of the usable expression itself, including a first expression for a partial construction under available rules. The subject Method still supplies geometry, arithmetic, rhythmic composition or another operation performed with it. Construction of the expression and production of a subject result may alternate within the same work.
E.5.2 keeps interpretation portable across notations. C.37 helps choose representations for a use, and C.2.8 characterizes recoverable structure for a recipient. The present contribution is how to arrange the content so the selected operation can be performed. Designing notation rules and teaching their use remain further Methods within the notational repertoire.
SoTA-Echoing
Practice question and selected answer. How can available content be made usable in a notation for an operation? Prepare the participating parts, their common relations and a workable reference; try the subject operation and repair the expression.
A comparison for the phrase/cycle use. Consider a performer who knows the syllable-duration and hand-cycle conventions of :5.3 but still needs to locate the cycle boundaries within this phrase. Pulse-labelled syllables and a joint phrase/cycle expression are both available under the same pulse, duration assignments and six-pulse preparation. The compact syllable notation preserves the phrase and its durations; the performer must derive where the cycle boundaries occur. The joint expression adds the three boundary cues developed in :5.3: hold the first group's ki at pulse 12, begin the second group's ṭa at 24 and complete the final syllable as the next cycle begins at 36.
Choose those additional cues when locating that relation is the current difficulty. Their price is three more entries to prepare and follow; their gain is that the needed coordination can be read at its common reference instead of being reconstructed during this use. The compact notation remains sufficient when the performer already coordinates the phrase with the cycle. This exchanges a little preparation and notation for an explicit relation. Once that relation can be followed from the compact notation, the extra entries can be omitted.
Adapt Nelson's comparison of verbal instructions, pulse annotations and joint phrase/tāḷa notation (printed p. 17). It supplies the preparation-sensitive choice, rather than a measured universal improvement. The comparison governs the shared-reference operation in :4.3, the interpretation check in :4.4, the boundary cues in :5.3 and the sufficient-stop rule in :4.6.
Prepared parts and fruitful combination. Danielle Macbeth's “Seeing How It Goes: Paper-and-Pencil Reasoning in Mathematical Practice” (2011, pp. 16-18 and 36-42) analyzes geometric regrouping and preparation of expressions for combining content. Adapt the shared-part and preparation operations in :4.2-4.5. The Euclidean case develops her account of a segment used as a radius and as a triangle side. Her historical-philosophical comparison motivates these operations; it supplies neither a universal notation-design procedure nor a measured effect for the present Method.
Manipulation and interpretation. Catarina Dutilh Novaes, Formal Languages in Logic: A Philosophical and Cognitive Analysis (2012), §§3.2, 5.2 and 6.1, especially pp. 201-203, examines writing used in reasoning and learned symbolic manipulation. Adapt the connection between available rules, recipient preparation and operative use. Her discussion makes abstraction from meaning neither necessary nor sufficient for a cognitive gain. This pattern therefore keeps both rule-governed manipulation and the interpretation required by the next use. The source's accounts of human cognition do not establish equal effects for all readers or AI agents.
Vocal and gestural construction. David P. Nelson, Solkattu Manual: An Introduction to the Rhythmic Language of South Indian Music (2008), printed pp. 17 and 19, supplies the notation comparison above and exercise 7's duration assignments, continuing hand cycle and six-pulse preparation. Adapt their coordination in :5.3; the added boundary cues are derived from those durations. The rhythmic Method and learned conventions supply the subject operation. The source's teaching advice and the constructed alignment give bounded support for this use; performance remains subject to its execution.
Exploratory expressions. The two-column duration comparison in :5.4 preserves the reported numbers but leaves their meanings unresolved. The event table adds source-supported endpoints and permits the waiting/occupation distinction. Its fixed row convention then fails for Q43, whose two attempts require a different unit. Retain useful constraints while revising the one that excludes the relevant history.
David Kirsh's analysis of external representations in problem solving supports making operations possible through external arrangements; Shipman and Marshall's analysis of premature formality supports allowing structure to develop with the work. These are conceptual and historical grounds for the construction, not comparative efficacy evidence for the tables.
The sufficient existing log remains the lower-burden alternative when it already supports the same operation.
These are conceptual and practice-specific sources for the chosen construction, with the common sequence developed by synthesis. Reopen the choice when an available expression supports the same operation with less preparation, a local repair fails because notation rules are inadequate, or use reveals a consequential relation that the current expression hides.
Relations
- A.6.3.RT compares content carried between source and target representations.
- E.5.2 governs recoverable interpretation and portable conceptual meaning; E.5.2.L defines the representation language and distinguishes its conventions from the effective interpretation of a particular episteme.
- B.5.RC and B.5.RA recover a missing construction or argument.
- B.5.RR carries a changed premise through the dependent reasoning.
- B.5.QD and C.40.CD develop the next question when a result changes the inquiry; B.5.WN carries a thought through notes and later occasions when that continuation is needed.
- C.3.1 supplies the distinction between a domain kind, its individuals and the upper-kind claims used in a typed expression.
- C.37 selects representations that jointly support a working use.
- C.2.8 characterizes structure recoverable by a specified recipient under stated conditions.
- A.6.0 and A.6.1 describe reusable language vocabulary, rules or operations when those declarations are needed.
- The applicable subject Method supplies the construction, inference, calculation or performance carried out with the expression.
A.6.3.RT.OE:End
Structure-to-Narrative Rendering
Type: Specialization pattern Status: Stable Normativity: Normative unless marked informative
Problem frame
Use this pattern when selected source structure must become a readable sequential account for a declared reader or listener use. In plain language: turn this structure into a narrative that this reader can follow without hiding what the narrative leaves behind. Typical cases include a scientific mechanism turned into a paper section, an architecture trade-off turned into a team explanation, a conceptual graph turned into a lesson sequence, or an event graph turned into a story draft.
Start from the reader's practical need. Select the source structures that matter for that need, choose a useful order and connective account, draft the narrative, then compare it with the sources for preservation, foregrounding, loss and unsupported additions.
Plain starting vocabulary:
First useful move. Write a useful narrative and give the reader enough source and ordering information to see what it preserves, foregrounds or omits. A compact note can carry that information. Add a source-return condition when omitted structure or a changed question requires it; any excluded downstream use follows F.19:4's full guard test.
What goes wrong if missed. A memorable sequence substitutes for the source structure. Readers retain the story but cannot reconstruct the relations that licensed it, or they treat a connective sentence added for fluency as a source claim.
What this buys. Narrative ordering can make tangled structure usable while selection, sequence, loss and unsupported additions remain inspectable. Any proof, evidence or authority claim still needs its own grounds.
Ordinary use. For low-reliance teaching, orientation, or internal explanation, the useful narrative with the needed source and ordering information is enough. Exact endpoint identities and a formal construction record are not prerequisites for this first result.
Reliance-facing use. Open the exact branch only when the receiving use makes claim-level identity and preservation evidence material: for example, the narrative must travel independently, be cited or disputed, support a new operation of inspection or reasoning through a change of representation, enter generated-output admission under an identity-bearing receiver, support consequential reliance, or satisfy another named receiver that requires exact identity. A public context is a cue to ask which receiving requirement applies; publicness alone is not sufficient.
Then recover source episteme X, receiving narrative episteme Y, and construction n : X -> Y, together with the additional source dependencies, scheme relation, loss, evidence, or assurance required by that receiving use.
Carrier export, generated-output admission, publication, evidence, assurance, ethics, and work authorization are separate questions; apply the corresponding pattern only when that claim is current.
Problem
Projects often need narrative because selected source structures are too tangled for a reader to use directly. A mechanism, architecture, model, evidence set, or event graph may need a beginning, order, tension, action, update point, or learning path before its intended reader can follow it.
Without A.6.3.NAR:
- narrative is treated as a final style-polishing step;
- narrative is treated as mere lossy summary even when sequence-making is the main representational move;
- selected structure, ordering decisions, event models, and lost relations disappear behind fluent prose;
- engagement is allowed to raise confidence, authority, ethical permission, or policy force without the current evidence relation, assurance result, ethical basis, or policy basis required for that stronger claim;
- generated narrative output is trusted because it is coherent or dramatic;
- exact identity and assurance fields are demanded before an ordinary reader-useful narrative exists, making the pattern needlessly hard to enter.
Forces
Solution
Produce the ordinary useful result first:
- Name the reader or listener and the practical use: what must become understandable, reconstructible, predictable, or discussable.
- Point to the source material and select only the structures needed for that use. Say why those structures matter.
- State temporal posture or mediation only when it changes the ordering or the trust boundary.
- Choose an ordering and connective account: event, causal, discovery, didactic, tension, traversal, or another explicit rule.
- Draft the smallest narrative that lets the reader follow that path. For technical prose, use F.19 for plain-language repair.
- Compare the draft back to the source material. Record what it preserves and foregrounds, what it omits or weakens, and which connective or interpretive statements are not source claims.
- State the supported narrative use. When omitted structure or a changed question requires return, identify the source to restore or the stronger claim-specific question and its governing pattern. Any excluded use follows F.19:4's full guard test.
Use this compact note when it helps make the source-to-narrative comparison inspectable; otherwise keep the needed information in the narrative and its source references. Include only entries that affect use or block a locally grounded overread:
Exact construction branch
Open this branch when the identified receiving use depends on exact claim identity and preservation, under §1. Citation, distribution or generated status is a cue to examine that need, not a requirement by itself. Apply E.24.PUB separately when a publication occurrence, form, carrier, audience or bounded publication use matters.
Then establish the A.6.3 construction n : X -> Y:
- identify source episteme
Xand receiving narrative epistemeYindependently under C.2.1 by claim content, EntityOfConcern, and effective interpretation rules (ReferenceScheme); - require the same EntityOfConcern; a narrative about another concern requires A.6.4;
- state how claims in
Xand any named additional source epistemes construct the sequential claim content ofY; - state the endpoint scheme relation, ordering rule, preserved and foregrounded content, admitted loss, prohibited strengthening, applicability, and return; and
- cite every correspondence relation on which the construction depends and test it under its direct predicate.
Recover X as the source episteme whose claim content and EntityOfConcern supply the narrative source, and recover Y as the receiving narrative episteme. Treat input models and publications according to their source claims and keep forms and carriers in their direct roles. If the receiving item lacks recoverable claim content, an EntityOfConcern, or an effective reference scheme, keep it as candidate prose or a carrier and stop before asserting exact NAR.
When the exact branch is needed, use this fuller local record if the receiving use needs this form; otherwise retain the required construction information in the account already being used:
selectedSourceStructureRefs identifies the selected structures. A PatternID mentioned in sourceStructureSelectionRationale or surrounding prose only locates the content used to recognize or test them; it is not another structure reference. Include sourceStructureDefinitionClaimEpistemeRefs or sourceStructureConstraintClaimEpistemeRefs only when the identity of one or more definition or constraint claims changes reconstruction, comparison, dispute, or reliance. Both lists may be present and each resolves only to claim-bearing C.2.1 epistemes of the named kind.
Resolve X and Y to their C.2.1 identities and use this record only for the construction account. When production history matters, recover each performer's A.13 core and independently admit dated narrative-construction Work under A.15.1; add F.6 afterward only when precise assignment-bound attribution is current.
Include readerInterestOrUseHypothesis only when an assumption about the reader affects selection or ordering; retain it as a hypothesis. Include each optional System, system-role-kind, or assignment reference only when its referent and direct claim obtain independently.
Connect source epistemes, parameters, methods, tools, and Y through direct relations or A.6.1 bindings. If the Work first constitutes Y and that inception claim matters, use A.15.PROD to test that separate local claim.
epiplexityOrStructuralInformationRef? refers to a qualified C.2.8 comparison or estimate when the narrative use depends on structural amount. Identify the receiving narrative episteme, its expression, the observer and relevant preparation, access and budget. A formal epiplexity or other mathematical estimate uses the C.29 model-to-characteristic correspondence; a domain estimate retains its scale and evaluation conditions. The field remains optional for the ordinary narrative and note.
nonAdmissibleDownstreamUse?, also named groundedNonAdmissibleDownstreamUse?, is one optional explanatory field governed by F.19:4's plausible-reader test.
Publication remains separate. E.24.PUB identifies any occurrence that makes selected episteme Y available to an audience and bounded use through one independently identified expression and the state or realization of its independently identified carrier. Any selected reusable publication form constrains that expression separately. C.2.1 identifies Y, A.6.3 governs the construction n, and E.17.0 independently decides whether Y has U.View membership.
Use this optional unfolding block when an independently identified selected structure must be carried into a reader-facing sequence with explicit loss and return:
structureBeingRenderedRef, narrativeOrderingStructureRef, and any receiving narrative episteme occupy different positions. Use unfoldingStructureBeingRenderedRef only when the source structure is itself a constraint-governed unfolding structure. Apply A.22.CGUS identity and membership tests to the source or narrative-ordering structure whose CGUS membership is claimed. The block records references to those structures; ordinary NAR does not require such a qualification. returnCondition names the same value as narrativeStructureUseReturnCondition, not a second return rule.
Ordinary and reliance-facing cases
An internal explanation, teaching example, orientation narrative, or early team account normally closes with the narrative and its source comparison. A compact note is useful when it makes their relation inspectable.
Move progressively. Add temporal posture, event-model support, mediation, viewpoint, engagement, or worker history only when each distinction changes the use or blocks a likely error. Open the exact construction branch only at its declared trigger. A reliance-facing case then carries forward the ordinary narrative and its source comparison, adding only the exact account required by the receiving use.
Exact same-EntityOfConcern and correspondence-mediated profiles
This subsection applies only after the exact branch is open. Exact NAR is same-EntityOfConcern: X and Y designate the same concern even when their effective reference schemes differ. Similar content or a declared correspondence does not relax this rule. If the receiving narrative concerns another entity, use A.6.4 and state the retargeting relation there.
Use the direct-source-claims profile when n constructs Y from claims in X and fixed configuration. A situation, event stream, domain model, proof-dependency field, evidence set, fictional canon, or source pack can contribute only through claims in X or through named additional source epistemes and relation occurrences. The raw object, graph, set, or pack is not the source endpoint.
Use the correspondence-mediated profile when n depends on relations among X, additional source epistemes or their designated structures. Recover each needed relation under its defining predicate and identify the source assertion used by the construction. That assertion may remain within a broader source episteme; a separate relation-description episteme is needed only when the use depends on it. C.34 applies only when its correspondence test fits the architecture use.
Direct and architecture-mediated routes
In the direct route, the source episteme states or designates the source situation, event structure, proof dependencies, canon claims, or source-pack claims that n orders. Viewpoint discipline may help, but X, Y, and n remain the central objects.
In the architecture-mediated route, one architecture-description, architecture-view, decision, candidate-structure, or telemetry episteme participates as X or as a named additional source episteme. Independently recover any selected A.22 structures, world-side holons, decisions, relations, or telemetry occurrences that its claims designate. The return chain is Y to source episteme(s), then through their designation relations to structures or occurrences when those are current.
Keep every selection, coarsening, abstraction, omission, ordering, and correspondence explicit by using the applicable C.32.*, C.33, C.34, architecture-description, or decision test. NAR defines only n's source-to-narrative construction, preservation, loss, and return boundary.
In either route, identify temporal posture when it affects interpretation. A historical reconstruction, live commentary, prospective project narrative and fictional continuation have different source claims, uncertainty and ordering conditions. A dated narrative-construction Work claim remains separately governed by A.13 and A.15.1, with F.6 only for precise assignment-bound attribution.
Ordering rationale
The ordering rationale is the structure-to-sequence rule.
Common ordering rationales:
If the source material only changes carrier form, file format, export layout, OCR extraction, or byte order, this pattern is not open. Carrier serialization alone is not narrative rendering.
Event model, viewpoint, and agency
If the narrative asks readers to understand events, actions, mechanisms, or change, state enough event-model support to preserve the relevant happening or mechanism type, participants, causal or dependency links, update points, and what the reader is expected to predict or revise.
If viewpoint, narrator, focalized object, protagonist, or agency choices affect understanding, keep their detailed vocabulary in the narrative domain. In FPF Core the reusable check is: which selected source structure does the viewpoint foreground, hide, or weaken for this declared use? Invoke another FPF pattern only for a specific stronger claim that pattern defines.
Engagement, ethics, and assurance boundary
Engagement is a use claim. When engagement or motivation matters, state the intended effect, the source structure that may not be distorted for that effect, the affected reader or decision context, and the return condition. Use F.19:4's plausible-reader test for any optional explanatory guard.
Use D.1 for ethical value-frame entry, D.2 through D.4 for multilevel conflict and decision use, D.5 for bias, human impact, or ethical assurance, A.10 for evidence, and B.3 for assurance. Apply only the patterns needed by the current claim.
Reopen, lower, and return rule
An ordinary narrative remains fit while its source material, selected structures, reader use, ordering/connective account, loss statement, and return still match the actual use. An exact case additionally depends on the current identities of X and Y, the construction n, its source relations, and every qualification used by the receiving claim. Repair the smallest affected account and its dependent claims.
Archetypal Grounding
Tell: NAR turns selected source structure into a reader-useful sequence while keeping ordering, loss, unsupported strengthening, and source return visible. It is not a general story-writing pattern.
Scientific mechanism narrative
A chemistry paper has calculations, candidate mechanisms, failed synthesis attempts and unresolved tension between theory and experiment. If the sources establish the discovery history, an internal explanation can follow it: failed attempts, structural clue, revised mechanism, new experiment, remaining uncertainty. Its note identifies the preserved claims and deferred calculations; any connective added to explain the sequence is distinguished from a source assertion. A mechanism-proof question returns to the calculations and experiment record.
When a receiving use needs exact preservation of this account, identify source episteme ChemistryMechanism-X and narrative episteme ChemistryDiscovery-Y about the same reaction case. DiscoveryNarrativization : X -> Y states the selection, scheme relation, discovery order, preserved and lost claims, any grounded proof-use exclusion, and source return. The calculation files express source content; the paper form and carrier express the narrative. Their file labels alone identify neither episteme.
Architecture trade-off narrative
An architecture team needs to explain a candidate selection. It can order the account by the binding constraint, compared alternatives, decision and remaining trade-off. Preserve the decision's stated basis rather than inventing the sequence by which the team discovered it.
Source fixture. For project system S, data must be processed at Plant P. Under the same workload W, candidate C1 processes at P with a measured median latency of 40 ms; C2 processes at regional site R outside P with a measured median latency of 30 ms. Decision D selects C1 because the placement constraint is mandatory. D does not authorize implementation.
Narrative. Decision D selects C1 because it processes S's data at Plant P, as the mandatory placement constraint requires. C2 processes at regional site R outside P, which would violate the mandatory placement constraint. Under W, its measured median latency was 30 ms, 10 ms lower than C1's 40 ms. D does not authorize implementation.
Comparison. The narrative foregrounds the constraint before the performance trade-off. It preserves both candidates, sites, workload, measured characteristic and decision basis; the 10 ms difference follows from the two comparable medians. It asserts no discovery history or actual implementation. This short fixture omits no source claim. For a changed workload or placement rule, return to the measurement and decision basis before carrying the selection forward.
When the receiver needs exact claim identity, ArchitectureTradeoff-X and ArchitectureRationale-Y concern the same project system, and ArchitectureRationaleNarrativization : X -> Y states the construction and return. Independently identified A.22 candidate structures are designated by the source claims. The posture is prospective during choice and retrospective when recounting the decision; publication, decision, synthesis and performed Work remain separate.
Architecture narrative repair after source change
Later, a rejected candidate gains a new measurement basis and a placement constraint changes. The old story remains coherent but no longer preserves the live candidate set. Lower it to historical orientation, update the selected structures and ordering, state the changed loss and residual, and restore return to the current architecture description or decision material. In an exact case, reidentify only source epistemes whose C.2.1 identity changed, and restate the affected construction n under A.6.3.
C.33 carries captured and lost architecture-relevant structures: preserve the old rejected-candidate relation as history, capture the new candidate-set relation, and mark the obsolete measurement basis lost for current decision use. C.34 carries only a correspondence that remains. Implementation or decision use stays non-admissible until the architecture claim, decision result, or synthesis result and any required use relation are current.
Live unfolding event narrative
A commentator narrates a football match while it unfolds. The ordinary narrative selects score state, possession changes, tactical shape, player roles and positions, momentum, and uncertainty, then uses event and tension order for live orientation. Here player roles is ordinary football language for tactical contribution and behaviour—such as pressing, covering, marking, playmaking, or providing width—not an asserted FPF system-role kind or assignment. The narrative does not turn provisional interpretation into settled event evidence.
Later analysis, statistics, rule disputes, injuries or official-result use returns to the event record and official sources. When replay or dispute depends on exact claim identity, identify event-record episteme MatchState-X, commentary episteme LiveNarrative-Y and their construction LiveNarrativization. The match is the concern, source claims describe its events, and audio expresses the narrative through its form and carrier.
FPF seminar-route boundary
A team orders selected FPF claims for learners: EntityOfConcern discipline, problem frames, pattern use, relation records, source return, framework authoring, and improvement loops. The first result is a teachable route whose note records prerequisite order, deferred detail, reconstruction tasks, and return to exact FPF passages.
A separate E.24.PUB occurrence may make a selected narrative episteme available through a teaching form and carrier; publication neither constitutes the narrative episteme nor establishes the NAR construction.
Franchise-continuation storycraft boundary
A storycraft team develops a proposed continuation using canon constraints, premise, theme, character agency, causal plot structure, viewpoint and stakes. The new events come from that story construction. NAR then orders the proposed events and relevant canon claims into a readable account, making selection, foregrounding, loss and source return explicit.
For an exact same-entity continuity account, identify the source episteme describing the proposed continuation and any additional canon-source epistemes, then identify ContinuationNarrative-Y about that same continuation. The construction states how its assertions follow from those sources. Canon alone does not supply newly invented events. Canon classification, story generation, rights, publication and narrative-quality evaluation remain separately governed. G.2 applies to SoTA source-pack synthesis and C.35 to generated results intended to inform architecturing, only when those uses are current.
Homotopy-theory explanation boundary
A teacher turns graph-heavy mathematical material into a didactic sequence of definitions, dependencies, examples, counterexamples, theorem prerequisites, and proof-status boundaries. The ordinary note records which structures a learner can reconstruct, which proof details or generalizations are deferred, and when to return to formal statements.
When a mathematical use needs exact preservation, identify HomotopySource-X and HomotopyNarrative-Y about the same mathematical EntityOfConcern and state the construction, ordering and loss. Mathematical-lens, proof, source-use, publication and teaching-evaluation claims retain their applicable tests.
Automated event-graph narrative
An LLM or NLG system uses source claims designating an event graph, agent goals, constraints, and a domain schema, then performs generation Work and proposes the resulting story-scene carrier. The first inspection compares the proposed sequence with the selected event relations, marks preserved constraints, omissions, and hallucinated connective claims, and limits use to candidate review.
Use C.35 when the generated result is intended to inform architecturing; it tests that result's next architecture use. If reliance-facing use later opens exact NAR, independently identify EventPlan-X and StoryScene-Y, then state EventNarrativization : EventPlan-X -> StoryScene-Y, the additional source dependencies, loss, prohibited strengthening, and return. The graph and schema are not X; the system's generation Work, evidence, assurance, and publication remain separate.
Bias-Annotation
Conformance and counterexample replay
Counterexample replay:
Common Anti-Patterns and How to Avoid Them
Consequences
Positive consequences:
- A reader receives a usable sequence before formal identity work is required.
- Selection, ordering, connective additions, loss, and return remain inspectable.
- Exact episteme identity and source dependencies remain available when the receiving claim needs them.
- Human-authored and generated narratives face the same source-comparison boundary; their production histories remain separate from the narrative relation.
- Domain narrative conventions can be used without confusing them with FPF Core kinds.
Costs and trade-offs:
- Authors must compare the narrative with the source rather than judging it by fluency alone.
- Reliance-facing narratives require exact identity and preservation work proportionate to the receiver's use.
- If missing selected structure or source return makes the stated use unsupported, narrow the use to one whose requirements still hold, or keep the narrative as a draft.
- Evidence, assurance, ethics or policy claims add their own required work.
Rationale
Narrative makes non-linear structure usable by giving readers a path through events, mechanisms, evidence, options, architecture decisions, or prerequisites. That strength is also the risk: a well-formed story can make a source look simpler, more certain, more complete, or more permissible than it is.
The narrow reusable move is therefore reader-first and progressive. Choose structure for a use, order it, connect it, draft the account, and expose loss and return. Exact n : X -> Y is the stronger description of that move when a receiving use needs claim-level identity; it is not the entrance fee for every explanation.
SoTA-Echoing
Relations
- Specializes:
A.6.3for structure-to-sequence narrative construction. The ordinary entry exposes selection, ordering, loss, use, and return; the triggered exact branch states same-EntityOfConcernn : X -> Yand any correspondence dependencies. - Coordinates with:
A.6.3.CRfor same-regime textual re-expression,A.6.3.RTwhen the receiving operation depends on a representation transition,A.6.3.CSCfor controlled semantic coarsening,A.6.4for changed EntityOfConcern, andE.17.EFPfor explanation-use adequacy. - Uses when current:
C.2.8for extractable structural amount, the applicable domain evaluation for its local scale,C.29for a mathematical estimate's correspondence,C.33for captured and lost architecture-relevant structure, andC.34for a correspondence claim needed by architecture work. - Coordinates with:
A.22.CGUSfor its ordinary branch when continuation conditions need clarification. For a claimed source or narrative-ordering CGUS, establish that structure's identity and membership; the optional unfolding block records references to that structure. - Coordinates with:
C.35for generated results entering architecture work,G.2for its SoTA harvesting/synthesis claims,E.6andE.11for learning order and first-entry publication questions, andE.17for publication-form use,E.17.0for viewpoint conformance,E.17.AUDfor audience, andE.24.PUBfor publication questions. - Uses when current:
G.11for source-return currentness;D.1–D.5,A.10, andB.3for the ethics, evidence, or assurance claims they define. - Uses when current:
F.19for plain language in technical narrative and for the plausible-reader test of an optional explanatory guard. - Boundary: NAR defines the structure-to-sequence construction, preservation, loss, and return boundary.
A.6.3.NAR:End
EntityOfConcern Retargeting: Judge a Bounded Use Across Different Entities
Status: Stable Type: Definitional pattern
One-line summary. Use EntityOfConcern retargeting to classify an arrow between epistemes about different entities. A claimed receiving use needs a separate bounded-use assertion; a current-case judgement compares that assertion with the relevant facts.
Retargeting in plain terms. The two epistemes concern different things. One named receiving use is admitted only when facts establish the stated invariant and show that the visible loss remains acceptable under named conditions.
Use this when. Use this pattern only after C.2.1 identifies the two epistemes and shows that their EntitiesOfConcern differ. A changed model kind, ontology frame, predicate set, coordinate system, or notation is a cue to repeat that identity test, not proof of retargeting.
What goes wrong if missed. A changed EntityOfConcern is treated as “the same thing in another form”, so claims, evidence, gate results, work authority, or currentness are carried forward without their own direct predicates or current results. The opposite error is to demand a semantic Bridge or reversible mapping when the case needs neither.
First useful move. Identify r by its endpoint epistemes, arrow rule or designator, and the selected formal substrate's equivalence criterion. Name both EntitiesOfConcern. For a claimed receiving use, state the invariant, visible loss, named use and conditions in a separate bounded-use assertion q. When judging a current case, compare its facts with q.
What this buys. The reader can decide one receiving use from the bounded-use assertion q and current facts; source-claim survival, performed Work, and EntityOfConcern identity retain their separate bases.
Not this pattern when. If the EntityOfConcern is preserved, use the pattern for the change that occurred: A.6.3.CR for faithful restatement, including translation, A.6.3.RT when a change of representation language or reasoning medium enables the intended operation, A.6.3.CSC for controlled coarsening, or E.17.EFP for explanation mode. A normal time-to-frequency description of the same signal is an A.6.3.RT case. Use C.29 when a separate mathematical representation or transfer question remains; bring its correspondence and limits back to that representation change. Use F.9 only for a separately claimed Bridge between two local senses. Keep every other independently current claim under its direct pattern; the Relations section names the main neighboring owners once.
Problem frame
Several familiar moves can hide a change of EntityOfConcern, but none proves that change merely by its name or notation:
- Physical cabinet and selected functional structure. An episteme about cabinet
Cab-7and one about selected functionalU.StructureRoute-Aconcern different entities when C.2.1 identifies them independently. A behavior-test result can supply facts for a bounded retargeting judgement. The expressionRealises(Cab-7, Route-A)contributes only if its own relation and obtaining conditions are established; §5 shows a case whose judgement needs no such relation. - Signal and spectrum. The ordinary Fourier case often concerns one signal in two representations. Use A.6.3.RT when the EntityOfConcern is preserved. Add C.29 only when the needed mathematical correspondence or its limits remain unsettled. A.6.4 opens only if the receiving episteme concerns a separately identified spectrum object and the use explains why that object, rather than the original signal under another representation, is current.
- Observations and fitted model. A dataset and a learned model can be different entities. An affirmative q may state a predictive invariant and name a prediction use; the fit and held-out test outcomes then supply current-case facts for the separate judgement. Individual observations and unmodelled distinctions remain visible losses. Model fitting is a separate activity.
For a case used positively, the local arrow r relates two epistemes with different EntitiesOfConcern, q affirmatively states the bounded-use proposition, and the case facts satisfy it. Any claimed operation application or Work is identified separately under its own conditions.
A domain relation, mathematical transform, or F.9 Bridge contributes only the claim established by its own governor. C.2.1 independently identifies the two EntitiesOfConcern.
Problem
Without this discipline:
- Notation decides ontology. A changed coordinate system, mathematical domain, model kind, or predicate vocabulary is treated as proof that the EntityOfConcern changed.
- Retargeting is confused with viewing. A move from one independently identified entity to another is called another view, so its loss and receiving-use boundary disappear.
- The invariant and loss remain rhetoric. Phrases such as “energy is preserved” or “the model summarizes the data” do not say which claim survives, which distinctions disappear, or which use remains sound.
- A mapping apparatus replaces the case. A generic kind bridge, score, diagram, or reversible optic is demanded even when the endpoints, q, and current facts already let the reader judge the named use.
- Arrow, claim, and execution collapse. A mathematical arrow is treated as if it granted a use, performed an operation, or produced an episteme.
- A transformation-flow position is mistaken for a use judgement. Placing r and q in E.18 does not establish the invariant or acceptable loss for the receiving use.
- Neighboring changes disappear into one label. Grounding, representation, scope, operating conditions, viewpoint selection, publication, operation application, and performed Work are folded into retargeting instead of being identified only when they occur.
Forces
- Different subject versus unsupported claim. The endpoint EntityOfConcern may change while every receiving assertion remains subject to A.6.2 P2. A separate q states which invariant and loss support one receiving use.
- Useful loss versus hidden loss. Retargeting may discard information, but the loss boundary and the use that tolerates it must be visible.
- Direct case versus universal apparatus. Use a domain relation, mathematical map, semantic Bridge, or diagram as current-case basis only when its own governor establishes the needed claim. Identify r from its endpoints, arrow rule or designator, and formal equivalence; judge q separately from current facts.
- Composition versus accidental equivalence. Compatible retargetings may compose. Equality of two evaluation routes, reversibility, idempotency, or semantic correspondence requires its own stated conditions; it does not follow from the word retargeting.
- Modularity. The retargeting arrow relates two epistemes, q states one bounded-use proposition, and a separate current-case judgement says whether the facts satisfy it, fail it, or leave it undecidable. Grounding, publication, Work, evidence, assurance, gate, flow structure, and cross-local-sense correspondence remain separate.
Solution — separate the arrow, use claim, current-case judgement, and any application
Informal definition
Definition. An EntityOfConcern-retargeting morphism is a local
EpMorphism r : X -> Ywhose endpoint epistemes concern different entities. A separate bounded-use assertion q affirms or denies that one declared invariant makes the stated loss acceptable for one named receiving use under named conditions.
EntityOfConcernRetargetingMorphism is a local mathematical subtype in the selected formal substrate, not a durable kind. This pattern defines that subtype and the practical discipline for claims about its use.
Keep four things distinct:
- The arrow
r. Within the selected formal substrate, its domain X, codomain Y, arrow rule or designator, and declared formal equivalence identify it. The two endpoint epistemes and their different EntitiesOfConcern are recoverable. A changed use claim does not create another arrow. - The bounded-use assertion
q. This is a C.2.1 episteme about arrow r. Its ClaimGraph states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. Its complete claim content, EntityOfConcern, and effective ReferenceScheme identify q. A citation inside q can point to case facts; it does not decide whether those facts satisfy the proposition. - The current-case judgement. Compare the current facts with q's conditions and proposition, and report
satisfies,fails, orcannot decide. That result is not q's polarity and does not reidentify q or r. Use A.20 only when the case raises an internal-constraint check, A.10 only for a current evidence-use claim, and B.3 only for a current assurance claim or its material-reliance threshold. Otherwise the named rule and direct case facts are enough. - Any application occurrence. If a system computes, authors, or otherwise produces or changes an episteme by using the declared operation, identify that A.6.1 application, its argument and result bindings, the performing system, and any Work separately. The mathematical statement
r : X -> Yalone names no occurrence.
For a current-case judgement of a receiving-use assertion, ask:
These answers may be one short paragraph; they require no new record form or assurance package. Add a separately governed commitment change, neighboring claim, or durable result only when it changes q, the judgement, or the receiving action; ER-1 and CC-A.6.4-5 name the values to inspect. Add an F.9 Bridge only when the same case separately claims a semantic relation between two F.17 local senses.
When the judgement of an affirmative q is fails, retain q as the stated proposition but do not admit that case. When a current-case judgement is cannot decide, keep the source material, name the missing fact and what would reopen the question, and stop. Failure of an affirmative q does not by itself establish a negative q; a negative assertion needs its own claim content and case basis.
Formal declaration and object boundaries
When a receiving use needs a reusable formal declaration, an A.6.0 U.Signature(profile=FormalSubstrate) episteme can declare the local subtype EntityOfConcernRetargetingMorphism. The declaration remains distinct from the subtype, an arrow, a use claim and an application.
X and Y are C.2.1 epistemes. r : X -> Y is one local mathematical arrow in the selected formal substrate. Its identity uses the endpoints, arrow rule or designator, and the selected substrate's equivalence criterion; the endpoints alone do not identify it. The declaration states which parts of X and Y's claim content, EntityOfConcern, and effective ReferenceScheme remain the same or differ. If r's rule reads a representation or another separately obtaining relation, it names the occurrence and compares endpoint facts without changing that occurrence.
A.6.4 reuses the one A.6.2 formal model: category Ep, endpoint-only thin category EoCBase, dom, cod, identities, compose, and the declared mapping α. For retargeting arrow r, α(r)=u_{α(X),α(Y)} is the unique formal endpoint arrow between the independently different EntitiesOfConcern. It records only that endpoint difference and forgets r's arrow rule; it is not an independently declared domain or world-side relation. The local classification function entityOfConcernChangeMode returns retarget for r and records the same endpoint difference. It classifies only the endpoint-change mode; it adds no domain-function evaluation or second retargeting calculus.
The bounded-use assertion q, current-case judgement, and any application occurrence remain separate. Add A.6.5 SlotSpecs only inside a reusable direct-relation declaration; they are not fields of r, X, Y, or q.
Laws (ER-0...ER-6)
These laws refine A.6.2 for the local retargeting subtype. Every assertion in Y remains subject to the parent P2 support condition, including assertions outside the invariant named by q. The laws do not assert durable U-kind membership.
ER-0 - Arrow class and endpoint basis.
An arrow r : X -> Y is in the local retargeting subtype only when X and Y are C.2.1 epistemes, entityOfConcernChangeMode(r)=retarget, and their EntitiesOfConcern differ. A shared label, kind name, diagram, implementation, use claim, or F.9 card identifies neither r nor its endpoints by itself.
ER-1 - Arrow identity and neighboring facts.
- The selected formal substrate supplies r's arrow rule or designator and equivalence criterion; same endpoints alone do not identify an arrow.
- The declaration states which parts of X and Y's claim content, EntityOfConcern, and effective ReferenceScheme remain the same or differ. It names any separately obtaining representation or other relation that r's rule reads and the endpoint facts compared; r does not change that occurrence.
- Grounding, scope, operating condition, representation, and any viewpoint selected for a describing use remain separate values or relations.
- A different scheme, scope, context, or plane does not by itself create an F.9 Bridge. Cite F.9 only for a claimed direct relation between two F.17 local senses.
ER-2 - Separate use proposition and current-case judgement.
For each named receiving use, one separate C.2.1 assertion q states an affirmative or negative proposition about whether the source claims preserve the declared invariant in the receiving episteme and whether the visible loss is acceptable under the named conditions. The same r may have different q assertions for different uses without changing arrow identity.
A separate current-case judgement applies q to the current facts and returns satisfies, fails, or cannot decide. A direct fact, proof, test, or obtaining relation can enter the ordinary case basis through its own governor. Open A.20 only for an internal-constraint claim, A.10 only for evidence use, and B.3 only for assurance or its material-reliance threshold. Each retains its own identity; q's polarity stays as written, and cannot decide is reopened when its named missing fact becomes available.
ER-3 - Composition and separately claimed final use.
Two retargeting arrows with an exact matching middle episteme compose in the parent Ep category; A.6.2 category closure supplies the composite and requires it to satisfy the parent laws. The composite remains in the A.6.4 retargeting subtype only when its final endpoint EntitiesOfConcern differ and its other subtype laws hold. A round trip whose final endpoints concern the same exact entity is a preserve-mode EFEM arrow in the parent class, not an A.6.4 retargeting arrow.
A claim that an admitted composite is suitable for a final use is another q: it states the final source and receiving entities, preserved invariant, accumulated loss, receiving use, conditions, and polarity. A separate judgement applies that proposition to the final current case.
No universal SquareLaw follows. A consumer that claims two evaluation routes equivalent, or relies on a correspondence between epistemes, identifies the routes or correspondence, comparison rule, tolerated difference, and witness under the direct governor of that claim.
ER-4 - Determinism and repeat boundary.
Functionality, reversibility or equivalence of routes requires the selected formal substrate's domain, equality or equivalence and applicable witness. A retargeting arrow r : X -> Y has different endpoint EntitiesOfConcern, hence X ≠ Y; it is not self-composable, so compose(r,r) cannot express an idempotence law for that arrow. A repeat property of a construction operation is a separate claim about its rule and inputs. A.6.3:4.7 illustrates the first-arrow/next-arrow form when that repeat returns the same receiving episteme. Ambient time, randomness, solver state or external services must be accounted for when they can change the operation's result.
ER-5 - Applicability and optional semantic-Bridge branch.
The formal declaration states admissible endpoint families and material mathematical conditions. Each q separately states the invariant, loss boundary, receiving use, case conditions, and affirmative or negative polarity; the current-case judgement states whether the facts satisfy it. F.9 is triggered only for a separately claimed relation between two local senses. Optional CL summarizes evidence about that Bridge; it is neither a retargeting threshold nor a participant in r or q.
A named mapping or relation without a governing definition supplies no additional claim. If the receiving use needs that claim, identify its direct governor or leave the missing-governor question unresolved.
ER-6 - Separate application, Work, and resulting episteme.
An arrow that preserves the EntityOfConcern remains in A.6.2 preserve mode. A.6.3 additionally requires its viewing construction and laws. Describe measuring, fitting, translating or authoring in ordinary practitioner terms. Identify an A.6.1 application and its bindings when a declared operation is current. A dated Work claim follows A.13 and independent A.15.1 admission, with F.6 only for precise assignment-bound attribution. Identify any resulting episteme under C.2.1; the mathematical arrow relates endpoints without performing that activity.
Boundary with representation, explanation, transformation-flow structure, and neighboring claims
A.6.4 is triggered only by an independently established change of EntityOfConcern. A changed kind, ontology frame, predicate set, mathematical domain, or notation is a recognition cue that reopens the C.2.1 identity test; none decides the branch by itself.
Boundary rules:
- If the EntityOfConcern stays the same, use
A.6.3.RTwhen the intended operation depends on changing the representation language or reasoning medium. - if the EntityOfConcern is preserved and the main change is explanation mode, explanatory stance, or explanation-facing publication, use
E.17.EFP; - if the same case also asserts a semantic relation between two local senses from different semantic contexts, test
F.9separately and cite a Bridge only when its predicate obtains; useF.9.1only for an optional stance note about that already constituted use claim. A domain correspondence, mathematical rule, or direct case fact enters the current-case basis only through the claim established by its governor; that claim alone does not open F.9; - if the receiving use requires a mapping, correspondence or route-equivalence claim whose direct governor is missing, resolve that missing basis before relying on the claim;
- if the EntityOfConcern is preserved and the receiving item is useful only under narrower declared use with visible loss and source-bearing reopen, use
A.6.3.CSC; - if a
StructuralReinterpretation,PathSliceId,CrossingRef, orDecisionLogRefis present, useE.18,A.20, orA.21for graph, path, constraint, and gate relations. Those references do not prove semantic continuity or retargeting admissibility by themselves; - for decoded or latent output, use C.2.6 for source and use claims; use C.2.7 when representation-factor readings matter. For the named use, establish the source or model-state relations, decode or probe relations, and recoverability evidence it requires. Retain supported claims and uses; resolve a missing premise before relying on a use that depends on it. State any source-return action that use requires under its direct governor;
- B.5.2 governs changes within its abductive loop, including its prompt, candidate and rival sets, selected prime hypothesis, plausibility filtering, and reopen. Apply A.6.4 additionally only for an independently established EntityOfConcern change. State q when a receiving use is claimed, and judge a current case when that result is needed;
- keep any other independently current claim under the pattern that defines or tests it; the Relations section names the main neighboring owners.
A.6.4 defines arrow r, bounded-use assertion q, and the separate current-case judgement that E.18 may place at a StructuralReinterpretation locus. That placement identifies none of them and does not make the judgement satisfies.
Archetypal Grounding (Tell-Show-Show)
Tell. Retargeting relates epistemes about different EntitiesOfConcern. For a claimed receiving use, state the invariant, visible loss and conditions; judge a current case from its facts when that judgement is needed.
Show 1 — Physical cabinet to selected functional structure. Take Cab-7 and functional U.Structure Route-A as independently identified entities. Under an explicit finite-routing scheme, source episteme X states two observations of Cab-7 in configuration K: input L routed to output 1, and input R routed to output 2. X also identifies cabinet layout Layout-7 and manufacturer Maker-7. A separate definition episteme Z specifies Route-A with those pairs and a third pair M→3. Receiving episteme Y concerns Route-A and selects only its declared L→1 and R→2 pairs. C.2.1 distinguishes X, Y and Z by their complete claims, concerns and effective schemes.
In the selected finite-table substrate, r relates X to Y by the rule TestedRowProjection: match the named input rows and use Z's definition for the receiving structure assertions. Arrow equivalence uses the same endpoints and rowwise equality of that rule. This does not infer Route-A's definition from cabinet behavior alone.
Affirmative q states: Under K, Cab-7's observed outputs for {L,R} match Route-A's declared outputs. Dropping cabinet layout, manufacturer details and Route-A's M branch is acceptable for preparing a fault-isolation check list restricted to the observed inputs L and R. The current case compares L→1 with L→1 and R→2 with R→2; both match. The resulting check list is “for L, inspect output 1; for R, inspect output 2”; that use needs neither the omitted cabinet details nor the M branch. The judgement is therefore satisfies for this bounded use. A changed configuration or another input requires new case facts. Missing output observations yield cannot decide; an observed mismatch yields fails without changing q's polarity.
The unused expression Realises(Cab-7, Route-A) has no supplied direct predicate or governor in this fixture. It contributes nothing to the judgement. Placement of r and q in E.18 likewise supplies no case fact.
Show 2 — Fourier near-miss and positive branch. In the ordinary case, X and Y both concern sampled signal run Signal-17; X uses a time-domain representation and Y a frequency-domain representation. Use A.6.3.RT for this representation change. Under its declared conditions, Parseval's relation gives the energy-preservation equality; the spectrum notation still represents the same EntityOfConcern. If that mathematical correspondence or its conditions are unsettled for the receiving use, use C.29 to establish their adequacy before relying on the equality.
A positive A.6.4 branch opens only if C.2.1 separately identifies, for example, signal run Signal-17 and spectral-distribution object Spectrum-17 as the two EntitiesOfConcern. The receiving use must concern Spectrum-17—for example, comparing its peak distribution with another spectrum—rather than merely read another representation of Signal-17. Then r relates the two epistemes; affirmative q states the spectral-comparison proposition and may cite the Fourier relation and Parseval test. The current-case judgement is satisfies only when the named facts meet q's conditions and criterion while lost time localization remains visible.
Show 3 — Dataset to model. X concerns dataset D; Y concerns fitted model M, independently identified under the applicable model pattern. Affirmative q states the predictive invariant, visible losses, named prediction use, and conditions. The fit result and held-out test outcome are current-case facts; the judgement is satisfies when those facts meet q's conditions and invariant criterion. Individual observations and unmodelled distinctions remain visible losses, and any other dataset claim needs its own transfer basis. Identify any fitting application and performed Work separately under ER-6.
Bias-Annotation
A.6.4 foregrounds the source and receiving entities when the EntityOfConcern changes. Recover that pair. For a claimed receiving use, state q's invariant, visible loss, use and conditions. When judging a current case, recover the facts needed for that judgement. Open a neighboring branch only when a separately current claim needs its direct pattern.
Conformance Checklist (normative)
CC-A.6.4-1 - Endpoints and changed EntityOfConcern. C.2.1 identifies X and Y and their EntitiesOfConcern; the two entities differ. A changed kind, frame, predicate set, domain, or notation alone does not pass this check.
CC-A.6.4-2 - Arrow identity. The selected formal substrate supplies r's endpoints, arrow rule or designator, and equivalence criterion. Same endpoints, a diagram, or a use claim alone does not identify r.
CC-A.6.4-3 - Separate use proposition and case judgement. For a claimed receiving use, one C.2.1 assertion q names r, the receiving use, invariant, visible loss, conditions, and affirmative or negative polarity. When evaluating a current case, a separate judgement reports satisfies, fails, or cannot decide from current facts. The same r may have another q and judgement for another use.
CC-A.6.4-4 - Conservative receiving claim. Every assertion in Y satisfies A.6.2 P2. For an affirmative q, satisfies additionally requires enough case basis for q's invariant, loss condition and stated use. For either polarity, facts contrary to q yield fails; a missing deciding fact yields cannot decide and names that fact and the reopen condition. Neither result changes q's polarity.
CC-A.6.4-5 - Triggered additions only. For a Description or specification-use episteme, name every material change to claim content, effective scheme, grounding, scope, operating condition, or selected viewpoint under A.7 and E.10.D2. Add those values, evidence, currentness, a route-equivalence test, or a reopen condition only when they change q or the reader's action.
CC-A.6.4-6 - Separate semantic correspondence. Test an F.9 Bridge only when the case also claims a relation between two local senses. The Bridge, its bounded-use claim, optional CL, evidence, and reliance remain separate from r and q.
CC-A.6.4-7 - Separate application and Work. For measurement, computation, actuation, model fitting, authoring, and other effects, identify the operation application and its argument and result bindings when an A.6.1 operation declaration is current; identify any performed Work separately. The arrow statement r : X -> Y neither identifies an application or Work occurrence nor proves a production relation.
CC-A.6.4-8 - Fourier boundary. A same-signal time/frequency change uses A.6.3.RT; C.29 is added when a separate mathematical representation or transfer question remains. A.6.4 is used only after the receiving spectrum or other mathematical object is independently identified as a different EntityOfConcern.
CC-A.6.4-9 - StructuralReinterpretation boundary. E.18 governs structure position, path, crossing, and gate relations. A.20 tests q's proposition only when an internal constraint is current, and A.21 governs any gate decision. None identifies r or supplies a satisfies judgement merely by reference or placement.
CC-A.6.4-10 - Stop and ordinary use. A missing deciding fact yields cannot decide and names the fact and reopen condition; contrary facts yield fails. Otherwise one short paragraph answering the six practical questions is enough. No separate evidence, assurance, publication, currentness, or reusable declaration is required unless its own use condition is current.
Common Anti-Patterns and How to Avoid Them
Consequences
- Viewing and retargeting separate. A viewing arrow preserves the EntityOfConcern. A retargeting arrow relates epistemes with independently different EntitiesOfConcern; q states one bounded-use proposition, and the separate current-case judgement says whether the facts satisfy it.
- StructuralReinterpretation receives one core rule. E.18 can place r and q without duplicating their identities; the A.6.4 current-case basis remains the facts and separate judgement.
- Loss becomes usable information. A lossy mapping can serve one bounded purpose; reversibility and semantic identity remain separately established claims.
- Optional apparatus stays optional. F.9 enters only for cross-local-sense correspondence; route-equivalence, evidence, assurance, gate, publication, and Work branches enter only when their own claims are current.
- Description boundaries remain visible. Claim content, scheme, grounding, scope, operating condition, and viewpoint changes do not disappear into one retargeting bundle.
Rationale
A.6.4 exists because some mathematical arrows relate epistemes that concern different entities. A changed use claim does not create another arrow; the reader decides each receiving use from its q and current case facts.
SoTA-Echoing
Practice question. How can a transformation definition, its execution and a correctness claim remain separate, and which independent test establishes that the source and receiving epistemes concern different entities?
The A.6.4 split among r, q, and any application occurrence is a bounded FPF synthesis from these distinctions, not an externally established retargeting ontology.
Mini-checklist (for use)
Start with questions 1–2 to classify the arrow. Questions 3–4 concern a claimed receiving use; question 5 concerns its evaluation in a current case. Questions 6–7 apply when those additional claims are current.
- Does the EntityOfConcern change? If no, use A.6.3 or another preserving pattern.
- Which arrow, endpoint epistemes and EntitiesOfConcern are involved? Name them before naming a mapping technology.
- Which invariant does q state? Name its proposition and case assumptions.
- What is lost, and which receiving use tolerates that loss? A broad "same meaning" answer is insufficient.
- What witnesses the invariant and loss judgement? If the witness is missing or contradicted, stop or reopen.
- Is a relation between two local senses also claimed? Only then test F.9 separately; no Bridge follows merely from retargeting.
- Was computation or another activity performed? When an A.6.1 operation declaration is current, identify the application and its argument and result bindings. Identify any performed Work separately from r and q.
Relations
- Builds on. A.6.0 for a reusable FormalSubstrate declaration; A.6.2 for the local arrow discipline; A.6.3 for the preserved-EntityOfConcern neighboring branch; C.2.1 for episteme, EntityOfConcern, and use-assertion identity; C.29 for mathematical-lens use; A.6.3.RT for preserved-EntityOfConcern representation transitions; A.6.5 for SlotSpecs inside a reusable direct-relation declaration; A.7 and E.10.D2 for Description and specification-use boundaries; C.2 and C.3 or the relevant domain pattern for the invariant; and F.9 only for a separately claimed relation between local senses.
- Consumed by. E.18 may place r and q at a
StructuralReinterpretationlocus; A.20 may test the proposition carried by q; E.17 may publish an episteme that describes the case; KD-CAL and LOG-CAL may reason over a stated invariant. None redefines r or q. - Neighbor boundaries.
A.6.1andA.15govern an application and Work;A.10governs evidence;B.3governs assurance and reliance;A.21governs gate decisions;C.27governs temporal adequacy;A.3.3governs dynamics; the applicable direct control pattern governs control; andE.24.PUBgoverns publication. C.2.6 recovers source and use claims, and C.2.7 governs representation factors; B.5.2 governs its abductive-loop state.
A.6.4:End
Relational Precision Restoration - Recovering Direct Relations from Under-Specified Claims
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Plain name. Relation precision restoration.
Problem frame
Use this when. Use this pattern when a claim contains a relation-bearing phrase, but the phrase does not yet determine the direct relation, participants, direction, or detail needed by a later engineering claim or operation. Common recognition moments include a broad predicate such as "linked", "aligned", or "supports"; a participant named by metonymy; a qualifier that sounds precise while leaving the head kind unknown; service, server, provider, delivery, access, or bare role wording that leaves the promise, interface, System, system-role kind or assignment, direct participation, Method, Work, or evidence object unclear; whole, part, complete, turnkey, or end-to-end wording that leaves a candidate whole, boundary, parthood, composition, coverage, or Work claim unresolved; and integrity wording that still leaves open whether the sentence is about a structural whole, a characteristic or measurement, or evidence or assurance. When bare role is the trigger, use E.10.ROLE to recover the intended branch before applying A.6.P to a direct relation claim.
Quoted, external, or ordinary source prose may remain as written. Use A.6.P only when an FPF statement will use the phrase to guide action, justify a decision or gate, support assurance or reliance, publish a claim, or reuse it in another named source, practice, or model-use setting. Repair that receiving FPF statement; preserve the source wording as a quotation or source expression instead of rewriting it as though the source had made the repaired claim.
Primary working reader, viewpoint, and concern. The working reader is an engineer viewing the sentence as input to a later claim or operation. The concern is that another person can find the same world-side or episteme-side objects, find the same pattern that defines the relation or constrains the operation, and know which additional declaration, assertion, occurrence, designation, or representation detail that later use needs.
Primary EntityOfConcern. One relation-bearing claim in an episteme whose current expression leaves the direct relation kind or one or more actual participants unresolved, or leaves unclear whether a later claim or operation needs reusable declaration, explicit occurrence identity, designation, or representation.
First useful move. Replace the broad phrase with one readable sentence that names the participants and the direct relation believed to obtain. Name the rule defining its participants and obtaining condition; recover occurrence identity when the receiving use needs it. If either the participants or the relation remain ambiguous, keep a small working candidate note and resolve that ambiguity before adding a reusable declaration, assigning a designator, or choosing a representation.
First-minute result. The draft Bearing_B is linked to Pump_P becomes Bearing_B is part of Pump_P during Interval_T after inspection establishes the intended parthood claim under the applicable A.14 rule. The ordinary repair stops there. If a later maintenance claim must distinguish installation episodes, §5.1 returns the missing installed-part predicate and occurrence-identity rule; a RelationSignature, occurrence reference or graph representation cannot supply them.
What goes wrong if missed. A lexical replacement can make the sentence sound technical while preserving the same ambiguity. At the opposite extreme, an engineer can turn every relation phrase into a record-shaped episteme and then confuse that episteme, a declaration, or an identifier with the relation that obtains. Both failures obscure what is true, which object changes, and which pattern defines or constrains the needed claim or operation.
What this buys. The repaired claim remains readable. Load-bearing uses gain relation kinds, participant meanings, reusable typed declarations, occurrence identity, designations, and representations only where those distinctions change the later claim or operation.
Not this pattern when. Use the direct relation pattern when the relation and participants are already clear. Use A.6.5 when only reusable SlotSpecs are needed, A.6.REL when one obtaining occurrence needs explicit identity, C.2.1 when the issue is assertion or description identity, and F.18 when the object and relation are known and only designation remains unresolved.
FPF treats relation realism and epistemic access separately. A relation can obtain among its participants before anyone states, stores, diagrams, or names that fact. An assertion can affirm or deny the direct obtaining predicate. A declaration episteme carries reusable vocabulary and laws. A designator denotes an already recoverable object under an effective reference scheme. An episteme becomes available through a publication relation. A representation corresponds to an independently governed object or claim content. Relation precision restoration keeps these objects connected without collapsing them.
Problem
An under-specified relation claim blocks a later claim or operation because several ontological questions remain hidden inside one phrase:
- What kinds of objects are being related?
- Which direct relation predicate is asserted to obtain?
- Which relation-participant meanings are current, and are all actual participants named?
- Does the current text state world-side participation, make an episteme claim about the direct relation, or define a local kind of entities participating under one meaning?
- Does reusable typed use require a compatible
RelationSignatureand declaration-localSlotSpecs? - Does a later claim or operation need one obtaining occurrence to have explicit identity?
- If something changes, is the changed object the occurrence, a declaration edition, assertion content or reliance posture, an evidence relation, a designation, a receiving-episteme reference, a description, a publication relation, a Bridge, or a representation edition?
Without answers, readers cannot tell whether two statements disagree, whether one participant may replace another, whether an inverse sentence preserves meaning, or whether a later claim refers to an obtaining occurrence rather than to an assertion or representation of it.
Forces
Solution
Begin with the objects named by the claim. Recover actual participants and one direct relation first. Then add only the declaration, assertion detail, occurrence identity, designation, reference, or representation demanded by the later claim or operation.
Local RPR mantra. Name the referents. State the direct relation or comparison with its participants and use the pattern that defines it. Add a declaration, occurrence identity, designation or representation only when the receiving claim needs that contribution. For a change claim, identify what changed and apply its continuity rule. Then shorten without hiding the relation or its participants.
Referents means the objects recovered in 4.1; it is not a shared kind. Comparison means the direct comparison relation governed by A.19.CPM. Actual participants means the independently governed entities that participate under the relation's participant meanings. The mantra does not ask the reader to fill slots or positions or to create a record.
Sections 4.1–4.12 develop the same repair: resolve participants and hidden arity, preserve polarity, separate facts from assertions and representations, and stop at the sufficient readable claim. The additional branches are selected by the receiving use.
Recover the objects before choosing relation notation
Start from the claim as written and ground each load-bearing head:
- Identify the referent intended by each participant expression.
- Recover the participant kind required by the direct predicate. State that classification when it changes interpretation or the receiving use, using its applicable admission rule.
- Separate a world-side object from an episteme about it and from a publication or representation of that episteme.
- Recover metonymy. The phrase
at the tablemay state physical location or participation in a negotiation meeting. Evidence from the current case selects the direct relation; neither reading by itself establishes a local system-role kind or system-role assignment. - Leave the claim unresolved when the current evidence does not select one referent. A more technical synonym is not a repair.
The result of this step is an ordinary sentence containing identifiable objects. It is not a newly minted object kind. When several candidates remain live, use the small working note in A.6.P:4.9.
Copying an expression such as “my left” or “our project” into another participant's instruction can change its referent. Use A.6.P.RI when the receiving use still needs to establish whose reference is intended, what must remain the same, or which performer is to act. The result is a usable interpretation or instruction, or a specific missing condition. When those references and the task are already clear, use ordinary clarification or the relevant domain transformation; A.6.3.RT governs a change of representation language or reasoning medium needed for the receiving operation while the EntityOfConcern stays the same.
If the material is still a cue and no relation-bearing claim can yet be stated, stay with A.16.1 or B.4.1 instead of forcing relation publication. If the cue has stabilized into an open explanatory question but still has no selected relation answer, use B.5.2.0.
If counter-evidence or a failed use shows that a published relation statement overstates its articulation, closure, or framing, use A.16.2 to reopen, back off, or respecify that publication. A.16.2 records the retreat; A.6.P repairs the relation again only after the engineer can name a grounded candidate relation, its participants, and a discriminating check. Use A.16.0 only when readers must see lineage, branching, loss, or responsibility-transfer history; a local return needs no trajectory account.
A.6.P begins when the available observations or claims let the engineer name at least one grounded candidate relation, its participants, and a discriminating check.
State the direct relation, participant meanings, and obtaining condition
Write the smallest readable direct-relation sentence that answers the current question:
Then name the pattern that defines or constrains the direct relation and recover from it:
- the admitted direct relation kind, using an accepted domain relation name; recover its governed
RelationKindtoken when the receiving use needs that designation; - the relation-participant meanings and actual participants, each retaining its independently governed kind;
- the condition under which the relation obtains and its semantic predicate is satisfied by those participants considered under the participant meanings;
- applicability, direction, symmetry, inverse law, polarity, and temporal qualification when they change the predicate;
- the occurrence-identity rule when settling the relation kind or when the receiving use needs to distinguish, reidentify, refer to, or use an obtaining occurrence;
- when the direct ontology makes construction constitutive and the current question needs that construction or its identity contribution, the constructor, inputs, construction work or process, and the identity contribution required by that question.
An ordinary positive or governed-negative assertion can use an accepted domain relation name without introducing a new token. When the receiving use needs an explicit RelationKind token and no suitable token exists, first settle the relation value and any required relation-kind admission using the pattern that defines them, A.6.RCD, and E.24; then apply F.8 and, for durable naming, F.18 and F.17. Naming does not admit a kind or occurrence. An A.6.1 operation-application binding, local A.15.PROD or A.6.RCD claim, or non-assertability result keeps the semantics defined for that operation, production, or missing-relation claim and is not coerced into this relation-kind family.
An ordinary assertion may name the actual participants directly. When reusable typed use is current, a compatible RelationSignature declaration can restate the participant meanings, obtaining predicate, applicability, and identity rule and contain only the declaration-local SlotSpecs needed by the receiving typed uses. The declaration remains an episteme; it neither makes the relation obtain nor supplies occurrence identity.
Assertion polarity remains claim-side. An affirmative assertion claims that the direct predicate is satisfied; a negative assertion denies it. Judge any proposed refutation under the claim's direct rule or receiving evaluation. Use A.10 only when a bounded source-to-use reliance question needs its replayable account. Denial, refutation, or unresolved reliance creates no negative world-side occurrence.
Do not select ontology from grammar. A verb-shaped phrase supplies neither constructive identity nor agency. Use the pattern that defines, constrains, or tests the relation, object, Work, Method, change, local system-role kind, system-role assignment, or admitted System named by the current claim.
Recover actual participants, hidden arity, qualifiers, and typed declaration only when needed
Ask which actual participation belongs to the direct relation's obtaining condition. Add a participant or qualifier only when it changes one of these:
- predicate satisfaction or relation obtaining;
- applicability or admissible use;
- occurrence identity;
- whether one participant can replace another without changing the claim;
- interpretation under an effective reference scheme;
- scope,
Γ_time, viewpoint, view, or another qualification defined by the direct relation or receiving claim; - witness or evidence expectations for a named decision or publication use;
- the later claim or operation.
For Sample_S wasMeasuredBy Instrument_I, a later evidence claim may separately refer to the measurement work occurrence, its interval, the applied measurement method, a measurement-result episteme, and a calibration episteme. The measured-by relation includes only the actual participants selected by its direct obtaining condition; the other objects remain participants or content of their own work, evidence, temporal, method-use, measurement, assertion, or description relations.
When reusable typed use is current, declare each participant meaning needed by that use through A.6.5:
One SlotKind names one participant meaning locally inside one RelationSignature. ValueKind states the independently governed kind of the corresponding actual participant. refMode states how a receiving assertion or occurrence-description episteme designates that participant. The SlotSpec is declaration content; the participant does not become or occupy that declaration component. If one proposed ValueKind hides objects for which the predicate has different meaning, recover a real common kind or split the direct relation kind instead of preserving a hidden union as a prose list.
Keep world-side, declaration, assertion, designation, and representation objects distinct
State the correspondence needed to interpret the representation: which element represents which relation, assertion, declaration, participant or occurrence. Use the selected scheme directly when its conventions settle that question. C.29 applies when choosing, transferring or relying on a mathematical representation leaves a separate correspondence or inference question. The mere form establishes neither obtaining nor identity; its content may still state a claim or carry a supporting argument.
Functional and arrow forms are assertion or representation notation. The following installed-part example is hypothetical: a relied use first needs the missing direct relation and occurrence rules identified in §5.1.
The first can represent the content of a relational assertion; the second is a binary projection in a selected representation. After those rules exist, a use that relies on either notation declares how its argument or endpoint elements correspond to the actual participants, direct predicate, qualifications, and any designated occurrence. The ordinary readable sentence remains sufficient when no representation-dependent use is current.
Increase explicitness only for a named receiving use
Here receiving use is Plain shorthand for the later claim or operation that needs an additional object. It is not a shared FPF kind. Name that claim or operation and the rule that defines or constrains it before using it to justify more apparatus.
Use progressive elaboration from one recovered direct relation:
The diagram shows independently optional additions. A RelationSignature is not a prerequisite for explicit occurrence identity, and an assertion may name participants directly. A relation can obtain without a local occurrence designator. A stored row, graph edge, tuple or identifier may carry a claim or its grounds; its presence alone establishes no relation.
Apply A.6.REL when a receiving use needs to identify or reidentify the occurrence, compare its history, refer to it, or use it as a participant in another relation. A direct assertion can stop without explicit occurrence identity when that identity adds nothing to the receiving use. Repeated occurrences may have the same participants; their direct identity rule supplies the discriminator.
Resolve relation-dependent wording by the actual object
A readable word such as result, input, problem bearer, or next continuation can remain in Plain prose when the direct relation or claim is recoverable. Naming that reading creates neither a kind nor an occurrence. The world-side participant never becomes a declaration-local SlotSpec; the receiving episteme's designation denotes the participant without replacing it.
Name change by the object that changes
There is no universal relation-edit operation. First point to the object that the sentence says changed. If the sentence says that the same object continued, use that object's identity rule to test that claim. If identity-bearing episteme content changed, name the result as another episteme rather than an in-place edit:
The changed object controls the operation and continuity test. Ordinary revision can remain an activity description. When a claim deliberately asserts a particular dated U.Work, recover its A.13 basis and independent A.15.1 admission. F.6 applies only to a separate assignment-bound attribution through the same A.13 assignment; missing or failed attribution alone leaves independently admitted Work intact. If the same finding questions an admission premise, recheck that premise and its dependent conclusions. The resulting episteme is independently identified. A shared title, sequence, identifier or authoring intention alone does not establish edition, refinement or supersession. If no identifying fact changed, do not invent a change claim.
Preserve polarity and inverse meaning
Participant order is part of many relation predicates. Bearing_B isPartOf Pump_P and Pump_P hasPart Bearing_B can be paired as inverse readings only when that inverse law is declared under the direct parthood pattern. A symmetric relation is symmetric under its direct law, not because a sentence sounds reciprocal.
When two viewpoints use different readable directions:
- keep the same participant referents and their kinds;
- name the forward predicate defined or constrained by the direct relation rule;
- use an explicit inverse predicate or inverse reading when one is available under that pattern;
- keep scope, time, viewpoint, and reference scheme fixed while checking equivalence;
- treat a change of participant kind or predicate as a semantic change rather than a stylistic rewrite.
Use an actionable guide and keep a small candidate note when grounding is unresolved
For each ambiguity cluster, guide the reader through this order:
trigger expression -> candidate grounded objects and direct relations -> discriminating observations or tests -> readable direct-relation rewrite -> only the additional declaration, assertion, occurrence, designation, or representation needed by the named receiver -> applicable defining or testing rule
Do not organize the guide as a synonym list or make a table field the ontology. A qualifier such as comparative, safe, interactive, or reliable narrows wording but does not restore the head kind by itself.
When grounding remains unresolved and the work needs a note, use these prompts to keep the alternatives and discriminator recoverable. They prescribe no reusable schema or tuple kind.
For Alice is at the table, the physically present place and participation in a meeting are both plausible only while local evidence leaves them open. A location observation selects a located-at relation. A meeting roster may support a separately governed participation claim; a U.SystemRoleAssignment may also be relevant when its direct species predicate independently obtains. The note combines neither relation and infers neither a system-role kind nor an assignment from the place expression.
Unresolved alternatives prevent a conclusion that depends on selecting one of them. Name that dependent claim or action and the observation, test or direct-pattern condition that would decide it. The note can still support comparison, further inquiry, publication of the uncertainty, or a decision warranted under every live alternative. Stop only the dependent use; preserve the alternatives and any sufficient unaffected result.
Classify boundary claims and keep engineered rewriting epistemic
Use A.6.B only when a sentence at the boundary does at least one of four things: defines a truth-conditional relation or signature rule (L); states the conditions under which a named action or application may start or continue (A); states a generic prescription from a normative source, an individual duty with its actual bearer and obtaining U.Commitment, or a grant under A.6.B:8.4.1's permission-word branch (D); or states observations, effects or evaluation results and the conditions under which they are obtained (E). A sentence about claim scope or use, when to start or stop A.6.P, how to correct an endpoint kind, or whether a Bridge is needed does not qualify merely because it limits the repair.
Before giving a sentence an A label, answer two questions: Which named action or application may start or continue? What admission predicate governs that choice under the applicable rule? If either answer is missing, do not label the sentence A. Keep its scope or use, A.6.P start or stop decision, endpoint-kind correction, and Bridge need with the patterns that define or constrain those questions. Split any mixed sentence before classifying its claims:
- L states the direct relation semantics, declaration invariants, polarity, participant meanings, and any reusable
SlotSpectyping; - A states the admission predicate for a named action or application under the applicable rule. The actual satisfaction or admission-decision result is a separate E claim. A condition does not become A merely because it limits a claim, tells an author when to enter or stop this pattern, asks for an endpoint-kind correction, or requires a Bridge;
- D states what a normative episteme prescribes, an obtaining individual
U.Commitmentwith its actual duty bearer under A.2.8, or a grant selected by A.6.B:8.4.1 under A.2.8.PER. A generic prescription needs no invented individual bearer or commitment. An individual duty names its actual bearer; a system-role kind or assignment may be a rule ground but is neither that bearer nor the commitment relation. A grant retains its beneficiary, action and own obtaining basis; actual admission decisions and exercise remain separate E claims; - E states observations, effects or evaluation results and the conditions under which they are obtained. A separately claimed Work, evidence relation or freshness condition follows its own pattern.
Scope, Γ_time, viewpoint, reference scheme, witnesses, admissible use, any justified non-admissible overread, and stop or return condition stay with the direct relation or claim that needs them. They are not a universal qualifier kit. Select a non-admissible overread through F.19's plausible-reader test. An admissible use sentence is not an A claim unless the reader can point to both the named action or application and the predicate governing its admission.
If a later task must state a relation between a source episteme X and a receiving episteme Y, or describe an operation that produces Y, first identify X and Y independently under C.2.1. A difference in claim content, EntityOfConcern, or effective ReferenceScheme identifies another episteme; no component is rewritten in place. Keep X, Y, the mathematical arrow or construction, any use-specific assertion, and any operation application distinct. Use A.6.3 only for a compatible construction between epistemes about the same EntityOfConcern. Use A.6.2 for a local effect-free arrow family. Use A.6.4 for an arrow r whose endpoint epistemes concern independently different entities. For a claimed receiving use of r, add a separate C.2.1 bounded-use assertion q about r; its ClaimGraph states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. When a current-case judgement is needed, compare the facts with q and report satisfies, fails, or cannot decide; cannot decide names the missing fact and reopen condition. None of these patterns rewrites an episteme component or substitutes a declaration-local SlotKind or reference record for the arrow or application. If the needed entry or result condition is missing, preserve X, Y, the changed EntityOfConcern if any, and the sentence the next task needs as an explicit stop that names the missing arrow, use-claim, or application condition. Call X and Y editions, refinements, or successors only when that direct continuity relation independently obtains; a shared title, sequence, or authoring intention is not enough.
Ordinary authoring, checking or publication can be described directly. If the account deliberately asserts a particular dated U.Work, establish its A.13 basis and independent A.15.1 admission. Keep that Work, any operation application, mathematical arrow, endpoint epistemes and use assertion distinct. None alone makes the repaired world-side relation begin or cease, changes its participants or supplies occurrence identity. Stop before introducing these objects when the receiving use needs none.
Relax wording, then apply the governing rule
After the relation has been recovered, Plain wording may be shorter than the Tech explanation. The shorter wording remains usable when a reader can still recover the participants, direct relation, the pattern that defines its participant and obtaining rules, every qualification that changes the declared use, and the point at which reusable declaration, occurrence identity, assertion detail, or representation becomes necessary.
Stop using A.6.P when the direct relation and participants are selected. The selected direct pattern defines or constrains that relation. Apply the relevant pattern separately to any remaining assertion, occurrence-identity, evidence, work, Bridge, description, publication, designation, or representation question.
When generic relation recovery identifies one current claim at a method, intended-work, actual-work, production, evaluation, delivery, acceptance, transfer, or receiving-use boundary, apply A.6.P.WMR. Its application records exactly one of four result families:
- a direct subject-relation claim, positive or governed negative;
- an
A.6.1operation-application binding; - a local
A.15.PRODclaim or another local relation-bearing claim selected underA.6.RCDdisposition 2; - a non-assertability result with the reason defined in
A.6.P.WMR:4.3:factually unsupported,missing-information,missing-governor, the governing rule's inapplicable result, ormissing-substrate.
Missing-governor names the affected receiving use, participants, and missing predicate or obtaining law. A known rule's inapplicable result retains that rule and its unmet applicability condition; missing-substrate names unavailable constructor semantics under A.6.RCD:4.2. Neither by itself calls for a new relation kind. When participant referents and the named receiving claim have been identified but no current direct relation closes that claim outside A.6.P.WMR, require A.6.RCD rather than improvising a relation or kind.
Recover service/access claims through their rules
Start with the decision, not a facet list. Ask what the reader must choose, do, accept, explain, restart, or stop. Then write one plain sentence naming the subject or relation. If the source sentence carries several claims, write several plain sentences and name the pattern that defines or constrains each claim. The first useful result names each referent or relation, the claim needed for the current decision, and the next action. Add a C.2.1 assertion and ClaimGraph identity only when a named downstream use must carry or compare that claim independently.
Source-domain guard. Bare service has no default System reading. In ordinary business and physical-world talk it may name a dated occurrence of service provision, a reusable way of providing it, offered outcome or eligibility content, provider participation, or another direct claim. In software talk it may be metonymic wording for a process, deployed component, endpoint, application, host, or cluster. Name the referent before choosing Work, Method, U.PromiseContent, a local system-role kind, U.SystemRoleAssignment, U.System, or a direct relation. Never rewrite service automatically as server or as a System.
This table is a local recovery aid. Select the rows for the actual claims and stop when their direct results answer the receiving use.
Four language probes. Use these probes to select the current question and its relevant rows.
- “My service stopped.” Ask what stopped. Service-provision Work may have ceased; a bearer, such as deployed software or equipment, may have stopped or become unavailable; or promised availability or fulfilment may have failed. The sentence alone selects none. State, Work, promise, evidence, and fulfilment remain separate. Use A.1.SCR only if the repaired bearer claim itself depends on systemhood.
- “Which services do we provide?” Name the offerings or promise contents being compared and any provider assignments that are current. Open performed Work or fulfilment only when the question needs those claims.
- “How is this service provided?” A reusable way of providing it selects a Method; a procedure or API text selects an episteme and perhaps MethodDescription. Ordinary provision can be stated directly; a separate claim about a particular dated
U.Workfollows A.13 and A.15.1. Select the object from the claim the receiving question needs. - “Restart the service.” Name the bearer to restart—for example, a process, deployed component, endpoint, host, application, or cluster—and the action's governor.
Addressability is an aid, not a classification rule. If the sentence says call, visit, connect to, route to, restart, deploy, or scale, use it to ask which access point, delivery bearer, or other entity the claim concerns. Apply A.1 only when the repaired claim depends on systemhood. Actual Work still passes A.15.1, and every relation is tested against its defining predicate and obtaining condition. An endpoint may be an access point without being the whole delivery system.
Internet-access case. “We sell internet access” first becomes the commercial claim the reader needs: promise content, permission, provider or consumer participation, status, fulfilment, or another direct relation. For the promise reading, state the claim—for example, Customer-18 may rely on PromiseContent-IA-18 for the named connectivity outcome and acceptance content—using the pattern that defines or constrains it. If actual participation matters, state the direct provider and consumer participation predicates. State local system-role classifications or assignments separately only when their own A.2/A.2.1 conditions hold. If the source instead proposes the physically embodied whole InternetAccessArrangement-CA17, preserve that entity beside ProviderGateway-2, HomeRouter-18, and the status claims; use A.1.SCR only when the decision depends on whether the arrangement itself is a System. Do not substitute one gateway or endpoint before that evaluation. Keep the connection Method and API or procedure description separate. ProvisionConnectionPlan-18 is intended Work; ConnectionEstablishmentWork-42 is one dated occurrence. A real grant uses A.2.8.PER and is not inferred from a credential. Connectivity status, measurement, evidence, evaluation, delivery, fulfilment, and acceptance each need their own claim. After these claims are recovered, use A.1.STM only when the live question is how one result contributes to use of a named project system-of-interest; otherwise stop after stating the direct claim.
Physical repair-shop case. For “The repair service is delayed,” select the subject from the blocked decision. If the blocked decision is where to leave the machine, name the front desk or intake point and test systemhood only if that decision needs it. If the decision is what physically performs the repair, name the workshop, equipment, or other bearer. If it is who is responsible, name the direct responsibility predicate, its actual participants and applicability. Recover occurrence identity when the decision needs it; return the missing governor only for a required rule that is absent. A provider label, classification, or assignment is insufficient. What the customer was promised is promise content; an individual deadline duty is a separately obtaining commitment; how repair is done is a Method; the procedure card is a separate description. State an actual repair directly, or establish A.13 and A.15.1 grounds when the claim deliberately identifies particular dated Work. Fulfilment or acceptance requires its own relation.
Scope of the recovery. A.6.P defines only this recovery move. The recovery table introduces no common service/access kind or record. When the named decision depends on systemhood, cite A.1.SCR for the bearer or arrangement assertion. When the next question asks how an already recovered result contributes to project use, cite A.1.STM. State every other subject assertion under its predicate or constraint.
The selected predicate, its obtaining rule, and the current facts determine the result.
Recover pattern-governance and pattern-routing shorthand
Treat "pattern X governs/owns Y" as under-specified language. Recover Y and ask what X contributes: does it define a predicate, constrain a use, supply a test, describe a method, or only serve as a citation? State that contribution in ordinary prose. Add a C.2.1 assertion or ClaimGraph only when a named downstream use needs claim identity. A pattern id may remain as a locator for that content. If the sentence asserts actual formal-premise use, use A.6.RCD to derive or test the needed claim. If it asserts membership in or selection by a reusable signature, use A.6.0 to test that criterion under the signature's laws. Attribute any actual action, ownership, or authority claim through the direct relation that establishes it.
Likewise, "return/route/send/exit to the pattern for the next question" is procedural shorthand unless an actual relation is current. If work should continue, state the condition or unresolved question and name a candidate pattern whose Use this when entry accepts it. Preserve a real work, control, communication, API/tool, transport, graph, source/carrier, access, mathematical, or admitted B.4.1 route relation when that is the sentence's subject.
Ordinary instructions may say that an agent “uses” or “applies” a pattern. Expand that wording only when the claim depends on the identity of the actor, Method, description, dated Work, result, Transformation, or transformation-flow structure; then distinguish those objects using A.3.2, A.15.1, A.3.4, or the applicable flow pattern. A displayed sequence of pattern descriptions may describe a Method or constrain a separately admitted transformation-flow structure; establish any separately claimed Work, Transformation, or flow under its direct pattern.
Lexical guardrails
Overloaded words are diagnostic entry points, not relation kinds. In Tech or normative prose, same, synced, linked, connected, anchored, grounded, supported, and similar words cannot substitute for an unnamed direct relation or claim family. Bind and rebind remain name-binding or relation-specific vocabulary and are not generic relation-change verbs. A Plain gloss is admissible when its direct reading and the next applicable rule remain recoverable.
E.10 is the pattern for the trigger scan and E.10.ARCH the shared wording-use recovery architecture. F.18 is the pattern for durable name selection after the governed object is known. A.6.P does not maintain a second trigger registry or mint one specialization for every repeated word.
Archetypal Grounding
Physical assembly and repeated occurrences
Tell. A maintenance note says replacement bearing is linked to Pump_P.
Show the ordinary repair. Recover physical bearing Bearing_B, pump Pump_P, and interval Interval_T independently. The readable candidate claim is Bearing_B is part of Pump_P during Interval_T. Select the intended direct parthood reading under A.14 and its applicable subject rule. Where that predicate and the case facts already settle the receiving question, state the assertion and stop; an installation history or occurrence identifier is not required merely to report current parthood.
Show the identity-dependent stop. A reliability analysis needs to distinguish the installed-part relation before removal from that after reinstallation. Current A.14 does not define an InstalledPart relation kind, its participant meanings, obtaining predicate, applicability, or same-versus-new-occurrence rule. Return A.6.RCD missing-governor for that proposed relation, naming Bearing_B, Pump_P, the relevant intervals, and the reliability comparison. Removal and reinstallation alone do not establish two occurrences. A.6.REL explains how to apply a supplied identity rule; it does not supply this missing rule.
Conditional continuation. If a direct installed-part definition is accepted, apply its obtaining and same-versus-new-occurrence rules to the case facts. Distinguish two occurrences only when that rule and those facts warrant them; add stable designations or occurrence descriptions only when the receiving use needs them. For repeated typed reuse, an InstalledPartRelationSignature may then declare InstalledPartSlot and AssemblyWholeSlot under A.6.5. Until that definition exists, these names remain hypothetical declaration candidates, as in A.6.REL:5.2 and A.6.5:5.2.
If the adopted construction rule makes installation Work constitutive, identify that independently admitted Work and its declared identity contribution. Database rows, diagram edges, assertions, and declaration components retain their own identities and do not supply the obtaining or recurrence rule. When a mathematical representation is used, state its C.29 correspondence separately. A separate relator is needed only if the direct ontology identifies and justifies it.
Clinical evidence use and negative reliance
Tell. A care note says the measurement supports the dose change.
Show. Identify the measurement-result episteme, the named dose-change claim, and the evidence-use relation being asserted. Recover the measured characteristic and applicable range; C.16 governs measurement construction and applicability. The direct rule for the dose-change claim determines what the result warrants about it. Use A.2.4 for evidence-use classification and A.10 when the source-to-use account must remain replayable. Identify measurement Work or a WorkPlan only when the receiving question needs those separate claims, under A.15.1 or A.15.2 respectively. The broad predicate is not replaced by a universal support relation.
Show the boundary. If current evidence refutes the dose-change assertion or leaves reliance unresolved, the receiving evaluation records that posture. It does not create a negative world-side measurement, treatment, or evidence occurrence. A fresh publication of the same measurement-result episteme changes availability, not the measured condition or evidence relation by itself.
Episteme correspondence and representation
Tell. Two teams say the models are aligned, and one tool draws an edge between their model nodes.
Show — models. Model epistemes DesignModel_E and MaintenanceModel_E have EntityOfConcern PumpAssembly_P204 and effective reference schemes CAD-Part-Scheme-v7 and Asset-Register-Scheme-2026Q2, respectively. AlignmentEdge_17 joins nodes labelled BRG-6204 and bearing-4471.
Structure decision. No established model-use structure changes either label's reading or whether replacement approval may use the pairing. Add no BoundedModelUseStructure; a diagram boundary is not evidence.
Needed sentence. For bearing-replacement planning on PumpAssembly_P204, CAD-Part-Scheme-v7 label BRG-6204 and Asset-Register-Scheme-2026Q2 label bearing-4471 denote the same installed bearing. This is a candidate claim, not yet a fact.
Edge meaning. Under the selected graph convention, AlignmentEdge_17 expresses the candidate sentence. Its presence does not establish one referent or a Bridge occurrence. Use C.29 only if a separate mathematical representation or transfer question remains.
Adjacent reading. Record ninety-seven percent of endpoint pairs passed the mapping test with C.16. If approval relies on that result, classify the evidence use under A.2.4 and use A.10 when its source-to-use basis must remain replayable. The percentage does not establish the needed sentence.
Result. Bearing-replacement approval is not yet supported. First recover what each label designates under its reference scheme and the grounding or identity evidence for those referents. If the applicable designation and subject-identity rules establish one independently identified bearing, return that bounded identity claim; it does not by itself authorize replacement. If the labels designate different referents, or a kind and an individual, revise or reject the candidate claim as warranted. Keep missing interpretation or evidence explicit. Return A.6.RCD missing-governor only when the remaining predicate or a required applicability or identity rule is absent, naming that gap and the affected use.
Representation boundary. The edge and endpoint positions represent the assertion and its participants under the graph convention. Their interpretation makes the claim readable; the designation and subject-identity evidence decide its truth. Neither shared labels nor a visible edge establishes substitutability or an individuated relation occurrence by itself.
When the claim is that both model epistemes concern the same world-side holon, recover each episteme's exact EntityOfConcern or grounding designation plus the observations, trajectory, or identity evidence governed for that holon. A Bridge preserves stated correspondences and losses; it does not prove the common world-side referent.
Show the viewpoint-conformance use. A review must decide whether model episteme E conforms to maintenance viewpoint episteme P. Identify E from its claim content, EntityOfConcern, and effective reference scheme, and resolve P as one claim-bearing viewpoint edition before reading a diagram, field, or reference as ontology. Then apply the direct predicate governed by E.17.0: EpistemeViewpointConformanceRelation(E,P). Plainly, E conforms to this viewpoint.
For unchanged E and P, the pair <E,P> determines one positive occurrence. Selecting P for this review is a separate use qualification: selection neither makes conformance obtain nor enters occurrence identity. If another review selects P2, test <E,P2> instead of retagging E. A viewpointRef or diagram label does not identify either participant by itself. A query, transformation, or projection may supply construction history for E, but neither that history nor an assertion, evaluation, representation, or publication makes conformance obtain.
Add an occurrence designator when a receiving use needs to refer to or reidentify that conformance occurrence, distinguish it from another, or use it as a participant. Add evaluation, evidence, construction history, representation or publication detail only when the corresponding question matters. A.6.P stops after recovering E, P and the direct relation. E.17.0 governs the predicate and any separately requested U.View recognition; actual Work retains its own basis.
Method, Work, system-role objects, and agency
The sentence the inspection method checks Pump_P may remain ordinary metonymy under F.19. For a separate claim about actual inspection history, recover the following case. The source basis says that admitted System_S has the A.13 core for inspection: it is independently classified under local kind InspectorSystemRole and holds obtaining InspectionAssignment-17 of declared MaintenanceInspectionAssignment species for the stated scope and window. A.15.1 then independently admits InspectionWork_W and its enactsMethod(InspectionWork_W, InspectionMethod_M) relation; the examination relation separately connects the Work to Pump_P. Because this worked account expressly states under which assignment the inspection was performed, F.6 then establishes performedUnderAssignment(InspectionWork_W, InspectionAssignment-17) and checks the already recovered performer against the holder. If the deciding F.6 fact were missing, attribution would remain unresolved; contrary facts would refute that attribution. The independently admitted Work remains in either case. Taxonomy episteme and reference scheme may interpret the assertion but are not assignment participants. System_S performs InspectionWork_W.
Formal reduced case
3 < 5 states an ordinary mathematical comparison. The numerals designate values and the sign expresses the less-than predicate under familiar arithmetic conventions. No separate representation or transfer question remains, so C.29 requires no additional account. If a later use introduces one, explain the correspondence it needs. The present use requires no explicit occurrence identity and can stop at the assertion. A tool's graph edge, tuple or reifier represents that content without constituting the relation.
Bias-Annotation
This pattern favors ontology-first recovery, direct relation sentences, and the lightest explicit form that serves the named receiving use. That bias counters record-first and vocabulary-first repair.
The counter-risk is under-specification: an engineer may stop before a load-bearing participant, applicability condition, occurrence identity, or reference is exposed. The receiving-use test, hidden-arity check, three-way relation-dependent wording distinction, and explicit conditions for applying neighboring patterns provide the counterweight.
The pattern also favors neutral domain language. Examples span physical assembly, clinical evidence, epistemes, ambiguous source role wording, system-role kinds and assignments, Methods, and formal relations so that one publication technology or professional tradition does not become the default ontology.
Conformance Checklist
- Recognition. The use begins with one relation-bearing claim and states which later claim or operation is blocked by its ambiguity.
- Grounded heads. Every load-bearing head refers to an identified object or remains explicitly unresolved; a qualifier does not substitute for the head kind.
- Direct relation. Every positive or governed-negative direct subject-relation result states the actual participants and direct predicate under its applicable rule. Use an accepted domain relation name; require an explicit
RelationKindtoken only when the receiving use needs that designation. Recover occurrence-identity and construction content under §4.2 when the current question needs them. The A.6.P.WMR non-relation result families remain defined or tested by the rules for the recovered Method, Work, result, production, delivery, acceptance, transfer, or receiving-use claim. - Participant meanings. The direct pattern states the participant meanings, actual participation, obtaining predicate, applicability, and occurrence-identity rule; every participant retains its independently governed kind.
- No negative occurrence. Negative assertion, refutation, or unresolved reliance remains claim- or evaluation-side and creates no negative world-side occurrence.
- Demand-driven declaration. A compatible
RelationSignatureand declaration-localSlotSpecs appear only when reusable typed use is current; an ordinary assertion may name participants directly. - Designation separation. A participant designation or occurrence reference remains content of a receiving episteme and neither replaces the referent nor makes the relation obtain.
- Hidden arity and qualifiers. Every participant or qualifier included in the repair changes predicate satisfaction, applicability, identity, substitution, interpretation, admissible use, witness needs, or the named later claim or operation.
- Occurrence identity when needed. Apply the direct identity rule when a receiving use needs to identify, reidentify, compare or use an occurrence as a participant. Repeated occurrences with equal participants retain the direct discriminator.
- Construction choice. When construction is identity-bearing, the pattern defining that construction names the constructor, inputs, construction work or process, and identity contribution; otherwise the repair introduces no constructor.
- Object separation. Direct relation kind, participant meaning, actual participant, declaration, assertion, occurrence description, occurrence, designator, reference, publication, Bridge, and representation remain distinct where present.
- Relation-dependent wording. The reading resolves to world-side actual participation, an assertion- or description-side designation, or a justified C.3 local kind.
- Polarity. Participant order, inverse wording, symmetry, assertion polarity, and temporal qualification follow the direct relation law.
- Changed object. Every change statement selects one changed object and its governing row in A.6.P:4.7; no generic relation-edit operation remains.
- Boundary classification. Apply L, A, D, and E only to an A.6.B boundary statement. Before marking A, point to the named action or application and the predicate governing its admission under the applicable rule; if either is absent, leave claim use or scope, A.6.P entry or stop, endpoint-kind correction, and Bridge need with their own patterns.
- Candidate guide and stop. Unresolved alternatives are grounded candidates with a discriminating check. Name and stop the use that requires selecting one reading; preserve warranted inquiry, an explicit uncertainty report and decisions sufficient under all live alternatives.
- Representation boundary. The selected scheme makes the needed element-to-content correspondence recoverable. C.29 applies to a separate mathematical representation or transfer question; form alone establishes neither the direct relation nor its identity.
- Optional episteme relation or operation. Use this path only when a later task must relate source and receiving epistemes or describe an operation that produces the receiving episteme. Identify both endpoints independently under
C.2.1. UseA.6.3for a compatible same-EntityOfConcern construction,A.6.2for a local effect-free arrow that satisfies its entry and laws, andA.6.4for a different-EntityOfConcern arrowr. For a claimed receiving use ofr, add a separate C.2.1 bounded-use assertionqaboutrwith a ClaimGraph stating the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. When a current-case judgement is needed, compare the facts withqand reportsatisfies,fails, orcannot decide;cannot decidenames the missing fact and reopen condition. If the selected pattern's entry or result condition is missing, preserve the endpoints, changed EntityOfConcern if any, and needed sentence as an explicit stop naming the missing arrow, use-claim, or application condition. Keep any continuity relation separate, and useA.15.1for actual authoring, materialisation, checking, or publication Work. The arrow, use assertion, operation application, and Work remain distinct and none supplies occurrence identity for the repaired world-side relation. - Plain relaxation. Short final wording retains a recoverable direct relation, actual participants, and visible escalation points.
- Neighboring subject result. The repaired claim closes under one predicate or constraint selected in A.6.P:4.11, including exactly one of the four A.6.P.WMR families when that specialization is current; the neighboring pattern identifier is only its locator.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits
- Engineers can retain short practical relation language without surrendering exact ontology.
- Hidden participants and kind collapses become repairable through one repeatable sequence.
- Reusable declarations, occurrence identity, designations, and representations appear only for named receiving uses.
- Assertion, declaration, occurrence, evidence, designation, publication, Bridge, and representation changes remain independently reviewable.
- Neighboring claims remain separate subject assertions under their predicates rather than entering a generic container.
Costs and mitigations
- Grounding an ambiguous phrase takes more work than lexical replacement. The first useful move and small candidate note keep that work bounded.
- Some claims become longer when their truth depends on scope, time, viewpoint, witness, or another participant. Plain relaxation restores readability after the precise reading is stable.
- Domain-specific direct relation patterns still need their own obtaining and identity rules. A.6.P supplies recovery and selection of the defining or constraining rule, not a universal relation ontology.
Rationale
The problem is ontological before it is lexical. A broad expression is dangerous because it can hide different objects, predicates, participant meanings, actual participants, or later claims and operations. Replacing the expression without recovering those objects merely moves the ambiguity.
FPF therefore begins with relation realism: a relation may obtain independently of an assertion about it. Actual participants retain their independently governed kinds while participating under relation-local meanings. An optional RelationSignature makes those meanings reusable as typed declaration content; an assertion or description can designate participants or an already recoverable occurrence; a representation corresponds to the selected object or claim content. None of those adjacent objects substitutes for world-side obtaining or identity.
Construction matters only when the direct ontology makes it identity-bearing. In that case, constructor, inputs, construction work or process, and output identity explain how another occurrence begins. Other relations may obtain without such a constructor. A.6.P therefore uses constructional analysis as a discriminating test rather than as a universal ontology.
Progressive elaboration preserves affordability. An engineer can stop at a readable direct fact. Typed declaration, assertion detail, occurrence identity, stable references, descriptions, publications, and representations appear only when a named later claim or operation depends on them. This order also explains why naming comes late: a good name helps designate a recovered distinction but cannot create it.
The changed-object rule prevents a second ontology collapse. Revising an assertion, declaration, evidence relation, designation, reference, publication, Bridge, or representation is not automatically a change in the direct relation being discussed. Naming the changed object makes continuity, evidence, and return conditions intelligible.
Neutral terminology matters because A.6.P is cross-domain. Every claim about an object uses the rule that defines or constrains that claim; A.6.P does not collect unlike objects under one local umbrella. Domain-specialized vocabulary enters only when a direct local pattern defines or constrains the current object.
SoTA-Echoing
Ontological SoTA and constructive grounding
These sources constrain relation occurrence, identity, and construction. They are not interchangeable: FPF takes constructor-and-input discipline from the constructional-ontology line, uses BORO as a distinct 4D comparison, and treats implementation ontologies as stress comparators rather than proof.
Representation and implementation stress tests
These sources do not decide what exists. They test whether a representation can preserve the ontological distinctions selected above without turning a statement, row, graph term, tuple, or reifier into the world-side occurrence.
Service and access separation pressure
These sources constrain the recovery of service or access wording; they do not define a service ontology for FPF.
Further practice lineage includes ITIL 4, ISO 24617-2 speech-act work and SRE literature. ITIL offer and service-level wording can cue A.2.3 or A.6.C; A.2.9 separates a communicative act from its content and from any binding under A.2.3 or A.2.8. SRE interface, SLO, deployment, telemetry and incident distinctions help locate different subject claims. Apply those distinctions to the sentence; a word alone establishes no commitment, SpeechAct, Work or evidence relation.
These sources help separate the subject claims in §4.11a. Each claim retains its direct definition and obtaining basis; no shared service/access kind follows from the comparison.
Construction and identity comparisons inform the first recovery; representation questions follow the settled subject meaning. Service and access supply one recurring domain branch of the same method. The physical, clinical, epistemic and formal cases show how each receiving question selects its own direct rule.
Reopen the smallest affected passage. Start with the one claim, case, continuation, or source row that uses the changed fact. Reopen it when the subject predicate changes who participates, when the relation obtains, or how an occurrence is reidentified; when newer source evidence overturns or narrows the construction or reification distinction used there; or when an actual use can no longer reach the practical result or stopping boundary promised by that passage. Do not reopen the whole pattern unless the same change reaches several passages. If a continuation no longer matches the cited pattern's Use this when condition and promised result, stop using that continuation until it is repaired.
Relations
- The direct relation pattern defines or constrains obtaining, predicate satisfaction, and the occurrence-identity rule. After A.6.P recovers that relation,
A.6.RELgoverns demand-driven explicit individuation, application of that identity rule, and occurrence-as-participant use. A.6.0governsU.Signatureand compatibleRelationSignaturedeclarations;A.6.5governs declaration-localSlotSpec,SlotKind, participantValueKind, and receiving-episteme designation mode.- Use
A.6.RSIRto distinguish direct participation, declaration, operation, assertion or description, and representation when interface, role, slot, field, parameter, or endpoint wording is the entry cue. A.6.Bseparates L, A, D, and E claims after the direct relation is recovered. When the next task needs a relation between epistemes or an operation that produces a receiving episteme, identify both endpoints independently underC.2.1. UseA.6.3for its compatible same-EntityOfConcern construction,A.6.2for its local effect-free arrow, andA.6.4for a different-EntityOfConcern arrowr. Add a separate C.2.1 bounded-use assertionqaboutrfor a claimed receiving use, and the three-valued current-case judgement when that judgement is needed. If the selected pattern lacks an entry or result condition for the case, stop explicitly and name the missing arrow, use-claim, or application condition. UseA.15.1for actual authoring, materialisation, checking, or publication Work; keep the arrow, assertion, judgement, application, and Work distinct; and assert an edition or successor relation only after its own predicate is satisfied. Ordinary A.6.P repair stops before these objects.A.6.6provides specialized recovery for basedness. Service/access wording stays in A.6.P:4.11a until the predicate is recovered; cite the pattern that states it when the reference must travel. A.1.SCR applies only after one bearer or arrangement claim has been recovered and the decision depends on systemhood; A.1.STM applies only after recovery when the separate question is contribution to use of a named project system-of-interest. Cross-context and whole-part wording may useA.6.9orA.6.Honly when that pattern's entry accepts the objects named in 4.11 and its result states the direct predicate and participants or an explicit blocker. If either check fails, keep the 4.11 blocker and name the missing predicate or unmet entry condition. A situation record, Card, or bundle does not replace the direct relation, claim-bearing episteme, or representation.A.6.P.WMRdefines the method, work, result, production, delivery, acceptance, transfer, and receiving-use boundary and the four result families listed in 4.11.- Use
A.6.RCDafter the reader can name the participants and the sentence the next task needs, but no current pattern supplies its predicate. Broad wording alone is not amissing-governorresult. C.2.1governs assertions and descriptions. A.6.P identifies one candidate epistemeE, one viewpoint epistemeP, and the conformance question;E.17.0testsEpistemeViewpointConformanceRelation(E,P). If the next task also asks whetherEis aU.View,E.17.0handles that recognition separately. Viewpoint selection, evaluation, construction, representation, and publication do not establish conformance;A.10governs reliance, whileE.17andE.24.PUBgovern publication.- Use
C.3andC.3.1only if the next claim must quantify over a locally defined participant set, test membership or substitution, or order kinds. Otherwise do not mint a local kind. - Use
A.1,A.2,A.2.1,A.3.1,A.3.4, andA.15.1for the direct criteria for Systems, local system-role kinds, separate System-classification judgments, directU.SystemRoleAssignmentspecies, Methods, actual bounded change, and Work. A.2.4supplies first evidence-use or status-use classification;A.10supplies a replayable source-to-use account when needed, andB.3governs a separately named assurance claim.F.9directly definesBridgeas a species ofU.Relation, its two local-sense participants, itsBridgePredicateProfile, the condition under which the predicate is true, and its occurrence-identity and recurrence rule. UseC.2.1separately for assertions, occurrence descriptions, and Bridge Cards; useE.24.PUBfor publication, and the receiving object's own pattern for any use that actually occurs. UseA.6.RCDonly when the needed relation is not supplied by F.9 or another current defining or testing pattern after the participants and needed sentence are explicit.C.30.Pdefines or constrains architecture wording,C.16.Pcharacteristic wording,G.2palette/front/archive distinctions, andA.6.Ffunction-like wording. Each cited pattern contributes the named definition or constraint; its identifier is a locator only when that reference must travel.A.16.1andB.4.1retain cue material that has not reached a grounded relation-bearing claim;B.5.2.0carries a stabilized open explanatory question that has no selected relation answer;A.16.2records reopen, backoff, or respecification when a published relation overstates articulation, closure, or framing. UseA.16.0only when lineage, branching, loss, or responsibility-transfer history itself must be published.- Use
F.19for ordinary precise-plain-language repair and its plausible-reader test. UseE.10for wording triggers, E.10.ROLE to recover the branch of bare role, andE.10.ARCHfor the shared recovery architecture. UseF.18for designation after objects and relations are recovered.
C.29 mathematical-lens account and representation boundary
Use C.29 when choosing or transferring a mathematical representation could expose a needed relation, invariant, obstruction, approximation or resource limit, or when a proposed inference exceeds the representation's supported correspondence. Its operation identifies a mathematical object, establishes the needed correspondence, performs the mathematical work and returns the consequence with its limits. An adequate local equation, algorithm or domain model needs no C.29 note when no separate representation or transfer question remains. A relied-on representation still follows its selected interpretation conventions; neither a lens-use account nor visible form makes a world-side relation obtain or supplies occurrence identity.
For cross-context meaning, export or substitution wording, first distinguish designation, an operation and a semantic-correspondence claim under A.6.9. Only the last opens F.9: recover both local senses and test its direct Bridge predicate. F.9 supplies the obtaining condition and occurrence-identity rule when the two exact local-sense endpoints resolve, their interpretation bases differ, and the declared profile applies. Use C.2.1 for any independently needed assertion, occurrence description or Bridge Card, and for a bounded-use claim when a proposed use requires it. A.2.4 classifies evidence use; A.10 supplies a replayable source-to-use account when needed; B.3 governs a separately named assurance claim; E.24.PUB governs publication, and the receiving object's pattern governs any use that actually occurs. A changed claim, Card, evidence item, reliance result, or publication is not a changed Bridge occurrence. Use C.29 when a separate mathematical representation or transfer question remains. A representation may state or support a Bridge claim; its presence alone establishes neither the Bridge nor the represented world-side relation. If the sentence needs no cross-context correspondence or substitution claim, add no Bridge. If it needs another relation for which no current pattern supplies a defining or testing rule after the participants and needed sentence are explicit, record the established A.6.RCD missing-governor result.
A.6.P:End
Recover Agent-Relative References for Action
Type: Method pattern Status: Stable Normativity: Normative unless marked informative
Problem frame
Use this pattern when an instruction or account depends on who says, reads or acts on it, and copying its words could change the intended object or action. “My left”, “our account”, “here”, “now” and an omitted actor can remain understandable to their originator while becoming ambiguous or misleading for another participant.
The subject is the interpretation and use of such an expression. Recover what it refers to at its source, decide what the receiving use must preserve, and connect the recipient to the relevant participant or position before deriving an action.
The first useful result is an interpretable account or instruction for the receiving work, or a specific missing reference or transfer condition. Sometimes it is enough to preserve an attributed report; sometimes another performer needs a different instruction to obtain the same result.
If the participants, relative expressions and intended action are already clear, proceed directly. Use this method where a difference of speaker, recipient, position, time or other reference condition could change what happens next.
Problem
Two people can understand “left” and still move an object in opposite directions. Two systems can share the same description of a workplace while lacking the link that identifies which described participant each system is. A teacher can repeat a learner's first-person report while unintentionally presenting it as an observation the teacher made.
Making an account explicit helps, but does not settle how to use it after transfer. The recipient may be asked to preserve the same external destination, repeat a rule relative to their own body, or merely understand what the original speaker meant. These purposes can require different results even when everyone agrees on the participants and their orientations.
The difficulty is to preserve the relevant meaning without assuming that a copied expression retains its reference or that understanding an instruction supplies the means to perform it.
Forces
Solution
Recover the source reference, establish the receiving purpose, then derive only the interpretation or instruction that those conditions support.
Find the expression whose reference matters
Start with the statement and the work it is meant to support. Identify a word or omitted participant whose interpretation changes the result: for example, whose account, whose left side, which location or which time.
Use A.6.P to recover the relevant participants and relation. Read a quotation relative to its attributed speaker until the use calls for another interpretation. An imperative may leave the intended actor implicit; distinguish that actor from the person relaying the message.
Choose the smallest explicit account that removes the consequential ambiguity. A sentence such as “Dana means the cabinet to Dana's left” may suffice. If the source participant is unknown and the choice matters, retain that missing fact.
Recover the source conditions
Establish the source participant and only the conditions needed to interpret the expression. Direction can depend on orientation; “here” can depend on location; “now” on the time of utterance; “our account” on the organization and account relation.
C.2.1 supplies the distinction between the content and the rules used to designate its objects and interpret its expressions. Use the available records, communication setting or the participant's clarification to recover those values. A timestamp or sender field helps only if it identifies the relevant occurrence or speaker.
Keep unknown conditions visible. Where several interpretations permit the same safe continuation, that continuation may proceed without settling every detail. Where they lead to materially different actions, obtain the missing condition or give the conditional alternatives instead of silently selecting one.
Establish what the receiving use must preserve
Ask what the recipient is being asked to do with the source. For example:
- understand or report the original statement with its original referents;
- obtain the same external result through the recipient's own action; or
- apply the same relative rule afresh to the recipient.
Recover the purpose from the assignment or working agreement.
For example, “move the crate one metre to my left” can identify a direction from the speaker's orientation. A second performer preserving that displacement may need to move to their own right. “Repeat the movement to your own left” instead applies the relative rule to the second performer and can produce a different displacement.
Knowing both orientations does not choose between those tasks. If the transfer purpose is missing, state that missing condition before deriving an unconditional instruction.
Express the relation for the receiving use
Make the participants and preserved result recoverable in the form the recipient can use. This may be an ordinary sentence, a diagram or an instruction using an established coordinate convention. The relevant subject method supplies a spatial transformation, financial classification or other domain operation when one is needed.
Use A.6.3.RT when the EntityOfConcern stays the same and the operation the receiver needs depends on a change of representation language or reasoning medium. Extra information needed for the new expression remains an additional input. If C.2.1 identifies different EntitiesOfConcern, use A.6.4 for the invariant, visible loss and bounded receiving use. Changing the performer, notation or coordinates alone does not establish such a change.
For a report of experience, retain who experienced and expressed it. B.5.EA supports articulation and correction by that participant. Translating the report into an observer's vocabulary cannot by itself establish a bodily cause or give the observer the same experience.
Connect the recipient to the account and derive the action
Establish which described participant or position the receiving agent occupies for this use. A common description of all participants does not supply that link by itself. A person may recognize their part in the working situation. An artificial agent uses the identifying information and, where needed, sensed conditions supplied by its configuration.
Then interpret the account or derive the instruction under the purpose selected in §4.3. Recompute relative descriptions when necessary. When a message is only being quoted, preserve its original attribution rather than making the quoting recipient its speaker.
Before acting, retain the receiving work's requirements for authority, capability and resources. This method repairs the reference and transfer; the recipient performs the action using the relevant domain method.
Check the difference that could defeat the transfer
When a wrong reference could change the action, vary the relevant condition in a small safe case: another receiver, a changed orientation, a later time or a different organization. Derive the result from the recovered relation and compare it with the selected receiving purpose.
If the words stay the same but the result changes incorrectly, return to the source conditions or transfer purpose. If the instruction is correctly understood but cannot be performed, obtain the missing capability or support instead of continuing to repair its wording.
Stop when the account is sufficient for the intended use, or when a named unresolved condition prevents it. Retain a written reference or conversion rule only when later use needs it; an ordinary clarification can finish in the conversation.
Archetypal Grounding
The following constructed cases show different things a transfer can preserve.
Preserve a displacement across orientations
A faces north and asks B to displace a crate one metre in the direction A calls left. B faces south. The assignment is to preserve the external displacement, and both headings are known.
The source direction is west. For B, facing south, west is right. The receiving instruction is therefore to move the crate one metre to B's right. If B turns east before acting, west becomes backward. Copying “left” would now send the crate north.
Change the assignment to “move the crate one metre toward your own left”. With B facing east, the correct displacement is now north. The known headings did not settle the instruction; the preservation condition did.
If B's heading is unavailable, “one metre west” can still be a complete instruction for a performer who can act in that frame. Otherwise the body-relative instruction remains unresolved. The method asks for the information needed by the chosen means, not for every possible position description.
A mobile robot receiving the same external displacement needs a usable relation between the shared frame and its action representation. Obtaining that relation and the capability to perform the movement is a separate technical task.
Preserve the speaker when relaying a request
Dana writes to an assistant: “Put the comparison in my project folder.” The assistant sends the request to another worker. Replacing “my” with the new worker's own project folder would change the destination.
The receiving purpose preserves Dana's destination. The assistant identifies Dana's project folder through the available project information and relays: “Put the comparison in Dana's project folder,” with a usable reference to it. The worker uses its own authorized means of access; Dana's request does not grant access that the worker lacks.
If the next assignment is instead “each worker puts a copy in its own project folder”, the rule is applied relative to each worker. That is a changed distribution task, not another wording of the original destination.
Where the workspace contains several Dana projects and the intended one cannot be recovered, the useful result is a question selecting the project. Producing another fluent paraphrase leaves the same action unresolved.
Relate a dancer's report to an observer's account
A dancer facing the teacher says, “I feel a pull along my left side when I turn in this figure.” The teacher sees movement on the teacher's right. Both accounts can concern the dancer's left side even though the spatial words differ.
The first receiving task is to understand the report. Recover the dancer as the experiencing participant, the dancer's orientation and the turn being described. The teacher can say, “You report a pull along your left side during that turn,” and ask the dancer to correct the expression if needed.
A second task is to decide how to change the movement. The report and external observation can inform that inquiry, but do not themselves identify the tissue, force, cause or suitable exercise. The relevant bodily practice must supply the further operation.
In this figure, maintaining balance during the turn is part of performing the figure; regulating bodily effort helps enact that balance, while the steps keep their required rhythm. Changing whose account is used can make another question accessible; it does not by itself identify which constituent needs development. B.1.5.EW supplies the inquiry into these constituent–whole connections, and B.5.EA helps articulate a distinction the dancer cannot yet express.
Bias-Annotation
A translator can assume that the recipient occupies the same position as the source. A shared diagram or vocabulary makes this especially easy. Test the changed condition on which the action depends.
An observer can also replace the performer's report with an interpretation that is easier to describe externally. Keep the report open to correction by its source and give the additional interpretation its own basis.
Conformance Checklist
For a consequential interpretation or transfer, ask:
- Which expression depends on its speaker, user or situation?
- Are the source participant and action-changing reference conditions recoverable?
- What does the receiving use preserve?
- Can the recipient identify its own relevant position in the account?
- Does the derived action still satisfy that purpose when the consequential condition changes?
- Are missing information, authority, capability and support distinguished?
- Does any change of EntityOfConcern use A.6.4 rather than being assumed from new notation?
Use the questions needed for the receiving decision. An already clear instruction needs no additional record.
Common Anti-Patterns and How to Avoid Them
Copying a relative direction. The source and recipient face different ways, but both act on the same word. Recover the source direction and the intended receiving result before deriving the recipient's instruction.
Replacing every “I” with the recipient. A quotation or relayed instruction loses its original speaker. Preserve the source attribution unless the new task deliberately applies a rule to another participant.
Treating shared facts as self-identification. Several systems receive the same participant description, but none has been linked to its own entry. Obtain that link from the working configuration.
Turning a felt report into a bodily cause. “The dancer reports tension here” becomes “this tissue causes the failure”. Preserve the report and use the appropriate subject method to examine the causal claim.
Consequences
The same source account can support a usable receiving instruction without losing who or what it concerned. A changed position or participant becomes a condition to handle where it matters.
The method can expose missing information and thereby postpone an action that previously appeared clear. Where ordinary shared understanding already settles the reference, further formalization would add cost without improving the action.
Architectural Rationale
Relational precision restoration recovers missing participants. Agent-relative use additionally requires a link between the receiving agent and the described participants, together with a decision about what the transfer preserves. Neither a complete participant list nor a change of notation supplies these by itself.
The construction therefore combines the source interpretation, receiving purpose and recipient's position. Representation change and EntityOfConcern retargeting retain their existing conditions. Domain operations compute the conversion or classification; this method exposes the premises they need and returns their result to the receiving action.
The method applies when the receiving performer can be identified in the account and the relevant reference conditions can be recovered. Human first-person experience remains available through the experiencing person's account and correction. An artificial agent uses the identification, representations and signals its configuration supplies.
SoTA-Echoing
The practice question is how an explicit shared account becomes usable by an agent whose position differs from its source. The method recovers the source reference, chooses what the receiving use preserves and connects the recipient to the account. Its serious alternative is to make all participants explicit and assume that this alone determines the receiving instruction.
Adapt the distinction between common descriptions and agent-relative use. Partridge and colleagues, Ontology then Agentology (2018), §§2–4 and Figure 2, distinguish the reusable form of an account from its agent-dependent content and add a link identifying the system itself. This supports the self-identification required in §§4.2 and 4.5. It is a conceptual source, not evidence about human learning or current robot performance.
The crate case shows why this pattern also states the preservation condition in §4.3. Even correct source interpretation and self-identification leave two different possible tasks: preserve the displacement or repeat the relative movement. This is the pattern's methodological synthesis, rather than a result attributed to that paper.
Reuse representation and retargeting methods under their own conditions. A.6.3.RT is sufficient when the receiving use needs only a representation change under already available bindings. A.6.4 is needed when the independently identified EntitiesOfConcern differ.
Use the simpler direct clarification when it already settles the action. Reopen the construction when it cannot determine which reference changed, when the recipient cannot bind itself to the supplied account, or when the intended preservation condition fails under changed use. Technical conversion and learning methods require their own current subject evidence.
Relations
- A.6.P restores the participants and relations hidden by an underspecified claim.
- C.2.1 supplies designation, interpretation and EntityOfConcern distinctions.
- A.6.3.RT changes representation while preserving the EntityOfConcern; A.6.4 governs bounded use across a change of that object.
- B.5.EA articulates a distinction from experience while preserving the source participant's correction.
- B.1.5.EW recovers how constituent actions enact the encompassing work; a change of reference position is not itself a change of Method level.
- A.15.10 recovers a transferred or interrupted continuation. Use this method when an unresolved agent-relative expression prevents that continuation.
A.6.P.RI:End
Relation Recovery for Method and Work Claims
Plain label: recover the relation hidden by input, result, and handoff wording Type: Architectural precision-restoration pattern (A) Status: Stable Normativity: Normative unless explicitly marked informative Specializes:
A.6.PRelational Precision Restoration
Problem Frame
Use this when. Practitioners SHOULD use this pattern after A.6.P generic relation recovery has isolated one current method-or-work boundary claim and the exact entity is already in view, but words such as input, raw material, source data, source material, output, result, outcome, deliverable, or handoff still do not reveal the direct relation that makes the sentence true. They SHOULD also use it when method, intended-work, actual-work, production, evaluation, delivery, acceptance, transfer, or receiving-use wording leaves that claim's participant meaning or orthogonal claim dimensions unclear.
The primary EntityOfConcern is one relation-bearing claim in an episteme. The trigger word helps a practitioner notice the problem; it is not the governed object, a participant kind, a relation kind, or a universal family of inputs and results.
The practical question is which relation can be stated for the receiving use. SubjectPatternLocator identifies the pattern description containing the defining or constraining ClaimGraph; case facts determine whether the relation obtains.
First useful result. Start at the boundary-word sentence and answer three ordinary questions: what thing is being named, relative to what method, plan, work, operation application, transformation, delivery, or receiving use, and what direct verb can safely be said now—or why can it not yet be said.
For example, a note says, inspection report R-17 is the result of inspection. R-17 is a report episteme. If the current related object is independently identified inspection application P-17 and its declaration-local result-binding predicate holds, write: Inspection application P-17 returned report R-17. Then stop unless the current use separately asks about report inception, inspection Work, evidence, publication, delivery, or acceptance.
The nearest three failures keep the same thing and related object while changing only the deciding deficit:
- if the binding governor is known and the case facts fail its positive predicate, the proposed positive binding is
factually unsupported; - if the governor is known but the fact needed to decide whether P-17 returned R-17 is unavailable, return
missing-information; - if no current result-binding predicate or direct report relation governs that pair, return
missing-governorand name the participants, proposed predicate, affected use, and absent definition; name a future pattern or declaration need only when one is identifiable.
Only when another reading could change the answer should the practitioner make the formal distinctions explicit: reusable declaration versus intended, committed, current, or historical subject relation; exact extent; polarity; and whether the claim is assertable. A direct relation additionally names its exact RelationKind and resolving direct pattern or relation-declaration episteme. An operation binding or local claim instead names its declaration-local or admitted predicate and defining declaration. These assurance details check the ordinary answer; they are not prerequisites for understanding a simple positive past-tense sentence.
What changes in practice. The engineer stops debating which broad word is correct. They name the thing, the object it is relative to, and the direct verb they can safely say now; if the attempted claim is not assertable, they state the reason-specific stop under section 4.3. Formal claim dimensions and assurance apparatus appear only when they can change or check that answer. Planning, actual participation, production, evaluation, delivery, acceptance, and transfer no longer inherit one another through vocabulary.
What goes wrong if missed. A plan is read as actual participation; a method description is treated as a work occurrence; an operation result binding is mistaken for a produced entity; a changed continuing entity becomes a new output; a delivery or handoff package is treated as the transfer; or a convenient missing relation is replaced by a new universal kind.
Ordinary non-use boundary. Practitioners SHOULD NOT use this pattern when the exact direct relation and all claim dimensions needed by the receiving use are already readable; they SHOULD apply that direct pattern and stop. They SHOULD use C.2.P first when the unresolved question is which source expression, episteme, publication, or source-to-use relation is current; A.15.PROD directly when the only current question is production-work participation, entity-identity inception, or production completion and its participants are already exact; and the direct measurement, evaluation, commitment, delivery, acceptance, transfer, resource, premise, transformation, method, planning, or work pattern when that relation is already selected.
Problem
Boundary words are useful in ordinary language because they compress a relation into a role-like label. The compression becomes unsafe when a later claim depends on which relation obtains. The same entity can be a resource used by work, an argument bound in one operation application, an affected referent changed by work, a constituent of another entity, a premise used in reasoning, a newly constituted episteme, a delivered item, or an object used by receiving work. Those are not interchangeable positions.
The repair preserves ordinary readability without manufacturing a universal work-result ontology. It also recovers, without collapsing them, the claim subject, modality and temporal extent, polarity, and recovery or support state. A reusable declaration, an intended relation, an obtaining commitment, an actually obtaining or historically obtained subject relation, and an unresolved claim can overlap across those dimensions; they are not one posture axis. A sentence can be ontologically precise and still be false or unsupported; evidence and assurance remain separate questions.
Forces
Solution
Treat the boundary wording as a claim about one thing relative to another object. Recover the direct verb or reason-specific stop first. Keep claim subject, time, polarity and assertability independently recoverable when they can change the answer.
The method handles one relation-bearing claim at a time. The trigger word stays in view only until the thing, related object, and safe direct verb or stop are recoverable. The result replaces the compressed phrase with the shortest ordinary sentence. If a neighboring claim is still needed, apply the pattern whose Solution answers that question.
Thin recovery core and conditional interfaces
The stable ordinary core is one A.6.P-isolated relation-bearing claim, one thing, one related object, one direct verb or reason-specific stop, exactly one of four truthful exit families, and one readable sentence. The fourth family explains why the attempted claim cannot be asserted: factually unsupported, missing-information, missing-governor, a governing rule's inapplicable result, or missing-substrate, as distinguished in section 4.3. Missing-governor names the affected use and absent definition, applicability, or occurrence rule; it names a future pattern or declaration need only when one is identifiable.
Claim subject, modality and temporal extent, polarity, and recovery or support state remain four independent assurance controls. Their values must be recoverable whenever they can change the answer, but a practitioner does not have to recite the four labels when an ordinary sentence already makes the only material reading clear. WMR supplies this recovery and stop. It does not absorb the algorithms, checklists, or ontics of rules applied to a separate question.
Three ordinary questions and two conditional assurance questions
The practitioner stops after question 3 when the ordinary answer has one clear reading and no named later use needs more apparatus. Questions 4 and 5 inspect or reuse that answer; they do not replace it.
Use the four claim dimensions only when they can change the answer
The four dimensions remain independent. Make a dimension explicit when two plausible values would change the sentence, the next action, or the stop. Otherwise let ordinary grammar carry it: CF-17 was consumed by W-204 during I-204 already states a positive historical subject relation at one extent and does not require the reader to label four axes.
Well-formedness constraint WMR-WF1 — orthogonal claim dimensions. Whenever one of the four dimensions can alter the result, its value must be separately recoverable from the sentence or its immediate governed basis. No dimension supplies another. Explicit axis vocabulary is required only for a material ambiguity, comparison, assurance replay, or reusable formalization; it is not a prerequisite for every simple direct sentence.
Factually unsupported applies when an applicable governor and sufficient deciding facts are available but those facts fail the test for the proposed polarity. Missing-information applies when a fact needed to decide the test or its applicability is unavailable. Missing-governor applies when the participants and question are known but no direct rule supplies the needed predicate, condition or occurrence law. A failed test supplies no opposite polarity without its own basis.
A current commitment is expressible without collapsing fulfilment only when its commitment RelationKind, participant meanings, extent, obtaining predicate, and the SubjectPatternLocator for its defining or constraining content are named; a local id such as COM-17 is not that settlement. The commitment does not establish fulfilment of the promised delivery. Judge that separate claim under its own predicate and case facts; unavailable facts leave fulfilment unresolved rather than proving non-fulfilment. A separately stated past case fact remains positive at its governed extent after its named participants satisfy the governor's predicate; it need not obtain now to remain historically true. A generic prescription from a policy or another normative episteme does not by itself assert an individual commitment. Open that individual branch only when the sentence claims a duty of an actual System or separately governed party under A.2.8.
A change in any dimension is substantive. A plan does not become an actually obtaining relation because its date arrives; a later observation does not retroactively manufacture a missing relation; and stronger support does not substitute for the subject relation's own facts.
Choose one of four truthful exits
Choose by the kind of answer the receiving use needs:
- If one direct subject pattern or declaration defines the relation between the participants, use the direct relation exit.
- If the claim is only that one identified operation application used or returned one value, use the declaration-local
A.6.1binding exit. - If the question is production-work participation, entity inception, production completion, or another substrate-admitted local conjunction, use the local
A.15.PRODorA.6.RCDclaim exit. - If the attempted claim lacks the required basis, stop with the reason distinguished below. A known inapplicability result and missing constructor semantics also use this exit; neither is forced into a failed-fact result.
The exit determines the next action; it is not a fifth claim classification.
For the fourth exit, retain the distinction that determines the next move:
Factually unsupported: an applicable governor and sufficient case facts are available, but the test for the attempted polarity fails. An affirmative claim uses its positive test; a negative claim uses its negative or non-obtaining criterion or closure basis. Failure of one does not establish the other.Missing-information: a fact needed to decide the applicable test or its applicability is unavailable.Missing-governor: the required predicate, applicability condition, or occurrence rule is absent. Name the participants, affected use and missing rule; identify a future definition need only when one is identifiable.- Inapplicable under the named rule: available facts establish that the case is outside that rule's applicability. Return its inapplicable result, not a negative relation claim. Select another rule only when it governs the receiving question.
Missing-substrate: the proposed derivation needs constructor semantics that no current substrate supplies. Name that missing constructor basis under A.6.RCD:4.2; keep independently established base claims. This does not by itself justify a new relation kind.
These are reasons for withholding the attempted claim, not five truth values or new result kinds.
A positive direct-relation claim needs both a rule and case facts. The direct subject pattern or an applicable relation-declaration episteme supplies the admitted RelationKind, participant meanings, predicate, applicability and identity rule. Separate facts establish that the participants at the relevant extent satisfy that predicate. Within applicability, a failed positive test returns factually unsupported; an unavailable deciding fact returns missing-information; a case outside applicability retains the rule's inapplicable result. Reserve missing-governor for an absent governing rule. An additional published project declaration is unnecessary when the existing direct rule already supplies the needed meaning.
A governed negative sentence needs the analogous negative or non-obtaining criterion and separate facts satisfying it. Failure to support a positive claim, an absent record, or an unobserved event is not a negative premise.
A method-description field, planned filling, compatible type, stored reference, matching token or nearby record alone establishes no actual participant relation. Its content may make a claim or supply grounds; assess those under the direct predicate and establish the grounds for any reliance. Use A.10 when the source-to-use account is implicit or must remain replayable.
Ordinary sentence shapes
These informative shapes help draft an answer once its meaning is known. Include only distinctions needed by the receiving use. Direct-relation wording is an ordinary reading of an admitted RelationKind under its defining rule; an assertion id does not replace that rule. Current and historical claims need facts for their participants and extent, but the compact sentence need not repeat the supporting account.
For example, CF-17 was not consumed by W-204 does not follow merely because the positive consumption fact fails or is unavailable. It closes as a governed negative sentence only if the direct pattern or declaration for machining resource consumption supplies an applicable non-consumption criterion or complete closure basis for the quantity, work, and extent and separate case facts satisfy it. Otherwise the proposed positive claim remains factually unsupported or missing-information, or the relation question remains missing-governor, according to the independently recovered deficit.
A practitioner MAY retain the trigger word as optional Plain orientation after the direct sentence is recoverable. The direct sentence and its dimensions, not the familiar label or support state, carry the claim into planning, work, evaluation, delivery, acceptance, transfer, or receiving use.
Composition and universal-result stop
Invariant WMR-I1 — ontology economy. Recovering boundary wording does not introduce a universal input, result or handoff kind or relation; retain each recovered object and predicate under its own definition. Invariant WMR-I2 — transformation non-entailment. A plan, desired state, model, description, evaluation, publication or flow representation does not establish an actual transformation merely by its presence or label. Claims and evidence in that material can support a transformation judgement under A.3.4; shared time, Work or referent alone does not.
When the repaired claim depends on transformation composition, state its participants and question, then apply A.3.4 and the rule for that composition claim. Keep only the resulting independently identified transformations plus either one governed composition claim or the missing-governor or missing-substrate blocker. WMR does not restate or evaluate their contribution, compatibility, composition, or reidentification algorithm.
The blocker reaches only the composition-dependent claim; independent work, change, production, evaluation, delivery, acceptance, transfer, and receiving-use questions continue under their own governors.
Recognition and assurance remain separate
For ordinary recognition, the first three questions and one of four truthful exits are enough. Use the two assurance questions and explicit claim-dimension vocabulary only when they can change the answer or a named later use needs to inspect it.
A practitioner MAY open a separate assurance branch when the receiving use additionally needs evidence, warrant, assurance, gate, currentness, publication, or reliance. Apply the relevant evidence, assurance, gate, currentness, publication, or reliance check to the direct subject claim, A.6.1 application binding, local A.15.PROD or A.6.RCD claim, or non-assertability result together with its governor. Preserve the section 4.3 reasons and their different continuations. A missing subject rule may identify a future pattern or declaration need; unavailable constructor semantics retain their separate derivation question. Support or assurance changes neither polarity nor whether the subject relation obtains.
Recover a result and reuse its established meaning
Start with the receiving question: what may someone do because this result is available? Applying a description, accepting a produced entity, closing Work, and relying on a later effect need different answers. When the trigger is result, use the deciding fact before any catalogue:
- if the statement describes what successful enactment should obtain or preserve, use A.3.1 for the Method's intended effect, or A.15.2 for the particular WorkPlan's target;
- if the same entity continues and changed, recover that continuing entity and its separately governed change;
- if a condition continued to hold, state that condition over its required extent; attribute its maintenance to Work only through the applicable maintenance predicate and its facts;
- if an entity first began to exist, or that is the question, open A.15.PROD's entity-inception branch;
- if one operation application returned a value, state only its A.6.1 result binding;
- if the referent is a measured characteristic value, keep that value and its direct measurement relation; if it is a comparison, diagnosis, or evaluation claim, identify that C.2.1 episteme and its direct basis;
- if an entity was delivered or transferred, use the direct delivery or transfer occurrence;
- if the question concerns fulfilment of a promise, use A.2.3's specified outcome and acceptance conditions;
- if the claim is a downstream effect, apply the pattern whose Solution answers that effect-relation question;
- if
resultnames aC.11ChoiceResult, an acceptance verdict, a decision occurrence or record, or another value, entity, fact, or claim already identified under its applicable identity or occurrence rule, keep that kind and write only the direct relation current for this use.
If the selected reading lacks a deciding fact or governor, return its reason-specific non-assertability result. The word result does not establish one kind or relation family shared by these different readings. This does not prevent the same established meaning from recurring with different participants, including entities of different kinds.
Reuse the meaning, then obtain the facts of this case. A.15.PROD supplies one such repeated meaning: a produced result of Work is an entity that first exists through that Work's governed effects under its applicable identity specification. This is a readable summary of its local inception claim, not a new binary predicate. Keep the entity's own kind. A ship and an episteme use different identity specifications while instantiating this same production meaning. The Work, specification and applicability, first-existence boundary, and Work-to-change and change-to-identity grounds remain available in each claim. Use A.15.PROD:4.3–4.5 to obtain that answer; reusing its meaning does not supply a missing fact or subject rule.
The same discipline applies to other established relations. A.2.3:8.1 defines deliversPromisedOutcome(W, OS) and fulfilsPromiseContent(W, SC); the latter additionally tests acceptance. Their second participants are the OutcomeSpec and PromiseContent epistemes respectively, even when the promised condition concerns a physical entity. Substituting the affected thing for the specification changes the predicate. A Method's intended effect or a plan target does not by itself establish a promise or fulfilment. A.2.8 separately governs an individual duty.
For another occurrence of the same claim, retrieve its existing predicate or compound definition and retain its participant meanings, applicability and limits. Substitute the new participants and check their facts. A changed entity kind calls for the applicable identity or subject rule; it does not by itself call for a new result meaning. A different receiving question may require another relation even when the entity is unchanged.
When the same needed rule is repeatedly missing, use A.6.RCD:4.1–4.5. Reuse a direct predicate where one suffices; keep a one-use compound claim local; define a repeated compound rule once in its subject practice. Distinguish a law limited to one subject from a predicate definition reusable across subjects. The latter has the definition itself as its EntityOfConcern. Only a use that consumes the identity of an obtaining relation occurrence opens relation-kind admission. Neither repeated wording nor heterogeneous participants requires that additional ontology.
Keep useful preservation and later use visible. Work may achieve its intended benefit by keeping an existing condition within limits. A.3.1 supplies the Method's intended preserved condition. The subject rule and observations over the required interval decide whether that condition held; a further Work-to-maintenance claim needs its own applicable basis. Unchanged endpoints alone establish neither continuous preservation nor its attribution. A new object is unnecessary for this benefit. Performing Work alone does not establish a change of the referent whose condition was preserved.
Likewise, an existing description can be used in several later actions without being produced again. State what was used and how. A.6.1 can supply a binding when the receiving action is an application of that declared operation. A.6.RCD:4.5a supplies repeated formal rule-content derivation and criterion-selection semantics for exact ClaimGraphs; it does not assert consultation, Work use or causal benefit. Use the receiving subject's rule for those claims. If the rule is known but the use fact is unavailable, obtain that fact. If the required use meaning has no definition, develop that definition. Do not turn either gap into a claim that the existing result was useless.
Joint work and project results use the same subject meanings. For jointly necessary work parts, A.15.PROD:4.5 uses their independently established A.15.1 composite Work as identity-closing Work. A.15.6:4.1 adds the qualifications for an actual project. A plan, a shared document or several contributors does not establish either whole. Once the whole and its effects satisfy the production claim, its produced entity has the same result meaning as for another Work occurrence.
A supported part result can already be reported: “Within P, W1 obtained x under this rule.” That conjunction preserves the result and work parthood. To claim that P itself obtained x, closed its production, fulfilled its promise or caused a downstream effect, establish the grounds of that further claim at P's extent. Work composition supplies no universal rule for inheriting results or adding unlike measures. Preserve independently supported part results when the whole claim remains open.
The broader boundary-word palette below is an informative recognition aid. A row suggests a likely related object and candidate semantics; the result then leaves the palette for the direct governor. Several rows may apply to the same entity at different times or for different uses, and they remain separate claims.
When no direct governor closes a selected row, name the participants, proposed predicate and question, affected use, and absent definition, applicability, or occurrence rule. Name a future pattern or declaration need only when one is identifiable. A broader hypernym, another boundary word, or a new universal record does not settle the missing relation.
Work-name grounding by morphology and occurrence
An action nominal such as testing, assembly, maintenance, evaluation or inspection does not identify an occurrence by its morphology. Recover what it names under the applicable subject rule: for example, an admitted Method, a MethodDescription about that Method, a plan item, a required effect or a performed Work. Use A.6.F when function-like wording still hides its object or relation; that pattern distinguishes the transformation, structure, view, capability and other functional claims. A WBS element or Work Package ordinarily describes intended work; an actual occurrence needs its own basis.
A use that needs only the recovered method, method description, plan, structure, or other already governed value closes under that direct pattern. Only reliance on the label as one performed occurrence handles the candidate designation and required granularity under A.15.1.
For a deliberately asserted particular Work occurrence, recover its A.13 basis and apply A.15.1 independently. Use the established Work at the needed granularity, a supported neighboring object, or the stated blocker. A material workContinuityPolicyRef belongs to the A.15.1 identity judgement. If the sentence additionally attributes Work to an assignment, use F.6 with that same A.13 assignment; missing or contrary attribution facts alone do not erase independently admitted Work. Recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1. Apply F.18 only after the occurrence is established and needs a durable name.
Any output, result, outcome, production, delivery, or acceptance wording is a separate WMR claim only while its direct relation or claim dimensions remain hidden. Once readable, apply the rule for that relation or claim; it does not become part of work identity.
The preceding action-nominal classification is an FPF-scoped synthesis from recurring morphology-and-subject ambiguity, not a rule imported from PMI, PRINCE2, IDEF0, or IDEF3. A domain may conventionally use an action nominal as the durable name of an already grounded method, plan item, functional-view record, or dated work occurrence; that direct identity and predicate win over morphology. The synthesis reopens if repeated practice shows that the cue classifies a directly grounded value under the wrong predicate family, or if a trigger case cannot close through A.6.F, the subject predicate, or A.15.1 without new ontology.
Inspection contrast. inspection method names the way of doing. planned Pump-14 inspection work is intended-work content. Pump-14 inspection on 2026-07-15 09:10-09:34 becomes a performed occurrence only when applying A.15.1 establishes it at the required granularity; otherwise retain the lowered object or blocker. If the current question is whether the work first constituted an inspection-report episteme, apply A.15.PROD and use its local entity-identity-inception claim or branch blocker. A measured or diagnostic result uses its direct result rule, and a pass/fail verdict remains a separately governed evaluation-result episteme rather than the inspected entity or a downstream effect.
Archetypal Grounding
These constructed cases show different recovery branches. Their project declarations and case facts are supplied assumptions; local relation tokens do not thereby become FPF kinds. Section 5.1 shows both the ordinary result and the rule-and-fact comparison supporting it.
Inspection and machining: one ordinary result, one assurance replay
A source says, the inspection report is the result of inspection. First identify report episteme R-17 and ask what it is relative to. If inspection application P-17 returned R-17 under its declaration-local result predicate, write: Inspection application P-17 returned report R-17. If the current question is when exact Work first constituted the report, apply A.15.PROD. If neither relation is governed, return missing-governor naming R-17, the proposed application or Work participant, proposed predicate, affected use, and absent definition; name a future pattern or declaration need only when one is identifiable. Do not invent WorkResult.
Now a traveler says, raw stock WP-204 and cutting fluid CF-17 are inputs; the machined part and inspection report are outputs of machining. Machining Work W-204-MACHINE and continuing workpiece WP-204 are already identified. The ordinary result is:
Applying A.15.1 identifies W-204-MACHINE with affectedReferent WP-204.Cutting-fluid quantity CF-17 was consumed by W-204-MACHINE during I-204 under MachiningWorkConsumesResource.T-WP204-GEOMETRY is the bounded geometry change of continuing WP-204; W-204-MACHINE caused it under MachiningWorkCausesGeometryChange.
The workpiece remains WP-204, not a newly constituted output. A report binding or inception claim stays open until its own application or A.15.PROD basis is present. If the consumption fact fails, the proposed positive fluid claim is factually unsupported; if it is unavailable, return missing-information; if the relation governor is absent, return missing-governor and name the missing machining-resource predicate and its defining pattern or declaration.
A later measurement-result episteme R-204, diagnostic finding, evaluation verdict, or accepted-deliverable claim is a separately governed claim; delivery or physical transfer of continuing WP-204, and transfer or publication of R-204, are separate again. Shared chronology and one machining case entail none of them: each current claim needs its own direct governor and facts.
Case declaration and facts. Relation-declaration episteme MFG-WORK-REL-2026 contains the defining ClaimGraph for these case-local predicates:
Separate case facts establish that CF-17 was consumed by W-204-MACHINE during I-204 and that this Work caused T-WP204-GEOMETRY. Merely identifying the declaration, Work, transformation, chronology or assertion epistemes MFG-RU-CF17-W204 and MFG-WC-W204-TWP204 would not supply those facts. Assertion content and evidence can support them under the governing predicates. Comparing rule and case facts yields the ordinary sentences above and distinguishes the three failure reasons.
ETL data: direct participation, then a receiving-use stop
An ETL note says, RawOrders is the source input and WarehouseOrders is the delivered output. Work ETL_Nightly_0811 and both dataset entities under their admitted subject kinds are known. Relation-declaration episteme ETL-DATA-REL-2025 contains the defining ClaimGraph for SourceDatasetParticipatesInETLWork and DestinationDatasetParticipatesInETLWork; separate case facts say that RawOrders_0811 and WarehouseOrders_0811 satisfy the declared source-dataset and destination-dataset participant meanings and predicates for that job.
Write: RawOrders_0811 participated as the source dataset in ETL_Nightly_0811, and WarehouseOrders_0811 participated as the destination dataset in ETL_Nightly_0811. Those facts establish neither delivery nor use by analytics. If decision Work D-0811 is now claimed to use WarehouseOrders_0811 as a premise but no premise-use, reference-use, or application-binding governor is available, stop with missing-governor and name the missing analytics-decision predicate and receiving use. This case demonstrates a positive direct relation followed by a distinct blocked receiving use.
Before calling WarehouseOrders_0811 a new output, decide which dataset continues. If the ETL job updates the same dataset in place, identify that dataset's bounded change under A.3.4. If a derived dataset begins, apply its dataset-identity rule and use A.15.PROD only when the exact inception basis closes. When a catalog entry, lineage view, or publication is the source from which a reader reaches either dataset, use C.2.P to identify the exact source expression, source-to-use path, allowed use, and reopen condition. An E.17 face or form, or an E.24.PUB publication or availability occurrence, neither creates the dataset nor proves that analytics used it. Row-count, quality, latency, and drift results remain separate measurement or evaluation objects; each evaluation names its own criterion and predicate and cites the SubjectPatternLocator for their defining or constraining content.
Clinical work: administration is not a health outcome
A case note says, the patient and dose were inputs; the summary and good outcome were results. Clinical Work Appendectomy_Case_8472 has affected referent Patient_8472. Relation-declaration episteme MED-ADM-2026 defines ClinicalWorkAdministersDoseToPatient; the independent case fact states that this Work administered MedicineDose_8472 to Patient_8472 during the named interval, satisfying that predicate.
Write: Appendectomy_Case_8472 administered MedicineDose_8472 to Patient_8472 during the named interval. Keep DischargeSummary_8472 as an episteme whose binding or inception needs its own basis. First ask whether good outcome means a measured value, an evaluation verdict, a patient-state change, or an effect attributed to this Work. Keep that question open when the case does not select a reading. Once the claim is exact, apply its subject rule and distinguish an unknown fact, a failed criterion and an absent governor. Return missing-governor only for an absent rule. This case demonstrates a positive administration claim and a separately unresolved outcome claim.
Administration is only one possible relation for MedicineDose_8472. The same medicine quantity may instead be a constituent of an administered preparation or compound therapy, or a resource consumed by the clinical Work; each alternative needs its own exact direct governor and case fact, and the positive administration sentence proves neither. If a patient-state change is current, first identify that exact transformation under A.3.4. Then ask separately whether a declared work-to-patient-change predicate with the exact Work, transformation, applicability, and a satisfying case fact obtains. Administration alone proves neither the change nor that the clinical Work caused it.
Keep a measured value, diagnostic finding, evaluation verdict, and claimed health effect as four different objects or claims. A discharge summary may cite any of them without becoming them. Each current claim names its own participants, temporal extent, predicate, criterion when applicable, and the content that supplies that predicate or criterion; a measurement or diagnosis does not establish a verdict, and a verdict does not establish the patient's later health effect.
Pump 14: continuing entity and later decision use
A P2W note says, the pressure problem was the input, adjustment was the work, and restored pressure was the result. Keep accepted ProblemCard@Context PC-P14-PRESSURE as the separate problem-side object. Do not say that this accepted pressure-problem claim guided U.WorkPlan WP-P14-2026-07-15: the case supplies no direct relation for that use. Return missing-governor naming the ProblemCard and WorkPlan participants, proposed planning-use predicate, affected planning use, and absent definition; name a future declaration need only if one is identifiable. Do not infer that the problem caused W-P14-ADJUST-1010-1020. A.15.1 identifies that Work; A.3.4 identifies T-P14-PRESSURE-RISE as a bounded change of continuing HydraulicLoop_P14. Relation-declaration episteme P14-REL-2026 contains the defining ClaimGraph for AdjustmentWorkCausesPressureRise and MeasurementResultUsedByDecisionWork; separate case facts satisfy both predicates.
Keep four values separate: SetPointAdjustment@PlantOps-v3 is the selected U.Method; an A.3.2 U.MethodDescription has that admitted Method as its exact EntityOfConcern and makes a substantive claim about it as a way of doing; WP-P14-2026-07-15 states intended Work; and W-P14-ADJUST-1010-1020 is the dated Work occurrence. Naming any of them neither identifies an additional relation nor makes one obtain, so the unsupported ProblemCard-to-plan guidance claim remains missing-governor.
P14-REL-2026 is available in the current case record. Independently, a separately stipulated world-side fact satisfies its actual-causation predicate, so write: W-P14-ADJUST-1010-1020 caused T-P14-PRESSURE-RISE. In the explicitly earlier case record, P14-REL-2026 is absent; at that epistemic stage, keep that Work and transformation separate and return missing-governor naming both participants, the proposed causation predicate, the affected use, and the absent definition. No receiver or future declaration is required to state that blocker. Separately write: Decision Work D-P14 used measurement-result episteme MR-P14-AFTER as its declared basis. The loop continues; no entity begins, no production-completion criterion is current, and no transformation-composition claim follows. This case demonstrates work-caused change and later epistemic use without a production reading.
Hair styling: a changed referent and an unresolved configuration
A salon record says, hair and gel were inputs; the hairstyle, photo, and satisfaction were outputs. A.15.1 identifies styling Work W-STYLE-27 with affected referent Hair_27; A.3.4 identifies T-HAIR-27 as the arrangement change of that continuing hair. Relation-declaration episteme SALON-RESOURCE-USE-2026 contains the defining ClaimGraph for StylingWorkConsumesResource and StylingWorkCausesHairArrangementChange; separate case facts support the work-change claim and, when known, the gel-consumption claim.
Write: Applying A.15.1 identifies W-STYLE-27 with affectedReferent Hair_27, and W-STYLE-27 caused T-HAIR-27 under StylingWorkCausesHairArrangementChange. When the separate consumption fact is present, also write: W-STYLE-27 consumed StylingGel_27 under StylingWorkConsumesResource. Do not yet write EveningArrangement_27 is the resulting configuration: the case has not selected whether that name denotes an A.22 structure, a characteristic-state fact, a relation occurrence or a description episteme. Return the question of which subject and claim the receiving use needs, retaining the independently established hair change. Once that claim is recovered, apply its subject rule; distinguish a missing fact, a failed test and an absent governor. This case demonstrates a continuing changed entity and an unresolved configuration reading.
Client_27 is the person receiving the service; Hair_27 is the continuing affected referent. A hair-to-person part claim, a service-recipient claim, or a person-level effect claim needs its own exact direct governor and case fact; naming the client beside the hair establishes none of them. In this arrangement case, styling changes continuing Hair_27; the case supplies no new entity-identity inception. A separately individuated wig, extension, or other artifact may instead open its own identity-inception question under A.15.PROD when its identity rule and inception basis close.
For gel use, distinguish the three stops. With a current StylingWorkConsumesResource governor, a case fact that fails its predicate is factually unsupported, while an unavailable consumption fact is missing-information; an absent governing predicate or applicability condition is missing-governor. A method-description ingredient field or appointment-plan row substitutes for none of those bases. Photo_27 remains separately identified: its identity, photography or record-forming Work, representation of Hair_27, and publication are separate questions. A measured satisfaction response, an evaluation verdict, and any downstream effect of the service likewise require separate predicates and subject patterns; none constitutes the hairstyle or follows from the photo's presence alone. Its content may supply relevant observations, interpreted under the applicable subject rule.
Car 42: completion without inception
A finishing note says, the last nut was the input and completed Car 42 was the output. Car 42 already satisfies its identity rule before NutFasteningWork-42. Relation-declaration episteme CAR42-WORK-REL-2026 contains the defining ClaimGraph for FastenerParticipatesInFasteningWork and FasteningWorkCausesFastenerChange; separate case facts say that Nut-42-LAST participated and the Work caused the two independently identified fastening transformations.
Write: Nut-42-LAST participated in NutFasteningWork-42 under FastenerParticipatesInFasteningWork, and NutFasteningWork-42 caused the two named fastening transformations under FasteningWorkCausesFastenerChange. Do not open entity inception: the car continues.
For the narrowly bounded finishing use, NutFasteningWork-42 can be the whole Work selected by a local A.15.PROD production-work claim only when the fastening method's intended production effect and applicability, the exact work-to-change facts, and the current completion facts supply that narrow production basis. For the broader factory use, the same occurrence can be a proper operational part of CarProductionWork-42 only when an exact A.15.1 work-part relation obtains and the containing Work has its own separate production basis. Neither reading supplies the other, and neither proves that the two fastening transformations are parts of one composite transformation.
When completion is current, use completion-criterion episteme CAR-COMP-ED-42, its named applicability basis, exact boundary state, and production Work to ask A.15.PROD for the historically indexed completion claim. The suffix ED-42 and the criterion's publication establish no edition continuity. Assert a separate C.2.1 EpistemeEditionRelation only when its continuation predicate is established. Without that basis, retain the distinct criterion epistemes and leave continuity unresolved; a known non-continuing replacement may be stated on its own facts. If Car 42 had already completed earlier, classify the fastening separately as rework, repair, or maintenance. This case demonstrates completion distinct from inception and from automatic criterion lineage.
Production completion establishes neither delivery, acceptance, release, nor Car 42's present condition. Each current claim needs its own direct governor and facts.
Authoring: a produced explanation, its continuing use, and the next missing fact
An authoring note says, research notes were inputs; the draft was the output handed off to review. The reader needs to decide whether to review an available explanation, finish its construction, or recover a missing basis. This constructed case first obtains a positive answer through the existing suppliers, then changes one fact.
Identify what the author obtained. Under C.2.1, DraftEpisteme_31 has ClaimGraph G31, EntityOfConcern PreparationMethodProposal_31, and effective ReferenceScheme StudioPreparation-2026. G31 explains a proposed timing-correction procedure, its independently supplied error bound, and different limits for analysis and viewing. It is an episteme about a proposed way; writing it does not establish that the proposal is an identified Method or that a recording was edited.
If a later rendering leaves all three identity discriminators unchanged, keep DraftEpisteme_31 and state only the changed carrier, rendering, publication, evidence or transfer relation. If a discriminator changes, identify distinct LaterDraftEpisteme_31; assert EpistemeEditionRelation(DraftEpisteme_31, LaterDraftEpisteme_31) only when C.2.1's historical-continuation predicate obtains.
Obtain the production claim from A.15.PROD. In the positive case, an engineer's Work supplies the bounded technical argument and an author's Work connects that argument to the procedure and its uses. A.15.1 has independently established both occurrences, with their A.13 performer bases and enacted Methods, and their work-part relations to composite W-AUTHOR-31. The applicable authoring Method intends constitution of the complete explanation. The following is the case's supplied A.15.PROD basis, rather than an inference from the words draft output.
For this derivation, case substrate AuthoringInceptionClaims-31-v1 uses A.15.PROD:4.7's time-indexed conjunction of these named governed facts. It retains the Work parts and change witnesses, uses the supplied ordered candidate boundaries 10:00, 10:10, 10:20 and 10:30, and selects the first boundary satisfying all inception conditions. These are all content-constitution boundaries in the complete case history, not samples of an otherwise unobserved interval. That history makes the identity test false at the two earlier boundaries and true at 10:20. Unavailable premises remain undecided; their absence supplies no negative fact. The replay yields the local inception claim with EntityOfConcern = DraftEpisteme_31, indexed by the specification and applicability basis. These case declarations supply no universal authoring, change or result relation kind.
The useful sentence is now: “W-AUTHOR-31 jointly produced this explanation at 10:20; review its proposed procedure and stated limits.” Work continues until 10:30, so the inception result is not its completion claim. Production completion, acceptance and publication each retain their separate question.
This reuses the same production meaning as Ship 27 in A.15.PROD:5.2. There the produced participant is a U.System under an applicable hull-identity rule; here it is a U.Episteme under the applicable content-identity rule. In both cases, first existence through the governed effects of the identified Work is the result meaning. Neither the ship's hull rule nor the author's content rule is substituted for the other. The practitioner reuses A.15.PROD and the applicable subject definitions, rather than inventing a result predicate for each noun.
Remove one essential fact. Keep the two work identities, their composition, the observed manuscript change, the content-identity specification, its applicability and the first-satisfaction history. In this variant, the facts establishing which Work's editing operations targeted Manuscript_31 and effected those edits are unavailable. The definition of authoredContentChange remains known. The result is missing-information for W-AUTHOR-31's asserted link to ManuscriptContentChange_31. Recover that operation-and-target history before claiming production by this Work in the variant. The available explanation can still be reviewed on its content; the unresolved production attribution does not erase it. If the corresponding subject predicate had never been defined, the different result would be missing-governor; repeated authoring uses would justify developing that definition under A.6.RCD, not guessing the missing case fact.
Use the explanation outside its producing Work. Relation-declaration episteme AUTHORING-USE-REL-2026 supplies the already established source-premise and review-reference relations for this case. Its premise-use condition requires actual use of identified source claims in the Work's stated inference; its review-reference condition requires an actual bounded comparison using the identified reference content. Separate case facts support: Authoring Work W-AUTHOR-31 used SourceNotes_31 as a premise, and Review Work W-REVIEW-31 used DraftEpisteme_31 as a reference. The latter Work compares another proposal's viewing limit against G31's stated condition. It does not produce DraftEpisteme_31 again.
When only the content-basis question is current, A.6.RCD:4.5a's derivedUsingRuleContent or evaluatedAgainstRuleContent may already state it: name the exact dependent and base ClaimGraphs and the derivation or criterion-selection fact. Those predicates do not replace the separate Work-use claim above. The presence of a saved file, bibliography entry or handoff record alone supplies neither actual-use fact. Its content can supply a trace or other grounds for the actual-use claim. The next action after a missing reference-use fact is to recover the bounded comparison, not to assert that the reviewer benefited from receiving a file.
Continue a useful condition without replacing the result. A Method engineer can continue using that same explanation while its source-based qualification remains applicable. Suppose a source revision changes only the analysis limit. The applicable qualification rule requires the source argument, the selected use's limits and its dependencies to remain supported. The recovered dependency facts show that the viewing argument and its 8 ms condition are unchanged; the analysis claim depends on the revised argument. The engineer may continue the viewing use and return the analysis claim for requalification. A second description or a new production claim is unnecessary for that continuation.
Now remove the dependency information needed to bound the source change. Continued viewing use becomes unresolved too; absence of a visible edit cannot establish unaffectedness. Recover the affected dependencies or widen the recheck. This is a repeatable application of the qualification rule to a new situation. Claiming additionally that maintenance Work kept a condition true throughout an interval would require that Work's own predicate and interval facts. The useful preservation of an applicable result does not supply that further attribution.
Keep availability and transfer at their own scope. DraftFile_31 is a separately identified physical or digital entity whose actual state yields the selected expression, not DraftEpisteme_31. File inception and episteme inception are separate A.15.PROD questions. Rendering work or changed bits alone settles neither. When publication is current, occurrence PUB-31 obtains under E.24.PUB while its five fixed participants—the selected episteme edition, audience declaration, bounded-use declaration, independently identified expression and presentation carrier—satisfy its availability predicate. Together with the maximal continuous availability interval, they identify the occurrence. Any reusable form constrains the expression separately; broader availability can survive a changed expression or carrier under E.24.PUB:4.2.1. E.17 governs the multi-view face or form instead. The declaration-local phrase selected episteme edition creates no edition continuity.
Established availability lets the named audience obtain that content through that form and carrier. Actual access, delivery, acceptance, transfer, reliance and review use still need their own facts. If ordinary handed off wording already names one exact transfer relation, apply its direct pattern and stop. A package or handoff record alone establishes neither transfer nor receiving use; examine any asserted content and supporting facts under those relations' own rules. Apply E.10.MOVE only when the wording still hides an FPF-governed move, workflow, next action or readiness claim; its recovery creates none of those occurrences or permissions.
Bias-Annotation
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
- Practitioners retain short ordinary sentences while downstream users can recover the exact relation and its orthogonal claim dimensions.
- Method, plan, work, operation application, actual change, production, evaluation, delivery, acceptance, transfer, and receiving use remain independently inspectable.
- Local missing-governor blockers reveal where subject ontology is absent without forcing a new public kind.
- One compressed phrase may split into several claims; that is the cost of preserving different obtaining conditions and subject patterns.
Rationale
Boundary words describe a relation position only relative to an exact object. Treating them as entity kinds or universal relations erases the exact predicate, current facts, and subject assertion that determine obtaining. The three-question ordinary method restores the thing, related object, and direct verb or stop first; two conditional assurance questions expose claim dimensions and the formal predicate definition only when those distinctions can change or check the answer.
The worked-case relation tokens have meaning under their supplied project declarations. They neither add those kinds to FPF nor establish any occurrence by being named. Durable naming under F.18 follows recovery of the object and its identity basis.
Stop at the sufficient truthful result. Reuse a direct predicate when it answers the question; keep a compound claim local when no reusable definition is needed; develop such a definition only for its receiving uses. A missing rule remains a bounded definition question, rather than a reason to introduce a universal result relation.
SoTA-Echoing
These sources answer different practice questions. Provenance, metrology, and project-planning vocabularies expose useful distinctions and recurrent compression risks; none admits an FPF kind, makes a work or participant relation obtain, or replaces the three-question ordinary recovery and its two conditional assurance questions.
The three-question ordinary recovery, two conditional assurance questions, and four-exit architecture are an FPF-scoped synthesis hypothesis for one claim whose exact thing is known while its work or method boundary relation or one material claim distinction remains hidden. The cited traditions neither establish that architecture nor authorize it outside this boundary. The synthesis reopens if repeated subject practice yields a stable direct governor that replaces a branch, or if a trigger case cannot close through one of the four exits without new ontology.
For a practitioner encountering one of these standard vocabularies, the action is the same: preserve its bounded provenance, measurement, or planning meaning, then ask what thing is named, relative to what object, and what direct verb or stop is justified. Open the two assurance questions only when a material ambiguity or receiving use needs them. The standard term is evidence about likely interpretation, not the direct relation's governor.
Revisit the affected comparison when its source changes the relevant meaning: PMI activity, work-package, output, result or deliverable distinctions; an official PRINCE2 source proposed for a detailed planning claim; JCGM's measurement-result boundary; or provenance usage and generation semantics. Recheck the dependent adaptation rather than treating an unchanged source title as sufficient.
Relations
- Specializes:
A.6.Pfor the focused method-and-work boundary-word recovery case. - Entry condition: apply this pattern while a method-or-work boundary relation or a material claim dimension remains hidden. E.10 and E.10.ARCH can help locate that problem; they need not be reread when the object, direct relation and applicable rule are already clear.
- Uses:
A.6.RCDwhen participants are known but no direct relation closes the receiving claim;C.2.Pfor epistemic source expression and source-to-use recovery before the relation involving a Work occurrence is recovered. - Coordinates with:
A.3.1method identity and generic participant meanings;A.3.2method descriptions;A.6.1actual operation applications and declaration-local bindings;A.15.1dated work;A.15.2intended work and plans;A.15.3planned fillings;A.3.4actual bounded change; andA.15.PRODproduction-work, entity-identity-inception, and production-completion recovery. - Durable naming condition: apply
F.18only after the governed value from a direct subject relation,A.6.1application binding, or localA.15.PRODorA.6.RCDclaim, together with its receiving use, is recovered. The fourth family—a non-assertability result with its section 4.3 reason—does not authorize durable naming of the attempted relation.Missing-governornames a future pattern or declaration need only when one is identifiable;missing-substrateretains its separate constructor-semantics question. A durable performed-work name additionally requires theA.15.1occurrence basis. - Neighboring assertions: state the recovered measurement, evaluation, commitment, delivery, acceptance, transfer, resource, premise, source-use, Transformation, evidence, assurance, publication, gate, decision, or Work claim under its exact predicate; cite its
SubjectPatternLocatoronly when the locator is needed. - Boundary: A.6.P.WMR is the pattern for the recovery method and ordinary direct sentence. It does not define direct subject ontics, create the work occurrence, make an operation binding obtain, admit a relation kind, supply evidence or warrant, or decide downstream reliance.
A.6.P.WMR:End
Relation Claim Derivation and Relation-Kind Admission
Type: Kernel relation-foundation pattern Status: Stable Normativity: Normative unless marked informative
Plain name. Derive the needed relation claim before admitting a relation kind.
Use This When
Use this pattern when an engineer can name the participant referents and the claim, check, decision, or continuation that is blocked, but no current direct relation states the needed relation-bearing claim.
Typical first-minute situations are:
- several base-relation facts seem to imply the needed claim, but
related toor a convenient verb hides how; - a formula, query path, graph edge, or rule appears to define the answer, and the team is about to treat it as a relation kind;
- the same compound claim recurs and the team needs to decide whether to keep deriving it locally, publish reusable predicate semantics, or admit a relation kind;
- a proposed primitive relation appears to be only a composition, projection, closure, aggregation, or cross-algebra juxtaposition of existing claims.
Primary EntityOfConcern. One needed relation-bearing claim for one named receiving use. The application also settles whether that claim remains local, receives a reusable predicate-definition episteme, or justifies a derived or primitive relation kind.
First useful move. Write the blocked receiving use and the participant meanings in ordinary domain language. Then use A.6.P to recover the pattern containing the current subject predicate and ask whether that predicate can already state the needed affirmative, negative, or rule-qualified modal claim for those participants. If it can, apply its test and use the blocker boundary below when the result cannot yet be stated. Derive a compound predicate only when no current direct predicate can express the needed claim.
What goes wrong if missed. A team either leaves the claim as vague connective prose or promotes a formula, query, graph path, definition, or convenient name into ontology. The first loses replayable meaning. The second invents relation kinds without an obtaining law or occurrence identity.
What this buys. The engineer gets the lightest sufficient result: an existing direct relation, a local compound claim, reusable predicate-definition content with an optional separately admitted derived relation kind, or an irreducible primitive relation kind. The ontology grows only when the receiving use needs occurrence semantics that claim content alone cannot supply.
Ordinary non-use boundary. Do not use this pattern when a current direct predicate can already state the needed affirmative, negative, or rule-qualified modal claim; write that claim using the predicate's pattern and stop. A negative, hypothetical, forecast, or rule-qualified modal claim needs no obtaining relation occurrence. If the predicate and its applicability rule exist but the attempted positive result cannot be stated, use the three-way boundary below: factually unsupported only when the available case basis is sufficient to apply the positive test and that test fails; missing-information when a fact needed to decide that test is unavailable. Do not use A.6.RCD for wording-only cleanup, mathematical-lens adequacy, naming, evidence, assurance, or publication questions. E.10, C.29, F.18, A.10, B.3, and E.17 supply the relevant definitions or tests.
Cheap stop. If a readable current direct relation closes the receiving use, stop before constructing a compound claim. If a local compound claim closes it, stop before publishing a reusable definition. If a reusable definition closes it, stop before admitting a relation kind.
Name the blocker
Use three ordinary blocker phrases without turning them into a common result kind:
missing-governormeans that, for the stated participants and use, no current predicate definition, applicability condition, occurrence rule, or other governing rule can state or test the attempted relation claim. It says nothing about whether case facts exist.factually unsupportedmeans that the required governor and positive test exist, the available case basis is sufficient to apply that test, and the test fails. It stops the attempted affirmative; it does not establish the negative.missing-informationmeans that at least one fact needed to decide the current test is unavailable, so the test cannot yet return its positive, negative, or inapplicable result.
If an applicability rule exists and the available case basis establishes that the case is outside it, return that rule's inapplicable result. State a negative claim only when an applicable non-obtaining criterion or complete closure basis exists and the available facts satisfy it; failure of the positive test alone is not that basis. If the governing rule itself is absent, use missing-governor; if a fact needed to decide its test is unavailable, use missing-information. missing-substrate remains the narrower section 4.2 stop for unavailable constructor semantics. These phrases are readable outcomes, not new U-kinds, result records, or an omnibus blocker ontology.
Problem Frame
FPF permits rich claims over already identified entities and admitted relations without requiring one primitive relation kind for every useful sentence. The difficult case begins after relational precision restoration: the participants are recoverable, the receiving use is real, and simpler direct relations exist, but no one current direct relation carries the needed claim.
The ordinary result of this pattern is claim content in a C.2.1 episteme. Deriving that content is not the constitution of an actual relation occurrence. A receiving use that needs one stable rule definition can justify that content, including for anticipated reuse. Only a further occurrence-semantics need can justify a derived relation kind, and only irreducible action-facing semantics can justify a primitive relation kind.
Problem
Two errors compete.
- Under-definition.
Related to,fulfils,enacts,reachable,supports, or another convenient phrase hides the base facts, participant meanings, polarity, intermediate participants, applicability, or rule by which the claim follows. - Premature admission. A repeated expression, formula, query, graph path, table row, definition, or name is treated as a relation kind or relation occurrence although no direct subject settlement states obtaining and occurrence identity.
Authors MUST preserve expressive claims while preventing representation-created ontology and primitive-kind inflation.
Forces
Solution
Name the blocked receiving claim and participants. Reuse a current direct predicate when it can state that claim. Derive only what the selected substrate warrants. Identify reusable predicate semantics when a receiving use needs a stable rule definition, including anticipated reuse. Admit a relation kind only with its direct obtaining and occurrence-identity laws. Stop when the receiving use works.
Execute the demand-first method
- Name the blocked use. State the claim, check, decision, or continuation that cannot proceed, and what answer would close it.
- Recover participants and direct relations. Use
A.6.Pto name the participant referents under their relation-participant meanings and retrieve the smallest plausible base from the pattern content or declaration that defines each base predicate and its obtaining law. Similar tokens, shared field names, or adjacent graph edges are not a base. - Choose the least constructor admitted by the current substrate. State the constructor semantics and the base claim content it consumes. Do not infer an operator from punctuation or notation.
- Check the derivation and its use. Establish that the base claims and selected constructor support the required result and that it answers the named receiving use. Reuse an adequate existing proof or check; add positive or discriminating cases when needed to establish or explain applicability or failure. Keep hidden intermediates, polarity, scope, time, and base-definition editions visible when they change the result.
- Select the lightest disposition. Choose exactly one of the four dispositions in section 4.3 and stop at its stopping rule.
- Open reusable semantics when the receiving use needs one stable definition. This can support planned reuse or a reference to the rule; previously observed repetition is unnecessary. Decide whether the rule concerns one subject or is parameterized across subject instances. For one subject, identify a subject-bounded compound-law episteme whose EntityOfConcern is that subject and state the reuse limit. Across subjects, identify the reusable predicate definition itself as EntityOfConcern; that episteme may satisfy A.6.0 U.Signature membership before relation-kind admission, but it is not a RelationSignature.
- Open kind admission only when occurrence semantics are consumed. A derived kind needs a direct subject settlement with obtaining, applicability, base dependencies, and a non-optional occurrence-identity rule. A primitive candidate additionally carries the failed derivation, the action-facing distinction lost, its own obtaining and recurrence laws, independent receiving uses, and a standalone subject-pattern obligation.
When a separate note helps the live decision, use the applicable prompts below:
The note is a pattern-local prompt. A filled, claim-bearing use is an episteme under C.2.1; the printed shape is not a new record kind, RelationSignature, relation kind, or relation occurrence.
Respect substrate authority
A constructor probe is usable only when the selected substrate defines its inputs, output claim, applicability, and relevant laws. The following table is a non-exhaustive set of recurring single-substrate semantic probes. It is neither a universal operator registry nor a claim that any substrate supports the whole list.
Cross-algebra claim-use boundary. First distinguish a relation between claim contents from an assertion about their actual use. A local content derivation or the applicable rule-content predicate in §4.5a can answer the former without inventing Work. When the sentence asserts that a particular decision or Work used a result, establish its premise-use, reference-use, decision-use or other direct predicate and facts. An actual application of a declared operation may instead use its A.6.1 argument binding. Return missing-governor for an absent use rule, factually unsupported for sufficient facts that fail its test, or missing-information for an unavailable deciding fact. Co-publication, a shared topic or the mere presence of one decision record establishes no use relation; its content may supply an assertion or supporting trace.
Stop there when those independent uses close the named decision or work question. Open a separate joint predicate only when the decision depends on a joint condition that the independent use relations cannot express; then name that condition and use A.6.RCD to derive exactly it. Do not add a generic joint-use relation or record merely because one decision cites results from two algebras.
When a consumed result relies on an obtaining F.9 Bridge between two exact F.17 SchemeSenseCell values, cite that Bridge and the separate bounded-use claim; add CL or a loss note only when the receiving use needs it. When the result instead crosses exact ReferencePlanes, cite the applicable plane relation and policy. If both facts are current, state both under their own predicates. A cell or plane difference alone creates neither relation, and one branch never fabricates the other. A Bridge-related penalty is current only when a named B.3 assurance claim uses an applicable declared domain model, calibrated mappings where needed, stated dependencies and assumptions, and current case facts whose rule yields that penalty. It affects only the calculated assurance result for that named use; it supplies no default fold and changes no independently stated characteristic.
A local compound claim needs recoverable constructor semantics, but it does not need a separately materialized substrate document. Authors MUST name and pin the substrate when the derivation is nontrivial, intended for interoperability, used as proof, or becomes a reusable predicate definition. If no current substrate supplies the proposed operator, return a missing-substrate blocker rather than improvising a universal constructor algebra.
Select one of four dispositions
These are economy dispositions, not maturity stages. Later need can reopen a local claim or definition.
Keep kinds, predicates, claims, and occurrences distinct
The admitted relation kind classifies occurrences; its direct predicate states their obtaining condition. The subject facts or constituting history determine whether the relation obtains. A claim-bearing episteme asserts affirmative, negative or rule-qualified modal content about that relation. Available evidence supports, refutes or leaves that assertion unresolved; lack of a deciding fact does not itself settle obtaining. Apply §0.1 to the unresolved claim, and use A.6.REL when the receiving use needs explicit occurrence identity.
Settle a reusable predicate definition
When a receiving use needs a stable rule definition, establish its intended reuse boundary before publishing it.
- One subject. If every use asks about the same promise-content edition, subject structure, decision occurrence, or other subject, identify a subject-bounded compound-law episteme whose
EntityOfConcernis that subject. State plainly that the rule may be reused only for claims about that subject; a familiar formula does not make it portable to another subject. - Across subject instances. If the same parameterized rule is intended to apply across independently identified subject instances, identify one reusable predicate-definition episteme whose
EntityOfConcernis the predicate definition itself. If its claim graph supplies the subject and value range, Vocabulary, Laws, and Applicability required by A.6.0, the already identified episteme may satisfyU.Signaturemembership without relation-kind admission. It remains a predicate-definition declaration, not aRelationSignatureor a classifier of occurrences.
In either branch, the definition content states:
- parameter and participant meanings;
- the base-relation claims and the pattern content or declarations that define their predicates and obtaining laws;
- the derivation rule under the selected substrate;
- claim polarity and applicability, with any scope or time arguments the rule consumes;
- base-definition and substrate dependencies plus their editions when current;
- justification of the derived rule and its applicability, with cases where needed to expose a deciding condition;
- the admissible claim use, plus a restriction on occurrence or ontology inference only when F.19's independent-ground, plausible-reader and consequence test warrants it.
If neither the subject nor the reusable predicate definition is the EntityOfConcern, keep the needed results as local compound claims. Do not manufacture a union concern or alternate opportunistically between the rule and a nearby domain subject.
Reusable rule-content predicates stop before relation-kind admission
RuleContentBasisFindingDefinition@R7 is the disposition-3 declaration for two repeated cross-subject predicate semantics: derivedUsingRuleContent(dependentContent, baseContent) and evaluatedAgainstRuleContent(dependentContent, baseContent). Its EntityOfConcern is that reusable predicate definition. Its SubjectKind and RangedValueKind are both NonemptyClaimContent under C.2.1:4.1.2; satisfaction of either predicate is asserted in a C.2.1 episteme, so no separate result kind is introduced. The declaration may satisfy ordinary A.6.0 U.Signature membership. It is not a RelationSignature, relation kind, relation occurrence, registry, or claim that every definition or constraint was actually used.
Use the first predicate only when an identified derivation claim names the nonempty base subgraph as a formal premise under a declared inference rule or application producing the dependent content. Use the second only when an identified criterion-selection claim selects that base for a bounded evaluation claim concerning the dependent content. The dependent and base values are predicate parameters, not A.6.5 SlotSpecs. Assertions of these predicates remain ordinary C.2.1 epistemes; consultation, influence, provenance, evidence, evaluation Work, and later sufficiency remain separate.
Reuse the lightest sufficient branch. A subject-local assertion that names its defining or constraining ClaimGraph and closes the use stops at disposition 1 or 2. Use the R7 definition when its parameterized rule-content semantics answer the receiving question; there need not already be several observed applications. Open a basis analysis only for a named comparison, replay, conflict or reliance use. Stop at predicate-definition content unless a receiving use needs an obtaining occurrence as a participant, comparison object or otherwise identified relation.
Prepare derived or primitive relation-kind admission only with occurrence semantics
When a named use consumes occurrence semantics, A.6.RCD yields a relation-kind candidate and the settlement material needed for admission: a derived-kind candidate plus its proposed direct subject settlement, or a primitive-kind candidate plus its candidate standalone subject pattern. Apply the admission predicates defined in E.24 and E.24.UK, and the parsimony predicate in A.11 when that question is current. Neither a proposed settlement nor a candidate pattern locator admits the kind. For a candidate that is admitted, the resulting direct subject settlement states:
- the classified relation occurrences and participant meanings;
- the obtaining predicate and applicability;
- for a derived kind, the derivation law and base-definition dependencies;
- a direct occurrence-identity rule for identification and reidentification, including repeated occurrences when possible;
- recurrence, cessation, and continuation conditions when those distinctions matter;
- at least one named receiving use that consumes occurrence semantics;
- the standalone subject pattern.
An admitted relation kind never has identity intentionally absent. Ordinary use can omit explicit individuation, occurrence records, and designators because no named use consumes them; the direct identity rule still exists.
A pure converse preserves one base occurrence only when the direct subject ontology explicitly says that inverse wording concerns the same occurrence. Restriction, projection, composition, closure, aggregation, and hidden intermediates require an explicit identity decision. Their syntax does not decide whether the derived occurrence inherits one base identity, is constituted as a composite occurrence, or has a new direct identity rule. If no truthful rule is available, remain at local-claim or predicate-definition level.
Before relation-kind admission, authors MAY ask A.6.0 whether a reusable predicate-definition episteme satisfies ordinary U.Signature membership. That declaration's EntityOfConcern is the predicate definition, not a candidate relation kind, and the result neither classifies occurrences nor admits a kind.
Authors MAY publish under A.6.0 a RelationSignature whose EntityOfConcern is a relation kind only after that kind is admitted. The RelationSignature declares reusable SlotSpecs and restates the direct laws; it does not admit the kind or make an occurrence obtain.
Separate recognition from assurance
Recognition branch for ordinary receiving use. Ask only:
- What receiving claim or action is blocked?
- Who or what are the participants, and under which meanings?
- Does one current direct predicate already state the needed affirmative, negative, or rule-qualified modal claim?
- If not, what smallest substrate-admitted compound claim answers it?
- Which of the four dispositions lets the receiving use proceed now?
The ordinary branch can stop at a readable direct claim or one readable compound claim. It does not require a named substrate document, predicate-definition publication, new relation kind, signature, explicit occurrence, or designator when the receiving use consumes none of them.
Negative direct-claim case. A staffing check asks whether Robot_7 is assigned as InspectorSystemRole for Cell_3 during Interval_T under the declared CellInspectorAssignment species of U.SystemRoleAssignment. The species is the relation kind, not an assignment occurrence. A.2.1 and the species definition supply participant meanings and the positive predicate for the holder, cell and interval; taxonomy and reference scheme are not participants. When an applicable non-assignment criterion or complete closure basis is satisfied, a C.2.1 episteme can state the negative and disposition 1 closes the check without individuating an obtaining assignment. An absent direct predicate, applicability condition or required occurrence rule yields missing-governor; sufficient case facts that fail the positive test yield factually unsupported; an unavailable deciding fact yields missing-information. Neither a failed positive test nor a blocker supplies negative polarity by itself.
Check a compound claim or proposed definition. DPF and FPF authors verify the applicable grounds below when authoring a compound claim, reusable predicate definition, or relation-kind admission candidate, including a durable local compound claim that stops at disposition 2:
- exact base patterns, definitions, editions, and applicability;
- selected substrate and constructor semantics;
- the derivation's validity and receiving-use result, with positive or discriminating cases when needed to settle a consequential condition;
- one truthful definition
EntityOfConcernwhen reusable semantics are published; - dependency and currentness conditions;
- direct occurrence-identity and recurrence rules for every admitted relation kind;
- the representation conventions needed to recover the derivation, with C.29 only for a separate mathematical representation or transfer question;
- naming only after the definition episteme, kind, or occurrence is settled;
- A.10 when evidence reliance is claimed, B.3 for an assurance claim, A.21 for a gate result, and C.11 or the direct decision pattern for a decision result.
Passing the assurance branch does not make evidence constitutive of relation obtaining. It makes the derivation and admission decision replayable for the declared use.
Stop and return
Stop at the first disposition that closes the named receiving use. Use this pattern when:
- a relied-on base relation or predicate definition changes;
- the selected substrate edition or constructor semantics changes;
- applicability, polarity, participant meaning, scope, time, or hidden-intermediate policy changes;
- the derivation becomes unreadable, computationally unsuitable, or unable to interoperate for the declared use;
- a receiving use begins to need one stable definition or explicit occurrence identity;
- a purported primitive gains an accepted lossless derivation, or a derived kind loses a truthful identity rule.
G.11 supplies currentness, dependency closure, and scoped refresh when a relied-on base definition, substrate edition, or applicability settlement changes. Re-evaluate only affected claims and dependent kinds; do not rebuild a global relation registry.
Archetypal Grounding — Worked Cases
Promise-content fulfilment: use the existing direct A.2.3 predicate
Situation. PromiseContent_Housing42_v3 says that housing Housing_42 must be delivered to AssemblyCell_B during Interval_42, satisfy OutcomeSpec_Housing42_v3, and satisfy the acceptance predicate in AcceptanceSpec_Housing42_v3. The delivery work is the independently identified U.Work occurrence Work_DeliverHousing42; it is not the delivered entity, the post-delivery state, the evaluation, or the acceptance result.
A.2.3 predicate and required subset. A.2.3 already supplies the direct predicate fulfilsPromiseContent(W, SC), so disposition 1 is available. For this promise-content edition, the necessary and sufficient world-side subset is:
PromiseContentUse(Work_DeliverHousing42, PromiseContent_Housing42_v3, Interval_42)obtains;PromisedOutcomeDeliveryRelation(Work_DeliverHousing42, OutcomeSpec_Housing42_v3)obtains because the selected work facts, delivered entityHousing_42, and its post-delivery state satisfy that OutcomeSpec; and- the acceptance predicate in
AcceptanceSpec_Housing42_v3is satisfied for those facts and states.
No production or entity-inception claim is current because Housing_42 already existed before this delivery work. This edition requires no additional generic transfer or institutional-acceptance relation beyond the two A.2.3 relations and its acceptance predicate. If another edition requires one, it must name that direct relation and its participants rather than adding a delivery work bundle.
Evaluation, result, and evidence. Separate evaluation work Work_InspectHousing42 applies the declared acceptance method. Its exact operation-result binding carries the verdict value; optional episteme InspectionVerdict_Housing42 states that evaluation result. An A.10 evidence-use relation may support reliance on the affirmative fulfilment assertion. The evaluation work, result binding, verdict episteme, and evidence-use relation neither become parts of Work_DeliverHousing42 nor make PromiseContentFulfilmentRelation obtain. The three world-side conditions above make the direct relation obtain; evaluation and evidence only support an assertion about it.
Positive case. All three required conditions above are satisfied, so the direct predicate is satisfied and a claim-bearing episteme may state fulfilsPromiseContent(Work_DeliverHousing42, PromiseContent_Housing42_v3) without creating the occurrence.
Discriminating failures. Work_DeliverHousing42 can occur and Housing_42 can be in the target post-state while PromiseContentUse is absent or concerns another promise edition; then PromisedOutcomeDeliveryRelation for this promised outcome does not obtain and the promise is not fulfilled. Or the delivery relation can obtain while one acceptance condition is false; an accepted label or report cannot repair that failure. Missing evidence leaves reliance on the assertion unresolved; it creates neither fulfilment nor non-fulfilment.
Disposition and stop. Stop at disposition 1 under A.2.3. No new compound-law episteme, predicate definition, relation kind, or RelationSignature is needed. Use A.6.REL if a later use must identify or reidentify this fulfilment, distinguish it from another occurrence, refer to it or use it as a participant.
System-role assignment and performed Work: recover A.13 and A.15.1 first, then use F.6 directly when attribution is current
Situation. A work record needs the readable claim that one system performed one Work occurrence under one assignment to a system role.
Base and direct result. Recover S : U.System as the performer through A.13 and let A.15.1 independently admit W : U.Work. When the work record expressly needs the under-assignment claim, reuse the same obtaining A.13 assignment RA, apply F.6 to the direct predicate performedUnderAssignment(W, RA), and compare RA.HolderSystemSlot with the already recovered S. F.6 identifies neither assignment nor performer. A C.2.1 episteme may assert that result for the receiving use. The system performs the Work; the assignment supplies its holder and assigned-kind projection but neither acts nor creates another participation relation. If an F.6 deciding fact is unavailable, attribution remains unresolved; contrary facts refute it. In either case, withhold the under-assignment assertion. Retain the Work while its independent admission grounds hold; recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1.
Positive case. A.13 has already recovered S through the same obtaining RA, A.15.1 has independently admitted W, RA covers W, RA.HolderSystemSlot = S, and F.6's direct Work-attribution predicate holds for the pair. The readable result is “S performed W under RA.” No generic enactment object is needed.
Discriminating failure. The assignment obtains, but another system performs the Work, or S performs Work outside the assignment's extent. Assignment plus nearby Work is insufficient; capability, responsibility, authority, and a result also remain separate claims.
Disposition and stop. Stop at disposition 1 under A.2.1 and F.6. Admit no RoleEnactment kind, compound relation, occurrence, or RelationSignature. If a later use needs another participation or functioning relation in addition to Work attribution, name its direct predicate or return that missing governor instead of generalizing from enacted.
Supply-chain reachability: subject-bounded query or reusable predicate definition
Situation. One planner asks whether Supplier_A can reach Plant_B inside SupplyNetwork_North_2026. Other planners want the same directed-reachability rule for independently identified supply-network structures.
Base and derivation. Name the direct edge-relation kinds, direction, structure parameter, source and target parameters, path or closure rule, zero-length and cycle policies, applicability, and edge-definition editions. A one-off answer is a local compound claim. Repeated queries only about SupplyNetwork_North_2026 may use a subject-bounded compound-law episteme whose EntityOfConcern is that structure and whose reuse boundary excludes other structures. When the same parameterized rule is reused across independently identified structures, publish DirectedReachabilityPredicate_v1 as a predicate-definition episteme whose EntityOfConcern is that reusable definition. If its claim graph supplies A.6.0's subject and value range, Vocabulary, Laws, and Applicability, it may independently satisfy ordinary U.Signature membership without becoming a RelationSignature.
Positive case. A path exists whose every edge is an obtaining occurrence of the admitted base relation under the selected structure and closure rule.
Discriminating failure. A graph representation contains a visual or stored path, but one edge points in the wrong direction, denotes a different base relation, or belongs to a superseded structure edition. Representation connectivity therefore does not satisfy the reachability predicate.
Disposition and stop. The one-off query stops at disposition 2. Repeated use confined to one structure stops at disposition 3's subject-bounded branch. Cross-structure reuse stops at disposition 3's reusable predicate-definition branch and may add ordinary A.6.0 U.Signature membership. If a subject practice later needs reachability occurrences with action-facing identity, recurrence, continuation, or participation in another relation, the A.6.RCD application records a derived reachability-kind candidate plus a proposed direct subject settlement; apply the E.24 and E.24.UK admission tests and the A.11 parsimony test when current. Create a RelationSignature only for an admitted relation kind. Path identity, query-result-row identity, predicate-definition identity, subject-structure identity, and relation-occurrence identity are not interchangeable.
Formal and probabilistic result use: preserve separate algebras
Situation. One engineering decision-work occurrence consumes one formal result episteme and one probabilistic result episteme.
Base and derivation. Keep the formal result in its formal substrate and the probabilistic result in its probability substrate. State the two result-use assertions under their predicates in one C.2.1 episteme whose EntityOfConcern is the engineering decision-work occurrence. The formal and probabilistic result epistemes remain distinct used results; neither their pair nor a union of nearby objects replaces that concern.
No F.9 Bridge is needed for this case as stated: the two result epistemes enter the decision through separate direct use relations, and no obtaining relation between two exact F.17 cells is claimed. No ReferencePlane crossing is claimed either, so no plane relation or policy is added. Either fact could later become current without creating the other.
Positive case. Both direct use relations obtain for the decision-work occurrence under their own applicability, so the decision rationale can cite each result for its admitted use.
Discriminating failure. The two results are co-published or mention the same subject, but the decision work has no current direct use relation to one of them. Shared carrier, topic, or notation does not establish decision use.
Disposition and stop. The apparent combined need decomposes into two independently stated receiving claims. Each closes under disposition 1 with its direct decision-use relation. Do not publish a cross-algebra conjunction predicate merely to join the sentences, and do not infer one composite relation occurrence from a decision record.
Primitive-candidate stop test
A subject practice proposes a primitive relation because all accepted bases preserve co-occurrence and shared participants but lose one independently used subject distinction. The candidate advances only when the subject can name that lost distinction, show a positive and discriminating case, state its own obtaining and recurrence laws, distinguish repeated occurrences, and identify independent receiving uses. If any item is missing, the result is a local claim, reusable predicate definition, or blocker. This is disposition 4's positive test, not a license to mint a placeholder relation.
Bias-Annotation
This pattern corrects primitive-kind bias: a useful repeated phrase or representation can look ontologically important before its claim and occurrence semantics are recovered. It also corrects false-parsimony bias: if every accepted derivation loses a distinction that changes real work and the subject supplies its own obtaining and identity laws, refusing the primitive would hide needed ontology.
The formal examples can bias authors toward syntax-first reasoning. The method therefore begins from the blocked receiving use, direct participants, and direct relations. The ordinary branch stays readable; formal apparatus appears only when it changes replay, reuse, proof, interoperability, or admission.
Conformance Checklist
- Blocked use. The claim, check, decision, or continuation under repair is named.
- Participants first. Referents and relation-participant meanings are recovered before constructor or notation choice.
- Direct-predicate stop.
A.6.Precovers the current subject predicate before compound derivation begins. If that predicate can state the needed affirmative, negative, or rule-qualified modal claim, use it and stop. If no needed predicate, applicability condition, or occurrence rule exists, returnmissing-governor; if the governor exists and the available case basis is sufficient to apply its positive test but that test fails, returnfactually unsupported; if a fact needed to decide the test is unavailable, returnmissing-information. A negative additionally needs an applicable non-obtaining criterion or complete closure basis and facts that satisfy it. - Base. Every base predicate names the pattern content or declaration that defines it and its obtaining law. The current case separately supplies the relevant facts or constituting history; an assertion or representation does not turn that rule into an obtaining occurrence.
- Substrate authority. Every used constructor has semantics in the selected substrate; nontrivial, interoperable, proof-bearing, or reusable derivation pins the substrate and edition.
- Derivation and use. The selected constructor and base claims support the result required by the receiving use. Existing proof or verification may suffice; positive or discriminating cases are added where needed to establish or explain a consequential condition.
- Lightest disposition. Exactly one of the four dispositions closes the current use; later branches are not opened by habit.
- Claim polarity and occurrence boundary. Direct and compound assertions may be affirmative, negative, or rule-qualified modal claims. The subject predicate defines the test, current case facts or constituting history determine its satisfaction, and the assertion states the result without creating an occurrence. The three blocker phrases in section 0.1 remain distinct and are not predicate values. Use A.6.REL only when a satisfied affirmative case has an occurrence whose identity a named use consumes.
- Definition identity and reuse boundary. A subject-bounded compound-law episteme names the subject as its
EntityOfConcernand states that reuse does not travel to another subject. A reusable predicate-definition episteme names the reusable predicate definition as itsEntityOfConcern. Both state applicability and visible base dependencies. - Definition/signature boundary. A reusable predicate-definition episteme may satisfy ordinary A.6.0
U.Signaturemembership before relation-kind admission. It is not aRelationSignature, does not classify relation occurrences, and does not make one obtain. - Derived-kind candidate and admission. When a named use needs stable occurrence semantics, the A.6.RCD application records a derived-kind candidate plus a proposed direct subject settlement covering derivation and dependencies, obtaining, applicability, recurrence where current, and a direct occurrence-identity rule. Apply the admission predicates defined in
E.24andE.24.UK, and the parsimony predicate inA.11when current. Neither the proposal nor aSubjectPatternLocatoradmits the kind. Only an admitted relation kind proceeds to an A.6.0RelationSignature; ordinaryU.Signaturemembership of a predicate-definition episteme is independent of that branch. - Primitive-kind settlement. A primitive candidate records the failed derivation, action-facing loss, independent uses, own obtaining and identity laws, and standalone direct pattern before A.11/E.24/E.24.UK admission can pass.
- Identity never absent. Explicit individuation can be omitted from ordinary use; an admitted relation kind's identity rule cannot.
- Representation boundary. Formula, query, graph, tree, path, diagram, row, and name remain representations or designators connected to independently recovered content.
- Neighboring claims. Apply A.10 when the evidence source-to-use account is implicit or must remain replayable, B.3 for assurance, A.21 for gates, A.15 for work, C.11 or the decision pattern for decisions, E.24.PUB for publication availability and identity, E.17 when a reader-facing form is needed, F.18 for naming, and G.11 for currentness.
- Stop or return. The result states the current stop and the dependency or use change that would reopen it.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits. FPF can state many compound claims without multiplying primitive relation kinds. Repeated subject semantics become reusable without confusing a definition with ontology. When occurrence semantics matter, derived and primitive relation kinds enter with direct obtaining and identity laws rather than with syntax or names.
Costs. Authors MUST expose base dependencies and substrate semantics for nontrivial reuse. Authors of a direct subject pattern MUST supply the additional settlement content required by section 4.6 before a relation kind is admitted. Some familiar relation words remain local claims or blockers.
Boundary. This pattern reduces public primitive kinds and duplicate declarations; it does not reduce the number of true compound claims or obtaining base-relation facts.
Rationale
Claim composition and relation-kind admission answer different engineering questions. A claim asks whether a predicate, possibly built from admitted base predicates, is satisfied for named referents. A relation kind classifies obtaining occurrences and therefore needs a rule for reidentifying those occurrences. Repetition of the first question can justify publication of the predicate rule; it does not answer the second.
The demand-first order is asymmetric. An adequate existing direct predicate avoids a new derivation because its definition already supplies the needed meaning. Local compound claims preserve expressive reach without public ontology cost. Predicate-definition epistemes prevent repeated derivations from drifting. Derived relation kinds add occurrence semantics only where named uses consume them. Primitive relation kinds remain available for irreducible distinctions rather than being prohibited by abstract minimalism.
SoTA-Echoing
Reopen these source-use decisions when a selected substrate changes its operator semantics, a newer practice invalidates one of the representation boundaries, or a direct FPF relation pattern supplies a more action-capable derivation or identity rule without worse ontology truth, reader use, or modeling cost.
Reopen Conditions
Reopen the affected disposition, not the whole relation foundation, when:
- a base relation definition, participant meaning, obtaining law, or applicability changes;
- a substrate edition changes a constructor used by the claim;
- a receiving use needs a stable definition, including for planned reuse;
- a reusable definition gains or loses a truthful single
EntityOfConcern; - a named use begins or ceases to need stable occurrence identity;
- an admitted derived kind loses a base dependency or identity rule;
- an admitted primitive gains a lossless derivation or loses its independent action-facing use;
- repeated reader error shows that the definition, kind, occurrence, representation, or designator is being confused.
Relations
- Entered from:
A.6.Ponly after participants are recovered and no current direct relation closes the named receiving claim. - Builds on:
A.6.RELfor relation obtaining and occurrence identity;A.6.5for participant declaration discipline;C.2.1for local claims and predicate-definition epistemes; and the direct subject patterns supplying base relations. - Coordinates with:
A.11,E.24, andE.24.UKfor parsimony, ontic settlement, and durable admission;A.6.0for possible ordinaryU.Signaturemembership of a reusable predicate-definition episteme before relation-kind admission, and forRelationSignatureonly after the relation kind is admitted;C.29for a separate mathematical representation or transfer question about a derivation;F.9only when a consumed result relies on an obtaining Bridge between two exact F.17 cells and its separate bounded-use claim; the applicable plane relation and policy only when an exact ReferencePlane crossing is current;B.3only when a named assurance claim uses an applicable declared domain calculation for a Bridge-related penalty, with any resulting penalty confined to the calculated assurance result for that named use;F.18for names and designators after settlement; andG.11for dependency currentness and scoped refresh. Bridge and plane branches may coexist, but neither supplies or requires the other. - Does not replace: direct subject relation patterns,
A.6.P,E.24.UK,C.29,F.18, evidence or assurance patterns, or work and decision patterns.
A.6.RCD:End
Relation, Signature, Interface, Role, and Slot Precision Restoration
Type: FPF precision-restoration pattern Status: Stable Normativity: Normative unless marked informative
Use This When
Plain name. Relation-signature-interface-role-slot recovery.
Use this pattern when engineering wording such as role, interface, signature, slot or parameter hides the object or claim needed by the task. For bare claim-bearing role, apply E.10.ROLE once. If it identifies the object and rule or settles ordinary use, proceed with that result. Use RSIR only for a remaining question about direct participation, a reusable declaration, an interface, an operation declaration or binding, or a representation position.
Primary EntityOfConcern. The EntityOfConcern is one encountered use of an ambiguous engineering phrase together with the claim that this use is intended to carry.
RSIR recovers the object, direct relation and participant meaning, actual participant, declaration-local SlotSpec or operation declaration, operation application and binding, assertion- or description-side designation, representation position and correspondence, or claim before selecting its subject pattern. The phrase remains wording in an episteme or in speech; it is not the world-side object, occurrence, value, or relation named by the recovered claim.
The intended reader is an FPF practitioner, author or reviewer repairing an engineering phrase so that its next user can recover the object, rule and action it concerns.
First useful move. Recover the project concern first, then recover the EntityOfConcern or claim kind. As soon as the applicable definition, constraint, or test is clear, apply that rule and stop the RSIR repair. Keep a reduced-use source label only when no governed value is being asserted.
What goes wrong if missed. The same word is used for differently defined objects without saying which claim is meant. For example, interface may denote an API description, reusable signature, functional port, compatibility claim, or module-boundary relation. Bare role may point to a system-role kind, one assignment, direct-relation participation, a declaration-local SlotKind, a representation position, use of an episteme, another object, or ordinary wording. A later reader then cannot recover which relation obtains, which participant is meant, which declaration is current, whether an operation application binds an actual value, or which representation correspondence is intended.
What this buys. The reader gets one recovery move before the subject pattern is applied. The repair preserves useful engineering words while preventing a lexical cue from minting a new root kind or collapsing direct participation, reusable declaration, assertion or description, operation application and binding, and representation correspondence.
Not this pattern when. Do not use A.6.RSIR after the subject pattern is already clear. Do not use it for general relation repair after A.6.P is selected, for slot discipline after A.6.5 is selected, for function-like repair after A.6.F is selected, for module-interface repair after A.6.M is selected, for transformation wording after A.3.4.P is selected, or for publication and description repair after E.17, C.2.1, or C.2.P.DR is selected.
Problem frame
The RSIR cluster sits at a common failure point in FPF texts. A project team sees one word and treats it as if it already selected the ontology:
- bare “role” whose E.10.ROLE branch may be a system-role kind, assignment, direct relation-participant meaning, declaration-local
SlotKind, representation position, evidence use, another object, or ordinary wording; - "interface" in a module relation, functional port, API description, protocol, signature, or publication view;
- "slot", "field", "parameter", or "argument" in wording about an actual relation participant, a
RelationSignaturedeclaration, an A.6.1 argument or result declaration, one actual operation application and bound value, a data, formula, or method-call representation, or ordinary prose; - "signature" in a law-governed declaration, API shape, interface specification, or plain sign-off phrase;
- "function" in architecture, capability, method, work, mathematical modeling, or quality wording.
A.6.RSIR is the first-level recovery pattern for this bounded cluster. It does not decide every neighboring subject ontology. It helps the practitioner recover which object or claim is meant, identify the rule that defines or tests it, and then stop the RSIR repair.
Problem
Misreadings to resolve:
- Lexical cues create shadow kinds. Interface, role, slot, endpoint, and function words become local root kinds because they sound technical.
- Participant, declaration, and representation uses become system roles. A direct relation-participant meaning, declaration-local
SlotKind, argument, field, endpoint, or representation position is renamed as a system-role kind. Evidence-use, transformation, and interface claims then lose their direct relations and patterns. - System-role kinds become declaration or representation labels. A context-local system-role kind is demoted into a SlotKind or source-schema field. Its KindSignature can no longer be recovered, and any separately needed assignment, state or Work claim loses its own basis.
- Signatures absorb implementations. A law-governed
U.Signatureis used as if it were a mechanism, method, work-start gate decision, interface conformance proof, or publication. - Participant, declaration, application, and representation boundaries are skipped. A field or parameter is edited without deciding whether it denotes a direct relation-participant meaning or actual participant, a declaration-local
SlotSpec, an A.6.1 argument or result declaration, one operation application and actual binding, or a position in a selected representation. - Evidence and status uses keep old role grammar. An episteme, standard, report, publication, or badge is said to have a role instead of being used in an evidence-use, source-use, status-use, publication-use, assurance-use, or gate relation.
- Neighboring patterns are copied locally. A pattern repeats negative catalogues such as "not proof, not permission, not gate" instead of recovering the current object and applying the pattern that defines or constrains the claim.
Forces
Solution
Recover the project question, the object or claim that answers it, and the applicable rule. State the resulting next action or the condition that prevents it. A short note can retain that result when later use needs it; the RSIRRepairNote described below is working support, not a required form.
A useful RSIRRepairNote contains only the question, recovered meaning and rule, and next action or missing condition. Keep a source label or a blocked stronger interpretation only when it helps recognition or prevents a plausible consequential misreading. No unused branch needs filling.
Recovery order
- Recover the project concern. Say what the project is trying to do: assign work responsibility, declare a signature, check an interface, compare functions, name a port, use evidence, assert status, describe a method, or make another claim.
- Recover the object or claim kind. Decide whether the wording points to a direct relation or participant meaning, an actual participant, a reusable
RelationSignatureorSlotSpec, an assertion- or description-side participant designation, an A.6.1 argument or result declaration, one operation application and actual binding, a representation position and correspondence, a signature, interface claim, system-role kind, system-role assignment, system-role-kind description, port, boundary claim bundle, capability, affordance, Method, function, concern, interest, publication, source label, or ordinary prose. - Name the applicable rule. Use the table in
A.6.RSIR:4.2only until the definition, constraint, or test needed by the current question is clear. Record its PatternID only as a locator. - Separate direct participation, reusable declaration, and assertion or description. Use
A.6.5only when one completeSlotSpecin oneRelationSignatureis current. The direct relation pattern defines or constrains participant meaning, actual participants, obtaining, and occurrence identity. If an assertion or description episteme designates a participant,C.2.1governs that episteme's identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the predicate, polarity, or use relation. When a compatibleSlotSpecis current,A.6.5governs the designation'sValueKindandrefModediscipline; an ordinary assertion may instead name actual participants directly without opening a reusableRelationSignature. - Separate operation declaration, application and binding from representation. Use A.6.1 for ArgumentDeclaration and ResultDeclaration content. Open an actual binding claim only after identifying the application and the relevant bound value. Interpret a call, formula, tuple, edge or schema position under the conventions for positions in that expression; it represents the declaration or binding without being that object.
- Keep the source label reduced-use when no governed claim is current. A word can remain a cue, quotation, title, or local shorthand without being admitted as FPF-governed vocabulary.
Use Tech position for a place in a selected representation, such as a tuple component, call argument, edge endpoint or schema field. Recover its correspondence through the selected scheme and conventions; state it explicitly when the receiving claim needs that detail. The position remains distinct from the participant, SlotKind or SlotSpec it may represent. Its content can express or support a claim, but the position's presence alone establishes no obtaining relation. In every representation branch below, use C.29 only when a separate mathematical representation or transfer question remains.
Subject pattern selection
Relation-defined wording dispatch
When wording derives a qualification, status, or category from participation in a relation, recover the object needed by the next use before naming it:
- If the claim concerns an actual entity participating under one named relation-participant meaning, state the direct relation, that meaning, and the actual participant. The participant retains its direct kind.
- If reusable typed declaration is current, use
A.6.5for the correspondingSlotSpecinside oneRelationSignature. ItsSlotKindis declaration-local and neither is the participant nor makes the relation obtain. - If an episteme asserts, evaluates, or describes the participation,
C.2.1governs the episteme's identity and content, while the direct assertion, evaluation, evidence-use, or description family governs the predicate, polarity, or use relation. When a compatibleSlotSpecis current,A.6.5governs the participant designation'sValueKindandrefModediscipline; without reusable declaration, the assertion may designate the actual participants directly. - If the receiving use needs a local classification or quantification over such actual participants, use
C.3andC.3.1for the localU.Kind, membership rule, and extent rule. Neither the participant-meaning label nor the declaration-localSlotKindadmits that kind. - If the source exposes a tuple component, argument, edge endpoint, schema field or another representation position, interpret it under the selected scheme and recover the correspondence needed by the claim. A displayed value can state a participant or binding claim; its presence alone does not establish that claim.
For parameter, argument, or result wording, separately recover the A.6.1 declaration content, one independently identified operation application and any obtaining declaration-local binding, and the selected representation position. Open the binding only when the actual bound value matters to a receiving claim. Neither the declaration nor representation syntax establishes the binding; a result binding is distinct from production, a produced entity, a result episteme, evidence, and work.
When a receiving use compares or constrains a whole organization of relation occurrences, A.22 may govern a selected U.Structure. One actual participant, corresponding SlotSpec or designation, operation binding, or representation position does not by itself establish such a structure.
Replacement candidate rule
Do not replace one umbrella with another. The minimum admissible repair candidate names:
- the object or claim kind;
- the subject pattern;
- one result for the receiving use: a retained reduced-use source label, a blocked stronger reading, or the next admissible use.
Name a direct relation, claim-bearing episteme, declaration-local SlotSpec, A.6.1 operation declaration or actual application binding, or representation correspondence only when that object is current for the receiving use. Do not fill an unused branch or require both a retained source-label use and a blocked overread. If the minimum cannot be named, leave the phrase in quote-only or reduced-use form and record the blocker.
Reduced-use source labels
Reduced-use labels are allowed. They are not failures. A source label remains reduced-use when it helps readers find or recognize the case but does not carry FPF-governed content.
Examples:
- “API role” can remain a quoted source phrase while the branch is selected with
E.10.ROLE. The repaired claim may be an API description, a provider system-role assignment, a declaration or representation position, a promise-content episteme under A.2.3, an independently obtaining commitment under A.2.8,PromiseContentUse, a delivery or acceptance relation, another named direct relation, or an interface specification. - "parameter" can remain ordinary prose while a complete
SlotSpecis named only for a current reusable relation declaration, an operationArgumentDeclarationorResultDeclarationand any application binding stay underA.6.1, and a method-call, formula, or other representation position is interpreted under the conventions of the chosen expression. - "function" can remain ordinary engineering language when no architecture, capability, method, work, mathematical, quality, or module claim depends on it.
Shortcut Cost and Reopen Condition
The subject pattern supplies the substantive definition or test once RSIR has identified the question. The selection table keeps relation and slot rules, operation declarations and bindings, representation, system-role kinds and assignments, and the neighboring engineering claims separate. RSIR does not perform those operations merely by naming their patterns.
The saved effort is that a practitioner does not run several full patterns before knowing which one is current. The loss budget is narrow: RSIR may select a direct pattern, preserve a reduced-use source label, or record a blocker. It may not decide the system-role kind, system-role assignment, signature, operation application or binding, evidence-use relation, status assertion, service or access relation, architecture description, or Method relation that belongs to the selected pattern.
Reopen RSIR when the selected pattern shows that the source phrase carried more than one governed object, the object kind was selected too early, a needed slot distinction was missed, or evidence, status, publication, gate, method, work, architecture, capability, or concern claims were folded into one label. The reopened repair splits the phrase into multiple governed values or keeps the excess wording reduced-use.
Archetypal Grounding
System case: module interface claim. A team says "the cooling module exposes the heat-exchanger interface." RSIR first asks what claim is current. If the claim is substitutability or separate change, use A.6.M. If a reusable relation declaration for exchanged-medium and boundary-condition participant meanings is current, use A.6.0 plus A.6.5 for the RelationSignature and complete SlotSpecs. If the current use is a diagram, API schema, or other representation, interpret its positions under the selected scheme and state the correspondence needed by the receiving claim. If the claim is a functional port in a transformation-flow structure, use A.6.F, A.3.4, and E.18. RSIR does not create U.Interface.
Bare-role case: API provider wording. A source says “the API role is provider.” Apply E.10.ROLE once. If it recovers a provider System, local ProviderSystemRole kind, assignment, capability, provider Work, promise, access relation, publication, or another direct object, apply that object's rule and do not apply RSIR. Apply RSIR only when the still-unanswered question is the participant meaning in a direct relation, a reusable declaration, an interface claim, an operation declaration or binding, or an API-schema representation position. For protocol, service-term, SLA, or agreement-like wording that bundles several claims, use A.6.C to unpack the claims before stating each object or relation. Use A.6.M only for a module-interface claim and A.6.B only for boundary-package statement classification. Do not assign a system role to the API description.
Evidence case: reviewer and report wording. A report says “reviewer evidence role approved the gate.” Apply E.10.ROLE once and split the claims. Apply A.2/A.2.1 for any reviewer system-role kind or assignment. Use A.10 for evidence reliance on a named claim, B.3 only for a named assurance claim, F.10 for a status-use relation, E.24.PUB when publication availability is current, and E.17 when the accepted account needs a reader-facing publication form. Use A.21 for the gate decision and A.2.9 for any issuing speech act. None of those recovered branches needs RSIR unless a separate direct-participation, reusable-declaration, interface, operation, or representation-position question remains. No episteme receives a system-role assignment by being evidence.
Slot case: method parameter. A method description says "parameter target controls the model." The sentence does not identify what target designates or which control relation is claimed. Keep it as reduced-use source wording and recover those missing values before asserting the control claim.
A separate positive example illustrates an A.6.1 argument label. In the current recognizeAdmittedHolonCandidate declaration, candidate is an ArgumentDeclaration meaning one entity being evaluated, with ValueKind = U.Entity; recognitionJudgment is the declared result meaning. Under A.6.1, the project independently identifies the bounded recognition-evaluation invocation P-37 by that declaration's application predicate, identity rule, and extent rule. During P-37, Pump #37 is bound under candidate, and the returned value unknown is bound under recognitionJudgment.
In a call representation such as recognizeAdmittedHolonCandidate(target = Pump-37, ...), the named-argument position target corresponds to the declared candidate meaning but is neither the declaration nor either binding. The practitioner writes: "target is the call label; A.6.1 declares candidate : U.Entity; during application P-37, Pump #37 is bound as candidate." Stop there unless the receiving claim needs the result binding or another subject pattern.
Near-Miss Checks
Bias-Annotation
This pattern has a relation-cluster bias because it sits in A.6. It mitigates that bias by stopping as soon as the applicable definition, constraint, or test is clear.
It has an interface and software-language stress case because API, endpoint, protocol, and interface wording often enters from software. The pattern keeps the recovery general: architecture interfaces, physical ports, functional ports, service-access descriptions, and publication forms are all possible, and none is selected by word choice alone.
It resists semio-bias by keeping descriptions, publications, records, reports, standards, and source labels under the patterns that define or constrain those objects and uses: C.2.1, E.24.PUB, E.17, C.2.P.DR, A.10, B.3, F.10, C.28, E.10, or E.10.ARCH when those objects or uses are current. A source label may help recognition; its presence is not evidence that the denoted object is the current EntityOfConcern or that a proposed action is admissible.
Conformance Checklist
- The repair starts with project concern, not with a replacement word.
- The EntityOfConcern or claim kind is named before a subject pattern is applied.
- The repair stops once the applicable rule and concrete next action are clear.
- When reusable relation declaration is current, slot discipline uses
A.6.5and states one completeSlotSpec = <SlotKind, ValueKind, refMode>inside oneRelationSignature; actual participants and representation positions remain outside it. - An assignment claim uses its declared U.SystemRoleAssignment species and participant meanings. A positive claim needs facts satisfying that predicate; add explicit occurrence identity when the receiving use needs it. A governed negative claim creates no obtaining assignment. Apply A.2.5 for a state claim, A.2.7 for a structure among kinds, and the applicable rule for capability, Method or Work. Do not repeat a settled result through RSIR.
- Evidence-use and status-use cases are not represented through
U.SystemRoleAssignmentfor epistemes. ApplyE.10.ROLEonce to bare role; if it recovers evidence use, status use, or another direct object, apply that object's rule and leave RSIR closed. - Interface wording is kept as a recognition cue but is not admitted as generic
U.Interface. - Every neighboring object family selected in the dispatch table uses its defining or testing rule rather than being redescribed inside RSIR.
- Relation-defined wording dispatches separately to the direct participant meaning and actual participant; a declaration-local
SlotSpecwhen reusable typing is current; an assertion- or description-side designation whose episteme identity and content stay withC.2.1, whose predicate, polarity, and use stay with the direct claim family, and whose typing stays withA.6.5only when a compatibleSlotSpecis current; a C.3 local kind when the receiving classification or quantification needs it; or a representation position with its recoverable correspondence. It does not create one umbrella qualification object. - Operation wording keeps A.6.1
ArgumentDeclarationorResultDeclarationcontent, one independently identified application and obtaining argument or result binding, and any call or formula representation position distinct; it infers neither a public application kind nor production, a produced entity, a result episteme, evidence, or work from the binding. - Quote-only or reduced-use labels carry no action-facing claim beyond the claim admitted by the selected rule.
Common Anti-Patterns and How to Avoid Them
Consequences
A.6.RSIR adds a bounded recovery step when the engineering object or claim remains unclear after the F.19 reading with E.10 cues. The selected subject pattern then handles the substantive claim; neighboring patterns can refer to this recovery instead of repeating it.
The pattern also keeps useful source vocabulary alive. Engineers can still say interface, API, role, parameter, function, and endpoint. FPF refuses to let those words select ontology by themselves.
Rationale
The RSIR cluster needs a bounded recovery step when F.19's whole-span reading and E.10's compact cues leave an engineering object or claim unclear. Direct relation, declaration, interface, system-role, Work, publication, evidence, and status rules retain their own objects and predicates. Apply the thinner E.10.ROLE entry once to bare role. If one concrete direct-participation, declaration, interface, operation, or representation question remains unanswered, apply RSIR to that question; otherwise leave RSIR closed.
The main ontological principle is separation among participant, declaration, application and binding, assertion and designation, and representation. An actual direct-relation participant retains its direct kind under one participant meaning. A corresponding SlotSpec, when reusable typed relation declaration is current, states a declaration-local SlotKind, exact ValueKind, and refMode. An assertion or description remains a C.2.1 episteme; its direct claim family supplies predicate, polarity, or use, and A.6.5 types a participant designation only against a compatible current SlotSpec. An A.6.1 declaration states reusable operation meaning, while one application and obtaining binding relate that occurrence to an actual value. A representation position may correspond to any of those objects without becoming one.
The second principle is direct rule use. Once the current object is recovered, apply the rule that defines, constrains, or tests the claim. RSIR only identifies that rule and its PatternID locator when the reference must travel.
SoTA-Echoing
The comparisons below inform this bounded recovery: distinguish the engineering objects before selecting their direct rule. They do not supply the obtaining or identity rule for the recovered object.
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.
A.6.RSIR:End
Affordance and Action-Invitation Precision Restoration (ACT-INV)
Type: Architectural (A) Status: Stable Normativity: Normative (Core)
Plain-name. Affordance and action-invitation precision restoration.
Use this pattern when wording such as “affords”, “invites”, “calls for” or “actionable” leaves the intended claim or question unclear: who could do what, in which situation, on what grounds, and what the reader may do with that statement.
What goes wrong if missed. A physical opportunity, detected cue, proposed inquiry or interface prompt is read as a capability, duty, permission or completed action. The reader acts on the wording without recovering the claim that would justify that action.
What this buys. A sufficient statement of the opportunity, prompt, claim or question, with the participants, conditions and subject rule needed for its use. An unresolved rule or fact is returned as a gap. An ordinary sentence can be the complete result.
First useful move. Recover what the speaker means in this use. Compare the live alternatives—for example, an available physical action, detection of that opportunity, an operator prompt, or a proposed inquiry. State the supported interpretation or the question that distinguishes the remaining alternatives. Apply the recovered subject rule before asserting its result.
Not this pattern when. If the claim and its subject are already clear, use that subject pattern directly—for example, for a Method, MethodDescription, WorkPlan, actual Work, ability, duty, gate, evidence, evaluation or publication. A sufficient existing sentence needs no further recovery note.
Governed move. This pattern recovers the meaning of affordance-like and action-first wording. Its interpretation menu and optional recovery note do not define one common relation kind or a durable U-kind. Any opportunity, relation occurrence, Method, ability or Work that the result names keeps its own subject, obtaining conditions and identity rule.
Use A.6.P when the recovered content is a relation claim. Other recovered results, including an open inquiry question, go directly to their governing patterns. The recurring repair is to recover meaning, relevant participants and conditions, then express the result sufficiently for the receiving use.
Preserve an insufficiently articulated cue through A.16.1 or publish its possible continuations through B.4.1. A question can become clear enough for inquiry while its answer remains unknown.
When the result selects a Method for enactment, identify that admitted U.Method. A cited U.MethodDescription has that Method as its exact EntityOfConcern and makes a substantive claim about it as a way of doing under A.3.2. A proposed action or question can remain expressible before any Method is admitted. A WorkPlan describes intended Work. If the sentence deliberately claims a particular dated Work occurrence, recover A.13 first and independent A.15.1 admission with enactsMethod; use F.6 only for a separate precise attribution through the same A.13 assignment.
This recovery lets ecological psychology, phenomenology, active inference, control, interface design and robotics keep their distinct subject meanings while comparing a concrete action question.
Coordinates with. C.16.Q for evaluative-language repair; C.2.2a, A.16, A.16.1, A.16.2, and B.4.1 for language-state chart positions, articulation and closure coordination, admissible moves, early cue classification, next-use docking, and admissible retreat when a published recovery result must be reopened; use A.16.0 only when lineage, branch, loss, or an actual responsibility-handoff history itself must be published as an explicit trajectory account; B.5.2.0 when the recovered result is an explanatory question or candidate inquiry; C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 for articulation and closure readings, source and use claims, and representation-factor readings referenced but not governed here; A.10 and B.3 for evidence and assurance; B.4 and B.5 for anomaly-driven cycles; E.17.0 for viewpoint reference resolution and independent view conformance, and E.17 for publication; F.9 for Bridges and bounded-use claims; F.9.1 for optional stance notes about those claims; C.3.3 for kind-bridge repair when endpoint kind mismatches appear.
E.10.ARCH relation.
A.6.A supplies the wording-recovery method when an E.10 or E.10.ARCH use leaves an affordance-like or action-first phrase ambiguous. Recover the claim or question and then its direct governor. Evaluative content goes to C.16.Q; ability, Method, Work, duty, evidence, assurance, gate and decision claims use their own patterns. Keep a recovery note only when a later reader needs the interpretation or its grounds.
Non-goal. This pattern does not assert that physical affordances, interface affordances, social affordances, epistemic probe moves, articulation-closure moves, latent policy cues, and control opportunities are one concept.
Its job is to publish a treatment of action-first language across those traditions, using a direct contrast when that is enough and an F.9 Bridge only for a cross-context semantic-correspondence claim, while preventing false identity by shared language.
The recovered meaning selects the next pattern:
- where the repaired statement is primarily evaluative, use C.16.Q;
- where it is primarily about general capability, capability wording, method wording, or method-description wording, use A.6.F, A.2.2 qualified holder capability,
U.Method, orMethodDescriptionaccording to the claim being made; - where it is primarily deontic, apply A.6.B;
- where it concerns intended work, use A.15.2 for the WorkPlan; where it deliberately asserts a particular dated Work occurrence, use A.13 and independent A.15.1 admission. Keep the Method, its description, plan and Work distinct. Ordinary practitioner action does not require invented formal identities.
Problem frame
FPF repeatedly encounters a precision failure around affordance-like and action-first language.
Authors say:
- “this handle affords pulling”
- “the interface invites confirmation”
- “the alarm calls for rollback”
- “this discrepancy suggests probing deeper”
- “the draft is ready for formalization”
- “the model wants to brake”
- “the situation is actionable”
…but the intended meaning is one of several different action-oriented families, for example:
- Physical affordance — a physical or environmental configuration offers a bodily action to an embodied agent.
- Interface affordance — an operator-interface element, operator panel, alarm, or publication face presents an operator move.
- Social affordance — another agent or interactional setting invites a response or coordination move.
- Epistemic probe move — a problem situation invites asking, comparing, measuring, testing, or instrumenting.
- Closure-advance move — a situation invites naming, rescoping, proxy declaration, or formalization.
- Latent policy cue — a learned or distributed state carries an action-oriented tendency not yet locally articulated.
- Control opportunity — a closed-loop state invites braking, rollback, replan, isolate, escalate, or override.
The recurrent failure modes are:
- Site confusion. The invitation-bearing site is unclear: physical entity, scene, interface entity, description episteme, carrier, policy state, or problem episode.
- Enactor confusion. The system that would act is unclear: for example, a human operator, robot controller, team or automation system. An assignment may help designate its holder, but is not itself the actor.
- Action confusion. The candidate action is hidden behind vague language like actionable, calls for, ready for, natural next step.
- Invitation vs obligation collapse. A situation that invites an action is rewritten as if it already created a duty.
- Invitation vs capability collapse. A local, situated action opportunity is rewritten as if it were a general capability claim.
- Invitation vs work collapse. Offered action is narrated as if it had already been executed.
- Substrate confusion. Ecological, embodied, latent-distributed, and symbolic-local action cues are silently collapsed.
- Bridge illusion. Similar language across traditions is mistaken for sameness.
- Premature closure. An early cue is published as if it were already a committed method, gate, or policy.
Problem
How can FPF let authors use the communicative convenience of affordance-like and action-first language while preventing category errors when the language crosses:
- ecological and phenomenological discourse,
- interface and operator-facing discourse,
- active-inference and world-model discourse,
- control, monitoring, and incident-response discourse,
- robotics and embodied-AI discourse,
- epistemic exploration and problem-framing discourse?
Forces
- Action speed vs auditability. Action-first language is attractive because it is fast; that same speed makes it unsafe at boundaries.
- Situated opportunity vs its account. A physical opportunity can depend on the agent and environment even when no current account detects it; an information-constituted opportunity follows its own subject rule.
- Preconceptual cue vs later articulation. Detection, verbal articulation and the obtaining of an opportunity can have different conditions.
- Enactor specificity vs shared discourse. A cue may be visible to one detector yet relevant to another would-be enactor.
- Opportunity vs obligation. Not every invitation is a gate or commitment.
- Option plurality vs premature scalarisation. Several candidate actions may co-exist without an admissible total ordering.
- Cross-tradition dialogue vs false unification. The framework should preserve parallels without asserting identity.
- Different continuations. A cue can support inquiry, an action option or an existing policy application; each requires its own grounds, with no compulsory sequence.
Solution - Recover the claim, apply its subject rule and return sufficient wording
Trigger rule
Use A.6.A when the intended claim or question remains unclear for the receiving use. The following cues help locate that ambiguity:
- the prose uses tokens such as affords, invites, calls for, actionable, ready for, ripe for, natural next step, the model wants, the interface tells, this problem asks for;
- a boundary, gate, incident note, design note, or review note uses such language for admission, selection, triage, or action guidance;
- different traditions are compared using the same action-first wording;
- a draft introduces model affordance, interface affordance, actionable insight, policy invitation, or ready for formalization without declared sense;
- the author intends the phrase to carry more than one of: situational action opportunity, latent cue, operator move, probe move, closure move, or control move.
Operational repair sequence
- Recover the statement and receiving use. Read the sentence with its source context. State which interpretation, decision or action the reader needs it for.
- Compare the live interpretations. Consider a physical opportunity, its detection, an operator prompt, a social response, a candidate inquiry, a proposed clarification, a learned policy tendency or a control option. Also consider an actual evaluation, ability, commitment or Work claim when the sentence supports that reading. Use §4.3 as a menu, not a required classification.
- Select what the grounds support. State the intended interpretation and why a consequential rival is excluded. If the grounds do not choose, preserve the rival meanings and return the fact or question that would distinguish them. A short note is useful when a later decision needs those grounds; it is not a prerequisite to every repair.
- Recover the subject and relevant conditions. Name the site, would-be actor, action and other participants only to the extent that they determine the claim. For an obtaining relation, recover its direct predicate and any needed occurrence identity under A.6.REL. For an inquiry, state the question and what an answer would resolve. A menu label supplies neither result.
- Express the first useful result. Return a sufficient ordinary sentence, supported bounded claim, explicit question or missing basis. Use one of §4.5's optional forms only when the receiving use needs it. Separate a detector, viewpoint, source or representation when that distinction changes the result.
- Continue from that result. Apply the subject pattern for a needed evaluation, Method selection, WorkPlan, actual Work, authority, gate or evidence claim. Use A.6.B for the actual boundary-bearing claim. Stop when the receiving question is answered; wording recovery creates no extra invitation occurrence to establish first.
Recognition and assurance answer different questions
The first result is recognition of what the sentence means. Establishing the recovered claim then uses that subject's rule and evidence. An intelligible physical-opportunity claim can still lack support; an intelligible research question can be useful while its answer is unknown.
Use A.16.1 or B.4.1 when the cue cannot yet support a particular claim or question. When articulation is sufficient, express the recoverable content without requiring a relation record or a sense token. Any relevant AE or CD reading concerns the account and its next use; it does not establish a physical opportunity.
If an account later becomes unsupported, revise or withdraw it through the applicable subject pattern and A.16.2. With physical conditions fixed, changing its wording, carrier or detector establishes no beginning, ending or new occurrence of the physical opportunity. If information itself is constitutive under a source-specific relation predicate, use that predicate and its identity rule for the corresponding change.
Optional recovery note
When a receiver needs a reusable account of the repair, a note may contain:
This form expresses the result without defining a common relation kind. For a relation claim, its participants, direction, applicability, evidence conditions and identity rule come from the direct governor. Use A.6.5 for a reference-backed designation only when a compatible declared SlotSpec is current; ordinary note wording needs no invented relation declaration.
Omit fields that do not change interpretation or use. A sufficient sentence remains a complete result. A particular receiving publication can require more structure under its own conditions; that requirement does not become a universal prerequisite to wording recovery.
Viewpoint and view discipline.
When viewpointRef is present, effectiveReferenceScheme is also explicit and the reference resolves under that scheme to one independently admitted U.Viewpoint episteme.
view is a separate optional value: it names one independently identified C.2.1 episteme that already has U.View membership only because E.17.0 EpistemeViewpointConformanceRelation(view, viewpoint) obtains for at least one admitted viewpoint. The selected viewpointRef need not be the viewpoint to which an optional view conforms unless the record explicitly claims that relation.
Including viewpointRef or view in a recovery note establishes neither U.Viewpoint nor U.View dependent-kind membership; it only cites already established objects. Detector, viewpoint selection, view membership, viewing construction and publication remain separate.
A sentence such as “X affords Y” needs repair when its intended action, participants or basis remain hidden for the receiving use. For a recovered relation claim, apply A.6.REL; for a recovered question, preserve the question. Earlier cue content may remain a cue pack, RoutedCueSet or another appropriate expression.
Interpretation and enactment. A menu label names a candidate interpretation; it establishes neither an occurrence nor a common relation kind. A proposed action can remain a proposal. When it selects a Method, identify the admitted U.Method and treat any MethodDescription under A.3.2. Use A.15.2 for planning. For a deliberately asserted dated Work, recover its A.13 basis and independent A.15.1 admission; F.6 is additional only for precise assignment-bound attribution. A returned value, application binding, evaluation Work and result episteme retain their own identities and rules. A Work-to-result claim needs its direct predicate; a missing predicate blocks that claim without erasing an independently established binding.
A.7 boundary note.
When the site affects interpretation, distinguish an EntityOfConcern-side participant, a Description episteme participant and any non-claim-bearing site kind. Name a participating publication face, publication form, carrier or rendering separately under A.7. An optional note may use siteClassification and publicationOrCarrierParticipation for these distinctions; ordinary wording can express them too.
Separation note.
detector and invitedEnactor are not synonyms.
When both matter, they SHALL be published separately.
Enactor note. When the result names an actual would-be enactor, it SHALL identify the System that would act. An assignment may designate that System through its holder, but the assignment is not the acting participant. An episteme, publication face or carrier may instead be part of the site.
Episteme non-agency note. For a claim about actual enactment, identify the acting System and any carrier or acted-on system that matters. A description can guide that actor through its content; it is not itself the performer. Ordinary instrumental wording may remain when the actor and use are recoverable.
Candidate interpretations
The ActionInvitationSense menu in §4.3 is a discovery aid. Its AIS.* labels can help compare interpretations or preserve search terms; using a label is optional. Choosing one label does not assert one common actionInvitation relation or impose common obtaining and identity conditions on the listed subjects.
For a consequential interpretation, recover the source-local meaning, the participants and action it concerns, the conditions under which the claim would hold, and the result the receiving use needs. Keep an unresolved interpretation as an alternative rather than assigning a default because the sentence occurs in an ecological, interface, control or research context.
If a local practice needs a named interpretation profile, it may specify applicable sites and actors, action structure, relevant substrate, admissible evidence, forms of expression, change conditions and cross-context use. Such a profile describes that local recovery use. A relation declaration, Method or commitment still needs its own independently applicable rule.
A.16 articulation-token relation note
A recovery note may carry articulationHint as a local articulation-cue field when the receiving use needs it.
This field is not a new formality progression, not a maturity scale, and not a surrogate for F. Its only job is to preserve local articulation and closure cues until they can be related to A.16 move logic and the explicit C.2.4 and C.2.5 governing facets.
Local articulationHint tokens SHALL be related to A.16 move logic and to the explicit C.2.4 and C.2.5 governing facets one-for-one, and A.6.A SHALL treat them as local publication cues only.
Until then, local hints SHALL NOT be thresholded, aggregated, or compared across Contexts.
Interpretation menu
Consider these candidate meanings and any source-local alternative that can change the result. The menu helps recover a claim; it does not select its truth conditions by classification.
Using the menu.
- In ecological and embodied contexts, consider the physical-opportunity reading, while checking whether the claim instead concerns its perception or detection.
- In operator-interface, alarm, or operator-panel contexts, consider the interface-prompt and control-option readings, retaining both only when the sentence makes both claims. If the wording instead claims module interface, functional port, API, protocol, signature, interface specification, or service-access compatibility, use
A.6.RSIR,A.6.M,A.6.F, orA.6.0according to the recovered EoC rather than treating the cue as an action invitation. - In epistemic exploration contexts, "this suggests probing, formalizing, or reframing" can mean an inquiry question, candidate investigation or proposed clarification. Recover that result directly.
- In learned world-model, active-inference, or policy contexts, consider a learned policy tendency and a control option as different readings. A model state does not by itself establish a control decision, duty or performed action.
- If the sentence is chiefly about better, worse, fit, or merit, use C.16.Q instead of A.6.A.
Recover details that change the result
Use the following questions where their answer changes the recovered meaning or its use. They are not ten fields that every sentence must populate:
-
Site tuple and site classification. Site tuple members: named EntityOfConcern, scene, interface element or front-end element, Description episteme, episode, control state, or non-claim-bearing site kind - with publication or carrier participation stated separately when live.
-
Invited enactor tuple. Which System, including a qualified collective system, would act; an assignment may help identify its holder when that attribution matters.
-
Candidate action tuple. What action or inquiry the phrase concerns. If the result selects a Method for enactment, identify its
U.Method; keep any MethodDescription, WorkPlan and actual Work separate under their direct rules. -
Intended meaning. Which interpretation the context supports, and which consequential rival remains or is excluded. An
AIS.*label is optional. -
Coupling frame. The conditions and, where applicable, coupling relation on which the recovered claim depends; recover their rule rather than treating their names as proof. Examples: reach envelope, interface state, incident horizon, control horizon, probe pack, open issue set.
-
Detector, viewpoint reference, and independent view. Who or what detected the cue; which viewpoint episteme
viewpointRefresolves to under the effective reference scheme when a viewpoint is selected; and, independently, which already-conformingview : U.Viewis cited when a view itself participates. None follows from another. -
Normal form and
articulationHint. Whether a particular expression form or articulation cue changes what the receiver can recover or do. -
Scope and time when relevant.
U.ScopeandΓ_timeSHALL be explicit when omission changes meaning. -
Representation substrate when relevant. Especially when comparing ecological, embodied, latent-distributed, and symbolic-local treatments.
-
Witness mode and evidence references. Exemplars, sensory traces, probe notes, kinematic data, interface events, controller traces, run logs, or review notes.
Normal-form discipline
Use a sufficient ordinary sentence first. The four forms below are optional ways to preserve cues, present a candidate, compare alternatives or refer to an existing policy. Select one only when it contributes to the receiving use; no sense token requires a default form.
Docking note. Where the result selects a Method, cite that admitted Method. A MethodDescription, WorkPlan or Work is a separate object and is cited only when needed. A PolicyHook refers to an existing policy, Method, gate or protocol; each assertion about duty, admission or actual execution still follows its own rule.
ANF-1 — CuePack.
Use when preserving an early or incompletely articulated cue is the useful result, including AIS.PhysicalAffordance, AIS.SocialAffordance, and many cases of AIS.LatentPolicyCue.
A conforming CuePack publishes:
- exemplar or contrast episodes, sensory traces, or probe cues,
- site conditions,
- enactor descriptor or enactor constraints,
- a small gloss set of candidate actions,
- optional ordinal urgency or salience summaries,
- a qualification of a commitment, selection, gate or execution inference only when source context gives a plausible reader reason to make it and the distinction changes use.
ANF-2 — ActionOption.
Use when one candidate action tuple is explicit.
A conforming ActionOption publishes:
- one candidate action tuple,
- the would-be acting System and any assignment that the receiving claim needs,
- local guard sketch,
- expected near-field effect,
- a
U.Methodref when the option selects that Method for enactment, plus a separate optionalU.MethodDescriptionref orU.WorkPlanref only when that independently existing object is current, - any separately established selection, duty or execution state needed by the receiving use. If such a state is unknown, the option form supplies no negative state either.
ANF-3 — OptionSet.
Use when several candidate actions coexist.
A conforming OptionSet publishes:
- explicit action members,
- any local comparator, triage rule, or partial order,
- admissible incomparability if no total order is admissible.
ANF-4 — PolicyHook.
Use when the receiving use needs an explicit reference to an existing controller, gate, playbook, Method or override protocol.
A conforming PolicyHook publishes:
- references to the existing policy, Method, gate or protocol content governing this use, resolved under the applicable reference scheme,
- applicable guard or trigger conditions,
- the acting or maintaining System when the receiving use needs that identity, plus the responsibility or authority basis and any assignment claimed; a missing responsibility rule blocks only the dependent attribution,
- escalation or override references when relevant,
- enough source content to recover the applicable rule; publication of the hook alone establishes no individual commitment, admission decision or Work occurrence.
Separation from quality, capability, commitment, and work
A.6.A SHALL prevent the collapse of action invitation language into neighbouring families.
- A statement about better, worse, fit, or merit belongs to C.16.Q.
- A statement about what a system can do in general belongs to capability wording, method wording, or method-description wording under A.6.F and the subject pattern for the asserted capability, method, or method-description claim.
- For what must or may be done, distinguish a generic prescription, an individual duty, a grant and admission of a named action or application. A.6.B distinguishes their boundary claims; the normative source, A.2.8 commitment rule, A.2.8.PER permission rule or admission rule supplies the basis.
- Ordinary statements of what someone did may remain ordinary. A deliberately asserted dated U.Work follows A.13 and independent A.15.1 admission with its enactsMethod relation; precise assignment-bound attribution additionally uses F.6.
- A result that selects a Method identifies that Method without becoming a plan or occurrence; any
methodDescriptionRefremains auxiliary. A proposed action can remain a proposal without inventing its Method. A Description episteme never acts and is never what Work enacts. - When a sentence carries both evaluative and action-oriented content, make the two claims and their respective grounds distinguishable. Use linked records only when the receiving use needs them.
Two clear clauses or sentences may suffice.
Examples:
- “This scene is good for grasping” can combine a physical-opportunity claim with an evaluation under a particular criterion. Recover each claim and its rule.
- “This alarm requires rollback” needs the gate or duty rule, if that is the intended claim.
- “The robot can grasp this handle” can concern ability under conditions or a situated physical opportunity. Recover which result the reader needs and apply its rule.
- “The operator clicked rollback” reports an action rather than offering one. It needs no extra formal Work identity unless that identity is material to the receiving claim.
Bridge discipline across traditions
Whenever two traditions are compared using action-first language, first ask whether the comparison asserts or relies on semantic correspondence between exact senses in different semantic contexts. If it does, resolve those senses and test F.9; cite an obtaining Bridge only when its direct predicate is true, and state a separate bounded-use claim only when a proposed use is live. That claim carries the use, direction, correspondence rule, tolerated loss, and polarity.
If the comparison does not assert or rely on that correspondence, use E.17.ID.CR for bounded comparative review or the direct relation that supplies the contrast, then stop.
Add an F.9.1 stance note only as optional reader help for an already constituted bounded-use claim.
Useful stance labels include, for example:
localRenameoperationalizespartialAnalogyprojectionnonEquivalent
Examples:
- A named comparison between
AIS.PhysicalAffordanceandAIS.InterfaceAffordancemay remain a direct bounded contrast under E.17.ID.CR or another direct relation. If it asserts cross-context semantic correspondence, any bounded partial analogy needs an obtaining F.9 Bridge and a matching use claim. An optionalpartialAnalogynote helps reject identity; the label alone establishes nothing. - AIS.EpistemicProbe and AIS.ClosureAdvance use the direct progression or other relation claimed. Apply F.9 only if the statement asserts or relies on semantic correspondence between exact senses with different interpretation bases; a change of domain label alone does not open that branch.
- A named use from
AIS.LatentPolicyCuetowardAIS.ControlOpportunityneeds F.9 only when it relies on cross-context semantic correspondence; then any operationalization or projection reading follows the obtaining Bridge and the use claim's direction, rule, and tolerated loss. Otherwise the direct relation must supply the proposed contrast or use. - A robotics comparison from
AIS.PhysicalAffordancetowardPolicyHookmay remain a direct contrast. If it relies on cross-context semantic correspondence, a projection reading requires the obtaining F.9 Bridge and a matching bounded-use claim under the controller frame; an F.9.1 note only explains that existing claim. - Action invitation and quality ascription may co-occur, but co-occurrence is not identity.
Change lexicon
When a recovery note changes, state what changed. The following verbs are useful descriptions, not a required common operation signature:
publishRecovery(...)— publish the recovered claim, question or missing basis.withdrawRecovery(...)— withdraw that account.retargetSite(...)— change the named site in the account, applying the subject identity rule separately when an occurrence claim changes.retargetInvitedEnactor(...)— change the invited enactor tuple when that slot is ref-backed.reviseAction(...)— change the candidate action tuple by value (or split into the correspondingretargetParticipant(...)form if the account declares that action slot as ref-backed).reviseSense(...)— change the interpretation attributed to the wording; state the resulting change in the claim.reArticulate(...)— change the articulation cue while preserving the recovered meaning.reFrame(...)— change coupling frame.reGuard(...)— change guard sketch or hook condition.rePolicyHook(...)— change policy, gate, or method hook details.reView(...)— change detector publication, ref-backed viewpoint selection, or independent view inclusion under the declared ref-vs-value discipline. ChangingviewpointRefdoes not mutate the viewpoint episteme; adding or replacingviewdoes not establish E.17.0 conformance.rescope(...)— changeU.Scope.retime(...)— changeΓ_time.refreshWitnesses(...)— refresh witness bindings.changeRelationKind(...)— use only when a relation-kind claim changes under its direct governor. A different interpretation of wording need not be a change of relation kind.
These verbs describe changes to an account or its publication. Changed claim content, EntityOfConcern or effective reference scheme identifies a different episteme under C.2.1; an edition or other continuity relation needs its own basis. A change in the actual opportunity follows its direct obtaining and identity rule. Changing wording, its availability or its detector alone supplies no such world-side change. Invitation, commitment, capability and Work claims retain their separate predicates.
A.6.P rewrite note. The technical retargeting forms apply only when a compatible declared SlotSpec makes the corresponding designation reference-backed. Then apply A.6.5 to the reference change. Otherwise describe the changed participant designation or other by-value content directly and apply C.2.1 to the resulting episteme; do not introduce a SlotSpec merely to revise an ordinary note.
Classify the recovered boundary-bearing claim
When the recovered claim is boundary-bearing, use its A.6.B classification:
- L — the rule that defines or constrains the recovered subject, including an actual relation predicate when that is the claim; applicable enactor/site discipline and the F.9/F.9.1 boundary retain their direct governors.
- A — the admission predicate for a named action or application under the applicable rule. An actual satisfaction or admission-decision result is a separate E claim. A statement of allowable claim use or general scope does not qualify by itself.
- D — a generic prescription under its normative source, an individual duty under A.2.8, or a grant under A.2.8.PER. Individual commitments and grants need their own participants and obtaining basis; a generic prescription does not establish them.
- E — an observation, effect or evaluation result and the conditions under which it is obtained. A particular Work, evidence relation or carrier-condition claim uses its own rule. Cite a sensory result, event, probe or log only when its content supplies grounds for the claim; a reference list alone is insufficient.
Do not let bare action-first language carry L-, A-, D-, or E-classified claims, admissible-use consequences, or evidence consequences by itself.
Lexical guardrails
Apply these rules when the wording carries a consequential claim:
- action-first expressions MUST be clarified when their action, participants, conditions or intended meaning remain materially ambiguous; ordinary recoverable wording and metonymy may remain;
- the claim, candidate action, question or missing basis meant by actionable insight MUST be recoverable; use C.16.Q when an evaluative meaning remains unresolved;
- an affordance claim MUST preserve the actor, site and coupling conditions that change its meaning; an implicit participant may remain implicit when the intended value is cheaply and uniquely recoverable;
- an invitation MUST NOT be presented as if it were already a duty, gate, or work occurrence;
- a latent policy cue MUST NOT be presented as if it were already an explanation;
articulationHintMUST NOT be treated as F, as acceptance status, or as a replacement forA.16grounding references;- generic
Surfacefacet tokens MUST NOT be introduced inside A.6.A; publication face, publication form, interop publication form, carrier, or rendering participation must be declared under A.7 and publication-face and publication-form discipline, not by widening the site classification; - unpack an adjective such as graspable, deployable, actionable or ready when a hidden actor, action or condition changes the claim;
- distinguish quotation or discussion of an expression from an assertion using it when the distinction affects interpretation.
Elaborate only for the next use
Start with the recovered statement or question. Add participants, conditions, supporting sources, rival interpretations and expression structure only when the next use needs them. If further inquiry changes the interpretation, reopen it; elaboration is not a compulsory progression from cue to option to policy.
A move from a cue to a proposed action, from alternatives to a selection, or from a description to a Method, WorkPlan or Work claim requires that receiving subject's grounds. State the result of that move rather than silently upgrading the wording. Use §4.7 for a consequential comparison across traditions and A.6.B for a boundary-bearing claim.
Continue from the recovered subject
Once the result identifies an authority, relation, Method, WorkPlan, Work, gate or inquiry question, continue through its direct pattern if further work is needed. A declaration-local planned-filling row is addressed through its WorkPlan. Preserve a separate recovery note only when a reader needs the interpretation or grounds; there is no common invitation occurrence to establish before continuing.
Archetypal Grounding
Tell
Read an affordance-like sentence as a question about its intended meaning. The result can be an ordinary supported claim, a proposed action, an inquiry question, or a gap. Keep the subject conditions that make that result usable. An optional record can express the result but does not give different subjects one obtaining predicate.
Show (System case)
Draft: “The alarm calls for rollback.”
Repair A — control and incident line
Recover the proposed use: OpsTeam_Phoenix is considering RollbackMethod_R41 on Release_R41 in ProdCluster_EU_1 during RunWindow_RW. RollbackRunbook_R41 describes that Method. AlarmBundle_AB9 exposes the cue about ServiceState_S7; AnomalyPolicy_AP7 specifies the detection criteria. AlertTrace_91 and ErrorBudgetSeries_4 are candidate evidence for applying IncidentPolicy_IP2 over Horizon_H15m.
The first useful statement is: “Check whether the current incident-policy guard and authority permit this team to use RollbackMethod_R41 on Release_R41 in this window; the alarm alone does not settle that question.” If the rule and facts establish a rollback duty or an admission result for this use, state that independently grounded result. Otherwise retain the proposed action or the missing condition. Nothing in these supplied names asserts a performed rollback.
If the receiving operational review uses VP.OperationsControl, resolve its U.ViewpointRef under OperationsControlScheme_2026. OperationsRollbackView_9 remains an independently identified C.2.1 episteme and a U.View only if its E.17.0 conformance obtains. These are optional, separately established references, not additional requirements to understand the alarm sentence.
Recognizable near misses. A runbook reference alone does not establish that its Method has been selected for enactment. A viewpoint field does not make a dashboard a U.View. The alarm, a recovery note or a PolicyHook does not prove duty, gate passage or performed Work.
Repair B — ecological and robot line
Draft: “This handle affords pulling.”
Recover the proposed physical claim: ServiceRobot_R2 can pull DoorHandle_17 along Axis_A1 in Window_W1 while the door is closed, under the actual reach, grip and clearance conditions described by ReachEnvelope_RE2, GripClass_G1 and ClearanceProfile_CP3. The reach description is not the physical reach condition itself. PerceptionStack_PS4 is the detector; DepthFrame_883 and ContactModelRun_17 are candidate evidence.
Result with the supplied information. These names identify the question but provide neither the physical obtaining predicate nor its required readings. Return: “Can R2 pull this handle along A1 in W1 under the specified grip, clearance and reach conditions? The applicable physical rule and its supported inputs are still needed.” A rule that requires sufficient contact force or a collision-free path must say so and be supported by the relevant measurements or model result. Naming G1, CP3 or a model run does not establish those conditions.
When that subject rule and the evidence support the claim, return the qualified physical statement directly. If the receiving task instead needs an executable manipulation plan and already has a suitable domain method, use its required observations and constraint representation. Reuse any adequate existing interpretation; producing another recovery note adds nothing by itself.
With the same robot, grip, clearance, reach and door facts, changing PS4 can change detection without changing the physical opportunity. Changing an operator cue can likewise change what the operator notices. Withdrawing the description changes its availability; it does not close the door or remove the opportunity. A different, information-constituted relation must be assessed under its own predicate rather than inferred from this physical case.
Show (Episteme case)
Draft: “This problem asks for a better question.”
Repair A — epistemic probe line
ProblemFramingEpisode_PF3 is the framing account, ResearchTeam_A the intended inquirer and Reviewer_A1 the detector of the problem. Keep ExemplarPack_EP3, OpenIssueSet_O2, EpisodeNotes_3 and CounterexampleCard_2 as its named source context.
For this worked case, take EP3 to compare detected and missed handle opportunities with the robot, grip and clearance facts fixed. O2 asks whether a changed physical opportunity or a changed detector explains the discrepancy. CounterexampleCard_2 records the same physical configuration with a different detection result. The recovered question is: “With the physical conditions held fixed, does changing PS4's detection configuration change which pulling opportunities are detected?” The counterexample motivates that inquiry; it does not already establish its answer or a general detector effect.
This question is the first useful result. If further question construction is needed, the team can select the already admitted ContrastiveQuestioningMethod_Q2; ContrastiveQuestioning_Q2 is a separate MethodDescription with ContrastiveQuestioningMethod_Q2 as its exact EntityOfConcern and substantive claims about how to perform that Method. An explanatory prompt follows B.5.2.0 when its conditions hold. Choosing the inquiry, scheduling it and actually performing it remain separate claims. No invitation occurrence or compulsory OptionSet precedes the question.
Repair B — closure-advance line
Draft: “The draft is ready for formalization.”
Recover the proposed clarification: AuthorCollective_C1 would express DraftHypothesis_H7 using TypedInvariantSet_V1 within ClaimScope_G1. ReviewPanel_R4 points to AmbiguityMemo_8 and ReviewCommentSet_5 as grounds for that move.
Return the question: “Which unresolved claims in H7 can V1 express under G1, and which ambiguities would remain?” If the receiving rule establishes readiness, state its qualified result and the proposed action. The named memo and comments alone establish neither readiness, Formality F, acceptance nor performed formalization. A sufficient question can remain open without becoming a generic invitation record.
Bias-Annotation
- Gov bias: this pattern may tempt authors to smuggle decisions into invitation language. Mitigation: explicit A.6.B claim classification and obligation barrier.
- Arch bias: an interpretation menu can be mistaken for one ontology of all action-oriented claims. Mitigation: recover each subject and its rule; make the menu and recovery record optional.
- Ontology and episteme bias: this pattern insists on separating invitation from evaluation, capability, commitment, and work. Mitigation: first separate a direct contrast from a cross-context semantic-correspondence claim; test F.9 only for the latter, and keep any bounded-use claim and optional F.9.1 reading note separate.
- Prag bias: it favors enactor, site, and action explicitness, which raises authoring cost. Mitigation: stop at a sufficient sentence; recover only details that change the receiving result.
- Did bias: repeated rewrites make the pattern teachable, but may over-formalize early cues. Mitigation: preserve an early cue or open question without requiring a sense token, record or closed answer.
Conformance Checklist (CC-A.6.A)
A text or pattern conforms to A.6.A iff:
-
CC-A.6.A-1 — Recoverable claim or question. The intended claim or question and the participants and conditions needed for its use are recoverable. Apply a direct obtaining predicate when an actual relation is claimed; no common relation kind or sense token is required. An ordinary sentence may suffice, and an unresolved question may be the result.
-
CC-A.6.A-2 — Explicit site and site-facet relation binding. When the site changes the meaning, identify it; distinguish EntityOfConcern, Description episteme, publication and carrier participation where the claim depends on that distinction.
-
CC-A.6.A-3 — Explicit invited enactor. Identify the would-be enactor when the claim or question depends on it.
-
CC-A.6.A-4 — Enactor discipline. When the claim names an actual would-be enactor, identify the System that would act. A cited assignment may designate its holder; it is not itself the enactor.
-
CC-A.6.A-5 — Recoverable action and independently identified Method when selected. State the action or inquiry being discussed. If the result selects a Method for enactment, identify its
U.Methodand keep any MethodDescription separate. A proposed action need not invent a Method, WorkPlan or actual Work. -
CC-A.6.A-6 — Explicit coupling frame. Recover the conditions or coupling relation that determine the claim, when applicable; named configuration objects alone do not establish it.
-
CC-A.6.A-7 — Detector, viewpoint reference, and view separation. When current,
detector, ref-backedviewpointRef, its effective reference scheme, and independent optionalvieware not silently collapsed. The reference resolves to an admitted viewpoint episteme; a cited view already passes E.17.0 independently. -
CC-A.6.A-8 — Lawful normal form. When the receiving use needs one of §4.5's forms, apply its discipline. A sufficient ordinary sentence, claim or question has no additional record requirement.
-
CC-A.6.A-9 — Articulation-hint discipline. If omission changes meaning,
articulationHintis explicit and is not treated as F or as an acceptance state. -
CC-A.6.A-10 — No invitation-as-obligation. An invitation is not silently published as a duty or gate.
-
CC-A.6.A-11 — No invitation-as-work. An invitation is not silently published as a work occurrence.
-
CC-A.6.A-12 — No capability collapse. A situated invitation is not silently rewritten as a general capability claim.
-
CC-A.6.A-13 — No site-participant-property collapse. Affordance language is not published as a monadic site-participant property when enactor, site, and coupling frame matter.
-
CC-A.6.A-14 — No hidden scalarisation.
OptionSetpublication does not introduce a hidden comparator value or ranking without an explicit comparator or policy. -
CC-A.6.A-15 — No silent sense rewrite. State what interpretation changed and how that changes the claim or its use. The optional verbs in §4.8 can express that change.
-
CC-A.6.A-16 — No silent relation-family switch. A changed interpretation or an additional quality, ability, commitment or Work claim is made explicit under its own governor. Use a relation-kind change only when a relation-kind claim changes; two distinguishable sentences need no mandatory pair of records.
-
CC-A.6.A-17 — Bridge accountability. A cross-tradition comparison first states whether it asserts or relies on semantic correspondence between exact senses in different semantic contexts. If yes, it cites an obtaining F.9 Bridge only after the predicate passes and adds a matching bounded-use claim only when a proposed use is live. If no, it uses E.17.ID.CR or the direct relation that supplies the contrast. Any F.9.1 stance note remains optional reader help for an already constituted claim.
-
CC-A.6.A-18 — Boundary-claim hook when needed. Apply L, A, D or E only when the recovered statement is an A.6.B boundary claim. For A, identify the action or application and the predicate governing its admission under the applicable rule; otherwise retain the direct rule for scope, claim use, duty, publication or the actual result.
-
CC-A.6.A-19 — Consequential lexical ambiguity. Action-first wording is repaired when its intended claim, participants or conditions remain unclear for the receiving use. A trigger token alone does not require replacement.
-
CC-A.6.A-20 — Direct semantics for an actual relation claim. An obtaining relation or individuated occurrence uses its own predicate and any needed identity rule under A.6.REL. A recovery note, menu label, detector change or publication event does not supply those semantics or establish world-side change.
-
CC-A.6.A-21 — Material alternatives remain recoverable. If a different interpretation changes a decision, retain the rival and the ground that excludes it, or return the missing discriminating question. Use a separate note only when the receiving use needs one.
-
CC-A.6.A-22 — Record inclusion grants no dependent-kind membership.
viewpointRefresolves under the effective reference scheme to an independently admittedU.Viewpoint; optionalviewnames an independently identified episteme whoseU.Viewmembership follows only from E.17.0 conformance. Neither field nor a recovery note establishes either membership.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits. This pattern turns ambiguous action-oriented wording into a usable subject claim, question or gap. It preserves the distinctions needed for embodied, ecological, learned-policy, interface and control uses while avoiding a compulsory intermediate record.
It also complements C.16.Q: C.16.Q repairs evaluative ambiguity, while A.6.A repairs action-inviting ambiguity.
Trade-offs and mitigations. The pattern adds authoring overhead and can feel heavy in early exploration.
Mitigation: retain a sufficient ordinary sentence, including in technical and normative prose. Expand it when unresolved meaning would change the boundary, automation, assurance or publication use; formal vocabulary alone does not settle that question.
Rationale
Physical opportunities, their detection, operator prompts and inquiry questions can share an action-oriented sentence shape while having different obtaining and identity conditions. Recovering their meaning is a reusable method; their common grammar does not supply a common relation kind.
A universal invitation record would add an intermediate object whose truth conditions the menu cannot establish. A complete sum of independently specified relation kinds could serve a particular receiver, but it would require those predicates, identity rules and a receiving use. Wording recovery can usually stop earlier, at the supported subject claim or question. This reduces representation work while preserving consequential distinctions.
Use C.16.Q for an evaluative repair, A.6.B for the boundary-bearing claim, A.15 for Method/Work distinctions and A.16 for a needed account transition. C.2.3 remains the direct governor of Formality F. A physical-opportunity statement, an open inquiry and a policy decision need not pass through the same intermediate relation.
SoTA-Echoing — choose wording recovery or a domain form by the receiving task
Practice question. For §5.2's “This handle affords pulling,” should the receiver first recover the supported claim or directly produce a domain-specific action representation? The selected answer for ambiguous documentation is §4.0a's six-step recovery, stopping at the useful statement, inquiry or missing basis. The serious alternative is to apply the source's established interpretation and manipulation method directly. Adopt that shorter route when the intended meaning and receiving interface are already settled. Reject choosing an operational form merely because the sentence contains “affords.”
ReKep, PMLR 270 (2025) supplies a concrete form-and-method alternative: language instructions and RGB-D observations can be converted into constraints over 3D keypoints, then used in optimization for robot actions. It is a serious alternative for a manipulation task, not a proposed general theory of wording. Adapt its explicit interface demand to the last branch in §5.2: use the representation when the receiver needs that plan and has the required inputs. Its manipulation results do not establish the truth of this pattern's handle claim or validate the six-step recovery.
Compare the same receiving question and supplied inputs when choosing between recovery and a domain method:
The choice depends on the task, supplied information and required output. Ambiguous documentation needs interpretation before selecting a form; an already understood action task can proceed directly to its domain method. This reasoning supports the distinction but establishes neither a robot effect nor a measured reduction in effort.
The supporting sources constrain different claims:
- Hansen (2024), §2, distinguishes action possibilities from obligations and allows possibilities to escape immediate perception. Adopt those distinctions for the physical case; his account of perception supplies no universal ontology for metaphorical invitations. (Frontiers)
- Vauclin and colleagues (2023) review attunement and action calibration in human person-plus-object systems. Adapt the distinction to the question about changed detection versus changed capabilities or physical conditions. The human findings do not establish the robot case; its physical rule and evidence remain necessary. (Springer)
- Pezzulo and colleagues, in Neural representation in active inference, distinguish roles of generative models in action-perception, planning and imagination. Adapt that distinction when recovering a model-side claim from “the model wants”; the model tendency establishes no duty, explicit rationale or performed Work. (UCL Discovery)
- MOKA (2024) supplies a compact point-based interface between image predictions and robot manipulation. Adopt the principle of an intermediate form with an actual receiver. Its robot-interface use neither makes such a form compulsory for an inquiry nor provides one obtaining predicate for every invitation. (Robotics: Science and Systems)
Reopen the affected recovery when a source-specific meaning or physical criterion changes the supported interpretation, when new observations answer the named gap, or when the receiver now needs an executable interface. Recompare the method if a serious alternative preserves these distinctions with less required work. A new source's date, another field in a record, or shared terminology alone changes none of those conditions.
Relations
- Uses: A.6.P when the recovered content is a relation claim; A.6.REL for its direct predicate and any needed occurrence identity.
- Builds on: A.3 and A.7 for enactor discipline and EntityOfConcern and Description-episteme plus publication and carrier separation; A.15 for keeping invitation distinct from enactment; A.6.B for boundary claim classification; E.17.0 for viewpoint reference resolution and independent view conformance, and E.17 for publication.
- Works alongside: C.16.Q for evaluative language; the two are siblings, not substitutes.
- Coordinates with: C.2.2a, A.16, A.16.1, A.16.2, and B.4.1 for language-state chart positions, admissible moves before post-threshold repair, and retreat when a published recovery result must be reopened; use A.16.0 only when lineage, branch, loss, or an actual responsibility-handoff history itself must be published as an explicit trajectory account; B.5.2.0 for probe-question cases that are still prompt-shaped; C.2.LS, C.2.4, C.2.5, C.2.6, and C.2.7 for language-state readings and the source or use claims required beside them.
- Must not replace: C.2.3 as the single subject pattern for F.
- Uses for shared naming: E.10, F.17, and F.18 when an interpretation label or reusable recovery designation needs a shared name.
Early cues and recovered meanings
Use this method when the wording can support a useful interpretation or a question that distinguishes alternatives. Earlier cues may remain with A.16.1 or B.4.1. A recovered inquiry can remain open, and a recovered physical claim can return its missing rule or fact.
Continue from the recovered result
Apply A.6.B when the recovered claim is boundary-bearing and A.15 when a Method, plan or performed Work question is live. Keep an alert-intervention or operator-intervention reading distinguishable from a generic interface cue when human factors, authority or the policy rule change the result. A common invitation record is not a prerequisite.
Governance boundary
This pattern may cite an F.9 Bridge and bounded-use claim, an optional F.9.1 stance note, an A.16 articulation-state result, authority-reference fields, language-state Characteristic readings from C.2.4, C.2.5 and C.2.7, source and use claims recovered through C.2.6, or their joint profile under C.2.LS; it does not redefine any of them.
A.6.A:End
Function and Functional Precision Restoration (RPR-FUNCTION)
Type: Architectural pattern Status: Stable Normativity: Normative unless explicitly marked informative
Problem frame
Use this pattern when function, functional, functionality, effect, or similar wording leaves an action-changing object, claim, or applicable rule unresolved. The reading may concern architecture, work, method, capability, a system-role kind or assignment, participation, actual functioning, responsibility, quality, mathematics, module allocation, or an interface. These are possible meanings to distinguish, not one semantic kind.
First recover the object or claim and the rule that defines or tests it. Return the repaired wording and next useful action, including any necessary stop. Use the optional FunctionUseRepair note in §4.2 only when a receiving use needs inspectable detail.
Stop when the source cue, entity, value, claim, or claim-bearing episteme, subject pattern, and the next admissible use are clear. If the next step must test whether named participants stand in a relation, add its admitted direct predicate. If it must preserve an affirmative, negative, or modal claim about that predicate, identify the C.2.1 relational-assertion episteme and its claim. If it must track one particular obtaining instance, apply the subject pattern's identity rule and add the separately individuated occurrence. Otherwise leave those three branches empty. Add reusable declaration, other selected assertion, specification, or view episteme, or representation correspondence only when the next step needs it.
Misreadings to repair: a function becomes a root kind; functional architecture becomes a peer ontology beside architecture; a capability becomes a function; a method or work occurrence becomes a function; a mathematical function becomes design ontology; a module allocation becomes functional truth; or a quality claim hides behind "functionality".
What A.6.F buys in practice: the practitioner can keep useful engineering language while naming the object or claim and going straight to its subject pattern. Direct participation, reusable declaration, claim-bearing description, and representation remain separate instead of becoming one generic function record.
Keep already clear wording, including an FPF claim whose object, meaning and applicable rule are recoverable. For a general relation question, evaluative language, grounded architecture adequacy, or an architecture structural view, use A.6.P, C.16.Q, C.30, or C.30.ASV respectively.
E.10.ARCH subject-pattern relation. When E.10 encounters function-like wording whose entity, value, claim, claim-bearing episteme, direct relation, or subject pattern is hidden, E.10.ARCH may apply A.6.F until that object and the remaining action are clear or the wording is lowered to ordinary prose, quote-only wording, reduced-use cue, blocked use, or incomplete rewrite. A direct relation names its actual participants; a reusable RelationSignature and declaration-local SlotSpecs, selected assertion, specification, or view episteme, and representation correspondence are added only for a current receiving use. After recovery, apply the subject pattern; A.6.F alone establishes no architecture, mathematics, quality, work, evidence, assurance, gate, decision, or release claim.
Problem
FPF texts repeatedly use function-like wording for different FPF kinds and relations:
- required transformation or effect in an architecture view;
- capability of a System;
- method wording;
- work occurrence or work result;
- a system-role kind or assignment, participation, actual functioning, or responsibility;
- mathematical function or relation;
- quality, fitness, or characteristic wording;
- module allocation or interface relation;
- functional architecture shorthand.
These uses are all legitimate in ordinary engineering speech. They are not the same FPF object or claim. If the text does not name the entity, value, claim, or claim-bearing episteme and its subject pattern, subsequent reasoning cannot tell whether the sentence is about architecture, behavior, work, a system-role kind or assignment, participation, actual functioning, responsibility, mathematics, module structure, quality, evidence, or decision. When a separate direct relation, reusable declaration, assertion or specification, selected view, or representation is current, identify it as that separate object.
Forces
Solution
A.6.F is an A.6.P RPR specialization for function-like wording. It does not mint U.Function. It assigns the use under repair to an entity, value, claim, or claim-bearing episteme and its subject pattern, then stops unless another claim remains current. It does not package direct relations, declaration-local SlotSpecs, assertions, specifications, views, and representation elements as peer records.
Trigger rule
When function-like wording remains ambiguous, distinguish the readings below. They are possible meanings to inspect, not a U.* kind, claim kind, relation kind, or admission result:
One phrase may combine several readings or transfer metonymically between them. Recover the claim it makes and retain every distinction that changes its use.
- architecture or functional architecture;
- capability, effect, externally promised behavior, or user-visible functionality;
- method wording, work occurrence, or work result;
- a system-role kind or assignment, participation, actual functioning, or responsibility;
- mathematical function, mapping, relation, loss, objective, or value functional;
- quality, fitness, characteristic, score, or proxy wording;
- module allocation, interface, signature, port, API, protocol, flow, or mechanism relation;
- another independently established claim named by value, such as evidence, assurance, gate, decision, or release.
If none of those readings carries a current FPF claim, the wording may remain ordinary Plain prose.
FunctionUseRepair
FunctionUseRepair is an optional pattern-local repair note for a receiving use that needs inspectable detail. Its functionLikeReadingUnderRepair value only helps a reader recognize and dispatch a possible reading; neither that value nor the three scan groups below is a U.* kind, claim kind, relation kind, or admission result. The recovered result belongs in exactGovernedObjectOrClaim under its subject pattern. The note carries no project-publication, evidence, decision, or U.Function authority. FunctionalStructure is an ArchitectureStructureKindRef value under C.30.ASV, not a kernel Function kind.
The repair is complete when a practitioner can name the object or claim, apply its subject pattern, and state the remaining action. When a note is needed, at least one entity or value, claim or claim content, or claim-bearing episteme is required in exactGovernedObjectOrClaim. A source cue stays in sourceCueText; it is not a recovered value.
When a direct relation is current, first name its admitted kind, semantic predicate, and actual participants in directRelationPredicateUse. Add relationalAssertionUse only when one C.2.1 episteme affirms, denies, or otherwise modalizes that predicate. Add obtainingRelationOccurrenceUse only when the receiving use needs one separately individuated obtaining occurrence under the subject pattern's identity rule, applied through A.6.REL; a predicate or assertion never supplies occurrence identity.
Add a reusable RelationSignature and declaration-local SlotSpecs only for reusable typed use; add another selected assertion, specification, or view episteme only when it is a separate claim-bearing object; add a representation and its interpretation or correspondence only when that representation matters, using C.29 when a separate mathematical-representation, transfer or inference question remains. If the text still hides a function, capability, work, method, system-role kind or assignment, participation, functioning, responsibility, module, evidence, gate, or mathematical-function collapse, the repair is incomplete.
Preserve the subject's necessary applicability and stop conditions in the repaired claim. Add blockedLocalOverreadRefs or nonAdmissibleUse as an explanatory guard only under F.19:4's full independent-ground, plausible-reader, contribution, and smallest-clear-correction test. An unused guard may be omitted without an absence entry.
Repair assignments
When a function-like phrase is claim-bearing, recover the object or claim under concern before lowering or rewriting the phrase. C.30.ASV does not define a world-side or view-local FunctionalElement individual. Its FunctionalStructureView is the same ArchitectureStructuralView episteme about one selected functional U.Structure; a FunctionalStructureViewUse may cite FunctionalElementClaim epistemes and other values needed by the use. Required or desired effects, actual transformations, candidate bearers, capabilities, ports, allocations, and correspondences remain separately established claims or values.
If a distinct functional-element individual is needed, first define its predicate and identity in a subject pattern; otherwise stop at the smaller requirement, behavior or effect claim, capability, participant, condition, port declaration, or other directly defined object. A field name or source cue is not a substitute for that object.
Method-description guard. A procedure, code file, solver model, recipe, protocol, or algorithm is only a clue. First identify the knowledge object and the method it is about. Then point to at least one claim that says how that method is done, such as its transformation or enactment concern, applicability, precondition, intended effect or preserved condition, bound, generic participant meaning, or internal method composition. Only then classify that already identified U.Episteme as U.MethodDescription under A.3.2.
A title, author, citation, approval, file form, or runnable artifact alone is a near-miss. If no admitted U.Method is its EntityOfConcern, or no way-of-doing claim is present, do not use U.MethodDescription: keep the actual plan, work, result, formal substrate, mechanism declaration, representation, publication occurrence or form, or carrier with its subject pattern. A different code, text, diagram, or publication form does not decide membership.
If claim content, method, or effective reference scheme changes, C.2.1 first identifies the resulting episteme; then apply A.3.2 to that individual.
Required-versus-actual check. “The cooling loop shall reduce outlet temperature by 8 °C within 60 seconds” remains a requirement or functional-view claim; by itself it identifies no U.Transformation. If a later run changes the loop state, identify that cooling occurrence separately under A.3.4 from the changed loop, boundary and conditions, actual before/during/after facts, and continuity or reidentification rule. Requirement-only material is the countercase and stop: it cannot admit an actual transformation, observed functioning, or evidence of success.
Functional architecture boundary
Functional architecture is the FunctionalStructure case of ArchitectureOf@Context: the declared organization used to relate one selected functional structure to independently established claims about required behavior or effects, capabilities, functional dependencies, and constraints that a holon is to realize, before or alongside allocation to modules, local system-role kinds or assignments, work, evidence, control relations, selected transformation-flow structures, or mathematical descriptions of those structures. Under C.30.ASV, the view is an ArchitectureStructuralView episteme whose EntityOfConcern is that selected structure; it does not define a functional-element individual. A FunctionalStructureViewUse may cite FunctionalElementClaim epistemes and other separately established values needed by the use.
The view keeps requirement, required-behavior/effect, capability, dependency, and constraint claims with their subject patterns; their wording does not turn them into SelectedStructureReference values or actual transformations. An actual-transformation reference is admissible only after A.3.4 independently grounds the occurrence. A selected TransformationFlowStructure, path slice, crossing, flow valuation, or mathematical description may be related to functional structure through C.30.TFS-REL, E.18, or E.18.2, but it is neither the required effect nor the functional architecture itself unless the positive selected-structure co-reference check succeeds.
Function-flow-module alignment note
Recover the local alignment when functional wording touches flow or module allocation but does not yet require a full structural view or A.6.M module-relation repair. Use this note only when the receiving use needs an inspectable alignment record; otherwise state the recovered alignment and boundary in the repaired wording.
The note records only the local function-flow-module alignment and boundary. Its explanatory non-admissible-use guard is optional under the full F.19:4 test and needs no absence entry when unused. Functional architecture, module relation, implemented-interface, evidence-sufficiency, and architecture-decision claims remain with their subject patterns.
Common kind and relation separations
Composability and compositionality
Composability and quality compositionality are separate claims. If the text says parts can be assembled, keep that as a structure or use claim. If it says a quality of the whole follows from parts, assign the quality-composition claim to C.25 and the direct characteristic, measurement, or quality pattern governing that claim:
Compositional formalisms may express composition structures and view or model relations. They do not make safety, latency, reliability, or another quality propagate automatically.
A.6.F defines no separate quality-composition record. Use the claim form supplied by the applicable subject pattern. A composite family uses the C.25 Q-Bundle with its bearer and declared measures. Include scope, a qualification window, mechanisms, status, or evidence when that value changes the quality claim or receiving action. A single Characteristic and its Scale follow A.17 and A.18; use C.16 for a measurement question and C.16.Q when quality wording still needs repair. Keep a causal inference with its causal pattern. Use A.10 when the source-to-use account is implicit or must remain replayable. If a required value cannot be established, keep the dependent quality-composition claim unresolved rather than filling an A.6.F-only schema.
Worked slices
Function-like module claim; no direct relation. A release note says, “The brake-control functional package is in the vehicle-control system.” The receiving question asks what interface BrakeControllerPackage presents in Release-2026Q2 under BrakeControlInterfaceSpec-v5. That question selects the module-interface claim; the adjective functional alone selects neither that claim nor a new U.Function kind. Recover:
exactGovernedObjectOrClaim: A.6.MModuleInterfaceClaimcontent namingBrakeControllerPackage,VehicleControlSystem,Release-2026Q2,VP.ModuleInterface,BrakeControlBoundary, and aninterfaceSpecificationRefthat resolvesBrakeControlInterfaceSpec-v5; its direct-relation disposition isnoDirectRelationClaimed;selectedClaimBearingEpistemeUse:BrakeArchitectureNote_v3 : U.Epistemeunder C.2.1 carries that content and hasBrakeControllerPackageas itsEntityOfConcern;directRelationPredicateUse,relationalAssertionUse, andobtainingRelationOccurrenceUse:not used, because no domain rule has admitted a direct module relation predicate or an obtaining occurrence for this case;- remaining action: apply A.6.M to the declared interface and admissibility conditions; do not infer a function allocation, direct relation, or implemented compatibility from the source phrase.
Interrupted assignment; occurrence identity needed. A maintenance log says, “Robot-7 resumed its inspection function after a documented period with no inspection assignment.” Treat function as a cue. Recover InspectorSystemRole and one declared direct species CellInspectorAssignment <: U.SystemRoleAssignment; then test its direct predicate for Robot-7 : U.System and the species-specific cell and interval participants. Keep Robot7AssignmentLog_42 as the separate C.2.1 episteme that states the interval facts. A.2.1 says that the demonstrated non-assignment period ends the first assignment occurrence and the later resumption begins another. When the maintenance history must distinguish them, apply A.6.REL with that identity rule to keep InspectorAssignment_PreGap and InspectorAssignment_PostGap distinct. A taxonomy or scheme is not an assignment participant, and neither assignment implies inspection Work.
Neighbor claims that need their own relation.
TestArticle-7 participates passively in TestWork-9 during TestInterval-9is not established byTestArticleSystemRoleorTestArticleAssignment-7. Until a direct passive-test-participation predicate supplies participant order and identity, returnA.6.RCD missing-governor[direct passive-test-participation relation]; the tester's Work and F.6 attribution remain usable.Motor-M1 drives PumpAssembly-A during PumpRun-17needs a direct motor-drive-functioning predicate. Assignment, torque capability, and pumping Work remain separate; without that predicate returnA.6.RCD missing-governor[direct motor-drive-functioning relation].Hammer-3 supports PaperStack-9 during Interval-Pneeds a direct artifact-support predicate. Do not replace that claim with an interchangeable list of use, load, support, or function kinds; without the predicate returnA.6.RCD missing-governor[direct artifact-support relation].
Functional architecture phrase. A team says, "the functional architecture is the user journey." A.6.F does not let the phrase create a separate architecture kind. For a receiving use that needs inspectable detail, the repair can be recorded as:
Functionality as quality. A product note says, "new functionality improves adequacy." The repair separates the added-capability or required-effect claim from the quality claim. Capability or effect wording may stay as recognition, but the adequacy claim goes to C.25, C.16, C.16.Q, or the admitted characteristic or measurement pattern that states its bearer and criterion. A.6.F stops once those claims and subject patterns are clear; it adds no reusable declaration, view, or representation apparatus unless the receiving use needs it.
Mathematical function or loss. A model note says, "the loss function explains the holon purpose." The repair keeps the mathematical function under C.29 lens discipline: domain, codomain or relation domain, preserved and lost structure, lens-use admissibility value, and stop condition. The loss may inform a reasoning move; it does not become holon purpose, evidence sufficiency, causal proof, assurance, or project decision by itself.
Pump-station functional dependency. A maintenance note says, "the backup pump function is degraded." A.6.F first separates the required effect, the qualified ability claim about the holder System, the physical module allocation, the performed maintenance work, the evidence relation, and the quality claim. The functional wording may open a FunctionalStructure view under C.30.ASV or go to the capability pattern; it does not by itself prove the pump was tested, authorize operation, or make the backup module compatible with the main line.
Product-platform allocation. A hardware team says, "thermal management functionality moved to the chassis." The repair separates required heat-removal effect, module allocation, interface constraints, signature constraints, architecture structural view, and any evidence or gate claim. A.6.F keeps the function-like wording useful for architecture work while sending module-interface and evidence claims to their subject patterns.
Archetypal Grounding
Bias-Annotation
Scope: unresolved function-like wording that changes an FPF claim or its use.
Use the checklist to verify a repair when needed; it adds no required project form.
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Rationale
Preserve useful function-like wording and clarify unresolved meanings. The smallest useful repair is not a new ontology or a generic record. Name the entity, value, claim, or claim-bearing episteme, apply its subject pattern, and state the remaining use. Add an explanatory rejected reading only under the full F.19:4 test.
This follows A.6.P: recover the direct predicate and participants when a relation question is current; add a reusable RelationSignature and declaration-local SlotSpecs only when typed use needs them; distinguish assertion, specification and view epistemes; and interpret a representation under its applicable correspondence. Use C.29 only for a remaining mathematical representation, transfer or inference question. Under C.30, functional architecture concerns selected structure for a described holon. A selected transformation-flow structure or mathematical graph description requires its own basis.
The pattern keeps ordinary language usable, including an FPF claim whose object and governing rule are already clear. Repair ambiguity when it changes an ontological, evidence, causal, assurance, bridge, gate, work, decision or admissibility claim. A generic record does not supply the missing meaning.
SoTA-Echoing
Relations
Builds on: A.6.P, A.6.RSIR, A.6.0, A.6.5, A.6.B, A.6.C, A.6.9, A.7, E.10, E.10.ARCH, C.2.P, F.18, and E.8.
Coordinates with: C.2.1 when the task must preserve an assertion about the direct predicate; A.6.REL only when the task needs explicit identity for an obtaining occurrence; C.30, C.30.ASV, C.30.TFS-REL, E.18, A.15, A.2, C.29, C.25, C.16, C.16.Q, A.17, A.18, A.10, G.6, B.3, A.20, A.21, C.11, A.6.RSIR, and A.6.M when a module or interface claim is being made.
Does not replace: C.30 grounded architecture and selected-structure adequacy, C.30.ASV architecture structural-view adequacy, E.18 selected transformation-flow structure, E.18.2 mathematical descriptions, C.29 mathematical-lens use, C.25 Q-Bundles, C.16 characterization, A.15 work and method discipline, A.10 or G.6 evidence, B.3 assurance, A.20 or A.21 gate or release records, or C.11 decisions.
A.6.F:End
Module and Interface Claim Repair
Type: Architectural pattern Status: Stable Normativity: Normative unless explicitly marked informative
Problem frame
Use this pattern when module, component, interface, port, platform or open-architecture wording leaves a module-interface claim unresolved. The question is whether a holon is claimed as a replaceable, reusable or separately changed structural unit of a larger holon, under VP.ModuleInterface when that viewpoint matters. Keep already clear wording. Use C.30.STRAT first only when a covered stratification or architecture-operation label still hides the claim; return here if that recovery selects module-interface content. The claim does not itself make a direct module relation obtain.
The first useful output is a sufficient account of the recovered claim or question; an ordinary sentence can be complete. Use ModuleRelationRepairNote when its structure helps the receiving use, including policy, blocked-interpretation and neighboring-claim details only when they change that use:
In this note and the fuller form below, effectiveReferenceScheme carries a rule collection by value with the C.2.1:4.1.2 range EpistemeInterpretationScheme. It must supply the designation and interpretation rules used in the module-interface claim, including its holons, boundary, interface conditions and any asserted substitution or change policy.
Exactly one of interfaceSpecificationRef and interfaceSpecificationGap is current.
noDirectRelationClaimed leaves the direct-relation fields empty. admittedPredicateClaim names an already governed predicate, its participants and the affirmative, negative, modal or unresolved claim being made; it requires no invented obtaining occurrence. admittedRelationAndOccurrence additionally identifies one independently obtaining occurrence when its identity matters. missingGovernor names the participants, proposed predicate, affected use and missing rule.
Missing case facts under an available rule leave a factual question, not a missing governor. A PatternID may locate the rule but cannot substitute for its predicate, participants or facts.
Ordinary use stops when the whole, candidate module, boundary, interface specification or explicit gap, relation disposition, and conditions needed by the selected claim are clear enough to choose the next architecture move. Recover substitution or change policy when replacement or separate change is claimed, and a neighboring subject pattern when another claim remains current. Use the fuller ModuleInterfaceClaim record only when substitutability, conformance, publication, evidence, assurance, change policy, repeated reuse, or cross-team coordination requires durable claim content.
Misreadings to repair: a functional link becomes a module interface; a signature becomes an implemented interface; a port label becomes proof of integration; "open" becomes a decoration; a platform label hides the extension rules; a stratification or architecture-operation source label bypasses C.30.STRAT and mints a false local kind; autonomy-like wording is confused with separate module change policy; and a module diagram starts being used for claims governed elsewhere.
What A.6.M buys in practice: the practitioner can repair one module or interface phrase into usable claim content, distinguish it from an independently admitted direct relation occurrence, see which FPF pattern defines or constrains any remaining non-module claim, and stop before full measurement, evidence, or mechanism-suite records are needed.
Not this pattern when the question under repair is the general architecture claim, selected architecture structure kind, structural view, stratification wording or source-label recovery, function wording, procedural or work-package wording, role or enactor wording, autonomous operation, independent acting, unsupervised decision or action, measurement, modularity characterization, or reusable-structure residue. Use C.30, C.30.ASV, C.30.STRAT, A.6.F, A.15, A.2, E.16, C.31, C.16, or C.31.RSA as appropriate. For any other claim being made, apply the governing FPF pattern and keep A.6.M only for the module-relation and interface-specification portion.
E.10.ARCH relation. A.6.M is the precision-restoration pattern for module-interface relation wording, interface-specification wording, platform-grammar wording, substitutability wording, change-policy wording, and open-architecture module-interface claims. E.10, E.10.ARCH, or C.30.STRAT applies A.6.M only after the recovered result is a module-interface relation, interface specification, platform grammar, substitutability policy, change policy, or open-architecture module-interface claim.
If the source wording is still a stratification or architecture-operation source label covered by C.30.STRAT, apply C.30.STRAT first.
If the claim being made is non-module work, role, evidence, assurance, gate, decision, characteristic, flow, autonomy, component, mechanism, or mathematical-lens use, apply the subject pattern named in A.6.M:12 and keep A.6.M only for the module-interface slice when that module-interface relation remains the claim being made.
Problem
Engineering teams use module language for several different things:
- a component in a part-whole decomposition;
- a replaceable unit under a declared interface;
- a functional element;
- a software package, neural-network block, hardware board, chiplet, subsystem, service, team boundary, or delivery unit;
- a published API, protocol, signature, port, connector, or endpoint;
- a platform extension point;
- a control relation, deployment scope, or stratification or architecture-operation source label that still needs
C.30.STRATrecovery; - an open-architecture claim.
These are useful ordinary words, but they do not establish the same FPF claim. A module claim is not created by a label. A conforming module-interface claim names the candidate U.Holon, larger U.Holon, VP.ModuleInterface viewpoint episteme when needed, boundary, interface specification, admissibility conditions, substitutability policy when replacement is claimed, change policy when separate change is claimed, and any evidence, conformance, or admissible-use claim being made. It remains claim content unless a separate direct relation pattern has admitted a module relation and its obtaining predicate is satisfied.
The practical question is: does this phrase name a module relation, component relation, functional allocation, procedural or work-package relation, system-role-assignment occurrence, direct domain responsibility relation, deployment or placement structure, interface specification, signature declaration, port or endpoint slot, transformation-flow crossing, mechanism realization, platform grammar, control relation, autonomy-like operation claim, source label governed first by C.30.STRAT, or only plain source wording?
Forces
Solution
A.6.M specializes A.6.P for module, component, interface, platform, and open-architecture wording when the recovered result is module-interface claim content, an interface specification, platform grammar, substitutability claim, or open-architecture module-interface claim. Stratification or architecture-operation source labels covered by C.30.STRAT are governed by C.30.STRAT until that repair recovers this module-interface content. A.6.M neither mints root kinds from those labels nor admits a direct module relation from record syntax.
A candidate module is a U.Holon used in a claim that treats it as a replaceable, reusable, or separately changed structural unit of a larger U.Holon, ordinarily under the VP.ModuleInterface viewpoint episteme. The claim names its boundary, interface specification, admissibility conditions, substitutability policy when replaceability is claimed, and change policy when separate change is claimed. Effective reference scheme and U.ClaimScope qualify the claim; an optional selected model-use structure appears only when its organization changes module meaning. None replaces the two holons or makes a module relation obtain.
A FunctionalElementClaim is different: it is a claim-bearing episteme cited by a functional structural view under C.30.ASV, not a root kind or a module relation. It binds required behaviour or effect to bearer or candidate bearer, capability, functional ports, and allocation claims when those claims are current; required or desired content is not an actual U.Transformation.
The relation between functional and module claims is separately governed allocation or correspondence, not identity. One module candidate can correspond to many functional elements; many module candidates can correspond to one functional element; a functional element can remain unallocated; and a module candidate can be present in a module-interface view with no current functional behaviour in the functional view.
Functional ports and module interfaces may both use U.Signature discipline, but they govern different claims. A functional port constrains input condition, output condition, accepted-state, and produced-state slots for a functional behavior or transformation. A module interface constrains boundary, substitutability, compatibility, protocol references, schema references, version policy, change policy, and conformance expectations for a module relation. Do not move a functional-port claim into module-interface structure unless a module-interface or substitution claim is being made.
For modular synthesis, A.6.M supplies only the module-interface claim slice. A synthesis action may align required functional claims under VP.Functional, transformation-flow topology under E.18 and C.30.TFS-REL, control structure under C.30.LCA, procedures and work packages under VP.Procedural, and module and interface claims under VP.ModuleInterface.
VP.AllocationResponsibility is only a recognition cue for allocation or responsibility concerns: a positive responsibility claim needs its domain predicate and supporting participant and applicability facts, with explicit occurrence identity when the receiving use needs it. Missing facts leave that claim unknown; only an absent governing rule leaves an A.6.RCD missing governor.
Use A.6.M to repair claims about modules and their interfaces; non-module candidate generation, allocation, responsibility, evidence, assurance, decision, Work, and characteristic claims remain with their direct patterns.
ModuleInterfaceClaim record
Use ModuleInterfaceClaim only when the light repair note is not enough and durable claim content is needed. Its Plain reading is claim about a module and its interface in a larger whole.
This form is claim content in one C.2.1 episteme. Its identity uses that content, the one entityOfConcernRef, and the effective reference scheme. claimScope qualifies the claim when its coverage matters. modelUseStructureRef is present only when one independently selected model-use structure changes the meaning of module for this claim; it is not a module participant, whole, boundary, or source of relation obtaining. VP.ModuleInterface is a reference to the viewpoint episteme when viewpoint use matters; citing it does not make this claim a U.View.
The interface-specification and direct-relation fields obey the same exclusive branches as ModuleRelationRepairNote. If entityOfConcernRef names an admitted direct module-relation occurrence, the disposition is admittedRelationAndOccurrence and obtainingRelationOccurrenceRef resolves that same occurrence. Under the other dispositions, entityOfConcernRef stays with the module holon or selected dependency structure.
A record, package path, file boundary, graph edge, list position, name or publication does not make a world-side module relation obtain. Its content may supply a claim or grounds; assess those under the applicable rule. A.6.M admits no general direct module relation kind. If the receiving use needs a predicate that no subject rule supplies, use A.6.RCD to settle participant meanings, obtaining conditions, applicability and any needed recurrence or identity rule. Use A.6.REL when explicit identity is needed to distinguish, reidentify or refer to an obtaining occurrence, or to use it as a participant. A separately constituted RelationSignature may declare reusable SlotSpecs; neither declaration nor claim creates the occurrence.
For an already defined domain predicate p(M, W, B) over module M, whole W and boundary B, a practitioner may report that its truth is unknown because required protocol facts are missing. If established facts violate its rule, the practitioner may instead assert that p(M, W, B) does not hold. Both use admittedPredicateClaim, preserving the predicate, participants and grounds without positing an obtaining occurrence. A positive claim may also use that branch when explicit occurrence identity adds nothing. Use admittedRelationAndOccurrence only when the obtaining occurrence is independently established and its identity is needed.
Well-formedness: the claim names both holons, one EntityOfConcern, an effective reference scheme, one boundary, and exactly one of an interface-specification reference and an explicit interface-specification gap. Its direct-relation disposition has exactly the fields required by the selected branch. Optional structure, relation, evidence, mechanism, policy, conformance, source, and reliance references are used only when those objects and claims are current under their direct rules.
Interface specification is not a label
A.6.M calls the independently identified specification episteme an InterfaceSpecification. It is one U.Episteme under C.2.1 whose EntityOfConcern is the boundary named by the module claim. Its identity is <ClaimGraph, that one EntityOfConcern, effective reference scheme>. Its claim content may include:
interfaceSpecificationRef is one U.EpistemeRef constrained to that specification form. Under the effective reference scheme it resolves one already identified InterfaceSpecification; it carries none of the specification content itself. Two spellings or serialized references may resolve the same unchanged specification. Retargeting the reference selects another already identified specification without changing the previous one. Changing identity-bearing specification content, its EntityOfConcern, or its effective reference scheme yields another episteme. When no complete specification is established, keep an explicit interfaceSpecificationGap rather than a partly filled reference.
A signature declares vocabulary, laws, and applicability. A slot or endpoint record names positions and field structure. A protocol or schema constrains interaction. A mechanism reference can substantiate a realization relation. Evidence relations, source relations, reliance relations, and conformance expectations substantiate reliance only when the corresponding evidence, source-use, assurance, or conformance claim is being made. A referenced specification may contain all the conditions needed for a simple interface; its citation alone does not establish that a candidate satisfies them. Any explanatory nonAdmissibleUse or unsupportedModuleInference is optional: retain it only when an independently grounded, plausible misreading changes truth or use under F.19:4.
Repair applications for overloaded words
First repair sequence
- Name the phrase and the practical situation.
- Recover the meaning using §4.3 when needed; a clear meaning needs no additional classification.
- For a module-interface claim, identify the whole and candidate module holons. Keep any other claim with its governing pattern.
- State the boundary and the declared interface specification or explicit interface-specification gap.
- State the admissibility conditions needed by the claim. Recover substitution policy when replacement is claimed and change policy when separate change is claimed. Omit an inapplicable policy; keep a required but unestablished policy as an explicit gap.
- Apply the subject pattern for any remaining non-module claim; §12 identifies the relevant boundaries.
- Stop when the claim, direct-relation disposition and next use are clear. Use A.6.RCD only for a needed missing rule, and A.6.REL only when the receiving use needs explicit identity for an independently obtaining relation.
Worked slices
Ports line up.
Open platform claim. A team calls its platform open. Suppose the published ExtensionGuide-v3 specifies AdapterBoundary and AdapterSpec-v3, lists the AdapterSlot, permits an adapter to be replaced after ProtocolTest-P and SchemaTest-S pass, and requires a major interface version for a semantic change. These supplied facts support a bounded claim:
The first slice makes the missing compatibility basis usable without requiring measurement. The second uses the supplied extension and replacement rules to identify the next action: test a proposed adapter under the two named tests before claiming its conformance. Publication of the rules supports planning; a test result would support a different claim.
Supplier-diversity, procurement suitability, use-context compatibility, business constraint, policy authorization, and provider-selection claims are not module-interface fields. If those claims are being made, A.6.M names only the module-interface slice; non-module selection, procurement, work, role, evidence, assurance, gate, release, and mechanism claims are governed by the patterns named in A.6.M:12.
Team boundary claim.
The third slice uses Conway-like mirroring as a diagnostic prompt. It does not make organization structure, communication relations, a system-role assignment, or delivery responsibility into module-interface structure by identity. Assess any team-delivery or on-call responsibility claim under its own admitted predicate for the actual Systems, scopes and intervals. Retain a supported claim, an adequately grounded negative, or an unresolved factual question as warranted. Return the A.6.RCD missing governor only when a needed defining, applicability or identity rule is absent.
If the repair proposes more modules, more open interfaces or more parallel transformation-flow paths, assess the possible costs before claiming improvement. Synchronization work, communication overhead, conformance work, shared-resource pressure, hidden exception cost, or cross-boundary change cost can become the claim being made. A.6.M repairs only the module-interface relation; speedup, bottleneck, modularity, measurement, work, and quality tradeoffs are governed by C.29, E.18, C.31, C.16, A.15, or the related subject pattern named by value when that related claim is being made.
Lowering and Reopen Conditions
Lower only the part of an A.6.M repair that depends on an unavailable required basis, keeping the supported claim or explicit question usable. A missing interface specification can block a compatibility claim; a missing substitution or change policy blocks the replacement or separate-change claim that requires it. A policy not needed by the selected claim is inapplicable, not a reason to lower that claim.
Reopen the repair when any of these change: the whole holon, candidate module holon, boundary, interface specification, explicit interface gap, substitutability policy, change policy, platform grammar, conformance expectation, relied-on evidence relation, relied-on source relation, source-label recovery from C.30.STRAT, team-boundary correspondence, work correspondence, or the subject pattern for a related claim being made.
If the reopened material is no longer a module-interface relation, A.6.M keeps only the previous repair as source context and the claim being made is governed by the pattern named in A.6.M:12.
Archetypal Grounding
A module claim concerns a holon as a structural unit of a larger whole under a boundary, interface specification and applicable conditions. Replacement needs a substitution policy; separate change needs a change policy.
A software package, neural-network block, chiplet, power converter, document template or organizational unit may be a module candidate. Identify the whole, boundary and interface specification, and the policies required by the replacement or separate-change claim. The claim remains distinct from an independently obtaining direct relation.
A port or endpoint label, flow edge or function name may help locate relevant content. Evaluate that content under the applicable interface, correspondence or evidence rule; presence of the label alone establishes no compatibility.
Holon, relation, and episteme: the candidate module and whole retain their admitted holon kinds. A ModuleInterfaceClaim is content in a C.2.1 claim episteme and may concern the module holon, one selected dependency structure, or an independently admitted direct module relation occurrence; it is not that relation. The InterfaceSpecification is another independently identified episteme, and interfaceSpecificationRef only resolves it.
Framework and module-description epistemes, authoring Work, publication occurrence, publication form, carrier, effective reference scheme, ClaimScope, and optional model-use structure retain separate identities and direct relations. Method descriptions enter as epistemes; method values enter through their Method pattern. Stratification and architecture-operation labels named by C.30.STRAT remain source labels unless C.30.STRAT recovers module-interface claim content that A.6.M can repair.
Bias-Annotation
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits:
- Module and interface talk becomes usable without minting false root kinds.
- Practitioners get a cheap relation repair before measurement or evidence work.
- MOSA and open-system claims become precise enough to make substitution and change reasoning admissible.
- Functional, flow, control, mechanism, work, evidence, assurance, gate, decision, and causal claims stay with their subject patterns.
Costs:
- Ordinary architecture prose loses the convenience of treating boxes, ports, interfaces, and modules as one kind.
- Interface claims sometimes require additional records before substitutability can be relied on.
- "Open architecture" becomes harder to claim because interface publication alone is not enough.
Rationale
The central decision is to treat module as relation-sensitive claim language over admitted holons, not as a root kind and not as a relation admitted by notation. The same system, organization-as-system, episteme, Work occurrence, discipline, or other admitted holon may be claimed as a component under one direct relation, as a module candidate under one interface-and-change claim, or as a bearer/candidate bearer in functional claim content.
effectiveReferenceScheme and ClaimScope make the claim interpretable and bounded. An independently selected model-use structure may qualify model-local meaning, but it neither becomes a holon nor supplies module membership. Method descriptions and publication-family material enter through their episteme and publication patterns; authoring, description edition, publication occurrence, form, and carrier remain distinct.
A.6.M follows A.6.P: overloaded relation language is repaired by recovering the subjects, claim content, direct-relation disposition, qualifiers, admissible use, and sources. A.6.M is the pattern for the module/interface claim repair. A direct module relation, if later needed, is admitted only by its subject pattern with A.6.RCD's participant, obtaining, applicability, and identity discipline; A.6.REL handles explicit identity when the receiving use needs it for an obtaining occurrence.
The pattern keeps measurement out of the first move. A module relation can be repaired before anyone knows whether external coupling density, interface standardization share, evidence reuse, or reusable-structure accounting will be needed. When those claims are being made, A.6.M applies C.31, C.31.RSA, and C.16.
SoTA-Echoing
Relations
A.6.M:End
Relation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Problem frame
Plain name. Relation-declaration slot discipline.
Use this when. Use this pattern after the direct relation kind has been recovered and a reusable typed declaration of its participants is current for another assertion, comparison, substitution, or reference use. Typical triggers are one relation declaration reused across patterns, another relation referring to an explicitly individuated occurrence, or an engineer checking a proposed replacement participant against the declared ValueKind.
Primary working reader and concern. The intended reader is an engineer making one relation declaration reusable.
Primary EntityOfConcern. One SlotSpec declaration in one RelationSignature.
First useful move. Write the readable relation sentence, identify the relation kind and relation-participant meanings, and name where its predicate, applicability and occurrence-identity rule are defined. For every relation-participant meaning whose reusable typed declaration is current, add one SlotSpec to the RelationSignature, using the compact declaration notation SlotSpec = <SlotKind, ValueKind, refMode>. refMode states how an assertion or relation-occurrence description episteme carrying a relation-participant designation denotes the entity named under that meaning. When refMode is a RefKind, the reference retains that RefKind and its referent retains the declared ValueKind; the SlotSpec remains declaration content. If the direct relation or its relation obtaining predicate is still unclear, stop and use A.6.P or A.6.RSIR; declaration notation cannot recover a missing ontology.
First-minute result. For Robot_7 is assigned to InspectorSystemRole for this inspection shift, start from an independently defined species under U.SystemRoleAssignment, here illustrated as InspectionShiftAssignment, and use its predicate and case facts to determine whether a shift occurrence obtains. When reusable participant typing is needed, give HolderSystemSlot the value kind U.System and entity-reference mode; give AssignedSystemRoleKindSlot the value domain InspectorSystemRoleKindDomain and ByValue designation mode. Add another participant only when it changes the predicate or occurrence identity. An assertion designates the occurrence's participants and states its assignmentInterval separately. Stop there unless later work must substitute a participant, distinguish this assignment episode from another, or test an A.2.5 state condition.
What goes wrong if missed. In the readable sentence Robot_7 is assigned to InspectorSystemRole, the holder system, the system-role kind, each declaration-local SlotKind, and each participant designation carried by an assertion episteme can collapse into one word such as role or holder. A later claim then cannot tell what may be substituted, what retains identity, or whether it refers to a system, a system-role kind, an assignment occurrence, an assignment-state relation, or an assertion about either occurrence.
What this buys. Engineers retain a readable relation sentence while its load-bearing uses gain participant typing, unambiguous reference use, and a route to the definitions or constraints for predicate truth and occurrence identity.
Not this pattern when. Use A.6.P or A.6.RSIR first while the relation kind or its participants remain unresolved. Use A.6.REL for relation-occurrence identity, A.6.0 for the containing U.Signature, C.2.1 for an assertion or description, and C.3 for a local kind needed by membership, substitution, typed quantification, or subkind use; use C.3.2 for its declaration, membership judgment, or optional extension. In every other case, find the direct relation's accepted definition before applying this slot discipline.
The following objects meet at this boundary and remain distinct:
- an obtaining relation occurrence in the world;
- the direct relation kind and its predicate;
- a
RelationSignatureepisteme whose content includes SlotSpecs corresponding to the direct relation's relation-participant meanings and restates its predicate, applicability, and identity rule for reuse; - a
SlotSpeccontaining the declaration-local SlotKind name for one relation-participant meaning, its actual-participant ValueKind, and its designation mode; - an assertion or other episteme affirming, denying, modalizing or leaving unresolved whether the predicate holds.
Use the A.6.REL relation-object architecture. A relation-participant meaning specifies one domain contribution to the obtaining predicate. An actual relation participant is an entity participating in an obtaining occurrence under that meaning while retaining its own kind. A SlotSpec is declaration content corresponding to the participant meaning. A relation-participant designation is a value or reference carried by an assertion or description to designate the entity in that participant meaning. The entity is an actual participant in an obtaining occurrence only if the predicate holds; correct designation also serves negative or unresolved claims without establishing participation. Source-specific vocabulary retains its meaning until the applicable declaration or representation correspondence relates it to the FPF object.
A RelationSignature is a declaration episteme whose content includes SlotSpecs for reusable relation semantics. A world-side relation obtains under its direct predicate independently of those epistemes, and its own rule supplies any needed occurrence identity.
In Tech register, SlotKind is the declaration-local kind by which one RelationSignature distinguishes a relation-participant meaning. World-side relation prose names the meaning and actual participant directly; the relation occurrence contains no SlotKind. In an assertion or relation-occurrence description episteme, the corresponding SlotSpec distinguishes a relation-participant designation carried by value or by a reference of the declared RefKind. External representation elements retain their source-specific names. A declared correspondence must relate such an element to a named SlotSpec before an FPF relation claim can reuse it.
Problem
The engineering problem appears when the same relation declaration is used in another claim, substitution, or comparison. A ValueKind that covers participants for which the predicate has different meanings makes typed reuse unsound. A reference value leaves its referent kind unstated. A designator for an actual participant is promoted into a U-kind. A role value is confused with the system that holds it. A verb-shaped predicate is read as proof that the relation is work, a method, a transformation, or an acting holon.
These errors change which substitutions are valid, which object a later claim may reference, what makes the relation obtain, and which definition or constraint the repair must preserve.
Forces
Solution
Apply relation-declaration slot discipline only after the direct relation and its relation-participant meanings have been recovered. Give every relation-participant meaning needed by the current typed use one complete SlotSpec in the RelationSignature. Let the direct-relation definition supply the obtaining predicate and occurrence-identity rule. Follow the A.6.REL minimum-current-object rule: a later use adds only its current object and the direct relation to an already recoverable object rather than restating the complete relation-object architecture.
Ontological status of the discipline
A.6.5 constrains one SlotSpec declaration belonging to one RelationSignature. Operation argument and result declarations remain under A.6.1; mathematical operands and their order remain representation elements; use C.29 when that representation is used as a declared mathematical lens.
A.15.3 may cite one SlotSpec as the target of a planned participant designation inside a U.WorkPlan. That citation does not fill the SlotSpec, extend SlotSpec to another description family, make the planned designation an actual participant, or make the direct relation obtain. Planned operation arguments and results instead cite their A.6.1 declarations. Only a declaration-local participant specification inside one RelationSignature is a SlotSpec. Method-description, plan, work, evaluation, card, schema, and record fields retain the kinds and declaration rules supplied by their defining patterns. A field that receives relation semantics follows the applicable declaration or representation correspondence route in §4.2; the field, SlotSpec, designation, and actual participant remain distinct.
Use each object's defining rules
None of these objects gets its identity or truth condition from A.6.5. A.6.5 supplies the participant-declaration and designation-typing discipline at their shared boundary.
Declare one complete SlotSpec for each relation-participant meaning needed by typed reuse
The following code block is a compact representation of a declaration. Its assignment mark, angle brackets, order, and alternatives are notation elements.
SlotKind is the declaration-local kind by which one RelationSignature distinguishes one relation-participant meaning. HolderSystemSlot and AssignedSystemRoleKindSlot are different SlotKinds inside the InspectionShiftAssignment declaration even when a receiving assertion designates the holder by reference and the assigned system-role kind by value. A receiving semantic field is covered by an explicit declaration against one SlotSpec. An external or independently named representation field keeps its source name and requires an explicit correspondence to the declared SlotSpec; use C.29 when that correspondence is part of a declared mathematical-lens use. Neither route makes the field a SlotSpec or the designation an actual participant. A mathematical operand or numbered argument belongs to its mathematical representation, not to the relation declaration.
ValueKind is the world-side kind admitted for an entity designated under the declared participant meaning. Recover it from the accepted declaration that defines that kind. The declaration may settle a durable U-kind, a current C.3 kind, a Concept-Set entry, or an imported sort whose bridge states the corresponding FPF kind. If one proposed ValueKind hides several kinds for which the predicate has different meaning, recover their common kind or split the relation kind. A prose list of alternatives does neither.
RefKind is the kind of reference used when a named-use assertion or relation-occurrence description episteme carries a relation-participant designation by reference. A system applying the declared resolution Method obtains a referent of the declared ValueKind; resolution alone does not establish participation. U.EntityRef, U.HolonRef, and U.EpistemeRef are examples only where their RefKind declarations and admission predicates apply. SelectedStructureReference uses the bounded declaration and resolution criterion in A.22:4.9. The shorthand byRef is usable in a compact local sketch only when the RefKind is declared next to that sketch; it is not a complete refMode by itself.
ByValue means that an assertion or description carries a value as its participant designation. By reference means that it carries a reference value of the declared RefKind. In either case, check the designated entity against ValueKind separately from checking whether the predicate holds. A reference retains its RefKind, its referent retains its own kind, the SlotSpec remains declaration content, and any obtaining occurrence retains its direct identity.
Naming and source-token repair. Use ...Slot for a declaration-local SlotKind inside one RelationSignature. Use ...Ref for a reference kind or value, distinguishing that reference from its referent. For example, HolderSystemSlot is the SlotKind, U.System is the participant ValueKind, and Robot_7_Ref : U.EntityRef designates Robot_7 : U.System. If a relation independently admits a reference itself as a participant, retain that reference's kind and do not substitute its referent. Split a source word such as holder when it conflates these meanings. A source field keeps its own name and is related to the declared SlotSpec through the applicable declaration or representation correspondence.
Apply the well-formedness constraints
A system performing typed substitution keeps the SlotSpec fixed, resolves the designation under its declared scheme when refMode is a RefKind, and checks the designated entity against the ValueKind; the designation must still satisfy the declared refMode and, when applicable, RefKind. A system performing retargeting changes a reference value in an assertion or description while preserving SlotKind, ValueKind, and RefKind. Neither designation operation by itself changes a world-side participant or makes the direct predicate true. The identified direct-relation definition supplies that predicate and identity rule; the current case must supply the relevant facts or constituting history. A system applies the direct obtaining test to those facts or constituting history, and a claim-bearing episteme records the warranted affirmative or negative claim, or leaves the factual question unresolved. Only when an explicit reliance judgment is current does A.10 or the receiving evaluation separately record supported, refuted, or unresolved reliance. Type compatibility and assertion form do not by themselves establish obtaining or occurrence identity. Evidence supporting the case conclusion and any constitutive contribution are governed separately by the relevant evidence and direct-relation rules.
Distinguish predicate grammar from holonhood and agency
A relation predicate is often written as a verb phrase: a system is assigned to a system-role kind, a part belongs to a whole, one claim supports another, or one occurrence results from Work. The grammatical verb only helps express the predicate. It does not settle the ontological kind of what the expression denotes.
Use the following definitions for that distinction:
A.15.1andA.3.1supply the constructive assembly, composition, identity, and meta-holon-transition conditions that admitU.WorkandU.Methodas holon kinds.U.Transformationis instead a root U-kind underA.3.4for one independently grounded actual bounded change. Verb-shaped wording proves neither classification.- One context-local system-role kind is admitted under
C.3and described throughA.2; it is neither a holon nor an assignment. An admittedU.Systemparticipates as holder in an assignment occurrence whose species is declared underU.SystemRoleAssignment. U.Relationis an individuable obtaining relation occurrence underA.6.REL. A SlotSpec does not give it constructive parthood or meta-holon transition and does not admit it as a holon.- Only an admitted
U.Systemacts. A system may be classified by a local system-role kind and may participate as holder in an obtainingU.SystemRoleAssignment; neither the kind nor the assignment acts. Work is performed, a Method is applied in Work, and a transformation occurs or is carried out.
When one word could denote a relation predicate or a holon occurrence, first ground the participants and ask what obtaining or occurrence identity rule the receiving claim needs. Then find its definition. Do not decide by part of speech.
Predicate grammar also decides neither claim polarity nor reliance. An ordinary relational assertion states affirmative or negative polarity for the direct predicate; a forecast, scenario, counterfactual, permission, or other claim family retains the rules that define that claim family. Only when an explicit reliance judgment is current for the declared use does A.10 or the receiving evaluation separately state supported, refuted, or unresolved reliance. Those claim-side distinctions do not by themselves make the world-side relation obtain; any constitutive effect follows the direct relation's rule.
Keep ordinary predicate parameters outside SlotSpec
A reusable predicate definition may be an ordinary A.6.0 U.Signature without being a RelationSignature. Its semantic parameters are not SlotSpecs unless an independently admitted direct relation kind has world-side participant meanings that a typed receiver must reuse. In particular, the dependentContent and baseContent parameters of RuleContentBasisFindingDefinition@R7 are NonemptyClaimContent values (C.2.1:4.1.2) in a predicate declaration, identified by their interpreted claims and selected semantic relations. They do not name relation participants, SlotKinds, occurrence positions, or a new relation kind.
A C.2.1 assertion of derivedUsingRuleContent or evaluatedAgainstRuleContent designates those values and its derivation or criterion-selection claim. A record or formula may represent the parameters; use C.29 when that representation is used as a declared mathematical lens. Table shape does not turn the parameters into SlotSpecs. If later work proposes a relation kind, it needs an independent A.6.RCD account of participant meanings, obtaining, applicability and a direct occurrence-identity rule. E.24 governs a proposed framework pattern, and E.24.UK applies when a new U-kind is proposed; the predicate declaration supplies none by implication.
Use progressive elaboration
Start with the lightest object that supports the named engineering use. The branch diagram maps three independent receiving-use thresholds that share one recovered direct relation; none is a prerequisite for either of the others:
The branches are independent thresholds; explicit occurrence individuation does not require a RelationSignature. The direct-relation definition supplies the obtaining predicate and direct occurrence-identity rule, while current case facts or constituting history must satisfy the predicate before that rule distinguishes an occurrence.
The local-kind branch does not turn every participant qualification into a kind. It is justified only when membership, substitution, quantification, or U.SubkindOf reasoning will be performed. C.3.2 supplies the KindSignature, pre-judgment admissibility, membership judgment, and any separately needed extension; a local-kind judgment does not require a RelationSignature or a materialized extension.
Dispatch the world-side fact, claim, and local kind
Keep the direct relation fact under its relation pattern, the claim under C.2.1, and introduce a C.3 local kind only when membership, substitution, quantification, or typed reasoning is current.
The declaration's local ValueKind constrains the actual participant corresponding to that meaning; when typed quantification is current, a separately defined C.3 local kind and its membership rule supply the reusable classification.
Read the SlotSpecs of a Direct System-Role-Assignment Species
A.2.1 defines the U.SystemRoleAssignment relation family through directly declared species. The family has no root RelationSignature that hides several participant laws. Conditional on an independently defined two-participant InspectionShiftAssignment species, a compatible RelationSignature declares the following SlotSpecs under A.6.5. Its predicate, applicability, and InspectorSystemRoleKindDomain remain supplied by that species' definition, not by the family citation:
Every assignment species declares its own participant meanings, predicate, applicability, and occurrence-identity rule. It adds another participant meaning only when its corresponding participant changes the predicate or occurrence identity. A KindSignature, system-role-taxonomy episteme, effective reference scheme, bridge, or model-use structure may interpret a receiving assertion or use when needed; it is not another participant merely because it helps interpret the claim.
assignmentInterval is not another SlotKind or a ValueKind admitted for a relation participant. It is a local content value in an assignment assertion or relation-occurrence description. The field states the currently known temporal extent of one occurrence, including an explicit open end when the occurrence is current. Under A.2.1, an occurrence of one direct species begins when its predicate starts obtaining for all fixed actual participants and continues while it obtains without interruption. A later assertion that supplies the end time can refer to the same occurrence when obtaining was uninterrupted. C.2.1 identifies the revised assertion separately. A missing-evidence interval remains unknown and establishes neither continuity nor a split. The direct rule ends the occurrence when a participant changes or its predicate ceases to obtain; demonstrated non-assignment supports concluding that it ended. A.2.5 defines assignment-state predicates and direct state relations; the patterns for capability, performed Work, and supporting claims retain their distinct definitions.
Recover interface and port relations before declaring slots
Keep recognizable source words such as interface, port, endpoint, API, and signature in the recognition sentence; do not erase them and do not promote them into a generic U.Interface. Then use this sequence:
- Repeat the source sentence so the practitioner can still recognize the situation.
- Say in ordinary language what connects, crosses, or is transferred between which entities.
- Recover the direct relation and its definition. If no current definition supplies the needed participant meanings, predicate, applicability, and identity rule, require
A.6.RSIRor record one missing-relation result naming the proposed participants, required predicate, and receiving use. - Only after the direct relation's definition is recovered, let its
RelationSignaturedeclare the SlotSpecs for participant meanings reused by the receiving typed claim.
Compact contrast. In “the evaporator outlet interfaces with the compressor inlet,” keep interfaces for recognition. If the intended claim is that refrigerant crosses from one named outlet to one named inlet, name that medium and those two endpoints and recover the transfer-relation definition before declaring any slots. If interface instead names a diagram boundary, API description, protocol, or publication form, use the definition for that object and use. A catalogue of possible participants closes neither branch; without a definition of the direct relation, stop before a RelationSignature.
Name the operation by the object that changes
F.18 supplies the rules for durable name designation; participant-designation substitution and reference resolution do not. When a system selects a method at run time, use the definition of that method family or selector; A.6.5 supplies no method-selection operation. Do not rename that choice with the generic slot binding metaphor. If early or late timing matters, name which operation in this table is early or late.
Archetypal Grounding
System-role assignment: first minute, substitution, and repeated occurrence
First minute. Assume the case facts explicitly: Robot_7 is an admitted U.System; InspectorSystemRole is a local system-role kind; and InspectionShiftAssignment <: U.SystemRoleAssignment declares only two participant positions, holder System and assigned system-role kind. InspectionShiftAssignment-17 is the occurrence with those values that obtains without interruption from 09:00 to 17:00 on 13 July. A.2.1 supplies the family and continuity discipline; it does not inspect this robot or warrant the assertion. The species predicate, applicability, and InspectorSystemRoleKindDomain must come from the independent InspectionShiftAssignment definition, which is assumed but not supplied here. The directClaimFamilyRef below is a placeholder for that source. The stated case facts satisfy that predicate, and the SystemRoleAssignmentAssertion records affirmative polarity. Any evidence and reliance posture remain separately established. The following field block represents that assertion episteme:
The two labels inside participantDesignations are convenient source-side labels in this compact representation. An explicit representation correspondence relates each label to the SlotSpec identified by the matching SlotKind in the InspectionShiftAssignmentRelationSignature; equal spelling does not identify field and SlotKind, and another source field keeps its own name. assignmentInterval is a different assertion field and corresponds to no relation-participant SlotSpec. Robot_7_Ref : U.EntityRef resolves to Robot_7 : U.System; InspectorSystemRole is carried by value under the declaration-local InspectorSystemRoleKindDomain. The assertion does not create the assignment, and neither the system-role kind, assertion, nor assignment performs inspection Work.
If inspection admission also needs InspectionReady, A.2.5 tests InspectionShiftAssignment-17 against that SystemRoleAssignmentStatePredicate. The resulting SystemRoleAssignmentStateRelation is separate from the assignment and has its own maximal continuous truth interval. The assignment may continue while that state relation ceases to obtain.
Substitution. Assume Robot_8_Ref : U.EntityRef resolves to another admitted Robot_8 : U.System. Replacing only the HolderSystemSlot designation with Robot_8_Ref passes the declared ValueKind check, but it does not create an assignment for Robot_8. Current case facts must separately satisfy the direct InspectionShiftAssignment predicate before an affirmative assertion is warranted. The proposed designation can therefore be type-correct while the direct claim remains negative or unresolved.
Repeated occurrence. If the same two participants enter another inspection shift after a demonstrated non-assignment period, the A.2.1 continuity rule ends the first occurrence and starts another. A copied field block or reused row key does not merge them. Conversely, an assertion that closes an open assignmentInterval can refer to the same uninterrupted assignment; an evidence gap alone does not split it. Under that continuing assignment, true → false → true for one fixed A.2.5 predicate creates two assignment-state-relation occurrences without creating another assignment.
Hypothetical physical-assembly boundary
Bearing_B isPartOf Pump_P may remain a readable source claim, but current A.14 supplies no generic or installed-part occurrence-identity rule based on removal, reinstallation, installation interval, or installation work. PartHolonSlot, WholeHolonSlot, and their RefKinds are therefore only a hypothetical declaration candidate until an accepted direct part-relation pattern states the participant meanings, predicate, applicability, and same-versus-new-occurrence rule. Do not claim current conformance or an individuated part-relation occurrence from this sketch.
Conditional on such a future declaration, changing a proposed part designation from Bearing_B_Ref to Bearing_C_Ref could be ValueKind-compatible while the direct relation remains false because current case facts do not satisfy its predicate. Until that parthood relation is defined, keep the bearings, pump, installation work, proposed part relation, assertion, designations, and representation separate. The counterexample demonstrates that typed substitution cannot create obtaining; it does not supply the missing parthood settlement.
Episteme fields are not relation participants by table shape
C.2.1 identifies an evaluation episteme by its EntityOfConcern, ClaimGraph, and effective ReferenceScheme. An EntityOfConcernRef designates that entity when such a reference is used. A card or tuple view may contain visible fields such as entityOfConcernRef, claimGraph, and referenceScheme. Their co-occurrence in one record does not by itself establish another world-side relation, make the fields participants, or declare SlotSpecs for them.
When a direct relation among an episteme and other entities is current, its definition states the relation kind, participant meanings, obtaining condition, and occurrence identity, and its compatible RelationSignature contains the needed SlotSpecs. A.6.5 supplies the rules for typing participant designations in a receiving assertion. This prevents a convenient episteme form from becoming a pseudo-relation merely because it can be drawn as a tuple or table.
Relation-dependent result wording
After machining, the machined component can remain the same physical entity in a changed state. It does not acquire a special result kind. Start with one question: did this same component continue through the change, or did a new entity begin?
- Same component continued. Name that component, the characteristic that changed, and the machining transformation. Use the pattern that defines that characteristic and A.3.4 for the bounded change. The component's identity continues; calling it the work's “result” adds no kind, participant meaning, or relation.
- A new entity began. Use this branch only when a current definition supplies an admitted identity-inception predicate and identity rule and the current Work and change facts satisfy them. If no such definition exists, return one missing identity-inception result naming the candidate entity, relevant work and change facts, required inception predicate, and receiving use. Do not infer a generic work-result relation.
- The sentence names another relation. Rewrite it with its one verb and participants before declaring slots. For example,
Component_C was delivered to AssemblyCell_2selects one candidate delivery claim about that item and receiver, not aresultkind. Recover that direct relation's definition and any additional participant meanings it requires; if that definition cannot be recovered, return a missing-relation result. Handle an evaluation or acceptance sentence separately when that is the wording rather than listing possible pattern families.
Only the direct relation selected by one of those sentences receives a compatible RelationSignature, and only when reusable typed use is current. Its assertion episteme records that relation; A.6.5 neither invents a broad result participant nor turns the domain choice into a catalogue.
Formal reduced case
The expression 3 < 5 is notation in a mathematical assertion. Its numerals, comparison sign and operand places are representation elements; they are not thereby SlotSpecs. An ordinary comparison can stop with its mathematical meaning. Suppose a later FPF use needs to substitute operands under one reusable typed lesser-than declaration. The direct-relation definition must then supply the entities denoted by the numerals, the lesser-number and greater-number participant meanings, obtaining condition and direct occurrence-identity rule. A compatible RelationSignature may declare LesserNumberSlot and GreaterNumberSlot, with a correspondence from the representation's operand places and designations. Operand order remains local to the representation. The mathematical interpretation and applicable rule supply the comparison's grounds; notation shape alone supplies no FPF relation declaration. This receiving use needs typed substitution but no explicit occurrence individuation, so the engineer stops there.
Bias-Annotation
This pattern has a typed-declaration bias because it serves relation uses that depend on reusable participant typing. Progressive elaboration limits that bias: ordinary users stop at a readable relation sentence when no receiving use depends on SlotSpecs.
It also has a logic-facing bias because predicates and typed declarations make substitution and comparison reviewable. Constructive FPF adds what that logical form alone cannot supply: grounded participants and direct rules for obtaining and occurrence identity.
A declaration episteme describes reusable relation semantics; a separate representation episteme may represent an assertion or relation-occurrence description. Neither episteme is the world-side relation occurrence by form. Publishing an unchanged episteme preserves its C.2.1 identity; any effect on a world-side occurrence follows that occurrence's direct rule.
Conformance Checklist
- The direct relation kind and the definition of its predicate, applicability, participant meanings, and occurrence-identity rule are named before SlotSpecs are declared.
- Every participant meaning needed by reusable typed use has one complete
<SlotKind, ValueKind, refMode>SlotSpec in theRelationSignature. - Each SlotKind is local to the one
RelationSignaturethat contains its SlotSpec. - World-side relation prose names participant meanings and actual participants. Declaration prose uses
SlotSpecfor the complete declaration and...Slotfor its declaration-local SlotKind. Receiving-episteme prose distinguishes a designation from its referent, using...Reffor the reference kind or value. For a field receiving relation semantics, apply the §4.2 declaration or representation-correspondence rule. Position and place remain ordinary representation words unless a declaration establishes a SlotSpec. - Each ValueKind is exact enough for the direct predicate and does not combine participant kinds for which the predicate has different semantics.
- An assertion or description episteme that designates a participant by reference names the RefKind and resolves it to the declared ValueKind.
- The actual relation participant, its reference, reference resolution, SlotSpec declaration, participant designation in the assertion, and relation occurrence remain distinct.
- A C.3 kind is introduced only for a current typed-quantification, membership, substitution, or subkind use.
- A verb-shaped predicate is not used as evidence of work, method, transformation, agency, or holonhood.
- Only an admitted
U.Systemis admitted forHolderSystemSlot. Each species underU.SystemRoleAssignmentdeclares itsAssignedSystemRoleKindSlotdomain and any additional participant meaning whose value changes the predicate or occurrence identity. U.WorkandU.Methodrely on their own constructive holon tests, whileU.Transformationrelies onA.3.4's actual-bounded-change identity; A.6.5 admits none of them by grammar.- The direct-relation definition supplies the obtaining predicate and occurrence-identity rule; current-case facts or constituting history supply the factual basis; a claim-bearing episteme records polarity; and evidence or reliance remains a separate judgement.
- A declaration, assertion, description, representation, or publication episteme does not create the world-side relation by form.
- Ordinary use can stop before signatures, explicit occurrence identity, or C.3 kind derivation when the receiving use depends on none of them; typed reuse, occurrence identity, and local-kind quantification are independent thresholds, and none is a prerequisite for another.
- A relation fact, an episteme claim, and a locally derived kind are handled by the patterns that define those respective objects.
- A SlotSpec declares one direct-relation participant meaning inside one
RelationSignature. Method-description, operation, plan, work, evaluation, representation, card, schema, and record fields retain the kinds and declaration rules supplied by their defining patterns; a field that receives relation semantics uses the applicable §4.2 route. - An A.15.3 planned-filling row may cite a SlotSpec, but the planned designation remains plan content and establishes neither an actual participant nor relation obtaining.
- Interface, port, endpoint, API, and signature language remains available for recognition. The text states what connects, crosses, or is transferred between which entities and recovers the direct-relation definition before declaring SlotSpecs; an unresolved case requires A.6.RSIR or a missing-relation result.
- When result wording leaves continuation or inception unresolved, determine whether the same entity continued or a new entity began. Recover a separately asserted delivery, acceptance or evaluation relation from its predicate and participants; clear wording needs no additional history inquiry. A catalogue or generic result kind cannot supply a missing relation.
Common Failure Modes and Repairs
Consequences
Benefits. Typed relation reuse becomes reviewable without treating an assertion or storage record as the world-side relation. Substitution checks can name the SlotKind and participant ValueKind. Reference changes can be distinguished from referent changes. Local system-role kinds remain separate from their holder systems and assignment occurrences, and relation predicates remain separate from Work and agency.
Costs. Load-bearing relation patterns need participant ValueKinds and designation modes. A proposed ValueKind may require a relation-kind split when the direct predicate has different semantics for different participant kinds. Existing compact byRef sketches may need adjacent expansion before another pattern can rely on them.
Limits. A.6.5 is limited to SlotSpec declarations and participant-designation typing. It neither defines the direct obtaining test nor decides a current case. The direct-relation definition supplies the predicate and identity rule, current facts or constituting history supply the case basis, and a claim-bearing episteme states the result. Separate patterns define evidence, reliance, model-use structure selection, and domain-interface semantics.
Rationale
SlotKind, ValueKind, and refMode answer three different engineering questions about one RelationSignature: which participant meaning does this declaration distinguish, what kind must an entity designated under that meaning have, and how does a receiving assertion or description episteme designate that participant. When refMode selects reference designation, RefKind names the reference kind. Keeping the answers separate is enough to support typed substitution and reference use without adding a universal relation record.
The direct-relation definition remains essential. A pair of typed participants does not say whether the relation obtains or whether repeated occurrences with the same participants are identical. Constructive ontology therefore combines logical slot discipline with grounding and domain identity rather than treating a schema as the world.
The predicate boundary prevents a second collapse. Natural language often verbalizes relations, work, methods, and transformations. FPF admits their kinds through direct ontological tests, not through grammar. This keeps only systems as actors and as actual participants corresponding to HolderSystemSlot, while preserving the accepted holonhood of work and methods and the separate actual-bounded-change identity of transformations.
SoTA-Echoing
Relations
A.6.0definesU.SignatureandRelationSignature; A.6.5 supplies SlotSpec declaration discipline inside their vocabulary declarations.A.6.RELdefines explicit relation-occurrence individuation and the progressive threshold for stable reference.A.6.PandA.6.RSIRrecover the direct relation and its participants before slot typing begins.- Use
A.2.1for the system-role-assignment family's discipline and continuity rule, the direct species definition for its predicate, applicability, participant meanings, and assigned-kind domain, and A.6.5 for the SlotSpec reading of that species' declaration. C.2.1defines episteme identity, assertion and description content, and their semantic fields; A.6.5 §4.2 gives the declaration and representation correspondence routes by which such fields receive relation semantics while field, SlotSpec, designation, and actual participant remain distinct.C.3andC.3.1define local participant kinds, subkind relations, and continuity when membership, substitution, typed quantification, or subkind use is current;C.3.2supplies the KindSignature, membership judgment, and optional extension.A.15.3may cite a RelationSignature SlotSpec for a planned participant designation; A.15.2/A.15.3 define the planned claim, the direct-relation definition supplies the participant meaning and later actual-participation predicate, and A.6.5 supplies only SlotSpec declaration discipline. Operation arguments and results remain A.6.1 declarations.A.15.1andA.3.1define the constructive holonhood and identity of Work and Methods;A.3.4defines the actual-bounded-change identity of transformations;E.18defines selected transformation-flow structures over those independently defined transformations and adjacent loci.A.1,A.2,A.2.1, andA.15keep acting systems, local system-role kinds, system-role assignments, Methods, and performed Work distinct.- Use
A.2.4for compact episteme evidence-use and status-use relation SlotSpecs,A.10for the full evidence-provenance path, andF.10for durable status semantics. - A named C.30 architecture-relation pattern supplies the rule for its relation.
A.6.Mrepairs module-interface claims and specifications; it admits no general direct module relation. After A.6.RSIR recovery, a direct relation needs its own definition before A.6.5 declares its SlotSpecs. C.29governs a declared mathematical-lens use of tuple, graph, database, or mathematical representations of a relation, assertion, signature, or occurrence description.E.10supplies wording-use recovery,E.24.UKsupplies the U-kind admission test, andF.18supplies designation guidance after the object is known.
A.6.5:End
Base Declaration Discipline: Say What Something Depends On
Status: Stable Type: Definitional relation-discipline pattern
Plain-name. Saying what something depends on.
Use this pattern when a sentence says that one thing is calibrated to, based on, attributable to, constrained by, or otherwise usable relative to another, and the relation is still hidden by words such as anchor, support, ground, or based on.
First useful move. Name the dependent and base, state the direct relation in an ordinary sentence, and apply that relation's own predicate to the current facts. Stop when this readable assertion answers the receiving question.
What goes wrong if missed. An umbrella word hides the relation kind or reverses its participants. At the opposite extreme, a simple assertion is expanded into slots, witnesses, editions, and a new record even though no later use needs them.
What this buys. A direct, testable assertion first. Scope, time, evidence, a reusable RelationSignature, or a reviewable record is added only when the direct predicate or one named receiving use needs that distinction.
Not this pattern when. If the direct relation and its participants are already clear, use its direct pattern. If support means evidence use, assurance, ordinary help, work enablement, navigation, source description, or another non-basedness reading, use that reading's direct pattern instead.
Problem frame
FPF repeatedly needs to express a family of situations of the form:
The use, admissibility, or interpretation at issue depends on an explicit relation between the dependent and its base.
Examples occur across several disciplines:
- reference selection and identification (IDs, handles, pointers, registries),
- scale/datums/calibration (measurement traceability, baselines, normalisation),
- grounding of properties and abstractions to objects (attribution; “this property is about that thing”),
- admissibility/assurance (claims linked to evidence, checks, or proofs),
- publication discipline (what a statement is fit to be used for, where, and when).
An umbrella metaphor such as anchor can leave different relations and operations indistinguishable. When it hides the relation, recover that relation so its direction, invariants and applicable rules are clear.
This family can expose a typing mismatch: the named dependent or base may not satisfy the participant kind required by the direct relation, or its designation may not satisfy the receiving declaration's reference mode. Resolve the mismatch under the applicable rule; renaming participants or reversing direction does not fix it. Add SlotSpecs only when a reusable declaration needs them.
Every ordinary basedness assertion first needs only:
- the dependent;
- the base; and
- the direct relation and its obtaining test.
Scope, time, evidence, continuity, or a reusable declaration is added only when the direct predicate or one named receiving use depends on it. Until the direct relation is named, umbrella words such as anchor, ground, attach, support, or based on usually mean only:
“There is an under-described relation here.”
The repair is therefore progressive: recover and test the direct relation, stop if the assertion is enough, and materialize declaration or assertion machinery only for a later use.
Problem
Typical failure modes this pattern is designed to eliminate:
-
Relation-kind elision. One verb phrase is used to cover: ID-to-registry reference, claim-to-evidence admissibility, calibration-to-standard, property-to-object attribution, policy gating, etc. Rules and invariants cannot be stated because the relation kind is unspecified.
-
Perspective flip (dependent-view vs base-view). The same situation is described alternately as “X is anchored/grounded” and “Y is an anchor/ground”, with incompatible naming, hidden directionality, and silent re-typing of the ends.
-
Base–witness confusion. Evidence, pins, certificates, or proofs are treated as “the base”, even when they are only witnesses for a base relation (or conversely: a base is treated as a mere witness).
-
Scope/time collapse. A time-dependent assertion leaves its interval or temporal rule unclear, so readers cannot tell which case it covers.
-
Γ_timeused as a proxy for freshness. Authors treatΓ_timeas “freshness” or “evidence decay”, collapsing TimePolicy with witness-timespan/freshness predicates. -
Decision use without its required basis. Declarations that gate work, publication, or assurance omit the basis required by that decision. A witness, pin, or time selector is required only when that use needs it; omitting the required basis prevents its audit.
-
Grounding conflation. “Grounding” is used as if it were one relation, while FPF already distinguishes at least:
-
Slot/basing conflation. A.6.5 separates a declaration-local SlotSpec, a designation carried in an episteme and the actual participant. Editing a designation does not itself change the obtaining relation.
-
Anchor relapse (source or meaning surrogate). “Anchor/anchoring” is used to mean “the source”, “the meaning”, “the global reference”, or “the thing that makes this true”. This hides the source, scheme, expression, local claim, and any obtaining basis relation behind a metaphor; the phrase alone does not let a reviewer recover them.
-
Support bucket relapse. “Support”, “support basis”, “support relation”, or “support record” is used as a generic container for unlike relations. Some cases are direct base-dependence; others are evidence use, assurance input, causal-use support basis, mathematical-lens use, work enablement, source description, publication companionship, or ordinary help. Treating them as one support relation recreates the under-described dependence that A.6.6 is meant to repair.
Forces
Solution - State the direct relation, then add only what the receiving use needs
Ordinary direct path
Start with a readable sentence:
Thermocouple channel TC-17 is calibrated to standard ITS-90 for rig R3.
Identify TC-17 and ITS-90, then apply the direct calibratedTo predicate and its applicability rule to the current facts. If the task only asks whether that calibration relation obtains for this rig, the sentence and predicate result are complete. Do not create a declaration record, witness set, edition, or assurance package merely because those fields could be written down.
Add a qualifier only when it changes the direct assertion or a named receiving use:
- name scope when the relation is limited to a range, population, rig, publication, or other extent;
- name time when the predicate or the use is time-dependent;
- cite an evidence-use or provenance relation when a claim about the relation is relied on;
- open occurrence identity only when another claim must refer to the same occurrence, compare it, qualify it, or record its history; and
- open a reusable declaration only when the reuse test in A.6.6:4.3 is met.
The assertion episteme, reusable declaration, world-side relation occurrence, evidence, and any Work remain different objects.
Optional scoped assertion record
When replay, comparison, publication, or repeated review needs a stable representation, a project may show one C.2.1 assertion episteme in this local form:
This is a representation of claim content, not a public kind, RelationSignature, or world-side occurrence. directRelationKind resolves to an already governed relation kind; an affirmative assertion requires that relation's predicate to obtain for the actual participants, while a negative assertion requires nonobtaining to be established under the applicable criterion or closure basis. Failure to establish the affirmative does not establish the negative. scope and gammaTime are present only when the direct relation or named use needs them. evidenceUseRefs, when present, resolve to A.2.4 evidence-use relations for this assertion. The evidence epistemes, producing Work, operation result, carrier, provenance, currentness, and later reliance remain separately identified under A.2.4 and A.10.
A.6.6 admits neither U.BaseDeclarationDiscipline nor U.ScopedWitnessedBaseDeclaration. The latter is a retired spelling and must not be used as a kind or as a world-side relation occurrence.
The record's C.2.1 identity follows its complete ClaimGraph, EntityOfConcern, and effective ReferenceScheme. Changing an identity-bearing value identifies another episteme; a representation-only edit need not. Neither change by itself begins, ends, or alters the world-side relation it describes.
Direct relation and optional assertion are different objects
The picture is a direct arrow in ordinary reading:
dependent stands in the named direct relation to base.
The arrow is not a generic mathematical constructor. Its participant meanings, predicate, applicability, and occurrence identity come from the selected direct relation pattern. A scoped assertion episteme may affirm or deny that this predicate holds, and evidence may support reliance on that assertion. Filling the optional record or merely asserting the claim establishes no occurrence. An episteme or publication may have a constitutive role under the direct relation's own rule; evidential support remains independently governed.
Calibration, attribution, policy dependence, constructive grounding, and other cases therefore remain different relation kinds. A.6.6 supplies a recovery discipline, not one universal BaseRelation kind.
Reusable declaration only for a named reuse
Use the direct relation's A.6.0 RelationSignature only after its kind is admitted and a named receiving use needs reusable participant typing or declaration content. An observed second consumer is not required; an anticipated use can justify the declaration. The signature restates the direct relation kind's participant meanings, predicate, applicability and occurrence-identity rule for reuse. A.6.5 SlotSpecs belong inside it; an ordinary one-case assertion may need no signature or explicit occurrence individuation.
If no direct pattern supplies the relation kind, participants, or predicate, keep the local claim or return the A.6.RCD missing-governor result. Do not repair the gap by minting a generic BaseRelation kind or token, SlotSpecs, or a scoped-record type.
What a reusable direct-relation declaration must say
For a named receiving use that needs a RelationSignature, the direct relation definition states:
- the dependent and base participant meanings and direction or symmetry;
- the obtaining predicate and applicability;
- the occurrence-identity rule, without requiring an occurrence to be explicitly individuated;
- admissible participant kinds and reference modes;
- any scope, time, evidence, or cross-local condition that changes this predicate or the named reuse; and
- the direct continuity or change rules, when that history is current.
Different local kinds, F.17 senses, scopes, or ReferencePlanes are handled by their applicable direct relations. Source difference alone creates no Bridge. A RelationSignature declares reusable content; the reusable form by itself neither asserts a current case nor establishes an occurrence.
Claim-scoped non-kind predicate-base branch
When one identified derivation or criterion-selection claim uses claim content as its base, reuse A.6.6's endpoint, scope, time, witness, Bridge/loss, change, and overread discipline without claiming that a new relation kind or special base-declaration occurrence has been admitted. Identify the dependent ClaimGraph and selected nonempty base subgraph as by-value NonemptyClaimContent values under C.2.1:4.1.2. State the derive or evaluate mode, derivation or evaluation-and-selection claim identity, bounded receiving use, and effective reference scheme. Add an A.2.6 ClaimScope, temporal policy/domain, source or witness qualification, or cross-scheme Bridge and loss account only when that independently varying fact changes the assertion.
The assertion is ordinary C.2.1 claim content under derivedUsingRuleContent or evaluatedAgainstRuleContent. The dependent and base are predicate parameters, not automatically A.6.5 SlotSpecs, participants of a reusable relation occurrence, or an intrinsic rule-bearing classification. Same-scheme use adds no Bridge. A source edition, designation, acceptance/currentness fact, trace, or witness qualifies the assertion but does not enter semantic-base identity. Equal graphs under the same scheme count as one semantic base with multiple qualifications; a changed graph is another base.
Change only the fact that changed: declare or withdraw a selected base, repoint the dependent, rescope, retime, refresh witnesses, or change the predicate relation. A changed subject, content, mode, bounded use, scope extension, temporal policy, or interpreted endpoint identifies another C.2.1 assertion. A claimed edition succession additionally requires the continuity conditions of C.2.1:4.5. Do not infer a new relation kind, occurrence, evidence result, Work, authority, or reliance from that change.
A basis-family analysis is a separate, optional C.2.1 episteme opened only for a named comparison, replay, material-conflict, or reliance receiver. Its candidate universe, evaluations, pairwise compatibility, temporal partition, established family, and disposition neither edit this reusable predicate declaration nor become fields of each derivation or criterion-selection assertion. A separate claim about actual use in Work follows its own rule; neither R7 predicate establishes that use.
Perspective and voice
State the relation in the shortest ordinary sentence that keeps both participants and direction recoverable: TC-17 is calibrated to ITS-90 is valid. Functional or arrow notation may be added when it helps a formal receiver; it is not the default. Base-view wording is also valid when it preserves the same relation and direction. Do not turn B validates X into an inverse relation unless that inverse is independently defined.
Lexical discipline
Normative lexical rule. In Tech or normative prose, do not use umbrella metaphors (anchor, attach, ground, or support) in place of the relation. Prefer an ordinary relation-specific sentence; add functional or arrow notation only when a named receiver benefits from it.
Red-flag rule (anchor* as dependence metaphor).
- In Tech or normative prose, repair
anchor*when it leaves the relation or participants unresolved. Keep an adequate ordinary or already governed use. - Source wording may remain for recognition or traceability alongside its recovered meaning. It cannot supply a missing rule merely by being renamed
validatedBy,verifiedBy,SupportRelation, or another formal-looking token.
Pattern-defined meanings. E.10 MG-DA token-to-EntityOfConcern anchoring and A.10 evidence anchors retain their own definitions. Apply the rule when that is the intended sense; do not open another basedness repair solely because the word appears.
Naming guard for relation vocabulary. Do not mint a new direct relation whose name merely preserves a metaphor such as Anchor*, Ground*, or Attach*. Name the relation kind and use the corresponding ordinary verb phrase. In an optional assertion record, the local directRelationKind field identifies that already admitted relation kind; the field is not another relation kind.
Lane guard for meaning. If the intent is “say what this expression means in this source”, do not introduce an Anchor… or Ground… relation. Recover the source-local claim under F.0.1; use F.17 only when a durable SchemeSenseCell or obtaining LocalSenseBasisRelation is needed. Semantic meaning assignment is not a base-declaration record.
Grounding disambiguation. When grounded leaves a consequential meaning unresolved, recover it. These branches illustrate distinct meanings, not an exhaustive classification:
- constructive grounding (
tv:groundedBy, base is a trace), - situational/empirical grounding (base is a grounding holon or experimental setup),
- source-local meaning lane (source, scheme, expression, local claim, and optional F.17 cell or basis relation; no special base-declaration object).
Bind deconfliction note. Do not use “bind/binding” as a synonym for declaring, refreshing, or changing an assertion or reusable relation declaration. This local edit vocabulary does not rename name binding or other already governed binding relations, including A.6.1 application bindings. Use the local declaration-change label only when a named receiver needs that history.
Base-change operation lexicon
The following local labels classify changes to an optional assertion episteme or reusable declaration when a named receiver needs that history. They do not describe the beginning, ending, or change of the world-side relation itself, and an ordinary direct assertion needs none of them. In decision or publication use, preserve the prior episteme when changing its ClaimGraph, EntityOfConcern, or effective ReferenceScheme; such a change identifies another episteme. A representation-only edit need not do so. Claim edition continuity only when the C.2.1:4.5 rule and case facts establish it.
Operation classes (conceptual):
- declareBase - create a new optional assertion with explicit
dependent,base,directRelationKind, andassertionPolarity, or a new reusable declaration for that same already governed direct relation kind; add only the scope, time, evidence-use, or other qualifications that its direct predicate or named receiver needs. - withdrawBaseDecl — retire an assertion or declaration (or render it inapplicable by scope narrowing or time restriction, depending on the direct relation's declaration).
- rebase — change
basewhile keeping the samedependentanddirectRelationKind(legality depends on the direct relation's declaration; often requires witness refresh). - repointDependent — change
dependentwhile keeping the samebaseanddirectRelationKind. - rescope — change
scope(widen/narrow/translate) under the direct relation's scope rule; widening often triggers witness refresh. - retime — change
Γ_timeselector/policy when time matters; not a substitute for witness-timespan/freshness predicates. - refreshWitnesses — add/refresh witnesses/pins when decision use continues across time advances, scope widening, or evidence refresh.
- changeDirectRelationKind — not an edit-in-place. Changing
directRelationKindchanges claim meaning; mint a new assertion or declaration rather than silently rewriting the kind. When edition history is needed, relate it to the prior episteme only if C.2.1:4.5's continuity rule and case facts establish that relation. Use F.13 for a separately current lexical-continuity claim.
Relation to A.6.5 designation operations (informative). Apply A.6.5 when the changed assertion designation is governed by a compatible RelationSignature SlotSpec. Other assertion or declaration fields retain their own C.2.1 or direct definition. State which content changed. A separately claimed world-side change uses the direct relation's rule; ordinary editing requires no invented Work occurrence.
Relation to E.18 assurance ops (informative). E.18:5.4 applies ConstrainTo, CalibrateTo, CiteEvidence and AttributeTo to the annotation of a resolved connection(q), retaining the relation r and any participant subject the operation requires. Each operation keeps its own meaning and basis. A project may use the local declaration-change labels for changes in a represented assertion; those labels neither perform an assurance operation nor establish a subject relation.
Disambiguation guide for selecting the direct relation
When umbrella wording leaves the relation unclear, recover the direct meaning that fits the claim:
This table is illustrative. Each row keeps its own direct relation and governor; it is not a list of species of one universal base relation or record. Grammatical subject and object expose a sentence's direction but do not by themselves determine dependent/base allocation. Where the domain predicate or participant allocation is not supplied, recover it from the source or leave that local choice open; this guide does not define it. Ordinary aboutness and source-local meaning do not by themselves select a basedness or construction branch.
Note. A.6.3 defines the viewing arrow. A.6.4 distinguishes the retargeting arrow r from a bounded-use assertion q and a current-case judgement. When a named receiving use is claimed, q's ClaimGraph contains that use, its invariant, visible loss, conditions, and affirmative or negative polarity. When a case is evaluated, the judgement compares its facts with q and returns exactly satisfies, fails, or cannot decide. A cannot decide judgement names the missing fact and reopen condition. This table directs those construction cases to their own patterns; it defines no second operator, arrow, assertion, judgement, application, or Work.
Support wording selection test
When a draft uses support, supported by, supporting, support basis, support relation, or a support-headed compound, do not first choose a more formal synonym. Ask what assertion the next reader needs.
If the sentence is about basedness, write the smallest direct form:
Identify the participants and apply that direct predicate. Stop there when it answers the use. Add scope, time, an assertion record, a reusable RelationSignature, occurrence identity, or evidence only when the predicate or one named receiver needs it.
If the sentence is not basedness, use the matching ontology:
Do not create SupportRelation, SupportBasis, SupportRecord, validatedBy, or verifiedBy as a fallback. Work, a result episteme, its carrier, provenance, evidence use, and later reliance remain separate.
Archetypal Grounding
System archetype: calibration to a standard
Tell. A lab instrument channel TC‑17 is described as “anchored to ITS‑90”. Later, the reference standard is swapped, the phrase “still anchored” is kept, and the applicability window silently expands. Downstream work disagrees and nobody can reconstruct what changed.
Show. First state the direct assertion: TC-17 is calibrated to ITS-90 for rig R3 over 0–200 °C during the stated calibration interval. Apply the calibration predicate and stop there if this answers the use. When a later publication or comparison needs the assertion edition, show the same claim in an optional scoped record:
When a later decision relies on this assertion, identify the calibration-certificate episteme and its A.2.4 evidence-use relation to the assertion. Use A.10 when the decision needs a bounded-reliance judgment or the producing Work, operation result, carrier, provenance or currentness path. Distinguish changes by what changed:
- New standard ⇒ rebase; establish the evidence-use relation required for the new assertion, reusing suitable witnesses or refreshing them when needed.
- Wider applicability window ⇒ retime and likely refreshWitnesses.
- Relation-kind change (“not calibration, just normalisation”) ⇒ changeDirectRelationKind is not an edit; mint a new assertion or declaration. Claim continuity with the prior episteme only when that history is needed and C.2.1:4.5's rule and case facts establish it.
Episteme archetype: an evaluation result used as evidence
Tell. A report says that model M improved accuracy by 4%. The team points to EvalRun-2025-10-12, but that Work occurrence is neither the claim nor an evidence relation, and its log carrier does not become evidence merely by being attached.
Show. First recover the accuracy measure, reference condition or population, and percentage convention from the reported comparison. If those operands cannot be recovered, the 4% comparison claim remains unidentified; stop before relying on that numerical target. Once they are recovered, identify the result episteme that states the measured comparison and the target claim about the 4% improvement. State the A.2.4 evidence-use relation between that episteme and claim, including the ClaimScope, polarity, window, and receiving use. If the decision also needs replayable source, carrier, provenance, currentness, or bounded-reliance information, use A.10 to cite the evaluation Work, its operation-result binding, the result episteme, the log carrier, and their independently obtaining direct relations.
Stop with the short evidence-use statement when it answers the question. No validatedBy(claim, Work) edge or scoped base-declaration record is required. If a project later needs a reusable evidence-relation declaration, that direct relation must first have its own participant meanings, predicate, applicability, and occurrence-identity rule.
Structural archetype: constructive grounding of a model edge
Tell. Suppose a B.3.5 assurance requirement for this publication requires a recoverable constructor trace. A structural edge is published (“A componentOf B”) without that trace. It becomes treated as “obvious”, while the construction chain is not recoverable. Ordinary parthood does not require this trace; the failure here concerns the selected hypothetical assurance requirement.
Show. Locate the required constructor trace and test the direct tv:groundedBy predicate for the model edge and trace. If the trace remains unavailable, retain that gap and stop the dependent assurance claim. For illustration, suppose ComposeCAL#c17 is recovered and the case facts satisfy the grounding predicate for Edge:componentOf#17. The short affirmative assertion may be enough; a publication needing a stable assertion edition with its qualifiers can represent it as:
The printed trace reference names the intended constructor trace; its presence does not establish the trace or the grounding relation. If another use relies on the assertion that the grounding relation obtains, cite its evidence-use and provenance relations separately. This example shows why “grounding” must be disambiguated: here it is a declared constructive relation with an explicit base (trace).
Bias-Annotation
Conformance Checklist
An A.6.6 use conforms when the checks for its selected branch pass:
- CC-BD-1 - Direct assertion first. The dependent, base, direct relation, and readable assertion or unresolved factual question are recoverable. The direct pattern supplies the predicate. Test affirmative obtaining or establish nonobtaining under its applicable criterion or closure basis; a record, label, or failure to establish the affirmative supplies no case result. Missing case facts leave the question unknown; only a missing governing rule requires A.6.RCD.
- CC-BD-2 - Ordinary stop. If that assertion answers the receiving question, no SlotSpecs, declaration record, witnesses, edition, occurrence identity, or assurance package is required.
- CC-BD-3 - Reusable declaration is demand-driven. A
RelationSignaturesatisfies the reuse test in A.6.6:4.3 and applies only to an already admitted relation kind. - CC-BD-4 - Assertion and occurrence stay separate. A scoped witnessed record, when used, is a C.2.1 assertion or description episteme. It is not the world-side relation occurrence, and its form alone does not establish that occurrence; any constitutive contribution follows the direct relation's rule.
- CC-BD-5 - Qualifiers are local. Scope and time are explicit when the selected predicate or named receiving use depends on them; they are not a universal field kit.
Gamma_timeis not used as a proxy for evidence freshness. - CC-BD-6 - Evidence ontology is direct. Evidence use follows A.2.4 and A.10. Work, operation result, result episteme, carrier, provenance, evidence-use relation, and reliance remain separate; no generic
verifiedByorvalidatedByedge is minted. - CC-BD-7 - Crossings are conditional. A relation between two F.17 cells uses F.9 only when its predicate obtains and keeps the bounded-use claim separate. A ReferencePlane crossing uses its applicable plane relation. One creates neither the other.
- CC-BD-8 - No silent retyping or direction flip. Participant kinds and direction follow the direct relation. A mismatch is repaired by the applicable narrowing, Bridge, retargeting, or direct relation rule, not by renaming an endpoint.
- CC-BD-9 - Plain language remains sufficient. Ordinary relation-specific prose is preferred. Functional or arrow notation is optional and may not replace the readable assertion.
- CC-BD-10 - Wording does not create ontology. Recover the meaning of anchor, ground, attach or support when it is unresolved. Keep an adequate ordinary or governed meaning; a metaphor or new label cannot supply an absent relation rule.
- CC-BD-11 - Meaning lane stays separate. Source-local meaning starts with F.0.1 and uses F.17 only when a durable sense address or basis relation is needed; it is not a base-declaration record.
- CC-BD-12 - Change claims name the changed object. Changing an assertion's or reusable declaration's ClaimGraph, EntityOfConcern, or effective ReferenceScheme identifies another episteme; representation-only editing need not. An actual relation change requires the direct relation's own change predicate and any separately current Work.
- CC-BD-13 - Optional history is proportional.
declareBase,rebase,rescope,retime, orrefreshWitnessesis used only when a named receiver needs that declaration history. The label establishes no world-side fact.
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits
- A readable direct assertion can close an ordinary question without record-first work.
- Reusable declarations are available when a receiving use needs their participant typing and laws.
- Scope, time, evidence, and continuity are explicit exactly where they change a predicate or receiving use.
- Evidence use, source-local meaning, semantic Bridges, plane crossings, and ordinary help keep their own ontologies.
Trade-offs and mitigation
- The author must identify the direct relation instead of hiding it behind support or anchor. The mitigation is one ordinary sentence and the direct predicate, not a universal form.
- A later replay or publication use may require more detail. Add only the missing declaration, qualifier, assertion, evidence, or occurrence identity at that point.
Adoption test (informative). A team has adopted A.6.6 when it can answer three questions in order: What are the participants and direct relation? Does its predicate hold for this case? Does a named later use require a reusable declaration, occurrence identity, scope, time, evidence, or history? A negative answer to the third question is a valid stop.
Rationale
Why focus on base declaration rather than a metaphor. The recurring ambiguity is not “how to attach”, but which direct relation is being asserted between which participants. A readable relation-specific sentence exposes that answer; an optional declaration can then preserve it for a named reuse.
Why keep the direct relation, assertion, and evidence separate. The relation's predicate determines whether the world-side fact obtains. A C.2.1 episteme may affirm or deny it under the polarity test, and A.2.4/A.10 may support reliance on that assertion. Conflating these objects lets a record or carrier stand in for truth. A base is a participant in the selected direct relation. Evidence or other supporting material justifies an assertion only through its own direct relations. Conflating the two makes both reasoning and audit unreliable.
Why add scope and Gamma_time conditionally. They are required when the direct predicate or receiving use changes across extent or time. Adding them everywhere hides the ordinary relation behind a universal qualifier form.
Recover extent and time from the direct relation and the receiving use. An already clear interval or temporal rule needs no duplicate field; an implicit current or latest that leaves the intended case ambiguous does.
Why distinguish semantic revision from representation editing. Changing the relation kind changes the assertion's meaning. Preserve the former episteme when history matters and establish any claimed continuity under C.2.1; a new wording or representation alone need not change identity.
Why retain a local declaration-change lexicon. When a named receiver tracks assertion or declaration history, the labels distinguish which episteme field changed. They are optional and do not describe actual relation change without the direct relation's own predicate. When that history is needed, explicit change classes distinguish rebase, retime, rescope, and witness refresh; a generic edit label hides those differences and recreates the ambiguity A.6.5 removed at the slot layer.
SoTA-Echoing
-
RDF-star and statement qualification. Adopt/Adapt. RDF-star/SPARQL-star explored attaching qualifiers/provenance to statements and edges. RDF 1.2's Candidate Recommendation Snapshot of 7 April 2026 distinguishes representing a proposition from asserting that it holds. We adopt the “qualified statement” intuition, but adapt it by requiring an explicit relation kind and by making
Γ_timeand USM scopes explicit when the direct relation or receiving use needs them. Primary sources: Hartig and Thompson, Foundations of an Alternative Approach to Reification in RDF (first submitted 2014), retained as history and marked obsolete by its authors; RDF 1.2 Concepts and Abstract Data Model, Candidate Recommendation Snapshot, 7 April 2026. -
Wikidata-style statements with qualifiers and references. Adopt/Adapt. Wikidata statements separate a core statement from optional qualifiers and references. We adopt that separation and adapt it by making decision-relevant basis requirements explicit through evidence-use relations, with slots only for a reused declaration, and explicit scope/time where the assertion or time-dependent use needs them. Primary source: Wikidata, Help:Statements.
-
Metrology traceability and calibration competence. Adopt/Adapt. Calibration is an operation relating a standard's quantity values and uncertainties to indications, then using that information to obtain measurement results. Metrological traceability is a property of a measurement result related to a reference through a documented calibration chain. We retain the need for documented calibration evidence and adapt time-dependent applicability through explicit
Γ_timeand the witnesses or pinned calibration records required by the assertion or receiving use. Primary sources: JCGM VIM, calibration (2.39) and metrological traceability (2.41); ISO/IEC 17025:2017, edition confirmed in 2023. -
Assurance case metamodels for claim–evidence structure. Adopt/Adapt. SACM formalises claim/evidence structures and emphasises structured support relations. We adopt the idea that decision-relevant admissibility links should be explicit, and adapt it by using FPF’s scope/time discipline and by treating relation-kind elision as a first-order defect. Primary source: OMG Structured Assurance Case Metamodel (SACM), version 2.3, October 2023.
-
Objects over a base as a mathematical lens. Adopt/Adapt. Category-theory treatments of objects over a base, including slice categories, offer a mathematical way to compare an X-relative-to-B construction. Use that lens only when the selected mathematical construction and its correspondence to the direct domain relation are established under C.29. It supplies no universal obtaining predicate, scope, time or witness rule for calibration, evidence, attribution and the other distinct domain relations. Primary source: Riehl, Category Theory in Context (2016).
Relations
Specialises A.6.P Relational Precision Restoration. A.6.6 handles basedness wording by recovering the dependent, base, and direct relation, then stopping or opening only the additional object required by a named use.
Builds on A.6.REL and A.6.0. The direct pattern supplies relation obtaining and occurrence identity. A reusable RelationSignature is justified only for an already admitted relation kind and shared declaration content; the declaration form alone establishes no occurrence.
Builds on A.6.5 only when reusable declaration content is current. A SlotSpec declares a participant meaning, ValueKind and designation mode inside one RelationSignature. An ordinary assertion needs no SlotSpec record unless its receiving use requires that declaration.
Coordinates with A.2.4 and A.10. A.2.4 states the evidence-use relation. A.10 represents the independently established sources, Work, result epistemes, carriers, provenance, currentness, and later-use relations needed for bounded reliance. Neither pattern admits generic verifiedBy or validatedBy edges, and Work is not an evidence carrier.
Coordinates with A.14 and C.2.1. Constructive grounding and empirical grounding retain their direct predicates and participants. Their assertion epistemes and evidence remain separate from the world-side relations.
Coordinates with A.6.3 and A.6.4. A.6.3's viewing construction separately identifies the source and receiving endpoints with the same EntityOfConcern; the endpoints may identify the same episteme in identity viewing. A.6.4 retargets between different EntitiesOfConcern; its retargeting arrow r, bounded-use assertion q, current-case judgement, operation application, and Work remain distinct. Ordinary aboutness alone selects neither construction. A.6.6 adds no second arrow or universal relative-to object.
Coordinates with F.9 and ReferencePlane rules conditionally. F.9 applies only to an obtaining Bridge between two F.17 cells and keeps its bounded-use claim separate. A ReferencePlane crossing uses its plane relation. If both are current, state both; if only one is current, introduce no object from the other branch.
Coordinates with A.2.6, A.7, and E.24.UK: A.2.6 governs scope and Γ_time when the assertion or receiving use depends on them. A.7 distinguishes EntityOfConcern, description, specification and publication uses. E.24.UK supplies the U-kind admission boundary; an optional local record form admits no new kind.
Coordinates with C.3.3 and E.18. C.3.3 supplies U.KindBridge only for an independently established cross-local kind correspondence, with its kinds, direction, declared CL^k, and use/loss conditions; different participant kinds alone establish no KindBridge or silent re-typing. E.18 retains the meanings and subject resolution of its assurance operations on connection(q), including CalibrateTo, CiteEvidence, AttributeTo, and ConstrainTo; A.6.6's declaration-change labels do not replace them.
Coordinates with E.8, F.0.1, F.15, and F.17: E.8 governs pattern-authoring order and SoTA discipline. F.0.1 recovers source-local meaning; F.17 supplies an optional durable sense address or basis relation. F.15 supplies the carrier/source-currentness, provenance, and refresh validation harness when that validation is current.
Feeds E.10, E.10.D1, and F.18 lexical governance. Umbrella words trigger recovery of the direct relation. Ordinary relation-specific prose remains valid; notation and durable public names are added only for a named use.
A.6.6:End
MechSuiteDescription — Shared Conditions for Joint Use of Distinct Mechanisms
Type: Architectural pattern. Status: Stable. Normativity: Normative [A] (Core).
Use this when. Several distinct mechanism declarations must be used together under shared conditions. Select their contracts and cite the required specifications. State a permitted operation order when joint use needs a protocol.
First useful result. The distinct member declarations, their joint conditions and required specification references are recoverable. Each declared protocol step also resolves to one member declaration edition and one operation in that declaration. Two implementations of the same declaration do not become two members.
Not this pattern when. Use A.6.1 for one reusable operation-family declaration, A.3.1 for a way of doing, and A.15.2 for an ordinary plan or edition baseline. A suite is useful only when several declarations have joint conditions to express.
A MechSuiteDescription describes a finite set of distinct mechanism declaration contracts, their shared obligations and required specification references, with any declared protocols and audit requirements. Two realizations of one contract remain one member. The description is distinct from a MechFamilyDescription and a publication Pack.
Plain-name. mechanism suite description; mechanism suite passport.
Builds on. A.6.1 (U.Mechanism canonical form), A.6.5 (SlotSpecs where a RelationSignature is current), E.10 (lexical + ontological rules; strict distinction; minimal specificity; kind suffixes), E.18 (transformation-flow structure and crossing visibility), E.18.1 (P2W carry-through), A.21 (gate-level decisions).
Used by. Mechanism stacks governed by shared admissibility, transport and audit obligations and operation declarations, including shared suites reused by Part G patterns such as G.5.
Declared vocabulary and references.
- Declares:
MechSuiteDescription(KernelToken, Description) and the record names used by its canonical form:MechSuiteId,SuiteObligation,SuiteObligations,SuiteSpecPins,SuiteProtocol,ProtocolStep,SuiteAuditObligations. - Reuses (by reference):
U.Mechanism(members),MechFamilyDescription/MechInstanceDescription(optional citations), existing pinned references such asCN‑Spec/CG‑Spec(as pins), and E.18/P2W notions (as obligations/pins), without introducing new U-kinds.
LEX.TokenClass.
LEX.TokenClass(MechSuiteDescription) = KernelToken.LEX.TokenClass(MechSuiteId) = KernelToken.LEX.TokenClass(SuiteObligations) = KernelToken.LEX.TokenClass(SuiteSpecPins) = KernelToken.LEX.TokenClass(SuiteProtocol) = KernelToken.LEX.TokenClass(SuiteAuditObligations) = KernelToken.
EntityOfConcern. A finite set of distinct mechanism declarations intended for joint use. The description's Tech name ends with …Description.
Lexical note: do not prefix this token with U.. The U.* namespace is for admitted U-kinds and governed kernel values; MechSuiteDescription is a description value for a suite of mechanism declarations, not a root kind.
Problem frame
An A.6.1 U.Mechanism declares its operations, arguments, results, laws, guards and any transport or audit conditions. Some architectures need several distinct declarations to be used together under shared conditions: for example, a characterization chain or an admissibility-gated selection protocol. The suite description states those joint conditions without redefining the member operations.
FPF already has MechFamilyDescription, but its meaning is: many realizations of one and the same U.Mechanism. That construct cannot correctly represent a bundle of different mechanisms (different declarations), and trying to overload it creates a level error.
Additionally, FPF reserves “Pack” for publication/shipping bundling (e.g., G.10); using “Pack” to mean “container of mechanisms” creates ontological collisions and downstream confusion.
Problem
The suite user needs one description that can:
-
represent a set of distinct mechanisms (distinct
U.Mechanism), -
declare shared obligations that must hold across the set (e.g., crossing visibility, admissibility-citation discipline, guard decision format, penalty routing),
-
provide shared spec pins (e.g., “this suite is governed by CN-Spec and CG-Spec”), without duplicating those spec contents,
-
constrain allowed protocols of use (allowed pipelines / permitted ordering), without turning the suite into a mechanism, and
-
preserve the distinction among:
- a description of several distinct mechanism contracts (
MechSuiteDescription), - a description of realizations of one contract (
MechFamilyDescription), - a publication bundle (
Pack, e.g., G.10).
- a description of several distinct mechanism contracts (
Forces
-
Strict distinction (level hygiene). “many mechanisms” must not be encoded as “many realizations of one mechanism”. Violating this blurs specialization laws, mechanism-declaration invariants, and audit/crossing responsibilities.
-
Minimal specificity + kind suffix discipline (E.10). The token name should encode only what is essential: it is a description, it is about mechanisms, it is a suite. It must not capture a domain (e.g., CHR) in the Kernel name.
-
Governing spec ref centrality (CN‑Spec and CG‑Spec). Suites must cite governing spec refs as pins, not duplicate their internals, otherwise multiple competing admissibility centers arise.
-
Transport and crossing visibility discipline. A claimed semantic correspondence between different local interpretation bases needs its obtaining F.9 Bridge; a kind correspondence needs its C.3.3 basis; a plane relation retains its own defining rule. Expose the anchors required by each actual relation and receiving use. An independently governed E.18 crossing or A.21 gate retains its required bundle or gate evidence. Assess loss under the receiving-use rule; apply the model-bound penalty conditions in §4.2(2). Suites do not embed CL/Φ/Ψ/Φ_plane tables.
-
Guard vs gate separation. Mechanisms can output tri-state guard outcomes and explanations; gate decisions (including
block) andDecisionLogremain gate-level (OperationalGate(profile)). A suite must not collapse these layers. -
Description and actual use. Shared conditions constrain later use; they are not that use or its results. Implementation references may be cited under their own rules, while member declarations retain the operation semantics.
Solution
Declare the members and their shared conditions in a MechSuiteDescription:
MechSuiteDescription (data model)
MechSuiteDescription declares:
- Suite identifier: a stable identifier for downstream citation.
- Membership: a finite set of distinct mechanism declarations.
- Suite obligations: shared invariants that every member (and any permitted composition of members) must respect.
- Suite spec pins: required citations/pins to governing spec refs and other “anchor” references.
- Suite protocols, when needed: allowed pipelines of use (permitted ordering and optional steps), expressed at the descriptive level.
- Suite audit obligations, when needed by downstream use: required audit/pin visibility (UTS/Path pins, crossing pins, guard pins), expressed as required anchors (not run-time values).
- Notes: optional explanations or boundaries needed to interpret or use the suite.
A minimal canonical form:
Norms.
- Suite identifier.
mech_suite_idMUST be present and stable: it is the citation handle for downstream planning and audit.
Well-formedness constraints (admissibility; non-deontic).
-
WF‑MS‑1 (Membership set semantics).
mechanismsresolves to pairwise distinct A.6.1 declaration epistemes under C.2.1 identity; field order carries no semantics. Two citations of the same declaration are one member. -
WF‑MS‑2 (Protocol closure and resolution). Every
ProtocolStep.mechanismresolves to one member declaration at its selected edition, andstep.operationresolves to one operation designator in that declaration. The selected operation supplies its arguments, results, laws and admission conditions. A stage label or unqualified family name is insufficient. -
WF‑MS‑3 (Suite ≠ Pack).
MechSuiteDescriptiondoes not carry shipping/publication payloads; use the applicable shipping or publication pattern for those results. -
WF‑MS‑4 (Suite ≠ Mechanism).
MechSuiteDescriptioncontains noOperationAlgebra/LawSet/execution semantics and is not admissible where aU.Mechanism.*node is required. -
Membership is by declaration (order-free).
mechanismsMUST resolve to a duplicates-free set of member declaration epistemes. Membership order has no semantics; intended ordering belongs insuite_protocols. Shared conditions and selected operations determine which joint uses the description permits.
Declaration reference and edition selection. MechanismDeclarationRef is a reference to an independently identified A.6.1 U.Mechanism episteme, not a new kind. Resolve it under the effective reference scheme to its content and EntityOfConcern. The published edition used for that resolution must be explicit or uniquely determined by the cited suite baseline. When several editions qualify, state a selection condition that yields one before using a protocol step; otherwise return the unresolved alternatives. There is no implicit latest.
Changing declaration content, EntityOfConcern or effective reference scheme follows A.6.1/C.2.1 identity. Changing a carrier, layout or citation alone can leave the member unchanged. A changed guard or argument selects a different declaration contract and requires the affected protocol bindings to be checked again. A claim that two declarations concern the same operation family needs that subject's own identity rule; suite membership does not establish it. Distinct declaration contracts can be selected without inventing a universal operation-family kind. A change to a shared specification or policy similarly reopens the steps and downstream results that depend on it. Reuse unaffected conditions and results when their grounds still hold.
-
No substitution by
MechFamilyDescription. A suite MUST NOT be encoded as aMechFamilyDescription. If desired, a suite MAY additionally citeMechFamilyDescription/MechInstanceDescriptionfor members (e.g., “preferred realization for this context”), but such citations do not redefine membership. -
No “Pack” meaning. A suite MUST NOT be named or treated as a publication pack.
Packremains reserved for publication/shipping bundling (e.g., G.10). -
No mechanism semantics in the suite. A suite is a Description, not a mechanism: it does not define
OperationAlgebraand does not absorb gate logic.
SuiteObligations (canonical obligation vocabulary)
A MechSuiteDescription may state additional shared obligations within the member contracts and applicable FPF rules. The names in §4.1 are reusable examples, not an exhaustive inventory.
SuiteObligations SHOULD be written as an explicit, duplicates-free clause set. Select applicable clauses from the canonical vocabulary in §4.1 and state any additional obligations explicitly. The requirements below remain applicable under their stated conditions.
Obligation meanings (normative).
-
semantic_correspondence_requirements. For an actual semantic correspondence between distinct recovered local senses, recover the F.17 endpoints and an obtaining F.9 Bridge, then the bounded-use and reliance claims required for this use. A suite creates none of those facts. A changed entity, reference scheme, plane or notation alone establishes no semantic crossing under A.6.4.1.1.
independent_correspondence_requirements.- When both an F.9 semantic correspondence and a C.3.3 kind correspondence are claimed, establish each under its direct rule. Any separately claimed plane relation keeps its own governor. Changing the EntityOfConcern alone creates neither relation. Retain the separate use conditions and applicable penalty policy; do not invent a second Bridge from the change label.
1.2.
transport_declarative_only.- Well-formedness constraint: suite obligations do not embed CL/Φ/Ψ/Φ_plane conversion or penalty tables. Transport obligations cite the applicable rules, pins and anchors; E.18 accounts for changed use bindings, and the applicable gate owns its decision. Distinct direct predicates retain their meanings and occurrence rules. Drawing an edge or declaring a suite obligation does not establish a relation, conversion or penalty.
-
penalties_route_to_r_eff_only. Well-formedness constraint: loss is assessed under the receiving-use rule and any tolerance it requires; a supported qualitative assessment can suffice. A numerical assurance penalty is used only when a named assurance claim consumes it under an applicable domain model in B.3:4.3–4.4, with the required dependency, calibration and unit assumptions. The selected model determines which result or results the penalty affects; apply anR/R_eff-only restriction only when that model establishes it. A penalty alone changes no legality, invariant orU.ClaimScopefact; those retain their own governing rules. -
guard_decision_tristate(pass|degrade|abstain)andunknown_never_coerces_to_pass. Well-formedness constraint: admissibility/eligibility outcomes use a tri-state guard resultGuardDecision := {pass|degrade|abstain}. Unknown/insufficient evidence is not coerced topass; it resolves to{degrade|abstain}under declared failure behavior (e.g., probe-only as a SoS‑LOG branch id, not as a new decision value). -
gate_decision_separation. Well-formedness constraint: suites do not define or useGateDecisionvalues (includingblock) as part of mechanism/suite semantics. Gate-level outcomes andDecisionLogremain onOperationalGate(profile). -
guard_lexeme_reservations. Well-formedness constraint:USM.CompareGuardandUSM.LaunchGuarddenote gate-owned guard events/pins; member mechanisms and suite protocols use…Admissibility/…Eligibilityfor guard predicates, not the reserved gate lexemes. -
cg_spec_cite_required_for_numeric_ops. For a suite whose numeric comparison, aggregation or scoring is admissibility-gated under CG-Spec, the relevant member operations cite that specification and its needed subrefs. Keep the admissibility content in the specification; a suite does not create a second local version. -
no_silent_scalarisation_of_partial_ordersandno_silent_totalisation. Well-formedness constraint: if a member mechanism induces a partial order, it preserves set-/relation-valued semantics; it does not silently reduce to a scalar/total order. Any totalization is explicit and policy-bound. -
no_thresholds_in_suite_core. Well-formedness constraint: suite core does not publish acceptance thresholds (“passing scores” / hidden cutoffs). Thresholds belong to acceptance clauses / task signatures / gate profiles. -
crossing_visibility_required. Well-formedness constraint: for each GateCrossing relevant to suite use, make its changed bindings, from/to values and establishing basis visible under E.18:5.1. Publish aCrossingBundlewhen a named downstream use relies on durable crossing evidence, including an applicable suite audit requirement under §4.5; that bundle can be cited as an audit anchor. Apply E.18 only for an independently selected TransformationFlowStructure and its actual governed crossing; apply A.21 for a current work-entry gate. An edition, entity or notation change alone supplies neither that crossing nor a semantic Bridge. Suites may requireCrossingBundleRef/ UTS / Path pins and policy-id pins as anchors, and MUST NOT embed CL/Φ/Ψ/Φ_plane tables. -
planned_filling_in_workplan. Any planned filling used as a baseline for suite use is content of an A.15.2U.WorkPlan; A.15.3 applies only to independently declared members. These are intended values under the plan's conditions, preserved separately from later actual-use facts. -
actual_launch_facts_and_witness. For an actual launch claim under E.18:5.6, establish one independently admitted A.15.1 Work occurrence and the actual launch values through independently obtaining direct relations or A.6.1 application bindings. A separateFinalizeLaunchValuesepisteme may then designate that occurrence and those facts. A plan or suite requirement supplies none of those actual facts by itself.
SuiteSpecPins
A MechSuiteDescription MUST be able to declare required spec pins as references, not as duplicated content. Canonically:
Norms.
- If the suite is admissibility-gated for characterization,
CNSpecRefandCGSpecRefMUST be required (as references/pins). - Spec pins are citations and anchors. They do not replace the underlying
…Specobjects. - A suite may require an edition/reference baseline in ordinary A.15.2 WorkPlan content. Address it through the plan and its local content locator; it supplies no launch value or gate decision.
- Use A.15.3 typed planned filling only when an existing declaration member independently supplies the position meaning, designation, cardinality and actual-use predicate. A suite Description field is not a SlotSpec or operation argument merely because a plan names it. Missing planned information can remain unknown in the plan; a missing governor requires recovery or definition of that member before typed filling. Actual application bindings retain their A.6.1 predicates; Work admission is additionally needed when the claim consumes a dated Work occurrence. An actual launch claim and any separate
FinalizeLaunchValueswitness follow E.18:5.6.
SuiteProtocols
A suite MAY describe allowed protocols (pipelines) as descriptive constraints on how suite members are intended to be composed. A SuiteProtocol describes the member-operation sequence. Its description:
- MUST name the member mechanisms it uses,
- MAY mark steps as optional,
- MUST NOT introduce hidden crossings or hidden admissibility steps,
- MUST identify any “publish/telemetry” as an external step of the surrounding protocol, realized through existing publication surfaces (e.g., Part G shipping), rather than as a hidden tail inside a mechanism. This external step is not a
ProtocolStepin the suite-member sequence.
A canonical shape for the suite-member sequence:
SuiteAuditObligations
A suite MAY require that downstream use provide audit anchors. These are requirements, not run-time values. A suite audit obligation MAY include:
- required
UTS+Pathpins, - required crossing-surface visibility pins for any crossing relevant to suite use,
- required presence of
USM.CompareGuardand/orUSM.LaunchGuardpins (not gate checks), - required declaration of guard ownership (e.g., a
GuardOwnerGateSlotanchor), - required expression of guard violations as
GuardFailevents aggregated by the guard-owning gate (perGuardOwnerGateSlot), not as extra mechanism/suite states, - required policy-id pins for any degrade/sandbox/probe-only branches (SoS‑LOG branch id anchors).
- required parity/selection-grade pins when applicable (e.g., when suite use claims parity-grade comparison/selection surfaces downstream).
Norm. A suite must never publish a DecisionLog or GateDecision. If the suite requires guard pins, it requires their presence as anchors so that the gate-level owner can aggregate GuardFails and decide degrade|block per gate profile.
Examples
Example 1 — compare two offers and retain the nondominated set. The question is whether either offer can be discarded without accepting a worse cost or quality. This is a stipulated mathematical use; the following specifications and applications are case facts, not empirical measurements or dated Work claims.
Selected contracts and specifications. The baseline OfferChoiceB1 selects Dcmp = A.19.CPM §4.1 and Dsel = A.19.SelectorMechanism §4.1, including their operation-local declarations, application/binding predicates, identity and extent rules, in the same publication edition as this case. These references mean that edition's content, not a later revision. Resolve another publication's references again before reuse. Their effective scheme is the CHR reference scheme declared there.
The case's independently stipulated specification editions are:
These definitions are the cited case specifications, outside the suite description. OfferBasis@1 gives position cost the price Characteristic and EUR ratio scale, and position quality the declared defect-free proportion Characteristic and a dimensionless ratio scale. The already admitted measure profiles are A=(10 EUR, 0.8), B=(12 EUR, 0.9). Both use these positions, with complete exact stipulated values.
Filled suite description. OfferChoiceSuiteDescription has mech_suite_id = OfferChoiceSuite, membership {Dcmp, Dsel}, required spec references {OfferCN@1, OfferCG@1}, and required policy/comparator references {OfferSelection@1, OfferPareto@1}. Its shared obligations are tri-state eligibility with unknown never passing, explicit numeric admissibility, a set of relation tokens from comparison and a set of candidate references from selection in this suite, without hidden scalarization or totalization, and gate-decision separation. The one protocol contains four required steps:
The protocol invariant requires both members to use the same admitted profiles, scope, slices, scheme, plane and evaluation point, and Select to consume the actual returned Compare binding. The audit obligation is to recover those effective arguments, eligibility judgments and output bindings, including token provenance. There is no public naming, semantic/kind/plane correspondence, flow crossing, gate, implementation export or planned-launch claim in this use, so it requires none of their conditional anchors. The description supplies no operation law or runtime output of its own.
Application and result. Outside the description, stipulate one completed application of each of the four selected operations, in the listed order. Each takes up the following arguments and ends at its own return; those four invocation episodes are distinct from the evaluation point they share. OfferScope@1 delimits the comparison and selection of A and B for this offer question; {OfferSlice@1} is its selected A.2.6 context-slice set. Both members bind that scope and set, the CHR reference scheme, the concept reference plane, and evaluation point 2030-01-01T00:00Z in UTC. No additional CharacteristicSpacePredicate or MinimalEvidence override is used. Normalization has no dependency because OfferCN@1 compares the original matched scales.
The comparator guard uses A as LeftProfileSlot and B as RightProfileSlot, with OfferCN@1, OfferCG@1 and OfferPareto@1, and returns pass: both profiles are complete, admitted and scale-compatible. Application c1 then returns ComparisonResultSlot = {A ∥ B}. Its returned binding, not an equal saved token, supplies the selection basis.
The selector guard binds CandidateSetSlot={A,B}, comparisonBasis={c1}, requiredComparisons={(A,B,OfferPareto@1)}, tokenProvenance={A ∥ B ↦ c1's returned binding}, and ComparisonResultSlot={A ∥ B}. CriteriaSlot contains the single clause “retain all nondominated candidates”; selectorPolicy is OfferSelection@1; TaskSignatureSlot is absent because no default is obtained from it. CN, CG and the common use arguments are those above. Coverage is complete and the guard returns pass. Select consumes that eligibility result and returns SelectionSlot = {A,B}. Incomparability is retained; neither offer is silently chosen as the winner.
Changed condition and stop. If B's quality is unknown, OfferCG@1's evidence condition fails: CompareEligibility returns abstain, no Compare result is fabricated, and the selector has no complete comparison basis. Its guard returns abstain, with no Select application or selected-set result. Changing only the selected comparator declaration to an unresolved edition also stops at protocol resolution before calculation. A suite-shaped record cannot cure either missing basis.
The description answers which contracts can be jointly used and under what conditions. The four stipulated applications answer what happened in this case. A gate decision, dated Work account or published result would need its own independently established basis.
Declaration-change case. The CHR normalize stage resolves to apply in a selected UNM declaration edition. Let D1 admit pass and policy-supported degrade, as A.19.UNM §4.1 does. Suppose a separately proposed D2 changes the operation guard to pass only. For the same input whose eligibility is degrade, D1 permits the qualified output and D2 does not. Merely pinning both sources or writing UNM + normalize cannot decide which contract governs. A step selecting D1 remains on D1; substituting D2 changes the member contract and requires the new guard to pass. These are illustrative edition names, not claims that both editions are published.
Two different realizers of D1 still use one member. UNM and the independently identified UINDM declaration are different members. A differently formatted publication of D1 can preserve the declaration identity. A new declaration about an independently established same family is still a new contract when its content changes; any family-continuity claim remains separate. Thus the protocol can resolve even where family continuity is irrelevant or unresolved.
Example 2 (non-conformant). Misusing a family as a suite:
This is a level error: MechFamilyDescription is reserved for realizations of a single mechanism declaration.
Example 3 (non-conformant). Conflating suite conditions with decisions, governing rules or relation facts:
- The suite declares
GateDecisionvalues or embeds aDecisionLog. - The suite defines acceptance thresholds (“pass score ≥ 0.7”) as part of suite obligations.
- The suite embeds conversion or penalty tables, invents relation facts from a graph label, or treats referenced transport pins as an applied conversion or gate decision.
Gate decisions remain at the gate; acceptance clauses, task signatures or gate profiles state thresholds; and the applicable specifications, policies and direct predicates govern conversions, penalties and relation facts. A suite states the requirements on their use.
Archetypal Grounding
A suite is an archetypal mechanism-suite “passport”:
- It answers what mechanisms exist in the bundle and what shared invariants make their composition lawful.
- It provides shared governing spec anchors (pins) that downstream planning and work must cite.
- It remains descriptive: it does not contain run-time outputs, and it does not replace the transformation-flow structure selected under E.18 for composition and crossing visibility.
Bias-Annotation
Common biases this pattern guards against:
- Overloading “family”. Treating “many different mechanisms” as “many realizations of one mechanism” destroys level hygiene and encourages semantic drift across members.
- Publication conflation. Using “pack” semantics to include publication/shipping obligations in the meaning of a mechanism bundle.
- Gate conflation. Treating suite-level obligations as gate decisions (“block”) instead of keeping
blockat the gate layer. - Convenience totalization. Collapsing partial orders into scalars “for ease of selection”, which undermines set-return semantics and admissibility gating.
Conformance Checklist
A MechSuiteDescription is conformant iff all applicable items hold:
CC‑A.6.7‑1 (Correct level). The suite’s mechanisms enumerate distinct U.Mechanism members. The suite is not encoded as MechFamilyDescription.
CC‑A.6.7‑2 (Description token, not U.*). The suite token is a Description token and MUST NOT be introduced under U.*. Its name ends with …Description.
CC‑A.6.7‑3 (No execution semantics). The suite MUST NOT define mechanism blocks (OperationAlgebra, LawSet, etc.) and MUST NOT be used as a mechanism node.
CC‑A.6.7‑4 (No gate decisions). The suite MUST NOT define GateDecision, MUST NOT publish DecisionLog, and MUST preserve gate/mechanism separation.
CC‑A.6.7‑5 (Spec pins, not duplication). If the suite is admissibility-gated for numeric comparison/aggregation/scoring, it MUST require CG-Spec citation pins (and SHOULD require CN-Spec pins where applicable). It MUST NOT duplicate spec content as “local CG-Spec”.
CC‑A.6.7‑5a (CN+CG pins for admissibility-gated characterization). If the suite is admissibility-gated for characterization, it MUST require both CNSpecRef and CGSpecRef as pins (references), consistent with A.6.7:4.3.
CC‑A.6.7‑6 (Transport discipline preserved). The suite MUST NOT introduce transport exceptions. For an actual semantic crossing, it MUST require the obtaining Bridge and bounded-use grounds under the direct rule, with loss assessed for that receiving use and any numerical assurance penalty satisfying §4.2(2). Entity, scheme, plane or notation changes alone establish no Bridge.
CC‑A.6.7‑7 (Tri-state guard discipline when used). If the suite declares admissibility/eligibility semantics, it MUST use GuardDecision := {pass|degrade|abstain} and MUST NOT coerce unknown to pass.
CC‑A.6.7‑8 (No thresholds in core). The suite MUST NOT publish acceptance thresholds or “passing scores”. Thresholds must remain in acceptance clauses / task signatures / gate profiles.
CC‑A.6.7‑9 (Crossing visibility anchors). If suite use consumes an actual semantic crossing or an independently governed E.18 crossing/A.21 gate, require only that claim’s applicable visibility and audit anchors, including Bridge, CL, policy, UTS or Path pins when its direct rule requires them. A changed edition alone creates none of those objects; keep the changed edition pin without manufacturing a crossing.
CC‑A.6.7‑10 (Suite id present). The suite MUST declare mech_suite_id: MechSuiteId so that downstream planning/audit can cite it stably.
CC‑A.6.7‑11 (Independent correspondence conditions). A claimed kind correspondence MUST satisfy C.3.3 and retain the calibration and use conditions required there. When the use also relies on an F.9 semantic correspondence, establish that Bridge independently and retain both channels' applicable policies and penalties. A new EntityOfConcern of the same kind or a plane-only change creates neither correspondence by itself.
CC‑A.6.7‑12 (Implementation export hygiene when cited). If the suite cites realizations/implementations, the citations MUST preserve export/import discipline (LOG/CHR: no Γ export; CAL: exactly one Γ; imports acyclic).
CC‑A.6.7‑13 (No Pack conflation). The suite MUST NOT be introduced, named, or used as a publication/shipping Pack.
CC‑A.6.7‑14 (Protocol closure & explicitness). Each step resolves to one member declaration edition and one operation designator in that declaration (WF‑MS‑2). The operation's argument, result, law and admission meanings are recoverable. No unresolved edition choice, implicit operation or implicit crossing can supply that resolution.
CC‑A.6.7‑15 (P2W split preserved when applicable). If the suite requires a planned-baseline pin, that baseline MUST be content of an A.15.2 U.WorkPlan. Preserve its intended values and references. Actual launch values require independently established facts under E.18:5.6; any FinalizeLaunchValues witness remains a separate episteme.
Common Anti-Patterns and How to Avoid Them
-
Anti-pattern: “Family-as-suite”. Using
MechFamilyDescriptionto list multiple distinct mechanisms. Fix: useMechSuiteDescriptionfor “many mechanisms”, and keepMechFamilyDescriptionfor “many realizations of one mechanism”. -
Anti-pattern: “Pack-as-suite”. Naming/using the suite as a
Pack. Fix: reservePackfor publication/shipping bundling; useSuitefor mechanism bundles. -
Anti-pattern: “Suite contains admissibility tables”. Duplicating CG‑Spec or embedding CL/Φ/Ψ tables in suite obligations. Fix: publish pins and references only; keep admissibility content in
...Specand policy registries; keep crossing realization in E.18/gate surfaces. -
Anti-pattern: “Suite is a hidden gate”. Introducing thresholds,
block, orDecisionLogin the suite. Fix: suite declares guard formats and required pins; the gate issues decisions. -
Anti-pattern: “Implicit calls”. A protocol implies “normalize happens somewhere” without explicit member and pin visibility. Fix: identify the selected member operations and required pins. When an E.18 flow structure is independently selected, keep its Uses edges explicit too.
Consequences
Benefits.
- Eliminates level confusion between “family of realizations” vs “bundle of mechanisms”.
- Lets several protocols reuse one identified set of shared conditions.
- Makes admissibility/transport/audit obligations shared and explicit, reducing semantic drift across member mechanisms.
Costs.
- Adds a description that must be maintained when its member contracts or shared conditions change. Publication is needed only when the receiving use requires it.
- Requires discipline: suites must remain descriptive and must not become “meta-mechanisms” or “hidden gates”.
Rationale
Characterization and admissibility-gated selection pipelines are unified by:
- shared governing spec refs (e.g., CN‑Spec / CG‑Spec),
- shared conditions for actual semantic, kind and plane relations, independently governed flow/gate crossings, and loss assessed under the receiving-use rule,
- shared guard semantics (tri-state, no coercion),
- and explicit protocol constraints (allowed pipelines).
A suite descriptor keeps distinct contracts and their joint conditions explicit. Shared conditions alone establish neither one A.6.1 operation-family declaration nor realizations of one contract; assess any separately proposed mechanism declaration under A.6.1.
SoTA-Echoing
Question and selected answer. How can a practitioner reuse several operation contracts under one set of conditions without selecting an implementation prematurely? For this question, adapt the explicit process-reference, input/output and requirement separation in CWL Workflow v1.2.1, §3.3 and §4.3. Its abstract Operation describes inputs and outputs before binding a concrete process. This supplies a declaration-first composition comparison; FPF admissibility and operation identity retain their own rules.
Serious alternative. A pinned executable pipeline is preferable when the task is already to fit and run compatible estimators. scikit-learn 1.9.1 Pipeline, steps exposes named estimator steps; each has fit, and intermediate steps have transform. It is a composition alternative.
For OfferChoice, compare both approaches with the same two contracts, four operation uses and four specification references. Adopt explicit member/operation resolution and one common specification baseline; reject the shortcut of identifying these contracts only by stage names or selected realizers. An executable pipeline could carry the same facts through adapters and metadata, but those additions still need their declarations and checks. The suite keeps them inspectable before an implementation exists. The deliberate cost is another reference layer; it offers no execution or performance advantage. Once executable estimators and their composition fully answer the question, use that pipeline and do not add a suite merely for documentation.
This choice is expressed in §4.1's declaration/edition resolution, §4.4's separate protocol and the filled §4.6 case: a returned comparison binding supplies selection, and absent evidence stops the chain. The architectural comparison is a local inference from the stated use and these primary specifications, not a measured productivity result. Reopen it if a receiving use needs only one already complete executable pipeline, if an additional reference layer hides a required condition, or if a rival represents the same distinct contracts and joint conditions with less total reader work.
Relations
- Relates to A.6.1: suite members are
U.Mechanism; the suite does not replace the mechanism definition. - Relates to A.6.5: member operation declarations retain A.6.1 argument/result meanings, ValueKinds and binding rules. A.6.5 applies only where a cited
RelationSignatureindependently declares participant SlotSpecs; there SlotKind stability, correct refMode and non-semantic SlotIndex remain required. - Relates to E.18 / P2W: suite protocols describe intended composition; use E.18 for the selected transformation-flow structure and its crossings, and E.18.1 for P2W carry-through.
- Suite conformance: use §7 for the applicable requirements. Resolve required references and check the content and facts those requirements consume; a pin's presence alone does not establish conformance.
- Relates to G.10: suites are not packs; G.10 handles shipping of Part-G outputs as a SoTA pack, while E.17 publishes reader-facing forms of an already accepted engineering account.
A.6.7:End
Cross-Context Sameness Disambiguation - Restoring the claim behind "same", "equivalent", and "align" (RPR-XCTX)
Type: Relational precision-restoration pattern; Architectural (A) — A.6.P specialisation (RPR) Status: Stable Normativity: Normative
Use this pattern when a document, table row, boundary statement, or publication claim uses same, equivalent, aligned, mapped, or corresponding in a way that may hide ordinary designation, a non-semantic lane or id claim, or a real relation between local senses.
What goes wrong if missed. A label match, explanation, ID mapping, or partial correspondence becomes global identity or a licence for an unspecified use. Direction, use rule, tolerated loss, evidence, and the actual downstream act disappear inside one umbrella word.
What this buys. The sentence becomes one result: a same-context designation, a claim stated using its concrete predicate or constraint, an obtaining F.9 Bridge with a separate bounded-use claim when a use is proposed, or an explicit stop. A card is added only when the claims must travel.
Builds on: A.6.P for relational prose repair; F.17 for scheme-based SenseCells; F.18 for designation; F.9 for the direct Bridge relation, profile, bounded-use boundary, and card boundary; C.2.1 for claim and description identity; F.0.1, F.7, and F.8 for sense-family and downstream naming discipline; A.7 and A.6.6 for lane and identifier dispatch Coordinates with: A.10 for descriptive evidence-provenance paths and local reliance dispositions; B.3 for assurance; E.17.0 for View membership; E.24.PUB for publication occurrence, form, and carrier; C.3.3 for the
KindBridgerelation and C.3.2 for a fresh target classification judgment; A.2.6 for scope operations; A.6.3.RT for representation transition; A.22 for structure; A.2.1, A.13, A.15.1, and conditional F.6 for system-role-kind, assignment, and Work claims
Use this pattern when umbrella sameness wording could hide which local senses, designation, lane, identifier, scope operation, representation transition, structure relation, or proposed use is current. The trigger starts a dispatch; it does not oblige the author to assert a Bridge or complete a card. Keep wording whose object, meaning and use are already clear.
When the remaining question is semantic, first test whether a Bridge obtains. For a proposed use of an obtaining Bridge, state the use separately in ordinary language: what someone will do, in which direction, by which correspondence rule, and how much semantic loss that use tolerates. Give that C.2.1 claim affirmative or negative polarity. F.9, A.10, and B.3 supply the follow-through; A.6.9 teaches the reader how to recover it from ambiguous prose.
Problem frame
Cross-context prose routinely compresses a multi-part claim into one adjective: same, equivalent, align, map, matches, or corresponds.
First decide whether this is a Bridge situation at all. A positive F.9 case has two F.17 SchemeSenseCell endpoints whose <ReferenceScheme, LocalSenseClaim> projections differ, plus an applicable relation-semantic profile whose predicate is true for those cells. Labels, identifiers, systems, mapping implementations, selected structures, cards, and publications may help identify endpoints or support the predicate; none by itself supplies a resolved endpoint or makes the profile predicate true.
If a Bridge obtains, several questions still remain independent:
- what comparison, substitution, translation, explanation, publication, or other use is proposed;
- the direction of that use;
- the use-specific correspondence rule;
- the semantic-loss tolerance for that use;
- whether the C.2.1 claim about that use is affirmative or negative;
- whether current A.10 evidence or B.3 assurance supports relying on that claim;
- whether separate authorization is required; and
- whether any Work, assertion, publication, relation, operation application, or other receiving object actually occurred.
A.6.9 makes that dispatch visible. It prevents an explanation, mapping witness, score, or card from becoming global identity, authorization, or proof of performance.
Problem
When an umbrella predicate is used as if it were a complete answer, readers silently choose defaults:
- Symmetry hallucination: “equivalent” is read as symmetric even when the intended relation is narrower or broader.
- Relation-to-use jump: a true correspondence is treated as sufficient for the requested comparison or substitution.
- Loss erasure: “same” implies lossless transfer although units, granularity, preconditions, or stance differ.
- Permission confusion: “A is suitable for this comparison” is read as permission or authorization to perform it.
- Implicit inversion: relation symmetry is treated as two safe use directions, or endpoint order is mistaken for the safe inclusion direction.
- Occurrence smuggling: a named “publication use” or “mapping use” is treated as an actual publication or mapping operation.
- Temporal incoherence: an unpinned claim silently combines different glossary, schema, code-list, ontology, or model editions.
These are ontology and inference defects, not merely word-choice defects.
Forces
Solution
Treat an umbrella sameness sentence as a dispatch trigger, not as an automatic Bridge and not as a demand for a card. Recover the concrete subject and action first. Then choose the smallest truthful branch:
- Ordinary designation inside one semantic bounded context. If both expressions resolve to the same
<ReferenceScheme, LocalSenseClaim>projection, keep ordinary designation and stop; use F.18 only when a durable name is needed. When only the admitted extent of that claim changes, apply A.2.6widen,narrow, orrefit. No F.9 Bridge is current. - Lane or reference-plane repair. If the sentence confuses Object, Description, Carrier, or
CHR:ReferencePlane, restore the kinds under A.7 or the governing plane rule. - Identification or indexing. If the sentence means same id, key, code, or index target, apply the identification or indexing rule. Use A.6.6 when the relation or its participants remain hidden. Identifier equality does not establish meaning correspondence.
- Scope operation. A.2.6 is the pattern for
widen,narrow,refit, andtranslateover scope values; when the sentence concerns claim extent, recover theU.ClaimScope.translatemay consume an independently obtaining F.9 Bridge and a separate affirmative claim for that direction, rule, and tolerance; it is neither representation Work nor a structure crossing. - Other locality hidden by context wording. Route interpretation to the effective interpretation rules (
ReferenceScheme); claim extent toU.ClaimScope; empirical grounding to oneEpistemeEmpiricalGroundingRelation; time to the qualification window required by the temporal predicate; a deliberately asserted actual composite project Work to A.13, independent A.15.1 admission and A.15.6; viewpoint use to the E.17.0 viewpoint relation and oneU.ViewpointRefresolving P; and any world-side subject claim to the pattern that defines its relation predicate and obtaining condition. A bare context word supplies none of these governed objects or claims. - Representation transition. A representation change is not a Bridge. For ordinary A.6.3.RT use, name the same concern, content to survive, target representation, source comparison, and supported use with its material limits. Add a source-return condition when a limitation, representation feature, misunderstanding or risk makes return necessary for that use, and name its destination. When a dependency across interpretation rules or another use makes claim identity material, independently constitute source episteme
Xand receiving epistemeY, requireEntityOfConcern(X)=EntityOfConcern(Y)exactly, and statev : X -> Ywith the relation between the endpoint interpretation rules, preservation, loss, and prohibited strengthening. AssertRepresentationTransitionRelation@Contextonly when every six-participant obtaining condition and actual dated representation-transformation Work are present; performed Work alone neither provesvnor makes that relation obtain. A Bridge supplies neithervnor the Work and makes no transition occurrence obtain. - Structure comparison or crossing. Identify the structures and what the comparison must establish under their direct rules; use A.22 for
U.Structureidentity. Apply §4.8 only when the receiving question depends on the organization of actual subject crossings among several independently identifiedBoundedModelUseStructurevalues. A SenseCell Bridge, label, diagram, shared participant, or reference alone supplies neither structure selection nor a crossing. For a required crossing without a direct governor, return the A.6.RCD missing-governor stop. - Cross-local semantic relation. Resolve two F.17
SchemeSenseCellvalues from different semantic bounded contexts, declare the F.9 relation-semantic profile, and cite a Bridge only when its predicate obtains. Scheme difference, same spelling, a mapping witness, or two endpoint references alone establishes no Bridge. - Proposed use of an obtaining Bridge. In a second sentence, name action
u, directiond, use-specific ruler, tolerated losst, and claim polarity under C.2.1. When someone will rely on that claim, recover A.10 or B.3 reliance for the same use. - Explanation or unresolved proposal. Say plainly what remains unestablished. A candidate or negative card carries no positive occurrence reference.
- Claim that the use happened. Name the actual receiving object and use the rule that defines the claim about that object; the use position inside the C.2.1 claim is not that object.
For A.6.9, semantic bounded context is a Plain practice name for the local interpretation basis recovered from one cell's <ReferenceScheme, LocalSenseClaim> projection. It supplies only that interpretation basis; each receiving object or relation remains governed by the applicable branch above. Representation transition, A.2.6 scope translation, F.9 local-sense Bridge, and direct structure crossing remain four independently governed moves.
Trigger and endpoint recovery
Open the dispatch when same, identical, equivalent, align, map, match, correspond, treat as, reuse, share, unify, canonical source, synced, normalized, one-to-one, same ID, or mirrors could hide the current object or action. Apply equivalent triggers in any language.
If the dispatch leaves a semantic-correspondence question, resolve the local senses before deciding whether a Bridge is current. A shared semantic-context projection still exits through ordinary designation. Each candidate endpoint reference must be a SenseCellAddressRef resolving one F.17 SchemeSenseCell. Keep the cell distinct from each C.2.1 description episteme about it, each F.18 designator, and each address reference. A reference resolves the cell, a designator names it, and a description claims something about it; only the cell fills the Bridge endpoint. A string, system, table, class name, file, context label, card, or identifier may be the source expression or a neighboring evidence object from which that cell is recovered. If a token is metonymic — the system, the model, the service, that table — test only governed referents that a plausible intended reader could recover from the local span, then recover the intended local expression and claim. If either endpoint remains unresolved, keep the sentence explanatory and return unresolved SenseCell endpoint.
Pin the endpoint reference-scheme and local-sense-claim editions, or an as-of basis, when the correspondence can change with a canon or model edition. Γ_time may be used as a compact card label for that basis. It is not a participant. It contributes to profile identity only when it states the profile's applicability or as-of basis.
Before testing a Bridge, check ontological strata. C.3.3 establishes only the KindBridge between source and target local kinds. C.3.2 makes a fresh target classification judgment under the target KindSignature edition and slice. Use the pattern that defines the measurement claim for value normalization, A.2.1 for system-role assignment, A.13 and independent A.15.1 admission for actual Work, with F.6 only for precise assignment-bound attribution, E.24.PUB for publication occurrence, form, and carrier, and A.6.3.RT for representation transition. F.9 can supply a semantic premise needed by one of those claims; each neighboring claim obtains only under its named subject pattern.
Stable lens: relation, use claim, reliance, and receiving object
Keep these objects distinct:
- Bridge occurrence. The direct relation has exactly two F.17 cell participants and obtains under one F.9 profile.
- BridgePredicateProfile. It contains only Bridge kind, kind-defined symmetry or orientation, endpoint-sense readings, relation-specific correspondence or difference condition, applicability and as-of basis, Boolean truth condition, and stop dependencies.
- Bounded-use claim. An ordinary C.2.1 claim says whether the obtaining Bridge is suitable for
<u,d,r,t>. Its EntityOfConcern is the Bridge; its ClaimGraph designates the use, direction, rule, tolerance, and polarity; its effective scheme interprets them. - Optional Bridge Card. It packages claims and evidence when durable reuse pays. It neither creates the relation nor grants the use.
- Separately governed receiving object. If the use happened, its Work, assertion, publication, direct relation, operation application, or other object keeps its own participants, obtaining or performance condition, and identity.
Use that notation only after the F.9 predicate passes. For a proposal, write candidate Bridge(...) or use a candidate card with no positive occurrence reference.
Changing u, d, r, or t changes the bounded-use claim, not the Bridge. Changing evidence, an independently established relation cited by the A.10 path, the local RelianceDisposition, or a B.3 claim, record, or disposition reopens reliance without reidentifying the Bridge or the bounded-use claim. A changed endpoint or relation-semantic profile identifies another Bridge candidate.
Claim skeleton
Use this table for the semantic branch. The action, direction, rule, and tolerance rows apply only to a proposed use of an obtaining Bridge.
Only the two endpoint cells fill the direct relation's participant slots. Use content is ClaimGraph content, not another relation participant or profile component.
Judgement and change
State the F.9 kind warranted by the correspondence or difference at issue: Equivalence, Narrower-than, Broader-than, Partial-overlap, Disjoint, or one declared cross-family relation kind. The kind settles relation semantics only.
If a Bridge obtains and a use is proposed, judge that use separately:
Partial-overlapcan support an affirmative label-use claim when its rule preserves the named differences; the Bridge does not grant that use automatically.Disjointcan support a contrastive explanation. A substitution that requires shared meaning receives negative polarity; other proposed uses still need their own rule and tolerance.Equivalenceis symmetric, butA -> BandB -> Aare different use claims.Narrower-thanandBroader-thanorient the semantic relation. Narrower-to-broader is usually easier to warrant, but every use direction still needs its own rule, tolerance, and polarity; recover reliance when someone will rely on that claim.- For a broader-to-narrower use, establish the target conditions required by that use. This may require fresh classification, a bounded use restricted to qualifying cases, or refined cells with a separately tested Bridge. Merely changing a profile cannot make an unsupported use safe.
- Type-structure reuse requires a separate claim naming the structural rule and loss tolerance. Matched invariants can support that claim; no
CLnumber grants it.
CL may remain optional evidence shorthand: 0 contradicted, 1 weakly comparable, 2 bounded support with counterexamples, 3 matched stated invariants with no current material counterexample. It is neither profile identity nor a suitability threshold.
Narrate changes by the object that changed:
- when an endpoint changes, identify the new source or receiving cell;
- replace the Bridge profile when its relation-semantic content changes;
- revise the bounded-use claim when
u,d,r,t, effective scheme, or polarity changes; - retest the fixed Bridge predicate when endpoint facts or dependencies change;
- reassess reliance when evidence, currentness, a direct relation cited by the A.10 path, the local
RelianceDisposition, or a B.3 claim, record, or disposition changes; - revise the Bridge Card when its package content changes;
- when reporting a publication occurrence, identify the published Bridge Card edition; and
- identify the actual receiving object when the use is claimed to have happened.
An inverse asymmetric relation and any direct A-to-C relation require their own profiles and tests. Two chained Bridges do not entail a third.
Lexical guardrails
When normative or decision-carrying wording leaves its meaning unresolved, expose the action and any necessary stop:
Keep clear same, align or map wording, including in technical prose. Add a non-inference only when the rejected reading has independent local grounds, a plausible intended reader could take it here, and the distinction changes truth, understanding or action. Use the smallest sufficient correction under F.19:4.
Disambiguation guide
Mapping witnesses are not Bridges
A lookup table, aligner model, transformation function, API or ETL step may implement or represent a mapping. Its content may express claims or supply grounds for a Bridge or a bounded-use judgment; its mere presence or successful execution does not establish either. Code may run A → B while the semantic relation is symmetric, oriented the other way or absent. Even an obtaining Bridge needs a separate judgment for the operation's rule and tolerated loss.
Assess a mapping witness's content and grounds against the F.9 predicate. Recover an A.10 account when provenance, currentness or reliance must remain replayable; use a Card when reusable packaging is warranted. If a Bridge obtains and a use is proposed, state the C.2.1 bounded-use claim and recover reliance when someone will rely on that claim.
Coordination boundaries
- Naming and endpoint objects: F.18 selects designators; F.17 governs scheme-based cells and rows. A
SchemeSenseCell, C.2.1 description episteme, designator, and resolving reference remain distinct; none creates a Bridge. - Reference scheme and scope: C.2.1 is the pattern for the effective interpretation rules (
ReferenceScheme); A.2.6 is the pattern forU.ClaimScope,widen,narrow,refit, andtranslate. A.2.6 translation may consume a Bridge plus its affirmative bounded-use claim but is not representation Work or structure crossing. - Grounding: C.2.1 alone supplies an
EpistemeEmpiricalGroundingRelation. Its grounding holon is the participant against which covered empirical claims are grounded; it is not assumed identical to the episteme's EntityOfConcern. - Time: the qualification window is part of the temporal or subject predicate and assertion. F.9 profile applicability or
Γ_timedoes not become a generic context or time participant for another claim. - Project wording: keep an ordinary project label or plan under its own meaning. When an actual composite project Work is deliberately asserted, use A.13, independent A.15.1 admission, and A.15.6 with work parthood. A label, plan or Bridge alone establishes no such occurrence.
- Viewpoint: E.17.0 governs the direct
EpistemeViewpointConformanceRelation; oneU.ViewpointRefresolves viewpoint episteme P. The viewpoint, its reference, candidate/View episteme, and evaluator remain distinct. - Evidence and assurance: A.10 is the pattern for evidence provenance and local reliance; B.3 is the pattern for assurance claims, records, and explicit dispositions.
- Representations and publications: E.17.0 governs conformance-dependent View membership and E.24.PUB publication occurrence/form/carrier. Apply the direct representation rule; use C.29 for an unresolved mathematical-lens choice, correspondence, or transfer question. A.6.3.RT starts an ordinary same-concern representation move with content to survive, source comparison, material loss and supported use. Add a source-return condition and destination when return is needed for that use. Its triggered construction independently identifies
X,Y, andv; actual representation-transformation Work is required only for the six-participant occurrence. - Kinds and classifications: C.3.3 establishes the
KindBridgebetween source and target local kinds. C.3.2 separately judges the candidate under the target kind, targetKindSignatureedition, and target slice; the result may betrue,false, orunknown. F.9 supplies only local-sense correspondence needed by that use. - Structures: identify the structures under their defining rules and use A.22 for
U.Structureidentity. Ordinary comparison uses the criterion needed by the receiving question. When §4.8's crossing-organization question is current, A.1.1/A.22 independently establish each participatingBoundedModelUseStructure; the conditional cross-structure rule additionally requires governed crossings and all four structure discriminators. A SenseCell Bridge cannot substitute for that architecture. - Direct subject relations, Work, and system-role claims: a world-side relation obtains under its own predicate and participant conditions, independently of whether an assertion describes it. A.2.1 governs assignment. Actual Work requires A.13 and independent A.15.1 admission; F.6 applies only for precise assignment-bound attribution, and A.15.6 for the separately claimed composite Work. A semantic relation or use claim establishes none of those occurrences by itself.
- Permission: apply A.2.8.PER and cite the result the proposed use needs—an obtaining strong grant, weak non-prohibition finding, exercise relation, or conflict result. Policy and direct predicates supply conditions or grounds but are not the permission result. Any required authority relation remains separate.
Structure comparison and conditional cross-structure selection
Use this branch only when the receiving question depends on the organization of actual subject crossings among several bounded model-use structures. First recover every participating BoundedModelUseStructure independently under A.1.1/A.22: one model episteme, its admitted model-use holons, the obtaining applicability, actual-use, and fixed-content model-expression-coherence occurrences, the applied constraint claims, and one named bounded-model-use frame. A shared system, model, episteme, scope, or other participant does not merge two selected structures and proves neither overlap nor parthood.
Next enumerate every obtaining subject-crossing occurrence selected for the proposed organization. For each one, name its participants, relation kind and predicate, direction when asymmetric, applicability, obtaining result, occurrence identity, and recurrence rule, and test them against the pattern that defines those relation rules. An F.9 Bridge relates local senses only. Context labels, edge labels, Cards, registry rows, references, Views, diagrams, and common participants may help locate the proposed crossing's objects or evidence; only an occurrence satisfying its direct governor establishes that crossing. If no current pattern defines a required crossing, stop through A.6.RCD at the missing-governor question; do not replace it with a vague edge family.
Only then apply A.22's conditional cross-structure rule for one named receiving or crossing-analysis use. Declare the substrate as the independently selected BoundedModelUseStructure values; the selected relation organization as the obtaining crossing occurrences; the applied constraints and invariants; and the use frame as the question, admissible action and necessary use boundary. Those are the four A.22 discriminators. Include an explanatory forbidden reading only under the F.19:4 guard test. The A.22-local label CrossContextRelationStructure serves only as a retrieval aid under that rule; A.6.9 gives it no public-vocabulary use. The resulting U.Structure is the dependent organization identified by those four discriminators. Container or holon identity, context grouping, and the crossing occurrences remain governed separately. Any U.View, Context Map, diagram, Card, or publication that depicts, packages, or carries the organization retains its own identity and relation to it.
A selected structure can be described by its four discriminators without inventing a dated selection Work. If the claim concerns an actual selection judgment, identify that judgment and result under its own rule; preserve a C.2.1 result episteme with the structure as EntityOfConcern when persistence is needed. If a particular dated selection Work is deliberately asserted, establish its A.13 basis and independent A.15.1 admission, with F.6 only for precise assignment-bound attribution; identify the system, Method and participation or A.6.1 bindings required by that Work claim. An accountable decision additionally needs its own decision rule. These objects remain separate from the structure's four discriminators; every selected crossing still needs its direct governor.
Archetypal Grounding
System archetype: IAM User and CRM Customer
The ambiguous sentence is: “An IAM User is the same as a CRM Customer.”
Treat this as a schematic hypothetical illustration. The abbreviated endpoint readings are:
SenseCell(IAMRoleReferenceScheme-v3, User-human-or-service-account-role);SenseCell(CRMRoleReferenceScheme-v5, Customer-commercial-party-role).
These sketches name the intended scheme editions and sense readings. A full case must still resolve each <ReferenceScheme by value, LocalExpression, LocalSenseClaim> value, with User and Customer as the respective local expressions.
For the illustration, assume that the local meanings share some human cases, while service accounts and prospects provide cases excluded by the opposite reading. These are additional hypothetical premises, not facts recovered from the ambiguous sentence. Profile P-IAM-CRM-OVERLAP-v2 states the symmetric Partial-overlap relation, endpoint readings, overlap and difference conditions, edition basis, truth condition, and required membership evidence. The example additionally stipulates that the profile applies and its predicate is true, and therefore uses b-iam-crm as an obtaining Bridge. The profile description lists what a full test needs; it does not supply that test or its evidence.
Now state the use separately. Dashboard team proposes u-actor-label: render IAM users as “actors” in a CRM-oriented comparison. Direction d-iam-crm is IAM-to-CRM dashboard reading. Rule r-actor keeps account eligibility and customer eligibility visible as separate columns. Tolerance t-actor allows the shared label but no eligibility, assignment, workflow, or Work inference. A C.2.1 claim about b-iam-crm is affirmative for <u-actor-label,d-iam-crm,r-actor,t-actor>.
Reliance on that claim remains conditional on the descriptive A.10 evidence-provenance path, the independently established direct relations it cites, and RelianceDisposition=pass for the named dashboard comparison. A hypothetical passing result would be an additional example premise, not a result recovered from the endpoint sketches. It would not authorize data processing, create a system-role assignment, or prove that a dashboard publication occurred. Reverse label reuse is another bounded-use claim even though the Bridge relation is symmetric.
An optional actual card may package the Bridge claim, this bounded-use claim, observed counterexamples, the A.10 path and disposition, currentness and any independently grounded use restriction that passes the F.19:4 test. Its EntityOfConcern is b-iam-crm; the card neither creates the relation nor performs the dashboard work.
If a later workflow isolates HumanVerifiedUser and VerifiedCustomer, distinguish a restriction to qualifying cases from a change to the local-sense readings. For a case restriction, retain the existing endpoints and establish the target conditions and bounded-use claim. If a reading changes, identify the changed endpoint and test the resulting Bridge candidate. A stronger use claim over the broad cells cannot make a false relation predicate true or establish an unsupported use.
Episteme archetype: Person in two knowledge-graph schemes
The sentence is: “Person in KG-A is equivalent to Person in KG-B.” The named readings are Person-including-fictional under KG-A v4 and Person-real-with-external-id under KG-B v7. Sherlock Holmes illustrates the fictional-person distinction; the external-id rule adds another membership condition. These cues establish neither Partial-overlap nor inclusion.
To test Partial-overlap, recover the membership definitions and a common admissible case, an A-only case and a B-only case. To test inclusion, establish the chosen proper-inclusion predicate from those definitions and case facts; the short labels do not supply it. Until then, stop and name the missing membership definition or case fact. No overlap Bridge is asserted by this sketch.
The two proposed uses remain conditional illustrations. If a Bridge obtains, a glossary comparison that labels both rows “Person” while displaying the fiction and external-id differences can receive affirmative polarity only for a stated direction, correspondence rule and loss tolerance, with a warranted A.10 result when relied on. A type-structure merge receives negative polarity only when its direction and merging rule cannot preserve membership and its tolerance permits no such loss. Those rule and case premises still have to be supplied.
When their basis is supplied, both claims concern the same obtaining Bridge; neither changes its identity. Refining KG-A into RealPerson and FictionalPerson changes an endpoint and opens a new Bridge test.
Published NAICS language and a Conformist cue
Consider a hypothetical application with the following independently identified objects. C.2.1 identifies the model episteme edition NAICS-2022-ClassificationEpisteme by its ClaimGraph, EntityOfConcern, and effective ReferenceScheme; A.1 independently identifies IndustryClassificationApplication-7 : U.System. If availability matters, E.24.PUB separately tests EpistemePublicationRelation(NAICS-2022-ClassificationEpisteme, ClassificationAudienceDeclaration-2, ClassificationUseDeclaration-5, NAICS-2022-TableExpression, NAICS-2022-PDFCarrier) together with its expression and expression-bearing occurrences. Identify NAICS-2022-TableExpression independently as the keyed typed classification table, and test its conformance to reusable NAICS-2022-TableForm when that form matters. The episteme, publication occurrence, expression, form, carrier, declarations, and application system keep different identities. Publication establishes availability to the audience and use declarations. Access, adoption, applicability, actual use, performed Work, and any application-side parthood remain claims under their own predicates and facts.
Recover the use branch before selecting structure. Establish the A.13 basis and independent A.15.1 admission of ClassificationWork-4. This model-use claim additionally consumes assignment-bound attribution: require HolderSystem(ClassificationAssignment-3)=IndustryClassificationApplication-7, F.6 performedUnderAssignment(ClassificationWork-4, ClassificationAssignment-3), and the application's actual use of the selected NAICS content during that Work concerning ClassifiedOrganization-42; only then may ModelUseRelation(ClassificationAssignment-3, NAICS-2022-ClassificationEpisteme, ClassificationWork-4, ClassifiedOrganization-42) obtain. A positive NAICSClassificationModelUseStructure additionally requires ModelApplicabilityRelation(NAICS-2022-ClassificationEpisteme, ClassifiedOrganization-42, ClassificationClaimScope), fixed-content coherence with the classification-expression episteme under a declared predicate and ReferenceScheme, applied constraint claims naming the edition and classification distinctions to preserve, and NAICSClassificationFrame: “Which NAICS edition and distinctions govern the classification of ClassifiedOrganization-42 as a complete organization?” Model use comes from the actual-use facts above; any application-system parthood claim requires its own predicate and facts. Without the complete A.1.1/A.22 basis, stop at publication availability or the direct relation that does obtain.
Treat DDD Conformist only as a Plain cue to a proposed directed subject dependency. Preserve the proposed source, target, direction, adoption condition, dependency predicate, update authority, required preserved meaning, permitted loss, claim scope, and standard-edition basis. A positive occurrence would additionally require participant meanings and fillers, its direct relation kind and predicate, obtaining and applicability conditions, occurrence identity and recurrence, all supplied by one compatible direct subject governor. The label, published-language status, table edge, and selected structure may cue or represent the proposal; only a compatible direct subject governor supplies its predicate and occurrence rules. When no such governor is current, return missing CROSS-LOCALITY-BRIDGE governor.
An F.9 Bridge may separately obtain between NAICS-side and application-side SchemeSenseCell values and may support one bounded interpretation claim. Adoption, dependency, update authority, preservation of application meaning, and a subject-crossing occurrence remain separately governed claims. A later NAICS edition is a distinct C.2.1 episteme. Before NAICSClassificationModelUseStructure is selected for that edition, establish applicability, actual use, coherence, preservation, loss, and any governed crossing for the edition. Republishing unchanged claims in another form or carrier changes the publication objects only; it does not establish the application's use of another episteme edition.
Bias-Annotation
This pattern is biased toward:
- Explicit action over fluent ambiguity. It slows only sentences that would otherwise hide what someone will do.
- Relation-use separation. One Bridge can support several independently tested uses without becoming a licence.
- Locality of meaning. Scheme and local-sense claims provide the interpretation basis without a reified context bearer.
- Evidence humility. Scores, counterexamples, and invariants inform claims and reliance but do not manufacture relation truth or permission.
The dispatch stays cheap: same-context designation and other directly governed cases stop before F.9. Use the F.9 branch when the current question needs a cross-local semantic relation. A separate bounded-use claim is needed only when a use of an obtaining Bridge is proposed.
Conformance Checklist
A repaired sentence or boundary statement conforms iff:
- Concrete action. The reader can say what object, comparison, substitution, translation, publication, or other action is at issue.
- Use the applicable subject rule. Recover only the reference-scheme, scope, grounding, time, project, viewpoint, representation, structure, subject-relation, identifier, system-role or Work claim actually made. A clear ordinary statement does not require all those neighboring objects.
- Endpoints. Every Bridge candidate uses two F.17 cell addresses resolving values.
- No context proxy. Semantic bounded context is the Plain local interpretation basis recovered from the endpoint projection; it is not a project situation, model-use structure, scope, grounding, time, viewpoint, identity, or direct relation participant.
- Direct Bridge truth. A positive occurrence appears only after the profile applies, its predicate is true, and dependencies are present.
- Profile boundary. Profile identity contains relation semantics only, with no use, tolerance, polarity, reliance, authorization, or receiving object.
- Separate use claim. Every proposed use of an obtaining Bridge names
u,d,r,t, polarity, and effective scheme in a C.2.1 claim about the Bridge. - Evidence honesty. Mapping artifacts may carry claims and grounds; evaluate their contribution under the applicable evidence rule. Keep observed loss separate from the permitted loss in the bounded-use claim. CL grants nothing.
- Reliance branch. Current reliance follows A.10 or B.3 for the same use and does not become authorization.
- Receiving-object boundary. Any claim that the use happened names the actual object and states the concrete claim using the rule that defines its predicate.
- Card boundary. Actual, candidate, and negative cards use the correct EntityOfConcern and never create a Bridge or receiving occurrence.
- Change honesty. Endpoint, profile, use claim, reliance, card, publication, and receiving-object changes remain distinct.
- No inferred inverse or composition. An asymmetric inverse, opposite use direction, or direct A-to-C Bridge gets its own judgement.
- Practical result. The final sentence conveys the useful action and any necessary stop or reopen condition. An explanatory non-inference passes the independent-ground, plausible-reader and contribution tests in §4.4.
- Same-locality route. Same projection uses ordinary designation and, when claim extent changes, A.2.6
widen,narrow, orrefit; it does not mint a Bridge. - RT boundary. An ordinary A.6.3.RT note states the same concern, preserved content, representation delta, material loss and supported use. It includes a source-return condition and destination when return is needed for that use. A triggered construction adds
X,Y, andv; actual representation-transformation Work enters only when the six-participant occurrence is asserted. None is scope translation or a Bridge. - Structure boundary. When §4.8's crossing-organization branch is current, each participating
BoundedModelUseStructureis independently selected; every selected subject crossing satisfies the predicate and obtaining condition defined for that relation, with its participants and occurrence identity explicit; and the conditional A.22 cross-structure selection names substrate, relation organization, applied constraints and invariants, and receiving-use frame. Recover a separately claimed selection judgment or dated selection Work under §4.8; identify a result episteme when persistence is needed and a governed decision when an accountable choice is claimed. Missing relation law returns the A.6.RCD missing-governor stop; shared participants or artifact presence alone establish none of these facts; their content may supply claims or grounds under the applicable rule. - Grounding and endpoint distinctions. Grounding holon and EntityOfConcern are not assumed identical; every SenseCell, description episteme, designator, and reference remains distinct.
- Published-model crossing stop. The NAICS replay independently identifies the episteme edition and application system, keeps E.24.PUB occurrence/form/carrier separate, recovers applicability and actual model use before structure selection, and treats Conformist as a proposal only. If the receiving use selects another edition, establish applicability, actual use, coherence, preservation, loss, and any governed crossing for that episteme before selecting the structure. A positive adoption, dependency, or update-authority crossing requires a current pattern that defines its predicate, obtaining condition, and identity rule; an F.9 Bridge or publication evidence may support but does not supply that governor.
Common Anti-Patterns and How to Avoid Them
Consequences
-
Pros
- Turns ambiguous sameness into a visible relation question and a visible action question.
- Lets one Bridge remain stable while use direction, tolerance, evidence, and polarity change.
- Prevents scores, cards, assurance, and publications from becoming hidden permission or occurrence.
- Gives authors local stops instead of a vague “not equivalent”.
-
Cons
- A positive use normally needs two sentences instead of one adjective.
- Reviewers must inspect the correspondence rule, tolerated loss, and evidence for the named action.
- Many “same” claims become only an explanatory comparison or a negative use claim.
Adoption test (PRAG). Take one sentence containing same, equivalent, align, or map. A practitioner passes when they can name the concrete action and state the truthful result of the selected branch. A non-semantic result uses its concrete predicate or constraint and exits before F.9.
For a semantic-correspondence question, resolve the local senses and decide whether the F.9 branch applies. If it does, recover the cells and profile and say whether the Bridge obtains. Distinguish a false predicate result or an inapplicable case from missing facts or a missing governor. Only a proposed use of an obtaining Bridge additionally needs the separate bounded-use claim and, when someone will rely on it, the applicable reliance result. Name any required authorization or claimed receiving occurrence that remains missing. If the wording prevents recovery, keep it explanatory and name the missing meaning; a complete false test is not missing information.
Rationale
Cross-context sameness wording is not one predicate. A.6.9 first restores the question and states designation, lane, id, scope, representation, structure, system-role-kind, assignment, and Work claims in ordinary language using their concrete rules. Add C.2.1 assertion and ClaimGraph identity only when a later use must carry or compare one of those claims independently. Only a remaining cross-local semantic question uses the F.9 Bridge predicate.
For that branch, cells and a relation-only profile make correspondence falsifiable. A separate C.2.1 claim makes the proposed use equally explicit without reidentifying the Bridge. A.10 or B.3 can reopen reliance without changing either object. Authorization and the actual receiving object remain visible rather than hiding inside suitable, aligned, or mapped.
The repair sequence is therefore: name the action and route the object; for a remaining semantic-correspondence question, test F.9; for a proposed use of an obtaining Bridge, state the use claim and check reliance when someone will rely on it; recover permission or performance only when claimed.
SoTA-Echoing
(informative; post-2015 alignment)
Relations
- Specialises: A.6.P by restoring the concrete object and action hidden by cross-context sameness wording.
- Uses: F.17
SchemeSenseCellidentity; F.9 Bridge participants, relation-only profile, obtaining, occurrence identity, bounded-use boundary, and card boundary; C.2.1 claim identity and polarity; A.10 or B.3 for reliance. - Coordinates with: F.18 and F.5 for designators; A.6.6 for an identification or indexing relation whose meaning or participants remain hidden; C.2.1 for effective reference scheme, episteme edition, and empirical grounding; A.2.6 for scope operations; A.15.6/A.15.1 for composite project Work; the patterns that define the temporal and direct predicates for their qualification windows; E.17.0 for viewpoint conformance and View membership; E.24.PUB for publication occurrence, form, and carrier; C.29 for an unresolved mathematical-lens choice, correspondence, or transfer question; A.6.3.RT for the ordinary same-concern representation note, triggered construction, and occurrence only when actual Work is current; C.3.3 for the cross-local
KindBridgeand C.3.2 for the fresh target judgment; A.1.1/A.22 and the pattern that defines each selected structure crossing; A.2.8.PER for the permission result and any direct pattern needed for a separate authority relation. - Constrains: every proposed use of an obtaining Bridge to cite an obtaining Bridge, state a separate C.2.1 claim for its direction, rule, tolerance, and polarity, recover current reliance when someone will rely on that claim, and state any claim about the actual receiving object using the rule that defines its predicate.
A.6.9:End
TargetSignature and optional ConstructorSignature - demand-driven signature engineering
Type: Architectural (A) Status: Stable Normativity: Mixed (normative where RFC 2119 keywords appear; quadrant classification is governed by A.6.B) One-liner: Start from the signature assertion, revision, relation, operation application, or Work. Add a separate ConstructorSignature only when a named receiving use needs reusable constructor vocabulary, laws, and applicability. Keep an operation description, any mathematical arrow, its application, performed Work, and publication faces distinct.
Object boundary. A.6.S admits no U.SignatureEngineeringPair kind or durable arrangement individual. The spelling is retired. TargetSignature and ConstructorSignature are use-specific designations for two independently identified U.Signature epistemes; neither designation adds another kind, constitution relation, or identity discriminator. Merely pairing two documents or naming both signatures establishes no relation between them.
Use this pattern when a project already has, or needs, a reusable signature that declares how another signature is to be authored or revised, and at least one named receiving use needs that declaration to remain stable across applications, editions, or publishers.
Do not use this pattern merely because one signature is edited, one direct relation is stated, one view is prepared, or one work occurrence changes a carrier. Apply that direct rule and stop. A one-off revision needs no ConstructorSignature.
First useful move. Say what changes in ordinary language: for example, The editor added the refund law to PaymentBoundarySignature and issued edition 4. Identify the changed signature episteme and, when current, the operation application, System, Work, result, or edition relation. Only then ask whether a later receiver needs a reusable declaration of the constructor operations.
What goes wrong if missed. At one extreme, the signature, the operation description, and the Work that changes or publishes it collapse into one “contract/editing” story. At the other, every small edit acquires a second signature, a pair object, two operation lexicons, and a full attribution package.
What this buys. The light path stays light. Where repeatable constructor language has users, the ConstructorSignature can preserve that language while the TargetSignature, operation description, A.6.2 arrow, application, Work, assignment, carrier, and publication view keep their own identities and direct relations.
PCP-TERM/LEX token guards (local-first)
This pattern reserves the following tokens in Tech (normative) register:
- TargetSignature — the engineered signature episteme (and its editions) under construction and stabilisation (not the EntityOfConcern, and not the target source or cell of an F.9 relation).
- ConstructorSignature — the enabling signature that describes constructor operations for TargetSignature evolution (do not mint a second Tech token such as
EnablingSignature).
Rename-guards (common collisions):
- enabling — Plain adjective meaning “producing/maintaining the TargetSignature”; it is not a
U.*token. - constructor — distinguish the objects consumed by the claim: ConstructorSignature, constructor-operation description, any A.6.2 mathematical arrow, the applying System, and independently admitted Work. A system-role classification or assignment is a separate claim. Spell out Constructor Theory when that physics concept is intended.
- target — qualify the word when its intended object is ambiguous: for example, TargetSignature, F.9 target cell or target holon. A locally clear use needs no repeated expansion.
- contract — if source wording uses this Plain shorthand, recover whether it means
TargetSignature, Contract Bundle, promise content, commitment, or work/evidence. In this pattern the intended recovered value is usuallyTargetSignature; promises, duties, and gates are classified underA.6.BandA.6.C.
Problem frame
Boundary descriptions often arrive as “half-signatures”: an n-ary relation in ordinary prose, overloaded markers such as binding, anchoring, or contract, and unstated assumptions about participants, applicability, and publication. Teams then revise the boundary through edits, reviews, and partial publications.
A.6.5, A.6.6, A.6.2-A.6.4, and E.17 already govern several different moves that may occur during that work. The missing discipline is not a universal engineering container. It is a proportional choice:
- state the edit, relation, arrow, application, Work, edition, or view and stop when that answers the use; or
- when a named receiver needs the same constructor vocabulary and laws again, identify a separate ConstructorSignature and state the dependency or use that connects it to the work.
Without that choice, four failures recur:
- the TargetSignature, constructor-operation description, application, and performed Work are conflated;
- a one-off revision is inflated into a durable two-signature apparatus;
- semantic changes hide behind generic edit language instead of identifying the receiving episteme and any actual edition, continuity, or reference change; and
- publication views acquire claims not present in the described signature.
An episteme does not act. When performed Work is claimed, recover each actual performer U.System and the complete A.13 core, then independently admit the dated occurrence under A.15.1, as set out in §4.0. A System may separately apply a described operation. Use F.6 afterward only for a receiving claim that consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and the assignment itself does not act.
Problem
FPF needs a pattern for engineering signatures as boundary epistemes: a disciplined way to construct, revise, and publish a target U.Signature from partial input, while maintaining:
- separation between signature and mechanism (A.6.0 vs A.6.1),
- separation between laws, admissibility, deontics, and work evidence (A.6.B),
- explicit multi‑view publication without semantic drift (E.17),
- reproducible evolution across editions without silent mutation.
Forces
-
Stability vs evolution. TargetSignatures must be stable enough to coordinate, yet change as understanding improves.
-
Explicitness vs overhead. Unpacking slots/bases/views increases clarity but also increases authoring effort.
-
Arrow law vs enacted work. An A.6.2 arrow may state the effect-free relation between source and receiving signature epistemes. An application of the described constructor operation has its own predicate, extent, and identity rule under A.6.1. Claims about a created successor or written carrier identify the changed object and effect; any performed Work is admitted separately. For performed Work, recover each actual performer's complete A.13 core and let A.15.1 independently admit the occurrence, as in §4.0. Add F.6 only when a later claim expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 checks that exact Work-assignment link and identifies neither the assignment nor the performer. Missing or failed F.6 alone leaves the Work intact.
-
Multi‑view richness vs semantic coherence. Views help stakeholders, but they risk becoming divergent “versions of truth”.
-
Local meaning vs cross-local reuse. Signature claim content pins its effective ReferenceScheme where interpretation matters. The local kind and any source-local meaning remain separate values. Use F.9 for an actual semantic Bridge between local senses whose
<ReferenceScheme, LocalSenseClaim>interpretation bases differ, and judge its bounded-use claim separately. Distinct F.17 cells or a mapping alone do not establish that relation. -
Contract talk vs ontology. “Contract” language invites mixing promises, norms, and invariants; FPF requires quadrant discipline.
Solution - start with the direct move; add a ConstructorSignature for named reuse
Keep the signature, arrow, application, and Work separate
The smallest account names the object and move. Describe a signature revision through its source and receiving signature epistemes. A changed C.2.1 discriminator identifies another episteme; an edition or continuity relation requires its own source use, continuation rule, and preserved or deliberately changed features. Republishing unchanged claim content need not identify another episteme. A view, direct relation assertion, operation application, carrier write, and performed Work remain under their own patterns.
A ConstructorSignature is optional. When used, it is a U.Signature whose reusable declaration content describes a family of constructor operations: its subject and value or result range, vocabulary, laws, and applicability. It does not perform those operations and does not contain the Work that applies them.
If a constructor family also uses an A.6.2 mathematical arrow, identify that arrow separately. The arrow relates source and receiving epistemes. Its rule states how their claim content, EntityOfConcern, and effective ReferenceScheme compare. When it reads a neighboring grounding, representation, conformance, edition, or provenance occurrence, name that occurrence and the endpoint facts compared; the arrow neither changes the occurrence nor makes it obtain. A.6.3 and A.6.4 apply only to their viewing or EntityOfConcern-retargeting cases.
When dated authoring, deriving, materializing, validating, storing, or publishing Work is claimed, first recover each actual performer as a System under A.1 and its complete A.13 core: the local agential system-role kind and criterion, System classification, obtaining A.2.1 assignment, and the scope, working situation, and window needed by the use, with evidence for those claims. A.15.1 then independently admits the dated occurrence from its performance history, at least one Method actually followed, temporal extent, and at least one obtaining locally declared containing-System relation. Use F.6 afterward only for precise assignment-bound attribution through that same obtaining assignment; missing or failed F.6 alone leaves the independently admitted Work intact. Recheck an admission premise only when the same finding questions it. Additional classifications or assignments, an operation application and its bindings, the resulting episteme, and carrier, evidence, or publication relations enter only when their own claims are current. Add an agency-characteristic profile only when the local criterion, a claimed characteristic, or an assurance use requires it under A.13/A.15.1.
Decide whether a second signature is needed
Start with the TargetSignature: the U.Signature being authored, stabilized, or revised. Its A.6.0 declaration content identifies its subject and value or result range and supplies the reusable vocabulary, laws, and applicability that make it a signature. It contains neither operational gates, deontic duties, evidence claims, nor construction Work merely because those topics occur nearby.
Add a ConstructorSignature when a named receiving use needs reusable constructor-operation vocabulary, laws and applicability under A.6.0:4.8. This may serve later editioning, another authoring System, publication or another use that would otherwise reconstruct the same declaration. A concrete anticipated use can justify it; an observed second consumer is not required. A one-off edit, assertion, arrow, application or Work occurrence by itself supplies no such need.
The two signatures remain separate C.2.1 epistemes. State only the relation that is current:
- when one signature cannot interpret a required term or replay a law without the other, use the A.6.0 declaration-dependency claim;
- when a System uses a Method or MethodDescription that cites the ConstructorSignature while revising the TargetSignature, state that method/source use and any actual application or Work under its direct pattern;
- when both signatures are merely relevant to the same local question, name them without inventing a pair relation; and
- if a receiving use needs a relation between them, use its direct rule or A.6.RCD for a missing rule; add explicit occurrence identity only when needed. A new framework pattern follows E.24, and a proposed U-kind follows E.24.UK. A.6.S admits no generic pair relation.
TargetSignature and ConstructorSignature are Tech designations of each signature's place in this use, not local system-role kinds. A publication may explain TargetSignature as “the signature being engineered”. SoI designates a product System in an extended enterprise under A.1.STM, rather than this episteme. Do not conflate the TargetSignature with its C.2.1 EntityOfConcern. Distinct signature editions remain distinct epistemes when their C.2.1 discriminator triples differ; any empirical-grounding, edition, continuity, dependency, source-use, or publication relation remains separately identified.
Choose the constructor vocabulary that the receiving use needs
A ConstructorSignature declares only operation families that a named receiver will reuse. It need not contain both A.6.5 slot operations and A.6.6 declaration-change labels, and it need not contain either family when another direct operation declaration is enough.
Designation operations, when current. Use A.6.5 for designations governed by a compatible RelationSignature SlotSpec: supplying or replacing a designation, typed substitution, reference retargeting and reference resolution. Keep the declaration, designation and actual participant distinct. Operation arguments and results remain A.6.1 declarations, and durable naming follows F.18. A reference retargeting and a change in its referent are different operations; ordinary wording may state either without a new SlotSpec.
Assertion or declaration history, when current. Use A.6.6 first to state the actual dependent, base, and direct relation. Stop when that readable assertion answers the use. If a named receiver needs the history of an optional assertion representation or reusable declaration, its local labels such as declareBase, rebase, rescope, retime, or refreshWitnesses may describe which represented field changed. They do not establish or change the world-side relation. Changing a witness reference is a designation edit. A claim that new evidence was produced needs its own basis; any deliberately asserted dated production Work follows §4.0.
Mathematical arrows, when current. An operation description may cite an A.6.2, A.6.3, or A.6.4 arrow only when that mathematical relation is useful to the receiver. The ConstructorSignature states the arrow family and the endpoint values or facts it reads or compares. The arrow remains effect-free; an application that produces a receiving episteme and any performed Work remain separate.
Publication operations, when current. For E.17 publication, a ConstructorSignature may declare a reusable publication or view-producing operation when its named receiver needs that declaration. Apply A.6.3 only when the operation uses a mathematical source-to-receiving viewing construction; identify those epistemes and the viewing rule. Keep the publication face faithful to its source and apply §4.4 for any separate U.View claim. For publishing a face, writing a carrier, committing a file, or issuing a release, distinguish any claimed operation application under A.6.1, any actual changed-object or effect claim, and Work admitted under §4.0. Neither signature performs those actions.
The test is practical: remove the proposed operation family. If the named receiver can still perform or assess its use without reconstructing a shared vocabulary or law, leave that family out.
Change discipline: Viewing vs Retargeting vs editing
When more than one distinction is current, classify each move separately rather than forcing all four buckets into every revision:
-
Publication form and conditional viewing. A presentation change (views, stakeholder cards, projections) may be an E.17/E.24.PUB form or carrier change. Use A.6.3 only when a mathematical source-to-receiving viewing construction is current, preserving the EntityOfConcern; E.17.0 separately governs any
U.Viewmembership claim. -
Direct edits and conditional declaration history. State a one-off vocabulary, law, applicability, or reference change directly. Use A.6.5 only when a compatible RelationSignature SlotSpec governs the needed declaration or designation operation; other references retain their direct rules. Use A.6.6 declaration history only after the actual base-dependence relation is stated and a named receiver needs that history.
-
Editioning and reference retargeting. When downstream use selects a new TargetSignature edition, identify that edition and retarget the references that must resolve it. Apply each reference's direct resolution and continuity rules; A.6.5 applies only where a compatible SlotSpec governs its designation. Preserve the previous episteme for uses that still select it.
-
Epistemic retargeting and structural reinterpretation (A.6.4; rarer). Use only when the source and receiving
EntityOfConcernRefvalues resolve to different EntitiesOfConcern. A reference-only change that still resolves to the same entity stays with its actual reference operation. A.6.4 identifies the source and receiving epistemes and one arrowr. For a claimed receiving use, state a separate C.2.1 bounded-use assertionqaboutr, with the invariant, visible loss, named use, conditions, and affirmative or negative polarity. When a current-case judgement is needed, compare the facts withqand return exactlysatisfies,fails, orcannot decide;cannot decidenames the missing fact and reopen condition. This is distinct from an ordinary new edition of the same TargetSignature.
Rule of thumb:
- If only the publication form or carrier changes, use E.17/E.24.PUB and stop; no slot/base declaration is required unless another receiving use needs it.
- If the change is “new TargetSignature edition for consumers”, identify the new edition and retarget the references whose receiving use now selects it.
- If the change is a different EntityOfConcern, use A.6.4 to identify the arrow
r. State a separate C.2.1 bounded-use assertionqwhen a receiving use is claimed, and a separate current-case judgement when that case is evaluated. A kind difference alone identifies none of them.
EFEM discipline.
When a constructor operation uses an A.6.2 arrow family, declare its endpoint comparison and entityOfConcernChangeMode under A.6.2. An operation description that needs no mathematical arrow introduces none.
Editioning is orthogonal: you MAY mint a new edition even under preserve; references whose receiving use now selects that edition MUST be retargeted explicitly, with A.6.5 slot discipline where applicable.
For an actual measurement, actuation, validation run, carrier write, or other effect, identify any claimed operation application under A.6.1, changed-object or effect claim under its direct rule, and Work under §4.0 independently. An effect alone establishes neither application nor Work; the A.6.2 arrow performs none of these actions.
Add publication and claim controls only when they are current
For E.17 publication, choose a faithful publication form for the bounded reader/use and point to the source episteme edition. Preserve E.17's no-content-extension rule: informative explanation may expose source meaning without adding boundary commitments. Only when the selected episteme's U.View membership is asserted or needed, resolve its viewpoint and E.17.0 conformance; add an A.6.3 source-to-receiving construction only when that separate relation is current. The publication occurrence, carrier, viewpoint use, conformance claim, and any publication Work remain separate. When E.17's CC-MVPK-3b boundary claim-set condition applies, keep normative face text traceable to that A.6.B claim set, with informative commentary; a face does not become a second boundary specification. No MVPK package is required merely because a signature changed.
Classify atomic boundary claims under A.6.B: law content; entry or continuation conditions for a named action or application; generic prescriptions, individual commitments or grants; and observed, measured or evaluated results retain their distinct meanings. Evidence use and actual Work need their own basis. Correct classification needs no register by itself. Use the applicable claim register when stable identifiers serve reuse, a decision, audit or cross-face citation, retaining a claim ID or canonical source location for a material dependency. Keep a TargetSignature focused on its declaration content; ordinary claims and their direct patterns suffice when no register is needed.
Signature-construction relation in a transformation-flow structure (informative)
If a team represents actual signature-construction Work as an E.18 TransformationFlowStructure, reference only the A.6.S objects and direct relations that the flow uses; do not convert them into a second graph ontology:
- Declared constructor arrows may appear at transformation-flow loci as independently defined A.6.2 values over signature epistemes. An actual operation application and any performed Work remain separately identified.
- Concrete carrier writes (commits, releases, registry writes, and carrier and source-currentness pinning) may be admitted as Work under §4.0; an E.18 Work locus may bind that already admitted Work. Use F.6 afterward only when the receiving flow account consumes precise attribution through the performer's obtaining A.13 assignment; missing or failed attribution alone leaves the carrier-write Work intact. Use A.10 for evidence and provenance, E.17 for publication, and the relevant carrier patterns for carriers. The constructor-operation declaration, any identified application that writes a carrier, and the admitted Work remain distinct.
- For validation and admission, E.18 governs any selected gate/check position; each check follows its own subject rule. When an actual gate decision is present, use A.21 and name its exact
GateDecisionResult, bounded action, applicableGateProfileapplication, complete requiredGateCheckApplicationResultset, decision value, consequence, scope/window, and recheck condition. Use a shortGateCheckRefonly when a selected publication structure needs one, and aDecisionLogonly when audit or reuse is current. - When the source and receiving
EntityOfConcernRefvalues resolve to different EntitiesOfConcern, use A.6.4: identify the arrowr. Add a separate bounded-use assertionqwhen a receiving use is claimed and a separate current-case judgement when that case is evaluated. Let E.18 place each only when that transformation-flow use is current. A kind change without that basis supplies no positive claim, and any actual operation application remains separate.
This mapping is optional. A one-off revision needs neither an E.18 flow nor a ConstructorSignature. When a flow is current, use E.18 for its structure and E.18.2 for any mathematical description of that selected structure, including a graph or path description. Use C.29 only for a declared mathematical-lens use. A.6.S identifies the TargetSignature and any independently justified ConstructorSignature and operation declarations.
State during construction (informative)
Use an existing edition or status distinction when it answers the construction question. A different state claim needs its own definition; a convenient label does not admit a kernel kind. In most cases, use:
- edition + explicit continuity/withdrawal links for semantic evolution, and
- a coarse status (
Draft/Review/Stable/Deprecated) for process signalling.
If a project needs a reusable state-change policy, place it in the applicable signature's declared content or in a separately identified policy episteme, according to its EntityOfConcern and use. A one-off status change is stated directly. Where state-change policy is normative, express it as a status or state-transition policy for the relevant signature episteme or publication under its effective scheme and ClaimScope, with A.2.4 and F.10 status-use discipline and A.6.5 slot discipline where needed. Do not call the episteme's status a system role or create a system-role assignment for it; use E.10.ROLE to route bare role wording to the status, state, declaration position, or other direct branch.
Worked cases
Ordinary cheap stop. An editor adds the law Refund does not increase net balance to PaymentBoundarySignature and issues edition 4. The changed ClaimGraph identifies a new signature episteme; the edition or continuity relation and the editor's Work are stated only when the receiving claim uses them. If nobody needs reusable constructor vocabulary, stop. No ConstructorSignature or pair object is created.
Repeated engineering of a service boundary
Working situation. Several client teams and two authoring Systems will revise and republish the same payments boundary over multiple editions. They need one reusable account of the allowed authoring operations.
TargetSignature: PaymentBoundarySignature declares operations such as Authorize, Charge, and Refund; the participant meanings and ref modes reused in any relation declaration; laws such as idempotent charging; and the external-API applicability boundary. Keep operation arguments and results under A.6.1; A.6.5 governs participant positions only in a RelationSignature.
ConstructorSignature: PaymentSignatureEngineering is justified because the named authoring and review uses reuse the same operation vocabulary and laws. It may declare:
- a by-value law revision and a reference-retargeting operation when those distinctions are reused; apply A.6.5 only if the move concerns a SlotSpec in a RelationSignature, keeping ordinary law-content revision under its declaration rule and operation arguments/results under A.6.1;
- a direct calibration, provenance, or other relation assertion under its own pattern, with an A.6.6 declaration-change label only when a receiver tracks its represented history; and
- an E.17 publication operation for the repeated Plain, Tech, and interoperability publications, with a reusable view-producing operation only when needed and any A.6.3 construction identified separately.
PaymentSignatureEngineeringPipeline, if admitted as a System, may apply the described operations. Any claimed dated authoring or publication Work requires its complete A.13 performer core and independent A.15.1 admission as in §4.0. The ConstructorSignature does not act. Add the separate F.6 Work-assignment relation only for precise attribution through that same obtaining assignment; state an application binding, carrier, evidence relation, or additional classification or assignment only when its own claim is current.
The sentence Charges are recorded in Ledger L for the external API must first name and test its direct relation. Do not replace it with declareBase, a generic baseRelation, or a witness package. If later comparison needs a stable representation of that assertion and its scope, A.6.6 may add the optional declaration history.
The publication faces are faithful forms over the TargetSignature edition for their bounded readers and uses. Any claim that the selected episteme is a U.View requires its own E.17.0 conformance under §4.4. Guarantees idempotency is unpacked into the law, any separate mechanism admission condition, deontic commitment, and evidence-use claim; the word contract creates none of them.
Repeated engineering of a model-correspondence signature
Working situation. A research group maintains a correspondence signature across several model editions and publishes mathematical and engineering views. A second group must reproduce the same revisions.
ModelCorrespondenceSignature is the TargetSignature. Its vocabulary, laws, and applicability state the correspondence claim and the schemes in which it is interpreted. Cite an F.9 Bridge only when its direct predicate obtains between the F.17 local senses. State a separate bounded-use claim when a receiving use of that Bridge is claimed.
CorrespondenceSignatureEngineering is an optional ConstructorSignature because the second group reuses its declared revision and view-production vocabulary. A reference-retargeting operation may identify a new model edition. An A.6.2 arrow may compare source and receiving signature epistemes and any named neighboring facts; it changes none of those facts. The actual application, authoring System, Work, resulting episteme, and publications remain separate.
If the project only changes one reference dataset window once, state that direct revision and any needed Work or successor edition, then stop. Do not create the ConstructorSignature merely to host retime.
Bias-Annotation
Scope: signature-engineering uses that meet the entry condition; ordinary one-off revisions remain outside the two-signature branch.
-
Architecture bias (Arch): a reusable ConstructorSignature can improve repeated work but can also turn one edit into a framework. Mitigation: require a named receiver for the reusable vocabulary and laws; otherwise use the direct move and stop.
-
Onto/Epist bias (Onto/Epist): treating “editing the signature” as harmless can hide semantic change. Mitigation: distinguish a direct edit or new same-EntityOfConcern edition from an A.6.4 retargeting. A changed C.2.1 discriminator identifies another episteme; A.6.4 opens only when the EntityOfConcern changes.
-
Pragmatic bias (Prag): repeatable operation declarations cost authoring effort. Mitigation: introduce them only when a named receiver would otherwise reconstruct the same vocabulary or law.
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
Benefits. One-off work remains readable and cheap. Repeated engineering can still reuse a stable ConstructorSignature. Edition, view, arrow, application, Work, assignment, evidence, and carrier claims remain independently repairable.
Costs. A project must decide whether reusable constructor content is needed by a named receiving use instead of opening a standard package automatically. When it is needed, maintaining another signature costs attention. The mitigation is the named-receiver test and a declaration containing only the vocabulary and laws that receiver reuses.
Adoption test (informative). Ask three questions in order: What signature claim or change is current? Does that direct account answer the use? Which named receiver, if any, needs reusable constructor vocabulary and laws? A valid adoption result may contain one TargetSignature and one ordinary revision sentence, with no ConstructorSignature.
Rationale
Stable boundaries sometimes benefit from a reusable description of how they are revised. That is the useful two-signature technique: one U.Signature is the current target declaration, and another U.Signature declares constructor operations for a named reuse. It is not a universal architecture for editing and does not require a third pair object.
A.6.5, A.6.6, A.6.2-A.6.4, and E.17 supply distinct optional moves. Treating all of them as mandatory constructor primitives would recreate the ambiguity and overhead those patterns are meant to remove. The direct move comes first; the reusable ConstructorSignature packages only the operation language that has a receiver.
The result keeps viewing, declaration edits, episteme succession, reference retargeting, EntityOfConcern retargeting, application and Work distinct. A.6.B separately recovers the law, admissibility, deontic or observation claim hidden by contract wording.
SoTA-Echoing
-
Adopt: algebraic effects and effect systems separate operation signatures from handler semantics. The cited effect-system work describes operation signatures independently of how effects are handled (Leijen 2017; Hillerström & Lindley 2018). A.6.S adopts that separation: a TargetSignature declares the boundary, while operation application, construction Work and operational enforcement retain their own identities and rules.
-
Adapt: categorical optics treat “focus” and “round‑trip laws” as a disciplined interface for bidirectional structure. Categorical optics make preservation and round-trip laws explicit for bidirectional structure (Pickering, Gibbons & Wu 2017). A.6.S adapts the practice of stating the laws a constructor use needs. An A.6.3 viewing or A.6.4 retargeting still follows its own rule; this analogy alone establishes neither an optic nor a round-trip law for a particular constructor.
-
Adapt: architecture-description practice relates views to viewpoints and stakeholder concerns. ISO/IEC/IEEE 42010:2022 contributes that discipline. FPF's local adaptation identifies the
U.Viewpointepisteme and tests the selected episteme'sU.Viewmembership through E.17.0 conformance; a publication face remains the separate form over its source for a bounded reader/use, with membership and A.6.3 construction conditional under §4.4. Any separateresponsibilityorview-accountabilityclaim needs its participants and governing predicate. A ConstructorSignature is added only when a named receiver reuses the view-producing operation declaration; it is not required to explain how every view was produced. -
Adopt in spirit: behavioural protocol disciplines treat boundaries as typed interaction protocols with safety commitments. Session and behavioural type practice treats boundaries as protocols with progress and safety properties, which matches the A.6 split between signature laws and mechanism entry gates. A.6.S does not import tooling or typechecking, but it adopts the practice of making boundary interactions explicit and law‑governed (the MPST sources discussed in A.6.1).
Relations
-
Depends on:
- A.3.1/A.3.2/A.15/A.15.1/A.15.2 — Method, MethodDescription, WorkPlan, Work, and work-result separation
- A.7 — Strict Distinction (object ≠ description ≠ carrier; Face ≠ Surface)
- A.6 — Signature Stack: Classify and Place Boundary Claims
- A.6.0 —
U.Signature - A.6.2 — effect-free episteme-arrow discipline, only when a constructor operation uses a mathematical arrow; endpoint facts are read or compared, not changed by the arrow
- A.1, A.13, and A.15.1 — System admission, the complete actual-performer core including local-kind classification and an obtaining A.2.1 assignment, and independent dated-Work admission; F.6 follows only for precise attribution through that same assignment
- C.2.1 — episteme identity through claim content, EntityOfConcern, and effective ReferenceScheme, with empirical grounding and edition continuity kept as separate direct relations
- (optional) E.18 — TransformationFlowStructure, when signature-construction work is represented as a transformation-flow structure
- E.10 and LEX discipline — if the publication uses Plain twins (“the signature being engineered”) or shorthands, keep their exact Tech readings recoverable and keep Plain twins out of normative register
- A.6.3 — Episteme viewing — EntityOfConcern-preserving episteme construction
- A.6.4 — EntityOfConcern-retargeting arrows, their separate C.2.1 bounded-use assertions, and separate current-case judgements
- A.6.5 — relation-declaration slot discipline
- A.6.6 — Base Declaration Discipline
- A.6.B — Boundary Norm Square & Claim Register discipline
- E.17 and E.17.0 — MVPK and multi‑view describing
-
Coordinates with: A.6.5 for a compatible RelationSignature SlotSpec and its designation operations, and A.6.6 for direct base-dependence assertions and optional declaration history. Neither vocabulary is mandatory.
-
Constrains: a signature-engineering use only where the relevant meaning change, edition, reference retargeting, view, application, or Work claim is current; one distinction does not make the others mandatory.
A.6.S:End
Wholeness Language Unpacking — RPR-WHOLE
Type: Relational-precision specialization Status: Stable Normativity: Normative unless marked informative
At a glance. Use A.6.H when words such as whole, part, integrity, complete, turnkey, or end-to-end hide the object or relation on which a decision depends.
Use this when. Enter after A.6.P:4.11 has recovered the candidate objects and the sentence needed by the receiving use, and that sentence asks about a whole, part, structure, integrity, coverage, or completion. A.6.H helps the practitioner expose the candidate whole or other bearer, its boundary when relevant, the independently identified parts or constituents, and the direct claim together with the rule that defines, constrains, or tests it.
Not this pattern when. Do not enter merely because a source contains a trigger word. Use A.17 or the applicable subject rule for a Characteristic or constraint, C.16 for a measurement, and C.16.P while characteristic or scale wording remains unresolved. Evidence-use and assurance questions follow §6. Use C.2.1 for episteme identity or edition, E.17/E.24.PUB for publication, and the applicable A.3/A.15 rule for Method, WorkPlan, or Work. Keep using A.6.P when the candidate objects or the receiving sentence are still unknown.
What goes wrong if missed. A situation record, diagram, bundle, adjective, phase label, or coverage slogan becomes the supposed whole or relation. Parts, members, portions, phases, method factors, Work parts, evidence, and measured characteristics are then silently treated as one generic “part of” claim.
What this buys. A short identity-first repair from overloaded prose to one or more direct claims with participants and, when needed, PatternID locators for their definitions or tests—or to an explicit blocker when a needed predicate is absent.
What changes in practice. The practitioner writes the few direct sentences the next decision consumes: which entity, which relation and participants, and which rule defines or tests the claim. Add a blocked-inference guard only when its rejected reading has an independent local ground, is plausible for the intended reader, and changes truth, understanding or use; use the smallest clear correction under F.19.
Problem frame
Natural language compresses several different engineering questions into the same small vocabulary:
- What individual is being treated as one whole?
- Where is its boundary, and what lies outside it?
- Which independently identified objects are parts, constituents, members, portions, or proper temporal restrictions?
- Which relations among those objects obtain?
- Does a named use need a construction trace or a selected structure?
- Is the same whole being recognized again, or must it be reidentified?
- Is “complete” about performed Work, capability, specification, evidence, or another coverage claim?
- Is “integrity” a measured characteristic, an assurance claim, or a claim that an assembled entity remains one whole?
Those questions have different participants, predicates, and subject patterns. A.6.H keeps the source wording readable while making the load-bearing claims exact.
A word is load-bearing here when a requirement, invariant, interface statement, architecture choice, model relation, decision, test oracle, assurance use, or downstream action depends on its interpretation. E.10 is the pattern for shared wording-use discovery. A.6.H begins only after the current wholeness-family claim has been selected by value.
Problem
Without identifying the objects, the following failures recur:
- Candidate-whole ambiguity. “The whole system” is asserted before one candidate entity, boundary, or identity rule is recoverable.
- Reference-level drift. One noun phrase alternates among a referent, a claim-bearing episteme, a publication form or carrier, intended Work, performed Work, and evidence.
- Parthood overload. Physical components, conceptual constituents, collection members, measured portions, and temporal restrictions are written as one generic inclusion.
- Order-as-structure. A method factor, step description, plan item, or performed occurrence is treated as a component because a diagram places it inside a box.
- History-as-parthood. A
v2, revision, edition, shift, retry, or monitoring window is routed throughPhaseOfbefore episteme identity or Work-temporal law is applied. - Construction-by-list. A list of objects, repeated trace, or selected diagram is treated as proof that one whole or direct relation obtains.
- Coverage-as-wholeness. “Complete”, “turnkey”, or “end-to-end” is treated as a whole-level property without a scope, covered items, direct coverage or completion predicate, or current Work state.
- Integrity collapse. A measured characteristic, security or data-integrity term, evidence report, assurance claim, and structural-whole claim are all forced through mereology.
- Change-by-vocabulary. Generic verbs such as recompose, rephase, or recomplete replace the changed object and direct changed relation.
The practical failure is non-decidability: another reader cannot tell which object is at issue, what relation is claimed, what evidence would bear on it, or which stronger use is blocked.
Forces
Solution
Entry and result contract
Enter with:
- one sentence or decision that depends on wholeness-family wording;
- the candidate objects recovered under A.6.P:4.11;
- the receiving use that would change if the wording were read differently; and
- any already known definition, constraint, or test and its PatternID locator when that reference must travel.
Return one of:
- one or more readable direct claims, each naming the predicate or claim family, ordered participants, material qualification, and the PatternID locator when its defining or testing content must be cited;
- one next action for a still-current measurement, evidence-use, episteme, publication, Method, plan, Work, production, or completion question: apply the named rule when its entry holds, or stop when no such question remains; or
- an A.6.RCD
missing-governor[...]result naming the participants, proposed predicate, affected use, and absent definition, applicability, or occurrence-identity rule. Name a future pattern or declaration need only when one is identifiable.
When evidence cannot yet select among several readings, keep the candidate objects, discriminating questions, and affected receiving use explicit in ordinary prose. Under an already known rule, missing case facts leave the claim unknown; contrary facts can support a negative result. Neither is a missing-governor result. An ordinary shared note may hold the alternatives, keeping each separately recoverable. Its contents may supply claims or grounds, but its presence alone establishes no whole, relation occurrence, identity, coverage, assurance result, or new kind.
Recover objects and relations
Use the following sequence only as far as the current sentence requires:
- Recover the working question. State what a reader must decide, do, accept, measure, rely on, start, continue, or stop. The cue word selects no branch.
- Name the subject and reference level. Distinguish the referent entity, claim-bearing episteme, publication occurrence, publication form, presentation carrier, Method, MethodDescription, WorkPlan, performed Work, and evidence carrier. Keep only the subjects current in this case.
- Recover a candidate whole only for a whole claim. Identify the candidate individual, its direct identity pattern, relevant boundary or delimitation, environment, and at least one interaction, dependency, or constraint across that boundary when the use needs it.
- Identify the alleged parts independently. A label, location, list, graph node, file section, timestamp, or common name does not by itself establish the claimed parthood. Recover each component, constituent, entity said to belong to a collection, portion, temporal restriction, Method factor, Work part, or other object using the rule that defines or tests that claim.
- State each needed direct relation claim separately. Name its participants and test the predicate under the asserted polarity, modality or conditions. Identify an occurrence only when the receiving use needs that identity. Recognition of the whole or the mere presence of a trace, view or record does not establish the relation; relevant content can supply facts to test under its rule.
- Add construction or selected structure only when the receiving use consumes it.
C.13may report already recovered parts, relations, constraints, and a construction rule.A.22may identify one selected structure when its selection basis and identity discriminators are current. Their presence alone establishes no direct part or relation; apply the relevant rule to the claims and grounds they supply. - Recognize or reidentify the whole only when that question is current. Use
A.1for holon recognition andB.2for a remaining whole-reidentification question after direct existing-whole explanations have been tested. A changed adjective or part list alone decides neither. - Separate coverage, completion, and performed Work. Name what is covered, under which scope and criterion, by which relation, and whether the claim concerns a MethodDescription, capability, plan, Work occurrence, production result, evidence set, or another subject. Apply the rule for that subject. For a deliberately asserted dated Work, recover A.13's performer basis and independently admit the occurrence under A.15.1; use F.6 afterward only for attribution through the same assignment. A.15.PROD governs its production claim when applicable. Ordinary practitioner action needs no invented Work identity.
- Stop after unpacking. State each recovered whole, relation, characteristic, Work, evidence use, or verdict directly. Apply another named rule only when one question remains and its entry holds; otherwise stop with the completed claims or blocker.
Classify integrity by the claim it carries
The word integrity never chooses mereology by itself.
If the source leaves these readings open, preserve the alternatives and block the named use until evidence discriminates them.
Select the direct relation, not a generic part edge
Unpack complete, turnkey, and end-to-end
Ask what the claim of completeness allows the next reader to do.
A sentence may require several rows. Write several direct claims; an ordinary note may hold them when each remains separately recoverable.
Use wording as a cue, not as ontology
The following recurring expressions are useful review cues:
- whole, entire, integrated, coherent, holistic — ask whether there is a candidate whole, a measurement or assurance claim, or only rhetoric;
- part, piece, component, module, element, subsystem, includes, contains, comprises — recover the object and direct relation rather than accepting the noun;
- phase, version, revision, edition, lifecycle — apply the direct identity pattern before any history label;
- complete, turnkey, end-to-end, fully specified — recover the coverage or completion claim;
- pipeline, workflow, process, step, stage — distinguish Method, MethodDescription, WorkPlan, performed Work, order relation, and publication representation;
- collection, group, team, set — distinguish who or what belongs under the collection's own rule, an acting system, system-role assignments, and a selected collection structure;
- context, environment, discipline as a whole — name the bounded context, episteme family, community, organization, or other subject before making a boundary or nesting claim.
When a cue occurs inside a defined term of art, retain the definition and its PatternID locator when needed. Open A.6.H only if the sentence also makes an unresolved whole, part, structure, coverage, or completion claim.
Describe change through the object that changed
When a wholeness-looking story changes, name the object and direct relation:
- for a different boundary or interaction claim, state the changed object and apply the applicable boundary or delimitation rule;
- for an added, removed, or differently related item, test the parthood, collection's own belongs-to, portion, or selected-structure claim;
- for changed episteme content, EntityOfConcern, or effective ReferenceScheme, compare C.2.1 identity and test edition continuity separately;
- for a different publication form, occurrence, or carrier, state that publication or carrier claim and apply its rule;
- for a changed Method, MethodDescription, WorkPlan, Work history, production result, or completion claim, state that object and apply its rule;
- for a changed coverage scope, criterion, evidence set, or assurance use, repair that direct claim rather than inventing a generic completeness status.
Do not substitute a generic change lexicon for those objects and predicates. A readable verb is welcome when the direct claim remains recoverable.
Archetypal Grounding
Assembled pump
Source sentence: “After seal replacement, the assembled pump remains an integral whole.”
- The subject is
PumpUnit-37, not the maintenance record, drawing, or seal-replacement Work. - The pump's direct identity rule decides whether the same individual continued.
- The current use names the pump boundary, impeller, casing, replacement seal, and the assembly or parthood relations on which operation depends.
- If the decision consumes one selected organization of those relations, A.22 governs that structure; if it consumes a construction account, C.13 reports already recovered facts.
- A.1 recognizes the candidate whole; B.2 opens only if the replacement leaves a whole-reidentification question.
- For a calibration, seal-replacement or inspection Work claim, use the basis in §4.2. State any claimed change separately under the rule for the changed object.
Laboratory pipeline
Source sentence: “The whole chromatography pipeline is turnkey, and the chemist owns the whole thing.”
The repair separates the following claims and unresolved questions; turnkey and owns still need the receiving decision and discriminating facts:
- the reusable procedure is one Method or composite Method under A.3.1/B.1.5, with joins and exposed interactions;
- identify its procedure document as a separate episteme under C.2.1. It is a
U.MethodDescriptionunder A.3.2 only if its EntityOfConcern is an admitted Method and it makes a substantive claim about that Method as a way of doing; - “turnkey” becomes the specification, capability, Work, or evidence coverage claim needed by the receiving use;
- treat owns as a local wording cue. First state the decision that depends on it and the proposed sentence. Candidate readings include, for example, property or title, possession or custody, operational control, decision authority, stewardship or responsibility, assignment, commitment, and permission; they have different participants and predicates. Apply the direct rule when one exists, or return A.6.RCD
missing-governor[...]naming the participants, proposed predicate, affected use, and absent definition; and - identify any asserted dated laboratory run as Work using §4.2.
Thus “the laboratory owns the instrument,” “the chemist has custody during the run,” “the chemist may authorize disposal,” and “the chemist is responsible for calibration” are four different claims. None follows from belonging to the team, classification, assignment, commitment, or permission merely by form.
No one claim is a component relation merely because the source uses pipeline or whole.
Paper, proof, and revision
Source sentence: “Section 3 is part of the proof, and v2 is part of v1.”
- Recover whether Section 3 is a constituent of the paper episteme, a publication-unit constituent, or a described proof step. Keep those subjects separate.
- Recover argument order under its subject pattern rather than as physical containment.
- Compare the C.2.1 triples for the two labelled epistemes. Changed claim content identifies two epistemes. Assert
EpistemeEditionRelation(E_v1,E_v2)only when its historical-continuation predicate obtains. - If the subject rule and A.14 admit a proper temporal restriction of one unchanged episteme,
PhaseOf(E@τ,E)may state that restriction. Needing or using the episteme only during an interval states a use or applicability condition; it does not by itself identify a temporal part. Neither claim connects v1 to v2. - Keep any drafting, review, or publication Work separate from publication occurrences and from the two epistemes that participate in
EpistemeEditionRelation.
Integrity measurement and assurance
Source sentence: “The structural integrity score is 0.82, so the system is assured.”
Recover the bearer, integrity Characteristic, Scale, measurement method, result episteme, evidence, and time stance under C.16; use C.16.P if the characteristic or scale construction remains unclear. For “the system is assured”, name the target claim and assurance use before applying B.3; then recover the evidence-use relation, scope, limitations, and relying context. The score alone does not establish that assurance result.
Recognition and assurance stay separate
Recognition questions decide which objects and direct relations are current:
- Is there one candidate whole under A.1?
- Which independently identified parts, constituents, members, portions, or temporal restrictions participate?
- Which direct relations obtain?
- Does a selected structure or construction account matter to this use?
- Does the same whole persist, or is reidentification current?
Evidence-use questions ask how the evidence bears on the claim for the stated use. Apply the rule for the target claim, with A.2.4 for evidence-use classification. Use A.10 when provenance, currentness, or reliance requires a replayable source-to-use account, including carrier identity when material:
- Which claim is being examined?
- Which evidence bears on it through which relation?
- What scope, limitation, time stance, and relying use apply?
- What judgement about recognition, relation truth, measurement, completion, or another claim does the evidence warrant?
Apply B.3 only when a named assurance claim and assurance use are current. Evidence can make an assertion inspectable without becoming constitutive of the whole or relation.
Bias-Annotation
- Governance bias. The pattern favors reviewable direct claims over rhetorically satisfying wholeness language. Ordinary prose and explicit unresolved alternatives mitigate this when a decision is not yet due.
- Architecture bias. Use the applicable patterns and small typed vocabularies instead of one reusable wholeness schema. The minimum-current-object rule mitigates unnecessary apparatus.
- Ontological/epistemic bias. It insists on separating referent, episteme, publication, Method, plan, Work, and evidence. This cost is paid only when the distinction changes the receiving use.
- Pragmatic bias. It favors early disambiguation to avoid downstream refactoring. A local direct sentence is sufficient; reusable declarations or structures are added only for a named later use.
- Didactic bias. It uses recurring cue words and worked cases to teach the route;
F.19governs the connected language-and-precision reading, withE.10cues and direct wording rules where needed.
Conformance Checklist
Common Anti-Patterns and How to Avoid Them
Consequences
The practical test: if “whole” matters, name the thing, the relation, and what the reader may do with the claim.
Rationale
Wholeness language is useful because it compresses boundary, identity, relation, construction, coverage, and assurance into ordinary speech. The same compression becomes dangerous only when downstream work relies on one particular reading.
The minimal repair starts with the working decision, recovers only the objects that decision consumes, and applies another rule only for a still-current question. This preserves conversational economy while preventing a representation, record, label, or adjective from replacing an in-world object or relation.
The sequence also preserves two positive uses. PhaseOf can state a proper restriction of one unchanged enduring individual, including an unchanged episteme, when A.14 and the subject's direct rule admit it; fixed episteme identity alone does not establish the restriction. Ordinary whole recognition remains useful when a candidate entity, boundary, parts, relations, and direct identity rule are current.
SoTA-Echoing
Whenever fraction, percentage, or share is used as a part claim, recover the extensive measure μ and additivity basis before PortionOf; otherwise keep the value with the pattern that defines its measurement, allocation, collection belonging, or other claim.
Relations
- Specialises:
A.6.Pafter its 4.11 whole/part/integrity/coverage branch has recovered candidate objects and the receiving sentence. - Uses for direct mereology:
A.14; construction accounts toC.13; selected structures toA.22; holon recognition toA.1; and remaining whole reidentification toB.2. - Uses for episteme and publication questions:
C.2.1,A.3.2,E.17,E.24.PUB, andC.29as selected by the subject. - Uses for Method, plan, and Work questions:
A.3.1,B.1.5,A.15.2, the A.13/A.15.1/conditional F.6 basis in §4.2,A.15.PROD, andB.1.4only for bounded aggregation of already recovered temporal or order relations. - Uses for integrity, evidence, and assurance questions:
A.17or the applicable subject rule for a Characteristic or constraint;C.16for measurement, withC.16.Pfor unresolved characteristic or scale wording;A.2.4for evidence-use classification,A.10for a needed replayable source-to-use account, andB.3for an assurance claim. - Uses for absent relation governance:
A.6.RCDafter the participants, required predicate, and blocked receiving use have been identified. - Does not establish from wording or record form alone: a whole, lifecycle or other new kind, automatic edition series, universal part relation, coverage status, assurance verdict, or direct relation occurrence.
A.6.H:End
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)