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

Source changed 2026-11-22 12:18:55 UTC · snapshot created 2026-11-22 12:19:56 UTC · last check 2026-11-22 12:30:20 UTC

Cluster A.V - Constitutional Principles of the Kernel

A.7 - Distinction: Repair Conflations of FPF Objects (Clarity Lattice)

Status: Stable

A.7:0 - Use this when

Use this pattern when one sentence, diagram, card, identifier, file, plan, or run is being read as several nearby FPF objects and the team needs to recover the relation position before checking the recovered claim under its subject predicate. A frequent case is deciding whether the live object is a Method, an episteme that qualifies as MethodDescription, a system Capability, a WorkPlan, or dated Work.

What goes wrong if missed. A label such as algorithm, SOP, recipe, or script is treated as membership evidence; a direct Method reference is forced through a document; or a description, plan, capability and occurrence inherit one another’s force.

What this buys. A practitioner can identify the current object, make the smallest direct claim, and stop without manufacturing a description, execution, evidence, gate, or authority relation.

Primary working object. The sentence or publication position whose nearby objects have been conflated. A.7 restores the distinctions; A.3.1 is the pattern for the Method, C.2.1 is the pattern for episteme identity, A.3.2 is the pattern for same-individual U.MethodDescription membership, A.15 is the pattern for plan and Work, and naming/reference patterns contain the defining content for designation and resolution.

First useful move. Name the object the receiving use needs. For a suspected MethodDescription, first identify one admitted U.Episteme, then require one admitted U.Method as its EntityOfConcern and at least one substantive claim about that Method as a way of doing. For a direct Method use, resolve the identifier or receiving methodRef under its effective reference scheme; do not invent a MethodDescription.

Not this pattern when. If the current object and direct relation are already clear, use the applicable pattern immediately. A.7 supplies no decision about Method identity, episteme identity, MethodDescription membership, capability adequacy, work readiness, occurrence, evidence, publication, or gate passage; handle each such claim under its applicable pattern.

A.7:1 - Intent

Use the following distinctions to recognize and correct category errors. The pattern develops four recurrent confusion families:

  1. System-role kind vs function-like wording (classification versus the actual functional, behavioural or other claim),
  2. MethodDescription vs Method vs Capability vs Work (description vs abstract way-of-doing vs system ability/envelope vs performed occurrence),
  3. Holon vs System vs Episteme (what can act and what cannot),
  4. EntityOfConcern vs Description episteme, View, and Publication (the item under concern vs epistemes and publication relation positions that make it available; specification is a use of a Description episteme subject to C.2.1:6, not a third peer member of this distinction).

It harmonizes A.2 and A.2.1 for system-role kinds and system-role-assignment relations, A.3.4 for transformation, A.10 for evidence-provenance and carrier and source-currentness relations, A.14 for advanced mereology, A.15 for System-Role-Method-Work alignment, C.2.1 for episteme constitution and its separate empirical-grounding and edition relations, E.17 for publication and view discipline, and F.9, F.17, and F.18 for bridge and naming discipline.

A.7:2 - Problem frame

  • Holons (A.1) and systems. All holons are part-whole units; a System can act because its organization satisfies A.1. Add a local system-role-kind classification or assignment only when the receiving claim uses that stronger distinction.
  • Transformation (A.3.4), Work, and optional attribution. A claimed change names the affected entity and the direct transformation facts used by the claim. For a precise dated Work claim, first recover each actual performer System and its A.13 core: local agential kind and criterion, classification, obtaining assignment, scope, working situation, window, and supporting evidence. Then admit the occurrence independently under A.15.1 from its performance history, at least one Method actually followed, temporal extent, and at least one obtaining local containing-System relation. A short Work reference may leave these facts implicit only when they remain recoverable. If the current claim must also identify the assignment under which the Work was performed, name the same obtaining assignment and check that attribution separately through F.6. F.6 identifies neither performer nor assignment. A failed F.6 check alone leaves independently admitted Work intact; recheck an admission premise only when the same finding questions it.
  • Method and Work backbone (A.3.1, A.3.2, A.15). Keep MethodDescription, Method, Capability, WorkPlan, and Work distinct. Name only the values used by the current claim. A System acts; a local kind, assignment, Method, or episteme does not.
  • Evidence (A.2.4, A.10). Identify the episteme and the claim for which it is used as evidence. Add provenance, carrier, source-currentness, and reliance relations when the use requires them. Systems inspect or revise epistemes, publish or store their representations on carriers, and rely on their claims; those epistemes do not perform these actions.

Practitioner check: recover the intended referent and action in sentences such as “the document decided” or “the process executed itself”. Correct a literal or metonymic claim that assigns the action to a participant unable to perform it. Keep established shorthand when the capable System and its action are recoverable.

Boundary for use from other patterns: A.7 restores the EntityOfConcern, the admissible describing relation, and the publication boundary; then use the defining or testing rule for the remaining claim, with its PatternID kept only as a locator. Do not let A.7 turn an architecture, structure, work, method, evidence, characterization, or decision question into a general discussion of descriptions. If the EntityOfConcern is itself a Description episteme or view, keep the pattern centered on that episteme as the item under concern; description-of-description or publication-force issues open only when they are the claim being made.

A.7:3 - Problem

When documents blur the above lines, three classes of defects appear:

  1. Category collapse. People write “function”, “role”, or “process” interchangeably; teams then disagree whether they are changing a MethodDescription, a Method, a Capability envelope, or reporting an actual Work occurrence.
  2. Agency misplacement. Epistemes (documents, models) are treated as doers; collectives as raw sets; or a “holon” is used where only a system makes sense.
  3. Audit failures. A MethodDescription alone is taken to establish that its Method was performed; a Work claim lacks its occurrence basis or time span; or a Description episteme, a Description episteme admitted for specification use, a View, publication face, publication unit, or carrier is treated as the EntityOfConcern, decision, permission, gate, work occurrence, or assurance result merely because of its label or publication position.

A.7:4 - Forces

ForceTension
Didactic brevity vs conceptual precisionTeams want short words (“process”, “function”) ↔ the framework must keep the four distinction families apart.
Universality vs domain idiomsWe admit engineering idioms (procedure, SOP, algorithm, workflow) ↔ internally we must map them unambiguously.
Parsimony vs completenessMinimal concept set ↔ enough distinctions to avoid the classic traps: system-role kind versus function; description, Method, Capability, and Work; and episteme versus carrier.

A.7:5 - Solution — The Clarity Lattice (normative distinctions & vocabulary)

A.7:5.1 - Terminology (normative): orthogonal characteristics

  • senseFamily — the categorical characteristic, used by F.7/F.8/F.9: {Role | Status | Measurement | Type‑structure | Method | Execution}. Rows must be sense‑uniform.
  • ReferencePlane — the referent mode per CHR: {world/external | conceptual | epistemic}.
  • EntityOfConcern and Description-episteme boundary — the item under concern is separated from Description epistemes (E.10.D2, C.2.1). Specification use requires an independently constituted Description episteme, checkable claims, and a named harness, validation, conformance, measurement, or evaluation relation capable of checking them for the stated use. When viewpoint selection affects reliance, preserve or explicitly update the named describing use and its selected viewpoint. Formality, acceptance conditions, a C.16 measurement criterion, and verification practice may contribute under their direct rules. Specification is not a third member of the distinction.
  • DesignRunTag — identifies design or run use; it does not select a ReferencePlane.
  • Publication face, form, unit, carrier, and rendering boundary — Description epistemes, including Description epistemes admitted for specification use, may be made available through publication units, publication forms, faces, renderings, and carriers. Their publication positions do not by themselves identify the EntityOfConcern, the Description episteme, or a specification use or model-refinement relation; readable form alone establishes no evidence, gate passage, work, assurance, or decision force. The ordinary didactic faces for architectural patterns in FPF are: {PlainView (explanatory prose), TechCard (typed cards and IDs), NormsCard (TechCard profile for checklists), AssuranceLane (evidence bindings)}. Publication faces and forms are orthogonal to the EntityOfConcern and Description-episteme boundary, to specification use and model refinement, and to DesignRunTag.
  • Direct Description account and specification-use boundary — a Description episteme is independently identified under C.2.1 by its complete claim content, EntityOfConcern, and effective ReferenceScheme. A.7 introduces no universal EntityOfConcern-to-Description constructor or morphism. When it matters how the claims were produced, selected, carried, or revised, state the authoring, measurement, observation, model, source-use, representation, refinement, or other direct relation that is current. A later specification-use claim must satisfy the preceding conjunction under E.10.D2 and the direct pattern that supplies the capable checking relation.

A.7 establishes the following distinction groups. Use their names and scope exactly as below.

A.7:5.2 - System-role kind vs function-like wording, functional behaviour, capability, method, and work

  • System-role kind. One local U.Kind with U.System candidates and an operative condition for a stable, assignable, work-facing contribution. Its member/non-member boundary and continuity rule complete the C.3 recovery. A practice or source reference locates defining content; the reference label alone identifies no kind. An obtaining assignment occurrence may relate a system to that kind only through a directly admitted U.SystemRoleAssignment species. The kind is not the behaviour. Example: the kind currently named CoolingCirculatorSystemRole, whose ThermalLoop-7 provenance locates one definition.
  • Function-like wording. A source phrase such as “function”, “behaviour”, “service”, or “does X” may name a required transformation or effect (A.3.4), functional behaviour (A.6.F), a capability envelope, a method, performed work, a quality, or a structure. Recover the governed claim before choosing the FPF term.
  • Under a system-role assignment. A System or acting holon that holds an assignment may have a Capability to enact a Method under conditions. A precise Work claim still uses A.13 to identify the actual performer and A.15.1 to admit the dated occurrence independently. Add F.6 only if the claim must also identify the assignment under which that Work was performed. The system-role kind, assignment, Method, Capability, transformation, and effect do not substitute for the Work or performer.

System identity and changing contributions. A U.System can keep its identity while its classifications and obtaining assignments change. A contribution named by a system-role kind may call for a Method, a Capability envelope to enact that Method under conditions, and possible Work occurrences; none follows from the kind alone.

Use system-role kind for that local U.Kind, an admitted direct species under U.SystemRoleAssignment for assignment occurrences, functional behaviour for a behaviour claim stated with A.6.F, Method for the abstract way-of-doing, Capability for a holder System’s bounded ability or envelope for a Work family or result class under stated conditions, Work for the performed occurrence, and Transformation or effect wording for an actual change identified with A.3.4. Do not call the kind or assignment itself a function, and do not define Method as Capability or as the transformation or effect itself.

A.7:5.3 - MethodDescription vs Method vs Capability vs Work (description vs way-of-doing vs ability envelope vs occurrence)

  • MethodDescription — one already identified claim-bearing U.Episteme whose C.2.1 EntityOfConcern is one admitted U.Method and whose claims, under its effective reference scheme, say something substantive about that Method as a way of doing. A transformation or enactment concern, generic participant meanings, applicability, precondition, intended effect or preserved condition, bound, or internal method composition can satisfy the positive threshold. The labels algorithm, SOP, recipe, script, procedure, code, diagram, or design-time artifact are cues only. Authoring, revision, citation, publication, approval, or use time establishes neither episteme identity nor U.MethodDescription membership. Its publication cites A.10 carrier/source-currentness refs when the carrier is used as evidence or source.
  • Method — the reusable way of doing under stated applicability, whose composition is governed by B.1.5. A Method is not an occurrence, description episteme, or system ability. Actual participation and operation values require their corresponding direct relations or A.6.1 bindings to obtain; a dated Work claim separately requires the basis in :2.
  • Capability — a named holder System’s bounded ability for a Work family or result class under stated conditions and attained bounds. Operating and resource conditions, including time when it changes the ability claim, qualify that proposition. Qualification windows and currentness conditions concern reliance on its support and are stated when the receiving use requires them. Name a Method or system-role assignment only when that condition or fit input is current. It is not the MethodDescription and not the performed Work.
  • Work — the dated run-time occurrence (what actually happened), with resource spend (Γ_work) and temporal coverage (Γ_time).

Designation, reference, and description are different. A Method identifier designates one U.Method under the applicable designation rules of an effective reference scheme. A receiving claim’s methodRef separately resolves under its effective scheme to that same Method. Neither operation needs a MethodDescription. Cite a separate methodDescriptionRef only when that receiving claim depends on claims in an episteme edition that has already passed A.3.2 membership.

Minimally viable reference and membership case. Under MaintenanceReferenceScheme-2026, identifier PumpSealInspectionMethod designates admitted Method M-PSI. MaintenancePlan-47 is a separately governed U.WorkPlan; its methodRef = PumpSealInspectionMethod resolves directly to M-PSI, without a description hop. Episteme PumpSealInspectionGuide-e3 is independently identified by C.2.1 from its claim content, EntityOfConcern = M-PSI, and effective scheme. Its claims state the inspection precondition, ordered clean–inspect–classify way of doing, rejection bound, and stop; the same episteme therefore passes A.3.2 membership as U.MethodDescription. If MaintenancePlan-47 relies on those e3 claims, a separate methodDescriptionRef = PumpSealInspectionGuide-e3 may be cited. The plan, Method, MethodDescription, Capability and any later Work remain different objects.

Recognizable near misses. A catalogue row containing only PumpSealInspectionMethod designates or mentions a Method but is not a MethodDescription. A file named PumpSealInspectionSOP-v3.pdf supplies neither the C.2.1 episteme identity nor the substantive method claim by filename. methodRef = PumpSealInspectionMethod does not imply that a description exists. A newly authored, revised, cited, approved, published, or used episteme does not gain membership unless its Method EntityOfConcern and substantive way-of-doing claim satisfy the same test.

A MethodDescription alone does not establish that its Method was performed. Its claims may support a named claim only through the applicable evidence-use relation; never present Method or Capability as if it had happened; never define Method as Capability; never infer MethodDescription membership from form, label, lifecycle time, or use. Resolve direct Method designation and receiving references without mandatory description indirection.

A.7:5.4 - Holon vs System vs Episteme (who can act)

  • System or acting holon. A System is physically embodied; its organization of constituents and interactions makes it eligible to act under A.1. An ordinary sentence may name the recognizable System by a contribution noun: The engineer designed the pump, The reviewer checked the manuscript, or The service accepted the request. Keep that wording when the System and contribution are recoverable and no receiving inference depends on a local system-role kind or assignment identity.
  • System-role kind and assignment, when current. Add a local system-role-kind classification and obtaining assignment when their identity, extent, or participants are used by the claim, including the A.13 core for precise Work admission. State the admitted assignment species when that relation is current. Precise attribution of an already admitted Work to that assignment remains a separate F.6 claim. The assignment and kind do not make the System able to act and do not act themselves.
  • Capability, Method, and Work, when current. Name Capability only for an ability or envelope claim, Method only for the way of doing, and Work only for a performed occurrence. An ordinary actor sentence need not materialize all three.
  • Episteme. An episteme cannot act. A System may author, revise, use, or publish it; state the operation, Work, carrier, publication, evidence, or source relation only when the receiving claim uses that distinction.
  • Holon. Use the umbrella word when it adequately identifies the subject. An entity claimed to act must satisfy A.1 as a System; name that distinction explicitly when the capable participant would otherwise be unclear. An assignment is not the System-admission test.

Progressive example. The design team selected valve V-12 is enough for an ordinary design account when the team is a recoverable collective System and no later inference needs a precise Work or assignment identity. If an audit claims dated ValveSelectionWork-47, use A.13 to recover DesignTeamSelectionSystem as the actual performer with its core basis, then A.15.1 to admit the Work independently from the occurrence facts in :2, including at least one Method actually followed. If the audit must also identify the assignment under which that Work was performed, use F.6 to check ValveSelectionAssignment-47 and compare its holder with the already identified performer. Keep the core’s admitted assignment species, assigned local kind, extent, and evidence recoverable; add another Method, Capability, or further evidence detail only to the degree used by the audit.

A.7:5.5 - Episteme vs publication carrier and source-currentness record

  • Episteme — one C.2.1 knowledge holon identified by its complete claim content, EntityOfConcern, and effective ReferenceScheme. Its content may include a claim, model, or requirement set.
  • Publication carrier — the physical or digital bearer of an episteme publication or stored representation (file, volume, dataset item).
  • Source-currentness record — a record of claims about source currentness for a stated use and conditions, distinct from the source episteme and the carrier bearing the record. Use the applicable A.10/G.11 relations when the receiving evidence, source, or reliance claim depends on them.
  • Use: Evidence use relates an episteme to the claim for which it is used (A.2.4). Arguments and validity concern its claims; provenance and reproducibility also need the source, production, carrier, or checking conditions on which the particular use depends. Apply A.10 and B.3 only for the provenance, reliance, or assurance claims made.

When “we updated the spec” matters to the receiving use, state whether its C.2.1 claim content, EntityOfConcern, or ReferenceScheme changed, a carrier changed, or a source-currentness claim was updated. Name the affected object and its direct relation; a carrier change alone does not establish a new episteme.

A.7:5.6 - Formal inclusion, world-side collection, and collective System

  • Mathematical or representation inclusion — say that an element is in a set, a value fills a tuple place, or a value lies in a coordinate domain under the applicable mathematical statement. Keep the statement with its defining mathematical rule; use C.29 for an actual mathematical-lens use and A.19 when a characteristic scale or coordinate is current. No world-side belongs-to relation follows.

  • World-side collection — identify the collection and use its subject-specific belongs-to rule. That rule says who or what may belong, when belonging begins and ends, whether it may recur, and how past belonging is stated. Belonging alone establishes neither parthood nor holonhood, but it does not prohibit a separately grounded constructive part relation.

  • Collective System — treat a team or other grouping as an acting System only after the candidate passes all six A.1 matters. A list, formal set, catalogue, or belongs-to statement does not establish that result.

  • Use the direct relation for every stronger claim:

    • ComponentOf — mechanical or structural part in systems.
    • ConstituentOf — logical or content part in epistemes.
    • PortionOf — quantitative portion with conserved extensives.
    • PhaseOf — a proper temporal restriction of the same unchanged enduring individual, admitted under A.14 and its direct identity rule; Work parts use A.15.1.
    • System-role assignment — a System is the HolderSystemSlot value in one obtaining occurrence of a directly admitted U.SystemRoleAssignment species.

Formal inclusion establishes no world-side belonging. Collection belonging establishes neither constructive parthood nor holonhood and does not make either impossible. If a grouping is claimed to act, test it against all six A.1 matters. Add a local system-role kind, assignment, Method, Work, or constructive part relation only when that separate claim obtains.

A.7:5.7 - Match composition to its subject

  • System aggregation and delimitation — use B.1.2:4 to coordinate the independently established parts, crossings and whole-characteristic claims needed by the engineering decision. Each characteristic keeps its own aggregation or inference rule.
  • Method composition — use B.1.5 to determine whether constituent Methods and their relations construct one reusable way of doing, including its order and branching.
  • Temporal aggregation — first establish Work occurrences and temporal parts under A.15.1, or the identities and temporal relations of other subjects under their own rules. B.1.4 combines those recovered relations for a stated window and use.
  • Work-resource aggregation — use B.1.6 for resource spend and yields tied to admitted Work, with the required measurements, accounting boundary and aggregation policy.

Select the rule for the composition claim. For domain “process” or “behaviour”, recover the object and predicate under its direct rule; it may concern a Method, Work, A.3.4 transformation, A.6.F functional behaviour, mechanism, or another domain object. Add an explicit distinction only when the intended value is not cheaply recoverable.

A.7:5.8 - EntityOfConcern and Description-episteme boundary vs publication face, form, unit, and carrier boundary (orthogonal, normative)

  • EntityOfConcern-to-description boundary. A.7 keeps the EntityOfConcern and an episteme that describes it distinct; E.10.D2 supplies the Description and specification-use repair. What the EntityOfConcern value is and how it is described are different questions. A Description is a U.Episteme about that entity under its effective scheme. A named describing use may separately select one viewpoint when the selection changes what is read or checked. Specification is a checkable use of the independently constituted Description episteme and requires checkable claims plus a named harness, validation, conformance, measurement, or evaluation relation capable of checking them for the stated use. Formality, acceptance, a C.16 measurement criterion, or verification practice may contribute to that test but does not substitute for it. When viewpoint selection affects reliance, preserve or explicitly update the named describing use and its selected viewpoint. EntityOfConcern, Description, selected viewpoint, and specification use remain distinct. If two epistemes serve as models, B.5.MR separately tests a refinement or abstraction claim.
  • Publication governs availability. Publication units, publication forms, faces, renderings, and carriers make Description epistemes available to readers or tools, including Description epistemes admitted for specification use. That availability relation alone identifies neither the EntityOfConcern nor the Description episteme and grants no specification use or evidence use. A description may independently concern one of these publication objects. Name A.10 carrier/source-currentness relations when the receiving evidence, source, or reliance use depends on them.
  • Publication-face field pins. A TechCard retains the source pins needed to interpret its claims. For a displayed numeric or comparable characteristic value, resolve the characteristic and its interpretation rule; the CHR-Pins fields are {UnitType, ScaleKind, ReferencePlane, EditionId}, with each supplied when it affects that interpretation. An E.17 publication profile is separately selected. A nonnumeric description requires no unit or scale merely from being shown as TechCard.
  • Semantic and plane boundary. A context or ReferencePlane difference alone establishes no F.9 Bridge, CL, or trust penalty. When two F.17 local senses and the direct F.9 predicate establish a Bridge, cite that relation. Add a separate bounded-use claim when a receiving use of the Bridge is proposed; CL remains optional evidence shorthand. A cross-plane use cites its applicable plane relation. Apply a trust penalty only when a named current policy applies to the use.

A.7:5.8a - Same or near-same EntityOfConcern across descriptions and views

Different descriptions, views, viewpoints, publication units, or role-method-interest positions may concern the same EntityOfConcern, different entities of concern, or an unresolved candidate set. A.7 does not accept sameness by publication title, view label, carrier continuity, shared ordinary name, or common reader interest.

Use this split when the text needs to say whether two descriptions or views are about the same thing:

CaseA.7 relation caseAdmissible move
same referent by valuethe localized EntityOfConcern or relation named by value, carried by the current claim, or selected by a reference case and the resolved entityOfConcernRef, where live, refer to the same item by declared reference disciplinesame-entity work inside the declared use
preserved by viewingA.6.3 viewing is an EntityOfConcern-preserving mathematical construction; its source and receiving endpoints may identify the same episteme or differ in claim content or effective ReferenceScheme. Any representation relation and any viewpoint selected for a named describing use remain separatesame-EntityOfConcern Description, Specification, or view transformation
publication-unit primary onlya bounded publication unit states what it is mainly about, plus its carried move and outside-work boundary, without establishing a claim-bearing episteme trace by itselfpublication-unit stability only
bridge-conditional semantic reuseAn F.9 Bridge obtains between two local senses, and a separate affirmative bounded-use claim names the proposed use, direction, correspondence rule, tolerated loss, and polarity. A practitioner may first use F.18 to settle the governed value’s designations and, only when a durable term row is needed, then use F.17 to constitute that row; neither step establishes the Bridge or licenses reuse, while publication, evidence, and any reliance judgement remain separate.bridge-scoped semantic reuse only; no entity-identity conclusion follows
retargeted under invariantA.6.4 identifies an arrow r between epistemes with different EntitiesOfConcern. A separate C.2.1 bounded-use assertion q about r states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. A separate current-case judgement compares facts with q’s conditions and proposition and returns satisfies, fails, or cannot decide; cannot decide names the missing fact and reopen condition.retargeted use only after an affirmative q for the named use receives a separate satisfies judgement; otherwise retain the result, including the missing fact and reopen condition for cannot decide
unresolved candidateconstruction/reference/bridge/witness trace is insufficientcandidate tracking, question framing, or non-use
different entitythe applicable identity or reference rule and the available facts establish that the two descriptions concern distinct entitieskeep the established difference; a missing sameness or reuse path alone leaves identity unresolved

When a sameness, difference, or reuse claim needs mathematical justification, use the defining mathematical rule; use C.29 only for an actual lens. E.18 and E.18.1 govern their transformation-flow and problem-to-work carry-through claims. Use E.18 for a gate crossing only when that crossing belongs to the selected transformation-flow structure. A structural, graph, flow, or architecture-description comparison uses its relevant architecture pattern. If no rule supplies the needed identity, correspondence, or postulate-theory justification, leave that claim unresolved.

A.7:5.8b - Compact relation-position recovery aid

When a visible representation could be read as several FPF objects, recover the position used by the claim: the EntityOfConcern, description or view, publication object, or a separate evidence, gate, Work, authority, source or mathematical-use relation. Apply the pattern for that position; §§5.5–5.9 distinguish the relevant objects and relations.

If the object and direct claim are already clear, apply the subject rule immediately. A separate recovery note is unnecessary.

A.7:5.9 - Direct Description account and specification-use boundary (normative)

To say that one episteme describes something:

  1. identify the Description episteme through its complete C.2.1 claim content, EntityOfConcern, and effective ReferenceScheme;
  2. state the claims it makes about that EntityOfConcern in ordinary language;
  3. when the receiving use asks how those claims arose or are carried, name the authoring, measurement, observation, model, source-use, representation, refinement, or other direct relation and its participants; and
  4. keep any publication occurrence, form, face, carrier, evidence use, Work, or specification-use gate separate.

If the EntityOfConcern is itself an episteme, the new Description does not automatically copy, preserve, refine, or extend its claims. Any representation, source-use, comparison, refinement, or loss claim needs its own direct rule. If the EntityOfConcern is a system, structure, Method, Work occurrence, physical object, characteristic, relation, or other non-episteme, claims are likewise not “inside” it waiting to be copied; the measurement, observation, model, postulate, authoring, or other relation explains the claim when that explanation is current.

Example. PumpPerformanceDescription-e4 is a C.2.1 episteme whose EntityOfConcern is pump P-12 and whose claims state the measured flow and pressure under the named scheme. MeasurementRun-88 produced ObservationEpisteme-88, and that observation supports the stated measurement claim through its direct evidence-use relation. The Description, pump, measurement Work, observation episteme, evidence use, and publication carrier remain different objects.

A Description episteme becomes usable as a specification when its C.2.1 constitution, checkable claims, and a named harness, validation, conformance, measurement, or evaluation relation capable of checking them for the stated use are recoverable under E.10.D2 and the applicable direct pattern. When viewpoint selection affects reliance, preserve or explicitly update the named describing use and its selected viewpoint. Formality, acceptance conditions, measurement criteria, and verification practice contribute under their own rules; formal notation alone is insufficient. Specification use remains separate from the EntityOfConcern, Description identity, publication expression, and Work.

A Description episteme, its specification-use status, and a publication result are distinct from the activity producing them. Admit a deliberately asserted dated describing, formalizing, specifying or publishing Work using the basis in :2. Use B.1.5 for Method composition, A.15.1 for Work occurrences and temporal parts, B.1.4 for aggregation of already established temporal relations, and B.1.6 for resource spend and yields tied to that Work. An ordinary statement about authoring needs those relations only when its claim uses them.

A.7:5.10 - Outcome specification distinction

A.7 supplies only the distinction. The authoritative promise-facing OutcomeSpec shape is in A.2.3:4.1.1, and the authoritative unit-of-delivery counting rule is in A.2.3:4.1.2.

An OutcomeSpec is a specification-use episteme form, not a new U-kind, a Work occurrence, an affected entity, a post-work state, an operation-result binding, or a verdict episteme. Its mode says which facts the promise constrains:

  • WorkOnly constrains selected facts about one or more delivery Work occurrences;
  • ResultOnly constrains the affected referent and required post-work state, regardless of method; and
  • Composite constrains both.

Example. The provider cuts and styles the client's hair within 20 minutes, and the resulting hairstyle meets the stated evening-style condition. The first clause constrains delivery Work and may name the Method. The second constrains the client’s post-work hairstyle state. Affected-referent, actual-change, production, delivery, acceptance, and evidence-use relations are stated only when the receiving claim needs them. No U.Work.Delta field or universal delta record is required; an optional mathematical change expression remains a separate lens when a named comparison uses it.

Evidence supports assertions about the selected Work facts, affected referent, post-work state, and direct relations. Evidence and its carrier do not become any of those facts. Counting is also separate: A.2.3’s unitOfDelivery says how accepted delivery is counted and how double counting is prevented; it is not part of OutcomeSpec.

A.7:6 - Worked cases

A.7:6.1 - System and episteme

Digital twin and asset. In this example, Twin-e4 is a C.2.1 description episteme about the asset. Maintenance system M updated the asset configuration using Twin-e4. This ordinary sentence keeps the acting System, asset, and episteme visible. If the receiving claim concerns Work, carrier change, evidence, source currentness, or an assignment, add those objects and direct relations separately. Twin-e4 supplies the representation used by M; the updating action belongs to M. A cross-plane use cites only its applicable plane relation and policy.

Review and manuscript. Reviewer Dana reviewed Manuscript-e7 and wrote Review-e2. This is valid ordinary actor wording when Dana is a recoverable System and no inference uses assignment identity. PeerReviewGuide-e2 is a MethodDescription only if its EntityOfConcern is the PeerReview Method and its claims say substantively how that Method is performed. For a precise audit, use A.13 to identify the review performer and A.15.1 to admit the review Work independently. Add F.6 only if the audit must also identify the assignment under which that Work was performed. Keep the resulting review episteme, manuscript and review carriers, and evidence or source relations separate.

A.7:6.2 - Progressive technical examples

Pump in a cooling loop. Pump P-12 circulated coolant during the 10:00-10:45 run. If that sentence remains ordinary actor wording, no full performance record is required. For a precise Work claim, recover the actual performer and its A.13 core, then use A.15.1 to admit the dated run independently with at least one Method actually followed, the interval, and an obtaining containing-System relation. That core includes an obtaining assignment, here CoolingLoopCirculationAssignment-17, its admitted species, holder and assigned-kind participants. Add F.6 only if the claim must also identify the assignment under which the run was performed. Add Capability and another Method only for their own claims; none follows merely from the noun pump.

Standard used in a design. The design team used Safety Standard S-174 when selecting valve V-12. The standard is an episteme and does not act. Its PDF and printed volume are carriers; name them when the receiving source or evidence claim uses them. Valve Selection SOP v5 is a MethodDescription only after the A.3.2 membership test; the ordinary sentence does not require an assignment. A reliance-bearing Work account uses A.13 to identify the actual performer and A.15.1 to admit ValveSelectionWork-47 independently. Keep its :2 admission basis, including the core assignment and Method actually followed, recoverable. Add F.6 only if the account must also say under which assignment the Work was performed. Evidence use and current source edition remain separate.

Set and team. {Alice, Bob, 3.14} is a set and cannot act. Cooling maintenance team T repaired pump P-12 is ordinary actor wording when T is already recoverable as a collective System. Add its coordination Method, Work occurrence, local system-role kind, or assignment only when the corresponding stronger claim is current.

A.7:7 - Conformance Checklist (normative)

IDRequirementPractical test
CC-A7.1 (System, system-role-kind, and behaviour split)A System acts because it satisfies A.1. A local system-role kind classifies it; an assignment occurrence relates it to that kind only when the direct assignment predicate obtains. Method, Capability, Work, transformation, kind, and assignment keep their separate meanings.Accept ordinary actor wording when the System and contribution are recoverable; add classification, assignment, Capability, Method, or Work only for the stronger current claim.
CC‑A7.2 (Transformer-system-role assignment domain)A suffixed source designation such as TransformerSystemRole@ValveSelectionContext is only a locator. The kind must first be recovered through its C.3 candidate domain, membership distinction, boundary probes, and continuity rule; the suffix identifies none of them. A direct U.SystemRoleAssignment species must then admit that kind in its declaration-local kind slot and systems in its holder slot.Type-check the species, holder, kind domain, predicate, applicability, and occurrence identity; do not filter a permissive family value by a role label.
CC-A7.3 (Episteme non-agency)An episteme does not act or hold a work-facing assignment. A System may author, revise, use, or publish it.The ordinary sentence names the acting System; add Work, carrier, publication, evidence, source, or assignment relations only when the receiving claim uses them.
CC‑A7.4 (MethodDescription ≠ Method ≠ Capability ≠ Work)MethodDescription is the same independently identified C.2.1 episteme only when its EntityOfConcern is one admitted Method and it makes at least one substantive claim about that Method as a way of doing; Method, Capability, and Work retain their separate meanings. Form, label, design-time status, authoring, revision, citation, publication, approval, or use time grants no membership.Identify the episteme triple and apply the A.3.2 threshold; then name each current Method, Capability claim and dated Work occurrence separately.
CC-A7.5 (Composition fits its subject)Use B.1.2 for a system-aggregation decision, B.1.5 for Method composition, A.15.1 for Work occurrences and temporal parts, B.1.4 for aggregation of recovered order or temporal relations, and B.1.6 for Work-resource aggregation.The claimed result and its required inputs determine the applicable rule; a generic “process” label supplies none of them.
CC-A7.6 (Carrier/source-currentness reference)An evidence-use claim SHALL identify the episteme and the claim for which it is used. Cite A.10 carrier/source-currentness refs when the particular evidence, source, or reliance use depends on them.Recover the episteme and target claim, then the carrier or source-currentness facts required by that use; ordinary citation does not itself assert an evidence-use relation.
CC-A7.7 (Formal inclusion, collection, and collective)Mathematical set, tuple, coordinate, and other formal inclusion stays with its defining mathematical rule and creates no world-side relation. Use C.29 for an actual mathematical lens and A.19 for the relevant characteristic scale or coordinate. A world-side collection uses its own identity and belongs-to rule. A grouping claimed to act must separately pass all six A.1 matters.Check the distinct formal, collection, and collective-System claims. Infer neither belonging from formal inclusion nor parthood or holonhood from belonging; do not prohibit a separately grounded constructive part claim.
CC‑A7.8 (Diagram legend)Domain “process” or “behaviour” keeps its recovered meaning under the direct rule for that claim. For composition, select the subject’s rule under :5.7; disambiguate an unclear domain use explicitly.A clear domain sentence may stand; an ambiguous one identifies its object and predicate without forcing a Method/Work binary.
CC-A7.9 (Progressive actor wording)A contribution noun may stand for a recoverable System in ordinary prose. An assignment, local system-role kind, Capability, Method, or Work is added only when that distinction changes a receiving inference.The engineer designed the pump may stand. For a precise Work claim, recover the A.13 core and A.15.1 admission basis stated in :2, including the core assignment and at least one Method actually followed. Add F.6 only if the receiving use must also identify the assignment under which that Work was performed.
CC-A7.10 (Work-facing chain clarity)A diagram shows only the positions used by its claim. MethodDescription membership, Capability, assignment, Work, and evidence are not inferred from a complete-looking chain.Begin with the acting System and direct claim; expand the chain only for a named design, attribution, or reliance use.
CC-A7.11 (Acting participant)The acting System is recoverable, whether named directly, by an ordinary contribution noun or by a locally clear actor designation.Clarify the subject where its identity or kind changes the claim. Assignment identity is required only for the corresponding assignment or precise attribution claim.
CC‑A7.12 (System-role domain guards)Work-facing assignment species declare HolderSystemSlot for systems or acting holons and a local system-role-kind domain for AssignedSystemRoleKindSlot. An episteme’s use is governed by its direct relation; the use alone establishes neither a system-role kind nor an assignment.Each assignment names its occurrence and declared species. The species defines participant meanings, predicate, applicability, and occurrence identity; the occurrence supplies holder, assigned kind, case applicability, and extent. Episteme uses name the relation.
CC-A7.13 (EntityOfConcern and Description visibility)Each Description episteme is independently identified by complete claim content, EntityOfConcern, and effective ReferenceScheme. A.7 supplies no universal describing constructor.Text or diagram keeps the EntityOfConcern and Description episteme visible and states any current authoring, measurement, observation, model, source-use, representation, or refinement relation separately.
CC-A7.14 (Description-source discipline)A Description about an episteme does not automatically copy or preserve its claims; a Description about a non-episteme does not extract claims from the subject.Name the source-use, representation, refinement, measurement, observation, model, authoring, or other relation that warrants the claim when that explanation is current.
CC-A7.15 (Specification-use boundary)When text claims specification force for a specification, formal specification, requirement, acceptance item, harnessed invariant, or measurement-criterion object, it retains the independently constituted Description episteme, checkable claims, and a named harness, validation, conformance, measurement, or evaluation relation capable of checking those claims for the stated use. Preserve or explicitly update the named describing use and selected viewpoint when they affect reliance. C.2.3 formality, A.21 gate or acceptance discipline, C.16 measurement criteria, A.6.2 epistemic morphing, B.5.MR model refinement, and other direct patterns may contribute under their own conditions. E.17 expresses an already admitted specification use; E.10 governs its suffix. Neither publication, suffix, nor formal notation substitutes for the admission conjunction.Recover the episteme, claims and capable checking relation for the stated use, plus any reliance-relevant viewpoint selection. Specification remains a use of the Description episteme, not a peer ontology class.
CC-A7.16 (Method and Work separation)A Description episteme, its specification-use status, and a publication result do not carry the cost or time actuals of the activity producing them.Recover any separately admitted describing, formalizing, specifying, or publishing Work; keep Method composition, Work histories and temporal parts, and Work resource relations distinct.
CC-A7.17 (Publication face and form discipline)Distinguish publication face, form, unit, carrier and rendering when the claim uses those positions. PlainView, TechCard, InteropCard and AssuranceLane are faces over epistemes or views; A.7 introduces no new publication kind.Check the publication object and relation under their direct rules. Use F.18 when a durable name needs settlement; token form alone establishes no kind or membership.
CC‑A7.18 (Semantic and plane crossings).A face relying on an obtaining F.9 Bridge cites its two F.17 local senses, that Bridge, and a separate bounded-use claim; CL is optional. Other semantic relations use their own predicates and participants. Cross-plane content cites the applicable plane relation. Context or plane difference alone creates no Bridge, CL, or penalty; any trust penalty cites the named current policy and its applicability to this use.Audit resolves the semantic or plane relation and any current policy application without inferring one from labels, contexts, planes, cards, or CL.
CC-A7.19 (UTS row reference)When a selected durable naming settlement and the receiving use require an F.17 term row, public names shown on faces SHALL point to that UTS row with twin labels (Tech/Plain), edition pins, and carrier/source-currentness refs when the source or evidence use depends on them.If the row is needed, recover its identifier, labels, edition pins, and applicable source/evidence refs. Otherwise keep the sufficiently defined local designation; publication alone requires no row.
CC-A7.20 (Direct Method reference)An identifier’s designation of one Method under an effective ReferenceScheme and a receiving claim’s resolved methodRef remain separate from U.MethodDescription membership. Neither requires a description hop; methodDescriptionRef is optional and edition-specific only when the receiving claim uses that episteme’s claims.Resolve the identifier and receiving reference directly to the Method, then apply A.3.2 independently only for a cited description episteme.

A.7:8 - Canonical rewrites (didactic library)

The middle column stipulates facts for each teaching case, including its named System, Method, classification, object, or occurrence; these facts are not recovered from the short quotation in the first column. In a real repair, establish the needed facts before using the corresponding rewrite. Keep an ordinary deployed-System metonymy when that is the recoverable intended reading, and do not invent an actor, Method, classification, or assignment to complete a chain.

Source wordingStart withAdd only for the stronger claim
“The process enforced the rule.”Control system CS-4 enforced Rule R during Run 12.If dated Work is current, recover the actual performer and its A.13 core, then admit the occurrence independently through A.15.1 with the :2 basis, including at least one Method actually followed. If the account must also identify the assignment under which the Work was performed, check it separately through F.6. Add another Method or further evidence detail only when the receiving claim needs it.
“The specification decided to tighten limits.”Design-control team D changed the limit in Specification-e4.The successor episteme, authoring Work, carrier and publication relations when current. The specification never acts.
“Our role is pump; the role circulates coolant.”Pump P-12 circulates coolant in loop L.The local system-role kind for a classification claim; the assignment occurrence only for assignment or attribution; Capability, Method, and Work only for their respective claims.
“We followed the blueprint, so it is done.”Team T used Method M; completion requires evidence that the stated Work or result conditions, or both, hold.The blueprint label identifies neither a Method nor a MethodDescription. Cite a MethodDescription only after A.3.2 membership is established and its claims are used; keep the blueprint carrier, Work and evidence relations separate.
“Team = set of members; it repaired the pump.”Team T repaired pump P-12 only after T is recoverable as a collective System under all six A.1 matters.State any world-side belongs-to rule separately; add coordination Method, Work, local kind, assignment, or constructive part relation only when that stronger claim is current.
“Method composition establishes the cost of the work.”Method composition follows B.1.5; Work cost requires the actual resource and time relations used by B.1.6.Admit the Work under A.15.1 and recover the resource measurements, accounting boundary and aggregation policy required for that cost claim.
“Holon has TransformerRole.”System S counts under the kind currently named TransformerSystemRole for the ValveSelection use.Recover the C.3 kind independently. Add the assignment occurrence and species only when an assignment claim is current; the use label is not part of kind identity.
“The publication relation is a special mechanism.”Publication makes Description episteme E available through form F on carrier C.State the publication occurrence, view or conformance, carrier, and publishing Work under their direct patterns.

A.7:9 - Anti‑patterns (with fixes)

  1. System-role-kind-as-behaviour — calling the system-role kind a function or saying it acts. Fix: Name the acting System and direct behaviour or Work first. Add the local kind, assignment, Method, or Capability only when that stronger claim is current; none of them acts.

  2. Episteme‑as‑system — “the model routed traffic” when “model” denotes an episteme rather than the deployed acting System. Fix: Name the System that used the episteme; keep recoverable deployed-System shorthand when that is the intended referent. Add Work, carrier, assignment, evidence, or source details only when the receiving claim uses them.

  3. Missing performed-occurrence claim — a receiving decision needs facts about actual Work but receives only Method, description or Capability claims. Fix: Admit and state that Work under the basis in :2. An ordinary action sentence or design-time distinction diagram needs no invented Work identity.

  4. Composition blur — using one “process operator” for unlike claims. Fix: Recover the subject and intended result, then use :5.7 to select the system, Method, temporal or Work-resource rule and its prerequisites.

  5. Formal set, world-side collection, and collective collapse — mathematical inclusion or collection belonging is used to make a grouping act or to infer constructive parthood. Fix: Keep formal inclusion with its mathematical or representation rule; state world-side belonging under the collection’s own rule; require all six A.1 matters for a collective System; state any constructive part relation separately.

  6. Unspecified evidence use — citing content as evidence without identifying the episteme, target claim, or conditions needed for that use. Fix: Recover the evidence-use relation. Add A.10 carrier/source-currentness refs when that evidence or source use depends on them; a carrier reference alone does not establish support.

  7. Holon/system drift — “holon maintains temperature”. Fix: Identify the acting System when “holon” leaves the capable participant unclear. Ordinary wording may stand when that participant is already recoverable.

  8. Function and system-role-kind swap in tables — columns labelled “Function” whose entries are local system-role kinds. Fix: Rename the column to System-role kind. If behaviour is also being compared, give it a separate column and state the behaviour claim under its direct rule, including A.6.F functional behaviour or A.3.4 transformation where applicable.

  9. Process‑word leakage — domain “process” used as FPF operator. Fix: Use the Γ operator for the composition claim. Keep a clear domain use of “process”; if it is ambiguous, state the Method, Work, transformation, mechanism, or other object intended.

  10. Carrier and episteme swap — “we versioned the model” meaning a file was renamed. Fix: State whether the episteme content changed; if only a carrier was renamed, say so.

  11. Publication relation versus publishing operation — treating the availability relation as the Method or Mechanism used to publish. Fix: Identify the Description episteme through C.2.1 and keep specification use and publication separate. State any authoring, measurement, observation, model, source-use, representation or refinement relation needed by the claim. An asserted dated build, render or upload Work uses the basis in :2; the publishing System acts on carriers.

  12. Form-first MethodDescription — “this is an SOP/algorithm/script, therefore it is a MethodDescription.” Fix: Identify the C.2.1 episteme, resolve one admitted Method as its EntityOfConcern, and find at least one substantive way-of-doing claim; otherwise retain only the source cue.

  13. Mandatory description hop — a Method identifier or receiving methodRef is forced through a document or description edition. Fix: Resolve designation and the receiving reference directly to the Method under their effective ReferenceScheme discipline; cite methodDescriptionRef separately only when its claims are used.

  14. Lifecycle time as membership — authoring, revision, citation, approval, publication, or use is treated as creating MethodDescription membership. Fix: Keep the authoring, revision, citation, approval, publication or use relation under its subject rule; admit dated Work separately only when claimed. Apply the A.3.2 membership test to the independently identified episteme.

A.7:10 - Consequences

BenefitWhy it mattersTrade‑off / Mitigation
Category safety at scaleMakes category slips in claims across holarchies easier to recognize and correct.Slight explicitness; mitigate by keeping ordinary System-and-action wording and adding assignment, kind, Method, Capability, Work, carrier, or evidence detail only when a receiving inference needs it.
Inspectable evidence useClaim-relative evidence use and the needed A.10 provenance, carrier and source-currentness relations expose the audit basis.Recover only the relations and facts needed by that use.
Composition rule selectionThe subject determines which Γ rule and premises govern an aggregation claim.Check the invariant under that rule and its premises.
Readable repair examplesThe rewrites show how a recovered distinction changes the sentence.Establish the teaching case’s stipulated facts in a real use before adopting its rewrite.

A.7:10.1 - EntityOfConcern and publication-boundary consequences

BenefitsTrade‑offs / Mitigations
Category-error detection and correction. Clear separation of System and Episteme, EntityOfConcern and Description-episteme boundary, specification use and model refinement, and publication availability helps expose recurring modeling defects.Name publication face, form, unit, carrier, and rendering uses when the distinction matters; E.8 supplies publication-face guidance.
Audit and explanation share referents. References distinguish the evidence episteme, target claim, carrier and any needed source-currentness claim. Different publication faces can explain or expose those same values.Add only the face and reference detail the receiving use needs.
Cross-context and plane safety. Faces expose an obtaining F.9 Bridge only for two local senses and keep any separate bounded-use claim and optional CL distinct; cross-plane use exposes its applicable plane relation.Authors must name only current relations and policies; tooling may assist, but no penalty follows automatically from context, plane, Bridge, or CL.

A.7:11 - SoTA‑Echoing

A.7:12 - Rationale (informal)

  • Engineering cognition: A small, repeatable grammar helps practitioners recognize and correct category slips such as “process vs procedure vs execution”.
  • Didactic primacy: Practitioners start with a readable sentence naming the System, action, subject, or Description. They add assignment, local system-role kind, Method, Capability, WorkPlan, Work, MethodDescription, carrier, source, or evidence relations only when the current claim uses those distinctions.
  • Publication boundaries: A card or table makes claims available; it may also be the subject of a different description. Identify which relation is current before treating it as the EntityOfConcern, a Description, a specification use, or evidence. Keeping those positions separate lets one source support several publication forms without changing its claims merely through presentation.

A.7:13 - Relations

Builds on: A.1 (Holon), A.2 and A.2.1 (system-role kinds and system-role-assignment relations), A.3.1/A.3.2/A.3.4 (Method, MethodDescription, Transformation), A.10 (evidence-provenance, carrier, and source-currentness relations), A.14 (Mereology), A.15/A.15.1/A.15.2 (System-Role–Method–Work, Work, and WorkPlan Alignment).

  • Constrains: A.13 (Agency sits on systems only; epistemes non-behavioural), B.1.2:4 system-aggregation and delimitation decisions, B.1.5 Method composition, B.1.4 temporal aggregation, and B.1.6 Work-resource aggregation. These uses preserve the System, Method, Work, and Episteme distinctions; publication follows its own availability conditions in E.24.PUB.
  • Extends: E.8, E.10, Part F and Part G, B.3, and the C-cluster by enforcing the EntityOfConcern/Description boundary, specification-use and publication orthogonality, System/Episteme separation, same or near-same EntityOfConcern discipline across views, and progressive actor wording. Publication remains the separately governed availability of an episteme through a form and carrier.
  • Coordinates with: E.18 for crossing visibility, A.21 for gate checks, E.17 for publication, and E.10 for lexical checks. F.17 identifies local senses and F.9 governs an obtaining Bridge between two such senses; a ReferencePlane crossing follows its applicable plane relation. The bounded-use claim, reliance, optional CL, and any named policy penalty remain separate.

A.7:14 - Practitioner one-page review (copy-paste)

Ordinary repair account

Engineer Dana repaired pump P-12. MaintenanceNote-e4 describes the repair. Carrier C bears publication form F.

Keep the sentence this short when the receiving use needs no stronger distinction. Contribution nouns such as engineer, reviewer, pump, team, or service are acceptable when the underlying System and contribution are recoverable and no decision, attribution, admission, or reliance depends on a hidden kind or assignment identity.

Reliance-bearing expansion, when needed

The practitioner used A.13 to identify System S as the actual performer with its core basis, then used A.15.1 to admit dated Work W independently from its performance history, enacted Method M, temporal extent, and obtaining containing-System relation. If the receiving account must also say under which assignment W was performed, the practitioner uses F.6 to check that relation against the same obtaining assignment A and compare S with A's holder. Keep the required core facts recoverable; add Capability C, another Method, further detail of local system-role kind K, method-description episteme D, carrier P, evidence-use relation R, or resource relations only where the receiving claim relies on them.

Six checks

  1. Acting subject: Is the acting System recoverable? If assignment identity is not used, do not invent it.
  2. Current distinctions: Are Method, Capability, Work, assignment, local kind, and MethodDescription named only for claims that use them?
  3. Description boundary: Is each Description episteme independently identified by claim content, EntityOfConcern, and effective scheme, with any authoring, measurement, source-use, representation, or refinement relation stated separately?
  4. Method and Work: Use B.1.5 to judge Method composition; use A.15.1 and B.1.6 for the Work occurrence and its resource actuals, and B.1.4 when already established temporal relations need aggregation.
  5. Episteme and carrier: Does the episteme remain non-acting and distinct from its publication form and carrier?
  6. Grouping: If a group acts, is it recoverable as a collective System rather than merely a set?

Diagram legend stub

  • process in source language may mean Method, Work, transformation, mechanism, or another direct object; recover the live claim.
  • A system-role-kind column lists local classifications, not behaviour.
  • A behaviour column states the behaviour claim under its direct rule; it need not display a full assignment chain.

A.7:End

A.7.1 - Consequence-Guided Ontological Problem Solving

Type: Architectural (A) Status: Stable Normativity: Normative

A.7.1:0 - Use this when

Use this pattern when a clear or apparently clear engineering claim produces the wrong action, identity, dependence, obtaining, responsibility, or projection consequence, and a typed or constructive distinction may repair it. One grounded counterexample or one subject-pattern invariant can trigger the work; you do not need two alternative ontologies before starting.

The first useful move is to state the affected engineering result and the smallest defeated or disputed claim, then enter the first diagnostic locus that can change that result. Stop as soon as an admitted working account determines the next move truthfully.

Not this pattern when. If the blocker is missing observation or evidence, reopen the domain or evidence question and its predicate. If wording alone hides the distinction, use F.19, with C.2.P or E.10 for a remaining semantic question. If the problem is a material premise conflict between FPF methods, use A.7.2. A proposed new framework pattern or U-kind follows the applicable E.24 or E.24.UK admission, with A.8 and A.11; a local clarification or saved result alone requires neither proposal.

The primary reader is a domain engineer or ontology analyst responsible for the affected use. The procedural content describes the consequence-guided ontology-analysis Method developed in §4. To assert U.MethodDescription membership for a pattern episteme, identify that admitted Method as its EntityOfConcern and satisfy A.3.2.

When ontology-analysis Work is claimed, recover the performing U.System through A.13 and let A.15.1 independently admit the dated U.Work and enacted Method. Add F.6 only when the analysis result also consumes assignment-bound attribution through the same obtaining A.13 assignment; missing or failed attribution alone leaves independently admitted Work intact. Recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1.

The reader, performer System, description episteme, Method, any assignment and attribution, Work, and returned engineering result remain separate.

A.7.1:1 - Problem frame

A maintenance sentence can be lexically clear and still merge two relation occurrences across removal and reinstallation. A responsibility claim can use a plausible system-role word or assignment while omitting the direct responsibility predicate and its participants. A graph or logical type can look exact while omitting the construction that changes the action. In these situations, a glossary is too little and an exhaustive ontology exercise is too much.

The concern is the smallest ontology-analysis application that changes one declared engineering use, result, or guarantee. The ordinary product is a repaired statement, Method choice, action, subject-qualified result, or explicit blocker—not an ontology artifact by default.

A.7.1:2 - Problem

Ontology work often starts from available vocabulary rather than a failed consequence. That encourages blanket constructive replay, premature kind admission, and durable records even when direct kinds and relations already decide the next action. The opposite failure treats clear words as sufficient and leaves a category error inside Work, evidence, system-role-kind, assignment, state, capability, relation, responsibility, or representation claims.

The practical question is which distinction changes the engineering move at the required guarantee, and which sufficient return requires the least effort.

A.7.1:3 - Forces

ForceTension
Consequence focus vs ontological completenessThe next action may need one distinction, while the subject admits many legitimate constructions.
Subject-pattern reuse vs missing ontologyExisting patterns should decide ordinary cases, yet a durable missing distinction sometimes must be admitted.
Early stop vs hidden projection lossCoarse accounts are economical until a consequential counterexample defeats them.
Domain inquiry vs ontology analysisMissing facts require observation; conflated kinds require conceptual repair.
Working account vs reusable recordA local decision may be enough; recurrence, automation, dispute, or high consequence can justify durable capture.

A.7.1:4 - Solution

A.7.1:4.1 - Retain the complete application boundary

The analysis described here narrows C.19.2’s method claims to consequence-guided ontology questions. Retain the declared use, problem-facing result, claimed guarantee, horizon and useful threshold. Keep the description episteme, described Method, reader and result distinct; add the performer, assignment and dated Work basis in §0 only when such a Work is asserted. This relation between descriptions alone establishes no relation occurrence between their described Methods.

The normal short path uses the already selected A.7.1 analysis method as its one apparatus. It begins from an engineering subject, subject predicate, and the pattern content locating that predicate; subject and predicate are inputs and constraints, not apparatus candidates.

Use C.18 only when the team must generate or reframe alternative analysis methods, models, formalisms, or other direct-kind apparatuses for the same declared use. Use C.11 only when two or more already available apparatuses are eligible for that same use and guarantee and a local choice is needed.

Apply A.15.2 when planning remains necessary, the §0 basis when dated Work is asserted, and C.24 when tool-call enactment planning is the remaining question.

A.7.1:4.2 - Start from the defeated consequence

Name five things in ordinary domain language:

  1. the affected engineering result and its required guarantee;
  2. the smallest claim whose current reading fails or is disputed;
  3. the observed consequence failure, subject-pattern invariant, or grounded counterexample;
  4. at least one candidate correction or a request to recover one; and
  5. any action that must remain blocked until the distinction is settled, with the rule or consequence that requires that stop.

One defeated reading is enough. Recovering or constructing an alternative can be part of the work.

A.7.1:4.3 - Enter one of four diagnostic loci

The four loci are a named diagnostic set; they are not a mandatory sequence.

  1. Domain inquiry. Ask whether the relevant behaviors, interventions, evidence, and consequences are known. If not, return domain, measurement, or evidence work without ontology invention.
  2. Wording use. Ask whether one term or sentence obscures distinct claims. Use F.19; continue to C.2.P or E.10 only when a semantic question remains.
  3. Working typed account. Test whether direct kinds, participant positions, relation direction, temporal qualification, evidence relation, and occurrence identity suffice for the use. Reuse the direct relation, local system-role-kind, system-role-assignment, state, capability, Method, Work, responsibility, and evidence patterns already in FPF.
  4. Subject-specific constructive ground. Return to the subject construction only when action, identity, dependence, obtaining, constitution, or decision-changing CT2R loss differs across constructions. Use the direct relation-occurrence, local system-role-kind, direct U.SystemRoleAssignment species, system-recognition, Work-occurrence, state or capability, responsibility, or structural-construction pattern. Do not default to C.13 or a generic constructive calculus.

A.7.1:4.4 - Perform only consequence-changing ontology work

  1. Select the first locus capable of resolving the delta.
  2. Perform the required domain inquiry, wording repair, typing, evidence assessment or construction analysis.
  3. Cite A.7.CP claim IDs when their contents are load-bearing. Use ClaimUsedAsReasoningBasisRelation@Context when the receiving use needs to recover the Work, receiving result, posture, scope, or interval of that reliance. Do not traverse the compact by default.
  4. Preserve direct evidence, currentness, source-use, kind-admission, and subject-construction patterns.
  5. Return the repaired result immediately when the next action is truthful at the declared guarantee.

The method result uses one of these closed local dispositions in its result episteme:

  • repairedEngineeringStatement;
  • methodChoice;
  • actionSelected;
  • noOntologyIntervention;
  • returnToDirectOwner;
  • unresolvedWithBlocker.

These are method-result dispositions, not new U-kinds. Each names the affected use, practical result or blocked claim, and stop/reopen condition.

A.7.1:4.5 - Decide whether the working account is enough

A working account is sufficient when admitted direct kinds and relations determine the next move and plausible constructional alternatives do not change the result or guarantee. Stop without declaring the alternatives false. Do not create an occurrence ledger, evidence apparatus, publication package, or ontology record whose distinctions cannot change the use.

Save the ontology result when reuse, dispute, consequence, automation or cross-pattern change makes persistence valuable.

Admission of a proposed framework pattern or U-kind follows E.24 or E.24.UK respectively; a local distinction follows its subject rule. Persistence alone opens no new-kind admission. If a needed predicate or kind remains unadmitted, return the missing governor or affected blocked claim; rely on it only after the applicable positive admission.

A.7.1:4.6 - Reopen and teach without premature structure admission

Reopen on a consequential counterexample, changed guarantee, failed use, projection loss, changed occurrence identity, or a newly admitted subject-pattern distinction. Reopen only the affected engineering and ontology decisions.

A short presentation of the domain inquiry, wording repair, typed account or constructive ground may remain an ordinary explanation. Identify any claim-bearing episteme under C.2.1 when its identity matters; persistence is a separate choice.

A reusable CGUS requires one identified A.22 structure, local locus bindings, selected relations and applied constraints, and at least two potential continuations; its present-case continuation results remain separate.

A.7.1:5 - Archetypal Grounding

Support occurrence inquiry. A maintenance claim says bearing B1 continued supporting shaft S1 after removal and reinstallation. The A.7.1 analysis method is already selected; the bearing/shaft subject and the applicable subject predicate are inputs and constraints, so the work creates no option set.

Recover the load-bearing relation and its obtaining and occurrence-identity rules before counting occurrences. If an admitted subject rule makes removal end one occurrence and reinstallation begin another, apply that rule and the current facts to repair the warranty and incident-attribution claim. If the receiving use needs that distinction but no applicable rule defines it, return the missing governor and blocked claim.

Use A7CP-01 and A7CP-10 only when their claims are load-bearing in this reasoning; neither compact claim defines the subject relation.

Missing telemetry non-use. A team cannot determine pump state because telemetry was never collected. State kinds, evidence relations, and candidate actions are already clear. The result is returnToDirectOwner for measurement and evidence work with the blocked state claim; no premise-use occurrence or ontology artifact is created.

Construction-changing case. A maintenance account uses “part” both for an item belonging to inventory collection R and for a component installed in pump P. Suppose R’s membership rule includes exactly items with an active inventory entry. Closing that entry ends belonging to R; it does not by itself remove the installed component. Physical removal changes ComponentOf only under the direct A.14/subject predicate and case facts. If one item participates in both relations, test each separately. Use C.13 when the decision also needs the resulting construction account. Repair the maintenance claim to name the change and preserve any unaffected relation.

A.7.1:6 - Bias-Annotation

Ontology-display bias favors elaborate category systems even when existing predicates and current facts already decide the case. Lexical bias treats clear wording as proof of sound ontology. Evidence bias converts unresolved reliance into a third world state. The mitigation is a defeated consequence, first-capable locus, subject-qualified result or blocker, and positive stop.

A.7.1:7 - Conformance Checklist

IDCheck
CC-A7.1-1The use names one engineering result, guarantee, smallest disputed claim, and consequence failure.
CC-A7.1-2One grounded defeated reading can trigger the method; fabricated alternatives are not required.
CC-A7.1-3The work enters the first capable domain, wording, typed-account, or constructive-ground locus rather than a mandatory ladder.
CC-A7.1-4The normal case uses the already selected A.7.1 analysis method as its one apparatus; the engineering subject and its subject pattern remain inputs and constraints. Candidate generation and choice open only for alternative direct-kind apparatuses eligible for the same use and guarantee.
CC-A7.1-5Keep the reader, description episteme, Method and problem-facing result distinct. A MethodDescription claim satisfies A.3.2; an asserted dated Work uses the independent A.13/A.15.1 basis in §0, with F.6 only for the precise attribution consumed. Local system-role-kind classification and the obtaining assignment remain separate claims.
CC-A7.1-6Cite only load-bearing A.7.CP claims; identify their reasoning-basis occurrences when the receiving use needs the reliance account under §4.4.
CC-A7.1-7Direct relation, local system-role-kind, assignment, state, capability, responsibility, evidence, source-use, Work, and kind-admission patterns remain authoritative.
CC-A7.1-8The result uses one declared local disposition and includes stop/reopen or blocker.
CC-A7.1-9A saved ontology result serves reuse, dispute, consequence, automation or cross-pattern change. Any new framework-pattern or U-kind proposal satisfies its applicable admission; saving a local distinction does not itself open that proposal.
CC-A7.1-10No provisional branch presentation is treated as an admitted CGUS.

A.7.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Begin from a glossary or full ontology checklist.Begin from the affected result and defeated claim; enter only the capable locus.
Treat missing evidence as a missing kind.Return to measurement/evidence with the blocked claim.
Run constructive analysis for every typed relation.Stop when direct kinds, positions, direction, time, and identity already determine the move.
Treat a graph, predicate, or formal class as the world construction.Recover CT2R loss and the direct subject construction before reverse inference.
Let a description episteme, local kind or assignment act.Name the capable System when it is unclear. For a deliberately asserted dated ontology-analysis Work, apply the §0 basis; keep local-kind classification, assignment and any F.6 attribution distinct. Ordinary reader action needs no invented Work identity.
Copy the twelve compact claims into the method.Cite A7CP-* IDs only when load-bearing; keep A.7.CP as the authoritative source.

A.7.1:9 - Consequences

The pattern gives ontology work a practical exit. It can repair a consequential conflation, return to the unresolved domain question, or stop at an adequate working account without declaring the unneeded alternatives false. The practitioner must identify the defeated claim and what result resolves it. This bounds the ontology work while retaining the facts and distinctions the engineering action needs.

A.7.1:10 - Rationale

Ontology effort should scale with the consequence that changes. A subject-pattern invariant or grounded counterexample exposes why the current account fails. The four loci distinguish where repair can occur without forcing an order. C.19.2 supplies the consequence-relative effort boundary, result separation and sufficient one-apparatus path.

Repair only the ontology that changes the engineering move.

A.7.1:11 - SoTA-Echoing

Practice questionSource contributionFPF alignmentDisposition
How should analysis effort be bounded?Resource-rational cognition ties analysis to decision value under limited resources (Lieder & Griffiths 2020).The useful threshold, first-capable locus, and positive subject-qualified result or blocker bound current ontology work. The missing-telemetry case demonstrates non-use.Adapt. No universal cost scalar decides ontology truth.
How much model detail is useful?Resolution is question-relative and balances decision distortion against parsimony (Merrick & Weyant 2019).A working account is enough when alternatives cannot change the result or guarantee; consequence-changing cases reopen it.Adapt. FPF preserves multiple direct ontological accounts under their applicable patterns rather than one resolution axis.
Do different ontology questions need different methods and outputs?Competency-question research distinguishes purposes and expected products (Keet & Khan 2024).The four diagnostic loci and result dispositions keep domain, wording, typed, constructive, and return outcomes distinct.Adapt. No mandatory competency-question artifact is imposed.
When should a coarse account be refined?Counterexample-guided abstraction refinement repairs only distinctions exposed by a consequential counterexample (Clarke et al. 2000, canonical verification lineage).A grounded counterexample can trigger one application and reopen the smallest receiving claim.Comparator only. Model-checking authority and tooling are not generalized to ontology.

A.7.1:12 - Relations

  • Description-level specialization: A.7.1 narrows the method claims stated by C.19.2 to ontology analysis. It retains the use, problem-facing result, guarantee, horizon, useful threshold and stop/reopen conditions. On the ordinary one-apparatus path, the selected analysis Method is the apparatus and the engineering subject and its rule are inputs. Alternative generation and choice use C.18/C.11 only under §4.1. Description membership and Work use the separate conditions in §0; this description-level relation alone establishes no relation between the described Methods.
  • Consumes: A.7.CP claim content when load-bearing; uses ClaimUsedAsReasoningBasisRelation@Context when the receiving use needs the reasoning-basis account under §4.4.
  • Coordinates with: A.7.2 when a material cross-pattern premise conflict is current; neither method is the other’s parent or source of premise truth.
  • Returns to: direct relation, local system-role-kind, assignment, System, state, capability, Method, Work, responsibility, evidence, temporal, structural, and domain patterns for the claim being repaired.
  • Uses for new framework-pattern or U-kind proposals: E.24 or E.24.UK, with A.8 and A.11. A.7.1 itself admits neither; local kinds and relations retain their subject rules.
  • Preserves: A.7 Distinction and A.22.CGUS admission law.

A.7.1:End

A.7.2 - FPF Ontology-Premise Reconciliation

Type: Architectural (A) Status: Stable Normativity: Normative

A.7.2:0 - Use this when

Use this pattern when two or more dated applications of current FPF methods or patterns yield ontology-claim or decision epistemes whose claims or practical consequences cannot jointly support the same receiving claim or consequence in the same scope. Trace each result to the pattern or method clauses, premises, and source-use occurrences that the application used; a difference between texts alone is not a conflict. One material contradiction is enough; recurrent conflict is not required.

The first useful move is to name the smallest receiving ontology claim and, for each dated application, the result claim or decision, the practical consequence it would support, and the clause, premise, or source use on which it relied. If the apparent conflict disappears after recovering the applicable scopes, return a context split. Different scope labels alone do not resolve incompatible claims in their shared domain.

Not this pattern when. A vocabulary difference, unlike source function, or different subject with no shared practical consequence is not a premise conflict. Use A.7.1 for one engineering ontology defect, F.19 for wording repair with C.2.P/E.10 for a remaining semantic question, direct evidence-use or formal patterns for missing warrant, and source-currentness patterns for stale editions.

The primary reader is an FPF maintainer, architecture steward, or pattern author responsible for a material cross-pattern contradiction. The procedural content describes the reconciliation Method in §4. A U.MethodDescription assertion requires that admitted Method as the episteme’s EntityOfConcern and A.3.2 membership.

For any dated reconciliation U.Work, use A.13 to identify the performer System and let A.15.1 independently admit the occurrence. If the case or receiving result must also identify the assignment under which the reconciliation Work was performed, check that relation separately through F.6 against the assignment used by A.13. A short result may omit an assignment identifier it does not use; no unused assignment or attribution is presumed.

The pattern episteme, described Method, reader, performing System, any separately established assignment species and occurrence, optional attribution check, Work, source uses, and returned FPF decision remain distinct.

A.7.2:1 - Problem frame

Neighboring FPF pattern epistemes and U.MethodDescription epistemes can state different premises about existence, constitution, identity, dependence, obtaining, representation, agency, or formal projection. One dated application of a system-role-assignment clause may conclude that a relation does not obtain for its participants and scope because the instituting act required by its applicable rule has not occurred, while another concludes that the same relation obtains from a signed organization chart alone. Both texts may be internally clear, yet these application results conflict about assignment constitution in the same scope; duty and responsibility remain separately governed claims.

The concern is one bounded reconciliation of FPF receiving claims and their practical consequences. The ordinary result can be compatibility, separation, non-composition, no-conflict stop, or unresolved escalation. Convergence is not mandatory.

A.7.2:2 - Problem

A premise catalogue does not repair dated applications whose result claims conflict. Prestige ranking of sources can hide the receiving claim, while broad foundation rewriting can damage unrelated pattern decisions. Conversely, treating different source functions as automatically incomparable can leave a same-claim contradiction unresolved.

Reconciliation recovers what each application used, what source content bore on the receiving claim, and which evidence and currentness assertions the comparison needs. Reopen an FPF decision only when that comparison establishes a conflict requiring repair.

A.7.2:3 - Forces

ForceTension
Compatibility vs pluralismShared use is valuable, but some methods should remain context-separated or non-composable.
Small repair vs foundation driftReopen the decision that carries the conflict without rewriting unrelated ontology.
Source use vs source prestigeSources matter through claim use, not status labels or total rankings.
Formal comparability vs domain evidenceTyped consequences can expose contradiction, but formal shape cannot settle the world by itself.
Current decision vs reopenabilityThe current published FPF decisions supply an internal basis, while grounded counterexamples and contradictions can require reconsideration.

A.7.2:4 - Solution

A.7.2:4.1 - Recover the conflict

  1. Name the smallest disputed receiving ontology claim and its current edition.
  2. For each dated application, name its resulting ontology-claim or decision episteme, the practical consequence the receiving use would take from it, and the method clause, premise, or source-use occurrence on which the work relied.
  3. Recover the FPF claim epistemes, dated application Work, direct kinds and relations, and source-use occurrences needed for this comparison. Include A.7.CP reasoning-basis occurrences only for claims used; recover scope and currentness where they affect the result.
  4. Test whether the result claims support incompatible answers to the same receiving claim or practical consequence in the same scope. If not, return noConflictStop or contextSplit.
  5. Compare source content through direct evidence, formal-semantics, domain, scope, and currentness patterns. Do not rank source labels.
  6. Translate candidate distinctions into FPF objects and constructive consequences. Test them against subject evidence and only the A7CP-* claims used by the reconciliation work.
  7. When the comparison establishes a defective method clause or subject-pattern decision, reopen the smallest affected decision set and repair it, preserving unaffected decisions. Run enough of the affected application again to obtain a checked result. When the available grounds warrant neither correction, retain the appropriate doNotCompose or unresolvedEscalation result under §4.2.
  8. Return one declared result with affected use, stop, and reopen condition.

A.7.2:4.2 - Use one closed reconciliation result set

The result episteme uses exactly one local disposition:

  • reconciledCompatibility — repaired clauses and checked application results now support compatible use for the named claim and scope;
  • contextSplit — the apparent incompatibility disappears under the recovered contexts or scopes; each claim retains its separate subject-matter warrant;
  • doNotCompose — both may remain current, but their outputs must not be combined for the named use;
  • unresolvedEscalation — evidence or decision authority is insufficient, with the blocked use and receiving subject pattern named;
  • noConflictStop — the apparent conflict disappears after claim, consequence, or scope recovery.

These are reconciliation-result dispositions, not new U-kinds. Compatible co-use is demonstrated only when warranted. A conflict does not have to end in one winner.

A.7.2:4.3 - Record claim-relative source use

OntologyClaimSourceUseRelation@Context relates one source episteme, one receiving ontology claim, and the dated ontology-decision or reconciliation work occurrence that consumes that source for that claim. It is local to this use and does not create a universal source-authority relation.

OntologySourceUseFunctionValue ::=
  formulateReceivingClaim
  | constrainReceivingClaim
  | testOrStressReceivingClaim
  | interpretFormalOrImplementationSemantics
  | compareReceivingAlternatives
  | traceLineage

OntologySourceUseDispositionValue ::=
  adopt | adapt | reject | comparatorOnly | lineageOnly | unresolved

ReceivingClaimChangeDispositionValue ::=
  changed | unchanged | undeterminedPendingResolution

OntologyClaimSourceUseRelation@Context <: U.Relation

RelationSignature:
  SourceEpistemeSlot:
    SlotKind: SourceEpistemeSlot
    ValueKind: U.Episteme
    refMode: U.EpistemeRef
  ReceivingOntologyClaimSlot:
    SlotKind: ReceivingOntologyClaimSlot
    ValueKind: U.Episteme
    refMode: U.EpistemeRef
  OntologyDecisionWorkSlot:
    SlotKind: OntologyDecisionWorkSlot
    ValueKind: U.Work
    refMode: WorkRef

semanticDirection: SourceEpistemeSlot -> ReceivingOntologyClaimSlot
  through the named OntologyDecisionWorkSlot

RelationOccurrenceQualifiers:
  sourceUseScope: U.ClaimScope
  useFunction: OntologySourceUseFunctionValue
  sourceContentSliceRef?: U.EpistemeRef
  sourceContentKindRef?: U.KindRef
  modelUseStructureRef?: SelectedStructureReference
  sourceCurrentnessResultRef?: U.EpistemeRef
  receivingClaimCurrentnessResultRef?: U.EpistemeRef
  landedFPFDecisionRef?: U.EpistemeRef
  evidenceUseRelationRefs[]?: U.EntityRef
  disposition?: OntologySourceUseDispositionValue
  blockedOverreadRef?: U.EpistemeRef
  receivingClaimChangeDisposition?: ReceivingClaimChangeDispositionValue

OccurrenceIdentity:
  <source-episteme edition,
   receiving-claim edition,
   ontology-decision work occurrence,
   useFunction,
   sourceUseScope,
   maximalContinuousUseInterval>

The source participant is the source episteme and edition consumed. The receiving participant is the ontology-claim episteme and edition being formulated, constrained, tested, interpreted, compared, or traced.

For the Work participant, use A.13 to identify the performer and A.15.1 to admit the dated ontology-decision U.Work independently. If the case must also identify the assignment under which that Work was performed, F.6 checks the assignment used by A.13 and compares its holder with the already identified performer. The assignment relates the independently identified System to its assigned-kind value; that System performs the Work.

The minimal occurrence needs only those three participants, useFunction, sourceUseScope, and the maximal continuous interval during which the named Work consumes content from that source episteme for that receiving claim. Citation, access, bibliography membership, prestige, publication status, or co-location alone is insufficient.

If the Work consumes a separately identified claim or content episteme within the source, sourceContentSliceRef names that slice.

A different consumed source or receiving-claim edition, Work occurrence, function, scope, or maximal continuous use episode identifies another occurrence. Correcting knowledge of the same actual episode changes the assertion, not that occurrence. A changed optional qualifier identifies another occurrence only when it changes the direct use predicate; a later review record alone does not.

Add modelUseStructureRef only when one independently selected BoundedModelUseStructure changes interpretation of this use. Add source-content kind, currentness-result, published-decision, evidence-use, disposition or receiving-claim-change references only when the reconciliation asserts or consumes that item under its subject rule.

A blockedOverreadRef additionally requires F.19’s independent local ground, plausible intended-reader error and effect on truth, understanding or use; state only the smallest needed correction. A recorded unresolved disposition needs no fabricated blocked-overread episteme.

Record unchanged only when the Work reaches that result; an absent change disposition makes no claim.

A.7.2:4.4 - Identify source-use conflict without ranking traditions

OntologySourceUseConflictFinding@Context <: U.Episteme cites two or more source-use occurrences and states a conflict only when their content bears on the same receiving claim or same practical consequence in the same scope and their conclusions cannot jointly hold.

Different use functions are neither automatically comparable nor automatically insulated. Compare their content through direct evidence, formal-semantics, domain, scope, and currentness patterns. A finding can support adoption, adaptation, rejection, context split, non-composition, or unresolved return only with the counterexample, contradiction, proof consequence, or evidence relation that warrants it. “Stronger source” without claim-specific grounds is not a resolution.

A.7.2:4.5 - Stop and reopen

Stop with noConflictStop when the shared claim or consequence disappears after recovery. Stop with contextSplit or doNotCompose when that boundary truthfully protects the use. Stop unresolved only with the missing evidence basis or decision predicate and source and blocked use.

Reconsider affected uses when a source or receiving-claim edition changes, needed currentness changes, new domain or formal evidence bears on the same claim, a grounded blocked-overread issue becomes relevant, the consumed FPF decision changes, or later applications of repaired clauses yield incompatible same-scope consequences. Reopen only dependent source-use, application-result and receiving decisions; preserve results whose grounds remain unchanged.

A.7.2:5 - Archetypal Grounding

Compatible repair. The receiving claim asks whether a MaintenanceCoordinatorAssignment obtains for holder MaintenanceSystem-4 and assigned kind MaintenanceCoordinatorKind in scope S. Its independently admitted local rule requires a policy-valid assignment act and treats the signed organization chart as evidence only. The chart is present, but current facts establish that the required act did not occur.

One dated application of the local rule concludes that the relation does not obtain; another application of a chart-sufficiency clause concludes that it obtains for the same participants and scope.

Reconciliation Work recovers both result claims, their method clauses, source uses, and reasoning-basis uses of A7CP-01, A7CP-03, A7CP-05, and A7CP-06. It repairs the assignment clause to apply the local obtaining rule and use the chart as evidence for an assertion. Replaying both applications now yields the supported non-obtaining conclusion, without inventing an assignment occurrence. The result is reconciledCompatibility for that claim and scope.

If the evidence does not establish whether the required act occurred, reliance on the obtaining claim remains unresolved.

Under a different independently admitted rule, authorized signing may itself be the required act; establish that actual act instead of applying this case’s evidential-only rule.

A separate policy-valid act may create MaintenanceCommitment-17, borne by MaintenanceSystem-4; neither this commitment nor the assignment claim by itself establishes responsibility. Test any responsibility claim separately against its admitted maintenance-responsibility predicate, actual participants, applicability, and identity; if that governor is missing, return the missing governor.

Context split. One dated application uses a pattern’s ComponentOf clause for a pump assembly; another applies a maintenance-set pattern’s belongs-to rule to a candidate item. Both result claims say “part”, but their subjects, receiving claims, constructions, and consequences differ. The result is contextSplit; neither source clause nor application result defeats the other.

Non-convergence. Two dated method applications yield incompatible same-scope dependence claims, but available evidence and formal consequences warrant neither correction. If the receiving question is whether the outputs may be combined for an assurance use requiring compatibility, return doNotCompose for that use. If the receiving decision instead needs the unresolved premise settled, return unresolvedEscalation with the result claims, missing evidence basis or decision rule, its source and the reopen condition. Familiarity or institutional status settles neither question.

A.7.2:6 - Bias-Annotation

The dominant biases are prestige hierarchy, forced convergence, and formal-shape authority. The mitigations are claim-relative source-use occurrences, same-claim/same-consequence tests, direct evidence/currentness patterns, a smallest-decision repair, and truthful context-split/non-composition outcomes.

A.7.2:7 - Conformance Checklist

IDCheck
CC-A7.2-1The conflict names receiving claims, practical consequences, contexts, scopes, and current editions.
CC-A7.2-2Vocabulary difference or unlike source function alone does not trigger reconciliation.
CC-A7.2-3Keep the reader, pattern episteme, described Method and result distinct. Any MethodDescription claim satisfies A.3.2. For an asserted dated reconciliation Work, retain the independent A.13/A.15.1 basis in §0, including the separately admitted assignment species and obtaining occurrence used by A.13; add F.6 only for the precise attribution consumed. A short result may omit unused identifiers without presuming their facts.
CC-A7.2-4Every load-bearing common claim is cited from A.7.CP through a reasoning-basis occurrence.
CC-A7.2-5Every source-use occurrence has the three participants, source and receiving-claim editions, function, claim scope and maximal continuous actual-use interval. Corrected knowledge of that interval does not itself change occurrence identity. Include only qualifiers used or asserted in this reconciliation, with blocked-overread references satisfying §4.3’s F.19 conditions.
CC-A7.2-6Evidence, publication, formal semantics, and currentness remain with subject patterns.
CC-A7.2-7The repair reopens the smallest decision set and preserves unrelated FPF decisions.
CC-A7.2-8The result is one of the five declared dispositions with affected use and stop/reopen condition.
CC-A7.2-9Compatibility is demonstrated rather than assumed; context split and non-composition remain valid outcomes.

A.7.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Rank sources or traditions before naming the receiving claim.Recover source content, use function, scope, currentness, and consequence.
Rewrite a premise list while dated applications keep yielding conflicting results.Repair an established defect in the smallest affected method clause or subject-pattern decision, then check the application result. When the grounds warrant neither correction, use the non-convergence result under §4.2.
Force one ontology because shared terminology looks desirable.Permit contextSplit or doNotCompose when constructions or uses differ.
Treat citation, publication, or a completed review dossier as an obtaining source-use relation.Require consumption by dated decision work for one receiving claim; keep optional content-slice, model-use, currentness, evidence, and disposition records only when this reconciliation uses them.
Let a pattern, source, reader label, system-role kind, or assignment perform reconciliation.Name the capable practitioner or System performing the reconciliation. For an asserted dated Work occurrence, use A.13 and independent A.15.1 admission, retaining the assignment species and obtaining occurrence required by A.13; add F.6 only if the result needs precise assignment-bound attribution. Neither the kind nor the assignment acts.
Copy the common compact into this method.Cite A7CP-* claims; keep A.7.CP as the authoritative source for the claim content and relation definition.

A.7.2:9 - Consequences

The Method can establish compatible co-use, retain scoped alternatives, block composition for a named use, or return an unresolved decision with its reopen condition. Its cost is recovering the source, receiving claim and application facts, including currentness where it affects the comparison. That work is justified by a material conflict and stops at the sufficient scoped result.

A.7.2:10 - Rationale

The receiving claim supplies the adjudication question. This keeps source kind, currentness, evidence use, local use function, disposition, and claim change orthogonal. Repairing the smallest method decision preserves corpus stability, while non-convergence outcomes prevent a neat vocabulary from overruling absent evidence.

Repair the smallest foundation conflict; do not manufacture one foundation.

A.7.2:11 - SoTA-Echoing

Practice questionSource contributionFPF alignmentDisposition
Do unlike formal modalities or calculi share one world semantics?Typed proof traditions preserve operator and inference behavior (Rijke, Shulman & Spitters 2020; Acclavio, Catta & Straßburger 2021).Formal source use is one local function; representation or notation cannot settle the receiving ontology claim by form. The non-convergence case retains direct formal patterns.Adopt as formal comparator. FPF does not import either calculus as universal ontology.
Do different ontology questions warrant different comparisons?Keet & Khan 2024 distinguish competency-question purposes and products.Reconciliation starts from one receiving claim and practical consequence instead of comparing whole source traditions.Adapt. No mandatory question taxonomy or artifact is imported.
Can modal expression, object, scope, and satisfier be collapsed?Moltmann 2024 separates modal expression, object, scope, weak/strong permission, and action satisfiers.The method compares claim contents and constructive consequences instead of vocabulary labels; direct permission patterns retain their semantics.Adapt as a consequence-sensitive source use. No modal-object or truthmaker U-kind is imported.
Do capability claims require more than possibility wording?Toyoshima et al. 2022 retain bearer and realization conditions in applied-ontology capability accounts.A source can test one receiving capability claim while A.2.2 remains the FPF subject pattern.Comparator only. The external hierarchy is not imported.

A source contributes through its content and the receiving claim. A newer publication alone does not reopen unrelated FPF decisions.

A.7.2:12 - Relations

  • Coordinates with: A.7.1. A.7.2 is neither its parent nor child; it handles material cross-pattern premise conflict and can return repaired subject-pattern decisions to it.
  • Consumes: claim contents from A.7.CP through ClaimUsedAsReasoningBasisRelation@Context occurrences; it does not copy or own the compact. Pattern epistemes and U.MethodDescription epistemes supply clauses or declared premises; their described Methods remain distinct, while dated application Work and its separately governed result claims supply the reconciliation inputs.
  • Defines: OntologyClaimSourceUseRelation@Context and OntologySourceUseConflictFinding@Context for bounded ontology-decision and reconciliation source use only.
  • Coordinates with: A.10 for evidence use, G.11 for currentness, C.29 and direct formal patterns for formal semantics, C.2.1 for source epistemes, E.24.PUB for publication-occurrence, form, and carrier questions, E.17 for multi-view publication, and subject patterns for the receiving ontology claim.
  • Preserves: current published FPF decisions as an internal basis, with grounded, claim-specific reconsideration. Use E.9.DA review or DRR discharge when that separately governed question is current.
  • Does not define: a universal source-authority kind, source role, prestige ranking, evidence relation, publication relation, or source-currentness relation.

A.7.2:End

A.7.CP - Constructive-Premise Compact and Reasoning-Basis Use

Type: Architectural (A) Status: Stable Normativity: Normative

A.7.CP:0 - Use this when

Use this pattern when reasoning, ontology analysis, choice, or reconciliation relies on a broad constructive claim and another reader must be able to recover which claim, receiving claim or result, posture, scope, work occurrence, and interval carried that reliance.

The first useful move is to name the dated reasoning work, each claim-bearing result or receiving decision it is forming, the A7CP-* claim IDs used for that result, and whether each use is an adoptedPremise or conditionalAssumption. Leave the other compact claims latent.

Not this pattern when. Use the relevant subject pattern for citation, publication, shared vocabulary, ordinary A.7 category-error repair, source currentness, or domain/evidence questions when no compact claim is used in reasoning. No reasoning-basis occurrence obtains in that case.

The primary reader is an author or reviewer who must make one load-bearing constructive premise use recoverable. The object is one ClaimUsedAsReasoningBasisRelation@Context occurrence and the compact claim content it cites.

A.7.CP:1 - Problem frame

Dated work applying an FPF method can rely on broad claims such as “a publication does not create world-side obtaining” or “a MethodDescription episteme does not perform Work”. A U.MethodDescription episteme may state or cite one of those claims as a declared premise or branch condition for its described U.Method.

ClaimUsedAsReasoningBasisRelation@Context obtains only when one inference, comparison, or choice in dated Work relies on that claim for the receiving result.

Copying the claim into every method description makes it drift; leaving the dated reliance implicit hides whether a result used an adopted premise, a conditional branch, or no common claim at all.

The compact publishes twelve stable claim contents once. A U.MethodDescription episteme can declare an intrinsic premise or a branch condition for its described Method; a dated application records only the compact claims used in its reasoning. Ordinary Work therefore does not acquire a foundation checklist.

A.7.CP:2 - Problem

Three conflations make premise use unreliable:

  1. claim content is confused with the posture in which one work occurrence uses it;
  2. citation or co-location is confused with reliance in reasoning; and
  3. a support pattern is treated as a method that performs or governs the consuming work.

The result is either hidden premises or a copied catalogue that becomes a second ontology authority. Both failures obscure occurrence identity and reopen behavior.

A.7.CP:3 - Forces

ForceTension
Stable claims vs local useClaim content should be durable, while posture, work, context, and interval vary per use.
Recoverability vs cheap first useLoad-bearing use needs a trace; ordinary method use should not traverse twelve claims.
Shared support vs subject rulesCommon claims coordinate patterns while evidence, currentness, construction, Work and kind admission keep their own rules.
Adopted premise vs conditional assumptionBoth can support reasoning, but their defeaters and reopen conditions differ.
Reuse vs copied variantsOne authoritative source avoids divergent copies; consumers still need locally intelligible action guidance.

A.7.CP:4 - Solution

A.7.CP:4.1 - Publish the compact once

The compact carries these stable claim contents:

  1. A7CP-01 Existence and obtaining. World-side obtaining is not created by a claim, database row, predicate, or publication merely representing it.

  2. A7CP-02 Constructive settlement. When identity, constitution, dependence, or obtaining changes a consequence, name the construction or direct governing relation that grounds it; a reconstructible trace is not itself the world construction.

  3. A7CP-03 Constitution and social objects. Constituting acts, admitted systems, and the relations they institute remain distinct from descriptions of those acts and relations.

  4. A7CP-04 Epistemic openness and fallibility. Evidence and reliance may remain unresolved without turning unresolved evidence into a third world-side obtaining mode.

  5. A7CP-05 Representation boundary. Descriptions, logical forms, database rows, graphs, and publications represent or carry claims under their applicable relations; their form alone does not establish the truth of their world-side claims.

  6. A7CP-06 Agency and work attribution. A U.MethodDescription episteme describes an admitted U.Method; for a performed-Work claim, recover each performer through A.13 and let A.15.1 independently admit the dated U.Work.

    Only when the claim or its receiving use expressly consumes precise assignment-bound attribution does F.6 separately relate that Work to the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer, neither the system-role kind nor the assignment acts, and missing or failed attribution alone leaves independently admitted Work intact.

    Recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1. A result follows only through its own separately established relation—for example, a production, operation-result, measurement, evaluation, decision, delivery, or acceptance relation—not from Work in general.

  7. A7CP-07 Kind discipline. Use direct existing kinds and local admission before proposing a universal kind, root relation, or role-like surrogate.

  8. A7CP-08 Scoped pluralism. Different source traditions or apparatuses may be useful for different receiving claims; compatibility is tested by consequences, not achieved through prestige hierarchy.

  9. A7CP-09 Structure and wholeness. A description of structure is not the structure; not every construction is mereology, and C.13 alone defines constructional mereology.

  10. A7CP-10 Time, identity, and currentness. World-side temporal qualification, occurrence identity, claim/publication currentness, and source supersession are separate questions.

  11. A7CP-11 Subject-pattern separation. Capability, state, architecture, role, method, work, evidence, permission, and relation families retain their subject patterns even when an ontology method diagnoses a conflict among them.

  12. A7CP-12 Formal projection non-reversal. CT2R and formalization may preserve, collapse, or omit structure. Logical validity or representation form alone establishes no unique world construction.

The twelve IDs form a stable closed compact in this pattern. They are not steps, completeness criteria for every ontology use, or twelve intrinsic premise kinds.

A.7.CP:4.2 - Record reasoning-basis use

Premise and assumption name postures of claim use, not disjoint claim kinds.

ClaimUsedAsReasoningBasisRelation@Context <: U.Relation

RelationSignature:
  BasisClaimSlot:
    SlotKind: BasisClaimSlot
    ValueKind: U.Episteme
    refMode: U.EpistemeRef
  ReasoningWorkSlot:
    SlotKind: ReasoningWorkSlot
    ValueKind: U.Work
    refMode: WorkRef
  ReceivingReasoningResultSlot:
    SlotKind: ReceivingReasoningResultSlot
    ValueKind: U.Episteme
    refMode: U.EpistemeRef

semanticDirection: BasisClaimSlot -> ReceivingReasoningResultSlot
  through the named ReasoningWorkSlot
ReasoningBasisPostureValue ::= adoptedPremise | conditionalAssumption

RelationOccurrenceQualifiers:
  basisClaimAddress: ClaimAddress
  posture: ReasoningBasisPostureValue
  reasoningUseScope?: U.ClaimScope
  modelUseStructureRef?: SelectedStructureReference

OccurrenceIdentity:
  <basis-claim edition and claim ID,
   reasoning-work occurrence,
   receiving-result edition,
   posture,
   reasoningUseScope when present,
   maximalContinuousRelianceInterval>

BasisClaimSlot is the claim-bearing episteme used, and basisClaimAddress is a C.2.1 ClaimAddress selecting the claim inside that same edition by its intrinsic ClaimGraph identity. ReasoningWorkSlot is the dated reasoning, choice, ontology-analysis, or reconciliation U.Work that relies on it. ReceivingReasoningResultSlot is the claim, comparison, decision, or other claim-bearing result episteme whose content that Work forms or revises using the basis claim. If the practical result is world-side, use the direct result claim that bears on it; the world-side object retains its subject pattern.

Use A.13 to identify the admitted U.System that performs the Work and retain the obtaining occurrence of the separately declared U.SystemRoleAssignment species used by A.13. Independently admit the dated Work under A.15.1. Recover the obtaining F.6 attribution for that Work-assignment pair only when the claim or its receiving use expressly consumes assignment-bound attribution; the assignment holder must be the same System. The assignment’s existence, holder, or interval does not establish that attribution; the independently identified System performs the Work.

Claim episteme, described Method when one is used, Work occurrence, assignment occurrence, attribution, use posture, receiving result, and any world-side result remain distinct. The words “premise” and “assumption” are not relation participants.

The relation obtains during the maximal continuous interval in which the named work relies on the basis claim to form or revise the receiving result. Access, citation, publication, co-location, or use of the claim elsewhere in the same work is insufficient.

reasoningUseScope appears only when this premise use is narrower than or otherwise differs from the receiving result’s declared claim scope; modelUseStructureRef appears only when an independently selected BoundedModelUseStructure changes interpretation. Source currentness, evidence, publication, work method, and the receiving result’s own governance remain with their subject patterns.

One occurrence is identified by the basis-claim edition and ID, reasoning-work occurrence, receiving-result edition, posture, optional narrower use scope, and maximal continuous reliance interval. If one Work uses the same basis claim for two independent results, record two relation occurrences that share the Work participant but name different receiving results; do not duplicate the Work. An actual change to any of these identity values identifies a different or later result-specific occurrence. Correcting a later assertion about the same historical use does not itself change that occurrence.

A.7.CP:4.3 - Keep posture and transition explicit

adoptedPremise means the named work presently uses the basis claim as accepted support for the receiving result. conditionalAssumption means the work uses it for that result only in a narrower model, scenario, proof, or branch with an explicit test, defeater, or reopen condition. Every conditional assumption used can function as a premise inside that bounded subargument; not every adopted premise is conditional. Neither posture changes the basis-claim episteme’s intrinsic kind.

The same claim can have different postures in different Work or for different receiving results of one Work. An actual posture transition creates a later occurrence for the affected receiving result. Reconsider that result and its dependents; another result remains reusable when its own premise use and all other consumed grounds remain unchanged.

A.7.CP:4.4 - Use the cheapest truthful path

  1. Name the reasoning work and each receiving claim, decision, comparison, or other claim-bearing result it is forming.
  2. For each receiving result, cite only the compact IDs that are load-bearing.
  3. Record one relation occurrence per basis claim, receiving result, posture, and continuous reliance interval; reuse the same work reference across independent results.
  4. Name a narrower U.ClaimScope or selected BoundedModelUseStructure only when it changes this premise use.
  5. Keep evidence, currentness, source use, kind admission, subject construction, work method, and result governance with their subject patterns.
  6. Stop when every load-bearing receiving result points to its premise-use occurrences. Do not inspect unused compact entries.

A.7.CP:5 - Archetypal Grounding

Relation-occurrence inquiry. Ontology-analysis work returns SupportOccurrenceInquiryDecision-17: the receiving claim requires an occurrence distinction, but the applicable subject rule does not yet establish whether removal and reinstallation identify one occurrence or two. The result relies on A7CP-01 and A7CP-10 to keep the represented relation, its obtaining, occurrence identity, and currentness separate; it returns the missing subject rule instead of inventing that rule. Two reasoning-basis occurrences name the same work and receiving result but different basis claims. The other ten claims stay latent.

Role/chart reconciliation. Reconciliation work returns AssignmentConstitutionDecision-42, which distinguishes assignment constitution from a chart that evidences the assignment. Four result-specific relation occurrences connect that decision to A7CP-01, A7CP-03, A7CP-05, and A7CP-06. Source-use and evidence relations stay under their subject patterns.

Same-work selective reopen. ReasoningWork-19 returns WarrantyClaimAnalysis-19 and AlternativeOntologyComparison-19. Each has its own relation occurrence to A7CP-10.

The warranty analysis uses that claim as an adopted premise. The comparison uses it only as a conditional assumption in a named branch separating temporal qualification, occurrence identity and currentness.

If the comparison later adopts that separation as an accepted basis, its changed posture and revised result receive a later reasoning-basis occurrence. Reopen the comparison result and its dependents. In this case, the warranty analysis does not depend on that comparison and its other grounds are unchanged, so its earlier result and premise use remain reusable.

No compact use. Missing telemetry blocks a state claim while the relevant state and evidence distinctions are already clear. Work returns to measurement/evidence. No compact claim is load-bearing, so no reasoning-basis occurrence is created.

A.7.CP:6 - Bias-Annotation

The main biases are foundation maximalism, premise-kind inflation, and trace-by-citation. The mitigation is one compact publication source, claim IDs, two context-local postures, work participation, and a non-use rule that keeps ordinary reasoning cheap.

A.7.CP:7 - Conformance Checklist

IDCheck
CC-A7CP-1Every relation occurrence names one basis-claim episteme/ID, dated reasoning-work occurrence, receiving-result episteme, posture, optional narrower use scope, and maximal continuous reliance interval.
CC-A7CP-2The work relies on the claim for that receiving result; citation, access, publication, or use elsewhere in the work is insufficient.
CC-A7CP-3adoptedPremise and conditionalAssumption are use postures, not intrinsic claim kinds.
CC-A7CP-4An actual change of posture or another occurrence-identity value identifies a different or later result-specific occurrence and reopens that result and its dependents. Correcting knowledge of a historical use changes the assertion, not the occurrence; reuse other results only when their consumed grounds remain unchanged.
CC-A7CP-5Consumers cite only load-bearing claim IDs and do not copy the compact.
CC-A7CP-6The support pattern is not a Method, performer, work plan, result, or mandatory catalogue traversal. A U.MethodDescription episteme may declare a premise or branch condition for its described Method, but only an admitted U.System performs dated reasoning Work. Any assignment, F.6 attribution, and result relation used by the case must obtain separately.
CC-A7CP-7Evidence, currentness, source use, subject construction, kind admission, and work method remain with subject patterns.
CC-A7CP-8The twelve compact claims retain their stable IDs and contents as one closed support set.

A.7.CP:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
Require every ontology use to check all twelve claims.Cite only load-bearing claims; unused entries remain latent.
Treat a citation or work-wide claim use as a premise-use occurrence for every result.Name the dated work, receiving result, and inference or comparison that relies on the basis claim; use separate relation occurrences for independent results.
Define “premise” and “assumption” as separate episteme kinds.Keep one claim episteme and record the context-local posture.
Let the compact, a MethodDescription episteme, its described Method, a system-role kind, or an assignment perform the consuming Work or bring about its result.Name the admitted U.System that performs the dated reasoning U.Work and retain the assignment species and obtaining occurrence used by A.13. When the claim or its receiving use expressly consumes assignment-bound attribution, name the obtaining F.6 attribution for that Work-assignment pair. State any result only through the direct result relation that the case independently establishes.
Copy the compact into A.7, A.7.1, or A.7.2.Keep one authoritative source and use claim-ID references.
Hide evidence or currentness inside the relation.Cite direct evidence/currentness results without turning them into relation fields.

A.7.CP:9 - Consequences

The compact makes consequential constructive reliance recoverable from one claim source. Ordinary use requires no traversal of unused claims. For a load-bearing use that another reader must recover, identify the basis claim, Work, receiving result and posture. That account supports reconsidering only results that depend on a changed ground.

A.7.CP:10 - Rationale

Claim content and reasoning posture vary independently. One source for the content and a separate relation for its use let readers recover both without treating premise and assumption as different claim kinds. The System performs the reasoning Work; the episteme supplies the claim on which that Work relies.

Use only the premise the work relies on.

A.7.CP:11 - SoTA-Echoing

Practice questionSource contributionFPF alignmentDisposition
Can exact claim content be reduced to possible-world equivalence?Fine 2017 argues for exact truthmaker content beyond coarse modal equivalence.Compact claims retain contents and IDs; FPF does not merge them into one modality field.Comparator only. No truthmaker ontology is imported.
How should formal claims preserve typed behavior?Homotopy type theory and related typed proof practice preserve exact proposition/type roles (Rijke, Shulman & Spitters 2020).Reasoning-basis use cites a claim episteme and does not infer world ontology from formal form.Adapt as formal comparator. Direct formal patterns keep proof semantics.
Do bearer and realization distinctions matter for capability claims?Applied-ontology capability work retains bearer and realization conditions (Toyoshima et al. 2022).A7CP-11 keeps capability claims under A.2.2 rather than importing a compact capability ontology.Comparator only. The external hierarchy is not imported.
Do weak permission, strong permission, and action satisfiers have the same content?Moltmann 2024 distinguishes those contents and their use.A7CP-11 protects direct permission patterns; claim IDs can support analysis without becoming permission objects.Adapt as separation pressure. No modal-object U-kind is added.

A.7.CP:12 - Relations

  • Defines: the twelve A7CP-* constructive claim contents and ClaimUsedAsReasoningBasisRelation@Context, whose direct result-specific edge states that dated reasoning work used one basis claim to form or revise one receiving result episteme.
  • Is consumed by: dated Work applying the Methods described by A.7.1 or A.7.2, which cites compact claims and exposes relation occurrences only for load-bearing reliance. Their procedural epistemes may separately declare premises or branch conditions; any MethodDescription membership satisfies A.3.2. Neither a MethodDescription nor a Method is a participant of ClaimUsedAsReasoningBasisRelation@Context.
  • Coordinates with: A.7 for the object and relation distinctions needed by the receiving claim.
  • Retains subject rules: A.10 and G.11 govern evidence/currentness; E.24/E.24.UK govern applicable pattern/U-kind admissions; subject construction patterns govern constructive settlement; A.7.2 governs ontology source-use relations.
  • Does not define: a premise method, source authority, evidence relation, work plan, performer kind, common realism checklist, or universal foundation ontology.

A.7.CP:End

A.8 - Universal Core Principle: Test a U-Kind Across Domains

Type: Kernel admission discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

A.8:0 - Use This When

Use this pattern when a candidate durable U-kind is proposed as a kernel-level universal primitive rather than as a local concept, C.3 U.Kind, direct subject-pattern value, Concept-Set row, slot, relation, record, publication form, or dependent durable value.

What goes wrong if missed. A local domain noun enters the kernel as if it were universal, or a universal primitive is rejected because its domain projections use different words.

What this buys. Kernel admission becomes a falsifiable cross-domain claim: the candidate must keep the same abstract contribution across diverse domain families while losses and local differences stay visible.

Typical moments:

  • a candidate U-kind is proposed because several domains use similar words;
  • a local subject value starts being treated as universal because it is useful in one field;
  • a new U-kind proposal includes a universal-core claim, or an already admitted kind is being considered for kernel placement;
  • source or draft type wording claims kernel-level status and must be recovered into current U-kind governance.

Primary EntityOfConcern. The universal-core admission claim for one candidate U-kind.

First useful move. Recover the candidate and its proposed membership or identity rule through E.24.UK. If kernel-level status is claimed, test whether it makes the same abstract contribution in at least three foundationally different domain families. Use the applicable accepted admission result for an already admitted kind; a new proposal supplies the shared decision’s independently recovered candidate inputs.

Not this pattern when.

  • If the issue is C.3 typed claim quantification, use C.3 and C.3.1.
  • If the issue is whether the public U.* spelling should survive at all, use E.24.UK.
  • If the candidate can be expressed by composition, dependent value, slot relation, or direct subject pattern, use A.11 and the direct pattern before A.8.

A.8:1 - Problem Frame

FPF needs universal primitives while keeping domain-specific concepts outside the kernel. A term used in software, finance, biology or physics may still name a local kind. A kernel-level U-kind must retain its defined contribution when applied across the foundational domains in its claimed scope.

When source wording proposes a kernel-level U-kind, recover its admission claim: E.24.UK decides durable U-kind admission basis, and A.8 tests the universal-core claim.

A.8:2 - Problem

Without A.8:

  1. Parochial drift. A local domain concept enters the kernel and later cracks outside its home domain.
  2. Kernel bloat. Near-universal values accumulate because each domain asks for its own core noun.
  3. False universality. Search frequency, source prestige, or familiar spelling replaces cross-domain evidence.
  4. C.3 confusion. A context-local U.Kind is mistaken for a universal FPF U-kind.

A.8:2.1 - Forces

ForceTension
Universality vs parsimonyFPF needs a small kernel, but some concepts carry the same modeling work across domains.
Domain familiarity vs abstract contributionFamiliar words and prestigious sources can hide that the candidate only works in one tradition.
Same word vs same workDifferent domains may use different words for the same abstract contribution, and the same word may name different local objects.
Stable kernel vs evolving FPFA kernel primitive must survive new pattern families without forcing every local distinction into U-kind status.

A.8:3 - Solution

Recover the basis for the three-domain falsification test through E.24.UK:

  • Already admitted kind. Use its applicable accepted admission result and the candidate facts it establishes. Reconsider kernel placement at the claimed scope; an unchanged, still-applicable admission does not need to be repeated.

  • New admission proposal. Use the independent candidate inputs of the shared decision in E.24:4.0a: governed individuals, proposed membership or identity rule, intended extent, nearest non-member and receiving use.

    Complete the A.8 test alongside the other applicable admission tests, before E.24.UK closes the decision. The projections provide evidence for the core-placement claim; the complete E.24.UK test decides admission.

In either case, the candidate description and the domain evidence must support the comparison independently of the conclusion being sought.

The candidate passes A.8 only when all four conditions hold:

  1. Distinct domain families. At least three projections come from foundationally different domain families.
  2. Same abstract contribution. Each projection shows the same kernel contribution, not merely a similar word.
  3. Non-trivial diversity. Each projection supplies a distinct test of the contribution, with facts or correspondence evidence not subsumed by the other projections.
  4. Recorded losses. Differences, losses and comparison risks are visible enough to distinguish the shared contribution from local conditions. An F.9 Bridge is needed only for the semantic-correspondence claim governed by that pattern.

Use the following fields to make each projection inspectable. Equivalent prose or a shared table is sufficient when it preserves these values:

UniversalCoreProjection:
  CandidateUKind:
  UKindAdmissionResultRef: accepted E.24.UK output, when available; follow it to the shared decision only when common inputs or decision mode are needed.
  DomainFamily:
  DomainTerm:
  LocalEoC:
  SameAbstractContribution:
  DifferenceOrLoss:
  EvidenceRef:

For a new proposal, CandidateUKind identifies the candidate under consideration. Keep its projection findings with the shared decision’s ClaimGraph. Supply UKindAdmissionResultRef when an applicable accepted result exists; a pending decision reference is not an accepted-result reference. The other projection values can be supplied and tested before that result exists.

At least three supported projections are required. Try to defeat the proposed universal-core claim: a supported counterexample within its claimed scope refutes that form of the claim. A misidentified local object or invalid projection first needs correction. Three successful cases support this admission test; they do not prove universality over every future case.

A.8:3.1 - Archetypal Grounding - Diversity Evidence

Test one proposed contribution across different domain families. If it fails a valid projection, reconsider the proposed core claim. Any local, dependent or subject-constrained use of the content still needs the conditions supplied by E.24.UK, A.11 and the defining subject rule.

Candidate under testDomain-family projectionsWhat must stay the sameWhat may differ
U.Systemthermodynamic control volume; biological cell or organism; cyber-physical systemphysically embodied acting holon satisfying all six constructive components and the applicable kind-specific condition in A.1:4.2–4.3boundary physics, substrate, observability, and control style
U.Epistemetheorem or proof text; clinical guideline; model card or safety caseclaim-bearing non-agentive knowledge object that can be used, cited, revised, or publishedcarrier, notation, authority source, and assurance regime
U.Workmachining run; lab assay; review or approval actdated performed occurrence: use the complete A.15.1 admission, including A.1:4.2’s six common constructive components, A.13’s actual-performer basis, grounded performance history, enacted Method and extent, and facts establishing containment of the complete occurrence under a declared System boundary; F.6 adds an assignment check only when the current use must also say under which assignment the Work was performedphysical medium, institutional form, measurement trace, and evidence carrier

These rows identify candidate comparisons, not completed admissions. Each needs an E.24.UK basis, projection evidence and stated differences or losses.

Worked projection and counterexample. Consider an illustrative U.Episteme core claim, with an accepted E.24.UK admission result already available. The receiving team must decide whether one claim-bearing, non-agentive kind can cover mathematical, clinical-research and engineering knowledge objects. Assume the three source epistemes below are independently identified under C.2.1; their stated content is the evidence for this projection exercise.

Domain family and sourceLocal EntityOfConcern, claim and effective schemePreserved contribution and local limit
Mathematics: Theorem-e1Integer addition; 2 + 2 = 4 under its arithmetic scheme, with a derivation as warrant and no experimental verification.A non-acting episteme bears a claim about its subject. Mathematical derivation supplies this claim’s warrant.
Clinical research: StudyReport-e2Study S; its report states that 12 of 100 observed cases met outcome criterion O in population P under observation scheme Q.The same claim-bearing contribution remains; empirical design, measurements and population limits govern this claim’s warrant.
Engineering: Assessment-e3Pump P; the assessment reports 10 L/min at 100 kPa and conformity to R, which requires at least 8 L/min under those same conditions.The same contribution remains; measurement conditions and the acceptance rule govern this claim’s use.

The three cases test distinct warrant and application conditions while preserving the proposed contribution. The comparison retains the derivation, population boundary and acceptance rule locally; it transfers none of them into a universal assurance rule. Under the stipulated evidence, it supports the claim-bearing U.Episteme contribution in this A.8 test.

Now strengthen the proposed core definition to “every episteme is experimentally verified.” The mathematical case supplies a counterexample within the intended scope: its warrant is derivation, not an experiment. Reject that stronger core claim, retain the supported contribution, and keep experimental verification under the subject and evidence rules that require it. A new counterexample reopens the affected universality claim and uses that depend on it; independently supported claims remain reusable.

First-admission replay. Stipulate a proposed edition in which this claim-bearing kind has no accepted admission result. Its candidate description and the independently identified source objects, claims and schemes above supply inputs to the shared E.24 decision. The same projection test can establish the supported core contribution from those inputs. Keep that finding in the decision while the other admission conditions are examined.

If the required by-value dependence of downstream uses remains unsupported, admission remains unresolved despite the successful projections. After all conditions for the selected positive form pass, the accepted E.24.UK result supplies UKindAdmissionResultRef and naming can proceed. The existing-kind example instead consumes its already applicable result.

Record domain-family coverage, each distinct test, and the differences or losses needed to assess the comparison. Quality-diversity telemetry such as Diversity_P or IlluminationSummary can contribute only under its governing C.17, C.19 or direct rule; it does not itself admit a U-kind or establish the projection.

A.8:3.2 - Bias-Annotation

A.8 resists kernel growth based on familiar names because downstream patterns may rely on each admitted primitive. The three-domain test also resists rejection based only on different spellings: compare the contribution and retain differences and losses.

A.8:4 - Conformance Checklist

CheckRequirement
CC-A8-1The test uses the applicable accepted E.24.UK result for an already admitted kind, or the independent shared-decision candidate inputs for a new proposal. UKindAdmissionResultRef identifies only an accepted result. A new proposal completes the other applicable admission conditions before admission.
CC-A8-2The A.8 claim is kernel-level universal-core admission, not C.3 typed reasoning.
CC-A8-3At least three domain-family projections are recorded.
CC-A8-4Each valid projection tests the same abstract contribution and contributes distinct evidence; repair a misidentified object or invalid projection before judging the candidate. Successful cases support the test rather than proving all future applications.
CC-A8-5Differences and losses are explicit; same-word evidence alone is insufficient.
CC-A8-6A failed A.8 test does not support the proposed universal-core claim. Reconsider local use, a dependent value, a Concept-Set row, C.3 U.Kind, or a subject-pattern expression under E.24.UK, A.11 and the defining subject rule; select an alternative only when its own conditions hold. Rejection or an unresolved proposal remains possible.

A.8:4.1 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsCorrect action
Same-word admissionA term is admitted because many domains use the same word.Require three domain-family projection records that show the same abstract contribution.
Prestige admissionA famous source or standard is treated as universal-core evidence by itself.Record how the candidate is used in multiple domain families and state difference and loss.
Local success as kernel statusA local pattern works well and is therefore promoted to universal primitive.Try dependent value, Concept-Set row, C.3 U.Kind, or direct subject-pattern value first.
False demotion by vocabulary mismatchA universal candidate is rejected because domains use different names.Compare abstract contribution, not spelling. After the ontic test, use F.18 for naming and F.9 only for a remaining cross-local semantic-correspondence claim.

A.8:4.2 - Consequences

A passed A.8 test strengthens the case for kernel placement but does not bypass E.24.UK admission predicates, A.11 parsimony, or the subject assertion. A failed test does not support the proposed universal-core claim. Reconsider the useful content under E.24.UK, A.11 and the defining subject rule; a local, dependent, or subject-constrained alternative needs its own basis. The failed placement test does not invalidate an independently established admission. The cost is evidence work across at least three domain families.

A.8:4.3 - Rationale

Universal core primitives are expensive because every downstream pattern can rely on them. A.8 therefore treats universality as a claim about repeated abstract contribution across different foundational domains, not as a claim about lexical frequency, popularity, or early convenience.

A.8:4.4 - SoTA-Echoing

The design combines the separation of upper-level commitments from domain concepts, comparison across heterogeneous cases, and treatment of diversity. A.8 uses them as an FPF admission test: identify the same contribution, preserve local conditions, and seek a counterexample. The minimum of three domain families is this pattern’s admission rule, not a logical proof of universality. C.17/C.19 govern any quality-diversity telemetry used as evidence.

A.8:5 - Relations

  • Builds on: E.24.UK, A.11, C.3, C.3.1, F.8, and F.18.

  • Coordinates with: Concept-Set and F.18 for naming domain-family projections after the ontic question is settled.

    Use F.9 only for a cross-local semantic-correspondence claim in comparison, naming or translation: resolve two F.17 SchemeSenseCell values with different semantic-context projections and test the F.9 predicate under its profile, applicability and dependency conditions. State any proposed use of an obtaining Bridge in a separate bounded-use claim. Ordinary designation or an already shared meaning follows its direct rule.

  • Does not replace: E.24.UK for U-kind admission, A.11 for parsimony, or C.3 for typed claim quantification.

A.8:End

A.9 - Choose and Check an Aggregation Law for the Intended Result

Status: Stable

A.9:1 - Context

Use this when a receiving decision needs a combined result, but the law that gives the proposed operation its meaning or preserves a needed property is unresolved. The same input values can support different operations: component success probabilities combine differently for “both succeed” and “at least one succeeds”. Reordering functions can change their result even when the notation looks like an ordinary fold.

The first useful result is a justified combining law with its applicable conditions, a supported limited result or bound, retained separate inputs, or the missing premise. Reuse an adequate domain law and its current applicability result without creating another A.9 record.

Non-use boundary. B.1 governs whole/part construction, C.29 governs mathematical representation and correspondence, and ULSAM performs an explicitly selected CHR fold over admitted measures. None supplies one universal aggregation algebra. Use their results when they already answer the question; A.9 supplies only the unresolved law-selection or property check. Composition of functions or Methods does not require a measured quantity merely to enter this pattern.

A.9:2 - Problem

FailurePractical consequence
An operation is chosen from the numbers alone.A sum, minimum or product answers a different question from the one the receiver needs.
A roll-up hides dependence, overlap or interaction.Repeated evidence is counted as independent, or component claims are promoted to an unsupported whole claim.
Reordering or repartitioning is assumed harmless.Ordered Methods or numerical computation return a different result.
Failure of an aggregation model is treated as a new whole.A repairable model premise is confused with the independent identity question.

A.9:3 - Forces

ForceTension
Simple operation, faithful meaningA compact formula must still express the intended result under the subject model.
Reuse, changed conditionsRetain a justified law while reopening the dependence or applicability premise that changed.
Local work, combined resultParallel or separate computation helps only when its recombination preserves what the receiving use needs.
Useful answer, incomplete basisA bound or separate inputs can be a better answer than an unsupported scalar.

A.9:4 - Solution — Select the Law Before Relying on Its Result

  1. Name the intended result and operands. State what the combination must mean, which inputs contribute and what operation is proposed. For reliability, distinguish joint success from alternative success. For a composed Method or function, retain the intended order and participant meanings.
  2. Recover the subject model and conditions. Identify dependence, overlap, interaction, grouping and numerical interpretation where they change the result. For quantities, also recover the Characteristic, Scale and any applicable units. Recover measurement conditions when measured values are used. Use C.29 when the representation or its correspondence to the subject is unresolved; mathematical notation alone is not that correspondence.
  3. Select a justified law. Use the domain source or Method that supports this operation for this result. Reuse its current applicability judgment when adequate. If no available law is justified, name the missing model or condition; do not pick a convenient average or a generic weakest-part rule.
  4. Check the property needed by the current action. A requested reorder needs an order-invariance claim; a repartition needs valid decomposition and recombination; a bound needs the model that warrants it. For a numerical reproducibility claim, state whether the use requires the same exact value, the same bits, or an error bound before accepting a regrouping. Use the applicable argument or warranted test under those conditions. The table below supplies possible questions, not a compulsory set of five checks.
  5. Return the warranted answer and limit. Apply the justified law, or return a supported bound, separate inputs or the missing/defeated premise. If a condition changes, withdraw only the conclusion that depended on it and recover the needed model. Pass a CHR measure fold to ULSAM when that mechanism use is current. Use B.3 only for a receiving claim that requires assurance.

Describing the choice does not perform the fold, establish parthood or authorize reliance. No additional record is needed when the law, inputs, conditions and answer are already recoverable in the working account.

A.9:4.1 - Select Only the Relevant Property

Property or legacy codeQuestion and applicability
Singleton base case — IDEMIf the construction has this requirement, does a one-element input return the corresponding element? This differs from algebraic idempotence x ⊕ x = x. Repeated sources need their own dependence treatment.
Reordering — COMMDoes exchanging the operands preserve the intended result under the operation and model? Keep order when it is consequential. Commutativity alone does not establish independence of the observations.
Repartitioning or moving computation — LOCDo the declared decomposition, recombination and numerical conditions preserve the required result? Exact arithmetic and floating-point implementations may answer differently.
Weakest-part bound — WLNKDoes the specified result and dependency model justify this bound? A bound need not be the exact result, and it is not a cap on every aggregate.
Monotonicity — MONOUnder which input/output order and side conditions can improving an input not worsen the result? Interactions can defeat the proposed claim.

A layered-control contract may state a reference signal, guaranteed tracking error and cycle time. Check the needed composition property under its control model. Possessing that contract alone proves neither reordering nor repartitioning valid.

A.9:4.2 - Keep Whole Reidentification Separate

If observations defeat a law’s premise, reopen the model, applicability conditions and resulting claim. B.2 is needed only when the current question also concerns whether the existing whole still satisfies its identity rule. A failed aggregation model alone neither identifies a new whole nor establishes a Meta-Holon Transition.

A.9:5 - Archetypal Grounding

These six cases are constructed model checks, not empirical performance reports. Read each row from the intended result through its model to the warranted answer.

Intended result and stated modelSelected law, result and limit
Total of disjoint exact resource contributions 2 and 3 on one additive quantity scaleAddition gives 2 + 3 = 5 under B.1.6. No weakest-part cap applies to this total; exceeding either part creates no new whole.
Probability that both independent components succeed, with probabilities .9 and .8The joint-success model selects multiplication: .9 × .8 = .72. A minimum would not calculate that probability.
Probability that at least one of those same independent components succeedsThe alternative-success model selects 1 - (1-.9)(1-.8) = .98. Identical marginals and unchanged components support a different law because the intended event changed.
Compose f(x)=x+1 and g(x)=2x in the required orderg(f(x))=2x+2 differs from f(g(x))=2x+1. Keep the order; no Characteristic or measurement Scale is required for this function-composition claim.
Reorder or repartition disjoint exact additive resource contributionsExact addition permits the stated reorder and regrouping. That argument establishes neither arbitrary floating-point regrouping nor independence of repeated-source evidence. Check the numerical and source conditions when they matter.
New evidence defeats independence in the reliability cases, while the assembly retains its identityWithdraw the .72/.98 computations that used independence. Obtain a justified dependence model or return only a supported bound or the separate marginals. The same assembly remains the subject unless its independent identity rule requires a different conclusion.

For the additive construction, the singleton base case returns 2 from the one-element input [2]. It does not claim 2 + 2 = 2. Nor does writing the same observation twice create two independent observations.

A.9:6 - Conformance Checklist

IDRequirementPurpose
CC-A9-1Name the intended result, inputs, operation, subject model, applicability conditions and justified law. Add Characteristic, Scale and any applicable units for the quantitative branch; recover measurement conditions when it uses measured values.Recover what the result means without excluding non-quantitative composition.
CC-A9-2Select only the property needed by the current action and supply its applicable argument or warranted test. Distinguish singleton identity from idempotence and repeated-source handling.Avoid a compulsory universal algebra.
CC-A9-3Claim order or partition independence only under the model and recombination/numerical conditions.Preserve lawful sequential or parallel composition.
CC-A9-4Use a weakest-part bound only for a result and dependency model that justify it; distinguish a bound from a calculated value.Prevent both unsupported optimism and a false universal cap.
CC-A9-5Return the warranted result, bound, separate inputs or missing premise; reopen the conclusion when its supporting condition fails.Make incomplete evidence usable without inventing a scalar.
CC-A9-6A claimed Meta-Holon Transition satisfies B.2’s existing-whole comparison and the candidate whole’s identity rule.Keep reidentification independent of a model failure.

A.9:7 - Consequences

The practitioner can explain why the chosen operation answers the question and what would defeat it. A combined result remains usable only while the stated model and conditions apply. Lawful reordering or repartitioning can support distributed calculation.

The cost is recovering the domain meaning, dependencies and any property required by the action. A sufficient existing law can make this cheap. When its basis is absent, a qualified bound or retained inputs preserves useful information and exposes the missing premise. Whole recognition uses A.1; use B.2 for a remaining whole-reidentification question.

A.9:8 - Rationale

A common Γ notation locates a construction but cannot choose between joint success, alternative success, additive accounting and ordered composition. Those results have different laws even when some inputs or symbols coincide. Selecting the receiving meaning before the operation prevents a syntactically valid calculation from answering the wrong question.

Checking only the needed property also keeps the burden proportionate. A request to reorder exact additive contributions requires a different argument from a safety bound or a floating-point reproducibility claim. Retaining that distinction preserves a supported result while a different property remains unknown.

A.9:9 - Relations

PatternContribution and boundary
A.1 and B.1Identify the whole, parts and construction when those are the subjects; they supply no universal aggregation algebra.
A.7Keeps the mathematical operation, its subject, performed Work and claims about its result distinct.
A.8Tests a proposed durable U-kind’s universal-core placement only when that separate admission question is live.
C.29Governs the mathematical representation and its subject correspondence; domain theory supplies the application law.
A.19.CN, A.19.CHR and A.19.ULSAMCN records the selected characteristic basis and aggregation claim; ULSAM operates the selected CHR fold under its own admissibility and scale rules. A.9 settles an unresolved choice or needed property before reliance.
B.1.5 and B.1.6Supply Method-composition and resource-accounting rules for those uses.
B.3Supplies assurance when the receiving claim requires it.
B.2Governs whole reidentification independently of aggregation-law failure.

A.9:10 - Application situations

Apply the method to an unresolved choice in resource combination, joint or alternative reliability, control composition, numerical regrouping or ordered Methods. Use the subject source for the intended result and its applicability.

A.9:11 - SoTA-Echoing

Practice question. Which law, and which property check, preserve the intended result when dependence, order or numerical interpretation matters?

The selected line separates the subject model from the permitted computation. For the reliability branch, the NIST/SEMATECH e-Handbook, §8.1.8.2, series model, and §8.1.8.3, parallel model, supply competing laws with their independence and failure-event assumptions.

Adopt that event-first choice in §4 steps 1–3 and §5’s .72/.98 cases. With the same component data, neither a familiar product nor a minimum answers both questions. A minimum can still supply a bound where the intended event warrants it. These sources support those non-repairable or first-failure reliability models; they establish no law for every aggregate.

For computation, MPI 5.0, §7.9.1, Reduce, supplies the practical comparison. Its reduction contract permits regrouping under associativity and, where applicable, reordering under commutativity. It also recognizes that floating-point addition can change under those freedoms and advises enforcing an evaluation order when the application requires it. The source supplies both a parallel-reduction default and an explicit-order alternative, not proof that a caller’s domain operation has the assumed properties.

Adapt this contract distinction in §4 step 4 and the LOC question. Given the same operands and required result, first check only the property needed for the proposed rearrangement. A tree reduction is appropriate when that property or an adequate error bound holds. An explicit ordered fold is the stronger answer when a particular evaluation order is part of the required result. It preserves that result at the possible cost of parallelism; it does not become the most accurate summation algorithm merely by fixing order. Reject treating acceptance by a reduction interface as evidence that rearrangement is harmless.

For a constructed binary64 calculation with round-to-nearest, ties-to-even, (10^16 + (-10^16)) + 1 yields 1, while 10^16 + ((-10^16) + 1) yields 0. The inputs, two additions and operand order are the same; grouping alone changes the answer. If the receiver requires the left-associated result, the second calculation fails that requirement. If a justified receiving tolerance permits both, this example alone does not forbid regrouping. Both candidates can be compared from the same operands and result requirement before choosing an implementation.

Reopen the selected law when the intended event or dependence model changes. Reopen only the affected computation claim when the numeric representation, allowed error, grouping or order changes. A stronger reduction method matters when it preserves the required result with a preferable cost; its speed alone does not establish the domain law.

A.9:End

A.10 - Evidence Graph Referring: Claim-Bound Evidence and Provenance Graph

Type: Kernel pattern Status: Stable Normativity: Normative

A.10:1 - Problem frame

Use this pattern when a source, carrier, result episteme, credential, dashboard, provenance label, generated explanation, model card, or review note is being relied on for a named claim or bounded action and the source-to-use account is still implicit.

Primary EntityOfConcern. The relied-on claim and bounded use. A.10 builds a descriptive evidence-provenance path that represents the independently established sources, carriers, work, result epistemes, provenance relations, currentness, and later-use relations needed to judge that use. The path is not a new world-side relation and its edges establish none of the facts they cite.

First useful move. Name the selected claim C in episteme E and its bounded use U. Recover the cited sources, carriers, and direct relations S, and currentness T when it affects that use. Use §4.5 to determine the bounded A.10 disposition D, or name what is missing for that classification.

When C states a local result R, retain the rule that defines or tests R and the episteme stating it. Add a dated U.Work occurrence only when that Work is itself a current claim. If the account says that Work returned, produced, or obtained a value, name the A.6.1 application binding, one local A.15.PROD claim, or a direct subject relation under its own pattern; otherwise keep the Work and value as separate facts. Mark any missing rule or relation as a gap.

What goes wrong if missed. Carrier presence becomes truth, provenance becomes approval, a result record becomes performed work, MethodDescription becomes a run trace, a graph edge becomes an obtaining relation, and a currentness or assurance decision is inferred from display styling.

What this buys. A source-to-use account that can be replayed, contested, refreshed, narrowed, or handed to the pattern that defines or tests an additional claim, while keeping the claim, carrier, performed work, local result, result episteme, provenance, currentness, reliance, assurance, and action distinct.

Not this pattern when. A.10 does not establish measurement, formal, causal, diagnostic, conformance, comparison, selection, acceptance, gate, permission, commitment, Work, or decision results. It does not establish representation correspondences. Use the pattern that defines or tests each result, A.15.1 and A.6.1 for performed Work and actual bindings, C.2.1 for the result episteme, G.11 for currentness, and B.3 only when a named assurance claim is current. Use A.6.3.RT for a same-EntityOfConcern representation transition, or the applicable transition pattern for another transition. Use C.29 only for an unresolved mathematical-lens choice, transfer or reliance question.

Use A.2.4 first when only the first evidence-use or status-use classification of an episteme is at issue. Enter A.10 when carrier identity, source recovery, provenance, currentness, rival explanations, or bounded reliance must remain replayable.

Here path means a path in a descriptive evidence/provenance graph, never a route of action or a universal evidence relation.

A.10:2 - Problem

Source-backed reasoning fails in recurring ways:

  1. the relied-on claim is not named;
  2. a carrier or publication face is substituted for the claim it represents;
  3. a method description, plan, signature, or stored reference is substituted for actual work and bindings;
  4. a local domain result is replaced by a generic evidence or result field;
  5. provenance, currentness, reliance, assurance, and authorization are collapsed; or
  6. a graph edge is asserted before the direct source, work, production, representation, participation, or use relation is known to obtain.

The practical effect is false authority and unreplayable decisions: a badge looks like permission, a dashboard looks like a gate decision, or a model output looks like an accepted conclusion.

A.10:3 - Forces

  • Minimality vs consequence. Orientation needs a small path; material reliance needs the fields that change the decision.
  • Carrier identity vs claim content. The same content can appear in several carriers and editions; a carrier can be authentic while the claim is false or stale.
  • Reusable method vs performed work. A method is a repeatable way of doing. Ordinary reading, orientation, or reliance can remain ordinary; a claim about performed U.Work requires the dated occurrence and bindings consumed by the claim.
  • Provenance vs result establishment. A.10 must make a result traceable without establishing the result itself.
  • Graph convenience vs ontic discipline. A graph can represent many relations compactly but cannot make them obtain.
  • Contestability vs confidentiality. Reliance must be challengeable while sensitive carriers may require scoped, redacted, hashed, or access-controlled views.

A.10:4 - Solution — recover the objects before drawing the path

A.10:4.1 - Start with the relied-on claim

Name the C.2.1 episteme and select the claim or proposition being relied on from its ClaimGraph. Recover that claim’s subject, interpretation basis, polarity or status when current, and uncertainty or qualification when relevant. If the claim is used as evidence for another target claim, name that target separately under A.2.4.

When the selected claim states a local result, use the pattern that defines or tests that result: C.16 for measurement, C.28 for causal support, A.19 for comparison or selection, G.4 for an acceptance-clause application, A.21 for a gate decision, C.11 for an option-set choice, and the applicable formal, diagnostic, conformance, identity, permission, or commitment pattern.

When role leaves the intended claim unresolved in a technical result, use E.10.ROLE to select the local system-role-kind classification, U.SystemRoleAssignment occurrence or state, relation among system-role kinds, declaration, participation, interface, or representation claim before citing its governor.

A source episteme may contain several claims. Keep an ordinary source citation ordinary; use C.2.1:4.2.5 ClaimAddress only when an intrinsic claim reference is needed and resolves uniquely. If that needed address does not resolve uniquely, follow C.2.1’s whole-episteme or separately identified claim-episteme alternative.

A carrier, citation, provenance entry, or A.10 classification does not constitute the result episteme or the domain result. When their identity is live, use C.2.1 for the result episteme and the subject pattern for the domain result; use A.15.PROD when inception through Work is claimed.

A.10:4.2 - Ground source, carrier, publication, and representation

Recover the selected source episteme and its edition and claim content. When availability, form, or carrier matters, separately recover the EpistemePublicationRelation occurrence, publication form, carrier, or face involved, together with any copy, extraction, or transformation between source and use. Use E.24.PUB for publication, form, and carrier relations and E.17 for multi-view publication. Use C.29 only when a separate mathematical-representation choice, transfer or reliance question remains. The descriptive graph points outward to those independently established objects and relations.

Carrier authenticity, integrity or provenance can support a named origin, history, build or transformation claim under its rule. The content may also support another claim through that claim’s evidence or constitutive relation. Carrier presence or provenance alone establishes no additional truth, approval, permission, assurance or Work occurrence.

A.10:4.3 - Separate method, work, participants, and local result

Under A.3.2, an already identified episteme is a U.MethodDescription when its EntityOfConcern is one admitted U.Method and it makes at least one substantive claim about that Method as a way of doing. Generic participants, parameters, effects—including intended effects—and operating conditions can supply such claims; a name, date, or approval alone cannot. A particular work-plan intention, actual-participant binding, or proof/test occurrence remains a separate claim. Generic participant meanings and method claims do not establish actual operation-application bindings or that Work occurred.

Source production, measurement, verification, interpretation, transformation, query, review, publication, or later reliance may be described ordinarily. When the current claim says that one of these is a dated U.Work occurrence, first recover each performer’s A.13 core and independently admit the occurrence through A.15.1 from its performance history, enacted Method, extent, and containing-System relation. Add F.6 afterward only when the evidence account also needs precise assignment-bound attribution.

The A.13 core always includes the obtaining assignment. A short Work account may omit an assignment identifier unused by the receiving claim only when the complete core and all consumed relations remain recoverable; a precise attribution claim additionally requires the F.6 facts.

Affected or evaluated referents, resources, and participants enter only through direct subject relations or A.6.1 operation-application bindings. Capability, authority, and responsibility remain separate predicates. A compatible signature, plan, description, log schema, or graph node establishes none of those bindings.

For every cited result, recover its defining or testing rule and identify its result episteme separately when that identity matters. A PatternID can locate the rule without requiring a new pattern application. The provenance path may represent Work, participants, entities, domain results, result epistemes, and outcomes only after their direct relations are established.

Relate Work to a returned or produced value only through an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate under its own pattern; otherwise show the two facts separately and return the reason-specific non-assertability result if that connection is needed.

A.10:4.4 - Build a descriptive evidence-provenance path

The minimum A.10 path records only what the bounded use needs:

FieldRequired content
Relied-on claimThe selected claim or proposition in one identified C.2.1 episteme; a separate target claim when the evidence use distinguishes it
Bounded useThe ordinary orientation, learning, action, or reliance use being judged, and its premise, reference, decision-use, operation-argument, or other direct use relation. Add a later U.Work occurrence only when it is independently current.
Sources and carriersSelected source epistemes and editions; publication occurrences, forms, carriers, and faces when material; transformations; and direct provenance/citation relations
Work and bindingsOnly independently current dated U.Work, its complete basis, and the performers, Methods, resources, direct relations, and A.6.1 bindings used by the claim. A claimed Work-to-value link also needs an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate defined by its own pattern.
Result ruleThe defining or testing rule for each asserted local result, and its result episteme when that identity is used
Time/currentnessSource and result windows plus G.11 currentness when currentness affects use
ChallengeA live rival explanation when it needs discrimination; a locally grounded, plausible unsupported use when excluding it changes reliance; an available contest/redress path when a party is affected; and the stop or reopen condition applicable to this use

For every unsupported-use guard in this pattern, require an independent local ground for the rejected reading, a plausible intended-reader error, and a change in truth, understanding or use. State only the smallest correction needed under F.19. A live rival explanation remains a substantive alternative to test, not a mandatory invented opponent.

Graph nodes retain their admitted kinds. Each edge cites one independently established direct relation; no generic evidences, verifiedBy, validatedBy, measuredBy, producedByWork, or criterion-participant relation is minted as a fallback. A project may label display edges for navigation, but the label has no ontic force.

A.10:4.5 - Classify bounded reliance

The canonical local RelianceDisposition member set is exactly: pass, degrade, abstain, reopen, evidence-needed, assurance-needed, and blocked-current-use. pass supports only the bounded use; degrade supports only the named narrower or reversible use.

assurance-needed says that A.10 alone cannot support the attempted use because a direct domain rule or receiving decision requires a separately stated assurance claim. It creates no assurance claim and does not open B.3 until that claim is current. No disposition is claim truth, CV.Status, gate decision, selector outcome, approval, permission, release, assurance, or Work authorization.

When a named assurance claim is current, use B.3 for that assurance question. A.10 continues to supply the source and provenance paths but does not issue the assurance result. Consequential evidence use without such a claim stays with the direct safety, access, status, gate, permission, release, responsibility, or controlled-action pattern.

A reliance limitation qualifies the attempted use. When advice must also say what to do next, use C.11.DUA to compose a feasible continuation from that limitation. Further inquiry is one possible continuation. Retain the unsupported claim boundary when choosing a narrower use, another action or a stop. Use an already adequate C.11 choice directly.

A.10:4.5a - Route unlike exploratory inputs without changing their kind

When an observation, objective, former cue, novelty characterization, or similar item is proposed as a premise for an exploratory or creative move, recover the item under its direct owner before applying this bounded reliance classification. Do not rename every item signal or cue, and do not create a second premise-disposition vocabulary.

Incoming itemSource/result recoveryA.10 useReceiving choice
Evidence-bearing measurement, assessment, experiment, inference, or capability resultThe selected claim in an identified C.2.1 episteme and the measurement, capability, experiment, inference or other rule that defines or tests its result.State the relied-on claim, evidence-provenance path, bounded premise use, and existing RelianceDisposition; exclude a locally plausible unsupported use when that distinction changes reliance.When an option or probe comparison is current, C.11 compares the available alternatives and emits its ChoiceResult.
Objective, reward, utility term, loss, preference, or heuristic that is not evidenceThe objective, evaluation, preference, Method, or source-local construction.Apply A.10 only to a separate evidence or source-reliance claim about that construction or its bounded transfer; the numeric objective is not self-authenticating evidence.Enter the term as the declared EvaluativeMeasure, PreferenceOrder, or ChoiceRule input that it supplies, with assumptions and limits visible.
A former pre-articulation cue that has now been articulatedA.16.1 no longer owns the articulated result. Use B.4.1, B.5.2, or the endpoint claim owner selected by the articulation.Qualify reliance only when that articulated claim is used as a premise.C.11 owns any current option/probe comparison; the earlier cue pack neither selects nor evidences the move.
A non-evidential C.17 novelty, surprise, use, or creativity characterizationC.17 owns the characteristic claim, its scale/basis, and its limitations.Apply A.10 only when evidence or source reliance for that characteristic claim is current; characterization is not evidence merely by being decision-relevant.C.11 may consume the bounded characteristic together with other premises and still choose, reject, probe, or reroute.

The composition retains the source result and an existing RelianceDisposition when bounded reliance is current. A later ChoiceResult is required only for an actual option/probe comparison under C.11. If the source claim is already qualified and the current C.11 record can use it directly, stop; no intermediate premise record is required.

A.10:4.6 - Currentness, actual use, and graph limits

Source availability and source currentness are distinct. Record issue/effective windows, supersession, revocation, source-order rules, and the G.11 currentness result when a use depends on them.

Actual reliance requires one premise, reference, decision-use, operation-argument, or other direct relation to the relied-on episteme. When that reliance is also claimed as dated U.Work, recover the Work independently. Storage, indexing, citation, graph membership, visibility, or co-location establishes neither reliance nor performed Work.

Part-whole, temporal, production, publication, representation, provenance, participation, and reliance relations must each be established separately. The A.10 graph may cite them together for replay but never substitutes one for another.

A.10:4.6a - Authority-reliance use of ordinary A.10 evidence-provenance paths

Use this subsection when an authority-looking carrier is being relied on. The A.10 path represents one named claim, its sources and direct relations, and one bounded use; it is not an authority relation. If the Work occurrence, gate decision, speech act, commitment, permission, system-role assignment, assignment-state assertion, or other required relation already exists in a project-side source, recover that object by value and let the graph cite it.

Start with A10-lite for source-finding, orientation, learning, and bounded reversible probes. It is sufficient only when these fields supply the evidence required by the claim and its rule; reversibility alone does not establish sufficiency:

FieldRequired content
claim or effectThe claim, effect, or source-backed reliance use the evidence carrier is being asked to evidence for the named work occurrence or reliance use.
evidence carrierThe display, badge, credential, attestation, dashboard tile, copied text, generated text, log, trace, source file, report, or other SymbolCarrier/publication carrier.
producer, issuer, verifier, or source contactName the producer, issuer, verifier or source contact and the direct relation through which it bears on the claim only when the evidence use needs them. A recognizable ordinary actor designation needs no further expansion. If dated Work is asserted, first recover each performer’s A.13 core and independently admit the Work under A.15.1. The core includes the obtaining assignment; add an F.6 link through that same assignment only when this evidence path consumes precise assignment-bound attribution.
method use or Work occurrenceName the ordinary source-finding or method use. Add admitted measurement, verification, review, build, attestation, copy, extraction, generation, query, trace, or log U.Work only when independently current. If that Work is said to have returned, produced, or first constituted the carrier or result, cite an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate under its own pattern; otherwise keep the facts separate.
time windowIssue time, effective window, decay, supersession, revocation, policy or gate version, and reopen condition, each when the selected source or bounded use depends on it. Name a missing required value rather than inventing one.

Minimum evidence-provenance path for routine reliance:

FieldRequired content
evidenced claim or effectApproval, permission, gate passage, local system-role-kind classification, system-role-assignment occurrence or state, relation among system-role kinds, status currentness, work occurrence, evidence relation, assurance input, or other claim named by value or effect being attempted. Use E.10.ROLE only when a technical role claim remains ambiguous.
evidence carrierThe visible or recovered carrier, with enough identity to reopen it.
issuer, performer, trust root, status register, and source-side predicatesName every object this path uses: the admitted System performing source-side Work; the trust-root or status-register episteme, register, or service; and the issuer, publication, registration, status-source, source-maintenance, trust, acceptance, or currentness predicate by which that object bears on the relied-on claim. For admitted Work, first recover every performer’s A.13 core and independently admit the Work under A.15.1. The core includes the obtaining assignment; add an F.6 link through that same assignment only when this path consumes precise assignment-bound attribution. If no current pattern defines or tests the needed predicate, return the A.6.RCD missing-governor result. Authority and source-maintenance responsibility remain separate relations.
affected entity and relying contextThe release, service, model, person, admitted System and any separately obtaining assignment, policy subject, work target, claim, audience, tenant, environment, or other entity for which reliance is attempted.
time window and freshnessRetain each issue/effective, decay, supersession, revocation, policy/gate-version, or reopen value that the selected source or bounded use consumes; report a missing required value.
relevant Work occurrence or method traceAny independently current production, verification, query, generation, review, or other U.Work, plus the method trace when the method matters. Connect that Work to the carrier or result only through an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate under its own pattern; otherwise record them separately.
evidence relation and rival explanationWhich source claim or content bears on the target claim, through which evidence relation, and which live rival explanation must be distinguished—for example, stale status, a spoofed badge, a copy changing the claim, or a scope change defeating the use. Recover the relevant episteme from its carrier.

Expanded fields are collected only insofar as they decide the current reliance question. Evidence depth follows consequence severity, reuse, contestability, cross-context movement, and the evidence relation required for the attempted claim. Do not expand a source-finding note into a full evidence dossier, and do not collect every expanded field merely because a carrier is copied, generated, credential-like, provenance-like, or cross-context.

Adversarial misuse guard. When a carrier appears to support a claim, name what it appears to establish and any live competing explanation. An apparently current credential may have an authentic carrier but a stale displayed status; a copied approval may be genuine but concern a different scope or window. Test the source, issuer, or currentness predicate and relying context that distinguish that explanation; include source-side Work and precise attribution only when the claim uses them. Authenticity and provenance can contribute to their named claims, but appearance or provenance alone does not establish additional truth, currentness, or authority. If the required predicate has no governor, return that A.6.RCD gap.

Data-minimization and privacy boundary. Preserve the source, provenance and direct-relation account sufficient for the intended use. Use redacted, hashed, scoped or access-controlled references when raw material would disclose secrets, unnecessary personal or tenant identifiers, privileged records, or sensitive security, incident, model or data provenance. Redaction creates no source relation; it must preserve enough recoverability for the relying context.

Expanded fieldWhen it is needed
method trace or work traceThe selected provenance, attestation, generated/copy/dashboard/rollback source relation, or Work claim depends on how the method was applied or the Work occurred. A source relation alone need not assert Work.
evidence-carrier integrityA plausible spoof, stale source, copy, transformation, rendering, redaction, or context shift could change the relied-on claim or its use. Check the integrity property that discriminates that risk.
identity or holder bindingThe claim depends on a credential holder, admitted System, separately obtaining assignment holder, acting holon, issuer, performer, delegate, revoker, verifier, or relying party.
verifier context, relying-party context, and acceptance ruleThe evidence relation is accepted only for a verifier, audience, tenant, environment, release line, policy subject, operational mode, or consumer-side policy or gate rule that accepts the evidence for this use.
proof, cryptographic-signature, or status verification resultThe selected credential, provenance, attestation, authenticity, revocation, or currentness claim requires that verification result under its source specification or verification/use policy. Retain every check required by that regime.
policy version, gate version, and decision sourceThe attempted permission, release, rollback-authority, policy-authorization, or other use depends on that policy or decision. Gate version and gate-decision source are required for a gate-dependent use.
source-chain transform notesEvidence relation passed through extraction, copy, rewrite, representation shift, explanation rendering, summary, export, redaction, or another transform step before reliance.
source order and supersession ruleMultiple source candidates disagree or freshness or priority may defeat the visible publication face, publication carrier, rendering, or cue. Include the direct register or status-source-order relation when a register entry is the source for a system-role-assignment occurrence, status assertion, permission, commitment, or gate state.
minimum disclosure boundaryRaw evidence would expose secrets, personal data, tenant identifiers, privileged logs, tokens, security-sensitive traces, or unnecessary identities.

Case repairs:

CaseEvidence repair
Stale credential badge or status displayName the issuer or trust-root object and its direct issuer or trust relation; name the status register, entry, and direct registration or status-source relation when one exists; then show the verifier and relying-party context and the proof, status, freshness, window, entry-version, and integrity facts needed to resolve the stale-source claim. Include holder or subject binding when the claim or regime requires it, validity limits when present or required, and revocation/status checks when the mechanism is present or the selected verification/use policy requires them. Display presence is not an obtaining system-role-assignment occurrence, status assertion, or permission.
Verifiable credential, credential view, or register excerptTreat it as an A.10 carrier. Name the issuer or trust-root object and relation; the status register, entry, and registration or status-source relation when present; the selected source U.Episteme and edition and, when availability matters, its EpistemePublicationRelation; verifier, relying context, acceptance rule, and the proof/currentness facts required by that rule. Include holder or subject binding only when required by the claim or verification regime, validity limits when present or required, and status/revocation checks when that mechanism is present or the selected verification/use policy requires it. Passing the applicable checks may evidence credential currentness for that bounded use; it does not imply a holder-bound claim where none was established. A strong grant, exercise, weak non-prohibition or non-violation finding, or conflict requires A.2.8.PER; a commitment requires A.2.8; an issuing act requires A.2.9; a system-role assignment requires A.2.1; a status assertion requires its status pattern; an entry predicate requires its defining pattern and A.6.B boundary classification; and gate passage requires A.21. Display presence creates none of them.
Copied approval or review summaryShow the original A.2.9 SpeechActRef or issuing act when approval or authorization is claimed, or the original reviewed source when only review-content currentness is claimed. Add the copy relation, currentness, scope, and window. Add a separately identified dated U.Work only when it is current, and connect it to the copy or result only through an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate defined by its own pattern. State separately whether the claim concerns an A.2.8.PER grant, finding, exercise, or conflict result; an A.2.8 duty, recommendation, or prohibition commitment; or another Work relation. Copy evidence is not approval by itself.
Provenance, authenticity, or attestation labelShow the bounded origin, history, build, or process claim; selected source U.Episteme, the EpistemePublicationRelation occurrence when availability is material, or evidence carrier; the method/Work trace, source-specific proof, and carrier-integrity facts that this claim and its verification regime require; the verifier or relying policy that accepts them; and any live rival that changes reliance. Provenance does not show truth, safety, approval, release, gate passage, permission, or assurance unless another FPF relation named by value carries that additional claim or effect.
Dashboard status tileRecover the dashboard query and the source relation or source-bearing record it uses, with the time, window, currentness, source order, freshness policy, and live rival relevant to the claim. For a gate-dependent use, cite the current A.21 GateDecisionResult, directly or through its DecisionLogRef, with gate profile, gate version, release target, and work target. For a release claim not dependent on a gate, cite that claim’s own rule and decision source; do not invent a gate result. A.10 records this source-to-use account. A status display is not gate passage or Work occurrence by itself.
Rollback command-like cueRecover whether the claim concerns a command, an issuing speech act or only an A.6.A action invitation. Name the actor, target, scope and window the claim uses; recover the command record or issuing act and any authorization relation only when the claimed use depends on them. A command cue is not performed-work evidence.
Rollback performed-work resultRecover the independently admitted A.15.1 U.Work occurrence and the Method, performance evidence and time window relevant to the performed-work claim. Include logs or outcome evidence when that claim uses them. Performed-work evidence is not approval, assurance, or gate passage by itself.
Generated explanationRecover the source or source-to-target relation claimed. Use E.17.EFP only when an unresolved explanation-use ambiguity changes the interpretation or use. For reliance, recover each operative claim’s source basis or independently established inference/result under its rule, including any source passage, carrier, relationFunctionClaimRef or authoritySourceRef that the claim uses. A.10 can then qualify reliance on that claim. Fluent wording alone supplies no evidence, approval, authorization, gate passage, performed Work or assurance.
Model card or datasheet used as evidenceShow documented bounded-use statement or external intended-use field, version, window, evaluation condition, limitations, evidence carriers, and whether a B.3 assurance claim is being made. Documentation does not become readiness or assurance by presence.
Extracted source-to-use path to gate or release claimName the selected source U.Episteme ref and, when availability is material, the EpistemePublicationRelation occurrence ref; the source-bearing relation or pattern reference that identifies the rule carrying the claim; the transformation chain and any loss or non-commutativity, identifying its first step when present; the FPF relation or pattern that defines or constrains each relevant transform (A.6.3.CR, A.6.3.RT, A.6.3.CSC, E.17.EFP, E.17.ID.CR, or E.18 where applicable); and the bounded inference relation after the transform. A lossless chain retains those relations without a lossy step. When the claim consumes a relation-function or authority-source claim, name its relationFunctionClaimRef or authoritySourceRef; otherwise retain the direct source reference already recovered. State what change reopens the use and which source, transformation, evidence relation or rule must then be rechecked. Identify any gate or release claim whose use remains blocked by an unresolved dependency.
Conflicting source relationsWhen display, source publication carrier, decision log, recency signal, freshness signal, copied summary, generated summary, credential status, provenance label, or assurance evidence disagree, name the visible source relation, rival source relation, source-order rule, decision-source relation, freshness policy, and supersession rule. Do not choose by color, visual salience, confidence wording, copied wording, or apparent recency; the work claim or reliance claim is contested until the source-order question is resolved.
Sensitive evidence-provenance pathUse redacted, hashed, scoped, or access-controlled carrier refs when raw carriers expose secrets, personal data, security-sensitive traces or data, privileged logs, tenant identifiers, or unnecessary identities. Redaction does not create a source relation; it must preserve enough recoverability for the relying context.
Pointer or proof-status evidence-provenance pathUse a hash, proof or status verification result, selected source U.Episteme, EpistemePublicationRelation occurrence when availability matters, source or source-currentness relation, scoped pointer, disclosure receipt, or access-controlled view instead of copying raw sensitive carriers or payloads when that pointer preserves enough recoverability for the relied-on claim or effect. Do not copy raw secrets, tokens, privileged logs, personal identities, or tenant details merely to make the path look fuller.

If the path is incomplete, name the missing source, carrier, Work, result rule, direct relation or needed currentness fact and narrow or block only the dependent use. Select a feasible continuation under C.11.DUA when one is still needed: recover or verify the source, refresh a query, narrow reliance, choose a permitted reversible probe, or stop. An explicit WorkPlan is needed only when planning that continuation requires it; reversibility alone establishes no permission or evidential sufficiency.

Missing source-relation repair assignment. If the relying actor cannot recover or verify the source relation, first name the missing relation or source-bearing record and the affected use. Source-finding, a request, narrowing, or a stop may be the complete continuation.

If the selected continuation allocates or requests repair, recover the recipient and the independently obtaining project-side responsibility, allocation, permission, or commitment relation that the instruction consumes. An assignment to an admitted System must identify that System and its assignment basis. Plan or request the future repair under its applicable planning or assignment rule; this is not an assertion that repair Work has occurred.

The source-side objects and relations identified above remain separate facts, not responsibility by source label or form. Return an A.6.RCD missing governor only when the selected assignment claim requires that missing predicate. Source exposure and the affected party’s challenge remain available independently of who may later perform repair.

ViewpointPrompt
Relying actorWhich claim named by value or effect needs an evidence relation, and what is the minimum carrier, source-bearing record or relation, time, and evidence-provenance path for that claim or effect?
Issuer, verifier, or status relation maintainerWhich facts in the selected source relation and verification regime must be exposed or repaired for this claim?
Auditor or technical reviewerCan the carrier and selected source relation be recovered, together with the method/Work trace, time, and live rival that this reliance question needs?
Security reviewer or compliance reviewerWhich applicable verification, source-order, supersession, and disclosure conditions decide this reliance question?
LLM user or tool userWhich generated or copied operative claims map to source passages or carriers, and which claims remain only source-finding?
Author of model documentation or data documentationWhich intended-use, evaluation-condition, version, window, limitation, and evidence carriers bound the model documentation or data documentation?

Repeated source failure. When repeated stale, contested or missing-source findings suggest a shared source or display defect, check that explanation before selecting a repair. If the defect is established and correction is needed, repair the affected source relation or display: for example, expose the decision-source reference, add a needed currentness check, preserve claim-to-source correspondence through copying, or show the scope of an attestation. Recheck uses that depended on the repaired source. Repetition does not require each relying user to reconstruct the path manually.

Display the claim, recoverable source and carrier references, relying context, and the time/currentness values that affect use. Add a guard only under §4.4’s F.19 conditions. A display of source availability must identify that limited claim; approval, permission, gate passage, Work and assurance retain their separate rules.

Incident-learning fields for evidence and currentness overread: visible carrier or publication face, intended claim or effect, missing evidence-provenance field, evidence carrier named by value, source-side predicate used, ordinary method trace or admitted Work trace, and needed time relation; any live rival relevant to the incident; current safe disposition; and the smallest upstream repair to the implicated source relation, instrumentation, or publication. Identify the selected source episteme and the publication occurrence, form, carrier, or source display when that object needs repair; the field definitions above determine which facts must remain recoverable.

Contestability and redress relation: when an evidence-provenance path or source-currentness relation affects person or team status, access, responsibility, a compliance relation, or a release decision, the A.10 result names the disputed claim, evidence carrier, affected use or harm, available challenge, review, redress, communication, source, publication, register, access, or contact relation, allowed evidence or argument, possible disposition change, outcome route, reopen trigger, and safe interim disposition.

Source exposure remains independent of who may later perform review or repair Work. Name a responsibility, allocation, commitment, permission, or authority relation—or its missing governor—only when the current claim consumes that relation, including when allocating future review or repair; its absence does not close the challenge.

Positive repaired evidence-use statement. When the source account is complete, write the smallest bounded statement: named relied-on claim; carrier and source; direct provenance and citation relations; ordinary bounded use; and RelianceDisposition. Include currentness, a locally plausible unsupported use, and a stop or reopen condition when each changes that reliance decision.

Add producing or interpreting U.Work, each performer’s A.13 core, independent A.15.1 admission, Method, actual bindings, and later Work only when those facts are current. Add F.6 afterward only when the receiving account needs precise assignment-bound attribution. A claimed Work-to-value link needs an A.6.1 application binding, one local A.15.PROD claim, or a direct subject predicate under its own pattern. Add authority or responsibility only when a relation is independently required by the use. A short Work statement may omit an unused assignment identifier only when the complete A.13 core, including its obtaining assignment, and every consumed relation remain recoverable; an assignment is never the authority or responsibility result.

A.10:4.6b - Local evidence-use classifier and RelianceDisposition for source-bearing carrier or display reliance

Use this subsection when a visible carrier, publication face, selected source U.Episteme ref, EpistemePublicationRelation occurrence ref when availability is material, source relation ref, or display is being relied on for a named claim or act. First recover the claim kind, the pattern or source rule that defines or tests the claim, the source/provenance path, and the bounded use. Broad words such as source, metric, confidence, conformant, safe, ready, certified, approval, or permission are recovery prompts, not relation names.

This is a local reliance-use classifier, not a Core evidence-kind ontology. Use only the row that decides the attempted use. The path represents direct relations and the RelianceDisposition records one bounded A.10 judgment; neither becomes a general evidence or authority relation. Affordability: ordinary orientation or source-finding can stop here; bounded reliance states one evidence use and the currentness window, unsupported-use boundary, and stop or reopen condition that apply to it. If a domain rule requires assurance, state the assurance claim and then use B.3. Plain wording remains ordinary unless it changes one of the named source, evidence, gate, assurance, Work, decision, or control claims.

Stop when the bounded claim and use, source, evidence relation and applicable currentness and stop/reopen conditions are recoverable. Reuse already established subject results when their grounds still apply. Open B.3, A.21, B.2.5, a Work pattern or another supplier only for an unresolved question under its entry conditions; an official-looking, quantitative, generated, credentialed or safety-related display does not itself create that question.

Plain disposition palette: RelianceDisposition=pass means proceed only inside the bounded evidence use; degrade means use only a narrower or reversible version; abstain means do not decide yet; reopen means a changed or contested evidence relation defeated the previous classification; evidence-needed names missing evidence at the decision point; assurance-needed says a separately stated assurance claim is required before this attempted use can proceed; blocked-current-use blocks the attempt until its evidence-provenance path or source relation changes.

Source-looking evidence use or attempted useFirst A.10 actionEscalation triggerForbidden overread
Ordinary source-backed report, record, citation, observation, model card, datasheet, data card, or publication excerptName the claim, carrier, producer or Method trace when relied on, evidence-provenance path, and bounded evidence use. Add currentness, a locally plausible unsupported use, and a stop or reopen condition when they change reliance.Open B.3 only when a named assurance claim is current; open A.21 for a relied-on gate decision, A.15 or A.15.1 for Work, or another pattern only when that relation is claimed.Evidence presence as approval, gate passage, assurance, release permission, Work authority, control authority, or safety acceptance.
Confidence, calibration, prediction interval, abstention reason, or selective-action cueName the act and the assumptions of the selected inference or calibration method. Retain its calibration population and exchangeability when that method requires them, and the window, shift, applicability, and stop condition that bound this evidence use. Use pass or degrade only for that use; exclude a locally plausible unsupported wider use when the distinction matters.Open C.27 or G.11 when timing, expiry, refresh, distribution shift, monitoring, or applicability changes the act; open B.3 only for a named assurance claim.Confidence as global permission, trust, readiness, safety, release reliance, or engineering justification.
Generated explanation, generated summary, or didactic reconstructionRecover the source or source-to-target relation claimed; use E.17.EFP only when explanation-use ambiguity still changes the interpretation or use. For a claim used beyond source-finding, recover its source basis or independently established inference/result and its A.10 evidence-provenance path.Apply the rule defining or testing that operative claim; B.3, A.21 or A.15 applies only to its own current question.Treating fluent wording alone as evidence, assurance, approval, gate passage, Work or permission.
Conformance label, CV.Status, benchmark result, score, semantic-fidelity marker, or CV-looking publication near releaseRecover the declared relation: measurement or marker relation, A.20 step-local CV status, A.21 gate check, E.19 admission/refresh review result, E.21 pattern-quality evaluation result, C.16 characterization, or external-rule source named by value. A score label alone selects neither E.19 nor E.21.Open A.21 only when a named gate applies its profile rule to the effective check-application results and returns a GateDecisionResult; open B.3 only when an assurance claim is being made.Conformance or a score as an unrestricted value, adequacy, release, safety, trust or gate conclusion outside the declared relation.
Provenance, authenticity, C2PA-like credential, SLSA-like attestation, build record, or status-register displayState the bounded origin, history, build, or currentness claim being evidenced and the source relation carrying it. Retain the method/production trace, holder, status, verifier rule, and relying-context facts required by that claim or verification regime.Open the record or relation that carries truth, permission, safety, release, gate passage, work occurrence, or assurance only when that relation is being claimed by value.Provenance, authenticity, or status-currentness as truth, safety, approval, permission, release, gate passage, or assurance.
Contest, redress request, challenge, appeal, or conflicting source relationName the contested claim, evidence carrier, source-order or currentness issue, affected use or harm, available challenge or redress relation, allowed evidence, possible disposition change, outcome route, and reopen trigger. Add a review-responsibility relation or missing governor only when the claim assigns future review Work.Open neighboring system-role, assignment-state, commitment, gate, control, assurance, Work, or representation patterns only when those effects are claimed by value.Appeal-channel presence, challenge form, or redress workflow presence as truth, compliance proof, social-effect acceptance, completed redress, gate passage, or work authorization.

For A.10 use, RelianceDisposition is a local disposition over the evidence-provenance path and the bounded reliance use. Outside a table column already headed RelianceDisposition, write the qualified form RelianceDisposition=... and bind it to the named bounded evidence use, with currentness and window, an unsupported-use boundary, and a reopen or stop condition when applicable; it is not CV.Status, GateDecisionResult, selector result, or ProblemCard@Context state.

Observed-effect or consequence evidence supports what happened or is credibly recorded. If the claim says that the source caused, prevented, would have changed, or causally contributed to the effect, use C.28 for that causal question while retaining its A.10 evidence path and any separately required Work or assurance relation. A normative responsibility or allocation claim uses its own rule; the phrase ‘responsible for’ must be resolved from the source claim before selecting either branch.

If a proxy marker, benchmark, confidence value, dashboard metric, or score becomes the primary driver for action, release, resource allocation, people status, team status, or P2W priority, check whether the claim being made also raises an E.13 proxy-to-objective question. Do not open E.13 for every metric; open it only when the proxy is being used as the target or decision driver.

Use C.26.1 when publication, observation, or another interaction changes the represented state while its output is being used as if it were a passive read, export, comparison, or decision input. First identify what the interaction changed and which use of the output must change. This is the probe-coupled question for a dashboard, warning, label, or public status display; ordinary influence without the false passive-read use does not activate it.

RelianceDispositionA.10 classificationMinimum A.10 statement
RelianceDisposition=passThe evidence relation named by value is present and current for the named use, evidence of the required kind is present, the source relation is current enough for that use, and the evidenced use is bounded.State the evidenced claim, act, work occurrence, review claim, or P2W carry-through use and its evidence-provenance path. Add the applicable window and any locally plausible unsupported use that must be excluded.
RelianceDisposition=degradeThe source relation carries only a narrower claim, smaller audience, reversible local act, lower assurance input, or shorter window.State the narrowed bounded evidence use, the proposed or locally plausible wider use it excludes, and the applicable stop condition.
RelianceDisposition=abstainEvidence is insufficient, stale, out-of-context, uncalibrated, conflicted, or not tied to the claimed relation, while immediate rejection is not justified.State the claim not decided and the missing evidence or relation needed before use.
RelianceDisposition=reopenA contest, changed representation, changed selected entity, stale source, expired window, changed profile, conflicting source, retargeting, or new evidence defeats the previous evidence-provenance path.State the source or relation to reopen and the previous use that is no longer evidenced.
RelianceDisposition=evidence-neededThe visible carrier, selected source U.Episteme ref, publication-occurrence ref when availability is material, source relation ref, or display may matter, but evidence of the required kind or the source-currentness relation is absent.State the missing evidence kind, the pattern or source rule that defines or tests it, and the decision point so delay does not become indefinite.
RelianceDisposition=assurance-neededA domain rule or receiving decision requires a separately stated assurance claim before the attempted use may proceed, and the current A.10 basis alone cannot supply it.State the required assurance claim and its domain basis. Apply B.3 only after that claim is current; until then block or narrow the attempted use.
RelianceDisposition=blocked-current-useNo current evidence-provenance path carries the evidence relation needed for the attempted act, work, claim, gate, release, assurance, review, control-bearing feedback, or P2W use.State the blocked use and the neighboring pattern or project record required before a new attempt.

Minimum contest relation with possible redress: a contest relation exists when the affected party can identify the disputed claim or source, affected use or harm, an available challenge, review, redress, communication, source, publication, register, access, or contact relation, evidence or argument allowed in challenge, possible disposition change, outcome route, and reopen trigger. A system-role label, assignment, feedback channel, complaint form, or appeal label without those recoverable values is not enough to change the disposition. Responsibility for future review Work is a separate claim.

Affected-party contestable minimum: even when raw evidence stays restricted, the contesting party must be able to see enough of the claim, source class, disposition, affected use, available challenge or contact route, and allowed challenge evidence to challenge the result. Privacy, security, or privilege can narrow disclosure; they cannot erase the challengeable minimum while still claiming contest or redress.

False-negative reliance guard: a blocked, abstained, or evidence-needed use is not final if challenge evidence, missing affected-party evidence, changed source relation, changed selected source U.Episteme edition, changed EpistemePublicationRelation occurrence when availability is material, changed publication form, changed evidence carrier, changed representation, or redress can materially change the disposition. If refusal is based on missing evidence, name the missing evidence kind and decision point rather than closing the dispute by vagueness.

Sensitive evidence boundary: use scoped, hashed, redacted, or access-controlled evidence refs when raw carriers would expose personal data, secrets, tokens, privileged logs, tenant identifiers, incident details, security-sensitive traces, or unnecessary identities. A redacted path must still preserve enough recoverability for the relied-on claim, disposition, and contest relation.

Worked source-overread slices:

SliceA.10 usable classificationUnsupported lift
Software supply-chain attestation is cited near a release conversation.The attestation may evidence its named bounded origin, build-method, or production-trace claim. Recover the verifier-rule, holder, and currentness facts that this claim or its verification/use regime requires.Runtime safety, release approval, gate passage, or assurance unless B.3, A.21, or another relation that carries the asserted use is established for that use.
A verified provenance credential, watermark, or authenticity mark appears on a publication face.The mark may evidence where the carrier, signature, assertion, or manifest came from under the verifier regime.Truth of the represented world-state, safety, permission, or adequacy by provenance alone.
A confidence interval or calibration result is used for one reversible act.State the act, context, calibration condition, and bounded evidence use, with the applicable window, unsupported-use boundary, and stop condition.Global readiness, trust, safety, release reliance, or engineering justification.
A generated explanation or summary says a result is reliable.Keep source-finding or explanation use until the operative claim has a recovered source basis or independently established inference/result under its rule and bounded A.10 reliance.Evidence, approval, gate passage, Work or assurance inferred from fluent wording alone.
Contest or redress is claimed after a source relation, selected source U.Episteme, publication occurrence, publication form, or evidence carrier is challenged.State the disputed claim, affected use or harm, available challenge or redress relation, allowed challenge evidence, possible disposition change, outcome route, and reopen trigger. Add future-review responsibility only when that stronger claim is current.Claim truth, compliance proof, completed redress, or social-effect acceptance by appeal-channel presence.
A harmed party gives challenge evidence that could change the disposition, but the receiving System answers “evidence insufficient” without naming the missing evidence kind or decision point.Treat the refusal as RelianceDisposition=reopen or invalid RelianceDisposition=evidence-needed; name the missing evidence kind, decision point, available challenge route, and possible disposition change.Closed refusal, completed redress, or RelianceDisposition=blocked-current-use by vague insufficiency.

A.10:4.6c - Route a Changed Claim Across Several Actual Receiving Uses

Use A.10.1 when a later or replacement source may materially change a claim and the receiving uses must still be found across a bounded frame or closed across several actual uses. A.10 continues to govern each one-use source-to-use account, direct-use relation, and RelianceDisposition. Applying A.10.1 bounds the receiving-use search frame, states source-outward and receiver-oriented coverage and gaps, classifies found candidates as depends, mentions only, or unresolved, and identifies the depends branches that need subject judgment. This includes a conclusion whose scope may change while the decision stands.

If one already-known bounded reliance use is the whole question, apply A.10 and the direct subject guidance. A citation, carrier, declared edge, or graph-reachable node does not become affected merely because the source changed. The completed A.10.1 account cites each independently obtained subject result afterward; it neither replaces that result nor changes A.10’s disposition set.

A.10:4.7 - Causal support in evidence-provenance paths

An A.10 path used for a causal claim cites the C.28 components it carries; it does not compress them into one alternative-valued “support basis”.

causalSupportComponentRefs?: CausalSupportComponentRefs
causalUseSupportResultRef?: CausalUseSupportResultRef

CausalSupportComponentRefs remains defined only by C.28. A.10’s ordinary evidence-provenance path still identifies the source, carrier, Work or data, provenance relations, and bounded use required by this pattern. Inside the C.28 contract, cite only the components the causal claim relies on. When C.28 admits another specialist component, A.10 can cite it through that contract.

Examples:

  • an observational cohort path cites the observation and measurement Work plus observationalOrNaturalBehaviorData; an intervention-effect statement still needs a C.28 identification or design result;
  • a randomized estimate path cites assignment and Work evidence, its identification or design result, estimate, uncertainty, and limits;
  • a prospective counterfactual-sampling path may cite the realizability result, its decision Method, the sampling construction or obstruction required by its status, and any unresolved question; counterfactual-quantity bounds use a separate identification result, and the prospective path claims no performed sampling or data;
  • a performed counterfactual-sampling path cites independently admitted dated sampling Work and the resulting sample or data; add precise assignment-bound attribution only when the receiving support claim uses it. Only the complete Work/data path may support realizedCounterfactualSamplingData;
  • a simulation path cites model output, assumptions, validation, and bounded model use; it does not become realized or interventional evidence by relabeling;
  • a target-trial emulation path cites its TargetTrialMappingResult, including the observational source, protocol-to-data mappings, gaps, residual-confounding assessment, and sensitivity mappings; reporting completeness alone establishes neither identification nor low bias;
  • an off-policy or causal-RL path cites its OffPolicyCausalEvaluationResult with the question, behaviour and evaluation policies, overlap check, supported and unsupported use, and reopen condition. It also cites optional details about history or horizon, confounding, changed endpoints or transport, the estimator, and uncertainty only when they change what the path supports, where that support came from, whether it is current, its bounded use, or when it reopens;
  • a causal-representation path cites its CausalVariableRepresentationRecord with the question, source representation, selection or abstraction Method, representation assumptions, intervention-validity result, supported and unsupported use, and reopen condition. It also cites optional invariance, fidelity, query-preservation, uncertainty, or shift-limit results only when they change what the path supports, where that support came from, whether it is current, its bounded use, or when it reopens;
  • a transport path cites every changed endpoint, assumptions, overlap evidence, formula or comparator, uncertainty or unresolved assumptions, and bounded use carried by its transportability result; and
  • an observationally identified estimate cites both the evidence path and separate identification and estimate results.

What changes in practice: the path exposes where every relied-on component came from and may cite the C.28 support-result episteme. A.10 creates none of the C.28 components, the causal verdict, or downstream authority by carrying their refs.

A.10:5 - Archetypal Grounding

Runtime acceptance from a measurement result. C.16 dated measurement work obtains a pressure measurement result with uncertainty under a named model and calibration; a distinct C.2.1 episteme states it. If the claim that this Work first constituted that episteme is current, A.15.PROD recovers one local entity-inception claim. Separate evaluation work applies the declared G.4 pressure clause through A.6.1 bindings and obtains unknown; another C.2.1 episteme states that verdict. Later C.11 decision work uses the verdict episteme as a premise and defers.

A.10 can trace the source publications, calibration and measurement work, result episteme, evaluation work, clause declaration, bindings, provenance, and any currentness or live rival that affects reliance.

The supplied G.4 unknown and C.11 deferral are separate results, not an A.10 disposition. The bounded claim/use and the evidence basis needed by §4.5’s seven-value rule are not specified here, so the A.10 reliance classification remains unresolved. Select that claim and use and recover their required basis before classifying them; neither unknown nor deferral fills the gap. No ledger edge establishes measurement, verdict, decision, or use.

Complete the bounded classification. Continue the constructed case with claim C in Verdict-e7: “The evaluation of PressureClause-v3 for Batch-B17 returned unknown.” The intended use U is to report that clause verdict for Batch-B17. Stipulate that Verdict-e7 and the current clause are recoverable, the independently checked evaluation bindings select that batch and return unknown, their source and provenance relations hold, and the relevant window covers this use. No unresolved rival changes that reporting claim. These facts supply the missing basis; they are not inferred merely from the word unknown. A.10 returns RelianceDisposition=pass for reporting C within U. The pressure-acceptance verdict remains G.4 unknown, and the separately established C.11 deferral remains unchanged. A pass for reporting the verdict does not authorize acceptance of the batch.

Meta-analysis. Source study publications, datasets, analysis code, inclusion work, statistical method, and synthesis work are recovered by their direct relations. The application of the statistical method and the result relation establish the pooled estimate and uncertainty; the relied-on claim in the result’s C.2.1 episteme states that pooled estimate and uncertainty. A.10 records source identity, transformations, coverage, provenance, currentness, and the bounded clinical or policy use, not a generic validatedBy relation.

Credential display. A credential view can support credential currentness when the issuer or trust-root object and relation, verifier, relying use, and applicable verification facts are recoverable. Retain validity limits when present or required, status-source/register and revocation facts when the mechanism is present or the selected verification/use policy requires them, and holder binding when that claim or regime requires it. A bearer credential need not identify its holder, and a holder need not be the credential subject; neither case relaxes the selected policy.

Permission remains with A.2.8.PER, commitment with A.2.8, an issuing act with A.2.9, and a system-role-assignment occurrence with A.2.1. A status assertion requires its status pattern; an entry predicate requires its defining pattern and A.6.B boundary classification; gate passage remains with A.21. Display presence creates none of them.

A.10:6.1 - Bias-Annotation

A.10 corrects carrier-authority bias and graph-authority bias. A polished badge, attestation, dashboard, generated explanation, or provenance mark can make an unsupported claim look settled; a tidy graph can make an ungrounded edge look like an obtaining relation. The repair is to recover the claim, source, carrier, direct relations, bounded use, and disposition. Add Work and its local result, defining rule, and result episteme when asserted, and currentness or a live rival when it changes reliance.

A.10:6 - Conformance Checklist

  1. Claim: the selected claim or proposition and its C.2.1 episteme are named, together with a separate target claim when the evidence use distinguishes it. An asserted local result retains its defining or testing rule.
  2. Result rule: each asserted local result retains the rule that defines or tests it. Cite the applicable FPF pattern or domain source when that reference is needed. Use E.10.ROLE only for a remaining ambiguity about a technical role claim.
  3. Carrier/source: the selected source episteme and edition, any material publication occurrence, form, carrier, or face, the copy/transform chain, and direct provenance or citation relations are recoverable.
  4. Work: whenever production, interpretation, transformation, evaluation, or reliance is asserted as dated U.Work, point to its basis: the A.13 core including the obtaining assignment first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. Add direct relations, A.6.1 bindings, and resource-use facts only when the receiving claim uses them. Ordinary source-finding action need not be admitted as U.Work.
  5. MethodDescription boundary: when an episteme is identified as a U.MethodDescription, it meets A.3.2’s positive membership rule. Its generic method claims, including intended effects, establish no actual participants, occurrence, use, proof/test event, or result.
  6. Result boundary: domain result, result episteme, carrier, provenance entry, outcome, and later action remain distinct.
  7. Graph boundary: every asserted edge names an independently established direct relation; no edge establishes work, participation, production, result, currentness, reliance, or representation by graph membership.
  8. Time/currentness: edition, window, supersession, revocation, source order, and G.11 result are explicit when they affect use.
  9. Reliance: bounded use and local RelianceDisposition are present. A live rival and stop/reopen condition are included when they affect reliance; any unsupported-use guard satisfies §4.4’s full F.19 test. B.3 opens only for a named assurance claim.
  10. Contest/privacy: the affected party can challenge the claim and disposition, while sensitive carrier access is minimized without erasing recoverability.

A.10:6.2 - Common Anti-Patterns and How to Avoid Them

  • Carrier as truth. Recover the claim and direct source relation; authenticity or availability is not truth.
  • MethodDescription replaced by a plan or run trace. Recover the substantive generic method claims, including any intended effect, separately from a particular plan, dated Work, and actual bindings.
  • Generic result field. Recover the domain result and its defining or testing rule; identify the result episteme separately when its identity matters.
  • Edge as fact. Establish the direct relation first; then let the graph represent or cite it.
  • Provenance as assurance or permission. Enter B.3, A.2.8.PER, A.21, or the pattern that defines or tests the additional claim only when that claim is live.
  • Citation as actual use. Ground the premise/reference/argument relation and any later Work claimed as such.
  • Full dossier by default. Collect only fields that decide the bounded use, consequence, contestability, and reopen condition.

A.10:7 - Consequences

Benefits. Reliance becomes replayable without turning A.10 into an authority over the results it cites. The same path can expose stale sources, hidden transformations, ungrounded work, incompatible currentness, or an unsupported lift from provenance to action.

Trade-offs. Subject-pattern recovery takes more effort than a single evidence edge. The gain is that later users can challenge the claim, work fact, source relation, currentness result, or reliance boundary that failed.

Failure containment. Missing source, work, direct binding, rule for a cited result, currentness, or use relation blocks or narrows only the affected reliance use. It does not authorize a universal evidence or result relation.

A.10:8 - Rationale

Evidence use is a relation-specific claim about why one later use may rely on one episteme. Provenance records make the source history recoverable; they do not create the source facts, local result, truth, work, or use. Keeping the descriptive graph outward-facing keeps each cited result with the rule that establishes it while still making complex source chains inspectable.

A.10:8.1 - SoTA-Echoing

These sources contribute distinctions to source-to-use recovery. Apply their relevant contracts to the selected claim and verification/use regime; identify FPF objects and direct relations independently.

SourcePractical lesson for A.10Limit on reliance
W3C PROV-O, Recommendation 30 April 2013Qualified provenance descriptions and stable source/activity/agent references help recover source, copy, and transform identity. In an A.10 path, every edge cites an independently established direct relation between the appropriate FPF objects.A PROV-shaped graph, wasGeneratedBy label, or qualified relation does not establish FPF Work, participation, result, truth, currentness, or later use.
W3C Verifiable Credentials Data Model v2.0, Recommendation 15 May 2025Distinguish issuer, represented subject, holder, verifier, validity, status, proof, and relying context. Recover the verifier rule and the currentness facts needed for the bounded use and its local disposition. Check validity limits when present or required, status when the mechanism is present or the selected policy requires it, and holder binding when the claim or verification regime requires it. Retain any stronger requirement of the selected policy.The holder need not be the subject; bearer credentials need not identify the holder. A conforming or cryptographically verifiable credential does not by itself create transitive trust, permission, a U.SystemRoleAssignment occurrence, gate passage, assurance, or truth of every represented claim.
SLSA specification v1.2 and in-toto Attestation Framework v1.2, with its Statement/v1 contractDistinguish artifact subject, predicate type, producing context, source inputs, authenticated envelope, verifier expectation, and versioned attestation. Recover the bounded build/source claim and the producing Work or System, verifier rule, holder, and window required by that claim or regime. Keep provenance separate from the reliance decision and exclude a locally plausible unsupported wider use.A signed attestation, SLSA level, or verification summary is not runtime safety, release approval, gate passage, assurance, or proof that an uncited Work/result relation obtains. SLSA and in-toto versions are separate; Statement/v1 alone does not identify an in-toto minor specification version.
C2PA Content Credentials Technical Specification 2.4, April 2026For claim-bound content attribution, distinguish asset/manifest identity, claim generator, assertions, ingredients/actions, signature validation, trust policy, and specification version. Recover the carrier, manifest/assertion, transformation, verifier/trust regime, edition, and currentness window relevant to that claim.A valid manifest, repository receipt, authenticity mark, or visible Content Credential does not establish truth of the represented world state, authorship beyond its assertion, permission, safety, or adequacy.
Mitchell et al., Model Cards for Model Reporting, FAT* 2019, and Gebru et al., Datasheets for Datasets, CACM 64(12), 2021Use intended-use, evaluation-condition, performance/limitation, motivation, composition, collection, and maintenance disclosures to find sources. For every operative claim relied on, recover its source, carrier, and bounded use, plus Work and the local result when asserted.A model card, datasheet, polished summary, or disclosed limitation is not evidence for an unstated claim, performed evaluation, assurance, approval, or deployment permission.

Credential, attestation, documentation and provenance content must be interpreted under the rule for the claim. Their format alone supplies no additional authority.

A.10:9 - Relations

  • Builds on: C.2.1 for claim and result epistemes; E.24.PUB for publication, form, and carrier relations and E.17 for multi-view publication; A.13 for every performer’s local core, A.15.1 for independent dated Work admission, and F.6 only for a current precise assignment-bound attribution; A.6.1 for actual operation bindings; A.15.PROD when entity inception through Work or production completion is current; and the selected A.2-family rule for a technical role claim, with E.10.ROLE only when its meaning remains unresolved.
  • Coordinates with: A.2.4 for first-use evidence/status classification; G.11 for currentness; C.29 for an unresolved mathematical-representation choice, transfer or reliance question; B.3 for assurance; C.16 for measurement; C.28 for causal use; A.19 for comparison/selection; G.4 for acceptance declarations and applications; C.11 and A.21 for option-set choice and gate results, respectively.
  • Constrains: provenance and reliance descriptions only. A.10 does not create another pattern’s result, occurrence, participation, representation, currentness, assurance, permission, commitment, gate, or decision.

A.10:10 - Older source text interpretation and neighboring-pattern notes

Treat legacy names such as manifest, creator, observer, symbol register, SCR, RSCR, MIC, verifiedBy, validatedBy, or evidence path as recovery prompts, not decisions about object kinds or current relations.

  • For a manifest or source register, recover what the claim selects: for example, claim-bearing content, a source register or service, a publication occurrence or form, a carrier, or a provenance description. Recover the source, edition, claim, and direct relations relevant to that use; the old name does not decide among these objects.
  • For a creator, observer, producer, verifier or maintainer claim, recover the System and the participation relation asserted. A recognizable ordinary actor designation needs no further expansion. If dated Work is asserted, recover every performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 only for precise assignment-bound attribution, and other direct relations or A.6.1 bindings only when consumed. A label or assignment alone establishes neither participation nor authority or responsibility.
  • Keep an ordinary method-instantiation note as such. If it asserts performed Work, recover the Method, occurrence, enactment, ordering, participants and result that the claim consumes under their rules; the note’s presence alone establishes none of them.
  • A work result, measurement result, validation result, or verification result label requires the domain result and a separate C.2.1 episteme; the legacy field name establishes neither.
  • Read a resource roster’s claims about resources. Distinguish those claims from the resources and resource-use relations described, and from the carrier or provenance account through which the claims are encountered. Use C.2.1 or E.24.PUB when those distinctions change the use; an ordinary roster citation can remain ordinary.

When older text also claims approval, permission, gate passage, assurance, causality, comparability, representation, publication effect, or decision, use the pattern that defines or tests that additional claim and let A.10 retain only source recovery, provenance, bounded reliance, and contestability.

A.10:10a - Evidence carriers for quantum-like statements

Use A.10 when a quantum-like statement is being relied on. Name the minimal claim, selected source episteme and edition, any material publication occurrence, form, or carrier, bounded use, and RelianceDisposition. Include time/currentness, a live rival, and a locally plausible unsupported-use boundary when they change reliance. Add producing or interpreting dated U.Work, Method, actual bindings, and a Work-to-value predicate only when those facts are independently current. Use C.16 for a measurement claim, the relevant C.26 pattern for actual probe or frame effects, and C.29 only when a separate mathematical-lens choice, transfer or reliance question remains. Use F.9 when the claim needs a Bridge between senses in different contexts; then distinguish that relation from the judgment of its bounded use and tolerated loss. Use B.3 only for a named assurance claim. Consequential uses without one retain their direct safety, permission, gate, release, or other governing rule.

The quantum-like label has no evidence weight. A descriptive graph may represent the source and use relations only after those relations are established.

A.10:10b - C.29 mathematical-lens use relation

Recover the mathematical correspondence and application conditions on which the evidence use depends. Use an adequate domain result directly; use C.29 only when a separate representation, transfer or reliance question remains. A.10 may cite the resulting episteme and record its provenance, currentness, bounded reliance, and later use; an A.10 graph edge does not establish the correspondence. Use C.16 when measurement construction is the question and B.3 only when a named assurance claim is current.

A.10:End

A.10.1 - Revalidate Affected Uses When a Relied-on Source Changes

Pattern type. Method pattern.

Status. Stable.

Normativity. Normative unless a passage is marked informative.

One-sentence summary. When a relied-on claim changes, identify which uses count for the question, look for any that still need to be found, and follow direct uses as far as the change could alter what a receiver can conclude or do. Return each subject result with its limits.

A.10.1:1 - Problem Frame

Use this pattern when a claim-bearing source has been revised, replaced, refined, superseded, or challenged and the practical question is not merely whether the source is current, but which existing results or actions relied on the changed claim.

The primary EntityOfConcern is the bounded source-to-use structure: the changed claim and the direct use relations through which receiving results, decisions, specifications, plans, or actions depended on it. The practitioner is not asked to know every receiving use in advance. The first move is to state the source comparison and the question that determines which receiving uses count.

First useful move. Compare source episteme S0 with later or replacement episteme S1 for the present question Q. Identify what changed in the claim or its applicability for Q, or state what prevents that comparison.

When relevant meaning, applicability and access remain compatible, a repaired reference can be the completed result. It needs no multi-use search or additional subject-result record. A new URL, file, layout, revision label, carrier, or publication occurrence alone establishes no material claim change. Missing claim content or access leaves a scoped gap rather than establishing unchanged meaning.

When a material change warrants revalidating several uses or finding additional ones, state:

The material claim change is ΔC. Uses count for question Q within search frame F; the first known coverage limits are G.

What goes wrong if missed. One team replays every analysis because a version changed. Another preserves every result because the represented world did not change. A third follows citations or graph edges and calls every reachable item affected while missing an undeclared use of the premise. All three replace actual reliance with a proxy.

What this buys. The practitioner can finish with a repaired reference, a qualified subject result, or a scoped limit. When a common receiving question needs an affected-use account, it remains local, replayable, and bounded by its coverage. Inspected unaffected uses remain usable for their stated conditions; unresolved reliance and inaccessible surfaces bound the conclusion. Apply the subject rule to uses classified as depends. Follow each branch through the last use whose conclusion, conditions, required checks or actions could change.

Not this pattern when.

  • Use A.10 when one already-known bounded reliance use is the whole question.
  • Use C.2.1, E.17, or E.24.PUB when source identity, edition continuity, publication, carrier, form, audience, or availability is the live question and no revalidation across several uses is needed.
  • Use G.11 when currentness, decay, refresh planning, or refresh reporting is the live result.
  • Use E.15 when the changed object is one FPF pattern edition; it retains Delta-Class, predecessor-function continuity, pattern checks, and its own change result.
  • Use the direct subject pattern for a world-side change with no source change; examples include a changed sensor, market, organization, configuration, or situation affecting a law’s applicability.
  • Use the direct subject pattern for the judgment or action needed after discovering an affected use. Section 4.5 identifies the governing contributions for those questions.

What changes in practice. The team compares the claims and identifies any missing evidence. If it needs to find affected uses, it states which uses count, searches for them, and checks reliance in the receiving content. It then applies the relevant subject guidance where the changed claim could alter a conclusion or action. A sufficient direct result closes its receiving question.

A.10.1:2 - Problem

Source-change impact is difficult when the receiving uses are partly unknown. A source register may know the source but not every later premise. A receiving decision may use an equivalent claim without retaining the same citation. A dependency graph may include declared edges that do no current work and omit an informal premise that does.

The cheapest apparent boundaries are therefore unreliable:

  1. a file or edition label says too little about changed meaning;
  2. a citation, mention, link, carrier, adjacency, or graph path says too little about actual reliance;
  3. a repository search says too little about surfaces it could not inspect;
  4. stopping at the last changed action can miss a conclusion that needs revision, while following every link can reach results that never used the changed claim, and
  5. a local revalidation summary says too little about the subject result that justified it.

Without a bounded search frame, “no affected use found” can silently mean “we searched one convenient repository.” Without application of direct subject guidance and an independently obtained subject result, “preserved” or “reopened” becomes an ungoverned universal status. The method must make both errors visible without turning every source change into a corpus-wide programme.

A.10.1:3 - Forces

ForceTension
Unknown receiving uses vs bounded effortReceiving uses cannot all be named before discovery, but a global corpus search is rarely justified.
Source-outward trace vs receiver-side realityBacklinks and lineage find declared uses; receiver inspection finds equivalent or undeclared premises. Neither direction alone is generally adequate.
Automation vs judgmentSearch, lineage, traces, and AI can find candidates; the practitioner tests actual reliance in the receiving content under the direct rule.
Local closure vs hidden gapsIndependent resolved branches should finish, while inaccessible or unindexed surfaces must not become implicit evidence of no impact.
Reuse vs changed groundsReuse an unaffected result directly; when a consumed premise changes, recheck the needed condition and retain the result if it remains justified.
Common move vs subject authoritySource-to-use discovery is reusable; materiality remains specific to the subject, including any separate evidence, assurance, or release question.
Short account vs recoverabilityThe result should be usable without a universal impact record, yet another practitioner must be able to reproduce the frame, coverage, direct-use test, and stop.

A.10.1:4 - Solution

Use the outline in 4.1 to locate the current move; sections 4.2–4.7 give its comparison criteria, fields, and stop conditions.

A.10.1:4.1 - Perform the Nine-Step Move

  1. Start from the changed source, not a presumed receiver. Name the predecessor and later or replacement source epistemes, the claim set whose change may matter, and the present question that bounds the search. Leave source identity, edition continuity, access, or applicability unresolved when the required fact is missing.

  2. Compare claims rather than files. Separate changes in proposition, subject, scope, applicability, assumptions, limits, evidence status, and effective conditions from wording, layout, publication, carrier, and revision-label changes. If comparison establishes compatible meaning, applicability and access, finish with any needed reference repair. If comparison cannot establish them, return the material gap; neither branch requires a multi-use search merely to record its stop.

  3. Bound the receiving uses. State which uses count for the question. If the question concerns named uses, identify them. If you rely on a list to cover a wider frame, establish what makes it complete for that frame. Use the search-frame fields in 4.3 when some uses must still be found.

  4. State discovery coverage where you search. Name the source identifiers, aliases and claim addresses used, the included surfaces, the source-outward and receiver-oriented routes, and any material gap in coverage.

  5. Inspect candidate receiving uses. Start with the identified uses. Where others must be found, use search, citations, lineage, traces, indexes or relevant practitioners’ knowledge. Inspect the receiving content and identify the premise, evidence use, operation argument, specification, decision basis or other direct relation through which it used the claim.

  6. Classify and bound reach. Distinguish actual dependence, irrelevant mentions and unresolved uses within the searched frame. Group equivalent irrelevant mentions when one inspected reason covers them. Retain the direct-use basis and gaps that can change the receiving conclusion, without a separate exclusion record for each mention. Follow direct uses while the changed premise could alter a conclusion, the conditions under which it holds, a required check or an action. Supply the discovery-and-reach content needed by each subject judgment.

  7. Apply the direct subject pattern’s guidance. Use the discovery-and-reach statement to apply that guidance to the changed claim, direct use, current conditions, affected reach, coverage limits, and material subject facts. Applying that guidance may show that the proposed dependence must be narrowed or rejected or that stronger evidence is required.

    Use adequate existing evidence and return the supported subject result or its scoped blocker directly to its existing consumers. Further inquiry is selected for the receiving question; a discovery gap alone does not commission Work.

  8. Supply a common account when a receiver needs it. A sufficient direct subject result can finish the use. If another receiving question needs an overview, cite the independently governed results and summarize only the consequences it needs. That summary neither replaces those results nor changes A.10 RelianceDisposition.

  9. Stop at the completed receiving answer. Apply the branch conditions in 4.7. Preserve the coverage and direct-use basis needed for the conclusion returned, including material gaps. Name a next actor or reopen observation when the receiving use needs that continuation. An unresolved independent branch need not delay a completed one.

The numbered outline presents the information dependencies of the Method. Discovery, source recovery, subject inquiry and communication may overlap; the numbering alone establishes neither a lifecycle nor a sequence of dated Work. An A.22.CGUS claim additionally requires its independently identified structure and admission conditions.

A.10.1:4.2 - Compare the Source at Claim Size

Recover each source as a C.2.1 claim-bearing episteme, separately from its file or display. Name the predecessor and later or replacement episteme, relevant claim content, subjects, interpretation bases and effective conditions. Use claim addresses when needed and uniquely resolved; include an edition relation only when established.

Treat a difference as material here only when it can alter a receiving action or result. Useful comparison dimensions are:

Comparison dimensionQuestion
Proposition or resultDoes the later source state a different fact, value, rule, or result?
Subject and scopeDoes the claim now concern a different entity, population, configuration, jurisdiction, interval, or use?
Applicability and assumptionsDid an entry condition, premise, model assumption, or interpretation basis change?
Limits and uncertaintyDid a supported range, exclusion, uncertainty, evidence status, or unsupported use change?
Effective conditionsDid an effective date, validity window, revocation, supersession, or conditional branch change?

Wording can change without meaning changing; one word can also reverse an obligation. A text diff is a locator, not the semantic verdict.

If the same source episteme is merely republished on a new carrier, update the governed identity, publication, representation, availability, or one-use reliance facts through C.2.1, E.17, E.24.PUB, and A.10 as applicable. Do not open the several-use search unless availability itself changes the bounded reliance question.

A.10.1:4.3 - Bound the Search Frame and Make Coverage Reproducible

These fields apply when affected-use discovery is selected. Set the frame before treating found candidates as the universe. Keep it in the existing result or working source at the detail needed to interpret the search. A harmless reference repair opens none of these fields. A claim of no impact across a frame does require adequate coverage and support for that frame.

Search-frame fieldMinimum useful content
Present questionThe decision, result, release, account, or other use for which impact matters now.
Organizational and product boundaryNamed project, product, portfolio, organization, or other working boundary.
Receiving familiesDecision, result, model, specification, plan, account, procedure, or other families in which a use would count.
ConditionsConfigurations, jurisdictions, populations, situations, intervals, horizons, or editions that bound applicability.
Discovery surfacesRepositories, registers, model stores, data catalogues, decision records, account stores, owner-held sources, and other included locations.
Owners and accessContacts, access limits, and unresolved surface ownership or identity when they affect discovery, the conclusion, or a needed continuation.
Explicit exclusionsThe boundary and exclusion reasons needed to delimit this question. Group equivalent exclusions; do not enumerate every non-receiving product, period or mention.

Coverage is adequate only relative to that frame. Use complementary routes:

  • Source-outward discovery starts from source identifiers, aliases, citations, backlinks, provenance, data or model lineage, declared traces and transformations, using claim addresses where they help locate the relevant content.
  • Receiver-oriented discovery inspects the included receiving families for the same or an equivalent premise, limit, parameter, assumption, evidence use, or decision basis, even when the source identifier is absent.

One justified complete index may cover both directions. Otherwise state both routes and their limits.

For every surface, record the query or inspection basis, the source identifiers and aliases used, the date or source value inspected when it matters, and the result or gap. An unsearched, inaccessible, stale, unindexed, or identity-ambiguous surface is a discovery-coverage gap. For an uninspected surface, use occurrence remains unknown; absence from the returned search results establishes neither no use nor no impact.

A.10.1:4.4 - Confirm Direct Reliance Before Following Reach

Search output supplies candidates. The receiving content supplies the reliance test.

Discovery dispositionUse it whenWhat follows
dependsThe receiving action, interpretation, condition, result, check, specification, or public reference uses the changed claim through a direct relation and could change if that claim changes.Include the use in affected reach and prepare a discovery-and-reach statement for application of its direct subject-pattern guidance.
mentions onlyThe content cites, lists, stores, describes, or sits near the source, but its current action or result does not use the changed claim.Exclude it from affected reach. Group equivalent irrelevant mentions and retain a short reason in the existing result when its receiver needs it; no separate certificate is required.
unresolvedThe premise, equivalent claim, applicability, direct relation, receiving content, or necessary access cannot yet be recovered or contested dependence remains.Name the gap that prevents deciding dependence; add a responsible contact when the next action needs one. Continue independent resolved branches, but do not classify this candidate as unaffected.

These discovery dispositions answer whether a found candidate belongs in the affected branch. They are not A.10 RelianceDisposition values. Use A.10 to judge whether one bounded evidence use passes, degrades, abstains, reopens, needs evidence or assurance, or is blocked for current use.

A citation, a present or missing trace, storage, indexing, carrier co-location, succession, ownership, declared dependency, graph reachability, or a shared keyword does not establish depends. A missing trace may be a discovery or coverage gap; it is not impact and it does not prove no impact. Conversely, an undeclared use can depend when the receiving content uses an equivalent premise.

Follow a depends branch through direct use relations. At each receiver, substitute the changed claim for the premise it used. Could that change the result the receiver can support, the conditions under which it holds, a required check or an action? Include that use and apply its subject guidance. A decision can stand while the grounds or limits reported for it need revision. Stop before the next use when the change can no longer affect what that use supports or requires. The affected reach comprises these branches within the stated search frame.

For a branch that needs subject judgment, supply the following discovery-and-reach content at the detail required by its receiver. It may already be present in the direct result; no second statement is needed:

PositionRequired content
Source changePredecessor and later or replacement epistemes; material claim difference; unresolved identity, edition, or applicability facts.
Search and coveragePresent question, bounded frame, included surfaces, source-outward and receiver-oriented routes, explicit exclusions, and known gaps.
Direct useNamed receiving result or action, premise or other direct use relation, current conditions, and the evidence for depends.
Reach and stopFurther uses followed, the last affected use on each branch, what could change there, and why the branch stops. Include mentions only and unresolved candidates when they matter to this judgment.
Subject application and resultThe direct subject pattern to apply, its needed current inputs, the independently governed subject result to obtain, and the existing consumer that should receive that result.

The statement is usable claim content for that subject judgment, not a new mandatory carrier or universal record. A table, list, matrix, or optional G.6 path slice may present it; the representation establishes none of its relations.

A.10.1:4.5 - Apply Direct Subject Guidance and Keep the Result Independent

Discovery and reach classification prepare the branch for subject judgment. Apply the direct subject pattern’s rule or test to each depends branch. Recover or recheck facts about current conditions, evidence, authority, cost, and Work only where those facts can change the independently governed result.

Live questionGoverning contribution to apply
Source and claim identityC.2.1
One bounded evidence or source reliance useA.10
Truth claim or measurement, formal, causal, diagnostic, conformance, comparison, or acceptance resultThe direct definition or test: C.16 for measurement, C.28 for causal support, A.19.CPM for comparison of admitted CHR profiles under an explicit comparator, A.19.SelectorMechanism for selection from admitted candidates under explicit criteria after comparison, G.4 for an acceptance-clause application, and the applicable truth, formal, diagnostic, or conformance pattern.
Choice or decisionC.11 or the applicable subject decision pattern
AssuranceB.3, only when a named assurance claim is current
Authority, responsibility, commitment, permission, gate, or releaseThe direct authority, commitment, permission, gate, or release pattern
Currentness and refresh planningG.11
Planned or performed Work and actual bindingsA.15.2 for a current WorkPlan/PlanItem question; A.13 and independent A.15.1 for a deliberately asserted dated Work; F.6 only for precise assignment-bound attribution; A.6.1 for actual operation bindings
FPF pattern-edition continuityE.15

The practitioner may, by applying the direct subject rule or test, narrow or reject the proposed affected reach. Return the independently obtained result to its receiver: for example, SYSE.14 for an engineering release decision, FIN.4 for revising a financial account or forecast, STR.3 for a needed strategic problem formulation, or STR.4 for needed scenario construction.

When a common account is needed, it cites independently governed subject results and is never their own input. The information dependency is:

material source change → needed discovery and reach → application of direct subject guidance → independently governed subject result → common account, if a further receiving use needs it

A.10.1:4.6 - Complete the Affected-Use Revalidation Account

Prepare a common account only when a receiving question needs an overview beyond the sufficient direct results. Cite each independently governed result used by that overview. A repaired reference or direct subject result can close its own question without this account. Identify the account episteme under C.2.1 when that identity matters; preserving it durably is a separate choice.

Account positionContent when needed for this receiving question
Source comparisonSource epistemes, relevant claim addresses and material change or gap. Include publication, carrier and access distinctions when they affect the conclusion.
Search frame and coverageThe question, boundary, discovery basis and material limits of a search performed. Preserve enough to judge any no-impact claim at its stated scope.
Candidate usesDirect-use bases for affected branches and unresolved candidates that limit the conclusion. Equivalent irrelevant mentions may share one short exclusion reason.
Affected reachThe direct uses on each affected branch, what could change at the last affected use, and why the branch stops there.
Subject applications and resultsThe subject result and its governing contribution, with the conditions and existing receiver material to this overview.
Local summariesThe supported use consequences that the receiver needs, with the cited subject basis.
Reuse and continuationEarlier values and inspected independent results needed for reuse; material gaps and any continuation or reopen condition the receiving use needs.

Preserved, narrowed, reopened, superseded, reliance withdrawn, and blocked are local prose summaries, not a universal status vocabulary. When they summarize subject judgments, they require those judgments’ basis. They replace neither RelianceDisposition nor assurance, permission, authority, release or decision.

Keep earlier source editions and prior results recoverable for their original uses and conditions. A later source does not rewrite what an earlier source meant. Reuse a result directly when its conclusion and conditions remain applicable and the changed content lies outside its consumed basis. If a consumed premise changed, recheck the affected condition or step under the subject rule; retain the result when that check still justifies it, with the updated basis. Unaffected work need not be repeated.

A.10.1:4.7 - Stop, Return Gaps, and Reopen Locally

Close the branch that answers the present question:

Branch takenSufficient completion
Compatible meaning, applicability and access; only a reference or carrier changedComplete the needed reference repair. No affected-use search, separate subject-result record or common account follows merely to certify that stop.
A claim of no impact within a receiving-use frameSupply a bounded frame, adequate discovery coverage and the actual-use basis supporting that claim. Equivalent irrelevant mentions may be grouped. Missing coverage limits the claim; absence of a search hit alone does not establish no impact.
Affected uses need subject judgmentReturn their independently governed supported results or scoped blockers with the direct dependence, affected reach and material coverage limits. Finish independent resolved branches. A common summary follows only when its receiver needs it.
Comparison, dependence, access or subject qualification remains unresolvedReturn the gap and its effect on current use. Preserve independently supported results. Name further Work only when it is needed and selected for the receiving question.

Retain the history and reasoning needed to reuse the result. State who must receive an unresolved action question or what would reopen a continuing use when that information changes practice; a completed small repair need not create a monitoring arrangement.

An inaccessible or unsearched surface is not established unaffected. Reopen locally when a source, claim, direct relation, included surface, subject result or applicability condition changes enough to affect the current conclusion. Use A.15.9 and C.11.DUA when further acquisition is considered; attainable contribution and whole burden govern its selection without weakening support or authority conditions.

A.10.1:5 - Archetypal Grounding

Tell. A source change matters through a claim that a receiving use relied on. Search finds candidates; the practitioner applies the subject rule to determine whether a result or action can change. The following constructed cases use named subject patterns; their stated project facts and results are illustrative.

A.10.1:5.1 - Show: Sensor-Calibration Range

A pump-controller project used edition E2 of a sensor-calibration MethodDescription. E2 states that temperature compensation for module TS-2 is valid from -20 °C to 50 °C. E3 narrows ordinary validity to -10 °C through 50 °C and requires a new calibration Method and evidence below that range. The service-release requirement includes cold start at -15 °C, below E3’s ordinary validity range.

The search frame is the named pump-controller project, TS-2 configurations, current service-release interval, and the model, test, safety, interface-architecture, and decision stores used for that release question. Other hardware configurations are excluded when they do not use TS-2 under the changed condition.

The source-outward route follows exact E2 references and established traces. The receiver-oriented route scans the included stores for the old temperature range and equivalent cold-start premises. Inspection finds:

  • the thermal-model parameter bound depends;
  • the cold-start test condition depends;
  • the safety claim’s use of evidence produced under that condition depends, and the service-release decision relies on that safety claim; and
  • the interface description’s bibliography entry mentions only.

The affected reach stops at the last service-release action that can change. The practitioner applies SYSE.19 to the discovery-and-reach statement. The independently governed engineering revalidation result records tests using the new calibration Method at -15 °C for units S006–S008, supporting that release condition, and leaves S009–S010 without the needed calibration evidence. That result goes directly to SYSE.14, where the authorized release decision remains.

The release coordinator also needs one overview across the unit groups. That common account cites the engineering result, preserves the bibliography-only use and unaffected configurations, and summarizes the affected release branches. The engineering result could otherwise finish its direct receiving use without a second account.

A.10.1:5.2 - Show: Financial Model and Data Refresh

A market-data supplier corrects a yield-curve claim for a named date range. The old claim was used by a valuation model and a cash forecast; a nearby finance memo merely cites the vendor report.

The search frame fixes the corporation and portfolio, jurisdiction, decision date, currency and instrument families, model and dataset inventory, finance-account stores, and the desks and periods explicitly excluded from the current question. Data lineage and source identifiers provide the source-outward route. A receiver-side scan checks model inputs, forecast assumptions, liquidity-account premises, and exposure calculations for the same or an equivalent claim.

The valuation input and forecast assumption are depends. The nearby memo is mentions only. One local workbook cannot be accessed, so that workbook is a discovery-coverage gap; it is not called unaffected. The practitioner applies FIN.17 to the resolved discovery-and-reach statements, retaining finance-specific model, data, jurisdiction, accounting, reconciliation, evidence, and authority judgments within that application. The independently governed finance result goes as revision feedback directly to FIN.4.

The portfolio receiver needs an overview of the resolved models and the inaccessible workbook. That account cites the finance result and retains the workbook’s coverage limit. It adds no exclusion record for each vendor-report mention.

A.10.1:5.3 - Show: A Changed Research Estimate Is Only One Kind of Strategic Signal

An industry-research edition corrects an adoption estimate used as a premise for one strategic assumption and option. Nearby scenario prose cites the report without using the estimate.

The search frame fixes the named strategic decision, assumption and option registers, current scenario set, decision horizon, and source store. Source references and a receiver-side assumption scan identify the relied-on assumption branch as depends and the nearby citation as mentions only. An inaccessible business-unit assumption store remains a coverage gap.

The practitioner applies STR.2 to the discovery-and-reach statement. That application keeps signal qualification, uncertainty, the affected strategic assumption, option or commitment consequences, horizon, and the assumption-impact result within STR.2’s governing scope. The independently governed impact judgment supplies the supported disposition or scoped limit for the affected strategic choice. The nearby scenario prose remains a mentions only use. A market or competitor change with no changed source claim goes straight to STR.2; it is not forced through A.10.1.

A.10.1:5.4 - Reduced Boundary Cases

CaseA.10.1 responseDirect continuation
The same source episteme appears at a new URL with a new layout.Compatible claims, applicability and access; repair the reference and finish without multi-use discovery or another result record.C.2.1, E.17, E.24.PUB, and A.10 when availability affects one bounded use.
A bibliography or catalogue mentions the changed source but uses none of its claims.mentions only; no affected reach. Group equivalent mentions and retain a short reason only when the existing result’s receiver needs it.No subject revalidation follows from mention alone.
A revised service study widens its estimate of weekly demand from 40–60 hours to 35–65. A maintained report gives the estimate for current planning, and a planning brief uses that range.Reassess the current range in both documents. The staffing rule adds capacity whenever even the lower estimate exceeds 30 hours. Both ranges meet it.Update the report and brief for current planning. Preserve the earlier report edition with its original basis. Retain the staffing decision on its revised basis.
Candidate content appears to use the claim, but the premise or applicability cannot be recovered.unresolved with the missing fact.Return the gap now. Obtain the missing basis only when a needed stronger conclusion warrants that contribution.
An included repository is inaccessible or its index is stale.Record a discovery-coverage gap; finish independent resolved branches.Do not call possible uses in that surface unaffected.
The source is unchanged but the represented world changed.Outside this pattern’s selected branch.Use the direct configuration, currentness, change, or decision pattern.

A.10.1:6 - Bias-Annotation

This pattern counteracts version bias, visibility bias, graph-completeness bias, and authority transfer. A newer or official source deserves inspection, but recency and status do not establish materiality for a named use. A visible link or graph path is easier to count than an undeclared premise, and a polished impact report can look like a subject verdict.

The repair is asymmetric: tools may broaden candidate discovery, while inspection of direct receiving content and application of the direct subject rule or test narrow what can be concluded. The pattern therefore favors recoverable local closure over confident global claims. Sensitive repositories may use scoped, redacted, hashed, or responsible-party-attested searches, but their access limits remain visible.

A.10.1:7 - Conformance Checklist

IDRequirementPurpose
CC-A10.1-1 (Source and claim).A conforming use MUST name predecessor and later or replacement source epistemes, exact claim addresses or recoverable content, and unresolved identity or edition facts.Prevents carrier or version labels from becoming source meaning.
CC-A10.1-2 (Material difference).Material claim changes MUST be separated from wording, publication, carrier, layout, and revision-label changes; established compatible meaning, applicability and access MUST take the cheap stop. Missing comparison or access facts MUST remain a scoped limit rather than proof of no change.Keeps harmless republishing cheap and one-word semantic changes visible.
CC-A10.1-3 (Bounded frame).The present question, organizational or product boundary, receiving families, conditions, discovery surfaces, and explicit exclusions MUST be stated before a clean no-impact conclusion. Owners or contacts MUST be named when they affect discovery, the conclusion, or a needed continuation.Makes “where uses count” inspectable.
CC-A10.1-4 (Coverage and gaps).When a search supports the returned impact conclusion, coverage MUST name exact identifiers and aliases, source-outward and receiver-oriented routes or a justified index covering both, included surfaces, and each known unsearched, inaccessible, stale, unindexed or identity-ambiguous surface within the frame.Prevents omitted coverage from becoming evidence of no use.
CC-A10.1-5 (Direct reliance).Every depends disposition MUST cite a receiving action or result and the direct premise, evidence-use, operation-argument, specification, decision-basis, or other relation by which it uses the changed claim.Rejects mention, adjacency, and graph reachability as impact.
CC-A10.1-6 (Discovery dispositions).A searched frame MUST distinguish dependent, irrelevant and unresolved candidates at the detail needed for its conclusion. Equivalent irrelevant mentions MAY be grouped; a separate exclusion record per mention is not required. Discovery values MUST NOT replace A.10 RelianceDisposition or a subject result.Keeps discovery membership distinct from use admissibility and subject judgment.
CC-A10.1-7 (Closure over affected uses).Reach MUST follow only direct use relations and MUST stop after the last receiving action, condition, result, or check that can change.Prevents transitive fanout.
CC-A10.1-8 (Dispatchable statement).Every branch prepared for application of direct subject-pattern guidance MUST carry the changed claim, bounded frame, coverage and gaps, direct use, current conditions, affected reach, stop, and direct subject pattern.Gives the applying practitioner a usable input without a universal impact record.
CC-A10.1-9 (Subject governance).Truth, evidence, causality, choice, currentness, assurance, authority, permission, release, planning, Work, and other subject results MUST remain governed by their direct patterns and continue to their existing consumers.Prevents common discovery from becoming domain authority.
CC-A10.1-10 (Acyclic completion).A common account summarizing a subject judgment MUST cite its independently governed result and MUST NOT be used as that result’s own input. A sufficient reference repair or direct result needs no additional account.Preserves the changed source → subject result → completed account direction.
CC-A10.1-11 (Local summaries and reuse).Local summaries of subject judgments MUST retain their subject basis. Inspected unaffected uses and earlier source/result values MUST remain recoverable for their stated conditions. A changed consumed premise requires the affected recheck; a still-justified result may be retained with its updated basis. A harmless reference repair requires no separate preservation judgment.Preserves valid results without ignoring changed grounds or repeating unaffected work.
CC-A10.1-12 (Honest stop).Completion MUST meet the branch conditions in 4.7 for the conclusion returned. A no-impact claim requires adequate frame, coverage and actual-use support; unresolved coverage MUST NOT be called unaffected. Further records, Work and continuation fields are required only by the receiving use.Makes local closure reproducible without claiming global completeness.

A.10.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Version fanoutA new edition reopens every downstream result.Compare the claims first. Follow direct uses while the changed premise could alter what a receiver can conclude or do.
Carrier preservationThe same world object or familiar file shape is treated as proof that all uses remain valid.Separate source episteme, claim content, publication, carrier, and world-side change.
Search hit equals impactEvery textual hit is classified affected.Inspect the receiving content and direct use relation.
Declared graph equals realityEvery reachable node is reopened and undeclared premises are missed.Combine source-outward and receiver-oriented discovery; establish each relation independently.
One convenient repository equals coverage“No use found” hides inaccessible, stale, or excluded surfaces.State the frame, surface-by-surface basis, explicit exclusions, and gaps.
Unresolved means unaffectedA missing premise or inaccessible source receives a silent clean result.Return unresolved or the coverage gap. Name a responsible practitioner/System only when a selected continuation requires that allocation.
Subject judgment in the common account“Preserved” or “reopened” is issued before engineering, finance, strategy, assurance, permission, or release judgment.Apply the direct subject guidance and pass its independently governed result to its existing consumers. Add a local summary only for a common receiving question.
Completed account fed back into its own resultThe common summary becomes circular evidence for the subject verdict it contains.Keep the acyclic application and direct subject-result-to-consumer route.
Perpetual impact programmeEvery change creates a standing corpus-wide monitoring obligation.Stop at the present bounded question; use G.11 only when a named currentness or refresh need remains.

A.10.1:9 - Consequences

Benefits. Source changes receive effort proportional to their actual use. Teams can preserve inspected unaffected results, expose undeclared dependencies, continue clean branches despite a local gap, and apply the correct governing pattern to each affected question while preserving its evidence and authority boundaries. The account remains usable without a mandatory graph, matrix, workflow, or new ontology.

Costs and limits. Claim-sized comparison and receiver-oriented inspection require judgment. Coverage can be expensive when repositories are fragmented or access is restricted. The method makes those limits visible; it cannot convert incomplete access into assurance. A broad claim with many actual consumers can still produce broad revalidation.

Failure containment. A missing source fact, unresolved direct relation, inaccessible surface, or subject blocker narrows or blocks only the affected frame or branch. It neither invalidates unrelated uses nor supports a global unaffected-use claim.

A.10.1:10 - Rationale

A source change matters through reliance. A.10 handles one known bounded source-to-use account. A.10.1 follows several receiving uses and, when some must be found, bounds the search, uses complementary routes and states the coverage limits.

The search frame solves the unknown-receiver problem without claiming a universal corpus. Complementary discovery solves a second asymmetry: source-side traces miss undeclared or equivalent premises, while receiver-side searches can miss transformed or aliased source content. The direct-use test then prevents either search route from becoming semantic authority.

The subject-application/result sequence is acyclic. The common method can identify where subject judgment is needed, but applying it does not establish engineering release, finance reconciliation, strategic consequence, assurance, permission, or other domain meaning. When a receiver needs an overview, completing it afterward preserves that use without replacing the independently governed results that justify it. A sufficient direct answer needs no duplicate completion.

No new kind or primitive relation is needed. Existing epistemes, direct relations, subject results, Work, plans, publications, and representations can carry every required claim. The method establishes how far to follow a changed claim through its actual uses.

A.10.1:11 - SoTA-Echoing

Problem-solving claimPractice and sourceA.10.1 alignment and working implicationAdoption
Reverify only the slice that can affect the checked property, and reuse an unchanged prior result when its actual dependency is outside the change.Dependency-aware incremental build practice distinguishes actual from declared dependencies (Bazel dependency concepts); change-aware model checking reuses prior results through property-relevant dependency slices (Li, Chen, Huang, and Ding, 2024).Sections 4.3–4.4 require actual receiving-use inspection, closure over affected uses, and explicit reuse conditions. A build or program graph is only an analogy: it cannot establish prose meaning or reliance.Adopt and adapt. Adopt dependency-bounded reverification and result reuse; adapt the dependency test to claim use and independently governed subject results.
Traceability, heterogeneous-model links, and automated analysis can lower the cost of candidate impact discovery, but conflict and semantic judgment remain explicit.A systems-engineering change-impact case connects heterogeneous model semantics, traceability, conflict handling, and versioning (Wu et al., 2025); SYSE.19 supplies the current FPF-aligned engineering host.Section 4.3 uses traces and tools for source-outward discovery, pairs them with receiver inspection, and treats gaps and unresolved candidates as results rather than hiding them. The calibration case in section 5.1 shows the practical boundary.Adapt. Use tools to find candidates and coverage limits; retain direct-use and subject-authority tests.
Broad rerun and graph reach do not replace discovery of actual reliance.Broad replay can be warranted by a broad change or a subject rule. Graph reach alone can omit undeclared uses and include irrelevant nodes; rerunning known consumers does not establish that all consumers were found.Sections 4.2–4.7 bound the frame, inspect receiver-side content and extend revalidation when actual dependence or a material coverage gap requires it.Reject as automatic defaults. Retain broad replay when its frame or subject rule warrants it.

The practical SoTA contribution is the combination of claim-sized comparison, bounded bidirectional discovery, actual-use classification, dependency-closed reach, reuse of unaffected results, and an acyclic subject-application/result sequence. No one graph, repository, or status vocabulary substitutes for that combination.

A.10.1:12 - Relations

Builds on:

  • C.2.1 for source-episteme identity, claim content, subject, interpretation basis, edition continuity, and publication/carrier separation.
  • A.10 for each source-to-use account and its independent RelianceDisposition.
  • A.11 for using existing kinds, relations, results, records, forms, and representations instead of minting an impact ontology.

Coordinates with:

  • G.6 when an addressable evidence or provenance path slice is useful; graph representation remains optional and establishes no reliance.
  • G.11 when currentness, decay, or the completed result justifies a refresh plan or report; G.11’s result shape remains unchanged.
  • E.15 as the specialization for changes to one FPF pattern edition, retaining Delta-Class, predecessor-function continuity, proportionate pattern checks, and its candidate-plus-change-account result.
  • B.3 and every direct evidence, truth, causal, choice, authority, permission, gate, release, planning, and Work pattern governing the corresponding results.

Supplies: A practitioner using A.10.1 obtains a bounded discovery-and-reach statement for application of SYSE.19, FIN.17, STR.2, PSDA.15, or another direct subject pattern when its receiving content relied on the changed claim. The independently governed subject result continues directly to its existing consumers. A common A.10.1 account cites it only when a further receiving question needs that overview.

If an already localized earlier decision use still needs comparison of its relied-on basis with a later result, C.11.DBR prepares that separate current-choice question. Unknown receiving uses stay here, and an adequate subject decision goes directly to its existing consumers. Pass the localized premise and use, not a completed account that already contains the decision to be made.

Constrains: changed-source affected-use discovery and local closure only.

A.10.1:End

A.11 - Ontological Parsimony

Type: Kernel parsimony and admission discipline pattern Status: Stable Normativity: Normative unless a section is marked informative

A.11:0 - Use This When

Use this pattern when FPF work proposes a new U-kind, core relation, dependent durable value, or public structural name and the question is whether existing ontology can express the claim without the proposed durable ontology addition.

Typical moments:

  • a new U-kind seems useful after E.24.UK recovers the candidate object;
  • a proposed root kind may be a dependent value, slot, relation, record, publication form, lens, local frame, or C.3 U.Kind;
  • two candidates overlap strongly;
  • a name is convenient but the ontology may already be expressible through existing patterns.

EntityOfConcern. The parsimony claim for one candidate ontology addition.

First useful move. Recover the candidate with E.24.UK or the subject pattern, then find the best current FPF expression for the receiving claim or use.

In this pattern, an existing governed expression is an expression whose use is defined by an applicable pattern. It can identify an admitted kind or dependent value, slot, relation, record, publication form, lens or local frame, or state a claim governed by the applicable pattern.

What goes wrong if missed. FPF grows duplicate kinds for claims already carried by governed expressions. Later patterns then argue over words instead of recovering the EntityOfConcern, relation or slot, and admissible claim.

What this buys. A small ontology can express rich project situations: A.11 either identifies the existing governed expression that carries the claim or supplies a positive parsimony finding, with a boundary, for the candidate’s complete admission test.

Not this pattern when. The question is only a local display name, publication title, naming taste, or ordinary glossary cleanup. Use the relevant Part F naming pattern unless the name is being asked to carry durable ontology.

A.11:1 - Problem Frame

FPF needs enough primitives to be useful, but every new primitive creates learning cost, bridge cost, and future repair cost. Ontological parsimony is not anti-growth. It tests whether composition, reuse, dependent-value settlement, and subject patterns can express the action-facing claim without material loss. A positive parsimony finding is necessary for the proposed addition; it does not complete its admission.

When source or draft wording proposes a candidate durable value in U.* form, treat that as a proposal requiring an admission decision. Apply A.11 after E.24.UK recovers the governed object and before naming patterns choose a public label.

For a relation-kind candidate, first apply A.6.P. If the participants are exact but no current direct relation expresses the named receiving claim, apply A.6.RCD. Stop when it returns an existing predicate, a local compound claim, or subject-bounded or reusable predicate-definition content. A derived relation-kind candidate continues only when a named use needs stable occurrence semantics and supplies its proposed settlement; an irreducible primitive relation-kind candidate continues only under A.6.RCD disposition 4.

A.11:1.0 - Problem

A useful project word, slot-position label, publication form, diagram element, mathematical lens, or repeated source term can start acting like a durable FPF kind before the governed object and subject pattern are recovered. The problem is to decide whether the candidate preserves an action-facing distinction that the best existing governed expression cannot carry, or should remain that expression or a local name.

A.11:1.1 - Forces

ForceTension
Expressive reach vs. kind inflationFPF must name durable objects clearly, but each extra root kind increases learning, checking, and bridge cost.
Local usefulness vs. universal burdenA local project name may be helpful in one context, while a U-kind becomes a cross-corpus obligation.
Composition vs. material lossExisting slots, relations, and patterns often express the claim, but some candidates preserve a distinction that composition would hide.
Reader clarity vs. ontology compactnessA plain label can help users, but a convenient label must not conceal a relation, slot position, publication form, or mathematical lens.
Growth vs. reopenabilityFPF needs new primitives when problems demand them, but admitted values need reopen conditions when overlap or fuzziness appears.

A.11:2 - Solution

Use four gates to establish the parsimony finding for the proposed ontology addition. Apply every gate to the same candidate, receiving claim or use, and facts. Find the best existing expression first; then state the material loss, overlap discriminator, newly admissible claim or action, and nearest excluded case for that same use. A positive finding continues the complete admission test under E.24/E.24.UK or the candidate’s subject-kind governor; it is not that admission result or project-side permission.

GateTest questionPass condition
CompositionWhat is the best existing governed expression for this receiving claim or use?Pass only when that expression loses a stated claim, boundary, or admissible use.
Non-redundancyHow far does the candidate overlap an existing governed value or relation, and what discriminates the remainder?Pass only when the bounded remainder changes an admissible claim for the same use.
Action-facing contributionWhich claim or action becomes admissible because this addition exists?Pass only when that contribution reaches the named use rather than supplying naming comfort or source prestige.
BoundaryWhat is the one-sentence inclusion test, and which nearest case is excluded?Pass only when both cases can be distinguished from stated facts without private author intent.

The questions can be answered as an ordinary comparison. The following view may help retain or communicate the result. If an E.24-family decision is current, put or reference the parsimony evidence there and resolve this view back to that decision, preserving every required E.24:4.0a value. The view is not a second independently editable admission decision; a local wording or existing-expression answer need not create one.

ParsimonyAdmissionRecord:
  Candidate: candidate examined by this parsimony inquiry
  RecoveredGovernedObject:
  E24FamilySettlementDecisionRef: E.24:4.0a shared decision when one is current
  ReceivingClaimOrUse:
  CurrentFactsRef:
  ExistingExpressionAttempt: best existing governed expression for that claim or use
  MaterialLossIfComposed: lost claim, boundary, or admissible use
  OverlapWithExistingValues: extent plus discriminator
  ActionFacingContribution: newly admissible claim or action
  BoundaryTest: inclusion test plus nearest excluded case
  Disposition: parsimony finding and continuation; cite the separate admission result when current

Possible continuations of the parsimony finding:

  • retain as a root U-kind only with the corresponding complete admission result;
  • retain as a dependent durable value only with its complete root-coupled settlement: same-individual dependence keeps the root individual’s identity and adds a stable membership condition implying root-kind membership for that same individual; identity dependence identifies a distinct individual through a governed relation to a named root individual and all additional discriminators;
  • retain as a local C.3 kind or typed claim under its rule;
  • express through an existing governed expression;
  • keep as source wording or a local name;
  • for a relation-kind candidate, stop at the A.6.RCD existing-predicate, local-compound, subject-bounded-law, or reusable-predicate-definition result; none of these stops admits a relation kind;
  • continue a derived relation-kind candidate only with the required stable occurrence semantics, named receiving use, and proposed settlement; or
  • continue an irreducible primitive relation-kind candidate only when A.6.RCD disposition 4 passes: every accepted derivation loses the action-facing distinction, and independent receiving uses and obtaining, recurrence, applicability, and occurrence-identity laws are supplied.

These are continuation alternatives, not a single admission-result vocabulary. A U-kind decision uses E.24.UK:4.1–4.2: root, same-individual-dependent, identity-dependent, reuse, local-kind, or reject. Only the first three are positive admissions after the complete test; the remaining three are non-admission exits.

A.11:2.1 - Archetypal Grounding - Maintenance

Candidate claimParsimony resultWhy
CoolingPump as a new root U-kindFirst recover the project claim that distinguishes role classification, function, capability, component relation, or another governed expression. If that claim identifies an admitted U.System in a local cooling-circulator role, use the C.3 classification; otherwise return the missing discriminator. Add an assignment occurrence, capability, Method, or Work only when its predicate is current.The useful result follows the grounded project claim; the noun alone neither selects the role reading nor creates a universal kind.
Actuator or another transformer-like nounRecover the governed object and predicate needed by the candidate use; keep an ordinary functional or other subject claim with its rule. Use A.3 for a grounded acting-side claim and A.3.4 to identify any independently claimed actual change. An asserted Work needs the complete A.13 core and independent A.15.1 admission, with F.6 only when precise attribution is needed. If the facts do not select the predicate, return the missing discriminator. A new durable value needs the parsimony finding and complete E.24.UK admission.Neither the noun nor an identified change supplies an acting System, assignment, or Work. Those claims need their own facts.
Provenance-chain wordingUse A.10 for one source-to-use account and bounded reliance. Open G.6 when the use needs path identity, slicing, citation, or local refresh through already established objects and relations. Continue a new durable-value proposal only if the evidence or provenance patterns cannot express the needed claim without material loss; complete admission remains separately required.Parsimony tries subject patterns before minting a kernel addition; a chain label does not itself require an addressable path.
SmallPart or similar vague size classReject or keep local.The boundary depends on private scale expectations unless a measurement or classification pattern supplies a crisp rule.

Worked case: retain a local classification. A maintenance inventory needs to select the installed pumps whose specified function is coolant circulation in Loop-L. The stated project facts admit P-17 as a U.System and establish that it is an installed pump with that function. P-18 is also an installed pump, but its specified function is fuel supply. The project already has a C.3.2 declaration of the local kind CoolingPumpInLoopL whose membership rule is the inventory selection condition; its classification admits P-17 and excludes P-18.

The proposal is to add a root U.CoolingPumpInLoopL with the same membership rule. The four gates give one result. Composition already expresses the selection without loss; the proposed extension coincides with the local kind; the new root admits no additional claim or maintenance action; and the P-18 boundary is already supplied by the local rule. Retain that local classification. If the proposal is carried into an E.24.UK decision, record local-kind through the existing C.3.2 declaration. If later work needs a claim the local classification cannot express, reopen that loss and the applicable admission test; the useful project label remains available in the meantime.

A retained addition also needs a reopen condition. Reconsider the parsimony finding and admission under its governing rule when usage collapses, overlap is discovered, an existing expression becomes adequate, the boundary becomes fuzzy, or the name hides the underlying claim. A scheduled review is useful only when it helps detect such a change.

A.11:4 - Bias-Annotation

A.11 corrects kind-inflation bias. A useful word, field name, record label, or diagram element can start behaving like a universal kind because it appears often, feels important, or has prestige in a source tradition. The repair is ontological: recover the governed object and try the best existing governed expression before admitting a new durable value.

It also corrects false-parsimony bias. A compact ontology is not achieved by refusing every new value. If composition hides a reviewable distinction or blocks an action-facing claim, a positive parsimony finding supports continuing the candidate’s admission test and states its boundary, overlap, and reopen condition.

A.11:3 - Conformance Checklist

CheckRequirement
CC-A11-1The candidate’s governed object is recovered before parsimony is judged.
CC-A11-2If the candidate uses U.* force, E.24.UK is applied before F.5, F.8, or F.18 naming.
CC-A11-3The best existing governed expression is attempted by value. For a relation-kind candidate this includes the A.6.P / A.6.RCD disposition. A representation may supply evidence. A derived relation-kind candidate requires its justified stable occurrence semantics, receiving use, and settlement; only a primitive candidate requires A.6.RCD disposition 4’s irreducibility test. Admission remains the complete governing result.
CC-A11-4Material loss is stated as a lost claim, lost distinction, lost boundary, or lost admissible use, not as naming discomfort.
CC-A11-5Strong overlap lowers or rejects the candidate unless the difference changes claims.
CC-A11-6The parsimony finding identifies the applicable section 2 continuation and, for a relation-kind candidate, the A.6.RCD result. Any U-kind admission cites the complete E.24.UK result rather than treating a continuation as admission.

A.11:5 - Common Anti-Patterns and How to Avoid Them

  • Slot label becomes kind. A system-role designation, transformation-participant label, source-maintenance position, carrier position, or boundary slot is renamed as if the label created a new universal kind; recover the admitted System, local system-role kind or direct relation, any separately obtaining assignment, and Work only when each is current.
  • Publication form becomes ontology. The appearance of a card, record, view, dashboard, figure, or report title does not establish a new durable kind or make a depicted relation obtain. Recover what the claim selects: claim-bearing content, a publication form, a carrier, or another subject. Use C.2.1/E.24.PUB when that distinction changes the claim; a form can be a legitimate subject, and a view-episteme remains distinct from its carrier.
  • Mathematical lens becomes object. A graph, tuple, algebra, metric, coordinate, or threshold does not establish a new durable kind by mathematical appearance. Recover its object and predicate. Use C.29 when a question about choosing, transferring, or relying on a mathematical representation remains unresolved; identify the represented subject, correspondence, and preservation/loss boundary needed for that question. An ordinary threshold, measurement, formal declaration, or other governed claim stays with its subject rule.
  • Local project name becomes kernel vocabulary. A useful project label is promoted to durable FPF vocabulary before composition and pattern expression are tried.
  • Overlap is ignored. A candidate is admitted even though an existing pattern already carries the same claim with clearer boundaries.
  • Parsimony as refusal. A new value is rejected because “fewer kinds is better” even though existing composition loses a distinction users need to claim, compare, repair, stop, or rely on.

A.11:6 - Consequences

ConsequenceBenefitCost or boundary
Smaller durable vocabularyReusing adequate expressions reduces the number of U-kinds that readers must learn and relate across domains.The comparison must show the best existing expression by value. Keep it recoverable when later use depends on it.
Better U-kind admissionsComplete admission requires the parsimony evidence: material loss, non-redundancy, action-facing contribution, boundary test, and reopen condition; these do not replace the other admission conditions.Some attractive names remain local or dependent even when they are common in source traditions.
Clearer neighboring-pattern useReaders know when to use E.24.UK, A.8, C.3, Part F naming, or a subject pattern.The pattern supplies the parsimony finding; the governing admission test decides admission and Part F chooses the public name.

A.11:7 - Rationale

Ontological parsimony preserves FPF’s ability to handle many domains without turning every local distinction into a root object. The pattern follows the same discipline used by E.24.UK: recover the governed object first, then decide whether a new durable value is needed. Using an existing governed expression is a successful result, not a failure to mint a kind.

The practical criterion is not abstract minimalism. A candidate earns a positive parsimony finding only when users gain a claim, comparison, repair, stop condition, reliance condition, or boundary they cannot recover by composition without material loss. Admission still requires its complete governing test. That keeps parsimony tied to FPF’s work-facing purpose rather than to a taste for small vocabularies.

A.11:8 - SoTA-Echoing

Receiving use and reuse. Two historical ontology-engineering contributions supply comparison methods. Noy and McGuinness, Ontology Development 101 (2001), §3, use competency questions to specify the intended application and test whether an ontology supplies enough information, and recommend considering existing ontologies for reuse. Shimizu, Hirt and Hitzler, MODL: A Modular Ontology Design Library (2019), §§3.2–3.3, develop reusable, adaptable modules whose competency questions identify the intended answers. A.11 applies this comparison to the receiving claim or use and the best existing FPF expression.

Construction and identity. Florio and Linnebo, Introduction to Constructional Ontology (2024), §§1 and 3, distinguish constructors, inputs and constructional processes, and show how construction choices bear on identity: a set has its particular elements, while the same sum can have different decompositions. Borgo and Righetti, Towards Applied Constructional Ontology (2025), §§3–5, explore reconstructions of BFO, DOLCE and UFO with explicit choices about dependence, parthood, inherence and participation. Their exploratory comparison helps expose which construction and relation account a candidate uses.

FPF synthesis. Recovering a candidate’s construction and identity establishes what the proposed addition concerns. A.11 then asks whether a new durable kind changes admissible claims, boundaries or work-facing use. Its four gates combine material loss, non-redundancy, action-facing contribution and a boundary for the same candidate, use and facts. The complete E.24.UK admission decides the proposed U-kind’s disposition and root or dependent form.

A.11:9 - Relations

  • Builds on: E.24.UK, A.6.P, A.6.RCD, A.8, C.3, F.8, F.18, and subject patterns.
  • Coordinates with: E.24.CD for candidate detection and E.24.PUB when a publication form or structural name created the admission claim.
  • Does not replace: universal-core testing in A.8, typed claim quantification in C.3, or naming discipline in Part F.

A.11:End

A.11.OP - Decision-Relevant Least Action and Operational Parsimony: Test a Proposed Requirement

Type: Part A pragmatic principle pattern Class: Prag Status: Stable Normativity: Normative unless marked informative

Plain name. Keep only work that changes a substantive choice or result, or protects a condition on which the use relies.

Primary reader. A practitioner or designer deciding whether one proposed action or supporting apparatus should be mandatory.

A.11.OP:1 - Problem frame

Use this when. Use this pattern when someone proposes making an action or apparatus mandatory and a plausible question remains: does this requirement change the subject work, or does it only make the route look controlled?

The primary EntityOfConcern is one proposed mandatory requirement under one declared use and one substantive horizon. The pattern screens the requirement for a substantive contribution. A contribution is necessary, but does not alone make the work obtainable, worthwhile or obligatory; action, apparatus, requirement, and horizon keep their ordinary meanings.

First useful result. Return one of two short answers:

  • retain the requirement for this use and horizon because it has a named substantive contribution and its direct choice, realization, assurance or authority basis justifies requiring the work; or
  • remove the requirement or leave it optional because it has no such contribution, or because a contribution does not justify its burden for this use.

For a proposed inquiry whose worth is still open, use C.11.DUA to compare what can be gained with feasible effort, delay, opportunity cost and downside; use C.11 when a current chooser and options need a local choice. Finish with the supported answer and feasible continuation, which may retain the current action, narrow a claim or decline an unsupported use.

Ordinary use needs no score or separate record. State the disposition together with the receiving decision, result, reliance, or recovery condition that justifies it.

Three recognition cases.

  • A team has added a second status update before a repair decision. Every possible status leaves the same repair action, and no later user relies on the duplicate update.
  • A laboratory considers a bounded probe that leaves today’s setup unchanged but can determine which of two methods will be used next week.
  • A release route contains both a deterministic build step that creates the selected publication and an assurance check whose evidence is consumed by the release decision.

These are one recurring problem across unlike situations: mandatory effort can be ceremonial, immediately productive, decision-relevant only later, or necessary because another use relies on the assurance or recovery condition it preserves.

What goes wrong if missed. Requirements accumulate because each sounds prudent in isolation, while their possible results change no substantive choice and produce no selected result. The opposite error removes exploration, deterministic realization, safety evidence, recovery support, or a small discriminating cue merely because it does not change the next administrative state.

What this buys. The practitioner can remove ceremony without treating the fewest steps as the goal. Useful exploration, realization work, assurance, option preservation, and recovery remain when their receiving use is named.

Not this pattern when.

  • When the question is the force or applicability of an instituted obligation, use its direct authority. Apply A.11.OP only to discretionary apparatus inside the space it leaves. If the present question concerns the obligation’s merits, use C.11.DUA to examine its protective contribution, burden and feasible amendment; that appraisal does not cancel its current force.
  • When several already qualifying alternatives need comparison, use their direct choice, apparatus, architecture, or Method Engineering pattern.
  • When the question is whether a new durable ontology value should exist, use A.11.
  • When the question is how to use an already selected pattern, use E.11.PUA or E.11.PUR.
  • When ongoing Work needs one next action chosen from current facts, use A.15.7.
  • When an available direct-kind apparatus is already being configured for a declared use, use C.19.2 for that application question.

A.11.OP:2 - Problem

Methods and their administrative or support arrangements can accumulate apparatus, such as duplicate reads, checks, and handoffs. Each addition can be defended by a possible future benefit. If hypothetical usefulness is enough, every requirement survives. Attention and elapsed time then move from the subject result to the route’s own states and receipts.

Simple minimization fails in the other direction. A deterministic assembly step may have no rival outcome yet still create the selected result. A decision maker may use new information to change a later policy while leaving the immediate action unchanged. A safety check may return the expected result while supplying evidence on which release reliance depends. A practitioner may use a recovery cue to avoid continuing from the wrong place. Counting branches, steps, documents, or minutes does not distinguish those cases.

The problem is therefore not how to minimize action in general. It is how to admit one proposed mandatory requirement only when a materially plausible difference reaches a named substantive use, without weakening the direct authority that governs the action.

A.11.OP:3 - Forces

ForceTension
Economy versus result productionRemoving ceremony saves effort, but a deterministic action can be the work that realizes the selected result.
Immediate economy versus delayed information valueA probe can leave the next action unchanged while changing a later decision inside the relevant horizon.
Light use versus assuranceOrdinary decisions should stay conversational, but a relied-on exposure, release, rollback, or recovery condition may need evidence.
Local closure versus open-world reuseA declared horizon makes action possible; unspecified future reuse cannot justify every precaution.
Parsimony versus authorityA burden screen can expose ceremony, but it cannot override law, regulation, Guard-Rails, assurance floors, or direct duties.
One general rule versus direct ownersThe recurring admission question should be easy to find, while Method, choice, apparatus, evidence, assurance, and Work claims retain their own patterns.
Plain guidance versus theory launderingUse epistemic and counterfactual distinctions without importing a universal engineering objective from free-energy or physical least-action formalisms.

A.11.OP:4 - Solution

Apply one bounded admission question before making the proposed action or apparatus mandatory.

Admission rule. An author or method designer MUST NOT make a proposed action or apparatus mandatory unless at least one materially plausible result can change a named substantive decision or branch within the declared horizon, the action realizes an already selected transformation or required subject result, or removing it changes a named assurance or recoverability condition on which the declared use relies.

Passing one branch establishes only a substantive contribution for this use and horizon. It does not establish that the work can be obtained or is worth requiring. Complete any live worth or choice question through its direct owner before selecting the requirement.

A.11.OP:4.1 - Name the use and nearest substantive horizon

  1. Name the proposed requirement and the declared use for which mandatory status is being considered.
  2. End the horizon at the nearest named substantive decision, receiving use, selected transformation result, assurance use, or recovery use that can justify the requirement.
  3. Name the possible result or removal consequence that reaches that horizon. Do not use the requirement’s own status, completion flag, receipt, or other administrative transition as its receiver.

The nearest substantive horizon is not necessarily the next event. It may include a later decision when the dependency from the present result to that decision is stated. End it before any further use whose receiver and dependency have not been named.

A.11.OP:4.2 - Compare keeping and removing through three branches

Admission branchPassing conditionBoundary of the result
Decision-changing resultAt least one materially plausible result changes a named subject branch or selection among named alternatives inside the horizon. An information-gathering action passes when one of its possible results changes a later policy even if the immediate action stays the same.The passing basis is the result-to-decision dependency. Obtainability, expected contribution after uncertainty, burden and eventual choice remain open.
Selected realizationThe action performs a required part of an already selected transformation or obtains the required subject result. A deterministic step needs no fabricated rival outcomes.This branch establishes the action’s contribution to the selected result; it presupposes selection and leaves feasibility, authorization, actual Work, and result status to their direct owners.
Assurance or recoverability preservationRemoving the action changes a named assurance or recoverability condition on which the declared use relies.This branch preserves that condition; its required level and evidential basis come from the direct assurance or recovery owner.

Compare the situation with and without the requirement. A passing branch removes the objection that the work contributes nothing. Retain it only as far as its direct basis justifies requiring it. An already selected transformation or established reliance can supply that basis without another comparison.

When a proposed inquiry could matter but its worth remains open, apply C.11.DUA to the demand and receiving question. Identify the attainable observation, what it could change, and its whole cost within the receiving horizon. Compare available continuations through C.11 when a local choice is needed. A useful possible result can still arrive too late, require unavailable means, or cost more than its contribution. Keep the presently supported answer or select a feasible alternative under its limits. Do not invent an OptionSet or an inquiry merely to certify that none is needed.

If no branch passes, remove the requirement or leave it as an optional convenience. Convenience and prior investment do not supply the missing receiving difference.

A.11.OP:4.3 - Judge material plausibility through the subject claim

Materially plausible means more than logical possibility and less than certainty. The direct owner of the claimed consequence supplies its standard of evidence. A low-probability result can remain material when its consequence changes exposure or the admissible policy. A large information volume is material only when some possible result changes a named receiving use.

When the branches cannot be distinguished, name the claim and missing basis and return them to that claim’s direct owner. Keep the qualified answer already supported. A bounded experiment is one possible continuation only when an attainable result and worthwhile contribution justify its whole burden under §4.2. Unresolved usefulness alone does not select an experiment or create permanent mandatory status.

A.11.OP:4.4 - Return authority and claims to their direct owners

Apply this screen only inside the space left by every applicable direct authority. The direct owner establishes the obligation or floor and resolves disputes about its basis or applicability.

When the requirement itself is being appraised, use C.11.DUA to compare the protected bearer and interest, the threshold and horizon, the causal contribution claimed, and who bears the burden. Identify who can amend the requirement and whether that amendment is feasible in time. Keep its merits and present force distinct: neither a protective label nor a burdensome rule settles the merits, and an unfavorable appraisal supplies no unilateral waiver. The legal, ethical and domain claims remain with their direct owners.

A passing branch establishes only the named contribution. Every downstream claim remains with the direct pattern named in Relations; obtain the required result by value instead of treating this screen as its substitute.

A.11.OP:4.5 - Keep the result light and reopenable

For ordinary use, a short answer can be:

Keep <requirement> for <declared use> until <nearest substantive horizon> because <named contribution and the basis for requiring this work>.

or:

Remove or demote <requirement> for <declared use> because keeping and removing it produce the same substantive decision and result and change no relied-on assurance or recovery condition.

If a proposed inquiry has a contribution but is unavailable or not worthwhile, finish with the current supported answer and selected continuation. Keep a short reason or limitation in that result when the recipient needs it; add no empty probe fields or separate omission account.

Record the disposition in the existing record kind appropriate to a named later use when its recipient must cite, compare, audit or rely on it. Otherwise the supported answer is complete.

Reopen the disposition when the horizon, plausible results, selected transformation, direct duty, assurance floor, recovery reliance, or burden-bearing alternative changes.

A.11.OP:4.6 - Keep framework layers distinct

FPF owns this cross-domain admission principle. A Method Engineering DPF may use it when deciding which requirements should be mandatory in a named Method situation; that DPF still owns the Method-specific design. A local practice framework may bind the principle to its own execution and assurance mechanisms. Those mechanisms retain local scope, and the FPF admission condition must still be established for the declared use.

A.11.OP:5 - Archetypal Grounding

A.11.OP:5.1 - Duplicate status update and deterministic publication build

A publication repair route asks for a second status update immediately before the repair decision. The update has the same possible values as the first one. None changes repair, stop, or publish, no receiver cites it, and removing it changes no assurance or recovery condition. The second update passes no branch, so the route removes it or leaves it as an optional convenience.

The same route runs a deterministic build after the sources and publication form have been selected. The build has no decision-changing outcome by design, but it assembles the selected sources into the required publication. It passes selected realization and remains. Any claim about the assembled publication or its release still needs its direct owner.

A.11.OP:5.2 - Exploration whose value appears in a later decision

A maintenance team must choose next week between Method A and Method B for a recurring seal failure. A bounded probe performed today can return one of three observations: evidence favoring A, evidence favoring B, or an unresolved result that triggers a hold. Today’s immediate action is unchanged, but every possible probe result has a named effect on the later Method-selection decision.

The probe passes the contribution screen. Its horizon ends at that named selection and window. The team still has to decide whether to obtain it.

For a constructed comparison, suppose A, B and holding are all available within the applicable operating constraints. The team minimizes expected hours of later rework or deferral over the same maintenance horizon. Its current model gives three conditions with weights 0.4, 0.4 and 0.2:

Selected continuationCondition favoring ACondition favoring BUnresolved condition
Method A0 hours10 hours5 hours
Method B10 hours0 hours5 hours
Hold4 hours4 hours4 hours

These are illustrative planning inputs. On this basis, A and B each cost five expected hours; holding costs four. Suppose the probe distinguishes the three conditions in time. Choosing A, B or holding after its result costs 0.8 expected hours before probe effort.

At one hour for the whole probe, the total is 1.8 hours, so the team selects the probe and the stated conditional continuation.

At five hours for the same probe, still available before selection, the total is 5.8 hours: the completed advice is to hold on the current basis. If the probe cannot return before selection, its information does not serve this horizon. The operating constraints and uncertainty remain visible in each answer.

If instead the team establishes that every materially plausible observation leads to Method A and no other reliance changes, the probe fails even the contribution screen for that use. The team can choose A directly, without inventing a study and then recording why it was omitted.

A.11.OP:5.3 - Assurance evidence with an unchanged operating decision

A pressure-system release check is expected to confirm the current operating decision. The release authority nevertheless relies on its evidence, and omission changes the accepted exposure for release. The check passes assurance preservation even when its most likely result leaves the operating branch unchanged.

B.3, the applicable evidence pattern, and the release authority set the assurance floor and disposition. A.11.OP returns only that the check is non-ceremonial for this named release reliance. A candidate check qualifies here only when the relying condition, exposure change, and direct owner are known.

Now consider a local rule requiring a copy of the same accepted check record. In this constructed case, every relying reader already has the original, and retyping adds no independent verification. It consumes the technician’s only hour available for correcting an identified defect. The local rule owner can amend this copying requirement today while retaining the required check and its accessible evidence. The useful amendment is to use the original record and recover that hour for correction. The protected people and pressure-system condition, the lost correction opportunity and the feasible authority to amend supply the comparison.

If the amendment cannot be obtained in time, the technician follows the applicable requirement or authorized hold route; a favorable merits comparison alone does not authorize omission.

A.11.OP:5.4 - Recovery cue and discriminating language

After an interrupted multi-part analysis, a small progress marker identifies the last closed item and the next item. Removing it can cause the practitioner to repeat completed work or resume from the wrong branch. The marker passes recovery preservation while that continuation use relies on it. If the task is short and the next item is already unambiguous, the marker becomes optional.

In another case, a sentence must distinguish a reusable Method from dated Work that enacted it. The distinction changes whether the practitioner repairs a description claim or a performance claim. The requirement to preserve that distinction passes the decision-changing-result branch for this use. Other terminology remains informative unless a named interpretation or action depends on it.

A.11.OP:5.5 - Speculative compliance without a receiver

A team proposes generating a compliance packet for possible future reuse. No applicable authority or named receiving use has been established for the packet, so it passes no branch and is not mandatory.

If an applicable duty or relying receiver is later established, reopen the disposition under that direct authority. The earlier speculative possibility was not evidence that the duty already existed.

A.11.OP:6 - Bias-Annotation

Scope: Universal for the cross-domain admission question governed by this pattern.

LensLikely biasCountermove
GovParsimony language is used to bypass an instituted duty, safety rule, or assurance floor.Return authority and applicability to the direct law, duty, Guard-Rail, evidence, gate, or assurance owner.
ArchEvery special case receives another owner, or this pattern absorbs Method, choice, Work, evidence, and assurance decisions.Keep one three-branch admission screen and return every downstream claim to its direct pattern.
Onto/EpistAn author declares ordinary words such as action, apparatus, or horizon as new kinds, or treats information volume as decision relevance.Keep the words ordinary and name the receiving decision, result, reliance, or recovery condition.
Prag“Less is better” deletes exploration, deterministic realization, prevention, or recovery; “might help” preserves ceremony forever.Compare keeping and removing at the nearest named substantive horizon through all three branches.
DidThe branch table becomes a mandatory form that costs more than the judgement it supports.For ordinary use, give the disposition and its needed explanation; introduce durable evidence only for a named relying use.

A.11.OP:7 - Conformance Checklist

CheckPassing condition
CC-A11.OP-1 Governed requirementOne proposed mandatory requirement, one declared use, and one nearest substantive horizon are recognizable.
CC-A11.OP-2 Substantive receiverThe justification reaches a named subject decision, receiving use, selected result, assurance use, or recovery use; the requirement’s own route state is not its receiver.
CC-A11.OP-3 Three-branch comparisonKeeping and removing the requirement have been compared through decision-changing result, selected realization, and assurance or recoverability preservation.
CC-A11.OP-4 Material plausibilityEach claimed difference has the basis appropriate to its subject, evidence, risk, causal, decision, or assurance claim; bare logical possibility and information volume are insufficient.
CC-A11.OP-5 Deterministic realizationA required deterministic step is retained when it realizes the already selected result without fabricated outcome branches.
CC-A11.OP-6 Delayed decision valueFor an inquiry proposed for a later decision or reliance, at least one materially plausible result reaches that named use inside the horizon. This contribution is not sufficient to require acquisition; a live inquiry decision also establishes obtainability and worthwhile contribution under its direct owner.
CC-A11.OP-7 Assurance boundaryA retained assurance or recovery action names the relied-on condition and its direct owner; that owner establishes the floor and evidential basis.
CC-A11.OP-8 Disposition boundaryPassing a branch establishes contribution only. The final disposition uses the applicable choice, realization, assurance or authority basis; appraisal of a requirement’s merits remains separate from its current force.
CC-A11.OP-9 Light resultOrdinary use ends in a direct disposition with the basis needed for its use; a durable result uses an existing record kind required by a named later use.
CC-A11.OP-10 Direct-owner returnEach downstream claim remains with the direct pattern named in Relations and is obtained from that pattern by value.
CC-A11.OP-11 Reopen conditionThe disposition names or makes recoverable which change in horizon, result, transformation, duty, reliance, or alternative can reopen it.
CC-A11.OP-12 Theory boundaryEpistemic value and a counterfactual horizon may inform the comparison. Expected free energy, variational free energy, and Hamiltonian least action do not supply a universal engineering admission rule.

A.11.OP:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhat failsRepair
Fewest steps winsDeterministic realization, exploration, assurance, or recovery is deleted because it adds work.Apply all three branches and compare substantive consequences, not step count.
Next-click horizonA probe is judged useless because it changes a later decision rather than the next administrative action.End the horizon at the nearest named substantive receiver and state the dependency.
Infinite downstream usefulnessAny requirement survives because it might help an unnamed future user.Require a named receiver, decision, reliance, or recovery use; otherwise remove or demote it.
Administrative self-receiverA receipt is justified because it updates the route state that exists only to carry the receipt.Name a subject decision or reliance outside the requirement’s own administration.
Fabricated alternatives for deterministic workA build or transformation step must invent outcome branches to look decision-relevant.Retain it through selected realization when it performs the already selected result.
Precaution label as assuranceCalling a step “safety” or “compliance” creates an unsupported floor.Name the direct authority, evidence, exposure, and relied-on condition; return their disposition to the direct owner.
Possible contribution as sufficient reason to require workA probe is demanded because it could matter, despite unavailable means, excessive burden or a missed receiving window.Establish contribution here; complete the live demand or choice question through C.11.DUA or C.11 and retain a useful current answer when acquisition is not selected.
Mandatory parsimony recordThe screen creates the same ceremony it is meant to remove.Give the disposition and its needed explanation in ordinary language; use a durable episteme only when a named later use needs it.
Free-energy or physics launderingExpected free energy, variational free energy, or Hamiltonian least action is presented as proof of a universal engineering rule.Keep only the bounded epistemic, pragmatic, horizon, and risk distinctions; reject mathematical equivalence and mandated scalarization.

A.11.OP:9 - Consequences

The pattern changes practice before a requirement is installed. A designer names the receiving horizon and checks what keeping or removing the requirement changes. Duplicate status work becomes removable without making “less paperwork” a universal argument. Deterministic transformations remain because they produce the selected result. Exploration, assurance, recovery, and small cues have a substantive reason to remain when their delayed or relied-on consequence is explicit. Their direct basis determines whether to require them; a relevant but excessive inquiry can give way to a qualified current answer.

BenefitCost or boundary
Mandatory effort is tied to a decision, result, reliance, or recovery use.The designer must name that receiving use instead of appealing to generic prudence.
Immediate and delayed value are distinguished without a universal calculation.Material plausibility still depends on the applicable subject, evidence, risk, or assurance basis.
Ordinary application stays conversational.Consequential or disputed use may need an existing claim-bearing episteme for its relying consumer.
Direct owners remain intact.The screen decides only whether the requirement is non-ceremonial for the declared use and horizon.
Local closures can remove speculative work and still reopen.A changed horizon, duty, result, reliance, or alternative can reverse the earlier disposition.

A.11.OP:10 - Rationale

Operational parsimony is about relevance, not abstract minimization. The fewest-step method can be wrong when one additional action realizes the chosen result, changes a later policy, or preserves a relied-on condition. The longest method can also be wrong when its extra actions have no substantive receiver. Comparing keeping and removing one proposed requirement makes that difference visible without inventing a global cost function.

The three branches distinguish contributions that a step-count screen would confuse. Decision-changing result recognizes exploration and discrimination. Selected realization recognizes deterministic work. Assurance or recoverability preservation recognizes a named relied-on condition. None alone establishes obtainability, net value or an obligation. Existing selection or reliance can settle the need; otherwise the direct choice or demand method completes it. This preserves useful work while allowing a probe that could matter to lose against an available continuation.

The horizon must be substantive and bounded. A next-event horizon hides delayed information value; an indefinite horizon lets hypothetical future usefulness justify everything. The nearest named receiver is the smallest horizon that can carry the reason and the smallest reopen boundary when the use changes.

The rule coordinates existing decisions, transformations, results, evidence, assurance, and recovery uses. Keeping these objects under their direct patterns preserves FPF layering while giving practitioners one discoverable admission question.

A.11.OP:11 - SoTA-Echoing

Practice questionBest-known line and serious alternativeContribution to the MethodSource roles and limitsReopen condition
How should a process designer recognize information-seeking action whose value appears in a later decision rather than the immediate result?Historical anchors distinguish epistemic from pragmatic value and evaluate present action across counterfactual future policies. The serious default is an immediate-result screen that calls a probe useless when the next action stays unchanged.The default deletes useful exploration. Adapt: the decision-changing-result branch recognizes a probe’s contribution when a materially plausible result changes a named later policy inside the substantive horizon; the receiving choice still decides whether obtaining it is worthwhile.Friston et al., “Active Inference: A Process Theory” (2017), supplies the epistemic/pragmatic distinction; Friston et al., “Sophisticated Inference” (2021), supplies the counterfactual policy horizon. They supply historical discriminators, not evidence of a universal engineering threshold, FPF ontology, or effectiveness claim. Naming the receiving decision makes a delayed contribution visible when the immediate-result screen would omit it.Reopen if stronger current evidence changes the epistemic/pragmatic distinction, defeats the receiving-decision test, or supplies a lower-effort discriminator that preserves the same exploration boundary.
When does relevant uncertainty justify another inquiry?The constructed-value-of-information line separates decision relevance from uncertainty magnitude and examines uncertainty in the prioritization itself. The serious alternative treats either large uncertainty or a possible decision change as a sufficient acquisition rule.Adapt: contribution screens a demand; the receiving decision then compares attainable gain with the whole burden. Use a proportionate sensitivity comparison when plausible input changes could reverse that result.Runge et al., A Simplified Method for Value of Information Using Constructed Scales (2023), supplies preliminary decision-relevance assessment. Davis et al., Constructed value of information with iterative scoring and parametric uncertainty (2026), supplies a later research-priority comparison in which scoring uncertainty can change priorities. Their domain results motivate these distinctions; they do not establish a universal required score, authority or engineering threshold. C.11 and C.11.DUA carry the local choice and advice methods.Reopen when a relevant source or actual use changes how attainable information alters the receiving decision, or defeats the proportionality of the comparison.
Can expected free energy or physical least action serve as a universal scalar rule for admitting engineering actions?The selected critical line shows that expected free energy is not obtained merely by projecting variational free energy forward, while least-action results in the free-energy principle depend on a particular random-dynamical and Bayesian construction. The serious alternative is to transplant EFE, VFE, or Hamiltonian “least action” as a general engineering objective.The transplant launders model-dependent mathematics into authority and can hide the receiving use. Reject: no EFE/VFE/Hamiltonian equivalence or mandatory score enters the Solution. Adapt: judge information-seeking work by a named receiving decision and counterfactual horizon, with risk and ambiguity supplied by their direct owners.Millidge, Tschantz, and Buckley, “Whence the Expected Free Energy?” (2021), supplies failure evidence against the simple VFE-forward account. Friston et al., “The free energy principle made simpler but not too simple” (2023), supplies the model-dependent least-action construction. Neither source establishes an engineering duty, assurance floor, scalar optimum, or universal process law. The qualitative rule asks for the receiving use and its governing conditions.Reopen if a current primary result establishes a transferable engineering admission rule with explicit scope and lower decision error at comparable effort, or if a governed use requires a quantitative comparator under its own direct pattern.

A.11.OP:12 - Relations

  • Classified by: E.3 as one Prag principle. It primarily advances P-1 Cognitive Elegance, P-7 Pragmatic Utility, P-10 Open-Ended Evolution, and P-11 State-of-the-Art Alignment while respecting the other Pillars.
  • Coordinates with: A.11 for whether an ontology addition is needed. A useful operational requirement does not by itself require a new ontology value; an admitted value does not by itself justify mandatory work.
  • Coordinates with: E.11.PUA and E.11.PUR, which govern use, recommendation, coordination, and reuse after a pattern has been selected. A.11.OP asks whether an extra mandatory requirement belongs in the first place.
  • Coordinates with: C.11.DUA for the merits and feasible continuation of an advice or evidence demand, including a single requirement with no live OptionSet; C.11 for a current local choice and probe-worthiness; and C.19.2, A.19, and Method Engineering for their apparatus, architecture or Method comparisons. A.11.OP supplies the contribution screen. These direct owners complete the applicable demand, selection or configuration question.
  • Coordinates with: E.13 for proxy-to-value repair and E.23 for operations inside repeated evaluated improvement. A.11.OP retains the initial action-admission question.
  • Coordinates with: A.3.1 and A.3.2 for Method and MethodDescription identity, A.15.1 for dated Work, and A.15.7 for next-action choice during ongoing Work. A.11.OP governs design-time admission of the requirement.
  • Constrained by: applicable law and regulation, E.5 Guard-Rails, A.10 reliance boundaries, B.3 assurance floors, and any other direct subject or authority pattern for the use.
  • Consumed by: Method Engineering and other DPFs when they decide whether domain-specific requirements or support apparatus deserve mandatory status. Those frameworks retain their domain decisions and evidence.
  • May be specialized by: local practice frameworks for execution and assurance. Their local arrangements remain local rather than FPF authority.

A.11.OP:End

A.12 - Acting-Side Externalization and Reflexive Split: Identify Who Acts on What

Type: Part A architectural ontology pattern Status: Stable Normativity: Normative unless a section is explicitly informative

A.12:0 - Use This When

Use this pattern when self-action or passive wording hides the acting participant or the subject claimed to change, or when interaction is mistaken for parthood.

Typical moments:

  • “the robot calibrates itself”;
  • “the model updates itself”;
  • “the document refreshes its own cross-references”;
  • “the organization corrected itself”;
  • “the system verifies that its own change succeeded”;
  • “the lathe makes the workpiece, therefore the workpiece is part of the lathe during manufacturing”.

First useful move. Name the proposed acting participant and the subject claimed to change, then state the relation between them that matters to your question. For the robot below, the calibration controller acts on the sensor suite. Keep ordinary wording when those participants and their relation are already clear. Use §4.1 when their identities or a System, change, Work or evidence claim need the precise account.

What goes wrong if missed. A controller and controlled part can collapse into one object, an automated publication update can hide its performer, and the performer’s output can be mistaken for sufficient evidence of success. Changing another holon can also be mistaken for containing it.

What this buys. You can locate the acting participant, trace the claimed change, and ask separately what establishes the change or its success. When both participants are distinct parts of one holon, Reflexive Split exposes their internal relation.

Not this pattern when.

  • If the current question is whether a bounded change occurred, use A.3.4.
  • If the current question is whether work was performed or succeeded, use A.15 and A.15.1.
  • If the current question is an assignment occurrence, use A.2.1; if it is a relation among exact local system-role kinds, use A.2.7. For another participation relation, use the pattern that defines that relation.
  • If the current question is evidence independence or source use, use A.10 and the evidence-use or source-use patterns.
  • If the current question is part-whole admission, use A.1, A.14, and C.13.

A.12:1 - Problem Frame

Separate the acting and changed participants before deciding whether the claimed change, Work or evidence obtains. Their participation, System recognition and part-whole relations are separate questions. A self-action sentence may describe internal regulation; §4.2 gives the conditions for that reading.

A.12:2 - Problem

  1. Self-action hides the acting side. “The system changed itself” leaves unclear who acts, what changes, and which participation relation is asserted.
  2. Transformation and work collapse. A bounded transformation, a method, a work occurrence, and evidence of success are treated as the same claim.
  3. Epistemes become agents. An episteme is treated as the acting participant because its carrier or an executing System is described as updating, deciding or verifying.
  4. Reflexive systems become single blocks. A regulator and regulated part are hidden inside one block, so failure analysis and architecture work lose the internal relation that mattered.
  5. Transformation becomes containment. A system changing another holon is treated as that holon’s containing whole.
  6. Evidence becomes self-certifying. The acting system’s own output is treated as sufficient evidence for the success or safety of its work.

A.12:3 - Forces

ForceTension
Causal clarity vs convenient speechEveryday speech compresses “self-repair” and “automatic update”; engineering use needs the acting side and changed object.
Internal regulation vs object collapseA larger holon may contain both regulator and regulated parts; that does not make the regulator and regulated position identical for the current claim.
Automation vs accountabilityAutomated action may require distinct System, role, Method, Work and evidence claims; include each only when the explanation needs it and its basis holds.
Episteme use vs episteme agencyA carrier update, another episteme edition and a changed publication relation need different identity tests (§4.3). A Work performer or U.SystemRoleAssignment holder must be an admitted U.System.
Boundary crossing vs parthoodWhen a boundary-crossing relation independently satisfies the predicate, applicability, and identity rules that define it, it does not thereby make the acting system a part of the changed holon or the larger whole containing it. Without those rules, keep the crossing claim open rather than inferring either crossing or parthood.

A.12:4 - Solution

Separate the acting participant from the subject claimed to change. Add the precise claims needed to explain the case.

A.12:4.1 - Acting-Side Externalization

Either of the two optional A.12 outlines can organize the participants and independently governed claims of a precise change-bearing account. Their fields are prompts for the explanation. Fill a neighboring-claim position only when that claim is needed and its own admission conditions hold:

ActingSideExternalization@Context:
  changedSubjectRef: one exact continuing referent identified by the identity rule that defines that referent
  actingEntityRef: exact U.Entity proposed for the acting side
  actingSystemRef?: U.System, fill only after actingEntityRef satisfies the complete A.1 U.System criterion
  actingSystemA13CoreRef?: A.13 performer basis, required when an actual Work performer is claimed
  a1RecognitionDispositionOrBlockerRef?: required when this account needs an A.1 recognition result and actingSystemRef is unfilled
  actingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment, only when one exact obtaining work-facing assignment is current
  actingSideParticipationRef?: one exact obtaining relation occurrence satisfying the predicate and participant meanings that define the participation, causal, or interaction claim
  transformationRef?: U.Transformation, fill only when A.3.4 identifies a bounded change of changedSubjectRef
  methodRef?
  methodDescriptionRef?
  workPlanRef?
  workOccurrenceRef?
  holonBoundaryCrossingRelationRef?: one exact obtaining relation occurrence satisfying the predicate, applicability, and identity rules that define the crossing relation
  evidenceRelationRefs?

Identify actingEntityRef and changedSubjectRef as distinct participants in the claim. changedSubjectRef is a question-local position, not a U-kind or union ValueKind: its value retains its independently admitted kind and identity rule. A presentation carrier does not become a U.Holon by filling it. Fill transformationRef only when A.3.4 establishes a bounded change of that same continuing referent.

Use the complete A.1 criterion or an applicable established A.1 result before classifying the acting entity as a U.System. When this account needs recognition and it is not established, retain the entity and its recognized | rejected | unknown disposition or blocker. Leave actingSystemRef unfilled until recognition is established; once recognized, it names the same entity under U.System. Tight coupling or membership in a larger holon does not merge the acting and changed positions.

In these two A.12 outlines, @Context denotes a short case label: the examples use RobotInternals, RobotCalibration, DocumentBuild and Machining. Each stated claim keeps its own participants and defining or testing rule. Make the grounds needed by the present use recoverable with that claim, through an existing reference or an ordinary explanation. Neither A.12 outline has a generic context, scope or qualifier position. Ask what the proposed qualifier changes:

  • If claim content, EntityOfConcern or the effective reference scheme changes, C.2.1 identifies another episteme.
  • If the question is whether a U.ContextSlice belongs to a claim’s set-valued applicability boundary, use A.2.6’s U.ClaimScope and membership evaluation.
  • Select A.1.1’s BoundedModelUseStructure only when the decision depends jointly on one model edition’s applicability, actual use in assigned Work, fixed-content expression coherence, applied constraints and complete selection-use frame.

For another condition, state the condition or relation and apply its defining or testing rule. A pattern citation is usually enough to locate that rule. Recover its identity-bearing defining or constraining ClaimGraph only when the graph’s identity changes interpretation, comparison, migration, conflict, publication or reuse. A claim phrase or nearby participant does not fill an A.12 field unless it satisfies that field’s meaning.

Use:

  • A.3.4 when transformationRef becomes current;
  • A.3.1 for Method identity, A.3.2 for MethodDescription admission, A.15.2 for a WorkPlan, and A.15.1 for a dated Work claim; A.15 connects these distinct claims, and a Work occurrence follows the performer/admission/attribution order below;
  • A.2.1 when an exact assignment occurrence becomes current, and A.2.7 only when a relation among exact local system-role kinds becomes current;
  • A.10 when evidence or source independence becomes current;
  • A.1, A.14, and C.13 when holon identity, part-whole, or constructive grounding becomes current.

For a dated Work claim, first establish each actual performer’s A.13 core: an admitted System, a local agential system-role kind and criterion it satisfies, an obtaining assignment, and the scope, situation and window the use needs, supported by evidence. Add an agency-characteristic profile only for a consumed Grade/autonomy/profile claim, a characteristic-dependent local criterion, or an assurance use that requires it.

Then admit the occurrence independently under A.15.1 from its performance history, enacted Method, temporal extent and obtaining containing-System relation.

Only if precise assignment-bound attribution is also claimed does F.6 relate that admitted Work to the same obtaining assignment. A Work-only account stops after admission.

When the receiving question also asks how that Work changed the subject, use A.3.4:4.2.4. Recover the action performed within the Work, the property changed and the subject grounds connecting them. A.6.RCD permits an ordinary compound claim when its base facts and constructor semantics suffice.

A physical account may need the interacting participants, an applicable response law and preparation under A.3.3.TR; a boundary-exchange question additionally selects the quantity, boundary and interval under C.29.BB. Develop only the connection the receiving question consumes. Section 5.3 shows a local contribution claim and the separate question of a durable crossing reference.

A.12:4.2 - Reflexive Split

Use Reflexive Split when the acting and changed participants are two distinct entity parts or subsystems of one containing holon, with an independently obtaining part relation for each. Establish those premises before using this frame; the word “self-” alone does not establish them. If the source supports another reading, keep that acting-side or relation account and leave any unsupported internal-parts claim open.

ReflexiveSplit@Context:
  containingHolonRef: exact U.Holon
  actingPartOrSubsystemRef: exact U.Entity
  changedPartOrSubsystemRef: exact U.Entity
  holonDelimitationRelationRefs?: exact obtaining parthood relations to containingHolonRef
  holonBoundaryCrossingRelationRef?: one exact obtaining relation satisfying the predicate, applicability, and identity rules that define the crossing relation
  actingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment, only when one exact obtaining work-facing assignment is current
  transformationRef?
  methodRef?
  workOccurrenceRef?
  evidenceRelationRefs?

ReflexiveSplit@Context carries no system-recognition position. Its two part-or-subsystem fields identify exact entities, not phases, assignments, relation occurrences, or generic structures. Each filled entity position needs an independently obtaining parthood or subsystem relation to containingHolonRef under A.14 and the direct part-relation specialization.

When the acting-position entity must also be evaluated as a system, state its A.1 recognition result or blocker alongside the part relations. An optional companion ActingSideExternalization@Context can carry that result or blocker: its actingEntityRef identifies that U.Entity; its disposition or blocker remains explicit before recognition; and its optional actingSystemRef may identify the same entity only after A.1 recognition. Do not insert actingSystemRef or an A.1 disposition into ReflexiveSplit@Context.

A temporal phase, system-role assignment, parthood occurrence, software-module description, or selected structure remains a separate object under the identity and relation rules that define it. A software component fills a part-or-subsystem field only when it is itself the exact entity and its direct part relation obtains. If a source supplies only unlike positions such as phases or assignments, state those direct relations and do not force them into this frame.

The minimal rule is:

actingPartOrSubsystemRef != changedPartOrSubsystemRef

for the current change-bearing claim.

For controlled self-change, this split supplies the internal acting and changed participants. Connect their action to the rule or intended result that selects the intervention, its effect on later operation and the consequences used to revise it. C.43:4.1.2 develops that account.

An updater installing a poor setting can satisfy Reflexive Split; whether the update is suitably controlled and improves the result are further questions. If only roles or successive states are established, retain the supported acting-side account without inventing internal entity parts.

A.12:4.3 - Episteme And Publication Cases

If a source says “the document updates itself”, identify the acting participant and decide which changed-object reading the claim needs:

  • Carrier-change reading. One exact publication file, representation carrier, or source-record carrier continues through a separately grounded change under its direct carrier identity rule. It may fill changedSubjectRef as that exact carrier, not as a U.Holon merely by carrier form; use A.3.4 only when the bounded change of that same referent is independently admitted.
  • Episteme-edition reading. Changed claim content identifies another episteme, with the predecessor, successor, and exact edition relation governed separately. Do not call it transformation of one unchanged episteme.
  • Relation-occurrence reading. One exact episteme-related direct relation—for example constitution, empirical grounding, edition, reference, or publication use—obtains when its actual participants satisfy its direct predicate. Its direct identity and change rules determine whether that occurrence continues, ceases, or is replaced. Use C.2.1 for episteme identity and edition distinctions and E.17 or E.24.PUB for publication use. The relation’s obtaining or replacement does not by itself establish a bounded change of one continuing referent. If a change is claimed, identify its continuing subject under its own identity rule and establish the A.3.4 facts before claiming that transformation.

Choose the reading before filling a singular field; carriers, epistemes and relation occurrences are not interchangeable values. Call the acting entity a U.System only after A.1 recognition, and fill a work-facing assignment only when that U.SystemRoleAssignment obtains. Use C.2.1 for episteme identity, E.24.PUB for publication relations and publication-form or carrier identity, and E.17 when the account needs a reader-facing publication form.

A.12:4.4 - No Containing-Whole Inference From Interaction

Treat the interaction and part-whole claims separately. A system changing another holon does not thereby become its part or the larger whole containing it.

For a part-whole claim, use A.14 or the rule defining the part-whole predicate to test parthood independently of the interaction claim.

A.12:4.5 - No Self-Evidence Shortcut

A producer’s output does not automatically establish a claim of success, safety, adequacy or authorization. State the claim you need to support, then use A.10 to identify its evidence and provenance. The producer’s output may contribute when that evidence relation supports the claim.

Use B.3 when a separate assurance conclusion is requested. Introduce an observer, measurement setup or independent source only when its contribution matters to the evidence account.

A.12:5 - Archetypal Grounding (Worked Cases)

A.12:5.1 - Robot Self-Calibration

Source wording: “the robot calibrates itself.”

CalibrationController-R17 acts on SensorSuite-R17; both are parts of Robot-R17. The precise account below takes their A.1 recognition and two independently obtaining A.14 ComponentOf relations as premises, then distinguishes performer admission, Work, attribution and change:

ReflexiveSplit@RobotInternals:
  containingHolonRef: Robot-R17
  actingPartOrSubsystemRef: CalibrationController-R17
  changedPartOrSubsystemRef: SensorSuite-R17
  holonDelimitationRelationRefs: ComponentOf(CalibrationController-R17, Robot-R17); ComponentOf(SensorSuite-R17, Robot-R17), each independently obtaining under A.14

ActingSideExternalization@RobotCalibration:
  changedSubjectRef: SensorSuite-R17, the exact continuing U.Holon identified under A.1 for this claim
  actingEntityRef: CalibrationController-R17
  actingSystemRef: CalibrationController-R17, the same entity after it satisfies the complete A.1 U.System criterion
  actingSystemA13CoreRef: A.13 core for CalibrationController-R17 as precise performer in this action, including CalibrationAssignment-R17 as the same obtaining assignment
  actingSystemRoleAssignmentRef: CalibrationAssignment-R17, one obtaining work-facing U.SystemRoleAssignment held by CalibrationController-R17
  transformationRef: SensorCalibrationTransformation-R17, independently admitted under A.3.4 as a bounded change of SensorSuite-R17
  workOccurrenceRef: CalibrationWork-R17, independently admitted under A.15.1 from its performance history, enacted Method, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to CalibrationAssignment-R17

Robot-R17 remains the containing holon. CalibrationWork-R17 and SensorCalibrationTransformation-R17 are separate admitted objects. The A.13 core includes CalibrationAssignment-R17; after independent A.15.1 Work admission, this case’s additional F.6 attribution uses that same obtaining assignment. The references name the admissions used by the example; each admission still needs its stated basis.

A.12:5.2 - Document Cross-Reference Update

Source wording: “the document updates its cross-references.”

BuildRunner-4 updates the cross-references in PublicationFile-17. BuildScriptEpisteme-9 has the already admitted CrossReferenceUpdateMethod-3 as its exact EntityOfConcern and describes how that Method updates links, satisfying A.3.2. The script is its MethodDescription; BuildRunner-4 is the acting participant. This case follows the publication carrier through the update.

The bounded case-local continuity rule treats PublicationFile-17 as the same carrier only if the file object opened for the build still exists when the build closes, every write asserted to update PublicationFile-17 targets that same open object, and the build neither deletes and recreates that file, atomically replaces it, nor substitutes another carrier. E.24.PUB states which independently identified expression the carrier’s actual state yields; it does not supply this case-local identity rule.

If a continuity fact fails, identify the replacement carrier rather than asserting a transformation of one continuing file. If carrier identity is unresolved, stop before asserting that change. A changed C.2.1 episteme discriminator selects the separate episteme-edition reading.

ActingSideExternalization@DocumentBuild:
  changedSubjectRef: PublicationFile-17, the exact continuing digital U.Entity reidentified by the bounded case-local continuity rule stated above
  actingEntityRef: BuildRunner-4
  actingSystemRef: BuildRunner-4, the same entity after it satisfies the complete A.1 U.System criterion
  actingSystemA13CoreRef: A.13 core for BuildRunner-4 as precise performer in this action, including CrossReferenceUpdateAssignment-27 as the same obtaining assignment
  methodRef: CrossReferenceUpdateMethod-3, admitted under A.3.1
  methodDescriptionRef: BuildScriptEpisteme-9, admitted under A.3.2 as a description of CrossReferenceUpdateMethod-3
  actingSystemRoleAssignmentRef: CrossReferenceUpdateAssignment-27, one obtaining work-facing U.SystemRoleAssignment held by BuildRunner-4
  transformationRef: PublicationCarrierChange-27, independently admitted under A.3.4 from the build boundary, the before/during/after carrier-state facts below, and the bounded case-local continuity rule
  workOccurrenceRef: DocumentBuildWork-27, independently admitted under A.15.1 from its performance history, enacted CrossReferenceUpdateMethod-3, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to CrossReferenceUpdateAssignment-27

A.10 governs source recovery and bounded reliance on the build log for the following carrier-history claims; A.7 keeps the carrier distinct from the episteme it presents.

Before the boundary, PublicationExpressionBearingRelation(PublicationFile-17, CrossReferenceExpression-26) obtains. CrossReferenceExpression-26 is the independently identified ordered text containing the stale link addresses. During the boundary, the same open file object remains in place while its link-address state is rewritten; the build log records no replacement event. After the boundary, PublicationExpressionBearingRelation(PublicationFile-17, CrossReferenceExpression-27) obtains; the changed address strings identify another ordered-text expression.

Both expressions can conform to the same reusable CrossReferencePublicationForm, so PublicationFormBearingRelation(PublicationFile-17, CrossReferencePublicationForm) can remain continuously true through the update when a conforming expression remains recoverable.

Those facts, the build-open/build-close boundary, and the case-local continuity rule ground PublicationCarrierChange-27 under A.3.4. They do not decide episteme identity: if claim content, EntityOfConcern, or the effective reference scheme changed, C.2.1 identifies another episteme and any historical continuation needs a separately governed edition relation.

An episteme-edition case instead identifies predecessor and successor epistemes plus their edition relation. A reference-relation case identifies one relation occurrence and its defining rule. Keep those accounts separate from the carrier-change case; they are not alternative values for its singular fields.

A.12:5.3 - Lathe And Workpiece

Source wording: “the lathe makes the workpiece, so the workpiece belongs to the lathe during manufacturing.”

Lathe-3 is the acting participant; Workpiece-8 is the changed subject. That distinction does not establish that Workpiece-8 is part of Lathe-3. Test any such parthood claim independently under A.14 or its defining part-whole rule. The precise account separates the admitted Work and change:

ActingSideExternalization@Machining:
  changedSubjectRef: Workpiece-8, the exact continuing U.Holon identified under A.1 for this claim
  actingEntityRef: Lathe-3
  actingSystemRef: Lathe-3, the same entity after it satisfies the complete A.1 U.System criterion
  actingSystemA13CoreRef: A.13 core for Lathe-3 as precise performer in this action, including MachiningAssignment-8 as the same obtaining assignment
  actingSystemRoleAssignmentRef: MachiningAssignment-8, one obtaining work-facing U.SystemRoleAssignment held by Lathe-3
  transformationRef: MachiningTransformation-8, independently admitted under A.3.4 as a bounded change of Workpiece-8
  workOccurrenceRef: MachiningWork-8, independently admitted under A.15.1 from its performance history, enacted Method, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to MachiningAssignment-8

MachiningWork-8 and MachiningTransformation-8 are independently identified. To explain their connection, extend this constructed case with the following supplied facts. During the named Work, Lathe-3 performed TurningApplication-8 with CuttingTool-3 on the continuing Workpiece-8. The operation history identifies the actual engaged cutting pass, its tool and workpiece bindings, and its start/end interval. The supplied material-removal account establishes that this pass removed the outer layer of the selected cylindrical surface, reducing its radius from 10 mm to 9.5 mm. Before/after measurements under the same dimensional reference conditions identify the corresponding diameter change from 20 mm to 19 mm as MachiningTransformation-8.

The useful result is the local assertion MachiningContribution-8: this Work included the actual cutting application whose material removal produced this diameter change. Under A.6.RCD disposition 2, its conjunction has these named base facts and their common workpiece and interval; it holds when all those facts hold for the same application and transformation. This supplies one C.2.1 compound claim.

If the history records only a commanded feed and actual engagement is unknown, the connecting claim has missing-information; the independently observed diameter change remains available. Selecting a different physical regime reopens the material-removal account that the connection consumes.

For an ordinary boundary explanation, select the tool-workpiece contact surface and interval. The contact force is the rate of the tool’s momentum transfer to the workpiece across that surface; C.29.BB locates that contribution in a momentum balance. Predicting the workpiece’s motion also needs the other consequential forces and applicable response conditions.

This explanatory claim does not supply an occurrence identity for holonBoundaryCrossingRelationRef. If a further use needs that exact reference, it still needs the crossing predicate, applicability and occurrence-identity rule; their absence is the A.6.RCD missing-governor for that reference. The local contribution and boundary explanation remain usable, and parthood keeps its separate A.14 test.

A.12:5.4 - Bias-Annotation

Bias riskFailureMitigation
Self-action convenience“The system changed itself” hides the acting side and exact continuing changed subject.Recover that changed subject by the identity rule that defines it, identify the acting-side entity, and then state each direct relation used by the claim.
Episteme agencyA document, model, report or source record is treated as acting.Identify the acting entity; apply A.1 if Systemhood is claimed and §4.1’s admission order if Work is claimed. Keep C.2.1 episteme identity and E.17/E.24.PUB publication claims separate.
Containing-whole inference from interactionA system that changes another holon is treated as that holon’s containing whole.Test parthood independently under A.14 or C.13. §5.3 supplies a local contribution and boundary explanation while keeping a durable crossing-reference question separate.
Self-evidence shortcutThe acting system’s output is treated as sufficient evidence by default.Apply §4.5’s claim-first evidence question; add B.3 only for an assurance conclusion.

A.12:6 - Conformance Checklist

CheckRequirement
CC-A12-1A self-action or passive change account names the proposed acting participant and changed subject separately. When the precise frame is used, it identifies one exact continuing changedSubjectRef by that referent’s identity rule and requires actingEntityRef. Fill the optional actingSystemRef only after complete A.1 recognition; it identifies the same entity under U.System. When this account needs an A.1 recognition result and recognition is not established, keep the exact disposition or blocker. A filled transformationRef identifies an A.3.4 bounded change of that same changedSubjectRef. ReflexiveSplit@Context has no system-recognition position; state any needed A.1 recognition result or blocker separately, using a companion acting-side outline if useful.
CC-A12-2A Reflexive Split case identifies distinct exact entity parts or subsystems inside one containing holon, and each position has its independently obtaining direct part relation. Temporal phases keep their phase identity rules; assignments use A.2.1; parthood uses A.14 or the exact part-relation rule; descriptions use C.2.1; selected structures use A.22. None fills an A.12 part position merely by being nearby.
CC-A12-3An acting-side account uses the existing entities and relations it requires. A proposal for a new durable kind, including a transformer, boundary or interaction kind, needs the separate A.11 and E.24.UK admission process.
CC-A12-4Bounded transformation claims require A.3.4; Method identity uses A.3.1, MethodDescription admission uses A.3.2, and a WorkPlan uses A.15.2. For a Work claim, establish each performer’s A.13 core before independent A.15.1 occurrence admission. The profile is conditional as stated in §4.1.
CC-A12-5A system-role-assignment field is filled only by one exact obtaining work-facing U.SystemRoleAssignment; any claim that exact Work was performed under it uses F.6. System-role-kind relation claims require A.2.7.
CC-A12-6Evidence and source-use claims use A.10’s direct relations; a separately current assurance conclusion uses B.3.
CC-A12-7Episteme and publication cases do not assign agency to the episteme or publication form.
CC-A12-8Changing another holon does not make it a part of the acting system. A filled singular crossing reference resolves one exact obtaining relation and its defining rule. If that rule is absent, leave the field unfilled and state the A.6.RCD missing-governor problem: the participants, needed sentence and receiving use. An ordinary explanation is enough; no additional record is required. Any containing-whole claim requires a separately admitted exact part-whole relation.

A.12:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Self-action literalism“The system fixed itself” is accepted as one undivided claim.Identify the acting and changed participants. Use ReflexiveSplit@Context only when §4.2’s two-entity-part and one-holon conditions hold.
Transformer kind inflationThe acting side is modeled as U.Transformer, as a special system kind, or as a provisional phrase placed in a U.System slot.When System recognition is needed, retain the U.Entity and A.1 disposition or blocker until actingSystemRef can identify that same entity as a System. Add a local TransformerSystemRole classification only after A.2/C.3 establishes the system-role kind from its system-candidate domain, work-facing membership distinction, member/non-member boundary and continuity rule. Add participation or assignment only when that relation is claimed.
Boundary as object by wordBoundary or interaction words become durable root objects.Identify the relation actually claimed: holon delimitation, boundary crossing, transformation, signaling, evidence, source use or publication use. Apply its defining or testing rule; §4.1 gives the condition for recovering an identity-bearing ClaimGraph.
Work success by actionBecause a system acted, the work is treated as successful.Use A.15.1 and evidence-use patterns for performed work and success.
Evidence by producerThe acting system’s own output is accepted as enough evidence.Use §4.5 to identify which claim the output supports under A.10.
Manufacturing as containmentA tool or teacher changing another holon is treated as its containing whole.Keep transformation and part-whole claims separate.

A.12:8 - Consequences

Positive consequences:

  • Self-action claims become inspectable without denying real internal regulation.
  • Transformation, Work, assignment and evidence claims can be tested separately.
  • An automated publication update identifies its performer separately from the script and changed content.
  • Internal control loops and automated changes can be traced through their acting and changed participants.
  • Interaction cases retain a separate parthood question.

Costs:

  • When the acting/changed distinction matters, a compact “self-” sentence needs unpacking.
  • Some diagrams need one more internal distinction between acting and changed positions.
  • Supporting a success or safety claim can require evidence beyond the producer’s success message.

A.12:9 - Rationale

The acting/changed distinction helps trace an internal control loop, locate the performer of an automated update and separate a produced result from the evidence supporting a claim about it. Those questions can require different admissions; §4.1 gives their conditional routes.

A.12:10 - SoTA-Echoing

Source or practiceContribution to the distinctionFPF use
Control practiceDistinguishing controller, controlled object, feedback and plant structure helps inspect regulation.Use Reflexive Split for internal regulation when the two-entity-part and one-holon conditions hold.
Constructor theory: introductory accountA substrate undergoes a specified possible task; a constructor retains the capacity to perform the task again.Keep the changed substrate and proposed acting entity distinct. FPF separately requires A.1 for a System claim and A.3.4 for a bounded change claim.
Assurance and evidence practiceA produced result and evidence supporting a claim about it are different objects.Use A.10 for the claim’s evidence and provenance; use B.3 when an assurance conclusion is requested.
Software and automation practiceAn automated-update sentence can hide the distinction between the executing entity, script and changed object.Identify the acting entity and apply A.1 before calling it a System. Apply A.3.2 before treating the script as a MethodDescription; keep change, Work and evidence claims separate.

A.12:11 - Relations

  • Builds on: A.1 for holon and System admission, A.2.1 for a directly declared assignment species and its obtaining occurrence, A.2.7 for relations among exact local system-role kinds, and A.3.4 for bounded transformation.
  • Coordinates with: A.10 for evidence, A.14 and C.13 for part-whole claims; A.3.1, A.3.2, A.15.2, A.15.1 and the integrating A.15 for Method, MethodDescription, WorkPlan and Work; C.2.1 and E.17 for episteme and publication cases; and B.2.5 for supervisor-subholon feedback.
  • Does not own: transformation occurrence evidence, work success, evidence independence, part-whole admission, MHT declaration, or the architecture of the larger holon.

A.12:End

A.13 - The Agential Role & Agency Spectrum

Status: Stable

A.13:0 - Use This When

Use this pattern when a precise claim of agency matters: which System qualifies for a local goal-directed system-role kind, and which assignment actually holds for the action in question? Start with that System, the kind and criterion it satisfies, the obtaining assignment, and only the scope, situation and window the use needs. Keep the evidence for those facts recoverable. The first result is a supported agency claim, not a five-characteristic measurement exercise.

Open the characteristic profile when a Grade, autonomy or profile claim consumes it, when the local kind’s criterion depends on a characteristic, or when a named assurance use requires it. Otherwise stop at the core. A characteristic-only claim about an admitted System need not assert a system-role assignment.

Ordinary use of “agent” does not by itself require this precise account. Use A.12 for an acting/changed-participant question and A.15.1 for whether a dated Work occurrence took place.

A.13:1 - Intent & Context

A.13 separates a precise agency claim from a claim about the holder’s agency characteristics. The former identifies a System’s local kind and obtaining assignment; the latter states the characteristics the receiving use needs.

A.1 establishes the holder as a U.System. A.2 and A.2.1 distinguish a local system-role kind, classification by that kind, and an obtaining occurrence of a directly declared U.SystemRoleAssignment species. A.12 helps recover the acting and changed participants when that distinction matters.

This distinction serves three uses:

  1. Define agency as an assignment claim: a local agential system-role kind is assigned to a U.System through an obtaining U.SystemRoleAssignment, rather than being an intrinsic holon type.
  2. Describe a multi-dimensional spectrum of agency through the agency-characteristic profile when its values are needed.
  3. Provide a didactic grading system for communicating a profile summary.

A.13:2 - Problem

Treating agency as an intrinsic property or a mere label hides different questions:

  1. Episteme-as-Actor: When “the specification decided to update the system” hides the actor, use A.12 to identify the proposed acting entity. A precise agency claim needs that entity admitted as a System under A.1, distinct from the specification under A.7.
  2. Type Inflation: Adding a root agent kind duplicates existing ontology when System, local kind and assignment already express the needed claim. The same System may qualify for an agential system-role kind and receive an assignment in one working situation but not another. Scope and window remain separate; a root label alone does not express these differences. A.11 tests a proposed ontology addition for material loss under the best existing expression.
  3. Unsupported Claims: A label such as “agent” supplies neither the local kind criterion and obtaining assignment nor evidence for a claimed autonomy profile. Those claims need their own support under A.10.
  4. The Binary Trap: “Agent/not-agent” alone does not distinguish a thermostat’s feedback, a cruise-control system’s prediction and a strategic robotic swarm’s self-learning capabilities.

A.13:3 - Forces

ForceTension
Scientific Fidelity vs. SimplicitySpectrum accounts draw attention to different capacities and levels of agency. A teachable summary still needs to state which characteristics and measurement bases it uses.
Role vs. TypeThe same System can qualify for a local agential kind and hold its assignment in one situation but not another. Characteristic claims are additional when consumed by the use.
Measurement vs. LabelA quick label such as “Level 3 agent” summarizes more detailed claims. When assurance consumes agency characteristics, it needs their evidence-backed values, not that label.
Collective AgencyA precise agency claim for a team or swarm needs the collective admitted as a U.System, not merely named as a group.

A.13:4 - Solution

Establish the agency core when making a precise agency claim. Build the characteristic profile when the receiving claim requires it; use a Grade only as its didactic summary.

A.13:4.1 - The Core Definition: Agential participation through an exact system-role assignment

An ordinary-language “agent” is not a fundamental FPF type. When a precise agency claim is needed, name four things:

  1. the acting holder recognized as a U.System;
  2. the exact local agential system-role kind whose membership criterion the holder satisfies;
  3. an occurrence of a directly declared U.SystemRoleAssignment species that assigns that kind to the holder and actually obtains; and
  4. any claim scope, working situation, and time window needed by the intended use, kept separate from the assignment’s identity.

This keeps a useful ordinary word without creating a universal Agent or AgentialRole kind. Classification by the local kind does not establish an assignment or performed Work. An episteme cannot be this assignment’s holder because the holder must be a U.System. Support each core fact under its own criterion, using characteristic results when that criterion requires them. A characteristic-only claim about an admitted System need not add an assignment.

A.13:4.2 - Local Agential System-Role Kinds and Their Specializations

  • Local agential system-role kind: A practice or source may define a local kind whose stable work-facing contribution is goal-directed action. The kind classifies candidate Systems under its own criterion; it is not a universal root kind, an assignment occurrence, or Work.
  • Specialized agential system-role kinds: A local practice may distinguish transformation, observation, planning, or another contribution when it supplies a criterion for the distinction. An assignment to one such kind establishes only that assignment; any transformation, observation, plan, or performed Work still needs its own claim.

A.13:4.3 - Measuring Agency: The Agency Characteristic Profile and the Spectrum

The agency-characteristic profile describes distinct capabilities of the holder. Use it for a consumed Grade/autonomy/profile claim, a characteristic-dependent local criterion or a named assurance use that requires it. A.13 defines this domain profile; A.17, A.18, A.19, C.16 and A.10 govern characterization, measurement and evidence.

The following descriptions state what the five characteristics concern. A measured value also needs its declared characteristic definition, scale, measurement method and evidence basis under the patterns above. Each measurement names its holder and, where relevant, task family or work target, claim scope, situation and time window. A.10 governs the claim’s evidence and provenance.

  1. Boundary Maintenance Capacity (BMC): The ability of the System to maintain its own structural and functional integrity against perturbations. The maintained property is the holder’s integrity, not merely the value it controls.
  2. Predictive Horizon (PH): The temporal or causal depth of the holder’s internal model. State which depth the claim uses; the horizon is distinct from prediction accuracy.
  3. Model Plasticity (MP): The rate at which the holder can update its internal model in response to prediction errors. Describe the model update and its rate; evaluate capability acquisition separately under E.10.LRN.
  4. Policy Enactment Reliability (PER): The probability that the holder will successfully execute its chosen U.Method under operational conditions. The event is successful Method execution; a result or safety claim needs its own basis.
  5. Objective Complexity (OC): A measure of the complexity of the objective the holder can pursue, from simple set-points to abstract, multi-scale goals. These examples distinguish objectives; a complexity comparison needs a declared criterion and scale.

Build the profile for its receiving use. First name the claim or decision that needs a characteristic. Select the characteristics whose values can change that answer. Keep the holder, configuration, task or Method, assistance and relevant conditions common across the results you combine. Reuse a sufficient existing account; a characteristic-only claim can remain separate from an assignment claim.

For each selected question, use or construct a domain definition that connects an observable distinction to a characteristic value. A.17 and A.18 separate the characteristic, its scale and allowed operations from preference or scoring. C.16 supplies measurement discipline. Explain how the observation distinguishes the values needed by the receiving use. If the same observations fit materially different values, obtain a discriminating observation or retain that uncertainty.

CharacteristicConstruct the measurement needed by the use
BMCIdentify the holder’s structural and functional properties to preserve, the perturbations, tolerated loss and recovery, and external assistance. Test that integrity condition on the specified cases. Report the perturbations withstood, a supported limit or a success proportion for a declared population.
PHName the internal model and choose temporal or causal depth. Establish the future interval or kind and number of causal transitions that the model represents. Report that extent in its declared units; assess prediction accuracy separately when the receiving use needs it.
MPIdentify the changing model, prediction-error signal, measure of model change and time or budget denominator. For a scalar parameter, state whether the result uses net change or total variation; these differ when updates oscillate. Interpret the achieved rate under its observed conditions.
PERIdentify the chosen Method, successful-execution event, operational population and probability model. Include required operations and permitted stops in the event definition. A sample frequency estimates a probability only under the stated sampling and inference assumptions.
OCDescribe the objective and select a complexity criterion, such as independently adjustable targets or a declared rubric for coordinating conditional goals. Establish that the holder can pursue an objective with that structure. A demonstrated objective can supply a result without establishing the holder’s maximum capacity.

Retain each value or admissible value range, uncertainty, evidence and applicability. An unmeasured characteristic remains unmeasured. Evidence that a holder has no predictive mechanism can establish zero PH; missing information about that mechanism cannot. A model-update rate and a task-performance improvement answer separate questions. A.13:4.3.1 connects a supported adaptation result to the task-family claim.

Assemble only the results that the receiving use consumes, and apply its comparison or decision rule. Values require compatible meanings and conditions, or a justified transformation, before comparison. A faster model change can be useful correction or harmful oscillation; the receiving objective determines that preference. Use the Grade mapping in §4.4 only when a didactic summary is wanted. After a change, reopen the dependent result: new measurement error changes its warranted value range; a tighter task tolerance can change suitability while leaving that range intact; a new model can require a different PH or MP definition.

A.13:4.3.1 - Task-family specialization claims

When assessing a holder’s time-to-usable specialization, name the holder, TaskFamily and work target. Use C.22 for the task anchor and C.22.1 for adaptation time or budget to the declared work-measure threshold. Keep task family, work target, claim scope, situation, measurement window, threshold, adaptation budget and provenance basis distinct where the claim uses them. The same holder can show different specializations for different task families; this does not establish greater intelligence in general or a new U-kind.

For a task-family comparison described as low-human-overlap, use C.22:5.2.1 to state the human-practice reference set, correspondence and coverage rule. Newly discovered families retain the same explicit task-family, evidence and reuse-window conditions. Such a comparison characterizes the task-family relation; the holder’s specialization still needs its own result.

A.13:4.4 - The Agency Grade (Didactic Layer)

Engineers and managers can use the Agency Grade as a non-normative, didactic summary of a profile. The scale runs from 0 to 4; an assurance use that consumes agency characteristics needs their supported values, not this summary.

GradeLabelIllustrative agency-characteristic profileArchetypal Example
0Non-AgentialBMC ≈ 0, PH ≈ 0, MP ≈ 0An admitted System whose supported profile has the stated values. A document or another non-System has no Agency Grade.
1ReactiveBMC > 0, PH ≈ 0, MP ≈ 0A thermostat; a simple feedback controller. Follows fixed rules.
2PredictiveBMC > 0, PH > 0, MP ≈ 0A model-predictive controller with a fixed model; a chess engine that plans moves but doesn’t learn new strategies.
3AdaptiveBMC > 0, PH > 0, MP > 0A self-calibrating sensor system; a machine learning agent that updates its model with new data.
4Reflective/StrategicHigh BMC, PH, MP, PER, and OC. Capable of meta-cognition (reasoning about its own reasoning) and pursuing abstract goals.An autonomous R&D system; a cohesive, self-organizing DevOps team.

The Grade 0 label summarizes a profile; it does not settle the separate local-kind classification or assignment claim.

The profile states characteristic claims and their supporting evidence; the Grade is a pedagogical summary. An actual Grade claim needs a supported profile and a stated mapping from its values to the label, including thresholds when the mapping uses them. Without that basis, leave the Grade unresolved. CC-A13.3 governs that support; CC-A13.4 excludes the Grade as a normative premise.

A local mapping may cover only the profiles needed for its communication use. State non-overlapping conditions for the labels it assigns and leave other cases unclassified. When a supported value is a range, check the permitted values against those conditions. One label is supported only when all consequential admissible values select it; otherwise retain the uncertainty or alternatives allowed by the mapping. Preserve the characteristic results that the label does not summarize.

A.13:5 - Archetypal Grounding

Start with the controller: “Thermostat_Model_T800 holds T800-home-heating-assignment as HomeHeatingController for household-temperature control.” In this constructed case, Thermostat_Model_T800 identifies one installed unit, admitted as a System, in House-H1 from 08:00 to 12:00 on Day-D.

The local HomeHeatingController criterion is the ability to read the household temperature and selected set-point, command heating below the set-point and stop heating at or above it. The stipulated device behavior satisfies that criterion at the selected 21 °C set-point. The directly declared HomeHeatingAssignment species assigns a qualifying System to that kind when the household controller designation and enabled control connection obtain; both hold for T800 in that household and window.

The core result is that this System qualifies for HomeHeatingController and holds the obtaining assignment for the stated use. No Grade or autonomy measurement is needed for that result. If the household withdraws the designation while the device retains its capabilities, the assignment ceases under its rule; classification may remain true, and the precise agency claim must change. The table gives further schematic variations for individual and collective Systems, then a knowledge-artifact contrast. Its local kind names and profile/Grade assumptions are illustrative.

ArchetypeHolder (U.System)Illustrative local agential system-role kindDistinct obtaining assignment occurrenceAgency-characteristic profile sketch (illustrative assumptions)Illustrative Agency Grade
Simple ControllerThermostat_Model_T800HomeHeatingControllerT800-home-heating-assignment assigns Thermostat_Model_T800 to HomeHeatingController for household-temperature control.BMC: High (assumed). PH: Zero (no prediction). MP: Zero (fixed logic). PER: Very High. OC: Low (single set-point).Grade 1 (Reactive)
Advanced ControllerPredictiveCruiseControl_v3VehicleDynamicsControllerPCC-v3-vehicle-dynamics-assignment assigns PredictiveCruiseControl_v3 to VehicleDynamicsController for the driving situation supplied by the working case.BMC: High. PH: High (predicts traffic flow). MP: Zero (fixed model). PER: High. OC: Medium (optimization).Grade 2 (Predictive)
Learning SystemSelfCalibratingSensorArrayIndustrialProcessAdaptiveControllersensor-array-process-adaptation-assignment assigns SelfCalibratingSensorArray to IndustrialProcessAdaptiveController for the calibration task family and window supplied by the working case.BMC: High. PH: High. MP: Medium (assumed). PER: High. OC: Medium.Grade 3 (Adaptive)
Collective acting holderDevOpsTeam_Phoenix (a collective U.System)ProjectPhoenixDeliveryCoordinatorphoenix-team-delivery-assignment assigns the collective System DevOpsTeam_Phoenix to ProjectPhoenixDeliveryCoordinator for the project work being claimed.BMC: High (assumed). PH: High (release planning). MP: High (assumed). PER: Medium-High. OC: High (abstract business goals).Grade 4 (Reflective/Strategic)
Knowledge artifactNo acting holder. ISO_26262_Standard.pdf is a file carrier; the selected standard edition and any exact claim episteme made available through it remain distinct.N/AN/A: neither the carrier nor an episteme is a U.System, so neither can receive an agential system-role assignment.N/AN/A — no System holder or agency-characteristic profile

The profile values above are illustrative assumptions, not measured results. The case explanations support narrower statements:

  • The thermostat “maintains temperature” in the household-control use. That does not establish the thermostat’s own structural and functional integrity under perturbation; BMC: High remains an assumption.
  • “Learns drift” leaves the sensor’s model/parameter-update versus capability-acquisition meaning unspecified. MP: Medium does not supply that missing account.
  • The team’s retrospectives name an activity, not a measured rate of internal-model update. MP: High remains an assumption; E.10.LRN keeps model change and capability acquisition separate.

Key takeaway from grounding: The same ontology works for a thermostat, a predictive controller, a learning System, and a collective System: classification by a local kind and an obtaining assignment are both stated, while scope, situation, Work, evidence, profile, and grade remain separate. An exact ISO claim episteme may be cited in an A.10 evidence-provenance account or a B.3 assurance claim; any direct relation relied on by that account or claim must actually obtain under its own defining rule. The file carrier bears an expression conforming to a publication form.

A.13:5.1 - Construct a measured profile for a calibration use

Consider one installed SensorArray-S7, admitted as a System. This constructed case supplies its local IndustrialProcessAdaptiveController criterion and obtaining assignment: S7 detects deviation from a reference signal, selects a permitted offset update or stops calibration on an invalid input, and has the designation and enabled connection for that control. Those premises establish the agency core. The additional question is what its bench profile shows and whether calibration reaches residual error at most 0.1 °C within three minutes.

The measurement definitions and observations below are stipulated case inputs. The internal sensor model is z = r + b, where z is the raw indication, r the reference value and b the estimated offset. The reference relation establishes a constant raw offset z - r = 0.6 °C for this test. The admitted OffsetUpdateMethod-3 reads that reference, checks the allowed update and commits the new offset once per minute:

b_next = b + 0.5 * (z - r - b).

Starting at b = 0, the three committed offsets are 0.3, 0.45 and 0.525 °C. The measurement basis bounds the total uncertainty in interpreting residual error by ±0.02 °C. After the third update, that residual therefore lies in [0.055, 0.095] °C, satisfying the 0.1 °C target. The following profile keeps the other supported characteristics separately interpretable.

ResultBasis and use boundary
BMC: integrity maintained in four of four specified perturbation casesIntegrity I requires an intact executable, one valid configuration and restoration of both channels within five seconds. The supplied test histories establish I after each one-second interruption of power, one channel or communication, and after an interrupted parameter write. Recovery is automatic after the interruption ends. This is coverage of those four cases.
PH: 30 seconds temporal depthS7’s internal forecasting function produces z_hat(t+h) = r(t) + b(t) for 0 <= h <= 30 s, holding the current reference and offset over that prediction interval. The implementation supplies that model extent. Prediction accuracy is a separate question.
MP: 0.175 °C per minute over the three updatesThe declared measure is total variation of the stored offset divided by elapsed time. All three updates have the same sign, so both total variation and net change equal 0.525 °C; divide by three minutes. Parameter readback resolution is 0.01 °C.
PER: 0.95 for uniform selection from the stated finite populationThe population is 20 fully examined scripted bench episodes with valid inputs. Successful execution means completing the required reads, checks and commits of OffsetUpdateMethod-3. Nineteen histories meet it; one records a failed commit. Under uniform selection of one of these episodes, the probability is 19/20. A production-population estimate would need its own sampling and inference basis.
OC: one independently adjustable target pursued in this caseThe local complexity criterion counts independently adjustable target quantities. Here the target quantity is residual temperature error; the three-minute budget and offset-update bounds are fixed conditions of this comparison. The calculation establishes pursuit of this objective in the stated regime.

For the C.22.1 adaptation question, the first successful minute checkpoint is at 180 seconds, with a budget of three reference/update cycles and the stated initial model. This threshold result uses the residual-error bound; MP reports the parameter-change rate.

For a local didactic convention, assign Grade 3 within this controller family when BMC covers the named perturbation set, temporal PH is positive and error-driven MP is distinguishable from zero at the declared resolution. Leave other profiles unclassified. S7 receives that label; PER and OC remain explicit profile results outside what this partial mapping summarizes.

Changed receiving condition. Tighten the residual-error target to 0.05 °C while keeping the three-update budget. The profile values and local Grade remain supported, but the calibration result fails the new target: even the lower residual bound after three updates is 0.055 °C.

Under the same model, five updates would give an upper residual bound of 0.03875 °C. The practitioner can compare a larger adaptation budget with another update Method. The changed tolerance reopens the adaptation decision.

A.13:6 - Conformance Checklist

Apply these normative checks to the corresponding agency, profile or Grade claim in an FPF publication:

IDRequirement (Normative Predicate)Purpose / Rationale
CC-A13.1 (Holder Type)The holder System of an obtaining agential U.SystemRoleAssignment MUST be a U.System.Prevents the “episteme-as-actor” category error. Enforces Strict Distinction (A.7).
CC-A13.2 (Assignment Mandate)A precise claim of agency MUST name the exact local agential system-role kind and an obtaining occurrence of a directly declared U.SystemRoleAssignment species. Any claim scope, working situation, and time window needed by the use remain separate.Binds agency to a specific holder and assignment without turning a generic context field into their identity.
CC-A13.3 (Characteristic Evidence)An actual claim about a holder’s Agency Grade or autonomy profile MUST have a supported agency-characteristic profile with recoverable evidence and provenance under A.10. A Grade claim also states the mapping from those values to its didactic label. Use an Evidence Graph Ref when that representation is needed.Supports the characteristic values and the Grade interpretation.
CC-A13.4 (Grade is Didactic)The Agency Grade (0-4) SHALL NOT be used as a normative input for formal reasoning. It is a didactic summary of the agency-characteristic profile.An assurance case that consumes these characteristics uses their supported values, not the Grade.
CC-A13.5 (Collective as System)To claim agency for a collective (e.g., a team or swarm), it MUST first be admitted as a U.System under the complete A.1 criterion.Distinguishes an admitted collective System from a mere set or collection (MemberOf); parthood claims use A.14.
CC-A13.6 (MHT for Emergent Agency)If new supervision and a documented agency-characteristic threshold crossing raise a whole-reidentification question about an established prior whole, apply B.2’s comparison. When B.2 establishes the transition, a Meta-Holon Transition (MHT) MUST be declared.First constitution or recognition without an established prior whole uses A.1 and the applicable construction and kind-specific patterns. If the same whole explains the changed facts, stop without MHT. A prior description as non-agential or at a lower didactic Grade may describe the starting case; it is not a normative premise.

A.13:7 - Consequences

BenefitsTrade-offs / Mitigations
Agency core: Local kind, classification and obtaining assignment answer different questions; the same System may qualify and be assigned in one situation but not another.Modeling granularity: Distinguish those claims and any performed Work; state scope or window when it changes the claim. Use a short ordinary-language account first and expose identifiers only when needed.
Characteristic claims: The profile separates the capabilities being claimed and the evidence needed for their values.Measurement effort: Testing, analysis and data gathering take work. Build the profile iteratively; an initial estimate can be used with its uncertainty and evidence limits explicit. Missing support for that estimate does not imply low System reliability.
Didactic communication: The 0–4 scale gives a short vocabulary for discussing profiles, from simple automation to strategic intelligence.Grade misuse: A Grade claim needs the underlying profile under CC-A13.3 and cannot replace its characteristic values in formal reasoning under CC-A13.4.
Collective agency: The same core distinguishes agency claims for admitted team, swarm and organization Systems.-

A.13:8 - Rationale

The core answers which System qualifies for a local kind and holds its assignment. The profile answers separate questions about that holder’s capabilities. A Grade summarizes the profile for communication; it does not replace the detailed characteristic results needed by an assurance use.

The five characteristics are FPF engineering choices. A domain profile develops their operational definitions for its intended use; its measurement methods and any Grade mapping need their own stated basis. The following research contributions inform different agency questions:

  • Levin’s scale-free cognition paper (2019) proposes an account of individuality and goal-directedness while allowing more than one useful agent definition.
  • Levin’s TAME proposal (2022) describes a rich space of capacities rather than one privileged scalar of cognition. It motivates distinguishing capabilities instead of treating “agent” as a sufficient comparison.
  • Friston et al.’s active-inference account of agency (2013) is a historical anchor concerning prior beliefs about action in an embodied account. That question differs from defining A.13’s five measurement scales or Grade mapping.

A.13:9 - Relations

  • Builds on:
    • A.1 Holonic Foundation: Supplies the constructive and acting-eligibility conditions for recognizing the holder as a U.System.
    • A.2 System-Role Kinds and Assignments: Distinguishes an exact local system-role kind, classification by that kind, and an obtaining U.SystemRoleAssignment.
    • A.12 Acting-Side Externalization and Reflexive Split: Identify Who Acts on What: Separates acting and changed participants when that distinction matters; its precise account is conditional on the claims needed.
  • Coordinates with:
    • B.2 Meta-Holon Transition (MHT): Changed supervision and a documented agency-characteristic threshold crossing can raise a whole-reidentification question about an established prior whole. B.2 first tests whether that whole’s identity rule accommodates the change and whether the whole meets the receiving use. Only an established transition warrants the MHT declaration.
    • B.3 Trust & Assurance Calculus: A profile can supply evidence-backed characteristic results when a named reliability, safety or other assurance argument uses them. Retain each result’s bearer, scale and basis; the didactic Grade is not the assurance input.
    • D.2 Recognize Ethical Concerns Across Levels and Scopes (Multilevel Ethics): For a multilevel ethical concern, name the local gain, possible loss, affected levels or scopes and next subject question. State responsibility or accountability separately under the rule defining that relation and its participants; use an agency-characteristic input only if that rule calls for it.

A.13:End

A.14 - Mereology: Components, Portions, Aspects & Phases

Type: Kernel mereology and part-whole relation discipline pattern Status: Stable

At a glance. Use A.14 when wording such as part, member, portion, aspect, or phase could hide different claims. Recover whether the subject is a constructive part, belongs to a collection, is an amount of the same stuff, is one aspect, or is the same holon during a proper time interval before downstream architecture, Work, assurance, or U-kind admission relies on it.

Use this when. Use this pattern when a text says that something is part of something else, belongs to a collection, is some amount of the same stuff, is an aspect of one holon, or is the same holon during a time interval, and choosing the wrong relation would change identity, aggregation, responsibility, evidence, or structural grounding.

What goes wrong if missed. Teams count members as components, portions as components, aspects as separate wholes, or phases as separate objects; constructive traces and Working-Model relation claims then ground the wrong EntityOfConcern.

What this buys. One relation catalogue that keeps constructive components and constituents, measured portions, bearer-dependent aspects, proper temporal phases, and collection belonging under each collection’s own rule distinct without inventing a catch-all aspect or member vocabulary.

Not this pattern when. Use the direct pattern when the current question is only a selected Characteristic (C.16/A.19), viewpoint or view (E.17.0/E.17.1), representation or projection (C.29 or its direct projection pattern), temporal claim without a PhaseOf relation (C.27.TA), constructive trace (C.13), Working-Model assurance grounding (B.3.5), meta-holon transition (B.2), or general U-kind admission (E.24.UK).

A.14:1 - Problem frame

Before choosing a relation, identify the candidate part and whole, or the entity and collection. Use their normal identity rules. A local system-role kind, Method, Work occurrence, view, or trace does not become a structural part merely because the text calls it one; use its own pattern unless a separate part claim is established.

Four recurring questions then matter:

  1. Quantities vs. parts. Engineers routinely need “some of the fuel”, “the first 10 pages”, or “a 30% subset of data”. These claims concern measured stuff or extent: use PortionOf when its measure and boundary conditions hold, and account for conservation. State any separately obtaining structural relation independently.

  2. Selected concern vs. structural aspect. Engineers also say “the thermal aspect”, “the safety view”, or “the inspection slice”. A Characteristic, viewpoint, representation, selected partition, or time window does not become a world-side part by that wording. AspectOf is used only for a bearer-dependent structural part distinguished under a named facet rule.

  3. Change vs. replacement. “The prototype before calibration” may be a proper temporal restriction of the same continuing pump. By contrast, “v2 of the spec” first opens C.2.1 identity and, for two different epistemes, its independent edition-continuity test; “shift 1 vs. shift 2” first opens A.15.1 Work-part or occurrence law. None of those labels selects PhaseOf by itself.

  4. Belonging vs. construction. “Vehicle 12 belongs to Fleet North” uses the fleet’s own rule. That sentence alone makes neither the vehicle a constructive part nor the fleet an acting System, and it does not prohibit either separate claim.

A.14:2 - Problem — what breaks without these distinctions?

If we only have “generic partOf” plus Component/Constituent, five classes of errors appear:

  1. Conservation errors. Counting “20 L of fuel from Tank A” as a component supplies no measure, additivity or conservation account for additions and removals. Establish the common measure and boundary under :5.1, then reconcile the remaining fuel with the actual additions and removals under the applicable conservation law.

  2. Aspect creation by wording. A selected Characteristic, view, projection, partition rule, dashboard slice, or concern label is turned into a world-side part without identifying the aspect, bearer, facet rule, or identity condition.

  3. Temporal smearing. Flattening “before/after” for one enduring holon into a timeless whole collapses history; treating two changed epistemes or two Work occurrences as temporal pieces of that holon collapses identity and occurrence history. Resolve those identities and Work relations before temporal aggregation (B.1.4) or Method composition (B.1.5).

  4. Identity confusion. Modelling a “new version” as a component or phase lets a label decide identity. For an episteme, first compare the C.2.1 identity triple and then test edition continuity separately; for another enduring holon, apply its direct identity rule to determine whether the same individual persists or a reidentification question opens.

  5. System-role leakage. A local system-role kind, assignment, or relation-position label is put into a part tree (“the PumpRole is part of the plant”), making structural reasoning brittle.

A.14:3 - Forces

ForceTension
Expressiveness vs. parsimonyPortion, aspect, and phase claims need usable direct relations, while the catalogue must not turn every concern word into a part kind.
World-side structure vs. analysisA bearer-dependent aspect must be stateable, while Characteristics, views, projections, partitions, and time windows keep their own meanings.
Universality vs. domain nuanceOne relation discipline must serve physical systems and epistemes, while measurement, facet rules, and time behave differently by subject.
Identity vs. changePreserve the holon’s identity through allowed change, while making reidentification explicit when its rule fails.
Readable claim vs. assuranceThe ordinary relation sentence must stand on its own, while a named assurance use may require a sum, slice, or set account.

A.14:4 - Solution — extend the mereology catalogue

A.14 defines three additional direct sub-relations of partOf:

  1. PortionOf — a measured part of a whole under one extensive measure and boundary rule.
  2. AspectOf — a bearer-dependent structural part distinguished under a named facet rule.
  3. PhaseOf — the same holon restricted to a proper time interval.

Two neighboring distinctions govern how these relations are used:

  • Keep local kinds, Methods, and Work out of structural part trees. Do not treat a local system-role kind or a Method as a structural part. A separately identified System or Episteme may have its own direct part relation; use method-composition patterns for submethods and A.15.1 for Work parts and occurrences.
  • Use the collection’s own belongs-to rule. State who or what may belong, what makes belonging begin and end, and how recurrence and past belonging are handled. FPF does not use one public MemberOf relation for unlike collections. Belonging alone establishes neither holonhood nor parthood, and it does not rule out a separately grounded constructive part relation after all six A.1 matters pass.

The classical pair ComponentOf (structural, discrete) and ConstituentOf (conceptual, logical/epistemic) remain as in the kernel; § 6 distinguishes them from PortionOf, AspectOf, PhaseOf, and collection belonging.

A.14:5 - Formal cores (normative semantics)

A.14:5.1 - PortionOf — metrical part of a measurable whole

Intent. Capture “some of the same stuff/extent”, governed by a measure that adds up.

Applicability. Any U.Holon that carries an extensive measure μ on the chosen scope (examples: mass, volume, length‑of‑text, byte size, wall‑time budget).

Several expressions of one episteme can have different text lengths, pagination or encoded sizes. Attach the measure to the selected expression or carrier state, using C.2.1 and E.24.PUB to keep its identity separate from the episteme. An A.14 PortionOf claim additionally requires independently admitted part and whole holons. Ordinary counting within an expression can use that expression domain’s rules directly.

Primitive. PortionOf(x, y) means: x is a measured part of y of the same kind of stuff/content, allowing x = y; the strict case is ProperPortionOf under POR-2.

Axioms (A14‑POR‑*)

  • POR‑1 (Partial order). PortionOf is reflexive, antisymmetric, transitive on its domain.
  • POR‑2 (Metrical dominance). If x ProperPortionOf y then 0 < μ(x) < μ(y) for the agreed μ.
  • POR‑3 (Additivity on disjoint portions). If PortionOf(x,y), PortionOf(z,y), and x ⟂ z (the two portions do not overlap), and their join is admitted under the same measure and boundary rule, then μ(x ⊔ z) = μ(x)+μ(z) and PortionOf(x ⊔ z,y). ProperPortionOf additionally requires the joined measure to remain strictly below μ(y); a join equal to the whole is PortionOf but not ProperPortionOf.
  • POR‑4 (Kind integrity). x and y must share the same measure kind and unit (or a declared conversion).
  • POR‑5 (Boundary compatibility). For physical wholes, the whole’s boundary encloses the union of its portions; cross‑boundary “leaks” are interactions, not portions.

Check POR-2 separately for the chosen measure: additivity alone supplies only non-strict monotonicity. One sufficient case is an admitted disjoint decomposition y = x ⊔ r with finite μ(y) and positive μ(x) and μ(r); additivity then gives strict dominance.

If a proposed proper part has zero measure or the same measure as the whole, use a measure that distinguishes the portion and remainder, or retain the separately justified part relation under its own pattern.

Didactic tests.

  • ✔ “5 kg from a 20 kg billet” — PortionOf.
  • ✔ Two disjoint 5 kg cuts from the same 20 kg billet have a 10 kg join under the same mass unit and boundary rule; that join is still a ProperPortionOf the billet.
  • ✔ “The report text rendered on pages 1–10” — measure the span within the selected expression under fixed pagination or a separately established token count. Use PortionOf when the span and whole text are independently admitted holons and satisfy the same-content, measure and boundary rules.
  • ✘ “The pump module of the plant” as an integrated structural part — use ComponentOf for that claim, not PortionOf.
  • ✘ “The Methods section of the paper” as a conceptual part of its argument — use ConstituentOf for that claim, not PortionOf.

Either object may also support a separate PortionOf claim when it satisfies the same-stuff/extent, measure and boundary conditions above.

A.14:5.2 - PhaseOf — temporal part of the same holon

Intent. Capture “the same holon during a sub‑interval”, preserving identity through change.

Applicability. Any U.Holon that persists across time with a recognised holon identity.

Primitive. PhaseOf(x, y) means: x is y itself restricted to a proper time interval. Identify that temporal part of the holon; a time-limited use of y or a claim about y retains its own applicability rule.

Axioms (A14‑PHA‑*)

  • PHA‑1 (Strict temporal parthood). PhaseOf is irreflexive, asymmetric, and transitive on proper temporal restrictions of one continuing holon. In particular, PhaseOf(y,y) is false: a whole-lifetime or self-reference is not a proper temporal part.
  • PHA‑2 (Proper interval and same holon). PhaseOf(x,y) requires the interval of x to be a proper sub-interval of y’s interval and the holon-identity rule to hold throughout both. It does not require x to be a maximal cell of a partition.
  • PHA‑3 (Nesting and overlap are allowed). Temporal restrictions of the same holon may nest or overlap. A week may be part of a year-long phase, and a diagnostic window may overlap a calibration window. Those facts are not contradictions and do not by themselves select an aspect or partition.
  • PHA‑4 (Selected partition is an additional claim). When a use needs exhaustive non-overlapping cells, declare one holon, one interval to be covered, one analysis aspect or partition rule, and the selected family of PhaseOf values. Only cells of that same explicitly selected partition must be pairwise non-overlapping and jointly cover the declared interval. Another aspect or rule may select a different, overlapping family.
  • PHA‑5 (Identity through change). Properties may vary between phases while the holon’s complete identity rule holds continuously. For an episteme, this includes its unchanged C.2.1 identity triple; a stable name or theorem statement alone does not establish that identity.
  • PHA‑6 (Identity failure). If the holon-identity criterion fails, do not assert PhaseOf across that boundary. Apply the subject’s identity and continuation rules; use B.2 only for a whole-reidentification claim and declare MHT only after its conditions hold.

Didactic tests.

  • ✔ “PumpUnit#3 before calibration” — PhaseOf(Pump#3_pre, Pump#3).
  • ✔ If PhaseOf(Pump#3@week-32, Pump#3@2026) and PhaseOf(Pump#3@2026, Pump#3), transitivity also gives PhaseOf(Pump#3@week-32, Pump#3). A high-vibration diagnostic window may overlap a calibration window for the same pump; neither is thereby a cell of one selected partition.
  • ✔ “Specification episteme E during τ₂” — PhaseOf(E@τ₂, E) when E@τ₂ is identified as a proper temporal restriction of E itself and the C.2.1 identity triple remains unchanged. ✘ “Spec v2” — if a C.2.1 discriminator changed, identify another episteme and test EpistemeEditionRelation(E_v1,E_v2) separately; the label proves neither identity nor continuity.
  • ✘ “Shift 1 of the same batch run” — use A.15.1 TemporalPartOf_work, EpisodeOf_work, OperationalPartOf_work, or another Work-part or occurrence relation whose predicate obtains.
  • ✘ “Prototype vs. production unit” — identify each holon and any separately established relation. The labels alone select neither PhaseOf, ComponentOf, ConstituentOf, nor MHT.

A.14:5.3 - AspectOf — bearer-dependent structural part under one named facet rule

Intent. State that one identified bearer-dependent structural part is an aspect of its bearer under a named facet rule.

Participants and qualifier. x and y occupy the U.Holon parthood domain: x is the aspect and y its bearer. Each must already satisfy its applicable holon-kind and identity rule; AspectOf does not grant systemness, agency, or independent-whole status. The qualifier f names the facet rule used in this occurrence; it does not introduce a universal U.Facet kind.

Primitive. AspectOf(x, y; f) means: x is the bearer-dependent structural part of y distinguished under facet rule f. The notation shows the required qualifier; the public sentence may remain “x is an aspect of y under the f rule.”

Obtaining conditions and properties (A14-ASP-*).

  • ASP-1 (Identified occurrence). Name x, y, f, the relation occurrence, and the aspect-identity rule. The facet rule states what distinguishes x from the rest of y and what change preserves or ends this aspect.
  • ASP-2 (Structural dependence). AspectOf(x,y;f) implies ut:StructPartOf(x,y), x != y, and asymmetry for that occurrence. It implies none of ComponentOf, ConstituentOf, PortionOf, PhaseOf, collection belonging, or independent systemhood.
  • ASP-3 (Facet-local and non-transitive). An occurrence under f gives no occurrence under another facet. AspectOf is not assumed transitive through another bearer or facet; state every relied-on relation directly.
  • ASP-4 (Bearer and aspect identity). If the bearer is reidentified, or f and the aspect-identity rule no longer identify x, the old occurrence ends. A changed view, diagram, name, or measurement does not by itself change the world-side occurrence.
  • ASP-5 (Neighbor boundary). A measured quality routes to C.16/A.19; a viewpoint or view to E.17.0/E.17.1; a representation or projection to C.29 or its direct projection pattern; a selected temporal window to PhaseOf or C.27.TA; a selected partition to the pattern governing that structure. None creates AspectOf by selection alone.

Didactic tests.

  • ✓ In this constructed case, Reactor-7 and ThermalEnvelope-7 are independently admitted holons. The thermal-boundary rule distinguishes ThermalEnvelope-7 as the connected enclosure of insulation panels, seals, and boundary interfaces that constrains heat transfer across the reactor boundary. ThermalEnvelope-7 is identified by the continuing enclosure under that rule, not by a fixed panel list. AspectOf(ThermalEnvelope-7, Reactor-7; thermal-boundary) obtains while that enclosure and Reactor-7 continue. Replacing one panel under the same rule preserves the aspect; dismantling the enclosure, replacing the facet rule with a different boundary, or reidentifying Reactor-7 ends the occurrence. A changed temperature reading or dashboard view does not.
  • ✗ “Safety is an aspect of the design” when safety is only a Characteristic, concern, viewpoint, or heading. Recover that claim first.
  • ✗ “Pump-7 during warm-up is its thermal aspect.” Use PhaseOf for the proper temporal restriction and A.19 for a measured thermal Characteristic when those claims obtain.

A.14:5.4 - CT2R-LOG and Compose-CAL handshake

  • A direct structural parthood claim is usable without this assurance handshake. If the publication elects B.3.5 or a named current requirement demands it, link the claim through tv:groundedBy to its applicable current C.2.1 Γ_m.sum or Γ_m.slice construction-trace episteme and declare validationMode=axiomatic.

    The direct relation pattern decides whether the occurrence obtains and how it is identified; the relevant entity pattern decides identity through change. The trace only reports that basis.

  • PortionOf uses the measured-portion slice account in C.13:4.1.1 when B.3.5 is elected: identify the portion and whole, delimiting boundary, same-stuff/content basis, extensive measure and compatible unit. The aspect profile of slice has different conditions.

  • AspectOf uses one current C.13 slice trace when that assurance branch is elected. The trace names the aspect, bearer, facet rule, relation occurrence, and identity conditions.

  • PhaseOf is temporal parthood and shall not be grounded through Γ_m. Its assurance follows the same-holon and proper-interval criteria, the separately declared selected-partition rule when one is claimed, and Γ_time ordering (B.1.4).

  • A collection’s own belongs-to relation remains distinct from constructive parthood (CC-MEM-2). State its participants, what makes it obtain, and whether later belonging is the same occurrence or a new one under the collection’s pattern. A direct claim needs no B.3.5 fields.

    If B.3.5 assurance is elected, link validationMode=axiomatic to one current C.13 set trace that reports the relation that already obtains. The trace supports neither a ComponentOf inference nor a universal prohibition on separately grounded parthood.

Two identity tests apply before relying on a trace. The same listed constituents can form a different whole when their direct assembly relations or rule differ. Conversely, a permitted constituent replacement can preserve the same whole. An equal input list, a repeated trace, or validationMode=axiomatic decides neither case.

A.14:6 - Choosing a relation (decision table)

You want to say…UseWhy
“This is a piece of the same stuff or extent.”PortionOfOne extensive measure and conservation rule govern the claim.
“This is a discrete structural part inside the whole.”ComponentOfThe part is structurally integrated; amount and facet selection do not decide it.
“This is a logical or content part of a conceptual whole.”ConstituentOfThe claim concerns conceptual or epistemic assembly.
“This dependent structural part is one aspect of this bearer under this facet rule.”AspectOfName the aspect, bearer, facet rule, occurrence, and identity rule; a Characteristic, view, projection, partition, or time window is not enough.
“This is the same entity during a proper sub-interval.”PhaseOfThe same holon and its identity rule hold over a proper temporal restriction.
“This item belongs to that collection.”The belongs-to rule defined for that collectionName the entity and collection, state what makes belonging begin and end, and distinguish recurrence. Belonging establishes neither parthood nor its impossibility.
“This System is classified by a local work-facing kind, has an assignment to that kind, or participates in a direct relation.”The corresponding local system-role-kind classification, U.SystemRoleAssignment, or direct relation participation; use A.6.5 when the relation needs reusable participant typing.Kind classification, assignment occurrence, and relation participation are not parts.

If the sentence is about system-role-kind classification or assignment, how action is done, or what happened when, use A.2/A.2.1, A.3.1, or A.15.1 as appropriate. For an episteme, use A.14 for content parthood or a proper interval of one unchanged C.2.1 identity; changed claims, EntityOfConcern, or effective reference scheme identify another episteme, and any historical continuation uses C.2.1 EpistemeEditionRelation only when its predicate obtains.

A.14:7 - Archetypal Grounding

RelationPhysical or engineering-design exampleText, publication, or episteme example or boundary
PortionOf50 L from the 200 L fuel stock in Tank-A, under one volume measure and its stated conditions.Text on pages 1–10 of one 120-page expression under fixed pagination, with the text span and whole independently established as holons. Token count is a separate measure.
ComponentOfImpeller ComponentOf PumpUnit.The printed region occupied by Figure 2, independently identified as a physical part of the poster.
ConstituentOfControl law ConstituentOf Controller Design.Lemma A ConstituentOf Theorem Proof.
AspectOfThermalEnvelope-7 AspectOf Reactor-7 under the thermal-boundary rule; A.14:5.3 shows the bearer, enclosure, occurrence, identity, preservation, and ending conditions.A selected view, concern, heading, or projection of an episteme is not AspectOf. Use this relation only if a bearer-dependent structural aspect, facet rule, occurrence, and aspect identity are independently established.
PhaseOfPumpUnit-3 before calibration, with the same holon identity.One unchanged theorem episteme restricted to a proper interval while its C.2.1 identity remains fixed.
Collection belonging“Vehicle 12 belongs to Fleet North under its registration rule.” The rule supplies beginning, ending, recurrence and history; the claim establishes neither holonhood nor parthood.The same discipline applies to collections of epistemes. A listing establishes belonging only when the collection’s rule makes that act constitutive and its conditions hold.

A.14:8 - Bias-Annotation

A.14 corrects parthood bias: ordinary words such as part, member, phase, aspect, section, version, module, function, role, and ingredient can hide different objects or relations. Recover whether the source means component, constituent, measured portion, bearer-dependent aspect, proper temporal phase, collection belonging, local system-role-kind classification, assignment, Method, Work, evidence, or transformation.

It also corrects analysis and representation bias. A Characteristic, viewpoint, view, projection, selected partition, dashboard slice, diagram, table row, or time window may describe or foreground something about a bearer without becoming a world-side structural aspect. AspectOf begins only after the aspect, bearer, facet rule, relation occurrence, and aspect identity are established. Publication or construction traces report such a claim; they do not create it.

A.14:9 - Conformance Checklist - type guards

A.14:9.1 - Global firewall and scope

IDRequirementPurpose
CC-A14-0A local system-role kind MUST NOT occur as a node in any partOf chain by kind identity; a U.System classified by that kind remains eligible for holon mereology on its independent system identity. U.Method MUST NOT occur in A.14 structural ComponentOf or structural partOf chains by method identity alone; A.3.1 and B.1.5 define submethod assembly. If an admission predicate establishes a different entity, such as a SystemRoleKindDescription, Work occurrence, U.SystemRoleAssignment occurrence, SystemRoleKindRelationStructure, method relation structure, or episteme, name that entity, assertion, and subject-pattern locator.Keeps local system-role kinds out of holon mereology by kind identity and keeps method holarchy out of structural component mereology while preserving admitted entities.
CC‑A14‑0aU.MethodDescription / U.WorkPlan and other describing epistemes MAY participate in partOf only as U.Episteme nodes: content ConstituentOf, PortionOf when the epistemes themselves meet :5.1, or PhaseOf for a proper interval of one unchanged C.2.1 identity. A changed C.2.1 discriminator identifies another episteme; connect two such identities only through an independently obtaining EpistemeEditionRelation. They MUST NOT be asserted as ut:StructPartOf of any U.System.Allows episteme structure and temporal restriction without smuggling Methods or automatic edition continuity into structure.
CC‑A14‑0bA collection-belonging relation MUST NOT be inferred or auto-rewritten as any partOf sub-relation. This non-inference does not prohibit a separately grounded constructive part relation for the same entities.Separates collection belonging from parthood without assuming they can never coexist.
CC‑A14‑0cSerialStepOf / ParallelFactorOf MUST NOT appear in any partOf chain or table in A.14; model order and concurrency potential via A.15 and direct method-composition patterns such as B.1.5. If a node linked by those relations is also a submethod, state that U.Method claim separately before using method holarchy.Prevents the “order‑as‑structure” and “edge-as-part” category errors.

A.14:9.2 - PortionOf guards

IDRequirementPurpose
CC‑POR‑1 (Domain)PortionOf(x,y) is valid only if the modelling scope declares an extensive measure μ for y. ProperPortionOf additionally requires the strict inequality in :5.1/POR-2; check it independently of additivity.Prevents “portion” without a measure.
CC‑POR‑2 (Kind)x and y SHALL share the same μ‑kind and compatible units (or an explicit conversion).Prevents apples‑to‑oranges addition.
CC-POR-3 (Monotone additivity)For disjoint portions x ⟂ z with PortionOf(-,y), whose join is admitted under the same measure and boundary rule: μ(x ⊔ z) = μ(x)+μ(z).Justifies the additive measure of that admitted join; additions, removals and boundary flows still need their applicable conservation account.
CC‑POR‑4 (Boundary)For physical systems, the whole’s boundary encloses the union of portions; cross‑boundary flows are not portions.Distinguishes stock vs flow.
CC‑POR‑5 (Non‑replacement)When replacing a measured portion of y, state the removed and inserted amounts under their applicable measure and boundary rules, and test y’s identity under its governing rule. Add ComponentOf or ConstituentOf only when that separate structural or content relation obtains.Avoids inferring another relation from a measured replacement.

A.14:9.3 - PhaseOf guards

IDRequirementPurpose
CC‑PHA‑1 (Proper interval & holon identity)PhaseOf(x,y) requires x ≠ y, a proper sub-interval of y’s interval, and the complete identity rule for y valid throughout both restrictions. Identify x as the temporal restriction of y itself under §5.2; an interval of use alone is insufficient.Excludes self/whole-lifetime phasing and prevents re-identification by stealth.
CC‑PHA‑2 (Nesting & overlap)Nested or overlapping PhaseOf values for one holon MAY obtain. Do not infer a partition, aspect difference, or holon difference merely from overlap.Keeps universal temporal parthood consistent and permits ordinary windows.
CC‑PHA‑3 (Selected partition)If a claim selects an exhaustive partition, it MUST name one holon, covered interval, aspect or partition rule, and family of phase cells. Only cells of that same selected partition are required to be pairwise non-overlapping and jointly cover the declared interval.Makes coverage and non-overlap local to the claim that needs them.
CC‑PHA‑4 (Identity failure)If the holon-identity criterion fails, PhaseOf does not span that boundary. Apply the subject’s identity and continuation rules; a claimed Meta‑Holon Transition must independently satisfy B.2.Keeps temporal parthood separate from whole reidentification.
CC-PHA-5 (Episteme & Work boundary)PhaseOf MAY restrict one unchanged U.MethodDescription episteme to a proper interval only after its C.2.1 identity triple remains fixed. Changed description epistemes use EpistemeEditionRelation only when C.2.1’s historical-continuation predicate obtains. Work intervals, episodes, performed parts, retries, resumptions, and later occurrences SHALL use A.15.1’s relations; generic PhaseOf is not their substitute. PhaseOf never applies to a local system-role kind by kind identity or to U.Method.Keeps episteme identity, edition continuity, and Work-temporal law with their subject patterns.

A.14:9.4 - AspectOf guards

IDRequirementPurpose
CC-ASP-1 (Participants and rule)Name the aspect and bearer in the U.Holon parthood domain, the facet rule, the relation occurrence, and the aspect-identity rule. The relation grants neither systemness nor independent-whole status.Prevents an aspect label from admitting its own object.
CC-ASP-2 (Obtaining)The facet rule must state what distinguishes the aspect and what change preserves or ends it. A chosen concern, Characteristic, viewpoint, view, projection, partition, label, or temporal window establishes no AspectOf occurrence.Keeps selection and description from becoming world-side parthood.
CC-ASP-3 (Relation properties)AspectOf(x,y;f) implies one asymmetric ut:StructPartOf(x,y) occurrence with x != y. Infer neither another facet occurrence, transitivity, ComponentOf, ConstituentOf, PortionOf, PhaseOf, collection belonging, nor independent systemhood.Keeps the relation facet-local and non-omnibus.
CC-ASP-4 (Identity and assurance)Bearer reidentification or failure of the facet and aspect-identity rule ends the old occurrence. A direct claim needs no B.3.5 fields; after profile election it uses one current C.13 slice trace and validationMode=axiomatic.Keeps occurrence identity and optional assurance separate.

A.14:9.5 - Grounding and validation (normative)

IDRequirementPurpose
CC-GND-1A direct ut:StructPartOf assertion is usable without this assurance profile. When its publication elects B.3.5 or a named current requirement demands that profile, the assertion must use validationMode=axiomatic and link through tv:groundedBy to its applicable current C.2.1 sum or slice construction trace. The trace reports independently grounded participants, direct relation occurrences, the construction rule, and identity or reidentification conditions.Makes an elected assurance basis inspectable without making it the relation’s truth-maker.
CC-GND-2For epistemic edges (ut:EpiPartOf and its sub-types), retain the independently established content-part basis. When a publication choice or named current requirement elects B.3.5, supply the support references and validationMode required by the applicable epistemic branch. Preserve any evidence reference independently required by the receiving use.Harmonises evidence treatment for epistemic edges.
CC-GND-3The public query Standard remains ?x ut:PartOf+ ?y; every result still depends on its direct relation semantics and identity. Alias, trace, or validation mode creates or reidentifies no occurrence.Preserves one query surface without moving authority into assurance apparatus.

Note. Property names and trace semantics are defined in CT2R-LOG and Compose-CAL.

A.14:9.6 - Collection belonging and separately grounded parthood

IDRequirementPurpose
CC-MEM-1State collection belonging with the predicate defined for that subject. Name the entity, collection, collection identity rule, what makes belonging begin and end, whether it can recur, and how past belonging is said.Keeps unlike fleets, corpora, communities, populations, products, and Suites under their own rules.
CC-MEM-2From collection belonging alone infer neither a constructive part relation nor holonhood. Also do not infer that either is impossible.Separates non-implication from universal prohibition.
CC-MEM-3If the same collection independently passes all six A.1 matters and a constructive part relation obtains, publish that second claim under its direct pattern. A direct belonging sentence needs no B.3.5 fields. When B.3.5 assurance is elected for it, use validationMode=axiomatic and one current C.13 set trace; the trace reports the collection, entities, relation occurrences, rule, and identity conditions.Keeps collection belonging, constructive parthood, assurance, and collective action separate.

A.14:9.7 - CT2R‑LOG handshake (Working‑Model → Assurance)

IDRequirementPurpose
CC-A14-10A published direct relation may remain usable without B.3.5 fields. When its publication elects B.3.5, follow the relation’s branch: structural parthood links its current sum or slice construction trace, while collection belonging links one current C.13 set trace under the collection’s own rule; both declare validationMode=axiomatic. The direct relation and identity tests remain decisive.Keeps direct use lightweight while making an elected assurance posture inspectable.
CC‑A14‑11PhaseOf edges SHALL NOT use Γ_m for grounding. The relation record SHALL provide identity and proper-interval criteria per CC‑PHA‑1/2; a selected exhaustive partition additionally follows CC‑PHA‑3 and references Γ_time when ordering matters.Keeps temporal parthood distinct from construction and partition-specific constraints.

A.14:9.8 - Relation-use decision procedure

Step 0 — Recover the claim. If the sentence concerns system-role-kind classification or assignment, Method, Work, evidence, a Characteristic, viewpoint, view, projection, partition, or temporal claim without parthood, use that direct pattern. A.14 is not selected merely because ordinary speech says part or aspect. State different obtaining relations as separate claims.

Step 1 — Does the claim concern measured stuff or extent? If yes, use PortionOf after declaring μ, unit, boundary and additivity conditions. For ProperPortionOf, also check the strict inequality in :5.1/POR-2 independently of additivity.

Step 2 — Does the claim concern a discrete integrated or conceptual part? If yes, use ComponentOf or ConstituentOf. Do not use PortionOf merely because the part can also be measured.

Step 3 — Is it the same holon during a proper sub-interval? If yes, use PhaseOf after the holon-identity and interval tests. Another episteme or Work occurrence uses its own identity and relation patterns.

Step 4 — Is it a bearer-dependent structural aspect? Use AspectOf only after naming the aspect, bearer, facet rule, relation occurrence, and aspect-identity rule. If the source names only a Characteristic, viewpoint, view, projection, selected partition, concern, or time window, return that claim instead.

Step 5 — Does the entity belong to a collection? Use the belongs-to rule defined for that collection after naming the entity, collection, beginning, ending, recurrence, and history conditions. Infer neither part nor holonhood and do not infer that separately grounded parthood is impossible. If collective action is current, apply all six A.1 matters separately.

Spot-tests.

SmellLikely errorFix
“20% of the chassis”A percentage substitutes for the structural or measured-extent predicate.Establish ComponentOf for an integrated part; state a separate PortionOf claim for same-stuff extent under its measure and boundary conditions. The percentage alone establishes neither.
“Chapter 2 is 15% of the book”Content assembly and text measure are collapsed.State the chapter’s conceptual contribution as ConstituentOf. Measure the chapter and book text in a selected expression; use PortionOf only when the measured entities independently meet :5.1.
“Safety is an aspect of the design.”Characteristic, concern, viewpoint, or structural aspect remains unresolved.Recover the claim. Use AspectOf only with an identified aspect, bearer, facet rule, occurrence, and identity condition.
“The dashboard slice is an aspect of the reactor.”A view or projection is made into a world-side part.Use the view, publication, or representation pattern; add AspectOf only for an independently established reactor aspect.
“Spec v2 overlaps v1.”A version label is asked to decide identity and phase.Compare C.2.1 identities and test edition continuity; use PhaseOf only for one unchanged episteme over a proper interval.
“Team is part of the project.”Collection belonging is confused with constructive parthood.State the affiliation rule. If an integrated whole is also claimed, apply all six A.1 matters and state the part relation separately.

A.14:9.9 - Mereology in composition and aggregation

Receiving useMereological hooks (what A.14 supplies)Key effect
System aggregation decision (B.1.2:4)Add measures of disjoint portions only under :5.1 and the selected whole-characteristic rule in B.1.2:4.4. Establish ComponentOf and boundary integration separately. AspectOf remains facet-local structural parthood; PhaseOf requires its own holon identity and temporal restriction.Supports justified quantitative roll-up while preserving the distinct component, aspect and phase claims.
Γ_epist (B.1.3)ConstituentOf composes claim-bearing parts such as arguments or sections. Measure text or data extent on its selected expression or carrier; a separate PortionOf claim requires :5.1. AspectOf is available only for an independently admitted episteme-dependent structural aspect under a declared facet rule. A viewpoint, view, heading, or projection remains with E.17 or C.29. PhaseOf may restrict one unchanged episteme to a proper interval.Preserves provenance and prevents description choices from creating episteme parts.
Γ_ctx / Γ_time (B.1.4)PhaseOf supplies proper temporal restrictions, including nested or overlapping windows. A separately selected partition supplies non-overlap and coverage only for its own cells. Order/dependencies live in Γ_ctx and method graphs (A.15/B.1.5). PortionOf is orthogonal (quantities inside steps/runs).Ensures chronological consistency without turning every temporal restriction into one partition.
Γ_method (B.1.5)Γ_method composes Methods rather than A.14 structural parts. A recipe-labelled claim-bearing episteme is a MethodDescription only when its EntityOfConcern is one admitted U.Method and it makes at least one substantive claim about that Method as a way of doing under A.3.2. A graph may represent those claims; use C.29 when a separate mathematical-representation choice, transfer, or reliance question remains. When a recipe refers to stuff-like inputs, those are PortionOf statements on resources.Separates recipe composition from structure.
Γ_work (B.1.6)For a Work consumption claim such as “consumed 5 kg from Tank A”, identify the consumed fuel as a PortionOf the stock before consumption under its mass measure and boundary rule.Connects the portion identity to the consumption delta; B.1.6 supplies the resource-balance account.

A.14:10 - Common Anti-Patterns and How to Avoid Them

  • Member as component. A person, team, document, or object belongs to a collection and is then counted as structurally integrated.
  • Aspect by label. A Characteristic, concern, viewpoint, view, projection, partition, heading, dashboard slice, or time window is called an aspect and entered into a part tree. Recover the claim; require the full AspectOf occurrence when structural parthood is intended.
  • System-role expression as part. A local kind, assignment, or relation position is put into a part tree instead of using its direct pattern.
  • Method as part. A Method, recipe, or algorithm is treated as a structural component instead of using Method, MethodDescription, Work, or transformation patterns.
  • Portion without measure. Some fuel, data, time, or text is named as a portion without measure kind, unit, boundary, and additivity conditions.
  • Phase as replacement or lineage. Another episteme, version label, or Work segment is treated as PhaseOf without applying C.2.1 or A.15.1.
  • Diagram or trace as relation. The presence or form of a breakdown, graph, table or trace is taken as proof of parthood or identity. Inspect its content and the applicable relation and identity rules; the content may supply grounds, while the representation alone establishes no occurrence.

A.14:11 - Pedagogy aids (non-normative)

Practitioner checklist

  1. What subject and relation does the sentence claim?
  2. Does every PortionOf have a declared extensive measure, unit, boundary, and additivity condition?
  3. Does every AspectOf name the aspect, bearer, facet rule, occurrence, and identity rule—and avoid replacing a Characteristic, view, projection, partition, or time window?
  4. Is every PhaseOf a proper interval of one continuing holon rather than another episteme or Work occurrence?
  5. Does every collection claim use its own belongs-to rule without inferring or prohibiting a separate part relation?
  6. Are local system-role kinds, assignments, Methods, Work, views, and traces kept outside the part tree unless an independently admitted entity and direct part relation are current?

A.14:12 - Consequences

Benefits

  • Predictable composition. Additive portions, facet-local aspects, same-holon phases, and explicit collection rules keep unlike claims separate.
  • Analysis does not create ontology. Characteristics, viewpoints, views, projections, partitions, and time windows remain usable without being turned into structural parts.
  • History without confusion. Aspect and phase identity changes are explicit; collection history stays with the collection’s rule.
  • Readable first use. A practitioner can state the direct component, constituent, portion, aspect, phase, or belongs-to sentence before any elected assurance account.

Trade-offs and mitigations

  • More distinctions. Authors must name a measure for PortionOf, a facet and identity rule for AspectOf, or a proper interval and holon identity for PhaseOf. The decision table and practitioner checklist organize that first relation choice.
  • Aspect judgement. Distinguishing a structural aspect from a Characteristic, view, projection, or temporal claim requires judgement; neighboring patterns provide the stop and route.
  • Optional assurance effort. sum, slice, and set traces are added only when B.3.5 or another named current requirement elects them.
  • Escalation discipline. When the holon’s identity rule fails, use the direct reidentification pattern rather than preserving an AspectOf or PhaseOf occurrence by label.

A.14:13 - Rationale

A.14 exists because part-whole words carry identity, aggregation, measure, facet, time, and assurance commitments. The pattern keeps those commitments in the direct relation instead of letting everyday nouns, concerns, views, diagrams, or breakdown tables decide ontology. Component, constituent, portion, bearer-dependent aspect, proper phase, and collection-belonging claims can then support downstream work without smuggling Characteristics, viewpoints, local kinds, assignments, Methods, Work, or publication claims into mereology.

A.14:14 - SoTA-Echoing

The collection-belonging rule uses a constructional question: what is the collection, what gives it identity, and which relation obtains? A subject-specific rule supplies the belonging predicate.

Source lineUseful contributionLimitA.14 decision and destination
Partridge et al., the constructional turn, and BORO C-FORS 2025Set, sum, tuple, and assembly constructors have different outputs, dependence, and identity conditions.BORO’s extensional, 4D, and unrestricted-composition commitments are not FPF defaults.Adapt. The collection rule in §4 and CC-MEM-1 distinguish a collection’s own belongs-to rule from a C.13 sum; CC-MEM-2/3 require a separate constructive-part claim rather than deriving or prohibiting it from belonging.
Florio and Linnebo, constructional ontology, and Borgo and Righetti, applied constructional ontologyGivens, constructors, inputs, and construction processes must be distinguished; set, sum, and ordered-pair constructions are not interchangeable.The applied work is exploratory and does not supply FPF’s domain-facing identity, admission, use, or history rules. Its plural membership is not a world-side belongs-to predicate.Adopt the explicit-choice obligation; reject predicate import. The decision table and Step 5 ask for the entity, collection, and its own beginning, ending, recurrence, and history conditions.
Kit Fine, Towards a Theory of PartComposition comes before derived part claims, and different operations have different application, identity, presence, and character principles.Fine’s broad use of part can also cover set elements or sequence places; that umbrella is too broad for a practitioner-facing FPF relation.Adopt operational priority; narrow the public result. CC-MEM-2 blocks both the inference from belonging to parthood and the inference that parthood is impossible; CC-MEM-3 admits the second claim only after all six A.1 matters pass.
Kit Fine, The Identity of Social GroupsStructured groups can persist through changing manifestations, and the same participants need not identify the same group.An identity-through-change rule does not make a register, corpus, product series, or Suite a structured whole.Adopt the identity questions, not automatic embodiment. CC-MEM-1 requires the collection’s identity and belonging history; the A.1 gate remains separate.

The resulting collection alternatives are distinct:

  • Selected: an ordinary subject-specific belongs-to sentence plus the collection’s own rule.
  • Rejected: one generic MemberOf, because it collapses formal inclusion, classification, participation, collection belonging, and constructive parthood.
  • Rejected for present public use: one qualified generic collection-belonging predicate, because its qualifiers must recreate every subject rule.
  • Retained as a separate possible claim: constructive parthood, but only when its direct relation obtains and all six A.1 matters pass.

A.14 supplies no immediate cross-domain query key for all belongs-to relations; use F.18 to name a narrower relation when repeated query, comparison, or declaration use justifies that extra vocabulary.

The other relations draw on the following bounded contributions. The cited models have different domains and identity commitments; A.14’s rules are FPF adaptations.

  • Measured parts. Krifka’s historical Nominal Reference, Temporal Constitution and Quantification in Event Semantics (1989), §2, ties measurement to a specified part structure and restricts addition to non-overlapping parts. Tao’s An Introduction to Measure Theory, §1.4.3, supplies the general limit: a nonempty set can have zero measure, so proper inclusion need not give strictly smaller measure. Adapt: :5.1 keeps POR-2 as an independent condition and gives one sufficient finite-measure case; POR-3 applies only to admitted disjoint joins. Same-stuff/content, compatible units, boundary identity and any conservation law remain separately stated conditions of the FPF use.
  • Temporal parts. BFO 2020, BFO_0000139, defines transitive temporal parthood between occurrents. The OWL-Time Recommendation (2017), §§4.2.23–4.2.35, distinguishes strict interval inclusion, equality and overlap. Adapt: :5.2 applies proper temporal restriction to a continuing holon under its own identity rule. That holon domain, identity condition, partition-only coverage and non-overlap, and identity-failure return are FPF choices. OWL-Time supplies interval relations; the subject pattern supplies holon identity.
  • Engineering product identity and composition. ISO 15926-2:2003, §5.2.6 (accessible standard excerpt, pp. 108–113), distinguishes simple composition from arrangement and assembly, and functional continuity from matter/energy continuity. The same tank can satisfy both object criteria; a stream can instead have path-based identity. Its temporal-whole-part relation belongs to its own 4D model of possible individuals. Adapt: choose the identity criterion and composition relation before asserting a part claim. FPF’s specific PortionOf conditions and resource conservation accounts come from :5.1 and the applicable domain, not from a blanket rule about all stocks or consumables in ISO 15926.
  • Engineering-model versions. OMG’s Systems Modeling API and Services 1.0 (March 2026), §§7.1.1–7.1.2 and 7.2.3, distinguishes a continuing DataIdentity, separately identified DataVersion values and commit history. Adapt: identify the compared endpoints and the history being asserted. These software identities do not supply C.2.1’s episteme-identity test.
  • Provenance and research versions. The historical PROV-DM Recommendation (2013), §§5.2, 5.4 and 5.5, distinguishes revision, derivation, alternate and specialization relations. Zenodo versioning distinguishes a version DOI from the concept DOI for all versions; its file-correction policy also permits bounded corrections without changing the DOI. Adapt: recover the content and provenance of each endpoint. FPF uses the C.2.1 identity triple and independently obtaining EpistemeEditionRelation for distinct epistemes; A.14 reserves PhaseOf for a proper temporal restriction of one unchanged episteme.

The catalogue keeps direct component, constituent, portion, bearer-dependent aspect, phase, and collection-belonging claims distinct, while a separately grounded constructive part claim remains possible without another universal relation vocabulary.

A.14:14.1 - Aspect branch application

For AspectOf, A.14 adapts the constructor-and-identity questions of Partridge et al. and Florio and Linnebo’s Core Constructional Ontology: which bearer, facet rule, dependent aspect and identity conditions make this structural part? The bearer/facet conditions and required StructPartOf relation are FPF choices. Fine’s historical composition-first treatment motivates identifying the composition operation before the part claim. A.14 adapts that line in A.14:5.3, the decision procedure, and CC-ASP-1 through CC-ASP-4; C.13 slice remains an optional report, not the constructor of the aspect.

The alternatives are routed rather than renamed: measured Characteristic (C.16/A.19), viewpoint or view (E.17), representation or projection (C.29 or its direct pattern), selected partition, and temporal restriction (PhaseOf/C.27.TA). Identify the relation before reusing the word aspect.

A.14:15 - Relations

  • Builds on: A.1, A.7, B.1, B.2, C.13, and B.3.5 for holon identity, strict distinction, gamma-flavour separation, meta-holon transition, constructive grounding, and Working-Model assurance.
  • Coordinates with: C.16 and A.19 for measured Characteristics; E.17.0/E.17.1 for viewpoints and views; C.29 and direct projection patterns for representations; C.27.TA for temporal claims; and A.2, A.2.1, A.3.1, A.3.2, A.15, A.15.1, and A.3.4 when wording concerns a local kind, assignment, Method, Work, or transformation rather than parthood.
  • Used by: architecture, description, evidence, and U-kind admission patterns when their structural claim depends on a parthood relation.

A.14:End

A.15 - System-Role–Method–Work Alignment

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

At a glance. Use this pattern when a team must say which System performed which Work, under which assignment, which Method the Work enacted, and which plan applied without confusing any of those values with a description, capability, record, or result. A precise actual-performer branch first reuses A.13’s core, then A.15.1 independently admits the dated Work, and only afterward F.6 uses the same obtaining assignment when precise assignment-bound attribution is current; an agency characteristic profile remains conditional on its receiving use.

Use this when. Use A.15 when a receiving decision needs to connect classification or assignment, Method, capability, planning and performed Work while keeping the claims distinct. Recover only the values and relations that decision consumes.

Start here when. The team is mixing system classification or assignment with recipe, schedule, capability, or performed Work, often under an ambiguous source word such as role, process, workflow, or activity.

First output. For planning, identify the intended WorkPlan, performer, local system-role kind and Method only as the next decision requires them. For precise actual performance, recover the A.13 core and independently admit dated Work under A.15.1 from its history, Method, extent and containing-System relation. Add F.6 performedUnderAssignment only for precise assignment-bound attribution, using that same obtaining assignment. State that the System performed the Work under the assignment and that the Work enacted the Method only when both relations obtain. Keep descriptions, plans, capability claims, records and results distinct.

Minimum sufficient use. Recover only the values and relations needed by the receiving use. Ordinary orientation can stop at one clear sentence. A reliance-bearing claim may also need occurrence identity and extent, the selected source and its currentness, a capability-fit claim, and the evidence or assurance claim relied on.

Recovered-reference sufficiency condition. Proceed when every value and relation consumed by the claim is recoverable with the meaning, identity and conditions that use needs. Otherwise narrow the claim or recover the missing basis. A bounded reversible probe is one option when its attainable contribution justifies its burden under C.11.DUA. Record a repair or decision request, prospective plan entry or source gap only when the continuation needs it.

Ordinary use. “Robot-7 performed InspectionWork-17 under InspectionAssignment-17, and the Work enacted TurbineInspectionMethod” can be enough when the A.13 core, same obtaining assignment, F.6 link, and enactsMethod relation remain recoverable and the receiving use needs no additional identifiers. A Grade or autonomy profile is not implied.

Reliance-bearing use. Use the fuller frame when assignment identity, assignment state, Method edition, capability fit, plan baseline, approval, evidence, release, or disputed responsibility changes the decision. Responsibility and authority remain separate direct relations; neither follows from a system-role kind or assignment.

Stop condition. Stop when the needed values and relations are clear enough for the supported next use and further separation would not change that use.

Admissible-use examples.

Admissible project useSource-finding or reversible probeNon-admissible use
A maintenance team identifies the local inspection kind, assignment species and occurrence, Method, and any description or WorkPlan needed by its decision. After inspection, it identifies dated Work independently of the inspection record.A briefing lacks a source or relation required for its attempted use; use it to locate or recover that basis before making the unsupported claim.The presence or form of a dashboard, copied approval, generated explanation, label or briefing is treated as proof of assignment, Method, WorkPlan or performed Work. Assess the content’s evidence contribution under the rule for the claim it bears on; use A.10 when that use needs a replayable source-to-use account.

Alignment frame in plain terms. The system-role kind says what contribution kind is in question. The assignment relates this System to that kind while its predicate obtains. The Method is the way the Work is done. A MethodDescription describes the admitted Method; a WorkPlan states possible future Work. Dated Work is what happened. A log reports it and remains distinct from that occurrence.

What goes wrong if missed. A team collapses classification, assignment, recipe, plan, capability, and performed Work into one fuzzy “process” or “role” label, then mistakes documentation for execution, capability for performance, a schedule for an occurrence, or an assignment for responsibility.

What this buys. A compact trace answers who performed the Work, under which assignment, which Method it enacted, and which separate plan and evidence applied, while leaving each additional claim to its direct pattern.

Not this pattern when. Use A.15.1 for one dated Work occurrence, A.15.2 for planning or schedule baselines, A.15.5 for work-entry readiness, A.16 or A.16.1 for a cue that has not become an alignment question, A.6 or A.6.B for boundary or policy wording, E.10.ROLE when role is still unresolved, and A.15.4 when a visible item is being relied on by appearance.

Related pattern contributions. Use A.2 and C.3 to identify local system-role kinds, A.2.1 for direct U.SystemRoleAssignment species, A.13 for the local agency core and any conditionally consumed profile, F.6 for performed-Work attribution through that same assignment, A.15.1 for dated Work, A.15.2 for WorkPlan epistemes, A.15.3 for declaration-local planned-filling content inside a WorkPlan, A.15.4 for work-relevant reliance by appearance, A.15.5 for work-entry readiness, F.11 to align Method and Work vocabulary across contexts, and F.17 for the human-facing term sheet.

Causal-use work boundary. Causal inquiry can use the Method, plan, performer and Work distinctions when those claims are needed. C.28 separately governs the causal-use question, rung, estimand, identification, estimate, sampling and simulation contributions, and supported or unsupported uses. Alignment alone does not establish causal admissibility.

Related-record mistakes. A cue, publication, plan, record, result, evidence item, or approval can help locate a value without becoming that value. Recover the dated Work under A.15.1. State a subject-specific production or result relation only under its direct pattern; for a production-work, entity-inception, or production-completion question, A.15.PROD may instead return one local claim or blocker. Use A.15.4 only when reliance on an encountered appearance is the problem.

Boundary to coarsened renderings. A briefing, summary, redacted note, or coarsened rendering may orient work. Rely on it for an execution, approval, gate, or evidence question only when the sources and relations required by that use remain explicit and reopenable. Use A.6.3.CSC when coarsening itself changes what may be relied on.

Outside-practice result boundary. When one receiving decision or piece of Work needs a bounded result governed by another practice, use A.15.9 to inspect an already-available result before requesting anything new, ask only for the remaining gap, and preserve supplier Method and authority separately from the receiving decision. A.15 keeps the underlying Method, Work, performer, assignment, communication, result, and record distinctions unchanged.

A.15:1 - Problem frame

When the alignment is already clear and ongoing Work still needs one next action chosen from current facts within an applicable domain Method, use A.15.7. It keeps the domain Method, steering Method, deciding System, intended performer, and any later WorkPlan or performed-action claim separate.

Complex work requires several independent distinctions: what a System is; which local system-role kind classifies it; which assignment occurrence obtains and which declared U.SystemRoleAssignment species it instantiates; how Work is done through U.Method; whether an episteme is a U.MethodDescription; which holder capability is relied on; what U.WorkPlan states; which dated Work happened; and which separate assertions, records, results, and evidence concern that Work.

A.15 brings these already defined values together without creating a new process object or redefining their ontologies:

  • A.2 and C.3 identify a local system-role kind and any classification judgment. Classification neither creates an assignment nor proves Work.
  • A.2.1 identifies an assignment occurrence and its declared species under U.SystemRoleAssignment. The species declares HolderSystemSlot, a declaration-local AssignedSystemRoleKindSlot with its local system-role-kind domain, its predicate and applicability, any additional participants, and its occurrence-identity rule. The occurrence supplies the actual participants and extent. Taxonomy, scheme, signature, assertion, evidence, and interval may interpret or describe the claim; they are not generic participants.
  • A.13, A.15.1, and F.6 govern ordered but distinct results. A.13 supplies the System, local agential kind and criterion, classification, obtaining assignment, scope, working situation, window, and adequate core evidence; its characteristic profile is conditional. A.15.1 then independently admits dated Work. Only after admission, and only when the receiving use expressly consumes precise assignment-bound attribution, does F.6 relate that Work to the same assignment through performedUnderAssignment. Its holder projection is used only to compare holder equality with the actual performer already recovered through A.13; F.6 identifies neither assignment nor performer. Missing F.6 attribution does not revoke Work membership.
  • A.3.1 and A.3.2 keep U.Method distinct from U.MethodDescription.
  • A.15.1 and A.15.2 keep actual dated Work distinct from intended WorkPlan and from every record about either.
  • A.2.2, A.10, and neighboring direct patterns keep capability-fit claims, evidence use, source currentness, publication, responsibility, authority, access, results, and assurance outside assignment and Work identity.

When source wording such as process, workflow, action, activity, schedule or role leaves its meaning unresolved, use F.19 and then the applicable E.10, E.10.ARCH or E.10.ROLE rule. Keep ordinary wording when the needed object, relation or action is already clear. Recover the precise FPF value only when the receiving claim depends on it.

A.15:2 - Problem

Without this alignment, several category errors recur:

  1. System-role-kind as part. AuditorSystemRole is placed in structural partOf decomposition although it is a local kind used to classify systems.
  2. Description as execution. A recipe, algorithm, SOP, or MethodDescription is treated as proof that Work occurred.
  3. Capability as Work. Ability and actual performance are collapsed.
  4. Incomplete Work basis or attribution. A Work claim lacks its required performer, assignment, or Method basis, or a precise assignment-bound attribution claim lacks its holder-equality check.
  5. Assignment as responsibility or authority. Holding a system-role assignment is treated as if it established a duty, permission, responsibility, authority, or approval relation.
  6. Universal assignment record. A permissive root signature hides different direct species and turns taxonomy, scheme, context, or source into generic participants.
  7. Actor by association. A kind, assignment, capability, Method, description, plan, or record is made to act. Only the admitted holder system performs Work.
  8. Process soup. One overloaded source word stands for classification, assignment, Method, description, plan, Work, result, and record at once.

A.15:3 - Forces

ForceTension
Structure and enactmentStable structural decomposition must remain distinct from system classification, assignment, Method, plan, capability, and dated Work.
Simple and specialized assignmentsA simple assignment should remain light, while a commission, position, or locus must retain the participant that distinguishes its species and occurrence.
Method, plan, and occurrenceA reusable Method, its description, intended Work, and performed Work must stay connected without becoming one record.
Clarity and precisionPractitioners need ordinary readable claims, while reliance-bearing use may need occurrence identity, evidence use, source currentness, or assurance.
Accountability and proportionalityAuditability may require a full trace, but ordinary orientation should stop at the shortest sufficient relation chain.

A.15:4 - Solution

Recover the values first, then state only the relations needed by the receiving use. A.15 aligns system-role kind, assignment, Method, MethodDescription, capability, WorkPlan, Work, and separate records; it does not create a universal process object or a universal assignment signature.

When wording about changing, producing, selecting, deriving, controlling or maintaining leaves its object unresolved, use E.10.ARCH. A workflow graph, process calculus, matrix, category, embedding or neural representation may describe or serve as a lens over a Method relation structure; its representation form alone establishes no Method, assignment, WorkPlan or Work occurrence.

A.15:4.1 - Core entities kept distinct

  • Local system-role kind. A value such as InspectorSystemRole : U.Kind is admitted under A.2 with C.3 through its U.System candidate domain, operative work-facing membership condition, member/non-member boundary, and continuity rule. It is not a system, assignment, relation slot, capability, Method, Work, responsibility, or authority. A system classification judgment and an assignment occurrence are separate claims.
  • U.SystemRoleAssignment. This is the relation family consumed by A.15 and F.6. It has no permissive root RelationSignature. Each direct species declares HolderSystemSlot : U.System, a declaration-local AssignedSystemRoleKindSlot whose ValueKind is one local system-role-kind domain, its predicate and applicability, every additional participant, and its occurrence-identity rule.
  • U.Method. The run-independent semantic way of doing. A Work occurrence can stand in enactsMethod(W, M); the Method does not act.
  • U.MethodDescription. An already identified U.Episteme whose EntityOfConcern is an admitted Method and whose substantive claims say how that Method is done, as judged by A.3.2. Wording, file form, or publication alone establishes no membership.
  • Holder capability (A.2.2). The holder’s ability to perform named work under stated conditions and bounds. Its assertion, evidence, currentness assessment and fit to a demand remain separate. Ability establishes neither assignment nor performed Work.
  • U.WorkPlan. A U.Episteme about possible future Work, including intended windows, dependencies, performers, and budgets. It does not bring a future Work occurrence into existence.
  • U.Work. The admitted kind for concrete dated Work occurrences. One Work individual has its own temporal extent, at least one obtaining A.15.1 enactsMethod relation, and at least one obtaining locally declared containing-system relation. It may stand in further enactment, affected-referent, binding, resource-use, production, and result relations when the receiving use needs those independently obtaining facts. Any log, ticket, assertion, description, or performed-work record is a separate episteme.

Work occurrence and record boundary. Recover the affected-referent, transformation, speech-act effect, commitment effect, production, delivery, acceptance, or other relation under its direct pattern. Labels such as operational, communicative and epistemic can remain recognition cues; they do not define Work subkinds by enumeration.

Didactic note for managers: the chef analogy. ChefSystemRole is one local system-role kind. A kitchen-assignment species defines the holder and assigned-kind positions and adds shift, station, or commission only when it changes the assignment. A particular assignment fills those positions with the chef System, the kind, and any additional value. A cookbook can be a MethodDescription; the chef’s skill can be a capability; a WorkPlan can schedule cooking; and making one souffle on Tuesday is dated Work. Its temporal and resource-use relations can state the 25-minute extent, eggs, butter, and consumed gas, while a kitchen log remains a separate episteme. A restaurant vocabulary or scheme can help interpret the claims without becoming a participant in every assignment. The cookbook, skill, plan, assignment, and log do not cook.

A.15:4.2 - Canonical relations

graph TD
    subgraph "Direct system-role assignment species"
        H["holder H : U.System"] -- "HolderSystemSlot" --> RA["RA : InspectionShiftAssignment<br/><: U.SystemRoleAssignment"]
        K["InspectorSystemRole<br/>local kind"] -- "AssignedSystemRoleKindSlot" --> RA
    end

    subgraph "Method, description, and capability"
        M["M : U.Method"]
        D["D : U.Episteme<br/>A.3.2 membership: U.MethodDescription<br/>EntityOfConcern = M"]
        Cap["Qualified ability claim about H"]
        Fit["capability-fit condition"] -- "tests" --> Cap
    end

    W["W : U.Work"] -- "performedUnderAssignment<br/>holder equality check: RA.Holder = H" --> RA
    W -- "enactsMethod" --> M
    style K fill:#fff2cc,stroke:#d6b656,stroke-width:2px
    style Cap fill:#d5e8d4,stroke:#82b366,stroke-width:2px
    style Fit fill:#d5e8d4,stroke:#82b366,stroke-width:2px,stroke-dasharray: 4 4
    style M fill:#d5e8d4,stroke:#82b366,stroke-width:2px
    style D fill:#f8cecc,stroke:#b85450,stroke-width:2px
    style H fill:#e1d5e7,stroke:#9673a6,stroke-width:2px
    style RA fill:#dae8fc,stroke:#6c8ebf,stroke-width:3px,stroke-dasharray: 5 5
    style W fill:#ffe6cc,stroke:#d79b00,stroke-width:2px,font-weight:bold

The diagram shows a simple direct assignment species. A stronger appointment can declare an additional participant such as a review commission; that specialized occurrence itself is the U.SystemRoleAssignment. Do not create a weaker generic occurrence beside it. The displayed F.6 edge is included because this example claims precise assignment-bound attribution; a Work claim that does not need that attribution omits it.

  • Capability fit. A MethodDescription, WorkPlan, or work-admission assertion may require a holder capability threshold. The fit condition compares the holder’s qualified ability claim with the receiving work conditions and bounds and may cite declared measures, U.Characteristic values, Q-Bundle slots, or architecture-characteristic criteria. It is neither an assignment participant nor a second capability kind.
  • MethodDescription membership. D is a U.MethodDescription only when A.3.2 recovers Method M as its EntityOfConcern and at least one substantive way-of-doing claim. “D describes M” is shorthand for that constitution and membership result, not another binary relation.
  • enactsMethod(W : U.Work, M : U.Method). This relation states which Method the dated Work enacts. A.15.1 defines its participant order, predicate, occurrence identity, and multiplicity. It neither attributes a performer nor turns a description into the Method.
  • performedUnderAssignment(W : U.Work, RA : U.SystemRoleAssignment). F.6 defines this relation. For a precise actual performer, RA is the same obtaining assignment used by A.13 for the action, scope, working situation, and window. It must be an occurrence of a declared assignment species, have the A.13-qualified System as holder, and cover the Work while the species predicate obtains. The assignment is the attribution ground, not the actor. A record may state the relation without constituting it. Read an existing performedBy(W, RA) claim only through the F.6 compatibility boundary after resolving the holder System; do not author new claims with that spelling.

One assignment occurrence continues through the maximal uninterrupted interval in which its direct species predicate obtains for fixed participants. A declared interval, taxonomy, scheme, KindSignature, assertion, evidence item, or selected model-use structure can describe or interpret the claim but does not create the occurrence or become a generic participant.

For a precise performed occurrence, first recover the A.13 core for the actual performer System and action, then admit W : U.Work under A.15.1 from its independent occurrence, Method, extent, and containment facts. Only afterward trace W to the same RA through F.6 performedUnderAssignment when the receiving use needs precise assignment-bound attribution, and compare RA.HolderSystemSlot with the already recovered performer; F.6 identifies neither. Trace W to M separately through enactsMethod. Cite a characteristic profile only when conditionally consumed; cite a MethodDescription, plan, capability claim, evidence item, taxonomy, or scheme separately only when the receiving use relies on it. The performer System acts; the kind, assignment, capability, Method, description, plan, evidence, and record do not.

A.15:4.3 - Bounded specialization scouting and CheckpointReturn

For a human-plus-AI pair planning tool calls or probing a route, recover only the Systems, assignments, Methods, plans and Work needed by the alignment claim, with their applicable admission grounds. The pair may use four local system-role kinds for this bounded work: OutcomeCriterionHolderSystemRole, AIScoutSystemRole, AISpecialistProbeSystemRole, and CommitAuthoritySystemRole. Claim an assignment only by naming its occurrence and declared species under U.SystemRoleAssignment. The CommitAuthoritySystemRole name does not supply decision authority; any authority relation must obtain independently.

First distinguish the current question. If another probe could change which option survives the OptionSet, return to C.11. If changed live facts or domain-Method limits could change the next action during ongoing Work, return to A.15.7. Use C.24 when an applicable domain prescription or a completed decision has fixed the action or option and tool or service calls must be planned.

Use a sufficient existing CallPlan directly. Otherwise use C.24 to construct the fixed action’s route from available inputs, qualified Method contributions and required intermediate results, then check its feasibility. Select a bounded scout or probe only for a specific unresolved fact that could change the usable route and when the attainable answer justifies the inquiry under the applicable criterion, budget and permission. After actual probing, return what was tested and observed in a CheckpointReturn. Use A.15 for the assignment, Method, plan and Work claims this use needs, and C.24 for planning and checkpoint semantics. When an E.16 autonomy budget governs the scouting, retain its scout budget, probe budget, commit checkpoint and guard or override path.

After a bounded probe, its CheckpointReturn carries the C.24 action basis and:

  • the objective or TaskFamily and the applicable outcome criterion;
  • the Methods tested, with approach descriptions when needed;
  • the evidence observed for those tests and important failure signals, including progress toward any work-measure threshold used by the decision;
  • burned and residual budget;
  • the recommended next action, such as a further bounded probe, adoption of an identified CallPlan, a narrower supported claim, return to the applicable pattern or domain prescription, or stop; and
  • the commit trigger for considering whether to end the probe and adopt an identified CallPlan.

The return is evidence about the tested approaches, observed results, budget and proposed continuation. It is not the selected Method, U.WorkPlan or actual Work. Use the trigger, probe evidence, residual budget and any required safety or assurance result to decide whether to adopt the identified plan, probe further or stop. Plan adoption, permission to perform calls and actual Work remain separate. Recover the execution-evidence, provenance or rollout-decision claims consumed by that decision or later rollout under their applicable rules.

A.15:4.4 - Boundary to A.15.4 Work-Relevant Appearance-Based Reliance Repair

Use A.15.4 when an encountered episteme, carrier, display, credential view, generated explanation, copied statement, provenance mark, dashboard tile, schema wording, API wording, or source-relation chain is being relied on by appearance for Work, assignment currentness, assignment state, source currentness, approval, authorization, gate passage, evidence, engineering justification, release, or another reliance-bearing claim.

A.15 itself keeps the local system-role kind, holder system, direct assignment occurrence, Method, MethodDescription, WorkPlan, dated Work occurrence, and every separate episteme distinct. A.15.4 recovers the project-side value and relation that must hold before the visible item can warrant the attempted use.

A principle scheme, functional diagram, scenario, screen, or explanation that exposes an E.18.1 P2W carry-through structure may help a team plan Work or find a source. It does not become the selected Method, plan, Work occurrence, result, evidence, or authority by publication.

A.15:4.4a - Inspecting Method–Work Alignment Across an Unfolding Structure

Do not create a linkage record merely because one unfolding structure mentions several Method- and Work-related values. Keep each direct relation under the pattern that defines it. When a receiving use must preserve an inspectable explanation across those relations, write one bounded C.2.1 episteme whose EntityOfConcern is the selected unfolding U.Structure. Its ClaimGraph may cite, as separate claims, the selected Method and Method-relation structure, MethodDescription epistemes, relevant local system-role kinds and assignment occurrences, the Work that enacts the Method, Work-part relations, independently identified transformations and their direct Work-to-change claims, intended WorkPlans, readiness results, capability-fit conditions, evidence, assurance, and gate decisions. Include only claims needed by that receiving use.

Call this episteme a Method–Work alignment account in ordinary prose. Its identity comes from its EntityOfConcern, ClaimGraph, and effective ReferenceScheme, not from a field bundle. Each claim in the account remains defined or tested by its own pattern: A.3.1 for Method, A.3.2 for MethodDescription, A.15.2 for planning, A.15.5 for readiness, A.15.1 for dated Work and Work relations, B.3 for assurance, A.20 for internal-constraint results, and A.21 for gate decisions. Assess evidence under the rule for the claim it bears on; use A.10 when a replayable source-to-use account is needed. If the useful account would need several unrelated entities of concern, split it instead of using one umbrella record.

Another structure, such as CGUS, P2W, P2S, an improvement-loop slice or a transformation-flow slice, may cite the episteme when its receiving use needs the alignment explanation. Recover the cited claims under their source, identity and applicability conditions; reuse an established result while those grounds remain valid.

A.15:4.5 - Boundary to A.15.5 Work-Entry Readiness

Use A.15.5 when the current question is whether intended Work is ready to enter its boundary. A.15 keeps system-role kind, assignment, Method, plan, and Work distinct; A.15.5 carries WorkEntryReadiness@Context, FullKitCondition, commitment disposition, resource-readiness references, WIP or flow-policy references, planned baselines, and launch-gate references when those values are current.

Readiness is not performed Work, evidence sufficiency, or gate passage. A briefing, dashboard, source bundle, or P2W record may cue A.15.5. Ground the result in the WorkPlan being judged, the PlanItem content the criterion consumes, that criterion and the facts used to evaluate it. State the readiness result, its qualification window, and the applicable stop or degraded-use condition. Identify missing or unknown required inputs; include performed preparation Work or a planned baseline only when the criterion or receiving use consumes it. Address the PlanItem content through that WorkPlan; it is not another readiness target.

A.15:5 - Archetypal Grounding

Use this alignment whenever the live question joins a holder system, local system-role kind, assignment occurrence, Method, plan, capability, or performed Work. Physical engineering, knowledge work, and socio-technical work can use the same distinctions without turning A.15 into a universal process ontology.

Boundary case — possessed algorithm versus enacted Method. Robot-7 : U.System is classified under InspectorSystemRole and is the holder of InspectionAssignment-17, an occurrence of a direct maintenance-assignment species. A capability claim may say that Robot-7 can inspect turbines, and source prose may say it “possesses inspection algorithm A”. Neither claim is dated performance, and neither makes TurbineInspectionProcedure-v3 a U.MethodDescription. If InspectionWork-17 occurs, first recover Robot-7’s full A.13 core through that same obtaining assignment and let A.15.1 independently admit the Work. Then, because this alignment also expressly consumes precise assignment-bound attribution, establish F.6 through InspectionAssignment-17. The already recovered performer performed the Work under that assignment, and the Work enacted TurbineInspection@Maintenance-2026. Use A.3.2 to decide whether the procedure episteme is a MethodDescription. Robot-7 acts; the kind, assignment, capability, algorithm wording, Method, and description do not.

Alignment positionManufacturingScientific peer review
Local system-role kindWeldingRobotSystemRolePeerReviewerSystemRole
Holder systemABB_Robot_Model_IRB_6700, designating one particular robot U.System in this hypothetical case; IRB 6700 is its model designationDr_Alice_Smith, modeled as an admitted U.System
Direct assignment species and occurrenceFactoryWeldingAssignment with the robot and WeldingRobotSystemRole; include another participant, for example a factory line or work order, only if that species predicate depends on itJournalReviewAssignment with Alice and PeerReviewerSystemRole; a commission-sensitive appointment species also carries the review commission
Separate semantic sources when usedFactoryProductionSystemRoles-2026 and Factory-Line-B-Scheme may be used as sources for classification or interpretation claims under the applicable source and evidence relationsPhysicsPeerReviewSystemRoles-2026 and PhysicsLetters-A-Review-Scheme may be used as sources for classification or interpretation claims under the applicable source and evidence relations
Selected model-use structure, only when currentCited by the receiving factory interpretation claim, never inserted as a participant of every assignment speciesCited by the receiving journal interpretation claim, never inserted as a participant of every assignment species
U.MethodDescription epistemeThe procedure episteme available through Welding_Procedure_WP-28A.pdf, with admitted WeldingMethod as EntityOfConcern and substantive way-of-doing claimsThe guideline episteme available through Peer_Review_Guidelines_v3.docx, with admitted PeerReviewMethod as EntityOfConcern and substantive way-of-doing claims
Holder capability, when relied onability to execute a 3F welding seam within a declared envelope and current windowability to evaluate a quantum-optics manuscript within a declared envelope and current window
Work occurrenceWeld_Job_#78345, whose temporal relation covers 15:32–15:34 UTC on 2025-08-15; separate resource-use relations connect 1.2 kWh and 5 g Argon, and enactsMethod connects WeldingMethodReview_of_Manuscript_#PL-2025-018, whose temporal relation ends on 2025-08-15; a separate resource-use relation connects four hours of reviewer time, and enactsMethod connects PeerReviewMethod

Worked continuation: attribution can remain open after Work is identified. In a constructed inspection, Robot-7 is an admitted System satisfying the local InspectorSystemRole criterion of detecting the specified blade discontinuities from the required images. InspectionAssignment-18 obtains under its direct maintenance-assignment species for Robot-7 in the morning inspection window. The performance history places InspectionWork-18 from 08:10 to 08:25 on Day-D; its independently established enactsMethod relation identifies the admitted TurbineInspection@Maintenance-2026 Method, and the locally declared containing-System relation identifies the independently admitted System MaintenanceCell-1. These facts satisfy the stated A.13 core and the independent A.15.1 admission basis.

The receiving attribution question additionally asks whether InspectionWork-18 was performed under InspectionAssignment-18. The case establishes that Robot-7 accepted the inspection task under InspectionAssignment-18 and carried out InspectionWork-18 as that assigned task. The assignment’s holder is Robot-7 and its obtaining interval is 08:00–09:00. With the declared species and its obtaining conditions also established, these facts satisfy the F.6 constraints and the separate Work–assignment link. Another assignment with the same holder and interval does not inherit that link. If later evidence leaves the assignment’s ending time unresolved, reopen that attribution and every decision relying on it. Preserve the independently established performance history and Method enactment. Retain Work identity where its independent admission grounds still hold, and recheck any admission condition that consumed the disputed premise. Missing F.6 attribution alone establishes neither no Work nor successful inspection; success requires its own result and evidence claim.

Key takeaway. Both cases use an admitted holder System, a local system-role kind, an assignment occurrence and its declared species, a Method, a separate MethodDescription, a capability relied on for the case, and dated Work. Their taxonomies, schemes, commissions, records, and results remain separate values and relations. This common alignment does not erase their different domain ontologies.

A.15:5.1.a - Briefing guides orientation, not execution

Source set. A release team has one deployment method description, one current work plan, one approval or decision record when required, and the evidence records and evidence relations used to decide whether the rollout may proceed. A short rollout briefing is prepared for the daily stand-up.

Briefing slice. For stand-up orientation: the source bundle reports that the rollback procedure passed its named check. Before rollout, recover that result and the deployment Method, WorkPlan and any required authorization and evidence under their applicable conditions.

This briefing may orient the team and cue attention. If the team wants to execute from the briefing alone, use A.15.4 or the evidence, gate, decision, or assurance pattern that defines or tests the claim to recover the missing project-side kind and reference. Inside A.15, keep only the system-role kind, assignment, Method, plan, and Work-occurrence separation.

A.15:5.1.b - P2W principle-scheme publication guides planning, not occurrence

Source set. A team has a principle scheme that shows an E.18.1 P2W carry-through structure for a fabrication task: signature or principle episteme, method-family selection, selected method, U.WorkPlan, an actual Work occurrence admitted under U.Work, a separate work-result record, and result measurement.

Published slice. For the proposed next batch, Method M-2 is selected from the declared family; prepare WorkPlan WP-17 before performing that batch's planned Work.

This publication can guide Method inspection and planning. Keep the selected Method, WorkPlan, any earlier actual Work occurrence, its record and result measurement distinct. For evidence, gate or engineering reliance, recover the required project-side claim under its direct rule. If that basis is missing, retain the supported planning use and state only the gap or continuation the receiver needs.

A.15:5.1.c - Scenario guides method selection, not performed work

Source set. A method-selection scenario says that material X is below threshold T, resource window W is available, and the fabrication cell is under setup condition S. The scenario is admitted source material; a publication form or carrier may expose that source material for choosing between method families but does not become the selected method or plan.

Published slice. Under scenario S, method family MF-2 is admissible for planning; choose the selected method and prepare the work plan before execution.

The scenario can guide Method-family selection and planning. Identify a selected Method or resulting WorkPlan in the account where that result is needed. Ground any later dated Work independently under A.15.1; a record may designate it but is not that occurrence. For evidence, gate or engineering-justification reliance, establish the required claim, relation or decision under its direct rule, such as A.20 for internal-constraint results, A.21 for gate decisions or B.3 for assurance. Use A.10 when that reliance needs a replayable source-to-use account. If a required basis is unavailable, narrow the use and keep the needed gap or continuation in the receiving account.

A.15:6 - Bias-Annotation

Bias lenses: Gov, Arch, Onto and Epist, Prag, Did. Scope: Universal for system-role–Method–Work alignment across engineering, operational, and knowledge-work settings.

Bias riskFailureRepair
Governance biasA familiar system-role label, assignment row, approval display, or status is treated as proof that Work happened or responsibility obtains.Keep classification, assignment, Work, responsibility, authority, and evidence in their direct relations.
Architectural biasA system-role kind, capability, fit condition, Method, or record is placed in structural decomposition.Keep structure, classification, dependent capability, relations, epistemes, and dated Work distinct.
Epistemic biasA recipe, schedule, roster, or log is treated as its world-side referent.Recover the Method, assignment, WorkPlan, Work, and obtaining relations; keep the source as an episteme.
Pragmatic biasOne overloaded process or role term is retained because it feels shorter.Use E.10.ARCH or E.10.ROLE, then write the shortest sentence that names the recovered values.
Didactic biasThe chef analogy hides direct-species and occurrence requirements.Recover the concrete assignment species; add F.6 only for precise assignment-bound attribution. An ordinary explanation needs no complete schema.

A.15:7 - Conformance Checklist

IDCheckWhy
CC-A15-1Keep local system-role kind, U.SystemRoleAssignment, U.Method, U.MethodDescription, qualified holder-ability claim, U.WorkPlan, U.Work, and every record or result distinct.Prevents one alignment frame from becoming one object.
CC-A15-1aTreat a dated Work individual as world-side; keep assertions, descriptions, logs, tickets, and performed-work records as separate epistemes. Actual performer, Method, temporal, locally declared containing-system, affected-referent, binding, and resource-use relations obtain independently and are not stored fields of the occurrence.Blocks record fields from constituting Work.
CC-A15-2Keep the reusable Method, its description, intended Work, and performed Work distinct. Operational events do not mutate a MethodDescription or WorkPlan.Prevents recipe, schedule, and execution collapse.
CC-A15-3For a precise actual performer, reuse the A.13 core and independently admit dated Work through A.15.1. Only when the receiving use expressly consumes precise assignment-bound attribution, relate that Work through the same obtaining occurrence of a directly declared species under U.SystemRoleAssignment; confirm that RA.HolderSystemSlot equals the already recovered performer and that the assignment predicate covers the Work interval. Require a characteristic profile only when conditionally consumed.Preserves the independently recovered performer and Work while adding only the conditional attribution; F.6 discovers neither and no universal assignment signature is invented.
CC-A15-4For precise assignment-bound attribution, trace the A.13-qualified H through the same obtaining assignment RA, then W -performedUnderAssignment-> RA, RA.HolderSystemSlot -> H, and W -enactsMethod-> M. Cite characteristic profile, MethodDescription, plan, capability, source, and evidence separately only when relied on.Preserves one inspectable A.13→A.15.1→F.6 chain without turning interpretation metadata into participants.
CC-A15-5Keep system-role kinds, capabilities, fit predicates, Methods, and evidence or assurance records out of partOf hierarchies unless another direct pattern admits a structural relation.Blocks classification, evidence, and assurance as parts.
CC-A15-6Attribute resource use to dated Work through obtaining relations, not to a MethodDescription, WorkPlan, capability, assignment, or fit predicate.Keeps costs with performance.
CC-A15-7Use U.WorkPlan for intended Work and identify actual Work independently.Stops schedule-as-performance drift.
CC-A15-8Resolve ambiguous process, workflow, activity, schedule or role wording through F.19 and the applicable E.10 rule. Retain ordinary wording whose meaning is already clear.A cue prompts inspection rather than automatic formalization.
CC-A15-9State enactsMethod and performedUnderAssignment separately. Only the admitted holder System with its A.13 core performs Work; a profile is conditional. A capability or algorithm-possession phrase proves neither performance nor MethodDescription membership. Spontaneous physical evolution without this alignment is not Work. Use A.3.4 to identify an actual bounded change, and A.3.3 when a U.Dynamics episteme describing its state space and transition law is needed.Prevents kind, assignment, capability, Method, description, plan, dynamics, and records from becoming actors.
CC-A15-10Treat a speech act that institutes an assignment, authorization, or gate-relevant effect as its own Work occurrence only when A.15.1 admission and the effect relation obtain.Keeps the communicative Work distinct from later operational Work.
CC-A15-11Recover the assignment’s direct species, local assigned-kind domain, participants, predicate, and occurrence. Taxonomy, scheme, signature, context, and source are cited separately when the receiving claim uses them. An approver or deployer label neither creates a Work subkind nor proves performance.Prevents a permissive assignment record and kind-by-label.
CC-A15-12For causal intervention or sampling, state the Method, description, plan, dated Work, assignment attribution or enactment claims the use needs, under their own rules. Use C.28 for the causal-use question, rung, estimand, separate support components, support result and admissible-use boundary.Keeps work alignment from becoming causal authority or a compulsory full claim set.
CC-A15-13Use A.15.4 when a visible item is relied on by appearance; retain only the system-role–Method–Work separation here.Keeps reliance repair out of the alignment kernel.
CC-A15-14Keep an E.18.1 P2W structure, its publication, selected Method, WorkPlan, Work, result record, and measurement distinct.Publication alone establishes none of the project-side values.

A.15:8 - Common Anti-Patterns and How to Avoid Them

  • System-role-kind as part. Do not place InspectorSystemRole, a capability, fit condition, or evidence or assurance record in structural decomposition merely because it appears on an architecture diagram.
  • Universal assignment signature. Do not give U.SystemRoleAssignment one permissive root signature. Recover the direct species and its local assigned-kind domain.
  • Generic assignment beside an appointment. Let the specialized appointment occurrence itself belong to U.SystemRoleAssignment; F.6 uses its common holder projection.
  • Recipe as evidence. A MethodDescription can identify or constrain a Method but does not prove performed Work.
  • Plan as performed Work. A schedule or intended-assignment claim remains distinct from dated Work, which is identified independently under A.15.1; use A.15.2 for WorkPlan membership.
  • Capability as Work. Ability, a capability statement, or a passing fit condition is not performance.
  • Assignment as responsibility or authority. Recover the direct neighboring relation required by the claim, for example responsibility, commitment, permission, authority, access, or gate passage, or return its missing governor.
  • Approval collapse. Keep approval or authorization Work and the operational Work it permits as separate occurrences and effect relations.
  • Process soup. Resolve ambiguous source wording before relying on it; do not create a generic process object.
  • Appearance as execution. Use A.15.4 when a dashboard, credential, copied approval, generated explanation, provenance label, or command-like cue is being relied on by appearance.
  • P2W publication as Work. A principle scheme, functional diagram, scenario, screen, or explanation can guide planning without becoming Method, WorkPlan, Work, result, evidence, gate, or justification.

A.15:9 - Consequences

GainCost or trade-off
Teams can ask which System performed which Work, under which assignment and Method, without making a kind or document act.Reliance-bearing use must recover the assignment occurrence and its declared species rather than stop at a familiar label.
Simple assignments stay simple while commission-, position-, or locus-sensitive assignments preserve their participants.Each bounded vocabulary must admit the direct species and local system-role-kind domain it uses.
MethodDescription, WorkPlan, Work, result, and evidence can change independently. A MethodDescription can be revised without rewriting past Work; a holder can be replaced when the replacement satisfies the required classification, assignment, and capability-fit conditions.A decision-relevant case may need several short direct claims instead of one overloaded record.
Responsibility, authority, permission, capability, assignment state, and result stay available without being inferred from assignment.The receiving use must say which of those additional relations it needs.
The chef analogy and ordinary first sentence make the distinction teachable.Readers still need one concrete direct-species example so the analogy does not hide assignment identity.

For example, AuditorSystemRole can be the local kind used by an audit-assignment species. A particular assignment names its holder System, but this precise attribution still requires F.6 to relate ApprovalWork-17 to that same assignment and confirm holder equality with the A.13-qualified performer after A.15.1 independently admits the Work. Any decision authority, responsibility, gate effect, Method, capability fit, result, and evidence are separate claims. The kind name and assignment prove none of them.

A.15:10 - Rationale

Teams often store classification, assignment, recipe, plan, capability, execution, result, and evidence in one “process” record, then cannot tell which fact changed. A.15 keeps the values separate and adds only the two alignment relations needed most often: performed-Work attribution and Method enactment.

The separation follows established ontology and practice distinctions among enduring systems, relation occurrences, event-like Work, and epistemes. Process-theory formalisms such as Petri nets and process calculi remain source lineage for dynamic interaction, but their word process is recovered here to Method, MethodDescription, WorkPlan, dated Work, Dynamics, Transformation, or a separate episteme rather than imported as one FPF object. FPF adapts the useful distinctions through local system-role kinds, assignment species and their occurrences, a common holder projection, Methods, WorkPlans, dated Work, and neighboring relations; it does not import a foreign hierarchy.

The distinction is operationally useful. When work fails, a team can ask whether the wrong system was assigned, the assignment did not cover the Work, the Method was unsuitable, the MethodDescription was wrong, the plan was stale, the capability claim was unsupported, or the performed occurrence departed from the Method. Correcting one answer need not rewrite the others.

A.15:11 - SoTA-Echoing: Adopted Invariants and Rejected Shortcuts

Practice needSource line and statusFPF adaptationRejected shortcut
Keep case, decision, plan, and executed occurrence separable.OMG CMMN 1.1 (2016) and OMG DMN 1.5 (2024) provide mature modeling lineage; ITIL 4 Change Enablement (2023) provides current practitioner guidance.Keep MethodDescription, WorkPlan, approval Work, and operational Work separate, with every Work occurrence admitted on its own A.15.1 basis.One undifferentiated process object.
Keep system classification, relation occurrence, and dated Work distinct.Almeida, Guizzardi, Sales, and Fonseca, gUFO (2026 preprint), is a current foundational-ontology comparator rather than imported hierarchy.Retain FPF’s local system-role kinds, direct assignment species, holder projection, and Work identity laws.A foreign role hierarchy or relation model deciding FPF identity.
Recover event, performer, qualified association, and records without making a log row the event.OCEL 2.0 (2024) is current object-centric event-log practice; W3C PROV-O (2013) is representation lineage.Identify dated Work and the assignment occurrence first; keep logs and provenance as separate epistemes and relations.Anonymous Work, assignment by label, or record-as-occurrence.
Keep authorization acts and the operations they permit distinct.ITIL 4 Change Enablement (2023) and DMN 1.5 (2024) separate assessment, decision, authorization, scheduling, and realization.Admit each communicative or operational Work occurrence independently and state its effect relation.Approval collapsed into later operational Work, or label-defined Work subkinds.
Keep bounded exploration separate from committed rollout.Current agentic tool-use, self-correction, and human-in-the-loop work-control practice extends the ReAct, Toolformer, and Reflexion lines with explicit checkpoints and bounded tool use.For tool-call planning after the action is fixed, keep the relevant System, assignment, Method, plan and Work claims distinct. Retain an adequate CallPlan; after a needed bounded probe, return the tested Methods, evidence, budget and commit trigger in CheckpointReturn under C.24, with E.16 controls when an autonomy budget applies.One successful probe silently becomes the selected Method, WorkPlan, or rollout.

Use the direct FPF identity rules for the alignment claims above. Use C.30.AD for an architecture-description question.

For visible credential, provenance, dashboard, explanation, or composed-source cases that require a project-side value and relation before reliance, use A.15.4.

A.15:12 - Relations

  • A.15.9 coordinates one receiving decision or piece of Work with one bounded result governed by another practice. It first tests an already-available result, requests only a remaining gap, and preserves supplier Method and authority separately from receiver decision authority; it creates no new alignment object or result kind.

  • A.15.7 supplies the situation-responsive steering Method after current Work, its domain Method, and relevant facts are known; it returns the selected action, intended performer, and stop or feedback condition without making the answer into Work.

  • Architecture-work boundary: C.32.P2S and C.32.PAD may cite MethodDescriptions, pattern-use references, system-role assignments, separate responsibility or authority relations, readiness exits, and expected structure effects. C.32.ADR may publish those references. A.15 supplies only Method, description, plan, readiness, performed Work, and attribution distinctions.

  • Uses: A.7 for strict distinction among system-role kind, assignment, Method, MethodDescription, plan, Work, and records.

  • Builds on: A.2 and C.3 for local system-role kinds and classification; A.2.1 for direct U.SystemRoleAssignment species; A.13 for the local agency core and conditionally consumed profile; A.2.2 for capability; A.2.5 for SystemRoleAssignmentStateRelation; A.2.7 for relations among system-role kinds; A.6.5 for relation-slot discipline; A.3.1/A.3.2/A.3.3/A.3.4 for Method, MethodDescription, Dynamics, and Transformation, respectively; A.15.1 for independent Work admission; A.15.2 for WorkPlan; A.15.3 for declaration-local planned-filling content inside that WorkPlan; A.15.5 for readiness; and F.6 for the later performedUnderAssignment relation and holder-equality projection only when precise assignment-bound attribution is consumed.

  • Coordinates with: A.15.4 for work-relevant reliance repair; E.10, E.10.ARCH, and E.10.ROLE for wording recovery; A.6 for boundary and policy claims; A.10 for evidence and provenance; B.3 for assurance; A.20 and A.21 for constraints and gates; C.28 for causal-use admissibility; C.29 for mathematical-lens use; E.18.1 for P2W carry-through; C.32.P2S for architecturing-flow references; and E.17.EFP for generated-explanation faithfulness.

  • Used in: claims that must keep systems, local system-role kinds, assignments, Methods, WorkPlans, Work occurrences, result records, and reliance repairs distinct. A.15 is not a generic process ontology, workflow engine, evidence graph, gate pattern, or publication pattern.

A.15:12a - Coordinated-work evidence and distributed-state relation note

Use A.15 first when the claim concerns which system performed which Work, under which system-role assignment, which Method the Work enacted, and which separate result is claimed. Coordinated Work, routine skill, team alignment, tacit knowledge, and fit among assignment, Method, and Work are not quantum-like by default.

Application choices:

  1. Name the holder systems, local system-role kinds, assignments, Methods, Work occurrences, and separate results needed by the claim.
  2. State which Work occurrences and which separate C.2.1 assertions, traces, observations, reports, or metrics make the coordination visible.
  3. Ask whether ordinary system-role–Method–Work alignment explains the case. If yes, stop in A.15.
  4. Add a C.26.2 low-recoverability distributed-state reading only after establishing its collective U.System bearer and boundary under C.26.2, and only when no participant statement, local component report, single evidence record, dashboard, or exported representation carries the inferred state faithfully enough for its intended use. Without that collective bearer, retain ordinary A.15 alignment of individual performers.
  5. State the weakest evidence-bound reading, its time window, rival explanations, and export loss.
  6. Use C.26.2:4.11 to select the evidence posture and additional support needed by the intended use. Use A.10 when the selected posture or intended reliance requires a replayable account of evidence provenance and bounded reliance. Obtain a B.3 assurance result for the named target claim and receiving use when an actual assurance claim is current. QLP-3 use or a direct domain requirement for assurance requires that claim and result. Momentary, low-consequence local Work guidance does not by itself require B.3.

The C.26.2 reading is a minimal evidence-bound U.Episteme claim about that collective System. It is not a group mind, performed Work, evidence sufficiency, or assurance by itself.

PositionRequired content
Evidence or provenance relationWork, or a separate assertion, trace, observation, report, or metric about it, connected to the reading through an independently established direct evidence/provenance relation. Use A.10 when a replayable source-to-use account is needed, and G.6 when a trace representation is needed.
Time windowThe interval for which the reading is supported and any local stop; add decay or refresh conditions when the intended reuse, contest or consequential reliance needs them.
Probe or occasionThe question, task, workshop, incident, handover, dashboard, or coordination situation that made the state inferable
Weakest claimThe minimal distributed-state reading carried by the sources
Rival explanationsFor example, routine compliance, policy, command, coincidence, incentive, documentation, or local skill
Export lossWhat is lost when the reading is summarized into one report, score, or statement

Useful outputs are an A.15 alignment claim when assignments and Work explain the case; a C.26.2 reading about the declared collective System within its boundary when the evidence survives ordinary rivals; an A.10 account of the evidence relation; a B.3 assurance result for a current named assurance claim, including the claim required by QLP-3 use or a direct domain rule; or no distributed-state reading when the sources, rivals, or time window cannot be named.

A.15:12b - C.29 mathematical-lens use relation

When a mathematical lens helps select a Method, compare Method families, shape a WorkPlan, or diagnose Work, use an adequate domain result directly, retaining the correspondence, application conditions and material limits needed by the claim. Use C.29 when a separate mathematical-representation choice, transfer or reliance question remains. The next concrete value remains under its direct pattern: ChoiceResult or another local choice record when a choice is made, the selected Method when Method selection is claimed, U.WorkPlan for intent, dated Work for execution, a separate result record for a result claim, and A.15.4 when a reliance appearance is being used as the reason before the required relation is known. A mathematical lens may explain why a distinction is useful; it does not make a plan into performed Work or a Method explanation into execution evidence.

A.15:12c - P2W Work-Family Split

When an E.18.1 P2W use reaches work planning or work-entry readiness, keep the selected Method, one U.WorkPlan with any declaration-local SlotFillingsPlanItem content, WorkEntryReadiness@Context, dated Work occurrence, and separate result records distinct. A planned-filling row is addressable only through that WorkPlan and gains no independent identity. A principle scheme, functional diagram or scenario may help identify a Method or planning question and guide its examination. Establish the particular Method, WorkPlan, readiness result or dated Work under its own pattern before asserting or relying on that value.

Work planning may cite evidence and currentness requests for the direct relation under repair. A.15.5 may cite the WorkPlan and designate declaration-local PlanItem content when its readiness criterion uses that content. Name evidence, gate passage, performed Work, result measurement, assurance, or refresh before relying on a planning or readiness record for that stronger claim.

A.15:12d - P2W Performed-Work Relation

When E.18.1 reaches performed Work, keep U.Work as the admitted kind and identify one dated occurrence under it.

A performed-work record is a separate U.Episteme. It may cite a WorkPlan, planned baseline, and Work occurrence. It can state bindings, performed values, substitutions, variance, telemetry, outputs, outcome claims, and result references only through independently obtaining relations; none is stored in or constituted by the Work occurrence. Comparator, transport, PrincipleFrame, formal-substrate signature, evidence, assurance, and gate relations remain separate.

A.15:12e - P2W Integration as System-Role Assignment and Work Feasibility

When E.18.1 uses integration to ask whether an admitted system can hold a local system-role kind and perform Work under interface constraints, name the system-role kind, the direct U.SystemRoleAssignment species and occurrence when assignment is claimed, the Method or MethodDescription, the relevant WorkPlan or Work occurrence, and the interface constraints defined by the architecture or module-interface pattern.

Classification, assignment, capability fit, interface satisfaction, authority, responsibility, Method selection, planning, and performed Work remain separate claims. Other connected values, for example artifacts, telemetry, acceptance records, diagrams, selected structures, checks, gates, evidence, and provenance, also keep their direct relations.

A.15:12f - Lowering, Repair, and Refresh Conditions

Lower an A.15 claim when the holder system, local system-role kind, direct assignment species or occurrence, Method, MethodDescription, WorkPlan, readiness relation, dated Work, or capability fit cannot be named at the granularity needed by the next use. A weaker result can be a separation note, missing-source note, A.15.4 repair request, decision request, prospective WorkPlan entry, or A.15.5 readiness-gap note.

Repair the changed relation or its account and recheck every claim that depends on that change. A corrected assignment or SystemRoleAssignmentStateRelation does not by itself rewrite the Method or historical Work; a changed WorkPlan does not rewrite performed Work. Corrected evidence may change what is justified about an assignment or Work without changing the past occurrence. Preserve independently supported claims and unchanged dependencies.

Refresh before reliance when the local system-role kind or its criterion changes, the assignment species or predicate changes, another assignment occurrence is needed, the Method family or WorkPlan changes, the execution window changes, or a result, evidence, assurance, gate, reliance, or mathematical-lens relation is no longer current. A taxonomy, scheme, KindSignature, or selected model-use structure triggers refresh only when the receiving claim depends on the changed semantic basis. If the remaining question is no longer system-role–Method–Work alignment, use its direct pattern and keep only the A.15 separation still needed.

A.15:End

A.15.1 - U.Work: Dated Performed Work Occurrence

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

At a glance. Identify a dated action, its performer Systems, the Methods they followed and the interval of performance. Apply the full §4.1 test to admit that occurrence as U.Work. Its results, resource use and other relations need their own grounds. Plans and logs are epistemes describing intended and reported work.

Use this when. Use this pattern to identify a dated performed occurrence and establish its admission basis. It also resolves cases where a representation—for example, a plan, log or result statement—has been mistaken for the occurrence or leaves that basis unclear. Use F.6 separately after admission when a precise claim about the assignment under which Work was performed is current.

Primary reader. Engineers, operators, process owners, modelers, auditors, and FPF authors who need to establish what happened as performed Work and which claims the available evidence supports.

First useful object and short-account rule. Name the candidate dated action and keep the evidence needed by §4.1 recoverable. A Work-only account may stop after admission. Add another enactment, containment, attribution or neighboring claim only when the receiving use needs it; §4.6 routes result, change, production, delivery and judgment claims.

Use the following route:

  1. Recover the direct subject first. If the question is only about a Method, plan, capability, result, change, resource, evidence item, or publication, use that subject’s pattern and stop.
  2. Identify the candidate performer as a System under A.1 without using the candidate Work to prove systemhood.
  3. For every precise Agent claim, recover the A.13 core in §4.0 under independently stated criteria. Observed behavior may supply evidence; assuming that the candidate is already Work may not supply the proof. Open the characteristic-profile branch only under its stated receiving-use condition.
  4. Apply the full §4.1 test, including the occurrence’s A.1:4.2 construction and its Work-specific factual premises. Follow its candidate-facts-to-claims explanation to admit W : U.Work and then assert its obtaining typed relations.
  5. Only after admission, and only when precise assignment-bound attribution is current, use F.6 with the same obtaining A.13 assignment for each performer.
  6. Add direct Work-to-referent, operation-binding, resource-use, result, change, production, delivery, evaluation, or acceptance claims only when their own predicates and case facts obtain.

Compact positive example. On 27 July 2026, Robot-7 performed the 09:00–09:20 inspection in InspectionService-A, following TurbineInspectionMethod under InspectionAssignment-17.

Basis of this example. Before inspection, Robot-7 is independently admitted as a System. InspectionControllerSystemRole has a declared A.2 membership criterion for goal-directed, condition-sensitive regulation of the inspection action; evidence shows that Robot-7 satisfies it. InspectionAssignment-17 is an obtaining direct assignment of that kind for the service scope, working situation, and window. The same candidate inspection occurrence satisfies the six common constructive components in A.1:4.2. Together with the established construction and performer bases, the 09:00–09:20 inspection history on 2026-07-27, TurbineInspectionMethod, and the declared containment within InspectionService-A satisfy the A.15.1 occurrence test, so first admit InspectionWork-17 : U.Work.

Then separately use the direct case fact for the pair to establish F.6 performedUnderAssignment(InspectionWork-17, InspectionAssignment-17) and say: Robot-7 performed InspectionWork-17 under InspectionAssignment-17.

A separate assurance use can evaluate obstacle response, policy choice, persistence or operational closure under its declared criteria. Cite A.13 characteristic-profile values only when that use consumes those characteristics; the core Work claim needs no profile here.

Nearest non-use example. A dashboard says inspection complete but exposes only a schedule row and a copied log. Keep the schedule as WorkPlan content and the log as possible evidence. Inspect the log for the facts it supports; leave Work admission unresolved until the A.13 performer basis and all occurrence premises can be recovered.

Recognition check. Can the team recover the full §4.1 basis for one dated occurrence? When precise assignment-bound attribution is needed, can it also establish the separate F.6 relation under the conditions stated there?

Stop condition. Stop the admission branch once the candidate is admitted under §4.1 as one U.Work at the needed granularity, or the account has been limited to the independently supported neighboring claim. Keep an unresolved admission distinct from a failed proposed admission basis. If precise assignment-bound attribution is current, resolve that separate F.6 claim; missing or rejected attribution alone leaves established Work intact. Recheck an admission premise only when the same finding questions it under §4.1. A missing optional profile blocks only the Grade, autonomy, profile, criterion-dependent or assurance claim that requires it.

What changes in practice. A team establishes one occurrence and its actual performer basis from the available evidence, then adds only the result, change, resource, or evidence relations that the current decision consumes.

What this buys. An inspectable identity for one dated Work occurrence, with its admission basis recoverable and its attribution and neighboring claims judged separately when needed.

Not this pattern when. Use the direct pattern when the current question concerns agency (A.13), a Method (A.3.1), MethodDescription (A.3.2), plan or schedule (A.15.2), readiness (A.15.5), appearance-based reliance (A.15.4), evidence or assurance (A.10 or B.3), publication-use behavior (E.17, with E.24.PUB for publication identity), or a declarative representation (C.2.P.DR).

A.15.1:1 - Problem Frame

After we have separated which system-role assignment obtains (via U.SystemRoleAssignment), what capability is being relied on (through an A.2.2 qualified holder-ability claim), how in principle the Work is done (the U.Method), and which claim-bearing episteme, if selected, describes that Method (U.MethodDescription), we still need a concept for what happened as performed Work in real time and space.

Every Work individual has an A.13 core basis for every claimed actual performer System, an independently grounded performance history, at least one enacted Method, temporal extent, and at least one locally declared containing-system relation. Several such relations may obtain under different system boundaries. The A.13 core already contains one obtaining assignment for its scope, situation, and window; an F.6 relation may later use that same occurrence but is not a Work-membership premise. A Work stands in a direct work-to-referent, binding, or resource-use relation only when that relation obtains world-side; none is a field stored in the occurrence. A separate assertion or description episteme designates that individual and states the independently obtaining relations. Judge its evidence against the occurrence or relation claim being made.

A.15.1:2 - Problem (what breaks without a notion of Work)

  1. Plan and occurrence confusion. Schedules and diagrams get mistaken for performed work, so audits and KPIs attach to plans or representations instead of dated occurrences.
  2. Method-description and work conflation. A method description, code artifact, or SOP is reported as if it were performed work; conversely, logs are treated as recipes.
  3. Who and when leakage. People and calendars are baked into method descriptions; reuse and staffing agility collapse.
  4. Resource misattribution. Performed energy, material, time or cost use is booked to a Method or assignment as though it occurred there. State the actual resource-use relation involving the dated Work; keep estimates and derived Method-level statistics separate under their accounting rules.
  5. Mereology muddle. Teams hand-wave over work parts, retries, overlaps, or long-running episodes; roll-ups double-count or miss work.

A.15.1:3 - Forces (what the definition must balance)

ForceTension we resolve
Universality vs. domain detailOne Work notion for surgery, welding, ETL, proofs, lab cycles—while letting each keep its vocabulary.
Granularity vs. aggregationSelected-grain occurrences vs. composite Work; we need roll-up without presuming partlessness or letting Work parthood create another object’s composition.
Concurrency vs. orderParallel or overlapped activities need clear part and overlap semantics.
Identity vs. retriesA failed attempt, a retry, and a resumed episode—what is “the same” work?
Time realism vs. simplicityWe need intervals and coverage but cannot bury users in temporal logic notation.

A.15.1:4 - Solution — admit dated Work occurrences under U.Work

A.15.1:4.0 - Recover the A.13 agency basis before claiming an Agent performer

This pattern does not define another kind of Agent and does not infer agency from Work. In precise FPF prose, Agent is shorthand for the A.13 core result about one admitted U.System, one local agential system-role kind and its membership criterion, classification of that System under the kind, one obtaining assignment of that kind, and the claim scope, working situation, and time window needed by the use. Evidence must support each asserted core fact. An agency-characteristic profile is a separate conditional result, not a universal member of that core.

Before concluding that a candidate occurrence is Work:

  1. admit the candidate performer S as U.System under A.1 without using the candidate Work, assignment, capability, or actor-like name to establish systemhood;
  2. state the proposed action, relevant objective or norm, conditions, System boundary, scope, working situation, and window without calling the occurrence Work;
  3. recover a local agential system-role kind K under A.2 whose independently stated membership criterion names the stable work-facing contribution and the minimum goal-directed, condition-sensitive regulation required at this grain;
  4. establish with appropriate evidence that S satisfies that criterion and is classified under K;
  5. recover one direct A.2.1 assignment species that assigns K and one obtaining occurrence RA whose holder is S, assigned-kind value is K, predicate and participants pass, and extent covers the scope, situation, and window; and
  6. open A.13’s agency-characteristic profile only when the receiving claim asserts a Grade, autonomy, or profile value, the local membership criterion explicitly consumes one of its characteristics, or a named assurance use requires it. Then cite only the characteristic values, evidence, and qualification limits that use consumes. Otherwise the core basis stops at item 5 plus the evidence needed to establish items 1–5.

The local membership criterion is the positive discriminator. It may require selection or regulation among admissible continuations, or maintaining or returning to a declared target under relevant perturbation. Initiating, continuing, redirecting, regulating, pausing, and stopping are possible evidence, not a universal checklist. A closed loop can pass a narrow Grade-free regulation role and fail a broader inspection, diagnosis, or project-decision role. A separately asserted Grade still requires the auditable profile specified by A.13.

Only then test the candidate action, Method followed, time, containment facts under the declared local rule and other needed facts under §4.1. On pass, admit W : U.Work without assuming an F.6 conclusion. F.6 may then attribute W through the same obtaining RA. Underlying observations of the action can support the independently defined A.13 criterion; the assumption that it is already Work cannot establish agency or assignment. Test assignment under its own species rule, and do not use F.6 to establish Work membership. A profile substitutes for none of these tests.

Do not infer agency from systemhood, acting eligibility, an actor-like product name, assignment alone, capability, causal power, physical change, participation, containment, being the project system-of-interest, or one irrelevant feedback loop. If the local kind or its criterion, classification, obtaining assignment, required scope, situation, or window fit is missing, lower the sentence to functioning, behaviour, interaction, causal participation, transformation, or an unresolved performer claim as the available evidence warrants. If only a conditionally required profile or assurance basis is missing, retain any independently grounded core agency and Work claims and lower only that stronger profile, Grade, autonomy, or assurance claim.

A.15.1:4.1 - Definition and occurrence identity

U.Work is the admitted U-kind for dated 4D occurrence holons. One Work individual is one independently identified performed occurrence with its own temporal extent. Admit a candidate when its construction satisfies the six common components in A.1:4.2; the performance history is grounded; every claimed actual performer is an admitted U.System with a current A.13 core basis under section 4.0 for the exact action, scope, working situation, and window; the action actually follows at least one exact Method; its extent is known; and the complete occurrence lies inside an exact System boundary under the delimitation and qualification conditions declared for at least one local Work-to-System relation.

On admission, state the obtaining enactsMethod and containing-System relations. A.15.1 neither assumes nor requires F.6 performedUnderAssignment to establish W : U.Work.

From candidate facts to typed claims. A.1:4.1 permits reference to the independently identified occurrence as a U.Entity while its Work membership is unsettled. Use A.1:4.2 for the six common constructive components of that same occurrence. In addition to identifying the candidate, recover its constituents, constructive part relations and assembly, reidentification rule, composition-grounded whole-level characteristic, and possible participation in a larger constructive assembly, under that pattern’s conditions.

Recover the facts required by each constructive part predicate and assembly rule. Make a resulting Work-typed part assertion after the participating Work individuals have been admitted. Where those facts cannot be established independently of the proposed Work classification, leave the common premise unresolved. Reuse an established common-criterion result when its candidate and grounds are unchanged. Combine these construction premises with the Work-specific factual premises in §§4.0–4.1.

Establish the exact Method and containing System under their own patterns. Check the candidate’s performed history against the Method at the extent claimed for enactment. For containment, recover the local relation’s participant meanings, applicability and obtaining condition, then check its factual conditions on the complete candidate occurrence, including the declared System delimitation and qualification window. The Work participant’s kind is established by the admission judgement that follows.

When all required admission premises are grounded, admit that same occurrence as W : U.Work. For each typed assertion, combine that membership with the other participant’s independently admitted kind and the previously checked facts required by its predicate. These grounds support enactsMethod(W, M) and the declared containing-System relation. Keep each claim tied to the occurrence, participants, extent and qualifications whose facts were checked.

If a required fact is unresolved, retain the supported claims and leave the dependent Work-admission conclusion unresolved. If the facts establish that a required condition fails, that proposed admission basis fails. A missing containment rule returns missing-governor[work-containment]; missing evidence for an available rule instead leaves its factual test unresolved. Facts satisfying another declared containment rule may supply the containment premise. A.6.REL governs the resulting relation assertions and any later need to distinguish their occurrences.

Worked admission case. In a constructed variation of the entry’s Robot-7 example, retain the same occurrence’s established A.1:4.2 construction, performer basis, inspection history, TurbineInspectionMethod and 09:00–09:20 extent. Let Cell-3 be an independently admitted System. The local predicate workOccursWithinCellBoundary(work, system) requires the complete performed occurrence to lie inside that System’s declared physical boundary throughout the relevant window. The checked inspection history places all performed content inside Cell-3’s boundary during 09:00–09:20. Together with the other admission premises, this supports InspectionWork-17 : U.Work; the same history and participant identities support enactsMethod(InspectionWork-17, TurbineInspectionMethod) and workOccursWithinCellBoundary(InspectionWork-17, Cell-3). If the 09:10–09:15 location history is missing, this containment basis remains unresolved. If it shows inspection outside Cell-3, this particular containment claim fails; facts satisfying the containment rule for another independently admitted System may still supply the required premise. In either variation, retain the inspection facts already established and return to the missing or failed premise.

Use records for the claims they support. Identify the candidate action and the claim supported by each source, using the A.2.4 evidence-use relation or the A.10 evidence-provenance account required by that use. A trace linked to the Robot-7 inspection can support its 09:00–09:20 interval while other sources establish the performer’s A.13 basis, Method followed and containment. Work admission requires all the §4.0–4.1 premises to be grounded across the sources used. If only the interval is supported, retain that timing claim and leave Work admission unresolved. For an already admitted Work, evidence for a later claim about its interval need not repeat the admission evidence; keep the admission basis recoverable.

Elsewhere in FPF, a complete A.13/A.15.1/F.6 basis is the combined post-admission basis used only when a receiving claim needs both admitted Work and precise assignment-bound performer attribution. Its order is fixed: section 4.0 supplies the A.13 core and evidence for every performer; A.15.1 independently admits one dated Work occurrence with at least one obtaining enactsMethod relation, its temporal extent, and at least one obtaining locally declared Work-to-System relation whose stated boundary contains the complete occurrence; only then does F.6 test the link through the same covering A.13 assignment occurrence for every precisely attributed performer. This combined basis is not the A.15.1 admission test. A missing F.6 link alone leaves W : U.Work intact and the exact assignment-bound attribution unresolved. Add an A.13 characteristic profile only when the receiving claim consumes a Grade, autonomy or profile result, a criterion-dependent characteristic, or an assurance result. A failed F.6 test alone leaves independent Work admission intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions. Preserve independently grounded history and relations; an unresolved attribution is neither proof of no performance nor proof of success.

The canonical F.6 relation performedUnderAssignment(W, RA) is checked only after W is admitted and attributes that Work occurrence to one assignment occurrence. For an obtaining attribution, its attribution-facing holder projection is S = attributedPerformerSystem(W, RA) = RA.HolderSystemSlot; this projection does not discover S, and the direct case fact must establish that the System already recovered through A.13 performed W under RA. The assignment must also cover the attributed extent. In practitioner prose name both objects: S performed W under RA. If the relation is unresolved, retain independently grounded Work and do not assert that sentence; apply the preceding premise-recheck rule if needed. The legacy spelling performedBy(W, RA) is a deprecated compatibility alias only; do not author new claims with it, and never say that RA performed W. One or more enactsMethod relations connect the Work individual to the U.Method values actually enacted. At least one locally declared Work-to-System relation locates the complete occurrence under an exact containing-system boundary; several may obtain under different valid boundaries. Direct work-to-referent, binding, and performed resource-use relations are recovered independently only when they obtain and the current claim needs them. An occurrence designator permits reference but does not identify work by label, ticket, trace, record, or storage convention; an assertion or description about the occurrence is a separate U.Episteme.

The actual enactsMethod relation obtains between the Work occurrence and the exact U.Method; it is not a field of either participant. An exact U.MethodDescription may be cited when its claims identify, constrain, or justify that method for the receiving use; the description is not enacted and its fields do not become actual work bindings. A selected model-use structure likewise enters only through the exact receiving relation whose interpretation it changes.

Call a selected MethodDescription, continuity policy or criterion a later edition only when the C.2.1 EpistemeEditionRelation to the earlier episteme is established. Otherwise identify the separate episteme and leave that continuity claim open. A replacement use and a negative continuity claim each need their own basis; missing evidence for an edition establishes neither.

A.15.1:4.1a - Direct Work relations used by this pattern

These relations are world-side facts, not fields stored in Work. Before asserting an A.15.1-owned relation below, independently admit both participants under the stated kinds. For a Work participant, use the candidate-facts-to-claims route in §4.1. The exact relation kind plus the ordered participant pair identifies the relation occurrence for ordinary use; if a later claim must distinguish its history or compare two occurrences, use A.6.REL. A changed participant pair identifies another occurrence. State a relation only when its predicate passes.

Relation and participant orderWhen it obtains and where it appliesIdentity, multiplicity, and boundary
enactsMethod(work, method) with <U.Work, U.Method>The performed occurrence actually follows that exact way of doing over the stated Work extent or an explicitly named performed part. A plan, MethodDescription, label, or intended use does not establish it.Identity is this relation kind plus the ordered Work–Method pair. Every Work enacts at least one Method. Several may obtain when each Method is actually enacted and its covered extent or performed part is stated.
TemporalPartOf_work(part, whole) with <U.Work, U.Work>The first Work is a proper temporal sub-occurrence of the second: its exact extent is strictly inside the whole’s extent and all of its performed content belongs to that same occurrence history. It applies only when the slice is itself useful as an independently admitted Work individual.Identity is this relation kind plus the ordered part–whole pair. A part may belong to several larger Work occurrences when the predicate passes for each; no unique parent is assumed. An interval, telemetry segment, or record is not thereby a Work part.
EpisodeOf_work(episode, whole) with <U.Work, U.Work>The first Work is an independently admitted event-bounded sub-occurrence of the second. Actual start and end events and the performed content must establish both the episode boundary and its inclusion in the whole. A named use selects which already grounded episode matters.Identity is this relation kind plus the ordered episode–whole pair. Several episodes and several larger wholes are allowed when each predicate passes. If boundary facts permit more than one grouping, apply the cited continuity-policy episteme’s criterion to those facts to support the assertion. The relation participants remain the episode and whole Work.
OperationalPartOf_work(part, whole) with <U.Work, U.Work>The first Work is an independently admitted performed sub-occurrence whose performed content is a constitutive part of the whole occurrence at the stated operational grain. Mere overlap, a Method factor, schedule row, interval, or result label does not establish it.Identity is this relation kind plus the ordered part–whole pair. Several parts and several containing Work occurrences are allowed when each predicate passes. State any Method-factor relation separately.

To recover these connections in practice, B.1.5.EW starts with an action and asks what encompassing work is under way through it. Adding a value can be part of computing a total while report preparation is ongoing. This does not make the report complete, create a separate occurrence for every description, or count the same resource use several times. Independently claimed Work parts still satisfy the predicates above.

Containing Systems. Current assertions do not use bare executedWithin. Declare a direct local predicate such as workOccursWithinPlantBoundary(work, system) with participant order <U.Work, U.System>. Its predicate must say which exact system delimitation and qualification window make the complete Work occurrence lie within that System for the stated use, and must route that delimitation to A.1, A.14, or the applicable domain pattern. Its ordinary occurrence identity is the exact local relation kind plus the ordered Work–System pair. The §4.1 admission test first establishes the required containment facts; the admitted Work account states at least one such obtaining relation.

The same Work may stand in several true containing-System relations at different valid boundaries; no universal uniqueness or automatic “immediate” System is assumed. A part relation between Systems, organizational accountability, colocation, or a diagram does not by itself establish another Work-containment relation.

If no applicable local containment predicate is declared, return missing-governor[work-containment]. With a declared predicate, use §4.1 to distinguish missing factual support from a failed condition and to test another available containment basis. Historical executedWithin is only a route cue to recover this local relation; do not author a new current claim with it.

Retries and resumptions. Bare retryOf and resumptionOf are likewise route cues, not complete universal relation names. A domain that needs either relation declares a local two-participant species over <U.Work, U.Work>. A retry predicate states which earlier Work ended without satisfying which independently named completion condition, which target remains current, and which facts make the later Work another attempt rather than mere repetition. A resumption predicate states the earlier unfinished Work, the interruption boundary, and the direct continuity facts that make the later Work continue it rather than start another attempt. For either species, the exact local relation kind plus its ordered later–earlier pair identifies the ordinary occurrence; the declaration states applicability and whether more than one predecessor is allowed. A repeated label, shared Method, or temporal adjacency establishes neither relation. A continuity-policy episteme may support an ambiguous judgment but is not a participant and cannot replace the local predicate.

When a Work use needs overlap, precedence, containment, or another interval relation, use C.27.TA to name the temporal bearer, reference, intervals, direct temporal predicate, and the use that needs it; use B.1.4 only when those already recovered relations are aggregated. These declarations also do not replace F.6 performedUnderAssignment or a domain-specific Work-to-referent predicate. A consumer names the relation and participants rather than citing “the Work record.”

If the receiving sentence says that a referent changed, identify one exact U.Transformation independently under A.3.4. If a declared domain predicate relates exact Work W and transformation T, name that predicate, its participant order, and the facts that make it obtain. If no one direct predicate suffices but a one-case compound claim does, use A.6.RCD disposition 2 only when the substrate-admitted constructor, governed base predicates, actual participants, and case facts are recoverable; the result is C.2.1 claim content, not a relation kind or occurrence. Otherwise retain W and T separately and return missing-governor[work-to-change], or A.6.RCD’s missing-substrate result when the proposed constructor itself has no current semantics. Shared time, referent, or wording does not establish that Work-to-change claim. A morphism, delta expression, state-plane trace, pre-state, or post-state may represent or support the neighboring change claim; none is a Work field or identity discriminator.

Memory aid: Work = “how it went this time” (dated, resourced, attributable).

A.15.1:4.2 - Core occurrence references and neighboring links

When current Work also uses live steering. One current Work occurrence may enact both its domain Method and the A.15.7 steering Method, but only if each enactsMethod relation is independently grounded. Merely consulting the pattern or a MethodDescription, or admitting the steering Method as a submethod of a composite Method, proves neither enactment. The next-action answer says what should happen next. Treat choosing as a smaller Work occurrence only when its own A.15.1 basis and its relation to the larger Work are both needed and grounded.

When a separate assertion or description episteme describes one Work occurrence, recover the following content at the granularity required by the current use. Each item names an occurrence designator, a world-side relation or temporal fact, or a reference to another episteme; the list is not a slot or field schema for the Work individual:

  1. Occurrence and extent — one occurrence designator plus exact start and end, or an explicitly open end for in-flight work; add location only when the work claim depends on it.
  2. Performer System and agency basis — for admission, name every actual performer U.System and its A.13 core, including the obtaining assignment for the action, scope, situation, and window. After Work admission, use F.6 only when the receiving claim needs the exact assignment under which that System performed the Work; keep the declared species, holder, other participants, and coverage recoverable.
  3. Enacted method — actual enactsMethod -> U.Method. Cite methodDescriptionRef -> U.MethodDescription only when the receiving claim depends on that exact description episteme; the description is not enacted.
  4. Containing Systems — name at least one locally declared Work-to-System predicate, its actual Work and U.System participants, and the exact system boundary and qualification window that make it obtain. Name several when different valid boundaries matter to the receiving use. A System’s part relation to a larger holon does not by itself establish another Work-containment relation.
  5. Work-to-referent relation used by the claim — name the declared domain predicate, its participant order, and the actual Work and referent participants only when that predicate obtains and the receiving claim uses it. “Work on X”, shared timing, a record mention, or a convenient affected field establishes no such relation. If the use needs the relation but no predicate governs it, keep the Work and referent and return missing-governor[work-to-referent]. An obtaining work-to-referent fact does not by itself assert change, production, delivery, or acceptance.
  6. Actual participation and bindings — for an operation argument or result, name one identified A.6.1 application and its exact declaration-local binding. For another participant, parameter, supplied constituent, premise, or reference use, name the declared subject predicate, participant order, and actual values. If the required route is absent, name the missing relation or binding in the missing-governor result rather than asserting it. A MethodDescription field, plan row, type-compatible value, or log token establishes none of them.
  7. Performed resource use — name the declared resource-use predicate and its actual Work, resource, amount, unit, and extent participants at the boundary needed by costing or sustainability use. If no predicate governs the needed use, return missing-governor[resource-use]; do not infer use from colocation, timing, or a plan estimate.
  8. Continuity policy for an unresolved segmentation — when a named identity, episode, retry, resumption, or aggregation use has more than one defensible segmentation, cite workContinuityPolicyRef to the exact C.2.1 episteme whose claims state the branch criterion and tolerances for that use, and interpret those claims under its effective reference scheme. If the criterion or its applicability cannot be recovered, leave that segmentation unresolved. The episteme is a U.MethodDescription only if it independently satisfies A.3.2’s method-description criterion. A simple uninterrupted occurrence needs no continuity-policy reference; use the policy to judge the ambiguous segmentation against the performance history.
  9. Work mereology and temporal relations — exact parent, part, predecessor, successor, overlap, retry, or resumption relations only when their predicates obtain.
  10. Actual change and production claims — identify each actual transformation independently under A.3.4; connect it to Work only through a declared domain predicate with its exact Work and transformation participants or a filled A.6.RCD disposition-2 claim with recoverable constructor, base predicates, participants, and case facts. Otherwise return missing-governor[work-to-change]. Keep the current A.15.PROD production-work, entity-identity-inception, and production-completion claims separate. None follows from work identity or parthood.
  11. Evaluation and downstream claims — use the one matching §4.6 row for evaluation work and result, evidence use, delivery or transfer, and acceptance; omit every row that is not current.
  12. Evidence, publication, and model use — cite only the exact evidence-use, publication-use, currentness, claim-scope, reference-plane, bridge, or selected model-use relation needed by the receiving claim.

Capability for a required contribution. When a capability condition matters to a Work claim or receiving decision, recover the contribution it requires and the holder to which it applies. Under A.2.2, compare that holder’s qualified ability with the Method-side demand for the work interval or declared checkpoints; reuse an adequate current fit. A collective ability claim concerns the independently identified System in its stated configuration. Conditions on individual contributions apply to the corresponding performers. A condition imposed on every performer still requires every performer to satisfy it. When performance depends on help or coordination, retain those conditions and the evidence for the combined contribution.

Report the fit, mismatch or named unresolved premise; stop when that answer suffices for the receiving decision. If a selected continuation still requires a positive fit, obtain the missing basis or arrange a permitted way to supply the required contribution, as the unresolved premise or failed test warrants; recheck the affected fit after any selected action. Before entry, use A.15.5’s actual readiness criterion, including any allowed gap. During Work, use A.15.7 to choose a supported continuation or stop under the domain Method. When loss or replacement of a performer or support makes the configuration uncertain, A.15.8 identifies and tests the relation to repair. Preserve independently grounded performance history, and recheck any Work-admission premise that the finding also challenges.

Example. The department in A.2.2:6.3 can close books for eight legal entities under IFRS with ERP v12, at least six qualified staff and a duration below five business days. In a constructed variation, reconciliation and consolidation are assigned to different performers, and the Method requires each performer to detect duplicate entries. Compare each performer’s qualified ability with its contribution’s requirement and with the Method’s shared duplicate-detection condition. Losing the sole consolidation specialist leaves that contribution unsupported even if reconciliation is finished. Recover qualified support or revise the continuation under the Method’s limits, and recheck the affected individual and department-level claims.

A.15.1:4.3 - Clear distinctions in a Work claim

You are pointing at…The right FPF conceptLitmus
A claim-bearing episteme expressed through a recipe, code artifact, or diagram and substantively about one admitted methodU.MethodDescriptionDoes the same episteme meet A.3.2’s membership threshold? Otherwise retain the claim-bearing episteme and any representation, publication, or formal-substrate object independently identified by its own pattern; do not call the episteme a MethodDescription.
The semantic “way of doing”U.MethodDoes the referent meet A.3.1’s conditions for a reusable way of doing under stated applicability? When comparing descriptions or notations, test semantic identity under A.3.1:4.7.
The assignment (which admitted System is assigned under which local system-role kind in this case)one obtaining occurrence of one directly declared species under U.SystemRoleAssignmentDoes the direct A.2.1 species’ assignment predicate obtain for its actual participants, including the admitted holder System and an assigned kind from that species’ declared domain? Identify the occurrence under A.2.1:4.3.
The ability (“can do within bounds”)Qualified holder ability (A.2.2)Does the claim state what an independently admitted holder System can do or produce, under which conditions and attained bounds, with the support and currentness required by A.2.2 for this use?
The dated occurrence with logs and resource-use evidenceOne Work individual admitted under U.WorkDoes the occurrence satisfy the full §4.1 test, including its A.1:4.2 construction, actual action during the stated extent, every actual performer’s A.13 core, at least one Method actually followed, and containment under at least one declared local rule? If precise assignment-bound attribution is also claimed, does a separate F.6 relation obtain for the already admitted Work? Are any claimed binding, work-to-referent, or resource-use facts independently obtaining?
The actual state change associated with this occurrenceU.Transformation plus a named domain predicate, or a C.2.1 local compound claim under A.6.RCD disposition 2Is the change independently grounded under A.3.4? Does the direct predicate obtain for exact W and T, or does the local claim expose its constructor, governed bases, participants, and case facts? If neither route is present, retain both objects and return missing-governor[work-to-change].

A.15.1:4.4 - Publication-use boundary for U.Work

A publication about one Work occurrence projects claims from an already declared assertion or description episteme. Preserve the source’s evidence basis and qualifications for the claims used from the publication. A completion-looking dashboard requires the same occurrence evidence as any other claim that the work happened.

Preparation is classifiable as one Work individual under U.Work only after it actually occurs and, under the full §4.1 test, its A.1:4.2 construction, its performer’s A.13 basis, at least one enacted Method, temporal extent, and at least one obtaining locally declared Work-to-System containment relation are independently grounded. After that admission, establish the covering assignment’s F.6 attribution separately only when the receiving preparation claim needs precise assignment-bound performer attribution. Add a Work-to-referent, binding, or resource-use fact only through its own obtaining relation when the receiving claim needs it. WorkEntryReadiness@Context under A.15.5 asks whether intended Work is ready to enter a Work boundary; a readiness label, full-kit checklist, or launch-looking cue is not a performed occurrence.

Publication-use pressureWork-local rule
PlainView, TechCard, InteropCard, or AssuranceLane presents work materialProject the claims and work-occurrence references used by that view. For an occurrence presented as admitted Work, keep its full §4.1 admission basis recoverable: its A.1:4.2 construction, independently grounded performance history, temporal extent, every actual performer System and its A.13 basis, enacted Method, and at least one obtaining local containing-system relation. Keep the assignment and F.6 attribution recoverable when the receiving claim uses their identity, and any separately established binding, resource-use, or Work-to-referent relation on which the view relies. Following E.17, provide an accessible source return or carry the source-attributed content needed for use without that access. A narrower view may expose only its selected claim and supporting references. Project a neighboring result, change, production, delivery, evidence, or judgment through its matching §4.6 row.
a numerical observation, comparison, aggregation, or benchmark result is publishedState what the value describes and retain the source basis needed to interpret it. Use C.16 for measurement, A.19.CPM and its CG-Spec for comparison, and B.1.4 or B.1.6 for temporal or resource aggregation. Preserve the selected operation’s rule, material editions and any required conversion or reference-plane relation. Make any scalarization explicit.
publication cites method-description, work-plan, or cross-context materialKeep the Work occurrence as the dated performed individual admitted under U.Work. Cite the exact selected method-description or work-plan episteme. For a semantic crossing, cite an obtaining F.9 Bridge between two exact SchemeSenseCell values and state the proposed action, direction, correspondence rule, and tolerated loss in a separate bounded-use claim. Cite a UTS, reference-plane, or edition relation only when its own predicate obtains.
reconstructed records look like a performed occurrenceDistinguish what the records establish from what remains unresolved. Cite an occurrence as admitted Work only when its complete occurrence basis is grounded; a reconstruction that supports only a narrower claim remains usable for that claim.

Publication example. A report of 12 kWh consumed by one stated Work occurrence keeps its C.16 measurement basis recoverable. Reporting a total for two occurrences adds the B.1.6 inclusion and shared-use policy. Saying that one run consumed less than another adds the A.19.CPM comparison basis. Each publication carries the source content needed to interpret its own claim, through E.17’s accessible source return or source-attributed content.

A.15.1:4.5 - Crossing visibility for work publications

When a work publication relies on another selected method-description episteme, name that episteme and the relation the publication actually uses; do not infer an edition from a version label or later date. For a semantic crossing, name the two F.17 sense cells and test the F.9 Bridge predicate profile, then state the proposed action, direction, rule, and tolerated loss in a separate C.2.1 bounded-use claim. For a reference-scheme, claim-scope, model-use, reference-plane, unit, or publication change, cite the direct relation that the publication actually uses. State ordinary evidence reliance through the applicable A.10 account of independently established evidence-use relations, including the same-use RelianceDisposition required by F.9:4.2 for reliance on an affirmative Bridge-use claim. Add a B.3 assurance result only when an actual named assurance claim is current.

When a Work assessment applies a penalty, cite the applicable rule, the conditions under which it applies, and the assessment value it changes. For a calculated adjustment, retain the value’s bearer, characteristic, scale and applicable unit, the required calibration or calculation, and the resulting value. Use B.3:4.3–4.4 when an assurance argument consumes that calculation. If its required rule or calibration is unavailable, report the available inputs and leave the adjustment unresolved. These assessments concern the same independently admitted Work occurrence.

A claim that a planned, gate-selected, or launch-labelled value was actually used requires a named direct predicate with its actual participants to obtain, or an exact A.6.1 operation-application binding to connect one identified application to that value. If the required predicate or binding rule is undefined, keep the planned designation and return missing-governor[actual-use]. If the rule exists but its positive test fails or lacks a deciding fact, keep the planned designation and return factually unsupported or missing-information, respectively. Do not back-fill a plan or infer an actual binding from shared wording. Pre-state and post-state references remain with an independently governed transformation or comparison claim; bracketing the Work interval does not bind them to the occurrence.

A.15.1:4.6 - Route a result or consequence without folding it into Work

Start with the ordinary sentence the reader needs, then select exactly one row for each separate claim. The table is not a result record to fill.

Reader’s sentenceWhat to identifyStop / non-inference
This work happened.A.15.1: W : U.Work, every actual performer’s A.13 basis, independently grounded performance history, enacted Method, extent, and at least one locally declared containing-system relation with its boundarythe presence or form of a log, plan, output or verdict does not establish W; inspect its evidence content. F.6 alone is not the admission basis
S performed W under RA.F.6 after Work admission: the same obtaining A.13 assignment, declared species and participants, direct case fact for the exact pair, holder equality, and interval coveragea covering assignment or admitted Work alone does not establish performedUnderAssignment
The application returned X or X is a result of W.for an application return, the exact A.6.1 application and result binding; for a Work-to-result claim, its already declared domain predicate, exact W and X participants, and obtaining facts. If the required Work-to-result predicate is absent, retain any independently established application binding and return missing-governor[work-to-result]. Use A.6.P.WMR when the source wording hides which route is intendeda result binding is not production, delivery, acceptance, or a universal work-result relation
This referent changed through W.A.3.4: one exact U.Transformation; then name the declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with its substrate-admitted constructor, governed base predicates, actual participants, and case facts. Without either, return missing-governor[work-to-change] and keep W and T separately usabletemporal overlap, a delta picture, or common referent does not connect the change to W
W produced X, X first existed through changes attributed to W, or production completed.the one current A.15.PROD branch: production-work participation, entity-identity inception, or production completion, each with its own criterion and boundaryone branch establishes neither of the other two nor delivery or acceptance
Evaluation found V.identify the evaluation application and result binding or direct evaluation-result relation. Admit a separate evaluation U.Work only when that dated occurrence is claimed; identify a C.2.1 evaluation-result episteme when the result content needs its own referencea performed evaluation, returned value and result episteme remain different objects; a value claim alone requires no additional Work identity
These observations support the claim.A.10 account of the independently established evidence-provenance relations supporting the named claim, or A.2.4 for the lighter episteme evidence-use relationidentify the claim supported and the bounded use; a Work-admission conclusion requires the complete §4.0–4.1 basis across the sources used
X was delivered or transferred.name the declared delivery or transfer predicate, its exact source, destination, transferred X, and any required occurrence or interval participants. Use A.2.3 for a separately current promise-content claim; if no delivery or transfer predicate governs the claimed transfer, return missing-governor[delivery-or-transfer]production, a package, or a handoff label does not establish transfer
X was accepted.Apply the declared acceptance predicate to X, its actual participants and the facts its conditions require. Identify a decision, verdict or dated evaluation or acceptance Work when the rule or claim requires it. Use A.2.3 for a promise-content claim. If no predicate governs the asserted acceptance, return missing-governor[acceptance].Delivery or a passing value settles acceptance when the rule gives it that effect and its other conditions hold. For a conclusion about several undertakings together, use A.6.C:4.1.

Three-question result check. (1) Did the Work occur? Recover its §4.0–4.1 admission basis; add F.6 only for the separate assignment-bound claim. (2) What result or consequence is claimed? Identify the returned value, entity, change, production claim or transfer through its §4.6 row. (3) What established the judgement or acceptance for this result? For a judgement, apply the criterion to the relevant facts and identify the returned value and the evidence for it. For acceptance, identify the rule and the facts that establish whether its conditions were met. Where a decision by a participant was required, establish who made it and for whom. Add a dated evaluation Work identity when that occurrence is at issue. Stop after the last current question.

A.15.1:5 - Work mereology (how occurrences form holarchies)

Work identity is occurrence-grounded and 4D. Start from the actual performance history: work-entry and end events, occupied spatiotemporal extent, actual performer Systems with their A.13 bases, enacted Methods, the locally declared containing-system relations needed by the use, any direct work-to-referent relations, actual bindings, resource use, and work-part or temporal relations. A separately asserted F.6 relation relates the Work to the obtaining assignment under which it was performed; it neither admits nor reidentifies the Work.

A.15.1:5.1 - Parts and wholes of Work (occurrence facts)

  • Temporal-part (TemporalPartOf_work). Both participants are independently admitted Work individuals. The first is a proper temporal sub-occurrence of the second under the §4.1a predicate, with its own exact extent and performed content. Use it when a later resource, evidence, KPI, acceptance, repair, or aggregation claim needs that Work part as an individual. A bare interval, telemetry window, or evidence slice stays a C.27.TA temporal aspect or its direct domain object; it is not the first participant of TemporalPartOf_work.
  • Episode-part (EpisodeOf_work). Both participants are independently admitted Work individuals. The first is an event-bounded performed sub-occurrence of the second under the §4.1a predicate. Entry, resumption, mode switch, switch-to-method, interruption, switch-away, completion, or a declared pause may supply candidate boundary events. Cite an exact workContinuityPolicyRef only when direct facts permit more than one grouping for the named use; timestamps, a policy, or an episode-looking label alone establish no episode relation.

workContinuityPolicyRef designates the C.2.1 episteme stating the named use, boundary events, tolerated variation and branch criterion. Interpret it under its effective reference scheme. Add claim scope, qualification window or model-use structure only when it changes the segmentation assertion. The policy supports classification of the existing history for that use; another policy can support a competing assertion. Apply §4.1’s edition rule: unestablished continuity remains unresolved, rather than becoming a negative continuity claim. A policy is a U.MethodDescription only after A.3.2 admission.

  • Operational-part (OperationalPartOf_work). A work-part occurrence that may enact a factor of a recovered U.Method, for example, an incision occurrence within an appendectomy occurrence, possibly overlapping with others in time. If a method-description reference is used, it identifies, describes, constrains, or evidences that method factor; the referenced U.MethodDescription is not enacted. If no U.Method factor is recovered, retain the object actually identified; do not infer a Method factor from its label.
  • Concurrent work parts (derived use-side reading; no fourth parthood relation). First state each exact work-part relation to the same parent. Then use C.27.TA to state the exact temporal-overlap predicate, reference, intervals, and use. If a claim also says that the parts were coordinated, name its declared coordination predicate and actual participants. Shared parentage and overlap do not by themselves establish coordination, and ConcurrentPartOf_work is not introduced as a primitive work-part relation.

Naming threshold. First identify the actual Work part under its occurrence and relation rules. Give it a stable name when a current or later use needs a distinct reference—for example for resources, evidence, KPI, acceptance, repair or aggregation. Otherwise retain the interval, evidence slice, telemetry or other object actually needed. A proposed new U-kind has its separate admission test.

Didactic rule: Method composition is not proof of Work decomposition, and Work decomposition is not proof of method composition. A temporal work part may enact the same whole method during a slice. An episode may continue one method or mode, span several operational parts, or repeat the same method fragment; an evidence policy may support a finer segmentation claim without changing method identity. An operational part may correspond to a method factor only when that factor is recovered as U.Method.

Quick choice test.

  • Ask “do I need only an interval or aspect, or an independently admitted Work sub-occurrence?” Use C.27.TA or the direct temporal object for the first. Use TemporalPartOf_work only for the second, after its proper-sub-occurrence predicate passes.
  • Ask “does this named use need an event-bounded fragment of the parent?” If yes, recover the candidate boundary events. Cite workContinuityPolicyRef only when interruption, resumption, switch, replacement, or pause leaves the grouping ambiguous for that use; then use EpisodeOf_work only when its direct predicate is satisfied.
  • For two independently admitted Work occurrences, ask “is the performed content of the proposed part a constitutive part of the whole occurrence at the stated operational grain?” Assert OperationalPartOf_work when the §4.1a predicate holds. Use another Work-part relation only when its own predicate holds. When precise assignment-bound attribution is also current, check the separate F.6 relation only after admitting the sub-occurrence.
  • Ask “which way-of-doing part is being composed?” If the answer needs preconditions, effects, interface, and whole-method relation, recover a U.Method submethod under A.3.1 and B.1.5; do not make the work part itself carry the method identity.

A.15.1:5.2 - Key relations among Work

Temporal order and overlap. A.15.1 supplies each Work occurrence and its exact extent. Use C.27.TA to name the temporal bearer, reference, exact intervals, direct temporal predicate, and use that needs it. A differently named predicate is used only when its own declaration gives the same participant meanings and law. Use B.1.4 after those temporal facts are recovered when the task asks for a roll-up.

Retry and resumption. Use only a locally declared retry or resumption species that passes §4.1a. Name that predicate and the actual later–earlier Work pair. Bare retryOf or resumptionOf wording is a prompt to recover the local relation, not a positive claim.

Causal use. If one Work occurrence is claimed to explain, trigger, or cause another, keep the Work-to-Work relation separate from the causal-use claim. Use C.28 or the pattern that defines and tests that causal use.

A.15.1:5.3 - Work-occurrence relations used by Part B roll-ups

A.15.1 supplies the identity of each independently identified Work occurrence or Work part and makes its exact temporal and performed resource-use relations recoverable. It does not itself return a temporal aggregate or resource ledger.

  • Temporal coverage. When a receiving use needs elapsed time, phase coverage or another roll-up over Work intervals, apply B.1.4 to the intervals and the selected combining rule. For resource utilization establish which intervals or amounts correspond to occupancy under the selected resource measure. Preserve the temporal inputs, coverage and overlap conditions consumed by that rule. An adequate ordinary account can state the result; use a separate record or optional Gamma_time notation when the receiving use needs it. The Work intervals remain A.15.1 facts.
  • Resource aggregation. When a receiving use needs a total over performed resource values, apply B.1.6 to the attributed inputs, included subjects, accounting scope, time basis and operative rule. Preserve the value-attribution grounds and any overlap, allocation or deduplication conditions used by that account. An adequate statement or existing ledger can convey the result; a separate record and optional Gamma_work notation are chosen by the receiving use. Each contributing performed resource-use relation obtains separately with its Work occurrence as a participant; an assertion about that relation remains distinct from the relation.

Manager’s tip: cite the B.1.4 or B.1.6 aggregation result and policy beside the KPI. A Work-part list, shared parent, or operator spelling supplies neither the aggregate nor its policy.

A.15.1:5.3a - Before A Timetable Becomes Architecture Evidence

A timetable, workflow row or architecture table can help locate candidate Work and may contain evidence. Its presence or layout alone establishes no Work occurrence, part, overlap or order. Before relying on its content in an architecture decision:

  1. identify each Work occurrence under the full §4.1 test from its A.1:4.2 construction, every actual performer’s A.13 basis, independently grounded performance history, enacted Method, actual interval, and an obtaining relation to a containing System; when precise assignment-bound attribution is current, apply F.6 separately after admission;
  2. if several rows are claimed as parts of one Work whole, identify that whole and every part independently, then state the exact Work-part relation that holds;
  3. if two occurrences are claimed to overlap or follow one another, state their actual intervals and the exact C.27.TA temporal relation; and
  4. state coordination, participation, resource use, result, or acceptance only through its own obtaining relation when the architecture decision needs it.

Two activities with similar names or one planned time window can still be distinct Work, and a schedule row may remain only plan content. If the actual occurrence or required relation is missing, preserve the plan, description, interval, or separately grounded Work that is available and stop the stronger architecture claim.

A.15.1:5.4 - Identity and reidentification of Work

Two descriptions, assertions, records, or traces resolve to the same Work occurrence only when they designate the same actual world-side performance history, not merely the same name, policy label, similar policy content, or later date. First compare the direct facts at the selected grain:

  • the same actual work-entry or start and compatible occupied spatiotemporal extent;
  • the same performance history, with each actual performer System’s A.13 basis, enacted Method, and the locally declared containing-system relations used by the identity claim, plus every obtaining work-to-referent, binding, and resource-use fact used by that claim, placed at the interval where it obtains; any separately asserted F.6 relation remains an attribution fact rather than a Work-identity discriminator;
  • compatible work-part and temporal relations; and
  • no fact that already identifies distinct individuals: a proper part versus its parent, independently grounded concurrent performances, or a later work-entry after the first occurrence’s established completion or termination.

A corrected or later description can refine the assertion about the same actual start, open end, or completed end. A change of performer, assignment, enacted Method, referent, binding, resource use, or obtaining containing-system relation during an otherwise unended performance history is an actual change to state explicitly; that change alone neither splits nor preserves the Work occurrence.

When a named receiving use must decide whether the performance history stays inside one parent, examine the direct facts first. If more than one grouping remains defensible, cite the exact continuity-policy episteme, its effective reference scheme, applicable scope and window, and the branch criterion it applies to those facts. The selected policy can support one identity or segmentation assertion for that use. A later or competing policy episteme may support another assertion; call it a later edition only when the C.2.1 EpistemeEditionRelation is established. Otherwise retain the separately identified policy and any supported replacement-use claim without inferring non-continuity.

A.15.1:5.5 - Interruptions, retries, resumptions, and description changes

  • Established end and later entry: identify a later Work occurrence when the first occurrence has actually completed or terminated and another work-entry occurs. A larger composite Work may contain both only through explicit work-part relations.
  • Retry: identify the later Work occurrence independently. Add a retry relation only through a locally declared species whose exact predicate connects it to the ended attempt and whose participant meanings, identity, cardinality, and applicability are stated; bare retryOf remains only a route cue.
  • Ambiguous interruption or resumption: preserve the actual boundary events and facts. If a named use must decide same-parent versus separate-occurrence grouping, apply its exact workContinuityPolicyRef; without that criterion, return an unresolved segmentation rather than making the policy implicit.
  • Performer, assignment, method, referent, binding, retune, or mode change: state the actual change where it occurs. Split or retain the parent only when the direct facts already decide the boundary or a policy current to the named identity, episode, retry, resumption, or aggregation use supplies the criterion.
  • Method-description episteme change: record the newly selected description episteme separately. That selection neither splits nor preserves Work by itself; only an accompanying actual occurrence change enters the boundary judgment. Call the two descriptions editions only when their exact C.2.1 EpistemeEditionRelation obtains.
  • Rework: identify the later performance independently. Relate it as another occurrence, episode, or operational part only after the applicable direct predicate and any needed boundary policy are satisfied. Keep causal attribution with the governing causal-use pattern.

These rules answer Work-occurrence identity and segmentation. When the current question is instead whether exact performer, support, and continuation-state relations let the admitted occurrence continue or recover under interruption, handoff, or degraded support, use the actual-Work branch of A.15.8. It neither splits nor preserves the Work occurrence; return every identity, retry, or resumption claim here.

Plans, costs, quality statistics, telemetry evidence, and method-reliance claims may depend on whether the selected history is a temporal part, event-bounded episode, operational part, or later occurrence. Name a continuity-policy episteme, effective reference scheme, scope, and qualification window only when direct occurrence facts leave more than one defensible grouping for the current claim. When those facts already establish the needed grouping, use them directly.

A.15.1:5.6 - Work mereology does not compose effects or transformations

A parent Work can have work parts without having one composite effect or composite transformation. Any temporal aggregate uses B.1.4; any performed-resource aggregate uses B.1.6; each names its own concern, policy, evidence, and result. Identify every actual transformation independently under A.3.4. Connect one to Work only through a named domain predicate and exact participants, or a C.2.1 local compound claim under A.6.RCD disposition 2 with its constructor, governed bases, participants, and case facts recoverable; otherwise return missing-governor[work-to-change].

Work parthood, method parthood, temporal inclusion, a common affected referent, a list of changed characteristics, or adjacent plan items establishes neither transformation parthood nor a composite transformation. If a production or effect claim needs transformation composition, name the declared composition predicate, its participants, and the facts that make it obtain. If none is available, retain the Work and independently identified transformations and return missing-governor[transformation-composition]. A.15.PROD may still recover any independent production-work, entity-inception, or completion claim that does not depend on that missing composition.

A.15.1:6 - Archetypal grounding (parallel domains)

The following constructed cases use stipulated project facts and the full §4.1 admission premises, including the six common A.1:4.2 constructive components for every occurrence named as admitted Work. They illustrate Work admission and the separately grounded claims described here; they do not report observed practice. Each is presented as readable content of an assertion or description episteme. Arrow notation abbreviates the stated world-side relations; MethodDescription and policy references identify separate epistemes. The bullet layout declares no fields on Work.

A.15.1:6.0 - Work admission in two change cases

  • Transformation with unresolved Work admission: LunarTideRise-2026-07-27 may be identified under A.3.4 as a Transformation of the exact water body over the stated interval. The supplied account leaves Work admission unresolved: it has not established an actual performer U.System with an A.13 agency basis for the tidal action, a Method that the performer followed, or containment of the complete occurrence under a declared local Work-to-System rule. If Work recognition matters to the receiving use, return to the missing premises under the full §4.1 admission test. Keep any independently supported Transformation claim.
  • Self-directed Work: in this rehabilitation model, Person-7’s right-arm motor-control system stretches the left arm for five minutes. The current model admits MotorControlRightArmSystem-7 : U.System and Person-7 : U.System; A.14 ComponentOf(MotorControlRightArmSystem-7, Person-7) and ComponentOf(LeftArm-7, Person-7) obtain, so the mover and the affected limb are distinct parts of one person. SelfCarePerformerSystemRole is a declared local agential kind for the stated stretch action; the case stipulates its target-relative membership criterion, classification of MotorControlRightArmSystem-7 under it, an obtaining SelfCarePerformerAssignment-7 for the scope and window, and adequate evidence that the System satisfies that local criterion; this case makes no Grade or autonomy-profile claim. MotorControlRightArmSystem-7 then performs LeftArmStretchWork-7 from 2026-07-27T07:30:00+03:00 to 2026-07-27T07:35:00+03:00 under that assignment; F.6 performedUnderAssignment obtains and the Work enacts AssistedLeftArmStretchMethod-E1. Clinic relation specification ClinicRehabRelations@Clinic-E1 declares RehabWorkOccursWithinPersonBoundary@Clinic-E1(work, system) for the stated person delimitation and five-minute window, and the case facts make it obtain for that Work and Person-7. The same specification declares RehabWorkStretchesLimb@Clinic-E1(work, limb, interval), which obtains for that Work, LeftArm-7, and the five-minute interval. Separately, A.6.1 application AssistedStretchApplication-7 binds its declared AffectedLimbArgument to LeftArm-7. The first Work-to-limb fact and the operation binding remain different; neither is a primitive self-relation, and this case-specific decomposition is not a required anatomy for every self-directed action.

These branches test admitted facts, not human resemblance. A non-human or molecular-scale System can perform Work when its A.1 admission, A.13 local kind and criterion, classification, obtaining assignment for the scope, working situation, and window, evidence adequate for those core claims, exact performance history, actual enacted Method, extent, and containment facts under at least one declared local Work-to-System rule combine with the occurrence’s A.1:4.2 construction to satisfy the full §4.1 test; unfamiliar agency is not a reason to reject it. If a receiving use also claims the exact assignment under which that Work was performed, check F.6 separately after admission. Add an A.13 characteristic profile only for a Grade, autonomy or profile claim, a criterion-dependent characteristic, or a named assurance use.

A.15.1:6.1 - Surgical case (overlap and episodes)

OR_Team_A performs an appendectomy from 09:05 to 11:42 on 10 August 2025. Exploration overlaps monitoring, and a power dip interrupts performance for five minutes.

  • Top work occurrence: Appendectomy_Case_2025-08-10T0905_1142.
  • Actual method and containing-system relation: enactsMethod -> Appendectomy@Hospital-2025; SurgicalWorkOccursWithinServiceBoundary@Hospital-8472(Appendectomy_Case_2025-08-10T0905_1142, SurgicalService_A) obtains under the service delimitation declared in SurgicalServiceWorkBoundaryRelations@Hospital-8472.
  • Patient and administered dose: project relation specification MED-ADM-2026, owned by ClinicalAdministrationRelations@Hospital-8472, declares ClinicalWorkAdministersDoseToPatient(dose, patient, clinicalWork, interval). The stipulated administration facts make it obtain for MedicineDose_8472, Patient_8472, Appendectomy_Case_2025-08-10T0905_1142, and the surgery interval. This relation establishes only that administration claim. The case names no admitted predicates for theatre, consumables, or staff-time resource use, so those optional claims return missing-governor[SURGERY-RESOURCE-USE] and do not enter Work identity.
  • methodDescriptionRef: Appendectomy_v5, an episteme whose exact EntityOfConcern is admitted Appendectomy@Hospital-2025 and whose substantive claims describe its operative steps under A.3.2.
  • A.13 Agent basis, performer System, and assignment: SurgicalTeamSystemRole is a declared local agential kind for coordinated operative action; its criterion requires goal-directed, condition-sensitive regulation of the stated surgical action, the case stipulates classification of OR_Team_A : U.System under it and adequate evidence for that local criterion and classification for the surgery scope and window; no Grade or autonomy-profile claim is used. SurgicalTeamAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. OR_Team_A_SurgicalTeamAssignment_2025-08-10 is the obtaining occurrence: its holder is OR_Team_A, its assigned kind is SurgicalTeamSystemRole, and its extent covers the surgery. The stated facts establish F.6 performedUnderAssignment for this Work and that occurrence.
  • Operational parts: Incision (09:15–09:22), Exploration (overlaps with monitoring), Closure (11:10–11:35).
  • Episode: a brief power dip occurs from 10:02 to 10:07. The named surgery-continuity use applies HospitalWorkContinuityPolicy_2025, a C.2.1 policy episteme interpreted under Hospital-Operating-Scheme-2025; the case stipulates that its pause-and-resumption criterion keeps both event-bounded fragments under the same parent Work. The power dip alone would not decide that grouping.
  • B.1.4 temporal roll-up. SurgeryWorkCoverage-8472 takes the union of the selected surgery Work intervals. SurgeryPatientLeadTimeAggregation-8472 takes the span between the declared start and end under PatientLeadTimeHullPolicy-2025. To determine operating-room occupancy, identify when this room was in use or remained reserved under the chosen measure, including during the pause. A utilization fraction also needs its available-time denominator.
  • B.1.6 resource roll-up: no positive aggregate is asserted in this case because the direct theatre-, consumables-, and staff-time resource-use predicates are absent. Preserve the Work and the administration relation and return missing-governor[SURGERY-RESOURCE-USE]; open B.1.6 only after the project declares those predicates and supplies their actual participants and facts.

A.15.1:6.2 - ETL pipeline (parallelism and retries)

ETL_Runtime performs the nightly ETL from 01:00 to 01:47 on 11 August 2025. The two extractions run in parallel; Transform starts when either finishes, and a failed warehouse write is retried with a smaller batch.

  • Top work occurrence: ETL_Nightly_2025-08-11T01:00-01:47.
  • Actual method and containing-system relation: enactsMethod -> Nightly_ETL_Load@DataOps-2025; ETLWorkOccursWithinPlatformBoundary@WarehousePlatform(ETL_Nightly_2025-08-11T01:00-01:47, DataPlatform_Prod) obtains under the platform delimitation declared in ETLWorkBoundaryRelations@WarehousePlatform.
  • Dataset participation; resource stop: relation specification ETL-DATA-REL-2025, owned by ETLDataUseRelations@WarehousePlatform, declares SourceDatasetParticipatesInETLWork(dataset, work, extent) and DestinationDatasetParticipatesInETLWork(dataset, work, extent). The stipulated job facts make the first obtain for RawOrders_2025-08-11, ETL_Nightly_2025-08-11T01:00-01:47, and its extent, and the second for WarehouseOrders_2025-08-11 with the same Work and extent. Neither predicate means later analytics use or dataset transformation. The case names no direct cluster-time or storage-use predicate, so those optional claims return missing-governor[ETL-RESOURCE-USE].
  • Actual change, no connection yet: A.3.4 identifies WarehouseOrders_LoadTransformation_2025-08-11 as the bounded change of the exact dated warehouse partition across 01:00–01:47 under the declared source-snapshot and partition-write conditions. Before that boundary the partition lacks AcceptedOrdersRowSet_2025-08-11; after it, the project data-state relation to that row set obtains. This case declares neither a direct W-to-T predicate nor a complete A.6.RCD disposition-2 claim with a constructor, governed base predicates, participants, and case facts, so it returns missing-governor[ETL-WORK-TO-CHANGE]. Keep the Work, transformation, and dataset-participation facts; shared time, destination label, and post-state do not connect W to T.
  • A.13 Agent basis, performer System, and assignment: ETL_Runtime is independently admitted as the exact running System. BatchExecutionControllerSystemRole is a declared local agential kind whose membership criterion requires condition-sensitive regulation of the stated batch action against the batch completion and failure policy. The runtime’s scheduler, authoritative state, policy branches, retry/redirect behavior, and stop conditions support its classification under that local criterion at this grain; no Grade or autonomy-profile claim is used. TransformerRuntimeAssignment is the direct assignment species; ETL_Runtime_TransformerAssignment_2025-08-11 is the obtaining occurrence with holder ETL_Runtime, assigned-kind value BatchExecutionControllerSystemRole, and an extent covering the ETL interval. Actual trace facts then support the dated ETL action and Method enactment; F.6 relates that Work to the same assignment. Code, a model artifact, the assignment alone, or a successful output does not supply agency or Work.
  • Parallel parts. Extract_A and Extract_B overlap. The rule permits Transform to start when either completes. Whether the transform actually overlapped the remaining extraction depends on their execution times.
  • Retry: WarehouseWriteAttempt-1 ended at 01:36 without satisfying WarehousePartitionWriteComplete@ETL-2025; WarehouseWriteAttempt-2 then entered to satisfy that same condition for the same dated partition and source snapshot with a smaller batch. Local declaration ETLRetryRelations@WarehousePlatform defines RetriesWarehousePartitionWrite(later, earlier) over <U.Work, U.Work> by exactly those facts and permits one immediate failed predecessor. The relation obtains for the two named attempts; a generic retryOf token is not used.
  • B.1.4 temporal roll-up. ETLSLAElapsedSpan-2025 uses the hull of the selected Work-part intervals. ETLWorkCoverage-2025 uses their union. To determine cluster utilization, identify which cluster resources these executions occupied and for how long, then apply the selected capacity measure. The job intervals alone leave that resource question open.
  • B.1.6 resource roll-up: no compute or storage aggregate is asserted until the ETL project declares cluster-time and storage-use predicates and supplies the exact Work, resource, value, unit, and extent participants. Until then return missing-governor[ETL-RESOURCE-USE]; the two dataset-participation relations remain valid.

A.15.1:6.3 - Thermodynamic cycle without a whole-rig performer shortcut

Carnot_Cycle_Run_2025-08-09T1300_1306 is a candidate Work designator, and Carnot_Cycle_Operation@ThermoLab is the proposed enacted Method. A state-plane trace can support thermodynamic state and Transformation claims, while a declared ThermoWorkOccursWithinRigBoundary@ThermoLab relation can locate an independently admitted Work occurrence inside LabRig_7.

The current case admits LabRig_7 as a System and supports its containment and thermodynamic participation, but it does not independently declare a local agential kind for the rig whole, classify the rig under it, establish an obtaining assignment, or supply evidence that the rig whole satisfies such a criterion for the proposed cycle action. Do not invent whole-rig initiation, redirection, or stop facts. Recover the actual performer System, its A.13 core, and the independently grounded occurrence, Method, extent, and containment facts before admitting the candidate as performed Work. Only after admission may a precise assignment-bound claim add F.6.

Until then, retain the supported System functioning, thermodynamic change, Method proposal, state-plane representation, and evidence claims. Lower only the unsupported Agent, performer, U.Work, and F.6 claims. A containing System, controlled apparatus, MethodDescription, or trace does not perform by being the locus or evidence of the cycle.

A.15.1:6.4 - Claim handling (episodes versus monitoring slices)

ClaimsTeam_A performs claim handling on 3 June 2026, with a 29-minute gap between initial review and resumed resolution. The one-hour callback criterion supports treating the resumed performance as an episode of the same Work; the fifteen-minute alternative supports treating it as a later occurrence.

  • Top work occurrence: ClaimHandling_Case_8142_2026-06-03.
  • Actual method and containing-system relation: enactsMethod -> ClaimHandling@InsuranceOps-2026; ClaimWorkOccursWithinOperationsBoundary@InsuranceOps(ClaimHandling_Case_8142_2026-06-03, ClaimsOperations_A) obtains under the operations delimitation declared in ClaimsWorkBoundaryRelations@InsuranceOps-2026.
  • Claim and resource stop: this case names Claim_8142, handler-time intervals, and ClaimsPlatform_A, but supplies no admitted Work-to-claim, handler-time-use, or case-system-time-use predicate. Keep the grounded claim-handling Work and return missing-governor[CLAIM-REFERENT-AND-RESOURCE-USE] for those optional relations. Callback and monitoring records remain neighboring evidence or telemetry, not occurrence constituents.
  • methodDescriptionRef: Claims_Method_v7, an episteme whose exact EntityOfConcern is admitted ClaimHandling@InsuranceOps-2026 and whose substantive claims describe its handling procedure under A.3.2.
  • A.13 Agent basis, performer System, and assignment: ClaimsHandlerSystemRole is a declared local agential kind for claim-resolution action; its criterion requires goal-directed, condition-sensitive regulation of the stated handling action, the case stipulates classification of ClaimsTeam_A : U.System under it and adequate evidence for that local criterion and classification for the claim scope and window; no Grade or autonomy-profile claim is used. ClaimsHandlerAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. ClaimsTeam_A_HandlerAssignment_2026-06-03 is the obtaining occurrence: its holder is ClaimsTeam_A, its assigned kind is ClaimsHandlerSystemRole, and its extent covers the claims Work. The stated facts establish F.6 performedUnderAssignment for this Work and that occurrence.
  • Episode policy: InitialReviewEpisodeWork-8142 and ResumedResolutionEpisodeWork-8142 are first independently admitted as Work individuals with their own A.13-qualified actual performers, performance histories, enacted Methods, extents, and containing-System relations. Any precise assignment-bound attribution for either episode is checked separately through F.6 after admission. The named claims-handling continuity use then applies ClaimsWorkContinuityPolicy_v7, a C.2.1 policy episteme interpreted under Claims-Handling-Scheme-2026. Its stated under-one-hour callback criterion supports assertion ClaimsSegmentation-v7-8142 that the two named Work individuals stand in EpisodeOf_work relations to ClaimHandling_Case_8142_2026-06-03. The policy supports the ambiguous grouping.
  • Competing policy with unresolved edition continuity: ClaimsWorkContinuityPolicy_15min-Alt, interpreted under the same reference scheme, states a fifteen-minute callback threshold. Applied to the same 29-minute gap, it supports assertion ClaimsSegmentation-15min-8142 that the resumed performance is a later Work occurrence rather than an episode under the first parent. The case establishes neither positive nor negative C.2.1 edition continuity between the two policies. The receiver can select the alternative for this use while retaining that uncertainty. Switching policy supports a different use-local segmentation judgment of the same interval history. A claim that it is a later edition requires C.2.1’s historical-continuation predicate to be established.
  • Temporal monitoring slice: MonitoringSlice_09:15-09:20 is a C.27.TA temporal aspect used for queue-latency evidence. It is not a TemporalPartOf_work participant or an episode. If a later use needs an independently admitted Work sub-occurrence with its own performed content and exact extent, identify that Work first and test the applicable §4.1a part predicate.
  • Method relation: under ClaimsSegmentation-v7-8142, both episodes enact the same claim-handling method; under ClaimsSegmentation-15min-8142, each of the two Work occurrences enacts that method. The segmentation choice changes neither enactment fact. The five-minute slice does not prove a submethod.

A.15.1:6.5 - Internal-combustion engine without cell-whole performerhood

EngineRun_Cell7_2026-06-03T1300_1330 is a candidate Work designator and FourStrokeEngineOperation@TestBench-2026 is the proposed Method. Engine_Cell7 may be an admitted containing System, and EngineUnderTest_7 may exhibit functioning, behaviour, causal participation, state change, and resource use under separately governed claims.

Those facts do not classify the cell whole or engine-under-test under a local agential kind. This case supplies no independent A.13 local-kind criterion, cell-whole classification, obtaining agential assignment, or evidence that the cell whole satisfies such a criterion. Recover the actual performer System, its A.13 core, and the independently grounded test action, Method, extent, and containment facts before admitting performed test Work. Only afterward may a precise assignment-bound attribution add F.6. If the admission basis is absent, keep the engine-cycle, telemetry, Method-factor, Transformation, and resource claims and leave the performer and Work unresolved.

Crank-angle intervals and one-second telemetry windows remain C.27.TA temporal aspects unless a receiving use first identifies an independently admitted performed Work sub-occurrence and the TemporalPartOf_work predicate passes. Intake, compression, combustion-expansion, and exhaust are Method factors only when A.3.1/B.1.5 establish their Method identities and whole-Method relation; physical strokes and traces do not become submethods or Work parts by label.

A.15.1:6.6 - Detector receiver: narrow control agency versus broad reception Work

Receiver_Rx42 is an admitted System whose components can function and interact with RF_TestSignal_42_2115. A named automatic-gain-control loop may support a narrow A.13 claim only if a local GainRegulationControllerSystemRole has an independent target-relative membership criterion, the exact controller System satisfies it, an assignment obtains for the relevant window, and evidence shows that the System satisfies that criterion; add a characteristic profile only if the receiving use consumes one. That narrow claim does not make the receiver whole an Agent for envelope detection, diagnosis, or a broader reception service.

Admit ReceiverReception_Rx42_2026-06-03T2115_2120 as Work only after the exact performer System, its complete A.13 basis, actual performance history, enactsMethod fact for EnvelopeDetection@RadioLab-2026, temporal extent, and containing-System relation independently pass A.15.1. Only after that admission may a precise assignment-bound claim add F.6. Otherwise retain receiver functioning, component behavior, waveform interaction, retuning trace, and Method proposal without a Work assertion.

A one-second reception slice remains a C.27.TA temporal aspect unless an independently admitted performed Work sub-occurrence and the direct part predicate are established. Tuning, rectification, smoothing, and acoustic output may be Method factors, component behaviors, mechanism material, evidence traces, or operational Work parts only under the pattern that defines the claimed relation; an AGC loop or detector component does not settle those identities.

A.15.1:6.7 - Classification work without result collapse

RecognitionEvaluator_A evaluates Pump_37 from 10:15 to 10:22 on 20 July 2026. The evaluation application returns unknown; the occurrence of evaluation and the candidate’s recognition judgment remain separate claims.

Pump37_RecognitionWork_2026-07-20T1015_1022 is one Work individual admitted under U.Work, with temporal extent 10:15–10:22. RecognitionEvaluatorAssignment is a directly declared species whose signature uses the local RecognitionEvaluatorSystemRole domain. The case stipulates RecognitionEvaluatorSystemRole as a declared local agential kind with an evaluation-action membership criterion, classification of RecognitionEvaluator_A under it, and adequate evidence that the System satisfies that local criterion for the scope and window; no Grade or autonomy-profile claim is used. Pump37_EvaluatorAssignment_2026-07-20 is its obtaining occurrence, with RecognitionEvaluator_A as holder and an extent covering the Work. F.6 performedUnderAssignment and enactsMethod(Pump37_RecognitionWork_2026-07-20T1015_1022, HolonRecognitionEvaluation@FPF) obtain. FPFRecognitionWorkBoundaryRelations declares RecognitionWorkOccursWithinServiceBoundary(work, system); under its stated service delimitation and 10:15–10:22 window, the relation obtains for this Work and FPF_Recognition_Service_A. A.6.1 application Pump37_RecognitionApplication_2026-07-20T1017 has obtaining candidateArgument -> Pump_37 and judgmentResult -> unknown bindings, so candidate participation and returned value need no generic affected-referent or Work-result relation. This case supplies no admitted evaluator-time or runner-compute resource-use predicate; return missing-governor[PUMP37-RESOURCE-USE] for those optional claims without lowering the Work or application bindings.

The returned unknown value remains the A.6.1 result binding. No U.Transformation of Pump_37 or of a classification record is asserted. This evaluation Work remains admitted under the full §4.1 test from its stipulated A.1:4.2 construction, the stated performer’s A.13 basis, independently grounded performance history, enacted Method, extent, and the obtaining service-boundary relation just stated; its covering assignment and F.6 attribution remain separate obtaining facts. The application binding is another separate fact, and the absent optional resource-use predicates do not lower the Work. No pre-state, post-state, or delta is needed. Candidate-side criterion satisfaction remains under A.1; evidence and assurance remain neighboring relations; and any materialized classification assertion or evaluation-result episteme remains under C.2.1.

A.15.1:6.7.1 - Filled result route: build, verify, transfer, accept

BuildRunner_A builds ReleaseBinary_12 during 09:00–09:12 on 21 July 2026 and populates ArtifactStorePartition_12. Separate verification takes place during 09:13–09:18. Its application returns pass, supported by checksums and test logs. The binary moves from ArtifactStorePartition_12 to StagingSystem_A; acceptance remains unresolved because the case supplies no acceptance predicate relating that verification verdict to the binary.

BuildRunnerAssignment is a directly declared species whose signature uses the local BuildRunnerSystemRole domain. The case takes as premises the declaration of BuildRunnerSystemRole as a local agential kind with a specified build-action membership criterion, classification of BuildRunner_A : U.System under it, and adequate evidence that the System satisfies that criterion for the scope and window; no Grade or autonomy-profile claim is used. BuildRunnerAssignment_2026-07-21 is its obtaining occurrence, with that System as holder and an extent covering 09:00–09:12. The stipulated A.1:4.2 construction, action history, enacted Method ReproducibleBuild@BuildOps-v12, extent, and containment facts under BuildWorkOccursWithinServiceBoundary for BuildService_A support the §4.1 admission of ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work. The separate F.6 test establishes attribution of that Work to the same assignment with BuildRunner_A as holder. Those facts establish distinct Work and attribution results.

The rows below add only the result and consequence claims that are current in this case. Every additional verification, evaluation, or acceptance Work named in a row needs its own A.15.1 admission basis; any precise assignment-bound attribution for it needs its own later F.6 check. It does not inherit BuildRunner_A or the build assignment.

Current case claimObject or relationKept separate from
build application returned the binaryA.6.1 application BuildApplication_12 of declared operation storeWrite@BuildOps-v12, with argument binding storeTarget -> ArtifactStorePartition_12 and result binding builtBinary -> ReleaseBinary_12entity inception, production completion, delivery, acceptance
subject practice also needs a direct result relationcase-local occurrence BuildRunReturnedBinary_12 under already declared predicate BuildRunReturnedBinary@BuildOps-v12, relating the build Work to ReleaseBinary_12; if that declaration were absent, this row would be omitted and the A.6.1 binding retaineda universal WorkResultRelation
the artifact-store partition changedA.3.4 identifies ArtifactStorePopulationTransformation_12. BuildOps relation specification BuildOpsWorkChangeRelations-v12 declares the direct predicate BuildWorkPopulatedStore@BuildOps-v12(work, transformation) with participant order <work, transformation>. Its test requires the named Work to be the performed process that, through storeWrite@BuildOps-v12 application BuildApplication_12 and its storeTarget -> ArtifactStorePartition_12 binding, brings about the independently identified population transformation of that same partition. The stipulated Work, application, target binding, and transformation facts make the predicate obtain for ReleaseBinary12_BuildWork_2026-07-21T0900_0912 and ArtifactStorePopulationTransformation_12; C.2.1 assertion BuildWorkPopulatedStore-12 states that positive claimthe application remains an independently identified occurrence used by the predicate test; shared time, artifact label, or returned binary cannot establish the direct W-to-T claim
this was production, the binary first existed, and production completedthree separate A.15.PROD local claims: whole-production-work participation for the build Work; inception of ReleaseBinary_12 at 09:11 under ReleaseBinaryIdentitySpec_v12; completion at 09:12 under BuildCompletionCriterion_v12one omnibus production/result record
verification returned passseparate ReleaseBinary12_VerificationWork_2026-07-21T0913_0918 : U.Work, A.6.1 application VerifyApplication_12, result binding verdict -> pass, and C.2.1 episteme BinaryVerificationResult_12 when the verdict content needs its own referenceacceptance and the build Work’s result binding
checksums and test logs support that verdict claimA.10 account citing evidence-provenance relation BinaryVerificationEvidenceUse_12, bounded to the verification claim and staging decisiontruth by carrier presence or acceptance
the binary moved to stagingrelation occurrence ArtifactTransferToStaging_12 under declared predicate ArtifactTransferredToStaging@BuildOps-v12, with participants ReleaseBinary_12 and StagingSystem_A, establishes transfer from the declaration’s fixed source ArtifactStorePartition_12 to that staging Systemproduction, verification, acceptance
staging accepted the binaryStagingAcceptanceWork_12 and StagingAcceptanceCriterion_v12 are identified. VerifyApplication_12 returned pass through the binding verdict -> pass. This case declares no acceptance predicate relating that verification verdict to ReleaseBinary_12 under the criterion; return missing-governor[STAGING-ACCEPTANCE] and do not assert acceptancetransfer, evidence, or a bare pass value cannot fill the missing relation

For a narrower report, keep only the rows its claims need and retain access to their grounds under §4.4.

A.15.1:6.8 - Bias-Annotation

BiasHow A.15.1 prevents it
Plan-as-work biasU.WorkPlan, schedules, method descriptions, and intended parameter bindings stay separate from the dated occurrence.
Log-as-work biasTelemetry, dashboards, provenance rows, and work publications can evidence or describe a work occurrence; they do not become the occurrence.
Method-as-occurrence biasU.Method and U.MethodDescription identify or describe the way of doing; an independently grounded assertion that one Work individual is admitted under U.Work designates the dated performed occurrence.
Evidence-as-authority biasEvidence, assurance, gate, release, and causal-use claims keep their subject patterns and do not follow from a work record by appearance.
Record-handling-as-transformation biasCopying, formatting, evaluating, or publishing records can be grounded as Work occurrences admitted under U.Work without an automatic change claim. Any claimed record or dataset transformation still needs independent A.3.4 identity plus a declared predicate with the exact Work and transformation participants, or a filled C.2.1 local compound claim under A.6.RCD disposition 2; otherwise return missing-governor[work-to-change].

A.15.1:7 - Scope Declaration and Rationale

  • Applicability: Use the same occurrence test for pragmatic costing, architecture use, teaching examples, and source or evidence questions; when the current claim is only about a description, publication, source, or evidence relation, apply the direct pattern for that claim.
  • Scope declaration: The occurrence head is universal. Temporal semantics use the declared temporal reference. A simple uninterrupted occurrence needs no continuity-policy episteme; identity, episode, retry, resumption, or aggregation claims cite workContinuityPolicyRef and its effective reference scheme only when the named use must resolve an ambiguous boundary. Add claim scope, a qualification window, model-use structure, evidence use, or source-currentness assessment only when changing that neighboring fact would change the receiving assertion or reliance; otherwise omit it.
  • Rationale: Gives FPF a notion of occurrence with an A.13 agency basis for every actual performer U.System, an independently grounded performance history, an obtaining enactsMethod relation, temporal extent, and containment. When precise assignment-bound attribution is current, a separately checked F.6 relation uses the covering occurrence of the exact directly declared U.SystemRoleAssignment species. Costing, quality, and audit then rest on independently identified Work occurrences rather than plans, recipes, assignments made to act, or a generic role-enactment fact.

A.15.1:8 - Conformance Checklist (admission checks)

CC-A15.1-1 (Distinct objects). U.Work is the admitted kind for dated performed Work occurrences. Each Work individual is world-side; it is not a U.Method (reusable way), U.MethodDescription (description), local system-role kind, System-classification judgment, U.SystemRoleAssignment (assignment), U.WorkPlan (plan or schedule), or assertion, record, log, or publication about Work.

CC-A15.1-2 (Required occurrence basis). A conforming world-side Work account starts with one dated candidate action and every actual performer U.System with its A.13 local kind and criterion, classification, obtaining assignment, scope, working situation, and window, plus evidence adequate for those core claims and any characteristic profile conditionally consumed by the receiving use. Apply A.1:4.2 to the candidate occurrence’s construction and the full §4.1 test to its admission. It establishes that the action actually followed at least one Method, has a temporal extent, and lies inside at least one locally declared Work-to-System boundary; on that independent basis A.15.1 admits the occurrence under U.Work and states its owned relations. F.6 is not an admission condition. When the receiving claim also needs precise assignment-bound performer attribution, apply F.6 afterward to the already admitted Work and the same obtaining A.13 assignment. The account also names every declared Work-to-referent, participation, or resource-use predicate used by the receiving claim, or returns the missing governor instead of inventing a relation. CC-A15.1-3 (Time window). A conforming assertion or description about one Work occurrence designates a world-side individual with a closed temporal extent [t_start, t_end], or an explicitly open end while the occurrence is in flight. The episteme states or designates that extent and, where relevant, location or asset; neither an interval field nor the presence of the record creates the occurrence.

CC-A15.1-4 (Interpretation and policy basis). A load-bearing work claim names direct occurrence facts first. It cites workContinuityPolicyRef, its effective reference scheme, and applicable scope or qualification window only when a named identity, episode, retry, resumption, or aggregation use must resolve an ambiguous segmentation. Any selected method-description episteme, aggregation-policy episteme, selected model-use structure, acceptance criterion, evaluation work, result episteme, and evidence use remains a neighboring claim rather than a work-identity field.

If two local senses must be related, F.9 receives two exact SchemeSenseCell endpoints and one BridgePredicateProfile; a Bridge is positive only when that profile’s predicate obtains. State the proposed comparison, substitution, translation, or publication separately in a C.2.1 bounded-use claim, with its action, direction, correspondence rule, and tolerated loss. State ordinary evidence reliance through the applicable A.10 account of independently established evidence-use relations, including the same-use RelianceDisposition required by F.9:4.2 for reliance on an affirmative Bridge-use claim. Add a B.3 assurance result only when an actual named assurance claim is current. A different reference scheme, system-role assignment, selected description episteme, or model-use structure alone establishes none of these facts. CC-A15.1-4b (No mandatory state-plane or delta). A Work claim needs no StatePlaneRef, pre-state, post-state, or delta merely to establish occurrence identity. If the receiving claim says that a referent changed, A.3.4 identifies the transformation and its state or boundary facts. Connect it to Work only through a declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with a recoverable constructor, governed base predicates, actual participants, and case facts; otherwise return missing-governor[work-to-change]. CC-A15.1-5 (SystemRoleAssignment interval coverage). Every obtaining F.6 performedUnderAssignment(W, RA) attribution cites two assignment identities already recovered through A.2.1 and the performer’s A.13 core: the exact directly declared species and the same obtaining occurrence RA of that species. The species supplies the signature, participant meanings, predicate, and applicability. The occurrence supplies the actual participant values, including the holder System, and has an extent covering the Work or exact performed part. The holder equals the exact admitted U.System already recovered as actual performer through A.13. If holder equality or coverage fails, keep the Work occurrence, performer claim, assignment occurrence, and attribution separate; repair or reject the attribution, also rechecking any A.13 or A.15.1 admission premise that the same finding challenges. A retroactive occurrence may be established only under A.2.1’s exact rule for its directly declared species. F.6 discovers neither identity nor performer.

CC-A15.1-6 (Actual participant and operation binding). For an operation argument or result, name one identified A.6.1 application and its exact declaration-local binding. For any other actual parameter, participant, premise, constituent, reference use, resource, or work-to-referent claim, name the declared subject predicate, participant order, and actual participant values. If the required route is absent, name the missing relation or binding in the missing-governor result and do not assert it. A MethodDescription declaration, default, A.15.3 planned filling, gate selection, compatible ValueKind, or stored token establishes no actual binding. CC-A15.1-7 (Capability check). Any capability threshold relied on for a Work occurrence is the declared bound in the selected Method-side claim. Test it by a named A.2.2 capability-fit predicate against the qualified ability of the holder named by that condition for the required contribution, for the work interval or declared checkpoints. Apply a collective condition to the collective holder, an individual condition to its performer, and a condition required of every performer to each performer, as explained in §4.2. Name the predicate, holder and ability claim, required contribution, threshold, work need and result. If the fit predicate is absent, return missing-governor[capability-fit] and assert neither fit nor failed fit. A U.Method or U.MethodDescription may cite or describe the threshold but creates neither capability nor fit. State a failed fit in its evaluation-result episteme or direct characteristic/evaluation relation, never as an intrinsic work outcome.

CC-A15.1-8 (Acceptance criteria). An acceptance claim names the declared acceptance predicate, its participants, applicable conditions and the facts that establish the result. Where the rule calls for a comparison or verdict, identify the criterion episteme or comparator specification and its required result. Where an authorised act is decisive, establish the act and its authority for this result. Identify evaluation or acceptance Work when the claimed occurrence matters. A claim of historical criterion continuity needs the C.2.1 EpistemeEditionRelation; a version label is insufficient. If no predicate governs acceptance, return missing-governor[acceptance]. Success class, measurement, comparison result and acceptance verdict remain distinct; none is a Work field or a condition of Work membership. CC-A15.1-9 (Resource attribution). Performed resource-use facts (energy, materials, machine-time, money, tool wear) are attributed through declared predicates that name the particular Work, resource, amount, unit, and extent participants, not to U.Method, U.MethodDescription, a system-role kind or assignment, or an assertion of holder ability. If no predicate governs the needed performed-use claim, return missing-governor[resource-use]; keep any separately warranted estimates or derived values with their source values, model and conditions. Any aggregate ledger, unit conversion, allocation, or overlap and deduplication result belongs to B.1.6 and cites the contributing Work occurrences and resource-use facts.

CC-A15.1-10 (Mereology declared). When exact work-part relations obtain among Work individuals, declare each relation: temporal-part, episode-part, operational-part, or another relation with its own predicate. Ambiguous mixtures lower aggregation and identity claims. Each A.15.1 work-part relation uses two independently admitted Work participants and the predicate and identity rule in §4.1a. A bare interval stays with C.27.TA or its direct domain object. Concurrency adds a separately declared temporal-overlap claim through C.27.TA. If the reader also claims coordination, name its declared predicate and actual participants; overlap alone does not establish it.

CC-A15.1-11 (Temporal coverage selection). For a temporal roll-up, B.1.4 identifies the participating Work occurrences, their intervals, temporal reference and time window, aggregation concern, selected combining rule, coverage and overlap conditions consumed by that rule, and admissible use. A.15.1 supplies the occurrence intervals but does not own the aggregate.

CC-A15.1-12 (Resource aggregation). For a resource roll-up, B.1.6 identifies the contributing Work occurrences, typed resource values with applicable units and attribution grounds, accounting scope and time basis, aggregation rule and admissible use. Preserve the delimitation, overlap, allocation or deduplication conditions consumed by that account; an adequate statement or existing ledger can convey the result. A.15.1 supplies performed resource-use facts but does not own the aggregate.

CC-A15.1-13 (Identity and retries). A distinct actual work-entry after an established completion or termination identifies a later Work occurrence; a proper work part and its parent and independently grounded concurrent performances are also distinct individuals. Add an EpisodeOf_work relation only when its §4.1a predicate holds. Add a retry or resumption relation only under a locally declared species whose participant meanings, predicate, identity, cardinality, and applicability pass §4.1a; bare retryOf and resumptionOf are route cues only. An interruption, performer or assignment replacement, method or mode switch, retune, rework, affected-referent change, or binding change is stated as direct history and neither splits nor preserves the parent by itself. Cite workContinuityPolicyRef only when a named use needs a branch criterion for that ambiguity. A changed MethodDescription or another policy episteme alone revises at most the dependent description or segmentation judgment. Call the policy an edition only when an exact C.2.1 EpistemeEditionRelation obtains; a non-continuing replacement can support a different judgment about the same performance history. CC-A15.1-14 (Concurrency and ordering). Overlaps and precedences among Work occurrences use C.27.TA with an exact temporal bearer, reference, intervals, and declared predicate. Implicit “step order” is not performed-work evidence.

CC-A15.1-15 (Cross-locality evaluation). A work occurrence keeps one identity when several receiving uses evaluate it. Each use names the reference scheme, claim scope, criterion, qualification window and result basis it needs; a separate evaluation Work is identified only when that occurrence claim is current. When two local senses must be related, test the exact F.9 Bridge, then state the proposed comparison or substitution, direction, rule, and tolerated loss in a separate bounded-use claim and check reliance under A.10 or B.3. A shared work name, record, or Bridge carries no acceptance across uses. CC-A15.1-16 (Method-description changes do not decide Work identity). If the selected MethodDescription episteme changes during the occurrence, state the description-selection or override claim separately. That selection change alone neither splits nor preserves Work. When an accompanying actual performer-system, covering-assignment, enacted-method, binding, affected-referent, mode, or extent change creates a boundary question for a named use, first use the direct occurrence facts. Apply that use’s exact continuity-policy criterion only if those facts leave the grouping ambiguous. A later or competing policy episteme may support another judgment; it is a later edition only when its exact C.2.1 EpistemeEditionRelation to the earlier policy obtains. Otherwise retain the separately identified policy and leave edition continuity unresolved unless a negative result is independently established. CC-A15.1-17 (Distributed performers). If multiple admitted U.Systems jointly perform the same top-level Work occurrence, name every actual performer and recover its A.13 basis before A.15.1 admission. If precise assignment-bound attribution is current, use F.6 after admission to check the exact assignment for each System. If the use instead needs a parent Work with child occurrences, admit every child independently under the full §4.1 test from its own A.1:4.2 construction, performer basis, history, Method, extent, and containment, then add any needed F.6 attribution and Work-part relation. A lead, responsibility, or coordination claim remains separate and cannot substitute for the actual performer set.

CC-A15.1-18 (Evidence for the claim and complete Work-admission grounds). For logs and telemetry, identify the candidate action, the claim supported, and the applicable evidence-use relation under §4.6. One source may support only part of the occurrence account. To admit the occurrence as Work, ground the complete §4.1 basis across the sources relied on: its A.1:4.2 construction, performance history, every actual performer System with its A.13 basis, at least one Method actually followed, temporal extent, and at least one obtaining local Work-to-System containment relation. Keep that admission basis recoverable when a later source supports a narrower claim about admitted Work. When precise assignment-bound attribution is also current, support its separate F.6 assertion through the evidence relevant to that relation.

CC-A15.1-19 (Affected referent and work scope). Each assertion or description about a Work occurrence designates the exact Work individual and states a direct work-to-referent relation only when the receiving use needs one. That relation must obtain independently; naming the referent in the episteme establishes neither actual change, production, delivery, acceptance, nor a universal affected relation. When the receiving use needs no such relation, omit it without lowering the Work occurrence. CC-A15.1-20 (Actual change stays neighboring). When the receiving claim needs actual change, identify an exact U.Transformation under A.3.4. Connect it to Work only through a declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with a recoverable constructor, defined base predicates, actual participants, and case facts; otherwise retain both objects and return missing-governor[work-to-change]. Work can occur without a current transformation claim, and a no-op, evaluation, inspection, communication, or record-handling occurrence is not forced into a delta schema. The inverse also holds: an accompanying occurrence is admitted as Work only when every actual performer System has an A.13 basis and the exact performance history, enacted Method, temporal extent, and at least one obtaining local containing-system relation satisfy the full §4.1 test together with the occurrence’s A.1:4.2 construction. Any precise assignment-bound attribution is then checked separately through F.6. Do not invent an assignment for a causal participant, reject a non-human performer by resemblance, or collapse internal performer and affected positions into a primitive self-relation. CC-A15.1-21 (Record handling remains Work without automatic transformation). Copying, formatting, evaluating, or publishing records can be admitted as U.Work under the full §4.1 test, including the occurrence’s A.1:4.2 construction, when every actual performer System has an A.13 basis and the exact action history, at least one obtaining enactsMethod relation, extent, and at least one obtaining local containing-system relation are grounded. A precise assignment-bound attribution is a separate later F.6 result. State an affected referent, binding, or resource-use fact only through its independently obtaining relation when the receiving claim uses it. Identify any actual record or dataset transformation separately under A.3.4; a label, output record, or post-state picture does not establish it. CC-A15.1-22 (Containing-System relation declared). Each Work occurrence has at least one obtaining locally declared Work-to-System relation whose predicate names the exact system delimitation and qualification window that contain the complete occurrence. Name several when distinct valid boundaries matter; none is inferred from a System part relation, accountability, colocation, or a diagram. Keep every containing System distinct from the affected referent. If the receiving claim relates Work to that referent or to a Transformation, name the separate declared predicate, actual participants, and obtaining facts; containment and shared timing establish neither. Bare executedWithin is a historical route cue, not a current positive relation.

CC-A15.1-23 (No transformation composition from Work mereology). Work parts support only their declared work-part facts and provide inputs to separately recovered B.1.4 or B.1.6 aggregation claims. They establish neither component transformations, transformation parthood, a composite transformation, nor a parent effect. Recover each actual transformation independently; when a production or effect claim needs unavailable transformation composition, return missing-governor[transformation-composition]. CC-A15.1-24 (No new claims on publication views). MVPK views about Work project the declared assertion or description of the Work occurrence; they do not add properties or claims. For a displayed measurement or comparable value, name the Characteristic and the unit, scale, reference-plane and EditionId pins needed to interpret it under its source definition. Apply E.17’s PC-field requirements when its formal publication profile is selected. Use “signature” only for a signature under its defining pattern.

CC-A15.1-25 (No Gamma leakage). Publication views cite exact B.1.4 temporal-aggregation or B.1.6 work-resource-aggregation results and policies when showing aggregates. An explanation of the calculation preserves the cited definition, policy, edition and qualifications; any defaults come from that declared basis. Optional Gamma notation remains with the recovered Part B aggregation claim. The view may carry the source-attributed explanation and references needed by its use.

CC-A15.1-26 (Input and output declarations on publication views). In E.17’s optional morphism profile, keep the signature-side declarations authoritative. Provide an accessible source return, or carry the needed source-attributed declarations and material pins when the face must support use without that access. A readable explanation may restate the source content needed by its use while preserving the source’s input and output declarations.

CC-A15.1-27 (Comparator ordering and return sets). Across-occurrence comparison presented on a publication view about Work uses a declared ComparatorSet (map-then-compare), returns sets when order is partial, and rejects hidden scalarization or means that the ordinal Scale does not admit.

CC-A15.1-28 (Comparator and transport pins). When an acceptance or KPI claim uses a comparison, pin the selected ComparatorSet.edition and comparator-spec edition. Retain the rule and edition for any conversion used by that claim; where a TransportRegistry governs it, pin TransportRegistry.edition and the selected transport policy ids. When two local senses must be related, cite the exact obtaining F.9 Bridge only as the correspondence premise, state the proposed bounded reuse in a separate C.2.1 claim, and check reliance under A.10 or B.3. A selected reference-plane change remains with CHR and its direct relation; the Bridge transfers neither reuse nor a plane value. For a claimed penalty, identify the rule and affected assessment as described in §4.5.

CC-A15.1-29 (Telemetry-reference pins, when applicable). If a work occurrence feeds G.11 or QD and OEE portfolios, the evidence relation cites the telemetry, archive, and policy references declared by the governing comparison, archive, evidence, or refresh pattern. Illumination remains report-only telemetry unless a governing comparison, archive, or selection pattern promotes that use.

CC-A15.1-30 (Part naming parsimony). Give an independently admitted Work part a stable name only when a current or later use needs to identify it distinctly. An interval, telemetry segment, pause, event-log row, engine-stroke label or detector component does not become a Work part by naming. Use §5.1’s occurrence and naming tests; retain a sufficient temporal, evidence or other neighboring object.

CC-A15.1-31 (Method and work granularity are coupled but not isomorphic). A work part may enact a recovered submethod, but the correspondence is not automatic. A temporal work part usually enacts the same whole method during a slice. An episode may continue under one method or mode, span several operational parts, or repeat the same method fragment; an evidence policy may support a finer segmentation claim without changing method identity. An operational work part corresponds to a method factor only when that factor is recovered as U.Method under A.3.1 and B.1.5; otherwise retain the object actually identified without asserting that Method-factor correspondence.

CC-A15.1-32 (Work rows do not create architecture). Before a timetable, workflow, or architecture row supports a Work whole, part, overlap, or order claim, every Work occurrence is independently admitted under the full §4.1 test from its A.1:4.2 construction, each actual performer System’s A.13 basis, grounded action history, enacted Method, actual interval, and required containing-System relation; every whole, part, and temporal relation is then established separately. Apply F.6 afterward only for a precise assignment-bound attribution. Similar labels, shared rows, or planned co-occurrence establish none of these facts.

A.15.1:9 - Work-to-aggregation interface

A.15.1 makes the occurrence-side inputs recoverable without storing them in the occurrence: a separate assertion or description episteme designates exact Work individuals or work parts and states their temporal extents and the separately obtaining resource-use relations selected for aggregation. B.1.4 identifies the temporal-aggregation claim and result; B.1.6 identifies the resource-aggregation claim and result; a ledger may convey that account. These aggregation accounts remain distinct from Work-occurrence identity.

A.15.1:9.1 - Temporal aggregation return

For utilization, lead time, cycle time, phase coverage or another temporal roll-up, use B.1.4. Recover the Work intervals, aggregation concern, time basis, selected combining rule, conditions it consumes and admissible use. An adequate ordinary account can state the result; a separate record is needed only by its receiving use. Union, convex hull and optional Gamma_time notation concern that temporal aggregation, not Work-occurrence identity.

When the B.1.4 result selects the Work-interval profile, retain these use-specific choices:

  • Union of intervals gives the instants covered by at least one contributing interval. For time occupied or available, use intervals for which that specific resource status is established. For the fraction in that status, choose a denominator covering the same resource and assessment period.
  • Convex hull [min t_start, max t_end] gives the span of the selected intervals, including their gaps. To use this span as lead time or cycle time, establish that its endpoints coincide with the events named by that measure. If a request precedes the first work or delivery follows the last work, measure request-to-delivery time from those events.
  • Declared algebraic behavior: for either exact set-based policy, duplicate input is idempotent, input order is irrelevant, and adding intervals cannot shrink the union or hull. If another policy lacks those properties, name it rather than borrowing the union/hull result.

Never switch union and hull silently between KPIs. The formulas above profile a recovered B.1.4 aggregation over Work intervals; the selected B.1.4 claim, not A.15.1, states the temporal result.

A.15.1:9.2 - Resource aggregation return

For a total or ledger over performed resource-use facts, use B.1.6. Recover the Work participants, typed resource values with applicable units and attribution grounds, accounting scope, time basis, aggregation rule and admissible use. Establish any holon-delimitation, overlap, allocation or deduplication facts used by the account. An adequate existing statement or ledger can suffice. Additivity, allocation, traceability and optional Gamma_work notation concern the resource aggregate, not Work-occurrence identity.

Filled heterogeneous BuildOps route. Published case-local specification BuildOpsResourceUseRelations-v12 declares BuildWorkUsesResource@BuildOps-v12(work, resource, amount, unit, extent) with participant order <work, resource, amount, unit, extent>. Its test requires the named Work actually to occupy or consume the named resource during that extent, with the amount measured in the named unit. Separate case facts state that ReleaseBinary12_BuildWork_2026-07-21T0900_0912 occupied BuildPoolCPU_A for 24 runner-core-minute during 09:00-09:12, and consumed 0.84 kWh of GridElectricity_BuildZone3 within BuildService_A_Delimitation-v12 during the same extent. Those facts make relation occurrences BuildRunUsedCPU_12 and BuildRunUsedElectricity_12 obtain with those exact participant tuples. BuildRunnerAllocationEvidence_12 and BuildZone3EnergyMeasurement_12 support the facts; neither record is the resource use, and neither relation is a field of the Work.

B.1.6 result BuildResourceAggregation_12 : WorkResourceAggregation@Context names concern Build12MeasuredResourceUse, bounded context BuildOps-v12, that exact Work, and the two relation occurrences. It uses typed basis BuildComputeAndElectricityBasis-v12, measures BuildRunnerCoreMinuteMeasure_12 and BuildZone3KWhMeasure_12, evidence refs BuildRunnerAllocationEvidence_12 and BuildZone3EnergyMeasurement_12, holon delimitation BuildService_A_Delimitation-v12, and window 09:00-09:12. Policy BuildResourceRelationDedup-v12 counts each exact relation occurrence once across repeated evidence or a parent/child view. Rule BuildTypedResourceVectorSum-v12 adds only entries of the same resource type and unit. Ledger BuildResourceLedger_12 contributes <BuildRunUsedCPU_12, 24 runner-core-minute> and <BuildRunUsedElectricity_12, 0.84 kWh> and returns Build12MeasuredResourceVector = <24 runner-core-minute, 0.84 kWh> without summing or converting its unlike components. Its admissible use is the measured resource-disclosure input for Build 12; it proves no Work identity, production result, efficiency, cost, sustainability verdict, or acceptance.

When a B.1.6 aggregation must allocate shared or overlapping resource use, retain these non-default policy examples:

  • Parent attribution: book a declared shared fixed value once at the parent and independently measured variable values at children.
  • Pro rata by wall time: divide a declared shared value by relative durations only when that driver is admissible for the resource basis.
  • Driver based: allocate by a measured driver such as CPU share, weight, or priority and state the allocation rule that uses it.

Whichever policy is selected, add only disjoint or explicitly deduplicated values and keep every aggregate figure traceable to its contributing Work refs and evidence. A policy label alone establishes neither allocation nor ledger value.

A Work publication or KPI may cite either result through the E.17 publication face that projects that exact result. It may not recreate an unselected operator, infer an aggregate from parthood, or turn an aggregation record into a Work occurrence.

A.15.1:10 - Work-claim interpretation checks

When another decision relies on Work, apply only the following checks that its claims consume; reuse an established result while its basis remains applicable:

  1. Method-description interpretation, when used. Does methodDescriptionRef resolve to the selected U.MethodDescription episteme under the effective reference scheme used by the receiving claim? If the claim also says this is an edition of an earlier description, does the exact C.2.1 EpistemeEditionRelation obtain? If two local senses must be related, test an F.9 Bridge and state the bounded use separately rather than treating the reference change as a Bridge.
  2. Performer and conditional assignment coverage. For every admitted U.System named as performer, does section 4.0 recover its A.13 basis? If this receiving check expressly consumes precise assignment-bound attribution, does the account also cite the exact directly declared assignment species and the same obtaining occurrence RA already recovered through A.2.1 and A.13, and does F.6 obtain for the already admitted Work and that RA? Does RA carry the actual participant values, have that System as holder, and cover the Work or exact performed part? If no attribution is current, stop after the performer and Work checks. If the conditional attribution branch fails, repair or reject the unsupported attribution. Retain independently grounded Work and performer claims; under §4.1, recheck any admission premise also affected by that finding.
  3. Evaluation or acceptance, when claimed. For an evaluation, identify the criterion, its application to the required facts, the returned value and its evidence. For acceptance, identify the applicable predicate, participants and facts meeting its conditions, including any required decision or evaluation value. Identify evaluation Work separately when its dated occurrence is claimed. Historical criterion continuity requires the C.2.1 relation.

These checks tell the reader which description, assignment, criterion, evaluation, and relation to cite. They do not make acceptance part of work identity.

A.15.1:11 - Common Anti-Patterns and How to Avoid Them

  • “The log is the performed occurrence.” Dumping telemetry without recoverable candidate-action facts—every actual performer System’s A.13 basis, at least one Method actually followed, time window, and at least one obtaining local containing-system relation, plus any other relation the receiving claim uses—does not establish Work. Recover and admit the occurrence independently, keep the log as evidence, and add F.6 only afterward when precise assignment-bound attribution is current.
  • Record-handling-as-transformation. ETL, copying, formatting, evaluation, or publication work is treated as proof that a record or dataset changed -> Keep the grounded Work occurrence, but assert actual change only after A.3.4 identifies the transformation and either a declared domain predicate with the exact Work and transformation participants obtains or a C.2.1 local compound claim under A.6.RCD disposition 2 exposes its substrate-admitted constructor, governed base predicates, actual participants, and case facts; otherwise return missing-governor[work-to-change].
  • Silent cross-locality acceptance. “Ops accepted it, so audit accepts it.” -> Identify the acceptance rule for each receiving use and the facts it requires. Where one decision binds both recipients, establish that scope. Where their terms require separate decisions, identify the qualifying act for each. If no predicate governs the asserted acceptance, return missing-governor[acceptance]. Identify evaluation or acceptance Work separately when that occurrence claim is needed; identify a C.2.1 evaluation-result episteme when the result content needs its own reference. If the criteria use different local senses, test the F.9 Bridge, state the proposed cross-local comparison or substitution in a separate bounded-use claim, and check reliance; the Bridge itself transfers no acceptance.
  • Description-change-as-occurrence-change. Selecting another MethodDescription episteme is treated as automatically splitting or preserving Work -> State the description-selection change separately. For an identity question raised by an actual history change, first use the direct facts. Apply the named use’s continuity-policy criterion only if the grouping remains ambiguous; the policy revises the judgment, not the occurrence. Call the descriptions editions only when their exact C.2.1 relation obtains.
  • Performed cost and estimate collapse. Treating an estimate or Method-level statistic as actual resource use -> recover the dated Work and its resource-use relations. Keep forecasts, allocation and derived statistics under their own accounting rules.
  • Part ambiguity. Mixing retries, episodes, and operational parts with no declared relation → Independently admit the participating Work occurrences, then assert the relation whose §4.1a predicate holds. For a retry claim, use the locally declared species required by §5.2.
  • Timetable-as-Work-architecture. Rows with similar labels or one planned window are treated as one Work whole, its parts, or overlapping Work → Recover every actual Work occurrence first; then establish each Work-part and temporal relation separately. Keep an unperformed or ungrounded row as plan or description content.
  • Slice-as-episode. A monitoring interval, telemetry window, crank-angle segment, or one-second reception trace is called an episode only because it has timestamps -> Keep it as a C.27.TA temporal aspect, evidence relation, or telemetry relation. Use TemporalPartOf_work or EpisodeOf_work only after the first participant is independently admitted as Work and the corresponding §4.1a predicate passes; add a continuity policy only if direct boundary facts leave its grouping ambiguous.
  • Episode-as-new-work by habit. A pause, retune, or interruption is always recorded as either a new occurrence or the same one -> Preserve the boundary events first. Use direct facts when they settle the grouping. If a named use still has more than one defensible grouping, apply its workContinuityPolicyRef; without the needed criterion, leave that segmentation unresolved.
  • Method-factor-as-work-part by label. A step, stroke, receiver component, graph node, or method-description section is treated as a work part or submethod by name -> Identify the actual object and any claimed Method-factor or Work-part relation, including the relation’s participants; use the pattern that defines that relation.
  • Granularity inflation. Every interval or trace row receives a durable Work-part name -> admit the Work part independently and name it only when the receiving use needs a distinct reference under §5.1.
  • Union-hull confusion. Changing KPI coverage silently between reports -> recover the B.1.4 temporal aggregation and cite its policy per KPI.
  • Double-count in overlaps. Summing child and parent resource facts as one ledger -> recover the B.1.6 aggregation claim and apply its overlap or deduplication policy.

A.15.1:12 - Existing work-log repair applications

  1. Recover occurrence assertions. For existing logs, apply the full §4.1 test: recover the exact candidate action and its A.1:4.2 construction, every actual performer System’s A.13 basis, at least one Method actually followed, the extent, and containment facts under at least one declared local rule. Admit the Work from those independent facts, then assert the typed relations. If precise assignment-bound attribution is current, then recover the same covering assignment occurrence and its separate F.6 relation. Add optional methodDescriptionRef and only those independently obtaining work-to-referent, binding, and resource-use relations on which the receiving claim relies. Do not create Work by creating a record.
  2. Recover the work-judgment basis. Name the direct occurrence facts first. Add exact workContinuityPolicyRef, effective reference scheme, scope, or qualification window only when the identity, episode, retry, resumption, or aggregation judgment has more than one defensible branch. Keep any selected MethodDescription episteme, aggregation policy, criterion, and evidence-use relation outside the Work.
  3. Record a continuity policy only for an actual ambiguity. Cite exact workContinuityPolicyRef and its named use when an interruption, resumption, replacement, switch, or composite boundary could support more than one segmentation. If direct facts already close a simple uninterrupted case, omit the policy.
  4. Separate temporal aspect, temporal Work part, episode, and operational part. Keep a bare interval or aspect with C.27.TA or its direct domain object. Use TemporalPartOf_work only between independently admitted Work individuals when the proper temporal-sub-occurrence predicate passes; use EpisodeOf_work only for an independently admitted event-bounded Work sub-occurrence; and use OperationalPartOf_work only for an independently admitted performed constituent of the whole. Recover any Method factor separately.
  5. Name only useful Work parts. Apply §5.1’s threshold to the current or later use. Preserve the independently established relation, evidence or telemetry slice when it is sufficient, without adding a Work-part identity.
  6. Use B.1.4 for temporal roll-up. Cite the temporal aggregation’s result and selected combining rule, including the coverage and overlap conditions it uses, in the KPI; keep that account separate from Work.
  7. Use B.1.6 for resource roll-up. Recover the typed resource result, its attribution basis and the aggregation rule, with any allocation, overlap or deduplication conditions used by that account; an adequate statement or existing ledger can suffice. Each contributing performed resource-use relation remains independently obtaining with a Work occurrence as a participant.
  8. Pull plans out. Keep calendars and planned fillings in exact U.WorkPlan content; establish performed values only through direct relations in which the Work occurrence participates and through exact A.6.1 bindings.
  9. Bind actual values directly. For an operation argument or result, name the identified A.6.1 application and its exact binding. For any other participant or parameter, name the declared subject predicate, participant order, and actual values; return the matching missing-governor result when that predicate is absent. Retain MethodDescription defaults and WorkPlan choices as non-actual neighbors.

A.15.1:13 - Consequences

BenefitsTrade-offs and mitigations
Auditable occurrence claims. Cost, time and quality accounts can refer to independently identified Work through their governing relations.Identify the occurrence separately from the assertion or description; record creation is not occurrence creation.
Sound roll-up inputs. Work refs, intervals, parts, and performed resource-use facts make temporal and resource aggregation replayable.Separate aggregation. Recover temporal aggregation in B.1.4 and work-resource aggregation in B.1.6; cite their policies and results rather than copying Gamma semantics into Work.
Cross-locality clarity. Method-description, scheme, scope, criterion, evaluation, and acceptance relations prevent silent meaning drift.Bridge upkeep. Maintain F.9 Bridges only for exact local-sense crossings that a receiving use actually needs.
Explicit occurrence identity. Distinct parts, overlaps and retries provide the inputs needed to detect double-counting and identity errors.Their correct use still requires the applicable identity, temporal and accounting rules.

A.15.1:13.0 - Rationale

U.Work is retained as the admitted kind for dated Work occurrences because performer System, local system-role kind, system-role assignment, Method, MethodDescription, WorkPlan, affected entity, actual change, evaluation-result episteme, delivered entity, and downstream effect are different FPF objects. One Work individual is the world-side occurrence. Every actual performer is an admitted U.System with an A.13 agency basis for the action, scope, and window. A.15.1 admits the occurrence under the full §4.1 test from its A.1:4.2 construction, that performer basis and independently grounded history, Method, extent, and containment. Only when precise assignment-bound attribution is current may F.6 then relate that already admitted Work to the same obtaining assignment already recovered through A.13; it identifies neither. An assertion or description about the Work is a separate episteme. Missing assignment attribution alone does not revoke Work membership; a finding against a separate admission premise requires its own recheck under §4.1. Add direct Work-to-referent, binding, resource-use, or change facts only when their own relations obtain.

A.15.1:13.1 - SoTA-Echoing

Source traditionSource reference and contributionFPF useShortcut rejected
Occurrent and 4D occurrence ontologyBFO 2020, standardized in ISO/IEC 21838-2:2021, distinguishes occurrents and temporal parthood; Partridge and de Cesare’s 2013 BORO account supplies the historical lineage of identifying individuals by spatiotemporal extent.U.Work admits dated occurrence holons; each Work individual has its own temporal extent and participates in separately obtaining occurrence relations, while assertions and records about it remain separate epistemes. Parts, retries, resumptions, and overlaps stay explicit.Treating a Method factor, diagram, system-role label, log entry, or record schema as the performed occurrence.
Object-centric event logging and process miningThe OCEL 2.0 metamodel represents typed events, qualified event–object and object–object relations, and changing object attributes. The OCEL 2.1 prerelease adds single-file CSV and bundled CSV/Parquet serializations.For an event record, identify the candidate action and the claim its content supports. Several sources may jointly ground Work admission; the complete §4.1 basis must make the occurrence’s A.1:4.2 construction, performance history, every actual performer’s A.13 basis, enacted Method, temporal extent and local containing-system relation recoverable. Recover any relied-on object, binding, resource-use, interpretation or policy relation when the receiving claim needs it. Any precise assignment-bound attribution remains a separate later F.6 result. These admission conditions apply across serialization formats.Treating the existence of telemetry or event rows as sufficient grounds for U.Work admission without inspecting the claims they support.
Observability and telemetry practiceOpenTelemetry Specification 1.62.0 for trace, metric and log representation.Telemetry can support, replay, measure, or diagnose a claim about Work, but the occurrence still needs every actual performer’s A.13 basis, independently grounded history, enacted Method, temporal extent, and local containing-system relation. Add F.6 only for a separately claimed precise assignment-bound attribution, and add another enactment, affected-referent, binding, or resource-use fact only when the receiving claim uses it.Counting trace, metric, or log existence as the performed Work, a result, or dominance evidence without the direct evidence, comparison, or archive relation.
Provenance and evidence-provenance practiceW3C PROV-O is a 2013 Recommendation; the 2025 PROV-O and BFO alignment is a later interoperability contribution.Assertions or descriptions about Work cite the evidence-provenance relations and currentness notes their use needs without letting evidence, assurance, gate, or provenance claims replace the occurrence.Using a provenance relation, assurance statement, or gate result as if it were the performed Work.
Temporal-interval reasoningAllen’s interval algebra (1983) supplies qualitative relations among intervals; W3C OWL-Time (2017 Recommendation, §§3.1–3.4) represents these relations together with interval boundaries, durations and temporal reference systems.A.15.1 supplies identified Work intervals, parts, and performed resource-use facts; use B.1.4 for temporal aggregation and B.1.6 for work-resource aggregation, each with its stated policy and admissible use.Mixing union, hull, parent cost, child cost, and ordinal comparison on the Work object without a recovered Part B aggregation claim.

A.15.1:14 - Relations

  • Builds on: A.1 for the candidate occurrence’s common constructive criterion and System admission; A.2 for local agential system-role kinds and classification; A.2.1 for direct assignment species and occurrences; A.13 for the precise agency claim, characteristic profile, scope, window, and evidence; A.3.1 for U.Method; A.3.2 for U.MethodDescription; C.2.1 for episteme editions and effective reference scheme; A.2.6 for claim scope; and C.27.TA for temporal qualification.
  • Coordinates with: F.6 for attribution through the same obtaining A.13 assignment; A.15 for alignment; A.6.1 for actual bindings; A.3.4 for actual Transformations; A.15.PROD for production and inception; B.1.4 and B.1.6 for aggregation; E.10/E.10.ROLE for Agent, performer, and role wording; A.10, B.3, E.17, and A.15.4 for evidence, assurance, publication-use, and appearance-based reliance; A.15.5 for readiness; and C.32.P2S for carry-through. Permission, gate, result, production, delivery, and acceptance remain independent of Work identity.
  • Informs: reporting and KPI patterns, assurance and evidence patterns that use Work as the reference occurrence, and planning patterns that compare exact U.WorkPlan claims with independently identified Work occurrences.

A.15.1:15 - Didactic quick cards

  • What is Work? How it went this time → dated, attributable, and actually enacted.
  • Performer chain: Who performs? An admitted System with an A.13 agency basis at this grain. Did dated performance occur? A.15.1 independently admits Work. When precise assignment-bound attribution is current, under which assignment? The same obtaining A.13 assignment later tested by F.6; otherwise stop at admitted Work. Can? Capability. How? Method. Intended? WorkPlan.
  • Three-question result check: Did the Work occur? What separate result or consequence is claimed? Who judged or accepted what, by which criterion and evidence? Use section 4.6 and stop after the last current question.
  • Passive stop: Containing equipment, affected subjects, causal participants, actor-like labels, and assignments do not perform by implication.
  • Roll-ups: A.15.1 supplies Work references, intervals, parts, and performed resource-use facts; cite B.1.4 for temporal aggregates and B.1.6 for resource ledgers, each with its declared policy.
  • Episodes vs retries: record end, interruption, resumption, and later work-entry facts first; add a continuity policy only when a named use still has more than one defensible grouping.

A.15.1:15a - P2W Performed-Work Use Relation

When E.18.1 reaches performed Work, first recover each actual performer System’s A.13 local kind and criterion, classification, obtaining assignment, scope, working situation, and window, with evidence adequate for those core claims and a characteristic profile only when conditionally consumed. Then apply the full §4.1 test to the exact candidate action: establish its A.1:4.2 construction, Method actually followed, extent, and containment facts under at least one declared local rule. Admit the same occurrence under U.Work, then assert its typed relations. Only after admission, if precise assignment-bound attribution is current, use F.6 to relate that Work to the same assignment. Add only the actual operation binding, resource use, or Work-to-referent relation on which the receiving sentence relies. Planning may name intended performer conditions but does not backdate an A.13 assignment, agency claim, or Work occurrence. A Work occurrence may be designated by an episteme that also cites a U.WorkPlan, exact A.15.3 planned-filling claim, or prior readiness claim as a baseline. For an operation argument or result, cite one identified A.6.1 application and its exact binding. For another participant, premise, resource use, or work-to-referent claim, name the declared predicate, participant order, and actual values; if that predicate is absent, return the corresponding missing-governor result. Do not copy a result or consequence into Work; follow the concrete §4.6 route.

A.15.1:16 - Lowering, Repair, and Refresh Conditions

Lower a candidate Work assertion when any claimed actual performer lacks the complete A.13 basis for the action, scope, and window, or when the exact candidate-action history, occurrence designator, temporal extent, at least one Method actually followed, or one required locally declared containing-System relation cannot be recovered. A missing, unresolved or failed F.6 relation lowers the precise performedUnderAssignment and assignment-bound performer claim. Preserve independent Work admission; if that finding also questions an actual admission premise, recheck it and its dependents under §4.1. Lower an additional enactment, Work-to-referent, operation binding, or resource-use claim separately when its direct basis is missing. Do not lower supported System functioning, behaviour, causal participation, Transformation, plan, Method, evidence, or telemetry claims merely because the Agent, Work, or attribution branch fails. Repair the Work assertion or description when a subsequent source changes the resolved temporal extent, actual performance history, an actual performer System’s A.13 basis, enacted Method, selected method-description reference, direct binding, resource-use claim, work-to-referent relation, obtaining containing-system relation, or work-part relation. Repair the separate F.6 attribution when the covering assignment, direct pair fact, holder equality, species, participants, or coverage changes; do not rewrite Work membership merely because attribution changes. Reidentify only when the direct A.15.1 boundary rules decide the change or the selected policy’s branch criterion applies to a named ambiguous use. Repair a result or consequence through the matching §4.6 row rather than editing Work.

Before a new receiving use, confirm that the occurrence and related results still have the meaning, applicability and currentness that use requires. Reuse a result with unchanged grounds; recheck changed, missing or expired dependencies, using A.10.1 when a changed relied-on source affects several uses. If the question is no longer about performed Work, apply its direct pattern and keep a Work reference only when the claim depends on that occurrence.

A.15.1:End

A.15.2 - U.WorkPlan: Plan Content for Coordinating Future Work

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

At a glance. Use U.WorkPlan when a system needs one plan to coordinate possible future performed Work for an already existing subject over a stated horizon. One PlanItem names the intended Method, window, performer System or local system-role-kind condition, and only the resource, dependency, commitment, target, or baseline needed now. The plan states what is intended; A.15.1 identifies actual Work separately.

Use this when. Coordinate possible future Work through a schedule, rota, ticket or other plan content. Identify the existing subject, intended performances, horizon and reference scheme, then state enough constraints to make the current coordination decision. Use §4.3 when schedule or workflow wording leaves the claim unclear.

First useful object. One WorkPlan about a present subject, interpreted under one reference scheme, with a horizon and one usable PlanItem. Later fulfilment or variance checking is a separate use.

Ordinary path.

  1. Identify the already existing subject whose future work is being coordinated, the horizon, and one PlanItem.
  2. In that item name the possible future performance, target Method, planned window, and the intended performer System or local system-role-kind condition needed now.
  3. Add only the resource, dependency, commitment, target, or baseline needed for the current coordination decision.

Filled ordinary example. A plan about existing Lathe-7, interpreted under FabMaintenanceScheme-E2, can set horizon 2026-07-27, item inspect-spindle, method SpindleInspectionMethod-E2, window 08:00–09:00, intended performer System MaintenanceTech-4 with local kind MaintenanceTechnicianSystemRole, a one-hour machine reservation, dependency lockout complete, and baseline normal vibration. The team can coordinate the rota and reservation for that day from this content and stop before selecting a later fulfilment or variance comparison. If lockout will not be complete by 08:00, the planners defer that item or revise its window and reservation.

Detailed authoring and later comparison. Use §4.1–4.4 to settle plan identity, item content and organization. Open §4.5 only when a receiving question asks whether an independently identified Work occurrence fulfilled or deviated from a plan item. Choose the smallest A.6.RCD result that this comparison needs.

Stop condition. Stop once a system can coordinate the intended work at the needed granularity. Assess any separate claim introduced at step 3 under its governing pattern, while retaining a WorkPlan whose intended-work content meets §4.1. If no pattern states the predicate needed for a later fulfilment, variance, or occurrence-facing relation, stop only that stronger use; the plan and any local comparison whose predicate and supporting facts can be stated remain usable.

What goes wrong if missed. Intended work can be mistaken for completed performance, and later changes to the plan can erase the baseline needed for comparison.

What this buys. The team can coordinate intended Work now and, when needed, compare actual performance with the identified plan under an explicit policy.

Not this pattern when. Use the direct pattern when the current claim is a dated performed work occurrence (A.15.1), A.15.3 declaration-local planned-filling content, work-entry readiness or full-kit condition (A.15.5), a reliance appearance being used before the governing pattern or relation is recovered (A.15.4), a method (A.3.1), a method description (A.3.2), evidence or assurance (A.10 or B.3), an internal constraint result (A.20) or gate decision (A.21), publication-use behavior (E.17, with E.24.PUB for publication identity), a non-agentive forecast or dynamics model (A.3.3), or a declarative representation overread as a work-control or method claim (C.2.P.DR).

A.15.2:1 - Context (plain‑language motivation)

Before and during Work. Before Work begins, keep intended-work content in this WorkPlan. Use A.15.5 when the question is whether that Work is ready to start, and use C.11 only when a known chooser must compare an already formed OptionSet. Do not invent current Work for A.15.7. During Work, an A.15.7 answer remains separate from the plan. Revise the WorkPlan only when the intended-work content changes, and identify any later performed action under A.15.1 rather than back-filling the plan.

Intended operations are coordinated in time. A system uses a WorkPlan to decide when and by whom possible future work is intended, under what constraints and budgets. Distinguish this scheduling content from:

  • the semantic “way of doing” (that is U.Method),
  • the claims about how an admitted Method is done (that is U.MethodDescription),
  • the performed work occurrence (an individual admitted under U.Work), or
  • the state-change model (that is U.Dynamics).

U.WorkPlan identifies that intended-work episteme.

A.15.2:2 - Problem

  1. “Workflow = schedule” conflation. A way-of-doing description is used to answer a scheduling question while time, performer or resource constraints remain unstated.
  2. Plan and occurrence blur. Gantt bars or Kanban tickets are reported as if the work already happened; audits and costing degrade.
  3. Specification and time leakage. A reusable MethodDescription embeds one staffing or calendar choice without distinguishing it from the Method’s required conditions.
  4. Missing comparison basis. Without the planned baseline and applicable comparison rule, a later time, cost or quality difference cannot be classified as plan variance.
  5. Structure entanglement. Equipment or organization structure is copied into a plan without stating which structural relation constrains the intended Work.

A.15.2:3 - Forces (what the definition balances)

ForceTension we resolve
Universality vs. domain idiomsOne plan concept that fits hospitals, fabs, data centers, and research labs—while honoring local terms.
Commitment vs. flexibilityPlans need enough firmness to coordinate, while remaining easy to update as reality changes.
Intended performer vs. performed-work assigneePlans may name intended performers; the assignment used for performed work is still checked for the work interval.
Budgets vs. performed resource usePlans state targets and reservations; A.15.1 and the resource-use or ledger pattern govern performed resource-use facts.
Decomposition vs. fulfilmentPlan tasks decompose conveniently; they do not force a shape on performed Work occurrences.

A.15.2:4 - Solution - U.WorkPlan as the time-bound intention for U.Work

A.15.2:4.1 - Definition, membership, and identity

U.WorkPlan is a same-individual dependent kind under U.Episteme. C.2.1 first identifies episteme P by:

<ClaimGraph, one already identified present EntityOfConcern, effective ReferenceScheme>

A.15.2 recognizes that same P as U.WorkPlan when its ClaimGraph substantively declares coordination of work intended as future from the planning perspective recorded in P, over one horizon through at least one PlanItem and, when it contains several items, their plan-content organization. The intended-performance designator may denote one proposed future performance, a named repeated-work family, or one bounded proposed group. It remains claim content: planning it neither asserts the existence of a dated Work occurrence nor makes a merely possible performance into C.2.1’s already identified EntityOfConcern. The unchanged P retains its original intended-coordination claims after performance, cancellation or passage of that horizon. Those claims provide the baseline for a later fulfilment or variance comparison. A revised intention changes the claim content; a later report of actual performance has its own claims.

The present EntityOfConcern is the already identified existing entity that the plan’s claims are about: for example, a system, asset, or promise-content episteme for which work is being coordinated. When the plan claims are expressly about their own coordination commitments, C.2.1’s reflexive option permits P itself. The ClaimGraph may also designate other independently governed entities as participants. When the asserted subject is a joint entity, identify that entity independently. Split the ClaimGraph only when it combines independent subjects in a way that makes the selected EntityOfConcern untruthful or breaks the intended identity or comparison use; do not split merely because one predicate connects several participants.

The stable positive membership condition is substantive intended-work content. At least one PlanItem must name its intended-performance designator, intended method or method family, planned window or entry condition, intended performer System or local system-role-kind condition, and enough constraints, resources, dependencies, commitments, targets, or baseline to make one coordination decision—for example, reserve a machine, order two items, staff a window, or set the target to be checked later. Membership depends on those intended-work claims, not on the carrier or presentation format.

The dependent kind supplies no second identity rule. Changing ClaimGraph content, the present EntityOfConcern, or the effective ReferenceScheme identifies another episteme under C.2.1. An explicit EpistemeEditionRelation may preserve historical continuity only when its own predicate obtains. Changing only a file path, carrier, layout, publication occurrence, ticket key, or version label leaves identity unchanged when the three C.2.1 discriminators are preserved.

The choices in §4.2 are intended-work content. Claims about actual occurrences, participants and effects retain their separate grounds under §9.

Distinction (memory aid): Method = how in principle. MethodDescription = claims about how the Method is done. WorkPlan = when, by whom in intent, under which constraints. Work = what was actually performed on this occasion.

A.15.2:4.2 - PlanItem content

A PlanItem is a declaration-local content component in one U.WorkPlan. Its designator is interpreted inside that plan episteme. A receiving episteme may refer to this content component.

Choose only the claims the team will use to coordinate the intended work. The list is an open recognition palette, not a record schema or a kind defined by enumeration. When one row mentions a neighboring relation, state its own participants and predicate rather than treating the row or reference as proof that it obtains:

  1. Target Method and description use — identify the Method intended for enactment. When a plan claim relies on a MethodDescription, cite that episteme and the instruction, constraint or justification it supplies. A.3.2 requires the admitted Method as its exact EntityOfConcern and substantive way-of-doing claims. Call it a later edition only when the C.2.1 EpistemeEditionRelation obtains. The plan describes intended Work that is to enact the Method, with a System as its intended performer; the MethodDescription supplies the claims used in planning. These intended relations do not establish an actual Work occurrence.
  2. Planned window or entry condition — earliest start, latest finish, timebox, recurrence, blackout period, or another exact intended temporal condition.
  3. Intended performer and system-role-kind conditions — an intended performer U.System designator, the local system-role kind under which that performer is expected to qualify, its admission conditions, and, only when it already obtains, an assignment occurrence whose species is declared under U.SystemRoleAssignment and that is expected to cover later Work. A proposed holder-and-kind pair is not an actual assignment.
  4. Capability requirement — an exact A.2.2 threshold or CapabilityFitCondition needed for planned work entry. Cite an existing capability claim only when the plan relies on it. The plan establishes neither the holder’s actual ability nor fit for the later work interval.
  5. Resource budgets and reservations — intended energy, materials, machine windows, money, and reservation claims. A planned budget is neither a performed resource-use fact nor a B.1.6 aggregate ledger result.
  6. Dependencies and commitments — state the source item or commitment, the affected target item, and the condition that blocks, orders, overlaps, or excludes the planned work. A cited gate, approval, source-currentness, or promise claim keeps its own predicate; the citation establishes neither gate passage, approval, promise fulfilment, nor world-side ordering.
  7. Acceptance targets — name the criterion and target value or window that a later evaluation will test. The target is not the evaluation or acceptance verdict.
  8. Location, affected-subject, and asset constraints — where a proposed performance is intended to occur and which existing referent it is intended to concern, without asserting actual participation or change.
  9. Desired planned bindings — use A.15.3 only when the plan fills one participant, argument, or result member already declared by A.6.5, A.6.1, or another pattern that states both the member meaning and its later actual-use predicate. A.15.2/A.15.3 state the intended choice; the declaration states what later counts as actual use. Without that member, keep an ordinary plan choice when typed reuse is unnecessary, or return missing-governor when it is necessary.
  10. Expected effect, result, or delivery target — write the planned sentence with its intended subject and target: for example, the machine state sought, measurement window to be met, entity to be produced, or publication or delivery to be completed. Use the pattern that defines that effect. The broad words output, result, outcome, deliverable, or handoff do not name one plan field or universal kind.

A method description may describe generic participant meanings and intended effects, but it supplies no planned filling by itself. Record the desired choice or expected effect in the plan.

Keep the baseline identifiable. Record later fulfilment or variance claims separately from the plan being compared. A new plan may use actual observations as its basis, but changing its identity-bearing content identifies another episteme under C.2.1. Keep step logic and solver details in the applicable Method or representation.

A.15.2:4.3 - Distinctions for schedule, process, and workflow wording

If you say…In FPF it is…Why
“The schedule for tomorrow’s surgeries”U.WorkPlanEpisteme declaring intended cases, windows, intended performer Systems and local system-role-kind conditions, resources, dependencies, and targets without asserting occurrence.
“The workflow for appendectomy”a U.Method, or its U.MethodDescription when A.3.2 admission holdsDistinguish the way of doing from the episteme describing that admitted Method; neither supplies a schedule merely by form.
“The process already ran at 10:00”a Work occurrence only when A.15.1 grounds that dated individualRecover the performer’s A.13 core, independent occurrence history, enacted Method, temporal extent and containing-System relation. Add F.6 only for precise assignment-bound attribution and other result or resource claims only when needed.
“The thermodynamic trajectory”a trajectory representation or model; U.Dynamics only when the episteme meets A.3.3’s state-space and transition-law criterion; add changed-subject and U.Transformation claims only when their direct predicates obtainA trajectory expression is neither plan nor performed work by form.
“The plan assigns Dr. Lee”U.WorkPlan carrying a claim about the System intended to perform the Work and its local system-role-kind condition; cite an assignment occurrence and its declared species only when that assignment already existsThe plan does not create or validate an assignment for the performed Work interval.
“The budget for Shift-B”a planned resource-budget claim inside a U.WorkPlan when the enclosing episteme meets §4.1The plan states the budget. A.15.1 identifies later Work, the applicable resource-use predicate states what it consumed, and B.1.6 aggregates those facts only when a ledger or allocation result is needed.

Schedule-word guard. Schedule-like words do not determine the kind by themselves. Use U.WorkPlan only when the text states intended Work, a horizon or window, the System intended to perform the Work or its local system-role-kind conditions, and enough constraints, resources, dependencies, targets, or baseline to coordinate it. Otherwise use the pattern for the claim made.

A.15.2:4.4 - Plan mereology (composition of plans ≠ composition of methods or work occurrences)

Keep these three relations distinct:

  • Method composition admits a composite U.Method only when A.3.1/B.1.5 supplies the submethods, whole-forming relations, and whole-level commitments.
  • Work organization starts with A.15.1 work-part relations. Temporal overlap is an independently governed interval fact under C.27.TA, and coordination is a separate direct claim when it obtains. Shared parentage or overlap creates neither a ConcurrentPartOf_work primitive nor coordination.
  • Plan-content organization arranges declaration-local PlanItem components inside the ClaimGraph for coordination. It is epistemic organization, not world-side work or method mereology.

Common plan-content claim families include:

  • precedence or dependency constraints naming source and target item designators, start or finish conditions, and any prerequisite or gate condition;
  • overlap or exclusivity constraints naming the scheduling policy and the windows it permits or excludes;
  • model-refinement claims comparing two plan models for one coordination inquiry about the same intended work under B.5.MR; and
  • alternative claims stating the alternatives and the independently governed condition used to choose among them.

For that comparison, recover what each plan model permits and requires. Establish how every completion of the proposed refined model is read against the earlier model. At least one completion must exist, and every completion must satisfy the earlier assertions under that reading. Strict refinement also excludes an earlier admitted answer; abstraction uses the converse comparison and checks the conclusion still needed. A tighter window, constraint, target or budget can supply the restriction. Check it together with the other assertions. C.2.1 identifies each plan episteme and any edition continuity separately; §4.5 tests later Work against a plan.

Start with the readable plan constraint—for example, “item B starts only after clearance claim C for item A is current.” Keep that claim inside the WorkPlan ClaimGraph and name the two item designators, the condition, scope, and qualification. Display order alone establishes no world-side ordering or Work parthood. When the receiving use needs a stable parameterized plan rule, A.6.RCD may supply a predicate-definition episteme. Open relation-kind admission only when a named receiver must distinguish occurrences of that relation; then E.24/E.24.UK and the standalone direct pattern must supply obtaining and identity before A.6.REL is used. If the rule, its source predicates, or occurrence identity cannot be stated, return the corresponding A.6.RCD blocker rather than minting Precedes_pl, MutuallyExclusive_pl, Refines_pl, or another pseudo-kind here.

Didactic rule: A PlanItem does not force an identical work shape. A later one-case comparison with an independently identified Work occurrence remains a separate local plan-use assertion unless an admitted direct relation has been supplied.

A.15.2:4.5 - How WorkPlan meets Work

Ask one concrete question first: “Did Work W satisfy plan item I under policy F?” Identify W under A.15.1, then name WorkPlan episteme P, declaration-local item I, and policy episteme F. Check only the independently obtaining facts that F requires—for example, enacted Method, required assignments, and Work extent in the hospital case below. Put the answer in a separate C.2.1 assertion whose EntityOfConcern is P. The assertion neither changes P nor admits a WorkPlanFulfilmentRelation kind.

A positive answer requires every fact in F’s positive criterion. State a negative answer only when F contains an applicable failure or closure criterion and the case facts satisfy it. Missing occurrence facts return missing-information; an absent predicate or policy authority returns missing-governor. Neither stop is a negative claim. The assertion keeps W, P, I, F, polarity, and the supporting facts explicit; a matching label, window, ticket, record link, or policy name alone does not establish the facts required by F. Several Work occurrences may satisfy different parts of I, or one consolidated Work may satisfy several items, only when F states that mapping. Unplanned Work remains valid Work; a separate assertion may classify it as unplanned for one named variance or improvement use.

If a receiving use needs a stable parameterized fulfilment definition but consumes no relation-occurrence identity, use A.6.RCD disposition 3 to publish one predicate-definition episteme with one truthful EntityOfConcern, participant meanings, derivation, applicability, polarity, dependencies, and currentness; it is not a RelationSignature or relation kind. Only when a named receiver also needs distinguishable fulfilment occurrences may A.6.RCD return a relation-kind candidate for E.24/E.24.UK admission, a standalone direct subject settlement, and later A.6.REL discipline. Until those requirements are met, preserve the local assertion and reusable predicate semantics, and return the A.6.RCD blocker for the occurrence-facing use.

A variance question is handled in the same economy. Use a separate local comparison assertion unless the measurement, evaluation, acceptance, resource, or temporal pattern already states the exact comparison. Name one planned value in P and I, one independently established actual value, the comparison method, scale, qualification window, and result. Do not make variance an intrinsic field of a Work occurrence, enter it into P’s identity-bearing claim content, or rewrite the plan. Common comparison questions include:

  • schedule variance: actual Work extent against the planned window, using the exact temporal comparison and any B.1.4 aggregate needed by the receiving KPI;
  • resource or cost variance: A.15.1 performed resource-use facts or a B.1.6 aggregate result against the planned budget;
  • method variance: actual enactsMethod against the intended method, including a substitution claim when the comparison asserts substitution;
  • description-selection variance: the method-description episteme cited by a named assertion about a Work occurrence or by a separately governed instruction-use claim, compared with the description reference planned earlier; call either object an edition only when the C.2.1 EpistemeEditionRelation predicate obtains, and do not treat that episteme as enacted;
  • acceptance-target variance: a separately governed measurement, evaluation, or acceptance verdict against the planned target; and
  • assignment variance: for every actual performer, compare the obtaining assignment occurrence used by F.6 with the corresponding intended performer and local system-role-kind conditions in the plan. Check the occurrence’s directly declared species, actual holder System, assigned local system-role-kind value, every additional participant that the plan constrains, and the part of its covering interval constrained by the plan. Report a species mismatch when the actual occurrence instantiates a different assignment species; when the species matches, report an occurrence-value mismatch only for a holder, assigned-kind value, plan-relevant additional participant, or interval value that differs from the plan. Do not collapse either comparison into a label match.

Manager’s view: A usable coordination plan can stop before later comparison. If a receiving question needs fulfilment or variance, recover the relevant baseline and policy under §4.5; missing comparison grounds limit that use rather than cancelling the plan’s membership.

A.15.2:5 - What a good WorkPlan states (review checklist)

Apply the items needed by the coordination or comparison claim; this is a recognition palette, not a required full schema:

  1. Present EntityOfConcern, horizon, and cadence (for example, the current service system and “W36 surgeries” or “daily ETL”), with possible future performances kept as plan-content designators.
  2. PlanItem content components with intended-performance designator, target Method, the selected method-description episteme when one plan claim relies on it, planned windows, and dependencies.
  3. Intended performer System and local system-role-kind conditions, any reference to an existing assignment occurrence and its declared species, and the A.2.2 capability threshold or fit condition; a proposed holder-and-kind pair or threshold is not an assignment or fit result.
  4. Safety envelopes, constraints, and other admissibility conditions for planned work.
  5. Resource budgets and reservation claims on assets.
  6. Acceptance targets with their direct criteria and intended qualification windows.
  7. Cross-context interpretation boundary: when a proposed use depends on correspondence between local senses with different interpretation bases, pin both effective reference schemes and resolve the two F.17 SchemeSenseCell values. F.9 says only whether their Bridge obtains. A separate C.2.1 claim says whether this reuse is acceptable in this direction, under this correspondence rule and tolerated loss; A.10 governs ordinary evidence reliance and B.3 governs assurance-bearing reliance. A negative use claim leaves the Bridge true but stops the reuse; a non-passing reliance result stops or narrows it. Establish any value conversion, target comparison, commitment, acceptance, verdict reuse, plan coordination, or Work claim separately under the pattern that defines it.
  8. Baseline when the receiving comparison needs one. Keep the earlier plan identifiable. Claim edition continuity only when EpistemeEditionRelation obtains, and use a change note when the attributed difference needs explanation. If continuity is unestablished, leave it unresolved; a first plan has no earlier plan relation, and a negative continuity claim needs its own basis.
  9. Policy pointers to A.15.1 work continuity, B.1.4 temporal aggregation, B.1.6 resource aggregation, and any local comparison policy needed by the receiving KPI.
  10. Exception question stating how ad hoc or emergency Work will be handled by a local plan-use assertion; use one reusable predicate-definition episteme when the receiving use needs a stable definition, and require an admitted direct relation kind before claiming fulfilment or exception occurrences.

A.15.2:6 - Archetypal grounding (parallel domains)

These constructed cases stipulate their project facts. The hospital case follows one plan item through a later comparison; the other cases show different constraints and reuse limits.

A.15.2:6.1 - Hospital OR day plan (shift rota + cases)

  • WorkPlan: OR_DayPlan_2025-08-12-E3 : U.WorkPlan is one C.2.1 episteme. Its present EntityOfConcern is existing system OR-Service-System-12 : U.System; its effective reference scheme is HospitalORPlanningScheme-E4; its horizon is 2025-08-12T00:00:00+03:00/2025-08-13T00:00:00+03:00. Proposed case performances remain ClaimGraph designators and are not dated Work occurrences.
  • One PlanItem: Case_1_Appendectomy coordinates proposed performance PlannedAppendectomy-Case1 through the following content.
PlanItem concernFilled value
target methodLaparoscopicAppendectomyMethod-E2 : U.Method
planned window2025-08-12T09:00:00+03:00/2025-08-12T10:30:00+03:00
intended performer and system-role-kind conditionsone performer System satisfying SurgeonSystemRole and AppendectomyLeadCapability-v3; one performer System satisfying AnesthetistSystemRole and ORAnesthesiaCapability-v2; these are intended conditions, not system-role assignments
budget and reservations90 minutes of OR-3, one SterileKit-A17, and consumables budget ORCase1-Consumables-B3
dependencypositive PreOpClearance-Case1-E2 claim must be current before the planned window starts
acceptance targetprocedureCompleteBy10:30, compared under C.27.TA against the exact Work extent after Work occurs
baselineC.2.1 episteme OR-DayBaseline-2025-08-05-E1
  • Later Work: The case independently admits DrK and DrM as Systems. Under the local A.13 criteria, DrK regulates the operative action to the procedure target and DrM maintains the declared anesthesia conditions under relevant perturbations; the stipulated observations support these classifications for the surgery scope and window. Under the directly declared assignment species, the stipulated case facts establish obtaining RA-Surgeon-DrK-2025-08-12 and RA-Anesthetist-DrM-2025-08-12 occurrences with those Systems as holders and the intended local kinds, covering that window. The observed performance history and the local containing-System predicate place the complete occurrence within OR-Service-System-12. For this constructed case, also assume that all six common construction components under A.1:4.2 have been independently established for AppendectomyWork-2025-08-12-Case1.

    These premises and the enactment and extent below independently admit AppendectomyWork-2025-08-12-Case1 : U.Work under A.15.1, with workContinuityPolicyRef = SingleProcedureFromAnesthesiaStartToHandover-E1, temporal extent 2025-08-12T09:04:00+03:00/2025-08-12T10:21:00+03:00, and enactsMethod to LaparoscopicAppendectomyMethod-E2.

    Because the named one-case policy expressly consumes both assignment-bound attributions, F.6 afterward establishes performedUnderAssignment for RA-Surgeon-DrK-2025-08-12 and RA-Anesthetist-DrM-2025-08-12 through those same assignments. The named policy tests the within-window claim qualified under C.27.TA. Either failed F.6 relation alone would prevent this attribution-dependent fulfilment conclusion while preserving independent Work admission. If the same finding questions an actual admission premise, recheck that premise and its dependents under A.15.1.

  • Named one-case policy: ORCase1FulfilmentPolicy-E2 is one C.2.1 episteme about plan episteme OR_DayPlan_2025-08-12-E3, interpreted under HospitalORPlanningScheme-E4. Its ClaimGraph is limited to item Case_1_Appendectomy and states positive polarity only when the identified Work enacts the target Method, both required performedUnderAssignment relations obtain, and its extent lies inside the planned window. It uses only those four facts for this local conclusion, does not travel to another plan episteme, and admits no fulfilment relation kind.

  • Visible result: C.2.1 assertion episteme OR-DayPlan-Case1-Fulfilment-Assertion-E1 has OR_DayPlan_2025-08-12-E3 as its EntityOfConcern; its ClaimGraph names AppendectomyWork-2025-08-12-Case1, item Case_1_Appendectomy, policy ORCase1FulfilmentPolicy-E2, the four supporting facts, and positive polarity. The result says that this Work satisfies this plan item under that policy. It does not rewrite the plan and does not assert a universal relation.

  • Nearest false shortcut: a theatre log row carrying key Case_1_Appendectomy and start time 09:04 establishes neither performedUnderAssignment nor enactsMethod. Without those independently obtaining facts the local conclusion returns missing-information; matching labels and times produce neither negative polarity nor fulfilment.

  • Edition boundary: this is the first plan episteme selected for the day. Changing its ClaimGraph identifies another episteme; edition continuity with the earlier plan requires its own C.2.1 basis. If that relation is unestablished, continuity remains unresolved rather than becoming negative. A reused label or Rev-4 note supplies no such basis. A later fulfilment policy must identify whichever plan it judges.

A.15.2:6.2 - Fab maintenance weekend (asset reservations)

  • WorkPlan: Fab_Maintenance_W36 is interpreted under FabMaintenancePlanningScheme-E3, has horizon [2025-09-06T00:00Z, 2025-09-08T00:00Z), and concerns already identified Fab-Production-System-4 : U.System. Tool_42 and Tool_13 remain assets named by the PlanItems; they are not an unproved joint EntityOfConcern.
  • PlanItem content: Tool_42 chamber clean under ChamberCleanMethod-E2; Tool_13 calibration under ToolCalibrationMethod-E1; the ClaimGraph carries an exclusivity constraint with production windows. The scheduling policy, per-item windows and reserved quantities remain case inputs for this abbreviated illustration.
  • Reservations: nitrogen, DI water, metrology window.
  • Later local assertion: The chamber-cleaning Work occurrence is identified independently as an individual admitted under U.Work. FabChamberCleanPlanUsePolicy-E1 asks whether that Work enacted ChamberCleanMethod-E2, stayed inside the planned window, and kept nitrogen use within the reserved amount. A.15.1 supplies the Work and enactment facts; C.27.TA qualifies the within-window claim; B.1.6 supplies the resource aggregate used in the budget comparison. For this illustration, assume that the three policy conditions all obtain; a separate C.2.1 assertion about the plan then states positive fulfilment. Early completion and nitrogen underrun additionally require the corresponding strict comparisons. A shared item label or reservation row supplies none of those facts.

A.15.2:6.3 - Data-center rollout (multi-context plan)

  • WorkPlan: DC_Rollout_Phase-2 is interpreted under DCOperationsPlanningScheme-E5, has horizon [2025-09-01T00:00Z, 2025-09-15T00:00Z), and concerns already identified Service-A-Operations-System : U.System. The Security Audit scheme remains a separate interpretation source used only through the branch below.
  • Interpretation boundary: Operations uses DCOperationsPlanningScheme-E5; Security Audit uses SecurityAuditScheme-E4. Their acceptance criteria remain separate; apply the branch in checklist item 7 before proposing any cross-context reuse.
  • Bridge premise: F.17 cells OperationsReadyCell-E3 and SecurityAuditPassedCell-E2 participate in F.9 Bridge OpsAuditReadinessOverlapBridge-E1 under OpsAuditPartialOverlapProfile-E1. The Bridge obtains as partial-overlap: both senses exclude a known blocking security defect, while Operations readiness also requires rollback rehearsal and live monitoring and the audit sense applies its own security criteria.
  • Rejected verdict transfer: C.2.1 claim AuditPassAsOperationsReadyUse-E1 proposes copying GateDecision=pass from A.21 gate SecurityAuditGate-E2 into an A.15.5 work-entry readiness result, from the audit cell to the Operations cell, by identity transfer and with zero tolerance for omitted readiness conditions. The claim is negative because the two senses do not align on rollback rehearsal or monitoring readiness. A.10 evidence-provenance path OpsAuditTransferEvidencePath-E1 has RelianceDisposition=pass for that negative claim, so the team retains the A.21 audit decision and evaluates Operations readiness separately under A.15.5. The obtaining Bridge remains true. A narrower plan use may cite the audit decision as one readiness input; it still cannot transfer the verdict.
  • PlanItem content: Deploy Service A, Pen-test A; dependency and window claims name their predicates and conditions inside the plan ClaimGraph.
  • Later local assertions: Deployment and audit Work occurrences are identified independently as individuals admitted under U.Work. Separate operations and audit evaluations apply their own targets and produce separately governed verdicts; plan-use assertions state local fulfilment and per-context comparison without adding those actual facts to the plan content or creating one cross-context fulfilment relation.

A.15.2:7 - Scope Declaration and Rationale

  • Applicability: Use the same intended-work test for coordination, budgeting, architecture planning, teaching examples, and source or evidence questions.
  • Scope declaration: Domain-general where a system is coordinating possible future performed work. A tide table, weather forecast, simulation schedule, or predicted natural trajectory is not a WorkPlan unless its claim content also coordinates a system’s intended Work. Interpret the plan through its effective ReferenceScheme and, when the use needs a bounded claim set or model-applicability question, the exact U.ClaimScope and ModelApplicabilityRelation governed by A.2.6 and A.1.1. An already identified BoundedModelUseStructure enters only when a separate receiving claim or use relation states how that structure changes this plan use and its direct predicate obtains; otherwise omit the structure rather than inventing a context field. Ordinary project, domain, or context wording stays Plain and creates no container or identity field. For cross-context sense reuse, apply checklist item 7.
  • Rationale: A WorkPlan is an episteme that systems can use to coordinate intended Methods, intended performer Systems and local system-role-kind conditions, and possible future Work. The plan retains those intended choices for coordination and, when needed, later comparison.

A.15.2:7a - Conformance Checklist

IDRequirementPractical test
CC-A15.2-1C.2.1 ClaimGraph, one already identified present EntityOfConcern, and effective ReferenceScheme identify the episteme; A.15.2 adds one stable intended-work membership condition and no second identity.A possible future performance or PlanItem designator is not used as an existing EntityOfConcern merely because it appears in the plan. Carrier, layout, publication, ticket key, and version label can change without reidentification when the three discriminators remain fixed.
CC-A15.2-2A conforming U.WorkPlan makes substantive claims for coordinating possible future performed Work over a horizon through at least one PlanItem.The plan states an intended-performance designator, Method, window or entry condition, the System intended to perform the Work or its local system-role-kind condition, and the constraints, resources, dependencies, commitments, targets, or baseline needed by its receiving use without asserting that a Work occurrence exists.
CC-A15.2-3Every PlanItem remains declaration-local plan content and names the possible future performance and claims it coordinates.Resolve the designator to the content component in the identified WorkPlan; establish a claimed occurrence or participant separately under its own predicate.
CC-A15.2-4Claims about a System intended to perform the Work, its local system-role-kind conditions, and A.2.2 capability requirements remain planned. Cite an assignment occurrence and its declared species only when that assignment already obtains; the plan supplies no capability-fit result.Publishing a proposed holder-and-kind pair or threshold creates neither assignment, capability, nor fit for the later Work interval.
CC-A15.2-5A desired participant, argument, or result uses A.15.3 only after one declaration member supplies its reusable meaning and later actual-use predicate.The plan states the intended choice; it does not turn method-description wording, a broad field label, a compatible ValueKind, or a planned reference into participation. Keep ordinary plan content when typed reuse is unnecessary; otherwise return missing-governor.
CC-A15.2-6An expected change, result, entity, delivery, acceptance, or outcome names its intended subject and target and remains a plan claim.No output, result, outcome, deliverable, or handoff field is treated as a universal kind or as proof that the object exists or the effect occurred.
CC-A15.2-7PlanItem organization names local predicates and conditions but does not admit relation kinds or force the same shape on performed Work.Graph order and spellings such as Precedes_pl or MutuallyExclusive_pl establish no reusable relation or world-side fact.
CC-A15.2-8A one-case fulfilment answer is A.6.RCD disposition 2: a separate assertion about plan episteme P, item I, Work W, and policy F. F names the independently obtaining Work facts and the positive or negative criterion used.Shared labels or links cannot close the claim. Negative polarity needs an applicable explicit criterion and case facts; unavailable facts return missing-information, absent predicate or policy authority returns missing-governor. Repeated semantics may use a predicate-definition episteme; only an occurrence-facing receiver can open relation-kind admission.
CC-A15.2-9A variance question compares exact planned and actual values through one local comparison assertion or the measurement, temporal, resource, evaluation, or acceptance pattern that defines the comparison.Comparison method, scale, qualification window, and result are explicit; no universal variance relation or intrinsic Work field is inferred.
CC-A15.2-10When cross-context plan use depends on semantic correspondence between differing local interpretation bases, apply the separate Bridge/use/reliance branch in checklist item 7.F.9 is cited only for an exact SchemeSenseCell Bridge; the separate C.2.1 use claim and A.10 or B.3 reliance result decide whether the attempted use proceeds, narrows, or stops. Run target conversion, commitment, acceptance, and verdict reuse under the pattern that defines each claim; the Bridge establishes none of them.
CC-A15.2-11Evidence, assurance, gate, launch-value, and result-measurement claims stay in the patterns that govern those relations.Evidence references and requests in the plan do not by themselves establish the cited support or requested result. An A.15.5 readiness result and GateDecision=pass alone establish neither an A.2.8.PER permission relation nor a Work occurrence.
CC-A15.2-12Planned preparation tasks may appear in the WorkPlan, but A.15.5 governs the local readiness criterion and result.The plan says what should be prepared. A.15.5 judges readiness for work entry from the facts required by its selected criterion.

A.15.2:7b - Common Anti-Patterns and How to Avoid Them

  • Future-work-as-entity. Do not use a possible future performance or PlanItem designator as C.2.1’s already identified EntityOfConcern or as a dated Work occurrence; keep it in plan claim content until an exact direct entity or occurrence exists.
  • Plan-as-actual. Do not treat a Gantt bar, Kanban ticket, shift rota, or calendar booking as performed work; identify or cite a Work occurrence admitted under U.Work only when A.15.1’s occurrence basis is present.
  • Workflow-as-schedule. Do not infer a plan from a MethodDescription or flowchart; recognize a U.WorkPlan only when the claims state a present subject, intended-performance designator, horizon, window, constraints, the System intended to perform the Work or its local system-role-kind conditions, and any baseline needed for the current coordination decision.
  • Assignment-or-capability-by-plan. Do not treat an intended performer System, local system-role kind, proposed holder-and-kind pair, threshold, or capability reference as an obtaining U.SystemRoleAssignment, actual holder ability, or fit result for later Work; apply A.2.1/A.2.2 at the exact interval and use.
  • Budget-as-cost. Do not book planned budgets as performed resource use; establish performed facts on A.15.1 Work and any aggregate ledger or allocation under B.1.6.
  • Plan-shape overreach. Do not force performed Work to match plan decomposition, infer non-fulfilment from a missing link or unavailable facts, or mint a fulfilment relation from a local comparison. Stop at a positive or governed-negative local compound assertion when it suffices; use a predicate-definition episteme when a stable definition is needed without occurrence identity; open relation-kind admission only for a named occurrence-facing need.
  • Context-bridge overreach. Do not bridge contexts as wholes or use F.9 to convert planned values, commitments, criteria, or verdicts. F.9 relates exact SchemeSenseCell values; apply checklist item 7 when a proposed plan use depends on that cross-context semantic correspondence.
  • Evidence-note-as-claim. Do not infer that referenced support is available or that a requested result was obtained merely because the plan contains a reference or request.
  • Readiness-or-gate-as-permission. A ready result reports entry conditions and an A.21 gate decision governs its declared crossing; neither institutes permission or performed Work. Recover an exact current A.2.8.PER grant when permission is required.
  • Description-as-planned-filling. Do not turn a method-description word such as input or output into a planned slot. Use A.15.3 only when one declaration member already states what the value means and what later counts as actual use. Otherwise keep the choice as ordinary plan content or return missing-governor when typed reuse is required.
  • Expected-as-actual. Do not treat a desired filling, expected effect, output, result, outcome, deliverable, or handoff as an actual participant, change, returned value, produced entity, delivery, acceptance, or downstream effect.

A.15.2:7c - Consequences

BenefitTrade-off and mitigation
Plans become inspectable without being confused with performed work.More explicit claims; mitigate by using compact PlanItem content for ordinary coordination.
Variance becomes meaningful because planned baseline and performed work stay separate.Requires discipline around baselines; keep the plan episteme and baseline visible, and name an edition relation only when its predicate obtains.
Cross-context reuse exposes the correspondence and conditions on which the proposed transfer depends.Apply checklist item 7 to the changed sense or value being reused; establish its required correspondence, use claim and reliance basis.
P2W carry-through can supply intended-work coordination.Use A.15.1, A.15.3, A.15.4, A.15.5, A.10, B.3, A.20, or A.21 only when the source makes the corresponding performed-work, planned-filling, appearance-based reliance, readiness, evidence, assurance, internal constraint, or gate claim.

A.15.2:7d - SoTA Alignment

Source tradition and contributionFPF useShortcut rejected
ISO 21502:2020 project-management guidance and PMBOK Guide Eighth Edition (2025), cited for planning practiceA plan declares its horizon and intended Method or Method family, adding only the baseline, dependencies, resource expectations and acceptance targets needed for current coordination. Compare planned and performed values when the receiving question needs that result.Treating a schedule, ticket, or baseline as evidence that the Work already occurred.
ISO 55000:2024 asset-management practiceAsset reservations, maintenance windows, lifecycle objectives, risk, and value expectations belong in planning until A.15.1 identifies the performed Work and the applicable change and resource-use predicates are satisfied.Treating planned asset availability or reserved capacity as actual asset intervention or actual resource consumption.
ISO 9001:2015 with Amendment 1:2024, a quality-planning sourcePreserve planned quality objectives, acceptance targets and performance-evaluation criteria so actual results can be compared with that baseline.Rewriting the plan after the fact so that quality, cost or schedule variance disappears.
Mature adaptive-work representation practice such as OMG CMMN 1.1 (2016)Weakly structured or ad hoc Work can still be compared with identified plan content through a local assertion, or through a direct relation when one is defined.Forcing every emergency, adaptive, or consolidated Work occurrence into the original plan shape; or minting a universal fulfilment relation from one comparison.

A.15.2:7e - Relations

  • Builds on: C.2.1 for episteme identity and local assertion identity; A.15 for System-Role-Method-Work alignment; A.15.1 for independently identified performed Work occurrences admitted under U.Work; A.2.1 for direct U.SystemRoleAssignment species; A.2.2 for qualified holder-ability claims, thresholds and fit conditions; A.3.1 for U.Method; and A.3.2 for U.MethodDescription.
  • Coordinates with: B.5.MR for refinement and abstraction comparisons between plan models; A.15.3 for planned filling against governed declarations; A.6.1 for operation argument and result declarations; A.6.5 for RelationSignature participant declarations; A.6.RCD for the existing-direct/local-compound/reusable-predicate/relation-kind economy; E.24/E.24.UK for any later kind admission; A.6.REL only after an admitted direct or derived relation needs occurrence discipline; A.15.4 for work-relevant appearance-based reliance repair; A.15.5 for work-entry readiness; C.27.TA for direct temporal-aspect claims; B.1.4 for temporal aggregation; B.1.6 for performed-resource aggregation; A.10 for accounts of independently established evidence-provenance relations; B.3 for assurance; A.20 for internal constraint results and A.21 for gate decisions; C.32.P2S for architecturing-flow references to intended work; E.17 for publication-use questions; and F.9 only for cross-context SchemeSenseCell correspondence, with any proposed use and reliance routed through checklist item 7.
  • Used by: P2W carry-through when accepted problem-side content must guide work planning, and P2S carry-through when architecture-selected structures require intended-work epistemes. Both uses keep present plan subject, possible future performance, readiness, performed Work, actual use, evidence, gate, comparison, result, and downstream effect separately governed.

A.15.2:8 - P2W WorkPlanning use

When the next P2W question concerns planned work, use the accepted problem-side claim to choose or qualify the relevant PlanItem content. One U.WorkPlan retains its present EntityOfConcern and states possible future performed Work over a horizon through PlanItem content: intended-performance designators, windows, Methods, intended performer Systems and local system-role-kind conditions, capability requirements, constraints, budgets, dependencies, commitments, targets, evidence-reference notes, and source-currentness requests. If the plan chooses a value for a reusable declaration member, use A.15.3; if it states an expected effect, name the intended subject and target under the pattern that defines that effect.

When the P2W use also needs a readiness question, the WorkPlan may supply target PlanItems, planned preparation tasks, reservations, and planned baselines. A.15.5 supplies the exact readiness criterion and local result about that plan content; the criterion may consume current commitment, resource, work-in-progress or load, flow-policy, and launch-gate claims only through their separately governed values, boundaries, counting or threshold rules, and qualification windows.

If the same P2W source material also claims performed work, an actual launch value or participant, evidence, gate passage, result, measurement, publication use, appearance-based reliance repair, or refresh, state that claim outside the WorkPlan under the pattern that defines it.

A.15.2:9 - Launch-value and actual-use boundary for P2W

For P2W use, U.WorkPlan may state intended performer Systems and local system-role-kind conditions, planned values, A.15.3 fillings, constraints, reservations, commitments, and evidence-reference notes. A.15.5 may later publish one C.2.1 work-entry readiness result whose EntityOfConcern is this WorkPlan; its ClaimGraph may designate the relevant declaration-local PlanItem content used by the readiness criterion. An A.21 GateDecision separately selects, narrows, blocks, or passes its declared crossing under one current GateProfile. Neither result institutes permission.

When the entry criterion consumes permission material, keep the current A.2.8.PER values distinct. A GrantedPermissionRelation@Context occurrence is strong permission only for its exact beneficiary, action specification, U.ClaimScope, and validityWindow. A NonProhibitionFinding@Context reports only its frame-relative result for its evaluationWindow; it is not a grant. A PermissionNormConflictFinding@Context exposes overlap for its overlapWindow, and a current resolution result is usable only when the A.2.8.PER resolution predicate obtains and the result names its effectiveWindow; an unresolved conflict stops or degrades the proposed use. PermissionExerciseRelation@Context and NonViolationFinding@Context require already dated actual Work and therefore cannot be prospective proof that the intended performance may start. When the governing entry policy requires a grant, absence or unavailability of that exact current grant permits no authorization claim; readiness, gate passage, or non-prohibition cannot stand in for it.

At performed-work entry, identify one Work occurrence as an individual admitted under U.Work by A.15.1. For an actual relation participant or another world-side value, name the direct relation and its obtaining predicate. For an operation argument or returned result, use A.6.1 only after the application and its declaration-local binding predicate obtain.

A.15.2:10 - Lowering, repair, and refresh conditions

Lower a candidate U.WorkPlan claim when the reader cannot identify one present EntityOfConcern, the effective ReferenceScheme, the horizon, one substantive PlanItem, or its intended-performance designator well enough to coordinate the intended work. Keep other participants in the ClaimGraph. Split only when combining independent subjects makes the selected EntityOfConcern untruthful or breaks the intended identity or comparison use under C.2.1. Retain independently usable content and any other established claims; do not claim a conforming WorkPlan without its membership basis.

When intended-work content changes, revise the affected claims and reconsider dependent coordination or comparison uses. A change to ClaimGraph, present EntityOfConcern or effective reference scheme identifies another C.2.1 episteme. Test EpistemeEditionRelation separately: established continuity supports an edition claim, an established negative result excludes it, and absent evidence leaves it unresolved. A replacement use can be selected without settling historical continuity. A file, layout, ticket key or revision label alone establishes neither reidentification nor continuity.

Do not rewrite an independently identified Work occurrence when only the plan changes, and do not make a revised plan evidence that Work occurred. Repair an actual participant, resource use, change, result, production, delivery, acceptance, evidence, or downstream effect under the pattern that defines that claim. When a one-case local fulfilment or variance assertion is no longer enough, use A.6.RCD disposition 3 if a stable predicate definition is sufficient. Only when a named receiver needs distinguishable relation occurrences does kind admission open; if no truthful occurrence settlement or governing pattern is available, preserve the plan, local assertions, and reusable definition and return missing-governor for that stronger use.

Before a new reliance-bearing use, confirm that the selected plan and supporting claims remain applicable and sufficiently current. Reuse unchanged grounds and recheck affected dependencies. Where the use crosses local senses, apply checklist item 7 to the actual correspondence, proposed transfer and reliance question; establish any required value conversion or verdict use under its own predicate. Keep only intended-work claims in the plan being used; route a separate readiness, performance, evidence, gate or result claim to its governing pattern.

A.15.2:End

A.15.3 - SlotFillingsPlanItem: Plan a Value for an Existing Declaration Member

Tech-name: SlotFillingsPlanItem Plain-name: planned-filling plan item Short code: SFPI Type: WorkPlanning pattern Status: Stable Normativity: Normative unless explicitly marked informative

Builds on: C.2.1 episteme identity, A.15.2 U.WorkPlan, A.6.5 relation-declaration SlotSpec discipline, A.6.1 operation declarations, and the pattern that defines any other target member Used by: plans that must remember a chosen future relation participant, operation argument, expected result, or another value tied to an already declared member before work begins

At a glance. Use SlotFillingsPlanItem when a plan must preserve a choice before Work begins—for example, Robot_8_Ref as the planned holder for a future system-role assignment, with the assignment species named separately, or Pump_37_Ref as the planned candidate in a recognition operation. Point to the declaration member that already defines that position, and record the planned value and conditions. When a later question asks whether the choice was used, compare the established actual facts with the preserved plan. A field name, compatible type, Method phrase, form position, or plan label is not such a declaration.

Use this when. Use this pattern only when the choice points to a member already defined in a RelationSignature, an A.6.1 OperationDeclaration, or another declaration whose own pattern states both the member’s meaning and the rule for its later actual use. If the plan merely says use this method, reserve this resource, or meet this threshold without reusing such a member, keep ordinary A.15.2 plan content.

First useful object. One PlanItem inside an identified U.WorkPlan with at least one row that names the intended future use, declaration episteme, declaration-local member, planned value or designation, and the conditions under which that choice applies. The row follows the member’s designation rule and semantic cardinality; it does not redefine either.

Working use order.

  1. Identify the U.WorkPlan episteme and the future performance being planned. Keep the WorkPlan’s already identified present EntityOfConcern unchanged.
  2. Open the declaration that will be used later and choose one member it defines. Verify that the declaration’s own pattern states both what that member means and what must hold for actual use.
  3. Record the declaration episteme, its local member designator, and the planned value or designation. Do not substitute a description, record, form field, or matching label.
  4. Apply the member’s ValueKind, designation rule, and semantic cardinality. Add conditions and edition pins only when they can change which planned value is effective. State prohibitions, exclusions, and completeness as separate plan claims; omission is not prohibition.
  5. When a later question requires comparison, establish each claimed relation participant or operation binding independently. Identify a dated Work under A.15.1 only when that occurrence claim is needed. Compare actual with planned under the applicable policy, preserving the plan as the baseline.

Ordinary use. One row is enough: declaration episteme, member designator, planned value or designation, and the condition under which it is intended. The declaration’s own pattern must already define the member and its later actual-use rule.

Reliance-bearing use. Add concrete reference kinds, declaration or value episteme pins, alternative-selection conditions, target-declared cardinality, and a later comparison policy only when coordination, replay, audit, or work-entry preparation would change without them.

Stop condition. Finish with one of these results.

  1. The row resolves to an existing declaration member, and the planned value meets its ValueKind, designation, cardinality, and condition rules.
  2. No reusable member is needed, so the choice stays ordinary A.15.2 plan content.
  3. Typed reuse is needed but the member, its meaning, its actual-use rule, or the pattern that defines them is missing; return missing-governor for that planned use.
  4. Required planning information is missing or unresolved; name what must be recovered (§12b).

Do not invent a SlotSpec, wrapper declaration, generic field, or actual-use relation here.

What goes wrong if missed. A plan silently turns method prose or a schema field into a slot, treats type compatibility as planned or actual participation, treats omission or an empty filler as a prohibition, or later edits the baseline to match what happened.

What this buys. The team can later say what it intended, what actually happened, and whether the two differ, while the declaration, plan, work, and actual participation remain separate objects.

Not this pattern when. Use the declaration predicate and ClaimGraph located through A.6.5, A.6.1, or another declared-member source when defining the member; use A.15.2 for ordinary intended work without a planned filling; use A.15.1 for dated work; and use the applicable predicates for actual relation participation, operation bindings, methods, evidence, assurance, gates, acceptance, results, publication, or representation.

A.15.3:1 - Context

A WorkPlan may need more precision than use this Method or perform this task. An inspection plan may propose Robot_8_Ref for HolderSystemSlot in InspectionRobotSystemRoleAssignmentSignature; §5.1 shows the declaration needed for that typed choice. A recognition plan may need to remember that Pump_37_Ref is intended for the declaration-local candidate argument.

The declaration already states the participant, argument, or result meaning. The WorkPlan states the intention. A.15.3 joins them only as plan content.

A.15.3:2 - Problem

The following five failures motivate this boundary:

  1. Generic slot creation. Any description field named input, output, role, result, or parameter is treated as a SlotSpec.
  2. Declaration-family collapse. RelationSignature SlotSpecs and operation arguments or results are placed in one undifferentiated slot schema.
  3. Plan-as-actual inference. A planned value is treated as a participant in an obtaining relation or an actual operation binding.
  4. Description-as-declaration inference. A U.MethodDescription that mentions an input or effect is treated as if it declared a reusable participant locus.
  5. Baseline rewrite. Performed values are copied back into the plan, erasing substitution and variance.

A.15.3:3 - Forces

ForceDemand
Planning usefulnessPreserve the value or designation intended for later work.
Declaration localityRead each member only inside the cited declaration episteme and the pattern that defines it.
Family separationKeep RelationSignature participants distinct from A.6.1 operation arguments and results.
Intention versus actualityPermit useful planned claims without asserting work or participation.
Replay versus burdenPin only the editions and conditions that can change a later planning or comparison decision.

A.15.3:4 - Solution

A.15.3:4.0 - Planned-filling content and its identity

SlotFillingsPlanItem is a content form inside one U.WorkPlan ClaimGraph. Its item and row designators have meaning only within that WorkPlan episteme.

C.2.1 and A.15.2 identify the WorkPlan episteme. Changing an identity-bearing row creates different WorkPlan claim content and therefore another WorkPlan episteme. The two are historical editions only if an EpistemeEditionRelation predicate obtains between them; a shared file, label, carrier, or revision order does not supply that continuity. A reference may point to the WorkPlan and this content component, but it gives the PlanItem no separate identity or edition rule.

A planned-filling claim says: for this intended future performance and under these conditions, use this value or designation for this declared member. A.15.2 and A.15.3 state that intention. The member’s own pattern still defines what the participant, argument, or result means and what must hold for its later actual use.

A planned filling states the intended designation. Establish later relation participation or an operation binding under the selected member’s actual-use predicate. A later claim that the plan was fulfilled, missed, or changed belongs to A.15.2, A.6.RCD, or the applicable comparison pattern.

A planned-filling row states a positive intention. To prohibit or exclude a value, require its absence, or claim the list is complete, write a separate constraint or negative plan claim with its own applicability and polarity rule. Omission, an empty filler, and a negated reference do not express those claims.

A.15.3:4.1 - Use only members that a declaration already defines

Each row points to one member in one declaration episteme selected for the intended future use. First choose what is being planned; then open the pattern that defines that member and the rule for its actual use:

Planned choiceExisting declaration memberWhat remains defined elsewhere
participant in a future direct-relation claimone SlotSpec in one RelationSignature epistemethe relation pattern defines participant meaning and the obtaining predicate; A.6.5 defines the local SlotKind, ValueKind, and refMode; A.15.3 records only the planned designation
argument in a future operation applicationone ArgumentDeclaration in one A.6.1 OperationDeclarationA.6.1 and the cited mechanism define the argument meaning, ValueKind, designation rule, binding predicate, and cardinality; A.15.3 records only the planned value
expected result of a future operation applicationone ResultDeclaration in one A.6.1 OperationDeclarationA.6.1 and the cited mechanism define result meaning and the result-binding predicate; an expected value is not a returned value
another declared future useone declaration member whose own pattern defines both the member meaning and its actual-use predicatecite that pattern and declaration; if either definition is absent, return missing-governor instead of inventing a target

A U.MethodDescription is not a target merely because it mentions inputs, effects, parameters, bounds, or acceptance conditions. A table or form exposes an A.6.5 SlotSpec only when a cited RelationSignature contains that SlotSpec. Operation arguments and results stay in A.6.1 declarations; planning them does not turn them into A.6.5 SlotSpecs.

One item may contain several rows when they serve the same intended performance, baseline policy, and rule for revising the plan. Each row still resolves to its own declared member. Split the item when those three controls differ. The WorkPlan’s present EntityOfConcern remains its C.2.1 identity discriminator; a merely possible future performance does not replace it.

A.15.3:4.2 - State one planned-filling row

A conforming item contains or resolves these values:

SlotFillingsPlanItem:
  planItemDesignator
  workPlanRef
  intendedPerformanceDesignator
  plannedFillingRows:
    - rowDesignator
      targetDeclarationRef
      targetOperationDesignator?
      targetMemberDesignator
      targetMemberFamily:
        RelationSignatureSlotSpec |
        OperationArgumentDeclaration |
        OperationResultDeclaration |
        OtherDeclaredMember
      memberDefinitionPattern
      plannedValueOrDesignation
      planningConditions?
      declarationEditionPin?
      plannedValueEditionPin?
  baselinePolicyRef?
  laterComparisonPolicyRef?

This block represents WorkPlan claim content. targetMemberFamily is an open local dispatch vocabulary, not a public kind or closed inventory. For an operation argument or result, targetOperationDesignator is required so the member resolves inside the cited mechanism episteme; it stays absent for relation SlotSpecs. The memberDefinitionPattern field points to the pattern that defines the member and its actual-use predicate. A.15.3 still states only the plan’s intention.

Read the designation rule from the selected member instead of copying it into the plan. An A.6.5 member uses its refMode; an A.6.1 member uses its bindingDesignationRule. A ByRef value must use the concrete reference kind required there and resolve to the declared ValueKind. A generic Ref, SpecRef, stored token, or merely compatible value does not pass.

Use the selected member’s semantic cardinality. For a single-valued member, conditions and a resolution rule must make at most one planned value effective for one intended use. Alternatives need conditions and a rule that selects among them; row order supplies neither priority nor exclusivity. A multivalued member keeps the declaration’s set, sequence, multiset, repetition, and ordering semantics. If the declaration and cited policy do not decide the needed cardinality, return missing-governor for the member cardinality or selection policy.

Omitting a row leaves that planned filling unstated by this item. It does not say the value or later participant is absent. Prohibition, exclusion, required absence, and closed-world completeness remain separate plan claims with their own applicability and polarity rules.

intendedPerformanceDesignator names the future use being planned. The enclosing WorkPlan keeps its already identified present EntityOfConcern under C.2.1 and A.15.2.

Include a planning condition only when changing it would change whether the planned value applies or which value is selected. For example, state the readiness condition that a future use must satisfy; cite an independently established readiness result when the planned choice relies on that result. planningConditions names these conditions under their governing patterns.

When a baseline or comparison policy selects a planned value or judges a match, identify its kind, defining pattern, applicable episteme, conditions and reference scheme. A generic PolicyRef or shared label supplies no policy. Pin a declaration or value when another resolution could change the planned meaning, and make the reference and pin agree. Such a pin identifies the selected episteme; it asserts historical continuity only when the C.2.1 EpistemeEditionRelation is separately established.

A.15.3:4.3 - Plan a future relation participant

For a RelationSignature row:

  1. open the relation pattern and its obtaining predicate;
  2. choose the RelationSignature episteme the plan will use;
  3. choose its declaration-local SlotSpec and SlotKind;
  4. check the planned designation against the SlotSpec’s ValueKind and refMode;
  5. apply the declaration’s semantic cardinality and participant constraints; and
  6. record the row as a positive intended designation.

The row does not fill the SlotSpec. The SlotSpec remains reusable declaration content. The planned designation does not become the actual participant, and the direct relation does not obtain until its direct predicate is satisfied for independently identified participants.

A.15.3:4.4 - Plan a future operation argument or result

Open the cited A.6.1 mechanism episteme, choose its operationDesignator, then choose the argumentDesignator or resultDesignator. Apply that declaration’s ValueKind, bindingDesignationRule, binding predicate, semantic cardinality, and the plan’s stated conditions.

The row plans a value; it is not an application or binding. An actual argument binding needs an identified application whose argument-binding predicate holds. An actual result binding additionally needs that application to return the value under the declared result meaning. Type compatibility, an expected result, a method phrase, a ticket value, or a matching token establishes neither binding.

A.15.3:4.5 - Compare later use without changing the plan

When actual use is compared with the plan, establish the relation participation under its obtaining predicate or the operation argument/result binding under A.6.1. A plan row, matching label, type or value supplies none of those facts by itself. Add an independently admitted A.15.1 Work identity only when the comparison also consumes that dated occurrence claim.

If the team must state whether actual use matched the plan, name the comparison policy and the independently established actual facts. A one-off comparison may use A.6.RCD disposition 2 for a local compound assertion. Repeated parameterized comparisons may use disposition 3: keep a compound law subject-bounded when every reuse concerns one subject, or identify a reusable predicate-definition episteme when the rule is used across subjects. Do not admit a comparison relation kind unless a named receiving use needs distinct comparison occurrences as such; then name that use and follow relation-kind admission. None of these comparisons changes the WorkPlan or creates a universal planned-to-actual relation.

An unplanned participant is still an actual participant when the relation’s obtaining predicate holds for the complete participant set. To say that a planned value was missing, excluded, or substituted, apply the comparison policy’s closure or negative criterion to the case facts. Return missing-information when facts required to decide the comparison are unavailable; return missing-governor when the required comparison predicate or policy rule is absent.

A.15.3:4.6 - Preserve revisions and replay

Pin a declaration episteme or edition-bearing planned value only when choosing another one could change the planned meaning. Latest, a mutable alias, a publication face, or an untyped policy label is not a reproducible reference.

When a newer declaration becomes available, establish which declaration the planned use selects and whether that selection remains admissible. Retain an unchanged earlier selection while it remains admissible. Revise the WorkPlan claim content when its intended member, value, conditions or selected declaration reference changes, including a change required by the governing rule. If the necessary rule or selection is unresolved, identify that gap before claiming the row is usable. An identity-bearing change creates another WorkPlan episteme; assert historical continuity only when EpistemeEditionRelation obtains. Preserve the earlier WorkPlan reference already cited by work or another actual use, and state substitution or variance separately. A carrier or representation change alone does not reidentify the plan while the C.2.1 discriminators stay fixed.

When presenting selected WorkPlan content, keep it traceable to the plan under the applicable publication rules. A new planned row, default, condition or baseline rule belongs in a revised WorkPlan under §4.0; it cannot acquire authority merely from that presentation.

A.15.3:5 - Archetypal Grounding

These constructed cases supply illustrative planning facts; they do not report observed executions.

A.15.3:5.1 - Planned holder designation against one direct system-role-assignment species

An inspection team plans a future assignment of Robot_8. It proposes InspectionRobotSystemRoleAssignment as the species and Robot_8_Ref as the intended holder; Robot_8_Ref : U.EntityRef resolves to admitted Robot_8 : U.System. The proposed InspectionRobotSystemRoleAssignmentSignature names HolderSystemSlot, InspectionRobotSystemRoleKindDomain as the domain of its local assigned-kind slot, and InspectionRobotSystemRole as the required value. The enclosing A.15.2 WorkPlan separately states InspectionRobotSystemRole as the intended local system-role-kind condition.

Planning result: these inputs preserve the intended holder choice, but supply no resolving species declaration with its specific assignment predicate. A.2.1 states what each species must declare and the common occurrence-identity discipline; A.6.5 governs its declaration-local SlotKinds, ValueKinds and reference modes. Return missing-governor for the typed holder row until the domain declaration supplies the participant meanings, predicate, applicability and occurrence rule. The team can retain the intended holder as ordinary A.15.2 plan content.

With that declaration available, the typed row points to its HolderSystemSlot and records the planned holder designation under §4.3. A later affirmative assignment assertion requires the direct species predicate to hold for its complete real participant set and its occurrence law to be satisfied. Preserve the planned holder choice as the baseline when that predicate fails under a stated negative criterion or its satisfaction remains unresolved.

Blocked near-miss: Bearing_C isPartOf Pump_P cannot supply a relation row. A.6.5:5.2 keeps PartHolonSlot and WholeHolonSlot hypothetical until a part-relation pattern defines their meanings, predicate, applicability, and occurrence identity. Return missing-governor: planned part-relation participant designation for <Bearing_C, Pump_P> or keep the choice as ordinary A.15.2 plan content; do not present the sketch as an admitted RelationSignature.

A.15.3:5.2 - Planned argument and expected result against A.6.1

A team plans one Pump #37 recognition evaluation. It expects the application to use Pump #37 as candidate and return true if the cited criterion, construction facts, reidentification rule, interpretation basis, and required fastening-relation fact are available and determine satisfaction. The condition reference records that expectation; it makes none of those claims true. Pump37-Classification-Plan-E1_Ref identifies the WorkPlan, HolonRecognitionMechanism-E1_Ref identifies the cited A.6.1:5.7 mechanism episteme, and Pump37-ExpectedTrue-Conditions-E1_Ref identifies the separate condition claims.

The WorkPlan concerns the already admitted Pump #37, uses PumpMaintenanceEvaluationScheme-E1, and coordinates intended HolonRecognitionEvaluation@FPF during 10:00–10:15 UTC on 2026-07-21 with intended performer RecognitionEvaluator_A. These are planning claims; the later application below is established separately.

The WorkPlan carries this copyable planning content:

SlotFillingsPlanItem:
  planItemDesignator: pump37-recognition-baseline
  workPlanRef: Pump37-Classification-Plan-E1_Ref

  intendedPerformanceDesignator: planned-pump37-recognition-use-01
  plannedFillingRows:
    - rowDesignator: candidate-pump37
      targetDeclarationRef: HolonRecognitionMechanism-E1_Ref
      targetOperationDesignator: recognizeAdmittedHolonCandidate
      targetMemberDesignator: candidate
      targetMemberFamily: OperationArgumentDeclaration
      memberDefinitionPattern: A.6.1
      plannedValueOrDesignation: Pump_37_Ref
      planningConditions: Pump37-ExpectedTrue-Conditions-E1_Ref
      declarationEditionPin: HolonRecognitionMechanism-E1
    - rowDesignator: expected-recognition-true
      targetDeclarationRef: HolonRecognitionMechanism-E1_Ref
      targetOperationDesignator: recognizeAdmittedHolonCandidate
      targetMemberDesignator: recognitionJudgment
      targetMemberFamily: OperationResultDeclaration
      memberDefinitionPattern: A.6.1
      plannedValueOrDesignation: true
      planningConditions: Pump37-ExpectedTrue-Conditions-E1_Ref
      declarationEditionPin: HolonRecognitionMechanism-E1

In that operation declaration, candidate accepts exactly one U.Entity through a U.EntityRef; recognitionJudgment returns exactly one carried-by-value member of RecognitionJudgmentValue = {true, false, unknown}. The rows cite those rules instead of redeclaring them.

Later, A.6.1 identifies Pump37RecognitionApplication-2026-07-21T100000Z. The application binds Pump #37 as candidate, but a required fastening-relation fact is unavailable, so it returns unknown. Comparison result: the plan expected true under its cited conditions; the actual application returned unknown because one availability condition failed. An A.6.RCD disposition-2 local compound assertion may state that comparison from the preserved plan episteme, application, result binding, and failed condition. It neither rewrites a row nor admits a universal planned-to-actual relation.

The plan keeps the expected true; A.6.1 supplies the separately established application and its returned unknown. Use A.1 for the recognition criterion and C.2.1 if a separate result episteme is needed. Evidence and assurance remain governed by their applicable patterns.

A.15.3:5.3 - Hardware-acceptance pseudo-slots rejected

A hardware acceptance method says to use a calibrated instrument, selected reference plane, calibration record or certificate, and threshold. That sentence describes a method; it declares no A.6.5 SlotSpecs. Keep those choices as ordinary A.15.2 plan content, each under the pattern that defines the plane, calibration or evidence reference, and threshold.

Open A.15.3 only when an A.6.1 declaration, a RelationSignature SlotSpec, or another declared member already defines both the position and its actual-use rule. Otherwise return missing-governor for typed reuse; do not wrap the method description or equipment card in a fictitious slot-bearing declaration. Measurement, evidence sufficiency, readiness, acceptance, and actual instrument use remain separate.

A.15.3:5.4 - Edition-sensitive selector or archive planning

A selector or archive plan may need to preserve a comparator, descriptor definition, distance definition, evidence policy, or another edition-sensitive choice. A suite description, archive card, or generated view does not make those labels declaration members.

If a cited declaration exposes an A.6.1 argument or result, a RelationSignature SlotSpec, or another member whose defining pattern supplies its meaning, actual-use predicate, and cardinality, record one A.15.3 row per chosen member and pin only editions that affect the plan. Otherwise keep the choice as ordinary A.15.2 content or return missing-governor for typed reuse. The later application, dated work, archive or selection result, evidence path, publication, and variance remain separate; a card used as a view conveys the selected plan rather than establishing additional planning claims.

A.15.3:6 - Scope Declaration and Rationale

Scope. A.15.3 records positive planned designations against existing declared members inside one WorkPlan. When a later question requires comparison, establish actual-use claims under each member’s predicate and compare the resulting facts under §4.5. Prohibitions, exclusions, required absence and completeness use separate plan claims under §4.0; other claims use the governing patterns named in §12.

Rationale. The practitioner gets a reusable planned baseline without another U-kind or universal slot relation. Each declaration family keeps its own member meanings and actual-use rules; A.15.3 adds only the planned choice.

A.15.3:7 - Conformance Checklist

IDRequirementPractical test
CC-A15.3-01The item is declaration-local WorkPlan content.Its designator resolves inside one cited WorkPlan episteme; no independent PlanItem identity or row authority is claimed.
CC-A15.3-02The WorkPlan keeps its already identified present EntityOfConcern; the item separately names the future performance being planned.Use the intended-performance designator as plan content; the EntityOfConcern resolves to the already identified present subject.
CC-A15.3-03Every row points to one declaration episteme and member whose pattern defines both member meaning and actual-use predicate.The declaration reference, local member designator, family, defining pattern, and predicate route all resolve; A.15.3 states only the intention.
CC-A15.3-04Relation rows use only conforming A.6.5 SlotSpecs inside cited RelationSignature epistemes.Resolve the selected SlotSpec inside the cited RelationSignature, including the relation’s predicate and participant meanings; the Robot_8 row in §5.1 awaits that declaration. Hypothetical PartHolonSlot and WholeHolonSlot retain their named blocker.
CC-A15.3-05Operation rows use A.6.1 argument or result declarations.Mechanism episteme, operation designator, member designator, ValueKind, designation rule, binding predicate, and cardinality resolve together.
CC-A15.3-06Any other target has a pattern that explicitly defines it.Missing member meaning, actual-use predicate, or defining pattern yields missing-governor, not a generic target.
CC-A15.3-07The planned value follows the member’s ValueKind, designation rule, and cardinality.A single-valued target has at most one effective planned value; conditions and a resolution rule select among alternatives, while multivalued and ordering semantics come from the declaration.
CC-A15.3-08A row states a positive intention.Omission is open-world; prohibitions, exclusions, required absence, and completeness use separate plan claims rather than empty or negated fillers.
CC-A15.3-09Planned filling remains planned.Read each row as the positive intention defined in §4.0, keeping its intended performance and applicability conditions explicit.
CC-A15.3-10Plan revision follows C.2.1 WorkPlan identity.Changed identity-bearing content identifies another WorkPlan episteme; edition continuity is asserted only when EpistemeEditionRelation obtains, and PlanItems gain no separate edition ontology.
CC-A15.3-11Later actual facts are established independently.Establish actual relation participation and operation bindings under their direct predicates. Identify Work under A.15.1 only when that dated occurrence claim is needed; none follows from a plan row.
CC-A15.3-12Later comparison preserves the cited baseline and polarity.Substitution or variance uses a stated comparison policy; a missing-filler or negative result needs its closure or negative criterion and case facts.
CC-A15.3-13Edition, reference, and policy pins are concrete and decision-relevant.No implicit latest, generic RefKind, generic PolicyRef, publication face, or conflicting pin controls a row.
CC-A15.3-14Conditions retain their own grounds; a view alone adds no plan authority.Cite the governing conditions from their own patterns. Trace a view to its WorkPlan; any new planned row or rule requires the corresponding plan revision.

A.15.3:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Generic slot-bearing descriptionAny description with fields is treated as a reusable declaration.Point to a declared RelationSignature SlotSpec, A.6.1 argument or result, or another member whose pattern defines its meaning and actual use.
Dependent PlanItem U-kindA ClaimGraph component receives a rival identity and ontic settlement.Keep SlotFillingsPlanItem as declaration-local WorkPlan content.
Planned SlotRelationThe plan claim is reified as an obtaining world-side relation.Keep planned filling as positive claim content; open an actual relation only under its direct predicate.
Declaration/plan responsibility blurThe declaration pattern is said to make the planning intention, or A.15.3 is said to define actual use.Let the declaration pattern define member meaning and actual-use predicate; let A.15.2 and A.15.3 state the intention.
Method-description slotGeneric method wording is mistaken for a declaration member.Keep it as ordinary plan content or return missing-governor when typed reuse is required.
Relation/operation collapseA.6.1 arguments and results are written as A.6.5 SlotSpecs.Dispatch by target family and keep each declaration vocabulary local.
Row-count cardinalityRow count or order silently defines multiplicity, alternatives, or sequence.Use the declaration’s cardinality; for alternatives, state conditions and a resolution rule.
Empty filler as prohibitionOmission, null, or a negated reference is read as must not use.State prohibition, exclusion, required absence, or completeness as a separate plan claim.
Plan-as-actualA planned value is treated as actual participation or a returned result.Establish the relation or application binding independently; identify Work separately when that occurrence claim is needed.
Generic reference or policyRef, SpecRef, PolicyRef, or a shared label is treated as sufficient.Use the concrete RefKind and identify the policy’s kind, defining pattern, episteme, applicability, and reference scheme.
Latest-as-baselineA mutable label stands for a declaration or value episteme.Pin the selected episteme when another resolution could change the planned or comparison result.
Backfilled planActual values replace planned rows after work.Preserve the cited plan episteme and state a neighboring substitution or variance claim.

A.15.3:9 - Consequences

BenefitCost and control
Planned choices remain replayable.Each row must point to a declared member and the pattern that defines it.
Declaration families remain coherent.Planners must dispatch relation participants and operation values separately.
Actual-use claims have separate grounds.A matching plan row supplies neither relation participation nor an application binding; add Work admission only when the claim consumes it.
Missing declared semantics becomes visible.Return the specific missing-governor result when the member or actual-use rule is absent; distinguish missing planning information under §12b.

A.15.3:10 - Rationale

Planning needs a way to preserve intended values without turning every planning field into ontology. Existing RelationSignature SlotSpecs, A.6.1 operation declarations, and other declarations already define reusable member meanings and actual-use predicates. A.15.3 records only the intended use of those members inside one WorkPlan.

The declaration pattern defines member meaning and actual-use rule; A.6.5 or A.6.1 defines the applicable declaration form; the WorkPlan records intention under C.2.1 and A.15.2. Establish a later application, relation occurrence, result or comparison under its own predicate. Identify dated Work only when its occurrence is claimed. The planning row supplies none of those actual-use facts by itself.

A.15.3:11 - SoTA-Echoing

Source contributionAdoption in A.15.3Rejected shortcut
ISO/IEC/IEEE 12207:2017 describes software life-cycle processes, activities and tasks; it is retained as a historical anchor, withdrawn on 29 April 2026 and superseded by 12207:2026. ISO/IEC/IEEE 15288:2023 provides system life-cycle process descriptions without prescribing a specific life-cycle model and refers detailed information-item content to ISO/IEC/IEEE 15289.Keep the declaration, intended plan content, and performed work separate.Treating a process-tooling layout or checklist field as an FPF declaration.
SLSA v1.2 build provenance separates build definition, including resolved dependencies, from run details; in-toto Statement v1 separates subjects from the typed predicate content.Cite declaration and edition only when replay depends on them; keep run, provenance, result, and evidence claims separate.Importing a supply-chain record schema as a universal slot or result ontology.
The Nix 2.26 manual’s lock-file mechanism records resolved dependency inputs in flake.lock, including revisions where applicable and content hashes. An existing, up-to-date lock file preserves the selected direct and transitive dependencies for repeatable input resolution.Pin the selected declaration or value episteme when another resolution could change the planned meaning.Saying latest when a later comparison needs one edition.

A.15.3:12 - Relations

  • Builds upon: C.2.1 and A.15.2 for WorkPlan identity, present EntityOfConcern, intended-performance designators, and intended-work content; A.6.5 for SlotSpecs inside RelationSignature epistemes; A.6.1 for operation argument and result declarations; and the pattern that defines any other admissible declaration member.
  • Coordinates with: A.15.1 for dated Work; relation patterns for actual participants; A.6.1 for applications and bindings; A.6.RCD for local fulfilment or variance claims when no comparison relation is already defined; A.15.5 for work-entry readiness; and the evidence, gate, evaluation, result, production, delivery, acceptance, publication, and currentness patterns when those claims are made.

A.15.3:12a - P2W planned-filling use

When P2W reaches intended work and a planned value reuses a member already declared under §4.1, carry the WorkPlan, intended-performance designator, declaration episteme, member designator, defining pattern, planned value, and each condition or pin whose change would alter the effective planned value or later comparison. The declaration pattern defines the member and actual-use rule; A.15.2 and A.15.3 state the intention.

If no reusable member is needed, carry ordinary A.15.2 plan content. If typed planned use is needed but the member, its meaning, its actual-use predicate, or its defining pattern is absent, carry missing-governor for that intended use. For an incomplete or unresolved plan, name the planning information to recover (§12b). The row may cite a separately established condition when it controls the planned choice. Establish other claims under their own patterns—for example, A.15.1 identifies performed Work and A.15.5 decides work-entry readiness.

A.15.3:12b - Lowering, repair, and refresh conditions

Use ordinary A.15.2 plan content when no reusable declaration member is needed. For typed use, name any missing or unresolved planning information, including the intended-performance designator, declaration episteme or member designator; an operation argument or result also requires its operation designator. Recover that information so the row identifies the intended use and resolves to an existing declaration member. Return missing-governor only when the needed member or its defining pattern does not exist, or the member’s meaning, designation rule, cardinality, or actual-use predicate has not been defined. Do not replace that blocker with a generic slot-bearing description.

State prohibitions, exclusions, required absence, and completeness under their plan-constraint or negative-claim patterns instead of using omission or an empty filler. A later missing-filler, substitution, or variance result needs a comparison policy whose closure or negative criterion applies to the case facts.

Apply §4.6 to decide whether the selected declaration must change. Revise the WorkPlan ClaimGraph when its selected target member, planned value, intended-performance designator, condition, or relied-on declaration reference changes. If a C.2.1 identity discriminator changes, identify another WorkPlan episteme and relate it to the earlier one only when EpistemeEditionRelation obtains. Preserve the earlier WorkPlan reference already cited by work or another actual use. Refresh only a declaration, reference resolution, policy, or WorkPlan episteme whose changed resolution would alter the later decision; re-evaluate an actual-use change under its relation predicate or A.6.1 application predicate.

A.15.3:End

A.15.4 - Work-Relevant Appearance-Based Reliance Repair

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

At a glance. Use A.15.4 when a display, copied approval or generated explanation is about to justify work or reliance, but the prerequisite for that use is unclear. Ask three questions: What am I about to do or rely on? Which fact, relation, decision, or result would warrant that use? Can I check that it holds for this case and time? Keep the appearance at the lightest safe use until that prerequisite can be checked.

Use this when. Use this pattern only while appearance hides the direct object and test needed for one attempted use. If the direct question and the pattern that defines or tests it are already known, apply that pattern directly.

First output. Start with one ordinary sentence:

This green tile points to GateDecision-42, but its link is stale. Use the tile only to find the current decision; do not deploy Release-42 until that decision says pass for this release, target, scope, and window.

That sentence is a complete first result for this one-prerequisite use: it identifies the attempted use, appearance, missing prerequisite, allowed use now and return condition. If the prerequisite is recovered immediately, omit the note and apply its direct rule.

When a short worksheet is useful, unpack the same result without adding ontology:

Attempted use:
Appearance:
Missing prerequisite:
Safe use now:
Blocked overread:
Return when:

Keep each independently required object, its subject pattern and test, required posture or currentness, and dependency on the attempted use separately recoverable. Keep a native reference when its governing rule or the receiving use requires one; an ordinary statement may identify its participants directly. Retain a sufficient existing note or accessible source account. Use RequiredPositionEntries when rows help compare or inspect the prerequisites; in that layout, use one row per direct object:

RequiredPositionEntries:
  - SubjectPatternLocator:
    DirectObjectKind:
    ProjectSideObjectRef:
    RequiredPostureOrCurrentness:
    DependencyOnAttemptedUse:

These rows represent prerequisites defined by their subject patterns. When the analysis needs a separately referable claim, identify the C.2.1 episteme whose EntityOfConcern and ClaimGraph carry it; use an existing sufficient account when available. Split claims with different entities of concern. For a separated handoff, include the interpretation and source return the recipient would otherwise lose; a link is sufficient when that recipient can access and use it.

First repair use in practice. Choose the sufficient supported continuation: orientation or source finding, preservation of an early cue under A.16.1, ordinary planning, a bounded reversible probe, narrowed reliance, or a stop on the unsupported use. Admit WorkPlan content under A.15.2 only when that coordination claim is made.

What goes wrong if missed. The appearance is treated as proof of approval, gate passage, evidence, assurance, performed Work, currentness, or release authorization. Work then proceeds or stops while the relation or result that must support the claim is missing, stale, revoked, or contradicted.

Subject of the repair in plain terms. The pattern handles one attempted-use question. The appearance, attempted use, direct prerequisites, safe current use, and blocked overread retain the kinds and relations supplied by their own patterns.

First repair checks.

  1. Name the appearance by its kind without treating it as the required relation or result.
  2. Name the attempted use and the subject that use concerns.
  3. Name the first missing prerequisite and the pattern that defines or tests it. A note stopping the unsupported use can finish there; a decision to proceed still requires every prerequisite consumed by that use.
  4. Keep each independently required claim, instituted effect, relation occurrence, result, decision, assignment, evidence relation, currentness relation, or plan separately recoverable. Choose typed rows when their arrangement helps comparison or inspection.
  5. Before allowing the attempted use, establish each required relation or result under its own criterion and match its applicable participants, scope, time and reliance basis to this case. Reuse an applicable established result; recheck what is changed, missing or expired.
  6. A relevant permission or norm conflict, gate decision, or work-entry-readiness result remains a separate prerequisite. An unresolved conflict blocks only the affected use and does not make an independently obtaining grant cease.

Not this pattern when. Stay in A.15 when the question is only separation among the acting System, local system-role kind, classification judgment, direct U.SystemRoleAssignment species, U.Method, U.MethodDescription, U.WorkPlan, and U.Work. Stay in A.15.2 for WorkPlan construction, A.15.3 for declaration-local planned-filling content, and A.15.5 for full-kit condition or work-entry readiness. Stay in A.16.1 and C.2.4 for pre-articulation cue preservation, C.16.Q for a dynamic-quality claim, A.6.A for an action invitation, and E.17 for publication-face exposure. When the direct evidence, gate, constraint, boundary, permission, authority, Work, or other claim is already known, use the pattern and test selected by the §3 lookup instead of A.15.4.

What this buys. The practitioner can keep a useful source-finding or limited-use continuation while withholding an unsupported stronger conclusion. Repeated ambiguity can then be repaired in the source or presentation that causes it.

A.15.4:1 - Problem Frame

A display or copied claim can look sufficient for a decision while the required fact, relation or result remains hidden. The practitioner must recover the prerequisite for that particular use and decide which continuation its grounds support.

Plain recognition line. Follow the displayed claim or pointer to the required relation or result and its test. A recoverable native reference can serve that purpose; appearance alone establishes no authorization or other relied-on fact.

Reliance-appearance and claim/effect-position discipline. Recover the value required for the attempted use: an actual relation occurrence, decision/finding/status result, plan, Work occurrence, or claim about that object. Apply the criterion defined for that value. A project record may be a U.Episteme that names it, and a publication relation may expose that record; inspect its content under the governing predicate. Use a typed reference when the governing rule or receiving use needs that identity. If the prerequisite or its applicable test cannot be recovered, keep the appearance at orientation, source-finding, cue-pack preservation, repair request, or bounded-probe use.

How to read the optional note and rows. The labels below are worksheet prompts for objects and relations defined by their own patterns:

  • RelianceAppearanceRef names the dashboard tile, credential view, copied wording, generated explanation, publication face, carrier, display, API wording, source-finding pointer, or low-articulation indication whose appearance is tempting the work or reliance use. RelianceAppearanceKind states its kind rather than making these items one kind. If the live value is a preserve-worthy early cue, use PreArticulationCuePack under A.16.1.
  • WorkOrRelianceUseKind and WorkOrRelianceUseRef name the use being justified: intended work, reliance on a claim, reliance on performed work, a work-relevant P2W claim, or a P2W chain position. These fields select the current branch; they do not create a durable kind.
  • When the worksheet is selected, RequiredPositionEntries carries the prerequisite set for the attempted use, with one row per independently required direct object. Every row states SubjectPatternLocator, DirectObjectKind, the native ProjectSideObjectRef required for that object, RequiredPostureOrCurrentness, and DependencyOnAttemptedUse. The locator points to the pattern whose content defines, constrains, or tests the direct object; a proxy or navigation pattern is insufficient. One row may point to a required claim, another to an instituting speech act, grant, conflict finding, gate decision, assignment, evidence/currentness relation, plan, or other direct object; the row set creates none of them and never turns a claim into an instituted effect.
  • AllowedUseNow states what use remains admissible after repair, such as orientation, source-finding, bounded reversible probe, narrowed reliance, or proceed-inside-recovered-relation.
  • AppearanceOverreadBlocked names the false use that the reliance appearance would create by appearance, for example treating a dashboard color as gate passage or a copied approval as a current speech act.
  • RecoveryOrStopCondition names the failed prerequisite and what must change. On return, recheck that premise and affected dependents; every prerequisite still needs an applicable result under its own criterion, currentness and reliance conditions. Reuse unchanged applicable results. A relevant PermissionNormConflictFinding@Context retains its separately recoverable A.2.8.PER disposition; an unresolved or norm-selecting result blocks the affected use without changing grant currentness.

Here evidence, attestation, provenance, and currentness relations retain their direct predicates and identity rules. A.10 makes the independently established relations, their sources, and the bounded reliance on them recoverable in a descriptive account; it defines no universal evidence-provenance relation. That account supplies no authorization by itself.

A.15.4:2 - Problem - Cluster Boundary

A.15 remains the kernel for separating an acting System, local system-role kind, classification judgment, direct U.SystemRoleAssignment species, U.Method, U.MethodDescription, U.WorkPlan, and dated U.Work. A.15.4 starts only when a reliance appearance begins to justify a work or reliance claim and the team still needs to recover the required relation or result and the rule or test that applies. Recover a project-side reference when that rule or use needs one. If the question and its rule are already known, use them directly.

A.15.4:2.1 - Forces

ForceTension
Work momentum vs. prerequisite recoverabilityTeams need to keep work moving, but a reliance appearance can make the wrong claim look like work authorization while a required relation or result is still unnamed.
Cheap first note vs. high-impact relianceRoutine source-finding should stay light, while release, safety, compliance, system-role-assignment, credential-status, assignment-state, and gate cases need the distinctions and evidence required by their direct rules.
Publication face vs. required valueThe visible carrier may be useful for orientation, but the work or reliance claim belongs to the project-side FPF kind, relation or result, and reference named by value.
Neighboring claims vs. local repairA.15.4 can recover a missing prerequisite for the attempted work or reliance use, but evidence, gate, assurance, boundary, work-occurrence, and the permission/authority object selected by the §3 branch use the patterns and tests that define them.
Repeated ambiguity vs. individual burdenRepeated ambiguity about a required claim, instituted effect, relation, result, or reference should become prerequisite-lookup or source-relation repair work, not repeated manual reconstruction by every acting practitioner.

A.15.4:3 - Solution - Work-Relevant Appearance-Based Reliance Repair

A.15.4:3.3 - Core stress-case rule

Ordinary local note. The opening sentence or six-line note can stop at the first missing prerequisite when its result is a bounded stop or source-finding continuation. A decision to proceed must still satisfy all prerequisites required for that use.

Treat an irreversible use or one with external impact as high-impact. For several prerequisites, a high-impact use, audit, handoff, or later reliance, keep each prerequisite separately recoverable together with the allowed use, blocked overread, and recovery or stop condition. Use a sufficient note, accessible source account, or worksheet selected for comparison or inspection.

The reliance appearance may be a tile, credential view, approval-looking memo, generated explanation, copied review, provenance mark, API wording, functional-description publication, or composed source-relation chain. The A.15.4 check asks whether every direct object required by the attempted use resolves and meets the posture and currentness predicates defined for that object, not merely whether a project-side reference is named or the reliance appearance is impressive, fluent, easy to inspect, or visually salient.

Choose the worksheet detail by use. The questions below help recover the distinctions required by the attempted use and each prerequisite’s own rule. Such a rule may require assignment identity, assignment state, credential status, assurance, currentness, revocation, or cross-context detail. Keep that detail available in whichever expression serves the use. The fields can help an ordinary note or a separately identified C.2.1 account.

FieldWorking question
acting or affected systemWho would act, rely on the appearance or be affected? Use ordinary practitioner wording unless a precise System, Agent or dated Work claim is needed; then recover the applicable A.1, A.13 and A.15.1 basis.
system-role-assignment claimWhich assignment occurrence is being claimed, and which U.SystemRoleAssignment species declares it? A context field ending in ...SystemRoleAssignmentRef is typed by U.RelationRef constrained to U.SystemRoleAssignment and resolves the occurrence. Keep capability, authority, responsibility, and Work attribution separately recoverable.
intended work or work targetIs the user planning intended work, relying on a dated U.Work occurrence or result, or making another reliance claim? Name that branch and its required relation or result before the reliance appearance guides it.
affected resource or claimWhich resource, claim, gate, credential, credential-status, system-role-assignment-state relation or assertion, evidence, approval, or source-finding pointer with an authority relation is supposedly affected?
contextWhich bounded context, environment, project slice, API setting, connector setting, protocol setting, or relying situation makes the claim applicable?
policy or gate versionWhich policy, gate profile, constraint version, method version, or register edition applies to the claim?
time windowDuring which window is the claim, effect, source relation, or recovered-use boundary claimed to hold?
currentness or revocation fieldIs the source relation current, stale, revoked, superseded, expired, contradicted, or unknown?
issuer or required referenceWhich issuer, project reference, register entry, source-currentness or credential-status record, speech act, gate decision, evidence relation, or work-occurrence record is required for the current use, and where is its criterion defined?
verifier or relying contextWho is checking or relying on the claim, and in which context?
evidence or attestation relationWhich independently established evidence, provenance, or attestation relation does the A.10 account cite for this claim and bounded use?
sourceRelationClassWhich E.17:5.1b source-relation class or claim-use class applies to the reliance appearance and required claim or use?
unsupported effectWhich requested work claim, reliance claim, required value, or downstream effect remains unsupported and needs narrowing, repair, reopening, probing, or blocking?

Start with the A.15.4 first repair checks above when the reliance appearance is being used as a reason for intended work, reliance, or a work-relevant claim. If the direct question is already known, use the §3 lookup and apply its predicate; permission or authority uses the single branch there. Use A.15.4 while the required object, applicable test or basis for the attempted use still needs recovery.

When a reliance appearance seems to authorize work or reliance. Use A.15.4 when a publication, display, credential view, wording, or explanation looks like permission, prohibition, readiness, or evidence for intended work or reliance. Ask what the user intends to do next, what relation or result would make that use admissible, and which test and supporting facts that claim requires.

Name the record or relation that authorizes, forbids, records, or supports the required claim under its subject pattern. Use E.17:5.1c for the shared meanings of orientation use, reliance use, operative claim, unsupported downstream use, and reopen trigger; use E.17:5.1d when the primary question under repair belongs to another FPF rule or result.

Name the attempted use, recover each required object and apply its governing predicate. Keep episteme, publication and display distinct when those differences affect access or reliance. Follow a record’s reference and inspect the content needed for obtaining, applicability, currentness and evidence. Cite the defining ClaimGraph when its identity changes the use; an ordinary pattern citation is otherwise sufficient.

Positive repaired disposition. After recovering every prerequisite consumed by the attempted use, confirm that each satisfies its own criterion, applicability, currentness and required evidence or source relation. Reuse unchanged applicable results. A permission/norm conflict retains its separate A.2.8.PER disposition: an unresolved or norm-selecting result blocks the affected use without cancelling an independently obtaining grant. State the next supported action; a failed prerequisite blocks only the use depending on it.

Reliance dispositions after prerequisite recovery:

Work or reliance dispositionUse whenMinimum useful result
Orientation or source-finding noteThe reliance appearance is only a publication face, publication carrier, rendering, cue, retrieval cue, learning aid, or reversible local probe trigger.Use a sufficient ordinary sentence or note. Name the first missing direct object in plain language; choose RequiredPositionEntries only when rows help the current comparison or inspection.
Supported bounded relianceEach prerequisite for the attempted use meets its own criterion, case facts and applicable conditions.Keep each independently required object recoverable in a sufficient note, accessible source account or selected rows. Include participants, scope, window, assignment, capability, authority and responsibility only when the use consumes them. Retain any additional conditions required for high-impact use under its applicable rule. For each required permission or authority claim, apply the matching row in the branch below or its direct governing rule.

If the worksheet helps, use only the rows and fields that the attempted use needs:

FieldValue
RelianceAppearanceRefName the appearance being relied on by value, such as the dashboard tile, credential view, copied text, generated explanation, publication face, publication carrier, rendering, or source-finding cue.
RelianceAppearanceKindName the encountered object or relation kind without granting authority by appearance: selected U.Episteme, EpistemePublicationRelation occurrence or reference, publication form, MVPK face, publication carrier, rendering, PublicationUnit, dashboard tile, credential view, generated wording, copied wording, or source-finding cue.
WorkOrRelianceUseKind and WorkOrRelianceUseRefName the use being justified by value: intended work, reliance on a claim, reliance on a dated U.Work occurrence, method-family selection, selected method, method of work, work plan, planned work, work result, result measurement, release reliance decision, non-work reliance claim, work-relevant P2W claim, or P2W chain position. A planned baseline remains claim content in one U.WorkPlan; performed work becomes U.Work only after its actual performer is identified and that performer’s A.13 core basis is independently recovered and the dated occurrence is independently admitted through A.15.1; for a work-result measurement, use C.16 to distinguish the measurement, its result and the episteme stating that result; use A.10 when a separate reliance account is needed.
RequiredPositionEntriesIn this worksheet, use one row per independent direct object, whether it is a claim, instituted effect, relation occurrence, result with a pattern-defined criterion, gate decision, assignment, evidence/currentness relation, plan, or other prerequisite. Each row names its SubjectPatternLocator, exact DirectObjectKind, native typed ProjectSideObjectRef, RequiredPostureOrCurrentness, and DependencyOnAttemptedUse. The locator must identify the pattern whose content defines, constrains, or tests that direct object. Do not pack several independent prerequisites into one row or coerce their native refs into one generic U.EntityRef list.
AllowedUseNowState the safe current use. proceed-inside-recovered-relation is allowed only after every required entry passes its RequiredPostureOrCurrentness and exact-use match; otherwise retain orientation, source-finding, bounded probe, repair request, narrowed reliance, or blocked unsupported use.
AppearanceOverreadBlockedState the overread being blocked, such as treating display color as gate passage, copied approval as a current speech act, a credential screenshot as permission, or a generated explanation as evidence.
RecoveryOrStopConditionName the failed prerequisite and what would restore the required basis. Before proceeding, revisit that result and any dependencies affected by the change; reuse unchanged applicable grounds. Apply each direct object’s criterion and keep separately required conflict, gate and readiness results recoverable.

Borrowed episteme and publication discipline. A.15.4 borrows the C.2.1, E.17, and E.24.PUB distinctions. The claim-bearing FPF kind here is U.Episteme. When availability of its selected edition matters, name the EpistemePublicationRelation occurrence or reference. Publication forms, MVPK faces, publication carriers, renderings, PublicationUnit instances, and source-finding cues are separate kinds or relation positions in the case; no publication-kind shortcut replaces them. A planned baseline remains one U.WorkPlan episteme; any A.15.3 planned-filling rows remain declaration-local ClaimGraph content inside it. Keep launch and finalization values distinct from the project records stating them; decision logs remain gate or decision records, performed-work evidence remains evidence, and dated Work occurrences remain A.15.1 matters.

When a prerequisite or its applicable test is incomplete, name the attempted work or reliance use and choose the lightest sufficient continuation. Combine the actions below as needed, adding project-side reference detail when the governing rule or receiving use requires it:

  1. Use the reliance appearance only for orientation or source-finding.
  2. Reopen the selected source U.Episteme for the current claim, the EpistemePublicationRelation occurrence when availability is the issue, the source-bearing relation, register entry, direct record, or direct relation; or refresh source-currentness, credential-status, system-role-assignment-state, context-state, or another currentness relation.
  3. Narrow the proposed use to the participants, action, target, context and window covered by the recovered rule or result. Recover capability through A.2.2, precise assignment-bound Work attribution through F.6, and authority or responsibility through its direct predicate only when the use requires that claim; keep a missing governing rule explicit.
  4. Use a bounded reversible probe when its own conditions permit it. Add a WorkPlan only when coordination of that probe needs one; reversibility supplies no missing permission or safety condition.
  5. Separate finding or exposing the missing source from assigning its repair. For source finding, ask an identified issuer, maintainer, verifier, holder, publisher, source contact, or acting user to expose the source or record using the direct source, publication, register, communication, access, or contact fact already available. For an allocation or duty to repair, apply §3.4 to that distinct claim. Keep the supported information request available and every additional missing gate, evidence, assignment, state, currentness, or boundary object separately recoverable.
  6. Repair the U.WorkPlan, U.MethodDescription, dashboard label, source-relation link, or boundary wording that made the overread plausible.
  7. Proceed only inside the recovered scope and window.
  8. Block only the work claim or reliance claim that lacks the required relation.

A.15.4:3.4 - Repair assignment rule

Missing source exposure versus repair assignment. If a required source or record is unavailable, ask an identified issuer, maintainer, verifier, holder, publisher, source contact, or acting user to expose or locate it using the available direct source, publication, register, communication, access, or contact fact. Assign repair work through the applicable allocation rule and its case facts. A claim of responsibility, commitment or duty, permission, or authority needs its own predicate, participants and grounds: permission to repair does not by itself allocate the work, and allocation does not by itself institute a duty. Use A.2.8 for an asserted commitment or duty and the §3.5 permission branch when that claim is current. A system-role kind or assignment contributes only the applicability ground consumed by the particular rule.

Keep the reason for an unresolved repair claim precise under A.6.RCD: use missing-governor when the needed predicate or governing condition is absent, missing-information when a deciding fact is unavailable, and factually unsupported when sufficient facts fail the positive test. A failed positive test alone does not establish a negative claim. These limits apply to the affected allocation, duty or other stronger claim; retain a source-finding request or narrowed use whose own conditions are satisfied.

Reliance-appearance kind check. First name the kind of the reliance appearance: episteme, publication occurrence, publication form, carrier, rendering, dashboard tile, credential view, generated/copied wording, or source-finding cue. If it exposes a typed ref, follow that ref to the required relation or result and apply the criterion defined in its SubjectPatternLocator. Resolve a defining or constraining ClaimGraph only when the rule identity or edition changes this use. If the required object and its grounds remain unrecoverable, retain only the supported orientation or source-finding use. A record’s content may supply those grounds even though its form alone does not.

Source-relation guard. A dashboard tile may guide release when its content exposes the applicable GateDecisionResult, scope and window, with the evidence and currentness grounds required for this reliance. Release urgency, display color, copied wording or fluency cannot supply a missing prerequisite.

A.15.4:3.5 - Prerequisite lookup table

Patterns and checks by required direct-object kind:

  • cue-only orientation: use only for attention, learning, source-finding, or a reversible local probe trigger; stay with A.16, A.16.1, or A.6.A when those claims are being made.

Permission and authority branch — use only for a live permission or authority claim. Do not route from approved, authorized, allowed, may, or the look of a permit. For each independently required claim, select the row whose question matches it; when no row applies, use that claim’s direct governing rule.

Plain questionPattern and required objectWhat closes or blocks this branch
Did an admitted system perform an approval, authorization, delegation, grant, or revocation communication?A.2.9; one SA : U.SpeechAct occurrence.Identify the System that actually performed the communication and independently recover its A.13 core basis, then let A.15.1 admit the speech-act Work independently. If the reliance claim must also identify the assignment that covered the communication, or the policy makes that assignment material, name the assignment already used in the A.13 account and use F.6 to compare its holder with the performer. For a grant or revocation under A.2.8.PER:4.7, recover the required grantor assignment and the act performed under it, including its F.6 attribution; authority retains its separate grounds. Add the context, time, act type, and evidence needed for reliance. The assignment supplies neither performerhood nor authority. A SpeechActRecord, message, or carrier is not the act, and the act alone does not make an institutional effect obtain.
Does a policy-valid strong grant currently obtain for this beneficiary and action?A.2.8.PER; one GrantedPermissionRelation@Context occurrence.Match beneficiary, action specification, policy/context, scope/window, and instituting SpeechActRef. A valid revocation, supersession, or policy failure may prevent or end the grant. An unresolved same-case conflict can block this attempted use without making the grant cease to obtain; keep those results separate. This is the permission-side instituted effect.
Before action, did a current frame complete enough for this use contain no applicable prohibition?A.2.8.PER; one NonProhibitionFinding@Context.Name the frame, use, beneficiary/action, scope/window, and evaluation. A stale or incomplete frame returns unresolved, not permission.
Did dated Work actually exercise one obtaining grant?A.2.8.PER; one PermissionExerciseRelation@Context occurrence.Identify the actual performer, independently recover its A.13 core basis, and use A.15.1 to admit the dated Work. Match its action and scope to the grant, which must obtain throughout the exercise interval. An assignment beneficiary requires the named covering assignment with that performer as holder. A kind beneficiary requires a covering assignment with that holder, the named kind in its declared kind slot, and satisfaction of the policy’s eligibility rule. For a party beneficiary, the performer must be that party or act under the obtaining on-behalf-of relation licensed by policy. Use F.6 when the receiving claim additionally needs precise assignment-bound attribution. No dated Work means no exercise; non-exercise is not violation.
After Work, did a current sufficiently complete frame find no applicable violation?A.2.8.PER; one NonViolationFinding@Context.Independently admit the acted-on Work under A.13/A.15.1. Recover the checked frame, its sufficient completeness and currentness, applicable prohibitions, evaluation and finding. Identify a separate dated evaluation Work only if that occurrence is asserted; then it needs its own admission basis. Add F.6 only for a consumed assignment-bound claim. Exercise or non-exercise alone settles no violation result; a stale or incomplete frame returns unresolved.
Do an obtaining grant and a current norm reach incompatible conclusions for the same beneficiary/action and overlapping scope/window?A.2.8.PER; one PermissionNormConflictFinding@Context.For settledByApplicableRule, cite the policy rule whose conditions match and which selects the governing claim. For settledByDecisionResult, recover the current PermissionConflictResolutionResult@Context, its resolutionWorkRef, deciderSystemRef, covering deciderSystemRoleAssignmentRef, independently obtaining decisionAuthorityRelationOccurrenceRef, selected grant or norm, scope/window and reopen condition. Independently admit that decision Work through A.13/A.15.1, then use F.6 for the required assignment-bound attribution. The direct result relation must connect that Work to the resolution result. If neither branch resolves the conflict, keep it unresolved and block the affected use.
Is an actual system or separately governed party obliged, prohibited, or given a recommendation-as-duty?A.2.8; one U.Commitment.Name the actual duty bearer, direct predicate, modality, exact referents, scope and window, applicable constitutive policy and rule, and actual instituting basis. A system-role kind or assignment may satisfy a rule antecedent but is not the duty bearer or commitment. The utterance, record, and carrier are not the commitment.

A gate or readiness result remains an additional A.21 or A.15.5 prerequisite; it creates none of these objects. If the issue is only wording, classify it through A.6 or the single permission-word branch in A.6.B. If only a permit, badge, message, record, or tile is visible, stay at orientation or source finding until every prerequisite consumed by the attempted use passes its own test.

  • system-role-assignment reliance: use A.2.1 and name the assignment occurrence and its declared species. Assignment-state reliance instead uses the A.2.5 SystemRoleAssignmentStateRelation; credential-status reliance uses the result established under the applicable credential-status rule, with A.10 for the evidence/currentness account when the use needs it; context-state reliance uses its applicable direct state pattern and record; and a state established by a gate decision keeps its separate A.21 GateDecisionResult. Keep every required object separately recoverable.
  • boundary, policy, API, schema, “allowed”, “authorized”, “approved”, “recommended”, or “guaranteed” wording: split the statement through A.6 or A.6.B. When its live job is permission or authority, return to the branch above; the displayed word does not choose the object.
  • gate decision or gate passage: cite A.21 GateDecisionResult (the result referenced by the local GateDecisionRef used below), its gateRef, profileApplicationRef, rationale, gate profile and version, complete effective check set, check-application results and mappings, decision and action consequence, scope/window and recheck condition. Keep the native A.21:4.1 content recoverable. Use DecisionLogRef when a log supplies the access, audit or replay path or the applicable policy requires it; retain replay or freshness pins when the claim requires them.
  • Flow constraint-validity witness: cite A.20 ConstraintValidityResult, its evaluation state, outcome when present, and witnessOrReason. Keep PathId or PathSliceId, window, sentinel and pins when applicable to the claim. When an A.21 gate consumes that result, also recover the GateCheckRef resolving to the GateCheckApplicationResult that cites it through sourceResultRef.
  • release, deployment, repair, inspection, or rollback work occurrence: cite the actual performer’s A.13 basis, one dated U.Work occurrence independently admitted under A.15.1, and the direct evidence or provenance relation recovered through A.10 when reliance on the occurrence is needed. If the reliance claim must also identify the assignment under which the Work was performed, check that relation separately through F.6.
  • evidence, provenance, authenticity, currentness, copied-source, or generated-source relation: recover each independently established direct relation under its defining pattern. Use A.10 for the descriptive claim-bound account, currentness and bounded RelianceDisposition; the account cites the relations and their basis rather than creating them.
  • a named assurance claim: apply B.3 to that claim and its limitations and reopen condition. A safety, compliance, trust, release, or characteristic claim first uses the direct pattern that defines or tests it; use B.3 only when that use separately requires assurance. Work-entry readiness uses A.15.5 and gate decisions use A.21.
  • generated explanation: recover the operative claim and the basis required for its proposed use. Use E.17.EFP when explanation-class ambiguity changes that use, and A.10 when the evidence/provenance account must remain replayable.
  • ambiguous approval, permission, or authorization wording: use the permission and authority branch above and choose by the plain question it answers now, never by the displayed word.

Recovered prerequisites for A.15.4 closure:

Pattern or relation usedRecovered output for this A.15.4 repairA.15.4-local use
A.6 or A.6.BThe recovered claim and its quadrant, with the pattern that defines or constrains it. A.6.B recommends stable L-*, A-*, D-*, and E-* IDs; material dependencies require an ID or canonical-location reference. A one-off sentence needs no separate Claim Register.Use for wording, boundary, API, schema, or use-boundary recovery before intended work or reliance.
A.10A descriptive claim-bound evidence-provenance account, the direct relations and currentness facts it cites, and its RelianceDisposition for the attempted use.Use for evidence, provenance, authenticity, credential-currentness, copied-source, or generated-source recovery.
B.3Typed assurance claim, no-assurance-use disposition, or rejected or downgraded assurance claim.Use only when the work or reliance claim under repair relies on a typed assurance claim.
A.21GateDecisionResult with its A.21:4.1 content, including gateRef, profileApplicationRef, check-application results and rationale, decision and action consequence, scope/window and recheck condition. Recover DecisionLogRef and replay or freshness pins when the actual use requires them.Use for gate-passage reliance in the named scope and window.
A.20ConstraintValidityResult with its evaluation state, outcome when present, and witnessOrReason, PathId or PathSliceId when applicable, window, sentinel, and pins when those fields are needed for the claim.Use for flow constraint-validity reliance.
Permission or authority is currentFor each independently required claim, use the matching row above or its direct governing rule and retain the required object with its own closing conditions.Do not mint or cite a generic permission-result object.
A.13 and A.15.1; F.6 when the assignment mattersIdentify the actual performer from the performance facts and independently recover its A.13 core basis; A.15.1 independently admits the dated U.Work occurrence. If this reliance must also state under which assignment the Work was performed, F.6 checks that separate relation. Add the direct evidence or provenance relation recovered through A.10 when the reliance uses it.Use for reliance on performed Work without turning the assignment check into a Work premise.
E.17.EFPBounded explanation-use classification over the identified source or target episteme, with its required source-to-target relation and any publication occurrence material to availability.Use when explanation-class ambiguity changes how the explanation may be reviewed or used.

For a consequential reliance claim, keep every participant, condition and evidence basis required by its governing rules recoverable. The preceding lookup identifies their separate sources; it does not impose all listed objects on every case. A sufficient orientation, source-finding or reversible-probe result can stop at its narrower boundary. Quick dispositions:

Encountered caseFirst A.15.4 disposition
Release dashboard tile exposing a source relationIf the tile is a current dashboard view of A.21 GateDecisionResult with decisionValue=pass (recovered directly or through a DecisionLogRef that cites it) plus release scope or work target, environment, scope, window, gate profile, gate version, and direct support relation recovered through A.10, it may carry gate-passage reliance for that release and environment.
Release dashboard tile without current gate or evidence relationUse the tile only for display or source-finding until the current A.21 GateDecisionResult (recovered directly or through a DecisionLogRef that cites it), release scope or work target, environment or scope, time window, gate profile, gate version, and direct support relation recovered through A.10 are recoverable. Open B.3 only when an assurance claim is being made.
Copied review summary or copied approvalTreat it as copied wording and a currentness cue. If the intended use relies on permission or authority, apply the matching row for each independently required claim, or its direct governing rule when no row applies. Gate passage still needs the A.21 decision. Performed Work still needs its actual performer identified and that performer’s A.13 core basis independently recovered and the dated occurrence independently admitted through A.15.1; if the relied-on account must also identify the assignment, check it separately through F.6. Reliance still needs the applicable direct evidence/currentness relation recovered through A.10.
Delegation chain with forwarded approvalEach link names delegator, delegatee, delegated operation or work class, affected work target, affected resource, affected claim, scope, window, the delegation record or relation permitting delegation, subdelegation allowance if any, revocation relation, currentness relation, and evidence relation. A forwarded approval is not delegated authority by copy alone.
System-role-assignment, revocation, assignment-state, or credential-status displayResolve an assignment claim to both its occurrence and declared U.SystemRoleAssignment species. Resolve the other claims to the assignment-state relation, state-changing speech act, context-state record, credential proof or credential-status result, or gate decision with freshness field, revocation relation, or revocation record; visual display cannot defeat a higher-priority revocation or supersession relation.
Conflicting source relationsDo not resolve by color, visual salience, copied wording, or apparent recency. Name source-relation order, the decision or rule establishing that order, freshness policy, and supersession rule; the work claim, reliance claim, or effect is contested until resolved, while source-finding and bounded reversible probes remain available.
Register-backed credential-status viewRecover the entry episteme, publication and the rule under which the register is authoritative for this claim. Then test only the direct status, assignment, grant, exercise or finding that the attempted use consumes, with its evidence/currentness and revocation conditions. Any asserted Work needs A.13 and independent A.15.1 admission; add F.6 only when assignment-bound attribution is needed. The entry may be authoritative under its rule, but presence alone establishes neither exercise nor non-violation.
Rollback command-like cueTreat the display as a cue; use A.6.A when action-invitation wording leaves its intended claim unclear. Recover any command, authorization, performed-work or result claim independently under the pattern that defines or tests it.
Generated explanation says “authorized”Use the explanation only to find source publications, claim-bound source relations, or required relations and results. If permission or authority is the live claim, route through the single branch above. The explanation itself supplies none of that branch’s objects and proves neither gate passage nor performed work.
Extracted source publication, rewrite, representation shift, explanation, then gate or release claimIdentify the operative claim and the basis required for the gate or release use. Return to the source-bearing side or repair a transformation when that use depends on a distinction, source relation or result no longer recoverable after the transformation. Retain independently established support and unaffected uses. Establish each required transformation, evidence, explanation, gate or assurance claim under its own rule before allowing the dependent use.
Repeated green-tile failures without recoverable source relationTreat recurrence as upstream source-relation repair work: expose decision refs, fix dashboard semantics, add claim-bound source relations and currentness, revise boundary wording, or add review cues so the acting user is not repeatedly forced to reconstruct missing source relation.

A.15.4:3.1 - Archetypal Grounding - Worked Dashboard And Approval Examples

Constructed dashboard case:

At 09:20 UTC on 2026-05-08, a green tile for Release-2026.05.08-prod points to an unavailable gate decision. The immediate question is whether the release gate passed; the engineer uses the tile for source finding and withholds that claim. The source now yields GateDecision-May08-prod: pass for that release in production during 09:00–10:00 UTC, under the applicable GateProfile, with its required evidence and currentness basis. Matching the release, environment and window supports gate-passage reliance. It establishes neither deployment nor any separate permission or readiness prerequisite. A later superseding block decision reopens this reliance and the decisions depending on it. The repair exposes the decision reference, scope and window on the tile, so the next receiver can follow that decision directly.

StepRequired record or relation
Question in this caseWhether the release gate passed for the named release, environment and window. The rows below identify the needed gate basis and separately conditional neighboring claims.
Gate decision recordCite the current A.21 GateDecisionResult (recovered directly or through a DecisionLogRef that cites it), gate profile, gate version, release scope or work target, scope, window, and replay or freshness pins. Without that record, the tile is not release authorization or gate passage.
Flow constraint-validity witnessCite A.20 ConstraintValidityResult and its witnessOrReason only when the claim is about flow constraint validity, not about the gate decision itself.
Evidence and currentness relationUse A.10 for the dashboard query, publication-carrier integrity, evidence refs, time, window, freshness field, revocation relation or revocation record, verifier context, relying context, and rival explanation such as stale display or copied status.
Assurance claimUse B.3 when the attempted use requires a separately named assurance claim, with its target, evidence basis, limitations, and reopen condition. Safety, compliance, trust, release confidence, or a characteristic label alone does not establish that requirement. Use A.15.5 for work-entry readiness and A.21 for a gate decision.
Repaired gate-use relianceWith the decision and evidence relation recovered, rely on gate passage only for the named release scope or work target, environment, gate profile, gate version, time, and window. A claim that deployment happened still needs its actual performer identified and that performer’s A.13 core basis independently recovered, the dated Work independently admitted through A.15.1, and the evidence or provenance relation needed for the relying context. If that claim must also identify the assignment under which deployment was performed, check the assignment separately through F.6.
Blocked overreadsThe dashboard color does not create approval, deontic permission, compliance proof, rollback success, work occurrence, or assurance by display.

Approval memo green-tile case:

An approval memo may carry an approval claim when it exposes the A.2.9 SpeechActRef, the identified actual performer, that performer’s independently recovered A.13 core basis, and the A.15.1 account that independently admits the speech-act Work. If the approval use must also identify the grantor assignment, or that assignment changes policy applicability, add actingSystemRoleAssignmentRef : U.RelationRef constrained to U.SystemRoleAssignment and use F.6 to compare its holder with the already identified performer. Keep affected release scope or work target, judgement context, time, window, publication-carrier refs, evidence refs, and the instituted effect separate. Authority is never supplied by the assignment. The memo supports only the bounded approval use defined in A.2.9; release, deployment, rollback, or other performed Work needs its own A.13/A.15.1 basis and any independently established support relation recovered through A.10 for reliance.

Credential-status and system-role-assignment-state green-tile case:

For a register-backed credential or assignment-state response, identify the entry episteme and its publication separately from the status assertion or SystemRoleAssignmentStateRelation. Apply the named register rule to determine which claim the entry supports, with the issuer/holder binding, relying situation, freshness and window it requires. Recover authorized entry-producing Work only when that rule or the current claim consumes it. Test the direct status relation or finding and its evidence under the selected §3 rule. A response’s presence alone supplies no further Work, gate, permission or evaluation result.

Situation viewpoint prompts:

Viewpoint or repair concernPrompt
Acting practitionerWhat can I safely do next without turning the encountered episteme or episteme publication into unsupported work or reliance justification?
Release engineerWhich gate decision is current, and does this question also require a separately established deployment Work or other prerequisite?
Source, gate, evidence, or assignment-record contactWhich source-currentness value, assignment-state relation or assertion, credential-status value, decision ref, or evidence relation needs exposure? Which direct source, publication, register, communication, access, or contact fact supports that request? For an allocation or duty to repair, apply §3.4 to its distinct predicate and case facts.
Audit or peer-review viewpointWhich prerequisite, object, and test in the §3 lookup must be recoverable? If permission or authority is current, which rows or direct governing rules answer the independently required claims?
Boundary claimantIs the operative claim clear? If wording still hides its predicate or governed value after F.19, use A.6 or A.6.B to recover it.
ManagerIs repeated ambiguity prerequisite-lookup or source-relation repair work rather than another manual check for the acting practitioner?
LLM user or tool userWhich required claim or result does the explanation help recover, and what basis does the proposed use require? Use A.10 when that evidence/provenance account must remain replayable.
Security or compliance source contactWhich revocation relation, currentness relation, proof, credential-status record, system-role-assignment-state assertion, source-relation order, or supersession relation needs exposure, and which direct source, register, communication, access, or contact fact supports asking for it? For a repair allocation or duty, use §3.4 to recover that claim’s rule and grounds and distinguish missing information from a failed test.
Model or data documentation stewardWhich intended use, evaluation condition, version, window, limitation, and evidence relation bound the model or data documentation?
Assurance viewpointWhich named claim has a B.3 assurance claim, with what assurance tuple, evidence relation, limitations, and reopen condition?

Use the prerequisite lookup in §3.5 once the direct question is clear; return to A.15.4 only if an appearance still hides that question or its basis.

For a state label intended to guide action, expose the source reference and the scope, time and currentness needed by that action. For example: Gate decision: pass; GateDecisionRef; release; environment; window. Add a denied overread only when it is locally plausible and changes the use; F.19 governs that wording decision.

For incident learning, retain only the content needed to explain or repair the overread:

  • encountered selected episteme, publication occurrence, form, or carrier
  • work or reliance claim under repair
  • required relation or result, its SubjectPatternLocator, and project-side reference
  • acting or affected System
  • a context field ending in ...SystemRoleAssignmentRef only when assignment identity matters to F.6 attribution or another direct relation that independently obtains
  • separately recoverable capability, authority, and responsibility claims when current
  • affected target, context, and window
  • missing or stale source, publication occurrence, source-bearing relation, register entry, or project-side reference
  • the direct source, publication, register, communication, access, or contact fact supporting a cheap exposure request
  • only for an allocation or duty to repair, its distinct rule, case facts and any unresolved ground under §3.4
  • plausible overread
  • safe disposition
  • smallest upstream repair.

Contestability and redress relation: when an authority-looking case affects assignment state, credential status, access, assignment, responsibility, release blockage, compliance claim, or safety-impacting Work, name the available challenge, review, redress, communication, source, publication, register, access, or contact relation before the work claim or reliance claim hardens. Recover the disputed source relation or claim, affected use or harm, allowed evidence or argument, possible disposition change, outcome route, and reopen trigger. Keep source exposure available under its own access conditions.

A claim that a System has a duty to conduct later review or repair needs that duty’s bearer, predicate and instituting basis; allocation and permission remain separate claims under §3.4. An unresolved duty limits that assertion, while a challenge can continue under its own established conditions.

Lintable overread cues:

Lint signalRequired relation or result named by value
Ambiguous approved, authorized, allowed, recommended or guaranteed wordingFirst read the full claim under F.19. If its governed meaning remains unclear, use A.6/A.6.B; route a permission or authority question through the branch above. A word alone selects no object.
Dashboard tile, credential-status color, system-role-assignment-state color, or release tile used as release evidence or gate passageFor a gate-passage claim, recover the A.21 GateDecisionResult; for another release claim, recover the result under its own governing pattern. Use A.10 when the needed evidence/currentness account must remain replayable. A displayed assignment-state label may express an assertion; evaluate that assertion’s state claim under A.2.5.
Register screenshot or entry used as status, permission, assignment or gate evidenceRecover the entry and publication, applicable register rule, direct object or finding, and required evidence/currentness. Identify any entry-producing, exercised or evaluation Work only when the rule or occurrence claim requires it, then apply A.13/A.15.1 and conditional F.6. A register entry may support the rule’s exact claim; its presence alone establishes neither actual exercise nor non-violation.
Generated explanation uses authorized, approved, or similar wordingRecover the claim and its governing rule. Use E.17.EFP when explanation-class ambiguity changes the use, and A.10 when a replayable evidence/provenance account is needed. For each required permission or authority claim, apply the matching row above or its direct governing rule.
Model card, datasheet, label, or note cited as readiness, safety, compliance, or release confidenceRecover the direct readiness, safety, compliance, or release claim and its criterion, intended-use match, evidence, and limits. Use A.15.5 for work-entry readiness, A.21 for a gate decision, and B.3 only for an independently current named assurance claim.
Provenance or attestation label cited as truth, safety, release, permission, or authorityRequire the bounded A.10 provenance/process-trace claim plus the applicable pattern and test for the relied-on truth, safety, release, permission, or authority claim. For the last two, use the single branch above; the label is not its result.
Evidence, assurance, gate, or work-occurrence words without the relation or result that carries that claim or effectRecover the independently established support relation through A.10, the separately named B.3 assurance claim, A.21 gate decision, or A.15.1 work-occurrence account as required by the attempted use.

Stress cases for practice:

CaseExpected A.15.4 disposition
Green release dashboard tile with no GateDecisionRef.Source-finding only; recover the A.21 GateDecisionResult, directly or through a decision log that cites it, plus A.10 evidence before gate-passage reliance.
Copied approval from last month.Treat the copy as a source-finding cue. Recover each permission or authority claim consumed by the intended use under the matching row above or its direct governing rule, with the currentness and evidence basis it requires.
Register-backed credential badge screenshot after revocation.Recover the entry, publication, status rule, direct status and required evidence/currentness/revocation basis. Add entry-producing Work only when the rule consumes it. A valid revocation blocks reliance even while the old entry remains visible.
Register entry says grant exercised; no violation, but matching actual Work is unavailable.Keep those claims unresolved. Recover the acted-on Work under A.13/A.15.1, the exercise predicate and the sufficiently complete current checked frame. A separate evaluation Work is needed only when that occurrence is claimed; it then needs its own basis. Add F.6 only for consumed attribution. Entry presence establishes neither result.
Generated explanation says authorized by policy.Recover the claim and its governing rule. Use E.17.EFP when explanation-class ambiguity changes the use, and A.10 when a replayable evidence/provenance account is needed. For each required permission or authority claim, apply the matching row above or its direct governing rule.
Boundary wording says guaranteed approved for production.Split the sentence through A.6 or A.6.B; use A.6.C for agreement-like or promise-bearing content and the single permission/authority branch above only for the permission or authority claim that remains.
Dashboard says green while decision log says blocked.Treat as conflicting source relations; name source-relation order, the decision or rule establishing that order, freshness policy, and supersession rule before the work claim or reliance claim is used.
CRISPR lab dashboard says the guide edit is ready.Treat the dashboard as orientation or source-finding until the protocol publication or protocol record, approval record or gate record, exact direct system-role-assignment occurrence when assignment identity matters, evidence relation, current lab context record, and U.WorkPlan for the intended edit are recoverable. Recover capability, authority, responsibility, permission, and Work attribution separately when current. If the question is full-kit or work-entry readiness for the intended edit, use A.15.5; the readiness tile still does not create biological-intervention authorization, deontic permission, safety, or performed Work.

A.15.4:3.2 - Archetypal Grounding - High-Impact Reliance-Repair Slice

In this constructed case, a lab manager sees CRISPR-guide-G42 ready and a copied approval. The intended use is to determine the next permitted preparation or intervention step. The local policy separately requires the following prerequisites; this is not a universal kit for all appearance-repair cases.

A.15.4 structured local note:
  RelianceAppearanceRef: B17-G42-GreenTile plus B17-CopiedApprovalMessage
  RelianceAppearanceKind: dashboard display plus copied wording
  WorkOrRelianceUseKind: intended work
  WorkOrRelianceUseRef: B17-GeneEditIntervention
  RequiredPositionEntries:
    - EntryId: B17-PROTOCOL
      SubjectPatternLocator: E.24.PUB
      DirectObjectKind: EpistemePublicationRelation
      ProjectSideObjectRef: B17-ProtocolPublication-e5
      RequiredPostureOrCurrentness: obtains; protocol edition e5 is currently available to the B-17 lab audience for this intervention use
      DependencyOnAttemptedUse: supplies availability of edition e5; selecting that edition for the intended Work also requires the intervention's protocol-applicability rule and case facts
    - EntryId: B17-GRANT-ACT
      SubjectPatternLocator: A.2.9
      DirectObjectKind: U.SpeechAct occurrence
      ProjectSideObjectRef: B17-GrantSpeechAct
      RequiredPostureOrCurrentness: actual performer identified; performer's A.13 core basis independently recovered; speech-act Work independently admitted through A.15.1; the grantor assignment required by A.2.8.PER:4.7 is recoverable and F.6 establishes that the act was performed under it, with its holder matching the performer; recognized by the current grant policy
      DependencyOnAttemptedUse: grounds B17-InterventionGrant; the act itself is not permission
    - EntryId: B17-GRANT
      SubjectPatternLocator: A.2.8.PER
      DirectObjectKind: GrantedPermissionRelation@Context occurrence
      ProjectSideObjectRef: B17-InterventionGrant
      RequiredPostureOrCurrentness: obtains and is current for the exact beneficiary, intervention action, sample batch, scope, and window, with no valid revocation or supersession ending the grant
      DependencyOnAttemptedUse: the intervention requires this strong grant
    - EntryId: B17-CONFLICT
      SubjectPatternLocator: A.2.8.PER
      DirectObjectKind: PermissionNormConflictFinding@Context
      ProjectSideObjectRef: B17-InterventionPermissionNormConflictFinding
      RequiredPostureOrCurrentness: current disposition=settledByApplicableRule; B17-ConflictPrecedenceRule-e2 matches this beneficiary, intervention action, sample batch, scope, and window and selects the grant for this attempted intervention
      DependencyOnAttemptedUse: an unresolved or norm-selecting disposition blocks AllowedUseNow for this intervention; the finding neither revokes nor ends B17-InterventionGrant
    - EntryId: B17-CONFLICT-EVIDENCE
      SubjectPatternLocator: A.10
      DirectObjectKind: C.2.1 episteme carrying an A.10 evidence-provenance account
      ProjectSideObjectRef: B17-ConflictFindingEvidence
      RequiredPostureOrCurrentness: supports only the current B17-InterventionPermissionNormConflictFinding disposition and the applicability of B17-ConflictPrecedenceRule-e2 to this exact attempted use
      DependencyOnAttemptedUse: supplies the evidence/currentness path for B17-CONFLICT without becoming the finding, rule, or grant
    - EntryId: B17-GATE
      SubjectPatternLocator: A.21
      DirectObjectKind: GateDecisionResult
      ProjectSideObjectRef: B17-InterventionGateDecision-e2
      RequiredPostureOrCurrentness: current GateDecisionResult with decisionValue=pass under the applicable GateProfile application, with its DecisionLog recoverable
      DependencyOnAttemptedUse: the current lab policy separately requires gate passage; this decision does not create the grant
    - EntryId: B17-WORK-ENTRY
      SubjectPatternLocator: A.15.5
      DirectObjectKind: C.2.1 result episteme carrying an A.15.5 readiness claim
      ProjectSideObjectRef: B17-WorkEntryReadiness-e3
      RequiredPostureOrCurrentness: current A.15.5 readiness claim for the exact plan item and intended B17-GeneEditIntervention in B17-GeneEditWorkPlan-e4, performer, kit, context, and entry window; ReadinessResultValue=ready, seeking a separately governed commitment is its stated next move, and no StopCondition is triggered
      DependencyOnAttemptedUse: the current lab policy separately requires work-entry readiness; readiness does not create the grant or gate decision
    - EntryId: B17-ASSIGNMENT
      SubjectPatternLocator: A.2.1
      DirectObjectKind: B17EditorSystemRoleAssignment, a direct species of U.SystemRoleAssignment
      ProjectSideObjectRef: B17-EditorAssignment
      RequiredPostureOrCurrentness: obtains, names the intended performer as holder, and covers the proposed Work window
      DependencyOnAttemptedUse: supplies the holder-and-kind condition consumed by the grant beneficiary branch; any later precise Work attribution requires its own F.6 check after Work admission
    - EntryId: B17-PROTOCOL-EVIDENCE
      SubjectPatternLocator: A.10
      DirectObjectKind: C.2.1 episteme carrying an A.10 evidence-provenance account
      ProjectSideObjectRef: B17-ProtocolPublicationEvidence
      RequiredPostureOrCurrentness: supports only the claim that B17-ProtocolPublication-e5 obtains and exposes protocol edition e5 for this lab audience and intervention use throughout the decision window
      DependencyOnAttemptedUse: supplies the publication/currentness evidence required for B17-PROTOCOL without standing in for that publication relation
    - EntryId: B17-GRANT-EVIDENCE
      SubjectPatternLocator: A.10
      DirectObjectKind: C.2.1 episteme carrying an A.10 evidence-provenance account
      ProjectSideObjectRef: B17-InterventionGrantEvidence
      RequiredPostureOrCurrentness: supports only the claim that B17-InterventionGrant obtains and is current for this beneficiary, action, batch, scope, and window, including the instituting act, policy, revocation, and supersession sources used by that claim
      DependencyOnAttemptedUse: supplies the evidence/currentness path required for B17-GRANT without creating or replacing the grant
    - EntryId: B17-GATE-EVIDENCE
      SubjectPatternLocator: A.10
      DirectObjectKind: C.2.1 episteme carrying an A.10 evidence-provenance account
      ProjectSideObjectRef: B17-InterventionGateEvidence
      RequiredPostureOrCurrentness: supports only the claim that B17-InterventionGateDecision-e2 is the current GateDecisionResult with decisionValue=pass for this attempted use under its GateProfile application, with its DecisionLog recoverable
      DependencyOnAttemptedUse: supplies the evidence/currentness path required for B17-GATE without becoming gate passage
    - EntryId: B17-ASSIGNMENT-EVIDENCE
      SubjectPatternLocator: A.10
      DirectObjectKind: C.2.1 episteme carrying an A.10 evidence-provenance account
      ProjectSideObjectRef: B17-EditorAssignmentEvidence
      RequiredPostureOrCurrentness: supports only the claim that B17-EditorAssignment obtains, has the intended performer as holder, and covers the proposed Work window
      DependencyOnAttemptedUse: supplies the evidence/currentness path required for B17-ASSIGNMENT without creating or extending the assignment
    - EntryId: B17-PLAN
      SubjectPatternLocator: A.15.2
      DirectObjectKind: U.WorkPlan
      ProjectSideObjectRef: B17-GeneEditWorkPlan-e4
      RequiredPostureOrCurrentness: current plan for the intended performer, intervention, sample batch, method, resources, and window; not actual Work or permission
      DependencyOnAttemptedUse: coordinates intended Work; after the other entry prerequisites pass, seek the separately governed commitment required by this case before starting
  AllowedUseNow: source-finding and prerequisite refresh only; do not intervene while any entry is absent or fails its required posture or currentness
  AppearanceOverreadBlocked: tile color and copied message do not authorize biological work or prove safety
  RecoveryOrStopCondition: revisit each missing or failed prerequisite and its affected dependencies; retain unchanged applicable results. The conflict must have a current grant-selecting disposition, the gate must pass, and readiness must be ready for this use. Before the stated commitment-seeking next move, the selected protocol must also be applicable under the rule for this intervention. Intervention remains blocked until the separately required commitment and all other entry conditions obtain.

The note identifies the publication prerequisite; the protocol-selection rule and its case facts remain to be recovered. Keep that applicability question separate and add its prerequisite to the account when recovered. The present result remains source finding. Once all prerequisites for the next move are satisfied, follow the readiness result’s stated commitment-seeking action; the commitment has its own rule and instituting basis.

Named-but-revoked grant near-miss. Suppose B17-InterventionGrant and its complete-looking record are present, but policy-valid B17-GrantRevocation took effect before the intervention window. The B17-GRANT entry then fails RequiredPostureOrCurrentness because the grant no longer obtains. A current protocol, plan, GateDecisionResult with decisionValue=pass, readiness result, and green tile do not repair that failure: AllowedUseNow remains source-finding and prerequisite repair, and the intervention stays blocked.

A.15.4:4.1 - Bias-Annotation

A.15.4 corrects appearance-based reliance. A publication face, dashboard tile, credential view, generated explanation, copied approval, provenance mark, schema wording, or API response can look ready for work before the required relation or result is established for that use. The repair keeps the reliance appearance separate from the source relation or other relation that supports the claim.

It also corrects over-repair bias. Retain a sufficient ordinary result, choose rows when they help comparison or inspection, and persist the analysis as a reusable claim only when a later use needs it.

A.15.4:4 - Conformance Checklist

IDRequirement (Normative Predicate)Purpose and Rationale
CC-A15.4-1 (One attempted use; proportionate prerequisite account)Name the attempted use. A sufficient stop or source-finding result may identify only the first missing prerequisite; before allowing the attempted use, establish every prerequisite it consumes. A sufficient ordinary note or accessible source account may carry these prerequisites. Keep their subject predicate and test, participants, required posture/currentness and dependency on the attempted use recoverable, with the kind and native project-side reference detail required by the governing rule or receiving use. If RequiredPositionEntries is selected, keep its five named fields matched to each direct object; use one row per object and retain native reference types rather than coercing them into a generic U.EntityRef list. If a prerequisite is absent or fails its posture, AllowedUseNow stays at the safe narrowed use.Keeps the ordinary path light and every prerequisite under the rule or test that defines it.
CC-A15.4-2 (P2W publication use boundary)A principle scheme, functional diagram, scenario, screen, or explanation that exposes a P2W chain guides only the project use selected for it: method-family selection, selection of a particular Method, work planning, reliance on dated Work, or use of a work-result record or measurement. Each claim retains its own governing pattern. Claims outside that selected use require their own relation or result and source relation named by value.Keeps P2W publication use tied to the work use under repair instead of turning publication form into project authority.
CC-A15.4-3 (Lowering and refresh)When a prerequisite or its applicable test cannot be recovered, state a supported narrower use or stop. Name the first failed prerequisite and its return or refresh condition. Before proceeding, keep every prerequisite consumed by that use separately recoverable, with the native reference detail required by its governing rule or receiving use.Preserves a supported narrower use while the required prerequisite is recovered.
CC-A15.4-4 (Reopening judgment)Before allowing the attempted use, establish each consumed prerequisite under its own criterion and applicability, currentness and evidence rules. Recheck changed or failed premises and their dependents; retain unchanged applicable results. Keep permission/norm conflict separate from grant currentness: an unresolved or norm-selecting result blocks the affected use. A separately required gate and readiness result must satisfy their direct rules; neither substitutes for permission or a required commitment.Prevents named records and green displays from replacing the current basis of the attempted use.
CC-A15.4-5 (Register source and effect)For register-backed reliance, distinguish the entry episteme, publication, authoritative-source rule and the direct relation or finding. Recover entry-producing, exercised or evaluation Work only when the rule or occurrence claim consumes it; each asserted Work needs A.13 and independent A.15.1 admission. Add F.6 only for assignment-bound attribution. A failed F.6 test alone leaves independent Work admission intact; recheck any admission premise also affected by that finding. Use the entry only for claims supported under its rule and evidence/currentness basis.Preserves rule-governed register authority while rejecting inference from entry presence alone.

A.15.4:5 - Common Anti-Patterns and How to Avoid Them

  • Appearance as source relation. A dashboard tile, credential display, copied approval, generated explanation, provenance label, command-like cue, or composed source-relation chain is used as if presentation itself carried the work-relevant source relation. Name the attempted use, recover the required prerequisite and its test, and add a project-side reference when that rule or use requires it. If the basis is missing, lower only the unsupported reliance.

A.15.4:6 - Consequences

ConsequenceTrade-off and costMitigation
Work can continue at the lightest use supported by a recovered relation instead of stopping on every suspicious display.The practitioner names the claim being made and the required relation or project reference before relying on the appearance.Retain a sufficient ordinary result; use rows when they help comparison or inspection.
Appearance-based approval, evidence, assurance, gate, and work-occurrence overreads are blocked.Some convenient dashboard or copied-text shortcuts become unusable until source-currentness relation is recovered.Keep orientation, source-finding, and bounded reversible probes available when no external-impact reliance is being made.
Repeated ambiguity becomes prerequisite-rule or source-relation repair work rather than repeated manual reconstruction.The repair may reveal missing register entries, stale selected source epistemes, non-current or unresolved EpistemePublicationRelation occurrence refs, or underspecified gate and evidence relations.Assign only prospective repair work or source-relation gap work; do not backdate evidence, gate passage, work occurrence, or assurance.

A.15.4:7 - Rationale

Practitioners often encounter a claim through a display, generated explanation, copy or credential view before its basis is recoverable. A.15.4 connects that encountered expression to the predicate and evidence required for the attempted use. The practitioner can retain a useful source-finding continuation while withholding an unsupported stronger claim.

Once the required §3 relation or result is recovered, apply its own predicate and test. Resolve a defining or constraining ClaimGraph only when rule identity or edition changes this use; an ordinary PatternID is otherwise enough.

A.15.4:8 - SoTA-Echoing

Claim needSource contributionNamed sourceFPF applicationShortcut rejected
Dynamic authorization or policy-response displays need the requested operation and the policy conditions relevant to this use.NIST SP 800-207 recommends resource access per session under dynamic policy. Cedar 4.5 evaluates a principal–action–resource–context request against policies and entity data. OpenFGA checks a user’s modeled relation to an object using an authorization model and relationship tuples, with conditions and request context where applicable.NIST SP 800-207 Zero Trust Architecture; Cedar Policy Language Reference Guide v4.5; OpenFGA authorization concepts.Name the attempted work or reliance use and the policy inputs it consumes, including the affected resource or work target, situation, policy edition and qualification window when material. Recover the direct permission or authority result required by that use.Apply the policy, currentness and bounded-use conditions; reject treating policy-looking output as permission or authority by display alone.
Register-backed credential status or system-role-assignment state needs source and effect separation.Verifiable Credentials Data Model 2.0 distinguishes issuer claims, holder presentations, credential verification and purpose-specific validation. Its credentialStatus property provides information for checking status under a selected scheme. Bitstring Status List v1.0 specifies how to retrieve and verify the referenced status-list credential and read the relevant status entry.W3C Verifiable Credentials Data Model v2.0; Bitstring Status List v1.0 as one status scheme.Treat the entry as authoritative source only under the named rule for its exact effect; test the direct relation or finding and the evidence and currentness claims separately.Use the register under its named authority and status rule; verify issuer/holder binding, current status and the particular claim the intended use consumes.
Provenance and attestation marks need a checked link to the underlying assertions and a defined scope for using those assertions as evidence.C2PA 2.4 binds provenance assertions to assets through signed claims and defines validation of their bindings and signatures. SLSA v1.2 build provenance describes a build’s inputs, builder and execution; verification checks the artifact and provenance against trusted identities and expected values. in-toto Statement v1 binds a typed predicate to artifact subjects identified by digest.C2PA Specifications 2.4; SLSA v1.2 build provenance and artifact verification; in-toto Statement v1.Follow the mark to the independently established provenance or process-trace relation. Use A.10 for bounded reliance on it and the direct subject pattern for any further truth, release, permission, gate or Work claim.Use validated provenance as evidence within its supported scope; reject inferring truth, release authorization, deontic permission, gate passage, assurance or work occurrence from a mark alone.
Change, gate, release, and approval displays need decision, schedule, and performed-work separation.ISO/IEC/IEEE 15288:2023 describes system life-cycle processes; the historical ISO/IEC/IEEE 12207:2017 describes software life-cycle processes, activities and tasks. ITIL 4 Change Enablement addresses change-risk assessment, authorization and scheduling. ITIL 4 Release Management addresses making new or changed services available under organizational policies and agreements with service consumers.ISO/IEC/IEEE 15288:2023 and the historical ISO/IEC/IEEE 12207:2017 life-cycle process frameworks; the latter was superseded by 12207:2026. ITIL 4 Change Enablement and Release Management.An approval-looking display supports reliance only when it exposes the §3 branch object, GateDecisionResult, U.WorkPlan, or dated A.15.1 Work occurrence required by the attempted use, plus the evidence/currentness relation needed for reliance.Adopt decision, permission/authority, schedule, and performed-work separation; reject a green tile, copied approval, or generated explanation as any of those by appearance.

Source scope and FPF application. The FPF applications and rejected shortcuts above are this pattern’s adaptation of the cited contributions. Use §3 to identify the relation or result required for the intended reliance, then inspect the relevant content and case facts under its authority, evidence and currentness conditions. Verified provenance may support a Work claim within its recorded scope; a visible mark alone is insufficient.

A.15.4:9 - Relations

  • Cluster relation: A.15.4 is a cluster member under A.15 for work-relevant appearance-based reliance repair; it does not replace the A.15 system-role-kind, assignment, Method, plan, and Work kernel.
  • Uses: E.17, E.17:5.1b, E.17:5.1c, and E.17:5.1d for source-relation and use-boundary vocabulary; E.17.EFP for explanation faithfulness and source-finding; A.16.0 when source lineage, branches, retirement, loss or a responsibility handoff needs reviewable history; A.6, A.6.B, and A.6.C for boundary wording; A.10 for evidence and currentness; B.3 for assurance; A.15.5 for work-entry readiness; A.20 for constraint validity; A.21 for gate decisions; A.2.1 for system-role assignments; A.2.5 for assignment-state relations; A.13 for actual performers’ core agency bases; A.15.1 for independently admitted dated Work; F.6 only when the receiving result must also identify the assignment under which that Work was performed; and A.2.8, A.2.8.PER, and A.2.9 only through the single permission and authority branch in §3.
  • E.10 and E.10.MOVE relation-selection rule: When the direct question is already known, apply its subject pattern directly or use the §3 lookup. Use E.10.MOVE when work-entry or readiness wording still hides the governed claim. Use E.10.ARCH when the distinction among a world-side fact, reusable declaration, claim or report, and representation remains unresolved. Permission or authority uses the single §3 branch. A.15.4 starts only while a required relation or result is still hidden by the reliance appearance.
  • A.15 boundary relation: use A.15 directly when the remaining question under repair is system-role-kind, assignment, Method, plan, and Work alignment rather than a reliance appearance being used as a reason for Work or reliance.

A.15.4:9.1 - C.29 mathematical-lens use relation

Use C.29 when choosing or transferring a mathematical representation could answer the reliance question or expose a limit on the proposed inference. Select the mathematical object and its correspondence to the situation, identify preserved and omitted distinctions and assumptions, and derive the consequence for the prerequisite test. State what would defeat that use. An adequate local calculation needs no additional lens account. For a Method, MethodDescription, plan or performed Work claim, use A.3.1, A.3.2, A.15.2 or A.15.1 respectively; A.15 explains their alignment.

A.15.4:9.2 - P2W Result-Related Source Boundary

When a P2W use under E.18.1 produces result wording, use this pattern only when a reliance appearance such as publication, dashboard, generated explanation, copied statement, provenance mark, schema wording, API wording, or composed source-relation chain is about to justify result-related work or reliance by appearance.

For the result-related claim, recover the prerequisite and test its basis under its direct rule; retain a project-side reference when that rule or intended use requires it. If the applicable basis is missing, keep the appearance at orientation or source-finding and block only the unsupported result-related work or reliance.

A.15.4:9.3 - Lowering, Repair, and Refresh Conditions

Lower only the attempted use that depends on an unrecovered prerequisite or applicability condition; retain independently supported uses, including orientation, source-finding or a probe permitted under its own conditions.

When a change affects the appearance-to-use account, repair the local note or persisted claim. Apply the pattern governing each affected prerequisite to repair that value.

Before a consequential reliance use, confirm that the needed grounds remain applicable and sufficiently current. Reopen a changed, missing or expired prerequisite and every dependent use affected by it; retain unchanged applicable results. Apply the direct pattern to repair the failed premise, then reconsider the narrow disposition under A.15.4.

A.15.4:End

A.15.5 - Work-Entry Readiness and Full-Kit Preparation

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

At a glance. Judge whether an intended performance in a WorkPlan and PlanItem satisfies a local work-entry criterion at the stated time. Apply that criterion to the current inputs it requires. Identify a separate checking Work only when its dated occurrence is claimed. Keep the result and its grounds recoverable for the receiving use; readiness creates neither the intended Work nor its prerequisite facts.

Use this when. Use this pattern when a team is about to commit, release, launch, or admit intended work and needs to test its work-entry conditions against the available facts and preparations.

Primary EntityOfConcern. The C.2.1 readiness-result episteme has the U.WorkPlan being judged as its exact EntityOfConcern. Its ClaimGraph designates the relevant PlanItem, intended performance, criterion, evaluated facts, verdict, and applicability window. Preserve the plan’s exact intended-work kind or work-family classification when that distinction is current; it remains ClaimGraph content and does not instantiate a dated U.Work. The plan names the target U.Method; cite a separately constituted U.MethodDescription episteme only when the readiness criterion or planned use relies on that exact description. The intended-performance designator, intended-work kind, plan item, method, and description are not a dated target U.Work occurrence.

First output. A readable result identifying the WorkPlan, PlanItem and intended performance; criterion and evaluation time; readiness value; consumed input propositions and their qualification intervals; reliance window; and stop or recheck condition. Add a checking-Work reference only when that occurrence matters. Inputs keep their own predicates and identities.

Ordinary route. Identify the plan content, criterion and evaluation time. Check the criterion against its current inputs and return ready, readyWithKnownGaps, notReady or unknown, with the reliance window and stop or recheck condition. Reuse applicable input results. Stop when this answers the receiving question; add a separate checking Work, result-episteme reference, gate, permission or assurance claim only when the use needs it.

When degraded support, handoff, or continuation-state evidence can change work entry, use the present-WorkPlan branch of A.15.8 to test the proposed performer, support, and state configuration, then return here with its bounded result. Ordinary full-kit checking does not require A.15.8.

What this buys. A team can decide the next bounded move—start no work yet, prepare a missing input, recheck, or submit declared checks to a gate—under the criterion and the entry conditions required.

Not this pattern when. Use A.15.2 for the work plan itself, A.15.3 for planned slot fillers, A.15.1 for dated performed work, A.21 for gate decisions, A.15.4 only when a reliance appearance is already being used as a reason for work or reliance before the subject pattern slot, relation, or project-side reference is named, B.1.6 for resource aggregation after work, E.18 for transformation-flow structure, and E.18.1 for P2W carry-through from accepted problem-side material.

A.15.5:1 - Problem Frame

Teams often say that work is “ready”, “full-kitted”, “committed”, “green”, “released”, or “good to start.” Those words can point to different FPF values: an intended WorkPlan, a PlanItem baseline, a performed preparation activity, a gate decision, a source-currentness relation, resource availability, or resulting performed work.

A.15.5 gives the work-entry readiness question a local criterion and result semantics. A readiness judgement is pre-entry unless a recheck after launch or post-launch variance claim is explicitly current. It may use established preparation or checking Work as an input.

A.15.5:2 - Problem

Without one local work-entry readiness claim and result semantics:

  1. Full-kit preparation becomes an umbrella for planning, source relations, gate passage, and performed work.
  2. A green tile or ready label is treated as a GateDecisionResult.
  3. Declaration-local planned-filling content inside the WorkPlan is overread as evidence that the planned values were prepared or used.
  4. Resource readiness is confused with resource consumption.
  5. A committed item becomes “done” by position in a board, not by a separately established completion claim about dated U.Work.

A.15.5:3 - Forces

ForcePressure
Work-entry speedTeams need a short readiness result before work entry.
Open-world disciplineAn input omitted from one criterion is not thereby absent; an unavailable required fact returns unknown unless an applicable explicit failure condition is established.
Plan and work splitA readiness claim can cite intended work and performed preparation or checking Work without becoming performed target Work.
Gate separationAn A.21 gate may consume a readiness result as a declared check input, but readiness does not publish a GateDecisionResult.
Full-kit usefulnessFull-kit thinking is valuable when it states what must be known, prepared, reserved, or checked before work starts.

A.15.5:4 - Solution

State readiness as a domain-local result about the identified plan content. When the result needs its own reference, identify its C.2.1 episteme; retain a durable representation when later access requires it.

Full-kit use. Use the plan, input facts and readiness result needed by the work-entry question. The source contribution and limits of the TameFlow adaptation are stated in §11.

A.15.5:4.1 - One work-entry readiness claim

Start with one ordinary sentence:

At evaluation time T, criterion C applied to intended performance I in PlanItem J of WorkPlan P yields readiness value R for use through window V; stop or recheck when Q occurs.

P is a WorkPlan episteme; J and I are its plan-local ClaimGraph content. A.15.3 applies when that content selects a member of an admitted declaration. C is the criterion episteme applicable to that item and evaluation time. R is one local ReadinessResultValue. If the account also identifies a dated checking occurrence W, admit it independently under §4.2’s A.13/A.15.1 rule and add F.6 only for a consumed assignment-bound claim. The readiness verdict remains separate from that Work, a gate decision, permission or commitment.

The local value family is:

  • ready — every input required by C is determined and satisfies C for V;
  • readyWithKnownGaps — C explicitly admits the named gaps for this bounded use, every non-waived input is determined and satisfied, and V plus the stop condition expose the remaining risk;
  • notReady — an applicable failure or closure condition in C is determined for this case; and
  • unknown — one required fact, currentness result, predicate, or applicability basis cannot be determined, and no already determined applicable failure or closure condition settles the result as notReady. Absence of an assertion or persisted episteme is not by itself notReady.

When the result needs a separate identity, its C.2.1 episteme has P as EntityOfConcern and a ClaimGraph stating J, I, C, R, the evaluated facts, evaluation time, reliance window and recheck condition under the effective reference scheme. Include W only when its occurrence is a claimed input. C.2.1 supplies identity. For reusable predicate semantics use A.6.RCD’s corresponding branch; open relation-kind admission only when a receiving use needs distinct readiness occurrences.

When reporting what a particular evaluation returned, identify its actual application and result binding or a direct evaluation-result predicate with its obtaining facts (A.15.1:4.6). Retain the ordinary result format when the receiving use asks for readiness itself.

The result episteme states the readiness judgement. If a current claim says that exact checking or preparation Work first constituted that episteme, recover that local entity-identity inception claim under A.15.PROD.

A.15.5:4.2 - Readiness criterion and full-kit inputs

Use one readiness criterion when the entry question depends on what must be known, prepared, reserved, gathered, communicated, assigned, or pinned before work starts. The criterion states:

  • the exact WorkPlan and its present EntityOfConcern, PlanItem, intended-performance designator, any exact intended-work target and intended outcome or value claim current in the plan, any current intended-work kind or work-family classification, target U.Method, evaluation time, and applicability window it judges;
  • each required positive or negative predicate, the allowed named gaps if any, and the rule for ready, readyWithKnownGaps, notReady, and unknown;
  • which changed fact, expired interval, new conflict, source revision, or resource or assignment change ends reliance; and
  • the stop, degraded-use, preparation, or recheck action for each non-ready result.

Full-kit thinking helps recognize possible inputs. Check only the input claims that C consumes:

  1. exact A.15.2 plan content and any A.15.3 planned fillings, with the declaration member and conditions that give each filling meaning;
  2. current information, source-currentness, publication, measurement, evidence, or assurance claims under their subject patterns;
  3. resource-availability or reservation claims, intended performer Systems and local system-role-kind conditions, any already obtaining occurrence of an exact directly declared U.SystemRoleAssignment species when C requires an assignment, capability threshold or fit result, and commitment claims when C uses them; plus any current work-in-progress or load and flow-policy claims under the pattern that defines their counted work, boundary, threshold, and qualification window;
  4. preparation or checking results required by C, and separately admitted preparation/checking Work only when its occurrence is consumed by the criterion;
  5. prospective A.2.8.PER grant, non-prohibition, or conflict facts and their qualification windows when permission is current; and
  6. an exact A.21 GateDecisionResult only when a current A.21 profile application governs the declared check applications and their mappings to that decision. The gate decision remains a separate result.

A post-launch variance or recheck result may enter only after the target Work is actual and only through the measurement, comparison, evaluation, resource, temporal, acceptance, or other pattern that defines that result. Name the target Work, comparison or evaluation rule, local result, qualification window, and subject pattern. It may trigger or inform an explicitly marked recheck; it neither proves that readiness held before entry nor rewrites the earlier readiness result. For each input, name the subject pattern, exact proposition or relation occurrence, and the interval or currentness result on which this readiness check relies. A generic input, evidence, context, resource, assignment, or policy reference supplies none of those facts. Omission says only that the current criterion did not consume that input; it does not prove absence.

Full-kit preparation can include gathering information, coordinating intended performer Systems and local system-role-kind conditions, producing a missing source U.Episteme or source publication, reserving a resource, pinning a planned filling, or creating shared understanding. When a dated occurrence is claimed as U.Work, actual performance and the admission basis below must be established. Plan the preparation beforehand; cite its actual result or admitted Work only after the corresponding facts are established.

For every cited preparation or readiness-checking Work occurrence, apply the complete A.15.1:4.0–4.1 admission test. Establish the common A.1:4.2 construction of that same candidate, each actual performer’s A.13 core, grounded performance history following at least one identified Method, temporal extent, and the factual conditions of a locally declared relation containing the complete occurrence within a System boundary. Admit the candidate, then state its typed Method-enactment and containing-System relations. Only when the readiness claim needs precise assignment-bound attribution, establish F.6 afterward through the same obtaining A.13 assignment and keep its declared species, participants, holder, coverage, and exact Work-assignment link recoverable. Name another enacted Method, boundary, direct participant relation, or A.6.1 binding when the readiness claim uses it. A planned preparation task remains A.15.2 content until the occurrence facts obtain.

Boundary with planned fillers and appearance-based reliance. An ordinary missing plan choice stays with A.15.2. Use A.15.3 when the proposed choice is declaration-local planned-filling content: recover the actual declaration member and its meaning and use conditions. A known evidence, currentness, publication, gate, permission or assurance claim goes directly to its subject pattern. Use A.15.4 while an appearance is being relied on before the required predicate and its basis have been recovered.

A.15.5:4.3 - Commitment and Launch Boundary

Keep commitment facts separate from the readiness value. The criterion may consume current commitment claims and their qualification intervals, but ready, readyWithKnownGaps, notReady, or unknown does not mean committed, institute a commitment, discharge one, or authorize entry. State the practical next move—stop, prepare, probe, seek a separately governed commitment, submit to a gate, launch only under its separately satisfied entry conditions, or recheck—as the result’s bounded use and return condition, not as another ontic status family.

The older labels readyForProbe, readyForCommitment, committed, blocked, and requiresGateDecision therefore resolve to a local readiness value plus an explicit next move, commitment claim, stop, or gate question; they are not additional ReadinessResultValue members.

Use A.2.8.PER when a pre-entry readiness criterion consumes permission material. Name each value and its own qualification: a current GrantedPermissionRelation@Context occurrence with its beneficiary, permitted-action specification, U.ClaimScope, and validityWindow; a distinct NonProhibitionFinding@Context with its frame and evaluationWindow; and any PermissionNormConflictFinding@Context with its overlapWindow and disposition. For a settled conflict, retain the applicable precedence rule and its qualification, or the current resolution result and effectiveWindow, according to A.2.8.PER:4.6. Non-prohibition is not a grant, and a grant does not itself settle a conflict. An unresolved conflict limits the readiness use under C; the affected action remains blocked under the permission rule. Cite PermissionExerciseRelation@Context or NonViolationFinding@Context only for already dated Work: either as evidence about a different Work occurrence or in an explicitly marked post-launch recheck after the target Work is actual, retaining its own exerciseInterval or evaluationWindow. Those retrospective findings support their named past claims; prospective grant, capability, readiness and entry claims need their own current grounds.

Use A.21 when a current profile application governs the declared check applications and their mappings to a distinct GateDecisionResult. Keep that result, scope, currentness and qualification window recoverable. Use DecisionLogRef when a log supplies the access, audit or replay path or the applicable policy requires it.

A.15.5:4.4 - Relation to A.15 Family

Current claimSubject pattern
Intended target work and horizonA.15.2 U.WorkPlan.
Planned fillings before workA.15.3 declaration-local planned-filling content inside the U.WorkPlan.
Preparation activity that actually happenedA.15.1 U.Work.
Target work that actually happenedA.15.1 U.Work.
Readiness before work entryA.15.5 local result claim; C.2.1 identifies a result episteme when that content needs its own reference.
Resource budgets or reservations before workA.15.2 plan content plus the exact predicate and source for the current resource-availability or reservation claim; A.15.5 cites the current claim only when the criterion consumes it.
Resource consumption by workB.1.6 plus A.15.1.

A.15.5:4.5 - Relation to P2W and Pattern Use

When E.18.1 carries accepted problem-side material to a readiness question, E.18.1 names that carry-through relation and cites A.15.5 for the readiness result. When a user needs to know which pattern to use before readiness is current, use E.11.PUR.

A.15.5:5 - Archetypal Grounding - Worked Slices

The following constructed cases stipulate their project facts and illustrate the separate readiness, occurrence and reliance questions.

A.15.5:5.1 - Fixture deformation test

Situation. An accepted cooling-fixture ProblemCard has been carried through E.18.1 into WorkPlan-LAB-043 : U.WorkPlan; that P2W carry-through creates neither readiness nor target Work. Its PlanItem-TEST-043 designates possible future performance planned-fixture-deformation-test-043, classifies the intended work as fixture-deformation testing under the plan’s current scheme, selects FixtureDeformationTestMethod-E2 : U.Method, and relies on FixtureDeformationTestProcedure-E5 : U.MethodDescription with that admitted Method as its exact EntityOfConcern and substantive setup-limit claims under A.3.2. The plan records specimen and instrument choices labeled SFI-043. To use them as A.15.3 planned-filling rows, recover the selected declaration, its members and their actual-use conditions; until those are recovered, retain the ordinary plan choices and leave their declaration-local filling interpretation unresolved. The plan also records planned resource reservation FixtureBayReservation-043 and intended performer-system and FixtureTestTechnicianSystemRole conditions. These choices remain content of this WorkPlan.

FixtureTestEntryCriterion-E2 requires, for the proposed 09:00–09:30 UTC start window on 2026-07-27, a resolved specimen identity, heat-flow invariant claim, boundary-condition plan, sensor-calibration result, selected fixture-drawing edition, resource-availability claim, and fixture-test-technician assignment, all current for this use. FixtureTestTechnicianAssignment is a directly declared U.SystemRoleAssignment species. It defines the holder and assigned-kind positions, uses FixtureTestSystemRoleKindDomain, requires FixtureTestTechnicianSystemRole, and applies to this laboratory test. Its obtaining occurrence FixtureTestTechnicianAssignment-043 has FixtureTechnicianSystem-043 as holder and covers the proposed start window. SFI-043 preserves the planned specimen and instrument choices; their actual preparation or use needs its own facts. The calibration result, its A.10 evidence path and currentness result, and the E.17 drawing-edition publication use remain separate inputs. The criterion explicitly treats known expiry or a recorded unresolved required-input status as failure and returns notReady. If the input or its status cannot be determined and no such failure is established, return unknown. A change to a consumed input, assignment coverage, resource availability or start window reopens the affected readiness conclusion; unchanged applicable input results remain reusable.

LabMetrologySystem-2 and LabOperationsCoordinatorSystem-1 are independently admitted Systems. For this constructed case, CalibrationCheckingSystemRole requires condition-sensitive calibration checking, and ReadinessCheckingSystemRole requires selection of readiness/preparation actions against the entry criterion; the stipulated observations support both classifications for this checking scope and window. The directly declared LabMetrologyAssignment and LabOperationsCoordinationAssignment species establish their holder/kind meanings, and case facts make RA-LabMetrology-2-E7 and RA-LabOperationsCoordinator-1-E4 obtain for those Systems and local kinds throughout 08:40–08:50 UTC on 2026-07-27.

The performance history identifies candidate occurrences CalibrationCurrentnessCheck-043 during 08:40–08:45 and FixtureEntryReadinessCheck-043 during 08:46–08:50 on that date, following CalibrationCurrentnessCheckMethod-E1 and FixtureEntryReadinessEvaluationMethod-E2 respectively. For each complete candidate, this constructed case stipulates the independently established A.1:4.2 construction. The local LabCheckingWorkOccursWithinService@LAB043 declaration requires the complete checking occurrence to lie within admitted LabQualityServiceSystem-043’s declared calibration/readiness-checking boundary throughout its checking interval; the stipulated performance histories satisfy that condition. Together with each performer’s established A.13 basis, these premises admit both candidates under A.15.1. Their typed enactsMethod and containing-System relations then obtain on those same grounds. Their separate F.6 attributions use the same obtaining assignments and the case’s Work-assignment facts. Neither is the intended fixture test.

For this constructed case, the laboratory defines two local evaluation-result predicates. calibrationExpiryReported(W, X, T) holds when W’s actual performer compares calibration result X’s governing validity end with T, determines that it is no later than T, and completes that check by reporting expired. fixtureReadinessReturned(W, R) holds when W’s actual performer evaluates the named plan item and proposed start window under FixtureTestEntryCriterion-E2, using the identified input facts, and completes that check by reporting R as its readiness verdict. Each claim concerns one terminal report in one checking episode; a recheck is another episode.

The constructed history stipulates that the calibration result’s validity ended at 08:30 UTC on 2026-07-27. During CalibrationCurrentnessCheck-043, LabMetrologySystem-2 makes that comparison and reports expired at 08:45. During FixtureEntryReadinessCheck-043, LabOperationsCoordinatorSystem-1 evaluates PlanItem-TEST-043 in WorkPlan-LAB-043 for the proposed 09:00–09:30 start window. It uses the established calibration expiry and the recorded unresolved drawing-edition status, applies the criterion’s explicit failure rule, and reports notReady at 08:50.

The C.2.1 episteme FixtureTestEntryReadinessResult-E1, whose exact EntityOfConcern is WorkPlan-LAB-043, reports that readiness verdict and its grounds for PlanItem-TEST-043: the calibration result is expired and the fixture-drawing edition remains unresolved. Its stop is do not start planned-fixture-deformation-test-043; its return condition is obtain a current calibration result, select the drawing edition, and rerun the readiness check. The preparation and checking Work occurred; the target test did not. No A.21 gate decision or A.2.8.PER permission result follows from this readiness result.

What changes in practice. The team withholds the target test and prepares the current calibration and selected drawing. After those inputs are available, it reapplies the criterion and reuses other unchanged applicable grounds. Any assignment of that preparation has its own allocation basis; the readiness result itself supplies no duty or target Work.

A.15.5:5.2 - Documentation Repair Probe

Situation: an assisting agent can run a reversible documentation probe to find source-currentness gaps.

Use A.15.5 for the probe only if its work-entry decision needs a readiness criterion; an ordinary sufficient reversible probe needs no automatic formal plan or readiness result. When that branch is selected, apply the criterion to the probe’s WorkPlan and return the bounded value. If the account later claims the performed probe as a dated Work, recover its A.13 core and independent A.15.1 admission, adding F.6 only for precise attribution. A target-repair readiness question is then evaluated separately; the probe plan, readiness, actual occurrence and target-repair result establish different claims.

A.15.5:5.3 - Release screen with separate readiness, gate, and permission windows

At 10:00 UTC on 2026-07-27, the evaluator applies ReleaseEntryCriterion-E3 to ReleasePlan-E7 and PlanItem-Deploy-12. The result says ready for reliance only in [10:00, 10:30) and requires recheck when a consumed source, resource, assignment, permission or gate input changes. All times below use UTC on that date.

At 10:05, the current A.21 application of profile Release-Core-E4 consumes that readiness result through one identified GateCheckApplicationResult, cited by its GateCheckRef, among the complete effective check set. The gate returns a GateDecisionResult with decisionValue=pass for [10:05, 10:20); DecisionLogRef=ReleaseGateLog-12 cites the separate log recording that result. That gate result is not the readiness result and does not institute permission.

Separately, A.2.8.PER GrantedPermissionRelation@Context occurrence DeployGrant-12 covers the named beneficiary and deployment action for [09:00, 11:00). DeployNonProhibitionFinding-E2 reports nonProhibited from its named current frame, explicitly complete for this use, in evaluation window [10:00, 10:15); it is not the grant. A PermissionNormConflictFinding@Context, if an incompatible current norm is established over the same content and window, would be a third permission-side input and an unresolved disposition would stop the use. A policy that requires readiness, gate passage, a current grant, and the frame-relative non-prohibition result may rely on those distinct inputs at 10:10; it must re-evaluate the relevant branch when any window ends or a conflict appears. None of them proves that deployment Work occurred. A.15.1 identifies that Work only after its dated occurrence basis obtains.

If a dashboard shows green but the required readiness result or its reliance window, the current A.21 profile application and gate result, or the required permission value and qualification window cannot be recovered, resolve the missing basis under its subject pattern before relying on the affected claim. Recover the gate result directly or through ReleaseGateLog-12; loss of the log alone need not block reliance on a fully recoverable result. Open the A.10 evidence-provenance and currentness question when that basis for a consumed claim is unresolved.

A.15.5:6 - Bias-Annotation

  • Ready-label bias. A green tile, ready label, release screen, or commitment board position can look stronger than the recoverable claim. Recover whether the current object is readiness, appearance-based reliance repair under A.15.4, gate decision, work authorization, or performed work.
  • Full-kit umbrella bias. Full-kit preparation can hide planned baselines, performed preparation work, resource readiness, source currentness, and target work. Keep each current value in its subject pattern.
  • Baseline-as-actuals bias. Planned fillers and readiness references do not prove launch values, performed values, variance, or results.

A.15.5:7 - Conformance Checklist

IDA conforming readiness use…Check
CC-A15.5-1names the WorkPlan, PlanItem, intended performance, criterion, and evaluation time.The readiness result cannot float free of the plan content and bounded entry question it judges.
CC-A15.5-2separates readiness from performed work.No target U.Work occurrence is asserted unless dated work evidence is current.
CC-A15.5-3separates full-kit inputs, checking results and preparation/checking Work.A readiness claim need not identify a separate checking Work. Every dated Work it does assert needs A.13 and independent A.15.1 admission; F.6 applies only to a consumed precise assignment-bound claim.
CC-A15.5-4cites planned baselines without rewriting them.A.15.3 planned-filling rows remain declaration-local content inside the WorkPlan.
CC-A15.5-5keeps gate decisions in A.21.When the use requires a gate result, establish it through the applicable A.21 profile application over its complete effective check set and mapping rules; readiness may supply one declared check input.
CC-A15.5-6keeps resource readiness and resource aggregation distinct.Planned reservations and actual consumption are not merged.
CC-A15.5-7states stop, degraded-use, or recheck condition.The reader can identify the next supported action; committing or launching still requires its separately satisfied conditions.
CC-A15.5-8keeps prospective and retrospective permission inputs temporally typed and non-productive.A current grant uses its validityWindow; non-prohibition uses its evaluationWindow; conflict uses its overlapWindow and any subject-pattern resolution effectiveWindow. Exercise and non-violation appear only for different dated Work or an explicit post-launch recheck, with their own intervals. None proves another permission value, readiness, gate passage, capability, or target-work performance.
CC-A15.5-9keeps the readiness result, domain-local inputs, provenance, assurance, and any inception claim under their subject patterns.C.2.1 identifies the readiness-result episteme; each measurement, evaluation, resource, permission, gate, or other input keeps its own result algebra; use A.10 for provenance and state any assurance result separately under B.3, and A.15.PROD is opened only for a separately current local entity-identity inception claim.

A.15.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsBetter use
Ready label as authorizationA label is treated as permission, conflict resolution, work authorization, or gate passage.Use A.2.8.PER for the permission/conflict result, A.21 for gate decision, or A.15.4 when a reliance appearance is being used as a reason for work or reliance before the subject pattern slot, relation, or project-side reference is named.
Full kit as work donePrepared inputs are treated as target work completion.Keep prepared-input facts separate from target completion. Establish any claimed preparation or target Work under A.15.1, and any completion claim under its applicable criterion and case facts.
Baseline as actualsPlanned slot fillers are treated as launch or performed values.Keep planned fillers in A.15.3. When the receiving question needs a comparison, establish the actual values independently and state the result under the applicable comparison rule.
MOVE imported as kindTameFlow source wording becomes an FPF object.Recover intended work, commitment, readiness, gate, preparation work, or performed work under FPF patterns.

A.15.5:9 - Consequences

Benefits:

  • Teams can inspect work-entry readiness without flattening plan, preparation, gate, resource, and performed-work claims.
  • The adapted pre-entry Full-Kitting distinctions supply a recognition palette for a local readiness criterion; neither TameFlow nor its source vocabulary governs FPF readiness.
  • The result exposes the input claims and qualification intervals on which a later gate or work-entry decision may rely.

Costs:

  • Some “ready” claims become incomplete until the target work, missing inputs, and stop condition are named.
  • A full-kit check may expose missing preparation Work or inputs that need their own plan, subject-pattern currentness, evidence-provenance, publication, resource, or assignment claims.

A.15.5:10 - Rationale

The readiness question is practical and recurrent: does this intended performance satisfy its work-entry criterion at the stated time? FPF already has the kinds needed to answer it. One local criterion and result claim keep the answer inspectable without collapsing the plan, its inputs, the checking Work, gate, permission, or target Work into one object.

The result depends on the inputs consumed by its criterion. It may use an immediate A.15.4 disposition without making that note a new formal object. Later reliance needs the claim and its grounds recoverable under the relevant access and currentness conditions; a durable representation is one way to provide that access. A missing input may need preparation, clarification or a direct subject-pattern check, rather than automatically becoming a source-repair problem.

A.15.5:11 - SoTA-Echoing

Source familyBounded source contributionLocal adoption
Steve Tendon, The Book of TameFlow: Theory of Constraints Applied to Knowledge-Work ManagementAdapt only the pre-entry Full-Kitting distinctions used to recognize minimum outcome or value, target scope, commitment, WIP pressure, and preparation inputs. Reject source MOVE or Full-Kitting as an FPF kind or universal readiness ontology; the source remains scoped to knowledge-work management.Use the adapted distinctions only as inputs to an FPF-local readiness criterion and result; keep WorkPlan, PlanItem, gate, preparation Work, resource, assignment, permission, and performed-Work claims under their subject patterns.

A.15.5:12 - Relations

  • Builds on: A.15, A.15.1, A.15.2, A.15.3, A.15.4, A.21, B.1.6, E.18, E.18.1, and E.24; consumes current A.2.8.PER grant/non-prohibition/conflict refs as prospective inputs, and exercise/non-violation refs only as evidence about different dated work or in an explicit post-launch recheck after target work is actual.
  • Coordinates with: E.11.PUR for recommended pattern use before readiness is selected, E.10.MOVE for readiness wording repair, C.32.P2S when readiness prepares work that realizes architecture-selected structures, and A.3.4.P when workflow or process wording is primarily transformation-situation wording.
  • Does not replace: target U.WorkPlan, its declaration-local planned-filling content, U.Work, GateDecisionResult, the A.15.4 reliance question and note, resource aggregation, or transformation-flow structure.

A.15.5:End

A.15.6 - Recover What Project, Process, or Case Wording Refers To

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Reader. This pattern is for the FPF practitioner who must identify what project-, process-, or case-management wording refers to before relying on the claim, then open the pattern that defines or constrains that subject.

A.15.6:1 - Problem frame

Use this when. Use this pattern when project, process, case, program, initiative, or situation wording is about Work and change, but the claim does not yet reveal whether it concerns one performed Work whole, a reusable way, a selected structure, or another named subject or claim being followed to a closure decision.

Use it also when a team cannot keep its problem-development, solution-development, and development-platform questions connected. This branch recovers the selected subjects without collapsing them into one project object. When a systemic account is needed, A.1.STM supplies its project system-of-interest and intended-use basis; the local subjects may still be Methods, epistemes, Work, capabilities or other results.

Use it also when project system-of-interest wording leaves unclear whether the claim concerns the system whose use organizes the undertaking or the current local subject, whether an actual U.System or only a future holder is intended, or whether designation is being inferred from a role label.

A claim of locality to one actual project requires a direct relation to its performed project Work, as section 4.5 states; an @Project name supplies only a label.

First useful move. If the project focus is unresolved, state the sought outside difference, relying use, comparison-and-acceptance conditions and receiving decision. Include any conflicting interests, evidence horizon or uncertainty that can change the choice or qualify its use. Compare candidate project subjects and materially different solution forms before designating a project system-of-interest or Method-of-interest.

Otherwise ask what the next decision is about: the Work that happened, the reusable way of doing, the organization of Method-side objects and relations, a TransformationFlowStructure, the referent being changed, or the System whose change or later use organizes the project.

In the process branch, identify whether the question concerns U.Method, a U.Structure selected under A.22, or TransformationFlowStructure. Then choose any representation needed for that question.

In the system branch, distinguish the project’s system-of-interest from the current subject of inquiry or local work, and an actual holder from a future description. Keep designation, the participants’ working agreement, technical classification and assignment as separate claims.

Three short recognition cases. Use these before the full pump example.

  • Project: a plan designates PumpUnit-3 for an upgrade. While work is only intended, use A.15.2 for the U.WorkPlan and stop there. After performance, use A.15.1 to identify the composite project U.Work; add a work-to-pump or work-to-change relation only under its own predicate. Stop when the current plan or Work question is answered—the plan, Work, and pump are not one project object.
  • Process: several inspections use BearingInspectionMethod-4. Use A.3.1 for that reusable U.Method and stop when the way-of-doing question is answered. Open A.22 only when the organization of identified method-side objects and obtaining relations changes the next action, and E.18 only when transformation flow is the question. One inspection Work enacts the Method.
  • Case: a failed pressure test opens a closure question about PumpUnit-3 or about one readiness or acceptance claim. Use A.15.5 when the question is whether an intended performance in a U.WorkPlan or PlanItem can enter under its work-entry conditions. For equipment condition, product readiness or acceptance, use the predicate that defines that claim. Stop when the closure answer and its basis are known. Name later release or pumping use, when relevant, as outside the case closure.

What goes wrong if missed. A plan is counted as performed work, a temporary organization is identified with its project, one work occurrence is mistaken for a repeatable process, or a case record replaces the named subject or claim whose bounded closure is being managed. Parallel @Project, @Process, and @Case names then create apparent kinds without identity rules.

What this buys. Project Work receives one occurrence identity under A.15.1. Process improvement can select one reusable U.Method, one A.22 U.Structure, or one TransformationFlowStructure without collapsing them. Case Work stays oriented to the subject its claims concern.

Plans, organizations, Transformations, descriptions, publications, results, and evidence can then be related through the claims the decision needs. A responsibility assertion needs its own predicate and participants. Use an applicable existing rule or a sufficient local claim under A.6.RCD; return missing-governor only when a governing predicate, applicability condition, necessary occurrence rule or other required rule is absent.

Not this pattern when. Use A.15.1 when the subject is already known to be performed work, A.3.1 when it is already a reusable method, A.3.4 when it is already a bounded transformation, or E.18 when it is already a selected transformation-flow structure. This pattern recovers the subject from management wording; it does not replace those ontics or domain management methods.

Recover the subject from management wording. Project, process, case, program, initiative, and situation are useful Plain cues. Section 4 explains the positive recovery: an actual project may be composite U.Work; a process concern may select U.Method, an A.22-selected U.Structure, or TransformationFlowStructure; a case concern follows the named subject or claim to its closure. Plans, organizations, changes, descriptions, results, and evidence keep their own identities and relations.

A method-side structure may be called MethodRelationStructure locally after A.22 selects it for one question and use. Its identity comes from that selection, including its constituents, obtaining relations, constraints and use frame. For another needed claim, recover the participants and the rule that defines or tests it. A local claim can suffice without a dedicated pattern or relation kind. If its governor is absent, name the missing rule and use A.6.RCD’s lightest sufficient branch.

A.15.6:2 - Problem

The same happening can be approached through three legitimate concerns. A project manager may need the identity, cost, completion, or result of one Work whole, but a result or measure remains its own subject when that is what the claim asserts. A process engineer may need one reusable U.Method, one A.22-selected U.Structure whose organization changes the next question or action, or a TransformationFlowStructure. A case worker may need to follow one named subject or claim to a bounded closure while keeping any relevant downstream use outside that closure.

Treating these concerns as three views of one unspecified “project situation” loses the subjects. Treating them as three sibling kinds duplicates ontics already supplied by U.Work, U.Method, U.Transformation, selected structures, epistemes, characteristic bearers and assignments, relation occurrences, and continuing referents. The problem is to recover the subject or claim and its direct relations while keeping familiar Plain wording available for retrieval.

A.15.6:3 - Forces

ForceTension
Familiar management vocabulary vs kind precisionProject, process, and case are useful recognition words, but they do not by themselves provide FPF identity rules.
Unique occurrence vs repeatable wayOne Work whole has a dated 4D identity under the full A.15.1:4.1 admission test. Precise assignment-bound attribution adds F.6 only when that claim is needed. A reusable Method may be enacted by many Work occurrences; each asserted enactment needs the obtaining A.15.1 relation between that Work and Method. Relations among method-side values remain direct until all four A.22 discriminators select a U.Structure; a TransformationFlowStructure separately organizes transformation flows.
Case subject or claim vs neighboring historyA case follows the named subject or claim in its closure question; Work, changes, editions, measurements, decisions, evidence, records, and downstream use remain separately defined.
Intention vs actualityA charter, plan, authorization, or funded intention can establish intended work. Performed work needs its independently grounded occurrence basis.
Actual system vs intended future systemA plan can describe the system the work is meant to produce or use, but an intended future System cannot be treated as an existing U.System or assignment holder before its applicable identity-inception boundary.
Project designation vs system-role classification and assignmentA project may designate one System without classifying it under a local system-role kind or asserting a system-role assignment. Conversely, an A.2 classification under a local system-role kind, or even an assignment occurrence and its declared U.SystemRoleAssignment species, does not prove that the project designated the holder.
Expected target vs actual resultAn objective or target guides work; an actual change, produced entity, evaluation, delivery, acceptance, or later use needs the pattern and facts that define its relation to the Work.
Temporary work vs temporary organizationA team or organization may change while the same work whole continues, or persist across several work wholes.
Description coherence vs subject identityShared source events tempt authors to call project, process, and case accounts views of one entity even when their descriptions concern different entities.
Continuity vs. organizational changeRecover the actual history first; use a Work-continuity policy when interruption, replacement, split or merge leaves an identity question for the receiving use.

A.15.6:4 - Solution

Recover the subject selected by the working concern. Use the pattern whose Solution answers that subject question, then relate plans, Systems, Transformations, results, descriptions, and publications through their own obtaining relations.

A.15.6:4.0 - Recover the subject before adding management detail

  1. Read the working question, not the management label. Ask whether it is about one performed Work whole, a reusable way, an organization of already identified things and relations, a transformation flow, or a named subject or claim being followed to closure.
  2. Name that subject in ordinary language. Use A.15.1 for Work, A.3.1 for a Method, A.22 for a selected U.Structure, E.18 for a transformation-flow structure, or the applicable rule for another subject or claim.
  3. Add only the plan, system, assignment, change, result, description, evidence, or publication relations needed by the question, using their governing predicates and obtaining facts.
  4. Stop when the subject and the claim needed now are clear. Continue to section 4.1 for actual-project qualification, 4.2 for a process concern, or 4.3 for case closure only when that further question remains current. If a needed rule is absent, return the participants and that missing-governor; a sufficient local rule needs no dedicated pattern.

A.15.6:4.0a - Select or reopen one bounded project focus

Use this branch only while the next decision depends on selecting or reopening the problem, project subject, solution form, Method relation, or development-platform contribution. If one already identified Work, Method, System, transformation, structure, episteme, capability, population, relation, or other subject answers the current question, use its pattern and stop rather than completing a project template.

Project-focus decision is Plain wording for one C.11 ChoiceResult over a current OptionSet. If options are still being invented, expanded, or reframed, complete that work under the Method that governs the project question. If the rows are only labels or fragments and the question is several complete ways to obtain the same result, stop here and apply C.38. Use C.18 when candidate retention or a comparison front is the unresolved question. Return when a current OptionSet exists.

When the result needs a reference, identify its C.2.1 episteme through all three discriminators. Preserve a durable representation when later access requires it:

C.2.1 discriminatorProject-focus value
claim contentthe complete interpreted claims that state the current C.11 inventory and result together with the five project-focus content groups below (C.2.1:4.1.1)
EntityOfConcernthe DecisionSubject whose current choice result is being recorded, at the declared DecisionSubjectGranularity
effective reference schemeone named project-decision scheme and edition whose designation, interpretation, comparison, and evaluation rules give the C.11 terms, alternatives, focus content, and result their meaning

This aboutness choice lets one chooser revise the selected problem. Authority, commitment, budget ownership, Agent status, and performed Work remain neighboring claims under their own governors; none changes the EntityOfConcern merely by appearing in the decision record. One chooser’s C.11 result also does not establish a shared understanding or agreement among project participants. When that common basis is at issue, use A.1.STM:4.1 to compare their project-system and use accounts and resolve the consequential differences.

The minimally useful result carries the full C.11 choice discipline through five connected content groups:

  1. the observed situation, sought outside difference, and available bounded problem options in the current OptionSet;
  2. affected entities and interests, materially relevant alternatives, and one comparison basis: a PreferenceOrder or EvaluativeMeasure, plus the current BeliefState and OutcomeModel and any decision-relevant dependence layer;
  3. the selected option’s direct-subject disposition: one System, Method, capability, Work, episteme, population, relation, arrangement, or other admitted subject when that choice changes the decision, or an unresolved-subject disposition;
  4. the identified DecisionSubject and DecisionSubjectGranularity, one ChoiceRule, and, when an inquiry alternative is live under C.11, its probe-worthiness account using ProbeActionSet, ProbeBudget, CostToProbe, and the applicable ValueOfInformation or ValueOfComputation; and
  5. one ChoiceResult—choose now, reject current set, probe again, or reroute—with the receiving decision or use and any limitation needed to interpret it. Name the next question when further work remains, and retain an evidence horizon, material uncertainty or reopen condition when the decision or its recipient needs it.

Keep any inquiry limitation or reason needed by the decision or its recipient in the same result; inactive inquiry adds no placeholder or omission account.

Apply the C.11 ChoiceRule to the available basis. choose now may retain a lawful tie-set, or select a bounded problem whose option leaves its later direct subject unresolved and names the next question. reject current set applies when the rule excludes every current option. probe again requires a named feasible probe within the remaining budget whose expected decision-changing contribution justifies its cost; reroute applies when the question changes.

Close as choose now only when no feasible next probe is expected to change the survivor relation enough to justify its cost; close as reject current set only when no such probe is expected to rescue an option. In both cases retain C.11’s stable-current-set and local-choice conditions.

If the facts needed for a lawful result remain unavailable and no such probe or reroute is warranted, leave that premise and the unfinished comparison unresolved; this is not a fifth ChoiceResult. If the current set needs reframing, return to option formation at the start of this branch.

Stop when the lawful ChoiceResult and the reason it is lawful are recoverable. Changing the selected problem, OptionSet, comparison or acceptance basis, direct-subject disposition, ChoiceRule, ChoiceResult, or receiving decision changes the identity-bearing claim content and therefore identifies another episteme even when the chooser remains the same. Another supporting item, evaluation, or publication does not reidentify the focus episteme unless claim content, EntityOfConcern, or effective scheme also changes.

Call a later focus episteme another edition only when a C.2.1 EpistemeEditionRelation obtains under the named project-focus continuation rule: the later episteme uses the earlier one as its revision source; preserves the DecisionSubject as EntityOfConcern, the receiving-use lineage, and the scheme features that keep the decision interpretable; records every deliberately changed focus-defining claim or permitted scheme feature; and is not a fork, translation, retargeting, or independent reconstruction.

Shared chooser, performers, organization, budget source, label, or calendar alone establishes neither episteme identity nor edition continuity. Focus succession decides no performed-Work identity question.

Proceed by logical dependency, not by a compulsory Work sequence:

  1. problematize the situation and comparison basis. B.5.PI can expose a consequential question through an ordinary work occasion or a suitable mantra before a difficulty is felt;
  2. recover the result or use that makes the decision matter. For a systemic project question, A.1.STM first follows intended receiving changes at the operating time, including a possible future use, and moves from the system boundary to the larger whole and the joint functioning of its parts. A non-system or non-project question retains its own subject and grounds;
  3. compare candidate subjects for the current decision. Distinguish the common product SoI from a local system-in-hand, including an organization being engineered. Distinct usable product supplies can have their own SoIs under A.1.STM:4.1; a separate organizational project retains the product-use basis. Then investigate construction and creation using that basis. Keep functioning, behaviour, interaction, causal participation, intended Work, actual Work, and Method enactment under their own governors;
  4. compare materially different solution forms, which may be Systems, Methods, epistemes, arrangements, or combinations;
  5. designate a project Method-of-interest only when that Method’s identity, architecture, comparison, enactment, development, or maintenance is the question; and
  6. recover the Methods and arrangements used to develop it and the other Methods whose change affects the selected problem or solution.

Inspect the account through the lightest optional view that changes the decision:

ViewWorking questionFirst useful resultBoundary
Problem factoryWhich problem merits attention and resources, for whom, and under what comparison and acceptance conditions?A lawful C.11 ChoiceResult over bounded problem options.A lawful problem choice may leave its later direct subject unresolved.
Solution factoryWhich materially different System, Method, episteme, arrangement, or combined candidates should remain, be selected, or be rejected?A ChoiceResult with the current alternatives and the grounds supporting the result; include evidence needs and a reopen condition when the choice or its receiving use requires them.The result records the choice. Candidate realization, an actual selecting Work occurrence, and any Method claim each need their own grounds.
Factory of factoriesWhich provider Systems, Methods, capabilities, tools, assignments, organization arrangements, and cultural practices enable or distort the first two views?One bounded platform or organization-change ChoiceResult and its receiving contribution claim.A platform improvement is not project success without receiving contribution and outside consequence.

The development lemniscate is a didactic view of recurrent dependency and feedback among these questions. For a mantra or diagram, state whether the order shown is teaching order, logical dependency, Method unfolding, planned Work order, observed Work order, or feedback. Establish each ordering from its own grounds.

Return ordinary prose and add a small map only when it changes the decision. The account may be distributed across existing artifacts and may remain partly unresolved. A missing chooser, granularity, current option set, comparison basis, lawful choice result, direct-subject disposition, or receiving decision is a named stop or reroute—not an invitation to fill a project template. A missing performer basis or authority claim leaves only a selected claim that depends on it unresolved. An actual project occurrence enters section 4.1 and receives its identity only as admitted composite U.Work.

A.15.6:4.1 - Recover an actual project as composite U.Work

In Plain use, actual project denotes one temporary composite U.Work occurrence: the performed work whole, with a start and a completion or termination condition. The performing organization or cooperating performer Systems remain distinct from the Work. Any claimed collective System needs its own A.1 recognition basis.

The intended work and result are described in a U.WorkPlan or other intention episteme; the system being created or changed has its own identity. A continuing organization can perform successive or overlapping projects and ongoing operational work. A project-focus decision, authorization, schedule, budget, dashboard or repository is a neighboring object or claim; none supplies another identity for the performed whole.

Admit the candidate composite under the full A.15.1:4.1 test, including the A.1:4.2 common construction of that same occurrence. While it is a candidate U.Entity, ground its construction and performance facts independently. Recover every actual performer’s A.13 core: the admitted System, local agential system-role kind and classification, obtaining assignment for the scope, working situation and window, evidence adequate for the local criterion and classification, and any characteristic profile consumed by a Grade, autonomy, criterion-dependent or assurance claim.

A.15.1:4.1 also governs the Method actually followed, temporal extent and complete-occurrence containment under a declared local rule; the containment facts precede the typed Work-containment assertion. Reuse an already established full admission result when it covers this occurrence.

Admit each included Work occurrence independently. After the composite is admitted as W : U.Work, assert its grounded typed enactment, containment and Work-part relations. An admitted part or a temporal inclusion alone does not admit the whole or establish Work parthood. If a common or Work-specific premise is unknown, leave the dependent admission unresolved; if a necessary condition fails, reject that proposed basis while retaining independently supported facts.

When precise assignment-bound attribution is current, use F.6 afterward to relate the admitted Work to each performer’s same obtaining A.13 assignment, preserving direct case support, holder equality, species, participants and coverage. A short attribution account may omit an unused identifier only when every required link remains recoverable. F.6 is not an admission premise. Apply these five project-specific qualification tests to the independently admitted Work:

  1. The composite work has a temporary or transient boundary with a start and a completion or termination condition.
  2. An accepted intention episteme states the intended objective and any intended product, service, result, or value. For this qualification, either an existing direct predicate connects its intended-performance designation to the admitted Work and obtains, or one local claim under A.15.2 or A.6.RCD names the plan or decision, designation, Work, applicable policy, and independently obtaining Work facts. An absent predicate, applicability condition or required occurrence rule returns missing-governor; unavailable constructor semantics for a proposed local derivation return missing-substrate under A.6.RCD. When the governor exists, preserve its inapplicable result or use test 5’s reason-specific result for the applicable test and available facts. Do not imply a generic plan-or-decision relation.
  3. Apply A.15.1’s Work-part and identity rules. When interruption, resumption, split or merge leaves an identity question that the receiving use must resolve, use the applicable continuity policy to interpret the actual history.
  4. At least one independently admitted performed Work occurrence is connected to the composite Work by an obtaining work-part relation.
  5. For each claim used to qualify the project, name what the claim is about—the participating system, affected referent, transformation, result referent, or another subject actually asserted—and say how that subject matters to the Work. Choose a claim form whose rules fit that use: an obtaining direct relation; a typed A.6.1 binding for a reusable-operation application; a local production, inception or completion claim under A.15.PROD; or another local claim under A.6.RCD. If the claim cannot be asserted, preserve independently established facts and return the reason-specific outcome from A.6.P.WMR. Distinguish a failed applicable test for the attempted polarity, missing deciding facts, an absent governing rule, known inapplicability and missing constructor semantics. If the facts contradict a necessary condition of the specified qualification, they rule it out within that scope. A search that merely failed to find the needed evidence can leave both answers possible. A missing rule calls for the lightest sufficient contribution under A.6.RCD, not automatically a new relation kind or pattern.

No performed work means no actual project occurrence yet. A proposal, charter, authorization, schedule, budget decision, or funded intention can establish a U.WorkPlan and related commitments. It does not backdate performed work, a future system, an assignment, an actual change, or a result.

The project occurrence uses the identity, temporal extent, parts, episodes, continuity, and relation-specific aggregation defined in A.15.1. Project wording adds no second identity rule. When a reader asks for the project result, ask first: What is the result, and result of or for what? Keep that referent in the kind or claim already established for it, then apply test 5 to the proposed relation or claim.

State what failed. Confirmed absence of any performed work by the date in question rules out an actual project occurrence by that date. An incomplete search for such work leaves the answer open. To exclude every admissible way of obtaining the result, establish that a condition necessary for all of them failed, or cover all admissible ways and show why each was ruled out. Different ways may fail for different reasons. Preserve independently established facts about the subject and the target specified in the plan.

Whole-project roll-up requires obtaining work-parthood plus an aggregation policy defined for the one relation and measure being aggregated. Outputs, effects, verdicts, epistemes, deliveries, and uses do not become one result merely because they share the project label.

A.15.6:4.1a - Connect project work, the system-of-interest and the local subject

Start with the local work and its purpose in an ordinary sentence: this temporary work is intended to establish this result for this product use or other stated receiving purpose. Name the composite project U.Work when it has been performed; while it is only intended, name the U.WorkPlan. Recover the actual subject or intended-subject designator, the plan or decision that selected it, the change or use being pursued, and the next decision needing that account. For organizational work, distinguish the creator being engineered, its promised capability, the local result and the product use that gives them their reason.

The system-of-interest (SoI) is the product System that a particular extended enterprise is organized to create, change, sustain in use or retire. The extended enterprise is the organization System. Keep it distinct from performed work and work plans; section 4.1 supplies the conditions for admitting actual composite project Work. Agents acting for the participating organizations establish or accept the objectives and commitments. Several projects can serve the same SoI. The current subject of inquiry or local work answers what must be understood, obtained or changed now; for a system, use system-in-hand or our system with the relevant participant’s relation stated.

A product undertaking can supply a usable test rig to laboratories and have that instrument as its SoI. A project developing the pump-test laboratory engineers a creator whose capability is justified by the pumps’ qualification needs. A contract, performer or budget change for that same work does not change this distinction. Several products and other results can matter to one project; retain each use and the shared constraints relevant to the decision.

A.1.STM:4.0–4.3 develops this use basis. It follows receiving changes at the selected operating time and moves from the system boundary to the larger whole of which the system is, or is intended to be, a part. The joint functioning of that whole’s parts grounds the system’s required contribution before the reasoning turns inward to construction and backward to Methods and creator contributions. If that whole is unknown, the missing account must be investigated before relying on a dependent function or construction judgement.

A.1.STM:4.1.1 connects organizational design, provision and finite acceptance through the required product use and creator capability. The organization remains engineerable even when it is sold as a business. A new product supply requires its own use and bounded fitness obligations; an economic product label alone supplies neither. A local result can close while wider use remains open.

Research has its own epistemic acceptance, including a supported negative result; when it serves a capability decision, its fitness for that decision is an additional question. Keep a missing or contested system-and-use basis open only where the current systemic question needs it.

When the designated system already exists, identify that same entity under its admitted U.System kind. The plan or decision may say why it matters to the project. Links come from relations that obtain: a work-to-referent or work-to-change relation, one independently identified Transformation, a branch-local A.15.PROD production or inception claim, an evaluation, a participation or use relation, or another separately defined direct relation. Include only links used by the named decision.

When the System is only intended, agree the SoI role, required holder characteristics and intended use while keeping the holder’s designator inside the U.WorkPlan, decision, System description, or other claim episteme. Before its identity rule first holds, there is no future U.System, system-role-assignment holder, or Transformation of that not-yet-existing System. A.15.PROD may later state the identity-inception boundary.

After inception, relate the actual System to the earlier description through the applicable reference or identity claim, then test project designation, participation, local system-role classification, and any assignment at their own times.

For a series or family, keep the common requirements and the later individual holders distinct; a specification or collection does not become one System. A.1.STM:4.2 develops this case.

Project designation, local system-role classification, and system-role assignment are separate claims. The ordinary explanation is sufficient while participants only need to understand the system’s place in the cooperation. When classification matters, identify the local system-role kind and its feature criterion under A.2, then test the actual System against it. A local SystemOfInterestSystemRole using this Library meaning must express the named extended enterprise, its agreements for the product’s creation, change, sustaining in use or retirement, the intended use or withdrawal from use and designation grounds under A.1.STM:4.1. A criterion selecting whatever an observer investigates or engineers answers a different question. Calling an organization that kind does not replace the product SoI in organizational work.

When assignment identity or its window matters, select a declared U.SystemRoleAssignment species under A.2.1. Recover its holder position, declaration-local assigned-kind domain, predicate, applicability, additional participants and occurrence rule. Use a system-role kind value only if it belongs to that species’ declared domain, and assert an occurrence only when its obtaining facts satisfy the declaration. Classification is a prerequisite only if those rules consume it. An assignment can therefore be established without a separate holder-classification claim.

A missing declaration, required rule or deciding fact leaves the typed assignment unresolved. An inapplicable declaration or a failed obtaining test does not support that assignment claim. Retain an independently supported ordinary designation.

A patient record, damage claim, measurement result, or other non-System case subject can remain central to project Work but cannot be classified under a system-role kind or hold such an assignment.

When one project question spans operation or use of the project system-of-interest together with production, identity inception, later change, verification, feedback, or recursive builder questions, E.18.NET may select the relevant independently identified TFS or nested-network members. The selection must pass its four A.22 discriminators: direct members, obtaining cross-member relation occurrences, applied constraints, and one networkUseFrame; all endpoint bindings must resolve.

If a member or relation is ungrounded, keep a Plain proposed network explanation and name the missing member, governor, false or unresolved predicate, occurrence, or binding. The selected network is a non-agentive U.Structure. Work membership in a project requires obtaining A.15.1 work-parthood.

When the network-selection judgment needs a separate reference, identify the C.2.1 result episteme whose EntityOfConcern is the selected network and whose claim explains its use under the stated basis and qualification window. A durable representation may preserve access. Project Work, changes, case closure, production, evidence and decisions retain their own claims.

Use the lightest claim that answers the project-selection question. A plan or decision designation and every independently obtaining Work, change, production, evaluation, delivery, acceptance, or use fact remain usable. Often the ordinary sentence “this plan designates PumpUnit-3 as the system this upgrade is about” answers a local designation question; do not construct a conjunction around it. It does not by itself establish the participants’ common SoI, agreement or expected contribution. Keep the larger systemic question at its own scope through A.1.STM.

For one bounded decision that needs the combined truth, a C.2.1 local compound claim may cite the named plan or decision, composite Work, actual System, direct facts, applicability, and case facts. Its constructor semantics must be recoverable, but A.6.RCD does not require a separately materialized substrate document for a simple one-case claim. Name and pin the substrate when the derivation is nontrivial, intended for interoperability, used as proof, or reused.

Repeated parameterized use may justify a reusable predicate-definition episteme. Admit a relation kind only when a named receiver also needs distinguishable project-selection occurrences with their own identity.

Return missing-substrate[project-selection-conjunction] only when the stronger compound claim is needed and no substrate supplies the proposed operator semantics. The blocker stops that compound claim; it does not invalidate the plan designation or any direct fact.

For PumpUnit-3, the plan and upgrade decision designate the pump, while the admitted composite Work, Work parts, and pump-change facts remain supported independently by their defining patterns and facts. That answers the local designation and Work questions; the common SoI and use basis is supplied separately through A.1.STM. Open a compound local claim only for a decision that consumes the conjunction, and materialize or pin its substrate only under the conditions above.

A.15.6:4.2 - Recover a process concern through U.Method, a selected U.Structure, or TransformationFlowStructure

When the question is about repeatability, ordering, throughput, variation, control, or improvement, select the subject that the claim concerns:

  • U.Method for the reusable way of doing;
  • a U.Structure selected under A.22 when the organization of already identified method-side objects and relations changes the next question or admissible action;
  • TransformationFlowStructure when the question concerns the organization of transformation flows.

Keep a measure, evaluation result, relation occurrence, event collection, or dated Work as its own subject when that is what the claim asserts.

For a method-side U.Structure, identify the constituents, the selected obtaining relations, the applied constraints, and the use frame: selection question, admissible action and stop or return condition. These are A.22’s four identity discriminators. Only then may MethodRelationStructure serve as a local designator. If any discriminator is absent, keep the direct relations unbundled. An explanatory warning may help a reader but is outside that identity unless it changes a constraint or the use frame.

A Work occurrence supports only facts grounded in its history and relations. For Method enactment, establish A.15.1 enactsMethod for that Work and Method. For an operation application, identify its A.6.1 declaration, application and argument/result bindings. A trace or record may supply evidence; a shared label, compatible result or record presence alone establishes neither predicate and does not retype Work as a Method or structure.

Do not force multi-object event data into one preselected case key or one flattened sequence. Preserve the relevant object and event relations, then select a process execution, grouping, query, or constraint only when the use needs it. The selection is a modeling decision.

Identify any selection-result episteme under C.2.1 from what its claim-bearing whole concerns: observed material, a selected structure, a rule or another independently identified subject. Its use as evidence requires an obtaining evidence-use relation. Method identity retains its own grounds. Stop when the reusable way, selected organization, or transformation-flow question has been answered.

A.15.6:4.3 - Recover a case concern through one named subject or claim

A case label is a cue to read the closure question. Recover:

  1. the named subject or claim and the rule that identifies or defines it;
  2. only the Work, changes, conditions, measurements, evidence, decisions, and references used by this closure question;
  3. the applicable rule and facts that define the closure basis;
  4. any later receiving use that matters to this closure or to the current receiving question, kept outside the closed case.

The subject need not be one continuing changed entity. It may be any independently identified thing or claim needed by the closure question—for example, a maintained System, patient, material batch, episteme edition thread, characteristic bearer or assignment, measurement or result episteme, relation occurrence, decision, Work occurrence, or selected edition-lineage structure. Each keeps its own identity rule. Changed claim content identifies another episteme; a measurement claim identifies its own bearer and value.

Do not infer the case subject from a log’s case key or from one record format. Object-centric evidence may connect several objects and several possible groupings. Select the grouping the closure question needs and state any information lost by flattening that limits that use or could mislead its reader. CMMN, DCR, Declare, and similar notations can help represent flexible case work. Evaluate their usefulness and ease of use for that representation task; establish the case subject, closure and any asserted Work from their own grounds.

When case claims need separate reference, identify their C.2.1 epistemes from the claim-bearing whole. Several independently identified participants may occur in one account with one truthful EntityOfConcern. Split the account when that concern would be untruthful or the combination would break the identity or comparison needed by the use.

A closure question may concern an independently identified grouping, query or result episteme. Select a structure under A.22 when a current or later use needs that organization and its four discriminators pass; otherwise keep the sufficient direct claims.

You may state the working boundary without asserting a new relation. If a later use requires a relation from the closed case to that use, recover its participants and apply an applicable predicate or sufficient local claim. Return missing-governor only for an absent rule needed to state or test that relation; distinguish missing deciding facts and a failed positive test under section 4.1.

Establish closure and change through the predicates and facts that define those claims. A Method or completed Work may contribute to their grounds, but neither alone supplies the closure or Transformation test.

A.15.6:4.4 - Do not force the three readings into one view family

Project, process, and case wording is only a cue to inspect the claim. Under C.2.1, each description is identified through its claim content, the EntityOfConcern recoverable from that content, and the effective reference scheme; a management topic does not assign that EntityOfConcern.

Description wordingRecover the EntityOfConcern from what the claim says
project cost, completion, or resultSelect the composite project U.Work only when cost, completion, or another predicate is asserted of that Work. If the claim is about a measure, transformation, produced entity, value, condition, verdict, decision, relation occurrence, or result episteme, select that named subject instead.
process repeatability, variation, throughput, or improvementSelect U.Method only when the claim concerns the reusable way; select an A.22 U.Structure or TransformationFlowStructure only when it concerns that admitted organization. Otherwise select the measure, evaluation result, obtaining relation, relation-bearing claim, or admitted collection-as-whole of occurrences asserted.
case condition, trajectory, closure, or next downstream useSelect the subject or claim named by the closure question: a continuing referent and its conditions, an episteme edition thread, characteristic bearer or assignment, measurement or result episteme, relation occurrence, Work, decision, or another identified subject. Name a downstream receiving use when the current question needs it, and keep it outside the closed case.

One description keeps one truthful EntityOfConcern for its claim-bearing whole, including any independently identified relational participants. Use separate epistemes when combining the claims would make that concern untruthful or defeat the needed identity or comparison. When accounts must be related, keep their C.2.1 identities and state the correspondence relations required by their use.

If an account is claimed as a U.View, E.17.0 additionally tests its conformance to a viewpoint episteme’s concern and rules. Ordinary related accounts need no viewpoint-conformance claim. Shared source events alone establish neither that conformance nor the required correspondence.

If the description needs empirical grounding, identify the admitted grounding holon and the EpistemeEmpiricalGroundingRelation defined by C.2.1. GroundingHolonSlot belongs to that relation’s RelationSignature; it is not a slot of the description episteme. Project Work, U.Method, a selected method-side U.Structure, TransformationFlowStructure, transformation, and affected referent do not acquire episteme or grounding-relation slots from the account.

For process and case descriptions, readability, simulation support, and ease of use are properties of the representation in a stated use. They can change which representation a team chooses, but they do not identify the described subject, establish claim truth, close a case, or prove that Work occurred.

A.15.6:4.5 - State project-local relations

An existing @Project name is a compatibility and retrieval cue. It does not establish identity, parthood, authority, viewpoint, or locality.

When a record or relation is local to one actual project, identify the composite U.Work and the obtaining relation that makes it local. Use the following typed references when the chosen representation needs reference fields:

Referenced objectReference head
the selected composite project-work occurrenceprojectWorkOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work
another work occurrenceworkOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work
a repeatable methodmethodRef : U.EntityRef, constrained to ValueKind U.Method
a selected method-side structuremethodRelationStructureRef : U.EntityRef, resolved to the U.Structure selected under A.22; the local designator MethodRelationStructure adds no kind or identity constraint
a transformation-flow structuretransformationFlowStructureRef : U.EntityRef, constrained to ValueKind U.Structure
the entity being changedaffectedReferentRef : U.EntityRef, narrowed to the ValueKind already admitted for that entity when the reference must carry that constraint

Use projectWorkOccurrenceRef only for the identified project-work occurrence.

A.15.6:4.6 - Apply work continuity rather than label or focus continuity

Project-focus succession and actual-project Work continuity are different questions. A changed focus-defining claim, EntityOfConcern, or effective scheme identifies another C.2.1 episteme. It becomes another focus edition only through an obtaining EpistemeEditionRelation under the project-focus continuation rule in 4.0a; a same chooser or label is insufficient. Neither another focus episteme nor an edition relation continues or reidentifies performed Work. Conversely, one composite Work may continue under its declared A.15.1 policy while its focus episteme changes.

For interrupted, resumed, split, merged or performer-changing project Work, recover the actual history and apply A.15.1’s identity and Work-part rules. Use a continuity policy when the named use needs a boundary judgment:

  • performer or team replacement changes participation and A.13/F.6 bases but need not change parent-Work identity;
  • interruption and resumption may be episodes of one parent Work or later occurrences; establish their identities and the applicable part or locally declared resumption relation, using a continuity policy only for the remaining ambiguity;
  • split and merge require independently identified Works and the obtaining Work-part or other direct relations claimed; predecessor or successor wording needs its own governed predicate;
  • failed or terminated Work remains actual project Work even when its intended result is absent or adverse; and
  • continuous operations qualify as a project only when one finite composite Work first passes independent A.15.1 admission and obtaining work-parthood, then passes the five project-specific qualifications; any precise assignment-bound performer attribution is a separate later F.6 result.

The organization performing or coordinating project Work is a neighboring U.System. Organization, project-focus, DecisionSubject, or label continuity does not decide project-Work continuity.

A.15.6:4.7 - Use the recovered subject and stop

Section 4.0 is the first pass. Sections 4.1–4.6 add only the branch detail needed by the current question. The worked cases below point back to those tests instead of restating them as new admission rules.

Stop when the subject, the required relation or claim, and its basis are clear. Continue to A.15.7 only when ongoing Work now needs a next-action choice. When observations or evidence about several performances support competing candidate ways, use A.3.1.MR. For a proposed way in documentary guidance, use A.3.1.DR when its source meaning or status needs recovery. Apply A.3.1 directly when a candidate way is ready for the Method identity test. A later decision, publication, evidence, or assurance question opens its own pattern rather than extending this recovery indefinitely.

A.15.6:5 - Archetypal Grounding

The following constructed cases illustrate the distinctions with stipulated admission and relation facts; they are not field observations. Whenever a case stipulates an admitted Work, that premise includes the full A.15.1:4.1 test for that occurrence, including its independently grounded A.1:4.2 common construction and complete-occurrence containment facts under a declared local rule. The Work-specific facts highlighted below explain the case; they are not a replacement admission test.

Integrated pump-modernization case: one project, several subjects. Before performance, PumpUpgradePlan-7 : U.WorkPlan describes intended upgrade Work, the existing PumpUnit-3, a proposed replacement controller, and expected later pumping use. At this point there is no actual project Work, no replacement-controller System, and no achieved vibration reduction.

The stipulated upgrade history runs from 08:00 UTC on 2026-07-20 to 16:00 UTC on 2026-07-23. The candidate composite occurrence has an independently established A.1:4.2 common construction. Its performers, MaintenanceTeam-4 and ControllerAssemblyCell-2, are independently admitted Systems. The local UpgradeCoordinatorRole and ControllerProductionPerformerRole criteria require respectively goal-directed upgrade coordination and condition-sensitive controller production; observations support those classifications. The declared UpgradeCoordinationAssignment and ControllerProductionAssignment species assign those kinds when the project designation and relevant control connection obtain. The stipulated designations and connections establish RA-Upgrade-Team4 and RA-Controller-Cell2 for the stated scope and window.

The performance history shows the composite following PumpUpgradeMethod-E7. Under the declared local containing-System predicate, the complete candidate history satisfies the boundary, window and other applicability conditions of admitted PlantMaintenanceService-3. These and the full admission premises stipulated above establish PumpUpgradeWork-7 : U.Work; the typed enactment and containing-System relations can then be asserted.

The diagnosis, bearing-replacement, controller-production-and-installation and qualification Works are independently admitted. Their assembly and performance facts, together with admission of the composite, support four obtaining Work-part relations. F.6 is checked separately when precise assignment-bound attribution through the same assignments is needed. A common timestamp or project label supplies no Work parthood.

The five project qualifications add only what this use needs. A local C.2.1 claim may record that the admitted composite Work fulfilled the intended-performance designation under the stated policy; the claim uses that local rule. MaintenanceTeam-4 and ControllerAssemblyCell-2 remain the performer Systems, with identities distinct from the project Work. A failed pump-qualification test may leave actual project Work while the intended result remains unachieved.

Apply section 4.1a to the project system-of-interest. The operator, controller supplier and maintenance organization have agreed the upgrade work and responsibilities, forming the extended enterprise for this alteration. Their plan and upgrade decision designate the already existing PumpUnit-3; direct Work-to-pump and Work-to-change facts separately say how the pump matters. Classification under a local SystemOfInterestSystemRole and any assignment occurrence require their own tests. A proposed controller remains plan content until its identity rule first holds; production completion, later operation, classification, and assignment are separate claims.

Apply section 4.3 separately to the pump, calibration, and controller-production cases. The pump case follows pump condition through repair and test while later pumping use stays outside closure. The calibration case follows TestRig-2 and the calibration facts used by qualification. The controller-production case closes only when the applicable Work, change, inception, completion or readiness, evidence, and decision facts support that result.

Any Work-realized change separately names the performer System with its A.13 basis, Work, changed referent, and the relation connecting Work to change, plus F.6 attribution only when the receiving question asks under which assignment the Work was performed.

Apply section 4.2 to the process question. BearingDiagnosisMethod-4 is the reusable way. An A.22-selected enactment-review structure may organize independently admitted Work and the obtaining relations that state which Method each occurrence enacts, but it neither composes the Methods nor proves pump change. If event data links the work order, pump, controller, test rig, measurements, and several Work occurrences, keep those object relations visible; select a grouping or query only for the question being answered.

Expected and actual results remain apart. A vibration target in the plan is intended. A pump Transformation, production result, evaluation episteme, delivery, acceptance, and later use each need their own pattern and facts. If result wording hides the relation, apply A.6.P.WMR and return its one applicable outcome. Whole-project roll-up requires an obtaining Work-part basis and one policy for the stated relation and measure.

After the project completes, PumpingRunWork-8 is separate Work unless an obtaining Work-part relation says otherwise. Likewise, controller-production and pump-test transformation-flow structures remain independent. Select an E.18.NET network only when the engineering question needs both and the required cross-boundary relation occurrences obtain. The selected network has its own A.22 structure identity.

Receiving decisions. A cost question requires the resource-use facts and accounting rule in addition to Work parthood; this case supplies no cost ledger, so the total remains open. To improve diagnosis across upgrades, the team compares outcomes of independently grounded BearingDiagnosisMethod-4 enactments under the same diagnosis criterion. To decide whether PumpUnit-3 may return to service, it applies the pump case’s acceptance and release conditions. If the final vibration test fails, that last use remains blocked while the performed upgrade and diagnosis observations remain available. Repair is planned from the failed condition; the failure does not erase earlier Work or establish a new Work-part relation.

Construction case: bricks become a wall. Vasya performs one bounded wall-building occurrence. For the project question, the stipulated full A.15.1:4.1 basis admits that occurrence as composite U.Work; its independently admitted parts and obtaining Work-part relations support the project qualifications in section 4.1. Keep the intended wall description, resources, completion condition, and any actual-change, identity-inception, or completion claim separate.

For the process question, select the repeatable bricklaying U.Method; use an A.22-selected U.Structure only when its four discriminators make method-side organization matter, or TransformationFlowStructure when transformation-flow organization matters. Vasya’s Work supports an enactment observation only when A.15.1 states that it enacts the Method. A declared operation application instead needs its A.6.1 declaration and typed binding.

For the case question, follow the subject named by closure: pre-existing bricks or other continuing materials for actual A.3.4 changes, a production or identity-inception claim while the wall comes to exist, or the continuing wall only after inception. Do not give a not-yet-existing wall a transformation history. These are related project, process, and case subjects, not three kinds of one object.

Medicine case: a patient episode. Consider a hospital improvement initiative whose composite occurrence passes the full A.15.1:4.1 test and whose independently admitted Work parts are connected by obtaining Work-part relations. It introduces and evaluates a new care arrangement; apply section 4.1’s five tests to qualify it as project Work.

The clinical-pathway concern selects U.Method, an A.22-selected U.Structure only when its four discriminators make care-method organization change the next action, or TransformationFlowStructure when the question concerns care-flow organization. Evaluation across Work occurrences uses only occurrences for which A.15.1 states the enacted Method, or for which a declared A.6.1 operation and typed application binding support the observed fact.

One patient’s changing condition is the case concern only when that is what the claim asserts; diagnostic claims, treatment Work, evidence, and decisions remain separate subjects and relations. The improvement plan, care team, patient record, and performed clinical Work likewise retain their own identities.

Learning case: a course redesign. The finite redesign effort is composite project Work when its occurrence passes the full A.15.1:4.1 admission test and section 4.1’s project qualifications, with independently admitted parts and obtaining Work-part relations.

The teaching U.Method, an A.22-selected U.Structure used only when its four discriminators make teaching-method organization change the next action, and TransformationFlowStructure for learning-flow organization are distinct possible process subjects tested across cohorts.

One learner’s changing mastery is a case concern only for claims about that learner or condition. Use C.2.1 and E.24.PUB to distinguish the epistemes and publications encountered through a syllabus, progress card, and course dashboard; none is the performed redesign, teaching Method, structure, or learner.

Research case: an experimental materials campaign. The finite campaign prepares alloy specimens, performs load tests, and analyzes measurements. Admit its composite occurrence under the full A.15.1:4.1 test, then assert the grounded relations to independently admitted preparation, testing and analysis Work parts and apply section 4.1’s five project qualifications.

Identify the reusable experimental U.Method separately from the protocol episteme; the latter is a MethodDescription only under A.3.2. The selected preparation-test-analysis organization is a transformation-flow structure only when that organization changes the research decision. Each specimen remains the affected referent followed through preparation and testing. Identify the claim-bearing epistemes under C.2.1, keeping the hypothesis, preregistration claims and measurement results distinguishable. Use E.24.PUB to identify their expression and publication uses, including the article. A surprising measurement becomes a Problem only when the C.22.PFR condition and applicability relations obtain.

Project progress, protocol improvement, specimen history, result interpretation and publication can therefore change independently.

A grounded result that rejects the proposed alloy hypothesis can meet the research acceptance criteria. If the campaign informs a product or creator-capability decision, assess that contribution separately; it establishes neither a usable product nor the capability itself.

Situation-wording contrast. The Plain word situation does not select one common kind.

  • An operating pump configuration comprises the admitted U.System, its parts, and state relations, plus Work or transformation only when the account asserts those facts.
  • A proof gap is carried by the proof episteme and the named unresolved-consequence and proof-acceptance applicability relations needed for the proof decision.
  • A multi-party emergency comprises the participating Systems, actual Transformations, response Work, and relevant temporal or causal relations; an emergency description is a separate episteme.
  • A future scenario is a U.MethodDescription only when the same episteme meets A.3.2’s criterion for describing one independently admitted Method. A possible-state description keeps its own claim content; describing a future state alone does not admit a MethodDescription.

Recover those subjects and relations.

Incident wording. Recover what the decision or action needs: the actual event or bounded change, responsive U.Work, participating Systems, obtaining relations, and any incident-description episteme or publication used. An incident record conveys claims about those subjects; establish their identities from the applicable rules and facts.

Planning-only boundary. A funded proposal with objective, schedule, assigned team, and charter can establish intended project work and a U.WorkPlan. An actual project requires a composite occurrence that passes the full A.15.1:4.1 admission test and section 4.1’s project qualifications, including independently admitted parts and obtaining Work-part relations. Until then, keep intended work and its estimates in the plan and leave dependent claims of actual project cost, result or completion unestablished. Retain independently supported facts about any performed part. F.6 may add precise assignment-bound attribution only after Work admission; the first task or its timestamp alone does not admit the composite.

A.15.6:6 - Bias-Annotation

This pattern has a project-recovery bias because project wording is widespread in FPF names. The process and case branches prevent that bias from making composite work the subject of every management claim.

It has a 4D work-occurrence bias for actual projects. The guard has an order: first A.13-qualified performer facts and A.15.1 Work admission with obtaining work-parthood; separately, F.6 attribution when a precise assignment-bound claim is current; apply the five project-specific qualifications to the independently admitted Work.

A temporary organization, plan, Transformation, product, dashboard, or time-contained occurrence remains a neighboring object unless the admission and qualification facts establish the composite Work and the claim is about it.

The examples include engineering, medicine, and learning to resist software-document bias. Working product is Plain recognition wording. Recover the entity under the pattern that defines or constrains it, then state the production-work, entity-identity-inception, changed-referent, measurement, evaluation, delivery, acceptance, or later-use claim that the decision needs. Keep the Plain wording only while the needed relation or claim remains recoverable.

A.15.6:7 - Conformance Checklist

  1. Start with section 4.0: read the claim and name the subject it concerns rather than interpreting the management label as a kind.
  2. For an actual project, apply A.15.1 to the composite U.Work, then the five project qualifications in section 4.1. Planning material remains content of its U.WorkPlan until Work occurs.
  3. Use obtaining Work-part relations and A.15.1 identity rules; apply a continuity policy only for the boundary question the receiving use needs. A time interval, team, charter, repository, policy or label establishes neither parthood nor continuity.
  4. For a process concern, choose among U.Method, an A.22-selected U.Structure, and TransformationFlowStructure as section 4.2 states. Ground each evidence use in the claim it supports: Method enactment needs the A.15.1 relation; an operation-application result needs its A.6.1 declaration, application and bindings; a timing, cost or condition claim needs its own relevant evidence. A report of admitted Work keeps its full admission basis recoverable under A.15.1:4.4 without repeating all of it in each narrow claim.
  5. Preserve multi-object evidence until the current use selects a grouping, query, or constraint. State omitted information when it limits that use or could mislead its reader. Identify the selection result from its claims under C.2.1; it can be a case subject when its independent identity and the closure question warrant that use. Method and Work claims retain their own admission grounds.
  6. For a case concern, name the subject or claim, the references used by closure and the closure basis. Name a downstream use when it matters to the current question and keep it outside that closure. Keep any case-record episteme under its own identity.
  7. Recover each description’s claim content, EntityOfConcern, and effective scheme under C.2.1. Treat notation readability or simulation support as a representation-use question, not as subject identity, claim truth, case closure, or performed Work.
  8. Recover the product, named extended enterprise and agreement basis for a SoI designation under section 4.1a, keeping the local system-in-hand and finite acceptance of organizational work distinct. System identity, designation, local system-role classification and any assignment occurrence remain separate in every direction. Do not backdate a future System.
  9. Use section 4.1a for a project-selection account. A direct designation may answer the ordinary case; a stronger compound claim needs recoverable constructor semantics, and missing-substrate blocks only that stronger claim.
  10. Keep performer, Work, change, result, success, acceptance, evidence, decision, description, publication, and later use as separate claims. Apply the pattern that defines or tests the current relation.
  11. For result wording, name the referent and say what it is a result of or for; then use the applicable A.6.P.WMR outcome. Whole-project aggregation also needs its Work-part basis and relation-and-measure policy.
  12. Use E.18.NET only for independently identified transformation-flow structures connected by obtaining cross-boundary relation occurrences. Work membership in a project requires obtaining A.15.1 work-parthood.
  13. For a Transformation, first identify the actual bounded change and continuing referent. Add an actor-side or Work-realization claim only when its own predicate and facts establish it.
  14. Reuse of one Method or transformation-flow structure elsewhere has its own enactment or selection facts and creates neither cross-project Work parthood nor cross-case identity.

A.15.6:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Charter-created project occurrenceAuthorization or funding is counted as performed project work.Keep the U.WorkPlan and any separately defined decision claim; admit actual project work only after the complete A.15.1 occurrence basis obtains.
Interval-made work partAn occurrence is called part of project Work because its timestamp lies inside the chosen project interval.Admit the occurrence and composite Work independently, then state the obtaining work-part relation. Otherwise retain only the temporal relation.
Team-is-projectThe temporary organization and the work it performs share one identity.Identify the organization as U.System, the project as composite U.Work, and connect them through participation relations.
Occurrence-is-processOne successful or failed execution is treated as the repeatable Method, or a local structure label is treated as an admitted process object.Select U.Method, an A.22-selected U.Structure, or TransformationFlowStructure according to the claim. Fill all four A.22 discriminators before locally calling the structure MethodRelationStructure; otherwise keep direct relations unbundled. Work supports a Method-enactment observation only when A.15.1 states which Method it enacts. An operation-application observation instead needs the declared A.6.1 operation and typed application binding.
Case-file or changed-entity substitutionA record replaces the subject, or every case is forced into one continuing affected entity.Read the closure claim, select the EntityOfConcern it names, preserve episteme-edition, characteristic or measurement, relation, decision, result, and continuing-referent identity laws, and keep the case file as a separate episteme.
Three-view collapseProject, process, and case topics assign subjects to descriptions and accounts with different subjects are published as one multi-view description.Recover one truthful EntityOfConcern from each claim-bearing whole. Split only when combining claims would make that concern untruthful or defeat the needed identity or comparison. Add the correspondence required by the use; test viewpoint conformance only for a claimed View.
Suffix-provided locality@Project or @BoundedContext is expected to establish identity, authority, or a selected structure.Name the obtaining relation and referenced object; use a typed reference when the chosen representation needs one. For a method-side structure, fill A.22’s four discriminators; no suffix contributes locality or identity.
System-role-kind-by-labelA System is classified under SystemOfInterestSystemRole because someone called it the project system-of-interest.Keep an ordinary project designation when sufficient. For classification, identify the local system-role kind and test its A.2 feature criterion. For assignment, independently select the A.2.1 species and test its declaration-local domain, predicate, applicability, participants and occurrence conditions. Require holder classification only when that declaration consumes it.
Assignment proves project designationAn obtaining system-role assignment is treated as proof that one project designated its holder.Use the designation stated by the named plan or decision for the ordinary claim. If a named decision consumes a compound selection truth, use the lightest A.6.RCD disposition and keep assignment, Work, change, and use facts separate.
Backdating a future SystemA planned controller or plant is treated as an admitted System, classified under a local system-role kind, or made an assignment holder before it exists.Keep the designator and expected use in plan content; after identity inception, test designation, classification, and assignment separately.
Project-result fieldEntities, values, conditions, choices, measurements, verdicts, decisions, relation occurrences, changed referents, and claim-bearing epistemes are grouped as one intrinsic result of the project.Ask what the result is and what it is a result of or for. Keep that subject in the kind or claim already established for it, then choose one WMR outcome. If the attempted claim cannot be asserted, preserve independently established facts and return WMR’s reason-specific stop, including the rule’s inapplicable result or missing-substrate when applicable. An absent governing rule calls for A.6.RCD’s lightest sufficient contribution.
Network-is-projectA network of transformation-flow structures is treated as the project, workflow actor, or work-breakdown structure.Keep the E.18.NET structure non-agentive and include Work in the project only through obtaining A.15.1 work-parthood.
Probe-is-constructorThe A.6.RCD:4.2 conjunction row or a reference scheme is treated as if it supplied constructor semantics.A simple one-case claim may use recoverable constructor semantics without a separately materialized substrate document. Pin the substrate for nontrivial, interoperable, proof-bearing, or reusable derivation; otherwise return missing-substrate only for the stronger unavailable claim.
Actor invented or suppressedEvery Transformation is forced to have a Work performer, or project Work, a TFS or network, a Method, a record, or the changed subject is silently put in an acting position.Ground the A.3.4 change first. Add a causal or interaction participant only when the applicable predicate and the case facts establish that position. For a Work-realized change, establish the performer System with its A.13 basis, Work, changed referent, and the relation that connects Work to the change, plus F.6 attribution only when the receiving question asks under which assignment the Work was performed; a short account may omit an unused assignment identifier. Otherwise invent no actor, assignment, Method, or Work.

A.15.6:9 - Consequences

Benefits. Cost and completion claims can refer to one actual composite Work occurrence through their predicates. A responsibility assertion separately names its predicate and participants, then applies an existing or sufficient local rule; an absent required rule yields missing-governor. The project system-of-interest, selected project-relevant network, case subjects, system-role classifications and assignments, changed referents, produced entities, evaluations, deliveries, acceptance decisions, and downstream uses retain their own facts.

A team can name the temporary work, its local subject and intended result, the performing organization and the common product-use purpose without treating them as one object. It can also tell when a described System is only intended. Process evaluation can use Work observations whose A.15.1 relation states which Method was enacted, or operation-application observations supported by a declared A.6.1 operation and typed binding, without turning observed Work into a Method or structure. Case Work can close around a continuing entity, episteme edition, characteristic inquiry, relation, decision, or result while keeping any relevant downstream use outside closure.

Costs. Practitioners must distinguish intended from performed work and recover a continuity policy when an identity ambiguity requires it. A legacy @Project reference may need its actual relation made explicit; descriptions with different EntitiesOfConcern need separate identities rather than one project label.

Limits. This pattern does not supply project-management, process-management, or case-management methods. It does not decide success, acceptance, evidence strength, authority, or result semantics. It only recovers the FPF subject and relations those methods operate on.

A.15.6:10 - Rationale

Admit actual project Work through the full A.15.1:4.1 test for the same candidate occurrence, with every actual performer’s A.13 core and any conditionally required profile. Independently grounded common construction and Work-specific facts support membership; typed enactment, containment and Work-part assertions follow under their own predicates. Use F.6 afterward for any precise assignment-bound attribution. Add an episode, continuity or aggregation claim only when the project use needs it. A short project account may omit assignment identifiers or further valid boundaries its receiving claim does not use.

State resource use, Work-to-referent facts, change, production, evaluation, delivery, acceptance and later result use as separate claims, each under its predicate and case basis. The five project-specific tests qualify that admitted Work. This preserves the performed whole’s identity while keeping its plans, performing organizations, Transformations and descriptions distinguishable.

Repeatability belongs to U.Method; direct method-side relations remain unbundled until the structure’s constituents are identified independently, its selected relations obtain, its constraints are applied, and one use frame names the selection question, admissible action and stop or return condition. Only then select one U.Structure under A.22 and, if useful for that question, call it MethodRelationStructure. Transformation-flow organization belongs to TransformationFlowStructure. None is the unique dated Work occurrence.

A case remains centered on the subject or claim named by its closure question, even when several Methods, structures, Work occurrences, Systems, results, measures, and decisions are relevant. Recovery therefore preserves more information than a three-label hierarchy.

The common product SoI and local-subject distinctions follow the same economy. A plan or decision can designate a system; a shared systemic account additionally explains why that system’s intended use organizes the participants’ joint undertaking. A.1.STM develops that basis and the connection of local contributions to it, while A.2 separately answers whether an actual System is classified under a defined local system-role kind and U.SystemRoleAssignment answers which assignment occurrence obtains. Use that designation when it answers the question.

For a one-case compound claim, recover the constructor semantics and direct facts; materialize or pin a substrate only for nontrivial derivation, interoperability, proof, or reuse. Return missing-substrate only for a needed stronger claim whose operator semantics are unavailable.

An intended future System remains claim content until inception. Reopen A.6.RCD for a reusable predicate or relation kind only when a named receiver needs that stronger result.

A.15.6:11 - SoTA-Echoing

Source contributionWhat it contributesFPF adoption
PMI, What Is a ProjectPractice terminology emphasizes a temporary endeavor producing a unique product, service, or result through structured activities.Adapt as vocabulary pressure. After A.13 and A.15.1 independently admit the actual referent as composite performed U.Work, qualify it as project Work; when precise assignment-bound attribution is current, add F.6 afterward. Keep intended product or result, task descriptions, and deliverables as related values rather than a project kind.
APM, What Is Project ManagementProject practice describes a unique transient endeavor and discrete packages of work directed toward planned objectives.Adopt the work selection. Use independently admitted transient composite Work and obtaining Work-part relations, while separating the temporary performing organization.
Winch, An Action Theory of the Project, 2025 issueDistinguishes temporary organization, permanent organization, future-oriented action, intention, and intended future state.Adapt. Keep organization, performed Work, plan or intention, affected referent, and intended state as related objects with different identities.
Sydow, Lundin, Ekstedt, and Braun, The theory of temporary organization three decades later, 2025Project plasticity and continuity persist across changing organizational arrangements.Adopt as a continuity safeguard. Use A.15.1 identity and Work-part rules, and a continuity policy when needed for the boundary question; team identity or a project label is insufficient.
Adams et al., Defining Cases and Variants for Object-Centric Event Data, 2022, and Küsters and van der Aalst, OCPQ, 2025Real events may relate to several objects; one preselected case key or flattening can lose information, while object-centric queries and constraints select bounded answers.Adopt for process and case recovery. Preserve object relations until a named use selects a grouping, query, or constraint. A selection-result episteme may serve as evidence through an independently obtaining evidence-use relation; it is not automatically a Method, Work occurrence, or case subject.
Jalali, Evaluating user acceptance of knowledge-intensive business process modeling languages, 2023In two studies of trained course participants, CMMN, DCR, and Declare received different perceived-usefulness and ease-of-use results; interactive simulation may influence learning and perceived usability.Adapt as a representation-use boundary. A notation can help practitioners represent flexible case work. The case subject, closure and any asserted Work use their own rules and facts. Keep perceived ease of use and simulation support visible when selecting a description form.

FPF uses these contributions to distinguish temporary organization, intended and performed work, and the subjects selected by process and case questions. Its own admission and relation rules then test those claims. The project, process and case accounts can inform one another without acquiring a shared identity.

A.15.6:12 - Relations

  • A.1 supplies the common construction of the candidate occurrence and defines the identities of participating Systems, affected holons and description-grounding holons.

  • A.3.1 defines reusable U.Method identity and composition. Apply A.22 to select a method-side U.Structure: identify its constituents, selected obtaining relations, applied constraints, and a use frame with the selection question, admissible action and stop or return condition. Use MethodRelationStructure only as a local designator after that selection.

  • Use A.3.4 for one actual bounded change of one continuing referent. State actor-side participants only when the applicable dynamics, interaction, participation, or causal-use predicate obtains; Work-facing performer, assignment, Work, and work-to-change claims remain separate.

  • Apply A.13 to recover each actual performer’s local agential kind and criterion, classification, obtaining assignment, scope, working situation and window, with evidence adequate for those core claims; add a characteristic profile only when a Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use consumes it.

    Use the full A.15.1:4.1 admission test for the same candidate occurrence. It connects its common construction and Work-specific facts to membership, after which grounded typed Work relations can be asserted.

    F.6 adds precise assignment-bound attribution through the same assignment only when needed. Name another enacted Method, episode, continuity claim or relation-specific aggregation when the receiving use needs it. A short account may omit unused assignment identifiers or further valid boundaries. Project qualifications preserve that Work identity and require actual Work parthood.

  • Use A.15.2 for intended work and U.WorkPlan before and during performance; a merely intended future System remains plan content rather than an actual holder.

  • Use A.2 to identify and classify local system-role kinds from their feature criteria. When assignment identity matters, A.2.1 adds an assignment occurrence and its declared U.SystemRoleAssignment species. The species defines participant meanings and the predicate; the occurrence supplies the participants and extent for the case. Neither classification nor assignment grounds project designation.

  • Use A.15.PROD only for the selected production-work, entity-identity-inception, or production-completion question.

  • A.6.RCD defines the economy among one-case claims, reusable predicates, and relation kinds. For project selection, use the plan or decision designation when sufficient. A one-case compound claim needs recoverable constructor semantics but no separately materialized substrate document unless nontrivial derivation, interoperability, proof, or reuse requires one; missing-substrate blocks only a stronger claim whose operator semantics are unavailable.

  • Apply A.6.P.WMR when result wording hides the relation. Choose one of four outcomes: obtaining direct relation, typed A.6.1 binding, local claim under A.15.PROD or A.6.RCD, or one non-assertability result. Preserve the corresponding WMR reason: factually unsupported, missing-information, missing-governor, an inapplicable result under the named rule, or missing-substrate. Keep independently established facts. Use A.6.RCD’s lightest sufficient branch if the receiving question needs the missing rule or constructor basis.

  • A.7 restores the EntityOfConcern, description-episteme, and publication boundary before a project card, charter, repository, dashboard, or other record is related to the composite work occurrence.

  • C.2.1 defines description and record episteme identity through claim content, one EntityOfConcern recoverable from that content, and the effective reference scheme. Management topics assign no subject; empirical grounding, viewpoint membership, scope, edition, and publication remain separate relations.

  • Use E.17 and E.24.PUB to publish project, process, and case accounts without replacing their subjects.

  • E.18 defines one selected transformation-flow structure. E.18.NET defines a non-agentive network only when independently identified structures and obtaining cross-boundary relations are selected; its use frame can answer one named project question. Work membership in a project requires obtaining A.15.1 work-parthood.

  • Use A.6.REL when a Work, Method, Transformation, result, or correspondence relation occurrence must be identified because it participates in another relation.

  • A.1.STM supplies the project SoI and intended-use basis for a systemic project account, distinguishes that role from local attention, and connects local results and creator provision through the system-thinking long dependency. Its first-unsupported-dependency mode remains available when the shared basis is sufficient. Use E.10 to recover project, process, case, and situation wording when source expressions remain ambiguous.

A.15.6:End

A.15.7 - Situation-Responsive Work Steering and Next-Action Selection

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Choose the next action while Work is under way and current facts matter.

Reader. A person, team, robot, AI system, organization, or other deciding System that must choose what should happen next during ongoing Work, or someone supporting that choice.

A.15.7:1 - Problem frame

Use this when. Use this pattern when you are in the middle of Work, current facts can change what should happen next, and a domain Method sets what is allowed.

First useful result. Give a supported next-action answer in ordinary language, with the content needed for its use:

  1. Decision now: state the selected continuation and its grounds, or the limitation that requires a stop or return to another question.
  2. Performer: identify the intended System performer when an action is selected. Name the chooser separately when it differs.
  3. Stop and feedback: retain the stop, fallback, reconsideration or observation condition that the selected continuation or receiving use needs.

For a reversible local choice, ordinary project language is enough. When a use needs to cite, compare, audit, or rely on an identified claim, use an existing sufficient episteme or identify one under C.2.1. Preserve access when later reliance requires it. The answer states the supported result and its grounds.

Three recognition cases.

  • A DJ is already performing. The current track is ending, the room response has changed, a promised genre constraint applies, and several known tracks remain possible. The question is what to play next, who will make the transition, and what cue would make the DJ abandon it.
  • A case worker is handling an open case. New evidence may make the displayed case state stale, while policy and authority bound the allowed response. The question is whether to refresh, take the safe fallback, compare several live actions, or stop.
  • A robotic maintenance system receives a recommendation during inspection. A sensor state has changed since the recommendation was produced. The question is whether the recommendation remains usable, needs refresh, or must give way to a safe response.

What goes wrong if missed. A plan, policy, score, case file, recommender output, dashboard, trace, or pattern body is treated as the chooser. Every cue is forced into a heavy decision record, or every adjustment is called improvisation. The team may also invent an option set after the real issue has become stale information, missing authority, missing capability, or no current Work at all.

What this buys. The user gets a supported continuation or a named blocker, with the domain Method, current Work, deciding System, intended performer when one is needed, and applicable authority, stop and feedback conditions clear. Familiar recognition, quick adaptation, explicit comparison, candidate generation, and tool-call planning remain different branches rather than one universal procedure.

Not this pattern when. Use the nearest applicable pattern instead:

  • Before Work exists, use A.15.2 for intended-work content and A.15.5 for work-entry readiness.
  • After an interruption, use A.15.10 when the purpose, governing method or unfinished contribution must be recovered before a useful next action can be selected. If these are already available, continue here.
  • When ongoing Work is blocked because a performer, support, or continuation-state relation is missing or unsupported—not because known candidates need choosing—use the actual-Work branch of A.15.8 to repair that configuration or stop, then return here.
  • For a settled short procedure with no material branch, use the applicable domain Method; consult its A.3.2 MethodDescription when a description is needed.
  • For a choice outside current Work when the chooser and OptionSet are already known, use C.11.
  • For missing action candidates, use a subject-specific generation Method; use C.18 only for an open-ended candidate archive and front.
  • After the action is fixed, use C.24 if calls to tools or services must be planned. An already prescribed action can enter C.24 before Work begins; it needs no A.15.7 decision.
  • For intended-work content or plan revision before or during Work, use A.15.2; return here when current facts require a next-action choice.
  • For retrospective Method recovery, use A.3.1.MR.

Adapt to the domain. Apply the steering Method to the domain facts, constraints and intended result that can change the next action. For example, a DJ tests a transition against the promised genre and live response; a maintenance practitioner tests an intervention against the equipment state and applicable safety conditions. The same steering operations can yield different actions because their domain premises differ.

A.15.7:2 - Problem

Situation-responsive Work needs more than permission to vary. A practitioner must notice which facts can change the continuation, remain within the applicable domain Method, distinguish choosing from performing, and know when to stop or reconsider. C.11 compares an already formed OptionSet for a known chooser. Steering selects a next continuation from current Work facts; planning records or revises intended-work content before or during performance. Tool-call planning begins after the underlying action has been fixed.

Without a steering Method, teams oscillate between two errors. They follow an obsolete plan as though nothing changed, or they call unconstrained variation improvisation and lose reviewability. In both cases the current fact, relevant Method limits, chooser, performer, and return condition disappear.

A.15.7:3 - Forces

ForceTension
Responsiveness versus method disciplineCurrent facts may require a different continuation, but the domain Method limits admissible action.
Speed versus truthfulnessKeep a supported choice as light as its consequences allow. When a changed condition or missing required support defeats a consumed premise, compare feasible refresh, a supported alternative, fallback or stop.
Recognition versus explicit comparisonA familiar cue may support one response without constructing an OptionSet; several live alternatives may require C.11.
Choice versus actionThe deciding System and intended performer may be the same or different, and neither a score nor a document occupies either position.
Domain Method versus steering MethodThe reusable way being performed and the Method for choosing its next action are distinct even when the same Work enacts both.
Feedback versus claims about past performanceA new observation can guide the next choice and reveal an earlier unsupported claim. Correct the claim while preserving the actual occurrence history.
Plain use versus durable relianceMost local choices need a readable sentence; another use may need a separately identified claim-bearing episteme and supporting relations.

A.15.7:4 - Solution

Use the following steering Method. Keep the answer as small as the current decision permits, and stop as soon as a result or blocker is available.

A.15.7:4.1 - Keep the two Method positions distinct

The domain Method is the reusable way whose current enactment is being steered. It states the applicable way of doing, participant meanings, intended result or preserved condition, allowed variation, and stops.

The steering Method supplied here uses current facts to choose one next action within those limits.

One current Work occurrence may enact the domain Method and, when this steering Method is used, also enact the steering Method. Before either claim, use A.13 to identify the actual performer and A.15.1 to admit the dated Work independently.

If this account must also say under which assignment the Work was performed, check that relation separately through F.6. Ground each enactsMethod claim separately; neither follows from the other.

If the choice must be treated as a smaller Work occurrence, identify its own performer and Work basis and state its relation to the larger Work only when that relation obtains.

A domain Method may instead be an admitted composite containing the steering Method as a submethod. That requires the identity of both Methods and a composition relation under A.3.1 and B.1.5 or another composition rule. Method composition does not prove that a Work occurrence enacted the submethod.

Reading this pattern, consulting a MethodDescription, following a plan, or receiving a recommendation does not by itself establish those Method, composition, or enactment claims.

A.15.7:4.2 - Run the seven-step steering Method

  1. Confirm current Work or close this entry. Name the ongoing Work occurrence at the grain that changes the decision. When the performed-Work claim matters, use the full A.15.1:4.1 admission test, including the candidate occurrence’s common construction and every actual performer’s A.13 core. Ground the claimed domain-Method enactment as section 4.1 explains.

    If this steering account must also identify the assignment under which the Work was performed, check that assignment separately through F.6; F.6 identifies neither performer nor assignment. Its failure alone leaves independently admitted Work intact; if the same finding questions a premise of that admission, recheck that premise and the claims that depend on it.

    If Work has not begun, stop using this pattern: use A.15.2 for intended-work content, A.15.5 for work-entry readiness, or C.11 only when a known chooser must compare an already formed OptionSet. Do not turn intended Work into a current occurrence or every small action into separate Work.

  2. Use only action-guiding information about current facts. Name the relevant observation, participant response, available material, resource or safety limit, commitment, case fact, or time pressure. Recover the source and time conditions that can change its use. A missing timestamp or the age of a record alone does not defeat applicable information.

    When a changed condition or missing required support defeats a relied-on claim, retain the other qualified information and name the affected limit. Use C.11.DUA to compare a feasible, timely refresh with a supported narrower action, the declared safe fallback or stopping. Obtain the needed evidence for the selected use; do not act on an unsupported premise because refresh is costly.

    A directly checkable live cue needs an ordinary observation sentence, not a universal situation record or evidence dossier.

  3. Recover both Method positions. State the domain Method and its relevant allowances and stops. When this steering Method is being used, keep that contribution clear. Add a separately grounded co-enactment or admitted-submethod account under section 4.1 only when that relationship is asserted or needed by the receiving use; an ordinary next-action answer need not assert either. Use a description, plan, policy, score, case model, recommendation or dashboard for the information it supplies to the deciding System.

  4. Form the smallest set of available actions. Include only actions allowed now by the domain Method and named constraints. If the Method already requires one action and no material branch remains, follow it and stop using this pattern.

    When further candidate development is needed to make a supported choice, use a subject-specific generation Method; use C.18 only when an open-ended candidate archive and front are needed.

    When the obstacle is a known constraint or missing required ground, resolve that question under its rule or stop; see step 6 and section 4.3. Do not hide invention inside choice.

  5. Use the lightest choice mode. State the cue, comparison, quick forecast, value concern, or mandatory criterion that can change the answer. A reliable cue may support a familiar response after an applicability and consequence check. A claim that it is better than alternatives additionally needs the comparison rule and basis that establish that claim.

    An unfamiliar or consequential case may require diagnosis, adaptation, or a quick mental or physical forecast.

    When several live alternatives require comparison, pass the chooser, current OptionSet and comparison basis to C.11. Include an inquiry question only when it is live under C.11’s conditions; an already supported choice needs no invented probe or omission account.

  6. Keep choosing, authority, and acting separate. Identify the deciding System and, for a selected action, the intended performer. If the choice depends on permission, responsibility, commitment, capability, or authority, establish that relation instead of inferring it from a system-role label or recommendation score.

    If its factual basis is unknown, seek the needed information from an appropriate source, use a supported alternative, or stop.

    If the required relation is known not to obtain, choose an admissible alternative, repair the relevant conditions under their governing rule, or stop. An obligation for another System to supply information or make the repair needs its own ground.

  7. Return the supported answer and its continuation conditions. When an action is selected, state it and its grounds, the intended performer, and any stop, fallback, observation or return condition needed for that use. If no action can yet be supported, state the blocker and the supported return or stop.

    If the choice revises a U.WorkPlan’s intended-work content, update that plan separately under A.15.2.

    If the receiving claim needs a distinct Work occurrence for the performed action, follow step 1 for its performer and independent admission; add F.6 only for assignment-bound attribution. Otherwise retain the action and observation at the current Work grain. Ground any asserted operation application separately.

    Use any resulting observation that bears on a subsequent choice. If it challenges an earlier Method-enactment or Work claim, recheck that claim and its dependents as in step 1; correct or retract the claim when the new grounds refute it. Preserve the actual performance history.

A.15.7:4.3 - Select the branch

SituationWhat to use nowResult and stop
The domain Method already requires one actionFollow the Method or its selected description.The required action and its existing stop; no steering or decision wrapper.
One familiar live cue points to one response and a quick consequence check passesUse the recognition branch in this pattern.One decision, intended performer, live cue, and any stop or feedback condition needed for the continuation.
Several admissible actions remain and comparison can change the choiceUse C.11; add A.19 kernels only when their comparison or selection result matters.A ChoiceResult under the applicable constraints. Return a fixed action here for performer and feedback; keep any retained tie-set explicit, and follow a reject current set, probe again, or reroute result to its stated next question.
Adequate action candidates need to be developedUse a subject-specific generation Method; use C.18 only for an open-ended archive/front question.New candidates or a failure to generate; no premature choice.
The action is fixed but calls to tools or services must be plannedUse C.24.A call plan and checkpoint return; the call plan is not the underlying choice.
A changed condition or missing required support defeats an action-guiding claimKeep the other qualified information; compare feasible, worthwhile refresh with a supported narrower action, the named safe fallback or stopping under §4.2.Qualified information supports the selected continuation, with the affected limit stated. Age or a missing administrative time field alone does not invalidate an applicable claim.
A required safety, authority, capability, applicability, or current-Work condition is unresolved or failsUse the pattern that defines or tests that condition—for example, A.2.2 for capability, A.15.1 for performed Work, and A.15.5 only for work-entry readiness; keep safety, authority, and applicability with the pattern that defines them.Retain the supported result: if a needed fact is unknown, name the gap; if the applicable test fails, name the failed condition. Obtain a needed basis, make a permitted repair, choose a supported alternative, or stop. An unresolved or failed condition does not establish action, permission, capability, Work, or a Method change.

A current account may treat an unexamined outcome or recurring adjustment as ordinary, so that no question enters this choice. B.5.PI uses a selected demonstration, handover or other ordinary work occasion to compare a result with its use and develop a question or retain an early cue. It requires access and attention, not a prior diagnosis. Use it when that contribution is needed; ordinary next-action selection does not require auditing every action.

When an available method repeatedly goes unconsidered at a relevant moment, use A.15.11 to connect it with an occasion in the work. This can make a useful candidate available to step 4; the current constraints determine which actions are admissible.

A.15.7:4.4 - Keep the first result light

For a reversible local use, speak plainly: “Choose track B because the room response changed and it satisfies the promised genre constraint; the DJ performs the transition; abandon it if the next cue shows the transition is failing.”

When a current or later use needs an identified claim-bearing episteme, reuse a sufficient one or identify one under C.2.1. State the decision or observation it concerns and the distinctions on which that use relies. Arrange durable access when later reliance requires it.

A.15.7:5 - Archetypal Grounding

A.15.7:5.1 - DJ performance

In this constructed case, assume the full A.15.1:4.1 admission basis is independently established for one performance from 20:00 to 21:00 UTC on 20 July 2026, including that occurrence’s A.1:4.2 common construction. Its complete history satisfies the declared local containment predicate’s boundary, window and applicability conditions for the admitted System EventService-1. The independently identified performer System is the DJ. The local SetPerformerRole criterion requires control over track selection and transition; the observed behavior satisfies it independently of the Work label. The declared SetPerformanceAssignment species assigns that kind when event designation and control of the set’s playback obtain. Both stipulated facts establish RA-DJ-Set1 for the stated set and window.

The performance history shows the DJ following the independently identified EventPerformanceMethod-1. With admission established, identify SetWork-1 : U.Work and assert its grounded domain-Method enactment and containing-System relation. No assignment-bound attribution is requested.

The DJ is already performing under that Method. The current track is ending, the DJ hears that room response has fallen, one promised genre constraint applies, and three known tracks fit the remaining time. The DJ rules out one track because its transition violates the domain Method, recognizes a familiar cue favoring a second, briefly checks how the transition is likely to land, and chooses it.

The answer names the chosen track and reason, the DJ as chooser and intended performer, and the condition for abandoning the transition. The described selection, cue check and stop condition supply the separate basis for saying this Work also enacts the steering Method. The performance history supplies its domain-Method enactment; neither claim follows merely from the other. The playlist supplies the available material; the performance and selection facts above ground the two enactment claims.

A.15.7:5.2 - Social dance or jazz

During one performance, a participant recognizes a familiar phrase ending and chooses a contribution that fits the domain Method and the other participants’ current response. A quick forecast is enough because the contribution is reversible and the next cue arrives immediately. If several materially different contributions need comparison, the chooser forms a current option set and opens C.11; otherwise no formal comparison record is needed.

The performers, deciding System, musical or movement material, interaction, Methods, and Work occurrence remain distinct. “Improvisation” is a retrieval word here, not a universal Method or permission for random variation.

A.15.7:5.3 - Case handling and stale information

A worker is performing one case-handling Work occurrence under a domain Method. A displayed case state predates newly filed evidence. The new evidence changes a fact consumed by the displayed state, so the worker refreshes that affected claim before relying on it. If refresh is unavailable, the worker uses the declared safe fallback or stops. The case file conveys the claims used by the worker; any authority or performed-Work claim keeps its own grounds.

The worker also uses an identified procedure whose version and applicability remain unchanged. The displayed copy has no separate expiry field, and this use requires none. The worker retains that procedure while refreshing the case-state claim affected by the new evidence. The result names the next action and its limits, with no separate certificate for retaining the unaffected procedure.

If the organization’s admitted case-handling Method already includes this steering Method, state that composition separately. Do not infer it from the case model or a repeated workflow label.

A.15.7:5.4 - AI recommendation

An AI system using a model proposes the next inspection action, but a sensor condition changed after the model’s input window closed. The model and recommendation remain separate from the deciding and performing Systems. The responsible deciding System refreshes the input, tests the recommendation under the current Method and safety constraints, uses a safe fallback, or stops. A confident score establishes neither currentness, authority, capability, nor the action.

A.15.7:6 - Bias-Annotation

  • Optimization bias: do not force every responsive choice into a fully enumerated optimization problem.
  • Human-only bias: deciding and performing Systems may be people, teams, robots, AI systems, organizations, or other equipped or combined arrangements.
  • Automation bias: a recommender output, score, dashboard, or case file informs a decision only through current and applicable claims; it does not become the chooser.
  • Improvisation romanticism: responsiveness remains bounded by the domain Method, constraints, and stop conditions.
  • Record inflation: durable records are optional and use-driven; an observation sentence can be enough.

A.15.7:7 - Conformance Checklist

  • CC-A15.7-1 — Current Work. Is ongoing Work identified, or did the user stop and name A.15.2, A.15.5, or C.11 for the question that remains?
  • CC-A15.7-2 — Method limits. Is the applicable domain Method and the relevant allowance or stop explicit?
  • CC-A15.7-3 — Action-guiding information. Does every stated fact matter to the action, and is the observation, report, recommendation, or other information current enough when that matters?
  • CC-A15.7-4 — Method relation. Are domain and steering Methods distinct, with co-enactment or composition asserted only from its own basis?
  • CC-A15.7-5 — Available actions. Are mandatory action, recognition, comparison, generation, and tool-planning branches kept separate?
  • CC-A15.7-6 — Chooser and performer. Are the deciding System and, when an action is selected, its intended performer clear, with any authority or capability claim grounded separately?
  • CC-A15.7-7 — First result. Does the answer state the supported continuation or blocker and its grounds, with any stop or feedback condition needed for its use?
  • CC-A15.7-8 — History and corrected claims. Are later observations, plan changes, performed actions and Method changes kept at their actual times, with any refuted earlier claim corrected and its dependents rechecked?
  • CC-A15.7-9 — Plain use. Can a cold practitioner understand what to do before meeting the formal distinctions?

A.15.7:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The dashboard chose the next action.”Name the deciding System; state which current dashboard claim it used and why that claim remained applicable.
“We improvised.”State the relevant domain-Method limits, current fact, chosen action, performer, and any applicable stop or feedback condition.
“Every cue needs a decision dossier.”Keep a reversible live cue in ordinary language unless another use relies on a durable claim.
“The steering Method is obviously part of the domain Method.”Assert composition only with the admitted Methods and an obtaining composition relation. A needed co-enactment claim instead requires two separately grounded enactments. If neither relationship is asserted or needed, retain the ordinary next-action answer without adding one.
“The recommendation was recent enough.”Establish that the action-guiding claims remain applicable. When a consumed premise is defeated, refresh it, use a supported alternative or safe fallback, or stop.
“The plan already contains the action, so Work occurred.”Keep plan revision, next-action answer, and performed Work separate.
“Several options might exist, so use C.11 first.”Recover the current Work, relevant Method limits, facts, and available actions first; use C.11 when the live alternatives need comparison.

A.15.7:9 - Consequences

BenefitCost or caution
Responsive Work remains methodical without becoming rigid.The practitioner must identify the few facts that can change the next action.
Familiar cue recognition stays lightweight.High-consequence cases require grounds adequate to the consequence. An already supported choice may suffice; uncertainty in a consumed premise can require comparison, refresh, fallback, or stop.
Choosing, authority, and acting remain visible.A recommender cannot absorb accountability merely because it supplies a score.
Feedback can improve later choices or Methods.Preserve the actual occurrence history. Correct or retract an earlier claim when new grounds refute it, and recheck dependent conclusions. Preserve an earlier claim edition when the receiving use needs it.
C.11, candidate generation, and C.24 keep clear entry points.The user must stop this pattern when another question becomes current.

A.15.7:10 - Rationale

This pattern supplies a reusable Method for a common working question: what should happen next during current Work, which System is to perform it, and which current facts and domain-Method limits support that choice? Name the deciding System separately when it differs from the intended performer. Keeping the steering Method distinct from the domain Method permits separate enactment or composition claims when the use needs them and their grounds hold.

The pattern begins before late-stage option comparison and ends before tool-call planning or performed-action recording. That placement keeps the first result small and makes explicit comparison, generation, planning, evidence, and assurance conditional rather than universal burdens.

A.15.7:11 - SoTA-Echoing

Source lineContributionFPF adoption
Reviews of high-risk decision-making (2023) and recognition-primed decision-making in sport (2022)Distinguish direct recognition, diagnosis or adaptation, quick simulation, rule-based response, analytic comparison, and adaptive response in different situations.Adopt the plurality of choice modes. Do not turn one occupational model into a universal law; use the lightest mode for the current case.
Mature representation standard: OMG CMMN 1.1 (2016)Represents discretionary, event-centered case work whose later actions can depend on changing case information.Use as a representation contrast, not as current universal practice. A case account can name or describe its deciding System. That System’s agency and authority, and the next-action Method used, require their own grounds; notation alone does not establish them.
OMG Essence 2.0 Beta 2 (beta, March 2026)Offers a beta proposal for describing and composing engineering-method elements.Use only as neighboring beta Method Engineering. Its beta status and method-description purpose do not make it a stable next-action doctrine.
Method Engineering lineage: the 2010 situational Method Engineering review and a 2023 reviewDescribe ways to construct or adapt Methods for a situation.Keep as neighboring Method Engineering. Constructing or describing a Method and choosing the next action during its enactment are distinct activities; a claim about a dated Work occurrence of either requires its own A.15.1 basis after A.13 identifies the performer.

A.15.7:12 - Relations

  • Builds on: A.3.1 for domain and steering Method identity; A.13 for each actual performer; A.15.1 for independently admitted current Work and each separately obtaining enactment; F.6 when the result must also identify the assignment under which that Work was performed; and A.10 when a source-to-use account must remain replayable.
  • Coordinates with: A.15 for SystemRole–Method–Work alignment before next-action selection; A.15.6 for recovery of the subject from project, process, or case wording before live Work steering; A.15.2 for intended-work content and a separate WorkPlan change; A.15.5 for work-entry readiness; B.1.5 for admitted Method composition; C.11 for comparison among a current OptionSet; A.19 only for a comparison or selector result; C.18 only for an open-ended candidate archive/front; C.24 for tool-call planning after the action is fixed; and G.11 for scoped refresh.
  • Keeps separate: chooser, intended performer, authority, capability, MethodDescription, plan, recommendation, performed action, result, and later Method or description change.

A.15.7:End

A.15.8 - Work-Performance Configuration and Recovery Testing

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Test whether the performer, support, and continuation-state configuration for Work can continue or recover when something important changes.

Reader. A practitioner preparing or performing human, automated, biological, organizational, computational, or mixed Work whose result may depend on several Systems, tools, records, resources, and environmental conditions.

A.15.8:1 - Problem frame

Use this when. Use this pattern when a result succeeds in one configuration but may fail after interruption, handoff, delay, support loss, replacement, or changed conditions, and the decision needs to know which relation to repair or test. Choose the branch for the focus being examined:

  • Actual-Work branch: start from one dated U.Work occurrence already admitted under A.15.1. Name actual performers, assignments, and attribution only where the rules governing those claims pass.
  • Present-WorkPlan branch: start from one present U.WorkPlan under A.15.2. Intended performers and intended performance remain declaration-local plan content; they are not an existing future U.Work, obtaining assignment, or actual attribution.

Start with a sentence appropriate to that branch:

Actual Work: For this admitted Work occurrence, these Systems performed it under the attribution rules; these other Systems or values supported it; this is where the state needed to continue lives; this is what the available evidence establishes about continuation or recovery; continue within the supported conditions, repair the affected relation, or stop as that result warrants.

Present WorkPlan: For this present WorkPlan, these Systems are named as intended performers in its declaration-local content; these other Systems or values support the proposed configuration; this is where the state needed for intended performance would be recovered; this is what the current plan and probe evidence support or leave unresolved; obtain a needed basis, revise the plan, continue within the supported conditions, or stop as that result warrants.

First useful result. Return a short branch-specific account of the Work or WorkPlan focus, required result and receiving decision, performers, supports, continuation state and probe observations needed by that decision, the supported, failed or unresolved relation claims, and the warranted next action or stop.

What changes in practice. Instead of saying that a person, tool, team, organism, service, or machine must “pay attention”, “remember”, or become one “extended performer”, the practitioner names the relation whose loss changes continuation or recovery and challenges that relation under one representative condition. The next move follows the result: continue within the supported conditions, obtain a needed basis, make a bounded configuration or plan repair, or stop.

Cheap non-use. Do not use this pattern merely because Work uses a tool, a person takes notes, software has state, a bacterium responds to its environment, or several Systems participate.

Stop when current results from domain Work already identify the configuration of the named Work or WorkPlan, continuation state, representative recovery evidence, and limits needed by the decision, with the applicable Method and evidence boundary explicit.

If A.15.5 has established an ordinary full kit and no interruption, handoff, support loss, or configuration ambiguity can change entry, stop there. If the configuration is adequate and only the next action during current Work is open, use A.15.7. For ordinary preparation and return after an interruption, use A.15.10 when the purpose, method or unfinished contribution must be recovered; that use does not require a configuration test.

Not this pattern when. Use A.1 to recognize a proposed System, and B.2 when changed facts require comparison with an established prior whole; A.2.2 for capability of one admitted holder; A.15.1 for Work occurrence identity or resumption segmentation; A.15.2 for the WorkPlan; A.15.5 for ordinary entry readiness; A.15.7 for next-action selection; A.22 for one selected Structure; C.30 for architecture; the pattern governing a representation; A.2.4 for the first evidence-use or status-use classification and A.10 when the bounded source-to-use account must remain replayable; or the applicable domain Method when only its test, threshold, algorithm, safety rule, or intervention is missing.

A.15.8:2 - Problem

Performance often depends on relations among actual or intended performers, supporting Systems, physical resources, representations, records, services, models, environmental conditions, and state needed for continuation. A perfect run can hide that one dependency is stale, inaccessible, inconsistent, unavailable to a successor, or supported only by the current session.

Umbrella words conceal different objects. “Attention” may mean sensing, selection, monitoring, search, checking, or a holder capability. “Memory” may mean internal state, a record, model state, retrieval, cultural continuation, or a relied-on claim. “Work state” may mix world state, epistemes, carriers, and cues. Treating these words as fields on one composite performer hides the relation that must change and can incorrectly assign System identity, Work, capability, authority, or evidence.

Recover the Work-dependent configuration and expose the minimum state needed to continue. Under a representative condition, test a dependency whose result can change the decision. If the available evidence identifies the weakest such dependency, test that one. Return the result to the pattern that defines or tests the affected claim.

A.15.8:3 - Forces

ForceTension
Useful whole versus justified wholeA coupled arrangement can be a useful unit of analysis without being one admitted U.System, performer, Agent, or capability holder.
Actual versus prospectiveActual Work permits obtaining performer and support claims; a present WorkPlan permits only current claims about plan content and a proposed configuration.
Compact result versus separate ownershipA reader needs one short result, while System identity, Work, capability, representation, evidence, architecture, and choice remain independently governed.
Perfect-run success versus recoverabilitySuccess in one live configuration does not establish recovery after interruption, handoff, staleness, or degraded support.
Transferable skeleton versus domain mechanismMany domains share the configuration-and-probe move, but their checkpoints, cues, thresholds, safety conditions, and recovery mechanisms differ.
Recognition versus assuranceOne credible failure can open the pattern; consequential use may require much stronger evidence, authority, and stop rules.
State availability versus state correctnessA carrier may be present while its value is stale, inconsistent, uninterpretable, inaccessible, or unsafe to use.

A.15.8:4 - Solution

Choose one branch, keep every System and value separately identified, recover only relations that can change the named result or decision, and run the least burdensome representative probe capable of exposing a dependency that can change the decision. Return the branch-specific result to the patterns governing the affected claims. Do not first decide whether cognition, mind, or agency is “extended”.

A.15.8:4.1 - Keep the focus and participating objects explicit

In the actual branch, the governed world-side focus is one admitted U.Work occurrence. In the prospective branch, it is one present U.WorkPlan; proposed performance stays declaration-local content of that episteme.

Supporting Systems and values may be inside or outside a selected containing-System boundary. Their contribution, dependency, access, update, control, or other relations must be declared and supported when the result relies on them.

An arrangement remains ordinary prose unless another use needs a U.Structure admitted under A.22. An architecture claim enters only through C.30. A configuration account can designate several independently governed Systems and values without making them one whole or using a plural EntityOfConcern.

A.15.8:4.2 - Follow the seven-step configuration-and-recovery sequence

  1. Choose the branch and name its focus, required result, and receiving decision. For an actual case identify one dated U.Work occurrence under A.15.1. For a prospective case identify one present U.WorkPlan under A.15.2 and the declaration-local intended-performance content used by the configuration claim. Use A.15.5 only when entry readiness is current. Do not call intended performance a future Work entity.

  2. Keep performers, intended performers, supports, and values separate. In the actual branch identify the admitted Systems that performed the Work, with assignments and attribution only where their predicates pass. In the prospective branch name intended performers only inside the WorkPlan’s claim content. In either branch identify supporting and external interacting Systems, physical resources, representations, records, models, tools, services, and environmental conditions without forcing them into one whole.

  3. Recover contributions and dependencies. Translate words such as attention, memory, computation, and checking into sensing, selection, monitoring, operation, record, state, evaluation, communication, access, update, control, or other relations. For actual Work, retain only relations whose obtaining, loss, or change can alter continuation, result, or recovery of that occurrence. For a WorkPlan, retain only relations whose obtaining, loss, or change can alter the current plan, proposed configuration, or intended-performance content.

    For every attempted relation claim, name the participants and receiving use. When a current predicate definition, applicability condition, occurrence rule, or other governor can state or test it, apply that governor and preserve its result: use factually unsupported only when the available case basis is sufficient and the positive test fails, missing-information when a needed fact is unavailable, and an inapplicable or negative result only under the governor’s own rule.

    Return missing-governor only when no current rule can state or test the attempted claim for those participants and that use. Name capability and authority only when their claims are current.

  4. Expose the minimum continuation state. For each value needed after interruption, handoff, support loss, or delay, state what it concerns. Recover where it resides, who or what may update and use it, how currentness or consistency is determined, and what makes it usable on return, insofar as those details affect the continuation. Keep world state, claims, carriers, and cues distinct.

  5. Select a representative decision-changing condition. Choose one representative interruption, handoff, degraded support, changed performer, changed tool or environment, or delayed-continuation condition. Apply it to the named Work occurrence in the actual branch. In the prospective branch, formulate it as a condition of the current WorkPlan, proposed configuration, or intended-performance content.

    If the receiving claim identifies a distinct test or later-performance Work occurrence, admit it through A.13 and A.15.1; an ordinary observation can remain within the current Work grain. A proposed condition stays in the plan or probe claim. Do not demand a ritual battery.

  6. Run the domain probe and observe recovery. Select an applicable human-factors, biological, software, robotics, operations, rehearsal, safety, or other domain U.Method only to define or constrain the probe, mechanism, thresholds, safety rules, and evidence rules.

    When the account claims a distinct dated probe Work, recover each actual performer through A.13, admit that Work independently under A.15.1, and ground its enactment of the Method. Add A.2.1 and F.6 only when this probe account consumes assignment-bound attribution through the same obtaining A.13 assignment. A missing or failed attribution alone leaves independently admitted probe Work intact. If the finding also questions a premise of that admission, recheck that premise and its dependent claims.

    When the probe remains prospective, keep it as a condition in the WorkPlan or probe claim.

    Observe result recovery, time or burden where material, wrong continuation, missing or stale state, unsupported dependency, protected-condition loss, and fallback or stop. This pattern supplies no universal cue, timeout, checkpoint algorithm, intervention, or safety threshold.

  7. Return one branch-specific account for the affected claims. State which Work occurrence or present WorkPlan is the focus, what configuration is supported for which occurrence or intended-performance content and window, what failed or remains unknown, and the warranted continuation, repair or stop.

    Return System recognition to A.1 and comparison with an established prior whole to B.2; Structure to A.22; architecture to C.30; capability to A.2.2; actual Work and resumption identity to A.15.1; plan content and plan change to A.15.2; representations to their governing patterns; first evidence-use classification to A.2.4 and a needed replayable source-to-use account to A.10; a receiving choice to C.11; and next-action selection during current Work to A.15.7.

A.15.8:4.3 - Return the first result in plain language

The following prompts can help state the account; omit those the receiving decision does not need:

Focus: actual U.Work occurrence … / present U.WorkPlan … and its declaration-local intended-performance designator …

Required result and receiving decision: …

Actual performers for the Work / intended performers in the plan, plus supports: …

State needed to continue and where it is recovered: …

Probe and observation: …

Relation result or blocker, and warranted next action or stop: …

For a small reversible use, this ordinary prose is enough. Its conclusion is limited to the named configuration, condition, window and available evidence.

A.15.8:4.4 - Persist only the account another use needs

When a current or later use needs an identified account, reuse a sufficient episteme or identify one under C.2.1. Arrange durable access when later reliance requires it.

  • An actual-branch account selects the U.Work occurrence as its one truthful EntityOfConcern.
  • A prospective-branch account selects the present U.WorkPlan as its one truthful EntityOfConcern. Its ClaimGraph may designate the declaration-local intended-performance content; that designation alone establishes no dated Work occurrence.
  • The ClaimGraph may also designate independently governed actual or intended performers, supports, state bearers, relation claims, and the governor’s result. It may record the ordinary A.6.RCD blocker factually unsupported, missing-information, or missing-governor only under that pattern’s three-way split; these phrases are not new kinds or relation values. Probe observations, uncertainty, and the warranted next action or stop remain separate claim content.
  • The effective reference scheme always supplies the designation and interpretation rules needed by those claims and adds only the measurement, comparison, or evaluation rules used. Any actual measurement, comparison, or evaluation occurrence remains under the pattern governing it.
  • If one focus cannot truthfully carry the combined claims, keep claims local or use several epistemes. Do not invent a plural focus.

The account describes the configuration or WorkPlan; it is distinct from its focus and carrier. Its claims may support a named target claim under A.2.4. Use A.10 when the source-to-use account must remain replayable; establish each described relation or actual performance under its own rule and facts.

A.15.8:4.5 - Separate recognition from assurance

  • Recognition: one actual or credible failure under interruption, transfer, support loss, or stale intermediate state is enough to open A.15.8. One ordinary sentence can name the first weak relation and probe.
  • Assurance: safety-, release-, compliance-, irreversible-, or high-impact use adds the applicable direct test, evidence, assurance, authority, and stop rules. A successful probe does not establish universal readiness or waive those rules.

A.15.8:5 - Precision restoration

Recover the object or relation before relying on the umbrella word.

Source phraseRecover before relying on itDo not infer
extended performerSelect the branch first. For actual Work, name admitted performer Systems and obtaining assignments or attribution only through the rules governing those claims. For a WorkPlan, keep intended performers in declaration-local plan content. In both branches name supports, relations, and the boundary selected for the use.Coupled things form one System, Agent, mind, performer, or capability holder.
attentionAfter branch selection, recover the observation, sensing, selection, prioritization, monitoring, search, checking, or capability claim whose obtaining, loss, or change affects the named Work or current WorkPlan.One scalar resource or mechanism is shared by a person, model, robot, organization, and collective.
memoryRecover the holder capability, internal state, model state, record or episteme, persistent runtime state, cultural-continuation claim, or retrieval, update, and forgetting relation that is current.Storage, retrieval, capability, knowledge, model state, and cultural continuation are one value.
computationRecover the operation, Method, performed Work, performing System, inputs, outputs, and resource relation when each is current.A model, calculator, or service performs the containing Work merely because it computes.
checkingRecover the observation, monitoring, evaluation, verification, validation, assurance, or decision and its separately governed result. Identify dated Work only when that occurrence is part of the claim.A checklist or score performs checking, supplies authority, or proves fitness.
work stateRecover the minimum world-side states, claims, intermediate results, commitments, configuration values, bearers, carriers, update/use relations, and currentness conditions needed for the named continuation.A record is identical to world state, or persistence proves resumability.
cue or return pointRecover the sign, representation, event, location, state condition, or source-finding aid; who or what interprets it; and the observation that it changes recovery. Use A.2.4 for a claim used as evidence, A.10 when its source-to-use account must remain replayable, and A.15.4 when appearance-based reliance hides its owner.A cue is evidence of correctness, a universal trigger, or an obtaining recovery relation by appearance alone.
configuration or arrangementRecover the Systems, values, and obtaining or proposed relations needed by the branch. Use A.22 or C.30 only when a selected Structure or architecture claim is required.A support list is already one Structure, architecture, whole, or performer.

Bias check. Human-centered cognitive vocabulary and anthropomorphic AI vocabulary are easy to recognize and therefore easy to overgeneralize. Begin with the Work or WorkPlan and recover the participants, values and relations needed for its result.

A.15.8:6 - Worked cases

A.15.8:6.1 - Literature qualification across a researcher, services, and files

Situation. In this constructed case, LiteratureQualificationWork-2026-08-27-AM runs from 09:00 to 11:00 UTC on 27 August 2026 within the admitted containing System ResearchService-3, enacting the admitted LiteratureQualificationMethod-2. The independently identified performer System Researcher-17 satisfies the local LiteratureQualifierRole criterion by controlling source selection and claim qualification. The declared ResearchAssignment species assigns LiteratureQualifierRole to a System when its question designation and authorized source access obtain. Those stipulated facts establish RA-Researcher17-Question6 throughout this interval and complete the A.13 core.

This constructed case stipulates the full A.15.1:4.1 admission basis, including that core, the independent performance history, A.1:4.2 construction, and a declared containing-System relation covering the complete occurrence. Because this account also compares accountability, F.6 then checks attribution through that same assignment.

A search service, language-model service, repository, pinned papers, claim sheet, and unresolved-question note support the Work; none becomes a performer or constituent of a new whole merely by appearing in the configuration. A reviewer may continue later.

Probe. The fresh-session and reviewer-handoff probe removes the original model session and asks the reviewer to recover the bounded question, source editions, accepted and rejected claim reasons, open uncertainty, and next probe.

Observation and result. The reviewer can recover the papers but cannot distinguish why one claim was rejected because the claim sheet lacks a decision reason and one citation lacks an edition pin. The result focuses on the Work occurrence, identifies the missing source and record relations, and returns two repairs to their representation and source owners. Do not rely on the unrecovered qualification; retain independently supported claims.

What changed. Recover the missing source edition and decision reason for that qualification, or retain the bounded stop.

A.15.8:6.2 - Non-human distributed computation after worker loss

Situation. In this constructed case, SettlementComputationWork-2026-08-27-Run42 runs from 08:00 to 12:00 UTC on 27 August 2026 within the admitted containing System SettlementService-2, enacting SettlementMethod-5. Its independently identified performer Systems Worker-1 and Worker-2 satisfy the local SettlementExecutorRole criterion through observed message processing and settlement-effect control. The declared SettlementExecutionAssignment species assigns that kind when registration for Run42 and connection to its queue obtain. Those stipulated facts establish RA-Worker1-Run42 and RA-Worker2-Run42 throughout the Work window.

The full A.15.1:4.1 admission basis is stipulated, including A.1:4.2 construction and a declared containing-System relation covering the complete occurrence. The performance history establishes the Method enactment. No assignment-bound attribution is required for these workers.

They exchange messages and use an object store, configuration values, intermediate results, completed-effect records, and provenance records. Another worker must continue without duplicating an irreversible settlement effect.

Probe. The independently identified RecoveryTestController-Run42 : U.System satisfies the local RecoveryProbeControllerRole criterion by controlling worker removal and observing recovery. WorkerLossRecoveryProbeWork-Run42-P1 : U.Work runs from 09:15 to 09:20 UTC on the same date within SettlementService-2. The full A.15.1:4.1 admission basis is stipulated, including A.1:4.2 construction and a declared containing-System relation covering the complete occurrence. Its history establishes that it enacts the admitted WorkerLossRecoveryTestMethod-1.

The declared RecoveryControllerAssignment species assigns RecoveryProbeControllerRole when probe designation and connection to the control interface obtain. Those stipulated facts establish RA-Controller42-P1 for that interval and complete the A.13 core. The comparison also uses which assignment covered the probe, so F.6 checks attribution through this same assignment.

The probe removes one worker after a message has been emitted but before its local completion record is available, then attempts recovery from the selected state mechanism.

Observation and result. Process state is recoverable, but channel state and the completed-effect provenance relation are not mutually consistent. The branch-specific account names those state bearers and update/use relations and returns the missing idempotency or provenance condition. A Chandy-Lamport snapshot, event sourcing, transaction protocol, or another computing Method may be selected as the reusable way for the repair. If the receiving account needs a distinct repair Work, admit its performer and occurrence through A.13 and A.15.1 and ground its Method enactment. An ordinary repair need not acquire a separate occurrence identity.

What changed. Add or repair the checkpoint, provenance, or idempotency condition.

A.15.8:6.3 - Equipped performer in a present WorkPlan

Situation. ConcertPerformancePlan-2026-09-12 is one present U.WorkPlan. Its declaration-local content names a musician and a robotic prosthesis controller as intended performers for a proposed performance after device replacement. It also names an instrument, cue source, power support, control link, and allowed latency. None of this content is a future Work occurrence or obtaining assignment.

Probe. The current plan proposes a rehearsal under changed latency and a degraded visual-cue condition. Its material, timing, control, threshold, and stop rules are taken from the applicable music-performance, robotics, human-factors, and safety Methods. If the account identifies a dated rehearsal Work, first recover each actual performer through A.13 and admit that Work independently under A.15.1.

Observation and result. Current evidence leaves recovery after cue loss within the required timing window unresolved. The WorkPlan-focused account names the intended performers, support and control relations, return condition, uncertainty, and the planned probe. Obtain the needed recovery evidence through the planned rehearsal or another sufficient source, or stop the dependent use. Change the cue/control relation or narrow the proposed use when the result requires it. Capability claims for the musician, device, or any independently admitted whole stay separate.

What changed. Resolve the recovery question before relying on a dependent entry-readiness claim. Make any needed configuration repair under the applicable domain conditions.

A.15.8:7 - Conformance and practical checks

A use conforms to this pattern only when it passes the checks that its claimed result needs:

  1. A cold reader can obtain the first result without deciding whether cognition or mind is extended.
  2. The selected focus is one admitted actual U.Work occurrence or one present U.WorkPlan; intended performance remains declaration-local plan content.
  3. Actual performers, intended performers, supports, values, and environmental conditions remain distinct. Every attempted relation claim names participants and the receiving use, applies a current governor when one exists, and preserves its factually unsupported, missing-information, inapplicable, negative, or other result; missing-governor is used only when no rule can state or test that claim.
  4. No arrangement becomes a System, performer, Agent, capability holder, Structure, architecture, or evidence merely by inclusion or wording.
  5. Continuation-critical state names its concern, bearer or carrier, update and use relations, currentness or consistency condition, and return condition when each matters.
  6. The probe uses the least burdensome representative condition that can change the receiving decision; its mechanism, thresholds, safety rules, and evidence rules come from an applicable domain Method. For any dated probe Work, recover the actual performer through A.13 and let A.15.1 independently admit the occurrence; add F.6 only for a consumed assignment-bound attribution, whose failure alone preserves independent Work admission unless the finding also questions an admission premise.
  7. A distinct test or later-performance Work asserted by the account has its own A.13 and A.15.1 basis; ordinary observations may stay within the current Work grain. A proposed condition remains a plan or probe claim.
  8. The result states what the available evidence establishes for the selected condition and window, any unsupported dependency and its reason, and the warranted next action or stop.
  9. A relied-on account has one truthful C.2.1 focus and effective ReferenceScheme; incompatible focuses split instead of forming a plural EntityOfConcern.
  10. Recognition and assurance remain separate; high-consequence use opens direct evidence, assurance, authority, and domain-stop rules.

Recognition check. Ask a reader to produce the compact result from one case in ordinary language. If the reader first needs a theory of attention, a new performer whole, a capability diagnosis, or a full architecture model, repair the entry and boundary.

Assurance check. For consequential use, identify the direct test, evidence, criterion, authority, protected condition, applicability window and stop that the proposed use requires. If a required basis is missing, retain the configuration observation and leave only the dependent readiness, safety, release or permission claim unsupported.

A.15.8:8 - Anti-patterns

  • Composite by coupling. Treating person, device, service, records, and environment as one performer because they jointly matter.
  • Future Work from a plan. Giving intended performance, intended performers, or proposed relations actual Work identity or obtaining attribution.
  • Umbrella slots. Adding universal attention, memory, cue, or Work-state fields instead of recovering objects and relations.
  • Carrier equals state. Treating a note, trace, checkpoint, model context, or file as identical to the world state or claim it carries.
  • Perfect-run readiness. Generalizing one successful live configuration to interruption, handoff, support loss, or changed conditions.
  • Probe as assurance. Treating success under one probe as universal capability, safety, permission, release, or certification.
  • FPF as domain algorithm. Inventing a universal timeout, checkpoint, cue, redundancy, practice, or recovery procedure in this pattern.
  • Configuration as architecture by default. Naming a support list a Structure or ArchitectureRelation without the admission and selection rules.

A.15.8:9 - Consequences and trade-offs

ConsequencePractical effect
Named failure relationRepairs target an assignment, interface, carrier, update rule, source pin, control link, support condition, or return condition rather than a vague lack of attention or memory.
Neutral transferThe same entry and result work for people, software, machines, organisms, teams, and mixed configurations.
Preserved ownershipWork, plan, capability, System identity, representation, evidence, architecture, and choice remain independently checkable.
Better handoff and degraded-mode evidenceA representative interruption or support-loss probe can expose dependencies hidden by a perfect run.
Additional modeling costIdentifying the needed relations and recovery conditions takes more effort than using one umbrella noun.
Bounded conclusionA conclusion is bounded by the named configuration, condition, window and evidence available; further assurance or transfer needs its direct grounds.

A.15.8:10 - SoTA-echoing source effects

Use these source contributions to identify relations and select probes while retaining their domain limits.

Source traditionUse of the cited contributionAction-changing contribution retainedLimit retained
Clark and Chalmers, “The Extended Mind” (1998)Retain as historical lineage and a live contrast; reject constitutive extension as an FPF System-admission or performer-attribution rule.Makes constitutive extension a live alternative and therefore forces an explicit boundary rather than an implicit “extended performer”.Coupling or parity is not an FPF System-admission test, Work-attribution rule, or design Method.
Hutchins, cockpit memory (1995), and Hollan, Hutchins, and Kirsh, distributed cognition (2000)Retain as historical cognitive-science lineage; adapt only the search for information propagation and material supports.Inspect information propagation and material supports around activity, not only an unaided person.An analytical unit is not automatically one System or capability holder, and the human-technology lineage is not universal ontology.
Hollnagel and Woods, cognitive systems engineering, and Fern, NASA HMI study (2016)Retain human-factors and cognitive-systems-engineering lineage plus the 2016 NASA application; adapt only coordination/recovery search and stress-scenario use.Add coordination, synchronization, interface, and recovery relations and use stress scenarios instead of component lists alone.“Joint cognitive system” remains a source-local stance and supplies no general whole identity, authority, safety, or evidence rule.
NASA, Objective Function Allocation Method, page updated 2024Adapt the cited official project record as a scoped systems-engineering and human-factors allocation example.Compare alternative human, automation, and robotic allocations as performance configurations rather than by static stereotypes.Allocation quantities and trade-offs remain systems-engineering and human-factors Methods.
ISO 6385:2016 and ISO/IEC CD 25589Use the cited ergonomic standard as a scoped inventory reference and the cited committee-draft edition as a specialist contrast.Make workers, equipment, space, environment, interaction, and current human-machine-teaming questions visible in the inventory.One is ergonomic and human-centred; the cited edition of the other is a specialist draft. Neither creates a transdisciplinary WorkSystem or team kind.
Hodgetts and Jones, interruption recovery (2006); Ratwani and Trafton, cue association (2010); Ülkü et al., resumption timing (2025)Retain the 2006/2010 human-task studies as empirical lineage and adapt the 2025 study as a bounded probe source.Make return cues and resumption conditions testable rather than inferred from perfect-run performance.Bounded human laboratory tasks establish no universal cue, delay, mechanism, threshold, or transfer to unlike Work.
Chandy and Lamport, distributed snapshots (1985), and Marinho et al., workflow provenance (2021)Retain mature distributed-systems lineage and adapt the 2021 provenance result as a non-human recovery stress test.Supply the non-human contrast: recovery may require consistent process, channel, control-flow, and provenance state.Snapshot and provenance techniques are computing Methods, not universal FPF algorithms or proof that every Work needs a checkpoint.
Hu, Wang, and McAuley, MemoryAgentBench (ICLR 2026), and Liu and Gabriel, PM-Bench (COLM 2026)Adapt these cited benchmarks only for their configuration-specific probe distinctions.Separate retrieval, updating, long-range use, forgetting, deferred-intention execution, and environment monitoring into configuration-specific probes.Benchmark labels are not FPF kinds or capability holders; the reported results do not transfer outside tested agent configurations without evidence.

A.15.8:11 - Relations

A.15.8.MS constructs how methodological material is obtained and applied across the named tasks, including a Method Base only when its maintained shared selection earns its cost. It returns the actual-Work or WorkPlan continuation question here when interruption or support loss is material.

  • Builds on: A.1 and A.13 for admitted Systems and actual-performer cores; A.15.1 for independent actual-Work admission; A.2.1 and F.6 only for a consumed assignment-bound attribution; A.15.2 for present WorkPlans and declaration-local intended-performance content; A.6.REL and the patterns defining obtaining relations; A.6.RCD for the missing-governor, factually unsupported, and missing-information split; and C.2.1 when a use needs an identified account episteme.
  • Coordinates with: A.15.5 for work-entry readiness; A.15.7 when the configuration is adequate and next-action selection during current Work remains open; A.2.2, E.23.CAE, and E.23.CDI for holder capability, the wider access/expression differential, and capability development; A.22 and C.30 for selected Structure and architecture; C.27.TA for temporal/currentness claims; C.2.P.DR and the patterns governing carriers and representations; A.2.4 for first evidence-use classification and A.10 for a needed replayable source-to-use account; A.15.4 for appearance-based reliance repair; C.11 for receiving decisions; domain patterns and Methods for probe mechanisms, thresholds, and safety rules; and subject patterns for authority and evidence. An A.15.8 observation may support an E.23.CAE configuration disposition, while the Work/WorkPlan relation test remains here.
  • Informs: domain patterns for equipped or joint performance, human capability development, organizational coordination, operations and service recovery, human factors, robotics, software and distributed systems, and biological Work when they retain their own quantities, mechanisms, evidence, and stops.

A.15.8:12 - Didactic quick card

  • Which branch? Actual dated Work, or a present WorkPlan with intended performance only as plan content.
  • Who performs? Independently identified actual performer Systems; add assignment-bound attribution only when needed. Keep intended performers within plan content.
  • What supports? Separately identified Systems and values through relations.
  • What must survive? The minimum state and the bearer, carrier, update/use, currentness and return conditions needed for continuation.
  • What do we test? Use an applicable domain Method to define one decision-changing loss, handoff, delay, or reconfiguration; identify a distinct dated probe Work only when the account needs that occurrence claim, with its A.13 and A.15.1 basis.
  • What comes back? What is supported, failed or unresolved for the named configuration and window, and the warranted next action or stop.

A.15.8:End

A.15.8.MS - Configure Methodological Support for Work

Type: Method pattern Status: Stable

Working result: a tested configuration that covers a bounded set of named-user tasks, or a lower result: several retained candidates, a stated split boundary, or a missing priority or test. Method material, user Systems, participating Systems, relations, Work, results, and gaps remain separate. An A.22 selected structure is returned only when its four identity discriminators obtain for the named use. A claim of dated selection Work needs its own performance basis.

A.15.8.MS:0 - Use This When

Use this pattern when Method material exists but named user Systems cannot reliably find the current edition, distinguish status, compare alternatives, tailor a branch, use a needed tool or automation, give feedback, or stop at the right boundary. A named user may be human, automated, biological, organizational, computational, or mixed; performance, capability, permission, and authority require their own facts. Begin with the failed or at-risk user task, not with a repository or platform design.

The first useful result identifies the bounded tasks and any gaps that affect their use: the named users and actions, material or aids, receiving Work or decisions where applicable, criteria, evidence status, and required relations or conditions. Include time qualifications and stops when they change the task or its admissible result. Use task rows when they help comparison or later reliance; an ordinary answer can be sufficient. Keep distinct task and Work identities. A small manual arrangement can be enough; a curated Method Base is added only when its collection and current-edition discipline change a named task.

“Method Base and enactment-support arrangement” is a Plain practice name for the separately identified Method or candidate accounts, descriptions, representations, collections, editions, Systems, relations, assignments, permissions, authority, capabilities, constraints, user Work, and results configured for the named uses. It is not one FPF technical kind and does not make a repository, interface, provider, tool, prompt, or proposed organization a Method, actor, authority, capability, Work occurrence, or selected U.Structure.

Do not use this pattern to decide whether a Method is fit or effective, to perform the receiving domain Work, or to develop user capability. It configures and tests the way Method material is obtained and used for bounded tasks; those neighboring judgments remain separate.

A.15.8.MS:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
bounded task setA finite set of identified tasks for named user Systems and uses, with the criteria and conditions needed to judge their results. Rows may represent that set for comparison or later use.Each task, Work occurrence, and relation keeps its own identity; the set does not become one Work occurrence or a new whole.
configuration candidateOne identified combination of material, Systems, relations, conditions, and stops proposed for some or all tasks in the bounded task set.A candidate can be sufficient, insufficient, untested, failed, or non-dominated for the stated use without becoming a selected A.22 structure.
Method BaseA Plain maintained boundary for a project-level entry collection together with its separately identified edition account, publication occurrence, and retrieval use.It is not one technical kind. A folder, catalogue, repository, or publication alone does not establish collection membership, currentness, or usability.
enactment-support arrangementPlain name for the identified material, Systems, conditions, and relations chosen to help named users carry out specified Method-related tasks.It is not a generic SupportRelation, one product-shaped object, or an automatically selected structure.
named-user task WorkIndependently admitted dated Work in which a user System performs the retrieval, comparison, tailoring, tool, automation, feedback, or other named task.This is an ordinary descriptive phrase, not another U.Work subtype. A click trace, access grant, planned task, or tool output alone does not establish the Work or its result.
direct System-use relationA domain relation whose Work and System participants, predicate, extent, and use are explicit.It creates no entitlement, capability, assignment, permission, authority, or task success unless those predicates independently obtain.
proposed organizationA recoverable proposal for constituents, relations, constraints, and use frame.A selected U.Structure requires the four identity discriminators under A.22 for the named use. A dated selection-Work claim is separate.
task resultAn observation-bounded result for one performed user task.It does not prove Method fit, effectiveness, transfer, or general holder capability.

A.15.8.MS:1 - Problem Frame

Method descriptions and representations do not reach practice by their existence alone. A user may find an obsolete edition, miss candidate status, choose the wrong branch, expose confidential material to a provider, or accept a tool suggestion beyond their authority. The material can be correct while the surrounding user task fails.

The practical question is therefore: which named users need which Method-related tasks, under what conditions, which criteria and stops are mandatory for the bounded use, and what smallest supported change would cover them or expose an unresolved choice? Repositories, search, prompts, automation, training, provider access, permissions, and feedback matter only through their contribution to those tasks and their own governed relations.

A.15.8.MS:2 - Problem

One failure treats a Method Base as a folder and declares success when files are uploaded. Another builds a platform before observing a user task. A third lets tool integration stand in for access, assignment, capability, permission, authority, or performed Work. A fourth groups all components under a convenient label and calls the proposal a selected structure.

These shortcuts hide which task or condition needs attention. Users cannot tell whether the wrong edition, missing relation, denied access, unsuitable representation, absent assignment, missing permission, authority boundary, or capability gap defeated a task criterion, or whether the task is untested or information needed to judge it is missing. Repairs then grow around the platform rather than around the task and its conditions.

A.15.8.MS:3 - Forces

ForceTension
User-task valueA small configuration may solve the problem, while platform ambitions encourage premature breadth.
Current materialUsers need trustworthy status and editions, while publication and collection membership do not establish currentness by themselves.
Tool assistanceSearch, PLM, CI, prompts, and automation can reduce burden, while their presence alone establishes no authority.
Organizational precisionRelations and constraints may need an A.22 structure, while a proposal must remain useful before selection facts exist.
User and provider boundariesHuman and non-human user Systems and provider Systems can contribute differently, while vague “support” wording can merge performance, service, capability, permission, authority, and result.
TestingObserved user performance is needed to test the arrangement, while a successful bounded task proves neither general capability nor Method effectiveness.

A.15.8.MS:4 - Solution

A.15.8 configures and tests continuation of one actual Work or present WorkPlan. Here the design question is how performers obtain and apply methodological material across the named tasks; it can return a small arrangement or a justified shared Method Base. Pass an actual interruption or support-loss question to A.15.8 without repeating its recovery Method.

Build a bounded set of named-user task criteria and assess the available configuration. For a small reversible task, a configuration with acceptable burden that meets every mandatory criterion and respects every stop can be the sufficient result.

Use matching task observations or run the needed task probe. Open comparison when a live choice could change that result; compare alternatives against the same task set and repair the first defeated material, relation, condition, or task.

Return several candidates, a stated split boundary, or a missing priority or test when that choice remains unresolved.

Use a cheap ordinary task-and-gap account for a small reversible case. When an unresolved Work or WorkPlan configuration or recovery question can change the needed result, use the applicable A.15.8 branch, reusing matching results or running its needed probe. When several criteria, missing evidence, or incomparability make the configuration choice non-trivial, consume current A.19.CPM comparison results and A.19.SelectorMechanism selected-set semantics rather than forcing one route. A.15.8.MS specializes these patterns for Method material through two content branches.

In the direct branch, take the C.37 direct exit when one owning result already supplies the complete one-result/one-use selection and limits. When the A.15.8.MS task row owns that use, keep the same logical basis: receiver/action, subject result, claim, applicable reliance, receiving task result, exposure and loss, disposition and return.

Retain it in that row only when later use needs it; a sufficient immediate answer needs no new C.37 record or C.37.MP profile.

In the profile branch, consume one complete C.37.MP profile when complementary governed representations must be allocated to unlike named Method-related actions.

That profile contains one complete C.37 claim group per action and a separate Method-specific result showing the shared source, correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections.

Both branches preserve Method and candidate status, the A.3.2.DE source account, Method Base collection and edition facts, retrieval and tailoring particulars, provider and AI boundaries, and the named-use task content and return conditions they require. Neither a C.37 row nor the C.37.MP cross-use result selects the support configuration.

If the task set, a required comparison basis, or the task evidence needed to judge adequacy cannot be recovered, return missing-task-set, missing-configuration-basis, or missing-task-test. If retained candidates require an absent priority or decision, return unresolved-configuration-choice[...]; do not improvise a platform or call a local minimum the arrangement.

A.15.8.MS:4.1 - Pattern-Use Unfolding

  1. Construct the bounded task set. For each named user System and use, identify the task and the Method, candidate account, description, representation, aid, or other support result to be retrieved or used. Identify the receiving Work or decision and use relation when the task depends on them.

    Mark each criterion mandatory or optional for this configuration decision, state what would count as pass or failure, and retain any time qualification or stop that changes the result.

    A task need not already be a performed Work. A user System may be human, automated, biological, organizational, computational, or mixed.

  2. Select only the needed Method content and branch by use. Identify the admitted Method or status-preserved candidate account and its current A.3.2.DE MethodDescription or candidate-account edition.

    Direct branch: use the owning complete one-result/one-use answer and its material limits. When the A.15.8.MS task row owns the use, retain the applicable complete C.37 basis there if later use needs reconstruction; otherwise finish the sufficient immediate answer. Do not create a C.37.MP row or duplicate standalone account, or report their absence as a gap.

    Profile branch: when complementary governed representations serve unlike named actions, consume one complete C.37.MP profile. Require one complete C.37-bearing row for every action, then require the separate cross-use result that returns all rows to the same Method source and records correspondences, conflicting omissions, edition relations, keep-separate decisions, and changes that reopen several rows. If the source account, a subject result, reliance or receiving layer, one action row, or the cross-use result is missing, stale, or for another action set, return that gap instead of importing colocated artifacts as a profile.

  3. Identify the participating Systems and required relations. Identify the participating Systems independently, including the users and providers and any repositories, tools or automation that qualify under A.1. Use A.15.6 when project wording leaves the Work, intended-work content or performing organization unclear. Establish the relations required by the named tasks and configuration, such as access, provision, assignment, permission, authority, capability, publication, or direct System use. Keep these predicates distinct; return a missing required relation rather than inferring it from configuration.

  4. Assess the available route and compare for a live choice. For a small reversible task, keep an available configuration when the task evidence supports every mandatory criterion, no stop is violated, and its burden is acceptable for this use. This sufficient result needs neither a second route nor a proof that no smaller route exists.

    Open comparison when a failed criterion, material burden, changed task, or plausible alternative could change the configuration decision enough to justify the comparison’s cost.

    For every candidate considered, map every mandatory and optional task criterion, stop, burden, risk, and required relation. Include cross-task effects such as shared currentness, duplicated maintenance, conflicting confidentiality, latency, provider exposure, or incompatible authority. A per-task minimum does not automatically make their union a smallest shared configuration.

  5. Keep evidence status distinct. For each candidate and criterion assessed, distinguish observed pass, observed failure, untested, insufficient because a declared feature or relation is absent, and unknown because information is missing. These phrases are task-account content, not new FPF kinds. Do not convert untested into insufficient, or a pass by one route into failure by another.

  6. Resolve the live choice without forcing a winner. When step 4 already establishes an adequate route for the bounded task, retain that result without claiming that it is the smallest or best route.

    When comparison is needed, a small reversible case may use an ordinary comparison row if yes/no coverage and burden make the order clear. When comparison is multi-criteria, partial, evidence-gated, or otherwise non-trivial, use A.19.CPM and, when selection is required, A.19.SelectorMechanism; preserve incomparability, degrade, abstain, and a selected set.

    Claim one smallest sufficient route only when it covers every mandatory criterion, violates no stop, and the declared comparison and selection basis supports a singleton. If that comparative claim remains unsupported, retain the alternatives and missing priority or evidence, or split the arrangement by a stated task, user, confidentiality, authority, or maintenance boundary.

  7. Configure only a justified test route or retained set. Configure the functions and conditions needed by the declared tasks: retrieval and selection aids, status and provenance cues, tailoring rules, tool or automation behavior, provider and decision boundaries, feedback receiving use, and stops as applicable. Choosing a candidate for bounded testing is not an A.22 structure selection and does not erase other retained candidates.

  8. Add a curated Method Base only when needed. Identify the project or namespace, collection purpose, current entry-disposition rule, admitted entry kinds, return conditions, edition policy, and continuity. Institute membership only through the identified granted-permission occurrence, admitted Work, operation application, result binding, and belongs-to predicate required by the local declaration. A label, folder, record, result token, or publication occurrence creates no membership.

  9. Select an A.22 structure only when organization changes the action. Establish its four identity discriminators for the named use: independently identified constituents, the selected obtaining relation occurrences, constraints as applied, and the selection-use frame. Apply A.22’s tests to an unresolved required value and return its qualified result or gap; retain the proposal where that basis does not support a selected-structure claim.

    Only if dated selection Work is asserted, identify the selecting System through A.13, independently admit that Work through A.15.1 with its Method enactment, and establish any claimed direct participation or operation binding. F.6 applies afterward when assignment-bound attribution is needed.

  10. Keep editions and reliance accounts separate. When a curated Method Base is used, maintain its C.2.1 edition account. Add a named-use episteme when a receiving decision needs that separate focus and its claims about the Systems, Work, capabilities or relations relied on. Use C.13 only when a materialized construction account changes the receiving use. Publication and actual access remain separate results.

  11. Use matching observations and run needed task probes. Use existing observations when they cover the current criteria and relevant conditions. Cover every materially different mandatory task family, stating when one observation covers several. For each live weakness that can change the configuration decision, use observations under a discriminating condition or probe that condition. Run a new probe only for a remaining decision-relevant gap; choose its pass and failure criteria and conditions before performance.

    For a simple case, observing the user performing the task can be enough. Identify a dated task Work only when the receiving claim needs that occurrence; then supply A.13 and independent A.15.1 admission, with F.6 only for needed assignment-bound attribution.

    For an unresolved configuration or recovery question under interruption, handoff, changed performer, stale state, or support loss, apply one A.15.8 actual-Work or present-WorkPlan branch at a time, reusing matching evidence or running its least burdensome representative probe that can change the decision. Admit a distinct probe Work when the account claims that occurrence. Do not call convenience statistically representative or merge several Work foci into one.

  12. Repair, recompare, and rerun only the affected position. Change the material, System, relation, constraint, access condition, assignment, permission, authority, capability input, edition fact, provider boundary, feedback path, or user step that defeated a criterion. Preserve unaffected collection, proposal, candidate, and task facts. Rerun the same criterion. If the bounded task set, candidate universe, criteria, scope, evidence status, or window changes, make a new comparison or selection use rather than reusing the prior minimum.

  13. Return the bounded result and any needed continuation. Report the applicable per-task evidence status, supported configuration, retained candidate set, split boundary, failed task, changed position, rerun result, or named missing premise. When a receiving use needs a continuation, state what the result supports—for example, a representative Method trial, a description or representation correction, a collection or user-task repair, or later capability development. Reopen only the affected task, configuration comparison, or result.

A.15.8.MS:4.2 - Record the Result

Use the following positions when they are needed to compare configurations or retain the result for a receiving use. An ordinary answer is sufficient when its task coverage, grounds and limits are recoverable. Include the content of each applicable position; do not create empty fields for absent questions.

Result positionContent when the position applies
bounded task setNamed users and tasks, material or aids, mandatory or optional criteria and the observations needed to judge them. Identify receiving Work or decisions, use relations, time qualifications and stops where the tasks depend on them.
Method materialAdmitted Method or candidate status and current MethodDescription or candidate-account edition. Direct branch: one complete one-result/one-use answer, or one A.15.8.MS task row embedding the applicable C.37 group once, with receiver/action, subject result, claim, applicable evidence/reliance layers, receiving result, exposure and loss, disposition, status boundary, provenance, currentness, and return. Profile branch: one complete C.37.MP profile containing those complete action rows plus a separate result showing their shared source, correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections. A missing C.37.MP result is a gap only when the profile branch is required.
participating Systems and relationsIndependently identified participating Systems and the relations required by the named tasks or configuration, with each obtaining, failed or unresolved predicate qualified by its own basis.
available route and live alternativesThe available configuration and any alternatives considered, with coverage of the same task rows, stops, burdens, risks, cross-task effects, and required relations. A sufficient direct result does not require inventing another candidate.
task evidencePer candidate and criterion assessed: observed pass, observed failure, untested, insufficient by a declared missing feature or relation, or unknown from missing information; the source and time qualifications needed to interpret the observations.
adequacy or comparison resultFor a sufficient available configuration, the supported task coverage, acceptable burden and stops. For a live comparison, the ordinary comparison or cited A.19 basis and its retained candidates, singleton justification, unresolved priority or evidence, abstention, or stated split boundary.
configured routeThe needed retrieval, comparison, tailoring, tool or automation, provider, feedback, and decision functions or conditions chosen for testing or supported for the bounded task set.
optional collectionCollection identity and purpose, entry rule, identified membership occurrences, edition, publication, and any construction account, each separately identified.
optional structureThe four A.22 identity discriminators and the judgement they support for the named use, or a proposal with any required unresolved value qualified under A.22. Add the selection-performance basis only for a claimed dated selection Work.
observations and needed testsCoverage of the materially different mandatory tasks and decision-changing conditions, using matching existing observations or needed new probes. A new probe has pass and failure criteria and conditions selected before performance; earlier observations are assessed against the current criteria at their actual coverage. Use an A.15.8 actual-Work or WorkPlan branch when its configuration or recovery question remains.
observed performanceThe user action, direct System interaction, observation, task result, evidence status and gap. Each claimed dated Work has its own A.13 and independent A.15.1 basis; add F.6 only for needed assignment-bound attribution.
repair and rerunFailed criterion, smallest changed position, preserved facts, rerun result, and any new comparison required by a changed task set or basis.
returnThe supported configuration, retained candidates, split boundary, bounded task result, defect or missing priority/test, with material limits and any next use or reconsideration condition needed by the receiver.

A.15.8.MS:4.3 - What Changes in Practice

Teams stop measuring progress by uploaded files, platform features, or one locally successful task. They can show which named uses a configuration covers, which are untested or incompatible, why one route is supported or several remain, and which edition, relation, condition, permission, authority, capability input, or Work result must change.

The same discipline makes automation safer. A user System or provider may be human or non-human and may retrieve, compare, or propose; performed Work, consumed output, permission, authority, capability, evidence status, and result remain visible and separately testable.

A.15.8.MS:5 - Worked Build and Test Replays

A.15.8.MS:5.1 - Minimal One-Task Manual Replay

This constructed replay shows the cheap branch. The named Method and MethodDescription editions are admitted. CalibrationEngineer-5 is an independently identified System meeting the local MethodMaterialRetrieverRole criterion by controlling material selection. The declared CalibrationRetrievalAssignment species assigns that kind when service designation for family-B retrieval and access to its material obtain. Those stipulated facts establish RA-CalEngineer5-Retrieve-B throughout both retrieval intervals.

The two retrieval Works occur within the admitted containing System CalibrationPreparationService-1 on 27 August 2026: W-ME10-Retrieve-Cal-B-0 from 08:00 to 08:02 UTC and W-ME10-Retrieve-Cal-B-1 from 08:05 to 08:07 UTC. Their performance histories independently establish enactment of the admitted MethodMaterialRetrievalMethod-1; no assignment-bound attribution is needed for this comparison.

CalibrationEngineer-5 must retrieve the current description of admitted Method M-Calibrate-Sensor-B for planned calibration Work. The pass criterion is: return MD-Calibrate-Sensor-B-v4, its current status, applicability to sensor family B, and the stop for an unknown serial class. The failure criterion is return of another edition or omission of status, applicability, or stop.

This is one receiver and one action. Candidate REP-Cal-B-Retrieval-1 is a C.2.1 episteme whose claim content is expressed in the maintained index row. Its use claim is that v4 is the current family-B description and carries the unknown-serial stop for this retrieval. It exposes currentness, applicability, the stop, and publication link; it withholds a stable audit digest and makes no capability, permission, authority, Work, or calibration-result claim.

The A.15.8.MS task row is the owning domain result for this use and carries the receiving task criterion, observation, and return. That one embedded realization supplies the complete one-result/one-use selection boundary, so the C.37 direct exit applies: no C.37.MP profile row and no duplicate standalone C.37 account are created.

A later decision that relies on the retrieved content needs the grounds and qualifications required by its claim. Add the A.10 path and disposition when that source-to-use account must remain replayable.

The initial shared-folder route contains v3 and v4 but exposes neither currentness nor applicability. In W-ME10-Retrieve-Cal-B-0, the user retrieves v3; the task returns task-fail[wrong-edition] without changing either edition or admitting a capability claim.

Candidate configurationCriterion coverage and burdenDisposition
Rename v4 to “FINAL” and leave both files in the folderCheap, but the label supplies no governed currentness relation, applicability, or stop and obscures why v3 remains.Insufficient for the declared criterion.
Add one manually maintained index row naming the Method, v4, currentness basis, family-B applicability, unknown-serial stop, and publication linkCovers every current criterion with one new episteme and no new platform. The folder remains a carrier; the index does not become the Method, publication occurrence, Work, or authority.Retain as the only currently supported sufficient configuration for this one-task set; this does not exclude the untested portal.
Build a search portal with automated recommendationsCould add later functions, but no present criterion requires them and their provider, access, suggestion-use, and authority relations are ungrounded.Untested and larger than this one-task need; do not claim failure.

The repair adds only the retained index row and its maintained currentness cue. In W-ME10-Retrieve-Cal-B-1, the same user retrieves v4, sees family-B applicability, and stops on an unknown serial class. The receiving task result is task-pass for this retrieval action, so the use-bounded row disposition is select inside the stated v4/family-B window. Return if the source edition, currentness cue, applicability, unknown-serial stop, or task observation changes.

For the bounded set containing only this task, the currently supported set is the singleton containing the index row: the rename route is insufficient by its declared missing features, while the portal remains untested and is not ruled out as logically insufficient. This establishes neither unique sufficiency nor multi-task minimality, Method fit, general user capability, a selected A.22 structure, or worth in another project.

If the maintained index and matching observed retrieval result are already available when this same bounded task is raised, check that the edition, currentness basis, task conditions and acceptable burden still apply, then finish with the adequate route. No portal comparison or new minimality claim is needed. A new audit task, changed stop or defeated currentness cue reopens the affected adequacy question; the next replay shows why.

A.15.8.MS:5.1.1 - Configure a Tailoring Aid and Repair Its Failed Check

Extend the constructed calibration setting with a different task: prepare a plan for one named sensor using the permitted choices in the current MethodDescription. This example concerns support for that preparation; it does not report a real calibration or establish its effectiveness.

Assume the following domain facts are supplied with the admitted v4 description: the planner may select an approved fixture whose working interval contains the sensor’s required interval, but must retain the prescribed test points, acceptance rule, and unknown-serial stop. The current fixture register already establishes approval and intervals; matching numbers alone would not establish approval. The user’s assignment, permission and required preparation are also assumed independently established for this bounded planning task.

The input is sensor B-17 with a required interval of 0–10 V, description v4, and two current approved fixture entries: F10 covers 0–10 V and F5 covers 0–5 V. The output criterion is a plan naming B-17, the v4 edition and a covering fixture, with the unchanged test points, acceptance rule and serial-class stop. Unknown sensor class, absent approval, incompatible units, or an interval not covered by any available fixture must return the missing premise before a plan is released for use. This does not authorize actual calibration.

Configure one local planning worksheet to consume those inputs. Its tailoring rule is: establish sensor class and the register’s currentness; check the supplied approval relation and compatible units; require fixture lower bound <= required lower bound and required upper bound <= fixture upper bound; copy the allowed selection into the plan while retaining v4’s fixed operations and stops.

Selecting a parameter within these declared options creates a plan for this case; it does not by itself alter reusable Method semantics. If the task needs a new acceptance rule, return to Method design and A.3.1.MV instead of silently editing the template.

In the first constructed planning attempt, the worksheet lists both fixtures but checks approval only. The user chooses F5 and obtains a plan labelled ready. The task fails: 5 V does not cover the required upper bound of 10 V. The register and v4 rule are correct, so the repair belongs to the worksheet’s omitted interval check. Add that check before export.

In a separate repeat of the same task, F5 is rejected with the uncovered 5–10 V interval, F10 is accepted, and the resulting plan retains the prescribed operations and stops. A further changed-input probe with an unknown serial class stops before fixture selection.

These are stipulated observations in the constructed replay. A receiving claim that distinguishes dated Work occurrences must supply each occurrence’s A.13 and A.15.1 basis.

The receiving result is bounded: the repaired worksheet supports this permitted plan adaptation under the named edition, register and task conditions. The earlier retrieval result alone supplied none of this evidence. A changed fixture register reopens its coverage and currentness premises; a changed tailoring rule reopens the affected plan construction; a failed repeat returns to the defeated worksheet check. Neither the successful preparation nor the worksheet’s ready label establishes release authority, general user capability, Method fit, or the result of performing the calibration.

A.15.8.MS:5.2 - Two-Task Trade-off with Two Retained Candidates

Extend the constructed case with a second mandatory action. CalibrationEngineer-5 must retrieve the current description for planned family-B calibration Work. Computational user System AuditService-2 must use the v4 edition in ReleaseAudit-7 under a stable digest and audit currentness record.

These are different receiver/action pairs, so they require different use-bounded claim groups even when one maintained source could realize both. No AuditService-2 task Work has yet occurred.

The Method-specific problem is now cross-use allocation of complementary governed representation results. The C.37.MP profile branch applies. Each row below embeds the applicable complete C.37 group and preserves admitted Method M-Calibrate-Sensor-B and current A.3.2.DE result MD-Calibrate-Sensor-B-v4 as its source. The rows select for their own actions; they do not yet constitute the C.37.MP cross-use result or select a support configuration.

C.37.MP row and actionResult, claim, and relianceExposure and lossReceiving result, disposition, and return
MRP-Cal-B-Retrieve-1: CalibrationEngineer-5 retrieves material for planned family-B calibration Work. Qualification window: the currentness cue is checked at retrieval and remains usable only for that v4 family-B use through the planned Work.REP-Cal-B-Retrieval-1 is the governed C.2.1 index episteme. Claim: v4 is current for family B and carries the unknown-serial stop and publication link. A.2.4 classifies the intended status-evidence use. A.10 path P-Cal-B-Retrieve-v4 carries that currentness/applicability premise with RelianceDisposition=pass inside the stated window.Exposes current edition, family-B applicability, stop, and link; omits the stable audit digest and audit currentness record, which this action does not require.task-pass from W-ME10-Retrieve-Cal-B-1; select for this retrieval action. Return to A.3.2.DE for changed source claims, C.2.1 or A.10 for a failed result, or this row when the use, window, disposition, or observation changes. Stop if the edition or cue changes, applicability no longer covers family B, or the serial class is unknown.
MRP-Cal-B-Audit-1: AuditService-2 uses the edition in ReleaseAudit-7. Qualification window: at audit start the currentness record must identify v4 and the stable digest must identify the v4 bytes used by that audit run.REP-Cal-B-Audit-1 is a governed C.2.1 audit-register episteme tied to a separately identified E.24.PUB publication result. Claim: the named digest and record bind the audit use to the current v4 edition. A.2.4 classifies the intended audit-evidence use. A.10 path P-Cal-B-Audit-v4 returns RelianceDisposition=abstain until the digest/currentness pair is checked inside the audit window; missing, stale, out-of-window, or mismatched values stop before reliance.Exposes edition identity, stable digest, and audit currentness record; omits the human applicability explanation and unknown-serial stop, which this action does not consume. Publication does not supply reliance or the task result.missing-task-test[AuditService-2]; no audit task Work exists and no task-pass is claimed. The row is unresolved, not failed. Return to A.3.2.DE for changed source claims, C.2.1, E.24.PUB, or A.10 for a failed result, or this row when its use, window, stop, task observation, or disposition changes.

C.37.MP now returns cross-use profile result MRP-Cal-B-Retrieve-Audit-1 rather than treating row colocation as composition:

Profile positionCross-use result
shared Method sourceBoth rows return to admitted Method M-Calibrate-Sensor-B and current MethodDescription MD-Calibrate-Sensor-B-v4.
cross-use correspondenceThe retrieval currentness cue and the audit digest/currentness pair must designate the same v4 edition. Matching the label v4 is insufficient; a changed edition reopens both rows and this correspondence.
conflicting omissionsRetrieval needs family-B applicability and the unknown-serial stop but omits the stable digest. Audit needs the digest and audit-currentness record but omits the human applicability explanation and serial-class branch. Combining the presentations does not erase either omission or prove consistency.
edition relationsThe retrieval row is qualified for the planned family-B Work window; the audit row is qualified only for the named ReleaseAudit-7 run after its digest/currentness check. A serial-class change can reopen retrieval alone; a digest mismatch can reopen audit alone.
keep-separate decisionREP-Cal-B-Retrieval-1, REP-Cal-B-Audit-1, their C.37 dispositions, and their receiving task results remain separate. The profile creates no super-representation, common task pass, publication, or support arrangement.
profile returnRetain retrieval as select and audit as unresolved; return missing-task-test[AuditService-2] and the unchecked digest/currentness relation. Reopen both rows only when their shared source identity or correspondence changes.

The configurations below compare how those two governed results and the cross-use relation could be supplied and maintained. C.37 does not choose among them, and the C.37.MP profile does not rank them; A.15.8.MS retains that configuration decision.

Candidate configurationEngineer retrieval rowAudit-service rowCross-task burden and disposition
Manual index row onlyObserved pass in W-ME10-Retrieve-Cal-B-1.Insufficient: the editable row supplies no stable publication digest or audit currentness record.Exclude for the two-task mandatory set.
One signed read-only register supplies separate retrieval and audit presentationsUntested for the engineer; its declared retrieval presentation can expose applicability and the stop.Untested for AuditService-2; its declared audit presentation can expose the digest and currentness record.One maintained source for two governed results, but the case lacks approval-latency evidence. Retain.
Manual retrieval index plus a signed audit logThe existing retrieval pass remains relevant to the index route.Untested for AuditService-2; its declared design can expose the audit record.Lower expected retrieval delay but duplicated currentness maintenance and an untested consistency relation. Retain.

The last two candidates cover the declared features differently, but the case supplies neither audit-task evidence nor a priority between approval latency and duplicated currentness maintenance. The audit profile row therefore remains unresolved, the cross-use profile returns its unchecked correspondence and missing-task-test[AuditService-2], and reliance stops; retain both candidates with unresolved-configuration-choice[approval-latency-vs-duplicate-currentness-maintenance].

If a receiving decision authorizes a split, name the user/task boundary, currentness owners, and consistency relation; do not call the union globally minimal.

A.15.8.MS:5.3 - EC-417 B2 Bounded Task Set and Evidence

The EC-417 B2 material exists, but TraceReviewer-17, SafetyReviewer-17, and ReleaseDecider-17 need support for three distinct tasks. The intended task set has the following criteria; its tailoring operation lacks the definition needed for reuse:

Task rowMandatory pass and stop observations
retrieval by TraceReviewer-17Recover MBE-EC417-B2-1, candidate status, prompt episteme ATP-2, confidentiality boundary, and D0 stop.
tailoring by SafetyReviewer-17Use the non-confidential fixture, preserve signed-before-closure, reject a stale edition, and stop on missing permission or authority.
branch selection by ReleaseDecider-17Distinguish A, B2, and R and stop when assignment, permission, authority, confidentiality, or reversibility is absent.

The receiving relations remain: TraceReviewer-17 retrieves the edition and prompt episteme for trace-review preparation; SafetyReviewer-17 uses the tailoring aid in named tailoring Work; ReleaseDecider-17 uses the selection aid in named branch-selection Work. None is release Work or the release decision.

Candidate configurationEvidence against the same three rowsDisposition for this case
Published files and manual lookup onlyThe case supplies no performed task evidence for current status, ATP-2, D0, stale-edition rejection, signed-before-closure, or A/B2/R stops through this route.Untested. Do not call it failed or insufficient from absent task evidence alone.
Bounded PLM retrieval and selection aids plus the non-confidential CI tailoring fixtureRetrieval and branch-selection pass their declared checks through the identified PLM and CI Systems. Tailoring observations cover the fixture, signed-before-closure and stale-edition rejection, but not the permission/authority stop.Supported for the observed actions; the missing tailoring definition and missing-task-test[tailoring-permission-authority-stop] prevent a pass for the complete three-task set. No claim of global minimality or parity superiority.
Add an AI-provider route and feedback pathThe case supplies no AI-provider interaction, used suggestion, review of such a suggestion, feedback Work, or feedback receiving use. No mandatory row currently requires this branch.Untested and outside the supported result. Its absence is a gap only for a named task or additional claim that requires it.

The configured PLM/CI route includes the Method Base edition and status cues, PLM retrieval and branch-selection aids, the CI fixture and stale-edition rejection, ATP-2, and the confidentiality, signed-evidence, assignment, permission, authority, reversibility, and D0 stops.

The manual and AI routes lack parity evidence, so this table does not select the globally smallest arrangement. It identifies the only configuration with performed observations across all three tasks; the missing tailoring definition and tailoring-stop test prevent complete task-set support. It is not an A.22 selected structure.

A.15.8.MS:5.3.1 - Missing Tailoring Definition

The case names tailoring aid TAIL-EC417-B2-1 and Work W-MESUP-EC417-Tailor-1, but does not identify the object and edition to adapt, the alteration or selection performed, or the resulting tailored object. The fixture and guard observations below do not recover those missing values. The method engineer configuring this support task must recover them before offering it as a repeatable tailoring instruction or claiming tailoring coverage.

Until then, return missing-task-set[tailoring-input-action-result] and retain only the described CI-use, signed-before-closure and stale-edition observations. This missing definition is separate from the untested permission/authority stop; neither gap turns the admitted Work into a performed failure.

A.15.8.MS:5.4 - Three Performed Tasks and Their Bounded Reach

The supplied EC-417 account takes the three Work occurrences below as admitted premises. Their admission is not established by these task observations. An actual use must recover each performer through A.13 and each independent A.15.1 basis, including Method, time and containing-System relation; use F.6 only if the account needs attribution through the same obtaining assignment. Without those grounds, retain the reported observations without asserting the Work identity.

User WorkSystem interaction and observed resultResult boundary
W-MESUP-EC417-Retrieve-1 by TraceReviewer-17The user retrieves MBE-EC417-B2-1 through SYS-EC417-PLM-1 and recovers candidate status, ATP-2, the confidentiality boundary, and the D0 stop. The local SupportSystemUsedInWork@EC417 occurrence obtains for that Work-System pair and interaction interval.The result establishes this retrieval task only; it creates no general access entitlement, capability, or authority.
W-MESUP-EC417-Tailor-1 by SafetyReviewer-17The user applies the tailoring aid with a non-confidential SYS-EC417-CI-1 fixture, recovers signed-before-closure, and rejects the stale edition. Its separate direct System-use occurrence obtains.The result establishes these observations only; the tailoring operation remains undefined, and stopping on missing permission or authority remains untested. It neither performs release Work nor approves closure.
W-MESUP-EC417-Select-1 by ReleaseDecider-17The user applies the selection aid through SYS-EC417-PLM-1 to distinguish pre-entry A, bounded B2, and post-entry R and stops B2 when a named assignment, permission, authority, confidentiality, or reversibility condition is absent. Its separate direct System-use occurrence obtains.The result establishes this bounded selection task only; the tool does not make the release decision or acquire authority.

RES-MESUP-EC417-B2-1 returns task-pass for retrieval and branch selection. It retains the observed tailoring fixture, signed-before-closure and stale-edition results, but returns missing-task-set[tailoring-input-action-result] and the separate missing-task-test[tailoring-permission-authority-stop] for the full tailoring task.

The other user’s branch-selection stop does not fill that gap. No AI-provider interaction, used AI suggestion, review of such a suggestion, feedback SpeechAct, or feedback receiving use is part of that pass. Retrieving ATP-2 is not provider use.

No repair and rerun occurrence is asserted for EC-417: no performed task is reported as failed, and an untested tailoring stop is not a performed failure. If a later task fails, apply step 12 and preserve the new observation and rerun separately from these histories; identify dated Work only when needed by the receiving claim. The minimal one-task replay supplies the filled failure-repair-rerun branch; the two-task extension supplies the unresolved-trade-off branch.

A.15.8.MS:5.5 - Proposed Organization, Not a Selected Structure

PSO-EC417-B2-Use-1 is a case-local proposal designator. Its four candidate A.22 groups remain disjoint:

  1. the identified collection, entries, edition, aids, prompt episteme, Systems, and three Work occurrences;
  2. two instituted entry-membership occurrences and the three direct PLM and CI System-use occurrences;
  3. current-edition, status, confidentiality, signed-before-closure, assignment, permission, authority, reversibility, and D0 constraints; and
  4. the use frame for retrieval, comparison, tailoring, and bounded PLM and CI use for WP-EC417-B2-Trial-1.

This support account retains PSO-EC417-B2-Use-1 as a proposal; it does not assert a selected U.Structure. If a named receiving use requires that stronger claim, establish the four A.22 values for that use from the case facts. ESA-EC417-B2-1 returns missing-selection-basis only when a value or judgement required for that use remains unresolved.

A separate claim of dated selection Work would need its selecting System, enacted Method, independently admitted Work and any claimed participation or operation binding. The three task observations and the separate missing tailoring test retain their own grounds.

A.15.8.MS:5.6 - Collection and Edition Remain Subordinate Results

MBC-EC417-B2-1 identifies the project collection and its entry-disposition rule. Two admitted curator Work occurrences, their permissions and operation applications, positive result bindings, and identified MethodBaseEntryBelongsTo@Project predicates establish membership for the candidate-account and WorkPlan epistemes. The collection, membership episodes, assertion or evidence accounts, optional construction account, edition, publication occurrence, and named-use reliance episteme remain separate results.

Those facts make the named material eligible for the three user tasks; they do not show that the tasks succeeded. Conversely, the bounded task results do not prove general capability, select the proposed structure, admit C-EC-Release-v2 as a Method, perform release Work, or establish Method fit or effectiveness.

A.15.8.MS:6 - Bias-Annotation

Recurring biasLikely driftRepair
task-set omission biasOne visible task defines the arrangement while another mandatory use remains invisible.Identify every named user and task; when comparing configurations, assess every candidate against that same bounded set. Use rows where they help keep the uses distinct.
forced-winner biasA local minimum or one observed pass becomes the single arrangement despite incomparability.Preserve retained candidates, missing priorities, abstention, or a stated split boundary.
evidence-status biasNo test evidence is reported as failure or insufficiency.Separate observed pass, observed failure, untested, feature-level insufficiency, and missing information.
repository biasUploading files is reported as a usable Method Base.Test the declared task rows and retain the collection predicates separately.
platform biasFeature breadth replaces the failed task set.Include an element only for a named criterion, stop, cross-task dependency, or directly supported relation.
tool-authority biasA recommendation or branch display becomes a decision or permission.Keep tool interaction, user Work, permission, authority, and result separate.
structure-selection biasA complete proposal table becomes an A.22 selected structure.Establish the four identity discriminators under A.22 for the named use. Add selecting-System, Method, Work and participation or binding grounds only for the corresponding dated-performance claims.
success inflationOne task pass becomes capability or Method-effectiveness evidence.Bound the result to observed Work and return neighboring claims separately.

A.15.8.MS:7 - Conformance Checklist

  • The bounded task set identifies each named user and action, material or aid, mandatory or optional criterion and needed observation; receiving Work or decision, use relation, time qualification and stop are included where they change the task or its admissible result.
  • Human, automated, biological, organizational, computational, and mixed users remain possible; performer, capability, permission, and authority claims use the patterns governing them.
  • In the direct branch, the complete one-result/one-use selection, material loss and receiving result remain usable. A later receiving need gets its complete basis once in the owner; an immediate answer needs no new C.37.MP row, standalone C.37 account or omission record.
  • In the profile branch, every consuming action recovers one complete row with its embedded C.37 claim group, required Method claims, governed result, applicable evidence/reliance layers, receiving result, exposure and loss, status boundary, disposition, and return.
  • The same branch also recovers one C.37.MP cross-use result that names the shared Method source, correspondences, conflicting omissions, edition relations, keep-separate decisions, and changes that reopen several rows. Row colocation is not that result.
  • Neither C.37, an action row, nor the C.37.MP cross-use result is treated as selecting the support configuration, admitting a Method, publishing material, establishing access, capability, authority, Work, or task success.
  • Every configuration compared is assessed against the same task set and applicable stops, burdens, risks, cross-task effects and evidence qualifications.
  • Observed pass, observed failure, untested, feature-level insufficiency, missing information, and an unresolved use-bounded row are not substituted for one another.
  • A sufficient direct route has supported mandatory task coverage, acceptable burden and respected stops; it makes no smallest-or-best claim. A comparative singleton has its declared comparison and selection basis; unresolved comparison preserves candidates, abstention, a split boundary, or a missing priority or test.
  • A simple task uses the cheap branch; configuration or recovery testing reuses A.15.8, and non-trivial comparison or selection reuses A.19 rather than copying their kernels.
  • Project Work, intended-work content and the performing organization remain distinct under A.15.6. Participating Systems and their access, assignment, permission, authority, capability, publication, direct System-use, Work and task-result claims retain their own grounds.
  • A curated collection has a project or namespace, purpose, current rule, identified membership predicates, edition policy, and return conditions.
  • An A.22 selected-structure result has all four identity discriminators for the named use; any unresolved required value retains its A.22-qualified result. A proposal may remain a proposal. A claimed dated selection Work has its separate performance basis.
  • Each positive task result rests on observed performance and the relations used. Any claimed dated Work has its independent A.13 and A.15.1 basis; assignment-bound attribution additionally uses F.6.
  • Provider or AI use, review, feedback, capability, fit, effectiveness, transfer, and authority are claimed only when their own facts obtain.

A.15.8.MS:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The Method Base is the repository.”Identify the collection, membership rule, edition, publication, access, task set, and observed uses separately.
“The profile row chose the support arrangement.”Use the row only for its representation/action claim group; compare and select support configurations in A.15.8.MS.
“C.37 selected the representation, so the task passed.”Keep use-bounded disposition separate from performed Work and the receiving task result.
“The PLM route passed, so manual lookup is insufficient.”Record PLM as observed pass and manual lookup as untested unless a declared missing feature proves insufficiency.
“Choose the smallest arrangement for each task and combine them.”Check shared currentness, maintenance, confidentiality, latency, authority, and provider effects; return a retained set or stated split when the union has no supported order.
“The interface gives users access.”Establish the access relation and relevant permission; an interface is only one System or presentation element.
An AI-use label leaves its contribution to a decision unclear.For a claim that AI contributed to a decision, identify the AI System interaction, contribution used and resulting decision. Identify a provider interaction or review when it occurred or is required, and establish any required permission and authority. A missing required premise limits the dependent claim or use. Identify dated Work only when the claim needs that occurrence.
“All components are listed, so the structure is selected.”Establish all four A.22 discriminators for the named use; keep the proposal where that claim is not supported. Dated selection Work is a separate claim.
“Three users passed, so the team is capable.”Report the three Work-task observations and evaluate capability under A.2.2 only when its holder, Work family, envelope, measures, and window are present.
Feedback availability is confused with its occurrence or use.Establish the usable channel for an availability claim. Identify the feedback and its recipient for an occurrence claim, and its contribution to the receiving result for a use claim. Supply Work or SpeechAct grounds when claiming those kinds.

A.15.8.MS:9 - Consequences

Declared task coverage and observed performance show what users can obtain from the Method material and where the configuration needs repair. Repairs are smaller because the defeated task row, edition, representation-use claim, relation, constraint, permission, authority, capability input, interaction, or Work result is visible. A useful result may be one supported configuration, several retained candidates, a stated split, or a missing priority or test.

The cost is preserving the distinctions and grounds needed by the named uses. Results, collection and edition facts, publication, participants, relations, observations and criteria may share a sufficient account when its C.2.1 focus and claims remain truthful. Separate them when their uses require it; retain durable accounts only for later reliance.

Some sophisticated features remain untested; some choices remain set-valued; and a proposed organization may remain unselected even when all bounded tasks pass.

A.15.8.MS:10 - Rationale

Enactment assistance is relational and work-bound. A repository can hold material; a representation can expose a claim; a tool can return a value; a provider can offer a service; a user System can perform Work; a System can institute granted permission through an admitted SpeechAct under the conditions in A.2.8.PER; an assignment or authority relation can obtain. None substitutes for the others.

FPF supplies the generic one-receiver/one-action representation-selection discipline in C.37, configuration-and-recovery in A.15.8, and comparison and set-valued selection in A.19.CPM and A.19.SelectorMechanism. A.15.8.MS specializes those moves for Method material and adds the bounded task-set bridge across Method or candidate status, A.3.2.DE results, Method Base collection and edition facts, retrieval, tailoring, provider and AI particulars, and their receiving uses.

The direct branch remains cheap: use the complete one-result/one-use answer without a new profile or duplicate account. Retain the full applicable selection basis in its owning task result when a later receiver needs it. A.15.8.MS opens C.37.MP only when unlike actions need the Method-specific cross-use allocation, including source correspondences, conflicting omissions, edition relations and return conditions. Neither C.37 nor the profile selects the support configuration.

A.15.8.MS brings these contributions together for Method-material tasks: identify the tasks that need support, choose the comparison and recovery approach required by those tasks, and return observed gaps to the practice responsible for the failed material, relation or condition. The constructed one-task and two-task replays and the bounded EC-417 case show how to apply this combination; they do not establish general effectiveness.

A.15.8.MS:11 - SoTA-Echoing

SourceAdopted or adapted contributionBoundary and practitioner implication
Daalhuizen and Cash, Method content theory; Gericke, Eckert, and Stacey, Elements of a design methodAdopt user-relevant content, representation, tools, adaptation conditions, and intended-use questions.These inputs help construct task rows; they do not establish task Work, configuration adequacy, or one selected arrangement.
Gericke et al., method ecosystemsAdapt attention to interacting Methods, actors, tools, representations, and organizational conditions.The position paper identifies no universal platform or selected structure. Practitioners keep Systems, relations, task criteria, and evidence status explicit.
Stacey et al., Methods as engineering knowledgeAdopt maintained knowledge, provenance, retrieval, and use as engineering concerns.Knowledge maintenance, publication, and availability do not establish user Work, task coverage, fit, or effectiveness.
Inkermann, AI-supported design-Method useAdopt explicit AI contribution, criteria, provider-to-output traceability, transparency, responsibility, and feedback questions.The framework is exploratory. It supplies no autonomous authority, effectiveness, or general configuration-selection claim; EC-417 keeps provider use and feedback untested.

A.15.8.MS:12 - Relations

  • A.3.2.DE supplies use-bounded MethodDescription or candidate-account content. The direct branch uses the complete one-result/one-use answer and retains its full applicable C.37 basis only for a later receiving need, without a C.37.MP row or duplicate account. The profile branch consumes C.37.MP’s complete action selections and Method-specific cross-use result. A.15.8.MS owns its separate support-configuration comparison.
  • C.37 governs use-bounded representation selection and co-use. It does not select the support configuration, establish Method status, publication or access, capability, authority, Work, task result, or arrangement adequacy.
  • A.15.8 governs generic actual-Work or present-WorkPlan performer-support configuration and recovery probes. A.15.8.MS supplies Method-material-specific users, tasks, supports, criteria, and repair returns.
  • A.19.CPM governs non-trivial comparison results; A.19.SelectorMechanism governs set-valued selection. A.15.8.MS does not turn a configuration pass into a forced winner.
  • A.22 defines selected structures and their discriminators; a retained candidate, proposal label, colocation, or selected test route establishes none of them.
  • A.2.2 defines capability; A.2.8.PER defines granted permission and exercise; A.13, A.15.1, and F.6 define or constrain performer, Work admission, and assignment-bound attribution claims.
  • A.6.1 defines reusable operation declarations, applications, and result bindings; a result designator or record does not make an application occur.
  • C.2.1, C.13, and E.24.PUB define or constrain the separate episteme, collection account, edition and publication, and carrier claims used here.
  • A later representative Method trial consumes only tested task conditions and named gaps; coherence, fit, worth, capability development, and cultural continuation remain neighboring practices.

A.15.8.MS:End

A.15.9 - Use or Request a Bounded Result from Another Practice

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

A.15.9:1 - Problem frame

Plain name. Use the outside-practice result this decision can rely on; obtain a new contribution when it is worth the work.

Use this when. One decision or piece of Work can change because of a legal interpretation, safety limit, tax consequence, privacy condition, calculation, objection, observation, or another result governed by a different practice. The available source or request instead names a department, title, document, meeting, approval, provider, or tool, so the receiver cannot tell what result is needed or how it may be used.

Reader. The person, team, organization, or other deciding System that owns the receiving decision or Work. When acquisition is selected, seek a supplier able to return the needed result from the applicable practice; neither supplier, specialist, profession, nor professional result is a new FPF kind.

First useful result. Give the useful answer the present basis supports, with the limitation that changes its receiving use. A conditional conclusion or an available action can settle a commission that calls for it. If a related action remains possible while the requested fact is unknown, give that distinction to the recipient.

A missing result for a stronger claim does not itself select acquisition. Request the smallest additional contribution only when it is obtainable and worth its whole burden for this question. A simple answer can remain two ordinary sentences without a separate acquisition disposition.

What changes in practice. The receiver checks a result before commissioning more Work, asks for an answer rather than a department or document, and states where supplier judgement ends and the receiving decision begins. A usable existing answer can stop the work before any new request, assignment, meeting, delivery, or acceptance ceremony.

Cheap non-use. Do not open this pattern merely because another practice originally produced a source. If the current result, its limits, and its permitted use are already clear and no cross-practice boundary changes the next action, use the result under the pattern governing it and stop. Use A.10 directly when the only open question is evidence, currentness, or bounded reliance. Use the RESULT-TO-NEXT-MOVE entry when a result already exists and only its next downstream question is open.

Not this pattern when. Use the supplier’s domain Method for the specialist answer itself; A.2.2 for capability; A.13 for agency; A.15.1 for dated Work; A.2.9 for communication; C.11 for a live choice among an existing OptionSet; and C.38 only when the question has changed from one bounded contribution to several complete ways of obtaining the same receiving result.

A.15.9:2 - Problem

A receiver often asks for legal approval, a safety review, an architect sign-off, a tax memo, or an AI check. Those phrases identify a search direction or artifact, not the result that can change the receiving decision. They hide the subject, configuration, interval, assumptions, evidence, qualification, authority boundary, and non-use condition.

The opposite failure is to rebuild an organization around a small question. A reversible exchange acquires a fixed role catalogue, responsibility matrix, approval workflow, supplier account, and mandatory record even though an existing qualified answer could have closed the issue. The administrative apparatus grows while the result remains vague.

The missing move is small: start with the receiver’s decision, inspect what already exists, preserve the useful answer and its limits, and select further acquisition only when its obtainable contribution warrants the work. Preserve the supplier’s Method and authority and use the result inside its supported boundary. The request, planned or actual Work, communication, result, evidence, acceptance, reliance, authority, and receiving decision remain different facts.

A.15.9:3 - Forces

ForceTension
Reuse versus fresh WorkA current qualified result can be cheaper and safer than a new request; a narrower answer can remain useful when a stronger one is unsupported. Acquisition must earn its cost without treating a stale or wrong-configuration answer as adequate.
Small request versus useful boundaryThe receiver needs a short request without omitting the subject, situation, use, and stop that make the answer meaningful.
Supplier judgement versus receiver authorityThe supplier governs its Method and professional conclusion; the receiver owns the decision that consumes it unless a separate authority relation says otherwise.
Informal exchange versus recoverabilityTwo sentences may be enough for a reversible choice; consequential reliance may require exact sources, Work, evidence, authority, dissent, and currentness.
Named specialist versus supported performerA title, department, credential, provider label, or tool name can help find a candidate but does not establish capability, assignment, authority, or performed Work.
Recognition versus assuranceA vague outside-practice dependency is enough to open the pattern; high-consequence use requires stronger direct evidence, assurance, and stop rules.
Shared move versus domain ownershipThe inspect-reuse-or-request boundary transfers across practices, while every domain keeps its own questions, Methods, evidence standards, acceptance, and consequences.

A.15.9:4 - Solution

Begin with one receiving decision or piece of Work and one result that could change its next action. Inspect an available result before commissioning anything new. Return what it supports now, including a stop where required. If an additional contribution is worth obtaining, bound the request, let the supplying practice govern how it answers, then assess and use the return without transferring either side’s authority.

A.15.9:4.1 - Follow the nine-step bounded-result sequence

  1. Name the receiving decision or Work. State who will use the result, what action can change, and the consequence of delay or error. Do not begin with a department, profession, meeting, or document.

  2. Inspect an already-available result first. Identify the result or claim, its subject, conditions, source, date or window, qualification, and intended use. Apply A.10 only to the evidence, currentness, provenance, and bounded reliance needed. Use the result where adequate and retain the limit that matters.

    Check whether the result applies to this claim and configuration. A narrower result can settle the use when the receiving decision only needs that result. If the requested answer could still differ, state what remains unresolved.

  3. Select acquisition before constructing the request. When a missing result or proposed inquiry makes acquisition live, use C.11.DUA to compare an obtainable calculation, interpretation, limit, objection, observation, decision, or other contribution with the present answer, narrower action, alternative, deferral, or stop. Include formulation, qualification, delivery, supplier Work, interpretation and use, delay, displaced work, and downside within the receiving horizon.

    Being able to change the answer is necessary for a useful contribution, but does not alone make obtaining it worthwhile. If acquisition is selected, ask for the smallest result that can supply that contribution; permit a supported result, bounded objection, or blocker as its return.

  4. Bound the subject and use. State the subject, configuration or situation, interval, assumptions, important exclusions, acceptance condition, and non-use boundary at the grain that can change the answer.

  5. Preserve the supplier’s practice and Method. Name the supplying practice and applicable Method, source, or inquiry status when known. The request may state needed inputs and evidence, but it does not replace the supplier’s Method. If no applicable Method or source is known, state the missing basis. Inquiry into that basis is further acquisition subject to step 3; naming the gap creates no assigned Work.

  6. Recover performer and authority only when reliance needs them. A small exchange may not need either. When they matter, establish capability, access, conflict, assignment, permission, authority, responsibility, and commitment under the patterns governing them.

    When the receiving claim identifies a dated supplier Work, recover each performer through A.13, let A.15.1 independently admit the dated Work, and use F.6 afterward only if the receiving use also needs to say under which assignment the Work was performed.

    Failure of that attribution alone preserves independently admitted Work and separately supported results. If the finding also questions an admission or result premise, recheck that premise and its dependents.

  7. Keep request, Work, communication, and result distinct. State the request content separately from the act of requesting or communicating it. Identify a request episteme when the use needs that content separately referable. A WorkPlan, assignment, commitment, communicative Work, dated supplier Work, source or returned result, evidence, delivery, acceptance, and later effect each require their own basis. Sending a file or holding a meeting establishes none of the stronger facts by itself.

  8. Assess and use the result. Check the subject, conditions, provenance, evidence, uncertainty, qualification, dissent, currentness, and authority boundary that matter to this use. Rely within the supported limit, reject the unsupported use, or keep the blocker. Select any repair request or other new contribution through step 3. The supplier does not make the receiving decision merely by supplying the result.

  9. Reopen locally. Name the source, Method, subject configuration, use, capability, authority, conflict, evidence, or later observation whose change can alter the disposition. Reopen only the affected request, result, reliance, or receiving decision.

The sequence is logical, not a compulsory workflow. Step 2 can close a useful narrower answer as well as full reuse. Step 3 opens when acquisition is live, and the later steps only when their qualification, request, return, or reliance question is current. Several independent contributions may proceed concurrently, and one receiver may use one result while another claim remains blocked.

A.15.9:4.2 - Return the first result in ordinary language

For a small reversible use, give the answer and retain only what its recipient needs to interpret it. For example, an administrator may ask for one date already authorized for a contractor submission. Give Thursday if its eligibility is established. For the different question of whether Friday would also qualify, a calendar that excludes contractors leaves Friday unresolved. Obtain the contractor cutoff when resolving that question is required and feasible.

When acquisition has been selected under §4.1, a compact request may read:

For [receiving decision], answer [smallest result question] about [subject and configuration] for [window and use]. State the supported result, a bounded objection, or the blocker; do not decide the receiving question for us.

Do not add a field merely because it appears in a larger case. Add the supplier, Method, performer, Work, evidence, authority, acceptance, or reopen detail only when it changes or supports the receiving use.

A.15.9:4.3 - Persist only what another use must recover

If several contributions, audit, dispute, or consequential reliance require a durable account, use one or more ordinary C.2.1 epistemes. Each account identifies its EntityOfConcern and effective reference scheme, then designates only the request, Work, result, relation, evidence, disposition, and reopen facts used. This pattern adds no professional-contribution kind, universal account schema, profession taxonomy, or approval record.

Keep incompatible focuses separate. An account about the receiving decision is not the supplier Work; an account about a returned result is not the world-side subject it concerns; a file carrying either account is not the result or authority. Use A.10 for source-to-use reliance on evidence and the subject pattern for the result’s own identity and validity.

A.15.9:4.4 - Separate recognition from assurance

  • Recognition. A title-, department-, document-, approval-, or tool-shaped request that cannot yet name the result and receiving use is enough to open A.15.9. One available-result check and a short answer with its use limit can finish the question. A new request is one possible selected continuation.
  • Assurance. Safety-, release-, compliance-, irreversible-, or high-impact use adds the applicable domain Method, evidence, authority, independence, assurance, acceptance, and stop rules. A concise request does not lower those burdens, and a fluent answer does not satisfy them.

A.15.9:5 - Worked cases

A.15.9:5.1 - Which payroll scheduling question can the existing result answer?

An administrator asks whether moving one contractor submission from Thursday to Friday will miss the current pay run. The existing Thursday submission is already admissible under the contractor arrangement; only the proposed later date is unresolved. Before requesting new payroll Work, the administrator finds a dated payroll result covering the same payroll entity, cutoff, and calendar edition. The source is current for employee payments but explicitly excludes the contractor batch.

The answer about Friday is still open. The employee calendar would read the same whether the contractor cutoff was Thursday or Friday. If that answer is needed to decide on the move, obtain the rule for this contractor and this pay run while the choice is still available. For a recipient who only needs one date already known to make the current run, Thursday answers the question. An agreement to retain Thursday can close the scheduling decision.

A.15.9:5.2 - A heat-pump choice needs one acoustic result

An engineering team is choosing a compressor operating region. It already has a general product noise rating, but the decision concerns tonal noise in a named room, mounting configuration, and speed range. The general rating is useful source material but is not qualified for that use.

Suppose the existing qualified operating region remains available, but the proposed region could meet an important capacity need before the controller choice. The acoustics team can answer the configuration-specific question in that window using an available test setup; the expected gain over keeping the existing region warrants the preparation, test, interpretation, and delay together. This case premise selects acquisition; a general rating or merely cheap test would not do so.

The team requests: “For the controller decision, return the observed tonal-noise and vibration limits for this compressor, mounting, room, and speed range, with the tested conditions and unsupported region. A supported limit, objection, or missing-test blocker is useful; the acoustics result does not choose the controller.”

The acoustics practice keeps its Method and evidence rules; the engineering team keeps the architecture decision.

If the question later becomes which complete internal, provider, reuse, or redesign way can make the same accepted control result available, leave this one-contribution question and use C.38.

A.15.9:5.3 - A fluent tool output is not specialist approval

A case worker receives a generated summary labelled verified legal review. The summary cites no governing edition, jurisdiction, case configuration, performing Agent, Method, or authority. It may help locate sources, but it cannot support the current eligibility decision.

The case worker returns: “The generated summary can help locate sources, but is not qualified for this eligibility decision in this jurisdiction. That decision remains blocked on the missing legal basis.”

A dated legal-result request becomes a continuation only if the obtainable contribution warrants acquisition for this case. If later evidence supports the tool or another Agent as the performer of bounded legal-research Work, those facts do not create legal authority or make the receiving administrative decision.

A.15.9:6 - Precision restoration

Source phraseRecover before relying on itDo not infer
professional result or specialist returnThe governed result kind, subject, conditions, supplier practice, and receiving use.A new FPF result kind or universal profession ontology.
ask legal / safety / architecture / financeThe smallest result question and the decision it can change.A department, title, or field name already identifies the answer.
reviewThe reusable Method, planned Work, dated review Work, communication, and returned result that are claimed.Scheduling or delivery proves Work, acceptance, or adequacy.
approved or signed offThe result plus any separately supported authority, permission, acceptance, or gate relation.A word, signature image, or provider status transfers decision authority.
specialistThe practitioner or other supplying System relevant to the result. If an Agent claim is needed, recover its A.13 local-kind classification and obtaining assignment. Add capability, access, conflict and authority only when consumed by the use.Title, credential, organization, species, or tool label establishes those relations.
AI review or tool checkThe source or result, actual performer if current, Method, dated Work, provenance, checks, evidence, and authority boundary needed by this use.Fluency, automation, branding, or activity establishes truth, Work, permission, or acceptance.
received or deliveredThe communication or transfer that occurred, the independently identified result, and any separate acceptance and use.Delivery is production, acceptance, reliance, or effect.

Bias check. Prestige, recency and popularity can help locate a source; assess its claims against the receiving question’s evidence and applicability requirements. Official status may matter through an applicable authority or binding rule, whose scope must be established separately. That status alone does not establish empirical adequacy or fit outside that scope.

A.15.9:7 - Conformance and practical checks

A use conforms only when the checks needed by its claimed result pass:

  1. The receiving decision or Work, receiver, and action that can change are recognizable to a cold reader.
  2. An already-available result is inspected before new supplier Work is requested, unless none can reasonably be found at the required cost.
  3. The first result gives the useful supported answer and its material limit or blocker. Any new request is selected for its obtainable contribution against the whole acquisition burden under C.11.DUA; a limitation alone requires neither a request nor a separate no-request explanation.
  4. Subject, configuration or situation, interval, assumptions, intended use, and non-use boundary are present at the grain that can change the answer.
  5. The supplying practice keeps its Method, evidence standards, qualification, and domain authority; the receiver keeps its own decision authority unless a separate relation says otherwise.
  6. Request, WorkPlan, assignment, communicative Work, dated Work, result, evidence, delivery, acceptance, reliance, authority, and receiving decision are not collapsed.
  7. A performer, capability, assignment, authority, or Work claim appears only when its basis is current. Performer recovery follows A.13, independent Work admission follows A.15.1, and F.6 applies after that admission when the receiving claim requires assignment-bound attribution.
  8. A.10 governs evidence, provenance, currentness, and bounded reliance rather than being copied here.
  9. A supported result, bounded objection, and blocker are all usable returns; an approval-looking label cannot erase a blocker.
  10. The reopen condition names the smallest changed fact that can alter this use, not a ritual periodic review.

Recognition check. Give a reader a department-, document-, approval-, or tool-shaped request. The reader should be able to name the receiving decision, return the supported answer or blocker, and select further acquisition only when worthwhile, without designing an organization.

Assurance check. For consequential reliance, ask which domain Method, evidence, source edition, independence or conflict condition, authority, acceptance rule, applicability window, and stop are required. Missing assurance narrows or blocks reliance; it does not erase a separately identified source or result.

A.15.9:8 - Anti-patterns

  • Request the artifact. “Send a report” replaces the question and receiving use.
  • Mandatory fresh work. A current qualified result is ignored because the workflow expects a new review, or a useful narrower answer is withheld until every gap becomes a request.
  • Approval by appearance. A title, logo, signature, provider label, dashboard state, or verified tag is treated as authority or acceptance.
  • Receiver takeover. The request dictates the supplier’s Method or rewrites the professional conclusion to fit the desired decision.
  • Supplier takeover. Supplying one result is treated as making the receiver’s decision.
  • One contribution account as ontology. Request, assignment, Work, communication, result, evidence, acceptance, and authority become fields of one invented world-side object.
  • Tool exceptionalism. AI output is either accepted by fluency or rejected by species rather than assessed under the same result, evidence, Work, and authority rules.
  • Local change, global reopen. One changed source or condition forces every contribution and decision to be repeated.

A.15.9:9 - Consequences and trade-offs

ConsequencePractical effect
Existing-result stopAvoids unnecessary specialist Work, delay, and duplicate review while keeping stale or wrong-case answers visible.
Smaller requestsSuppliers receive a decision-relevant question and may return an objection or blocker without manufacturing a document-shaped success.
Preserved authoritySupplier judgement and receiver decision stay independently reviewable.
Better failure informationMissing Method, capability, access, authority, evidence, or current source limits the affected claim without automatically commissioning its replacement.
Cross-domain reuseEngineering, administration, finance, governance, science, medicine, law, safety, and other practices can share the boundary without sharing one domain Method.
Additional precision costConsequential cases require subject, conditions, evidence, authority, and use instead of a familiar approval label.
Bounded conclusionThe result supports only the named receiving use and limits; broader transfer needs another check.

A.15.9:10 - Rationale and SoTA use

The Method starts with the result and its receiving use: define what the receiving decision needs, reuse a qualified result when possible, retain a useful narrower answer, select worthwhile obtainable acquisition, and preserve the supplier’s Method and authority separately from the receiver’s decision. SYSE.9 demonstrates the bounded-request, specialist-Method, authority-split, and receiving-use parts of this move in engineering, while C.11.DUA governs acquisition value and feasibility; the unlike administration, finance, and governance cases show that the boundary transfers while their domain content does not.

A.10 already owns evidence, provenance, currentness, and bounded reliance, while RESULT-TO-NEXT-MOVE already routes an obtained result to the downstream question that is current. A.15.9 contributes only the cross-practice receiving-decision boundary, the existing-result stop, the bounded request after acquisition is selected, the supplier/receiver authority split, and local reopen.

A.15.9:11 - Relations

  • Builds on: A.15 for System-role-Method-Work separation; A.10 for evidence, provenance, currentness, and bounded reliance; A.13 and A.15.1 when performer and Work facts matter; A.2.2 for capability; A.2.1 for assignment identity and the obtaining assignment required by the A.13 core; F.6 when later assignment-bound Work attribution is needed; A.2.9 for communication; C.2.1 for any persistent claim-bearing account; and the subject pattern for the result itself.
  • Coordinates with: C.11.DUA for the value and feasibility of acquiring a further contribution; the supplying DPF or domain Method for the answer; E.18.1 for accepted-problem carry-through; A.15.7 when a qualified result becomes one fact in ongoing Work steering; and RESULT-TO-NEXT-MOVE when the result exists and a later downstream question becomes current.
  • Question-change boundary with C.38: stay in A.15.9 when one receiving decision needs one bounded result from another practice. Move to C.38 only when the new question is how several complete ways could make the same receiving result available. From C.38, return here only for one missing or unqualified outside-practice result inside a way.
  • Keeps outside: supplier-domain ontology and Methods, organization design, procurement and service arrangements, fixed role catalogues, universal approval workflows, the receiving choice, actual realization, and authority transfer.

A.15.9:End

A.15.10 - Resume Work

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

A.15.10:1 - Problem frame

Use this pattern when work has been interrupted or handed to another performer and the next step depends on recovering what was being attempted, how it was being done, or which result can already be used. Use its preparation branch before a likely interruption when a small retained cue can prevent a consequential loss.

The first useful result is a performed continuation under the recovered purpose and method, or a missing contribution that prevents it. Sometimes the useful result is to abandon an obsolete continuation. A note can help obtain these results; creating a note is not the result the practitioner came for.

Begin with the existing work and its ordinary records, tools and surroundings. You need access to the material that supports the next operation and the capability to use it, or a way to obtain the missing contribution. Another performer’s memory or a fluent summary may not contain what you need.

If the question, rules and unfinished action are already available, continue. A brief interruption does not require a written checkpoint. Use A.15.8 when you need to test or repair a performer, support or recovery dependency; use A.15.7 when the basis for continuing is available and only the next action remains to be chosen.

A.15.10:2 - Problem

A bookmark can retain the paragraph while losing the question that made it worth reading. A task list can retain the next item while losing the rule for completing it. A colleague can receive a conclusion without the condition that limits its use.

Consequently, a practitioner may restart everything, repeat finished work or continue a different task. Requiring a detailed account at every pause creates another failure: preparation and record keeping consume more effort than the interruption would have cost.

The practical question is how to retain or recover enough meaning to continue the work, without turning every switch of attention into a reporting procedure.

A.15.10:3 - Forces

NeedDifficulty
Preserve the point of the workThe position can survive after its purpose or governing method has been lost.
Keep preparation smallA complete history can be more expensive to create and read than a bounded reconstruction.
Use current conditionsA faithful old note can be wrong about what is available now.
Transfer workThe recipient may have different capabilities, access and responsibilities.
Resume without false confidenceRemembering an intended action is not evidence that it was completed.
Protect the main workReminders and self-monitoring can become a competing workload.

A.15.10:4 - Solution

Recover the question, the method and the useful state of the work together. Reconstruct only what the next operation needs; then perform that operation. Prepare for an interruption only when doing so is likely to be worthwhile.

A.15.10:4.1 - Decide what could be lost

Ask what would make a return go wrong: losing the purpose, a condition of the method, an unfinished reasoning step, the location of a result, an access route or the occasion for returning.

Use what already holds that contribution. An open calculation, a marked physical arrangement, a working document or a shared task may be enough. Retaining another copy adds a consistency problem unless it serves a different use.

Choose a small preparation when reconstructing the contribution is likely to be difficult, costly or consequential. If it is cheap to reconstruct, leave it to the return. If the interruption is sudden, start with recovery in §4.3. This judgement needs no new estimate, form or justification record merely to make an ordinary reversible choice.

A.15.10:4.2 - Leave a usable return when preparation helps

Preserve the contributions that are at risk:

  • the result being sought and the current question;
  • the method or instruction that governs the unfinished operation, including a condition easily forgotten;
  • the last established result and what remains tentative or unfinished;
  • the material needed to continue, and where it can be obtained; and
  • the next useful operation or open choice, together with a cue that will bring the work back when appropriate.

Keep these in the working material when possible. A short comment beside a calculation may do more than a separate summary. A pointer to a method is useful only if the returning performer can reach and interpret the needed instructions.

Arrange the return cue where it will be encountered: on reopening the work, at the relevant event, or through an agreed reminder. A saved file that the performer will not know to open does not supply that cue.

Use a time reminder only when time is the relevant trigger. Avoid copying sensitive material into a reminder when an accessible protected source can supply it.

Choose a pause point with a recoverable distinction between established and unfinished work when circumstances allow. Do not assume that every subtask boundary is equally easy to resume, and do not delay a necessary interruption merely to complete a record.

A.15.10:4.3 - Reconstruct the working question and method

On return, recover why this work was undertaken and whether that purpose applies. Read the relevant working material, including the operative part of the method when the summary or bookmark does not preserve it.

For an uncertain continuation, try stating:

We are trying to obtain this result. This is the open question. These rules govern the next operation. This contribution is established; this other part has not yet been completed.

This can be an internal or spoken reconstruction. It is not a required written formula.

If you cannot recover a decisive relation, use its source rather than filling the gap with a plausible story. Reconstruct a small missing calculation or argument, ask for the unavailable contribution, or return to the last reliable point. B.5.RA helps recover an argument; B.5.RC helps reconstruct a construction.

Repeat the whole task only when the needed contribution cannot be recovered adequately through a smaller safe operation under the applicable rules.

A remembered intention, a selected next step and a performed operation remain different. When the completion of an important step is uncertain, inspect its result or repeat the smallest safe operation that settles the uncertainty. Do not repeat an irreversible action merely because its record is missing.

A.15.10:4.4 - Restore the conditions needed now

Compare the recovered account with conditions that can change the continuation: the question, inputs, material state, definitions, decision criterion, available tools, access or responsible performer. Inspect only the dependencies that matter to the intended use.

A retained record says what was known or intended when it was made. Assess whether its claims apply to the physical state, access or permission needed now; continued availability of the record alone establishes none of those conditions.

If a changed premise affects a result, revise the affected reasoning; B.5.RR supplies that operation. If a support dependency is missing or its recovery is in question, use A.15.8. When the working basis is usable but entry conditions remain unresolved, A.15.5 supplies the readiness question.

Retain a result whose conditions hold. Reopen a result whose changed condition matters. Set aside a continuation that no longer serves the purpose. Do not require a complete recheck merely because time has passed.

A.15.10:4.5 - Continue far enough to use the recovered basis

Perform a bounded, useful next operation under the recovered method. For example, finish the pending comparison, derive the next consequence, or use the recovered observation to select the next action. A.15.7 helps if that action is open.

Let the operation expose a consequential missing link. If it does, recover that link rather than treating the difficulty as proof that all previous work is unusable. Stop or obtain help when access, capability or a protected operating condition is missing.

Update the working result in its normal place. Correct a misleading return cue or retire an obsolete one if it would cause a later mistake. An uninterrupted continuation requires no extra “resumed successfully” report.

A.15.10:4.6 - Transfer the contribution to another performer

When someone else continues, supply what they need to act, not a transcript of everything the previous performer did. Preserve the purpose, governing method, established and unfinished contributions, relevant conditions and accessible source material.

The recipient reconstructs and uses those contributions. Where misunderstanding would change the work, a brief explanation of the intended next operation or a small continuation can expose the mismatch. Do not demand a ceremonial read-back when shared material and ordinary performance already make it clear.

A handoff does not itself supply the recipient’s capability, access or authority. Obtain a missing contribution through its owner; A.15.9 can help frame a bounded request.

If responsibility must change, make that change through the applicable arrangement rather than inferring it from receipt of a message.

A.15.10:5 - Archetypal Grounding

A.15.10:5.1 - A bookmark survives but the reading method does not

An AI assistant resumes a wording review at paragraph six. Its summary says “five paragraphs done; next, six”, but the operative instruction was to determine what each optional expression contributes, not just to replace conspicuous jargon.

It opens the method’s operative section and the last substantive result. The fifth paragraph was completed; the sixth was only located. It reads the sixth paragraph as a connected argument and tries removing “approved” from a procedure name. The word identifies which procedure may be used, so deletion would change the instruction. It retains the word and explains that contribution through the review’s existing result.

The return recovered both the position and the method. It did not require reviewing the first five paragraphs again.

A.15.10:5.2 - The recipient receives a conclusion with an obsolete condition

A colleague takes over a comparison of two providers. The working sheet says “A costs 600; B costs 680; choose A”. The underlying calculation includes a 100-unit reuse credit for A. The next task is to confirm the choice for the revised specification.

The recipient recovers the price comparison method and the condition for the credit. The revised specification makes the credit inapplicable. Retaining the unchanged quoted costs, the recipient recalculates A as 700 and compares it with B at 680.

With the other selection conditions unchanged, B is now the cheaper option. If another criterion would change the selection, price alone would not settle it.

The handoff did not justify accepting the old choice or rerunning every part of the procurement study. Recovering one condition identified the reasoning that needed revision.

A.15.10:5.3 - An ordinary pause needs no checkpoint

A designer stops to answer a short question. The drawing remains open at the unresolved joint, the two alternatives and their load condition are visible, and the designer can explain the pending comparison. They continue the comparison.

If the drawing is later transferred to a colleague, the same visible marks may be insufficient: the colleague may not know which load condition governs the comparison. A short annotation at that point can supply the missing contribution. The useful support depends on the receiver and the work, not on a universal note format.

These are constructed illustrations. They demonstrate the operations and their different branches; they are not evidence of general productivity gains.

A.15.10:6 - Bias-Annotation

Much interruption research studies humans doing short tasks or office work. Its findings do not establish identical mechanisms in AI, teams or machinery. The general method concerns recoverable purposes, instructions, results and conditions. Human stress, memory and learning remain matters for the appropriate human-specific methods.

External support is sometimes helpful and sometimes costly. Confidence that one will remember can be inaccurate, but that fact does not justify a universal reminder or record policy.

A.15.10:7 - Conformance Checklist

  • The continuation serves a current purpose and an identifiable working question.
  • The performer can recover the operative method, not only the position.
  • Established results, tentative conclusions and unperformed steps are distinguishable where the next action relies on them.
  • A retained cue can be found and interpreted when needed.
  • Changed conditions reopen only affected reliance; an old record is not treated as a current observation.
  • Missing capability, access or authority remains a missing contribution.
  • Preparation and reporting are omitted when ordinary continuation already suffices.
  • The result is useful continuation, a warranted change of direction or a blocker.

A.15.10:8 - Common Anti-Patterns and How to Avoid Them

FailureConsequenceRepair
Resume from a cursor aloneThe performer applies a different rule to the right item.Recover the governing method and the last established result.
Turn a planned step into a completed stepLater reasoning relies on a result that was never obtained.Inspect the result or reconstruct the smallest safe missing contribution.
Retain everything in a separate reportPreparation, reading and synchronization displace the work.Keep only the threatened contributions in existing working material.
Trust the old account as present stateA changed input, tool or physical condition invalidates continuation.Inspect the dependencies that can change the next use.
Restart all work after any doubtValid results and effort are discarded.Return to the last reliable point and revise the affected part.
Equate delivery with a usable handoffThe receiver lacks a rule, access or capability needed to act.Restore that contribution and test understanding through useful continuation when needed.

A.15.10:9 - Consequences

A return becomes an act of reconstructing and using the work, rather than locating an item or rereading its history. Useful preparation can reduce reconstruction and wrong continuation. Its cost includes writing, retrieving, interpreting and maintaining the support.

The method can expose that a different result is now needed, that help is required or that the work should stop.

A.15.10:10 - Rationale

A continuation depends on more than a position. Purpose selects what matters, the method determines what the next operation means, and prior results constrain what can be used. Retaining any one of these while losing another can produce plausible work toward the wrong result.

Preparing a cue and resuming later are temporally related contributions. During continuation, applying the subject method and regulating the return can contribute simultaneously to the encompassing work.

Their occurrence does not by itself establish Method parthood; use B.1.5 when that relation matters.

Configuration recovery testing asks whether a dependency withstands a condition; this method supplies the ordinary preparation and reconstruction that can be performed or tested. A configuration test is not a mandatory predecessor of every return.

The smallest useful support is receiver-relative. A familiar short cue can work for the original performer while a colleague needs the rule behind it. Conversely, a full narrative can obscure the two lines the colleague needs. Existing material plus a bounded reconstruction is an alternative to writing a new account.

A.15.10:11 - SoTA-Echoing

Leroy and Glomb, 2018 investigated a brief ready-to-resume intervention across four studies. The reported benefit concerns attention residue and performance on the interrupting task under anticipated time pressure. It does not establish that every return to the original task becomes faster. It supplies a historical reason to prepare an unfinished question before switching.

Van Zoonen and Scharp, 2025 tested a related daily intervention with 50 workers over four days. Its questions concerned progress, where to continue and remaining challenges. The study reported reduced effects of intrusions through attention residue, but the intervention also increased overall exhaustion on average.

Adopt the brief preparation as an available human technique, retaining burden and the study’s scope. The study’s submitted form is research apparatus, not a required working record.

Gilbert and colleagues, 2023 review intention offloading: reminders interact with internal memory, confidence, effort, reward and the reliability of external support. These costs and limits support choosing reminders for a use rather than treating more reminders as inherently better. Laboratory cost and reward findings do not fix a general threshold for professional work.

Ngai and Gilbert, 2026 report that predictions combined with feedback can improve offloading decisions under experimental conditions; prediction alone did not produce the relevant improvement. Transfer to everyday use remains uncertain. A reminder policy therefore remains revisable through the work it helps or burdens.

The synthesis here joins selective external support with reconstruction of the governing method and changed-condition reasoning. The human studies supply bounded techniques and counterexamples; they do not establish the whole cross-agent method or a common cognitive mechanism.

Reconsider the preparation branch when relevant field evidence changes its benefit or burden for the intended setting.

A.15.10:12 - Relations

  • A.15.1 governs the identity and temporal extent of Work; a return does not settle occurrence identity by itself.
  • A.15.2 governs WorkPlan content. A return plan remains a plan until work is performed.
  • A.15.5 handles entry readiness; A.15.7 selects a next action once the working basis is available.
  • A.15.8 tests and repairs configuration and recovery dependencies when that question is current.
  • A.15.9 helps obtain a bounded missing contribution from another practice.
  • B.5.RA recovers an argument; B.5.RC reconstructs a construction; B.5.RR revises reasoning affected by a changed premise.
  • C.11.DUA keeps preparation, advice and demands for further evidence proportionate to the decision.
  • E.23.CAE distinguishes apparent capability loss from failures of access, selection or expression when competing explanations require a probe.
  • B.1.5 supplies Method parthood when the constituent and encompassing methods must be stated.

A.15.10:End

A.15.11 - Make Methods Noticeable in Work

Type: Method pattern Status: Stable Normativity: Normative unless marked informative

A.15.11:1 - Problem frame

Use this pattern when a useful way of working repeatedly goes unused because the practitioner or agent does not recognize an occasion for it. Use it also to introduce a promising possibility into successful work: a failure need not occur before a better way becomes worth considering.

A colleague can know how to compare alternatives yet estimate a proposed addition without asking whether it is worth making. An assistant can retrieve an applicable method when asked while never offering it at the moment it would help. A learner can recognize a difficulty after a teacher points it out but overlook it during the whole task.

The subject is the arrangement that brings a potentially useful method into consideration during work. It connects an occasion, a recognizable relation to the work, and access to the needed operation. A cue is something encountered that makes that relation available: a question in a working document, a contrasting case, a colleague’s agreed intervention or an event in a tool.

The first useful result is a method considered at the point where it could help, followed by use, a named unresolved condition or dismissal. Someone arranging the opportunity needs a method that may help, or a question about a missed opportunity. The recipient need not already have diagnosed the omission.

When no useful method or meaningful question has yet been identified, B.5.PI helps bring ongoing work into inquiry. Arranging a reminder for a known method does not supply that preceding contribution. The cue arranged here can make that inquiry method available at an ordinary handover or demonstration, without anticipating the difficulty it may reveal.

If the useful method is already being considered, continue with selection or application. If its description cannot be obtained, repair access. If the performer recognizes the need but cannot perform the operation, obtain that contribution or develop the capability. More reminders alone do not supply it.

A.15.11:2 - Problem

A searchable library helps someone who has begun to search. A well-written description helps someone who reaches and understands it. Neither ensures that a familiar, apparently adequate way of working will make room for a relevant alternative.

The missed relation may be between levels of work. A component can function correctly while its contribution no longer serves the larger task. Conversely, improving a constituent capability can be more useful than replacing the whole method. Unless that relation is noticed, the practitioner may keep optimizing the wrong contribution.

Prompting creates its own problem. Frequent recommendations interrupt work, consume interpretation time and can turn an adequate answer into an unnecessary procedure. The practical question is where and how to make a useful possibility apparent, while preserving the option to continue without it.

A.15.11:3 - Forces

NeedDifficulty
Reach the work before a query existsThe person who would benefit may not see a reason to search.
Show applicabilityA shared word or resemblance can hide different conditions.
Preserve the encompassing taskA locally attractive improvement can displace more valuable work.
Support learningGiving the answer can help this attempt without developing later use.
Keep attention availableRecognizing and dismissing advice also costs effort.
Respect different performersA human, an organization and an AI system need different arrangements and learning methods.

A.15.11:4 - Solution

Connect a possible contribution with an occasion already present in the work. Make the relation understandable and the operation reachable; then see whether that arrangement helps enough to keep it.

Use what is already known before spending effort on the arrangement. Stop when the available information already settles that it would not be worthwhile. Construct a countercase or run a trial only when its result could change whether or how to use the arrangement.

A.15.11:4.1 - Choose the work and the possible contribution

Start from work someone does. State what could improve: a choice, a result, the range of situations the performer can handle, or the effort required. Identify who can arrange the opportunity and who would encounter it. The same person can prepare a cue for their own future work.

Identify how the selected action contributes to the encompassing work. When the proposed improvement depends on cooperating methods, recover the larger method and the constituent methods that make the action possible; they may be performed together in the same action. Use B.1.5.EW when that connection is unclear. Judge the improvement under the conditions of the encompassing work, including any missing capabilities or resources on which it depends.

When no question has yet been raised, B.5.PI uses an ordinary work occasion to compare a result with its use and develop a question or retain an early cue. Arrange that opportunity without presupposing a particular error.

When the useful contribution is uncertain, examine a small, permitted sample of the work with a relevant practitioner or source. Ask what an available alternative could make possible. C.40 and C.40.CD supply constructive inquiry where the question or method itself needs development. Do not install a standing prompt merely because a topic sounds relevant.

A.15.11:4.2 - Explain the relevance relation

Read the candidate method’s operative instructions. Recover the result it can obtain, the inputs and capabilities it needs, and the conditions that limit its use. Connect that result to the receiving task.

A useful cue can take this form:

This feature of the work makes this question worth considering. This method could obtain this contribution, provided these conditions hold.

Use the language of the work. For example: “Before estimating the extra report, compare what decision it would improve with the report we already have.” Naming a pattern can provide access after this relation has become clear.

When a plausible false match could change the suggestion, use a nearby case in which the method should not be suggested. Matching existing observations can supply this comparison. If the same cue recommends the method there, refine the relation or leave the recommendation tentative.

Shared terminology is a lead for investigation; applicability depends on what the operation would do under the conditions.

A.15.11:4.3 - Place the cue where it can be encountered

Choose an existing occasion: preparing a plan, receiving a result, changing a tool, estimating an addition or revisiting a commitment. Put the cue in material used at that occasion, or arrange an intervention by a participant who already attends to it.

Select the means according to the performer. A visible comparison can help a human notice a relation. An organization’s existing review meeting can bring a specialist into the choice. A tool can provide relevant instructions to an AI agent when an existing software event occurs. These arrangements share a functional purpose without requiring the same internal mechanism.

A short execution checklist is one possible cue. Give it an occasion and user, express each check as something that user can inspect, and say what to do when a condition is unmet or cannot be determined. Distinguish checking a known condition from discovering whether the chosen method and its result fit the work.

A pattern’s Conformance Checklist can supply content, but copying it does not automatically produce a usable execution aid.

For example, before using a calculated amount in a quotation, a check can ask whether the amount is defined for these inputs and means what the quotation requires. An unresolved item leads to examination of that case, not a forced tick.

Keep a way to raise a consequential concern that none of the listed checks expresses; use B.5.PI to develop the question and B.5.EA when a participant cannot yet put the difference into words. Passing the listed checks establishes only what those checks support.

Choose timing that preserves the work. An explanation during a difficult movement can disrupt the action it is intended to help; an agreed pause may be the useful occasion. A quiet pointer may suffice where interruption would cost more. Use only observation and access already authorized for this purpose.

A.15.11:4.4 - Make the next operation attainable

Ensure that the recipient can interpret the cue and reach enough instruction to begin. A familiar pattern name may be sufficient for an experienced practitioner; another recipient may need a small contrast showing why the method fits.

When the relation is not yet discernible to a person, obtain a suitable learning method and practice. When the relation is understood but execution is unavailable, identify the missing capability, resource or supporting participant. E.23.CDI frames capability development; obtain a teaching or training method suitable for the practice being learned.

Keep the action proportionate to the present need. Sometimes a colleague’s answer is enough. Sometimes the recipient needs a reusable method or practice across changed conditions. Introducing a method does not by itself choose between those purposes.

A.15.11:4.5 - Try the intended arrangement

When a trial can change the arrangement decision and its result is not already available, use a safe instance of the receiving work. Establish whether the cue is encountered, whether its relevance can be recovered, and what the participant then does.

Include a condition that defeats the proposed match when a plausible false recommendation could change the outcome.

Keep the intended aids available. If a coach adds an explanation during the trial, that explanation becomes part of what enabled the result. If an AI assistant receives additional context, its success applies to that context.

To claim use without those aids, examine that different configuration separately.

Use E.23.CAE when distinguishing recognition, access, adaptation and capability change would alter the remedy. A bounded practical repair can proceed without a complete causal diagnosis. If the arrangement fails, locate the failure: no encounter, unclear relation, unavailable instruction, missing capability, inappropriate method or excessive burden.

A.15.11:4.6 - Compare with continuing without the suggestion

Ask what changed in the receiving work and what the arrangement cost. Include preparing and maintaining the cue, interpreting false matches, acquiring any missing capability, performing the method and displacing other work.

C.11.CRC compares a finite change with the current configuration. C.11.DUA examines the work that following the suggestion would impose on its recipient and whether that work helps their decision. Use them when the choice needs that examination. An ordinary reversible decision can remain a brief judgement.

Compare at the level where the gain is needed. A better component result may leave the whole task unchanged. A small preparatory improvement may enable several larger methods at once. Recognition, correct application and worthwhile use are separate outcomes.

Keep, revise or remove the arrangement accordingly. A recipient can dismiss an inapplicable suggestion or one not worth its burden without producing a refusal record.

Where an accountability requirement applies, use its existing record rather than inventing one for every cue.

A.15.11:4.7 - Adjust after use

Repeated false matches can reveal a poor occasion, an overbroad relevance relation or a different recipient need. Repeated recognition followed by inability calls for a capability or support change. Advice that has become familiar and adds no value can be shortened or removed.

Retain aids that remain useful in the intended configuration. If independent performance is the goal, arrange a separate transition and assess it under the relevant learning method. Removing every aid is not a universal measure of mastery.

A.15.11:5 - Archetypal Grounding

The cases below are constructed examples of the method, not measurements of its effectiveness.

A.15.11:5.1 - An optional report enters a portfolio decision

A team estimates six hours to add a chart to a weekly report. The existing report already supports the current staffing decision. Their planning sheet asks only how long the addition will take, so that estimate is taken as a reason to start implementation.

A planner adds one question beside the estimate: “Which decision becomes better with this addition, compared with the report we already use?” The linked instruction explains how to compare an attainable addition with the current arrangement. For this example, adding and using the question takes ten minutes.

For this staffing use, the team finds no improved decision and keeps the current report. Under the stated estimates, preparing and using the cue leaves five hours and fifty minutes available for other work compared with adding the chart. A different benefit of the chart would reopen the comparison.

For a different, one-off cue whose only possible benefit is saving at most two minutes, while preparation and explanation would take twenty minutes, the planner stops before creating or testing it. The known benefit does not justify that work.

Now change the report case: the new report is needed for an already accepted contractual obligation. The same optional-improvement question no longer settles whether to provide it. The team retains the obligation and compares ways to satisfy it. This contrast narrows the cue to optional additions and prevents an attractive cost comparison from silently changing the commitment.

A.15.11:5.2 - A model-review question reaches an assistant

An organization has an instruction for examining how data were recorded. Its assistant usually starts fitting a model as soon as a table arrives. The column label “measurement” does not reveal that some entries are selected or censored.

At the existing model-review step, the organization makes a question available: “What procedure produced each kind of record, including values omitted or reported only as bounds?” In this example the data documentation says that an entry “below 5” records any value under the instrument’s reporting threshold.

The assistant obtains the relevant modeling instruction. For that record, it evaluates the proposed model’s probability of a value below 5 instead of treating 5 as an observed value.

If the documentation instead says that values below 5 are absent from the dataset, the receiving calculation changes. The cue has exposed a condition to investigate; the modeling method determines the calculation. If documentation is unavailable, the result is a missing fact, not a guessed observation procedure.

The assistant’s access to this question is part of the configured work. This case establishes neither parameter learning nor recognition without the provided question.

A.15.11:5.3 - A teacher distinguishes noticing from movement capability

During a familiar dance figure, a learner remembers the sequence and follows the rhythm in a simpler version, but loses balance during a turn. At an agreed pause, the teacher asks the learner to compare the two versions and identify where continuing the figure becomes difficult.

The cue makes a coordination question available. It does not establish the cause of the loss or supply the bodily method that would repair it.

The teacher now needs a movement-practice method for examining the loss of balance and choosing a suitable exercise within the learner’s limits. After practice, the relevant return is to the figure with its rhythm, balance and partner relations occurring together.

Repeating “notice your balance” is unhelpful once the learner already recognizes the difficulty. The next contribution lies in acquisition or execution, not in making the question more prominent.

For an artificial performer, the corresponding next contribution must be selected from its sensing, control and learning methods; a human first-person instruction is not automatically an executable robot instruction.

A.15.11:5.4 - A checklist supports a handover without claiming completeness

A laboratory’s existing handover requires the recipient to know which sample each result concerns. A short execution check asks the producer to compare the identifiers on the result and the specimen record before transfer. The action for an unresolved match is to recover that correspondence before using the result; a tick without that comparison supplies no assurance.

The identifier check can pass while the recipient cannot use the result because its unit or measurement condition is unclear. The handover therefore leaves room to name a concern outside the listed checks and obtain the relevant explanation. B.5.PI helps develop the question if neither person can yet state it.

The checklist remains useful for its selected condition; it is not enlarged into a claim that every possible problem has been excluded.

A.15.11:6 - Bias-Annotation

The person arranging a cue has a candidate method in mind and can mistake its uptake for success. Retain cases where the appropriate outcome is to dismiss the method or continue with a simpler answer.

Institutional authority and repeated prompting can make an optional suggestion feel compulsory. State optionality where it affects the recipient’s choice. A method supplier’s wish for adoption does not establish value for the work.

A.15.11:7 - Conformance Checklist

For a consequential use, inspect the arrangement and the resulting work:

  • Is there a recognizable occasion and a reason the candidate could change the receiving work?
  • Can the recipient recover the applicability relation and a condition that would defeat it?
  • Is the cue encountered through the intended means, with the needed access and authority?
  • Does the next operation have its necessary capabilities and supports, or does the result identify what is missing?
  • Were any extra explanations or aids retained in the claim about what worked?
  • Does the comparison include the cue’s burden and its effect on the encompassing task?
  • Can a useful dismissal, revision or removal count as success?
  • When a checklist carries the cue, can the user inspect its condition and continue when it is unmet, unknown or insufficient for the receiving use?

Use the questions that can change the judgement about this arrangement.

A.15.11:8 - Common Anti-Patterns and How to Avoid Them

Publishing without arranging an encounter. An unused method receives a clearer title and another index entry, but the intended practitioner never reaches either. Improve the occasion and route into the work.

Matching a topic while missing a condition. A cue for comparing optional additions is shown when the task is to fulfil a binding reporting obligation. Retain the obligation and compare permissible ways to meet it.

Repeating a cue after recognition succeeds. A learner or agent can identify the need but lacks a constituent capability. Obtain the missing contribution; repetition does not resolve that failure.

Counting uptake as value. Counting more opened patterns or applications can conceal delay or displaced work. Examine what improved, including cases where no intervention was preferable.

A.15.11:9 - Consequences

A useful method can enter work before the recipient formulates a search query. Its relation to the task becomes available for examination, including rejection. The arrangement can be as small as a question beside an existing estimate.

This adds preparation and maintenance costs and can create distraction. It also depends on someone finding a method worth introducing. Repeated use can justify improving a shared arrangement; a one-off answer can remain the better choice.

A.15.11:10 - Architectural Rationale

Publishing a method, recognizing its relevance, obtaining its instructions, learning it and performing it require different contributions. Connecting them at a work occasion addresses the gap left when a capable recipient never begins to search. It also makes a failed connection repairable without assuming that every omission is a memory defect.

The method keeps the constituent and encompassing work visible because the value of advice can change between them. A local improvement earns its place through what it enables or preserves in the whole, with the necessary constituents available. B.1.5.EW helps identify which constituent actions perform the larger work; this pattern uses that relation to choose and assess the suggestion.

The general contribution is the construction of an encounter and a usable relevance relation. Domain methods determine whether the proposed operation is sound, and capability-development methods determine how a performer learns it. A configurable assistant, a human teacher and a revised working document are alternative implementations; none is prescribed for every use.

A.15.11:11 - SoTA-Echoing

The practice question is how to make a useful method available before a recipient asks for it, without imposing more burden than the contribution warrants. The selected answer is a methodological synthesis: arrange an encounter, expose the relation, preserve access and prerequisites, and compare use with non-intervention. No single cited experiment validates this complete method across domains.

Adapt relational comparison; reject a hint as proof of spontaneous use. Gick and Holyoak’s Schema Induction and Analogical Transfer (1983) remains a historical experimental anchor for this distinction. Their comparison of example structures informs §4.2; their prompted and unprompted conditions inform §4.5. A principle or diagram added to one story did not reliably produce the same benefit as their richer comparisons.

These bounded tasks do not prescribe an example quota or establish transfer to all work. Relational comparison is worth its added effort when a simple pointer leaves applicability unclear.

Adapt cue placement and cost comparison. Tsai and Gilbert’s Strategic reminder setting for time-based intentions (2025) examines short laboratory intentions, reminder effort and cue visibility. It informs §§4.3 and 4.6: an external cue changes both the remembering task and the ongoing work. The alternative is using the support already available.

These experiments concern known intentions and cannot establish discovery of an unnoticed method. Use their contribution after identifying a candidate occasion; do not generalize their brief delays or participant exclusions into everyday guarantees.

Adopt separate questions about immediate assistance and later use. Teo and colleagues’ AI Assistants Overassist (2026 preprint), §§3.1–3.5, separates intervention timing, immediate results and performance on a related problem under different retained contexts. It informs §4.5 and the comparison with no intervention in §4.6. A supplied answer may be the right immediate contribution, while development requires a different comparison.

The simulated students and context manipulations do not establish parameter learning or human acquisition; the arrangement needs examination in its receiving work.

Adapt a checklist to execution. Degani and Wiener, Human Factors of Flight-Deck Checklists: The Normal Checklist (1990), §§3.1.4 and 5.2.2, distinguishes doing items from verifying their state and describes a correct response being given without the corresponding verification. This historical aviation analysis informs §4.3 and §5.4: choose an occasion, inspect the relevant condition, and give an unresolved item a continuation.

A publication’s conformance list and a usable execution aid have different jobs. The aviation method does not make any finite list comprehensive for all work; an unlisted concern retains its own path into inquiry.

Reopen the choice when a simpler entry works just as well, a cue repeatedly misfires, changing work defeats its relevance, or a stronger subject method offers the same gain with less disruption. Human learning and automatic recommendation require their own more specific evidence when those are the intended claims.

A.15.11:12 - Relations

  • A.15.7 chooses an action from the available situation and applicable methods. This pattern constructs an encounter when a relevant possibility repeatedly fails to enter that choice.
  • A.15.8 examines performer and support dependencies. A.15.10 retains or reconstructs an interrupted continuation; this pattern can introduce a method that has never belonged to the present work.
  • B.1.5.EW recovers how constituent actions enact encompassing work and which whole conditions constrain those actions.
  • B.5.PI connects ordinary work with inquiry before a known problem or help request; B.5.EA develops an unformulated distinction. They supply what merely arranging a known-method cue cannot.
  • C.40 and C.40.CD develop problems and useful possibilities where the candidate relation is missing.
  • C.11.CRC compares the finite change with the current configuration. C.11.DUA examines and repairs the demands imposed by advice. C.11 supplies the resulting choice when it needs explicit treatment.
  • E.23.CAE distinguishes explanations of changed performance when that distinction matters; E.23.CDI frames development of the required capability.
  • E.11 governs publication entries that can carry part of the encounter. A publication entry remains one possible means.

A.15.11:End

A.15.PROD - Production Work, Entity-Identity Inception, and Production Completion Recovery

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Name. Separate production work, when this entity first exists, and when production was completed.

At a glance. Production wording often compresses three questions: is this dated Work the whole production Work or only a declared part; when did this entity first satisfy the applicable identity rule, and which Work brought that about if attribution is required; and, for completion, which subject state satisfied the criterion and which separate governor made that satisfaction close the production Work? This pattern answers each question with separate local claims. It introduces no universal production relation or production-work kind.

Call one specification or criterion an edition of another only when their C.2.1 EpistemeEditionRelation obtains.

Claim-record gloss. A local compound relation-bearing claim is one checkable statement for one selected question, built from already governed facts. It is neither an omnibus production record nor a new relation kind. Whole production work, first existence, and completion therefore remain three separate claims even when they cite overlapping facts.

A.15.PROD:1 - Problem Frame

Use this when. Practitioners SHOULD use this pattern when work is said to have made, produced, built, assembled, grown, generated, finished, or completed something and the receiving decision needs to know which production question is true. They SHOULD prefer it when one work occurrence is nested in larger work, several work parts occur concurrently, an entity becomes identifiable before all work ends, or completion is being confused with delivery, acceptance, release, publication, or availability.

EntityOfConcern by selected branch. Production wording is the umbrella. A production-work-participation claim concerns currentWork; an entity-inception claim concerns producedEntity after inception. Completion needs two claims when Work closure is asserted: the state-satisfaction claim concerns completionSubject, while the production-work-completion claim concerns productionWork and cites the separate closure governor.

Keep each in its own C.2.1 episteme when persisted; never manufacture a union concern.

Working reader. A practitioner or modeler responsible for settling one of these production, identity, or completion questions for a current engineering, manufacturing, construction, lifecycle, audit, or scientific use before relying on delivery, acceptance, release, publication, or availability.

Viewpoint. The practitioner SHOULD recover the smallest receiver-relevant claim: select one branch, identify its EntityOfConcern, and stop when that branch is decided or its blocker is known. This pattern is not a form to fill in.

First useful move. The practitioner SHOULD first ask which answer the receiving action or decision needs now:

  1. Is this dated Work the whole production Work for this use, or a declared proper part of it?
  2. Under the applicable identity rule, when did this entity first exist? If the recipient also asks which Work brought it into existence, establish how that Work changed the conditions in the rule.
  3. Which subject state satisfies the applicable completion criterion, and which declared predicate or local claim makes that satisfaction close the production Work at this boundary?

The practitioner MUST NOT substitute one branch’s conclusion for another branch’s answer. Shared facts may support more than one branch only through each branch’s own predicate and applicability.

What goes wrong if missed. Any work-caused change is called production; an entity is treated as existing before its identity rule first holds; a finishing operation is mistaken for entity creation; a plan, log, post-state picture, or first observation is treated as the change-producing link; and a later delivery or acceptance claim is used to revise historical completion without a new basis and claim.

What this buys. Teams can attribute production work at the right work boundary, state when one entity first exists, and preserve historical completion without inventing a universal relation kind. Narrow and larger production readings can coexist through work-part relations. Identity, completion, rework, delivery, acceptance, release, publication, and availability remain independently inspectable.

Cross-domain recognition test. These three non-exhaustive recognition situations show that the same three production questions remain separate across heterogeneous practice:

Recognition situationFirst current questionBlocked overread
A fastening step is said to have “produced Car 42”.Is the step whole production work or a proper part, did Car 42 already exist, and which completion criterion is current?The last visible step establishes neither first existence nor completion by narrative order.
A culture run or spontaneous biological process is said to have “produced Batch B17”.Does the user need the first time the batch existed, the time it met a state criterion, or attribution to particular Work? For attribution, apply the performer and Work route in section 4.2.Growth or reaction may ground a transformation, while production through Work requires independently admitted Work and its own attribution basis.
A build pipeline is said to have “produced ReleaseBinary 12”.Which dated build work and governed effects first established the artifact identity, or satisfied the build-completion criterion?Build success, publication, release, deployment, and availability remain different claims.

First worked replay — Car 42. Apply the common performer/Work route in section 4.2 to FasteningCell-7, NutFasteningWork-42, and their enacted fastening Method. The named Work-to-change predicate, finishing-state criterion, and separate closure rule establish that the Work completed the required fastening; Car 42 already existed. A missing Work-to-change or Work-closure governor returns the blocker shown in case 5.1 while preserving the independently established Work, transformation, or state-satisfaction claim.

So-what adoption test. Would replacing the separate branch answers by one broad production sentence change what the receiver may rely on, schedule, audit, accept, release, or reopen? If yes, the practitioner SHOULD apply this recovery. If only one already-governed neighboring claim is current, the practitioner SHOULD use the pattern that governs that claim instead.

Not this pattern when. Practitioners SHOULD use A.15.1 when the only question is what work occurred; A.3.4 when the only question is what changed; A.3.1 when the only question is the reusable way of doing; the pattern that defines entity identity when only entity identity is current; or the pattern governing evaluation, delivery, acceptance, release, publication, availability, evidence, or assurance when only that neighboring claim is current.

This pattern coordinates those objects only for a selected production-recovery question.

Local claim and ontology boundary. This pattern introduces neither a production-Work U-kind nor universal production, inception or completion relation kinds. The default result is a local compound claim under A.6.RCD disposition 2; identify its C.2.1 episteme when a receiving use needs that separate identity.

A reusable predicate-definition episteme is justified when its parameterized participant meanings serve a named use. Consider a derived relation-kind candidate when a named use needs an obtaining occurrence as a participant, comparison object or otherwise identified relation; A.6.RCD and later admission govern that continuation.

A.15.PROD:2 - Problem

Production speech crosses several ontological boundaries. Dated Work is an occurrence. A transformation is the bounded change of a referent. An identity-specification episteme states when a candidate counts as the entity in question; a named applicability predicate or filled local claim applies it to the candidate basis and boundary. Entity-identity inception is the first boundary at which that applicable rule becomes true.

For completion, a criterion first tests the state of completionSubject; a separate closure predicate or local claim says whether that satisfaction closes productionWork. A measurement or evaluation result is a separately defined value or episteme about its own concern; it is neither the produced entity nor Work completion.

These boundaries often differ. A ship can first exist while outfitting continues. A car can already exist before a required nut is fastened. A finished product can later be damaged, delivered, rejected, repaired, republished, or made unavailable. One broad production predicate hides those differences and also hides the missing governor when attribution cannot be established.

A.15.PROD:3 - Forces

ForceTension
Familiar production language vs claim identityOne sentence often carries work participation, entity inception, completion, and later acceptance at once.
Narrow work vs containing workA finishing occurrence may be production work for one bounded use and a proper part of a larger production occurrence for another.
Product-class identity before the entity existsEntity-inception recovery remains blocked unless the identity-specification episteme and either a named applicability predicate or a filled local claim apply it to the candidate basis, subject context, and inception boundary before inception; no surrogate future entity is introduced.
Actual work effects vs observationLogs, deltas, pictures, and first observations may support a claim; named predicates and obtaining facts establish the Work-to-change or change-to-identity links.
Work composition vs transformation compositionA.15.1 may ground composite work while no accepted transformation-composition governor exists.
First existence vs completionIdentity and completion may coincide, but neither criterion entails the other.
Historical truth vs later stateIndex earlier completion by its criterion, applicability basis, boundary, and state; later damage, loss, rework, delivery, or acceptance receives a separate claim.
Reusable language vs ontology economyRepeated domain use may justify predicate semantics, but a convenient production label does not justify a universal relation kind.

A.15.PROD:4 - Solution

The practitioner MUST choose one of the three production questions, identify the subject of the requested claim and gather the facts that decide it. Identify the Work when attributing a change or closing production. The practitioner MUST state each answer as a separate local compound relation-bearing claim and MUST stop or return a blocker when a required predicate, criterion, applicability rule, boundary fact, work granularity, or transformation-composition rule is missing.

When the receiving use needs the separately referable claim, identify its C.2.1 episteme. When the receiving use also depends on availability to an audience through a form or carrier, establish the separate E.24.PUB publication occurrence.

Core and branch cut. The common recovery core is receiver-first question selection, object recovery, closure through declared predicates or one local claim selected under A.6.RCD disposition 2, and a stop. The production-work, entity-identity-inception, and production-completion branches add only their own EntityOfConcern, criterion or boundary, and branch-specific base.

One branch neither inherits facts from another nor turns the common method into an omnibus production object. Work identity, transformation identity, subject identity, evidence, assurance, delivery, acceptance, release, publication, and availability remain with their subject patterns.

A.15.PROD:4.1 - Split the three questions before recovering evidence

QuestionClaim contentOrdinary stopping resultWhat it does not establish
Production-work participationcurrentWork is productionWork, or currentWork is a declared proper work part of productionWorkone local positive or negative compound claim, or a work-grounding blockerentity inception, completion, delivery, acceptance, or a universal production-work kind
Entity-identity inceptionproducedEntity first satisfied the applicable productIdentitySpecification at inceptionBoundary. Attribution also identifies the governed effects of identityClosingWorkthe first time or a supported bound on it. When attributing inception, the supported Work claim or claims, or the missing groundproduction completion, later persistence, acceptance, or a reusable binary relation kind
Production completioncompletionSubject satisfies applicable productionCompletionCriterion at completionBoundary, and a separate declared closure predicate or local claim connects that satisfaction to productionWorkone state-satisfaction claim plus, when asserted, one historically indexed Work-completion claim; otherwise the closure blockerentity inception, delivery, acceptance, release, publication, or availability

The three claims may cite overlapping facts. They remain different claims because they answer different receiving questions and can have different boundaries, criteria, and truthful C.2.1 EntityOfConcern values.

A.15.PROD:4.2 - Recover the smallest base

The practitioner MUST use only objects needed by the selected branch:

Working nameObject and governorRequired contribution
productIdentitySpecificationone C.2.1 predicate-definition episteme whose subject pattern states the identity rule; any continuing-edition relation to another specification episteme is stated separatelystates the identity rule before inception without pretending that a future entity exists
identity-specification applicability basisone named applicability predicate with its participants and boundary facts, or one filled local compound claim selected under A.6.RCD disposition 2applies the specification episteme to the candidate basis, subject context, and candidate inceptionBoundary; it introduces no universal applicability relation
producedEntityone U.Entity, designated only after inceptionis the entity whose identity rule first became true
productionMethodone U.Method under A.3.1states the governed way of doing, intended production effect, applicability, and relevant identity or completion criterion meaning
currentWorkone Work individual admitted under U.Work by A.15.1designates the world-side dated occurrence; the grounding instructions below recover its basis
productionWorkone Work individual admitted under U.Work by A.15.1designates either the same occurrence as currentWork or the larger Work occurrence of which currentWork is a declared proper part
actualTransformationone or more independently identified U.Transformation occurrences under A.3.4names what changed without becoming the work or the produced entity
work-to-change basisone named domain predicate with Work and transformation participants and obtaining case facts, or one filled local compound claim selected under A.6.RCD disposition 2establishes that selected changes are effects of work; coincidence is insufficient
completionSubjectthe state-bearing entity or continuing referent judged by the completion criterionkeeps the criterion’s subject explicit instead of applying a product-state test to Work
productionCompletionCriterionone C.2.1 predicate-definition episteme whose subject pattern states the state-satisfaction rule; any continuing-edition relation to another criterion episteme is stated separatelystates what state of completionSubject counts as satisfying the production requirement at the candidate boundary
production-work closure governorone declared subject predicate or one filled local A.6.RCD claim that connects criterion satisfaction for completionSubject to closure of productionWork at the boundarystates why the Work is complete; criterion satisfaction alone does not supply this link
local assertionone C.2.1 epistemecarries only the state-satisfaction claim or the production-work-completion claim needed by the selected question

For currentWork, recover every performer through A.13, then let A.15.1 independently admit the Work from its history, at least one obtaining enactsMethod relation, extent, and at least one obtaining locally declared containing-system relation.

When this production claim also consumes assignment-bound attribution, reuse the already grounded A.13 assignment occurrence and its directly declared species, then test the separate F.6 relation through that same assignment.

Missing or failed F.6 alone preserves independently admitted Work. If the same finding questions an admission premise, recheck that premise and its dependent claims.

Name an additional enactment, binding, resource-use, or affected-referent relation only when the production claim uses that independently obtaining fact; none is a field stored in the occurrence.

A neighboring object enters only when a named predicate or filled local claim connects it to the selected Work, entity, or claim and omitting that connection would change the named action or decision. Otherwise keep method descriptions, work plans, objectives, commitments, product specifications, evaluation results, and E.24.PUB publication occurrences, forms, and carriers separate. None is constitutive of every production occurrence.

A.15.PROD:4.3 - Select one production-work branch

Whole-work branch. currentWork = productionWork is admissible only when that dated Work enacts productionMethod; the method states its intended production effect; a named applicability claim applies the method to this case’s inputs and conditions; the named work-to-change predicates obtain for the Work and transformations; and the identity or completion criterion that decides the selected question is named and applicable.

A familiar broader production label establishes no parent work.

Proper-part branch. currentWork is admissible as a proper part of productionWork only when OperationalPartOf_work or another A.15.1 work-part relation with fitting occurrence semantics obtains. Interval overlap or concurrency is asserted separately and establishes neither parthood nor coordination.

The containing Work must likewise enact the production method; the method must state its intended production effect; a named applicability claim must apply it to the containing case; the named work-to-change predicates must obtain; and the identity or completion criterion that decides the selected question must be named and applicable. A shared label, project membership, common referent, temporal containment, overlap, or adjacency in a plan establishes no work parthood.

The two branches can support different bounded uses. A nut-fastening occurrence can be the whole production work for a narrowly bounded finishing operation and also a proper part of a larger car-production occurrence, provided each local claim names its extent, criterion, and work relation. productionWork is a relation-defined reading of one Work occurrence admitted under U.Work, not an intrinsic kind.

A.15.PROD:4.4 - Ground actual effects without inventing transformation composition

The practitioner MUST first recover every transformation independently through A.3.4: changed referent, exact extent or formal boundary, boundary conditions, before/during/after facts, and continuity or reidentification rule. The practitioner MUST then name the declared domain predicate for each Work-to-transformation pair, state its participant order, and show the case facts that make it obtain.

If no one direct predicate suffices, use a local compound claim selected under A.6.RCD disposition 2 only when its constructor, governed base predicates, participants, and case facts are recoverable.

If neither a direct governor nor a sufficient compound-claim rule exists, keep the Work and transformation separate and return missing-governor[work-to-change]. If a governor exists but a deciding case fact is unavailable, return missing-information; if the available basis is sufficient and the positive test fails, return factually unsupported.

A negative conclusion additionally needs the governor’s applicable non-obtaining criterion or complete closure basis.

Temporal overlap, a common changed referent, a delta expression, a log record, or a post-state picture may supply evidence for those facts; the declared predicate or compound claim and its obtaining facts establish the link.

One transformation identified at the resolution needed by the production claim establishes neither presence nor absence of finer transformation parts. Work parts, method parts, samples, temporal subdivisions, concurrent changes, and flow representations do not establish transformation parts or a composite transformation.

If the selected production claim uses only independently identified transformations, continue without a composition claim. If it asserts positive composite-transformation identity, transformation parthood, or transformation holonhood and no accepted governor supplies that basis, return the missing-governor blocker. Composite identityClosingWork under A.15.1 does not cure that blocker and does not imply an isomorphic composite transformation.

A.15.PROD:4.5 - Recover entity-identity inception

Definition: A15PROD-D1 (Entity-identity inception). Entity-identity inception is the boundary at which producedEntity first satisfies the identity rule stated by productIdentitySpecification and a named applicability predicate or filled local claim applies that specification to the candidate basis, subject context, and boundary.

Plain: when this entity first exists. inceptionBoundary is a case-local boundary designator, not a second technical term, claim kind, or relation kind.

For a question about time, recover the applicable identity rule, its candidate basis and the period that could contain first existence. Establish that the rule held at the proposed boundary and that every earlier admissible boundary is excluded. A complete history of the relevant state can establish this time even when the worker is unknown. If only a later satisfying state is known, report existence by that time. When the recipient asks for the Work that brought the entity into existence, complete the following five steps:

  1. recover productIdentitySpecification as one C.2.1 predicate-definition episteme in the subject pattern that states the identity rule.

    Before inception, the governed question remains about work, method, effects, that specification episteme, and its candidate basis; no future producedEntity participant exists;

  2. recover the named applicability predicate or filled local claim that applies that specification episteme to the candidate basis, subject context, and candidate inceptionBoundary, together with the effects of work and the declared links by which those effects bear on that rule;

  3. find the earliest inceptionBoundary at which the rule in that applicable specification episteme becomes true and designate the resulting producedEntity only on the after-side of that boundary; the pre-inception candidate basis remains distinct from that entity;

  4. identify identityClosingWork, using the one closing work occurrence when it exists or, for jointly necessary concurrent or nested work parts, their composite work under A.15.1 and its declared work-part relations; and

  5. state a positive local inception claim only after producedEntity exists and the claim names productIdentitySpecification, its named applicability predicate or filled local claim, identityClosingWork, inceptionBoundary, and all declared Work-to-change and change-to-identity predicates or compound bases.

    Identify its C.2.1 episteme when a receiving use needs the separately referable claim. Add an E.24.PUB occurrence only when a receiving use also needs that episteme to be available through a named form or carrier.

A local inception claim MUST be indexed by the specification episteme and applicability basis used at inceptionBoundary. A later specification episteme does not silently rewrite that earlier claim.

If a C.2.1 EpistemeEditionRelation connects the two specifications, the lineage can trigger refresh of a current dependent use, but the later specification needs its own applicability basis at the boundary being judged.

When that relation is unestablished, leave continuity unresolved and evaluate the later specification’s applicability independently. Call it non-continuing only when the applicable continuity rule supports that negative result.

Changed applicability yields either a separately qualified claim under its new basis or a blocker; it does not move the earlier indexed boundary.

Supporting material, whether a representation, plan, record, rule episteme, or observation, enters one of the five steps only through its declared relation to that step; it does not replace the required Work, applicability, effect, or boundary predicate. Absence of recoverable work granularity for identityClosingWork yields a work-granularity blocker. Several incomparable minimal work composites yield several local inception claims and remain plural unless a separate selection rule applies.

Regulated-identification boundary. Identifier allocation and entity inception are separate claims. If the applicable subject-identity rule makes allocation constitutive, apply that rule. When a practice keeps allocation at build or registration separate from entity status, the identifier supplies designation and continuity only. First existence then requires a separate applicable identity rule; its absence yields the identity-governor blocker.

A.15.PROD:4.6 - Recover state satisfaction and historically indexed production completion

Completion wording often hides two claims. First ask whether the state-bearing subject satisfied the applicable criterion. Then ask whether the subject practice makes that satisfaction sufficient to close the production Work.

The state-satisfaction claim names:

  • completionSubject whose state is judged;
  • completionBoundary;
  • productionCompletionCriterion episteme applicable to that subject and boundary;
  • the named applicability predicate or filled local claim; and
  • the boundary-state facts and the criterion predicate they satisfy.

When persisted, this C.2.1 episteme has completionSubject as its EntityOfConcern. It says nothing yet about whether Work is complete.

The separate production-work-completion claim names productionWork, the state-satisfaction claim, the same boundary, and the declared closure predicate or filled local A.6.RCD claim that makes this criterion satisfaction sufficient to close that Work. Its EntityOfConcern is productionWork.

If no closure governor is available, keep the positive state-satisfaction claim and return missing-governor[production-work-completion]; do not apply a subject-state predicate to Work by metonymy.

Index every historical state-satisfaction and Work-completion claim by its criterion episteme, applicability basis, boundary, and boundary-state facts.

Later damage, loss, destruction, delivery, rejection, acceptance, release, publication, or unavailability receives a separate claim. Rework or later production Work that closes under an applicable criterion at a later boundary receives another local Work-completion claim.

Entity-identity inception, criterion satisfaction, and production-Work completion remain separate even when they share a boundary. A later evaluation-result episteme may support one of these claims under a direct evidence-use relation; the branch’s declared predicates and facts establish its boundary, subject state, and Work closure.

Past Work and the two completion claims remain addressable after later destruction or evidence decay. A later assertion carries its own evidence currentness and reliance status. The produced entity, measurement or evaluation result, delivered entity, acceptance verdict, release, publication, availability, and downstream effect remain objects and claims defined and tested separately.

Practice-specific criteria stay local. NASA systems-engineering guidance, Scrum’s Definition of Done, and similar authoritative practice sources can supply a criterion for the subject and practice use they address.

A.15.1 Work identity and a subject-practice closure predicate or local claim separately establish whether criterion satisfaction closes that Work. Transition, delivery, review, and release retain their own claims.

A.15.PROD:4.7 - State one local claim and stop

The default A.6.RCD disposition is local compound relation-bearing claim. For an ordinary positive answer, the practitioner MUST:

  1. name the receiving action or decision, state what it must decide, and select one production question;
  2. recover the participants, direct predicates, applicability facts, and boundary facts needed by that question;
  3. state the smallest readable conjunction of those governed facts and the one answer it supports, or return the missing-information, missing-governor, criterion, applicability, work-granularity, or boundary-state blocker; and
  4. keep any durable answer in one truthful C.2.1 episteme with claim content, one EntityOfConcern, and an effective reference scheme, then stop without introducing a relation kind, relation signature, or relation occurrence.

This ordinary positive branch does not require the practitioner to name a substrate document, constructor, hidden-witness policy, polarity algebra, or ordered-boundary operator. It requires the governed facts and a readable answer.

Open author-side semantic replay only when A.6.RCD:4.2 requires a substrate pin—nontrivial, interoperability-facing, proof-bearing, high-consequence, or reusable use—or when the current negative claim or first-satisfying-boundary claim depends on negation, witness, ordering, or earliest-boundary semantics.

Branch constructor semantics for the triggered replay. These are branch-local claim constructors, not a universal production algebra:

BranchLeast constructor over governed base claimsHidden-participant, polarity, and time policy
production-work participationone typed conjunction over A.15.1 work identity, actual method enactment, method applicability and intended production effect, affected referent, direct work-to-change facts, the receiver’s current criterion, and either work identity or one A.15.1 proper-part relationevery participant and conjunct remains named; no projection hides work, transformation, or criterion witnesses; a negative result requires the selected substrate’s explicit negation law rather than absence of a base assertion
entity-identity inceptionselect the first boundary satisfying the applicable identity rule over the declared ordered domain. For attribution, include the Work, its governed effects and the Work-to-change and change-to-identity links that establish which Work brought this first satisfaction aboutthe candidate basis remains distinct from the after-side entity; work parts and actual transformations remain named or follow the substrate’s explicit witness policy; incomparable minimal work composites remain plural, and A.15.PROD supplies no arbitrary minimization rule
production completionone boundary-indexed conjunction first states criterion satisfaction for completionSubject; a second conjunction states productionWork, that satisfaction claim, and the declared closure predicate or local closure rulethe claims keep their different entities of concern; no earliest-boundary operator is implied unless separately required, and missing closure semantics preserves satisfaction while blocking only Work completion

For DPF or FPF authoring and every other pin-triggering use, the responsible author or modeler MUST name the selected substrate and edition and replay its constructor inputs, output claim, applicability, hidden witnesses, polarity law, and temporal policy.

A negative or earliest-boundary claim MUST recover the negation, witness, ordering, or selection semantics it consumes even when no broader replay is needed.

If no current substrate supplies semantics that the claim requires, return the missing-substrate blocker. A.15.PROD supplies no fallback operator.

For an ordinary positive result, the EntityOfConcern is currentWork for production-work participation and producedEntity for entity-identity inception. Completion uses completionSubject for the state-satisfaction episteme and productionWork for a separate Work-completion episteme.

A modeler MUST split claim content that cannot truthfully concern one entity and MUST NOT manufacture a union concern from work, method, transformations, criteria, evidence, and receivers.

A named use of reusable predicate semantics may justify one predicate-definition episteme, with the subject pattern locating its defining ClaimGraph.

Consider a subject-specific derived relation kind when a named use consumes occurrence identity. The subject definition must then state obtaining, applicability, base dependencies and occurrence identity, adding recurrence, cessation and continuation conditions when those distinctions matter. A.6.RCD defines that candidate-construction branch; A.15.PROD defines no such kind admission by itself.

A.15.PROD:4.8 - Separate recognition from assurance

Recognition branch for ordinary work. Use the three questions in section 1, the branch outcomes in section 4.1, and the ordinary claim rule in section 4.7. Stop with one readable answer or blocker; open only the semantic replay needed for a negative claim, an earliest-boundary judgement, or an A.6.RCD:4.2 substrate pin.

Assurance branch for authors and high-consequence use. Replay the basis in six visible groups:

  • Work and Method. Check work identity and every relied-on work-part relation, the actual enactsMethod relation, method applicability, and the intended production effect.
  • Actual change and entity inception. Check every work-to-change and change-to-identity predicate and retain the explicit non-inference from work or method composition to transformation composition.
  • State satisfaction and Work closure. Check every criterion-applicability fact and boundary-state satisfaction fact. Keep the state-satisfaction claim separate from the closure predicate or local claim that closes the Work.
  • Claim epistemes and their current basis. Check the identity-specification and completion-criterion epistemes, the named applicability predicate or filled local claim for each episteme at its claimed boundary, any separately current C.2.1 EpistemeEditionRelation, C.2.1 identity, and the evidence-use relations relied on.
  • Deciding premises. Check that each conclusion is supported by the premises it consumes. Use positive or discriminating cases when needed to establish or explain that dependence; reuse sufficient existing proof or verification.
  • Pinned author substrate. When A.6.RCD:4.2 requires a pin, DPF and FPF authors MUST record the selected substrate and edition and expose direct base predicates, applicability, hidden participants, polarity law, boundary domain and ordering, witness policy, and every earliest-boundary rule used by the claim.

Assurance may warrant reliance on the claim. Work, change, entity inception, and completion remain established by their branch predicates and obtaining facts.

Assurance scope by use. Replay only what the reliance consumes. For assurance of a model or declaration, check claim content, one truthful EntityOfConcern, reference scheme, participants, predicates, polarity, and boundary indexing.

A conformance use checks that the selected branch reaches one grounded answer or blocker and stops. Each assurance use assesses the stated claim; it neither widens that claim nor replaces the branch predicates and facts.

A.15.PROD:4.9 - Run the recovery sequence and stop

The ordinary sequence is section 4.7 applied to the selected branch. If several production questions are current, handle each as a separate claim. For production-work participation, choose the whole-work or proper-part branch in section 4.3; for inception or completion, use sections 4.5 or 4.6. Stop after the readable answer or blocker.

If later reuse needs a durable claim, identify its C.2.1 episteme; if the receiving use also needs availability through a form or carrier, establish the separate E.24.PUB occurrence.

Open delivery, acceptance, release, publication, availability, result, evidence, assurance, or relation-kind questions only when the named action or decision asks one of them; none follows from the production answer.

A.15.PROD:4.9.1 - Triggered author replay

Continue only for an A.6.RCD:4.2 pin-triggering use or when a negative or earliest-boundary answer consumes additional semantics:

  1. name the branch-local constructor and, when a pin is required, the substrate and edition; expose only the inputs, applicability, hidden-participant or witness policy, polarity law, boundary domain and ordering, and temporal rule that can change this answer;
  2. for entity inception, verify the ordered candidate-boundary domain and earliest-satisfying rule; for a negative claim, verify the applicable negation law; for completion, keep the claim indexed by its criterion, applicability basis, and boundary;
  3. if one required operator or substrate is unavailable, return the missing-substrate blocker rather than lowering the absence to a negative production answer; and
  4. stop after the author replay returns the same ordinary answer or blocker.

A.15.PROD:5 - Archetypal Grounding

The following constructed cases isolate the production questions under stated domain premises. The ReleaseBinary case exposes a complete build-to-inception basis; the other cases retain their named assumptions and conditional claims.

A.15.PROD:5.1 - Car 42 and the required nut

Identity boundary. Car 42 already satisfies its identity rule before NutFasteningWork-42.

Assignment declaration. Car42FasteningAssignmentSpecies is a directly declared U.SystemRoleAssignment species. Its ordered participant positions are holder and assigned system-role kind; their domains are U.System and Car42FasteningPerformerSystemRoleKindDomain.

Assignment occurrence rule. The species applies to fastening Car 42. It assigns Car42FasteningPerformerSystemRole when the cell designation and enabled fastening-control connection obtain. The kind’s criterion is condition-sensitive control of the specified fastener attachment; stipulated observations show that FasteningCell-7 satisfies it.

The designation and connection establish Car42FasteningAssignment-42 from 08:00 to 08:20 UTC on 27 August 2026. Holder, assigned-kind value and that uninterrupted interval identify the occurrence.

Work and Method basis. The common route in section 4.2 is instantiated here: A.13 recovers FasteningCell-7 : U.System through obtaining Car42FasteningAssignment-42. Its independent performance history places NutFasteningWork-42 from 08:05 to 08:10 UTC on that date, enacting the admitted Car42FasteningMethod, within admitted CarAssemblyService-42 under the declared FasteningWorkOccursWithinService@Car42 predicate. These facts and the A.13 core independently admit the Work under A.15.1.

Because this case consumes assignment-bound attribution, F.6 then relates the admitted Work through the same assignment.

Actual-change basis. A.3.4 separately identifies Car42FastenerAttachmentTransformation. It concerns the same continuing car and does not bring Car 42 into existence.

Whole-work branch for the narrow use. NutFasteningWork-42 can be the whole productionWork when its fastening method is applicable and FasteningWorkChangedAttachment@Car42(work, transformation) obtains for that Work and Car42FastenerAttachmentTransformation.

State satisfaction. At the fastening boundary, Car42FinishingStateSatisfactionClaim has EntityOfConcern Car42 and states that the car satisfies Car42FinishingCriterion-v1.

Work closure. Separately, subject-bounded Car42FasteningClosureRule-v1 supports Car42FasteningWorkCompletionClaim, whose EntityOfConcern is NutFasteningWork-42, because the required attachment state is satisfied and no required fastening activity remains for this narrow use.

Wider-work contrast. For the broader factory use, the same occurrence can be a proper operational part of CarProductionWork-42 under an A.15.1 part relation. The verb fasten and narrative order decide none of these claims.

Result and missing grounds. Applying section 4.7 to the case facts returns: this Work completed the required fastening for this use; Car 42 already existed. The case uses Car42FasteningPredicates-v1 for the Work-to-change predicate and Car42-Claims-v2 for the separate state-satisfaction and Work-completion claims.

If FasteningWorkChangedAttachment@Car42 is undefined, return missing-governor[CAR42-FASTENING-WORK-TO-CHANGE] and obtain its governing predicate before attributing the attachment change to this Work.

If Car42FasteningClosureRule-v1 is absent, preserve the independently grounded Car42FinishingStateSatisfactionClaim and return missing-governor[CAR42-FASTENING-WORK-COMPLETION]; obtain the completion rule before claiming that this Work completed the required fastening. These two missing grounds concern different claims.

A.15.PROD:5.2 - Incomplete but identifiable Ship 27

Identity rule and applicability. Ship-identity specification episteme SHIP-ID-2 states the hull-closure rule. Local applicability claim ShipIdentitySpecApplies-2 applies it to candidate hull basis Ship27-HullBasis, yard context Yard-27, and the ordered candidate boundaries ending at inceptionBoundary.

Entity inception before later Work ends. Hull-assembly work can close that specification’s rule at inceptionBoundary while outfitting, software installation, trials, and commissioning continue. The resulting inception claim concerns when Ship 27 first exists and remains indexed by SHIP-ID-2 and ShipIdentitySpecApplies-2.

Ordinary answer. Ship 27 first exists at inceptionBoundary under that specification and applicability basis; later Work continues, and production completion remains a separate question.

Continuing edition — assignment declaration. ShipIdentityRuleRevisionAssignmentSpecies is a directly declared U.SystemRoleAssignment species. Its ordered positions are holder and assigned system-role kind, with holder domain U.System and assigned-kind domain ShipIdentityRuleReviserSystemRoleKindDomain.

Continuing edition — assignment predicate. The assignment predicate applies to ship-identity revision in Yard-27. It obtains when the holder is designated to revise that rule and has the operative access needed for revision. ShipIdentityRuleReviserSystemRole requires controlled revision that preserves the declared identity claims and exposes a changed claim; the stipulated revision actions satisfy this criterion independently of Work admission.

The designation and access establish the assignment from 10:00 to 11:00 UTC on 27 August 2026. Holder, assigned-kind value, Yard-27 and that uninterrupted interval identify one occurrence.

Continuing edition — Work and Method. Applying the common route in section 4.2, A.13 recovers YardIdentityGovernanceSystem through obtaining ShipIdentityRuleReviserAssignment-2R, whose assigned-kind value is ShipIdentityRuleReviserSystemRole and whose interval covers the full Work. The independent revision history runs from 10:05 to 10:30 UTC in that interval, enacts the admitted ShipIdentityRuleRevisionMethod, and lies within admitted YardGovernanceService-27 under the declared IdentityRevisionOccursWithinService@Yard27 predicate. With the A.13 core, these facts independently admit ShipIdentityRuleRevisionWork-2R under A.15.1.

Because this branch consumes assignment-bound attribution, F.6 then relates the admitted Work through that same assignment.

Source expression and predicate. C.2.P recovers the source expression hull assembly closes Ship 27 identity in SHIP-ID-2. Predicate-definition episteme YardRevisionSourceUsePredicates-v1 declares case-local predicate usesAsRevisionSource(work, sourceEpisteme) with participant order <revision Work, source episteme>.

Source-use obtaining test. The predicate applies only to ship-identity revision Work under ShipIdentityRuleRevisionMethod. It is true only when that Method application opens the source episteme and uses the selected source claim as a premise.

Edition basis. The source-use participants are ShipIdentityRuleRevisionWork-2R and SHIP-ID-2. The revision Work opens SHIP-ID-2, selects its hull-closure claim as an explicit premise, and produces SHIP-ID-2R, whose separate C.2.1 ClaimContent says that hull assembly plus installed propulsion closes Ship 27 identity. Those facts make usesAsRevisionSource(ShipIdentityRuleRevisionWork-2R, SHIP-ID-2) obtain.

The applicable continuity rule for this specification family requires use of SHIP-ID-2, preservation of the same identity-rule definition as EntityOfConcern and of the listed identity claims, and explicit identification of the corrected claim content without a reference-scheme retargeting. The current source use and preserved and deliberately changed features satisfy that rule, so ShipIdentitySpecEdition-2-to-2R : EpistemeEditionRelation obtains for SHIP-ID-2 and SHIP-ID-2R.

The performer, Method, Work, provenance, and replacement facts supply evidence for the test; no label makes continuity true. The lineage carries forward neither old applicability nor a new inception boundary.

Lineage blockers. Keep the two failures distinct:

  • If the source-use predicate is not defined, return missing-governor[SHIP-IDENTITY-REVISION-SOURCE-USE].
  • If its definition is current but the premise-selection facts cannot be recovered, return missing-information[SHIP-IDENTITY-REVISION-SOURCE-USE].

Either result keeps SHIP-ID-2R usable as a separately identified specification episteme but leaves ShipIdentitySpecEdition-2-to-2R unestablished. A similar title, later date, common publisher, or bare provenance edge does not restore that lineage.

Unestablished continuity. SHIP-ID-3 is another specification episteme, but this case establishes no EpistemeEditionRelation from SHIP-ID-2 or SHIP-ID-2R to it. That leaves continuity unresolved; it does not establish a negative result. A later date, similar ship terminology, and use by the same yard do not make it an edition.

A use selecting SHIP-ID-3 must establish its applicability independently and constitute a separately qualified C.2.1 claim or return the blocker; lineage-based refresh cannot substitute it for either earlier specification.

The continuing edition reopens dependent current uses through the named lineage. A separately identified specification with unresolved continuity needs its own applicability basis without altering earlier claims.

Author-side substrate. Substrate edition YardIdentityHistory-v3 defines time-indexed conjunction over the named work, applicability, actual-effect, work-to-change, change-to-identity, and identity-satisfaction claims. It also defines earliest selection over its declared ordered candidate-boundary domain.

The positive replay returns boundary tI because the identity predicate stated by SHIP-ID-2 is false at every earlier candidate boundary and true at tI. Work and transformation witnesses remain named.

Nearest substrate failure. A snapshot substrate can conjoin facts at tI but supplies no ordered boundary domain or earliest-selection law. It cannot establish inception even if a later image satisfies the rule, so the branch returns the missing-substrate blocker rather than treating first observation as first existence.

The example adds no universal earliest operator or arbitrary minimal-work selection.

Designation is not identity. The cited IMO integrated scheme uses an IMO ship identification number as a stable designator across later flag, name, ownership, or type changes and states that allocation does not define ship status. Ship identity and continuity therefore require their applicable subject rules.

If the receiving use cannot recover a separate ship-identity rule for this candidate basis and boundary, the inception branch returns the identity-governor blocker.

Larger Work. A larger production-work occurrence contains the identity-closing and later Work through declared A.15.1 part relations.

State satisfaction. At completionBoundary, one claim may state that Ship 27’s state satisfies the applicable completion criterion.

Work closure. A separate yard closure predicate or local claim must connect that satisfaction to completion of the larger production Work. Without it, preserve the state claim and return missing-governor[SHIP27-PRODUCTION-WORK-COMPLETION].

Delivery, class acceptance, and operational release remain separate. The sentence the yard produced Ship 27 is admissible only after the writer selects Work participation, first existence, state satisfaction, or Work completion.

A.15.PROD:5.3 - Nested and concurrent attribution

Recover the joint contribution. Begin with the identity rule for the particular product. Suppose the rule for a release requires the accepted bytes and a valid signed manifest for those same bytes in the store. Establish which Work supplied each and when the two conditions first held together. Identical service names and execution times could accompany a manifest for another build. That manifest would leave the rule unsatisfied. If both contributions were needed and both were performed within this production Work, identify the relevant composite under A.15.1. If an accepted manifest was already available and was reused, its availability contributes to the result. Attribute a new manifest-producing Work to this execution only on evidence that it occurred as part of it.

Plural minimal composites. Two incomparable minimal work composites yield two local inception claims, each indexed by its identity-specification episteme and applicability basis. Nested or concurrent attribution creates no additional inception occurrence, and none of those work compositions establishes transformation composition.

Epistemic basis remains separate. The identity-specification and completion-criterion epistemes remain cited by the local claims. Each applicability basis remains its named predicate or filled local claim, and any C.2.1 edition relation between such epistemes is separate. None is a work participant.

A.15.PROD:5.4 - Pressure adjustment without entity inception

Work, Method, and change. A dated pressure-adjustment Work occurrence may enact a pressure-adjustment method, while A.3.4 independently identifies a pressure transformation.

Work-to-change claim. Use the direct subject predicate or a sufficient local compound rule relating the Work and transformation. When its applicability conditions and case facts establish the relation, state the positive claim.

If neither rule is available, keep the two occurrences separately identified and return missing-governor[pressure-work-to-change]. An unavailable deciding fact yields missing-information; under an applicable rule, sufficient facts that fail the positive test yield factually unsupported. Report known inapplicability separately.

A negative claim additionally needs the applicable non-obtaining criterion or complete closure basis under §4.4.

Stop. If the affected vessel or process already exists and no production-completion criterion is current, the result records the Work, the transformation, and their obtaining Work-to-change predicate. The production-work-participation, entity-inception, and completion branches remain unopened.

A.15.PROD:5.5 - PumpSkid assembly before PumpSkid identity

Actual Work and change. Mounting, wiring, fluid-connection, and whole-configuration changes may each be independently identified under A.3.4, and work parts may be grounded under A.15.1.

Inception basis. Apply the PumpSkid identity rule to the candidate configuration at the relevant boundaries. To date first existence, establish the first satisfaction within the stated history or report the bound that history supplies. To attribute inception to the named assembly Work, also establish its relation to the changes and their role in first satisfying the identity rule. If those links remain open, retain the supported timing conclusion.

Transformation-composition boundary. A claim that additionally requires positive composite-transformation identity or transformation parthood stops at missing-governor[transformation-composition]. Work or method decomposition supplies no proof of transformation decomposition.

A.15.PROD:5.6 - Completion persists after later destruction

Historical positive case. The product’s state satisfied criterion episteme PC-3 at boundary tC, and the subject-practice closure rule made that satisfaction sufficient to close the named production Work.

CompletionHistory-v1 keeps the Work identity, applicability of PC-3, subject-state facts at tC, state-satisfaction claim, and separate Work-completion claim explicit. The two claims keep their different entities of concern. The history uses the declared boundary and does not apply an earliest operator.

Record a later accident and destruction in separate claims while retaining the historical claims at tC.

Nearest historical failure. Keep the later certificate or an unindexed current-state predicate, but remove the semantics that say the subject satisfied PC-3 at tC. The historical check then returns the missing-substrate blocker; neither the certificate nor the current-state predicate supplies the missing boundary-indexed satisfaction or Work-completion basis.

If only the closure rule is missing, the state-satisfaction claim remains and only Work completion returns its missing governor. Current evidence, availability, replacement Work, acceptance status, and insurance decisions remain separate.

A.15.PROD:5.7 - Non-agentive biological synthesis

Actual transformation. A spontaneous reaction or biological growth process may be independently grounded as one or more actual transformations under A.3.4. The transformed referent may be a U.System; the performer question remains separate.

Performer and Work result. Apply the common route in section 4.2. A production-through-Work claim opens only after A.13 recovers every performer and A.15.1 independently admits dated Work with an applicable enacted Method. This case stipulates neither basis, so it retains the referent and transformations and returns the performer/Work blocker.

Assignment-bound attribution and F.6 are additional only when the receiving use consumes them; their absence is not itself a Work-membership failure.

The identity rule and history can date first existence or bound it. Apply the state criterion to dated facts about the batch to establish when it met the condition, or the bound on that time that the facts support. Closing production Work requires an applicable closure rule and the Work to which it applies. Attribute the growth to a particular performer only when the relevant performance and its effect have been established.

A.15.PROD:5.8 - Scrum Increment before review or release

Product-state and identity basis. The Scrum Guide and one organizational Definition of Done episteme are authoritative practice sources for this bounded software-product use. When PBI-84 first satisfies that criterion at tD, the local product-state and Increment-identity claims may be stated under their applicability rules. Work that does not meet that Definition of Done is not part of the Increment.

Review and release stay separate. Multiple Increments may exist before Sprint Review, and review is not a release gate.

A.15.PROD use. The pattern may use the applicable Definition of Done for the state-satisfaction or identity question it answers, while keeping Sprint Review, delivery, and release separate.

Work-completion boundary. The guide does not identify A.15.1 Work, its performer basis, or a local predicate that makes satisfaction close that Work. A Work-completion claim therefore needs an additional subject-practice closure governor.

Otherwise keep the product-state claim and return the Work-completion blocker.

A.15.PROD:5.9 - ReleaseBinary 12: complete build-to-inception replay

BuildOps asks when ReleaseBinary_12 first existed. A production reviewer additionally asks which build Work brought it into existence. The identity rule and the history of its satisfaction answer the first question. The second also requires a connection between the effects of this build and the first satisfying state.

Ordinary answer. The runner performed the named Work under the applicable build Method. The named Work-to-change predicate connects that Work to the store-population transformation, and the named change-to-identity predicate says that the transformation made the applicable binary-identity rule become true first at 09:11. Therefore ReleaseBinary_12 first exists at 09:11 through this build Work; decide completion and later uses separately. The table below supplies the assurance basis for that answer.

Needed factCase fact
Work, performer, and methodApplying the common route in section 4.2, A.15.1:6.7.1 first reuses BuildRunner_A : U.System’s A.13 core for this action, including the direct assignment species and obtaining occurrence BuildRunnerAssignment_2026-07-21; A.15.1 then independently admits ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work from its performance history, enacted Method ReproducibleBuild@BuildOps-v12, interval 09:00–09:12, and the obtaining BuildWorkOccursWithinServiceBoundary relation to BuildService_A. Because this case claim consumes attribution under that assignment, F.6 then establishes the relation. The enacted Method states the intended effect of producing an immutable binary. Method-applicability claim ReproducibleBuildApplies-12 applies that Method to build input and configuration BuildInputSet_12.
Application and candidate basisAfter the produced entity exists, A.6.1 application BuildApplication_12 has result binding builtBinary -> ReleaseBinary_12; that binding designates the returned entity but establishes neither its inception nor its boundary. The same identified application is an application of declared operation storeWrite@BuildOps-v12 and has argument binding storeTarget -> ArtifactStorePartition_12; A.15.1:6.7.1 uses this application and binding in the obtaining test for the named Work-to-transformation predicate below. Before inception, BuildOutputBasis_12 designates the candidate bytes, manifest, digest, and their positions in that partition, not a surrogate future binary.
Actual transformationA.3.4 independently identifies the one transformation consumed here: ArtifactStorePopulationTransformation_12 : U.Transformation, the change of ArtifactStorePartition_12 from no complete candidate tuple at 09:00 to the written bytes, manifest, and digest at 09:11, after which that tuple remains fixed through build completion at 09:12.
Work to changeA.15.1:6.7.1’s BuildOps relation specification declares BuildWorkPopulatedStore@BuildOps-v12(work, transformation) with participant order <work, transformation>. Its stated test and the stipulated Work, application, target-binding, and transformation facts make BuildWorkPopulatedStore@BuildOps-v12(ReleaseBinary12_BuildWork_2026-07-21T0900_0912, ArtifactStorePopulationTransformation_12) obtain. Shared timing or the result binding alone would not establish this predicate.
Identity criterion and applicabilityPredicate-definition episteme ReleaseBinaryIdentitySpec_v12 says that this BuildOps binary exists when one immutable byte sequence, manifest, and digest are fixed together and addressable by that digest in ArtifactStorePartition_12. Applicability claim ReleaseBinaryIdentitySpecApplies-12 applies that episteme to BuildOutputBasis_12, the BuildOps-v12 context, and the ordered candidate boundaries from 09:00 through 09:12. This is the criterion episteme for the selected inception question; BuildCompletionCriterion_v12 belongs to the separate completion question at 09:12.
Change to identityBuildOps predicate-definition episteme ReleaseBinaryIdentityPredicates-v12 declares case-local predicate StorePopulationClosedBinaryIdentity@BuildOps-v12(transformation, identitySpecification, candidateBasis, boundary, producedEntity) with that participant order. Its test requires that the applicable identity rule did not hold at any earlier admissible candidate boundary and that the governed store change brought about its first satisfaction at the named boundary. The stipulated case facts make it obtain for <ArtifactStorePopulationTransformation_12, ReleaseBinaryIdentitySpec_v12, BuildOutputBasis_12, 09:11, ReleaseBinary_12>.
Local resultC.2.1 episteme ReleaseBinary12InceptionClaim has EntityOfConcern = ReleaseBinary_12 and states only that this entity first exists at 09:11 through the governed effects of ReleaseBinary12_BuildWork_2026-07-21T0900_0912 under ReleaseBinaryIdentitySpec_v12 and ReleaseBinaryIdentitySpecApplies-12. It asserts neither build completion nor verification, transfer, acceptance, release, deployment, publication, or availability.

Nearest failing variant.

Keep every fact above, including the result binding, store transformation, work-to-change predicate, identity specification, applicability, ordered boundaries, and the state that satisfies the identity rule at 09:11. Remove only the declaration and obtaining fact for StorePopulationClosedBinaryIdentity@BuildOps-v12.

The remaining state evidence establishes that ReleaseBinary_12 existed by 09:11 under the applicable rule. If independent records also exclude every earlier candidate boundary, BuildOps can still give 09:11 as the first time. If the earlier exclusions depended on the removed evidence, the exact first time remains open. For the separate attribution through this change the return is missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY] for <ArtifactStorePopulationTransformation_12, ReleaseBinaryIdentitySpec_v12, BuildOutputBasis_12, 09:11, ReleaseBinary_12>.

Author-side replay of the same result. Case substrate ReleaseBinaryInceptionClaims-v1 defines a time-indexed conjunction over the named Work, performer basis, method applicability, the performed storeWrite application fact (not the later result binding), affected referent, transformation, work-to-change predicate, identity specification, applicability claim, and change-to-identity predicate.

Its declared ordered boundary domain is 09:00-09:12, and its earliest-satisfying rule returns 09:11. The positive replay therefore yields ReleaseBinary12InceptionClaim.

In the failing variant this constructor lacks the change-to-identity conjunct and returns missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY] for the claim attributing inception to the build Work. The independent time conclusion retains the extent supported by the state history. These case-local predicates and this substrate introduce no universal production, work-to-change, or change-to-identity relation kind.

A.15.PROD:6 - Bias-Annotation

Scope limitation. These annotations cover the three production-recovery branches and their named neighboring claims; they do not classify production language outside a current A.15.PROD use.

BiasCountermeasure
Verb biasThe countermeasure treats make, produce, build, finish, and complete as retrieval cues and selects one of the three questions by facts.
Record biasThe countermeasure keeps plans, logs, pictures, tickets, certificates, and publications as epistemic or publication objects until direct relations connect them to work, change, identity, or completion.
Final-step biasThe check rejects creation by last-visible-step order and replays the applicable identity-specification episteme, its applicability basis, and the work effects.
Container biasA project, factory, batch, case, or common referent supplies no proof of work parthood or production attribution.
Composition biasWork parts, method parts, samples, and flow structure supply no transformation-part inference.
Present-state biasThe check evaluates completion at its historical boundary under the criterion episteme used there, not only from the entity’s current state.
Universal-relation biasThe countermeasure prefers the local compound claim that answers the receiver over a broad production relation name.

A.15.PROD:7 - Conformance Checklist

CheckRequirement
CC-A15.PROD-1The receiving use selects production-work participation, entity-identity inception, production completion, or a subset. One branch conclusion is never another branch’s answer; shared facts support each branch only through its own predicate and applicability.
CC-A15.PROD-2currentWork and productionWork designate A.15.1 Work occurrences admitted under U.Work, not plans, labels, methods, logs, publications, or records that describe those occurrences.
CC-A15.PROD-3The whole-work branch names actual enactsMethod, method applicability and intended production effect, affected referent, work-to-change facts, and the criterion current for the receiver.
CC-A15.PROD-4The proper-part branch names an A.15.1 work-part relation and gives the containing work the same grounding required by the whole-work branch.
CC-A15.PROD-5Every actual transformation is independently identified under A.3.4; work, method, samples, temporal subdivision, and flow representations do not imply transformation composition.
CC-A15.PROD-6Every Work-to-change and change-to-identity link names a declared predicate with participant order and obtaining facts or a filled local A.6.RCD claim. Completion separately names the criterion-satisfaction predicate for completionSubject and the closure predicate or local claim for productionWork; neither substitutes for the other.
CC-A15.PROD-7productIdentitySpecification is identified as a C.2.1 episteme before inception without a surrogate future producedEntity; a named applicability predicate or filled local claim applies it to the candidate basis, subject context, and inceptionBoundary, and the entity is designated only after that applicable rule first holds. Publication availability, when required, is a separate E.24.PUB occurrence. Any claim that this is an edition of another specification names an obtaining C.2.1 EpistemeEditionRelation.
CC-A15.PROD-8A claim of first existence satisfies A15PROD-D1. Identify producedEntity, productIdentitySpecification, its applicability basis, inceptionBoundary and the grounds for first satisfaction there. If the claim also attributes inception to identityClosingWork, identify that Work and the effects that satisfy §4.5.
CC-A15.PROD-9Concurrent or nested identity-closing work is composed only through A.15.1 work-part relations; incomparable minimal composites remain plural, and each local inception claim retains its identity-specification episteme and applicability basis.
CC-A15.PROD-10A completion use first names completionSubject, criterion episteme, applicability, boundary-state facts, and state-satisfaction predicate. A separate Work-completion claim names productionWork and the closure predicate or local claim that makes that satisfaction sufficient to close it. Missing closure semantics blocks only Work completion.
CC-A15.PROD-11Historical state-satisfaction and Work-completion claims retain their criterion episteme, applicability basis, boundary, and boundary-state facts. Rework, a later criterion, damage, loss, delivery, acceptance, release, publication, or availability receives a separate claim.
CC-A15.PROD-12Each separately identified local assertion is one C.2.1 episteme with one truthful EntityOfConcern, claim content, effective reference scheme, and decided positive or negative polarity; no union concern is manufactured, and unresolved information sufficiency or reliance remains separately evaluated.
CC-A15.PROD-13An unresolved basis is returned as the missing-information, missing-governor, work-granularity, criterion, applicability, boundary-state, or transformation-composition blocker, not as a third predicate value.
CC-A15.PROD-14This pattern introduces no universal production relation kind, U.ProductionWork, relation signature, or relation occurrence and asserts no universal reducibility. A subject-specific candidate requires A.6.RCD when a named use consumes occurrence identity; its definition states obtaining, applicability, base dependencies and occurrence identity, with recurrence, cessation and continuation when relevant. A primitive candidate additionally demonstrates failed lossless derivation, one action-facing distinction every accepted derivation loses, and independent receiving uses.
CC-A15.PROD-15Recognition and assurance remain separate. Evidence and evaluation can support a branch claim; the branch predicates and obtaining facts establish Work, transformation, entity inception, or completion.
CC-A15.PROD-16The produced entity, measurement or evaluation result, delivered entity, acceptance verdict, release, publication, availability, and downstream effect remain distinct; each positive claim names its declared predicate or its own subject pattern, and a missing predicate returns the corresponding blocker.
CC-A15.PROD-17A practice-specific source is used only for the branch question it answers: a stable identifier alone does not establish entity status or inception; a systems-engineering realization criterion does not collapse transition into completion; and a Scrum Definition of Done does not supply work identity, effects, review, or release.
CC-A15.PROD-18An ordinary positive local claim names its governed base facts, the Method and/or criterion applicability consumed by its branch, readable conjunction, answer, and stop without requiring a substrate document. A pin-triggering use names the substrate and edition and replays only the constructor semantics it consumes. A negative or earliest-boundary claim exposes its polarity, witness, boundary-domain, ordering, or selection law; unavailable required semantics returns the missing-substrate blocker.

A.15.PROD:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Every work-caused transformation is productionModification of a continuing entity is treated as entity creation or completed production.The repair first recovers work plus actual change and opens only the production question needed by the receiver.
The final visible step created the productNarrative order substitutes for first satisfaction of the applicable identity-specification episteme.The repair recovers identityClosingWork, actual effects, the specification episteme, its named applicability predicate or filled local claim, and the earliest satisfying boundary.
Plan or log as production workIntended or recorded material is treated as the dated occurrence.The repair recovers A.15.1 work and relates plan, log, and evidence separately.
Shared label as work parthoodTwo occurrences called assembly are treated as parent and part.The repair states the A.15.1 work-part relation or keeps the occurrences separate.
Work parts imply transformation partsComposite work is used as proof of a composite transformation.The repair keeps transformations independently identified and returns the missing transformation-composition governor when needed.
Completion equals acceptanceA later customer or regulator verdict is used as the production-completion criterion.State completion at its historical boundary and govern acceptance separately.
Current damage erases completionPresent nonconformance is used to deny an earlier satisfied criterion.Keep the earlier claim indexed by its criterion, applicability basis, boundary, and boundary state; state the later transformation separately.
One omnibus production epistemeWork, inception, completion, delivery, and evidence are put into one claim with a union concern.The repair splits one local C.2.1 episteme per selected question and neighboring claim.
Relation-name escalationFamiliar production wording is promoted to a universal relation kind.The repair stops at A.6.RCD disposition 2 unless the named use of reusable predicate semantics or occurrence identity justifies the corresponding A.6.RCD continuation.

A.15.PROD:9 - Consequences

BenefitsTrade-offs and mitigations
Production attribution becomes replayable at work boundaries.More than one local claim may replace one familiar sentence; the three-question first move keeps ordinary use short.
Entity first-existence and production completion no longer overwrite each other.The added cost is one identity-specification or completion-criterion episteme and its applicability basis for each current claim; name a separate C.2.1 edition relation only when lineage is current. Reuse the specification episteme already identified by the subject pattern instead of copying it.
Narrow and containing production work can coexist without a new kind.Absence of work mereology yields an unresolved work-granularity blocker.
Historical completion survives later change while current evidence remains refreshable.Boundary truth and present reliance stay separate; the patterns governing evidence and refresh define or constrain current reliance.
Missing transformation composition no longer blocks independent production claims.A composition-dependent claim stops at a blocker; independently identified transformations and blockers remain useful results.

A.15.PROD:10 - Rationale

Production-work participation, first existence and completion can concern different entities, predicates and boundaries. A branch-local claim connects the declared predicates and obtaining case facts needed by one receiving question. The bases differ across manufacturing, construction, biology, software and epistemic production; naming those bases preserves the domain distinctions and locates a missing predicate. A subject-specific use requiring another relation follows A.6.RCD.

Use A.6.RCD when a named use needs reusable participant meanings or relation-occurrence identity. Predicate reuse alone stops at a reusable predicate-definition episteme. A derived-kind candidate additionally states obtaining, applicability, base dependencies and stable occurrence identity, with recurrence, cessation and continuation when relevant. A primitive candidate additionally requires failed lossless derivation, one action-facing distinction lost by every accepted derivation, and independent receiving uses. This pattern neither forbids nor admits a subject-specific derived or primitive relation kind.

The three-question split also preserves temporal distinctions. Work may begin before an entity exists and continue after it first exists. Completion may occur at inception or later. Delivery, acceptance, release, publication, and availability may occur later still. Keeping each boundary and criterion separate gives practitioners useful historical claims without treating every neighboring event as part of production identity.

A.15.PROD:11 - SoTA-Echoing

Scrum, NASA systems-engineering guidance, and IMO regulation are authoritative practice or regulatory sources for their named local questions. They are not treated here as SoTA merely because they are official or widely used. Manufacturing-information, product-information lifecycle, event-log, constructional-ontology, and provenance sources remain bounded comparators. None supplies a universal production ontology or a cross-domain answer to every A.15.PROD branch.

The Method combines Work identity and parthood with separate identity and completion rules supplied by the subject practice. The sources below contribute local criteria, designations or information distinctions; their authority within those uses does not establish one cross-domain production ontology.

Source, named branch question, and classificationAnswer carried into A.15.PRODUse and limit
Schwaber and Sutherland, The Scrum Guide, official edition 2020. Authoritative practice source for the bounded Scrum question.The guide makes the applicable Definition of Done the quality-state criterion, says that an Increment is born when a Product Backlog item meets it, excludes work that does not meet it, permits multiple Increments before Sprint Review, and says that review is not a release gate. The guide does not identify Work or provide the subject-practice rule that closes Work.Adopt for this bounded practice question, not as SoTA or a cross-domain production rule. The Definition of Done supplies only the branch-specific criterion; a Sprint, backlog item, Increment label, review, or release supplies neither the A.15.1 Work, its performer and effects, nor a universal production rule.
NASA NPR 7123.1D, Systems Engineering Processes and Requirements and the official NASA Systems Engineering Handbook product-realization guidance. Authoritative agency practice source family for its tailored realization question.The sources distinguish implementation or integration, verification, validation, and transition. The handbook also keeps a validated end product separate from its later transition to the next product layer or user. They do not identify the local Work or make criterion satisfaction close that Work.Adopt for the named NASA practice branch, not as SoTA or a universal completion rule. The tailored product-layer success, verification, or validation criterion can supply a local state-satisfaction basis; a validation report, transition record, or delivery is not the world-side boundary or the separate Work-closure governor.
IMO Resolution A.1215(34), Integrated IMO Identification Number Scheme and Circular Letter No.5096. Authoritative regulatory source family for ship designation.The cited scheme allocates an identifier at build or first registration, keeps it unchanged through the ship’s life, and says that allocation does not define ship status. It supplies neither an applicable identity rule nor inception or Work completion.Adopt the stable-designation boundary, not as SoTA or an identity-inception rule. The number can help reidentify Ship 27 but does not by itself make the hull basis the ship, locate first existence, or establish completion, delivery, or operational status.
IEC 62264-2:2026. Standard reference for the manufacturing-information question: which operations objects and relationships can an interface exchange?Sections 4.2, 4.6, and 4.8 keep work, actual resources, criterion or test content, boundary-state facts, records, and evaluation results separately recoverable; case 5.6 preserves an earlier completion claim after later destruction.Adopt and adapt as an information-interface reference, not a SoTA-bearing production-recovery answer. An exchanged operations object, record, test result, or work definition establishes neither a Work occurrence admitted under U.Work nor any work-to-change, inception, or completion fact by form.
Failla, Rossoni, Quirini, and Colombo, “Managing lifecycle of product information with an ontology-based knowledge framework”, 2025. Research proposal for the product-information traceability question.Sections 4.2 and 4.8 and cases 5.2 and 5.5 preserve traceability between product knowledge and a project instance while keeping templates, cloned information individuals, records, and the project-world entity distinct.Adapt for product-information lifecycle traceability, not physical or project-world inception. The paper does not supply A.15.PROD’s identity-specification applicability, earliest world-side boundary, work-to-change chain, or completion architecture.
IEEE 1849-2023 XES. Standard reference for the event-evidence interchange question.Sections 4.4 and 4.8 and the plan-or-log anti-pattern let logs and event streams support reconstruction while A.15.1 work, A.3.4 transformations, work-to-change facts, identity, and completion remain independently governed.Adopt for evidence interchange; reject as ontology. A logged event, timestamp, trace order, or extension attribute establishes neither a performed occurrence nor a causal, production, identity, or completion link by form.
Borgo and Righetti, “Towards Applied Constructional Ontology”, 2025. Ontology-design analogy about givens, constructors, dependence, mereology, and identity choices.The Rationale and the construction-label and composition anti-patterns retain only the caution that a chosen ontology construction or label does not settle a product-construction fact. The paper supplies no production-work, project-world inception, or production-completion practice answer.Retain as a limited design analogy, not SoTA-bearing product-construction evidence. Lexical proximity between constructional ontology and constructing products supplies no support for sections 4.3-4.6 or case 5.5.
The historical W3C PROV-DM Recommendation, 2013. Historical lineage for provenance generation and availability.Sections 4.1, 4.5, and 4.6 separate production-work participation, entity-identity inception, production completion, and later availability so each can have its own work, rule, boundary, and evidence.Reject wholesale; retain as lineage. PROV remains useful for provenance interchange, but its generation bundle is not imported as FPF’s universal production ontology.

The practical source-use result is visible in the Solution, checklist, and cases: the Scrum source supplies a bounded product-state criterion without collapsing review into release; NASA guidance distinguishes realization activities from transition; and IMO regulation supplies stable designation without status or inception. These are authoritative local constraints, not evidence that any one source is the best-known cross-domain production architecture.

A.15.PROD:12 - Relations

  • Builds on: A.13 for the performer; A.15.1 for Work identity, Work parts, concurrency, continuity, and independent Work admission; F.6 only for a production claim that consumes assignment-bound attribution through the same obtaining A.13 assignment; A.3.1 for the production Method, intended effect, and applicability; A.3.4 for actual transformations and the transformation-composition stop; C.2.1 for local claim and predicate-definition epistemes; and A.6.RCD for disposition, derivation, blocker, and subject-specific continuation.
  • Coordinates with: A.1 and the subject-specific identity owner; A.6.1 for an actual application and result binding without treating either as inception; C.2.P for source expressions; A.15.2 for plans distinct from Work; A.15.6 for project and process wording recovery; A.10 for an evidence-use or bounded-reliance claim; B.3 for assurance; E.24.PUB for availability through a publication occurrence, form, and carrier; and G.11 when a pinned definition, substrate edition, or applicability settlement changes.
  • Coordinates with: the characteristic-state, evaluation, completion-criterion, delivery, acceptance, release, availability, and refresh predicates or patterns selected by the current case.
  • Informs: production attribution, manufacturing and construction histories, biological and informational entity inception, rework analysis, product-lifecycle records, completion audits, and P2W or P2S continuation when the receiving action or decision asks one of the three recovered questions.

A.15.PROD:13 - Lowering, Repair, and Refresh Conditions

An ordinary production-work claim lowers when its Work, Method enactment, Method applicability, intended production effect, affected referent, Work-part relation, Work-to-change predicate or local claim, or the criterion and its applicability consumed by the receiver is missing.

An inception claim lowers when its identity specification and applicability, identity-closing Work, actual effects, Work-to-change and change-to-identity bases, or after-side entity cannot be recovered. A claim that this is the first satisfying boundary additionally needs an ordered candidate-boundary domain and an earliest-satisfying rule.

A completion use preserves a valid state-satisfaction claim whenever possible. That claim lowers only when its completion subject, criterion and applicability, boundary, boundary-state facts, or state-satisfaction predicate is missing. The separate Work-completion claim lowers when production Work or its closure predicate or local claim is absent; loss of that link does not erase the state-satisfaction claim.

An ordinary positive claim needs no materialized substrate document. A negative claim needs the selected substrate’s applicable negation law. A pin-triggering or earliest-boundary use needs only the constructor, witness, polarity, ordering, or time semantics it consumes; missing required semantics yields the missing-substrate blocker. A representation, record or publication may carry the required declared semantics or evidence. Its form or presence alone supplies no missing operator or rule.

A maintainer MUST repair only the affected local claim when later information changes work identity or parthood, a direct work-to-change fact, the identity-specification episteme or its applicability basis, the completion-criterion episteme or applicability relation, a boundary state, a relied-on base-predicate edition, or the selected substrate edition or constructor semantics.

An earlier inception or completion claim remains indexed by the specification or criterion episteme and applicability basis used at its boundary.

An obtaining C.2.1 EpistemeEditionRelation can trigger lineage-aware refresh of current dependent uses but does not rewrite that claim; a specification whose continuity is negative or unresolved needs an independent applicability judgement.

A later transformation, delivery, acceptance, release, publication, or availability claim does not by itself repair or invalidate an earlier production claim.

A relying practitioner MUST refresh an earlier claim after a change to its identity-specification episteme or applicability basis, completion-criterion episteme or applicability relation, any relied-on C.2.1 EpistemeEditionRelation, relied-on base-predicate edition, selected substrate edition, constructor semantics, witness or hidden-participant policy, polarity law, temporal policy, work-continuity policy, evidence basis, reference scheme, claim scope, or receiving use.

Follow an obtaining edition relation only to discover the continuing later episteme, then re-evaluate that episteme’s applicability for the current use.

A separately identified replacement with unestablished continuity carries no warranted lineage or inherited applicability; keep continuity unresolved until its rule decides it.

Refresh claim currentness and reliance separately from the historically indexed occurrence, specification or criterion episteme, applicability, and boundary facts.

A maintainer MUST reopen source binding only for the branch whose practice answer changed: a changed Scrum Definition-of-Done rule reopens the software-Increment branch; a changed NASA realization, verification, validation, or transition rule reopens the affected systems-engineering completion use; and a changed IMO identification rule reopens regulated ship designation and continuity, not a generic entity-inception claim.

A new source that answers cross-domain whole/proper-part production-work attribution reopens section 4.3 and the FPF synthesis hypothesis.

A changed comparator reopens only the information, evidence, analogy, or lineage boundary it supports unless a direct subject rule also changes.

A.15.PROD:End

A.16 - Language-State Moves: Choose the Next Publication and Use of a Cue or Claim

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain-name. Language-state move coordination.

Start here when. You have a cue or claim-bearing episteme and need to choose its next publication or use, including reopening or retiring it. For an early cue, preserve what is available without claiming that it already meets a downstream pattern’s entry conditions.

First useful move. Name the cue or current claim-bearing episteme and the intended next use. Then decide which identity case applies:

  1. a precursor cue or witness is being preserved in its first typed publication;
  2. the same episteme edition is being issued in another publication form; or
  3. changed C.2.1 identity content requires a separately identified successor episteme.

Choose one admissible move from §4.1 and make the content in §4.4 recoverable from its publication. Add a short move note when the existing material does not convey that content. Stop when the next use is supported; add history, Work, publication, rendering, or authority detail only when that use depends on it.

Typical next patterns. Use A.16.1 for early preservation, B.4.1 for route publication, B.5.2.0 for cue-derived abductive prompting, precision repair in A.6.P or C.16.Q, wording recovery in A.6.A followed by the recovered subject rule, and A.16.2 when the right move is reopen, backoff, respecify, or retire.

Not this pattern when. Use A.16.0 when history itself needs an accountable trajectory; use A.6.P or C.16.Q for their precision repairs and A.6.A to recover an ambiguous action-oriented claim or question; use E.18 only when the current subject is an independently selected TransformationFlowStructure, and E.18.2 for its mathematical description. For a known project-action question, use its subject pattern directly, such as E.11.PUR, A.15.5, A.15.1, or A.15.2. Use E.10.MOVE only when move-like wording still leaves the governed claim unclear.

A.16:1 - Problem frame

The language-state U.CharacteristicSpace in C.2.2a makes positions explicit, but practitioners still need admissible moves for preserving, publishing, narrowing, reopening, or docking selected content to a later use. Those moves must not become a second formality-only climb, a generic one-pass process, or an invisible jump into a stronger pattern claim.

The existing publication or a short local note can make the move recoverable. A fuller history is warranted only when lineage, branching, loss, supersession, or a history-dependent responsibility handoff changes what a later reader may conclude.

A.16:2 - Problem

Without one coordination rule, authors force cues into anomaly or requirement language too early, describe every change as maturation, hide reopen and backoff, confuse a new form with a new episteme, treat route selection or publication as authority, or wrap every move in a trajectory account.

A.16:3 - Forces

ForceTension
Coordination vs duplicationCoordinate moves over the declared language-state chart without recreating A.19, endpoint patterns, or E.18.
Local sufficiency vs history visibilityUse sufficient local content while preserving richer history when it changes a later decision.
Early capture vs endpoint disciplinePreserve low-articulation content without claiming that an endpoint test has passed.
Continuity vs identity changeKeep a form-only publication of one episteme distinct from the first typed preservation and from a content-changing successor episteme.
Advance vs retreatSupport formalize and operationalize together with reopen, sketch-backoff, respecify, and retire.
Plain use vs assurance detailKeep the practitioner path short while exposing Work, publication, or authority relations when they are current.

A.16:4 - Solution

A.16 defines admissible move names, guards, identity decisions, and next-use docking.

Here move means a typed transition in the publication of selected episteme content. Observation can supply a precursor cue for early preservation under A.16.1; B.4.1 begins when route publication becomes worth making explicit. A.16 starts when a cue is deliberately noticed, stabilized, route-published, projected, formalized, operationalized, reopened, respecified, or retired.

A.16:4.1 - Canonical move table

This is the canonical move table. Later examples apply it; they do not define another move family.

MoveUse it whenPublication resultKeep explicit
noticea low- or unstable-articulation cue is worth preservingpreservation-worthiness becomes explicit; a first typed preservation may beginwhy the cue is worth preserving and which witnesses remain
stabilizethe noticed cue needs a steadier local shape before route or endpoint choicePreArticulationCuePack or an equivalent early form may become admissiblecue nucleus, anchors, contrasts, witnesses, and preservation rationale
routea stabilized cue has several plausible downstream directions or one route must be selectedRoutedCueSet or another route-bearing publication makes plurality and any selection explicitlive routes, selected route if any, selection reason, and reopen condition
projectionone aspect of an explicit route must be foregrounded without claiming endpoint admissiona typed route-bounded partial publication on an existing MVPK facewhat is foregrounded, what is omitted or lost, and how reopen remains possible
formalizearticulation or closure can increase under a named later rulea more explicit symbolic, slot, or normal-form publicationthe rule used, changed facets, and any new evidence-generating Work boundary
operationalizeselected content is ready to face a method, Work, gate, or other operational questionthe episteme or project record is docked to the pattern that defines or tests that usethe downstream contribution, its guard, and any world-facing Work boundary
reopenthe inquiry or intended use remains appropriate, but closure was over-committedthe publication expresses the reopened alternatives and reduced closure claimreopened rivals, retained witnesses, and which prior endpoint-use or current-use claim no longer holds
sketchBackoffan endpoint-bound or operational form over-commits the available groundsan exploratory cue-bearing form becomes admissible againretained anchors and witnesses, withdrawn closure, and the next safe question
respecifythe inquiry or intended use remains appropriate, but its framing, facet reading, or route specification is wronga revised framing or route specification replaces the earlier onereplaced commitments, what remains supported, and any episteme-identity change
retirea cue, route-bearing publication, episteme, or branch is no longer current for the named use because its grounds failed, a successor took over, or a current-use decision endedretirement or withdrawal is explicitreason, retired object, preserved history, and supported successor information or an unresolved successor question when the receiving use needs it

The table names moves, not the resulting objects. PreArticulationCuePack and RoutedCueSet are publication forms defined elsewhere. U.AbductivePrompt is the question account defined by B.5.2.0; its publication form is selected separately. A claim-bearing episteme remains U.Episteme; E.24.PUB separately defines a bounded publication occurrence.

projection means route-bounded partialization. Publish its result in a typed publication form. An expression must satisfy that form’s content requirements as well as the presentation rules of any selected MVPK face; a face label or an untyped placeholder supplies no such conformance. respecify changes framing, route specification, or a facet-profile reading. A revision can also reopen closure; state both changes when both occur, using A.16.2:4.1. Precision repair remains with A.6.P or C.16.Q; recovery of an ambiguous action-oriented claim or question remains with A.6.A.

Do not use A.16 to decide measurement admissibility, Bridge substitution, endpoint ontology, or another subject claim. Name the applicable pattern and test directly; A.16 coordinates only the publication move that makes that question current.

A.16:4.2 - Guard discipline

State the guard through the language-state readings or route condition on which the move depends. Obtain any required AE reading from C.2.4, CD reading from C.2.5, and representation-factor reading from C.2.7. State required source, evidence, access or action conditions separately under C.2.6. A guard can use both readings and direct relation claims, cited separately or through one published profile; a relation account is not a CharacteristicSpace slot. Add witnesses, scope, and GammaTime selectors when needed. “The idea matured” is not a guard.

A summarized chain may omit repeated unchanged fields, but it must leave every move identity, endpoint-rule change, loss, and status change that affects interpretation reconstructible. A later higher-closure publication does not retroactively strengthen an earlier cue; later retreat does not erase the earlier publication.

A.16:4.3 - Decide identity before describing movement

Do not use “move between publication forms” as a shortcut across these three cases:

  1. First typed preservation. A precursor cue, trace, contrast, or witness may have no source episteme or source publication form. Name the precursor and the first typed preservation form. C.2.1 governs the identity of the first claim-bearing episteme when one is admitted.
  2. Same episteme edition, another form. When EntityOfConcern, ClaimGraph content, and effective reference scheme remain the same, one episteme edition may be issued in another form or on another carrier. Name the episteme and source and target forms only when they matter. E.24.PUB governs each claimed availability occurrence; neither form nor occurrence creates a successor episteme.
  3. Content-changing successor. When a C.2.1 discriminator changes, identify a separate target episteme. Name the source and target epistemes, the changed discriminator, what content is preserved, changed, and lost, and the lineage relation only when its predicate obtains. A repeated label, form, carrier, or move name proves no continuity. Use A.16.0 only if the multi-step or branching history is load-bearing.

The same discipline applies to project records through their own identity patterns. E.24.PUB says that an already identified episteme was made available for a bounded use; it says neither that content changed nor that an endpoint test passed.

A.16:4.4 - Minimum content for a move

Make the following content recoverable in the publication or, where needed, a short move note. Include conditional details only when they change the use:

FieldMinimum content
Current itemprecursor cue or source episteme/project record; source form only when one exists and matters
Identity casefirst typed preservation, same edition in another form, or content-changing successor
Move and guardone move from §4.1 and the changed facet or route condition that justifies it
Targettarget episteme/project record when identified, typed target publication form, and the concrete object or claim that the downstream pattern defines, constrains, or tests; name the ClaimGraph carrying that rule only when its identity or edition changes the use
Preservationwitnesses or anchors retained; for a successor episteme, content preserved, changed, and lost plus any lineage relation
Returnendpoint condition not yet met, omitted or lost content, and reopen or retirement condition

Add an EpistemePublicationRelation occurrence only when bounded availability matters. Add the MVPK face only when rendering matters. Neither replaces the form, episteme, or next pattern.

A.16:4.5 - Work crossing and actual relation changes

Some formalize and operationalize moves only re-express available content. Others require measurement, experiment, installation or use of instrumentation, or execution. Expose the needed action and use the applicable measurement, experiment, gate, or endpoint pattern. If the receiving claim requires a distinct dated U.Work, establish its A.13 basis and independent A.15.1 admission; use F.6 afterward only for precise assignment-bound attribution. A.16 records the pending or separately established crossing; it does not establish that the action occurred or produced a result.

Next-use docking and a Work crossing do not by themselves establish a change in authority, responsibility, permission, or commitment. If one of those relations changes, record it as a separate claim: the relation under its governing pattern; participants in that relation’s own roles, including giving and receiving admitted systems when its predicate requires them; any U.SystemRoleAssignment occurrences through which they participate; its object or action, scope, and effective interval; and the assigning, instituting, revoking, or superseding act when its pattern requires one. A.2, A.2.1, and the applicable deontic or authority pattern establish and test that claim.

Use A.16.0 for such a handoff only when its legitimacy or interpretation depends on upstream move or lineage history. Otherwise the local account of the needed or performed action and the separately established relation are enough.

A.16:4.6 - Keep coordination claims separate

Do not compress several claims into AuthorityState. A reusable language-state coordination readout is only a compact view of independently established facts, not a new U-kind or world-side state. Include only the fields needed by the reader:

ClaimWhat to show
Route plurality or selectionlive routes; selected route if any; selection reason; route-bearing publication
Endpoint admission or use dispositionnamed endpoint test, its result, and the stronger use admitted, narrowed, or blocked
Publication availabilityepisteme, form, bounded use, and EpistemePublicationRelation occurrence when current
Current use or retirementcue, episteme, publication, or branch and the currentness, withdrawal, supersession, or retirement claim that applies
Actual relation changeonly an independently established authority, responsibility, permission, or commitment relation with participants, object or action, scope, interval, and any act required by its governing pattern; otherwise omit the optional claim or report the unresolved change; state that a relation is unchanged only when an applicable negative criterion or complete closure basis supports that claim

Open route plurality is not a lineage fork. A multi-route state keeps several directions live inside one route-bearing publication. A lineage fork has separately identified successor members, their preserved and lost content, and any lineage relations that obtain.

EndpointAdmissionProfile may be reused as a declarative decision profile for next-use docking. Include only inputs required by the proposed use: the relevant C.2.2a position, selected C.2.LS facet readings, any route condition from B.4.1, any prompt-entry conditions from B.5.2.0, and the witness or grounding conditions it consumes. Apply it to judge only whether docking to the later question is admissible: relation-like content toward A.6.P, an open question and rival set toward B.5.2.0, evaluative content toward C.16.Q, ambiguous affordance-like wording toward A.6.A and then the recovered subject, viability or other quality-family content toward C.25 when quality-family decomposition is the question, and executable docking toward A.15. Apply the selected pattern’s own tests. A.6.A may return a sufficient claim, question or missing basis; that recovery establishes no common invitation relation. Tone, style or apparent explicitness supplies no subject result by itself. The admission result creates no authority, responsibility, permission, commitment, publication, gate, or Work state.

A.16:4.7 - One history threshold

Local publication content is sufficient when the move or short chain is reconstructible without extra lineage machinery. Use A.16.0 only when at least one of these is load-bearing:

  • derivation, supersession, fork, merge, or retirement structure;
  • a multi-move history whose compression would hide a change in the applicable pattern or rule;
  • loss notes or reopen conditions spanning more than one move; or
  • an actual responsibility handoff, Bridge entry, or viewpoint entry whose legitimacy or interpretation depends on upstream history.

A.16 defines move admissibility and A.16.0 packages the trajectory account. A graph representation alone does not establish a TransformationFlowStructure. Use E.18 only for an independently selected structure that meets its rules, and E.18.2 for a mathematical description of that structure. Publication faces and bounded audience availability remain under E.17 and E.24.PUB; use C.29 when mathematical-lens adequacy is the current question.

A.16:5 - Worked moves and recoveries

A.16:5.1 - Incident-control line

An operator alert about a production disturbance may follow notice -> stabilize -> route -> operationalize, then reopen when counter-evidence arrives. The alert need not become an anomaly or requirement immediately. Each step names the form and next pattern; any dated response Work remains a separate claim.

A.16:5.2 - Inquiry and admissible retreat

An inquiry cue about a model-versus-observation discrepancy may follow notice -> stabilize -> route -> projection -> formalize. If the framing over-commits while anchors remain unstable, continue with reopen -> sketchBackoff -> respecify, retaining the witnesses and withdrawing only the unsupported closure.

A.16:5.3 - Three identity cases in one line

A raw vibration trace and operator contrast may first be preserved as PumpVibrationCuePack-1; no fictional source episteme is required. Publishing the unchanged cue-pack episteme in a review card and a long-form note is a form-only case under E.24.PUB. If later analysis changes its ClaimGraph from “unexpected vibration” to a bounded bearing-fault proposition, C.2.1 identifies a successor episteme; its publication or an accompanying note states the changed claim, retained trace, discarded rival, and any EpistemeEditionRelation that obtains.

A.16:5.4 - Retired route or branch

A RoutedCueSet may keep evaluative and abductive routes live. If review later shows the evaluative route unsupported, record that route’s retirement while the abductive route remains current. Do not rewrite the history as though only one route ever existed. A route inside one publication becomes a lineage branch only after a separate successor member is identified.

A.16:5.5 - Premature endpoint capture

notice -> gate decision is not admissible merely because the cue sounds urgent. Recover the contributions required by the applicable endpoint test; stabilize or publish a route when that test or the receiving use needs it. Reopen an over-committing requirement label and publish the earlier safe form.

A.16:5.6 - Silent route drift into Work planning

If an evaluative note starts guiding Work planning, make the changed route or operational use explicit in the existing material or an accompanying note. Apply A.15.2 to the WorkPlan content. Name an acting system, Method, system-role assignment, or Work only when the claim depends on that distinction.

A.16:5.7 - Recover the content rules behind a face

“The move publishes a Tech face” identifies presentation rules but leaves the required route content unstated. “The move enters A.6.P” names a pattern without identifying its contribution. Name the typed content form and the object or claim that the cited pattern defines, constrains, or tests; identify the selected MVPK face when rendering or review depends on it.

A.16:5.8 - Short compound histories

notice -> stabilize -> route -> projection and endpoint admission -> reopen -> sketchBackoff -> route can be summarized only when each intermediate move, changed rule, loss, and independent status claim remains reconstructible. Retreat preserves the earlier endpoint result in the history. When comparing histories, do not treat route -> projection and an unsupported cue -> requirement leap as one “formalization speed”; compare the moves, forms, applicable rules, and independent status claims.

A.16:6 - Bias and common mistakes

A.16 biases authors toward typed movement and away from “it naturally matured.” Make the move recoverable in sufficient existing content; add a note only for information the receiving use would otherwise lose.

  • Trajectory-wrapper inflation. Do not wrap every move in A.16.0.
  • Presentation substituted for content. Selecting an MVPK face does not establish conformance to the cue or route form. Recover the expression and applicable rules; keep the episteme, form, publication occurrence and carrier distinct under E.24.PUB.
  • Identity laundering. A new form is not automatically a new episteme; changed C.2.1 content cannot be hidden as reformatting.
  • Irreversible maturity story. Reopen, sketch-backoff, respecify, and retire are admissible.
  • Route/fork confusion. Several routes in one publication are not separate successor epistemes.
  • Silent branch disappearance. Retire, merge, or show that a route never became a separate branch.
  • Status bundle. Do not call route selection, endpoint admission, publication, current use, and actual authority one state.
  • Hidden Work. Formal wording, a gate-facing form, or an operational hook establishes no Work or Work result.
  • Endpoint substitution. A.16 docks to the endpoint pattern; it never relaxes or replaces that pattern’s conditions.
  • Old formality-only climb. Unpack “informal to formal” into the move, facet change, route selection, identity case, and use change.
  • Hidden-lineage laundering. If an endpoint claim depends on earlier move publications that cannot be recovered anywhere in the publication chain, treat the history as incomplete until those records or an adequate A.16.0 account are supplied.

A.16:7 - Conformance checklist

Use this checklist for authoring and review:

  1. A.16 does not redefine F, an endpoint test, Work, publication, or a graph-path calculus.
  2. The publication or accompanying note identifies one move from §4.1 and its facet or route guard; rhetorical relabeling is insufficient.
  3. The identity case is explicit. A precursor needs no invented source episteme; a form-only case preserves all C.2.1 discriminators; changed content identifies a target episteme and records preserved, changed, and lost content.
  4. The source condition, typed target form, and object or claim that the downstream pattern defines, constrains, or tests are recoverable. The publication occurrence and MVPK face are added only when material and substitute for none of them.
  5. projection names a typed route-bounded form and its omissions; respecify does not hide an A.6.P, C.16.Q, or A.6.A precision repair.
  6. Route plurality or selection, endpoint disposition, publication availability, and current-use or retirement claims remain separate.
  7. A multi-route publication is not called a lineage fork. A fork names separate successor identities, losses, and lineage relations.
  8. Reopen, backoff, respecify, and retire say which witnesses remain and which closure, route selection, endpoint use, publication, or current-use claim changes.
  9. Any dated Work and Work-result claim is established separately under its own patterns.
  10. Docking or a Work crossing alone establishes no authority, responsibility, permission, or commitment change. A change names the relation and its own participants, object or action, scope, interval, and any instituting or ending act required by its governing pattern. An unchanged-relation claim requires an applicable negative criterion or complete closure basis.
  11. Use EndpointAdmissionProfile only to judge admissible docking; apply all of the endpoint pattern’s own conditions.
  12. Sufficient local publication content stands alone. A.16.0 opens only at the §4.7 threshold, and E.18 opens only for an independently selected TransformationFlowStructure.
  13. A summarized chain leaves intermediate move identities, endpoint-rule changes, losses, and material status changes reconstructible.
  14. Compared histories are typed by form, move, applicable pattern or rule, and independent status claims; they are not compared as generic “maturity speed.”

A.16:8 - Consequences

Benefits. Practitioners can advance or retreat without inventing maturity, Work, publication, or authority claims. The three identity cases prevent both false continuity and needless successor creation. Local publication content can be sufficient; A.16.0 opens when history is load-bearing, while E.18 requires its independently selected transformation-flow subject.

Trade-off. A consequential move needs explicit guards and preservation content. The move table, minimum content, history threshold, and checklist provide one reusable account of those requirements.

Failure containment. A missing endpoint rule, Work relation, publication occurrence, lineage predicate, or actual authority relation blocks only that additional claim. The cue and any independently admitted earlier publication remain available.

A.16:9 - Rationale

C.2.3 defines formality; C.2.2a and A.19 define position semantics; A.16 defines admissible movement; A.16.0 records only history that needs its own accountable publication. Keeping identity, route, endpoint, publication, current use, and actual authority separate prevents a convenient process word from becoming a substitute ontology.

A.16:10 - SoTA-Echoing

Incident-response contribution. NIST SP 800-61r3 (2025), §2 connects lessons from incident-response activities to revisions of cybersecurity practices; learning can affect ongoing work rather than wait for recovery to end. A.16 uses that feedback idea for reopening a publication or its use. The source’s scope is cybersecurity incident response.

Historical provenance contribution. W3C PROV-DM (2013), §5.2.2 distinguishes revision as a derivation relation between entities. This supplies a historical comparison for stating a lineage predicate rather than inferring it from a repeated label. C.2.1 supplies FPF episteme identity.

FPF adaptation. The ten moves and the threshold for a separate A.16.0 history are FPF’s coordination choices. Neither cited source establishes that move set or the threshold. Keep sufficient local content, expose consequential loss and retreat, and use E.18 only for an independently selected TransformationFlowStructure.

Local stance. Admissible language-state movement needs typed moves, explicit identity and status claims, and retreat options. It needs neither a mandatory formality climb nor a single “authority” scale.

A.16:11 - Relations

  • Builds on: C.2.1 for episteme identity; C.2.2a for language-state positions; C.2.LS for facet profiles; C.2.4 for articulation, C.2.5 for closure, C.2.6 for source and use conditions, and C.2.7 for representation-factor readings; A.18 for Scale semantics; and A.19 for CharacteristicSpace and Coordinate semantics.
  • Coordinates with: A.16.0 for accountable trajectories; A.16.1 for early preservation; A.16.2 for retreat and respecification; B.4.1 for route publication; B.5.2.0 for abductive prompting; A.6.P, A.6.A, C.16.Q, and C.25 for endpoint-local questions; E.11.PUR, A.15.5, A.15.1, and A.15.2 for non-A.16 move wording and project action; E.24.PUB for bounded publication availability; E.18 for an independently selected TransformationFlowStructure and E.18.2 for its mathematical description; and E.10.MOVE when move-like wording still leaves the governed claim unclear.
  • Constrained by: A.2/A.2.1 and the applicable deontic or authority pattern for any actual relation change; A.13 followed by independent A.15.1 for precise performed Work, F.6 only afterward when precise assignment-bound attribution is current, A.15.PROD for production or inception, and the applicable domain predicate for result claims.

A.16:End

A.16.0 - Keep an Episteme’s Language-State and Publication History Recoverable

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Technical alias. LanguageStateMoveTrajectory names the optional history-account form described here. It is not an additional U-kind or an identity rule for the filled account.

Builds on. C.2.1, C.2.2a, A.16, A.19, E.24.PUB, E.17, E.10, F.18.

Used by. A.16.1, A.16.2, B.4.1, B.5.2.0, A.6.P, C.16.Q, A.6.A, F.9.1, E.17.1.

Use this when. Use this pattern when one local language-state move is no longer enough because a reviewable history must keep episteme editions, publication forms, branches, retirements, or losses visible, or because an actual responsibility handoff depends on that history.

What goes wrong if missed. Readers treat cue packs, routed cue sets, endpoint-bound publications, and next-use dockings as successive states of one unchanged episteme; forks, losses, authority changes, and work-requiring crossings become implicit, and an actual responsibility change may be mistaken for semantic docking.

What this buys. One optional trajectory account that records lineage, position claims, move kinds, publication forms, losses, and the next use and authority boundary without requiring a history account for every local A.16 move.

A.16.0:1 - Problem frame

In engineering, inquiry, operator, and management practice, teams sometimes need more than a local move note. When branch structure, supersession, retirement, bridge-sensitive loss, a multi-step change in the applicable rule, or an actual responsibility handoff whose legitimacy depends on upstream history matters, readers need one place that identifies the episteme editions, publication forms, and links involved.

Cue packs, routed cue sets, abductive prompts, typed route-bounded projection forms, partial normal forms, and endpoint-bound records may appear in that history as publication forms or published records. They are not the disturbances, telemetry traces, model outputs, bodily tensions, or carrier documents that ground it.

The trajectory account records the selected episteme edition at each load-bearing step, the form and publication occurrence when availability matters, and independently established lineage links among distinct epistemes when claims change.

A.16.0:2 - Problem

When history needed for the receiving use is left implicit:

  1. history is mistaken for a generic one-pass process story rather than read as typed language-state moves over a declared U.CharacteristicSpace;
  2. an early seam form is confused with an endpoint-admitted episteme or with the publication occurrence that makes an episteme edition available;
  3. forks, merges, route retirement, supersession, and route-sensitive loss become implicit and unverifiable;
  4. local move accounts may add unnecessary history detail or omit a work boundary or responsibility change that the receiving use needs;
  5. bridge and viewpoint docking inherit under-described upstream history.

A.16.0:3 - Forces

ForceTension
History value vs wrapper inflationPublish lineage only when it matters, without making trajectory accounts mandatory around every admissible move.
Lineage fidelity vs readable publicationTrajectory history must stay branch-aware without becoming unreadable bookkeeping.
Seam usefulness vs endpoint disciplineUpstream publications must be useful while remaining visibly upstream of endpoint admission.
Account clarity vs neighboring rulesThe trajectory account must explain cases that need history without taking over the position, move, publication, path, or endpoint rules.
Local move lineage vs bridge entryA trajectory may later cross viewpoint or context boundaries, but that crossing does not redefine its move or lineage semantics.

A.16.0:4 - Solution

LanguageStateMoveTrajectory is an optional account form for history across positions in the language-state U.CharacteristicSpace named in C.2.2a. A filled history account is an ordinary C.2.1 episteme when its claim content, EntityOfConcern and effective ReferenceScheme are identified. Its content can state selected source editions, independently obtaining lineage, typed moves, publication forms and any availability occurrence that matters.

It does not define position semantics, move admissibility, publication forms, or transformation-flow structure. Use C.2.2a and A.19 for positions, A.16 for moves, E.24.PUB for publication availability, and E.17 for publication faces. E.18 applies only when the current subject is an independently selected TransformationFlowStructure; E.18.2 describes that structure mathematically.

It answers the question: when the history matters, which episteme edition is current, what precedes or branches from it, which moves and links connect the entries, how is each edition published when availability matters, what was lost, and which rule or use applies next?

A.16.0:4.0a - Identify the account and its expression

  1. Apply the history threshold. Keep the local A.16 publication content when it answers the receiving question. Use the fuller account only when branch, loss, lineage or an actual responsibility history changes a later use.
  2. Identify the account’s subject. For a source-centred history, name the source episteme as EntityOfConcern and state the relevant edition and relation claims in the account’s ClaimGraph. For a relation-centred account, identify the independently obtaining relation it concerns. A negative or unresolved lineage claim remains about an independently identified source or other subject; it creates no relation occurrence.
  3. Recover the relevant history claims. Distinguish the source editions, position claims, actual lineage, moves, losses and next use needed here. Use their direct rules below. Distinguish an unknown link from a no-successor result supported by an applicable negative criterion or complete closure basis. Neither result establishes continuity.
  4. Choose an adequate expression. The LanguageStateMoveTrajectory form can express that account. Under E.24.PUB, publication form is a relation-defined participant meaning over an independently identified entity; using the form admits no subtype or second account individual. Recover its expression relation, carrier and any availability occurrence only when the receiving claim needs those distinctions.
  5. Return the history needed by the next use. Make the relevant branch, loss, limit or responsibility fact recoverable. Stop when that use is supported; a further account of the account’s own history is needed only if another receiving question requires it.

The filled account has its own C.2.1 identity. Described source editions, position claims, loss notes and relation facts contribute to its content; they are not additional identity fields. A source-history event and the account acquiring knowledge of that event are different changes. Changed account content identifies another episteme, with edition continuity asserted only when its own relation obtains.

Several unrelated sources displayed in one table do not become one history individual. A common carrier or form can support separately grounded accounts and expression claims. Each claimed E.24.PUB publication occurrence still concerns one selected episteme edition and one bounded use. Publishing a history account is also distinct from publishing each source edition that it describes.

A.16.0:4.1 - Keep the account positions distinct

Keep the account’s own identity and publication distinct from these values described in its history:

  • selected episteme edition - the current U.Episteme whose claims are being positioned or re-expressed;
  • lineage links - independently established derivation, supersession, fork, merge or retirement relations among the selected epistemes, each under its defining predicate; state a no-successor result when that is the supported account;
  • grounds or witnesses - disturbances, discrepancies, traces, model outputs, bodily tensions, contrasts, or exemplars that justify the history;
  • publication form - the reusable rules for a cue pack, routed cue set, prompt, typed route-bounded projection, partial normal form, or endpoint-bound record;
  • publication expression - the sign construction that follows the selected form and expresses enough of the selected edition for the bounded use;
  • publication occurrence - an EpistemePublicationRelation occurrence only when availability to an audience for a bounded use matters;
  • publication face - the MVPK face on which a form is rendered when face typing matters;
  • carrier - the independently identified physical or digital entity whose actual state or realization yields that expression, such as a document file, physical card, or trace file.

A form, face, carrier, or publication-occurrence change can leave the selected episteme unchanged. A changed C.2.1 discriminator identifies another episteme. Call it a continuing edition only when the C.2.1 EpistemeEditionRelation obtains; any other lineage claim requires its own defining predicate and obtaining facts. Publication alone creates neither the episteme nor a lineage link.

Several live routes for one selected edition are not yet a lineage fork. A fork claim requires independently identified successor epistemes and the obtaining lineage predicate under its direct rule. Disclose losses and any authority facts that the selected account or that rule needs; authority is not a universal extra fork participant. Publication of the successors is not a universal prerequisite, and two publications of the same edition create no fork.

A trajectory step may reuse one edition in another form, add a successor episteme, or relate several epistemes through fork, merge, supersession, or retirement. It does not describe a trajectory of the source phenomenon.

Here route names an A.16 move-family label or a typed upstream publication-form cue. It is not an action route, work sequence, workflow, or transformation-flow path.

A.16.0:4.2 - Position-account discipline

The position read by this pattern is the slot-explicit claim defined in C.2.2a: a partial coordinate publication in the declared language-state U.CharacteristicSpace, where each basis-slot reading reports one value or a supported set of remaining possible values within the slot’s Scale domain. An interval is usable only where that Scale admits it (C.2.2a:4.2).

Early seam publications may leave some slots unknown or wide. That uncertainty is admissible only if it is explicit. A trajectory account therefore records the position claim for the current episteme edition and, when needed, for predecessor or sibling editions that justify the move reading.

A.16.0:4.3 - Use threshold and core trajectory record

Local A.16 publication content is sufficient when no load-bearing branch, loss, or supersession structure needs publication and no actual responsibility handoff depends on upstream history. An existing version history can also supply the answer when the needed source-use, continuity and loss facts are already recoverable there; the form does not require copying them into another document.

Use the LanguageStateMoveTrajectory account form when at least one of the following changes the receiving use:

  • derivation, supersession, fork, merge, or retirement structure;
  • multi-step loss notes or reopen conditions that would be hidden by a compressed move note;
  • an actual responsibility handoff whose legitimacy or interpretation depends on upstream history;
  • bridge or viewpoint entry that depends on upstream route, loss, or lineage structure.

An account using this form identifies its own subject, claim content and effective ReferenceScheme. It makes the following history content explicit to the extent needed by the selected use:

  • the current selected episteme edition;
  • predecessor, sibling, or ancestor editions when the current reading depends on lineage;
  • the obtaining lineage link kind, such as derivedFrom, supersedes, forkedFrom, mergedFrom or retiredWithSuccessor; a supported retiredWithoutSuccessor result is a claim about the retired episteme, not a link to an invented successor;
  • the current position claim and any load-bearing predecessor position claims;
  • the typed move or move sequence;
  • the publication form and, when availability matters, the publication occurrence;
  • the MVPK face only when rendering matters;
  • the next question or use, the applicable pattern, and its concrete contribution;
  • when an actual responsibility handoff is load-bearing, the separate participants, relation, object or action, scope, interval, and instituting-act references required by A.16.0:4.6;
  • the grounds or witnesses and still-live rivals needed to justify the entries, with any loss note, reopen condition, branch-specific authority note or bridge-sensitive note that matters.

A.16.0:4.4 - Recorded move-family discipline

The LanguageStateMoveTrajectory account form records the A.16 move family: notice, stabilize, route, projection, formalize, operationalize, reopen, sketchBackoff, respecify, and retire.

Not every account uses every move. Forward movement, retreat, reframing, and explicit retirement belong to one family defined in A.16 when that history is worth publishing.

A.16 defines the detailed move guards. A.16.0 records the moves and their satisfied guards; it does not replace them.

A.16.0:4.5 - Seam publication and face discipline

A trajectory account may refer to seam publication forms that remain upstream of endpoint admission. Examples include:

  • PreArticulationCuePack;
  • RoutedCueSet;
  • partial normal forms already typed elsewhere;
  • other explicitly typed upstream publications that preserve a non-endpoint position.

These are not a rival publication-face sequence. They are typed publication forms rendered, when necessary, on existing MVPK faces under E.17.

For a published U.AbductivePrompt, identify the question account under B.5.2.0:4.2.1–4.2.2 and its selected form separately. When a trajectory returns to that entry, distinguish a changed account from a changed explanatory question.

Untyped placeholders such as “route-bounded publication face” are non-conformant in a trajectory account unless the text also names the publication form and, separately, the MVPK face if face typing matters.

A.16.0:4.6 - Endpoint docking and next use

A trajectory does not need to terminate to be useful. What matters is a visible docking milestone to the next pattern-based question or later use.

Typical next-use patterns include:

  • A.6.P for relation precision or repair;
  • A.6.A when action-oriented wording leaves the intended claim or question unclear; return the recovered meaning to its subject pattern for any further result;
  • C.16.Q for quality or evaluative-characterization wording repair;
  • B.5.2 for abductive inquiry;
  • A.15.2 for planning future Work, including its target Method;
  • C.25 for quality-family decomposition and Q-Bundle structure.

Name the next pattern and what its content defines, constrains, or tests. The account already identifies the selected episteme edition; add a project record, publication form, or publication occurrence only when that distinction changes the next use. This is next-use docking, not a transfer of responsibility, and a pattern reference alone does not prove endpoint admission.

Separate responsibility-handoff branch. Open this branch only when responsibility, commitment, permission, or authority changes. Name the relation before and after the change under its applicable pattern, then the participants in that relation’s own roles. Include giving and receiving admitted systems when its predicate requires them and, when their system-role classification matters, the system-role kinds and assignments through which they participate. State its governed object or action, scope, effective interval, and any assigning, instituting, revoking, or superseding act that the relation requires. The trajectory account cites that relation and its history; episteme lineage, publication form, publication occurrence, endpoint admission, and next-use docking neither create nor prove it.

After docking to a next use, monitoring, maintenance, revisit, or later re-entry may continue through new lineage entries or later trajectories. Keep lineage continuity separate from the current endpoint use and from any separately established responsibility or authority relation.

A.16.0:4.7 - Re-expression and additional world-facing Work

Some formalize and operationalize steps re-express already available grounds through rewriting, slot-explicit articulation, route-bounded partialization, view retargeting, or normal-form repair. Performing those activities can itself be dated Work under A.15.1; the distinction here is whether new world-side measurements or interventions are needed.

Some steps additionally require new measurements, experiments, installation or use of instrumentation, or execution. Make that needed action and its reason visible; use the relevant measurement, experiment, gate, or endpoint pattern to describe or test it. A distinct Work identity is needed only when the receiving claim or reliance depends on that occurrence: establish the A.13 basis and independent A.15.1 admission, then apply F.6 if precise assignment-bound attribution is needed. An assertion or ClaimGraph identity is likewise conditional on its use.

A work-boundary crossing does not by itself transfer responsibility or authority. If a separate responsibility handoff occurs, use the triggered branch in A.16.0:4.6 and keep its relation distinct from the Work, episteme lineage, publication, and endpoint use.

A.16.0:4.8 - Relation to A.16 and E.18

A language-state trajectory account does not by itself establish an E.18 TransformationFlowStructure, and A.16.0 does not define language-state move semantics.

  • A.19 and C.2.2a define the declared characteristic-space reading of positions;
  • A.16 defines move kinds and guards;
  • E.17 defines publication-face discipline; E.18 governs an independently selected TransformationFlowStructure and E.18.2 its mathematical description;
  • endpoint patterns define, constrain, or test endpoint-local claims and uses;
  • E.24.PUB distinguishes the selected episteme edition, publication form, carrier, bounded use, and any publication occurrence that matters.

A.16.0 standardizes only the history account form for cases where that history is worth publication.

Here move names a typed language-state publication transition under A.16. For an already clear project-action, work-entry, pattern-use or other question, use its subject pattern directly. Use E.10.MOVE only while the wording still hides the governed claim.

A.16.0:4.9 - Bridge and viewpoint entry

A trajectory may later cross a viewpoint or context boundary. When that happens:

  • the trajectory establishes neither an F.9 Bridge nor the suitability of any bounded cross-context use; relation and use claims remain with F.9;
  • stance notes remain with F.9.1;
  • viewpoint reuse remains with E.17.1;
  • endpoint-local semantics remain in the rules defined or tested by the named endpoint patterns; publication availability remains a separate E.24.PUB relation.

A.16.0 only makes those entry points explicit. It establishes no current reliance, authorization, or receiving use. When those questions are live, apply triggered A.10 or B.3 for reliance, the pattern that directly constrains the receiving action for authorization, and evidence of the receiving Work or publication for occurrence. No bundled record is required when those questions are not live.

A.16.0:5 - Archetypal Grounding

Tell. A language-state trajectory account is an optional, lineage-aware account of episteme editions and their publication history, with declared position claims, move kinds, losses, and the next applicable pattern or use.

Show (System). A service disturbance is a system-side phenomenon, not a trajectory lineage member. It grounds an alerting episteme lineage. One stabilized cue pack may first keep two routes live in one RoutedCueSet; record a fork only after distinct successor epistemes and their independently established fork links are identified.

Show (Episteme). A model-vs-observation discrepancy is a witness-lane tension, not the positioned episteme edition or its lineage. Once the discrepancy is preserved in a cue pack, one branch may express the selected edition in a typed prompt form and later formalize it; if the claims change, identify another episteme and assert continuation only when its relation obtains. Another branch may reopen or retire if the provisional route proves unsupported.

A.16.0:5.1 - Five identity and use cases

These are constructed distinctions. History account H1 has source episteme S0 as its EntityOfConcern, claims about S0’s language-state history and an effective ReferenceScheme.

Change or receiving questionResult
H1’s unchanged claims are displayed in another arrangement or on another carrier.H1 remains the same episteme. Recover the changed form, bearing or availability relation only when needed.
The author learns a new supported fact about S0’s history and changes the account’s claim content.The resulting account H2 is another episteme. It is a continuing edition of H1 only if the C.2.1 edition relation obtains. Learning this fact did not itself change S0’s history.
Independently identified S1 and S2 are successors of S0, and the historical facts satisfy the selected lineage rule’s fork predicate; neither successor has been published.The fork already obtains and can be described. Two different publications of S0 alone would not satisfy this case.
A route projection retains a conclusion but omits an assumption needed to reconstruct its applicability.The loss note identifies that assumption and which receiving use can no longer recover it, retaining the supported content and stating the needed reopen condition.
Under an already defined review-responsibility rule, Ana is responsible for review case K until time t; an authorized instituting act G assigns that responsibility to Boris from t.Cite the rule, both actual relations, their participants, review scope, time and instituting act. The history account reports this change. Language-state movement, a new form or next-use docking supplies none of those responsibility facts.

For a question about whether S0 has a successor when the evidence is incomplete, keep S0 as the account’s subject and state that unresolved claim. For a question about an actual independently identified lineage relation R, an account may instead have R as its subject. A table showing unrelated S0 and T0 does not supply a common history-object identity.

A.16.0:6 - Bias-Annotation

The pattern biases authors toward lineage-aware history accounts rather than stage stories that conflate re-expression with changed claims. That bias is intentional when branch, loss, next-use, actual responsibility, or authority semantics matter. The counter-bias is equally intentional: reuse sufficient local publication content instead of adding another account.

A.16.0:7 - Conformance Checklist

  • CC-A.16.0-1 The LanguageStateMoveTrajectory account form SHALL NOT be treated as mandatory wrapper syntax around every A.16 move or as an additional U-kind.
  • CC-A.16.0-2 Identify the account episteme through its own C.2.1 content, subject and scheme. Distinguish it from the source editions and relations it describes, and distinguish each selected publication edition from grounds, form, availability occurrence, face and carrier.
  • CC-A.16.0-3 Position claims used in the trajectory SHALL be published as slot-explicit claims in the declared language-state U.CharacteristicSpace, not as folk stage labels.
  • CC-A.16.0-4 State the independently obtaining fork, merge, supersession, derivation or retirement facts whenever the account depends on them. Distinguish negative claims supported by an applicable criterion or complete closure basis from unresolved claims; neither creates a relation. Successor publication and generic authority are not universal fork requirements.
  • CC-A.16.0-5 Publication form and MVPK face SHALL NOT be collapsed, and untyped seam placeholders SHALL NOT substitute for typed publication forms.
  • CC-A.16.0-6 projection SHALL be read as route-bounded partialization with visible loss notes and an admissible reopen condition.
  • CC-A.16.0-7 Work-requiring formalize or operationalize steps SHALL expose the work-boundary crossing; they SHALL NOT call that crossing a responsibility handoff unless the separate A.16.0:4.6 branch is satisfied.
  • CC-A.16.0-8 When the history is represented by an independently selected TransformationFlowStructure, authors SHALL apply E.18 to that structure and use E.18.2 when a mathematical description is needed. A graph rendering alone establishes neither subject.

A.16.0:8 - Common Anti-Patterns and How to Avoid Them

  • Meta-wrapper inflation. Treat A.16.0 as obligatory around every move. Repair by using sufficient local A.16 publication content unless a later use depends on the history.
  • One-publication myth. Record a changed claim discriminator under the same episteme edition. Repair by identifying the different epistemes and only the lineage links whose predicates obtain.
  • Pattern and form collapse. Treat a pattern reference as if it were a publication form. Repair by naming the form and the cited pattern’s concrete definition, constraint, or test separately.
  • Form and face collapse. Treat seam publications as if they minted a second MVPK face family. Repair by naming form and face separately.
  • Multi-route and fork collapse. Treat several live routes for one selected episteme edition as if they were already several successor epistemes.
  • Hidden work crossing or invented responsibility handoff. Do not describe operationalization as purely linguistic when it required new world-facing work, and do not treat that crossing or next-use docking as a responsibility transfer. Publish the work boundary; open the separate A.16.0:4.6 branch only for an actual responsibility, commitment, permission, or authority change.

A.16.0:9 - Consequences

Readers can recover which epistemes supplied later claims, what changed or was lost, and how that history constrains the next use. The trade-off is more explicit publication of position claims, lineage links, move kinds, loss notes, next-use docking, and any actual responsibility handoff when history is worth publishing.

A.16.0:10 - Rationale

A later use may depend on lineage, branch structure, retirement, next-use conditions or an actual responsibility history. The account makes those facts recoverable when local notes do not supply them. Reuse an adequate existing history; the selected form is useful when it exposes a needed connection without adding unnecessary reconstruction.

A.16.0:11 - SoTA-Echoing

Practice question. What is the lightest history that lets a later reader recover which note supplied a claim, what changed or was lost, and how that affects the next use?

The selected line retains only the source and loss relations needed by that question. W3C PROV-DM, Recommendation of 30 April 2013, §§2.2.1.2 and 5.2.1–5.2.2, supplies the substantive provenance distinction: derivation connects an output to what it used, can be expanded when activity details matter, and is broader than revision. Adapt that selective detail in §§4.0a and 4.3. A PROV derivation or revision assertion supplies no automatic C.2.1 edition relation, truth warrant or language-state position; those claims still need their own facts and rules.

The alternative is ordinary version history with relevant diffs and change notes. Pro Git, second edition, §2.3, Viewing the Commit History, supplies a concrete implementation: patches expose textual changes and a graph exposes repository branches and merges. This is often sufficient and should be reused. Its limit for the present question is that a file parent or deletion does not by itself say which source claim was used, whether episteme continuity holds, or which omitted condition changes reliance.

For the same three notes in §14, both approaches can expose the missing restart window. The targeted history also makes two needed judgments explicit: S1 used S0 but failed the stated continuation rule; S2 returns directly to S0 and restores the observations and rivals needed by the diagnostic question. This requires no new incident observations. Its cost is a short semantic annotation after the same content comparison; its gain is that the next reader need not reconstruct why the capacity conclusion was withdrawn. Reject deriving those judgments solely from chronological adjacency or repository ancestry. When the existing change note already supplies them, §4.3 stops without another account.

The loss annotation has a separate practice basis. The Site Reliability Workbook (2018), chapter 10, “Missing context” and “Key details omitted”, contrasts an inadequate incident account with one that retains the context and facts needed for learning and action. Adopt that action-changing-detail criterion in §4.3 and §14’s restart-window loss. This is failure evidence for an unqualified summary, not a requirement to write a full postmortem or a source for FPF lineage identity. The selected history preserves an unresolved diagnostic question; it need not manufacture a settled cause or corrective action.

Reopen the choice of account when the receiving question needs an unrecorded branch, source use, lost condition or authority fact. If an existing note or diff annotation now makes all those facts recoverable, reuse it. If automated interchange becomes the need, compare an adequate structured provenance representation with this small human-readable account; prose alone may then cease to suffice.

A.16.0:12 - Relations

A.16.0:13 - Worked trajectories

A.16.0:13.1 - Multi-route state before fork

A routed operator cue may first keep intervention and inquiry routes live for one selected episteme edition in one RoutedCueSet. That is still a multi-route state. A lineage fork exists when independently identified distinct successor epistemes and the historical facts satisfy the selected fork predicate. Both successors may still be unpublished. Conversely, publishing the same edition twice creates two publication claims, not a fork.

A.16.0:13.2 - Inquiry trajectory with fork

An inquiry cue pack centered on a felt or trace-anchored discrepancy cue may first identify one selected episteme edition, then fork into:

  • notice -> stabilize -> route -> projection -> formalize, with a cue-derived prompt form expressing the explanatory branch, and
  • notice -> stabilize -> route -> projection -> operationalize

if one branch supports explanatory work while another supports immediate probe or control work. The account of that fork identifies the successor epistemes and obtaining lineage links, and discloses each branch’s relevant losses and next-use conditions. These disclosures describe the fork; their publication does not create it. If responsibility changes, keep the separately established responsibility-handoff conditions distinct as well.

A.16.0:13.3 - Operator trajectory with retirement

An operator alert note about a service disturbance may move:

notice -> stabilize -> route -> projection -> operationalize

If later evidence no longer supports one route, the admissible continuation may include explicit retirement of that branch rather than silent disappearance. The retirement ends the branch’s current use while preserving its history. Any episteme-continuity claim still requires its own obtaining relation. Any authority change still requires the separate relation in §4.6.

A.16.0:13.4 - Bridge-sensitive trajectory

A route-bearing comparative note may move through a seam publication and only later dock to a bridge overlay or viewpoint bundle. Apply F.9 or E.17.1 to the receiving use and reuse the established history needed there. A Bridge or viewpoint attachment supplies no missing lineage facts.

A.16.0:14 - Filled history: a restart incident loses its scope

This constructed incident concerns CheckoutSystem-17. All three notes below use Incident17Scheme, which fixes the System name, trace identifiers and time interpretation. History account H17 has source episteme S0 as its EntityOfConcern; the notes it describes have the checkout System as theirs.

The local incident-edition rule permits a note to continue S0 only if it uses S0, retains that System and scheme, preserves the reported observation window and observations, and explicitly marks any changed diagnosis or next question. It allows a diagnosis to be withdrawn or a question added; a scope-dropping summary fails the continuation condition. This is the applicable C.2.1 rule for this example, not a rule inferred from the filenames.

Entry and source useContent and position needed hereHistory result and receiving action
S0, the initial incident note, grounded in trace T17Three timeouts occurred during 09:00–09:02 after restart; the 09:04 request succeeded. Cold-cache startup and database-pool startup remain rival explanations. The named observations and rivals support ValueSet(AE)={AE2} and ValueSet(CD)={CD2} using the C.2.4/.5 starter anchors.Preserve the time window, later success and both rivals for the diagnostic question. The note establishes no permanent capacity shortage.
S1, a briefing composed from S0“Checkout is permanently undersized; add replicas.” The explicit claim/action supports AE3; the selected capacity route is CD3. It omits both the restart window and the later success, and drops the rival explanations.S1 has changed claim content and fails the stated edition-continuity rule. Record that failed continuation claim rather than linking it as the next valid edition. Its polish and closure establish no stronger warrant.
S2, a corrected note composed directly from S0 after S1’s loss is foundRetains both observations and rivals; adds “Which explanation accounts for the restart-only timeouts, and what observation would distinguish them?” It withdraws the permanent-shortage conclusion. Its explicit diagnostic structure gives ValueSet(AE)={AE3}; restored rivals give ValueSet(CD)={CD2}.C.2.1 continuation from S0 to S2 obtains: distinct content, actual source use, same System/scheme, retained observations and an explicitly changed question satisfy the stated rule. Do not infer continuation from S1.

The A.16 reopen guard is met for the earlier capacity-route commitment: recovering S0 reveals the lost scope and unsupported elimination of rivals. The local next-use rule requires at least AE2, both named rivals and the observation window to be recoverable; it permits a return to B.5.2.0’s diagnostic-question entry, not authorization to add replicas. S2 meets that guard. The receiving practitioner can now frame the discriminating inquiry while withholding the permanent-capacity conclusion. Any additional measurement remains to be planned and performed under its applicable rule; admit a distinct Work only when that claim is needed.

This short history is needed because the loss occurred between notes and changes how the later action proposal may be used. If the same facts and return were already recoverable in one adequate local move note, §4.3 would stop there. No successor publication, fork, responsibility transfer or history-of-H17 is required for this result.

A.16.0:15 - Practitioner check

A practitioner should ask:

  1. Is the author describing history over the declared language-state U.CharacteristicSpace, or only narrating progress informally?
  2. Is the selected episteme edition distinct from the grounds, publication form, occurrence, face, and carrier?
  3. Does the receiving use need a fuller history, or does existing local content already suffice?
  4. Are multi-route state and lineage fork being kept distinct?
  5. Are derivation, supersession, fork, merge, or retirement links visible where the reading depends on them?
  6. Does the current claim concern an episteme edition, a seam or endpoint publication form, or—when bounded availability matters—an EpistemePublicationRelation occurrence? Are those positions kept separate, and is the endpoint test named?
  7. If formalize or operationalize required world-facing work, is the work-boundary crossing explicit? If responsibility, commitment, permission, or authority also changed, are its participants, relation, object or action, scope, interval, and required instituting act stated separately?

A.16.0:End

A.16.1 - PreArticulationCuePack: Preserve an Early Cue Before Choosing Its Use

Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative

Plain-name. Pre-articulation cue pack.

Use this when. Use this pattern when the first supported publication is a preserve-worthy cue nucleus that should remain visible while its interpretation and next use remain open.

What goes wrong if missed. Early cues either vanish, become vague “signals”, or are cited prematurely as a route decision, supported explanation, evaluation, method, or Work record.

What this buys. One admissible preservation form for low-articulation but meaningful cue content, with enough witness, anchor, and route-candidate discipline for later successor publication without treating the endpoint as established.

First output. One PreArticulationCuePack with an explicit cue nucleus, preservation rationale, primary witness or anchor when one is load-bearing, and any early lane candidates or route-candidate hints that are already visible.

Typical next patterns. Use B.4.1 when route plurality or route selection becomes publishable; B.5.2.0 for cue-derived abductive prompting; A.6.P when a relation-bearing claim needs repair for a named receiving use and you can name at least one grounded candidate relation, its participants, and a discriminating check; A.6.A to recover an unclear action-oriented claim or question and return it to its subject pattern; C.16.Q under its own entry conditions; and A.16.2 when reopening or retirement is warranted. Use C.2.4 for any additional local articulation threshold declared for a receiving branch.

Common neighboring-pattern mistakes. Do not publish a cue pack as a selected-route decision, anomaly statement, evaluative ascription, claim or question recovered through A.6.A, or Work record; if route selection is already explicit, use B.4.1; if endpoint semantics are already stable, use the applicable endpoint pattern to test them and publish the corresponding form; if backoff or retirement is the active problem, use A.16.2.

A.16.1:1 - Problem frame

Some U.Episteme content is worth preserving before it is ready for route or prompt publication, relation or evaluative repair, wording recovery under A.6.A and the resulting subject-specific use, method or work use, or endpoint admission. PreArticulationCuePack therefore exists as an early publication form for such pre-threshold cue content. Keep it accessible for as long as the receiving use needs it.

The cue pack is earlier than RoutedCueSet. It may carry early directional hints, but it does not yet contain a selected route, route-selection status, or route rationale.

A.16.1:2 - Problem

Without an explicit cue-pack publication form, such epistemes either disappear, are prematurely forced into AnomalyStatement or Characteristic, or leak into prose as vague cue or signal language, loose evaluative talk, fit-talk, premature work-possibility claim, or premature reliance-possibility claim.

A.16.1:3 - Forces

ForceTension
Low-articulation shape vs publishabilityPreserve early cues without pretending that the preserved episteme already carries a stabilized endpoint claim, is expressed in a later publication form, or has an endpoint publication occurrence.
Pre-route preservation vs later B.4.1 publicationLet cue preservation stand independently before route publication is justified.
Carrier awareness vs stack duplicationRespect traces, bodies, and model states without creating a second carrier stack beside A.7.
Plurality vs auditabilityAllow several plausible continuations without collapsing the cue pack into a route record.

A.16.1:4 - Solution

PreArticulationCuePack is a publication form for preserving a cue while its interpretation and next use remain open. A filled account can state what was observed and why it merits preservation. That content does not by itself establish a causal explanation, evaluative result, selected route, Method or Work occurrence. When rendered, the form appears on an ordinary MVPK face; it defines no face kind.

A cue pack may exist before any route is selected and even before route-candidate hints can yet be named clearly. When route plurality or selection becomes explicit enough to publish, use B.4.1 to state it and publish the next form as a RoutedCueSet.

A.16.1:4.0a - Publication form and filled account

PreArticulationCuePack names the publication form defined here; it is not an admitted U-kind. A filled claim-bearing preservation account is an episteme only when its claim content, EntityOfConcern and effective ReferenceScheme satisfy C.2.1. The form, that episteme, its cue and witnesses, its carrier and any E.24.PUB publication occurrence remain distinct.

A.16.1:4.1 - Core shape

cueNucleus is required. Fields marked ? are optional and selected for the receiving use:

  • cueNucleus
  • preservationRationale?
  • laneCandidates?
  • routeCandidateHints?
  • valenceProfile?
  • languageStateClosureDegreeRef?
  • languageStateFacetProfileRef?
  • detector?
  • primaryAnchor?
  • candidateAnchors?
  • primaryWitnessRef?
  • witnessRefs?
  • exemplars?
  • contrasts?
  • traceRefs?
  • embodimentRefs?
  • modelStateRefs?
  • scope?
  • GammaTime?

cueNucleus names what is being kept visible. When several sources contribute, state what unifies their traces, tensions or contrasts into this cue; a collection of unrelated fragments supplies no common nucleus.

When the nucleus is still unclear, try arranging the available material as in the operator example.

Use primaryWitnessRef or primaryAnchor when one witness or anchor carries the preservation need. If several grounds are jointly essential, preserve that joint basis instead of inventing a single primary one. Add secondary material only for the contribution it makes to understanding or using the cue.

laneCandidates and routeCandidateHints are early directional hints only. They are not a selected route, route rationale, or route-selection status. Those belong to RoutedCueSet under B.4.1.

The referenced facets keep their own definitions. primaryAnchor, candidateAnchors, contrasts, and exemplars commonly provide anchor material for AE under C.2.4; languageStateClosureDegreeRef docks to C.2.5; source and use claims follow C.2.6, and representation-factor refs follow C.2.7; languageStateFacetProfileRef may bundle them through C.2.LS.

In this cluster, a cue is a salient epistemic nucleus extracted from witnesses, traces, felt tensions, model outputs, work-possibility hints, reliance-possibility hints, contrasts, or other grounds and made preservable as a pack. A raw signal-like trace counts as a cue only when that salience and preservability have been made explicit; otherwise it remains a trace, not yet a cue. For evidence use, establish the grounds for the named target claim. Use A.10 when the source-to-use account is implicit or must remain replayable.

A.16.1:4.2 - Use boundary

The cue pack preserves the nucleus, its grounds and any visible directional hints. Valence, urgency, discomfort, promise or attraction may explain preservation; they do not by themselves establish an evaluation, abductive prompt, selected route, or an action-oriented claim recovered through A.6.A.

If the content already contains a route decision or an endpoint result, apply its governing pattern and use the corresponding publication form. Choosing the cue-pack form does not establish that the later test has passed.

A.16.1:4.3 - Transition discipline

A cue pack may feed:

  • B.4.1 once route plurality or route selection deserves explicit publication;
  • B.5.2.0 to constitute and check a cue-derived abductive prompt;
  • A.6.P when a relation-bearing phrase needs its direct relation, participants, direction, or detail restored for a named receiving use;
  • A.16.2 when prior stabilization must be reopened, backed off, respecified, or retired.

A.16.1:5 - Archetypal Grounding

A cue pack says “there is a preserve-worthy cue nucleus here” without falsely claiming that a later route or endpoint form already exists.

System case. A console alert with traces and tension indicators may be worth preserving as a cue pack before there are grounds to publish route selection, gate logic, or work execution.

Episteme case. A researcher’s stabilized discrepancy cue from bodily observation or inspection of a trace with exemplars and contrasts can be published as a cue pack before it becomes a routed cue set, an abductive prompt, or an anomaly statement.

A.16.1:6 - Bias-Annotation

This pattern biases authors toward preserving low-articulation meaningful cues instead of discarding them or disguising them as later publication forms with higher closure, a selected route, or a passed endpoint test. The counter-bias is deliberate as well: a cue pack must still name what is being preserved and why.

A.16.1:7 - Conformance Checklist

  • CC-A.16.1-1 Cue preservation SHALL NOT be presented as sufficient grounds for an endpoint claim, Characteristic, Method, Work occurrence or route decision. A filled account may state its observations and preservation grounds.
  • CC-A.16.1-2 A cue pack SHALL make cueNucleus explicit.
  • CC-A.16.1-3 When one witness or anchor carries the preservation need, primaryWitnessRef or primaryAnchor SHALL be explicit. When several grounds are jointly essential, their joint contribution SHALL remain recoverable.
  • CC-A.16.1-4 laneCandidates and routeCandidateHints MAY be published early, but selectedRoute, routeRationale, and route-selection status SHALL NOT be included in the cue pack.
  • CC-A.16.1-5 If route-candidate hints are not yet nameable, publication is still admissible only when preservationRationale and grounding make the preservation need explicit.
  • CC-A.16.1-6 Language-state readings, source and use claims, and representation-factor details MAY be referenced; use C.2.LS for the facet profile, C.2.4 for articulation explicitness (AE), C.2.6 for source and use conditions, C.2.5 for closure degree, and C.2.7 for representation factors.
  • CC-A.16.1-7 A cue pack SHALL NOT claim that an endpoint test passed or that a stronger use is admitted; use the applicable endpoint pattern to test and publish that later result.

A.16.1:8 - Common Anti-Patterns and How to Avoid Them

  • Cue as established conclusion. Apply the appropriate test before treating a preserved observation or tension as an explanation or other endpoint result.
  • Cue as route record. Do not let selectedRoute, route rationale, or route-selection status appear in cue-pack prose.
  • Cue without nucleus. Do not publish only refs and carriers while leaving the preserved core unnamed.
  • Cue without triage. Do not treat all witnesses or anchors as equally load-bearing when one carries the preservation need.

A.16.1:9 - Consequences

The benefit is an admissible preservation form for early cues and a transition into B.4.1 route publication and the later patterns that define, constrain, or test endpoint claims. The trade-off is one more explicit publication form that must be named and maintained.

A.16.1:10 - Rationale

PreArticulationCuePack preserves content before route selection is justified, without requiring premature entry into A.6.P, B.4.1, or B.5.2.

A.16.1:11 - SoTA-Echoing

FPF proposal. The form preserves a recognizable observation or tension while its interpretation and next use remain open. Its contribution is a publication constraint; recognizing the phenomenon and testing an interpretation remain with the applicable domain methods.

A.16.1:12 - Relations

A.16.1:13 - Worked Examples and Invalid Publications

A.16.1:13.1 - Operator cue pack

The nucleus can emerge from arranging the available material. Put the T17 events in time order: “Three timeouts during 09:00–09:02 after restart; a successful request at 09:04.” Their contrast supplies the question “Which conditions differed between the failed and successful requests?”

An ordinary incident note can keep that line with the question and the reason for preservation: the different outcomes need to remain visible while their cause and next route are open. T17 is the primary witness. The note preserves this cue without selecting a route or publishing a causal conclusion.

If an existing incident note already carries this content and the source return, use it directly. On separate hand-off, keep the meaning of the cue in the note. A reference can supply further details when the recipient can access the source content and interpret it; otherwise include the details needed for the next use.

A.16.1:13.2 - Inquiry cue pack

An inquiry cue pack may preserve exemplars, contrasts, a discrepancy cue nucleus from bodily observation or inspection of a trace, and candidate anchor fragments. This is admissible even before route publication is needed or an under-specified relation-bearing claim requires A.6.P.

A.16.1:13.3 - Invalid publication to reject

It is invalid to publish a cue pack and then cite it as if it were already an anomaly statement, a routed cue set, an explanatory bundle, or a control obligation. The cue pack is only the preservation form.

A.16.1:14 - Authoring and Practitioner Checks

A.16.1:14.1 - Author prompt

A cue pack should answer four questions:

  • what is being preserved?
  • why is it worth preserving now rather than losing it?
  • which witness or anchor carries the preservation need, or which grounds are jointly essential?
  • which downstream directions, if any, are already visible without implying that a route has been selected?

A.16.1:14.2 - Practitioner check

A practitioner should check:

  • whether the pack has a clear cue nucleus;
  • whether primary witness or primary anchor triage is explicit when needed;
  • whether preservation is being treated as sufficient grounds for an endpoint conclusion or route decision;
  • whether route language is still an early directional hint rather than route selection.

A.16.1:14.3 - Carrier reminder

Use the carrier-analysis boundary in §20.2.

A.16.1:15 - Migration and Extension Notes

A.16.1:15.1 - Migration from vague cue or signal language

Source prose often says merely “there is a signal” or “something suggests possible work”. A conforming migration first asks whether the source is signal-like in the narrow telemetry or trace sense, or whether the load-bearing phenomenon is a broader cue nucleus, work-possibility hint, reliance-possibility hint, contrast, or figure-against-background shift. It then makes the cue nucleus and its grounds explicit, naming a primary witness or anchor when one carries the preservation need. Include route-candidate hints only when already visible.

A.16.1:15.2 - Local extension rule

Contexts may add local cue-pack fields only if they remain preservation aids rather than route-decision or endpoint semantics.

A.16.1:17 - Cue-Pack Lineage

A.16.1:17.3 - Multi-direction state versus lineage fork

Several lane candidates or several low-articulation route-candidate hints may live inside one cue pack. That is still one cue-pack publication.

A fork claim requires distinct successor epistemes or project records and facts satisfying the applicable lineage predicate. Identify those members, the obtaining links and relevant preserved or lost content; neither identification nor disclosure creates the fork. Making those epistemes available through the forms to an audience for a bounded use is a separate E.24.PUB claim. Practitioners should not treat pre-route plurality inside one cue pack as if it were already a forked lineage.

A.16.1:17.4 - Split and merge cases

One cue pack may later split into several route-bearing continuations if its preserved cue nucleus contains several tensions. Several cue packs may also merge if later stabilization reveals that they were fragments of one more coherent cue complex. Establish each claimed split, merge or continuation under its applicable predicate and show relevant preserved and lost content. Record successor publication separately when availability matters; disclosure alone establishes neither lineage nor continuity.

A.16.1:18 - Worked Cue Complexes and Practitioner Tests

A.16.1:18.2 - Practitioner test for under-specified packs

A practitioner may ask whether the intended recipient can name the cue nucleus and understand its preservation rationale from the account and the referenced material they can access and interpret. If the required meaning remains unclear, revise the account to supply it, retire the pack, or postpone publication.

A.16.1:18.3 - Practitioner test for covert endpoint capture

Check any proposed inference from the cue pack to an endpoint result, publication availability or authority. Apply the pattern that establishes the required claim; if its grounds are missing, retain the supported observation and withhold that additional conclusion. Preserve any independently established facts needed to understand the cue.

A.16.1:19 - Cue-Pack Continuation and Comparative Preservation Rule

A.16.1:19.1 - Continuation visibility

A cue pack should make visible which continuations apply: keeping the cue open, later route publication, a split or merge of cue packs, or retirement of the cue, publication, or branch.

A.16.1:19.2 - Preservation worthiness test

Keep a cue pack only when its nucleus would likely be lost or distorted without it. If the same cue already lives stably in a later receiving form with more closure, a published route selection, and any needed endpoint-use disposition, the cue pack may have become redundant.

A.16.1:19.3 - Comparative preservation rule

Compare cue packs for a named preservation use and criterion, recovering their nuclei and the grounds that criterion needs. Felt intensity or urgency may explain the need for attention; neither by itself establishes stronger warrant or endpoint admission.

A.16.1:20 - Witness and Carrier Triage

A.16.1:20.1 - Witness priority rule

When one witness anchors the cue nucleus, distinguish it from secondary material. When several are jointly essential, preserve their joint contribution. This lets the receiving practitioner retain the needed grounds during later route publication.

A.16.1:20.2 - Carrier overload boundary

A cue pack may cite traces, embodiment, model-state refs, or document fragments, but it should not absorb their full carrier semantics. When carrier analysis itself becomes central, use A.7 or the applicable carrier pattern instead of embedding that analysis into the pack.

A.16.1:20.3 - Early directional plurality rule

Plural lane candidates or plural route-candidate hints are not a flaw. Keep the visible hints with the cue. Use B.4.1 when publishing live routes or a selected route becomes useful; several early hints alone do not require that further publication.

A.16.1:End

A.16.2 - Reopen, SketchBackoff, Respecify, or Retire a Language-State Publication

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain-name. Admissible reopen / backoff / respecification.

Use this when. A published framing, route or use claim exceeds its grounds, or a branch should cease to be used. Choose the move in §4.1, retain the supported content and revise only the dependent claims affected by the change.

First useful result. Make the source, reason, surviving content and changed use recoverable in the existing publication or an accompanying note. Apply A.16:4.3 to any episteme-identity change. Use A.16.0 only when the receiving question needs a separate account of the history.

A.16.2:1 - Problem frame

A governed history across the language-state chart must support admissible retreat as well as tightening. When a route, publication form, or framing scaffold over-commits, teams need a way to reopen, back off, respecify, or retire a branch while making the change visible.

A.16.2:2 - Problem

Without an explicit retreat pattern, teams treat reopening as failure, hide regressions, silently mutate endpoint-bound or route-bearing forms back into exploratory cue-bearing publication forms with no audit trail, or let obsolete branches disappear without any visible withdrawal note.

A.16.2:3 - Forces

ForceTension
Reversibility vs trustAllow backoff without making the trajectory discipline look arbitrary.
Explicit retreat vs clutterName retreat and retirement without drowning the model in bookkeeping.
Witness retention vs revisionKeep what remains valid while explicitly discarding what no longer holds.
Framing revision vs repair-pattern boundaryAllow route-specification or framing-scaffold revision while leaving slot-explicit epistemic precision repair to its governing patterns.

A.16.2:4 - Solution

This pattern defines the retreat, reframing, and retirement side of the A.16 move family.

Identify the claim or question being reconsidered, its subject, the intended next use, the alternatives and the current grounds for closure. State which of those commitments remain supported. Choose a move by what must change: closure, the publication form, the framing or route specification, or current use. Apply A.16:4.3 to any resulting episteme-identity change.

A.16.2:4.1 - Move family

MoveWhen to use itWhat remains stableWhat may change
reopenthe inquiry or intended use remains appropriate, but closure was over-committedthe supported inquiry or intended use and relevant witnessesclosure, rival set, guards
sketchBackoffthe current publication form overstates articulation or stabilitywitnesses, traces, some anchorspublication form, articulation-explicitness value, route certainty
respecifythe inquiry or intended use remains appropriate, but the framing, route specification, or facet-profile reading is wrongthe supported inquiry or intended use and relevant witnessesframing, route specification, facet-profile reading
retirea cue, route-bearing publication, episteme, or branch is no longer current or no longer worth preservingrecorded history and any cited witnesses that still mattercurrent-use or retirement status, successor information, and any separately established relation change

One revision can both restore alternatives and replace a framing or route specification. State both reopen and respecify, with the grounds for each change. These names describe what changed; they prescribe no fixed order. Reopening alternatives alone leaves the framing in place, while replacing a framing does not establish its conclusions.

respecify is narrower than epistemic precision repair. Slot-explicit epistemic precision restoration, bearer repair, or endpoint-local lexical precision remains with governing patterns such as A.6.P, C.16.Q, and A.6.A.

A.16.2:4.2 - Required publication content

Make the following content recoverable for each retreat or retirement move; add a note only when the existing material is insufficient:

  • source publication form,
  • source articulation, closure, route plurality or selection, endpoint-use disposition, publication availability, and current-use status insofar as each is current,
  • trigger or counter-evidence,
  • target publication form, inquiry or intended use when one is selected; a retired branch may have no successor,
  • retained witnesses,
  • withdrawn assumptions, route claims, endpoint-use or current-use claims, and any authority, responsibility, permission, or commitment relation that separately changes,
  • required dependent updates under §20;
  • and successor information when the receiving use needs it. Identify a successor only under its applicable relation; distinguish a no-successor result supported by a negative criterion or complete closure basis from an unresolved successor question.

A.16.2:4.3 - Status and relation discipline

Reconsider each route selection, endpoint or gate conclusion, publication availability, current-use or retirement claim that depends on the changed basis. Revise those no longer supported and preserve unaffected claims. A past test result remains a historical fact; distinguish it from whether its conclusion still applies to the current use. The move does not by itself establish a change in authority, responsibility, permission, or commitment. If one of those relations changes, establish the change under its direct predicate, with its participants and the scope, interval, or instituting or ending act the rule requires.

If only one route claim, scope assumption or operational use fails, retain the surviving content. Follow its dependencies under §20 instead of resetting the entire publication.

A.16.2:5 - Archetypal Grounding

Backoff is admissible when the current publication form over-commits. Retirement is not erasure; it says that the cue, episteme, publication, or branch is no longer current for the named use while preserving its history.

System case. On a rollback cue, a practitioner may reopen a prior decision path instead of pretending the original operationalization still holds, or retire one branch once a better-supported successor line has taken over.

Episteme case. A formalized hypothesis may sketch-backoff to a cue pack when its framing collapses under new exemplars, or it may respecify its route specification while leaving slot-explicit epistemic precision repair to governing patterns.

A.16.2:6 - Bias-Annotation

The pattern pushes against false linear progress narratives. The cost is that teams must expose when closure, route selection, endpoint-use disposition, publication availability, or current use is being relaxed, replaced, or retired.

A.16.2:7 - Conformance Checklist

  • CC-A.16.2-1 Retreat or retirement moves SHALL cite the trigger or counter-evidence that justifies them.
  • CC-A.16.2-2 Reassess claims that depend on the changed basis. Revise an endpoint-use, gate, publication-availability or current-use conclusion when it is no longer supported; preserve the historical test result and unaffected claims.
  • CC-A.16.2-3 Reopen / backoff / respecify / retire moves SHOULD preserve witnesses and trace links whenever still valid.
  • CC-A.16.2-4 Target articulation, closure, route selection, endpoint-use disposition, publication availability, and current-use or retirement status SHALL remain separate and be explicit when the move substantively changes them.
  • CC-A.16.2-5 respecify SHALL NOT be used to transfer slot-explicit epistemic precision repair out of governing patterns.

A.16.2:8 - Common Anti-Patterns and How to Avoid Them

  • Shame-driven concealment. Teams hide the retreat. Publish the move.
  • Silent downgrade. The publication loses closure, a selected route, a passed endpoint test, publication availability, or current use, but no one updates the affected claim.
  • Retreat as erasure. Earlier witnesses disappear even though they remain valid.
  • Respecify as silent repair. respecify is used to hide an epistemic precision restoration that belongs to later repair governing patterns.
  • Silent branch disappearance. A branch stops mattering, but no retirement or supersession note is published.

A.16.2:9 - Consequences

The benefit is explicit reversibility, reframing, and retirement handling. The cost is making the changed use and its affected dependencies recoverable; existing publication content may suffice.

A.16.2:10 - Rationale

Language-state history is not one-way tightening. Without retreat and retirement discipline, A.6.P and endpoint forms would encode only one-way progress and would hide the cost of over-commitment.

A.16.2:11 - SoTA-Echoing

FPF proposal. The four moves distinguish reopening closure, reducing an over-committing form, changing a framing and ending a use. A.16:10 gives bounded incident-response and historical provenance comparisons; the move distinctions and admission rules here remain FPF’s own contribution.

A.16.2:12 - Relations

A.16.2:13 - Worked Retreat Trajectories

A.16.2:13.1 - Reopen an evaluative inquiry

A routed evaluative note may retain its evaluative question but move from high closure to lower closure when a rival frame becomes a live alternative again. This is reopen; a move to a less articulated publication form would additionally need the grounds for sketchBackoff.

A.16.2:13.2 - Sketch-backoff to cue pack

An account recovered through A.6.A may assert more than its grounds support. For example, a supposed pulling opportunity may have only a detector cue and no established physical predicate. First select the account-identity case under A.16:4.3 and C.2.1, then express the publication-form change:

source form: physical-opportunity account; move: sketchBackoff; target form: PreArticulationCuePack

Withdraw the unsupported claim and any route selection or endpoint-use claim that depended on it. This changes the account; a change to the physical opportunity or an actual authority relation requires that subject’s own predicate.

A.16.2:13.3 - Respecify without repair-pattern drift

A route-bearing publication may retain its intended use but replace one framing or route specification with another. That is respecify; make the replacement and its grounds visible. Apply the governing pattern separately if a semantic slot also needs precision repair.

A.16.2:13.4 - Retire an obsolete branch

A route-bearing branch may later become obsolete because another branch now carries the governing pattern and witness support for the current use. The admissible continuation is explicit retire, not silent disappearance.

A.16.2:15 - Migration Notes

A.16.2:15.1 - Migration from regression language

Older language often talks about “going backwards” or “regressing”. The preferred migration is to name whether the change is reopen, sketch-backoff, respecify, or retire, and which route, endpoint, publication, current-use, or actual relation claim changes.

A.16.2:15.2 - Integration reminder

When retreat affects governing patterns such as A.6.P, A.6.A, C.16.Q, or A.15, update the affected subject result, recovered action claim or question, evaluation, Work hook, or current-use claim instead of leaving a stale downstream assertion.

A.16.2:17 - What each retreat preserves and withdraws

A.16.2:17.1 - Reopen

reopen retains the inquiry or intended use while withdrawing closure. It reintroduces rival possibilities and preserves the other supported claims; the entire earlier publication need not have been inadmissible.

A.16.2:17.2 - Sketch-backoff

sketchBackoff withdraws the closure, route selection or stronger-use disposition that the available grounds no longer support; it preserves the historical fact of any earlier test. It typically preserves witnesses, exemplars, or cue anchors while withdrawing the over-committing publication form. Establish any change in authority under its own predicate and facts, including an act when required; a changed publication form alone does not establish that change.

A.16.2:17.3 - Respecify

respecify retains the inquiry or intended use but changes its framing, route specification or facet-profile reading. Retain the supported content and identify any changed episteme under C.2.1. Assert continuity only when its relation obtains; apply governing patterns for semantic slot repair.

A.16.2:17.4 - Retire

retire ends current use of the cue, episteme, route-bearing publication, or branch while preserving its history. Report supported successor information or an unresolved successor question as §4.2 requires. Publication availability and any actual authority relation remain separate claims.

A.16.2:18 - Worked Recovery Cases

A.16.2:18.1 - Reopening a routed evaluative note

An evaluative note may have reached a high closure state under one route, but new contrasts give the reviewer grounds to reconsider a serious rival. reopen is admissible when the evaluative question and its subject remain supported but the closure claim must be relaxed. Retain the witnesses that still support the inquiry.

A.16.2:18.2 - Sketch-backoff from prompt to cue pack

An abductive prompt may later prove over-committed because its open question was formulated before the cue anchors had stabilized. The admissible recovery is to sketch-backoff to PreArticulationCuePack, preserving the cue carriers while withdrawing the prompt-readiness and current-use claims.

A.16.2:18.3 - Respecifying a route specification

A route-bearing publication may keep the same general direction but replace one route specification with another when later review shows that the original framing selected an unsuitable governing pattern within that broader question. The point of respecify is to make that replacement visible without pretending the earlier route specification never existed.

A.16.2:18.4 - Retiring a route branch

A route-bearing branch may later be withdrawn because better-supported grounds, clearer closure, or a more adequate successor publication now carry the work. retire keeps that withdrawal visible instead of letting the branch vanish into later prose.

A.16.2:19 - Review Matrix for Retreat Integrity

A reviewer can test retreat integrity with five questions:

  1. Was the trigger explicit? If not, the retreat risks becoming retrospective narrative repair.
  2. Were the affected claims updated? If the earlier route selection, endpoint admission, gate result, publication availability, current-use claim, evidence-use basis, or actual authority relation no longer applies, revise that dependent claim under its direct pattern.
  3. Did valid witnesses survive? If all earlier grounding disappeared without reason, the retreat probably became erasure.
  4. Was the move kind correctly named? Reopen, sketch-backoff, respecify, and retire solve different problems; confusing them obscures what changed.
  5. If the next use needs successor information, is its basis clear? Distinguish an obtaining successor relation, a supported no-successor result and an unresolved question.

A.16.2:20 - Required Downstream Repairs

A.16.2:20.1 - Stale downstream publication/work-target rule

A retreat or retirement often leaves stale downstream publications or Work targets behind: prompts, claims or questions recovered through A.6.A, evaluative notes, requirement candidates, or Work hooks that were admissible only under the prior closure, route selection, or endpoint-use disposition. A conforming retreat should therefore name which downstream publications or Work targets remain valid, which must be revised, and which must be withdrawn.

A.16.2:20.2 - Narrow retreat propagation

Retreat propagation should be as narrow as truth permits. If only one framing scaffold failed, then only the downstream publications or Work targets that depend on that scaffold need revision. Over-broad rollback is wasteful; under-broad rollback leaves false route, endpoint, publication, or current-use claims in circulation.

A.16.2:20.3 - Retreat timestamping and witness continuity

Where several revisions exist, the changed publication or accompanying note should identify the earlier publication and retained witnesses. State which obtaining relation, if any, supports episteme continuity. Without that linkage, readers may not know whether two nearby texts are alternative drafts or a retreat sequence.

A.16.2:21 - Comparative Retreat Rule

A.16.2:21.1 - Retreat kinds are not interchangeable

reopen, sketchBackoff, respecify, and retire solve different problems. Comparing them as if they all meant “we stepped back” erases the closure, framing, route, endpoint-use, publication, or current-use change each one makes.

A.16.2:21.2 - Honest recovery over softening prose

Authors in a context may prefer softening language such as “refined further” or “adjusted slightly” even when a retreat or retirement occurred. A.16.2 rejects that habit. If closure dropped, framing was withdrawn, route selection or endpoint use changed, or a branch was retired, name the move directly.

A.16.2:21.3 - Boundary to silent editing

For a reviewable retreat, keep the relevant earlier claim and the reason for its change recoverable. Existing version history or publication content can supply that account. A separate note is needed only when that material is insufficient; a continuity claim still requires its own relation.

A.16.2:End

A.17 - Canonical “Characteristic” (A.CHR-NORM): Name What Is Measured

Status: Stable

Use this when. A measurement description leaves unclear what aspect is measured, which entities it concerns, or how its value differs from a Score. First name the Characteristic and its bearer or tuple; then recover the Scale and any calculation or preference used. An already clear domain description needs no extra terminology table.

A.17:1 - Context

A measurement needs a recognizable aspect, its bearer or participants, and a way to express the result. C.16 supplies the CSLC discipline: define a Characteristic, choose a Scale and any applicable Unit, and report a Level/Value as a Coordinate on that Scale. A ScoringMethod may then map Coordinates to a Score for a declared evaluation. A.17 fixes the vocabulary and arity of the measured aspect so that terms such as axis, dimension, feature or metric do not hide these different meanings.

A.17:2 - Problem

When measurement concepts are not kept distinct, several issues arise:

  • Polysemy at the anchor. Teams say “dimension” or “feature” but mean slightly different things, so the trait being measured is ambiguous.

  • Arity mistakes. A relational quality (e.g. similarity between two items) might be treated as if it were an intrinsic property of one item, or vice versa, leading to logical errors.

  • Expression conflation. The aspect being measured is often mixed up with its expression – for example, using “scale” or “axis” to mean both the quality and its unit or range. This leads to unsafe arithmetic (averaging ordinal ranks, comparing raw numbers from incompatible scales, etc.) because values get interpreted out of context.

A.17:3 - Forces

  • F1 — Recoverable measured aspect. A reported number needs the answer to “value of what?” before it can be interpreted as a measurement.

  • F2 – Arity clarity. Some characteristics apply to a single entity (e.g. its mass or length), while others inherently relate multiple entities (e.g. distance between two points, coupling between modules, agreement between judges). If arity isn’t explicit, claims and calculations become corrupted.

  • F3 — Scale integrity. Scale types constrain meaningful operations. A numerical encoding of ordinal ranks does not by itself justify their arithmetic mean; interval and ratio values retain their applicable unit and transformation rules. A calculation also needs the relation or ScoringMethod that gives its result meaning.

  • F4 - Combining measurements. A measurement model relates quantities to obtain another quantity; a ScoringMethod combines values into a score for a declared evaluation. Each calculation needs its applicable relation and Scale operations. A common numerical encoding alone supplies neither.

  • F5 — Disciplinary meanings. The same distinctions can describe a lab temperature, a software-cohesion rating or a judged performance. Each retains its domain definition, bearer, Scale and conditions of assessment.

  • F6 - Revisable state descriptions. Development can change the Characteristics and state distinctions that matter. The description should support the changes, returns and further questions needed by the practice, including revision of its state space or transition law.

A.17:4 - Solution

Establish “Characteristic” as the one canonical construct for “what is measured.” In every FPF context, the aspect or trait being measured MUST be referred to as a Characteristic. This term replaces “axis” or “dimension” when they are used as names for the measured aspect; Plain aliases must keep that mapping clear. By fixing a single name and schema, we separate a Characteristic from its Scale (and Unit), and from any observed Value/Level on that scale. The solution also differentiates single-entity vs multi-entity cases and binds all measurements to the standard CSLC sequence.

Recover the same aspect. Identify a Characteristic by the aspect it distinguishes, the domain and arity of its possible subjects, the roles of an ordered subject tuple when relevant, and the conditions constitutive of that aspect. A changed reading, bearer, observation window or description does not by itself define a new Characteristic. A different Scale can express the same aspect through a justified conversion. Conversely, an unchanged name does not preserve the Characteristic if it now distinguishes another aspect or changes the subject roles. Preserve the original definition and establish the correspondence needed by the receiving comparison; unresolved equivalence is not identity. A content evaluation and a physical observation can both use this rule without being the same measurement practice.

To enforce this solution, the following rules apply:

  • A17-R1 (Canonical term). In all normative models and specifications, the measured aspect SHALL be referred to as a Characteristic. “Axis” and “Dimension” are not technical substitutes for the measured aspect.

  • A17-R2 (Entity vs. relation subtype). Each Characteristic MUST declare its intended arity. An Entity-Characteristic applies to exactly one bearer (e.g. Temperature of a reactor, Evolvability of a software module), whereas a Relation-Characteristic applies to an ordered tuple of two or more bearers (e.g. Distance between two sensors, Coupling between modules, Agreement among reviewers). The arity is part of the definition and must be explicit wherever it’s not obvious from naming.

  • A17-R3 (Characteristic space). When several Characteristics form a declared space, identify their slots, Scales and admissible values under A.19. State the constraints and additional structure required by its use. Use A.3.3.CC when compatible combinations must be constructed: it selects variables and constraints and compares implicit descriptions, parametrizations and finite sets. A.3.3 completes the state and transition account when the question concerns modeled change.

  • A17-R4 (Lexical guardrails). When naming the measured aspect, its scale, its value or position, or an evaluative result, normative text SHALL use the corresponding governed term: Characteristic, Scale, Unit, Level/Value, Coordinate, Score, Normalization or ScoringMethod. Do not use axis, dimension, metric, grade or property as an undeclared substitute for those constructs. A disciplinary term naming another defined subject keeps that meaning; a mathematical dimension or metric, for example, is not renamed Characteristic. A Plain alias may be used when its mapping is clear. Apply E.10 to an unresolved lexical question.

  • A17-R5 (Symbol policy). The Γ_ prefix is reserved for algebraic operators under E.10:8.3 and E.10.P. Each operator retains its defining laws, including those for holonic composition or a declared scale-lawful fold under A.19.ULSAM. 𝒢 denotes a ScoringMethod from Coordinates to a Score. Documents SHALL NOT reuse Γ for a ScoringMethod.

  • A17-R6 (Scale order and preference). For an ordered Scale, use its order to compare values of the Characteristic: a higher temperature value means hotter. A use that ranks values by desirability SHALL declare its preference rule, such as higher-is-better, lower-is-better, a target or range, or another ordering. Describing or comparing magnitudes requires no preference rule.

  • A17-R7 (Scoring against preference). A ScoringMethod SHALL state how its score order represents the declared preference. Where one input is higher-is-better or lower-is-better, improving that input while holding the others fixed MUST NOT worsen the score, for admissible inputs under the stated conditions. Target-based preference is checked against its declared target or loss rule; the preferred direction may change across the target. A quantity calculation or unit conversion uses its measurement relation and Scale rules under A.18/C.16.

  • A17-R8 (Arity declaration). Authors SHALL identify whether a Characteristic applies to exactly one bearer or to an ordered tuple of two or more bearers, and declare the tuple roles. For example, a cohesion Characteristic defined for one module is unary; a coupling Characteristic defined for an ordered pair of modules is relational. This arity declaration suffices for direct use; a receiving typed interface can require a C.3 classification when it needs a recurring membership decision.

  • A17-R9 (Relational readings). For a Relation-Characteristic, the admissible subject tuples belong to its declared domain; the Scale supplies the admissible values attributed to those tuples. A reading SHALL identify the tuple it concerns and express its result on that Scale.

  • A17-R10 (Characteristic and description). Distinguish the Characteristic from an episteme that describes it. A rubric, catalogue of levels or examples can contribute to that description; identify a separate episteme under C.2.1 when the receiving use needs its claim content, EntityOfConcern and effective ReferenceScheme.

A.17:4.1 - CharacteristicSpace & Change Reasoning (Normative/Clarifying)

R17 - State-space use. When a change model uses a CharacteristicSpace, declare its Characteristics, Scales, any applicable units and admitted combinations under A.19. Add topology, distance or another structure when the inference relies on it.

R18 - Allowed changes and state recognition. For a model of change, state the allowed continuations and their conditions through A.3.3. Use a state predicate or checklist when the receiving use needs to recognize a condition. A.2.5 governs the case of a condition on an assignment to a system role; a gate or assurance use supplies its own required support.

I7 — Vector interpretation. A vector may collect multiple Scale-specific Coordinates for multi‑Characteristic reasoning; composition into a single Score, if desired, requires an explicitly identified applicable ScoringMethod 𝒢 on that vector.

A.17:5 - Archetypal Grounding (System & Episteme Examples)

In a physical system (U.System): Consider a Distance Characteristic defined for a pair of physical objects. For example, two machines in a factory have a Distance of 3.5 meters between them. Here Distance is a Relation-Characteristic (applies to the pair), with an associated Scale (e.g. a ratio scale in meters), and the measured 3.5 m is a Coordinate on that scale. If we instead look at an Engine Temperature Characteristic (unary), an engine might have a Temperature of 350 K at some moment – Temperature (the Characteristic) is separated from how its value is expressed (the kelvin temperature Scale) and the reading (350, a Coordinate on that scale). A value of 360 K is hotter than 350 K. Whether it is preferable depends on the intended operation: heating and cooling can prefer opposite changes while using the same temperature Scale.

In an epistemic context (U.Episteme): Consider a local Characteristic describing which requirements of a specification-expression rubric are met. Its ordered levels can require stable terms; stable terms plus explicit acceptance predicates and interpretation; and all those conditions plus expressed derivations for specified obligations. The criteria are nested by declaration. A specification at the last level satisfies the earlier expression requirements, but this supplies neither a universal rank of languages nor evidence that its derivations were checked. C.2.3 governs the formality assessment and any mapping to this local summary. The Characteristic names what is assessed, the Scale defines its levels and order, and the Coordinate reports the document’s assessed level. Comparisons use that same rubric; its ordinal encoding alone does not justify averaging the levels. For a quantitative example, define the local Characteristic as the proportion of an article’s reviewed claims meeting a stated verification criterion. If 85 of 100 reviewed claims meet it, the Coordinate is 85% on the proportion Scale. Retain the reviewed set, criterion and assessment method; this result does not by itself estimate the reliability of unreviewed claims.

A.17:6 - Bias-Annotation

A shared term can conceal different measured aspects. When adapting a disciplinary term, recover its bearer or tuple, Characteristic and Scale before reusing a value. Quantitative and qualitative measurements retain the different operations their Scales allow. Development may require revising the selected Characteristics and the model relating their changes; A.3.3 supplies that construction.

A.17:7 - Conformance Checklist

When authoring or reviewing FPF-compliant measurements, check the following:

  1. Declared Characteristic: Have you explicitly named a Characteristic for each aspect being measured, instead of using generic terms? (e.g. use “Reliability” as a Characteristic name rather than saying “this dimension”).

  2. Arity Explicit: Is it clear whether the Characteristic is unary or relational? If a metric involves a relationship, are the participating entities (pair, tuple, etc.) identified in its definition?

  3. Separate Scale/Unit: For each Characteristic, have you defined the Scale (and Unit, if applicable) separately, rather than embedding units or ordinal terms in the name of the Characteristic? (e.g. “Length (m)” should be captured as Characteristic = Length, Unit = meter).

  4. Scale-appropriate operations: Are you only performing comparisons or calculations that make sense for the declared scale type? (An ordinal encoding alone licenses no arithmetic mean; interval/ratio calculations retain their transformation and unit conditions.)

  5. Calculation or scoring: Does a quantity calculation use a stated relation with compatible quantities and Scale operations? If values are combined into an overall Score, does the ScoringMethod state the preference it represents and preserve the declared preference in its score order?

  6. Canonical terminology in use: Do formal descriptions distinguish Characteristic, Scale, Level/Value, Coordinate, Score, ScoringMethod and Unit, with any Plain alias explicitly mapped? Keep disciplinary terms that name different defined subjects instead of mechanically renaming them Characteristic.

  7. State use: When Characteristics describe modeled change, are their admitted combinations and the transition law sufficient for the question under A.3.3? If a state condition is being recognized, is its predicate and required support determined by that receiving use?

Lexical checks can locate inconsistent terms; deciding the measured aspect, admissible operation and applicability requires the corresponding semantic rules.

A.17:8 - Consequences

The distinctions support the following uses:

  • Recoverable measurement meaning: a reader can identify the Characteristic to which a reported value belongs.

  • Separate aspect and expression: the Characteristic names what is measured; the Scale defines its admissible values and structure, with a Unit where applicable.

  • Recoverable participants: unary and relational Characteristics expose whether a value concerns one bearer or a tuple, such as the distance between two objects.

  • Cross-domain construction: temperature and a verified-claim proportion can each be described through Characteristic → Scale → Coordinate. Their shared structure supplies no common desirability order. Combining them into a Score requires an explicit ScoringMethod with its preference and applicability conditions under A.19.USCM.

  • Revisable change accounts: Characteristic meanings and Scales remain explicit as a state model changes. Revising a constraint, input or law can change which states are reachable; adding a Characteristic can supply predictive information that an earlier description omitted.

The cost is identifying disciplinary meanings and revising ambiguous descriptions. A shared term reduces one source of confusion; it does not establish measurement accuracy, evidence quality or a justified scoring model.

A.17:9 - Rationale

The distinction between Scale order and preference follows the different questions they answer. VIM3 §1.27 orders quantity values by magnitude. Evaluation adds a judgement about which values are desirable for a use. VIM3 §1.22 supplies the separate notion of a relation between quantities. FPF adopts these measurement distinctions and places use-dependent preference with A.19.ECS and the applicable comparison or scoring Method.

A.7 keeps the measured aspect distinct from its description and result. For example, a requirement category, a measured Characteristic and an evaluative Score may all have been called a dimension; identifying their different functions lets the reader select the corresponding rule.

The historical distinction among nominal, ordinal, interval and ratio Scales identifies which transformations preserve the represented meaning. FPF uses those distinctions to constrain calculations. A domain model or ScoringMethod may justify an additional operation; a shared numerical encoding alone cannot.

Distinguishing entity and relation Characteristics keeps the bearer of a measurement recoverable. A.3.3 can use the declared Characteristics to describe a state; an assurance argument can name the aspect for which it uses a measurement. Quantity calculations use their mathematical relation and applicability conditions; evaluative scores additionally need the preference that the scoring method represents. This lets a reader distinguish a derived physical value from a judgement about that value.

The question determines the required state description. A model may need repeated states, several continuations or a stopping condition. Development can revise that model and open new questions. A state-recognition checklist serves a use that needs such recognition; it does not supply the transition law.

A.17:10 - Relations

  • Builds on: C.16 for measurement construction and A.7 for the distinctions among a Characteristic, its description and its result.

  • Constrains: measurement claims in other patterns. A.3.3 state variables, A.2.3 promise acceptance conditions and B.3/D.3 assurance calculations retain the Characteristic, Scale, participants and applicable calculation rule required for their use.

  • Coordinates with: A.18 (CSLC-KERNEL), which defines the minimal Characteristic/Scale/Level/Coordinate Standard in detail. A.17 provides the vocabulary and basic distinctions (what is a Characteristic, and its arity), while A.18 applies this to ensure each measurement template is well-formed. Also coordinates with C.2 KD-CAL and the A.19/C.16 characterization stack; those patterns use the Characteristic/Scale constructs to build domain-specific metrics (e.g. knowledge quality scores) and rely on A.17’s canon for consistency.

  • Coordinates with: E.10 for governed terms and clear Plain aliases; F.7 when a table helps display the named source-local comparison; F.9 when the receiving claim needs a semantic correspondence or difference between local meanings from different semantic contexts. A common name alone establishes no equivalence between disciplinary meanings.

A.17:End

A.18 - CSLC in Kernel (Characteristic ⟷ Scale ⟷ Level ⟷ Coordinate) (A.CSLC‑KERNEL)

Status: Stable

Use this when. A reported value or proposed calculation leaves its measured aspect, Scale or permissible interpretation unclear. Recover those meanings from an existing adequate measurement template, or define the missing parts below. CSLC makes the value interpretable; the receiving use still selects its measurement and inference rules.

Aliases (for narrative use only): “Axis” (≈ Characteristic), “Point” (≈ Coordinate). (These colloquial aliases may be used in Plain language explanations, but never in formal identifiers or normative text.)

A.18:1 - Problem Frame

Characterizing an aspect of an entity or a relationship between entities can mean recording a physical quantity, an architectural property or a performance rating. The characterization must:

  • remain domain-neutral (work for engineering metrics, subjective scores, etc.),

  • support magnitude comparison when values have the same Characteristic and Scale and compatible measurement conditions; a declared conversion may establish that common basis, and

  • accommodate both ordered tiers (qualitative levels like Low/Medium/High) and numeric magnitudes (continuous or interval values) without mixing them up.

The CSLC pattern (Characteristic–Scale–Level–Coordinate) binds each measurement template to one Characteristic and one Scale. Each reported value belongs to that Scale; a named Level is optional for a discrete or tiered Scale. Reusing the declared meanings lets a receiving practitioner determine whether two readings can be compared.

A.18:2 - Problem

Uninterpretable measurements. A reported “4”, “High” or “9.81” needs its Characteristic, Scale and measurement conditions to be interpreted as a measurement. Across disciplines, “5” could encode an ordinal risk rank, a length in meters or a satisfaction assessment under a stated model. Common failures include:

  • In an ordinal Scale such as Novice < Skilled < Expert, the order is meaningful; assigning 1 and 3 to its labels supplies no distance that would justify their arithmetic mean.

  • Interval and ratio calculations require compatible units, the Scale’s transformation rules and the relation being calculated. Combining seconds and minutes requires conversion; a ratio calculation also depends on the meaning of zero.

A practitioner needs the measured aspect, its Scale and the rule for the proposed operation. Otherwise equal numerical encodings can hide incompatible meanings, such as a 4-star rating and 4 seconds. Qualitative tiers need no invented distances between their labels.

A.18:3 - Forces

  • F1 — Disciplinary interpretation. Physical measurements and human assessments can use the same structural distinctions while retaining their different domain assumptions and methods.

  • F2 — Comparability and alternative Scales. Compare values under a common Characteristic and Scale with compatible conditions under C.16. The same Characteristic may use different Scales, such as temperature in Celsius or Kelvin; use a declared conversion when the comparison needs a common Scale.

  • F3 — Scale integrity. Retain the distinction between category, order, interval and ratio structure. Numerical labels alone establish neither distances nor admissible arithmetic.

  • F4 — Optional named Levels. A Scale can provide named tiers, such as Technology Readiness Levels or bond credit ratings. A continuous measurement needs no Level labels unless a categorization is introduced.

  • F5 — Method agnosticism. CSLC defines the Characteristic, Scale and value structure. The applicable domain patterns (e.g. Sys-CAL or KD-CAL) govern how values are obtained through sensing, simulation or expert judgement. C.16 and the receiving use supply the further measurement and comparability conditions.

A.18:4 - Solution

Bind each measurement template to one Characteristic and one Scale. A Coordinate is one value on that Scale; a named Level is optional when the Scale supplies discrete categories or tiers. A performed measurement may attribute one value or a set of values, with uncertainty and measurement conditions under C.16. CSLC types those values; it does not require every observation to determine one Coordinate.

Exactly one Characteristic + exactly one Scale; each reported Coordinate belongs to that Scale, with an optional named Level.

The parts of this clause are defined as follows:

  • Characteristic: the aspect being measured, such as Distance, Temperature or a defined quality or reliability aspect. It answers “What are we measuring?”

  • Scale: the organized set of possible values that the Characteristic can take, including the type of scale (nominal, ordinal, interval, or ratio), the measurement Unit (if applicable), and any bounds or structure. The Scale defines “How are values represented, and which operations does the Scale permit?” – e.g. “meters on a linear scale from 0 up to 1000” or “ratings 1 through 5 with ordering only”.

  • Coordinate: one value in the declared Scale’s value domain, numeric or categorical. A measurement result may attribute one Coordinate or a set of admissible Coordinates to its subject; C.16 supplies the model, uncertainty and conditions for that attribution. Examples of Coordinates are 7.4 on a meter Scale or Expert on the declared expertise Scale.

  • Level (optional): a named tier or category within a Scale, such as Low, Medium, High on an ordinal Scale. When a continuous measurement is categorized, define the category boundaries; an uncategorized continuous Scale needs no Level labels.

Keep distinct reported Characteristics in separate templates. A quantity calculation or ScoringMethod may combine input values under §4.2; keep each reported output’s Characteristic, Scale and governing relation recoverable.

A.18:4.1 - Characteristic-space support must stay declared

When a comparison uses a declared space, make the subject kind and CharacteristicSpace recoverable. Use SpaceRef when its identity matters. Different questions about the same subjects may use different spaces; a shared display or atlas label does not determine which one applies.

Keep outcome-side, representation-side and search-side spaces distinct when their difference affects the comparison. Use OutcomeMapRef only when the receiving use needs a declared map from a set result into an outcome or effect space. Identify that source result and target space together; the map supplements the view’s interpretation rather than selecting a universal space for it.

A.18:4.2 - Scale order, preference and calculation

For a magnitude comparison, interpret values under the Characteristic and Scale, including the meaning of their order and units. For a judgement about which value is better, state the preference for that use: higher, lower, a target or range, or another declared rule. A nominal Scale supplies labels without an intrinsic order; a receiving use can still express a preference among them. A descriptive measurement needs no preferred direction.

A mathematical relation can combine quantities into another quantity, as a measurement model does in C.16. Identify that relation, its conditions and the Scale of the resulting quantity. A unit conversion expresses the same quantity on another compatible Scale. A ScoringMethod instead supplies a Score for a declared evaluation and follows A.17-R7’s preference rule. For example, multiplying resistance by current gives voltage; ranking designs by cost and reliability requires a choice of preference.

For evaluative comparison or combination across different CSLC templates, the ScoringMethod must declare its Score Scale and output range. Supply finite bounds when the method or receiving use requires boundedness, as specified in A.19.USCM; do not invent bounds for a lawfully unbounded score.

A.18:4.3 - Preserve value meaning through change

A Scale is identified by its interpreted values and their domain, the equality or order structure it supplies, and, where applicable, its unit, reference and origin. A label or numeral alone supplies none of these. A Level denotes a value or declared category within that Scale; changing its spelling can preserve the Level, while moving a category boundary changes what it denotes. A Coordinate is a value of that Scale, not an independently measured object or the content that attributes the value to a subject. Keep the declared Scale recoverable when writing, comparing or passing Coordinates.

A measurement unit is an adopted reference for expressing quantities of the applicable kind. Its symbol is a representation of that reference. A change of unit can preserve the quantity through an established conversion while changing the Scale-specific Coordinate; an unchanged symbol does not establish that the unit, quantity kind or Scale is the same. A changed measurement model or calibration can change the attributed result without changing the Scale. Recover which interpretation or assertion changed before revising a dependent calculation.

For a proposed replacement, establish the required correspondence of Characteristics and Scales, then apply the conversion or evaluation rule used by the receiver. Being a Coordinate on some Scale is insufficient for filling a position on another Scale. Where no classification decision is needed, this declaration and correspondence suffice; recurring typed receivers can use the content and space ranges in C.16:5.5.1 and A.19:5.1.1.1. Membership in those ranges does not establish comparability or authorize arithmetic.

A.18:5 - Archetypal Grounding (System & Episteme Examples)

In a physical scenario (U.System): Consider an athlete’s long jump. We define a Characteristic Jump Distance with a Scale “meters (m)” ranging from 0 upward (ratio scale with meters as the unit). When the athlete jumps and lands at 7.45 m, we record a Coordinate of 7.45 m for the Jump Distance Characteristic. This ratio Scale permits interpreting a 1.5 m distance difference between comparable jumps.

For another physical measurement, consider Battery Health of a device, which might be categorized qualitatively. We could define an ordinal Scale with Levels like Good, Fair, Poor for the Battery Health Characteristic. If a device is rated “Poor”, that is a Coordinate on the Battery Health scale (with Poor as the Level name). No arithmetic is done on these labels, but we can order devices by health (Good > Fair > Poor).

In knowledge-related assessment: A person’s expertise may be assessed on a declared ordinal Scale Novice < Competent < Expert. Alice is assessed as Expert in software engineering and Bob as Competent. Their Coordinates are ordered by that rubric; numerical labels alone supply no mean expertise. The bearer here is the person, not the description of the assessment.

For an episteme-related example, a stated probabilistic model and conditioning evidence may assign probabilities 0.95 and 0.7 to two non-exclusive hypotheses. The Characteristic is the probability assigned to each hypothesis under those conditions, and the Scale is [0,1]. A higher value means a higher assigned probability under that model. Combining the values requires the model’s joint or conditional relations. Using their product as the probability that both hypotheses hold requires independence under the stated conditioning information. A probability and a statistical confidence level retain their different interpretations; the same numerical encoding does not make them one Characteristic.

A.18:6 - Bias-Annotation

The CSLC structure supports physical measurements and human assessments by keeping the Characteristic, Scale and reading distinguishable. The chosen measurement procedure supplies the domain assumptions. Scale order describes the Characteristic; an evaluation states which values it prefers for its use. This separation allows a descriptive reading to remain interpretable when the evaluation changes.

A.18:7 - Conformance Checklist

When defining a new metric template or using measurements, practitioners SHALL verify the following:

  1. One Characteristic, one Scale: Each metric template binds exactly one Characteristic to exactly one Scale. Keep different reported Characteristics in separate templates. A calculated quantity or composite Score may use multiple inputs under §4.2.

  2. Order and preference: Is the Scale’s order interpretable for the Characteristic? When the use judges which value is preferable, is that preference stated? A descriptive magnitude comparison requires only the measurement interpretation. A target-based evaluation states its target and how deviations are compared.

  3. Unit and Level clarity: State the applicable Unit or dimensionless-value convention and make it recoverable for each quantitative value. Define named Levels within their Scale. A label may occur on different Scales, but the receiving use must be able to recover which meaning applies. Keep the Unit separate from the Characteristic name.

  4. Scale-appropriate operations only: Only perform those comparisons or calculations that are valid for the given scale type. For a nominal scale, the Scale supplies equality but no intrinsic order; a use-dependent preference is a separate rule. For an ordinal Scale, its order alone does not justify arithmetic differences between numerical labels. For interval scales, an operation must respect the Scale’s admissible changes of origin and unit; differences and appropriate means can be meaningful, while ratios of raw values generally are not. For ratio scales, ratios are meaningful, but further calculation still needs the applicable quantity or scoring relation and its conditions, with compatible units. For example, encoding High as 3 and Medium as 2 supplies no interpretation of their mean, 2.5.

  5. No bare numbers: Never present a raw number or value without its context of Characteristic and Scale. A reader seeing “42” should be able to recover “42 of what, measured how,” even without knowing the metric’s template. Label reports and data with the metric name or identifier so values can be traced back to their meaning.

  6. Cross-template operations: For a conversion, recover the relation between compatible Scales, including units. For a quantity calculation, recover the model and its conditions under C.16. For an evaluative comparison or combination, state the ScoringMethod, its preference under A.17-R7 and its Score Scale and output range, including any required bounds. For example, converting 0.5 minutes to 30 seconds preserves duration; combining cost and reliability into a score needs an evaluation rule.

  7. Level optionality: Use named Levels when they help express the selected Scale’s discrete values or non-overlapping categories. Define the categories and their boundaries; leave Level unused for an uncategorized continuous measurement.

  8. Comparability test: For a magnitude comparison, use the same Characteristic and Scale, with compatible measurement conditions under C.16. A declared conversion can establish that common basis. A preference judgement additionally uses its declared preference; changing that preference alone does not change the measurement Scale.

A.17 and E.10 supply the vocabulary. A template can expose missing fields; it does not establish that the declared meanings, measurement model or resulting inference are adequate.

A.18:8 - Consequences

Adopting the CSLC Standard in the kernel yields these benefits:

  • Recoverable value meaning: Each reported value names or resolves its Characteristic and Scale, with Unit and Level when applicable. C.16 supplies the measurement model, conditions and uncertainty needed to interpret a performed reading.

  • Interpretable comparison and calculation: A magnitude comparison retains the Characteristic, Scale and measurement conditions that make the values comparable. A unit conversion preserves that basis across presentations. A derived quantity uses its measurement model; a composite Score adds the evaluation rule. Readers can therefore question a scoring choice separately from the measurement it uses.

  • Reuse across domains: temperature, length, code complexity and satisfaction assessments can expose their Characteristic, Scale and Coordinate through the same structure. Their methods and interpretation still need the applicable domain rules.

  • Scale limits: categorical assessments and quantitative measurements retain the operations their Scales allow. Named Levels can expose categories without pretending that their numerical labels measure equal distances.

  • Interpretable multi-factor scoring: A ScoringMethod exposes how its input Coordinates contribute to the Score. Its preference, score order and declared output range allow the reader to examine the weighting or formula and judge whether it represents the intended evaluation.

  • Method selection remains with the measurement: CSLC can express results obtained by sensing, simulation or judgement. The receiving use still needs the method’s assumptions, uncertainty and applicable evidence before relying on a result.

Defining a Characteristic, Scale and measurement method takes work that can be reused. When an existing definition answers the question, use it. When two presentations differ, determine whether a unit conversion supplies a common measurement basis or a different model is needed. Introduce a ScoringMethod when the intended result is an evaluative Score.

Neighboring patterns can reuse the declared Characteristic and Scale meanings. The receiving measurement, comparison, calculation, evaluation or assurance use still applies its own conditions; CSLC conformance alone does not establish measurement adequacy, valid evidence combination or assurance.

A.18:9 - Rationale

Defining a measurement template makes the aspect, Scale and value meaning available for later use. The receiving practitioner can reuse that definition instead of reconstructing it from the reported number. The following choices support that result:

  • Shared structure, distinct domain rules: a usability rating and a throughput measurement both identify an aspect, Scale and reading. Their common structure exposes the difference rather than supplying a common calculation or evidence rule.

  • Comparison and preference: Measurement comparison needs a common interpretation of the Characteristic, Scale and measurement conditions. A unit conversion can establish that interpretation across compatible presentations. Preference answers a further question: which result serves the intended use? The same temperature Scale supports identifying the hotter sample, choosing a cooling intervention or maintaining a target. Only the latter uses add a preferred direction or target rule.

  • Preserved information: an ordinal Scale states order without asserting distances. An interval or ratio model can support further calculations only when its additional assumptions are justified; wanting an average is not a reason to assume such a model.

  • Optional Levels: named tiers make category boundaries recoverable where the Scale uses them. A continuous measurement needs no Level labels unless a categorization is introduced.

  • Separate structure and method: the same CSLC structure can describe measurements made through different methods. Domain measurement patterns supply their procedures, applicability and evidence conditions; sharing the template does not make those methods interchangeable.

A.18:10 - Relations

  • Extends A.17: uses its Characteristic vocabulary and entity/relation arity distinction, then binds each template to a Scale and its reported values. A.17 supplies the participant and naming rules; A.18 supplies the CSLC structure.

  • Used by C.16 and A.19: C.16 supplies measurement methods, models, conditions and uncertainty; A.19 and A.19.CHR use Characteristic and Scale meanings in spaces and characterization templates. CSLC is the shared value structure, not a storage or computation implementation.

  • Supports dynamic reasoning: A.3.3 uses Characteristics and Scales to specify state variables. Linking a five-level performance rating to a probability needs a justified model or correspondence between their meanings. A ScoringMethod is appropriate when the result is an evaluative Score.

  • Coordinates with assurance patterns: A receiving assurance or trust claim may use measurements or Scores whose Characteristic, Scale, model conditions and uncertainty are recoverable. CSLC conformance does not establish comparability merely because values share a 0–1 or percentage encoding. Apply B.3 to the named assurance claim; a cross-domain comparison, normalization or aggregation additionally needs its own declared rule and applicable evidence.

  • Lexical and external correspondence: E.10 governs the measurement vocabulary; A.18 applies A.17’s distinction between measurement interpretation and use-dependent preference to CSLC templates. Defined scale types and units make the terms used in quantity measurement recoverable for an F.9 correspondence with external measurement standards.

A.18:End


A.19 - CharacteristicSpace: Coordinates, State Predicates and Dynamics Hook (A.CHR‑SPACE)

Type: Kernel characteristic-space and dynamics-typing pattern Status: Stable

Use this when. Use this pattern when the object is either a declared CharacteristicSpace or a reusable by-value CharacteristicSpacePredicate over that space: characteristics, scales, value sets, coordinate bindings, optional overlays, predicate operators and cuts, comparability and normalization boundaries, partial-observation handling, and the U.Dynamics.stateSpace hook.

What goes wrong if missed. Teams compare raw numbers from different scales, treat dashboards or scores as the space, hide thresholds inside state labels, silently change a predicate use’s scope or evaluation window, smuggle method sequences into checklists, or give consumer patterns private space and predicate kinds.

What this buys. One declared space and one recoverable predicate form that make state, threshold, comparability, normalization, and dynamics-typing claims inspectable while leaving each evaluation, result, evidence use, gate, and selection occurrence with its subject pattern.

A.19:0 - First use: declare a space and one predicate

Declare which Characteristics form the space. Add a reusable predicate when the receiving use needs to test a condition on a state in that space.

First move. Name the CharacteristicSpace and list its slots. Each slot names one Characteristic, its subject or input roles, and one Scale with its admissible values. Add order, topology, distance, or a mapping only when a use needs it.

Smallest complete case. A pump team declares PumpOperatingSpace with two slots:

SlotCharacteristic and subjectScale
coolantTemperaturetemperature of one Pumpdegrees Celsius, 0..120
dischargePressuredischarge pressure of one Pumpkilopascals, 0..1000

For Pump #37, the available tuple of Coordinates is (72 °C, 315 kPa). The reusable condition is:

ready(x) := 60 °C <= x.coolantTemperature <= 80 °C and x.dischargePressure >= 300 kPa.

For this tuple, ready(x) is true. That is the result: a reader can recover the two meanings, inspect the input, and repeat the test. The declaration does not by itself claim that the readings are current, authorize work, or pass a gate.

Add only what the next use needs.

  • If the Characteristic, Scale, or measurement chain is not sound yet, start with A.17, A.18, or C.16.
  • Use A.19.UNM for normalization, A.19.UINDM for indicator choice, A.19.USCM for scoring, A.19.ULSAM for scale aggregation, A.19.CPM for comparison, and A.19.SelectorMechanism for selection. Use B.1 for a separate holonic-composition claim. G.0 checks whether the numeric operation is admissible.
  • Use A.3.3 when the space types a dynamics model.
  • Use A.19.CHR when a characterization task needs shared suite contracts; add A.15.3 for typed planned fillings of independently declared positions, and E.18 when the selected flow structure is needed. Use E.20 when an FPF change introduces or revises mechanism or suite semantics or their governing definitions.
  • Use the evaluation, gate, evidence, or assurance pattern for that separate use.

If none of those questions is current, stop with the space and predicate above.

Boundary. A.19 defines the space and reusable predicate. A subject binding, partial observation, evaluation, result, comparison, gate, evidence use, view, or publication remains a separate value or occurrence under its pattern.

A.19:1 - Intent & Scope (Normative)

Intent. Establish two composable A.19 values. U.CharacteristicSpace is the declared space of characteristics, scales, Scale value sets, Coordinate positions and groups, optional overlays, comparability boundaries, normalization boundaries, and typing hooks. CharacteristicSpacePredicate is a typed unary Boolean predicate over declared Coordinates in one such space. Partial observations and their absence statuses remain consumer inputs. For dynamics, U.Dynamics.stateSpace points to the declared space so a holon’s change can be described as a trajectory in typed Coordinates. For epistemes, state remains governed by ESG; F-G-R are assurance coordinates, not an episteme state space.

U.CharacteristicSpace is the declared multi-characteristic space. CharacteristicSpacePredicate is a reusable predicate by value, not its wording, evaluation, or result. Consumer uses remain separate from both.

Scope. Pattern A.19 defines:

  • the declared U.CharacteristicSpace value as a finite product of slot value sets under A.18;
  • the slot construct that binds one Characteristic to one selected scale and value set;
  • the typed unary CharacteristicSpacePredicate over declared Coordinates, including its input variable, domain and coordinate projection, Scale meanings, any A.19.UNM normalization used to obtain its inputs, Boolean expression, cut or band, composition, and polarity;
  • optional order, topology, and distance overlays that downstream patterns may use when declared; and
  • the typing hook U.Dynamics.stateSpace : CharacteristicSpace.

A.19 stops after the space, predicate, optional overlays, and dynamics typing hook. Use A.19.UNM for normalization, A.19.CPM for comparison, A.19.SelectorMechanism for selection, C.16 and A.10 for measurement and evidence, and A.3.3 for dynamics.

Space-and-predicate versus consumer boundary. A consumer reference such as ...SpaceRef designates one declared space. A consumer use of a predicate separately identifies its subject/input and, when an evaluation is claimed, its operation and result. It binds the U.ClaimScope, relevant A.2.6 U.ContextSlice membership, effective reference scheme and reference plane, application or evaluation window, and partial-input conditions required for interpretation, applicability or reliance, or by the receiving pattern. Those bindings are not fields of the space or predicate. They may change while the predicate remains the same; changing the predicate’s input domain or coordinate projection, Scale meaning, normalization, Boolean expression, cut or band, composition, or polarity creates a different predicate. Any obtaining semantic Bridge, its bounded-use claim and reliance, and any applicable plane relation are separately identified for the consumer use; none identifies the predicate. A.19.CPM separately governs comparison relations, comparator applications, and their results.

A.19.ECS constructs an evaluation CharacteristicSpace for an object kind under improvement. E.21, E.9.DA, E.2.DA, and other evaluation patterns consume declared spaces and predicates for their own evaluated objects. A.19 supplies the reusable values; those patterns supply object-specific applicability, evaluation, result, evidence-use, stop, and receiving-work semantics.

A.19:2 - Context (Informative)

FPF already standardizes what is characterized through A.17 and how one characteristic is scaled through A.18. Dynamics, evaluation, and comparison additionally need a declared common value space in which several characteristics coexist without losing scale, arity, or meaning. They also need reusable predicates whose semantic components remain recoverable independently of a criterion description, one evaluation occurrence, or one result. A.19 supplies those two values without inventing a generic semantic-locality container or duplicating consumer scope, time, evidence, and result relations.

A.19:3 - Problem (Informative)

  • P1 - Feature-vector drift. A list of values with implicit units, scales, subject/input arity, or partial-input handling cannot support a sound state or comparison claim.
  • P2 - Hidden change conditions. Stage labels can conceal the state differences and allowed returns needed by the current model. Declare those meanings and transitions when the use relies on them.
  • P3 - Semantic-locality collapse. Different claim scopes, context slices, reference schemes, or reference planes may use different coordinate sets or meanings. Treating one umbrella context label as their common identity makes projection and comparison unverifiable.
  • P4 - Relational characteristics. A multi-entity characteristic loses arity and direction when flattened into an intrinsic scalar.
  • P5 - Hidden predicate semantics. A threshold label or criterion-description edition can conceal the input variable, Coordinate projection, Scale, Boolean operator, cut, polarity, and normalization or coordinate-mapping basis.
  • P6 - Geometry by implication. An undeclared order, topology, distance, scalarization, or aggregation can silently decide a comparison or selection.

A.19:4 - Forces (Informative)

  • F1 - Scale integrity at product size. Every Coordinate retains its own Characteristic, Scale, any applicable unit, and admissible domain, while an observation’s missing or censored status remains separate.
  • F2 - Transdisciplinarity with lexical clarity. Quantitative, qualitative, intrinsic, and relational characteristics must compose without replacing the canonical A.17-A.18 vocabulary.
  • F3 - Minimal core with explicit overlays. Order, topology, distance, normalization, scalarization, and aggregation are available only when declared under their subject patterns.
  • F4 - Predicate reuse without consumer collapse. One semantic predicate should be reusable across state, comparison, acceptance, selection, and improvement uses, while each use retains the scope, slice, plane, window, evaluation, result and evidence relations that it requires.
  • F5 - Composition. Projection, embedding, product, and declared coordinate transport must preserve coordinate and scale meaning and make losses explicit. Any semantic Bridge or plane relation remains separate from coordinate transport and is cited only by a consumer that needs it.
  • F6 - Ordinary usability. An engineer should be able to state a space and criterion without first creating a publication record, evaluation occurrence, or generic result relation.

A.19:5 - Solution

A.19:5.1 - U.CharacteristicSpace

A.19:5.1.1 - Type signature

Each slot i names one Characteristic and one chosen Scale:

slot_i = (Characteristic_i, Scale_i).

The Characteristic supplies its subject/input signature: the entity kinds and roles required when it is assigned a value. For a relation Characteristic the signature also gives the role order, or states that the relation is symmetric. A use of the slot binds that participant tuple separately. The tuple is not the Coordinate; the Coordinate is a value on the chosen Scale. C.16 uses the same separation between measurand or subject tuple and measured Coordinate.

The CharacteristicSpace is the Cartesian product of the slots’ Scale value sets:

CS = product_i ValueSet(Scale_i).

A point x in CS supplies one Coordinate x(i) from ValueSet(Scale_i) for every slot. Using that point for a subject separately binds a conforming subject/input tuple b_i and states or evaluates the characteristic assignment between b_i and x(i). For example, the distance Characteristic may bind (Machine-A, Machine-B) while its Coordinate is 3.5 m.

A complete state is total over the selected basis. An observation or evaluation input may instead be partial: it supplies Coordinates only for a subset of slots and records missing, censored, unknown, or another observation status separately. A consumer applies its own applicability and tri-state or error rule before treating such input as a state. not-applicable is normally an applicability fact, not a Scale value; a domain may use it as a value only when the Scale explicitly defines that meaning.

Any U.Dynamics.stateSpace refers to a declared CharacteristicSpace. The dynamics model states the constraints selecting its admitted states within that product, and its trajectories use points satisfying the applicable state constraints. A.3.3.CC constructs the configuration description; A.3.3 supplies additional state information, the dynamic law, time base, observation relation and prediction-use conditions.

A.19:5.1.1.1 - Identity, classification and resolution of a declared space

A declared CharacteristicSpace is an abstract mathematical entity individuated by a finite ordered basis of interpreted Characteristic/Scale pairs, the product of those Scales, and any declared structural overlays with their domains. Its description expresses these components; the description is not the space. The empty ordered basis is permitted and has the singleton product containing the empty tuple. It is not a missing declaration. A point in the product, a partial observation and a dashboard displaying observations are also distinct from the space.

DeclaredCharacteristicSpace is a C.3 kind individual over independently identified abstract spaces. Its membership criterion requires the finite ordered Characteristic/Scale basis, the product structure, and an interpretation of any structural overlays on declared domains. A mathematical space without such a basis is a non-member. An unlabelled tuple, document or partial observation is outside this candidate space-entity domain. When the components needed to decide the criterion have not been recovered, membership remains unknown. This content-fixed criterion concerns the declared structure, not whether an observation is complete, a threshold is met or an action is eligible. Pin its declaration edition and the C.3.2 evaluation slice with explicit versions and temporal selector; applicability requires the A.17/A.18 interpretation of its components. An out-of-domain candidate or interpretation gives not-applicable; missing knowledge for an admitted classification gives unknown.

The space satisfies A.1’s entity criterion through this individuation and the identity-preserving transformations of its construction; DeclaredCharacteristicSpace is consequently a C.3 subkind of U.Entity. Changing a basis position, Scale interpretation or constitutive overlay changes the space; changing the notation or description edition can preserve it when those components are preserved. Adding a Characteristic/Scale position yields a different space, not a new membership criterion. The kind continues while its candidate domain and membership distinction remain unchanged. Neither this local classification nor the word “space” establishes admission of another universal kind.

A CharacteristicSpaceRef resolves to exactly one such space under its declared effective reference scheme. Any version or temporal qualifier that selects the target is part of the reference’s designation, not an ambient setting that may change its referent. Selecting another space requires an explicit new reference value; a path’s current contents never silently retarget the old one. A returned document may help recover the space it describes, but cannot replace that space. After resolution, check the receiver’s required basis positions, Scale semantics, projection and other operation conditions. Membership alone does not make two spaces interchangeable.

When the use depends on one defining or describing episteme, carry characteristicSpaceDescriptionRef: U.EpistemeRef separately. Its referent is that C.2.1 episteme; neither the space nor CharacteristicSpaceRef has an edition property. Resolve both references and establish that the relied-on defining components describe the same selected space. Missing or multiple targets, unavailable resolution grounds, or a mismatch between that description and the selected space leave the dependent use unresolved; do not choose an implicit latest description or substitute a document for the space. A description reference is required only by a use that relies on it, including the explicit pin requirements of UNM and UINDM. Ordinary use of a space construction requires no additional description record.

A construction can be used without a separate classification declaration. When replacing a space, preserve the previous space, its selected description and the results obtained on that basis. Identify what changed, resolve the new positions, and establish the correspondence or re-obtain the affected observations and predicates required by the receiving use; a retained number alone cannot establish the new position meaning. For example, adding a substantive explanatory claim can give another description episteme of the same Celsius/kelvin space. Reversing its ordered positions instead gives another space, as in A.19.UINDM:5.4. Changing only the displayed layout establishes neither change. Keep C.16’s measurement grounds and A.6.1’s bindings available for the uses that need them.

A.19:5.1.2 - Slot discipline (invariants)

To ensure consistency and comparability, a CharacteristicSpace must obey the following invariants:

  • A19-CS-1 (Exactly one per slot). Each slot binds exactly one Characteristic to exactly one Scale (including its scale type and, when applicable, its Unit with the quantity-kind and conversion semantics governed by C.16). This mirrors the CSLC clause of “one aspect – one scale”: there are no ambiguous or compound mappings in a single slot. (If a Characteristic can be measured on multiple Scales, choose one Scale for each slot; another Scale for that Characteristic requires a separate slot in this space or a slot in another space.)

  • A19-CS-2 (Named basis). A CharacteristicSpace declaration contains an ordered basis of slots. Each slot has a stable technical name and makes its Characteristic, Scale, position, and the Characteristic’s subject/input signature recoverable. Plain-language aliases may aid recognition but do not change the basis.

  • A19-CS-3 (Stable meaning). Do not silently change a slot’s Characteristic, Scale, or position while claiming the same space. Declare the changed space. Add an explicit mapping from the earlier space when the receiving use needs to relate their values. Call that mapping an embedding only when it is point-injective and preserves every named structure; use a lossy normalization or projection for deliberate coarse-graining.

  • A19-CS-4 (Arity preservation). A slot for an entity Characteristic binds one subject. A slot for a relation Characteristic binds the subject/input tuple required by that Characteristic. Its declared role order, direction and symmetry govern interpretation. In either case the Coordinate remains one value on the declared Scale; the participant tuple never substitutes for it.

  • A19-CS-5 (No hidden normalization, preference, or aggregation). A CharacteristicSpace carries no implicit normalization, polarity preference, threshold, formula, or aggregation. A CharacteristicSpacePredicate may declare polarity, operator semantics, and a cut or band over that space. Normalizing, indicatorizing, scoring, folding, comparing, and selecting remain explicit operations under their subject patterns. A.19.UNM governs normalization semantics and admissibility; C.16 governs relied-on measurement and calibration claims.

  • A19-CS-6 (Value and absence discipline). Each slot declares its admissible Scale domain. Missing, censored, unknown, and inapplicable input states stay with the observation, record, or evaluation use rather than entering the ontic Scale value set. not-applicable is a Scale value only when that domain explicitly gives it a subject-side meaning.

  • A19-CS-7 (Space-versus-consumer boundary). A CharacteristicSpace declaration contains only its basis, optional overlays, and typing hooks. A consumer separately declares references to the space, relation positions, source use, views, publication details, applicability, partial-input handling, and evaluation results.

A.19:5.1.3 - Minimal structure hooks (optional overlays)

A CharacteristicSpace has no default order, topology, or distance. Declare only the structure that a use needs:

  • Order overlay. OrderOverlay = (D, preceq, laws, applicability), where D is a stated subset of CS, preceq is a typed binary relation on D, and laws say whether it is a preorder, partial order, or another named order. The declaration explains how the relation respects each participating Scale.
  • Topology overlay. TopologyOverlay = (D, tau, construction, applicability), where tau is a topology on D. The construction may cite a product topology or give another basis; the name alone supplies no continuity claim.
  • Distance overlay. DistanceOverlay = (D, d, distanceLaws, parameters, applicability), where d : D x D -> nonnegative values. distanceLaws states exactly which separation, symmetry, direction, and triangle conditions hold; parameters include any weights, units, normalization basis, and validity conditions.

The declaration of every overlay is optional. Once a consumer relies on one, however, it names the overlay and stays within its domain and applicability conditions; any claimed order preservation, continuity, convergence, sensitivity, robustness, or stability must satisfy the laws of that overlay. An overlay adds analysis structure and cannot redefine a slot’s Characteristic, Scale, admissible operations, or Coordinate meaning.

Here distance means a mathematical distance function, not a performance measure or a C.16 measurement method. Use a measurement specification under C.16:5.2 for the measurement definition and its DHCMethodRef for reference resolution.

A.19:5.1.4 - Dynamics hook (typing only)

A U.Dynamics.stateSpace SHALL refer to a CharacteristicSpace that types its state values. The dynamics model declares the subset admitted by its constraints; when these depend on time or external conditions, that dependence remains part of the model. States and trajectories use points of the CharacteristicSpace satisfying those applicable constraints. Thus the product supplies coordinate meanings and the model supplies compatibility and change. A.3.3.CC constructs the configuration description, including implicit constraints or a parametrization. A.3.3 determines the additional information and transition law required for the prediction. A.19 supplies the space and applicable overlays without choosing that law or time base.

A.19:5.1.5 - Lexical discipline (Normative)

Use Characteristic, Scale, Level, Coordinate, CharacteristicSpace, slot, and basis for the objects defined here. Use “slot” or “basis element” for one component of the declared basis, and “Characteristic” for the measured or evaluated aspect. An explanatory alias must preserve that meaning. Mathematical uses of “axis” or “dimension” remain available when they denote their own declared mathematical objects rather than substitute ambiguously for a Characteristic or slot. A point in this CharacteristicSpace is a tuple of Coordinates. In a single Scale, point may instead name one Coordinate; keep the selected space recoverable.

A.19:5.1.6 - Normalized values, classes and representative choice

Subject-pattern note. A.19.UNM governs the directed transformation, optional equality-of-output relation ≡_UNM and NormalizationFix. Cite the selected method instance, domain, target, preservation/loss basis and validity conditions when state-space reasoning uses that result.

For an equality, join, acceptance predicate or comparison, state which distinctions its answer requires. A directed normalization suffices when its declared preservation basis supports that answer. A many-to-one normalization requires the receiving query to be constant on its classes; otherwise retain the original distinction, refine the normalization or return the missing basis. Forming the set of classes does not prove an operation on them well defined.

If a state-space operation is inherited by classes, require compatible outputs and, for a partial operation, representative-independent availability under A.19.UNM. Cite a NormalizationFix only when an established class use needs a representative; choosing one does not restore the original state. Keep equality of labels separate from the claimed state or value equality.

A.19:5.1.7 - Overlay use, sensitivity, and calibration (Normative)

Use the weakest declared overlay that the argument needs. Declaring an order or distance does not make every predicate monotone, every map non-expansive, or either property necessary or sufficient for acceptance. Bands, target regions, and Boolean cuts are valid even when they are not isotone or continuous.

When a consumer makes a sensitivity, robustness, continuity, stability, or prediction-use claim, that consumer states:

  1. the function, predicate evaluation, or transition map and the overlay it uses;
  2. the domain, codomain, applicability conditions, and claimed property;
  3. any bound, margin, approximation, uncertainty, or error allowance required by the consumer’s policy; and
  4. the evidence or argument needed for that use.

A useful bound need not be Lipschitz <= 1; its admissible value comes from the named use and policy. Claim isotonicity only when the use depends on order preservation. Claim commutation with normalization only when that composition matters. C.16 governs relied-on measurement and calibration claims. A.3.3 governs prediction error, horizon, and model applicability; A.20, A.21, G.4, and the authority pattern govern their own constraint, gate, criterion, and decision consequences. Non-expansiveness or commutation alone grants no gate, release, assurance, or work authority.

A.19:5.1.8 - CharacteristicSpacePredicate (by-value)

A CharacteristicSpacePredicate is a typed unary predicate over one declared space:

P : D_P -> Boolean, where D_P is a declared subset of CS.

Its input variable denotes one state. The predicate declares which coordinates it reads and any projection used to obtain them. Its complete by-value meaning contains:

  • the CharacteristicSpace, input variable and domain;
  • each read Coordinate’s Scale and value interpretation;
  • any coordinate projection or A.19.UNM normalization instance used to obtain those inputs;
  • the operators, cuts, bands, regions, or unary subpredicates used in its Boolean expression; and
  • the polarity that says which outcome satisfies the predicate.

Conditions defined by thresholds, bands, and regions are unary predicates of this kind. Compose predicates with logical operators only after their input bindings and domains are aligned; otherwise give the composition an explicit binding that makes the conversion visible. A dominance or other comparison between two states is instead a typed binary comparison relation such as R : D_left x D_right -> Boolean, governed by A.19.CPM or another comparison pattern. Its comparator application and result are not components of a unary CharacteristicSpacePredicate. Use an n-ary predicate only when its full variable roles, domains, projections, and result type are declared.

An arbitrary condition relation is not automatically a state or Coordinate. A use binds either a direct characteristic assignment or an explicit governed projection from its subject/input tuple to the predicate input. When the affected entity differs from the condition participants, the consumer also states that relation. An F.9 Bridge relates two local senses; it is not this subject-to-input binding.

The predicate carries no applicability, assessment, observation, evidence, or evaluation window. A consumer separately identifies the available input and any evaluation operation and result it claims, with the U.ClaimScope, relevant U.ContextSlice membership, effective reference scheme and plane, application or evaluation window, and partial-input conditions required by that use. An evaluation may return unknown, not-applicable, or error when input or applicability is unresolved; those consumer results do not enlarge the predicate’s Boolean codomain or the space’s Scale value sets. When asserting a performed evaluation as U.Work, establish its A.13 basis and then its independent A.15.1 admission; keep its operation application and result separate from the predicate.

Predicate identity changes when one of these semantic components changes. Wording, notation, carrier, publication, identifier, or description-edition changes alone do not create another predicate. A consumer may evaluate the same predicate in another scope or window, but may not silently change its space, projection, Scale, normalization, expression, cut, band, composition, or polarity. An obtaining semantic Bridge or plane relation may be cited by one consumer use without becoming part of predicate identity.

Minimally viable case. In a pump space with batteryVoltage on the volt Scale, batteryReady(x) := x.batteryVoltage >= 24 V is a unary predicate with Boolean result. A maintenance check separately binds Pump #37, its current measured input and window, and the evaluation result. Comparing two pumps by voltage would be a separate binary comparison relation, not a second reading of batteryReady.

A.19:5.2 - State Spaces & Comparability

Memory hook: Compare only values already in the same declared space or carried into one common space through an exact coordinate mapping. Reusing a predicate also requires the same semantic predicate. If the use also claims a relation between two F.17 local senses, cite an F.9 Bridge only after its predicate obtains and state the bounded-use claim and reliance separately. If the ReferencePlane changes, cite the applicable plane relation. Scope and window remain separate in either case.

This section supplies space projection, embedding, product, and two coordinate-comparability regimes. It does not perform a CPM comparison or a SelectorMechanism selection. A consumer that names a state or category cites the declared space and any predicate required by that use, then keeps its own scope, evaluation, result, evidence, and work relations.

A CharacteristicSpace may be written abstractly as CS = ⟨I, basis⟩, where I indexes slots and basis is the ordered set of (Characteristic, Scale) bindings. A consumer-specific label for a space does not create another A.19 kind; the consumer instead states the use or relation position, entity and any predicate required by that use, with the claim scope, context-slice membership, effective reference scheme and plane required by that use.

A.19:5.2.1 - CS Operators (notation-neutral, reference-scheme-local)

To enable model composition, define operations on CharacteristicSpaces independently of notation. State any effective reference scheme or reference plane on which interpretation or use of the operation depends. Those values locate the operation but create no correspondence. When a use relates two F.17 local senses, test the F.9 predicate and cite the Bridge only when it obtains; state the bounded-use claim and any reliance separately. A ReferencePlane crossing cites its applicable plane relation. A scheme or plane difference alone establishes neither relation.

A.19:5.2.1.1 - Subspace — projection

For a space CS_I with basis I and a subset S, the projection pi_S^I : CS_I -> CS_S keeps the Coordinates in S and discards the others. The type-correct laws are pi_I^I = identity_CS_I and, for T subseteq S subseteq I, pi_T^S after pi_S^I = pi_T^I. A projection preserves an order, topology, or other structure only when that fact follows from the named overlays; projection alone makes no such promise.

A.19:5.2.1.2 - Embedding and lossy mapping

An embedding iota : CS_1 -> CS_2 is point-injective and preserves every structure named by its declaration. It gives an injective slot correspondence and an injective value map for each corresponding slot. Identity maps and exact, reversible unit conversions can support an embedding when they preserve the declared Scale meaning. The declaration states its domain, image, preserved structures, and any A.19.UNM instances used.

A mapping that loses distinctions on its declared domain is not an embedding. State the preserved and lost distinctions, and let each consumer decide whether that loss is admissible for its comparison, prediction, gate, or assurance use. Dropping a Coordinate is a projection; on a restricted domain it may still be point-injective if the retained Coordinates determine the dropped value. An embedding claim additionally requires the declared slot correspondence and preservation of every named structure. When the use relates two F.17 local senses and the F.9 predicate obtains, cite that Bridge and a separate bounded-use claim. A ReferencePlane change instead cites its applicable plane relation. The coordinate mapping, semantic relation, plane relation, and C.16 calibration or measurement backing remain separate.

A.19:5.2.1.3 - Product – Combination CS₁ ⊗ CS₂ = CS⊗.

The product of two spaces CS₁ and CS₂ is a new space CS⊗ whose basis is the disjoint union of both bases, so even same-named slots retain their source identity. Its state is a pair (x₁, x₂). For example, a product can combine internal capability Coordinates with external-condition Coordinates for a readiness use. The product does not aggregate them: any cross-slot scale aggregation uses a declared Gamma fold under A.19.ULSAM and any needed A.19.UNM normalization. Use B.1 when a separate holonic-composition claim is made.

A.19:5.2.2 - Comparability of States (two admissible regimes)

A label such as Ready, Authorized, or Degraded is a consumer-side category, not a space or comparison result. Its subject pattern states the predicate and evaluation use. Comparing two coordinate states depends on the declared spaces, mappings, scales, and comparison scope; A.19 permits only the following two coordinate regimes.

A.19:5.2.2.1 - Coordinatewise comparability (≼_coord)

Two states can be compared coordinatewise only under the conditions below. Essentially, we require the states to be expressed in the same measurement space, with the same applicable units and scales, and using the same state definitions. Formally, coordinatewise comparison is allowed only if all of the following hold:

  • Same space. Both coordinate values lie in the same CharacteristicSpace by value. Similar names, shared storage, or a common model-use label are insufficient.

  • Scale congruence. For each slot being compared, the scale type, any applicable unit, and polarity orientation are identical. For example, if comparing temperature values, both must be on the same scale (say, °C on an interval scale with “higher = hotter” orientation). No unit mismatches or differing interpretations can be present.

  • Predicate and use congruence. When comparison depends on a category predicate, both values use the same CharacteristicSpacePredicate by value. CPM still states the comparison scope, comparator, reference plane, and evaluation window; A.19 does not infer them from matching labels.

When these conditions are met, one can define a coordinatewise preorder over states. Common patterns include:

  • Dominance: For a given set of “higher is better” slots, we say state x ≼_{\mathrm{coord}} state y if and only if for every relevant slot a, the coordinate a(x) \le a(y) (after orienting all slots to the declared polarity for that slot). In other words, y is as good or better on all enforced criteria. This defines a Pareto-like ordering (often partial, not total).

  • Predicate-region inclusion: Predicate-defined categories denote regions of the declared space. Compare their regions by inclusion: Region(P) subseteq Region(Q) means every point satisfying P also satisfies Q. For example, speed > 120 and accuracy > 95% implies speed > 100 and accuracy > 90%. Two points satisfying the same category predicate need not be ordered; ordering those points requires the separately declared coordinate comparator.

By default, no comparability is assumed unless proven. If any of the above congruence conditions fails, one must not fall back to ad-hoc comparisons (like matching by name or normalizing without declaration). Use an admissible normalization-based regime or return the missing comparison basis. Declare states incomparable under the declared preorder only when neither direction holds; missing support alone establishes no such result.

A.19:5.2.2.2 - Normalization‑based comparability (≼_normalization)

When two state vectors do not meet the conditions for coordinatewise comparison (e.g. they come from different spaces, or the “same” Characteristics are measured on different scales or units), the only sanctioned way to compare them is: normalize, then compare.

Concretely: if we have state x in CS₁ and state y in CS₂, a normalization‑based comparison is permitted only if the model can cite a set of NormalizationMethodInstanceId(s) under a chosen UNM (per A.19.UNM) that lands the relevant coordinates of x into CS₂ (or lands both into a declared common target space). The base results are NCVs with their preserved/lost distinctions. Use an ≡_UNM class only when the receiving query is recoverable from that class; an inherited operation needs its separate compatibility and availability argument under A.19.UNM.

Comparability rule (normalize-then-compare). We say x ≼_{\mathrm{normalization}} y only if, after applying the cited normalization instances to produce a representation of x in CS₂ (or a common target), the mapped state can be compared coordinatewise under ≼_coord. In other words, we never compare raw x and y; we compare after mapping into a common, well-typed space.

If a normalization use also spans different reference schemes or planes, keep the decisions separate. The A.19.UNM instance supplies the coordinate mapping. Cite an F.9 Bridge only when the use relates two F.17 local senses and its predicate obtains; state the bounded-use claim and reliance separately, with CL only as optional evidence shorthand. A ReferencePlane crossing cites its applicable plane relation. CPM supplies the comparison scope and evaluation window, and B.3 enters only for an assurance use. None of these relations or consequences follows from the scheme or plane difference alone.

Inspectability. Each normalization instance used for comparison is recoverable through its A.19.UNM declaration. C.16 governs measurement and calibration backing. When values differ in scale, reference scheme, or plane, keep the normalization, any independently obtaining semantic Bridge with its separate use claim, any applicable plane relation, and their limitations explicit.

Mnemonic: Never compare before both values are carried into the same well-typed space; never claim the same predicate, scope, plane, or window merely from matching labels.

A.19:5.2.3 - Predicate-use and state-assertion boundary

A.19 defines the space and CharacteristicSpacePredicate; it does not define a state assertion, applicability relation, dated evaluation work, gate, evidence relation, assurance result, or permission to act.

A consumer use recovers the subject or input, any direct characteristic assignment or projection from that subject, the A.19 space, and any predicate required by that use. It supplies the set-valued U.ClaimScope, relevant A.2.6 U.ContextSlice membership, effective reference scheme and reference plane, and application or evaluation window required for interpretation, applicability or reliance, or by the receiving pattern. When the use needs an obtaining F.9 Bridge, identify it with its separate bounded-use claim and reliance; identify any applicable plane relation separately. When an evaluation is claimed, identify the evaluation-operation application and its typed result under the applicable evaluation or assertion rule. A.10 provenance, G.11 currentness, measurement backing, assurance, and receiving-work disposition remain separate.

For a Ready claim requiring temperature below a cut and pressure above a cut, A.19 supplies the two declared coordinates, scales, normalization or coordinate-mapping basis, operators, cuts, polarity, and conjunction. The state assertion binds the pump, inputs and result, with the scope, slice, evaluation interval and evidence use required to interpret or support that assertion. Any semantic Bridge or plane relation needed by that use remains separate. Changing the evaluation interval does not change the predicate; changing either cut does.

Transporting a predicate into another space or transporting an assertion across spaces requires the exact Coordinate correspondence. Use an embedding only for point-injective structure-preserving transport; use a declared lossy mapping or projection when normalization discards distinctions. If the use relates two F.17 local senses and the F.9 predicate obtains, cite that Bridge and its separate bounded-use claim. If the ReferencePlane changes, cite the applicable plane relation. A scheme or plane difference alone establishes neither relation. If the required correspondence is absent, return the unsupported comparison or evaluation with its missing basis. Approximate use needs its own stated relation, tolerances and warrant.

A.19:5.2.4 - Cross-reference-scheme and cross-plane comparability

A comparison across reference schemes or planes follows the relations the case needs. When it relates two F.17 local senses and the F.9 predicate obtains, cite that Bridge and a separate bounded-use claim; CL is optional evidence shorthand. A plane crossing cites its applicable plane relation. Keep the coordinate mapping and A.19.UNM instances explicit. A context, scheme, or plane difference alone establishes no Bridge or comparison admissibility, and a reverse comparison needs its own justified direction.

A comparison may reuse a predicate only when its complete by-value meaning is unchanged. When a coordinate mapping is needed, it must preserve every predicate component required by this use. If the reuse also relates two local senses through an obtaining Bridge, a separate bounded-use claim states that semantic use and any required reliance passes. CPM separately binds comparison scope, comparator, input values, effective reference plane, and evaluation window. The Bridge alone copies neither predicate content, scope, nor time, and a common label establishes none of them.

C.16 governs measurement uncertainty and calibration limits; A.3.3 governs prediction error and model applicability. Use B.3 or the assurance pattern when the use makes an assurance claim. Return the comparison as unsupported for the intended use when a critical coordinate lacks an admissible normalization or coordinate mapping; a separately needed semantic Bridge, bounded-use claim or plane relation is absent; required reliance does not pass; or the required predicate, plane, scope or window cannot be held fixed. Keep that missing basis distinct from comparator-established incomparability.

A.19:5.2.5 - Characteristic-Space Reference Chain

When evaluating a checklist, StateAssertion, gate, assurance argument, or decision through a declared CharacteristicSpace, keep the space-related references distinct:

declared Coordinates -> [normalization or quotient, when used] -> [indicator choice, when used] -> [order, topology, or distance overlay, when used] -> neighboring predicate evaluation, assertion, gate, assurance, or decision claim

Only the branches used are present. A.19 supplies the declared space and any named mapping, quotient, or overlay; the consumer supplies applicability, operation, result, and consequence. Co-implementation in software or records does not collapse these values.

A.19:5.3 - Operator library (notation‑neutral)

Space operations: Sub (projection), Emb (embedding), Prod (product), Quot (quotient by declared equivalence). Representative choice: NormalizationFix chooses a representative for an established normalization-class use under A.19.UNM.

Predicate and assertion transport: Pull transports a predicate through a declared embedding or lossy mapping; Push transports an assertion only with the support and conditions required by its subject pattern; a permitted narrower use states its changed or lost meaning. Indicatorization and aggregation: Indicatorize applies an IndicatorChoicePolicy; Fold_Gamma performs admissible aggregation under its subject pattern. Semantic-relation mnemonic: Align_B is not a space operator: when retained as a consumer mnemonic, it names only an already obtaining F.9 Bridge between two F.17 local senses. A ReferencePlane relation remains separate.

OP-1 (Normative). Use Align_B only after the F.9 predicate obtains. The consumer cites that Bridge, a separate bounded-use claim, and the reliance required for the named gate, comparison, or assurance use; CL remains optional evidence shorthand. A ReferencePlane crossing cites its applicable plane relation and does not use Align_B unless an independently obtaining semantic Bridge is also current. The consumer separately binds scope, evaluation window, and result; any assurance consequence requires a separately current B.3 assurance result.

A.19:5.4 - Set-view, comparison, and selection boundary

A view, comparison result, selection, portfolio, distance-based neighborhood, or transition-sensitive interpretation is a consumer value. It may cite an A.19 space, predicate, order, distance, or transition relation, but its identity and result remain with the view, comparison, selection, or transition pattern.

A.19:5.5 - Further worked uses

More coordinates. A pump condition may add vibration or calibration Coordinates to the two-slot example. Add each slot only with its Characteristic, subject/input signature, Scale, and value domain; then extend the predicate explicitly.

Episteme evaluation. A method-description review uses clarity, evidence recoverability, source currentness, and relation precision coordinates. A.19 supplies the declared characteristic space; the evaluation pattern contains the defining content for the stop condition, rating interpretation, and improvement decision.

Cross-scheme comparison. A built-asset team compares readiness values expressed under different measurement conventions. It first names an admissible normalization into one declared target space. If the use also relates two F.17 local senses, it tests the F.9 predicate and cites the Bridge only when it obtains, with a separate bounded-use claim and reliance. If the ReferencePlane changes, it cites the applicable plane relation. A separate A.19.CPM application then binds the compared states, comparator, scope, window, and result.

A.19:5.6 - Bias-Annotation

A.19 corrects feature-vector bias: a list of numbers, labels, or dashboard fields is not yet a CharacteristicSpace. The space exists only when each slot binds a Characteristic to a Scale and Scale value set with declared meaning and optional overlays. Partial-observation and applicability statuses remain with the consumer.

It also corrects consumer-pattern bias. A.19 is the pattern for the reusable space and semantic predicate values. Each gate, evaluation, comparison, selection, assurance, dashboard, or portfolio claim retains the application, scope, window, result, evidence use and publication consequences required by that use or the applicable pattern; consuming the A.19 values creates no private space or predicate kind.

A.19:6 - Conformance checks

Start with the base declaration. If the job is only to declare a local space, or that space plus one predicate, stop after these checks.

Base declaration

  1. The ordered basis names every slot’s Characteristic, Scale, admissible value set, position, and subject/input signature.
  2. A complete point contains one Coordinate from each Scale. Missing, censored, unknown, and inapplicable inputs remain separate observation or evaluation statuses.
  3. No order, topology, distance, normalization, indicator, aggregation, or comparison is implied. Any one that is present is named explicitly.
  4. When a CharacteristicSpacePredicate is present, its input variable, domain, Coordinate projection, Boolean expression, cut or band, composition, and polarity are recoverable. A binary comparison remains separate.
  5. The declaration contains no hidden evaluation result, gate decision, evidence relation, publication object, or permission to act.

Triggered additions

Apply a row only when its trigger is present.

TriggerAdditional check
Subspace or productList the carried slots and Scale meanings. Projection uses the type-correct composition law; a product performs no aggregation.
Embedding or lossy mappingAn embedding is point-injective and preserves every named structure. State loss for a many-to-one mapping or coarse-graining. A dropped Coordinate is a projection and may remain point-injective on a stated restricted domain; any embedding claim still meets all its slot and structure conditions.
Normalization, quotient, equality, or join across spacesCite the admissible A.19.UNM instance, Scale conditions, domain, and validity window. Compare in one declared target space. Check preservation of the equality/join question; a class-level use needs query constancy and any inherited operation needs compatibility. Retain lost inputs, refine the transformation or return the unsupported comparison.
Same-space state comparisonCompare Coordinates directly only when both states use the same declared space, slot meanings, Scale metadata, and state definition. A.19.CPM separately binds the comparator, scope, plane, window, application, and result.
Indicator useCite the IndicatorChoicePolicy; a normalized value is not automatically an indicator.
Cross-reference-scheme or cross-plane useCite an F.9 Bridge only for two F.17 local senses when its predicate obtains, and state the bounded-use claim separately; CL is optional. Cite the applicable plane relation separately. Name matching, context/scheme/plane difference, and an expired mapping establish neither relation nor admissibility.
Predicate evaluation or state assertionBind the subject/input tuple and available Coordinates or governed projection. The consumer identifies any evaluation operation and typed result it claims, together with the scope, relevant slice, reference scheme and plane, applicability or evaluation window, and partial-input rule required to interpret or support the use or required by the receiving pattern.
Changed predicate, mapping, or overlayKeep earlier assertions tied to the earlier values. A new declaration does not retroactively rewrite a historical assertion or result.
Sensitivity, robustness, continuity, stability, or order-preservation claimName the function or predicate use, overlay, domain, assumptions, and bound or law required by the consumer’s policy. Add C.16 uncertainty and calibration limits when measured Coordinates are relied on.
Dynamics prediction used in comparison or gatingApply A.3.3 and the consumer’s policy for model edition, domain, horizon, currentness, error or uncertainty, observation, sensitivity, stability, and normalization-composition conditions. No one regularity property grants authority.
Gate, permission, evidence, or assurance useUse the gate, authority, evidence, and assurance patterns for their applications and results. A.19 contributes only the cited space, predicate, mapping, or overlay and requires no persistence identifier or log by itself.

Choose the needed expression form through C.2.3. Automation or assurance can require more explicit identifiers and records under their patterns, but it does not enlarge the base A.19 declaration.

A.19:7 - Common Anti-Patterns and How to Avoid Them

The following are common modeling mistakes (“anti-patterns”) related to measurement spaces, and how to correct them:

  • “Same label ⇒ comparable.” ✗ Assuming two Ready labels or two same-named coordinates are comparable across different reference schemes or planes. ✓ Normalize into one declared target space. Cite an F.9 Bridge only when its predicate obtains between two F.17 local senses, state the bounded-use claim and reliance separately, and cite the applicable plane relation for a ReferencePlane crossing. Let CPM state the comparison scope, comparator, plane, and window.

  • “Compare before common-space mapping.” ✗ Comparing values directly across different scales, e.g. Drift_A = 5°C vs Drift_B = 5°F as if they were the same. ✓ Normalize to common units first: for drift expressed as a temperature difference, use ΔT_C = ΔT_F × 5/9. For absolute temperature values, apply the Fahrenheit-to-Celsius NormalizationMethod m(T_F) = (T_F - 32) × 5/9. Then compare the converted values of the same declared Characteristic. Always normalize into one space before comparing magnitudes.

  • “Checklist = method sequence.”

    • Wrong: Ready means “do Step 1, then Step 2.”
    • Repair: let the checklist state the conditions that must hold. Put the way of reaching them in a separate Method or MethodDescription, planned occurrences in a WorkPlan, and what happened in Work. Evidence separately supports an assertion or evaluation result; it is not the condition itself.
  • “Retro-fix past assertions.” ✗ Going back to edit or reinterpret old StateAssertions after changing a threshold or NormalizationMethod (e.g. “We updated the criteria, let’s ‘fix’ last quarter’s records to match”). ✓ Preserve the historical assertion and its basis. New criteria require a new evaluation for the use that needs them, with the relevant NormalizationMethod, UNM declaration or checklist identified. Correct an erroneous assertion or retract an unsupported conclusion explicitly while retaining what was asserted, when, and under which criteria. Renewed use checks applicability and currentness; it does not silently rewrite the earlier criteria.

C.27 temporal-claim relation.

  • C.27 may flag: a rate or rate-change claim that needs base characteristic, scale and unit, time base or sampling window, transformation or finite-difference method, evidence, and admissible use.
  • A.19 governs CharacteristicSpace and Coordinate discipline; C.16 governs measurement construction and backing.
  • Non-admissible use: words such as velocity, acceleration, throughput, cadence, or recovery speed do not by themselves establish a Characteristic, Scale, or measurement method.
  • Use boundary: when the interpretation governs the claim, cite baseCharacteristicRef, the relevant measure reference, sampling window, construction method such as DHCMethodRef, and the C.16 measurement or construction relation reference; C.27 does not define a parallel measurement system.

A.19.ECS object-under-improvement evaluation construction relation.

  • A.19 defines CharacteristicSpace as an ontological structure: slots, characteristics, scales, value sets, overlays, and comparability boundaries.
  • A.19.ECS governs the construction of one object-under-improvement evaluation CharacteristicSpace for an object being improved. It is used before E.22 and E.23 when no adequate object-under-improvement evaluation exists.
  • Existing object-under-improvement evaluation patterns such as E.21, E.9.DA, E.2.DA, and the naming vector inside F.18 are examples of this construction shape for object kinds under improvement. They keep their own coordinate, value-meaning, and stop-condition definitions.

A.19:8 - Consequences

ConsequenceBenefitCost or boundary
Coordinate and observation claims become inspectableA reader can recover the subject/input tuple, slot, Characteristic, Scale, value set, Coordinate, partial-input status, window, and mapping references.Declaring the space and its use takes more work than naming a feature vector or dashboard column.
Predicate meaning remains reusableA criterion survives description, evaluation, scope, and window changes when its semantic components are unchanged.Authors must name coordinates, scales, operator, cut or band, polarity, and normalization or coordinate-mapping basis. Any semantic Bridge and plane relation are cited separately by the consumer; the bounded-use claim and reliance remain separate from both.
Consumer patterns stay boundedGates, evaluations, comparisons, selectors, assurance claims, and dashboards use declared spaces and predicates without redefining them.Each consumer declares the scope, slice, plane, window, result and evidence use required by that use or its governing pattern.
Dynamics has a typed state spaceA dynamics model can say which space its state belongs to without letting A.19 define the dynamic law or time base.Dynamic laws, evidence, and work consequences must still be governed elsewhere.

A.19:9 - Rationale

A characteristic space is the minimal object that keeps multi-characteristic claims from becoming loose feature lists. The pattern binds each characteristic to a scale and value set, then lets neighboring patterns consume the declared space for state predicates, thresholds, comparisons, gates, evaluations, assurance, dashboards, and dynamics models.

The separation matters because a threshold or region is not the space, yet its semantic predicate is reusable before and after any one evaluation. A.19 is the pattern for that by-value predicate; comparison, acceptance, selection, assertion, evidence-use, publication, and decision occurrences and results require their own current claims under the applicable patterns.

A.19:10 - SoTA-Echoing

FPF’s characteristic and measurement patterns require explicit variable definitions, subject/input roles, Scales, applicable units, value ranges, partial-input treatment, normalization when used, and comparability for multi-criteria comparison. A.19 applies A.17, A.18, C.16 and A.19.UNM by treating the CharacteristicSpace and its Coordinate values as the declared ontic object, while observation absence, scoring, indicator choice, normalization use, and assurance remain with their patterns.

FPF’s dynamics construction distinguishes the declared state space from the law and time base, any observation model, and any intervention on the modeled subject. A.19 supplies the space and typing hook; A.3.3 governs the state-law account and its conditional returns for other uses. This boundary lets characteristic-space declarations be reused across system, episteme, evaluation, and architecture work, with consumer semantics retained in their patterns.

A.19:13 - Relations - Ontic Relations and Consumer Boundary

  • Builds on: E.24 for ontic-head discipline, A.17 and A.18 for characteristic and scale discipline, A.2.6 for U.ClaimScope membership over U.ContextSlice values, and C.16 for measurement and coordinate claims.
  • Coordinates with: A.19.CPM for comparator and comparison scope; A.19.SelectorMechanism for explicit selection conditions; G.4 and other consumers for typed predicate evaluation; F.9 when a receiving use needs a semantic correspondence or difference between two F.17 local senses; the applicable plane pattern for a plane relation; A.10 and G.11 for provenance and currentness; and C.2.1 when a predicate description or evaluation assertion is itself an episteme.
  • Does not replace: a consumer’s evaluation, comparison, selection, evidence use, gate, assurance, view, or publication.

A.19:12.1 - C.29 mathematical-lens use relation

If topology, order, distance, product, subspace, or embedding is only a CharacteristicSpace overlay or operation, stay in A.19. When using that mathematical structure to explain, predict, assure, compare across reference schemes or planes, relate independently governed values, or carry a reusable explanation leaves a representation or transfer question unresolved, use C.29 to establish the needed construction, correspondence and limits for that inference. An adequate local equation, algorithm or domain model needs no separate C.29 result when no such question remains. C.29 does not replace the A.19 space or predicate declaration.

A.19:End

A.19.ECS - CharacteristicSpace Construction: Define What Counts as Better

Type: Method pattern Status: Stable Normativity: Normative

Use this pattern when an object version is to be improved or judged, but the evaluation that says what “better” means is not yet available, not yet explicit or not yet adequate for the object.

A.19.ECS:1 - Problem frame

A.19 says how a CharacteristicSpace is structured: declared characteristics, declared scales, slots, value sets, declared coordinate groups, and no hidden normalization or aggregation. A.19.ECS says how to make such a CharacteristicSpace for the evaluated object, so the object can be evaluated and E.23 can run an improvement loop without inventing values.

The ordinary output is an evaluation characteristic-space specification: a grouped set of characteristics, scales, value meanings, evidence-basis rules, missingness rules, result-row shape, calibration points, coordinate-specific evidence payloads, protected trade-offs, status meanings, and stop or reopen conditions for one evaluated object kind and use scope.

When to use another pattern.

  • If a suitable evaluation already exists, cite it and use E.22 for question framing or E.23 for repeated improvement.
  • Use A.17, A.18, and C.16 when the problem is one characteristic, one scale, or measurement admissibility and scale lawfulness.
  • Use C.16.P first when candidate coordinate wording still hides whether the use under repair is a characteristic, scale, coordinate, score, metric label, quality-term repair, or subject-pattern relation.
  • Use A.19 when the problem is the structure of CharacteristicSpace itself.
  • Use C.25 when the evaluated EntityOfConcern is a composite engineering quality family that already fits Q-Bundle form.
  • Use F.18 when the problem is durable naming.
  • Use E.21, E.9.DA, or E.2.DA when the evaluated EntityOfConcern is respectively one FPF pattern version, one DRR, or one FPF-level Pillar-adequacy evaluated EntityOfConcern.

First useful move. State the sentence: “good as what kind of object, for which use, against which contrast cases?” Then name the evaluated object kind, the use scope, and at least three contrast cases: one admissible evaluated object, one below-floor evaluated object, and one outside-declared-object-kind boundary case that should return to evaluation selection before the evaluation is opened or receive an object-kind-fit defect/value when that evaluation has already been invoked.

Existing-evaluation boundary. If the answer is “use this existing evaluation” and the evaluated object kind, use scope, floor, protected trade-offs, and stop meanings are already recoverable, do not construct a new CharacteristicSpace.

What goes wrong if missed. A team says “improve this” and then chooses convenient scores. A scale set appears from nowhere. Chairs, coal plants, nuclear plants, and FPF patterns all get compared on coordinates that do not distinguish the evaluated object kind. One visible value improves while the intended use gets worse. A review can say “better” but cannot say which object property changed, what trade-off was protected, or why improvement may stop.

What this buys. A.19.ECS gives improvement work a way to create the missing evaluation before the loop starts. It keeps E.23 universal: E.23 changes the object and asks an evaluation to re-evaluate it; A.19.ECS helps build that evaluation when none is yet adequate.

Primary EntityOfConcern. The primary EntityOfConcern is the construction of one evaluation CharacteristicSpace for one evaluated object kind and declared use.

Intended reader. The intended reader is an engineer, analyst, pattern author, evaluator, steward or method designer who must define what counts as improvement for an evaluated object before running an improvement loop.

A.19.ECS:2 - Problem

FPF already has named patterns for single characteristics, scales, coordinate values, Q-Bundles, and repeated improvement. The gap is the construction of a useful grouped scale set for an evaluated object kind.

Recurring failures:

  1. Scale set from air. An evaluation lists coordinates because they are familiar, not because they discriminate the evaluated object kind or use.
  2. Wrong-kind comparison. Objects outside the declared kind are scored as if they were weak objects under improvement, or are silently skipped, instead of being returned to evaluation selection before opening or handled by an object-kind-fit defect/value after opening.
  3. One-score collapse. Several independent characteristics are averaged into one score, hiding object-kind-fit defects and trade-offs.
  4. Unstated polarity. Readers cannot tell which direction is preferred or when a value has no preferred direction.
  5. No floor or exceptional meaning. Values are recorded, but nobody can say what is viable, exceptional, or still inadmissible for the declared use.
  6. No evidence or missingness rule. A coordinate value is asserted without saying what observation, content locus, test, example, source, or judgment can justify it, or what absence means.
  7. No protected trade-off. The evaluation encourages improvement on visible coordinates while damaging safety, usability, affordability, source preservation, entry cost, neighbour fit, or another value that should constrain the change.
  8. No stop or reopen condition. Improvement continues forever or stops after a convenient checklist closure, not because the evaluation says the evaluated object has reached the declared aim.
  9. Specification underdeclaration. A new evaluation is mentioned in prose, table, rule, or local rubric, but its declared specification does not make evaluated object kind, coordinate set, value meanings, status meanings, relations, and non-use boundaries recoverable.
  10. Result-form underdeclaration. The evaluation has coordinates, but the returned result can be a prose impression, a two-column value table, or a checklist count without its evidence basis, Scale-appropriate rationale, calibration discipline, or required coordinate-specific payload.
  11. Evidence-basis leakage. Evidence needed to justify the evaluation result, corpus projection, currentness, retrieval, or parity is written as if it were the evaluated object’s own method or user action.

A.19.ECS:3 - Forces

ForceTension
evaluated-object-kind discrimination vs broad reuseThe evaluation must fit the evaluated object kind, but it should reuse existing FPF characteristic and scale discipline where possible.
Small first version vs enough coordinatesA useful first evaluation can be compact, but it needs enough coordinates to block false improvement and wrong-kind comparison.
Measurement admissibility and scale lawfulness vs content judgmentSome coordinates are measured through C.16; others are evidence-backed content values. The evaluation must say which is which.
Improvement direction vs trade-off protectionPreferred movement must be visible without turning every coordinate into an optimization command.
Contrast cases vs overfittingContrast cases are needed to test the scale set, but the evaluation must not become a list of examples only.
Reusable specification vs local useA reusable evaluation must make the same evaluation characteristic-space elements recoverable across uses. A local project can use a smaller specification when the use is bounded and non-reusable.
Local stop vs open-ended improvementA loop may stop for the declared use while the object and the scale set remain improvable under a new use, source, or comparison concern.

A.19.ECS:4 - Solution

Construct an evaluation specification that declares an A.19 CharacteristicSpace and its use. The space contains the characteristic slots, Scale bindings and value meanings. The evaluation separately supplies the object kind, use scope, contrast cases, evidence and missingness rules, result content, calibration, protected trade-offs, statuses and stop or reopen conditions; these consumer rules do not become fields of the space.

EvaluationCharacteristicSpaceSpec := <EvaluatedObjectKindRef, ObjectVersionUnderImprovementRef?, DeclaredUseScope, WorkingReaderScope, QualificationWindow, DiscriminatingCaseSet, ObjectKindFitRule, CharacteristicSlotSet, ScaleBindingSet, PolarityAndPreferredMovement, FloorAndExceptionalMeaningSet, EvaluationEvidenceBasisRule, EvidenceAndMissingnessRule, ResultRowShape, AdjacentValueRationaleRule, CalibrationPointSet, CoordinateSpecificEvidencePayloadRule?, ProtectedTradeoffSet, DominanceOrComparisonRule?, StatusValueSet, StopOrReopenCondition, NeighborPatternExitSet, E22QuestionFrameUse?, E23StartCondition>

A.19.ECS:4.1 - Local names and kind settlement

Local nameUseNon-use boundary
EvaluationCharacteristicSpaceSpecLocal specification for constructing one evaluation CharacteristicSpace.Declaring an evaluation alone establishes neither a value for the evaluated object nor permission to act.
EvaluatedObjectKindRefKind of object being evaluated.—
DeclaredUseScopeUse for which the evaluated object is being judged or improved.Not all possible uses.
DiscriminatingCaseSetPositive, below-floor, and outside-declared-object-kind boundary cases used to test whether the characteristic space distinguishes the evaluated object kind and use.Not a substitute for the coordinate set.
ObjectKindFitRuleRule for admissible evaluated object, below-floor evaluated object, and outside-declared-object-kind boundary case.Not permission to omit declared coordinates after an evaluation has been invoked.
CharacteristicSlotSetThe grouped slots, each binding one characteristic to one scale.Not an arbitrary checklist and not hidden aggregation.
ScaleBindingSetThe chosen scale and value meaning for each characteristic slot.—
PolarityAndPreferredMovementDirection of preferred movement for each coordinate, or a statement that the coordinate has no simple preferred direction.Not permission to optimize one coordinate while damaging protected trade-offs.
FloorAndExceptionalMeaningSetViable-for-use and exceptional-for-use value meanings for declared coordinates.An exceptional value does not establish that future improvement is impossible.
EvaluationEvidenceBasisRuleThe checked evidence loci required for the result: object version, corpus/projection loci when corpus-facing, source-currentness loci when currentness is valued, comparator loci when parity is valued, worked-case loci when case coverage is valued, and any missing or unchecked basis that limits the conclusion.An unchecked premise leaves its dependent value unestablished; it supplies neither a low property value nor a positive evaluation. Do not infer values from reputation, review state, or absence of visible defects.
EvidenceAndMissingnessRuleWhat justifies a value and how missing, censored, unknown, object-kind-fit, or boundary-return cases are handled.Claiming a property value still requires the evidence specified by the rule.
ResultRowShapeRequired result content: coordinate, value and a short rationale, with evidence loci or payload when needed.A paragraph or table is sufficient when it carries that content; a value list without its basis is insufficient.
AdjacentValueRationaleRuleFor a discrete ordered Scale, explain why adjacent alternatives misstate the evidence; at the top value, state what would lower or reopen it. For a continuous Scale, justify the value or interval at the applicable resolution and uncertainty.Do not invent adjacent values for a dense Scale or order for nominal categories.
CalibrationPointSetReusable cases and reference values for common disagreements, including 3/4/5 or equivalent adjacent values when the Scale has them.Calibration uses the declared Scale and supplies no second score system.
CoordinateSpecificEvidencePayloadRuleExtra payload that a coordinate needs when a category label can fake discharge: comparator plus selected ingredient plus current locus, source plus adopted payload plus currentness window, projection locus plus retrieval cue, or another payload named by value.Not the evaluated object’s method, and not live evaluated-object text unless the evaluated object itself is an evaluation result or projection carrier.
ProtectedTradeoffSetQualities or neighbour claims that must be checked when visible coordinates improve.Not a hidden veto without a declared evaluation pattern or value meaning.
PrecisionRepairKindRuleRule for checking pre-repair and post-repair evaluated object kind, characteristic kind, relation or claim kind, ontic slot, relation position, use relation, admissible use, and scope when coordinate or evaluation wording is repaired; cite another pattern’s definition or constraint when it governs that meaning; name a ClaimGraph only when its identity or edition changes the use.Not permission to change object kind or slot, relation position, use relation, or claim kind by cleaner wording.
StatusValueSetLocal admissible-use result values for the evaluation.Not release state, gate status, or evaluator praise.
E23StartConditionMinimum condition for using this evaluation inside E.23.—

These names are local to this pattern.

A.19.ECS:4.2 - Construction moves

Use these moves when constructing or repairing an evaluation. They are not a mandatory work sequence; each move is a required content question whose answer must be recoverable before the evaluation is used for improvement.

  1. Name the evaluated object kind and use. Say what object kind is being evaluated and for which declared use. If the evaluated object kind is not recoverable, stop before choosing coordinates.
  2. Build the discriminating cases. Include at least one evaluated object that should pass, one object admitted to the evaluation that should fail the floor, and one different object kind that should return to evaluation selection before opening or receive an object-kind-fit defect/value if this evaluation has already been invoked.
  3. Choose candidate characteristics. Draw candidates from the object kind’s failure modes, first-principles structure, user or operator harms, domain tradition, current SoTA, existing evaluations, and FPF neighbouring patterns named by value.
  4. Bind each slot. For each candidate, state the characteristic, chosen scale, value set, admissible domain, missingness semantics, and whether the value is a measurement claim or a content evaluation. Keep the property value, object-kind fit, and missing observation distinct. An observed absence of required support can justify a low value; an unperformed check cannot establish that absence. A local diagnostic code such as 0 may represent missing basis only when declared as a code, without the arithmetic or comparison rights of a measured zero. Preserve supported values while leaving dependent conclusions open.
  5. Remove false coordinates. Drop coordinates that do not change admissible action, do not discriminate the evaluated object, duplicate another coordinate without a different repair action, or belong to another evaluation.
  6. Split compound coordinates. If a coordinate mixes two repair actions, two object kinds, or two incompatible scales, split it or assign one part to the neighboring pattern that governs that claim.
  7. State preferred movement and trade-offs. For each declared coordinate, state the preferred direction or explain why no simple direction exists. Name the protected trade-offs that must be checked when the coordinate improves.
  8. Define result form, evidence basis, and calibration. State the required result content, evidence basis, Scale-appropriate rationale rule, calibration cases for common disagreements, and any coordinate-specific payload needed for high or floor-reaching values.
  9. Define floor, exceptional, status, and stop. State the viable-for-use floor, exceptional-for-use meaning, status values, and local stop or reopen condition.
  10. Recover dependent claims and their rules. When a coordinate depends on a separate evidence, assurance, gate, Work, decision, publication, naming, measurement, quality-bundle, OEE/NQD or mathematical-lens claim, identify its subject, relation and the rule that defines or constrains it. An ordinary pattern citation can locate that content. Identify a ClaimGraph only when its identity or edition affects the use; the citation itself establishes no subject fact.
  11. Start E.23 with a usable evaluation basis. A repeated improvement loop can start only when the evaluated object version, evidence basis, result form, and evaluation are recoverable for re-evaluation.

A.19.ECS:4.3 - Evaluation specification minimum

A.19.ECS does not prescribe a publication or record form. It states which evaluation characteristic-space elements must be recoverable before an evaluation characteristic space is reusable for judgement or improvement. The selected publication or record form may be an FPF pattern, local engineering standard, rubric, table, review form, model card section, protocol note, or project rule, but that form is not governed here.

The evaluation characteristic-space specification must make these items recoverable by value:

Specification itemRequired content
Evaluation problem frameEvaluated object kind, declared use, first useful move, existing-evaluation boundary, and what goes wrong if no evaluation exists.
Non-use boundaryBoundaries that distinguish this evaluation from other questions or claims relevant to its declared use.
Local names and kind settlementAny local names used, their meanings, and the boundaries needed to interpret or apply them.
Evaluation expressionHow the required evaluation content is made recoverable in the chosen form.
Object-kind fit ruleAdmissible evaluated object, below-floor evaluated object, and outside-declared-object-kind boundary handling before and after invocation.
Evaluation evidence basisLoci named by value that must be checked or named when a value depends on object version, corpus projection, source currentness, mature comparator, worked case, retrieval, or other external evidence.
Result-row shapeCoordinate, value and short rationale, plus the evidence locus or payload required for that value. These are content requirements, independent of table or prose layout.
Coordinate setCoordinate heads, evaluated-object properties and use conditions, scale/value meanings, evidence loci, and protected trade-offs.
Calibration and payload rulesScale-appropriate calibration cases and required coordinate-specific payloads; use adjacent 3/4/5 cases only where the Scale has those values.
Status and stop conditionAdmissible-use statuses, local stop meanings, and reopen conditions.
Worked slicesAt least one passing evaluated object, one below-floor evaluated object, and one outside-declared-object-kind boundary case.
Common anti-patternsThe false interpretations or values the evaluation must block.
Neighbouring-pattern claim assignmentNeighbouring FPF patterns named by value and the claims being made that each pattern defines or constrains.

This minimum is a content requirement, not a file-format requirement. For an FPF pattern publication form, E.8 still governs the authoring form. A.19.ECS only states what the evaluation must make recoverable so that E.22 can frame an improvement-oriented quality evaluation and E.23 can run a repeated improvement loop.

When construction or repair changes coordinate wording or evaluation wording, compare the pre-repair and post-repair evaluated object kind, characteristic kind, relation or claim kind, ontic slot, relation position, use relation, admissible use, and scope. Cite another pattern’s definition or constraint when it governs the repaired meaning. Identify its ClaimGraph only when identity or edition matters to the repaired use.

A cleaner phrase that changes those items, treats a coordinate position as an object kind, or loses the value’s slot, relation position, use relation, or claim kind is a changed evaluation decision, not a wording repair.

A.19.ECS:4.4 - Discriminating-case test

An evaluation is not ready if it cannot distinguish these three outcomes:

  1. Admissible evaluated object. The object is of the evaluated object kind and can meet or exceed the floor under the declared use.
  2. Below-floor evaluated object. The object is of the evaluated object kind or a declared comparable family, but fails one or more floors.
  3. Outside-declared-object-kind boundary case. Before the evaluation is opened, the object should return to evaluation selection or construction rather than be treated as the evaluated object kind. If the evaluation has already been invoked for that object, the result identifies the object-kind-fit defect or repair status and marks the affected coordinates inapplicable under the declared rule. It does not assign weak property values to an object outside their domain.

Example: for a nuclear-plant adequacy evaluation, a nuclear plant can vary along safety, output, maintenance, regulatory, thermal, waste-handling, grid, and resilience coordinates.

A coal plant may be a power-generation alternative only when the declared use compares power-generation options across plant kinds.

A chair or FPF pattern is outside the nuclear-plant evaluated-object kind: before opening the evaluation it returns to a suitable evaluation; after a forced invocation, the result records the kind mismatch and explains why the plant-specific coordinates do not apply to the chair.

A.19.ECS:4.5 - Scale-set improvement

Improve an evaluation when its use misses a consequential defect, rejects an admissible object, recommends a harmful repair, fails on a new use, or demands more work than its decision value justifies. First distinguish a defect in the evaluation from a failure to perform it, unavailable inputs, or reliance beyond its scope. A better-written specification and more agreement among evaluators do not by themselves establish better decisions.

Use the following comparison to decide whether to adopt a change:

  1. Name the lost practical result. State which decision or next action the current evaluation gets wrong or cannot support, for which object and use. Preserve the current evaluation as the comparison basis and propose the smallest change that addresses that loss.
  2. Establish contrasting cases independently of the proposed evaluation. Use subject requirements, observed work results, or other applicable grounds to identify a consequential defect and a difficult but admissible case. Include a case in which an apparently helpful repair would damage a protected quality. The proposed evaluation’s own verdict cannot establish these cases’ correctness.
  3. Apply both evaluations to the same material. Keep object versions, task conditions and available evidence comparable. Inspect missed defects, false objections, the proposed action, damage from that action and the work needed to obtain and use the answer. Investigate disagreement through the conflicting grounds and conditions; neither majority agreement, stricter verdicts nor a larger finding count establishes practical improvement.
  4. Test adoption beyond the cases used for tuning. When the change was fitted to known cases, use a new case with an independent basis for the adoption decision. Keep its relevant answer out of tuning and disclose prior exposure or assistance. Replaying a known case remains useful development evidence; if no independent case is available, limit the conclusion to a trial in the examined scope.
  5. Choose at attainable cost. Use C.11.DUA to compare the useful decision change with preparation, data collection, independent judgement, interpretation, repair, repeated evaluation, maintenance, transition and displaced useful work. Keep uncertain and non-commensurable costs visible. Adopt for the supported use, retain on a bounded trial, revise, reject, or keep the existing adequate evaluation.
  6. Preserve scoped results. Name the changed evaluation and whether earlier results remain comparable, need an explicit bridge, or cannot support the new use. Re-evaluate only conclusions that depend on the changed rule or conditions. A new evaluation does not erase an earlier result within its supported scope.

This comparison checks the evaluation’s practical contribution. Use E.21 separately when the specification is an FPF pattern whose quality is in question; E.9.DA for the decision record selecting it; E.2.DA for FPF-level Pillar adequacy; F.18 for naming; and C.16, A.17, A.18, or A.19 for measurement, scale or characteristic-space admissibility. Their results answer those questions and can supply premises here. Use E.23 when repeated improvement of the evaluation is needed.

An independent subject basis and a bounded adoption comparison can settle the choice without creating an endless sequence of numeric meta-evaluations. If a decisive premise remains unknown, retain the corresponding limit or trial disposition; another score does not supply that premise.

Worked comparison. A team proposes replacing a review criterion that counts source links with one that checks whether a required claim is supported. A known defective text has many links but omits the dependent claim; a difficult admissible text uses one sufficient source and a different valid explanation. The new criterion detects the omission and preserves the admissible explanation. A proposed repair that copies every source paragraph would make ordinary use harder, so the comparison also checks the repaired text.

These are development results on known cases. Adoption still needs an independently grounded new case and an affordable way to obtain the supporting judgement. If the new criterion merely produces more objections or requires whole-corpus reading for every local use, revise it or retain the adequate earlier procedure in its supported scope.

A.19.ECS:5 - Archetypal Grounding

FPF pattern quality. The evaluated object kind is one FPF pattern version. The existing evaluation is E.21, so A.19.ECS stays closed unless E.21 itself is being redesigned. E.23 may improve the pattern version under E.21.

DRR adequacy. The evaluated object kind is one DRR version for a declared campaign-decision use. The existing evaluation is E.9.DA. If a campaign needs a different DRR adequacy coordinate, A.19.ECS can test whether that coordinate belongs inside E.9.DA, another evaluation, or no current FPF pattern.

FPF Pillar adequacy. The evaluated object is FPF as a corpus or release candidate. E.2 gives the Pillars; E.2.DA is the evaluation. A.19.ECS explains why E.2.DA needs evaluated object, use, eligibility, coordinates, evidence loci, stop meanings, and neighbour governing relations rather than a Pillar essay.

Name improvement. The evaluated object is a durable term candidate. F.18 already supplies a grouped lexical quality vector: SemanticFidelity, CognitiveErgonomics, MorphologicalActionFit, and AliasRisk, plus NQD discipline over candidate names. A.19.ECS treats F.18 as an existing local evaluation for naming, not as a reason to build another one.

No evaluation yet. A team says “make this onboarding method better” but cannot say better for whom, by what values, or with what stop. A.19.ECS opens before E.23: it names evaluated object kind, user, use, contrast cases, candidate characteristics, scales, floors, missingness, protected trade-offs, and neighbour governing relations. Only then can E.22 frame an improvement-oriented quality evaluation and E.23 improve the method.

A.19.ECS:5.1 - Bias-Annotation

A.19.ECS corrects score-first bias. Teams often begin improvement by choosing convenient scores, visible dashboards, or familiar criteria. The pattern starts instead from evaluated object kind, declared use, contrast cases, characteristic slots, scale bindings, value meanings, evidence basis, missingness, protected trade-offs, and stop conditions.

It also corrects evaluation-reuse bias. A reusable evaluation is useful only when it fits the object kind and use. If the existing evaluation already fits, use it; if it does not, construct or repair the evaluation characteristic space before starting an improvement loop.

A.19.ECS:6 - Conformance checklist

CheckRequirementWhy
CC-A19ECS-1An evaluation characteristic-space specification SHALL name evaluated object kind, use scope, reader scope, and qualification window.Prevents context-free quality claims.
CC-A19ECS-2It SHALL include admissible, below-floor, and outside-declared-object-kind boundary contrast cases.Tests evaluated-object-kind discrimination.
CC-A19ECS-3Each coordinate SHALL bind one characteristic to one scale, including for an ordinal content evaluation. State separately whether the value is a measurement claim or a content evaluation.Preserves A.17/A.18/C.16/A.19 discipline.
CC-A19ECS-4Each coordinate SHALL state value meanings, polarity or no-simple-direction value rule, evidence rule, and missingness rule.Makes values replayable.
CC-A19ECS-5The specification SHALL state floor, exceptional, status, stop, and reopen meanings for the declared use.Lets improvement stop locally without claiming final perfection.
CC-A19ECS-6Protected trade-offs SHALL be named when improving visible coordinates can harm another live value.Blocks Goodhart-style improvement.
CC-A19ECS-7The specification SHALL not average ordinal coordinates or turn undeclared coordinates into hidden pass, waiver, or failure.Preserves non-scalar comparison.
CC-A19ECS-8Wrong-kind objects SHALL return to evaluation selection before opening. After invocation, report the kind mismatch and the declared inapplicability of dependent coordinates instead of assigning low property values outside their domain.Preserves declared coverage and distinguishes object fit from property quality.
CC-A19ECS-9If made reusable beyond one local use, the evaluation characteristic-space specification SHALL make the minimum items in A.19.ECS:4.3 recoverable by value. If the selected publication form is an FPF pattern, E.8 also applies to that publication form.Prevents underspecified evaluations.
CC-A19ECS-10If the evaluation itself changes, justify its adoption or trial through §4.5 and name the comparability effect on earlier results. Keep known-case development, independent adoption evidence and full cost distinguishable.Prevents silent value drift and improvement claims based only on the new evaluator.
CC-A19ECS-11The evaluation characteristic-space specification SHALL state any evidence, assurance, gate, work, decision, publication, naming, measurement, Q-Bundle, OEE/NQD, mathematical-lens, or related claim as a subject assertion or named relation by value when that claim is being made. The coordinate Solution carries the evaluation construction itself; a subject-pattern locator, reference boilerplate, architecture-placement rationale, and neighboring content stay in relations, rationale, source-basis, or decision-rationale material unless they change a coordinate.Prevents an evaluation from becoming a second ontology or reference boilerplate.
CC-A19ECS-12A reusable evaluation characteristic-space specification SHALL state what would lower, reopen, or retire the evaluation: missing contrast case, changed use, changed source-use relation or source-currentness status, hidden trade-off loss, or corrected neighbouring-pattern claim assignment.Makes high-value evaluation claims falsifiable instead of permanent praise.
CC-A19ECS-13A reusable evaluation specification SHALL define the required result content and require a short rationale for every coordinate value, in a sufficient prose or table form.Makes the value and its basis recoverable.
CC-A19ECS-14It SHALL define the evaluation evidence basis and any coordinate-specific evidence payload needed for source-currentness, comparator, corpus-projection, worked-case, retrieval, or external-currentness claims. Apply the declared missingness rule when evidence is missing or unchecked. Lower a value for that absence only when the coordinate’s value rule evaluates evidence adequacy or otherwise makes that absence a lower value; do not infer a low property value merely from an unknown value.Makes values replayable while preserving missingness and the declared coordinate coverage.
CC-A19ECS-15When different evaluators will reuse it, the specification SHALL provide calibration cases for common disagreements: adjacent-value cases where the Scale has them, or the applicable reference values, resolution and uncertainty for continuous readings.Keeps calibration compatible with the Scale.
CC-A19ECS-16It SHALL declare where result evidence, corpus-projection evidence, retrieval evidence, comparator evidence, currentness evidence, and quality-status evidence live. These payloads SHALL stay in the evaluation result, evidence basis, projection carrier, or selected publication carrier unless the evaluated object itself is that carrier. If the payload implies a user-facing action for another evaluated object, publish that move or boundary, not the carrier proof. This is an evaluation-payload placement rule, not a lexical ban: evidence-use payloads do not enter live evaluated-object text merely because they are true or useful to authors or evaluators.Prevents evaluation evidence from leaking into the evaluated object’s method or live text.
CC-A19ECS-17If construction or repair changes coordinate wording or evaluation wording, perform a pre/post check of evaluated object kind, characteristic kind, relation or claim kind, ontic slot, relation position, use relation, admissible use, and scope. Use the relevant definition or constraint from another pattern when it governs the repaired meaning; identify a ClaimGraph only when its identity or edition affects use.Prevents coordinate cleanup from changing what the evaluation evaluates.

A.19.ECS:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Scale set from air.Coordinates appear because they are familiar.Rebuild from evaluated object kind, use, contrast cases, failure modes, domain tradition, first principles, and current source-use relation.
Wrong-kind object forced through the table.Objects outside the declared kind are either scored as weak members of that kind or silently exempted from declared coordinates.Add an object-kind-fit rule and boundary cases: before opening, return to a suitable evaluation; after invocation, record an object-kind-fit defect/value or repair status.
Checklist masquerading as characteristic space.A list of tasks is treated as coordinates.Convert each task row to an evaluated EntityOfConcern property with a characteristic, scale, value meaning, and evidence rule, or move it to work planning.
One total quality score.Several ordinal values are averaged.Use coordinates, statuses, dominance or comparison rule, and protected trade-offs; do not scalarize unless a neighboring pattern governing the claim declares the operation.
Improvement without floor.A loop continues because more change is possible.State floor, exceptional meaning, stop condition, and reopen condition.
Hidden value drift.The evaluation changes while old evaluations are compared as if nothing changed.Version the evaluation and state comparability, bridge, or retirement.
Evaluation theft.The new evaluation starts asserting evidence, assurance, gate, work, decision, or publication truth without the corresponding predicate and case facts.State each neighboring subject assertion under its predicate or constraint and leave only the value evaluation here.
Values without their basis.An evaluator returns a value or impression without the required evidence and rationale.Make each value and its grounds recoverable in sufficient prose or a table; apply the declared missingness rule where needed evidence is missing or unchecked.
Evidence basis as evaluated-object method.Corpus projection, retrieval, currentness, comparator, monolith-parity, quality-status evidence, or author or reviewer turn correspondence is written in the evaluated object as if it were what the evaluated-object user does.Move the evidence to the evaluation result, evidence basis, projection carrier, or selected publication carrier; keep only the user action or boundary that the evidence justifies.
Coordinate wording as ontology change.A coordinate or repair name sounds cleaner, but changes the evaluated object kind, characteristic kind, relation or claim kind, admissible use, or scope.Treat it as a changed evaluation decision, recover the pre/post kind relation, and repair or reopen the evaluation rather than accepting lexical cleanup.

A.19.ECS:8 - Consequences

A conforming A.19.ECS result lets E.22 ask a useful improvement-oriented quality-evaluation question and lets E.23 run a repeated improvement loop without inventing values during the loop.

It also gives object-specific evaluation patterns such as E.21, E.9.DA, E.2.DA, and F.18 a common construction shape: evaluated object kind, use, contrast cases, coordinates, value meanings, evidence basis, result-row shape, calibration points, coordinate-specific payloads, protected trade-offs, status meanings, and local stop or reopen condition.

Reuse may require additional explanation of the evaluation’s applicability, value meanings, evidence requirements and limits. When a local rubric is enough, keep the rubric local. When reuse is needed, carry the evaluation by value.

A.19.ECS:9 - Rationale

An evaluation used to justify improvement must distinguish practical gains from changes to convenient proxies. Its object-kind fit, value meanings, evidence, missingness, protected trade-offs and stop conditions explain what a better reported value permits the practitioner to conclude.

A.19 governs the structure of CharacteristicSpace; A.19.ECS governs the construction method for evaluations of declared EntityOfConcern kinds and uses. A.19.ECS governs the selected characteristics, scales, coordinate construction, and evaluation-use boundaries of the evaluation characteristic space, not its publication or record form. An FPF pattern is only one possible publication form when the evaluation belongs in FPF; a local rubric, standard, table, or project rule is enough when the use is local.

E.23 stays a universal loop method because it does not need to know how every domain chooses its scales. Domain and FPF-specific evaluations such as E.21, E.9.DA, E.2.DA, and F.18 keep coordinate choices inside those evaluations.

A.19.ECS:10 - SoTA-Echoing

ClaimCited practice lineAdoption in A.19.ECSBoundary
Evaluation artifacts must declare intended use, object, criteria, and missingness before their values are useful.Cited reporting approaches: BenchmarkCards/EvalCards practice for evaluation-card structure, model-card lineage for intended-use and performance-characteristic reporting, and HELM/VHELM/AHELM-style evaluation suites for scenario, metric, raw-result, and modality-extension transparency.A.19.ECS starts from evaluated object kind, use scope, contrast cases, coordinate meanings, evidence rule, and missingness rule.A.19.ECS does not prescribe a publication format.
Multicriteria evaluation needs preserved dimensions and protected trade-offs.Cited QD overview: A survey on Quality-Diversity optimization: Approaches, applications, and challenges, Swarm and Evolutionary Computation 100:102240 (2026); retained design lineage: MCDA and value-focused thinking for criterion separation and trade-off visibility.The pattern requires coordinate values, polarity or no-simple-direction value rule, protected trade-offs, status meanings, and stop or reopen conditions.Scalarization belongs only to a neighboring pattern governing the claim or declared local method.
Improvement concern can damage the intended value when the evaluation is a weak proxy.Cited proxy-risk studies: Goodhart's Law in Reinforcement Learning (ICLR 2024) and catastrophic-Goodhart reward-misspecification work (NeurIPS 2024); retained lineage: Goodhart taxonomy.A.19.ECS requires evidence rules, missingness rules, protected trade-offs, and lowering/reopen conditions before a loop can treat a value as improved.It is not an anti-measurement rule; it makes the measurement or ordinal evaluation explicit enough to be challenged.
OEE and NQD work keeps the quality side distinct from novelty, diversity, archive, pool, and selected-set semantics.QD, OEE, and NQD neighbour basis: quality-diversity work evaluates quality together with novelty and diversity, while archive and front are separate relations. Use C.17 for novelty and diversity characterization, C.18 for archive and front relations, C.19 for pool treatment, G.5 for selected-set result declaration, G.9 for parity, and G.11 for currentness and refresh. When audience availability is current, use E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability.An evaluation may supply Q values. It does not thereby establish neighboring search, selection, retention, currentness, or publication claims. Examples include novelty, diversity, archive, front, pool, selected-set, parity, refresh, and publication claims; apply the named definitions and tests only when the corresponding claim is current.A.19.ECS constructs an evaluation U.CharacteristicSpace; using it neither performs nor establishes OEE or NQD generation, selection, archive, publication, parity, or refresh.
Evaluator quality must be connected to the decisions it improves.Kim et al., Rethinking Reward Model Evaluation Through the Lens of Reward Overoptimization (2025), studies reward-model evaluation in bounded mathematical tasks. HCD.18/.19 supply developed domain treatments of criterion error and support conditions; C.11.MV supplies the general comparison of a Method option’s practical worth.Adapt: §4.5 compares missed defects, admissible difficult cases, proposed repairs and cost. This evaluation construction requires subject grounds: HCD’s treatments provide domain examples, while C.11.MV supplies the practical-worth comparison without establishing the evaluation criteria or their validity.Reward-model correlation, evaluator agreement and a better specification do not establish general decision usefulness. Reopen when a target use cannot obtain the independent basis the comparison needs.
Adaptive reuse can turn adoption cases into tuning material.Dwork et al., Generalization in Adaptive Data Analysis and Holdout Reuse (2015), is statistical lineage; Iacob et al., The Red Queen Gödel Machine (2026), is cited bounded research on evolving evaluation.Adapt: separate known-case development from independent adoption, preserve scope and expose cost in §4.5.Neither statistical holdout guarantees nor benchmark improvement transfers automatically to qualitative framework evaluation. Reopen if leakage, a new population or comparison burden defeats the intended use.

A.19.ECS:11 - Relations

PatternRelation
A.19Defines CharacteristicSpace. A.19.ECS gives the method for constructing one evaluation CharacteristicSpace for an evaluated object.
A.17, A.18, C.16Govern characteristics, scales, scale values, coordinates, measures, units, measurement admissibility, and scale lawfulness. A.19.ECS uses them by reference for each slot.
C.25Governs Q-Bundle normal form for composite engineering quality families. A.19.ECS may select or repair the characteristic-space part before a Q-Bundle endpoint is used.
E.22Frames one improvement-oriented quality-evaluation question after an evaluation is declared. A.19.ECS constructs the missing or inadequate evaluation.
E.23Governs repeated improvement after evaluated object version and evaluation are declared. A.19.ECS constructs a missing evaluation and supplies the adoption comparison when that evaluation changes.
C.11.DUASupports choosing attainable evaluation effort from the useful decision it can change and the full cost of obtaining and using its result.
E.21Existing evaluation for one FPF pattern version. A.19.ECS explains the construction shape but does not replace E.21.
E.9.DAExisting evaluation for one DRR decision-adequacy claim. A.19.ECS does not replace it.
E.2.DAExisting evaluation for FPF-level Pillar adequacy. A.19.ECS explains why it must publish evaluated object, coordinates, values, evidence loci, status, and stop meanings.
F.18Existing naming discipline with a grouped lexical quality vector. Use F.18 for durable term and name improvement.
C.16.P, C.16.Q, E.10, A.6.P, C.2.PRepair overloaded characteristic/scale/score, quality, lexical, relation, and source-use wording before it becomes a coordinate or status value.
C.17, C.18, C.19, G.5, G.9, G.11Govern OEE/NQD novelty, diversity, archive, pool, selected-set, parity, and refresh semantics. An evaluation may supply Q values, but it does not govern the rest of OEE/NQD.
C.29Use C.29 when defining or justifying coordinates leaves a mathematical representation or transfer question unresolved. An adequate local calculation or domain model needs no separate C.29 result.
A.10, B.3, A.20, A.21, A.15Govern evidence, assurance, local CV, gates, and work when an evaluation result is reused for those claims.

A.19.ECS:End

A.19.SPR - Repair State and Status Wording

Type: State-family precision-restoration pattern Status: Stable Normativity: Normative unless marked informative

Plain-name. State-wording repair.

A.19.SPR:0 - Use this when

Use this pattern when a phrase such as “the system is ready”, “the source is current”, or “the evidence status is incomplete” matters to an FPF claim but does not yet say which item the sentence is about, what is true of it, or which rule makes that statement meaningful.

What goes wrong if missed. A short status word starts carrying several claims at once. A source label becomes evidence, a readiness label becomes gate passage, or a project-side status leaks into pattern guidance.

First question. Ask:

What item is this sentence about, what does it say about that item, and which rule or criterion gives the statement its meaning?

Repair. Write the answer as one ordinary technical sentence. Name the item, the value, relation, result, or claim, and the rule or criterion only when the reader needs it to understand or act. If that sentence is clear and safe for the intended use, stop. Do not create a repair note or list every claim the sentence does not make.

What this buys. A reader can understand the statement and its next use without learning a hidden status vocabulary.

Typical triggers include state, status, posture, stance, currentness, validity, stable, accepted, blocked, candidate, degraded, readiness, ready, and similar compounds. A precise-looking field such as LensUseBoundaryValue or dynClaimPosture is also a trigger when its object, possible values, or rule cannot be recovered.

Not this pattern when.

  • If the item, claim or value, and applicable rule are already clear, use that rule directly.
  • If readiness or ready still hides whether the sentence concerns a subject state, assignment condition, work entry, gate decision, publication use, permission, or performed Work, use E.10.MOVE first.
  • If the wording is ordinary prose and carries no FPF-governed claim, keep it ordinary.
  • If one Characteristic, Scale, Coordinate, score, or measurement construction is hidden, use C.16.P first.
  • If a source expression, publication, carrier, or source-use relation is hidden, use C.2.P first and return here only if a state-wording problem remains.
  • For relation, architecture, quality, function, or naming problems, use A.6.P, C.30.P, C.16.Q, A.6.F, or F.18 as selected by E.10.

A.19.SPR:1 - Problem frame

FPF needs compact state words. Engineers reasonably say that a pump is stable, a source is current, an evidence path is incomplete, an assurance claim has expired, or an intended performance is ready for work entry.

The words work when the reader can recover the item, the claim or value, and the rule behind it. Trouble begins when the word replaces those facts. “Ready” may mean a patient condition, an assignment satisfying a condition, an A.15.5 work-entry result, an A.21 gate decision, or merely a green display. Those are different claims.

A repaired sentence may therefore name an ordinary domain condition, an obtaining relation, an assertion episteme, an evaluation result, a decision result, or a project-side record field. It introduces a predicate only when the rule for that claim defines or needs one.

A.19.SPR:2 - Problem

How can FPF keep useful words such as state, status, and ready without:

  • creating one general Posture or readiness kind;
  • replacing one broad status word with another;
  • treating every state statement as a CharacteristicSpace position or predicate;
  • merging source use, evidence, assurance, publication, assignment state, work entry, gate decisions, performed Work, and project records;
  • copying the same wording-repair procedure into every pattern; or
  • deleting a useful local finite field whose object, values, rule, and practical use are already clear?

A.19.SPR:3 - Forces

NeedTension
Short working languagePractitioners need compact sentences, but a consequential claim must still identify what is being judged.
Local fieldsA finite field can be useful; a vague status field can hide several unrelated claims.
PatternsA.19 covers characteristic spaces, while evidence, assurance, publication, assignment state, readiness, gates, and project records keep their own rules.
Small repairMost cases need one rewritten sentence, while replayed or high-consequence cases may need a few additional fields.

A.19.SPR:4 - Solution

Start with the sentence:

  1. name the item;
  2. say what value, relation, result, or claim is current; and
  3. name the rule or criterion when the sentence is not understandable or usable without it.

Stop there when the intended reader can use the sentence. Add evidence, time or allowed-use detail when it changes that use. Under F.19, a blocked-inference clause needs independent local grounds for a plausible misreading and must change truth, understanding or action; state the smallest sufficient correction.

Use the optional StateFamilyPrecisionRepair form when replay or consequential reliance needs an inspectable basis that the existing text does not already supply:

StateFamilyPrecisionRepair:
  triggerSpan:
  finalSentence:
  recoveredObjectRef?:
  recoveredClaimValueRelationOrResult?:
  definingOrTestingPatternLocator?:
  predicateRef?:
  criteriaOrEvidenceRef?:
  allowedUse?:
  blockedInference?:
  checkAgainWhen?:

The optional fields are triggered separately:

Add this fieldOnly when…
predicateRefthe pattern defines or needs a reusable predicate.
criteriaOrEvidenceRefa receiving decision relies on the criterion or evidence identity.
allowedUsethe same value could drive materially different actions.
blockedInferencethe independently grounded plausible-reader test above warrants the correction, such as preventing an unsupported inference from readiness to gate passage.
checkAgainWhenexpiry or change could alter the claim or action during the intended use.
references and machine fieldsthe receiving use depends on those identities, including automation, audit, comparison or replay.

A relation, classification, assertion episteme, evaluation result, decision result, or record field keeps its own form. The repair note does not turn it into a new state predicate or result kind.

A.19.SPR:4.1 - Repair

For ordinary prose, inspect the sentence and the nearby text needed to recover its participants and referents:

  1. Find the item. For system-role wording, distinguish a local system-role kind, an obtaining assignment, its state condition, the world-side assignment-state relation, and an assertion about either. Do not stop at bare role.
  2. Write the claim. Say that the item has a value, that a relation obtains, that an assertion or result says something, or that a project record has a field value.
  3. Use the rule. Cite the applicable pattern when its criterion or distinction matters. If the rule already settles the sentence, A.19.SPR has finished its job.

Add a time boundary, evidence basis, allowed use, or blocked inference only under the triggers above. If the item or claim still cannot be recovered, keep the wording as a quotation or navigation cue, narrow its use, or state the blocker.

A.19.SPR:4.1.1 - Assignment-state exits
Recovered claimExit
One system-role assignment or its holder, with no state condition claimedA.2.1; the assignment itself is not readiness.
A reusable condition for assignments to one local system-role kindA.2.5 SystemRoleAssignmentStatePredicate, by value.
One assignment satisfies that condition during the relevant intervalThe world-side A.2.5 SystemRoleAssignmentStateRelation occurrence.
An affirmative or negative claim about the assignment or an established relation occurrenceA.2.5 SystemRoleAssignmentStateAssertion : U.Episteme; the assertion is not its EntityOfConcern.
Evidence, currentness, reliance, or an evaluation concerning that assertion epistemeA.2.4, A.10, or the evaluation pattern. Keep the assertion episteme distinct from the assignment and world-side relation.
Whether intended Work may enter nowA.15.5 or the receiving pattern. A.2.5 may supply an assignment-state input; it does not publish the admission result, gate decision, or Work occurrence.
A.19.SPR:4.1.2 - Readiness exits

When readiness or ready still hides which governed value is meant, use E.10.MOVE first. Once the meaning is recovered, use the pattern for each claim. A compound statement may need more than one exit:

Recovered readiness-like claimExit
A subject such as a patient or system has a value in a still-hidden state frameA.19.SPR, followed by the subject pattern that defines or tests that value.
An assignment satisfies an assignment-state conditionA.2.5.
One intended performance satisfies a work-entry criterionA.15.5 work-entry readiness result.
A distinct OperationalGate(profile) consumes declared checks and publishes a decisionA.21; a ready label alone is not gate passage.
A publication use, permission claim, or dated performed Work is meantUse E.24.PUB for publication availability or E.17 for a publication face, the permission pattern for permission, or A.13 followed by independent A.15.1 for Work. F.6 applies afterward only for assignment-bound attribution. Readiness wording establishes none of these claims.

A.19.SPR:4.2 - Where the repaired claim belongs

What the sentence meansUse this pattern or record
position in a declared CharacteristicSpaceA.19, with A.17, A.18, C.16, and C.16.P when construction is hidden
reusable transition law, trajectory, or dynamics modelA.3.3
system-role assignment with no state condition claimedA.2.1; do not treat assignment as readiness
by-value assignment-state condition, obtaining assignment-state relation, or assertion episteme about eitherA.2.5, keeping SystemRoleAssignmentStatePredicate, SystemRoleAssignmentStateRelation, and SystemRoleAssignmentStateAssertion distinct
evidence, currentness, reliance, or evaluation concerning an assignment-state assertionA.2.4, A.10, or the evaluation pattern; the assertion episteme does not become its subject
work-entry use of an assignment-state claimA.15.5 or the receiving pattern; A.2.5 supplies only the assignment-state input
language-state position for episteme or publication wordingC.2.2a and A.16.* after C.2.P when source-publication recovery is needed
source use, source currentness, source publication, or source-use dispositionC.2.P, E.17, E.24.PUB, E.9.DA, or the source-use rule for the recovered claim
evidence path state, evidence relation, or reliance dispositionUse A.10 to recover the source, independently established support relations, currentness and bounded use; use the defining pattern for the support relation or reliance decision.
assurance result, assurance claim, assurance input, or engineering-justification useB.3
constraint or local CVA.20 or the constraint pattern
ambiguous readiness or ready wordingE.10.MOVE until the governed value is recovered
work-entry readinessA.15.5
distinct gate decisionA.21 only when an OperationalGate(profile) consumes declared checks and publishes that decision
release or permission claimthe release or permission pattern; a readiness value establishes neither
publication use, publication face, form, or unit value, source-finding useE.17, E.17.0, E.17.AUD, or E.24.PUB as appropriate to the recovered claim
Description episteme admitted for specification use or specification refinementA.7, plus the specification-granting neighbouring pattern named by value: A.6.2, C.2.3, A.21, C.16, E.17, E.10, or another named pattern
temporal-claim classification and adequacy of an intervention-sensitive useC.27, using its Dyn0, Dyn1 or Dyn2 readings
mathematical-lens use admissibilityC.29, retaining LensUseBoundaryValue only as a declared C.29 field
DRR decision-adequacy result or source-use classificationE.9.DA
pattern-quality result or pattern-quality review statusE.21, with E.19 only as review or admission profile
administrative, review, dispatch, release or admission, or source-control statethe project record that carries the state. Keep current framework-development status there; retain reusable guidance and worked examples when they explain the pattern’s method.

A.19.SPR:4.3 - Keeping a technical state field

A technical field such as ...Status, ...Readiness, or ...State may stay when the text makes three things clear: what item the field describes, which values it can take, and which rule or criterion gives those values meaning.

Add an allowed-use boundary when it changes the receiving action. Apply §4’s grounded plausible-reader test before adding a blocked inference. Add a validity window or recheck condition when change could alter the claim or action during use. Add an identifier when that use depends on the identity.

If the three basic facts are missing, complete them or replace the field with the ordinary sentence the reader needs. A narrowing adjective alone does not recover the claim.

A.19.SPR:5 - Worked examples

Each example starts with wording for the stated use; §4 determines which further details are needed.

A.19.SPR:5.1 - Physical-system state

Before: “Pump 37 is in a good operating state.”

After: “Pump 37 satisfies InspectionOperatingCondition: its coolant temperature is 72 °C, within the 60–80 °C band, and its discharge pressure is 315 kPa, above the 300 kPa minimum.”

For a relied-on inspection decision, make the measurement basis and applicable condition recoverable. Add the reading time, condition edition and recheck condition when the decision depends on them.

A.19.SPR:5.2 - Work-entry readiness is not gate passage

Before: “Release 12 is ready.”

After: “At 10:00, the A.15.5 check found that PlanItem-Deploy-12 satisfied its release-entry criterion and was ready for work entry until 10:30; recheck if a required input changes.”

For replay, make the plan item, criterion, input facts, result and reliance window recoverable. Identify a separate result episteme or checking Work only when that identity matters; a claimed Work needs its A.13 basis and independent A.15.1 admission, with F.6 only for assignment-bound attribution. The work-entry finding alone establishes no gate passage. Use A.21 for a distinct OperationalGate(profile) that consumes declared checks and publishes its own decision.

A.19.SPR:5.3 - Source use and currentness

Before: “The source posture is good.”

After: “This review uses edition E7 for decision question Q. Reconsider that choice if the question or the source content needed to answer it changes.”

When the decision relies on a claim from E7, assess that claim’s currentness under B.3.4 using the premises and time limits that matter to this use. Preserve source and result identities when the receiving operation depends on them.

A.19.SPR:5.4 - Other repairs

  • Evidence. Replace “evidence status incomplete” with “Reliance on claim C remains unestablished because the needed calibration basis is missing; obtain the missing calibration basis and check again.” Add evidence and currentness references only when the receiving decision needs them.
  • Publication. Replace “publication posture allows decision input” with “This publication exposes candidate input X for the decision; the decision rule still evaluates X.”
  • Mathematical lens. Keep LensUseBoundaryValue in C.29 when its possible values and intended lens use are defined. State what the value permits for the intended lens use under C.29.
  • Temporal claim. For a C.27 classification, name the temporal claim and its Dyn0, Dyn1 or Dyn2 reading. State the supported use; add the intervention account only when the claim is intervention-sensitive.
  • Project-side state. Keep current framework-development status in its project record. Retain reusable guidance and worked examples that help the reader handle project status in the pattern’s stated practice.

A.19.SPR:6 - Conformance checks

CheckRequirement
CC-A19SPR-1The final sentence names the item and what is claimed or valued, or keeps the wording ordinary, quoted, navigation-only, narrowed, or blocked.
CC-A19SPR-2The rule or criterion is recoverable whenever the claim is not understandable or usable without it.
CC-A19SPR-3A predicate appears only when the pattern defines or needs one; relations, assertions, results, decisions, and record fields keep their own forms.
CC-A19SPR-4An allowed-use clause changes the receiving action. A blocked-inference clause passes §4’s independent-ground, plausible-reader and contribution test.
CC-A19SPR-5A time window, expiry rule or recheck condition appears when change could alter the claim or action during the intended use.
CC-A19SPR-6Source, evidence, assurance, publication, assignment state, work entry, gates, decisions, release or admission, and project records use the patterns or records that define or test those claims.
CC-A19SPR-7Source and publication patterns are not used as a general home for evidence, assurance, gate, Work, temporal, mathematical-lens, or project status.
CC-A19SPR-8A retained technical field names its item, possible values, and rule; it adds use, time, evidence, and blocked-inference fields only under their triggers.
CC-A19SPR-9A cold reader can say what the sentence is about, what it claims, and what to do or check next. Type-correct but opaque wording fails.
CC-A19SPR-10Corpus repair classifies each use; it never performs a blind global replacement of posture, state, status, or readiness.

A.19.SPR:7 - Common mistakes

MistakeSymptomRepair
Status word as coverposture or status hides a source relation, evidence result, assurance result, gate decision, or release claim.Say what item has which value or relation under the rule.
One broad word replaces anothersupport becomes support posture, basis posture, or source posture.Recover the source, evidence, assurance, relation, characteristic, or reader-help claim before choosing words.
Technical field without meaningA ...Status or ...Posture field has no object, possible values, or rule.Complete those three facts or replace the field with an ordinary sentence.
Development status in pattern proseThe framework-development project’s current review, dispatch, landing, release, or source-control state appears as user guidance.Move that status to the project record; keep the reusable explanation and examples needed by the pattern user.
Everything becomes a source-language caseEvidence, assurance, gate, Work, temporal, or lens-use claims are all sent to source or publication repair.Use the pattern for the claim.

A.19.SPR:8 - Relations

PatternContribution
E.10, E.10.ARCHRecognize the wording problem and keep one shared restoration architecture.
E.10.MOVEResolves ambiguous readiness-like wording before it exits to A.19.SPR or the pattern governing the recovered claim.
A.2.5, A.15.5Distinguish assignment-state predicate, world-side relation, assertion episteme, and the separate work-entry readiness result.
A.19, A.3.3, C.16.PDefine characteristic-space, dynamics, and characteristic or scale claims when those are the subject.
C.2.P, C.2.2a, A.16.*, E.17, E.24.PUBDefine source, language-state and publication claims, including the separate publication-availability occurrence.
A.10, B.3A.10 recovers provenance and bounded reliance; B.3 governs assurance claims. Each support relation retains its defining pattern.
A.20, A.21Define constraint or adjudication results and distinct gate decisions.
C.27, C.29Define temporal-claim and mathematical-lens uses, including their local fields.
E.9.DA, E.21, E.19Define DRR adequacy, pattern-quality results, and review or admission profiles.
F.18, F.19Settle durable names after the claim is known and rewrite the final practitioner path in plain technical language.
E.11Places first-use cues without creating a second routing table.

A.19.SPR:9 - Rationale

Recover the item and the value, relation, result or claim being stated; name the rule or criterion when the reader needs it to understand or act. These facts let practitioners use short engineering language while retaining each claim’s kind and conditions.

A local field such as LensUseBoundaryValue remains useful when its object, possible values, and rule are clear. Broad phrases such as source posture, evidence posture, or release posture should instead become the sentence or project record the reader needs.

A.19.SPR:End

A.19.SOURCE-SET-SPACE-SUBSTRATE - Source-Set and Search/Outcome-Space Substrate

Type: Architectural (A) Status: Stable Normativity: Normative

Plain-name. Source-set / search-outcome-space substrate.

Working contribution. Identify the set being searched or compared, the space used to describe its members, and the space in which their outcomes are judged. State the relation that connects source members to outcome values and the limits of that relation. Search and outcome may use the same A.19 space; the two uses still need to remain distinguishable.

A.19.SOURCE-SET-SPACE-SUBSTRATE:0 - Use this when

Use this pattern when a search, comparison or synthesis depends on all of the following:

  • one declared source set or composition of source sets still matters and must stay recoverable;
  • one search-side space reference and one outcome-side space reference must both be explicit;
  • the line must say whether those refs resolve to one declared CharacteristicSpace or to two distinct declared CharacteristicSpace values;
  • the reader must know what the source-to-outcome relation connects, in which direction, and through which declared carrier, declared map ref, or qualifier ref;
  • distortion, uncertainty, or error must be specified.

This is the right pattern for QD, OEE, archive/front, or adjacent synthesis lines when the problem is no longer only “what space exists?” and not yet “what shortlist or shipped result do we publish?”.

Not this pattern when:

  • you only need to declare or compare CharacteristicSpace itself, with no source-set or source-to-outcome requirement; use A.19;
  • you are publishing selector or shipping metadata such as SelectorOutcomeKind, SetResultFamily, HandoffKind, or public shortlist identity; use G.5 or G.10;
  • you are building one interpretive view over an already-declared substrate; use A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW or a local specialization such as G.2;
  • you need live-pool or frontier-retention policy; use C.19. Use A.15.7 to choose a situation-responsive next action and C.24 to plan tool or service calls after the action is fixed.

A.19.SOURCE-SET-SPACE-SUBSTRATE:0.1 - What goes wrong if missed

If this pattern is missed, authors usually collapse several different things into one vague “space” or one vague “projection”:

  • the declared source set disappears behind bare words such as front, archive, palette, or portfolio;
  • SearchSpaceRef and OutcomeSpaceRef never become explicit, or SpaceRefRelationKind never becomes explicit, so one line hides whether search and outcome use one declared space twice or two different declared spaces;
  • DescriptorMapRef or DistanceDefRef gets mistaken for the space itself rather than one representation or metric qualifier;
  • publication metadata in G.5 or G.10 starts standing in for substrate semantics;
  • and distortion, uncertainty, or error is either hidden or treated as if every non-trivial case were only one bridge-loss story.

The result looks tidy, but the reader cannot tell what is being searched, what is being evaluated, what is only being published, and where uncertainty enters.

A.19.SOURCE-SET-SPACE-SUBSTRATE:0.2 - What this buys

This pattern buys one conservative but expressive substrate declaration:

  • the source set stays visible;
  • the search-side and outcome-side references over A.19 spaces stay distinct;
  • the relation between those refs becomes inspectable instead of being hidden in one overloaded noun or verb;
  • heavier qualifier refs remain available without being forced into every case;
  • and interpretive-view or publication neighbors can reuse the substrate without changing what it means.

The practical payoff: readers can tell what the line is acting on, what relation between the two space refs it assumes, what kind of qualification they must keep in view, and which neighboring pattern governs the next use or action if that requirement grows.

A.19.SOURCE-SET-SPACE-SUBSTRATE:0.a - TERM/LEX token-status guard (local-first)

Keep this token-status split explicit:

  • CharacteristicSpace is the reused A.19 kind. This pattern does not mint a second space kind.
  • SearchSpaceRef and OutcomeSpaceRef are role-named local fields whose slot content is typed by the existing CharacteristicSpaceRef / SpaceRef idiom. They are not new heads, not slot aliases inside the space, and not U.Role claims. These field names distinguish the search-side and outcome-side uses of the referenced A.19 space.
  • SpaceRefRelationKind is a local relation-kind field over those two refs. In this pattern, sameDeclaredSpaceAs and distinctDeclaredSpaceFrom are controlled token values for that field, not free prose.
  • SourceToOutcomeRelation and DistortionPosture are local declaration fields. Their field names do not by themselves create one new generic ontology; the declaration requirement is satisfied only when their payload is explicit enough to audit.
  • SourceSetFamily, SourceSetComposition, and DerivedViewKind are local fields in this SourceSetSpaceSubstrate declaration. Their use as fields does not establish a new object kind.
  • BasePaletteRef, OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, BridgeDistortionNote, DescriptorMapRef, and DistanceDefRef are neighboring refs or interpretive qualifiers reused here. This pattern may cite them, but it does not redefine them.
  • carrier inside SourceToOutcomeRelation identifies the relation definition, map, model or operation that supplies the connection. Its definition can be stated or cited where the reader can recover it. A containing paragraph expresses that definition; the physical or digital entity bearing that text is identified separately under E.24.PUB.

A.19.SOURCE-SET-SPACE-SUBSTRATE:0.b - First-minute operator cue and confusion guide

When the receiving use depends on the source set, search space and outcome space together, recover the following facts from the existing account. Add only what is missing; an adequate paragraph or model declaration needs no duplicate form.

First recover:

  1. Name the source set, or the contributing source sets and their composition.
  2. Point SearchSpaceRef and OutcomeSpaceRef to declared CharacteristicSpace.
  3. Choose sameDeclaredSpaceAs or distinctDeclaredSpaceFrom.
  4. State the source-to-outcome relation in direction, mode, and carrier.
  5. State the applicable limitations. A primary posture token may organize them; supply it when a selected interface requires one, without hiding other material qualifications.

If one of these facts cannot yet be recovered, preserve the established source and space facts, name the missing basis, and withhold the complete substrate claim and only the use that depends on that basis. Use the applicable subject pattern when it can supply the missing result.

If the question under repair sounds like…Use nowWhy
“Which space are we searching in and which space are we judging in?”A.19.SOURCE-SET-SPACE-SUBSTRATEThis pattern governs the source set, both space uses and the source-to-outcome relation.
“How should I help the reader inspect that already-declared line?”A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWThat is one interpretive reading over the substrate, not the substrate declaration itself.
“What do we publish, ship, keep live, or plan next?”Use the corresponding alternative in §0.Distinguish publication, live-pool policy, next-action choice and call planning for an already fixed action.
“I only need one space declaration.”A.19No source-to-outcome relation needs to be declared.

A descriptor map or distance definition supplies one part of this account; it does not identify the source set and both spaces by itself.

A.19.SOURCE-SET-SPACE-SUBSTRATE:1 - Problem frame

A search, comparison or synthesis may depend on several source sets and spaces. Make the following information recoverable:

  • one declared source set, such as a front, archive or palette, or a composition of identified source sets;
  • one search-side reference to an A.19 CharacteristicSpace;
  • one outcome-side reference to an A.19 CharacteristicSpace;
  • one SpaceRefRelationKind over those two references, stating whether they resolve to the same declared space or to two different declared spaces;
  • one relation from the source-side line into the outcome-side line;
  • and one declared posture about whether that relation is transparent, approximate, learned, lossy, uncertain, or otherwise qualified.

Without a declaration of these components, readers may use a neighbouring declaration for a question it does not answer. A.19 gets stretched from space typing into source-set governance. C.18 descriptor maps start masquerading as the whole search space. G.5 and G.10 publication fields start reading like ontology. Interpretive views or atlas views drift into default meaning instead of staying optional derived help.

A.19.SOURCE-SET-SPACE-SUBSTRATE:2 - Problem

How should one declare a source-set and search/outcome-space line so that:

  1. the declared source set remains explicit and recoverable;
  2. SearchSpaceRef and OutcomeSpaceRef stay refs to declared A.19 CharacteristicSpace, not new free-floating space kinds;
  3. the text states whether those refs point to one declared space or to two distinct declared spaces;
  4. the source-to-outcome relation is explicit enough for the reader to know which source-to-outcome relation mode is being claimed: mapped, projected, translated, scored, or otherwise connected;
  5. distortion, uncertainty, and error are stated rather than hidden in prose;
  6. SourceSetComposition and DerivedViewKind remain conditional fields rather than fabricated mandatory baggage;
  7. qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote remain available but substrate-side only;
  8. and neighboring declarations such as A.19, C.18, G.5, G.10, and A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW can dock to the substrate without redefining it?

A.19.SOURCE-SET-SPACE-SUBSTRATE:3 - Forces

ForceTension
A.19 typing vs adjacent substrate requirementA.19 already declares CharacteristicSpace, but source-set and publication-form semantics still need a separate substrate declaration.
Precision vs over-typingThe line needs to state its ref positions, ref-to-ref relation kind, and relation posture, but it should not fabricate composition, derivation, metrics, or transition qualifier when the case does not need them.
Reuse vs semantic collapseDescriptorMapRef, DistanceDefRef, OutcomeMapRef, or BridgeDistortionNote are useful qualifiers, but they must not silently become the whole substrate.
User readability vs architectural honestyCold readers need a first-minute explanation, while specialist readers still need boundaries and docking rules.
Interpretive views vs substrate coreAtlas or interpretive-view lines can be valuable, but they should remain optional derived help rather than the default meaning of the substrate.
Uncertainty honesty vs fake closureMany current lines use learned, adaptive, unstructured, or distribution-valued spaces or relations; the pattern must expose that posture without pretending the heaviest qualification posture is already settled.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4 - Solution

Declare the source set, both space uses and the source-to-outcome relation with its limitations. Add conditional fields or companion declarations when the intended use requires them.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.1 - Substrate declaration and related work

Use this pattern to declare:

  • the source set, or composition of source sets, used by the search or comparison;
  • the recoverable source-set identity when the family name alone would be ambiguous;
  • the search-side reference to one declared A.19 CharacteristicSpace;
  • the outcome-side reference to one declared A.19 CharacteristicSpace;
  • the SpaceRefRelationKind over those two ref positions;
  • the source-to-outcome relation;
  • and the distortion, uncertainty, or error posture for that relation.

Do not use this pattern to declare:

  • A.19 space typing itself;
  • selector outcome publication, shortlist identity, or shipping closure;
  • live pool policy or enactment planning;
  • or optional interpretive-view families that interpret or reorganize an already-declared substrate.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.2 - Minimal declaration

The notation below names the required content and conditional fields:

SourceSetSpaceSubstrate := <
  SourceSetFamily?,
  SourceSetRef?,
  SearchSpaceRef,
  OutcomeSpaceRef,
  SpaceRefRelationKind,
  SourceToOutcomeRelation,
  DistortionPosture,
  SourceSetComposition?,
  DerivedViewKind?,
  BasePaletteRef?,
  OutcomeMapRef?,
  SpaceMetricRef?,
  TransitionRelationRef?,
  BridgeDistortionNote?
>

Interpret the fields as follows:

  • SourceSetFamily? names the declared family of the immediate source set and is required for a single-source account. For a composition without a distinguished source, SourceSetComposition supplies the source basis by identifying each contributing source, its family and member contribution rule. If the receiving use singles out a primary source, identify that source and retain its family in SourceSetFamily.
  • SourceSetRef? names the declared source set or set result when its identity would otherwise be ambiguous, including when a neighboring governing pattern supplies that identity. For a composition, recover each contributing set through SourceSetComposition; add a separate SourceSetRef when the receiving use also depends on the identity of a combined set result. A reference may be omitted only when its intended set is otherwise unambiguous.
  • SearchSpaceRef points to one declared A.19 CharacteristicSpace in the search-side position.
  • OutcomeSpaceRef points to one declared A.19 CharacteristicSpace in the outcome-side position.
  • SpaceRefRelationKind states how those two refs relate. In ordinary use, the token is either sameDeclaredSpaceAs or distinctDeclaredSpaceFrom.
  • SourceToOutcomeRelation identifies the source members or values, target outcome values, direction and relation mode, with the defining map, model, operation or rule in carrier. The mode distinguishes a description, projection, prediction, scoring relation or other declared connection; naming it does not establish that its output is accurate or suitable for a receiving use.
  • DistortionPosture states the conditions and limits needed by the receiving use. A primary token may organize this account or satisfy a selected interface requirement. It does not make the qualifications mutually exclusive: a learned map may also be uncertain and model-dependent. The local tokens include transparent-for-current-use, lossy-bridge, metric/model-dependent, transition-dependent, uncertainty-bearing, learned/adaptive, and unstable-under-refresh.
  • SourceSetComposition, DerivedViewKind, and related ...Kind values remain declaration fields or controlled field values unless some governing pattern promotes them; they are not automatically independent heads merely because their names end with Kind.

The two reference fields designate A.19 spaces. SpaceRefRelationKind reports whether their resolved values are the same or distinct under A.19 meaning. Two identifiers or declaration documents may describe the same space; different spellings alone establish no distinction. Recover a changed basis, Scale meaning or other space-defining content before asserting distinctness. This local token field is not itself an A.6.5 reusable relation-kind declaration.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.3 - Substrate declaration laws (SS-0..SS-7)

SS-0 - Required declaration content. Treat a line as declared substrate only if one recoverable source-set basis, two recoverable space refs, one explicit ref-to-ref relation kind, one explicit source-to-outcome relation, and one explicit posture are present together.

SS-1 - Ref typing is preserved. SearchSpaceRef and OutcomeSpaceRef must resolve to declared A.19 CharacteristicSpace. They do not become parallel space kinds, slot aliases, or role claims.

SS-2 - Source-set recoverability is mandatory. The reader must be able to recover the source set and its declared family. For a composition, recover every contributing set, its family and its member contribution rule; identify a primary source only when the receiving use distinguishes one. Use SourceSetRef, SourceSetComposition or an accessible source that uniquely supplies the needed identities. A family name alone does not resolve several same-family sources.

SS-3 - Relation requirement must be explicit. SourceToOutcomeRelation is conforming when its participants, direction, mode and defining map, model, operation or rule are recoverable. Add an interpretive qualifier only when it changes that relation’s use.

SS-4 - Posture honesty is mandatory. DistortionPosture must say whether the line is transparent for current use or qualified by loss, metric/model dependence, transition dependence, uncertainty, learning/adaptation, or instability under refresh. State all material qualifications, even when one primary token is used for indexing. A token alone supplies no error bound, validation result or permission to rely on the outcome.

SS-5 - Conditional and qualifier fields stay subordinate. SourceSetComposition, DerivedViewKind, BasePaletteRef, OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote may clarify the substrate, but they do not replace the required declaration content and do not become mandatory everywhere.

SS-6 - Publication and policy stay outside. Publication metadata, shortlist identity, live-pool policy, and enactment policy remain neighboring decisions. A substrate line may feed them, but it does not decide them.

SS-7 - Admission is fail-closed. If the source basis cannot be recovered, either space ref is unresolved, SpaceRefRelationKind cannot be chosen, relation direction, mode or carrier remains vague, or a qualification needed by the receiving use is unresolved, then the complete substrate claim is not established. Preserve the recovered source and space facts, state the missing basis and withhold only the use that depends on it. Use the applicable subject pattern when it can supply the missing result.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.4 - Profiles

Use one of these ordinary profiles:

  • Shared-space profile. SearchSpaceRef and OutcomeSpaceRef both resolve to the same declared CharacteristicSpace, and SpaceRefRelationKind = sameDeclaredSpaceAs.
  • Cross-space profile. SearchSpaceRef and OutcomeSpaceRef resolve to two distinct declared CharacteristicSpace values, and SpaceRefRelationKind = distinctDeclaredSpaceFrom.
  • Derived-source supplement. If the visible source set is derived, make the derivation recoverable. Use DerivedViewKind and BasePaletteRef when the receiving use needs that derivation or would otherwise lose the base palette, as §4.7 specifies.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.5 - Operational declaration sequence (fail-closed)

When declaring one substrate-bearing line, proceed in this order:

  1. Entry test. Confirm that the line needs source-set plus search/outcome-space plus relation/posture discipline. If it only needs CharacteristicSpace typing, use A.19. If it only needs publication or policy, apply the governing pattern that carries that publication or policy question.
  2. Recover the source basis. For one immediate source set, state its family and recover its identity. For a composition, use SourceSetComposition to identify every contributing set, its family and how its members contribute; designate a primary source only when the receiving use singles one out. Add SourceSetRef or cite a source when needed to make an identity unique.
  3. Recover the space refs. Point SearchSpaceRef and OutcomeSpaceRef to already-declared CharacteristicSpace.
  4. Choose the ref-to-ref relation kind. Declare sameDeclaredSpaceAs when both references resolve to the same A.19 space by value, and distinctDeclaredSpaceFrom when their defining contents establish distinct values. If that identity question is unresolved, retain the uncertainty rather than inferring difference from two declarations.
  5. State the source-to-outcome relation. Give direction, mode, and carrier. If one named OutcomeMapRef or another declared interpretive qualifier carries the relation, cite that qualifier. Otherwise state the relation definition or supplying operation in prose.
  6. State the qualifications. Identify the loss, model or metric dependence, transition dependence, uncertainty, adaptation or refresh limit that affects the use. A transparency claim needs a basis. Retain every material condition; use a primary token when useful for indexing or required by a selected interface.
  7. Add only needed fields. Add composition, derived-view, base-palette, metric, transition, or bridge qualifiers only when the case depends on them.
  8. Run the boundary check. If the line starts deciding publication metadata, shortlist identity, live candidate policy, enactment policy, or interpretive-view organization, stop and apply the pattern that governs that question.

Incomplete-account result. An unresolved requirement in steps 1-5 leaves the complete substrate claim unestablished. Apply SS-7: preserve what is known and withhold only uses that require the missing basis. A declared uncertainty is a qualification to preserve, not by itself a failure to identify the substrate.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.6 - Canonical rewrite forms

The §4.2 schema can express either profile: both space references may resolve to the same A.19 value or to distinct values. Use a block, prose or an existing model account that makes the source, spaces, relation and limitations recoverable. A new block is not required when that content is already sufficient.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.7 - Conditional fields stay conditional

Use SourceSetComposition when the account consumes several declared source sets. Identify each contributing set and its family, and state how its members enter the source basis, such as a union or specified subsets when that is the construction.

For a single immediate source, SourceSetFamily remains required. For a composition, retain a primary source and its family only when the receiving use distinguishes one. Otherwise the recoverable composition supplies the source basis without inventing a primary family. Neither branch silently changes any contributing set’s identity or family.

For example, a comparison may consume the union of declared Front-F and Archive-A without privileging either. SourceSetComposition identifies both sets, their families and the union. No primary SourceSetFamily is required; both space refs and the source-to-outcome rule apply to that declared source basis.

Use DerivedViewKind only when one derived view is active and the reader must be able to recover that derivation.

Use BasePaletteRef only when a derived tradition or palette view would otherwise hide the recoverable base palette.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.8 - Qualifier refs stay substrate-side

OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote are admitted as substrate-side qualifier refs.

Use them when:

  • one OutcomeMapRef or named declared map ref disciplines the source-to-outcome relation;
  • one metric disciplines spread, neighborhood, or comparison claims;
  • one TransitionRelationRef disciplines dynamic coupling or transfer;
  • or one bridge-loss note is the reason the relation is qualified.

These qualifiers help explain the relation. They do not replace the recoverable source basis, the search-side and outcome-side spaces, or the declared relation and its applicable limitations. The source basis may be one set or the composition described in §4.7.

The substrate cites the qualifier definition on which it relies. A later view may introduce its own representational qualification; distinguish that view claim from a change to the source-to-outcome relation. If the underlying relation changes, revise its declaration and recheck dependent uses.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.9 - Descriptor maps and distance definitions dock here, but do not replace the space refs

When a neighboring line already uses DescriptorMapRef or DistanceDefRef, dock it:

  • DescriptorMapRef may realize or qualify the search-side or outcome-side representation requirement, as the current line requires;
  • DistanceDefRef may realize or qualify the metric requirement over that representation on either side, as the current line requires;
  • but neither one replaces SearchSpaceRef or OutcomeSpaceRef;
  • and CharacteristicSpace remains a different kind from DescriptorMap.

Use this rule when a reader could mistake a descriptor map or distance definition for the declared space.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.10 - Publication and shipping remain downstream consumers

G.5 and G.10 may carry metadata such as SelectorOutcomeKind, SetResultFamily, SourceSetFamily, SourceSetComposition, DerivedViewKind, and BasePaletteRef when one selected or shipped result is being published.

That does not mean G.5 or G.10 defines the substrate.

Read the boundary this way:

  • this pattern defines the substrate that later publication must preserve;
  • G.5 publishes selector-facing outcome metadata;
  • G.10 ships publication metadata and pins;
  • neither one redefines the search-side reference, the outcome-side reference, or the source-to-outcome relation.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.11 - Ordinary and heavier use

Stop with the source set, both resolved spaces, their same/distinct relation, the source-to-outcome connection and its applicable limits. Add composition, derivation, map, metric, transition or Bridge detail only when it changes the receiving use. A later view or publication can reuse this account without copying it into another declaration.

A.19.SOURCE-SET-SPACE-SUBSTRATE:4.13 - Using the substrate with neighboring patterns

Once the substrate is declared, select the neighboring pattern for the remaining question:

  • Use A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW when the next requirement is interpretive help over the same substrate. The interpretive view may foreground the line, but it does not become the ontology.
  • Use G.2 when that interpretation becomes palette-first, tradition-facing atlas work. Keep the base palette and the cited substrate recoverable while doing it.
  • Use A.6.P when one passage collapses source set, space ref, interpretive view, atlas view, or map/ref wording into one umbrella word. Repair the wording back to the substrate declaration before adding more theory.
  • Use F.18 when the problem is label choice or naming-side comparison around this declaration. Naming notes may explain why one head is better named; they do not settle the substrate relation.
  • Use A.0 when the task is cold-reader glossing of these tokens. Glosses explain the terms; the source, spaces, relation and limitations required by §4.2 must still be recoverable from the account.

If a neighboring use needs a changed source-to-outcome relation or qualification, revise the declaration and reconsider the conclusions that depend on the change. Reuse unaffected content.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5 - Archetypal Grounding

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.1 - System

One QD line keeps saying that one archive is both the search-side role and the evaluation basis. Downstream readers need to see that the same declared CharacteristicSpace can still occupy two different role positions without turning the archive or the descriptor map into the space itself.

In this constructed case, Archive-12 is the selected candidate set. The declared descriptor map assigns behavior Coordinates to its members; the separately declared neighborhood metric is used to assess coverage in that same behavior space.

SourceSetFamily       = Archive
SourceSetRef          = Archive-12
SearchSpaceRef          = BehaviorCharacteristicSpace@ed=12
OutcomeSpaceRef         = BehaviorCharacteristicSpace@ed=12
SpaceRefRelationKind    = sameDeclaredSpaceAs
SourceToOutcomeRelation = QDDescriptorMap@ed=9 assigns each Archive-12 candidate
                          its Coordinates in BehaviorCharacteristicSpace@ed=12;
                          a coverage comparison uses ArchiveNeighborhoodMetric@ed=4
                          on those Coordinates
DistortionPosture       = metric/model-dependent; descriptor realization and
                          neighborhood metric qualifier are active
DescriptorMapRef        = QDDescriptorMap@ed=9
DistanceDefRef          = ArchiveNeighborhoodDistance@ed=4
SpaceMetricRef          = ArchiveNeighborhoodMetric@ed=4

The archive supplies the candidate members; both space references resolve to the same declared CharacteristicSpace. The descriptor map assigns Coordinates, and the distance and metric define the stated coverage comparison. Selection or archive maintenance can reuse these relations while keeping the archive distinct from the space.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.2 - Episteme

One synthesis line presents one derived tradition front and then starts speaking as if the visible front were the default meaning of the whole palette.

SourceSetFamily        = Front
DerivedViewKind        = TraditionFront
BasePaletteRef         = SoTAPaletteDescriptionId
SearchSpaceRef         = TraditionComparisonSpace@ed=3
OutcomeSpaceRef        = AdoptionOutcomeSpace@ed=2
SpaceRefRelationKind   = distinctDeclaredSpaceFrom
SourceToOutcomeRelation = for each retained tradition profile, AdoptionEstimate@ed=1
                          uses its integration requirements and the named team's
                          capability and workload facts to estimate adoption cost
                          and expected benefit in AdoptionOutcomeSpace@ed=2
DistortionPosture      = metric/model-dependent; the estimate is conditional on those
                         team and workload facts and omits unmodelled adoption effects

The visible front stays a derived view over the recoverable palette. AdoptionEstimate@ed=1 supplies the stated conditional source-to-outcome mapping. A later interpretive or atlas view may reorganize the presentation while preserving that mapping and its model limitations.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.3 - Boundary anti-case

One note says only that “the shortlist front is the published result for the current selector result” and names no source-to-outcome relation, no search-side space, no outcome-side space, and no posture.

This is not a substrate declaration. It is publication metadata over one already-selected set.

Apply G.5 or G.10 to that note.

A.19.SOURCE-SET-SPACE-SUBSTRATE:5.4 - Use-situation spread

Use the pattern this way across different working situations:

Working situationWhat to do with this patternWhat must stay explicitCommon miss avoided
Archive-side QD line where navigation and evaluation stay in one declared behavior spaceUse the shared-space profile. Recover the source basis, both space uses, their same-space relation, the source-to-outcome connection and its limitations; add descriptor/metric qualifiers when used.The archive as source set, both role-refs, the same declared space and applicable qualifications.Treating the archive or descriptor map as if it were the space itself.
Derived tradition/front line that is judged against one different outcome spaceUse the cross-space profile. Keep the derivation and base palette recoverable where the receiving use depends on them; add DerivedViewKind and BasePaletteRef when needed or required by its selected publication contract.The derived view stays derived, the needed base palette remains recoverable, and the cross-space relation stays explicit.Letting the visible front replace the base palette or hiding the adoption model’s limitations.
Learned, adaptive, or uncertainty-bearing line where the space is declared but heavier qualification remains case-boundKeep the substrate core recoverable and state the uncertainty, adaptation or refresh conditions that affect the receiving use. Add a posture token when the selected interface requires it.The reader can distinguish the declared substrate from unresolved accuracy, applicability or stability claims.Pretending every case is either fully transparent or fully described by one metric specification.
Shortlist or publication note that only says what set result or publication form is shown or shippedDo not use this pattern. Apply G.5 or G.10.The note stays publication-facing instead of imitating substrate depth.Padding publication metadata with pseudo-substrate language.

A.19.SOURCE-SET-SPACE-SUBSTRATE:6 - Bias-Annotation

  • Gov bias. The pattern prefers explicit declaration over convenient shorthand.
  • Arch bias. The pattern keeps substrate, interpretive view, and publication consumers separated even when one merged story would read more smoothly.
  • Prag bias. The pattern prefers a short substrate declaration that can be reused across search, synthesis, and publication-adjacent lines.
  • Qualification bias. Learned or adaptive relations need their applicable uncertainty and model limits. A metric or transition model is added only when the claim uses it.

A.19.SOURCE-SET-SPACE-SUBSTRATE:7 - Conformance Checklist

Apply these declaration checks to the claims and qualifiers used:

IDCheck questionFail whenRepair or governing pattern
CC-A19SS-1Is the line declaring one substrate-bearing relation rather than only CharacteristicSpace, publication metadata, or policy?The line only names a space object, or only publishes, ships, or retains something, without declaring the source, space references, connecting relation and applicable qualifications.Use the corresponding alternative in §0.
CC-A19SS-2Is the source basis recoverable for the case?A contributing set, its family or its member contribution rule is ambiguous, or a primary source is invented for a composition that distinguishes none.Recover each set identity and family and any composition under §4.7; use refs or accessible defining sources as needed.
CC-A19SS-3Do SearchSpaceRef and OutcomeSpaceRef both resolve to declared A.19 CharacteristicSpace, and is SpaceRefRelationKind explicit?One or both refs are vague, or the line leaves the same-space versus cross-space question to inference.Restore the two refs and declare sameDeclaredSpaceAs or distinctDeclaredSpaceFrom.
CC-A19SS-4Is the source-to-outcome relation explicit in its participants, direction, mode and defining basis?The relation remains hidden in an umbrella phrase with no recoverable map, model, operation or rule.State the participants, direction, mode and defining basis or cite where they can be recovered.
CC-A19SS-5Are the relevant qualifications explicit and supported for the claimed use?Material limits are missing, or different qualified cases are blurred into one generic loss story.State the qualifications and the basis needed by that use. If needed support is missing, retain the established content and withhold only the dependent conclusion; a primary token is required only by a selected interface.
CC-A19SS-6Are conditional and qualifier fields used only when they do work?Composition, derivation, base-palette, declared map ref, metric, transition, or bridge qualifiers are fabricated everywhere or silently become core.Remove unused qualifiers; keep only the fields the case depends on.
CC-A19SS-7If DescriptorMapRef or DistanceDefRef is active, does the text say they realize or qualify the relation rather than replace the space ref?The descriptor map or distance definition is treated as if it were the declared search-side or outcome-side space.Re-state the docking rule and keep the two space refs visible.
CC-A19SS-8Does the line stay out of publication and policy work?The prose starts deciding shortlist identity, selector outcome, shipping closure, or live-pool/enactment policy.Split the line and move those downstream decisions to their governing patterns.
CC-A19SS-9Can the account establish the substrate claim needed by the use without inventing facts?A required source identity, space resolution, relation or material qualification remains unsupported.Return the recovered components and the missing basis; withhold the complete claim and only uses that depend on that gap.
CC-A19SS-10Could a cold reader take the next declaration step from this line without surrounding memo help?The line still speaks only in umbrella words such as space, projection, or portfolio, and the reader cannot tell what to fill next.Use the declaration sequence in §4.5 and recover the needed content from §4.2 before reuse.
CC-A19SS-11When the next question is interpretive-view, publication, or policy, is the next governing pattern explicit?The text fails to distinguish substrate declaration, interpretation, publication and policy decisions, so the reader cannot tell where to continue.Separate the claims and use the corresponding alternative in §0.
CC-A19SS-12Does the use claim only the breadth its declared posture and qualifiers license?The prose implies universal geometric closure or one universal heavy-qualification story, but the declared posture or qualifiers stay narrower, uncertain, learned/adaptive, or case-bound.Narrow the claim or add the missing posture/interpretive qualifiers that make the broader claim honest.

A.19.SOURCE-SET-SPACE-SUBSTRATE:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
Treating one archive or front as the search space itselfA source set is not the same kind as one declared CharacteristicSpace.Keep the source-set identity and family, or its composition, separate from SearchSpaceRef.
Leaving SpaceRefRelationKind implicitThe reader then has to guess whether search and outcome share one declared space or use two distinct declared spaces.Declare sameDeclaredSpaceAs or distinctDeclaredSpaceFrom next to the two refs.
Letting DescriptorMapRef stand in for the whole substrateA descriptor map is distinct from the declared space and its uses.State the docking rule and keep the space refs visible.
Making SourceSetComposition or DerivedViewKind mandatory in every lineThe line fabricates composition or derivation where none exists.Keep them conditional.
Publishing with bare portfolio languageportfolio blurs retained-set, selected-set, and posture talk.Use declared source-set and outcome metadata instead.
Treating all distortion as one bridge storyNot every qualified relation is bridge-mediated.State the posture.
Letting G.5 or G.10 sound like the substrate itselfPublication metadata then replaces substrate semantics.Keep publication as downstream use of the substrate.

A.19.SOURCE-SET-SPACE-SUBSTRATE:9 - Consequences

Benefits

  • Readers can see what the line is acting on, what spaces it distinguishes, what relation is declared between the two space refs, and what outcome load it claims.
  • The source and space declaration can be reused for representation, selector-result declaration and publication.
  • Heavier qualifiers such as declared map refs, metrics, transitions, and bridge-loss notes remain usable without being forced into every initial declaration.

Trade-offs

  • The line must expose one relation and one posture instead of hiding them in umbrella prose.
  • Some cases that used to look “simple” will expose uncertainty or loss that now needs to be declared.
  • Neighboring interpretive-view or publication patterns may need to be read as companions rather than assumed from local shorthand.

A.19.SOURCE-SET-SPACE-SUBSTRATE:10 - Rationale

Beyond the space structure defined by A.19, this declaration identifies:

  • which declared source set is active;
  • which declared space is named in the search-side position;
  • which declared space is named in the outcome-side position;
  • what SpaceRefRelationKind says about those two refs;
  • how source members are connected to outcome values;
  • and the transparency, distortion, uncertainty or error claimed for that connection.

That is why this pattern stops before interpretive views and before publication metadata. If it tried to say less, the load would collapse back into vague space or projection talk. If it tried to say more, it would start absorbing views, fronts, archives, shortlists, or shipping semantics that belong elsewhere.

A.19.SOURCE-SET-SPACE-SUBSTRATE:11 - SoTA-Echoing

SoTA practicePrimary source(s)Practice demand disciplined herePractical safeguard boughtAdoption stance
Evolutionary models relate genotype and phenotype descriptions or model selection across several levels.Vanchurin, Geometric framework for biological evolution (2026); Warrell et al., Variational methods for Learning Multilevel Genetic Algorithms using the Kantorovich Monad (2024).SS-0, SS-2, CC-A19SS-1, CC-A19SS-2.Provides comparisons for making the represented objects and their connecting relations explicit.Adapt. These are subject-specific mathematical constructions; the source-set declaration rules here are an FPF adaptation.
MOUR-QD distinguishes candidate solutions, feature descriptions, objective values and an archive with local Pareto comparisons.Janmohamed and Cully, Multi-Objective Quality-Diversity in Unstructured and Unbounded Spaces (2025), Introduction and §2.SS-1, SS-3, CC-A19SS-3, CC-A19SS-4, worked cases 5.1 and 5.2.Keeps the source members, space uses and source-to-outcome relation distinguishable.Adopt/Adapt. Preserve the subject distinctions; express the needed references and relations under FPF.
Feature spaces may be learned or unstructured, while uncertain QD may require distributions of fitness and descriptor values rather than single deterministic values.Janmohamed and Cully (2025), Introduction and §2; Flageat et al., Extract-QD Framework: A Generic Approach for Quality-Diversity in Noisy, Stochastic or Uncertain Domains (2025), Introduction and §2.2.SS-4, SS-5, CC-A19SS-5, CC-A19SS-6.Makes the applicable uncertainty and model limits explicit without prescribing one metric or transition model for every use.Adopt/Adapt. Retain the stated qualifications; select additional models and references for the receiving use.

A.19.SOURCE-SET-SPACE-SUBSTRATE:12 - Relations

A.19.SOURCE-SET-SPACE-SUBSTRATE:End


A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW - Interpretive Views of Declared Source Sets and Search/Outcome Spaces

Type: Architectural (A) Status: Stable Normativity: Normative

Plain-name. Declared-substrate interpretive view.

Declared-substrate interpretive view. An explanation or representation that answers an inspection question about an already-declared source set, its search/outcome spaces and their connection. Cite that substrate directly or through a source set or set result that makes it recoverable. Use the simplest sufficient interpretation; use atlas form when the question needs several views or qualifications read together. Formal epistemic viewing and U.View claims have the additional conditions in §4.8.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0 - Use this when

Use this pattern when one already-declared substrate from A.19.SOURCE-SET-SPACE-SUBSTRATE is already in force, and the current passage either cites that substrate directly or works through one declared source-set entry point or set-result entry point that keeps the substrate recoverable, but the reader still needs one interpretive view to see how the line should be read in practice.

Typical indicators are:

  • the substrate is already declared, but one thinner interpretive view is still needed so the active source set, search-side space, outcome-side space, or distortion posture stays understandable;
  • one fuller atlas-form reading may help collect several typed set views, active set results, cited spaces, declared map refs, or interpretive qualifiers without changing the underlying substrate;
  • one derived tradition or palette view must stay recoverable as a view over a base palette rather than silently becoming the palette’s default meaning;
  • or one line needs optional qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, or BridgeDistortionNote, but those pins must stay qualifiers rather than the semantic center.

This is the right pattern when the working need is no longer “what substrate is declared?” and not yet “what shortlist, publication form, or shipped result do we emit?”.

Not this pattern when:

  • you still need to declare the substrate itself, including source-set and search/outcome-space roles; use A.19.SOURCE-SET-SPACE-SUBSTRATE;
  • you only need CharacteristicSpace, its slots, or its typing hooks; use A.19;
  • you need to declare selector outcomes or shortlist identity; use G.5. Use G.10 for shipping a Part-G SoTA pack and E.24.PUB for making an exact view or episteme available to an audience;
  • you are setting live candidate-pool or retained-set policy; use C.19. Use C.24 for tool or service call planning after the action is fixed; other planning or enactment questions retain their own governing patterns;
  • you are defining a new generic view law, viewpoint bundle, or publication-view family rather than one domain-specific interpretive reading; use A.6.3, E.17.0, E.17, or E.17.1;
  • the line would change the EntityOfConcern rather than preserve it; use A.6.4 or the appropriate retargeting pattern.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.1 - What goes wrong if missed

If this pattern is missed, interpretive-view work usually fails in one of four ways:

  • the substrate is forced to carry every inspection question itself, so A.19.SOURCE-SET-SPACE-SUBSTRATE starts reading as if it also governed interpretive views, atlas readings, or palette interpretation;
  • the word view appears as one fresh local theory, detached from existing U.EpistemicViewing and U.MultiViewDescribing, so viewpoint, view, and publication face start collapsing again;
  • one atlas-form reading quietly becomes the default meaning of the whole family, so a fuller interpretive form starts redefining the base palette or base source set;
  • or qualifier refs such as OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote either disappear into vague prose or are promoted into mandatory core everywhere.

The reader then cannot tell whether a visible interpretation is one optional interpretive view, one fuller atlas reading, one publication face, or one new semantic head.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.2 - What this buys

An interpretation helps the reader inspect the declared substrate while keeping the following distinctions explicit:

  • the substrate remains the semantic center;
  • thinner interpretive views remain admissible when a full atlas form is unnecessary;
  • DeclaredSubstrateAtlasView remains available as one fuller reusable specialization, but not as the default head;
  • derived palette or tradition views keep their base palette and base source sets recoverable;
  • active set results, cited spaces, declared map refs, and qualifiers stay recoverable when the current reading uses them;
  • and publication, shipping, and pool-policy questions stay outside the view.

The practical payoff is simple: the reader can use one interpretive view to understand the declared line better without mistaking that interpretive view for the line’s ontology, output, or policy.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.a - TERM/LEX token-status guard (local-first)

Keep this token-status split explicit:

  • DeclaredSubstrateInterpretiveView is the ordinary/common interpretive-view head introduced here for domain-specific reuse over one already-declared substrate-bearing basis: either the substrate line itself or one declared source set or declared set result that keeps the substrate recoverable.
  • DeclaredSubstrateAtlasView is the fuller specialization of that same family. It is not the common head and it is not automatically required.
  • TypedSetViews is one local plural field over already-declared set-view heads or ids. It is not a new generic set-result ontology.
  • TraditionAtlasView is one local G.2 specialization of DeclaredSubstrateAtlasView, not the family head for all interpretive-view use.
  • OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote are guarded neighboring refs or interpretive qualifiers reused here. This pattern may foreground them, but it does not mint them.
  • inspection question is one local declaration field naming the interpretive load the current reading helps with. It is not a replacement for U.Viewpoint.
  • DerivedViewKind and BasePaletteRef stay local recoverability aids here; they do not silently turn the derived reading into the base ontology.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:0.b - First-minute operator cue and confusion guide

Use this pattern only after one substrate is already declared, either cited directly or kept recoverable through one declared source set or declared set result. The first-minute move here is not “write more about the same space”. It is “decide what inspection question the reader needs answered without changing the EntityOfConcern”.

Do this in the first minute:

  1. Cite the base substrate or the source-set entry point or set-result entry point that stays recoverable with it.
  2. State the inspection question in one sentence.
  3. Choose thin interpretation or atlas interpretation.
  4. Keep the active source set and any active set result recoverable.
  5. Add only the qualifiers that truly discipline the reading.

If you cannot name the base substrate or the recoverable source-set entry point or set-result entry point that carries it, or if the current prose would change the source-to-outcome relation or its posture, stop. You are either repairing the substrate, retargeting the object, or drifting into publication/policy.

If the question under repair sounds like…Use nowWhy
“How do I help the reader inspect the declared substrate?”A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEWThis pattern governs substrate-side only reading.
“What is the substrate itself?”A.19.SOURCE-SET-SPACE-SUBSTRATEThe base line has to exist first.
“Which palette-first or tradition-facing atlas reading should I use?”G.2 over this familyThat is one local specialization of atlas interpretation.
“What do we publish, ship, keep live, or plan next?”The pattern governing the remaining question; see §4.10.Distinguish selector outcomes, SoTA-pack shipping, view/episteme availability, live-pool policy and action planning.

Common confusion to kill early: one visible atlas or metric note does not make atlas form automatically necessary. Thin interpretation is already a complete admissible answer.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:1 - Problem frame

A declared source-set and search/outcome-space substrate may still need an interpretation that answers a reader’s inspection question.

Examples include:

  • one archive-centered reading that needs optional metric or transition qualifier to explain why certain regions stay promising;
  • one derived tradition or palette reading that must remain visibly derived from a base palette;
  • one atlas-form reading that collects several typed set views, active set results, spaces, declared map refs, metrics, or distortion notes so that cross-scale structure stays readable;
  • one interpretive rendering that helps the reader inspect the declared substrate without turning that rendering into the substrate’s default meaning.

A.6.3 governs EntityOfConcern-preserving epistemic viewing; E.17.0 separately qualifies a resulting episteme as a U.View through viewpoint conformance. G.2 uses TraditionAtlasView for an optional interpretation of a palette and declared set results. This pattern applies those distinctions to inspection of a declared substrate, with the amount of representation determined by the inspection question.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:2 - Problem

How should one declare an interpretive view so that:

  1. it is explicitly one domain-specific use-site of existing U.EpistemicViewing and U.MultiViewDescribing law, not one fresh autonomous theory of views;
  2. it keeps the already-declared substrate recoverable instead of replacing it;
  3. it allows both ordinary thinner interpretive views and one fuller atlas-form interpretive view;
  4. it keeps OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote optional and substrate-side only;
  5. it keeps derived palette or tradition views recoverable through DerivedViewKind and BasePaletteRef when those are active;
  6. it does not mint new set-result family heads, selector policy, publication policy, or shipping semantics;
  7. it lets G.2 keep TraditionAtlasView as one local specialization rather than as the generic head of the whole family;
  8. and it fails closed when the line would really be retargeting, new view-law work, substrate repair, publication, or policy?

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:3 - Forces

ForceTension
Existing view law vs local usefulnessThe interpretive view must be useful in local substrate work, but it cannot invent a second view ontology beside A.6.3 and E.17.0.
Substrate stability vs interpretive helpReaders may need help interpreting the declared substrate while retaining its source sets, spaces and relations.
Thin interpretation vs atlas-form readingSome cases need only one light interpretive view; others genuinely need one fuller atlas-form reading. The pattern must admit both without making the fuller form default.
Recoverability vs convenienceDerived tradition or palette views help reading, but they must not hide the base palette, base source set, or active declared spaces.
Qualifier richness vs semantic inflationDeclared map refs, metrics, transition qualifiers, and distortion notes are often useful, but they must stay optional interpretive qualifiers rather than new mandatory core.
Readability vs downstream boundary disciplineThe interpretation should answer the inspection question while leaving selector outcomes, publication, live-pool policy and action planning to their governing patterns (§4.10).

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4 - Solution

Declare interpretive views as substrate-side only readings over one already-declared substrate-bearing basis, keep them explicitly under existing view law, and reserve atlas form for the cases that truly need it.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.1 - Interpretive-view content and related work

Use this pattern to declare:

  • one DeclaredSubstrateInterpretiveView, the ordinary/common head of this interpretive-view family;
  • one substrate-side only reading over one already-declared substrate-bearing basis: either one explicit A.19.SOURCE-SET-SPACE-SUBSTRATE line or one already-declared source set or declared set result whose declared spaces, declared map refs, and qualifiers remain recoverable through such a line;
  • the inspection question that makes this view worth showing;
  • the recoverable source set or source sets that the interpretive view is reading;
  • any active set result, derived view, or base palette that the current reading keeps in play;
  • any cited spaces or declared map refs that the current reading depends on, provided those remain recoverable through declared refs or the cited substrate-bearing line;
  • and any optional qualifiers that the current view genuinely needs.

DeclaredSubstrateAtlasView is one fuller specialization inside that same family. It is not the common head.

Do not use this pattern to declare:

  • CharacteristicSpace itself;
  • the substrate role/relation stack from A.19.SOURCE-SET-SPACE-SUBSTRATE;
  • selector outcomes, shortlist heads, or shipping outputs;
  • live pool policy or enactment policy;
  • or a new generic law for views, viewpoints, or publication faces.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.2 - Minimal interpretive view declaration

A conforming interpretive view makes the following explicit:

  • which interpretive-family head is active: ordinary DeclaredSubstrateInterpretiveView or fuller DeclaredSubstrateAtlasView;
  • which already-declared substrate-bearing basis it is reading: either the explicit substrate line or the declared source-set entry point or set-result entry point that keeps that substrate recoverable;
  • which inspection question the view is answering;
  • which source set or source sets must stay recoverable while the view is active;
  • which active set result, if any, the current reading is using over that source set;
  • which cited spaces and declared map refs, if any, the current reading depends on, and how they remain recoverable;
  • which optional qualifiers are genuinely doing work in the current case;
  • and any use boundary needed to distinguish this interpretation from a substrate revision, publication or policy decision.

The minimum ordinary interpretive view declaration is therefore:

  1. one declared substrate-bearing basis from A.19.SOURCE-SET-SPACE-SUBSTRATE: either the explicit base substrate line or one declared source set or declared set result whose substrate remains recoverable with it;
  2. one explicit inspection question;
  3. one recoverable active source-set basis, plus any active set result drawn from it when the reading uses one;
  4. any cited spaces, maps and applicable uncertainty or distortion qualifications remain recoverable.

These are content requirements. Existing prose or a model can supply them; a separate record or repeated boundary statement is unnecessary when the content and use are already clear.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.3 - Interpretive-view declaration laws (IV-0..IV-8)

IV-0 - View-law docking is explicit. An ordinary interpretive reading keeps its declared substrate recoverable. An asserted epistemic viewing follows A.6.3; an asserted U.View additionally satisfies E.17.0 viewpoint conformance, as specified in §4.8.

IV-1 - The EntityOfConcern is preserved. The interpretation continues to concern the declared substrate. In an A.6.3 epistemic viewing, the source and receiving epistemes preserve the same EntityOfConcern while their ClaimGraphs or ReferenceSchemes may differ. Changing that EntityOfConcern requires a separate retargeting account.

IV-2 - The base substrate remains the semantic center. The interpretive view may foreground aspects of the base line, but it does not replace or repair the base substrate declaration. Substrate repair belongs back in A.19.SOURCE-SET-SPACE-SUBSTRATE.

IV-3 - Source, set-result, and palette recoverability are mandatory. The current source set, any active set result drawn from it, and any active derived view or base palette must remain recoverable while the interpretive view is active.

IV-4 - Distinguish substrate and view qualifications. The view may foreground the substrate’s OutcomeMapRef, SpaceMetricRef, TransitionRelationRef or BridgeDistortionNote. It may also introduce a qualification of its own representation. State which relation a qualification concerns; changing the underlying source-to-outcome relation requires revising its substrate declaration.

IV-5 - Thin interpretation and atlas interpretation are different profiles. Ordinary DeclaredSubstrateInterpretiveView is a complete admissible profile, not a placeholder. DeclaredSubstrateAtlasView is used only when the fuller composite inspection question is real.

IV-6 - Atlas form keeps its constituent views and connections recoverable. If atlas form is active, the view must keep the base substrate, the active source or set result, the relevant TypedSetViews, any cited spaces, any cited declared map refs, and any qualifiers explicit enough for the reader to recover how those parts answer the inspection question.

IV-7 - Local specialization stays local. If TraditionAtlasView is used, it remains one G.2 specialization of DeclaredSubstrateAtlasView; it does not become the common head of the family.

IV-8 - Admission is fail-closed. If the current line would change the EntityOfConcern, add new generic view law, repair the substrate, decide publication, or decide policy, it is not a conforming interpretive view here. Apply the pattern that governs that question instead of stretching the family.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.4 - Profiles

Use one of these profiles explicitly:

  • Thin-interpretation profile. Use ordinary DeclaredSubstrateInterpretiveView when a direct explanation answers the inspection question. The number of cited references alone does not require atlas form.
  • Atlas-interpretation profile. Use DeclaredSubstrateAtlasView when answering the question requires showing how several declared views, spaces, maps or qualifications relate within the same substrate.

If neither profile can be chosen honestly, the line is not ready as interpretive-view text.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.5 - Operational declaration sequence (fail-closed)

When declaring one interpretive view, proceed in this order:

  1. Entry test. Confirm that one already-declared substrate exists and that the current inspection question can cite it either directly or through one declared source-set entry point or set-result entry point that keeps it recoverable, rather than drifting into substrate repair, publication, or policy.
  2. Name the active interpretive head. Use ordinary DeclaredSubstrateInterpretiveView unless the current reading genuinely needs the fuller atlas form.
  3. Cite the base line. Name the already-declared substrate the view is reading, or cite the source-set entry point or set-result entry point together with the recoverable substrate it depends on.
  4. State the inspection question directly. Say what the view helps the reader see that the substrate alone leaves hard to inspect.
  5. Keep the base source/result recoverable. Name the active source set, and if the view is over one declared front, archive, shortlist, palette, or other set result drawn from that source, keep that active set result recoverable too.
  6. Recover derived-view and palette structure when it matters. If the view depends on one derived tradition or palette reading, state DerivedViewKind and BasePaletteRef.
  7. Add the actual qualifiers. Add TypedSetViews, cited spaces, declared map refs, metrics, transition qualifiers, or distortion notes only when the current reading truly depends on them.
  8. Run the preservation check. If the interpretive prose would materially change the base source-to-outcome relation or the base distortion/uncertainty/error posture, stop and reopen the substrate declaration.
  9. Run the boundary check. If the prose starts changing the EntityOfConcern, minting new generic view law, publishing selected sets, shipping outputs, or deciding policy, apply the pattern that governs that question.

Incomplete declaration. Missing base recovery or an unresolved change to the underlying relation prevents the dependent interpretive-view claim. Preserve independently established content and resolve the missing basis. Split out any separate publication or policy decision and apply its governing pattern.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.6 - Thin interpretation remains a complete admissible form

Many cases need one interpretive view but not one atlas-form interpretation package.

Use thin interpretation when a direct explanation answers the inspection question, including when it cites a needed metric, map, transition or loss qualification.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.7 - Atlas form combines views and their connections

Use DeclaredSubstrateAtlasView when the inspection question requires showing how several declared views, spaces, maps or qualifications relate within the same substrate. The minimal admissible atlas-form interpretation declaration therefore contains:

  • the cited base substrate or source-set entry point or set-result entry point;
  • the active source set and any active set result drawn from it;
  • TypedSetViews when several declared set views are being held together;
  • any cited SearchSpaceRef, OutcomeSpaceRef, or other declared space refs that the atlas reading depends on;
  • any cited OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, or BridgeDistortionNote that materially disciplines the reading;
  • DerivedViewKind and BasePaletteRef whenever the atlas reading is over one derived palette or tradition view;
  • the connections among these parts needed to answer the inspection question.

If the available basis cannot support the composite interpretation, retain what is established and state the missing basis. Use thin interpretation only if it still answers the inspection question; otherwise leave that question unresolved and use the pattern governing the missing basis if further work is needed.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.8 - No autonomous local view law is introduced here

Start with the declared substrate and the inspection question. An ordinary interpretation can stop with a recoverable explanation. When the use claims an A.6.3 epistemic viewing, identify the source episteme X whose ClaimGraph describes that substrate and the receiving episteme Y produced by the stated projection or re-expression. Both retain the same EntityOfConcern; state the transformed ClaimGraph and any changed ReferenceScheme explicitly.

Qualify Y as an E.17.0 U.View only when it independently conforms to the named U.Viewpoint for that concern. A return to A.6.3 alone does not establish viewpoint conformance. Keep the viewpoint, the view episteme and any E.17 publication face separate. A different EntityOfConcern requires the applicable retargeting account; changing or repairing the substrate returns to A.19.SOURCE-SET-SPACE-SUBSTRATE.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.9 - Qualifier refs stay substrate-side

OutcomeMapRef, SpaceMetricRef, TransitionRelationRef, and BridgeDistortionNote are admitted here only as interpretive qualifiers.

Qualifiers of the source-to-outcome relation are declared with the substrate and reused here. Qualifiers of the view itself belong to its representation account; for example, rounding displayed Coordinates can lose distinctions while the underlying Coordinates and map remain unchanged.

Use them when the current interpretive view genuinely needs them:

  • OutcomeMapRef when the current reading must show how one declared source or set result bears on one outcome-side declared space/ref;
  • SpaceMetricRef when neighborhood, spread, reachability, or crowding claims are load-bearing in the current reading;
  • TransitionRelationRef when the current reading depends on explicit transition or cross-scale state-change qualifier;
  • BridgeDistortionNote when the reader must keep one declared loss or distortion visible near the current reading.

If a new loss, uncertainty or other qualification changes the underlying source-to-outcome relation, revise the substrate declaration and recheck dependent uses. Reuse unaffected content. A view-only qualification does not by itself change that relation.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.10 - Publication, set-result, and pool-policy boundaries

This pattern does not publish selected sets, declare shortlist heads, or decide which candidate lines stay live.

Keep the split explicit:

  • A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW helps the reader inspect one already-declared substrate;
  • G.5 declares selector outcomes and their source/publication metadata;
  • G.10 ships a Part-G SoTA pack with its publication faces and pins;
  • C.19 governs live candidate-pool and frontier policy;
  • C.24 plans tool or service calls after the action is fixed;
  • E.24.PUB governs making an exact view or episteme available to an audience.

Other planning and enactment questions belong to the pattern governing the action. If the prose starts deciding who survives, what is published, or what is shipped, it has already left this pattern.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.11 - G.2 keeps the tradition-facing atlas specialization

When the current interpretive view is tradition-facing and palette-first recoverability matters, use the local specialization governed by G.2.

Read the relation this way:

  • A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW states the generic interpretive-view family and the generic fuller atlas form DeclaredSubstrateAtlasView;
  • G.2 keeps the palette-first, tradition-facing specialization TraditionAtlasView;
  • TraditionAtlasView is therefore one local specialization of the fuller atlas form, not the common head of the whole interpretive family.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:4.13 - Using the interpretive view with neighboring patterns

Once the interpretation is sufficient, stop. Select a neighboring pattern only for a remaining question:

  • Use G.2 when the interpretive view becomes palette-first, tradition-facing atlas work. That is one local specialization of atlas interpretation, not the common family head.
  • Use F.18 when the question under repair is label choice around interpretive-view, atlas, palette, or declared-map-ref language. Naming notes may explain the labels, but they do not change the base substrate or the inspection question.
  • Use A.6.P when one passage collapses view, surface, space, map, or palette into one umbrella word. Recover the intended predicate and its participants, then continue.
  • Use A.0 when cold-reader glossing is what the current line lacks. Glosses help recognition; they do not replace the base interpretive view declaration.
  • Use the corresponding pattern in §4.10 when the remaining question concerns selector outcomes, shipping, publication, live-pool policy or action planning.

If a neighboring passage would change the EntityOfConcern or the base substrate posture, this pattern is no longer the governing pattern for that sentence. Reopen the base line or apply the pattern that governs the new question.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5 - Archetypal Grounding

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.1 - System

Tell. One QD archive has a declared substrate. A reader asks which candidates are neighbors of candidate p under its declared metric.

Show. In this constructed case, Archive-12 uses BehaviorCharacteristicSpace@ed=12 and ArchiveNeighborhoodMetric@ed=4. The declared neighborhood criterion is distance at most 0.3. Distances from p to q and r are 0.2 and 0.8 respectively. An ordinary DeclaredSubstrateInterpretiveView groups q with p and leaves r outside that neighborhood, showing the criterion alongside the grouping. The source Coordinates and metric remain recoverable.

Cash-out. The reader can recover why q is a neighbor and r is not. This grouping answers the inspection question; it does not itself select which candidates to retain. No fuller atlas is needed.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.2 - Episteme

Tell. One synthesis line already keeps a base SoTA palette and one derived tradition-facing reading. The reader now needs one fuller atlas-form interpretive view that keeps the base palette recoverable while showing how several tradition-facing views and cross-scale notes sit together.

Show. The active interpretive head is DeclaredSubstrateAtlasView. It reads one declared palette-facing substrate line whose source-set family remains TraditionPalette, whose active derived view remains TraditionFront, and whose base palette remains recoverable through SoTAPaletteDescriptionId. The cited spaces stay explicit as TraditionComparisonSpace@ed=3 and AdoptionOutcomeSpace@ed=2. The atlas reading keeps together the declared set views TraditionFront and TraditionArchive, the OutcomeMapRef value PaletteToAdoptionOutcomeMap@ed=1, the distortion note CrossTraditionComparisonLossNote@ed=1, and the local G.2 specialization TraditionAtlasView.

Cash-out. The reader follows a tradition profile from the palette into its front or archive view, then follows PaletteToAdoptionOutcomeMap@ed=1 to its conditional adoption outcome. The comparison-loss note stays beside comparisons that depend on it. These connections explain why the views are shown together; a front alone would hide the archive and its relation to the same palette. The atlas changes inspection, not membership of the base palette.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.3 - Boundary anti-case

Tell. One note starts from “atlas view” language, then quietly changes the base outcome posture and argues that only one shortlisted tradition should remain live.

Show. The changed-relation and retention claims need their own governing patterns.

Cash-out. Reopen the substrate if the base relation or posture changed. Use C.19 for the claim about which candidate traditions remain live; G.5 governs any declaration of a selector outcome.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:5.4 - Use-situation spread

Use the interpretive-view family this way across different working situations:

Working situationChooseWhat must stay explicitCommon miss avoided
Archive-side QD line that only needs one metric cue so the reader can see local neighborhoodsThin interpretationOne base substrate, one inspection question, one active source set, and the specific metric qualifier doing work.Forcing atlas form into a case that only needs one simple reading aid.
Palette-first synthesis line that really needs several declared views, spaces, declared map refs, and loss notes held togetherAtlas interpretation, with G.2 when the case is tradition-facingThe base palette, derived view, cited spaces, qualifying map-ref/distortion refs, and the connections needed to answer the inspection question.Letting the most salient visible atlas overlay replace the palette-first base line.
Derived tradition/front note that only needs to remind the reader how to read one already-declared substrateThin interpretationThe inspection question, derived-view recoverability, and the base palette when it would otherwise disappear.Treating every derived tradition reading as if it were already full atlas work.
Passage that starts changing the outcome posture, survivor set, or publication resultDo not use this patternThe boundary out to substrate repair, publication, or policy stays explicit.Smuggling retargeting or policy decisions into interpretive-view prose.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:6 - Bias-Annotation

  • Gov bias. The pattern prefers explicit reuse of existing view law over local convenience talk about one view.
  • Arch bias. The pattern keeps substrate, interpretive reading, publication, and policy separated even when one merged story would sound simpler.
  • Prag bias. The pattern prefers thinner interpretive views by default and treats atlas form as one fuller option rather than a universal baseline.
  • Did bias. The pattern insists on recoverability of the base palette or base source set because readers otherwise over-trust the most salient visible interpretive form.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:7 - Conformance Checklist

Apply these checks to the interpretation and claims actually made.

IDCheck questionFail whenRepair or governing pattern
CC-A19IV-1Is one already-declared base substrate or source-set entry point or set-result entry point named explicitly?The interpretive view floats free of the line it is supposed to help read.Cite the base substrate or the recoverable source-set entry point or set-result entry point.
CC-A19IV-2When formal viewing is claimed, are the A.6.3 source and receiving epistemes recoverable, and is E.17.0 viewpoint conformance established separately for a U.View claim?A pattern citation is treated as sufficient to establish either relation.Recover the exact epistemes and viewing transformation; test the named viewpoint only when U.View qualification is needed.
CC-A19IV-3Does the line preserve the same EntityOfConcern and keep the base substrate as semantic center?The interpretive prose retargets the EntityOfConcern or repairs the substrate in place.Reopen under A.19.SOURCE-SET-SPACE-SUBSTRATE, A.6.4, or the appropriate neighboring pattern.
CC-A19IV-4Are the current source set, any active set result, and any active derived view or base palette recoverable?The interpretive reading hides the base palette, base source/result, or active derived set result behind one fuller visible overlay.Restore the missing recoverability fields.
CC-A19IV-5Is the active profile chosen honestly: thin interpretation or atlas interpretation?Atlas language is used by reflex, or the line needs atlas interpretation but never says so.State the profile and the inspection question it answers; explain the composite need when choosing atlas form.
CC-A19IV-6If atlas form is active, is the composite atlas-form interpretation declaration complete?A source set/result, declared view, space, map reference, qualification, or connection needed to answer the composite inspection question remains hidden.Supply the missing content needed by the inspection question; use thin interpretation only if it gives an adequate answer.
CC-A19IV-7Is each qualification attached to the relation it qualifies?A view qualification silently changes the source-to-outcome relation, or a material substrate qualification disappears.Preserve substrate qualifications; state any view-only loss separately. Revise the substrate if its underlying relation changes.
CC-A19IV-8If TraditionAtlasView is used, is it kept as one G.2 specialization rather than the common family head?The local specialization is treated as if every interpretive case were already palette-first atlas work.Restore the split between DeclaredSubstrateAtlasView and TraditionAtlasView.
CC-A19IV-9Does the line stay out of publication and policy work?The prose starts deciding who survives, what is published, or what is shipped.Separate the interpretation from the remaining decision and apply the corresponding pattern in §4.10.
CC-A19IV-10Could a cold reader choose thin interpretation versus atlas interpretation and fill one interpretive view declaration without hidden invention?The reader still needs surrounding memo knowledge to know which head to use, what fields matter, or why atlas is or is not needed.Use the content requirements in §4.2 and sequence in §4.5; show the composite inspection need if atlas form is necessary.
CC-A19IV-11Is the inspection question explicit enough to tell the reader what this view helps inspect now?The view mostly restates the base theory, but the practical inspection load stays unnamed.State the inspection question directly and keep the base line recoverable beside it.
CC-A19IV-12When specialization, naming repair, publication, or policy becomes the next question, is the governing neighbor explicit?The prose answers a specialization, naming, publication or policy question as if it were part of the interpretation.Split the line and cite the governing neighbor instead of stretching interpretive-view prose across that boundary.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
Writing as if A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW were a fresh autonomous theory of viewsIt duplicates existing A.6.3 and E.17.0 law and collapses U.Viewpoint, U.View, and publication-face discipline.State the docking to existing view law explicitly.
Letting atlas language become the default meaning of every interpretive caseThe fullest visible interpretive form silently becomes the family head.Keep ordinary thinner interpretive views admissible and say when atlas form is actually needed.
Treating qualifier refs as the view’s semantic centerMetrics, transitions, or distortion notes then replace the base substrate.Keep the base substrate and inspection question explicit, and keep qualifier refs optional.
Letting a derived tradition view replace its base paletteThe reader loses palette-first recoverability and mistakes one local interpretation for the default ontology.Keep DerivedViewKind and BasePaletteRef visible together.
Turning the interpretive view into publication or pool policyThe reader can no longer tell whether the text is helping interpret the line or deciding what survives and gets published.Separate the interpretation from selector, publication and live-pool decisions; apply their governing patterns in §4.10.
Forcing atlas form into every first readingSimple cases become over-typed and harder to use.Start with the thinner interpretive-view form and widen only when the current need genuinely requires it.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:9 - Consequences

Benefits

  • Readers can inspect the source sets, spaces and relations while keeping their declarations recoverable.
  • FPF keeps one common interpretive-view family without forcing G.2 or another local specialization to carry the whole interpretive requirement.
  • Atlas-form interpretation remains available where it helps, but thinner interpretive views stay lawful.

Trade-offs

  • The declaration must keep more boundaries explicit: view law, substrate, publication, and policy no longer collapse into one comfortable narrative.
  • Some cases that once looked like “just a view” must now say whether they are thin interpretation, atlas interpretation, publication, or policy.
  • The pattern requires the base palette or source set to stay recoverable, which can make local prose slightly less terse.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:10 - Rationale

An inspection question determines which aspects and connections of a declared substrate need to be shown. Keeping the source sets, relevant results and material qualifications recoverable lets the reader inspect those connections without changing the substrate; thin or atlas form supplies the amount of explanation the question needs.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:11 - SoTA-Echoing

Practice linePrimary accepted basisPractice demand disciplined herePractical safeguard boughtAdoption stance
Interpretive readings should remain entityOfConcern-preserving views rather than becoming fresh semantic centers.A.6.3 preserves EntityOfConcern between source and receiving epistemes; E.17.0 adds independent viewpoint conformance for U.View.IV-0, IV-1, IV-8, CC-A19IV-2, CC-A19IV-3.Keeps interpretive prose from quietly turning into retargeting or new view-law invention.Adopt. Reuse the existing view law directly rather than minting one local alternative.
Palette-first SoTA synthesis already treats atlas interpretation as optional neighboring interpretation rather than the default meaning of Tradition or SoTAPaletteDescription.G.2:4.7 already keeps TraditionAtlasView as optional neighboring interpretation and preserves palette-first recoverability.IV-5, IV-6, IV-7, CC-A19IV-5, CC-A19IV-8, worked slice 5.2.Keeps atlas form available without letting the most salient visible interpretation replace the base palette or family head.Adopt/Adapt. Adopt palette-first recoverability and adapt it into one reusable common interpretive family.
FPF keeps richer map, metric and transition qualifications conditional on the inspection question.The bounded QD comparisons in A.19.SOURCE-SET-SPACE-SUBSTRATE:11 motivate this design choice; they do not establish it as a universal rule of contemporary practice.IV-4, IV-5, IV-6, CC-A19IV-5, CC-A19IV-6, CC-A19IV-7.Keeps thinner interpretation admissible, keeps atlas interpretation reusable but non-default, and prevents rich formal qualifier from being smuggled in by default.Adapt. Keep richer formal qualifier available without pretending it is the baseline for every interpretive reading.

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:12 - Relations

A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW:End


A.19.CN - CN-frame: Specify and Maintain Comparability and Normalization

Status: Stable

Scope. Use a CN-frame to state which values may be compared for the intended use. The specification can apply to one bearer or to members of a named bearer kind; each reading retains the subject or participants it concerns. Declare the characteristic space, chart and comparison basis in CN-Spec, adding normalization when needed. Maintain editions retained for later reuse or shared use, and apply the conditions for each proposed reuse.

Use this when readings need a recoverable comparison basis or a changed basis may affect their reuse. Keep the bearer, Characteristic and Scale meanings, observation or evaluation basis and intended comparison together. An already sufficient account can serve as CN-Spec; its notation is unrestricted. Apply the corresponding A.19 mechanism pattern when normalization, indicatorization, scoring, aggregation, comparison or selection is needed. C.16 governs measurement backing and G.0 governs the applicable admission conditions.

Reader guide.

  • “What does NormalizationMethodId/…InstanceId/≡_UNM/NormalizationFix mean?” → A.19.UNM.
  • “What is an Indicator / IndicatorChoicePolicy and why NCV ≠ Indicator?” → A.19.UINDM.
  • “Why can we trust a normalization / where does calibration or evidence live?” → C.16 (MM‑CHR).
  • “What is admissible to compare or aggregate, and what is MinimalEvidence?” -> G.0 (CG-Spec).

A.19.CN:1 - Context

A.19 established a substrate‑neutral picture:

  • a CN‑frame = a selected CharacteristicSpace (CS) + chart (coordinate patch and value basis, with Units where applicable) + a referenced Normalization mechanism (UNM) when the use needs normalization, for a declared bearer or bearer kind, comparison basis, intended use, and any scope/window that qualifies it. A.19.UNM defines directed normalization, its preservation/loss basis and any separately justified ≡_UNM class use;
  • operators (subspace, product, pullback/pushforward) and comparability (coordinatewise vs normalization‑based (normalize‑then‑compare));
  • RSG touch-points: state predicates use observable characteristics; an evaluation establishes whether their conditions hold for the named bearer and window;
  • entity/relational mixtures across CN‑frames, represented by the schemas in §8.4, with each required correspondence grounded under its own rule.

Frame, specification and explanation. A CN‑frame is the selected basis for interpreting and comparing the readings. Its CN‑Spec fixes the bearer or bearer kind, characteristic and scale editions, chart, comparison basis, comparability rule, intended use and qualifying scope/window, with normalization and aggregation choices when used. A CN‑Description explains the declared comparison basis and the grounds and limits of its use. Worked examples and anti-patterns can illustrate that account. Mechanism-level terms such as NormalizationMethod, NormalizationMethodInstance, NCV, ≡_UNM, and IndicatorChoicePolicy retain the definitions supplied by the corresponding A.19.<MechId> patterns.

Normalization names. Use A.19.UNM’s method and instance identifiers to identify the selected normalization. Ordinary mathematical “mapping” describes its function; it does not assert a specialized FPF Map kind or an F.9 Bridge. Resolve a legacy identifier through F.18 alias docking when needed.

The practitioner can compare values within this declared basis and identify which conclusions need reconsideration when it changes.

A.19.CN:2 - Problem

When the comparison basis is missing or changes silently, these failures can occur:

  1. Chartless numbers. Measures move between teams without units, reference states, or declared normalization → illusory comparability.
  2. Hidden normalization changes. Re-parameterisation, such as normalising by batch size, can change the quantity being compared while a trend line still appears continuous.
  3. CN-frame sprawl. Unrelated dashboard definitions can leave receivers unable to establish a shared comparison basis.
  4. Incompatible roll-ups. Cross-team roll-ups average incongruent CN-frames without a justified common comparison or aggregation model. Use B.3 when the result serves a named assurance claim.

A.19.CN:3 - Forces

ForceTension we must balance
Universality vs nuanceOne Standard for robotics, safety, and finance, while each named source scheme retains its own meanings.
Speed vs auditA short sufficient comparison basis; further evidence when assurance or independent certification is required.
Local truth vs federationKeep meanings tied to their schemes and claims; still allow explicit relations and bounded receiving uses.
Minimalism vs safetyFew mandatory slots; enough structure to forbid silent normalization drift.

A.19.CN:4 - Solution — Specify the comparison basis and maintain it when reused

A.19.CN:4.1 - The CN‑Spec (comparability and normalization specification)

A CN‑frame is described by a notation-free specification. The specification names the bearer and the boundary within which its readings may be compared:

CN‑Spec {
  name              : CN‑frameName
  edition           : <edition>
  bearer_ref        : <evaluated bearer or bearer kind>
  characteristic_space_ref : <CharacteristicSpaceRef>
  characteristicSpaceDescriptionRef? : <U.EpistemeRef to the exact defining/description episteme>
  scope_ref?        : <ClaimScopeRef>
  window?           : <qualification interval>
  reference_or_comparison_basis : <corpus, baseline, reference state, or declared comparison set>
  cs_basis          : [{
    slot_id         : <tech-token>,
    characteristic  : <Characteristic defined under A.17>,
    scale           : { type: nominal|ordinal|interval|ratio, unit?: <measurement unit under A.18/C.16>, bounds?: <…> },
    polarity?       : <preference rule when ranking desirability; e.g. up, down or target-range>,
    // if needed: missingness?, admissible_domain? (MM‑CHR-consistent metadata)
  }]
  chart             : { reference_state, coordinate_patch, measurement_protocol_ref?, value_ascription_basis? }
  normalization?    : {
    UNM_id?,
    methods: [NormalizationMethodId],
    instances?: [NormalizationMethodInstanceId],
    method_descriptions: [NormalizationMethodDescriptionRef],
    admissible_reparameterizations,
    invariants,
    fix?: <NormalizationFixSpec>
  }
  comparability     : { mode ∈ {coordinatewise, normalization-based}, minimal_evidence }
  intended_use      : <claim, comparison, admission, or aggregation use>
  indicator_policy? : { IndicatorChoicePolicyRef, scope, edition }
  acceptance        : { checklist_for_admission, window?, evidence_anchors }
  aggregation?      : { Γ_fold, selected WLNK/COMM/LOC/MONO claims, time_policy }
  alignment?        : { semantic_uses?: <Bridges and separate bounded-use claims under §4.3>, plane_relation_refs?: <applicable plane relations> }
  maintenance?      : { responsibility, DRR_links?, applicable_deprecation_arrangement }
}

Reading: the CN-frame is the selected characteristic space and chart for the declared bearer or bearer kind and intended use. When bearer_ref identifies a kind to delimit the candidate bearers, the specification applies to readings about members of that kind. Each reading retains the individual subject or participant tuple required by its Characteristic under A.19. Apply the admission and comparison conditions to the actual operand pair.

The normalization block is needed for normalization-based comparison; coordinatewise comparison can omit it. Add maintenance arrangements when the specification is retained for later reuse or maintained as a shared edition. CN‑Spec fixes the editions, comparison basis, qualifying scope/window and admission evidence needed by that use, with normalization references and aggregation choices when used. A.19.UNM defines normalization semantics, A.19.UINDM defines indicatorization, C.16 supplies measurement and evidence backing, and G.0 supplies the applicable admission conditions. A Γ_fold cites its law and applicability basis. Its property codes express only the claims needed by this use; A.9 supplies an unresolved law choice or property check, while ULSAM retains the CHR fold and admissibility rules.

The space reference selects the space itself. Add characteristicSpaceDescriptionRef when the selected use needs one definition or description edition; UNM and UINDM require this pin for their applications. Resolve the pair under A.19:5.1.1.1 and check that the description supplies the basis of that same space. An unchanged space may have a different description episteme, and a changed basis may require a different space even when the description retains its familiar title.

Mechanism references. UNM_id identifies the admitted normalization mechanism. NormalizationMethodId and NormalizationMethodInstanceId retain the meanings declared by A.19.UNM, and evidence for a relied-on instance remains with C.16. CN‑Spec neither redefines those terms nor implies transport or a cross-local relation.

L‑CN‑Spec‑NORM‑IDs (by reference). Cite the normalization identifiers defined by A.19.UNM.

A.19.CN:4.2 - CN-frame registry and conditional independent certification

First identify whether the receiving claim or applicable control requires independent certification of this CN-Spec edition or admission basis. When it does, the holder certifying it must not have authored or materially selected that basis. Include relevant earlier authoring whose content the certified basis retains. Renaming an assignment or waiting until an authoring assignment ends does not satisfy this condition.

Recover the holders, their relevant Work, the edition or basis and the applicable history under A.2.1 and A.2.7. Distinct assignments do not establish distinct holders. Missing history leaves independence unresolved. Different holders can satisfy this non-self-certification condition while their assignment windows overlap; any stronger organizational-independence or commissioning control still applies. The certifier’s authority and adequacy of examination require their own grounds.

When no independent-certification claim or control applies, an adequately grounded one-person comparison can remain explicitly uncertified. Its measurement, comparison and reliance requirements still apply.

One named registry edition may publish the CN-frame’s names, editions, characteristic-space and bearer references, the maintenance assignment, and the deprecation relation. When certification affects the receiving use, it also makes the applicable control, relied-on edition, certification result and supporting references recoverable. Distinguish:

  • an adequate comparison for the named use with independent certification not required and no such claim made;
  • a certification condition satisfied for the edition, with the participation, authority and examination grounds;
  • a required condition that is unmet or unresolved, with its consequence for the dependent use under the applicable control.

These are different conclusions, not interchangeable registry labels. The registry helps discovery and currentness; it supplies no missing comparison, independence or certification evidence. A changed comparison basis reopens only the certification and receiving conclusions that rely on that change. A display-only registry change does not reopen them.

A.19.CN:4.3 - Bridges between local meanings

When a comparison or reuse needs a semantic correspondence or difference between two F.17 local senses, test the F.9 predicate. Cite a Bridge only when it obtains; otherwise retain the F.9 exit and its reason. A use that needs an absent or unresolved correspondence remains unsupported. A coordinate mapping or plane relation keeps its own grounds. A compact account may show an obtaining Bridge and its separate bounded-use claim together:

Bridge: <obtaining occurrence between exact source and receiving F.17 cells>
  predicate_profile: <relation kind, endpoint readings and obtaining condition>
BoundedUseClaim:
  applicable_use: <the receiving comparison, admission or aggregation>
  direction: <source-to-receiving use>
  correspondence_rule: <how the local claims are used together>
  tolerated_loss: <declared limit for this use>
  polarity: affirmative | negative
  grounds: <kept/lost distinctions and other support or counterevidence>
  coordinate_transform?: <separately justified pullback, pushforward, re-scaling, re-binning, etc.>
  plane_relation_ref?: <only when a separately defined plane relation obtains>
  reliance_ref?: <required reliance judgement for this use>
  assurance_ref?: <result for a current named assurance claim>
  extra_guards?: {additional evidence, required review, or an authorized exception within its applicable scope}

The Bridge is only the sense relation. The separate C.2.1 claim states whether it suits the named use, direction, rule and tolerated loss. For reliance on an affirmative claim, obtain or reuse the A.10 disposition required by F.9:4.2; a negative or unresolved claim supplies no positive use basis. Add a B.3 result only for a current named assurance claim. Matching names establish no Bridge, and a reverse use needs its own justified direction. B.3 determines any assurance consequence under the selected argument or model; CN-Spec may state additional receiving-use conditions.

A.19.CN:5 - Conformance Checklist (normative)

These checks establish the declared comparison basis. Assurance and cross-team reuse still require the evidence and relation conditions of their receiving claims.

CC‑A19.D1‑1 (Local identity and scope). Every CN-frame MUST identify its name and edition, bearer or bearer kind, characteristic space, reference or comparison basis, intended use, and any scope/window that qualifies the readings. The same label under another scheme or edition is not evidence of the same frame.

CC‑A19.D1‑2 (Scales, units and preference). Each characteristic slot in cs_basis MUST declare its Scale and value meanings, and its Unit when that Scale has one. A comparison that ranks values by desirability MUST state its preference rule. Descriptive comparisons need no preference rule.

CC‑A19.D1‑3 (Chart). chart MUST name its reference state and coordinate patch. For measured values, cite the applicable measurement method and protocol under C.16; for evaluated or otherwise ascribed values, cite the rule and basis that establish those values.

CC‑A19.D1‑4 (Normalization references, not redefinition). When normalization is used, normalization MUST identify the admitted mechanism and provide the normalization references required by A.19.UNM (methods / invariants / fix, and instances when used) so that any normalization‑based comparison is auditable. This pattern does not define what a “NormalizationMethod” is — it requires that CN‑Spec can point to the governing pattern that does.

CC‑A19.D1‑5 (Comparability mode). comparability.mode MUST be either coordinatewise (same chart, Scales and applicable Units) or normalization‑based (“normalize‑then‑compare” via the declared UNM). Mixed/implicit modes are prohibited. A.19.UNM governs the directed result and any optional classes. The receiving comparison must retain its required distinctions; equality of normalized outputs alone establishes no operational congruence. CN-Spec pins the chosen result branch and its basis.

CC‑A19.D1‑6 (Admission checklist). acceptance.checklist_for_admission MUST state testable conditions and any interval needed for the intended use. Each admitted datum SHALL have the measurement, evaluation or other value-ascription basis required by that use. Cite a StateAssertion when a state claim is being made; a datum is not automatically such a claim.

CC‑A19.D1‑7 (Aggregation discipline). When aggregation is used, aggregation.Γ_fold MUST identify the declared scale-lawful fold, its applicable algebraic properties and any required time policy. G.0 and A.19.ULSAM govern admissibility and the fold; B.3 applies when the fold serves an assurance claim. Keep the values separate when no fold is needed.

CC‑A19.D1‑8 (Relation and use discipline). When reuse depends on a semantic correspondence or difference between two F.17 local senses, test the F.9 predicate and cite a Bridge only when it obtains. To use an obtaining Bridge, the receiving C.2.1 claim MUST separately state the use, direction, correspondence rule, tolerated loss and polarity. Reliance on an affirmative claim requires the A.10 disposition under F.9:4.2; a named assurance use also requires its B.3 result. Missing or unresolved required correspondence blocks the dependent use. A coordinate mapping and any applicable plane relation retain their separate grounds.

CC‑A19.D1‑9 (Conditional non-self-certification). When the receiving claim or control requires independent certification, the certifying holder MUST NOT have authored or materially selected the CN-Spec edition or admission basis being certified, including relevant retained earlier content. Apply §4.2 to holder/Work/history, required authority and examination. Unknown history is unresolved. An adequate use with no such requirement may remain explicitly uncertified.

CC‑A19.D1‑10 (Maintenance, deprecation, and DRR). A CN-Spec maintained for later reuse or as a shared edition MUST make its maintenance responsibility, applicable deprecation arrangement and consequential decisions recoverable. Use E.9 for decisions that need a DRR. A one-use comparison need not invent a maintenance assignment or retirement plan.

CC‑A19.D1‑11 (Evidence for the receiving use). An admission later used for comparison or aggregation SHALL retain the independently established measurement, evaluation or other value-ascription results and support relations that the receiving use needs, including applicable currentness and validity windows. Use A.10 when their provenance or bounded reliance must remain replayable. Add B.3 assurance lanes and an assurance result only when the receiving use makes that assurance claim. Missing required inputs have the disposition declared by the comparison or aggregation rule.

CC‑A19.D1‑12 (Notation independence). CN‑Spec content MUST NOT depend on a tool or file format; semantics precede notation (E.5.2 Notational Independence).

CC‑A19.D1‑13 (Recoverable names). Characteristic names and role labels MUST preserve the distinctions required by the comparison. Apply Part E lexical guidance and F.18 where a durable name or alias is needed.

A.19.CN:6 - Consequences (informative)

BenefitWhy it matters
Auditable comparabilityChart and any required normalization expose the basis on which equal numbers may be compared; changes to that basis remain visible.
Safe roll‑upsΓ-folds preserve only the properties justified by the named quantity, operation and dependency model.
Pluralism without incoherenceObtaining Bridges and separately grounded use claims support the stated cross-local reuse. Retain the observed losses and required reliance; use CL only as optional evidence shorthand.
RSG‑readyAdmission checklists let RSG states reference CN‑frame‑backed facts (e.g., Ready requires characteristics within bounds).

A.19.CN:7 - Rationale (informative)

A comparison depends on the meaning and basis of its values. Keeping that basis with the CN-Spec makes a changed chart, normalization or intended use visible to the receiver. A claimed aggregation also needs its justified model; a required assurance claim retains its applicable loss policy under B.3.

A.19.CN:8 - Archetypal Grounding

The cases use plain-language normalization descriptions to illustrate the choices. Applying a selected normalization requires its A.19.UNM method and instance references and the backing required by C.16.

A.19.CN:8.1 - Industrial line — Weld‑quality CN‑frame (AssemblyLine_2026)

  • cs_basis: BeadWidth[mm] (target 6.0±0.2), Porosity[ppm] (↓), SeamRate[1/min] (↑ until limit)
  • chart: reference jig, fixture ID, torch type; MethodDescription#Weld_MIG_v3
  • normalization: affine rescale on gray‑level calibration → invariant = physical porosity
  • comparability: normalization‑based (UNM) (calibration tables applied)
  • aggregation: a minimum bound only for a declared bottleneck quality model; commutative count addition only for disjoint contributions; time = per-shift histograms
  • RSG hook: WelderRole.Ready requires Porosity ≤ 500 ppm & BeadWidth within ±0.2 mm admitted by this CN‑frame.

A.19.CN:8.2 - Software/SRE line — Latency CN‑frame (SRE_Prod_Cluster_EU_2026)

  • cs_basis: P50Latency[ms] (↓), P99Latency[ms] (↓), Load[req/s]
  • chart: client vantage, trace sampler v4; MethodDescription#HTTP_probe_v4
  • Before comparing a client end-to-end reading with a server processing reading, resolve their Characteristic and observation basis. Both may use ms yet answer different questions. Keep separate coordinates or obtain readings for the same declared characteristic and basis; a unit conversion alone cannot supply that match.
  • normalization: monotone time‑warp compensation for collector skew; invariant = percentile order
  • comparability: normalization‑based (UNM) with declared normalization
  • aggregation: use a max-of-mins latency fold only when the declared service model justifies it; a WLNK bound needs its own bottleneck model. Neither follows from latency percentiles alone.
  • RSG hook: DeployerRole.Active gated if P99 < declared SLO over the admission window.

A.19.CN:8.3 - Clinical/episteme line — Trial‑outcome CN‑frame (Cardio_2026)

  • cs_basis:
    • slot_id: ΔBP characteristic: BloodPressureChange scale: { type: ratio, unit: mmHg } polarity: down
    • slot_id: AdverseRate characteristic: AdverseEventRate scale: { type: ratio, unit: “%” } polarity: down
    • slot_id: Age characteristic: Age scale: { type: ratio, unit: years } polarity: none
  • chart: cohort definition; MethodDescription#TrialProtocol_v5
  • normalization: the named propensity-score case-mix adjustment uses its declared covariates and target population to estimate the specified ΔBP contrast. Preserve the estimand, adjustment assumptions and residual limitations; the adjusted estimate is an output, not an invariant guaranteed by the method name.
  • comparability: normalization‑based (UNM) (post‑adjustment)
  • aggregation: recombine subcohorts only under the declared population and weighting model; select the law or supported bound for each named safety outcome under its own justified dependency model.
  • RSG hook: evidence-use validation of an admission requires CN-frame acceptance. A named assurance claim uses B.3 and the relation or bounded-use evidence its argument needs; CL may summarize that evidence but supplies no automatic assurance result.

A.19.CN:8.4 - Worked mini-schemas (entity and relation mixtures across CN-frames, informative)

The three small schemas below show an operations use, an assurance use, and an alignment use. They are explanatory representations, not storage requirements. Each keeps the bearer, system-role kind and assignment, measurement or evaluation result, source-local relation, and evidence use distinct.

A.19.CN:8.4.1 - Operations CN‑frame — runtime gating and enactment

Entity graph view:

System ── classifiedAs ──> SystemRoleKind
System + SystemRoleKind + scope/window ── assignment ──> SystemRoleAssignment
Role-state graph ── lists ──> State
Checklist ── tested by evaluation Work ──> StateAssertion
Work ── performedBy ──> assigned System
Work ── enacts ──> Method

The System is classified under the local system-role kind and participates in the obtaining assignment used by this RSG account.

An asserted evaluation or operational Work additionally needs the complete A.13 core: the performing System, local agential-role kind and its membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits the Work; F.6 applies afterward only when precise assignment-bound attribution is needed. The schema abbreviates these grounds; its arrows do not establish them.

A role-state graph lists states such as Ready, Waiting, or Degraded. Evaluation applies the state checklist and supports a StateAssertion. In this gating use, operational enactment requires an admissible assertion that an enactable state obtains; the Work, Method, assignment, and result remain different objects.

Relational stub:

TableKey columns (essential)
ROLE_ASSIGNMENTRA_ID; HOLDER_SYSTEM_ID; SYSTEM_ROLE_KIND_ID; REFERENCE_SCHEME_ID; SCOPE_REF?; WINDOW_FROM; WINDOW_TO
RCS_SNAPSHOTSNAP_ID; RA_ID; WINDOW_FROM; WINDOW_TO; CHAR_ID; VALUE; UNIT?; SCALE_TYPE; RESULT_REF
RSG_STATESTATE_ID; SYSTEM_ROLE_KIND_ID; NAME; ENACTABLE
CHECKLISTCHK_ID; STATE_ID; PREDICATE_TYPE; PREDICATE_SPEC
STATE_ASSERTIONSA_ID; RA_ID; STATE_ID; CHK_ID; WINDOW_FROM; WINDOW_TO; VERDICT; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?
WORKWORK_ID; PERFORMER_SYSTEM_ID; METHOD_ID; WINDOW_FROM; WINDOW_TO; result and evidence refs as needed

The RCS snapshot keeps the characteristic, value, any applicable unit, scale, window, and result identity visible. A StateAssertion separately identifies any normalization instance and any claim that uses a Bridge. An enactment query can therefore ask whether the latest admissible assertion for this assignment has an enactable state and a passing verdict without treating a role label, CN-frame, or Bridge as the acting System.

A.19.CN:8.4.2 - Assurance CN‑frame — evidence freshness and related local meanings

Entity graph view:

NormalizationMethodInstance ── used for ──> characteristic re-expression
F.9 Bridge ── relates ──> exact source and target F.17 cells
ComparisonClaim ── cites ──> normalization instance and/or Bridge-use claim
RelianceClaim ── cites ──> evidence status and assurance limits

The normalization instance identifies the declared re-expression and its validity window. The Bridge identifies only an obtaining relation between two local senses. A comparison that relies on either one says so in its own use claim; its evidence and assurance limits remain explicit.

Relational stub:

TableKey columns (essential)
NORMALIZATION_METHODNORMALIZATION_METHOD_ID; KIND; DESCRIPTION_REF
NORMALIZATION_INSTANCENORMALIZATION_INSTANCE_ID; NORMALIZATION_METHOD_ID; SRC_CHAR_ID; TGT_CHAR_ID; FORMULA_SPEC_OR_LUT_REF; VALIDITY_WINDOW; EVIDENCE_REF
BRIDGEBRIDGE_ID; SOURCE_CELL_REF; TARGET_CELL_REF; PREDICATE_PROFILE
BRIDGE_USE_CLAIMBOUNDED_USE_CLAIM_ID; BRIDGE_ID; DIRECTION; CORRESPONDENCE_RULE; APPLICABLE_USE; TOLERATED_LOSS; POLARITY
COMPARISON_USEUSE_CLAIM_ID; RESULT_REF; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?; EVIDENCE_USE_REF; ASSURANCE_REF?
ASSURANCE_EVENTAE_ID; USE_CLAIM_ID; EFFECT; DETAILS; WINDOW

The table can express the relevant claims and their audit path; its presence supplies no missing evidence. A changed assurance result, stale normalization instance, or revised evidence can reopen only the comparisons whose grounds it changes.

A.19.CN:8.4.3 - Alignment CN‑frame — design-time reuse across local schemes

Entity graph view:

Checklist for target state ← re-expression (N when normalization is used) ─ Checklist for source state
source F.17 cell ── obtaining Bridge under its predicate profile ──> receiving F.17 cell
SystemRoleKind' ── stated refinement relation ──> SystemRoleKind

A checklist re-expression cites the normalization instance when it uses normalization. When it also needs a semantic correspondence or difference between local senses, apply §4.3: test the F.9 predicate, retain any missing or unresolved required correspondence, and separately ground the use of an obtaining Bridge. A stated refinement between system-role kinds records how their state distinctions correspond; it must preserve the entailment needed for enactability rather than relying on similar role names.

Relational stub:

TableKey columns (essential)
RSG_REFINEMENTREFINEMENT_ID; SOURCE_SYSTEM_ROLE_KIND_ID; TARGET_SYSTEM_ROLE_KIND_ID; SOURCE_STATE_ID; TARGET_STATE_ID; ENTAILMENT_RULE; EVIDENCE_REF
CHECKLIST_REEXPRESSIONREEXPRESSION_ID; SRC_STATE_ID; TGT_STATE_ID; NORMALIZATION_INSTANCE_ID?; BRIDGE_USE_CLAIM_REF?; SOURCE_EDITION; TARGET_EDITION; VALIDITY_WINDOW?

At least one enactable source state must correspond under the stated rule to an enactable target state when that is the promised refinement. The re-expression record fixes the two editions and any validity window required by the re-expression or receiving use, so later changes can reopen the affected alignment rather than silently changing an old checklist. A referenced UNM instance retains its required validity window.

A.19.CN:8.5 - Same basis, different holder and timing cases

For this worked case, the receiving comparison cites CN-Spec E7, and its commissioning control requires independent certification of E7’s comparison basis. Alice authored that basis. After her stewardship assignment ends, she receives a certifier assignment and examines E7. The holder condition fails: the later assignment still certifies her own basis.

Bob’s certifier assignment instead overlaps Alice’s stewardship assignment. When Bob neither authored nor materially selected E7’s basis, this local holder condition is satisfied despite the overlap. The receiver must still establish Bob’s authority for E7, the required examination and any stronger organizational-independence condition from the commissioning control. Missing evidence for one of these conditions leaves that dependent certification conclusion open; different names alone do not establish it.

In an ordinary comparison with no independent-certification requirement or claim, Alice may use a sufficiently supported E7 basis and publish the comparison as uncertified. If E8 later changes the compared population or normalization basis, reopen only uses and certification claims depending on that changed basis. Correcting E7’s registry display while its content and evidence stay fixed does not have that effect.

A.19.CN:9 - Anti‑patterns (and the fix)

Anti‑patternSymptomWhy it hurtsFix (CN‑Spec slot)
Chartless number“Latency = 120”No unit/vantage → untestableFill cs_basis + chart
Normalization smugglingQuiet “per‑unit” normalisation mid‑streamTrend reversalDeclare UNM normalization references (NormalizationMethodId / NormalizationMethodInstanceId) + named invariants (see A.19.UNM)
Bridge-by-nameReusing equal labels under different schemesFalse comparabilityTest the needed F.9 predicate; cite a Bridge only when it obtains, then ground the separate receiving-use claim and reliance. An unsupported required correspondence blocks that use.
Free-hand averagingAn arithmetic mean is used without a model for the intended risk resultThe number can answer the wrong questionUse A.9 to select a justified law, bound or separate-input result; declare a Γ_fold only for the selected fold
CN‑frame sprawlOverlapping definitions obscure which comparison basis to useAvoidable reconstruction and maintenanceReuse a sufficient basis and retain differences that change the use. A registry supports maintained editions; use E.9 when a consequential decision needs a DRR.
Self-certification hidden by assignmentsA holder authors the basis and later certifies it under a new roleA required independent check still examines that holder’s own basisApply §4.2 to participation in the edition; separate authority and examination, and keep uncertified use explicit when certification is not required

A.19.CN:10 - Didactic quick cards (one‑liners teams reuse)

  1. Numbers travel with their basis. Cite the characteristic and scale editions, bearer, reference or comparison basis, any qualifying scope/window, and result.
  2. Expose a normalization used by the trend. An undisclosed change leaves the comparison basis unresolved.
  3. The intended result selects the law. Use a weakest-part bound only when its declared dependency model justifies it; a safety label alone selects no fold.
  4. Ground an RSG-based Work-admission decision. Establish the required state assertion before relying on it for admission; establish the other Work-admission conditions separately under A.15.1.
  5. Ground the semantic correspondence needed by reuse. Test the F.9 predicate between local senses; use an obtaining Bridge only through the separate bounded-use claim and required reliance. Retain a false or unresolved result when no positive relation is established.
  6. When independence is required, check who made the basis. A later role assignment does not remove self-certification; a sufficient uncertified comparison remains possible when no independent certification is required.
  7. Ground each chart value. Name the reference state and coordinate patch. For measured values, cite the applicable measurement method and protocol; for evaluated or otherwise ascribed values, cite their rule and basis.
  8. Make deprecation recoverable. A maintained edition identifies its retirement conditions and any supported successor relation.
  9. Keep the characteristics needed by the use. Omit irrelevant coordinates; retain every distinction that changes the comparison.
  10. Identify the normalization used. Cite its method and instance under A.19.UNM; ordinary mathematical mapping language alone identifies neither.

A.19.CN:11 - SCR / RSCR Harness (acceptance & regression)

These are concept‑level checks; notation‑agnostic.

A.19.CN:11.1 - SCR — Acceptance (first introduction)

  • SCR‑A19.4‑S01 (Completeness). CN-Spec has every applicable mandatory value. Each cs_basis position declares its Scale and value meanings, Unit when that Scale has one, and any preference rule used for desirability ranking. Descriptive comparisons need no preference rule. The chart names its reference state and coordinate patch; measured values cite their C.16 measurement method/protocol, while evaluated or otherwise ascribed values cite the rule and basis that establish them, as required by CC-A19.D1-2 and CC-A19.D1-3.
  • SCR‑A19.4‑S02 (Normalization clarity). When normalization is used, normalization identifies the admitted mechanism and provides the normalization references required by A.19.UNM (methods / invariants / fix, and instances when used). If instances are referenced in assurance logs, their evidence/backing and validity constraints are handled by C.16, not by A.19.CN.
  • SCR‑A19.4‑S03 (Comparability test). Provide one worked coordinatewise or normalization-based comparison and the source/evaluation basis needed for its result. Use an Evidence Graph reference when that is how the required basis is represented.
  • SCR‑A19.4‑S04 (Γ‑fold audit). When aggregation is used, the rule states the intended result, law and applicability basis, with only the required property claims; the reviewer reconstructs the result on a toy set under that model.
  • SCR‑A19.4‑S05 (Required certification). Identify the receiving claim/control and relied-on CN-Spec edition or admission basis. If independent certification is required, check the certifier against authoring/material-selection history, then the applicable authority and examination conditions. Replay both successive same-holder assignments and overlapping different-holder assignments. When neither an independent-certification claim nor a control applies, keep the sufficiently grounded comparison; add a certification status only when it matters to the receiving use.
  • SCR‑A19.4‑S06 (Bearer and basis recoverable). For each CN-Spec characteristic used in the worked example, retain its bearer, Characteristic and Scale editions, reference/comparison basis, any qualifying scope/window, and the measurement, evaluation or other value-ascription grounds required for the reading. Shared frame-level values need not be repeated for every characteristic. Use A.10 when provenance or bounded reliance must remain replayable.

A.19.CN:11.2 - RSCR — Regression (on change)

  • RSCR‑A19.4‑R01 (UNM edit). When normalization changes, flag every comparison and Bridge-use claim that cites that normalization for affected-only reassessment, then rerun the corresponding worked comparisons.
  • RSCR‑A19.4‑R02 (Slot or basis change). A changed definition receives a new edition. Preserve old results with their original basis; their present admissibility still depends on their evidence and intended use. A display-only correction that preserves the definition is handled as such.
  • RSCR‑A19.4‑R03 (Chart drift). Updating measurement protocol bumps edition; historic Work keeps old edition link.
  • RSCR‑A19.4‑R04 (Fold change). A changed fold requires reassessment of roll-ups that rely on the changed rule. Recompute dependent results; reuse unaffected results and retain historical outputs with their original rule.
  • RSCR‑A19.4‑R05 (Changed relation or use basis). After either endpoint or its relation-semantic basis changes, test the applicable F.9 predicate for the new candidate. Reassess the separate use direction, correspondence rule, loss tolerance and reliance when their grounds change; reopen only dependent claims.
  • RSCR‑A19.4‑R06 (Deprecation rule). On deprecating a CN-frame, the registry gives any supported successor relation, or states that no successor is established when that matters to reuse. Reconsider affected Bridges and uses; preserve historical relations instead of silently changing their endpoints.
  • RSCR‑A19.4‑R07 (Certification basis). A change to the relied-on basis, relevant participation history or applicable control reopens only the certification and receiving conclusions it can change. A registry display change alone does not.

A.19.CN:12 - Interaction summary

  • A.2 / A.2.5 (Roles / RSG). RSG checklists quote CN‑Spec.acceptance; enactment gates rely on admitted CN‑frame data.
  • B.1 and A.9. B.1 supplies any claimed whole/part construction; A.9 supplies an unresolved aggregation-law choice or property check. CN-Spec records the justified Γ_fold, including its model and time policy.
  • B.3 (Assurance). For a named assurance claim, retain the relation and use evidence consumed by its argument. CL may serve as evidence shorthand; any quantitative effect needs a declared Scale and model. A safety roll-up requires the law or bound justified for its named outcome and dependency model.
  • Proof/inference support and the C.16/A.19 characterization stack. Scales, applicable Units and measurement guidance come from C.16, A.17, A.18 and A.19. Claims about folds use C.2.1 when claim/episteme identity matters, A.10 when evidence or provenance must remain replayable, B.3 for a named assurance claim, and C.23 when method-family evidence or maturity is at issue.

A.19.CN:13 - Minimal CN‑Spec template (copy/paste, informational)

This example arranges the information needed to specify the comparison basis. A.19.UNM defines normalization terms; A.19.UINDM defines indicatorization; C.16 governs measurement and evidence backing; G.0 supplies the applicable admission conditions.

CN‑frame: <Name>      Edition: <edition>      Bearer: <bearer or bearer-kind ref>
ComparisonBasis: <corpus, baseline, reference state, or declared comparison set>
ScopeAndWindow: <scope ref and qualification interval, when used>
IntendedUse: <claim, comparison, admission, or aggregation use>
characteristics:
  - <CharacteristicName> : <Scale; Unit when applicable>  [Polarity, when used: <preference rule>]
Chart:
  reference_state: <text>
  coordinate_patch: <domain/subset>
  measurement_protocol_ref?: <applicable measurement MethodDescriptionId>
  value_ascription_basis?: <applicable evaluation rule and evidence>
Normalization (when used):
  UNM: <UNMId?>
  methods: [<NormalizationMethodId>… ]
  method_descriptions: [<NormalizationMethodDescriptionRef>… ]
  invariants: [<property>… ]           # what the selected transformation preserves; name losses too (A.19.UNM)
  fix?: <NormalizationFixSpec>          # only for an established class whose receiving use needs a representative (A.19.UNM)
Indicators (optional):
  policy_ref: <IndicatorChoicePolicyRef>
  resulting_indicators: [<IndicatorId>… ] // selection is policy‑defined; NCVs alone do not make an Indicator (see A.19.UINDM)
Comparability:
  mode: coordinatewise | normalization-based
  minimal_evidence: <basis required for this comparison>  # admission conditions under G.0; measurement/evidence backing under C.16
Aggregation (when used):
  fold: <Γ_fold expr>   time_policy: <window, statistic>
  WLNK/COMM/LOC/MONO: <only selected property claims, with their model and applicability basis>
Acceptance:
  checklist: [<observable criterion>… ]
  window?: <qualification interval when required>
  evidence_anchors: [<required observation, evaluation or other support refs>… ]
Alignment (optional):
  semantic_uses: [<obtaining Bridge, separate use claim, required reliance, kept/lost distinctions, applicable guards, optional CL>… ]
  plane_relations: [<applicable plane relation>… ]
MaintenanceAndDeprecation (for a maintained edition):
  responsibility: <responsible holder or maintenance arrangement>
  DRR_links?: [<DRR ids for decisions that need them>… ]
  deprecation_plan: <short note>

When producing a StateAssertion, an implementation should be able to cite the CN-Spec edition and evidence anchors used, along with any normalization instance and Bridge on which the assertion depends.

A.19.CN:14 - SoTA-Echoing — enough basis to compare coordinate values

Practice question. What must accompany two chart values before a practitioner treats them as comparable? The selected comparison basis identifies the bearer/property, value-producing procedure or evaluation rule, relevant time and result basis alongside Scale/Unit meanings. A serious smaller alternative is to carry only the quantity kind, value and unit, converting units before comparison.

The QUDT quantity model is the useful comparator: it separates Quantity, QuantityKind, QuantityValue and Unit and supports precise quantity descriptions. Adopt that discipline where a Unit applies. Using only that portion is cheaper and sufficient when the same property, procedure and observation basis are already fixed outside the record. Reject treating it alone as evidence that two independently obtained readings answer the same question; this is a limit of that reduced use, not a claim that QUDT forbids richer descriptions.

The SOSA/SSN 2023-edition working draft of 24 September 2026 supplies the compared observation/procedure line: it distinguishes the feature, observed property, procedure, result and temporal qualifications. Adapt that separation in CN-Spec’s bearer, cs_basis and chart, CC-A19.D1-1/-3/-11, and SCR-S01. The source is work in progress and does not establish FPF admission, Scale lawfulness, certification independence or a Bridge; those retain their rules. An evaluated coordinate keeps its rule and basis rather than acquiring a fictive measurement or Unit.

At comparable effort, both alternatives start from the same pair of readings and existing method records. The selected line adds the references that can change this comparison, reusing common frame-level values rather than repeating a full observation history for every cell. The SRE case in §8.2 shows the gain: equal millisecond units cannot make client end-to-end latency and server processing latency the same Characteristic. Keep them separate or obtain values for the same declared characteristic and observation basis. The added references cost more than a bare numeric pair; that cost is accepted when the basis is not already common and recoverable.

Reopen when a proposed comparison changes the property, value-producing rule, reference state or relevant window, or when a smaller representation demonstrably retains all the distinctions needed by that use. These sources support the compared representational choices; they do not validate every CN-frame or make its registry self-certifying.

A.19.CN:Close - Closing perspective

A CN-Spec keeps the comparison basis with the readings. Reuse it while that basis remains sufficient; revise it and the dependent conclusions when the Characteristic, chart, normalization or intended use changes. A registry supports maintained editions. Cross-local reuse retains the coordinate mapping, semantic relation or plane relation it needs, with any separate bounded-use claim and required reliance.

A.19.CN:End

A.19.CHR - Shared Rules for Characterization and Selection

Type: Architectural (A) Status: Stable

Use this when. A characterization or selection task combines normalization, indicator choice, scoring and comparison, and the stages must agree on admissibility, uncertainty and the meaning of their results. A locally reasonable calculation can still be unusable downstream if it changes a scale, hides a default or discards a distinction needed for comparison.

Start here. Select the declaration edition for each of the six CHR roles in §4.2. For the intended protocol, resolve each stage to its operation and governing specifications before choosing input values. The first useful result is a chain whose arguments, results and stop conditions agree. §4.8.1 works this through from a baseline to a selected set.

Ordinary boundary. For one operation, use its A.19 member pattern. For a different set of jointly used contracts, use A.6.7. For an edition/reference plan without shared CHR conditions, use A.15.2. A CHR suite describes the shared contract; applications, gate decisions and publication retain their own rules.

CHRMechanismSuiteDescription is the canonical MechSuiteDescription instance for the six CHR roles. Its selected edition can be cited through MechSuiteDescriptionRef. On a P2W path, an ordinary A.15.2 WorkPlan records the chosen baseline; CHRMechanismSuiteSlotFillingsPlanItem is used only when A.15.3 typed filling is needed for an independently declared position.

A.19.CHR:1 - Problem frame

A team compares options whose measurements use different units or scales. Normalization must preserve the distinctions its comparator needs; indicator choice must retain basis positions; scoring must respect the declared scale rules; selection must consume the comparisons made. Missing evidence can interrupt any stage.

When each stage silently chooses its own editions, defaults or handling of uncertainty, the final selected set no longer follows from one recoverable basis. A shared suite makes those conditions explicit while leaving each operation’s law in its own declaration. On a P2W path, the plan records the intended editions and references; applications supply their own bindings later.

A.19.CHR:2 - Problem

This pattern applies when a workflow (especially in Part G) needs lawful characterization over measurable slots/coordinates (e.g., in Q‑bundles), including normalization, indicatorization, scoring, aggregation, comparison, and selection.

A.19.CHR:3 - Forces

  • No implicit crossings. Identify the relations claimed or consumed: F.9 semantic correspondence, C.3.3 kind correspondence, or a separately governed plane relation. Use E.18/A.21 visibility and gate anchors when their crossing or gate is present. Context, entity, plane and edition changes alone create none of those relations.
  • CN‑Spec and CG‑Spec must remain the governing spec refs. Mechanisms cite them; mechanisms do not duplicate them.
  • Content allocation. Keep suite-wide obligations separate from discipline/method specializations, generators and packaging.
  • SlotKind invariance. Specialisation chains must preserve SlotKind meaning and only refine ValueKind / strengthen guards/laws.
  • No silent scalarization / totalization. CPM comparison results preserve the declared partial-order distinctions, and selection remains set-returning; any numeric summary is report‑only unless declared as a lawful comparator/policy.
  • P2W split. Planned slot filling belongs to WorkPlanning; launch values belong to WorkEnactment.

A.19.CHR:4 - Solution

Select the six declarations, cite one CN-Spec and CG-Spec baseline, and state the protocol under §§4.2–4.5. Check the arguments and result of each used operation against that baseline. Record planned editions in A.15.2 when a P2W path is involved; add A.15.3 typed filling only for an independently declared position. For a launch claim, establish the Work occurrence and its launch facts under E.18:5.6; any FinalizeLaunchValues witness is a separate episteme about those facts.

The suite contains membership, shared obligations, references and permitted protocols. It supplies no operation result or gate decision.

A.19.CHR:4.0 - Resolve the contract before use

A usable step names the selected member declaration, its operation and the governing argument, result, law and admission content. Use §4.2.2 to locate the declaration and the selected baseline to resolve its edition. A missing contract or unresolved edition stops that dependent step; a stage name or source list cannot fill the gap.

A.19.CHR:4.1 - Objects published by this pattern

A.19.CHR:4.1.1 - CHRMechanismSuiteDescription

A MechSuiteDescription instance whose role is to:

  • enumerate the canonical CHR mechanisms (as MechanismDeclarationRefs),
  • declare suite‑level obligations/invariants,
  • declare suite‑level spec pins (refs only),
  • declare admissible suite protocols (Uses pipelines),
  • require an edition/reference baseline in WorkPlanning on P2W paths; add typed planned fillings only when their independently declared positions are current.

A.6.7 supplies the general suite form. This pattern selects the six CHR roles and their shared obligations, with the P2W baseline specified below.

A.19.CHR:4.1.2 - Planned baseline and conditional typed filling

Use ordinary A.15.2 WorkPlan content for the selected suite, declaration and CN-Spec/CG-Spec editions, method and comparator references, time rule, expected guards and any required crossing references. Address that content through the WorkPlan and its local locator.

Use CHRMechanismSuiteSlotFillingsPlanItem under A.15.3 only when a selected operation argument or relation position already has its own meaning, designation, ValueKind, cardinality and binding predicate. Cite that governing declaration and position. A suite field or a name in the CHR lexicon does not create such a position. A missing fact may remain unknown in the plan; a missing declaration must be recovered before typed filling. Bindings and launch witnesses remain with enactment.

A.19.CHR:4.2 - Canonical mechanism membership

Select one A.6.1 declaration contract for each of the following six CHR roles. The resulting mechanisms set contains six distinct declaration epistemes, not implementations or unqualified operation-family names:

  1. UNM — Normalization Mechanism
  2. UINDM — Indicatorization Mechanism
  3. USCM — Scoring Mechanism
  4. ULSAM — Lawful Scale Aggregation Mechanism
  5. CPM — Comparison Mechanism
  6. SelectorMechanism — universal set‑returning selection kernel
CHRMechanismSuiteDescription.mechanisms :=
  [ UNM.IntensionRef,
    UINDM.IntensionRef,
    USCM.IntensionRef,
    ULSAM.IntensionRef,
    CPM.IntensionRef,
    SelectorMechanism.IntensionRef ]

Membership semantics note (normative). mechanisms denotes a duplicates-free set of declaration epistemes; order carries no semantics. The displayed …IntensionRef labels are retained citation names for those declarations. In a suite baseline, each resolves to one selected edition under A.6.7 §4.1. They are not references to a newly defined operation-family kind. Any intended ordering is expressed only in suite_protocols.

Rationale. The shared CN-Spec and CG-Spec define the comparison and admission basis; the suite adds the common obligations for using its member operations together. Transport and crossing obligations apply when those relations are used.

A.19.CHR:4.2.1 - CHR SlotKind Lexicon (suite‑wide minimum)

To prevent SlotKind drift across the CHR mechanism chain and across SoTA wiring modules, CHR mechanism declarations SHOULD use the SlotKind tokens from this lexicon whenever they refer to the corresponding semantic roles. New SlotKinds MAY be introduced, but only by first extending this lexicon (suite‑governed), then citing the new SlotKind from the affected mechanism card.

Lexicon (minimum). Tokens below are SlotKind names (not types). Meanings, ValueKind / reference designation and binding rules come from the governing A.6.1 operation-local declarations; A.19 and G.0 constrain their domain use. A.6.5 relation SlotSpecs are not the source of these operation positions.

  • Core suite SlotKinds

    • CharacteristicSpaceSlot
    • CNSpecSlot
    • CGSpecSlot
    • ContextSlot
  • Indicatorization

    • IndicatorChoicePolicySlot
    • IndicatorSetSlot — A.19.UINDM’s selected declaration-local basis positions, retained with the CharacteristicSpace basis; each position keeps its Characteristic and Scale
    • JustificationSlot
  • Scoring

    • InputProfileSlot
    • ScoreProfileSlot
  • Aggregation

    • MeasureSetSlot
    • GammaFoldSlot
    • GammaTimeRuleSlot (optional)
    • AggregatedMeasureSlot
    • ContributorSetSlot (optional)
  • Comparison

    • LeftProfileSlot
    • RightProfileSlot
    • ComparatorSpecSlot
    • ComparisonResultSlot
  • Selection

    • CandidateSetSlot
    • CriteriaSlot
    • TaskSignatureSlot (optional)
    • SelectionSlot
  • Evidence / admissibility (optional, policy‑bound)

    • MinimalEvidenceSlot (optional)

Note. This lexicon is small and role‑based: it constrains naming, not method semantics. Method/discipline specifics belong in SoTA packs (G.2) and wiring‑only GPatternExtension modules, not in the suite core.

A.19.CHR:4.2.2 - Canonical Intension targets (no dangling refs)

Each …IntensionRef resolves through its governing pattern below to one A.6.1 declaration edition. These targets locate the declaration; the selected suite/WorkPlan baseline supplies edition resolution for use. A draft stub can locate unfinished work but cannot resolve an operation contract it does not declare.

Canonical targets (normative anchors).

A.19.CHR:4.3 - Suite obligations

CHRMechanismSuiteDescription.suite_obligations MUST be written using the canonical obligation vocabulary from A.6.7:4.2 and MUST include the following clauses (duplicates-free set semantics; order carries no meaning):

{ semantic_correspondence_requirements, independent_correspondence_requirements, transport_declarative_only, penalties_route_to_r_eff_only, guard_decision_tristate(pass|degrade|abstain), unknown_never_coerces_to_pass, gate_decision_separation, guard_lexeme_reservations, cg_spec_cite_required_for_numeric_ops, no_silent_scalarisation_of_partial_orders, no_silent_totalisation, no_thresholds_in_suite_core, crossing_visibility_required, planned_filling_in_workplan, actual_launch_facts_and_witness, implementation_export_discipline_when_cited }.

A.19.CHR:4.3.1 - Crossings, visibility, and penalties
  • semantic_correspondence_requirements: for a semantic correspondence between different local interpretation bases, recover the F.17 endpoint cells, the obtaining F.9 Bridge, and the bounded-use/reliance basis required for this use.
  • independent_correspondence_requirements: a C.3.3 kind correspondence retains its own endpoints, obtaining and receiving-use conditions. If an F.9 correspondence is also used, establish it independently. EntityOfConcern change alone supplies neither relation. Plane-only claims stay under their governor.
  • transport_declarative_only: the suite does not embed CL/Φ/Ψ/Φ_plane conversion or penalty tables. It states the refs, pins and anchors consumed by its obligation; applicable rules and E.18 crossings or gate decisions remain with their owners. Distinct governed relation kinds may participate in the selected structure. A graph label or suite obligation supplies neither an obtaining relation nor a hidden conversion, penalty or gate decision.
  • penalties_route_to_r_eff_only: apply the model-bound condition in A.6.7:4.2(2). Its applicability and result meaning come from the selected assurance model; the same clause governs loss assessment and separation from legality, invariant and claim-scope judgments.
  • crossing_visibility_required: an E.18 crossing in an independently selected TransformationFlowStructure retains any CrossingBundle required for a named downstream use of durable crossing evidence under E.18:5.1; an A.21 work-entry gate retains its applicable gate anchors. A changed edition pin triggers the recheck required by its receiving use, but does not itself create a crossing, Bridge or gate.
A.19.CHR:4.3.2 - Guards and gate separation
  • Guard decision tristate: mechanism‑level guards return GuardDecision := {pass | degrade | abstain}.
  • Unknown never coerces to pass: unknown/insufficient evidence MUST map to degrade or abstain, not to pass.
  • Gate decision separation: mechanisms and suite objects MUST NOT publish GateDecision nor DecisionLog. block is gate‑only (OperationalGate(profile)).
  • Guard lexeme reservations: USM.CompareGuard / USM.LaunchGuard are gate‑level pins; mechanism predicates use suffixes …Admissibility / …Eligibility.
A.19.CHR:4.3.3 - Numeric admissibility and order lawfulness
  • CG‑Spec citation required: any numeric scoring/aggregation/comparison MUST cite CG-Spec (SCP, ComparatorSet, MinimalEvidence and any Γ_fold or Φ/CL pins used), and MUST NOT embed a “shadow CG‑Spec” inside mechanisms/suite.
  • No silent scalarisation of partial orders: CPM results retain the declared comparison distinctions and the selector returns a set; any scalar summary is report‑only unless declared as a lawful comparator/policy.
  • No silent totalisation: absence of totality MUST NOT be hidden by “tie‑breakers” or implicit weights.
A.19.CHR:4.3.4 - P2W discipline
  • Edition/reference baselines use A.15.2 WorkPlan content. Typed planned filling uses A.15.3 only for independently declared positions.
  • Launch facts. Under E.18:5.6, establish an independently admitted A.15.1 Work occurrence and the obtaining relations or A.6.1 application bindings that establish its launch values.
  • A separate FinalizeLaunchValues episteme may designate that Work occurrence and those facts. Preserve the planned baseline; neither the suite requirement nor a planned value establishes launch facts.
A.19.CHR:4.3.5 - Thresholds and defaults
  • no_thresholds_in_suite_core: acceptance thresholds live in AcceptanceClauses / TaskSignature / GateProfile, not in CHR suite core.
  • Default discipline (no competing defaults): the suite MUST NOT introduce competing defaults. If a default is used (e.g., PortfolioMode), it MUST be cited from its single declared source (typically a TaskSignature or a policy-id), and all other mentions are citations.
A.19.CHR:4.3.6 - Implementation export discipline (when cited)
  • Suite MAY cite implementations (CAL/LOG/CHR) as refs, but:

    • LOG/CHR do not export Γ,
    • CAL exports exactly one Γ,
    • imports are acyclic.
A.19.CHR:4.3.7 - Claim reference index

The existing claim identifiers resolve to the rules below. The rules are stated once at their governing locations.

Claim identifiersGoverning content
L-A67CHR-01§4.2 membership set semantics
L-A67CHR-02, L-A67CHR-03, A-A67CHR-02§§4.1.2 and 4.6 planned baseline and its separation from enactment
A-A67CHR-01§4.5 operation/edition resolution
D-A67CHR-01, D-A67CHR-02CC-A67CHR-1 description kind
D-A67CHR-03§4.2 and CC-A67CHR-2 canonical membership
D-A67CHR-04§4.4 and CC-A67CHR-3 specification references
D-A67CHR-05§§4.3.1 and 4.4; CC-A67CHR-13 transport/crossing content
D-A67CHR-06§4.6 and CC-A67CHR-10 planned baseline
D-A67CHR-07, D-A67CHR-08CC-A67CHR-10a and CC-A67CHR-11 typed filling and plan/enactment separation
D-A67CHR-09CC-A67CHR-16 anchors required by the claim
E-A67CHR-01, E-A67CHR-02§4.6 and CC-A67CHR-14 baseline citation and enactment evidence

A.19.CHR:4.4 - Suite spec pins

CHRMechanismSuiteDescription.suite_spec_pins MUST be refs‑only and MUST include:

  1. Required spec refs: {CNSpecRef, CGSpecRef} (as required pins, not copied content).

  2. Planned baseline on a P2W path: cite the A.15.2 WorkPlan and content locator carrying the selected suite, declaration and spec editions. Other uses still resolve their selected editions but need no invented WorkPlan. A typed A.15.3 item is additional only when §4.1.2 applies.

  3. Required edition pins / policy pins (when applicable):

    • editions{CG‑Spec, ComparatorSet, UNM.TransportRegistryΦ, …} when the chosen protocol path is edition‑sensitive,
    • policy‑id pins for Φ/Ψ/Φ_plane when crossings are expected.

Spec pins are anchors; they do not embed tables (CL ladders, Φ registries) and do not introduce transport edges.

A.19.CHR:4.5 - Suite protocols

CHRMechanismSuiteDescription.suite_protocols follows A.6.7: each step resolves to one selected member declaration edition and one operation designator in that declaration. Its guards, laws, arguments and results come from that edition. Stage names below are labels, not substitute operation designators.

If suite_protocols is present, it SHALL include at least one protocol that is equivalent to the canonical suite-closed pipeline below (with fold_Γ optional).

The declaration-local bindings for the canonical stages are:

Stage labelGoverning declarationOperation designator
normalizeselected UNM.IntensionRef edition, A.19.UNM §4.1; consume its directed value and preservation/loss basis, adding class use only under its conditionsapply
indicatorizeselected UINDM.IntensionRef edition, A.19.UINDM §4.1Indicatorize
scoreselected USCM.IntensionRef edition, A.19.USCMScore
fold_Γ, optionalselected ULSAM.IntensionRef edition, A.19.ULSAMFold_Γ
compareselected CPM.IntensionRef edition, A.19.CPM §4.1Compare
selectselected SelectorMechanism.IntensionRef edition, A.19.SelectorMechanismSelect

Resolve each cited edition before applying these bindings; a changed designator or contract requires a revised binding. A list of source pins alone selects no operation. If two editions remain eligible, the suite baseline must state the condition that selects one, or stop that dependent step with the unresolved choice.

Canonical suite-closed protocol.

normalize (UNM) →
indicatorize (UINDM) →
score (USCM) →
fold_Γ? (ULSAM) →
compare (CPM) →
select (SelectorMechanism)
  • The fold_Γ step is optional; it is not implicit inside score/compare/select.
  • suite_protocols encodes a pipeline/Uses contour between mechanisms; it does not define a specialisation relation (⊑/⊑⁺). A claimed refinement, conservative extension or equivalence uses its own A.6.1 §4.8 content-preservation test, predicate and endpoint facts, including the applicable A.6.RCD missing-governor/substrate branch. Project extensions retain their independently declared restrictions; a pipeline order or ⊑/⊑⁺ label establishes no such comparison.
  • Any publish/telemetry step is outside suite_protocols (to preserve WF-MS-2 closure) and follows the rules for that separate use. G.10 governs shipping Part-G outputs as a SoTA-Pack; E.24.PUB governs episteme availability, form and carrier claims. These steps are not hidden continuations of CHR mechanisms.

A.19.CHR:4.6 - P2W hook: planned edition and reference baseline

For each P2W path that uses the suite, record the chosen suite and member declaration editions, CN-Spec and CG-Spec, method/comparator references, time selection, and applicable guard or crossing references in A.15.2 WorkPlan content. That baseline selects the contracts expected by the protocol and remains separate from actual values and gate decisions.

When a downstream claim needs a typed planned filling, apply §4.1.2 and A.15.3 to the independently declared argument or relation position. At enactment, identify the application and its bindings under the selected declaration. The planned baseline alone establishes neither binding nor performed Work.

A.19.CHR:4.7 - Canonical concept card fragments

A.19.CHR:4.7.1 - CHRMechanismSuiteDescription as a MechSuiteDescription

Canonical skeleton (references only).

CHRMechanismSuiteDescription := ⟨
  mech_suite_id        : MechSuiteId,
  mechanisms           : [UNM.IntensionRef, UINDM.IntensionRef, USCM.IntensionRef,
                          ULSAM.IntensionRef, CPM.IntensionRef, SelectorMechanism.IntensionRef],

  suite_obligations    : SuiteObligations {
                          semantic_correspondence_requirements,
                          independent_correspondence_requirements,
                          transport_declarative_only,
                          penalties_route_to_r_eff_only,
                          guard_decision_tristate(pass|degrade|abstain),
                          unknown_never_coerces_to_pass,
                          gate_decision_separation,
                          guard_lexeme_reservations,
                          no_thresholds_in_suite_core,
                          cg_spec_cite_required_for_numeric_ops,
                          no_silent_scalarisation_of_partial_orders,
                          no_silent_totalisation,
                          crossing_visibility_required,
                          planned_filling_in_workplan,
                          actual_launch_facts_and_witness,
                          implementation_export_discipline_when_cited
                        },

  suite_spec_pins  : SuiteSpecPins {
                          required_spec_refs := {CNSpecRef, CGSpecRef},
                          required_planned_baseline_ref? := WorkPlan ref + local baseline locator, // on a P2W path
                          required_edition_pins? := …,
                          required_policy_id_pins? := …
                        },

  suite_protocols?     : SuiteProtocol[*],            // includes the canonical pipeline
  suite_notes?         : …,                            // didactic boundaries + anti-patterns
  suite_audit_obligations? : …                         // UTS+Path pins, crossings visibility, guard governing-pattern assignment
⟩
A.19.CHR:4.7.2 - Baseline content and conditional CHRMechanismSuiteSlotFillingsPlanItem

The baseline names the selected declaration edition for every protocol step, the CN-Spec and CG-Spec editions, and any selected method or comparator references. Retain the described entity, bounded context, CG-frame, path slice, publication scope and time selector when they qualify the planned use; a reference plane may be derivable from its cited governing context. There is no implicit latest.

Expected USM.CompareGuard or USM.LaunchGuard pins identify their gate owner where needed to aggregate later GuardFail events. An expected crossing carries only the applicable obtaining Bridge/plane relation and policy references, plus a crossing-bundle anchor when its rule requires it. The baseline copies no governing table.

For an A.15.3 typed filling, cite the declaration edition and its independently declared argument or relation position. target_slot_bearing_description_ref cannot point to the suite merely because the suite lists a CN-Spec field. Reuse the position’s meaning, designation and binding rules. In the UNM apply case, planning CN-Spec use first requires the selected operation’s CN-Spec argument declaration; the suite’s own citation is not that argument.

Preserve the cited baseline and its intended values. Operation applications and bindings follow A.6.1; a claimed Work occurrence additionally requires A.15.1 admission. E.18:5.6 governs launch facts and any separate FinalizeLaunchValues witness; GateDecision and DecisionLog retain their gate governor.

A.19.CHR:4.8 - Examples

A.19.CHR:4.8.1 - Worked case — two offers from baseline to selected set

Situation and planned baseline. The question is whether either offer can be discarded without accepting a worse price or defect-free proportion. Stipulate an A.15.2 WorkPlan OfferReviewPlan@1, local content locator characterization, selecting suite OfferCHRSuite@1.

This case’s suite has the six distinct member declarations in §4.2.2, each at its §4.1 content in the same publication edition as this example. Its stable mech_suite_id is OfferCHRSuite; its obligations are the §4.3 clause set. The full canonical protocol is available, with Fold_Γ optional. The selected path uses apply → Indicatorize → Score → Compare → Select, under the operations’ own eligibility evaluations.

The plan pins OfferCHR-CN@1, OfferCHR-CG@1, the methods and policies below, and the point 2030-01-01T00:00Z in UTC. The suite requires those same references and the OfferReviewPlan@1#characterization baseline. No typed filling is needed for this ordinary reference selection. These are planned references; no application or result is claimed by the plan.

Case specifications, outside the suite. Take the two offers, lower-price/higher-quality Pareto rule and all-nondominated selection rule defined as OfferPareto@1 and OfferSelection@1 in A.6.7 §4.6. The raw case values here are A=(1000 eurocents, 0.8), B=(1200 eurocents, 0.9), stipulated exact rather than measured in a claimed real-world episode.

OfferCHRSpace@1 has basis positions cost and quality, with the price and defect-free-proportion Characteristics. Its input price chart uses eurocents; its normalized price chart uses EUR. Quality uses the same dimensionless ratio scale in both charts.

Pinned case referenceContent used by the protocol
OfferCHR-CN@1Admits A and B on this basis; binds the bearer identified by each coordinate/profile to OfferScope@1, selected slice set {OfferSlice@1}, the concept plane, the CHR reference scheme and the planned evaluation point. Its comparability mode is normalization-based into the EUR/quality chart. The admitted normalizers are CentsToEUR@1 and QualityIdentity@1; indicator_policy is BothPositions@1. Both complete candidates satisfy acceptance, with no further threshold.
CentsToEUR@1Configured ratio:scale method on cost values from 0 to 1,000,000 eurocents; n(x)=x/100 EUR. Bound coordinate set={cost}. Preserves price, equality and order; loses no distinction on this domain.
QualityIdentity@1Configured ratio:scale method on quality values in [0,1]; n(q)=q. Bound coordinate set={quality}. Preserves all values and their order.
BothPositions@1Select {cost,quality} from OfferCHRSpace@1, retaining position meanings and order for profile projection. The policy is evidence-gated and uses the CG default; missing either required value means abstain.
IdentityScore@1Description of the stipulated admitted identity-scoring Method: apply the identity to each normalized measure. Domain/codomain are price in [0,10000] EUR and quality in [0,1]; result cardinality is two measures. Preserve scales and polarities (lower price, higher quality). No aggregation or scalarization occurs.
OfferCHR-CG@1SCP permits the two declared ratio-scale normalizations, identity scoring and componentwise order comparisons. ComparatorSet contains OfferPareto@1. MinimalEvidence requires the two input values, basis, configured-method declarations and their algebraic preservation facts. CN normalization evidence uses the same requirement. No evidence override or degrade branch is selected.

Both normalizer instances and their method descriptions are declared by the case CN-Spec, with validity window [2030-01-01T00:00Z, 2030-01-02T00:00Z). Their positive scale factors establish the stated preservation facts. The profiles retain their bearer, basis positions and the resulting EUR/quality chart. No quotient, class representative or additional CharacteristicSpacePredicate is used.

Applied protocol, separate from the plan. Stipulate the following mathematical invocation episodes, each extending from taking up its named inputs to returning its result. Each episode’s inputs bind by use and its results bind at that return under the selected declaration. The evaluation point qualifies the offers; it is not the calculation interval. All episodes retain the case’s scope, slice set, scheme, plane, point, basis and cited evidence. This account asserts no dated U.Work.

Resolved stageBound inputs and eligibilityReturned value
A.19.UNM §4.1 / applyFour invocations, one per coordinate: the bound normalizer, raw CoordinateValueSlot, OfferCHRSpace@1 and OfferCHR-CN@1. Each UNM_Eligibility evaluation passes: coordinate, method, domain, invariants, validity and evidence agree.The cost invocations return 10 EUR and 12 EUR; the quality invocations return 0.8 and 0.9. Each has its own NCVSlot binding.
A.19.UINDM §4.1 / IndicatorizeFor each bearer, OfferCHRSpace@1, OfferCHR-CN@1, BothPositions@1 and OfferCHR-CG@1; no MinimalEvidence override. The policy and complete evidence yield pass.Each invocation returns {cost,quality}; the projected profiles retain those positions and their normalized values.
A.19.USCM §4.1 / ScoreEach projected InputProfileSlot, OfferCHR-CN@1, OfferCHR-CG@1 and IdentityScore@1; no override. ScoreEligibility passes the admitted method, normalized input and evidence.Two separate ScoreProfileSlot bindings: A=(10 EUR,0.8), B=(12 EUR,0.9).
A.19.ULSAM §4.1 / Fold_ΓThe baseline selects its declaration as a suite member but skips this optional step. There is no multi-value fold in this use.No fold application or output is asserted.
A.19.CPM §4.1 / CompareThe A/B score profiles, case CN/CG, OfferPareto@1 and the common use arguments. CompareEligibility passes; normalization refs and preservation facts are retained.Invocation cCHR returns {A ∥ B}.
A.19.SelectorMechanism §4.1 / SelectCandidateSetSlot={A,B}; comparisonBasis={cCHR}; requiredComparisons={(A,B,OfferPareto@1)}; tokenProvenance maps A ∥ B to cCHR’s own returned binding. ComparisonResultSlot is its token union. CriteriaSlot retains all nondominated candidates, selectorPolicy=OfferSelection@1, and TaskSignatureSlot is absent. The same CN/CG and use arguments apply, with no predicate or evidence override. Select consumes its SelectEligibility pass result.SelectionSlot={A,B}. Both offers survive because each is better on one criterion.

The suite’s audit requirement is to recover these operation refs, effective arguments, guards and returned bindings, together with the baseline citation. Shared order and uncertainty obligations are satisfied without constructing a total score. There is no semantic, kind or plane correspondence, E.18 flow crossing, A.21 gate, implementation export or publication claim in this case; their conditional anchors are therefore inactive.

Changed condition. Move the evaluation point to 2030-01-03T00:00Z while retaining the selected method validity windows. UNM_Eligibility returns abstain. The planned method refs remain readable, but there is no new admitted NCV and no basis for continuing this selected normalization-based path to a new selected set. Reusing yesterday’s values by changing their date would fail their binding and use conditions. A new valid method baseline and new applications are needed.

The useful result is the justified retained set under one resolved contract chain. Acceptance or authorization to buy, an independently admitted dated Work account, and publication of the result are separate claims; none follows from {A,B} or from the plan. A PlainView may say “both offers remain; neither dominates at the stated evaluation point” and cite the baseline. It may not say “purchase approved” or erase the expiry stop.

A.19.CHR:4.8.2 - Variant — archive retention with report-only illumination

For an Archive-mode use, retain the selected set under the selected selector policy. The two-offer case can retain {A,B}; archive maintenance requires its own admitted policy and declarations. Record the DescriptorMap and DistanceDef editions when computing illumination, together with the policy declaring that result report-only. A separate CAL policy is required before illumination influences dominance. An archive label, descriptor display or diversity summary cannot silently change the comparison or discard either offer.

A.19.CHR:4.9 - Evolution rules

  • Kernel-first stability. This suite is minimal. Adding a core CHR mechanism changes the suite edition and membership. Use F.18 alias docking when a changed name or alias needs it; preserve the ability to cite earlier editions. For exploratory or domain‑specific extra stages, prefer a suite variant (e.g., A.19.CHR+ / A.19.CHR.Extended) or project‑level specializations (patterns P.*) instead of mutating the kernel.
  • Mechanism specializations are not wiring. A claimed domain/project specialization needs its A.6.1 §4.8 comparison predicate, endpoint facts and content-preservation test under its governing pattern. A variant label or ⊑/⊑⁺ symbol alone establishes no refinement. The suite binds to declaration editions through …IntensionRef; the A.15.2 planned baseline records the selected contracts and any method or realizer references. A specialization that changes a used contract requires the corresponding suite member and protocol binding to change.
  • Protocols evolve within the suite boundary. Adding/changing suite protocols (A.19.CHR:4.5) is allowed as long as each protocol remains suite‑closed and does not import publish/telemetry as a mandatory step. If a protocol introduces a new required stage not present in membership, treat it as a suite variant rather than a protocol edit.
  • SoTA harvesting updates methods, not the kernel. Updates from SoTA harvesting/synthesis (G.2) are carried via edition‑pinned MethodDescriptionRef / ComparatorSpecRef selections and wiring modules (G.x:Ext.*), preserving the selected declaration set while its content stays unchanged. If a SoTA update requires changing a mechanism’s signature/laws, the change happens in the governing A.6.1 mechanism card and MUST emit RSCR triggers from G.Core.
  • New mechanism families (outside CHR). Introduce new mechanism kinds as new family-specific patterns under the appropriate mechanism family. If they require suite-level composition and P2W binding, add a corresponding suite pattern A.6.7.<FamilyKey> with an A.15.2 edition/reference baseline and A.15.3 typed filling only when independently declared positions require it, mirroring the governing-pattern assignment routing of this pattern.

A.19.CHR:5 - Archetypal Grounding

A.19.CHR:5.1 - U.System vignette

A decision about a system must select a declared set of options when measurable evidence comes from multiple slices (test rigs, simulations, field trials). Measurements are multi-scale and not always comparable without explicit normalization, and some evidence is missing or stale. The team needs lawful comparison and selection without forcing a single scalar “fitness”.

Use the filled reference selection in §4.8.1 as the baseline: contracts, scales, methods, time rule and policies yield a retained set of two offers. When the inputs instead come from tests or field trials, replace the stipulated case evidence with the evidence required by the CN-Spec/CG-Spec; incomplete evidence follows the declared failure rule. A claimed dated Work and any launch witness require their independent enactment basis. Any semantic/kind/plane relation or flow/gate crossing retains its own required anchors.

If a required UNM operation is hidden inside scoring, or an undeclared weighted sum replaces the selected partial-order comparison, the protocol no longer identifies the operations and comparison rule used. Make each required operation explicit and select a lawful scoring or comparison rule. Keep Fold_Γ optional unless the chosen method uses it.

A.19.CHR:5.2 - U.Episteme vignette

A research episteme compares methodological claims across traditions where some evaluation scales are ordinal (rank-based) and others are interval or ratio. The group wants to select a method family for a task while keeping uncertainty explicit and avoiding illicit aggregation (e.g., averaging ranks).

The comparison cites CNSpecRef (comparability mode and indicator policy) and CGSpecRef (SCP, ComparatorSet, MinimalEvidence and Γ_fold when used). On a P2W path these references belong to the planned baseline. The application uses the selected UINDM operation to choose indicators, USCM to compute scale-lawful scores, ULSAM only for a selected fold, and CPM to preserve the comparison distinctions. The selector returns a selected set rather than forcing a single winner.

If a draft evaluation writes “take the mean rank and pick the minimum”, replace that step with a scale-lawful comparator declared in CG-Spec. For report-only telemetry, retain the rank distribution or another summary justified by the declared ordinal scale, such as a median when applicable. An arithmetic mean requires a separately justified quantitative model; calling it telemetry does not make ordinal averaging lawful.

A.19.CHR:6 - Bias-Annotation

The following trade-offs matter when using the suite:

  • Gov. Bias toward fail-closed admissibility and auditability (applicable relation/crossing references, pinned spec refs, guard–gate separation). Mitigation: the tri-state GuardDecision allows uncertainty to degrade or abstain without forcing gate-level blocking; exploration can still proceed via SoS‑LOG policy branches.
  • Arch. Bias toward explicit operation composition, with E.18 node-level structure when a TransformationFlowStructure is selected, and planned baselines on P2W paths. Mitigation: the suite fixes only the universal core; discipline-specific generators and extensions remain separate mechanisms connected by Uses, keeping the suite compact.
  • Onto/Epist. Bias toward a separation of CN‑Spec and CG‑Spec spec refs, mechanisms (A.6.1), and planning epistemes (A.15.2; A.15.3 for typed fillings). Mitigation: specialization is supported (⊑/⊑⁺) and does not require inventing new kernel constructs; method diversity is expressed via MethodDescription refs and ComparatorSpec refs.
  • Prag. Bias toward conservative uncertainty handling (unknown does not coerce to pass) may reduce decisiveness. Mitigation: “probe-only” and “sandbox” behaviors are permitted as audited degrade modes (policy-id + branch-id), not as silent coercions.
  • Did. Bias toward explicit terminology and pins increases authoring surface area. Mitigation: this pattern provides a canonical protocol and ordinary baseline content with reusable references so authors can reuse a stable template rather than re-inventing local prose conventions.

A.19.CHR:7 - Conformance Checklist

A CHR mechanism-suite publication set is conformant to A.19.CHR iff all applicable items below hold. Existing claim references resolve through §4.3.7.

A.19.CHR:7.1 - Suite object checks

CC‑A67CHR‑1 (Correct description kind). A conforming CHRMechanismSuiteDescription SHALL be a MechSuiteDescription instance and SHALL NOT be encoded as a MechFamilyDescription.

CC‑A67CHR‑1a (Stable citation handle). A conforming CHRMechanismSuiteDescription SHALL include a stable mech_suite_id suitable for downstream planning and audit citation.

CC‑A67CHR‑2 (Canonical membership). A conforming CHRMechanismSuiteDescription SHALL enumerate exactly the six CHR mechanisms (UNM, UINDM, USCM, ULSAM, CPM, SelectorMechanism) as MechanismDeclarationRefs.

CC‑A67CHR‑2a (Membership set semantics). A conforming CHRMechanismSuiteDescription.mechanisms SHALL be duplicates-free and SHALL NOT treat order as semantic (WF‑MS‑1).

CC‑A67CHR‑2b (No dangling IntensionRefs). Each member reference resolves to one declaration edition under §4.2.2, and each used operation resolves within that declaration. A stub without the contract is insufficient for use.

CC‑A67CHR‑3 (Governing spec refs are pins, not copies). A conforming CHRMechanismSuiteDescription SHALL cite CN‑Spec and CG‑Spec as required spec refs and SHALL NOT duplicate them as “shadow specs”.

CC‑A67CHR‑3a (Planned-baseline requirement is pinned). For a P2W path, a conforming suite cites the WorkPlan and baseline locator carrying its selected editions and references. Other uses resolve the editions without inventing a WorkPlan. A.15.3 typed filling is conditional on independently declared positions.

CC‑A67CHR‑4 (Crossing discipline is complete). A conforming CHRMechanismSuiteDescription.suite_obligations SHALL include the complete clause set in §4.3, with each clause applied under its stated conditions.

CC‑A67CHR‑5 (Guard/gate separation). A conforming CHRMechanismSuiteDescription.suite_obligations SHALL:

  1. enforce tri‑state guard decisions (pass|degrade|abstain),
  2. enforce unknown_never_coerces_to_pass,
  3. enforce guard–gate separation (no GateDecision / DecisionLog at mechanism/suite level; block remains gate‑only), and
  4. enforce guard lexeme reservations (USM.CompareGuard / USM.LaunchGuard are gate-level pins; mechanism predicates use …Admissibility/…Eligibility).

CC‑A67CHR‑6 (No hidden scalarization/totalization). A conforming CHRMechanismSuiteDescription.suite_obligations SHALL include bans on silent scalarization of partial orders and silent totalization.

CC‑A67CHR‑7 (No thresholds in core + single-source defaults). A conforming CHRMechanismSuiteDescription.suite_obligations SHALL include no_thresholds_in_suite_core. If any suite protocol relies on defaults (e.g., PortfolioMode), the suite description and plan items SHALL cite those defaults from their single declared source (typically a TaskSignature or policy-id), and SHALL NOT introduce competing defaults in the suite.

CC‑A67CHR‑8 (Protocol explicitness + closure). If suite_protocols is present, a conforming CHRMechanismSuiteDescription SHALL:

  1. express any dependence as an explicit protocol step (no hidden invocation of UNM/UINDM/ULSAM inside score/compare/select), and
  2. satisfy WF‑MS‑2: every step resolves to one member declaration edition and one operation in that declaration, with no unresolved edition choice.

CC‑A67CHR‑8a (Canonical protocol is available when protocols are published). If suite_protocols is present, a conforming CHRMechanismSuiteDescription SHALL include at least one protocol equivalent to: normalize (UNM) → indicatorize (UINDM) → score (USCM) → fold_Γ? (ULSAM) → compare (CPM) → select (SelectorMechanism), where fold_Γ is optional. Any publish/telemetry continuation follows its applicable rules: G.10 for Part-G pack shipping and E.24.PUB for episteme availability, form or carrier claims. It MUST NOT be encoded as a ProtocolStep inside suite_protocols (to preserve WF-MS-2 closure).

CC‑A67CHR‑9 (Packaging separation). A publish/telemetry continuation is outside suite_protocols and follows its applicable rules. G.10 governs Part-G pack shipping; E.24.PUB governs episteme availability, form and carrier claims. The suite description itself is not the shipping publication.

A.19.CHR:7.2 - Planned baseline checks

CC‑A67CHR‑10 (Planned baseline exists). Every P2W path slice using the suite has an A.15.2 WorkPlan baseline with the selected suite and member declaration editions.

CC‑A67CHR‑10a (Typed filling has its governor). Use a CHRMechanismSuiteSlotFillingsPlanItem only when A.15.3 applies to an independently declared operation argument or relation position. Cite that declaration and position; a suite field is insufficient.

CC‑A67CHR‑11 (Plan and enactment). Planned references and values establish no actual binding, launch value, execution witness or gate decision.

CC‑A67CHR‑11a (Use anchors). Recover the described entity, bounded context, CG-frame, path slice, publication scope, reference plane when current, and time rule needed for the declared use.

CC‑A67CHR‑11b (Expected guards). Expected guard pins belong to {USM.CompareGuard, USM.LaunchGuard} and name the responsible gate when later event aggregation requires it.

CC‑A67CHR‑11c (Spec baseline). The baseline cites CN-Spec and CG-Spec and their selected editions. Cite the independently declared position separately when either reference is also used as a typed planned argument filling.

CC‑A67CHR‑12 (Edition resolution). Each used declaration and operation has one governing edition. Multiple applicable editions require a selection condition before use; a source list or implicit latest does not resolve them.

CC‑A67CHR‑13 (Applicable crossing references). Expected crossings cite only the relations, policies and bundle anchors their governing rules require; the baseline embeds no CL/Φ tables.

CC‑A67CHR‑14 (Audit traceability). Later Work audit can cite the WorkPlan and baseline locator and distinguish bindings or deviations from planned values.

A.19.CHR:7.3 - MVPK face checks (when projected)

CC‑A67CHR‑15 (Views do not add meaning). Any TechCard(…) / PlainView(…) projection of the plan item does not introduce new assertions beyond the plan item.

CC‑A67CHR‑16 (Fail-closed pins on claimful faces). If a face publishes an edition reference, retain that reference. For a comparability or launch claim, also publish every anchor required by the relations, receiving policy and gate used; a gate-owned USM pin retains its GuardOwnerGateSlot. Missing a required anchor makes that claim nonconformant. A note that only pins a new declaration edition needs no invented BridgeCard, UTS crossing row, CrossingBundle or gate event.

A.19.CHR:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsAvoid / repair
Using MechFamilyDescription as a suite containerCollapses “many implementations of one mechanism” into “many mechanisms”, breaking reuse constraintsUse MechSuiteDescription for multi-mechanism sets; use MechFamilyDescription only for multiple implementations of a single U.Mechanism
Embedding a second CG‑Spec or CL/Φ/Φ_plane tables inside the suite or plan itemDuplicates the governing spec refs and creates drift between planning, gates, and auditPublish refs and pins only (CGSpecRef, BridgeCardRef, policy-id pins); keep tables in their canonical registries and cite them
Implicit UNM/UINDM/ULSAM “inside” score/compare/selectBreaks auditability and violates the suite protocol explicitness obligationMake dependencies explicit as protocol steps (Uses) and cite the chosen mechanism instances in the planned baseline and audit pins
Hidden thresholds or weights in CHR coreMoves acceptance criteria into the wrong layer, defeating the declared defaults source and traceabilityKeep thresholds in AcceptanceClauses, TaskSignature, or GateProfile; if a policy is needed, mint a policy-id and cite it
Scalarizing partial orders “for convenience”Violates set-return semantics and hides incomparabilityKeep comparisons set-valued via CPM and selectors set-returning; any scalar summary must be declared as report-only telemetry or as a lawful comparator
Treating planned baseline as a launch witnessSmuggles execution facts into planning and blurs P2W separationRecord the edition/reference baseline in A.15.2; add A.15.3 fillings only for declared positions and keep bindings and launch witnesses in enactment
Using CompareGuard / LaunchGuard as mechanism lexemesCollides with reserved gate-level pins and blurs guard vs gate responsibilitiesIn mechanisms use …Eligibility / …Admissibility; reserve USM.CompareGuard and USM.LaunchGuard for gate-visible pins

A.19.CHR:9 - Consequences

ConsequenceUpsideCost / riskMitigation
Shared CHR contracts across usesA later comparison can recover the same member declarations and joint conditionsResolving the declarations and their editions takes effortReuse the baseline while its contracts and intended use remain applicable; keep method-specific choices in their governing descriptions
P2W planned baselineMakes planned editions, time selectors and applicable crossing references recoverableAdds the baseline content needed by that pathReuse adequate A.15.2 content; add a typed item only for an independently declared position
Tri-state guard semanticsAvoids false precision and prevents unknown from silently passingMore conservative behavior can yield larger selected sets or more abstentionsUse SoS‑LOG degrade branches for probe-only exploration while preserving traceability
Spec pins, not copied spec contentReduces drift and keeps CN‑Spec/CG‑Spec as the governing specificationsRequires discipline in authoring and reviewEnforce “refs-only” at suite/plan level and use conformance items CC‑A67CHR‑3 and CC‑A67CHR‑13 to prevent copied specifications

A.19.CHR:10 - Rationale

The suite description records membership and shared conditions, while each member declaration supplies its own operation contract. This arrangement has four consequences:

  1. Member contracts remain distinct. The suite is a D-episteme that enumerates mechanisms and obligations. Each A.6.1 member declaration retains its arguments, results, laws and admission conditions.

  2. Spec refs remain centralized. CN-Spec and CG-Spec state the applicable comparison, normalization, indicator-choice and numeric-admission conditions. The suite cites those specifications without copying their content.

  3. P2W integration becomes explicit without turning planning into execution. Ordinary A.15.2 content records the edition/reference baseline. Typed A.15.3 filling is needed only for an independently declared position; only enactment supplies bindings and launch witnesses.

  4. Uncertainty has a disposition. Tri-state guard decisions distinguish passing, qualified degradation and abstention. Safety of a receiving use still depends on its evidence and policy; a decision token supplies no missing ground. Gate decisions and decision logs remain with OperationalGate(profile).

A.19.CHR:11 - SoTA-Echoing

Working question. How should a team connect normalization, indicator choice, scoring, comparison and selection so that the final result still follows from the selected scales, evidence and method conditions when one of them changes?

For this question, adapt declaration-first workflow composition, the selected line compared in A.6.7 §11. CWL v1.2.1’s process references, requirements and abstract operations supply the external model for distinguishing a described operation from a concrete process. The CHR adaptation makes the shared CN/CG conditions and each operation’s result bindings explicit. CWL supplies neither these FPF laws nor the justification of the offer comparison.

The alternative is one pinned executable estimator pipeline, exemplified by scikit-learn 1.9.1 Pipeline. It is attractive when fitting and sequential transformation already express the whole task. For the same five used CHR stages, compare it with the suite while holding the methods, data, policy and evidence requirements fixed. Both can calculate the two offers correctly. A pipeline plus checks can also reject expired normalization.

That pipeline’s executable composition alone, however, does not state the case’s scale-preservation argument or resolve the separately governed selection policy; those facts still need an inspectable account.

Adopt method/specification resolution and reject a stage-name-only chain as sufficient justification. The suite accepts the extra reference cost to expose these conditions before choosing implementations. This is a trade-off in explanation and reuse, not a claimed runtime benefit or measured authoring saving. If a single existing pipeline already exposes every condition needed by the receiving use, reuse its account; creating another suite copy adds no gain.

The effect is in §§4.0, 4.5 and 4.8.1: choose each contract before using a stage, retain every transformation’s basis through the comparison, and stop the normalization-based path when its selected validity window fails. The final {A,B} remains a set even though the five stages could be packaged behind one callable interface. That packaging cannot add a singleton preference or purchase approval.

The two primary specifications are source models and a comparator; the choice for CHR is a local architectural inference. They establish no empirical superiority of this pattern. Reopen the comparison if the receiving task becomes one fully self-contained executable pipeline, if its account already makes the same conditions cheaper to recover, or if a changed member contract makes the common baseline insufficient.

A.19.CHR:12 - Relations

A.19.CHR:12.1 - Builds on

  • A.6.7 MechSuiteDescription (the base suite description kind and obligations surface)
  • A.15.2 WorkPlan for edition/reference baselines; A.15.3 for conditional typed planned filling
  • A.6.1 U.Mechanism (operation-local argument/result declarations, their derived SlotIndex, and the comparison tests in §4.8)
  • A.19.CN CN-Spec and G.0 CG-Spec (comparison and admission conditions)
  • E.18 / E.18.1 for a TransformationFlowStructure, its crossings and P2W carry-through
  • E.10 (lexical and ontological discipline) and E.19 (conformance style)

A.19.CHR:12.2 - Coordinates with

  • G.5 (selector semantics, set-return defaults, archive semantics and report-only illumination discipline)
  • G.10 for Part-G pack shipping and E.24.PUB for episteme availability, form or carrier claims; publication and telemetry remain external steps, not suite internals
  • A.21 OperationalGate(profile) and USM.Guards (gate-level decisions and reserved guard pins)
  • C.23 SoS‑LOG (degrade branches such as probe-only and sandbox)

A.19.CHR:12.3 - Constrains and informs

  • Constrains Part G universalization: G patterns should reference this suite for the universal CHR node set and express method and generator specifics only as (a) specializations (⊑/⊑⁺) or (b) separate provider mechanisms connected via Uses.
  • Informs other kits and suites: resolve the selected edition/reference baseline; on P2W paths record it in A.15.2 WorkPlan content. Use A.15.3 only where independently declared positions require typed planned filling.

A.19.CHR:End

A.19.UNM - Normalize Coordinate Values under Declared Invariants

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) Boundary: A.19.CN defines the CN-Spec fields that select normalization and comparability. This pattern defines the normalization operation and how it uses those fields.

Use this when a coordinate value must be re-expressed for a declared comparison or characterization use. First recover the input, selected transformation and the distinctions the receiver needs. If direct comparison already has an adequate common basis, use it without introducing normalization.

For a claimed normalization, recover:

  1. Which UNM_id (if applicable) and which NormalizationMethodInstanceId (and its validity window) was used?
  2. Which NormalizationInvariant[*] were declared (i.e., what is preserved)?
  3. Which bearer, reference or comparison basis, evidence and intended use qualify the value, including any scope or data window? Does the receiving use rely on an obtaining F.9 Bridge, kind relation or plane relation?

Mental model. UNM applies a declared directed transformation from an input coordinate value (CV) to an output (NCV). State its domain, target and preserved or lost distinctions. An inverse, an equality-of-output class or an operation on those classes is a narrower result requiring its own conditions.

A.19.UNM:0 - At a glance — informative

Intent. Declare how coordinate values in a DeclaredCharacteristicSpace are normalized for a chosen comparison or characterization, including the transformation, admissibility conditions and preserved or lost distinctions.

Where it sits.

  • CN-Spec: normalization and comparability.mode select the normalization and whether comparison is coordinatewise or normalization-based.
  • CHR suite role: stage normalize (first-stage, when enabled by the suite protocol / comparability routing).

Key outputs.

  • NCV (NormalizedCharacteristicValue) values for coordinates.
  • When requested for a function n:D→N, the equality-of-output relation x ≡_UNM y iff n(x)=n(y) on its domain D. Its classes form a set quotient; preserving further operations or answers needs the additional tests below.
  • An inverse only on the stated image of an invertible transformation; an operational quotient only for compatible operations and recoverable queries; a NormalizationFixSpec only when a representative of an established class is needed.

Declaration and configured-method identifiers.

  • UNM_id? identifies the selected UNM declaration episteme and its edition under A.6.1; it is distinct from the configured method and from an operation application.
  • NormalizationMethodInstanceId selects the normalization method instance applied to coordinate(s), with its validity window and evidence pins.

Minimum declaration set.

  • In CN_Spec.comparability: set mode, and (when UNM participates in acceptance/comparison) set minimal_evidence.
  • In CN_Spec.normalization: declare UNM_id?, methods, instances, method_descriptions, invariants, and (if representatives are required) fix.
  • For the normalization or eligibility evaluation, recover the available inputs, selected method and specification editions, preservation conditions and result or reason for abstaining under Audit below. Retain a separate record when the receiving use requires one.

Non-goals.

  • Not indicator selection (that is UINDM).
  • Not scoring, aggregation, comparison, selection (USCM / ULSAM / CPM / SelectorMechanism).

A.19.UNM:1 - Problem frame

To compare coordinate values, engineers need to establish:

  • What it means to compare values across charts, slices, bearers, or reference bases, and
  • Which transformations preserve the required distinctions, with their conditions and losses.

Teams routinely face a mismatch between:

  • values that look comparable (“they’re numbers”), and
  • values whose comparison basis differs, such as units, observation populations or validity windows. A supported normalization may make the needed values comparable; some differences instead require new measurements or evaluation grounds, a different comparison, or an unresolved result.

CHR distinguishes normalization, indicatorization, scoring, aggregation, comparison and selection. The chosen protocol determines which stages are needed; UNM supplies normalization when that comparison or characterization requires it.

A.19.UNM:2 - Problem

Hidden or inadequately specified normalization causes four recurring difficulties:

  1. Normalization drifts into hidden places. It gets embedded inside scoring, comparison, or selection, making admissibility and governance non-local.

  2. Comparability becomes rhetorical. People say “we normalize” but cannot answer: Which method and invariants? Which bearer, comparison basis and scope or window? Which evidence? Does the receiving comparison rely on an obtaining Bridge, kind relation or plane relation?

  3. Basis and relation changes become invisible. Teams reuse normalizations for another bearer, comparison basis, source-local meaning, or reference plane without naming what changed or the relation on which the new use depends.

  4. Engineers cannot reconstruct the operation. Scattered definitions can hide its inputs, result, preservation conditions or limits, preventing a justified reuse.

A.19.UNM:3 - Forces

ForceTension
Evolvability vs UsabilityA stable operation contract supports evolving method families; readers still need to find the selected method and its conditions.
Semantic precision vs Cognitive loadFormal invariants/quotients ↔ a mechanism description that engineers can act on.
Shared definitions vs Connected useUNM uses CN-Spec, CG-Spec and any required relation claims; each retains its own governing definition.
Trustworthiness vs OverreachEvidence must support the normalization used; measurement meaning and calibration retain their own grounds.
Locality vs ReuseA normalized value retains its declared bearer, basis, scope/window and use; a later use may require another relation or normalization.
Fail-closed safety vs ConvenienceUnknown/insufficient evidence must not coerce ↔ teams want “a number anyway”.

A.19.UNM:4 - Solution

UNM declares directed normalization operations. For an admitted input in the selected transformation’s domain, return its NCV and the preserved/lost distinctions needed by the receiving use. An undefined input has no normalization result. Use the additional branches below only when the receiver needs an inverse, classes, a class-level operation or a representative.

Select the configured method and apply the declaration below:

  • Routing lives in CN_Spec.normalization and CN_Spec.comparability.mode.
  • Evidence/calibration legitimacy lives in C.16 (MM‑CHR).
  • Method definitions come from the selected normalization methods and their descriptions. G.2 can supply method families; extensions identify the methods and references used.

A.19.UNM:4.0 - Vocabulary (normative)

NormalizationMethodId. A stable token naming a normalization method kind, used in CN_Spec.normalization.methods.

NormalizationMethod. The method kind (class) that defines:

  1. its input/output domains, the directed transformation and the invariants it preserves (NormalizationInvariant[*]), with any distinctions it loses,
  2. its closure rules (composition, and inverses where defined), and
  3. its validity rules (admitted bearer, reference or comparison basis, intended use, and any scope or qualification window that constrains them).

NormalizationMethodDescription. An editioned epistemic description of a normalization method (bounds, validity region/window, scope constraints, and evidence links governed by C.16). For an A.3.2 U.MethodDescription claim, its EntityOfConcern must be an independently admitted A.3.1 Method and its content must make a substantive claim about that Method as a way of doing.

NormalizationMethodDescriptionRef. A ref to an editioned NormalizationMethodDescription, used in CN_Spec.normalization.method_descriptions.

NormalizationMethodInstanceId. A stable token naming a normalization method configured for coordinates in a base DeclaredCharacteristicSpace, with a named validity window and (when required) evidence pins. One such configuration can be used by several apply occurrences; this identifier does not identify a calculation invocation. Used in CN_Spec.normalization.instances.

NormalizationMethodInstance. That configured method, referenced by NormalizationMethodInstanceId. Its coordinate qualification and validity window are separate from the extent of a calculation that uses it.

CV (CoordinateValue). A raw coordinate value for a named measurable slot in a chart: conceptually ⟨slot_id, raw_value⟩ (plus any chart/slice scoping needed by the chart). UNM re‑parameterizes CV → NCV under declared invariants and validity constraints.

NCV (NormalizedCharacteristicValue). A normalized value for a coordinate (UNM does not “normalize characteristics”; it normalizes coordinate values under declared invariants).

Directed transformation. The selected method states its input domain D, target N and transformation rule. For a partial normalizer, D is the subset where a result is defined. An edge from x to its output does not supply a reverse edge. A relation-valued or uncertain output needs its declared result semantics; the function theorem below cannot be applied without a function and equality on its output values.

≡_UNM (equality of normalization outputs). For one fixed function n:D→N, define x ≡_UNM y iff n(x)=n(y). Equality in N gives reflexivity, symmetry and transitivity on D. Thus the fibers form the set quotient D/≡_UNM. Inputs outside D have neither an n-value nor membership in this partition. This relation is distinct from the directed transformation graph.

Operational quotient. To inherit a total operation on classes, equivalent argument tuples must produce equivalent outputs. For a partial operation, its availability must also agree across equivalent tuples. Use the relevant equivalence on each input and output sort. A receiving query q is recoverable only when x ≡_UNM y implies q(x)=q(y). Only after these tests may the equivalence be called a congruence for the named operations. A set quotient alone supplies no such result.

Reversible chart change. A declared inverse recovers the input on the transformation’s stated image. A strictly monotone encoding on a totally ordered domain is injective and invertible on that image, even if the declared target contains other values. A merely monotone LUT may merge inputs. Repeated normalization or idempotence requires its own composable domain and law; it does not follow from the fibers.

NormalizationInvariant. A named invariant (e.g., unit alignment, polarity, reference plane) declared in CN_Spec.normalization.invariants and/or the selected NormalizationMethodDescription. Preserving the declared NormalizationInvariant[*] is the core admissibility claim for a normalization method instance.

NormalizationFixSpec. A declared policy selecting a representative of an already established ≡_UNM class when the receiving use needs one. It does not recover which member was the input or restore a lost query answer. Bound via CN_Spec.normalization.fix; omit it when no class representative is needed.

UNM_id. An optional identifier in CN_Spec.normalization.UNM_id? selecting the UNM declaration episteme used by this CN-frame. Resolve its edition; it is distinct from NormalizationMethodInstanceId (configured normalization method).

ValidityWindow. A named validity window attached to a NormalizationMethodInstanceId, bounding where/when the instance is admissible (no implicit “latest”).

Relation and reuse boundary. A normalized value remains tied to the selected normalization-method instance and edition, characteristic space, its separately referenced description episteme, CN-Spec edition, bearer, reference or comparison basis, evidence and intended use. Retain any scope, slices or data window that qualify that use, as well as the configured method’s declared validity window. Reuse does not establish a transfer relation. Cite an obtaining F.9 Bridge or plane relation when needed, and assess the receiving use separately.

Lexical discipline. Name a UNM operation as normalization, re-parameterization or a coordinate mapping under its declared invariants. Use a specialized FPF Map designation only when its defining conditions apply; an ordinary mathematical mapping does not thereby assert that specialized kind or an F.9 Bridge. Legacy κ‑notation for normalization is retired; do not re‑introduce it.

A.19.UNM:4.1 - UNM operation declaration (normative)

UNM.IntensionRef is the citation name for the A.6.1 declaration episteme presented here. It does not identify a generic family in place of that declaration. The CHR baseline selects its edition before use; the normalize stage resolves to the declaration-local apply operation below. Its four named input meanings, NCV result and eligibility guard come from that selected declaration.

A different realizer of the same declaration changes no suite member. A corrected layout or citation can preserve its C.2.1 identity. A changed argument, law or guard changes the declaration contract and must be selected in the suite and protocol. For example, replacing pass|degrade admission with pass only would change whether apply may produce an NCV for degraded evidence; that hypothetical revision cannot enter through the unqualified name UNM. Whether two declarations concern the same operation family is a separate claim requiring that subject’s kind and identity rule; the UNM label supplies neither.

Scope note. A.6.1 governs this operation declaration. The selected use baseline supplies the project editions and policy references; A.15.2 governs a P2W baseline, and A.15.3 typed filling applies only to independently declared positions. UNM returns the declared operation results and tri-state GuardDecision; gate decisions remain with their governing pattern. Audit below states the information needed to recover an application.

IntensionHeader

  • IntensionId: UNM
  • IntensionRef: UNM.IntensionRef
  • Name: Unified Normalization Mechanism
  • Status: Stable
  • Version: v1.0
  • SuiteRole: CHR.normalize (when enabled by CN/CHR routing)

Imports (cite, don’t duplicate)

  • A.6.1 (shape: U.Mechanism, specialization discipline)
  • A.19.CHR:4.2 (CHR suite boundary / membership)
  • A.19.CHR:4.2.1 (CHR SlotKind Lexicon)
  • A.19.CHR:4.5 (suite protocols: ordering/optionality; suite closure)
  • A.19.CN (CN-frame routing: normalization, comparability.mode)
  • G.0 (CG-Spec admissibility and evidence conditions where required downstream)
  • C.16 (evidence carriers; calibration/validity for normalization legitimacy)
  • A.17/A.18 (measurement meaning & scale lawfulness; not redefined here)

SubjectBlock

  • SubjectKind: declared normalization methods, with their domains, output kinds and preserved/lost distinctions; functional methods may additionally supply ≡_UNM over their admitted inputs
  • RangedValueKind: coordinate values (CV) for named measurable slots in the resolved DeclaredCharacteristicSpace, with characteristicSpaceDescriptionRef and the CN-Spec edition pinned; UNM normalizes values, not characteristics
  • BearerAndUseBoundary: the bearer, reference or comparison basis, evidence and intended use, with any scope, slices or data window that qualify those values
  • Input qualification: coordinate values admitted by the selected CN-Spec for this bearer and use, within the configured method’s declared validity window. This is not an operation-application extent or an A.6.1 slice-membership ExtentRule.
  • ResultKinds:
    • NormalizedCharacteristicValue (NCV)
    • optional function-kernel equivalence (≡_UNM) and its set of classes; a congruence claim only for separately checked operations
    • optional quotient objects and/or Normalization-fixed representatives (via NormalizationFixSpec)

Space range and resolution. Use the DeclaredCharacteristicSpace criterion and paired reference resolution in A.19:5.1.1.1. CharacteristicSpaceRef selects the space; CN_Spec.characteristicSpaceDescriptionRef: U.EpistemeRef pins the description supplying its basis. Both must resolve and agree on that space before normalization; otherwise the dependent use remains unresolved and eligibility abstains. Membership establishes the input’s space structure; the selected operation must still resolve its positions, Scales and use conditions.

A changed basis requires a new space reference and position resolution, even if its label or document path is unchanged. Preserve the preceding space, description and results; reuse requires the correspondence and operation conditions of the receiving use.

Operation-local argument and result declarations

The names below are declaration-local designators. ByValue carries the stated value; each named Ref resolves to one value under this declaration’s effective reference scheme. An episteme reference selects its edition; the space reference and its separate description-episteme reference follow the rule above. Cardinality is per application. The first four arguments are shared declarations instantiated separately for apply and UNM_Eligibility.

Operation and directionLocal designatorMeaning and ValueKindDesignation; cardinality
apply / UNM_Eligibility argumentNormalizationMethodInstanceSlotConfigured normalization method selected for the value; NormalizationMethodInstanceIdByValue; 1 for apply, 0..1 for eligibility
apply / UNM_Eligibility argumentCoordinateValueSlotCoordinate value to transform or assess; CV in the named chartByValue; 1 for apply, 0..1 for eligibility
apply / UNM_Eligibility / compose argumentCharacteristicSpaceSlotSpace that supplies the coordinate meanings and Scales; DeclaredCharacteristicSpaceCharacteristicSpaceRef; 1, or 0..1 for eligibility
apply / UNM_Eligibility / compose argumentCNSpecSlotCN-Spec used for the bearer, basis, evidence requirements and intended comparison, including any scope, slices or qualification windowCNSpecRef; 1, or 0..1 for eligibility
apply resultNCVSlotTransformed value returned under the selected method’s domain and preservation/loss basis; NCVByValue; 1 on successful return, 0 without a defined/admitted result
UNM_Eligibility resultGuardDecisionEligibility judgment under the predicates below; pass, degrade or abstainByValue; 1 on completed evaluation
compose argumentNormalizationMethodInstancePairSlotOrdered pair of configured methods, first inner and second outer; NormalizationMethodInstanceId2ByValue; 1 pair
compose resultNormalizationMethodInstanceSlotConfigured composed method, with its declared validity window and evidence basis; NormalizationMethodInstanceIdByValue; 1 on successful construction
quotient argumentdomainAdmitted domain D of the selected normalization function, with coordinate meanings recoverable; set of CV valuesByValue or one chart-domain reference; 1
quotient argumentNormalizationMethodInstanceSlotConfigured functional method used to form equality-of-output classes; NormalizationMethodInstanceIdByValue; 1
quotient resultUNMEquivalenceSlotRelation on D defined by equality of that function’s outputsByValue; 1 on successful construction
quotient resultclassesSet D/≡_UNM of all classes of that relationByValue; 1 on successful construction

For each argument row, its bindingPredicate obtains exactly when that application uses the resolved value for the row’s stated purpose: as the transformation operand, selected method, governing space/CN-Spec, ordered composition pair or quotient domain. A supplied but unused value is not bound.

UNM_Eligibility may assess an incomplete proposal; an absent argument has no binding and the corresponding missing-input condition gives abstain. This does not relax apply’s inputs.

For each result row, its bindingPredicate obtains exactly when that application returns the resolved value as the row’s declared result, subject to the result laws below. A returned NCV binds the transformation value; compose binds the identifier of the method it constructed; quotient binds the relation and class set it constructed; the guard binds the judgment it evaluated.

Each binding has the A.6.1 identity and maximal continuous extent within its application; a result binds at return, not before. Equal values returned by different applications have distinct bindings because their applications differ.

SlotIndex (derived projection). Project the designators, ValueKinds, designation rules and cardinalities from these operation-local declarations; the index adds no meanings. The historical Slot suffix permits CHR lookup. A.6.5 relation SlotSpecs are not the source of these operation meanings. Method descriptions, invariants and any NormalizationFixSpec are resolved from the selected configured method and CN-Spec. They qualify the method or a separately chosen representative use; they are not additional arguments of every operation.

Relation note (not a SlotKind). A Bridge, kind relation, or plane relation is cited only when the use relies on that obtaining relation. Its declaration and receiving use remain separate from the UNM SlotIndex.

OperationAlgebra

  1. apply

    • Preconditions: UNM_Eligibility(…) ∈ {pass, degrade} (fail‑closed; abstain ⇒ no NCV output).
    • Inputs: NormalizationMethodInstanceSlot, CoordinateValueSlot, CharacteristicSpaceSlot, CNSpecSlot; the selected CN-Spec supplies the bearer, basis, evidence requirements, intended comparison and scope or data window.
    • Outputs: NCVSlot for an input in the selected transformation’s domain, with the declared preservation/loss basis. Undefined inputs produce no NCV; an eligibility result cannot create a transformation value. The optional class/operation results follow their separate conditions below.
  2. compose

    • Purpose: build a composed method when the inner outputs lie in the outer operation’s domain and the claimed preservation laws compose. Losses and receiving-use restrictions remain explicit.
    • Inputs: NormalizationMethodInstancePairSlot (roles = {inner, outer}), CharacteristicSpaceSlot, CNSpecSlot; both instances must be admitted for the same declared bearer, basis, intended use and any scope/window.
    • Output: NormalizationMethodInstanceSlot (new composed NormalizationMethodInstanceId), with a validity window and evidence pins.
  3. quotient(≡_UNM) (optional)

    • Preconditions: one fixed functional normalization on its domain, with an explicit output equality. Recover that domain and the method/use basis.
    • Inputs: domain, resolved from the characteristic-space declaration or a declared chart domain, and NormalizationMethodInstanceSlot.
    • Outputs: UNMEquivalenceSlot and its classes set. Inherited operations additionally require equivalent-output and representative-independent-availability proofs; a class query additionally requires constancy on each class.
    • Use the declared NormalizationFixSpec only when a representative is needed. It selects a member of a class rather than proving that member was the original input.

Applications of these operations

The ApplicationPredicate differs by operation:

  • apply: a calculation applies the selected configured method to the bound CV under the bound space and CN-Spec. Its defined, admitted return is the NCV required above. An abstain decision prevents this application from starting; passing eligibility alone does not start it.
  • compose: a construction resolves the bound inner/outer methods, checks the domain and preservation conditions and constructs their composite for the bound space and CN-Spec. A failed condition yields no composed-method result.
  • quotient: a mathematical construction uses the bound functional method and domain to determine equality of outputs and form its classes. A symbolic construction is sufficient; enumeration of an infinite domain is not required. Stronger inherited-operation and query claims retain their separate proofs.
  • UNM_Eligibility: an evaluation assesses the bound proposal under the eligibility predicates below and returns the corresponding GuardDecision. Its result is separate from any subsequent normalization.

For each operation, the ApplicationIdentityRule identifies one invocation at its calculation or construction locus, from taking up those operands for that operation until return or termination. References to the same uninterrupted invocation reidentify one application. A second invocation, including a nested or later one with the same operands, method, qualification window and result, is another application. Changing an operand after beginning a fresh calculation starts another invocation; a continuation of an interrupted calculation counts as the same application only when continuity of that same invocation is established.

The ApplicationExtentRule takes that invocation’s interval: first use of its arguments through its return or termination. For the guard it is the eligibility evaluation; for compose it is the composite construction; for quotient it is the class construction; for apply it is the value calculation. An unfinished invocation has an open extent and no unreturned result binding. The data’s qualification window and the method’s validity window do not date these invocations. A trace may designate an invocation; a copied record, matching value or valid method identifier does not establish it. Ordinary function and projection guidance remains usable without an assertion of dated U.Work.

For example, with fixed method n(x)=x/10, domain [0,100] and the same CN-Spec, two separate calculations of n(20) both return 2. The first operand-to-return episode and the second are two apply occurrences; each binds 20 and its own return of 2. A third record containing 2, with no corresponding calculation, supplies no third result binding. Two constructions of g∘n, or of the same quotient, are likewise distinct when performed in separate construction episodes; their equal constructed mathematical values do not merge those episodes. Conversely, a second description of the first episode adds no application.

LawSet (UNM laws; identifiers are stable)

  • UNM‑L0 (Values, not characteristics). UNM produces NCV as a value under declared invariants; it does not redefine the underlying characteristic meaning (measurement meaning remains governed by A.17/A.18 and evidence by C.16).
  • UNM‑L1 (Declared method classes). A normalization method instance is admissible only if its method is declared in the allowed method class set: {ratio:scale, interval:affine, ordinal:monotone, nominal:categorical, tabular:LUT(+uncertainty)}.
  • UNM‑L1a (Method semantics are governed by the method). NormalizationMethod defines invariants, closure (composition / inverses where defined), and validity rules. UNM consumes these declarations; it does not invent extra admissibility.
  • UNM-L2 (Directed result before narrower claims). Return the defined transformed value with its domain and preserved/lost distinctions. Functional equality of outputs forms equivalence classes on that domain. A receiving operation descends only after compatibility and, for a partial operation, representative-independent availability hold. A query descends only when constant on the classes; otherwise retain/refine the input or return the missing distinction.
  • UNM-L2a (Declared-basis locality). Every transformed value, function-kernel equivalence and stronger operation/query claim retains the selected method, domain, characteristic space, its separately referenced description episteme, CN-Spec edition, bearer and comparison basis. Keep the scope and data window and the method’s declared validity window. Reusing an unchanged equivalence for a new query does not make that query recoverable; assess its own constancy/compatibility and the receiving-use conditions.
  • UNM‑L3 (Fail‑closed). If admissibility/evidence is insufficient (or required inputs are missing/stale), UNM does not coerce; it yields abstain or degrade (tri‑state guard discipline) and may surface a freshness/work request (see A.19.UNM:4.5). Didactic reading: abstain ⇒ no admitted NCV from this proposed application, so a comparison depending on that output cannot proceed on this basis; degrade ⇒ NCV may be produced but must be treated as policy‑gated and auditable (never “quietly good enough”).
  • UNM‑L4 (No implicit indicatorization). NCV does not imply “indicator”; indicator status is a separate policy step (UINDM).
  • UNM-L5 (Relation before reuse). When a receiving comparison depends on an F.9 Bridge, kind relation or plane relation, establish that relation under its own rule and separately assess the receiving use. For an F.9 use, retain its direction, correspondence rule, loss tolerance and required reliance disposition. A change of bearer, scope, corpus, scale, method or window does not itself establish a relation. Assess losses under the receiving rule; a numerical assurance penalty requires an applicable domain model under B.3.
  • UNM‑L6 (Time explicitness). Validity windows are named; no implicit “latest”.
  • UNM-L7 (Auditability). The application’s selected specifications, supplied inputs, method, conditions, evidence, returned result and any relied-on relation must be recoverable under Audit below. Missing inputs or unresolved references remain explicit when eligibility abstains.
  • UNM-L8 (Source references). Downstream uses cite the method, CN-Spec, basis and evidence editions on which they rely; a registry helps locate those sources but does not supply their content.
  • UNM-L9 (Publication boundary). Publication and telemetry remain outside these operation declarations; any published normalization result retains the meaning defined here. The Audit information is separately recoverable.

AdmissibilityConditions Definition (UNM‑Eligibility): UNM_Eligibility(NormalizationMethodInstanceSlot, CoordinateValueSlot, CharacteristicSpaceSlot, CNSpecSlot) → GuardDecision where GuardDecision ∈ {pass | degrade | abstain} and follows this predicate semantics:

  • pass iff all of the following hold:
    • (CN-Spec binding) the selected NormalizationMethodInstanceId is declared in CN_Spec.normalization.instances (or an equivalent declaration), its method kind is included in CN_Spec.normalization.methods, and (if present) it satisfies normalization.admissible_reparameterizations; the characteristic space, its separately referenced description episteme, CN-Spec edition, bearer, reference or comparison basis and intended comparison are recoverable, together with any scope, selected slices or qualification window required by those declarations or that use;
    • (Target coordinate binding) the input CV’s slot_id belongs to the method instance’s declared bound coordinate set and its value lies in the selected transformation’s input domain;
    • (Scale‑regime compatibility) the method kind is compatible with the coordinate’s regime (ratio:scale | interval:affine | ordinal:monotone | nominal:categorical | tabular:LUT(+uncertainty)) and preserves the declared NormalizationInvariant[*] (from CN_Spec.normalization.invariants and/or the method description);
    • (Validity window) the method instance’s validity window covers the active slice/time policy (no implicit “latest”);
    • (Evidence sufficiency when routed into governance) when comparability.mode = normalization-based (or downstream uses NCV in gated decisions), the method instance’s evidence pins satisfy CN_Spec.comparability.minimal_evidence (minimal-evidence conditions defined in G.0; evidence semantics governed by C.16).
  • degrade iff all non‑evidence conditions above hold, but the evidence check does not pass and the declared failure behavior permits producing a policy‑gated degraded NCV rather than abstaining.
  • abstain otherwise (including missing binding, coordinate mismatch, undefined input, out-of-window validity, or evidence failure when the declared failure behavior is abstain).

Applicability UNM is applicable when:

  • CN_Spec.comparability.mode = normalization-based, or
  • a declared downstream step requires “compare-on-invariants” and thus requires normalization.

UNM is typically skipped when comparability.mode = coordinatewise (unless an explicit downstream step requires a declared quotient/fix anyway).

Relation and reuse boundary

  • A normalized value retains the method instance and edition, its declared validity window, characteristic space, separately referenced description episteme, CN-Spec edition, bearer, reference or comparison basis, evidence and intended comparison, with any scope or data window.
  • If a receiving use depends on a relation between distinct source-local meanings, cite the F.9 Bridge, its direction, what it preserves or loses, and that receiving use. If reference planes differ and the comparison depends on their relation, cite the plane relation as a separate claim.
  • A changed bearer, scope, corpus, scale, method or window does not by itself establish either relation. A correspondence between bearer kinds has its own grounds. Retain the receiving-use rule and its loss limits; quantify an assurance effect only under an applicable B.3 domain model.

Γ_timePolicy

  • Default: point (no implicit “latest”).
  • If normalization relies on time windows, the validity window is part of the method instance and must be declared.

PlaneRegime

  • A normalized value keeps the reference plane declared for its input and intended comparison; normalization creates no implicit plane crossing.
  • When a comparison relies on a relation between different planes, cite that relation, its direction and loss, and keep its use separate from the normalization result.

Audit Make the following information recoverable from the specifications, inputs, evidence and results used. Retain a separate record when the receiving use requires one. For an incomplete eligibility proposal, identify missing inputs or unresolved references and the resulting abstain; do not invent an apply occurrence or an NCV.

  • for a supplied and resolved CN-Spec, CNSpecRef.edition + comparability.mode, the CharacteristicSpaceRef, the separate characteristicSpaceDescriptionRef: U.EpistemeRef pinned there, and the evaluated bearer
  • (when present) CN_Spec.normalization.UNM_id (the selected UNM declaration identity for this CN-Spec)
  • the selected NormalizationMethodInstanceId, when resolved, its validity window and any NormalizationMethodDescriptionRef.edition
  • declared NormalizationInvariant[*] and NormalizationFixSpec (if used)
  • any declared admissible re-parameterizations (if present in CN_Spec.normalization)
  • reference or comparison basis, intended comparison, all evidence pins used, and any claim scope, selected slices or data window that qualify this use
  • an F.9 Bridge, kind relation, or plane relation only when the recorded result or receiving use relies on it, including direction, preserved or lost meaning, and the receiving use
  • the operation evaluated or applied, its returned value or absence of a result, and any emitted FreshnessRequest / work request identifiers (see §4.5)

A.19.UNM:4.2 - CN-frame wiring: normalization and comparability routing (normative-by-reference)

CN-Spec selects normalization and the basis of comparison:

  • comparability.mode ∈ {coordinatewise, normalization-based} governs whether comparisons are done directly or “normalize-then-compare”.
  • normalization.UNM_id? selects the UNM declaration episteme and its edition for this CN-frame.
  • normalization.methods / instances / method_descriptions / invariants / fix provide the declared surface that UNM consumes.

(If present) normalization.admissible_reparameterizations constrain which re‑parameterizations count as “admissible” under the declared invariants. A.19.CN defines these CN-Spec fields; this section states how UNM uses them.

A.19.UNM:4.3 - Evidence and calibration are governed by MM‑CHR (normative-by-reference)

Ground the normalization’s applicability and preservation claims in the relevant evidence, calibration and validity account under C.16, referenced from the configured method. A reference identifies that basis; assess its content for the receiving use.

A.19.UNM:4.4 - Select the result needed by the receiver

For a value comparison, first use the transformed values and their declared preservation/loss basis. Ask whether that basis retains every distinction the comparison requires. Keep original values, refine the normalization, or return the missing distinction when it does not.

Form classes only when their set-level result is useful. For an operation on classes, check output compatibility and partial-operation availability. For a query, check class constancy. Name a NormalizationFix only when an already justified class use needs a representative. A representative-selection policy and additional evidence cannot repair a false compatibility theorem.

A.19.UNM:4.5 - P2W and transformation-flow integration note (normative-by-reference)

When UNM is used inside transformation-flow structures/graphs (e.g., E.18):

  • UNM occurs before selection/decision steps.
  • If required measurements are missing or stale, apply the declared abstain or degrade rule and state the gap. The receiving practitioner first checks whether an adequate current basis is already available and whether obtaining new evidence is worth doing. Any chosen acquisition is separately planned and performed under its applicable method; UNM itself neither obtains measurements nor mandates new Work.
  • A receiving step cites the normalized values, method and CN-Spec editions, bearer, comparison basis, evidence, intended use and scope/window. Establish any relation and its receiving-use conditions under UNM-L5; an assurance penalty follows the applicable B.3 domain model.
  • Downstream consumers cite editioned method, basis and evidence anchors as refs and do not re-author them.

A.19.UNM:5 - Archetypal Grounding

Use the normalization declaration to re-express coordinate values with their preserved and lost distinctions:

  1. Choose an admissible configured method with its evidence and validity window.
  2. Apply it to produce NCVs.
  3. Return an inverse, equivalence, class-level operation or query result only when its additional conditions hold for the receiving use.

Normalization before comparison. A team compares alternatives using normalization-based comparability:

  • CN-Spec declares:
    • comparability.mode = normalization-based
    • normalization.invariants = {unit-alignment, polarity}
    • a method instance M_unitScale with validity window VW_2026Q1 and evidence pins.
  • UNM applies M_unitScale to each coordinate value, producing NCVs.
  • CPM compares the NCV-profiles (not raw profiles).
  • If required evidence pins are missing for a slice, UNM returns GuardDecision = abstain; this comparison cannot rely on a new admitted NCV.

A many-to-one LUT. Let D be {0,1,2} and n(0)=0, n(1)=n(2)=1. Applying n to 2 returns the transformed value 1. Equality of outputs partitions D into {0} and {1,2}: it is reflexive, symmetric and transitive. The directed edge 2→1 supplies no edge 1→2.

The query x>0 is constant on each class and can be answered from the class. The query x>1 is false at 1 and true at 2, so no function of their common class can recover it. Retain x, split that class with the needed distinction, or return the unresolved answer set {false,true} when that set answers the receiving question. Selecting 1 as a representative would answer a question about the representative, not the lost original input.

Now let a partial operation f be defined at 0 and 1 but not at 2, with f(1)=0. Because 1 ≡_UNM 2 while availability differs, f cannot descend to a representative-independent operation on these classes. Matching only the outputs that happen to exist would miss the failure. Preserve the distinguishing input or refine the class before applying f.

Reversible conversion and partial normalization. For exact temperature values in the declared physical domain, Celsius-to-kelvin conversion n(c)=c+273.15 has inverse c=k-273.15 on its image. For example, 20 °C maps to 293.15 K and back to 20 °C. Measurement uncertainty remains governed by its measurement result; the exact coordinate law does not remove it. More generally, a strictly monotone encoding has an inverse on its image, not automatically everywhere in the named target.

Restrict the LUT above to D={0,1}. Input 2 is then undefined, has no NCV and belongs to no kernel class of that partial normalizer. A policy’s degraded-evidence allowance does not define n(2). Likewise, an idempotence claim needs composability and n(n(x))=n(x) on the named domain; a function’s fibers do not prove it.

Missing or stale inputs in a transformation flow.

  • A selector (or comparator) requires comparability under normalization-based mode.
  • UNM finds that a required coordinate value is missing/stale for the current slice and the instance validity window.
  • UNM returns GuardDecision = abstain (fail-closed) and identifies the missing current measurement. The receiver may reuse an adequate existing result, choose a justified acquisition, or leave this comparison unresolved; any acquisition has its own planning and enactment basis.

A.19.UNM:6 - Bias‑Annotation

Common cognitive traps around normalization:

  • Normalization-as-truth bias: treating an NCV as a justified answer before checking its input basis, transformation and receiving-use conditions.
  • Hidden-steps bias: assuming normalization “happened somewhere” and skipping routing/pins.
  • Unit-blindness: treating numeric sameness as semantic sameness.
  • Proxy legitimacy: assuming a popular method is legitimate without evidence pins or validity region.

Mitigation: enforce NormalizationMethodInstance + validity window + evidence pins; and distinguish the directed output, optional classes and any separately justified operation or query on them.

A.19.UNM:7 - Conformance Checklist

  • Normalization identity: cite the selected method and configured instance, its description, invariants and any representative-fixing rule. Resolve legacy identifiers through F.18 when used. An ordinary coordinate mapping does not assert a specialized Map kind or a Bridge; apply the lexical distinction in §4.0.
  • CN routing: uses CN_Spec.comparability.mode and the CN_Spec.normalization surface; does not embed “shadow CN-spec”.
  • Fail-closed: eligibility is tri-state and never coerces unknown to pass.
  • Lawfulness classes declared: method class is one of {ratio:scale, interval:affine, ordinal:monotone, nominal:categorical, tabular:LUT(+uncertainty)} and the instance’s validity window is named.
  • No indicator conflation: does not treat NCV as automatically implying indicator status.
  • Relation and reuse discipline: recover each NCV’s method and CN-Spec editions, bearer, basis, evidence, intended comparison and qualifications. Any relied-on relation and its receiving use satisfy UNM-L5; an assurance penalty has a justified domain model.
  • Result branch: the domain, directed output and preserved/lost distinctions are explicit. An inverse is claimed only on its stated image. A set quotient uses equality of function outputs on that domain; an inherited operation also passes compatibility and partial-availability checks, and a recovered query is constant on each class. A required representative has a declared fix and is not treated as the lost original input.
  • Auditability: the inputs, method and specification editions, evidence, conditions, result or reason for abstaining, and any relied-on relation are recoverable under Audit in §4.1. A separate record is retained when required by the receiving use.
  • Source references: downstream uses cite the method, basis and evidence editions they need, preserving the source definitions.
  • Missing or stale inputs: apply the declared abstain/degrade rule and name the gap. An undefined transformation input has no NCV. Reuse an adequate existing basis or plan a justified acquisition under its own method; normalization alone mandates no new Work.
  • SlotKind discipline: SlotKind tokens reuse the CHR SlotKind lexicon where applicable; UNM‑specific SlotKinds are docked into the suite lexicon before use (no ad‑hoc drift).

A.19.UNM:8 - Common Anti‑Patterns and How to Avoid Them

  1. Hidden normalization inside scoring or selection Avoid this by using CN_Spec.comparability.mode and applying UNM.

  2. “NCV ⇒ indicator” shortcut Avoid by treating indicatorization as UINDM policy, not a byproduct of normalization.

  3. “We normalized” without declaring invariants Avoid by naming the domain, transformation, preserved invariants and lost distinctions; supply a class or congruence claim only under its additional conditions.

  4. Reusing a normalized value after its basis changed Recover the bearer, method and CN-Spec editions, comparison basis, evidence, intended use and scope/window. Recheck the conditions that changed, including any relation required by the new use.

  5. Choosing a representative implicitly Avoid by either keeping quotient objects abstract or declaring NormalizationFix.

  6. Treating a generic mapping word as a specialized relation claim State the normalization’s operands, rule, invariants and loss. Test any specialized Map or F.9 Bridge claim separately under its defining pattern.

  7. Treating UNM outputs as comparable beyond their declared bearer, basis, scope/window, or reference plane Avoid by keeping comparison local to the recorded premises. Where a conclusion depends on another source-local meaning, bearer kind, or plane, cite the obtaining relation and its loss; otherwise constitute a new normalization result or fail closed.

  8. Re-authoring method, basis, or evidence anchors downstream Avoid by citing the editioned method, basis, and evidence anchors as refs; a downstream pattern neither rewrites them nor replaces them with a generic registry.

A.19.UNM:9 - Consequences

Benefits

  • Makes the selected normalization and comparison basis inspectable.
  • Separates the common operation contract from each method’s definition and applicability.
  • Allows a method family to change without changing the common operation contract when its meanings and conditions remain compatible.
  • Makes known admission failures explicit through the declared guard result; correctness still depends on the grounds used by the evaluation.

Costs

  • Requires declarations (method instance, invariants, validity window, evidence pins).
  • Class-level use requires compatibility/query arguments; ordinary transformed-value use need not construct a quotient or fix.

A.19.UNM:10 - Rationale

UNM separates three contributions needed to justify a normalized value:

  • The selected transformation defines its domain, output and preservation/loss conditions.
  • CN-Spec states when normalization is needed and which configured method applies to the comparison.
  • C.16 supplies measurement and calibration grounds for that use.

The receiving use determines which distinctions must survive and whether a relation to another meaning, kind or plane is required. Those relations and any assurance calculation retain their own conditions; a common numeric range supplies none of these grounds.

A.19.UNM:11 - SoTA-Echoing — preserve the answer needed after normalization

Practice question. May a receiver answer its original query from normalized values after the transformation merges inputs? The selected mathematical condition checks whether that query is constant on each fiber of the declared function. An alternative keeps only bounded normalized values and uses a representative or inverse-transform interface for later queries. The latter is convenient when the receiver deliberately accepts the lost distinctions; it is insufficient for recovering an exact original-input answer that differs within a fiber.

The Lean reference on quotients supplies the mathematical line: lifting a function requires equal results for equivalent representatives. It also describes canonical-representative implementations as a useful alternative representation. Adopt the query-constancy criterion in §4.0, UNM-L2 and §4.4. Reject the inference that choosing a representative recovers an original-input query: the representative defines a choice, and recovery still needs constancy. These are mathematical conditions; using Lean or constructing a proof-assistant artifact is not required by UNM.

The scikit-learn 1.9 MinMaxScaler documentation supplies a preprocessing alternative and its declared trade-off. Optional clipping keeps held-out values in the chosen range, while its documentation warns that inverse transformation may not restore the original data and that clipping can distort the test distribution. Adapt this loss disclosure as a receiving-use check, rather than banning bounded preprocessing or treating the software interface as evidence of invertibility.

For example, a declared clipped transform n(x)=min(1,max(0,x/100)) sends 120 and 150 to 1. The query “was x above 130?” gives different answers, so it cannot be recovered from that NCV or its class representative. Keep the original value, refine the output with the needed distinction, or return the unresolved answer allowed by the receiving rule. This is the same test used by the finite-domain example in §5 and the Result branch checklist; separately inherited partial operations also retain their availability check.

At comparable effort, both choices use the same declared transform and query. One counterexample within a fiber can settle failure cheaply; a positive exact-recovery claim needs a constancy argument over the admitted domain, not just sampled successes. Keeping additional input information has a storage/handling cost, while clipping can be appropriate for a model that only needs its bounded input. The chosen rule makes that trade-off explicit and leaves ordinary transformed-value use cheap. Reopen when the receiver changes its query, the transformation or domain changes, or a proposed smaller representation retains the required answer with a sound argument. Neither software documentation nor the quotient theorem supplies measurement legitimacy, evidence sufficiency or assurance for an application.

A.19.UNM:12 - Relations

Builds on / cites

  • E.8 (pattern template)
  • E.20 for introduction or revision of a mechanism definition and its governing-pattern assignment
  • A.15.2 for the edition/reference baseline on a P2W path; A.15.3 only for typed planned filling of an independently declared position
  • F.18 (alias docking / token continuity, when renaming or retiring legacy UNM tokens)
  • A.6.1 (U.Mechanism shape; specialization discipline)
  • A.19.CHR (CHR suite boundary; slot lexicon; suite protocols)
  • A.19.CN (CN_Spec normalization + comparability routing)
  • C.16 (MM‑CHR evidence/calibration carriers)
  • G.0 (CG-Spec admissibility and evidence conditions used downstream)
  • G.2 (SoTA synthesis packs as the method‑family ingress; wiring‑only integration)
  • E.18 (when UNM is used in transformation-flow structures/graphs; P2W freshness/work routing)
  • C.29 when the chosen function, equivalence or quotient leaves an unresolved representation or transfer question; use an adequate local calculation. B.3 applies to a named assurance claim.

Used by

  • CHR suite protocols (normalize stage), when comparability.mode requires normalization-based comparability.

A.19.UNM:End

A.19.UINDM - Indicatorization: Select Indicators Under a Declared Policy

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative)

Use this when a receiving comparison, score or dashboard needs a declared choice of indicator positions from an existing CharacteristicSpace. Start with that receiving question and the selection policy, then resolve its chosen positions and Scales. Reuse an already adequate selection while its basis and intended use remain applicable; a measurement alone need not introduce indicatorization.

A.19.UINDM:0 - At a glance (didactic, informative)

  • Suite stage: indicatorize (ordering lives only in A.19.CHR:suite_protocols).
  • Inputs (conceptual): CharacteristicSpaceRef, CNSpecRef, and IndicatorChoicePolicyRef, with the bearer, claim scope and selected slices, qualification window, evidence basis, and intended use declared by those editions; when the selected policy is evidence-gated, also supply CGSpecRef and, optionally, a MinimalEvidenceRef override.
  • Output: IndicatorSetSlot = S⊆I, a set of positions in the A.19 space declaration’s ordered basis I. Each position retains its Characteristic, Scale and meaning. The selection is not a measurement or conversion.
  • Non‑goals: does not normalize, score, compare, aggregate, threshold, publish, or emit telemetry; it only selects a subset under explicit policy.
  • P2W seam: the A.15.2 baseline records space/spec/policy editions; A.15.3 typed filling applies only to independently declared positions. Actual use retains its effective refs and pins in Audit.
  • Failure mode: tri‑state guard (pass|degrade|abstain); unknown never coerces to pass.
  • Quick rule of thumb: if CN‑Spec.indicator_policy is absent → IndicatorizeEligibility = abstain (fail‑closed); if the selected policy is evidence‑gated → CGSpecRef MUST be available and the effective MinimalEvidence MUST be explicit (override or CG‑Spec.MinimalEvidence).

A.19.UINDM:1 - Problem frame

FPF’s Characterization (CHR) suite treats indicatorization as a mechanism boundary (authoritative membership: A.19.CHR:4.2). Suite membership is a set (order has no semantics); any intended ordering is expressed only via suite_protocols (A.19.CHR:4.5), under the suite obligations (A.19.CHR:4.3).

Within the canonical suite‑closed protocol, UINDM appears as the indicatorize stage (after normalize, before score/compare/select; optional stages remain optional per suite_protocols).

UINDM is governed by CN-Spec and, for an evidence-gated policy, CG-Spec: it selects an indicator subset over an existing DeclaredCharacteristicSpace under CN‑Spec.indicator_policy, using the suite-wide SlotKind lexicon to prevent SlotKind drift across the CHR mechanism chain and across SoTA wiring modules. A “subspace view” (if needed) is treated as a derived support view over the chosen set (see A.19.UINDM:4.2), not as an extra mandatory output of the kernel signature.

A.19.UINDM:2 - Problem

Engineering teams routinely need to decide “which characteristics count as indicators” for a CN‑frame—when a downstream score, comparison, aggregation or selection depends on that choice. Leaving the choice implicit can produce these failures:

  • Hidden indicatorization: downstream mechanisms (scoring/comparison/selection) implicitly decide which characteristics matter, making the CHR pipeline opaque and hard to audit.
  • NCV conflation: measurability (or “having an NCV”) is treated as sufficient to be an indicator, collapsing the distinction between “measurable characteristic” and “indicator chosen under policy.”
  • Drift and non-determinism: indicator sets vary between teams, bearer classes, source or corpus editions, windows, and intended uses without stable policy and basis pins, making comparisons and decisions irreproducible.
  • Silent evidence coercion: missing/unknown evidence is implicitly treated as acceptable (“pass”) or collapsed to an empty set, degrading decision quality without visibility.

A.19.UINDM:3 - Forces

  1. Policy primacy vs method freedom. Indicatorization must be governed by explicit IndicatorChoicePolicy, while still allowing multiple method families (e.g., theory‑first, invariance‑driven, evidence‑gated) to be wired later without mutating the mechanism’s signature.

  2. Selection‑only vs “semantic alchemy.” UINDM must not smuggle normalization, scaling, polarity flips, aggregation, or scoring inside “indicator choice.” It is a selection mechanism over the declared characteristic-space basis, not a transformation mechanism.

  3. Declared-use locality vs reuse. An indicator set is valid for its characteristic space, its separately referenced description episteme and the CN-Spec edition, bearer, scope and window, evidence basis, policy, and intended use; a later use must recheck those premises and cite any source-local, kind, or plane relation it relies on.

  4. Auditability vs authoring overhead. Engineer‑managers need to see why an indicator set was chosen and which editions/policies were in effect, but FPF stays conceptual (no data governance, no tool‑enforced metadata). Audit obligations must therefore be minimal yet decisive.

  5. Fail‑closed discipline. Unknown/insufficient evidence must never be coerced into “pass”; tri-state guards (pass|degrade|abstain) state the policy’s disposition of uncertainty; their correctness still depends on the evidence and rule used.

  6. P2W separation and gate/guard separation. UINDM must expose eligibility and audit pins without turning into (i) a WorkPlanning baseline binder or (ii) an admissibility gate: planned slot fillings belong to WorkPlanning plan items, while GateDecision/GateLog live in gate patterns / WorkEnactment (suite protocols remain mechanism‑steps only).

A.19.UINDM:4 - Solution

Resolve the indicator policy against the characteristic-space basis and return the selected positions with their Characteristic, Scale and original relative order. Keep their values unchanged. If the policy is absent or an action-changing match remains unresolved, apply the declared abstain behavior. An evidence-gated policy also needs its CG-Spec and effective MinimalEvidence.

Use the operation and guard declarations below for eligibility and bindings. Audit keeps the selected editions and the bearer, scope/window, evidence basis and intended use needed for replay. A receiving use adds relation references only for relations it relies on. Gate decisions, publication and telemetry follow their own patterns; methods for choosing indicators can be supplied through G.2 and extension declarations.

A.19.UINDM:4.1 - Operation declaration (normative)

UINDM.IntensionRef cites the A.6.1 U.Mechanism declaration episteme presented here. CHR selects that declaration and its edition; its indicatorize stage resolves to the local Indicatorize operation. A changed basis-selection law or eligibility rule requires selection of the changed declaration, while another realizer of the same declaration changes no suite member.

  • Scope note: A.6.1 governs this declaration’s operations, arguments, results, application identities and laws. An A.15.2 plan can select its editions; typed filling under A.15.3 is needed only for an independently declared receiving position. Application bindings are governed below. Indicatorization returns S; its guard and audit remain separate from GateDecision/GateLog.

  • IntensionHeader: id = UINDM, version = 1.0.0, status = stable.

  • IntensionRef: UINDM.IntensionRef (canonical target for the suite member named in A.19.CHR:4.2).

  • Tell. Policy‑bound indicatorization: select an indicator subset over an existing DeclaredCharacteristicSpace under CN‑Spec.indicator_policy.

  • Purpose: freeze a policy‑bound indicator subset early so downstream CHR mechanisms can assume a declared indicator profile (or degrade/abstain) rather than silently “choosing indicators” inside scoring/comparison/selection.

  • Imports: A.19.CN (CN‑Spec.indicator_policy), A.6.1 (operation declarations and actual bindings), A.19.CHR:4.2.1 (CHR SlotKind Lexicon), and (when evidence‑gated) G.0 (CG‑Spec.MinimalEvidence).

  • SubjectBlock:

    • SubjectKind: DeclaredCharacteristicSpace, supplied by CharacteristicSpaceSlot.
    • RangedValueKind: declaration-local basis positions of that space. Indicatorize selects from them; IndicatorizeEligibility assesses their selection under the policy.
    • SliceBasis: the declared U.ClaimScope and its selected U.ContextSlice members, together with the qualification window and intended use.
    • Input qualification: indicatorization ranges over the declared characteristic-space basis CNSpecSlot.cs_basis (within CNSpecSlot.chart) for the bearer, claim scope and selected slices, qualification window, evidence basis, and intended use; it never enlarges that basis.
    • Result kinds are declared per operation: a finite basis-position subset and a separate guard judgment.

Space range and resolution. Use the DeclaredCharacteristicSpace criterion and paired reference resolution in A.19:5.1.1.1. CharacteristicSpaceRef selects the space; CN_Spec.characteristicSpaceDescriptionRef: U.EpistemeRef pins the description supplying its basis. Both must resolve and agree on that space before indicatorization; otherwise the dependent use remains unresolved and eligibility abstains. Membership establishes the input’s space structure; the selected operation must still resolve its positions, Scales and applicable use conditions.

A changed basis requires a new space reference and position resolution, even if its label or document path is unchanged. Preserve the preceding space, description and results; reuse requires the correspondence and operation conditions of the receiving use.

Operation-local declarations

Each argument row declares the same meaning separately for Indicatorize and IndicatorizeEligibility. References identify one value under the declaration’s effective reference scheme. An episteme reference selects its edition; the space reference and its separate description-episteme reference follow the rule above.

Cardinalities below are for Indicatorize; the guard can assess a proposal with a missing required argument, which then has no binding and yields abstain.

DirectionLocal designatorMeaning and ValueKindDesignation; cardinality
ArgumentCharacteristicSpaceSlotDeclaredCharacteristicSpace whose basis I supplies the candidate positions, their Characteristic and ScaleCharacteristicSpaceRef; 1
ArgumentCNSpecSlotCN-Spec used to delimit that basis and the bearer, scope/slices, qualification window and intended useCNSpecRef; 1
ArgumentIndicatorChoicePolicySlotIndicatorChoicePolicy whose rules select positions in I and govern unresolved choices and evidence failureIndicatorChoicePolicyRef; 1
ArgumentCGSpecSlotCG-Spec supplying evidence conditions when the selected policy is evidence-gatedCGSpecRef; 0..1, required for evidence-gated use
ArgumentMinimalEvidenceSlotMinimalEvidence override used instead of CGSpecSlot.MinimalEvidence when supplied in evidence-gated useMinimalEvidenceRef; 0..1
Indicatorize resultIndicatorSetSlotFinite subset S of the space declaration’s basis-position set IByValue; 1 on an admitted resolved selection, 0 on abstain
IndicatorizeEligibility resultGuardDecisionPolicy-governed eligibility judgment: pass, degrade or abstainByValue; 1 on completed evaluation

For each argument, its bindingPredicate holds when this application uses that resolved value in the stated role: the space supplies I, the CN-Spec delimits the use, the choice policy supplies the selection or eligibility rule, and any evidence arguments supply the effective evidence condition. An unused evidence reference in a non-evidence-gated use creates no binding. For the guard, each required argument has cardinality 0..1 so that missing inputs can be assessed; absent inputs cannot be counted as bindings.

The IndicatorSetSlot bindingPredicate holds when that Indicatorize application returns S after applying the bound policy to the bound basis under the admitted use; the laws below govern S. The GuardDecision bindingPredicate holds when that IndicatorizeEligibility application returns the judgment determined by its stated predicates. A compatible set or guard value copied into an audit entry establishes neither return.

A.6.1 identifies each binding by the application, local declaration, value and continuous binding extent; input extents are within the selection/evaluation episode and result binding begins at return.

SlotIndex (derived projection). The argument/result designators, ValueKinds, designation modes and cardinalities in the table are its sole source. Their historical Slot names support CHR lookup; A.6.5 relation SlotSpecs do not define operation arguments.

  • OperationAlgebra (suite stage = indicatorize, per A.19.CHR:4.5; canonical stage‑op = Indicatorize):

    • Indicatorize(CharacteristicSpaceSlot, CNSpecSlot, IndicatorChoicePolicySlot, CGSpecSlot?, MinimalEvidenceSlot?) → IndicatorSetSlot; the space declaration supplies I and each position’s Characteristic, Scale and meaning. Resolve any policy stated by Characteristic criteria to positions before returning S. If several positions match, apply the declared choice or all-matches rule; without a resolving rule, return the policy’s unresolved/abstain disposition rather than select an arbitrary position. ApplicationPredicate. Indicatorize obtains when a selection episode resolves the bound policy against the bound space’s basis positions for the CN-Spec use and determines S. It proceeds on pass, or on degrade only when that policy permits a degraded selection; abstain yields no S. IndicatorizeEligibility obtains when a separate evaluation episode assesses those inputs under the eligibility predicates and determines its GuardDecision. A planned choice or a passing guard is not an Indicatorize episode.

ApplicationIdentityRule. Each operation’s occurrence is one selection or eligibility-evaluation invocation at its calculation locus, starting when it takes up its arguments and ending at return or termination. Two references to that same episode identify one application. Taking up the same values and policy for a second calculation identifies another, even when both return the same S or judgment. Replacing the input basis or policy for a fresh calculation likewise begins another application; a copied result begins none.

ApplicationExtentRule. Indicatorize extends from taking up the basis/policy for selection through return of S or termination without S; IndicatorizeEligibility extends from taking up the proposal for assessment through judgment or termination. An unfinished episode has an open extent and no unreturned result binding. These are the calculation extents, which can differ from the selected data window. An invocation reference designates that episode only when its identity is established; no U.Work claim follows from ordinary selection or projection mathematics.

For example, select Celsius temperature twice from CS7 under the same policy in §5.4. Each completed selection returns {i1}, but the two operand-to-return episodes and their result bindings are distinct. An audit record copied from the first episode can describe its result; it cannot establish a result binding for the second without the second return. Re-reading the first record also creates no new selection application.

  • LawSet (CHR‑lawful indicatorization):

    1. Selection‑only: Indicatorize MUST NOT alter units, scales, and polarities; it only selects a subset (no implicit UNM).
    2. Declared-basis restriction: return S⊆I for the A.19 basis of the resolved space, with its description episteme and CN-Spec edition selected separately. The projection x|_S retains the selected positions’ original relative order, Characteristic, Scale and meaning. Re-resolve the policy after a basis change; naked indices from the preceding declaration do not identify positions in the new one.
    3. No implicit NCV⇒indicator: measurability/NCV is not sufficient; indicators exist only via IndicatorChoicePolicySlot (cites A.19.CN indicator_policy).
    4. Fixed-input determinism for the declared use: for one resolved CharacteristicSpaceRef, its separate characteristicSpaceDescriptionRef, and fixed editions of the remaining ByRef inputs (CNSpecRef, IndicatorChoicePolicyRef, and—when evidence-gated—CGSpecRef plus optional MinimalEvidenceRef), with fixed bearer, claim scope and selected slices, qualification window, evidence basis, and intended use, the IndicatorSetSlot result is stable.
    5. No silent evidence coercion: if evidence is insufficient/unknown under the chosen policy, the result MUST NOT be “silently emptied” nor silently treated as “pass”; use tri‑state guards.
  • AdmissibilityConditions (tri‑state guard; fail‑closed on missing admissibility/evidence):

    • IndicatorizeEligibility(CharacteristicSpaceSlot, CNSpecSlot, IndicatorChoicePolicySlot, CGSpecSlot?, MinimalEvidenceSlot?) → GuardDecision ∈ {pass|degrade|abstain}.
    • pass requires: (i) CNSpecSlot.indicator_policy is present, (ii) IndicatorChoicePolicySlot matches that policy reference and edition, (iii) CharacteristicSpaceSlot matches the declared characteristic-space basis and its required description reference resolves to the episteme supplying that same basis, and (iv) that policy’s eligibility conditions hold for the bearer, claim scope and selected slices, qualification window, evidence basis, and intended use.
    • If the chosen IndicatorChoicePolicy is evidence‑gated: (i) CGSpecSlot MUST be present, (ii) define EffectiveMinimalEvidence := (MinimalEvidenceSlot if present, else CGSpecSlot.MinimalEvidence), and (iii) insufficient/unknown evidence MUST yield degrade or abstain per the effective failure‑behavior policy (never a silent pass).
    • If the chosen IndicatorChoicePolicy is not evidence‑gated, absence of MinimalEvidenceSlot MUST NOT affect eligibility; no accidental “always‑evidence‑gated” behavior is permitted.
  • Applicability:

    • Intended to be used before any scoring/comparison/selection that assumes an indicator profile, while remaining a distinct step (no hidden indicatorization inside downstream mechanisms).
    • Reuse for another bearer, source-local meaning, scope and window, evidence basis, reference plane, or intended use requires a new eligibility decision. Cite an F.9 Bridge, kind relation, or plane relation only when the new use relies on it.
    • Pin-binding note: a P2W path records intended policy editions in its planned baseline. Every application consumes resolved references and keeps the effective ones in Audit; a direct use needs no invented WorkPlan.
  • Relation boundary: indicatorization creates no transfer relation. When a receiving use relies on an obtaining F.9 Bridge, kind relation, or plane relation, cite it with direction, preserved or lost meaning, and receiving use; assess loss for the receiving use and apply any numerical assurance penalty under A.6.7:4.2(2).

  • Γ_timePolicy: point by default (no implicit “latest”).

  • PlaneRegime: the indicator set keeps the reference plane declared by the characteristic space, its separately referenced description episteme and the CN-Spec edition; UINDM introduces no plane shift. When a receiving conclusion depends on a relation between different planes, cite that plane relation, its direction and loss, and keep its use separate from the indicator set.

  • Audit:

    • MUST record the following values when resolved: CharacteristicSpaceRef, the separate characteristicSpaceDescriptionRef: U.EpistemeRef pinned in CN-Spec, CNSpecRef.edition, IndicatorChoicePolicyRef.edition, bearer, claim scope and selected slices, qualification window, evidence basis, and intended use. Identify any required value that remains missing or unresolved.
    • When evidence‑gated, MUST record the following when resolved: CGSpecRef.edition and effective MinimalEvidence (MinimalEvidenceRef when provided; otherwise CGSpecSlot.MinimalEvidence).
    • SHOULD record: the realized GuardDecision (pass|degrade|abstain) and, when non‑pass, the policy‑bound failure behavior reference that justified it.
    • SHOULD record: a stable description of IndicatorSetSlot (or an id reference to a citable indicator-set publication unit), plus any F.9 Bridge, kind relation, or plane relation only when the result or receiving use relies on it.

A.19.UINDM:4.2 - Interpretation notes (informative)

  • IndicatorSet selects basis positions. A Characteristic reference can match several positions with different Scales. S identifies the selected positions in the space declaration; each resolves uniquely through that basis. Obtain or reuse their values under the corresponding measurement/evaluation rule and retain the position and Scale in the profile. UINDM computes no measurement or conversion.

  • Subspace views are derived, not mandatory. If a project needs a subspace view, treat it as a derived support view CS|_S, with S = IndicatorSetSlot over the base CS = CharacteristicSpaceSlot. Restrict its ordered basis and any state x|_S to S without reordering the retained positions. Do not add a new mandatory output to the kernel signature; declare a separate support-view result only when needed, and justify any extension claim under §7 item 9.

  • Justification is optional and externalized. The CHR SlotKind lexicon includes JustificationSlot, but the canonical UINDM intension does not require it. If a project needs a separately declared justification output, specify the additional result and test the claimed extension under §7 item 9, and model the justification as a justification U.Episteme (e.g., JustificationSlot : ⟨ValueKind = U.Episteme, refMode = U.EpistemeRef⟩).

  • Evidence-gated indicatorization is explicit. Evidence gating is activated only by the chosen IndicatorChoicePolicy. In that case CGSpecSlot is required and the effective MinimalEvidence is explicit: use MinimalEvidenceSlot when supplied, otherwise CGSpecSlot.MinimalEvidence. The override remains optional.

A.19.UINDM:5 - Archetypal Grounding (informative)

A.19.UINDM:5.1 - Tell

Use UINDM to select the basis positions for a policy-bound projection:

  • Input: “the declared characteristic basis for this bearer, claim scope and selected slices, qualification window, evidence basis, and intended use, plus an explicit indicator choice policy”
  • Output: “the selected positions of this basis, each retaining its Characteristic, Scale and meaning for downstream use”

UINDM selects basis positions. A projection to those positions retains their coordinate values and Scale meanings.

A.19.UINDM:5.2 - Show (U.System) — cross‑unit engineering dashboard

A program manager maintains a DeclaredCharacteristicSpace for manufacturing sites, including ~30 characteristics (quality, safety, cost, throughput, sustainability).

  • The CN‑Spec’s indicator_policy for the “weekly executive dashboard” selects a subset: {DefectRate, IncidentRate, UnitCost, LeadTime, EnergyPerUnit, OnTimeDelivery}.
  • In this example each named Characteristic has one basis position. UINDM resolves the six names to those positions and returns S; each position retains its original Scale.
  • One site lacks reliable incident reporting for the last week. This example’s evidence-gated policy permits retaining the fixed six-position set under degrade, with that gap explicit. IndicatorizeEligibility therefore returns degrade, and the audit retains the effective MinimalEvidence and edition pins. The selected IncidentRate position supplies no missing value; a downstream comparison depending on that value follows its own insufficient-evidence rule.

Downstream mechanisms can now be held to the invariant: they may only score/compare/select using the declared indicator profile (or abstain/degrade). This avoids “dashboard drift” where different teams silently score on different subsets.

A.19.UINDM:5.3 - Show (U.Episteme) — robust evaluation across environments

A research lead wants indicators for model robustness under distribution shift (different hospitals, sensors, geographies).

  • The declared characteristic-space basis includes many candidate metrics (accuracy slices, calibration, subgroup error, OOD detection quality).
  • The indicator choice policy is “invariance-driven”: prefer indicators whose meanings remain applicable across the selected environments; deprioritize proxies with an established environment-sensitive interpretation. For example, a constructed policy retains subgroup-error positions only when the subgroup definition, target label and error criterion match the intended comparison in each environment.
  • UINDM returns the positions resolved by that policy. An action-changing unresolved match yields no selection. Once the positions are resolved, insufficient evidence follows the declared degrade/abstain rule. Keeping the same error definition does not establish stable model performance under distribution shift; the later evaluation needs the values and evidence for that claim.

A.19.UINDM:5.4 - One Characteristic at two Scale positions

Let the space declaration CS7 have ordered positions i1=(Temperature, Celsius) and i2=(Temperature, kelvin), followed by an unrelated cost position. A state contains x_i1=20 °C and x_i2=293.15 K. The policy “select Celsius temperature” returns S={i1}. The all-matches policy “all Temperature positions” returns {i1,i2}, with x|_S in the original order and both Scale meanings retained. UINDM converts neither value. This use retains the reference to CS7 and a separate characteristicSpaceDescriptionRef to the episteme defining that basis.

For the first policy, a separately admitted USCM scoring use can read the Celsius value under its declared method g_C(c)=(c-0)/(40-0) on Celsius interval [0,40], returning 0.5 at 20. The interval endpoints are part of this illustrative scoring declaration. Supplying 293.15 as though it were Celsius violates that method’s input basis; a TemperatureRef alone would not reveal the error. All-matches selection requires a receiving method that accepts those two Scale-specific positions, or a narrower selection; it is not a universal default.

Suppose a different space CS8 reverses these two positions. Select CS8 and its description episteme, preserving CS7, its description and the earlier result. Resolving “Celsius temperature” now selects its CS8-local position i2. Reusing CS7’s naked integer 1 would select kelvin and is invalid. If the policy says “Temperature” and supplies no rule for the two matches, return its unresolved/abstain disposition. A missing indicator policy retains the defined abstain result, and evidence gating still applies only when the selected policy requires it.

A.19.UINDM:6 - Bias-Annotation (informative)

  • Gov (governance). Bias toward explicit policy surfaces (IndicatorChoicePolicyRef, edition pins, auditable outcomes) rather than tacit “expert choice.” Risk: perceived extra work. Mitigation: keep the mechanism minimal (selection‑only) and push method detail into wiring modules.

  • Arch (architecture). Bias toward stable interfaces: SlotKind tokens come from the suite lexicon and evidence gates are explicit inputs. Risk: reduced “quick hacks.” Mitigation: allow ⊑⁺ extensions for additional outputs (e.g., justification) without mutating the kernel signature.

  • Onto/Epist. Bias toward a distinction between “measurable characteristic” and “indicator under policy.” Risk: teams accustomed to “everything measurable is an indicator” may resist. Mitigation: embed this as a LawSet clause (“No implicit NCV⇒indicator”).

  • Prag (pragmatics). Bias toward fail‑closed guards and traceability under uncertainty. Risk: more abstain/degrade outcomes early. Mitigation: couple degrade with explicit downstream behaviors (policy‑bound) rather than silent coercions.

A.19.UINDM:7 - Conformance Checklist

A UINDM publication or use is conformant if it satisfies:

  1. A.6.1 declaration completeness. Indicatorize and the separately reused IndicatorizeEligibility have local argument/result declarations, obtaining predicates and application identity/extent rules. Their declared selection and guard laws hold; SlotIndex projects those declarations. A binding requires the value used or returned by the identified application, not a compatible audit record.

  2. SlotKind discipline. SlotKind tokens match the CHR SlotKind lexicon for the roles used (CharacteristicSpaceSlot, CNSpecSlot, IndicatorChoicePolicySlot, etc.); no generic ContextSlot is introduced. New SlotKinds, if any, first extend the suite lexicon rather than appearing ad hoc in the mechanism.

  3. Selection-only behavior. Indicatorize returns positions in the declared basis, retaining their Characteristic, Scale and meaning. A projected state keeps their original relative order. There is no implicit normalization or enlargement. After a basis change, resolve the policy again rather than reuse naked indices.

  4. No NCV shortcut. “Measurable/NCV” is not treated as sufficient for indicatorhood; indicatorhood arises only via IndicatorChoicePolicySlot consistent with CN‑Spec.indicator_policy.

  5. Evidence gating is explicit. When the chosen IndicatorChoicePolicy is evidence‑gated, CGSpecSlot is present and the effective MinimalEvidence is explicit and auditable (MinimalEvidenceSlot when provided; otherwise CGSpecSlot.MinimalEvidence); insufficient/unknown evidence must yield degrade/abstain per the effective failure‑behavior policy, never a silent pass.

  6. Recheck eligibility for reuse. Another bearer, scope and window, basis, plane, or intended use gets a fresh eligibility decision; any F.9 Bridge, kind relation, or plane relation is cited only when the conclusion relies on that obtaining relation, with loss assessed under the receiving-use rule and any numerical assurance penalty applied under A.6.7:4.2(2).

  7. Gate/guard separation + lexeme discipline. UINDM uses …Eligibility returning GuardDecision ∈ {pass|degrade|abstain} and does not embed GateDecision/GateLog in suite steps. Reserved gate‑lexemes (e.g., …Guard) are not used for indicatorization eligibility predicates.

  8. Planning and actual use. On a P2W path, an A.15.2 WorkPlan selects the intended editions; A.15.3 governs typed filling only for independently declared positions. Record the application and its effective bindings under §4.1, keeping the refs and pins needed for replay in Audit.

  9. Extension discipline (if extended). A proposed UINDM specialization MUST preserve the inherited SlotKind designators and their meanings, add no mandatory input to Indicatorize, and declare any additional output or operation (the local extension notation is ⊑⁺). A refinement, conservative-extension or equivalence claim additionally uses its own A.6.1 §4.8 preservation test and comparison predicate; those three claims are not interchangeable. Preserve inherited application/binding meanings, identity and extent to the degree required by the claimed comparison, and retain narrowed applicability or stronger conditions explicitly. A missing comparison predicate or substrate returns the applicable A.6.RCD gap.

For example, an extended Indicatorize may add an optional justification result while retaining the original inputs and selected-position result. To claim a conservative extension, establish that every inherited admitted use, result and application/binding rule remains as specified; the new output has its own declaration. Making a new explanation input mandatory fails the local restriction. A label such as ⊑⁺ does not settle the comparison: use the admitted comparison relation or A.6.RCD’s case-specific claim branch under A.6.1 §4.8, returning its missing-governor/substrate gap if necessary.

A.19.UINDM:8 - Common Anti‑Patterns and How to Avoid Them

  • “NCV ⇒ indicator.” Treating all measurable characteristics as indicators. Violates “No implicit NCV⇒indicator.”

  • Indicatorization hidden in scoring. A scoring method silently ignores some characteristics or introduces an implicit “feature selection” without an explicit indicator set.

  • Characteristic reference substituted for a position. Temperature occurs at Celsius and kelvin positions, but the returned set contains only TemperatureRef. Resolve the policy to the requested position or its selected all-matches set before returning S.

  • Silent emptying. When evidence is insufficient, returning an empty indicator set (or treating missing evidence as “pass”) without a tri‑state guard decision.

  • Reusing an indicator set after its basis or use changed. Reusing it for another bearer, scope and window, evidence basis, reference plane, or intended use without a new eligibility decision; or naming Bridge or plane-relation pins without an obtaining relation.

  • Confusing planning with an application. A description of intended editions or planned fillings does not establish argument bindings or launch values. Keep the P2W baseline separate and record effective application references in Audit.

  • GateDecision leakage. Emitting or implying GateDecision/GateLog as part of the indicatorize step.

A.19.UINDM:9 - Consequences

Benefits

  • Makes the selected indicator basis explicit, auditable and policy-bound, so downstream changes can be detected and assessed.
  • Supports reproducibility under the complete fixed-input conditions of the edition-determinism law; edition labels alone are insufficient.
  • Preserves evolvability: new indicator selection method families can be added via wiring (packs/extensions) without changing the mechanism’s intension.

Costs / trade‑offs

  • Adds an explicit step (and explicit policy work) before scoring/comparison.
  • Fail‑closed behavior can increase early degrade/abstain outcomes until evidence and policies are properly specified.

A.19.UINDM:10 - Rationale

Indicatorization is separated because it answers a different question from scoring or comparison:

  • Indicatorization determines which coordinates may be used under the indicator-selection policy.
  • Scoring, aggregation, and comparison determine how those coordinates are transformed, combined, or ordered under their admissibility conditions.

By making indicatorization selection‑only, UINDM avoids “semantic alchemy” (changing meanings while claiming to merely “pick indicators”) and supports the CHR suite’s broader discipline: explicit specification references, any used crossing relations, and explicit handling of uncertainty via tri‑state guards.

A.19.UINDM:11 - SoTA-Echoing — choose indicators for their intended use

Practice question. Which coordinates should a dashboard or receiving method use when several available columns are plausible indicators? The selected line makes the phenomenon and intended use govern an explicit choice policy, then checks the selected positions and their Scale meanings. An alternative ranks available features by a statistical score and keeps the best k. That alternative is useful for its declared predictive or exploratory objective; its ranking alone does not decide which quantities a dashboard must report.

The European Commission JRC’s 10 Step Guide, steps 1–2, published as a navigation guide in March 2025, supplies the purpose-led line for composite indicators: define the conceptual basis and choose relevant, analytically sound, obtainable indicators. Adapt that ordering to CN-Spec.indicator_policy, the IndicatorChoicePolicy argument in §4.1 and the selection-only law. UINDM selects existing coordinates; the guide’s later normalization, weighting and aggregation steps belong to their separately declared mechanisms. The guide does not prove that any policy is adequate or stable under distribution shift.

The scikit-learn SelectKBest documentation supplies the statistical alternative: choose k features using a declared scoring function; equal scores can be resolved in an unspecified way. Adopt statistical selection when the intended use chooses that criterion, with the data, scoring rule and treatment of ties declared in the policy. Reject substituting a top-k result for an undeclared semantic choice. The documentation establishes the selector’s behavior, not the meaning or fitness of the selected indicators.

The two Temperature positions in §5.4 expose the distinction. Suppose the Celsius and kelvin columns receive equal statistical scores and k=1. Either could be retained under an unspecified tie rule, while the downstream Celsius scoring method accepts only the Celsius position. At comparable effort, the Celsius policy resolves the required input; when prediction is the objective, the statistical policy can instead choose a position and bind its Scale to an appropriate receiving method. This changes checklist items 3–4 in §7: retain the selected position, and resolve an action-changing tie by the policy or return its unresolved result. A promise that both columns concern Temperature is insufficient.

The trade-off: a purpose-led policy makes the required indicator meaning inspectable, but it does not by itself optimize prediction. A statistical policy needs data and a justified score, and its selected subset can vary with them. Neither approach permits UINDM to rescale values. Reopen the comparison when the receiving question changes, evidence shows that the selected indicators fail that question, or a rival policy preserves the needed meaning with better usefulness at comparable effort.

A.19.UINDM:12 - Relations

  • Builds on

    • A.19.CN (CN‑Spec, specifically indicator_policy).
    • A.6.1 §4.2 for operation-local declarations and §4.8 for the refinement, conservative-extension or equivalence comparison being claimed.
    • A.19.CHR:4.2.1 (CHR SlotKind lexicon).
  • Used by

    • A.19.CHR (suite membership and suite protocols; UINDM is the indicatorize stage).
  • Coordinates with

    • G.0 (CG‑Spec / MinimalEvidence) when indicator choice is evidence‑gated.
    • E.20 for the governing declaration and F.18 when resolving a legacy alias.

A.19.UINDM:End

A.19.USCM - Scoring Mechanism

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative)

Use this when admitted values need a declared valuation for comparison or selection. Select the scoring rule and recover its input basis, output meanings and permitted use before calculating. If the receiving comparison can use the admitted values directly, scoring is unnecessary.

USCM.IntensionRef identifies the U.Mechanism declaration in §4.1 under A.6.1. CHR resolves its score stage to the local Score operation; the declaration supplies the meanings and application/binding rules below.

A.19.USCM:0 - At a glance — didactic, informative

  • Suite stage: score (ordering lives only in A.19.CHR:4.5 / suite_protocols; suite membership is a set in A.19.CHR:4.2).
  • Inputs, conceptual: an admitted measure profile for the evaluated bearer, plus CNSpecRef, CGSpecRef, and ScoringMethodDescriptionRef; their editions name the criteria, comparison or reference basis, evidence policy, intended result use, and any claim scope, selected slices or qualification window that qualify that use. MinimalEvidenceRef may override the CG-Spec minimum.
  • Output: ScoreProfileSlot = a set of score measures (vector scores are first‑class; a scalar score is allowed only if declared).
  • Non‑goals: does not normalize (UNM), aggregate (ULSAM), compare (CPM), select (SelectorMechanism), issue a gate decision, publish, or emit telemetry; it is a scoring step with explicit admissibility and evidence surfaces.
  • P2W seam: an A.15.2 baseline selects editions and policies, including ScoringMethodDescriptionRef when USCM is used. A.15.3 typed filling applies only to independently declared receiving positions under A.19.CHR:4.7.2. Score bindings obtain under §4.1; Audit makes the effective refs and pins recoverable.
  • Failure mode: tri‑state guard (pass|degrade|abstain); unknown never coerces to pass, and MUST NOT be coerced to 0/false.
  • Quick rule of thumb: if CGSpecSlot.SCP is missing → ScoreEligibility = abstain (fail‑closed); if ScoringMethodDescriptionSlot is missing → ScoreEligibility = abstain (no implicit scoring method); if CN‑Spec.comparability requires normalization‑based comparability → normalization MUST be explicit in choreography (Uses/pins), never hidden inside Score.

A.19.USCM:1 - Problem frame

FPF’s Characterization (CHR) suite treats scoring as a mechanism boundary (authoritative membership: A.19.CHR:4.2). Suite membership is a set (order has no semantics); any intended ordering is expressed only via suite_protocols (A.19.CHR:4.5), under the suite obligations (A.19.CHR:4.3).

Within the canonical suite-closed protocol, USCM appears as the score stage (after normalize and indicatorize, before comparison and selection). USCM’s surface is admissibility-first: it produces score measures from admitted profiles while remaining constrained by the ScaleComplianceProfile (CG-Spec.SCP) and by scale-lawfulness (CSLC).

USCM exists to keep a distinction between:

  • normalization (UNM),
  • indicatorization (UINDM),
  • scoring (USCM),
  • aggregation/folding (ULSAM), and
  • comparison/ordering/selection (CPM + SelectorMechanism),

so that each commitment has a single place to live, can be audited, and can evolve without smuggling extra semantics into adjacent steps.

A.19.USCM:2 - Problem

Engineering teams often need to convert an admitted (indicator or NCV) profile into one or more score measures for downstream comparison and selection. When the scoring rule, scale constraints or input basis remain implicit, the following failures can occur:

  • Illicit arithmetic by convenience: teams apply weighted sums, averages, or nonlinear transforms across mixed scale kinds without an explicit admissibility profile, creating scores that are not CSLC‑lawful.
  • Hidden normalization: scoring implementations silently normalize, align, or flip polarities, collapsing the distinction between “normalize” and “score” and making downstream reasoning non‑reproducible.
  • Silent scalarization: multi‑criteria realities (vector scores, partial‑order comparability) are reduced to a single scalar via hidden tie‑breakers, producing an apparent total order that is not justified.
  • Unknown coercion: missing or insufficient evidence is coerced into 0/false or treated as “good enough,” yielding scores that look precise while being epistemically unsafe.
  • Drift and non-auditability: differences between teams’ scores for the same admitted target cannot be explained or replayed when the effective admissibility constraints and policies (editions, evidence rules, used relations) are not recoverable.

A.19.USCM:3 - Forces

  1. Admissibility discipline vs operational pressure. Admissibility must remain explicit and checkable under operational pressure: SCP and CSLC constraints must bound permissible transforms.

  2. Method diversity vs stable mechanism boundary. Scoring methods evolve rapidly; USCM’s signature must remain stable so method families can be wired through SoTA packs and extensions without mutating the mechanism boundary.

  3. Vector reality vs scalar simplicity. Many situations require multiple score dimensions. A single scalar score may be convenient but must be a declared commitment, not a hidden reduction.

  4. Uncertainty vs decisiveness. Teams need decisions under uncertainty; the framework must prevent epistemic overconfidence. Tri-state admissibility guards state whether the declared conditions pass, permit degraded use or require abstention; their correctness depends on the rule and evidence.

  5. Distinction across CHR steps. USCM must not absorb UNM, ULSAM, or CPM semantics “for convenience,” or the suite becomes opaque and non‑teachable.

  6. Evolvability vs didactic usability. Interfaces must remain evolvable (stable SlotKind surface; method semantics externalized), while the spec remains teachable: a reader must find USCM’s purpose, boundary, laws, guard behavior, and audit minimum in one place.

  7. P2W separation and gate/guard separation. On a P2W path, selection of planned editions and policy ids belongs to WorkPlanning plan items; gate decisions belong under gate patterns and work‑enactment logs belong with WorkEnactment. USCM must expose eligibility and audit pins without turning into a gate or a planner.

A.19.USCM:4 - Solution

USCM is the canonical scoring mechanism in the CHR suite. It defines:

  • a stable mechanism boundary (score is its own stage with a canonical Score operation and a tri‑state eligibility predicate),
  • a stable SlotKind surface (via the suite lexicon),
  • an admissibility‑first LawSet anchored in CG‑Spec.SCP and CSLC,
  • an anti‑smuggling rule (no implicit normalization), and
  • an audit minimum (the evaluated bearer and input profile, editions, criteria, comparison basis, evidence used, effective evidence policy, result use, any scope or window that qualifies that use, and any relation used).

USCM does not embed GateDecision/GateLog or perform publish/telemetry steps. It cites relation pins only when the score or its receiving use depends on an obtaining relation; assess loss under the applicable receiving-use rule.

Scoring-method semantics remain outside the suite core. The selected ScoringMethodDescription supplies them; G.2 packs can provide method choices, while wiring-only GPatternExtension modules cite the corresponding governing content and required pins.

A.19.USCM:4.1 - Operation declaration

USCM.IntensionRef cites the A.6.1 U.Mechanism declaration episteme here. The CHR score stage resolves to its local Score operation. Selecting a changed argument, scoring law or guard requires selecting that changed declaration explicitly; another realizer of the same declaration changes no suite member.

  • Scope note: A.6.1 governs the operation and its argument/result bindings below. The planned baseline selects method and specification editions; independently declared receiving positions may use A.15.3 typed filling. Score returns a score profile, while eligibility and Audit retain their own meanings. GateDecision/GateLog remain outside this declaration.

  • IntensionHeader: id = USCM, version = 1.0.0, status = stable.

  • IntensionRef: USCM.IntensionRef (canonical target for the suite member named in A.19.CHR:4.2).

  • SignatureManifest (optional; importability): if a USCM publication is intended to be imported/reused, it SHOULD publish a SignatureManifest (A.6.0:4.5 and A.6.1; A.6.0 checklist item 10 with SM-1 through SM-4) consistent with IntensionHeader/Imports, exposing the stable SlotKind surface (including ScoringMethodDescriptionSlot) and any declared scalarization commitment.

  • Purpose: SCP‑first scoring: produce score measures from admitted profiles without violating CSLC / scale lawfulness.

  • Imports: G.0 (CG‑Spec.SCP, CG‑Spec.MinimalEvidence), A.18 (CSLC), C.16 (measurement constitution and scale-lawful operations when measurement is claimed), A.19.CN (comparability.mode + normalization routing), A.19.CHR:4.2.1 (CHR SlotKind Lexicon).

  • SubjectBlock:

    • SubjectKind: ReadingContent, supplied by the reading contents in InputProfileSlot; each retains its bearer, Characteristic and Scale.
    • RangedValueKind: ReadingContent; Score transforms the admitted profile under the selected method, and ScoreEligibility assesses that proposed transformation.
    • SliceBasis: any declared U.ClaimScope, selected U.ContextSlice members or qualification window that qualify the scoring result or its intended use.
    • Input qualification: scoring ranges over the admitted indicator or NCV profile for the evaluated bearer, criteria, comparison or reference basis and intended result use, under any scope, slice or window conditions required by that use; CN-Spec.comparability routes comparison and CG-Spec.SCP constrains the permitted scoring transformations.
    • Results are declared per operation: the score-measure profile and the eligibility judgment.

Reading range. ReadingContent and profile interpretation come from C.16:5.5.1. Resolve each component’s subject, Characteristic, Scale, attribution and conditions before using its values. A content member can be conditional or insufficiently supported; this operation’s eligibility and evidence rules still decide whether it may be used. Profiles retain the positions or contributor identities, ordering and multiplicity required by their declared basis. An independently materialized result episteme is distinct from the calculated Coordinate and the bound reading content.

Operation-local argument and result declarations

Each input meaning is declared separately for Score and ScoreEligibility. ByRef inputs resolve to the stated value and edition. Cardinalities shown are for Score.

ScoreEligibility may assess an incomplete proposal: each required input then has cardinality 0..1, and an absent value has no binding and triggers the corresponding missing-input rule.

DirectionLocal designatorMeaning and ValueKindDesignation; cardinality
ArgumentInputProfileSlotAdmitted profile of ReadingContent components to score; each UINDM-derived value retains its basis position, Characteristic and ScaleByValue; 1 profile
ArgumentCNSpecSlotCN-Spec used for the bearer, basis, intended use and comparability routing, including any scope/slices or qualification window required by that useCNSpecRef; 1
ArgumentCGSpecSlotCG-Spec supplying the SCP restrictions and default evidence requirement for this scoring useCGSpecRef; 1
ArgumentScoringMethodDescriptionSlotScoringMethodDescription supplying the selected Coordinate→Score rule, domain, codomain, Scale, polarity and use-required propertiesScoringMethodDescriptionRef; 1
ArgumentMinimalEvidenceSlotMinimalEvidence override used in place of CGSpecSlot.MinimalEvidenceMinimalEvidenceRef; 0..1
Score resultScoreProfileSlotProfile of ReadingContent components returned by the declared scoring ruleByValue; 1 profile on completed admitted scoring, 0 on abstain or termination without a result
ScoreEligibility resultGuardDecisionEligibility judgment under the predicates below: pass, degrade or abstainByValue; 1 on completed evaluation

An argument’s bindingPredicate holds when this Score or ScoreEligibility application uses the resolved value for that row’s purpose: the profile supplies the operands, the method supplies the transformation, CN-Spec delimits its use and routing, and CG-Spec plus any override supplies its admission and evidence conditions. Mere inclusion in an Audit record is insufficient.

The ScoreProfileSlot bindingPredicate holds when that Score application returns the profile obtained by applying the bound method lawfully to those operands, with the declared scalar/vector cardinality. The guard’s result binding holds when that ScoreEligibility application returns its evaluated judgment. Each binding follows A.6.1 identity and continuous extent within the application; the result begins to bind at return.

SlotIndex (derived projection). Project this table’s local designators, ValueKinds, designation modes and cardinalities. Its historical Slot names permit CHR lookup and introduce no separate meanings; A.6.5 relation SlotSpecs do not govern these operation positions. A repeated Characteristic name alone cannot select a profile value whose basis position and Scale matter.

  • OperationAlgebra (suite stage = score, per A.19.CHR:4.5; canonical stage‑op = Score):

    • Score(InputProfileSlot, CNSpecSlot, CGSpecSlot, ScoringMethodDescriptionSlot, MinimalEvidenceSlot?) → ScoreProfileSlot; the cited inputs supply the evaluated bearer and use qualifications.

ApplicationPredicate. Score obtains when a calculation applies the bound scoring method to the bound input profile under the CN-Spec/CG-Spec conditions. It proceeds on pass or on an explicitly permitted degrade branch and returns the lawful score profile; abstain starts no Score calculation. ScoreEligibility obtains when an evaluation assesses the proposal under the eligibility predicates and returns the corresponding judgment. A passing guard or a cached compatible profile does not establish a new Score calculation.

ApplicationIdentityRule. One application is one scoring calculation or eligibility evaluation at its calculation locus, from taking up the chosen operands/rules until return or termination. Reidentifying that same invocation preserves identity. A second invocation with identical profile, method, specifications, qualification point and output is a distinct application; changing those arguments for another calculation also makes another application. A record identifier designates an established invocation and cannot create it.

ApplicationExtentRule. Score extends from use of the input profile under the selected method to the return of its score profile or termination; ScoreEligibility extends from proposal assessment to judgment or termination. An unfinished invocation has an open extent and no unreturned result binding. The qualification point or input window identifies what is scored, not when the scoring occurs. Ordinary use of a scoring function does not by itself assert dated U.Work.

For the Celsius example in §4.2, two separate calculations of (20−0)/(40−0) each return 0.5 under the same declared method. Their operand-to-return episodes and result bindings differ. A saved 0.5 can refer to the earlier result when that return is established; numerical agreement and the same method pins cannot establish a second return. The example retains its specified Celsius input and interval endpoints.

  • LawSet (minimum; admissibility‑first, no hidden scalarization):

    1. SCP+CSLC lawfulness: any numeric transform used to produce ScoreProfileSlot MUST be admissible under CGSpecSlot.SCP and CSLC‑lawful (cites G.0 + A.18).
    2. ScoringMethod is explicit (no hidden defaults): Score MUST cite ScoringMethodDescriptionSlot (with its edition resolved for this use and recorded in the P2W baseline when applicable; see A.19.CHR:4.7.2). Disclose the scoring method 𝒢 (Coordinate→Score), its domain, codomain, Scale, polarity and the properties required by the declared scoring use. Apply C.16 when measurement is claimed and enforce the SCP/CSLC restrictions. Boundedness or monotonicity is required only when the selected method or use requires it. USCM MUST NOT rely on an implicit default scoring method.
    3. No implicit normalization: Score MUST NOT silently perform UNM; if CNSpecSlot.comparability requires normalization‑based comparability, the normalization step MUST be explicit in choreography (Uses/pins), not hidden in Score.
    4. Vector scores allowed; scalarization must be explicit: producing a single scalar score is allowed only if declared (e.g., by fixing ScoreProfileSlot cardinality to 1 and citing the lawful transform); partial‑order semantics MUST NOT be silently reduced to a scalar “tie‑breaker”.
    5. Unknown is not coerced: unknown / insufficient evidence MUST NOT be mapped to 0/false; use tri‑state guards and explicit failure behavior.
  • AdmissibilityConditions (tri‑state guard; fail‑closed on missing admissibility/evidence):

    • ScoreEligibility(InputProfileSlot, CNSpecSlot, CGSpecSlot, ScoringMethodDescriptionSlot, MinimalEvidenceSlot?) → GuardDecision ∈ {pass|degrade|abstain}.
    • pass requires: (i) CGSpecSlot.SCP is present, (ii) the scoring method and edition are explicit, (iii) the input profile is admitted for the bearer and criteria, (iv) the cited specs apply to the comparison or reference basis and intended result use, including any required claim-scope, slice or window qualifications, (v) the evidence supporting the admitted profile passes the effective minimum, (vi) CN-Spec.comparability routing is satisfied, including explicit UNM when needed, and (vii) the declared transformation is defined on the input profile and satisfies the applicable SCP/CSLC restrictions.
    • If MinimalEvidenceSlot is absent, the guard MUST evaluate evidence against CGSpecSlot.MinimalEvidence, and MUST NOT return pass when evidence is missing/unknown.
    • If ScoringMethodDescriptionSlot is missing or unresolved or ambiguous under the selected use baseline, the guard MUST return abstain (fail‑closed), not “assume a default”.
    • degrade requires every non-evidence condition above and an effective failure policy that permits the stated degraded result when evidence is insufficient. abstain applies otherwise, including an undefined transformation or missing required input. A degrade policy supplies no undefined value.
  • Applicability:

    • Score is intended to be used after indicatorization (when indicator profiles are used) and before comparison/selection.
    • Score is applicable only when admissibility/evidence surfaces are present via CGSpecSlot (fail-closed otherwise).
    • Score is applicable only when a scoring method is declared via ScoringMethodDescriptionSlot (edition-pinned when reproducibility matters). A “do nothing / identity scoring” intent (if needed) MUST still be declared as a scoring method description, not as an implicit default.
  • Relation boundary: scoring creates no transfer relation. If the input profile or receiving use relies on an F.9 Bridge, kind relation, or plane relation, cite that obtaining relation, its direction and loss. Establish the bounded-use and reliance grounds required for that proposed use, and assess loss against its receiving rule and tolerance. Apply a numerical assurance penalty only when a named assurance use consumes it and an applicable B.3 domain model warrants it under its declared assumptions.

  • Γ_timePolicy: when a temporal qualification is needed, point by default (no implicit “latest”).

  • PlaneRegime: each admitted input and score keeps its declared reference plane; USCM introduces no plane crossing. When a conclusion depends on a relation between planes, cite that relation, its direction and loss, and keep the receiving use separate.

  • Audit: Make the application basis below recoverable from the specifications, inputs, evidence and results used. For ScoreEligibility, identify missing or unresolved required inputs and policies, and apply the following requirements to the values supplied or resolved. Retain a separate record when the receiving use requires one.

    • MUST make recoverable: the evaluated bearer, input profile and its admission status; CNSpecRef.edition, CGSpecRef.edition, and ScoringMethodDescriptionRef.edition; criteria, comparison or reference basis and intended result use; and any claim scope, selected slices or qualification window that qualify that use.
    • MUST make recoverable the evidence refs used for input admission or the ScoreEligibility evaluation.
    • MUST make the effective evidence policy recoverable:
      • if MinimalEvidenceSlot? is present → identify MinimalEvidenceRef as effective;
      • otherwise → identify CGSpecSlot.MinimalEvidence as effective.
    • SHOULD make recoverable the realized GuardDecision for ScoreEligibility, and (when degrade/abstain) the referenced failure behavior / downstream handling policy id (e.g., SoS-LOG branch id) when such a policy is in scope.
    • SHOULD make recoverable: a stable description of ScoreProfileSlot; any F.9 Bridge, kind relation, or plane relation only when the score or receiving use relies on it; and, when normalization-based comparability was required, the upstream UNM ref or pin.

A.19.USCM:4.2 - Interpretation notes — informative

  • Selected-input basis. Consume the UINDM S and space declaration when an indicator profile is used. For CS7 in A.19.UINDM §5.4, the Celsius policy selects i1 and the declared Celsius scoring rule reads 20, giving 0.5. It cannot read the kelvin position’s 293.15 under that rule. After a basis change, resolve the selected positions and the scoring method’s input requirements again; keep any projection in the original basis order.

  • A score profile retains its component meanings. ScoreProfileSlot is a declared profile of ReadingContent components, with each component’s score Characteristic and Scale recoverable. An ordered vector rendering retains the correspondence between positions and those components. Several score dimensions are different from uncertainty expressed by an interval or set for one component. A scalar score, or an interval-valued result, requires its own declared meaning and admissible operations.

  • USCM does not order; it scores. USCM produces score measures. Any ordering, dominance, or set‑valued comparison is performed by CPM and SelectorMechanism (and any optional aggregation is made explicit via ULSAM). Treating the score as “the decision” is a category error in CHR terms.

  • ScoringMethod is explicit (no hidden defaults). USCM requires ScoringMethodDescriptionSlot with its selected edition. A formal A.3.2 U.MethodDescription claim requires an independently admitted A.3.1 Method as EntityOfConcern and substantive content about that Method as a way of doing. This keeps “how we score” evolvable (wired via method packs) without making it implicit or accidental.

  • No implicit UNM is a boundary guard. This discourages convenience implementations that “just normalize inside scoring.” USCM forbids that: if comparability requires normalization‑based routing, the UNM step is explicit in choreography (Uses/pins) and visible in audit surfaces.

  • Evidence policy is explicit and auditable. MinimalEvidenceSlot? is an optional override; otherwise the effective policy is CGSpecSlot.MinimalEvidence. Failures do not disappear; they must show up as degrade/abstain and be traceable.

  • Relations are explicit; loss is judged for the receiving use. When a score or receiving conclusion depends on another source-local meaning, bearer kind, or reference plane, cite the obtaining relation and supported loss. Apply the receiving rule and tolerance; a numerical assurance penalty needs the applicable B.3 domain model. A changed bearer, scope, method, basis, or use is not by itself a crossing.

A.19.USCM:5 - Archetypal Grounding — informative

A.19.USCM:5.1 - Tell

Think of USCM as admissibility‑gated scoring:

  • Input: “an admitted profile of measures for this bearer, criteria, comparison basis, evidence policy and result use, with any scope or window that qualifies that use, plus the CN-Spec and CG-Spec editions that declare those bounds”
  • Output: “a set of score measures that downstream steps may compare/select on”

USCM is allowed to transform measures only within the admissibility surface (SCP+CSLC), and it must not hide normalization, aggregation, or ordering.

A.19.USCM:5.2 - Show — rollout-plan evaluation

A program manager evaluates competing rollout plans for a product launch.

  • The admitted profile includes measures like {Cost, LeadTime, Reliability, RiskExposure, CarbonPerUnit}.
  • The CG-Spec’s SCP states the allowed transforms and their output meanings. A rescaling that preserves a ratio chart uses a positive factor; an interval-chart conversion uses its admissible affine rule. A different scoring function declares its score Scale and valuation instead of claiming that any monotone function preserves the original quantity.
  • USCM runs Score(...) and outputs a score profile such as {UtilityScore, RiskScore} rather than forcing a single number.
  • A plan lacks sufficient evidence for RiskExposure. In this constructed case the declared method can return a bounded risk-score interval from the available inputs, and the effective failure policy permits that qualified output. ScoreEligibility returns degrade only if the non-evidence conditions still hold. Audit retains the interval meaning, limitation and CN/CG editions. If the method has no defined result on the available inputs, the result is abstain instead.

A downstream comparison can use that interval only under a rule that accepts its meaning and uncertainty. The audit identifies the grounds; it does not supply a missing comparison rule.

A.19.USCM:5.3 - Show — U.Episteme

A research lead compares several model families for deployment across heterogeneous environments.

  • Indicators include calibration and robustness metrics; scoring is done using a calibrated probabilistic score plus uncertainty‑aware score dimensions.
  • A chosen scoring method may require monotonicity or interpretability, as in the additive and lattice examples below. A separate prediction-uncertainty account may supply an interval under its own method and conditions; its interval is not another name for a vector of score dimensions.
  • The declared score profile retains each score dimension and any justified uncertainty representation. Unknown input is not replaced by a point score. Downstream comparison explicitly handles the scalar, vector or interval meanings it consumes.

A.19.USCM:6 - Bias-Annotation — informative

  • Gov (governance). Bias toward explicit admissibility and evidence surfaces (CGSpecRef, SCP, MinimalEvidence) rather than “standard practice” arithmetic. Risk: perceived overhead. Mitigation: keep the shared signature small; use the selected ScoringMethodDescription for method-specific rules and wiring modules for their references and pins.

  • Arch (architecture). Bias toward stable interfaces and strict step boundaries (no implicit UNM; no hidden scalarization). Risk: reduced room for ad‑hoc shortcuts. Mitigation: allow richer scoring method families via wiring, without mutating the USCM intension.

  • Onto/Epist. Bias toward treating scores as measures with declared semantics, not as “the truth.” Risk: teams accustomed to one‑number rankings may resist. Mitigation: treat scalarization as an explicit, auditable commitment, not as the default.

  • Prag (pragmatics). Bias toward fail‑closed guards and traceability under uncertainty. Risk: more degrade/abstain outcomes early. Mitigation: couple degrade with explicit downstream behavior policies, rather than silent coercion.

  • Did (didactics). Bias toward “one place to learn the mechanism”: the problem/forces/solution narrative is co‑located with the canonical Mechanism.Intension.

A.19.USCM:7 - Conformance Checklist

A USCM publication or use is conformant if it satisfies:

  1. Mechanism declaration completeness. The A.6.1 operation-local arguments/results, application predicates, identity/extent rules and laws in §4.1 are recoverable, together with the declared imports, subject, admissibility, applicability, transport, time, plane and Audit conditions. SlotIndex projects the argument/result declarations; eligibility retains its tri-state result.

  2. SlotKind discipline. SlotKind tokens match the CHR SlotKind lexicon for the roles used (InputProfileSlot, CNSpecSlot, CGSpecSlot, MinimalEvidenceSlot, ScoringMethodDescriptionSlot, ScoreProfileSlot); no generic ContextSlot is introduced. If a required token is missing, suite-dock it rather than introducing it ad hoc in the mechanism.

  3. SCP+CSLC admissibility is enforced. Any numeric transform used to produce score measures is admissible under CGSpecSlot.SCP and CSLC-lawful; illicit operations (especially “convenient arithmetic” over non-lawful scales) are excluded.

  4. ScoringMethod is explicit and auditable. Score cites ScoringMethodDescriptionSlot (edition-pinned when reproducibility matters). Its domain, codomain, Scale, polarity and use-required properties are disclosed and satisfy the applicable SCP/CSLC restrictions. Apply C.16 for any measurement claim.

  5. No implicit normalization. Score does not silently perform UNM. If CN‑Spec.comparability requires normalization‑based routing, the normalization step is explicit in choreography (Uses/pins) and auditable.

  6. No hidden scalarization. Vector scores are permitted. A scalar score is produced only when declared, and partial‑order semantics are not reduced to a scalar tie‑breaker.

  7. Unknown and evidence handling is explicit. Unknown / insufficient evidence is not coerced to 0/false. Eligibility uses GuardDecision ∈ {pass|degrade|abstain} and evaluates evidence against the effective policy (MinimalEvidenceSlot override or CGSpecSlot.MinimalEvidence).

  8. Planning and actual binding remain separate. On a P2W path, A.15.2 carries the intended edition/policy baseline; A.15.3 governs typed filling only for independently declared positions. The application uses its effective bindings under §4.1, and Audit makes their refs and pins recoverable. Planned selection alone does not establish actual use.

  9. Relation and plane discipline. Another bearer, scope and window, basis, method, plane, or result use gets a fresh eligibility decision. Any F.9 Bridge, kind relation, or plane relation is cited only when the score or conclusion relies on that obtaining relation. Judge loss under the receiving-use rule; a numerical assurance penalty requires an applicable B.3 domain model.

  10. Specialization discipline, if extended. Retain inherited operation-position meanings, add no mandatory input to the inherited Score operation, and declare extra outputs or operations using the local extension notation ⊑⁺. A claimed refinement, conservative extension or equivalence additionally needs its A.6.1 §4.8 predicate, endpoint facts and applicable preservation test; ⊑/⊑⁺ alone establishes none of them.

A.19.USCM:8 - Common Anti‑Patterns and How to Avoid Them

  • Hidden normalization inside scoring. Scoring silently normalizes or aligns measures. Avoid by making UNM explicit in choreography and keeping Score as the declared scoring transformation under its admission conditions.

  • Weighted sum across mixed or non-admissible scales. Treating “weights + sum” as universal. Avoid by requiring SCP+CSLC admissibility.

  • Silent scalarization. Collapsing vector scores or partial orders into a single “overall score” via an untracked tie‑breaker. Avoid by leaving vector scores intact, and making scalarization a declared commitment.

  • Implicit scoring method (“we just use the standard formula”). The scoring method is assumed rather than declared and pinned. Avoid by requiring ScoringMethodDescriptionSlot and resolving its edition, recorded in a planned baseline on P2W paths; treat “identity scoring” (if needed) as an explicit method description, not a hidden default.

  • Unknown → 0 coercion. Treating missing evidence as zero, false, or “good enough.” Avoid by tri‑state guards and explicit failure behavior, with auditable effective evidence policy.

  • Shadow CG‑Spec. Copying governing CG conditions into a competing local specification creates drift. Cite CGSpecSlot.SCP and retain the scoring method’s own domain, law and restrictions; method-specific conditions are substantive content, not merely wiring.

  • Telemetry or publish leakage. Treating scoring as a reporting step. Avoid by keeping publish/telemetry outside suite closure and using the appropriate post-suite mechanisms.

  • SlotKind drift. Renaming or re‑purposing slots across specializations or across mechanisms. Avoid by using the suite SlotKind lexicon and the ⊑/⊑⁺ discipline.

A.19.USCM:9 - Consequences

Benefits

  • Makes scoring a first‑class, admissibility‑gated CHR step, reducing illicit arithmetic and silent assumptions.
  • Improves auditability and reproducibility via edition pins and explicit evidence policy selection (override vs default).
  • Preserves evolvability: scoring method families can change via SoTA wiring without changing the USCM intension.
  • Makes uncertainty disposition explicit through the guard result and its effective failure policy.

Costs / trade‑offs

  • Requires explicit CG‑Spec admissibility surfaces (SCP) and explicit evidence policies to achieve pass; this can feel slower than “just compute a score.”
  • Vector scores can be less immediately comfortable than a single number; downstream comparison/selection must be explicit about how vector scores are used.

A.19.USCM:10 - Rationale

Scoring can lose semantic precision through hidden normalization, illegal arithmetic, implicit thresholds or uncertainty coercion. USCM requires the following commitments to remain explicit:

  • Admissibility first: transformations satisfy the restrictions in CG‑Spec.SCP and CSLC.
  • No hidden steps: normalization is explicit (UNM), aggregation is explicit (ULSAM), ordering is explicit (CPM/SelectorMechanism).
  • Uncertainty is visible: admissibility is tri‑state; unknown is not coerced.
  • Recoverable audit basis: effective editions and the effective evidence policy remain traceable.

A.19.USCM:11 - SoTA-Echoing

The following research and architecture-description lines inform distinct choices. A receiving task selects its method and verifies the conditions it needs; none of these examples establishes a universal scoring policy.

A.19.USCM:11.1 - SoTA alignment map

Practice contributionSource examplesWhere it connects to USCMAdoption status
Prefer monotone and interpretable scoring surfaces where appropriateExplainable additive and monotone model lines, e.g., Nori et al. 2019; monotone deep lattice style models, e.g., You et al. 2017Expressed as admissibility‑bounded transform freedom via CGSpecSlot.SCP and explicit scalarization rules; method details stay out of the kernelAdapt
Assess calibration when interpreting probability estimates as correctness likelihoodsGuo et al. (2017), On Calibration of Modern Neural Networks, including temperature scalingExpressed as “score is a measure on an explicit scale,” bounded by SCP+CSLC and evidence gating; calibration itself is wired as method semantics, not kernel lawAdapt
Keep prediction uncertainty distinct from multiple score dimensionsRomano, Patterson and Candès (2019), Conformalized Quantile Regression, constructs prediction intervals under its stated conditionsRetain the interval’s declared meaning and conditions when a receiving score or comparison uses it. Vector cardinality alone does not establish uncertainty semanticsAdapt
Keep architectural commitments traceable to one governing patternISO/IEC/IEEE 42010:2022 architecture description disciplineFPF adapts architecture-description distinctions to explicit governing-pattern references; that local assignment is not a rule claimed from the standardAdapt

Notes per row

  1. USCM does not “implement a particular scoring model”; it preserves a stable, admissibility‑gated surface on which such models can be wired.
  2. A calibration transform must satisfy SCP+CSLC; USCM does not mandate a specific calibration method.
  3. A prediction interval and a vector of score measures carry different meanings. A downstream CPM/SelectorMechanism use needs a declared comparator for whichever result it consumes; neither form supplies an ordering automatically.

A.19.USCM:12 - Relations

  • Builds on

    • A.6.1 (operation declarations and application/binding rules).
    • A.19.CHR:4.2.1 (CHR SlotKind lexicon).
    • G.0 (CG‑Spec, specifically SCP and MinimalEvidence).
    • A.18 (CSLC lawfulness discipline).
    • C.16 (measurement constitution and scale-lawful operations when measurement is claimed).
    • A.15.2 for the planned edition/policy baseline on P2W paths; A.15.3 plus A.19.CHR:4.7.2 for typed filling of independently declared positions.
    • A.19.CN (CN‑Spec, specifically comparability routing and normalization‑based comparability expectations).
  • Used by

    • A.19.CHR (suite membership and suite protocols; USCM is the score stage).
    • Downstream CHR stages that require score measures as inputs (e.g., CPM, SelectorMechanism).
    • E.18 when USCM instances are used as nodes in a selected TransformationFlowStructure; the selected ScoringMethodDescriptionRef@edition(…) and other pins live in planned baselines (P2W), while executions surface effective refs/pins via Audit.
  • Coordinates with

    • UNM when CN‑Spec.comparability requires normalization‑based comparability (explicit choreography, no hidden UNM).
    • ULSAM when folding/aggregation is needed as a distinct, explicit step.
    • G.2 for scoring-method choices and GPatternExtension modules for their wiring, without mutating the USCM kernel.
    • E.20 (governing-pattern discipline) and F.18 (alias docking) for governing-source references and designation continuity.

A.19.USCM:End

A.19.ULSAM - Unified Lawful Scale Aggregation Mechanism

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative)

ULSAM.IntensionRef identifies the U.Mechanism declaration in §4.1 under A.6.1. CHR resolves its optional fold_Γ? stage to the local Fold_Γ operation; the declaration supplies the meanings and application/binding rules below.

A.19.ULSAM:0 - At a glance (didactic, informative)

  • Suite stage: fold_Γ? (ordering lives only in A.19.CHR:suite_protocols; mechanisms[] membership is a set, not an order).
  • Input surface: an admitted MeasureSetSlot, CNSpecSlot, CGSpecSlot, and GammaFoldSlot, with the grouping or membership basis, fold and policy editions, claim scope and selected slices, qualification window, evidence basis, contributors, and intended result declared by those inputs; MinimalEvidenceSlot? may override the CG-Spec minimum.
  • Output surface: AggregatedMeasureSlot (+ optional ContributorSetSlot? as an explanation surface).
  • Non‑goals: no scoring, no comparison, no selection, no “method catalog”, no hidden defaults, no hidden thresholds.
  • P2W seam: an A.15.2 baseline selects the fold, evidence policy and their editions. A.15.3 typed filling applies only to independently declared receiving positions under the CHR P2W hook. Fold arguments bind under §4.1; a planned value does not establish that binding.
  • Failure mode: tri‑state guard GuardDecision := {pass|degrade|abstain}; unknown/insufficient evidence never coerces to “pass”.
  • Rule of thumb: if you are about to “average/sum/roll up”, you probably need a ULSAM Fold_Γ stage (or a justified decision to not fold).

What this mechanism is. ULSAM is the CHR mechanism that makes aggregation explicit: it performs a Γ‑fold over a set of admitted measures, producing an aggregated measure (and optionally a contributor surface) under declared admissibility.

Use this when the receiving use needs an aggregate measure:

  • You want to “roll up” multiple measures into one measure (e.g., an overall reliability/assurance coordinate, a single aggregated risk measure, an aggregate score coordinate).
  • You need the fold to be auditable (what contributed; what was excluded by evidence/admissibility).
  • You need the fold to be scale-lawful (no ordinal arithmetic; no illegal mixing of units).
  • You need the fold to be policy-bound and edition-stable (replayability and pin traceability).

Choosing the fold. If the law for the intended result or a required property is unresolved, use A.9 or reuse a sufficient domain result. When the result selects a fold, its law and conditions supply the basis for the fold reference; ULSAM still governs admission of the measures, scale lawfulness and the mechanism operation.

Where it sits in CHR.

  • In the CHR suite protocol, ULSAM corresponds to the optional stage fold_Γ?, never hidden inside score/compare/select.

First useful move. State what the aggregate must mean and which contributors it covers. Resolve the fold and its conditions, then check the inputs. If separate measures already answer the receiving question, stop without folding. Make the actual contributors recoverable; a separate ContributorSet result is optional.

A.19.ULSAM:1 - Problem frame (normative)

Within CHR, teams frequently need an explicit aggregation step (Γ‑fold) to produce an aggregated measure that is later consumed by comparison and/or selection. Without a dedicated mechanism boundary, aggregation tends to:

  • leak into scoring (“the score function also averages everything”),
  • leak into selection (“the selector silently computes a scalar”),
  • become an “implementation default” rather than a declared policy,
  • violate scale lawfulness (especially via ordinal arithmetic or unit-mixing),
  • become unauditable (“what got folded, and under what evidence posture?”).

A.19.ULSAM:2 - Problem (normative)

How do we define an aggregation step that:

  1. is explicit (separate from scoring/comparison/selection),
  2. is scale-lawful and admissibility-gated (CSLC + CG-Spec.SCP),
  3. is Γ‑fold-policy-bound (CG‑Spec.Γ_fold or explicit override),
  4. is evidence-gated with tri‑state guards (no unknown → 0/false coercions),
  5. is auditable (editions, effective fold, contributor surface),
  6. preserves kernel stability while allowing SoTA evolution via wiring.

A.19.ULSAM:3 - Forces (normative)

  • Lawfulness vs convenience. The most “convenient” aggregation (e.g., weighted sums) is often illegal across scales/units; lawful folds require explicit constraints.
  • Explicitness vs brevity. A single scalar is short to discuss, but expensive in hidden assumptions.
  • Stable declaration vs method variation. Different realizers can use the same operation declaration while preserving its argument meanings, fold law and guard. Changing that content requires selection of the changed declaration.
  • Evidence gating vs “always return a number.” The mechanism must support abstain/degrade rather than coercion.
  • Optional stage vs pipeline clarity. fold_Γ? is optional in CHR protocols; optionality must be explicit (not implicit “sometimes scoring folds”).
  • Auditability vs minimal overhead. Recording contributor sets and effective pins adds overhead but prevents semantic drift.
  • Declared-set locality vs reuse. A fold is valid for one admitted measure set, grouping or membership basis, policy editions, scope and window, evidence basis, contributors, and intended result; a later use must recheck those premises and cite any relation it relies on.
  • P2W separation and gate/guard separation. ULSAM must expose eligibility and audit pins without turning into (i) a WorkPlanning baseline binder or (ii) an admissibility gate: planned slot fillings belong to WorkPlanning plan items, while GateDecision/GateLog live in gate patterns / WorkEnactment (suite protocols remain mechanism-steps only).

A.19.ULSAM:4 - Solution (normative)

ULSAM is the canonical scale‑aggregation mechanism in the CHR suite. It defines:

  • a stable mechanism boundary (fold_Γ? is a stage with its own operation and eligibility predicate),
  • a stable SlotKind surface (via the suite lexicon),
  • a tri‑state admissibility guard (fail‑closed on missing admissibility/evidence),
  • and an audit minimum (admitted set and membership basis, fold and policy editions, scope and window, evidence, contributors, result, and any relation used).

Method semantics (“which aggregation family to use”) remain out of suite core: they belong in SoTA packs (G.2) and wiring‑only extension modules (GPatternExtension blocks), while ULSAM remains the stable mechanism boundary.

A.19.ULSAM:4.1 - Operation declaration (normative)

ULSAM.IntensionRef cites this A.6.1 U.Mechanism declaration episteme. CHR resolves its fold stage to the local Fold_Γ operation. A changed argument, fold law or guard requires selection of that changed declaration; another realizer of the same declaration changes no suite member.

  • Scope note: A.6.1 governs the operation and its bindings below. A planned baseline selects the fold and specification editions; typed filling is conditional on an independently declared receiving position. Fold_Γ returns the aggregate and any declared contributor set. Eligibility, Audit, GateDecision/GateLog and publication retain their separate meanings.

  • IntensionHeader: id = ULSAM, version = 1.0.0, status = stable.

  • IntensionRef: ULSAM.IntensionRef (canonical target for the suite member named in A.19.CHR:4.2).

  • Purpose: explicit Γ‑fold (and, when declared, time‑fold) over admitted measures — no hidden aggregation inside scoring/selection.

  • Imports: G.0 (CG‑Spec.Γ_fold, CG‑Spec.SCP, CG‑Spec.MinimalEvidence), A.18 (CSLC), A.19.CN (CN‑Spec.acceptance + aggregation routing), A.6.1 (operation declarations and bindings), B.3 (justified quantity and dependency model for any R_eff fold), A.19.CHR:4.2.1 (CHR SlotKind Lexicon).

  • SubjectBlock:

    • SubjectKind: ReadingContent, supplied by the reading contents carried by the contributor entries in MeasureSetSlot.
    • RangedValueKind: ReadingContent; Fold_Γ aggregates the admitted measures, and FoldEligibility_Γ assesses that proposed aggregation.
    • SliceBasis: the declared U.ClaimScope and selected U.ContextSlice members, together with the qualification window and intended result use.
    • Input qualification: aggregation ranges over the admitted measure set and its declared grouping or membership basis, scope and window, evidence basis, contributors, and intended result; CNSpecSlot.acceptance routes admission while CG-Spec.Γ_fold and CG-Spec.SCP govern admissibility.
    • Results are operation-local: aggregate, optional contributors and separate eligibility judgment.

Reading range. ReadingContent and profile interpretation come from C.16:5.5.1. Resolve each component’s subject, Characteristic, Scale, attribution and conditions before using its values. A content member can be conditional or insufficiently supported; this operation’s eligibility and evidence rules still decide whether it may be used. Profiles retain the positions or contributor identities, ordering and multiplicity required by their declared basis. An independently materialized result episteme is distinct from the calculated Coordinate and the bound reading content.

Operation-local argument and result declarations

Each input is declared separately for Fold_Γ and FoldEligibility_Γ. References resolve to one value and edition. Cardinalities shown are for Fold_Γ; the guard may assess an incomplete proposal with 0..1 of each otherwise required input. A missing value has no argument binding and invokes the corresponding abstain condition.

DirectionLocal designatorMeaning and ValueKindDesignation; cardinality
ArgumentMeasureSetSlotSet of contributor entries carrying ReadingContent, retaining contributor identities and its declared grouping or membership basisByValue; 1 set
ArgumentCNSpecSlotCN-Spec whose acceptance conditions delimit the admitted portion, scope/window and intended aggregate useCNSpecRef; 1
ArgumentCGSpecSlotCG-Spec supplying SCP, the declared fold and default evidence conditionsCGSpecRef; 1
ArgumentGammaFoldSlotΓFold selected through CGSpecSlot.Γ_fold or an admitted overrideΓFoldRef; 1
ArgumentMinimalEvidenceSlotMinimalEvidence override used in place of CGSpecSlot.MinimalEvidenceMinimalEvidenceRef; 0..1
Fold_Γ resultAggregatedMeasureSlotReadingContent returned by applying the effective fold to its admitted contributorsByValue; 1 on completed admitted folding, 0 without a result
Fold_Γ resultContributorSetSlotSet of contributor entries carrying ReadingContent used in that aggregateByValue; 0..1 set, optional
FoldEligibility_Γ resultGuardDecisionEligibility judgment under the predicates below: pass, degrade or abstainByValue; 1 on completed evaluation

An argument’s bindingPredicate holds when that application uses the resolved value in the row’s stated role: as offered measures, acceptance/use conditions, fold/admissibility declaration or evidence override. The AggregatedMeasureSlot bindingPredicate holds when that Fold_Γ application returns the measure it computes using its bound effective fold and admitted contributors. The ContributorSetSlot binding holds only when the same application also returns that contributor set; Law 5 requires both its subset condition and equality of the aggregate to the effective fold of that subset. An omitted contributor result creates no contributor binding. The guard result binds when that FoldEligibility_Γ evaluation returns its determined judgment. A.6.1 governs binding identity and maximal continuous extent within the application, with result binding beginning at return.

SlotIndex (derived projection). Project the local designators, ValueKinds, designation modes and cardinalities above. Historical Slot names support CHR lookup; A.6.5 relation SlotSpecs add no operation meanings. The optional FoldTime_Γ extension is not a base operation or a prerequisite of ordinary folding.

  • OperationAlgebra (suite stage = fold_Γ?, per A.19.CHR:4.5; canonical stage‑op = Fold_Γ):
    • Fold_Γ(MeasureSetSlot, CNSpecSlot, CGSpecSlot, GammaFoldSlot, MinimalEvidenceSlot?) → (AggregatedMeasureSlot, ContributorSetSlot?); the cited inputs supply the set, grouping and use qualifications.

ApplicationPredicate. Fold_Γ obtains when a calculation applies the resolved effective fold to the admitted contributors selected from the bound measure set under the bound acceptance/use conditions. It proceeds on pass or a permitted degrade branch; abstain produces no folding result. FoldEligibility_Γ obtains when an evaluation assesses the proposed set, fold and conditions under the guard predicates and returns its judgment. Numerical equality to a lawful fold and a passing guard alone establish neither calculation nor its result binding.

ApplicationIdentityRule. One Fold_Γ occurrence is one aggregation invocation at its calculation locus, from taking up the admitted operands/fold to return or termination. One FoldEligibility_Γ occurrence is one corresponding proposal-evaluation invocation. A second invocation remains distinct even when every measure, contributor, fold, policy, qualification window and returned value is equal. Several references to the same established invocation identify one application; creating another reference or copying its result creates none.

ApplicationExtentRule. The fold extends from use of its operands and rule through aggregate/contributor return or termination. The guard extends from proposal assessment through judgment or termination. An unfinished invocation has an open extent and no unreturned result binding. A time window qualifying the measures or a declared time-fold does not supply the occurrence interval of the calculation that processes them. Ordinary folding mathematics needs no asserted dated U.Work.

For example, two separate lawful sums of admitted 2 kg and 3 kg measurements under the same fold, grouping and policy both return 5 kg, with contributor set {2 kg, 3 kg} if requested. Law 5 holds for both contents. The first and second operand-to-return episodes nevertheless supply different aggregate/contributor bindings. A copied pair (5 kg, {2 kg, 3 kg}) is not evidence of another performed sum; two descriptions of the first sum still describe one application.

  • LawSet (minimum; explicit, scale‑lawful folding only):

    1. No hidden aggregation: any Γ‑fold MUST be explicit as Fold_Γ (no folding hidden inside Score/Compare/Select).
    2. Scale‑lawfulness: aggregation MUST be CSLC‑lawful and admissible under CGSpecSlot.SCP; ordinal arithmetic (e.g., means on ordinal ranks) is forbidden unless explicitly allowed by the relevant CSLC fragment.
    3. Γ‑fold admissibility: GammaFoldSlot MUST resolve to either CGSpecSlot.Γ_fold or a pinned override (CAL policy) – never an implicit “implementation default”.
    4. Evidence‑gated folding: if evidence is insufficient/unknown, folding MUST follow tri‑state guard behavior and MUST NOT silently coerce.
    5. Contributor accountability (when produced): when ContributorSetSlot? is produced, it MUST be a subset of the admitted portion of MeasureSetSlot, and AggregatedMeasureSlot MUST be the result of applying the effective Γ‑fold to that contributor subset (no “hidden contributors”).
    6. No implicit UNM: ULSAM MUST NOT silently normalize/rescale to “force comparability.” If establishing a compare‑on‑invariants surface requires UNM for the measures being folded, UNM MUST appear as a stage (Uses + pins) upstream; ULSAM itself remains folding‑only.
  • AdmissibilityConditions (tri‑state guard; fail‑closed on missing admissibility/evidence):

    • FoldEligibility_Γ(MeasureSetSlot, CNSpecSlot, CGSpecSlot, GammaFoldSlot, MinimalEvidenceSlot?) → GuardDecision ∈ {pass|degrade|abstain}.
    • pass requires: (i) CGSpecSlot provides SCP, (ii) GammaFoldSlot resolves to the admitted fold or an override, (iii) the contributor subset and its grouping or membership basis are admitted by CNSpecSlot.acceptance, (iv) scope, window, evidence, contributors, and intended result are recoverable, and (v) the set is scale-compatible for that fold, (vi) the fold is defined for the contributors and satisfies its law and SCP restrictions, and (vii) any exclusions or multiplicities agree with the declared aggregate meaning.
    • Define EffectiveMinimalEvidence := (MinimalEvidenceSlot if present, else CGSpecSlot.MinimalEvidence); the guard MUST evaluate evidence against EffectiveMinimalEvidence.
    • If evidence is missing/unknown under EffectiveMinimalEvidence, the guard MUST NOT return pass (return degrade or abstain per the effective failure behavior; record the basis in Audit).
    • degrade requires every non-evidence condition above and an effective policy permitting the qualified result. abstain applies otherwise, including an undefined fold or missing required contributor basis. A policy cannot supply a value where the fold is undefined, including an empty contributor set unless the fold declares a result for it.
  • Applicability:

    • Intended to be used only when a fold is required (and never as a hidden sub‑step of scoring/comparison/selection).
    • Applicable only when CG-Spec supplies SCP and the effective fold resolves through its Γ_fold or an admitted override (fail-closed otherwise).
    • If comparability routing is UNM-based, applicability requires the upstream result and preservation/loss basis needed by the fold. A fold inherited on classes requires equivalent outputs and representative-independent availability; a requested aggregate answer must be recoverable. Otherwise retain/refine the original inputs or return the missing distinction.
  • Relation boundary: folding creates no transfer relation. If the admitted set or receiving use relies on an F.9 Bridge, kind relation, aggregation or membership relation, or plane relation, cite the obtaining relation, its direction and loss; assess loss for the receiving use and apply any numerical assurance penalty under A.6.7:4.2(2).

  • Γ_timePolicy: point by default; time‑fold requires explicit windowing policy (if an explicit operator is needed, introduce FoldTime_Γ as an ⊑⁺ extension using GammaTimeRuleSlot from the CHR SlotKind Lexicon).

  • PlaneRegime: each contributor and aggregated measure keeps its declared reference plane; ULSAM introduces no plane crossing. When a result depends on a relation between planes, cite that relation, its direction and loss, and keep the receiving use separate.

  • Audit:

    • MUST record the proposed measure set and its grouping or membership basis when available, including the admitted portion when established; the CNSpecRef.edition, CGSpecRef.edition, and effective ΓFoldRef that were resolved; and the available claim scope, selected slices, qualification window, and intended result. Identify any required value that remains missing or unresolved. MUST record the aggregated measure if Fold_Γ returned one.
    • MUST record the evidence refs used to admit the measure set and evaluate FoldEligibility_Γ.
    • If GammaFoldSlot resolves via an override, SHOULD record the override’s policy-id (or its stable ref) alongside ΓFoldRef.
    • When MinimalEvidenceSlot? is present, MUST record its resolved MinimalEvidenceRef or identify the override as unresolved. When no override is supplied, MUST cite the resolved CGSpecSlot.MinimalEvidence or identify the default policy as missing or unresolved.
    • When ContributorSetSlot? is produced, SHOULD record it (or an id reference) as an auditable explanation surface.
    • SHOULD record: any UNM invocation ids/pins when folding presumes a compare‑on‑invariants surface established by UNM.
    • SHOULD record: an F.9 Bridge, kind relation, aggregation or membership relation, or plane relation only when the fold or receiving use relies on that obtaining relation.
    • SHOULD record: the evaluated GuardDecision (especially when not pass) and, when applicable, the effective evidence policy / failure behavior reference used to justify degrade|abstain.

A.19.ULSAM:4.2 - Interpretation notes (didactic, informative)

  • Identify the fold and its governing conditions. The fold is the aggregation rule; ΓFoldRef identifies the selected rule. GammaFoldSlot MUST be resolvable to CGSpecSlot.Γ_fold routing or a pinned override. A calculation can still have occurred without that citation, but its conformance and reuse basis remain unresolved until the rule is recovered.
  • ULSAM is not normalization. ULSAM does not establish comparability by itself: it does not normalize, rescale, or “align units” as a hidden convenience. If a compare‑on‑invariants surface is required, invoke UNM upstream and cite the effective pins in Audit.
  • Keep separate measures when sufficient. If separate measures answer the receiving question, keep them separate. Use CPM for a needed comparison and SelectorMechanism for a needed selection, under their declared partial-order and set-return rules. A fold can discard distinctions; state which distinctions the declared fold preserves and loses.
  • Recover the actual contributors. Existing input and calculation content may already establish the contributor subset; use the optional ContributorSet output when it supplies needed recoverability. Equal numbers from different contributors remain distinct measures: two boxes each measured as 2 kg contribute twice to their total, rather than collapsing to the bare set {2}. Conversely, copying the assertion about one box does not make two boxes or authorize counting its mass twice. Any ordering, multiplicity or weight consumed by the fold must be declared in its grouping basis or rule. Excluding a contributor may change a total into a partial total; retain that distinction in the result instead of treating missing input as zero.
  • Time-fold is a specialization, not a loophole. The base ULSAM declares Γ_timePolicy and allows time-fold only via explicit windowing policy. If a project needs an explicit FoldTime_Γ operator, declare it with its additional operation and arguments, preserve inherited meanings and test the claimed extension under A.6.1 §4.8. The local ⊑⁺ label alone establishes no preservation result.
    • Use the suite lexicon token GammaTimeRuleSlot for the additional windowing rule input; do not overload GammaFoldSlot or invent a generic context input to carry time semantics.

A.19.ULSAM:5 - Archetypal grounding (didactic, informative)

A.19.ULSAM:5.1 - Tell

  • In CHR, ULSAM exists to keep the stage fold_Γ? explicit: if a pipeline wants folding, it invokes ULSAM.Fold_Γ; otherwise it skips the stage. Folding MUST NOT be smuggled into USCM.Score, CPM.Compare, or SelectorMechanism.Select.
  • For a U.System decision: ULSAM folds the admitted measures about the named System, under the declared grouping or membership basis and CG-Spec fold policy, only when that aggregate result is needed.
  • For a U.Episteme assessment: ULSAM folds the admitted evidential or measurement set about that episteme into an aggregate coordinate, using an aggregation model justified for that quantity and support dependence; reliability-like wording alone supplies no weakest-link law.

A.19.ULSAM:5.2 - Show

Scenario A (manager-facing): assess a proposed aggregate readiness measure.

  1. A CHR pipeline produces a set of admitted measures (post-USCM or directly from characteristic measures): MeasureSetSlot = {m₁, m₂, …, m_k}.
  2. The team wants a single “readiness” measure m_ready to be used as an input to later comparison/selection. Define the question this aggregate would answer and its acceptance or comparison use; a readiness label supplies no aggregation law.
  3. Before folding, answer:
    • Admissibility: Is the fold admissible under CGSpecSlot.SCP (units/scale) and CGSpecSlot.Γ_fold (declared fold kinds)?
    • Evidence: Is the evidence posture sufficient under MinimalEvidence? If not, do we degrade or abstain?
    • Policy identity: What is the identity of the fold (which ΓFoldRef, which edition)?
  4. When those conditions hold, the application computes: Fold_Γ(MeasureSetSlot, CNSpecSlot, CGSpecSlot, GammaFoldSlot, MinimalEvidenceSlot?) → (AggregatedMeasureSlot, ContributorSetSlot?). The audit records ΓFoldRef and makes the actual contributors recoverable, with the optional contributor output when needed. If no justified fold answers the readiness question, retain the separate measures and their criteria.

Scenario B (engineer-facing): proposed aggregation across different bases.

  • A project tries to fold measures with different bearers, membership rules, scales, comparison bases, or reference planes. ULSAM first checks whether one admitted set and lawful fold can be stated. If the conclusion relies on an F.9 Bridge, kind relation, aggregation or membership relation, or plane relation, the project cites that obtaining relation and its loss. If a required relation is absent or unresolved, keep independently supported folds separate or abstain from the dependent fold.

A.19.ULSAM:6 - Bias-Annotation (informative)

This pattern biases CHR authoring toward explicit aggregation boundaries and against “scalarization by convenience”.

  • Gov (governance). Bias toward auditable folds (editions, effective ΓFoldRef, contributor surfaces). Risk: perceived overhead. Mitigation: keep the signature stable and move method specifics to SoTA wiring.
  • Arch (architecture). Bias toward keeping fold_Γ a distinct stage (no leakage into score/compare/select). Risk: longer pipelines. Mitigation: the stage is optional (fold_Γ?) and can be omitted when not required.
  • Onto/Epist (ontology/epistemology). Bias toward scale-lawful aggregation (no illegal ordinal arithmetic; SCP-bound). Risk: forbids many informal “single-number” habits. Mitigation: retain separate measures when sufficient; use partial-order comparison or set-return selection when the receiving question needs it.
  • Prag (practice). Bias toward policy-bound defaults (no “implementation default Γ‑fold”). Risk: teams must name policies. Mitigation: provide conservative defaults in CG‑Spec.Γ_fold and keep overrides explicit.

A.19.ULSAM:7 - Conformance Checklist (normative)

IDRequirement
CC‑A19ULSAM‑0Mechanism declaration completeness: §4.1 MUST supply the A.6.1 operation-local arguments/results, application predicates, identity/extent rules, laws and admissibility/applicability conditions. SlotIndex projects those declarations.
CC‑A19ULSAM‑1Single governing pattern: the ULSAM declaration is governed by §4.1; a use cites it rather than inferring semantics from a copied summary.
CC‑A19ULSAM‑2No hidden aggregation: any Γ‑fold MUST be explicit as ULSAM.Fold_Γ (no folding hidden inside Score/Compare/Select, including inside USCM/CPM/SelectorMechanism).
CC‑A19ULSAM‑3Scale-lawfulness: a conformant ULSAM fold MUST be CSLC-lawful and admissible under CGSpecSlot.SCP. Ordinal arithmetic is forbidden unless explicitly allowed by the relevant CSLC fragment.
CC‑A19ULSAM‑4Γ‑fold admissibility: a conformant ULSAM publication MUST ensure GammaFoldSlot resolves to CGSpecSlot.Γ_fold or a pinned override (CAL policy). “Implementation default fold” is non-conformant.
CC‑A19ULSAM‑5Evidence gating: a conformant ULSAM publication MUST guard folding via FoldEligibility_Γ with `GuardDecision ∈ {pass
CC‑A19ULSAM‑6SlotKind discipline: SlotKind tokens used in the ULSAM intension MUST come from the CHR SlotKind Lexicon (A.19.CHR:4.2.1). New SlotKinds require lexicon extension first.
CC‑A19ULSAM‑7Audit surface: Audit MUST record the resolved CNSpecRef.edition, CGSpecRef.edition, and effective ΓFoldRef; and MUST record a resolved MinimalEvidenceRef when overridden, or the resolved CGSpecSlot.MinimalEvidence otherwise. Identify missing or unresolved required values as such.
CC‑A19ULSAM‑8Contributor accountability: when ContributorSetSlot? is produced, it SHOULD be recorded (or referenced by stable id) as an explanation surface for what contributed after admissibility/evidence gating.
CC‑A19ULSAM‑9P2W separation: on a P2W path, the A.15.2 baseline MUST select the intended fold/evidence policies and editions. A.15.3 typed filling applies only to independently declared positions. Fold_Γ bindings MUST obtain under §4.1 and remain distinct from planned values and their Audit representation.
CC‑A19ULSAM‑10Gate/guard separation: ULSAM MUST NOT embed GateDecision/GateLog or publish/telemetry operations in the fold_Γ? stage; admissibility is via FoldEligibility_Γ (tri‑state) and run‑time observability via Audit pins only.
CC‑A19ULSAM‑11No implicit UNM: ULSAM MUST NOT silently normalize/rescale to force comparability. When normalized inputs are required, cite the upstream directed result and preservation/loss basis in Audit. A class-level fold also needs compatibility, partial-availability and receiving-query recovery under A.19.UNM; invoking UNM alone supplies none of them.

A.19.ULSAM:8 - Common anti-patterns (didactic, informative)

Anti-patternSymptomWhy it fails in FPFHow to avoid
Hidden rollup inside scoring“Our score already averages everything.”Violates the “no hidden aggregation” law and hides Γ‑fold identity.Keep USCM.Score scoring-only; use ULSAM.Fold_Γ as a stage.
Averaging ordinalsMeans on ranks/levelsIllegal under CSLC/SCP unless explicitly allowed.Keep ordinal outputs as ordinal; use CPM if a comparison is needed; if folding is required, use an ordinal-legal fold declared by Γ_fold policy.
Implementation default Γ‑fold“If not specified, we use X.”Breaks replayability and violates Γ‑fold admissibility.Require GammaFoldSlot to resolve to CGSpecSlot.Γ_fold or pinned override.
Coercing unknown to a number“Missing metric becomes 0.”Violates tri-state guard discipline; silently changes meaning.Use FoldEligibility_Γ with `{pass
Folding after the admitted set or basis changedMeasures with different bearers, membership rules, scales, scopes or windows, comparison bases, or planes are folded “as-is”The result no longer follows from one declared set and lawful fold; relation labels cannot repair that gap.Re-establish the admitted set and eligibility. Cite an obtaining relation and supported loss only when the fold or receiving use relies on it. If a required relation is absent or unresolved, keep independently supported folds separate or abstain from the dependent fold.
Treating fold_Γ as mandatoryAlways folding even when not neededUnnecessary aggregation can hide distinctions needed by the receiving use.Keep fold_Γ? optional in protocols; retain separate measures when sufficient, and use CPM or SelectorMechanism for a needed comparison or selection.

A.19.ULSAM:9 - Consequences (didactic, informative)

BenefitsCosts / trade-offs
Clear separation of concerns: folding is explicit and auditable.Adds a step; authors must name Γ‑fold policies.
Exposes the scale and model conditions that an admitted aggregate must satisfy.Some familiar heuristics become non-conformant.
Improves evolvability: folding methods evolve via wiring, while the kernel signature stays stable.Requires discipline to keep method specifics out of kernel prose.
Supports evidence-aware aggregation via tri-state guards.Guard + Audit expectations may feel heavier than ad-hoc aggregation.

A.19.ULSAM:10 - Rationale (didactic, informative)

Aggregation is a semantic commitment: it changes a set/vector of measures into a single measure, and therefore changes what later comparison/selection can legitimately claim. In CHR, that commitment must be explicit, admissibility-gated, and auditable.

Keeping ULSAM as its own mechanism preserves:

  • the boundary between method choice (SoTA packs) and operation declaration,
  • the boundary between planned baseline (pins chosen in WorkPlanning) and run-time audit (what executed),
  • and the engineer-facing clarity that “we folded here, not everywhere”.

A.19.ULSAM:11 - Typical uses (didactic, informative)

  • CHR suite optional stage fold_Γ? (never hidden).
  • Folding a trust/assurance quantity only under its justified model and applicable policy; a declared default alone supplies no numerical warrant.
  • Any project that requires an auditable “roll-up” measure prior to lawful comparison/selection.
  • In E.18 transformation-flow structures, the planned baseline selects the fold and evidence-policy editions for a ULSAM mechanism-instance node. Argument bindings obtain under §4.1; Audit records the effective references.

A.19.ULSAM:12 - Builds on / Relates to

Builds on (cite, don’t duplicate).

  • A.6.1 (operation declarations and application/binding rules).
  • A.6.1 §4.2 (operation-local argument/result declarations as the source of SlotIndex).
  • A.19.CHR (CHR suite boundary; stage fold_Γ?; CHR SlotKind Lexicon).
  • G.0 (CG-Spec.Γ_fold, CG-Spec.SCP, CG-Spec.MinimalEvidence; fold, admissibility and evidence conditions).
  • A.18 (CSLC).
  • B.3 (support dependence and the justified model for any R_eff calculation).

Relates to (coordination, not governing-pattern assignment).

  • A.19.CN (CN‑Spec), via CNSpecSlot.acceptance gating in admissibility.
  • A.19.UINDM, A.19.USCM, A.19.CPM, and A.19.SelectorMechanism as adjacent CHR stages (Uses contour; no governing-pattern assignment transfer).
  • Part G SoTA packs and wiring (G.2 + G.*:Ext.*) for method family selection and edition/policy binding.

A.19.ULSAM:13 - SoTA-Echoing (informative)

SoTA here is treated as method-family source publications and G.2 claim sheets to be wired through G.*:Ext.* wiring, not as kernel semantics. ULSAM’s contribution is the stable boundary: explicit, admissible, auditable folding.

These source lines inform candidate methods. Their use still requires the selected quantity, fold and admission conditions; the examples do not establish a universally preferred aggregation.

SoTA practice pointer (post‑2015+)Primary sourceWhere it connectsAdoption status
Permutation‑invariant set aggregation as a method family (set → summary)Zaheer et al., “Deep Sets” (2017) A19ULSAM-1Candidate ΓFold families can include permutation‑invariant folds; ULSAM keeps them admissibility-gated and policy-pinned.Adapt (keep admissibility/pins explicit; do not treat learned folds as implicit defaults).
Attention-based permutation‑invariant set aggregation as a method familyLee et al., “Set Transformer” (2019) A19ULSAM-4Alternative learnable set folds (pooling by attention); still requires policy binding and admissibility gating.Adapt (publish as method family in SoTA pack; pin editions/policies; keep kernel unchanged).
Choosing a risk-aware objective under distributional uncertaintyRahimian & Mehrotra, “Distributionally Robust Optimization: A Review” (2019) A19ULSAM-2The optimization framework is not itself a fold over these measures. A receiving application identifies the particular risk quantity and operation, then establishes its aggregation law and conditions.Adapt (policy‑bound and SCP/CSLC‑gated).
Governing-pattern discipline for architectural statementsISO/IEC/IEEE 42010:2022 A19ULSAM-3FPF adapts architecture-description distinctions to governing-pattern references; the one-pattern assignment is an FPF design choice.Adapt (local FPF pattern assignment, not a rule attributed to the standard).

A.19.ULSAM:End

A.19.CPM - Compare Admitted Profiles under a Declared Comparator

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) This pattern declares the CPM comparison operations under A.6.1. Their applications, evidence use and any dated Work retain the separate conditions in §4.1.

A.19.CPM:0 - At a glance (didactic, informative)

CPM is the CHR comparison kernel: it compares two admitted profiles under an explicit, admissibility‑gated comparator and returns a set‑valued comparison outcome.

Purpose. CPM answers: “Given two admitted profiles and an explicit comparator, what relation holds under the declared admissibility frame?” It does not answer: “Which one should we pick?” (selection) nor “What is the score?” (scoring).

Use this when. Two admitted profiles must be compared under a declared rule. Recover their value meanings, select the admitted comparator and test its use conditions. Return only justified relation tokens when comparison proceeds; retain the eligibility judgment and withhold a comparison result when it must abstain. If this answers the receiving question, stop without adding selection or authorization.

What this buys. A completed admitted comparison gives the practitioner one set-valued outcome that downstream selection can consume. The Compare application keeps the profile pair, comparator, claim scope and selected context slices, optional A.19 predicate, reference plane, evaluation window, policies, and output binding recoverable. Partial order, incomparability, missing evidence, and scale limits remain explicit instead of becoming a hidden scalar winner.

First output. When comparison returns a result, read the by-value set bound to ComparisonResultSlot: only the relation or poset tokens. Read comparator, comparison scope, predicate when used, plane, window, eligibility value, and evidence use from the operation application and their neighboring relations; they are not fields hidden inside the output.

Manager quick checklist (before you trust a comparison):

  • Comparator is explicit: do we have a ComparatorSpecRef, and is it admitted by CG‑Spec.ComparatorSet?

  • Admissibility is declared: do we cite CG-Spec and any required SCP, and restrict a degraded result to a lawful outcome explicitly permitted by the failure policy?

  • Evidence is not faked: are missing or unknown inputs treated as degrade|abstain under the effective MinimalEvidence policy (never as pass)?

  • Partiality is preserved: are we willing to accept incomparability and ties as first‑class outcomes (set‑valued result), rather than forcing a winner?

  • Suite stage: compare (pipeline order lives in A.19.CHR:4.5, not in the mechanisms[] enumeration).

  • Input (conceptual): left profile, right profile, CN-Spec, CG-Spec, an explicit ComparatorSpec, one U.ClaimScope with selected A.2.6 U.ContextSlice members, an optional A.19 CharacteristicSpacePredicate when the comparison depends on one, effective reference plane, explicit evaluation window, and optional MinimalEvidence override.

  • Output (conceptual): the by-value ComparisonResultSlot set of relation or poset tokens.

  • Planned use: an A.15.2 baseline selects ComparatorSpecRef editions and policy ids. A.15.3 and SlotFillingsPlanItem apply only to independently declared receiving positions under A.19.CHR:4.7.2. The Compare application carries its argument and result bindings under §4.1. Any dated comparison Work and A.10 evidence-provenance account retain their independent grounds.

  • Reproducible comparisons: for parity and benchmark style runs that require a stable run package plus report record (editions, windows, parity pins), use G.9 (Parity and Benchmark Harness). CPM stays kernel-only.

  • Core safety commitments: admissibility gate via CG-Spec.ComparatorSet + CG-Spec.SCP + CSLC; tri-state admissibility (pass|degrade|abstain); unknown never coerces to “pass” or to a fabricated outcome; no silent scalarization or totalization.

  • Where method details live: in editions of ComparatorSpec and their SoTA wiring (Part G packs and extensions), not inside CPM’s kernel semantics.

  • Quick rule of thumb: use USCM when you need scores from a declared scoring method and SelectorMechanism when you need a selected candidate set. Obtaining measured values follows the C.16 measurement method; normalization follows UNM. CPM compares admitted profiles and returns relation tokens.

A.19.CPM:1 - Problem frame

FPF’s Characterization (CHR) suite treats comparison as a distinct mechanism stage (compare) with suite‑wide obligations that forbid hidden scalarization or totalization, require tri‑state guards, and enforce admissibility declarations for numeric operations. Comparison must therefore be described as:

  • a mechanism (an operation declaration under A.6.1),
  • that is suite‑conformant (per CHR obligations and protocol closure in A.19.CHR),
  • whose profile admission and comparability follow CN-Spec, and whose comparator admissibility follows CG-Spec.

Within suite protocols, CPM appears as the explicit compare stage: it consumes admitted left and right profiles, including scores and folded measures when those upstream stages are present, and produces an admissible, replayable comparison result that downstream selection can consume without CPM smuggling selection or scoring semantics into comparison.

A.19.CPM:2 - Problem

Engineering teams frequently need to compare two options (designs, methods, vendors, trajectories, hypotheses, etc.) across multiple measures and under incomplete evidence. Without a comparison mechanism, teams fall into one or more of these failure modes:

  • Hidden scalarization: forcing a single number (or a single winner) from multi‑criteria reality, erasing incomparability and ties.
  • Silent totalization: inventing an implied total order by convenience tie‑breakers or implicit thresholds, even when only a partial order is warranted.
  • Inadmissible arithmetic: comparing across measures using operations that are not scale-admissible (CSLC‑violating) or not admitted by the declared admissibility frame.
  • Comparator drift: the comparison rule or selected edition is unresolved, so teams can use different rules for the same profiles. Explicit prose or code can supply the rule when its meaning and edition are recoverable.
  • Unknown coercion: missing or unknown evidence is coerced into an outcome (e.g., missing = equal), producing comparisons that look decisive but are epistemically unsafe.
  • Comparison-boundary drift: the same result label is reused after the profile pair, comparator, A.19 predicate, claim scope, selected context slices, reference plane, or evaluation window changed.
  • Cross-scheme or cross-plane leakage: a comparison relies on a semantic relation between two F.17 SchemeSenseCell values without an obtaining F.9 Bridge and its separate bounded-use claim, or crosses ReferencePlanes without the plane relation and policy. The relation or policy needed by the comparison is then unrecoverable.

CPM exists to make comparison explicit, admissibility-gated, set-valued, and replayable, so downstream selection can remain a separate policy-bound step.

A.19.CPM:3 - Forces

  1. Usability vs correctness: engineers want a “simple compare” function; correctness demands that admissibility, comparator choice, and handling of incomparability and unknown evidence be explicit.
  2. Total order convenience vs partial order truth: total orders simplify downstream selection; partial orders are often the faithful representation (especially in multi‑criteria settings).
  3. Evolvability vs stability: comparator methods evolve (SoTA churn); kernel semantics and slot field sets must remain stable and wiring‑friendly.
  4. Replayability vs speed of discussion: teams want fast decisions; replay requires the Compare or CompareEligibility application, its edition, policy and argument bindings, and its returned value or explicit absence. Recover dated comparison U.Work and the A.10 evidence-provenance path when the account asserts them or the receiving use consumes them, under §4.1.
  5. Cross-scheme reasoning vs Bridge and ReferencePlane discipline: a comparison that relies on a semantic relation between two F.17 SchemeSenseCell values requires an obtaining F.9 Bridge and a separate C.2.1 bounded-use claim; a plane-only crossing requires the ReferencePlane relation and policy. Neither branch supplies scope, predicate, plane, or time from an umbrella context label.
  6. Semantic consistency vs duplicate definitions: suite references, A.6.1 archetypes and Part G wiring need one governing CPM definition.

A.19.CPM:4 - Solution

CPM is an A.6.1 U.Mechanism declaration whose core commitments are:

  • Comparator admissibility is declared and gated (CG-Spec.ComparatorSet, and CG-Spec.SCP when numeric operations are involved; scale admissibility via CSLC).
  • Results are set‑valued relation or poset tokens; partial orders remain partial; no silent scalarization or totalization.
  • Admissibility is tri‑state and fail‑closed on missing admissibility and evidence; unknown never coerces into a fabricated outcome.
  • Comparison remains distinct from selection; CPM produces relation outcomes; SelectorMechanism consumes them.

This pattern defines:

  1. a stable mechanism boundary for admissible comparison: Compare(...) → ComparisonResultSlot plus a tri‑state CompareEligibility guard;
  2. a stable SlotKind field set (by suite lexicon tokens) that downstream selection and Part‑G wiring can rely on without SlotKind drift;
  3. an admissibility and evidence responsibility split: admissibility is gated by CG-Spec (and CSLC), while admission and comparability relations are cited from CN-Spec;
  4. a minimal replay basis: the identified Compare or CompareEligibility application, its bound arguments and returned value or explicit absence, with an A.10 evidence-provenance path when the receiving reliance requires it;
  5. planned and actual use: on a P2W path an A.15.2 plan selects editions and policies; A.15.3 typed filling applies to independently declared receiving positions. Actual arguments and results belong to the comparison application; a dated U.Work claim is independently governed;
  6. a comparison-use boundary: claim scope, selected A.2.6 context slices, optional A.19 predicate, reference plane, and evaluation window are occurrence bindings, not generic context, comparator content, output fields, or an optional model-use structure.

A.19.CPM:4.1 - Operation declaration (normative)

CPM.IntensionRef cites the A.6.1 declaration episteme presented here. CHR resolves compare to its local Compare operation. A changed argument, comparator law or guard requires explicit selection of the changed declaration; another realizer of the same declaration changes no suite member.

  • Declaration boundary: this A.6.1 mechanism intension declares Compare and CompareEligibility. Applications and their bindings are established separately under the rules below.

    • Planned use: A.15.2 selects the editions and policies for a proposed comparison. If a receiving position is independently declared, A.15.3 can specify its planned filling. Neither plan asserts an actual Compare argument or result binding.
  • IntensionHeader: id = CPM, version = 1.0.0, status = stable.

  • IntensionRef: CPM.IntensionRef designates this U.Mechanism episteme as the suite member named in A.19.CHR:4.2; it is not the EntityOfConcernRef of the declared operation family.

  • SignatureManifest (optional; importability): if a CPM publication is intended for reuse beyond the CHR suite, author SHOULD publish a SignatureManifest that records (i) the declared Compare stage‑op signature, (ii) the SlotKind field set (by lexicon tokens), and (iii) the set‑valued output commitment (no silent scalarization or totalization).

  • Purpose: admissible comparison producing set‑valued parity or poset outcomes (not a single scalar).

  • Imports: G.0 (CG‑Spec.ComparatorSet, CG‑Spec.SCP, CG‑Spec.MinimalEvidence), A.18 (CSLC), A.19.CN (comparability and admission declarations), A.19.CHR:4.2.1 (CHR SlotKind Lexicon).

  • EntityOfConcernRef: the comparison operation family declared by Compare and CompareEligibility in this section.

  • Effective reference scheme: the CHR suite reference scheme in which the A.19.CHR SlotKind lexicon, CN-Spec, CG-Spec, and ComparatorSpec tokens are interpreted.

  • Direct signature components:

    • SubjectKind: ReadingContent, supplied by the reading contents in the left and right profiles.
    • RangedValueKind: CHR-typed profile values in a CG-Frame (see CG-Spec.ComparatorSet).
    • Results are declared per operation: a set of relation/poset tokens and a separate eligibility judgment.
    • Input qualification: bind the left and right profiles to be compared. The U.ClaimScope states when claims about comparing them apply. Check that the selected U.ContextSlice values belong to that scope under A.2.6. The extent of the calculation is determined separately.

    These are direct A.6.0 declaration components.

Reading range. ReadingContent and profile interpretation come from C.16:5.5.1. Resolve each component’s subject, Characteristic, Scale, attribution and conditions before using its values. A content member can be conditional or insufficiently supported; this operation’s eligibility and evidence rules still decide whether it may be used. Profiles retain the positions or contributor identities, ordering and multiplicity required by their declared basis. An independently materialized result episteme is distinct from the calculated Coordinate and the bound reading content.

Operation-local argument and result declarations

Each argument meaning is declared separately for Compare and CompareEligibility. ByRef means one reference to the stated value and edition; ByValue carries the value itself. Cardinality is per application. A guard can assess an incomplete proposal with 0..1 of each required argument; a missing argument has no binding and prevents pass.

DirectionLocal designatorMeaning and ValueKindDesignation; cardinality
ArgumentLeftProfileSlotLeft operand: profile of ReadingContent components with their basis positions, Characteristic and ScaleByValue; 1 profile
ArgumentRightProfileSlotRight operand of the same kind, matched by the comparator or a separately justified basis mappingByValue; 1 profile
ArgumentCNSpecSlotCN-Spec governing admission and comparability of the operand pairCNSpecRef; 1
ArgumentCGSpecSlotCG-Spec governing comparator admission, SCP and default evidence conditionsCGSpecRef; 1
ArgumentComparatorSpecSlotComparatorSpec supplying the comparison rule and any thresholds or tie-breakersComparatorSpecRef; 1
ArgumentMinimalEvidenceSlotMinimalEvidence override used instead of CGSpecSlot.MinimalEvidenceMinimalEvidenceRef; 0..1
ArgumentclaimScopeU.ClaimScope specifying the cases in which the comparison claim applies. The two profile slots identify what is compared.ByRef; 1
ArgumentselectedSlicesSet of selected U.ContextSlice members of claimScope under A.2.6ByValue set of slice references; 1 set
ArgumentcharacteristicPredicateA.19 CharacteristicSpacePredicate used to restrict this comparison, if anyByValue; 0..1, explicitly absent when unused
ArgumentreferenceSchemeEpistemeInterpretationScheme (C.2.1:4.1.2), governing this comparisonByRef through C.2.1 SchemeDesignation; 1
ArgumentreferencePlaneCHR:ReferencePlane value qualifying the comparisonByValue; 1
ArgumentevaluationTimeEvaluation point or interval in the declared time basis, qualifying what is comparedByValue; 1
Compare resultComparisonResultSlotSet of relation or poset tokens returned by the declared comparatorByValue; 1 set on completed admitted comparison, 0 without a result
CompareEligibility resultGuardDecisionJudgment determined by the eligibility predicates: pass, degrade or abstainByValue; 1 on completed evaluation

Resolve the scheme designation under C.2.1:4.2.6 to one rule collection, then check its C.2.1:4.1.2 range and the rules needed by these comparison inputs. The reference token is not the bound scheme. An unresolved required interpretation cannot support a completed admitted comparison; apply the guard and abstention rules below.

Membership alone supplies neither successful comparison nor a cross-scheme correspondence. The application and result bindings below remain independently required.

The argument bindingPredicate for each row holds when that application uses the resolved value for the row’s meaning: operand, comparison/admission rule, evidence condition or explicit comparison-use restriction. A scope, predicate or time appearing in nearby metadata is not bound unless it qualifies this comparison/evaluation. Each indicator-derived profile retains its selected UINDM positions and A.19 basis; equal indices or Characteristic names alone do not establish the comparator’s required position/Scale match.

The ComparisonResultSlot bindingPredicate holds when that Compare application returns the comparator’s lawful set-valued outcome for its bound operands and use restrictions. The guard’s result predicate holds when that CompareEligibility application returns its evaluated judgment. Type compatibility, equal tokens or a copied audit record establish neither return.

A.6.1 governs binding identity and continuous extent within the application; result binding begins at return. Evidence use and a result episteme remain separate relations or objects.

SlotIndex (derived projection). Project the above designators, ValueKinds, designation and cardinalities; the historical Slot suffix supports CHR lookup. The comparison-use arguments are declaration-local names, not new CHR SlotKinds. A.6.5 relation SlotSpecs are not the source of these operation meanings.

OperationAlgebra. The compare stage resolves to Compare with the six profile/specification arguments and the comparison-use arguments above, returning ComparisonResultSlot. CompareEligibility uses those argument meanings to return GuardDecision.

ApplicationPredicate. Compare obtains when a comparison act applies the bound comparator to the bound left/right profiles under the bound scope, slices, optional predicate, scheme, plane and evaluation time, with its admission conditions satisfied by pass or an explicitly permitted degrade branch. A completed act returns the comparator’s token set. CompareEligibility obtains when an evaluation assesses that proposal under the guard predicates and returns its judgment. An unexecuted proposal, passing guard or compatible saved token set does not establish a Compare act.

ApplicationIdentityRule. One application is one comparator invocation or guard-evaluation invocation at its calculation locus, from taking up its operands/rules through return or termination. Reidentification requires that same episode. Two independently begun invocations are distinct even if all their bindings and results agree. Law 7 also distinguishes a newly evaluated comparison after any listed binding changes; it cannot mutate a completed earlier application.

ApplicationExtentRule. Compare extends from use of the chosen operand pair under the comparator to token-set return or termination; CompareEligibility extends from proposal assessment to judgment or termination. An unfinished act has an open extent and no unreturned result binding.

These calculation intervals can occur after, and can be repeated for, the same evaluationTime. A trace identifier only designates an established episode. Ordinary comparison mathematics creates no dated U.Work claim.

For example, an admitted Pareto comparison takes supplier A with cost 10 and quality 0.8, and B with cost 12 and quality 0.9, under declared lower-cost/higher-quality criteria. Neither dominates the other. Two separate invocations for the same procurement evaluation interval can return the same incomparability token set, while each has its own application and result binding. A stored compatible set does not determine which invocation returned it; the claimed binding requires that invocation’s return. Describing the first comparison twice still identifies one application.

  • LawSet (minimum; set-valued comparison, no hidden scalarization):

    1. ComparatorSet gate: ComparatorSpecSlot MUST be an element of CGSpecSlot.ComparatorSet (admissibility gate; cite G.0).
    2. Set‑valued semantics: ComparisonResultSlot is set‑valued (parity or poset tokens); partial orders remain partial — no silent totalization or scalarization.
    3. CSLC+SCP admissibility: any numeric ops implied by the comparator MUST be admissible under CGSpecSlot.SCP and CSLC-admissible (cite G.0 + A.18).
    4. Unknown is not coerced: missing or unknown evidence MUST NOT be mapped to a comparison outcome; use tri‑state guards.
    5. No hidden thresholds or tie-breakers: any thresholds, epsilons, priority orders, or tie-break logic MUST live in the declared ComparatorSpecSlot, or in CNSpecSlot.acceptance as explicit acceptance clauses, and be edition-pinned for replay; CPM MUST NOT smuggle constants.
    6. No implicit UNM: CPM does not normalize or align internally. Normalization-based comparability requires already-normalized inputs, upstream refs and preservation of the distinctions used by this comparator. If it consumes classes, its query must be constant on them; an inherited operation needs its compatibility/availability argument. Missing support yields degrade or abstain under the declared rule.
    7. Binding changes require a new application: a Compare application does not change its profile pair, U.ClaimScope, selected context slices, optional A.19 predicate, comparator, reference scheme or plane, or evaluation window. A changed binding is a different application and requires a newly evaluated outcome.
  • AdmissibilityConditions (tri‑state guard; fail‑closed on missing admissibility and evidence):

    • CompareEligibility(LeftProfileSlot, RightProfileSlot, CNSpecSlot, CGSpecSlot, ComparatorSpecSlot, MinimalEvidenceSlot?; comparison-use bindings) → GuardDecision ∈ {pass|degrade|abstain}.
    • pass requires: (i) comparator admission and a profile pair in its declared domain; (ii) scale-admissible operations; (iii) profiles admitted to this comparison under the claim scope and selected A.2.6 context slices, whether its result is an order relation, tie or incomparability; (iv) an explicit evaluation point or interval and reference plane; (v) the bound by-value A.19 predicate is applicable and its restriction is respected when used; and (vi) satisfaction of the effective MinimalEvidence policy.
    • If CNSpecSlot.comparability is normalization‑based (compare‑on‑invariants), pass additionally requires that the inputs are already in the required invariant and normalization regime and that the declared comparator can recover its answer from those results; CPM MUST NOT “make them comparable” by silent normalization.
    • If MinimalEvidenceSlot is absent, the guard MUST evaluate evidence against CGSpecSlot.MinimalEvidence, and MUST NOT return pass when evidence is missing or unknown or fails the effective MinimalEvidence gate.
    • A degrade result requires an explicit failure policy and a defined, admitted narrower comparison whose required input meanings, operations and relations are established. Return only the tokens justified for that bounded use. An undefined comparator result or a missing relation required by every permitted outcome yields abstain; the policy cannot fabricate a relation.
  • Applicability:

    • Intended for the CHR stage compare: it may follow indicatorization or scoring and optional folding when those stages are present, and it precedes selection wherever selection occurs. It remains distinct from selection.
    • Applicable only when CGSpecSlot supplies the current admissibility and evidence-policy declarations. Missing declarations fail closed.
    • Inside the CHR suite, A.19.CHR:4.5 alone determines stage ordering and optionality; CPM does not infer order from mechanisms[].
    • Every comparison application binds one U.ClaimScope, selected A.2.6 U.ContextSlice members, optional A.19 predicate, effective reference plane, and explicit evaluation point or interval. There is no implicit latest value and no default window inherited from the predicate.
    • When a comparison relies on a semantic relation between two F.17 SchemeSenseCell values, test the F.9 BridgePredicateProfile, cite the Bridge only when its predicate obtains, and state a separate C.2.1 bounded-use claim. If the predicate is false or unresolved and that semantic relation is required, CompareEligibility cannot be pass; follow the declared degrade policy when applicable, otherwise abstain.

    A plane-only crossing instead cites the ReferencePlane relation and policy. If both facts are current, state both under their own predicates. Neither branch supplies claim scope, selected slices, predicate, comparator, or evaluation time.

  • Neighboring F.9 Bridge, C.2.1 bounded-use claim, and ReferencePlane relation and policy:

    When profiles require interpretation across different semantic contexts, resolve the two F.17 SchemeSenseCell endpoints and test one F.9 BridgePredicateProfile. For an obtaining Bridge, state its endpoints and profile separately, then state suitability for the named comparison use in a C.2.1 assertion whose EntityOfConcern is that Bridge and whose ClaimGraph carries <u,d,r,t> and polarity. Include CL or an observed-loss note only when the receiving use consumes it; permitted loss remains t in the bounded-use claim.

    For a ReferencePlane crossing, cite the plane relation and policy separately. Use A.10 when the bounded source-to-use account must remain replayable, and B.3 when a named assurance claim is current. If that assurance argument consumes a locally declared R_eff calculation, cite its domain model and calculation; neither the Bridge nor CL creates a penalty.

    Adding or changing any of these neighboring facts does not by itself change the CPM declaration.

  • Neighboring dated work, operation application, result binding, and evidence relations:

    The Compare or CompareEligibility application carries its bound argument values and the corresponding result binding, when returned. If the account also asserts dated comparison U.Work, first establish its complete A.13 core: the performing System, local agential-role kind and membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits that performance; F.6 applies afterward only for precise assignment-bound attribution. Work identity and extent are not automatically those of one operation application.

    A.2.4 governs any asserted or consumed evidence use with its own evidence claim scope and relevance window. Use A.10 for the evidence-provenance path and local RelianceDisposition when the bounded source-to-use account must remain replayable, and G.11 for any asserted or consumed source or assertion-edition currentness claim.

    A durable result episteme, when needed, is governed by C.2.1, and any current entity-identity inception claim by A.15.PROD. No universal work-result or comparison-result relation is presumed.

    To replay the comparison or eligibility evaluation, recover:

    • the profile values or upstream refs, U.ClaimScope, selected A.2.6 context slices, optional A.19 predicate, effective reference scheme and plane, and evaluation point or interval that were bound; identify any missing required argument;
    • the bound CNSpecRef.edition, CGSpecRef.edition, and effective ComparatorSpecRef, identifying any required reference that was missing;
    • the effective MinimalEvidence policy, either the explicit override or CGSpecSlot.MinimalEvidence, or the absence of a required policy;
    • the returned GuardDecision or its explicit absence and, for degrade or abstain, any current downstream-handling policy;
    • any upstream normalization dependency the comparison uses, or the absence of a required normalization result that caused degradation or abstention;
    • the ComparisonResultSlot value, or its explicit absence; any obtaining F.9 Bridge and separate C.2.1 bounded-use-claim refs consumed by this occurrence; any optional CL or observed-loss-note ref used; any ReferencePlane relation and policy refs; and, only when the comparison consumes a named assurance claim, that claim’s B.3 AssuranceResult and declared domain-model and calculation refs.

    Use G.9 when a parity or benchmark use requires a stable run package and report record. These neighboring records support replay; none is CPM declaration content.

A.19.CPM:4.2 - Interpretation notes — informative

  • The output is a value, not a replay container. The by-value set bound to ComparisonResultSlot contains relation or poset tokens only. Comparator, scope, predicate, plane, window, eligibility, evidence use, provenance, and currentness remain separate bindings or relations.
  • Set-valued output is the default. “Set‑valued” means CPM preserves incomparability, ties, and partiality as first‑class outcomes; it does not authorize silent post‑processing into a scalar or a single winner.
  • Total orders are allowed only if declared by the comparator. If a ComparatorSpec defines a total order, CPM still outputs a (singleton) set of relation tokens; the totalization is a property of the declared comparator, not an implicit kernel default.
  • Normalization is not smuggled into comparison. If CN‑Spec.comparability declares normalization‑based invariants for comparison, that dependence must be represented explicitly via the suite protocol and, where needed, Uses contours (CPM consumes admitted profiles; it does not silently normalize them).
  • Thresholds and tie-breakers are never kernel constants. If thresholds exist, they belong to explicit policies or specs such as ComparatorSpec and AcceptanceClauses. Keep their editions and effective use recoverable from the comparison application for replay.

A.19.CPM:5 - Archetypal Grounding — informative

A.19.CPM:5.1 - Tell

Think of CPM as a declaration for a replayable, relation-producing comparison operation:

  • Input: “two admitted profiles + an explicit comparator spec + declared admissibility and evidence declarations”
  • Output: “a set‑valued relation outcome that preserves incomparability and uncertainty”

CPM returns the comparison relation; candidate selection and work authorization require their own rules.

A.19.CPM:5.2 - Show (U.System) — comparing two supplier options without faking a total order

A program manager compares Supplier‑A vs Supplier‑B for a safety‑critical component. The team tracks a profile of measures (cost, lead time, defect rate, assurance, sustainability), but not all measures are comparable across regions (different reporting regimes, different units).

  • The project has a declared CN‑Spec (admission and comparability declarations) and a declared CG‑Spec that lists admissible comparators in ComparatorSet and evidence rules in MinimalEvidence.

  • The comparator is ParetoDominanceComparatorSpecRef@edition, declared in CG-Spec.ComparatorSet.

  • The application binds the two supplier profiles; the claim scope supplier options for the named component and procurement decision; its selected regulatory and reporting U.ContextSlice members under A.2.6; ComparisonPredicate = none because Pareto dominance is supplied by the comparator; the stated procurement reference plane; and the explicit comparison interval.

  • CPM runs Compare(...); a changed component, scope member, comparator, plane, or interval is another comparison rather than an update to the same output.

    • Supplier-A is better in cost but worse in defect rate, while assurance evidence is missing. The known cost/defect trade-off can justify Pareto incomparability if the declared comparator and partial-evidence policy admit that inference. Missing assurance evidence alone establishes no incomparability relation.
    • CompareEligibility returns degrade or abstain under the evidence policy. On abstain, no comparison tokens are fabricated. When an explicit degrade policy permits a bounded partial comparison, ComparisonResultSlot contains only the justified relation tokens and preserves incomparability.
  • The downstream SelectorMechanism can then return a selected set (e.g., keep both suppliers in the candidate set) rather than forcing a single winner by hidden tie‑break rules.

A.19.CPM:5.3 - Show (U.Episteme) — uncertainty‑aware comparison with set‑valued outcomes

A research lead compares two proposed methods for a system component. Both methods have performance estimates with uncertainty bounds (e.g., distributions or prediction intervals). The team uses a SoTA uncertainty quantification package (for example, a conformal prediction method) to avoid overstating confidence.

  • USCM produces score profiles that are interval‑valued (or otherwise uncertainty‑annotated) rather than point estimates.
  • The chosen comparator is uncertainty‑aware and declared as a ComparatorSpec (edition‑pinned) in CG‑Spec.ComparatorSet.
  • CompareEligibility returns its guard value separately. If comparison proceeds, CPM returns justified relation tokens such as not worse or incomparable; if it abstains, no abstain token is smuggled into ComparisonResultSlot.
  • The comparison or eligibility application, its effective comparator and evidence policy, and its returned value or explicit absence make the outcome recoverable. Use A.10 when the bounded source-to-use account must remain replayable. A dated Work account is additional only when asserted and independently grounded under §4.1.

A.19.CPM:6 - Bias-Annotation — informative

CPM makes comparator choices and failure behavior inspectable. This can expose hidden thresholds, tie-breakers or unknown coercion; the declaration alone does not establish that an application avoided them.

Typical bias risks and mitigations:

  • Comparator choice encodes value judgments. Weights, priority orders, thresholds, and “tie‑break” conventions can encode organizational bias. Declare these choices in the selected ComparatorSpec or policy, using existing prose or code when it makes their meaning and edition recoverable.
  • Systematic missingness. If evidence is systematically missing for certain contexts or groups, naive “unknown → worse” is a bias amplifier. CPM’s tri‑state guard avoids coercion; but teams must still define policy‑bound failure behavior and be explicit when abstention is acceptable.
  • Cross-scheme comparisons can embed structural unfairness. A comparison that relies on a semantic relation between two F.17 SchemeSenseCell values cites the obtaining F.9 Bridge and its separate bounded-use claim; together they expose the tested correspondence or difference and tolerated loss. A plane-only crossing cites the ReferencePlane relation and policy. Neither branch replaces comparison scope, predicate, comparator, or time.
  • Overconfidence via scalarization. Collapsing partial orders into scalars often overstates certainty and hides tradeoffs. CPM makes set-valued outcomes available to a decision maker who needs to take those tradeoffs into account.

A.19.CPM:7 - Conformance Checklist

Apply the declaration checks to a CPM publication and the application checks to a use, together with the applicable A.6.1 checks and, for CHR membership, A.19.CHR:4.3. Replay always requires the application and its local bindings. Neighboring Work, evidence-use, reliance, currentness and result-episteme checks apply only when the account asserts those objects or the receiving use consumes them:

Check IdRequirement (normative)Notes (didactic and evidence)
CC-A19CPM-0Mechanism declaration completeness. One U.Mechanism episteme, its comparison-operation-family EntityOfConcernRef, effective reference scheme, operation-local argument/result declarations, OperationAlgebra, LawSet, AdmissibilityConditions, Applicability, and optional SignatureManifest are recoverable.Applications, bindings and neighboring claims are checked separately under §4.1.
CC‑A19CPM‑1Single governing pattern. The CPM intension is governed here (A.19.CPM:4.1); other descriptions cite this section rather than restating the kernel law.Prevents near-duplicate comparison semantics from drifting.
CC‑A19CPM‑2Suite stage alignment. Compare is the canonical stage‑op for CHR stage compare; ordering and optionality are taken only from A.19.CHR:4.5.Never infer order from mechanisms[].
CC‑A19CPM‑3SlotKind discipline. SlotKind tokens follow the suite lexicon (A.19.CHR:4.2.1).No SlotKind drift across specializations and wiring.
CC‑A19CPM‑4Comparator admissibility gate. ComparatorSpecSlot ∈ CGSpecSlot.ComparatorSet is enforced (fail-closed otherwise).Admissibility is declared, not improvised.
CC‑A19CPM‑5Scale admissibility. Any numeric operations implied by the comparator are admissible under CGSpecSlot.SCP and CSLC-admissible.“Weighted sum” etc must be explicitly admissible.
CC‑A19CPM‑6Set‑valued semantics. Outputs remain set‑valued; no silent scalarization or totalization is introduced.Incomparability and ties are first‑class outcomes.
CC‑A19CPM‑7Tri‑state admissibility (fail‑closed). `CompareEligibility(…) → {passdegrade
CC‑A19CPM‑8MinimalEvidence defaulting is explicit. If MinimalEvidenceSlot? is absent, the effective evidence policy is CGSpecSlot.MinimalEvidence.Avoid “implicit evidence policy.”
CC‑A19CPM‑9Gate and guard separation + lexeme discipline. CPM does not publish GateDecision nor DecisionLog; mechanism predicates use …Eligibility (not reserved gate …Guard).Aligns with suite obligations (gate_decision_separation, guard_lexeme_reservations).
CC-A19CPM-10Bridge and reference-plane discipline. A comparison that relies on a semantic relation between two F.17 SchemeSenseCell values cites an obtaining F.9 Bridge under a satisfied BridgePredicateProfile and a separate C.2.1 bounded-use claim; a plane-only crossing cites the ReferencePlane relation and policy; both are stated when both facts are current.CL is optional. CPM supplies no default assurance penalty, fold, or R_eff; a local R_eff is admissible only for a named assurance claim under its declared domain model and calculation. These neighboring facts are not CPM declaration content.
CC-A19CPM-11Replay basis completeness. The Compare or CompareEligibility application and its bound profile, comparator, U.ClaimScope, selected A.2.6 context-slice, optional A.19 predicate, reference-scheme and plane, evaluation-window and policy arguments are recoverable, together with the corresponding returned ComparisonResultSlot or GuardDecision value or its explicit absence.If asserted or consumed, independently recover dated comparison Work through the A.13 core and A.15.1 admission in §4.1, evidence use under A.2.4, currentness under G.11 and a result episteme under C.2.1. Use A.10 when the bounded source-to-use account must remain replayable. These facts remain outside the output value.
CC-A19CPM-12Planned-filling separation. On a P2W path, an A.15.2 baseline selects intended editions and policies; A.15.3 typed filling applies only to independently declared positions. Compare applications carry their effective argument and result bindings.A dated comparison Work and any relied-on A.10 provenance remain separately established.
CC-A19CPM-13No implicit UNM. When comparability depends on normalization, CPM uses the explicit upstream directed result and preservation/loss basis. A class-level comparison also passes its query/operation conditions under A.19.UNM; a reference or equal normalized numeral alone is insufficient. Unsupported comparisons follow abstain or the declared narrower degrade use.Keeps compare-on-invariants explicit.
CC-A19CPM-14Comparison-scope completeness. Every Compare application binds one profile pair, U.ClaimScope, selected A.2.6 context slices, optional A.19 predicate, effective reference scheme and plane, and explicit evaluation point or interval.No generic context input, optional model-use structure, or label supplies these values.
CC-A19CPM-15Outcome separation. ComparisonResultSlot contains only the by-value set of relation or poset tokens; GuardDecision remains the separate eligibility value, and abstention fabricates no output token.Comparator, scope, plane, window, evidence, provenance, currentness, result episteme, and selection remain separate.
CC-A19CPM-16No generic result relation. The A.6.1 operation application binds the output; C.2.1 governs a durable result episteme when needed; subject patterns govern any other result relation.CPM mints no universal comparison-result or work-result link.

A.19.CPM:8 - Common Anti‑Patterns and How to Avoid Them

  • Anti‑pattern: “Comparison returns a score.” Symptom: Compare(x,y) returns a numeric margin or a single rank position. Avoid: keep numeric scoring in USCM; CPM returns relation tokens (set‑valued). If a numeric comparator is desired, it must be an explicit ComparatorSpec and still yields relation tokens as the kernel output.

  • Anti‑pattern: “CPM picks the winner.” Symptom: comparison logic embeds winner selection or selected-set truncation. Avoid: CPM only compares; selection is SelectorMechanism, which consumes comparison outcomes and remains policy‑bound.

  • Anti-pattern: Implicit comparator choice. Symptom: comparator choice is implicit (e.g., “we usually do lexicographic by safety then cost”), not edition‑pinned. Avoid: require an explicit ComparatorSpecRef from CG-Spec.ComparatorSet; the Compare application binds the effective edition.

  • Anti‑pattern: “GateDecision leakage.” Symptom: the compare step emits or assumes GateDecision, GateLog, or DecisionLog records as part of suite closure, or uses reserved gate‑lexemes (…Guard) for mechanism‑level predicates. Avoid: keep CompareEligibility as the mechanism-level tri-state predicate and assign gate decisions to their governing pattern.

  • Anti‑pattern: “SlotKind drift.” Symptom: renaming or re‑purposing LeftProfileSlot, RightProfileSlot, ComparatorSpecSlot, or ComparisonResultSlot in CHR mechanism descriptions and their specializations. Avoid: use the suite SlotKind lexicon (A.19.CHR:4.2.1) and keep SlotIndex as a derived projection.

  • Anti‑pattern: “Smuggling plan‑binding into CPM.” Symptom: hard‑coding comparator editions, policy ids, or “launch values” inside the CPM intension or pattern prose. Avoid: resolve the intended editions and policies, recording them in A.15.2 on a P2W path; use A.15.3 typed filling only for independently declared positions. Establish Compare bindings under §4.1.

  • Anti‑pattern: “Tie‑breakers as hidden constants.” Symptom: forced total order via untracked thresholds, epsilons, or “if equal then compare cost” logic. Avoid: make tie-break policy part of explicit comparator and acceptance policies, pin their editions, and keep their effective use in the Compare application recoverable.

  • Anti‑pattern: “Unknown coerces to outcome.” Symptom: missing evidence treated as equal, zero, or worse, producing decisive comparisons from absent information. Avoid: tri‑state guard; fail‑closed on missing evidence; explicit failure behavior via evidence policy.

  • Anti-pattern: ComparisonResultSlot as a replay record. Symptom: comparator, scope, predicate, window, evidence, or currentness fields are placed inside the set-valued output. Avoid: keep the output to relation or poset tokens; recover effective arguments from the operation application and neighboring relations.

  • Anti-pattern: Using one F.9 Bridge rule for both semantic and ReferencePlane crossings. Symptom: an F.9 Bridge is required merely because reference schemes or planes differ; the separate C.2.1 bounded-use claim is absent; or CL and a bare R_eff penalty are treated as mandatory. Avoid: cite an obtaining F.9 Bridge and separate bounded-use claim only for the semantic branch; cite the ReferencePlane relation and policy for the plane branch; state both when both facts are current. Make only consumed refs recoverable for the Compare application. Add CL only when needed. Open B.3 only for a named assurance claim, and use a local R_eff only if its declared domain model and calculation define it. Use A.2.4 for evidence-use classification and A.10 when the bounded source-to-use account must remain replayable; the crossing patterns establish their relations.

A.19.CPM:9 - Consequences

  • Improved usability: CPM gives a single, engineer‑readable place to learn “what admissible comparison means” and what it does not mean.
  • Higher replayability: comparison results remain traceable through the Compare application and its ComparisonResultSlot binding, any consumed obtaining F.9 Bridge with its separate bounded-use claim, and any ReferencePlane relation and policy. Recover dated comparison U.Work and the A.10 evidence-provenance path when the account asserts them or the receiving use consumes them.
  • Reduced semantic drift: teams cannot silently shift from Pareto to lexicographic to “weighted sum” without changing explicit comparator specs and pins.
  • Explicit tradeoffs: set-valued outcomes retain incomparability and uncertainty for downstream reasoning.
  • Cost: downstream consumers (notably selection) must handle sets, abstentions, and partial orders explicitly. This moves complexity from hidden heuristics into explicit policy‑bound mechanisms.

A.19.CPM:10 - Rationale

  1. Set‑valued by design: partial orders are common in multi‑criteria settings; pretending they are total creates false certainty and brittle decisions.
  2. ComparatorSet gating: declaring which comparisons are admissible, and under what scale or evidence rules, prevents “algorithm by convenience”.
  3. Tri‑state guards: explicit pass|degrade|abstain keeps unknown from being converted into an outcome.
  4. Comparison, scoring and selection remain separate: separating compare from score and select prevents hidden semantic coupling and improves evolvability (methods change via wiring; kernel stays stable).
  5. Single governing pattern: one governing definition lets other descriptions cite the comparison semantics they use.

A.19.CPM:11 - SoTA-Echoing

The following research lines inform comparator choices. Their methods require their own conditions; no source family alone establishes the CPM outcome or admission rule.

Concrete comparator-family SoTA packages are cited through their current Part G pack or claim sheet when one governs the use. CPM’s kernel semantics remain unchanged.

Research contributionHow it connects to CPMAdoption status in FPF
Fair ranking and constrained ranking (e.g., Zehlike et al., 2017; Biega et al., 2018)Reinforces the “no hidden tie‑breaks and thresholds” stance: fairness constraints belong in explicit comparator and acceptance policies, not as silent kernel constants.Integrate via ComparatorSpec editions in CG‑Spec.ComparatorSet + policy pins; CPM remains unchanged.
Uncertainty-aware and set-valued inference (e.g., Romano et al., 2019; Barber et al., 2021)Prediction intervals or other uncertainty results retain their own semantics. A declared comparator determines which relation tokens follow; an interval is neither a CPM token set nor by itself a reason for abstention.Model as comparator families (or supporting method families) packaged in G.2; wired into declared ComparatorSpec.
Differentiable sorting and learned comparators (e.g., Grover et al., 2019; Blondel et al., 2020)Replay and drift assessment use the learned ComparatorSpec edition and the comparison’s policy, argument and result bindings. Add an A.10 evidence-provenance account when the bounded source-to-use grounds must remain replayable.Use a sorting or learned-comparison component only under a ComparatorSpec that establishes the returned relation semantics and required conditions; an algorithm label is insufficient.

A.19.CPM:12 - Relations

Builds on and cites (non‑exhaustive):

  • A.6.1 (operation declarations and application/binding rules)
  • A.6.1 §4.2 (operation-local argument/result meanings and binding rules; SlotIndex projects those declarations)
  • A.19.CHR (suite membership + obligations + suite_protocols; CHR SlotKind lexicon)
  • A.15.2 for the edition/policy baseline on P2W paths; A.15.3 plus A.19.CHR:4.7.2 for typed filling of independently declared positions.
  • A.19 for CharacteristicSpace and the optional by-value CharacteristicSpacePredicate used by one comparison
  • A.2.6 for U.ClaimScope identity and U.ContextSlice membership
  • A.19.CN for CN-Spec comparability plus acceptance and admission declarations
  • G.0 (CG‑Spec: ComparatorSet, SCP, MinimalEvidence, CL and ReferencePlane framing)
  • A.18 (CSLC scale admissibility)
  • C.27.TA for an explicit comparison-evaluation point or interval
  • A.2.4, A.10, and G.11 for evidence-use scope, provenance, and currentness, separately from comparison scope and outcome
  • E.10 (lexical and ontological authoring rules; kind suffix discipline)
  • E.19 (checks; authoring discipline)
  • E.20 for mechanism introduction or revision and governing-definition assignment
  • F.18 (alias docking; ID continuity)
  • E.18 for a selected transformation-flow structure that includes a CPM comparison

Relates to (typical named patterns in the CHR Uses contour):

  • UNM.IntensionRef, UINDM.IntensionRef, USCM.IntensionRef, ULSAM.IntensionRef, and SelectorMechanism.IntensionRef (downstream consumer of CPM results).
  • G.5 (selection conformance), G.9 (parity and benchmark harness), G.10 for Part-G pack shipping and E.24.PUB for episteme availability, form or carrier claims. Publication and telemetry remain outside suite closure.

A.19.CPM:End

A.19.SelectorMechanism - Selection Kernel

Type: Architectural (A) Status: Stable Normativity: Normative (unless marked informative) This pattern declares Select and SelectEligibility under A.6.1. Applications and any separately asserted Work use the conditions in §4.1.

A.19.SelectorMechanism:0 - At a glance — didactic, informative

  • What it is: a universal set-returning selection kernel: it takes candidates, admissible comparison outcomes, and explicit criteria, and returns a selected set, not a forced single winner.
  • Why it exists: to prevent three recurring failure modes: hidden thresholds, silent scalarization, and winner‑take‑all defaults under partial orders and uncertain evidence.
  • Use this when: admitted candidates must be selected under explicit criteria after comparison. Identify the candidate universe and choice rule, recover the required comparisons and their conditions, then return the justified subset. Stop with comparison when the receiving question needs no selection; a selection result alone supplies no authorization to act.
  • What this buys: the practitioner gets one selected-set value whose criteria, finite basis of upstream binary CPM applications, required comparison coverage, token provenance, scope, any governing A.19 predicate, plane, window, and policy bindings are explicit. degrade and abstain remain eligibility values, not selected-set members or alternative result kinds.
  • First output: read the by-value candidate set bound to SelectionSlot. Read the candidate universe, finite upstream CPM application basis, required pair coverage, derived comparison-token union, selection conditions, claim scope and context slices, reference plane, evaluation window, eligibility value, and evidence use from the Select application and neighboring relations; they are not fields inside the selected set.
  • How it evolves: method semantics and SoTA algorithm families connect via G.2 packs and wiring modules; the kernel signature stays stable and teachable.
  • Suite stage: select (ordering lives only in A.19.CHR:4.5 and suite_protocols; suite membership is a set in A.19.CHR:4.2).
  • Inputs (conceptual): admitted candidates; a finite by-value basis of upstream binary CPM applications, each with its pair, realized GuardDecision, and own ComparisonResultSlot binding when produced; the union of justified relation or poset tokens from those bindings; explicit CriteriaSlot, CNSpecSlot, CGSpecSlot; one U.ClaimScope with selected A.2.6 U.ContextSlice members; the same A.19 predicate basis when one governs the comparisons or selection criteria; effective reference plane; explicit evaluation window; and optional TaskSignature and MinimalEvidence policy refs.
  • Output (conceptual): the by-value SelectionSlot candidate set. A singleton is allowed when the explicit criteria determine one candidate; a total order supplies comparison information but needs a choice rule. The output is not a decision log, guard value, result episteme, generic result relation, publication, or replay record.
  • Planned use: on a P2W path, an A.15.2 baseline selects editions and policies. A.15.3 and SlotFillingsPlanItem apply only to independently declared receiving positions under A.19.CHR:4.7.2. The Select application carries its effective arguments and SelectionSlot binding under §4.1. Dated selection Work and an A.10 provenance account retain their independent grounds.
  • Transformation-flow use: when selection is represented by an E.18 node, that node cites this declaration. Planned refs use A.15.3 typed filling only for independently declared receiving positions; Select bindings remain governed by §4.1.
  • Failure mode: tri‑state guard (pass|degrade|abstain); missing or unknown evidence never coerces to pass.
  • Mental model: SelectEligibility gates the step; Select applies explicit criteria to set‑valued comparison outcomes; the result is a selected set whose “single winner” behavior must be explicit.

A.19.SelectorMechanism:1 - Problem frame

FPF’s Characterization (CHR) suite treats selection as a mechanism boundary within the suite (authoritative membership: A.19.CHR:4.2). Suite membership is a set; order has no semantics. Any intended ordering is expressed only via suite_protocols (A.19.CHR:4.5), under suite obligations (A.19.CHR:4.3).

Within the suite‑closed protocol, SelectorMechanism appears as the select stage (after admissible comparison; optional stages remain optional per suite_protocols). Under CN-Spec and CG-Spec, the declared Select operation:

  • consumes admissible comparison outcomes without collapsing them into a hidden scalar,
  • applies explicit criteria and policy references, and
  • returns a selected-set result under policy-bound defaults, with the Select application and its argument and result bindings recoverable; dated Work and evidence-provenance grounds enter when the account asserts them or the receiving use consumes them.

The kernel uses the CHR suite SlotKind lexicon (A.19.CHR:4.2.1) to prevent SlotKind drift in specializations and SoTA wiring modules.


A.19.SelectorMechanism:2 - Problem

Engineering teams regularly need to make “a selection decision” under conditions that are normal in projects:

  • comparisons are partial, multi‑criteria, or set‑valued,
  • evidence is incomplete or policy‑gated, and
  • different stakeholders ask for different “best” notions.

If selection is not a first‑class mechanism boundary with stable semantics, the same high‑risk drift happens repeatedly:

  • Silent winner forcing: partial orders get collapsed to a single winner by ad‑hoc tie‑breakers or hidden weights.
  • Hidden thresholds and constants: thresholds, weights, dominance regimes, and default PortfolioMode fields get smuggled into implementations and become invisible in discussion and audit.
  • Scalarization by convenience: set‑valued comparison outcomes get replaced by a scalar “score summary” that is treated as decision‑relevant without being declared as such.
  • Evidence coercion: missing or unknown evidence gets treated as “good enough” (implicit pass) rather than yielding explicit degrade or abstain.
  • Boundary erosion: selection performs comparison, scoring, aggregation, or publishing.
  • Selection-boundary drift: a selected-set label is reused after candidate universe, finite upstream comparison-application basis or its required coverage, selection conditions, A.19 predicate, claim scope, selected context slices, reference plane, or evaluation window changed.
  • Guard-output collapse: degrade or abstain is treated as a selected-set member or as a generic selection result.

A.19.SelectorMechanism:3 - Forces

  1. Set‑valued reality vs single‑winner convenience. Many admissible comparisons are partial orders. The kernel must preserve set‑valued semantics while still allowing single‑winner outcomes when requested by criteria.

  2. Policy primacy vs method freedom. Criteria and defaults must be explicit and policy‑bound, while multiple method families and decision styles must remain add‑able without mutating the kernel.

  3. No hidden thresholds vs usability pressure. Engineers often want “just pick one.” If the spec does not constrain this, hidden thresholds and tie‑breakers become de facto policy.

  4. Evidence discipline vs delivery pressure. Under uncertainty, teams default to coercion (unknown → pass). The kernel must enforce tri‑state eligibility and fail‑closed discipline.

  5. Replayability vs conceptual minimalism. The mechanism declaration stays small. Replay recovers the Select application, its argument and SelectionSlot bindings, effective editions, policies, candidates, and selected set. Dated selection Work and evidence-provenance retain their independent grounds when asserted by the account or consumed by the receiving use.

  6. Evolvability vs didactic usability. The kernel must be stable enough to support SoTA wiring and specialisation chains, but also teachable: one place states the mechanism boundary, laws, eligibility behavior, and the neighboring replay basis for realized use.

  7. Planned use and gate/guard separation. On a P2W path, A.15.2 carries the intended baseline; A.15.3 typed filling is conditional on independently declared positions. Selection must not mutate into a gate pattern: no GateDecision or decision logs inside the mechanism boundary.

  8. No competing defaults. If defaults exist for PortfolioMode, dominance regime, or archive policy, cite their declared sources rather than re-declaring them in the kernel.

  9. Scope continuity vs legitimate reselection. Selection may narrow candidates or apply explicit policy, but it may not change the finite upstream comparison-application basis, its required pair coverage, any member’s predicate basis, claim scope, selected context slices, reference plane, or evaluation window. A justified change is a new selection application and may require new binary comparisons.


A.19.SelectorMechanism:4 - Solution

SelectorMechanism is the selection kernel for CHR and for selector specializations. It provides:

  • a stable mechanism boundary for select,
  • a stable SlotKind field set (via the CHR lexicon),
  • a minimum law set that preserves set‑valued semantics and forbids hidden thresholds and hidden scalarization,
  • a tri‑state admissibility guard that is fail‑closed under missing admissibility or evidence,
  • a replay basis that separates effective occurrence bindings, the selected-set result, and supporting evidence from reusable selector semantics;
  • a selection-use boundary that keeps candidate universe, the finite upstream comparison-application basis and required coverage, the derived token union, selection conditions, scope, predicate basis, plane, and window distinct; and
  • output discipline: SelectionSlot contains only the selected candidate set, while eligibility, evidence use, provenance, currentness, result epistemes, and publications remain separate.

Method semantics and SoTA algorithm families do not live inside the kernel: they connect via G.2 SoTA packs and wiring modules, and via declared specializations subject to the local restrictions in CC‑A19SelectorMechanism‑10. A claimed refinement, conservative extension or equivalence uses its own comparison test in A.6.1 §4.8; the labels ⊑ and ⊑⁺ do not supply that test.

A.19.SelectorMechanism:4.1 - Operation declaration — normative core

  • Declaration boundary: this A.6.1 intension declares Select and SelectEligibility; it does not bind project-specific pins or create selection scope, dated work, an operation application, gate decision, selected-set episteme, evidence use, provenance path, currentness relation, or publication relation. Each neighboring object or relation uses its governor.

  • Declaration identity: SelectorMechanism.IntensionRef cites this A.6.1 U.Mechanism episteme. The CHR select stage resolves to its local Select operation. A changed argument, selection law or guard requires explicit selection of the changed declaration; another realizer of the same declaration changes no suite member.

  • IntensionHeader: id = SelectorMechanism, version = 1.0.0, status = stable.

  • IntensionRef: SelectorMechanism.IntensionRef designates this U.Mechanism episteme as the suite member named in A.19.CHR:4.2; it is not the EntityOfConcernRef of the declared operation family.

  • Purpose: universal set‑returning selection kernel over candidates and criteria; defaults remain policy‑bound; no hidden thresholds.

  • Imports: A.6.1:4.8 (declaration comparisons), A.6.1 (operation-local declarations and bindings), A.19.CN (CN-Spec comparison basis and use conditions), C.22 (TaskSignature as a policy-reference artifact when used), G.5 (selector conformance and default selection policy), G.0 (CG‑Spec admissibility and evidence gates), A.19.CHR:4.2.1 (CHR SlotKind Lexicon).

  • EntityOfConcernRef: the selection operation family declared by Select and SelectEligibility in this section.

  • Effective reference scheme: the CHR suite reference scheme in which the A.19.CHR SlotKind lexicon, CN-Spec, CG-Spec, and any current TaskSignature tokens are interpreted.

  • Signature components:

    • SubjectKind: candidate set, supplied through CandidateSetSlot in both Select and SelectEligibility. An incomplete eligibility proposal can leave this argument unbound under the rule below.
    • RangedValueKind: pair of values <admitted candidate set, relation or poset token set over the same candidate universe>, carried respectively by CandidateSetSlot and ComparisonResultSlot in both operations.
    • Results are operation-local: the selected candidate set and the separate guard judgment.
    • Input qualification: selection ranges over one admitted candidate set and the union of justified relation or poset tokens from a finite basis of binary CPM applications whose pair endpoints lie in that candidate set and whose coverage satisfies the explicit selection conditions, all in one U.ClaimScope; selected U.ContextSlice values are members of that scope under A.2.6 and do not create duplicate membership.

    These are A.6.0 declaration components. They do not form another selector-content container, and they do not absorb candidate admission, comparison work, dated selection work, result, evidence-provenance, or replay relations.

Operation-local argument and result declarations

Each argument below is declared separately for Select and SelectEligibility, except the realized eligibility argument of Select itself. ByValue carries the stated value; a named Ref or ByRef resolves one value and edition. Cardinality is per application. The guard can assess an incomplete proposal with 0..1 of each required argument; missing inputs have no binding and prevent pass.

DirectionLocal designatorMeaning and ValueKindDesignation; cardinality
ArgumentCandidateSetSlotSet of admitted candidate values, each retaining its governing kind and identityByValue; 1 set
ArgumentComparisonResultSlotSet of relation/poset tokens, the union of the comparisonBasis members’ own returned valuesByValue; 1 set
ArgumentCriteriaSlotSet of selection clauses and explicit tie-breakers used to determine the selected set; acceptance thresholds remain in their own declarationsByValue; 1 set
ArgumentTaskSignatureSlotTaskSignature supplying selector policy defaults when used; it does not replace CN-Spec or CG-SpecTaskSignatureRef; 0..1
ArgumentCNSpecSlotCN-Spec supplying admission/acceptance and candidate-use conditionsCNSpecRef; 1
ArgumentCGSpecSlotCG-Spec supplying selector admissibility and default evidence conditionsCGSpecRef; 1
ArgumentMinimalEvidenceSlotMinimalEvidence override used instead of CGSpecSlot.MinimalEvidenceMinimalEvidenceRef; 0..1
ArgumentcomparisonBasisFinite set of binary CPM Compare application references, each with its left/right pair, realized eligibility and own output binding or explicit absenceByValue set; 1
ArgumentrequiredComparisonsFinite set of required binary comparisons derived from the candidates, criteria and effective policy, including direction/comparator distinctions that affect selectionByValue set; 1
ArgumenttokenProvenanceMapping from every consumed token to at least one producing CPM output binding in comparisonBasisByValue; 1 mapping
ArgumentclaimScopeU.ClaimScope for claims about comparability and selection under the specified conditions. CandidateSetSlot binds the candidates considered in this application.ByRef; 1
ArgumentselectedSlicesSet of selected U.ContextSlice members of claimScope under A.2.6ByValue set of references; 1 set
ArgumentcharacteristicPredicateA.19 CharacteristicSpacePredicate basis shared as required with the relevant CPM membersByValue; 0..1, explicitly absent when none governs the use
ArgumentreferenceSchemeEpistemeInterpretationScheme (C.2.1:4.1.2), governing this selectionByRef through C.2.1 SchemeDesignation; 1
ArgumentreferencePlaneCHR:ReferencePlane value qualifying selectionByValue; 1
ArgumentevaluationTimeSelection-evaluation point or interval in the declared time basisByValue; 1
ArgumentselectorPolicyEffective selection policy and resolved defaults, including candidate-level failure behavior when degrade is usedByRef to the declared policy; 1, resolved through TaskSignature when it supplies that policy
Select argumenteligibilityGuardDecision determined by SelectEligibility for these same proposal arguments, used to admit this selectionByValue; 1, with its producing guard-result binding recoverable
Select resultSelectionSlotSet of candidate values selected under those criteria and policyByValue; 1 set on completed admitted selection, 0 on abstain
SelectEligibility resultGuardDecisionJudgment determined by the eligibility predicates: pass, degrade or abstainByValue; 1 on completed evaluation

Resolve the scheme designation under C.2.1:4.2.6 to one rule collection, then check its C.2.1:4.1.2 range and the rules needed by these selection inputs. The reference token is not the bound scheme. An unresolved required interpretation cannot support a completed admitted selection; apply the guard and abstention rules below.

Membership alone supplies neither successful selection nor a cross-scheme correspondence. The application and result bindings below remain independently required.

For each argument row, its bindingPredicate holds when that application uses the resolved value for its stated purpose: candidates supply the selection universe, criteria/policy supply the choice rule, specifications/evidence requirements govern admission, and the basis, coverage and provenance supply the comparisons on which the choice relies. Scope, slices, predicate, scheme, plane and time bind only when they qualify that application. A nearby policy or copied comparison record does not supply those bindings.

The SelectionSlot bindingPredicate holds when that Select application returns the candidate subset determined by its bound criteria/policy from the justified comparison basis, under its declared pass/degrade conditions. The GuardDecision bindingPredicate holds when that SelectEligibility application returns its assessed judgment. An equal selected set or guard value stored elsewhere is insufficient.

A.6.1 governs each binding’s identity and continuous extent within the application; result binding begins at its return.

SlotIndex (derived projection). Project the designators, ValueKinds, designation and cardinalities above. Historical Slot names support CHR lookup. The other local names declare operation arguments, not new U-kinds or CHR SlotKinds; A.6.5 relation SlotSpecs supply none of their semantics.

OperationAlgebra. The select stage resolves to Select with the declared candidate/token, criteria/specification and selection-use arguments, returning SelectionSlot. SelectEligibility evaluates that proposal under the guard below. ComparisonResultSlot contains only the token union; application references, coverage, scope and provenance remain separate arguments. A CPM abstain with no output contributes no token. Every required comparison must be discharged by a basis member; degraded selection names excluded candidates under the bound failure behavior and retains complete coverage for its reduced use.

ApplicationPredicate. Select obtains when a selection act applies the bound criteria and effective policy to the candidate universe using the bound justified CPM outputs and use restrictions, with pass or an explicitly permitted degrade outcome under SelectEligibility. It returns the resulting set; on abstain no Select act proceeds. SelectEligibility obtains when an evaluation checks that proposal’s coverage, provenance, admission and evidence conditions and returns the corresponding judgment. A valid proposal or an equal saved selected set does not establish that selection act.

ApplicationIdentityRule. One application is one selection invocation or guard-evaluation invocation at its calculation locus, from taking up its declared arguments until return or termination. References to that same episode reidentify it. Two independently begun invocations remain distinct even when the complete CPM basis, criteria, policies, qualification window and results are equal. Law 6 additionally makes a changed binding a new selection application; a completed prior application cannot acquire the replacement basis or result.

ApplicationExtentRule. Select extends from use of its candidates, CPM basis and choice rules through selected-set return or termination; SelectEligibility extends from proposal assessment through judgment or termination. An unfinished invocation has an open extent and no unreturned result binding.

The selection-evaluation window qualifies the use and does not determine these calculation intervals. A trace designates an established episode; ordinary set-selection mathematics asserts no dated U.Work.

For example, use the admitted incomparable supplier pair from A.19.CPM §4.1 and the declared criterion “retain every nondominated candidate.” With complete required coverage and the CPM token binding, two separately performed selections can each return {A,B}. Their Select occurrences and result bindings differ even when they reuse the same CPM producer application. A copied {A,B} without a corresponding selection return establishes no fresh binding. A copied comparison token whose producing CPM return is unestablished fails tokenProvenance and causes abstain; it cannot enter the basis merely because its text matches.

  • LawSet (minimum): the selection kernel is set-returning and policy-bound

    1. Set‑returning by default: a conformant Select MUST return a declared selected set by default. It MUST NOT silently collapse partial orders or incomparabilities to a single winner; a singleton outcome MUST follow from the explicit criteria applied to the admitted comparison outcomes.
    2. No hidden thresholds or constants: a conformant publication MUST NOT smuggle thresholds, weights, dominance rules, or tie‑breakers. Selection‑level commitments MUST be explicit in CriteriaSlot and, where needed, in policy defaults exposed through TaskSignatureSlot. Admissibility and acceptance thresholds are applied only via SelectEligibility using CNSpecSlot.acceptance and the effective evidence policy (MinimalEvidenceSlot? or CGSpecSlot.MinimalEvidence).
    3. No hidden scalarization or token aggregation by assertion: a conformant publication MUST consume ComparisonResultSlot as the union of the finite basis members’ justified set-valued or partial outputs. Every consumed token MUST be traceable to at least one producing CPM application. Scalar summaries or relation tokens inferred from a missing pair, empty output, degrade, or abstain are forbidden; scalar summaries, if produced at all, are report-only unless explicitly promoted by policy outside suite closure.
    4. Evidence gating is explicit: when selection depends on evidence, it MUST cite either MinimalEvidenceSlot or the effective CGSpecSlot.MinimalEvidence policy and evaluate selection with the tri-state predicate. Candidate-level ineligibility handling MUST be explicit in current criteria or upstream results and bound by the selection application; the kernel MUST NOT invent evidence thresholds.
    5. No competing defaults: effective PortfolioMode, dominance regime, and other defaults come from declared policy refs and are bound by the application.
    6. Binding changes require a new selection: Select does not change candidate universe, comparison-application basis membership, required comparison coverage, any member’s pair, eligibility or output binding, selection conditions, A.19 predicate basis, claim scope, selected context slices, reference scheme or plane, or evaluation window. A changed binding is another selection application and may require new binary comparisons.
    7. Guard-output separation: GuardDecision is not a selected-set member. On abstain, no SelectionSlot value is fabricated. A degrade eligibility value permits a reduced set only under the bound failure behavior and criteria.
  • AdmissibilityConditions (tri-state guard; fail-closed on missing admissibility, comparison coverage, token provenance, or evidence)

    • SelectEligibility(CandidateSetSlot, ComparisonResultSlot, CriteriaSlot, CNSpecSlot, CGSpecSlot, TaskSignatureSlot?, MinimalEvidenceSlot?; selection-use bindings) → GuardDecision ∈ {pass|degrade|abstain}.
    • pass requires: (i) every basis member’s pair lies inside CandidateSetSlot; (ii) the basis covers every binary comparison required by the candidate universe and explicit selection conditions; (iii) every consumed relation token traces to a member’s own output binding; (iv) explicit selection conditions and tie-breakers; (v) compatible claim scope, selected A.2.6 context slices, reference plane, and evaluation window across the basis and selection, together with any A.19 predicate governing the comparisons or selection criteria; (vi) coherent CN-Spec and CG-Spec editions; and (vii) satisfied admission, acceptance, and effective MinimalEvidence predicates under their owners.
    • If MinimalEvidenceSlot is absent, SelectEligibility MUST evaluate evidence against CGSpecSlot.MinimalEvidence, and missing or unknown evidence MUST NOT yield pass.
    • A basis member with GuardDecision = degrade may support a reduced set only when a current selector policy names the candidate-level failure behavior and the remaining basis still covers the comparisons required for that reduced use. The selection application binds that policy and its own realized eligibility value.
    • A missing required comparison, untraceable token, or required basis member with GuardDecision = abstain makes SelectEligibility = abstain; selection does not proceed and no selected-set output is created.
  • Applicability:

    • Intended for the CHR select stage after the required finite set of admissible binary comparisons and produces a selected-set value. Selection remains distinct from comparison, acceptance, gate decision, publication, and telemetry.
    • Applicable only when CNSpecSlot, CGSpecSlot, explicit criteria, the effective evidence policy, and a finite comparison-application basis with complete required coverage and token provenance are current for the candidate universe. Missing declarations or coverage fail closed.
    • Inside the CHR suite, A.19.CHR:4.5 alone determines stage ordering and optionality.
    • Every selection application binds one U.ClaimScope, selected A.2.6 U.ContextSlice members, the finite basis of binary CPM applications and their pair, eligibility, and output bindings, the derived token union, any A.19 predicate governing the comparisons or selection criteria, effective reference plane, selection conditions, and explicit evaluation point or interval. There is no implicit latest value and no default window inherited from the predicate or comparison label.
    • A selection across reference schemes or planes follows the relations the case needs. When it relates two F.17 SchemeSenseCell values from different semantic contexts, test the F.9 BridgePredicateProfile and cite the Bridge only when its predicate obtains; state suitability for the named selection use in a separate C.2.1 claim. If that predicate is false or unresolved and the semantic crossing is required by the selection conditions, SelectEligibility cannot be pass; follow the already declared degrade policy when applicable, otherwise abstain.

    When the selection crosses ReferencePlanes, cite the plane relation and policy. If both facts are current, state both under their own predicates. A cell or plane difference alone establishes neither relation, and one branch never fabricates the other. Neither relation supplies candidate universe, comparison-application basis or coverage, relation tokens, selection conditions, scope, predicate, or time.

  • Neighboring semantic-Bridge, bounded-use, and reference-plane relations:

    When candidates or comparison tokens require interpretation across different semantic contexts, resolve the two F.17 SchemeSenseCell endpoints and test one F.9 BridgePredicateProfile. For an obtaining Bridge, state its endpoints and profile separately. State suitability for the named selection use in a C.2.1 assertion whose EntityOfConcern is that Bridge and whose ClaimGraph designates <u,d,r,t> and polarity. Include CL or an observed-loss note only when the receiving use consumes it; permitted loss remains t in the bounded-use claim.

    For a ReferencePlane crossing, cite the plane relation and policy separately.

    Open A.10 only when bounded reliance is current and B.3 only when a named assurance claim is current. If that assurance argument consumes a locally declared R_eff calculation, cite its domain model and calculation; neither the Bridge nor CL creates a penalty.

    Adding or changing any of these neighboring objects does not by itself change the selector declaration.

  • Neighboring dated work, operation application, result binding, and evidence relations:

    The identified Select application binds the candidate set, finite comparison basis, required coverage, token union, selection-use arguments, policies and returned SelectionSlot. If the account also asserts dated selection U.Work, first establish its A.13 core: the performing System, local agential-role kind and membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits that performance; F.6 applies afterward only for assignment-bound attribution. The Work identity and extent are not automatically those of one Select application.

    When the account asserts them or the receiving use consumes them, A.2.4 governs evidence use with its own claim scope and relevance window, A.10 governs reliance and provenance, and G.11 governs source or assertion-edition currentness.

    A durable selected-set episteme, when needed, is governed by C.2.1, and any current entity-identity inception claim by A.15.PROD. No universal work-result, comparison-result, or selection-result relation is presumed.

    To replay the selection, recover:

    • the candidate set and required binary comparisons; for every basis member, the CPM application, pair, realized GuardDecision, and its own output binding or explicit absence; and the trace from every consumed token to its producing member;
    • one U.ClaimScope, selected A.2.6 context slices, the optional A.19 predicate basis (explicitly absent when none governs), effective reference scheme and plane, and evaluation point or interval shared as required by the selection conditions;
    • CNSpecRef.edition, CGSpecRef.edition, and TaskSignatureRef.edition when TaskSignature is used;
    • the effective MinimalEvidence policy, either the explicit override or CGSpecSlot.MinimalEvidence;
    • the Selector’s realized GuardDecision and, for degrade or abstain, the current failure-behavior policy;
    • the candidate-set value and derived union bound to the Selector’s ComparisonResultSlot argument;
    • the effective criteria and selector-default refs; and
    • the selected-set result; any current obtaining F.9 Bridge and its separate C.2.1 bounded-use claim; any optional CL or observed-loss note consumed; and any ReferencePlane relation and policy. Recover A.10 reliance or B.3 assurance only when the selection use consumes it.

    These neighboring objects support replay. The finite basis is a binding of the selection application, and none of them is selector-declaration content or a generic result container.

A.19.SelectorMechanism:4.2 - Selection boundaries and dependencies

  1. Selection conditions are explicit values, not a new object kind. The application binds CriteriaSlot plus effective selector-policy refs, defaults, and degrade failure behavior. Acceptance and admission predicates remain separate. SelectionSlot contains only the resulting candidate set; eligibility, conditions, scope, evidence, and replay metadata stay outside it.

  2. Selection consumes a traceable finite basis of upstream CHR products; it does not invent them. Any indicator-derived scoring or comparison input retains its A.19 basis and the UINDM positions selected under that declaration. A changed basis requires rechecking affected upstream position resolutions and dependent results, preserving reuse where their grounds still hold; the selector cannot carry old naked indices into the new declaration.

    The selection application binds binary CPM applications separately and supplies ComparisonResultSlot only as the union of their justified outputs. The kernel MUST NOT perform normalization (UNM), indicatorization (UINDM), scoring (USCM), folding (ULSAM), comparison (CPM), batch-result fabrication, or missing-pair completion inside Select. If a scalar “overall score” is desired, it must be declared upstream as an admissible scoring or comparator choice, not invented inside selection.

  3. Threshold discipline (acceptance is not selection). Acceptance and admission thresholds are not selection criteria: they remain in their governing declarations and are applied only through SelectEligibility. Selection-level tie-breakers, PortfolioMode, and selected-set constraints may exist, but they MUST be explicit in current criteria or policy refs and bound by the selection application, never hidden as unnamed constants.

  4. Report‑only summaries inside suite closure. Any scalar summaries, illumination metrics, or auxiliary “why not chosen” telemetry are report‑only unless explicitly promoted by policy, and MUST NOT be used as hidden dominance rules (A.19.CHR:4.3.3). Publication and telemetry are separately governed continuations outside suite closure. G.10 governs shipping Part-G outputs as a SoTA-Pack; E.24.PUB governs a claim about episteme availability, form or carrier.

  5. Declare specializations under these restrictions. A proposed specialization of SelectorMechanism must retain these local restrictions:

    • SlotKind invariance for inherited operations,
    • no new mandatory inputs to inherited Select,
    • added capabilities appear as declared new operations or additional results under the local ⊑⁺ notation.

    For the refinement, conservative-extension or equivalence claim, apply its own A.6.1 §4.8 test, preserving the applicable operation, application and binding meanings. CC‑A19SelectorMechanism‑10 retains the predicate, endpoint facts and A.6.RCD gap branch.

  6. Planned use and actual binding. On a P2W path, an A.15.2 baseline selects TaskSignature, CG-Spec and evidence-policy editions. A.15.3 supplies planned filling only for an independently declared receiving position. Select arguments and returns are established under this declaration; the planned values remain available for a separately governed comparison with what occurred.


A.19.SelectorMechanism:5 - Archetypal Grounding — informative

A.19.SelectorMechanism:5.1 - Selection under partial comparisons

When comparisons are partial or set-valued, selection must not pretend there is a single best candidate by default. SelectorMechanism makes selection explicit, policy-bound, and replayable: it returns a set, including a singleton when the criteria determine one candidate.

A.19.SelectorMechanism:5.2 - Deployment options

Scenario. A platform team must pick a set of deployment options for a subsystem under multiple criteria: latency, cost, and regulatory risk. Comparisons are multi-criteria and do not induce a total order.

  • CandidateSetSlot = {OptionA, OptionB, OptionC}.

  • CriteriaSlot requires Pareto selection over the three unordered pairs {A,B}, {A,C}, and {B,C}, returns all non-dominated admissible candidates, and preserves the full selected set unless an explicit current criterion requires a singleton.

  • The finite upstream comparison-application basis covers all three required pairs:

    • Compare(OptionA, OptionB, ...) has GuardDecision = pass: OptionB is strictly better than OptionA on latency, while OptionA is strictly better than OptionB on cost under the declared comparator. Its ComparisonResultSlot records those strict opposite wins, so neither dominates the other;
    • Compare(OptionA, OptionC, ...) has GuardDecision = degrade because OptionC lacks the required risk attestation. In this constructed case, the admitted comparator and partial-evidence policy define the empty token set as the lawful output for this restricted use; its output binding contributes no relation token about OptionC; and
    • Compare(OptionB, OptionC, ...) has the same degrade basis and likewise contributes no relation token about OptionC.

    The Selector’s ComparisonResultSlot argument is the union of those justified member outputs, so its two tokens both trace to the {A,B} CPM application. No equality, worse-than, or abstain token is fabricated for OptionC.

  • MinimalEvidenceSlot? is absent, so evidence is evaluated against CGSpecSlot.MinimalEvidence.

  • The selection application binds the three CPM applications and their pair, eligibility, and output bindings; the required-pair coverage and token trace; the deployment-option claim scope and selected regulatory U.ContextSlice members; the same predicate basis or explicit none; the reference plane and evaluation interval; and a degrade policy that permits exclusion of OptionC.

Outcome.

  • Under that bound degrade policy, SelectEligibility returns degrade. Select then excludes OptionC under that policy and returns {OptionA, OptionB}, bound to SelectionSlot.
  • If either required comparison involving OptionC instead had GuardDecision = abstain, that basis member would have no output binding, SelectEligibility would return abstain, and no selected-set value would be created. Neither guard value is a member of ComparisonResultSlot or SelectionSlot.
  • The selection or eligibility application, finite CPM application basis, policies and returned value or explicit absence preserve the branch taken. An A.10 provenance account is added for the bounded reliance at issue; any dated Work claim requires the independent grounds in §4.1.

A.19.SelectorMechanism:5.3 - Analysis-method families

Scenario. A methods group selects a declared set of analysis-method families for a task. Candidates are refs to those families. The group wants diversity in the selected set, but does not want diversity metrics to silently become dominance criteria.

  • CandidateSetSlot = {Family1, Family2, Family3, Family4}

  • The selection conditions declare which binary method-family comparisons are required. A finite basis identifies every relied-on CPM application, its pair, eligibility value, and own output binding; the Selector’s ComparisonResultSlot argument is their justified-token union.

  • TaskSignatureSlot is present and is the single policy-default slot or ref:

    • PortfolioMode and dominance regime,
    • budgeting and telemetry hooks (when used).
  • CriteriaSlot declares that diversity signals are telemetry unless explicitly promoted by policy.

Outcome.

  • SelectionSlot returns a selected set of those families; any archive‑style behavior is a specialization and policy choice, not a hidden kernel default.
  • The Select application retains its TaskSignatureRef.edition, effective criteria and SelectionSlot bindings for later explanation. Add provenance and dated Work only under their independent grounds in §4.1.

A.19.SelectorMechanism:6 - Bias-Annotation — informative

This pattern biases selection authoring toward explicitness and admissibility.

  • Governance bias. Bias toward explicit criteria and policy-reference records rather than implicit constants. Risk: perceived overhead. Mitigation: use existing prose or code when it makes the criteria recoverable, and centralize defaults via TaskSignatureSlot when used.
  • Architecture bias. Bias toward set‑return semantics and against forced total orders. Risk: consumers may expect a single winner. Mitigation: make the choice rule explicit; a declared total order alone does not choose a candidate.
  • Epistemic bias. Bias toward fail‑closed evidence handling and against unknown coercion. Risk: more degrade or abstain early. Mitigation: improve evidence pins and policy clarity; do not relax the kernel.
  • Practice bias. Bias against embedding telemetry and publication into selection. Risk: teams want one step to select and report. Mitigation: keep those relations under their governing patterns; retain replay through selection bindings and the separately applicable Work, evidence and currentness relations in §4.1.

A.19.SelectorMechanism:7 - Conformance Checklist

IDRequirement
CC-A19SelectorMechanism-0Mechanism declaration completeness: one U.Mechanism episteme, its selection-operation-family EntityOfConcernRef, its effective reference scheme, the operation-local argument/result declarations, OperationAlgebra, LawSet, AdmissibilityConditions, and Applicability are recoverable under A.6.1.
CC‑A19SelectorMechanism‑1Single governing pattern: the SelectorMechanism U.Mechanism declaration is governed by A.19.SelectorMechanism:4.1; other descriptions cite this section rather than restating the kernel law.
CC‑A19SelectorMechanism‑2Set‑return default: a conformant Select MUST be set‑returning by default; it MUST NOT silently collapse partial orders or incomparabilities to a single winner.
CC‑A19SelectorMechanism‑3No hidden thresholds or constants: a conformant SelectorMechanism publication MUST NOT smuggle thresholds, weights, dominance rules, tie‑breakers, or default PortfolioMode fields. Selection‑level commitments MUST be explicit in CriteriaSlot and policy defaults when used (e.g., via TaskSignatureSlot). Acceptance thresholds remain governed by AcceptanceClauses, TaskSignature, or GateProfile records and MUST be applied only via SelectEligibility.
CC‑A19SelectorMechanism‑4No hidden scalarization: if ComparisonResultSlot is set‑valued or partial, a conformant publication MUST consume it as such; scalar summaries are report‑only unless explicitly promoted by policy outside suite closure.
CC-A19SelectorMechanism-5Evidence gating: SelectEligibility returns pass, degrade, or abstain; missing or unknown evidence never yields pass. Candidate exclusion or restricted use is explicit in the current criteria or policy bound by the selection application.
CC‑A19SelectorMechanism‑6SlotKind discipline: SlotKind tokens used in the SelectorMechanism intension MUST come from the CHR SlotKind lexicon (A.19.CHR:4.2.1). New SlotKinds require lexicon extension first.
CC-A19SelectorMechanism-7Bridge and reference-plane discipline: a semantic crossing cites an F.9 Bridge only between two F.17 SchemeSenseCell values when its profile applies and its predicate obtains; its C.2.1 bounded-use claim is separate and CL is optional. A ReferencePlane crossing cites its relation and policy separately. A scheme, cell, or plane difference alone establishes neither relation. A false or unresolved required Bridge predicate permits no pass; use only the degrade or abstain route already declared. A.10 enters only for current reliance, and B.3—including any locally defined R_eff calculation—only for a named assurance claim under its declared domain model and calculation. All remain outside selector-declaration content.
CC-A19SelectorMechanism-8Replay basis completeness: recover the Select or SelectEligibility application. Identify bound or returned values and required inputs that were missing: the candidate set, required binary comparisons, every upstream CPM application with pair, eligibility and own output binding or absence, token-to-producer trace, criteria and policy, U.ClaimScope, selected A.2.6 context slices, any governing A.19 predicate (or its explicit absence), reference scheme and plane, evaluation window, derived token union, guard judgment, and any returned SelectionSlot binding. An abstain judgment has no selection result. Independently recover dated Work through the A.13 core and A.15.1 admission in §4.1, evidence use under A.2.4, reliance and provenance under A.10, currentness under G.11 and a result episteme under C.2.1 only when asserted by the account or consumed by the receiving use. A Select application does not itself require separately admitted upstream comparison Work. The output values carry none of this metadata.
CC-A19SelectorMechanism-9Planned-filling separation: on a P2W path, A.15.2 carries intended editions/policies; A.15.3 typed filling applies only to independently declared positions. Select applications carry effective argument/result bindings; dated selection Work and any relied-on A.10 provenance remain separately established.
CC‑A19SelectorMechanism‑10Extension discipline: a proposed SelectorMechanism specialization MUST preserve inherited SlotKind designators and their meanings and add no mandatory input to inherited Select. For a claimed refinement, conservative extension or equivalence, apply the corresponding A.6.1 §4.8 preservation test, including application/binding predicates, identity and extent. The comparison predicate and endpoint facts must be established; use A.6.RCD’s missing-governor/substrate result when they are absent. The symbols ⊑ and ⊑⁺ alone establish none of these comparisons.
CC-A19SelectorMechanism-11Guard and gate separation: SelectorMechanism publishes neither GateDecision nor DecisionLog; SelectEligibility returns pass, degrade, or abstain separately from the selected set.
CC-A19SelectorMechanism-12Selection-condition completeness: CriteriaSlot, effective selector policies and defaults, and any degrade failure behavior are explicit and bound by the application; acceptance and admission predicates remain separate.
CC-A19SelectorMechanism-13Selection-scope completeness: every admitted Select application binds candidate universe, finite binary CPM application basis, required comparison coverage, token-to-producer trace, U.ClaimScope, selected A.2.6 context slices, any A.19 predicate governing the comparisons or selection criteria, effective reference scheme and plane, and explicit evaluation point or interval. No generic context input, optional structure, batch result, or label supplies them.
CC-A19SelectorMechanism-14Output separation: SelectionSlot contains only the by-value selected candidate set. On abstain no output is fabricated; a reduced set under degrade requires explicit current policy.
CC-A19SelectorMechanism-15Comparison continuity: selection cites the finite basis of binary CPM applications and may not change its membership, required coverage, member pairs, eligibility or output bindings, predicate basis, scope, selected slices, plane, or window. A justified change is a new application and may require recomparison.
CC-A19SelectorMechanism-16No generic result relation: the A.6.1 operation application binds SelectionSlot; C.2.1 governs a durable selected-set episteme when needed; subject patterns govern other result relations.
CC-A19SelectorMechanism-17Finite comparison-basis coverage: selection conditions derive the required binary comparisons; each is discharged by a CPM application, and every consumed relation token traces to its producing member output. A missing pair, untraceable token, or required member that abstains forces selector abstention rather than a fabricated batch result.

A.19.SelectorMechanism:8 - Common Anti-Patterns and How to Avoid Them — informative

Anti-patternWhat it looks likeRemedy
GateDecision leakageSelect emits GateDecision or writes a decision logKeep gate decisions in their governing patterns. SelectEligibility remains the mechanism predicate; the application retains its realized eligibility value and replay basis.
Forced single winnerSelect always returns exactly one candidate even under incomparabilityReturn a declared selected set. If a singleton is required, state the choice rule in CriteriaSlot and derive that result from the admitted comparison basis; any ordering used must be declared and admissible.
Hidden tie-breakers“If incomparable, pick lower cost” without declaring that as policyMove tie-breakers into explicit criteria or into declared comparator policies; never embed inside the kernel
Scalarization by convenienceReplace set-valued comparison with a scalar “summary score” treated as decisiveKeep summaries report-only unless declared as admissible comparator outputs
Unknown coerced to passMissing evidence treated as acceptableUse tri-state SelectEligibility; unknown maps to degrade or abstain
Selection does comparisonSelection stage recomputes scoring or comparison internallyKeep comparisons upstream; SelectorMechanism binds CPM applications and consumes only their justified-token union in ComparisonResultSlot
One binary comparison treated as a batchOne Compare(left,right) application is said to cover three or more candidates, or a token union loses its producing applicationsBind a finite basis of binary CPM applications, derive required pair coverage from the selection conditions, and trace every consumed token to a member output
Selected set as replay recordCandidate universe, comparison ref, criteria, scope, evidence, or currentness are placed inside SelectionSlotKeep SelectionSlot to selected candidates; bind use arguments on the application and use evidence, provenance, and currentness relations
Boundary driftSelection reuses a token union after comparison-basis membership, coverage, member pair or eligibility, predicate, scope, selected slices, plane, or window changedTreat it as another selection application and perform the required binary comparisons again when their governed basis changed
Publish inside selectionSelection emits a publication or telemetry relation as part of mechanism semanticsKeep publication and telemetry under their governing patterns; application bindings and applicable relations retain replay

A.19.SelectorMechanism:9 - Consequences

Benefits

  • Preserves incomparable candidates when the criteria require them.
  • Makes thresholds, weights and scalarization choices inspectable; correct selection still depends on applying the admitted criteria to the justified inputs.
  • Supports replay through application bindings and the relations that the receiving use consumes.
  • Supports evolvability: new method families and selection styles can be wired without changing the kernel signature.

Costs and trade-offs

  • Selected-set results can require downstream handling when a single decision is needed.
  • Evidence discipline increases early degrade or abstain until criteria and evidence policies are explicit.
  • Teams must make the selection criteria recoverable; existing descriptions may already suffice.

A.19.SelectorMechanism:10 - Rationale

Selection is where many systems accidentally convert admissible but nuanced information into an unjustified scalar decision. Making selection a separate, explicit mechanism boundary achieves two things that matter for engineering management:

  1. Technical integrity: the declared guard tests the admissibility and evidence conditions needed by this selection.
  2. Organizational clarity: it makes defaults and thresholds discussable, reviewable, and maintainable as explicit policy references.

The set‑returning default is not a preference for large retained sets; it is a correctness safeguard when the order is not total. Single-winner outcomes remain possible when the criteria select one candidate from the admitted comparison outcomes.


A.19.SelectorMechanism:11 - SoTA-Echoing

The research lines below supply application families and design comparisons. Their distinct output meanings and conditions remain with the cited methods; they do not establish the selector laws by themselves.

Selector-family SoTA packages are cited through their current Part G pack or claim sheet when one governs the use. They connect through CriteriaSlot and TaskSignatureSlot references while kernel semantics remain unchanged.

A.19.SelectorMechanism:11.1 - SoTA alignment map (normative)

SoTA practice pointer, post‑2015+Primary source examples, post‑2015+Where it connects to SelectorMechanismAdoption status
Retain several candidates under explicit criteriaPugh, Soros and Stanley (2016), Quality Diversity: A New Frontier for Evolutionary Computation, §4.2QD supplies retained-set application families with different niche and retention rules. Declare the choice rule in each use; an archive rule is not the general Pareto-selection rule.Adapt
Use declared archive-insertion criteriaVassiliades, Chatzilygeroudis and Mouret, Using Centroidal Voronoi Tessellations to Scale Up the Multi-dimensional Archive of Phenotypic Elites Algorithm, author manuscript revised 2017CVT-MAP-Elites assigns a candidate to its nearest region and replaces a less-fit occupant. An FPF adaptation states the region and quality criteria; auxiliary telemetry supplies no undeclared dominance rule.Adapt
Organize candidates as environment–solution pairsWang et al. (2019), Paired Open-Ended Trailblazer (POET)POET pairs generated environments with optimized agents and transfers solutions between environments. Candidate and criteria structuring is an FPF adaptation; the source does not establish this kernel’s laws or FPF Method membership.Adapt
Admit a declared rejection optionGeifman and El-Yaniv (2017), Selective Classification for Deep Neural NetworksThe possibility of rejection informs FPF eligibility design. A selective-prediction rejection rule is not identical to this three-valued guard; apply each rule under its own conditions.Adapt
Make architecture commitments traceableISO/IEC/IEEE 42010:2022 architecture description disciplineFPF assigns this declaration to one governing pattern; that assignment is an FPF design choice.Adapt

A.19.SelectorMechanism:12 - Relations

  • Builds on

    • A.6.1 and its conformance checklist for mechanism identity, declaration content, applicability, and specialisation-chain discipline.
    • A.19.CHR for suite membership, suite protocol closure, SlotKind lexicon, and threshold and default discipline.
    • G.0 for CG‑Spec admissibility and evidence declarations.
    • A.19 for the CharacteristicSpacePredicate basis when one governs selection.
    • A.19.CPM for every binary Compare application in the finite basis, its pair, realized eligibility value, and own set-valued output binding.
    • A.2.6 for U.ClaimScope identity and U.ContextSlice membership.
    • A.19.CN for CN-Spec, whose declared comparison and candidate-use conditions supply an explicit input.
    • C.22 for TaskSignature as a policy-reference artifact when used.
    • A.6.1 §4.2 for operation-local argument/result meanings and their SlotIndex projection; the local extension rule preserves inherited meanings.
    • A.15.2 for the edition/policy baseline on P2W paths; A.15.3 plus A.19.CHR:4.7.2 for typed filling of independently declared positions.
    • C.27.TA for the explicit selection-evaluation point or interval.
    • A.2.4, A.10, and G.11 for evidence-use scope, provenance, and currentness, separately from selection scope and output.
  • Used by

    • A.19.CHR as the select stage in CHR pipelines.
    • G.5 as the primary conformance and specialization context for selector-based method dispatch and PortfolioMode policies.
    • E.18 when this declaration is used by transformation-flow nodes. A.15.3 governs planned refs only for independently declared receiving positions; operation bindings and any dated selection Work retain their rules.
  • Coordinates with

    • CPM and other admissible comparison stages as producers of the result bindings whose justified-token union fills the Selector’s ComparisonResultSlot argument.
    • ULSAM and other admissible aggregation stages that must remain explicit rather than hidden inside selection.
    • E.20 for governing-pattern discipline; F.18 when a reusable name or alias needs to be chosen. An F.9 semantic Bridge requires its own predicate, not merely a source term.

A.19.SelectorMechanism:End

A.20 - Constraint Validity for Transformation Steps

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Internal-constraint check.

Technical result name. ConstraintValidityResult.

A.20:0 - Use this when

Use A.20 when one transformation or one operation application is current in a transformation-flow structure and the question is whether that subject satisfies one named internal constraint for one stated case. It also applies when an A.6.4 bounded-use assertion q is current there and q’s proposition is the named internal constraint. A.6.4 retains the separate current-case judgement.

First useful move. Recover the subject, constraint and case from the existing description. Determine applicability; if it remains unresolved, state the missing fact and deciding rule. Once applicability is established, report its value, the evaluation state and any test outcome, with the evaluation window and witness or reason.

Quick worked case. TemperatureConversion-7 must add 273.15 to a Celsius input and must not return a value below 0 K. For input 25 °C, the test returns 298.15 K, so both required conditions are satisfied; the witness records the formula edition, input, output, and test result for this evaluation window. The practitioner may reuse this result for that case and window, or pass it to a current gate or assurance use; changed input, formula edition, assumptions, or window requires reassessing affected grounds and establishing whether this result still covers the receiving case and use. If the output were 297.15 K, the formula condition would be violated; if no output could be recovered, it would be unknown; if the test had not run, its evaluation state would be notRun.

Stop after that result unless a gate, assurance argument, publication, or another named task needs it. Path and crossing structure, refresh, gate decisions, evidence, assurance, Work, and semantic bridges keep their own patterns. What goes wrong if missed. A class label or green status replaces the constraint and test. An unknown or unrun required check disappears inside pass. A failed local constraint makes unrelated gate-fit facts look inapplicable. Copying the surrounding flow architecture into this result obscures the local finding.

What this buys. A practitioner can see which constraint was tested, why it applied, what case was used, what the result means, and which later decision may consume it.

Not this pattern when.

  • Use A.21 for a gate decision or profile consequence.
  • Use E.18 for transformation-flow positions, paths, crossings, valuations, or PathSlice identity.
  • Use E.17 for publication forms and faces, G.11 for refresh work, and C.27 for temporal-claim adequacy.
  • Use A.6.4 for retargeting semantics and F.9 only for a separately claimed semantic correspondence.
  • A Signature, WorkPlan, dated Work, or gate check does not enter A.20 merely because it occupies an E.18 position; use the pattern that defines the claim.

A.20:1 - Problem frame

An E.18 transformation-flow structure may place a transformation beside signatures, mechanism descriptions, work-planning material, Work, checks, and retargeting material. Those neighboring values do not all have the same internal constraints.

A.20 addresses a narrower question: one identified subject is tested against one identified constraint under stated assumptions and case facts. The result may later be used by a gate or assurance argument, but it is not itself a gate decision or policy consequence.

A.20:2 - Problem

How can FPF report internal constraint validity without:

  • inventing a world-side FlowConstraintValidity relation whose participants are unspecified;
  • using one status value for not applicable, not run, unknown, policy degradation, and gate blocking;
  • requiring every specialist constraint for every transformation;
  • suppressing independently useful gate-fit results after one local failure;
  • copying publication, path, refresh, gate, or retargeting architecture into A.20; or
  • treating an entity reference as a semantic bridge or requiring every retargeting to be reversible?

A.20:3 - Forces

NeedTension
Small local resultA user needs one check result, while later replay needs its constraint, case, and window.
Open constraint familiesDifferent transformations carry different laws; a fixed universal checklist would create false requirements.
Truth and policy separationWhether a constraint holds is not the same as what a gate does with the result.
Missing informationNot applicable, not run, unknown, and error lead to different next actions.
Reuse without fanoutA reusable result must be precise without copying every possible consumer’s record and policy.

A.20:4 - Solution

A.20:4.1 - Result ontology

ConstraintValidityResult is a C.2.1 result episteme. It is not a new U-kind and not a world-side relation. Its EntityOfConcern is the constrained subject. Its ClaimGraph states one application of one named constraint to one case.

The constrained subject is normally:

  1. one independently identified U.Transformation used at an E.18 transformation position;
  2. one A.6.1 operation application whose internal law is being tested; or
  3. the proposition carried by one A.6.4 bounded-use assertion q, only when that proposition is the named internal constraint. q remains a C.2.1 episteme about arrow r; its ClaimGraph and the separate current-case judgement remain under A.6.4, and any operation application remains separate.

Another subject is admissible only when its own pattern defines a named internal constraint and states why this result form applies. An E.18 locus label alone supplies neither the subject nor the constraint.

When a fact needed to determine applicability is missing, state the unresolved question, the missing fact, and the rule that will decide it. Assign applicabilityValue and construct the result below once applicability is established.

Minimum result content:

ConstraintValidityResult:
  resultRef: C.2.1 episteme
  constrainedSubjectRef:
  constraintRef:
  constraintEdition:
  applicabilityValue: required | optional | notApplicable
  applicabilityBasis:
  caseFacts:
  referenceSchemeAndScope:
  evaluationWindow:
  evaluationState: evaluated | notRun
  outcome?: satisfied | violated | unknown | error
  witnessOrReason:
  effectiveUseWindow?:
  evaluationWorkRef?:

outcome is present only when evaluationState=evaluated and applicabilityValue is required or optional. A not-applicable constraint records the reason it is outside this case. A not-run constraint records that evaluation work has not produced a result. Neither is unknown and neither counts as success.

If a dated evaluation Work occurrence is asserted, first establish its A.13 core: the performing System, local agential-role kind and membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits that performance; F.6 applies afterward only for assignment-bound attribution. The optional evaluationWorkRef cites that Work separately from the result episteme.

The legacy label FlowConstraintValidity may be retained only as a locator for this result family. It does not name a relation, gate status, publication record, or flow-wide property.

A.20:4.2 - Applicability, required set, and summary

Before evaluation, name the constraints being considered for the current subject and case. Mark each as required, optional, or notApplicable and state why. The required set is complete only when every constraint that the current use depends on is named and no unresolved applicability question could change that set.

For one evaluated applicable constraint:

  • satisfied means the test established the named constraint for the stated case and window;
  • violated means the test established a counterexample or failed condition;
  • unknown means required case facts or witness content could not be determined after applicability was established; unresolved applicability remains the preliminary question in section 4.1;
  • error means the selected evaluation could not complete correctly.

When a consumer needs one local summary over the complete required set, use:

ConstraintValiditySummary ∈ {satisfied, violated, unresolved, notApplicable}.

The summary rule is:

  1. notApplicable only when the declared required set is empty because no required A.20 internal constraint applies to this subject and use; any optional results remain separately available;
  2. violated when at least one required result is violated;
  3. unresolved when no required result is violated but at least one required constraint is notRun, unknown, or error; and
  4. satisfied only when the required set is nonempty and every member has an evaluated satisfied result.

Optional results do not change the summary unless a separately accepted use decision moves their constraints into the required set. A missing required result can therefore never disappear beside a satisfied result.

A.20:4.3 - Constraint families and outcome rules

The following families are recognition aids, not a universal required list. Each application still names the constraint, edition, assumptions, case facts, and test.

Constraint familyTriggersatisfied meansOther outcomes
Type, domain, and rangeThe subject consumes or produces typed values.Every case input and result used by the claim lies in the declared type, domain, and range.A counterexample is violated; unavailable values are unknown; an evaluation that cannot complete correctly is error.
Admissibility conditionsThe operation or transformation declares guards or admissible cases.Every required guard is true for the case and window.A false guard is violated; undetermined guard truth is unknown.
Law or invariant setThe current claim relies on a named law or invariant.The named invariant holds for the case under its assumptions.A counterexample is violated; missing case facts or witness content are unknown.
Quantity and unit coherenceThe current operation combines quantities or units.The case is coherent under the already declared quantity, unit, and reference-scheme rules.A mismatch is violated; an unrecovered declaration is unknown. A.20 does not define or translate units or planes.
Sensitivity or stability boundA robustness, continuity, perturbation, safety-envelope, or stability claim depends on a bound.The cited bound covers the stated domain, assumptions, distance or norm, and case.A counterexample is violated; absent assumptions or certificate content are unknown. No bound is required without this trigger.
Return-shape preservationA consumer relies on a declared set, archive, order, or other non-scalar result shape.The transformation preserves that declared shape for the current case.Hidden scalarization or lost required structure is violated; unrecovered shape facts are unknown. A.20 does not rank or select the result.
A.6.4 retargeting invariantThe proposition in q is the named internal constraint for the current use; q remains the C.2.1 bounded-use assertion about r.Current case facts establish the proposition as stated, including its invariant, visible loss, named receiving use, conditions, and polarity.A counterexample is violated; a missing deciding fact is unknown unless the constraint itself makes absence a failure. This A.20 result may enter the case basis for A.6.4’s separate satisfies, fails, or cannot decide judgement; it is not that judgement, and the current facts remain separately named. r and any application remain separate.

The constraint’s own pattern supplies its truth condition. A.20 supplies the application result form and summary only.

A.20:4.4 - Gate and policy boundary

An A.21 gate may consume an A.20 result or summary as one declared input. A.20 does not translate satisfied, violated, or unresolved into pass, degrade, block, or abstain; A.21 applies the current gate rule to its complete check set.

Every other applicable gate-fit check keeps its own result. A failed or unresolved internal constraint may prevent the aggregate gate decision from passing, but it does not make freshness, system-role fit, channel fit, regulatory conformance, reference-plane crossing, or another independent fact undefined or not applicable.

An implementation may defer expensive evaluation work after an already blocking result. That is a Work or evaluation policy. A deferred required check remains notRun; it is not published as not applicable or as a successful neutral value. Any aggregate decision must preserve that incompleteness under A.21.

A.20:4.5 - Retargeting boundary

For a StructuralReinterpretation use, receive the A.6.4 arrow r and q, a C.2.1 bounded-use assertion about r. q’s ClaimGraph states the invariant, visible loss, named receiving use, conditions, and affirmative or negative polarity. A.20 opens only when that proposition is the named internal constraint. The separate A.6.4 current-case judgement compares current facts with q and returns satisfies, fails, or cannot decide; it is not the A.20 result. If an operation application is also current, identify and test it separately.

A.20 returns only a ConstraintValidityResult for that named internal constraint. That result may enter the case basis for the separate A.6.4 current-case judgement; the current facts remain separate, and the result reidentifies neither r nor q and records no application. It leaves EntityOfConcernRef as an entity reference and adds no KindBridge or UTS row. An isomorphism or lens, including reverse put and Put-Get or Get-Put laws, enters only as a separately current reversibility claim under its own governor.

Use F.9 separately only when the current claim also needs an obtaining semantic correspondence between two F.17 local senses. Keep its bounded-use claim, optional CL, evidence, and reliance separate; A.20 creates none of them.

A.20:4.6 - Neighboring claims

A.20 keeps only the result content needed to reuse the internal-constraint finding. When another claim is current:

  • E.17 defines publication relations and faces;
  • E.18 defines structure positions, transfers, paths, crossings, and PathSlice identity;
  • G.11 defines refresh planning and performed refresh work;
  • C.27 defines temporal-claim adequacy;
  • A.21 defines check applications, profile use, gate aggregation, and decision consequences;
  • A.10 recovers provenance and bounded reliance; the support pattern defines each evidence relation and B.3 governs assurance; and
  • A.15.2 defines WorkPlans; an asserted dated Work uses the admission grounds in §4.1.

Citing an A.20 result in one of those claims does not copy that consumer’s identity, scheduling, publication, or policy fields into A.20.

A.20:5 - Worked cases

A.20:5.1 - Satisfied unit-conversion constraint

TemperatureConversion-7 converts a Celsius input to kelvin. For the numerical Celsius value c and numerical kelvin value k, the named constraint requires k = c + 273.15 and k >= 0; the corresponding temperature is k K. It is required for this use. For input 25 °C, the test obtains 298.15 K and a non-negative result, so the outcome is satisfied. The witness records the input, formula edition, output, and test result for this evaluation window.

The local summary is satisfied because this is the complete required set for the stated case. That result does not say that a release gate passed or that conversion Work occurred.

A.20:5.2 - Violation and missing-witness variants

If the same implementation returns 297.15 K for 25 °C, the formula constraint is violated and the returned values are the counterexample. If the implementation output cannot be recovered, the outcome is unknown, not violated and not satisfied. If the test was never run, its evaluation state is notRun and the summary is unresolved.

A.20:5.3 - Lossy retargeting

Suppose an A.6.4 arrow r relates an episteme about a detailed equipment classification to one about three maintenance classes. A separate q affirmatively states that the receiving classes preserve the maintenance action selected for every source case under named conditions and allows loss of manufacturer-specific distinctions for that use. Because that proposition is the named internal constraint here, A.20 tests it on the stated cases. A sample supports only those sampled cases unless the evaluation also supplies an argument covering the proposition’s universal quantifier. No reverse mapping is part of that constraint. Facts that establish the invariant and keep loss within the boundary yield the A.20 outcome satisfied; a counterexample yields violated; a missing deciding fact yields unknown. The separate A.6.4 current-case judgement then compares all current facts with q’s conditions and proposition and reports satisfies, fails, or cannot decide; the A.20 outcome does not replace it. Any operation that produced the receiving episteme remains separate.

A.20:6 - Bias annotation

  • Status bias. A green field or class label can look like a result. Recover the constraint application and case.
  • Gate bias. A local constraint result can look like permission or release. Keep the gate decision separate.
  • Checklist bias. A familiar list can look universally required. Select only the constraints triggered by the subject and use.
  • Formalism bias. A reversible optic can look more rigorous than a lossy but adequate case. When q’s proposition is the named internal constraint, test that proposition under its stated invariant and loss boundary; keep any separately claimed reversibility relation under its own governor.

A.20:7 - Check the ordinary local result

For an ordinary A.20 use, check only these five points:

  1. Subject and constraint (CC-A20-1). Name the subject and the constraint and edition being applied.
  2. Case and applicability (CC-A20-2). State the assumptions, case facts, scope, evaluation window, and why the constraint is required, optional, or notApplicable.
  3. Evaluation and outcome (CC-A20-2). Record evaluated or notRun. For an evaluated applicable constraint, record satisfied, violated, unknown, or error under the constraint’s own outcome rule.
  4. Support (CC-A20-1). Give the witness, counterexample, missing-information reason, or error reason that supports that result.
  5. Complete summary (CC-A20-3). Use ConstraintValiditySummary=satisfied only when the complete declared required set is nonempty and every member was evaluated and satisfied.

A specialist constraint such as a stability bound, return-shape condition, or retargeting invariant is present only when its trigger in section 4.3 applies (CC-A20-4).

A.20:7.1 - Extensions only when another use is current

TriggerAdditional checkPattern
A gate consumes the resultKeep every applicable GateFit result independently recoverable; an A.20 failure changes only the A.21 aggregate under its current rule (CC-A20-5). A deferred required check remains notRun (CC-A20-6).A.21
The proposition in an A.6.4 bounded-use assertion q is the named internal constraintApply A.20 to that proposition for the stated case and return only its ConstraintValidityResult; keep r, q, any operation application, and the A.6.4 current-case judgement separate. A Bridge or reversibility claim enters only when separately current (CC-A20-8).A.6.4; add F.9 only for a separate semantic-correspondence claim
Publication, structure, time, refresh, evidence, assurance, or Work is currentKeep those claims in their own result or relation and follow the pattern (CC-A20-9). A.20 adds no publication-face, path, slice, scheduler, gate-profile, or gate-algebra fields (CC-A20-7).E.17, E.18, C.27, G.11, A.10, B.3, or A.15, as applicable

A.20:8 - Common mistakes

MistakeWhy it failsRepair
Class label as truthLipschitzBounds or TypeDomainRange does not identify the constraint application.Name the constraint, edition, case, test, and result.
abstain for everything missingNot applicable, not run, unknown, and policy consequence require different actions.Keep applicability, evaluation state, outcome, and gate consequence separate.
Missing required result joins to passA neutral element erases incompleteness.Use the complete required-set summary rule.
Constraint failure suppresses GateFitIndependent repair information disappears and results depend on evaluation order.Preserve each applicable result; let A.21 combine them.
A.20 becomes a package architecturePublication, paths, refresh, and gate fields are copied into a local result.Keep only the result and cite the consumer’s pattern.
Entity reference becomes bridgeRetargeting and semantic correspondence are confused.Use A.6.4; add F.9 only for a separate cross-semantic claim.

A.20:9 - Consequences

The result retains the local finding and its reuse conditions. The summary rule prevents a missing required check from counting as success; a gate can retain useful independent findings even after one internal failure. The cost is that a consequence-bearing use must name its required constraint set and cannot hide policy inside A.20 status words.

A.20:10 - Rationale

Constraint truth, knowledge about that truth, and a policy response are different. A.20 records the evaluation result. The constraint’s own pattern defines the truth condition. A.21 or another consumer decides what follows. Keeping those steps separate preserves independent findings across evaluation order and leaves policy consequences with the receiving decision.

A.20:11 - SoTA echo

Practice comparisonAdopted moveLimit
Refinement-type, property-based, and proof-carrying validationName the property, case, outcome, and witness rather than publishing an unqualified validation label.A witness supports only the stated property and case.
Dimensional analysis and assumption-bound numerical validationKeep quantity, unit, domain, assumptions, and validity region with the result.The check does not define unit conversion or comparison policy.
Safety and assurance practiceKeep technical finding, evidence use, assurance, and decision consequence separate.A complete record does not make the tested constraint true.
Current FPF A.6.4 retargetingUse the proposition in q as A.20’s constrained subject only when it is a named internal constraint; keep r, q, any application, and the separate tri-state current-case judgement distinct.A semantic Bridge is a separate F.9 relation and use claim.

A.20:12 - Relations

  • E.18 places independently defined transformation and adjacent values in a selected transformation-flow structure.
  • A.6.1 and E.20 define operation and mechanism content whose named constraints may be tested.
  • A.6.4 defines the retargeting arrow r, the separate bounded-use assertion q, and the separate current-case judgement. A.20 may test q’s proposition only when it is a named internal constraint; any operation application remains separate.
  • A.21 consumes check results and defines gate-policy consequences without suppressing independent applicable results.
  • E.17, G.11, C.27, B.3, and A.15 govern publication, refresh, temporal, assurance and Work claims. A.10 recovers provenance and bounded reliance on independently established support.
  • F.9 applies only when an additional semantic correspondence is current.
  • C.2.1 supplies result-episteme identity.

A.20:End

A.21 - Gate Decisions from Independent Check Results

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Gate decision.

Technical result name. GateDecisionResult.

A.21:0 - Use this when

Use A.21 when a named gate must decide whether one bounded action or transition may proceed under an applicable profile rule. Identify every check that the rule requires, including the subject and criterion of each check.

First useful move. Name the action being decided, the profile rule that applies, and every required check result. Map each check result under that rule, then let the worst mapped value win.

Quick worked case. WorkshopEntryGate-4 decides whether CalibrationCycle-17 may start before 16:00. WorkshopEntryProfile-E5 requires two checks: CalibrationCertificate-44 for TorqueWrench-12 is current under CalibrationRule-E3, and WorkshopEnclosure-2 is closed under EnclosureRule-E2. Both checks are evaluated and satisfied, so each maps to pass; the gate returns pass and the cycle may start before 16:00. Recheck if the instrument, certificate edition, enclosure state, profile edition, or time window changes.

If the state of WorkshopEnclosure-2 is unknown, that check remains unknown. WorkshopEntryProfile-E5 maps the uncertainty to block, not to abstain, so the cycle stays on hold until the enclosure is checked. A different policy may accept a bounded uncertainty only through an explicit rule that names the subject, tolerance, consequence, and validity window.

Short boundary. A gate decision is neither work-entry readiness nor performed Work. Use A.15.5 for the ordinary readiness question. An asserted later Work uses the independent admission grounds in §4.9. The gate, plan item and prospective claim do not identify that later Work.

What goes wrong if missed. A green display is mistaken for permission, an unknown required check disappears as a neutral value, two different check subjects are merged by label, or a new path slice is treated as authority to weaken policy.

What this buys. The practitioner can recover what was decided, which rule applied, which facts supported the decision, what action follows, and when the decision must be made again.

Not this pattern when.

  • Use A.20 for one internal-constraint result.
  • Use A.15.5 for full-kit or work-entry readiness without a gate decision.
  • Use E.18 for transformation-flow positions, paths, slices, and structural crossings.
  • Use the pattern that defines the policy, safety rule, regulatory rule, evidence claim, channel condition, or system-role claim for the truth of that check.
  • Use E.17 when the decision needs a source-backed reader face and return to source; use E.24.PUB when its publication occurrence, form, carrier, or availability matters.

A.21:1 - Problem frame

A gate combines results defined elsewhere. A.20 may report an internal constraint; A.10 or B.3 may support an evidence or assurance check; E.18 may establish a structural crossing; a regulatory or safety pattern may define another criterion. A.21 does not redefine those truths. It records how one applicable profile maps their results to one bounded decision.

The gate is optional. A guard, dashboard, readiness label, plan item, path boundary, or publication form does not create a gate decision by resemblance.

A.21:2 - Problem

How can one gate decision remain reproducible without:

  • losing the identity and result of each check application;
  • treating not applicable, not run, unknown, and policy consequence as one value;
  • allowing a missing required result to vanish beside a passing result;
  • inferring policy selection or weakening from a PathSlice boundary;
  • requiring semantic-Bridge, publication, replay, crossing, or LaunchGate apparatus for an ordinary local decision; or
  • turning a prospective work-entry question into a future Work individual?

A.21:3 - Forces

NeedTension
One usable decisionThe practitioner needs one action, while every contributing result must remain recoverable.
Order independenceEvaluation order should not change the decision, but early failure may justify deferring expensive work.
Policy flexibilityDifferent profiles may react differently, but no implicit default or path boundary may supply policy authority.
Plain entry“Worst result wins” is easy to use, while result and rule identities are needed for replay.
Conditional assuranceCrossing, publication, regulation, safety, and reuse can need more evidence, but ordinary local use should stop earlier.

A.21:4 - Solution

A.21:4.1 - The decision result

GateDecisionResult is a C.2.1 result episteme. Its EntityOfConcern is the bounded action or transition being decided. Its ClaimGraph says that one identified profile application maps one complete effective set of check-application results to one decision and action consequence.

Minimum content:

GateDecisionResult:
  resultId
  gateRef
  decisionSubjectRef
  boundedActionRef
  profileApplicationRef
  requiredCheckApplicationIds[]
  optionalCheckApplicationIds[]
  checkApplicationResultRefs[]
  scope
  qualificationWindow
  decisionValue: abstain | pass | degrade | block
  actionConsequence
  recheckCondition
  rationale

decisionSubjectRef names the proposal, transition, crossing, or prospective work-entry claim being decided. boundedActionRef names what the practitioner may do or must hold. Neither identifies a later Work occurrence.

One result is identified by the tuple containing the gate, decision subject, bounded action, profile application, canonical required and optional check-application identity sets, the consumed check-application result refs, scope, and qualification window. A changed rule edition, checked subject, criterion, case, result, scope, or window requires another result. The decision value and rationale are the content derived for that fixed tuple; a contradictory value for the same tuple is an error, not another result to merge.

The rationale links every check-application result to its mapping rule and then to the aggregate and action consequence. A GateDecisionExplanation may restate the rationale and decision value in ordinary language. It is optional and creates no additional decision; the identified result remains the basis for its explanation.

A.21:4.2 - One check application

A GateCheckApplicationResult is a C.2.1 result episteme that identifies one check application, its evaluation state, and any available source result for the gate-facing use:

GateCheckApplicationResult:
  checkApplicationId
  checkKind
  checkedSubjectRef
  criterionRef
  criterionEdition
  ruleApplicationRef?
  caseFactsRefOrValue
  scope
  qualificationWindow
  requirement: required | optional | notApplicable
  evaluationState: evaluated | notRun
  sourceResultRef?
  sourceOutcome?
  mappingRuleRef
  mappingRuleEdition
  mappedDecisionValue?: abstain | pass | degrade | block
  witnessOrReasonRefs[]

The pattern that defines or tests the source claim determines sourceOutcome; A.21 only applies the cited mapping rule. A not-applicable application states why the criterion does not apply. A not-run application states that evaluation work did not produce a result. Unknown, error, violation, and success keep the meanings supplied by their source patterns.

The application identity includes the checked subject, criterion and edition, applicable rule application, case facts, scope, and window. Two SystemRoleFit applications for different Systems and two RegulatedConformance(X) applications for different regulators or rule editions are different applications. Deduplicate only identical application results under these identity conditions. If two copies claim different source outcomes for the same identity, stop and resolve the contradiction; do not join them by checkKind.

When a publication or selected structure needs a short GateCheckRef, that value refers to one identified GateCheckApplicationResult. It is not the old {aspect, kind, edition, scope} record and cannot omit the checked subject, criterion or rule application, case, scope, or window needed to resolve that result.

A.21:4.3 - Profile application

A GateProfile describes a policy. It does not show that the policy applies. Every gate decision points to the current application of one profile rule. That application identifies:

  • the profile rule and edition;
  • the gate, decision subject, and bounded action to which it applies;
  • its scope and qualification window;
  • the complete required and optional check set;
  • the mapping rule for each applicable source outcome;
  • the consequence attached to each aggregate decision; and
  • any separately required authority or responsibility relation.

A.21 has no implicit default profile. A branch name, PathSlice, sentinel, publication mode, product label, or earlier decision does not select or authorize a profile. A new slice may bound changed data or trigger reevaluation; it cannot weaken inherited safety, regulatory, evidence, or other obligations. Any weakening needs another current rule application that permits it and any authority relation required for that change.

A.21:4.4 - Complete check set and independent results

Before aggregation, recover the complete effective required set from the profile application. Every required application is present even when it is notRun, unknown, error, or failed.

  • notApplicable is allowed only when the application gives its scope or applicability reason.
  • notRun never becomes abstain or pass.
  • unknown and error remain visible before their explicit profile mapping.
  • a failed A.20 result can prevent passage but cannot make freshness, channel, role-fit, regulatory, crossing, or another independent check inapplicable.
  • evaluation work may defer an expensive check after a blocking result, but the deferred required check remains notRun in the result.

If a profile deliberately accepts known uncertainty, its mapping rule names the checked subject, tolerated uncertainty, permitted bounded action, consequence, and expiry or recheck condition. A generic neutral fold is insufficient.

A.21:4.5 - Aggregate and action meaning

In ordinary language: the worst mapped result wins. Only after every required application is present and its mapping is known, the technical aggregation is the order-independent join:

abstain <= pass <= degrade <= block.

The join is associative, commutative, and idempotent. abstain is neutral and block absorbs other values, but those algebraic properties do not change the source results.

The join determines the decision value; the profile rule also determines its action consequence. Retain every applicable action restriction unless an authorized rule changes it. For example, two checks may each map to degrade, one requiring reduced speed and the other supervision: the permitted action must satisfy both. Conflicting restrictions permit no action unless an applicable rule resolves the conflict; the shared degrade value alone supplies no permission.

DecisionMeaning for the bounded action
abstainThe applicable profile says this gate makes no decision for this action and names the remaining decision route or absence of one. It grants no permission. It is not used for missing, unknown, failed, or unrun required checks.
passEvery required application is present and the current profile accepts the bounded action without an added restriction, within the stated scope and window.
degradeThe profile accepts only the named restricted or conditional form of the action. The result states the restriction, stop or exit condition, and recheck condition. It is not an unspecified “proceed carefully”.
blockThe profile refuses or holds the bounded action under the current facts and states what change or new result can reopen the decision.

An optional application affects the aggregate only when the cited profile rule says it does. A required missing or notRun result can map to degrade or block under an explicit rule, never to pass or neutral abstain.

A.21:4.6 - Scope, composition, and change

Compose check sets only through the profile applications that cover the decision subject and scope. A more specific application may add, replace, or remove a check only when its policy rule and applicability fact say so. Preserve parameterized identities such as regulator X and its rule edition.

lane, locus, subflow, and profile may be used as scope values only when the selected structure or policy defines the corresponding boundary for this application. A scope label alone neither selects a profile nor merges check applications. Recompute the result when the decision subject, bounded action, profile application, required set, check application identity or result, scope, or window changes. A refresh, edition bump, expired evidence window, changed crossing, or changed path slice matters only when it changes one of those inputs under its own pattern.

A.21:4.7 - Optional LaunchGate use

Use LaunchGate only when an A.21 gate decision is needed for one prospective workEntryClaimRef, WorkPlan or PlanItem entry question, and bounded attempted action. The gate refers to that prospective claim; it never targets a not-yet-existing Work individual.

A.15.5 remains the ordinary route for full-kit and work-entry readiness. Add a LaunchGate only when the selected transformation-flow structure contains that gate use. Freshness, design-run-tag consistency, A.20 ingress validity, structural crossing, and SquareLaw are checks only when their claims, rules, and defining patterns are current. No one of them is mandatory merely because the word “launch” appears.

If a required ingress A.20 summary is not satisfied and the applied profile defines a pre-run barrier, the aggregate is block. Other available results remain visible; deferred checks remain notRun.

A.21:4.8 - Crossing and semantic-Bridge boundary

For a structural crossing, receive the changed-binding and crossing facts from E.18. Add a crossing check only when its criterion applies. SquareLaw is required only when the E.18 crossing rule for that case requires it.

A structural crossing does not imply an F.9 semantic Bridge. Add an F.9 Bridge, bounded-use claim, reliance, optional Bridge Card, or optional CL only when the separate semantic-correspondence relation and downstream use obtain. A gate whose decision does not rely on semantic correspondence carries none of this apparatus. Do not encode absent Bridge material as mandatory fields with none values.

A.21:4.9 - Guards and check families

A guard event is not automatically a GateCheck. When a selected structure assigns a guard failure to a gate, the current profile may consume that identified event through a declared check application and mapping rule.

The following names are recognition aids, not a universal catalogue: freshness, design-run-tag consistency, reference-plane crossing, comparator constraints, evidence completeness, safety envelope, regulator conformance, system-role fit, channel fit, equivalence preservation, outflow audit, and snapshot consistency. Each application names its checked subject, criterion, rule edition, case, evaluation state, and any available source result.

Use A.10 for claim-bound evidence reliance and B.3 when a named assurance claim is current. Use A.2 and C.3.2 for system-role classification, A.2.1 for assignments, and F.6 only for a consumed assignment-bound Work attribution. A.2.6 answers whether a claim covers the selected slice; channel criteria remain with their domain pattern. Use E.18 for crossing claims within its applicable structure and the applicable comparison pattern for comparator claims.

If later Work is asserted, first establish its A.13 core: the performing System, local agential-role kind and membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits that performance; F.6 applies afterward only for assignment-bound attribution.

A.21:4.10 - Publication, rationale, and reuse

The ordinary one-time result needs the content in section 4.1 and a short rationale; existing descriptions may supply it without a new form. It does not require a Multi-View Publication Kit (MVPK) face, AssuranceLane, evidence bundle, Bridge apparatus, cache key, or equivalence witness.

When publication is current, E.24.PUB defines the publication occurrence, form, carrier, audience, bounded use, and availability. Use E.17 when the result needs a source-backed reader face and return to source. A publication mode changes only that form; it neither selects a profile nor changes the required check set or aggregate. The published minimum is the result identity, decision subject, profile application, check-application refs, decision, action consequence, scope, window, and recheck condition. Crossing, evidence, regulation, safety, and assurance fields appear only when the corresponding claim is current.

A DecisionLog is an optional audit or reuse record that cites one or more GateDecisionResult values. It may retain source outcomes, mappings, rationale, evidence refs, and change history; it neither creates nor changes the decision.

Require an equivalence witness only when reuse, cacheability, or a stability interval is claimed. That witness covers every input whose equality is needed for the claimed reuse. A changed profile edition, required set, checked subject, criterion, case, source result, mapping, scope, or window defeats reuse and requires another decision.

A.21:5 - Worked cases

A.21:5.1 - Ordinary local pass

The workshop case at the entry uses two required checks. Each application names its subject and criterion: CalibrationCertificate-44 for TorqueWrench-12 is current under CalibrationRule-E3, and WorkshopEnclosure-2 is closed under EnclosureRule-E2. WorkshopEntryProfile-E5 maps both satisfied results to pass. Worst-result aggregation gives pass; the short rationale names both results, and the bounded action is “start CalibrationCycle-17 before 16:00”. No publication or replay record is required.

A.21:5.2 - Unknown and failed checks

If the state of WorkshopEnclosure-2 cannot be established, that application is unknown; it does not disappear as abstain. The profile maps it to block, so the action is “hold the cycle and inspect the enclosure”. If CalibrationCertificate-44 is expired while the enclosure check passes, the certificate application maps to block; the passing enclosure result remains available for repair and need not be rerun unless its own recheck condition is met.

If inspection was not performed after the block was already known, record that check as notRun. It remains in the required set and cannot support pass.

A.21:5.3 - Conditional high-consequence extension

RegulatedReleaseProfile-E9 adds RegulatedConformance(Regulator-X, Rule-E9) and evidence-completeness applications for ReleaseLot-27. Unknown regulator conformance maps to block. The profile cites Regulator X, Rule E9, the evidence tolerance, the refusal consequence, and the window. If the decision is published, apply E.24.PUB for the publication occurrence, form and carrier, adding E.17 when a source-backed reader face and return to source are needed. If reuse is claimed, supply the equivalence witness for the reused inputs; an audit record remains optional. Internal reuse alone does not require publication.

A.21:6 - Bias annotation

  • Green-display bias. A display can look like a decision. Recover the gate result and applicable profile.
  • Neutral-value bias. An algebraic neutral can hide an unknown or unrun check. Preserve applicability and evaluation state before mapping.
  • Profile-label bias. A profile name can look authoritative. Require its applicable rule and any separate authority relation.
  • Infrastructure bias. Publication and replay fields can look like the gate itself. Keep the decision result primary and add infrastructure only for its triggered use.

A.21:7 - Check the ordinary gate decision

  1. Decision. Name the gate, the action or transition being decided, its scope, and its time window.
  2. Applicable rule. Point to the profile rule and edition that apply to this gate and subject. Recover its required checks, mappings, consequences, scope and window, and any authority the rule itself requires.
  3. Checks. For each check, name its subject, criterion and edition, case, requirement, evaluation state, any available source result, and mapping rule.
  4. Nothing missing. Keep every required check visible, including notRun, unknown, error, and failure.
  5. Worst result wins. Aggregate only after the rule has mapped every required result. A missing or unrun required result cannot support pass.
  6. Next action. State what pass, degrade, block, or abstain means for this action, retain every applicable restriction under §4.5, and state when to decide again.
  7. Boundary. Do not turn the decision into work-entry readiness or performed Work, and add no crossing, Bridge, publication, or assurance claim that is absent.

A.21:7.1 - Triggered additions

Current useAddPattern
Launch decisionProspective work-entry claim and only the checks selected by the applicable profileA.15.5, E.18, and the pattern defining each check
Structural crossingChanged-binding and crossing facts; SquareLaw only when its crossing rule appliesE.18
Semantic correspondenceSeparate Bridge and bounded-use claim; optional evidence or publication apparatus only when usedF.9, F.17; E.17 for a source-backed reader face, E.24.PUB for publication occurrence, form, carrier, and availability
PublicationForm, carrier, publication occurrence, and the minimum decision refsE.24.PUB; E.17 when a source-backed reader face is needed
Evidence, safety, regulation, or assuranceSource result and its evidence or assurance relationA.10, B.3, or the applicable domain pattern
Reuse or replayEquivalence witness when claiming reuse, cache, or stability over an interval; optional decision log for audit, history, or replay§4.10; G.6 when a citable provenance path is needed, G.11 when currentness or refresh is at issue, and E.24.PUB when published

A.21:8 - Common mistakes

MistakeWhy it failsRepair
Green cue as passNo result, profile application, or check set is recoverable.Recover the A.21 result or leave the cue non-decisional.
Merge by check labelDifferent subjects, criteria, regulators, or cases disappear.Merge only identical check-application identities.
Unknown as abstainA missing required fact becomes neutral and may yield pass.Preserve unknown; apply an explicit profile rule.
New slice weakens checksLocality is mistaken for policy authority.Cite another applicable policy fact and any required authority.
degrade with no actionThe word sounds precise but gives no usable consequence.State the permitted restricted action, condition, stop, and recheck.
Every gate is a LaunchGate or crossingOptional branches become universal infrastructure.Activate only the branch present in the decision subject and selected structure.
Every crossing has a BridgeStructural and semantic relations are collapsed.Use E.18 for the crossing and F.9 only for a separate semantic relation.

A.21:9 - Consequences

The gate result preserves repair information, prevents unknown or unrun required checks from disappearing, and makes profile change auditable without turning a path boundary into authority. Ordinary gates stop after one result and short rationale; publication, replay, crossing, safety, regulation, and assurance add cost only when their claims are current.

The cost is explicit identity. A practitioner must name the decision subject, profile application, and each required check application instead of relying on labels such as “green”, “Core”, or “regulated”.

A.21:10 - Rationale

Constraint truth, evidence about that truth, policy application, and bounded action are different claims. The source patterns define the claims and tests; their evaluations establish the check results. A.21 applies one current profile and records the consequence. Keeping those claims separate makes the decision independent of evaluation order and keeps failures useful for repair.

The join lattice gives a compact, deterministic aggregation after the complete effective check set has been identified and mapped under the profile. It does not supply applicability, evidence, permission, authority, or a missing result.

A.21:11 - SoTA echo

Basis or practice comparisonMove used in A.21Limit
The join-semilattice defined in §4.5Use the associative, commutative, idempotent worst-result join after explicit profile mapping.Algebra does not make unknown or unrun input neutral.
Open Policy Agent: Rego policy evaluation, including undefined results and explicitly declared defaultsKeep the applicable policy, its inputs and evaluated result recoverable; A.21 separately specifies the mapping to a bounded action.Rego values and undefined results do not themselves define A.21 decision values or authority.
in-toto Statement v1 and SLSA v1.2 provenance bind typed attestations and production information to identified artifactsRetain the subject and claim references needed by the declared audit, transfer or reuse. Publication follows the receiving use.Attestation or provenance information supplies neither the gate decision nor the truth of every source claim; A.21 keeps those judgements separate.
Structural-crossing rules supplied by E.18Apply crossing equations to the identified crossing when its rule requires them.A structural crossing does not imply a semantic Bridge; each applies only when its own relation and use are current.

A.21:12 - Relations

  • A.20 supplies internal-constraint results or a complete required-set summary without gate policy.
  • E.18 supplies selected-structure positions, paths, slices, and structural crossing facts; it does not make every work-entry question a gate or crossing.
  • A.15.5 defines full-kit and work-entry readiness and remains the ordinary route when no gate decision is current.
  • Source claims remain under the applicable subject patterns named in §4.9; safety and regulatory criteria remain with their domain patterns.
  • F.9 and F.17 apply only to a separately established semantic correspondence and bounded use.
  • E.17 governs a source-backed reader face and return to source; E.24.PUB governs publication occurrence, form, carrier, audience, bounded use, and availability when the result is published.
  • G.6 applies when a citable evidence-provenance path is needed; G.11 governs source currentness and refresh when changed inputs may make the result stale. Reuse inputs and equivalence remain under §4.10.
  • F.19 keeps the ordinary decision path visible before algebra, publication, and assurance extensions.

A.21:End

A.22 - Structure and Structural Views

Type: Architectural pattern Status: Stable Normativity: Normative unless marked informative

A.22:1 - Problem frame

Use this pattern when a practitioner needs to select U.Structure as the EntityOfConcern: an organization among constituents and obtaining relations, selected to expose a relation class, applied constraint, invariant, variation class, preserved arrangement, or lost arrangement that changes the next engineering or reasoning action.

Recover the organization selected for the named use:

  1. identify every constituent independently through the content that defines its kind and identity;
  2. recover the relation occurrences among those constituents that obtain under their predicates;
  3. state the constraints applied to those constituents and relations, plus the named selection-use frame that says what question or action this organization serves;
  4. name the resulting selected organization and the admissible action or stop that follows.

When the account asserts dated selection Work, establish its independent grounds under §4.1. Those facts explain the performed selection and remain outside U.Structure identity. If the judgment must persist, identify a separate C.2.1 result episteme whose claim content designates the selected structure.

The four values above can be stated in ordinary prose or recovered from an existing description. The following optional aid also keeps use limits and any separately needed claims visible:

StructureQuestionCard@Project:
  named selection use:
  independently identified constituents:
  obtaining relation occurrences selected:
  constraints applied:
  selected structure:
  preserved structure:
  lost, hidden, or excluded structure:
  admissible action:
  stop or non-admissible overread: stop or return condition
  grounded non-admissible overread, optional:
  selecting system, method, and dated work, only when dated Work is asserted:
  selection-result episteme, when a durable result is needed:
  claim scope or effective reference scheme of that claim, if current:
  reliance relation, if a neighboring reliance claim is being made:

StructureQuestionCard@Project is a project-side triage aid for this selected-structure use. It is not a new structure kind. Fill the reliance row only when extraction, coarsening, source-description, base-dependence, grounding, evidence, lens, simulation, representation, or action reliance is being claimed; otherwise leave it unused and keep the move on selected structure.

The @Project suffix is a local retrieval cue. If the account separately asserts a composite project U.Work, identify that Work and how the current selection, decision or description concerns it. The suffix supplies neither identity nor that relation; the same applies to ArchitectureStructureKindTriage@Project.

Stop when the selected organization and next use are clear. Develop a neighboring description, view, publication, extraction, comparison or other claim only when the receiving task needs it.

What goes wrong if A.22 is missed: the practitioner reasons from the visible diagram, source publication, source-use record, lens output, generated representation, project record, or architecture description instead of asking which organization is selected and what loss or reliance boundary matters for action.

What A.22 buys in practice: a practitioner can name selected structure, state preserved and lost structure, name source-basis or lens reliance only when it is being claimed, add a StructureUseReturnCondition when loss matters, and apply the FPF definition or test for any non-structure claim being made.

Not this pattern when the question under repair is grounded architecture adequacy, architecture structural-view adequacy, or mathematical-lens use. Use C.30, C.30.ASV, or C.29 respectively. For any other claim, use the pattern that defines or tests that claim and keep A.22 only to the selected-structure portion.

For unresolved wording: when the wording still may name a structure, a structure description, an architecture description, a view, a publication form, or another claim, use C.30.P or C.30.STRAT first as triggered. Apply A.22 only after the selected-structure claim or structure-view portion is recoverable.

A.22:2 - Problem

FPF needs a selected-structure EntityOfConcern that is usable across domain ontologies, mathematical formalisms, architecture notations, and publication forms. Working projects often notice that “the structure” is doing work:

  • dependencies repeat across cases;
  • a method or work description hides an invariant relation;
  • a model compresses a trace by preserving one relation class and losing others;
  • a diagram shows an arrangement but is mistaken for the arrangement itself;
  • a mathematical lens exposes preserved structure but is then overread as ontology;
  • an architecture discussion needs selected structure over a holon before it can describe architecture.

How can FPF let a practitioner name structure as an EntityOfConcern while preserving the distinction between:

  • selected structure and the source-description relation, source-use relation, evidence relation, lens output, simulation, generated representation, or declared substrate from which it was inferred or declared;
  • structure and a Description episteme or view of that structure;
  • structure and a publication face, diagram, table, graph, or publication form;
  • structure and mathematical-lens application;
  • structure and another FPF claim kind whose definition or test remains in the cited pattern;
  • structure in general and architecture-specific structure selected by C.30.

A.22:3 - Forces

ForceTension
First-principles structure EntityOfConcern vs ontology inflationFPF needs a reusable selected-structure EntityOfConcern for organizations that expose relations, applied constraints, invariants, variation classes, preserved arrangement, and lost arrangement, but adding one such EntityOfConcern can accidentally invite many false root kinds.
Useful compression vs structure-use returnStructure makes work easier by compressing cases, but a StructureUseReturnCondition is needed when compression, extraction, coarsening, source-description reuse, base-dependence reuse, grounding reuse, evidence reuse, lens reuse, simulation reuse, or representation reuse hides a distinction needed for action.
Description and view usability vs structure confusionDescriptions and views make structure inspectable, but a useful view can be mistaken for the structure itself.
Mathematical-lens application vs mathematical overreadC.29 lens output is usable within its declared mapping, preserved structure, lost structure, and stop condition; any evidence, causal, assurance, or decision claim uses its predicate and result.
Architecture dependency vs architecture takeoverArchitecture uses selected structure through C.30; A.22 does not import architecture as its parent or make every structure an architecture.
Plain engineering speech vs Tech recoveryWords such as structure, graph, architecture, module, function, interface, pattern, block, layer, level, tier, stack, expert, cache, router, and gate can remain in Plain prose, but a claim that depends on their precise meaning needs recoverable Tech fields and pattern applications. Use C.30.STRAT when a source label leaves the selected-structure claim ambiguous.

A.22:4 - Solution

Select U.Structure as the A.22 ontic head: a dependent, non-agentive organization selected from independently identified constituents and obtaining relation occurrences under applied constraints for one named use frame.

The constituents keep their identities and kinds. Every selected relation occurrence must already satisfy its defining predicate and retain identity under that predicate’s occurrence rule. A system or practitioner selects their organization; A.22 supplies the identity and boundary rule for that selected organization.

The applied constraints are the constraint claims used in the selection judgment, not the identity of the document, table, rule card, or constraint episteme that carries them. A usable frame states the question, admissible action, and stop or return condition. A generic phrase such as “current use” or “appropriate structure” is not a use frame. Any optional explanatory overread follows F.19:4’s plausible-reader test and remains outside structure identity.

Ordinary structure selection needs the four discriminators below. An account of dated selection Work additionally uses its admission grounds; a durable result episteme, operation binding, direct participation relation or decision also retains its identity outside the structure.

A diagram, graph, table, model, description, view, or publication may designate, represent, or describe the selected organization and its already identified constituents. Use C.2.1 for the describing episteme, E.17.0 for claimed view membership, and the publication or source-use patterns for those claims. Use C.29 when a mathematical representation-choice, transfer, or reliance question remains unresolved; the participant and relation predicates remain the obtaining basis.

A.22:4.1 - Base U.Structure Identity and Selection

For a selected structure S, recover four identity discriminators:

StructureIdentity(S) = <
  independently identified constituents,
  selected obtaining relation occurrences,
  constraints as applied,
  one named selection-use frame
>

Base U.Structure identity has no ambient context field. A bounded-context label, U.ContextSlice, U.ClaimScope, project record, description, view, graph, table, or publication is not automatically an additional discriminator. If a scope is referenced by an applied constraint, that constraint contributes through the third discriminator. If a model-use structure is independently selected as a constituent of another structure, it contributes through the first discriminator.

The first discriminator is a plurality, not a graph node set created by notation. A separately useful C.13 collection may designate the same constituents, but collection membership neither proves parthood nor replaces their identities. The second discriminator contains the relation occurrences chosen for this organization; a relation name, edge label, tuple position, or adjacency row is insufficient. The third contains the semantic constraints applied; changing only the rationale, formatting, or publication of an unchanged constraint claim does not change this discriminator. The fourth names the use question, admissible action, and stop or return condition.

Two references resolve to the same U.Structure when all four discriminators resolve to the same values. A changed designator, selecting system, method, work occurrence, result episteme, description, graph, representation language, view, or publication leaves the structure unchanged when the four discriminators remain unchanged. Replacing a constituent, a selected relation occurrence, an applied constraint, or the named use frame can identify another structure.

If a relation occurrence may have been reidentified, apply its relation pattern before reapplying A.22. A change to an explanatory guard alone does not change identity. If its content changes an applied constraint or a frame value, compare that existing discriminator.

If no current predicate definition, applicability condition, or occurrence rule can identify the required constituent or test the obtaining-relation claim for this use, stop at the description or representation and return missing-governor. If the governor exists and the available case basis is sufficient to apply its positive test but that test fails, return factually unsupported; if a fact needed to decide the test is unavailable, return missing-information.

State a negative only when an applicable non-obtaining criterion or complete closure basis and satisfying facts establish it. If the constraints or named use frame are absent, name that gap: the material may show an arrangement, but it does not yet support the claimed selected U.Structure.

For asserted dated selection Work, first establish the A.13 core: the performing System, local agential-role kind and membership criterion, and an obtaining assignment of its declared direct species for the relevant scope and time. A.15.1 independently admits the performance with its enacted Method and extent; F.6 applies afterward only for assignment-bound attribution. Establish any direct participation or A.6.1 operation binding needed by the receiving claim separately.

The following two records are recovery aids, not new ontic kinds. In SelectedStructureBasis, the selected structure, constituents, selected obtaining relations, applied constraints, and use frame state identity; the preserved/lost and action/stop rows state the use-return boundary rather than adding identity fields.

SelectedStructureBasis:
  selectedStructureRef:
  constituentRefs:
  selectedObtainingRelationOccurrenceRefs:
  appliedConstraintClaimRefs:
  namedSelectionUseFrame:
  preservedStructure:
  lostHiddenOrExcludedStructure:
  admissibleAction:
  stopOrNonAdmissibleUse: stop or return condition
  groundedNonAdmissibleUse?:

StructureSelectionUse:
  selectingSystemRef:
  selectionMethodRef:
  selectionWorkRef:
  directParticipationOrOperationBindingRefs?, when the receiving claim needs them:
  selectedStructureRef:
  selectionResultEpistemeRef?, when the judgment must persist:
  selectionDecisionRef?, when an accountable choice is current:

StructureSelectionUse is used when that dated performance is asserted; it records how the system performed the selection and reached the judgment. SelectedStructureBasis records the four identity discriminators plus the use-return boundary. Do not copy the system, work, method, result episteme, or decision into the structure basis.

A U.ClaimScope, effective reference scheme, or model-use structure that merely qualifies a claim about either record does not enter base identity. A scope referenced by an applied constraint or a model-use structure selected as a constituent enters only through that already declared discriminator. stopOrReturnCondition is another name for stopOrNonAdmissibleUse, not an independently filled value.

A.22 structure-aspect names such as functional, mereological, modular, transformation-flow, control, semantic, causal, dynamical, algebraic, topological, geometric, or coarse-grained remain cues for which relations and constraints to recover. They do not identify a structure without the four discriminators. C.30.ASV ArchitectureStructureKindRef values remain architecture-local classifiers; a matching label does not imply identity.

A.22:4.1a - Auxiliary boundary

Use description, publication, source-use, evidence, work, gate, decision, release, architecture-description, and mathematical-lens patterns when those claims are being made. The A.22 application contains the selected-structure portion and any structure-use return condition required by §4.5; use each neighboring pattern only for the definition or test it contributes. A publication, diagram, graph, table, dashboard, file, model card, generated representation, or lens output may make a structural description or view available; it does not become the selected structure or supply neighboring claim authority by appearance.

A.22:4.1b - Constraint-governed unfolding structure

Use A.22.CGUS to clarify available continuations and their conditions. Use its formal branch when the named use depends on the identity or CGUS membership of the selected organization. Then identify one A.22 structure with several locally declared loci whose bindings identify the independently selected constituents for the unfolding question; its selected obtaining relation occurrences and applied constraint claims must define at least two potential continuations across allowed cases. The loci are not free-standing A.6.5 slots. A separate case- and time-indexed result may enable zero, one, or several candidates. This specialization remains U.Structure; a Method, plan, Work or present-case continuation result is a separate object.

A route card, table, graph, README entry, narrative, slide, or happy-path example may describe or demonstrate the unfolding structure, but it is not the structure itself.

A.22:4.1c - Bounded And Cross-Context Model-Use Structure Specializations

BoundedModelUseStructure is a U.Structure selected over one model episteme, admitted model-use holons, the obtaining model-applicability, actual model-use, and model-expression-coherence occurrences defined and tested by A.1.1, applied constraint claims used by the selection judgment, and one named bounded-model-use frame. Its A.22 identity uses exactly those constituents, selected occurrences, constraint claims, and frame.

A claim scope, membership outcome, boundary display, or carrier is not an applied constraint by itself; a constraint claim may instead state a proposition about that scope or its A.2.6 membership predicate. No boundary crossing participates in that identity.

Continuity across model editions additionally requires the C.2.1 episteme-edition relation and declared A.1.1 continuity rule. BoundedModelUseStructure is not a holon, description, view, or endpoint manufactured by a later crossing.

CrossContextRelationStructure is a conditional specialization of a different already identified U.Structure. Membership requires obtaining crossing occurrences that satisfy independently defined predicates, selected among several bounded model-use structures, applied constraints, and one named crossing-analysis use, with all four A.22 base discriminators established.

Until a compatible crossing predicate and current facts establish those occurrences, a Context Map can describe only a proposed crossing organization and no positive CrossContextRelationStructure member is asserted. The selecting system and its work remain separate. Sharing a participant does not merge structures, and overlap does not prove parthood.

CrossContextRelationStructure is a provisional A.22-local designator for this conditional membership rule.

DDD Context Mapping names a repeatable way of constructing a Context Map; a U.Method claim uses A.3.1. When a mapping plan is needed, use A.15.2. An asserted dated mapping Work uses the complete admission grounds in §4.1; assignment-bound attribution additionally uses F.6.

C.2.1 identifies the resulting Context Map episteme independently. While crossing occurrences or the four structure discriminators are missing, its EntityOfConcern is the proposed or described organization. Once both are established, an episteme may designate the selected structure. It is additionally a U.View only when E.17.0 establishes EpistemeViewpointConformanceRelation(E, P). Use C.29 for an unresolved mathematical correspondence or transfer question, and E.17/E.24.PUB for rendering or publication. These conditions preserve the source terms without merging the mapping, its product and the described organization.

A.22:4.1d - Transformation-flow structure network profile

Use E.18.NET when one engineering use selects two or more independently identified transformation-flow structures, or nested networks of them, together with obtaining relations across their boundaries. Apply the four A.22 discriminators: the TFS or nested-network members are the constituents; the cross-member relation occurrences satisfy their defining predicates and identity rules; the applied endpoint, boundary-exposure, and acyclic direct-member constraints are selected under E.18.NET; and the named network-use frame states the practical question, admissible action, and stop or return condition.

Any optional explanatory overread follows F.19:4 and remains outside structure identity. The return condition reopens selection when a member, relation, constraint, or use-frame value changes and is not a fifth identity discriminator. The result is one dependent, non-agentive U.Structure specialization. E.18.NET defines the network’s detailed identity, reference, recursion, local-state, and conformance rules; A.22 does not copy those fields.

Use the first discriminator to record structure constituents. Introduce a separately re-identifiable world-side membership relation only when a receiving use needs it and can supply its participants, obtaining predicate, and identity rule.

A.22:4.9 - Resolve a reference to one selected structure

Use SelectedStructureReference when a description, view, transformation account, or architecture claim must refer to the same selected structure. It is a bounded C.3 kind of reference values and an A.6.5 RefKind for this use, not another durable public U-kind. Its target range is the U.Structure individuals identified in :4.1.

A candidate reference value is interpreted as <R, d>: one effective reference scheme and one designation value identified under that scheme. R supplies designation equality and the resolution Method. Designation d includes every registry snapshot/version, temporal qualifier or other input that selects its target under R. A time of inspection or freshness observation that does not select the target remains an evaluation condition. Successful resolutions of one fixed <R,d> must identify the same S; using a lookup basis that selects another target requires an explicit change to d or R.

The reference value remains the same when both components remain the same under those rules. Different reference values can resolve to the same structure; identical printed tokens under different schemes need not. A carrier, description episteme, diagram, or the structure itself is outside this reference-value domain.

The membership criterion requires R to resolve d to exactly one independently identified structure S with all four :4.1 discriminators. The receiving use fixes the declaration edition and C.3.2 judgment slice with explicit versions and a temporal selector. It evaluates resolution using the target-selecting pins already fixed in d under R; a time-independent resolution states that condition. A new assessment can leave the same reference unresolved when its fixed resolution grounds are unavailable, without selecting another target.

For an admissible reference candidate, established unique resolution to S satisfies the criterion; a completed resolution to no target, several targets, or an object outside the target range fails it. An unavailable resolution dependency or unsettled target identity leaves the judgment unknown. An uninterpretable candidate or an inapplicable slice is not-applicable under C.3.2.

In every case without established unique resolution, the structure-dependent use remains unresolved; no negative claim about a purported structure follows. The kind continues while this candidate interpretation and membership distinction remain unchanged.

A returned document can help recover S, but the reader must recover the structure it describes rather than use the document as S. Resolve the four discriminators before testing any additional receiving condition, such as model-use or transformation-flow specialization. Reference membership establishes neither that specialization nor a description, viewpoint, architecture, or reliance relation. A proposal lacking established structure identity remains proposal content under C.2.1.

Retargeting explicitly selects a new <R,d> by changing R or a target-selecting component of d, then repeats resolution and the affected receiving tests. A path whose current content describes a different organization cannot replace S. Preserve the earlier target and dependent conclusions; reopen only uses whose target or required basis changed. A changed carrier or notation can preserve both reference and target when R retains their meanings.

For example, two drawings can designate one pump-flow structure with the same constituents, obtaining connections, applied constraints and use frame. They may use different reference values while resolving to that same S. A new drawing that proposes a replacement connection is proposal content until its required structure basis is established; retaining the old file path does not retarget the earlier reference or make the proposed connection obtain. For a registry reference with d=(CoolingFlow, registry@v1, t1), choosing the same printed path under registry@v2 and t2 changes d and requires explicit selection of that new reference. If the v1 snapshot becomes unavailable, the earlier reference remains the same and its resolution judgment becomes unknown; v2 does not supply a replacement target for it.

A.22:4.2 - Structure claim reliance relation selection

When a structure claim relies on something beyond the selected structure, identify the reliance relation and apply the definition or test that supplies its participants and conditions. Use that definition for the relation’s required fields and use limits.

Reliance relation kindWhat is namedDefinition or test to apply
Source-description relationsource episteme, source view, publication form or rendering where relevant, described structure or structure claim, source-basis pins or structure-use return condition, admissible use, and any grounded non-admissible useA.7 when nearby objects need distinguishing; C.2.1 and E.10.D2 for the episteme and describing use; E.17.0 for claimed view membership; A.6.3 for a source-to-receiving construction; E.17 for a source-backed reader face; E.24.PUB and local rules for publication
Base-dependence or basednessdependent and base, named direct predicate, and an optional C.2.1 assertion episteme; scope, time and evidence only when the relation or receiving use needs them; admissible use and any needed return conditionA.6.6 for direct-relation recovery and optional assertion content; the subject-specific relation pattern supplies participant meanings, applicability, obtaining predicate and any needed occurrence identity
EntityOfConcern or empirical groundingclaim-bearing episteme, its EntityOfConcern, and effective ReferenceScheme; when empirical grounding is claimed, the grounding holon, covered claim subgraph, and obtaining C.2.1 EpistemeEmpiricalGroundingRelation; claim scope, optional model-use structure, describing-use viewpoint, reference plane, and observation or witness condition only when currentC.2.1, A.2.6, A.1.1, E.17.0, A.6.4, A.6.3.RT, and A.6.6 only for a separate base-dependence claim
Evidence or witness reliancethe evidence-use relation and target claim; provenance, witness publication or observation record, time and currentness when the receiving use needs them; if an evidence graph is current, its graph path remains a mathematical or provenance expression rather than an action routeA.2.4 for evidence-use classification; A.10 when provenance or bounded reliance must remain recoverable; G.6 when a citable evidence-provenance path is needed
Mathematical-lens reliancethe mathematical object and its correspondence to the named subject, the structure preserved or lost, and the use and stop conditions needed by the receiving claim; when C.29 is applied, retain its result and any output reference required by the receiving useC.29 when mathematical representation choice, transfer, or reliance remains unresolved; C.26 only when a residual contextual-model obstruction calls for its quantum-like lens; F.9 only for separately needed cross-context semantic correspondence; the named mathematical-lens pattern for its claims
Simulation, generated representation, model, or extracted tracesource episteme and publication when source availability matters, representation or extraction method, validation boundary, preserved structure, lost structure, and any structure-use return condition required by §4.5C.29 when a mathematical representation-choice, transfer, or reliance question remains unresolved; E.10.D2 and E.17.0 for description and view claims; E.17 and E.24.PUB for publication; C.2.1 only for episteme identity or a claimed empirical-grounding relation; A.10 for evidence; or the pattern that defines or tests the simulation, extraction, or validation claim

If the required reliance relation remains unestablished, retain the usable source description or recognition cue with that limit. Do not create a generic reliance record to make the claim look resolved.

U.Structure does not carry description, representation, extraction, mathematical-lens, simulation, or generic reliance state as an internal structure field. Those are source-description, source-use, base-dependence, evidence, lens, extraction, simulation, or publication relations about a structure. PublicationRef is not an admissible substitute for the source episteme, source view, evidence relation, direct-relation assertion, or lens output.

A.22:4.3 - Structural descriptions and views

Structural descriptions use C.2.1 episteme identity; claimed view membership uses E.17.0. Every record whose name ends in Description@Context here designates an existing U.Episteme: C.2.1 supplies its identity and E.10.D2 constrains its describing use. Every record whose name ends in View@Context remains that same episteme and has U.View membership only when the E.17.0 conformance test to a viewpoint episteme passes. A.6.3 supplies only an optional source-to-receiving construction. The @Context suffix is a local retrieval convention; it does not add a context object or identity field.

In the description and view forms below, admissibleUse states the use and its limits. nonAdmissibleUse?, also named groundedNonAdmissibleUse?, carries one optional explanatory guard under F.19:4’s plausible-reader test; the two names do not introduce separate fields.

StructuralDescription@Context ::= {
  descriptionId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  structureRefs: FinSet(SelectedStructureReference),
  structureClaimRelianceRefs?: FinSet(EvidenceRelationRef | EvidenceProvenanceRelationRef | MathLensUseOutputRef | StructureUseReturnConditionRef | U.EpistemeRef),
  describingEpistemeRef,
  admissibleUse,
  nonAdmissibleUse?
}

StructuralView@Context ::= {
  viewId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  structureRefs: FinSet(SelectedStructureReference),
  structuralAspectDescriptionRefs?,
  selectedRelationsOrOperations,
  hiddenOrLostStructure,
  admissibleUse,
  nonAdmissibleUse?
}

The EntityOfConcern and effective scheme identify the episteme with its claim content under C.2.1. selectedViewpointRef, when present, records that this named describing use selects viewpoint P; it does not establish conformance or U.View membership.

selectedModelUseStructureRef, when present, resolves one independently selected BoundedModelUseStructure used by the receiving assertion or calculation; it is neither episteme identity nor another viewpoint field.

When reliance is on a named claim, U.EpistemeRef resolves the C.2.1 claim-bearing episteme; a PatternID normally locates the definition, constraint, or test it uses, and a ClaimGraph is added only when that identity changes the use.

A.22:4.3a - Orientation belongs to a representation of a named structure

Use vertical, horizontal, above, below, or at the same level as structural shorthand only when the reader can recover which object’s structure is represented, which relation is shown, and how the drawing or ordering convention represents it. These words can make an explanation easier to follow. Their useful content comes from the named structure and convention.

For example, a diagram of a Method’s composition may place encompassing Methods above their constituents and draw each established methodPartOf connection upward. A diagram of result use may place a supplying Method to the left of a receiving Method. The second diagram needs to state what result is used and under what conditions; its horizontal arrow supplies no parthood claim. Rotating either diagram changes its orientation, not those relations. Conversely, two boxes at the same height need not denote peers, independent participants, objects of one kind, or simultaneous work.

Recover the relation before choosing an axis:

Represented subject and questionWhat gives the orientation meaning
A System or Method and its constituentsThe whole–part relation and its independently established participants; nesting or height alone supplies neither.
Kinds, concepts, or Methods ordered by generalityThe declared classification, inclusion, subsumption, or refinement relation and its direction. This is a different structure from composition.
Actions, result uses, or possible continuationsThe named order, dependency, guard, overlap, or return relation. Several relation kinds may require different arrow labels in one picture.
Systems, resources, or performed work in spaceTheir placement, adjacency, or spatial relation in the stated reference frame. Literal vertical and horizontal directions remain spatial claims about these participants.

A holon can participate in several structures, each with its relevant relations and constraints. A family of holons drawn as a hierarchy need not be one tree. Calling a representation a lattice requires the mathematical claim used: a specified order, the requisite meets and joins, and a justified correspondence to the represented subject. Use C.29 when a mathematical representation-choice, transfer, or reliance question remains unresolved. A branching picture or the presence of several encompassing wholes establishes none of these properties.

For a first explanation, a sentence such as “in this diagram of Method composition, upward arrows connect a constituent to its encompassing Method” is sufficient when the relations are already clear. Add a separate structure, view, or mathematical account only when the intended use needs it. C.30.ASV:4.5a develops the selection of structures for Methods; C.30.STRAT recovers an unresolved architecture label.

A.22:4.4 - Extracted and transformed structural views

Recover the extraction or transformation basis when a view of structure is obtained from a corpus, trace, model, simulation, or generated representation, through a mathematical lens or coarsening pass, or within an observer or budget boundary, and may hide distinctions.

ExtractedStructuralView@Context ::= {
  extractedViewId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  sourceCorpusOrTraceRefs,
  structureRefs: FinSet(SelectedStructureReference),
  extractionDescriptionRef,
  preservedStructure,
  lostStructure,
  validationBoundary,
  structureUseReturnCondition?,
  admissibleUse,
  nonAdmissibleUse?
}

StructureExtractionDescription@Context ::= {
  extractionDescriptionId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  sourceInputKind,
  lensOrMethodRef,
  budgetOrObserverBoundary?,
  preservedStructureKinds,
  lostStructureKinds,
  validationBoundary,
  structureUseReturnCondition?,
  admissibleUse,
  nonAdmissibleUse?
}

StructuralAspectDescription@Context ::= {
  aspectDescriptionId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  aspectKindRef,
  structureRefs: FinSet(SelectedStructureReference),
  structureClaimRelianceRefs?: FinSet(EvidenceRelationRef | EvidenceProvenanceRelationRef | MathLensUseOutputRef | StructureUseReturnConditionRef | U.EpistemeRef),
  admissibleUse,
  nonAdmissibleUse?
}

StructuralCoarseningDescription@Context ::= {
  coarseningDescriptionId,
  entityOfConcernRef,
  effectiveReferenceScheme,
  selectedViewpointRef?,
  selectedModelUseStructureRef?,
  sourceStructureRefs: FinSet(SelectedStructureReference),
  resultStructureRefs: FinSet(SelectedStructureReference),
  preservedUnder,
  brokenBy,
  lostStructure,
  structureUseReturnCondition?,
  admissibleUse,
  nonAdmissibleUse?
}

A.22:4.5 - Structure-use return

StructureUseReturnCondition states when to return to the fuller basis because an extracted, coarsened or reused account hides a distinction needed by the receiving action or judgement. Name the hidden distinction, the use that needs it, and the condition that requires returning before that use proceeds.

Do not make structure-use return mandatory for ordinary local recognition when no hidden distinction is being used for action.

A.22:4.6 - Relation to architecture

StructuralAspectDescription@Context describes one selected structural aspect under A.22. It is not an ArchitectureStructureKindRef by itself. ArchitectureStructuralView@Context is a C.30.ASV view over the architecture claim or selected architecture-relevant structures. An asserted architecture relation is an independently obtaining C.30 ArchitectureRelation between a holon and a selected structure.

A.22 is upstream of C.30. Architecture uses structure; structure does not import architecture as a parent.

C.30 uses A.22 to identify one selected architecture-relevant structure, then tests the ArchitectureRelation between that structure and one holon. C.30.ASV separately defines and tests an architecture structural view. A reference from an architecture description establishes neither the relation nor view conformance.

C.30 and its subpatterns supply the architecture-specific description, view and adequacy rules. Select the one that defines or tests the architecture claim.

A.22:4.7 - Boundary and repair table

Tempting collapseA.22 repair
The reliance relation is treated as the structure.Recover the constituents, selected obtaining relation occurrences, applied constraints, and named use frame. When a neighboring source-description, source-use, base-dependence, grounding, evidence, lens, simulation, extraction, or representation reliance claim is current, name that relation and the content that defines or tests it separately.
The diagram, graph, table, dashboard, or publication form is the structure.Recover the description or view and its publication occurrence, form, or carrier when relevant. If the account claims a source-description, base-dependence, grounding, evidence, lens, simulation, extraction, or representation relation, identify and test that relation separately.
A transformation-flow graph expression is the structure in every sense.Use E.18 for one selected TFS and its internal paths, crossings, and valuations; use E.18.NET for a selected network of independently identified TFS members and cross-member relations; use E.18.2 for the graph expression and C.29 only when a mathematical representation-choice, transfer, or reliance question remains unresolved. A.22 supplies only the selected-structure identity, and C.30.TFS-REL defines and tests the architecture-to-transformation-flow relation claim.
A mathematical lens output is the structure.Use C.29 for lens-use result and admissibility, and cite MathLensUseOutputRef only through C.29 lens-use result, preserved structure, lost structure, and stop-condition discipline.
A structure is cited as sufficient basis for evidence reliance, assurance, safety, causality, or gate passage.Use A.10 for claim-bound evidence reliance, G.6 when a citable evidence-provenance path is needed, B.3 for a named assurance claim, the safety pattern for safety, C.28 for causal use, A.20 for internal-constraint validity, and A.21 for a gate decision.
A structure is a decision or work record.Use C.11 or the project-side decision pattern for the decision, A.15 for the work-family object, and C.2.1 for an episteme describing it. A.20 or A.21 applies only when an internal-constraint result or gate decision is at issue.
Architecture is treated as identical to a selected structure.Use C.30 to test the ArchitectureRelation between the holon and selected structure. Recover the architecture claim and any description or view separately.
Function, module, interface, platform, layer, stack, block, expert, cache, router, or gate becomes a root kind by appearing in structure prose.Use C.30.STRAT for an ambiguous source label, then the definition or test required by the recovered claim: A.6.F for function, A.6.M for a module-interface relation, A.6.0 for a signature, A.6.5 for relation slots, A.6.B for boundary norms, A.6.C for contract unpacking, A.6.P:4.11a for service or access wording, E.18 for transformation-flow structure, or C.30.ASV for an architecture structural view. Apply any other pattern only for the claim it defines or tests.

A.22:4.8 - Worked slices

Maintenance-isolation structure selection. In this constructed case, a planner chooses which relations matter for planning pump-skid isolation. Under the project’s independently tested installation predicates, Motor_12 drives Pump_37, Bus_7 supplies Motor_12, and Valve_In_4 and Valve_Out_4 lie on the inlet and outlet material paths of Pump_37. Assume these are the complete live energy and material paths for this illustration.

named selection use: choose isolation points before Pump_37 maintenance
constituents: independently identified Pump_37, Motor_12, Valve_In_4, Valve_Out_4, and Bus_7
selected obtaining relations: the established drive, supply, inlet-path, and outlet-path occurrences with the participants named above
applied constraints: isolate every live energy and material path to Pump_37; retain only relations relevant to this isolation use
selecting system: MaintenancePlanner_A
selection method: IsolationStructureSelectionMethod
selected structure: Pump37_MaintenanceIsolationStructure
admissible action: prepare the isolation sequence from the selected paths
stop: reopen selection when a constituent, selected occurrence, or isolation constraint changes

Pump37_MaintenanceIsolationStructure is identified by the constituents, selected obtaining occurrences, applied isolation constraints, and maintenance-isolation use frame. The selection method and any C.2.1 episteme describing the judgment remain separate.

The selected organization directs planning to Bus_7 and both material-path valves; it establishes no completed isolation. If the completeness assumption fails, return to path identification before planning from this selection.

A C.29 graph may represent the same organization, while the predicates of the selected relation occurrences remain its obtaining basis. A visually identical graph with an unestablished connection remains a representation candidate.

Architecture kernel slice. A team says, “the architecture is the graph.” Recover the selected structure and the graph’s reliance relation:

declaredStructureSubstrateRef: TransformationFlowStructureRef under E.18, with mathematical graph description under E.18.2 when that expression is the current claim
candidate structure: selected transformation-flow structure
structure-claim reliance relation: selected relation record named by value(
  sourceDescriptionOrPatternApplicationRef = SourceViewRef, structure or crossing record selected under E.18, or E.18.2 mathematical graph description,
  relationContribution = E.18 selected-structure or crossing definition | A.6.6 base-dependence test | independently established support relation recovered through A.10 provenance and bounded-use account | C.29 mathematical-lens result, chosen for the claim being made,
  relationKind = source-description | base-dependence | evidence | lens, selected for this reliance,
  validationBoundary = graph-path currentness boundary, slice currentness boundary, or crossing currentness boundary
)
next FPF pattern application: C.30.TFS-REL when this selected structure is used in an architecture-to-transformation-flow relation
stop or return condition: stop at the selected reliance relation's result; for a Work, evidence, gate, or decision claim, apply its test in A.22:4.7
non-admissible use: the graph as the whole architecture

The practitioner can now use the graph through the selected source-description, base-dependence, evidence, or lens relation and route the architecture claim to C.30.TFS-REL.

Extracted code structure slice. A code-agent relation graph or probe JSON reports imports, calls, registry wiring and data-flow links. Recover the source codebase or publication, extraction method, preserved and lost structure, validation boundary and structure-use return condition. That establishes the declared extraction result only. For an A.6.3 epistemic-viewing claim, identify source episteme X and receiving episteme Y, their same EntityOfConcern, and the projected or re-expressed ClaimGraph and ReferenceScheme. Qualify Y as a U.View only when the applicable E.17.0 viewpoint conformance independently obtains. A claim about the codebase architecture, internal agent belief, assurance or release readiness still needs its evidence and governing predicate.

ExtractedStructuralView@Context:
  sourceCorpusOrTraceRefs: repo snapshot, probe outputs, traces
  preservedStructure: selected typed relation families
  lostStructure: unexplored regions, dynamic calls, hidden generated code, ambiguous relation kinds
  validationBoundary: probe coverage and source codebase or publication edition
  structureUseReturnCondition: when an architecture decision, assurance use, or repair depends on a relation not observed by the extraction

A.22:5 - Archetypal Grounding

Tell-Show-Show rowGrounding
TellA practitioner sees an arrangement that matters but does not yet know whether it is a diagram, a model, a graph, an architecture claim, a source description, base-dependence relation, evidence relation, lens relation, or decision. A.22 asks first: which constituents and obtaining relations are selected, under which applied constraints and named use frame, and what loss changes the next action?
Show: U.SystemIn a plant, vehicle, software system, or neural-network model, the selected structure may be transformation-flow, control, module-interface structure, placement, information, scale, or declared logical structure. The structure record does not become the system and does not prove that the system is safe, maintainable, or ready.
Show: U.EpistemeA paper, model, generated relation graph, dashboard, architecture note, or mathematical-lens output may describe or present a description of selected structure. A selected-structure claim may rely on that description through a source-description relation or an A.6.6 base-dependence relation. The episteme, view, and publication remain separate from the structure and from each relied-on relation; name that relation and any validation boundary required by its definition or intended use; add a structure-use return condition when §4.5 requires it.

A.22:6 - Bias-Annotation

Bias riskMitigation
Architecture biasDo not make architecture the parent of all structure. A.22 stays upstream; C.30 carries grounded architecture and selected-structure adequacy.
Mathematical-formalism biasA mathematical lens can expose preserved structure and lost structure, but C.29 still defines the lens-use result, admissibility, and stop condition.
Diagram biasA useful diagram or generated relation graph is attractive enough to be mistaken for the structure. Description, specification-use, and publication boundaries stay explicit.
Review-only biasA check returns the supported recognition, conclusion or action needed for the receiving use. Repair a defect when the check exposes one.

Use the checklist to inspect the selected structure claim and only the neighboring claims made.

A.22:7 - Conformance Checklist

IDRequirementFailed-check repair
CC-A22-1 Base identity.The selected U.Structure is recoverable from independently identified constituents, selected obtaining relation occurrences, constraints as applied, and one named selection-use frame.Recover the missing discriminator. If a constituent lacks its defining identity content or a relation lacks its predicate or occurrence rule, stop at that blocker rather than naming a structure from a graph or record.
CC-A22-1a Independent grounding.Every constituent and selected relation occurrence keeps its identity; a collection, constraint episteme, graph, table, description, view, or publication neither creates them nor makes a relation obtain.Apply the constituent and relation patterns first; treat the visible artifact as a C.29 representation or C.2.1 episteme only when that is what is present.
CC-A22-1b Selection work and result separation.When dated selection Work is asserted, establish the complete A.13 core and A.15.1 admission in §4.1 and the method-enactment relation. Establish any direct participation or A.6.1 binding relation needed by the receiving claim separately. Any durable result is a separate C.2.1 episteme, and any accountable choice uses its decision predicate and test.Name the acting system, method and work separately from structure identity; identify any binding, result or decision needed by the current claim under its grounds.
CC-A22-1c Reidentification.A changed designator, method, work, result episteme, graph, description, or publication leaves the structure unchanged when all four identity discriminators remain unchanged; a changed discriminator reopens identity.Compare the four discriminators and apply each selected relation occurrence’s identity rule before reapplying A.22.
CC-A22-1d Transformation-flow network profile.An E.18.NET value applies all four A.22 discriminators to TFS or nested-network constituents, cross-member relation occurrences satisfying their predicates, the E.18.NET constraints as applied, and one named network-use frame. A constituent row supplies no generic membership occurrence, and A.22 carries no duplicate network fields.Recover any missing member, relation predicate, or identity rule, then apply E.18.NET. If a separate membership relation is needed, state its participants and apply its predicate rather than inferring it from the constituent list or graph.
CC-A22-2 Non-agentive structure.Any claimed action has a recoverable capable actor. Use F.19:4 to test literal or metonymic action wording; apply the relevant proof, decision, warrant, or adaptation predicate when that claim is current.Recover the actor and action; identify System and Work only when the claim needs their identity. For another claim, use the pattern that defines or tests its result.
CC-A22-3 Structure-claim reliance relation boundary.When source-description, source-use, base-dependence, grounding, evidence, lens, simulation, extraction, or representation reliance is claimed, name the relation and the definition or test used for it.Add the relation kind, definition or test, admissible use, and any validation boundary or stop condition required by that relation or receiving use. Add a structure-use return condition when §4.5 requires it. Test any optional non-admissible use through F.19:4. If no admissible reliance is established, mark the reliance phrase as carrying no admissible reliance.
CC-A22-4 Description and view separation.A structural description, structural view, extracted view, diagram, table, graph, dashboard, or publication face is not treated as the structure itself.Recover any description or view and its publication form or occurrence; resolve any source-description relation or A.6.6 base declaration separately. Name the selected structure separately only if selected organization is being claimed.
CC-A22-5 Describing-use separation.Description epistemes keep claim content, EntityOfConcern, and effective scheme under C.2.1. A named describing use may separately select one viewpoint, and a receiving calculation or assertion may separately select one independently identified BoundedModelUseStructure. E.17.0 alone supplies the U.View conformance test; A.6.3 supplies optional viewing construction.Remove any compound context field; state only the episteme values and the optional use selections that the current action needs.
CC-A22-6 Structure-use return.StructureUseReturnCondition is present when hidden selected-structure, source-basis, source-description, evidence, lens, simulation, extraction, or representation distinctions are used for action, assurance, causal use, legal or regulatory review, comparison, or decision reopening.Add one structure-use return condition or narrow the record’s admissible use so the hidden distinction is not relied on.
CC-A22-7 Non-structure claim kind.Evidence, assurance, gate, release, causal, dynamics, measurement, work, decision, publication, bridge, and mathematical-lens claims use the patterns that define or test those claims.The check passes when that contribution and the claim kind are named, while the A.22 record remains limited to selected-structure use.
CC-A22-8 Architecture pattern application.Architecture claims use C.30 and ArchitectureRelation; A.22 does not treat architecture as a root kind or define C.30-specific records.Apply C.30 or a C.30 subpattern and keep A.22 only as the selected-structure EntityOfConcern and structure-claim reliance relation.
CC-A22-9 Plain and Tech recovery.Plain structure phrases may remain, but if they carry ontological, evidence, causal, assurance, bridge, gate, work, decision, or admissibility claim, the relevant Tech fields and FPF pattern applications are recoverable.Add the missing Tech fields or demote the Plain phrase to ordinary recognition wording.
CC-A22-10 Useful action.The repair preserves the supported recognition, understanding, decision or action the practitioner needs.Restore the information or action required by that use. If the wording cannot support it, use E.10:17 to name any remaining use as a cue or quotation, identify a blocked transfer, or say that the rewrite is unfinished.
CC-A22-11 CGUS qualification and case use.A formal CGUS qualification identifies one A.22 structure by the four discriminators; its local locus bindings, selected relations, and applied constraints define at least two potential continuations. The present-case result, any description, and every stronger neighboring claim are judged separately.Use A.22.CGUS’s ordinary branch to clarify available alternatives and their conditions. Use formal qualification when the named use depends on structure identity or CGUS membership. If the structure qualifies but case facts are missing, return unknown for the affected alternatives. If only a display is present, keep it as an explanation; send description adequacy and stronger claims to their patterns.

A.22:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Structure-as-documentA diagram, table, dashboard, relation graph, or prose section is called the structure.Recover publication, publication-form, description, or view relation; name the structure separately only when selected organization is being claimed.
Reliance-interpretation-as-structureA trace used as source basis, benchmark, lens output, model, or simulation is treated as the structure.Name the A.6.6, source-description, evidence, or lens relation and its definition or test; state the validation and stop conditions required by that relation or intended use, and add a structure-use return condition when §4.5 requires it. Use F.19:4 for any optional explanatory guard.
Loss-free extractionAn extracted or coarsened account hides a loss that changes the receiving use.State what is preserved and lost, the supported use and any required validation boundary. Add a structure-use return condition under §4.5 or narrow the use so the hidden distinction is not relied on.
Architecture root-kind reboundStructure work reintroduces U.Architecture or treats architecture as parallel to structure.Use ArchitectureRelation and C.30; keep A.22 as the upstream selected-structure EntityOfConcern.
Lens ontology importA mathematical lens output becomes the imported ontology.Use C.29 for the lens, cite it through C.29 lens-use result, preserved structure, lost structure, and stop-condition discipline.
Sterile precision rewriteThe text removes overread but no longer tells the practitioner what to do.Restore the information and any action still needed for the practitioner’s receiving question.

A.22:9 - Consequences

BenefitCost or trade-off
FPF gains a reusable selected-structure EntityOfConcern without minting architecture, module, interface, platform, or graph as root kinds.A conforming use recovers the four structure-identity discriminators, including the question, admissible action and stop or return condition in the named use frame. Extraction, coarsening and reliance claims also retain the preservation, loss, validation and structure-use return information required by their receiving use.
Structural views become usable without confusing the view, publication form, publication, source-use relation, grounding relation, and selected structure EntityOfConcern.Existing loose prose that says “the structure is the diagram” needs repair.
Structure claims can rely on C.29 mathematical-lens results or E.18 transformation-flow structures through separately established relations, without treating them as the general structure ontology.FPF pattern applications are named when evidence, assurance, causal-use, gate, work, or decision claims are being made.
Architecture work can start from selected structure through C.30 instead of forcing architecture to be either a document or a module diagram.Architecture-specific conformance stays outside A.22, so practitioners can require one extra C.30 application when the architecture claim or durable architecture-description use is being made.

A.22:10 - Rationale

FPF needs one general selected-structure kind because many useful claims depend on organization before they depend on an architecture, mathematical, measurement, or publication pattern. The selected structure is dependent and non-agentive. Claims about it are carried by separate epistemes and views: it can be described, sourced, compared, coarsened, extracted, or used by architecture.

A practitioner can state the four identity values and stop when they answer the receiving question. StructureQuestionCard@Project is one optional aid. Heavier describing-use viewpoint selection, independently selected model-use structure, A.6.6 base-dependence, extraction, lens, evidence, and structure-use return records are used only when the next use would otherwise hide loss, source-basis dependence, or a non-structure claim kind.

C.30 defines the ArchitectureRelation between one holon and one selected A.22 structure. An architecture claim states whether that relation obtains, or describes candidate or expected structure. Architecture descriptions and views are epistemes; publication makes them available. A.22 supplies the selected structure and its identity basis.

A.22:11 - SoTA-Echoing

Practice or source anchorFPF adoptionAction consequenceBoundary
FPF C.2.1 and E.10.D2 description discipline, E.17.0 view membership, A.6.3 construction, and E.17/E.24.PUB publication disciplineFPF separates EntityOfConcern, effective reference scheme, viewpoint, grounding holon, view, publication, rendering, and carrier.A.22 structural descriptions and views reuse those relations rather than inventing a local display ontology or mandatory context field.A description or view does not become the selected structure and supplies no evidence, assurance, gate, or decision authority by form.
Evans, Context Mapping with an AI-based Component, 2026The cited DDD case motivates distinguishing model-use boundaries and their relationships from the Context Map used to inspect them; the FPF identities are an adaptation.A.22 admits the BoundedModelUseStructure membership condition and the conditional CrossContextRelationStructure membership condition; the latter has no positive member until independently defined crossing occurrences and all four base discriminators exist. A mapping Method and any dated Work use their admission grounds; the product is a C.2.1 episteme concerning a proposed organization until a structure can be designated; it becomes U.View only under E.17.0 conformance.The DDD terms do not turn a system part, method, proposal, structure, view, and diagram into one object.
C.29 mathematical-lens disciplineAdopt preserved structure, lost structure, lens-use admissibility, and stop-condition discipline when a mathematical lens is used for a structure claim.Cite C.29 output through C.29 lens-use result, preserved structure, lost structure, stop condition, and structure-use return discipline.The lens output remains separate from the selected structure. Its evidential use, any assurance or causal-use claim, and any decision need their grounds.
arXiv:2603.00601 code-space architecture relation-graph work and related code-probing practiceAdapt partial-observability, typed-relation, uncertainty, and structure-use return pressure for extracted structural views.State the extraction basis, its validation boundary and, where needed, whether a relation is observed, inferred, or unknown. Add a structure-use return condition when §4.5 requires it.Do not mint U.CodeSpace. Probe and benchmark outputs may contribute evidence under an established evidence-use relation; their presence alone does not establish structure adequacy, assurance or release readiness.
Coarsening, compression, and RG-adjacent traditionsAdopt the need to say what structure is preserved and what is lost.Use StructuralCoarseningDescription@Context when the receiving use needs that account; add StructureUseReturnCondition when §4.5 requires it.For RG, epiplexity, structural information, or equivalence reasoning, use C.29, C.16, or the cited pattern that defines or tests the claim.
GonzoML neural-network architecture discussions as practitioner-language intakeAdapt block replacement, dataflow change, memory placement, cache placement, path-selection, pruning, distillation, and architecture-search wording as general architecture-operation recognition material.Keep the source’s local terms when their meaning is clear. Use C.30.STRAT when a label leaves the claimed object or relation unresolved. Recover the selected or proposed organization, and any further relation, only when the current claim needs it.Neural-network labels, benchmark results, ablations, or pruning masks do not become structure ontology, architecture decisions, evidence sufficiency, gate passage, assurance, or architecture adequacy by themselves.

How can an orientation cue preserve a structural claim across different diagrams? §4.3a uses the named subject, relation and representation convention. The default is to read height, nesting or direction as one common relation across holons, kinds and activities. That reading fails when the same Method is shown inside one composition and beside a Method using its result. The FPF construction retains each claim when the drawing rotates or changes layout, at the cost of naming the relation once. OMG Essence 2.0 beta 2, Figure 7.1 is a positive comparator: its vertically arranged boxes already have differently labelled relations for composition, description and definition. Adopt that relation-sensitive reading; the figure does not establish FPF parthood or a universal holon lattice.

A.22:12 - Relations

Builds on: A.1, C.13, C.2.1, A.6.REL, A.6.0, A.6.5, A.3.1, A.6.1, A.15.1, A.6.P, A.7, A.6.2, A.6.3, A.14, C.16, C.29, E.10.D2, E.10, C.2.P, E.17.0, E.17.1, E.24, E.24.PUB, and F.18.

Coordinates with: A.1.1, A.2.6, A.22.CGUS, C.30.P, C.30.STRAT, C.30, C.30.ASV, C.30.TFS-REL, C.30.LCA, C.30.ILC, A.6.F, E.18, E.18.NET, E.18.3, A.10, G.6, B.3, A.20, A.21, C.28, A.15, C.11, C.16, C.25, G.5, C.33, C.34, and C.35 when architecture-specific structure-capture, preservation, or discovery adequacy claim kinds are being made.

Architecture-specific adequacy: C.33, C.34, and C.35 define or test architecture-specific capture, preservation, and discovery adequacy over selected structures. A.22 keeps the general selected-structure portion; it does not decide architecture use, candidate admission, measurement, evidence, assurance, or decision authority for those adequacy claims.

Does not replace: C.30.P or C.30.STRAT wording-use precision restoration, C.30 for grounded architecture adequacy and conditional architecture-description use, C.29 for mathematical-lens use, C.16 for measurement and characterization, C.28 for causal-use relation, B.3 for assurance, A.10 for claim-bound evidence reliance, G.6 for citable evidence-provenance paths, A.20 for internal-constraint validity, A.21 for gate decisions, the subject pattern for release claims, A.15 for work-family objects, C.11 for decisions, E.17 for a source-backed reader face, or E.24.PUB for publication occurrence, form, carrier, audience, bounded use, and availability.

Use F.19 for ordinary precise-plain-language repair and its plausible-reader test for optional guards; unresolved structure or architecture wording follows C.30.P or C.30.STRAT.

A.22:End

A.22.CGUS - Which Continuations Are Available? — Constraint-Governed Unfolding Structure (CGUS)

Type: A.22 specialization of U.Structure Status: Stable Normativity: Normative unless marked informative

A.22.CGUS:0 - Use This When

Use this pattern when a diagram or explanation shows several possible next actions, but readers may mistake one displayed path for the required work sequence. Start with one ordinary question:

Which alternatives are available now, and what condition blocks each one?

Name the decision or question, the visible alternatives, the condition for each alternative, and the facts available now. If a missing fact or rule could change the answer, mark that alternative unknown. An established blocking condition may already settle it as unavailable. Stop when this answers the practical question. A useful explanation need not first become a formal record or an admitted structure.

Open the formal branch when a named use needs the identity and qualification of the unfolding organization as a CGUS. A ConstraintGovernedUnfoldingStructure (CGUS) is one A.22 U.Structure whose locally named loci, constituents, obtaining relations, and constraints define at least two potential continuations across the cases allowed by those constraints. A separate result says which alternatives are enabled, disabled, unknown, or error for one case and time window.

Do not use CGUS merely because a card, graph, table, narrative, prompt path, or README line looks route-shaped. A single recommendation or displayed sequence is not enough. The structure may branch, join, cycle through subject relations, remain partially ordered, or leave several alternatives live at once. A result with zero or one enabled alternative can still concern that same branching structure.

What changes in practice. Practitioners correct the visible alternatives and their conditions before completing formal fields. They keep potential structure separate from the result for the present case, and they mark an alternative unknown when an unresolved fact or rule prevents deciding it. Display order alone neither prescribes nor performs Work.

A.22.CGUS:1 - Problem Frame

FPF often needs to explain how several identified things and relations constrain what may follow without turning that explanation into a workflow. The shared object is one A.22 structure. CGUS adds local loci and a membership test for potential branching; a continuation judgement then evaluates one case.

Descriptions, publication forms, evidence, assurance, authorization, work plans, performed Work, architecture claims, and mathematical models can be used alongside that structure. They remain separate objects and claims under the patterns that define or test them.

A.22.CGUS:2 - Problem

A route-shaped explanation can hide the relations and constraints that make an alternative available. Readers then follow the displayed order as if it were a required procedure, or they treat a condition label as proof that the condition is true now.

The opposite repair is also harmful: authors replace the simple decision question with a large admission, replay, publication, and assurance package. The formal package becomes harder to use than the misleading card it was meant to correct.

A.22.CGUS:3 - Forces

ForceTension
Useful explanation vs workflow overreadA visible path helps a reader, but Work may be nonlinear, interrupted, iterative, or arranged by another Method or plan.
Potential structure vs present resultThe structure can retain several possible branches while the present case enables none, one, or several.
Plain entry vs formal replayAn ordinary correction should be cheap; qualification and replay still need enough identity and relation detail to be checked later.
Description vs described structureA card, graph, table, or narrative can describe a structure without creating it.
Reuse vs copied mini-patternsCGUS needs exits to relation, transformation-flow, work, publication, and assurance patterns without copying their architectures.

A.22.CGUS:4 - Solution

A.22.CGUS:4.1 - Ordinary branch

Write the smallest useful answer in domain language:

  1. name the decision or question;
  2. list the alternatives;
  3. state the condition for each alternative;
  4. state the facts known for this case;
  5. mark each alternative available, blocked, or unknown under its condition, and name any gap that prevents deciding it. If the evaluation itself failed, state that error rather than treating it as a domain fact.

For example, a design review has two alternatives: accept the design or repair it. Acceptance needs both checks to pass. Repair needs at least one failed check and a repair proposal that concerns this design.

AlternativePresent factsResult shown on the card
Accept the designThermal check failed; service check passed.blocked — thermal check failed
Repair the designA check failed and a repair proposal exists, but the proposal-to-design relation has not been established.unknown — proposal target not established

That corrected card is already useful. It keeps both potential alternatives visible and refuses to invent the missing relation. Retain the rules, facts, and result when the ordinary answer must be reconsidered or compared later. Continue into formal qualification only when a named use depends on the organization’s CGUS identity or membership.

When retaining or handing over this card separately, include the two rules above or a usable return to them so the recipient can reconsider availability after the facts change.

A.22.CGUS:4.1.1 - Conditions through constituent and encompassing work

When a continuation is a way of performing work, recover the constituent–whole relations in the relevant Method and Work structures that can change availability. Ask what constituent actions must be performable and what encompassing work is being done through them. B.1.5.EW supplies that recovery; knowing a Method’s description does not supply the capability or resources to perform it.

Distinguish conditions needed at entry, conditions that must remain satisfied during combined performance, and the result required by the encompassing use. In particular:

  • a constituent may be individually performable but fail in the needed coordination;
  • adequate local resources may be insufficient when constituents share them;
  • a constituent result may satisfy its own postcondition while leaving the whole’s result unresolved.

For each relevant condition, state what it concerns and how it affects this continuation. Reuse an understood connection or adequate existing basis. A missing condition blocks or leaves unknown the dependent alternative; it need not block an independent way to learn, obtain support or change the arrangement. Capability belongs to its performer and conditions under A.2.2; prospective resources and support remain prospective until available.

In the formal branch, express these dependencies with the existing constituents, selected relations, applied constraints and continuation judgements. A temporal edge alone cannot express that one action constitutes part of another ongoing work. Nor does a nested flow position establish Method or Work parthood. A diagram may show the relations together when their meanings remain recoverable.

A constituent’s postcondition supports the encompassing conclusion only through the relevant composition and result-use conditions. An expected postcondition is not an observed result. If the displayed account omits conditions needed to perform the whole, state the narrower question it answers. A constituent hierarchy without potential alternatives does not require CGUS qualification.

A.22.CGUS:4.2 - Formal qualification branch

Use the four A.22 discriminators to identify one U.Structure:

  • its constituent references;
  • the obtaining relation occurrences it selects;
  • the applied constraint claims;
  • the named selection-use frame: the question, admissible action, and stop or return condition. Any optional explanatory overread follows F.19:4 and remains outside the identity basis.

CGUS membership adds locally declared loci and bindings that expose how those constituents matter to the unfolding question. The selected relations and constraints must define at least two potential continuation candidates across allowed cases. The current continuation result, a description, or a publication field adds no structure-identity discriminator.

selectedCGUSRef: one A.22 U.Structure
A22IdentityBasis:
  selectedConstituentRefs[]
  selectedObtainingRelationOccurrenceRefs[]
  appliedConstraintClaimRefs[]
  namedSelectionUseFrame:
    questionOrAction: selection question
    admissibleAction
    stopOrReturnCondition
forbiddenOverread?: optional explanation outside A22IdentityBasis
constraintGovernedProfileBasis:
  locusBindingRows[]:
    locusRef: <selectedCGUSRef, locusId>
    locusMeaning: why this constituent matters to this question
    selectedConstituentRef
  potentialContinuationRows[2..*]:
    continuationCandidateRef
    constrainingRelationOccurrenceRefs[]
    appliedConstraintClaimRefs[]

forbiddenOverread? and groundedForbiddenOverread? name the same optional explanation. Use F.19:4’s plausible-reader test to decide whether it is useful here.

A CGUS locus belongs to this structure, not to a reusable relation declaration:

CGUSLocusRef := <selectedCGUSRef, locusId>
CGUSLocusBinding := <selectedCGUSRef, locusId, locusMeaning, selectedConstituentRef>

The constituent must already belong to the A.22 identity basis. A locus binding neither changes that constituent’s kind nor creates a relation. Do not use an A.6.5 SlotSpec as a free-standing structure position.

When replay must identify one participant in a relation occurrence, retain the relation definition, the occurrence, the participant order, and the participant binding:

RelationParticipantLocator := <relationDefinitionRef, relationOccurrenceRef, participantOrder, participantRef, relationSignatureRef?, slotSpecRef?>

Add a RelationSignature and its declaration-local SlotSpec together only when an existing reusable declaration is needed for replay. Neither declaration value substitutes for the obtaining occurrence. The CGUS has no ambient context field.

Judge each continuation separately. An immediate local use may keep the following values in the explanation; persistence or replay may place them in an ordinary C.2.1 result episteme.

ContinuationJudgementResult:
  selectedCGUSRef
  continuationCandidateRef
  basisRows[]:
    basisKind: conditionEvaluation | obtainingRelation
    conditionEvaluation?:
      conditionPredicateOrTestRef
      applicabilityResult
      caseInputRefs[]
      currentFactOrEvidenceRefs[]
      requiredPolarity
      observedOutcome: satisfied | notSatisfied | unknown | error
    obtainingRelation?:
      relationDefinitionRef
      relationOccurrenceRef
      participantRefsInPredicateOrder[]
      currentFactOrEvidenceRefs[]
    dependentSelectedRelationOccurrenceRefs[]
  qualificationWindow
  result: enabled | disabled | unknown | error
  reason

CurrentContinuationSetResult:
  selectedCGUSRef
  caseInputRefs[]
  qualificationWindow
  judgementResultRefs[]
  enabledContinuationCandidateRefs[]
  disabledContinuationCandidateRefs[]
  unknownContinuationCandidateRefs[]
  errorContinuationCandidateRefs[]
  stopOrNextAction
  recheckConditions[]

A claim reference identifies the claim being applied; it does not show that the test applies or that its condition is satisfied. An obtaining relation is not a condition claim. Keep these two basis branches distinct and derive the case result only from completed judgements. Apply the candidate’s condition logic: for example, one false required conjunct can establish disabled despite another unknown conjunct. Retain that unknown basis value; it is not thereby satisfied. An evaluation failure yields error under the applicable test, not an invented fact about the candidate.

The membership test concerns potential topology. Changed facts, evidence, test outcomes, or time windows normally change a judgement and the current set, not the structure. Reidentify the A.22 structure when a constituent, selected obtaining relation occurrence, applied constraint, or named use frame changes. Reapply CGUS membership when a locus binding or potential-continuation row changes.

A.22.CGUS:4.3 - Four separate decisions

DecisionPassing basisLower result
A.22 identity and CGUS membershipThe four A.22 discriminators identify one structure; its local loci, relations, and constraints define at least two potential continuations across allowed cases.Name the missing discriminator, binding, relation, constraint, or candidate. Keep the artifact as an explanation.
Continuation result for this caseEach candidate retains its condition-evaluation and obtaining-relation basis rows as applicable. A condition-evaluation row keeps the test, applicability, inputs, required polarity, and observed outcome; an obtaining-relation row keeps the definition, occurrence, and ordered participants. Keep the relevant facts or evidence, time window, and an enabled, disabled, unknown, or error result.Mark the affected candidate unknown when the gap prevents deciding its condition; retain an independently established disabled result. Do not revoke an independently established structure.
Description or demonstrative-slice adequacyThe description says what it shows and omits for its declared use. Use C.33 only when a carrier’s loss affects a declared architecture use within C.33’s scope.Narrow or correct the description. Missing publication or loss material does not deny the structure.
A stronger neighboring claimThe method, Work, evidence, assurance, gate, architecture, publication, currentness, or mathematical claim passes its own definition or test.Stop only that stronger use and name its missing rule or basis.

Potential branches and joins remain part of the structure even when the present case enables one or none. A linear teaching slice neither removes the other topology nor fixes the order of performed Work.

A.22.CGUS:4.4 - Explanations, descriptions, and the non-workflow boundary

An ordinary explanation keeps the subject designated by its claims. When its episteme identity matters, recover that independently identified EntityOfConcern under C.2.1. It may already be an A.22 structure whose CGUS membership is unresolved. An assertion of CGUS membership still requires its qualification basis.

After qualification, a whole-structure description may describe loci, bindings, relations, constraints, potential branches, case results, and relevant omissions. A separate demonstrative slice may show one traversal for a declared teaching or comparison use. That slice is a C.2.1 episteme: its claim content, the qualified CGUS as EntityOfConcern, and its effective reference scheme jointly recover its identity. DemonstrativeUnfoldingSlice@Context is readable lineage for this possibility, not a U.Kind or a slice by itself. The slice neither creates nor reidentifies the structure. Use C.33 only when hidden or lost structure in its carrier matters to a declared architecture use within C.33’s scope.

Where a slice shows one selected pattern use, it may recall the difficulty through the pattern’s Problem frame or Problem, or recall the way of addressing it through the Solution. To show that same use in either form, preserve the selected pattern, working subject and question or proposed use, current conditions, expected result, stop or continuation, and relevant locus bindings. Changing between those formulations changes only the description when the selected pattern use and the qualified structure remain the same. A.22 structure identity still depends on its constituents, selected obtaining relations, applied constraints and named selection-use frame; CGUS membership additionally depends on its locus bindings and at least two potential continuations. Question or action labels establish neither.

Displayed words such as move, next, and path remain ordinary language unless a stronger claim requires another kind. A proposed action, a plan item, a U.WorkPlan, dated U.Work, and an actual U.Transformation are different values. Use E.10.MOVE, A.15, and A.3 only when that distinction changes the claim; a display performs and authorizes nothing.

For a transformation-flow use, apply E.18.3. It owns the choice among one TFS, one parent-relative SubflowRef, or an E.18.NET network and the corresponding position and demonstration locators. CGUS keeps only its local locus bindings and potential topology; it does not copy the network’s members, positions, valuations, Work, transformations, or tags.

Cite another pattern only when its content supplies a needed definition, constraint, test, method, evidence rule, or assurance rule. For example, use C.30 for an architecture claim and C.32 for architecture-candidate synthesis, E.23 for repeated quality improvement under a declared evaluation, G.11 for source currentness, C.29 for a mathematical-lens claim, A.10 when the source-to-use account is implicit or must remain replayable, or B.3 for a named assurance claim.

If a durable name or a relation between local senses is the question, use F.17, F.18, or F.9 after the value has been recovered. Do not copy their naming or Bridge procedures into this pattern. Entry cards and publication faces remain under E.11 and E.17.

A.22.CGUS:4.5 - Replay and change localization

Replay structure identity from the four A.22 discriminators. Replay CGUS membership from the local locus bindings and potential topology. Replay the case result from each candidate’s basis rows, retaining the values required by each applicable condition-evaluation or obtaining-relation branch in 4.2, the relevant case inputs and facts or evidence, dependent occurrences, time window, continuation result, and reason.

Localize change before reopening wider work. A changed constituent, selected occurrence, constraint, or use frame can reidentify the A.22 structure. A changed locus binding or potential-continuation row reopens CGUS membership. A changed fact, evidence item, test result, or time window normally reopens only the affected judgement and current set. A changed omission reopens the affected description use. A changed neighboring claim stays with the pattern that defines or tests it.

A.22.CGUS:5 - Complete Worked Case

Return to the design review from 4.1. The team now needs to determine whether reviews across editions use the same qualified unfolding structure or a different one. Recover the formal basis below for that comparison.

selectedCGUSRef: DesignReviewAlternatives@DR-27
A22IdentityBasis:
  selectedConstituentRefs[]:
    DesignCandidate-A
    RepairProposal-A
    AcceptCandidate-Continuation
    RepairCandidate-Continuation
  selectedObtainingRelationOccurrenceRefs[]:
    RepairProposalTargetsCandidate@DR-27
  relationOccurrenceRecoveryRows[]:
    - relationOccurrenceRef: RepairProposalTargetsCandidate@DR-27
      predicateDefinitionRef: RepairProposalTargetsDesignCandidatePredicate
      participantRefsInPredicateOrder[]: [RepairProposal-A, DesignCandidate-A]
  appliedConstraintClaimRefs[]:
    AcceptIfBothChecksSatisfied
    RepairIfAnyCheckViolatedAndProposalTargetsCandidate
  namedSelectionUseFrame:
    questionOrAction: which review continuations satisfy the two-check rule for DesignCandidate-A?
    admissibleAction: show enabled, disabled, unknown or error results for the current case
    stopOrReturnCondition: recheck a case when its result inputs or window change; reidentify the structure when its selected basis changes
forbiddenOverread?: displayed order as performed Work, or an available branch as authorization
constraintGovernedProfileBasis:
  locusBindingRows[]:
    - <DesignReviewAlternatives@DR-27, candidate, design under review, DesignCandidate-A>
    - <DesignReviewAlternatives@DR-27, repair-proposal, proposed repair, RepairProposal-A>
    - <DesignReviewAlternatives@DR-27, accept, accept continuation, AcceptCandidate-Continuation>
    - <DesignReviewAlternatives@DR-27, repair, repair continuation, RepairCandidate-Continuation>
  potentialContinuationRows[]:
    - AcceptCandidate-Continuation, constrained by AcceptIfBothChecksSatisfied
    - RepairCandidate-Continuation, constrained by RepairIfAnyCheckViolatedAndProposalTargetsCandidate
caseBasis:
  checkResultRefs: [ThermalCheckResult-A, ServiceCheckResult-A]
  resultAboutCandidateOccurrences:
    - <ThermalCheckAboutCandidate@DR-27, CheckResultAboutDesignCandidatePredicate, [ThermalCheckResult-A, DesignCandidate-A]>
    - <ServiceCheckAboutCandidate@DR-27, CheckResultAboutDesignCandidatePredicate, [ServiceCheckResult-A, DesignCandidate-A]>
continuationJudgements[]:
  - candidate: AcceptCandidate-Continuation
    basisKind: conditionEvaluation
    predicateOrTest: AcceptIfBothChecksSatisfied
    applicability: both named results concern DesignCandidate-A
    caseInputs: [ThermalCheckResult-A, ServiceCheckResult-A]
    currentFacts: [thermal violated, service satisfied]
    requiredPolarity: both satisfied
    observedOutcome: notSatisfied
    dependentOccurrences: [ThermalCheckAboutCandidate@DR-27, ServiceCheckAboutCandidate@DR-27]
    window: ReviewWindow-DR-27
    result: disabled
    reason: thermal check is violated
  - candidate: RepairCandidate-Continuation
    basisKind: conditionEvaluation
    predicateOrTest: RepairIfAnyCheckViolatedAndProposalTargetsCandidate
    applicability: the proposal concerns DesignCandidate-A
    caseInputs: [ThermalCheckResult-A, ServiceCheckResult-A, RepairProposal-A]
    currentFacts: [thermal violated, service satisfied, RepairProposalTargetsCandidate@DR-27 obtains]
    requiredPolarity: at least one violation and the targeting relation obtains
    observedOutcome: satisfied
    dependentOccurrences: [ThermalCheckAboutCandidate@DR-27, ServiceCheckAboutCandidate@DR-27, RepairProposalTargetsCandidate@DR-27]
    window: ReviewWindow-DR-27
    result: enabled
    reason: one check is violated and the repair proposal concerns this design
currentContinuationSet: enabled [RepairCandidate-Continuation]; disabled [AcceptCandidate-Continuation]; unknown []; error []
stopOrNextAction: show repair as available; recheck when the case results or window change

The structure has two potential continuations although this case enables only repair. The selected proposal-to-design relation belongs to its identity basis. Thermal and service result epistemes, and their about-candidate relations, belong to the current case basis; they are not constituents or selected relation occurrences of this structure.

If the proposal-to-design relation cannot be established, this formal structure claim remains provisional. The ordinary explanation can still report repair as unknown. Do not treat an unknown identity-bearing relation as an established constituent of a qualified CGUS.

A later passing thermal check is a different result episteme and supplies a new case input. With service still satisfied, acceptance becomes enabled and repair becomes disabled. The selected design, proposal, continuation candidates, proposal-to-design relation, constraints, use frame, loci and potential topology are unchanged, so the same CGUS remains available for that new case.

A.22.CGUS:5.1 - A missing intermediate capability changes the continuation

In this constructed learning case, a dancer has the strength and static axis control needed by a figure and can recall its sequence. The known limitation is maintaining balance during its required rotation. The figure’s continuation depends on that coordinated performance, not just on adequate strength and memory.

AlternativeRelevant conditions in this casePresent result
Perform the complete figure under its intended conditions.The required balance during rotation cannot yet be sustained.Unavailable for the intended performance; naming the figure or its steps does not remove the gap.
Practise the rotational coordination under a suitable reduced demand.A domain-appropriate exercise, suitable space and the needed support are available in the stipulated case.Available as practice of the intermediate performance. It does not establish ability to perform the full figure.

During the rotation, balance coordination would constitute part of turning; that turn would constitute part of the figure. These are connections through performance, not three successive tasks. The practice alternative can exercise the first connection without already performing the intended figure.

When the coordination can be sustained, return to the encompassing figure and vary the relevant conditions before drawing a broader capability conclusion. The case condition and its continuation judgement can change without changing the potential alternatives. The subject’s training Method supplies the exercise and assessment; CGUS makes their effect on the available continuation explicit.

A.22.CGUS:6 - Bias-Annotation

Bias riskMitigation
Workflow biasAsk about alternatives and conditions; use work and method patterns only for work-order or way-of-doing claims.
Display biasTreat cards, graphs, tables, narratives, and entry lines as explanations or descriptions, not as the structure.
Formality biasStart with the ordinary decision answer and open formal qualification only for a named later use.
Consumer biasKeep transformation-flow, architecture, improvement, currentness, evidence, and publication details in their patterns.
Lexical biasWords such as route, path, loop, workflow, graph, or sequence establish no CGUS by themselves.

A.22.CGUS:7 - Conformance Checklist

IDPassing conditionFailed-check repair
CC-CGUS-1 Identity and profile.The four A.22 discriminators identify one U.Structure; local locus bindings, relations, and constraints define at least two potential continuations across allowed cases.Recover the missing value or keep the artifact as an explanation.
CC-CGUS-2 Local loci and relation participants.Every CGUSLocusBinding uses a locus declared inside this CGUS and binds one constituent for a stated meaning. A needed relation participant retains its definition, occurrence, order, and binding; RelationSignature and SlotSpec appear together only for declaration-level replay.Restore the locus or complete relation-participant basis. Never use a free-standing SlotSpec as a structure position.
CC-CGUS-3 Explanation and description separation.An ordinary or persisted provisional explanation concerns the subject of its claims; this may be an already identified A.22 structure whose CGUS membership remains unresolved. Post-qualification descriptions and slices concern the CGUS. None is the structure or a membership condition.Restore the right EntityOfConcern or keep the explanation ordinary.
CC-CGUS-4 Current continuation result.Each judgement retains its basis rows with the values required by each applicable condition-evaluation or obtaining-relation branch in 4.2, the relevant case inputs and facts or evidence, dependent occurrences, window, continuation result, and reason. The enabled set may contain zero, one, or several alternatives.Apply the candidate’s condition logic; mark it unknown only when the missing value prevents deciding the result, and retain evaluation errors separately.
CC-CGUS-5 Separate decisions.Identity and membership, case result, description adequacy, and each neighboring claim are judged separately.Reopen only the affected decision.
CC-CGUS-6 Work-order boundary.The selected structure and display expose branches and conditions.Put any prescribed or performed Work order under the Method, work-plan, or Work pattern that establishes it.
CC-CGUS-7 Graph-shaped coverage.Branches, joins, cycles, partial order, and live alternatives are preserved or explicitly omitted for the declared use.Keep a chain provisional or state what its demonstrative slice omits.

A.22.CGUS:8 - Common Anti-Patterns And Repairs

Anti-patternSymptomRepair
Pretty route as ontologyA card or graph is treated as the structure.Keep it as an explanation; qualify the structure independently.
Condition label as resultA label or claim reference is treated as proof that a continuation is enabled.Apply the test or recover the obtaining relation and facts. Mark the continuation unknown when the missing basis prevents deciding it.
One enabled branch as one-branch structureThe present result erases other potential continuations.Keep potential topology and the case result separate.
Formal package or field count firstA simple correction requires replay fields, or authors add references merely to raise schema completion.Use the ordinary branch and stop when it answers the question. In formal use, retain only fields consumed by qualification or replay and test whether readers recover the right alternatives and smallest repair.
Displayed order as WorkA teaching slice becomes a project procedure or authorization.Use the applicable Method, work-plan, or Work pattern for work order, A.21 for a gate decision, and the permission or authority rule for authorization, only when that claim is made.
Consumer architecture copied inwardCGUS repeats transformation-flow locators, naming procedures, or catalogs of neighboring claims.Keep the local structural rule and exit to the pattern that defines or tests the other claim.

A.22.CGUS:9 - Consequences

CGUS preserves the usefulness of a route-shaped explanation without making it a workflow. Ordinary use is cheap: decision, alternatives, conditions, facts, result, and stop. Formal use costs more because structure identity, CGUS membership, the case result, and any description or neighboring claim must remain separately checkable.

This separation prevents a changed fact from reidentifying a stable structure and prevents a missing publication, evidence, or assurance value from erasing a useful ordinary answer.

A.22.CGUS:10 - Rationale

The recurring object is a thin specialization of A.22 U.Structure, not a new root kind. The cited constraint-based, object-centric, artifact-centric and acausal approaches provide different ways to express relations and constraints beyond one displayed execution path. CGUS uses this design question while retaining its own A.22 identity and continuation tests.

The same distinction appears in acausal engineering models: component relations and constraints can be stated before an analysis chooses a calculation direction. FPF adopts only that general separation. Mathematical models, analyses, executions, results, and publications keep their own kinds and rules.

A.22.CGUS:11 - SoTA-Echoing

Source or practice anchorFPF adoptionBoundary
Aaron Küsters and Wil M.P. van der Aalst, “OCPQ: Object-Centric Process Querying & Constraints”, 2025Comparison for queries and constraint checks over typed objects and events, including linked instances and their qualified relationships in the cited 2025 work.A query or result is not the CGUS.
JuliaHub, Dyad Components and Reuse and Analyses documentationEngineering comparison for reusable equation-based component models and connections, separately defined analyses, and their solution objects.FPF imports neither Dyad ontology nor its tools. Modelica 3.7 is retained only as historical acausal-modeling lineage.
Declare/MP-Declare, DCR, artifact-centric/GSM, and CMMN workLineage for declarative constraints, live alternatives, stages, guards, and weakly structured case work.These are not current authority for a universal FPF process calculus; their notation and workflow ontology are not imported.
FPF pattern-language practiceOrdinary explanations may precede qualification; descriptions and demonstrative slices may follow it.Publication form alone supplies neither CGUS qualification grounds nor specification force.

A.22.CGUS:12 - Relations

Specializes: one A.22 U.Structure whose local locus bindings, obtaining relations, and constraints define at least two potential continuations across allowed cases. Continuation judgements, descriptions, slices, loss notes, and neighboring claims are separate results or uses.

Specialized by: E.18.3 when the same structure also satisfies its transformation-flow condition. Local applications include architecture, abduction, improvement, narrative, grounding, currentness, and first-entry uses only when their own constituents, relations, constraints, and use frames are recoverable.

Coordinates with: A.6.P and A.6.5 for relation occurrence and reusable declaration precision; E.18, E.18.NET, and E.18.3 for transformation-flow substrates; A.3 and A.15 for Method, plan, Work, and Transformation claims; A.10 for claim-bound evidence reliance, B.3 for a named assurance claim, A.20 for internal-constraint validity, and A.21 for gate decisions; C.30 for architecture claims and C.32 for architecture-candidate synthesis; E.23 for repeated quality improvement under a declared evaluation; G.11 for currentness; C.29 for mathematical-lens use; C.33 for description loss that affects a declared architecture use; E.11 for entry, E.17 for a source-backed reader face, and E.24.PUB for publication occurrence, form, carrier, audience, bounded use, and availability; and F.17, F.18, and F.9 for source-local sense, durable naming, and Bridge claims.

Does not replace any pattern that supplies the definition, constraint, test, method, evidence rule, or assurance rule for a neighboring claim.

Use F.19 for ordinary precise-plain-language repair and the plausible-reader test for an optional explanatory overread.

A.22.CGUS:End