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

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

Part A - Kernel Architecture Cluster

A.0 - Generative Search Onboarding Glossary (NQD & E/E‑LOG)

Status: Stable Use this when choosing or describing a generative search or selection. This glossary identifies the values, policies and set-result kinds needed by that operation, and connects them to their definitions in C.17–C.19. Section 4.3 shows how to use those terms with G.5 selection and the publication requirements of the receiving task.

Builds on. E.2 (P‑10 Open‑Ended Evolution; P‑2 Didactic Primacy), A.5, C.17–C.19 - Coordinates with. E.7, E.8, E.10; F.17 (UTS); G.5, G.9–G.12 - Constrains. Any pattern/UTS row that describes a generator, selector, typed portfolio publication, or set-return publication surface.

Keywords & queries. novelty, quality‑diversity (NQD), explore/exploit (E/E‑LOG), declared set result, typed portfolio publication, illumination map (report‑only telemetry), parity run, comparability, ReferencePlane, CL^plane, ParetoOnly default

A.0:1 - Problem Frame

Engineer-managers choosing a search or selection need to distinguish candidate quality, search coverage, explore/exploit policy and the result being returned. Plain definitions provide an entry to these distinctions; the corresponding operation in C.17–C.19 or Part G supplies the method and its conditions.

A.0:2 - Problem

The following mistakes obscure how a search result was obtained and what it can be used for:

  • Single‑winner bias. Teams look for “the best” option and publish a leaderboard, suppressing coverage & diversity signals essential to search.
  • Metric confusion. “Novelty” and “quality” are used informally; units and scales are omitted; ordinal values are averaged, breaking comparability.
  • Hidden policies. Explore/exploit budgets and governor rules are implicit; results are irreproducible and refresh‑unsafe (no edition/policy pins).
  • Tool lock‑in. Implementation terms (pipelines, file formats) leak into the Core, violating Guard‑Rails.

This glossary names the generative terms in Plain register and ties them to their formal anchors, so a publication can distinguish candidate scores, retained sets and selected results.

A.0:3 - Forces

ForceTension
Readability vs RigorOne‑liners for managers ↔ lawful definitions with editions and scale types.
Creativity vs AssuranceOpen‑ended search (OEE/QD) ↔ conformance, parity, and publication discipline.
Comparability vs LocalityShared N‑U‑C‑D terms ↔ context‑local CG‑frames and bridges with CL.
Tool‑agnostic CoreConceptual publication in UTS ↔ engineering teams’ urge to cite specific tools.

A.0:4 - Solution - Normative onboarding glossary and publication hooks

A.0:4.1 - Plain one‑liners (normative on‑ramp; formal anchors in C.17–C.19)

TermPlain definition (on‑ramp)See
Novelty (N)How unlike the known set a candidate is in your declared CharacteristicSpace. Use the declared DescriptorMapRef and DistanceDefRef, with no ad-hoc normalisation.C.17, C.18
Use‑Value (U / ValueGain)What the candidate helps you achieve now under your CG‑Frame; tie to acceptance/tests; publish units, scale kind, polarity, ReferencePlane.C.17, C.18
Constraint‑Fit (C)Satisfies must‑constraints (Resource/Risk/Ethics); legality via CG‑Spec; unknowns propagate (never coerce to zero).C.18, G.4
Diversity_P (declared retained set)Coverage or dispersion of the declared retained set under a named measurement policy; declare ReferencePlane. Its change on adding one candidate is DeltaDiversity_P.C.17, C.18
E/E‑LOGNamed, versioned explore↔exploit policy; governs when to widen space vs refine candidates; policy‑id is published.C.19
ReferencePlaneWhere a value lives: world (system), concept (definition), episteme (about a claim). For a plane relation, retain its source/target planes and basis. Cite CL^plane for a used or required calibration and the Φ_plane policy and loss model for a used or required loss calculation; any numerical assurance penalty requires an applicable B.3 model.F.9, G.Core:4.2.3
Scale Variables (S)The monotone knobs along which improvement is expected (e.g., parameterisation breadth, data exposure, iteration budget, resolution). Declare S for any generator/selector claimed to scale.C.18.1
Scale Elasticity (χ)Qualitative class of improvement when moving along S (e.g., rising, knee, flat in the declared window). Used as a selection lens; numeric laws live in domain contexts.C.18.1
BLP (Bitter‑Lesson Preference)A preference supported by a comparable, uncertainty-qualified scale comparison; begin with a cheap scale-claim probe. No scale claim yet or no scale-based preference are valid results. A local generality policy is a separate declared basis.C.19.1, C.24
Iso‑Scale ParityFair comparison across candidates at equalised scale budgets along S; may also include scale‑probes (two points) to test elasticity.G.9, C.18.1

(Use LEX‑BUNDLE for the applicable measurement and scope terminology.)

A.0:4.2 - Publication & telemetry duties (where these terms show up)

  1. UTS surface (Part F). When a UTS row describes a generator, selector, typed portfolio publication, or set-return publication surface, it MUST surface each glossary value or policy used by the declared operation or independently required by the receiving use. Type each reported value’s applicable units, scale, polarity and ReferencePlane under MM‑CHR and CG‑Spec, and cite its defining basis, including DescriptorMapRef and DistanceDefRef when used or required. (Row schema: F.17; shipping via G.10.)
  2. Parity & edition pins (Part G). When QD/OEE is in scope, pin the editions and policies used by the operation or required by its receiving use, including DescriptorMapRef.edition, DistanceDefRef.edition, the CharacteristicSpaceRef with its separate characteristicSpaceDescriptionRef: U.EpistemeRef under A.19:5.1.1.1 and TransferRulesRef.edition where applicable; record PathSliceId when required by that use. G.9 supplies the pin requirements for a parity use. Treat illumination/coverage as report‑only telemetry; publish an Illumination Map where G‑kit mandates parity records. Declare S (Scale Variables) and run at least one scale‑probe (two points along S) when claiming scale‑amenability. Dominance policy defaults to ParetoOnly; including illumination in dominance MUST cite a CAL policy‑id.
  3. Tell‑Show‑Show (E.7/E.8). Any architectural pattern that claims generative behaviour MUST embed both a U.System and a U.Episteme illustration using this glossary (manager‑first didactics).

A.0:4.3 - Putting the glossary to use

  1. Declare CG‑Frame (what “quality” means; admissible units and scales) and ReferencePlane.
  2. Choose the Q components and DescriptorMap coordinates needed by the intended operation; retain their meanings and applicable editions.
  3. Choose an E/E‑LOG policy and record its policy‑id when the operation or receiving use requires explore↔exploit control.
  4. Apply G.5 selection/dispatch with its applicable basis pins; add parity pins for a parity use. Keep any consumed Front or Archive identified as the source set. For a set outcome, return Shortlist or RankedShortlist for retained alternatives, or JointUseSet when all named members are included for one named use. Return a handoff, abstain, or escalation when that is the G.5 outcome.
  5. Keep the G.5 outcome’s required content and basis pins. Publish that result only when the receiving use calls for publication, with its applicable PathIds/PathSliceId. Add a UTS row for a named governed value only when F.17’s independent naming and reuse conditions hold; otherwise reuse its existing designation. Follow the outcome’s continuation or stop. An Illumination Map remains report‑only telemetry by default.

A.0:5 - Archetypal Grounding

Informative; manager‑first (E.7/E.8 Tell‑Show‑Show).

Show‑A - SRE capacity plan (selector returns a set). Frame. We must raise service commitment headroom for Q4 without breaking latency SLOs. Declared retained set. {cache‑expansion, read‑replicas, query‑shaping, circuit‑breaker tuning, schema‑denorm}. Glossary in action. U = latency@p95 & error‑rate, C = budget ≤ $X, risk ≤ R, N = dissimilarity to current playbook, Diversity_P = coverage of the declared retained set under the niche policy, DeltaDiversity_P = additional coverage from adding a candidate (e.g., “shifts load to edge” fills an empty niche). E/E‑LOG starts Explore‑heavy, flips Exploit‑heavy once ≥ K distinct niches are lit. (Publish a UTS row only when F.17’s naming and reuse conditions hold; retain parity pins for a parity use; illumination stays report‑only telemetry.)

Show‑B - Policy search with QD archive (MAP‑Elites‑class). Frame. Robotics team explores gaits that trade stability vs energy use. Glossary in action. CharacteristicSpace = {step‑frequency, lateral‑stability}, ArchiveConfig = CVT grid, N from descriptor distance, U = task reward, Diversity_P = coverage of the retained gait set under the declared grid policy; PortfolioMode=Archive. Families include MAP‑Elites (2015), CMA‑ME/MAE (2020–), Differentiable QD/MEGA (2022–), QDax (2024); publish editions and policy‑ids; treat illumination as report‑only telemetry.

(Optional) Show‑C - OEE parity (POET/Enhanced‑POET). Co‑evolve declared {environment, method} sets; publish coverage/regret as telemetry metrics; pin TransferRulesRef.edition; return sets, not a single winner.

Show‑Epi - Evidence synthesis (U.Episteme). Frame. A living review compares rival causal identification methods (e.g., IV vs. DiD vs. RCT‑adjacent surrogates) across policy domains. Glossary in action. U = external‑validity gain @ F/G‑declared lanes, C = ethics & data‑licence constraints, N = dissimilarity in **ClaimGraph** transformations, D_P = coverage of identification niches in the archive. ReferencePlane = episteme. Illumination/coverage stays report‑only telemetry; selection retains alternative methods as an unranked Shortlist, with the relevant identification niches stated for each method. When the receiving use calls for publication, publish a typed portfolio view of that result. (Publish UTS rows only when F.17’s naming and reuse conditions hold; cite obtaining Bridges for cross‑domain semantic correspondence, with calibration and loss‑model pins when used or required under G.Core:4.2.3; edition‑pin the Descriptor/Distance defs used or required by the QD use.)

A.0:6 - Bias-Annotation

Scope. Trans‑disciplinary; glossary applies to work concerning both Systems and Epistemes. Known risks & mitigations. Over‑aggregation: forbid mixed‑scale sums; use CG‑frame and MM‑CHR. Terminology drift: enforce LEX‑BUNDLE registers; ban tool jargon in Core. Optimization monoculture: require declared set-result or typed portfolio publication where G‑kit mandates parity; illumination stays report‑only telemetry unless a CAL policy promotes it (policy‑id cited).

A.0:7 - Conformance Checklist (SCR/RSCR stubs)

IDRequirementPurpose
CC‑A0‑1If a pattern/UTS row describes a generator, selector, typed portfolio publication, or set-return publication surface, it MUST surface the glossary values and policies used by its operation or independently required by the receiving use, with their applicable units, scale, polarity, ReferencePlane and policy‑ids.Makes generative claims comparable and auditable (UTS as publication surface).
CC‑A0‑2For QD/OEE, pin the editions and policy‑ids used by the operation or required by the receiving use, including DescriptorMapRef.edition, DistanceDefRef.edition, the CharacteristicSpaceRef with its separate characteristicSpaceDescriptionRef: U.EpistemeRef under A.19:5.1.1.1 and TransferRulesRef.edition where applicable. Log PathSliceId when required; follow G.9’s pin requirements for a parity use.Enables admissible parity and refresh; edition-aware telemetry.
CC‑A0‑3No mixed‑scale roll‑ups; ordinal data SHALL NOT be averaged; any roll‑up MUST live under a declared CG‑frame.Prevents illegal scoring; keeps comparisons lawful.
CC‑A0‑4Where the G‑kit requires parity, publish an Illumination Map (coverage per niche); single‑number leaderboards are non‑conformant on the Core surface when a ParityReport is required.Declared-set-first / typed portfolio-publication posture; avoids single‑winner bias.
CC‑A0‑5Keep illumination/coverage as report‑only telemetry; dominance policy defaults to ParetoOnly; any change is CAL‑authorised and cited by policy‑id.Separates fit from exploration; preserves auditability.
CC‑A0‑6Apply E.7/E.8: include a U.System and a U.Episteme illustration when claiming generative behaviour; obey E.10 register hygiene; use the subsection title “Archetypal Grounding.”Locks didactic primacy; prevents jargon drift.
CC-A0-7ReferencePlane declared for every reported N/U/C/Diversity_P head. For a plane relation, retain its source/target planes and basis under G.Core:4.2.3; cite CL^plane for a used or required calibration and the Φ_plane policy and loss model for a used or required loss calculation. Numerical assurance penalties follow an applicable B.3 model.Prevents plane/stance category errors while preserving applicable crossing and receiving-use grounds.
CC‑A0‑8Diversity_P ≠ Illumination. Diversity_P measures the retained set; DeltaDiversity_P measures a candidate’s marginal contribution to it. Either requires a declared PromotionPolicy before entering dominance. Illumination remains report‑only telemetry unless explicitly promoted by a CAL-authorized policy-id.Matches QD triad semantics and parity defaults.
CC‑A0‑9For any generator/selector scale-behaviour claim, declare S (Scale Variables), its ScaleWindow, and an E/E-LOG scale policy-id. Mark S = N/A only when no scale-behaviour claim is made.Keeps a negative scale result within its declared comparison basis.
CC‑A0‑10For scale-behaviour claims, execute a scale-probe (≥ 2 points along S within the declared ScaleWindow) and report the supported Scale Elasticity class (rising/knee/flat/declining), or leave χ unassigned and state what remains unresolved, under C.18.1. Use a UTS row only when F.17’s naming and reuse conditions hold.Distinguishes supported declining response from unresolved classification and N/A.
CC‑A0‑11Apply Iso‑Scale Parity in parity runs when S is declared; where infeasible, state the loss notes and treat results as non‑parity. For a penalty calculated or required by the receiving use, cite its model and policy; numerical assurance penalties require an applicable B.3 model.Keeps comparisons fair and auditable under scale constraints.
CC‑A0‑12Record a BLP-waiver only when overriding a declared generality preference that would otherwise decide the use. Apply C.19.1’s governed grounds: admissibility override, parity-supported scale-probe overturn, or non-blocking complementary bias. Bounded specialization alone requires no waiver.Makes a policy override transparent without imposing one on ordinary bounded tactics.

A.0:8 - Consequences

Benefits.

  • Plain definitions tied to the formal anchors needed for use and checking.
  • Distinct names for retained sets and selector outcomes, with their metric and policy meanings.
  • Explicit edition and policy basis for checking comparability and refreshing affected results.

Trade‑offs & mitigations.

  • Slightly longer UTS rows → mitigated by consistent schema and copy‑paste snippets.
  • Requires discipline on units and scales → mitigated by CG‑frame templates.

A.0:9 - Rationale

Quality-diversity and open-ended search require both candidate comparison and retention of useful search coverage. This glossary makes those purposes distinguishable in an operation and its published results, supporting P‑10 Open‑Ended Evolution. Plain definitions follow Didactic Primacy (P‑2) and LEX‑BUNDLE (E.10); references to C.17–C.19 retain the metric and policy definitions under Patterns Layering (P‑5). The examples in section 5 show how these distinctions apply to search without prescribing a particular tool.

A.0:10 - Relations

Builds on. E.2 Pillars (P-10, P-2, P-6), A.5 (Open-Ended Kernel), B.5/B.5.2.1 (Abductive loops + NQD integration), C.17–C.19 (Creativity-CHR, open-ended search archive/front stewardship, E/E-LOG).

Coordinates with. E.7/E.8 (Archetypal Grounding; Authoring template), E.10 (LEX‑BUNDLE), F.17 (UTS), G.5/G.9–G.12 (set‑returning selectors, iso‑scale parity, shipping & refresh). Constrains. Any generator/selector/typed portfolio publication on the Core surface: the glossary values, policies and basis pins used by its operation or required by its receiving use; lawful scales; S/Scale‑probe for scale claims; parity pins for parity use; declared-set publication where mandated. (Ties into UTS rows and parity records.) For agentic orchestration of scalable tool‑calls under BLP/SLL, see C.24 (Agent‑Tools‑CAL).

A.0:QF.0a - Scope of this glossary

Use C.17–C.19 for the corresponding metrics and search policies. This glossary connects their terminology to the selected operation and its publication or telemetry requirements.

A.0:QF.1 - Early set-result and metric-kind vocabulary

  • Use Palette for a plurality-preserving set with no dominance semantics yet.
  • Use TraditionPalette only when the members are traditions gathered before later comparison or choice semantics are declared.
  • For methods, hypotheses, environment-method pairs, candidate explanations, or other member kinds, use Palette plus explicit SubjectKind instead of borrowing the TraditionPalette head.
  • Use Front only for a non-dominated set under one declared DominanceSet.
  • Use Q-Front when the declared DominanceSet is the declared Q components.
  • Use Archive for a retained set whose purpose is coverage, stepping-stone retention, or frontier expansion rather than current non-domination.
  • Use ExplorationArchive for the broad retained exploration surface; it is the exploration-specific specialization of Archive.
  • Use SteppingStoneSet only for one narrower retained subset whose stated purpose is future frontier reach rather than the whole archive. It is not part of the ordinary first-pass public-head family for retained exploration.
  • Use Shortlist for the set chosen from one declared source set by one named lens.
  • Use RankedShortlist only when that shortlist is explicitly rank-ordered.
  • Use JointUseSet when every member is included for one named use; keep that use, keyed member entries, inclusion conditions, and basis pins under G.5.
  • Use ShortlistId for the stable public token of one emitted shortlist; it is not the shortlist itself.
  • Use ChoiceSet only when the mathematical set object underlying one shortlist must be named explicitly; do not let it replace the public shortlist head.
  • Use Q-set for the declared current objective tuple that may ground the current DominanceSet.
  • For a result or claim used by a pool policy, retain its direct pattern’s reference name and kind; for example, A.2.2 supplies capabilityHolderRef and capabilityStatementRef. Use C.19 for the resulting pool treatment. Citing an input does not add it to Q or dominance.
  • Use competenceModelRef under C.19 only for one model episteme used by the policy; identify the capability and supporting results separately.
  • When the pool treatment relies on an evidence-bearing or source-bearing claim, use a10RelianceRef for the claim and bounded pool-treatment reliance under A.10.
  • Use goalSpaceExpansionPolicyRef under C.19 when an independently declared archive or curriculum expansion policy governs goal- or task-space growth; that policy does not place a candidate on a front or add a dominance coordinate.
  • When future reach depends on a transition or transfer relation, cite its direct rule and supporting result references together with any model episteme used. Keep their use in archive/pool policy separate from any explicitly authorized promotion into dominance.
  • If one front is meant to be current-Q by default, say so as Q-Front or as Front over the declared Q components rather than leaving the relation between Q-set and DominanceSet implicit.
  • Use-Value may be one member of the Q-set only when the current Context declares it there; it is not the whole Q-set or the default Q-set by itself.
  • Metric-kind doctrine: the Q-set is the candidate/front-facing objective tuple; Novelty@context is one context-relative candidate signal; DeltaDiversity_P is one set-relative marginal diversity contribution; IlluminationSummary is one report-only archive telemetry summary unless one explicit policy promotes it.
  • Minimal mathematical lens: the current front lives in one declared comparison or outcome space, while the exploration archive may depend on one declared search, niche, or reachability space. Keep both spaces explicit when they differ.
  • Keep Novelty@context, DeltaDiversity_P, Surprise, and IlluminationSummary outside the default Q-set unless one declared PromotionPolicy says otherwise.
  • A reader should be able to tell whether one sentence is talking about a Palette, a Front, an Archive, a SteppingStoneSet, a Shortlist, a RankedShortlist, or a JointUseSet, and whether one selected set came from one declared source set, before later policy or geometry detail arrives.
  • Use portfolio only when the portfolio or set-result field is a declared retained set plus a selection/retention rule or a portfolio-publication posture. Do not use bare portfolio when Palette, Front, Archive, SteppingStoneSet, Shortlist, or RankedShortlist is already recoverable.

A.0:QF.1a - Helper declarations for set-result language

  • Ordinary public set-result family heads are Palette, TraditionPalette, Front, Q-Front, Archive, ExplorationArchive, Shortlist, RankedShortlist, and JointUseSet; the applicable pattern fixes which families its operation may return.
  • SteppingStoneSet is one narrow retained-subset head only when that subset itself is the visible published surface; do not treat it as the ordinary public head for retained exploration.
  • SetResultFamily is a declaration field naming which public set-result family is being emitted; it is not another public head.
  • SourceSetFamily is a declaration field naming the immediate source-set family acted on by a lens, such as Q-Front, ExplorationArchive, Front, Archive, or TraditionPalette; it does not specify derivation, composition, or object identifiers, and it does not rename the emitted result.
  • SourceSetComposition is an optional declaration field for a composition of several declared source sets, including different sets of the same family. Identify each contributing set and its family, and state how its members contribute, such as Front+Archive through a union when that is the construction. It is not itself a kind.
  • SubjectKind is a declaration field naming what the members are, such as traditions, methods, hypotheses, environment-method pairs, candidate explanations, or other subject-kinded alternatives.
  • EligibilitySet, DominanceSet, TieBreakerSet, and TelemetrySet are the comparison-bundle sets behind the published set result, not rival publication heads: EligibilitySet says what may enter, DominanceSet says what counts for current non-domination, TieBreakerSet says what may order or choose among survivors, and TelemetrySet says what may be reported without changing dominance.
  • PromotionPolicy is the policy pin that authorizes one tie-breaker or telemetry signal to move into dominance. Without that pin, novelty, diversity, surprise, illumination, or similar signals remain outside the current DominanceSet.
  • DerivedViewKind is an optional declaration field for a derived view, such as one tradition view used for interpretation or publication. It must leave the base SourceSetFamily, SetResultFamily, and emitted shortlist family recoverable.
  • BasePaletteRef is an optional cited id/ref for the base palette when one derived tradition view or shortlist depends on that palette; it is a ref, not a kind.
  • Stable values for SetResultFamily, SourceSetFamily, SourceSetComposition, SubjectKind, and DerivedViewKind should come from controlled tokens, cited ids, or already-declared head labels; do not let one ad hoc local prose label become a de facto field value.
  • When the upstream object is SoTAPaletteDescription and its members are traditions, TraditionPalette may be used as the reader-facing tradition-only alias for that same palette declaration. When the members are not traditions, keep SoTAPaletteDescription or Palette + SubjectKind explicit instead of widening TraditionPalette.
  • RetentionIntent=steppingStone is a field value on retained archive membership intended for future frontier reach. A SteppingStoneSet names a narrower retained subset only when that subset itself is the published set result being discussed; the ordinary archive head names the whole archive.

A.0:QF.2 - First public wording for shortlisted results

  • When a reader needs the visible selected set, say Shortlist from <SourceSetFamily> under <LensId>.
  • When the selected set must be cited as one stable emitted object, say ShortlistId and keep one nearby line that names the shortlist and its source set.
  • When the shortlist is ordered, say RankedShortlist and keep the underlying shortlisted set result recoverable rather than jumping straight from Front to ranking.
  • Use choice set underlying that shortlist only when the mathematical set object itself is the point of the sentence.
  • A reader should be able to recover on first pass what source set was acted on, what shortlist came out, and whether the text is naming the published set result, the token, or the mathematical set object.

A.0:QF.2a - Set/space reading glosses

The set/space terms have the following meanings:

  • SearchSpaceRef
    • a declared reference to the CharacteristicSpace currently used to search, compare, or navigate candidate possibilities
    • a role-named ref field using the existing CharacteristicSpaceRef / SpaceRef idiom; it introduces no new space kind
  • OutcomeSpaceRef
    • a declared reference to the CharacteristicSpace currently used to judge outcomes, effects, or realized value
    • a role-named ref field using that same idiom; it is not a synonym for SearchSpaceRef
  • DeclaredSubstrateInterpretiveView
    • the common head of an optional interpretive-view family over an already-declared substrate-bearing line, a source set, or a set result whose substrate remains recoverable
    • it helps the reader see the current inspection question; it does not replace the base source set or introduce a new substrate
  • DeclaredSubstrateAtlasView
    • an optional interpretive view that shows how several declared views, spaces, mappings or qualifications relate within the same substrate
    • use it only when the current reading needs that composite interpretation, and say why a simpler interpretation is not enough; it is not the default meaning of palette, front, archive, shortlist, or candidate set
  • TypedSetViews
    • a list of the declared set-view heads that the current atlas/support reading holds together
    • use it when several declared views must stay visible together; it does not create a new set result and should not hide the active source set or active set result
  • OutcomeMapRef
    • a map reference showing how a declared source or set result bears on a declared outcome-side or effect-side space when that map materially affects the interpretation
    • it qualifies the reading; the source set and the outcome-side declared space or reference remain distinct
  • SpaceMetricRef
    • a metric-ref qualifier for the metric, neighborhood, distance, density, or reachability discipline used inside a declared space
    • it qualifies how positions in that space are compared; it is not the space itself or a substitute for SearchSpaceRef or OutcomeSpaceRef
  • TransitionRelationRef
    • a transition-ref qualifier for the transition, cross-scale state-change, dynamic-coupling, or phase-change basis on which the reading depends
    • it explains why motion or cross-scale state change is read a certain way; it does not by itself decide policy, planning, or publication
  • BridgeDistortionNote
    • a note describing fidelity limits in a useful bridge, projection, aggregation, or derived reading
    • it identifies where comparison is distorted or information is lost, so claims of bridging, substitution, or reliance stay within the stated limits

A.0:QF.2b - Practitioner-facing reading cue

  • If the question is “Which space are we searching or navigating?”, look for SearchSpaceRef.
  • If the question is “Which space are we judging outcomes in?”, look for OutcomeSpaceRef.
  • If the question is “What optional overlay helps me read several declared views or set results together?”, look for DeclaredSubstrateInterpretiveView.
  • Use DeclaredSubstrateAtlasView when answering the named inspection question requires showing how several declared views, spaces, mappings or qualifications relate within the same substrate.
  • If the atlas/support reading must keep several declared set views visible at once, look for TypedSetViews.
  • If the overlay depends on one explicit source-to-outcome mapping, look for OutcomeMapRef.
  • If the overlay depends on one metric, neighborhood, or reachability discipline inside one declared space, look for SpaceMetricRef.
  • If the overlay depends on one transition, cross-scale state-change, or dynamic-coupling basis, look for TransitionRelationRef.
  • If the overlay depends on one bridge or projection that may lose fidelity, look for BridgeDistortionNote.

A.0:QF.2c - First-use classification check

  • Start with DeclaredSubstrateInterpretiveView when the NQD/OEE task is simply to keep one declared palette, front, shortlist, or archive readable while comparing candidate material.
  • Start with it only when any cited SearchSpaceRef, OutcomeSpaceRef, mappings, or qualifiers are already declared elsewhere and remain recoverable through the base substrate, source set, or set result.
  • Escalate to DeclaredSubstrateAtlasView only when one named InspectionQuestion about the same declared substrate requires reading several declared views, spaces, mappings, or qualifiers together. State what their joint reading contributes to that question and why a simpler interpretation is insufficient; use A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW for the declaration.
  • If the reading keeps several declared set views together, name TypedSetViews explicitly.
  • If the reading depends on one source-to-outcome map, name OutcomeMapRef explicitly.
  • If the reading depends on one metric or neighborhood discipline, name SpaceMetricRef explicitly.
  • If the reading depends on one transition, cross-scale state-change, or dynamic-coupling basis, name TransitionRelationRef explicitly.
  • Creating a search doctrine, an outcome metric family, or a publication surface lies outside this interpretive-view guidance; use the object’s governing patterns for those decisions.

A.0:End


A.1 - Recognize a Whole with Parts (U.Holon and Admitted Holon Kinds)

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

A.1:0 - Use This When

Use this pattern when a decision depends on whether an entity is a whole with parts, an acting System, or a claim-bearing holon.

Typical moments:

  • physical or operational abilities are being attributed to a theory or document merely because it is called a system;
  • an episteme is treated as an acting agent that decides, performs work, authorizes, promises, or revises itself;
  • a proposed whole needs an account of its constituents and construction;
  • a collection is expected to act, but no acting system has been constructively recognized;
  • architecture or selected-structure claims need the holon whose structure is being selected.

Primary EntityOfConcern. A U.Entity candidate whose actual construction may or may not satisfy the constructive recognition criterion for an already admitted holon kind.

Primary working reader. A practitioner or modeler who must decide whether part-whole, acting-system, or claim-bearing-holon reasoning is admissible for that entity before relying on neighboring work, architecture, evidence, or publication claims.

First useful move. Name the U.Entity under concern. Then test whether its actual construction satisfies the A.1 holon-recognition criterion under an already admitted public holon kind. The kind is already admitted in the current FPF; E.24.UK governs the separate one-time decision to admit public U-kinds. The A.1 candidate test does not repeat that ontology decision.

When the next decision depends on which System acts, is intended to change, carries a capability, persists, or is being considered or designated as the project system-of-interest, use A.1.SCR to find that proposed subject. A.1.SCR first checks whether a non-system subject already answers the decision; apply the complete A.1 criterion only while the decision still depends on systemhood.

Once the proposed or observed focus is current, use A.1.CSD when the next question is which other Systems may undergo relevant changes and omitting one could change a named decision or investigation. That branch discovers candidate bearers and qualified consequence claims; it does not repeat recognition of the focus or settle causality, evaluation, or choice.

After recognition, use A.1.STM when a connected project account is still needed to explain the System’s intended use, the functioning and construction required for that use, and how capable creators can obtain that System, including how to obtain or change a creator the project needs. Otherwise apply the rule that defines or tests the next claim.

What goes wrong if missed. A claim attributes revision Work to a document, gives a theory physical ports, or treats a list as an organization. A lathe that changes a workpiece is treated as its containing whole without an obtaining part-whole relation. An architecture claim lacks the holon whose structure is selected.

What this buys. FPF gets one compact part-whole foundation without turning every whole into a physical system: identity starts at U.Entity; part-whole treatment starts at U.Holon; acting work attaches to U.System; claim-bearing knowledge is carried by U.Episteme; method holonhood is governed by U.Method; other admitted holon kinds keep their own subject patterns.

Not this pattern when.

  • If the current question is a selected bounded model-use relation organization, use A.1.1.
  • If the current question is episteme identity, constitution, or neighboring-relation discipline, use C.2.1.
  • If the current question is relation vocabulary or component, portion, aspect, and phase discipline, use A.14.
  • If the current question is constructive part-whole grounding, use C.13; use B.3.5 for Working-Model assurance grounding.
  • If the current question is selected structure over a holon, use A.22.
  • If the current question is architecture of a holon, use C.30.
  • If the current question is transformation, method, system-role kind or assignment, work, capability, or functioning, use the subject pattern before relying on A.1.

A.1:1 - Problem Frame

A pump can move water, a theory can carry claims, and a team can coordinate work. FPF needs a referenceable root broad enough for these objects while retaining the different conditions for part-whole, acting and claim-bearing claims.

A.1 separates four questions that are often collapsed:

  • reference: what can be individuated as U.Entity;
  • part-whole treatment: which candidates satisfy the constructive recognition criterion for U.Holon or another already admitted public holon kind;
  • acting eligibility: which recognized holons also satisfy the kind-specific criterion for the already admitted U.System kind;
  • claim-bearing knowledge: which recognized holons also satisfy the kind-specific criterion for the already admitted U.Episteme kind.

Entity identity and world-side holon recognition have a context-independent base. Claim scope, effective reference scheme, and selected model-use structure can qualify an assertion or use, but none identifies the candidate, makes the constructive criterion true, or admits a public U-kind.

Other admitted holon kinds are not created by title, by filling one locally named slot, or by ordinary-language label. They remain governed by their direct patterns. Current accepted examples include U.Method under A.3.1, U.Work under A.15.1, and U.Discipline under C.20. BoundedModelUseStructure under A.1.1 is U.Structure, not a holon kind.

A.1:2 - Problem

Without A.1:

  1. System-bias spreads. Physical and operational assumptions are projected onto epistemes, descriptions, theories, documents, dashboards, and source records.
  2. Epistemes become agents. A document, model, theory, pattern, or report is said to decide, promise, authorize, perform work, or revise itself.
  3. Collections become collectives by wording. A collection is treated as an acting whole without establishing its constituent relations, assembly and acting eligibility.
  4. Transformation becomes containment. A system that changes another holon is treated as the larger whole containing it, or as standing in a part-whole relation to it, merely from that interaction.
  5. Architecture loses its grounding holon. A structure, view, graph, diagram, or architecture claim floats free of the holon whose selected structure is under concern.
  6. Slot filling creates false kinds. A system, episteme, holon, relation occurrence, or other value is given a new intrinsic kind merely because it fills one slot of a system-role assignment, evidence, publication, description, or another direct relation.

A.1:3 - Forces

ForceTension
Universal root vs domain comfortPractitioners know words such as system, model, product, team, document, program, and discipline; FPF needs a cross-domain root that does not import one domain’s assumptions.
Identity vs compositionA thing can be individuated before FPF knows whether it has parts or belongs to a larger whole.
Acting vs claim-bearingSystems can be classified by local system-role kinds, perform Work, and participate in separately governed system-role-assignment, Method-enactment, plan-use, publication, citation, comparison, or reliance relations. Changed claim content identifies another episteme under C.2.1.
Open-world modeling vs premature completionA holon slot can be relevant even when not yet filled; omission means “not current or not recovered”, not absence in the world.
Collection usefulness vs collective agencyCollections can have whole-level characteristics without being acting systems.
Architecture usefulness vs math-lens driftGraphs, algebras, matrices, and embeddings can describe structures; they do not become the structure or holon by spelling.

A.1:4 - Solution

Use A.1 to distinguish a referenceable entity from a candidate that satisfies the constructive holon criterion under an already admitted public holon kind.

U.Entity
  U.Holon
    U.System
    U.Episteme
    U.Method           only under A.3.1 and direct method-composition patterns
    U.Work             only under A.15.1
    U.Discipline       only under C.20
named C.3 U.Kind   only when the admission predicate defined in the subject pattern is satisfied

This is not a classical taxonomic ladder. E.24.UK is the pattern for public U-kind admission; A.1 is the pattern for recognition of candidates under the admitted holon kinds and the kind-specific patterns shown above. A selected U.Structure, including BoundedModelUseStructure, remains dependent relation organization rather than a holon kind.

A.1:4.1 - U.Entity

U.Entity is anything that can be individuated and referenced. It carries no part-whole, acting, claim-bearing, model-use, or architecture assumption by itself.

When observations may concern the same continuing entity and the next use depends on that identification, use A.1.RI. It constructs and compares connections under the entity’s continuation criterion and the applicable subject and observation rules. An adequate available identification can be used directly.

Use U.Entity when the current move only needs to point to something—for example, a number, claim, named product, material batch, data value, legal clause, local system-role kind, reference, document, or another object under concern.

Do not apply holon aggregation, part-whole grounding, acting-system roles, or architecture claims to a bare U.Entity unless its actual construction satisfies the A.1 criterion for U.Holon or a kind-specific criterion for another already admitted public holon kind.

A.1:4.2 - U.Holon And Context-Independent Recognition

U.Holon is the broad part-whole EntityOfConcern: a U.Entity whose actual construction supports treatment as a whole with parts and as a possible part of a larger whole.

Keep ontology admission and candidate recognition separate. Use E.24.UK for the one-time FPF decision that admits U.Holon and every other public holon kind. A.1 is the pattern for the constructive criterion by which a candidate is recognized under an already admitted kind. C.3.2 supplies three-valued discipline only for project-local kind membership; it does not own recognition under an admitted public holon kind. Candidate classification is a judgment about that entity; it is not a direct relation to a pattern edition, criterion episteme, evaluator, evidence set, or status value.

For the candidate, recover six distinct constructive components. Do not let one component stand in for another:

  1. Candidate. Identify one U.Entity under its direct identity rule.
  2. Constituents. Identify the entities claimed to constitute this candidate. Nearby entities, members of a set, sampled points, and arbitrary slices are not constituents by inclusion or wording.
  3. Constructive part relations and assembly. Recover the obtaining part-relation occurrences under their direct patterns and the assembly by which those constituents compose this candidate. A list, diagram, or shared boundary does not establish those relations.
  4. Reidentification rule. State the rule that distinguishes this whole and says which constituent, relation, boundary, or phase changes preserve or end its identity.
  5. Composition-grounded whole-level characteristic. Recover at least one characteristic whose value or state is produced or sustained by the composition and is not attributable to one constituent alone.
  6. Possible participation in a larger constructive assembly. Recover the candidate’s actual boundary, interfaces, relevant characteristics, and identity-preservation conditions. Those facts must satisfy the applicability and compatibility conditions of at least one governed larger-assembly construction method or rule under which an admissible construction would include this candidate as a constituent while preserving its identity. An episteme may describe that method or state that rule and its conditions.

Name the already admitted holon kind and its direct kind-specific pattern separately from those six components. The candidate satisfies the A.1 criterion when all six world-side components hold and any kind-specific condition is satisfied; it fails when a required component or condition does not hold. Satisfaction or failure does not vary with current evidence availability or evaluator access. Replacing a constituent or part-relation occurrence preserves the same holon only when the reidentification rule admits that change. An unassembled collection fails even when a project card calls it a holon.

Dated classification work belongs to A.15.1. When a reusable typed recognition-evaluation operation is current, A.6.1 governs its declared arguments and result plus the actual application bindings. The evaluation returns true when its governed inputs determine satisfaction, false when they determine failure, and unknown when missing evidence or an unavailable dependency prevents either determination. unknown is an evaluation result, not a third candidate state: the same candidate can satisfy or fail the criterion while the current evaluation remains unable to determine which.

When another use must inspect or cite the judgment, identify an optional C.2.1 classification-assertion or evaluation-result episteme whose EntityOfConcern is the candidate. Its claim content names the admitted kind, the A.1 criterion, the constituent and part-relation facts, reidentification rule, whole-level characteristic, candidate-side compatibility facts, construction method or rule and its applicable conditions, evaluation frame, and true | false | unknown judgment needed by that use.

A person or system performing the receiving work separately decides whether to rely, decline to rely, defer, or reopen. Evidence and assurance relations support or warrant assertion claim content. Use G.11 to test whether the selected assertion edition is current. B.2 addresses the different question whether the existing whole is no longer the right EntityOfConcern for a receiving use. A.1 recognition alone does not establish a B.2 whole-reidentification claim or select B.2.

In ordinary use, stop after naming the entity being evaluated, six constructive components, admitted kind, kind-specific condition, and resulting judgment needed by the task. Materialize a classification assertion only when a downstream task must inspect or cite that judgment. If a system-thinking long map consumes the result, pass only this recognition result and apply A.1.STM; do not add external value, project designation, architecture, Work, or network selection to the A.1 criterion.

Historical read path. Older FPF writing may use super-holon. Under F.13, read it either as the larger system of which S is an admitted part under one part-whole relation, or as the rejected inference that interaction, change, control, teaching, measurement, or repair alone makes such containment obtain. Current FPF does not use that historical expression as a head. Environment means the external referents and crossing relations made relevant by a stated system delimitation and use; a medium is named as such only when that medium is the subject. Neither denotes a generic Context or identifies a containing whole. A containing-system claim names the larger system and the obtaining part-whole relation.

A.1:4.3 - Admitted Holon Kinds

Current accepted holon-kind examples are:

  • U.System, used here for an acting physical or operational holon;
  • U.Episteme, used here only for a non-agentive claim-bearing holon, identified under C.2.1 by claim content, EntityOfConcern, and effective ReferenceScheme, with constitution, empirical grounding, and edition kept as distinct direct relations;
  • U.Work, admitted under A.15.1 for a dated 4D occurrence holon;
  • U.Discipline, defined in C.20 as a field-level practice-and-knowledge holon;
  • U.Method, defined in A.3.1, with method-composition patterns such as B.1.5 defining how submethods compose into a whole method across levels.

A project-local holon classification names its concrete C.3 U.Kind, the A.1 criterion, any kind-specific criterion, and the direct patterns for the construction facts it uses. A proposed public U.* holon kind first passes E.24.UK and gains one subject pattern. Before relying on a claim that depends on the candidate being a holon, recover its candidate-side criterion.

Candidate recognition is decided by the six candidate-side constructive components in A.1:4.2, not by agentivity, wording, evidence availability, or a B.2 whole-reidentification result. Grounding work selects the participating objects from the surrounding practice or world, fixes their boundaries, identifies constituents and part relations, recovers the assembly and reidentification rule, and tests the resulting whole-level characteristic and larger-assembly compatibility. Relations may arrange, constrain, assign, qualify, or describe constituents; those relations do not become constituents by that fact.

U.Method and a local system-role kind are not decided by whether they act. U.Episteme already shows that a non-agentive object can be a holon. U.Method is a non-agentive holon kind: submethods can compose into whole methods with whole-level preconditions, effects, invariants, interfaces, constraints, and assurance hooks, and a whole method can participate in a larger method. A step label or step description is not a method part by label: first recover a U.Method submethod rather than a method-description node, order relation, work-plan item, or work occurrence.

A local system-role kind is instead a local U.Kind whose candidates are U.System values; it is neither a public root U-kind nor a holon kind by kind identity. C.3 recovers it through the candidate domain, operative condition for a stable, assignable, work-facing contribution, intended member/non-member boundary, and continuity rule. A practice or source reference only locates or prompts comparison of the definition; the current KindSignature states the candidate-side condition against direct features of the system. Assignment may be one criterion only when that signature says so; assignment alone does not confer family-wide membership.

The assignment occurrence, assignment state, capability, responsibility, permission, commitment, obligation, method participation, and SystemRoleKindRelationStructure remain neighboring objects or relations rather than parts of the kind.

A.1:4.4 - U.System

U.System is an acting physical or operational holon kind. It can participate in system-role assignments, capability relations, method enactment, mechanism realization, work occurrences, transformations, functioning relations, and responsibility-bearing claims when their direct patterns make those claims current.

Its kind-specific condition is acting eligibility: the recognized whole has an actual physical or operational organization through which it can causally participate in work or transformation while preserving its identity. Capability evidence or actual participation can support a classification assertion; a U.SystemRoleAssignment, work occurrence, or capability relation does not create the system by participation alone.

Keep those relations separate:

  • Use A.2.1 to state the U.SystemRoleAssignment occurrence whose HolderSystemSlot is filled by the system.
  • A.2.2 governs capability claims about that system.
  • A.3.1, A.3.2, and the mechanism family govern method, method description, and mechanism realization.
  • A.15.1 governs independently admitted performed Work; recover its actual performer’s agency basis through A.13, and use F.6 only when precise assignment-bound attribution is needed.
  • A.3.4 governs the bounded transformation; the direct subject-relation pattern defines or constrains the system’s participation in it.
  • Functioning, evidence, assurance, temporal, and dynamics claims remain with their direct patterns.

A.1 introduces no omnibus participation relation over references to all those occurrences. Listing them together in a worked case creates no additional world-side relation. If the selected organization among several direct relations changes an engineering decision, select that organization as U.Structure under A.22 and keep every constituent occurrence under its direct identity. Claim scope, effective reference scheme, and optional model-use structure qualify each dependent assertion only where its direct pattern makes them current.

A.1:4.5 - U.Episteme

U.Episteme is a claim-bearing, non-agentive holon kind. Acting systems can use, cite, publish, represent, structure, compare, interpret, or rely on it through separately governed relations. Work may yield another edition, but changed claim content identifies another episteme under C.2.1 rather than an in-place transformation of the same one.

Use C.2.1 for episteme identity, EpistemeConstitutionRelation, and the direct empirical-grounding and edition relations declared there. Use the neighboring direct patterns for viewpoint, view, claim scope, bounded model use, evidence, publication, source use, carrier, and representation. A.1 only says that an episteme can be treated as a holon when part-whole treatment of the claim-bearing object is current.

A system may decide, approve, perform work, promise, revise, authorize, or bear responsibility through separately governed relations and Work. Classification by a local system-role kind or an assignment to it supplies none of those acts, permissions, commitments, or responsibilities by itself.

A.1:4.6 - Recover Holon Delimitation And Boundary Crossing

When a claim concerns where a holon is delimited, recover the delimitation relation, criterion, or selected structure supplied by the direct holon, mereology, architecture, or domain pattern. Do not force an identity rule, collection-belonging relation, environment relation, selected structure, and boundary condition into one universal relation signature. Those objects have different kinds and predicates.

When one direct relation crosses that delimitation, keep the direct relation occurrence under its own pattern. State the delimited holon, the direct crossing relation, direction, fit, loss, scope, and qualification window that are current for that use. When the claim also needs a semantic correspondence or difference between two F.17 local senses from different semantic contexts, use F.9 for that Bridge question. A crossing classification does not replace the signal, control, measurement, transformation, source-use, publication-use, evidence-use, coupling, or other direct relation occurrence.

Do not call every boundary an interface. Use interface language only when a governing signature, module, architecture, port, or interface pattern makes interface meaning current.

External holon vocabularies do not admit FPF kinds or establish candidate holonhood by label. Recover the current FPF claim first. Acting-agent and organization claims test the U.System criterion; data, document, and projected-content claims usually use U.Episteme, publication, source-use, evidence, or description rules; process-holon wording uses work, method, work-plan, or transformation rules; portal or traversal wording uses an access, crossing, policy, or evidence relation. A candidate-side holon or system claim passes only when the A.1 criterion is satisfied.

A Markov blanket is not a holon boundary by name. First recover whether the source names accepted local Markov dynamics, a mathematical or probabilistic lens, a holon-delimitation claim, a physical interface module or component, a functional element, a boundary description, or an agency-threshold claim. Apply the rule that defines or tests that recovered claim. The candidate is a holon under A.1 only when its constructive criterion is satisfied; the neighboring delimitation claim does not establish holonhood.

A.1:4.7 - Collections, Collection-As-Whole, And Acting Collectives

A collection becomes a recognized U.System only when it satisfies the constructive and acting-eligibility conditions below.

Start with the claim needed by the task. Use the collection’s own rule and A.14 for membership; the complete six-part A.1 test for a possible holon; and the additional acting-eligibility condition for a collective System. Use C.13 for a construction account of already established belonging, C.16 for a whole-level characteristic, and B.3.5 only for a named assurance use. B.2 addresses the separate whole-reidentification question.

An acting collective must satisfy all six A.1 components and have an actual physical or operational organization through which it can causally participate in work or transformation while preserving its identity. Assignment, capability, method and performed-Work claims require their own bases under the direct patterns in section 4.4. If only collection membership is established, state that collection claim; if missing evidence prevents a requested System classification, the evaluation result is unknown under section 4.2.

A.1:4.8 - Constructional Grounding

A.1 governs constructive holon recognition. Part-relation patterns govern part relations; C.13 governs constructional grounding; E.24.UK governs public-kind admission.

Use A.14 and the direct relation patterns to identify collection belonging and any independently obtaining component, portion, aspect, phase, constituent, or other constructive part relation. Use C.13 to report how already grounded facts form a collection, assemble the candidate, or distinguish an aspect. If a C.13 trace is materialized, it is a C.2.1 episteme about that construction. Use B.3.5 only when a named assurance use elects its profile.

Systems, epistemes, methods, dated work occurrences, and disciplines are admitted holon kinds under their direct patterns. C.13 may describe their construction only after those patterns identify the parts and whole-forming relations for the candidate. A selected U.Structure, including BoundedModelUseStructure, organizes already identified relations for a use; selecting or drawing that structure does not establish constructive part-whole relations or that its constituents form a holon; it supplies neither acting eligibility nor a B.2 whole-reidentification result.

FPF avoids unrestricted composition. A set of nearby objects, graph, diagram, system-role-kind or assignment bundle, method algebra, work breakdown, or source table does not become a holon merely because it can be listed or represented as a whole. Several independently identified transformations likewise do not become parts of one composite transformation from shared timing, a changed referent, a method or work decomposition, or a C.13 trace. When the work requires positive transformation composition or transformation holonhood and no direct composition pattern supplies the candidate whole, constituents, contribution, compatibility, and reidentification rule, retain the blocker and stop before A.1 classification.

A.1:4.9 - Slot Filling Does Not Create A Kind

A system that fills HolderSystemSlot of a U.SystemRoleAssignment occurrence remains a system. An episteme that participates as the EntityOfConcern in an EpistemeConstitutionRelation remains an episteme. A system can participate in a transformation through a governed direct relation without thereby becoming a part of the changed holon or the larger whole containing it. A holon that participates as the EntityOfConcern of a structure-description episteme remains that holon rather than becoming the description.

The SlotSpec belongs to the direct relation declaration. Its SlotKind names the local participant slot; its ValueKind constrains admissible fillers. Filling that slot establishes neither a new intrinsic kind for the filler nor a new relation occurrence unless the direct obtaining predicate and identity rule are also satisfied. Use the subject pattern before introducing any durable kind name.

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

A.1:5.1 - Pump As Acting System

Use this illustrative engineering case to decide whether Pump #37 qualifies as a U.System. Take the following construction and operating facts as the case inputs:

  • Pump #37 is the assembly initially built from casing C37, impeller I37, seal S37, motor M37, inlet flange FI37, and outlet flange FO37. Each is a physical component of that pump under A.14 ComponentOf.
  • C37 encloses I37; M37 is bolted to C37 and its shaft is coupled to I37; S37 seals the shaft entry; FI37 and FO37 are fastened to C37 and open into its water passage. These obtaining fastening, enclosure, coupling, sealing, and connection relations assemble the named components as one pump.
  • The case’s installed-assembly reidentification rule preserves Pump #37 through shutdown, temporary disassembly, and replacement of S37 by S38 with the same mating geometry and operating limits, provided C37 is retained and the assembly and its inlet/outlet boundaries are restored before return to service. Replacing C37 or permanently dismantling the assembly ends Pump #37 under this rule.
  • With water at 20 °C and a 400 V, 50 Hz supply, this assembly sustains a flow of 10 m³/h against a pressure rise of 200 kPa. The coupled motor, impeller, casing, and sealed passage produce that whole-pump response; no one component supplies it alone.
  • U.System is already an admitted public U-kind in FPF; E.24.UK governs admission of public U-kinds. The pump’s physical organization can cause the stated water-moving change while retaining its identity, supplying the kind-specific acting-eligibility condition.

For the larger-assembly test, CW-Install-1 is the case’s governed plant-installation rule. It integrates the intact pump as the replaceable circulation unit of CoolingLoop-2: bolt its feet to the loop support, connect FI37 to the loop’s return port and FO37 to its supply port, and connect M37 to the electrical supply. Compare its applicability conditions with the remaining case facts:

CW-Install-1 conditionPump #37 fact
Each water port must mate with a 50 mm bore flange having four 12 mm bolt holes on a 90 mm bolt circle.FI37 and FO37 each have that bore and hole geometry.
The support accepts four mounting holes on a 120 × 180 mm rectangle and a pump mass of at most 40 kg.The pump’s feet have that hole pattern; the intact pump has a mass of 35 kg.
With the available 400 V, 50 Hz supply and water at 20 °C, the pump must sustain at least 8 m³/h against a pressure rise of 200 kPa.The stated whole-pump response is 10 m³/h at that pressure rise under those conditions.
Installation must retain the casing, internal assembly, and pump-side inlet/outlet boundaries.The rule uses the existing mounting holes and flanges; it changes only the external attachments, preserving Pump #37 under the stated reidentification rule.

These facts supply one larger-assembly witness: CW-Install-1’s conditions are satisfied and its construction preserves the pump as a constituent. Together with the identified candidate, components, assembly, reidentification rule, whole-level response, and acting eligibility, they establish the A.1 criterion for this illustrative U.System case. A classification evaluation given these inputs returns true; a separate C.2.1 assertion may state that result.

The candidate-side facts and the available evaluation inputs remain distinct. If the mass fact is withheld and no other input resolves the compatibility question, evaluation returns unknown; withholding that fact changes neither the pump nor whether the criterion holds. Replacing S37 by the specified S38 preserves Pump #37 through the admitted maintenance phase. Replacing C37 instead requires identifying the resulting assembly as another candidate under this case’s rule.

If the intact candidate instead has a mass of 45 kg, CW-Install-1 cannot supply the sixth component because its support limit is 40 kg. A coupling, load-envelope, or boundary-interface violation likewise defeats that installation rule even when the drawing and rule-description episteme are current. Failure of this one rule does not settle the existential larger-assembly condition: the candidate fails that component only if none of the governed larger-assembly constructions has conditions satisfied by its actual facts. Evaluation returns false when its inputs determine that failure, and unknown when the searched methods or available facts do not settle it. Renaming or republishing the cited criterion pattern does not change Pump #37 or those facts; any change to the episteme’s designation, edition, or currentness remains separately governed.

Separate direct relations then state that Pump #37 fills the holder-system slot of its cooling-water circulation U.SystemRoleAssignment, has a flow-rate capability envelope, and participates in the water-moving transformation.

A separate inspection account may identify WO-1842 : U.Work, but the cooling-water assignment does not make Pump #37 its performer: the inspector System must have its own A.13 core, the Work must be independently admitted under A.15.1, and F.6 is added only if that account needs precise assignment-bound attribution through the inspector’s same obtaining assignment. Pump #37 remains the inspected or participating subject unless another direct performer basis establishes otherwise.

No omnibus participation or candidate-classification relation is added. The pump can have selected structures; its maintenance model may participate in a separately selected BoundedModelUseStructure, but that structure neither identifies the pump nor makes it a holon.

A.1:5.2 - Scientific Theory As Episteme Holon

This schematic illustration concerns Newtonian gravitation in one selected edition, first identified as a C.2.1 U.Episteme candidate. Its actual claim-bearing constitution can satisfy the A.1 criterion for the already admitted U.Episteme kind when the following facts obtain:

  • law, definition, derivation, diagram, exercise, and evidence-relation epistemes are the candidate constituents;
  • claim-composition and episteme part relations organize those constituents as one governed claim-bearing whole;
  • C.2.1 identifies this theory episteme by its claim content, EntityOfConcern, and effective ReferenceScheme; a change to any of these identifies another episteme. Historical continuation between the earlier and later epistemes requires a separate EpistemeEditionRelation under an applicable edition-continuity rule;
  • inferential and explanatory characteristics arise from the organized claim-bearing whole rather than from one constituent;
  • its actual inferential interfaces, effective reference scheme, applicability conditions, and identity-preservation conditions satisfy the applicability and compatibility conditions of at least one governed method for composing it as a constituent of a larger explanatory or educational episteme;
  • U.Episteme is already an admitted public U-kind in FPF; E.24.UK governs admission of public U-kinds, while C.2.1 supplies the kind-specific constitution condition.

For a theory, supply the constituent identities and an independently obtaining direct episteme-part or claim-composition predicate before drawing the recognition conclusion (C.13:5.3). A textbook publication can make this edition available, but the publication form and the episteme that describes the composition method do not create the theory’s compatibility or holonhood. Classification work may evaluate the criterion and a separate C.2.1 assertion may state the result; evidence, warrant, edition currentness, receiving reliance, and any B.2 whole-reidentification question remain separately governed.

A system under a U.SystemRoleAssignment may explain, publish, compare, or use this episteme through separately governed Work and relation occurrences; the assignment alone establishes none of those acts. Revision Work yields another episteme, with any edition relation tested separately.

A.1:5.3 - Fleet As Collection Or Acting Collective

A fleet register supports the claim that a vehicle belongs to the fleet only under its registration rule. In the register-only case the fleet is not thereby established as a holon: no vehicle-to-whole assembly or composition-grounded characteristic is claimed. Fleet availability is a separate collection characteristic. A fleet-coordination organization that coordinates vehicles, drivers, rules, and Work can be an acting collective U.System only after all six A.1 components, including its constructive relations and assembly, have been recovered.

If a source says “the fleet responded”, determine whether it reports actions of individual vehicles, Work by the fleet-coordination System, or a collection-level characteristic; identify the actual performers when Work is claimed.

A.1:5.4 - Lathe Changing A Workpiece

A lathe can change a workpiece during manufacturing without thereby becoming a part of the workpiece or the larger whole containing it.

Use A.3.4 to identify the bounded transformation from the changed referent, extent, boundary conditions, actual change facts, and continuity rule. Use the direct subject patterns for the lathe’s participation, method, dated work, work-to-change facts, and evidence. Use A.14 or C.13 for part-whole only when a grounded part relation independently obtains.

A.1:5.5 - Stop Before A Whole Is Constructed

A pallet holding an unconnected pump, motor, baseframe, and manifold is a collection of entities. The list and physical proximity do not supply the fastening, coupling, enclosure, connection, assembly, or reidentification facts needed to recognize a skid holon. A construction drawing is an episteme about a possible assembly.

A selected BoundedModelUseStructure may organize model-applicability, delimitation, maintenance, and crossing relations for an engineering use. It remains dependent U.Structure; selecting it, naming it, or drawing it supplies no part relations, whole-level characteristic, acting eligibility, or B.2 whole reidentification.

Mounting, wiring, and fluid-connection changes may each be U.Transformation occurrences. Their participation in one work episode or one flow description does not identify a composite transformation. Without a direct transformation-composition governor, retain the separate changes and stop before transformation parthood, composite identity, or A.1 holon recognition. This stop does not say that the changes are atomic or have no finer parts.

A.1:6 - Bias-Annotation

Relevant lenses: Onto, Arch, Epist, Prag, Gov, Did.

This pattern intentionally resists:

  • system-bias: treating all objects as acting physical systems;
  • episteme-agent bias: assigning work, authority, or decision to claim-bearing epistemes;
  • collection-bias: treating any collection as an acting collective;
  • boundary-bias: treating boundary words, diagrams, folders, or sections as holon delimitation by appearance;
  • interaction-bias: using one word for transformation, signal, source use, publication use, evidence relation, probe relation, and control relation;
  • math-lens drift: treating graph, algebra, matrix, tuple, or embedding expressions as the ontology-side structure by spelling;
  • publication-form bias: treating a document, dashboard, model, register, or digital twin as the holon it describes.

A.1:7 - Conformance Checklist

CheckConformance condition
CC-A1-1The candidate is first individuated as U.Entity; the public holon kind is already admitted in FPF before the candidate is tested against A.1. E.24.UK governs admission of public U-kinds; A.1 does not repeat that decision or require its result as a candidate-test input.
CC-A1-2A current recognition use separately recovers the candidate, constituents, constructive part-relation occurrences and assembly, reidentification rule, composition-grounded whole-level characteristic, and candidate-side compatibility with an applicable governed larger-assembly construction method or rule; it then names the already admitted holon kind and its direct kind-specific condition.
CC-A1-3A proposed new public holon kind first passes E.24.UK; its direct pattern then states the kind-specific membership condition without changing the common A.1 criterion for candidates.
CC-A1-4Candidate classification is not reified as a status relation. World-side satisfaction or failure, classification work, `true
CC-A1-5System-role-kind classification, U.SystemRoleAssignment, capability, method, work, transformation, functioning, evidence, and temporal claims remain separate; their reference bundle is not asserted as another occurrence.
CC-A1-6U.Episteme is non-agentive. Systems may publish, cite, use, or perform revision Work concerning epistemes, but changed claim content identifies another episteme and any edition relation is separately governed.
CC-A1-7Collection belonging under the collection’s own rule, a possible holon, an acting collective System, a whole-level characteristic, and B.2 whole reidentification are kept distinct.
CC-A1-8Boundary wording recovers a delimitation relation, criterion, or selected structure from its direct pattern; crossing wording preserves the crossing relation occurrence without minting universal delimitation or crossing relation kinds. F.9 applies when the claim needs a semantic correspondence or difference between two F.17 local senses from different semantic contexts.
CC-A1-9Changing, controlling, teaching, measuring, or repairing another holon does not make that holon a part of the acting system; any actual containing-whole claim names a separately grounded part-whole relation.
CC-A1-10A.14 and the direct part-relation patterns identify obtaining parthood; C.13 may ground an assembly only from those facts and does not create them; use B.3.5 only for a named assurance use.
CC-A1-11Publication forms, construction traces, and descriptions of holons remain distinct from the holons and world-side construction facts they describe.
CC-A1-12A candidate U.System, U.Episteme, U.Method, U.Work, or U.Discipline may use constructive grounding only after its direct patterns identify parts and whole-forming relations; a selected dependent U.Structure is not a holon by selection or name.
CC-A1-13Several actual changes are not classified as one composite transformation or holon without a direct transformation-composition governor; a missing governor neither proves composition nor proves atomism.

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

Anti-patternSymptomRepair
System as universal rootA theory, document, model, source, or dashboard receives physical system properties.Re-type as U.Episteme, publication, source-use object, or another direct object before using system claims.
Document edited itselfA model, theory, or document is said to perform a revision.Name the revising U.System. If the account claims revision Work, first recover that System’s A.13 core—local agential system-role kind and criterion, classification, and obtaining assignment with the required scope, situation, and window—then use A.15.1 to admit the Work. A short account may omit restating these facts only when they remain recoverable; add F.6 only for precise assignment-bound attribution. Changed claim content identifies another U.Episteme; test any edition relation separately, and distinguish publication or carrier changes under their own patterns.
Collection as actorA list, batch, pool, fleet, or community is said to decide or perform Work.Identify the Systems claimed to decide or perform Work. If the collection is claimed to act as one System, establish its constructive recognition and acting eligibility; retain a mere membership or collection-characteristic claim at that scope.
Interaction as one umbrellaSignal, source use, publication use, transformation, measurement, and control are all called interaction.Recover the direct relation; use F.9 for a needed semantic correspondence or difference between two local senses from different semantic contexts, and A.3.4 when bounded change is current.
Omnibus participation relationReferences to system-role-kind classification or assignment, capability, method, work, transformation, evidence, and time are packed into one additional relation-shaped record.Keep the direct relation occurrences separate; select their organization as U.Structure only when that organization changes the receiving use.
Boundary by drawingA box, folder, section, dashboard view, or diagram is treated as the holon boundary.Recover the delimitation relation, criterion, or selected structure from its direct pattern; keep the drawing as a description or view.
Architecture without holonA selected structure is discussed without the holon whose structure is selected.Use A.1 to name the holon, then A.22 and C.30 for selected structure and architecture.

A.1:9 - Consequences

Positive consequences:

  • FPF can talk about physical systems, organizations, documents, theories, models, work occurrences, disciplines, research programs, and selected structures without making them all systems or holons.
  • Acting work stays attached to systems in roles.
  • Epistemes can be described, compared, published, and relied on; revision Work yields another episteme when claim content changes.
  • Architecture and selected-structure claims gain a grounding holon.
  • Collection-as-whole and acting collective claims become inspectable instead of lexical.

Costs:

  • Practitioners pay the cost of replacing umbrella uses of “system”, “boundary”, “interaction”, “level”, “emergence”, and “collection” with governed claims.
  • A reviewable holon-recognition claim states the constituents, construction, reidentification, larger-assembly compatibility, whole-level characteristic, admitted kind, and subject pattern on which it relies.
  • Some familiar sentences need repair: “the document decided” becomes a claim about the deciding U.System, the direct decision relation or admitted Work, and an episteme or publication. A Work claim requires the A.13 performer core even when a short account leaves it recoverable rather than restating it; an ordinary direct decision or change account stays with its subject pattern.

A.1:10 - Rationale

A.1 prevents category errors by separating individuation, constructive part-whole recognition, acting eligibility, and claim-bearing. U.Entity gives the minimal referenceable object. U.Holon adds six separately recoverable constructive components: candidate, constituents, part-relation occurrences and assembly, reidentification, a composition-grounded whole-level characteristic, and compatible possible participation in a governed larger assembly. U.System adds acting eligibility. U.Episteme adds claim-bearing structure without agentivity. U.Work and U.Discipline are holon-kind examples only through their subject patterns; BoundedModelUseStructure is selected U.Structure, not another holon kind.

The recognition base cannot depend on a prior context object without recursion. It begins with the candidate and world-side construction facts. Public-kind admission is the separate one-time E.24.UK decision. Classification work evaluates what its available inputs establish about those facts and may return true, false, or unknown; the evaluation and its record remain distinct from the construction and identity being judged.

This also prevents ontology duplication. A theory under concern, a theory description, a publication of that description, and the system that edits the publication can all be named without turning the filling of one participant slot into a new kind. Architecture likewise starts from the holon recognized under an admitted kind whose selected structures matter; diagrams and structure descriptions remain epistemes.

The constructional stance is conservative: FPF avoids unrestricted composition and uses A.14 and C.13 before a part-whole claim is relied on for another claim or work occurrence; B.3.5 is added only when a named assurance use elects its profile. This keeps holonic thinking useful without letting every collection, expression, graph, selected structure, or source label become a holon.

A.1:11 - SoTA-Echoing

A.1 draws on current constructional-ontology, applied-foundational-ontology, and physics-side construction traditions for different questions. None of these sources admits an FPF kind, establishes a candidate’s construction, or replaces the direct patterns that define or constrain part relations, work, evidence, or publication.

Current source and practice answerUse in A.1Adoption status and blocked overread
Florio and Linnebo, Introduction to Constructional Ontology, 2024, distinguish constructors, constructor inputs, constructional processes, and the identity consequences of construction choices.A.1 requires constituents, obtaining constructive part relations, assembly, reidentification, and a composition-grounded whole-level characteristic before recognizing a candidate whole.Adapt. A.1 adopts construction-sensitive identity but keeps public-kind admission with E.24.UK and direct subject facts with their own patterns; a construction description or selected constructor does not make the candidate a holon.
Borgo and Righetti, “Towards Applied Constructional Ontology”, FOIS 2025, show that applying constructional ontology still requires explicit choices about mereology, dependence, and identity.A.1 requires A.14 for part-relation vocabulary and C.13 for constructive grounding, preserves a separate reidentification rule, and uses B.3.5 only when assurance grounding is current.Adopt. The demand for explicit applied choices is adopted; A.1 rejects the shortcut that a constructional-ontology label already settles constituents, parthood, whole identity, or warrant.
Deutsch, Constructor Theory, 2012, and Deutsch and Marletto, “Constructor theory of time”, 2025, treat possible transformations through substrate attributes and constructor conditions rather than through a written task alone.A.1’s larger-assembly component requires the candidate’s actual boundary, interfaces, relevant characteristics, and identity-preservation conditions to satisfy the applicability and compatibility conditions of a governed construction method or rule.Adapt. The modal discipline is adopted for candidate recognition; a task, rule episteme, drawing, or evidence item does not create applicability, compatibility, possibility, work, or assembly.
Partridge, BORO Ontology, C-FORS 2025, supplies a current 4D extensional and unrestricted-composition comparator.A.1 makes identity through change and actual construction explicit, while using A.14 and C.13 before relying on a part-whole claim.Reject wholesale; retain the identity test. A.1 rejects unrestricted composition and import of BORO’s category system, while retaining pressure to state the candidate, extent-sensitive reidentification, and construction facts.

For the Pump #37 and scientific-theory cases in A.1:5, the practical consequence is the same: recover the candidate and its subject-side construction first; use a governed method or rule only to test larger-assembly compatibility; keep evaluation, evidence, assertion, description, and publication as separately governed neighboring objects.

A.1:12 - Relations

  • A.1.RI develops reidentification across observations and supplies a supported identifying result or the alternatives still relevant to use.

  • Builds on: E.24.UK for one-time public U-kind admission, A.14 and C.13 for part relations and constructive assembly, and B.3.5 when Working-Model assurance grounding is current.

  • Coordinates with: A.1.STM after recognition when the System’s intended use, required functioning and construction, and work of its creators still need to be connected; A.15.1 for dated classification work; A.6.1 for a current typed evaluation operation and actual bindings; C.2.1 for classification-assertion or evaluation-result episteme identity; A.10 and B.3 for evidence and warrant; G.11 for assertion-edition currentness; B.2 for the separate whole-reidentification question; A.1.1 for bounded model-use structure; A.22 for selected structure; C.30 for architecture; A.3.4 for transformation; C.20 for discipline; and E.10.ARCH for wording-use restoration.

  • Applied by: Use A.1.SCR when a practitioner must find the acting or changed System for a decision that depends on systemhood. After a proposed or observed focus is current, use A.1.CSD when the next question is which other Systems may undergo relevant changes. Use A.1.STM when the practitioner still needs to connect the recognized System’s intended use, required functioning and construction, and the work of its creators. For a direct Work, Method, capability, structure, episteme, or relation question, apply the pattern that defines or tests that claim instead of invoking this complete criterion.

  • Used by: patterns that need a recognized holon, an already admitted holon kind, an acting system, a non-agentive episteme, a grounded part-whole claim, a collection-versus-collective distinction, a delimitation relation, or a boundary-crossing relation.

A.1:End

A.1.RI - Reidentifying an Object across Observations

Type: Method pattern Status: Stable Normativity: Normative

A.1.RI:1 - Problem frame

Use this pattern when the next calculation or action depends on whether observations concern the same continuing object, and the available identification does not yet settle that question. A moving object appears again after an observation gap. Two tracks compete for one detection. A process number appears in reports made before and after a restart.

The subject practice supplies what counts as continuation of that object: permitted motion, a process lifetime, a material continuity rule or another applicable criterion. The Method constructs and compares the connections that the observations and those rules allow.

First useful move. Name the object whose continuation matters and the use that depends on it. Then examine one available observation for a feature that distinguishes continuation from a live competing account. For a process run, a changed start time can settle a question that an unchanged process number leaves open.

The result is an identification or exclusion supported by the available premises, or the remaining alternatives relevant to the next use. It can be conditional on a stated motion or observation account. An adequate existing identification can be used directly.

This Method assumes that the object-continuation criterion and the relevant subject rules can be recovered. Constructing a new criterion, motion theory, sensor model or tracking algorithm is further work when one of those contributions is missing. A question about an aggregate quantity may be answerable without deciding which observation belongs to which object.

A.1.RI:2 - Problem

Observations describe what was found at particular occasions and under particular conditions. They can differ while concerning one object, or resemble one another while concerning different objects. A repeated name, location or appearance therefore has the identifying force supplied by the subject rules and observation conditions.

Pairwise plausible connections can also conflict. Under a model in which each object is detected once, assigning the same later detection to two earlier objects fails the joint account. Conversely, several complete associations may all satisfy the available constraints.

The practitioner needs to determine what the observations resolve and carry that result into the next calculation or action.

A.1.RI:3 - Forces

ForceTension
Continuation and changeAn object can change while continuing; the relevant criterion determines which changes matter.
Local resemblance and joint compatibilityA good pairwise match can prevent a coherent association of the other observations.
Observation gaps and available rulesRules can connect separated observations while leaving more than one connection possible.
Ranked choice and resolved identificationA preferred hypothesis may support an action even when the observations have not excluded its rivals.
Information and costAnother observation can distinguish alternatives, but the receiving use may already be possible.
General Method and subject constructionThe association procedure is reusable; its motion, lifetime and observation rules are subject-specific.

A.1.RI:4 - Solution

Recover the continuation question, construct the relevant associations under the subject rules, test their joint compatibility and use the distinctions they support.

Name the continuing object → recover observations and rules → construct competing connections → test them together → resolve what the use needs → continue or reopen.

A.1.RI:4.1 - Recover the continuation question

State which object the observations may concern and what would count as its continuation through the interval or change. A continuing software service, one process run and one execution of a requested job have different boundaries. Choose the object required by the question.

Recover the relevant temporal and contextual scope. Coordinates need a frame; a local process number needs the system and naming scope in which it was issued. If the observations use different references, establish their correspondence before comparing values.

State the receiving use. Estimating one object’s displacement needs its association across observations. Estimating the mean position of a fixed observed population can leave those associations unresolved.

A.1.RI:4.2 - Separate observations, rules and assumptions

Recover the observations already available, their occasions and the limitations that matter to this question. Distinguish the observed indication from a position, identity or event inferred through it. C.16.MR and C.16.IR help when the measurement interpretation itself remains unresolved.

Recover the subject rules used to connect those observations: allowed changes, motion bounds, lifecycle events or other continuity conditions. Include the observation conditions needed by the connection. “Each object was observed once” and “the set of objects stayed fixed” are substantive premises when they make the association one-to-one.

Keep an assumed rule available as an assumption. A conclusion derived under it can be useful while a later question requires a different or better-supported account. Use the assurance and information work appropriate to that receiving question.

A.1.RI:4.3 - Construct the materially different connections

Construct the associations still possible under the available account. A connection states which observations concern the continuing object and how the subject rules permit the intervening change. In a small finite case, listing the alternatives can be enough. Larger cases can use the domain’s assignment, constraint or probabilistic Methods.

Include a missed observation, new object, ended object or reused identifier when the observed situation and subject rules make that alternative live. For example, a process can terminate between reports and its number can later be reused. A fixed two-object motion exercise can instead supply persistence and complete detection as premises.

When several objects share observations, construct complete associations for the relevant group. Retain the conditions linking their choices. For independent point motions a pair of admissible paths may suffice; interacting bodies can require a joint evolution satisfying their interactions.

A.1.RI:4.4 - Test compatibility and the strength of the conclusion

Apply the subject constraints to each materially different connection. Construct a permitted realization where feasibility matters, or identify a violated condition that excludes it. A numerical solver can help perform this step; its returned result still needs the intended observation and subject interpretation.

Compare the surviving alternatives at the distinction required by the receiving use:

  • When the supported premises and considered alternatives determine the association, use that conditional identification.
  • When they exclude a proposed association, remove it from the current account.
  • When materially different associations remain, retain the unresolved distinction.
  • When none fits, inspect the failed observation, rule or assumption before extending the same account.

A best score answers the ranking question defined by that score. If the work uses the top-ranked association provisionally, carry its selection rule and relevant uncertainty into that use. Claiming that the observations uniquely determine it requires the corresponding exclusion of alternatives.

A.1.RI:4.5 - Resolve only the distinction the next use needs

Try the receiving calculation or decision on the surviving alternatives. If each gives the needed result, continue with that result and leave the unused identity question open. Section :5.1 obtains the same mean position under both surviving associations.

If the difference changes the next action, determine which available fact, observation or subject constraint would distinguish the alternatives. Prefer an already available discriminator. Obtain more information when its likely contribution warrants its cost and delay; C.11.DUA supplies that choice.

Some work permits a provisional action with the unresolved risk. State what that action assumes and what observation would call for correction. Work that requires the identity to be settled must return to the missing identifying contribution. An unresolved identification need not stop other work whose result is unaffected.

A.1.RI:4.6 - Carry the result into use and revise it locally

Use the association to join the relevant observations, calculate the change or address the continuing object. Keep the premises and unresolved alternatives that can change that use.

Reopen the affected connection when a new observation, changed rule or detected observation error invalidates it. Preserve associations and calculations whose basis still holds. B.5.RR helps carry a changed premise through dependent reasoning.

The observations retain their own occasions and claims after their subject is identified. C.2.1 governs observation epistemes and their identities. For a use that needs a separately designated relation occurrence, apply A.6.REL using the direct relation pattern’s predicate and occurrence-identity rule.

A.1.RI:5 - Archetypal Grounding

A.1.RI:5.1 - Associate two moving objects and retain an unresolved alternative

Consider two persistent point objects with independent motion on one axis; their paths may cross. Each object is observed once at each end of a one-second interval. Positions are assumed known in one common frame. Initially A is at 0 cm and B at 10 cm. Later R is at 1 cm and S at 9 cm.

The motion account limits speed to 2 cm/s. Construct the complete associations:

AssociationRequired displacement magnitudesResult under the speed bound
A to R; B to S1 cm eachAdmissible; the two straight paths give a joint realization.
A to S; B to R9 cm eachExcluded; each exceeds the permitted displacement.

Under these premises, R observes the continuing A and S the continuing B. A’s displacement is +1 cm and B’s is -1 cm.

Now allow speed up to 10 cm/s. Both associations have admissible straight paths. The observations leave A’s displacement as either +1 or +9 cm; choosing the shorter path adds a preference absent from the speed-bound premise.

Suppose the next question is instead the mean position of these two objects. It was 5 cm and is still 5 cm under both associations. That calculation can proceed without another observation. If a following action must address A individually, look for a discriminator that matters to that action or use an explicitly permitted provisional association.

If the motion premise changes again to a bound below 1 cm/s, neither complete association fits. Reconsider the bound or the observation account before asserting an identification.

A.1.RI:5.2 - Test associations together

Keep the one-second, independent, persistent-point and complete-detection premises. Initially A is at 0 cm and B at 1 cm; later R is at 2 cm and S at 3 cm. Each displacement is at most 2 cm.

The admissible pairs are A-R, B-R and B-S. B’s nearest detection is R. Assigning it first leaves A without a permitted observation. The joint association A-R with B-S satisfies every constraint and uses each later observation once. It is the only complete association under these premises.

The common Method contributes the joint comparison. The supplied motion bound and complete-detection rule determine which associations it tests. If missed or repeated detections become possible, revise those premises and reconstruct the affected alternatives.

A.1.RI:5.3 - Separate a process run from a reused number

An operator wants to compare resource use in two reports carrying the same process number. The object of interest is one process run. Both reports concern the same machine boot and PID naming scope; their fields are assumed to describe the indicated process consistently.

The first report gives start time 1,000 ticks after boot; the second gives 2,400 ticks. Linux exposes such a start-time field in /proc/pid/stat. The changed start time excludes continuation of the earlier run, despite the repeated number. Keep the two runs’ resource totals separate; subtracting the earlier total from the later one would not measure one run’s interval use.

If the reports contain only the number and executable name, they can fit either continuation or termination followed by reuse. An available lifecycle event may distinguish them. For ongoing supervision, a retained process reference such as a Linux PID file descriptor can make a fresh number-based inference unnecessary.

This case resolves run continuity. A question about a service continuing through replacement processes uses the service’s own continuation criterion.

A.1.RI:6 - Bias-Annotation

The finite examples favor explicit alternatives and simple constraints. Many real tracking problems require distributions, approximate inference or decisions under unresolved identity.

The Method can be performed by people, computational agents or coordinated teams. Their observation access and ability to construct alternatives differ.

A.1.RI:7 - Conformance Checklist

  • CC-RI-1 - Continuing object. The subject and its applicable continuation criterion are clear enough for the requested identification.
  • CC-RI-2 - Observation basis. Occasions, references and consequential limitations are distinguished from inferred identities.
  • CC-RI-3 - Subject premises. Allowed changes and observation conditions support the associations being considered.
  • CC-RI-4 - Joint construction. Connections that share observations or subject constraints are tested together.
  • CC-RI-5 - Supported result. The conclusion distinguishes a resolved association, exclusion, retained alternatives and an account that fits none.
  • CC-RI-6 - Affordable continuation. Additional information is sought when resolving the difference can change the receiving use enough to justify its attainable cost and delay.
  • CC-RI-7 - Local revision. Changed observations or premises reopen their dependent connections and results.

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

Failure in these situationsConsequenceRepair
Treat a reused label as uninterrupted object continuityResource totals or actions can be assigned to another run or object.Apply the relevant lifecycle or continuity rule to the available observations.
Accept a plausible pair without its shared constraintsAnother object loses its only possible observation.Compare the complete associations that must hold together.
Report the best-ranked connection as the only possible oneA scoring preference becomes an unsupported identification.Keep the ranking assumption and test alternatives when uniqueness matters.
Require identity resolution for an invariant aggregateAdditional observation delays a result already determined.Evaluate the receiving quantity across the surviving associations.
Treat a failed model as evidence that one convenient association is trueContradictory observations or rules remain hidden in later reasoning.Locate the incompatible premise or observation and repair that contribution.

A.1.RI:9 - Consequences

The practitioner can join observations through an explicit subject construction, distinguish what has been resolved from what remains assumed, and continue calculations that are unaffected by remaining alternatives. A changed premise has a recoverable effect on the identifying result.

The Method depends on the coverage and quality of the available subject account. Constructing and comparing many alternatives can become expensive; domain algorithms and the receiving decision determine how much of that work is worthwhile.

A.1.RI:10 - Architectural Rationale

Object continuity and observation identity answer different questions. Relating two observations to one object can be a substantive result of reasoning: a motion account connects positions, or lifecycle information distinguishes runs. The observations can retain different claims after that result is obtained.

The common construction couples three contributions: a criterion of continuation, constraints connecting observations, and a comparison of the connections relevant to use. Spatial motion supplies one realization. Lifecycle and other subject rules supply different realizations of the same Method.

A.1 supplies the general individuation question. This member develops observation-based reidentification without requiring the object to be recognized as a holon or system. C.2.1 retains the episteme questions, and C.16 supplies measurement interpretation. Their distinct results can participate in one investigation.

A.1.RI:11 - SoTA-Echoing

Practice question and choice. What may observations support about the continuation of an object? Use the domain criterion and observation account to construct and compare relevant associations; retain the distinctions that change the receiving use.

A comparison at the same finite task. In :5.1 with the 10 cm/s bound, selecting the association with the smaller total displacement gives A-R/B-S. Comparing all admissible associations retains that candidate and A-S/B-R. Both methods can use the same four distances and supplied constraints. The selected construction additionally keeps the second complete association and its consequences. This small cost answers whether the speed-bound observations resolve the identity. The minimum-displacement choice supplies a provisional association when the practice accepts that preference; it adds an assumption that the stated motion bound did not provide. The mean-position use needs neither choice nor more observations.

Adapt Andrei Rodin’s Venus Homotopically, §§2-8: observation and a theory-supported connecting construction contribute to identification. The distinction between possible and actual trajectories motivates :4.3-4.4. Its homotopy-type interpretation is one mathematical reconstruction, while the ordinary Method uses whichever subject construction supplies the connection.

Adapt the explicit association operation in Bewley et al., Simple Online and Realtime Tracking, §3.3, as a historical computational comparator. It combines predicted states, an association cost and a globally solved assignment for online tracking. The present synthesis keeps subject constraints, ranked selection and the strength of an identifying conclusion separate. SORT’s benchmark results do not establish the performance of this general Method, and the finite displacement comparison above is an authored case rather than its image-overlap algorithm.

Adopt the relevant lifecycle meanings from the current Linux manuals for process start time and PID file descriptors in :5.3. They supply a nonspatial continuation case and a direct-use alternative to reconstructing identity from repeated numbers.

Reopen the chosen construction when a changed subject or observation model admits a consequential omitted association, an available reference makes reconstruction unnecessary, or a cheaper procedure supplies the distinction needed for use. A new tracking algorithm’s practical gains belong to its stated object, data and decision conditions.

A.1.RI:12 - Relations

  • A.1 supplies general individuation; A.1.SCR can consume an identity result when system recognition is the next question.
  • C.2.1 distinguishes observation-episteme identities and the object they concern.
  • C.16.MR and C.16.IR construct and interpret the measurement relation when indication meanings affect association.
  • A.3.3.TR and A.3.3.PI construct permitted continuations and retain the information needed to predict them.
  • B.5.TU and B.5.TC construct a working theory use and compare accounts when the identifying premises need that work.
  • B.5.RR revises reasoning affected by a changed observation or premise.
  • C.11.DUA selects worthwhile information work for the receiving decision.
  • A.6.REL supplies occurrence individuation when a later use needs a designated identifying relation.

A.1.RI:End

A.1.1 - Bounded Model-Use Structure: Applicability, Use and Expression Coherence (DDD Bounded Context)

Type: Part A architectural ontology pattern Status: Stable Normativity: Normative unless marked informative

A.1.1:0 - Practitioner entry

Working reader and current decision. This pattern is for a domain architect, systems engineer, or service owner deciding whether several facts about one model must be treated together for the next engineering move. The reader starts from that decision—change scope, release scope, ownership boundary, integration boundary, or whether two uses belong together—not from a team name, repository, diagram, or the word context.

Governed object in plain language. A.1.1 governs the selected organization of where one model applies, how it is actually used in assigned Work, and whether concrete expressions still agree with it. The Tech name is BoundedModelUseStructure; the familiar Plain retrieval name is bounded context. It is a U.Structure, not a container for systems, teams, Work, documents, or publications.

First useful move — take the smallest branch.

  1. Name one model edition and one place or thing about which it is used.
  2. Ask what the present decision needs.
    • If applicability alone answers it, recover ModelApplicabilityRelation and stop.
    • If actual use is current, recover the performer through A.13 and let A.15.1 independently admit the performed Work; because ModelUseRelation expressly represents assignment-bound use, then establish F.6 through the same obtaining A.13 assignment and recover ModelUseRelation, then stop.
    • If maintained expression content is current, recover the fixed model content, fixed expression content, declared coherence predicate, and comparison scheme, then decide ModelExpressionCoherenceRelation and stop.
  3. Recover the remaining direct relations only when their joint organization changes the decision. Select BoundedModelUseStructure only then.
  4. Keep every boundary crossing separate. A proposed source, target, direction, required fit, permitted loss, and claim scope is useful planning content, but it is not an occurrence and cannot identify either endpoint structure.

Entry case. A press-control team must decide whether a controller-code change may be handled as a local code edit or must enter the independently governed release review together with model applicability and operating use.

  1. PressControlModel-5 is the claim-bearing model edition, Press-3 is the use locus, and the model applies within SafetyControlClaimScope; this is one ModelApplicabilityRelation occurrence.
  2. A.13 first recovers Operator-12 : U.System as the performer through obtaining OperatorAssignment-8, and A.15.1 independently admits PressOperationWork-91 : U.Work. Because this actual-use claim expressly represents assignment-bound use, F.6 performedUnderAssignment(PressOperationWork-91, OperatorAssignment-8) then obtains. The already recovered performer actually uses PressControlModel-5 during that Work concerning Press-3; this is one ModelUseRelation occurrence.
  3. ControllerImplementsControlModelPredicate checks the fixed contents of PressControlModel-5 and PressControllerCode-17 under PlantControlReferenceScheme. It returns true, so one ModelExpressionCoherenceRelation occurrence obtains. The predicate is the test value, not the occurrence or an evaluation procedure.
  4. Because independently governed PlantReleaseRule-3 needs model applicability, operating use, and fixed-content coherence together when each is material, select their organization and present those three facts jointly to the release review. This selection supplies the review’s subject matter; PlantReleaseRule-3 supplies the review obligation; release authority, if needed, is established separately.
Named selection-use frameQuestionAdmissible actionStop or return condition
PressControlReleaseFrameMust this change be considered as code alone, or together with current applicability, operating use, and fixed-content coherence?Give the three exact occurrences and applied constraints as the joint subject matter of the independently governed release review.Return to the three direct relations if PlantReleaseRule-3 is absent or does not require their joint review.

The named selection-use frame is developed in section 5.1. If the decision asks only whether the model applies to Press-3, stop after step 1. If PlantReleaseRule-3 is absent or does not require the three facts together, stop at the direct relations. No crossing is asserted.

Three quick recognition situations.

SituationFirst direct resultWhen the structure becomes current
Industrial controlApplicability, assigned-Work use, or fixed-content coherence for one control model and machine.Their exact three-relation organization, exact applied constraint claims, and a filled selection-use frame change an engineering decision.
Clinical and billing terminologySeparate F.6 attributions, A.1.1 use occurrences, and A.2.6 scopes for diagnosis and billing Work.Each positive structure has its own complete three-relation organization, applied constraints, and selection-use frame; a shared model does not merge them.
Published classification modelActual assigned-Work use of one published model concerning an organization.Applicability, use, coherence, constraints, and one classification-use frame jointly change the classification decision; publication alone is insufficient.

Short glosses. A model episteme is one claim-bearing model edition. A model-use holon is one already admitted holon, such as a system, a performed Work occurrence or an episteme, about which the model applies or is used; it is not a context container. Work (U.Work) is one exact dated doing, not its method, plan, or result. A claim scope (U.ClaimScope) is the set-valued boundary of context slices for one claim. A relation occurrence is a world-side relation actually obtaining under its predicate. A reference scheme is the interpretation basis for claim content. A structure here is a selected organization of already governed constituents, obtaining relations, applied constraints, and one exact selection-use frame; it is not another whole.

Adoption test. After applying A.1.1, name the exact organization that changes the present decision and the condition for stopping or returning to its direct relations. If either is missing, stop at the direct relation or the pattern that defines or tests it.

Names for retrieval. The Plain label is bounded context and the Tech label is BoundedModelUseStructure. Use F.18 for designation settlement and lineage, and F.17 for the public terminology row and its refresh evidence; A.1.1 keeps only the names needed to apply this pattern. Authors MUST NOT publish U.BoundedContext as a U-kind.

A.1.1:1 - Problem frame

Use this when. Use this pattern when a current decision depends on the organization of three distinguishable facts about one model edition: where it applies, how it is actually used in assigned Work, and whether maintained expression content remains coherent with it. Physical location, team ownership, a document title, or the word context is not enough.

First useful move. State the decision, model, and use locus; recover only the direct relation that answers the question and stop when it suffices. Select the wider structure only when several already governed relations, applied constraints, and one exact selection-use frame together change the decision.

What goes wrong if missed. Systems, Work, epistemes, and publications are merged into a context-shaped proxy. One subsystem under two models is treated as one context by location, while one model used coherently across several loci is split by an implementation boundary. Local vocabulary, rules, units, status, or evidence use is also forced into a context object even when a direct semantic-locality pattern answers the question.

What this buys. Actual participants retain their identities. Applicability, use, and fixed-content coherence remain inspectable direct relations; their decision-relevant organization can be selected as U.Structure; and ordinary semantic locality is stated through its exact value and relation assertion, with the subject pattern kept only as a locator.

Not this pattern when. If only a term sense, local system-role-kind value, system-role-assignment occurrence, relation among system-role kinds, rule or invariant, admissible inference, unit or measurement basis, status, evidence use, claim scope, description, publication, or direct relation is current, use the A.1.1:4.4 triage and stop at that direct result. Do not select BoundedModelUseStructure unless the relation organization itself changes the decision.

A.1.1:2 - Problem

DDD bounded-context practice couples several real concerns: a model is defined and applicable within a boundary; actual systems in assigned roles use it; code and descriptions contain expressions of it; integration and maintenance work aims to keep those expressions consistent; and maps describe relationships among model uses. These are practical prompts to recover exact FPF claims, not evidence that maintenance caused coherence or that a described crossing obtains. Their objects are related, but they are not parts of one additional whole by that fact.

FPF needs this joint model-use relation organization selectable as U.Structure so it can serve as EntityOfConcern for comparison and maintenance work without becoming a heterogeneous holon, a description, or one universal semantic-locality reference.

A.1.1:3 - Forces

ForceTension
Actual loci vs selected organizationSystems, work, teams, and epistemes keep direct identities, while their model-use relations may need treatment as one structure.
Model applicability vs semantic localityA model-use boundary can change the next engineering move; ordinary local meaning often needs only a reference scheme, scope, or governing episteme.
One subsystem vs several modelsPhysical or organizational location does not distinguish two competing model organizations over the same subsystem.
One model vs several lociA coherent model use can span several actual loci when one applicability, actual-use, and model-expression-coherence organization relates them.
Structure vs holonA selected relation organization is useful without claiming that its substrates are parts of another whole or pass a meta-holon transition.
World-side use vs descriptionA boundary description can be stale or absent while actual applicability, use, and model-expression-coherence relations continue.
Source vocabulary vs FPF kindsDDD uses context, mapping, and map as practice terms; FPF must recover method, structure, view, publication, and actual participants separately.

A.1.1:4 - Solution

Recover the Plain bounded context as one BoundedModelUseStructure, governed as a U.Structure. Identify it from one exact model episteme, exact already-admitted model-use holons, the selected organization of obtaining model-applicability, actual model-use, and fixed-content model-expression-coherence occurrences, exact applied constraint claims used by the selection judgment, and one exact selection-use frame.

Each U.ClaimScope remains only a participant of its selected ModelApplicabilityRelation; a separate applied constraint claim may refer to that scope or its A.2.6 membership predicate. A bare scope, slice, membership outcome, boundary display, or carrier enters no A.22 discriminator. No boundary crossing participates in this identity.

A later model edition has another C.2.1 episteme identity; continuity across it additionally requires exact EpistemeEditionRelation(earlierModelEpisteme, laterModelEpisteme) and the A.1.1 continuity rule.

A.1.1:4.1 - Select structure, not another holon

Use the four A.22 identity discriminators. The following sketch is a description of the selected organization, not the structure itself and not a relation signature:

BoundedModelUseStructure : U.Structure
  exact constituents:
    one selected model episteme
    exact admitted model-use holons
  exact selected obtaining relations:
    ModelApplicabilityRelation occurrences
    ModelUseRelation occurrences
    ModelExpressionCoherenceRelation occurrences
  exact applied constraint claims used by the selection judgment:
    one exact C.2.1 constraint proposition may refer to a U.ClaimScope or its A.2.6 membership predicate
    other exact applicability, coherence, release, or use-rule constraint propositions applied here
    no bare scope, slice, membership outcome, boundary display, or carrier episteme
  one named selection-use frame:
    exact question
    admissible action
    stop or return condition

A selection-use frame is the exact plain value formed by the question, admissible action, and stop or return condition; it is not a new kind, card, or record. A phrase such as current use, appropriate structure, or bounded-model-use frame does not fill it. Changing one of those three values changes that identity discriminator.

The structure depends on its constituents and selected relation organization. It is not a holon whose parts are the substrate systems, Work, methods, or epistemes. Their identities, direct part relations, and any construction or whole-reidentification questions remain separately governed.

A.1.1:4.2 - Recover the direct relations

A.1.1 states each direct predicate and its occurrence-identity rule. An obtaining occurrence is an instance of a relation kind already admitted under U.Relation; its existence does not depend on a project deciding to expose it. A named receiving use may justify explicit individuation and reference under A.6.REL. A reusable RelationSignature episteme declares the participant SlotSpecs. An assertion or occurrence description may designate the actual participants by value or reference. Each table below is a readable presentation of one signature declaration.

The two named temporal-extent ValueKinds below are local to A.1.1, not U-kinds. They can type a temporal extent stated in an assertion or occurrence description; they are not participant ValueKinds in either RelationSignature. For ModelApplicabilityRelation and ModelUseRelation, the direct obtaining history determines the maximal continuous extent used by the occurrence-identity rule. A filled assertion may state an open or closed extent.

Local ValueKindBoundary and continuity semantics
ModelApplicabilityIntervalThe maximal interval during which one fixed model episteme remains applicable to one fixed holon under one fixed claim scope, interpreted by that model episteme’s own effective reference scheme.
ModelUseIntervalThe maximal interval within one fixed work occurrence for which exact F.6 performedUnderAssignment(work, assignment) obtains, during which that assignment’s holder actually uses one fixed model concerning one fixed use-locus holon.

For these two temporally varying relation kinds, continued obtaining extends the same open occurrence; a demonstrated gap ends it, and later resumption begins another occurrence. ModelExpressionCoherenceRelation instead has the participant-determined identity declared below: it has no temporal-extent discriminator. Revising an assertion changes the episteme, not any world-side occurrence.

ModelApplicabilityRelation. Its participants are one model episteme, one exact holon, and one declared claim scope. Its predicate asks whether that model applies to that holon over the exact U.ContextSlice values delimited by that scope. The model episteme’s C.2.1 effective reference scheme supplies the interpretation basis; it is not a fourth participant.

SlotKindValueKindrefModeParticipant meaning
ApplicableModelEpistemeSlotU.EpistemeU.EpistemeRefThe model episteme whose distinctions and predicates are applied.
ModelApplicabilityHolonSlotU.HolonU.HolonRefThe exact holon about which the model is applicable.
ApplicabilityClaimScopeSlotU.ClaimScopeByValueThe scope whose A.2.6 member(slice, scope) predicate delimits the claim.

Well-formedness constraint WF-A1.1-APP. ModelApplicabilityRelation(M,H,S) obtains exactly when S is the model-declared applicability scope or scopeSubset(S, modelDeclaredScope(M)), both scope expressions are interpreted under effectiveReferenceScheme(M), and the model’s declared applicability conditions hold for H over every slice x for which member(x,S) is true. coversSet(S,T) applies only when T is an exact finite ContextSliceSet.

When S imports a local sense from another semantic setting, the interpretation branch exists exactly when the source and receiving F.17 SchemeSenseCell values are resolved and an F.9 Bridge obtains in the source-to-model orientation. Different schemes, shared spelling, or a Bridge Card does not establish that branch.

Well-formedness constraint WF-A1.1-APP-USE. A positive applicability assertion or structure selection that relies on the imported branch is admissible only when a separate current C.2.1 claim affirmatively states that the Bridge is suitable for this named scope-comparison use, direction, rule, and loss tolerance. The same use must have an exact A.10 evidence-provenance path whose edges cite independently established direct relations. Ordinary reliance requires RelianceDisposition=pass. If a named assurance claim about that use is at issue, require its B.3 AssuranceResult for the same bounded use: only supported-for-use supports the attempted assurance use, while narrowed supports only its stated narrower use. A domain rule may require such a claim.

Use guidance. If the Bridge, bounded-use claim, or selected reliance branch is missing, return respectively missing claim-scope interpretation bridge, missing claim-scope interpretation use claim, or missing claim-scope interpretation reliance. These stops block the receiving assertion or selection; they do not make an otherwise obtaining Bridge false. Any membership judgment, operation application, assertion, or Work remains under A.2.6, A.6.1, C.2.1, or A.15.1.

The occurrence is reidentified from the actual identities of the model episteme, holon, and claim scope together with the derived maximal continuous ModelApplicabilityInterval. Repeating the model’s effective scheme adds no independent discriminator.

ModelUseRelation. Its participants are one exact system-role-assignment occurrence, one model episteme, one performed Work occurrence, and one exact use-locus holon. Its predicate is actual use of that model content by the assignment holder while that system performs the same Work concerning that holon.

SlotKindValueKindrefModeParticipant meaning
ModelUserSystemRoleAssignmentSlotU.SystemRoleAssignmentU.RelationRefThe system-role-assignment occurrence paired with the Work by exact F.6 performedUnderAssignment.
UsedModelEpistemeSlotU.EpistemeU.EpistemeRefThe model episteme whose content is actually used.
ModelUseWorkSlotU.WorkByValueThe independently identified performed Work in which use occurs.
ModelUseLocusHolonSlotU.HolonU.HolonRefThe exact holon concerning which the model is used.

The Work designation denotes one independently identified A.15.1 occurrence W, with the extent needed by this claim. ByValue supplies that identified participant directly. A plan, log, or report may help recover W but cannot substitute for it. If the available material does not identify one W, leave the model-use claim unresolved.

Well-formedness constraint WF-A1.1-USE. ModelUseRelation(A,M,W,H) obtains exactly when F.6 performedUnderAssignment(W,A) obtains and HolderSystem(A) actually uses the content of M while performing W concerning H. The holder system is derived, not copied as a fifth participant. Any claimed enactment relation between W and a Method belongs to A.15.1; A.3.1 identifies that Method.

The occurrence is reidentified from the four participant identities and the derived maximal continuous ModelUseInterval. A useful counterfactual probe compares otherwise matching work situations that use model epistemes with different relevant content and asks whether that difference could change performance; availability or mention alone is not actual use.

Scope delimitation is not another direct relation kind here. The U.ClaimScope participating in ModelApplicabilityRelation is a set-valued scope over U.ContextSlice; A.2.6 governs its primitive membership predicate. A membership assertion or an evaluation result is an episteme about that predicate.

Local predicate-value declaration. ModelExpressionCoherencePredicate is an A.1.1-local ValueKind, not a U-kind and not an evaluation procedure. A by-value candidate belongs to this kind only when it declares all five components:

  1. the ordered model-content and expression-content input meanings;
  2. the exact comparison domain and local senses;
  3. a Boolean truth condition;
  4. the treatment of required congruence and permitted loss; and
  5. every dependency whose absence makes application stop rather than return false.

Two predicate values are identical exactly when those five by-value components are identical. A changed input meaning, domain, truth condition, congruence or loss rule, or dependency identifies another predicate value; a changed label, evaluator, evidence set, result episteme, representation, or publication does not. A label or procedure lacking the complete five-part declaration is not a member.

ModelExpressionCoherenceRelation. Its participants are one exact model episteme, one exact expression episteme, one by-value criterion admitted as ModelExpressionCoherencePredicate, and one exact abstract rule-collection entity belonging to EpistemeInterpretationScheme under C.2.1:4.1.2, used as the comparison basis.

SlotKindValueKindrefModeParticipant meaning
CoherenceModelEpistemeSlotU.EpistemeU.EpistemeRefThe model episteme whose fixed claims supply one side.
CoherentExpressionEpistemeSlotU.EpistemeU.EpistemeRefThe expression episteme assessed against that model.
ModelExpressionCoherencePredicateSlotModelExpressionCoherencePredicateByValueThe admitted five-part criterion value; its label, evaluator, result, or evidence cannot substitute for it.
ModelExpressionCoherenceReferenceSchemeSlotEpistemeInterpretationScheme (C.2.1:4.1.2)ByValueThe shared scheme or the receiving comparison basis used by the admitted bridged branch.

R is the abstract rule-collection entity individuated under C.2.1:4.1.1 and classified by the entity ValueKind in :4.1.2. That entity, rather than its description or designation, is the actual participant. Carrying its designation ByValue supplies the rules directly; a document or name for them is insufficient. Membership in EpistemeInterpretationScheme does not establish scheme equality, the required correspondence, or satisfaction of the declared coherence criterion. Changing R changes the participant tuple; changing only its expression while preserving all operative rules does not.

Well-formedness constraint WF-A1.1-COH. ModelExpressionCoherenceRelation(M,E,P,R) obtains exactly when either (a) R equals the C.2.1 effective schemes of both epistemes, or (b) P resolves every differing source and receiving F.17 SchemeSenseCell pair and names an obtaining F.9 Bridge for each required correspondence; and, after that semantic branch is established, the fixed predicate value P returns true for the fixed claim contents of M and E under R. An unresolved cell, missing Bridge, shared spelling, common label, Bridge Card, or mere interpretability establishes no bridged branch.

The Bridge profile carries relation semantics only. Comparison direction, use-specific rule, permitted loss, and reliance belong to the separate bounded-use claim and reliance path.

Well-formedness constraint WF-A1.1-COH-USE. A receiving assertion or structure selection that relies on a bridged coherence occurrence is admissible only when a separate current C.2.1 claim affirmatively states that the Bridge is suitable for this fixed-content comparison use, direction, rule, and loss tolerance compatible with P. The same use must have an exact A.10 evidence-provenance path whose edges cite independently established direct relations. Ordinary reliance requires RelianceDisposition=pass. If a named assurance claim about that use is at issue, require its B.3 AssuranceResult for the same bounded use: only supported-for-use supports the attempted assurance use, while narrowed supports only its stated narrower use. Establish any required authorization separately.

Use guidance. Return missing model-expression interpretation bridge, missing model-expression interpretation use claim, or missing model-expression interpretation reliance for the corresponding missing condition. A use stop does not make the Bridge or predicate false and does not erase or reidentify an otherwise obtaining coherence occurrence. Comparison Work, an assertion episteme, and an A.22 selection use remain separate.

One occurrence is participant-determined by <M,E,P,R>; it has no temporal-extent discriminator and no later recurrence for the same tuple. Changed claim content identifies another episteme and tuple. Changed predicate value or comparison scheme likewise changes the tuple. Changed evidence, bounded-use claim, reliance result, card, publication, evaluator, or timestamp does not.

Each claimed maintenance episode is a separate dated Work individual: recover each performer through A.13 and let A.15.1 independently admit the occurrence. Add F.6 through the same obtaining A.13 assignment only when the maintenance account or its receiving use expressly consumes precise assignment-bound attribution; F.6 identifies neither assignment nor performer, and missing or failed attribution leaves the Work intact. Its affected-referent, resource, parameter, premise, method-enactment, and operation-application facts use their direct relations or A.6.1 bindings. C.2.1 identifies any report or repaired episteme separately; only an exact A.15.PROD entity-inception claim may relate that episteme’s first existence to the performed maintenance.

An evaluator may separately be recovered through A.13 and perform independently admitted evaluation Work, with F.6 added only for a consumed precise attribution. C.2.1 identifies any result episteme asserting whether the coherence predicate holds, and only its exact A.15.PROD inception basis may relate its first existence to that performed Work. Neither that result episteme nor its provenance is the coherence occurrence.

Failed maintenance work remains actual work even when the changed episteme tuple has no obtaining coherence occurrence.

BoundedModelUseStructure selects obtaining participant-determined ModelExpressionCoherenceRelation occurrences. Maintenance methods and Work remain separate objects even when they change the receiving decision; if their organization must itself be selected, that is a distinct A.22 structure and does not enter this bounded-model-use identity.

Coherence-work stress cases. Coherence can obtain before any selected maintenance episode. Successful maintenance that leaves both episteme identities fixed leaves the same participant tuple; maintenance that changes expression claim content gives another C.2.1 episteme and a different tuple to evaluate. Failed maintenance may leave a changed expression episteme and a separately identified evaluation result while the new tuple has no obtaining coherence occurrence. Automated integration work and non-software maintenance use the same separation among fixed-content correspondence, work, result, evaluation, evidence, and provenance.

Occurrence-identity stress case. F.6 performedUnderAssignment(InspectionWork-42, InspectorAssignment-17) obtains, and its holder Robot-7 uses DefectModel-3 concerning Pump-6 during that work. An observation at 10:00 supports continued obtaining of the same occurrence whose ModelUseInterval began at 09:00 and remains open; it does not create another occurrence. If model use demonstrably stops at 10:15 and resumes at 10:30 during the same work occurrence and assignment attribution, the resumption begins a second model-use occurrence. Correcting an assertion’s timestamp without evidence of a world-side gap changes only that assertion.

Use guidance — unsupported crossing. First identify both endpoint BoundedModelUseStructure values without the crossing and state source, target, direction, required fit, permitted loss, and claim scope. Well-formedness constraint WF-A1.1-CROSS. A positive cross-structure member exists only when a current direct pattern supplies compatible endpoint SlotKinds, an obtaining crossing predicate, an occurrence-identity rule, and all four A.22 discriminators; the proposal, F.9 sense Bridge, label, diagram, or card supplies none of them. Otherwise preserve the six-part proposal, omit it from both endpoint identities and every positive cross-structure member, and return missing CROSS-LOCALITY-BRIDGE governor.

A.1.1 is the subject pattern for these three relation kinds. A.6.0 governs their RelationSignature epistemes, A.6.5 governs the SlotSpecs inside those declarations, and A.6.REL governs progressive explicit individuation. A.2.6 separately governs claim-scope membership. BoundedModelUseStructure is the selected organization of the resulting occurrences under those scope values; no context record copies their participants.

A.1.1:4.2a - Use the settled public relation names

The direct definitions, SlotSpecs, obtaining constraints, and occurrence-identity rules above govern the three relation kinds. A.1.1 uses only the settled Tech labels and their shortest Plain relation sentences:

Tech labelPlain relation sentenceNearest non-use
ModelApplicabilityRelationthis model applies to this holon within this claim scopenot scope membership, an applicability assertion, or the derived interval
ModelUseRelationthis assignment’s holder uses this model during this Work concerning this holonnot availability, method application, Work, assignment, or a use record
ModelExpressionCoherenceRelationthis model content and this expression content satisfy this declared coherence criterion under this comparison schemenot maintenance, implementation, evaluation, evidence, or the predicate value itself

ModelExpressionCoherencePredicate remains an A.1.1-local five-part criterion ValueKind. Use F.18 and F.17 when the receiving task independently requires a durable public designation and terminology row.

A.1.1:4.3 - Identify continuity through model use

At one observation time, the structure has the four A.22 discriminators:

  1. exact independently identified constituents—the selected model episteme and admitted model-use holons;
  2. exact selected obtaining applicability, use, and coherence occurrences;
  3. exact applied constraint claims used by this selection, each with a recoverable proposition and C.2.1 identity; a claim may refer to one U.ClaimScope or its membership predicate, but the bare scope, membership outcome, boundary display, or carrier is not this discriminator; and
  4. one exact named selection-use frame containing its question, admissible action, and stop or return condition.

No crossing or proposed six-part crossing record enters those discriminators.

At a later observation time, reidentify the same structure only when every continuing constituent is reidentified under its direct rule; any replacement model is connected by exact C.2.1 EpistemeEditionRelation and admitted by the declared continuity rule; every continuing relation occurrence retains its direct identity; every replacement occurrence is explicitly admitted; and all four A.22 discriminators remain the same under that rule.

The continuity rule therefore compares the exact constituents, selected occurrence organization, exact applied constraint claims, and the complete question/action/stop-or-return selection-use frame. A changed constraint proposition reopens the third discriminator; changing only a membership assertion, boundary rendering, carrier, or evidence about an unchanged constraint claim does not. A changed question, action, or return condition reopens structure identity even when every substrate and relation occurrence remains unchanged.

Compare an altered explanation for any change it makes to an applied constraint, question, action, or stop or return condition; only such a change reopens that discriminator. A changed page, wording, rendering, carrier, description edition, or publication does not.

File history, edition labels, publication order, a shared name, or membership in an edition collection establishes neither EpistemeEditionRelation nor bounded-model-use continuity; A.14 governs any separately selected collection of editions.

Missing evidence creates uncertainty about a continuity claim; it does not by itself end a world-side relation or structure. Any selected substrate holon may separately participate in a larger whole under A.14 and C.13; that is not parthood of BoundedModelUseStructure.

A.1.1:4.4 - Resolve semantic locality through direct values and relations

When the question is local meaning rather than joint model-use organization, recover the smallest direct result and stop:

Practitioner questionDirect governed resultSubject patternStop or return condition
What does this term or predicate mean here?one exact claim-bearing episteme, its C.2.1 effective reference scheme, and the needed F.17 SchemeSenseCell valuesC.2.1 and F.17Return to the source expression or scheme when the exact meaning or a required sense-cell value is unavailable.
Over which slices is this claim made, and which slices belong?one U.ClaimScope and its A.2.6 member(slice, scope) factsA.2.6Keep the scope and membership facts as this result; select a structure separately only when its organization changes a receiving decision.
Which system-role kind is assigned to which system, and when?First recover the assignment occurrence and its declared U.SystemRoleAssignment species. The species declares participant meanings and rules; the occurrence supplies the holder System, assigned local system-role-kind value, and any other participant values that distinguish the occurrence. If the question also needs a reportable time, recover a separate assignment assertion or occurrence-description episteme whose content states the currently known AssignmentInterval.A.2 and A.2.1; A.2.7 only for an independently current relation among system-role kindsReturn until the assignment species, all declared participant values, obtaining predicate, and any needed occurrence-description episteme are recovered. The occurrence retains its maximal uninterrupted extent. Context, scheme, and interval are not generic assignment participants; an organizational title supplies no assignment.
Which rule, policy, invariant, or inference is local?one C.2.1 episteme with the exact ClaimGraph and effective scheme, the A.2.6 claim scope, and the truth or admissibility predicate defined or constrained in the exact subject-pattern descriptionC.2.1, A.2.6, that exact predicate and its SubjectPatternLocatorIf no exact predicate states when the rule or inference holds, preserve the claim at its current scope and stop.
Which unit or measurement reading is local?one C.16 measurement basis naming bearer, characteristic, scale, coordinate or level, the measurement unit when applicable, polarity, and evidence stubC.16Return to the C.16 measurement basis when only a displayed label or value is available.
How is an episteme used as evidence, or how is a status consumed?the exact episteme or status bearer, target claim, scope, polarity or status value, relevance window, provenance constraint, and intended useA.2.4 and A.10 for evidence use; F.10 for status family and status use; B.3 only for assuranceReturn to the exact evidence or status relation when only its presentation is known. For a permission, gate, or assurance claim, use its own subject pattern.
Can a field, department, technology, or shared spelling choose the local semantics?no; restate the live question and recover its exact model-use structure, scheme and sense cells, system-role kind or assignment, rule or status, or Bridge from the corresponding row abovethe pattern selected by that questionRestate the live question and use its corresponding row; a broad label alone leaves the selection unresolved.
Which admitted holon grounds a description’s empirical claims?one exact C.2.1 EpistemeEmpiricalGroundingRelationC.2.1Return to C.2.1 until the grounding relation is recovered.
Does one joint model-use organization change this decision?an independently selected BoundedModelUseStructure with all four A.22 discriminatorsA.1.1 and A.22omit modelUseStructureRef when one direct value or relation answers the question

For movement between local meanings, resolve the exact source and receiving F.17 sense cells and then apply F.9. An obtaining Bridge states correspondence between those readings; the separate bounded-use claim states direction, rule, and tolerance. A.10 handles ordinary reliance; B.3 adds a bounded result only when a named assurance claim is at issue. The Bridge is not the rule, unit, status use, inference, or receiving action.

If a subject pattern still asks for a generic U.BoundedContext or BoundedContextRef instead of the exact values above, do not fabricate that participant. Preserve the exact value or relation already recovered and stop at the unresolved interface in the subject pattern. The transfer is not complete merely because A.1.1 names a destination.

A.1.1:4.4.1 - Semantic-locality examples

Hospital operating-room case. Recover direct values and relations.

DistinctionDirect move and first result
Local vocabularyC.2.1 identifies the operating-room policy episteme and its effective scheme; F.17 resolves the local senses of case, time-out, and independent auditor.
Local rule and inferenceA C.2.1 claim episteme states the surgeon and auditor incompatibility rule within the exact surgical-case claim scope. A.2.1 supplies the actual SurgeonAssignment-12 and candidate IndependentAuditorAssignment-13; F.6 performedUnderAssignment(SurgicalCaseWork-42, SurgeonAssignment-12) establishes the current Work attribution. When the same-holder incompatibility predicate holds, a context-local A.2.7 incompatibility relation between the two assigned system-role kinds obtains; the relation is only a premise. SurgicalAdmissionService-4 : U.System applies IndependentAuditorAdmissionMethod-3 : U.Method to those assignment occurrences in dated AuditorAdmissionCheckWork-43 : U.Work; the receiving Method’s result episteme AuditorAdmissionCheckResult-43 records reject. The rule is not global.
Evidence and status useA sterility-audit episteme is used for one named claim only through A.2.4/A.10 with scope, polarity, window, and provenance. A Ready status is separately typed by F.10 for its exact target and use; neither item grants release permission or assurance.
Cross-setting approximationFirst ask whether the local meanings correspond at all. OperatingRoomCaseSenseCell means one surgical episode governed by the operating-room policy; BillingCaseSenseCell means one billable service record. In this replay, OperatingRoomCaseBillingBridge obtains under F.9 as a Partial-overlap relation between those cells, independently of any coding use. Separate C.2.1 claim HospitalCaseCodingUseClaim proposes coding the named surgical episode as one billable service record; its content names the operating-room-to-billing direction, a rule requiring the same patient, encounter, performed procedure, and date, a tolerance that permits omission of internal time-out and auditor-assignment detail from the billing record but no patient or procedure change, affirmative polarity, and HospitalCodingScheme-2026 as the effective scheme. A.10 states whether ordinary reliance passes; when a named assurance claim is at issue, B.3 supplies its bounded result for the same use. If a later claim says coding occurred, recover the exact coding Work and resulting billing assertion, publication, or operation application under their subject patterns. A different operating-room-to-staffing sense pair needs its own Bridge profile and use claim. Changing only either use claim leaves the Bridge identity unchanged. Establish any required coding authorization separately.

This replay selects no BoundedModelUseStructure unless one exact model’s applicability, assigned-Work use, fixed-content coherence, applied constraints, and selection-use frame also become current.

Two further uses.

UseDirect resultStop
Special relativityC.2.1 and F.17 identify the selected theory-edition episteme, effective scheme, postulate and inference senses; a later theory edition has another C.2.1 episteme identity and needs exact EpistemeEditionRelation for a continuity claim; A.2.6 scopes the claim; C.16 carries units and measurement readings; A.2.4/A.10 carries evidence use; F.10 carries any current status use. F.9 identifies only the exact low-speed semantic correspondence between the selected relativistic-reading and Newtonian-reading sense cells. A separate C.2.1 bounded-use claim proposes interpreting specified relativistic low-speed readings with the named Newtonian approximation rule, in the relativistic-to-Newtonian direction, within a stated velocity and error tolerance, with explicit polarity and effective scheme; A.10 states whether ordinary reliance passes; when a named assurance claim is at issue, B.3 supplies its bounded result for the same use. If a later claim says the approximation occurred, recover its exact inference or operation application, any comparison Work, and the result claim episteme under their subject patterns; a proposed use alone does not establish that the approximation occurred.No theory truth, edition continuity, global equivalence, inference permission, or approximation use follows from the label relativity, the Bridge, the bounded-use claim, or passing reliance alone.
FPF pattern qualityStart with the bearer and evaluation frame under C.16.Q. For example, first-use affordability of this exact pattern edition for a named practitioner and task is the E.21 UseAffordabilityAndApparatusProportionality coordinate, not a free quality label. C.2.1 identifies the pattern edition and any separately authored PatternQualityEvaluation result episteme; E.21 governs that evaluation record, its coordinates, and declared use; A.2.4/A.10 governs evidence use and F.10 any status use. If bare quality is still ambiguous, C.16.Q first distinguishes pattern quality from a product-reliability characteristic or C.25 bundle, a C.16 manufacturing-yield characteristic and measurement, B.3 safety assurance, a service-satisfaction characteristic or bundle, and ordinary praise. Resolve exact senses before any F.17/F.9 cross-scheme relation.The word quality supplies neither a bearer, evaluation frame, shared characteristic, evaluation result, assurance claim, manufacturing-yield reading, nor cross-setting substitution.

A.1.1:4.5 - Keep descriptions and publications separate

A bounded-context description is a U.Episteme. Under its C.2.1 declaration, the description’s entityOfConcernRef designates the exact EntityOfConcern named by the description’s claims. EntityOfConcernSlot is the SlotKind in that declaration; it does not itself point to the world-side object. A meta-description designates that description episteme through ordinary C.2.1 recursion.

When a description claim needs empirical grounding, recover one exact C.2.1 EpistemeEmpiricalGroundingRelation between the description episteme and the admitted grounding holon. GroundingHolonSlot is only the signature-local participant meaning in that relation’s declaration; a groundingHolonRef in a card or description designates the participant. The selected structure cannot fill that participant because it is not a holon. Viewpoint, claim scope, effective reference scheme, publication use, rendering, and presentation carrier remain separately governed.

A stale description can remain the same episteme while failing to describe the current model-use structure. A changed description edition or currentness claim does not by itself change that structure or its world-side relations.

A.1.1:4.6 - Recover DDD context mapping by direct object

Start with three questions: what reusable way of mapping was used, what work actually happened, and what claim-bearing product resulted? Identify that product under C.2.1. Call the same episteme a view only after it passes one exact E.17.0 viewpoint-conformance test. Keep the relation structure it describes and every diagram, page, or publication separate.

DDD source term or useFPF object
Bounded Context when the joint model-use organization changes an engineering moveBoundedModelUseStructure, governed as a U.Structure
subsystem at the boundarythe exact existing U.System under its direct pattern
work performed by a team system at the boundaryone dated Work individual independently admitted under A.15.1 after the performer System is recovered through A.13; add the same obtaining assignment occurrence and F.6 performedUnderAssignment relation only when this account expressly represents precise assignment-bound attribution
code base or database schema at the boundaryfirst classify the exact referent: claim-bearing code or schema content is a C.2.1 episteme; a repository, file, publication form, or carrier stays under its direct representation, publication, or carrier pattern; a deployed database or software organization stays a U.System or selected U.Structure under its subject pattern; the source phrase supplies no common kind
bounded-context boundary descriptionU.Episteme whose C.2.1 EntityOfConcern reference designates the exact referent named by its claims
Context Mapping as a reusable way of doingU.Method; any work plan, performed mapping work, evaluation work, and evaluation result remain separate
relations among several bounded contextsconditional A.22 membership for one already identified U.Structure, available only after independently governed exact obtaining crossings are selected among several bounded model-use structures and all four A.22 base discriminators are established; A.22 retains a local pending label for this rule but F.17 publishes no public cross-structure term
candidate product called Context Mapone independently identified C.2.1 episteme whose EntityOfConcern is the proposed or described crossing organization while a direct crossing governor or A.22 base identity is missing; only after both are established may a corresponding episteme designate the exact structure admitted by A.22’s conditional cross-structure rule; either episteme has dependent U.View membership only when exact E.17.0 EpistemeViewpointConformanceRelation obtains
visual or interactive expression and availability of an already admitted Context Map viewthe representation and its correspondence to the described organization, rendering work, publication occurrence, particular expression, any selected reusable publication form, and physical or digital carrier remain separate; C.29 applies when the representation is used as a mathematical lens

Code/schema split. Start from the claim, not the source phrase. Claim-bearing source-code or schema content such as PressControllerCode-18 is a C.2.1 episteme with an exact EntityOfConcern and effective scheme. A particular expression of that content, any reusable publication form it follows, and the repository, file, or other carrier whose actual state yields the expression remain under their direct representation/publication/carrier patterns. A deployed controller, database, or software organization remains an actual system or selected structure under its subject pattern. The phrase code base or database schema grants none of those identities and never supplies one universal kind.

Positive case: the fixed claims expressed by PressControllerCode-18 participate as the expression episteme in ModelExpressionCoherenceRelation. Near misses: PressControllerRepository-2 is only the repository or carrier being referred to, and DeployedPressDatabase-4 is the deployed database system or structure. Neither near miss may fill an episteme participant merely because source practice calls it a code base or schema.

This dispatch table is a reading aid for selecting the governing FPF object and pattern. Only that direct pattern supplies object identity, relation obtaining, or dependent-kind membership. If a separately current claim says that the candidate episteme first existed through the performed mapping Work, apply A.15.PROD only to that exact local inception claim. If an earlier episteme participates as source, use C.2.P to recover the exact source expression and route the source-use relation to its direct governor. Evaluation Work and any result episteme remain separate. None of those facts, and no product name, representation, rendering, publication occurrence, form, or carrier, grants U.View membership.

FPF Map remains the mapping-method head for mapping subjects to coordinates in a declared Space. The quoted DDD product name stays a retrieval cue; by itself it grants neither dependent U.View membership, the FPF Map reading, nor identity with the structure.

BoundedModelUseStructure and A.22’s conditional cross-structure rule concern different structures. First identify every bounded model-use structure from its own model, admitted holons, three direct relation families—including each applicability occurrence’s exact U.ClaimScope participant—exact applied constraint claims, and named frame. A scope or membership result is not copied into the constraint discriminator.

Only then may a distinct A.22 structure select several such endpoints and independently governed obtaining crossings among them. Until those crossing occurrences and all four A.22 base discriminators exist, no member of that conditional specialization is asserted and its A.22-local label remains pending. Maintenance Work remains separate from both structures.

A candidate context-mapping episteme may carry claims about a proposed crossing organization without designating an exact structure. Once the direct crossing and A.22 identity exist, a corresponding C.2.1 episteme may designate that exact cross-structure and its participants.

A diagram, prose account, or interactive representation may show the structure or proposal through its stated correspondence to the participants, crossings, direction, and qualifications. Use A.6.3.RT when the intended operation on this material depends on changing its representation language or reasoning medium. Use A.6.3.RT.OE:4 to construct a suitable expression and C.29 when the question needs a mathematical lens. The episteme is a U.View only after exact E.17.0 conformance obtains.

A.1.1:4.7 - Preserve the lightweight path

When one direct claim answers the task, name its participant, semantic-locality value, system-role-assignment occurrence, or direct relation occurrence under the subject pattern and stop.

Select and expose BoundedModelUseStructure only when the joint organization of independently governed model applicability, actual model use, fixed-content model-expression coherence, exact applied constraint claims, and the named frame changes the next engineering move. Keep each claim scope solely in its applicability occurrence unless a distinct applied constraint proposition refers to it.

If a crossing matters, open the separate A.22 cross-structure question only after its direct governor makes that exact crossing obtain between already identified endpoint structures; never add it to either endpoint identity.

Recognize an episteme as U.View only after exact E.17.0 conformance. Publish that already recognized view under E.24.PUB only when a declared audience and use need it.

A.1.1:5 - Archetypal Grounding

A.1.1:5.1 - Detailed control-model case

Section 0 gives the entry case. The following detail develops the relation identities, maintenance and evaluation claims, and their stop conditions when the receiving use needs them. Any claim of authority over the Work needs its own governing basis.

  1. Applicability decision. ModelApplicabilityRelation obtains among model episteme PressControlModel-5, system Press-3, and claim scope SafetyControlClaimScope. C.2.1 fixes PlantControlReferenceScheme as the model episteme’s effective scheme, so it supplies the interpretation basis without becoming a fourth participant. The derived ModelApplicabilityInterval remains open while the model’s declared applicability conditions hold for Press-3 over the exact U.ContextSlice values admitted by member(slice, SafetyControlClaimScope) under that scheme.
  2. Actual-use decision. A.13 first recovers Operator-12 : U.System as the performer through obtaining OperatorAssignment-8, and A.15.1 independently admits PressOperationWork-91 : U.Work. Because this decision expressly represents assignment-bound model use, F.6 performedUnderAssignment(PressOperationWork-91, OperatorAssignment-8) then obtains. The already recovered performer actually uses PressControlModel-5 concerning Press-3 during that Work. Those four relation participants plus the derived maximal continuous ModelUseInterval reidentify one ModelUseRelation occurrence.
  3. Scope boundary. Under the A.2.6 membership predicate, EmergencyStopContextSlice belongs to SafetyControlClaimScope. This membership claim explains part of the applicability boundary; it is not another relation occurrence selected into the structure.
  4. Fixed-content coherence decision. ControllerImplementsControlModelPredicate is an admitted local predicate value. Its ordered inputs are the fixed claim contents of PressControlModel-5 and PressControllerCode-17; it returns true exactly when the code expresses every controller-command and feedback distinction required by the model, and false when a required distinction is missing. Both epistemes have PlantControlReferenceScheme as their C.2.1 effective scheme, so the relation-side comparison scheme is that same value and no Bridge is inferred. The predicate returns true for these participants, so their participant-determined ModelExpressionCoherenceRelation occurrence obtains before any selected maintenance episode.
  5. Maintenance and change stay separate.
    • Work: Engineer-4 : U.System performs ControllerCoherenceWork-22 : U.Work under ControllerEngineerAssignment-7. First recover Engineer-4’s A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the dated Work from its performance history, enacted ControllerAlignmentMethod-2, extent, and containing-System relation. Because this case explicitly attributes performance under ControllerEngineerAssignment-7, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Engineer-4 as holder, and covers the Work.
    • Transformation and later episteme: A.3.4 independently identifies PressControllerCodeCarrierChange-24 : U.Transformation as the bounded change of continuing digital entity PressControllerCodeCarrier-6 : U.Entity, using the exact edit boundary, before-and-after code-expression facts, and the carrier-continuity rule. Changed claim content identifies later episteme PressControllerCode-18 under C.2.1.
    • Stop: No current FPF relation says that ControllerCoherenceWork-22 caused or realized PressControllerCodeCarrierChange-24, so return missing work-to-change governor; temporal overlap and a shared code referent do not supply it. A.15.PROD remains closed for a claim that the Work first constituted PressControllerCode-18 until its exact entity-inception basis, including that missing link, is governed.
  6. Evaluation and result stay separate.
    • Evaluation Work: Evaluator-2 : U.System performs CoherenceEvaluationWork-23 : U.Work under CoherenceEvaluatorAssignment-5. First recover Evaluator-2’s A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the dated Work from its performance history, enacted CoherenceEvaluationMethod-4, extent, and containing-System relation. Because this case explicitly attributes performance under CoherenceEvaluatorAssignment-5, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Evaluator-2 as holder, and covers the Work. State any needed operation application through its A.6.1 binding.
    • Result: C.2.1 separately identifies result episteme CoherenceEvaluation-23, which asserts whether the coherence predicate holds; only an exact A.15.PROD inception basis may relate that episteme’s first existence to the evaluation Work. The result’s assertion, evidence-use relation, and provenance remain distinct.
    • Next tuple: Because PressControllerCode-18 has different claim content, it forms another participant tuple with PressControlModel-5; predicate truth for that tuple decides whether another coherence occurrence obtains. Maintenance, method enactment, changed referent, evaluation, result, evidence, and provenance neither substitute for that truth nor enter the relation’s participant set or identity.
  7. Crossing stop. If a diagnostics crossing matters, first retain the independently identified source and target structures, then record direction, required fit, permitted loss, and claim scope. F.9 governs correspondence between local senses. Omit the proposed crossing from any positive cross-structure member and return missing CROSS-LOCALITY-BRIDGE governor. The already governed endpoint relations remain available for their own selections.

Filled A.22 basis for the press-control structure.

  • Its exact constituents are model episteme PressControlModel-5 and use-locus system Press-3.
  • Its selected occurrences are ModelApplicabilityRelation(PressControlModel-5, Press-3, SafetyControlClaimScope), ModelUseRelation(OperatorAssignment-8, PressControlModel-5, PressOperationWork-91, Press-3), and ModelExpressionCoherenceRelation(PressControlModel-5, PressControllerCode-17, ControllerImplementsControlModelPredicate, PlantControlReferenceScheme) as established in steps 1–4. OperatorAssignment-8 and PressOperationWork-91 remain actual participants used to establish the selected ModelUseRelation; they are not copied into the constituent plurality.
  • Its exact applied constraint claims are PressSafetyScopeUseConstraintClaim, whose proposition says that every target slice used in the release judgment satisfies member(targetSlice, SafetyControlClaimScope); PressCommandFeedbackConstraintClaim, whose proposition says that the change preserves the model’s command-versus-feedback distinction; and PlantJointReviewConstraintClaim, whose proposition says that, under independently governed PlantReleaseRule-3, all three selected occurrences are required inputs to the release review when each is material. SafetyControlClaimScope, any membership outcome, boundary rendering, and the claim carriers enter no discriminator by themselves.
  • Its fourth discriminator is PressControlReleaseFrame from section 0: ask whether the change is code-only or jointly model/use/coherence-relevant; provide that joint subject matter to the release review; return to the three direct relations if PlantReleaseRule-3 is absent or does not require their joint review.

Missing any discriminator leaves the direct relations in place but blocks this structure selection.

The relation sentences above assert direct world-side occurrences; the scope sentence states an A.2.6 membership claim. If the question is only whether the model applies to the press, stop at ModelApplicabilityRelation. Select BoundedModelUseStructure only when the selected applicability, operating-use, and expression-coherence occurrences plus the exact applied constraint claims and frame change the decision or Work plan.

One subsystem, one model. The press-control replay above is the filled case. The machine keeps its U.System identity; the selected structure uses the exact constituents, three obtaining relations, applied constraints, and PressControlReleaseFrame. Without that complete basis, stop at the direct relations. A diagram or later crossing is unnecessary for the positive selection.

One subsystem, two competing models. DeviceSubsystem-2 remains one system. Two structures are available only because each organization is independently complete:

Selected structureConstituents, relation occurrences, and applied constraintsNamed selection-use frame
DeviceMaintenanceModelUseStructureconstituents DeviceStateModel-4 and DeviceSubsystem-2; applicability of DeviceStateModel-4 to DeviceSubsystem-2 within MaintenanceClaimScope; selected ModelUseRelation established by F.6 performedUnderAssignment(DeviceMaintenanceWork-31, MaintenanceAssignment-12) plus actual use during that Work; coherence of DeviceStateModel-4 and MaintenanceProcedureEpisteme-9 under DeviceStateMaintenanceCoherencePredicate and DeviceStateReferenceScheme; applied claim MaintenanceScopeUseConstraintClaim says every equipment-state slice used in the maintenance diagnosis satisfies member(slice, MaintenanceClaimScope), and MaintenanceStateDistinctionConstraintClaim says the diagnosis preserves the model’s available/degraded/failed distinctionsMaintenanceDiagnosisFrame: ask which current device-state distinctions govern diagnosis; use this organization for the maintenance diagnosis; for a redesign-capability question, return to CapabilityRedesignFrame.
DeviceCapabilityModelUseStructureconstituents CapabilityModel-6 and DeviceSubsystem-2; applicability of CapabilityModel-6 to DeviceSubsystem-2 within RedesignClaimScope; selected ModelUseRelation established by F.6 performedUnderAssignment(CapabilityRedesignWork-44, RedesignAssignment-15) plus actual use during that Work; coherence of CapabilityModel-6 and CapabilityDesignExpression-12 under CapabilityDesignCoherencePredicate and CapabilityDesignReferenceScheme; applied claim RedesignScopeUseConstraintClaim says every design slice used in the redesign analysis satisfies member(slice, RedesignClaimScope), and CapabilityDistinctionConstraintClaim says the analysis preserves current-versus-proposed capability distinctionsCapabilityRedesignFrame: ask which capability distinctions govern the proposed redesign; use this organization for redesign analysis; for a maintenance-diagnosis question, return to MaintenanceDiagnosisFrame.

An exact C.2.1 EpistemeEditionRelation may separately establish historical continuation; it does not merge simultaneous organizations. Near miss: if either side lacks its coherence occurrence, an applied constraint, or its complete frame, that side has useful applicability and use facts but no selected BoundedModelUseStructure yet.

One model, two use loci. Use the following constructed case. A.1:4.2 recognition and the kind-specific admission of both use loci are supplied premises of the model-use comparison.

PatientEncounter-42 : U.Work is one clinical consultation performed by ClinicalTeam-4 from 09:00 to 09:20 on CaseDay-1 in Clinic-A, enacting ConsultationMethod-2. The case supplies the team’s A.13 performer basis and the obtaining performer, Method and containing-System relations required by A.15.1. The actual performance history and its four-dimensional extent reidentify this encounter under A.15.1.

ReimbursementClaim-42 : U.Episteme has fixed claim content: the consultation in PatientEncounter-42 was completed and reimbursement of 50 account units is requested under BillingScheme-1. Its EntityOfConcern is that encounter; its effective ReferenceScheme is BillingScheme-1, which fixes the meanings of the service and account units. This claim content, EntityOfConcern and scheme fix the episteme’s C.2.1 identity. Its A.1 recognition is supplied independently of the terminology use below.

ClinicalTerminologyModel-7 participates in these two independently complete non-software structures:

Selected structureConstituents, relation occurrences, and applied constraintsNamed selection-use frame
DiagnosisTerminologyModelUseStructureconstituents ClinicalTerminologyModel-7 and PatientEncounter-42; applicability within DiagnosisClaimScope; selected ModelUseRelation established by F.6 performedUnderAssignment(DiagnosisWork-7, DiagnosticianAssignment-4) plus actual use concerning PatientEncounter-42; coherence of the model and DiagnosisExpression-11 under DiagnosisTerminologyCoherencePredicate and ClinicalTerminologyReferenceScheme; applied claim DiagnosisScopeUseConstraintClaim says every encounter slice used in the diagnosis claim satisfies member(slice, DiagnosisClaimScope), and ClinicalMeaningConstraintClaim says a clinical finding is not inferred from a billing codeDiagnosisUseFrame: ask which terminology distinctions govern this diagnosis; use the selected organization for the diagnosis claim; for a billing-code question, return to BillingUseFrame.
BillingTerminologyModelUseStructureconstituents ClinicalTerminologyModel-7 and ReimbursementClaim-42; applicability within BillingClaimScope; selected ModelUseRelation established by F.6 performedUnderAssignment(BillingWork-9, BillingAssignment-9) plus actual use concerning ReimbursementClaim-42; coherence of the model and BillingExpression-14 under BillingTerminologyCoherencePredicate and ClinicalTerminologyReferenceScheme; applied claim BillingScopeUseConstraintClaim says every reimbursement slice used in the coding claim satisfies member(slice, BillingClaimScope), and CodingMeaningConstraintClaim says the selected reimbursement code does not assert a clinical diagnosisBillingUseFrame: ask which terminology distinctions govern this coding claim; use the selected organization for the coding claim; for a clinical-diagnosis question, return to DiagnosisUseFrame.

Across these five filled structures, each expression episteme is a participant of the selected ModelExpressionCoherenceRelation. A replacement with different claim content gives another <M,E,P,R> tuple to evaluate and reopens the selected-occurrence discriminator (sections 4.2–4.3). Each assignment occurrence and the dated Work in which the model is used stays only in its selected ModelUseRelation and in the evidence establishing that occurrence. Changing either one reopens that relation and therefore the selected-occurrence discriminator; it is not also an independent constituent replacement. Replacement of PatientEncounter-42 reopens the constituent discriminator.

One spanning structure is available only when one exact constituent plurality, relation-occurrence organization, applied-constraint set, and selection-use frame together span both uses. Shared model identity alone neither merges nor splits them. Near miss: exact diagnosis and billing Work plus a shared model, without one side’s coherence occurrence or filled frame, supports only the direct facts on that side.

Published classification model. The published NAICS model is an episteme. F.6 performedUnderAssignment(ClassificationWork-4, ClassificationAssignment-3) and actual use of that model content concerning an organization supply the use branch. A positive NAICSClassificationModelUseStructure additionally needs exact applicability with ClassificationClaimScope as that relation’s scope participant, fixed-content coherence with the classification expression, exact applied constraint claims stating which edition and classification distinctions the judgment must preserve, and NAICSClassificationFrame: ask which NAICS edition and distinctions govern this classification; use the complete organization for the classification claim; without the complete basis, stop at publication availability or the direct relation that actually obtains. The bare scope or one membership result is not an applied constraint.

When a proposed directional dependency is called Conformist, retain its source, target, direction, required fit, permitted loss, and claim scope. Return missing CROSS-LOCALITY-BRIDGE governor until a compatible direct relation exists.

Stale description. An already recognized Context Map view is six months old while the same already governed applicability, actual-use, and model-expression-coherence relations continue. Its currentness claim can become obsolete; revising the U.View episteme or publishing another rendering changes those epistemic and publication objects only. Reidentify each structure using all four discriminators and the continuity rule in section 4.3.

Context-mapping case. Apply the method, product, view, and publication distinctions when the receiving claim depends on them.

  1. Method and Work. Architect-9 : U.System performs dated ContextMappingWork-14 : U.Work under ArchitectureAssignment-6. First recover Architect-9’s A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the Work from its performance history, enacted ContextMappingMethod-3 : U.Method, extent, and containing-System relation. Because this case explicitly attributes performance under ArchitectureAssignment-6, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Architect-9 as holder, and covers the Work. The repeatable Method and this dated Work remain different objects.
  2. Candidate product. C.2.1 independently identifies episteme ContextRelationsAnalysis-8. Its EntityOfConcern is the six-part proposed crossing organization: source, target, direction, required fit, permitted loss, and claim scope. The episteme is not the proposed organization.
  3. Current stop. No independent direct governor currently makes the proposed crossing obtain. A.22 therefore lacks the relation-occurrence discriminator needed for base identity, and the candidate episteme does not designate an exact member of the conditional crossing-analysis specialization. Stop at the proposed organization.
  4. Later positive route. Only if a future direct governor admits that exact crossing and all four A.22 discriminators are recovered may a corresponding C.2.1 episteme designate the resulting exact structure. Changing the EntityOfConcern remains subject to C.2.1 episteme identity.
  5. Source use and inception. If a current claim says ContextRelationsAnalysis-8 first existed through the mapping Work, A.15.PROD governs only that exact local inception claim. If source episteme ContextNotes-7 participates, C.2.P recovers its exact source expression and routes the source-use relation to its direct governor.
  6. View evaluation. Reviewer-6 : U.System performs ContextViewConformanceEvaluationWork-15 : U.Work under ContextViewReviewerAssignment-10. First recover Reviewer-6’s A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the Work from its performance history, enacted ContextViewConformanceEvaluationMethod-5, extent, and containing-System relation. Because this case explicitly attributes performance under ContextViewReviewerAssignment-10, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Reviewer-6 as holder, and covers the Work. Any result episteme and any A.15.PROD inception claim about that result remain separate. Under E.17.0, ContextRelationsAnalysis-8 becomes a U.View only when its declared conformance relation to ContextMappingViewpoint-4 obtains.
  7. Representation and publication stop. The product name, mapping method, performed Work, source use, evaluation result, representation, rendering, publication occurrence, form, and carrier grant neither crossing-structure identity nor U.View membership and remain under their direct patterns.

A.1.1:6 - Bias-Annotation

This pattern has a DDD lineage bias because bounded context is the source term. Outside software, use A.1.1 only when the domain has one claim-bearing model edition, explicit applicability, actual use in assigned Work, fixed-content expression coherence, and a present decision changed by their joint organization. Industrial control, clinical or billing terminology, and published classifications can meet that test through different direct governors; a familiar context label cannot.

It has a structure-selection bias. The lightweight stop rule prevents mere local terminology, model mention, or implementation and organizational partition from becoming a structure without the required model-use relation organization.

It also has a model-coherence bias. Actual systems, work, methods, transformations, epistemes, and system-role-assignment occurrences keep their own identities and can remain the referents designated by receiving epistemes when the joint relation organization is not the subject of the receiving use.

A.1.1:7 - Conformance Checklist

  1. A positive BoundedModelUseStructure exposes all four A.22 discriminators: exact constituents, exact selected obtaining applicability/use/coherence occurrences, exact applied constraints, and one named question/action/stop-or-return selection-use frame.
  2. For each claimed relation occurrence, establish that the corresponding obtaining conditions in WF-A1.1-APP, WF-A1.1-USE, or WF-A1.1-COH hold; any imported-sense receiving use additionally satisfies WF-A1.1-APP-USE or WF-A1.1-COH-USE. Missing conditions return the named stop rather than a positive assertion.
  3. Every ModelExpressionCoherencePredicate value satisfies the local five-part membership and value-identity rule. Every ModelExpressionCoherenceRelation occurrence is participant-determined by <model episteme, expression episteme, predicate value, comparison scheme> and has no interval discriminator.
  4. BoundedModelUseStructure is governed as U.Structure; its identity uses the four A.22 discriminators and their continuity rule.
  5. Reidentification compares all four discriminators and then applies A.1.1:4.3. A changed applied constraint or changed question/action/stop-or-return frame reopens identity even when constituents and relation occurrences are unchanged; an altered explanation reopens a discriminator only if it changes an applied constraint or frame value; a changed page, graph, rendering, or publication does not.
  6. Semantic locality follows the direct-value triage in A.1.1:4.4. A local rule, inference, unit, evidence use, or status use remains at its exact subject pattern; a broad label or unrepaired generic-context field cannot manufacture the missing participant.
  7. A description episteme designates its exact EntityOfConcern under C.2.1. When a description claim needs empirical grounding, recover one exact obtaining EpistemeEmpiricalGroundingRelation.
  8. DDD Context Mapping is recovered as method, dated Work, claim-bearing product, proposed or obtaining crossing organization, view conformance, representation, and publication under their separate subject patterns. WF-A1.1-CROSS blocks a positive cross-structure member while the direct crossing governor or an A.22 discriminator is missing.
  9. A code/schema cue is classified from the exact claim as claim-bearing episteme content, repository/file/form/carrier, or deployed system/structure; the cue itself supplies no common kind.
  10. Two model uses over one subsystem yield two structures only when each independently supplies all three obtaining relation families, applied constraints, and its exact selection-use frame. Missing coherence or another discriminator leaves that side at its direct relations.
  11. Use the structure only when its joint organization changes a receiving decision. The reader can name the admissible action and the stop or return condition.

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

Anti-patternFailureRepair
Context holonNearby systems, Work, and epistemes become parts of one extra whole.Keep their direct identities; select only the decision-relevant relation organization as U.Structure.
Subsystem shortcutLocation or team ownership identifies the bounded context.Recover all four A.22 discriminators. One subsystem can support several model-use structures.
One-relation or missing-frame shortcutApplicability or actual use alone is expected to carry coherence, constraints, or the selection decision.Stop at the direct relation until all three relation families, applied constraints, and one exact frame are current.
Description or publication substitutionA map, code repository, schema file, view, or publication is treated as the model-use organization or an occurrence.Classify the exact content, carrier, system, structure, and publication claims under their subject patterns.
Locality inflationA term, rule, unit, evidence use, or status use gets a context or structure proxy.Apply the A.1.1:4.4 triage and keep the direct governed value or relation.
Crossing by labelMapped, Conformist, or shared wording is treated as an obtaining structure crossing.Preserve the proposal and apply WF-A1.1-CROSS; stop until the direct crossing governor exists.

A.1.1:9 - Consequences

Benefits. Teams can compare model-use boundaries without inventing an enclosing whole. Competing models over one subsystem and one model across several loci become expressible through complete structure bases. Local vocabulary, rules, inferences, units, evidence use, and status use remain recoverable through subject patterns rather than a context proxy.

Costs. A load-bearing structure claim must recover three direct relation families, exact applied constraints, and one question/action/stop-or-return frame. Semantic transfer sometimes stops at a subject pattern that still cannot express the claim without a generic context field; that stop preserves the known participants and relations while the missing predicate is repaired.

Limits. A.1.1 does not decide model truth, local system-role-kind classification, system-role-assignment occurrence or state, a relation among system-role kinds, rule validity, measurement, status, evidence, claim-scope membership, reference-scheme construction, system parthood, Work performance, release authority, or publication currentness. Its own predicates define model applicability, actual model use, and model-expression coherence; the joint organization is selected only when the required direct claims are available.

A.1.1:10 - Rationale

The selected object must survive two decisive tests. Two independently complete model-use organizations over one subsystem need distinct bounded contexts without duplicating the subsystem. One model coherently used across several loci may need one bounded context without pretending those loci are parts of another whole. A dependent U.Structure over exact relations passes both tests.

The practical DDD lesson retained here is that boundaries matter because model applicability, actual use, expression consistency, and relationships can change engineering decisions. FPF does not copy that sentence as one ontology: it separates participant-determined fixed-content coherence from maintenance Work, identifies each bounded model-use structure without crossings, and includes an independently obtaining crossing only as a selected relation occurrence in a distinct A.22 structure over already identified endpoints.

A.1.1:11 - SoTA-Echoing

The source line is not one settled ontology. The 2015 reference defines a bounded context as a description of a boundary. The January 2026 worked case also uses the term for an actual system part and for use of the published NAICS model. FPF keeps those three readings distinct instead of choosing one of them as a universal context object.

Source line and currentnessWhat the source saysPractical problem changedFPF adaptationScope and limits
Eric Evans, Domain-Driven Design Reference, 2015 — historical lineageA bounded context is a description of a boundary, typically a subsystem or one team’s work, within which one model is defined and applicable. The pattern then asks practitioners to set actual boundaries in team organization, application use, code bases, and database schemas and to keep model concepts and terms consistent.A boundary description cannot stand in for the systems, Work, model edition, expressions, or applicability facts that an engineering decision depends on. Several models at one locus must not be mixed merely because one description names the locus.Keep the boundary description as a C.2.1 episteme. Recover actual participants under their direct patterns and use A.1.1 only when the organization of independently governed applicability, actual-use, and fixed-content coherence occurrences changes the decision. A source mention of relationships does not create a structure crossing.This historical source neither supplies BoundedModelUseStructure nor declares A.1.1’s three relation kinds.
Evans, Context Mapping with an AI-based Component, 6 January 2026 — current AI-component worked caseIn this case a bounded context corresponds to an actual part of the system; NAICS is treated as a distinct bounded context and a Published Language; and an honest context map must show the system as built rather than a wished-for design.The same practice term reaches both a concrete system part and use of a published model. A map can also describe a proposed arrangement that the actual system does not yet realize. Treating all three as one kind would hide the difference between world-side use, model publication, and a claim-bearing description.Keep the actual system part as its own U.System; keep NAICS as a published model episteme whose actual use must be shown separately; identify a mapping product as an episteme about the described or proposed organization. Require E.17.0 conformance before calling it a U.View. A proposed crossing remains the six-part unsupported-use record until a compatible direct governor makes that exact crossing obtain and A.22 can identify the resulting structure.This one worked AI-integration case does not establish a universal identity rule for every bounded context, an A.1.1 relation signature, or an obtaining crossing.
Florio and Linnebo, Introduction to Constructional Ontology, 2024; Borgo and Righetti, Towards Applied Constructional Ontology, 2025 — current but exploratory constructional lineThe 2024 line separates constructors, admissible inputs, constructional process, and output identity. The 2025 study makes a first exploratory comparison with BFO, DOLCE, and UFO and says that successful application to current foundational ontologies still needs further investigation.Co-occurring model-use participants and relations do not by themselves warrant another constructed whole. A claimed context holon must show its constructor, admitted inputs, construction, and identity rather than borrow them from a label or diagram.Use constructional ontology only as a stress test for a construction claim. Failure to supply that construction basis blocks admission of a new context holon; it leaves the already governed participants and relation occurrences available for an A.22 structure-selection question.The sources do not prove that the selected object is U.Structure, do not declare A.1.1’s three relations, and do not prove a general negative conclusion about every possible context whole.
Current FPF A.22 selected-structure disciplineA structure is a selected relation organization over a declared substrate, exact applied constraint claims, invariants, and a decision-facing use. It is not a holon, view, or representation by form.Practitioners need to reason about a useful organization without duplicating the actual systems, Work, and epistemes as parts of another whole.Test whether the already governed A.1.1 relation occurrences and exact applied constraint propositions form one decision-relevant BoundedModelUseStructure; keep each U.ClaimScope only in its applicability occurrence unless a separate constraint claim refers to it, and preserve every substrate and occurrence identity.BoundedModelUseStructure and the exact three-relation architecture are the scoped FPF synthesis stated below, not an entailment of the external sources.
Current FPF C.2.1, A.2.6, A.10, B.3, E.17.0, E.24.PUB, C.29, and F.9C.2.1 identifies epistemes and their effective reference schemes; A.2.6 defines claim scope and slice membership; A.10 handles ordinary bounded evidence reliance; B.3 is used only for a named assurance claim and its bounded result; E.17.0 tests conformance-dependent U.View membership; E.24.PUB handles publication occurrence and bounded availability; A.6.3.RT establishes which operation a change of representation language or reasoning medium supports, and A.6.3.RT.OE:4 constructs the expression needed for it; C.29 adds the mathematical-lens correspondence and inference conditions when needed; F.9 identifies Bridges between exact F.17 SchemeSenseCell values.A model, its scope, a use claim, evidence reliance, assurance, a view, a representation, a publication, and an interpretation Bridge can otherwise be collapsed into one “context” or used as proxies for world-side relation occurrences.State each object and claim under its exact predicate or invariant, using the pattern only as a locator. For an A.1.1 comparison across schemes, first require the obtaining F.9 Bridge, then the separate affirmative C.2.1 claim about the exact comparison use and its current A.10 reliance basis and, when a named assurance claim is at issue, its B.3 AssuranceResult; recover any comparison Work, assertion, publication, direct relation, or operation application only under its own pattern. For a proposed structure crossing, preserve source, target, direction, required fit, permitted loss, and claim scope, then stop at missing CROSS-LOCALITY-BRIDGE governor until a compatible direct relation kind exists.A publication or representation change alone does not change a world-side structure.

Synthesis and applicability limits. The working hypothesis is that, for the bounded uses declared here, the decision-relevant organization is one BoundedModelUseStructure over exactly the three direct relation kinds ModelApplicabilityRelation, ModelUseRelation, and ModelExpressionCoherenceRelation, its exact model-use substrate, exact applied constraint claims, and named frame. Each claim scope remains only the applicability-relation participant unless a distinct applied constraint proposition refers to it. Crossings belong only to a distinct A.22 structure over already identified bounded model-use structures. This organization is usable only while each direct relation has coherent participant meanings, an obtaining rule, and an occurrence-identity rule, each applied constraint proposition is recoverable, and selecting their joint organization changes a concrete practitioner decision.

Stop applying this organization to the affected case and recover the missing or different contribution when:

  1. any one of the three direct relations lacks coherent participant meanings, a coherent obtaining rule, or a coherent occurrence-identity rule;
  2. a DDD case needs a materially different relation organization rather than this three-relation organization; or
  3. selecting the joint organization changes no practitioner decision compared with stopping at the direct relations.

The external sources therefore change recognition and the tests applied to the working problem. Current FPF direct governors and the scoped, defeasible synthesis above supply the normative Solution. Constructional ontology tests a construction claim; it neither chooses the FPF kind nor proves the no-holon conclusion by citation.

A.1.1:12 - Relations

  • A.1 governs constructive recognition of exact candidates under already admitted holon kinds and its locally declared U.System/U.Episteme distinctions. Direct identity patterns define or constrain candidate identity; E.24.UK governs public-kind admission; A.14 and direct part-relation patterns define or constrain parthood; C.13 governs constructive assembly.
  • A.22 governs base U.Structure identity through exact constituents, selected obtaining relations, applied constraints, and one named selection-use frame. It also governs the conditional cross-structure question after a direct crossing governor exists.
  • C.2.1 governs model, expression, rule, inference, and description episteme identity, effective reference schemes, exact EntityOfConcern and ClaimGraph content, EpistemeEditionRelation, and empirical grounding. It also identifies the separate bounded-use claim about an F.9 Bridge.
  • A.2.6 governs U.ClaimScope, U.ContextSlice, and membership. C.16 governs measurement bases, readings, scales, units, and direct comparability. A.2.4 and A.10 govern evidence use; F.10 governs status family and status use; B.3 governs assurance.
  • A.2 distinguishes local system-role kinds and their classifications. A.2.1 defines and tests U.SystemRoleAssignment species, occurrences, and states; A.2.7 defines and tests any separately needed relation among system-role kinds in model-use loci. E.10.ROLE routes any other technical use of role before one of these claims is selected.
  • A.3.1, A.15.1, and E.18 govern Context Mapping method, performed mapping Work, and transformation-flow structures. A.15.PROD enters only for a separately needed local entity-inception claim.
  • F.17 and F.18 govern sense cells, durable public labels, candidate-name history, public rows, lineage, and name refresh. A.1.1 uses the settled names.
  • F.9 defines an obtaining Bridge between exact F.17 SchemeSenseCell values. A Bridge carries relation semantics, not a receiving-use decision or a structure-to-structure crossing. A separate C.2.1 claim states bounded suitability. A.10 handles ordinary reliance; B.3 adds a bounded result only when a named assurance claim is at issue.
  • E.17.0 governs view conformance; E.24.PUB governs publication through a particular expression and carrier, with a reusable form when selected. Use A.6.3.RT when a change of representation language or reasoning medium enables the needed operation. A.6.3.RT.OE:4 constructs a suitable expression. C.29 applies when mathematical representation and inference are needed.
  • C.2.P recovers an exact source expression and routes any source-use relation to its direct governor.
  • A.6.0 and A.6.5 govern the RelationSignature and SlotSpecs declared here; A.6.REL governs progressive explicit individuation after the direct relation kind, obtaining condition, and occurrence-identity rule exist.

A.1.1:End

A.1.SCR - Finding the Acting or Changed System

Type: Part A practitioner application pattern Status: Stable Normativity: Normative unless marked informative

Plain name. Find the system that acts or is intended to change.

A.1.SCR:0 - Practitioner entry

Use this when. Use this pattern when a decision depends on which system acts, is intended to change, carries a capability, persists through a lifecycle, or is being considered for the project system-of-interest role or as a local subject—and the proposed subject is still unclear. Ask: Which system acts or is intended to change here, and what decision depends on treating it as a system?

First useful move. State the claim, the proposed actor or change bearer, and what you will decide differently if it is or is not a system. If the phrase already names Work, a Method, capability, transformation, episteme, structure, or a direct relation and your decision does not depend on systemhood, name that object and leave through its subject pattern. Apply the complete A.1 criterion only in the system-dependent branch.

Recognized case. A maintenance decision asks whether Pump #37 or the larger pumping assembly must be isolated before repair. A.1:5.1 supplies the pump’s complete construction basis: constituents, part relations and assembly, reidentification through seal replacement, a composition-grounded pumping characteristic, compatibility with a governed larger assembly, and acting eligibility. The first result is: Pump #37 is the recognized U.System to which the repair is addressed. Use the applicable isolation rule with its boundary and connections to decide which assembly must be isolated.

Subject-pattern and proposed-system readings. “We develop the surgeon’s mastery” ordinarily concerns the person and their actual ability, training Work or evaluation. Use A.2.2 for the ability under stated conditions; an account of it has that independently identified person as its subject. Training can change the ability while the report stays unchanged; editing the report alone changes no ability. Select the assertion episteme as subject only when the question concerns that assertion.

If the source instead proposes the physically or operationally realized whole SutureControl-M17, identify that U.Entity and evaluate it—not a substituted surgeon or capability—under the already admitted U.System kind. Choose the reading on which the current decision depends.

Near-identical non-system case. PumpKit-37 contains parts of the same types and carries the same product label, but its constituents are not assembled by the required part relations, it has no composition-grounded pumping characteristic, and it cannot participate in the plant installation while preserving pump identity. The first result is: the kit is not the pump system; the current subjects are the material collection and its description.

Unknown case. WorkshopController-9 is a boxed device, but the team cannot recover its internal assembly, reidentification rule, or operating boundary. The evaluation is unknown and names those missing inputs; the decision that assumes an acting controller remains blocked. The entity itself satisfies or fails the criterion independently of current knowledge.

What this buys. A real actor, change bearer, lifecycle subject, capability holder, or proposed project system of interest gets a tested identity and boundary. A direct Work, Method, capability, structure, episteme, or relation question leaves immediately without an unnecessary A.1 evaluation. Continue through A.1.STM when the shared project SoI and intended-use basis, or this result’s connection to it, remains unresolved. Recognition alone does not require traversing the long map.

Not this pattern when. If the subject and its admitted kind are already clear, use the subject pattern of the claim. If service or access wording hides a promise, participant, bearer, permission, Work occurrence, status, evidence, or direct relation, begin with A.6.P §4.11a. Enter A.1.SCR from that route only when the repaired claim itself depends on whether the entity recovered by A.6.P—a bearer or access-providing arrangement—is a system. If only a name for an already recoverable object is unclear, use F.18.

A.1.SCR:1 - Problem frame

Familiar nouns can pull attention toward the wrong system or erase a supported proposed-system reading. Mastery may name a capability or the physical/operational whole SutureControl-M17. Session may name Work, an interval, a record, or GameSessionWhole-GS204. Access may name promise, permission, state, bearer, Work, or InternetAccessArrangement-CA17. Program may mean code, a Method, an intended designator, a deployed realization, or a run. The engineering cost is a wrong actor, identity boundary, change bearer, capability holder, or project system-of-interest—and the same error occurs when a convenient neighboring referent replaces the entity before A.1 evaluates it.

A.1 is the pattern for constructive recognition under admitted holon kinds. A.1.SCR does not relax or duplicate that criterion. It tells the practitioner when the complete test is worth doing, permits an immediate subject-pattern exit when it is not, and returns one result tied to a concrete decision.

A.1.SCR:2 - Problem

The following errors obscure the subject needed by the decision:

  1. classify every unusual noun before asking what the decision needs;
  2. treat wording, physical embodiment, a system-role label or assignment, or a record as proof of systemhood;
  3. stop at a list of PatternIDs without naming the actor or change bearer;
  4. infer designation as the project system-of-interest from recognition or from being affected by Work;
  5. reject a system reading without naming the actual Work, Method, capability, structure, episteme, or relation that remains useful.

A.1.SCR:3 - Forces

ForceTension
Useful entry vs classification ritualA.1 is rigorous, but many subject-pattern questions do not depend on systemhood.
Familiar wording vs identityA noun can retrieve a case but cannot identify an entity, boundary, or kind.
Physical grounding vs kind collapseEmbodiment helps locate a subject but does not identify it with a local system-role kind or assignment, capability, Work, or description.
Project intent vs actual existenceA designator or selection among alternatives is not yet an acting system.
Positive action vs uncertaintyMissing construction facts must block the affected decision without creating a third ontic state.
Reusable cases vs taxonomyThe examples teach one move but do not form a common kind.

A.1.SCR:4 - Solution

A.1.SCR:4.1 - State the system-dependent decision

Start with four plain statements:

  1. the claim you are trying to use;
  2. the entity proposed as actor, change bearer, capability holder, persistent subject, or project system-of-interest;
  3. the decision or action that would differ if this entity were or were not a system; and
  4. the observation, boundary fact, or construction fact that would settle that difference.

Keep a proposed system reading of a phrase separate from the entity being evaluated under U.System. Name the entity as soon as it is recovered. When a named project plan or decision compares possible referents for designation as the project system-of-interest, state that proposed designation separately from system recognition.

A.1.SCR:4.2 - Take the subject-pattern exit first

Before testing systemhood, ask whether the current decision already concerns one of these objects:

Current objectSubject pattern or exit
Holder-dependent capabilityA.2.2
Local system-role kind or obtaining system-role assignmentA.2 and A.2.1
Reusable way of doing or its descriptionA.3.1 and A.3.2
Intended workA.15.2 U.WorkPlan
Dated performed occurrenceA.15.1 U.Work
Actual bounded changeA.3.4 and the exact transformation pattern
Claim-bearing model, rule, report, code, or other epistemeC.2.1
Selected structure or transformation-flow structureA.22 or E.18
Promise, commitment, speech act, or permission resultA.2.3, A.2.8, A.2.9, or A.2.8.PER
Service/access referent, status, evidence, evaluation, delivery, acceptance, or other relationA.6.P §4.11a and then the exact subject pattern

If this result answers the decision, stop here. Name the object, its subject pattern, and what you can now do. Do not apply A.1 as a recurring project ritual. This is a local stop: it neither supplies nor removes the shared SoI and use hypothesis required for a systemic project account. Use A.1.STM when that common basis or the local result’s connection to it is the question.

If a needed relation has no current governor, state the exact participants and blocked receiving use, return missing-governor[...], and continue under A.6.RCD. Do not substitute relatedTo, a graph edge, or a local bundle.

A.1.SCR:4.3 - Apply A.1 only when systemhood remains load-bearing

When the decision still depends on systemhood, recover all six A.1 constructive components. A.1 supplies the criterion.

A.1 componentPractical recovery question
EntityWhich one entity is being tested, and what identity rule distinguishes it from its name, description, parts, environment, and successor?
ConstituentsWhich entities actually constitute it rather than merely being nearby, listed, sampled, or described with it?
Constructive part relations and assemblyWhich obtaining part relations and assembly make these constituents this whole?
Reidentification ruleWhich changes preserve it, and which replacement, disassembly, completion, or termination ends it?
Composition-grounded whole-level characteristicWhich characteristic follows from the actual assembly rather than from a label, plan, measurement, or one constituent?
Possible participation in a larger constructive assemblyWhich boundary, interfaces, relevant characteristics, and identity-preservation conditions satisfy the applicable governed construction rule?

Then apply the already admitted U.System condition: the whole has an actual physical or operational organization through which it can causally participate in Work or transformation while preserving identity.

A.1.SCR:4.4 - Return one decision-bearing result

DispositionRequired first result
Subject-pattern resultObject or relation, the claim needed for the decision, the cited subject pattern’s concrete contribution, and the action now possible; no A.1 test.
System recognizedSystem, identity and boundary, decisive construction facts, acting-eligibility basis, and the system-dependent next use.
Proposed system reading rejectedNon-system subject or relation, its subject pattern, and the action that remains possible.
Evaluation unresolvedU.Entity, missing A.1 component or kind-specific condition, needed information, and the decision that stays blocked.

SubjectPatternLocator locates the cited pattern; in ordinary prose, cite its PatternID. Add exact predicate or defining-content references, including a defining episteme edition or ClaimGraph, only when the governing claim or a named receiving use requires them (C.2.1 §4.2.4).

After one candidate bearer is recognized, rejected, or left unresolved, use A.1.CSD only when the current question is which other Systems may undergo relevant changes and that discovery can change a named decision or investigation. A.1.SCR does not generate the bearer set or qualify consequence paths; it supplies only the load-bearing recognition result or blocker.

Persist a classification assertion or evaluation-result episteme only when another use must inspect or cite it; C.2.1 is then the pattern for that episteme. true | false | unknown describes an evaluation and changes no kind extent.

A.1.SCR:4.5 - Add only the neighbors used now

After the first result, add only claims consumed by the decision. Shared extent, one carrier, a common label, or co-occurrence establishes none of their identities or relations.

A.1.SCR:4.6 - Keep service/access recovery independent

When service or access wording is the unresolved phrase, start in A.6.P §4.11a. A.6.P names the service-provision Work, Method, PromiseContent, system-role assignment, bearer, access-providing arrangement, permission, status, or direct relation. Use A.1.SCR only if the repaired sentence makes a separate system-dependent assertion about the entity recovered there—a bearer or access-providing arrangement.

“My service stopped” does not by itself say that a system stopped. Service-provision Work may have ceased, a deployed or physical bearer may have stopped or become unavailable, an access-providing arrangement may be proposed as the system whose functioning stopped, or promised availability/fulfilment may have failed. Use A.1.SCR only to test a separately proposed bearer or access-providing arrangement when its system boundary matters to the decision.

A.1.SCR:4.7 - Connect recognition to the project SoI

The system-of-interest (SoI) is the system whose intended use and expected benefit give the relevant cooperation of creators its common purpose. A.1.STM:4.1 distinguishes it from the system-in-hand, the system locally being investigated or changed. An organization can be that engineering subject while its product or products remain the SoI. A machine or component supplied as a usable product can be the SoI of its own product undertaking under the receiving-use and fitness obligations explained there.

Recognition under A.1 establishes the System; the cooperation’s purpose and designation need their own basis. One project can concern several systems and other results, while this recognition question tests the entity on which the current claim relies.

A plan or decision can designate the project SoI or select a local subject. Recover which claim is current and keep these questions separate:

  1. identify the actual System, or keep an intended future holder as a designator in plan, decision or description content;
  2. recover the designation and intended use; when common project purpose is claimed, recover the participants’ working agreement rather than infer it from the designation alone;
  3. admit composite project Work only after A.15.1 and A.15.6 qualifications hold;
  4. state each actual work-to-referent, transformation, production, evaluation, delivery, acceptance or later-use fact under its own governor;
  5. test any technical system-role classification and A.2.1 assignment separately; a local SystemOfInterestSystemRole criterion using this Library meaning must express the product-use and cooperation basis, rather than select any system being investigated or engineered; and
  6. use A.1.STM when the recognized System or a local result must be connected to the common SoI’s intended use. If that basis is already supported, its section 4.4 retains the narrower route: locate the first unsupported dependency, use its subject pattern, and return the answer or a named stop.

For example, a production team can recognize the factory as the actual System whose layout and capabilities it is changing. That recognition supports organizational engineering without making the factory the SoI of those works. The usable machines it must supply remain the product SoI. The project can close when sufficient evidence supports the factory’s agreed capability under A.1.STM:4.1.1. A prospective factory design still describes an intended system, and recognition remains open until its actual identity grounds hold.

A future SoI or a series of intended instances can likewise be described before any actual holder exists. Agreement about the SoI role and required kind of holder is not recognition of an individual System. A.1.STM:4.2 keeps these prospective and actual claims distinct.

For a claim about a particular dated Work occurrence, first identify every actual performing System and recover its A.13 core. Independently admit that occurrence under A.15.1 from its performance history, at least one Method actually followed, temporal extent, and at least one locally declared containing-System relation. Apply this branch to the occurrence being asserted, whether it is Work represented on the map or a separately asserted Work of using the map.

After admission, add F.6 only when the receiving claim also needs precise assignment-bound attribution through that performer’s same obtaining assignment. A Work-only claim may stop after admission.

Infer no project designation from system recognition, affectedness, familiar wording, a system-role label, or shared realization. When a decision needs one compound claim connecting the project designation with independently established Work, change or use facts, apply A.15.6:4.1a. Return missing-substrate[project-selection-conjunction] only when the needed operator semantics are unavailable; preserve the designation and direct facts.

A.1.SCR:4.8 - Use physical grounding without cross-kind identity

Ask what physically or operationally exists, where its boundary lies, and what preserves or ends its identity. This pressure helps test a proposed system reading and reject description-only substitutes.

A.1.SCR:5 - Archetypal Grounding — Seven Heterogeneous Worked Cases

These examples distinguish readings that need A.1.SCR from readings handled directly by another pattern.

Source phraseFirst useful result and routeNext move and governed additionsNear miss or stop
“We develop the surgeon’s mastery.”Keep the surgeon’s capability, training Work, and evaluation under their subject patterns. If the phrase instead proposes the physical or operational whole SutureControl-M17, identify that entity and use A.1 only when its systemhood changes the decision.Add training Method, dated Work, evidence and evaluation, and any actual change only when the named decision needs those claims; keep the subsystem and capability distinct.Curriculum, badge, report, system-role kind or assignment, capability, surgeon, and SutureControl-M17 are not interchangeable; do not substitute the surgeon before evaluating the proposed whole.
“We release a game session.”Keep composite dated Work, interval, and session record under their subject patterns. If the phrase instead proposes GameSessionWhole-GS204, identify that operational whole and use A.1 when its boundary, persistence, or acting eligibility matters.Recover every actual performer’s A.13 core and admit Work only with the full independent A.15.1 basis and exact work-part relations; add F.6 afterward only when this claim also needs precise assignment-bound attribution. Evaluate the operational whole through its constituents, assembly, authoritative-state continuity, larger-game compatibility, and acting eligibility. Keep player systems, deployed installation, rule episteme, interval, activities, and records separate.A label, shared interval, lobby record, or rules document establishes neither systemhood, Work, parthood, nor identity between the Work and the operational whole.
“We sell internet access.”Start in A.6.P with promise, permission, state, bearer, commercial relation, or other subject-pattern readings. If the phrase instead proposes InternetAccessArrangement-CA17, preserve that entity and use A.1 only when the arrangement’s systemhood matters.Add Method or MethodDescription, WorkPlan, permission, provisioning Work, system-role assignment, commitment, status, evidence and evaluation, fulfilment, and acceptance only when the named decision needs those claims; evaluate the arrangement separately from its gateway and status.No U.Access or generic AccessRelation; credentials, system-role labels or assignments, endpoints, promises, plans, evidence, connections, states, and bearers remain distinct and cannot replace the arrangement before A.1 evaluation.
“We develop a program.”Distinguish code/episteme, computational Method, intended designator, deployed realization, and run. Use A.1.SCR only when a decision depends on the deployed realization acting, persisting, or changing as a system.Add MethodDescription, planned or actual Work, transformations, and project system-of-interest designation only when the named decision separately asserts them.Code, algorithm, deployed system, run, and project designation are not one object.
“The salon creates a hairstyle.”Recover the intended hairstyle and its use. If the claim proposes an embodied hair-and-fastener whole as the SoI, preserve that entity for A.1 evaluation; keep a not-yet-existing hairstyle in description content. If the decision concerns only hair structure or characteristics, use those subject patterns.Add hairdressing Method, description, dated Work, transformation, affected-referent facts and acceptance when needed. A.1.STM connects the hairstyle’s use to these choices and distinguishes the salon as provider.A local structure or characteristic result may close its question. It does not establish the proposed SoI’s systemhood, remove the common SoI question, or justify replacing the proposed hairstyle with the client before evaluation.
“The surface needs a grind.”Name the workpiece or containing holon and the surface state, structure, and characteristics. Usually leave through those subject patterns without A.1.SCR.Add grinding Method, treatment Work, transformation, measurement, and acceptance only when the named decision needs them.A finish label is not an independent system, Work, or transformation.
“The batch moves through the flow.”Name the material batch under its collection or holon rule and separately the selected TransformationFlowStructure or FlowValuation. Use A.1.SCR only if a decision depends on whether the batch is an acting or changed system.Add movement/treatment Work, transformations, transfer relations, path/valuation, and evidence under their subject patterns.Recover an acting collective under A.1 only if that claim is current; for a claim that Work was performed, name its actual performer.

A.1.SCR:5.1 - Recognizing Systems at different scales

Apply the same six A.1 constructive components and acting-eligibility condition to each entity below. The table supplies bounded case inputs. true means the supplied inputs determine satisfaction; false means a required component fails; unknown names the missing input and blocks system-dependent reliance. For the sixth component, each positive case states one local larger-assembly condition and the fact that satisfies it. Establish other claims needed by the current decision under their subject patterns.

U.Entity evaluated under U.SystemResult under the case inputsCase-specific fact or next use
Pump #37true by reference to A.1:5.1: constituents, assembly, reidentification, whole-level pumping characteristics, larger-system compatibility, and acting eligibility pass.
Raven-17true: its skeletal, muscular, respiratory, nervous, wing, and feather constituents stand in obtaining biological part and organization relations; continuity of the same living raven through ordinary material turnover reidentifies it; flight and homeostasis are whole-level characteristics. The construction rule stated here for the larger Aviary-3 admits a living bird constituent only when it can cross the 1.5 m gate, remain within the 5 kg perch load, and retain organism identity through entry and exit; the case gives Raven-17 a 1.2 m span, 1.1 kg mass, and the same-living-raven continuity rule, so those conditions pass. Its physical organization is acting-eligible.
Engineer-4true: the embodied person has nervous, sensorimotor, metabolic, and musculoskeletal constituents under obtaining organism relations; continuity of the same living person through ordinary cellular turnover and changes of job, clothing, or tools reidentifies Engineer-4, while replacement by another person does not; coordinated perception, movement, and self-regulation are whole-level characteristics. The construction rule stated here for the larger BridgeInspectionTeam-2026 admits a person constituent only when the person can use the team’s spoken Channel-BR4 and Harness-H2 interfaces without changing personal identity; the case states that Engineer-4 can use both interfaces and remains the same person across the required clothing and tool changes, so those conditions pass. The physical organization is acting-eligible.
runtime whole DispatchAgent-12true for this runtime whole: one runtime process, authoritative state carrier, control loop, and tool adapters stand in obtaining control, data, and tool-link relations; continuity of the declared process boundary and authoritative-state lineage reidentifies the same running instance, while a separately initialized lineage does not; dispatch behaviour is whole-level. The construction rule stated here for the larger DispatchPlatform-DP4 admits one runtime whole only when its input boundary implements DispatchInput-v3, its adapters implement ToolPort-v2, and an allowed reconnect preserves the same authoritative-state lineage; the case supplies those two interface matches and that lineage-preserving reconnect, so the conditions pass. The operational organization is acting-eligible. Code or a model file is another object.
InspectionRobot-R7true: its chassis, sensors, controller, power unit, and drives stand in obtaining mounting, power, and control relations; the maintenance rule preserves identity across allowed component replacement but not replacement of the whole; sensing and motion are whole-level characteristics. The construction rule stated here for the larger PlantInspectionCell-7 admits one robot constituent only when mount M-R7, 48 V power, and InspectBus-v2 control interfaces all match and allowed component replacement preserves robot identity; this case supplies all three matches and the stated maintenance identity rule, so the conditions pass. Its physical/computational organization is acting-eligible.
BridgeInspectionTeam-2026; near miss: roster episteme BridgeInspectionRoster-2026true for the coordinated organization: named inspectors, equipment, and coordinating artifacts stand in obtaining membership, assignment, and coordination relations; the charter-and-coordination continuity rule reidentifies the team through permitted member substitution; inspection capability is whole-level. The construction rule stated here for the larger BridgeRenewalOrganization-2026 admits one coordinated team constituent only when its charter boundary exposes InspectionReportPort-BI and EquipmentHandover-BI and permitted member substitution preserves team identity; the case supplies both obtaining interfaces and the charter continuity rule, so the conditions pass. Independently grounded work-facing participation supports acting eligibility. false for BridgeInspectionRoster-2026: the episteme lists names but supplies no obtaining assembly or whole-level acting characteristic, so the proposed system reading for that roster and boundary fails.The team’s assignments and Work are independently grounded.
the Moon; neighboring tide case follows CoastalBasin-5true for the Moon: its crust, mantle, and core are constituents under obtaining material-part and gravitational-cohesion relations; continuity of the same gravitationally coherent astronomical body through ordinary surface impacts and mass exchange reidentifies it; orbital and gravitational characteristics are whole-level. The construction rule stated here for the larger EarthMoonOrbitalAssembly-1 admits one astronomical body constituent only when a direct dynamics account gives it a bound Earth-orbiting position and the body’s boundary and identity survive the ordinary impact and mass-exchange range; the case independently supplies that bound-orbit fact and the stated identity rule for the Moon, so the conditions pass. Its physical organization is acting-eligible. That direct dynamics fact, not systemhood, may separately give it an actor-side position. CoastalBasin-5 is instead identified by its shoreline, inlet, depth range, and persistence rule for the tide-related change; this row does not decide that bearer’s systemhood, and generic water identifies neither one referent nor a system.Use the dynamics account for the Moon’s causal participation; identify CoastalBasin-5 as the subject of the tide-related change.
SutureControl-M17, beside SuturingCapability@Surgeon-4true: NeuralController-17, ExocortexAid-3, and SensorimotorCircuit-4 are constituents under obtaining part and control relations; continuity of the learned-control profile through the allowed component-replacement rule reidentifies the whole; coordinated suture-control behaviour is whole-level. The construction rule stated here for the larger Surgeon-4-plus-tools assembly admits this control whole only when its boundary exposes matching NeuralLink-N17, AidControlPort-A3, and SensorimotorLoop-S4 interfaces and allowed replacement preserves the learned-control profile; the case supplies all three interface matches and that profile-continuity fact, so the conditions pass. Its physical or operational organization is acting-eligible.Evaluate the proposed SutureControl-M17 whole; use the subject-pattern exit in :0 for a claim about the surgeon’s capability.
GameSessionWhole-GS204, beside Work, interval, and record readingstrue: Player-A-GS204, Player-B-GS204, ClientRuntime-A-GS204, ClientRuntime-B-GS204, ServerRuntime-GS204, AuthoritativeStateCarrier-GS204, and two named client-server links are constituents under obtaining part/link relations and the stated session assembly; authoritative-state continuity plus the reconnect/terminal-close rule reidentifies the whole; interactive game-state evolution is whole-level. The construction rule stated here for the larger GameServiceAssembly-6 admits one session whole only when both links implement GameLink-v4, the server exposes SessionAuthority-v2, and reconnect keeps the same authority lineage until terminal close; the case supplies those link, authority, and lineage facts, so the conditions pass. Its operational organization is acting-eligible.Identify the play Work, interval or session record separately when that is the selected subject; this case tests the operational session whole.
InternetAccessArrangement-CA17, beside promise, permission, state, bearer, Work, and evidence readingstrue: CustomerTerminal-CA17, Gateway-7, ProviderEdge-CA17, LinkCarrier-CA17, and RouteController-CA17 are constituents under obtaining part/link relations and one operational assembly; circuit/account continuity plus allowed failover reidentifies the arrangement; end-to-end packet exchange is whole-level. The construction rule stated here for the larger ProviderDeliveryAssembly-CA17 admits this arrangement only when the terminal, gateway, provider-edge, carrier, and route-controller interfaces keep the same circuit/account through allowed failover and jointly meet availability at least 99.9%, latency at most 60 ms, and throughput at least 100 Mb/s; the case supplies those interface, continuity, and measured-threshold facts, so the conditions pass. Its operational organization is acting-eligible. A bare access-availability state has no constituents or assembly and fails only if substituted as the proposed whole; its bearer and state claim remain separately governed.Use A.6.P for service/access recovery. Gateway-7 remains a separately identified constituent and bearer.

Across all rows, first preserve the entity named by the proposed system reading.

A.1.SCR:6 - Bias-Annotation

Bias pressureMisreadingCorrection
Noun-induced systemhoodSession, service, program, or another familiar noun is treated as proof of a system.State the decision and proposed subject; use the subject-pattern exit or apply A.1 only when systemhood matters.
Classification ritualEvery unfamiliar phrase receives the complete A.1 test.Stop after a Work, Method, capability, structure, episteme, or relation answers the decision.
Temporary reading becomes ontologyRepeated testing creates a candidate kind or third ontic state.Keep one U.Entity; evaluation does not create kind membership.
Physical-realization identityShared material or extent identifies system, local system-role kind or assignment, capability, Work, transformation, Method, plan, evidence, or description.Apply each object’s direct identity rule.
Project-designation overreadA recognized or affected system is automatically called the project system-of-interest.Recover the product-use and cooperation basis under section 4.7 and the plan or decision designation. Keep system identity, local system-role classification and assignment separate.

A.1.SCR:7 - Conformance Checklist — Practical Checks

IDCheck
CC-A1-SCR-1The current claim, proposed actor/change bearer, and system-dependent decision are named before any A.1 test.
CC-A1-SCR-2A direct Work, Method, capability, transformation, episteme, structure, or relation result exits immediately when it answers the decision.
CC-A1-SCR-3The complete six-component A.1 criterion and acting eligibility are applied only when systemhood remains load-bearing.
CC-A1-SCR-4The first result names the direct object, recognized system, rejected reading, or unresolved evaluation and a concrete next move or stop.
CC-A1-SCR-5unknown remains epistemic and changes no world-side kind membership.
CC-A1-SCR-6Add a neighboring claim only under its subject pattern and only when the named decision needs that claim.
CC-A1-SCR-7Service/access ambiguity begins in A.6.P §4.11a and returns here only for a separate system-dependent claim about the entity recovered there—a bearer or access-providing arrangement.
CC-A1-SCR-8A missing relation preserves exact participants and dependent use and records the established A.6.RCD result missing-governor[...].
CC-A1-SCR-9A SoI designation has the product-use and cooperation basis in section 4.7 as well as its named plan or decision. The local system-in-hand, including an engineered creator, remains distinct. Recognition, designation, participants’ agreement, technical classification and assignment are supported at their own scopes.
CC-A1-SCR-10Physical grounding creates no cross-kind identity or unrestricted composition.

A.1.SCR:8 - Common Anti-Patterns and Repairs

Anti-patternWhy it failsRepair
Complete A.1 test before the decision is knownClassification work may change nothing.State what depends on systemhood; take the subject-pattern exit when it does not.
Pattern list without an actor/change bearerThe reader still cannot act.Name the subject and concrete decision.
Temporary reading treated as a kindEvaluation position becomes ontology.Keep one U.Entity under an admitted kind test.
Unknown as a third ontic stateMissing information becomes world-side indeterminacy.Name the missing input and blocked decision.
Neighbor bundleDifferent identity laws disappear.Return the subject first, then separately governed claims needed now.
Physical-realization identityCo-location or one embodiment merges kinds.Apply each identity rule and relation governor.
Project designation inferredRecognition or affectedness is mistaken for designation as the project system-of-interest.Recover the product-use basis and designation under section 4.7; test any local system-role classification and assignment separately.
Software service treated as systemSource-domain metonymy silently chooses a bearer.Begin in A.6.P, name the referent, and enter here only for a system-dependent claim.

A.1.SCR:9 - Consequences

The pattern makes full system recognition more useful by applying it only where identity and boundary change an engineering decision. It also makes subject-pattern results productive: Work, Method, capability, structure, episteme, and relations can close their own questions. The cost is that the practitioner must state the decision and may need to stop when construction facts or a relation governor are missing. A local non-System result remains useful while A.1.STM keeps any unresolved common-SoI question visible.

A.1.SCR:10 - Rationale

The conditional route preserves two useful results: a direct subject-pattern answer when systemhood does not change the decision, and a complete A.1 recognition result when it does. Keeping the proposed entity fixed through that choice prevents a familiar noun or a convenient neighboring referent from selecting a different actor, change bearer or project SoI. Project designation remains a separate claim.

Extent-sensitive identity remains useful because it forces the practitioner to state what exists and survives change. Unrestricted composition and category import remain rejected. The seven cases demonstrate transfer across domains without asserting a common kind.

A.1.SCR:11 - SoTA-Echoing

Informative. These external comparisons inform the practitioner route. A.1 and the named subject patterns remain authoritative for kinds, relations, and pass conditions.

External sourceContribution used hereA.1.SCR use and boundary
Florio and Linnebo, Introduction to Constructional Ontology, JOWO/FOIS 2024, CEUR Workshop Proceedings 3882, §1, pp. 1–3, and §3, p. 4Construction choices affect identity and require constructors, inputs, and construction-sensitive distinctions.Only the system-dependent branch in A.1.SCR:4.3 applies the six-component test. Return unknown when missing information prevents determining either satisfaction or failure.
Deutsch, Constructor Theory, arXiv:1210.7439v1 (2012), §1.1, pp. 1–4Possible transformations depend on substrate attributes and constructor conditions.At A.1.SCR:4.3 and 5.1, test whether facts about the proposed assembly satisfy the applicability and compatibility conditions of a governed larger-assembly construction rule.
Chris Partridge, BORO Ontology, C-FORS Summer School, University of Oslo, 23 May 2025, slides 19, 22–24 and 28Four-dimensional identity pressure asks what exists through change and across extent.Use A.1.SCR:4.8 for the entity and kind distinctions; shared extent alone does not establish identity.

The conditional method is an FPF synthesis.

A.1.SCR:12 - Relations

  • Builds on: A.1 for the complete constructive criterion, admitted holon kinds, acting eligibility, and true | false | unknown evaluation discipline.
  • Leaves directly through: A.2.2, A.3.1, A.3.2, A.3.4, A.15.1, A.15.2, A.22, C.2.1, E.18, and the exact relation pattern when systemhood is not load-bearing.
  • Service/access first use: A.6.P §4.11a; A.1.SCR applies only to a separate system-dependent claim about the entity recovered there—a bearer or access-providing arrangement.
  • Uses for projects: A.15.6 for the actual and intended system distinction, plan or decision designation of the project system-of-interest, separate tests of the system-role kind and assignment, project-relevant network selection, and missing-substrate[project-selection-conjunction]; A.1.STM only when the returned recognition result must re-enter the system-thinking long map.
  • Uses for missing relations: A.6.RCD with exact participants, receiving use, and missing-governor[...].
  • Coordinates with: A.1.CSD when a returned bearer result opens the separate question of which other Systems may undergo relevant changes; A.1.STM for the separate long-map use after recognition; and E.10 for lexical triggers.
  • Does not replace: A.1, direct kind patterns, relation patterns, A.6.P, or F.18 designation recovery.

A.1.SCR:End

A.1.CSD - Discovering Systems That May Bear Consequences

Type: Part A practitioner discovery pattern Status: Stable Normativity: Normative unless marked informative

Plain name. Find other Systems that may change.

Governed branch. The broad head is U.System recognition under A.1. This narrower branch examines concrete change-producing possibilities for one current focus, discovers actual Systems or intended System referents that may change under those possibilities, and returns qualified claims for one named receiver. The focus governs the account’s aboutness; it is not thereby the world-side changer. Any obtaining change-producing occurrence and any causal claim remain separately governed. The pattern does not recognize every candidate, establish causality, evaluate the changes, or make the receiving decision.

Primary EntityOfConcern. One exact proposed or observed focus entity whose possible or observed consequences are being investigated. The receiving decision or investigation is a neighboring use of the result. Candidate bearers remain participants in its claims.

A.1.CSD:0 - Practitioner Entry

Use this when. Use this pattern when proposed or observed Work, realization, operation, use, maintenance, misuse, failure, recovery, retirement, policy, or change may alter Systems omitted from the current decision or investigation, and finding one of them could change a probe, constraint, alternative, monitoring condition, explanation, or reopen decision.

Ask: Which other Systems may undergo a relevant change, through what supported relation or still-modal path, and what should the receiver do next?

First useful move. Name the exact focus and receiver. Generate a small set of concrete change-producing possibilities, trace outward through supported direct relations or explicitly modal path claims, and challenge the current boundary for a missing bearer.

First useful result. Return the smallest bounded consequence account useful to the named decision or investigation. A qualified claim, retained constraint or alternative, modal path, or explicit unknown can finish the answer with its material limit. Further discovery is selected only when its obtainable contribution warrants the whole burden.

Cheap stop. Stop if the current bearer set and consequence claims already support the receiver at the declared configuration, scope, horizon, and evidence window. Also stop the affected claim branch when an exact non-System finding or missing relation blocks its next claim; return that finding to its direct owner instead of inventing a System.

What goes wrong if missed. A familiar participant list becomes the boundary of inquiry, a possible path is reported as an obtaining relation, a scale label stands in for a constructed whole, or unlike changes disappear inside one aggregate. The receiver closes while a cheap observation or alternative could still have changed it.

What this buys. The practitioner gets a reviewable set of possible bearers, relation-status claims, changed characteristics, evidence limits, and a useful receiving result without importing a full domain impact, risk, due-diligence, or assessment procedure.

Not this pattern when.

  • If one proposed entity must first be tested as a U.System, use A.1.SCR.
  • If the current question is an already named direct relation, use its A.6 governor.
  • If the receiver relies on a causal effect, intervention, or counterfactual claim, use C.28 for that claim.
  • If the current question is comparison or choice among configurations, use C.11.CRC and C.11 after the needed bearer claims exist.
  • If the domain already has a qualified discovery Method with its own quantities, thresholds, evidence rules, and authority, use that Method; use A.1.CSD only for the shared early discovery result.

A.1.CSD:0.1 - Precision Restoration

ExpressionWorking meaning here
consequence-bearing SystemAn actual U.System whose state or characteristic may change under the stated conditions. This is a plain description, not a kind, role, assignment, or status.
intended System referentA designator for a System whose intended existence is stated in a modal claim. It does not assert current systemhood or existence. An unidentified bearer remains an explicit unknown with the claim’s modality preserved.
supported obtaining direct-relation occurrenceOne exact world-side relation occurrence whose participants, predicate, and obtaining conditions are supported under its direct governor.
modal path claimA claim that a path may obtain, naming the proposed relation kind, candidate participants, conditions, support, and uncertainty.
consequence claimA claim about a possible or observed changed state or characteristic, its bearer, conditions, time, support, uncertainty, and causal status. The claim is not the world-side change.
affected-System consequence accountOne ordinary C.2.1 episteme identified by one exact <ClaimGraph, EntityOfConcern, effective ReferenceScheme> triple. It is not a new result kind or the bearer Systems themselves.
receiverThe exact decision or investigation that can use the account. It is a neighboring use, not part of the account’s identity triple.

Affectedness creates no AffectedSystem, ConsequenceBearingSystem, AffectedSystemRole, ImpactRelation, U.Level, priority, aggregate, or decision. Use each stronger claim only under its direct owner.

A.1.CSD:1 - Problem Frame

A proposed change can affect Systems beyond its proposer’s chosen boundary, for example through material transfers, information exchange or dependencies in the work being performed. Some paths already obtain; others are plausible claims awaiting observation.

Find enough actual Systems or intended System referents whose changed states or characteristics can alter the named decision or investigation. For an actual candidate whose systemhood matters to the receiving decision or investigation, use A.1.SCR or reuse its existing recognition basis; visibility and the ability to answer an inquiry do not determine systemhood or consequence relevance.

Scale words do not solve the search. A constituent, containing System, neighboring whole, and later reidentified whole are relevant only through their actual construction, delimitation, direct relations, or a genuine whole-reidentification question. Consequences on several sides remain separate even when a domain calculation later compares them.

A.1.CSD:2 - Problem

A bounded discovery move addresses these failures:

  1. stop at systems already named by interfaces, ownership, participation, contracts, or observation;
  2. turn a plausible path into an asserted world-side relation;
  3. treat organism, population, team, organization, society, or ecosystem words as a ready ladder of Systems;
  4. force collections, places, descriptions, Methods, Work occurrences, or declared scopes into System rows;
  5. combine unlike bearer, horizon, evidence, and receiver coordinates before their differences are inspectable; or
  6. continue brainstorming without a decision-relative stop or next probe.

Premature closure can miss an action-changing consequence; an unbounded catalogue can delay an already supported decision.

A.1.CSD:3 - Forces

ForceTension
Reach vs supportConsequences can travel far, while evidence for distant paths is often weak.
Early action vs false actualityA plausible path can change a constraint or justify a worthwhile obtainable probe, while remaining insufficient to assert that the relation obtains.
Breadth vs ontologyMore candidate bearers improve discovery only while each keeps its exact kind or blocker.
Several scales vs one decisionSeveral holons may change differently, while the receiver still needs a bounded next move.
Reuse vs domain authorityA common discovery action is transferable; domain quantities, thresholds, evidence Methods, and decisions are not.
Proportionality vs completenessA bounded investigation can leave paths unexamined; its material residual must remain visible to the receiver.

A.1.CSD:4 - Solution

Discover outward from concrete possibilities, preserve the status of every relation and bearer claim, and stop at the smallest account that supports the receiving decision or investigation.

A.1.CSD:4.1 - Perform the Move

  1. Recognize the working situation. Use A.1.CSD only when an omitted System could change a named decision, investigation, probe, constraint, monitoring condition, explanation, or reopen condition.

  2. Name focus and receiver. State the exact proposed or observed focus entity, current configuration when relevant, exact receiving decision or investigation, scope, place when material, and horizon.

  3. Generate change-producing possibilities. Consider intended and plausible Work, realization, operation, use, maintenance, misuse, failure, recovery, adaptation, continuing change, retirement, and later conditions that matter here. These are examples of possibilities, not a lifecycle or mandatory sequence.

  4. Trace paths and challenge the boundary. Follow supported obtaining direct-relation occurrences separately from modal path claims. For a modal claim, name the proposed relation kind, candidate participants, conditions, support, and uncertainty. Then ask which Systems capable of bearing the stated change remain outside the current frame.

  5. Recover relation status and holon basis. Establish every claimed world-side relation occurrence—such as part-whole, participation, dependency, crossing, or exposure—only through its direct governor. Recover an environment from one focal System delimitation, exact external referents, supported crossing relations, and the selected use; recover a delimitation or boundary through its own FPF construction and supporting facts, retaining its kind under the direct pattern. A boundary label alone establishes no relation occurrence.

    Support a containing-System claim through the exact part-whole relation and construction. A context or declared scope remains a use-bounding fact and does not by itself make a world-side relation obtain. Use exact construction facts rather than a level word. Use B.2 or B.2.2 only when current facts create a real whole-reidentification question, then inspect possible bearers on both sides.

  6. Recognize or retain bearer references. Use A.1.SCR only when an actual candidate’s systemhood is load-bearing. Keep a not-yet-present intended bearer as a designator inside modal content; retain an unidentified bearer as an explicit unknown without changing the claim’s modality. Preserve a collection, place, scope, or other referent under its own kind or blocker.

  7. Qualify each consequence claim. Name the changed state or characteristic, exact bearer, obtaining-occurrence or modal-path status, conditions, configuration, direction and magnitude cue when known, time, grounded whole/part or declared-scope coordinate when current, evidence, uncertainty, and causal status.

  8. Keep cross-scale coordinates distinct. Preserve each bearer’s changed state or characteristic, conditions, horizon, evidence, uncertainty, and receiving use. A later domain aggregate may be added for its own use; it does not replace the original claims or set priority by scale.

  9. Connect the result. For each material claim, state whether the receiver needs a constraint, alternative, evidence-producing probe, specialist return, monitoring condition, reversible step, or explicit unresolved gap. Route a stronger claim to the pattern or practice that defines and tests it.

  10. Select further inquiry by contribution and burden. When a particular missing bearer or path could change the receiving use, apply C.11.DUA to what an attainable observation could establish and its full preparation, access, performer, interpretation, delay, displaced work, and downside. Compare further inquiry with using the present account, retaining a constraint or alternative, or stopping.

    Examine proposed observations separately and as a programme: individually useful requests can compete for the same capacity or jointly miss the window. Prioritize a selected inquiry by its consequences and reversibility, keeping poorly observed sides and their original coordinates visible.

  11. Stop and reopen. Finish when the account gives the receiver the useful qualified answer and its material limit. Retain plausible missing bearers or paths and a reopen condition where they change interpretation or a later use. Name a next discovery action only when selected under step 10; an unresolved path requires no study proposal or separate explanation for omitting one.

This sequence of actions is a reasoning aid. Discovery, observation, design, comparison, and specialist inquiry may proceed concurrently and reopen one another.

A.1.CSD:4.2 - Keep Relation and Holon Status Explicit

Current statementAdmissible treatment
A direct relation occurrence is supportedRecord the exact participants, predicate, conditions, support, and qualification window under its direct governor.
A path is plausible but not observedKeep a modal path claim with proposed relation kind, candidate participants, conditions, support, uncertainty, and its consequence for the present use. Add a probe only when selected for its attainable value.
A required relation kind has no governorReturn the exact participants and blocked use through A.6.RCD; do not mint relatedTo, impact, or consequence as a generic relation.
An environment is currentName the focal System delimitation, the exact external referents, the supported crossing relations, and the use that makes them relevant.
A containing System is claimedSupport the exact part-whole relation and construction; proximity, influence, or a larger box is insufficient.
A scale distinction changes the searchRecover exact holons or declared scopes and the obtaining construction, delimitation, crossing, or dependency facts. A level label alone establishes none.
A different whole may now carry the claimUse B.2/B.2.2 only for the exact existing-whole/new-whole comparison; then inspect candidate bearers on both sides without assuming either side wins.

A modal claim can qualify the present answer and identify what a later observation would have to establish. Add a separate actuality claim only when the direct obtaining predicate and its case conditions are supported.

A.1.CSD:4.3 - Make the account recoverable for use

For reuse, make the account’s focus, claims and interpretation basis recoverable. These supply its C.2.1 identity; ordinary prose can state the working content below.

Result partRequired content
C.2.1 identityOne exact proposed or observed focus entity as EntityOfConcern; one exact ClaimGraph carrying the examined possibilities, bearer and intended-referent designations, relation/path and possible-change claims, support, uncertainty, material residual, and any selected probe or useful reopen claim; and the effective ReferenceScheme supplying designation and interpretation rules plus only the measurement, comparison, or evaluation rules actually used.
working bounds and receiverConfiguration when relevant, scope, horizon, and exact receiving decision or investigation. The receiver remains a neighboring use.
examined possibilitiesThe concrete intended or plausible change-producing occurrences and the outside-in boundary challenge applied.
relation, holon, and transition basisSupported obtaining direct-relation occurrences; separately identified modal path claims; constructively recognized holons or declared scopes; any genuine whole-reidentification basis; and exact missing relation or recognition blockers.
bearer referencesEach actual System with its recognition basis, each intended System referent in modal content, explicit unknowns, and exact non-System findings routed to their direct owners.
consequence claimsChanged state or characteristic, exact bearer, obtaining-occurrence or modal-path status, conditions, time, grounded whole/part or scope coordinate when current, direction or magnitude cue, evidence, uncertainty, and causal status.
cross-scale separationThe original bearer, change, condition, horizon, evidence, uncertainty, and receiving-use coordinates for every retained side. Any aggregate remains additional.
receiver connectionConstraint, alternative, evidence-producing probe, specialist return, monitoring condition, reversible step, or unresolved gap.
discovery residual and reopenThe missing bearer or path and reopen condition that matter to the receiving use. Include a further action only when its obtainable contribution warrants the complete inquiry burden.

A thin account may contain one qualified consequence claim plus one unresolved bearer, path, or specialist return when those entries already support the receiving decision or investigation. Blank fields do not assert closure. Bearers and unknowns are participants in the ClaimGraph, not extra EntityOfConcern values. If one truthful focus cannot govern the combined claims, keep the claims local or identify several account epistemes.

A.1.CSD:4.4 - Recognition and Assurance Split

Recognition. A cold reader can find the focus, receiver, at least one possible bearer, the obtaining-or-modal status of its path, the possible changed characteristic, support and uncertainty, and the useful qualified answer, constraint, alternative, selected probe, or stop.

Assurance. Trust in systemhood, relation occurrence, measurement, causal effect, source reliance, comparison, and specialist result remains with the direct patterns and practices.

A.1.CSD:5 - Four First-Screen Situations

Working situationFirst actionFirst useful result or stop
A flood-pump modernization may shift load, maintenance demand, downstream flow, and failure exposure.Name the configuration decision, trace the finite change through supported plant relations and modal operating paths, and challenge the selected boundary.Return an additional consequence claim naming the affected System and possible change when that claim changes a design constraint or monitoring condition. Finish if the current account already supports the configuration decision. If a missing relation blocks the next needed claim, stop that branch and name the exact missing relation.
An on-call and platform arrangement is being reorganized.Trace the proposed Work and assignment changes to employee, provider, service, customer, and neighboring organization Systems without treating those names as a level ladder.Keep workload, capability, service, and organization consequences separate; return the missing bearer or relation to the organization-change Method.
A public appointment service is being redesigned through facilitated inquiry.Trace service and policy alternatives to applicant, staff, provider, transport, and other material Systems; use participation as a discovery source, not proof of systemhood or authority.Return descriptive bearer claims to the facilitated inquiry; route participation, concern, and authority questions to their direct practice.
A nutrient pulse in a bioreactor may change living and engineered Systems.Trace supported feed and effluent relations separately from modal biological and operating paths, and recover actual whole/part facts.Return the separate consequence claims and current limit; select spatial sampling, pressure observation, or effluent measurement only when their individual and combined contribution warrants the programme.

The same discovery action changes all four situations. Their domain Methods, quantities, evidence rules, and decisions remain different.

A.1.CSD:5.1 - Minimally Viable Worked Case: Nutrient Pulse

In this constructed case, FeedPulsePlan-FP4 proposes a larger nutrient pulse for BioreactorOperatingSystem-BR7. The receiving investigation is ProbeDecision-PD4: decide whether and which further observations are worthwhile before changing the feed setting for the next 48 hours. The plan is the account’s one exact focus EntityOfConcern; the ClaimGraph examines the possible feed-operation occurrence it specifies rather than treating the plan as a physical cause. The probe decision is the account’s neighboring use.

Baseline instrumentation supports one obtaining substrate-transfer occurrence from FeedLine-F2 into the reactor medium and one obtaining effluent-flow occurrence from BR7 to TreatmentTrain-TT2. Take a complete A.1 recognition basis for the individual bacterial Systems as a case input.

For BiofilmPatch-BP3, microscopy and persistence observations support matrix-linked constituents and their obtaining part relations, persistent assembly under the same-matrix continuity rule, and whole-level nutrient-processing and shear-resistance characteristics. The case’s governed biofilm-integration rule admits the patch as a constituent of BR7’s carrier assembly when its matrix attaches to Carrier-C3, its extent fits the available carrier surface, and it retains its matrix-connected identity at the declared operating flow. The case supplies those attachment, fit and continuity facts. Together with its physical organization and causal participation in nutrient transformation, these facts supply the A.1 recognition basis for the patch. Keep the constituent relations under their part-whole governors.

The proposed larger pulse has not occurred. The account therefore keeps four paths modal:

Candidate bearerModal path and possible changed characteristicSupport and uncertaintyReceiver connection
sampled individual bacterial Systems near the inletLarger pulse -> higher local substrate concentration -> changed individual metabolic states and sample-level viability distribution.Baseline gradient observations support plausibility; the proposed concentration field is unmeasured.Retain the local-exposure limit; spatial sampling could distinguish inlet and bulk responses in a selected bounded trial.
BiofilmPatch-BP3Larger pulse -> changed growth and matrix production -> changed patch coverage and shear resistance.Current patch identity and coverage obtain; the proposed growth response remains model-supported and uncertain.Preserve the current pulse alternative; short-window images may leave the growth response unresolved.
BioreactorOperatingSystem-BR7Changed patch coverage and local transfer -> changed transfer efficiency and pressure drop.Baseline pressure and transfer measurements obtain; the coupling under the larger pulse remains modal.Preserve the pressure/transfer constraint; a trace during a selected trial could test the proposed coupling.
TreatmentTrain-TT2Changed reactor effluent composition -> changed incoming load and treatment performance.The effluent connection obtains; the proposed composition and downstream response are unmeasured.Keep the downstream-load limit visible; an effluent observation could change whether a tested pulse may continue.

The account keeps bacterial, biofilm, reactor, and treatment-train characteristics separate. It does not average them into one score.

Its discovery residual names an observed unattached aggregate outside BiofilmPatch-BP3. Current evidence supports treating the observed members as a collection; whether that collection also forms a whole/System remains unknown because assembly, persistence, and the kind-specific A.1 facts are unsupported. The aggregate’s whole identity does not alter this receiving decision in the case, so it remains an explicit unknown.

If later reliance needs that identity, the relevant A.1/C.13 evidence would concern stable assembly, persistence, and whole-level behavior across observations; acquiring it still needs a worthwhile receiving contribution. Recover those facts before classifying it; only supported failure of a required A.1 component or condition warrants a negative System result.

The current pulse remains available while the larger pulse’s consequences are modal. For the inquiry choice, suppose the domain investigation supplies these attainable contributions and full efforts, including preparation, any required trial operation, observation, and individual interpretation: spatial sampling can distinguish local exposure within 48 hours for one staff-hour; a pressure trace can qualify the transfer constraint for one hour; and an effluent observation can address downstream load for one and a half hours. Those answers could change the admissible pulse comparison. A two-hour imaging series would not discriminate the growth response in this window. These are illustrative planning premises, not biological thresholds or observed effects.

The programme has four available staff-hours after existing duties and adds half an hour of shared coordination and joint interpretation. All four proposed observations would take six hours and exceed that capacity. Spatial sampling, pressure observation, and effluent measurement together take four hours, finish in the receiving window, and supply the worthwhile discriminating contribution. The inquiry selects that programme while retaining the current pulse alternative and the unresolved biofilm-growth and aggregate-identity claims. If access, interpretation capacity, protection, or trial authority cannot support it, the available result is the qualified account with the current setting retained.

The domain practice governs whether any trial or subsequent feed change is admissible. Selecting observations neither performs them nor establishes their outcomes, causal effects, or permission. Reopen when a new whole becomes material, the feed configuration changes, an observation reverses a path claim, or the programme’s contribution or feasibility changes.

A.1.CSD:6 - Bias Annotation

Bias riskFailureRepair
Visible-system closureOnly Systems already named by the current project or investigation are considered.Trace outward from concrete possibilities and challenge the current boundary.
High-agency biasSystems unable to speak, decide, or participate are omitted.Apply A.1 systemhood and consequence relevance; neither voice nor agency is required.
Relation promotionA plausible arrow becomes an obtaining world-side relation.Keep the modal path claim distinct; add a separate actuality claim only when its direct predicate and case conditions are supported.
Level ladderFamiliar scale words are treated as Systems in a fixed hierarchy.Recover exact holons, scopes, construction, crossings, and any real whole-reidentification question.
Aggregate closureA total hides changed characteristics, evidence, or receivers on one side.Preserve the original coordinates and make any aggregate an additional domain result.
Causal overreadSequence, association, or model output is treated as an effect of intervention.Keep the narrower claim and use C.28 when the receiver relies on causality.
Completeness theatreA long list is presented as exhaustive.Use a receiver-relative stop and retain the material residual; select additional discovery by its attainable contribution and complete burden.

A.1.CSD:7 - Conformance Checklist

IDA conforming use…
CC-A1-CSD-1names one exact focus entity and one exact receiving decision or investigation.
CC-A1-CSD-2states configuration when relevant, scope, horizon, and the possibilities examined.
CC-A1-CSD-3traces supported obtaining direct-relation occurrences separately from modal path claims and challenges the starting frame for possible consequence-bearing Systems that remain outside it, stopping relative to the named receiver rather than claiming exhaustive coverage.
CC-A1-CSD-4gives every modal path a proposed relation kind, candidate participants, conditions, support, uncertainty, and its present use limit; a probe is conditional on selected attainable value.
CC-A1-CSD-5uses A.1/A.1.SCR for load-bearing System recognition and preserves non-System findings under their own kind or blocker.
CC-A1-CSD-6derives scale distinctions from exact holons, scopes, construction, delimitation, crossings, or a genuine B.2/B.2.2 question rather than a fixed ladder.
CC-A1-CSD-7states the possible or observed changed characteristic, exact bearer, conditions, time, evidence, uncertainty, and causal status.
CC-A1-CSD-8keeps unlike bearer, change, horizon, evidence, uncertainty, and receiver coordinates visible across scales.
CC-A1-CSD-9identifies the constraint, alternative, probe, specialist return, monitoring condition, reversible step, or gap needed by the receiver.
CC-A1-CSD-10returns one ordinary C.2.1 episteme with one focus EntityOfConcern, exact ClaimGraph, and effective ReferenceScheme, or keeps the claims local.
CC-A1-CSD-11retains the missing bearer or path and reopen condition needed by the receiving use; any further inquiry is worthwhile and obtainable separately and as a programme, without a mandatory no-inquiry record.
CC-A1-CSD-12leaves measurement, causality, value, comparison, authority, assurance, and domain decisions with their direct owners.

A.1.CSD:8 - Common Failures and Repairs

FailureSymptomRepair
Actor-list substitutionThe search repeats owners, users, operators, or interface participants.Begin from possible changes and trace beyond the current list.
Mention inflationEvery nearby entity is called affected.Require a possible or observed changed state or characteristic and a receiver connection.
Affectedness as kind or roleA bearer is assigned a new universal category or duty.Keep affectedness in qualified claim content; use existing kinds and direct relations.
Diagram proofAn arrow or model edge is treated as an obtaining relation.State its status, participants, conditions, support, and uncertainty.
Collection-to-System jumpA population, fleet, community, or aggregate is treated as one acting whole.Apply A.1/C.13 to the exact candidate whole or retain the collection.
Scale trump cardOne constituent or larger whole receives automatic priority.Preserve each consequence coordinate; route any comparison or priority claim to its owner.
Universal assessment formEvery case must fill a domain-sized template.Return the thin account that supports the receiving use and name the residual.
Negative catalogueThe result mainly lists what was not found.Return usable bearer claims, probes, direct-owner exits, and the blocker.

A.1.CSD:9 - Consequences and Reopen Condition

The pattern makes quiet and remote Systems discoverable without turning discovery into a role taxonomy or universal assessment procedure. It gives downstream work a qualified starting point: an actual bearer, an intended referent, a supported relation occurrence or modal path, a possible changed characteristic, and the useful constraint, alternative, qualified answer, or selected evidence-producing move.

The cost is explicit uncertainty and more disciplined relation handling. Some inquiries stop with a missing System-recognition or relation fact; that limit can be useful without commissioning the observation needed for a stronger claim.

Reopen the account when the focus, configuration, scope, horizon, whole/part construction, obtaining-relation support, bearer recognition, observation, specialist result, or receiving use changes.

A.1.CSD:10 - Conditional Consumer Boundary

The core account ends before stronger neighboring claims. Continue only when the next question is current:

Next questionContinue through
Does evidence support a retained claim, and may it be relied on now?A.10, with C.27 for temporal adequacy and B.3 for assurance.
Does a claimed effect, intervention, or counterfactual have adequate causal support?C.28.
Does a mathematical scale, aggregation, optimization, or representation lens preserve what the receiver needs?C.29; use C.30.ILC only for a current cross-scope architecture residual.
Would a particular further inquiry warrant its full attainable burden?C.11.DUA; A.15.9 for a selected outside-practice contribution.
How does a finite configuration change compare, and what is chosen?C.11.CRC, then C.11.
Does a later question concern value, benefit, harm, responsibility, admissible sacrifice, or an actual interlevel conflict?Enter through D.1; use D.2 for multilevel entry, D.3 for an actual conflict description, D.4 for mediation or decision use, and D.5 for its bounded audits.

For the last branch, one admissible D.1 value-frame edition is multilevel holonic consequentialism: inspect consequences for every constructively identified affected holon without automatic priority for a person, collection, or larger whole. That frame is conditional and plural under D.1. It adds no field to the A.1.CSD account. Establish any conflict, priority, or decision claim under its direct pattern.

A.1.CSD:11 - Rationale

A.1.SCR answers whether one proposed entity is a System. A.1.CSD begins after a focus is current and asks which other Systems may undergo relevant changes. Merging the two would burden every systemhood check with an open-ended consequence search and would confuse candidate generation with recognition.

A.1.STM locates an unsupported answer across a long dependency; C.28 qualifies a causal-use claim; C.11.CRC constructs a finite comparison. A.1.CSD constructs the bounded bearer/path/change account for these receiving uses, leaving their stronger claims to the respective patterns.

The result remains an ordinary C.2.1 episteme because the recurring need is a reusable set of qualified claims, not a new world-side kind or relation. One focus fixes the account’s EntityOfConcern within its C.2.1 identity triple; claims about several bearers give it content.

A.1.CSD:12 - SoTA Echoing and Source Use

Each row distinguishes a descriptive result, constructive Method, normative premise, or institutional preference; it retains only the action supported for this use.

Source lineClaim and practical action retainedAdoption status and boundary
Ulrich and Reynolds, Critical Systems Heuristics: The Idea and Practice of Boundary Critique, 2020Boundary critique is an argued reflective and discursive Method. It changes practice here by adding an outside-in challenge after forward tracing.Adapt. Retain the boundary challenge; do not import its complete normative programme, twelve-question form, System recognition, completeness claim, or scale priority.
OECD, Guidelines for Multinational Enterprises on Responsible Business Conduct, 2023, and Due Diligence Guidance, 2018The guidance supplies an operational mapping and reassessment Method for actual and potential consequences across operations and remote relationships. It changes practice by widening path generation and reopening after conditions change.Adapt. Enterprise duties, rightsholders, severity priorities, remedy, and authority remain domain results; publication status is not evidence of effectiveness.
European Commission, Better Regulation Toolbox 2023, Tool 18 and Chapter 2The institutional procedure distinguishes direct/indirect, intended/unintended, positive/negative, and one-off/recurrent consequences and asks for proportionate depth.Adapt. Retain path and horizon prompts; reject its affected-group list, territorial ladder, reporting categories, monetization preference, and form as universal ontology or work order.
NIST, AI Risk Management Framework 1.0 and Map playbookThe framework and playbook add misuse, repurposing, downstream factors, external feedback, later conditions, and continuing remapping as prompts.Adapt. Reject AI actor classes, ready scale lists, risk taxonomy, governance apparatus, and aggregate score as general FPF results.
ISO/IEC/IEEE 24748-7000:2022, IEEE 7000-2021, and ISO/IEC/IEEE 15288:2023These normative engineering standards provide implementable traceability and iterative/lifecycle attention. They change practice by keeping selected concerns linked to concepts, requirements, design choices, and later observation.Adapt conditionally. Conformance and involvement do not prove bearer completeness, discovery effectiveness, System construction, representation, or authority. The full processes stay in engineering practice.
Friedman and Hendry, Value Sensitive Design, 2nd ed., 2026, and the authors’ Method accountVSD retains direct/indirect stakeholder and value-scenario prompts and multi-lifespan attention. Value scenarios can widen social/design path generation.Adapt conditionally. Human-value orientation is a normative premise, not the A.1.CSD admission test. Route Diverse Voices and tech-policy participation to the direct domain practice.
U.S. EPA, Conducting an Ecological Risk Assessment and EcoBox analysis materialLaboratory, field, monitoring, and modeled practices support stressor-to-receptor tracing, exposure/effect separation, time, recovery, uncertainty, and evidence-producing questions.Adapt. Organism, population, community, and ecosystem are prompts, not a ready FPF holarchy. Regulatory endpoints, adversity judgments, risk estimates, and the complete ecological procedure remain domain results.

These sources converge on path tracing, boundary challenge, proportional inquiry, qualified uncertainty, and reopening. Their taxonomies, normative ends, calculations, evidence thresholds, and authority do not converge and are not imported.

A.1.CSD:13 - Relations

  • Builds on: A.1 for admitted holon and System recognition; C.2.1 for the account episteme; A.14, B.1, B.1.2, and C.13 for exact relations, wholes, collections, delimitation, crossings, and constructive grounding.
  • Uses conditionally: A.1.SCR for a load-bearing bearer-recognition question; B.2 and B.2.2 only for genuine whole reidentification; A.6.RCD for a missing direct-relation governor; A.10, C.27, C.28, C.29, C.30.ILC, C.11.DUA, A.15.9, C.11.CRC, C.11, and the D-family only for their exact neighboring questions.
  • Supplies: a bounded affected-System consequence account to a named decision or investigation. Current SYSE.17 adds engineering possibilities, project/configuration inputs, engineering returns, assurance interfaces, and specialist authority boundaries.
  • Does not replace: domain impact, risk, due-diligence, value-engineering, ecological, safety, legal, medical, economic, governance, policy, participation, or facilitation Methods; System recognition; causal support; comparison; assurance; authority; or decision.

A.1.CSD:End

A.1.STM - Connect Project Reasoning (System-Thinking Long Mantra)

Type: Part A practitioner application pattern Status: Stable Normativity: Normative unless marked informative

Plain name. Use the system-thinking long mantra.

Long mantra and attention map are Plain names for a repeatable reminder and its readable display of connected questions. The developed account connects knowledge about use, functioning, construction, creation and cooperation. Its short wording helps keep that account in attention; it does not supply the knowledge that the account needs.

A.1.STM:0 - Practitioner entry

Use this when. Use this pattern when participants have knowledge about parts of a project but need to connect it into one systemic account: what should change in use, which system can make that difference, how it could function and be constructed, how it can be obtained, and how its creators can work together. Their answers must fit together, not merely be plausible separately. Identify the relevant project system-of-interest (SoI), or systems-of-interest when several matter, and the receiving uses relevant to that decision. Use the pattern also when participants say “our system” but leave its project context, contribution or receiving use unclear. A narrower use is to locate the first unsupported dependency when the connected account is already sufficient.

First useful move. You may arrive with a felt difficulty, a proposed change or a project account worth examining before trouble is noticed. Section 4.0 connects those entries. For a systemic project question, recover what should become different or remain possible in use, for whom and when. From the system’s boundary, look upward to the larger functioning whole and the joint action of its parts. Use that account to derive the system’s needed contribution before justifying its internal construction and the work needed to obtain it. Reuse a sufficient existing account; when the larger whole is unknown, investigate that question. Sections 4.1–4.3 develop this order, 4.3.1 connects the answers, and 4.4 locates a bounded gap.

Memorable reminder.

First look toward use: what should change, for whom and when? From the system’s boundary, look upward: of which larger functioning whole is it a part, and what do those parts accomplish together? Investigate an unknown whole. Derive what the system must do there and name the system sought by that function. Then look inward to possible constructions and backward to ways of obtaining them, needed contributions and capable creators. Organize their work and means so the contributions can be used together. Repeat for needed creators while retaining the results they serve. Follow what happens and revise the answers whose grounds change.

This is the Plain long mantra. Its first moves establish the use that gives the later choices their reason. Section 4 explains the two directions, the returns after changed knowledge, and the difference between this reasoning order and a schedule of work.

Not this pattern when. A known local system-recognition, service/access, architecture, Method, Work, transformation, evidence or closure question can be answered through its subject pattern. Such a result need not reopen the whole project account. Use this pattern when the common basis or the connection to it is itself at issue.

What this buys. Participants can form and criticize a connected project account, justify why its choices belong together, find a consequential incompatibility or missing answer, and revise the affected part without losing the whole. They distinguish project roles, current local subjects and the receiving connections between undertakings, while preserving valid local results. The account can remain ordinary prose and existing project descriptions; no new universal project record is required.

A.1.STM:1 - Problem

Division of labour lets different participants work on components, methods, descriptions, tools and provider organizations. Their local choices become coherent only if they can explain what common outcome those choices are intended to obtain. A component may meet its specification while the whole remains unusable; a provider may become efficient at producing something its intended users do not need. Local completion alone cannot settle the shared project purpose.

A system-of-interest (SoI) is the system whose intended use, and the benefit sought from it, give a cooperation of creators its common purpose. The participants connect their contributions to bringing about, changing, sustaining or retiring that system in light of its use and effects. A project account can carry this common SoI through one temporary body of work; each supporting project need not acquire a separate SoI. The same machine can be the SoI of its manufacturer’s product undertaking and a means of production for a component manufacturer. Its identity need not change when that relation differs. Before a future system exists, describe the intended system and use without asserting an actual holder.

The current subject of inquiry or local work answers a different question: what must this participant understand, obtain or change now? It can be a component, test rig, creator organization, Method or episteme. For a system, system-in-hand or our system can identify that local subject once the participant’s relation to it is clear.

In organizational work the organization remains the creator being engineered, while its products supply the SoI and the use that justifies its capabilities. Treating the firm itself as the common purpose can make necessary product work appear to be a dispensable expense. Conversely, a product design that ignores the creators’ means, rights and commitments may never become usable. The connected account must make both consequences visible in the decisions that allocate and provide work.

A project can also get every nearby statement locally right and lose the long dependency. A functioning argument can assume one construction while the creation plan can supply only another; capable contributors can require incompatible shared resources. Agreement on the SoI does not by itself make these answers jointly usable. One team improves a component, another produces a builder, and another measures operation, yet nobody can show how those results are expected to reach the SoI’s use or which actual relations now connect them. A diagram arrow, the word creates, or a calendar sequence can hide that gap.

The opposite failure is to turn the reminder into a universal route. Then every result becomes a System, a plan becomes an existing holder, project Work becomes a network, and every arrow appears to be the same relation. A.1.STM develops the shared systemic reasoning while leaving each local truth with its subject pattern.

A.1.STM:2 - Forces

ForceTension
Whole-project coherenceParticipants need a compatible basis for a joint decision while their project scopes, systems-of-interest, interests and local results may differ.
Use and encompassing functioning firstIntended use and the wider functioning at the operating time give reasons for construction and provision; discovery and feedback can reopen that basis.
Backward justificationReading from value toward missing support is useful, but it is not temporal order or transformation direction.
Forward actualityWork and changes must be traced through facts that obtain, not through planned arrows or shared names.
Local contributionA team needs to know how its result matters without inventing a universal contribution relation.
Recursive buildersBuild-the-builder reasoning must recur without a creator kind, fixed levels, or a generic creates edge.
Evidence and returnA supported answer may later become stale or fail; reopening should be local rather than restarting the whole map.

A.1.STM:3 - The attention map

Keep these connected questions available while reasoning about the project. Begin the justification with receiving use and the wider functioning in which the system participates, then examine its construction and creation. Reuse answers already sufficient for the current decision and investigate a gap where it can change that decision. The rows are reminders, not mandatory fields or work stages. One ordinary sentence can answer more than one question.

RegionPlain questionWhat the answer enables
Outside change and useWhat should become different or remain possible for whom, in which operating situation and time?Establish the result sought, receiving transformations and success conditions, including a proposed future use.
Wider functioning at that timeOf which larger functioning whole is the system a part, and how does the joint action of the parts produce the result sought?Establish the relevant part–whole relations at the operating time, moving through the levels and inclusions that affect the decision. An unknown whole leaves an inquiry to resolve. Keep use, interaction, ownership and creation distinct from containment.
Project systems-of-interest and usesWhich systems and receiving results matter to this decision, in which projects, and which boundaries and connections must the participants agree?Connect contributions to the relevant uses and shared conditions through section 4.1. A future system can be described before an actual holder exists.
Functioning and the system soughtWhat must the system do in use? What kind of system are we seeking by that function?State the required behaviour, then a functional description such as “coolant circulator” and the conditions for a suitable candidate. Section 4.3 explains how this opens the choice of constructions.
ConstructionWhat organization, parts or materials could provide that functioning?Compare possible constructions and their operating conditions through C.32.P2S and the C.30 family.
Ways of obtaining the systemHow could the chosen construction be produced, changed, verified and kept usable?Identify applicable Methods and what they require. A.3.1 and the A.15 family distinguish a way of doing from its plan, performance and result.
Creator contributions and fitWhat work and results do those Methods require, and which people, teams, equipment or other systems can supply them here?Select or develop capable creators. A.2.2 compares their qualified abilities with the demand; an occupation name or assignment does not settle that comparison.
Cooperation and needed creatorsHow can the contributions be available together, and which creators must themselves be obtained or changed?Resolve shared resources, access, authority, timing and handovers; repeat the reasoning for a missing builder while retaining the results its contribution must serve. Section 4.3 develops these connections.
Local result and receiving useWhat is our present subject, who or what uses the result next, and how does that use serve the SoI?Preserve a useful component, instrument, description or argument at its own scope and establish the relation the next use needs.
Grounds and revisionWhat supports the answers relied on together, what remains unknown, and what changed condition sends us back?Use section 4.3.1 to compare whole proposals and revise affected answers. Use A.10 when evidence support is the question and B.3 for a named assurance use.

First follow the anticipated contribution toward receiving use and examine the relevant containing whole upward, at the operating time. With that basis available, reason backward along the providing flow to what must be obtained and downward into construction to what could realize the functioning. These are two axes: a creator can provide a system without containing it. Test the proposed causal connections forward, then follow actual results as they become available. Reasoning direction, subject relations and planned or performed Work order remain distinct.

When actual relations or a network are the question. A proposal can be compared before it has been realized. An actuality claim needs the facts for that claim. For an actual runtime change, identify the environment or input referent that changed under A.3.4 separately from the existing system’s functioning, causal, interaction or participation claim. Add an assignment, Method or Work claim only when it is needed and independently supported. A required effect or an observed output alone does not establish that change or those system-side relations.

For an actual production account, distinguish Work, changes of continuing materials or parts, production participation, the new entity’s identity inception, completion and later use through A.15.PROD and the relevant subject patterns. A system cannot undergo a change before it exists. Use an available recognition result for an actual system; section 7 supplies the return when systemhood is unresolved.

When the receiving question needs a transformation-flow structure or a network of such structures, use E.18 to identify each TFS and E.18.NET for the network. The latter requires independently identified members, exact obtaining cross-member relation occurrences, complete endpoint bindings, applied constraints and the use frame. Production, operation, verification, feedback and recursive builder branches can concern different members.

A shared entity, temporal adjacency or a drawn arrow supplies no relation between them. Keep a proposed network provisional and name the missing member, governor, predicate result, occurrence or binding. An ordinary project explanation need not make this network claim.

A.1.STM:4 - Solution

A.1.STM:4.0 - Connect a noticed difficulty with the project account

B.5.PI:4.1–4.5 supplies the general way to initiate inquiry before a problem is felt; its section 4.2.1 explains how a suitable mantra can expose an unexamined connection. Here that operation uses the system-thinking account.

A difficulty, opportunity or task can be the point at which attention starts. Recover what happened or is proposed, whose result or condition matters, and what question a useful answer must settle. A complaint such as “the calculation takes too long” is a signal: it leaves open whether the difficulty concerns a needed product decision, an unsuitable calculation, unavailable means or another purpose. Use C.22.2 when the continuation needs a reviewable problem-side account. If a direct subject Method already answers the question, use it; an ordinary difficulty does not have to become a project or acquire a system-of-interest.

Move into systemic project reasoning when that question depends on how a system’s use, construction or creation contributes to a project result. Follow the concern to the receiving use that gives it significance. The slow calculation may matter because it prevents a construction decision needed for the machine’s intended operation; the inquiry must then recover that operation before selecting faster equipment. This transition turns the initial signal into a more discriminating question or hypothesis: which required result is unavailable, through which dependency, and what would change the answer? Sections 4.1–4.3 supply the connected reasoning. If the use basis is already adequate, section 4.4 can locate the particular gap without reconstructing it.

The mantra enters the same reasoning from the project account. It prompts examination of use, functioning, construction and provision even when nobody reports a difficulty. For example, it can reveal that a new sensor will be inaccessible for calibration although every team is content with its local design. The missing joint condition becomes a question to investigate; it is not a diagnosis proved by the reminder. Starting from a complaint can reconstruct that same dependency without prior knowledge of the mantra. The reminder makes the consequential questions available directly, while the developed account explains why those questions matter.

Thus the point where attention starts and the order of justification have different jobs. The entry reveals a candidate question. In a systemic project comparison, use and encompassing functioning supply the first grounds for deciding what to construct and provide. A discovered constraint can send the reasoning back to those grounds. Return a supported answer, a changed proposal or a precise uncertainty to the original concern, then obtain the needed subject contribution and follow its receiving use. If no project dependency is material, finish the direct inquiry at its own scope.

A.1.STM:4.1 - Establish the project system-of-interest, its use and the participants’ agreement

Start with the intended use because it tells the participants what their internal choices must accomplish. Describe the operating situation, its time or period, the affected participants and the changes or maintained conditions that matter to them. Ask what would be lost if the proposed system were absent, unusable or no longer maintained. The answer can concern a desired change, a condition that must continue, or a harmful effect that should cease. “Produce the deliverable” is insufficient while nobody can say what obtaining that deliverable is supposed to enable.

Follow the intended contribution toward its recipients: what will use the result next, and what will that use change or keep possible? Set out the boundary of the system being considered at the operating time, provisionally when the design is still open. From that boundary, move upward to the larger physical or operational whole of which it is, or is intended to be, a part. Identify the other parts and explain how their joint functioning produces the receiving result. For a pump, examine the water-supply installation: the pump’s contribution depends on the inlet supply, downstream path, power and control arrangements that make delivery possible. This account gives reasons for the pump’s required function before the choice of its internal construction.

Continue through the levels and supported inclusions whose conditions can change the decision. A pump can be part of a pump assembly that is itself part of a station; demands on the station can constrain both the assembly and the pump. One tree need not represent every relevant inclusion. State the whole, part relation and operating time for each relied-on connection, and reuse an adequate account already obtained for it.

Keep the two relations visible. Moving along receiving transformations follows what affects or enables what. Moving upward through system composition follows which system is part of which larger system at the time considered. A using system need not contain the used system, and a manufacturer is not its product’s suprasystem merely because it makes the product. A manager, owner or larger project is also not an encompassing System by title or scope. A.1 and A.14 govern a relied-on composition claim; C.30.STRAT helps when a level word still hides its meaning.

When the larger functioning whole or its composition is unknown, keep that question open and obtain the missing account. Inspect the operating arrangement, consult those who understand it, or investigate a proposed configuration. Describing neighbouring objects and their interactions can supply evidence for this work; it does not complete the upward move. State which function or construction judgement remains unsupported and continue inquiry or other work whose grounds are available. A.1:4.2’s possible participation in a larger assembly is a recognition condition; it does not identify the containing system and functioning needed for this project decision. Neither that condition nor the absence of current knowledge removes this inquiry.

Use the larger whole’s functioning to propose how the system’s functioning or other intended trajectory could meet the need. Refine the proposed SoI and its boundary, and describe it as a black box: what it encounters, what it does or permits, which conditions it must tolerate, and what its users or other affected participants regard as success. A functional name such as pump, learning aid or diagnostic instrument is a useful hypothesis; it does not settle the physical boundary or the A.1 system criterion.

For a system still to be created, this is a possible future operating situation. Describe the proposed holder, interactions, receiving changes and conditions without asserting that the holder or effects already exist. A desirable outcome gives a reason to investigate a design. Explaining how it could occur requires a mechanism and conditions: for example, how flow, pressure and the surrounding installation together could deliver water at the required outlet. Qualify that hypothesis with suitable engineering grounds and revise it when tests or later use disagree. The purpose alone supplies no causal connection.

Compare the participants’ accounts. Ask each relevant team and external participant to explain the proposed SoI in the same use situation and to locate its own contribution. Differences become actionable: one team may describe the provider organization, another the delivered system, and another the report about it; two teams may intend incompatible configurations under the same name. Resolve the consequential differences through inquiry, conversation, option comparison and, when needed, experiments or prototypes. C.11 helps choose among formed alternatives; it supplies neither the creative formation of those alternatives nor proof that several participants understand and accept the same choice.

Seek a working agreement adequate for the decisions being made: the systems-of-interest and project contexts involved, intended uses, relevant boundaries, success conditions and the contributions that rely on them. Participants may retain different interests. State a consequential unresolved disagreement and who can settle the affected decision; do not present a single chooser’s designation or a shared document title as evidence that agreement already exists. The useful result is a supported, revisable basis that the participants can use together. Inquiry and negotiation may still leave an important designation or agreement unresolved.

A project can seek several systems and other results. For example, a project may supply independently identifiable instruments to two laboratories, together with explanations and operator preparation. Recover each receiving use and the shared conditions that constrain the current decision. Neither the project label nor this plurality makes the instruments, explanations and preparation one System. When the question concerns one instrument, ordinary reasoning can follow that SoI alone while retaining any dependency that matters.

Different product undertakings can have different SoIs and boundaries. A supplier’s engine, an integrator’s aircraft and an operator’s transport installation need not be the same entity. Recover the usable supply, recipients, product decisions and fitness obligations at each boundary, then agree the contributions and conditions used in the joint work. The customer may specify the engine’s whole design and intended use; the supplier need not control the customer’s product strategy. The engine’s receiving use constrains its fitness without making its supplier responsible for every later aircraft. A separate project, budget or contractor for the same organizational work leaves its product-use basis in place.

Keep these answers distinguishable:

ExpressionWhat it selectsPractical consequence
System-of-interest (SoI)The system whose intended use and expected benefit supply the common purpose of the relevant creator cooperation.Recover that use, its recipients and contribution conditions. One or several product SoIs can constrain organizational work; each future system remains described until it exists.
Current subject of inquiry or local work; system-in-hand for a systemWhatever must be understood, obtained or changed for the present decision.A creator can be fully engineered and locally accepted while the product SoI and its use continue to justify that work. Methods, epistemes and other subjects retain their own names.
Required functioningThe behaviour or contribution needed in use, such as circulating coolant at a required rate under stated conditions.Supplies a demand to investigate; it does not yet select a construction or establish an actual effect.
System named by its functionThe kind of system sought for that contribution, such as a coolant circulator.Opens the search for suitable systems and constructions. This functional classification differs from the system’s role in the project.

This Library uses system-of-interest (SoI) for the system identified in relation to the undertaking described below. The meaning here keeps the useful product and its creators’ common purpose in view. When another source uses system-of-interest merely for whichever system an observer investigates, recover that source meaning explicitly; use system-in-hand for the local system in the present account. “Our system” needs the relation that makes it ours: what we make, change, operate or provide.

A component, instrument or machine can be the SoI of a distinct product undertaking when it is supplied for use to identified recipients or a known class of recipients, with a bounded product decision and obligations for its fitness. For example, a test-rig manufacturer supplies a usable instrument to laboratories. In the pump cooperation, a laboratory developing its test capability remains a creator, and its rig can be the local system-in-hand. The actual supply and obligations explain the distinction; incorporation, internal transfer prices, a contract or the word project do not settle it.

An organization being created or changed remains a creator with its own engineering object. A new team, factory or business can have a complete design, agreed boundaries, a budget, a contract and finite acceptance. Its product or products still supply the SoI for this work. This applies equally to an internal team, an external consultant and a supplier of a ready-to-operate enterprise. Valuing or selling the organization makes it an object of an investment or transaction; its price, asset value and ownership rights do not replace the useful use of its products.

A changed product purpose requires reconsidering the sought results, recipients, boundaries, funding basis and dependent agreements with those entitled to change them. Participants may develop another offering or end one that is no longer justified. Make that decision explicit. A new label for the same organizational work changes none of those grounds.

A.1.STM:4.1.1 - Develop a creator from the use its products must support

For work that creates or develops an organization, connect three answers: what product use and benefit must become possible or remain possible; what the creator must be able to do for it; and what local result this work will deliver and how it will be accepted. Use this connection in the choice and provision of work. Reuse adequate existing answers; a separate form or a fresh account of the entire enterprise is unnecessary.

  1. Name the product use that gives the work its reason. State the required change or preserved condition in use, the recipients and conditions that can alter the decision. For a shared creator, name the products or application classes whose demands affect this choice. Necessary accounting, maintenance, learning, funding and future capability can deserve provision through the work they enable; proximity to a product drawing is not the test.
  2. Derive the needed capability. Explain what the creator must reliably provide under the expected workload and conditions: relevant Methods, people, means, access, cooperation and authority. Retain the creator’s own boundary and architecture questions. An agreed purpose gives a reason for that capability; it does not establish the mechanism, available resources or people’s ability to perform.
  3. Choose a finite local result and its acceptance. State which capability, or bounded contribution to it, this work must establish and what evidence can establish it now. Acceptance of an installed machine, a research report, a prepared team and a functioning workshop answers different questions. If workshop capability is promised, establish that the needed Methods, means, people and handovers can work together under the agreed conditions. A component delivery can close while the wider capability remains open.
  4. Make provision and trade-offs real. Obtain the resources, access, time and authorized agreements that the chosen capability requires. Where products compete for shared capacity, compare the affected uses and commitments together. State who may change the allocation or accept the loss; a local manager can decide within delegated authority, while a loss outside it goes to those entitled to decide. Neither one product’s improvement nor one department’s metric settles what happens to the others.
  5. Close this work at its agreed scope and retain the receiving connection. Judge the local result against its actual acceptance basis, including the evidence sufficient for the promised capability and the declared uncertainty. Do not wait for every future product to operate. Keep the expected product effect conditional on its remaining contributions and use conditions, and state which later observation would reopen the capability or product decision.

Unknown future uses can be represented by application classes, scenarios and explicit hypotheses. When the receiving result is an episteme or another non-System subject, keep that result and its use explicit; leave a needed systemic designation open instead of filling it with the creator.

Research may establish that a proposed benefit or capability is infeasible; a well-grounded negative result can support revision or stopping. Judge an independent research result by its epistemic question and acceptance criteria. When commissioned to inform a capability decision, also assess its fitness for that decision. Accepted knowledge does not itself establish the capability it investigates. A theorem, historical explanation or openly reusable knowledge needs no invented physical SoI or immediate commercial application.

Keep provision and benefit connected but distinguishable. A customer, user, payer and investor can be different participants. Funding, an internal allocation, income or an asset sale can make work possible without establishing product usefulness; a justified useful result can precede revenue or rely on subsidy. Give those who decide resources and acceptance the relevant product-use and capability consequences, together with the rights and financial conditions of the choice.

A.1.STM:4.2 - Keep role, holder and future description distinct

The SoI role relates a System to the product use and common purpose explained in section 4.1. A holder is the actual System occupying that place; a description states what the participants intend or believe about it. These can be discussed together without treating them as the same object. An existing pump remains the project’s SoI when it fails a performance test: success is what the participants seek, not a condition that makes a failed SoI disappear from the undertaking.

Use ordinary role wording under A.2:4.9 while it is enough. If classification matters, define the local system-role kind under A.2 and C.3 through its System candidate domain and the work-facing distinction the project needs. For a SoI classification, the criterion must express that product-use and cooperation relation together with the designation grounds. A rig investigated only to support another system does not thereby take that other system’s role in the wider project. A criterion that selects merely whatever an observer studies answers a different question. If the needed criterion or its governing relations are unavailable, retain the ordinary project account and leave that technical classification unresolved.

If assignment identity matters, A.2.1 requires an obtaining occurrence with an actual System holder under a declared species. System recognition, project designation, classification and assignment remain different claims; none is created by writing the role’s name.

A new system can be intended before any holder exists. Agree the SoI role, intended use, required characteristics and boundary hypothesis in a plan or description. Describe the intended holder, its proposed identity rule and how later instances would be recognized. Before identity inception, this is prospective content, not an actual System or assignment occurrence. A.15.PROD separates production participation, the first satisfaction of the entity’s identity rule, and completion. After inception, relate the actual holder to the earlier description and evaluate the claims needed now.

Design reasoning also works with types, variants and repeated provision. A project may intend a series of systems satisfying a common specification rather than one already named individual. State the common intended use, the distinguishing requirements and what counts as one resulting instance; track actual holders as they become identifiable. The specification, the kind it describes and a collection of instances do not thereby become one System. Where materially different SoI families have different users or use conditions, preserve their separate SoI accounts before comparing shared builders. A vague umbrella such as “equipment” does not supply that comparison.

A.1.STM:4.3 - Derive the long mantra from the intended use

The order below gives the direction of project justification: establish intended use and the wider functioning first; then investigate construction and the ways of obtaining it. An answer supplies requirements, possibilities or limits for other answers; it need not determine them uniquely. Reuse an adequate outside-use basis. Later construction or capability knowledge can reopen it. Resolving these mutual constraints, including such returns, makes the account usable.

  1. From the system boundary upward to encompassing functioning, then to the SoI contribution. Describe the required receiving change or maintained condition in a selected operating situation. From the proposed SoI boundary, identify the larger functioning whole, the other parts and the joint functioning in which the SoI contributes. Follow the relevant levels and supported inclusions as section 4.1 explains. Derive what the SoI must do, through which interactions and under which conditions, for that result to be possible. An unknown containing whole leaves this derivation open and calls for inquiry. Work through the scenario before justifying an internal solution. If the SoI does not yet exist, retain this as a future-use hypothesis; investigate its mechanism and conditions.

  2. From functioning to the system sought, then inward to possible constructions. Name the kind of system being sought by what it must do in use. For example, after stating the required circulation of coolant, “coolant circulator” names the sought thing by that function. Use the functional description and operating conditions to identify suitable candidates before choosing their construction. Compare why different arrangements could meet the same demand and where they would fail. The name helps search and communication; suitability needs an argument about the candidate under those conditions. Starting with a favourite component can conceal an alternative construction that would serve the use better. C.32.P2S and the C.30 family develop that architecture choice; A.1.SCR tests an actual proposed whole when systemhood matters.

    Required behaviour and the system sought are different answers even when one phrase expresses both. “Circulate coolant” states an action; “a coolant circulator suitable for this circuit” identifies what is being sought. Neither requires an extra field or a different word when the existing explanation is clear. Informal functional role wording may express this functional consideration. It does not by itself establish an assignable system-role kind under A.2. Use A.2 when classification by a stable, assignable contribution to work is needed; use A.2.1 for a claimed assignment. The functional description, chosen construction and proposed or actual system remain distinguishable.

  3. Backward from the needed construction to ways of obtaining it. Determine what must be produced, assembled, changed, learned, verified or maintained for the proposed construction to support the intended use. Compare the necessary Methods and their subject matter. For example, choosing a welded assembly, a learned controller or a different service arrangement changes the ways and capabilities needed to obtain it. A.3.1 and the A.15 family distinguish the reusable way, intended work, performed work and its results.

  4. From Methods to creator contributions and capable performers. First state the kind of work and result required by the chosen Method: for example, joining the selected material by welding, producing a learned controller, or calibrating the assembled instrument. Name the corresponding creator contribution in familiar professional terms when this helps find the needed practice. The Method and its subject matter give that name its meaning; a job title alone does not supply the way of doing.

    Then compare concrete people, teams, equipment or other systems that could provide the contribution under the required conditions. A change from welding to another way of joining can change the needed contribution, tools and capable performers even while the intended product stays the same.

    Use A.2 for a needed system-role classification or assignment question and A.2.2 to establish qualified ability and fit. An able candidate can be considered before it is assigned. Tools can participate in production without being independent agential performers; A.13 and A.15.1 govern any actual performer and Work claims.

  5. From capable creators to their cooperation. Determine how their contributions can be made usable together. What must each receive from another, what shared conditions must remain true, and which decisions or changes must be agreed? Separate capability from availability and authority: each contributor may know how to perform its part while their combined work cannot obtain the result. Develop candidate arrangements of contributions, information, resources and decisions through C.32; use B.1.5.EW when the constituent and encompassing work is unclear. A common aim explains why to cooperate but does not settle how. If organization or supporting equipment must change, that becomes another creation question rather than a promise supplied by a team name.

  6. Repeat for the creators that must themselves be obtained. A missing instrument may need manufacture; a team may need training or organization; a production installation may need redesign. Apply the same questions to that local system while retaining its contribution to the original SoI. A builder’s period of use can be a period in which another system is produced or changed. This connection is not composition: a factory is not a constituent of its product.

  7. Follow each local result into its receiving use. State what receives it next and what that use is expected to enable on the way to the common SoI. Inspect the resulting facts as work proceeds. Failed tests, new interests or an unworkable method may reopen the construction, functioning, SoI boundary or even the original purpose. Reopen the premise that failed rather than protect the earlier choice because work has already been spent.

    When the SoI, intended use, boundary or expected contribution materially changes, compare the affected participants’ accounts again and trace which decisions rely on the changed premise. Restore the agreement needed by those decisions and make its revised basis available to the participants who must use it. Agreement between two teams does not update other dependent teams’ decisions; resolve or expose that remaining difference before relying on their combined work. Unaffected decisions need not be reopened.

An inverse inquiry can begin with an available person, tool or scientific result and seek a worthwhile use. Once a possible application is found, recover its receiving effects and wider functioning before justifying the construction or provision proposal. This preserves the same direction of justification without pretending that use was known at the start. Negotiation, exploration, fabrication and testing may overlap or repeat. Use a WorkPlan for intended execution order and actual histories for what happened.

A local result keeps its own kind and closure. A drawing’s content or a research argument can be an episteme; a measurement result can concern a characteristic; a completed workpiece is a separately identified entity. Show the connection through the relation needed by the next receiver, such as use of a description in design, installation of a component, or evidence supporting a decision. A.15.6 recovers the result and closure question; A.15.PROD distinguishes entity inception and production completion from later acceptance or use. The local result need not be a System to matter to the SoI.

Also separate two questions: is this Work part of the project Work, and does its result help obtain the SoI? Actual Work parthood uses A.15.1. A purchased instrument or a published theory may be useful even though the work that produced it was outside the project; an admitted project Work part may fail to make the expected contribution. Prospective dependencies justify plans under their stated assumptions. Actual relations and outcomes need their own evidence as they occur.

A.1.STM:4.3.1 - Assemble and revise a jointly workable account

Take the question reached through section 4.0 and recover the intended use and wider functioning that give it significance. Reuse that basis when sufficient; otherwise develop it before justifying a construction or a choice about its creators. Then recover the other answers already available and the conditions under which each is supported. A required use, a proposed construction, a demonstrated capability, an agreed resource allocation and an observed result have different grounds. Keep an important unknown or disagreement visible. A drawing that leaves it blank is not evidence that the condition is satisfied.

Explain how the subject matter of each answer constrains the others. The expected outside effect constrains the needed functioning; a construction makes some functioning possible and rules out other functioning; a creation Method requires particular subjects, capabilities and conditions; a cooperation arrangement determines whether those contributions can be available together. These relations need the relevant engineering, research, economic and organizational knowledge. The mantra recalls where that knowledge matters; it cannot deduce an unknown material law or create a missing production technique. Obtain the missing subject answer and bring back its conditions as well as its conclusion.

Compare coherent combinations. Do not combine the performance of one design with the cost of another, the capability of a fully prepared team with the schedule of an unprepared one, or a successful test with a later configuration the test did not examine. For the candidate under consideration, ask why its functioning, construction, obtaining Methods and creator arrangement can jointly serve the intended use. A supported local answer becomes part of this account only with the conditions needed for its use in that combination. The whole may remain a justified proposal; compatibility of the proposal does not establish that it has been realized.

Challenge the connection where a different allowed answer could matter. If a component, operating condition or creator changes, which other answers still hold, which must change and which become uncertain? Follow the material dependencies rather than changing every document or defending every earlier choice. A single defect can have several repairs: revise a construction, obtain another capability, change a way of producing it, or reconsider the promised use with those entitled to make that decision. Each repair has its own conditions and cost. Merely moving to the next phrase of the mantra chooses none of them.

Choose the next inquiry or construction for the consequence it can have. A missing fact may require measurement; incompatible answers may require a new alternative; disagreement may require clarification or negotiation; unavailable capability may require provision or development. Use the relevant subject Method and compare consequential alternatives when necessary. An unresolved release condition can leave release unavailable while inquiry, prototyping or obtaining support remains possible. Several independent questions may be pursued at once. Their results must return to the same candidate assumptions before being relied on together.

This is the useful sense of the analogy with solving simultaneous equations: partial answers restrict one another, and changing one can require changing others. It does not say that all questions have numerical variables, that normative agreement is an equation, or that a unique solution exists. Some hypotheses may remain unresolved; some sets of requirements may be incompatible. A project can narrow or reject a proposal rather than fill every line with an unsupported answer.

The compact mantra makes the direction of justification easy to recall. Attention may first be drawn to any consequential answer, and inquiry can explore alternatives or develop answers together. Use and encompassing functioning nevertheless provide the basis for the inward and creation-side choices; changed knowledge returns to that basis when necessary. Use A.22.CGUS when the available continuations and their conditions need explicit treatment. Its ordinary branch makes those alternatives and unknowns clear; a formal CGUS claim additionally needs the structure and qualification that pattern defines. A teaching traversal of that structure still does not prescribe the order of Work.

When the connected account changes a provision decision, carry the result to the participants who can make it effective. Establish which work, means, access, authority and timing the chosen combination requires; obtain the needed decisions and support through their subject Methods. A named capable creator or an approved allocation does not by itself make a resource available. Follow actual provision, performance, the next receiver’s acceptance and later use separately. Reopen the premise contradicted by the returned result while retaining valid local closures.

Keep other project inquiries connected through their shared subjects and assumptions. A choice of creation Method affects capability and resource needs; an operational proposal can expose a capacity limit; a strategic change can reopen which result is worth obtaining. These inquiries do not all have the same purpose or one mandatory ordering. Carry a changed answer to the other inquiry only when it changes a premise used there. The result is one mutually intelligible account, not identical documents or one person deciding every question.

For the decision now being made, stop when the necessary answers and their relevant joint conditions are supported, or when the unresolved condition and its consequence are explicit. Make the resulting reasoning available in the project’s ordinary prose, drawing or table: what changed in the proposal, why, and what each affected participant, including yourself, needs to do next. When working on one creator-to-result connection, show how it reaches the common SoI; extend the inquiry only as far as the current decision needs. Preserve accepted local results whose grounds still hold. Continued project reasoning, later operation and further development can open new questions without making every completed local result unfinished.

A.1.STM:4.4 - Locate the first unsupported dependency

Use this narrower mode when the shared SoI and intended-use basis is already sufficient for the current question. It also helps name a precise next inquiry when one part of that basis remains disputed.

  1. Choose by the result needed now. Name the decision or question and its connection to the common project SoI: for example, choosing a boundary, comparing constructions, obtaining a missing capability or deciding whether a result is ready for its next use. If a local result is current, say what it is about and what receiving work needs from it. If another long mantra better answers the local question, use it while retaining the shared SoI basis.

  2. Place supported answers and the current scope. Keep the answers already available, their grounds and the conditions for using them together. Distinguish a prospective hypothesis from a fact and make an important unknown or disagreement visible. An ordinary explanation or existing project note is enough. Use the conditional network branch in section 3 only when that stronger claim is needed; the network is not project Work.

    If the receiving question is whether a local case can be closed, state four things in ordinary language: the exact subject or claim; the bounded references and direct claims needed to answer this closure question; the separately governed closure basis; and one named downstream receiving use that remains outside the closed case. A.15.6 supplies any technical reference form that this question needs. A design inquiry can end with a supported proposal or a next inquiry without making a production-completion claim.

  3. Find the first unsupported dependency. Work backward from the answer needed now to the missing, stale, disputed or unsupported answer that prevents the next justified move. First means first on that logical dependency, not earliest in the calendar.

  4. Use the subject pattern. Obtain the missing answer through the Method whose Use this when fits the question. Retain the answer with its conditions, or the named stop.

  5. Return what the next use needs. Reconsider the affected combination using the returned answer. Individual answers can suffice. Select an E.18.NET network only with its independently identified members, obtaining relations, constraints, use frame and complete endpoint bindings. Select another A.22 structure only when one named use needs their organization and all four identity discriminators pass. Otherwise retain the direct plurality or Plain provisional map.

  6. Follow the consequence and revise. For a proposal, test whether the answers could be used together under their stated assumptions. As work and use occur, follow the actual Work, production, identity, change and participation claims through their subject patterns, including each relevant builder branch. Bind evidence to the claim it supports. A missing direct link blocks the claim that needs it; preserve independent results and reopen the smallest affected earlier answer.

Four orders remain separate throughout: the order used to teach the map; the logical dependency read backward; planned or actual Work order; and the subject relations that obtain. One ordering establishes none of the others.

A.1.STM:5 - Worked uses

A.1.STM:5.1 - Common pump SoI, separate organizational contributions

The intended operating situation requires reliable water delivery at the user’s outlet. Start there and, from the pump boundary, examine the water-supply installation of which the pump is a part at that time. Explain how the pump, inlet supply, downstream path, power and control equipment work together to maintain delivery. Demand and the required continuity of that whole determine the pump’s needed flow and pressure under the stated conditions. “Water-delivery unit” names the sought system by that contribution. The claimed mechanism needs engineering grounds; the desired outlet result alone cannot establish it.

Suppose only the pump drawing and desired outlet flow are initially available. The team cannot yet derive the pump requirements from the installation’s functioning. It obtains the installation arrangement and operating information, identifies the other parts and checks how they cooperate to supply the outlet. If the missing fact concerns upstream storage or control, that becomes the next inquiry. A list of nearby pipes or the pump manufacturer’s name would leave this account unfinished. Once the required account is supported, the team can reuse it when comparing internal pump constructions.

In this modernization project, the operator, controller supplier and maintenance team designate the existing PumpUnit-3 as the common SoI for the selected use. A supplier offering a usable controller under its own bounded delivery obligations can also have the controller as its product SoI. A separate project to develop the test laboratory has the laboratory as its engineering subject, with pump qualification providing the use basis. The water-supply installation is relevant through composition and operation; the supplier and laboratory are relevant through creation and provision. A.1 recognition, project designation, any local system-role classification and any assignment remain separate questions.

With the use basis available, compare constructions such as variable-speed regulation or a pressure-regulated bypass, with their different energy, operating and maintenance conditions. Then reason backward to how each could be produced and qualified. These are proposals whose suitability must be investigated. The following inquiry concerns a construction with a controller and sensor; its test arrangement must fit that construction.

A.1.STM:5.1.1 - Locally plausible answers that do not fit together

Suppose a proposed pump assembly must meet a stated delivery condition after installation. A functioning argument assumes a calibrated sensor in the completed assembly. The construction encloses that sensor, the production Method closes the housing before the proposed calibration, and the available calibration instrument needs physical access that the closed housing does not provide. Each team’s answer may have worked in another configuration. Together, these particular answers leave the proposed qualification impossible as described. A common SoI and three signed local documents would not repair that incompatibility.

The team can now compare different whole proposals. It could change the housing to preserve calibration access, provided the changed construction still meets its operating requirements. It could propose calibration before closure, but then must establish why closure and installation would preserve the calibrated condition or how a later check can detect a consequential change. It could obtain another measurement arrangement, provided that arrangement can establish the required claim in the completed assembly and can actually be supplied. None is established merely by being imaginable.

The teaching explanation may run from required delivery through functioning, construction, production and calibration capability. The actual discovery began at a calibration question and returned to construction. A drawing, experiment or qualified measurement may supply the missing answer. If the team changes the housing, it reopens the affected operating and production assumptions; if it changes the instrument, it reopens the measurement and provision assumptions. It retains unaffected knowledge and restores agreement among the contributors whose decisions changed.

This case shows why the mantra must connect whole bodies of subject knowledge. Repeating “function, construction, method, creator” cannot supply the missing measurement argument. Conversely, a complete measurement argument for an inaccessible configuration cannot settle the project question. The connected account identifies what must be explained, which alternatives remain open, and where the answer will matter.

For the next project step, suppose the proposed housing can still be revised, but no alternative calibration instrument with demonstrated fit is available. The team chooses to investigate an access feature in the housing: the designer develops an option, the production specialist checks whether it can be made, and the calibration specialist checks whether it permits the required measurement. Their next result is a jointly supported option or a reason to return to the other repairs, not a claim that the pump is already qualified. If sealing or strength rules out the access feature, that result reopens the pre-closure calibration or alternative-instrument question. The operating requirement remains in force until those entitled to change it agree otherwise.

This also distinguishes a creator contribution from its performer. The chosen option may require housing redesign, manufacture and a calibration argument. Those descriptions guide the search for suitable people and equipment; naming a designer or assigning a laboratory does not establish their fit. If the measurement Method changes, compare its required access, range and conditions with the proposed laboratory and instrument again, then check that design, fabrication and calibration can obtain their shared inputs in time.

A.1.STM:5.1.2 - When actual production and use must be established

The design inquiry above can finish at its supported option. Later, an installation decision may ask whether the controller has actually been produced and is ready. Use A.15.PROD for the particular question: production participation, identity inception or completion. ControllerSubassembly-7 and other pre-existing materials can be continuing subjects of changes; the future controller is not transformed before it exists. Identify the actual controller under its applicable identity rule when it first exists, and assess completion or readiness separately. Recover any claimed dated fabrication Work through A.13 and A.15.1; F.6 is needed only for precise assignment-bound attribution.

For a closure claim about this controller-production case, state its subject, the claims and references needed for that question, and the applicable closure basis. The case closes only when the production, identity, completion or readiness claims required by its question are supported, including the required evidence and decisions, and its closure rule is satisfied. Installation and later operation in PumpUnit-3 remain the named receiving use outside this local closure. The ordinary positive branch of A.15.PROD:4.7 can return a readable answer or a precise gap; its stronger semantic or assurance branch opens when the receiving claim requires it.

If the project now needs a network of controller-production, pump-modification, qualification and operation flows, identify each member through E.18 and apply E.18.NET. Establish the actual production, installation, participation, use or feedback occurrences and their endpoint bindings; keep applied constraints and the use frame explicit. Until those conditions hold, retain the proposed network and its named missing link. A successful fabrication step does not provide a missing installation or feedback relation.

Follow actual facts from fabrication and changes of existing subjects through controller inception and pump modification to pump operation. For a runtime claim, keep the existing PumpUnit-3 and its functioning, causal, interaction or participation claim separate from an A.3.4 change of the identified continuing delivery-side environment or input referent. If dated runtime Work is also claimed, use A.13 and A.15.1 for that claim, adding F.6 only for precise assignment-bound attribution. The reliable-delivery hypothesis establishes neither actual claim. A failed relation or missing binding stops the dependent claim while preserving valid local results.

If later operation shows that reliable water delivery depends on an upstream reservoir-control assembly outside the proposed PumpUnit-3 boundary, the team reopens the outside-use, project designation and boundary hypotheses before revising the architecture and any network selection. Work already spent does not make the old boundary adequate.

A.1.STM:5.1.3 - Two products sharing one creator

A shared laboratory supports water-supply pumps that face frequent starts and irrigation pumps that run continuously. These product uses require different test conditions. The laboratory has eight available bench-hours tomorrow, with four promised to each product line. A water-supply failure now needs four additional diagnostic hours. Renaming that work a priority project would not supply twelve hours or settle the irrigation commitment.

The laboratory manager compares the consequences: delaying diagnosis blocks the water-supply commissioning decision; displacing the irrigation test delays its delivery. No qualified extra shift is available. A qualified external laboratory can perform the irrigation Method and return the required result before its deadline, including sample transport. Outsourcing is allowed for that result, and the manager has authority to buy it within a reserve that covers the confirmed price.

The manager obtains that commitment, informs the affected receivers and keeps the eight internal hours for the promised water-supply test and the additional diagnosis. Both product requirements and deadlines remain explicit. The decision is local because the manager’s delegated authority covers the changed provision and expenditure. Without a suitable external commitment or that authority, the manager would have to return the unresolved trade-off to those entitled to change the product commitments; calling the laboratory the SoI would not settle it.

This one-off allocation does not establish a case for permanent expansion. If expected demand justifies developing the laboratory, a temporary organizational project can provide a defined capacity for both test classes. Its acceptance can establish compatible Methods, equipment, qualified people, sample access, handovers and capacity limits. The project can then close before future pumps operate. The test report, the laboratory’s demonstrated capability and each pump’s fitness remain distinct results. An internal budget transfer provides means; it is neither external customer income nor evidence of product usefulness.

A.1.STM:5.2 - One-off service: a usable hairstyle

A client and a stylist first describe the intended use: the appearance the client seeks while moving through an event and later ordinary conditions, including possible rain. Starting at the proposed hair-and-fastener assembly’s boundary, they examine the larger physical whole in use: the client with the worn hairstyle, including its attachment and the bodily movements it must accommodate. They must establish the claimed composition and explain how those parts function together. If that account is missing, they investigate it before treating an internal arrangement as justified. The event and other people also matter through interaction and reception. They then compare arrangements of hair and fasteners, cutting and styling Methods, a capable stylist and suitable tools. The salon contributes through creation; it is not a containing whole of the worn hairstyle. Merely completing the hair operations would leave the purpose unmet if the result cannot survive the agreed use.

The embodied hairstyle is the proposed SoI; the salon is a provider, the sketch is a description, and the appointment’s Work has its own boundary. Before the hairstyle exists, its designator belongs to the agreed description. For an actual system claim, A.1.SCR evaluates that exact proposed hair-and-fastener whole, its identity and physical organization; it does not substitute the client merely because the client is already a recognized System.

If the whole is established not to satisfy the System criterion, reject that System interpretation. If necessary facts are missing, leave recognition unresolved and name the missing basis. In either case, preserve the supported service and result claims; do not treat those claims as settling the project’s common SoI. The ordinary hairstyle name alone settles no systemhood question.

The sketch can be complete before styling; styling Work can end before the later use has been observed. Each local closure remains available at its own scope. A later failure under the agreed use conditions can reopen the design or service decision without making the earlier sketch an unfinished episteme or erasing the Work that happened.

A.1.STM:5.3 - Knowledge development with an epistemic result

A materials-instrument team is developing a diagnostic installation for laboratories. Its intended use is to distinguish two material failure mechanisms, so that installation is the product SoI. A bounded research project investigates an explanatory model and produces an account of experiments; those results are epistemes. The shared systemic account connects model construction, test design and instrument changes to the diagnostic use. The argument and publication can reach their own acceptance before the installation is changed or the improved diagnosis is demonstrated.

This choice depends on the stated research purpose. A project seeking a theorem, historical explanation or openly reusable knowledge must not invent an arbitrary laboratory, reader or computer as its SoI merely to fill a position. Its epistemic result can be legitimate and locally complete.

For the diagnostic research, a supported finding that the proposed model cannot distinguish the mechanisms can finish the agreed inquiry and justify another approach; it does not establish improved diagnostic capability. If participants need a systemic account, they must still establish which system’s useful use supplies their common purpose and how knowledge development contributes to it. An unknown or contested receiving use leaves that systemic basis open without invalidating the separate epistemic result.

A.1.STM:5.4 - The same machine in different project roles

A manufacturer proposes a cutting machine that does not yet exist. First describe its future use at the customer’s plant: which component transformations are needed, what the next operation must receive, and under which operating conditions. Look upward to the production cell in which the machine is intended to be installed and explain how its functioning depends on the machine’s contribution. These are proposed use and composition relations at the future operating time. The manufacturer’s organization is a creator, not that production cell.

The machine is the SoI of the manufacturer’s product undertaking because the manufacturer offers it as a usable supply with defined fitness obligations. The customer can supply the design and use requirements. Recover that use basis before comparing construction, manufacture and qualification, needed creator contributions and their provision. The control software, calibration rig and manufacturer organization are distinct local subjects. Work to develop the manufacturer has its own result and acceptance, judged by the agreed creator capability; the machine remains the product SoI.

The customer’s component-production work uses the machine as a means of production. Its product SoI is the component supplied for a receiving use, which gives the construction and provision choices their reason. In work maintaining this capability, the machine is the local system-in-hand. Its repair can finish under its own acceptance conditions before another component is produced. Moving that repair to another contractor preserves both its finite completion and the component-use basis for providing it.

If the customer undertakes to supply refurbished machines to other users, recover those recipients and their use before comparing the refurbishment. This undertaking can select the machine as SoI too. Explain the resulting requirements and commitments rather than infer a new purpose from the object currently under inspection. Several products, users or linked projects can constrain one decision; use their actual relations instead of assigning them a single universal boundary.

A.1.STM:6 - Direct exits and near misses

Current questionLeave throughNear miss blocked here
Is this exact existing entity a system?A.1 and A.1.SCRA noun, diagram box, plan, system-role label or assignment, or capability does not establish systemhood.
Which omitted Systems may undergo relevant changes that alter the current decision or investigation?A.1.CSDUse the current frame as a starting point for A.1.CSD’s bounded search; keep modal path claims distinct and add a separate actuality claim only when the direct predicate and its case conditions are supported.
Which system is the project’s SoI, and what is the current local subject?A.15.6 for designation; section 4.1 here when the shared basis is unresolvedDistinguish the project role from local attention, the actual holder from a future description, and designation from agreement, classification and assignment.
What is promised, provided, connected, permitted, or stopped?A.6.P §4.11a, then its subject patternService or access does not select a system or one service bundle.
Which inside could support the outside use?C.32.P2S and C.30 familyArchitecture chosen before a stated outside-use hypothesis must return to that missing basis.
What actual runtime change and system participation obtain?A.3.4 and the dynamics, interaction, causality, participation, assignment, Method, or Work pattern needed by the claimAn expected effect, required behaviour, observed output, or project designation proves neither an actual change nor an actor-side or Work claim.
What reusable way, performed occurrence, or actual change is current?A.3.1, A.15.1, or A.3.4Method, Work, and Transformation are different objects and none proves the others.
Did production, identity inception, completion, or readiness occur?A.15.PROD, A.15.5, and A.21 as applicableA final visible step, result label, or DesignRunTag proves none of these claims.
Is this one TFS, an internal subflow, or a network?E.18 and E.18.NETA graph shape, shared entity, or creates label does not identify a network or relation.
Does evidence support this claim, and may a receiver rely on it?A.10; B.3 only for a named assurance useEvidence availability and assurance are not truth, actuality, or map completion.

A.1.STM:7 - Recognition before relying on a system

Before relying on an acting system or changed-system boundary in the map, use an adequate available A.1 recognition result for that entity. Use A.1.SCR when a system-dependent question remains unresolved.

A.1.STM consumes only the returned recognition result. It does not repeat the six-component test, replace the exact entity with a convenient neighboring bearer, infer a system-role assignment from causal participation, or infer Method, Work, transformation, promise, permission, project designation, or a system-role kind from systemhood.

A.1.STM:8 - Conformance checklist

IDCheck
CC-A1-STM-1Participants can recover the product SoI or SoIs, useful uses and working agreement that give the relevant cooperation its common purpose. Local project subjects and results retain their identities and acceptance bases. In the narrower gap-finding mode, the result needed now and first unsupported dependency are readable without a technical record.
CC-A1-STM-2At the operating time, reasoning moves from the system boundary upward to the larger functioning whole and the joint action of its parts, through the levels and supported inclusions that affect the decision. This account grounds the required function before inward construction and backward creation/provision reasoning. An unknown whole remains an inquiry; adequate earlier reasoning can be reused. Transformation-flow and part–whole directions stay distinct. A proposed future use retains its assumptions; actual changes and participation require their own grounds.
CC-A1-STM-3Project SoI, current subject, required behaviour, system named by its function, selected construction and proposed or actual system remain distinguishable where they change the decision. Functional classification alone does not establish an A.2 system-role kind or an assignment. Creator contributions and the fit of concrete performers are considered separately.
CC-A1-STM-4Project Work, an admitted project-level network selection or Plain provisional map, and one minimal case placement retain their own identities.
CC-A1-STM-5The point where attention starts is connected to the order of project justification. A noticed difficulty and proactive use of the mantra can reach the same consequential question; an independent non-project inquiry keeps its own scope. Inquiry returns, Work order and obtaining subject relations retain their different meanings.
CC-A1-STM-6Each local answer states the claims and conditions needed by its receiving use, retaining the subject predicates that govern those claims and any unresolved stop. A cited pattern locates the governing content.
CC-A1-STM-7When a local closure claim is needed, the case states four things in ordinary language: the exact subject or claim; the bounded references and direct claims needed to answer this closure question; the separately governed closure basis; and one named downstream receiving use that remains outside the closed case. Ordinary design inquiry keeps its question, supported answers, joint conditions and next useful action without requiring that closure claim.
CC-A1-STM-8An admitted network has independently identified members, exact obtaining cross-member relations, applied constraints, a use frame, and complete endpoint bindings; otherwise that network proposal stays provisional. A shared systemic account does not by itself require this stronger claim.
CC-A1-STM-9Expected environmental effect, actual runtime transformation and system participation, production, identity inception, completion, later change, and use are separately grounded; required behaviour is not actuality, and no not-yet-existing system is transformed.
CC-A1-STM-10Evidence is bound to its claim, assurance is limited to a named reliance use, and changed grounds reopen only the smallest affected answer.
CC-A1-STM-11The account explains why the chosen answers can be used together under their actual shared conditions; it does not combine locally supported answers from incompatible variants.
CC-A1-STM-12The reader can follow a consequential change to the answers it affects, distinguish possible repairs and their conditions, and recover the difference between the teaching unfolding and performed Work.
CC-A1-STM-13Organizational work connects product use, needed creator capability and a finite locally accepted result under section 4.1.1. Resource choices and acceptance use that connection, including affected products, real provision and decision rights. Remaining uncertainty, research acceptance and later product-use evidence retain their own scope. A new contract or sale of the organization does not replace the product SoI.

A.1.STM:9 - Common anti-patterns

Anti-patternRepair
Mantra as fixed work sequenceUse its connected questions to construct and criticize hypotheses; use direct patterns for local truth and WorkPlan for planned order.
Correct parts, unsupported wholeRecover the conditions under which the particular answers can be used together; revise the failed connection or candidate rather than counting completed questions.
Short formula replaces knowledgeReturn to the developed subject explanation and bring its premises and limits into the common account.
A new contract hides an unchanged purposeFor the same organizational work, retain the product use, creator capability and finite local acceptance under section 4.1.1. A new product supply needs its own usable result, recipients and fitness obligations; a new budget or contractor does not provide them.
Role becomes an intrinsic system typeSeparate the SoI role from its holder and description; test the actual System under A.1 and any technical role claim under A.2/A.2.1.
Project equals networkKeep actual project as composite U.Work and E.18.NET as a selected non-agentive U.Structure.
Case equals subnetworkKeep the local question and its receiving use clear. Recover the closure basis when closure is at issue; select a structure only when one receiving use needs the whole organization.
Creator graph importExplain the required creator contributions and their relations. When a TFS network is claimed, identify its members and obtaining cross-member occurrences; an arrow adds no creator kind or generic creates relation.
Shared entity as edgeName the directly governed production, inception, participation, use, feedback, or other occurrence and bind its participants.
Architecture or provision chosen before its use basisRecover receiving changes and the joint functioning of the containing whole at the operating time, then derive the system’s contribution and justify inward and creation-side choices.
Environment description substitutes for the upward moveIdentify the larger functioning whole and the system’s part relation; when either is unknown, investigate it and retain the resulting limit on the dependent design judgement.
Maker treated as suprasystemRecover the creation or provision relation; use a containing-system claim only where the product is actually or prospectively a proper part at the stated time.
Intended system actsKeep it in plan or description content until identity inception; only an existing admitted system can perform Work.
Systemhood proves WorkTest causal participation, system-role assignment, Method, Work, and transformation separately.

A.1.STM:10 - Consequences

Benefits. Participants can justify local choices by the relevant SoIs and receiving uses, expose incompatible understandings, and preserve those connections while developing builders and other enabling systems. The mantra prompts examination of consequential dependencies before a complaint arises; the developed account connects an already noticed difficulty to the same reasoning. The narrower mode locates a missing dependency without requiring the whole account to be rebuilt.

Costs. Establishing usable project designations and agreements can require domain inquiry, negotiation and experiments. Keeping local subjects, prospective dependencies and actual outcomes distinct adds work, especially across organizations and future product variants.

Limits. This pattern supplies the common systemic reasoning and its return paths. It does not guarantee a correct SoI choice or settled agreement, and does not independently identify a System, admit Work or transformation, close a case, identify a TFS network, or establish evidence or assurance. A local result can be complete while the common system basis or a downstream use remains open.

A.1.STM:11 - SoTA-Echoing

Informative. These source contributions inform use of the long attention map. The named subject patterns remain authoritative for kinds, relations, participants, and pass conditions.

SourceContribution to the patternA.1.STM use and boundary
Levenchuk, Systems Thinking (R5; source manuscript SystemsThinking2026_guide_with_assignments_27nov25.docx), “System-thinking mantra”; Systems Modeling (R6; source manuscript SystemsModeling2026_guide_with_assignments_27nov25.docx), “System-of-interest and collective systems thinking”, “The system-of-interest depends on who seeks it”, and “Hair-salon example as a service provider”A common SoI sustains collective reasoning across division of labour. R5, “Variants of the systems approach”, and R6, the black-box and pump-assembly discussion, require moving from the system boundary upward to larger functioning wholes before considering its parts. The source moves from the needed outside change and that encompassing functioning to behaviour, the system named by its function, possible constructions, ways of obtaining them, creator contributions and suitable concrete creators. It calls for written reasoning on a project, consequential changes and actions, iteration and bounded recurrence.Sections 3–4 retain these operations under current FPF distinctions. A functional classification is not automatically an assignable system-role kind; a description is not an actual holder, and creation is not composition. The source’s physical-role ontology and broad function/Method/service equivalences are not adopted. Its accounts of learning and success are not independent evidence that this pattern improves either.
Levenchuk, R5, “The temptation of complexity”; R6, the creator, tool and provider discussion in “Common errors”; R8, Systems Engineering (2025 manuscript), use/construction/business-case discussion; R10, Systems Management (2023 manuscript), organization, system-of-interest and investor concernsThe managerial attention problem connects the creator’s design and provision to the products’ useful use. The corpus also calls a company the target system in investor discussions, while its management argument warns against replacing the product with its creator.Adapt as a deliberate attention rule. In organizational work, sections 4.1–4.3 retain the products as SoIs and give the creator its full engineering subject, capability grounds and finite acceptance. This selects a consistent practical norm from heterogeneous source usage; it is not a claim that organizations cannot be Systems, engineered or sold. The account supplies a way to examine decisions, not demonstrated psychological, commercial or learning success.
Levenchuk, Methodology for Engineers and Managers (R7; source manuscript Methodology2025_guide_with_assignments_22apr25.docx), the system-mantra passage in “Life cycle 2.0: from work stages to development methods” and “Creator graph”Creator graphs connect a builder’s period of use with work that creates or develops another system, and include both enterprises and simple tools.The recursive step in 4.3 preserves this connection; actual production, participation, performer and Work claims keep their respective FPF predicates.
Levenchuk, “Organizational-development mantras”, 13 March 2025; Checklists/canvases/“systems of equations”/mantras/plots for organizational development, slide-deck edition dated 15 May 2025 on its cover, slide 12The article explains that mantras retain a logical direction while inquiry is continuously refined; its short system-thinking mantra connects intended value, construction, ways of obtaining it, capable contributors and their cooperation. Slide 12 explains the equation analogy: answers constrain one another across several mantras and creator systems, and changes in the situation require revisiting their joint fit.Section 4.3.1 adapts this account into an FPF method for assembling and revising a jointly workable account across connected inquiries. The teaching order remains distinct from actual inquiry and Work. FPF uses the equation analogy for mutual constraints; it does not adopt the source’s restriction of mantra answers to types or claim a universal solver. The source’s fixed ordering of particular improvement priorities is not generalized here.
E.18 and E.18.NETBuild-the-builder reasoning must consider operation, production, identity inception, later change, feedback, and builder branches together, while independently identifying the TFS or nested-network members and relations behind any diagram.The conditional network branch in section 3, section 4.4 and the production continuation in 5.1.2 require exact cross-member occurrences and endpoint bindings when that network claim is needed. Shared identity, a creates label, or temporal adjacency does not admit a network or connect two members.
A.15.6, E.18, and E.18.NETA project team needs both the longer project dependency and a bounded local concern, with separate claims for project Work, network selection, case subject, closure, and later use.When closure is the receiving question, section 4.4 step 2 and section 5.1.2 name the exact subject or claim, only the references and direct claims needed now, a separately governed closure basis, and one downstream receiving use that remains outside the closed case. Project-level reasoning may continue to that later use without reopening the closed case.
Deutsch, Constructor Theory, arXiv:1210.7439v1 (2012), §1.1, pp. 1–4, read with current A.3.4, A.15.PROD, and E.18Possible production or change depends on substrate attributes and constructor conditions.The conditional actual-relations branch in section 3, forward trace and section 5.1.2 distinguish one continuing changed referent, production participation, identity inception, later use and system-side participation. Do not infer actual production or change from a requirement, Method, or Work alone. A not-yet-existing system is not transformed.

The combination used by this attention map is an FPF synthesis.

A.1.STM:12 - Rationale

The project-role and use account makes division of labour intelligible: it lets a participant explain why a local choice matters to people outside that task. The larger whole’s functioning at the operating time explains what contribution the system must make together with the other parts of that whole. Requirements derived from that account constrain plausible internal construction; construction constrains the Methods and capabilities needed to obtain it. Merely naming neighbours or desired effects leaves the reason for those requirements incomplete. These dependencies explain the mantra’s order. A complaint can lead back to the same grounds, while proactive examination can reveal an unanswered question before its consequences are felt. Criticism and experience explain the returns.

The same reasoning applies recursively to builders without making creation a composition relation or every builder a Work performer. Separating the project role from System identity preserves this organizing principle across different projects and before a holder exists. Separating local completion from receiving use lets a team finish bounded work without mistaking that completion for success of the whole undertaking.

A.1.STM:13 - Relations

  • Builds on: the Plain long/local boundary in the Architectural Reference; A.1 and A.1.SCR for system recognition; and A.15.6 for project SoI designation and local-subject recovery, actual project Work, and subject- or claim-centred case recovery.
  • Coordinates with:
    • B.5.PI for the general use of a suitable mantra to initiate inquiry before a difficulty is recognized.
    • C.22.2 when a signal or a question found through the mantra needs a reviewable problem-side account.
    • A.14 for relied-on part–whole relations.
    • C.30.STRAT for unresolved level wording.
    • C.32.P2S and the C.30 family for outside-use-to-architecture reasoning.
    • A.3.4 and the patterns for dynamics, interaction, causality, participation, assignment, Method, and Work claims in runtime change and system participation.
    • A.2 and A.2.1 for system-role-kind interpretation and assignment.
    • A.3.1, A.12, the A.15 family, A.15.PROD, A.15.5, and A.21 for Method, Work, production, identity, readiness, and gates.
    • E.18 and E.18.NET for TFS and project-level network selection.
    • A.15.6 for the minimal case recovery and closure boundary.
    • A.10 and B.3 for evidence and assurance.
    • A.1.CSD when the missing answer is which other Systems may undergo relevant changes.
    • C.28 only for actual causal-use claims.
  • Logical unfolding and continuation: A.22.CGUS supplies the account of alternatives and conditions when the reasoning structure’s continuations matter, and qualification for a formal CGUS or its demonstrative slice. The reminder, developed explanation, described structure and actual Work remain distinct. Ordinary use requires no new F.17 row, durable card or registration.
  • Does not replace: any direct pattern named above. A.1.STM connects their results to a shared systemic project account and returns each result or stop to the attention map; it defines no additional world-side predicate.

A.1.STM:End

A.2 - System-Role Kinds and Assignments

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

A.2:0 - Use This When

Plain name. Work-facing system classification and assignment.

Use this pattern when one admitted U.System can contribute to different work or functioning without becoming a different system, and the current claim must say either:

  • which work-facing kind the system counts under now; or
  • which system-role assignment actually obtains.

A system here is an individual independently recognized as a U.System under A.1. It can be a person, team, organization, deployed service system, organism, or non-human technical object. The SystemRole head in a name such as ReviewerSystemRole says that candidates are systems.

Typical moments:

  • the same pump counts as a cooling circulator in plant operation and as a test article in qualification work;
  • a project must decide whether Alice counts as a reviewer in one review slice;
  • a relied-on claim says that a system holds a named system role but leaves the assignment occurrence unclear;
  • ordinary wording says that a publication, method, capability, or relation participant “plays a role”, although the direct relation is still hidden;
  • a proposed “part of a role” may instead be another kind, a relation among kinds, an assignment-state predicate, a capability condition, a responsibility or commitment relation, or a method or Work structure.

Primary EntityOfConcern. One local U.Kind whose candidates are U.System individuals and whose operative membership condition distinguishes a stable, assignable, work-facing contribution. C.3 recovers the kind through that candidate domain and condition, a useful member/non-member boundary, and a continuity rule. A practice or source reference may locate the definition or prompt comparison; it does not identify the kind. Such a kind is called a system-role kind. Assignment is a neighboring direct relation, not part of the kind.

Working reader. A practitioner who needs to preserve system identity while making a classification or assignment inspectable.

First useful move. Start with the ordinary conclusion: “Alice counts as a reviewer for this submission” or “PumpUnit-3 is assigned as cooling circulator for this operating episode.” For classification, name the local system-role kind and evaluate the candidate with one KindSignature under C.3.2. Add a U.SystemRoleAssignment occurrence only when holding or assignment identity is claimed.

What goes wrong if missed. One label absorbs kind identity, classification, holder, assignment, capability, responsibility, and Work. Or every contribution is forced into a system role even when the real claim concerns evidence use, a relation participant, a declaration slot, or ordinary wording. In both cases readers cannot tell what exists, what merely describes it, and what actually happened.

What this buys. Systems retain their identities while work-facing classifications and assignments change. Membership is testable from the system features named by the membership rule rather than labels or circular hierarchy edges. Practices and sources may reuse one kind or define different kinds; comparing their distinctions decides which. Ordinary contribution wording can stay readable without manufacturing an ontology.

Not this pattern when.

  • Use A.2.1 when the current object is a U.SystemRoleAssignment species or occurrence and its participant, predicate, or identity law matters.
  • Use A.2.2 for capability and A.2.5 for assignment state.
  • Use A.2.7 for substitution, incompatibility, bundle, qualification, or another admitted relation among system-role kinds.
  • Use A.15 and its neighbors for method admission, planned Work, performed Work, and Work attribution.
  • Use E.24.UK when a local system-role kind is proposed as a durable public FPF U-kind.
  • Use E.10.ROLE when the source word role is ambiguous. If the recovered meaning is relation participation, a declaration place, an interface place, or a representation position, continue with A.6.RSIR.
  • When an episteme rather than a system is current, recover its direct use, evidence, publication, external-rule, currentness, or reliance relation through the relevant subject pattern.

A.2:1 - Problem Frame

One system can contribute in several ways while remaining the same system. PumpUnit-3 remains the same pump when it counts under CoolingCirculatorSystemRole for plant operation and under TestArticleSystemRole for qualification. A person remains the same person while counting under author and verifier kinds in different slices and holding different assignments.

These are local typed distinctions, not durable universal kinds. Each system-role kind has U.System candidates and a condition that distinguishes the stable, assignable contribution in question. C.3 also requires a useful member/non-member boundary and a continuity rule. Practice or source provenance helps readers find and compare the definition but decides neither sameness nor difference.

A KindSignature edition states how candidate features are evaluated. A C.3.2 judgment then answers whether one System counts under that kind in one slice. A separate assignment occurrence says that a System is assigned under its declared U.SystemRoleAssignment species.

Ordinary language also uses role to mean contribution or position. A design method can use a standard publication as a source for a constraint; a report can participate in an evidence relation; and a value can fill a relation slot. Those useful claims make neither the episteme nor the slot filler a system-role kind or assignment participant. The current relation must be recovered before the wording carries an FPF technical claim.

A.2:2 - Problem

Without this pattern:

  1. one system’s changing contributions are modeled as changes of system identity;
  2. a familiar label or taxonomy row is treated as a kind and as proof of membership;
  3. kind identity and the membership criterion are treated as the same thing;
  4. an assignment is used as a family-wide membership rule, or classification is used to manufacture an assignment;
  5. the holder, kind, assignment interval, capability, responsibility, and Work are compressed into one record;
  6. matching labels across local practices, sources, or editions are treated as identity or permission for reuse;
  7. proposed subkind edges or extension rows create their own membership evidence;
  8. ordinary role wording turns epistemes, slots, positions, or interfaces into system-held roles.

A.2:3 - Forces

ForceTension
Stable system identity vs changing contributionThe candidate remains one system while classifications, assignments, participation, and Work change.
Local typed use vs public ontology growthA project needs reusable work-facing kinds without admitting U.Role or another universal root.
Kind identity vs membershipCandidate domain, operative membership distinction, boundary probes, and continuity recover the kind; a current criterion application decides whether one system counts under it in a slice.
Classification vs assignmentA judgment classifies a system. An assignment is a direct relation occurrence and can exist or end independently.
Readable wording vs exact technical claims“Alice is reviewer” is useful; a receiving decision may still need the exact kind, judgment, assignment, or Work attribution.
Useful factorization vs false role mereologyCapability, responsibility, commitment, state, and Work remain separately governed rather than becoming parts of a role.

A.2:4 - Solution

Use a local U.Kind when U.System candidates need one stable, assignable, work-facing membership distinction. Recover the kind through the candidate domain, operative condition, useful member/non-member boundary, and continuity rule. Keep practice or source provenance as a locator and comparison cue. Give a live technical name the SystemRole head, such as ReviewerSystemRole or CoolingCirculatorSystemRole. Do not introduce U.SystemRole; the concrete value is already a local U.Kind under C.3.

Then keep four moves separate:

  1. identify the local system-role kind;
  2. declare or select the KindSignature edition used for membership;
  3. evaluate one system, kind, signature edition, and slice under C.3.2;
  4. add a directly declared U.SystemRoleAssignment species and occurrence only when an assignment actually obtains.

Capability, assignment state, method admission, performed Work, responsibility, commitment, permission, authority, evidence, reliance, and publication remain direct neighboring claims.

A.2:4.1 - Recognize a System-Role Kind

A local kind is a system-role kind only when all of these conditions hold:

  1. its candidate ValueKind is U.System;
  2. its operative membership condition states the stable, assignable, work-facing contribution and uses directly governed candidate features;
  3. at least one intended member and one relevant non-member or boundary case make the distinction testable;
  4. its continuity rule says which changes preserve that distinction and which require another kind; and
  5. its KindSignature does not treat a label, taxonomy row, description, assignment record, classification judgment, extension row, or proposed U.SubkindOf edge as the feature by form.

The kind asks what continuing distinction classifies candidate systems. A particular C.3.2 judgment asks whether one system satisfies the current signature now. Practice or source provenance shows where to inspect the definition; it neither creates nor splits the kind. CoolingPumpKind is not thereby a system-role kind. Its identity can be a physical or functional pump distinction rather than an assignable work-facing contribution. ShortAssignmentKind, if declared to classify assignment occurrences by duration, is also not a system-role kind because its candidates are assignments rather than systems.

A.2:4.2 - Evaluate Membership without a Circular Shortcut

Each membership clause names the candidate feature’s subject pattern, predicate or governed feature, applicability, dependencies, and slice. The classification has four explicit inputs:

J(candidateSystem, systemRoleKind, kindSignatureEdition, contextSlice)
  -> true | false | unknown

An assignment may be one feature only when the local KindSignature explicitly uses that independently obtaining assignment predicate. There is no family-wide rule that assignment means membership. The judgment being computed, a broader-kind judgment, an extension row, or the proposed U.SubkindOf occurrence cannot be a premise of the same judgment.

For an admissible candidate and slice, a known failed criterion gives false; missing support for a required feature or an unavailable dependency gives unknown. Evidence supports the claim that a governed candidate feature holds; the feature and membership criterion determine what is being classified.

Every U.SubkindOf proposal evaluates the aligned narrower and broader signatures independently for the same candidate and slice. Admit the order only when the C.3.1 monotonicity condition holds. The edge records an already established implication; it never produces either classification judgment.

A.2:4.3 - Keep Kind Identity, Declaration, and Extension Separate

The system-role kind is not its KindSignature, taxonomy episteme, reference scheme, classification judgment, or KindExtension. Same-kind continuity across declaration editions requires the C.3.1 comparison of candidate domain, operative membership distinction, member/non-member boundary, and continuity rule. A compatible criterion or scheme edition can preserve the kind while later judgments cite the edition actually used. A changed source or practice triggers that comparison but does not decide it.

An old role taxonomy or scheme can help recover the candidate domain, membership distinction, boundary probes, continuity rule, or provenance of the current definition. Its label or identifier does not decide sameness.

A selected BoundedModelUseStructure can qualify one receiving interpretation when that independently established organization matters; it is designated in the receiving assertion or use and is stored neither on the kind nor as an optional participant of a generic assignment or kind relation. A structure-dependent relation species instead declares the structure as a required participant, uses the stronger predicate, and states the resulting occurrence-identity law.

Use A.1.1 before citing that structure. Select BoundedModelUseStructure only when exact model applicability, actual model use in assigned Work, fixed-content expression coherence, exact applied constraints, and one named selection-use frame jointly change the receiving decision. If the direct kind, relation, assertion, or Bridge already answers the question, stop there; neither a model-use label nor a wish for more background selects the structure.

A.2:4.4 - Admit Only Exact System-Role-Kind Domains

U.Kind is too broad as the assigned-kind participant domain of an assignment species. Each bounded system-role vocabulary declares one local domain whose candidates are local kinds satisfying the recognition conditions above. For example:

JournalReviewSystemRoleKindDomain : U.Kind
  definitionProvenance: JournalReview-2026 (comparison cue only)
  candidateValueKind: U.Kind
  criterion:
    the candidate kind has U.System candidates, a stable assignable
    work-facing membership condition, useful boundary probes, and
    a continuity rule recovered under C.3

A direct assignment species uses that local domain as the ValueKind of its declaration-local AssignedSystemRoleKindSlot. The slot therefore rejects CoolingPumpKind, ShortAssignmentKind, and arbitrary local kinds. This is local C.3 typed use, not admission of U.Kind as a durable public root.

A.2:4.5 - Assignment Boundary

A.2.1 defines the U.SystemRoleAssignment family. The family contains directly declared relation species rather than one permissive universal signature. Every species declares:

  • HolderSystemSlot : U.System;
  • a declaration-local AssignedSystemRoleKindSlot whose ValueKind is one exact local system-role-kind domain;
  • any additional real participants needed to distinguish that species; and
  • its own obtaining predicate, applicability, and occurrence-identity rule.

A simple species can declare only the holder and assigned-kind participant meanings. A stronger appointment, authorization, or work arrangement can declare another participant meaning when its actual value changes occurrence identity. The specialized occurrence itself remains a U.SystemRoleAssignment; do not keep a second generic occurrence beside it merely for projection.

An assignment occurrence begins when its predicate starts obtaining for the fixed participants, continues over the maximal uninterrupted predicate-true interval, and ends when a participant changes or the predicate ceases to obtain. A taxonomy episteme, reference scheme, KindSignature, assertion, or interval description can interpret or describe the claim without becoming another world-side participant.

Assignment does not prove classification unless the kind’s signature uses that independently obtaining relation as a feature. Classification does not create an assignment. Neither one proves capability, agency, responsibility, authority, commitment, permission, functioning, method enactment, or performed Work.

A.2:4.6 - Relations around the Kind and Assignment

Current claimSubject patternKept distinct
Local kind, declaration, classification, and extensionC.3, C.3.1, C.3.2system-role kind, KindSignature, four-input judgment, optional extension, and kind-continuity decision
System-role assignmentA.2.1, A.6.5, A.6.RELdirect species, exact participants, predicate, applicability, and uninterrupted occurrence identity
Assignment stateA.2.5exact assignment occurrence, SystemRoleAssignmentStatePredicate, SystemRoleAssignmentStateRelation occurrence, and its maximal truth interval; target evaluation window, assertion polarity, evidence, and reliance remain separate
CapabilityA.2.2holder, qualified ability claim, work conditions, attained bounds, currentness and fit predicate
Relations among system-role kindsA.2.7, C.3.1exact kind participants and substitution, incompatibility, bundle, or monotonic qualification relation
Description and namingF.4, F.5, F.18kind, SystemRoleKindDescription, names, and publication or access carrier
Method and WorkA.3, A.13, A.15.1, F.6Method and MethodDescription; actual performer recovered through A.13; independently admitted Work occurrence; assignment and F.6 attribution only when precise assignment-bound attribution is expressly consumed
Responsibility, commitment, permission, or authoritydirect domain pattern, A.2.8, A.2.8.PER, or missing-governoractual bearer, exact relation participants, predicate, and instituting or permission basis
Evidence, reliance, or publicationA.10, A.15.4, B.3, C.2.1, E.17, F.10episteme, evidenced claim, reliance, provenance, currentness, and publication relation

Select only the objects needed by the current claim. None of these values is a “part of the role”.

SystemRoleKindDescription is an F.4 description episteme whose EntityOfConcern is one system-role kind. An episteme about an assignment or a relation among kinds has that assignment or relation as its EntityOfConcern instead.

A.2:4.7 - Recover Contribution Wording before Formalizing It

The phrase “the role of X” often means that X contributes to a use. Use E.10.ROLE when its technical meaning remains unclear; section 4.9 permits ordinary wording when no stronger distinction is needed. If X is an admitted system and the claim needs a work-facing classification, recover the local system-role kind and C.3.2 judgment; add an assignment only when holding is claimed. Otherwise keep X in its actual kind and name the direct relation or declaration place.

Ordinary wordingGoverned repair
RFC 9110 plays a normative role in this designIdentify the RFC’s claim-bearing content as the source episteme and state the external-rule, constraint, source-use, or publication relation selected by the design claim.
this dataset plays the benchmark roleState the measurement, benchmark, evidence, source-use, or currentness relation actually used. Identify any claim-bearing dataset account under C.2.1; keep its file or publication under the relevant direct pattern.
this parameter has the control roleRecover the Method or model parameter, or an A.6.5 participant slot, from the direct declaration.
this interface plays the integration roleRecover the selected module-interface, port, signature, or protocol relation under its governor.

Use these recognition probes to identify the relation in the current claim. If the predicate or participants remain unclear, recover them through A.6.P. Return missing-governor through A.6.RCD only when that recovered relation has no applicable governor; do not substitute a system-role kind.

A.2:4.8 - System-Role Vocabularies and Relations among Kinds

A system-role-vocabulary or taxonomy episteme may state local kind names, declarations, and selected relation claims under an effective reference scheme. Each live kind needs the C.3 distinction that lets readers recover it; each judgment cites its actual signature edition. An assignment claim separately requires an obtaining A.2.1 relation.

Use A.2.7 to state one selected SystemRoleKindRelationStructure over exact local system-role kinds and admitted relations among them. A receiving use can cite an assertion about substitution, incompatibility, bundle, qualification, or another residual relation alongside separately stated assignments, state, capability, and Work. Systems and assignments are not participants of the kind-relation structure.

Algebraic, graph, matrix, embedding, or neural representations are mathematical lenses over that selected structure when a project declares the lens use. They neither create the kinds nor make a relation obtain.

System-role kindRecognition caseBoundary
CoolingCirculatorSystemRoleA pump supplies a circulation contribution in plant operation.Capability, assignment, functioning, and performed Work remain separate.
TestArticleSystemRoleThe same pump is selected for qualification use.The classification or assignment does not change pump identity.
VerifierSystemRoleA person, team, organization, deployed service system, or non-human technical system supplies verification contribution under its local criterion.A verification report is an episteme, not the classified system.
TransformerSystemRoleA system is classified for a transformation-facing contribution.For performed Work, name the performer system.

A.2:4.9 - Reduced Use and Stronger Claims

Ordinary “Alice is reviewer” or “this component plays a control role” wording can remain Plain when no decision, attribution, admission, or reliance depends on another technical distinction. Do not materialize a kind, judgment, or assignment merely to decorate the sentence.

When a stronger claim appears, add only the needed object:

  • the local kind and judgment when classification matters;
  • the assignment occurrence when who holds what and when matters;
  • the direct state, capability, method, Work, responsibility, commitment, permission, evidence, reliance, or publication relation when that relation carries the claim;
  • the exact C.3.3 kind relation and, when local meanings differ, F.9 relation needed for cross-local use, without merging the kinds or creating assignments.

The earlier Plain sentence is not evidence for a stronger claim.

A.2:5 - Archetypal Grounding

A.2:5.1 - Reviewer Membership and a Non-Circular Subkind

The JournalReview practice records one local kind under C.3. The source label locates the definition; the kind itself is recovered through its system-candidate domain, substantive-review condition, boundary probes, and continuity rule:

ReviewerSystemRole : U.Kind
  definitionProvenance: JournalReview-2026 (comparison cue only)
  candidateValueKind: U.System
  operativeMembershipDistinction:
    can supply a substantive review judgment that meets the current
    JournalReview acceptance conditions
  intendedBoundary:
    a system that applies those conditions is a member; a report or a
    system that merely comments without applying them is not
  continuityRule:
    continue the kind only while that candidate range and distinction continue
KindSignature@ReviewerSystemRole/e3:
  EntityOfConcern: ReviewerSystemRole
  candidateValueKind: U.System
  membershipCriterion:
    the candidate system can perform substantive-review Work or produce
    the review-judgment result class under the declared conditions and bounds;
    the A.2.2 ability assertion has the support and currentness required here;
    the current JournalReview capability-fit predicate confirms the submission,
    review-phase, and judgment-quality conditions for this slice
  sliceApplicabilityConditions:
    the submission, review phase, and temporal selector
  effectiveReferenceScheme: JournalReview-Scheme-2026/e3
  assumptionsAndDependencies:
    the qualified holder-ability claim, its currentness condition and capability-fit predicate

The capability and fit predicate are governed under A.2.2. They are features used by the criterion, not substitutes for the kind or judgment. One application can therefore state:

J(Alice, ReviewerSystemRole, KindSignature@ReviewerSystemRole/e3, ReviewSlice-17) = true
J(Alice, ReviewerSystemRole, KindSignature@ReviewerSystemRole/e3, LaterSlice-18) = false

The later result follows only from a known failed currentness or fit condition. Ending an assignment alone changes neither judgment because this signature does not use assignment as a feature. If a dependency is unavailable, the result is unknown.

For RoboticsEngineerSystemRole U.SubkindOf EngineerSystemRole, evaluate the two aligned signatures independently for every admitted candidate and slice needed by the declared domain. Only after every defined true narrower judgment implies a true broader judgment may C.3.1 admit the relation. The proposed edge proves neither judgment. An independently obtaining robotics assignment also proves neither judgment unless the relevant signature explicitly uses it as a non-circular feature.

A.2:5.2 - Pump in a Cooling Loop

CoolingCirculatorSystemRole names a local kind whose candidates are admitted systems. Its membership condition requires the governed circulation features needed for the plant-operation contribution; member/non-member probes and the continuity rule expose the boundary. PlantOperations-2026 locates the current definition but does not identify the kind. PumpUnit-3 is judged against that exact signature edition and slice; the judgment does not change pump identity.

When the plant also claims an assignment, it uses a directly declared species:

PlantCoolingSystemRoleAssignment : U.SystemRoleAssignment
  HolderSystemSlot: U.System
  AssignedSystemRoleKindSlot: PlantOperationsSystemRoleKindDomain
  predicate:
    the holder is selected for the assigned plant-operation contribution
    under the declared operating conditions

PlantCoolingAssignment@PumpUnit3:
  HolderSystemSlot: PumpUnit-3
  AssignedSystemRoleKindSlot: CoolingCirculatorSystemRole
  assignmentInterval: [2026-06-01, open]

The interval is assertion content about the known extent; the occurrence continues only while the species predicate obtains without interruption for the same participants. PlantOperationsSystemRoleVocabulary-2026, its reference scheme, and the relevant signature can be cited as interpretation evidence. They are not extra assignment participants.

A later description may close the open interval while referring to the same uninterrupted assignment occurrence. Changed claim content identifies another episteme under C.2.1; the stated interval neither makes the relation obtain nor becomes another participant.

The assignment proves neither circulation capability over every operating region nor performed circulation or maintenance Work. Those claims use A.2.2, A.15.1, and the applicable Method, transformation, measurement, and evidence relations.

A.2:5.3 - A Standard Used in Design Work

An engineering team uses RFC 9110 while designing an HTTP service. Keep these claims separate:

  1. DesignTeam-2 independently counts under ProtocolDesignerSystemRole in the current slice when its signature criterion is satisfied.

  2. For this hypothetical assignment-bound case, suppose the practice has declared ProtocolDesignSystemRoleAssignment under U.SystemRoleAssignment according to A.2.1, and DesignAssignment-1 is one obtaining occurrence with holder DesignTeam-2 and assigned kind ProtocolDesignerSystemRole.

  3. The RFC’s claim-bearing content is the source episteme in the direct source-use or external-rule relation selected by the design claim; any publication relation remains separate.

  4. In this hypothetical case, recover DesignTeam-2 as the actual performer through A.13 with that same obtaining DesignAssignment-1, then let A.15.1 independently admit the dated design Work.

    Suppose this Work was performed under DesignAssignment-1; F.6 afterward establishes that relation to this same assignment. F.6 identifies neither assignment nor performer, and failed attribution would leave the Work intact. The Work may separately produce a MethodDescription or SystemDescription only through the applicable production claim.

A.2:5.4 - The Same Label in Two Local Practices

An editorial-review practice and a safety-assurance practice can each use ReviewerSystemRole. Compare their C.3 definitions before deciding whether one kind continues. In this case the safety-assurance condition admits a materially different contribution and member/non-member boundary, so two kinds are present. The practice names help locate those definitions; a shared label, vocabulary source, or reference-scheme spelling establishes neither sameness nor a Bridge.

Suppose a staffing dashboard proposes u-reviewer-display: show assignments from both practices in one Reviewer column. First recover the two local kinds and any F.17 cells needed by the displayed expressions; then establish only the C.3.3 kind relation and F.9 local-sense relation that the display actually consumes. State a separate C.2.1 bounded-use assertion with direction d-safety-to-editorial-display, rule r-preserve-reviewer-differences, and tolerance t-shared-label-only, plus polarity and effective scheme. The rule keeps the practices’ admission, independence, evidence, and completion fields separate and tolerates only the shared display label.

Current A.10 provenance and RelianceDisposition=pass can support that display use. They do not justify substitution between assignments or merge the two kinds. If a named assurance claim about that use is current, only its B.3 result can support that bounded assurance use; a non-positive disposition stops or narrows it.

A Bridge Card can package the Bridge, bounded-use assertion, evidence, and disposition, but it grants no assignment, eligibility, capability, use suitability, or performed-Work inference. A selected BoundedModelUseStructure is cited only in the receiving use whose interpretation it changes.

A.2:5.5 - A Relation Participant Slot Named role

An external notation may call one relation position role. Apply E.10.ROLE and A.6.RSIR to recover the participant meaning and declaration-local SlotKind. Its ValueKind is the participant kind. The external label creates neither a system-role kind nor an assignment. A System participates in the relation as declared; it holds a system-role assignment only through a separate occurrence of a declared assignment species.

A.2:6 - Bias Annotation

Bias riskFailureRepair
Lexical biasA familiar role label is treated as a kind, judgment, or assignment.Do not let the familiar word decide. Say which systems can count, which work-facing condition separates members from relevant non-members, and what preserves that distinction; keep ordinary wording Plain when no technical object is needed.
Document biasA taxonomy, description, card, or publication is treated as the kind or assignment.Keep the episteme and publication relation separate from the governed world-side values.
Episteme-as-agent driftA standard, report, dataset, or model is said to perform Work.Name the performer system and Work occurrence; keep the episteme in its evidence, reliance, external-rule, source-use, or publication relation.
Global-label biasMatching names are treated as matching kinds or sufficient permission for cross-local use.Keep local identities separate and establish only the C.3.3 kind relation, any F.9 local-sense relation, and the bounded-use claim that actually obtain.
Assignment-membership circularityAssignment proves classification or classification creates assignment.Evaluate direct features first; use assignment only when the signature explicitly cites an independently obtaining assignment predicate.
Slot-role driftA relation participant becomes a system-held role because a source labels the position role.Recover the exact participant meaning, SlotKind, and ValueKind under A.6.RSIR.
Capability-role driftAssignment or kind membership is treated as proof of ability.Use A.2.2 and a separate capability-fit predicate.
Method-role driftA system-role kind is treated as the Method or MethodDescription used for Work.Keep Method, MethodDescription, admission condition, assignment, and Work occurrence under A.3 and A.15.
Responsibility-role driftA system-role kind or assignment is treated as the responsibility result.Cite the admitted responsibility predicate and actual bearer, or return missing-governor.
Role mereologyState, capability, responsibility, or Work is modeled as a part of a role.Recover another kind, relation among kinds, or the direct neighboring object and relation.

A.2:7 - Working Guidance

  1. Identify the candidate and confirm its independent A.1 admission as U.System.
  2. Recover the local kind by saying which systems can count, which work-facing condition separates members from relevant non-members, and what changes preserve that distinction. Record practice or source provenance only when it helps find or compare the definition.
  3. Declare or select the exact KindSignature edition and its direct governed feature criteria.
  4. Evaluate the candidate, kind, signature edition, and slice as true, false, or unknown.
  5. Add an assignment only when an occurrence of a declared assignment species actually obtains.
  6. State each claim about state, capability, Method, Work, responsibility, commitment, permission, authority, evidence, or reliance through the pattern that defines or constrains it.
  7. Evaluate every subkind proposal from independently obtained aligned judgments; never use the proposed edge as a membership premise.
  8. For cross-local use, compare the C.3 definitions first. Reuse the same kind when its distinction continues; when two kinds are present, keep both kinds distinct and establish only the exact C.3.3 kind relation, any needed F.9 local-sense relation, and bounded-use claim actually consumed. In either branch, establish assignments independently; reusing the kind neither creates assignments nor licenses their substitution or merger.
  9. If a technical use of role still hides another object, use E.10.ROLE and continue with the recovered subject pattern. If the relation itself is unclear, use A.6.P; return missing-governor through A.6.RCD only for a recovered relation lacking an applicable governor.

A.2:8 - Conformance Checklist

IDCheck
CC-A2.1Every system-role kind is one local U.Kind; no U.Role or universal U.SystemRole is introduced.
CC-A2.2The U.System candidate domain, operative work-facing membership condition, intended member/non-member boundary, and continuity rule recover the kind; practice or source provenance only locates or prompts comparison of the definition.
CC-A2.3Kind identity, KindSignature, classification judgment, extension, vocabulary episteme, and reference scheme remain distinct.
CC-A2.4Each judgment names one system, system-role kind, signature edition, slice, and true/false/unknown result.
CC-A2.5Membership clauses use directly governed candidate features; labels, records, judgments, extensions, and proposed subkind edges are not features by form.
CC-A2.6An assignment is a membership feature only when the signature cites its independently obtaining predicate; no family-wide assignment-membership law exists.
CC-A2.7Every assignment occurrence belongs to one directly declared U.SystemRoleAssignment species with an exact local system-role-kind domain.
CC-A2.8Taxonomy, scheme, signature, assertion, and interval description are interpretation or claim content rather than generic assignment participants.
CC-A2.9Capability, state, Method, Work, responsibility, commitment, permission, authority, evidence, reliance, and publication remain separately governed.
CC-A2.10A U.SubkindOf claim follows independently evaluated aligned signatures and C.3.1 monotonicity.
CC-A2.11Same spelling across local practices, sources, or editions does not decide kind identity; continuity and actual relations are explicit.
CC-A2.12Relation-position or ordinary contribution wording creates no system-role kind or assignment by itself.
CC-A2.13A proposed decomposition is resolved through exact relations among kinds or neighboring subject patterns, not partOf over a system-role kind.
CC-A2.14Cross-local use compares the C.3 definitions first and reuses the same kind when its distinction continues; when two kinds are present, it keeps both kinds distinct, cites the exact C.3.3 kind relation and any needed F.9 local-sense relation, and states the bounded use, direction, preservation rule, tolerated loss, polarity, effective scheme, and current reliance needed by the receiver. Assignment occurrences remain independently governed in either branch; a Bridge Card is not a use licence.
CC-A2.15A selected model-use structure appears only in the receiving claim it changes; it neither classifies nor assigns a system and never enters a generic relation as an optional participant.

A.2:9 - Common Anti-Patterns

Anti-patternWhy it failsRepair
PumpAsCoolingCirculator as a new system subtypeOne contribution is mistaken for system identity.Keep the pump kind stable; use a local CoolingCirculatorSystemRole classification and a separate assignment when it obtains.
PumpUnit-3#CoolingCirculatorSystemRole:Plant-A@WindowThe compact token hides the kind declaration, assignment species and occurrence, and the kind of Plant A while suggesting a mandatory context participant.State the local kind and judgment; when assignment matters, name the A.2.1 occurrence and its declared species, and keep Plant A as the plant System or Work locus.
ReviewerSystemRole means “assigned reviewer”Kind membership and assignment occurrence are collapsed.Evaluate the signature; state the assignment independently.
Membership means “an assignment to this kind obtains”Broader classification would require a broader assignment and subkind order would create world-side facts.Use direct governed system features; assignment can be one explicitly declared feature.
One generic assignment signature accepts U.KindArbitrary kinds enter the assigned-kind slot and stronger appointments lose their participant law.Declare a direct species with an exact local system-role-kind domain.
Taxonomy and scheme are assignment participantsInterpretation editions become world-side identity changes.Keep them in declarations, assertions, or evidence about the predicate.
AssistantReviewerSystemRole partOf ReviewerSystemRoleNo constructive whole or part relation is established.Test a qualification, substitution, incompatibility, bundle, or another local kind and direct relation.
The PDF enforced the ruleAn episteme replaces the system and Work that performed enforcement.Name the performer and Work; state the PDF’s source-use, external-rule, evidence, or reliance relation separately.
Same label, therefore same kind or assignmentSpelling establishes neither kind continuity nor an obtaining assignment or Bridge.Compare the C.3 definitions first. Reuse the same kind when its distinction continues; when two kinds are present, establish only the exact C.3.3 and, when needed, F.9 result consumed by the use.

A.2:10 - Consequences

GainCost or tradeoff
Systems retain stable identity while contribution classifications and assignments change.Relied-on classification must identify the local kind, its current signature edition, and the C.3 distinction that makes the kind continuous; source or practice provenance is recorded when it helps locate the definition.
Membership can be checked without circular assignment or hierarchy premises.Direct candidate features and unavailable dependencies must be distinguished.
Assignment identity remains available through direct species and uninterrupted obtaining.A stronger appointment needs its real participants and predicate rather than a generic record.
Local vocabularies remain reusable without a universal role root.Cross-local sameness and use require explicit continuity, an obtaining C.3.3 kind relation, or an F.9 local-sense relation, as applicable.
Ordinary sentences remain readable.A stronger receiving claim must still expose the exact kind, judgment, assignment, or relation it consumes.
Episteme use, capability, responsibility, Method, and Work remain independently testable.Contribution wording must be resolved before it carries another technical inference.

A.2:11 - Rationale

System-role kinds solve a local classification problem. System-role assignments solve a relation-occurrence problem. The pump does not become another system because its contribution changes, and a kind does not become an assignment because one system currently counts under it.

The architecture therefore keeps these levels separate:

  1. the local system-role kind, its candidate domain, work-facing membership distinction, boundary probes, continuity rule, and useful definition provenance;
  2. the KindSignature and one C.3.2 judgment over a system and slice;
  3. any directly declared U.SystemRoleAssignment occurrence;
  4. direct neighboring relations for state, capability, Method, Work, responsibility, commitment, permission, authority, evidence, reliance, description, and publication.

Fields in a SystemRoleKindDescription belong to the description episteme. Proposed “parts” repeatedly resolve into other kinds, relation predicates, assignments, Method or Work structures, or parts of description epistemes. The useful structure for relations among system-role kinds is the relation structure governed by A.2.7. Resolve the other proposed “parts” through their subject patterns (§4.6), not role mereology.

Semantic locality needs no universal context participant. C.3’s candidate domain, operative membership distinction, boundary probes, and continuity rule recover the kind. A practice or source reference locates the definition and warns where comparison may be needed; it is not an identity participant. An assignment species declares only its real participants. A receiving assertion or use can cite a selected model-use structure when that structure actually changes interpretation.

A.2:12 - SoTA-Echoing

Practice lineSource and statusFPF mutationPractical consequence
Current foundational-ontology work separates role-like classification, relation participation, aspects, and situations instead of treating them as one category.Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint; current comparator, not an imported hierarchy.Use local C.3 kinds for work-facing classification, direct relation species for assignments, A.6.5 for participant slots, and separate state and episteme-use relations.Different classifications and assignments do not create system subtypes or role parts.
DOLCE separates endurants, perdurants, qualities, abstracts, dependence, and constitution but does not itself settle FPF system-role-kind or assignment identity.DOLCE 2022 axiomatization; bounded comparator.Preserve system, kind, relation occurrence, Work, quality, and episteme distinctions under their FPF governors.A borrowed category label cannot replace the local identity and predicate law.
DDD makes model applicability local and Context Mapping a method applied to actual model-use boundaries.Evans, Domain-Driven Design Reference (2015) and current context-mapping practice.Use a selected BoundedModelUseStructure only in the receiving claim it changes; keep the Method and performed Work separate.A plant assignment needs its local kind and species, not a universal context participant.
FPF relation and episteme discipline separates description and publication from evidence, reliance, source use, and the systems performing Work.Current C.2.1, A.6.REL, A.10, A.15.4, and E.17 line.Require an admitted system for system-role classification and keep each episteme in the relation that makes its use relevant.A team can use a standard as a constraint source without making the standard a performer or role holder.

A modeling notation does not decide the identity of a system-role kind, classification judgment, assignment occurrence, participant slot, responsibility relation, or Work.

A.2:13 - Relations

Builds on:

  • A.1 for system admission.
  • A.1.1 for selecting a BoundedModelUseStructure only when its complete decision-relevant relation organization, applied constraints, and named selection-use frame are current.
  • C.3, C.3.1, and C.3.2 for local kind identity, declaration, classification, extension, subkind, and continuity.
  • A.6.0, A.6.5, and A.6.REL for assignment declarations and occurrences.
  • C.2.1 for interpretation and assertion epistemes.

Governs with:

  • A.2.1 for system-role assignments.
  • A.2.2 for capability.
  • A.2.5 for assignment state.
  • A.2.7 for relations among system-role kinds.
  • A.15 and F.6 for Method-Work alignment and attribution.
  • F.4, F.5, and F.18 for description and naming.

Crosses locality through: C.3.3 for exact local kinds, F.9 for relations between exact F.17 cells, and A.6.9 for ambiguous sameness wording across local boundaries, followed by a bounded-use assertion and current reliance when the receiving action needs them. A matching name, Bridge, card, or selected model-use structure creates neither identity nor assignment.

Keeps separate from: responsibility, commitment, permission, authority, state, capability, Method, Work, evidence, reliance, publication, external-rule, and currentness relations. Apply E.10.ROLE to ambiguous wording and A.6.RSIR only when relation participation or its declaration must be recovered.

A.2:End

A.2.1 - U.SystemRoleAssignment - Contextual System-Role Assignment

Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative

A.2.1:0 - Use This When

Plain name. Assignment to a system role.

Use this pattern when another claim must rely on one obtaining assignment of an admitted U.System under one local system-role kind.

Typical moments:

  • a MethodDescription names InspectorSystemRole, but no current assignment occurrence has been established;
  • dated Work must be attributed through performedUnderAssignment(W, RA) and the exact assignment RA is still missing;
  • the same system receives the same system-role kind during two separated episodes;
  • two overlapping commissions or positions distinguish two assignments with the same holder and system-role kind;
  • an appointment, installation locus, or work commission may be a real additional participant of one domain assignment species;
  • a roster, configuration row, observation, decision, or evidence item supports an assignment claim without becoming an assignment participant.

Primary EntityOfConcern. One assignment occurrence whose relation species is declared directly under U.SystemRoleAssignment. Every species declares a holder participant with U.System as its domain, an assigned-kind participant drawn from one exact local system-role-kind domain, its own predicate and applicability, any real additional participant meanings, and its occurrence-identity rule. The occurrence supplies the actual participant values, including its holder System.

Working reader. A practitioner who must identify an assignment and any needed Work attribution while keeping their neighboring claims separate.

First useful move. Write the ordinary claim first: “Robot-7 is assigned as inspector for Shift-17.” Then identify the declared assignment species, the participant meanings and predicate it declares, and the participant values that satisfy that predicate in this case. Expose an occurrence reference only when another claim must distinguish or cite this episode.

What goes wrong if missed. A kind name is mistaken for an assignment, a permissive generic signature accepts arbitrary kinds, two real commissions collapse into one record, or a taxonomy and scheme become world-side participants. Work can then be attributed to the wrong occurrence while capability, authorization, and evidence hide as assignment fields.

What this buys. Simple assignments remain simple, stronger assignments retain their real participants, and every occurrence exposes its actual holder through the species-declared holder slot used by F.6. Repeated episodes are distinguishable without manufacturing a second generic assignment beside a stronger one.

Not this pattern when.

  • Use A.2 and C.3.2 for the system-role kind and one classification judgment.
  • Use A.2.2 for capability, A.2.5 for assignment state, and A.2.7 for relations among system-role kinds.
  • Use A.3, A.15, and A.15.1 for Method, MethodDescription, Work, and enactment.
  • Use F.6 for performed-Work attribution through an already identified assignment.
  • Use the direct responsibility, commitment, permission, authority, access, decision, evidence, reliance, provenance, publication, external-rule, or currentness pattern when that relation is current.
  • Use E.10.ROLE when the source word role has not yet been resolved; use A.6.RSIR when it means relation participation or a declaration place.

A.2.1:1 - Problem Frame

InspectorSystemRole can classify Robot-7 for one maintenance slice without any assignment occurrence. Conversely, an assignment can obtain while no Work occurs, and a local KindSignature can use or ignore that assignment when classifying the holder.

U.SystemRoleAssignment is the common relation family. It has no permissive root RelationSignature. Concrete domain species declare the participant law that their occurrences satisfy. A simple inspection assignment may need only the holder and assigned kind. A project-review appointment may also depend on one exact commission. The stronger occurrence itself is the assignment; it does not sit beside a weaker generic assignment with the same projection.

The holder can be any independently admitted U.System, including a person, team, organization, deployed service system, organism, or non-human technical object. Assignment establishes neither capability, responsibility, commitment, permission, authority, access, gate passage, functioning, Method enactment, nor performed Work.

Taxonomy epistemes, reference schemes, KindSignatures, assertions, and interval descriptions can interpret or describe the assignment claim. They are not generic world-side assignment participants. A selected BoundedModelUseStructure belongs in the receiving assertion or use unless one separately admitted relation species makes that structure a required identity-bearing participant.

A.2.1:2 - Problem

Without this pattern:

  1. a system-role kind or familiar job label is used as if it identified an assignment episode;
  2. one broad U.Kind slot admits physical, functional, assignment-occurrence, and arbitrary local kinds;
  3. a root signature hides different participant laws behind optional fields;
  4. a strong appointment is represented as one generic assignment plus another unrelated occurrence;
  5. assignments with the same holder and kind but different commissions or separated episodes collapse;
  6. taxonomy, scheme, context, interval, decision, and evidence become generic participants;
  7. assignment is treated as classification, capability, authorization, responsibility, or Work;
  8. a storage key replaces the predicate and uninterrupted occurrence identity.

A.2.1:3 - Forces

ForceTension
Common attribution projection vs domain-specific assignment identityF.6 needs the holder of every assignment, while domains can require different real participants.
Simple cases vs stronger appointmentsA two-participant assignment should stay light; a real commission or position must not be hidden or downgraded.
Readable assertion vs explicit occurrenceA sentence can state an assignment; attribution or state claims may also need a stable occurrence reference.
Stable participants vs repeated episodesIdentical participant values can recur after an interruption; time describes and distinguishes episodes without becoming a participant.
Interpretation vs world-side identityTaxonomies, schemes, signatures, and evidence matter to claims but do not automatically participate in the assignment.
Assignment vs neighboring factsClassification, capability, permission, responsibility, access, Method, and Work can vary independently.

A.2.1:4 - Solution

Declare each assignment relation species directly under U.SystemRoleAssignment. Do not give the family one universal participant signature. Every admitted species declares:

  • HolderSystemSlot : U.System;
  • one declaration-local AssignedSystemRoleKindSlot whose ValueKind is the exact local system-role-kind domain used by that species;
  • its direct assignment predicate and applicability;
  • every additional actual participant that changes the predicate or occurrence identity; and
  • its occurrence-identity rule.

The HolderSystemSlot and AssignedSystemRoleKindSlot names are declaration-local SlotKinds. Their spelling does not create global slots. Their complete A.6.5 SlotSpecs state ValueKind, refMode, participant meaning, multiplicity, and any constraints.

A.2.1:4.1 - Simple Direct Species

A simple species has only the two common participants:

JournalReviewAssignmentRelation <: U.SystemRoleAssignment

RelationSignature:
  HolderSystemSlot: U.System, U.EntityRef
  AssignedSystemRoleKindSlot: JournalReviewSystemRoleKindDomain, ByValue

predicate:
  the admitted holder is selected to supply the contribution denoted by
  the assigned system-role kind under JournalReview assignment conditions

applicability:
  JournalReview-2026 assignment episodes

JournalReviewSystemRoleKindDomain is the exact local C.3 domain defined by A.2. CoolingPumpKind, ShortAssignmentKind, and arbitrary local kinds cannot fill this species’ assigned-kind slot merely because each is a U.Kind.

A.2.1:4.2 - A Stronger Species Retains Its Real Participants

When an appointment, organizational position, installation locus, or work commission changes the predicate or occurrence identity, the domain species declares that participant. For example, conditional on a domain pattern already admitting ProjectReviewCommission and its appointment predicate:

ProjectReviewAppointmentAssignment <: U.SystemRoleAssignment

RelationSignature:
  HolderSystemSlot: U.System, U.EntityRef
  AssignedSystemRoleKindSlot: ProjectReviewSystemRoleKindDomain, ByValue
  ReviewCommissionSlot: ProjectReviewCommission, U.EntityRef

predicate:
  the holder is appointed under the identified commission to supply the
  contribution denoted by the assigned system-role kind

The commission is a participant because this admitted species makes it one. A decision episteme, roster row, or evidence item about the appointment is not thereby the commission or another participant.

If no current pattern admits the proposed participant kind or direct predicate, return A.6.RCD missing-governor for that specialized assignment. Do not hide the gap in an optional field.

A.2.1:4.3 - Occurrence Identity

An occurrence of a declared species begins when that species’ direct predicate starts obtaining for fixed participant values. It continues over the maximal uninterrupted predicate-true interval. It ends when a participant changes or the predicate ceases to obtain. A later resumption is another occurrence even when every participant value is the same.

A reference field ending in ...SystemRoleAssignmentRef uses U.RelationRef constrained to U.SystemRoleAssignment and resolves to the exact occurrence while keeping its declared species recoverable.

An assignment assertion or occurrence description can state assignmentInterval with a temporal reference, start, end or explicit open end, and continuity claim. A later assertion may close an open interval while referring to the same world-side occurrence when obtaining was uninterrupted. Changed claim content is separately identified under C.2.1.

When evidence is missing, whether the assignment obtained remains unknown; the evidence gap by itself establishes neither continuity nor a split. The occurrence ends when its predicate ceases to obtain; evidence of cessation supports a conclusion about when it ended.

Keep ordinary interval content here. When a positive temporal aspect itself becomes a relied-on object—its temporal reference, validity or currentness window, duration, cadence, rhythm, or interval structure—use C.27.TA for that aspect and keep the assignment occurrence separate. Use C.27 only for the different question of whether a temporal claim is adequate.

Taxonomy, scheme, KindSignature, assertion, interval description, and selected publication form can be cited when they matter to interpretation or evidence. Only the species’ declared participants and predicate determine world-side occurrence identity.

A.2.1:4.4 - One Strong Occurrence, Not a Generic Duplicate

If Alice has overlapping Commission-A and Commission-B, then ReviewAssignment-A and ReviewAssignment-B are two ProjectReviewAppointmentAssignment occurrences even when holder and ReviewerSystemRole match. Their commission participants and predicates distinguish them.

“Alice is the reviewer” is a readable existential projection over any qualifying occurrence. It is not a third assignment occurrence. Do not create a generic two-participant assignment beside either appointment simply to support that sentence or F.6.

Every admitted species supplies the common projection:

holderSystem(RA : U.SystemRoleAssignment) = RA.HolderSystemSlot
assignedSystemRoleKind(RA) = RA.AssignedSystemRoleKindSlot

The projection does not erase additional participants or assert that another occurrence exists.

A.2.1:4.5 - Assignment and Classification Are Independent

A C.3.2 judgment classifies one system under one local system-role kind for one signature edition and slice. An assignment occurrence relates participants under its species predicate. Either can be current without the other.

An assignment can be one membership feature only when the exact local KindSignature explicitly cites that independently obtaining predicate. RoboticsAssignment-1 alone establishes neither a RoboticsEngineerSystemRole nor an EngineerSystemRole membership judgment. A later U.SubkindOf result records monotonic implication among independently evaluated judgments; it creates no broader assignment.

A.2.1:4.6 - Demand-Driven Materialization

Ordinary use can stop at:

During Shift-17, Robot-7 is assigned as inspector under
MaintenanceInspectionAssignment.

Expose an occurrence identifier only when a receiver must distinguish episodes, cite the assignment as a participant, compare assertions, or preserve provenance. If a required participant or predicate is unresolved, state that missing basis and limit the claim. Use A.6.P to recover unclear relation meaning; return A.6.RCD missing-governor only when the recovered relation lacks an applicable governor. Never insert a dummy value or broaden the assigned-kind domain.

A.2.1:4.7 - Direct Neighboring Relations

Current questionDirect exitWhy it stays separate
Does the holder count under the system-role kind?A.2, C.3.2Classification is a four-input judgment, not assignment obtaining.
Can the holder do the Work?A.2.2 capability and fitAssignment does not create ability.
Does the assignment satisfy a state predicate?A.2.5State has its own predicate, relation occurrence, and truth interval.
Which Method admits or organizes the Work?A.3, A.15Method and MethodDescription do not assign a holder.
Was Work performed under this assignment?A.13, A.15.1, F.6Use A.13 to identify the actual performer and A.15.1 to admit the dated Work independently. Because this question explicitly asks under which assignment the Work was performed, F.6 then checks that separate relation against the assignment already used by A.13.
Does a decision or installation help constitute this species?the direct domain relation and species predicateIt matters only when the admitted species says so; an episteme is not a generic participant.
Is the holder responsible, committed, permitted, authorized, or able to access something?the admitted direct domain predicate, A.2.8, A.2.8.PER, or missing-governorEvaluate the claim about the holder using the direct predicate and its declared participants. The assignment can supply an applicability ground where specified.
What supports use of the assignment claim?evidence, reliance, provenance, source-use, or publication patternSupport concerns the assertion; it does not make the relation obtain.
Does a model-use structure change this receiving interpretation?A.1.1 plus the receiving assertion or useIt is not an optional participant of the assignment family.

Assignment-establishing world-side relations and epistemic support are not interchangeable. A constituting decision or installation occurrence affects a species only when its direct predicate says so. Evidence can support relying on the assertion without constituting the assignment.

A.2.1:4.8 - Performed-Work Attribution

F.6 retains one direct attribution with a comparison-only projection:

performedUnderAssignment(W : U.Work, RA : U.SystemRoleAssignment)
attributedPerformerSystem(W, RA) := RA.HolderSystemSlot

A.13 first identifies the actual performer S, and A.15.1 independently admits W : U.Work from its performance history, enacted Method, temporal extent, and containing-System relation.

F.6 is needed only for a precise assignment-bound attribution—when the current use must also say exactly under which assignment W was performed. It then establishes performedUnderAssignment(W, RA) against the same assignment already used by A.13 and requires S = attributedPerformerSystem(W, RA) = RA.HolderSystemSlot.

The projection exposes the assignment holder only for comparison with S; it identifies neither assignment nor performer. A missing or failed F.6 check alone leaves independently admitted Work intact; recheck an admission premise only when the same finding questions it.

SystemRoleAssignmentSlot in F.6 accepts any admitted assignment species because its ValueKind is the family U.SystemRoleAssignment. It is not a union of a generic relation and stronger non-assignment values. ReviewWork-A can be attributed to ReviewAssignment-A, and ReviewWork-B to ReviewAssignment-B, without creating generic duplicates.

Assignment does not prove that Work occurred. Work and assignment have separate identity rules; whether performed Work ends an assignment depends on the species predicate. For source wording such as RoleEnactment, first use A.13 to identify the actual performer and A.15.1 to admit the dated Work independently. If the current use also needs to say exactly under which assignment the Work was performed, add that assignment and the separate F.6 performedUnderAssignment check. Do not create a duplicate run-time kind or occurrence.

A.2.1:4.9 - Source Context Shorthand

Holder#Role:Context@Window is source notation, not the assignment ontology. Apply E.10.ROLE to recover the system-role kind or another meaning. Recover the object denoted by Context and its direct relation separately. It can be an actual system or Work locus, a claim scope, or a selected BoundedModelUseStructure; these have different kinds and uses.

If one assignment species depends on a structure or locus, its direct pattern declares that participant and stronger identity law. Otherwise keep the recovered object in the receiving assertion or use; never invent a generic context participant.

A.2.1:5 - Archetypal Grounding

A.2.1:5.1 - Robot Assigned for One Inspection Shift

The maintenance domain declares a simple species. Its participant slots and one occurrence are shown below:

MaintenanceInspectionAssignment <: U.SystemRoleAssignment
  HolderSystemSlot: U.System, U.EntityRef
  AssignedSystemRoleKindSlot: MaintenanceSystemRoleKindDomain, ByValue

InspectionAssignment-17:
  HolderSystemSlot: Robot-7
  AssignedSystemRoleKindSlot: InspectorSystemRole
  assignmentInterval: [2026-07-13T09:00, 2026-07-13T17:00]

The two fields designate the species participants. The interval is assertion content about the occurrence extent. MaintenanceSystemRoleVocabulary-2026, its effective scheme, and the relevant KindSignature can be cited to interpret the claim without becoming participants. Sensor capability, assignment state, inspection Method, and any performed inspection Work remain separate.

A.2.1:5.2 - Repeated Assignment Episodes

Robot-7 is assigned again on the next day under the same species and kind. The predicate does not obtain continuously across the two shifts, so the second shift is another U.SystemRoleAssignment occurrence. Reusing one staffing-row identifier cannot collapse the episodes.

A.2.1:5.3 - Motor Assigned as Drive

For a current equipment assignment, declare the species and identify its occurrence: Motor-M1 is the holder and DriveMotorSystemRole is the assigned-kind value. PumpAssembly-A remains the actual assembly System and Work locus rather than a generic context participant. If installation in that exact assembly distinguishes assignment identity, the domain species must declare a real installation-locus participant and predicate, and the occurrence must supply its actual value.

The separate claim “Motor-M1 drives PumpAssembly-A during PumpRun-17” is not established by assignment. Until a domain predicate supplies its participants, applicability, and identity, return missing-governor for the motor-drive-functioning relation. Torque capability, installation Work, pumping Work, and the assignment remain usable independently.

A.2.1:5.4 - DDD Model-Use Structure Changes a Receiving Interpretation

Two software contexts each use ApproverSystemRole. ApprovalService-2 can hold an assignment that obtains in the fulfilment context; name both the occurrence and its declared species. A receiving interpretation use can cite both the assignment-occurrence reference and Orders-Fulfilment-ModelUseStructure when the selected structure changes that use.

The structure was independently recovered under A.1.1. It qualifies the receiving interpretation and is not a generic assignment participant. A future species that depends on it must declare the structure as a required participant and state the stronger predicate and identity law.

A.2.1:5.5 - Two Review Commissions

Alice is independently admitted as U.System. Commission-A and Commission-B satisfy the admitted ProjectReviewCommission kind. Two overlapping ProjectReviewAppointmentAssignment occurrences have the same holder and ReviewerSystemRole but different commission participants.

ReviewWork-A is attributed to ReviewAssignment-A; ReviewWork-B is attributed to ReviewAssignment-B. “Alice is the reviewer” can remain a recognition sentence, but it does not merge the appointments or identify which Work belongs to which occurrence.

A.2.1:5.6 - Reviewer and Review Report

A.13 first recovers ReviewService-4 as the actual performer through its obtaining review assignment, and A.15.1 independently admits ReviewWork-82. Because this example expressly distinguishes which assignment covered the review, F.6 afterward establishes that Work-assignment relation through the same assignment. F.6 identifies neither assignment nor performer. Failed attribution alone leaves independently admitted Work intact; recheck an admission premise only when the same finding questions it.

ReviewReport-82 is a separately identified U.Episteme. When the Work first constitutes that episteme and the inception claim matters, A.15.PROD recovers one local entity-inception claim from the exact Work, change, and identity bases. The report can later participate in an evidence relation.

A.2.1:6 - Bias Annotation

Bias riskFailureRepair
Record-first biasA roster row or identifier is treated as the assignment occurrence.State the species predicate and uninterrupted occurrence identity; keep the row as an assertion or publication.
Universal-signature biasOne broad root signature hides several participant laws.Admit direct species with exact local domains and real participants.
Generic-duplicate biasA stronger appointment is accompanied by a weaker assignment occurrence.Let the specialized occurrence itself satisfy U.SystemRoleAssignment and use its common holder projection.
Universal-context biasEvery assignment receives a context or optional model-use participant.Keep context-denoted objects in their direct relation; declare a required participant only in a dependent species.
Assignment-as-classification driftAssignment is used as proof of kind membership.Evaluate the C.3.2 judgment; use assignment only if the signature names its independently obtaining predicate.
Assignment-as-Work driftCurrent assignment is treated as completed Work.Use A.13 to identify the actual performer and A.15.1 to admit W : U.Work independently. Name RA and run the separate F.6 check only if the current use must also say exactly under which assignment W was performed.
Episteme-as-holder driftA standard, report, model, or dataset fills HolderSystemSlot.Keep the episteme in its evidence, reliance, external-rule, source-use, or publication relation.
Responsibility or authority driftThe kind or assignment is treated as the responsibility or authority result.Cite the direct admitted predicate and actual bearer, or return missing-governor.

A.2.1:7 - Working Guidance

  1. State the assignment claim in ordinary language.
  2. Select or admit the direct assignment species; do not start from a universal root signature.
  3. Confirm the holder and exact local system-role-kind domain.
  4. Declare every real additional participant and the species predicate; reject placeholder fields.
  5. Decide whether a receiver needs explicit occurrence identity. Stop at the readable assertion when it does not.
  6. Distinguish repeated episodes by uninterrupted predicate obtaining, not by storage identifiers.
  7. Keep classification, capability, state, Method, Work, responsibility, commitment, permission, authority, access, evidence, reliance, and publication under their direct patterns.
  8. Use reference fields ending in ...SystemRoleAssignmentRef only with U.RelationRef constrained to U.SystemRoleAssignment and an exact recovered occurrence.
  9. For source shorthand, recover each hidden value by kind and relation before relying on it.

A.2.1:8 - Conformance Checklist

IDCheck
CC-A2.1-1U.SystemRoleAssignment has no permissive root RelationSignature; every occurrence belongs to one directly declared species.
CC-A2.1-2Every species declares HolderSystemSlot : U.System and one declaration-local AssignedSystemRoleKindSlot with an exact local system-role-kind domain.
CC-A2.1-3Every additional participant changes the predicate or occurrence identity and has an admitted kind and complete SlotSpec.
CC-A2.1-4The direct predicate, applicability, and occurrence-identity rule are explicit.
CC-A2.1-5One occurrence spans the maximal uninterrupted predicate-true interval for fixed participant values; after a demonstrated gap, a later resumption is another occurrence.
CC-A2.1-6assignmentInterval describes known extent and is not a participant or proof of obtaining. Ordinary interval content stays local; a relied-on positive temporal aspect uses C.27.TA, while temporal-claim adequacy uses C.27.
CC-A2.1-7Taxonomy, scheme, signature, assertion, evidence, publication, and model-use structure are not generic assignment participants.
CC-A2.1-8A specialized occurrence is itself a U.SystemRoleAssignment; no weaker generic duplicate is created.
CC-A2.1-9Every species declares the common holder slot that F.6 may use to compare an assignment’s holder with an already recovered performer. The comparison erases no additional participants and discovers no performer.
CC-A2.1-10Classification and assignment remain independent; assignment is a criterion feature only when the signature explicitly says so.
CC-A2.1-11A.13 identifies the actual performer and A.15.1 independently admits the dated Work. F.6 checks the same assignment only if the current use must also say exactly under which assignment the Work was performed; a missing or failed check leaves the Work intact.
CC-A2.1-12A ...SystemRoleAssignmentRef field is typed by U.RelationRef constrained to U.SystemRoleAssignment, resolves to one exact occurrence, and keeps its declared species recoverable.
CC-A2.1-13Missing evidence leaves whether the assignment obtained unresolved or unknown. Actual predicate cessation or participant change ends the occurrence; evidence supports a conclusion about its boundary.
CC-A2.1-14Reduced use stops before explicit individuation when no receiver needs an assignment reference.

A.2.1:9 - Common Anti-Patterns

Anti-patternWhy it failsRepair
Alice is reviewer, used as assignment identityIt names neither species nor occurrence.Recover the direct species and the obtaining occurrence needed by the receiver.
One universal binary assignment relation over U.KindIt admits arbitrary kinds and hides stronger participant laws.Use one exact local assigned-kind domain in every direct species.
Generic assignment plus appointment occurrenceOne world-side episode receives two competing identities.Make the appointment species a subtype of U.SystemRoleAssignment; use its holder projection.
One assignment row reused for every shiftStorage identity collapses repeated occurrences.Distinguish maximal uninterrupted predicate-true intervals.
Assignment proves WorkHolding is confused with dated performance.Use A.13 to identify each actual performer and A.15.1 to admit the Work independently. Add F.6 only if the current use also needs the exact assignment under which that Work was performed; a missing or failed check leaves the Work intact.
Durable RoleEnactment objectIt duplicates Work and attribution.Use A.13 to identify the actual performer and A.15.1 to admit the dated Work independently. Add the exact assignment and F.6 only if the current use must also say under which assignment the Work was performed; do not mint a duplicate occurrence.
Report holds a system-role assignmentAn episteme is made a holder by usefulness.Use its direct evidence, result, source-use, or publication relation.
Optional ContextSlot everywhereUnrelated locality, scope, structure, and locus meanings collapse.Recover the denoted object and declare it only when a direct species depends on it.

A.2.1:10 - Consequences

GainCost or tradeoff
Simple assignments keep two participants.Each bounded vocabulary must define its exact system-role-kind domain.
Strong appointments preserve their real identity.A domain must admit every additional participant and predicate it relies on.
All species support F.6 through one holder projection.Receivers must preserve both the assignment occurrence and its declared species rather than replace them with a generic record.
Repeated episodes remain distinguishable.Reliance-bearing use must recover uninterrupted predicate history, not just a row key.
Interpretation and evidence remain separate from world-side participants.Assertions must cite their actual semantic and evidence basis when the receiver needs it.
Ordinary prose remains lightweight.Authors must decide when explicit occurrence identity is required.

A.2.1:11 - Rationale

The family is needed because system classification and assignment occurrence answer different questions. Direct species are needed because the participant law for a simple shift assignment differs from the law for an appointment tied to a real commission, position, or locus.

One root signature would either reject legitimate stronger assignments or hide them behind optional slots. A generic occurrence beside a stronger one would duplicate the world-side episode and make F.6 choose between competing identities. Subtyping the direct species under U.SystemRoleAssignment preserves one assignment identity and one common holder projection.

Predicate obtaining, assertion, explicit individuation, identifier assignment, evidence, and publication also answer different questions. Keeping them separate lets evidence be corrected without rewriting the occurrence and lets ordinary recognition text remain shorter than a full relation declaration.

A.2.1:12 - SoTA-Echoing

Practice lineSource and statusFPF mutationPractical consequence
Current foundational ontology distinguishes role-like classification, relation aspects, and explicit relation occurrences.Almeida, Guizzardi, Sales, and Fonseca, gUFO, 2026 preprint; current comparator, not imported hierarchy.Keep local system-role kinds, direct assignment species, SlotKinds, and performed Work distinct under FPF identity laws.The same system can receive several assignments without becoming several systems.
Relation modeling distinguishes a family from concrete relation signatures with different participant laws.Current A.6.0, A.6.5, and A.6.REL line.Let directly declared species carry the exact participant and predicate law while the family provides the common ValueKind used by receivers.A commission-sensitive appointment remains usable by F.6 without a duplicate generic relation.
DDD makes interpretation local to an actual model-use organization.Evans, Domain-Driven Design Reference (2015) and current context-mapping practice.Cite a selected BoundedModelUseStructure only in a receiving claim it changes, unless a separately admitted species requires it.Ordinary physical and organizational assignments gain no fabricated context participant.

A.2.1:13 - Relations

Builds on: A.2 for system-role kinds and their exact local domains; A.6.REL for relation obtaining and occurrence identity; A.6.5 for complete SlotSpecs; and C.2.1 for assertions and interpretation epistemes.

Coordinates with: A.2.2 for capability; A.2.5 for assignment state; A.2.7 for relations among system-role kinds; A.3 and A.15 for Method and Work; A.15.1 and F.6 for performed-Work attribution.

Uses when current:

  • A.1.1 for a selected model-use structure.
  • C.27.TA when a positive temporal aspect is itself relied on.
  • C.27 for temporal-claim adequacy.
  • C.3.3, F.9, and A.6.9 for cross-context use.
  • direct responsibility, commitment, permission, authority, access, decision, evidence, reliance, provenance, currentness, and publication patterns.

Does not replace: a local system-role kind, a separate System-classification judgment, assignment state, capability, Method, Work, responsibility, commitment, permission, authority, access, assignment decision, evidence, publication, or their descriptions.

A.2.1:End

A.2.2 - System Capability: Conditions, Measures and Fit

Status: Stable

Capability is a System’s ability to perform a work family or produce a result class under stated conditions and measured bounds.

Use this when planning, promising or admitting work requires a justified answer to “can this holder do what is needed here?” The holder may be a person, team, machine, deployed software System, organization or composite cell. Identify that System independently under A.1, then state its qualified ability. The claim needs no separate capability individual.

Primary EntityOfConcern. The holder System whose ability is being asserted. A capability statement that needs an identified account is an episteme under C.2.1; its subject is the holder, and its claims state what that holder can do. Actual ability, the assertion, its support, current qualification and fit to a receiving demand remain distinguishable.

Working reader. A practitioner deciding whether a holder can meet a Work, Method-step, service-promise or architecture need.

First useful move. Name the holder, work or result, conditions and attained bounds. Then compare the receiving demand with that qualified claim, using the support and currentness required for this use. An adequate existing claim and fit result may be reused without another record. When a whole-result claim hides a consequential difference in how the holder uses a Method, use :2.1 to expose that difference.

What goes wrong if missed. Assignment, a MethodDescription, one successful run or a promise is mistaken for measured ability. Conversely, an expired report is treated as if it physically removed the holder’s ability. Both errors conceal which fact needs attention.

What this buys. Planning can separate ability from its warrant and fit: change the demand without inventing a new capability, or reopen an actual ability claim when the holder’s configuration changes. Independently required authority, assignment state, Method-side conditions and assurance remain separate receiving checks.

Not this pattern when.

  • If the current claim is which admitted System is assigned to an exact local system-role kind, use A.2.1.
  • If the current claim is whether that assignment is in an enactable state, use A.2.5.
  • If the current claim is a local system-role kind, its classification, description, designation, exact assignment, relation structure, or bundle, use A.2, A.2.1, F.4, F.18, or A.2.7 for that object.
  • If the current claim is a way of doing, use A.3.1; if it is an episteme describing that way, use A.3.2.
  • If the current claim is dated performed work or planned work, use A.15, A.15.1, or A.15.2.
  • If the current claim is a promise to others, use the promise-content and commitment patterns.
  • If the current claim is evidence, source, status, assurance, publication, or description use of an episteme, use the direct episteme-use pattern. Do not make the episteme a capability holder.
  • If the current claim is one measured aspect with a declared scale, use U.Characteristic through C.16.P, A.19, and the applicable characteristic or Scale pattern.
  • If the current claim is a composite quality family such as availability, resilience, security, or maintainability, use C.25 Q-Bundle.
  • If the current claim is an architecture-characteristic starter head, project criteria row, architecture eval reading, or architecture-description concern, use C.32.HCS, C.32.ACS, C.32.ACE, or C.30 as applicable.

A.2.2:1 - Problem Frame

These ordinary sentences make different claims about welding:

  • “The welding robot is the welder on this line.”
  • “The welding robot can weld seam type W at 12 seams per minute.”
  • “The welding procedure says how to weld seam type W.”
  • “The robot welded batch B at 10:20.”
  • “The supplier promises 12 seams per minute.”

Only the second sentence asserts the robot’s ability. Its holder, work family, conditions and measure bounds must be recoverable before the claim can be compared with a demand. The assertion still needs support for the receiving use. The others may state a local system-role assignment, MethodDescription, performed Work, or promise content. When FPF collapses them, project reasoning becomes brittle:

  1. System-role assignment becomes fake ability. “Assigned as verifier” is treated as “able to verify”.
  2. Method description becomes fake ability. A recipe or algorithm is treated as sufficient evidence of the holder’s ability.
  3. Past work becomes fake ability. One successful work occurrence is treated as stable capacity.
  4. Promise content becomes fake ability. A service promise hides the real system envelope and measured bounds.
  5. Description becomes fake holder. A standard, report, model card, or dashboard is said to “have capability” because it is useful in a capability argument.
  6. Unbounded ability becomes unreviewable. “Can machine titanium” does not name conditions, measures, version, calibration, or currentness.

A.2.2:2 - Qualified Ability and Its Use Basis

The positive claim is that a named holder can perform the named work or produce the named result under the stated conditions and attained bounds. If its truth depends on time, include that time in the claim. A reference to the holder identifies its subject; the other values qualify the proposition rather than identify another individual.

Use these values when the receiving comparison needs them:

ValueContribution
capabilityHolderRefThe independently admitted U.System whose ability is claimed.
WorkFamilyOrResultClassRefWhat the holder can do or produce. A particular Method or independently admitted MethodDescription may constrain this claim when the use requires it.
CapabilityEnvelopeThe inputs, environment, resources, configuration, version, calibration state, staffing and other conditions under which the ability is claimed. Its set-valued work-condition basis is U.WorkScope under A.2.6.
CapabilityMeasureSetThe attained bounds claimed for the holder, with units, scales, tolerances and success predicates. Keep the demanded bounds on the other side of the fit comparison. A Characteristic, Q-Bundle slot or architecture criterion can supply a measure without becoming the ability.
Capability statementAn assertion of that proposition; use a C.2.1 episteme when the account itself needs identity. Recording it does not make it true.
Evidence and source-use relationsThe tests, prior work, simulations, standards or other sources that warrant the assertion or constrain its use under their direct governors.
Qualification policy and currentness assessmentThe rule for relying on that support now, and its dated assessment. A qualification window may expire while actual ability remains unchanged.
Capability-fit predicateThe receiving comparison of demanded work conditions and bounds with the qualified holder claim. This is distinct from the ability proposition and its support.

WorkScope describes work conditions, even when an episteme states them. That episteme’s ClaimScope concerns its claims; the two scopes do not become interchangeable. Quantitative bounds and qualification policy remain separate from WorkScope membership. A time condition belongs in WorkScope only when it changes which work slices are covered; an evidence-age rule belongs in qualification.

These distinctions permit ordinary capability use without U.Capability as an additional kind. A separate kind question arises only if a concrete receiving use needs another individual’s continuity or a useful stable classification beyond the holder and these claims; E.24.UK then requires that question’s identity and membership facts.

A.2.2:2.1 - Method-relative capability: the structure the holder can use

Use this more detailed comparison when a person, machine or composite can produce part of a result, yet it is unclear which operation, distinction or connection of the Method it can use. A correct explanation, a supplied decision and successful execution with help can support different claims. Keep the ordinary ability-and-fit answer in :3 when it already settles the receiving question.

Select the Method organization that can change the decision: its consequential operations, distinctions, conditions and joins. Include recognizing when to select the Method, adapting it or composing it with another Method only when the promised contribution requires that. Choose a grain at which a missing relation changes the next action. Separate success at individual operations from success at their coordination.

Usable Method structure is the aspect of which selected operations and relations a specified System can bring to bear in named work under stated conditions. As an A.17 relational characteristic it has the ordered bearers (holder System, Method), arity two. The selected structure and granularity, work family, success criteria, relevant time/configuration, ordinary tools, supplied help, execution budget and observation horizon qualify that comparison. A MethodDescription can supply the account or evidence; it does not replace the Method in this pair.

A Method-relative capability profile expresses the qualified ability claims at that grain. It can be ordinary prose: identify the supported contribution, the help that supplied another contribution, and the unresolved or contradicted claim. It is an account about the holder, not another capability individual. An unobserved operation remains unresolved rather than becoming zero ability. A successful trial grounds only the capability inference warranted by its conditions and evidence.

Compare profiles only on a compatible selection and conditions. If one covers another’s supported organization and adds a consequential relation, it has greater supported structural coverage. Different strengths can remain incomparable. A count or fraction needs a fixed structural unit, denominator and inference rule; separately acquired actions do not add up to an acquired join. Use A.17/A.18 and C.16 for a declared scale or measurement. The resulting coverage is distinct from task value, a universal mastery rank or a bit estimate.

Make assistance part of the claim. If a specialist selects the right variant and the holder executes it, the occurrence does not yet support the holder’s selection capability. Removing that specialist changes the tested conditions. Keep tools and references that the receiving work ordinarily provides. If the capable whole is an equipped System or ensemble, state the claim about that whole rather than distributing it to every participant.

Current usable structure says what the holder can do now. Acquired structure adds a history claim, requiring comparable before/after capability accounts; attribution to a particular intervention needs its own grounds. Obtainable through learning concerns a starting holder and a specified acquisition arrangement, including how later learning actions are chosen. Use E.23.CDI for that construction and E.23.CAE when access, expression or changed conditions remain plausible explanations of the observed difference. Those questions do not add an acquisition arrangement as a third bearer of the current characteristic.

A.2.2:3 - Positive Solution

  1. Identify the holder and demanded result. Recover the System and the work family or result class. Keep a desired development target distinct from what the holder can currently achieve.
  2. State the qualified ability. Give the conditions and attained bounds claimed for that holder. Include relevant actual time or configuration. A useful sentence is “RobotArm_A can weld seam family W under conditions C at the stated precision and rate.”
  3. Recover sufficient support. Reuse or obtain the evidence and source-use relations required by the receiving claim. Assess their currency under the applicable qualification policy. When sampled measurements support a bound, retain the uncertainty needed for the receiving decision; a point estimate close to its limit may leave the comparison unresolved. Missing support leaves reliance unresolved; it is not proof of inability.
  4. Compare with the receiving demand. Under A.2.6, test whether the declared WorkScope covers the intended JobSlice, whether the claimed attained bounds meet the required bounds, and whether qualification holds at the evaluation time. If a necessary condition or translation is missing, name it instead of returning a positive fit.
  5. Apply the remaining entry conditions only when required. Authority, assignment and assignment state, resources, interfaces, Method-side conditions and assurance retain their direct governors. Passing the capability comparison supplies only its part of the receiving decision.
  6. Return the bounded answer. State the supported ability and fit, the mismatch, or the unresolved premise. Stop when that answer suffices. A described check does not assert that Work occurred or that a proposed intervention achieved its target.

One possible statement-and-use record is shown below. It is a way to preserve the claims needed by this use, not a mandatory new entity or classification.

CapabilityStatementRecord:
  capabilityHolderRef: U.System
  canDo: WorkFamilyOrResultClass
  workConditionBasis: U.WorkScope
  attainedMeasureBounds:
  actualTimeOrConfiguration?:
  capabilityStatementRef?: C.2.1 episteme
  evidenceOrSourceUseRefs:
  qualificationPolicy:
  currentnessAssessmentRefs?:

CapabilityFitCheck:
  holderAbilityClaim: the qualified proposition above
  receivingJobSlice:
  requiredMeasureBounds:
  evaluationTime:
  scopeCoverage:
  measureComparison:
  qualificationResult:
  result: fit, mismatch, or named unresolved premise

The record separates what is claimed about the System from the grounds for believing it and from what another use demands. The same supported ability may fit one demand and fail another.

A.2.2:4 - Separation From Neighboring Values

Source wordingRecovered FPF values
“Engineer role can approve the design.”Treat bare role as an E.10.ROLE trigger. If it means classification, recover local kind EngineerSystemRole and a C.3.2 judgment for an admitted System. If assignment identity matters, name the assignment occurrence and its declared U.SystemRoleAssignment species. Do not infer permission, capability, action, responsibility, or approval Work from either claim; add a capability claim only for the measured and qualified ability of the holder System, and use the permission and performed-Work relations when those claims are made.
“The robot is assigned as welder.”Name an assignment occurrence with the robot as holder and its declared U.SystemRoleAssignment species, whose assigned-kind position has local domain WelderSystemRoleKindDomain; the occurrence supplies WelderSystemRole as the value admitted by that domain. Add a capability claim only if the claim also says that the robot can meet a welding envelope and measures.
“The solver has the scheduling algorithm.”First identify what the possession phrase claims: a deployed-software relation, a capability statement about the solver system, a reference to a U.Method, or a candidate claim-bearing episteme. Apply A.3.2 only to the last candidate; it is U.MethodDescription only when its exact EntityOfConcern is one admitted Method and at least one substantive claim says how that Method is done. The phrase alone establishes none of these.
“The report has evidence capability.”Recover the report’s evidence-use relation. A separate capability claim needs a system that can perform evidential work.
“The team did one successful run.”U.Work occurrence; a broader capability claim needs justified conditions, attained measures and current support.
“We promise five-day close.”Promise content and commitment; the provider’s qualified ability and its fit to the promised result need separate support.
“The architecture provides resilience capability.”Architecture-characteristic or Q-Bundle material under C.30, C.32.HCS, C.32.ACS, and C.25; add a capability claim only when it states a named holder System’s ability to produce or maintain a result class within declared conditions and bounds. Resilience characteristics may constrain a capability-fit condition; they are not capability by name.

A.2.2:5 - Work-Admission Use

A Method step or Work claim may require both an exact system-role assignment and capability conditions.

WorkAdmissionCheck:
  systemRoleAssignmentCurrent: A.2.1 direct species under U.SystemRoleAssignment
  systemRoleAssignmentStateAdmitsWork: A.2.5
  methodStepRequires: A.3.1 or A.3.2
  holderAbilityClaim: A.2.2 qualified claim about the assignment holder
  capabilityFitCondition: admission predicate over declared capability measures and any named characteristic, Q-Bundle, or architecture-characteristic inputs
  performedWorkRef?: A.15.1, only for a separately asserted dated Work occurrence

The checks are separate:

  • one U.SystemRoleAssignment species defines the holder and assigned-kind participant meanings, the local system-role-kind domain, and any other participant meaning that changes the assignment predicate or occurrence identity; an occurrence supplies the holder System and other values for the case, and neither species nor occurrence establishes capability or Work;

  • SystemRoleAssignmentStateRelation says whether that assignment satisfies the selected state predicate over the required window;

  • one exact U.Method supplies the method-side condition, while an independently admitted U.MethodDescription or work-admission episteme may state the capability threshold used by the check;

  • the ability claim states what the holder can achieve under the declared conditions and attained bounds;

  • the capability-fit condition compares that qualified claim with the current work conditions and required bounds;

  • after execution, A.13 first recovers the actual performer and A.15.1 independently admits the dated Work occurrence.

    F.6 performedUnderAssignment(W, RA) is added only when this capability account or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment, while actual enactsMethod(W, M) separately relates the Work to the exact Method.

Do not put the threshold into the local system-role-kind name.

A.2.2:6 - Worked Cases

A.2.2:6.1 - Manufacturing Cell

This constructed example states the robot’s ability separately from its assignment:

CapabilityStatement:
  holder: RobotArm_A
  canDo: Weld_MIG_v3 seam family
  envelope: steel grades S235-S355, ambient 18-30 C, argon mix 92-95 percent, torch T-MIG-07
  measures: bead width 6.0 mm plus or minus 0.2 mm, throughput up to 12 seams per minute, defect rate below 0.5 percent
  qualificationWindow: calibration valid through 2026-09-30
  qualificationPolicy: rely on the test and calibration support only within its declared validity
  actualCondition: the robot configuration and calibration state satisfy the claimed envelope
SupportAndUseBasis:
  evidenceOrSourceUse: latest welding test report and calibration source relation

WeldingShiftAssignment is a declared species under U.SystemRoleAssignment. Under A.2.1 its signature defines the holder and assigned-kind participant meanings and uses WelderSystemRoleKindDomain as the local assigned-kind domain; it adds another participant only if that participant changes the assignment predicate or occurrence identity. One occurrence has RobotArm_A as holder, WelderSystemRole as the assigned-kind value admitted by that domain, and an extent lasting while the predicate obtains without interruption for the same participants.

The assertion has exact claim content, EntityOfConcern, and effective ReferenceScheme; a ClaimScope, selected slice, interval, or qualification window is stated separately when it changes interpretation or validity. None of those values is another assignment participant. A separate Work or system-locus relation may place intended or performed welding at AssemblyLine_2026 when that relation obtains.

If a Method step requires an obtaining WeldingShiftAssignment whose local kind is WelderSystemRole and bead-width tolerance below 0.2 mm, the assignment and capability are both checked. The declared ±0.2 mm bound does not establish the stricter tolerance, so this capability statement alone cannot support admission of the step.

Shared boundary case — Robot-7 possesses an inspection algorithm. InspectionReleaseAssignment is a declared species under U.SystemRoleAssignment; under A.2.1 its signature defines the holder and assigned-kind participant meanings and uses InspectorSystemRoleKindDomain as the local assigned-kind domain. Occurrence InspectionAssignment-17 has Robot-7 as holder and InspectorSystemRole as the assigned-kind value admitted by that domain. This simple species declares no taxonomy, reference-scheme, generic-context, or interval participant. An assertion about the occurrence may cite MaintenanceRoles-2026, Maintenance-Scheme-A, and the candidate inspection interval as interpretation and description content.

Robot7-TurbineInspectionStatement-2026 is an assertion about Robot-7: that System can perform turbine-inspection Work within the stated sensor, calibration, input and measure bounds. Qualification governs current reliance on its support. A statement that Robot-7 “possesses inspection algorithm A” does not by itself identify that capability claim, Method TurbineInspection@Maintenance-2026, a deployed-software relation, or a MethodDescription episteme.

Dispatch the phrase by claim: use A.2.2 only for the bounded ability; A.3.1 for the Method; a deployed-software or possession relation when that is the claim; and A.3.2 for candidate episteme TurbineInspectionProcedure-v3 only after its EntityOfConcern resolves to that Method and one substantive claim says how it is done.

Assignment and capability still do not prove execution. If InspectionWork-17 occurs, A.13 first recovers Robot-7 as the actual performer through obtaining InspectionAssignment-17, and A.15.1 independently admits the Work.

Because this example expressly states assignment-bound attribution, F.6 afterward establishes performedUnderAssignment(InspectionWork-17, InspectionAssignment-17) through that same assignment; F.6 identifies neither assignment nor performer, and failed attribution leaves the Work intact. The Work occurrence separately stands in enactsMethod(InspectionWork-17, TurbineInspection@Maintenance-2026).

A.2.2:6.2 - Software Service as Deployed System

PlannerService_v4 is a deployed System. In this constructed example, its claimed ability is to return feasible job-shop schedules for 50–500 jobs and 5–40 machines in less than 20 ms in PlantScheduling_2026, with makespan at most 1.05 × L_ref. Makespan is the elapsed time from the common start to the last job completion; L_ref > 0 is the makespan of the declared feasible reference schedule for the same instance. With L_ref = 100 min, 104 min passes this quality bound and 106 min fails. The reference is a comparison baseline, not a proved optimum.

The deployed System is the holder; the algorithm paper and MethodDescription are descriptions. Version, dependencies and input range qualify the ability claim. Measurements can support that claim, and their age can limit current reliance without itself changing the System’s ability.

A.2.2:6.3 - Organization or Team

FinanceDept can close books for eight legal entities under IFRS with ERP v12, staffing at or above six qualified people, and close duration below five business days. That is a capability of the organizational system.

The monthly-close service promise is a promise-content claim. The actual close for March 2026 is performed Work. Staff assignments and their SystemRoleAssignmentStateRelation occurrences are neighboring claims. The capability statement keeps the department’s ability measurable; a management report asserting it is an episteme about the department.

A.2.2:6.4 - Episteme Anti-Case

“ISO 26262 has safety capability” is not an ability claim about a holder System. The standard is an episteme used as source, requirement, or assurance input. A safety engineering team or toolchain may have a capability to perform safety-case work using that standard within a declared envelope.

A.2.2:6.5 - A recovered rule and a usable transition

Consider a constructed rhythmic case with eight pulses and audible attacks at pulses 0, 3 and 6. One Method alternates left and right on audible attacks; another alternates on every pulse, including silent ones. Both yield L,R,L in the first cycle. In the next cycle, attack-wise alternation yields R,L,R, while pulse-wise alternation yields L,R,L again. The first cycle therefore cannot distinguish control of these two state-update rules.

Suppose a performer draws both traces correctly and performs the second rule while following a teacher, but reverts to attack-wise alternation without that demonstration. The comparison preserves the correct explanation as a recovery result. Its capability conclusion concerns execution with the demonstration; independent control of the silent-pulse transition remains unsupported. A pulse reference may remain if the receiving performance normally provides it.

If the receiving work still needs a way to obtain correct execution of the pulse-wise rule, use E.23.CDI to decide how to develop the holder’s ability, supply the missing contribution through another arrangement, or combine the two.

A digital controller can be compared on the same selected relation using its input/output traces, but that comparison supplies neither a human learning mechanism nor evidence that either holder acquired the rule through training.

A.2.2:7 - Reconsider the Claim, Its Support or Its Fit

Reopen the value whose governing conditions changed. A different holder changes the subject. Configuration, calibration, wear, staffing, training or environment may change actual ability; evidence and qualification affect warranted reliance; the receiving demand affects fit. Assignment state and authority can separately defeat Work admission while ability remains.

The following constructed cases keep those changes apart:

ChangeResult
A new test supports the same measured performance under the same conditions.Support changes; no changed ability is inferred.
A holder has supported throughput 10 units/min; demand rises from 8 to 12 under the same conditions.The earlier demand fits that bound and the later demand does not. The holder’s ability claim is unchanged.
Recalibration or configuration changes what precision the holder can attain while its old report remains.Actual ability may change; reassess the predicate and the report’s applicability. Unchanged paperwork does not fix the truth.
A fault makes the named ability predicate false at t1; repair restores it at t2.State loss and recovery for the same holder under those times and conditions. No capability-individual continuity decision is needed.
RobotArm_A is replaced by RobotArm_B.The assertion has a different subject; support for A does not automatically establish B’s ability.

A qualification window expiring may require new support or narrower reliance. An input outside the declared WorkScope defeats this fit basis. A changed Method can change the required bounds without changing the holder. A development intervention may be performed while its target remains unmet; a later successful comparison alone does not establish which intervention caused improvement. Use E.23.CDI and E.23.CAE for those development and attribution questions.

A.2.2:8 - Composite Capability

A composite system may have a capability that none of its parts has alone. Treat the composite as the holder.

CapabilityStatement:
  holder: Cell_3
  canDo: place 12 PCB per minute
  envelope: feeder, vision, head, controller, and operator conditions
  measures: placement tolerance, throughput, fault rate
  actualCondition: the claimed component configuration and calibration state
  qualificationPolicy: rely on the supporting assessment only within its declared validity
  dependencyNotes: feeder and vision subsystem conditions

The claim is about Cell_3. Justify its attained bounds under the stated component and coordination conditions; component claims alone do not establish the composite’s ability. A changed dependency can reopen that claim even while each component retains its own qualified ability.

A.2.2:9 - Checklist

CheckQuestion
CC-A2.2-01Is the holder an admitted U.System under A.1 for this claim?
CC-A2.2-02Does the capability claim name the work family or result class?
CC-A2.2-03Does the capability claim name the envelope: inputs, environment, configuration, resources, constraints, or conditions?
CC-A2.2-04Does the measure set bind measurable bounds to units, scales, thresholds, predicates, declared U.Characteristic values, Q-Bundle slots, or architecture-characteristic rows without making those inputs the capability?
CC-A2.2-05Are the claim’s actual time and conditions distinguished from its qualification policy, support window and dated currentness assessment?
CC-A2.2-06Are statements, evidence, source-use relations, certifications, reports, dashboards, and currentness assessments expressed as neighboring support records or relations, without treating the records as holders or their existence as proof of ability?
CC-A2.2-07Are the exact system-role assignment, SystemRoleAssignmentStateRelation, Method-side admission or fit condition, performed Work, and promise content kept separate?
CC-A2.2-08For Work admission, are the exact system-role assignment, capability claim, and capability-fit predicate all visible when all are current?
CC-A2.2-09For composite holders, is the capability stated at the whole whose ability is being claimed?
CC-A2.2-10When conditions change, is it clear which ability proposition, assertion, evidence relation, currentness assessment or fit predicate needs reconsideration?
CC-A2.2-11When wording says that a holder possesses an algorithm, did the use dispatch separately to capability, exact Method, deployed-software or possession relation, or candidate episteme, and apply A.3.2’s exact-Method EntityOfConcern plus substantive-claim threshold before admitting U.MethodDescription? For a dated Work claim, are the actual performer and Work independently established through A.13 and A.15.1, with F.6 added only when precise assignment-bound attribution is needed and Method enactment kept separate?
CC-A2.2-12When a Method-relative profile is used, are the selected Method relations, holder, help, comparison conditions and supported claims explicit, with unresolved evidence and acquisition history kept distinct from current ability?

A.2.2:10 - Anti-Patterns and Repairs

Anti-patternSymptomRepair
System-role-kind-as-capability“The inspector role can detect this defect.”Treat bare role through E.10.ROLE; retain the exact local system-role kind and any independently obtaining assignment, then state capability for the holder System only when the bounded capability claim and current support justify it.
Assignment-as-capability“Assigned, therefore able.”Use A.2.1 for assignment and A.2.2 for the qualified holder ability.
Capability attributed to a procedure“The procedure has capability”Keep capability with the holder system.
Unjustified U.MethodDescription admissionTreating “the solver has the algorithm” as sufficient for U.MethodDescription admission.Treat procedure or algorithm wording as a cue to one candidate episteme only when that is the object; admit it as U.MethodDescription through A.3.2 only after its exact EntityOfConcern is an admitted Method and a substantive claim says how that Method is done.
Work-as-capability“We did it once, so we can.”Keep the work occurrence; add a separate capability claim only when envelope, measures, and currentness are justified.
Promise-as-capability“The SLA is our capability.”Use promise content or commitment for what is offered; capability is the internal measured ability that makes the promise credible.
Episteme-as-holder“The report has assessment capability.”Use evidence, source, status, or assessment relation for the episteme; capability holder remains a system.
Unbounded capability“The tool can machine titanium.”State the material grade and performance bounds needed by the receiving use, with the operating conditions and qualification basis that support them.
Capability threshold in system-role-kind nameHighPrecisionWelderSystemRole hides a measured threshold.Keep the system-role-kind name free of the threshold; put precision in the Method-side admission or fit condition and the holder capability claim.
Characteristic-as-capability“Low latency is a capability.”Use U.Characteristic with declared scale for latency; add a capability claim only when a named holder can produce a result class within an envelope that includes the latency measure.
Q-Bundle-as-capability“Resilience is our capability.”Use C.25 for the quality family. If a capability is claimed, state what the holder can maintain or produce under specified conditions and bounds; use a relevant bundle slot in the fit comparison when the receiving demand calls for it.
Architecture-row-as-capability“Maintainability row gives capability.”Use C.32.ACS for the architecture-characteristic criteria row; it may constrain a capability-fit condition but does not establish the holder’s ability.

A.2.2:11 - Consequences

Benefits.

  • Planning separates “can do” from “is assigned now”.
  • Method steps can name capability thresholds without putting extra meaning into system-role-kind names.
  • Work records can be judged against the capability claim and fit predicate current at the time of work.
  • The internal ability and measured envelope supporting a promise are explicit.
  • Composite-system ability can be stated at the right holder instead of scattered across parts.

Costs.

  • A relied-on ability claim must make its relevant envelope, attained bounds and qualification basis recoverable.
  • Teams need to stop using system-role labels or assignments as shortcuts for ability.
  • Some old “function”, “service”, “process”, and “algorithm” sentences need kind recovery before they can be used in FPF.

These distinctions let practitioners check authorization, ability, method, and performance separately.

A.2.2:12 - SoTA-Echoing

Practice question. When can measured performance support a new job, and which change calls for reconsidering the holder’s ability, the qualification of its assertion, or its fit to that job?

For repeatable production, the strongest answer in this comparison is to retain a condition-bound description of performance and compare it with the receiving specification. The NIST/SEMATECH e-Handbook of Statistical Methods, §3.4.5, requires stability before this process-capability use. Its §6.1.6 compares specification limits with the process distribution, distinguishes spread-only Cp from centering-sensitive Cpk, and treats estimation uncertainty and non-normal data separately. These sections supply the substantive practice answer and its limits, not an FPF classification of a capability holder.

An alternative is a Cp width screen: it usefully answers whether the process spread could fit the tolerance if centered. For an actual job, however, the same available mean, spread and limits permit a Cpk comparison without another production run. Retaining the mean removes the extra centering assumption. Adopt that condition-sensitive comparison; reject a spread-only score as sufficient evidence of actual fit when centering is unresolved. This choice costs one additional comparison, while preserving the width screen’s useful information.

In a constructed drilling case, take a stable normal diameter distribution with known mean 10.04 mm and standard deviation 0.02 mm, and demand 9.90–10.10 mm. Then Cp = 1.67, but Cpk = 1.00. A local rule requiring an index of at least 1.33 therefore gives different answers: the width screen passes, while the centering-sensitive fit fails. The threshold is this example’s demand, not a universal NIST rule. Real sample estimates would also need the uncertainty treatment required by that rule.

Adapt this separation in §§2–3: state the holder’s attained performance and conditions, retain its support, and compare the particular demand separately. Tightening the diameter tolerance changes fit without physically changing the drill. Changed calibration can change attained performance; an expired qualification assessment instead changes warranted reliance. Those differences determine which §7 question to reopen. This adaptation does not impose normal distributions, statistical stability or capability indices on every human, software or organizational ability.

Reopen this selection when instability or a changed distribution defeats the retained measurement model, when the decision needs a different loss or uncertainty criterion, or when a rival method distinguishes the same relevant failures with less required evidence. A changed job specification alone calls for a new fit comparison, not a new ability claim or a new method survey.

A.2.2:13 - Relations

PatternRelation
A.1Supplies holon and system grounding.
A.2Use for exact local system-role kinds and C.3.2 classification judgments; neither carries capability by label.
A.2.1Use for directly declared species under U.SystemRoleAssignment; an assignment’s holder System may separately have capability.
A.2.5Use for SystemRoleAssignmentStateRelation and Work-admitting state conditions; assignment state is not capability.
A.2.7Use for SystemRoleKindRelationStructure; admission substitution or incompatibility among system-role kinds does not create capability.
A.3.1Governs U.Method; method may require capability thresholds.
A.3.2Governs membership of one already identified claim-bearing episteme in U.MethodDescription; algorithm, procedure, or possession wording is only a cue until the exact admitted Method EntityOfConcern and substantive way-of-doing claim are recovered. An admitted method description may separately state required capability.
A.3.3Governs U.Dynamics, the state-space and transition-law episteme; dynamics may explain or predict capability but is not the qualified holder ability.
A.15, A.15.1, A.15.2Govern method, plan, and performed work alignment; capability is one input to work admission, not work itself.
A.6.5Governs SlotSpecs when an independently needed relation declaration is current; the capability statement can remain ordinary prose.
A.6.FRepairs function and functionality wording that may hide capability, method, work, math function, or functional-architecture claims.
A.6.RSIRUse it to recover relation, signature, interface, system-role, participation, declaration-position, and slot wording before capability repair when the source sentence is mixed; use E.10.ROLE to select the branch for bare role.
C.27.TA, C.27Use C.27.TA when a positive temporal aspect of capability—currentness, window, rhythm, or drift—is itself relied on; use C.27 for temporal-claim adequacy.
C.2.1, A.10, B.3, C.28, F.10, E.17Govern episteme, evidence, assurance, counterfactual, status, and publication-use relations that may justify or qualify a statement or reliance use about a capability claim.
C.16.P, A.19Govern characteristic, scale, and characteristic-space recovery when capability measures depend on declared measured aspects.
A.17, A.18, C.16Govern the relational characteristic, a declared coverage scale and an actual measurement of usable Method structure in :2.1.
C.2.8Governs structure recoverable from an expressed account; that recovery can inform a Method-relative profile without establishing enactment capability.
E.23.CDI, E.23.CAEE.23.CDI develops the acquisition or provision choice; E.23.CAE distinguishes apparent loss or failed use from a supported capability change.
C.25Governs composite quality families and Q-Bundles that may supply slots for capability-fit checks.
C.30, C.32.HCS, C.32.ACS, C.32.ACEGovern architecture-characteristic material, project criteria rows, and eval readings that may constrain capability use without thereby establishing the holder’s ability.
Promise-content and commitment patternsGovern outward promise and commitment relations; a promise or commitment claim may cite a qualified capability claim, but capability does not become promise or commitment.

A.2.2:14 - Neighboring Claims

Use the direct pattern for any additional claim that the ability or fit decision consumes. Section 4 distinguishes common ambiguous wordings, and section 13 identifies their governors. Keep the neighboring value’s own identity and the contribution it makes to the ability claim, its support or the receiving comparison.

A.2.2:End

A.2.3 - U.PromiseContent — Promised Outcomes and Acceptance Criteria

Type: Definitional promise-content episteme pattern Status: Stable

A.2.3:0 - Use This When

Use this pattern when a project needs to state what is promised to a consumer before asking who is obligated, what work occurred, which system exposes access, or which evaluation method and A.10 evidence relations support a fulfilment assertion.

Typical moments:

  • an SLA publication, service catalog, product offer, public API promise, utility offer, or government-service description contains a statement about what a consumer may rely on;
  • a team says “the service” but might mean promise content, provider organization, API, access point, delivery system, method, ticket, or performed work;
  • a fulfilment claim needs evaluation work that applies declared acceptance criteria to delivery-work facts, affected entities and post-work states, and any delivery or acceptance relation current for the use; the actual evaluation-operation result binding, optional verdict episteme, and A.10 evidence relations remain separate;

Primary EntityOfConcern. The EntityOfConcern of this pattern is U.PromiseContent: a consumer-facing promise-content episteme. For each PromiseContent episteme, the exact C.2.1 EntityOfConcern is the A.2.3:4.1.1 OutcomeSpec episteme designated by promisedOutcomeSpecRef. Its claim graph states the promised outcome, any eligibility predicate, and acceptance claims; accessSpec separately describes the access method when that description is current.

First useful move. Write the promise content as a clause: what outcome is promised, under which effective ReferenceScheme and U.ClaimScope, which local consumer system-role kind or other eligibility predicate applies, how access is described when relevant, and which acceptance criteria selected work facts and post-work states must satisfy. For a fulfilment assertion, name the evaluation Method and the supporting evidence epistemes and A.10 relations separately. Use U.Commitment only for an actual duty bearer after the applicable constitutive rule and its required instituting basis obtain.

What goes wrong if missed. The word “service” starts naming provider, API, method, ticket, work, department, and promise at once. Teams then judge work against an implicit promise, treat access systems as obligations, or count performed work without knowing which promised outcome it was meant to satisfy.

What this buys. One consumer-facing promise-content episteme with explicit outcome and acceptance claims. Each neighboring claim keeps its named EntityOfConcern and direct relation, defined or tested by its own pattern.

Not this pattern when. If the current EntityOfConcern is an individual deontic relation, use A.2.8; if it is performed delivery Work, use A.15.1; if service or access wording hides its concrete subject or direct relation, start with A.6.P:4.11a. A bearer or access-providing arrangement is only one possible recovered reading; code or another episteme, Method, Work occurrence, participation, promise, permission, status, and direct relations keep their own readings. Use A.1 or A.1.SCR only when a separate repaired claim depends on that entity being a system. If source agreement or SLA wording combines several objects, use A.6.C to unpack them.

A.2.3:1 - Problem frame

Across domains the word service is used for many different things: a server or provider, an API, a procedure, a run, a department, even a product bundle. Such polysemy is productive in everyday speech. In a normative model, the current claim must identify which referent is meant.

FPF therefore reserves U.PromiseContent for one kernel meaning: a consumer-facing promise content clause. When service denotes something else, use A.6.P:4.11a to recover whether it denotes code or another episteme, a Method, a Work occurrence or ordinary run, provider participation, a bearer or access-providing arrangement, permission, status, or a direct relation. A product label chooses none of these readings, and bare service has no default system reading. After recovery, name the referent or relation. Apply A.1 or A.1.SCR only when the recovered referent is an entity and the claim depends on its being a system.

Plain reading. A promise content says what a consumer may rely on. A provider System can be classified under a local provider system-role kind. When a claim needs exact delivery Work, use A.13 to identify the System that did it. A.15.1 then admits the dated occurrence as Work from its Method, history, extent, and containing System, without relying on F.6.

If the current use also needs to say exactly under which assignment that Work was performed, F.6 checks the separate relation against the same assignment used by A.13. A U.MethodDescription describes the Method.

PromiseContentUse obtains between the delivery-work occurrence and the selected promise-content edition during the named interval. Work-participation, affected-referent, change, delivery, and acceptance relations state what happened.

A separately performed evaluation applies the declared operation or method; its result binding states the evaluation value. If another use needs a verdict episteme, use C.2.1 to identify it and A.15.PROD to state any applicable entity-identity-inception claim. Evidence relations support the relied-on assertions.

Lexical note (L-SERV and A.6.P:4.11a). Bare service does not determine one FPF referent. When that word carries a relied-on claim, use A.6.P:4.11a to recover the concrete referent or relation: for example, a promise-content episteme and an access-point system have different kinds and participate in different relations. E.10 L-SERV triggers that recovery. After recovery, name the referent or relation and use the pattern that defines or constrains the current claim. Resolve the defining or constraining ClaimGraph only when this claim or a named later use depends on a particular rule edition; the pattern id then serves as its locator.

A.2.3:2 - Problem

Without a first-class U.PromiseContent, a project description tends to make five recurring category errors:

  1. Provider = Service. Calling the provider system or team “the service” collapses that provider referent with the promise-content episteme.
  2. API = Service. Treating an interface or endpoint as the service hides the promised consumer-side outcome and its acceptance criteria.
  3. Method or plan = promise content. Treating a semantic method, a method-description episteme, or a work plan as the promise content hides the consumer-facing outcome and acceptance claims.
  4. Run = Service. Logging Work as “a service” erases the promise-content episteme and acceptance specification needed for SLA reasoning.
  5. Business ontology lock-in. Large domain schemes are imported wholesale, losing FPF universality and comparability across projects and domains.

A.2.3:3 - Forces

ForceTension
Consumer promise vs provider abilityPromise content states the consumer-side outcome; capability states what the provider System can do under declared conditions.
Specification vs executionPromise content remains an episteme; exact delivery-work facts, affected entities, post-work states, and separately governed delivery or acceptance relations are evaluated against the promised predicates. The evaluation operation’s result binding and any verdict episteme remain distinct from those subject facts.
Universality vs domain richnessOne kernel meaning must cover IT, utilities, healthcare, public services—without absorbing domain taxonomies.
Reviewable acceptance vs method choiceConsumers need named outcome predicates, characteristics, scales, target values, and acceptance criteria. The provider selects a delivery Method within those constraints and any applicable commitments; an individual deontic duty enters only through an independently obtaining U.Commitment.
Stability vs evolutionA changed promise creates a new promise-content episteme edition, while earlier work occurrences and evidence relations retain their own identities.

A.2.3:4 - Solution - Define U.PromiseContent as the promise-content episteme

Definition (normative). A U.PromiseContent is an externally oriented promise-content episteme. Its claim content states a promised consumer-side outcome, any eligibility predicate, and acceptance criteria by which fulfilment is evaluated. Its optional accessSpec describes the access method. Interpretation is fixed by its effective ReferenceScheme; U.ClaimScope states where the claims hold.

U.PromiseContent is not a deontic commitment relation. One or more explicit U.Commitment occurrences under A.2.8 may have the promise content in their referents position; the promise-content episteme does not obligate an actor by itself.

In normative prose, the head phrase is promise content. Service offering clause and service promise clause are admissible Plain twins for that promise-content use; bare service does not identify a promise-content episteme.

Species-level identity follows C.2.1:

PromiseContentIdentity = <
  content,
  promisedOutcomeSpecRef,
  effectiveReferenceScheme
>

promisedOutcomeSpecRef is a U.EpistemeRef field that designates the exact A.2.3:4.1.1 OutcomeSpec episteme about which the promise claims are made; that episteme is the exact EntityOfConcern of this PromiseContent episteme. The field is not EntityOfConcernSlot: that SlotKind names the participant meaning only inside the reusable C.2.1 constitution RelationSignature. OutcomeSpec is a specification-use episteme form, not a separately admitted U-kind. The exact claimScope qualifies where the promise-content claims hold and remains outside the identity tuple.

  • FPF kind: U.Episteme.

  • Time stance: the promise content can be authored before delivery; later exact delivery-work facts, affected entities, post-work states, and any current delivery or acceptance relations are tested against the declared outcome and acceptance predicates. Evaluation work and the actual operation-result binding remain separate; when a verdict episteme is constituted, C.2.1 and A.15.PROD govern its identity and inception, while A.10 evidence relations support the relied-on assertions.

  • Orientation: consumer-facing promise claims, not provider capability claims.

  • Publication boundary: The selected promise-content U.Episteme may participate in an exact EpistemePublicationRelation for a declared audience and bounded use. PublicationExpressionRelation relates that selected edition, an independently identified expression, and the bounded-use declaration; PublicationExpressionBearingRelation relates an independently identified carrier to that expression. A selected reusable form constrains the expression through PublicationFormConformanceRelation; E.24.PUB’s form-mediated expression and bearing claims require that same expression as witness when used together for availability.

    Promise-content identity follows the C.2.1 episteme identity rule; no publication-relation occurrence, expression, form, or carrier enters that rule.

A.2.3:4.1 - Promise-content schema

U.PromiseContent : U.Episteme {
  content                  : NonemptyClaimContent,
  promisedOutcomeSpecRef   : U.EpistemeRef, resolving to OutcomeSpec,
  effectiveReferenceScheme: EpistemeInterpretationScheme,
  providerSystemRoleKindRef : U.KindRef,
  consumerSystemRoleKindRef?: U.KindRef,
  claimScope               : U.ClaimScope,
  accessSpec?              : U.MethodDescription,
  acceptanceSpec           : U.Episteme,
  unitOfDelivery?          : U.Episteme
}
  • content is the complete interpreted promise content: promised-outcome, eligibility, and acceptance claims together with the optional accessSpec value when an access-method description is current. It satisfies NonemptyClaimContent under C.2.1:4.1.2; a graph representation or document supplies it only through a recoverable interpretation.
  • providerSystemRoleKindRef and consumerSystemRoleKindRef are promise-content fields typed by the existing U.KindRef; each resolves to one exact local system-role kind. accessSpec, acceptanceSpec, and unitOfDelivery are episteme values carried by value in the claim graph; a publication or other declared representation may express them through U.EpistemeRef values that resolve to those same epistemes without changing their kinds. Changing one of these content values or resolved kind references changes content and therefore the promise-content identity.
  • promisedOutcomeSpecRef resolves to the A.2.3:4.1.1 OutcomeSpec episteme.
  • effectiveReferenceScheme is a C.2.1:4.1.2 EpistemeInterpretationScheme value whose rules and domains interpret this complete claim content and its references. Establish that it covers every acceptance criterion used; then judge fulfilment separately from the selected work facts and post-work states under the stated evaluation Method.
  • providerSystemRoleKindRef and consumerSystemRoleKindRef identify local work-facing kinds, not particular providers or consumers. When an actual assignment is claimed, identify its occurrence and directly declared species under U.SystemRoleAssignment.
  • claimScope is the exact U.ClaimScope over which the promise claims hold; it states the applicable operating conditions, populations, locales, and other admitted slices instead of leaving extent implicit.
  • accessSpec describes the access Method for an eligible consumer. Actual requests follow the performer-and-Work conditions in §4.3; an access-point system remains separate.
  • acceptanceSpec states the acceptance criteria and selects the exact evaluation Method. It cites a MethodDescription edition only when the acceptance claim depends on that episteme’s claims. Evidence-admissibility conditions may be stated there; actual evidence-use relations remain separate.
  • unitOfDelivery states how accepted delivery work is counted when counting is current.
  • There is no generic modelUseStructureRef field. When an independently selected BoundedModelUseStructure changes one model-local receiving interpretation, the receiving assertion or use designates that structure separately; the structure neither identifies the promise content nor becomes an optional participant of PromiseContentUse. A structure-dependent relation species would require its own direct pattern, mandatory structure participant, stronger predicate, and occurrence-identity rule.
  • An internal delivery method remains U.Method. An already identified episteme is a U.MethodDescription only when its exact EntityOfConcern resolves to that Method and at least one claim says how that Method is done. A promise-content or acceptance claim may cite that episteme for one named use; Method-selection work, performed work, and PromiseContentUse remain separately governed.
A.2.3:4.1.1 - OutcomeSpec - promised Work, post-work result, or both

This section is the authoritative FPF locus for the promise-facing OutcomeSpec shape. A.7 supplies the strict distinction among the specification episteme, Work occurrence, affected referent, post-work state, counting rule, and evidence; it does not define another schema.

promisedOutcomeSpecRef resolves to an independently identified specification-use episteme that says what is promised. OutcomeSpec is a specification-use episteme form, not a separately admitted U-kind.

OutcomeSpec : U.Episteme ::= {
  mode: WorkOnly | ResultOnly | Composite,

  workSpec?: {
    methodConstraintRef?: U.MethodRef,            // resolves directly to an admitted U.Method
    methodDescriptionRef?: U.EpistemeRef,         // only when exact claims in one A.3.2-admitted edition are used
    workPredicateRef: U.EpistemeRef                // predicate on selected facts about delivery Work
  },

  resultSpec?: {
    entityOfConcernRef?: U.EntityRef,              // promised affected referent or its declared kind
    statePlaneRef?: StatePlaneRef,                 // where the post-condition is interpreted, when current
    postConditionRef: U.EpistemeRef                // predicate on the required post-work state
  }
}

The modes have these completeness requirements:

  • WorkOnly requires workSpec and omits resultSpec;
  • ResultOnly requires resultSpec and omits workSpec; and
  • Composite requires both.

workSpec constrains selected facts about delivery Work. A Method constraint resolves directly to the Method; a separate MethodDescription reference is optional and edition-specific. resultSpec constrains the exact affected referent selected for the delivery and its required post-work state. At fulfilment time, state any actual-change, production, delivery, acceptance, or receiving-use relation under its own predicate. An optional mathematical Delta expression remains a separate lens only when a named comparison uses it; no U.Work.Delta field or universal change record is required.

In ordinary agreement wording, outcome may mean Work, achieved state, or both. Recover the intended mode instead of inventing one OutcomeInstance kind. A downstream bundling, invoicing, or dispute claim separately references the actual Work occurrences, affected entities, post-work states, direct relations, evidence epistemes, and evidence-use relations it needs.

Examples. Work for at least five minutes is WorkOnly. A hole at least one metre deep exists at the stated site is ResultOnly. Cut and style the client's hair within twenty minutes, with the resulting hairstyle satisfying the evening-style condition is Composite.

The head noun outcome is broad. When the passage means Work, affected entity, or required post-work state, name that object directly. Counting is not part of OutcomeSpec; A.2.3:4.1.2 governs unitOfDelivery.

A.2.3:4.1.2 - Unit-of-delivery counting

Use unitOfDelivery only when a receiving use counts accepted delivery. It is a specification-use episteme carried in the promise content.

An ordinary rule may say: Count one accepted delivery per appointment; rework under the same appointment does not add another unit. When replay or measurement needs a structured representation, use only the fields that rule requires:

UnitOfDeliverySpec : U.Episteme ::= {
  unitDesignator: U.NameToken,
  countingRule: {
    selectorRef: U.EpistemeRef,                   // selects only delivery Work for which fulfilment obtains
    quantityRuleRef: U.EpistemeRef,               // maps selected facts to the count or measured quantity
    aggregationRef?: U.EpistemeRef,
    dedupeKeyRef?: U.EpistemeRef,
    countingPolicyRef?: U.EpistemeRef,
    measurementMethodRef?: U.MethodRef,
    measurementMethodDescriptionRef?: U.EpistemeRef,
    evidenceAdmissibilityRef?: U.EpistemeRef
  }
}

The selector admits only Work occurrences for which the promise’s delivery and acceptance predicates are satisfied. For a cross-promise aggregate using one Work occurrence, or when rework must not add another delivery unit, dedupeKeyRef or the cited counting policy states the intended boundary. Separate per-promise counts may use the default below.

When the count depends on a measurement reading, identify the measurement Method and the specification values needed to interpret that reading. Cite a MethodDescription only when the calculation or interpretation uses claims in that edition. Retain the evidence-admissibility conditions, evidence epistemes and evidence-use relations required for reliance on the count.

If unitOfDelivery is absent, the local default is one unit per obtaining PromiseContentFulfilmentRelation occurrence. A separately governed charging relation may consume the resulting quantity but does not define this counting rule.

A.2.3:4.1.3 - Recommended acceptanceSpec mini-schema (informative, non-kernel)

Projects may express acceptanceSpec with the following small schema when downstream evaluation work requires replayable criteria and verdict semantics. Here SC denotes the promise-content episteme containing that acceptance specification:

AcceptanceSpec (recommended) ::= {
  targetOutcomeSpecRef?: U.EpistemeRef,          // resolves to OutcomeSpec; default is SC.promisedOutcomeSpecRef
  criterionRefs: [U.EpistemeRef],                // each resolves to one evaluation-criterion episteme
  evaluationMethodRef: U.MethodRef,               // resolves directly to the evaluation Method
  evaluationMethodDescriptionRef?: U.EpistemeRef, // only when exact claims in one A.3.2-admitted edition are used
  verdictScaleDescriptionRef: U.EpistemeRef,     // resolves to one declared scale description
  GammaTimePolicyRef?: U.EpistemeRef             // resolves to the policy selecting the evaluation window
}
  • targetOutcomeSpecRef makes explicit which promised outcome is being judged; if omitted, it is the containing promise content’s promisedOutcomeSpecRef.
  • criterionRefs resolve to evaluation-criterion epistemes. Their predicates are evaluated over the same selected work facts and post-work state references used for the targeted OutcomeSpec; direct evidence relations separately support assertions about those facts and states.
  • evaluationMethodRef resolves directly to the evaluation Method. evaluationMethodDescriptionRef, when present, cites one A.3.2-admitted episteme edition whose claims constrain or explain that Method; the description is neither the Method nor the evaluation Work.
  • verdictScaleDescriptionRef resolves to one scale-description episteme governed by the characteristic and scale patterns. That description states the admitted verdict values and how non-delivery is represented. Informative examples include Boolean pass/fail, trichotomy pass/partial/fail, or named graded values, with non-delivery represented as fail, N/A, or Inconclusive; these values are examples, not defaults.
  • GammaTimePolicyRef keeps temporal selection explicit and non-retroactive (F.10 and F.12): it resolves to the policy stating whether judgement is per work occurrence, reporting window, or another named temporal selection. Population and locale remain in U.ClaimScope; they are not temporal-policy values.

This mini-schema is a recommendation only: it does not admit another U-kind. An acceptance-specification episteme may contain these declared schema fields by value or refer to their values through the declared RefKinds.

A.2.3:4.2 - What U.PromiseContent is not

  • Not a provider: identify the provider; when the current claim is its system-role assignment, use an assignment occurrence and its declared species under U.SystemRoleAssignment. The occurrence identifies the provider System and assigned local kind; the species defines those participant meanings and the assigned-kind domain.
  • Not an individual deontic commitment: that is one obtaining U.Commitment under A.2.8 whose actual duty bearer, exact referents, constitutive rule, instituting basis, scope, and validity are established independently.
  • Not an access point or bearer: addressable service, server, desk, endpoint, process, component, application, host, or cluster wording first goes to A.6.P:4.11a. Recover whether it denotes code or another episteme, a Method, a Work occurrence or ordinary run, a bearer or access-providing arrangement, or another directly governed object; apply A.1 or A.1.SCR only when a separate repaired claim depends on a recovered entity being a system.
  • Not a method or method description: the semantic way of doing is U.Method; a recipe or other episteme describing that way is U.MethodDescription.
  • Not delivery work or its description: performed delivery is U.Work; a ticket, case description, or incident description is a separately governed episteme about planned or performed work.
  • Not a work schedule: use U.WorkPlan under A.15.2 when the content coordinates intended Work.
  • Not a capability: capability is the provider System’s ability to perform a work family or produce a result class under declared conditions and attained bounds. A.2.2 separates that proposition from its assertion, qualification and fit. Delivery may depend on several qualified ability claims about the provider or other holders.
  • Not its scope or use interval: U.ClaimScope states where the promise claims hold, U.WorkScope states the work conditions covered by the provider’s capability claim, and PromiseUseIntervalSlot states when one PromiseContentUse occurrence obtains. These are three different values.

A.2.3:4.3 - Promise content, delivery work, and evaluation work

  • Before delivery work: The promise-content episteme declares its effective ReferenceScheme, named U.ClaimScope, promised outcome specification, access specification when current, and acceptance specification. A.2.2 states the provider System’s qualified ability. A separate capability-fit predicate compares that claim’s work conditions and attained bounds with the conditions and thresholds selected for the planned delivery work, including any threshold stated by the chosen method description.

    Method-selection work may yield a C.11 ChoiceResult; enactsMethod obtains between the later delivery-work occurrence and the selected U.Method. A relied-on episteme is a U.MethodDescription only when it meets A.3.2 membership, and the promise-content or acceptance claim may cite it for the named use.

  • Run‑time: For request or visit Work, use A.13 to identify the actual consumer System S, then let A.15.1 admit requestWork independently. If the current use must also state under which assignment the request was performed, F.6 checks performedUnderAssignment(requestWork, consumerRA) against the same assignment used by A.13 and compares S with consumerRA.HolderSystemSlot.

    For delivery Work, use A.13 to identify the actual provider System S, then let A.15.1 admit deliveryWork independently. If the current use must also state under which assignment the delivery was performed, F.6 checks performedUnderAssignment(deliveryWork, providerRA) against the same assignment used by A.13 and compares S with providerRA.HolderSystemSlot.

    For evaluation Work, use A.13 to identify the actual evaluator and let A.15.1 admit the dated occurrence before saying that it enacts the Method selected by acceptanceSpec. Add F.6 only if the current use must also state under which assignment the evaluation was performed. Cite the optional MethodDescription only when the evaluation claim depends on that edition. The actual evaluation-operation application carries its argument bindings and result value. When another use needs a durable verdict episteme, C.2.1 governs that episteme and A.15.PROD governs any current identity-inception claim. The counting rule in unitOfDelivery maps admitted fulfilment occurrences to unit counts.

    The verdict episteme may assert whether a named service-level objective or another acceptance criterion was satisfied during the declared window. When a separately obtaining U.Commitment has the same U.PromiseContent in its referents position, the supported assertion concerns fulfilment of content that is also a referent of the obligation. Neither the operation-result binding, verdict episteme, nor commitment is a property of the promise-content episteme.

    When a separate F.6 performedUnderAssignment(W, RA) claim is made, W is already admitted and RA is the same assignment used by A.13. F.6 compares that assignment’s holder with the actual performer already identified through A.13 and used by A.15.1. A missing or failed F.6 check alone leaves independently admitted Work intact. If the same finding invalidates a premise consumed by A.13/A.15.1 admission, recheck that premise and its dependent conclusions under F.6:4.2.

Memory hook: Promise content states what is promised. A method constrains possible work. A system performs work. Evaluation binds a result value. A verdict episteme states the judgment. Evidence supports that assertion.

A.2.3:4.4 - Didactic card: Relations around one service-delivery evaluation

Didactic (non-normative). This representation keeps each promise-content episteme, access-description episteme, work occurrence, and direct relation in one delivery evaluation visible without prescribing an order of work. Promise content and an access description remain epistemes; an individual commitment and a system-role assignment remain relations; delivery and evaluation remain work occurrences; evidence remains in its A.10 relations. When order matters, describe semantic method order in U.MethodDescription, intended dated order in U.WorkPlan, and transformation dependencies in the relevant TransformationFlowStructure.

U.PromiseContent states the promise. An A.2.8 U.Commitment relation may refer to that content; its duty-bearer position is filled by one System or separately identified party. The provider-assignment species defines holder and assigned-kind meanings. Delivery and evaluation follow the §4.3 route: A.13 identifies who performed the Work, and A.15.1 admits the dated occurrence independently. The diagram shows an F.6 edge only when this case also needs the exact assignment under which that Work was performed. Evidence relations support selected delivery-work facts and post-work states. The evaluation operation carries its result binding, while C.2.1 identifies any verdict episteme and A.15.PROD states any identity-inception claim.

This informative diagram is a publication-side representation, not new ontology.

flowchart LR
  SC["Promise content<br/>(U.PromiseContent episteme)"]
  C["Commitment<br/>(deontic relation, when current)"]
  RA["Provider system-role assignment<br/>(A.2.1 direct relation occurrence)"]
  W["Delivery work<br/>(U.Work occurrence)"]
  EV["Evidence epistemes<br/>(observations used as evidence)"]
  EW["Acceptance evaluation<br/>(U.Work occurrence)"]
  ER["Evaluation result<br/>(U.Episteme with verdict value)"]

  C -->|"refers to"| SC
  %% The actual duty-bearer position of the commitment is filled directly; no universal commitment-to-assignment relation is asserted.
  W -->|"performedUnderAssignment"| RA
  EW -->|"evaluates selected facts about"| W
  EW -->|"criteria from"| SC
  EW -->|"evaluation operation; result binding stated in ER"| ER
  EV -->|"A.10 evidence relation supports verdict assertion in"| ER

Reading guide.

  • The promise content is the consumer-facing outcome and acceptance statement.

  • In the A.2.8 commitment relation, the actual duty-bearer position is filled directly and the referents position contains the promise-content clause. The exact constitutive rule and its required instituting basis must obtain before that individual relation is asserted.

  • The provider system-role assignment is an occurrence of a declared assignment species. The species defines the holder, assigned-kind, and any other identity-bearing participant meanings; the occurrence identifies the provider System, its assigned local kind, and any other participant values.

    The assertion has exact claim content, EntityOfConcern, and effective ReferenceScheme; its ClaimScope, selected slice, normative-frame edition, qualification window, or operating condition is stated separately when it changes interpretation or validity. None is a world-side assignment participant.

  • A.6.P:4.11a recovers the concrete referent or relation denoted by service wording. It adds no service-situation participant: provider assignment, access description, access-point system, delivery system, delivery method, promise content, and work occurrence remain distinct and keep their own kinds. Use A.10 for the evidence relations.

  • Delivery Work is what happened. Follow the §4.3 performer-and-Work route, and add the separate F.6 assignment check only if this use must also say exactly under which assignment the Work was performed. Exact affected referents, pre-work and post-work states, and any actual-change, production, delivery, or acceptance relations remain separately identified. Evidence-use relations support assertions about those facts. Evaluation Work follows the same route before its selected evaluation Method, application result, and any verdict episteme are stated separately.

Litmus rule (addressability). If the current claim is about invocation, connection, visitation, restart, or scaling, first use A.6.P:4.11a to recover the process, deployed component, endpoint, application, host, cluster, desk, or other bearer. That cue establishes neither U.System nor a whole delivery-system boundary. Apply A.1 or A.1.SCR only when the repaired claim depends on systemhood; after recognition, call the entity a service access point or service delivery system only when that boundary claim is current. Otherwise keep the bearer and keep promise content separate.

A.2.3:5 - Archetypal grounding (engineer‑manager friendly)

Worked-case premise. E.24.UK has already admitted the public U.System kind. Every entity named as a system in the rows below independently satisfies the complete A.1 criterion, including acting eligibility. If that premise cannot be established, keep the entity without system membership and stop only the provider-assignment, access-point, delivery-system, or Work-attribution claim that depends on it; other direct claims may continue under their subject patterns.

DomainPromise-content epistemeProvider and consumer assignmentsAccess specificationDelivery workEvidence and evaluation
Cloud storageStore and retrieve blobs up to 5 TB under declared criteria—for example, 99.9% availability and 99.999999999% durability (eleven nines); these values illustrate targets and are not defaults.CloudStoragePlatformSystem holds StorageProviderSystemRole; BackupControllerSystem holds StorageConsumerSystemRole, each through an A.2.1 assignment occurrence and its declared species.S3ApiDescription-vX, a U.MethodDescription; the endpoint is a separate bearer, treated as a U.System under the worked-case premise.Dated PUT, GET, replication, and integrity-check Work occurrences participating in PromiseContentUse.Request and integrity observations enter direct evidence relations; evaluation applications bind availability or durability results, and separately constituted verdict epistemes state the judgments.
Manufacturing utilityDeliver compressed air at 8 bar in Zone B under stated pressure, flow, and purity criteria.CompressedAirPlantSystem holds UtilityProviderSystemRole; LineBSystem holds UtilityConsumerSystemRole, each through an A.2.1 assignment occurrence and its declared species.ZoneBManifoldAccessDescription, a U.MethodDescription; the manifold is a separate bearer, treated as a U.System under the worked-case premise.Dated compression and delivery Work occurrences.Pressure, flow, and purity observations support delivery claims; an evaluation application binds the comparison result under the declared scale and window, and a verdict episteme states the judgment.
Public passport serviceIssue an admissible passport within 20 days under declared defect and eligibility criteria—for example, a ≤ 1% defect target; this value is illustrative, not a default.IssuingAgencySystem holds PassportIssuerSystemRole; ApplicantPersonSystem holds PassportApplicantSystemRole, each through an A.2.1 assignment occurrence and its declared species.PassportApplicationAccessDescription, a U.MethodDescription; portal and service-desk bearers are access-point U.System values under the worked-case premise when that boundary claim obtains.Dated application-handling and passport-issuance Work occurrences.Submission, issuance, elapsed-time, and defect observations support claims; evaluation applications bind lead-time or defect results, and separately constituted verdict epistemes state the judgments.

Key takeaway. The same pattern yields one promise-content episteme in each domain. Direct system-role assignment, PromiseContentUse, evaluation-operation, evidence, acceptance, and publication relations retain their own participants and governors; evaluation remains separately performed U.Work.

Locality replay. In the cloud-storage row, identify CloudStoragePromiseContent-v3, CloudStorageOfferScheme-2026, and EligibleStorageAccounts-EU-2026Q3 as the exact promise-content edition, its effective scheme, and its U.ClaimScope. Then PromiseContentUse(PUT-2026-07-14-1042, CloudStoragePromiseContent-v3, Interval-PUT-1042) ties one dated delivery-work occurrence to that edition.

Name a selected model-use structure only in a receiving assertion or use that is model-local. If another catalog scheme is consumed, add the exact obtaining F.9 Bridge, the separate claim that it suits this bounded use, and the A.10 evidence-provenance relation with RelianceDisposition=pass. Use B.3 only if a named assurance claim about this use is current.

A.2.3:5.1 - Bias-Annotation

A.2.3 repairs the collapse of several service-related referents into one service label. A visible service name often denotes provider, access point, method, work, commitment, ticket, evidence, and promised outcome without saying which claim is current. A.2.3 governs the promise-content episteme. For neighboring claims that are current, use A.2.8 for commitment, A.2.1 for a provider’s system-role assignment, A.3.2 for an access description admitted as U.MethodDescription, A.15.1 for delivery Work, A.10 for evidence relations, and the direct outcome and acceptance patterns for their respective relations.

In an agreement or SLA, an A.2.8 U.Commitment may have promise content in its referents position. An agreement publication, service catalog, API page, or offer publication may provide a physical or digital carrier whose actual state or realization yields an expression of selected U.Episteme values about the agreement, promise content, commitment, or fulfilment work. Identify the expression independently and any reusable form whose rules it follows. An exact EpistemePublicationRelation may make each selected episteme available to its declared audience for its bounded use. These commitments, epistemes, expressions, forms, publication occurrences, and carriers retain separate identities.

A.2.3:6 - Mapping the common “service” picture to FPF (didactic bridge)

A common service diagram is a representation. Recover the represented systems, epistemes, work occurrences, and relation occurrences as follows:

  • Provider participation -> when this mapping needs the provider’s assignment, name its occurrence and declared species under U.SystemRoleAssignment. The occurrence supplies its holder System, assigned local kind, and any other participants; the species defines their meanings. For each selected delivery-work occurrence, follow the §4.3 route to identify the actual performer and admit the Work independently. Add F.6 only if the mapping must also say exactly under which assignment that delivery was performed; a missing or failed check leaves the delivery Work intact.

  • Acceptance criterion -> an evaluation-criterion episteme in U.PromiseContent.acceptanceSpec; its target values, verdict scale, and GammaTimePolicyRef remain explicit. A U.WorkPlan is added only when planned delivery or evaluation work is current.

  • SLA obligation -> one A.2.8 U.Commitment occurrence whose actual duty bearer is explicit and whose referents include the relevant U.PromiseContent; assert it only after the applicable constitutive rule and required instituting basis obtain. Use A.6.C when one SLA publication combines wording about commitment, promise content, evidence specification, and publication relations.

  • Published SLA terms -> the selected U.PromiseContent / U.Episteme, the exact expression that expresses it for the bounded use, any selected reusable publication form whose rules that expression follows, the independently identified carrier bearing that expression, and the obtaining EpistemePublicationRelation occurrence that makes the selected edition available to the declared audience.

    When publication work also communicates or institutes a commitment, add the named A.2.9 speech-act and A.2.8 commitment relation occurrences; publication alone neither creates the commitment nor establishes fulfilment.

  • Operating conditions -> the named U.ClaimScope under A.2.6. The acceptance specification may cite that scope; it does not replace it.

  • Promised subject -> resolve promisedOutcomeSpecRef and follow the declared mode. Use workSpec for promised Work conditions and, when resultSpec is present, use its postcondition and any entityOfConcernRef to identify the required affected referent and post-work state. State only the direct delivery or acceptance relations required by the current claim.

  • Customer material—“ours versus theirs.” -> If the current claim depends on who owns or has custody of data, an asset, or a case, name the exact obtaining system-role assignment when work-facing assignment matters, and name the ownership or custody relation with its actual participants when that is the claim. Neither relation substitutes for the other, and neither becomes a kernel-global property of U.PromiseContent.

  • Access -> accessSpec : U.MethodDescription describes the Method enacted when an eligible consumer holder requests access. Recover the endpoint, desk, manifold, or other bearer through A.6.P:4.11a. Its label and addressability establish no U.System membership. Apply A.1 or A.1.SCR only when a current access-point, delivery-system, performer, or assignment claim depends on systemhood; otherwise keep the bearer claim separate.

  • One PromiseContentUse occurrence -> consumer request Work and provider delivery Work remain separate occurrences. Follow the §4.3 performer-and-Work route for each. If this mapping must also state the assignment under which either occurrence was performed, add its separate F.6 relation against the same assignment used by A.13; a missing or failed check leaves the Work intact.

    When request Work follows accessSpec, its A.15.1 methodDescriptionRef resolves to that same U.MethodDescription; following the description does not by itself introduce a second relation occurrence. PromiseContentUse obtains between selected delivery Work and the selected promise-content edition during PromiseUseIntervalSlot.

  • Consumer-side changed entity or relation -> recover the exact affected-referent and actual-transformation facts, plus any local entity-identity-inception, delivery, acceptance, or receiving-use claim that the current promise evaluation needs. If the changed entity is a holder system and its post-work state changes the truth of a qualified ability claim, use A.2.2 to restate that claim and reassess its support and currentness.

  • Service-enabled consumer-side capability or activity -> If the question is about ability, identify the consumer holder and state its qualified ability, support and currentness under A.2.2. If the question is about activity, identify the consumer-side dated U.Work under A.15.1. If the claim also says that delivery changed the consumer or was used by that Work, state only the exact actual-change or receiving-use relation that currently obtains; otherwise keep the objects separate. Do not create another U-kind or a generic capability-use relation.

When a domain claim concerns catalog entries, exposure relations, charging relations, or entitlement relations, govern those entries, participants, and relations directly. Relate them to U.PromiseContent only through named relations; do not treat them as components of U.PromiseContent or replace their direct relations with a locally minted context relation.

A.2.3:7 - Conformance Checklist (normative)

CC‑A2.3‑0 (Prose head phrase). In normative prose, an instance of U.PromiseContent SHALL be referred to as a promise content (or service offering clause or service promise clause) and SHALL NOT be referenced by the bare head noun service. For the conditional L-SERV recovery rule, see CC-A2.3-10.

CC‑A2.3‑1 (Type). U.PromiseContent IS a consumer-facing promise-content U.Episteme. One or more exact EpistemePublicationRelation occurrences may make the same selected promise-content edition available through separately identified expressions and carriers without changing its episteme identity. Identify reusable forms when their rules matter. No expression, publication form, or presentation carrier is the promise content. U.PromiseContent is not a U.System, U.Method, U.MethodDescription, U.Work, or U.WorkPlan.

CC-A2.3-2 (Semantic locality). Every promise content names its effective ReferenceScheme, promisedOutcomeSpecRef, and exact U.ClaimScope. A selected BoundedModelUseStructure may be designated only by the receiving assertion or use when it changes one model-local interpretation; it is neither a promise-content field nor an optional participant or identity discriminator of PromiseContentUse.

CC-A2.3-3 (System-role kinds stay distinct from holders and assignments). providerSystemRoleKindRef and, when present, consumerSystemRoleKindRef are promise-content fields typed by U.KindRef and resolve to local system-role kinds. When actual provider or consumer assignments are claimed, their species are declared under U.SystemRoleAssignment; a kind label or reference alone identifies neither a holder nor a performer.

CC-A2.3-4 (Acceptance). acceptanceSpec MUST be present and MUST define how delivered U.Work is judged as pass, fail, or a declared grade against named evaluation criteria and target values. Any SLA deontics are represented through U.Commitment. The promise content MUST declare Claim scope (G) where operating conditions, populations, locales, or another claim extent matter. Every verdict cites an explicit Gamma_time window.

If the acceptance criteria mention measurable characteristics such as availability, latency, accuracy, cost, or safety, each characteristic MUST be introduced through C.16 with its scale, unit when applicable, and measurement specification under C.16:5.2. A relied-on measured verdict additionally names its supporting evidence and direct evidence relations. When a quality-family label hides several possible contributors, use C.25 to retain the one characteristic or structured bundle that the acceptance claim needs. If the reading depends on a particular measurement Method, identify that Method. Cite its U.MethodDescription only when the acceptance claim depends on that edition’s claims. The characteristic is referenced by its exact identifier rather than by an unqualified KPI label.

CC‑A2.3‑5 (Access). When the promised use relies on a request-facing access Method, accessSpec MUST identify the A.3.2-admitted U.MethodDescription that describes it. Separately recover the endpoint, desk, manifold, or other exact bearer through A.6.P:4.11a. Apply A.1 or A.1.SCR only when a current claim depends on that bearer being an access-point U.System; otherwise keep the bearer without the stronger claim. If no access-method description is current because access is ambient, accessSpec may be omitted. In either branch, keep an eligibility predicate in the promise content when eligibility is promised; when eligibility depends on a separately obtaining admission relation, identify that relation and use the pattern that defines or tests it.

CC‑A2.3‑6 (Unit of delivery + counting rule). For a receiving use that counts accepted delivery, use the default one-unit-per-fulfilment rule or declare unitOfDelivery with the intended unit (for example, one request, kWh, or case) and counting rule. Declare unitOfDelivery when the default does not define the intended counting boundary, including rework or a cross-promise aggregate. The resulting count may fill a declared quantity position in a separately governed charging relation; that charging relation does not determine the unit-of-delivery specification. When declared, unitOfDelivery includes the A.2.3:4.1.2 counting rule that maps fulfilment Work to unit counts without silent double counting. If omitted, the default is one unit per obtaining PromiseContentFulfilmentRelation occurrence.

CC‑A2.3‑7 (No actuals on Promise Content). Resource and time actuals belong to the performed U.Work occurrence under A.15.1. An incident-log episteme may describe that occurrence and may separately participate in an evidence relation for a stated claim; neither the log nor its participation in that evidence relation fills a U.PromiseContent slot.

CC-A2.3-8 (Provider capability stays separate). When delivery depends on provider ability, use the A.2.2 qualified ability claim about the provider System and the separate capability-fit predicate for the planned delivery work. Do not insert capability into promise-content identity or infer capability or fit from a system-role designation or assignment.

CC-A2.3-9 (Edition and promise-use interval). A change to content, promisedOutcomeSpecRef, or effectiveReferenceScheme creates a new promise-content episteme edition under the C.2.1 identity rule. Each PromiseContentUse occurrence has one promise-content edition and one delivery-work occurrence as participants and PromiseUseIntervalSlot as its temporal qualifier; an untyped version or timespan entry fills none of those positions.

CC‑A2.3‑10 (Lexical rule). Apply E.10 L-SERV and A.6.P:4.11a only when service or access-like wording occurs in a relied-on FPF claim, recommendation, decision, gate, assurance, publication, or reuse and hides the concrete subject, participant, predicate, kind, permission, Work occurrence, or next route. The author MUST name that hidden choice or stop the relied-on use; quoted, historical, illustrative, and harmless ordinary wording is outside this rule.

CC‑A2.3‑11 (No mereology). Do not place a promise content clause in PBS or SBS, or treat it as a part or component. Structural assemblies live in PBS and SBS; the promise clause is an episteme (A.2.3). For hidden service referents, see CC-A2.3-10.

CC-A2.3-12 (Plan, work, and evidence stay distinct). Planned-work windows and calendars are content of U.WorkPlan (A.15.2). Performed delivery belongs to U.Work (A.15.1). Exact affected referents, pre-work and post-work states, and direct actual-change, production, delivery, or acceptance relations remain separate. Evidence epistemes and evidence-use relations support assertions about those facts; they are not slots or parts of the Work occurrence.

CC-A2.3-13 (Claim scope, work scope, and promise-use interval). The promise-content episteme names one exact U.ClaimScope; an intended maximal extent is stated as that scope rather than represented by omission. The qualified ability claim about the provider separately designates its U.WorkScope; this work-condition basis is distinct from the episteme’s ClaimScope. PromiseUseIntervalSlot is the temporal qualifier of each PromiseContentUse occurrence.

The ScopeCoverage predicate is satisfied only when the selected context slice belongs to the claim scope. When membership depends on time, name an explicit Gamma_time selector and its membership boundary; retain every selector already declared in the slice even when this predicate does not inspect it. Neither temporal extent nor capability scope replaces claim scope.

CC-A2.3-14 (Scheme and scope bridges). Cross-scheme reuse first names the exact obtaining F.9 Bridge occurrence. A separate current C.2.1 claim with affirmative polarity must say that this Bridge suits the named bounded promise-content use, in the stated direction, under the use-specific correspondence rule, and within the permitted-loss tolerance. Ordinary reliance requires the exact A.10 evidence-provenance relation with RelianceDisposition=pass for that use. Use B.3 only when a named assurance claim is current; its result supports, narrows, or blocks only that bounded assurance use. Cross-scope reuse separately names the mapped U.ClaimScope and its A.2.6 relations.

CC-A2.3-15 (OutcomeSpec typing). promisedOutcomeSpecRef MUST be a U.EpistemeRef resolving to an A.2.3:4.1.1 OutcomeSpec specification-use episteme. It MUST NOT point at a concrete U.Work occurrence, affected or delivered entity, actual operation-result binding, verdict episteme, or downstream effect, and OutcomeSpec MUST NOT be written as an independently admitted U.OutcomeSpec.

CC-A2.3-16 (OutcomeSpec is explicit and mode‑complete). promisedOutcomeSpecRef MUST be present and MUST reference an OutcomeSpec that declares mode in {WorkOnly, ResultOnly, Composite} and satisfies A.2.3:4.1.1 mode completeness:

  • WorkOnly → workSpec present, resultSpec absent
  • ResultOnly → resultSpec present, workSpec absent
  • Composite → both workSpec and resultSpec present

CC-A2.3-17 (OutcomeSpec predicates and delivery-work relations). To determine whether a U.Work occurrence participating in PromiseContentUse delivers the promised outcome, resolve OS as the A.2.3:4.1.1 OutcomeSpec from SC.promisedOutcomeSpecRef and test the following applicable conditions.

  • If OS.workSpec is present, the selected facts about the work occurrence satisfy OS.workSpec.workPredicateRef; when methodConstraintRef is present, the enacted method is compatible with that constraint.
  • If OS.resultSpec is present, the exact affected referent and selected post-work state satisfy OS.resultSpec.postConditionRef on its declared state plane. Any actual-change, production, delivery, acceptance, receiving-use, or optional mathematical Delta-lens claim remains separately governed.
  • A.10 evidence relations obtain between each relied-on satisfaction assertion and its supporting evidence epistemes.

Assert delivery only after these mode-specific conditions are established. Explicitly individuate PromisedOutcomeDeliveryRelation only when a downstream relation or claim must refer to its occurrence identity; otherwise retain the readable deliversPromisedOutcome(W, OS) assertion.

CC-A2.3-18 (Acceptance evaluation supports rather than constitutes fulfilment). Follow the §4.3 route: use A.13 to identify the actual evaluator and let A.15.1 admit the evaluation Work independently before saying that it enacts the Method selected in acceptanceSpec over the same Work facts and post-work states used to test delivery. Add F.6 only if this evaluation account must also state under which assignment the Work was performed. Cite a MethodDescription only when the claim depends on that exact edition.

The actual operation application carries its argument and result bindings. Any durable verdict episteme, any identity-inception claim, and evidence-use relations remain separate. Independently established A.10 evidence relations support reliance on the fulfilment assertion; they do not constitute fulfilment.

CC-A2.3-19 (OutcomeSpec ↔ unitOfDelivery coherence). If unitOfDelivery is present, its counting rule states a selectorRef that selects only work occurrences eligible to satisfy SC.promisedOutcomeSpecRef in the declared mode. For a cross-promise aggregate using one occurrence, the rule states either dedupeKeyRef or cites the counting-policy episteme that defines the counting rule. A selector may denote work occurrences filling FulfilmentWorkOccurrenceSlot in obtaining PromiseContentFulfilmentRelation occurrences; it does not count work for which fulfilment has not been established.

CC-A2.3-20 (Unit-of-delivery is computable from work facts). If unitOfDelivery is present, it follows A.2.3:4.1.2. For a pure count, identify its selector, quantity rule and any deduplication boundary. When the count depends on a measurement reading, identify its Method and required specification values; cite a MethodDescription only when the calculation or interpretation uses claims in that edition. Retain the evidence-admissibility conditions, evidence epistemes and evidence-use relations required for reliance on the count.

A.2.3:8 - Promise-content use, delivery, evaluation, and evidence

Keep PromiseContentUse, PromisedOutcomeDeliveryRelation, evaluation U.Work, the actual evaluation-operation application and result binding, any verdict episteme, and A.10 evidence relations separate. A direct relation may obtain even when the current episteme about it is unresolved; evidence supports the claim and does not become the relation.

A.2.3:8.1 - Core relations

PromiseContentUse : U.Relation. This direct use relation obtains between one delivery-work occurrence and one promise-content edition during one named promise-use interval; it makes no fulfilment claim.

PromiseContentUse : U.Relation
  DeliveryWorkOccurrenceSlot: U.Work, U.EntityRef
  PromiseContentSlot: U.PromiseContent, U.EpistemeRef
  PromiseUseIntervalSlot: temporal interval, byValue

Its occurrence key is <DeliveryWorkOccurrenceSlot, PromiseContentSlot, PromiseUseIntervalSlot>.

PromisedOutcomeDeliveryRelation : U.Relation. This derived relation obtains between one delivery-work occurrence and the A.2.3:4.1.1 OutcomeSpec resolved from the PromiseContentUse occurrence in which that work participates, when the conditions below hold.

PromisedOutcomeDeliveryRelation : U.Relation
  DeliveryWorkOccurrenceSlot: U.Work, U.EntityRef
  PromisedOutcomeSpecificationSlot: U.Episteme, U.EpistemeRef constrained to A.2.3:4.1.1 OutcomeSpec

The relation obtains only when one PromiseContentUse occurrence has the delivery Work and promise-content edition as participants, that edition resolves the same OutcomeSpec, and the mode-specific conditions hold. workSpec tests selected Work facts. resultSpec tests the exact affected referent and selected post-work state; any actual-change, production, delivery, acceptance, receiving-use, or optional Delta-lens claim remains separately governed.

Its occurrence key is <DeliveryWorkOccurrenceSlot, PromisedOutcomeSpecificationSlot>. The readable predicate is deliversPromisedOutcome(W, OS). An episteme may assert that this relation obtains and evidence may support the assertion; neither makes the underlying facts satisfy the specification.

Acceptance evaluation result. Follow the §4.3 performer-and-Work route before saying that the evaluation Work enacts the Method selected in acceptanceSpec. Add F.6 only if this result must also state under which assignment the evaluation was performed. A MethodDescription is cited only when its edition-specific claims are used. Keep the operation application, result binding, optional verdict episteme, any identity-inception claim and independently established evidence-use relations separate.

A.10’s descriptive evidence-provenance account cites the relevant facts and records reliance for the bounded assertion use; a passing disposition requires the evidence demanded by that claim and its direct acceptance rule. The account and verdict do not make fulfilment obtain.

PromiseContentFulfilmentRelation : U.Relation. This derived relation obtains between one delivery-work occurrence and one promise-content edition when the conditions below hold.

PromiseContentFulfilmentRelation : U.Relation
  FulfilmentWorkOccurrenceSlot: U.Work, U.EntityRef
  FulfilledPromiseContentSlot: U.PromiseContent, U.EpistemeRef

The semantic predicate for this relation is satisfied only when PromiseContentUse obtains for the same work and promise-content participants, PromisedOutcomeDeliveryRelation obtains for that work and the OutcomeSpec resolved from that promise content, and the acceptance predicate declared by acceptanceSpec is satisfied for the exact delivery-work facts, affected or delivered entities, post-work state, and any direct delivery or acceptance relation required by the criterion. PromiseContentFulfilmentRelation obtains for the declared participants when that semantic predicate is satisfied. Its occurrence key is <FulfilmentWorkOccurrenceSlot, FulfilledPromiseContentSlot>. The readable predicate is fulfilsPromiseContent(W, SC).

A later evaluation may change the supported assertion about whether the relation obtains; it does not change relation identity. When satisfaction of any required predicate is unresolved, no positive fulfilment assertion is available for reliance.

Expose a relation-occurrence reference only when a downstream relation or claim needs that identity, such as a unit-of-delivery selector or a fulfilment measure. Otherwise use the readable predicate.

Invariant: fulfilsPromiseContent(W, SC) implies that PromiseContentUse(W, SC, T) obtains for some declared interval T, that deliversPromisedOutcome(W, resolve(SC.promisedOutcomeSpecRef)) obtains, and that the acceptance criteria declared in SC.acceptanceSpec are satisfied. An exact evaluation-result episteme may support the corresponding assertion through independently established evidence-use relations cited in A.10’s descriptive account; neither that episteme nor the account becomes a fulfilment-relation participant.

Counting rule: Separate per-promise counts may each use the default one-unit-per-fulfilment rule. When aggregating counts across promise contents for the same Work occurrence, each applicable counting rule must state its dedupeKeyRef or cite its counting-policy episteme so the resulting quantities are not silently double counted.

A.2.3:8.2 - Promise-content delivery measures

Let W(SC, T) be the set of delivery-work occurrences for which PromiseContentUse obtains with SC during interval T. Let W✓(SC, T) be the subset for which PromiseContentFulfilmentRelation obtains with SC.

Until the membership judgements required by the selected counting rule and reporting window are resolved, withhold an exact delivered count and rejection rate. An unresolved fulfilment judgement is not a rejection.

  • Delivered units: delivered(SC, T) is computed from W✓(SC, T) using the A.2.3:4.1.2 counting rule. When unitOfDelivery is absent, delivered(SC, T) = |W✓(SC, T)|, one unit per obtaining fulfilment occurrence.
  • Rejection rate: for nonempty W(SC,T), rejectRate(SC, T) = 1 − |W✓(SC,T)| / |W(SC,T)| (declare handling of partial). When W(SC,T) is empty, declare a reporting rule before returning a value; this formula has a zero denominator.
  • Lead time: declare the characteristic definition and aggregation separately. The definition may use work duration or request-to-completion delta; the aggregation may use an average or named percentile.
  • Availability and uptime claims: select one declared characteristic instead of treating the labels as synonyms. Derive its observed characteristic value from selected work facts and telemetry observations through its C.16 measurement template, Gamma_time policy, and evidence relations. Identify any measurement Method that changes the interpretation; cite a U.MethodDescription only when this claim uses that edition’s claims.
  • Cost‑to‑serve: sum of Γ_work over W✓ per resource category (A.15.1).

Each resulting measurement-result claim is derived from selected facts about U.Work occurrences through its C.16 measurement template and named A.10 evidence relations. Make the measurement Method explicit when it affects interpretation; cite a U.MethodDescription only when the result claim depends on that edition’s claims. Resource and time actuals belong to the performed U.Work occurrences.

Aggregation across time uses the Gamma_time policy referenced by the named C.16 measurement template or acceptance specification; an unqualified KPI label does not select that policy.

When a measure needs a B.1.4 temporal-phase aggregation of one carrier, recover the selected policy—for example, union of covered intervals or their convex hull—together with carrier identity, time window, the coverage and overlap conditions consumed by that policy, and admissible use. An adequate ordinary account can state the result; use a separate ContextTemporalAggregation@Context record when the receiving use needs it. If those one-carrier conditions do not hold, this example is inapplicable; state the aggregation required and apply its defining rule. Union and convex hull are policy choices, not defaults; Gamma_time does not select either by itself.

A.2.3:9 - Common misclassification repairs

  • A microservice label is being used for the whole service claim. Use A.6.P:4.11a to recover whether the source word denotes service-provision Work, a Method, PromiseContent, provider participation, or a deployed process, component, endpoint, application, host, or cluster. Apply A.1 or A.1.SCR only when a repaired bearer claim depends on systemhood. Deployment and the label establish neither membership nor a delivery-system or access-point boundary; the consumer-facing outcome and acceptance claims remain in U.PromiseContent.
  • An API label is being used for the whole service claim. If the referent is an interface specification, use the episteme and U.MethodDescription only when A.3.2 admits it. If it is an addressable endpoint, recover that bearer through A.6.P:4.11a and apply A.1 or A.1.SCR only when a current claim depends on systemhood. Neither the API label nor addressability establishes membership, and neither referent is the promise-content episteme.
  • A process or procedure label is being used for the whole service claim. Recover the semantic way of doing as U.Method, its description as U.MethodDescription, planned work as U.WorkPlan, and performed occurrences as U.Work. Keep the promised outcome and acceptance claims in U.PromiseContent.
  • A ticket or case record is being used for the whole service claim. Recover its claim-bearing content as a ticket or case-description U.Episteme; keep the particular expression, any selected reusable publication form, and its physical or digital carrier separate. Relate that episteme to the named U.WorkPlan or U.Work occurrence it describes.
  • Cost or elapsed time is attached to the promise content. Keep resource and time actuals on the performed U.Work occurrence. Derive a measure over work occurrences participating in PromiseContentUse only through its declared characteristic, C.16 measurement template, named A.10 evidence relations, aggregation rule, and Gamma_time policy. Name the measurement Method when it affects interpretation; cite its U.MethodDescription only when this measurement claim depends on that edition’s claims.
  • Promise content is placed in a product or system breakdown. Keep the promise content as an episteme. The access and delivery systems may have parts and selected structures under A.22 and C.30; the promise-content episteme is not one of those parts.
  • A person or organization name is stored as the provider system-role kind. Identify the local provider system-role kind through providerSystemRoleKindRef. When an actual provider assignment is claimed, identify the person or organization, establish its A.1 System membership, and name one occurrence of a directly declared U.SystemRoleAssignment species with its explicit interval. A.2.1 requires an admitted holder U.System; describing the promise alone does not require creating an assignment.

A.2.3:10 - Existing promise-description repair applications

  1. Name the promises. Identify the consumer-facing promises needed by the project. Represent each as U.PromiseContent with effective reference scheme, promised outcome specification, acceptance specification, and claim scope, plus access specification and unit of delivery when current.

  2. Separate provider from promise content. Recover each provider, access point, or delivery bearer through A.6.P:4.11a. Apply A.1 or A.1.SCR only where a provider-assignment, access-point, delivery-system, performer, or other claim depends on systemhood. When an assignment is claimed, name its A.2.1 occurrence and declared species, with the provider System as holder.

  3. Relate promise content to delivery and evidence. Add PromiseContentUse for every delivery-work occurrence evaluated under the promise. Establish PromisedOutcomeDeliveryRelation only after work facts, affected or delivered entities, post-work states, and any direct delivery relation required by the resolved OutcomeSpec satisfy it; establish PromiseContentFulfilmentRelation only after those facts and states satisfy the declared acceptance criteria.

    Record the actual evaluation-operation result binding, any evaluation-result episteme, the evidence epistemes it cites, and the A.10 evidence relations separately.

  4. Define evaluation characteristics. Select the characteristics needed to evaluate the promise. Use an applicable §8.2 formula family—availability over a named window, lead time as a declared delta plus aggregation, rejection rate 1 − |W✓| / |W|, or cost-to-serve as summed Work resource use—or state a declared alternative. For each characteristic, name its scale, unit when applicable, C.16 measurement template, Gamma_time policy, and formula. A relied-on measured verdict additionally names its supporting evidence and direct evidence relations. Name a measurement Method when interpretation depends on it; cite a U.MethodDescription only when the evaluation claim depends on that edition’s claims.

  5. Bridge domain schemes. If a domain ontology distinguishes business, technical, or internal service kinds and relations, retain its reference scheme and name the exact obtaining F.9 Bridge for each selected sense and FPF counterpart. Add the separate C.2.1 claim that the Bridge suits the named use, then require the A.10 evidence-provenance relation with RelianceDisposition=pass. Use B.3 only for a named assurance claim. Keep PromiseContentUse, Work, delivery, fulfilment, result, evidence, assurance, and publication separate.

  6. Tidy relied-on language. Apply L-SERV and A.6.P:4.11a only when service or access-like wording hides a concrete subject, participant, predicate, kind, permission, Work occurrence, or next route in the current relied-on use. State what the wording denotes and use the pattern that defines or constrains that claim, or stop the use; use A.1 or A.1.SCR only when a recovered bearer claim depends on systemhood. Reserve U.PromiseContent for the consumer-facing promise content, and leave clear, quoted, historical, illustrative, and harmless ordinary wording outside this step.

A.2.3:10.1 - Consequences

ConsequenceBenefitCost or boundary
Promise content becomes explicitEvaluation work can apply declared acceptance criteria to delivery-work facts, affected or delivered entities, post-work states, and any direct delivery or acceptance relation required by the criterion.The promise-content declaration and its direct relations must keep provider, access point, method, ticket or case-description episteme, work occurrence, operation-result binding, evidence episteme, evidence relation, and evaluation-result episteme distinct.
Commitments stay distinctA promise-content clause can be referred to from U.Commitment.An individual duty still needs the A.2.8 direct predicate, actual duty bearer, exact constitutive rule, required instituting basis, and any current A.2.9 speech-act Work.
Promise use and evaluation become replayablePromiseContentUse obtains between the work occurrence and promise-content edition during the promise-use interval; delivery and fulfilment remain separate derived relations.A downstream fulfilment assertion retains the work, affected-subject and delivery facts, selected Delta expression when used, evaluation-operation result binding, named evidence epistemes and A.10 evidence relations, evaluation Method, its MethodDescription when the claim depends on that edition, and any evaluation-result episteme instead of treating the work occurrence or a dashboard as sufficient support.

A.2.3:10.2 - Rationale

Everyday “service” language is useful because one label can denote promise content, provider systems, access points, commitments, methods, work occurrences, and evidence epistemes. When those claims guide evaluation or work, FPF distinguishes the referents and states their direct relations. U.PromiseContent gives the promised-outcome side one stable episteme, A.6.P:4.11a recovers the referent intended by the service wording, and each named direct relation remains governed by its direct pattern.

The pattern keeps promise content in the episteme family because it is a clause or description whose outcome and acceptance predicates state conditions on delivery work, affected referents, and post-work states. A fulfilment assertion and the evidence relations supporting it remain distinct from those referents and from the world-side relations whose obtaining the assertion describes. The referents position of an A.2.8 commitment relation may contain it, an A.2.9 speech-act occurrence may communicate or institute that commitment, and A.6.C may unpack agreement or SLA wording carried by a publication, while gate and policy relations remain separate.

A.2.3:10.3 - SoTA-Echoing

The question is how to specify a reusable consumer-facing promise precisely enough to evaluate its fulfilment while keeping actual obligations and performance claims recoverable. A.2.3 selects a promise-content episteme containing the outcome and acceptance specifications. Actual commitment, delivery, measurement and verdict claims use their respective direct patterns. This is an FPF construction for that bounded question; its grounds come from distinct operational and ontological contributions.

Google’s Site Reliability Engineering (2016, chapter 4, “Service Level Terminology”) distinguishes a service-level indicator, its target, and an agreement with consequences for meeting or missing that target. The Site Reliability Workbook (2018, chapter 2, “What to Measure: Using SLIs”) further separates the user-relevant SLI specification from its measurement implementation: several implementations can assess the same specification with different coverage, accuracy and cost. A.2.3 adapts these distinctions when constructing acceptance criteria and selecting evaluation methods. The observed value, target and consequence remain separate claims. Service Level Objectives; Implementing SLOs.

A fuller alternative organizes the service account around commitments throughout offering, negotiation and delivery. The historical UFO-S treatment explicitly distinguishes offering and agreement descriptions from the relations they describe and from delivery actions (Nardi et al., 2015, §§4.1–4.3). The later Service Contract Ontology account likewise distinguishes an agreement description from the agreement relation (Griffo et al., 2023, §2.2). This approach supplies a richer account when the receiving question concerns agreement formation or change. For authoring one reusable clause, A.2.3 retains the narrower content object and connects it to separately established commitments through A.2.8. UFO-S; Modeling the dynamics of contractual relations.

Cloud storage makes the distinction consequential. Amazon’s S3 technical documentation states an annual durability design claim, while its SLA dated 28 November 2023 defines monthly availability using five-minute error rates, with account and storage-class scope, exclusions and credit conditions. These statements supply different criteria and grounds. A month of successful requests does not by itself establish the annual durability design claim. Likewise, a fulfilment judgement and eligibility for a service credit answer different questions. S3 data protection; S3 SLA, “Service Commitment”, “Credit Request and Payment Procedures” and “Definitions”.

In §5, the illustrative percentages therefore require their own declared characteristics, populations, windows and evaluation methods. C.16 supplies the measurement interpretation; A.10 carries the claim-specific grounds. If the promise concerns end-to-end retrieval but observations cover only requests reaching the backend, retain that coverage limitation when judging fulfilment.

If an actual obligation is claimed, establish its bearer and instituting basis under A.2.8. The cost of this separation is establishing those connections when the receiving use needs them. Revisit the source-based criteria when governing terms, measurement coverage or the intended use changes; a task whose primary result is agreement formation, amendment or remedy requires the corresponding fuller account.

A.2.3:11 - Relations

  • Builds on:

    • C.2.1 U.Episteme identity and reference scheme;
    • A.2 for local system-role kinds;
    • A.2.1 for directly declared U.SystemRoleAssignment species and occurrences;
    • A.2.2 qualified holder capability;
    • A.2.6 U.ClaimScope and U.WorkScope.

    A.1.1 is used only when an independently selected BoundedModelUseStructure changes one named receiving assertion or work use; the structure is not a promise-content constituent or generic relation participant.

  • Coordinates with:

    • A.3.1 U.Method;
    • A.3.2 U.MethodDescription;
    • A.15.1 U.Work;
    • A.6.1 for actual operation application and result binding;
    • A.15.PROD for current entity-identity-inception claims;
    • A.15.2 U.WorkPlan;
    • direct affected-subject, delivery, acceptance, and evaluation patterns;
    • A.10 for evidence relations and ordinary bounded reliance;
    • B.3 only when a named assurance claim is current;
    • A.2.8 for commitment;
    • A.2.9 for speech act;
    • A.6.P:4.11a for service-wording restoration;
    • F.9 for exact cross-scheme Bridge occurrences;
    • C.2.1 for the separate bounded-use suitability claim;
    • A.7 plus the direct publication pattern when specification use or publication is current.
  • Constrained by lexical rules: E.10 L‑SERV (service disambiguation); also L‑FUNC, L‑PROC, L‑SCHED, L‑ACT.

  • Informs: reporting and assurance patterns for measures over work occurrences participating in PromiseContentUse, plus directly governed catalog entries, exposure relations, charging relations, and entitlement relations when those claims are current.

A.2.3:12 - Didactic quick distinctions

Use §4.2 to distinguish promise content from neighboring objects, §4.3 for delivery and evaluation, and §8.1 for the relations needed by fulfilment claims. The worked cases in §5 show those distinctions across domains.

A.2.3:End

A.2.4 - Episteme Evidence-Use and Status-Use Relations

Type: Boundary and relation-use pattern Status: Stable Normativity: Normative

A.2.4:1 - Problem Frame

Use this pattern when an episteme, such as a report’s content, is being used as evidence, source, status bearer, assurance input, or causal-use input for a claim.

Use it when the working question is:

  • which episteme is being used;
  • for which claim or governed status it is being used;
  • which interpretation, scope and other §4.1 or §4.2 conditions change that use; and
  • whether the evidence-use or status-use relation is sufficiently specified for the intended reliance, or only enough for orientation, source-finding, a reversible probe, or a narrowed use.

Primary EntityOfConcern. The EntityOfConcern is the evidence-use relation or status-use relation around an episteme.

First useful move. Name the episteme and the claim or governed status for which it is being used. When the intended use needs more than this classification, use §4.6 to recover the additional claim and its direct governing pattern.

What goes wrong if missed. Producing or evaluating work is attributed to the document itself, a dataset is treated as if it were classified under a work-facing system-role kind, a dashboard status is used as permission, a proof is used outside its theory-version fence, or a simulation-only counterfactual output is relabelled as realized causal evidence.

What this buys. A first-use classification that identifies the episteme and its evidence-use or status-use relation. The further questions in §4.6 are answered through their direct patterns.

Not this pattern when. For a local result beyond evidence-use or status-use classification, use its defining pattern as §4.6 explains. In particular, A.13 identifies an actual performer and A.15.1 admits dated Work independently; add F.6 only when the result must also identify the assignment under which that Work was performed.

A.2.4:2 - Problem

Source text may use U.EvidenceRole or another evidence-like role label for a need: an episteme can be used as evidence for a claim under an effective source scheme and ClaimScope, with polarity, time, assurance use, weight, and provenance constraints. Treat those spellings as source-word triggers. The FPF repair states an evidence-use relation; it does not classify the episteme under a system-role kind or place it in a U.SystemRoleAssignment.

Unresolved role-shaped wording can lead to the following failures:

  1. Episteme-as-holder drift. A paper, proof, dataset, standard, or dashboard cell is treated as if it were classified under a work-facing system-role kind or filled the holder position of an assignment.
  2. Evidence-word ontology drift. ModelFitEvidenceRole, MeasurementEvidenceRole, or AxiomaticProofRole is treated as a kind merely because the source label ends in Role, instead of being resolved to an evidence-use relation classification or local evidence-use label.
  3. Claim relation collapse. Target claim, grounding holon, claim scope, polarity, relevance window, assurance use, weight model, and provenance constraints are hidden behind one source label ending in Role.
  4. Evidence and status collapse. A status badge, standard reference, approval-looking display, publication face, or requirement source is treated as evidence, status assertion, gate passage, permission, and assurance at once.
  5. Work confusion. The work that produced an episteme and the later use of that episteme as evidence are folded into one relation.
  6. Causal-use laundering. Observational association, intervention, realized counterfactual sample, identified counterfactual estimate, and simulation-only output are relabelled by evidence-wording instead of being governed by C.28.
  7. Cross-local leakage. Evidence accepted under one source scheme, ClaimScope, and use is reused under another without recovering the changed meaning, source currentness, reliance, or assurance-use conditions and any actual F.9 relation.

A.2.4:3 - Forces

ForceTension this pattern resolves
Episteme identity versus episteme useThe same episteme can be used for several claims while retaining its identity.
Compact evidence statement versus full evidence graphUsers need a small evidence-use statement first; A.10 remains the pattern for full evidence-provenance graph detail.
Formal proof versus empirical evidenceA proof can be stable inside one theory version; empirical evidence usually needs relevance windows, freshness, and provenance constraints.
Status display versus status assertionA visible badge, cell, or label can cue status but does not by itself create permission, gate passage, assurance, or work evidence.
Local acceptance versus cross-local reuseEvidence and status use are bounded by their source scheme, ClaimScope, window, and intended use; reuse recovers the changed values and any required F.9, source-currentness, publication-use, reliance, or assurance-use relation.
Causal evidence classes versus ordinary evidence relationCausal-use evidence classes need C.28; A.2.4 keeps the evidence-use relation from being misread as a system-role kind or assignment.

A.2.4:4 - Solution

Do not create or use source spelling U.EvidenceRole as a durable FPF kind. Do not place an episteme in U.SystemRoleAssignment merely because it is used as evidence, source, standard, requirement, definition, explanation, publication, status bearer, or assurance input.

Use direct relation patterns instead:

Current claimUse
one episteme is used as evidence for one claim, effect, or bounded reliance useThe evidence-use relation under A.2.4:4.1; use A.10 when its source-to-use account remains implicit or must be replayable.
evidence is used by an actual named assurance claimB.3, with the source/provenance and use grounds required by that claim; reuse an adequate account, or use A.10 when it needs recovery or replay. A.2.4 supplies the first-use classification.
the episteme itself is being identified, versioned, or distinguished from publication faces and publication carriersC.2.1
the use is causal, counterfactual, intervention-facing, or simulation-onlyC.28, with the A.10 descriptive source/provenance path and the A.2.4 first-use classification as inputs
the source says “status”, “approved”, “current”, “valid”, “stale”, “ready”, or another status-like valueF.10 or the direct status, gate, permission, safety, or release pattern; A.10 for bounded reliance and B.3 for an actual named assurance claim
the source is a publication face, view, description, source citation, standard, requirement, explanation, or specification-use caseE.17, E.17.0, E.17.2, E.17.EFP, E.10.D2, or the direct source-use pattern
an admitted system is classified under an exact local system-role kind, holds an obtaining assignment, and performs or prepares WorkA.2, A.2.1, A.15, A.15.1, or A.15.2

A.2.4:4.0 - First-use split

An A.2.4 assertion answers only: which episteme is classified for which evidence-use or status-use, under which effective source scheme when interpretation matters, with which ClaimScope, polarity or status value, and window.

When source production, evaluation, a local result, result episteme, provenance, currentness, receiving work, reliance, or assurance matters, the assertion names the direct object and the pattern passage that defines or constrains its claim; it does not re-express them as slots of a generic evidence result.

A.2.4:4.1 - Evidence-Use Relation Slots

An evidence-use relation obtains around an episteme and a claim or effect.

SlotKindValueKindIdentity and currentness discipline
EvidenceEpistemeSlotexact U.Episteme classified for evidence useIdentity of the classified episteme.
EvidenceTargetClaimSlotclaim or theory statementIdentity slot whenever the relation is claim-bound; a missing value blocks claim-bound evidence use.
EvidenceClaimGroundingHolonSlotexact U.Holon that participates in an obtaining C.2.1 EpistemeEmpiricalGroundingRelation covering the target claimIdentity or currentness-required when changing the grounding holon changes the evidence relation or the claim being evidenced.
EvidenceClaimScopeSlotclaim-scope value governed by B.3, A.10, C.28, or a direct evidence patternIdentity qualifier when changing scope changes the relation; currentness-required when scope changes admissible use.
EvidencePolaritySlotevidential polarity value such as supports, refutes, constrains, or neutral when that value set is currentIdentity qualifier when changing polarity changes which evidence-use relation is asserted.
EvidenceRelevanceWindowSlottemporal relevance window, theory-version fence, freshness policy, or decay policyIdentity or currentness-required when time, version, or freshness changes the evidence use; consideration slot for formal uses where the theory-version fence already carries the boundary.
EvidenceAssuranceUseSlotthe named bounded reliance or assurance-facing useRecords the intended receiving use only; A.10 is the pattern for the local disposition and B.3 is the pattern for any assurance result.
EvidenceWeightModelSlotweight, confidence, reliability, likelihood, or scoring model referenceConsideration slot; currentness-required when weighted evidence is claimed.
EvidenceProvenanceConstraintSlotrefs to the exact A.10/G.6 source and provenance accountCurrentness-required when provenance or a rival explanation decides admissible use.

These SlotKinds are evidence-use relation positions.

A.2.4:4.2 - Status-Use Relation Slots

A status-use relation is a relation around a bearer, status value, scope, window, source, and use.

SlotKindValueKindUse
StatusBearerSlotepisteme, claim, method description, publication, system-role-assignment occurrence, work occurrence, clause, gate record, or another governed bearer admitted by the direct patternThe value whose status is being asserted or read.
StatusTargetSlotclaim, method, episteme, publication, exact domain result or result episteme, clause, bearer, or another governed status targetRequired when the status is not simply about the bearer itself; the direct status or result pattern defines it.
StatusScopeSlotclaim scope, admission scope, requirement scope, or use scopeCurrentness-required when scope changes the status assertion.
StatusValueSlotstatus value governed by F.10 or a direct patternRequired for a status assertion.
StatusWindowSlottemporal validity window, freshness policy, or source/status windowRequired for time-sensitive use; G.11 is the pattern for an edition-currentness result when currentness is being judged.
StatusUseSlotgate, assurance, admission, source-currentness, work-plan readiness, or another exact receiving useIdentifies the intended use; its receiving work, direct relation, and result remain with their governors.
StatusProvenanceConstraintSlotsource order, authority source, publication, proof, verification, register, or provenance constraintCurrentness-required when provenance decides status use.

These names are repair vocabulary for status-use relations. Durable status families remain governed by F.10 or a direct status pattern.

A.2.4:4.3 - Minimal Evidence-Use Statement

Write only fields that decide this first use:

Episteme evidence-use statement:
  EvidenceEpisteme:
  EffectiveReferenceScheme:              # when interpretation changes the use
  EvidenceTargetClaim:
  ClaimScopeAndPolarity:
  RelevanceWindow:
  DirectClaimOrResultGovernor:
  ProducingOrEvaluatingWorkRef:        # when current
  DomainLocalResultAndEpistemeRef:     # when current
  ProvenancePathRef:                   # A.10/G.6 when current
  CurrentnessRef:                      # G.11 when current
  ReceivingWorkAndUseRelationRef:      # when actual use is claimed
  RelianceDispositionRef:              # A.10 when reliance is judged

A.2.4:4.4 - Minimal Status-Use Statement

Episteme status-use statement:
  StatusBearer:
  StatusTarget:
  StatusScope:
  StatusValue:
  StatusWindow:
  DirectStatusGovernor:
  SourceAndProvenanceRef:
  CurrentnessRef:                      # G.11 when current
  ReceivingWorkAndUseRelationRef:      # when actual use is claimed
  RelianceDispositionRef:              # A.10 when reliance is judged

A.2.4 does not fill a missing direct governor with a generic status, evidence, work-result, or evaluation-result relation.

A.2.4:4.5 - Formal, empirical, causal, and status first uses

Source labels such as AxiomaticProofRole, ObservationEvidenceRole, MeasurementEvidenceRole, ModelFitEvidenceRole, CalibrationEvidenceRole, and BenchmarkEvidenceRole are wording triggers. Recover the first-use classification or relation; the labels are neither local system-role kinds nor result kinds by spelling.

Formal line. Classify the proof, derivation, counterexample, theory note, or proof-result episteme against the named theorem and theory-version fence. The formal pattern contains the defining content for entailment, refutation, malformed-proof, timeout, or checker-failure results; C.2.1 is the pattern for the episteme that states the result.

When proof-checking is asserted as dated U.Work, use A.13 to identify the actual performer and A.15.1 to admit the occurrence independently. If the proof-checking account must also identify the assignment under which the Work was performed, check that relation separately through F.6. Keep the Method and bindings separate. A.2.4 states only how the episteme is used.

Empirical and measurement line. Classify the dataset, observation episteme, C.16 measurement-result episteme, replication result, calibration result, benchmark result, or model-fit result episteme against one named claim.

For any producing or evaluating Work, use A.13 to identify the actual performer and A.15.1 to admit the dated occurrence independently. If that account must also identify the assignment under which the Work was performed, check it separately through F.6. Keep direct relations or A.6.1 bindings separate. Each local result remains with C.16 or its exact domain governor; A.10/G.6 retain provenance; G.11 retains currentness.

Causal line. C.28 is the pattern for the causal-use question, estimand, separate evidence/identification/estimate/sampling/simulation components, realizability, support result, supported use, and unsupported use. A.2.4 may classify the C.2.1 episteme used at first contact; evidence wording cannot turn simulator output into interventional or realized-counterfactual evidence.

Status line. A visible status carrier is classified separately from the governed status assertion. F.10 or the status pattern contains the defining content for the status value, G.11 is the pattern for edition currentness, and a gate, permission, commitment, system-role-kind, assignment, Work, assurance, or decision pattern contains the defining content for its own result. Display presence establishes none of them.

A.2.4:4.6 - Work, result, provenance, and receiving-use boundary

Keep these objects separately recoverable whenever they are current:

  1. the classified episteme and the exact claim or status for which it is used;
  2. each actual performer identified through A.13; the dated source-producing or evaluating Work independently admitted through A.15.1; a separate F.6 check when the result must also identify the assignment under which that Work was performed; and separate Method, resources, and actual direct/A.6.1 bindings;
  3. the domain-local result and its direct governor;
  4. the distinct C.2.1 episteme that states that result;
  5. the A.10/G.6 source and provenance path;
  6. the G.11 currentness result when currentness affects use;
  7. the receiving dated work and exact premise, reference, decision-use, operation-argument, or other direct use relation; and
  8. the local A.10 RelianceDisposition.

Use B.3 only when an actual named assurance claim is being made. If a direct domain rule requires one for the intended use, state that claim and its required basis first.

Use A.2.4 only to classify evidence use or status use around the episteme.

When episteme inception through work matters, A.15.PROD supplies the local entity-identity inception claim.

A.2.4:4.7 - First-use boundary and reopen condition

A.2.4 classifies the episteme’s first evidence or status use. It may identify the episteme, target claim or status, effective source scheme when material, ClaimScope, polarity or value, window, intended use, and applicable definition or constraint. Questions about source Work, a local result, provenance, currentness, assurance or another receiving claim remain governed by their direct patterns.

Open only the subject question whose predicate decides the use:

  • A.13 for the actual performer;
  • A.15.1 for independent Work admission;
  • F.6 when the result must also identify the assignment under which that Work was performed;
  • A.6.1 for actual bindings;
  • the domain result predicate plus C.2.1 for result content;
  • A.10/G.6 for provenance and bounded reliance;
  • G.11 for currentness;
  • B.3 for assurance;
  • C.28 for causal use;
  • F.10 for a status family;
  • E.17 for publication.

Reopen the A.2.4 classification when the episteme, target claim/status, scope, polarity/value, window, or intended use changes.

A.2.4:5 - Archetypal Grounding

A.2.4:5.1 - Proof result used as evidence

ProofResult-12 is a C.2.1 episteme stating an entailment under GraphTheory_v3.1. Dated checker work, its method, theory and proof bindings, and the formal entailment result are recovered under their subject patterns. A.2.4 classifies the episteme as supporting Theorem-12 inside the theory-version fence. A.10 records source/provenance; in later review work, a reviewer uses the episteme through a premise relation. Timeout or checker failure would remain distinct from refutation.

A.2.4:5.2 - Measurement result used in acceptance

PressureResult-E is the C.16 measurement-result episteme for gas pressure at port P. It states the measurand, Characteristic, Scale, value, uncertainty, model, calibration basis, time stance, and dated measurement work. A.2.4 classifies it as evidence used for the pressure-limit claim.

In separate evaluation work, an evaluator applies the G.4 clause through A.6.1 bindings and obtains unknown; a different C.2.1 episteme states that verdict. A.10/G.6 preserve provenance, G.11 currentness, and in later C.11 decision work, a decision-maker relies on the verdict episteme. Raw detector output, indication, pressure state, measurement result, verdict, and decision remain distinct.

A.2.4:5.3 - Dashboard status cell

A release dashboard displays Ready. Recover the claim-bearing content of the cell and classify its episteme’s status use separately from the display carrier. The source register, scope, window, status value, G.11 currentness, and provenance must be recoverable.

A.21 governs any gate decision, C.11 any release decision, A.2.8.PER any permission, A.15.1 any performed Work, and B.3 any assurance claim. The cell’s presence alone establishes none of them; its content may contribute to the argument under the applicable rule.

A.2.4:5.4 - Simulation-only output

A simulation-output episteme is classified for one bounded C.28 claim. C.28 retains simulationResultRef, model assumptions, validation, the causal-use support result, supported use, and unsupported use. A.2.4 cannot relabel the episteme as realized-counterfactual or interventional evidence; simulation Work, simulator result, result episteme, provenance, and later reliance remain separate.

A.2.4:6 - Bias-Annotation

An evidence or status label can prompt readers to assume that the needed relation already obtains. Recover the episteme and its evidence-use or status-use relation before relying on that label. Apply the direct source, causal, or assurance rule when the receiving claim requires it.

A.2.4:7 - Conformance Checklist

CheckPass condition
CC-A2.4-1 First-use objectOne exact episteme and one target claim or governed status assertion are named.
CC-A2.4-2 Admitted jobThe statement is only an evidence-use or status-use classification; no U.EvidenceRole, episteme-as-system-role-kind classification, assignment holder, or generic result kind is created.
CC-A2.4-3 Scope and interpretationEffective source scheme when material, grounding holon, claim or status scope, polarity or value, and relevance or status window are explicit when they change the use.
CC-A2.4-4 WorkFor any source-producing, measurement, proof-checking, evaluation, transformation, or receiving Work, A.13 identifies the actual performer and A.15.1 independently admits the dated occurrence. Add F.6 only when the result must also identify the assignment under which that Work was performed. The Method and direct-relation or A.6.1 bindings remain separate.
CC-A2.4-5 Local resultWhen a domain-local result is claimed, identify the pattern passage that defines or constrains it.
CC-A2.4-6 Result epistemeThe C.2.1 episteme that states the local result remains distinct from that result, carrier, and work.
CC-A2.4-7 Provenance/currentnessUse A.10 and G.6 for source recovery and provenance; use G.11 for currentness when it affects use.
CC-A2.4-8 Receiving useWhen a particular receiving Work or receiving-use relation is asserted, name that Work and relation. Citation or availability alone does not establish actual use.
CC-A2.4-9 Reliance/assuranceA.10 defines the bounded RelianceDisposition. Use B.3 only when an actual named assurance claim is being made. If a direct domain rule requires one for the intended use, state that claim and its required basis first.
CC-A2.4-10 Publication/displayPublication face, generated explanation, credential view, evidence profile, ledger edge, or dashboard cell does not establish status, result, work, gate, permission, or decision by presence.
CC-A2.4-11 Causal boundaryC.28 is the pattern for causal-support components and results; source wording cannot promote simulation or observational evidence.

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

Source wordingFailureRepair
“The report has EvidenceRole for Claim A.”Treats a source label as a system-role kind or assignment without recovering the actual relation.Use an evidence-use relation with EvidenceEpistemeSlot, EvidenceTargetClaimSlot, scope, polarity, window, and provenance constraints when current.
“Dataset X proves safety.”Treats dataset presence as proof, assurance, and safety claim.Recover its claim-bearing content and use A.10 for the evidence relation. Use B.3 for an actual safety-assurance claim and state the supported use and any consequential limit.
“The standard has normative role.”Role word hides standard-use, requirement-use, source-use, or publication-use.Recover the relation governed by the current claim and apply E.10.D2, E.17, F.10, or the direct requirement pattern.
“The badge is current, so release is allowed.”Status display becomes gate passage or permission.Use status-use relation plus gate or release subject pattern; dashboard display alone is not a decision.
“Simulation output is counterfactual evidence.”Simulator output is promoted to realized or interventional causal evidence.Use C.28; keep simulationResultRef, model assumptions, validation, and bounded supported/unsupported use distinct from empirical, identification, estimate, and direct-sampling results.
“The work run is the evidence role.”Work occurrence, actual performer, assignment check, local result, result episteme, and later evidence-use are collapsed.Use A.13 for the actual performer and A.15.1 for independent admission of the dated Work. Add F.6 only if the use must also identify the assignment under which the Work was performed. Use A.6.1 for actual bindings, the domain pattern for the local result, C.2.1 for its episteme, A.10/G.6 for provenance, and A.2.4 only for first-use classification.

A.2.4:9 - Consequences

Admitted systems may be classified under exact local system-role kinds and may hold obtaining system-role assignments; epistemes are instead used through direct evidence-use, status-use, source-use, publication-use, requirement-use, definition-use, explanation-use, assurance-use, or causal-use relations.

The cost is explicit relation recovery. A phrase such as “evidence role”, “status role”, “standard role”, “proof role”, or “benchmark role” no longer closes the claim. The user needs to recover which episteme, claim, scope, status, time window, provenance constraint, and direct pattern are current.

The payoff is that one episteme can be reused across many claims. Each use can have a different target claim, grounding holon, scope, polarity, relevance window, assurance use, weight model, or provenance constraint without multiplying system-role kinds.

A.2.4:10 - Rationale

An episteme may be used for several claims or governed statuses. State each evidence-use or status-use relation separately. The classification points outward to, and never replaces, performed Work, the domain-local result, the C.2.1 result episteme, provenance, currentness, receiving reliance, or assurance.

A.2.4:10.1 - SoTA-Echoing

SourcePractical distinctionLimit
C2PA Content Credentials 2.4, April 2026, W3C Verifiable Credentials Data Model 2.0, Recommendation 15 May 2025, SLSA 1.2, and in-toto Attestation Framework 1.2 with Statement/v1Distinguish subject, issuer or producer, verifier, proof or status, time, inputs, and relying context. Use A.10/G.6 for source and provenance and G.11 for currentness; first-use classification remains separate from those questions.When the receiving claim goes beyond what the credential or provenance check establishes, obtain its required grounds under the direct pattern.
ISO/IEC/IEEE 15026-2:2022, Systems and software assurance — Part 2: Assurance caseCited evidence is distinct from the structure and maintenance of an assurance case. For an actual named assurance claim, use B.3 after A.10 source/provenance and bounded-reliance recovery.Citation alone does not establish support for the assurance claim.
Hernán and Robins, Causal Inference: What If, 2020 book, online 26 April 2024 editionDistinguish observational data, interventions, target-trial questions, counterfactual outcomes and estimands, identification assumptions, and realized results. C.28 governs the evidence class and causal-use result.A causal label, model, target-trial analogy, or simulated counterfactual does not establish intervention, identification, realized outcome, or a causal-use verdict.
Guizzardi et al., UFO: Unified Foundational Ontology, Applied Ontology 17(1), 2022; related implementation accounts: gUFO usage specification and Almeida et al., gUFO: A Gentle Foundational Ontology for Semantic Web Knowledge Graphs, 2026 preprintDistinguish kinds and types, roles, relators and relations, events, and situations. In FPF, evidence-use and status-use SlotKinds name relation positions; they do not classify an episteme under a work-facing system-role kind or make it an assignment holder.External Role, Relator, Situation, or OWL class vocabulary does not import a new FPF kind, replace an obtaining direct relation, or authorize an episteme system-role assignment.

A.2.4:11 - Relations

  • Builds on: A.2 for exact local system-role kinds, A.2.1 for U.SystemRoleAssignment, A.6.5 for SlotSpec discipline, and C.2.1 for episteme identity and its distinct constitution, empirical-grounding, and edition relations.
  • Coordinates with:
    • A.10 and G.6 for descriptive source/provenance paths;
    • G.11 for currentness;
    • B.3 for assurance;
    • C.28 for causal-use results;
    • F.10 for status families;
    • C.2.1 for result epistemes;
    • domain patterns for local results;
    • E.17/E.10.D2 for publication, view, explanation, and description-use cases.
  • Separates from:
    • A.13 for actual performers;
    • A.15.1 for independently admitted performed Work;
    • F.6 when a receiving result must also identify the assignment under which that Work was performed;
    • A.6.1 for actual bindings;
    • A.15.PROD for episteme inception when current;
    • the patterns that define or constrain the domain-local results;
    • receiving-work patterns for actual later use.
  • Precision-restoration route: When source wording says “evidence role”, “status role”, “standard role”, or another role-shaped phrase around an episteme, use E.10.ROLE to recover the governed object or relation. Use A.6.RSIR only when the result is a relation participant meaning, declaration place, interface place, or representation position; use E.10.ARCH for the wider ontology-first repair architecture.

A.2.4:12 - Lowering, Repair, and Refresh

Lower an attempted A.2.4 use when the episteme is known but the target claim, scope, polarity, status value, time window, or provenance constraints are not recoverable. The lowered result may be source-finding, orientation, an evidence-needed note, a status-source request, or a narrowed reliance use.

When the intended answer goes beyond evidence-use or status-use classification, obtain that answer through the direct pattern in §4.6–§4.7.

Reconsider the classification when the episteme, target claim, grounding holon, scope, polarity or status value, window, or intended use changes. Reopen the affected reliance question when a change in source currentness, proof checking, measurement, MethodDescription, or assurance basis could alter that use.

A.2.4:End

A.2.5 - SystemRoleAssignmentStateRelation - Assignment-State Recognition for Work Admission

Type: Definitional (D) Status: Stable Normativity: Normative unless marked informative

A.2.5:0 - Use This When

Plain designations. Say “this assignment to a system role satisfies this state condition” for the relation and “state condition for an assignment to a system role” for the predicate.

Use this pattern when one assignment to a system role already obtains, but a method step, Work occurrence, incompatibility check, or operational gate depends on that assignment satisfying a particular condition during a particular window.

Start with the practical question: Does this assignment satisfy this state condition throughout the window that matters now? The first useful result identifies an obtaining SystemRoleAssignmentStateRelation occurrence or establishes its absence; if neither is established, keep that determination unresolved. Add an assertion and evidence-use relation only when a later decision must rely on that result.

Typical working moments include these:

  • a calibrated inspection robot is assigned to InspectorSystemRole, but inspection Work should start only while calibration, synchronization, and operating-envelope conditions hold;
  • an incident commander remains on call, yet a conflict or fatigue condition may make that assignment non-admitting for one response window;
  • a method description declares a state condition for an assignment to a system role, while the current assignment has not yet been tested against it;
  • two assignments are incompatible only while both satisfy the conditions that make them work-admitting; and
  • a model-use structure, KindSignature, reference scheme, or bridge changes the meaning of one predicate clause and must therefore be included in that predicate’s semantic basis.

Primary EntityOfConcern. The EntityOfConcern is one obtaining occurrence of SystemRoleAssignmentStateRelation. This direct relation kind is admitted under U.Relation. The occurrence has two participants: one obtaining U.SystemRoleAssignment occurrence and one by-value SystemRoleAssignmentStatePredicate. Its maximal continuous temporal extent comes from uninterrupted predicate truth while that assignment obtains.

Primary working reader. The intended reader defines or checks the state conditions that the next operation requires of an assignment.

What goes wrong if missed. A system-role label is treated as current readiness. A dashboard value is substituted for the world-side state relation. Missing evidence is read as proof that the predicate is false. Capability is mistaken for Work admission. A state-machine diagram is used as both the ontology and the method order.

What this buys. The reader can identify repeated state episodes inside one continuing assignment, keep evidence and world-side obtaining distinct, combine simultaneous conditions, and pass the state claim to the direct pattern governing the next decision or Work use.

Not this pattern when. Use A.2 and C.3 for the local system-role kind, A.2.1 for the assignment and its holder, A.2.2 for capability and operating envelope, A.2.7 for relations among system-role kinds, and A.15.1 for Work that occurred. Use A.2.4 or A.10 when the current object is the evidence-use relation rather than the assignment-state relation. A displayed status, credential entry, gate decision, or organizational position keeps its own direct pattern.

A.2.5:0.1 - Kind Settlement

SystemRoleAssignmentStateRelation is admitted as a direct relation kind under U.Relation.

SystemRoleAssignmentStatePredicate is a local ValueKind declared by this pattern, not another root U-kind. One predicate value is identified by:

  1. the local system-role kind for whose assignments it is defined;
  2. normalized truth-condition ClaimGraph clauses naming the governed qualities or relations tested;
  3. its temporal reading;
  4. its applicability conditions; and
  5. the semantic basis whose edition changes meaning, including a KindSignature, reference scheme, bridge, or model-use structure only when the clauses depend on it.

A displayed name such as InspectionReady can designate the predicate. The name alone does not identify it. Ready@InspectorSystemRole and Ready@ApproverSystemRole are different predicate values unless one separately declared predicate has one common domain and identical clauses, temporal reading, applicability, and semantic basis.

A compatible semantic-basis edition preserves the predicate only through an explicit predicate-continuity decision showing that those identity-bearing facts continue. A changed system-role kind, truth clause, temporal reading, applicability condition, or meaning-bearing semantic basis yields another predicate.

A SystemRoleAssignmentStateAssertion is a U.Episteme whose EntityOfConcern is the exact assignment or an explicitly individuated state-relation occurrence, according to the claim. Its ClaimGraph names the predicate, direct claim family, and assertionPolarity: affirmative | negative. An affirmative claim may state a known actual extent only after A.2.5 independently establishes obtaining. A receiving evaluation may separately state its target window.

Supported, refuted, or unresolved reliance belongs to A.10 or a separately constituted evaluation result or reliance assertion. Assertion, reliance posture, evidence episteme, evidence-use relation, and world-side occurrence remain different objects.

A representation episteme may describe predicates, possible configurations, and possible changes. A statechart or state-machine display is a mathematical or representational lens.

A.2.5:1 - Problem Frame

An occurrence of a declared U.SystemRoleAssignment species assigns an admitted System to one local system-role kind and supplies any other values required by that species. It does not establish that the assignment satisfies a condition needed by a Method or Work claim in the evaluated interval.

Robot-7 can remain under InspectionShiftAssignment-17 throughout an eight-hour shift while calibration expires at noon. The assignment continues. The InspectionReady state occurrence ends when its predicate ceases to hold. Recalibration can start another occurrence under the same assignment without creating another assignment.

The same distinction appears in social and computational Work. An on-call person can remain assigned while conflicted or fatigued. A service can remain assigned to ApproverSystemRole while one predicate concerns fulfilment approval and another concerns payment authorization. A tool-using agent can expose a capability while a concrete action remains inadmissible for the current task and inputs.

The engineering problem is therefore to identify the assignment, predicate, and interval; distinguish affirmative or negative assertion polarity from reliance posture; recognize an occurrence only while the direct predicate is true; and connect an assertion to evidence only when a consequence-bearing use needs that support.

A.2.5:2 - Problem

Without a direct assignment-state relation ontology, six recurring failures appear.

  1. Assignment becomes readiness. Holding an assignment is treated as satisfying every state precondition of every method that names its system-role kind.
  2. State label hides the predicate. Ready, Approved, or Active travels between domains although its truth conditions differ.
  3. Evidence becomes the state. An evidence or display episteme is treated as the world-side relation.
  4. Missing evidence becomes falsehood. An unrecovered or stale evidence path is taken as proof that the predicate does not obtain.
  5. Capability becomes admission. A system’s ability to perform an operation is overread as current admission of this concrete method or Work claim.
  6. State notation becomes method order. A transition arrow is treated as the Work that changes the state, although Method, Work, transformation, and state-change claim have different ontics.

A.2.5:3 - Forces

ForceTension
Lightweight assertion vs reusable identityOrdinary Work needs a short state sentence; later admission, history, or comparison may need one individuated relation occurrence.
World-side obtaining vs evidence-backed relianceA predicate can hold before anyone measures it, while consequence-bearing use needs a current assertion and evidence relation.
Simultaneous predicates vs single-state notationCalibrated, Synchronized, and InRange may all hold together; a finite-state machine may still help with one narrower exclusive configuration.
Stable assignment vs changing stateOne assignment can contain several state episodes without being recreated at each change.
Predicate identity vs permanent interpretation participantsMeaning-bearing signatures, schemes, bridges, or model-use structures may distinguish predicate values; irrelevant editions must not become participants of every assignment or state relation.
Capability vs action admissionAbility is a neighboring claim; current Work admission depends on the exact state predicate and the direct consumer’s rule.

A.2.5:4 - Solution

Start from a readable assertion:

Robot-7’s current assignment to InspectorSystemRole satisfies InspectionReady throughout the inspection window.

When a receiving use needs reusable participant typing, use the declared RelationSignature. When it needs occurrence identity, apply the world-side identity rule in section 4.3.

A.2.5:4.1 - Direct Relation Declaration

This pattern defines the RelationSignature for SystemRoleAssignmentStateRelation:

SlotKindValueKindrefModeMeaning
SystemRoleAssignmentSlotU.SystemRoleAssignmentU.RelationRef constrained to U.SystemRoleAssignmentThe exact assignment occurrence being evaluated; its declared species remains recoverable.
StatePredicateSlotSystemRoleAssignmentStatePredicateByValueThe exact predicate value identified under section 0.1.

These are the only two generic participants. SystemRoleAssignmentStateRelation obtains exactly while the assignment obtains and the fixed by-value predicate is true under its temporal reading. Its actual extent is the maximal continuous interval of that obtaining.

An affirmative assertion or occurrence description may state the known extent as systemRoleAssignmentStateExtent only for an independently established occurrence; a receiving evaluation may state a separate declaredSystemRoleAssignmentStateEvaluationWindow. Neither temporal value, assertion polarity, reliance posture, taxonomy episteme, reference scheme, bridge, nor model-use structure is another relation participant.

A relied-on assertion uses a direct evidence-use relation. Another world-side occurrence affects predicate truth only when a truth-condition clause cites that occurrence through its subject pattern.

A.2.5:4.2 - Predicate Meaning and Semantic Basis

One SystemRoleAssignmentStatePredicate value names:

  • the local system-role kind for whose assignment species the predicate is defined;
  • normalized truth-condition ClaimGraph clauses, each naming its governed quality or relation, actual participants, and subject pattern;
  • the temporal reading, such as truth at an instant, throughout a receiving-use window, or for a declared tolerated portion of that window;
  • applicability conditions; and
  • only the semantic-basis references whose editions can change those clauses or their interpretation.

This content defines one predicate value. The direct qualities and relations keep their own kinds and subject patterns.

Predicates need not be mutually exclusive. Calibrated, Synchronized, and InRange can hold simultaneously; InspectionReady may be a conjunction over them. Use an exclusive state configuration only when the subject-domain model needs one.

A shared label does not establish shared meaning. Cross-context reuse needs the same predicate identity or an explicit comparison or bridge stating which truth and admission effects are preserved. A bridge or scheme enters the predicate’s semantic basis only when the predicate clauses depend on it.

A.2.5:4.3 - Occurrence Identity and Repeated Episodes

Do not replace the identity rule with a tuple key. One SystemRoleAssignmentStateRelation occurrence begins when one fixed assignment starts satisfying one fixed predicate. It continues while the assignment obtains and the predicate remains true without interruption. It ends when the assignment ceases, the predicate becomes false, or either participant changes. A later return to truth starts another occurrence.

An affirmative assertion or occurrence description may state the currently known systemRoleAssignmentStateExtent. Recording an end boundary for a previously open extent refines the description of the same occurrence when assignment obtaining and predicate truth were uninterrupted. A demonstrated predicate gap separates occurrences. Thus true → false → true produces two state occurrences inside one continuing assignment.

A later correction of an assertion interval, changed evidence relation, assertion edition, dashboard display, or publication creates no world-side occurrence while truth was uninterrupted. An evidence gap gives the receiving use unresolved reliance; it does not demonstrate a gap in predicate truth or add a third assertion polarity.

A.2.5:4.4 - Assertion and Evidence Use

For a relied-on state claim, keep this order:

  1. name the exact U.SystemRoleAssignment, by-value SystemRoleAssignmentStatePredicate, direct claim family, and affirmative or negative assertion polarity;
  2. when A.2.5 independently establishes obtaining and the receiving use needs occurrence identity, individuate the occurrence under section 4.3;
  3. state a SystemRoleAssignmentStateAssertion : U.Episteme whose ClaimGraph carries the predicate, direct claim-family reference, polarity, known systemRoleAssignmentStateExtent only for an affirmative claim about an established occurrence, and any separate declaredSystemRoleAssignmentStateEvaluationWindow;
  4. include a meaning-bearing semantic-basis reference in the predicate identity, while a non-meaning-changing receiving-use selection stays with that use;
  5. use A.2.4 to state the evidence-use relation. When bounded reliance needs a judgement, obtain or reuse it under A.10 or the directly governing evaluation pattern; add fuller source/provenance detail only when the use requires it.
  6. let the direct consumer apply the supported assertion under its own subject pattern.

When the account makes a claim about a particular dated evaluation Work, recover the evaluator System through A.13 and let A.15.1 independently admit that evaluation W_eval : U.Work.

Add F.6 performedUnderAssignment(W_eval, RA_eval) through the same obtaining A.13 assignment only when this account or its receiving use expressly consumes precise assignment-bound attribution; F.6 identifies neither assignment nor performer, and missing or failed attribution alone leaves independently admitted evaluation Work intact. Recheck any admission premise invalidated by the same finding and its dependent conclusions under A.15.1.

A separately constituted evaluation result is a C.2.1 episteme whose ClaimGraph states the judgment about the assignment or established occurrence. The evaluation and receiving use add no participants to the state relation: its participants remain the tested assignment and its predicate, and occurrence identity still follows §4.3.

The actual state extent, target evaluation window, and evidence-relevance interval answer different questions. When evidence no longer supports the receiving use, reconsider reliance without retroactively rewriting an earlier world-side occurrence.

A.2.5:4.5 - Work-Admission Use

A.2.5 defines the assignment-state relation and guides recognition of its occurrences and formulation of assertions. Use the direct subject patterns when Method selection, a gate decision, authority, or a claim that Work occurred is needed.

For a consequence-bearing admission use, apply the consumer’s direct pattern and check:

  1. the exact U.SystemRoleAssignment obtains throughout the receiving decision or Work window;
  2. the consumer selects one exact SystemRoleAssignmentStatePredicate, whose truth condition may be an explicit conjunction;
  3. each relevant assignment has an obtaining SystemRoleAssignmentStateRelation whose actual extent covers the receiving-use window;
  4. the assertion has the evidence relation and currentness that this consumer requires; and
  5. every other admission condition is separately established under its subject pattern.

The consumer’s direct pattern defines any admit, deny, defer, or unresolved outcome. This pattern supplies the state-recognition and assertion rules used in that decision.

A.2.5:4.6 - System-Role-Kind Relation Use

When substitution, incompatibility, bundle, or residual qualification among exact local system-role kinds is selected with A.2.7, test state sensitivity through exact assignments, state predicates, and windows.

  • Substitution supports one admission condition only when the candidate assignment’s current predicate satisfies the selected receiving rule.
  • Incompatibility uses the selected species’ holder rule, actual-Work or proposed-action identity condition, temporal test over the relevant windows, and state-predicate conditions under which the conflict appears.
  • A Work claim needing several system-role kinds uses the independently obtaining assignments and state occurrences needed by that claim. It does not require a Cartesian product of every possible state label.

A conjunction for one Work claim creates no composite system-role kind, assignment, or state predicate by form.

A.2.5:4.7 - State-Machine and Change Lenses

Use statecharts or state machines when mutually exclusive configurations, orthogonal regions, guarded changes, or event handling improve the subject-domain model. The notation describes possible configurations and changes; it does not replace the direct relation occurrence.

A change arrow represents a proposed or observed change in predicate truth; it is not the world-side change by form. Recover the exact changed object or relation, then use the direct pattern governing that change. Use the Method description for any prescribed Method order.

When the model needs continuous coordinates rather than discrete labels, use A.19 for the characteristic space and let the by-value state predicate select a region, band, ordering condition, or other condition. Measurement and evaluation stay with C.16 and their direct patterns.

A.2.5:4.8 - Semantic Basis and Receiving-Use Qualification

Use directly governed truth-condition clauses when they suffice for the state claim.

When a KindSignature, reference scheme, bridge, or BoundedModelUseStructure changes the meaning of a predicate clause, include its edition in SystemRoleAssignmentStatePredicate semantic basis and therefore in predicate identity. When it changes only how a separate receiving assertion, comparison, or Work use presents or consumes an unchanged predicate, cite it in that receiving use instead. The generic relation signature remains the two-participant declaration in §4.1.

A.2.5:5 - Working Guidance

  1. Write the readable sentence naming the current assignment and state condition; name the receiving-use window only when the current check selects one.
  2. Recover the predicate by value: system-role kind, normalized truth-condition clauses, temporal reading, applicability, and only meaning-bearing semantic-basis editions.
  3. Derive the maximal continuous extent from assignment obtaining and predicate truth; separately check any receiving-use window against that extent.
  4. Ask whether the receiving use needs occurrence identity and whether it relies on the state claim. If both answers are no, keep the readable assertion and stop.
  5. For relied-on use, make the assertion episteme, polarity, direct claim-family reference, and required evidence-use relation explicit. Record supported, refuted, or unresolved reliance separately; absent evidence is neither negative polarity nor world-side non-obtaining.
  6. Leave capability fit, Method selection, gate outcome, authority, assurance, and performed Work with their subject patterns.
  7. Put a meaning-changing semantic basis in predicate identity and a merely use-qualifying selection in the receiving use, never in the generic relation signature.

A.2.5:6 - Worked Slices

A.2.5:6.1 - Robot Inspection After Recalibration

Robot-7 already holds this A.2.1 assignment:

Robot7InspectionShiftAssignment-17 : InspectionShiftAssignment
InspectionShiftAssignment <: U.SystemRoleAssignment
  HolderSystemSlot: Robot-7
  AssignedSystemRoleKindSlot: InspectorSystemRole
  assignmentInterval: [2026-08-10T09:00, 2026-08-10T17:00]

The bearing-inspection method description declares InspectionReady, whose clauses require current calibration, clock synchronization inside tolerance, operating-envelope fit, and no active quarantine relation throughout the inspection window.

SystemRoleAssignmentStateAssertion:
  directClaimFamilyRef: A.2.5 SystemRoleAssignmentStateRelation
  SystemRoleAssignmentSlot: U.RelationRef(Robot7InspectionShiftAssignment-17)
  StatePredicateSlot:
    systemRoleKindRef: U.KindRef(InspectorSystemRole)
    NormalizedTruthConditionClaimGraph:
      CalibrationCurrent(Robot-7)
      and ClockSynchronizationWithinTolerance(Robot-7)
      and InspectionOperatingEnvelopeFit(Robot-7)
      and no ActiveQuarantineRelation(Robot-7)
    TemporalReading: continuous truth over the declared inspection interval
    Applicability: bearing inspection Work under InspectionShiftAssignment
    SemanticBasisRefs: omitted; these clauses use the direct subject predicates without another meaning-bearing edition
  assertionPolarity: affirmative
  systemRoleAssignmentStateExtent: [2026-08-10T09:20, 2026-08-10T12:00]

A calibration report is a separate U.Episteme; an A.2.4 evidence-use relation can support reliance on this assertion. At noon calibration validity ends and the predicate becomes false, so the first state occurrence ends while the assignment continues. If recalibration at 12:30 makes the same predicate true again, a second occurrence begins under that assignment.

A.2.5:6.2 - Drive Motor in a Pump Assembly

Motor-M1 is the holder of a pump-maintenance assignment whose assigned local kind is DriveMotorSystemRole. The current Work claim needs DriveReady, whose predicate names the exact supply relation, torque capability-fit relation, thermal band, and installed-connection relation.

The pump assembly grounds those direct claims; it is not a mandatory context slot. No scheme or BoundedModelUseStructure is required because the direct predicate clauses determine the state. Torque capability can remain while a missing supply relation makes DriveReady false. An affirmative DriveReady assertion states the assignment’s condition; use A.15.1 for any claim that pumping Work occurred.

A.2.5:6.3 - Socially Constituted Credential State

A clinician holds one assignment whose local kind is ProcedureOperatorSystemRole. Predicate CredentialCurrentForProcedure-X depends on an accepted credential decision, its validity interval, and absence of a suspending decision.

The accepted decision relation helps constitute the predicate because the credential ontology says so. A certificate publication may evidence that decision but does not substitute for it. The state occurrence still has the assignment and predicate as participants; evidence and publication remain neighboring relations.

A.2.5:6.4 - Two Approval Predicates

ApprovalService-2 holds an assignment to ApproverSystemRole. FulfilmentApprovalReady concerns fulfilment-state change; PaymentApprovalReady concerns payment authorization. Their truth clauses and applicability differ, so they are different SystemRoleAssignmentStatePredicate values even if one interface displays both as Ready.

If an independently selected model-use structure changes the meaning of one predicate’s clauses, its edition belongs in that predicate’s semantic basis. If it only selects which already identified predicate a view presents, it remains a receiving-use qualification.

A.2.5:6.5 - Approved Standard or Evidence Dataset Is a Different Relation

Suppose a project says, “Standard S is approved.” The standard is an episteme, not a system under a work-facing assignment. Recover the direct status-use, decision, source-use, or publication-use relation.

Likewise, a dataset or report that “plays a role” remains an episteme used through direct evidence, source, measurement, freshness, provenance, or assurance relations. Apply A.2.5 only if an admitted system’s assignment is being tested by a SystemRoleAssignmentStatePredicate that depends on one of those relations.

A.2.5:7 - Archetypal Grounding and Bias Control

Physical system. A motor, robot, laboratory instrument, or production cell can hold an assignment while its state predicate changes as physical relations and measured characteristics change.

Human or organizational system. A person, team, or organization can remain assigned while a current conflict, credential, fatigue, resource, or decision relation changes the predicate relevant to one Work claim.

Computational system. A service or agent can expose a capability while each concrete action still needs current assignment, state predicate, task relation, and direct authorization or gate evaluation. This is one specialization, not the universal meaning of assignment state.

Episteme boundary. A representation or evidence episteme can describe or support a state claim.

The main bias risk is label-first reasoning. A familiar state word invites the reader to skip predicate recovery. Repair it by recovering the assignment, predicate by value, actual state extent, and only the assertion and evidence-use relation needed by the receiving use.

A.2.5:8 - Conformance Checklist

CheckQuestion
CC-A2.5-01Does the claim concern whether the exact assignment satisfies the identified state predicate, with an occurrence named only when obtaining is established?
CC-A2.5-02Does SystemRoleAssignmentSlot use a U.RelationRef constrained to U.SystemRoleAssignment and resolve to the exact assignment occurrence being evaluated, with its declared species, holder, and extent established under A.2.1?
CC-A2.5-03Is StatePredicateSlot present by value with system-role-kind domain, normalized truth clauses, temporal reading, applicability, and only meaning-bearing semantic-basis refs?
CC-A2.5-04Is actual state extent derived from uninterrupted predicate truth while the assignment obtains, with any target evaluation window kept separate?
CC-A2.5-05When occurrence identity is needed, does it use the fixed assignment, fixed predicate value, and maximal continuous truth interval rather than a representation key?
CC-A2.5-06Are a demonstrated predicate gap and a mere evidence gap distinguished?
CC-A2.5-07Does SystemRoleAssignmentStateAssertion keep polarity, predicate, direct claim-family ref, known actual extent, target window, reliance posture, and evidence relations distinct?
CC-A2.5-08Are capability, Method selection, gate outcome, authority, assurance, and performed Work left with their direct patterns?
CC-A2.5-09If several predicates matter to the receiving use, are their conditions retained, with any required conjunction explicit and exclusivity imposed only when the subject-domain model requires it?
CC-A2.5-10Does cross-context reuse establish either the same full predicate identity or an explicit comparison or bridge showing which truth and admission effects are preserved?
CC-A2.5-11Is a meaning-bearing signature, scheme, bridge, or model-use structure included in predicate identity only when the clauses depend on it, and otherwise kept with the receiving use?
CC-A2.5-12If a statechart or graph is used, is it kept as a lens or description of possible configurations and changes?

A.2.5:9 - Common Failure Modes and Repairs

FailureObservable symptomRepair
Assignment-as-readinessA Work claim proceeds because a holder is assigned.Name the state predicate and establish the corresponding relation for the Work window.
State-label transportTwo domains use Ready as if it were one predicate.Compare full predicate identities; use an explicit bridge only when cross-context preservation is claimed.
Evidence-as-stateA certificate or dashboard display is entered as the state.Keep the world-side relation separate and target its assertion with an evidence-use relation.
Evidence-gap-as-falseA missing current report closes a state episode.Record unresolved reliance; close the occurrence only when a truth-condition clause is demonstrated not to hold.
Capability-as-admissionTool exposure or measured ability admits a concrete action.Keep capability in A.2.2 and evaluate current state and action-specific conditions separately.
Method-order driftTransition arrows are used as the procedure.Recover the represented change and its governing pattern; state any prescribed action order in the Method description. Identify particular Work or other occurrences only when the account claims they happened.
Product-state explosionA multi-assignment Work claim enumerates every combination of labels.Use separate state occurrences and only the conjunction needed by the current claim; create no compound system-role kind or assignment by form.

A.2.5:10 - Consequences

Benefits:

  • one assignment can support several separately identifiable state episodes;
  • simultaneous predicates remain expressible;
  • predicate truth, assertion, evidence use, and Work admission can change independently and be repaired locally;
  • Method and gate assertions cite an exact current relation instead of a status label; and
  • physical, social, organizational, and computational cases use the same relation discipline.

Costs and limits:

  • load-bearing predicates must be written by value, including temporal semantics and any meaning-bearing semantic basis;
  • consequence-bearing reliance needs only the evidence currentness and direct consumer that its use requires;
  • cross-context reuse may need a continuity or bridge decision rather than label matching; and
  • A.2.5 does not define every subject-domain predicate, measurement method, authorization relation, or state-changing Method.

Reassess only the affected state assertion or receiving use when the assignment, predicate identity, actual state extent, receiving-use window, evidence relevance, direct consumer rule, or meaning-bearing semantic basis changes. Do not rewrite the system-role kind or assignment when only one state episode changes.

A.2.5:11 - Rationale

The pattern starts from the world-side relation because state truth can matter before a record exists. A robot can cease to satisfy its inspection predicate before a dashboard refreshes. A credential decision can constitute an institutional condition before a certificate is published. A supported assertion is needed for some reliance uses.

Using uninterrupted predicate truth as the identity boundary distinguishes repeated episodes even when assignment and predicate stay the same. A description may refine an open interval’s end without creating another occurrence; a gap in predicate truth creates a boundary.

Assignment state is neither capability nor Work. Capability says what operations a system can perform in an envelope. SystemRoleAssignmentStateRelation says whether one current assignment satisfies one predicate over an interval. A Work claim states what was performed. A Method, gate, or Work pattern may depend on all three, but none proves the others.

A.2.5:12 - SoTA-Echoing

Current or mature lineWhat it contributesPractical use in A.2.5
W3C SCXML 1.0, a mature 2015 Recommendation rather than current competitive SoTAExplicit states, parallel regions, guarded transitions, events, and executable state-machine semantics.Keep statecharts available when the subject-domain model needs them, but type them as mathematical or description lenses rather than the world-side relation occurrence or universal Method order.
Esparza and Fischer, Runtime Verification for LTL in Stochastic Systems, 2025Runtime monitoring distinguishes true, false, and inconclusive results; finite observations do not settle every temporal property.Treat incomplete evidence as unresolved for the relying use, preserve the predicate’s temporal reading, and do not close an occurrence merely because a finite evidence path is silent.
Cedar Policy Language current referenceFine-grained decisions evaluate a concrete principal, action, resource, current attributes, and request-time conditions rather than a system-role label alone.Require the system performing consumer decision Work to combine current assignment, exact predicate, state window, and action-specific relations. Keep this as an implementable software specialization rather than the ontology of every assignment state.
Zuvic, Capability Gates Are Not Authorization, 2026 preprintA current agent-framework audit distinguishes exposed capability from per-call, value-sensitive authorization and reports fail-closed enforcement experiments.Keep capability in A.2.2 and require the consumer to evaluate the concrete state and action claim before side effects; do not infer authorization from tool exposure. The empirical scope remains the audited software frameworks.
Liu et al., A Framework for Formalizing LLM Agent Security, 2026 preprintTask alignment, action alignment, source authorization, and data isolation require runtime checks over the current task and action.In agentic cases, require the consumer’s governing claim to name the current task and action relations; A.2.5 defines the state relation and assertion form, while A.10 provides the rules for evidence use; the applicable evaluation or assurance pattern separately establishes any reliance posture.
A.6.REL, A.2.1, A.19, A.2.4, and A.10FPF already separates relation obtaining, occurrence identity, assignment episodes, characteristic-space predicates, assertions, and evidence use.Use §4.3 to distinguish state episodes; record an assertion and evidence use only when the receiving use requires them.

The sources’ transferable contribution is bounded: current action decisions need exact participants and predicates; temporal monitoring can remain unresolved; capability and action admission differ; and state-machine notation is optional modeling machinery.

A.2.5:13 - Relations

Related patternRelation
A.2 and C.3Govern context-local system-role kinds and their KindSignatures; assignment-state predicates may name those kinds and signatures without making them relation participants.
A.2.1Use for the declared U.SystemRoleAssignment species and the obtaining occurrence referenced by every state relation.
A.2.2Governs capability and operating-envelope claims that a state predicate may reference but does not replace.
A.2.4 and A.10A.2.4 governs first-use evidence classification; A.10 governs source/provenance recovery and bounded reliance.
A.2.7Use for relations among system-role kinds that may consume current assignment-state results without merging kinds, assignments, or states.
A.6.RELGoverns progressive relation-occurrence individuation and occurrence-as-participant use.
A.6.5Governs SlotKind, ValueKind, and reference-mode discipline for the direct declaration.
A.19 and C.16Govern characteristic spaces, predicates over measured coordinates, measurement, and comparability when used by a state predicate.
A.15, A.15.1, A.15.2, and A.21Govern Method participation, performed or planned Work, and gate outcomes that consume state claims.
A.1.1Use for any selected BoundedModelUseStructure; A.2.5 includes its edition in predicate identity only when meaning depends on it.
C.27 and G.11Govern temporal currentness, decay, and evidence refresh when those claims are current.

A.2.5:End

A.2.6 - Unified Scope Mechanism (USM): Test Scope Membership and Combine Scopes

Status: Stable Type: Ontic pattern

One-line summary. A.2.6 lets a practitioner test one U.ContextSlice against one set-valued scope. For a claim, member(slice, claimScope) is true or false: true admits the claim-scope condition and false stops that use. An evaluation returns unknown when its available basis cannot determine membership. The predicate is not a U.Relation occurrence.

Use this pattern when a receiving action needs to decide whether a claim, capability, or publication use covers one combination of standards, environment, local sense, platform, cohort, or time selectors.

First useful move. Name the claim, its U.ClaimScope, and the target U.ContextSlice; evaluate membership. Stop on false. On unknown, obtain the missing evaluation input, narrow the attempted use, or abstain. Add a result episteme or table only when the receiving use needs one. If exact local senses must be translated, follow §7.5: name the obtaining F.9 Bridge and separate affirmative C.2.1 claim for this translation, then establish the A.10 evidence basis and applicable reliance condition before using the translated scope.

For example, a workshop report supports a claim about checks made with a specified gauge, drawing revision and inspection period. Take the proposed job’s values for these selectors as one slice and ask whether that slice is in the report’s claim scope. The stool identified on the job card is the object being inspected. It can belong to the furniture kind used by the drawing, irrespective of whether this report covers the inspection. Two accepted checking methods might both work under the proposed conditions, or neither might work. A method can also work on jobs represented by several slices. Establish applicability from each method’s rule, choose using the job’s requirements when a choice is needed, then establish separately which method the technician used. Even a scope containing just one slice represents coverage. Its membership test does not perform any of these selections.

What goes wrong if missed. Teams infer coverage from a document, table, “current context” label, or selected structure; treat an unevaluated slice as excluded; or mint ScopeDelimitationRelation occurrences for included and excluded slices. Those moves collapse predicate truth, evaluation, representation, and structure.

What this buys. One set-valued scope algebra supports exact membership, intersection, supported union, translation, widening, narrowing, and refit while keeping claim content, evaluation work, result epistemes, model-applicability relations, and selected structures separate.

When a direct domain calculation is enough. A standalone mathematical applicability question may be settled by its stated conditions and calculation. When a receiving FPF rule requires scope membership, identify the required scope and slice and apply that guard; capability gating requires U.WorkScope (§10.3). A result record remains optional unless the receiving use needs one. Section 20 explains the additional value of reusable scopes.

Vocabulary boundary. Use these scope names in live FPF wording:

  • For epistemes, the only scope type is U.ClaimScope (nick G in F–G–R).
  • For system capabilities, the only scope type is U.WorkScope.
  • For publication views or forms, the only scope type is U.PublicationScope.
  • The abstract architectural notion is U.Scope — a durable scope value identified extensionally through one exact ContextSliceSet value under the effective reference scheme. Intersection, SpanUnion, translation, widening, and narrowing operate on those extensions; refit changes an expression without changing the extension. U.Scope is not a U.Characteristic and MUST NOT appear in any CharacteristicSpace.

Use source terms such as applicability, envelope, generality, and capability envelope with their domain meanings. When they designate an FPF scope value, identify its kind through the names above.

Cross‑references.

  • C.2.3 (Formality assessment F) and C.2.2 (F–G–R): this pattern defines G as U.ClaimScope.
  • A.2.2 (Capabilities): capability gating SHALL use U.WorkScope.
  • F.9 (Bridges): use an exact obtaining Bridge only when membership content must be translated across exact local senses; a different label or reference scheme alone does not trigger translation. F.9 supplies the direct semantic relation only. The separate C.2.1 claim states the exact translation use, direction, rule, tolerance, and polarity; A.10 or B.3 governs reliance on that claim.
  • Part E (Publication discipline; e.g., E.17 MVPK): publication views, cards, and lanes MAY declare U.PublicationScope to bound where a publication is admissible; U.PublicationScope MUST NOT widen the underlying U.ClaimScope/U.WorkScope. (USM supplies the scope calculus; Part E supplies publication discipline.)

A.2.6:1 - Problem frame - Purpose and Audience

This pattern gives practitioners one question: does this slice belong to the scope needed by this use? It applies first to claim scope and reuses the same value algebra for work and publication scopes.

The claim-bearing episteme, capability, or publication object designates or uses an exact U.ClaimScope, U.WorkScope, or U.PublicationScope. The membership predicate, evaluation work, result episteme, gate, and evidence claim also remain separate.

With USM, a practitioner can:

  • declare exact slice selectors and an exact scope predicate;
  • evaluate membership as true, false, or currently unknown;
  • combine exact scopes by intersection or independently supported union;
  • translate only when exact local senses require an obtaining F.9 Bridge, a separate affirmative C.2.1 claim about this translation, and the current A.10 or B.3 reliance branch.

A.2.6 defines the scope values, membership predicate, mathematical scope algebra, reusable A.6.1 operation declarations, and use boundaries. Use A.15.1 for evaluation work, A.10 for evidence, A.21 for gate decisions, and A.22 for structure selection. The practitioner decides whether and which claim to widen for the receiving use.

A.2.6:2 - Context

A.2.6:2.1 - Cross‑disciplinary pressures

A project may combine formal specifications, data-driven models, safety cases and operational playbooks. To rely on a claim from one of them, the practitioner needs its conditions of applicability. Their vocabularies can describe different aspects of those conditions:

  • Standards and specs often say applicability or scope.
  • Modeling communities say envelope.
  • Safety and performance documents speak about capability envelope.
  • Knowledge patterns have used generality (G) as if it were “more abstract,” when we need “where the statement holds.”

A.2.6:2.2 - Slice-bounded reasoning

U.ContextSlice is an addressable value identified by its exact declared selector schema and selector values under the effective reference scheme: for example local senses, named standard editions, environmental values, platform or cohort selectors, and a time selector when that selector belongs to the declared schema. One scope predicate may inspect only a projection of those selectors, but that projection does not reidentify the slice.

The practical question is therefore concrete: does this slice belong to this scope? A phrase such as “inside the current context,” a project label, or a selected U.Structure does not answer it.

A.2.6:2.3 - Minimal, composable trust math

In F–G–R:

  • F (formality) is “how strictly a claim is expressed” (C.2.3).
  • G must be “where it holds,” not “how abstract it sounds.”
  • R describes how strongly the claim is warranted by its evidence under the declared scope and use conditions (C.2.2). Observed semantic mismatch or loss may be evidence about a proposed translation, while the permitted-loss tolerance belongs to the separate C.2.1 claim about that use.

When G is a set‑valued scope, serial dependencies intersect scopes; parallel, independently supported lines can publish a SpanUnion over their supported areas.

A.2.6:3 - Problem

  1. Unresolved scope wording. Labels such as applicability, envelope, generality and capability envelope can hide different predicates or receiving uses. Recover the intended conditions before applying the common scope algebra.
  2. Abstraction confusion. Calling G “generality” invited teams to treat “more abstract wording” as “broader scope,” silently masking unstated assumptions.
  3. Split mechanics. Claims and capabilities need different use conditions, but their scopes share the set algebra. Separate those conditions without duplicating the algebra.
  4. Translation opacity. Exact local-sense translation was confused with ordinary designation resolution, causing automatic Bridge use and hidden changes to the supported slice set.
  5. Overloaded words. A phrase such as validity can mean a scope condition or an assurance judgment; operation can name an operation application or performed Work. Recover the intended object before applying the scope rule.

A.2.6:4 - Forces

ForceTension to resolve
One mechanism vs two worldsWe must serve both knowledge about the world (claims) and doing work in the world (capabilities) without duplicating concepts.
Exact local interpretation vs interoperabilityScope membership must stay checkable under its effective reference scheme. Cross-scheme translation needs an obtaining F.9 Bridge for the direct semantic relation, a separate C.2.1 claim for the proposed translation, and current A.10 or B.3 reliance, without redefining membership truth.
Expressivity vs minimal vocabularyTeams need to capture rich conditions (time windows, environment, versions) but not explode the lexicon into variants such as “envelope”, “applicability”, or “generality”.
Static content vs operational changeClaims may hold broadly while current operations are narrow (or vice versa). The mechanism must keep “what is true” and “what can be done” aligned yet distinct.
Open‑world exploration vs closed‑world gatingExploration benefits from permissive drafts; gates require crisp, observable checks. The same scope object must support both.

A.2.6:5 - Solution - Overview

USM keeps the following things distinct:

  • U.ContextSlice - one addressable value identified independently of the predicate that later inspects it;
  • ContextSliceSet - the mathematical ValueKind Set[U.ContextSlice], used for scope extensions and finite target sets;
  • U.Scope - one durable scope value whose extension is one exact ContextSliceSet value;
  • U.ClaimScope, U.WorkScope, and U.PublicationScope - C.3 specializations for claim, capability, and publication uses;
  • membership semantics, mathematical scope algebra, and reusable operations - three separate layers: the bivalent predicate, its C.29 set representations, and the exact A.6.1 declarations used only when a receiving use needs an actual application and binding.

The primitive claim-scope question is member(x, S) for exact slice x and exact scope S. Intersection handles serial dependence. spanUnion is allowed only for independently supported areas. widen and narrow change the extension; refit preserves it while changing only a scope expression or parameterization. translate is used only when exact local-sense content must cross an obtaining F.9 Bridge and a separate affirmative C.2.1 claim names this translation’s direction, rule, and tolerance.

A receiving guard relies on that claim through a passing A.10 disposition or, when an actual named assurance claim is current, a B.3 AssuranceResult for the same use with disposition=supported-for-use; a different label or reference scheme alone selects none of these.

One exact U.ClaimScope may participate in a ModelApplicabilityRelation. That relation, its actual obtaining extent, a selected A.22 structure, a membership evaluation, and a table displaying members remain separate.

Scope names. Use Claim scope (G), Work scope, and Publication scope when identifying the corresponding FPF scope kinds. Domain wording retains its source meaning; a synonym alone establishes neither a scope kind nor an equivalent scope.

A.2.6:6 - Normative Definitions

A.2.6:6.0 - Predicate semantics, mathematical algebra, and A.6.1 operations

Keep three layers explicit:

  1. Scope semantics. member(x,S) is a bivalent predicate over one exact U.ContextSlice and one exact U.Scope.
  2. Mathematical representation. The formulae below represent membership and set operations under C.29. Use the declarations and bindings below for an actual operation application.
  3. Reusable actual operations. When a receiving use needs one identified calculation or evaluation application and its bound result, use one of the A.6.1 OperationDeclarations below. These are argument and result declarations, never A.6.5 SlotSpecs.

Mathematical semantics.

member(x, S)                        : Bool
scopeSubset(S1, S2)                 := for every x, member(x,S1) implies member(x,S2)
coversSet(S, T)                     := for every x in T, member(x,S)
extension(intersect(F))             := intersection of extension(S) for S in F
extension(SpanUnion(F))             := union of extension(S) for S in F
extension(translate(B,C_use,S,RS))  := the target-slice image of extension(S) selected by C_use's rule and tolerance over Bridge B under RS
widen(S0,S1)                        := extension(S0) proper-subset extension(S1)
narrow(S0,S1)                       := extension(S1) proper-subset extension(S0)
refit(E0,E1,S)                      := expressions E0 and E1 both designate exact scope S

Here T : ContextSliceSet is a finite target set, F : Set[U.Scope] is a finite scope family, B is an exact obtaining F.9 Bridge, C_use is the exact current C.2.1 claim with B as EntityOfConcern and affirmative polarity for this named scope-translation use, and RS is the exact target reference scheme. The claim’s content names the direction, scope-correspondence rule, and permitted-loss tolerance used to select the target image; its effective ReferenceScheme makes those designations interpretable.

scopeSubset, coversSet, widen, narrow, and refit are mathematical predicates or comparison classifications, not actual A.6.1 operations. The formula represents the claim’s proposed mapping but proves neither the claim nor reliance on it and declares no operation application. Work that authors or compares scope declarations remains separately governed.

A.6.1 declaration A — ScopeMembershipEvaluationMechanism.

  • EntityOfConcernRef: operation family ScopeMembershipEvaluationOperationFamily = {evaluateMembership}.
  • effective reference scheme: the scheme under which this mechanism’s argument, result, and application meanings are interpreted.
  • SubjectKind: U.Scope.
  • RangedValueKind: U.ContextSlice.
  • ResultKind: declaration-local finite U.Kind MembershipEvaluationValue = {true, false, unknown} under C.3. Its membership rule admits exactly those three values. It is not a world-side third truth value, public U-kind, gate decision, or result episteme.
  • SliceSet and ExtentRule: absent; membership of the kind U.Scope is not slice-dependent in the A.6.0 sense.

OperationDeclaration evaluateMembership:

Declaration-local itemMeaningValueKindBinding designation ruleBinding predicateCardinality
argument targetSliceexact independently identified slice being testedU.ContextSliceByValuethis application evaluates the bound sliceexactly 1
argument scopeexact extensional scope against which membership is testedU.ScopeByValuethis application evaluates against the bound scopeexactly 1
argument interpretationBasisexact separately identified episteme containing the scope expression, available selector resolutions, and any translation input used by this applicationU.EpistemeByGovernedReferencethe reference resolves to the exact basis used; citation or availability alone is insufficientexactly 1
result membershipJudgmentwhat the application could determine about the bivalent predicateMembershipEvaluationValueByValuethis application returns this valueexactly 1

ApplicationPredicate: with those bindings, evaluate member(targetSlice, scope) under the bound interpretation basis; return true or false when the basis determines the predicate and unknown when a required selector resolution or translation input is unavailable. The application leaves the target slice and scope unchanged.

ApplicationIdentityRule: one application is one independently bounded evaluation invocation selected by the current calculation or evaluation-work locus. Repeating the evaluation with the same arguments is another application when another invocation occurs; argument equality alone does not merge them.

ApplicationExtentRule: the application begins when its exact argument bindings and interpretation basis are fixed for the invocation and ends when membershipJudgment is returned or the invocation stops without a result. A result binding cannot begin before the value is returned.

ScopeMembershipEvaluationMechanism LawSet. With the same exact argument bindings, interpretation basis, and effective reference scheme, evaluation is deterministic. true reports that the basis determines member(targetSlice, scope); false reports that it determines non-membership; unknown reports only that it cannot determine either result.

ScopeMembershipEvaluationMechanism AdmissibilityConditions. Admit an application only after the exact slice, exact scope, and exact interpretation basis are bound. unknown is admitted when that basis records an unavailable required selector resolution or translation input. A missing exact scope, slice, or basis blocks the application.

ScopeMembershipEvaluationMechanism Applicability. Use this declaration only for evaluating exact U.ContextSlice and U.Scope values under its effective reference scheme. The receiving use names its exact U.ClaimScope, selected evaluation time when current, selected CHR:ReferencePlane only when the use is plane-dependent, and any mechanism-specific condition.

ScopeMembershipEvaluationMechanism SignatureManifest (optional). When dependency replay needs it, name the imported or provided declarations for U.ContextSlice, U.Scope, and the local MembershipEvaluationValue.

ScopeMembershipEvaluationMechanism neighboring objects. An evaluation application can occur within dated work governed by A.15.1. A separately persisted result episteme remains optional under C.2.1; A.15.PROD enters only for a current claim that work first constituted that episteme. Evidence-use and gate occurrences stay under A.10 and A.21. None of those objects, nor another evaluation invocation, reidentifies this mechanism unless it reveals changed declaration content.

ScopeMembershipEvaluationMechanism refinement or conservative extension. A refinement preserves evaluateMembership, its argument and result meanings, binding rules, application predicate, identity and extent, and the bivalent-truth boundary while stating every strengthened law or admission condition. A conservative extension adds optional arguments, results, or operations without changing those inherited meanings or admitted uses.

A.6.1 declaration B — ScopeDerivationMechanism.

  • EntityOfConcernRef: operation family ScopeDerivationOperationFamily = {deriveIntersectionScope, deriveSpanUnionScope, deriveTranslatedScope}.
  • effective reference scheme: the scheme under which this mechanism’s operation meanings and returned scopes are interpreted.
  • SubjectKind: U.Scope.
  • RangedValueKind: U.Scope; each derivation operation still returns a U.Scope, so no distinct mechanism-level ResultKind is current.
  • SliceSet and ExtentRule: absent for the same A.6.0 reason stated above.
OperationDeclaration-local itemMeaningValueKindBinding designation ruleBinding predicateCardinality
deriveIntersectionScopeargument scopeFamilyexact finite family whose scope extensions are intersectedSet[U.Scope]ByValuethis application uses the bound set value, containing at least two exact scopesexactly 1 set value
result derivedScopeexact extensional scope returned for the intersectionU.ScopeByValuethis application returns this independently identifiable scope valueexactly 1
deriveSpanUnionScopeargument scopeFamilyexact finite family whose independently supported extensions are united by the established SpanUnion operationSet[U.Scope]ByValuethis application uses the bound set value, containing at least two exact scopesexactly 1 set value
argument independenceBasisexact episteme stating the support lines and their required independenceU.EpistemeByGovernedReferencethe reference resolves to the exact basis used by this applicationexactly 1
result derivedScopeexact extensional scope returned for SpanUnion(scopeFamily)U.ScopeByValuethis application returns this independently identifiable scope valueexactly 1
deriveTranslatedScopeargument sourceScopeexact source scope whose extension is mappedU.ScopeByValuethis application maps the bound scope valueexactly 1
argument bridgeOccurrenceexact obtaining F.9 Bridge whose direct semantic relation is usedU.RelationByGovernedReferencethe reference resolves to the exact obtaining occurrence used by this application; it carries no use-specific rule, tolerance, or relianceexactly 1
argument scopeTranslationClaimexact current C.2.1 claim that says the bound Bridge is suitable for this named scope translationU.EpistemeByGovernedReferencethe reference resolves to the exact affirmative claim whose EntityOfConcern is the bound Bridge and whose content names this use, direction, rule, and toleranceexactly 1
argument targetReferenceSchemeexact scheme under which target slices and their local senses are interpretedEpistemeInterpretationScheme (C.2.1:4.1.2)ByValuethis application interprets the returned target-slice extension under the bound schemeexactly 1
result derivedScopeexact extensional scope returned for the target image selected by the claim’s rule and toleranceU.ScopeByValuethis application returns this independently identifiable scope valueexactly 1

The target scheme is the exact rule collection classified by C.2.1:4.1.2, including the rules needed to read the target slices and local senses. A scheme can pass that range test while the proposed translation lacks its required mapping or bounded-use basis. Apply the translated-scope law to the bound value; range membership supplies neither that mapping nor any additional scope support.

ApplicationPredicate rules. deriveIntersectionScope returns the scope represented under C.29 by intersection of extension(S) for S in scopeFamily. deriveSpanUnionScope implements the already established SpanUnion: it is admitted only when independenceBasis establishes the section 7.3 independence condition and returns the scope represented by SpanUnion(scopeFamily). deriveTranslatedScope is admitted only when the bound Bridge obtains and the bound C.2.1 claim has that Bridge as EntityOfConcern, affirmative polarity, and content naming this scope-translation use, its direction, rule, and tolerance. The application applies that rule within that tolerance and returns the scope represented by translate(bridgeOccurrence, scopeTranslationClaim, sourceScope, targetReferenceScheme). The formulae and claim alone declare no application or result binding.

For every governed-reference argument, record presence, citation, or a compatible token is insufficient: the reference must resolve to the exact value used. For every result row, the result binding obtains only when this application returns the independently identifiable extensional scope.

ApplicationIdentityRule: each derivation application is one independently bounded calculation invocation identified through its exact invocation boundary, mechanism edition, and operation designator rather than the argument tuple alone. Repeated calculations with equal arguments remain distinct applications.

ApplicationExtentRule: the application begins after every required argument is bound for that invocation and ends when the derived-scope value is returned or the invocation stops without a result. A result-binding extent cannot begin before that scope value is returned.

ScopeDerivationMechanism LawSet. Serial composition uses intersection. Parallel publication uses the one established SpanUnion and preserves only slices supplied by independently supported lines. Translation returns only the target-slice image selected by the bound claim’s rule and tolerance over the bound obtaining F.9 Bridge. No derivation operation widens support by itself.

ScopeDerivationMechanism AdmissibilityConditions. Intersection and SpanUnion require at least two exact scopes. deriveSpanUnionScope additionally requires the bound independence basis to meet section 7.3. deriveTranslatedScope requires both an exact obtaining Bridge and the exact affirmative C.2.1 claim whose named rule and tolerance select the claimed target image. A missing or non-obtaining Bridge or a missing or non-affirmative claim blocks that positive derivation application; the latter does not negate an otherwise obtaining Bridge.

ScopeDerivationMechanism Applicability. Name the exact source scopes and reference schemes required by the selected derivation. For translation, also name the bound Bridge and separate C.2.1 claim. Before a receiving guard, assertion, publication, or structure selection relies on the returned scope, require the exact A.10 evidence-provenance relation for this bounded use. For ordinary reliance, require RelianceDisposition=pass. If an actual named assurance claim about that use is current, require its B.3 AssuranceResult for the same bounded use with disposition=supported-for-use. A direct domain rule may require such a claim, but neither scope translation nor consequence creates it.

A missing or non-affirmative use claim or a non-passing A.10 disposition stops ordinary reliance without changing membership truth or the Bridge. When an actual named assurance claim is current, a B.3 AssuranceResult with disposition=narrowed supports only its stated narrower use; abstain, evidence-needed, reopen, or blocked stops the attempted use. A.10 pass or B.3 supported-for-use supports only the named use. Neither is legal, policy, or deontic authorization, and neither proves that a derivation application or another receiving object occurred. Any required authorization remains under its direct pattern.

The receiving use also names its exact U.ClaimScope, selected time when current, selected CHR:ReferencePlane only when plane-dependent, and derivation-specific conditions. GammaTimePolicy enters only when time changes membership; ReferencePlane is absent from ordinary set algebra.

ScopeDerivationMechanism SignatureManifest (optional). When dependency replay needs it, name the imported or provided declarations for U.Scope and, for translation, the exact F.9 Bridge declaration and C.2.1 claim identity rules. The independence basis, particular Bridge, and particular scope-translation claim are application arguments, not declaration-manifest entries by adjacency. scopeTranslationClaim is only this declaration’s argument label; it names no public claim kind. A.10 and B.3 reliance objects remain under their subject patterns rather than becoming a common mechanism signature.

ScopeDerivationMechanism neighboring objects. A derivation can occur within dated calculation work under A.15.1. Its bound independence-basis episteme, Bridge, and C.2.1 scope-translation claim retain their own identities and direct patterns. The exact A.10 relation and disposition, or the exact B.3 AssuranceResult when an actual named assurance claim is current, states whether the use has the needed evidence or assurance support; neither is a mechanism argument or result.

The returned U.Scope is independently identified by its extension. Evidence, publication, gate, assurance, and any downstream Work, assertion, relation, or publication occurrence remain with their direct patterns. None of those objects, nor another derivation invocation, reidentifies this mechanism unless it reveals changed declaration content.

ScopeDerivationMechanism refinement or conservative extension. A refinement preserves the inherited derivation operations, argument and result meanings, binding rules, application predicates, identity and extent, and the intersection, SpanUnion, and translation semantics while stating every strengthened law or admission condition. A conservative extension adds optional arguments, results, or operations without changing those inherited meanings or admitted uses.

Relation between the declarations. These are two independently identified U.Mechanism epistemes. They coordinate by value: a later evaluateMembership application may bind a scope returned by one derivation application. If a receiving claim needs a refinement, extension, equivalence, or other direct relation between exact mechanism editions, state its endpoints, predicate, scope, and preserved and changed content under A.6.1.

A.2.6:6.1 - U.ContextSlice - exact membership target

U.ContextSlice is an addressable durable value formed from one exact declared selector schema and one value for every selector present in that schema. A scope predicate may inspect a declared projection of the slice, but it does not determine the slice’s identity. A minimal slice declaration contains:

ContextSlice:
  effectiveReferenceScheme:
  declaredSelectorSchema:
  exactLocalSenseRefs?, when included by that schema:
  standardOrInterfaceEditionRefs?, when included by that schema:
  environmentOrPlatformSelectors?:
  cohortOrJurisdictionSelectors?:
  gammaTime?, when included by that schema:
  otherDeclaredSelectors?:

The slice is one value. A finite target is one value of mathematical ValueKind ContextSliceSet. Two slice designators resolve to the same U.ContextSlice exactly when their declared selector schemas match and every declared selector resolves to the same value under the effective reference scheme. A predicate’s current argument projection, missing evaluation input, or receiving action cannot merge or split slice identity.

For example, slice_A and slice_B may share substrate Al6061, temperature 140 °C, and rig edition Calib-v3 while carrying different declared cohort selectors. A temperature-only scope predicate can return the same result for both slices, but the slices remain distinct; a cohort-sensitive predicate can distinguish them without reidentifying either one.

Do not write an implicit “current” or “latest” selector. If time changes membership, name the exact point, interval, or policy. If time does not change membership, do not add a temporal field merely to complete the tuple.

A.2.6:6.2 - U.Scope - set-valued scope

U.Scope is a durable value with one exact extension of mathematical ValueKind ContextSliceSet. U.ClaimScope, U.WorkScope, and U.PublicationScope are its C.3 specializations for receiving uses; the specialization does not copy the extension or add another identity discriminator.

For exact scope S and exact slice x, the primitive delimitation semantics is:

member(x, S)

The predicate has the slice and scope as arguments. It is not by itself an explicitly individuated U.Relation occurrence. Included slices satisfy it; excluded slices do not. The excluded area is not materialized as an unbounded complement entity.

For effective reference scheme RS, define extension_RS(S) := { x : U.ContextSlice | member(x, S) }. Two scope designators resolve to the same extensional U.Scope value when their extensions contain exactly the same independently identified slices under the same or explicitly reconciled reference scheme. An equivalent predicate expression, unit conversion, factoring, or publication change can preserve that value; a boundary change that adds or removes even one slice identifies another scope value.

A set or predicate expression, table, diagram, or query result can represent or designate a scope or a set of evaluated slices under C.29 and C.2.1.

USM admits subset, intersect, spanUnion, translate, widen, and narrow over exact scope extensions. refit is a same-extension normalization: it changes a predicate expression, units, or factoring while preserving member(x,S) for every exact slice under the effective reference scheme. A changed expression may require another declaration or claim-bearing episteme edition under its direct governor; it identifies another U.Scope only when the extension changes.

Membership alone supplies no independently individuated relation occurrence. A receiving use that needs one requires a direct relation kind admitted under A.6.REL, with participant meanings, obtaining condition, recurrence rule and occurrence identity. A.2.6 admits no ScopeDelimitationRelation, ScopeDelimitationMode, or ScopeDelimitationInterval.

A.2.6:6.3 - U.ClaimScope (G) and membership evaluation

U.ClaimScope is the exact set-valued scope used to say where one claim holds. The claim-bearing U.Episteme and the scope value are distinct; the episteme designates the exact scope current for that claim.

An evaluation of member(x, S) is also separate:

  • the predicate semantics determine membership;
  • when a particular dated evaluation Work is asserted, A.13 identifies its actual performer and A.15.1 admits the occurrence independently; add F.6 only if the account must also identify its assignment, and keep the Method and direct evaluation relation or A.6.1 bindings separate;
  • a separately current C.2.1 result episteme may state true, false, or unknown;
  • evidence and freshness claims remain under A.10 and their direct governors.

unknown reports that the evaluation cannot currently decide because a required selector, designation resolution, or translation input is unavailable. It does not mean false, does not exclude the slice, and does not create a third world-side membership state. A receiving guard abstains, narrows the attempted use, or follows an explicitly governed reliance policy; it does not rewrite the predicate.

One exact U.ClaimScope participates in ModelApplicabilityRelation when model applicability is current. A declared ModelApplicabilityInterval belongs to an assertion or occurrence description. The actual applicability occurrence uses the maximal continuous extent over which its predicate obtains, as governed by A.1.1; the interval is not another direct participant.

A BoundedModelUseStructure may be selected over exact model-applicability and other governed relation occurrences under applied constraints that refer to exact claim-scope values. Keep the scope value distinct from the two ways it can affect structure identity. A bare scope, slice, membership outcome, or displayed boundary never enters A.22 identity.

One exact U.ClaimScope remains a participant of an independently governed ModelApplicabilityRelation; when that exact obtaining occurrence is selected into the structure, the occurrence contributes through A.22’s relation-occurrence discriminator. Separately, one exact applied constraint claim may refer to that scope and contribute through A.22’s applied-constraint discriminator. Neither route turns the scope into a structure constituent, a membership-relation occurrence, or a second delimiter.

The same scope may participate in differently selected relation occurrences or be referenced by differently identified structures, and a changed structure does not by itself reidentify the scope.

Expression. State a Claim scope as an exact predicate or condition block over slice selectors: assumptions, parameter ranges, cohorts, platform or standard editions, exact local senses when current, and time conditions only when they change membership.

Algebra. Serial dependencies use intersection. Independently supported areas may use spanUnion with the independence basis stated. widen and narrow change the declared set; refit preserves it. translate uses the section 7.5 Bridge-plus-use-claim branch and keeps reliance separate.

A.2.6:6.4 - U.WorkScope — scope of doing Work (capability)

Subject and declared basis. A qualified A.2.2 ability claim about an independently identified holder System designates its U.WorkScope. This is the set-valued work-condition basis of that claim, not a scope carried by a separate capability individual.

Meaning. U.WorkScope is the set of U.ContextSlice values under which a capability’s deliverability claim may be evaluated. Work-measure targets and qualification windows are checked separately at use time; they are not members or identity fields of the scope.

Expression. The capability declaration designates an exact U.WorkScope expressed only as conditions over U.ContextSlice: environment, versioned standards or platforms, resource regimes, exact local senses when current, and gammaTime only when time changes membership. Quantitative deliverables and qualification windows are not part of the scope value:

  • Declare targets as work-measure target sets (e.g., latency <= L, throughput >= T, tolerance <= epsilon) bound in guards (WG‑2).
  • Declare inspection/recertification policies as qualification-window policies bound in guards (WG‑3).

The use‑time admission requires all of: WorkScope covers JobSlice AND WorkMeasures satisfied AND qualificationWindowHolds(holderAbilityClaim, qualificationWindowPolicy, evaluationTime).

Here holderAbilityClaim supplies the identified holder, claimed work conditions and bounds, and the declared support basis to which the qualification policy applies. The policy evaluates reliance at the stated time; its failure does not itself prove a loss of actual ability.

Method–Work gating. A Work step’s guard MUST check that the target slice is covered by the capability’s Work scope and that required measures and qualification windows are satisfied.

Composition and Delta-moves. Work scope uses the same algebra as Claim scope (intersection / spanUnion / translate / widen / narrow / refit). Section 7.5 selects translate only for exact local-sense translation through an obtaining F.9 Bridge plus the separate affirmative C.2.1 claim and its current reliance branch.

Separation from knowledge. A Work scope is a set-valued scope. The capability declaration uses it to delimit where a deliverability claim is evaluated. Measurements and monitoring may support that claim through separately governed evidence and reliance judgments.

Required guard facets (capabilities).

  • Work-measure target set (mandatory). A set of measurable targets with units and tolerated ranges, evaluated on the JobSlice.
  • Qualification-window policy (mandatory for operational use). A time policy stating when the capability is considered qualified; evaluated at the exact evaluation time selected by the receiving guard, not copied into U.WorkScope.

These facets are separate from U.WorkScope and belong to the evidence and reliance conditions. They MUST be referenced in Method–Work guards (see §10.3 WG‑2/WG‑3); B.3 applies when an actual named assurance claim is current.

A.2.6:6.5 - U.PublicationScope — scope of a publication view or publication form

Carrier. A publication view or form is rendered on a carrier; the carrier is a separate object.

Meaning. The set of U.ContextSlice where a publication (a view, card, or lane about some object or morphism) is admissible for use within its underlying Claim scope or Work scope.

Relation to other scopes (normative).

  • If the publication’s admissible use relies on claim c in episteme E: PublicationScope(view_E) ⊆ ClaimScope(c).
  • If the publication presents a qualified holder-ability claim C for work admission: PublicationScope(view_C) ⊆ WorkScope(C), where WorkScope(C) is the work-condition basis designated by that claim. Any relied-on episteme ClaimScope remains a separate constraint; stating the ability in an episteme does not turn its WorkScope into ClaimScope.
  • When publication use requires all contributing claims or capabilities to apply together, its scope is a subset of their intersection. For independent support lines for the same claim or capability, establish the supported SpanUnion under §7.3 and bound publication use by that resulting scope. When exact local senses require translation, use section 7.5 for each affected source scope: obtaining F.9 Bridge, separate affirmative C.2.1 use claim, and current A.10 or B.3 reliance before the returned scopes are combined under the applicable rule.

Expression. Declare U.PublicationScope as an exact predicate over only the U.ContextSlice selectors that restrict publication use: for example versioned standards, environment, audience, interface availability, exact local senses, or gammaTime when time changes membership. It may be narrower than the underlying scope but must not be wider.

Algebra and Delta-moves. Publication scope uses the USM algebra. A widened publication scope is admissible only when the resulting set remains a subset of the applicable underlying Claim scope or Work scope, using §7’s composition rule when several scopes contribute, and the publication conditions support each added slice; the underlying scope need not change when it was already broader.

Orthogonality to measurement. U.PublicationScope is a USM scope object (set‑valued), not a CHR Characteristic and MUST NOT appear as a slot in a U.CharacteristicSpace.

View refinement (profiles). When a publication profile or view refines another, its U.PublicationScope MUST be a subset of the scope of the profile or view it refines (for example, a typed card may require additional pins).

A.2.6:7 - Scope Algebra

A.2.6:7.1 - Membership and coverage

For exact slice x and scope S, evaluate member(x, S).

  • true: the slice is included and the scope condition for the attempted use passes;
  • false: the slice is excluded and that use stops or selects another scope;
  • unknown: the available evaluation cannot decide; the guard abstains or follows an explicitly governed reliance policy without asserting exclusion.

For a finite target set T : ContextSliceSet, coversSet(S,T) abbreviates for every x in T, member(x,S). Scope-to-scope scopeSubset(S1,S2) instead means for every x, member(x,S1) implies member(x,S2). A target set is neither a scope nor a substitute for one. There is no “close enough” membership and no implicit widening.

Membership evaluation work, its inputs and A.6.1 bindings, an optional C.2.1 result episteme, and a C.29 table remain neighboring objects.

A.2.6:7.2 - Serial Composition (Intersection)

Rule S‑INT (serial). For an essential dependency chain C1 → C2 → … → Ck that supports a claim/capability, the effective scope along that chain is:

Scope_serial = ⋂_{i=1..k} Scope(Ci)

If Scope_serial = ∅, the chain is inapplicable and MUST NOT contribute to published scope.

Monotonicity. Adding a new essential dependency can only narrow (or leave unchanged) the serial scope.

A.2.6:7.3 - Parallel Support (SpanUnion)

Rule P‑UNION (parallel). If there exist independent support lines L₁,…,Lₙ for the same claim/capability, each with serial scope S_i, the publisher MAY declare:

Scope_published = SpanUnion({S_i})  =  ⋃_{i=1..n} S_i

Constraints.

  • Independence MUST be justified (different support lines must not rely on the same weakest link).
  • The union MUST NOT exceed the union of supported slices.
  • Publishers SHOULD annotate coverage density/heterogeneity (informative) to aid R assessment, but numeric “coverage” is not part of G.
  • Independence criterion. Support lines in a SpanUnion MUST be partitioned so that each line has a set of essential components disjoint from the others’ essential components (no shared weakest link). The partition (or a certificate thereof) SHALL be referenced in the publication.

A.2.6:7.4 - Set-valued scope and scalar reporting

1) G is not an ordinal scale; it is set-valued. Under USM, U.ClaimScope is a set‑valued USM scope object over U.ContextSlice. The only well‑typed primitives are membership and set operations (⊆, ∩, ⋃). Imposing ordinal “levels” such as G0…Gk violates the type discipline and produces non‑invariant behavior (the same set could be “rated” with different numbers under different heuristics). (See also LEX‑CHR‑STRICT.)

2) G composes via ∩ / SpanUnion, not via min / avg. USM already fixes composition: along a dependent path use intersection; across independent support lines publish SpanUnion. None of these operations relies on (or preserves) any linear order. An ordinal “G ladder” invites people to take minimums/averages, which is incorrect for sets and breaks the established algebra.

3) Abstraction level is orthogonal to G. A ladder from instances through patterns and formal types to equivalence up to isomorphism describes an abstraction or typing distinction. That distinction does not determine where a claim holds. Abstraction can be described by the optional AbstractionTier (AT) facet; applicability is U.ClaimScope (G).

4) A G ladder breaks locality and Bridge semantics. When exact local senses require translation, an obtaining F.9 Bridge establishes their direct semantic relation while a separate C.2.1 claim states the proposed mapping rule and tolerated loss. There is no canonical way to translate an ordinal G level: the mapped area may be narrower or differently factored. USM translates exact sets only through that bounded claim and keeps A.10 or B.3 reliance separate rather than rewriting G.

5) A G ladder duplicates ESG guards without adding decision power. Expression quality and scope coverage answer different questions. C.2.3 governs expression properties. Explicit guards determine scope coverage, include gammaTime only when membership varies with time, and check freshness separately when current. A reported G number cannot replace those predicates.

Normative directive. U.ClaimScope (G) SHALL remain a set‑valued USM scope object; no ordinal or numeric ladder SHALL be defined for G. If a profile needs scalar reporting, it MAY publish an explicit report‑only proxy CoverageMetric(G), but CoverageMetric(G) MUST NOT substitute for G in norms, gates, Bridge semantics, bounded-use claims, or reliance decisions. Authoring and gating SHOULD use required expression properties or justified local formality thresholds (C.2.3) and explicit guard predicates (A.2.6) rather than pseudo‑levels of G.

A.2.6:7.5 - Translation across exact local senses

Use translation only when ordinary designation resolution cannot settle the exact local senses needed by the target membership predicate. Then proceed in this order:

  1. resolve the source and receiving F.17 SchemeSenseCell values and name the exact obtaining F.9 Bridge that relates them;
  2. state the proposed scope translation separately: name the source scope, target scheme, source-to-receiving direction, scope-correspondence rule, and tolerated loss, then cite the exact current C.2.1 claim with that Bridge as EntityOfConcern and affirmative polarity for this use;
  3. before a guard relies on the claim, require the exact A.10 evidence-provenance relation for this bounded use; ordinary reliance requires RelianceDisposition=pass; when an actual named assurance claim is current, require its B.3 AssuranceResult for that same use with disposition=supported-for-use; and
  4. use translate(Bridge, UseClaim, SourceScope, TargetReferenceScheme) as the C.29 mathematical representation, or invoke deriveTranslatedScope with those same four values when one actual calculation and returned scope are needed.

The Bridge establishes the direct semantic correspondence. The separate claim selects this translation’s direction, rule, and tolerance. A Bridge profile, Bridge Card, reference-scheme difference, project label, or slice designator cannot supply that claim or its reliance basis. A missing or non-obtaining Bridge blocks the semantic branch. A missing or non-affirmative use claim blocks reliance. A non-passing A.10 disposition blocks ordinary reliance; when an actual named assurance claim is current, a B.3 result other than supported-for-use stops or narrows the assurance-bearing use. None of these outcomes makes an otherwise obtaining Bridge false.

An A.10 pass, or a B.3 AssuranceResult with disposition=supported-for-use, supports only the named use; neither authorizes it. A direct domain rule may require an assurance claim, but it must be stated separately.

Observed mismatch, calibration error, and counterexamples are evidence about the use claim. The permitted loss is the tolerance inside that claim. If the rule and tolerance permit translation only for part of the source scope, identify that part and return its target image. Neither the Bridge nor the claim supplies direct support for adding a slice, and neither makes membership true. The exact deriveTranslatedScope application remains an A.6.1 operation application; the claim and reliance basis do not prove that it occurred.

A.2.6:7.6 - Δ‑Operations (Widen, Narrow, Refit)

  • Δ‑G+ (widen). Monotone expansion: S proper-subset S-prime. Every added slice requires direct support under the receiving use; a Bridge and affirmative translation-use claim can define a mapping but supply no such support by themselves.
  • ΔG− (narrow). Monotone restriction: S′ ⊂ S. Often used to remove areas invalidated by new findings.
  • Refit. A different expression or parameterization designates the same extensional scope after normalization (for example, changing units or factoring common predicates). Refit MUST NOT alter membership and does not create another scope value.

Refit (normalization). A refit MUST preserve membership exactly: extension_RS(S_after) = extension_RS(S_before), so both expressions designate the same scope value. Any change that alters boundary inclusion through rounding, unit conversion, or discretization is a ΔG± change, not a refit.

Edition triggers. A changed extension identifies a different scope value. A changed predicate expression with the same exact extension preserves the scope value but is a content change in the declaration or claim-bearing episteme that carries the expression; its direct governor decides whether another episteme edition is needed.

Discriminating cases. Under one effective reference scheme, 20 °C <= temperature <= 30 °C and the exactly converted 293.15 K <= temperature <= 303.15 K have the same extension and can be related as a refit while designating the same scope. Replacing the inclusive upper boundary with temperature < 30 °C removes every slice exactly at 30 °C; that one membership-boundary change identifies another scope rather than a refit.

A.2.6:7.7 - Invariants

  • I-LOCAL. Interpret membership under the effective reference scheme and exact local senses current to the declaration. Translate only through an obtaining F.9 Bridge plus the separate affirmative C.2.1 claim for that translation; keep A.10 or B.3 reliance outside membership truth.
  • I‑SERIAL. Serial scope is an intersection; it cannot grow by adding dependencies.
  • I‑PARALLEL. Parallel scope MAY grow by union, but only where independently supported.
  • I‑WLNK. F describes the required expression properties of the essential constituents and their connecting inferences under C.2:4.3 and C.2.3:15.1. The composition must preserve those properties; a minimum applies only under a justified rule on a shared local ordered scale. R follows the justified support-composition model or non-aggregate synthesis under C.2.2:4.3 and B.3:4.4; dependency paths alone supply no default minimum. G follows the set rules in A.2.6:7.2 and A.2.6:7.3.
  • I‑IDS. Idempotence: Intersecting or unioning a set with itself does not change it.
  • I‑EMPTY. Empty scope is a first‑class value; guards MUST treat it as “not applicable”.

A.2.6:7.8 - Empty & Partial Scopes

  • Empty scope (∅). No slice satisfies the declared predicate. A receiving guard stops.
  • Partial scope. Publishers SHOULD avoid “global” language when actual scope is thin; instead, publish explicit slices and (informatively) coverage hints to guide R assessment.

A.2.6:8 - Locality, Time & Version Semantics

A.2.6:8.1 - Local interpretation without a context container

Interpret a scope predicate under the effective reference scheme and exact local senses named by the claim or scope declaration. Evaluate it against exact U.ContextSlice values.

Do not assume that a similarly named selector elsewhere has the same sense. Use ordinary designation resolution when it suffices. Use translate only when exact local senses need an obtaining F.9 Bridge and a separate affirmative C.2.1 claim states the proposed translation’s direction, rule, and tolerance; establish the current A.10 or B.3 reliance branch before acting on the returned scope.

A.2.6:8.2 - Time selector Γ_time

When membership depends on time, the scope predicate and target slice name an exact gammaTime point, interval, or policy and state which boundary changes a slice from member to non-member or back. Implicit “latest” is forbidden. A time-independent predicate need not inspect gammaTime. Keep every selector already declared in the slice schema; do not add a time selector merely to complete a new declaration. Evidence freshness remains a separate R-lane predicate.

A.2.6:8.3 - Standards, versions & notations

When a standard, interface, or schema edition affects membership, name the exact edition. A notation change with faithful designation resolution does not change G. If exact local senses require translation, the F.9 Bridge establishes their relation, the separate C.2.1 claim states this translation’s rule and tolerance, and A.10 or B.3 governs reliance.

A.2.6:8.4 - Determinism of evaluation

For a fixed scope, slice, and available evaluation inputs, the evaluation method returns one reproducible result. false stops the attempted use. unknown also blocks admission but does not assert non-membership.

A.2.6:8.5 - Interaction with R (freshness & decay)

For empirical claims and operational capabilities, an evidence-freshness policy can change warranted reliance over time without changing the scope extension. Guards MAY combine “Scope covers” with “Evidence freshness holds” as separate predicates.

A.2.6:9 - Scope Terminology

L‑USM‑1 (names). Use Claim scope (G) for epistemes, Work scope for capabilities, and Publication scope for publication views or forms. Use Scope for the common extensional scope value. A scope value is not a characteristic; the source words applicability, envelope, generality, capability envelope, or validity must be interpreted before selecting either kind.

L‑USM‑2 (Work and operation). Use A.15 for performed Work and A.6.1 for operation applications. Use Work scope for the set of conditions under which a capability claim is evaluated.

L‑USM‑3 (Validation). When a claim concerns Validation Assurance (LA), use its Part B meaning. For a scope object, use the applicable scope name rather than the ambiguous label validity.

L-USM-4 (Domain). “Domain” is a recognition cue, not a guard input. Name the exact U.ContextSlice selectors needed by the membership predicate.

L-USM-5 (First mention). On first use in a pattern or working instruction, write “Claim scope (G)” so the F-G-R meaning is recoverable.

A.2.6:10 - Guard Patterns (ESG & Method–Work)

A.2.6:10.1 - Common guard shape

A claim-scope guard starts by evaluating membership:

membershipResult := evaluateMembership(TargetSlice, ClaimScope, InterpretationBasis)

Admit the scope condition only when the result is true. Stop on false. On unknown, abstain, obtain the missing input, narrow the attempted use, or apply a separately governed reliance policy. Evaluate any required freshness, formality, time-currentness and assurance conditions separately. The gate decision remains under A.21.

Add a translation branch only when the membership predicate uses exact local senses that ordinary designation resolution cannot align. Require the obtaining F.9 Bridge and the separate affirmative C.2.1 claim for this translation before deriving a scope, then require the current A.10 or B.3 reliance branch before the receiving guard relies on it. A different reference scheme or location label alone is not such a trigger.

A.2.6:10.2 - Claim-scope guard family

EG-1 - Exact membership.

member(TargetSlice, ClaimScope) = true

Name the claim-bearing episteme, U.ClaimScope, and target slice. The episteme, scope, and slice remain different values.

EG-2 - Formality or evidence, only when current. A receiving state may separately require a C.2.3 condition on expression properties, possibly abbreviated by a justified local threshold, or an A.10 freshness judgment.

EG-3 - Unknown evaluation. When a required selector, designation resolution, or translation input is unavailable, return unknown as the result binding of the exact evaluateMembership application, or as the result of the directly governed evaluation when no reusable application is current. Abstain or follow the exact receiving reliance policy; do not assert member = false. Add a C.2.1 result episteme only when a named receiving use needs the conclusion to persist. Use A.15.PROD only when the current claim is that dated work first constituted that episteme.

EG-4 - Translation. When exact local senses differ, require the obtaining F.9 Bridge and the separate affirmative C.2.1 claim naming this scope translation’s direction, rule, and tolerance. After the exact A.10 or B.3 branch supports reliance for that use, derive the scope with deriveTranslatedScope(SourceScope, ExactBridgeOccurrence, ExactUseClaim, TargetReferenceScheme), then use that returned scope in evaluateMembership. Scheme difference alone does not select this branch.

EG-5 - Scope-value versus declaration change. Widen or narrow only when the extension gains or loses at least one independently identified slice; that extension change identifies another U.ClaimScope. A changed predicate expression with the same exact extension is a refit: it preserves the exact scope value and may require another scope declaration or claim-bearing episteme edition under its direct governor. A result-record, table, or selected-structure change alone changes neither the scope value nor its declaration.

A.2.6:10.3 - Method–Work guard families (capabilities)

WG‑1 - WorkScopeCoverage (mandatory). Reliance on a holder-ability claim for a Work step requires coverage by the WorkScope that claim designates:

WorkScope(holderAbilityClaim) covers JobSlice

WG‑2 - work-measure target set satisfied (mandatory for deliverables). Guards MUST compare the claimed attained bounds with the quantitative targets required for the JobSlice:

SLO and target measures satisfied (latency ≤ L, throughput ≥ T, tolerance ≤ ε, … )

WG‑3 - qualification-window policy holds (mandatory for operational use). Operational guards MUST assert that the exact qualification-window predicate (qualification, inspection, or recertification) holds at the receiving guard’s exact evaluation time:

qualificationWindowHolds(holderAbilityClaim, qualificationWindowPolicy, evaluationTime) = true

WG-4 - Translation branch for capability use.

Translate U.WorkScope only when its condition predicates use exact local senses that differ from those needed by the job slice. Require the obtaining F.9 Bridge and a separate affirmative C.2.1 claim naming this Work-scope translation’s direction, rule, and tolerance; establish the exact A.10 or B.3 reliance branch before the capability guard uses the result. Neither the holder-ability claim nor the job slice supplies a hidden .Context field that automatically selects this branch.

Observed mapping loss is evidence about the use claim, and permitted loss is its tolerance. If the claim’s rule and tolerance permit translation only for part of the source Work scope, identify that part and return its target image.

WG‑5 - Δ(WorkScope). When widening Work scope (new operating ranges/platforms), the guard MUST require evidence at the new slices (measures + qualification windows). A membership-preserving refit does not itself require new deliverability evidence for the unchanged slices.

A.2.6:10.4 - Translation guard

Use this branch only after the exact local-sense translation need, the obtaining F.9 Bridge, and the separate affirmative C.2.1 claim for this translation are current. The claim names the source-to-receiving direction, scope-correspondence rule, and tolerated loss. Before the receiving guard relies on it, require the exact passing A.10 branch or, when an actual named assurance claim is current, a B.3 AssuranceResult that carries the same bounded use with disposition=supported-for-use.

translatedScope := deriveTranslatedScope(SourceScope, ExactBridgeOccurrence, ExactUseClaim, TargetReferenceScheme)
membershipResult := evaluateMembership(TargetSlice, translatedScope, InterpretationBasis)

The source claim-bearing episteme designates SourceScope. The Bridge relates exact local senses under F.9. The C.2.1 claim supplies this translation’s rule and tolerance, and A.10 or B.3 supplies the separate reliance basis. An unmapped slice yields unknown for the attempted evaluation unless the returned scope explicitly excludes it; it is not silently dropped and reported as false.

A.2.6:10.5 - Time selector

When membership depends on time, name an exact gammaTime point, interval, or policy and the boundary that changes membership. Keep every selector already declared in the slice schema, even when this predicate does not inspect it. If a work qualification or evidence-freshness condition varies with time, name its exact evaluation time and interval or policy under that condition’s direct governor rather than copying it into scope. For example, qualificationWindowHolds(holderAbilityClaim, Recertification90d, evaluationTime) is a separate guard; it is not a scope selector.

Do not write implicit “latest.” Do not add a time selector merely to complete a new slice declaration.

A.2.6:11 - Archetypal Grounding - Worked Examples

A.2.6:11.1 - Claim-scope membership boundary

Claim-bearing episteme E_adhesive states that Adhesive X retains at least 85 percent tensile strength on Al6061 for two hours at 120-150 °C under rig edition Calib-v3. It designates claim scope G_adhesive.

  • slice_in = {substrate=Al6061, temp=140°C, dwell=90min, rig=Calib-v3}. member(slice_in, G_adhesive) is true.
  • slice_out = {substrate=Al6061, temp=160°C, dwell=90min, rig=Calib-v3}. Membership is false; the attempted use stops.
  • slice_unknown = slice_in, evaluated with an interpretation basis whose required rig-edition resolution is unavailable. Evaluation returns unknown; it neither excludes the slice nor permits the use.

LabEvaluator_A may perform membership-evaluation work through the declared USM operation. When a named audit or replay use needs a judgment to persist, a C.2.1 episteme may record it. A table showing the three rows is a C.29 representation.

The same G_adhesive may participate in two independently governed model-applicability relation occurrences and may be referred to by exact applied constraint claims in two A.22 structures. Only a selected obtaining model-applicability occurrence or an exact constraint claim as applied contributes through its corresponding A.22 discriminator; the common scope itself contributes through neither path and neither merges nor identifies the relations or structures. A declared applicability interval in either occurrence description is separate from the actual maximal continuous obtaining extent.

A.2.6:11.2 - Translation only when local senses require it

An assembly use expresses temperature through an exact local calibration sense different from the laboratory sense used in G_adhesive. F.9 Bridge B-lab-assembly-temp obtains between those two cells under its calibration-correspondence profile; the profile contains no translation-use rule or loss tolerance.

Separate C.2.1 claim C-adhesive-scope-translation has that Bridge as EntityOfConcern and affirmative polarity. Its content names use translate G_adhesive for the assembly membership check, direction laboratory-to-assembly, the calibration rule for mapping the source interval, and tolerance no selector-meaning loss and at most 2 °C boundary uncertainty.

Use that translation only while A.10 relation EP-adhesive-scope-translation connects the claim and that bounded use to evidence record CalibrationComparisonRecord.Calib-v3-to-AssemblyCalibration-v5.2026-07-25. Provenance edge CalibrationComparisonRecord.Calib-v3-to-AssemblyCalibration-v5.2026-07-25 --carriedBy--> CalibrationComparisonRegister.Calib-v3-to-AssemblyCalibration-v5.2026-07-25.csv names its carrier. The window runs from 2026-07-25 through 2026-10-23 and closes earlier if either calibration edition, the mapping rule, or the 2 °C tolerance changes.

The path supports neither reverse translation, a mapping outside the named rule or tolerance, nor a claim that the A.6.1 application or membership evaluation occurred. If the record, carrier, or provenance edge is missing or stale, or the window closes, stop before translation and set RelianceDisposition=reopen; otherwise RelianceDisposition=pass applies only to this bounded use. No assurance claim is made.

For this worked case, let the named calibration rule associate each assembly reading t with possible laboratory temperatures in [t−2,t+2]°C, throughout the range being considered. Let the acceptance rule require this whole interval to lie within the supported laboratory range [120,150]°C. Then t−2 ≥ 120 and t+2 ≤ 150, so the accepted assembly readings are [122,148]°C.

These are assumptions of this example; a boundary-uncertainty limit alone does not supply the calibration rule or the acceptance rule. With the other selectors preserved, the actual A.6.1 application deriveTranslatedScope(G_adhesive, B-lab-assembly-temp, C-adhesive-scope-translation, AssemblyReferenceScheme) returns the scope with this temperature range. The receiving membership evaluation uses that scope.

If the receiving use merely uses another designation for the same sense under an ordinary resolvable reference scheme, introduce no Bridge, use claim, or translation.

A.2.6:11.3 - Capability: robotic weld Work scope

  • Context: RobotCell‑Weld@2026.
  • Holder and ability claim: WeldRobot_3; WeldAbilityClaim states that this System can weld seam W at bead width 2.5 ± 0.3 mm and cycle ≤ 12 s under the conditions below.
  • Work scope: {humidity<60 %, current∈[35,45]A, wire=ER70S‑6, controller=FW‑2.1}.
  • Job slice: {humidity=55 %, current=40A, wire=ER70S‑6, controller=FW‑2.1}.
  • Qualification policy: in this example, Recertification90d considers reliance on WeldAbilityClaim qualified for 90 days from the certification date recorded in the controller certificate.
  • Qualification evaluation time: 2026-07-25, outside the Work-scope tuple.
  • Guards (WG‑1..3): coverage true; measures satisfied; qualificationWindowHolds(WeldAbilityClaim, Recertification90d, 2026-07-25) is true because certification occurred on 2026-05-26.
  • Outcome: the capability-related guards pass for this Work. Authority, assignment state and other required entry conditions remain separate.

Controller certificate age does not change Work-scope membership in this case. When the 90-day qualification condition fails, WG-3 stops operational use without removing the Job slice from the scope.

A.2.6:11.4 - Serial intersection (API + dataset compatibility)

  • Claim A (API Standard): v2.3 request schema with constraint “idempotent under retry”.
  • Claim B (Dataset cohort): “metrics valid for cohort K with schema ds‑14”.
  • Composition: service S depends on both A and B → serial intersection of Claim scopes: {api=v2.3} ∩ {cohort=K, schema=ds‑14}.
  • Target slice: {api=v2.3, cohort=K, schema=ds‑14} → membership true.
  • Target drift (e.g., ds‑15). The changed target slice lies outside the intersection ⇒ path inapplicable for that slice.

A.2.6:11.5 - Parallel support (SpanUnion) in a safety case

  • Line L1: tests on dry asphalt support braking property; scope S1={surface=dry, speed≤50 km/h}.
  • Line L2: simulations for wet asphalt; scope S2={surface=wet, speed≤40 km/h}.
  • Independence basis: partition P-braking identifies complete disjoint essential-component sets for this braking claim: L1 uses DryTrackTestRecord and DryRigCalibration; L2 uses WetBrakeModel, WetValidationRecord, and WetRigCalibration.
  • Published scope: SpanUnion({S1,S2}) = {(dry, ≤50), (wet, ≤40)}, with reference to P-braking.
  • Guard: allowed; union does not include (wet, 45) because not supported.

With only the method labels, leave P-UNION unresolved. If CalibrationRecord-Q is essential to both lines, P-UNION fails for this pair; retain the individual lines and use their component scopes to assess any dependent combination.

A.2.6:11.6 - ML model deployment with different local feature senses

  • Model claim: “AUC >= 0.92 on cohort K, pipeline P, feature sense Training.F.”
  • Claim scope: {cohort=K, pipeline=P, exactLocalSense=Training.F}. No gammaTime selector is present because this example does not claim that model applicability changes with the slice time.
  • Target slice: product On-Device@v7, pipeline P-prime, feature sense Device.F-prime.
  • Translation trigger: ordinary designation resolution fails because Training.F and Device.F-prime have different declared semantics, not merely different labels. F.9 Bridge B-training-device-feature obtains between those cells under a lossy-subset correspondence profile; the profile carries no device-use rule or tolerance.
  • Bounded translation claim: current C.2.1 claim C-device-feature-scope-translation has that Bridge as EntityOfConcern and affirmative polarity. It names use translate the training claim scope for the On-Device@v7 membership check, direction training-to-device, the subset-mapping rule, and tolerance no feature-kind substitution and no target slice outside the tested mapped subset.
  • Evidence and reliance: Before translating, verify that A.10 relation EP-device-feature-scope-translation connects claim C-device-feature-scope-translation and this bounded use to both records below.
    • Mapping evidence: MappingTestRecord.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25, with carrier edge MappingTestRecord.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25 --carriedBy--> MappingTestReport.TrainingF-to-DeviceFprime.OnDevice-v7.2026-07-25.json.
    • Training evidence: TrainingEvaluationEvidence.K-P-TrainingF.2026-07-25, with carrier edge TrainingEvaluationEvidence.K-P-TrainingF.2026-07-25 --carriedBy--> TrainingEvaluationReport.K-P-TrainingF.2026-07-25.json.
    • Window and stop: the 180-day window runs from 2026-07-25 through 2027-01-21 and closes earlier if pipeline P or P-prime, either feature-sense edition, or the tested mapped subset changes. If a record, carrier, or edge is missing or stale, the window closes, or a named dependency changes, stop before translation and set RelianceDisposition=reopen; otherwise RelianceDisposition=pass applies only to this bounded use.
    • Boundary: the path supports neither feature-kind substitution, a target outside the tested subset, material release or assurance, nor a claim that deployment occurred. No assurance claim is made; a material release use stays with its direct release rule, and an actual assurance claim uses B.3.
  • Guard: bind translatedScope := deriveTranslatedScope(G, B-training-device-feature, C-device-feature-scope-translation, ProductReferenceScheme), then evaluate evaluateMembership(TargetSlice, translatedScope, InterpretationBasis); separately require the chosen formality predicate. The translated scope covers only the tested mapped subset.
  • Outcome: admit only a target slice in the returned subset; otherwise return false or unknown according to the returned scope and available evaluation input.

A.2.6:12 - Bias-Annotation

USM counters three recurring biases. First, scope wording can hide a claim that the object is usable everywhere; require an addressable U.ContextSlice instead of a vague domain phrase. Second, abstract wording can be mistaken for wider scope; keep abstraction tier and detail separate from U.Scope. Third, publication convenience can be mistaken for content permission; U.PublicationScope bounds the publication surface and does not widen U.ClaimScope or U.WorkScope.

A.2.6:13 - Conformance Checklist (USM)

IDRequirement
CC-USM-1 Exact values.Name one exact scope and one exact U.ContextSlice; do not substitute a context label, domain phrase, table, or selected structure.
CC-USM-2 Sole delimitation predicate.member(slice, scope) is the primitive delimitation semantics. ScopeDelimitationRelation, ScopeDelimitationMode, and ScopeDelimitationInterval are absent.
CC-USM-3 Included, excluded, unknown.True admits the scope condition, false stops it, and unknown reports an undecided evaluation rather than exclusion.
CC-USM-4 Evaluation separation.The acting system, method, dated evaluation work, direct relation or A.6.1 binding, optional C.2.1 result episteme, and evidence use remain separate from predicate truth. An unknown result binding does not require that episteme; A.15.PROD applies only to a separately current identity-inception claim.
CC-USM-5 No membership occurrence by default.A.2.6 admits no membership-relation kind. A receiving use requiring occurrence identity needs an independently admitted direct relation with exact participant meanings, obtaining condition, recurrence rule and occurrence identity under A.6.REL.
CC-USM-6 Structure separation.A bare scope, slice, membership outcome, or displayed boundary never enters A.22 identity. An exact U.ClaimScope remains a participant of its independently governed ModelApplicabilityRelation; selecting that exact occurrence contributes through the relation-occurrence discriminator. Separately, an exact applied constraint claim may refer to that scope and contribute through the applied-constraint discriminator. Neither path makes the scope a constituent, a membership occurrence, or a second delimiter.
CC-USM-7 Applicability interval.One exact U.ClaimScope participates in ModelApplicabilityRelation; a declared interval stays in assertion or occurrence-description content, while the actual occurrence extent is derived from maximal continuous obtaining.
CC-USM-8 Set algebra.Intersection, independently supported spanUnion, widen, narrow, and refit operate on exact scope values; refit preserves membership.
CC-USM-9 Translation boundary.translate uses an exact obtaining F.9 Bridge plus a separate affirmative C.2.1 claim naming the use, direction, rule, and tolerance. A receiving guard requires A.10 pass for ordinary reliance or, when an actual named assurance claim is current, a B.3 AssuranceResult for the same use with disposition=supported-for-use; scheme or label difference, a profile, or a card supplies none of these.
CC-USM-10 Representation boundary.A set expression, query, table, graph, or diagram is a C.29 representation of an independently identified scope or evaluation result.
CC-USM-11 Time only when material.Name gammaTime and its membership boundary when time changes membership; never use implicit “latest.” A time-independent predicate need not inspect gammaTime; retain every selector already declared in the slice, and do not add one merely to complete a new declaration.
CC-USM-12 Separate reliance.Evaluate any required freshness, formality, time-currentness and assurance conditions separately from membership. The gate decision remains under A.21. A.10 governs ordinary reliance on a cross-scheme translation claim; B.3 applies only to an actual named assurance claim. Either result supports only its named use; neither authorizes that use. unknown remains an evaluation result used by the receiving guard; it does not change the scope.
CC-USM-13 Publication and capability specializations.U.WorkScope and U.PublicationScope reuse the same value and membership boundary; their measures, qualification, publication, and carrier relations remain separately governed.

A.2.6:14 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it is wrongRepair
Context label as membershipA project, room, domain, or model-use label does not supply the exact slice selectors.Name the exact U.ContextSlice and evaluate member(slice, scope).
Evaluation-created membershipPerforming work or writing a positive result is treated as making membership true.Keep predicate truth, evaluation work, result episteme, and evidence separate.
Unknown as excludedMissing data is coerced to false.Return an unknown evaluation result and abstain, narrow the use, or obtain the missing input; persist it only when a named receiving use needs a C.2.1 episteme.
ScopeDelimitationRelation reboundIncluded and excluded slices are reified as direct occurrences.Use the primitive membership predicate; admit no occurrence without the full A.6.REL identity settlement.
Unbounded complement objectEvery non-member is gathered into an exclusion entity.State predicate false for the tested slice; do not materialize the complement.
Table-created obtainingA row, edge, query result, or diagram is treated as membership or scope identity.Treat it as a C.29 representation of an independently declared scope or evaluation result.
Scope-as-structureA bare scope, slice, membership outcome, or displayed boundary is treated as an A.22 constituent or identity discriminator.Keep the exact U.ClaimScope as a participant of its independently governed ModelApplicabilityRelation: only a selected exact occurrence contributes through the relation-occurrence discriminator. If an exact applied constraint claim refers to that scope, the claim contributes separately through the applied-constraint discriminator. The bare scope contributes through neither path and is never copied as a second delimiter.
Interval-as-participantA declared applicability interval is copied into the direct relation signature.Keep it in assertion or description content and derive actual extent from continuous obtaining.
Silent translationA different scheme, label, or location automatically invokes a Bridge or lets the Bridge define the receiving use.Translate only after naming exact local senses, an obtaining F.9 Bridge, a separate affirmative C.2.1 claim for the direction, rule, and tolerance, and the current A.10 or B.3 reliance branch.
Implicit “latest”A time-dependent predicate cannot be reproduced.Name the temporal selector and its membership boundary when time matters; keep every selector already declared in the slice.
Unsupported unionspanUnion claims areas not supported by independent lines.State the independence basis or use intersection/narrower supported scope.

A.2.6:15 - Consequences

A correct USM use makes scope checks reproducible: every judgment names an exact scope and slice, and true, false, and unknown evaluation results have different actions. Translation appears only for exact local senses after an obtaining F.9 Bridge, a separate affirmative C.2.1 claim about the proposed translation, and its current A.10 or B.3 reliance branch are distinguished. The cost is naming the selectors, mapping rule, tolerated loss, and evidence that affect the receiving use while keeping membership truth, operation application, result epistemes, representations, model applicability, and structure separate.

A.2.6:16 - Playbooks (Informative)

A.2.6:16.1 - Using a scope

  1. Name the claim and exact scope. Do not start from a context label or table.
  2. Name the target slice. Bind the full independently identified slice as targetSlice; put the selector resolutions and translation inputs needed by this evaluation in interpretationBasis.
  3. Translate only when needed. Use ordinary designation resolution first. If the membership predicate needs translation between exact local senses, name the obtaining F.9 Bridge and the separate affirmative C.2.1 claim for this translation’s direction, rule, and tolerance. Derive the scope for the target reference scheme and establish its A.10 or B.3 reliance branch before using the returned scope.
  4. Evaluate membership. Use the returned translated scope when step 3 derived one; otherwise use the named scope. True admits the scope condition; false stops it; unknown calls for abstention, obtaining the missing input, or narrowing the attempted use.
  5. Keep other checks separate. Evaluate any required freshness, formality, time-currentness and assurance conditions separately, along with capability measures and qualification when required. The gate decision remains under A.21.
  6. Persist only what the use needs. A C.2.1 result episteme may record the judgment when a named receiving use needs it to persist; a C.29 table may display it. Use A.15.PROD only when the current claim is that the work first constituted that episteme.

A.2.6:16.2 - Declaring and combining scopes

  • Make membership conditions explicit. Name the parameters, ranges and standard editions that affect membership. Ordinary prose can express the predicate when its meaning is recoverable; name gammaTime only when time affects membership.
  • Factor common conditions. Use Refit to normalize units and factor shared predicates while preserving membership.
  • Partition support lines. If you plan a SpanUnion, document independence up front.
  • Publish supported scope. When widening is needed, add only supported slices (ΔG+).
  • Prepare needed translations. When the receiving use needs a translation, establish the F.9 Bridge, then state the proposed use with its direction, mapping rule, tolerated loss and evidence plan. Establish the §7.5 reliance condition before using the mapping.

A.2.6:16.3 - Minimal DSL snippet for scope blocks (illustrative)

claimScope:
  effectiveReferenceScheme: MaterialsLabScheme@2026
  Standards:
    - rig: Calib-v3
    - api: v2.3
  env:
    substrate: Al6061
    temp: [120, 150] # °C
    dwell: { max: "2h" }
receivingGuards:
  evidenceProvenanceUse:
    relevance_window_days: 365 # A.10/R guard, not Claim scope

The specification does not mandate a particular syntax.

A.2.6:16.4 - Profiles as Scope configurations (informative)

Idea. A Scope profile is a named, editioned configuration that expands to a concrete U.Scope predicate block (over U.ContextSlice), used to avoid repetition and to keep declarations consistent across carriers.

Rules.

  • P1 (Expansion). Profiles are macros: guards MUST expand them to explicit predicates before evaluating Scope covers TargetSlice.
  • P2 (Edition). Profiles are editioned. A changed predicate expression changes the profile declaration even when the exact scope extension is preserved; a changed extension additionally identifies another scope value.
  • P3 (Explicit widening). A profile update MUST NOT implicitly widen a carrier’s published scope; ΔG+ must be explicit in that carrier.
  • P4 (Translation awareness). If a profile expands to predicates whose exact local senses require translation, name the obtaining F.9 Bridge and the separate affirmative C.2.1 claim for that translation’s direction, rule, and tolerance. The receiving guard must recover the current A.10 or B.3 reliance branch; a different label, scheme, profile, or Bridge Card alone is insufficient.
  • P5 (No hidden context container). A profile expands to predicates; it is not a context object, scope pattern, or additional scope kind.

Examples (illustrative).

  • An engineering team defines Ops-Lab-v3 as a profile pinning standard editions and environment selectors. It leaves LabEvidenceRelevanceWindow365d to the receiving A.10/R guard and contains no gammaTime, because evidence age does not change scope membership.
  • A field team defines WinterCampaign-v1 with gammaTime in [2026-11-01, 2027-03-31] because the scope predicate admits only slices during the declared winter campaign; a slice before or after those boundaries is a non-member.
  • A publication stack defines TechCard‑Lite@Σ as a profile that narrows U.PublicationScope to slices where required pins are available.

A.2.6:17 - Governance Hooks & Audits

A.2.6:17.1 - Durable audit evidence, when needed

When a scope-aware decision needs durable audit evidence, its C.2.1 result episteme may name:

  • Using object and exact scope. The claim-bearing episteme, qualified holder-ability claim, or publication object designates or uses the exact scope.
  • Exact target slice. Designate the independently identified slice with its complete declared selector schema and values. Bind the full slice as targetSlice; put the selector resolutions and translation inputs needed by this evaluation in interpretationBasis. Include gammaTime in the schema only when that temporal selector is part of the exact slice being evaluated.
  • Evaluation outcome. Record true, false, or unknown, plus the evaluation method or work occurrence when replay needs it.
  • Separate guard outcomes. Record work measures, qualification windows, formality, or freshness only when the receiving use checks them; none is membership.
  • Translation evidence, only when triggered. Name the exact obtaining F.9 Bridge, the separate C.2.1 claim with its polarity, use, direction, rule, and tolerance, and the exact A.10 or B.3 reliance branch. Record any observed loss as evidence rather than a Bridge identity field.
  • Scope change. Say whether the declared set widened, narrowed, or remained identical under refit.

A.2.6:17.2 - Illustrative USM use configurations

The following descriptions identify different uses; select the one needed by the receiving task.

  • USM-Ready. Exact scope and slice values are declared; editors can distinguish membership from evaluation, evidence, representation, and structure.
  • USM-Guarded. Guards evaluate exact Claim scope or Work scope membership, including gammaTime in the scope predicate only when time changes membership. Measures, qualification, and freshness remain separate checks.
  • USM-Auditable. Durable result epistemes identify the exact scope, slice, and evaluation result. When translation was triggered, they cite the obtaining F.9 Bridge, separate bounded-use claim, and current A.10 or B.3 reliance.
  • USM‑Composed. Serial intersection and SpanUnion are implemented in composition tooling.

A.2.6:17.3 - Audit checklist (informative)

  • Does each guard name a concrete TargetSlice?
  • Is membership reproducibly evaluable from the exact declared predicate and required inputs?
  • Are freshness and coverage separate predicates?
  • When exact local-sense translation was required, are the obtaining F.9 Bridge, separate C.2.1 use claim, direction, rule, tolerance, polarity, and current A.10 or B.3 reliance branch named?
  • For parallel support: is independence justified?

A.2.6:17.4 - Risk controls (informative)

  • Silent widening. Require ΔG+ review; flag any scope increase without new direct support. A Bridge may translate supported conditions but does not supply support.
  • Opaque slices. Disallow “domain” placeholders; enforce addressable selectors.
  • Time drift. Require an exact gammaTime boundary only when the scope predicate itself changes membership across time; keep qualification, calibration, recertification, data-age, and evidence-freshness windows under their direct guards.

A.2.6:18 - Extended FAQ (informative)

Q1. Is “Claim scope” the same as “domain”? No. “Domain” is descriptive and often fuzzy. Claim scope is addressable: it supplies an exact predicate over the U.ContextSlice selectors that determine membership, including gammaTime only when the predicate changes membership across time. Guards reference the exact slice, not a generic domain.

Q2. How do we express partial coverage across different cohorts or platforms? Declare each supported serial scope (S₁, S₂, …) and publish SpanUnion({Sᵢ}) with independence justification. Do not include unsupported slices.

Q3. Can raising F (formalizing) widen G? Formalization alone does not widen scope. Widening requires a changed extension and direct support for every added slice under §7.6; changing only the expression can preserve the same scope.

Q4. What is the difference between Work scope and SLOs? Work scope names the work conditions covered by the holder’s ability claim; SLO targets name required performance levels. At use time, check scope coverage and compare the claimed performance bounds with those targets, together with the required qualification check (WG‑1..3).

Q5. Can we assign numeric coverage to G? Not normatively. G is set‑valued. You MAY attach an informative, explicitly declared CoverageMetric(G) (e.g., a proportion under a pinned policy) to aid R assessment, but guards use set membership and CoverageMetric(G) MUST NOT replace G.

Q6. How do we handle “latest data” scopes? First decide what “latest” is doing. If it means that evidence or data must be no older than 90 days, do not put it in Claim scope: require the A.10 evidence-provenance path to satisfy its exact 90-day relevance or currentness window at the receiving use time. Put gammaTime in the scope only when claim applicability itself changes with the slice time, and state the membership boundary—for example, slices whose observation time falls outside the declared interval are non-members. The word “latest” alone supplies neither boundary.

Q7. How do we use a scope with differently named slice selectors? First resolve whether the designations refer to the same values under the effective reference scheme. If exact local senses differ and membership must be expressed across them, name the obtaining F.9 Bridge. Then state the separate affirmative C.2.1 claim for the proposed translation’s direction, mapping rule, and tolerated loss, establish the exact A.10 or B.3 reliance branch, and evaluate the scope returned by deriveTranslatedScope.

Q8. What about abstraction level or detail? Keep AT (AbstractionTier) and D (Detail and Resolution) as orthogonal, optional annotations. They never substitute for Claim scope or Work scope.

Q9. Can a capability’s Work scope be broader than a predecessor claim’s Claim scope on a dependency path? Claim scope bounds where a claim holds; Work scope bounds the work conditions of a qualified ability claim. If the receiving use depends on both, its effective scope is their intersection. Neither replaces the other because it is broader.

Q10. When does an empty scope make sense? No slice satisfies the declared predicate, so the receiving guard stops. This may occur during early drafting or after a refutation.

A.2.6:19 - Annexes (informative)

A.2.6:19.1 - Source wording -> USM dictionary

Source wordingUSM term
applicability (of a claim)Claim scope (G)
envelope (of a requirement/spec)Claim scope
generality GClaim scope (G)
capability envelopeWork scope
validity (when it denotes a scope condition)Claim scope or Work scope, according to the receiving use
operational applicabilityWork scope
publication or view applicabilityPublication scope

Interpret these source terms in their own use. In a guard or conformance claim, identify the exact FPF scope kind and membership predicate.

A.2.6:19.2 - Minimal data model hints

ContextSlice tuple (suggested keys): effectiveReferenceScheme, one exact declaredSelectorSchema, the values of every selector in that schema, and optional selector families such as exactLocalSenseRefs, standardOrInterfaceEditions, environmentOrPlatformSelectors, cohortOrJurisdictionSelectors, and gammaTime when that selector belongs to the declared schema. A scope predicate declares which projection it inspects; it does not define the tuple’s identity.

Claim-scope predicate block: assumptions, cohorts, platformOrStandardEditions, environmentSelectors, exactLocalSenseRefs?, and gammaTime? when time changes membership.

Work-scope predicate block: environmentSelectors, platformOrStandardEditions, resourceRegimeSelectors, exactLocalSenseRefs?, and gammaTime? when time changes membership.

Publication-scope predicate block: the exact audience, interface, availability, and other selectors that restrict publication use, always within the underlying claim or work scope established under the applicable composition rule in §7.

Separate use-time guard: work-measure targets, qualification windows, evidence freshness, and any decision threshold. These are not fields of the scope value.

The specification does not mandate a concrete serialization.

A.2.6:19.3 - Pseudocode membership evaluation (illustrative)

def evaluate_membership(scope, target_slice, interpretation_basis):
    required = scope.required_inputs(target_slice)
    if not interpretation_basis.resolves_all(required):
        return UNKNOWN
    resolved_inputs = interpretation_basis.resolve(required)
    return TRUE if scope.predicate(target_slice, resolved_inputs) else FALSE

required_inputs identifies the selector resolutions and any translation inputs needed by this scope predicate under the bound interpretationBasis. resolves_all requires resolved values, not merely available keys or selector tokens; a present but unresolved rig token therefore yields UNKNOWN. The full slice remains bound as targetSlice; only the needed resolutions are supplied to predicate evaluation. UNKNOWN belongs to the evaluation result because a required input is unavailable. The underlying membership predicate remains bivalent for an exact, fully interpreted scope and slice.

A.2.6:20 - Rationale

USM expresses the set-valued conditions under which a claim, qualified ability claim or publication may be used. Membership makes those conditions composable while preserving the F/G/R distinction. When local senses require translation, F.9 supplies the Bridge, C.2.1 the separate claim about this use, and A.10 or B.3 the applicable reliance basis; A.2.6 governs the scope calculation and membership question.

A stated domain condition and its calibration calculation can answer a standalone mathematical applicability question. For the adhesive, apply the calibration rule and compare the resulting interval with the supported range. When that result is used by an FPF rule requiring scope membership, identify the condition as the required scope value, identify the target slice and perform the guard. Capability gating uses U.WorkScope and the other conditions of §10.3; claim use follows its Claim-scope guard. Neither case requires an additional result record unless the receiving use needs one.

USM’s additional result is an independently identified scope that further uses can compare, intersect across dependencies, combine across independently supported alternatives, or translate under declared rules. The API-and-dataset use in §11.4, for example, needs one common slice to satisfy both component scopes; a changed dataset edition changes that joint result. The domain argument supplies each applicability condition, the calibration or performance claim, and the justification for relying on it.

A.2.6:20.1 - SoTA-Echoing - Source distinctions and scope terminology

Intent. This annex compares USM terms with usage in the sources below and explains the Unified Tech and Plain names used in A.2.6.

A.2.6:20.1.1 - Comparison basis

Compared sources and the passages used here:

  1. ISO’s published scope for ISO/IEC/IEEE 42010:2022, Software, systems and enterprise — Architecture description.
  2. OMG Essence 1.2, October 2018, §9.3.3.5–9.3.3.7 and §9.3.4.9–9.3.4.11.
  3. NIST AI 100-1, AI RMF 1.0, January 2023, §3.1 and §5.2/MAP.
  4. FDA, Assessing the Credibility of Computational Modeling and Simulation in Medical Device Submissions, final guidance, 17 November 2023, §IV and §VI.A, including definitions attributed there to ASME V&V 40–2018.
  5. W3C SHACL, Recommendation, 20 July 2017, §2.1.2–2.1.3; SHACL Advanced Features, Working Group Note, 8 June 2017, §3.
  6. W3C OWL 2 Second Editions, Recommendations, 11 December 2012: Direct Semantics, §2.2–2.2.3 and §2.3.2–2.3.3; Structural Specification and Functional-Style Syntax, §3.1–3.4.
  7. IETF BCP 14: RFC 2119, March 1997, as clarified by RFC 8174, May 2017, §2.
  8. FAA AC 20-115D, 21 July 2017, §1, §4, §6, §8 and §10, describing use of RTCA DO-178C, DO-333 and DO-330 (13 December 2011).
  9. ISO’s published scope summaries for ISO 26262 Part 1: Vocabulary, Part 3: Concept phase and Part 9: ASIL-oriented and safety-oriented analyses, second editions, December 2018.
  10. IEC’s Overview of IEC 61508 & Functional Safety, 2022, slides 9–18, alongside its IEC 61508-1:2010 edition 2 description; HSE’s older Control systems, “Proof testing”, for the effect of test intervals on a failure claim.
  11. ACM Artifact Review and Badging v1.1 as applied in SIGSIM PADS 2022 and CCS 2025, “Evaluation Criteria and Badges” and “Packaging Artifacts”.
  12. Google, Site Reliability Engineering, Chapter 4: “Service Level Objectives”, especially “Standardize Indicators” and “Defining Objectives”.

Terms compared: U.ContextSlice, generic Scope and set algebra, Claim scope (G), Work scope, Bridge plus a separate bounded-use claim and reliance basis, Γ_time, widen, narrow, refit, translate, SpanUnion, serial intersection, separation from F and R, and avoidance of overloaded validity and operation terms.

A.2.6:20.1.2 - Source term comparisons
#Context / SourceLocal label(s) (native)Closest USM conceptNotes on fit & deltas
1ISO/IEC/IEEE 42010:2022, published scopeArchitecture description; entity of interest; architecture viewpoints; model kindsContext slice and Scope for a selected applicability question42010 specifies the structure and expression of architecture descriptions. A claim recorded in such a description may have a USM scope; construct its slices and predicate from that claim’s conditions. A viewpoint does not by itself identify those values.
2OMG Essence 1.2Alpha State; Work Product; LevelOfDetail; EntryCriterion; CompletionCriterionD for information detail; ESG for claim-use conditions in state transitions; A.2.5 for assignment-state conditions used in RSG; Scope for applicabilityEntry and completion criteria test an alpha state or work-product level of detail. Keep the information-detail aspect of LoD with D. Reuse a checklist condition in ESG or RSG only after identifying its claim-use or assignment-state meaning. Scope requires a separate condition delimiting applicable slices.
3NIST AI RMF 1.0, §3.1 and §5.2/MAPContext of use; targeted application scope; validity, reliability, robustness; monitoringClaim scope (G) for specified applicability conditions; performance measures and reliance grounds remain distinctMAP places application scope within purposes, settings, affected people and risks. Extract conditions for the claim’s scope predicate; preserve performance/risk assessment and monitoring. Interpret validity-related claims by content, and keep the source’s performance reliability distinct from FPF R.
4FDA final guidance (2023), §IV and §VI.A; ASME V&V 40–2018 definitions reproduced thereContext of use; model risk; credibility; verification and validationClaim scope (G) for extracted applicability conditions; R for justified relianceThe COU also states the model’s role in answering a question and its use with other evidence. Preserve that decision relation when expressing applicability as a scope. Credibility is assessed for that use and its model risk; scope membership alone does not establish it.
5W3C SHACL §2.1.2–2.1.3; SHACL-AF §3Shapes; focus nodes; targets (sh:targetClass; AF sh:target); constraintsTarget selection provides an analogy for delimiting applicability; F concerns expression propertiesSHACL targets produce RDF terms to validate; constraints determine their conformance. A USM scope contains declared U.ContextSlice values. Identify those slices and their membership predicate before using the analogy; target selection alone does not establish that a claim holds. C.2.3 assesses the expression properties.
6OWL 2 Direct Semantics and Structural Specification, Second EditionsClass extension; intersection/union; property domain/range; imports; version IRISet extension as an analogy for scope algebra; ontology editions as selectors or interpretation inputs when applicableClass extensions supply sets; property domain/range axioms imply membership of property-pair ends in specified classes or data ranges. Construct the corresponding USM slice domain independently. Imports supply ontology dependencies; version IRIs identify editions. An edition enters the slice when claim applicability depends on it; otherwise retain a required edition in the interpretation basis.
7IETF BCP 14: RFC 8174MUST/SHALL/SHOULD; requirements languageRequirement strength in normative guard statementsBCP 14 defines the special meanings of its uppercase requirement keywords. The observable, deterministic membership conditions are USM requirements; they do not follow from those keywords alone.
8FAA AC 20-115D on DO-178C, DO-333 and DO-330Software level; formal-methods supplement; tool qualification level (TQL); life-cycle objectives and evidenceF for expression and proof properties; R for justified reliance; scope kind follows the bounded claim or capabilityThe software level selects applicable objectives; the formal-methods supplement and tool qualification address distinct assurance work. A condition on a software or tool claim can delimit Claim scope, while a capability’s operating conditions can delimit Work scope. Neither a level label nor a method name supplies the resulting FPF scope or assurance judgement.
9ISO 26262:2018, published scope summariesItem definition; hazard analysis and risk assessment; functional safety concept; ASIL-oriented analysesClaim scope or Work scope for stated applicability conditionsAn operating situation or mode can supply a selector when it changes applicability of the receiving claim or capability. Item definition and safety analysis also determine domain requirements. Preserve those requirements and their evidence; an ASIL label alone supplies neither a scope nor a measured value of FPF R.
10IEC functional-safety overview; HSE control-systems explanationSafety function; SIL; demand/continuous mode; proof-test intervalClaim scope or Work scope for stated operating conditions; performance requirements and reliance grounds remain distinctSIL specifies safety-integrity requirements. A proof-test interval affects the basis of a failure-probability claim, so it cannot be reduced to evidence age. State which operating or maintenance condition bounds applicability and which support condition must hold before reliance.
11ACM artifact badging, PADS 2022 and CCS 2025Available; Evaluated—Functional/Reusable; Results Reproduced/ReplicatedEvidence relevant to R; Context slice when the evaluated environment is explicitly identifiedThe badges distinguish availability, artifact assessment and independent result checks. Use the badge criteria, checked claim and environment when assessing support; the badges do not form a single FPF warrant scale. An environment description supplies slice selectors only when their schema and values are made explicit.
12Google SRE, “Service Level Objectives”SLIs; SLOs; measurement windows; workload classes; error budgetsPerformance measures; Claim scope or Work scope for stated service conditionsKeep metric definitions and aggregation windows with their measures. A workload class or region enters a scope when it changes applicability. In a USM rollout example, gammaTime enters scope only when crossing the declared start or end changes membership; an error-budget window alone does not establish that boundary.

These comparisons suggest two useful questions: which conditions matter to the receiving use, and under which of them the claim or ability applies. A.2.6 answers them with independently identified slices and set-valued scopes. Choose Claim scope or Work scope from what is being bounded; the source term alone does not choose the scope kind. Preserve the source’s decision relation, performance measures, safety requirements and evidence where the receiving use depends on them. Any relied-on translation follows §7.5.

A.2.6:20.1.3 - Scope names and their use
A.2.6:20.1.3.1 - Selected names (normative)
Concept in A.2.6Unified Tech (lexicon)Unified Plain (manager‑friendly)Allowed short formAvoid / unpack
Addressable evaluation contextU.ContextSliceContext sliceSlice (when local)“domain” (as guard input), “latest” time
Extensional scope valueU.ScopeScope—“applicability”, “envelope”, “validity” (as characteristic names)
Claim applicabilityU.ClaimScope (*nick G)Claim scopeG“generality”, “applicability/envelope (of claim)”
Capability applicabilityU.WorkScopeWork scope—“capability envelope”, “operational applicability”, “operation scope”
Time selectorΓ_timeTime selector—implicit “latest”
Exact local-sense translationObtaining F.9 Bridge + separate affirmative C.2.1 use claim + current A.10 or B.3 relianceBridge, translation rule and tolerance, checked reliance—automatic Bridge use or treating a loss score as permission
Parallel coverageSpanUnionUnion of supported areas—unqualified “union” without independence
Serial dependencyIntersectionIntersection of scopes—ordinal “more/less general” language
Scope editsΔG+ (widen), ΔG− (narrow), Refit, TranslateWiden, narrow, refit, translate—implicit widening
Optional didacticsDetail (D), AbstractionTier (AT)Detail and abstraction tierD / ATavoid as G substitutes

Naming rationale:

  • “Scope”. This name designates the extension over independently identified slices; domain words such as “envelope” or “validity” require interpretation before that designation is warranted.
  • “Claim scope” vs “Work scope”. These names distinguish claim uses and capability uses of the common set-valued scope notion.
  • G names Claim scope in the F–G–R triple.
  • “Context slice” keeps the evaluation target addressable through its exact declared selector schema and values; one membership predicate may inspect only a projection without reidentifying the slice.
A.2.6:20.1.3.2 - Wording membership and scope changes
  • Use “Claim scope (G) covers TargetSlice” and “Work scope covers JobSlice” in guards.
  • When time changes membership, name exact gammaTime and its membership boundary; never say “latest.” A time-independent predicate need not inspect gammaTime, but keep every selector already declared in the slice.
  • To compose, say: “intersection along dependency paths; SpanUnion across independent support lines.”
  • When exact local-sense translation is current, say: “through an obtaining F.9 Bridge and a separate affirmative C.2.1 claim for this direction, rule, and tolerance; rely on it only through the current A.10 or B.3 branch, then evaluate membership on the returned scope.”
  • When widening or narrowing, write “ΔG+ / ΔG−”. If support for the affected slices changed, say what support was gained or lost. Use “Refit” for unit/parameter normalization only when the exact scope extension is preserved.
A.2.6:20.1.3.3 - Source-phrase comparison summary

Use these conditional paraphrases with the source distinctions in §20.1.2.

Local source phraseUse in USM wording
“Context of use” (NIST, FDA/ASME)Extract a particular claim’s applicability conditions into G on stated slices; preserve the wider decision context.
“Operating modes/situations”May supply selectors for Claim scope or Work scope, according to what is bounded; retain performance and qualification conditions.
“Target” (SHACL)Selects RDF terms for validation. Construct any corresponding slice domain and scope predicate separately.
“Class extension; property domain/range; imports/version” (OWL)Class sets supply an analogy; property axioms, ontology dependencies and edition identity keep their own meanings. Construct the corresponding Context slices separately.
“Architecture view context” (42010)Locate the claim and its conditions, then construct the relevant slice and scope; the view’s organization does not determine them.
“Capability envelope” (safety documents)Work scope when it delimits a capability’s job slices, with performance and assurance requirements retained separately.
“Domain” (informal)Unpack the intended conditions into declared selectors and a predicate before using them in a scope guard.

A.2.6:21 - Relations - Cross-Pattern Coordination

A.2.6:21.1 - With F–G–R (C.2.2)

  • G is Claim scope. Use set algebra (∩ / SpanUnion).
  • F remains the expression rigor (C.2.3); R describes warrant strength under the declared scope, evidence and use conditions (C.2.2). Observed loss may bear on the translation-use claim; its permitted-loss tolerance remains in that claim rather than in G or the Bridge profile.
  • Composition. F follows C.2.3:15.1: the essential content and connecting inferences must provide the expression properties claimed for the whole. R follows the justified support-composition model or non-aggregate synthesis under C.2.2. G follows §7.2–§7.3 (set rules).

A.2.6:21.2 - With Formality (C.2.3)

  • No conflation. Strengthening an expression property changes G only when the scope extension changes; a different expression alone can be a refit.
  • Guarding rigor. ESG may require named expression properties alongside scope coverage. A local ordinal threshold abbreviates them only under its declared C.2.3 scale and mapping.

A.2.6:21.3 - With Work & Run (A.15)

  • Work scope delimits the exact job slices on which a capability’s deliverability claim is evaluated.
  • Method–Work gates use Work scope coverage plus measures and qualification windows.

A.2.6:21.4 - With exact F.9 Bridge occurrences

  • Translation boundary. Use an exact F.9 Bridge only for exact local-sense translation. State the translation’s direction, rule, tolerated loss, and polarity in a separate C.2.1 claim. Before the receiving use proceeds, require A.10 pass for ordinary reliance or, when an actual named assurance claim is current, a B.3 AssuranceResult for the same use with disposition=supported-for-use.
  • Best practice. If the bounded-use claim’s rule and tolerance permit translation only for part of the source scope, identify that part and return its target image; do not turn observed mapping loss into a Bridge identity field or a generic R penalty.

A.2.6:21.5 - With Capability governance (A.2.2)

  • For operational capability use, the capability declaration MUST identify Work scope, measure bounds and the applicable qualification-window policy; gates MUST check coverage, target satisfaction and qualification under §10.3.
  • Capability refits that preserve the set (unit changes) are Refit, not Δ(WorkScope).

A.2.6:End

A.2.7 - SystemRoleKindRelationStructure - Relations among System-Role Kinds

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

A.2.7:0 - Use This When

Plain designation. Say “structure of relations among system-role kinds” for SystemRoleKindRelationStructure.

Use this pattern when several context-local system-role kinds are already admitted, and a later admission, allocation, or interpretation check needs one of these results:

  • an assignment to one system-role kind may satisfy a condition written for another kind;
  • two system-role kinds are incompatible under a stated holder rule, actual-Work or proposed-action identity condition, and temporal test;
  • several independently obtaining assignments are required together under one allocation rule; or
  • one system-role kind narrows another, and the practitioner must decide whether that narrowing is monotonic U.SubkindOf or a different residual relation.

Typical working moments include these:

  • a pressure-test MethodDescription names HydraulicsTechnicianSystemRole, while the proposed holder is assigned to SeniorHydraulicsTechnicianSystemRole;
  • the same system must not hold author and approver assignments for the same hazard-analysis Work during overlapping windows;
  • a surgical procedure needs surgeon, anesthetist, and scrub-practitioner assignments together, with three distinct holders;
  • RoboticsEngineerSystemRole may be a subkind of EngineerSystemRole, but neither a nested label nor one assignment can establish that order.

First useful result. Write the readable direct relation or U.SubkindOf claim needed by the receiving use. Recover its predicate. Stop there unless another claim needs one relation occurrence as an identifiable object or needs several obtaining relations selected into one structure.

Primary EntityOfConcern. For a direct question, first identify the relation kind or C.3.1 U.SubkindOf, the participant kinds and its predicate. An assertion about a recovered obtaining occurrence uses that occurrence as its EntityOfConcern; claims without such an occurrence follow §4.7. When several such occurrences must be selected together, it is one SystemRoleKindRelationStructure: a dependent U.Structure selected from local system-role-kind constituents and obtaining relations under the applied constraints and one named selection-use frame.

The structure contains neither holder systems nor system-role-assignment occurrences. A graph, taxonomy table, policy file, or organization chart may describe it but does not become the structure or any selected relation by form.

What goes wrong if missed. A job-title order is used as admission authority. An independence rule omits the holder, the actual Work or proposed action, or the temporal condition. A bundle name hides whether one or several systems must hold the assignments. A semantic restriction is called U.SubkindOf although a known broader classification can be false. A scheme or taxonomy edition is then inserted as a participant of every relation even when it changes no meaning.

What this buys. Admission substitution, incompatibility, joint allocation, monotonic kind order, and residual qualification remain different claims with different truth and identity laws. Holders remain systems, assignments remain direct species of U.SystemRoleAssignment, and the system performing a receiving check remains visible.

Not this pattern when. Use A.2 and C.3 to admit and classify local system-role kinds. Use A.2.1 for assignments and their holders, A.2.5 for SystemRoleAssignmentStatePredicate and SystemRoleAssignmentStateRelation, A.2.2 for capability, A.3 patterns for Methods, and A.15 patterns for planned or performed Work. Use F.9 and A.6.9 for an actual cross-scheme Bridge, then a separate bounded-use assertion and reliance decision. Use C.29 when a graph, matrix, algebra, embedding, or table is the object under evaluation.

A.2.7:1 - Problem Frame

A system applying a maintenance-admission Method may admit a current assignment to SeniorHydraulicsTechnicianSystemRole where the MethodDescription names HydraulicsTechnicianSystemRole. A system applying a safety Method may reject overlapping author and approver assignments. A clinical MethodDescription may state a joint condition over three assignments. A classification review may ask whether every true RoboticsEngineerSystemRole judgment implies a true EngineerSystemRole judgment.

These uses all concern system-role kinds, but they do not concern the same relation. The assignment occurrences used by a receiving check are also not participants of the kind relation. They remain independently obtaining A.2.1 relations whose holder, assigned kind, extent, and any real domain participant are recovered under their direct species.

A system-role-kind description or taxonomy episteme may state a relation claim, and its reference scheme may help interpret that claim. The world-side relation obtains under its direct predicate. When a KindSignature, scheme, Bridge, or other edition changes the relation rule, include that edition in the predicate’s semantic basis; otherwise keep it as interpretation material outside occurrence identity.

SystemRoleKindRelationStructure is the selected organization among kinds and obtaining relations. If the account asserts a dated checking Work, identify its performer through A.13 and admit the occurrence independently through A.15.1; add F.6 only when precise assignment attribution is needed. The selected structure supplies the organization used by the check.

A.2.7:2 - Problem

The practitioner needs a reusable relation for a later engineering check, but familiar shorthand collapses four different questions:

  1. Can an assignment to one system-role kind satisfy an admission condition written for another?
  2. Are assignments to two system-role kinds incompatible under a stated holder rule, actual-Work or proposed-action identity condition, and temporal test?
  3. Must assignments to a finite set of system-role kinds be present together, and how may holders be allocated?
  4. Does one kind monotonically narrow another, or does the restriction require a different relation?

Calling every answer a hierarchy loses the predicate. Calling the answer a role part introduces mereology without constructive assembly or a meta-holon transition. Calling the answer a policy, chart, taxonomy, or scheme confuses a relation with an episteme or convention that describes or interprets it. The receiving check then cannot show which premise it used or what change would invalidate the outcome.

A.2.7:3 - Forces

ForceTension
Reuse vs local meaningSeveral contexts may use similar labels while their local kinds and relation rules differ.
Direct relation realism vs socially constituted rulesA row does not create predicate truth, while some specialized social relations depend on an accepted act or decision named by their direct rule.
Readable claim vs occurrence identityOrdinary use should stop at a direct sentence, while a later assertion may need one relation occurrence.
Kind relation vs holder assignmentA relation among kinds may guide a check; each holder assignment must obtain under its own direct rule.
Monotonic order vs residual restrictionTrue subkind order must preserve every defined classification judgment; many useful semantic restrictions do not.
Joint admission vs compound kindSeveral assignments may be required together without creating a combined system-role kind.
Stable predicate vs changing semantic basisA compatible edition may preserve meaning; a changed rule or identity-bearing basis requires another predicate whose obtaining must be established.
Structure vs representationA graph or matrix can make organization inspectable without becoming that organization.

A.2.7:4 - Solution

Start with the one relation family needed by the receiving use. Use local system-role kinds as its participants and put the rule, applicability, and only meaning-changing semantic-basis editions in its by-value predicate. Current assignments, assignment-state relations, capability, evidence, and the receiving window remain inputs to the later check.

Build a structure only when several relation occurrences must be selected together:

SystemRoleKindRelationStructure : U.Structure
  systemRoleKindSubstrate:
    finite set of independently identified context-local system-role kinds, by value
  selectedSystemRoleKindRelationOccurrenceRefs:
    finite set of references to obtaining relation occurrences
  appliedConstraintClaimRefs:
    constraint claims applied in this selection; an empty set is stated explicitly
  namedSelectionUseFrame:
    question:
    admissibleAction:
    stopOrNonAdmissibleOverread:
      stop or return condition; also named stopOrReturnCondition

The structure specializes A.22’s four-part identity: the system-role-kind constituents, the selected obtaining relation occurrences, the constraint claims applied, and one named selection-use frame stating the question, admissible action, and stop or return condition. stopOrReturnCondition and stopOrNonAdmissibleOverread name that same condition, not two independently filled values.

A changed rendering, identifier, selecting Work, publication, table, or graph changes no structure while all four values remain unchanged. Replacing a constituent, selected relation occurrence, applied constraint, or use frame identifies another structure. Without a required constraint or named frame, the material is still an arrangement or description rather than an admitted SystemRoleKindRelationStructure.

A.2.7:4.1 - Direct Relation and Declaration Discipline

Substitution, incompatibility, bundle, and residual qualification are four families of direct relations under U.Relation. This pattern gives their different laws. Each context declares its direct species with local ValueKinds in its RelationSignature; A.2.7 does not introduce a permissive root signature or four additional universal Tech kinds over every possible system-role kind.

Apply the relation-object order from A.6.REL:

  1. recover the participant kinds and by-value predicate;
  2. establish from current facts or accepted constituting history whether the predicate obtains;
  3. individuate one occurrence only when a receiving use needs occurrence identity;
  4. assign a stable reference only when another episteme needs it; and
  5. keep assertion, evidence, reliance, and representation separate from the occurrence.

The three binary families declare individual system-role-kind slots. The bundle declares the order-insensitive finite-set slot in §4.5. Every species also declares a by-value predicate slot. Each individual kind slot has a context-local ValueKind; the bundle’s set ValueKind specifies the local kind domain of its members. A system-role-taxonomy episteme, effective reference scheme, KindSignature, Bridge, or selected model-use structure is not another generic participant. Include its edition in predicate identity only when the rule depends on that edition.

Establish predicate truth under the context-local rule. If a specialized direct relation obtains only through an accepted appointment, policy decision, installation, or other constituting act, the context-local predicate must name that act and its acceptance condition.

Logical form supplies argument order, set semantics, and relation laws. Use the direct rules to establish participant kinds and predicate truth, and to recover occurrence identity when the receiving use needs it. Use the relevant patterns when the claim also concerns a Method, Work, transformation, agency, constructive assembly, or holon admission.

If current facts concern one actual bounded change, make that change a separate subject and use A.3.4 to recover one U.Transformation at the resolution and boundary needed by the use. Name its affected entity, boundary, precondition, postcondition, and obtaining relations. Keep it distinct from the relation among system-role kinds, an assertion about that relation, and the Work that checks it. U.Transformation by itself supplies neither a transformation-composition predicate nor holonhood.

A.2.7:4.2 - Admission Substitution

Use the admission-substitution family when one assignment may satisfy a receiving condition written for another system-role kind. The relation is directional.

For a context-local species, declare:

<context-local admission-substitution relation species> : U.Relation
RelationSignature:
  CandidateSystemRoleKindSlot: candidate-kind domain, ByValue
  RequiredSystemRoleKindSlot: required-kind domain, ByValue
  AdmissionSubstitutionPredicateSlot:
    context-local admission-substitution predicate kind, ByValue

One predicate value is identified by the ordered candidate and required system-role kinds, the receiving-use rule, applicability, and only the semantic-basis editions that change that rule. Reversing the two kinds requires another predicate evaluation. A job-grade order, common word stem, or U.SubkindOf relation may be evidence or another premise; none is the substitution relation by itself.

Current assignments and any required A.2.5 state occurrences are inputs to the receiving check. They are not participants of the relation among kinds. Establish classification, assignment, capability, authorization, gate outcomes, and Work under their direct patterns as the receiving use requires them.

A.2.7:4.3 - Incompatibility

Use the incompatibility family when assignments to two system-role kinds cannot be jointly admitted under one rule.

For a context-local species, declare:

<context-local incompatibility relation species> : U.Relation
RelationSignature:
  IncompatibleSystemRoleKindSlot[1]: local kind domain, ByValue
  IncompatibleSystemRoleKindSlot[2]: local kind domain, ByValue
  IncompatibilityPredicateSlot:
    context-local incompatibility-predicate kind, ByValue

For the actual-Work species, the predicate is identified by the unordered pair of kinds, the same-holder or different-holder rule, Work identity condition, temporal-overlap test, applicability, and only meaning-changing semantic-basis editions. The relation obeys the symmetry law:

incompatible(k1, k2, p) = incompatible(k2, k1, p)

The assignments later evaluated are receiving inputs. A conflicting allocation is a case satisfying the incompatibility rule; it is not what creates the kind relation. A system applies the receiving Method and records the resulting admit, reject, defer, or unresolved outcome under the pattern for that decision.

Prospective incompatibility species. A local policy may separately declare a direct incompatibility species for allocation to a bounded proposed action before performance. Keep the same unordered kind-pair signature and symmetry law. Its by-value predicate must declare the same-holder/different-holder rule, proposed-action identity condition, temporal test over the intended allocation windows, applicability and only meaning-changing semantic-basis editions. This species does not replace the actual-Work condition with an arbitrary entity slot. Use an existing WorkPlan/action locator when available; otherwise the local action rule must identify what is proposed.

For a release-action species, identify the artifact edition, target environment, promotion operation and bounded intended window, and define how a reschedule continues or replaces that action. Repeated request forms for the same action select the same subject. If a continuation rule preserves an action across a changed window, the changed window still reopens any permission whose applicability depends on it. Proposed actions, requests, plans and gate results are not future Work individuals.

The kind relation can obtain under its constituting policy before any prohibited allocation occurs.

Actual assignments, their holders, the proposed action and intended allocation windows are receiving-test inputs. A known prohibited same-holder/action/overlap case supports rejection; missing required facts leave that receiving decision unresolved or deferred under A.21. Any independent authority and other gate conditions remain separate.

Once performance occurs, identify its Work under A.15.1 and match it to prior permission through the policy’s actual action-match rule. The actual-Work species and §4.6 continuity law remain unchanged.

A.2.7:4.4 - Monotonic Kind Order and Residual Qualification

When one system-role kind appears to narrow another, test C.3.1 U.SubkindOf first. Use that relation only when the paired classification judgments satisfy monotonicity under the aligned editions and effective-reference-scheme edition required by C.3.1:

for every candidate x in the defined comparison domain:
  judgment(x, NarrowerSystemRoleKind) = true
  implies judgment(x, BroaderSystemRoleKind) = true

The proposed U.SubkindOf edge is never a premise for either membership judgment. Direct feature criteria must establish both judgments independently. A known narrower true with broader false refutes the relation. An unavailable broader dependency yields unknown and leaves the order unresolved.

When the restriction is useful but non-monotonic, use a separate residual relation rather than weakening U.SubkindOf:

<context-local residual qualification relation species> : U.Relation
RelationSignature:
  QualifiedSystemRoleKindSlot: local qualified-kind domain, ByValue
  ReferenceSystemRoleKindSlot: local reference-kind domain, ByValue
  ResidualQualificationPredicateSlot:
    context-local residual-qualification-predicate kind, ByValue

The residual predicate names the restriction, applicability, orientation, and only meaning-changing semantic-basis editions. A receiving Method needing substitution must establish that separate directional relation.

A.2.7:4.5 - Joint-Admission Bundle

Use the bundle family when a receiving use needs assignments to a finite set of system-role kinds together and the holder-allocation rule matters.

For a context-local species, declare:

<context-local bundle relation species> : U.Relation
RelationSignature:
  BundledSystemRoleKindSetSlot:
    order-insensitive finite set of local system-role kinds, ByValue
  JointAdmissionPredicateSlot:
    context-local joint-admission-predicate kind, ByValue

The predicate is identified by the order-insensitive set, joint-admission and holder-allocation rule, applicability, and only meaning-changing semantic-basis editions. The predicate states which assignments may have the same holder, which require distinct holders, and how the receiving window is tested.

Current assignments and the receiving window remain inputs to the later check. The bundle specifies a joint condition over distinct system-role kinds. Use the applicable direct pattern when assignment, team, or Work identity is needed. A list of labels without a joint-admission and allocation rule is not a bundle relation.

A.2.7:4.6 - Occurrence Identity and Continuity

For substitution and residual qualification, one occurrence begins when fixed ordered kinds satisfy one fixed predicate. For incompatibility, the participant identity is the unordered pair. For a bundle, it is the order-insensitive finite set. In every case, the occurrence continues through the maximal uninterrupted interval during which the fixed predicate obtains for those fixed participants.

When a declaration, scheme, KindSignature, Bridge or other cited semantic-basis edition changes, compare the rule, orientation or set semantics, applicability, system-role-kind identities and meaning-bearing semantic basis. If these identity-bearing values remain unchanged, predicate identity is preserved. If a value changes, identify the changed predicate and establish whether it obtains for its participants; a new relation occurrence begins only when it does. If the comparison is unresolved, leave predicate continuity unresolved. Equal displayed labels establish no continuity.

An affirmative assertion or occurrence description may state the known systemRoleKindRelationExtent only after current facts or accepted constituting history satisfy the predicate and the identity rule recovers the occurrence. Closing an open extent refines the same occurrence when obtaining was uninterrupted. A demonstrated predicate-false gap ends it; later truth begins another. Missing evidence leaves reliance unresolved and does not demonstrate a truth gap.

systemRoleKindRelationExtent is content of an affirmative assertion or occurrence description, not a temporal SlotSpec. A target declaredSystemRoleKindRelationEvaluationWindow belongs to the receiving assertion or check and is not part of the direct relation signature or occurrence identity.

For U.SubkindOf, use C.3.1’s own obtaining law and participant-determined occurrence identity. The effective-reference-scheme edition qualifies the obtaining judgment. Do not replace that identity rule with the generic A.2.7 interval rule.

SystemRoleKindRelationStructure identity follows all four A.22 discriminators: kind constituents, selected relation occurrences, applied constraint claims, and the named selection-use frame. A scheme change that changes a constituent, selected relation, applied constraint, or use frame changes the structure; selecting System, Method, Work, result episteme, and publication remain outside identity.

A.2.7:4.7 - Assertion and Receiving Check

A relied-on kind-relation claim is a C.2.1 assertion episteme, not the relation occurrence. Keep these moves in order:

  1. name the direct relation family or U.SubkindOf, participant kinds, predicate, and applicability;
  2. establish whether current facts or accepted constituting history satisfy that predicate;
  3. when the receiver needs occurrence identity, apply the direct identity rule and recover the already obtaining occurrence;
  4. for an assertion about that recovered occurrence, use it as the EntityOfConcern and state its known extent; and
  5. add evidence, currentness, and reliance only when the receiving use needs them.

When no positive occurrence is recovered, a negative, candidate, counterfactual, or unsupported affirmative claim normally uses the admitted relation kind, or another independently identified entity, as its EntityOfConcern. Its ClaimGraph carries proposed fillings, predicate, polarity or modality, and meaning-bearing semantic basis. It carries no fabricated positive occurrence reference or actual extent.

Unresolved reliance preserves the assertion’s stated polarity and leaves relation obtaining and occurrence identity unchanged. C.2.1 identifies the assertion by its content, EntityOfConcern, and effective reference scheme.

Supported assertions serve as typed premises for another Method. A system performs the receiving check by the selected Method, normally as follows:

  1. resolves the local system-role kinds and any current direct U.SystemRoleAssignment species or A.2.5 state occurrences needed by the rule;
  2. tests the relation predicate without copying assignments or state occurrences into the kind-relation participant set;
  3. individuates the relation only when the receiving use needs its identity;
  4. records the assertion and its separate reliance posture;
  5. evaluates the other conditions required by the receiving use under their direct patterns; and
  6. records the outcome defined for the next question’s decision kind.

Current facts make a world-side relation obtain. Optional individuation recovers one occurrence. An episteme asserts it. Evidence supports reliance. A system performs the check.

A.2.7:4.8 - Recover Apparent Decomposition

When ordinary wording says subrole, role part, or combined role, start from the engineering question:

Engineering questionRecovered object
May this assignment satisfy a condition written for another system-role kind?directional admission-substitution relation
Does every true narrower classification imply the broader classification?C.3.1 U.SubkindOf after independent paired judgments
Does one kind restrict another without monotonicity?residual system-role-kind qualification relation
Must assignments to two kinds not overlap under a condition?symmetric incompatibility relation
Must assignments to several kinds be present together under an allocation rule?order-insensitive bundle relation
Which system is assigned, and for which interval?direct species under U.SystemRoleAssignment; use A.2.1 to recover it
Does an assignment satisfy a Work-admitting state condition?SystemRoleAssignmentStateRelation; use A.2.5 to recover it
Can the holder perform within an operating envelope?the qualified ability claim and separate capability-fit predicate under A.2.2
Are ways of doing or Work occurrences composed?Method composition under A.3 and B.1.5, or Work structure under A.15
Did one actual bounded change occur?one U.Transformation under A.3.4, with its affected entity, boundary, precondition, postcondition, and obtaining relations

This recovery introduces no system-role mereology. Recover kinds, relations, assignments, predicates, Methods, and Work through the direct patterns above.

A.2.7:4.9 - Representation, Model-Use, and Cross-Scheme Boundaries

A graph, table, matrix, algebra, embedding, policy file, taxonomy, or organization chart may describe a SystemRoleKindRelationStructure or support a C.29 mathematical-lens use. It is not the selected structure or any selected relation occurrence by form. State what organization the representation preserves and loses before relying on it.

Reference an independently selected BoundedModelUseStructure only when interpretation depends on that model-use organization. Keep it with the receiving assertion or use unless one direct relation predicate depends on its edition; only then does that edition enter the predicate’s semantic basis.

When a comparison, translation or reuse needs correspondence between different local senses, recover the F.17 sense cells and obtaining F.9 Bridge. A difference of label or reference scheme alone does not establish that need. State a separate C.2.1 bounded-use assertion naming direction, correspondence rule, tolerated loss, polarity, use and effective scheme. Ordinary reliance requires the current A.10 evidence-provenance relation and a passing disposition for that use. Use B.3 only when a named assurance claim is current; require its result for the same bounded assurance use. Establish any required authorization separately.

Apply the direct rule for each claim of bounded-use suitability, an A.2.7 relation, assignment, authorization, receiving-check outcome, or performed Work. A Bridge, profile, or card may provide information for that claim. A local relation that obtains keeps the participant set and identity declared here.

A.2.7:4.10 - Lightweight Path

Ordinary prose may state a readable relation and stop:

For pump pressure-test Work, an assignment to SeniorHydraulicsTechnicianSystemRole
may satisfy the condition written for HydraulicsTechnicianSystemRole.

Add a direct-species RelationSignature when reusable participant typing matters. Individuate an occurrence only when another claim depends on its identity. Assign a stable reference only when another episteme needs it. Build a SystemRoleKindRelationStructure only when several selected relations must be used together and all four A.22 discriminators are recoverable. Completeness is not a reason to materialize every layer.

A.2.7:5 - Worked Slices and Archetypal Grounding

A.2.7:5.1 - Manufacturing Admission Substitution

Plant A admits SeniorHydraulicsTechnicianSystemRole and HydraulicsTechnicianSystemRole as local kinds. During 2026H2, the pressure-test admission Method uses this rule: an assignment to the senior kind may satisfy the condition written for the technician kind only for PumpPressureTestMethodFamily and only while the candidate assignment satisfies A.2.5 predicate PressureTestReady.

The direct species uses the local PlantMaintenanceSystemRoleKindDomain:

PlantPressureTestSystemRoleKindSubstitution :
  U.Relation
RelationSignature:
  CandidateSystemRoleKindSlot:
    PlantMaintenanceSystemRoleKindDomain, ByValue
  RequiredSystemRoleKindSlot:
    PlantMaintenanceSystemRoleKindDomain, ByValue
  AdmissionSubstitutionPredicateSlot:
    PlantPressureTestAdmissionSubstitutionPredicate, ByValue

The predicate names the ordered two kinds, receiving Method family, PressureTestReady rule, 2026H2 applicability, and the semantic basis whose edition changes either clause. PlantMaintenanceRoles-2026 and Plant-A-Maintenance-Scheme may be cited in the assertion; they are not extra relation participants.

When a later edition is used, compare those identity-bearing clauses. If they remain unchanged, use the same predicate. If a clause changes, identify the changed predicate and establish whether it obtains for its participants; a new relation occurrence begins only when it does. If the comparison is unresolved, leave predicate continuity unresolved.

PlantPressureTestSubstitutionAssertion:
  entityOfConcernRef: Plant-A-Pressure-Test-Substitution-2026H2
  ClaimGraph:
    directClaimFamilyRef:
      PlantPressureTestSystemRoleKindSubstitution
    participantDesignations:
      CandidateSystemRoleKindSlot:
        SeniorHydraulicsTechnicianSystemRole
      RequiredSystemRoleKindSlot:
        HydraulicsTechnicianSystemRole
      AdmissionSubstitutionPredicateSlot:
        PlantPressureTestAdmissionSubstitutionPredicate
    assertionPolarity: affirmative
    systemRoleKindRelationExtent: [2026-07-01, 2026-12-31]

The system performing admission checking resolves the candidate’s A.2.1 assignment and its current PressureTestReady state occurrence. Those are inputs to the receiving rule, not substitution-relation participants. Capability is checked separately. For a claim about a performed pressure-test Work, identify the performer through A.13 and admit the occurrence independently through A.15.1; add F.6 when precise assignment attribution is needed.

A.2.7:5.2 - Safety Separation of Duties

For one hazard-analysis Work item, the same system must not hold both author and approver assignments during overlapping windows. The direct species uses the SafetyCaseSystemRoleKindDomain and a predicate identified by the unordered pair {HazardAnalysisAuthorSystemRole, HazardAnalysisApproverSystemRole}, same-holder rule, same-Work rule, overlap test, applicability, and meaning-bearing semantic basis.

HazardAnalysisAuthorApproverIncompatibility :
  U.Relation
RelationSignature:
  IncompatibleSystemRoleKindSlot[1]:
    SafetyCaseSystemRoleKindDomain, ByValue
  IncompatibleSystemRoleKindSlot[2]:
    SafetyCaseSystemRoleKindDomain, ByValue
  IncompatibilityPredicateSlot:
    HazardAnalysisSeparationPredicate, ByValue

The predicate has characterized these kinds continuously since 2026-01-01. A pair of assignments with the same holder and Work item during overlapping windows is a later case satisfying the rule; it does not create the kind relation.

HazardAnalysisAuthorApproverIncompatibilityAssertion:
  entityOfConcernRef:
    HazardAnalysisAuthorApproverIncompatibility-2026
  ClaimGraph:
    directClaimFamilyRef:
      HazardAnalysisAuthorApproverIncompatibility
    participantDesignations:
      IncompatibleSystemRoleKindSlot[1]:
        HazardAnalysisAuthorSystemRole
      IncompatibleSystemRoleKindSlot[2]:
        HazardAnalysisApproverSystemRole
      IncompatibilityPredicateSlot:
        HazardAnalysisSeparationPredicate
    assertionPolarity: affirmative
    systemRoleKindRelationExtent: [2026-01-01, open]

A verifier system applies the work-admission Method to two assignment occurrences and the target Work item. The checking Work produces the receiving decision.

A.2.7:5.3 - Clinical Joint Admission

A surgical MethodDescription states a joint rule: assignments to SurgeonSystemRole, AnesthetistSystemRole, and ScrubPractitionerSystemRole must be held by three distinct systems throughout the procedure window selected by the receiving check.

OperatingTheatreThreeSystemRoleBundle :
  U.Relation
RelationSignature:
  BundledSystemRoleKindSetSlot:
    finite order-insensitive set of OperatingTheatreSystemRoleKindDomain values, ByValue
  JointAdmissionPredicateSlot:
    ThreeDistinctHoldersForProcedurePredicate, ByValue

The set is order-insensitive. The predicate names the three kinds, distinct-holder rule, full-window rule, procedure applicability, and meaning-bearing semantic basis. The taxonomy episteme and clinical reference scheme may help an assertion designate or interpret the kinds; they are not participants of the bundle relation.

OperatingTheatreThreeSystemRoleBundleAssertion:
  entityOfConcernRef: OperatingTheatreThreeSystemRoleBundle-2026
  ClaimGraph:
    directClaimFamilyRef: OperatingTheatreThreeSystemRoleBundle
    participantDesignations:
      BundledSystemRoleKindSetSlot:
        {SurgeonSystemRole,
         AnesthetistSystemRole,
         ScrubPractitionerSystemRole}
      JointAdmissionPredicateSlot:
        ThreeDistinctHoldersForProcedurePredicate
    assertionPolarity: affirmative
    systemRoleKindRelationExtent: [2026-01-01, open]

For one planned procedure, the receiving check separately names its evaluation window and resolves three independently obtaining assignments. The bundle supplies the allocation rule; the three system-role kinds remain distinct even when the holders form one procedure team. Credentials, state, capability, gate decisions, and procedure Work remain separate.

A.2.7:5.4 - Robotics Kind Order and Independent Musician Assignment

The lab proposes:

RoboticsEngineerSystemRole U.SubkindOf EngineerSystemRole

The proposal is not a premise for classifying Vasya or any other system. Under the aligned KindSignature editions and effective reference-scheme edition, direct robotics-engineering features are evaluated against both kinds. Only if every defined true RoboticsEngineerSystemRole judgment implies a true EngineerSystemRole judgment may C.3.1 establish the relation.

A known robotics-engineer true with engineer false refutes the relation. If a dependency required by the broader judgment is unavailable, the result is unknown and the order remains unresolved. A restriction concerning only one Method family, project phase, or allocation condition that fails monotonicity uses a residual qualification relation instead.

Vasya may separately hold assignments to RoboticsEngineerSystemRole and MusicianSystemRole. Those assignment identities and extents remain under A.2.1. Robot-engineering Work, music-performance Work, and teaching-robots-music Work remain A.15 occurrences. Establish capability and admission substitution separately when the receiving use needs them.

A.2.7:6 - Conformance Checklist

CheckQuestion
CC-A2.7-01For a direct question, are the relation kind or C.3.1 U.SubkindOf, participant kinds and predicate recoverable, with an occurrence identified only when obtaining and identity are established? For a dependent SystemRoleKindRelationStructure, are its kind constituents, selected obtaining relation occurrences, applied constraint claims and named selection-use frame recoverable?
CC-A2.7-02Are all individual kind-slot values and all members of the bundle set context-local system-role kinds?
CC-A2.7-03Does each direct context-local species declare SlotSpec ValueKinds and one by-value predicate?
CC-A2.7-04Does the predicate state the receiving, incompatibility, allocation, or residual-restriction rule, applicability, and only meaning-changing semantic basis?
CC-A2.7-05Are system-role-taxonomy and scheme epistemes absent as generic participants and included in predicate identity only when they change meaning?
CC-A2.7-06Is relation obtaining distinct from assertion, evidence, identifier, publication, representation, and receiving-check outcome?
CC-A2.7-07Is substitution directional, incompatibility symmetric, and bundle membership order-insensitive?
CC-A2.7-08Does incompatibility name its species, holder rule, applicability and temporal test, with the actual-Work identity condition or the separately declared prospective-action identity/continuation condition of §4.3? Are actual assignments and the proposed action receiving inputs rather than new kind-relation participants?
CC-A2.7-09Does a bundle state its joint-admission and holder-allocation rule without creating a compound kind?
CC-A2.7-10Is U.SubkindOf used only after independent paired judgments establish monotonicity under the C.3.1 basis?
CC-A2.7-11Does a non-monotonic restriction remain a separately predicated residual relation?
CC-A2.7-12When occurrence identity matters, does it use fixed kind participants, fixed predicate, and maximal continuous truth interval rather than a row, graph key, or temporal SlotSpec; and is any target evaluation window kept in the receiving assertion or check?
CC-A2.7-13When an edition changes, is a claim of predicate or occurrence continuity supported by the comparison in §4.6, with an unresolved comparison left unresolved?
CC-A2.7-14Are current assignments and A.2.5 state occurrences inputs to the receiving check rather than relation participants?
CC-A2.7-15When the account asserts a dated checking Work, are its performer, independently admitted Work, selected Method and outcome recoverable under A.13 and A.15.1, with F.6 only for precise assignment attribution?
CC-A2.7-16Are graphs, tables, matrices, algebras, policies, taxonomies, and publications kept as descriptions, lenses, or epistemes?
CC-A2.7-17Does a negative, candidate, counterfactual, or unsupported claim avoid fabricating a positive occurrence reference or actual extent?
CC-A2.7-18Does cross-scheme use keep the Bridge, bounded-use assertion, reliance, local relation, assignment, authorization, and Work distinct?

A.2.7:7 - Failure Modes and Repairs

FailureWhy it failsRepair
Job-title or taxonomy order used for admissionThe order states neither the receiving rule nor its applicability.Recover a directional admission-substitution predicate for the use.
RoboticsEngineerSystemRole treated as a subkind because of its nameA proposed edge is used as its own membership premise.Evaluate paired classifications independently and apply C.3.1 monotonicity.
Non-monotonic restriction forced into U.SubkindOfA true narrower judgment can coexist with a false broader judgment.A known narrower-true/broader-false case refutes the proposed order. Leave it unresolved only when required information is missing; use a separately predicated residual relation if that non-monotonic restriction remains useful.
Independence asserted without a joint conditionThe checker cannot determine which holders, actual Work or proposed action, and windows make the allocation incompatible.Put the holder rule, the species’ actual-Work or proposed-action identity condition, temporal test, applicability and basis into the incompatibility predicate.
Bundle name treated as one kindHolder allocation and independent assignments disappear.Keep an order-insensitive kind-set relation and allocation predicate.
Taxonomy or scheme made a permanent participantInterpretation support is turned into world-side relation identity even when meaning does not change.Keep only kind participants and predicate; include an edition in semantic basis only when the rule depends on it.
Positive assertion reference used to create an occurrenceA reference and interval appear before predicate truth and individuation.Establish truth, apply the identity rule when needed, then designate the occurrence.
Structure produces a decisionA non-agentive organization is made to act.Name the system that uses the structure and the applicable decision rule. If a dated checking Work is asserted, follow the performer-and-Work route in §1.
Graph treated as the relation structureRepresentation identity replaces selected relation identity.Recover the kind constituents, selected obtaining occurrences, applied constraints, and named selection-use frame; use C.29 for the graph and its preserved and lost structure.
Bridge used as substitution licenceCorrespondence is overread as suitability, assignment, authorization, or outcome.Keep Bridge, bounded use, reliance, local relation, and receiving Work separate.
Evaluation window declared as a participantThe receiver’s target interval is confused with the world-side relation’s derived extent.Remove the temporal SlotSpec; keep systemRoleKindRelationExtent in an affirmative assertion or occurrence description and the target window in the receiving assertion or check.

A.2.7:8 - Consequences

Benefits. Receiving Methods can reuse kind relations without hiding their predicates. Safety checks state separation conditions precisely. Joint Work distinguishes the required kind set from holder allocation. Monotonic order remains a classification law rather than a label convention. Residual restrictions remain useful without weakening U.SubkindOf. Relation assertions can stay readable until a receiving use needs occurrence identity.

Costs. A consequence-bearing use must state the rule that an informal hierarchy or bundle name concealed. Each context-local relation species needs kind domains and predicate identity. Cross-context reuse may need a Bridge and bounded-use reliance. A compatible edition needs an explicit continuity decision before the same predicate is claimed.

Limits. This pattern ends at the relation among system-role kinds and any selected structure over those relations. Use A.2.1 for assignments, A.2.2 and A.2.5 for capability and assignment-state relations, and A.15 for planned or performed Work. The final decision remains an occurrence of its own outcome kind. Storage and visualization remain implementation and lens choices.

Reopen only the affected relation or structure when a participant kind, rule, applicability, meaning-bearing semantic basis, truth interval, selected relation occurrence, or C.3.1 basis changes.

A.2.7:9 - Rationale

When a receiving check needs several kind relations together, a dependent SystemRoleKindRelationStructure identifies that organization. The assignments remain separate inputs to the check.

The families are separate because their laws differ. Substitution is directional. Incompatibility is symmetric under one joint condition. A bundle uses an order-insensitive finite set and an allocation rule. Monotonic qualification belongs to U.SubkindOf; non-monotonic restriction stays residual. One generic hierarchy cannot preserve those distinctions.

Direct predicates determine obtaining, and identity laws determine whether the same world-side relation occurrence continues; assertions, policies, and diagrams describe those facts. Slot discipline makes context-local participant domains reviewable and keeps the system-role kind, holder, assignment, predicate, slot, and representation position distinct.

A.2.7:10 - SoTA-Echoing

Source or practiceWhat it contributesConcrete use in A.2.7
gUFO 2026A foundational-ontology comparator with explicit type and relation reification distinctions.Keep relation obtaining, occurrence individuation, assertion episteme, and representation separate without importing gUFO’s upper taxonomy.
OpenFGA role-modeling guidanceDistinguishes static role-like relations, user-defined role forms, and instance-specific assignments in authorization models.Use it as a software stress case for separating kind relations, assignment inputs, and outcomes; do not make authorization the universal ontology.
Cedar policy constructionEvaluates concrete principal, action, resource, scope, and additional conditions.Keep structure as one premise while the checking system, assignments, action condition, and outcome remain visible.
Separation-of-duties practice across safety, clinical work, governance, and authorizationUseful independence claims depend on the holder rule, actual-Work or proposed-action identity condition, temporal test and applicability rather than title intuition.Put those conditions in the symmetric incompatibility predicate and test actual assignments separately.
FPF C.3.1, A.6.REL, A.6.5, and A.22Supply monotonic kind order, relation occurrence identity, declaration-local SlotSpecs, and dependent structure identity.Reuse the existing apparatus instead of creating another role taxonomy or relation-record ontology.

The software sources are stress cases, not the universal subject. Their transferable contribution is the separation of kind definitions, instance assignments, evaluation inputs, and outcomes.

A.2.7:11 - Relations

PatternRelation
A.1Keeps systems distinct from kinds, assignments, relation occurrences, and selected structures; only admitted systems act.
A.1.1Use for a selected BoundedModelUseStructure when interpretation depends on it.
A.2 and C.3Use for context-local system-role kinds, their descriptions, membership, and classification.
C.3.1Use for monotonic U.SubkindOf, its three-valued judgment discipline, effective-reference-scheme edition, obtaining, and identity.
A.2.1Use for direct U.SystemRoleAssignment species and occurrences supplied to receiving checks.
A.2.2 and A.2.5Use for capability and assignment-state predicates and relations that remain separate from kind relations.
A.3.1, B.1.5, and A.15Use for Method and Work identity, composition, planning, participation, and performance.
A.3.4Use when current facts require one actual bounded change as a separate U.Transformation; it supplies neither a transformation-composition predicate nor holonhood.
A.6.0, A.6.5, and A.6.RELUse for signatures, declaration-local SlotSpecs, relation obtaining, and progressive occurrence individuation.
A.22Use to recover SystemRoleKindRelationStructure as a dependent non-agentive U.Structure over kinds and relations.
A.6.9, F.9, C.2.1, A.10, and B.3Use for cross-scheme Bridges, bounded-use assertions, evidence reliance, and assurance without preserving local relation identity by form.
A.2.4, C.27, and G.11Use for evidence-use relations, currentness, and support for assertions consumed by a receiving check.
C.29Use for graph, table, matrix, algebra, and embedding representations and their preserved or lost structure.
E.24.UKUse to avoid admitting a selected structure, local relation slot, or convenient bundle name as a root U-kind by punctuation.
E.10.ROLE, F.5, and F.18Use for recovery of ambiguous source wording and durable naming after the object is known.

A.2.7:End

A.2.8 - U.Commitment — Individual Duties to Act or Refrain

Status: Stable Type: Definitional ontic pattern

A.2.8:0 - Use This When

Use this pattern to decide whether an actual system or party has a duty to perform or avoid a specified action within a stated scope and time. The modality distinguishes obligation, recommendation-as-duty, and prohibition.

Start with the ordinary question: does this actual bearer have this duty now? Name the bearer and the duty content. Then find the policy or prescription, the rule by which it creates an individual duty, and the actual event or other basis that the rule requires. The first useful result is one obtaining U.Commitment, a demonstrated non-obtaining result, unknown reliance when required evidence is unavailable, or missing-governor[individual commitment institution].

What goes wrong if missed. A policy sentence, system-role kind, assignment, publication, ticket, interface description, or complete-looking record is treated as the duty itself. A named office is called responsible without a responsibility predicate. Evidence is made constitutive merely because the duty is auditable.

What this buys. The actual duty bearer, content, modality, scope, validity, constitutive rule, and instituting basis remain inspectable. Generic prescriptions stay usable as generic claims, while evidence and records can support claims about actual commitments.

Not this pattern when. Use A.2.3 for promise content, A.2.9 for the communicative Work that may institute a duty, and A.2.8.PER for permission or authorization. For responsibility, use an admitted domain responsibility predicate; if none exists, return its A.6.RCD missing governor. Use a gate pattern for admissibility and A.15.1 for performed Work. If no current subject pattern defines how the proposed individual duty is instituted, return missing-governor[individual commitment institution] instead of completing a record by convention.

A.2.8:0.1 - Individual Duty and Source Wording

U.Commitment is an enduring individual deontic relation. It covers obligation, recommendation-as-duty, and prohibition.

The words bind and binding already denote technical bindings in FPF; they do not name this relation. Source phrases such as binding promise, must, shall, guarantees, is responsible for, or legally required are recognition cues. Recover their claim before selecting U.Commitment.

A.2.8:1 - Problem Frame

FPF needs both generic normative content and actual individual duties:

  • a policy can say what would apply to systems of a stated kind;
  • one constitutive rule can say when that content creates an individual duty;
  • actual world-side facts can satisfy or fail that rule;
  • one assertion or record can describe the resulting relation for reliance or audit.

Those are different objects. If a generic policy and an individual relation share one record-shaped ontology, an assignment row or published clause can appear to create a duty by being filled in. If the actual bearer is replaced by a system-role kind or assignment, the model cannot say who is obliged. If responsibility is inferred from the duty, another independent relation disappears.

A.2.8:2 - Problem

How can a practitioner state an individual deontic relation so that:

  1. the actual duty bearer is explicit;
  2. the duty referents, modality, scope, and validity are specified;
  3. one applicable constitutive rule and its required actual basis make institution testable;
  4. a generic prescription remains generic until the rule is satisfied;
  5. relation identity survives compatible description changes but not a changed bearer, content, rule, or interrupted validity;
  6. records and evidence support the claim without constituting the relation by form; and
  7. responsibility, permission, authority, assignment, Work, and compliance remain separately governed?

A.2.8:3 - Forces

ForceTension
Direct bearer vs generic policyPolicy often speaks about a system-role kind, while an individual commitment needs an actual system or party.
Minimal use vs truthful institutionRoutine prose should stay short, but a positive world-side relation cannot omit the rule and actual instituting basis that make it obtain.
Stable identity vs changing recordsA correction or compatible policy edition need not create another duty. A changed bearer, content, constitutive rule, or interrupted validity prevents reuse of the same occurrence; assert a successor only after it obtains under §4.2.
Auditability vs constitutionEvidence is needed for reliance, but evidence and publication do not create the duty by form. Institution requires the identified constitutive rule and its independently tested required facts.
Local meaning vs cross-context reuseModality and policy interpretation are local; a similar label or Bridge does not transfer an individual relation.
Duty vs neighboring governanceCommitment, responsibility, permission, authority, assignment, Work, gate result, and compliance can co-occur without becoming one object.

A.2.8:4 - Solution

A.2.8:4.1 - Direct Participants and Predicate Parameters

One U.Commitment occurrence has:

  • exactly one actual duty bearer, expressed by either dutyBearerSystemRef : U.EntityRef constrained to an admitted U.System or a separately governed local dutyBearerPartyRef : PartyRef;
  • a non-empty exact set of duty referents stating the action, avoidance, outcome, promise content, claim, or other governed object to which the duty applies; and
  • optional actual counterparties or beneficiaries when the duty is owed to someone.

Exactly one duty-bearer branch is filled. A system-role kind, classification judgment, assignment occurrence, organizational-position label, publication, policy, or claim record is not the bearer.

The normalized modality is a by-value predicate parameter:

DeonticModalityToken ::= MUST | MUST_NOT | SHOULD | SHOULD_NOT

SHALL and REQUIRED map to MUST; SHALL NOT and PROHIBITED map to MUST_NOT; RECOMMENDED maps to SHOULD; and NOT RECOMMENDED maps to SHOULD_NOT only after the source claim has been recovered as a duty. MAY and OPTIONAL do not normalize into U.Commitment; route their current meaning to A.2.8.PER, an admissibility predicate, or ordinary prose.

Scope and validity delimit applicability. Duty referents are cited by exact identifiers when they already exist. Useful duty referents include a claim, an instance of U.PromiseContent, an action or outcome specification, an admitted Method, or an already identified Work occurrence when the duty concerns that occurrence. A MethodDescription is cited only when the duty depends on claims in that exact episteme edition; description is not mandatory indirection to the Method.

The current normative policy or prescription, its constitutive rule, the actual instituting basis, provenance, and adjudication evidence are grounds or qualifiers. They are not extra duty bearers and do not become deontic participants by appearing in a record.

A.2.8:4.2 - When the Relation Obtains

For proposed occurrence C, the direct predicate C : U.Commitment obtains only when all of the following hold:

  1. the actual duty bearer and any actual counterparties are admitted, and the duty referents are identified;
  2. one identified normative policy or prescription is current and applies to those participants, referents, scope, and time;
  3. that policy contains or cites one exact constitutive rule for an individual commitment rather than only generic content about a system-role kind;
  4. the rule’s required instituting basis and world-side facts obtain;
  5. modality, scope, validity window, and every rule-required condition are satisfied; and
  6. no valid revocation, defeat, expiry, or supersession has ended the relation.

For the current A.2.9 path, the instituting basis is an actual U.SpeechAct Work occurrence recognized by the current policy, with the actual performer and exact covering system-role assignment independently established. Another basis is usable only when a subject pattern admits it and gives its occurrence rule.

If the corpus lacks the constitutive rule or the required instituting-relation predicate, return missing-governor[individual commitment institution]. If available facts establish that a required obtaining condition is false, the proposed commitment does not obtain. If a required evidence dependency is unavailable, reliance on the assertion is unknown; do not invent the relation or infer its negation.

A.2.8:4.3 - Occurrence Identity and Continuity

One occurrence is identified by:

  • the actual duty bearer;
  • exact duty referents and counterparties;
  • normalized modality and scope;
  • constitutive policy and rule;
  • the actual instituting basis, only when that rule makes the basis identity-bearing; and
  • one maximal continuous validity interval.

The actual instituting basis is always required for obtaining. It is part of occurrence identity only when the exact constitutive rule says that reinstitution identifies another duty.

A compatible policy edition, new record, or later instituting act preserves the occurrence only through an explicit continuity decision showing that every identity-bearing fact and the rule’s deontic effect continue. A changed bearer, modality, referent set, constitutive rule, identity-bearing basis, or interrupted validity prevents reuse of the same occurrence identity. Establish the new commitment under §4.2 before asserting another occurrence. The commitment ID and its describing claim do not decide sameness.

When a rule makes a duty end with a system-role assignment, an assignment boundary ends that commitment. When the rule makes the duty persist for the same actual system across a replacement assignment, state that continuity explicitly. A duty for a different actual bearer, if it obtains under §4.2, has another occurrence identity.

A.2.8:4.4 - Generic Prescriptions and Assignment-Mediated Rules

A generic prescription states what one exact policy or other normative episteme requires; it does not create an individual duty bearer or commitment occurrence. A claim that one actual System or separately governed party has that duty instead cites one separately obtaining A.2.8 U.Commitment.

For example, a policy can concern ProviderSystemRole or another exact local system-role kind. Its systemRoleKindRef : U.KindRef can appear in the rule’s antecedent, but the policy episteme is not an individual U.Commitment.

An exact systemRoleAssignmentRef : U.RelationRef constrained to U.SystemRoleAssignment can show that an actual system satisfies one applicability condition for a time. The assignment is not the duty bearer or the commitment relation. The only valid direction is:

current policy or prescription
+ exact constitutive rule
+ actual admitted system
+ obtaining exact system-role assignment or other rule-required facts
+ actual instituting basis required by that rule
-> one separately identified U.Commitment whose duty bearer is that actual system

Classification or assignment alone never completes the implication. The rule states whether the duty starts, continues, and ends with the assignment.

A.2.8:4.5 - Assertion, Record, and Adjudication

An assertion or record about a commitment is a separately identified claim-bearing episteme. For an independently identified actual U.Commitment occurrence, a compact occurrence-description record can expose:

CommitmentAssertion:
  entityOfConcernRef: U.RelationRef constrained to one exact U.Commitment occurrence
  dutyBearerSystemRef? | dutyBearerPartyRef?: the actual bearer stated by the relation
  dutyReferentRefs: non-empty exact set
  counterpartyRefs?: actual counterparties or beneficiaries
  modality: normalized by-value token
  scopeRef:
  validityWindowRef:
  constitutivePolicyRef: exact current normative episteme edition
  constitutiveRuleRef: exact rule claim
  institutingBasisRef: exact actual basis required by that rule
  evidenceClaimRefs?: exact support used for reliance or adjudication
  carrierRefs?: carriers used as evidence or source
  assertionPolarity: affirmative | negative
  relianceResultRef?: exact separately governed evaluation or evidence-use result, when the receiving use needs it

Before a commitment occurrence has been independently identified, express whether the commitment obtains as an ordinary C.2.1 assertion with an independently identified EntityOfConcern. Designate the relation kind and its participants in the claim content, and retain the failed or unknown obtaining condition. Do not invent a commitment occurrence or actual instituting-basis reference. Keep assertion polarity separate from the reliance judgement; unavailable evidence alone establishes no negation.

Use the record to describe the relation. evidenceClaimRefs and carriers support reliance; they are not participants or instituting facts unless the identified constitutive rule requires the particular item in that role and the pattern for that subject supplies its test. If adjudication is intended, cite the exact evidence claims, criteria, and carriers. If no adjudication is claimed, do not invent an audit apparatus.

When a later use must compare incompatible commitments, keep the commitments unchanged and carry the needed conflict inputs in one local claim:

CommitmentConflictInputClaim:
  selectionUseRef: exact conflict or choice question
  commitmentRows: non-empty set of
    commitmentRef: U.RelationRef constrained to one exact U.Commitment occurrence
    institutingBasisRef: exact actual basis required by its constitutive rule
    issuingSystemRef | issuingPartyRef: exactly one actual issuer recoverable from that basis
    authorityRelationRef?: U.RelationRef constrained by the direct authority predicate used by selectionUseRef
  selectingRuleRef?: exact priority or choice rule required by selectionUseRef
  unresolvedInputRefs?: exact missing-information or missing-governor results

These conflict inputs stay outside commitment identity by default. Each authority relation must already obtain under its own predicate, and each selecting rule must be current and applicable to this selection use under the pattern that defines it. If this selection use requires an authority relation or selecting rule and that input is unavailable or no current pattern defines it, put its exact unresolved result in unresolvedInputRefs, such as missing-governor[commitment conflict authority relation] or missing-governor[commitment conflict selecting rule]. An optional field means that the input is not required for this use; it never licenses dropping a required input.

For an interlevel ethical conflict, use D.3 to map the conflict and D.4 for mediation or decision use. When an explicit choice among already available options is current, C.11 supplies the ChoiceRule and ChoiceResult. Otherwise apply the direct pattern for the claimed conflict result; if none exists, return missing-governor[commitment conflict resolution].

Evidence used only to measure or verify the duty belongs to the support for the assertion. An evidence-producing or evidence-retaining duty instead names that production or retention content among its duty referents.

A.2.8:4.6 - Direct Neighboring Relations

Current questionDirect resultUnsupported inference
What does a generic policy prescribe?one normative claim episteme and its applicable rule contentan individual duty from generic content alone
Which System holds a local system-role assignment?one A.2.1 assignment occurrence and its declared speciesa duty or responsibility
Did a communicative act occur?one A.2.9 U.SpeechAct Work occurrenceits institutional effect without the constitutive rule
Is the bearer responsible?one admitted domain responsibility predicate and occurrence; otherwise the missing governorresponsibility from duty, assignment, position, or “owner” wording
Is an action permitted or authorized?the exact A.2.8.PER grant, exercise, non-prohibition, non-violation, or conflict resultpermission from commitment or assignment
Did access occur?an exact domain access relation; otherwise missing-governoraccess from permission, duty, or assignment
Did the bearer perform Work?recover the actual performer through A.13 and let A.15.1 independently admit one dated U.Work; add F.6 only when this duty account or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignmentWork or attribution from the duty alone
Was the duty satisfied or violated?a separately governed evaluation or compliance result using actual Work and evidencecompliance from publication or record completeness
What resulted?the separately identified result and its direct result relation, or A.15.PROD for production and inceptiona generic result relation from duty or Work

The common corpus has no universal responsibility predicate. VP.AllocationResponsibility can help a reader recognize the concern; the applicable domain responsibility predicate determines whether the relation obtains.

A.2.8:4.7 - Boundary Claim Use

An A.6.B D-quadrant claim about an obtaining individual obligation, recommendation-as-duty, or prohibition cites the exact U.Commitment occurrence. A D-claim about generic policy content remains a claim about that content until the individual predicate above is satisfied.

Strong or weak permission, exercise, non-violation, and permission-conflict claims cite their exact A.2.8.PER result and do not acquire a U.Commitment payload. Gates remain A-claims, laws and definitions remain L-claims, and Work and evidence effects remain E-claims.

A.2.8:5 - Archetypal Grounding

A.2.8:5.1 - Incident Response

Current IncidentResponsePolicy-2026 says that systems assigned to ProviderSystemRole are subject to a four-hour incident-response prescription. That policy and its kind reference remain generic content.

OpsTeamProviderAssignment-2026 is an assignment occurrence with admitted System OpsTeam as holder; its species is declared under U.SystemRoleAssignment. If the policy contains the holder-application rule, speech act SA-Issue-IncidentDuty-2026 : U.SpeechAct is the policy-recognized instituting Work, and the predicate is satisfied, then IncidentResponseCommitment-2026 : U.Commitment obtains with OpsTeam as duty bearer. Its modality is MUST; its referents include SVC-SLO-RESP-4H and the Sev-1 applicability claim; its scope is IncidentManagement; and its validity window is the interval established by the rule.

The commitment assertion may cite E-SLO-RESP-1, incident tickets, timestamps, and the selected clock source for adjudication. Those values make reliance testable; SA-Issue-IncidentDuty-2026 remains the policy-recognized instituting Work.

If OpsTeamProviderAssignment-2026 ends and RecoveryTeamProviderAssignment-2026 begins, apply the constitutive rule’s continuity conditions. When the rule ties duty continuity to the assignment, the OpsTeam commitment ends and a RecoveryTeam commitment begins only after its own required basis and facts obtain. If the rule instead preserves the duty for the same system across a replacement assignment, the continuity decision says so. Any duty that obtains under §4.2 for a different bearer has another occurrence identity.

Likewise, a second policy-recognized act reissuing the same uninterrupted duty identifies another commitment only when the constitutive rule makes that instituting basis identity-bearing; otherwise the new act is a new ground or record for the continuing occurrence.

A policy-recognized speech act can also institute ShutdownNoticeCommitment-7 directly for admitted system PlantController-7.

IncidentResponseCommitment-2026 can obtain while no incident-ownership responsibility relation exists. Conversely, an admitted MaintenanceActionResponsibilityRelation@Plant can obtain while no U.Commitment obtains. Both can obtain for the same system and interval only as separately identified relations with separate predicates, participants, bases, and occurrence identities.

If the corpus lacks the constitutive rule or the required instituting-relation predicate, return missing-governor[individual commitment institution]. If the available facts establish that the rule’s required instituting act did not occur, IncidentResponseCommitment-2026 does not obtain under §4.2. If deciding evidence is unavailable, reliance on the commitment assertion is unknown.

A.2.8:5.2 - Protocol Rule

A protocol description says: “Participants MUST follow the state machine; invalid traces are rejected; traces are retained for audit.” Recover separate claims:

  • L-claims define the state machine and its safety or progress properties;
  • A-claims define which runtime traces are admissible;
  • one generic normative claim states the participant prescription;
  • one actual U.Commitment is asserted only for an admitted bearer after an applicable constitutive rule and its required basis obtain;
  • the duty referents cite the state-machine, admissibility, and trace-retention content by exact identifiers; and
  • evidence claims and trace carriers support later adjudication.

A ParticipantImplementerSystemRole reference in the policy names a kind. Identify the actual bearer and apply the constitutive rule with its required basis before asserting the individual commitment.

A.2.8:6 - Invariants and Reasoning Primitives

  1. Every positive U.Commitment has one actual system or party as duty bearer.
  2. A system-role kind or assignment can be a rule ground but never the duty bearer.
  3. Generic normative content, individual relation, and describing assertion remain separate.
  4. The direct predicate includes an applicable constitutive rule and the actual basis that rule requires.
  5. Modality, scope, validity, and referents are explicit.
  6. Missing evidence makes reliance unresolved; it does not invent or negate the relation.
  7. Assignment turnover does not transfer a duty automatically.
  8. Responsibility, permission, authority, access, Work, result, and compliance remain separately governed.
  9. Compatible record correction does not decide world-side continuity.
  10. A Bridge or similar wording in another context creates no local commitment.
applicable current policy and exact constitutive rule
  and admitted actual bearer and referents
  and required instituting basis and facts obtain
  and modality, scope, validity, and continuation conditions hold
  and no defeat, revocation, expiry, or supersession applies
  -> one U.Commitment occurrence obtains.
policy mentions one system-role kind
  or one system-role assignment obtains
  -> no individual U.Commitment follows without the exact rule, bearer, and basis.

A.2.8:7 - Bias Annotation

Bias riskFailureRepair
Record-first biasA filled form is treated as an obtaining relation.Test the direct predicate; keep the record as an assertion.
Office-label biasA role, office, or assignment becomes the bearer.Recover the actual system or party and use the kind or assignment only as a rule ground.
Legal-form biasA maximal legal-policy schema is imposed on every duty.Keep the direct participants minimal and establish the rule-required instituting basis. Add further legal-policy detail or assurance only when the receiving claim needs it.
Evidence-as-constitutionAn audit trail is treated as what creates the duty.Keep support and institution separate.
Responsibility overreachDuty is read as ownership or accountability.Apply the direct responsibility predicate or return its missing governor.
Keyword biasMUST, SHALL, MAY, or responsible selects an ontology by spelling.Recover the claim first, then select the relation or ordinary non-use.

A.2.8:8 - Conformance Checklist

IDRequirement
CC-A2.8-1Exactly one actual admitted system or separately governed party is the duty bearer.
CC-A2.8-2Duty referents are non-empty and exact; existing claim or object identifiers are cited rather than paraphrased.
CC-A2.8-3Modality, scope, and validity are explicit.
CC-A2.8-4One current policy or prescription and its exact individualizing constitutive rule are identified.
CC-A2.8-5The actual instituting basis required by that rule obtains under the pattern that defines that basis.
CC-A2.8-6The occurrence identity and continuity decision distinguish changed bearers, content, rules, and interrupted intervals, and treat a changed instituting basis as identity-bearing exactly when the constitutive rule says so.
CC-A2.8-7System-role kind, classification, assignment, policy, publication, assertion, and evidence are not commitment participants or duty bearers by form.
CC-A2.8-8When the receiving use needs responsibility, permission, authority, access, Work, result or compliance, its claim is separately governed; the commitment alone supplies none of those results.
CC-A2.8-9An occurrence-description reliance or audit record names its exact U.Commitment EntityOfConcern and does not claim to create it.
CC-A2.8-10A missing constitutive rule or instituting-relation governor returns missing-governor[individual commitment institution]. Unavailable required evidence leaves reliance unknown; demonstrated failure of an obtaining condition yields non-obtaining. Do not complete a placeholder relation.

A.2.8:9 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
“The API shall…” as duty-bearer structureThe API label leaves unclear whether the sentence states generic policy or an individual duty, and what entity it concerns.Recover the referent. For an individual duty, identify the actual System or party and test institution under §4.2.
`CommitmentSubject ::= RoleRefRoleAssignmentRefPartyRef`
Optional institution sourceA published sentence appears sufficient to create the relation.Require the applicable rule and its actual instituting basis.
Assignment-as-dutyStaffing becomes obligation.Treat the assignment only as a rule fact and identify a separate commitment.
Duty-as-responsibilityOne deontic relation is treated as ownership.State the independent responsibility predicate or return missing-governor.
Gate-as-dutyEntry conditions become obligations.Keep the A-claim and let an independently instituted commitment cite it when required.
Auditable rhetoric without support“Guaranteed” cannot be adjudicated.Cite exact evidence claims and carriers only when reliance or adjudication is current.
Silent mutationChanged bearer or rule is hidden under one ID.A changed identity-bearing fact prevents reuse of the same occurrence identity. Establish the new commitment under §4.2 before asserting another occurrence.

A.2.8:10 - Consequences

Benefits

  • Generic policy content and actual duty no longer collapse.
  • Actual bearers are directly recoverable.
  • The reader can identify the modality, scope, referents and validity.
  • Assignment and responsibility independence is explicit.
  • Assurance is added for a named claim that needs it.

Costs and mitigations

  • An individual-duty assertion must establish the applicable rule and actual instituting basis. A generic policy statement can remain sufficient when no individual duty is being asserted.
  • Domains with another instituting basis need the pattern that defines that basis. Until then, return the missing-governor result.
  • Conflict resolution remains outside this pattern. Preserve each current commitment plus the exact source, independently obtaining authority relation, and selecting rule required by the named conflict or choice use; apply D.3/D.4 for an interlevel ethical conflict, C.11 for an explicit choice among available options, or return missing-governor[commitment conflict resolution] when no direct result rule exists.

A.2.8:11 - Rationale

Requiring an actual bearer, constitutive rule, and actual basis prevents description, assignment, and publication from becoming causes by form. Keeping assertion and evidence separate preserves both ontology and auditability. Keeping responsibility separate avoids replacing one ambiguous word with an equally ambiguous omnibus governance object.

A.2.8:12 - SoTA-Echoing

Informative. These comparisons motivate the distinctions; they do not govern local claims.

  • BCP 14 (RFC 2119 and RFC 8174). Controlled normative keywords support explicit modality, but keywords do not identify an individual bearer or institute a duty.
  • W3C ODRL 2.2. Duties, permissions, assignees, actions, constraints, and policy provenance motivate explicit participants and qualifiers. FPF keeps individual commitment, permission, policy episteme, and evidence separate.
  • Institutional and constitutive-rule approaches. Their distinction between rule content, institutional conditions, and resulting relations supports the required constitutive rule and actual basis.
  • Policy-as-code practice. Admission predicates and policy evaluation should not be confused with individual obligation or performed Work.
  • Trace-based compliance and supply-chain attestations. Evidence and carriers can support adjudication while remaining distinct from relation obtaining.

A.2.8:13 - Relations

  • Builds on: A.2 and C.3 for system-role kinds and classification; A.2.1 for declared system-role-assignment species and their obtaining occurrences; A.2.6 for scope and temporal qualification; A.2.9 for communicative Work; A.6.RCD for missing governors; A.7 for episteme and world separation.
  • Coordinates with: A.2.3 for promise content; A.2.8.PER for permission; F.6 and A.15.1 for Work attribution; A.6.B and A.6.C for claim classification and boundary wording; A.10 for evidence and source reliance.
  • Does not define: a universal responsibility, authority, access, compliance, or result relation; a system-role kind; a system-role assignment; a policy language; or a legal-party model.

A.2.8:End

A.2.8.PER - Granted Permission, Exercise, and Non-Prohibition

Type: Definitional ontic support pattern Status: Stable Normativity: Normative unless marked informative

A.2.8.PER:0 - Use this when

Use this pattern when a policy, approval, permit, system-role rule, boundary claim, readiness check, or later work use needs to distinguish five questions:

  • whether a sufficiently complete current frame supports a NonProhibitionFinding@Context;
  • whether a valid grant currently obtains as GrantedPermissionRelation@Context;
  • whether dated matching work exercises it through PermissionExerciseRelation@Context;
  • whether checked actual work supports a NonViolationFinding@Context; and
  • whether an incompatible current grant and norm require PermissionNormConflictFinding@Context.

First select the result needed now. Recover the inputs required by its declaration in §§4.2–4.6 and establish that result under its own rule. Do not infer a different result from the selected one.

Not this pattern when. Use A.2.8 for one actual bearer’s obligation, recommendation-as-duty, or prohibition; A.2.9 for the communicative work that institutes or revokes a grant; A.6.B for L/A/D/E classification; A.15.5 for work-entry readiness; A.21 for gate decisions; and A.15.1 for the identity and result of performed work.

When the account asserts a particular dated Work occurrence, identify its performer through A.13 and admit the Work independently through A.15.1. Use F.6 where the relevant declaration consumes precise attribution to a covering assignment; the grantor, beneficiary and decision branches below state those conditions.

A.2.8.PER:1 - Problem frame

Permission-looking language often compresses unlike values. “No rule forbids it” may be an incomplete search result. “The permit allows it” may refer to a document, an issuing act, or an enduring relation. “We used the permit” may mean only that a badge was visible, while no matching work occurred. A green gate can also look as if it defeated a current prohibition.

The concern is the smallest permission result needed for one beneficiary, action specification, normative-frame edition, ClaimScope, intended use, and window. The act, permit episteme, publication carrier, evidence relation, admissibility predicate, readiness relation, gate decision, actual Work, and work result remain distinct and are handled under their respective subject patterns.

A.2.8.PER:2 - Problem

How can FPF represent positive permission without turning it into an obligation modality, absence-of-evidence claim, permit document, gate result, readiness label, capability, or performed action?

A conforming account must make weak and strong permission different, keep grant occurrence identity inspectable, connect only eligible matching work to a current grant, keep both exercise and non-exercise from establishing a frame-relative non-violation finding, and expose same-scope normative conflicts instead of resolving them by display or wording.

A.2.8.PER:3 - Forces

ForceTension
Latitude vs dutyPermission makes an action allowable; it does not require the action.
Weak evidence vs world relationA complete-frame search can support non-prohibition, while an incomplete search is unresolved.
Enduring grant vs instituting actA speech act can ground a permission without being the continuing relation.
Beneficiary variety vs kind disciplineSystem-role kinds, exact assignment occurrences, and parties all occur in practice, but one generic beneficiary U-kind would erase their different eligibility tests.
Current grant vs actual exerciseA grant may obtain without work; work may occur without matching or exercising the grant.
Local policy vs visible artifactsA permit or gate display is easy to see, but scope, window, currentness, revocation, and precedence decide use.

A.2.8.PER:4 - Solution

A.2.8.PER:4.1 - Keep the permission objects separate

Use the object warranted by the current claim:

  • NonProhibitionFinding@Context is a frame-relative episteme returned before action when a sufficiently complete current normative frame contains no applicable prohibition.
  • GrantedPermissionRelation@Context is an enduring strong permission instituted under an exact policy.
  • PermissionExerciseRelation@Context connects actual dated work to one obtaining grant occurrence when action and beneficiary eligibility match.
  • NonViolationFinding@Context is a frame-relative episteme about actual work that instantiates no applicable prohibition in the checked frame.
  • PermissionNormConflictFinding@Context is an episteme exposing an incompatible current grant and prohibition or commitment over matching content, scope, and window.

Absence of any one object does not imply another. In particular, no grant is inferred from a weak finding, no exercise is inferred from a grant, and work outside a grant is not called a violation of that grant.

A.2.8.PER:4.2 - Use the closed beneficiary reference family

PermissionBeneficiaryRef ::=
  exactly one branch is present:
    beneficiarySystemRoleKindRef?: U.KindRef resolving to one exact local system-role kind
    beneficiarySystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment
    beneficiaryPartyRef?: PartyRef

The entity designated by the grant is its beneficiary. Apply the exercise-eligibility test for its reference branch:

  • beneficiarySystemRoleAssignmentRef names one assignment occurrence and its declared species and applies only to that occurrence.
  • beneficiarySystemRoleKindRef names one exact local system-role kind; the policy states which current assignments to that kind make an actual performer eligible.
  • PartyRef covers work only when its exact performer or on-behalf-of relation satisfies the policy. Shared naming or organizational membership is insufficient.

This is a closed ref union over admitted U.Entity values, not a new U-kind. A materially different beneficiary meaning requires a separate decision under the applicable subject pattern.

A.2.8.PER:4.3 - Record weak permission and non-violation as findings

NonProhibitionFinding@Context <: U.Episteme
  beneficiaryRef: PermissionBeneficiaryRef
  permittedActionSpecificationRef: U.EpistemeRef
  normativeFrameRef: U.EpistemeRef
  frameCurrentnessResultRef: U.EpistemeRef
  frameCompletenessForUseResultRef: U.EpistemeRef
  scope: U.ClaimScope
  intendedUse:
  evaluationWindow: QualificationWindowPolicy
  checkedProhibitionAddresses: set<ClaimAddress>
  result: nonProhibited | unresolved
  evaluationWorkRef?: WorkRef             # when the account asserts this dated evaluation Work

NonViolationFinding@Context <: U.Episteme
  workRef: WorkRef
  performerSystemRoleAssignmentRefs?: set<U.RelationRef constrained to U.SystemRoleAssignment> # when the checked norm uses precise assignment attribution
  onBehalfOfRelationOccurrenceRef?: U.RelationRef constrained to the direct on-behalf-of relation kind
  normativeFrameRef: U.EpistemeRef
  frameCurrentnessResultRef: U.EpistemeRef
  frameCompletenessForUseResultRef: U.EpistemeRef
  scope: U.ClaimScope
  intendedUse:
  evaluationWindow: QualificationWindowPolicy
  checkedProhibitionAddresses: set<ClaimAddress>
  result: nonViolating | unresolved
  evaluationWorkRef?: WorkRef             # when the account asserts this dated evaluation Work

nonProhibited and nonViolating are admissible only when the named frame is current and explicitly sufficiently complete for the intended use. Otherwise the finding is unresolved. Neither finding institutes permission or proves absence outside its frame.

Every ClaimAddress in this pattern means the reusable C.2.1 ClaimAddress: an exact episteme-edition reference plus an intrinsic claim identity declared by that edition’s ClaimGraph. A heading, row number, file location, or printed token is insufficient.

For NonViolationFinding@Context, recover the performer Systems from the independently admitted Work. Cite each covering assignment occurrence and its declared species when the checked norm uses that assignment attribution. If the norm instead turns on Work done for a PartyRef, cite the obtaining on-behalf-of relation defined in its pattern. These are case facts consumed by the evaluation. Omit unused assignment or on-behalf-of references. A finding need not identify a separate dated evaluation Work unless the account asserts that occurrence; its frame, completeness, currentness and checked-prohibition requirements apply.

A.2.8.PER:4.4 - Declare the strong granted-permission relation

GrantedPermissionRelation@Context <: U.Relation

RelationSignature:
  PermissionBeneficiarySlot:
    SlotKind: PermissionBeneficiarySlot
    ValueKind: U.Entity
    refMode: PermissionBeneficiaryRef
  PermittedActionSpecificationSlot:
    SlotKind: PermittedActionSpecificationSlot
    ValueKind: U.Episteme
    refMode: U.EpistemeRef

semanticDirection: PermissionBeneficiarySlot -> PermittedActionSpecificationSlot

RelationOccurrenceGroundAndQualifiers:
  institutingSpeechActRef: SpeechActRef
  grantorSystemRoleAssignmentRef: U.RelationRef constrained to U.SystemRoleAssignment
  grantValidityPolicyRef: U.EpistemeRef
  scope: U.ClaimScope
  validityWindow: QualificationWindowPolicy
  revocationOrSupersessionRef?: SpeechActRef

The beneficiary and permitted-action specification are participants. The grantor system-role assignment, instituting act, policy, ClaimScope, validity window, and revocation are constructive grounds or qualifiers.

The relation begins only when an admitted holder U.System performs a U.SpeechAct under the exact grantorSystemRoleAssignmentRef, the act satisfies the current policy’s grant-validity predicate, and it institutes permission for the named participants. The assignment’s HolderSystemSlot resolves to that system: the system performs the act, while the assignment supplies only the holder and assigned-kind fact used by the policy. Any authority claim required by the policy obtains independently.

The relation obtains while beneficiary applicability, policy continuation, scope, and window hold and no valid revocation or supersession ends it.

One occurrence is identified by the instituting speech-act occurrence, exact beneficiary ref and ref kind, action-specification edition, policy edition, ClaimScope, and effective interval. Beneficiary change, renewal, materially changed action specification, non-carried policy edition, or revocation ends or splits the occurrence. A policy edition preserves it only through an explicit satisfied carry-forward rule.

A.2.8.PER:4.5 - Declare actual exercise

PermissionExerciseRelation@Context <: U.Relation

RelationSignature:
  ExercisingWorkSlot:
    SlotKind: ExercisingWorkSlot
    ValueKind: U.Work
    refMode: WorkRef
  GrantedPermissionOccurrenceSlot:
    SlotKind: GrantedPermissionOccurrenceSlot
    ValueKind: U.Relation
    refMode: U.RelationRef constrained to GrantedPermissionRelation@Context
      // resolves to one exact obtaining grant occurrence

semanticDirection: ExercisingWorkSlot -> GrantedPermissionOccurrenceSlot

RelationOccurrenceQualifiers:
  beneficiarySystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment
  onBehalfOfRelationOccurrenceRef?: U.RelationRef constrained to the direct on-behalf-of relation kind
  exerciseScope: U.ClaimScope
  exerciseInterval: QualificationWindowPolicy

Decide exercise from two questions about the existing objects: did this dated Work instantiate the grant’s permitted-action specification, and did its actual performer satisfy the grant’s beneficiary branch?

For a beneficiarySystemRoleAssignmentRef branch, the named assignment must cover the Work and have that performer as holder. For a beneficiarySystemRoleKindRef branch, beneficiarySystemRoleAssignmentRef names the exact covering assignment whose declaration-local kind slot contains that kind and which satisfies the policy’s eligibility rule for that kind. For a beneficiaryPartyRef branch, the performer must be that party or onBehalfOfRelationOccurrenceRef must cite the already obtaining relation whose predicate is defined by its subject pattern and whose use is licensed by the policy. If either question fails, this exercise relation does not obtain.

The match and eligibility are direct obtaining predicates over the Work, grant, action specification, performer, and cited assignment or on-behalf-of relation. If a receiving assurance or audit use needs a separately recorded evaluation or evidence item, identify that item through the applicable evaluation or evidence-use relation; do not mint a placeholder episteme merely to fill this relation.

The exercise relation obtains only when those two predicates hold, the grant obtains throughout the exercise interval, and the work remains in scope. The work is a satisfier of permitted action content. Judge any obligation-satisfaction or discharge claim under the separate evaluation or compliance rule (A.2.8:4.6). The work consumes the grant only when the named policy explicitly makes it single-use or quota-bound.

Non-exercise leaves a grant unused; it continues while the §4.4 conditions hold. Neither non-exercise nor exercise establishes NonViolationFinding@Context without the separate checked-frame evaluation. Work outside the action specification, beneficiary eligibility, scope or window does not exercise the grant; any further consequence follows from the applicable prohibition, commitment, admissibility or Work-related predicate.

When a decision is required, identify its result and use the relevant decision rule; an asserted dated decision Work follows the performer-and-Work route above and any assignment or authority conditions required by that rule.

A.2.8.PER:4.6 - Expose conflict without inventing precedence

PermissionConflictResolutionResultRef ::= U.EpistemeRef
  // resolves only to PermissionConflictResolutionResult@Context

PermissionConflictResolutionResult@Context <: U.Episteme
  conflictFindingRef: U.EpistemeRef
  governingPrecedencePolicyRef: U.EpistemeRef
  resolutionWorkRef: WorkRef
  deciderSystemRef: U.EntityRef
  deciderSystemRoleAssignmentRef: U.RelationRef constrained to U.SystemRoleAssignment
  decisionAuthorityRelationOccurrenceRef: U.RelationRef constrained to the direct decision-authority relation kind
  selectedGrantOccurrenceRef?: U.RelationRef constrained to GrantedPermissionRelation@Context
  selectedNormClaimAddress?: ClaimAddress
  effectiveScope: U.ClaimScope
  effectiveWindow: QualificationWindowPolicy
  reopenConditionClaimAddress: ClaimAddress

PermissionNormConflictFinding@Context <: U.Episteme
  grantedPermissionOccurrenceRef: U.RelationRef constrained to GrantedPermissionRelation@Context
  conflictingNormClaimAddress: ClaimAddress
  overlapScope: U.ClaimScope
  overlapWindow: QualificationWindowPolicy
  governingPrecedencePolicyRef?: U.EpistemeRef
  applicablePrecedenceRuleAddress?: ClaimAddress
  decisionAuthorityRelationOccurrenceRef?: U.RelationRef constrained to the direct decision-authority relation kind
  resolutionWorkRef?: WorkRef
  resolutionResultRef?: PermissionConflictResolutionResultRef
  blockedWorkOrRelianceRef: U.EntityRef
  disposition: unresolved | settledByApplicableRule | settledByDecisionResult
  reopenConditionClaimAddress: ClaimAddress

Create the finding only when the grant and current prohibition or commitment concern the same beneficiary/action content, overlapping scope/window, and incompatible practical conclusions. Check that match directly from the two claims and their participants. Permission and an obligation to perform the same action are not automatically in conflict.

An unresolved finding may omit governingPrecedencePolicyRef when no governing precedence policy has been identified. Keep the disposition unresolved and retain the missing input and what would reopen the question. A settled finding identifies the governing policy and the applicable rule or independently grounded decision result. For a proposed action, blockedWorkOrRelianceRef identifies the action or its WorkPlan under the applicable subject rule; it does not designate a future Work occurrence.

Resolve the conflict through exactly one of two branches:

  1. The current policy already decides. applicablePrecedenceRuleAddress cites the policy claim whose stated conditions match this beneficiary, action, scope, and window. Set settledByApplicableRule only when that rule itself selects which claim governs the blocked use.
  2. A decision is required. Name the admitted U.System that decides, the covering assignment under which it performs the dated resolutionWorkRef, and the independently obtaining authority relation whose predicate is defined by its subject pattern and which authorizes this decision. The direct result relation for that decision must connect the Work to a current PermissionConflictResolutionResult@Context selecting either the grant occurrence or the conflicting norm claim for the stated scope/window.

PermissionConflictResolutionResult@Context is the decision result for this conflict. Exactly one of selectedGrantOccurrenceRef or selectedNormClaimAddress is filled. Its deciderSystemRoleAssignmentRef must cover resolutionWorkRef and have deciderSystemRef as holder; decisionAuthorityRelationOccurrenceRef must independently authorize that decision.

If no policy rule decides and no such current result exists, the disposition remains unresolved, even when a responsible office or system-role kind is named. Permit text, readiness, or a passing gate does not defeat the prohibition.

A.2.8.PER:4.7 - Keep the handshakes narrow

Neighboring objectHandshake
Grant or revoke actAn admitted holder U.System performs the grant-instituting A.2.9 U.SpeechAct under the exact grantor system-role assignment, and institutes.permissions cites the obtaining grant occurrence. A revoking U.SpeechAct is cited through revocationOrSupersessionRef and ends the grant only under the policy’s revocation conditions. Establish each act’s performer and any required assignment attribution or authority under A.2.9 and the applicable policy; the act and grant retain separate identities.
Permit episteme and carrierUse C.2.1 for claims about the permission, E.17 for a source-backed publication face, G.11 for source currentness and publication refresh, and A.10 for evidence used in reliance. Use E.24.PUB when the publication occurrence, form, or carrier identity matters.
Duty or prohibitionA.2.8 U.Commitment; permission remains outside its modality family.
Boundary claim or entry predicateA.6.B classifies the claim; an A-* predicate may consume a separately established current permission result.
Work plan and readinessA.15.2 is the pattern for the U.WorkPlan; A.15.5 may cite a separately established permission/conflict result as one readiness input.
Gate decisionUse A.21 for a gate outcome, citing the separate current grant or conflict result whenever its profile requires one.
Work and resultidentify the dated Work under A.15.1. Exercise requires the direct relation above. Claims of capability, readiness, safety, success, or result quality need their own predicates.

A.2.8.PER:5 - Archetypal Grounding

Assignment, permission, access, and authority. AdminAssignment is a declared U.SystemRoleAssignment species. Occurrence AdminAssignment-4 has admitted System ServiceOperator-4 as holder and AdminSystemRole as assigned-kind value. That fact alone establishes no grant, access, or decision authority. A policy-valid speech act can separately institute one GrantedPermissionRelation@Context for AdminSystemRole, RestartServiceActionSpec, the declared scope, and the declared window. Matching dated Work exercises that grant only through a separate PermissionExerciseRelation@Context.

If service access is claimed, cite its domain access predicate and participants; when no such predicate is available, return A.6.RCD missing-governor[direct service-access relation]. Permission, exercise, access, authority, assignment, and Work therefore remain separate.

Strong grant and exercise. PlantPermissionGrantorAssignment is a declared U.SystemRoleAssignment species. Occurrence MaintenanceCoordinator-A@DayShift has admitted System MaintenanceCoordinator-A as holder, and that System performs a policy-valid grant speech act under the assignment. The act institutes MaintenanceCalibrationGrant-2026-07-19 : GrantedPermissionRelation@Context for MaintenanceTechnicianSystemRole to run CalibrationProcedure-v3 during one service window. Its beneficiary uses beneficiarySystemRoleKindRef.

PlantCalibrationTechnicianAssignment is another declared species. Occurrence Tech-17@Shift-B has admitted technician System Tech-17 as holder and MaintenanceTechnicianSystemRole as assigned-kind value. Tech-17 performs dated CalibrationWork-17B under that assignment. The Work instantiates CalibrationProcedure-v3 within the grant’s zone, window, and scope, so the action-match predicate holds. The assignment covers the Work and satisfies the policy’s eligibility rule for that kind, so the beneficiary predicate holds.

CalibrationExercise-17B : PermissionExerciseRelation@Context therefore connects CalibrationWork-17B to MaintenanceCalibrationGrant-2026-07-19, cites beneficiarySystemRoleAssignmentRef=Tech-17@Shift-B, and states the Work interval and scope. The assignments supply holder and assigned-kind facts for the grant and Work attribution; any required authority relation obtains independently. The grant remains current for the rest of the window because the policy is not single-use. Claims about obligation, readiness, capability, gate passage, a safe result, or successful calibration need their own grounds.

Weak finding. A policy reviewer checks a named, current, sufficiently complete plant-access frame and finds no prohibition applicable to the exact system-role kind, action specification, zone, and window. The result is NonProhibitionFinding@Context(result=nonProhibited), not an instituted grant. If the emergency-policy register cannot be checked, the result is unresolved.

Actual-Work non-violation. After CalibrationWork-17B is performed, CalibrationComplianceEvaluation-17B : U.Work checks that Work against PlantCalibrationNormativeFrame-2026-07-19-e3, whose currentness and sufficient completeness for the technician, procedure, zone, and service-window use are named and whose applicable prohibitions are checked. The result is NonViolationFinding@Context(workRef=CalibrationWork-17B, performerSystemRoleAssignmentRefs={Tech-17@Shift-B}, normativeFrameRef=PlantCalibrationNormativeFrame-2026-07-19-e3, evaluationWorkRef=CalibrationComplianceEvaluation-17B, result=nonViolating). The covering assignment already relates the performer system to the beneficiary system-role kind.

The separate exercise relation shows which grant the Work exercised; exercise alone does not establish non-violation, and non-exercise alone does not establish it either. If the frame is stale or insufficiently complete for this use, the non-violation result is unresolved.

Conflict and non-use. The system-role-kind-level calibration grant still obtains under §4.4 while ContaminatedZoneEntryProhibition-7 forbids the same beneficiary and calibration action in Zone 7 during an overlapping interval. In the direct-rule case, EmergencyCalibrationPrecedencePolicy-e5 contains applicable claim CZ7-Prohibition-Overrides-CalGrant. The rule’s conditions match, so the finding is settledByApplicableRule, cites that rule, and returns “do not enter Zone 7” for the blocked Work.

In a discretionary Zone 8 case, PlantSafetyDecisionAssignment is a declared U.SystemRoleAssignment species. Occurrence SafetyDirector-3@EmergencyShift has admitted System SafetyDirector-3 as holder, and that System performs CalibrationConflictDecisionWork-8 under the assignment. The separately obtaining PlantEmergencyExceptionAuthority-8 relation authorizes that decision, and current CalibrationConflictResolutionResult-8 selects the prohibition claim for the stated scope and window. Only then is the finding settledByDecisionResult.

A second Zone 8 request that merely names the Safety Director but has no dated decision Work or current result remains unresolved. A visible permit and green readiness tile cannot repair either gap. If no calibration Work occurs, the permission is neither exercised nor violated.

A.2.8.PER:6 - Bias-Annotation

The chief bias is document-and-display authority: a readable permit, badge, policy response, or green gate looks stronger than its recoverable relation. The repair is to recover the grounds, participants, policy and its currentness, scope, window, and separate evidence. A second bias is obligation-shaped deontics; the exercise and non-exercise rules preserve permission as latitude.

A.2.8.PER:7 - Conformance Checklist

IDCheck
CC-A2.8.PER-1The current result is exactly NonProhibitionFinding@Context, GrantedPermissionRelation@Context, PermissionExerciseRelation@Context, NonViolationFinding@Context, or PermissionNormConflictFinding@Context.
CC-A2.8.PER-2Beneficiary selects exactly one of beneficiarySystemRoleKindRef : U.KindRef, beneficiarySystemRoleAssignmentRef : U.RelationRef constrained to U.SystemRoleAssignment, or beneficiaryPartyRef : PartyRef, with its branch-specific eligibility test. The branch record is not a new beneficiary U-kind.
CC-A2.8.PER-3A strong grant names the admitted U.System that performs the instituting act, the exact grantor system-role assignment whose HolderSystemSlot resolves to that system, participants, policy edition, ClaimScope and validity window, currentness, and occurrence identity. Any required authority relation obtains independently.
CC-A2.8.PER-4Weak findings require a current frame explicitly complete enough for the intended use; incompleteness returns unresolved.
CC-A2.8.PER-5Exercise names dated work, the admitted U.System that performed it, the one current grant occurrence through a U.RelationRef constrained to GrantedPermissionRelation@Context, scope, and interval; it answers action match and beneficiary eligibility from those objects and the exact covering assignment or on-behalf-of relation.
CC-A2.8.PER-6Neither exercise nor non-exercise establishes NonViolationFinding@Context; non-exercise does not violate the grant, exercise alone does not establish obligation satisfaction, and exercise does not consume a grant without an explicit policy.
CC-A2.8.PER-7A same-scope conflict is settled only by an applicable policy rule that selects the outcome or by a current resolution result produced by dated Work of an admitted system under a covering system-role assignment and independently obtaining decision-authority relation. Naming a policy, office, system-role kind, assignment, or “owner” alone leaves only the affected Work or reliance use unresolved.
CC-A2.8.PER-8Permit episteme, carrier, evidence, admissibility, readiness, gate, capability, Work, and result remain distinct and are handled under their respective subject patterns.

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

Anti-patternRepair
MAY stored as a U.Commitment modalityRecover whether the claim is a strong grant, weak finding, entry predicate, or ordinary prose; use the applicable subject pattern.
No prohibition found, therefore permissionReturn nonProhibited only for a current frame sufficiently complete for the use; otherwise return unresolved. Neither result establishes a grant.
Permit document as permissionRecover the instituting act, current grant occurrence, policy, scope/window, and evidence relation.
Gate pass as authorizationKeep GateDecisionResult in A.21; cite a separate grant/conflict result when the gate consumes one.
Permission as readiness or capabilityKeep readiness in A.15.5 and capability in A.2.2; permission supplies neither.
Work “violates permission”Test exercise coverage and any separately governed prohibition; uncovered work is not a permission violation by default.
Unnecessary evaluation records for action match or beneficiary eligibilityTest the Work against the action specification and the performer against the beneficiary branch; cite the already obtaining assignment or on-behalf-of relation and add separate evaluation evidence only when a receiving use needs it.
Precedence “owner” as resolutionApply a policy rule that itself selects the outcome, or name the authorized system’s dated decision Work and current conflict-resolution result; a system-role kind, office, assignment, or policy title alone decides nothing.
Hidden generic beneficiary kindKeep the closed reference union and branch-specific eligibility checks.

A.2.8.PER:9 - Consequences

Permission becomes inspectable. Practitioners can distinguish a frame-relative result from an enduring grant and from actual exercise, and can stop on unresolved conflict without letting a gate or permit display choose precedence. The cost is recording enough policy, identity, scope, window, and eligibility detail to support the intended use.

A.2.8.PER:10 - Rationale

Positive permission has different satisfaction and failure behavior from obligation. A grant can obtain while unused. Non-use does not violate that grant, but a separate duty may be violated; matching action can exercise the grant without discharging a duty. Separating weak findings, strong grants and exercise preserves these consequences through the existing episteme, relation, speech-act, policy, Work and evidence-use patterns.

A.2.8.PER:11 - SoTA-Echoing

Practice questionSource or practiceFPF alignmentBoundary
How do weak and strong permission differ?Moltmann (2024) distinguishes modal objects, strong permission, weak non-violation, and action satisfiers.Separate frame-relative findings, instituted grants, and actual exercise; retain FPF subject patterns.Do not import modal objects, truthmakers, or possible worlds as U-kinds.
How should permission, duty, and prohibition remain distinct?W3C ODRL 2.2 (2018) models permission, prohibition, duty, assignee, action, constraint, and policy separately.Keep beneficiary, action specification, policy, scope/window, and duty/prohibition predicates and pattern locations explicit.FPF uses direct relations and epistemic findings rather than importing the ODRL information model wholesale.
What makes a policy decision usable?NIST SP 800-207 (2020) and policy-as-code practice separate subject, requested action, resource and operating facts, current policy, and decision evidence.Exercise eligibility and conflict use are bounded by the exact beneficiary, action, normative-frame and policy editions, ClaimScope, window, and intended use.A policy response or gate display is not itself an enduring grant.
How should digital permit evidence be relied on?W3C Verifiable Credentials Data Model 2.0 (2025) separates issuer, holder, verifier, status, proof, and relying context.Permit publications enter A.10 evidence/currentness paths and do not replace the grant relation.Credential form supplies neither permission nor exercise by itself.

A.2.8.PER:12 - Relations

  • Coordinates with: A.2.8 for obligations, recommendations-as-duty, and prohibitions; A.2.9 for instituting or revoking speech acts; and A.6.B and A.6.C for deontic claim classification and agreement-like boundary-language unpacking.
  • Supplies inputs to: A.15.5 readiness and direct mechanism/gate checks only when their own predicates explicitly consume a current grant, finding, or conflict result.
  • Relates to work through: A.15.1 for dated U.Work identity and PermissionExerciseRelation@Context for the separate exercise claim.
  • Uses evidence from: A.10 and publication/currentness patterns for claims about the permission relation and its permit carriers.
  • Does not replace: system-role kind or assignment, capability, plan, gate, admissibility, policy precedence, evidence, performed Work, result, safety, assurance, responsibility, authority, access, or commitment patterns.

A.2.8.PER:End

A.2.9 — U.SpeechAct — Communicative Work and Its Intended Use

Status: Stable Type: Definitional work-ontic pattern Normativity: Normative unless explicitly marked informative

A.2.9:0.1 - Communicative Work and Its Description

U.SpeechAct is the admitted communicative-work kind under U.Work. One individual such as SA-Approve-4711 : U.SpeechAct is an actual temporally bounded speech-act occurrence. A SpeechActRecord : U.Episteme may state claims about that occurrence.

A.2.9:0 - Use This When

Use this pattern when one actual act of communicating matters because either:

  • a named System or audience, including the producer returning later, should understand or do something because of it, and you need to judge the evidence, smallest repair, or stop; or
  • a project must identify, model, audit, or rely on it as performed Work, for example as an approval, authorization, revocation, notice, declaration, or publication.

What goes wrong if missed. A response, silence, later action, or later change is treated as the meaning, achievement, or caused effect of the communication; or a document, interface, ticket, message, or log is treated as if it performed the act. Approval, wording, evidence carrier, commitment, receiving use, and performed Work then collapse into one phrase.

What this buys. A practitioner can first judge what the communication should enable and what evidence or repair the use needs. Communicative Work occurrences remain available for modeling, audit, and reliance without collapsing them into a claim-bearing SpeechActRecord, an utterance description, or an evidence carrier.

Typical moments:

  • a report, model, message, or answer seems clear, but it is unclear who should understand or do what with it or what evidence would be enough;
  • a response, later action, or later change is being used as proof that the named receiving use was achieved or that the communication caused the change;
  • a release, gate, or work step depends on whether a named approval or authorization was performed;
  • a publication, notice, or revocation may have an institutional effect only under an exact current policy or procedure, while the communicative act and any resulting effect retain distinct intervals;
  • a commitment must cite the act that instituted it, rather than only pointing at a document;
  • a message, ticket, signed record, or API call log is being mistaken for the act itself.

Primary EntityOfConcern. The EntityOfConcern is one actual act of communicating, admitted as communicative Work under U.SpeechAct. For a receiving-use question, identify that Work only far enough to say who should understand or do what and to keep the act distinct from its wording, representation, medium, response, and later effect.

When exact occurrence identity, institutional force, audit, or reliance is current, follow §4.1 and SA-C0/SA-C1: recover the A.13 performer core, independently admit the Work through A.15.1, and use F.6 afterward only for a needed precise assignment-bound claim through the same obtaining assignment. Also recover the recognition-taxonomy episteme, effective reference scheme, and any applicable policy or procedure. A SpeechActRecord, MethodDescription, utterance-description episteme, channel, and file, message, ticket, or log carrier remain separate objects.

First useful move. State who should understand or do what because of the communication, including later self-use by its producer, and what evidence would be enough for the present judgement. Keep response, achievement, later action or change, causal contribution, authority, consent, permission, and admissibility separate. Repair the smallest blocker in the wording, representation, prerequisites, medium, interaction, or a future receiving use—or stop.

Only when the named modeling, audit, institutional, or reliance use needs exact occurrence detail, follow the admission and conditional attribution route in §4.1 and SA-C0/SA-C1. Recover taxonomy, scheme, policy, optional channel, and any separate effect only when the use needs them. Create a SpeechActRecord only when a receiving use needs a persistent claim about the already admitted occurrence. Apply SA-C1 when a guard, gate, or claim needs exact assignment-bound attribution; otherwise the record may omit that attribution.

Not this pattern when. If the question is only what a document says, use A.7/C.2/E.17. If the question is only evidentiary support for a later claim or whether the communication caused a later effect, use A.10 or C.28 after identifying that claim. For whether an actual system or party has a duty, use A.2.8. When the Work is not an act of communicating under §4.1, use A.15.1 directly.

A.2.9:1 — Problem frame

FPF repeatedly needs to reference “someone said/did the approving/authorizing/declaring thing”:

  • System-role-assignment eligibility and enactability checklists often depend on the presence of an approval or authorization act within a freshness window.
  • Governance patterns and boundary writing (A.6 stack) need provenance: “this obligation or commitment, or this separately represented granted permission, was instituted by that act”.
  • Operational patterns need auditable notices (“depletion notice”, “override invoked”) whose existence and timing matter.

The same separation is needed before formal occurrence modeling. A reader may need to decide whether a report, answer, model, or message enabled one named use and what to repair. A visible response is not by itself achievement; a later action or change is not by itself evidence that the communication caused it; and the full occurrence-record apparatus should not be a prerequisite for this first bounded judgement.

Without a first-class kind for such communicative Work and a separate way to describe each occurrence, authors tend to:

  • attribute agency to descriptions (“the spec approves…”, “the interface guarantees…”),
  • collapse “utterance text” and “speech act event”,
  • leave provenance dangling as “if modeled”,
  • encode gates as prose obligations, or treat obligations as gates.

The definition below admits U.SpeechAct as an explicit Work kind and states the identity conditions for actual speech-act occurrences; their optional records remain separate from U.Commitment, utterance descriptions, and carriers.

A.2.9:2 — Problem

How can FPF represent communicative enactments so that:

  1. Agency is explicit: §4.1 and SA-C0/SA-C1 require the A.13 performer core, independent A.15.1 Work admission, and F.6 afterward only for a needed precise assignment-bound claim through the same obtaining assignment.
  2. The act is locatable in time: the act has an explicit Window (and thus freshness can be evaluated).
  3. The act is locatable in meaning: the act satisfies a type defined by an exact recognition-taxonomy episteme under an effective reference scheme; no generic bounded-context participant or Work judgement-context field substitutes for that basis, and U.ClaimScope remains only a claim-applicability object when a receiving claim needs one.
  4. The act is auditable: it has at least one declared utterance description, evidence carrier, or both when used for gate checks or governance.
  5. Institutional effects are linkable: the act can institute or update commitments, system-role assignments, statuses, and other exact relations by reference only after each effect’s direct obtaining conditions hold.
  6. Ambiguity is handled pragmatically: the model supports multi-function and multi-party communication without requiring full linguistic pragmatics.
  7. Receiving use stays affordable: a practitioner can name who should understand or do what, judge the available evidence, and repair the smallest blocker or stop without first constructing a complete occurrence record.

A.2.9:3 — Forces

ForceTension
MinimalityThe account should serve routine use without requiring a full pragmatics or legal-instrument model.
AuditabilityIf used as a gate, it must be evidence-backed; but not all communicative acts are equally observable or retainable.
Interpretive localityRecognition and institutional force depend on exact taxonomies, schemes, and current policies; F.9 is needed only when a receiving use crosses local meanings.
Multi-party realityMany boundaries are multiparty (protocols, organizations); dyadic “speaker-hearer” is too narrow.
Multi-function realityOne utterance can carry multiple recognizable functions; “one act = one force” is often false.
Separation disciplineMust preserve kind ≠ actual act occurrence ≠ SpeechActRecord ≠ utterance description ≠ carrier or trace.
Use proportionalityA receiving-use judgement must remain useful without a full occurrence record, while audit or institutional reliance needs exact Work, assignment, Method, taxonomy, and evidence, plus a policy when recognition or institutional force depends on it.

A.2.9:4 — Solution

When a receiving use is current, state who should understand or do what because of the communicative Work, including later self-use by its producer, then judge that Work against evidence relevant to the stated use. A response, silence, later action, or later change may be evidence, but none by itself defines what the utterance means, proves that the use was achieved, or shows that the Work caused the later effect. Keep the communicative Work distinct from its wording, representation, medium, interpretation, response, later action or change, and any causal claim.

Repair the smallest thing that blocks the stated use—for example, wording, representation, prerequisites, medium, interaction, or a future receiving use—or stop. Judge earlier communicative Work against the use stated for that occurrence. A revised use applies to later communication or to a separately named reevaluation; it does not turn the earlier response into achievement of the earlier declared use. Authority, consent, permission, and ethical or institutional admissibility remain separate questions.

When exact occurrence identity, governance, modeling, audit, or reliance is current, use the admitted kernel kind U.SpeechAct. A separate recognition-taxonomy episteme and effective reference scheme make the act-type classification inspectable; an applicable policy or procedure defines any claimed institutional force. A SpeechActRecord may describe the occurrence and point to a MethodDescription, optional channel, utterance descriptions, or evidence carriers; none is the act or enacted Method.

A.2.9:4.1 — Normative definition

U.SpeechAct <: U.Work is a kind declaration. An actual Work individual is admitted as SA : U.SpeechAct when its primary effect is communicative: it places an utterance through an optional channel in a way classified by an exact speech-act recognition taxonomy under an effective reference scheme. A claimed institutional force additionally depends on the applicable current policy, procedure or protocol rule. The taxonomy may distinguish functions such as:

  • asserting/informing,
  • requesting/directing,
  • promising/committing (as an instituting act),
  • declaring/authorizing/revoking (status-changing acts),
  • notifying (event announcement relevant for downstream work).

Per A.7 and A.15.1, the actual speech-act occurrence is a Work individual; its SpeechActRecord and utterance descriptions are epistemes, while its carriers are utterance carriers, publication carriers, or traces that allow observation and audit.

Occurrence identity specializes A.15.1. Admit a candidate as actual communicative Work from one exact communicative performance history, every actual performer’s A.13 core, an enacted Method, temporal extent, and containing-System relation; do not use an F.6 conclusion as an admission premise.

Several satisfied act types classify that one Work occurrence. Identify more than one occurrence only when distinct performance history, enacted Methods, institutional actions, or another admitted discriminator establishes distinct Work. A shared utterance, carrier, assignment, or interval decides neither sameness nor difference. If a named use admits more than one defensible segmentation, cite its continuity or segmentation rule or leave the occurrence boundary unresolved. Check any precise assignment-bound attribution through F.6 only after admission.

Whether a given act type institutes commitments, permissions, publication relations, or status changes depends on an exact current policy or procedure and on the direct obtaining conditions of the claimed effect. Absent that basis, treat SA : U.SpeechAct only as actual communicative Work.

A.2.9:4.2 — Minimal occurrence-description record (normative)

Use the following declaration schema only when a receiving use needs a persistent claim about one already admitted actual speech-act occurrence. The record fields state claims about the referenced occurrence. A source that has only a candidate observation uses the separate non-conformant episteme/stub described under SpeechActRef discipline; it supplies neither a SpeechActRef nor a SpeechActRecord.

U.SpeechAct <: U.Work

SpeechActRef ::= U.EntityRef
  // resolves to one actual Work individual admitted as SA : U.SpeechAct

SpeechActRecord <: U.Episteme

SpeechActRecord ::=
    {
      speechActOccurrenceRef: SpeechActRef,
      actualPerformerSystemRef: U.EntityRef,            // resolves to the A.13-qualified System projected as RA.HolderSystemSlot
      performedUnderAssignmentRef: optional<U.RelationRef constrained to F.6 performedUnderAssignment>, // omit when the record makes no exact assignment-bound attribution; any present reference resolves after independent Work admission to the exact relation for this act and the same obtaining A.13 assignment
      enactsMethodRef: optional<U.EntityRef>,        // resolves to the exact U.Method enacted by the actual Work
      methodDescriptionRef: optional<U.EpistemeRef>, // separate C.2.1 episteme used only when it identifies, constrains, or justifies that Method or intended Work
      unresolvedEnactsMethodClaimAddress: optional<ClaimAddress>,
      methodRelationGapProvenanceRef: optional<U.EpistemeRef>,
      reliancePosture: observationOnly | relianceReady,
      workContainmentRelationRefs: set<U.RelationRef>,       // non-empty; exact locally declared A.15.1 Work-to-System relation occurrences used by this record
      window: [start, end | open],                   // the act occurrence's extent, never an instituted effect's validity interval
      recognitionTaxonomyRef: U.EpistemeRef,         // exact speech-act recognition taxonomy
      effectiveReferenceScheme: EpistemeInterpretationScheme, // exact rules for the recognition-taxonomy claims used by actTypes
      policyOrProcedureRef: optional<U.EpistemeRef>, // current policy/procedure only when recognition or institutional force depends on it
      channelRef: optional<U.EntityRef>,              // optional independently governed communication channel
      utteranceSubjectRefs: optional<set<U.EntityRef>>,
      institutionalTargetRefs: optional<set<U.EntityRef>>,
      actTypes: set<SpeechActTypeRef>,                // ≥1 satisfied classifications under the named taxonomy and scheme
      addressedTo: optional<set<AddresseeRef>>,       // optional: who is addressed / audience
      utteranceDescriptionLocators: optional<set<DescriptionLocator>>, // where the utterance description is stated or recorded (A.7: Description)
      carrierRefs: optional<set<CarrierRef>>,         // evidence carriers/traces (A.7: Carrier; use A.10 when evidentiary)
      institutes: optional<InstitutedEffects>,        // references to separately obtaining objects/relations instituted or updated by this act
      notes: optional<InformativeText>                // explicitly informative
    }

DescriptionLocator ::=
  ClaimAddress | U.EpistemeRef
  // ClaimAddress here means C.2.1 ClaimAddress: exact edition plus intrinsic ClaimGraph identity; the other branch refers to the whole description episteme.

SpeechActTypeRef ::=
  RecognitionTaxonomyLocalTokenRef
  // Must be defined by recognitionTaxonomyRef and satisfied under effectiveReferenceScheme.

AddresseeRef ::=
  exactly one branch when addressee identity is required:
    addresseePartyRef?: PartyRef
    addresseeSystemRoleKindRef?: U.KindRef resolving to one exact local system-role kind
    addresseeSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment

GrantedPermissionRelationRef@Context ::= U.RelationRef constrained to GrantedPermissionRelation@Context
  // resolves only to one exact obtaining grant occurrence

EpistemePublicationRelationRef ::= U.RelationRef constrained to E.24.PUB EpistemePublicationRelation
  // resolves only to one exact obtaining publication occurrence

GovernedInstitutedRelationLink ::= local link record, not a U-kind
  relationOccurrenceRef: U.RelationRef constrained to the exact declared relation kind
  relationRuleLocator: PatternID
    // locates the rule that defines and tests that relation

InstitutedEffects ::=
  {
    commitments: optional<set<U.RelationRef constrained to U.Commitment>>,
    permissions: optional<set<GrantedPermissionRelationRef@Context>>,
    systemRoleAssignments: optional<set<U.RelationRef constrained to U.SystemRoleAssignment>>,
    publicationRelations: optional<set<EpistemePublicationRelationRef>>,
    otherGovernedRelations: optional<set<GovernedInstitutedRelationLink>>
  }

effectiveReferenceScheme carries the exact interpretation rules used for the recognition-taxonomy claims behind actTypes; C.2.1:4.1.2 supplies its range. The selected value must interpret the classification criteria and references. A partial rule collection can satisfy membership while leaving a needed criterion unresolved; the dependent classification then remains unresolved.

Interpret a cited policy, procedure or utterance under its own effective scheme and establish any correspondence needed by the receiving inference under SA-C6. This field supplies the classification basis, not one scheme for every meaning communicated by the Work. The record itself retains its own C.2.1 constitution. Scheme membership establishes neither a satisfied act type nor an institutional effect.

Occurrence-side constraints:

  • (SA‑C0) Actual Work conformance. The individual referenced by speechActOccurrenceRef MUST first satisfy independent A.15.1 admission: every actual performer has the A.13 core for the communicative action, scope, working situation, and window; the performance history is grounded; and the Work has an actual enactsMethod -> U.Method relation, temporal extent, and at least one obtaining locally declared Work-to-System containment relation. Add a characteristic profile only when a Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use consumes it.

    A record that makes no exact assignment-bound attribution MAY omit performedUnderAssignmentRef. Whenever that field is present or the record claims exact assignment-bound attribution, it MUST resolve to a separate F.6 relation established after admission for this already admitted act through the same obtaining A.13 assignment. methodDescriptionRef, when present, cites a separate C.2.1 episteme; the description is not enacted.

  • (SA‑C1) The System performs; exact attribution reuses the same assignment. The performer MUST be an admitted U.System that satisfies and is classified under one exact local agential system-role kind for this act. An observation-only or otherwise non-attribution record MAY omit performedUnderAssignmentRef and MUST NOT be used to satisfy a guard, gate, or claim that depends on exact assignment-bound attribution. If the field is present, it MUST resolve to the separately obtaining F.6 performedUnderAssignment relation for the already admitted act and the same obtaining assignment occurrence named by A.13, together with its declared U.SystemRoleAssignment species. If a guard, gate, or claim relies on exact assignment-bound attribution, the field MUST be present and that F.6 relation MUST obtain.

    The assignment MUST have the performer as holder, supply every other participant, cover the act, and satisfy its species predicate for the required scope, working situation, and window. Evidence supports those core facts; a characteristic profile enters only when conditionally consumed. The taxonomy episteme and the rules used to interpret its claims supply the classification basis; they are not assignment participants. Establish any authority required by the receiving use under its applicable rule.

  • (SA‑C2) Act types are independently satisfied recognition classifications. The occurrence MUST instantiate at least one SpeechActTypeRef defined by the exact recognitionTaxonomyRef under the stated effectiveReferenceScheme. If a policy or procedure supplies an additional recognition condition, cite its exact current episteme and satisfy that condition separately.

  • (SA‑C3) Actual extent and interval separation. The occurrence MUST have an actual temporal extent so freshness can be evaluated; the record’s window is a claim about that act extent. Every instituted commitment, grant, publication relation, status relation, or other effect keeps its own independently governed occurrence or validity interval. Coincident boundaries do not merge act and effect.

  • (SA‑C3a) Policy, procedure, and channel remain neighbors. A cited policyOrProcedureRef is a separate current C.2.1 episteme; its currentness, applicability, and any edition relation must be established under their subject patterns. An optional channelRef names an independently governed communication route or participating entity.

Keep three questions separate. utteranceSubjectRefs answers what the utterance or claim is about. institutionalTargetRefs answers which object or relation the act is intended to institute or update, or which episteme edition it is intended to publish, under the cited current policy or procedure. Actual change or institutional effect is a third world-side fact and is stated only through its exact direct change/effect relation and the matching typed institutes.* reference when the record needs it. An informative notice or assertion may have a subject without any institutional target or changed entity. Shared reference values do not collapse these relation meanings.

Record- and reliance-side constraints:

  • (SA‑C4) A relied-on occurrence must be observable. When a gate or checklist, or a judgement about a commitment or grant, relies on a SpeechActRef, the SpeechActRecord SHALL identify that same occurrence and cite at least one applicable entry from utteranceDescriptionLocators or carrierRefs, or a separately governed evidence relation. Evidence-critical uses SHOULD cite at least one carrier through A.10. Record completeness alone does not prove occurrence or institutional force.
  • (SA‑C5) Institutional-effect claims are typed references to world-side effects. institutes.* may reference only a separately obtaining commitment or relation occurrence through its declared RefKind. Each institutes.commitments value resolves through U.RelationRef constrained to U.Commitment and is usable only when an identified policy applies and A.2.8’s bearer, constitutive-rule, instituting-basis, and continuation conditions hold. Each institutes.permissions value resolves to one GrantedPermissionRelation@Context whose participants, policy, scheme, and validity satisfy A.2.8.PER; each institutes.systemRoleAssignments value resolves to one occurrence whose species is declared under A.2.1; and each publication value resolves to an obtaining EpistemePublicationRelation under E.24.PUB. A status claim is an episteme about an effect; keep it and its A.10 evidence relation outside institutes.*. A Bridge is added only if the receiving inference depends on translating or comparing local meanings across schemes.
  • (SA‑C6) F.9 only for a cross-locality dependency. Cite an F.9 Bridge when a receiving check, gate, provenance claim, or effect inference compares, substitutes, or transfers a speech-act type or policy meaning between different local taxonomies, schemes, or policies. A different consumer, organization label, repository location, or downstream use does not by itself create that dependency. The same token in two local schemes does not establish equivalence, and a Bridge does not transfer institutional force by itself.

A.2.9:4.3 — SpeechActRef discipline (normative)

A SpeechActRef resolves to one actual Work individual admitted as SA : U.SpeechAct. It never denotes the kind itself or a SpeechActRecord.

  • If an A.2.8 commitment predicate or assertion cites this occurrence as its instituting basis, the referenced occurrence MUST satisfy occurrence-side SA‑C0…SA‑C3a. Citing the act in the obtaining predicate identifies the required world-side basis; it does not itself require a record. A receiving judgement that relies on this occurrence, including a commitment or grant judgement, gate, audit, or provenance claim, additionally needs the record and evidence basis in SA‑C4. It needs SA‑C6 only when its inference crosses local taxonomies, schemes, or policies.

  • A SpeechActRef MUST NOT be replaced by an EpistemeRef (“see the document”) when occurrence provenance is needed. A SpeechActRecord or utterance-description episteme may make claims about the occurrence but is not the act.

  • If a source cannot yet establish A.15.1 admission for one actual occurrence, it may create a separate U.Episteme identified as a candidate observation stub. The stub is not a SpeechActRecord, supplies no SpeechActRef or speechActOccurrenceRef, and does not conform to the complete declaration schema or SA-C0. It carries a source-local candidate locator or C.2.1 ClaimAddress, known observation claims, provenance for those claims, and explicit unknowns.

    If the actual enactsMethod -> U.Method relation cannot yet be recovered, record that unresolved claim and its source-gap provenance in the stub; do not invent a U.MethodDescription to establish the missing Method relation. The stub supports no gate or deontic provenance and remains observation-only. After A.15.1 independently admits one exact actual occurrence, create a distinct conformant SpeechActRecord; do not promote or relabel the stub in place, though a separately governed provenance or evidence relation may cite it.

A.2.9:4.4 — Separation rules with U.Commitment, GrantedPermissionRelation@Context, and U.PromiseContent (normative)

  1. Instituting an enduring deontic relation. A speech-act occurrence may be the actual instituting basis for one U.Commitment or GrantedPermissionRelation@Context only under an exact current constitutive policy or rule and the effect pattern’s satisfied direct predicate. The enduring relation is separately identified. To state an instituted effect in SpeechActRecord, cite its already obtaining occurrence in institutes.commitments or institutes.permissions; quoted duty or permission wording alone does not establish that effect.

  2. Promise content and the act of offering it. U.PromiseContent is the promised-outcome statement. A speech act may offer or issue that promise; any resulting commitment references the separate promise-content episteme.

  3. The act and its evidence carrier. A “signed approval PDF”, ticket, message, or API log is a carrier; it may carry an utterance-description episteme or a SpeechActRecord. The speech act is the Work occurrence described or evidenced.

  4. Conditions for publication and institutional effects. Default interpretation rule (normative). A conformant model/interpreter MUST NOT infer a U.Commitment, GrantedPermissionRelation@Context, publication occurrence, or subject-specific status relation solely from a Publish/Approve speech-act occurrence or its record. Publication work may establish an EpistemePublicationRelation only when E.24.PUB’s selected edition, audience declaration, bounded-use declaration, independently identified expression, carrier, and availability conditions obtain. A constitutive policy may let an act institute a subject-specific Approved, Published, or similar status relation; then cite that exact relation occurrence through the subject pattern and separately cite any C.2.1 status claim and A.10 evidence. The claim represents the status; judge whether that status obtains under the cited status rule.

A.2.9:4.5 — Multi-function and multi-party support (normative)

  • Multi-function: actTypes is a set. When one actual communicative Work performs several recognizable functions, one speech-act occurrence carries all satisfied actTypes. Identify several occurrences only when the occurrence-identity rule in §4.1 finds distinct world-side grounds. Their records may share utterance or carrier references. If the named use admits competing segmentations, cite its continuity or segmentation rule or leave the boundary unresolved. Institutional effects remain separately referenceable (SA‑C5).

  • Multi-party: addressedTo is a set. Its optional members may be parties, exact local system-role kinds, or exact obtaining occurrences of directly declared U.SystemRoleAssignment species. State which branch each addressee uses. Identify the actual performer and establish any claimed authority, commitment, permission, responsibility or institutional effect under their applicable rules.

A.2.9:5 — Worked Communication Uses

A.2.9:5.1 — Receiving-Use Judgement and Observation Record

When a named receiving use is current, first state who should understand or do what, what evidence would be enough, and the smallest repair or stop. Keep the act of communicating, its wording and medium, observed response, achieved use, later effect, causal contribution, and authority or permission questions distinct.

When governance or gating depends on “someone said or did X”, first identify that saying or doing as SA : U.SpeechAct through the A.13-qualified performer, grounded communicative history, Method, extent, and containment required by A.15.1. Then, if the gate relies on the exact assignment under which it was performed, establish F.6 separately through the same A.13 assignment. Add a SpeechActRecord only to state relied-on claims about the already admitted act, and keep any MethodDescription, optional channel, utterance text, and carriers separate. If the occurrence institutes an obligation, recommendation-as-duty, or prohibition, cite a separately obtaining U.Commitment; if it institutes strong permission, cite a GrantedPermissionRelation@Context. The act institutes neither effect without an applicable policy or rule and independently satisfied conditions.

Receiving-use worked slice. An engineer sends a threshold-change note to an operator. The named use is that the operator can identify the new threshold and the next safe action; the engineer should also be able to recover the reason for the change later. The operator replies “Got it” but updates the wrong parameter. That reply is evidence of a response, not achievement of the named use. The parameter update is a later action and world change; it does not by itself show that the note caused the change. Use A.10 when the evidentiary claim needs support and C.28 before claiming causal contribution.

Persistent observation-only record slice. After A.13 supplies the performer basis and A.15.1 independently admits SA-Threshold-Change-17 : U.SpeechAct, a later review needs a durable observation that the threshold note occurred but makes no claim about the exact assignment under which it was sent. SA-Threshold-Change-17-Record : SpeechActRecord states the occurrence and actual-performer references, actual Method and containment references, act window, recognition taxonomy and scheme, act type, utterance-description locator, and carrier; it sets reliancePosture = observationOnly and omits performedUnderAssignmentRef. This record can preserve the observation and support receiving-use replay, but it cannot satisfy a guard, gate, or claim that depends on exact assignment-bound attribution. If that use later becomes current, establish F.6 for the already admitted act through the same obtaining A.13 assignment and add the resolving reference.

The smallest repair may be a clearer threshold sentence or a changed table, followed by evidence that addresses the named use. If the operator lacks permission to make the change, return that blocker instead of repeating the message. If a later need adds audit use, apply it to later communication or a separately named reevaluation. It does not turn “Got it” into achievement of the earlier use.

A.2.9:5.2 — Change-Control Approval and Deployment

Initial claim: “Change is approved, so the pipeline may deploy.”

Conformant modeling sketch. The first line names the actual communicative Work. The record then states claims about that occurrence. Check separately that the assignment and enacted-Method relations obtain, that the act satisfies the recognition classification, that the policy is current and applicable, and that the grant obtains. Because the deployment gate relies on exact assignment-bound attribution, this attribution-bearing record must include performedUnderAssignmentRef and its F.6 relation must obtain for the already admitted act through the same A.13 assignment.

  • Actual occurrence: SA-Approve-4711 : U.SpeechAct.

  • Performer and assignment: ApproverSystemRole is an exact local agential system-role kind whose criterion for this use is the capacity to issue the policy-recognized approval act under the board procedure; CAB_Chair_A is classified under it for this scope and window, and evidence supports that core classification without a Grade or autonomy-profile claim. ChangeControlApproverAssignment is a declared U.SystemRoleAssignment species. Under A.2.1 it declares the ordered holder and assigned-kind positions, their domains U.System and ChangeControlApproverSystemRoleKindDomain, its direct predicate and applicability, and its occurrence-identity rule.

    Occurrence CAB_Chair_A_ApproverAssignment_2026 obtains with admitted System CAB_Chair_A as holder, ApproverSystemRole as assigned-kind value, and an extent covering the act; it is the same assignment used by A.13 and F.6. CAB_Chair_A performs SA-Approve-4711 under that assignment. Taxonomy ChangeControlSystemRoles_v3 and ChangeControlReferenceScheme_2026 interpret the assertion rather than becoming assignment participants. The assignment grounds attribution. Apply the current approval policy’s authority conditions to CAB_Chair_A.

  • Actual Method and containing-system relations: enactsMethod(SA-Approve-4711, ChangeApprovalMethod_v3) independently obtains, with ChangeApprovalMethod_v3 : U.Method. ChangeControlWorkBoundaryRelations declares ApprovalWorkOccursWithinBoardBoundary(work, system) for the board-system delimitation and act window; occurrence ApprovalWorkWithinBoardBoundary-4711 obtains for SA-Approve-4711 and ChangeControlBoardSystem.

  • SA-Approve-4711-Record : SpeechActRecord states:

    • speechActOccurrenceRef = SpeechActRef(SA-Approve-4711);
    • actualPerformerSystemRef = U.EntityRef(CAB_Chair_A);
    • performedUnderAssignmentRef = U.RelationRef(PerformedUnderApprovalAssignment-4711), resolving to the F.6 relation between SA-Approve-4711 and CAB_Chair_A_ApproverAssignment_2026;
    • enactsMethodRef = U.EntityRef(ChangeApprovalMethod_v3);
    • methodDescriptionRef = EpistemeRef(ChangeApprovalProcedure_v3), a separate C.2.1 episteme used here to identify and constrain the Method;
    • recognitionTaxonomyRef = EpistemeRef(ChangeControlSpeechActTaxonomy_v3);
    • effectiveReferenceScheme = ChangeControlReferenceScheme_2026;
    • policyOrProcedureRef = EpistemeRef(ChangeControlApprovalPolicy_v3), current for this approval and grant use;
    • channelRef = U.EntityRef(CAB_TicketChannel);
    • actTypes = {SpeechActTypeRef(Approval)} under that taxonomy and scheme;
    • reliancePosture = relianceReady, workContainmentRelationRefs = {U.RelationRef(ApprovalWorkWithinBoardBoundary-4711)}, and window = [2026-06-12T10:03Z, 2026-06-12T10:04Z];
    • utteranceSubjectRefs = {ChangeRequestId(4711)};
    • institutionalTargetRefs = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)};
    • utteranceDescriptionLocators = {U.EpistemeRef(ChangeTicket#4711)} and carrierRefs = {CarrierRef(TicketSystemRecord#4711)};
    • institutes.permissions = {GrantedPermissionRelationRef@Context(PER-Deploy-4711)}.

PER-Deploy-4711 : GrantedPermissionRelation@Context obtains separately under A.2.8.PER:

  • beneficiarySystemRoleAssignmentRef = U.RelationRef(OpsBotDeployerAssignment-CD_Pipeline_v7), resolving to the assignment occurrence and its declared U.SystemRoleAssignment species;
  • permittedActionSpecificationRef = EpistemeRef(DeployChange4711WorkSpecification);
  • institutingSpeechActRef = SA-Approve-4711;
  • grantorSystemRoleAssignmentRef = U.RelationRef(CAB_Chair_A_ApproverAssignment_2026);
  • grantValidityPolicyRef = EpistemeRef(ChangeControlGrantPolicy_v3) under ChangeControlReferenceScheme_2026; the separately cited ChangeControlApprovalPolicy_v3 supplies the act-to-grant instituting rule;
  • scope, revocation stance, and validity interval [2026-06-12T10:04Z, 2026-06-19T10:04Z] are explicit.

The one-minute speech-act interval and seven-day grant interval are different facts even though the latter begins when the former ends.

The utterance is about ChangeRequestId(4711); its policy-selected target and demonstrated effect are the separately obtaining grant. Nothing here claims that the change-request entity itself changed.

Gate predicate A-Gate-Deploy-4711 may check exists SpeechAct(type=Approval, utteranceSubjectRefs includes ChangeRequestId(4711), actualPerformerSystemRef=CAB_Chair_A, performedUnderAssignmentRef=PerformedUnderApprovalAssignment-4711, within 90d), consume the current grant, and apply other prerequisites; passing the gate neither institutes nor equals the grant. No F.9 Bridge is needed merely because a pipeline consumes the result. A Bridge becomes current only if another receiving use translates or compares a different local meaning.

Near misses. A ticket row alone is a carrier-backed claim, not the act. ChangeApprovalProcedure_v3 is a MethodDescription, not what the act enacts. A current approver assignment does not prove that approval Work occurred. Without the exact current policies, the occurrence remains communicative Work but establishes no grant.

A.2.9:5.3 - Publishing a Specification Edition

Situation: “The interface spec declares MUST/SHALL requirements.” This sentence describes the specification’s contents. The current task is to model publication of version 12 and determine its institutional effects.

Conformant modeling sketch. SA-Publish-API-v12 : U.SpeechAct is the act. PublisherSystemRole is an exact local agential system-role kind whose criterion for this use is the capacity to execute the policy-recognized publication act; StandardsEditor_A is classified under it for this scope and window, and evidence supports that core classification without a Grade or autonomy-profile claim. StandardsPublicationAssignment is a declared U.SystemRoleAssignment species. Under A.2.1 it declares the ordered holder and assigned-kind positions, their domains U.System and PublisherSystemRoleKindDomain, its direct predicate and applicability, and its occurrence-identity rule.

Occurrence StandardsEditor_A_PublisherAssignment_v12 obtains with admitted System StandardsEditor_A as holder, PublisherSystemRole as assigned-kind value, and an extent covering the act; it is the same assignment used by A.13 and F.6. StandardsEditor_A performs the act under that assignment. Taxonomy StandardsSystemRoles_v12 and APISpecReferenceScheme_v12 interpret the assertion but are not assignment participants. The Work enacts Method SpecPublicationMethod_v12; SpecReleaseProcedure_v12 is a separate description of that Method.

SpecPublicationWorkBoundaryRelations declares PublicationWorkOccursWithinSpecSystemBoundary(work, system) for the publication-system delimitation and act window; occurrence PublicationWorkWithinSpecSystemBoundary-v12 obtains for SA-Publish-API-v12 and SpecPublicationSystem. SA-Publish-API-v12-Record : SpeechActRecord states:

  • speechActOccurrenceRef = SpeechActRef(SA-Publish-API-v12);
  • actualPerformerSystemRef = U.EntityRef(StandardsEditor_A) and performedUnderAssignmentRef = U.RelationRef(PerformedUnderPublisherAssignment-v12), resolving to the F.6 relation between the act and StandardsEditor_A_PublisherAssignment_v12;
  • enactsMethodRef = U.EntityRef(SpecPublicationMethod_v12) and methodDescriptionRef = EpistemeRef(SpecReleaseProcedure_v12);
  • recognitionTaxonomyRef = EpistemeRef(APISpecSpeechActTaxonomy_v12) and effectiveReferenceScheme = APISpecReferenceScheme_v12;
  • policyOrProcedureRef = EpistemeRef(APISpecPublicationPolicy_v12) and optional channelRef = U.EntityRef(StandardsReleaseChannel);
  • actTypes = {SpeechActTypeRef(Publish), SpeechActTypeRef(DeclareNorms)} under that taxonomy and scheme;
  • reliancePosture = relianceReady, workContainmentRelationRefs = {U.RelationRef(PublicationWorkWithinSpecSystemBoundary-v12)}, and window = [2026-06-14T09:00Z, 2026-06-14T09:06Z];
  • utteranceSubjectRefs = {EpistemeRef(APISpec_v12)}, institutionalTargetRefs = {EpistemeRef(APISpec_v12)}, utteranceDescriptionLocators = {U.EpistemeRef(APISpec_v12)}, and carrierRefs = {CarrierRef(GitTag:v12), CarrierRef(SignedReleaseArtifact:v12)};
  • institutes.publicationRelations = {EpistemePublicationRelationRef(APISpec-v12-Publication)}.

APISpec-v12-Publication : EpistemePublicationRelation separately names the selected APISpec_v12 edition, audience declaration, bounded-use declaration, exact expression, exact carrier, availability interval and governing publication conditions under E.24.PUB. It obtains only while those five participants remain fixed and that expression remains available from that carrier under those conditions. A selected reusable form has its separate conformance relation; broader availability of the edition can continue through another exact publication. Its interval need not equal the six-minute publishing act. The same episteme can be both utterance subject and publication object without those relations becoming identical.

Publication makes the selected APISpec_v12 edition available with its claim content unchanged. If D-StdStatus-APISpec_v12-Published is needed, keep it as a separate C.2.1 claim about the exact publication relation and cite its evidence through A.10; do not put the claim in institutes. Norms live in the published utterance description, while StandardsEditor_A performs the publishing Work. Another audience or scheme needs F.9 only when a receiving use translates or substitutes the local act or policy meaning.

Bounded non-use. If the only question is what APISpec_v12 says, stop at A.7/C.2/E.17. If the question is whether it is available to an audience, use E.24.PUB. If the question is evidentiary support for a status claim, use A.10. Keep A.2.9 only when the actual communicative Work occurrence itself matters.

A.2.9:6 — Bias-Annotation

The account favors explicit performers, recognizable communicative functions and evidence suited to a named use. Its limits are:

  • Exact occurrence and institutional claims need the performer and evidence basis, which adds modeling effort; an ordinary receiving-use judgement can remain conversational.
  • Recognition covers the functions needed by the use; the account does not provide a full model of intention, sincerity or perlocutionary psychology.

A.2.9:7 — Conformance Checklist (normative)

  1. CC‑A.2.9‑1 (Occurrence, performer, and assignment). One Work individual is admitted as SA : U.SpeechAct only through the independent A.13/A.15.1 route: exact actual performer System, local agential kind and criterion, classification, obtaining assignment, scope, working situation, window, adequate core evidence, conditionally consumed profile, grounded communicative history, enacted Method, extent, and containment. Any precise assignment-bound attribution is then checked separately through F.6 with the same obtaining assignment; its declared species, holder, other participants, predicate, and coverage remain recoverable.

    A SpeechActRecord MUST identify the actual performer through actualPerformerSystemRef, MAY omit performedUnderAssignmentRef when it makes no exact assignment-bound attribution, and MUST make every present attribution reference resolve to the F.6 relation for the already admitted act and the same A.13 assignment. The record MUST NOT claim authority on the basis of assignment alone.

    • CC‑A.2.9‑1a (Occurrence identity and segmentation). Several satisfied actTypes classify one communicative Work unless distinct performance history, enacted Methods, institutional actions, or another admitted discriminator establishes distinct occurrences. Shared utterance, carrier, or interval is not enough; unresolved competing segmentations retain an explicit continuity or segmentation question.
  2. CC‑A.2.9‑2 (Exact Method and auxiliary description). The actual occurrence independently satisfies enactsMethod -> U.Method. A current methodDescriptionRef resolves to a separate C.2.1 episteme used to identify, constrain, or justify that Method or intended Work; neither the reference nor the description is enacted.

  3. CC‑A.2.9‑3 (Recognition taxonomy and scheme). The actual occurrence satisfies at least one SpeechActTypeRef defined by the exact recognition-taxonomy episteme under the stated effective reference scheme. Merely writing a token into SpeechActRecord.actTypes is insufficient.

  4. CC‑A.2.9‑4 (Actual extent versus effect interval). The occurrence has an actual temporal extent, and a record’s window truthfully states it at the required precision. Every instituted relation keeps its own occurrence or validity interval.

  5. CC‑A.2.9‑5 (Observable relied-on occurrence and attribution branch). If a checklist, guard, or judgement about a commitment or grant relies on the occurrence, apply SA-C4: one SpeechActRecord identifies it and cites an applicable utterance, carrier, or direct evidence relation. Evidence-critical uses SHOULD cite at least one carrier through A.10. If that checklist, guard, gate, or claim relies on exact assignment-bound attribution, the record MUST include performedUnderAssignmentRef and satisfy SA-C1 through the separately obtaining F.6 relation for the already admitted act and same A.13 assignment; a record that omits the field cannot close that attribution-dependent use.

  6. CC‑A.2.9‑6 (Current policy and typed world-side effects). A record’s institutes.* branch references only an exact commitment or obtaining relation occurrence through its declared relation-occurrence RefKind. An otherGovernedRelations item also names the rule that defines and tests that exact relation. An institutional effect obtains only when the current policy or procedure supplies the applicable constitutive rule and current facts satisfy the direct predicate defined in its pattern or declaration; a status claim and its evidence stay separate.

  7. CC‑A.2.9‑7 (F.9 only for cross-locality dependence). A receiving claim cites an F.9 Bridge only when it compares, substitutes, or transfers speech-act or policy meaning across different local taxonomies, schemes, or policies. A new consumer or locality label alone neither requires a Bridge nor transfers force.

  8. CC‑A.2.9‑8 (No fabricated method anchor or candidate record). If the actual enactsMethod -> U.Method relation cannot be recovered well enough to establish A.15.1 admission, do not create a conformant SpeechActRecord. Put the unresolved claim, source-gap provenance, known observations, and explicit unknowns in the separate candidate observation stub; that stub remains observation-only and cannot support a gate or deontic provenance. A placeholder U.MethodDescription never closes the gap. After actual admission, create a distinct complete record rather than promoting the stub in place.

  9. CC‑A.2.9‑9 (Subject, target, and effect stay distinct). A record uses utteranceSubjectRefs for aboutness and institutionalTargetRefs only for a policy-selected target. It claims actual change or institutional effect only through the exact direct relation; an informative act needs no changed target.

  10. CC‑A.2.9‑10 (Optional channel stays separate). A channelRef, utterance description, carrier, or trace may support identification or observation.

  11. CC‑A.2.9‑11 (Receiving use, evidence, and later effect). When communicative Work is judged for a named receiving use, state who should understand or do what and which evidence supports that judgement. A response or silence alone establishes neither meaning, achievement, causation, authority, consent, permission, nor admissibility. A revised use applies to later communication or to a separately named reevaluation; it does not turn the earlier response into achievement of the earlier declared use.

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

Anti-patternWhy it failsRepair
Episteme or assignment in the actual-performer field (actualPerformerSystemRef resolves to a spec or assignment)an occurrence claim assigns Work to a description or relationfirst admit the actual act through the independent A.13/A.15.1 route; use actualPerformerSystemRef for the A.13-qualified holder System; only for a precise assignment-bound claim, add performedUnderAssignmentRef for the separately established F.6 relation; establish any required authority relation independently
Kind/occurrence/record collapse (U.SpeechAct used for all three)a complete record is mistaken for actual Workreserve U.SpeechAct for the kind, identify SA : U.SpeechAct as the occurrence, and use SpeechActRecord only for claims about it
Carrier in the occurrence-reference field (speechActOccurrenceRef resolves to a PDF carrier)conflates carrier with actidentify the actual speech-act occurrence; let its separate SpeechActRecord cite the PDF carrier and any utterance-description episteme
Placeholder method as Work anchora fabricated description hides an unknown world-side relationkeep the unresolved claim and source-gap provenance in a separate candidate observation stub; do not call it a SpeechActRecord or use it for reliance; recover the actual Method relation before A.15.1 admission and creation of the complete record
affected as aboutness, target, and effectone field makes mention look like world-side changestate the utterance subject and intended institutional target separately; cite an exact obtaining change/effect relation only when one exists
Status claim listed as instituted effecta claim ID is mistaken for the status it describescite the exact status or publication relation occurrence; keep the C.2.1 claim and A.10 evidence separate
Free-text type (“type=‘approved-ish’”)the claimed act type has no recoverable recognition criteriondefine SpeechActTypeRef in the exact recognition-taxonomy episteme and interpret it under the effective reference scheme
Generic judgement-context fieldone container word hides taxonomy, scheme, policy, channel, and receiving usename only the exact recognition taxonomy, effective scheme, current policy/procedure, optional channel, and any F.9 crossing
MethodDescription as enacted Methoda procedure episteme is made the world-side way of doingrecover exact enactsMethod -> U.Method; cite methodDescriptionRef only as a separate identifying, constraining, or justifying episteme
Channel or carrier as acttransmission or evidence is mistaken for communicative Workidentify the exact speech-act occurrence; keep optional channel, utterance description, and carriers in their direct relations
Quoted obligation treated as an instituted dutywording in the utterance or record is treated as the deontic relationidentify each separately obtaining U.Commitment occurrence instituted under the applicable rule
Gating without windowcannot evaluate freshnessadd explicit window and reference it in the guard/checklist
Untraced commitments (several commitments attributed to one act without identifying each obtaining relation)loses instituting-act traceabilityuse one actTypes set for one communicative Work and reference each separately obtaining commitment in institutes.commitments; identify several acts sharing a carrier only when distinct world-side grounds satisfy §4.1

A.2.9:9 — Consequences

Benefits

  • Explicit references to approvals, authorizations, and notices support state-condition and admission checks when the selected predicate or direct consumer requires the act.
  • Provides stable provenance: commitments, granted permissions, and status transitions can cite the instituting act explicitly.
  • Makes the actual performer recoverable in occurrence and institutional-provenance claims.
  • Lets a practitioner judge one named receiving use and repair the smallest blocker without first building a complete occurrence record.
  • Keeps observed response, achieved use, later action or change, causal contribution, and permission or admissibility as separately testable questions.

Trade-offs / mitigations

  • A receiving-use judgement may remain conversational when no later claim must cite it. A reliance-bearing use requires a small structured SpeechActRecord plus adequate evidence only when the occurrence itself must remain addressable.
  • Requires one exact recognition-taxonomy episteme and effective reference scheme for SpeechActTypeRef; mitigated by starting with a small set (Approve, Revoke, Publish, Notify, Authorize) and extending that taxonomy deliberately.

A.2.9:10 — Rationale

FPF uses communicative acts both for ordinary receiving uses and as operationally meaningful events such as approvals, notices, and overrides. A.2.9 begins with who should understand or do what and the evidence needed for that use, then admits U.SpeechAct through the independent A.13/A.15.1 route when exact occurrence identity is current. F.6 follows only for a separate precise assignment-bound attribution. It treats each actual act as a temporally bounded Work individual enacting an exact Method and uses SpeechActRecord only for claim-bearing representation. Occurrence admission remains independent of its description and of any later assignment-bound attribution judgement.

A.2.9:11 — SoTA-Echoing (informative)

Informative. Alignment notes; not normative requirements.

  • ISO 24617‑2:2020 / multi-dimensional communicative functions. Modern dialogue‑act standards treat communicative behavior as potentially multi‑functional. A.2.9 mirrors this with an actTypes set on one communicative Work and permits shared carriers across several acts only when their world-side histories establish distinct occurrences.
  • Commitment-based semantics for communication (multi-agent/protocol practice, 2015+). A pragmatic way to avoid mental-state modeling is to track communication by its social/institutional effects, especially on commitments, permissions, and protocol states. A.2.9 reflects this via separate institutes.commitments and institutes.permissions links to U.Commitment and GrantedPermissionRelation@Context without modeling sincerity or intention.
  • Illocutionary pluralism in multiparty discourse (2015+). One utterance can perform multiple recognizable functions. A.2.9 avoids the “single force” trap by allowing several recognized functions on one act, while several acts sharing an utterance or carrier require distinct occurrence grounds.
  • Purpose-relative grounding evidence and structured interaction. Clark and Brennan’s (1991) purpose-relative grounding principle is a historical anchor: evidence of understanding must be sufficient for the current purpose. Studies of grounding gaps in human–LLM dialogue (Shaikh et al., 2024, 2025) reinforce the risk of presumed shared understanding, while one structured-interface study (Do et al., 2024) shows that interaction structure can help in its tested setting. Section 5.1 applies that line by naming the receiving use and evidence first, then changing the wording, representation, prerequisite, medium or interaction that blocks it. A reply, silence or favourable outcome alone does not fix meaning, prove achievement or establish causal contribution. For the named receiving use, reconsider the affected evidence threshold or interaction choice when new evidence, changed participants, a changed medium or a failed source transfer invalidates its basis.

A.2.9:12 — Relations

Uses / builds on

  • Uses A.13 for the actual performer’s agency basis and A.15.1 (U.Work) for independent admission of the communicative occurrence. Uses F.6 only afterward for a needed precise performedUnderAssignment claim through the same obtaining assignment. Uses a separate optional methodDescriptionRef only when the receiving claim needs that episteme.
  • Uses A.7 for the actual-act≠record/description≠carrier split.
  • Coordinates with A.2.6 for scope/window discipline.
  • F.18 can serve as a lexical entry point for naming U.SpeechAct and “utterance” in the promise/utterance/commitment triad.

Used by

  • A.2.8 (U.Commitment) when an exact policy treats the speech act as the required instituting basis and the direct commitment predicate independently holds, and A.2.8.PER when a GrantedPermissionRelation@Context independently obtains with this act as institutingSpeechActRef.
  • A.2.5 (assignment-state predicates and their Work-admission use) when the selected state predicate or direct consumer requires an authorization or approval act.
  • A.6.C for unpacking promise, approval, guarantee, and agreement-like boundary wording while preventing episteme-as-agent claims and preserving provenance.

A.2.9:End

A.3 - Transformer Quartet: Distinguish Work, Performer, Method and Method Description

Status: Stable

A.3:1 - Intent

Use this pattern to distinguish a performed Work occurrence from its performer, enacted Method and any relied-on MethodDescription. Recover each performer’s A.13 basis, then admit the dated Work independently through A.15.1 with its enacted Method. Use F.6 when the account also needs precise assignment-bound attribution. Add MethodDescription, capability, work-to-change, evidence or aggregation claims only when the receiving use relies on them.

The Transformer Quartet keeps those object families distinct; it does not require every change claim or Work assertion to name all four. A.3.4 independently identifies an actual bounded change. That result alone establishes no acting System, agency, assignment, Method or Work. A.2, A.15.1 and C.2.1 define the neighboring objects; A.7 preserves their distinctions and A.10 governs evidence use.

A.3:2 - Context

  • Holonic substrate. FPF distinguishes what things are (Holon → {System, Episteme, …}) from a System’s classification under local system-role kinds and its obtaining assignments of those kinds (A.2/A.2.1). Only systems can be holders of these assignments, enact methods, and perform Work occurrences admitted under U.Work; epistemes do not act. This work-facing rule does not imply that every actual change has an acting-system side.
  • Local kind, assignment, Method, description, and occurrence stay distinct. A local system-role kind classifies Systems by its criterion; an obtaining assignment of that kind is a separate relation (A.2/A.2.1). U.Method is a run-independent semantic way of doing, U.MethodDescription is an episteme that may describe that Method, and each individual admitted under U.Work is the dated performed occurrence that enacts it.
  • Run-independent semantics vs dated occurrence. A Method and any episteme that describes it are not the occurrence. Add F.6 assignment-bound attribution, affected-referent, binding, or resource-use relations only when they independently obtain and the receiving use relies on them. When actual change is also claimed, identify it independently under A.3.4 and use a separately governed work-to-change relation.
  • Occurrence, assertion, evidence, and carrier. One Work individual is the world-side occurrence. A separate U.Episteme may assert or describe it and designate the exact occurrence and obtaining relations. Logs, observations, evidence items, and publications have their own carriers and direct relations; neither a carrier nor a record becomes Work by referring to it.

A.3:3 - Problem

Shorthand such as “actor,” “process” or “blueprint” can hide these different questions:

  1. Missing acting-side basis: a self-configuration claim depends on a performer or distinct acting and changed positions that its account has not established.
  2. Plan = event: blueprint/algorithm reported as if execution happened.
  3. Capability or Method = Work: having a capability or a Method is taken to establish that Work occurred.
  4. Episteme as doer: documents/models treated as actors.
  5. Occurrence-description confusion: a Method, plan, log, ticket or carrier is treated as the dated Work occurrence, leaving the actual occurrence and the basis required by the receiving claim unresolved.

A.3:4 - Forces

ForceTension
Identity vs behaviourKeep holon identity stable while roles/behaviours change.
Simplicity vs precisionOne process box can hide the distinctions among MethodDescription, Method and Work that a receiving use needs.
Universality vs idiomsAccounts of physical and epistemic Work need the common distinctions while preserving domain terms.
Reusable semantics vs dated occurrenceKeep Method, any MethodDescription edition, and Work distinct; make each relied-on connection explicit.
Evidence vs mereologyProvenance edges (EPV‑DAG) must never turn into part‑whole edges.

A.3:5 - Solution — The Transformer Quartet

For work enactment, A.3 distinguishes four objects: the performer System with its needed assignment basis, a MethodDescription edition when the use relies on one, the enacted Method, and the dated Work. Another independently grounded actor-side claim uses only the participants and relations required by its direct governing pattern. These distinctions qualify that acting-side claim; they are not occurrence conditions for every U.Transformation.

A.3:5.1 - The four anchors (terms & types)

  1. Acting side: for actual Work, use A.13 to recover each performer System and its obtaining assignment, then let A.15.1 admit the dated occurrence independently. If the current use also claims under which assignment the Work was performed, use F.6 performedUnderAssignment(W, RA) with that same assignment and its holder System. For another actor-side claim, its direct owner grounds the participants and decides whether a work-facing role assignment is current.

    Canonical phrase when that assignment is grounded: system assigned to the locally defined TransformerRole@Context kind. Local shorthand: after explicit binding in the same subsection, you MAY write Transformer for that same system; re-bind on context change and do not use the shorthand where the domain already has a conflicting transformer term. The shorthand neither identifies an actual transformation nor upgrades causal participation or broad physical agentivity into Work.

  2. MethodDescription (description episteme, when relied on): an SOP, program, protocol, script, diagram, or other source is a U.MethodDescription only when it meets A.3.2 membership for the exact Method. Its exact edition is cited only when the receiving claim about Work, assurance, gate, audit, or another use depends on that description.

  3. Method (run-independent semantic way of doing): the exact U.Method that Work may enact. It is neither an occurrence nor a MethodDescription, role assignment, or holder capability. Order-sensitive composition belongs to B.1.5 only when that composition claim is current.

  4. Work (world-side dated occurrence holon): U.Work is the admitted kind; one Work individual is admitted under A.15.1 from independently grounded performance history, each performer System’s A.13 basis, actual enactsMethod relations, its temporal extent, and at least one obtaining locally declared Work-to-System relation whose stated boundary contains the complete occurrence. Add F.6 performedUnderAssignment, affected-referent, binding, and resource-use relations only when their own facts obtain and the current use relies on them.

    A U.Episteme may assert or describe those facts and designate the occurrence; a ticket, log row, record, or carrier is not the Work. The occurrence neither requires one universal MethodDescription edition nor establishes an actual change, result, production, delivery, acceptance, or aggregate merely by occurring.

Memory line: A MethodDescription may describe a Method; one dated world-side Work occurrence may enact that Method; a Work assertion may designate that occurrence. The description, occurrence, and assertion are different holons, and none of these relations alone establishes actual change or result. A local system-role kind and an obtaining assignment are distinct (A.2/A.2.1); a Method is a reusable way of doing; a Work individual is the performed behaviour occurrence.

A.3:5.2 - System-role assignment (U.SystemRoleAssignment) for actor-side enactment

When a performed-work claim relies on an assignment, identify its directly declared species under U.SystemRoleAssignment, the participant meanings and predicate that species defines, and the actual participant values that satisfy that predicate. Preserve the holder System, the assigned local system-role kind, and any additional participant, such as a commission or position, required by that species. Use A.2.1 for its declaration and occurrence identity.

  • An assignment assertion or occurrence description may state assignmentInterval for the currently known temporal extent. That description does not make the predicate obtain or add a generic assignment participant.
  • Cite a taxonomy episteme and effective ReferenceScheme when they matter to interpretation. They, a generic U.BoundedContext, and a selected BoundedModelUseStructure are not generic assignment participants. When a receiving claim about Work depends on a selected interpretation structure, designate it through that receiving use’s relation.
  • The same System may hold several assignments to local system-role kinds when their direct compatibility rules admit them; labels or shared context wording do not decide compatibility.
  • When work on an episteme or carrier is claimed, the acting performer remains a System; episteme identity, carrier change, Work, publication, and evidence retain separate governors.
  • An independently grounded A.3.4 occurrence supplies none of the assignment participants or temporal facts by itself.

A.3:5.3 - Boundary & externality

A.3.4 first identifies the actual bounded change from its changed referent and subject-side occurrence facts. Add an asymmetric acting side and target side only when a direct participation, interaction, causality, or work owner independently grounds that factorization. If an exact interaction relation obtains, cite its direct governing pattern; A.3 does not create one from the word “transformation.”

Natural, spontaneous, and formal transformations can therefore remain actual without an invented performer. Joint dynamics, relational change, or a non-separable or frame-dependent participation case also remains under its direct dynamics, relation, interaction, or causality owner until an asymmetric actor–target split is justified. Ordinary coupling and scale-free or minimal physical agentivity alone establish neither TransformerRole@Context, U.Method, nor a dated Work occurrence admitted under U.Work.

For work on oneself, use the A.12 reflexive split only after two distinct internal positions are grounded for the current claim. The acting and changed positions may be subholons inside one containing holon; selecting those already grounded parts is an A.14/C.13 structure move, not a Meta-Holon Transition. Use B.2 only if the whole itself is reidentified.

A.3:5.4 - Align the temporal claims of descriptions, Methods and Work

  • A U.MethodDescription is a separately identified episteme; cite its exact edition only when the receiving use relies on what that edition says, using C.2.1 for any claimed edition relation.
  • A U.Method is run-independent and may be enacted by many dated Work occurrences.
  • One Work individual admitted under U.Work has its own governed temporal extent and performer basis under A.13/A.15.1. Use F.6 with the same obtaining assignment only when precise assignment-bound attribution is claimed; an assertion or description may designate those facts, but is not the occurrence.
  • When a work-to-change claim is current, identify the world-side Work under A.15.1, the actual change under A.3.4, and the exact direct relation between them. A formal ordering boundary or natural change remains under A.3.4 without a work-facing inference.

A.3:5.5 - Evidence Graph Referring

An assertion or description episteme about one Work occurrence makes its performer Systems with their A.13 assignments and enacted Method recoverable. Cite an obtaining F.6 relation for a claimed assignment-bound attribution and a MethodDescription edition only when the receiving use depends on it. Logs, observations, provenance, evidence, and their carriers remain separately related under their direct owners; neither the assertion nor a carrier or output produced by the performer is the Work occurrence or self-certifying evidence for it or its effects.

A.3:5.6 - Didactic dictionary

  • Process, workflow, SOP, algorithm, protocol, script, or recipe is source wording first. Recover whether the current object is a MethodDescription, Method, WorkPlan, dated Work, method-relation structure, or another directly governed object.
  • Operation, job, run, or performance is a Work individual admitted under U.Work only when the A.15.1 occurrence basis is recoverable; a log row, ticket, assertion, description, or label does not make it Work.
  • Function in an equipment specification may describe a Method, a MethodDescription, a capability, an intended effect, or another direct relation; the word alone decides none of them.
  • Creator becomes local shorthand for a Transformer only when an exact actor-side holder has already been bound as a system through the applicable direct relation and, for performed Work, an obtaining U.SystemRoleAssignment; otherwise recover the actual relation or stop.

A.3:6 - Illustrative scenarios (substrate‑neutral)

A.3:6.1 - Physical system — Cooling loop

The world-side occurrence run-2025-08-08-T14:03 is independently admitted under U.Work through A.13/A.15.1 with PumpUnit#3 as performer and an actual enactsMethod relation to CirculateCoolingFluid@CoolingLoop. If the receiving use also needs attribution under the same U.SystemRoleAssignment occurrence, cite its obtaining F.6 performedUnderAssignment relation. Cite centrifugal_pump_curve.ld when this Work claim relies on its content. Treat its claim-bearing episteme as a U.MethodDescription only if A.3.2 establishes that its EntityOfConcern is CirculateCoolingFluid@CoolingLoop and that it makes a substantive claim about that Method as a way of doing. A separately obtaining resource-use relation connects the Work individual to the 3.6 kWh use; the measured ΔT=6 K and any actual fluid change remain separately governed measurement, transformation, and work-to-change claims.

A.3:6.2 - Epistemic change — Proof revision

The world-side occurrence lemma-42-check-2025-08-08 is independently admitted under U.Work through A.13/A.15.1 with LeanServer as performer and an actual enactsMethod relation to CheckAndReviseLeanProof@Lean. If the receiving use also needs attribution under the same U.SystemRoleAssignment occurrence, cite its obtaining F.6 performedUnderAssignment relation. proof_tactic.lean, any exact MethodDescription edition, the theorem episteme, carrier or episteme change, and the check log remain separately governed. An exact evidence-use relation may use the log to support a receiving claim; production by the performer does not itself confer evidence status or support.

A.3:6.3 - Reflexive maintenance — “calibrates itself”

When the calibration controller and sensor suite are independently grounded as distinct internal positions, split into Regulator (acting position) and Regulated (changed position), cite the exact interaction and independently obtaining relations involving any claimed Work occurrence, and cite the evidence-use relation supporting each relied-on claim.

A.3:6.4 - Joint or non-separable physical participation

A tide-related change of seawater can be one independently grounded A.3.4 transformation. Moon–Earth–ocean gravitational coupling, joint dynamics, and causal participation are recovered through their direct relation, dynamics, interaction, and causality owners. Coupling or a minimal physical-agentivity reading alone does not make the Moon a holder of TransformerRole@Context and does not create U.Work. Use C.26 only if a residual probe-, frame-, order-, incompatible-read-, or no-faithful-export lens issue remains.

A.3:6.5 - Reflexive work — scratching oneself

For a work-on-oneself claim, the containing holon is the person, the acting position is the grounded neural-control/right-arm subsystem, and the changed position is the grounded left-hand tissue or state. The exact U.SystemRoleAssignment, applicable method, dated work, work-to-change facts, and A.3.4 occurrence remain separate. Selecting these already grounded subholons uses A.14/C.13; it is not an MHT unless the person as a whole is reidentified under B.2.

A.3:7 - Conformance Checklist (normative)

CC‑A3‑0 - Performer basis and conditional assignment-bound attribution. For actual Work, each performer System MUST have the A.13 core, including classification under a local agential system-role kind and an obtaining assignment of that kind. A.15.1 admits the Work independently. The assignment’s declared U.SystemRoleAssignment species determines its predicate, holder, assigned-kind domain, any additional participants, and occurrence identity under A.2.1. State the currently known extent separately as assignmentInterval when needed; taxonomy, scheme, and context references are not generic participants.

If the receiving use also claims under which assignment the Work was performed, that attribution MUST pass F.6 performedUnderAssignment(W, RA) with the same assignment; an unresolved attribution leaves the admitted Work intact. A conforming assertion or description designates the Work and the basis its claim uses. For a non-Work actor-side claim, use its direct governor and introduce a work-facing assignment only when that relation is independently current.

CC‑A3‑1 - Acting-side distinction. When an asymmetric actor-side claim is current, its directly governed acting and changed positions MUST be distinct for that claim. When performed Work is current, recover each actual performer and its obtaining assignment through A.13; add F.6 attribution through that same assignment only when the receiving use needs it. In reflexive Work the acting and changed positions MAY be grounded subholons or positions inside one containing holon; the containing holon need not be reidentified. Do not force this split or a role assignment onto a natural, joint, relational, non-separable, or formal change merely to satisfy A.3. This preserves acting-side externalization without fictive actors.

CC‑A3‑2 - Method-description-Work-assertion separation. U.MethodDescription is a description episteme, U.Method is a run-independent semantic way of doing, and a Work individual admitted under U.Work is a world-side dated performed occurrence. A Work assertion or description is another U.Episteme; a log, ticket, or carrier may express or support it but is not the occurrence. Neither Method nor MethodDescription is a run-time occurrence. A changed description edition and performed Work are separate facts, and a claim that Work occurred remains admissible without a MethodDescription reference when no receiving use relies on an exact description edition.

CC‑A3‑3 - Boundary-crossing evidence. A conforming actor-side or work-to-change assertion MUST designate the exact direct participation, interaction, flow, causality, or work-to-change facts on which it relies; an A.3.4 occurrence alone supplies none of them. Conservation-class effects, when claimed, MUST satisfy the applicable B-invariants.

CC‑A3‑4 - Method and conditional description traceability. Every Work individual admitted under U.Work stands in an exact actual enactsMethod relation to the U.Method it enacts; the assertion or description used by a receiving claim MUST designate both sides and that relation. Cite an exact U.MethodDescription edition only when the receiving claim depends on that edition to identify, constrain, or justify the Method. If actual enactment departs from a cited description, state the description-selection, override, exception, or deviation claim under its direct owner and apply the Work continuity policy to the actual occurrence facts. Absence of a description reliance claim is not silent drift.

CC‑A3‑5 - Episteme as object-under-change. When Work on an episteme or its carrier is claimed, the performer is a System; episteme identity, carrier continuity, edition succession, publication, and any actual carrier change remain under their direct owners. Do not infer a performer from the episteme change itself. See C.2.1, E.24.PUB, A.14’s mereology firewalls, and direct epistemic aggregation owners when current.

CC‑A3‑6 - Units and measures for performed resource use. Every performed resource-use fact relied on for a claim about Work MUST state its measure and units. A percentage that enters a resource aggregation must be grounded in the exact PortionOf measure needed by that use. Totals, allocation, overlap handling, deduplication, and optional Gamma_work notation belong to a separately recovered B.1.6 aggregation, not to Work identity.

CC‑A3‑7 - Authority, justification, and provenance boundary. Authority, justification and provenance are not generic constitutive fields of a SystemRoleAssignment or Work occurrence. When a receiving use relies on one of them, identify the exact episteme and direct authority, justification, source, evidence or provenance relation and connect it to the assignment occurrence, Work individual, assertion or description. The assignment must obtain under its species predicate; the Work occurrence must meet the A.15.1 admission conditions.

CC‑A3‑8 - Agentic policy, planning, Work, and outcome separation. An agentic case does not license a generic pipeline from policy, through a planned action, to an action. Recover each exact policy, objective, selection or decision, WorkPlan, SystemRoleAssignment, dated Work, actual change, and outcome claim under its direct owner when that claim is current. A policy does not create a plan or Work; a plan does not prove Work; and Work does not prove an outcome.

CC‑A3‑9 - Local interpretation and exact crossings. When interpretation depends on a taxonomy episteme or effective ReferenceScheme, identify that reference in the assertion about the SystemRoleAssignment occurrence. Test compatibility through the exact rule current for that assignment use. Similar labels across localities establish neither equivalence nor conflict. When a receiving use needs exact local-sense correspondence, use F.9 only for the exact SenseCell correspondence and its admitted use; local system-role-kind, policy, criterion, verdict, or other mappings retain their direct owners.

CC‑A3‑10 - Use-driven aggregation boundary. When a receiving use needs order-sensitive Method composition, recover B.1.5 and optional Gamma_method; when it needs a temporal aggregate over exact Work intervals, recover B.1.4 and optional Gamma_time; when it needs a resource ledger, recover B.1.6 and optional Gamma_work. A system-boundary or epistemic aggregation likewise uses its exact direct owner. Each aggregation has its own EntityOfConcern, policy, evidence, and admissible use; none is a universal field or identity condition of MethodDescription, SystemRoleAssignment, or Work.

A.3:8 - Consequences

Benefits

  • Recoverable Work basis. A conforming assertion about performed Work designates the world-side occurrence, each performer System’s A.13 basis, enacted Method, and any obtaining F.6 attribution or neighboring description, capability, work-to-change, evidence, or aggregation claim on which the current use relies; actual-change identity remains separately inspectable under A.3.4.
  • Keep system parts distinct from method and edition claims. A Method, local system-role kind, or description does not become a part of a System by describing its operation; edition succession is also distinct from a part-whole relation. Method-to-Method parts remain governed by A.3.1 and B.1.5.
  • Composable analytics without hidden ownership. Exact Work intervals and performed resource-use facts can feed separately recovered B.1.4 or B.1.6 aggregations; the selected policy, evidence, and result remain inspectable at that direct owner.
  • Local plurality without whole-context bridges. Exact role taxonomies, ReferenceSchemes, compatibility rules, and use-specific mappings let local practices differ without treating a shared label or one bridge as wholesale equivalence.

Trade‑offs

  • More explicit separation when reliance needs it. Start with the smallest grounded performer-assignment, Method, and Work claims; add MethodDescription, capability, policy, plan, change, evidence, and aggregation relations only when a named use depends on them.
  • Discipline for reflexive work. Modellers must ground distinct acting and changed positions before using a controller–plant or other reflexive split; this adds only the relation claims the use needs and avoids an ungrounded performer or arbitrary decomposition.

A.3:9 - Rationale and Source Comparisons

Constructor theory. Constructor theory informs the distinction between possible and impossible tasks and the conditions on substrates and constructors. A.3 adopts that modal discipline without equating a constructor-theory constructor with an FPF performer or TransformerRole holder. In the performed-Work branch, an independently grounded System may be the holder of an exact SystemRoleAssignment, and a Work occurrence performed under that assignment may enact an exact Method; natural, spontaneous, joint, formal, or otherwise non-agentive transformation remains possible without that actor-side factorization. A task description qualifies as a MethodDescription only under A.3.2; it is neither the constructor nor the Work. (Royal Society Publishing, arXiv, Constructor Theory)

Active inference & free‑energy mechanics (2017→). When an agentic claim is current, active-inference and free-energy work motivates keeping policy, objective, observation, selection, planning, performed Work, and evidence distinctions visible under their direct owners. It does not supply a universal action pipeline, make agentivity a Work occurrence, or make one policy, plan, or posterior prove another. (MIT Press Direct, PubMed, arXiv)

Provenance and FAIR packaging (2016→). FAIR, RO-Crate, OpenLineage, and ML Metadata motivate exact, machine-actionable provenance and evidence links when a receiving use relies on lineage, editions, runs, or jobs. A.3 therefore preserves those links as separately governed relations rather than making {authority, justification, provenance} constitutive fields of SystemRoleAssignment or Work. (Nature, researchobject.org, SAGE Journals, openlineage.io, GitHub, arXiv)

The source contributions above inform A.3’s design. Its performer basis comes from A.13, Work admission from A.15.1, Method and MethodDescription distinctions from A.3.1/A.3.2, and conditional assignment-bound attribution from F.6. A.3.4 separately governs actual change, including cases without a performer.

A.3:10 - Relations

A.7 Strict Distinction. A.3 keeps the target EntityOfConcern, MethodDescription, Method, local system-role kind, SystemRoleAssignment occurrence, dated Work occurrence, Work assertion or description, actual change, log or observation, and evidence relation distinct. A recipe or log is not part of the target merely by describing or recording work on it, and a record about Work is not the Work occurrence.

A.12 Acting-Side Externalization and Reflexive Split: Identify Who Acts on What. A.3’s CC-A3-1 uses A.12 only when an actor-side or reflexive-work claim is current. The split keeps grounded acting and changed positions distinct for that claim; it neither invents an actor for non-separable change nor turns ordinary descent to already grounded parts into an MHT.

A.13 Agential Role. When an agency claim is current, A.13 governs agenthood and the domain profile, while A.17, A.18, A.19, C.16, and A.10 govern its measurement and evidence as applicable. A.3 keeps identity, role assignment, method, plan, work, transformation, and evidence separate. Scale-free or minimal physical agentivity, observerhood, self-evidencing, or causal participation does not by itself establish an obtaining U.SystemRoleAssignment, TransformerRole@Context, method enactment, or dated Work.

A.3.4 Actual Bounded Change Under Conditions. A.3.4 independently identifies one actual bounded transformation from the changed referent and subject-side occurrence facts. A.3 opens only when an actor-side enactment claim is additionally grounded. Natural, spontaneous, formal, relational, and joint-dynamics changes therefore need no fictive performer.

A.3.3, direct relation, interaction, and causality owners. These patterns govern claims about participation and causal structure. Use an asymmetric actor-target factorization only when that result is independently grounded; retain a joint or non-separable account otherwise. C.26 may test a residual probe, frame, order, incompatible-read, or no-faithful-export lens issue.

A.15 Role-Method-Work Alignment. A.3 relies on A.15’s separation of local system-role kind, System-classification claim, exact world-side SystemRoleAssignment occurrence, run-independent Method, conditional MethodDescription reliance, intended WorkPlan episteme, world-side dated Work occurrence, and any assertion, description, log, or evidence about that occurrence. The Work stands in an actual enactsMethod relation; use F.6 with the same A.13 assignment only when precise assignment-bound attribution is claimed. A MethodDescription may describe the Method; neither the description, plan, nor record proves that Work or actual change occurred.

A.14 Mereology. A.3 consumes A.14/C.13 only for independently grounded part or structure relations and forbids inferring System-part membership from a local system-role kind or recipe. Selecting grounded internal positions for a reflexive claim is not an MHT; B.2 opens only when the containing whole is reidentified.

B-cluster (Gamma sections). A.3 supplies grounded actor-side facts and exact Work occurrences that receiving assertions may designate. B.1.5 governs order-sensitive Method composition and optional Gamma_method; B.1.4 governs a selected temporal aggregation and optional Gamma_time; B.1.6 governs a selected Work-resource aggregation and optional Gamma_work. System-boundary and epistemic aggregations use their exact direct patterns when current. Every such result has its own EntityOfConcern, policy, evidence, and admissible use rather than becoming a field or identity condition of MethodDescription, SystemRoleAssignment, or Work.

A.3:End

A.3.1 - U.Method: Reusable Way of Doing with Explicit Applicability

Type: Definitional pattern Status: Stable Normativity: Normative

A.3.1:1 - Problem frame

Use this pattern when a project needs to say how something is done in principle.

When observed performances or evidence about performances may show a reusable way that needs recovery, use A.3.1.MR first. It returns one source-traceable provisional account per candidate, a record-only result, or a named blocker. Include a distinguishing question only when it changes recovery or the receiving use.

For reusable-way claims proposed or described in documentary guidance, use A.3.1.DR when their source meaning or status needs recovery. Choose by the source’s role in the question: a document can contain both guidance and performance evidence.

When one candidate reusable way is ready for the U.Method identity test, apply this pattern directly.

Typical moments:

  • a team infers method identity solely from code, a BPMN diagram, or a solver model, or treats a workflow description as evidence of performed Work;
  • a practice, procedure, protocol, proof script, optimization model, control strategy, or recipe is intended for reuse across many runs;
  • two descriptions look different but may describe the same way of doing;
  • a graph, query, table, dashboard, checklist predicate, or mathematical representation is being interpreted as if it were an instruction sequence;

Primary EntityOfConcern. The EntityOfConcern is the U.Method: one reusable semantic way of doing under stated participant meanings, applicability, preconditions, intended effects or preserved conditions, and bounds. Cite an exact effective reference scheme and local senses only when their variation changes that method meaning.

U.Method is a non-agentive holon kind: methods can have submethods, compose into whole methods, and participate as submethods of larger methods. A step label or step description is not a method part unless the recovered object is itself a U.Method.

First useful move. Name the reusable way of doing, its generic participant meanings, applicability, preconditions, intended effect or preserved condition, and the concern it addresses. If local terminology changes that answer, cite the effective reference scheme and local senses.

What goes wrong if missed. Readers may mistake a diagram for work authorization, a query plan for performed work, a program for proof of operational success, or a graph path for a route actually followed.

What this buys. The project can reuse, compare, describe, plan, enact, and audit a way of doing without confusing the method with its descriptions, runs, mechanisms, mathematical substrates, evidence relations, gates, or authority claims.

Not this pattern when. If the sentence is about a document or representation that describes a method, schedules work, reports dated Work, declares a mechanism, presents a mathematical lens, cites evidence, decides a gate, asserts authority, or publishes a view, use the pattern that defines or tests that claim. When method-description membership is in question, apply A.3.2’s same-individual test to the already identified claim-bearing episteme; a carrier or representation is not thereby linked directly to the Method. State any planning, enactment, realization, evidence, gate, authority, publication, or representation relation only under its subject pattern when it obtains.

A.3.1:2 - Problem

When the reusable way of doing remains unclear, method-like wording can hide different claims:

  1. Description as method. A SOP, code repository, proof script, BPMN diagram, SQL query, solver model, or protocol is treated as the method itself.
  2. Plan or run as method. A calendar plan, access plan, run log, telemetry trace, or work-result record is called the method.
  3. Mechanism or formal substrate as method. A mathematical object, formal substrate, mechanism declaration, causal model, or control structure is used as if it already selected the way of doing work.
  4. System-role or capability leakage. Named people, organizations, teams, permissions, system-role assignments, or a particular holder’s capability assessment are baked into the Method instead of remaining with their direct classification, assignment, authority, capability, or gate patterns.
  5. Programming-paradigm overread. Imperative, functional, logical, constraint, object-centric event, or effect-handler wording is taken as a direct ontology of work rather than one possible description or representation of a way of doing.

The practical harm is fragile reliance. Changing a publication looks like changing the method; a run error looks like method invalidation; a mechanism declaration starts authorizing work; and a dashboard cue starts acting like evidence or permission.

A.3.1:3 - Forces

  • A method has enough identity stability to support comparison, reuse, teaching, improvement, and audit across many runs.
  • Work happens in dated situations with exact performer assignments, actual participants, resource uses, conditions, and separately governed effects; a method statement establishes none of those occurrence-side facts.
  • Method descriptions can be executable, formal, graphical, procedural, declarative, or hybrid; publication form alone does not decide the method ontology.
  • Mechanisms and mathematical substrates often make a method explainable or constrained enough to rely on, but the mechanism claim and the method claim answer different project questions.
  • A useful method statement remains applicable to welding, clinical triage, proof construction, optimization, agent orchestration, lab protocols, software execution, and organizational work without making software notation the default model of method.

A.3.1:4 - Solution

A U.Method is a repeatable way of doing work under stated conditions. In ordinary instructions, name the action and the conditions under which the method applies. A description can explain how to do the work before anyone performs it.

It is a non-agentive holon kind. Part methods can be selected, bounded, ordered, joined, adapted, and hidden or exposed through method interfaces to form a whole method with whole-level preconditions, effects, invariants, constraints, and assurance hooks. The whole method may then be used as a part method in a larger method.

A U.Method is:

  • semantically local: its identity uses the declared participant meanings, applicability, conditions, intended effects or preserved conditions, and bounds; add an effective reference scheme and local senses only when a meaning difference would change the method identification or a stated comparison;
  • concern-explicit: it states what a future enactment is intended to do or decide and its intended effect or preserved condition;
  • description-independent: one method may be described by several U.MethodDescription epistemes;
  • run-independent: one method may be enacted by many Work occurrences admitted under U.Work;
  • assignment-independent: Method admission conditions may name local system-role kinds or capability-fit conditions, but named holders and obtaining assignments belong elsewhere;
  • participant-semantic: it may state generic participant meanings and method-side applicability without declaring RelationSignature SlotSpecs, OperationAlgebra argument or result positions, planned fillers, or actual participants.

Do not begin by replacing method or practice with a preferred technical word. First finish the ordinary sentence, “Here the text is trying to name or assert ___.” Then use this table:

If the text is about…Govern it as…
semantic way of doingA.3.1 U.Method
relation or composition among methods, method families, method-description epistemes, or local method expressionsC.2.1 or the exact comparison/direct-relation pattern for an actual relation among description epistemes; A.22 only for a selected structure whose constituent relations already obtain; G.5 and A.19 for family selection; A.15.1 for enactsMethod; B.1.5 for order-sensitive method composition; A.6.3.RT for representation correspondence, with C.29 for mathematical-lens use
description of that way of doing: SOP, program, proof script, solver model, protocol, diagram, process model, recipe textA.3.2 U.MethodDescription
source phrase such as practice, technique, school, tradition, or a local method label whose claim is unclearleave it unresolved until the sentence identifies a reusable way, description, discipline or tradition, or model-use boundary; use A.1.1 for the bounded-context or model-use claim and C.36.P for the cultural-evolution, tradition, style, canon, recognition, selection, or mediation claim
selected formal declaration or mathematical lensA.6.0 for the declaration; C.29 when a stated use applies the mathematical lens
mechanism declaration or realization relationA.6.1 and E.20
system-role assignment, relation among exact system-role kinds, direct responsibility relation, or holder eligibility hidden under a practice or Method phraseA.2, A.2.1, A.2.7, A.6.RCD, and A.15 as applicable
planned dated work or authorization to prepare workA.15.2 U.WorkPlan plus the relevant gate, authority, or commitment pattern
dated work occurrence or run; trace, log, or result recordUse A.15.1 for the dated Work. Route a separate record or result by what it asserts—measurement, evaluation, production, delivery, acceptance, or evidence—and link it to Work only through a relation whose predicate and participants are defined by its direct pattern or declaration.
field, bounded-context or model-use, discipline or tradition, recognition or selection, mediation, variant, or cultural-evolution claimUse A.1.1 for a bounded-context or model-use claim; C.20, C.36, or C.36.P for a discipline, tradition, canon, or cultural-evolution claim; and F.17, F.18, F.9, C.18, C.19, G.5, or G.11 only after the sentence names its sense, recognition, mediation, variant, selection, or currentness claim.
evidence or provenance relation for a claimA.10
graph path, query, table, dashboard, publication face, or pattern relation made to prescribe action by its layoutapply C.2.P.DR, then state the method, Work, gate, or authority claim—or stop when none is present

A.3.1:4.0a - Strategy wording by claim position

Treat strategy as ordinary source wording until the sentence’s claim position is clear. Do not mint U.Strategy.

When the wording names a reusable way of deciding or acting under stated applicability, it identifies a U.Method. A clinical treatment strategy, manufacturing setup strategy, search strategy, or negotiation strategy qualifies only when it states the reusable action, participant meanings, preconditions, intended result, and bounds.

When a protocol, playbook, program, diagram, or prose passage describes that way, that episteme may be a U.MethodDescription. Reusable strategizing can itself be a U.Method; a dated strategy workshop, search episode, or planning session is a Work individual only when its A.15.1 occurrence basis is grounded.

When the sentence is about choosing among candidates, use A.19.SelectorMechanism and G.5 for the actual criteria, policy, and selector outcome. The label strategy does not replace those objects or prove that a reusable method has been stated.

Leave quoted or explanatory strategy wording alone when it carries no FPF claim. The repair is complete when a reader can say what the sentence asserts and which pattern contains the defining content for that assertion, not when every occurrence has been replaced.

A.3.1:4.1 - Thin first-use method identification

Start with the least apparatus that lets another reader recognize the same method:

  1. Ordinary use. State the reusable way of doing, the kinds of participants it is for, when it applies, what it is meant to achieve or preserve, and any applicable use limits or stop conditions. If that sentence is enough for the decision at hand, stop.
  2. Later comparison or reliance. Use the needed entries in the Plain aid below when the ordinary statement is insufficient to distinguish same-named methods, compare descriptions or variants, cite one edition in a plan, or audit why this method was selected.
  3. Organization of several methods or uses. Open A.22, B.1.5, or another direct composition pattern only when the question is about the organization itself—for example, which methods were composed, selected, used as fallbacks, or enacted in the reviewed work.

The following Plain identification aid is optional and is not a data schema. Omit every entry that the stated decision does not use.

Method identification aid:
  MethodRef:
  SemanticBasisIfMeaningVaries:
  Applicability:
  GenericParticipantMeanings:
  MethodConcern:
  Preconditions:
  IntendedResultOrPreservedCondition:
  MethodDescriptionIfReliedOn:
  WorkRelationIfReliedOn:
  SelectedStructureOrModelUseIfReliedOn:
  RelationsThatMustObtain:
  RelianceWindow:
  ReviewIf:

Add SemanticBasisIfMeaningVaries only when the same words have different meanings under another effective reference scheme or set of local senses. Add a claim scope, context slice, selected structure, or model-use relation only when its identity and conditions are established under the applicable pattern and changing it would change the method identification or the later decision. Assert a relation only when its predicate obtains.

For every relied-on relation, name its participants, the relation that must obtain, and the pattern that defines or constrains it. A generic source, support, evidence, or current use entry does not identify that relation. For the named receiving use, state the relevant temporal conditions in RelianceWindow and the concrete change that requires reconsidering that use in ReviewIf. For a comparison, identify the Method variants being compared and the description editions relied on separately.

A.3.1:4.1a - Closure and bounded non-use

Close positively when a reader can write the reusable action, generic participant meanings, applicability, preconditions, intended result or preserved condition, and any use limit or stop condition that changes the identification or decision. Resolve an effective reference scheme and local senses only when a meaning difference changes that answer. Cite a method description, selected structure, model-use relation, or Work relation only when the next decision depends on it.

If the project also claims an actual change, use A.3.4 separately for the actual changed referent, temporal boundary, subject facts, and transformation identity.

Close by non-use when the source is only a description, plan, dated Work occurrence, mechanism declaration, selector result, system-role-kind relation, another direct relation, evidence relation, publication use, or quoted wording. If the material does not distinguish those positions, retain the source phrase as an unresolved cue and stop rather than inferring U.Method.

A.3.1:4.2 - Method and mechanism settlement

Do not decide from words such as method, algorithm, process, or mechanism. First ask what the sentence lets the project assert:

Plain questionAnswer and pattern to use
What reusable way of observing, deciding, deriving, changing, or preserving is meant?State the U.Method under A.3.1: participants, applicability, conditions, intended result or preserved condition, and boundary.
What reusable family of operations and laws is declared?State the separate U.Mechanism declaration under A.6.1: its concern, subject and range meanings, operation algebra, laws, admissibility conditions, and Applicability.
What happened on this dated occasion?Recover every exact actual performer and its obtaining system-role assignment through A.13, then identify the dated Work occurrence independently under A.15.1. Its enacted Method, extent, containing System, bindings, and resources are occurrence-side facts. Add F.6 attribution through that same assignment only when the receiving claim expressly consumes precise assignment-bound attribution; missing or failed F.6 attribution does not erase the independently admitted Work.
What correspondence, realization, or support claim is being made around those objects?Name the relation, its participants, predicate, current facts, and subject-pattern locator. If no such predicate is defined, keep the objects separate and stop rather than implying the relation.

A method statement may cite a mechanism episteme whose content declares operations used by that method. A shared concern or operation name does not make the two values identical. A selector may choose a method, and an A.6.1 application may bind a method as an actual value. State that use only when the selector outcome, application binding, or another admitted direct relation is present; otherwise keep the method and neighboring object separate.

Keep these relation families distinct. An F.9 Bridge between two exact F.17 SchemeSenseCell values states a cross-context sense correspondence; it does not change an effective reference scheme or establish identity. A claim that this Bridge suits one named use remains a separate C.2.1 bounded-use claim. A.10 governs bounded reliance on that claim; use B.3 only for a named assurance claim.

An A.6.1 realization relation connects a mechanism declaration to a realizer; it is not the mechanism content. C.29 governs a mathematical preservation or representation claim. E.20 governs where mechanism meaning is maintained. Evaluation, measurement, and evidence-use patterns support their own claims; they do not add content to the method or mechanism.

When neither the reusable way nor the reusable operation declaration can be stated, keep the source wording unresolved. Replacing it with a more technical noun is not a repair.

A.3.1:4.3 - Method, MethodDescription, WorkPlan, Work

Keep the four positions separate.

PositionWhat it meansCommon mistaken substitutes
U.Methodhow in principle, for stated participants, applicability, conditions, effects, and boundscode, SOP, graph, solver model, proof script, workflow diagram
U.MethodDescriptionan episteme that describes a method in a representationmethod semantics, actual run, authority to work
U.WorkPlanplanned dated work or work preparationtimeless method, generic recipe, proof that work happened
U.Workadmitted kind for dated Work occurrences; one Work individual is one world-side occurrencemethod, plan, result interpretation, evidence relation, or record about the occurrence

The same solver model, repository, protocol, diagram, or run packet may figure in several claims, so say what each sentence is about. The solver-model episteme may describe a method; its mathematical representation may expose a formal substrate; a dated solver run may be Work; and a measurement or evaluation result may support another claim through its evidence relation.

A.3.1:4.4 - Method statement fields

A useful U.Method statement can usually answer these questions in ordinary project language:

FieldWhat to name
Method namethe reusable semantic way of doing
Semantic basis when neededthe effective reference scheme and local senses whose variation would change the method meaning
Applicabilitythe candidate family, conditions, limits, and qualification window under which the way of doing applies
Method concernwhat future enactments are intended to do or decide; this is reusable semantic content, not an actual occurrence
Preconditionsstates already in effect for the method to be applicable
Effects or postconditionswhat successful enactment is meant to produce or preserve
Generic participant and boundary meaningsthe kinds of entities, resources, conditions, interfaces, and Method-side local system-role-kind or capability-fit conditions that a future enactment may involve, without declaring RelationSignature SlotSpecs, OperationAlgebra positions, planned fillers, or actual participants
Capability acceptance conditionsMethod-side thresholds or envelopes required for use; state the actual holder capability and its assessment separately under A.2.2. A changed requirement that matters to Method identity follows §4.7.
Failure and stop conditionswhen the method cannot be used or an enactment must stop; assess the accuracy of a description or entry of planned Work separately under its applicable rule
Method-description membershipwhich epistemes, if any, meet A.3.2 membership for this exact Method; any comparison or plan must separately name the edition and claims it uses
Work relationWhen the receiving use relies on actual enactment, name the admitted Work and obtaining enactsMethod relation in its separate assertion or record; cite a MethodDescription only when that use relies on its claims.

This table is a recognition checklist, not a data schema. Start with the ordinary method sentence. Use A.6.1 for a reusable operation declaration, A.6.5 for a reusable direct-relation declaration, A.15.2 for planned use, and the direct relation or A.6.1 application binding for actual participation.

A.3.1:4.5 - Representation and programming-paradigm discipline

A U.Method need not be written as an imperative sequence. A way of doing may be described or represented through code, rules, constraints, process diagrams, SQL queries, proof scripts, optimization models, or functional or effect-handler programs.

Choose by the claim being made:

  • If the sentence states the reusable action, participants, applicability, intended result, and boundary, use A.3.1.
  • If it points to code, prose, a protocol, diagram, solver model, or other episteme that describes the method, use A.3.2. Use A.6.0 or C.29 when the claim is instead about a formal declaration or mathematical representation.
  • If it declares a law-governed operation family or asks where that declaration is maintained, use A.6.1 or E.20.
  • If it schedules future work or reports a dated occurrence, use A.15.2 or A.15.1.
  • If it claims evidence, provenance or support, use the direct pattern for that claim or relation. Add an A.10 source-to-use account when source recovery, provenance, currentness or bounded reliance must remain replayable. If a representation’s form or layout is being treated as sufficient to prescribe or authorize action, apply C.2.P.DR before choosing the pattern for that claim.

Use §4.2 for cross-context correspondence, bounded-use, assurance, and mechanism-realization claims. C.2.1 governs changes of episteme edition or effective interpretation rules. Use A.6.3 for viewing an episteme, A.6.3.RT for a representation transition, A.6.4 for retargeting, and A.1.1 for a model-use relation. A.6.1 governs an application binding. State one of these relations only when its participants and predicate are present; otherwise retain the source objects without asserting the relation.

Thus algorithm and practice remain source cues. “The SQL query is the method” fails unless the project can state the reusable way of querying, its admissible inputs, intended result, and stop independently of that query text. “Our review practice is the method” fails when the sentence is about a team assignment, dated review, discipline, tradition, evidence record, or publication.

A.3.1:4.6 - Constructor and process-theory settlement

When a method concerns change, its statement says what change a future enactment is meant to achieve; it does not assert that any referent changed. The same identification rule applies to other concerns, such as observation or proof.

The constructor-theory and process-theory source line supports this separation but does not supply a universal method ontology. FPF uses it as follows:

  • An exact actual performer first has the A.13 core; A.15.1 then independently identifies the dated Work, at least one obtaining enactsMethod relation, time, and at least one obtaining locally declared containing-system relation. Another enactment relation is named only when the receiving claim relies on it.

    F.6 enters only when that claim also consumes precise 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 System’s classification and the obtaining assignment remain separate claims.

  • The U.Method is the reusable way under stated participant meanings, applicability, conditions, intended result or preserved condition, and bounds. A U.MethodDescription is an episteme that describes it.

  • A formal substrate or mathematical lens can make the method analyzable, and a U.Mechanism can declare the relevant operation family and laws.

  • A cross-context Bridge, changed reference or model-use relation, mechanism realization, evaluation, or evidence-use claim remains a separately stated relation with its own participants.

  • A U.WorkPlan prepares or schedules dated Work; a Work individual is the occurrence that happened.

For example, “the etch method changed Wafer-22” contains at least two claims. A.3.1 identifies the reusable etch method. Only if an actual bounded change of Wafer-22 is independently grounded does A.3.4 identify that transformation; any claim connecting the Work and transformation additionally needs its own predicate or a missing-governor result.

Apply the same distinction across physical, informational, organizational, and mathematical work.

A.3.1:4.7 - Semantic identity and variants

Two U.MethodDescription epistemes describe the same U.Method when their EntityOfConcern references resolve to the same A.3.1 identity. For the proposed comparison or reuse, compare their claims about the following method bases separately:

  • effective reference scheme and local senses, when a meaning difference matters;
  • generic participant meanings and declared applicability;
  • compatible preconditions;
  • compatible intended effects or preserved conditions;
  • compatible safety and other non-functional bounds;
  • accepted nondeterminism or search behavior; and
  • the same work-facing acceptance relation, when that relation is part of the comparison.

Different control flow, proof notation, programming paradigm, diagram notation, or prose does not by itself make a different method. The converse also holds: the same name, repository, supplier label, or diagram family does not prove identity.

Keep one method across parameter ranges, equipment envelopes, or representation variants only when its declared applicability and the bases used by the comparison admit that variation. A change to an intended result, participant meaning, safety bound, semantic basis, or acceptance criterion that matters to identity requires reconsidering the Method identification under §§4.7–4.8 before asserting refinement, substitution, or a distinct Method.

A discipline may teach a family of methods or one method with variable inputs. To choose for a particular job, identify the required effect, conditions that exclude a candidate, and preferences that distinguish the remaining candidates. State which member you selected and why, or keep the admissible candidates when that is all the receiving decision needs. Binding a value already admitted by the selected way selects a setting of that method. If a required operation changes, compare its meaning and applicability with the original and examine the proposed variant under A.3.1.MV where appropriate. Assigning a date, resources and a performer makes a plan for the job. Its performance is Work. G.5 supplies a grouping or selector when the repertoire needs one. C.11 supports the local choice.

Same-name methods. An emergency-department Triage method applies to patient presentations awaiting clinical assessment; a clinician enacting it uses clinical signs to assign urgency, escalates unsafe cases, and stops when the evidence cannot support that assignment. A software-defect Triage method applies to defect reports awaiting product handling; a product team enacting it uses reproduction evidence, severity, and ownership to choose routing and release impact, and stops when the report cannot support that choice. The shared label identifies neither method. Their participants, applicability, local senses, intended results, and stops distinguish them without a generic context object.

A method without an extra locality object. EuclideanGCD over positive integers closes as one method when the integer meanings, division-with-remainder rule, positivity precondition, decreasing-remainder invariant, and greatest-common-divisor result are stated. If those facts answer the comparison, add no claim scope, context slice, model-use structure, or other locality object.

A.3.1:4.8 - Method relations, composition, and Work enactment

Start with the practical question, not a graph or the umbrella word specialization. Ask what must be decided now.

Current questionFirst useful result
Does this reusable way meet one or more Method-kind criteria?Use C.3.2 for the admissibility check and a true, false, or unknown judgment. An out-of-scope request is not-applicable and forms no judgment.
Does one Method kind have several broader kinds?Check each broader-kind claim under C.3.1.
Does one Method contribute to several larger Methods?Use B.1.5 for every part–whole pair and every whole construction. Each whole keeps its own action, boundary, interfaces, and reidentification rule.
Is one model of a Method a refinement or an abstraction of another?Use B.5.MR to compare their assertions and admitted answers for a stated inquiry and interpretation. The models may concern the same Method; §4.7 separately governs Method identification.
Are two Methods being compared for refinement or replacement?First identify both Methods and the use that needs the comparison. State the direction, what remains, what changes, and the material guards or losses. A sentence or local claim is often enough for one use.
Is this another question—for example, parameter variation, family grouping, fallback, dispatch, a description, a selected structure, performed Work, capability, provider contribution, or cultural change?Use the pattern that defines or tests that claim. The label alone establishes no Method kind, Method part, or relation occurrence.

Before claiming refinement or replacement between Methods, decide whether the changed account identifies the same Method. If it does, state what was preserved and what changed; do not invent a relation between two Methods. If two Methods are identified, a refinement comparison states its direction and use, the semantics retained from the first Method, what the second narrows or strengthens, and the action or result that changes.

A replacement comparison says which Method may replace which other Method, for what use, under which preconditions, with which intended result or preserved condition, and which bounds, interfaces, losses, and guards must remain visible. Do not infer the reverse direction. Shared kind criteria or similar descriptions do not prove replacement.

When the replacement question concerns a constituent used by one or several encompassing Methods, B.1.5.RS supplies the comparison: follow the candidate through each relevant use and retain any adaptation or narrower applicability. For the distinct question of which Methods are being enacted together through a current action, use B.1.5.EW.

A parameter change inside the Method’s declared applicability and identity rule is variation of the same Method. A change to a participant meaning, result, bound, interface, or acceptance condition that matters to identity identifies another Method or leaves the identity question unresolved.

A G.5 family row cites already identified Methods and states why they are grouped for the current use. A fallback can belong to a B.1.5 whole construction, a G.5 selector rule or result, or a local relation-bearing claim. A dispatch rule says which selector branch applies; state the current branch and its basis.

When FPF has no admitted predicate for refinement, replacement, fallback, or another relation-bearing claim, use A.6.RCD to choose the lightest sufficient result. For one use, a local claim may be enough; repeated use of the same rule may justify a reusable predicate definition. Continue through E.24 and E.24.UK only when a named later use must treat the relation occurrences themselves as stable objects. A local claim or predicate definition cannot become an A.22 edge.

Short positive. ChangeImpactReview can meet two Method-kind criteria and also be required by the independent constructions of ApproveControlSoftwareRelease and InvestigateFieldIncident. Those judgments and two methodPartOf facts remain separate.

Selector anti-case. A RapidRecoveryMethods row groups RollbackRelease, DisableFeatureFlag, and ShiftTraffic for one selector. Its stated grouping basis and fallback policy may support a G.5 result, but they do not establish a Method kind, one composite Method, or a refinement or replacement relation. If the fallback condition is incomplete, return the missing fact instead of drawing an edge.

MethodRelationStructure is a local name for an A.22 structure selected from independently identified constituents and relations that already obtain. It is not a durable kind, Method holon, or relation type. Composition, refinement, replacement, parameter variation, family grouping, fallback, dispatch, and enactment are recognition cues; the cue does not decide the claim.

Filled A.22 basis — enacted-method review. For this one-off review, a practitioner selects only two A.15.1 enactsMethod occurrences.

  • Independently identified constituents. InspectPumpSeal@PumpMaintenance-2026 and ClassifyPumpSealCondition@PumpMaintenance-2026 are two U.Method values. Pump37SealInspectionWork-2026-07-25T0900-0908 and Pump37SealClassificationWork-2026-07-25T0910-0916 are two admitted A.15.1 Work occurrences.

    PumpDiagnosticAssignment is a declared U.SystemRoleAssignment species. Under A.2.1 it defines the holder and assigned-kind participant meanings and uses PumpDiagnosticSystemRoleKindDomain as the local assigned-kind domain. Occurrence Pump37DiagnosticAssignment-2026-07-25 has PumpDiagnosticService-A : U.System as holder, PumpDiagnosticSystemRole as the assigned-kind value admitted by that domain, and an extent covering both Work occurrences. That System performs each Work under the assignment and within Pump37MaintenanceCell-A.

  • Selected obtaining relations. enactsMethod(Pump37SealInspectionWork-2026-07-25T0900-0908, InspectPumpSeal@PumpMaintenance-2026) and enactsMethod(Pump37SealClassificationWork-2026-07-25T0910-0916, ClassifyPumpSealCondition@PumpMaintenance-2026) obtain under A.15.1.

  • Applied constraint claims. DiagnosticReviewWindowConstraint states that an eligible enactsMethod occurrence must have one of the two independently admitted Work individuals as its Work participant, and that Work’s temporal extent must lie within 09:00-09:20 on 2026-07-25. NoCompositionFromEnactmentOrderConstraint states that their timestamps and order establish no serial, fallback, or whole-method relation.

  • Selection-use frame. DiagnosticMethodEnactmentFrame states the question: which methods did these two Work occurrences enact during the review window? The admissible action is to list the two enactsMethod occurrences in that review.

Those four discriminators identify DiagnosticMethodEnactmentStructure-2026-07-25-0900-0920, locally designated MethodRelationStructure for this use. Reidentify it only from its four constituents, two obtaining relations, two applied constraint claims, and use frame. A persisted description of the selection is a separate episteme under C.2.1.

If the claim also depends on the dated selection Work, recover its performer basis under A.13 and independently admit the Work under A.15.1, with F.6 only for precise assignment-bound attribution; name the selection Method and any participation relation or A.6.1 binding used by that claim. Add a C.11 choice claim only if one is asserted. If responsibility for that choice is also claimed, cite its direct domain predicate, actual participants, applicability, and occurrence identity or return the missing governor.

Missing-governor stop. Suppose a note additionally calls ClassifyPumpSealCondition@PumpMaintenance-2026 a fallback for InspectPumpSeal@PumpMaintenance-2026, but supplies no direct fallback predicate, compatible participant meanings, or occurrence-identity rule. Keep the two methods and the note, omit the fallback relation, and return missing-governor: fallback relation for <ClassifyPumpSealCondition@PumpMaintenance-2026, InspectPumpSeal@PumpMaintenance-2026>. If the question is specifically about fallback organization, do not select a positive structure until that relation and all four A.22 discriminators are available.

Method-holon composition is not A.14 component mereology. Source labels such as SerialStepOf or ParallelFactorOf remain cues until B.1.5 or another subject pattern supplies an admitted relation with participants and an obtaining rule. A method-description node is not a submethod unless the described object is independently identified as a U.Method.

Work composition is occurrence-side. Work may interleave, split, retry, or fail differently from the method description. A temporal Work part can enact the same whole method, and an episode can change Work continuity without changing method identity. Call a candidate a submethod only when it has its own reusable action, preconditions, intended result or preserved condition, boundary, and whole-method relation.

Quick distinction. A step label, graph node, detector component, event-log segment, telemetry interval, work-plan item, or document section is not a submethod by position. If it states a reusable way with method-level conditions and a relation to the whole method, test it under A.3.1 and B.1.5. If it states what happened, when it happened, what a component did, or what a record shows, use the direct Work, mechanism, evidence, or description pattern instead.

Mathematical or graphical notation may represent claims about the selected structure or an identified Method. A.6.3.RT governs the representation correspondence; C.29 additionally governs any mathematical lens. Apply A.3.2 when classifying the claim-bearing episteme as a method description. A registry row lists or describes candidates; state any relation among them separately under its defining pattern.

A.3.1:5 - Archetypal Grounding

Across the slices below, recognize a U.Method by a stable project answer to this question:

For these kinds of participants and conditions, what reusable way should a future enactment follow, what result or preserved condition is intended, and when should it stop?

Comparison method. DuplicateDefectReportComparison applies to two defect reports for the same product and release when both contain the required symptom and version data. An evaluator enacting it compares those fields and records same incident, different incidents, or insufficient information; missing version data is a stop. These facts identify the reusable comparison method.

Actual-transformation branch. The Etch_Al2O3 case in 5.1 closes the reusable method without actual-change facts. If a later assertion says that Wafer-22 changed during Work W-143, identify the Work under A.15.1 and the actual transformation of Wafer-22 under A.3.4 separately; connect them only through a declared predicate or return missing-governor[work-to-change].

Manufacturing, optimization, proof, graph or query overread, and clinical triage differ in material, representation, and assurance needs, but they share the same method-identification question. The archetypal failure is also shared: a nearby description, plan, run, mechanism, formalism, or evidence relation takes the method name and silently changes what the project can rely on.

A.3.1:5.1 - Manufacturing recipe

Situation. A fab process engineer must decide whether two current SOP editions describe the same alumina-etch method before either description is cited in a work plan. The engineer needs a reusable method identification.

Reusable way and applicability. Etch_Al2O3 applies to alumina-coated silicon wafers whose substrate class and coating range satisfy RecipeWindow-Al2O3-3, using a qualified PE-4 plasma-etcher family and the gas-mixture range declared by that window. Its generic participants are the wafer surface, qualified etcher, admitted gas mixture, and target-depth parameter. A future enactment holds the admitted pressure and temperature envelopes, adjusts exposure until the declared target-depth stop, and preserves the substrate and maximum-temperature conditions.

Preconditions and stop. The method is applicable only when the wafer material and coating range are known, the selected PE-4 calibration is current for the planned use, the admitted gas mixture is available, and the safety interlocks required by RecipeWindow-Al2O3-3 are part of the intended setup. If the recipe fails to state the material/coating range, calibration requirement, gas mixture, target-depth stop, or preservation limits needed to identify the way, keep alumina etch as a method cue until that meaning is recovered. If a particular wafer or setup fails the stated range or calibration requirement, retain the identified Method and stop that planned use under its applicable admission or gate rule.

Visible identification result. Under effective FabProcessScheme-2026, where Al2O3, target depth, and substrate preservation have the local senses used above, the engineer can write:

MethodRef: Etch_Al2O3
SemanticBasisIfMeaningVaries: FabProcessScheme-2026 (`Al2O3`, `target depth`, and `substrate preservation`)
Applicability: alumina-coated silicon wafer; RecipeWindow-Al2O3-3; qualified PE-4 family
GenericParticipantMeanings: wafer surface; qualified etcher; admitted gas mixture; target-depth parameter
MethodConcern: remove the admitted alumina layer to the declared target-depth stop
Preconditions: material and coating range known; calibration current; gas and safety setup available
IntendedResultOrPreservedCondition: target depth reached; substrate and maximum-temperature bounds preserved

This result lets the engineer compare the two SOP claim sets against one method identity and lets a later work plan cite that method and the selected description edition. The SOP, PLC program, calibration recipe, and supplier note remain U.MethodDescription candidates when A.3.2 identifies what each episteme describes (EntityOfConcern) and the substantive claims it carries. For later work authorization or claims that Work W-143 occurred or Wafer-22 changed or passed metrology, use the relevant A.15.2, A.15.1, A.3.4, measurement, evidence, assurance, or gate pattern.

A.3.1:5.2 - Optimization model

Situation and reusable way. JS_Schedule_v4 applies when the jobs, eligible machines, durations, precedence constraints, feasibility rules, and optimization objective are all stated for the scheduling problem. A planner or solver system enacting it constructs candidate assignments under the declared search and stopping rules, rejects infeasible candidates, and compares the remainder by the declared objective. It records the selected schedule, no feasible schedule when infeasibility is established, or no feasible schedule found within the stated search bounds. Missing precedence data, an unstated objective, or incompatible machine eligibility is a stop rather than permission to guess a method variant.

This identification lets a planner compare two solver packages as descriptions of the same scheduling method. The MILP formulation and solver configuration are U.MethodDescription or formal-substrate candidates according to the claim. The selected production schedule is a U.WorkPlan; the dated solver run is Work; and its decision record is a separate result episteme.

A.3.1:5.3 - Proof or derivation

Gauss_Elimination applies to a matrix and right-hand side over a declared algebraic domain in which the required row operations and pivots are valid. A mathematician or proof system enacting it applies equivalence-preserving row operations until solved or echelon form is reached. If the declared variant requires a pivot or division that is not admissible, follow its stated alternative or stop that step. An unspecified domain leaves the method identification incomplete. The visible result here is a method identification that a later derivation may enact.

Recover the claim-bearing episteme expressed by a textbook explanation, proof-assistant script, or formal rule set; apply A.3.2’s membership test for Gauss_Elimination. A concrete proof-assistant run is Work, and the algebraic structure may be a formal substrate. Using the resulting proof for a project decision additionally needs an evidence or assurance relation.

A.3.1:5.4 - Graph or query overread

A graph path, SQL query, checklist predicate, or dashboard table may itself be the current direct object or may represent a relation, state, evidence structure, provenance structure, or publication face. It supports a method identification only when the project can state the reusable action, admissible inputs, intended result, and any branch or stop condition that changes that identification. A query text that returns rows is a description or executable representation until that semantic way is stated.

Ordinary wording such as a graph “routes” or a query “calls” is usable when the operation and its participants are recoverable. Apply C.2.P.DR when a representation’s form or layout is treated as sufficient to establish method order, dated Work, gate passage, or authority.

A.3.1:5.5 - Clinical triage protocol

SepsisTriage_v3 applies to adult emergency-department presentations inside its declared population and assessment window. A clinician enacting it evaluates the stated signs and measurements, assigns an urgency class, and selects the next clinical response. Insufficient evidence, a patient outside the admitted population, or a presentation requiring another protocol is a stop. The visible result here is the reusable triage method and its boundary.

Recover the claim-bearing episteme expressed by the protocol PDF, order-set screen, or decision-support rule and apply A.3.2’s membership test for SepsisTriage_v3. Keep its carrier and publication form separate. A clinician’s dated assessment is Work. The physiological model or score formula may be a formal substrate or mathematical lens. Admission policy, treatment release, and evidence that triage reduced harm remain neighboring claims under their own patterns.

A.3.1:6 - Bias-Annotation

The following biases obscure method identity:

  • description-as-method bias: a document or representation is treated as the reusable way it describes;
  • practice-as-method bias: a source says “practice” and the repair silently chooses U.Method without checking whether the current claim is Work, system-role assignment, discipline, cultural-evolution, evidence, source label, or Method relation structure;
  • run-as-method bias: a trace, log, run, or result record is treated as the reusable way of doing;
  • software-notation bias: code, algorithm, workflow, or programming-paradigm language becomes the default ontology for every method;
  • mechanism-overread bias: law-governed mechanism or formal-substrate material is treated as if it already selected the project method;
  • holder-as-method bias: a team, system, supplier, or capability holder becomes the method name;
  • semio-bias: the discussion shifts to wording, a document, publication, or evidence face before the reusable action and its boundary have been stated.

Use one concrete test in every case: can the reader state the reusable action, its participants, applicability, intended result, and stop? If yes, identify the U.Method; apply A.3.2 when a method-description membership claim is needed and A.15.2 when planned Work is being described; and state only those enactment, evidence, or other relations that obtain. If not, keep the source phrase unresolved or use the subject pattern shown in §4.

A.3.1:7 - Conformance Checklist

CC-A3.1-1 (Method identity). U.Method is one reusable way of doing under a stated concern, participant meanings, applicability, preconditions, intended result or preserved condition, and bounds. If the sentence also makes a claim about an actual participant, A.3.4 transformation, description, plan, dated Work occurrence, evidence relation, system-role assignment, capability, mechanism declaration, formal declaration, publication face, or pattern relation, write that claim under its direct pattern and state only the relation to the Method that obtains.

CC-A3.1-2 (Semantic locality). State the applicability, participant meanings, conditions, intended result, and bounds that distinguish the method. Add an effective reference scheme and local senses only when different meanings would change the identification. Add a claim scope, context slice, selected structure, or model-use relation only when its identity and conditions are established under its applicable pattern, any asserted relation obtains, and changing that object would change the identification or the stated later decision.

CC-A3.1-3 (Method-description membership and use). When work, assurance, gate, or audit reliance depends on a method description, name the exact episteme and verify that it meets A.3.2 membership for this Method. If several epistemes are treated as descriptions of the same Method, their EntityOfConcern references must resolve to the same A.3.1 identity; compare their claim sets separately for the proposed use.

CC-A3.1-4 (Assignment-free Method). A Method may state local system-role-kind admission conditions or capability-fit conditions. These are Method-side admissibility conditions, not deontic obligations by default. The Method does not bind named people, teams, organizations, or calendar allocations.

CC-A3.1-5 (Runtime-free method). A dated run is a Work individual under U.Work, not a method field. Recover each exact actual performer and its obtaining system-role assignment through A.13; A.15.1 independently grounds the Work, enacted Method, extent, containing System, and every participation or resource relation used by the claim. Add F.6 attribution through that same assignment only when the receiving use expressly represents precise assignment-bound attribution. Telemetry, logs, measurements, evaluations, production, delivery, acceptance, and result records remain separate claims.

CC-A3.1-6 (Plan-free method). Work preparation, schedule, go or no-go date, work authorization, and planned work relation belong to U.WorkPlan, gate, authority, or commitment patterns.

CC-A3.1-7 (Mechanism and formal-substrate separation). A formal substrate, mathematical lens, mechanism declaration, realizer, or control model can constrain or help explain a method only through a relation with stated participants. Use E.10.ARCH:3.1 to classify that neighboring claim. It does not identify the method until the reusable action, applicability, intended result, and boundary are stated.

CC-A3.1-8 (Programming-paradigm neutrality). Imperative, functional, logical, constraint, object-centric event, effect-handler, and hybrid forms remain descriptions or representations until the reusable way and its boundary are stated.

CC-A3.1-9 (Graph and representation guard). A graph path, path slice, query, predicate, table, dashboard, publication face, or pattern relation is not a method or work sequence by layout. Use C.2.P.DR when representation wording is overread as imperative action.

CC-A3.1-10 (Method parts, structures, and Work parts). Call a candidate a submethod only when its reusable action, preconditions, intended result or preserved condition, boundary, and relation to the whole method are stated. Otherwise keep the step, graph node, description fragment, Work part, episode, component behavior, or telemetry slice under its own pattern. A selected method-side U.Structure must have all four A.22 discriminators; layout and list membership establish none of them. Use A.6.3.RT for representation correspondence and C.29 additionally for a mathematical lens.

CC-A3.1-11 (Practice wording recovery). For a source word such as practice, ask what the sentence lets the reader do: reuse a way, inspect a description, schedule or report Work, allocate a holder, classify a discipline or tradition, cite evidence, or merely quote a label. Choose the corresponding subject pattern only when that action is stated; otherwise retain an unresolved source cue.

CC-A3.1-12 (Parameter and variant discipline). Parameters may be method semantics or content of a U.MethodDescription. A U.WorkPlan may name planned values only against the declaration that gives those values their meaning. An actual value or participant requires an obtaining direct subject relation or A.6.1 application binding. Effects, bounds, participant meanings, applicability, and any semantic basis used by the comparison determine variant identity.

CC-A3.1-13 (Evidence and assurance boundary). A method or method description does not by itself prove that work happened, that a result is warranted for the claimed use, that a gate is passed, or that action is authorized. Those claims use the relevant evidence, assurance, gate, temporal, authority, work-plan, or work patterns.

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

Anti-patternRepair
Treating executable text as sufficient Method identity.If the claim concerns the reusable way, name its participant meanings, applicability, effects, and bounds under A.3.1. When a method-description membership claim is needed, recover the claim-bearing episteme expressed by the executable text and apply A.3.2’s membership test.
Treating a workflow diagram as the dated Work occurrence.For a claim about planned work, use A.15.2; for a claimed dated occurrence, use A.15.1 and its occurrence basis. Route the diagram by what it describes; apply A.3.2 when a method-description membership claim is needed.
Inferring prescribed action from graph layout.Use the pattern that defines the represented structure, such as E.18 for a transformation flow, and C.29 for a mathematical representation claim. Apply C.2.P.DR when layout is being made to prescribe action. State any gate passage or authority claim separately under its own rule.
Leaving the optimization-model claim unresolved.Ask whether the sentence states a formal object, a method description, a reusable way, a work plan, dated Work, or evidence; then keep only that claim in the method position.
Inferring safe execution solely from protocol approval.Separate publication-state claim, gate or authorization claim, evidence claim or assurance claim, work plan, and dated work.
Using a team’s identity in place of method semantics.Keep admitted Systems, local system-role kinds, classifications, assignments, and capability claims with their direct patterns; keep participant meanings, applicability, conditions, effects, and bounds with the Method.

A.3.1:9 - Consequences

  • Method-like language becomes reusable across physical, informational, organizational, and mathematical work without privileging software code or ordered instructions.
  • Teams can compare descriptions, variants, and implementations without confusing them with dated work.
  • Work planning and evidence become more reliable because a method statement separates reusable method semantics from authority, proof, schedule, and performed-work claims.
  • The cost is one explicit choice: before relying on method-like wording, say whether the source means a reusable way, its description, planned or performed Work, a mechanism, a representation, or another concrete claim.

A.3.1:9.1 - Lowering and local repair conditions

Withdraw a U.Method identification when the text cannot answer the ordinary method question: what reusable action is meant, for which participant kinds and conditions, with what intended result or preserved condition, and where it stops. Also withdraw it when the supposed method is only a document, repository, diagram, model, run log, team, supplier label, or authorization; when one value is called both method and mechanism without a governing dual-typing rule; or when graph or table layout is the sole basis for the asserted Method identity.

Keep a source word such as practice unresolved when the sentence does not reveal whether it means a reusable way, a description, planned or performed Work, an assignment, a discipline or tradition, evidence, or a quoted label. Do not force one of those meanings merely to complete the form.

Repair locally:

  • If the reusable way is recoverable, rewrite its identification with the missing applicability, participant meaning, condition, result, or stop.
  • If a description, plan, Work occurrence, mechanism, representation, evidence claim, or result has occupied the method position, handle that claim under its subject pattern. State a relation back to the method only if that pattern defines it and the current facts satisfy it; otherwise keep the two objects separate.
  • If a relied-on episteme no longer meets A.3.2 membership, or its cited edition, claim set, acceptance relation, semantic basis, or variant condition changed, review that changed basis and the comparisons that used it; do not invalidate every use of the method.

A new method-description edition requires reconsidering Method identity only when it describes a change to a method basis that the comparison relied on. A changed Work fact, measurement, evaluation, production, delivery, acceptance, or evidence result repairs that neighboring claim, not the reusable method by default. Use G.5 or the direct method-family pattern only when the available family or selector no longer separates the needed methods and variants. Poor explanation is a didactic defect to repair; it is not evidence that the method itself changed.

A.3.1:10 - Rationale

FPF needs U.Method because practical work often depends on a way of doing before there is one dated work occurrence, one accepted description, one final implementation, or one verified result. Treating the method as the document, code, mechanism, plan, or run makes reuse brittle: changing the publication looks like changing the method, a run error looks like method invalidation, and a mechanism claim starts authorizing work.

A method claim states the reusable way of doing, participant meanings, applicability, conditions, effects, and bounds. The mechanism episteme declares a law-governed operation family, its subject and range fields, operation algebra, laws, admissibility predicates, and Applicability. A Bridge, realization, evaluation, or evidence-use claim may relate to that episteme without entering its semantic content. The method and mechanism may be linked, but they are not two names for one untyped value.

A.3.1:11 - SoTA-Echoing

Source lineSource refsContribution and limitEffect in this pattern
Constructor-theory and process-theory bridge, with a time treatmentGogioso, Wang-Mascianica, Waseem, Scandolo, and Coecke, “Constructor Theory as Process Theory”, EPTCS 397, 2023; Deutsch and Marletto, “Constructor theory of time”, arXiv v3, revised 2026-06-05.Use the separation between a transformation specified as possible or impossible and a concrete process that realizes it. The FPF identification extends beyond physical tasks: an FPF method states a reusable way of addressing a declared concern, with generic participant meanings, applicability, conditions, intended effects, and bounds, without asserting an actual A.3.4 transformation. A concrete realizer is connected to a mechanism declaration by a separate realization relation; any actual changed referent and change occurrence belong to A.3.4, and dated enactment belongs to work. The 2023 paper is a formal bridge and the 2026 paper is a later extension, not evidence that constructor theory alone supplies a universal method ontology.The pattern starts from the method concern and separates method, actual transformation, mechanism, mechanism realization, description, plan, and work. In the manufacturing case, equipment equations and one tool run do not identify the reusable Method or prove an actual change.
Scoped effects, handlers, and semantic non-uniquenessBosman, van den Berg, Tang, and Schrijvers, “A Calculus for Scoped Effects & Handlers”, LMCS 20(4), 2024; Matache, Lindley, Moss, Staton, Wu, and Yang, “Scoped Effects as Parameterized Algebraic Theories”, ESOP 2024 extended version; Kura, “On Complete Categorical Semantics for Effect Handlers”, 2026 preprint.Use the separation among operation syntax, handling semantics, scope, resources, equations, and type-and-effect information. Kura’s result strengthens the guard: even a sound formal account need not be the only semantic model of the same handling constructs. Use only as a software-derived stress test; these calculi do not define methods in manufacturing, medicine, or organizational work.The pattern refuses to repair algorithm, program, function, handler syntax, or one semantic model to U.Method merely by programming-paradigm label. The proof and optimization cases ask for the bounded way of doing before admitting a method identity.
Graph, binding, and persistent-equivalence representationsTiurin, Barrett, Ghica, and Hu, “Equivalence Hypergraphs: DPO Rewriting for Monoidal E-Graphs”, revised 2025-05-20; Tiurin, Ghica, and Hu, “Categorical E-Graphs for Lambda Calculi”, revised 2026-06-25; Merckx et al., “E-Graphs as a Persistent Compiler Abstraction”, 2026 preprint.Use the demonstrated distinction between represented equivalence or rewriting structure and an ordered instruction sequence. Binding-aware hierarchical hypergraphs and equivalence state preserved across several intermediate-representation levels show why neither graph layout nor one representation level establishes the semantic method or dated work order. These sources are compiler and formal-representation results, not a general ontology of project methods.Graph paths, queries, tables, rewrite graphs, and persistent compiler structures remain descriptions or formal lenses until a direct method, method-relation, work, evidence, or gate claim is recovered. The graph-overread case and C.2.P.DR exit carry this safeguard.
Historical declarative versus imperative programming contrastsCodd 1970; Kowalski 1979; Selinger et al. 1979; van der Aalst, Pesic, and Schonenberg 2009; Van Roy and Haridi 2004; Deutsch 2013; Deutsch and Marletto 2015.Historical lineage and comparison cases; these anchors do not establish the current state of their fields.Treat slogans such as declarative versus imperative as recognition cues. Ask what the source phrase names—a reusable way, description, formal object, or dated Work—before assigning an FPF value.

Review a project’s U.Method identification when a change in participant meaning, applicability, precondition, intended result, preserved condition, safety bound, effective scheme, selected structure, model-use relation, or work-facing acceptance criterion could make a reader identify a different method or allow a different case. If only a description edition, Work occurrence, transformation, representation, measurement, or evidence relation changed, review that neighboring claim unless the change also alters one of those method bases.

Use G.11 when a later decision depends on the freshness or edition of a cited method description or source. A newer paper, implementation, or run is a reason to inspect the relation that cites it, not automatic evidence of a new method.

A.3.1:12 - Relations

For constructive work beyond identity, C.39.MF selects the Method question and C.39.RQ develops its situated requirements. A.3.1.DR recovers documentary contributions; A.3.1.QM qualifies an individual contribution; A.3.1.WT constructs a work trial; A.3.1.CC checks a relied-on claim; A.3.1.FT qualifies transfer; and A.3.1.MV constructs and maintains a semantic variant. Their different results do not replace this identity test.

  • Identity and meaning: builds on A.1, A.2, A.2.1, A.2.2, and C.2.1; use F.17 when a local sense matters and G.11 when a comparison relies on source or edition currentness.
  • Description, composition, and variation: coordinates with A.3.2 for method descriptions, A.3.3 for dynamics, B.1.5 for order-sensitive method composition, B.2 for whole reidentification, and G.5 for method families and selector outcomes.
  • Work and change: coordinates with A.15.2 for plans, A.15.1 for dated Work, and A.3.4 only after an actual changed referent and Transformation are independently claimed. Local system-role kinds, assignments, and relations among exact system-role kinds remain under A.2, A.2.1, and A.2.7.
  • Mechanism and representation: coordinates with A.6.0 for formal declarations, A.6.1 and E.20 for mechanisms, C.29 for mathematical-lens use, F.9 for sense Bridges, and A.1.1 only for an obtaining model-use relation or selected BoundedModelUseStructure that changes the method decision.
  • Source-wording exits: coordinates with C.20, C.36, and C.36.P for discipline and cultural-evolution uses of practice; A.10 for evidence and provenance; and C.2.P.DR for representations overread as routes or Work sequences.
  • Informs: E.18 and E.18.1 when flow-structure or P2W wording must keep descriptions, mathematical paths, method claims, and Work claims separate.

A.3.1:End

A.3.1.MR - Candidate-Method Recovery from Work Evidence

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Recover source-traceable candidate accounts of a reusable way from several performances or other direct evidence.

Primary reader. A practitioner, researcher, analyst or method engineer who needs to understand what an observed performance shows about a reusable way of working, or to recover candidate accounts from several performances or other direct evidence.

A.3.1.MR:1 - Problem frame

Use this when. Use observations or records from several performances to recover a candidate account of a reusable way before Method identification. A single demonstration can already show how one feature was enacted. If several rules could explain the action, retain the plausible alternatives and identify an observation that would distinguish them when the difference matters. If the step shown answers the immediate question, finish there.

First useful result. Return a traceable provisional explanation of the reusable way the material may show, its rivals, important gaps and limits—or state that the material shows only what happened. A distinguishing question is included when it changes the intended recovery or downstream use; neither an answerable future test nor an investigation plan is required merely to finish the account.

Three recognition cases.

  • Several maintenance visits have videos, logs, notes, and known performers. Most show one inspection order, while one changes order after a vibration cue. The question is whether the evidence supports a fixed-order way, a cue-responsive way, or only a local sequence.
  • Event data has been prepared and a discovery tool has produced a behavioural model. The question is what the selected data and modeling choices support, including what embodied, discretionary, or unrecorded contributions may be missing.
  • Several practitioners describe “the same practice,” but their accounts differ in applicability, participant meanings, intended result, or stop. The question is whether one candidate reusable way, several candidates, or no reusable account can yet be distinguished.

What goes wrong if missed. One vivid occurrence is generalized into a Method. Repeated event order is treated as reusable applicability. Several rival candidate subjects are combined into one false EntityOfConcern. A mined model, executable diagram, or coherent account is called a MethodDescription before a Method has been admitted. Missing tacit or discretionary contributions disappear behind the record format.

What this buys. A project can use imperfect evidence without overclaiming. Each positive candidate has a truthful subject, source-to-claim trace and important limits, with rivals or unresolved ambiguity preserved. A useful distinguishing question remains separate from a commitment to investigate it. Weak evidence can return a useful record-only result; RMP.10 follows only when its larger contribution is needed.

Not this pattern when. Use the closest applicable pattern instead:

  • If the evidence no longer leaves rival candidate ways and the remaining question is whether the proposed way qualifies as the U.Method being identified—or which identity claim needs repair—use A.3.1.
  • If the Method is already identified and the question is whether an episteme is its MethodDescription, use A.3.2.
  • If wording hides the object or relation being asserted, use F.19; follow an E.10 route only for a remaining FPF word, kind, or relation question.
  • If the question concerns one dated Work occurrence only, use A.15.1.
  • If the project needs prospective practice-architecture synthesis, use C.32.MWA.
  • If the domain needs a complete reconstruction programme, use RMP.10.

A.3.1.MR:2 - Problem

Evidence about Work is not the reusable way itself. Videos, logs, interviews, artifacts, and process models are selected and interpreted under Methods. They may omit perception, conversation, manual adjustment, authority, intent, failure, or local workarounds. Several observations may support more than one reusable explanation, and a coherent explanation can still be wrong.

The practical gap lies between two existing results. A.15.1 can identify what Work occurred and which Method it enacted when that claim is independently grounded. A.3.1 can identify a reusable U.Method once its meaning, scope, and limits are supportable. Neither supplies the several-occurrence recovery Method needed before Method admission. Without that intermediate result, projects either jump from record to Method or import a full specialist reconstruction programme into every case.

A.3.1.MR:3 - Forces

ForceTension
Reuse versus historical truthThe project seeks a reusable way, while every source first says something about particular Work or evidence construction.
Coherence versus underdeterminationOne neat account is useful, but several accounts may fit the same observations.
Traceability versus tacit contributionSources must support each claim, yet important perceptual, embodied, conversational, or discretionary contributions may not be recorded.
Useful grain versus false detailThe receiving use may need one broad reusable way or a safety-critical branch; the evidence should not force the wrong grain.
Discovery power versus modeling choiceProcess-mining tools can reveal patterns, but event extraction, naming, correlation, abstraction, and windows shape the result.
Provisional identity versus Method admissionA candidate reusable way needs enough identity to be discussed, without being admitted prematurely as U.Method.
Common minimum versus specialist burdenEvery domain needs source-to-claim recovery and a narrower result when the evidence is insufficient; complete sampling, elicitation, integration, and trials belong to an empirical reconstruction programme.

A.3.1.MR:4 - Solution

For every materially different reusable way that still fits the evidence, write a separate candidate account. Treat each account as one U.Episteme; use A.3.1 to decide the candidate’s Method identity while retaining the account’s source support and limits. Apply A.3.2 when the account concerns that admitted Method and a MethodDescription membership claim is needed.

A.3.1.MR:4.1 - Identify each candidate account truthfully

Each positive candidate account is one U.Episteme. Before Method admission, distinguish the possible reusable way as one provisionally identified candidate entity: give it a working designation and enough source-supported participant meanings, applicability hypothesis, intended result or preserved condition, variation, and limits to tell it from rivals. That candidate entity is the account’s EntityOfConcern.

The account’s effective reference scheme states only the designation and interpretation rules needed to read source terms such as performer, activity, cue, event, result, and stop. Add measurement or comparison rules only when the account uses them. This provisional entity identification admits neither a U.Method nor a U.MethodDescription.

When two or more candidate reusable ways still fit the evidence, return one account episteme per candidate. Each account may mention the rivals while retaining its own EntityOfConcern.

Compare them in ordinary working prose. If a later use depends on a selected comparison structure, use A.22 to identify its candidate constituents, independently obtaining relations, applied constraints and selection-use frame; a separate episteme can describe that structure. Retaining or reusing a comparison does not by itself require this construction. Several candidates do not by themselves form one subject for a combined account.

If no candidate entity or truthful effective scheme can be recovered, lower the result rather than fabricating an account.

A.3.1.MR:4.2 - Run the nine-step recovery Method

  1. State the receiving use and useful grain. Say why a reusable Method is being sought and which later action or decision would change. Do not reconstruct a fine sequence when the use needs one broad way, or a broad routine when a safety-critical branch must remain explicit.

  2. Name several grounded occurrences or other direct evidence. For every claimed Work occurrence, recover each precise performer’s A.13 core, at least one independently admitted Method enacted, and the other A.15.1 admission conditions. The recovered whole may remain a candidate while those enacted Methods are established, as in A.3.1.WT:0.1. If that admission basis is unavailable, retain the observations and sources as direct evidence without claiming Work membership.

    Add F.6 only when the candidate account also needs precise assignment-bound attribution. Keep sources such as videos, logs, notebooks, interviews, artifacts, measurements, and assertions as separate entities or epistemes with their actual evidence relations. One occurrence may open a hypothesis; it does not establish reusable applicability.

  3. Write what each source supports. Keep a readable source-to-claim account of performer Systems, relevant facts, enacted-Method claims when independently grounded, actions, cues, variations, results, and stops.

  4. Expose how evidence was constructed and what it misses. State which performers, objects, successful, failed, or atypical occurrences were observable and which contributions—such as embodied perception, conversation, manual adjustment, discretion, or tacit know-how—may be absent.

    For event data, name the preparation Method, relied-on description or configuration, source data, dated preparation Work, resulting event-log episteme, the identified event-data collection or structure that the log describes, and the interpretation scheme. If a relied-on Method, configuration, source, correlation key, event-state encoding, or observation window is unavailable, return that limit before mining.

  5. Distinguish each candidate subject. For every materially different possible reusable way, state the provisional identity and scheme from §4.1. If two candidates cannot be told apart without unsupported claims, retain the ambiguity or lower the result.

  6. Write one account per candidate. Ask the A.3.1 questions without granting Method membership: applicability, participant meanings, preconditions, intended result or preserved condition, reusable actions, supported parts or interfaces, allowed variation, and stops. Mark every unsupported position unknown rather than filling a familiar template.

  7. Compare stability, variation, and alternatives. Ask what recurs across independently grounded occurrences, what changes with the situation, what may be a performer-specific habit or local workaround, and whether another account explains the same evidence. Frequency alone establishes neither a Method part nor its value.

  8. State a distinguishing question when it changes use. If separating, repairing or lowering the candidates matters to the receiving use, identify the meaningful difference and the representative occurrence, trial, comparison or additional source that could expose it. When using held-out evidence to answer the question, keep it out of account construction. The question need not be answerable now and is not a study commitment. A source-traceable provisional account can finish without designing unavailable or irrelevant follow-up.

    Separately select investigation only when its attainable contribution warrants its whole design, acquisition, interpretation and displaced-Work burden.

  9. Return the result warranted for the receiving use. Return one or more candidate accounts ready for A.3.1 identification or specialist work, with a separate comparison only when needed; or lower to a Work-related record, local regularity, performer-specific habit, observed sequence, or unresolved cue. Prepare MethodDescription-authoring input separately. The same account can qualify as U.MethodDescription only after its EntityOfConcern is admitted as one U.Method and its claims pass A.3.2.

When the source is a live demonstration. Identify what the observer can see and what is already known about the proposed method. A performance of a known method can show a visible feature directly. If a signal and a fixed waiting time coincide in the recorded or observed episode, two different methods can fit the action. An observation in which the signal arrives later can distinguish waiting for the signal from waiting a fixed time. Use such a variation only if the difference matters. Retain the evidence at its actual scope when the methods remain indistinguishable. Admission of the observed episode as U.Work uses independently established enactment grounds from step 2.

The performed occurrence can itself serve as a model of the selected feature. A gesture or utterance can additionally express claim content under a recoverable interpretation. A judgement about the observer’s capability needs evidence about that observer under A.2.2. Evidence of a gain also calls for a comparable prior basis. Attributing the change to this demonstration calls for grounds connecting the two.

A.3.1.MR:4.3 - Select the result branch

Evidence stateResult
Several occurrences support one reusable account at the required grain, with visible source limitsOne source-traceable candidate-account episteme about one independently distinguished possible reusable way. No answerable held-out question is required unless that answer is needed by the receiving claim.
Several accounts still explain the observationsOne account episteme per candidate with source support, gaps and ambiguity; add a distinguishing question only when it changes recovery or downstream use, and a separate comparison episteme only for a named retained use.
The material shows only what happened or one local regularityA Work-related record, local regularity, observed sequence, or habit claim; no Method or MethodDescription.
A required candidate identity, scheme, claimed Work occurrence, source support, or evidence-construction premise cannot be groundedThe missing information, relation, Method, configuration, source, or interpretation rule and the dependent claim or receiving use it blocks. Retain any independently supported account or record-only result.

A.3.1.MR:4.4 - Keep process-mining contributions separate

Treat evidence preparation, process discovery, and candidate-Method recovery as three contributions.

  1. Named data-preparation Method or Methods select source events, name activities, correlate records and objects, choose event-state or start/complete encodings, and apply abstraction. Dated preparation Work uses named source data and produces an event-log episteme about the identified event-data collection or structure described by the log.
  2. A named discovery Method may return a behavioural-model episteme. Conformance checking may compare a log with a separate descriptive or normative model. Enhancement may add timing, organizational, performance, or prediction claims. Object-centric mining may preserve several typed objects and qualified relations.
  3. This recovery Method uses those well-scoped results with other evidence to return candidate reusable-way accounts or a narrower supported result, with any source-supported claims or gaps about unrecorded contributions. Include a distinguishing question only when it changes the intended use.

None of the earlier contributions automatically recovers a Method. Identify the discovered model’s claim-bearing episteme and its EntityOfConcern; keep that subject distinct from its evidential basis. A conformance result relates a log and model; it does not prove that the model describes the obtaining Method or that every deviation is defective. Executability and visual process form do not satisfy A.3.2.

Treat process, actual process, case, activity, event, variant, deviation, and process model as cues to recover the direct subject, not as types supplied by the words. Use E.10 and A.15.6 when the source remains ambiguous.

A.3.1.MR:4.5 - Stop or continue to an empirical reconstruction programme

Stop here when the receiving use needs only a source-traceable candidate account, a comparison, or a record-only result. Continue to RMP.10 when the domain and consequence require a reconstruction programme—for example, sampling across performers and settings, interviews, cognitive task analysis, ethnography, protocol analysis, process-mining design, artifact analysis, tacit-contribution recovery, fragment composition, domain trial design, or stronger assurance.

RMP.10 may strengthen the candidate accounts and prepare separate inputs for MethodDescription authoring. Use A.3.1 for Method identification and A.3.2 for MethodDescription membership.

A.3.1.MR:5 - Archetypal Grounding

A.3.1.MR:5.1 - Pump-inspection recovery

Four independently grounded pump-inspection Work occurrences have video, sensor logs, technician notes, and known performer assignments. Each occurrence enacts separately admitted vibration-measurement and bearing-temperature-measurement Methods; the evidence establishes those relations without establishing a Method for the whole inspection order. Three show the same inspection order. The fourth begins with a vibration cue and reverses two checks.

An analyst applying the recovery Method distinguishes two possible reusable ways under the plant’s current inspection vocabulary: a fixed order with an undocumented exception, and a cue-responsive order. Each candidate gets its own account episteme, candidate subject, interpretation scheme, and source-to-claim support. The account notes that the video misses a tactile check named in interviews and that successful outcomes alone do not distinguish the candidates.

A fifth occurrence is held out. A reversal when the vibration cue is present still fits both accounts while the fixed-order account’s exception condition is unknown. If the cue-responsive account requires reversal under those conditions, keeping the fixed order would challenge it. Before using a reversal to reject the fixed-order account, recover its proposed exception condition and whether it obtained. Until a supported comparison separates them, both remain candidates; neither trace nor account is a MethodDescription.

If that held-out occurrence and the remaining evidence support the cue-responsive account while the fixed-order rival no longer fits, recovery can return one candidate account ready for the A.3.1 identity test.

A.3.1.MR:5.2 - Process-mining case

The same team names its event-data preparation Method: select inspection start and completion events from the source files, name activities under the plant vocabulary, correlate records by pump and maintenance visit, and collapse duplicate sensor bursts under a stated rule. It cites the selected configuration because that configuration affects the result. Dated preparation Work on the named files produces an event-log episteme about the selected event-data collection.

If the correlation key, configuration, or source window cannot be recovered, the result is that limitation—not a raw-fact log. A separately named discovery Method returns a behavioural-model episteme with observed variants. Candidate-Method recovery then adds the two candidate reusable-way accounts, the gap concerning the tactile check absent from the video, the record-only branch, and the fifth-occurrence question.

A.3.1.MR:5.3 - Record-only lowering

Three timestamped records show that one operator checked A before B on three shifts, but the performer assignments, applicability, source window, and purpose of the sequence cannot be grounded. The useful result is an observed sequence in those records and a list of missing facts. It is not a candidate Method account, Method, or MethodDescription.

A.3.1.MR:5.4 - A useful account without another investigation

In a constructed continuation of the pump-inspection case, the supervisor needs only to compare the two candidate explanations against the four existing records before deciding how to organize the instruction material. The fixed-order and cue-responsive accounts, their separate subjects, source support and missing tactile contribution are enough for that limited comparison. Both remain provisional. No new question, fifth visit or research plan is needed to complete the requested account.

If the receiving use changes to deciding whether to retain the fixed inspection order when a vibration cue is present, the cue response becomes a load-bearing distinction. State the question and preserve the unresolved boundary even when a fifth visit is unavailable.

Select an investigation only if a suitable performer, source access, permission and window make useful discrimination worth its whole burden. Neither the useful question nor an available plan admits a Method or supplies an observed answer.

A.3.1.MR:6 - Bias-Annotation

  • Automation bias: admitting a Method from a mined or executable model without testing the reusable way under A.3.1.
  • Frequency bias: repeated order is evidence to examine, not a reusable Method part by count alone.
  • Success bias: favorable outcomes without failed or atypical cases may hide the limits of the reusable way.
  • Record bias: unrecorded perceptual, embodied, conversational, and discretionary contributions remain possible gaps.
  • Single-tradition bias: check whether the selected approach supplies what the receiving reconstruction needs; obtain another contribution only for a material remaining gap.
  • Template-completion bias: unsupported account positions remain unknown rather than being completed from familiar practice.

A.3.1.MR:7 - Conformance Checklist

  • CC-A3.1.MR-1 — Receiving use and grain. Is the later use clear enough to choose the useful reconstruction grain?
  • CC-A3.1.MR-2 — Grounded evidence. Are claimed Work occurrences and other sources identified under their own patterns and relations?
  • CC-A3.1.MR-3 — Source-to-claim trace. Can the reader see which source supports each account claim?
  • CC-A3.1.MR-4 — Evidence construction. Are selection, naming, correlation, abstraction, configuration, window, and likely missing contributions explicit when they matter?
  • CC-A3.1.MR-5 — One candidate per account. Does every candidate-account episteme have one candidate reusable-way EntityOfConcern and effective scheme?
  • CC-A3.1.MR-6 — Rival retained. Are real competing accounts or unresolved ambiguity visible without inventing a rival to complete the form?
  • CC-A3.1.MR-7 — Useful distinguishing question. Where discrimination changes recovery or downstream use, is the question clear and any held-out evidence kept out of account construction? Does the account remain usable when no answerable investigation is needed or available, with stronger dependent claims withheld?
  • CC-A3.1.MR-8 — Result branch. Does the result stop at candidate account, separate comparison, record-only result, or named blocker without granting Method or MethodDescription membership?
  • CC-A3.1.MR-9 — Specialist exit. Is RMP.10 used for complete reconstruction only when the receiving use needs its larger burden?
  • CC-A3.1.MR-10 — Plain use. Can a cold practitioner explain the candidate, evidence, rivals, gaps and supported current use without a mandatory next-test plan?

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

Anti-patternRepair
“The common sequence is the Method.”Recover applicability, participant meanings, intended result, variation, limits, rivals, and missing contributions first.
“The mined model is the MethodDescription.”Keep the model as an episteme with its subject and claims. Apply A.3.2 only when that same episteme concerns an admitted Method and makes a substantive claim about it as a way of doing.
“Several candidates form one concern.”Return one account per candidate; create a separate comparison subject only for a named use.
“One expert performance proves the reusable way.”Use it to open a hypothesis; seek several grounded occurrences or lower the result.
“The log is raw fact.”Name preparation Method, configuration, source, dated Work, correlation, encoding, window, and resulting event-log episteme.
“Unknown means fill the standard field.”Keep unsupported positions unknown and preserve their use limits. Add a distinguishing question only when it changes the receiving use; a missing field does not commission evidence collection.
“Every recovery needs a full study.”Stop when the source-traceable candidate or record-only result is sufficient for the receiving use; otherwise state its limit. Enter RMP.10 only when that use needs specialist reconstruction.

A.3.1.MR:9 - Consequences

BenefitCost or caution
Several imperfect sources can support a useful provisional account.Every account claim must remain traceable to its supporting sources. State the evidence-construction Method and choices when they affect reliance on those sources; retain the event-data requirements of §4.2.
Rival accounts remain visible instead of being averaged into one false subject.A project may have to carry several candidates until discriminating evidence arrives.
Process mining becomes a well-scoped contribution rather than an ontological shortcut.Preparation and discovery choices must be exposed when the account relies on them.
Record-only evidence returns a useful result.The user must resist promoting a coherent sequence to a Method by form or frequency.
Specialist Method Engineering receives source-traceable candidate accounts.Complete reconstruction remains a separate, sometimes costly programme.

A.3.1.MR:10 - Rationale

Candidate recovery connects evidence about performances to identification of a reusable Method. A candidate account is an episteme about one provisionally distinguished possible reusable way. Method identity and MethodDescription membership remain later, separate judgments.

The one-account-per-candidate rule protects episteme subject truthfulness when evidence underdetermines the reusable way. The record-only branch protects utility when evidence is too weak. The specialist exit keeps ordinary recovery usable while preserving the larger evidence burden for domains that need it.

A.3.1.MR:11 - SoTA-Echoing

Source lineContributionUse and limit
Feldman and Pentland, Routine dynamics: Toward a critical conversation (2022)Separates particular performances from enduring or emergent patterns and keeps variation visible.The performance/pattern distinction matters here: Repeated Work can support a candidate account without itself becoming the Method.
Stacey et al., Methods as a form of engineering knowledgeDistinguishes descriptive reconstruction from prescriptive method content and shows why the distinction can be difficult to maintain.Coherent description does not establish Method admission or MethodDescription membership.
Process-mining reference: Process Mining Handbook (2022); exchange-format boundary: OCEL 2.0 semantics and the 2.1 serialization revisionSupplies preparation, discovery, conformance, enhancement, and multi-object event representation capabilities.Event extraction, naming, correlation, object identity, encoding, abstraction, windows, and serialization remain modeling choices; mining alone establishes no applicability, intention, authority, tacit contribution, causal value, or Method identity.
Object-centric recovery alternatives: Adams et al., Defining Cases and Variants for Object-Centric Event Data and Küsters and van der Aalst, OCPQReal event data may relate one event to several objects; selecting one case key or flattening can discard information, while queries and constraints produce use-bounded results.Preserve the multi-object evidence and state the selected grouping, query, or constraint when it changes the candidate account. Keep an execution, its representation, and any query or constraint result distinct. Their form alone does not identify the reusable Method.

A.3.1.MR:12 - Relations

A.3.1.DR supplies the separate documentary-recovery question. RMP.10 constructs an empirical reconstruction programme when the required sampling, elicitation, event-data preparation and integration exceed the candidate-recovery result here; RMP.11 addresses the different question of an evidence-supported historical explanation.

  • Builds on: C.2.1 for each account episteme, its EntityOfConcern, and effective scheme; A.3.1 for the questions that shape a candidate without granting Method membership; A.13 for each precise performer’s local agency core; A.15.1 for independent admission of grounded Work occurrences; F.6 only when precise assignment-bound attribution is needed; and A.10 for bounded source reliance.
  • Coordinates with: A.3.2 for later MethodDescription membership; A.15.6 for ambiguous process or case wording; A.22 for a separately selected comparison structure only when needed; C.32.MWA for prospective several-structure practice synthesis; and C.11.DUA when a questionable investigation demand needs appraisal of its attainable contribution and whole burden.
  • Receives bounded evidence from: process-data preparation, discovery, conformance, enhancement, object-centric mining, interviews, observations, artifacts, and measurements under their own Methods and claims.
  • Hands off to: A.3.1 for Method identification or RMP.10 for complete reconstruction; neither continuation is automatic.
  • Keeps separate: source, record, event log, behavioural model, Work, candidate reusable way, candidate account, admitted Method, MethodDescription, and any comparison episteme.

A.3.1.MR:End

A.3.1.DR - Recover Method Contributions from Documentary Sources

Type: Method pattern Status: Stable

A.3.1.DR:1 - Problem Frame

Use this when. A methodology, standard, body of knowledge, maintained synthesis, reference model, or tool suite mixes reusable ways of doing with descriptions, Systems, capabilities, evidence, authority, and support. The receiving decision needs contributions from one package or several documentary sources, but their chapters and component lists do not establish Method structure.

Begin with one receiving decision and the exact source edition or snapshot. For several sources, keep each source’s role and recovery scope visible. Recover only contributions and dependency slices that can change the decision; completeness is relative to this boundary.

The first useful result is a source-traceable Method-recovery dossier. Identified Methods and individually scoped candidate accounts can proceed to A.3.1.QM with their support and evidence limits. A proposed whole proceeds to B.1.5.CM when its identity and relations are the question. Tools, descriptions, capability, authority, and other useful contributions remain available under their kinds.

Ordinary non-use. Do not decompose an already precise Method to populate a library or inventory material whose presence cannot change the receiving decision. If records, interviews, traces, or observations are offered as evidence from which a reusable way must be reconstructed, use A.3.1.MR; enter specialist RMP.10 only when its additional evidence programme is needed.

A document can contain both prescribed guidance and testimony about performance: route the selected contribution by its use, not by its file extension.

A.3.1.DR:1.1 - Working Distinctions

Name used hereMeaning
documentary source boundaryThe exact package, edition, snapshot, or bounded corpus from which the receiving use recovers claims. It establishes no Method whole.
documentary roleHow this source may contribute now: for example, a current comparator, maintained synthesis, normative statement, historical account, Method claim, or worked example. These are source-use descriptions, not FPF kinds.
recovery profileHow much source-local recovery the use needs. It differs from what the source is evidence for.
dossier entryOne source-traceable contribution retaining its existing kind or ordinary unresolved status.
source meaningWhat the selected source says or uses the contribution to do, before local adaptation or cross-source comparison.
bounded useThe receiving decision, scope, conditions, and claim for which the contribution is recovered.
decision-bearing relationA direct relation whose truth changes whether or how the contribution can be used.
provenance-preserving dependency sliceThe smallest set of source claims, descriptions, inputs/results, support, evidence references, and relations needed to judge one Method or candidate account.
navigation sectionAn open reading aid, such as “Methods and accounts” or “Systems and support”; membership creates no type.

Heavyweight packages connect concerns through publication, pedagogy, institutional history, tools, or viewpoints. Their visible organization may differ from Method, Work, subject, description, capability/provider/support, allocation, or cultural structures.

Method Content Theory and design-Method element research contribute questions about goal, procedure, rationale, framing, mindset, representation, intended use, and tools. Keep the answers with the Method, candidate account, description, capability, support relation, cultural claim, or other subject they concern. Several sources can ask similar questions without giving the same answer.

A.3.1.DR:2 - Problem

Copying package headings into a Method library can misidentify the contributions. A role becomes a Method, a checklist becomes a component, a tool becomes a participant Method, and adjacency becomes methodPartOf. The opposite error extracts a procedure alone and loses the rationale, input/result correspondence, authority, evidence, or support condition that makes it usable.

A later qualification then appears precise but cannot be replayed from the source and cannot distinguish a Method defect from missing access, capability, evidence, or authority.

A.3.1.DR:3 - Forces

ForceTension
RecoverabilityA later decision needs source meaning and provenance, while copying the whole package hides the load-bearing slice.
Ontological precisionEntries have unlike kinds, while one local dossier must remain readable.
Package cohesionSource relations can matter, while package position and visual nesting supply no relation by themselves.
AffordabilityA complete inventory feels safe, while decision-irrelevant entries add cost and false completeness.
AdaptationA source contribution may be useful under changed conditions, while adaptation must not rewrite what the source claimed.

A.3.1.DR:4 - Solution

F.0.1 supplies source-local meaning recovery; A.3.1.MR instead reconstructs a candidate reusable way from Work evidence. The documentary operation below retains what an author proposes, including the source’s complete constructive scope where that is the requested result. It does not convert a documentary assertion into an observation of practice.

Build a source-traceable dossier around the receiving decision. Recover each documentary contribution in its own source meaning, preserve unlike kinds, and prepare only the downstream subjects needed for the receiving decision.

A.3.1.DR:4.1 - Pattern-Use Unfolding

  1. Bound the receiving use and sources. Name the decision, relevant viewpoint, scope, and exclusions. For each documentary source give its exact edition or snapshot, source-return locator, role in this use, selected recovery profile, and currentness or reopening condition. One package normally needs one compact source/use statement, not a separate register.

  2. Choose how much to recover. Use the profiles below. A maintained source’s source-local recovery and comparison with current alternatives answer different questions; do not let the comparison erase a source contribution before it has been understood.

  3. Read source meaning before placement. For each selected contribution retain the source term and locator, difficulty or opportunity, any asserted reusable action or change, any first useful result or blocker, and receiving use. Keep its original status, limits, purpose, and explicit or implied relations. A source ambiguity remains an ambiguity.

  4. Preserve the subject and evidence role. Distinguish identified Methods, individually scoped candidate accounts, MethodDescriptions or other epistemes, Systems and support/access, capabilities and assignments, inputs/results/premises, and direct relations. A source’s report of evidence is recovered as that report, not as independently established Work or effectiveness. Send a new question about a reusable way in occurrence evidence to A.3.1.MR; specialist RMP.10 follows only under its entry condition.

  5. Record intended use and possible loss. Say what the receiving use proposes to keep, change, reject, or leave unresolved and what source meaning or context would be lost. These are source-local recovery dispositions. Do not yet assert cross-source sameness, perform semantic merging, allocate a remainder to a supplier, or design the resulting pattern language.

  6. Recover direct relations and small dependency slices. Retain supported production/use, schema correspondence, provider access, allocation, responsibility, authority, or other relevant relations. A line, container, chapter, lane, or local section supplies no relation. Attach only the source claims, conditions, and returns needed for the next judgement.

  7. Prepare the downstream subjects. A.3.1.QM receives only identified Methods and individually scoped candidate Method accounts, each with the smallest slice needed to judge contribution, inputs/results, applicability, burden, capability, support, authority/access, and evidence.

    B.1.5.CM receives a proposed-whole account when whole identity and relations are the question; retain its proposed semantics, participant statuses, relation boundary, and source slices. Other kinds remain in the dossier or accompany those subjects without becoming Methods.

  8. Return the dossier and any blocking gaps. Use open navigation sections when they help retrieval. Stop when the subjects and source basis needed for the receiving decision are recoverable. If edition, role, receiving use, a needed current comparator, source return, kind, relation, or evidence is missing, name the affected contribution and the missing basis. Continue unaffected recovery when it can still serve the receiving decision; do not claim completeness beyond the recovered boundary.

A.3.1.DR:4.1.1 - Select the Recovery Profile Per Source

For an ordinary package, the default is decision-bounded recovery: inspect only source claims and dependency slices that can change the receiving decision. This default needs neither maintained-synthesis status nor a prior supplier comparison. Select a specialized profile below only when its condition holds; naming a profile does not itself add a recovery operation or a record.

ProfileSelect whenRecovery and limit
SoTA-firstCurrent alternatives can change which contributions the receiving decision needs.Establish the relevant current comparison through C.39.RP or the direct source route, then recover its decision-bearing claims. “Recent” alone is not a qualification.
Full source-localAn accepted maintained synthesis must remain reconstructable within a named scope.Recover every decision-bearing contribution in that scope before later filtering. Preserve unsupported or non-selected material through source returns; do not import the source ontology or every chapter as a Method.
Gap-onlyAn exact earlier source/supplier comparison and its affected gap or delta are recoverable.Recover that gap and its dependencies. Widen or stop if the baseline, scope, or source meaning has changed. A missing keyword is not a gap definition.
MixedThe bounded corpus contains sources with different roles or recovery needs.Apply the appropriate profile separately to each documentary source. Route occurrence evidence separately and retain the limits of any returned candidate account, specialist dossier, or lower result.

“Full” is not an instruction to extract all possible knowledge from a source. The receiving decision sets the completeness boundary. A change from source-local recovery to cross-source reconciliation is a new question, not the final step of A.3.1.DR.

A.3.1.DR:4.2 - Record the Result

Dossier positionRequired content
recovery boundaryReceiving decision, source set and exact editions/snapshots, viewpoint, scope, and exclusions.
source/use statementPer source: locator, role, recovery profile, receiving use, and currentness or reopening condition; combine this with the boundary for one ordinary package.
entriesLocal reference, source locator and meaning, difficulty/opportunity, any asserted action/change, any first result/blocker, existing kind or unresolved status, bounded use, and loss.
direct relationsRelated subjects, relation, source or evidence basis, truth status, and unresolved condition.
occurrence-evidence return, when neededThe A.3.1.MR or RMP.10 result with its own candidate statuses, rivals, gaps and evidence limits. Include a distinguishing question only when it changes the receiving use, or a held-out result only when obtained. An ordinary account needs no prospective study to fill this row; raw observations are not documentary Method entries.
navigationOpen local sections used only for finding contributions.
downstream subjectsIdentified Methods and individually scoped accounts with dependency slices for A.3.1.QM; a proposed-whole account with its identity/relation boundary for B.1.5.CM when needed.
stop and returnSupported result for the receiving decision; any missing source, role, use, comparator, kind, relation, or evidence; any further question the decision requires.

Keep these distinctions in the dossier already being used; they are not a requirement for one file or row per field. A short one-source result can carry the source/use statement in its opening sentence.

A.3.1.DR:4.3 - What Changes in Practice

Practitioners can reuse a Method, retain a candidate account, cite a description, require a capability, preserve an authority stop, or depend on a System without importing a package as a Method whole. A plural dossier also shows why each source was inspected and how far its contribution reaches. Later qualification stays small and source-recoverable; later reconciliation can distinguish a real disagreement from unlike source roles.

A.3.1.DR:5 - Archetypal Grounding — EC-417 Release Assurance Package

For this constructed case, take the listed EC-417 package contents as one fixed documentary snapshot. Use it as Method guidance for the changed release decision, recover the decision-bearing slice, and return when the package, receiving use, or a relied-on condition changes. This supplies the source/use boundary for the one-source case.

The EC-417 team receives a “release assurance methodology” containing a stage table, release checklist, supplier procedure, AI prompt, PLM and CI instructions, test-rig guidance, role descriptions, and stored evidence bundles. The receiving decision is whether its Method contributions and candidate reconciliation accounts can support a changed release arrangement.

The dossier uses open sections but preserves unlike kinds:

Local sectionRecovered entries and statusesDecision-bearing slice
Methods and candidate accountsidentified M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, M-Release-Authorize; candidate C-Evidence-Reconcile-Internal, C-Evidence-Reconcile-Supplier, C-AI-Trace-Review, and proposed whole C-EC-Release-v2Each Method or account keeps its source claims, required inputs/results, support, evidence, and limits.
descriptions, representations, and source claimsstage table, release checklist, supplier procedure, AI prompt, bundle recordsThese epistemes may describe or evidence a Method/account; none is promoted by its section.
Systems, support, and accessPLM, CI, test rig, AI provider, and provider-access conditionAvailability and access are separate from Method identity and fit.
capabilities and assignmentssafety competence, supplier-configuration responsibility, and release-authority assignmentCapability, responsibility, and authority are checked for the receiving use.
inputs, results, premises, and evidencepinout schema, evidence bundle, verification result, confidentiality premise, and dated recordsEach item keeps its direct kind and use.
relationsproduction/use, schema correspondence A-17, provider access, allocation, responsibility, and authorityEach relation is independently stated; no section or package edge supplies parthood.

Two example dependency slices show why the full package is neither copied nor discarded:

  • M-HW-Verify travels with its change input, verification-result meaning, rig condition, hardware capability, procedure provenance, and evidence window.
  • C-Evidence-Reconcile-Supplier travels with the supplier procedure, signed-evidence condition, supplier-configuration responsibility, closure authority, four observed source cases, and the unresolved A.3.1 identification question.

The supplier procedure’s four reported cases remain a documentary source claim and evidence return in this recovery. Inspecting the underlying occurrence records to reconstruct a reusable way is a separate A.3.1.MR question.

The four identified Methods and the three individually scoped candidate accounts are potential A.3.1.QM subjects for this use. PLM, rig, competence, authority, schema, evidence, and descriptions remain in their slices under their own kinds. C-EC-Release-v2 remains a proposed-whole candidate account and may later be resolved by B.1.5.CM; its presence in the package creates neither a fifth Method nor methodPartOf facts.

A.3.1.DR:5.1 - Two Documentary Roles and an Interview

This constructed case concerns a change to the release-assurance arrangement. Handbook H, edition 3, section 4, is an accepted maintained synthesis for reconstructing the supplier-evidence practice. Comparison C, edition 2, section 2, is the current comparator for the same receiving decision. Interview I, recorded on day D1, is offered as evidence about what happened during one release. These are local scenario references.

Source/use statementSource-local contribution retainedResult and return
H/3 §4; maintained synthesis; full source-local within the supplier-evidence practice; return if that section or the receiving scope changes.Missing supplier evidence can stop release. The source proposes reconciliation before authorization and names a signed-evidence result. It also names supplier access and authorization conditions.Recover the reusable-way claim at its existing status with those conditions; preserve access and authority as different subjects. Return to H/3 §4 for its meaning.
C/2 §2; current comparator; SoTA-first for this decision; return if a rival or the comparison basis changes.A separately reviewed evidence bundle is proposed to reduce reliance on one supplier account. Its first result is a reviewed bundle or a named evidence gap. The claim’s tested reach is limited to the comparison’s cases.Retain this alternative and its limits separately from H. Do not decide that two differently supported activities are one Method or that either replaces the other.
I/D1; occurrence evidence, not a third documentary recovery profile.The interview reports one release episode but does not yet distinguish a reusable way from a one-off response.For the one-occurrence question use A.15.1. If several occurrences create a candidate-recovery question, use A.3.1.MR; keep a record-only lower result when that is all the evidence supports. RMP.10 is not an automatic next step.

The first result is the two-source documentary dossier plus the occurrence-evidence return, not a merged release Method. When the receiving decision needs a semantic comparison, examine whether the two documentary contributions overlap, conflict or complement one another; leave unresolved relations explicit.

If C’s full argument becomes unavailable but a page-located excerpt remains, retain the excerpt and reopen only entries whose receiving use depends on the missing context. H’s independent source-local result remains usable. Do not turn unavailable support into proof that C was false, or continue a gap-only recovery without its baseline.

A.3.1.DR:6 - Bias-Annotation

BiasLikely driftRepair
source-taxonomy biasGoal, procedure, rationale, framing, mindset, representation, role, or tool becomes a universal Method component kind.Use those terms as source questions and place each returned claim with its subject.
diagram-containment biasA box or lane is read as composition or parthood.Require the direct relation and its evidence independently.
package-authority biasInstitutional or standards status becomes Method identity, fit, or effectiveness.Separate source authority from the receiving claim and evidence.
procedure-only biasA reusable action is extracted without rationale, applicability, input/result, support, or authority.Carry the smallest dependency slice that can change qualification.

A.3.1.DR:7 - Conformance Checklist

  • The dossier names one receiving decision and an exact documentary source boundary, with each relied-on edition or snapshot recoverable.
  • Each source has a use-changing role, recovery profile, source return, and currentness/reopening condition; the one-source case needs only a compact statement.
  • Occurrence-evidence recovery remains with A.3.1.MR and conditional RMP.10; returned evidence limits and lower results are preserved.
  • Source-local recovery stops before cross-source sameness, semantic merging, supplier allocation, or pattern-language design.
  • Every selected entry retains its source locator, source meaning, existing kind or unresolved status, bounded use, and loss.
  • Navigation sections can be added, split, or omitted; membership in one does not establish a type.
  • Every direct relation has a source or evidence basis independent of layout.
  • Identified Methods and candidate accounts are distinguishable from descriptions, Systems, capabilities, assignments, evidence, and relations.
  • Every A.3.1.QM subject carries the smallest provenance-preserving dependency slice needed for judgement.
  • Missing source access, kind, relation, or evidence remains visible.
  • No package, chapter, list, view, or section creates Method candidacy, family membership, composition, or methodPartOf.

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

Anti-patternRepair
Six local sections become six ontology kinds.Call them open navigation and keep each entry’s existing kind.
Everything actionable becomes a Method candidate.Require a reusable way-of-doing account; keep support, capability, evidence, and authority under their direct kinds.
The package is reduced to a procedure.Recover rationale, framing, intended use, inputs/results, support, evidence, and authority only where they change the receiving decision.
The whole package is copied for provenance.Attach a bounded dependency slice to each Method/account and retain a source return to the package edition.
Unknown relation is inferred from adjacency.Record the relation as unresolved and name any known source or observation that could settle it.

A.3.1.DR:9 - Consequences

The package becomes selectively reusable while its provenance and the kinds of its contributions remain explicit. Later qualification can inspect one Method or account together with the dependencies that make its use meaningful.

The cost is explicit kind and relation recovery. Important support, authority, or evidence conditions may become more visible than the source’s headline procedure.

A.3.1.DR:10 - Architectural Rationale

A heavyweight package is a publication and practice carrier, not evidence that its visible organization is a Method structure. Preserving unlike kinds lets several useful representations coexist without forcing one-to-one correspondence among Method, Work, subject, description, capability/provider/support, allocation, and cultural structures.

The dossier is open. Its value lies in tracing source contributions to the receiving decision and retaining their dependency slices, not in a fixed number of sections or a universal element taxonomy.

A.3.1.DR:11 - SoTA-Echoing

SourceRetained contributionUse boundary
Daalhuizen and Cash, Method Content TheoryGoal, procedure, rationale, framing, and mindset as questions that prevent procedure-only recovery.Static content variables and initial study population do not define FPF kinds, Method parts, or cross-domain effectiveness.
Gericke, Eckert, and Stacey, Elements of a design methodCore idea, representation, procedure, intended use, tool, ecosystem, and adaptation prompts.Source elements remain questions and source claims, not a universal dossier ontology.
Stacey et al., Methods as a form of engineering knowledgeComparison of engineering-Method knowledge and the placement of representations, framing, and rationale.Conceptual comparison supplies no project Method identity or package parthood.

Revisit the recovered dossier when a source or package case exposes a decision-bearing contribution whose kind, provenance, role or relation remains unclear; when a selected recovery profile omitted a material receiving condition; or when the dossier imposes work that its receiving use does not need.

A.3.1.DR:12 - Relations

  • A.3.1.MR governs candidate recovery from occurrence evidence; RMP.10 supplies its specialist continuation only when needed. Documentary claims about evidence remain distinct from those recovery results.
  • Cross-source reconciliation and allocation consume the dossier later. A.3.1.DR preserves the inputs and return paths but does not settle that next semantic question.
  • A.3.1 governs Method identity; A.3.2 governs MethodDescription claims; B.1.5 governs Method composition; F.18 governs durable name claims.
  • C.39.MF supplies the focus and receiving decision when package recovery is the chosen next result. C.39.RP may supply an inherited repertoire or source lineage.
  • A.3.1.QM receives identified Methods and individually scoped candidate accounts with provenance-preserving dependency slices. It does not receive the local navigation sections as types or a proposed whole merely because the package presents one.
  • C.32.MWA.PP receives only a several-structure synthesis question that remains after individual qualification.
  • B.1.5.CM receives a proposed whole account when its identity and relations must be resolved.

A.3.1.DR:End

A.3.1.QM - Qualify a Method for Its Intended Contribution

Type: Method pattern Status: Stable

A.3.1.QM:0 - Use This When

Use this pattern when a project has one or more Methods identified under A.3.1, candidate Method accounts, and situational criteria, but it does not know which subjects are individually usable for the bounded result. Use it before a several-structure comparison when an individual condition can settle whether the subject remains a candidate for the receiving use.

Begin with one Method or candidate account, its status, the contribution it is expected to make, and the criteria that matter for that contribution. Keep whole-level allocation, synchronization, composition, and compatibility questions outside the individual result.

The first useful result says one of the following: an identified Method is qualified or not qualified for the bounded use; a candidate account is retained or excluded while its Method-identification question remains open; or a local connection claim is supported, unsupported, or unresolved independently of a whole synthesis.

Do not use qualification wording to admit a candidate account as a Method, to establish compatibility or parthood, or to declare a Method architecture fit.

A.3.1.QM:0.1 - Working Distinctions

Name used hereMeaning
identified Method subjectA Method already identified under A.3.1; A.3.1.QM judges bounded use without repeating identity.
candidate-account subjectAn episteme about a possible Method whose unresolved identity conditions remain visible throughout qualification.
individual contributionThe result or preserved condition expected from enacting the Method or proposed reusable way under the stated use, rather than the success of a whole arrangement.
local connectionAn input/result, schema-correspondence, or adapter-feasibility claim whose truth does not depend on choosing one whole synthesis.
individual qualificationA bounded result covering contribution, applicability, inputs/results, attributable time or burden, capability, support, authority/access, evidence, source limits, and stop.
architecture questionA claim about combined allocation, timing, composition, Work overlap, provider arrangement, authority distribution, or another several-structure relation. Use C.32.MWA.PP when such a question needs resolution.

A.3.1.QM:1 - Problem Frame

Method selection depends on situation and fit, but project candidates arrive with different bases for their identification. One is an identified Method with known use evidence, another is a candidate account recovered from Work records, and a third phrase refers only to a tool or support condition.

Individual qualification can save architecture effort by rejecting a candidate that cannot produce the required result or cannot meet one non-negotiable condition. It becomes misleading when it averages several Methods and support arrangements into one fit score or upgrades an account through confident language.

A.3.1.QM:2 - Problem

Three errors obscure the result. First, a retained candidate account is called a qualified Method. Second, one independently feasible schema mapping is called compatibility of the whole package. Third, a combined peak-load or authority conflict is hidden inside separate “passes” for each Method.

The project then believes the architecture problem is solved even though no result states how the individually plausible subjects work together.

A.3.1.QM:3 - Forces

ForceTension
Early rejectionAn individual condition can rule out a subject for the receiving use before whole comparison; combined conflicts remain visible for C.32.MWA.PP.
Status preservationCandidate accounts need useful assessment, while qualification cannot identify their Methods.
Comparable questionsA common set of questions aids choice, while not every question applies to every subject.
Evidence proportionalityA bounded use may need little evidence, while safety, authority, or high burden can require stronger support.
Local connectionsA schema or adapter can be tested independently, while its placement and maintenance belong to a whole synthesis.

A.3.1.QM:4 - Solution

A.3.1 decides Method identity. This Method uses that result, or an explicitly unresolved candidate, to qualify one contribution for a receiving use. It does not repeat Method admission or infer the adequacy of a combined arrangement from the qualification of its participants.

Qualify one subject at a time against the bounded receiving use. Preserve status, expose unsupported conditions, and route only combined questions to C.32.MWA.PP.

A.3.1.QM:4.1 - Pattern-Use Unfolding

  1. State the subject and status. Name the identified Method or candidate account and cite the identity or account basis already available. Reject unlike support facts as qualification subjects.
  2. Bind the use. State the receiving Work or result, situation family, scope, time window, non-negotiable criteria, acceptable variation, and decision that will consume the qualification.
  3. Recover the individual contribution. Name the input, result or preserved condition, procedure or invariant as far as known, applicability, and important source meaning. Do not credit the subject with another Method’s result.
  4. Check attributable conditions. Inspect the conditions relevant to this contribution: timing and burden attributable to this subject; performer capability; support and provider access; authority or responsibility; evidence; and source or transfer limits.
  5. Test local connections only. Check an input/result handoff, schema correspondence, or adapter feasibility when it can be assessed independently of a whole synthesis. Record its scope and any known failure condition relevant to the receiving use.
  6. Return the result. An identified Method is qualified or not qualified for the bounded use. For a not-qualified result, distinguish a failed criterion from an insufficient basis to judge it. A candidate account is retained or excluded as an account, with unresolved identification conditions unchanged. A local connection is supported, unsupported, or unresolved.
  7. Choose the stop. Stop when the individual qualification or local-connection result is sufficient for the receiving decision and no whole question remains. Enter C.32.MWA.PP only when a several-structure choice can change the decision.

A.3.1.QM:4.2 - Record the Result

Result positionRequired content
subject and statusMethod identity or candidate-account reference and the status that remains after qualification.
bounded useReceiving result or Work, situation, scope, window, criteria, and consuming decision.
contributionInputs, result or preserved condition, known procedure/invariant, applicability, and variation.
attributable conditionsTime/burden, capability, support/provider access, authority/responsibility, evidence, and source limits attributable to this subject and relevant to the receiving use.
local connectionsIndependently assessed input/result, schema, or adapter claims with scope and status.
verdict and stopQualified/not-qualified Method or retained/excluded account, failed criteria or missing qualification basis, open identity conditions, remaining whole question, and next action.

A.3.1.QM:4.3 - What Changes in Practice

Teams can use individual qualifications without treating them as a verdict on the whole arrangement. They can reject one Method, retain a promising account without admitting it, and prove one schema mapping without calling the whole arrangement compatible. C.32.MWA.PP then receives only the combined timing, allocation, support, authority, or composition questions.

A.3.1.QM:5 - Archetypal Grounding — EC-417 Individual Stops

The EC-417 dossier supplies four identified Methods and several candidate accounts. The bounded use is a safety-relevant release arrangement in which signed evidence must exist before safety closure, confidential supplier geometry must stay outside the AI provider, and decision Work remains with admitted human Systems under separate covering assignments and permission or direct decision-authority relations.

Subject and prior statusIndividual resultA.3.1.QM return
M-HW-Verify, identified Methodaccepts the affected change and pinout version; produces a verification result with named rig and hardware capability conditionsqualified for the bounded use
M-SW-Integrate, identified Methodaccepts explicitly versioned provisional or signed pinout evidence; its integration record preserves the exact edition, any provisional uncertainty, and the edition used; later signed evidence supersedes a provisional edition only for safety-closure reliance while the earlier use and provisional-to-signed relation remain traceable; software remains reversible until D-1qualified under the evidence-version, history, closure-reliance, and reversibility conditions
M-Supplier-Approve, identified Methodproduces signed supplier approval or the explicit missing-approval stop; requires supplier-configuration responsibility and evidence accessqualified under the named access and responsibility conditions
M-Release-Authorize, identified Methodconsumes the safety result and named evidence conditions; admitted human System ReleaseDecider-17 performs W-ReleaseDecision-17 under covering assignment ASG-ReleaseDecision-17 and independently supported direct relation AUTH-ReleaseDecision-17; returns release, withhold, or next-slot authorizationqualified for the bounded Work, assignment, and authority scope; none proves the others
C-Evidence-Reconcile-Internal, candidate accounteight internal cases support an account in which the versioned provisional edition, uncertainty, and earlier integration use remain traceable through reconciliation to later signed evidence before closureretained as a candidate account; A.3.1 identification remains open
C-Evidence-Reconcile-Supplier, candidate accountfour supplier-originated cases and one held-out supplier case support a signed-evidence branchretained as a candidate account; A.3.1 identification remains open
C-AI-Trace-Review, candidate accountthe account specifies a trace-suggestion contribution; TraceReviewer-17 performs the accept/reject Work under ASG-TraceReview-17 and PERM-TraceAcceptReject-17, while the AI provider holds neitherretained as a human-governed candidate account

The provider-default AI proposal is outside A.3.1.QM’s present qualification subjects because no identified Method or candidate Method account has been supplied for it. Independently, implementing the proposal would disclose confidential geometry to the AI provider, and the proposal names no admitted human decision performer, covering assignment, or permission/authority relation. Those failures would block this use even if a candidate account were supplied.

Local schema correspondence A-17 maps signed or explicitly provisional pinout-version fields to the integration bundle and preserves the exact edition and uncertainty used. Five stored bundles support that mapping for the named schema editions. The mapping preserves the provisional basis after later signed evidence becomes the safety-closure basis. This is a local connection result, not whole compatibility.

Two stops are now available. A project needing only hardware verification can stop with the qualified M-HW-Verify; no architecture comparison is required. A project investigating supplier reconciliation can stop with the retained C-Evidence-Reconcile-Supplier account and its open A.3.1 question. EC-417 continues to C.32.MWA.PP only because the combined safety allocation, board timing, evidence routing, and recovery burden differ among whole alternatives.

A.3.1.QM:6 - Bias-Annotation

BiasLikely driftRepair
fit-score biasUnlike contribution, capability, authority, evidence, and burden claims collapse into one number.Return the decision-changing conditions and qualification result instead of an opaque total.
candidate-upgrade bias“Qualified candidate” is read as identified Method.Repeat the account status in the verdict and state the open A.3.1 condition.
compatibility biasOne feasible handoff or schema mapping becomes whole fit.Call it a bounded local connection and route combined questions to C.32.MWA.PP.
decomposition biasEach support System, role, or evidence item is evaluated as a Method candidate.Accept only identified Methods and candidate Method accounts as qualification subjects.

A.3.1.QM:7 - Conformance Checklist

  • Every subject is an identified Method or a candidate Method account and keeps that status.
  • The qualification names one receiving use, scope, situation, window, and consuming decision.
  • Contribution, inputs/results, applicability, attributable burden, capability, support, authority/access, evidence, and source limits are checked as applicable.
  • No subject receives credit for another Method or whole arrangement’s result.
  • Local connection claims are independently testable and bounded.
  • A candidate-account verdict preserves unresolved A.3.1 identification conditions.
  • Whole allocation, synchronization, composition, provider, and architecture questions remain explicit rather than hidden in individual verdicts.
  • The result states whether to stop, reject, retain, or enter C.32.MWA.PP.

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

Anti-patternRepair
“This account fits, so it is a Method.”Retain or exclude the account and send identity to A.3.1.
“All individual Methods pass, so the architecture is compatible.”State the unresolved combined structure and use C.32.MWA.PP only when it changes the decision.
“The adapter works, so integration is solved.”Bound the adapter-feasibility result; use C.32.MWA.PP for placement, versioning, responsibility or failure questions only when the combined arrangement changes the decision.
“Use the same checklist for every subject.”Ask only applicable questions but preserve the common result positions needed by the decision.
“More evidence is always safer.”Select evidence by consequence and claim; stop when the bounded decision can be made on sufficient grounds.

A.3.1.QM:9 - Consequences

Subjects can be excluded early when a relevant criterion rules out their use; promising accounts remain usable without ontological promotion, and local handoffs become inspectable. Architecture comparison uses the retained subjects and unresolved combined questions.

The cost is keeping the different conditions visible even when a project needs one overall choice. Several qualified individual results may still leave no acceptable synthesis.

A.3.1.QM:10 - Rationale

Individual suitability and whole architecture answer different questions. A Method can be usable alone yet overload a shared Agent when combined with others. A candidate account can be useful evidence for design while failing Method identification. Keeping the individual and architecture results separate protects both cheap stops and escalation when combined questions remain.

A.3.1.QM:11 - SoTA-Echoing

SourceRetained contributionUse boundary
Henderson-Sellers and Ralyté, Situational Method Engineering reviewSituational construction, selection, and adaptation questions.Source-local fragment and process ontologies do not determine FPF subject status.
Daalhuizen and Cash, Method Content TheoryGoal, procedure, rationale, framing, and mindset questions relevant to individual content and use.These variables do not become universal qualification dimensions or Method parts.
Gericke, Eckert, and Stacey, Elements of a design methodIntended use, scope, representation, procedure, tool, ecosystem, and adaptation conditions.Conceptual elements guide questions; current project evidence supplies the verdict.

Revisit an individual qualification when its conclusion turns out to depend on a whole structure, or when a finding from C.32.MWA.PP exposes an individual condition that can be checked before comparing whole alternatives.

A.3.1.QM:12 - Relations

  • C.39.RQ or an applicable domain result supplies situational criteria; A.3.1.DR or another lawful route supplies identified Methods/accounts and dependency slices. Neither named predecessor is compulsory when equivalent content exists.
  • A.3.1 alone governs Method identification. A.3.1.QM does not admit Methods.
  • C.32.MWA.PP receives retained subjects only when combined Method, Work, allocation, support, description, subject, or cultural structures change the decision.
  • B.1.5.CM resolves a proposed whole; A.3.1.QM qualification supplies no whole identity, compatibility, or methodPartOf fact.
  • C.11 or the applicable domain decision Method consumes the bounded individual results when a choice is needed.
  • C.18 supplies candidate generation when needed; G.5 supplies bounded Method-family and selector results.

A.3.1.QM:End

A.3.1.WT - Design and Interpret a Method Work Trial

Type: Method pattern Status: Stable

A.3.1.WT:0 - Use This When

Use this pattern when a Method or candidate Method account is ready for a trial in actual Work and the next decisions need observations from named situations. Begin with one trial question: what must be learned from actual Work for a later coherence, fit, transfer, or worth decision?

The first useful result is an account of the selected trial Work and observations. It names the subject and its status, the situation-selection reason, the task and any available plan, the Work that occurred, its performers and enacted admitted Methods, relied-on Systems and capabilities, observations, gaps, and the later decision that may use them. A result that returns missing-performed-work is useful when the trial remains only planned.

Here trial is Plain practice wording for intentionally selected Work and observation. It is not a new subtype of U.Work, a Method admission, an evaluation result, or a claim that the situation statistically represents a population.

Do not use this pattern to declare description coherence, situational fit, transfer, practical worth, capability, causal contribution, or general effectiveness. It returns evidence for separately governed judgments, including A.3.1.CC coherence, A.3.1.FT fit or transfer, and C.11.MV practical worth.

A.3.1.WT:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
trial questionOne evidence question whose answer can change a named later decision.“Try the method” is not yet a bounded question.
representative situationA situation selected because stated characteristics match the named current-use question.The word does not imply random sampling, population coverage, or transfer.
discriminating situationA situation selected because one changed condition can expose a claimed limit, burden, or failure.Difference alone is insufficient; state which claim the changed condition can test.
WorkPlanIntended performers, tasks, Methods, situations, observations, and stops.A plan, script, simulation description, or scheduled demonstration is not performed Work.
admitted WorkOne dated Work occurrence admitted under A.15.1 from its performers, action history, enacted Method, temporal extent, and required containing-System relation.A report, trace, attendance record, or output can support the claim but does not create the occurrence.
candidate-account trial branchActual Work is admitted separately while claims in a candidate Method account are compared with observations.The candidate whole is not said to have been enacted. Name each independently admitted Method followed and its grounded enactsMethod relation.
capability inputA claim about a holder System, Work family or result class, operating envelope, measures, qualification or currentness window, and evidence used for reliance.Training, availability, assignment, permission, authority, or one success does not substitute for it.
trial evidenceOccurrence-level observations, source relations, burdens, adaptations, results, and gaps qualified for named later uses.It is not itself coherence, fit, transfer, worth, contribution, or causal proof.

A.3.1.WT:1 - Problem Frame

Method trials are often easiest to describe after the fact: a team used some material, produced a result, and reported value. That compression hides what Method was admitted, which Work occurred, who performed it, which support conditions were present, what changed, and which conclusions the observations can support.

Selecting only convenient success cases can miss conditions that change the outcome. A Method may look usable in a familiar task and fail when feedback is closed-loop, information is incomplete, capability is stale, or a required relation is absent. Representative and discriminating situations therefore serve different purposes and must be selected for an explicit later question.

A.3.1.WT:2 - Problem

A planned trial can be reported as performed Work. A candidate whole can be reported as enacted because some constituent activities occurred. Training completion can be reported as capability, tool logs as Work, immediate self-reports as lasting results, and one favourable occurrence as evidence of transfer or effectiveness.

These moves produce a positive story but weak evidence. Later reviewers cannot recover the actual occurrence, compare situations, separate Method claims from support conditions, or find the missing evidence that should stop a broader judgment.

A.3.1.WT:3 - Forces

ForceTension
Real WorkNatural Work exposes practical burdens, while uncontrolled conditions complicate attribution.
Deliberate discriminationChanged conditions can reveal a limit, while an artificial stress case may not answer the current-use question.
Status preservationCandidate claims need testing, while useful Work must not be reported as enactment of an unidentified Method whole.
ObservabilityLater decisions need traceable observations, while instrumentation and reporting can burden or distort Work.
CapabilityPerformer ability can change the result, while training or one success invites premature capability claims.
Failure valueFailure can localize a correction, while a preference for a favourable narrative can hide it.
Evidence reachSeveral occurrences can strengthen a local account, while they may not establish contribution, causality, transfer, or practical worth.

A.3.1.WT:4 - Solution

A.15.1 identifies performed Work and A.10 governs a claimed evidence use. The trial construction below determines which Work, variation, observation and stopping condition can answer the unresolved Method question. Its result is distinct from coherence, transfer and comparative worth; reuse a matching existing observation before commissioning a trial.

Select situations from the later evidence questions, use matching observations of existing Work or arrange and observe a new trial, preserve every subject’s status, and return occurrence-level evidence with explicit gaps and limits on the conclusions it supports.

A.3.1.WT:4.1 - Pattern-Use Unfolding

  1. Name the later decisions and trial questions. Separate the questions that may feed A.3.1.CC coherence, A.3.1.FT situational fit or transfer, and C.11.MV practical worth. Do not hide several conclusions inside “does the Method work?”.
  2. Preserve the subject branch. Identify the admitted Method under A.3.1, or keep the proposed whole as a candidate account. In the candidate branch, state which candidate claims are being compared and which Methods, if any, are separately admitted and may be enacted.
  3. Select a representative situation when the trial question needs one. Name the intended-use characteristics that matter to the question: task purpose, development phase, technical or domain conditions, performer population, holder capabilities, participating Systems, direct relations, constraints, and qualification window. State why this situation covers the current question without claiming population representativeness.
  4. Select a discriminating situation when the decision needs one. Change or seek one condition whose outcome can show whether a live claim holds in that situation: unfamiliar technical coupling, another domain, missing support relation, changed capability envelope, stale material, or another named alternative. State the claim that could fail. Do not require every trial to contain an artificial stress case.
  5. Keep intention and performance distinct. For a new trial, write the WorkPlan with intended tasks, performers, admitted Methods, support conditions, observation points, protected conditions, burdens to record, stop rules, and the later use of each observation. For existing Work, recover any available plan and leave unsupported claims about prior intentions unresolved. Distinguish planned or described activity from what was performed. A performed simulation or demonstration may itself be admitted as Work under §4.1(7); distinguish what was actually performed from what was only represented or planned.
  6. Check capability and support inputs separately. When reliance on capability changes interpretation, identify the holder System, Work family or result class, operating envelope, measures, qualification or currentness condition, and evidence. Recover only A.15.8.MS material, access, tool, provider, feedback, and decision conditions supported for the relevant task rows; preserve retained candidates, split boundaries, untested conditions, and gaps rather than treating them as configured inputs.
  7. Admit only Work that occurred. For each occurrence, recover every performer System and its A.13 basis, the action history, at least one admitted Method followed, temporal extent, and required containing-System relation under A.15.1. Use F.6 through the same obtaining A.13 assignment only when precise assignment-bound attribution is needed. Add System use, operation binding, affected referent, resource use, or result relations only when the claim needs them and their own predicates obtain.
  8. Record conditions and departures. For each Work occurrence, record the situation, relied-on Systems and direct relations, holder capabilities used in interpretation, departures from any available WorkPlan, adaptations, burdens, stops, domain results, and observations. Keep the domain result, report, log, and evidence-use relation separate from Work.
  9. Qualify the evidence reach. Distinguish direct observation, participant report, source interpretation, observed association, contribution claim, and causal claim. Return the supported level needed by the receiving claim and name missing comparison, temporal, capability, relation, or alternative evidence.
  10. Return evidence by later use. For each selected receiving question, send description or relation evidence to A.3.1.CC, the situation evidence and any comparison needed for the selected fit or transfer question to A.3.1.FT, and results, burdens, alternatives, side effects, and evidence limits to C.11.MV. Return missing-performed-work, missing-method-admission, missing-capability-basis, missing-direct-relation, or the named missing premise when a required condition is absent.

A.3.1.WT:4.2 - Record the Result

Result positionRequired content
trial useLater decision, bounded trial question, qualification window, and stop.
subject statusAdmitted Method, or candidate account plus each separately admitted Method whose enactment is claimed.
situationsRepresentative or discriminating situations selected for the question, selection criteria, any relevant matched or changed conditions, and the question or claim each addresses.
plan baselineAvailable plan for existing Work, or intended Work for a new trial, with performers, Methods, support conditions, observations, burdens, protected conditions, stop rules and any missing plan basis relevant to the question.
performed WorkEach admitted Work occurrence, its performers, enacted admitted Methods, temporal extent, containing System, and departures from any available plan.
relied-on conditionsHolder capabilities, Systems, Agent-performed Work, direct relations, access, assignments, permissions, authority, tools, providers, and support conditions that obtain or remain missing.
observationsDomain results, burdens, adaptations, failures, participant reports, direct observations, and their source or evidence-use relations.
reach and gapsSupported observation level, missing evidence, material limits on contribution or causal claims, and conditions that would reopen the slice.
returnOccurrence-level evidence for the selected A.3.1.CC, A.3.1.FT or C.11.MV question, or a supported lower result.

Keep these distinctions in the account and its referenced records. A table is useful when several occurrences need comparison; a single account need not use one row per position.

A.3.1.WT:4.3 - What Changes in Practice

Teams distinguish a planned or reported trial from the Work that occurred. They can point to that Work, the admitted Method that was enacted, the conditions on which the result depended, and the named later question each observation can answer.

A failed or incomplete occurrence remains useful. It can expose a description defect, a representation difficulty, a missing support relation, a capability condition, or a situation boundary without being inflated into a universal verdict on the Method.

A.3.1.WT:4.4 - Constructed Trial Case

This constructed case illustrates how later checks can reuse the same Work while reaching their own conclusions.

M-Unit-Review-1 is admitted for reviewing temperature-sensor calibration reports before release. Its current description tells the reviewer to identify every source unit, normalize values, compare them with the declared tolerance, and stop on an unresolved mismatch. WP-ME11-1 plans two review tasks for the same week. S-Rep-1 is a current same-unit report of the ordinary kind. S-Disc-1 keeps the product, decision, reviewer, description, and support fixed but introduces a Celsius/Kelvin mismatch; it is selected because the live claim is that the Method lets this reviewer expose a unit mismatch before release.

The interpretation relies on CAP-R17-1: holder Reviewer-17; calibration-report-review Work family; temperature-sensor-report envelope; measure “four of four seeded unit cases detected with description edition 4”; current through day D30; qualification record QR-R17-1. The qualification, assignment, permission to inspect the report, and release authority remain different facts. The trial also records description edition 4 and the manually retrieved conversion table as A.15.8.MS support inputs.

Two occurrences then happen and are admitted separately. W-Rep-1 is performed by Reviewer-17 inside Calibration-Team-A from 10:03 to 10:10, enacts M-Unit-Review-1, accepts the same-unit report, and records seven minutes of review burden. W-Disc-1 is performed by the same System in the same containing System from 11:14 to 11:26, enacts the same admitted Method, normalizes the Celsius/Kelvin values before comparison, detects an unresolved mismatch, stops the release decision, and returns the report for correction; it records twelve minutes and one conversion-table lookup. The WorkPlan, two Work occurrences, domain decisions, timing record, and observation account remain separate.

Later useEvidence returnedStop retained
A.3.1.CC coherenceThe two occurrences identify the description edition and the operations followed; neither exposed an internal contradiction in this slice.A.3.1.WT does not conclude that the whole MethodDescription or Method construction is coherent.
A.3.1.FT fit or transferThe matched pair records one changed situation condition and the resulting task observations for one current holder.One discriminating occurrence establishes no transfer to another holder, domain, tool, or qualification window.
C.11.MV practical worthThe domain decisions, seven- and twelve-minute burdens, lookup, and stop are available for comparison with named alternatives.A task pass establishes neither net worth nor causal contribution.

If W-Disc-1 had not occurred, return missing-performed-work; if its enacted-Method relation or relied-on capability basis were absent, return that missing premise. A favourable plan, simulated trace, or qualification record cannot replace the occurrence.

A.3.1.WT:5 - Archetypal Grounding - SSFD Workplace Projects

The automotive SSFD programme supplies reports and review evidence about actual workplace projects without supplying a universal effectiveness claim. More than 300 engineers participated in a three-year transfer programme; training was followed by supported four-to-six-month workplace projects. Seventy-two of the first 100 reviewed project reports recorded SSFD use, and 41 contained enough detail for deeper analysis. Across those 41, the study reports 95 examples of evidenced individual benefits while distinguishing direct and indirect contribution.

The published paper supplies report evidence. A local application admits a particular project Work occurrence only from the records required by §4.1(7); otherwise retain the report and name the missing occurrence or performer basis. The slices below distinguish possible answers to the later questions without admitting Work by citation.

A.3.1.WT:5.1 - Preserve the Status Branch

Before using the replay, establish whether SSFD is an admitted Method for the current FPF use. If it is, each supported project occurrence may be tested for its own obtaining enactsMethod relation. If it is not, admit the workplace Work independently, retain the SSFD account as a candidate, and name the independently admitted Methods whose enactment relations obtain. The report statement “used SSFD” does not perform either admission automatically.

A.3.1.WT:5.2 - Representative and Discriminating Slices

SliceReported project facts usedEvidence returnedStop retained
Project 11The report concerns functional analysis of a new by-wire steering system and records 48 failure modes for four system functions, 44 new requirements and design rules, 44 test cases for individual systems, and 33 requirements and test cases for the overall system.One bounded application account for checking whether description, representation, and support claims were usable in that project situation, plus the reported results and burdens available from the source.Do not infer that every programme participant had the same capability or that the reported benefits came from SSFD alone.
Project 32The report exposes difficulty representing the relation between a closed-loop sensor and controller.A discriminating representation difficulty for A.3.1.CC and an unlike-situation comparison for A.3.1.FT. A.3.1.CC uses the direct representation governor for the affected action and C.37 when a selection question remains; when a Method-specific cross-use profile is needed, it checks the affected action and cross-use dependency under C.37.MP:4.2. The report establishes neither selection result by itself.Do not turn the difficulty into general Method failure or claim that Project 11 supplies the counterfactual.
41-report evidence setThe review identifies 95 examples of evidenced individual benefits across business results, process improvement, and product-development-team capability improvement, while separating direct and indirect contribution.Bounded report and review evidence for later comparison of results, burdens, and evidence strength in C.11.MV.Counts and source classifications do not establish causality, universal superiority, transfer, or current capability for every participant.

The useful A.3.1.WT result is therefore not “SSFD works”. It is a set of reported workplace-project accounts, situation and support conditions, observed representation difficulties, reported results and burdens, evidence-source qualifications, and explicit gaps for three separate later judgments.

A.3.1.WT:5.3 - EC-417 Early Stop

The full EC-417 application supplies the receiving problem, alternatives, calculations and the distinct limits used below.

In EC-417, the three-release statement remains a WorkPlan. The three named-user retrieval, tailoring, and selection-support occurrences from A.15.8.MS establish only those support tasks; they do not perform a release or enact the candidate whole C-EC-Release-v2.

For a release trial, apply §4.1(6–9) to the release’s own occurrence, support, evidence and authority facts. The observed support tasks do not supply that release Work; until its basis is recovered, return missing-performed-work. Even after a release is admitted, keep C-EC-Release-v2 as a candidate and send the occurrence evidence to the selected A.3.1.CC, A.3.1.FT or C.11.MV question.

A.3.1.WT:6 - Bias-Annotation

BiasLikely driftRepair
plan-completion biasPlanned or represented activity is reported as performed trial Work.Admit each actual Work occurrence separately; otherwise return missing-performed-work.
candidate-laundering biasConstituent activity is reported as enactment of the candidate whole.Preserve the candidate account and name only separately admitted enacted Methods.
success-selection biasConvenient positive occurrences stand in for the intended situation family.State the situation-selection criteria and select a discriminating situation when the later question needs one.
instrument biasLogs, reports, or telemetry are treated as the Work or result.Keep the occurrence, result, record, and evidence-use relation separate.
capability inflationTraining or one success becomes a holder capability claim.Require the A.2.2 holder, Work family, envelope, measures, window, and evidence.
causal inflationReported benefit or association becomes Method-caused effect.State the observation level and missing comparison or causal basis.
trial-judgment collapseOne trial record decides coherence, fit, transfer, and worth at once.Route evidence to A.3.1.CC, A.3.1.FT, and C.11.MV according to the selected receiving questions.

A.3.1.WT:7 - Conformance Checklist

  • One later decision and bounded trial question are stated before the trial design.
  • The Method is admitted, or the proposed whole remains a candidate account throughout.
  • Every claimed enacted Method is independently admitted; no candidate whole is said to be enacted.
  • Situation-selection criteria are named, and every discriminating situation states the claim it can distinguish.
  • Plans, reports, traces and results remain distinct from Work; for a simulation or demonstration, distinguish what was actually performed from what was only represented or planned.
  • Each claimed Work occurrence independently satisfies the admission basis in §4.1(7).
  • Capability, System use, assignment, permission, authority, support, operation binding, and result relations are asserted only from their own bases.
  • Conditions, deviations, adaptations, burdens, observations, and domain results are recorded per occurrence.
  • Direct observation, self-report, association, contribution, and causality are not merged.
  • The result separates any selected A.3.1.CC, A.3.1.FT and C.11.MV uses and supplies evidence or gaps without claiming their judgments.

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

Anti-patternRepair
“The rehearsal ran, so the Method was trialled.”Recover actual Work and its enacted admitted Method; otherwise keep the rehearsal at its supported status.
“The team enacted the candidate Method.”Admit the Work, preserve the candidate account, and name only independently admitted Methods whose enactment relations obtain.
“Everyone was trained, so capability was controlled.”Record training separately and recover the holder capability input used in interpretation.
“The log proves the task occurred and succeeded.”Use the log as evidence for independently admitted Work and a separately established task result.
“Most reports were favourable, so the Method transfers.”Send the occurrence evidence and situation differences to A.3.1.FT; do not make the transfer judgment here.
“Reported benefit proves the Method caused the outcome.”Record the report and its contribution category, then return the missing causal basis.

A.3.1.WT:9 - Consequences

Trial Work produces inspectable evidence. Failures and missing premises survive as useful results, and later assurance decisions can compare the same occurrences without changing their identity or truth status.

The cost is more explicit occurrence recovery and narrower conclusions. Projects must record the performer, enacted Method and situation, together with the capability, support, direct relations, burdens and source limits that affect the receiving question, and they may finish a costly trial with a precise gap instead of a favourable verdict.

A.3.1.WT:10 - Rationale

Actual Work is the shared empirical base, but coherence, fit, transfer, worth, capability, contribution, and causality are different claims. Keeping them separate lets the same occurrence inform several decisions without allowing one decision to inherit another’s conclusion.

Representative situations answer typical-use questions; discriminating situations test a stated difference or boundary. Select either or both according to the receiving question. Their selection does not create statistical representativeness or a universal situation taxonomy.

A.3.1.WT:11 - SoTA-Echoing

SourceContributionBoundary and practitioner implication
Yildirim, Campean, and Uddin, function-modeling evaluation in industry practiceWorkplace projects, varied application situations, reported limitations, later report analysis, and separation of direct and indirect contribution supply trial-design and evidence-recording cues.One automotive OEM, SSFD used within a broader methodology, and retrospective reports establish neither SSFD-only causality nor universal transfer.
Tsai, Zdravkovic, and Söder, DBE-design Method action researchRepeated plan-perform-evaluate cycles in an operating health-services ecosystem provide an unlike-domain example of validation actions.The evaluation is ex ante and case-specific; it establishes neither long-term effect nor transfer to the other elicited domains.
Faludi, Yiu, and Agogino, empirical tests of sustainable-design MethodsExplicit alternative Methods, several industry situations, participant Work, activities, and immediate value reports supply a bounded comparison input.Immediate self-report establishes neither long-term product results, causal superiority, nor the effectiveness of recombined variants.

A.3.1.WT:12 - Relations

  • B.1.5.CM supplies an admitted Method or a status-preserved candidate account and may supply a realization or trial plan; it does not supply performed Work.
  • A.3.2.DE supplies MethodDescription content or candidate-account content for the trial question. A.15.8.MS supplies supported material and task conditions or a retained configuration set, split boundary, or gap; A.3.1.WT consumes only the obtaining support inputs and preserves every unresolved status. Neither pattern establishes trial Work or its result.
  • RMP.10 may supply a reconstructed candidate account and a trial question while preserving the candidate branch.
  • A.3.1 governs Method admission; A.15.2 keeps the WorkPlan separate; A.15.1 governs each Work occurrence; A.2.2 governs capability inputs; A.10 governs relied-on evidence paths.
  • A.3.1.CC consumes evidence for construction and description coherence, A.3.1.FT consumes situation evidence and any comparisons needed for the selected fit or transfer question, and C.11.MV consumes results, burdens, alternatives, and evidence strength for practical worth. None of those conclusions is returned by A.3.1.WT.

A.3.1.WT:End

A.3.1.CC - Check the Coherence of a Method Claim

Type: Method pattern Status: Stable

A.3.1.CC:0 - Use This When

Use this pattern when Method construction commitments, a MethodDescription, a selected representation, an enactment-support result, or trial evidence no longer agree well enough for a named use. Begin with the possible contradiction and the decision it blocks: which maintained claim may be wrong, incomplete, stale, or unsupported?

The first useful result is a bounded coherence finding. It names the claim being checked, its maintained owner and edition, the comparison basis, the observed agreement or defect, and any correction or stop required. An owner-not-recoverable or missing-comparison-basis result is better than declaring the whole Method incoherent.

Here coherence is Plain practice wording for checking whether claims relied on for the declared use agree where they should. It is not a new FPF relation, Method admission, fit result, effectiveness result, or universal consistency proof.

Do not use this pattern to decide whether the Method fits another situation, transfers, is worth keeping, caused a result, or is preferable to alternatives. A.3.1.FT owns fit and transfer; C.11.MV owns practical worth. A favourable trial can supply evidence for A.3.1.CC without making its conclusion.

A.3.1.CC:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
construction commitmentA maintained B.1.5.CM requirement, component decision, operation declaration, or obtaining-relation claim about the Method under construction.It is not a sentence in a later description merely because the sentence refers to it.
MethodDescription claimA claim in one MethodDescription edition for a named use, including coverage, omission, correspondence, evidence limit, or stop. A.3.2.DE can construct or repair the description when needed.Description agreement does not admit a Method or establish that Work occurred.
Method representation profileA C.37.MP result for several unlike Method-related actions. It contains one complete C.37-bearing row per action and a separate cross-use result naming the shared Method source, correspondences, conflicting omissions, edition relations, keep-separate decisions, and changes that reopen several rows.It does not select a representation for an arbitrary entity, make row colocation a composition result, or establish view, mathematical-lens, publication, or structure conformance by itself.
support claimOne A.15.8.MS task, configuration, A.22 proposal or selection position, collection, membership, edition, publication, direct-relation, test, or reliance claim.A repository or successful tool task cannot repair a contradiction in another maintained result by being convenient.
trial evidenceA.3.1.WT occurrence-level observations and gaps qualified for a named later use.An observation can bear on a claim. Any correction belongs in the maintained result that owns that claim.
coherence findingA bounded agreement, contradiction, missing-information, failed-declared-conformance, or currentness result about one named claim.“The Method is coherent” is too broad unless every claim relied on and its qualification window are in scope.
maintained ownerThe maintained result whose claim is being checked and where any warranted correction belongs: B.1.5.CM, A.3.2.DE, C.37.MP, one A.15.8.MS result, or another named governor.The file that displays a claim is not necessarily its owner.
declared conformanceA conformance claim with its named scheme, criteria, represented entity, use, and qualification window.Passing description-side conformance does not establish Method fit, Work performance, or worth.

A.3.1.CC:1 - Problem Frame

A Method can be internally plausible while its description omits a required stop, a representation hides a relation needed by its use, or a support route serves an obsolete edition. Trial Work can expose the mismatch, but the mismatch has to be located. Otherwise every defect is blamed on “the Method”, or every observed failure is pushed into the document that happens to be easiest to edit.

The practical question is narrower: which claim was relied on, what should it agree with, what evidence bears on that agreement, and which maintained result owns the smallest correction?

A.3.1.CC:2 - Problem

Coherence checks often collapse several questions. Construction conformance is treated as document completeness; description consistency is treated as practical fit; a failed representation is repaired by changing Method semantics; a stale support edition is called a Method defect; or one trial success is taken to verify the whole package.

This makes correction expensive and unsafe. Several maintained results are changed together, the original contradiction becomes unrecoverable, unaffected claims lose their evidence status, and later fit or worth decisions inherit a verdict that A.3.1.CC never established.

A.3.1.CC:3 - Forces

ForceTension
Local correctionRepairing the claim at its owner preserves unaffected claims, while dependent claims may also need rechecking.
Construction and descriptionThey must correspond for relied-on uses, while they remain different results with different tests.
RepresentationA representation must expose what its use needs, while omission can be deliberate for another use.
Trial evidenceActual Work can reveal contradictions, while failure can also come from situation, capability, support, or another direct relation.
ConformanceNamed schemes can make checks repeatable, while scheme passage can be mistaken for practical adequacy.
CurrentnessEditions and sources change, while a once-valid claim may remain syntactically consistent and practically stale.
Candidate statusCandidate accounts benefit from correction, while coherence must not launder them into admitted Methods.

A.3.1.CC:4 - Solution

This is a claim-to-basis comparison for Methods, descriptions, representations and support. Use A.10 for the relied-on evidence and each subject pattern for its positive claim. The local construction below identifies the consequential contradiction or missing basis and returns it to the maintained explanation that can be corrected.

Check one claim relied on for the named use against its declared basis, classify the result, and return any correction only to the maintained result that owns the defeated claim. Recheck the repaired claim while preserving every unaffected status and open question.

When the parts appear locally consistent but the required whole result still has no adequate explanation, use B.1.5.EW:4.3–4.5 to work back from that result to the constituent contributions and their connections. That supplier covers actual work and proposals for future work; it can expose a required operation or connection whose account is missing. Bring the contribution, dependency and supporting basis into step 1 below. Then distinguish a missing construction, an omitted description and an unsupported claim before choosing a correction owner. Agreement among the available parts alone does not settle the whole-result question.

A.3.1.CC:4.1 - Pattern-Use Unfolding

Use steps 4–8 only for the claims and evidence that the named coherence question depends on. Use steps 10–11 only when the finding warrants a correction; agreement or an unresolved gap can be returned at step 12.

  1. Name the blocked use and possible contradiction. Identify the reader or decision, the claim needed, its qualification window, and what would count as agreement, contradiction, missing information, or a stop. Do not begin with “verify the Method”.
  2. Preserve the subject and status branch. Identify the admitted Method under A.3.1, or keep the proposed whole as a candidate account. Keep Work, WorkPlan, description, representation, support, evidence, publication, and structure claims at their current statuses.
  3. Recover the maintained claim and owner. Record the claim text or predicate, owning result, edition or occurrence, source or construction basis, intended use, and currentness condition. If ownership cannot be recovered, return owner-not-recoverable before editing several carriers.
  4. Check construction claims at B.1.5.CM. Test construction requirements, component decisions, operation declarations, and obtaining-relation claims separately. Cite the governing FPF predicate where needed rather than recreating its admission test. A failed construction claim returns to that B.1.5.CM result.
  5. Check MethodDescription claims at A.3.2.DE. Test coverage, internal consistency, correspondence with admitted Method claims, navigation for the named use, stated evidence limits, omissions, stops, and any declared description-side conformance. Do not make section count or scheme passage a proxy for useful coverage.
  6. Check representation-use results at the right owner. Start from the affected representation result and its direct governor. Recover a C.37 selection account when the claimed use relies on one or needs a cross-kind selection account. When the claim concerns a Method-specific organization of several uses, recover the complete C.37.MP profile, including its shared source and separate cross-use result. Test the affected claim group and any profile relation that depends on it. The direct FPF governor owns view, mathematical-lens, publication, and structure conformance; if a governed result fails, return that lower result and reopen only the affected use result and cross-use relations that depended on it.
  7. Check support results at A.15.8.MS. Use A.15.8.MS’s result distinctions to identify the support claim being checked and the result that owns it. Test that claim against the evidence and return any needed repair there; one defeated claim is not a verdict on the whole support configuration.
  8. Use trial evidence to check the maintained claim. From A.3.1.WT, recover the actual Work occurrence, performer, enacted admitted Method, situation, capability and support conditions, direct relations, result, burden, observation source, and evidence reach. Ask which named claim the observation bears on. A success or failure does not by itself identify the owner.
  9. Classify the finding. Distinguish: agreement-within-window; contradicted-claim; missing-information; failed-declared-conformance; stale-source-or-edition; and owner-not-recoverable. Do not turn uncertainty into contradiction or a local defect into a whole-Method verdict.
  10. Select one correction owner. Return the smallest correction to B.1.5.CM construction, A.3.2.DE description, one direct C.37 use row, one complete C.37.MP Method representation profile, one A.15.8.MS result, or the direct governor of a lower representation result. If one observation defeats several independent claims, create separate findings with separate owners; do not copy one vague correction into every upstream result.
  11. Repair and repeat the same check. Preserve unaffected claims, statuses, evidence, and windows. Recheck the repaired claim against the same basis. If the use, subject, source, edition, or criteria changed, start a new coherence use instead of calling the old check passed.
  12. Return the bounded result. State the verified claim, correction or gap, owner, affected downstream uses, preserved claims, material use limits, and reopen condition.

A.3.1.CC:4.2 - Record the Result

Result positionRequired content
coherence useBlocked decision, reader, relied-on claim, qualification window, agreement and stop conditions.
subject statusAdmitted Method or candidate account, plus separately identified Work, WorkPlan, description, representation, support, and evidence results in scope.
maintained claimClaim or predicate, owner, edition or occurrence, source or construction basis, intended use, and currentness.
comparison basisConstruction requirement, description claim, selected representation rule, support premise, trial evidence, or declared conformance criterion used.
findingAgreement, contradiction, missing information, failed declared conformance, stale source or edition, or missing owner; include the evidence reach.
repair routingOne maintained result to reconsider, smallest correction, unaffected claims and statuses, and downstream uses that must be rechecked.
rerunSame-check result after repair, or the changed use or basis that requires a new check.
returnVerified bounded claim, corrected claim, or named gap; material use limits and reopen condition.

Use the existing claim and finding records or a concise account that preserves these distinctions; the positions do not require a separate form.

A.3.1.CC:4.3 - What Changes in Practice

Teams stop repairing the nearest document or declaring the whole Method inconsistent. They can identify the defeated claim, distinguish construction from description, representation, support, and evidence, and send one correction to its maintained owner.

The correction becomes cheaper to review and safer to reuse. Unaffected claims keep their status, and later fit and worth judgments receive a precise repaired input rather than a package-wide confidence label.

A.3.1.CC:4.4 - Minimal Constructed Coherence Replay

Continue the constructed A.3.1.WT trial of admitted M-Unit-Review-1. Construction result CCR-UR-1 states that unit identification and normalization precede tolerance comparison. MethodDescription edition 4 says the same and exposes the unresolved-mismatch stop.

Only one current action is at issue: Reviewer-17 must use the flow representation to guide pre-release unit review. Direct use result C37-UR-Flow-4 therefore takes the C.37 exit rather than opening C.37.MP. It returns to that Method and description edition, requires unit identification, normalization before tolerance comparison, the comparison branch, and the unresolved-mismatch stop, and uses governed representation result REP-UR-Flow-4.

Claim: that representation exposes those operations in order for the named review action. A.2.4 classifies the intended preparation use; A.10 path P-UR-Flow-4 carries the current-edition premise with RelianceDisposition=pass for the review window. Receiving task criterion UR-PreRelease-Guide-4 permits use only while those claims remain exposed. The row omits unrelated support-edition detail, preserves Method, description, representation, and Work status, is select for that action, and returns a missing exposure to the direct representation governor and this use row.

A.15.8.MS supplies the current conversion table used in W-Disc-1.

The trial evidence records that Reviewer-17 normalized the Celsius/Kelvin values before comparison and stopped the release decision. Inspection of REP-UR-Flow-4, however, shows identification followed directly by tolerance comparison; the normalization operation is absent. The finding is not “the Method is incoherent”. The construction claim, description claim, support edition, and observed Work agree within this slice. The contradicted claim is the C37-UR-Flow-4 exposure claim for its action; no C.37.MP profile exists or is needed for this one-use case.

Return CORR-C37-UR-1: revise governed representation result REP-UR-Flow-4 and its direct use row to expose normalization and the unresolved-mismatch branch, or narrow the row’s action, required claim, and omission account. Preserve M-Unit-Review-1, MethodDescription edition 4, W-Disc-1, its task result, and the conversion-table support result. Recheck the same exposure claim after repair. Do not infer fit or worth from the successful Work occurrence.

If the observed defect were instead…Owner to reconsiderResult not to change automatically
The admitted construction omitted any normalization requirement while the named problem required one.The affected B.1.5.CM construction or requirement result.A.3.2.DE and every affected direct C.37 use row or complete C.37.MP profile until their own action claims and dependent cross-use relations are checked against the changed construction.
MethodDescription edition 4 reversed the declared operation order while construction and Work supported the original order.The affected A.3.2.DE description claim and edition.Method identity and the Work occurrence.
The retrieved conversion table used a stale scale while construction, description, and representation were correct.The affected A.15.8.MS edition, retrieval, or named-user task result.B.1.5.CM construction and every unaffected direct C.37 use row or complete C.37.MP profile.
The source cannot show which of those positions is wrong.owner-not-recoverable with the missing comparison basis.All maintained results until evidence distinguishes them.

A.3.1.CC:5 - Archetypal Grounding - Representation Difficulty in SSFD

The SSFD workplace evidence reports that Project 32 had difficulty representing the relation between a closed-loop sensor and controller. This is a useful coherence trigger because the difficulty may concern Method semantics, a MethodDescription claim, a selected representation, support material, or a situation-specific applicability boundary.

The report does not by itself establish a defect in a maintained claim. Recover the receiving action, the claim that may be contradicted and its complete use basis through §4.1(3,6) before choosing a correction owner.

For the sensor-controller representation use, start from the direct representation result and its governor. Inspect C.37 when the use relies on its selection account or that account is needed. If the claim concerns a Method-specific organization of several unlike actions, inspect the complete C.37.MP profile identified in §4.1(6) and locate the affected action and dependent cross-use relation. The report does not establish that profile by itself.

If the facts locate a failed exposure claim, return the owning row and only the cross-use relations that depended on it; if they locate a construction or description contradiction, return it to B.1.5.CM or A.3.2.DE. If the report cannot distinguish the owner, return owner-not-recoverable rather than calling SSFD incoherent.

Project 11 records a different application and many reported results. It is neither the counterfactual for Project 32 nor proof that the same representation claim was coherent there. The 41-report set and its 95 reported benefit instances concern later evidence use; they do not erase the Project 32 difficulty or establish practical worth inside A.3.1.CC.

A.3.1.CC:5.1 - EC-417 Early Stop

The full EC-417 application supplies the receiving problem, alternatives, calculations and the distinct limits used below.

C-EC-Release-v2 remains a candidate account and the three-release statement remains a WorkPlan. A.3.1.CC may check current description, representation, A.15.8.MS task, collection, edition, reliance, permission, application, Work, result-binding, and proposed-organization claims against their own bases. It must not verify planned releases as performed Work or call the candidate whole coherent as a Method.

For every correction, name the maintained position. A stale method-base edition returns to that edition result. A failed viewpoint rule returns the lower episteme and failed E.17.0 rule to their direct governor. Recheck any C.37 use result that relied on the failed result. For a C.37.MP profile, follow §4.1(6) and recheck only its dependent cross-use relations. A missing A.22 selection-use basis remains the already named gap. Keep the observed support results separate from the missing tailoring definition and untested permission/authority stop; none supplies release evidence.

A.3.1.CC:6 - Bias-Annotation

BiasLikely driftRepair
package-coherence biasOne local contradiction becomes a verdict on the whole Method package.Bound the claim, use, owner, and window before checking.
document-owner biasThe document displaying a claim is edited even when construction or support owns it.Recover the maintained result and direct governor.
success-verifies-all biasOne favourable Work occurrence verifies construction, description, representation, and support together.Ask which named claim the observation bears on.
conformance-as-performance biasDescription-side conformance becomes fit or effectiveness.Keep scheme passage inside the declared description use.
repair-fanout biasThe same correction is copied into every upstream carrier.Route each contradicted claim to one owner; create separate findings only for separate claims.
source-authority biasA published report is treated as direct admission and owner identification.Preserve the evidence path and return missing occurrence or owner facts.

A.3.1.CC:7 - Conformance Checklist

  • The blocked use and one claim relied on for that use are named.
  • The Method is admitted or the proposed whole remains a candidate account.
  • Construction, MethodDescription, representation, support, Work, and evidence results retain separate identities and statuses.
  • The claim owner, edition or occurrence, intended use, source, and currentness window are recoverable, or the missing owner or comparison basis is explicitly returned.
  • Any trial evidence used is qualified for the named claim.
  • Agreement, contradiction, missing information, failed declared conformance, staleness, and missing owner are not merged.
  • Every correction returns to one maintained result and preserves unaffected claims.
  • A repaired claim is rechecked against the same basis, or a changed basis starts a new use.
  • The conclusion is limited to the claims checked; any stronger receiving claim retains its separate basis.

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

Anti-patternRepair
“The trial failed, so rewrite the Method.”Identify which maintained claim, if any, the trial evidence contradicts, considering the relevant situation, capability, support and direct-relation conditions.
“The standard checklist passed, so the Method is coherent.”State the declared conformance use and its limits relevant to the intended decision.
“Fix the diagram and the description together.”Determine which claims, if any, are contradicted and route each correction to its owner.
“Project 32 proves SSFD is inconsistent.”Treat the reported representation difficulty as evidence that opens an owner-specific check.
“No contradiction was observed, so coherence is proven.”Return agreement only for the claims, evidence, and window checked.

A.3.1.CC:9 - Consequences

Coherence work becomes a repair-routing practice rather than a package-wide verdict. A practitioner can see which claim failed, why it failed, what remains valid, and which downstream decisions need the repaired result.

The cost is explicit ownership and comparison recovery. Some checks end with a missing owner or missing basis, and a team may have to preserve several plausible defect locations instead of choosing the easiest file to edit.

A.3.1.CC:10 - Rationale

Method construction, description, representation, support, and trial evidence are coupled by use but are not interchangeable. Their claims can agree, disagree, or become stale independently. Returning each correction to one maintained owner protects that independence and keeps coherence separate from Method admission and effectiveness assessment.

The same evidence may support several checks, but its use relation is different in each. Treating evidence as a common source rather than a common verdict lets later fit and worth decisions reuse it without inheriting A.3.1.CC’s scope.

A.3.1.CC:11 - SoTA-Echoing

SourceContributionBoundary and practitioner implication
Ralyté, Koutsopoulos, and Stirna, verification, validation, and evaluation of modeling methodsKeep verification, validation, and evaluation questions separate and use evidence to locate the claim under check.The source is modeling-Method focused and does not supply one universal FPF owner map or prove practical worth.
ISO/IEC/IEEE 24774:2021Use description elements, rules, views, and declared description-side conformance as selectable comparison bases.The standard does not make description conformance a Method admission, fit, or performance result and is not imported as FPF ontology.
Cash, Daalhuizen, and Hekkert, method efficacy and effectivenessPreserve the difference between internal or use-side adequacy questions and practical effect questions.The contribution does not make one successful occurrence decisive.

A.3.1.CC:12 - Relations

  • B.1.5.CM supplies construction commitments and obtaining-relation results; A.3.2.DE supplies MethodDescription claims and use coverage; C.37 supplies one-action representation-use results; C.37.MP supplies complete Method representation profiles for several unlike Method-related actions, with their action rows and separate cross-use result; A.15.8.MS supplies task, support, collection, edition, publication, relation, test, and reliance results. Each remains the owner of its own claim, while a lower representation result remains with its direct FPF governor.
  • A.3.1.WT supplies occurrence-level observations and gaps. It neither identifies the correction owner automatically nor establishes coherence.
  • A.3.1.FT consumes coherent-enough claims and situation evidence for fit or transfer. C.11.MV consumes results and evidence limits for practical worth. Neither conclusion is returned by A.3.1.CC.
  • A.3.1 governs Method admission; A.10 governs claim-bound evidence use; C.2.1 governs episteme and edition identity; E.17.0 governs view conformance; A.22 governs selected structures. Cite the direct governor for every other predicate checked.
  • A.3.1.MV receives a variant question only when a proposed repair changes reusable Method semantics; a document, representation, support, or local Work correction alone does not identify a Method variant.

A.3.1.CC:End

A.3.1.FT - Qualify Method Fit and Transfer

Type: Method pattern Status: Stable

A.3.1.FT:0 - Use This When

Use this pattern when Work has supplied evidence in one or more situations and a practitioner must decide whether an admitted Method fits a named situation, where its applicability stops, or whether a supported claim transfers from a source situation family. Begin with the required result and the conditions of the situation in which the Method will be used. For a transfer question, also name the source situation and the claim whose support is being carried into the receiving situation.

The first useful result is a bounded assessment of fit, an applicability limit, or transfer, with the evidence used and any missing premise. Identify the Method or candidate status, the situation and required result, relevant actual Work, adaptations and evidence reach. Where the question requires comparison, also distinguish source and receiving situations, matched and changed conditions, and material differences in capability, support, domain results and burdens.

Here fit and transfer are Plain practice names for two different decisions. Fit concerns a Method and a bounded situation or situation family. Transfer concerns whether a supported claim survives a stated move from source to receiving conditions.

Do not use this pattern to infer practical worth, causal contribution, general effectiveness, capability, or cultural adoption. A Method can fit and still be a poor choice against current alternatives. C.11.MV owns that comparison. An account is never enacted, and a candidate whole remains a candidate even when separately admitted Work succeeds.

A.3.1.FT:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
source situation familyThe bounded set of source conditions under which the relied-on Method claim has evidence.A project label or industry name is insufficient; state the decision-relevant conditions.
receiving situation familyThe bounded set of conditions in which the practitioner wants to rely on the claim.It is not “everywhere else” or a population inferred from one case.
representative source sliceActual source Work selected because its stated characteristics bear on the current claim.Convenience or success alone does not make it representative.
discriminating unlike situationA receiving or held-out situation whose changed condition can expose a limit in the claim.Difference is useful only when the claim it can defeat is stated.
matched conditionA condition held comparable enough for the declared decision, with its evidence basis.Unrecorded sameness is not a control and does not establish causality.
adaptationA change made in performing or supporting Work for the receiving situation.If reusable Method semantics change, the result opens an A.3.1.MV variant question; it is not evidence for unchanged transfer.
situational fitA bounded result that the admitted Method is usable for the named situation and decision under stated conditions and limits.Fit establishes neither superiority, worth, causal contribution, nor general effectiveness.
transfer resultA bounded result about whether a source-supported claim survives the named change in conditions.A broader situation-family conclusion needs its own support; otherwise return the narrower result or missing evidence.

A.3.1.FT:1 - Problem Frame

Methods are often moved by name: a team says that a Method worked in one project, industry, or organization and applies it to another. The label hides the conditions that mattered—project purpose, development phase, technical problem, performer capability, support Systems, direct relations, adaptations, and the domain result being judged.

The reverse inference can also fail. Any adaptation or local failure is treated as evidence that the Method cannot transfer, even when the changed condition, support defect, or altered Method semantics has not been identified. A useful transfer result must show what stayed the same, what changed, what Work occurred, and what claim survives.

A.3.1.FT:2 - Problem

A favourable source case can be generalized without a discriminating receiving situation. A candidate account can be called enacted. Training or expert help can be hidden inside “same conditions”. A changed representation or operation can be called tailoring even though reusable Method semantics changed. Immediate self-report can become lasting transfer, and fit can become worth.

These shortcuts produce confident but unreplayable applicability claims. Practitioners cannot tell which condition matters, whether the same Method was used, whether the evidence came from actual Work, or what result should be revised after a failure.

A.3.1.FT:3 - Forces

ForceTension
Local usefulnessA narrow fit result can guide current Work, while a broader transfer claim needs further support.
Unlike situationsDifference can reveal a boundary, while too many simultaneous changes defeat interpretation.
Method identityAdaptation may be necessary, while semantic change can create a different variant.
Natural WorkWorkplace evidence has practical relevance, while conditions and contribution are less controlled.
Capability and supportThey can determine outcomes, while their presence is easily attributed to the Method.
Positive and negative evidenceSuccess and failure both matter, while selective reporting favours one direction.
Decision speedTeams need a bounded answer, while missing Work or comparability must remain a reason to stop.

A.3.1.FT:4 - Solution

Method identity under A.3.1 does not establish fit for a use. Assess the required result against relevant Work and the conditions under which it occurred. A local fit result can be sufficient for the named decision. To claim transfer or a broader applicability boundary, recover the additional situation evidence and comparison on which that claim depends.

Preserve Method semantics and status throughout. Compare source and receiving conditions when carrying a claim between them; use a situation capable of testing the asserted limit when qualifying an applicability boundary. Return the supported result at that scope, or the specific missing basis.

A.3.1.FT:4.1 - Pattern-Use Unfolding

  1. Name the decision, subject, and status. State whether the question concerns fit in one receiving situation, an applicability boundary, or transfer of one supported claim. Identify the A.3.1-admitted Method, or preserve the candidate account and name only separately admitted Methods whose enactment is claimed.
  2. Bound the situations needed for the decision. For local fit, name the situation or situation family and required result. For transfer, name both source and receiving families; for an applicability boundary, name the situations that can establish that limit. Record the conditions that matter to the claim, such as project purpose, development phase, technical or domain problem, performer population, holder capabilities, participating Systems, direct relations, constraints, support, qualification window and domain result.
  3. Recover the relevant Work and evidence. Use A.3.1.WT evidence only for actual Work whose performers, enacted admitted Method, temporal extent, containing System, conditions, deviations, burdens, adaptations, results, and evidence path are recoverable. Recover capability inputs and other direct relations on which the assessment relies. A report can support the account but does not admit Work by citation.
  4. Select discriminating evidence when the claim needs it. To test a transfer or applicability boundary, select or seek a receiving or held-out situation with a condition capable of defeating the claim: technical coupling, project phase, domain, performer or capability envelope, support relation, organizational condition, information availability, authority boundary, or another named condition. State why it matters. If minimality matters, name the alternatives, ordering criterion, and basis for treating one change as smaller or weaker; otherwise record concurrent changes and unknowns without ranking them.
  5. Qualify comparability when making a comparison. Separate matched, changed, and unknown conditions. Do not call conditions controlled unless the basis supports it. Record concurrent changes and missing facts; use missing-comparability-basis when the comparison cannot distinguish the claimed boundary.
  6. Establish any required receiving performance independently. Admit receiving Work and every claimed enacted Method under their direct governors. Distinguish plans and reports from performed activity. For simulation, demonstration, training or support tasks, identify what was actually performed and what was only represented or planned; a demonstration may itself perform the Method in the required receiving situation. If the Work needed for the selected conclusion did not occur, return missing-performed-work.
  7. Track adaptations and Method semantics. Record changes to operations, dependencies, participant or responsibility conditions, stops, representations, support, and local Work. Ask whether reusable Method semantics stayed within the admitted Method. If they changed, return variant-question[...] to A.3.1.MV and evaluate the unchanged and changed branches separately.
  8. Assess domain results and evidence reach. Assess the required result and the burdens, deviations, failures and limitations that affect the fit decision. Compare results across situations when the selected claim requires it. Distinguish direct observation, report, association, contribution, and causality. Do not use immediate self-report as long-term transfer without the missing time evidence.
  9. Classify the bounded result. Return fit-within[...], failure-within[...], applicable-if[...], transfer-supported-between[...], transfer-not-supported, missing-performed-work, missing-comparability-basis, or the named missing premise. Plain labels may be used, but the situation, claim, evidence, and window must remain inspectable.
  10. Route a defeated claim by result kind. Return a failure directly only to the C.39.RQ situational requirement, C.32.MWA.PP architecture decision, B.1.5.CM construction result or admitted Method claim, or A.3.1.MV applicability or variant entry that the evidence contradicts. When the evidence may contradict an A.3.2.DE description, direct C.37 representation-use result or C.37.MP Method representation profile row, or A.15.8.MS support claim, return the bounded observation to A.3.1.CC; A.3.1.CC identifies and rechecks the maintained correction owner, including the direct governor of any lower representation result. Do not reopen every carrier.
  11. State non-transfer and reopen conditions. State the supported applicability boundary and any uncovered use that matters to the receiving decision. Reopen when one condition crosses the declared boundary, Method semantics change, evidence currentness expires, or a new unlike situation defeats the claim.

A.3.1.FT:4.2 - Record the Result

Result positionRequired content
validation useFit, applicability, or transfer question; receiver; decision; claim; qualification window; stop.
subject statusAdmitted Method, or candidate account plus separately admitted enacted Methods.
situation and Work evidenceConditions of the situation being assessed, actual Work, performers, relied-on capability inputs, Systems and direct relations, adaptations, domain results, burdens and evidence reach.
source and receiving situationsFor transfer, identify both families and their Work evidence independently. For a broader applicability boundary, identify the situations needed to test it. Preserve missing facts.
discriminationWhen a boundary or transfer claim needs a discriminating situation, state the selected condition and why it matters. In a comparison, separate matched, changed and unknown conditions.
semantic continuityPreserved Method semantics, local Work or support changes, and any reusable semantic change returned as a variant question.
assessmentResult against the local fit criteria; differences across situations when needed; burdens and deviations needed for interpretation, evidence strength, and material limits on contribution or causal claims.
returnBounded fit, failure, applicability, transfer, or missing-evidence result; direct C.39.RQ, C.32.MWA.PP, B.1.5.CM, or A.3.1.MV return, or a bounded A.3.1.CC observation for a possible A.3.2.DE description, direct C.37 representation-use result, C.37.MP Method representation profile-row, or A.15.8.MS support contradiction; non-transfer and reopen conditions; unaffected results preserved.

Keep the distinctions needed for the selected decision in the assessment and its referenced evidence. A table is optional; no separate record is needed for each position.

A.3.1.FT:4.3 - What Changes in Practice

Practitioners can use a sufficient local fit result without arranging an unrelated comparison. When they transfer a claim or qualify an applicability boundary, they can show the relevant source and receiving conditions, actual Work, semantic continuity, discriminating evidence, and the claim that survived or failed.

A narrow result such as “Fits this decision for this holder and support window; transfer untested” can support a decision to use the Method now while protecting later teams from a universal claim.

A.3.1.FT:4.4 - Constructed Fit Case

Continue the constructed A.3.1.WT evidence for admitted M-Unit-Review-1. The immediate decision is whether the Method fits pre-release review of temperature-sensor reports for Reviewer-17 through day D30 when mixed Celsius/Kelvin inputs may occur. It is not yet a decision about another reviewer, product family, tool, or organization.

W-Rep-1 and W-Disc-1 are actual Work in Calibration-Team-A. The same reviewer, capability input CAP-R17-1 with qualification record QR-R17-1, MethodDescription edition 4, manually retrieved conversion table, release boundary, and containing System are recorded. The discriminating change is the Celsius/Kelvin mismatch in S-Disc-1; it can defeat the claim that the Method exposes a unit mismatch before the release decision. In W-Disc-1, the reviewer normalizes values, detects the mismatch, stops release, and returns the report. A.3.1.CC has separately corrected direct use result C37-UR-Flow-4 and its governed representation result REP-UR-Flow-4, which had omitted normalization for that named use.

Return fit-within[Reviewer-17, temperature-sensor reports, edition 4, manual conversion table, through D30] for the named release-review decision. Also return transfer-not-tested for other holders, product families, support routes, qualification windows, or organizations. The two occurrences do not establish causal superiority or practical worth.

For the narrower decision about the same-unit report already reviewed in W-Rep-1, its observed acceptance can support fit for that named situation, reviewer and support window. W-Disc-1 is not a prerequisite for this narrower result. Evidence about mixed-unit handling is needed when that condition enters the receiving question.

If the reviewer had changed the reusable operation from unit normalization to an approximation rule absent from M-Unit-Review-1, preserve the observed Work but return variant-question[approximation-rule] to A.3.1.MV. Do not call the changed branch successful transfer of the unchanged Method.

A.3.1.FT:5 - Archetypal Grounding - SSFD Situation Boundaries

The SSFD workplace evidence supplies varied actual-project reports and a decision-relevant unlike-situation probe. Project 11 concerns functional analysis of a new by-wire steering system and reports 48 failure modes, 44 requirements and design rules, 44 individual-system test cases, and 33 overall-system requirements and test cases. Project 32 reports difficulty representing the relation between a closed-loop sensor and controller.

Use Project 11 as a source situation only after the SSFD Method or candidate status, relevant Work evidence, performer and capability facts, support conditions, and relied-on claim are recovered. Use Project 32 as a discriminating unlike situation because the closed-loop relation can challenge a representation or applicability claim. Do not infer that Project 11 preceded Project 32, that the same performers and capabilities were present, or that a difficulty establishes whole-Method failure.

A result may be narrow: Project 11 supplies bounded evidence for one functional-analysis situation; Project 32 raises a question about a broader representation claim. A.3.1.CC can determine whether correction is needed when the relevant claim and evidence are recoverable; a transfer conclusion requires the receiving Work and comparison basis. The 41-report set broadens the evidence pool but does not establish transfer across every project stratum or causal contribution by SSFD alone.

A.3.1.FT:5.1 - Unlike-Domain and Current-Alternative Probes

The Digital Vaccine action-research case supplies performed validation actions in an operating health-services ecosystem and three plan-perform-evaluate cycles. Use it to examine the A.3.1.FT comparison in another domain, not to claim that SSFD transfers to health services. Its evaluation is ex ante and case-specific.

The sustainable-design workshops supply bounded applications of The Natural Step, Whole System Mapping, and Biomimicry across consumer electronics, furniture, and clothing. They can expose industry and activity differences, but immediate participant self-reports do not establish long-term transfer. The Halogen case shows that practitioner skill, project demands, and organization can accompany cyclic Method adaptation; if reusable semantics changed, route the result to A.3.1.MV instead of expanding one fit claim.

A.3.1.FT:5.2 - EC-417 Early Stop

The full EC-417 application supplies the receiving problem, alternatives, calculations and the distinct limits used below.

C-EC-Release-v2 remains a candidate account. The three support-use Work occurrences from A.15.8.MS do not perform a release and cannot support release fit or transfer. To assess local release fit, recover actual release Work, its performers, separately admitted enacted Methods, capability inputs, Systems and direct relations, support conditions, domain result, burdens, deviations and authority facts needed for that decision. A transfer or applicability-boundary claim additionally requires the receiving or held-out release evidence capable of testing that claim.

While the required release Work is absent, return missing-performed-work. Return missing-held-out-situation only when the selected boundary or transfer claim needs that missing situation. Preserve the candidate branch and the unsupported CUR-EC417-CadenceEffect-1; no cadence or transfer claim becomes supported by planning three releases.

A.3.1.FT:6 - Bias-Annotation

BiasLikely driftRepair
label-transfer biasThe same Method name is treated as evidence of the same Method and conditions.Recover Method status, semantics, actual Work, and situation positions.
success-generalization biasOne favourable occurrence becomes a situation-family claim.Return the narrow fit result and name the missing transfer evidence.
uncontrolled-sameness biasUnrecorded capability, support, and organizational conditions are called matched.Separate matched, changed, and unknown positions with their bases.
adaptation launderingChanged reusable semantics are called local tailoring.Return an A.3.1.MV variant question and preserve both branches.
failure-totalization biasOne difficulty becomes whole-Method failure.Determine which claim, if any, the evidence contradicts, and identify that claim’s situation boundary and correction owner.
fit-as-worth biasUsability in one situation becomes a keep or adoption decision.Send results, burdens, alternatives, and evidence limits to C.11.MV.
account-enactment biasA candidate account is said to be enacted in receiving Work.Admit Work and enacted Methods separately; preserve candidate status.

A.3.1.FT:7 - Conformance Checklist

  • The decision is explicitly fit, applicability, or transfer for one claim.
  • The Method is admitted or the proposed whole remains a candidate account.
  • The situation being assessed names decision-relevant conditions; transfer identifies source and receiving families, and an applicability boundary identifies the situations needed to test it.
  • Actual Work needed for the conclusion, performers, enacted admitted Methods, relied-on capability inputs, Systems, direct relations, results and evidence paths are recoverable or returned as gaps.
  • Any required discriminating situation is selected because its condition can expose a limit in the claim.
  • When situations are compared, matched, changed and unknown conditions are separate.
  • Adaptations are recorded, and reusable semantic change opens a variant question.
  • Direct observation, self-report, association, contribution, and causality are not merged.
  • The result is bounded by holder, situation, support, time, and evidence.
  • Fit is not overread as practical worth, general effectiveness, capability, or cultural adoption.

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

Anti-patternRepair
“It worked in automotive, so it transfers to health services.”Recover evidence for the same Method under the receiving conditions. Tests of another Method in health services do not establish this transfer.
“Project 32 proves the Method failed.”Identify the representation or applicability claim and the missing receiving evidence first.
“We tailored it, therefore it transferred.”Check whether reusable semantics changed; if so, return a variant question.
“The workshop participants liked it, so transfer is established.”Return only what the immediate self-report supports; identify any missing Work, result or time evidence required by the transfer claim.
“The candidate was enacted successfully.”Admit the Work and enacted Methods, not the candidate account.

A.3.1.FT:9 - Consequences

Fit and transfer claims become inspectable and narrow enough to guide decisions. Practitioners can see which conditions matter, what actual Work supports the result, whether the same Method persisted, and where another situation must reopen the claim.

The cost is that many plausible transfers end as missing evidence or a smaller applicability envelope. A semantic adaptation may also leave a separate variant to maintain.

A.3.1.FT:10 - Rationale

Transfer is not a property carried by a Method name. It is a claim about preserved reliance across a stated change in conditions, supported by actual Work and bounded evidence. A discriminating unlike situation is valuable because it can defeat the claim; it need not resemble a statistically representative sample.

Separating semantic continuity from local Work and support changes protects Method identity. It also lets a failure improve the applicability account without forcing rejection of the Method in situations for which evidence remains valid.

A.3.1.FT:11 - SoTA-Echoing

SourceContributionBoundary and practitioner implication
Yildirim, Campean, and Uddin, function-modeling evaluation in industry practiceWorkplace-project strata, reported applications and limitations, later report analysis, and the comparison of Project 11 and Project 32 supply an unlike-situation probe.One automotive OEM, retrospective reports, and SSFD use within a broader methodology establish neither SSFD-only causality nor general transfer.
Schønheyder and Nordby, design-Method use and evolution in professional practiceProject demands, practitioner skill sets, organization, and cyclic adaptation are conditions that can change a fit or variant decision.Keep the findings bounded to the studied firm and conditions; establish any causal claim or Method-variant identity separately.
Tsai, Zdravkovic, and Söder, DBE-design Method action researchRepeated plan-perform-evaluate cycles in an operating health-services ecosystem provide an unlike-domain example for the comparison method.The evaluation is ex ante and case-specific; it does not prove long-term effect or transfer to the other elicited domains.
Faludi, Yiu, and Agogino, empirical tests of sustainable-design MethodsSeveral Methods, industries, activities, and immediate participant reports supply bounded situation-comparison inputs.Immediate self-report establishes neither long-term product results nor causal superiority or transfer of recombined variants.

A.3.1.FT:12 - Relations

  • A.3.1.WT supplies occurrence-level evidence for the selected situations and explicit gaps. It does not make the fit or transfer conclusion.
  • A.3.1.CC consumes any bounded observation that may contradict an A.3.2.DE description, direct C.37 representation-use result, C.37.MP Method representation profile row, A.15.8.MS support claim, or directly governed lower representation result; it identifies and rechecks the maintained correction owner. Passing coherence does not establish fit.
  • C.11.MV consumes fit, failure, applicability, burdens, alternatives, and evidence limits for a separate practical-worth decision.
  • A.3.1.MV owns reusable Method variants, provenance, applicability entries, and retirement. A semantic change returns there; a local Work, support, description, or representation change alone need not create a variant.
  • A.3.1 governs Method admission, A.15.1 each Work occurrence, A.2.2 capability inputs, and A.10 claim-bound evidence. Cite the direct governor for every System, Agent-performed Work, relation, permission, authority, or result claim relied on.
  • A.3.1.MI may later consume a bounded fit or transfer result when introducing a Method in practice; it does not inherit a causal or worth conclusion.

A.3.1.FT:End

A.3.1.MV - Construct and Maintain a Method Variant

Type: Method pattern Status: Stable

A.3.1.MV:0 - Use This When

Use this pattern when a Method has been adapted, branched, recombined, or revised and future users must know whether they face the same Method, a reusable variant, a candidate proposal, or only a changed description, representation, tool, prompt, publication, support result, or local Work occurrence. Begin with the reusable way of doing that may have changed: which operation, dependency, participant condition, entry or stop rule, or other reusable Method semantic is different?

For a first pass, state what reusable way of doing changed, if any. If none did, name the changed object, the maintained result, the affected claim or edition, and what to maintain, reconsider, or stop. Use the fuller account only when later selection, reuse, comparison, or retirement needs it.

The first useful result is an account of the variant decision and any derivation needed for the maintained use. A fuller account, when needed, names the parent Method or candidate, the proposed child and status, preserved semantics, changed semantics, derivation basis, applicable situation claim, available supporting and defeating evidence, relied-on descriptions and support editions, current selection uses, currentness, retirement condition, and the next decision. If the visible change is not a Method variant, the account instead names the changed object, the separately governed maintained result, the claim or edition affected, and the next maintenance, reconsideration, or stop action.

Here variant is Plain practice wording for a Method whose reusable semantics differ in a way relevant to a named use while its derivation from another Method remains useful. The label alone does not admit a U.Method, establish provenance, or prove fit, worth, reuse, or superiority.

Do not use this pattern merely because a file, diagram, MethodDescription edition, prompt, tool, publication form, support configuration, team, project, or dated Work occurrence changed. Maintain those results under their own patterns unless the change also alters reusable Method semantics.

A.3.1.MV:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
reusable Method semanticsThe repeatable operations, dependencies, entry and stop rules, participant conditions, transformation commitments, or other claims that distinguish how the Method is carried out and when it applies.A wording, layout, carrier, tool, or local performance difference is not automatically semantic change.
admitted variantAn independently admitted Method whose changed and preserved reusable semantics and derivation are recoverable for the maintained use.Derivation from an admitted parent does not admit the child.
candidate lineageA status-preserved sequence or family of candidate accounts whose proposed semantic changes and derivations are tracked without Method admission.A well-documented candidate does not become a MethodDescription or enacted Method.
derivation claimThe evidence-bearing claim that one Method or candidate arose through identified changes from another.Similarity of names, files, or outcomes does not establish derivation.
preserved semanticsReusable Method claims intentionally retained across the derivation.“Mostly the same” is insufficient when the receiving use depends on the omitted difference.
changed semanticsReusable Method claims added, removed, reordered, constrained, generalized, specialized, or recomposed in the proposed child.A local departure in one Work occurrence remains a deviation until reusable semantics are recovered.
applicability entryA bounded claim about situations, capability and support conditions, evidence, and stops for selecting or rejecting a variant.It is not practical worth, organization-wide adoption, or a selection command.
edition and support linkThe MethodDescription, representation, method-base edition, publication, tool, prompt, or support result currently used for a variant.These results can change without changing variant identity and can serve several variants only when their claims permit it.
retirement conditionA named evidence, currentness, source, use, or replacement condition under which an entry stops being offered for the maintained selection use.Retirement from one repertoire use does not erase the Method, its history, or every other use.

A.3.1.MV:1 - Problem Frame

Method adaptation leaves many visible traces: a team edits a checklist, adds a tool, changes a diagram, rewrites a prompt, or performs the Work differently. Some traces express a reusable change in the way of doing; others are only descriptions, support configurations, local departures, or evidence. Treating every trace as a Method variant floods the repertoire with false identities. Treating none as a variant hides meaningful branches and makes later fit and worth evidence impossible to bind to the semantic branch they concern.

The practical question is whether reusable Method semantics differ for the named use, what derivation is supported, and which status, applicability, evidence, and currentness claims can be maintained while keeping candidate accounts distinct from admitted Methods.

A.3.1.MV:2 - Problem

Version numbers, filenames, team names, tool stacks, and project histories become variant identifiers. A successful local adaptation is generalized without an admitted reusable Method. Candidate recombinations inherit parent admission. A new MethodDescription edition is mistaken for a new Method, while a change to operation order or stop conditions is hidden as documentation maintenance.

The resulting repertoire cannot guide selection. Users cannot tell which semantics changed, whether evidence applies to parent or child, what support edition is current, which situation claim is supported, or when an entry should be retired.

A.3.1.MV:3 - Forces

ForceTension
ReuseStable variant identities help later selection, while premature naming creates spurious Methods.
Local adaptationWork must respond to situations, while one local departure need not be reusable semantics.
ProvenanceDerivation helps explain and compare variants, while similarity and chronology can be mistaken for evidence.
EvidenceFit and worth results should follow the right semantics, while evidence often bundles Method, support, capability, and organization.
CurrentnessUsers need current entries and editions, while retirement from one use must not erase history.
Candidate continuityProposed changes need traceability, while detailed lineage can launder candidate status.
RecombinationComponents can inspire new Methods, while hybrids do not inherit component admission or worth.

A.3.1.MV:4 - Solution

A.3.1:4.7–4.8 decides which semantic change identifies another Method; B.1.5.RS compares a constituent replacement in encompassing uses. The operation below constructs and maintains the proposed variant and its evidence, preserving a description or support correction as a different result.

Identify variants only through changed reusable Method semantics, preserve admission or candidate status independently, and maintain derivation, applicability, evidence, editions, selection uses, currentness, and retirement as separate claims.

A.3.1.MV:4.1 - Pattern-Use Unfolding

  1. Name the maintenance use. Identify the practitioner or decision that needs the repertoire, the Method family or candidate lineage in scope, the situation and qualification window, and what selection, reuse, comparison, or retirement action the entry must support.
  2. Recover each subject and status. Identify every A.3.1-admitted Method and every candidate account separately. A parent Method, candidate child, MethodDescription, representation, support configuration, and Work occurrence keep different identities and statuses.
  3. Recover the semantic baseline. From the parent or earlier candidate, record the reusable operations, dependencies, entry and stop rules, participant conditions, required relations, and applicability claims that matter to the maintenance use. Include the inclusion and decision rules that make professional judgments operational when those rules affect the reusable way of doing. Do not use a file diff as the semantic baseline.
  4. Classify the observed change. Separate changed reusable Method semantics from description wording, representation, publication, tool, prompt, support, capability, organizational System or selected structure, assignment, permission, authority, and local Work deviations. For every non-semantic change, name the changed object, the separately governed maintained result, the claim or edition affected, and the next maintenance, reconsideration, or stop action. For a representation change, locate the affected claim in its direct result, in a C.37 selection result when that selection is needed, or in a C.37.MP profile when several unlike Method-related uses must remain connected. When a profile is involved, use step 8 for its complete maintained basis. Name a direct predicate and its participants only when the disposition relies on that obtaining relation; otherwise assert no path or relation occurrence.
  5. Construct the proposed child account. State preserved semantics, changed semantics, reason for change, intended situations, required capability and support conditions, and the limits of the available evidence. A traceable candidate entry can complete the maintenance use. Select further evidence or a trial through C.11.DUA only when its obtainable result could change the receiving decision enough to warrant the full burden. If no reusable semantic difference remains, maintain an edition, support, or Work result rather than a variant.
  6. Establish derivation without inheriting admission. Record the source Method or candidate, change Work or source account, changed positions, chronology when relevant, and evidence supporting the derivation claim. Then admit the proposed child independently under A.3.1 or keep it as a candidate.
  7. Bind evidence to the right semantics and situation. Attach available A.3.1.WT trial observations, A.3.1.CC corrections, A.3.1.FT fit or transfer results, and C.11.MV worth decisions only to the Method or candidate semantics, situation, support, capability, alternative set, and window they concern. Parent evidence does not automatically cover the child.
  8. Maintain descriptions, representations and support relations separately. Name the MethodDescription editions, direct representation results, any needed C.37 selection results or C.37.MP profiles, and A.15.8.MS method-base or support results relied on by the maintained use. Include publications, tools, prompts and access or use relations only when that use depends on them. For every C.37.MP profile retain the shared MethodDescription or candidate-account source, one complete C.37 claim group for each unlike action, cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions for reconsidering several selections. A changed result, edition, or relation does not by itself change variant identity.
  9. State applicability and selection uses. Record supported situations, situations in which an applicability claim is contradicted, missing evidence, capability and support conditions, current alternative set, and the receiving decision that may use the entry. Use A.19 selected-set semantics for a non-trivial repertoire choice; the entry itself selects nothing.
  10. Maintain currentness and retirement. State source, evidence, edition, situation, and qualification windows; superseding or defeating evidence; review trigger; and what retirement means for this use. Preserve historical and other-use access when the Method or candidate still matters elsewhere.
  11. Return the maintained repertoire and non-variant dispositions. Report admitted variants, candidate lineages, applicability and evidence gaps, current entries, retired entries, and the specific repertoire claim, if any, that findings about applicability, evidence, currentness or retirement require reconsidering. For every non-variant, report the changed object, separately governed maintained result, affected claim or edition, and next maintenance, reconsideration, or stop action. Do not assign repair authority or invent a relation when the governing result and next action are sufficient.

A.3.1.MV:4.2 - Record the Result

Result positionRequired content
maintenance usePractitioner or receiver, repertoire decision, situation, qualification window, and stop.
subject and statusParent and child Methods or candidate accounts; separate descriptions, representations, support results, Work, and evidence.
semantic baselineReusable operations, dependencies, entry and stop rules, participant conditions, relations, and applicability claims relevant to the use.
change classificationChanged reusable semantics; for each non-variant, the changed object, separately governed maintained result, affected claim or edition, and next maintenance, reconsideration, or stop action.
derivationParent, proposed child, change basis, chronology when material, preserved semantics, changed semantics, and evidence reach.
admission branchIndependent Method admission or status-preserved candidate account and missing admission basis.
applicability and evidenceSituations, capability and support conditions, the available evidence and decisions from step 7, alternatives, gaps and qualification windows, all bound to the right semantics and receiving use.
edition and support linksRelied-on descriptions; direct representation results and, when needed, C.37 selections or C.37.MP profiles with the complete basis named in step 8; method-base editions, publications, tools, prompts, and support results for each maintained use.
currentness and retirementCurrent selection uses, source and evidence windows, defeating conditions, retirement meaning, retained history, and reopen trigger.
returnMaintained admitted-variant repertoire and candidate lineages; non-variant dispositions in the same four-part shape; the smallest defeated repertoire claim when one exists; and limits on what the repertoire establishes.

A.3.1.MV:4.3 - What Changes in Practice

Teams stop using version labels and project names as Method identities. They can show which reusable semantics changed, which evidence belongs to which branch, why a child is admitted or a candidate, and which description or support edition serves each use.

Local departures can remain Work evidence, descriptions can evolve without multiplying Methods, and semantic branches receive applicability, evidence, currentness, and retirement conditions.

A.3.1.MV:4.4 - Constructed Variant Case

Continue the temperature-sensor review chain. M-Unit-Review-1 is admitted with reusable semantics: identify every source unit, normalize values, compare with declared tolerance, and stop on an unresolved mismatch. C.11.MV retained it for reports whose sources can use different unit systems.

A team proposes an approximation rule for missing conversion metadata: infer a likely scale from sensor range, mark the inference, and continue only when the tolerance decision is unchanged under both plausible scales. This is not merely a new checklist. It changes the reusable operation and stop conditions, so create candidate account C-M-Unit-Review-Approx-1 derived from M-Unit-Review-1. Preserve identification, explicit normalization when metadata exists, tolerance comparison, and unresolved-mismatch stop; add the bounded inference operation and a two-scale invariance stop.

Do not admit the candidate from parent status. Link candidate-account content CA-M-Unit-Review-Approx-Content-1, proposed representation C-REP-Approx-1 of that candidate account, and the same conversion-table support result only as candidate-serving material; none is a U.MethodDescription for the candidate whole. Keep performance on missing-metadata reports unresolved. Retain that limit, the reviewer capability conditions and the comparison against stopping or metadata recovery where they matter to the entry’s use. To maintain the catalogue, record the proposed approximation rule, its origin in M-Unit-Review-1, its two-scale stopping condition and its untested candidate status. This is enough to retain the proposal in the catalogue. Choose a trial only when its useful attainable answer warrants the work and delay. Until independent Method admission, the repertoire contains admitted M-Unit-Review-1 plus candidate lineage C-M-Unit-Review-Approx-1; no Work is said to enact the candidate whole.

If the team only updates the diagram to show the already-required normalization step, first identify its action. For one action, maintain the diagram and the affected result under their direct governors; use C.37 only if a selection question remains. C.37.MP is not invoked for that one-action case. When that result belongs to a complete C.37.MP profile for several unlike actions, also maintain only the cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions for reconsidering several selections affected by the diagram change. Neither case creates a variant. If the team replaces the manual table with a verified tool while operations and stops remain unchanged, maintain the A.15.8.MS support result and no variant.

A.3.1.MV:5 - Archetypal Grounding - Adaptation and Recombination

The Halogen design-practice case reports conscious cyclic evolution and adaptation of Methods across safety-critical projects, practitioner skill sets, and organization of design activity. Use the evidence to recover proposed semantic changes, local Work deviations, situation conditions, and lineage candidates. The source concerns one 52-person multidisciplinary firm.

When reusable semantics can be recovered and a Method is independently admitted, maintain the variant with its derivation and applicability. When the recovered change is only a local Work departure, retain the Work evidence and return the non-variant disposition. When the material leaves it unresolved whether Method semantics or support, capability, or organization changed, maintain a candidate lineage only if the proposed reusable semantic differences and derivation can be stated; otherwise return the missing semantic basis.

The sustainable-design study reports activity- and mindset-level observations from separate workshops using The Natural Step, Whole System Mapping, or Biomimicry. Companies chose workshops, order varied, and participants could differ, so the publication supplies neither one current-alternative decision nor matched Work across the three Method families. Those immediate participant reports can motivate recombination candidates, but a preferred component set is not an admitted hybrid Method. Record the proposed preserved and changed semantics, parent contributions, situations and evidence limits; do not inherit worth or transfer from the source Methods.

A.3.1.MV:5.1 - EC-417 Candidate Lineage

The full EC-417 application supplies the receiving problem, alternatives, calculations and the distinct limits used below.

Maintain editions of C-EC-Release-v2 as a candidate lineage until A.3.1 admits a Method with recoverable reusable semantics. Keep the four admitted constituent Methods, their descriptions, representations, PLM and CI Systems, prompts, support arrangements, release Work, and local deviations separate.

A changed release document, cadence, tool integration, AI prompt, or method-base edition does not create a C-EC-Release-v2 variant by itself. A proposed semantic change must name the changed reusable operation, dependency, entry or stop rule, or another Method claim and preserve the candidate branch. Unsupported CUR-EC417-CadenceEffect-1 remains unsupported.

A.3.1.MV:5.2 - Preserve a Changed Basis of Judgment Behind the Same Map

Use the constructed contact-planning and handover-review accounts in A.3.2.DE:5.4. The maintenance decision is whether the proposed handover account is only another presentation of the contact Method or a candidate with changed reusable semantics. Recover the operations rather than comparing the two canvases.

The parent includes people with the approval or supply roles needed to arrange rollout contacts. The proposed child retains identifying roles, recording supported facts and arranging contact, but changes two operative commitments: include a role whose holders produce or use information needed for the handover in their work, regardless of approval influence; and withhold a complete-coverage conclusion while a material working dependency lacks an account or contribution. Thus a low-influence night operator can be essential to the child’s construction even when absent from a correct parent map. Changing an inclusion rule and the conditions for concluding the task is a reusable semantic change. Merely adding that operator’s name to a particular drawing, without changing the reusable rule, would not establish a variant.

Keep the parent admitted under its existing basis and maintain the child as a candidate derived from it. The child entry names the preserved operations, changed inclusion and completion rules, intended handover-review use, access to the needed work accounts, and unresolved evidence about its usefulness. The inherited canvas remains a representation choice; contact access and facilitator preparation remain separate conditions. Retaining the proposal for a future choice can finish this maintenance task without admitting the child or commissioning a trial.

Evidence is transferred claim by claim. Suppose a parent observation established that the day lead’s name and the IT contact details were correct in a stated window. Those facts may serve the child if current; the original observation and its scope remain unchanged. A parent observation of rapid approval coordination does not establish that the child covers receiving work, finds missing handover contributions, or improves the handover. The constructed replay in A.3.2.DE supplies an intelligibility check, not those performance claims. Missing access to the night or relief operator’s working account leaves that coverage claim open.

A later change to the canvas alone returns to its representation owner. A change to the working-dependency inclusion rule or the unresolved-dependency stop reopens the affected child semantics, description and selection claims. If the handover use is retired while approval-contact planning remains useful, retire that use of the child entry and preserve the parent and historical derivation. A common name or graphical form does not collapse those dispositions.

A.3.1.MV:6 - Bias-Annotation

BiasLikely driftRepair
file-version biasEvery document or repository version becomes a Method variant.Compare reusable Method semantics; for an edition-only change, name the maintained result, affected edition claim, and next maintenance or stop action.
local-deviation biasOne Work departure becomes a reusable Method.Recover intended reuse, a semantic account, and independent admission; otherwise keep Work evidence.
inherited-admission biasA child or hybrid inherits parent Method status.Admit every proposed Method independently or preserve candidate status.
tool-identity biasA new prompt, tool, or platform becomes the variant.Ask which reusable operations or stops changed; maintain support when none did.
evidence-smearing biasParent fit or worth evidence is attached to every descendant.Bind evidence to semantics, situation, support, capability, alternative set, and window.
lineage-as-worth biasDetailed provenance is treated as evidence that the branch should be selected.Keep derivation, applicability, and practical worth as separate claims.
retirement-erasure biasRetirement from one repertoire use deletes history and other uses.State the retired selection use and preserve the Method, lineage, and evidence where still needed.

A.3.1.MV:7 - Conformance Checklist

  • One maintenance and selection use, receiver, situation, window, and stop are named.
  • Every parent and child is independently admitted as a Method or preserved as a candidate account.
  • Reusable Method semantics are recovered before variant identity is claimed.
  • Preserved and changed semantics are explicit and decision-relevant.
  • Description, representation, publication, tool, prompt, support, capability, organization, and local Work changes remain separately governed.
  • Derivation has an evidence basis and does not transfer admission.
  • Trial, coherence, fit or transfer, and worth evidence is bound to the right semantics, situation, conditions, alternatives, and window.
  • Current description and support editions are linked without defining variant identity.
  • Applicability, missing evidence, selection use, currentness, and retirement conditions are recoverable.
  • Recombination candidates inherit neither parent admission nor parent worth.
  • A useful candidate entry can complete its maintenance use with the relevant evidence limits. Any further trial is selected for its useful obtainable contribution and full burden.

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

Anti-patternRepair
“Version 2.1 is a new Method variant.”Show the changed reusable Method semantics or maintain an edition only.
“The team adapted it, so the variant is admitted.”Preserve the Work evidence and candidate account until independent admission.
“The prompt changed, so the Method changed.”Recover the reusable semantics expressed by the prompt. Use A.3.1 to decide whether Method identity changed; maintain any separate support change under its own pattern.
“The hybrid inherits evidence from all three parent Methods.”Preserve the hybrid’s admission status and bind each relied-on result to the hybrid’s own semantics and situation. Select a trial when its useful attainable answer warrants its full burden.
“Retired means obsolete everywhere.”Name the selection use and defeating condition; preserve other supported uses and history.

A.3.1.MV:9 - Consequences

Variant repertoires show the reusable semantic differences and the evidence for each branch. Practitioners can select among stable admitted Methods and visible candidate branches without confusing package change with Method change.

The cost is more disciplined status and provenance work. Some attractive adaptations remain candidate lineages, and teams must keep descriptions, support editions, evidence, and selection uses linked without letting any one of them define identity.

A.3.1.MV:10 - Rationale

Reuse depends on knowing what way of doing is being reused. Files and tools can carry or support that way, and Work can reveal changes, but only reusable semantic change distinguishes a Method variant for the maintained use. Derivation does not supply the child’s Method admission; that admission is checked independently.

Maintaining applicability, evidence, currentness, and retirement with the variant prevents a static family tree. The result is a repertoire for decisions rather than a genealogy or archive alone.

A.3.1.MV:11 - SoTA-Echoing

SourceContributionBoundary and practitioner implication
Schønheyder and Nordby, design-Method use and evolution in professional practiceCyclic evolution, project demands, practitioner skill sets, organization, and observed adaptation supply inputs to variant and applicability maintenance.The reported adaptations concern one multidisciplinary design firm; Method admission and causal effect need their own grounds.
Faludi, Yiu, and Agogino, empirical tests of sustainable-design MethodsActivity- and mindset-level observations across three Methods and industries supply evidence that can motivate bounded branch or recombination questions.Immediate self-report does not establish long-term results, hybrid-Method admission, or the worth of recombined variants.
Gericke et al., method ecosystems, and Stacey et al., Methods as engineering knowledgeQuestions about maintained Method ecology, content, representation, use and change help construct the repertoire account.Their contribution is conceptual: distinctions for constructing the repertoire account.
Gray, Chivukula, and Asad, Toward an Architectural Model of Design MethodsThe question of which epistemic commitments a derived method preserves or loses informs the inclusion and decision-rule comparison in §5.2.This initial architectural sketch motivates that comparison. The example is a Method Engineering construction.

A.3.1.MV:12 - Relations

  • A.3.1.WT supplies actual adaptation and deviation evidence; A.3.1.CC supplies corrections tied to contradicted claims and maintained results; A.3.1.FT supplies applicability, fit, failure, and transfer limits; C.11.MV supplies bounded practical-worth and branch decisions. None identifies a variant without changed reusable Method semantics.
  • A.3.2.DE maintains descriptions; C.37 maintains one-action representation-use results; C.37.MP maintains complete Method representation profiles for several unlike Method-related actions, including their action rows and separate cross-use result; A.15.8.MS maintains method-base editions, publications, tools, prompts, and support results. A lower representation remains with its direct FPF governor. Changes to any of these results do not automatically change Method identity, and a non-variant disposition names the changed object, maintained result, affected claim or edition, and next action.
  • A.3.1 governs Method admission. A.3.1.MR can recover a candidate Method from Work evidence under its conditions. C.2.1 governs episteme and edition identity; A.10 evidence use; G.5 registered Method-family candidate sets; A.19 comparison and selected-set semantics.
  • A.3.1.MV records local source, evidence, situation, qualification-window, defeating-evidence, currentness, and retirement claims. Open G.11 refresh orchestration only for one of its named shipped packs, evidence or selected sets, archives or fronts, publication/currentness objects, dependencies on reused A.6.RCD predicate definitions or derived relation kinds, or another G.11-admitted condition.
  • A.3.4 governs any separate claim that one continuing carrier, organizational System, selected structure, or other subject changed across a bounded occurrence. A semantic difference, derivation account, edition relation, or local Work deviation does not by itself establish a U.Transformation.
  • A.3.1.MI consumes a maintained admitted variant or status-preserved candidate entry when attempting a bounded introduction. C.36.MC uses either an independently admitted Method, with actual enactment when its cultural claim relies on that performance, or a status-preserved candidate or observed-practice branch without Method or enactment inflation; neither inherits admission or worth from the repertoire.

A.3.1.MV:End

A.3.1.MI - Introduce a Method into Practice and Decide What to Keep or Change

Type: Method pattern Status: Stable

A.3.1.MI:0 - Use This When

Use this pattern when a Method or an interpretable proposal can be tried in real practice and the next decision depends on what its introduction and later use reveal. The target can remain a proposal: preserve that status and distinguish it from the independently admitted Methods enacted in the attempt. Start with the receiving result and the decision the observations could change.

For an ordinary first use, explain what the team tried to establish, what it did, what was later observed or could not begin, and what to keep, revise, branch, replace or stop. Separate a change to the target way from a change to how people obtain, learn or use it. The Harbor application (IS.Application:1.3) shows this small account leading directly to a receiving action.

Add the subjects, relations and evidence needed by the claims on which that decision relies. Sections 4.1–4.2 keep those conditions available: a capability claim needs its holder and grounds; a change governed by an authorization rule needs that basis; a causal explanation needs C.28. A description, plan, completed introduction and successful later use remain different results. Introduction can finish while access, fitness or later performance still fails.

Use an adequate current capability without prescribing development. Bring in E.23.CDI or the relevant domain capability-development Method when the attempt requires that change; an absent result returns to that supplier or prevents the dependent attempt. A.3.1.MI does not itself produce or certify capability development. Use C.36.MC when the primary question concerns transmission, recognition, selection, retention, loss or another cultural result across a population.

A.3.1.MI:0.1 - Working Distinctions

QuestionDistinction that changes the next action
What should become possible?The target practice and its intended receiving result differ from the way used to introduce it. Changing a lesson, access condition or support arrangement need not change the target Method.
What is already established?An admitted Method differs from a candidate account of a proposed way. Keep the proposal’s status; describing or trying it does not admit or enact a candidate whole.
What happened?A description or plan, performed introduction and later performed work are separate. An attempt can finish without establishing the intended condition.
Whose capability is needed?Qualified supply can make a result available without the recipient acquiring the supplier’s operation. A capability or capability-change claim needs its own grounds.
What does an observation show?Acceptance, fit, feasibility, enactment, burden, reach, continuation and an outside result answer different questions. A favourable observation in one does not settle the others or establish its cause.
What changes next?Decide which target, description, strategy or condition to keep or revise, and return it to the responsible practice. A revision decision supplies no new authority to act.

Use the detailed positions in §4.2 when the decision needs their kind, identity or evidence; they are not a requirement to populate every position for every introduction.

A.3.1.MI:1 - Problem Frame

A new procedure arrives with instruction, expert assistance, a tool, changed duties, management attention and a different review occasion. Later results are credited to “the Method”, while failure is blamed on resistance or ability. Either attribution can hide the contribution that needs changing.

The practitioner needs to decide what to do next: retain a useful way, repair its explanation or provision, develop a needed capability, adapt the introduction, replace the target or stop. Follow the intended change through the attempt and later receiving work. Keep observations and explanations separate until the required grounds are available; otherwise an access failure can provoke redundant training, or a completed workshop can be mistaken for usable practice.

A.3.1.MI:2 - Problem

A rollout plan can be reported as adoption. Training can be reported as capability. Tool availability can be reported as use. A manager’s sponsorship can be reported as permission or authority. Later Work can be merged with the introduction Work, and a favourable domain result can be assigned to the Method without an alternative or contribution basis.

When several positions are compressed into one intervention label, the team cannot revise locally. It either repeats the whole programme or rejects it, even when the defect lies in one description, support relation, capability condition, assignment, permission, authority boundary, or outside-result assumption.

A.3.1.MI:3 - Forces

ForceTension
Real practiceNatural Work reveals use and consequences, while many conditions change together.
Intervention claritySeparate intended changes make learning possible, while one programme label can hide those changes.
CapabilityNew Work may need development, while delivered training and acquired capability remain different results.
Authority and participationA governed change needs its applicable authorization and actual performers, while sponsorship and attendance are weaker facts.
TimeObservation timing must fit the receiving decision, while delay can make sources and alternatives stale.
ContributionA decision needs a plausible account, while causal isolation is often unavailable.
Revision localityA defeated claim should reopen its owner and affected dependents, while bundled rollout invites whole-programme repair.

A.3.1.MI:4 - Solution

Prepare and perform a bounded introduction, observe its later use, and decide what to keep or change. Distinguish the target from how it is introduced and supplied. Begin with the small working account in §0; make each relied-on claim precise through the applicable steps below. Use C.28 only for causal reliance, and return a correction or alternative to the particular maintained result or receiving work it changes.

A.3.1.MI:4.1 - Pattern-Use Unfolding

  1. Name the receiving result and decision. State what the practice should obtain, where and when the attempt and later observation can occur, and what keep, revise, branch, replace or stop would change. Preserve whether the target is an admitted Method or a candidate account. Identify the relevant population and qualification window; a company or team label alone does not establish an organizational System or selected structure.

  2. Distinguish the target from its introduction. Explain the intended target change and the way of obtaining it. Where their kind or identity affects the decision, identify the claimed subjects: admitted Methods; A.3.2-classified MethodDescriptions or other claim-bearing epistemes; representations; Systems; capability bearers and results; particular Work occurrences; domain entities; organizational Systems or selected structures. Keep candidate target accounts and descriptions separate; a mixed list does not establish the claimed objects or relations.

    If A.3.1 has admitted the introduction Method, name it and identify a U.MethodDescription only when A.3.2 classifies an episteme whose one EntityOfConcern is that Method. Otherwise retain a candidate introduction account and identify its claim-bearing material as a candidate account, description episteme, or other named episteme with status, claims, and maintained result; do not classify it as U.MethodDescription. Identify any WorkPlan separately; neither the plan nor performed Work admits or enacts the candidate.

    For every relied-on assignment, permission, authority, access, use, enactment, or other direct relation, name the predicate, participant meanings, participants, and obtaining basis. Omit unclaimed positions.

  3. Connect the observation to the result it can change. For each relied-on target or strategy claim and selected observation, recover the particular maintained claim or edition, its status and grounds, the observation that could support or defeat it, and the next receiving action or stop. Keep the source and qualification window where they affect use. Name the receiving Agent or governing pattern when current; otherwise retain a local decision rather than inventing a recipient.

  4. Select the capability branch. Omit capability detail that cannot change the attempt, interpretation, or decision. When the decision does rely on capability, recover the A.2.2 basis: holder, Work family, envelope, measures, qualification window, evidence, and currentness. If existing capability is adequate and no relevant capability change is required or asserted, retain it as a reliance or observation condition; no development result is needed. A missing capability basis returns that A.2.2 question, not an automatic development prescription. Only when a capability-change claim is needed, consume a compatible E.23.CDI or domain development result naming holder, Work family, baseline, target, intervention, representative transfer Work, evidence, and currentness. If that required result is missing or stale, name the gap and the next governing development decision or stop; A.3.1.MI does not fill it.

  5. Bound authorization and protected conditions. Recover the authorization rules that apply to each intended change. Identify the deciding System and any assignment, permission or authority relation those rules use, with its participants and scope. If a particular decision Work is asserted, recover A.13 and independently A.15.1, with F.6 only for precise assignment-bound attribution. Name participating Systems, confidentiality and safety stops, and protected conditions. Expertise, sponsorship, project position, ownership, tool control, assignment, permission, and authority are not interchangeable bases.

  6. Plan decision-relevant observations before intervention. Select only positions that can change the decision: acceptability or rejection; appropriateness or fit; feasibility; enactment or fidelity; burden or cost; reach; sustainment; changes to named targets or to the introduction strategy; and the outside result. Keep acceptability as a stakeholder observation, formal fit or transfer with A.3.1.FT, enactment with A.15.1, bounded reach as observed participation, and a population-level continuation question with C.36.MC. Preserve A.3.1.WT trial, A.3.1.FT fit, and C.11.MV worth questions as distinct inputs or later uses. Use §4.5 when selecting these observations requires distinguishing delivery, mechanism, adaptation and context explanations.

  7. Plan separate target and introduction-strategy adaptation records. First classify every planned or observed modification as a change to the Method-related target or a change to the way it is introduced. Record what changed, when, planned or reactive status, decision-maker and any applicable authorization predicate, affected level, reason and conditions.

    For a target change, name the affected Method semantics, description, support, capability input, fit claim, cultural question, or local-use condition. For an introduction-strategy change, name the admitted introduction Method or candidate introduction account, its admissibly classified description episteme, and any separate WorkPlan claim. An adaptation does not by itself change the kind or status of an account, description, plan, Method or Work.

    Return each modification to its own maintained result or local stop: A.3.1.MV for admitted Method semantics or candidate lineage; A.3.2.DE for a MethodDescription correction or improved candidate-account content, retaining the applicable subject and status; another named episteme or a local A.3.1.MI stop for other content; A.15.8.MS for support; A.15.2 for a WorkPlan; A.3.1.FT for fit; or C.36.MC for a population cultural question.

  8. Perform and admit introduction Work. Recover actual performers and A.13 bases, the independently admitted Method enacted by the introduction Work, action history, temporal extent, containing System, named changed subjects, used Systems, and relied-on relation occurrences. Use F.6 through the same obtaining A.13 assignment only when precise assignment-bound attribution is needed. Record the result as an attempt intended to establish named conditions. A completed failed attempt remains Work even if access, usability, or later enactment did not result. A candidate introduction Method is not enacted; name only the admitted Methods followed.

  9. Observe later actual Work, failed entry, and non-use. Admit later Work independently. Record which admitted Method was enacted, or preserve candidate status and name only separately admitted Methods enacted. Also record failed entry, rejection, non-use, workaround, adaptation, support demand, and burden when observed; absence of a record is not automatically non-use.

  10. Compare every selected position. For each target, introduction-strategy object, and decision-relevant observation, state supported change, no change, uncertainty, inapplicability, or missing evidence. State the particular maintained claim or edition and next action. If a continuing subject is claimed to have changed, use A.3.4; a before/after table or performed Work alone does not establish that transformation.

  11. Use C.28 for causal reliance. Return observations or association at their supported strength, with the limit needed by the receiving decision. When that decision relies on a causal or contribution claim, use current C.28 for the bounded causal-use question, supported use, unsupported stronger use, population and conditions, validity threat and reopen trigger. Name a contribution relation or compound claim only with its predicate, participants, applicability, and obtaining basis. C.28 settles causal support; A.3.1.MI still makes the bounded revision decision.

  12. Decide and return observations. Return keep, revise, branch, replace, stop, or a retained set with its limitation and any supported present course. Select a further observation or probe through C.11.DUA only when its obtainable result could change the decision enough to warrant its full burden and the needed window, access and authority are available. Use A.3.2.DE when the observation requires correcting a MethodDescription or candidate Method account. Its candidate branch returns improved content with unresolved identification conditions retained. Other description content returns to its own episteme or a local stop. Send other observations to A.3.1.MV, A.15.8.MS, A.15.2, A.3.1.FT, C.36.MC, a named capability-development result, another admissible maintained result, or a receiving Agent only when the particular claim or edition and next action are stated; otherwise keep the observation as a local decision or stop.

  13. State limits and refresh. State the scope supported by this introduction account, keeping the separate grounds of any causal, cultural or authorization claim used in the decision. Reopen when the setting, population, target, introduction-strategy or description status, separate WorkPlan, capability and support conditions, named authorization basis, alternative, outside result, evidence window, or maintained claim changes.

A.3.1.MI:4.2 - Record the Result

Keep the smallest account that lets the receiver make the bounded decision. The ordinary account in §0 and the Harbor application can suffice. The positions below expand that account when its claims require them; use the applicable content, not a compulsory inventory of unrelated objects. In particular, preserve candidate status and the admission conditions of any claimed Method or Work. Observation alone does not upgrade those claims.

Result positionRequired content when this position is used
introduction useReceiving practice, outside result, target admitted-Method or candidate-account status, setting, population, period, qualification window, decision, and stop.
changed subjectsNamed admitted Method, claim-bearing episteme, representation, System, capability bearer and result, Work occurrence, domain entity, organizational System, or selected structure claimed.
candidate accounts and descriptionsCandidate status, proposed claims, separately identified descriptions and representations, and missing admission basis.
relied-on relationsFor each relied-on assignment, permission, authority, access, use, enactment or other relation: named predicate, participant meanings, participants, applicability, obtaining basis, and interval when material.
maintained results and receiving actionsMaintained result, particular claim or edition, status, evidence, source and window, supporting or defeating observation, receiving Agent or governing pattern when current, and next action or stop.
capability branchOmit when decision-irrelevant. Otherwise retain the current A.2.2 basis for adequate existing capability without a development requirement, or return the missing capability basis. When a capability-change claim is needed, consume the compatible development result with holder, Work family, baseline, target, intervention, transfer Work, evidence and currentness; if required but missing or stale, name that development gap and next governing decision or stop.
introduction strategyAdmitted introduction Method or status-preserved candidate introduction account; its maintained result; a candidate description episteme before admission, or a U.MethodDescription only after A.3.1 admission and A.3.2 classification; any separately governed WorkPlan; intended conditions, version and window, evidence, and strategy modification kept separate from target modification.
introduction and later WorkSeparately admitted actual Work, performers, enacted admitted Methods, history, extent, containing Systems, changed subjects, relation occurrences, results, failed entry, non-use, and gaps.
decision-relevant observationsSelected acceptability/rejection, appropriateness/fit, feasibility, enactment/fidelity, burden/cost, reach, sustainment, target-change, and outside-result positions, each with its own subject, claim, evidence, disposition, and next action.
adaptationTarget or introduction-strategy classification; what changed and which target, strategy, description, or separate WorkPlan it changed; the recorded kind and status of each affected item; when; planned/reactive status; decision-maker and any applicable authorization predicate; affected level; reason and conditions; maintained result; and receiving action or stop.
causal reliance, when neededC.28 question and result, supported use, unsupported stronger use, conditions, validity threat, residual uncertainty and reopen trigger. Observation or association limits stay in the substantive result where they matter to its use.
returnkeep, revise, branch, replace, stop, or retained set; particular maintained claim or edition affected; local decision, named receiver, or stop; any selected next observation; bounded non-use and reopen condition.

A.3.1.MI:4.3 - What Changes in Practice

Teams stop reporting that a Method was “rolled out” and start distinguishing the Method-related target, the introduction strategy and its status, its description, any separate WorkPlan, performed introduction Work, later Work, named relied-on relations, and separate observations. An introduction attempt can be completed without establishing the intended conditions. A favourable outside result can remain useful without filling every observation position or becoming causal proof.

Revision becomes local. A stale target description, unsuitable target variant, failed support relation, missing capability result, weak introduction strategy, stale strategy description, unworkable WorkPlan, or local-use adaptation can be reconsidered through its own maintained claim or edition without repeating or rejecting the entire programme.

A.3.1.MI:4.4 - Constructed Introduction Case

Calibration-Team-B wants to reduce mixed-unit release escapes. It selects admitted target Method M-Unit-Review-1 from A.3.1.MV for a D30–D60 bounded attempt; candidate target C-M-Unit-Review-Approx-1 remains outside. The changed target subjects are MethodDescription edition 4, its repaired representation, verified conversion-table System ConversionTable-B, and the assigned pre-release review Work. Separate claim-bearing results state the intended local selection and support conditions. No new organizational System or selected structure is inferred from the team label.

The introduction strategy is separately admitted Method M-Introduce-Unit-Review-1: configure the description and representation, establish and check table access, brief the reviewer on the changed distinctions, and observe one review. MethodDescription-Intro-B-1 has that admitted Method as its one EntityOfConcern, and A.3.2 classifies it as a U.MethodDescription; WorkPlan-Intro-B-1 separately schedules this bounded use. Neither episteme is the target Method or the later review Work.

CDI-R22-1 names holder Reviewer-22, calibration-report-review Work, the mixed-unit report envelope, baseline detection results, target four-of-four seeded unit cases, supervised practice and representative transfer Work, qualification evidence, and currentness through D60. A.3.1.MI consumes this result; it neither treats attendance as capability nor performs the development.

MethodEngineer-B is independently admitted as an Agent for local Method-configuration Work. ASG-Intro-B-1 is an obtaining occurrence of the declared MethodConfigurationAssignment species: its holder is MethodEngineer-B, and its assigned-kind participant is MethodConfigurationRoleKind from the species’ admitted local kind domain. Its extent is D30–D60 and covers W-Intro-B-1; the species’ predicate and identity conditions are assumed satisfied in this constructed case. Independently obtaining permission PERM-Intro-B-1 permits MethodEngineer-B to configure MethodDescription-4, Representation-4, and ConversionTable-B. Release authority remains with ReleaseDecider-B; neither assignment nor permission transfers it to the reviewer, engineer, or tool.

Authorized W-Intro-B-1 is admitted as Work performed by MethodEngineer-B inside containing System Calibration-Team-B; it enacts M-Introduce-Unit-Review-1, configures the selected target description and representation, establishes access to ConversionTable-B, briefs the reviewer, and records the assignment and authority boundary. The Work is intended to establish those local conditions. If access configuration fails, the introduction Work still occurred but the support condition did not obtain. If the briefing or sequence proves unusable while the target Method remains adequate, the affected result belongs to M-Introduce-Unit-Review-1, MethodDescription-Intro-B-1, or WorkPlan-Intro-B-1, not to M-Unit-Review-1.

Later W-B-Review-1 is independently admitted as Work performed by Reviewer-22; it enacts M-Unit-Review-1, detects a seeded Celsius/Kelvin mismatch, stops the release recommendation, and records fourteen minutes and one lookup. The observation positions remain separate: the reviewer accepts the local use; appropriateness is supported only for the named report family; table access and completion show bounded feasibility; the recorded operations support enactment for this Work occurrence; fourteen minutes and one lookup are burden observations; reach is one holder and one Work occurrence; sustainment is unknown; and one corrected report is the outside result. No adaptation occurred in this replay.

Return keep for the D30–D60 attempt on the observed local conditions, later Work, mismatch detection and corrected report. The result supports that bounded continuation. A later claim that either Method caused fewer release escapes needs C.28 and the evidence for that stronger use.

If table access failed, return the support-gap account and any warranted correction to the maintained A.15.8.MS result. If the introduction sequence or briefing failed, return the observation to the maintained claim in M-Introduce-Unit-Review-1, MethodDescription-Intro-B-1, or WorkPlan-Intro-B-1 and keep the target result separate. If CDI-R22-1 expired, name that result and stop pending its governing development decision; if later Work changed reusable target or introduction semantics, reopen A.3.1.MV for the affected Method.

If the failed lookup path has two proposed later repairs that the available evidence cannot distinguish, and no useful comparative observation is obtainable before the current decision, return both options with that limit and keep the failed support route stopped. Return the account of the support failure, any contradicted claim and the options to A.15.8.MS. This completes the current introduction result; further comparison is selected when its obtainable answer warrants the full burden.

In a separate constructed no-development case, the same admitted review Method is introduced to Reviewer-23 by repairing the conversion-table lookup path. The current A.2.2 basis CAP-R23-1 identifies that holder, calibration-report-review Work, the mixed-unit envelope, the required detection measure, representative evidence, and a qualification window covering the attempt. It supports adequate existing capability; no capability change is required or claimed. The engineer repairs and checks the lookup path under separately supported configuration permission, and the independently admitted later review Work uses it successfully. Return keep for this bounded support change and preserve CAP-R23-1 as a reliance condition. No CDI result is missing merely because none was supplied, and no training is commissioned. If the capability basis later expires, return its currentness question to A.2.2; if the Work envelope instead changes so that development is needed, open that separately governed question. This case changes neither the reliance on CDI-R22-1 nor its expiry stop in the preceding case.

A.3.1.MI:4.5 - Explain a changed result before selecting an adaptation

Use this continuation when an unexpected result, changed setting or proposed adaptation leaves materially different explanations that would change the next application. Existing observations and a supported local correction may already settle the decision; a new study is not required merely because some causal uncertainty remains.

  1. Recover how the proposed contribution is expected to work. Connect the needed result to the function each relevant contribution serves, the concrete actions or form that supply it, and the conditions under which the proposed mechanism could operate. Read the target and the introduction strategy separately. For example, a rehearsal may be intended to develop recognition of a stop condition, whereas an expert checking the completed result may supply that recognition directly. Use C.28.CM and the relevant subject practice to construct or challenge this explanation. Keep assumptions and unknown functions visible. Preserving a function does not by itself preserve Method identity.

  2. Derive observations that could distinguish the live explanations. Compare what should be seen if the relevant contribution was not delivered, was delivered but did not activate the proposed mechanism, operated differently in this context, or was supplemented by another contribution. Several explanations may hold together. Link observations of actual actions, the proposed intermediate change and the outside result for the same cases and relevant times. Include failed entry and cases where the result differs. A procedure-completion count alone cannot decide among these explanations. Assess fidelity only against an interpretable baseline and only when that comparison can change the decision; unknown essential functions or an intentionally flexible strategy may support a narrower account of what was done instead.

  3. Select an attainable comparison. First ask whether existing evidence distinguishes enough for the receiving action. If a further inquiry is worthwhile, construct or obtain a design tied to the competing explanations, expected observations, case differences, timing, available access and whole burden. It must explain which attainable contrast can distinguish the accounts, what remains unresolved, and how the material can be obtained and interpreted under the permitted conditions. Give the selected design, its limits and the required operational protocol to the A.3.1.WT trial or other applicable inquiry. When that construction exceeds the trial Method, obtain the missing research contribution through A.15.9; the subject inquiry retains its own Method, qualifications and authority. Check separately whether the proposed application can be performed and whether the evaluation can obtain an interpretable answer. Specify which changes the design permits: holding a configuration stable and studying an adapting configuration answer different questions. If no useful comparison is attainable, return the supported course or unresolved alternatives with the limitation that matters now.

  4. Combine observations through the explanation. Use the selected methods to recover what was delivered, how participants used or responded to it, the pertinent context and the resulting benefit, harm or burden. Where broad records show a pattern, selected observations or interviews can investigate the difference; where a particular account suggests a mechanism, look for its expected consequences in the relevant records. Repeated observation can reveal a changed contribution or context. Keep the same cases, periods and measurement meanings recoverable when combining results. Separate an observation, a participant’s explanation and the investigator’s inference; use C.28 for any resulting causal reliance.

  5. Make each adaptation interpretable. Compare the actual change with its prior target or introduction-strategy baseline. Recover the affected action or component, proposed function, reason, decision-maker and any applicable authorization, conditions, decision time and actual implementation time when their difference matters. Keep coupled changes together when their contributions cannot be separated. Determine what supports a claim that the function was retained, changed or remains unknown. An adaptation description supplies neither that functional conclusion nor an effect estimate. Return changed reusable operations or conditions to A.3.1.MV even if the intended function stays the same.

  6. Return what the evidence changes. A.3.1.FT receives the conditions and configuration examined; C.11.MV receives comparable consequences, support demand and displaced work; A.3.1.MV receives the semantic change with separately qualified function and evidence; A.3.1.MI receives the basis to retain, refine, branch, replace or stop the target, its introduction, or their support. A favourable result despite poor delivery may support investigating another contribution; it neither confirms the proposed mechanism nor makes all useful work a failure. A new supported explanation or useful alternative may warrant development without contradicting the earlier bounded account. Revisit uses whose relied-on premises change through their governing patterns. Use F.0.2.RC when the change affects a source-coverage or reconstruction claim.

The result is an explanation sufficient for the named next action, with its evidence and unresolved alternatives. It can be a bounded continuation, a changed introduction strategy, a proposed target variant, a useful refinement of the explanation, or a stop. Additional detail is selected for the decision it can change.

A.3.1.MI:5 - Archetypal Grounding - Workplace Introduction and Revision

The SSFD programme reports a three-year intervention involving more than 300 engineers, training followed by supported four-to-six-month workplace projects, expert assistance, 72 reports recording SSFD use, and 41 reports supporting deeper analysis. Use this account to distinguish the target, strategy, performed Work, observations, adaptations, and outside results; it is not evidence from an isolated causal experiment.

Treat training followed by supported four-to-six-month workplace projects and expert assistance as a source-described candidate introduction strategy unless independent A.3.1 admission is available. Keep that candidate introduction account, its available description epistemes and separate plans, the SSFD target Method or candidate account, capability evidence, project Systems, performed Work, later reports, named assignment or use relations, target adaptations, strategy adaptations, burdens, and domain results separate.

If an observation exposes a content defect in the candidate introduction account, A.3.2.DE can improve that account without classifying it as a U.MethodDescription. Other description content returns to its own episteme or a local stop; introduction or use alone requires no revision.

Record acceptability or rejection, appropriateness or fit, feasibility, enactment or fidelity, burden or cost, reach, and sustainment only where the source supports each position. The reports do not admit the candidate introduction Method or make every modification a target-Method change. The bounded A.3.1.MI decision can use observations or association without C.28; any claim that SSFD or its introduction strategy caused the reported benefits needs a current C.28 result.

The Digital Vaccine case supplies three sequential action-research cycles in an operating health-services ecosystem. For each cycle, record the Method-related target, the introduction strategy and its status, its separately identified description, and any separate WorkPlan. Then record prioritization, performed introduction or validation Work, observation, target adaptation, strategy adaptation, and revision for the bounded concern. The evaluation remains ex ante and case-specific and establishes neither Method admission, long-term effect, nor transfer to the other elicited domains.

The Halogen and methodology-spread studies add observed adaptation, project demands, practitioner skills, identified organizational conditions where recoverable, drivers, and barriers. For each adaptation record whether it changed the Method-related target, the introduction strategy, its description, a separate WorkPlan, support, or local use, while preserving the recorded kind and status of each. Also record when, planned or reactive status, decision-maker and any applicable authorization basis, affected level, reason, and conditions. Use these observations for adaptation and spread questions; causal reliance requires C.28.

Implementation-science comparators sharpen this account without supplying its domain ontology. Proctor et al. motivate separate acceptability, appropriateness, feasibility, enactment/fidelity, burden/cost, reach, and sustainment questions. FRAME motivates recording changes to the Method-related target. FRAME-IS supplies the separate question of what changed in the introduction strategy itself. Updated CFIR motivates context and determinant questions; the 2021 MRC framework motivates iterative refinement around key uncertainty and decision usefulness. A.3.1.MI uses these comparators to distinguish the target, the introduction strategy and their observed effects. Method admission, Work, relation, capability, authority and cultural claims retain their separate FPF grounds.

A.3.1.MI:5.1 - APP-ME-01 Early Stop

The EC-417 three-release statement remains a WorkPlan. A claim that introduction occurred requires independently admitted introduction Work; a release-enactment claim requires the release Work separately. Recover each claimed occurrence’s performers and A.13 basis, enacted admitted Methods, extent, containing System and relied-on relations under A.15.1. Capability, permission, authority, adaptations, burdens and domain results need their own grounds when the receiving claim depends on them. Later revision, cadence effect and receiving-result claims are also separate. Completion of introduction does not have to wait for release, and neither occurrence can be inferred from the three-release plan.

The A.15.8.MS support-use task observations may supply identified support baselines and gaps. They do not establish an introduction Method, release Work, AI-provider use, feedback Work, capability, or Method fit. Preserve C-EC-Release-v2 as a target candidate and CUR-EC417-CadenceEffect-1 as unsupported. The application has no supplied A.2.2 capability basis, so a receiving decision that relies on capability returns that missing basis first. If a current adequate basis is supplied and no capability change is needed, retain it without requiring development. Name E.23.CDI or a domain development result and next action only for a needed capability change; do not invent capability or prescribe development from the gap alone.

A.3.1.MI:5.2 - Correct outputs with an undelivered learning mechanism

In this constructed example, a team introduces a report-review Method requiring the reviewer to trace each measurement to the equipment identifier and check its unit before recommending release. The proposed introduction strategy combines a lesson with individual rehearsal. Its working explanation is that rehearsal will enable newcomers to recognize identifier and unit mismatches independently. Release still requires a separately qualified reviewer; the introduction attempt has no authority to remove that safeguard.

Records show that the lesson occurred, but individual rehearsal was repeatedly cancelled. Reports released during the attempt have the required corrections. Observation of review meetings shows that experienced colleagues identified the mismatches and newcomers then corrected them. The attendance records and corrected reports therefore concern different contributions: neither establishes independent newcomer capability. The proposed learning mechanism remains unsupported, while the experienced reviewers’ identification of the mismatches is a useful observation.

The method engineer connects delivery records, the sequence of detection and correction, current capability evidence and report outcomes. This supports continuing the existing safeguarded review under its established conditions. It also identifies a rival explanation worth considering: supported joint review may supply the immediate checking function while creating a different opportunity for learning. Whether newcomers learn from that participation remains an open question.

Suppose a receiving decision now concerns assigning newcomers independent reviews next month. A feasible comparison uses archived reports with known mismatches, including an unfamiliar unit convention, and records each newcomer’s answer before help, the help given and the final correction. The inquiry designer must justify case coverage, comparison, timing, assessment and attainable burden; merely scheduling the exercise is not a result. If the protected inquiry window is unavailable, independent assignment stays unsupported and the existing review can continue.

After such an authorized comparison, suppose the observed records show that newcomers detect familiar identifier mismatches unaided but require expert help for the unfamiliar unit convention. Return that differentiated result to the capability owner and to A.3.1.FT; it supports neither a blanket failure nor unrestricted transfer. C.11.MV includes the expert’s time. A.3.1.MI can develop a proposed introduction variant using joint review and later independent rehearsal. A.3.1.MV determines whether its changed reusable operations constitute a variant; retaining the intended checking and learning functions does not settle that identity question.

The adaptation account records when the joint-review change was chosen and when it operated. If rehearsal and coaching change together, report the benefit observed under that examined arrangement; distinguish their contributions only to the extent supported by the evidence. The original lesson remains a delivered event. Its proposed mechanism is reconsidered on the new evidence; the history is not rewritten as if the later strategy had been used from the start.

A.3.1.MI:6 - Bias-Annotation

BiasLikely driftRepair
rollout-compression biasTarget subjects, introduction strategy, descriptions, plans, relations, Work, and observations become one “introduction”.Keep the typed target account, strategy and its status, description, any separate WorkPlan, performed Work, named direct relations, and observations distinct.
success-presupposition biasCompleted introduction Work is said to make the Method available and usable.State the intended conditions; later observations may return success, failure, uncertainty, or missing evidence.
training-as-capability biasAttendance or expert help becomes a holder capability.Recover the A.2.2 capability basis and currentness. A capability-change claim additionally needs its compatible development result; preserve adequate existing capability without inventing a development need.
availability-as-use biasPublished material or a configured tool becomes later enactment.Admit actual Work and the named enactsMethod or use relation independently.
authorization compressionExpertise, sponsorship, project position, ownership, assignment, permission, and authority become interchangeable.Name the predicate, participants, scope, and positive basis for each relied-on relation.
outside-result attribution biasA favourable domain result fills every observation position and becomes causal proof.Compare each selected position; use C.28 only when the decision relies on causality.
adaptation-smearing biasA local workaround silently changes the target, introduction strategy, descriptions, WorkPlan, support, and fit together.Classify the modification as target or introduction-strategy change and return only the maintained account, description, WorkPlan claim, support claim, fit claim, or local decision affected.
lifecycle biasIntroduction, reach, and later use become compulsory adoption stages.Keep A.3.1.MI independently enterable and use C.36.MC only for a bounded population-level cultural question.

A.3.1.MI:7 - Conformance Checklist

  • Claimed target subjects, the admitted introduction Method or candidate introduction account, any relied-on description, any separate WorkPlan, performed Work and relied-on relations are distinguished. A description is classified as U.MethodDescription only when A.3.2 establishes membership for an admitted Method.
  • Every organizational claim names the organizational System, selected structure, constituent organization, or relation organization relied on.
  • For each decision-relevant observation, state what it supports and the next action or stop; name a maintained result, particular claim or edition, and receiving Agent or governing pattern when that return is current.
  • Introduction Work is stated as an attempt intended to establish named conditions, with any applicable authorization basis kept separate. A failed attempt remains recordable as Work.
  • Decision-relevant capability keeps its A.2.2 basis and currentness, or returns the missing basis. Adequate existing capability without a needed change requires no development result. Only a needed capability-change claim consumes a compatible development result or returns its missing/stale basis with a next governing action or stop; irrelevant capability detail is omitted.
  • Assignment, permission, authority, access, use, enactment, and other relations name predicates, participants, scope, and obtaining basis.
  • Later Work is independently admitted; candidate accounts are not enacted, and only independently admitted Methods may fill an enactment claim.
  • Decision-relevant acceptability/rejection, appropriateness/fit, feasibility, enactment/fidelity, burden/cost, reach, sustainment, target-change, and outside-result observations remain separate.
  • Every adaptation distinguishes target change from introduction-strategy change and records the affected target, strategy and status, identified description episteme, separate WorkPlan, support or local-use condition; time and planned/reactive status; decision-maker and any applicable authorization; level, reason and conditions; maintained result; and receiving action or stop.
  • A relied-on causal or contribution claim uses C.28 and preserves supported and unsupported uses, validity threat and residual uncertainty. An observational result carries only the qualification needed for its receiving use.
  • The comparison records the action supported by the available evidence, or the alternatives that remain unresolved and the reason they cannot yet be distinguished. Any further observation or probe has a useful obtainable answer worth its full burden and feasible conditions.
  • A.3.1.FT receives a bounded fit or transfer question, C.36.MC a bounded population-level cultural question, and A.3.1.MV/A.15.8.MS/A.15.2 a supported correction, refinement or alternative tied to the particular maintained claim or edition it affects. A.3.2.DE receives a needed correction of MethodDescription or candidate-Method-account content and preserves its status; other content returns to its own episteme or a local stop.
  • The introduction account and any causal, cultural or authorization conclusions retain their own grounds and scope.

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

Anti-patternRepair
“We trained everyone and rolled out the Method.”Name the actual training or development result, introduction Work, later Work, and any missing observation that the receiving decision needs.
“The tool was available, so the Method was used.”Recover actual performer Work, enacted Method, direct tool-use relation, and result.
“Management sponsored it, so the team was authorized.”Recover assignment, permission or authority, Agent basis, and scope separately.
“Results improved after launch, so the Method caused them.”State timing, alternatives, covarying changes, contribution basis, and residual uncertainty.
“Several projects used it, so the culture adopted it.”Use C.36.MC only when a named cultural relation and population evidence exist.

A.3.1.MI:9 - Consequences

Method introductions become observable interventions. Teams can learn from use, non-use, adaptation, and outside consequences while keeping the target, introduction strategy and its status, description, any separate WorkPlan, support, capability, authority, identified organizational Systems or selected structures, Work, and domain changes distinct.

The cost is a more explicit baseline and observation design. Some programmes end with bounded association and residual causal uncertainty, and a capability gap can stop introduction even when training was delivered.

A.3.1.MI:10 - Rationale

An intervention can change several subjects, relations, and descriptions at once. Learning requires each claimed change to retain its own subject, governor, baseline, evidence, and receiving use. Otherwise the intervention label becomes a substitute for both Work and explanation.

Separating the Method-related target from the introduction strategy, its status and description, any separate WorkPlan, capability development, and cultural continuation prevents A.3.1.MI from becoming an adoption lifecycle. It remains the practice for introducing one bounded Method-related change, observing later Work and consequences, and using the resulting evidence to correct, refine or develop the particular maintained account or next application.

A.3.1.MI:11 - SoTA-Echoing

SourceContributionTransfer limit and practitioner implication
Yildirim, Campean, and Uddin, function-modeling evaluation in industry practicetraining, expert assistance, four-to-six-month workplace projects, later report analysis, application variety, limitations, and direct/indirect contribution as separate introduction and observation positions.One automotive OEM, retrospective reports, and SSFD within a broader methodology establish neither isolated causality nor capability.
Tsai, Zdravkovic, and Söder, DBE-design Method action researchprioritization followed by three plan-perform-evaluate cycles as a naturalistic revision structure.The evaluation is ex ante and case-specific and does not establish long-term organizational effect, causal superiority, or transfer.
Schønheyder and Nordby, design-Method use and evolution in professional practice, and Hiort af Ornäs et al., drivers and barriers in methodology spreadobserved modifications, project and skill conditions, identified organizational conditions where recoverable, drivers, and barriers as observation and revision questions.Observations from one firm and one interview study do not by themselves establish the causes of spread.
Proctor et al., Outcomes for Implementation Researchkeep acceptability/rejection, appropriateness/fit, feasibility, enactment/fidelity, burden/cost, reach, and sustainment as decision-relevant observation positions distinct from the outside result.The source categories do not establish FPF health-service/client kinds, cultural adoption or a compulsory outcome set or stage order. Use only positions that can change the bounded decision.
Stirman, Baumann, and Miller, FRAMEfor a Method-related target, record what changed, when, planned/proactive or unplanned/reactive status, decision-maker and applicable authority, affected level, reason and conditions, and whether Method semantics, description, support, or local use changed.Fidelity labels do not establish Method identity or admission, and healthcare intervention kinds do not become FPF kinds. Return each target modification to its particular maintained claim or local decision.
Miller et al., FRAME-ISdistinguish modifications to the introduction strategy from modifications to the Method-related target; for the strategy, record the changed component or function, nature, timing, participants in the modification decision, rationale, and scope.Healthcare intervention and implementation-strategy kinds are not imported as FPF kinds; neither Method admission nor a compulsory reporting module follows. Record the introduction strategy’s status and keep its description, any WorkPlan, performed Work, and affected maintained result separate.
Damschroder et al., updated CFIRask which context and determinant observations can explain anticipated or actual success or failure.Select context and determinant questions for the receiving use; establish any claimed FPF relation through its own predicate and grounds.
Skivington et al., 2021 MRC complex-intervention frameworkidentify key uncertainty, context interaction, refinement, stakeholder perspective, and comparative resource/outcome consequence; permit repeat, reconsider, or stop.The framework does not impose a phase sequence or gate on this Method. The source supplies a framework for inquiry; use C.28 for causal reliance.
Moore et al., MRC process-evaluation guidance, and Jolles et al., core functions and formsconnect the proposed explanation to observations of implementation, mechanisms, context and outcomes; distinguish a contribution’s function from its concrete form.Recover the subject-specific function and the evidence for its preservation; an observed benefit does not confirm the originally proposed mechanism.

A.3.1.MI:12 - Relations

  • C.39.MF supplies the Method-of-interest and outside result. A.3.1.MV supplies an admitted variant or status-preserved candidate lineage with applicability and currentness. A candidate account is not enacted; later Work may enact only independently admitted Methods.
  • A.3.1.MV governs admitted Method semantics and candidate lineage, provenance, evidence, applicability, currentness, and retirement claims for both target and introduction accounts. A.3.2.DE authors or revises a MethodDescription of an admitted Method, or improves a candidate Method account while retaining its unresolved status. Other description content stays with its own episteme. A.15.2 governs the separate introduction WorkPlan; A.15.8.MS particular support claims; A.3.1.FT bounded fit and transfer questions; and C.36.MC bounded population-level cultural questions. Return a correction, refinement or alternative with the affected maintained claim or edition and the next action.
  • E.23.CDI or a domain capability-development pattern governs capability change. A.2.2 governs the relied-on capability result; A.3.1.MI records it as an input, observation, or named gap.
  • A.3.1 governs admission of both target and introduction Methods, and A.3.2 governs U.MethodDescription membership. A WorkPlan and performed Work neither admit nor enact a candidate Method. A.13 governs precise Agent claims and A.15.1 every introduction and later Work occurrence. Assignment, permission, authority, access, use, enactment, and other direct relations retain their own named predicates, participants, applicability, and obtaining tests.
  • A.3.4 governs a claimed actual bounded change to a continuing subject. Introduction Work, a before/after account, an adaptation record, or a decision label does not by itself identify a U.Transformation.
  • A.10 governs evidence use. When the A.3.1.MI decision relies on a causal or contribution claim, C.28 governs the bounded causal-use question, supported and unsupported uses, conditions, validity threats, and reopen trigger. Without that reliance, A.3.1.MI stops at observation or association.
  • C.28.CM develops the proposed causal explanation and its rivals. A.3.1.WT can construct the bounded Method trial; a different or more extensive inquiry needs its own qualified design and operational protocol. A.15.9 obtains and qualifies any missing outside-practice result for this use. The selected design and protocol guide the actual trial or inquiry. Its obtained observations and their limits then inform the bounded introduction decision; A.3.1.MI:4.5 explains this connection for adaptation. F.0.2.RC is used when a change affects a source-coverage or reconstruction claim.
  • The implementation-science comparators inform the selected introduction and observation questions. FRAME and FRAME-IS distinguish target changes from changes in their introduction; the corresponding FPF subjects and claims retain their own identification and evidential grounds.

A.3.1.MI:End

A.3.2 - U.MethodDescription: Description Episteme for a Way of Doing

Type: Definitional pattern Status: Stable Normativity: Normative

A.3.2:1 - Problem frame

Use this pattern when practitioners need reusable claims about how one Method is carried out and must keep those claims distinct from the representation, publication, approval, plan, or actual Work through which the Method is discussed or enacted. In FPF terms, decide whether an already identified U.Episteme is a U.MethodDescription: whether its EntityOfConcern is one admitted U.Method and its claims say something substantive about that Method as a way of doing.

When the reusable way is only a candidate. A candidate account or mined behavioural model is not a U.MethodDescription merely because it is coherent, executable, process-shaped, or traceable to sources. Use A.3.1.MR when the question is recovery from performance evidence; use A.3.1 when a candidate is ready for Method identification. Positive U.MethodDescription membership requires an admitted U.Method as that episteme’s EntityOfConcern and at least one substantive claim about the Method as a way of doing.

Plain reading. A method description is the knowledge object whose claims say how one identified method is done. Code, text, or a diagram may represent those claims; a publication occurrence may make an edition available.

Recognizable working moments include:

  • a maintenance team comparing a revised procedure with the method used to plan the next service window;
  • a clinical team selecting a triage guideline while keeping guideline claims, approval, and patient-specific work separate;
  • a production-planning team comparing scheduling-method claims while the MILP representation and solver runs change.

Object being classified. A.3.2 examines one already identified claim-bearing U.Episteme candidate and judges whether that same individual belongs to the dependent kind U.MethodDescription. For positive membership, the candidate episteme’s C.2.1 EntityOfConcern must resolve to one admitted U.Method, and at least one of its claims must concern that Method as a way of doing. The Method is the internal subject of the episteme’s claims, not a second candidate and not the object being classified. A.3.2 adds neither another episteme identity nor a binary description relation.

First useful move. Name the candidate U.Episteme. Check two things: its C.2.1 EntityOfConcern is one admitted U.Method, and at least one claim says how that Method is done. If both hold, the same episteme is a U.MethodDescription; if either condition is false, it is not. If the basis does not establish whether a condition holds, leave membership unresolved.

Only then, if someone proposes a concrete further use, write that use’s criterion and result as a separate subject assertion under its predicate, with an optional subject-pattern locator. Otherwise stop at membership.

What goes wrong if missed. A visible file or diagram is classified by its form, a mere mention is mistaken for a description, or an episteme about a relation structure among several Methods is treated as if it described one composite Method. Planning, enactment, audit, and review then rely on the wrong object.

What this buys. The project can identify, compare, revise, and reuse claims about one Method while keeping representation, publication, planned use, enactment, and evidence use distinct.

Not this pattern when. Do not infer membership from words such as algorithm, program, proof, workflow, process, procedure, recipe, or model. Ask what the sentence asserts. If its EntityOfConcern is not an admitted U.Method, or it says nothing substantive about that Method as a way of doing, U.MethodDescription membership does not hold. Use the subject pattern for any further claim about the Method, selected structure, formal declaration, work plan, dated Work, evidence use, or publication use.

A.3.2:2 - Problem

Without the U.MethodDescription distinction, projects collapse several different claims:

  1. Description as run. A flowchart, repository, executable, lab protocol, or solver file is treated as if it were the dated work occurrence.
  2. Description as method semantics. A notation or file is treated as the method itself, so equivalent descriptions look like competing methods and different methods can hide behind one document name.
  3. Description as plan or authority. A protocol, dashboard cue, gate-looking entry, or approved procedure note is treated as a work plan, permission, gate passage, or evidence result.
  4. Description as declaration, mechanism, or formal substrate. A proof script, algorithm, model, or rule set is treated as if it already were a RelationSignature, an A.6.1 operation declaration, a mechanism law set, or a mathematical substrate.
  5. Imperative overread. A declarative representation, graph path, query plan, constraint model, or state predicate is interpreted as an ordered work-control claim.
  6. Subject identity and description equivalence collapse. Two epistemes that concern the same method are treated as equivalent despite incompatible claims, or a notational difference is used to fork method identity without the A.3.1 reidentification rule.

A.3.2:3 - Forces

ForceTension this pattern resolves
Representation versus method semanticsMany representations can describe one method; one representation can also carry other claims.
Reuse versus enactmentA method description should be reusable before any particular work occurrence happens.
Precision versus notation pluralitySOPs, code, proof scripts, solver models, process models, and lab protocols can all be useful without forcing one algorithmic paradigm.
Reviewability versus overclaimA description may be reviewable and executable, but that does not make it evidence, authorization, work, or mechanism law.
Identity versus variationVariants, refinements, parameter values, and contextual bridges must be visible enough to prevent silent method drift.

A.3.2:4 - Solution

A.3.2:4.1 - Definition

U.MethodDescription is a same-individual dependent kind of U.Episteme. Membership holds when the already identified episteme has one admitted U.Method as its EntityOfConcern and its claims, interpreted under the effective ReferenceScheme, make at least one substantive claim about that method as a way of doing. Such a claim may state the method’s transformation or enactment concern, generic participant meanings, applicability, precondition, intended effect or preserved condition, bound, or internal method composition. These are claims about method semantics, not planned assignments or actual participation. Naming the method, giving bibliographic metadata, or stating approval alone does not establish membership.

The C.2.1 claim content, EntityOfConcern, and effective ReferenceScheme remain the identity discriminators of the episteme; A.3.2 adds no second identity. Whether the claims are detailed, current, or reliable enough for a particular planning, enactment, comparison, audit, revision, publication, or teaching use is a separate evaluation. A new receiving use alone neither creates a new method description nor removes membership.

If someone claims empirical grounding, state the C.2.1 EpistemeEmpiricalGroundingRelation. If a proposed use depends on a test, write the tested claim, criterion, evidence path, and result under the evaluation, evidence, or assurance pattern that defines them. Do not add these as method-description fields or let a test change membership.

An assertion or description episteme about one dated Work occurrence may cite methodDescriptionRef when its claim depends on that description edition. Recover each performing U.System and its obtaining assignment of a local agential system-role kind under A.13. Independently admit the Work under A.15.1, including its obtaining enactsMethod relation to the Method. Only when precise assignment-bound attribution is claimed, use F.6 performedUnderAssignment with that same obtaining assignment of a separately declared U.SystemRoleAssignment species.

A.3.2:4.2 - Representation-agnostic stance

Begin with the claim-bearing episteme, then distinguish how its claims are made available:

  • an expression can represent claims through an identifiable correspondence; A.6.3.RT and A.6.3.RT.OE explain its construction, and C.29 applies only when a separate mathematical-representation choice, transfer or reliance question remains;
  • an E.24.PUB publication expression conveys the selected episteme for one bounded use and can conform to a reusable publication form;
  • an independently identified physical or digital carrier bears that expression.

Only the claim-bearing episteme can meet the membership rule in 4.1; keep its representation, form, carrier, and publication occurrence separate.

The representation may use procedural text, code, diagrams, rules, constraints, mathematical notation, or combinations of them. Notation choice does not decide membership. Read each assertion separately: use A.6.0 when reusable declaration content is the current object, C.29 only when a separate mathematical-representation choice, transfer or reliance question remains, A.6.1 or E.20 when it declares an operation family and laws, A.15.2 when it states intended Work, and A.10 or B.3 when another claim relies on it as evidence or assurance.

A.3.2:4.3 - Method-description claim content

The membership threshold is positive but small: at least one claim must answer a method-side question about the way of doing. A name, author, citation, catalogue entry, or approval status does not answer such a question. This threshold distinguishes description from mention; it is not a completeness test for a receiving use.

Name the receiving use before asking whether this method-description edition is adequate for it. A receiving use is not required for U.MethodDescription membership. If no use is current, stop at the membership result and make no adequacy claim.

Proposed useWhere that use belongsWhat to check in this edition
membership onlyA.3.2 judges the already identified C.2.1 epistemeno adequacy judgment; do not fabricate a receiver
preparing planned workA.15.2 is the pattern for the U.WorkPlan; a gate, authority, or evaluation claim stays with its own patterndoes this edition state the applicability, preconditions, parameters, bounds, and stops that the plan cites?
enacting or recording dated workA.15.1 is the pattern for the Work occurrence; its assertion may cite methodDescriptionRef when the edition mattersdoes this edition state the method claims used by that enactment or record? Actual participants and results need their own relations.
comparing, revising, or auditing claim contentC.2.1 identifies each episteme and any persisted comparison or audit result; the concrete evaluation, evidence, or assurance claim stays with its subject patternwhich method claims are preserved, absent, stale, or incompatible for this comparison or audit?
publishing or teachingC.2.1 is the pattern for the claim-bearing or teaching episteme; E.24.PUB is the pattern for publication occurrence and form; use A.15.1 only for teaching Work that happeneddoes this edition preserve the method distinctions needed by this audience or teaching use?

Name the concrete receiving object and the pattern that defines or tests the current claim about it.

Then inspect the claim concerns that matter for that named use:

Claim concernQuestion for the named receiving use
Method describedWhich admitted U.Method is the episteme’s EntityOfConcern, and under which effective reference scheme is it identified?
Transformation or enactment concernWhat way of changing, producing, deciding, learning, or checking does the method organize?
Generic participant and boundary meaningsWhich kinds of entities, resources, conditions, or interfaces may participate in a future enactment, and what method-side meaning does each have? These are semantic claims, not RelationSignature SlotSpecs, OperationAlgebra positions, planned fillers, or actual participants.
PreconditionsUnder which states, guards, invariants, participant conditions, or environmental conditions can the method be used?
Intended effectsWhich postconditions, intended effects, preserved conditions, and failure semantics are claimed for the method?
BoundsWhich latency, precision, cost, safety, reliability, uncertainty, or other local bounds constrain the method?
System-role kinds and capabilitiesWhich local system-role kinds and capability thresholds matter for enactment?
ParametersWhich values may vary between work occurrences, over which ranges, and when are they bound?
Evaluation conditionsWhich criterion is applied to the concrete Work occurrence, referent, measurement, or result, and which pattern defines that criterion?
Internal compositionWhich admitted methods are parts of one composite method, and what organization constructs that whole?
Change and comparisonWhich claims are preserved or changed? Distinguish equivalence of claim content, a C.2.1 edition relation, B.5.MR refinement or abstraction between models of a Method, and an A.3.1 claim about Method identity or relations.
Edition and publication useWhich episteme edition is relied on, and does its publication use affect currentness or availability?

Calendars, assignees, work authorization, gate passage, and dated execution witnesses are governed by planning, assignment, gate, or work-occurrence patterns. They may cite a method description.

The same episteme can also satisfy A.15.2 as a U.WorkPlan when its claims about that admitted Method include the required substantive intended coordination. Establish both membership predicates on the same independently identified E. A plan that merely names a Method does not thereby supply the way-of-doing claims required here. Planning and actual-performance judgements retain their own conditions.

A.3.2:4.4 - Method-description acceptance and use boundaries

A project may accept, regulate, prefer, deprecate, or forbid a method description for one stated use, organization, or policy scope. Record that separate publication, gate, authority, or policy claim under its own pattern. It does not establish U.MethodDescription membership.

When a method description is used to prepare or enact work, distinguish the planned-use and actual-occurrence branches:

  1. Identify the episteme under C.2.1 and apply the membership test in §4.1.
  2. U.WorkPlan may cite that episteme when preparing dated work.
  3. For a claim about actual Work, use the Work-admission and conditional assignment-attribution rules in §4.1. Cite methodDescriptionRef only when the claim depends on that edition.
  4. The word result is only a cue. Ask which claim is being made: an A.6.1 application returned a value, a referent changed under A.3.4, Work produced something under A.15.PROD, or a measurement, evaluation, delivery, or acceptance occurred. If the use needs a Work-to-result relation and no predicate is defined for it, keep Work and result separate and state missing-predicate[work-to-result]. A log, trace, measurement, or result episteme supports another claim only through its evidence relation.

A.3.2:4.5 - Method, mechanism, and formal-substrate boundary

First say what the sentence asserts. When the distinction remains unclear, use E.10.ARCH:3.1 to separate method, mechanism, formal-object, plan, Work and result claims; otherwise use the subject pattern directly. The source word alone does not decide the kind.

For A.3.2 ask only: is this episteme about one admitted Method, and does at least one claim say how that Method is done? If the same source also asserts a mechanism, formal declaration, work plan, dated Work, evidence use, gate, result, publication, or temporal claim, state that claim separately.

Use these claim checks instead of forcing distinct claims into one generic relation:

  • A method-description membership judgment identifies one admitted U.Method as the episteme’s EntityOfConcern and finds at least one substantive claim about that method as a way of doing.

  • A method claim states the reusable way of doing, its participant meanings, applicability, conditions, intended result or preserved condition, and bounds.

  • A formal-substrate claim concerns the selected formal object, structure, invariant, or mathematical declaration used for reasoning.

  • A mechanism-declaration claim concerns the law-governed operation family, direct subject and range fields, operation algebra, law set, admissibility predicates, and applicability. Transport, audit, realization, evaluation, and evidence-use relations remain separately governed neighboring claims.

  • A work claim concerns one dated occurrence independently admitted under A.15.1: each performing System with its A.13 core, including an obtaining assignment of a separately declared species, the enacted Method, temporal extent, and containing System.

    Add F.6 attribution through that same assignment only when precise assignment-bound attribution is asserted. Add participant, resource, or work-to-referent claims only through relations that obtain; otherwise return the corresponding missing-governor result.

Connect these claims only through an admitted relation whose predicate and participants are present. If no pattern or declaration defines the needed relation, keep the objects separate rather than inferring dual typing. Example: a U.MethodDescription episteme for a scheduling Method can meet the membership rule while a MILP file represents some of its claims. Another episteme may describe the mathematical formulation; a selector mechanism may declare operations over candidate Methods; a dated solver run is Work; and an issued production-schedule episteme is a separate result. Use that result as evidence only through a current A.10 path and its bounded disposition. Without that path, keep the result available but do not rely on it as evidence for another claim.

A.3.2:4.6 - Constructor and process-theory note

Constructor-theory and process-theory sources distinguish possible or impossible transformations from their realizations. This helps explain Method claims about change without privileging software code. It does not require every MethodDescription to concern transformation; the same membership rule applies to a Method for observation, comparison or preservation. For claims about change:

  • an episteme about an information-transformation method may be represented through a program, proof script, or solver model;
  • an episteme about a material, energetic, organizational, or mixed-transformation method may be represented through a procedure, lab protocol, or control recipe;
  • an assertion or description about dated Work may cite a method description; §4.1 gives the Work-admission and conditional assignment-attribution route;
  • a mechanism may declare law-governed operation structure for transformations, but that mechanism claim is separate from the method-description claim.

Across these cases, identifying the claim and described Method allows different representation forms to be treated under the same membership rule.

A.3.2:4.7 - Declarative representation boundary

Some method descriptions use declarative representations: constraint sets, graph patterns, state predicates, SQL-like queries, policy rules, e-graphs, monoidal diagrams, or process constraints. Do not translate such representations into an imperative route unless the method claim states an ordered action structure.

Even a representation that runs or is internally consistent may have more than one sound interpretation. If a comparison depends on variables and their bindings, surrounding context, or an e-graph kept across compiler stages, say what counts as equal. Agreement under one such rule does not by itself show whether the Method is the same, whether the claims are equivalent, or whether one episteme edition continued into another.

Use C.2.P.DR when a graph path, evidence path, query plan, predicate, checklist, publication face, or neighboring-pattern relation is treated as an action route by its form or layout alone. Recover the direct object or relation and any separate representation use, then check whether the source asserts the proposed order. State an ordered Method or WorkPlan as its own subject assertion with the ordering and conditions its claim defines.

A.3.2:4.8 - Composite methods and independent method structures

When claims concern relations among methods, first determine whether the related methods construct one admitted composite U.Method.

If admitted methods are method parts whose organization constitutes one composite method under A.3.1 and, when order-sensitive composition is current, B.1.5, the composite U.Method remains the EntityOfConcern. A U.MethodDescription can make substantive claims about that composite method’s internal organization without changing its object of concern to an independently selected structure.

Description nodes, workflow boxes, code blocks, proof-script blocks, diagram paths, and table rows are representation constituents. They do not become method parts by position in the description. A constituent can participate in method-holon composition only after the recovered object is itself an admitted U.Method.

If a selected relation structure instead connects several methods as alternatives, substitutes, fallbacks, comparison candidates, or members of a family without constituting one composite method, the selected U.Structure is the EntityOfConcern under A.22 and C.2.1. The resulting episteme can describe that structure, but the present rule does not classify it as U.MethodDescription.

A mathematical or graphical representation can express or analyze either case. Its correspondence to claims is recovered through A.6.3.RT and A.6.3.RT.OE, with C.29 additionally governing a mathematical lens. A work plan, work occurrence, method-family registry, or selector result also keeps its own governed object and subject pattern.

A.3.2:5 - Archetypal Grounding

Across the slices below, recognize the claim-bearing episteme before examining how it is represented or published. Ask in this order:

  1. Which admitted U.Method is its EntityOfConcern?
  2. Which claim says something substantive about that method as a way of doing?
  3. Is anyone proposing a use beyond membership? If so, name the use, its subject pattern, and the claims it needs; if not, stop at membership.
  4. When expression or availability matters, which expression conveys the claims, which reusable form does it follow when that matters, which carrier bears it, and which publication occurrence makes the selected episteme available? Use C.29 separately for a mathematical lens.

A.3.2:5.1 - Industrial procedure

A procedure episteme about EtchAl2O3@FabA qualifies when its claims state how the etching Method is done: gas-feed participant meanings, temperature bounds, chamber preconditions, intended etch profile, failure conditions, operator system-role kind, calibration capability threshold, or admitted parameter ranges.

An expression recoverable from a PDF carrier may convey one edition of those claims, and a PLC ladder representation may correspond to some of them. A U.WorkPlan states the planned maintenance-window preparation; tool run W-143 is Work. A metrology result supports another claim only through the evidence relation for that claim.

Named use — preparing WP-Etch-MW-47. The maintenance planner needs four claims before drafting this A.15.2 U.WorkPlan: the chamber is empty, inert, and leak-check complete before gas feed; the method’s temperature range is 58–62 °C; calibration is no more than 24 hours old; and pressure above the stated bound stops the run. EtchAl2O3-Description-e7 passes A.3.2 membership because it concerns EtchAl2O3@FabA and says how that Method is done. It also states all four needed claims.

To verify that this is the current edition, the planner checks its ClaimGraph against publication occurrence Pub-Etch-e7, particular expression EtchAl2O3-SOP-e7, and carrier FabA-MethodRepository-2026, plus the source trace from EtchDescriptionReleaseWork-e7, performed under EtchDescriptionMaintainerAssignment-4 with method trace ClaimGraphReleaseCheck-v2. A.10 path EP-Etch-e7-Plan47 links those sources to claim C-Etch-e7-has-Plan47-claims.

Its bounded use is citing e7 while drafting WP-Etch-MW-47; unsupported uses are gate passage, authorization, safe execution, and a claim that Work occurred. Its window reopens when e7, RecipeWindow-Al2O3-3, the calibration rule, or a source named in the path changes. RelianceDisposition=pass therefore supports citing e7 only for this drafting use.

EtchAl2O3-Description-brief-e7 passes membership because it concerns the same Method and states the gas-feed and temperature procedure. It omits the 24-hour calibration condition and pressure stop. A.10 path EP-Etch-brief-e7-Plan47 points to that brief edition and cannot evidence the two missing claims, so RelianceDisposition=blocked-current-use applies to drafting WP-Etch-MW-47. Reopen after selecting an edition that states both claims; until then the planner stops or selects another edition. Membership is unchanged.

If the result must persist, C.2.1 is the pattern for its result episteme and ClaimGraph, A.10 is the pattern for the evidence path and disposition, and A.15.2 is the pattern for the plan.

A.3.2:5.2 - Optimization model

A U.MethodDescription episteme for the scheduling Method qualifies when its EntityOfConcern is JSScheduleV4@Plant2026 and its claims state how a production schedule is produced or evaluated. A MILP representation and a recovered solver-configuration representation can stand in declared correspondence to those claims.

A separate formal-substrate episteme can make claims about variables, constraints, objective, admissible solution set, or invariants. An expression of that episteme can be borne by the same carrier and follow its selected reusable form. A timestamped solver run is work. A selector mechanism, if declared, is governed by A.6.1 and E.20. Solver search order does not by itself state the project work sequence.

A.3.2:5.3 - Proof script

An episteme about a reusable derivation or checking method qualifies when it identifies that U.Method and makes a substantive claim about how the derivation or check is done. A proof-assistant script may represent those claims.

A concrete proof-checking session is work. Claims about a formal substrate, a theorem, or evidence for the theorem remain separately governed even when expressions of those epistemes are borne by the same carrier. A publication occurrence makes a selected edition available to an audience for a bounded use.

A.3.2:5.4 - Clinical guideline

A guideline episteme qualifies when its EntityOfConcern is AcuteAppendicitisTriage@HospitalContext and its claims state the triage Method through patient-information and resource participant meanings, exclusions, decision criteria, relevant local system-role kinds and capabilities, intended effects, or failure response. A particular expression conveys one selected edition, optionally following reusable form rules, and a publication occurrence can make that edition available; approval status remains a separate claim.

Patient-specific dated enactment is a Work individual admitted under U.Work. If a causal claim relies on a triage disposition, diagnostic finding, or measurement result, name that premise and apply C.28. Merely using the guideline during Work establishes neither a causal effect nor a causal-use result.

A.3.2:5.5 - Workflow diagram

An episteme whose claims state one reusable method may qualify as U.MethodDescription; a BPMN or object-centric process model may represent those claims. A diagram can also represent a work plan, event-log model, or independently selected structure, so its notation does not settle the EntityOfConcern.

If readers treat the diagram as a route that tokens or workers must follow, compare that reading with the source claim. Keep an ordered sequence only when the method claim states one. When order comes only from layout, use C.2.P.DR and stop at the represented graph, constraints, objects, or events.

A.3.2:6 - Bias-Annotation

The following biases obscure method-description membership:

  • carrier-as-description bias: a PDF file, repository, screen, or presentation carrier is treated as the method description. Identify the episteme whose ClaimGraph is being read, then distinguish the representation or publication relations on which the use depends under §4.2;
  • description-as-method bias: the representation is treated as the way of doing itself;
  • description-as-work bias: executable or operational-looking representation is treated as dated work;
  • approval-as-proof bias: accepted, approved, or regulated descriptions are treated as evidence, gate passage, or safe execution;
  • notation-prestige bias: code, formal notation, or solver files are treated as more authoritative than procedures, diagrams, or guidelines. Compare the method claims; representation form supplies no priority;
  • imperative-metaphor bias: graph, query, predicate, or process-model representation is treated as an ordered work-control claim.

First identify the claim-bearing episteme, the claim it makes, and the Method it concerns. When the use needs them, keep its representation, publication occurrence, publication form, and presentation carrier separate under §4.2. State each additional plan, Work, evidence, gate, authority, mechanism, formal, or mathematical claim under its predicate or constraint with an optional subject-pattern locator.

A.3.2:7 - Conformance Checklist

CC-A3.2-1 (Episteme membership). A.3.2 judges one already identified U.Episteme candidate. That same individual is a U.MethodDescription only when its C.2.1 EntityOfConcern is one admitted U.Method and at least one claim says how that Method is done. Representation form, publication form, carrier, approval, and use adequacy do not decide membership; no binary description relation is minted.

CC-A3.2-2 (Positive description threshold). The episteme must make at least one substantive claim about the method as a way of doing, such as its transformation or enactment concern, generic participant meanings, applicability, precondition, intended effect or preserved condition, bound, or internal composition. A name, citation, author, catalogue entry, or approval status alone is mention, not method-description membership.

CC-A3.2-3 (No automatic trigger repair). Wording such as algorithm, program, proof, solver, workflow, process, procedure, recipe, or model is only a cue. Classify the episteme as U.MethodDescription only after its claim and admitted Method pass CC-A3.2-1 and CC-A3.2-2.

CC-A3.2-4 (Description not work). Executable-looking material is not a Work occurrence. For a program run, proof-checking session, solver run, lab run, or clinical application, first recover every performing System’s A.13 core, including its obtaining assignment of a separately declared species. Admit Work only after A.15.1 independently identifies the world-side occurrence, enacted Method, temporal extent, and containing System.

Apply F.6 through that same assignment afterward only when precise assignment-bound attribution is claimed; a missing or failed F.6 attribution leaves independently admitted Work intact. Any participant, resource-use, or work-to-referent claim needs its own admitted relation; if none exists, return the corresponding missing-governor result.

CC-A3.2-5 (Membership and additional claims). Method-description membership does not establish WorkPlan membership, a gate decision, permission, approval, external-rule authorization, or an evidence relation. Test each additional claim under its subject pattern. The same episteme may also be a U.WorkPlan when it meets A.15.2.

CC-A3.2-6 (Description not mechanism or declaration). A method description is neither a RelationSignature nor A.6.1 OperationAlgebra content and does not close a mechanism claim. If reusable direct-relation participant declaration is current, use A.6.0 and A.6.5. If operation algebra, law set, admissibility predicates, or applicability is current, use A.6.1; transport, audit, realization, evaluation, and evidence-use relations remain with their direct patterns.

CC-A3.2-7 (Description not formal substrate). A method description does not close a formal-substrate or mathematical-lens claim. If variables, equations, invariants, structure, substrate, or mathematical payoff are current, use A.6.0, C.29, or the direct mathematical pattern.

CC-A3.2-8 (Generic conditions and actual participants). A method description may state local system-role kinds and capability thresholds that bound admissible enactment. A claim that a particular System belongs to one of those kinds is a separate System-classification judgment. Named people or Systems, dates, schedules, launch values, assignment species and obtaining assignment occurrences, F.6 attributions, and Work witnesses belong to their planning, classification, assignment, or Work patterns.

CC-A3.2-9 (Parameters and use time). A method description may state parameter meanings and ranges. A U.WorkPlan names planned values against the declaration that gives them meaning. An actual participant or operation value requires an obtaining subject relation or A.6.1 application binding; otherwise keep it planned and return missing-governor[actual-use].

CC-A3.2-10 (Same subject versus equivalent descriptions). Two descriptions concern the same U.Method only when their EntityOfConcern references resolve to the same A.3.1 method identity. A scheme difference may require an F.9 Bridge to interpret a comparison, but the Bridge does not establish Method identity. Shared subject also does not make the epistemes equivalent: state which claims are preserved, absent, incompatible, or inaccurate for the proposed use. Do not use executable agreement, renaming of bound variables, graph equivalence, or persistence across stages by itself to decide whether the Method is the same or different or the claims are equivalent.

CC-A3.2-11 (Edition, model comparison and Method identity). Use C.2.1 for a claimed edition relation and state which description claims the comparison preserves or changes. When the descriptions are used as models, apply B.5.MR to a refinement or abstraction claim between them. Apply A.3.1 separately to Method identity and any proposed relation between Methods. A one-use comparison may stop as claim content under A.6.RCD; it creates no Method relation occurrence.

CC-A3.2-12 (Nondeterminism). When a description permits search, optimization, sampling, nondeterministic choice, or learned behavior, state the admissible result range and the criterion for evaluating actual Work or results. Name the pattern or declaration that defines that criterion.

CC-A3.2-13 (Cross-context and semantic-locality boundary). F.9 answers only whether a Bridge obtains between two SchemeSenseCell values. For proposed reuse, state a separate C.2.1 claim with the use, direction, correspondence rule, loss tolerance, and affirmative or negative polarity. Positive polarity alone is not reliance. Ordinary reliance with no assurance claim requires RelianceDisposition=pass on its A.10 path.

When a named assurance claim about the same bounded use is current, apply B.3; positive assurance requires its AssuranceResult with disposition=supported-for-use. A direct domain rule may require that claim, but consequence alone does not create it.

A negative or absent use claim, a non-passing A.10 disposition, or—when that assurance claim is current—a B.3 result that does not support the attempted use stops or narrows reuse even while the Bridge obtains. Changes of reference scheme, unit, role taxonomy, claim scope, or model use stay under their own patterns.

CC-A3.2-14 (Declarative representation). Use C.2.P.DR when a declarative representation’s form or layout is being treated as sufficient to prescribe work. Recover the direct object or relation and any representation use. Assert the proposed route, dispatch, call, or work-control sequence only when its predicate is defined and current facts satisfy it; otherwise retain the direct object or representation without that unsupported action claim.

CC-A3.2-15 (Causal-use boundary). A method description may describe intervention assignment, target-trial emulation, realized-counterfactual sampling, simulation, or causal-evidence collection. It does not by itself establish causal use. If causal effect, intervention success, counterfactual comparison, causal fairness, or policy effect is claimed, use C.28.

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

Anti-patternRepair
Treating executable text as sufficient Method identity.Identify the reusable way under A.3.1. When method-description membership is claimed, identify the episteme and apply §4.1. Use §4.2 for representation and publication, and A.15.1 for a run that happened.
Treating a Work log as a method description solely because it records a sequence.The log is an episteme about dated Work, not the Work or a method description by being recorded. Identify the occurrence under A.15.1; cite or write a separate method description only when its claims pass the membership rule.
Inferring safe use solely from protocol approval.Separate method description, approval or gate claim, safety evidence, work plan, and work occurrence.
Leaving the optimization-model claim unresolved.Ask whether the episteme says how a scheduling Method works or instead states variables, constraints, and an objective for a formal model. Keep the solver run as Work and any selector mechanism under A.6.1/E.20.
Inferring project-work dispatch from a query-plan layout.A database plan or graph may represent ordering without commanding project Work. Use C.2.P.DR when layout is being read as dispatch; write a WorkPlan or ordered Method only when its own claim states that sequence.
Inferring the workflow sequence solely from a diagram route.Check whether the method claim states the sequence. If the route is only a graph path, event trace, or drawing convention, keep it in the representation; do not turn it into a WorkPlan or performed Work.
Conflating a new file version with refinement of the Method.Separate the C.2.1 edition relation, a comparison of description claims, and any refinement relation between Methods. A file version establishes none of them.
“SOPs are notes, code is the real spec.”Neither notation establishes membership. Compare what each episteme claims about the Method. Ask adequacy only for a concrete proposed use.

A.3.2:9 - Consequences

BenefitCost or caution
Method descriptions become reusable across notations.Users must separate method identity from description form.
Audits can distinguish description, plan, work, evidence, and authority.The first repair is to identify the claim-bearing episteme, its Method, and one substantive method claim; replacing vocabulary is not enough.
Software, lab, industrial, organizational, and proof-centered descriptions can be compared under one FPF kind.Some files contain several current claims and must be split into several subject-pattern statements.
Equivalent descriptions can be declared without forcing identical notation.Equivalence and refinement need local criteria.
Declarative representations can be used without being turned into ordered work-control claims.An order inferred solely from form or layout needs C.2.P.DR; a supported order needs its subject assertion with its ordering and conditions.

A.3.2:10 - Rationale

Projects need reusable claims about ways of doing before any dated work occurs. Treating a file as the method description by appearance hides two decisions that later work needs: which episteme is being relied on, and which admitted method its claims concern. The positive claim threshold makes this distinction usable without demanding a complete procedure card.

The pattern is representation-agnostic because a method can be described through procedural text, code, diagrams, mathematical notation, protocols, or combinations of them. The episteme can be revised and evaluated while its representations, publication occurrences, publication forms, and presentation carriers change independently. This separation lets a project compare descriptions and judge fitness for a receiving use without turning notation, approval, publication, or enactment into kind membership.

A.3.2:11 - SoTA-Echoing

Source lineSource refsContribution and limitEffect in this pattern
constructor-theory and process-theory workGogioso et al., “Constructor Theory as Process Theory”, EPTCS 397, 2023, arXiv:2401.05364; Deutsch and Marletto, “Constructor theory of time”, arXiv:2505.08692v3, revised 2026-06-05.Descriptions stay close to transformation claims without becoming the transformation or Work occurrence.The pattern separates MethodDescription, Method, mechanism, WorkPlan, Work, and evidence across physical, informational, organizational, and mathematical examples.
scoped-effects and handlers workBosman et al., “A Calculus for Scoped Effects & Handlers”, 2024; Matache et al., “Scoped Effects as Parameterized Algebraic Theories”, 2024; Kura, “On Complete Categorical Semantics for Effect Handlers”, 2026.Separate syntax, handling, scope, resources, equations and semantic model; executable coherence does not establish uniquely determined semantics.An executable-looking episteme may describe a Method, but form or one working interpretation does not by itself settle its Method, mechanism law, semantic equivalence, or success.
binding-aware equality representationTiurin, Ghica, and Hu, “E-Graphs With Bindings”, 2025; Zucker, “Lifting E-Graphs: A Function Isn’t a Constant”, 2026.Variables, binders, and contexts need explicit representation semantics; ordinary graph equality is not enough.When equivalence depends on binding or context, state that comparison basis. Alpha-equivalent or graph-equivalent representations do not automatically identify one Method or equivalent claim content.
persistent equality representationMerckx et al., “E-Graphs as a Persistent Compiler Abstraction”, 2026.An equality representation may persist across several intermediate-representation levels while its expression changes.Persistence of one representation structure across compiler stages is a representation fact; it does not establish episteme-edition continuity, Method identity, MethodDescription membership, or performed Work.
Historical declarative-versus-imperative programming contrastsCodd 1970; Kowalski 1979; Selinger et al. 1979; van der Aalst, Pesic, and Schonenberg 2009; Van Roy and Haridi 2004.Historical lineage and comparison cases; these anchors do not establish the current state of their fields.Older slogans remain useful recognition cues, but the reader asks what the artifact asserts and which FPF object that claim concerns.

A.3.2:12 - Relations

A.3.2.DE develops the description for a declared receiving use, including explanation of the operation and its changed conditions. C.37.MP relates representations across different uses, and C.37.CF compares content and form changes. None changes MethodDescription membership merely by improving usefulness.

  • Builds on: C.2.1 for the identity, grounding, and edition relations of the same claim-bearing episteme; A.3.1 for the U.Method; and E.24.UK for admission of the dependent U-kind.
  • Coordinates with: A.3.1 and B.1.5 for Method parts, Method identity, and composite-Method organization; A.22 for an independently selected structure among several Methods; A.1.1 only when an independently selected BoundedModelUseStructure changes the proposed use; F.9 only for cross-context SchemeSenseCell correspondence; C.2.1 for the separate claim that one obtaining Bridge suits one bounded use; A.10 for ordinary evidence reliance on that claim and B.3 only when a named assurance claim is current; A.6.3.RT and A.6.3.RT.OE for representation correspondence, with C.29 when a mathematical lens is used or remains to be chosen; E.24.PUB for publication occurrence and form; A.15.2 for U.WorkPlan; A.15.1 for U.Work; A.2 for local system-role kinds and System-classification judgments; A.2.1 for assignment species and obtaining assignment occurrences; F.6 for Work–assignment attribution; A.2.2 for capability thresholds; and C.28 for causal-use claims.
  • Separates from: A.6.0 formal-substrate declarations; C.29 mathematical-lens use; A.6.1 U.Mechanism; E.20 mechanism-meaning introduction and revision.
  • Uses for precision restoration: F.19 for the connected reading of wording that leaves the claim, object, or relation unclear; E.10, E.10.ARCH, F.18, or C.2.P.DR for a remaining word, kind, durable naming, or declarative-representation question.

A.3.2:End

A.3.2.DE - Describe a Method for Its Intended Use

Type: Method pattern Status: Stable

A.3.2.DE:0 - Use This When

Use this pattern when people need usable claims about an identified Method or a candidate account of a proposed way of working. The receiving use may concern planning, enactment, comparison, review, revision, publication or teaching; retain the claims’ status. Start from one named use: who needs to do or decide what, which Method claims that use consumes, and what can remain outside the edition.

The first useful result is a short use-coverage account. It names the Method or candidate account, the receiving use, the claims needed now, the claims deliberately omitted, and the stop. That account prevents a documentation project from expanding before its practical question is clear.

Do not use this pattern merely to publish, diagram, approve, schedule, or record Work. A U.MethodDescription is the claim-bearing episteme whose EntityOfConcern is one Method already admitted under A.3.1; its representations, carriers, and dated enactments remain separate objects. Planning and approval have their own claim conditions; the same episteme may also meet A.15.2 as a U.WorkPlan. If the proposed whole is still a candidate account, improve that account without classifying it as a U.MethodDescription for the whole.

A.3.2.DE:0.1 - Working Distinctions

ItemWorking meaning hereBoundary
admitted MethodOne reusable way of doing whose identity has been established under A.3.1.A shared title, coherent document, WorkPlan, or successful occurrence does not establish it.
U.MethodDescriptionOne C.2.1 episteme with at least one substantive claim about that Method as a way of doing.Membership is not a completeness, approval, currentness, publication, or effectiveness result.
candidate accountClaims about a possible Method whose identity or obtaining relations remain unresolved.It can be improved and used prospectively without being renamed a MethodDescription.
named useA particular planning, enactment, comparison, audit, revision, publication, or teaching need with a receiver and stop.A generic wish to “document the method” is not yet a use boundary.
use-coverage accountA C.2.1 account that states which Method claims an edition exposes for each named use and which it omits.It does not prove that the claims are true enough for the use or that anyone used them.
representation and publicationA representation under A.6.3.RT/A.6.3.RT.OE, an E.24.PUB form or publication occurrence, and a carrier through which claims may be expressed or made available; C.29 applies when a mathematical lens is used or remains to be chosen.Form and availability do not decide MethodDescription membership.

A.3.2.DE:1 - Problem Frame

A working group often has too much material rather than too little: procedures, diagrams, code, examples, approval notes, logs, training slides, and tacit explanations. Different users need different portions. A planner needs applicability, preconditions, parameters, bounds, and stops; a performer needs the actionable claims for the current situation; a reviewer may need provenance, changed claims, and declared evidence limits.

Without a use boundary, authors either copy everything into one manual or reduce the Method to one convenient representation. Both moves hide whether the episteme describes an admitted Method and whether its claims are sufficient for the receiving use.

A.3.2.DE:2 - Problem

A document can look complete while saying little about the way of doing. Conversely, a small claim set can be a valid MethodDescription yet be unsafe for a consequential enactment use. Teams also copy calendars, assignees, tool states, observed results, and approval decisions into the description as if adjacency turned them into Method semantics.

The result is difficult to reuse and difficult to challenge. Readers cannot tell which claims belong to the Method, which belong to one Work occurrence, which are evidence or policy, and which omissions require a return.

A.3.2.DE:3 - Forces

ForceTension
Use fitnessEach receiving use needs enough claims, while one universal description becomes expensive and opaque.
Stable subjectSeveral editions and forms may describe the same Method, while a candidate or changed Method must not inherit that identity by typography.
Practical brevityThe edition should contain what its receiving use needs, while hidden preconditions or stops can make it misleading.
Representation pluralityText, code, diagrams, tables, and formal models may all help, while none determines MethodDescription membership.
Evidence limitsClaims may cite evidence and source limits, while the description must not become the evidence or assurance result.
RevisionA use may require a new edition, while editing a description does not by itself change the Method.

A.3.2.DE:4 - Solution

A.3.2 distinguishes description membership from adequacy for use. C.39:4.3–4.5 supplies construction of a missing action or join. Here the author develops the explanation for the declared reader: recover the operations, reasons, conditions and changed case that the reader must be able to follow, retaining an unresolved candidate as such.

Author claims for named uses while preserving the described Method’s identity or the account’s candidate status. Return gaps instead of filling them with neighboring objects.

A.3.2.DE:4.1 - Pattern-Use Unfolding

  1. Name the receiving use. State the reader or consuming system, the action or decision, the situation and qualification window, and the stop. Define completeness by the claims the receiving use needs, including their connections.
  2. Establish the subject branch. Name the admitted U.Method and the effective reference scheme for the description, including the rules that resolve its Method designation. If admission is absent, keep the subject as a candidate account and author only improved candidate content.
  3. Select the needed Method claims. For the named use, consider the transformation or enactment concern, generic participant meanings, applicability, preconditions, intended effects or preserved conditions, bounds, parameters, variation, internal composition, evaluation conditions, and stops. Include only positions that change the use. For enactment or learning, recover the operations the performer must carry out and where their inputs come from.
  4. Separate neighboring claims. Keep planned assignments and dates in a U.WorkPlan; actual performers, temporal extent, participation, and results with dated U.Work; operation declarations with A.6.1; evidence reliance with A.10; capability with A.2.2; approval, permission, and authority with the patterns that define those claims. Cite them when the use depends on them without absorbing them into Method semantics.
  5. Write the explanation or instruction. For enactment or learning, connect each needed action to its inputs, the operation performed, the result and the condition for continuing or stopping. Explain why a connection or ordering matters when the reader needs that reason to apply or adapt it. For a Method that depends on professional judgment, explain which observations bear on the decision, how they change the proposed action, and which unresolved conflict needs another contribution or a stop. Naming a mindset without showing that effect leaves the explanation incomplete. Unfold a constituent operation until the intended performer can carry it out, or identify the missing know-how or contribution; do not invent an operation to fill a heading. Retain alternatives and dependencies without imposing one order on independent actions. In the admitted-Method branch, identify the episteme by its claim content, Method as EntityOfConcern, and effective scheme. In the candidate branch, retain the account’s proposed content and unresolved Method-identification conditions. State which claims were added, retained, narrowed, or removed when another edition is being revised.
  6. Record use coverage and omissions. For each named use, list the claims exposed, claims deliberately omitted, unresolved claims, and the return condition. An omission is acceptable when the receiver does not rely on it; otherwise it is a gap.
  7. Choose expression and publication separately. Select text, code, diagrams, a mathematical lens, publication form, and carrier only after the claims are stable enough for the use. For one representation-use action, use C.37 or its direct governing pattern. When different named Method-related actions require complementary governed representations of the current MethodDescription or candidate account, C.37.MP returns a complete Method representation profile: one complete C.37 claim group per action, together with cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections. Use the FPF pattern governing any other represented entity.
  8. Try the receiving use from the description. Recover the claims, conditions and omissions needed by the receiving use. For enactment or learning, work through a small case: recover the first action and its inputs, follow its result to the next needed action or stop, and expose any instruction supplied only from the author’s memory. Return a description or candidate-account correction, or identify the missing input, know-how or other result needed by the use. This checks the description at that use; it does not establish the Method’s effectiveness or a learner’s acquired capability.

A.3.2.DE:4.2 - Record the Result

Result positionRequired content
subjectAdmitted Method and identity basis, or candidate account and unresolved admission condition.
named useReceiver, action or decision, situation, qualification window, and stop.
claim setMethod-side claims included in this edition and their effective scheme; the connected operations, inputs, results and conditions when the use requires an actionable instruction.
use coverageNeeded claims, exposed claims, deliberate omissions, gaps, and return condition for each use.
neighboring objectsAny WorkPlan, Work, representation, operation declaration, evidence path, capability, permission, authority, publication, or carrier relied on, each kept under its own kind.
edition dispositionMethodDescription edition, improved candidate-account content, or lower stop with the decisive missing condition.

These positions can be stated in prose or in an existing description account; they do not require a separate row or form.

A.3.2.DE:4.3 - What Changes in Practice

Authors stop treating “the method document” as one undifferentiated object. They can issue a small edition for one use, explain why it is enough, and name the gap when it is not. Readers can distinguish a claim about a reusable way of doing from a plan, an observed occurrence, a tool presentation, or an approval fact.

A.3.2.DE:5 - Archetypal Grounding

A.3.2.DE:5.1 - Stop at the Candidate Whole

C-EC-Release-v2 is a prospective account of a possible release-coordination whole. It proposes waiting for signed supplier evidence before software integration, or integrating from a versioned provisional edition and reconciling it with signed evidence before safety closure. It also specifies recovery after failed closure, authority boundaries, confidentiality, reversibility and stops. The Method identity of this proposed whole remains unresolved; B.1.5.CM:5 gives the full case.

Improve the claims required for selection or trial planning and retain the unresolved Method-identification condition. The result remains a candidate account.

A.3.2.DE:5.2 - A Bounded Description of an Admitted Constituent Method

For the admitted constituent M-HW-Verify, suppose the named use is preparing safety-verification Work for one EC-417 release. A description edition can state the applicable safety-relevant change family, the distinction between provisional and signed evidence, the comparison and affected-verification actions, the signed-before-closure bound, confidentiality conditions, and the mismatch or stale-edition stop. The use-coverage account says that it exposes those Method claims but omits dates, assignees, actual evidence versions, actual verification results, and release authority decisions.

The planner may cite that edition when constructing a WorkPlan. Supply separate claims about the Work schedule, the assignment of SafetyReviewer-17, the required capability, closure authorization, and whether verification occurred whenever the plan or later Work relies on them.

A.3.2.DE:5.3 - Turn a reconciliation reminder into an instruction

In this constructed case, a stock-reconciliation Method has already been identified. Its working rule is available, but the draft for a new storekeeper says only: “Reconcile stock and investigate discrepancies.” The reader can add and subtract counts; they still need to know which counts to compare and what the difference means.

The author recovers the rule’s inputs and dependencies. For one item, unit and interval, an opening stock count plus receipts minus issues gives the expected closing count, provided the movement account includes every change once. A physical count at the closing boundary supplies a different input. The author writes this instruction:

  1. Select the item, counting unit and interval. Obtain the opening count, receipts and issues for that same scope, and the physical count at its closing boundary. Resolve a missing movement class, unit conversion or mismatched boundary before treating the balance as complete.
  2. Calculate expected closing stock as opening stock plus receipts minus issues. The additions and subtractions represent movements into and out of the selected stock.
  3. Subtract expected stock from the physical count. Return the difference with the counts and scope used. A negative difference means fewer units were counted than the movement account predicts; it does not identify the cause.
  4. If the counts disagree, return the discrepancy for checking the movements and counts. Do not change a source count merely to force agreement.

With opening stock 48, receipts 12, issues 17 and a closing physical count of 41, the expected count is 43 and the discrepancy is -2. The description now supplies an operation, its operands, their origins, the reason for their combination and a useful return. Its authoring result is the instruction, not evidence that a storekeeper performed it.

The receiving-use check asks the reader to recover that calculation and return from the description. If the opening figure is in boxes while movements are in individual units and the conversion is unknown, a numerical balance remains unavailable. A comparison-only description could legitimately omit this enactment detail; this edition promises the storekeeper a way to perform the reconciliation.

A.3.2.DE:5.4 - Explain the Basis of a Professional Judgment

A stakeholder map can keep the same boxes and labels while the way of constructing and using it changes. In this constructed case, an admitted contact-planning Method includes people who hold the approval or supply roles needed to arrange a rollout. A proposed child account instead asks whether a new shift-handover routine covers the work of the people who produce and use the handover information. Its author cannot explain that change merely by adding “be inclusive” to the old instruction.

The receiving use is a facilitator’s preparation of a handover review. Available inputs are the proposed routine, the two-shift role roster, the information each role’s holders supply or need, and the known limits of those accounts. The author writes the proposed instruction:

  1. Start from the handover information that must reach the next shift and identify the roles whose holders produce or use it in their work. Include a role because of that working dependency, even when its holder has little influence over rollout approval. Use supplied facts; mark an uncertain dependency for clarification.
  2. For each included role, obtain an account of the information its holders need, the action that information enables and a relevant missing-information case. Distinguish what a participant or work record supplies from the facilitator’s assumption. A manager’s approval does not supply another role’s working account by itself.
  3. Relate those needs to the proposed routine. Show which handover action supplies each needed result and which dependency remains uncovered or unknown. Influence can help arrange contact; it does not remove a required receiving role from this check.
  4. Return the map with the supported coverage and the missing account or handover contribution. Stop a claim of complete coverage when a material dependency remains unresolved. The result can guide a correction or a bounded trial; it does not itself authorize rollout or show that the routine works.

For a small worked case, suppose a day lead approves the trial, an IT maintainer supplies the display, and a night operator uses unresolved-item flags to resume work. The approval-contact map may correctly contain the first two roles. The proposed method also includes the night operator because the operator consumes a result needed for the handover. If the routine supplies a flag but no next action, the map exposes that missing contribution. If a relief operator’s information need is unknown, add that unresolved dependency rather than treating a full roster of names as complete coverage.

The explanation now makes the changed judgment recoverable: inclusion follows a working dependency, and completion requires an account of its contribution. The canvas may remain unchanged, but the operation, required evidence and stop differ. This is proposed reusable content, so retain candidate status and use A.3.1.MV:5.2 for its derivation and evidence boundaries. The worked case checks whether the explanation supplies the intended distinctions; it is not a field validation of the proposed method.

A.3.2.DE:6 - Bias-Annotation

BiasLikely driftRepair
document identity biasA titled document becomes the Method or its complete description.Establish Method admission and identify the claim-bearing episteme separately.
completeness biasMore sections are assumed to make the edition adequate for every use.Name uses and expose only the claim positions they consume.
execution biasCode, a checklist, or executable syntax becomes evidence that Work happened.Keep representation, WorkPlan, Work, and result claims separate.
policy absorptionApproval, permission, or authority is written as Method semantics.Cite the separate policy or relation only where the receiving use needs it.
candidate launderingA useful prospective account is called a MethodDescription.Improve the account but do not call it a U.MethodDescription until A.3.1 admits the Method.

A.3.2.DE:7 - Conformance Checklist

  • Each U.MethodDescription result names one A.3.1-admitted Method as its EntityOfConcern.
  • A candidate whole remains a candidate account when Method admission is absent.
  • Every named use has a receiver, action or decision, situation, qualification window, and stop.
  • Included claims say something substantive about the Method as a way of doing. An enactment or learning description lets the prepared reader recover the needed operations and their input/result connections, or exposes the missing contribution.
  • Use coverage distinguishes exposed claims, deliberate omissions, unresolved gaps, and return conditions.
  • WorkPlan, dated Work, actual participants and results, operation declarations, evidence, capability, permission, authority, representation, publication, and carrier claims remain separate.
  • Representation choice does not decide MethodDescription membership.
  • The result says only whether this edition covers the named claim need; it does not infer Method fit, effectiveness, assurance, or actual use.

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

Anti-patternRepair
“Write the complete method once.”Split the request into named uses and record coverage and omissions for each.
“The workflow diagram is the MethodDescription.”Identify the claim-bearing episteme first; treat the diagram as one representation of selected claims.
“Add the project schedule so the description is actionable.”Keep the reusable Method claims in the description and put dates and intended assignments in the WorkPlan.
“The procedure passed review, so the claims are adequate everywhere.”Record the review or policy claim separately and evaluate each receiving use under its own conditions.
“The candidate account is detailed enough to count.”Detail does not replace Method admission; return improved candidate content.

A.3.2.DE:9 - Consequences

Method descriptions become more reusable and easier to compare because their subject and receiving uses are explicit. Candidate accounts remain useful without losing their truth status, and missing claims return to the right owner.

The cost is plurality: one Method may have several editions, use-coverage accounts, and representations. Projects must also maintain links to neighboring plans, evidence, policy, and publication results instead of copying them into one manual.

A.3.2.DE:10 - Rationale

Description adequacy is use-relative, while MethodDescription membership is not. Separating those questions lets a small episteme describe an admitted Method, with adequacy assessed for each receiving use. It also lets a rich candidate account remain prospectively useful without turning description quality into Method identity.

The claim-first order prevents representation and publication choices from selecting ontology.

A.3.2.DE:11 - SoTA-Echoing

SourceContributionBoundary and practitioner implication
ISO/IEC/IEEE 24774:2021, process-description elementsDescribe purpose, outcomes, activities, tasks, information items, roles, and views only where the receiving description use needs them.Description-side conformance does not establish process performance or FPF kinds. Practitioners still recover the admitted Method and each neighboring claim separately.
Daalhuizen and Cash, Method content theoryFocus on content that helps a user understand and use a Method.A.3.2.DE applies this focus through named-use coverage and explicit omissions.
Gericke, Eckert, and Stacey, Elements of a design methodIntended use, procedure, representation, tools and adaptation conditions supply authoring questions.Conceptual elements do not prove Method identity, obtaining relations, Work, or effectiveness. The EC-417 slices preserve those stops.
Stacey et al., Methods as a form of engineering knowledge, §§2.4 and 4.4Use the connection between procedure, required knowledge and the generation of inputs and results: make the reasoning steps recoverable where the receiving use needs them.This strengthens instruction construction and the small receiving-use check. Explicit content alone does not supply tacit skill, establish learning or settle FPF’s Method/description distinction.

A.3.2.DE:12 - Relations

  • A.3.1 supplies Method admission; A.3.2 defines U.MethodDescription membership and its boundary from plans, Work, representations, and publication.
  • B.1.5.CM can supply an admitted whole or a prospective candidate account. A.3.2.DE preserves the branch it receives.
  • RMP.10 can supply claim content and evidence limits for a candidate account; it does not admit the Method or create the description.
  • C.37.MP consumes A.3.2.DE’s current MethodDescription or candidate-account claims only when several unlike named Method-related actions require a Method-specific profile. It returns one complete C.37 claim group per action and a separate result showing how the selections relate: source correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions that require reconsidering several selections. For one action, use C.37 or the pattern that governs it; for another represented entity, use that entity’s governing FPF pattern.
  • A.15.2, A.15.1, A.10, A.2.2, and E.24.PUB define or constrain neighboring plan, Work, evidence, capability and publication claims. A.6.3.RT and A.6.3.RT.OE govern representation correspondence; C.29 governs a mathematical lens.

A.3.2.DE:End

A.3.3 - U.Dynamics: State-Space and Transition-Law Episteme

Type: Definitional pattern Status: Stable Normativity: Normative

A.3.3:1 - Problem frame

Use this pattern when you need a reusable account of how a subject’s state can change: which differences the state must retain, the law relating earlier and later state, and the conditions in which that law applies.

First useful move. Name the changing subject and what you want to find about its change. If the state and law are already available, state their meanings in one ordinary sentence; otherwise construct them through :4.4.1. For example: “In this two-substance mixture, the remaining masses in kilograms change from (a,b) to (a/2,b/4) after each treatment cycle; the instrument reports a+b.” The first question is whether the observed total contains enough information to predict the next total. Section 5.6 works out the answer.

If the ordinary statement is sufficient for the current comparison, stop. Add the observation, calibration or assurance account when the receiving use needs it. Before making a prediction, conformance or gate-use claim, name the applicability window and any observation relation that use requires; stop that use if a required condition is unavailable.

The practical gain is a model that supports the needed prediction or comparison, or identifies the missing distinction or rule. A model fitted to the wrong state can lose a difference that changes the answer.

This pattern identifies the episteme that states the model’s state space and transition law. Section 4.1 gives its membership rule. For a known model and a settled calculation, use the domain calculation directly. When the question instead concerns a procedure, an actual event or another receiving use, use the conditional contributions in :4.3.

A.3.3:2 - Problem

A time series describes observations but leaves the next state to be explained. A control instruction selects an action but may leave its physical effect unspecified. Even a declared law can give an inadequate prediction when its chosen state hides a consequential difference, as the two-substance case shows.

A usable account must connect the changing subject, the state distinctions and the transition law, adding the observation relation when the question uses observations. Its applicability and support must be sufficient for the particular prediction or decision, which may demand more than the initial model comparison.

A.3.3:3 - Forces

ForceTension
Universality and domain richnessOne kernel pattern must cover ODEs, PDEs, Markov kernels, queues, discrete events, Bayesian updates, enterprise characteristic evolution, and architecture-quality change without flattening the domain-specific model.
Model and worldU.Dynamics is an episteme, while evidence comes from dated work, telemetry, observation, and source relations.
Continuous, discrete, stochastic, and hybrid formsTime references, update rules, likelihood models, and disturbances differ; the state-space and transition-law declaration must keep them explicit.
Prediction and interventionThe same law can support exploration, while a control action may require additional validation and assurance.
Mathematical power and transfer riskMathematical form can make prediction precise, but transfer across domains, scales, or representations needs C.29 and sometimes A.6.0.
Freshness and gate pressurePredictions are attractive when observation is slow or expensive; gate use still needs stated currentness and applicability conditions.

A.3.3:4 - Solution

A.3.3:4.1 - Definition

U.Dynamics is a same-individual dependent kind of U.Episteme. Membership holds when one already identified episteme has the changing subject as its C.2.1 EntityOfConcern and its ClaimGraph, interpreted under the effective reference scheme, substantively declares both a state space and a state-transition law for that subject. The law may include exogenous inputs, constraints, disturbances, and an observation relation.

The C.2.1 ClaimGraph, EntityOfConcern, and effective reference scheme remain the episteme’s identity discriminators. A.3.3 adds no context field or second dynamics identity. A U.ClaimScope, operating region, applicability window, qualification interval, parameter regime, or scale band enters only through the claim that uses it and its subject pattern; changing one can change claim content without becoming an ambient container.

U.Dynamics can declare a deterministic transition, permitted alternatives, a probability law over continuations, or a combination of these. Its time description can be continuous, discrete or hybrid. It can make state-change claims about physical systems, software services, organizations, epistemes, claim portfolios, resource states, architecture characteristics, or another EntityOfConcern. If several subjects are jointly modelled, the C.2.1 EntityOfConcern must itself be an independently identified collection, system, or other admitted subject.

If empirical grounding is claimed, state the C.2.1 EpistemeEmpiricalGroundingRelation.

A.3.3:4.2 - Dynamics statement

Use this compact aid only when the ordinary sentence is insufficient for the current decision:

Dynamics statement:
  CandidateEpisteme:
  EntityOfConcern:
  EffectiveReferenceScheme:
  StateSpace:
  TransitionLaw:
  TimeReference:
  TransitionChoices:
  ProbabilityLawIfSpecified:
  InputsOrDisturbances:
  ObservationRelation:
  ConstraintsOrInvariants:
  ClaimScopeIfReliedOn:
  OperatingRegionAndApplicabilityWindow:
  CalibrationOrParameterSourceIfReliedOn:
  PredictionUse:
  EvidenceOrAssurancePathIfReliedOn:
  StopCondition:

These rows are an optional aid for the minimum claim content and separately governed references needed by the current use. C.2.1 identifies the candidate episteme.

A.3.3:4.3 - Conditional contributions to the work

Use a contribution below when its question arises while constructing or using the state-law account.

Question now requiring an answerContribution
Which reusable way is being identified, and does the episteme describe that way?A.3.1 identifies the U.Method; A.3.2 tests whether an episteme substantively describes that admitted Method.
Does a proposed whole Method have the claimed parts and whole behavior?B.1.5 establishes the part Methods, obtaining methodPartOf relations, whole-forming claims and constraints, whole semantics, boundary and reidentification.
What work is planned, or what was actually performed?A.15.2 identifies the U.WorkPlan episteme coordinating possible future Work; A.15.1 independently admits dated performed U.Work and establishes its actuals.
Does the question concern a continuing role assignment or a particular state episode within it?A.2.5 distinguishes the assignment from its SystemRoleAssignmentStateRelation occurrence: one maximal uninterrupted episode in which the specified predicate holds while that assignment remains in force. Select the subject the modeled change or prediction concerns.
Is one actual bounded change established?A.3.4 requires the changed referent, temporal extent under its continuity rule or formal ordering boundary, boundary conditions, actual characteristic-state and obtaining direct-relation facts, and continuity or reidentification.
Which independently selected organization of constituents and obtaining relations is being used?A.22 identifies that Structure, including a selected transformation-flow organization.
Which operation or law-governed application is admissible over the subject kind?A.6.1 identifies the U.Mechanism episteme declaring the operation family, laws and admissibility conditions. Use E.20 when introducing or revising a mechanism definition in FPF.
Which mathematical substrate or transferred representation supports the model?Use the direct mathematical Method; use A.6.0 when the model needs a reusable formal-substrate declaration. Section :4.7 specifies the C.29 transfer question.
Which observations or source claims support the model or comparison?A.10 supplies the evidence-provenance account; :4.5 states how observations are compared with the law.
Which temporal aspect, such as freshness, delay or a validity window, does the use require, and is the authored temporal claim adequate?C.27.TA supplies the temporal-aspect description; C.27 assesses the authored temporal claim.
What assurance or decision does reliance on the prediction require?B.3 supplies assurance and A.20 supplies a needed internal-constraint result. Use A.21 for a gate decision or the applicable decision pattern for another decision. Apply :4.6’s prediction-use conditions.

A.3.3:4.4 - State-space and transition-law fields

The following optional view groups the claim content of one C.2.1 episteme. Its scheme value has the C.2.1:4.1.2 range EpistemeInterpretationScheme and must interpret the state-space, transition-law and temporal expressions used by this candidate:

U.Dynamics membership view {
  candidateEpisteme: U.Episteme
  entityOfConcern: EntityOfConcern
  effectiveReferenceScheme: EpistemeInterpretationScheme
  claimGraph: {
    stateSpace: reference to an A.19 CharacteristicSpace with the admitted-state constraints
    transitionLaw: state-transition claim
    timeReference: continuous | discrete | hybrid
    transitionChoices: permitted continuations and conditions selecting among them
    probabilityLawIfSpecified?: conditional probability law over continuations
    inputsOrDisturbances?: CharacteristicSet
    observationRelation?: claim or exact relation reference
    constraintsOrInvariants?: claim content
    claimScopeIfReliedOn?: U.ClaimScope
    operatingRegionAndApplicabilityWindow?: ConditionSet
    calibrationOrParameterSourceIfReliedOn?: exact source or calibration-episteme reference
  }
}

stateSpace is claim content of this U.Dynamics episteme. It refers to an A.19 CharacteristicSpace: the product of declared characteristic value sets. The model states which combinations are admitted, through constraints or a predicate over that product. A.3.3.CC constructs such a configuration description; a predictive state can require additional information under :4.4.1.

Characteristics retain their local meanings, units, Scales and comparability rules; C.16 supplies measurement construction when needed. A receiving evaluation may reuse this CharacteristicSpace; its scoring and judgement belong to that evaluation.

Topology, geometry, aggregation or coordinate transformations are supplied over the domain where trajectories or comparisons use them; an independently selected organization of constituents and obtaining relations remains A.22 U.Structure.

transitionLaw is paradigm-agnostic. It can be an equation, relation, kernel, finite-state transition, queueing model, Bayesian update, Petri-net firing relation, simulation rule, learned predictor, or hybrid model, provided the state space, semantic basis, and applicability boundary are declared.

transitionLaw, observationRelation, constraintsOrInvariants, and calibrationOrParameterSourceIfReliedOn are ClaimGraph content or exact references inside the U.Dynamics episteme unless another governing pattern independently identifies one as an episteme, source, relation, or structure.

observationRelation specifies how the model connects its state to the observed quantity. For a deterministic observation, give the map y = h(x), where x is the model state and y the observed quantity. Identity observation (h(x) = x) is allowed only when the claim says the state coordinate is directly observed.

When proposing an exact deterministic one-step law on measured or aggregated coordinates, check whether two admitted states with the same current values of those coordinates, time and inputs can give different next coordinate values. Such a pair disproves that proposed law. Section 5.6 shows how to recover the missing predictive information or give a bounded answer.

For a proposed stochastic one-step law on aggregated coordinates, compare the next-observation distributions from the states it merges under the same time and inputs. If those distributions differ, the current aggregate omits predictive information. Retain a more informative state, condition a distribution over hidden states on the available history, or use a bound sufficient for the question. Equality for every merged group supports the aggregated one-step law under those conditions; longer use must preserve the later outputs and conditions it needs. Section :5.8 separates this question from long-run averaging.

A.3.3:4.4.1 - Construct the state and allowed continuations
  1. Start with the question and participants. Name what can change, which result is needed and the conditions being considered. From the relevant subject account, identify the interacting participants and which of their differences can affect that result.
  2. Describe allowed configurations. Use A.3.3.CC to select the participants’ retained differences, express compatible combinations, and choose independent coordinates, implicit constraints or finite enumeration for the receiving operation. Keep constraints on configurations separate from restrictions on rates or transitions. Sections :5.7 and A.3.3.CC:5 show how changed lengths, stock and job-order questions alter the description.
  3. Recover the information needed for continuation. Separate changing state from parameters held fixed by the model and externally supplied inputs. Determine the initial data required by the proposed law. A position may also need its velocity; a computation may need its instruction position and saved local values. For a field, name its argument domain and value quantities, then obtain the needed initial and boundary data from its law and the modeled arrangement.
  4. Construct the transition. Use the subject’s laws or operation rules to relate admitted states under the inputs. A.3.3.TR constructs that rule: state local effects, combine jointly active relations separately from alternative actions, and derive a small case. Check that the proposed continuation respects the constraints. If a constraint leaves the next state unresolved, supply the missing interaction or operation rule, or retain the alternatives it permits.
  5. Interpret the alternatives. State who or what can select a continuation and under which conditions. Use a probability law when one is supplied or supported for that use. Counting possible continuations establishes their number; probabilities require a rule assigning them weights. The distinction changes the result in :5.9.
  6. Test the description and choose the return. Apply the state-sufficiency comparison above to the prediction or observation needed now. A.3.3.PI constructs the retained state, usable history, predictive distribution or bound for that question and horizon. Return the state and transition account, a sufficient range or conditional conclusion, or the state distinction, law, input or observation still needed. Use C.11.DUA when choosing whether further information is worth obtaining.

The construction can finish before a complete dynamics model exists: a useful result may identify the missing physical interaction or computational rule. Section :4.1 admits U.Dynamics only when the episteme substantively states both the state space and the transition law.

A.3.3:4.5 - Evidence, prediction, conformance, drift, and calibration

Let D be a U.Dynamics about EntityOfConcern E. Let W denote only dated U.Work occurrences when Work is current, and let O denote separately identified observation, telemetry, source, or measurement records.

Derived valueMeaning
trace(W, O, D)ordered observed values produced by the declared observation relation from Work-side facts when present and separately identified telemetry, source, observation, or measurement records
initialState(W, O, D)stated, measured, or estimated state at trace start, with the statement or result and its subject pattern recoverable
predict(D, initialState, inputs, horizon)trajectory or distribution generated by the transition law over the declared horizon
insideOperatingRegion(D, state)check that state satisfies D’s constraints and invariants; separately name the prediction or use and its relevant time or horizon, then check D’s applicability window for that use
residuals(prediction, trace, alignment)discrepancies between the selected prediction and observed trace values under the stated alignment; prediction is the result of the identified predict(D, initialState, inputs, horizon) calculation
fits(D, trace, tolerancePolicy)conformance verdict under a declared tolerance, likelihood, interval, or distributional policy
drift(D1, D2, domain)divergence between two dynamics versions over a declared operating domain

These expressions name claim-side calculations or questions. When an observation, conformance, drift, measurement, evaluation, gate, or assurance result is claimed, the applicable evaluation or measurement declaration states the criterion and result semantics, and the actual application and result are identified separately; C.2.1 identifies any persisted result episteme, and use A.10 or B.3 only for the separately claimed reliance or assurance use.

Calibration Work and its domain result may support a later dynamics episteme whose changed ClaimGraph receives its own C.2.1 identity; an EpistemeEditionRelation obtains only when C.2.1’s continuation predicate is separately established.

A.3.3:4.6 - Prediction use in comparison or gating

A prediction used for comparison, release, gate, assurance, or work preparation states the dynamics edition, predicted Coordinates, operating region, horizon, and relevant error or uncertainty. State any time step, parameter regime or source-currentness condition on which the prediction or receiving use depends. The direct consumer’s policy then states which observation, validation, sensitivity, robustness, stability, or normalization-composition conditions that use requires.

A fresh observation may replace or check the prediction when the policy calls for it. A non-expansive bound, another sensitivity bound, or commutation with a normalization step is required only when the named use relies on that property. If the required conditions are absent or fail, the prediction cannot carry that use. State a needed currentness claim through C.27.TA. Use C.27 when a separate authored temporal-claim adequacy question remains. Obtain a needed internal-constraint result through A.20; use A.21 for a gate decision or the applicable decision pattern for another decision.

A.3.3:4.7 - Apply or transfer a dynamics model

Stay in A.3.3 when the transition law or observation relation uses accepted local dynamics under one explicit semantic basis and applicability boundary.

Use C.29 when the law’s use depends on a contested transfer, cross-domain analogy, learned or speculative mathematical lens, scale change, abstraction, quotienting or reusable explanation across contexts. Establish the preserved and lost structure, operating region or scale window, applicable rival, lens-use boundary and stop condition. Then state the resulting dynamics law and its observation, constraint and calibration conditions here. The direct prediction consumer determines reliance under :4.6.

A.3.3:4.8 - Recover an ambiguous source claim

When a source label such as “process” or “model” leaves the asserted relation unclear, recover one concrete claim before assigning a kind. Establish U.Dynamics membership on the episteme under :4.1 and a Method claim on the semantic way of doing under A.3.1. When an episteme is also claimed to describe that Method, apply A.3.2’s membership rule independently. Section 4.3 supplies the other conditional contributions; use E.10.ARCH if the represented relation remains unresolved.

A.3.3:5 - Archetypal Grounding

A.3.3:5.1 - Reactor control

A reactor team models temperature and concentration with a nonlinear ODE and disturbances. Identify the reactor as the changing subject, specify the two state coordinates, and declare the ODE, disturbances and applicable operating region. The resulting episteme meets :4.1 when those state-space and law claims are present under its reference scheme.

For a thermocouple comparison, the observation relation selects temperature from the modeled state. Align the observed and predicted temperatures over the comparison window, then use the tolerance and validation conditions required by :4.6. Changes to a control policy change the model’s input; selecting and describing that policy uses the Method contributions in :4.3.

If the question concerns an actual regeneration of the catalyst bed, recover that event’s boundary, observed bed conditions and continuity or reidentification under A.3.4. A proposed trajectory remains available for prediction; the actual-change claim needs the occurrence facts.

A.3.3:5.2 - Reliability and operations

A service platform models backlog, arrival rate and incident recovery with a queueing or birth-death model. Compare its predicted behavior with the stipulated service objective under the model’s operating assumptions. If that comparison is used for a release decision, apply :4.6.

A.3.3:5.3 - Evolutionary architecture

An architecture group tracks latency, coupling, operational cost, and change lead time across releases. An episteme about that architecture can be U.Dynamics when its ClaimGraph declares a state space over those characteristics and a discrete-time transition map as the transition law.

A.3.3:5.4 - Knowledge dynamics

A claim portfolio uses belief, evidence weight, source currentness, and contestability as state coordinates. An episteme declaring a Bayesian or likelihood update as the transition law over that claim-state space is U.Dynamics. Identify which incoming observation changes a belief coordinate under the update rule. Name the source content used to support or challenge the specified claim for that update.

A.3.3:5.5 - Natural physical evolution

A U.Dynamics episteme can model the Moon’s motion around Earth using an orbital state space and transition law.

A.3.3:5.6 - When the observed total is not enough to predict

A team wants to predict how much of two removable substances will remain after treatment. For this worked model, let a_n and b_n be their nonnegative remaining masses in kilograms after n cycles. Assume that each cycle leaves half of the first substance and a quarter of the second, with no new material added:

a_(n+1) = a_n/2, b_(n+1) = b_n/4.

The instrument reports only their total, y_n = a_n + b_n. The model’s state is (a_n, b_n); its observation relation maps that pair to the total. The states (1, 0) and (0, 1) both give y_0 = 1 kg, but their next totals are 1/2 kg and 1/4 kg. No deterministic law using only the current total can reproduce the next total for every admitted state.

Retain the two masses when they are available. If only totals are observed, two successive exact readings recover the composition in this model: solve a_0 + b_0 = y_0 and a_0/2 + b_0/4 = y_1, giving a_0 = 4y_1 - y_0 and b_0 = 2y_0 - 4y_1. These masses must be nonnegative.

Substitution into the next-cycle law gives y_2 = (3/4)y_1 - (1/8)y_0; the same recurrence applies at every later cycle. The prediction now uses one previous total as well as the current one. Equivalently, take that pair of totals as the predictive state.

If only the initial total is available, the model gives a range: for integer n ≥ 0, y_0/4^n ≤ y_n ≤ y_0/2^n. Each extreme is attained by putting all the initial mass in one substance. Use this range when it answers the working question; otherwise identify the composition information needed for a narrower answer and decide whether to obtain it. If the two substances instead have the same known retention factor r with 0 ≤ r ≤ 1, the total alone obeys y_(n+1) = r y_n. Thus whether aggregation preserves the needed law depends on the modeled operations.

The calculation assumes exact readings and fixed retention factors. Applying it to treatment data requires accounting for measurement error and establishing the retention law over the intended operating range. Lin and Lu, §§2.1–2.2 explain the broader state/observation and model-reduction problem; the two-substance case here supplies an elementary construction.

A.3.3:5.7 - A constraint changes the state description

Two endpoints move in a plane and are connected by a rigid link of length l > 0. Four Cartesian coordinates obey (x2-x1)^2+(y2-y1)^2=l^2. One configuration description uses three coordinates: place the first endpoint at (X,Y) and the second at (X+l*cos(phi),Y+l*sin(phi)), with phi taken modulo a full turn. The construction makes the length constraint hold. To predict motion under an ordinary second-order mechanical law, also supply the required velocities and the forces or other interactions.

Change the question to longitudinal vibration of an elastic link. Fixed l has removed the extension that matters. Replace it with variable length r, keep its rate of change when required, and obtain the restoring interaction from the physical model. A rigid-link calculation remains useful for its earlier premise; the elastic question needs another state and law. Tong, Classical Dynamics, §2.3 supplies the generalized-coordinate method; the two-endpoint comparison here applies it.

In another practice, two queues share a fixed total of N items. Retain q1 and recover q2=N-q1, with 0<=q1<=N. If external arrivals are admitted, the state must retain the changing total or both queue sizes. The source of the constraint changes, while the construction still identifies which values can vary independently.

A.3.3:5.8 - A long-run average can coexist with predictive memory

Consider a three-state Markov model with this transition matrix. A readout reports 0 for A or B and 1 for C.

Present stateNext ANext BNext C
A0.70.20.1
B0.10.20.7
C0.20.30.5

A present readout of 0 merges states with next-1 probabilities 0.1 and 0.7. The readout alone therefore leaves predictive information unresolved. The stationary distribution is (19/54,13/54,22/54).

At stationarity, after readouts 1,0, the current A/B weights are 2/5,3/5, so the next-1 probability is 23/50. After 0,0, those weights are 73/105,32/105, giving 99/350.

A decision that changes above probability 0.4 takes different actions after these histories. Keeping only the present 0 and the stationary A/B mixture gives 11/32 and loses that difference.

Condition on the available history or retain the resulting predictive distribution. With no information beyond the current 0, the range [0.1,0.7] may already answer a weaker question.

The full finite chain is irreducible and aperiodic, and its long-run proportion of readout 1 converges to 22/54. That long-run result leaves the history-dependent prediction above intact. The finite-chain results are given in Cambridge’s Markov Chains notes, §§9-10; the matrix and conditional calculations here are an authored example.

A.3.3:5.9 - Possible execution orders do not supply a probability law

Two participants A and B each read shared integer x into a local saved value, then write that saved value plus one. Each read or write is atomic, and each participant’s read precedes its write. Initially x=0. To follow the permitted reads and writes, use x, each participant’s position in its two-step procedure and any value already read.

There are six interleavings that preserve those local orders. Only readA,writeA,readB,writeB and its A/B reversal finish at 2. The other four finish at 1: both reads occur before either write, so each participant later writes 1. This enumeration identifies allowed histories that defeat the intended two-increment result.

The six histories have no assigned execution probabilities. Inferring a probability of 2/3 for a lost increment from these counts requires a scheduler model that justifies equal likelihood for the six histories. To obtain the intended result for every allowed history, serialize the read-and-write pairs or supply an indivisible increment operation. If that repair introduces waiting, separately check the progress condition required by the use.

A.3.3:6 - Bias-Annotation

Available measurements can determine the chosen state too early. In :5.6, a convenient total conceals the composition that determines the next total. Compare states that share the proposed observation before treating it as sufficient for prediction.

A familiar equation or a well-fitting simulation can also encourage extrapolation beyond its established conditions. Keep the observation relation and applicable region visible when interpreting its result. The physical and organizational examples require their own domain laws and validation.

A.3.3:7 - Conformance Checklist

CC-A3.3-1 (Membership and identity). A.3.3 judges one already identified U.Episteme. That same individual is U.Dynamics only when its C.2.1 EntityOfConcern is the changing subject and its ClaimGraph, under its effective reference scheme, declares both a state space and a transition law. A.3.3 adds no second identity.

CC-A3.3-2 (Local meanings and applicability). Interpret characteristic names under the effective reference scheme. State the units, operating region, time base, approximation regime, claim scope, qualification window and source-currentness conditions needed to interpret or rely on the model, as claim content or their separately governed values.

CC-A3.3-3 (EntityOfConcern). Name the changing EntityOfConcern. Joint modeling uses the independently identified joint subject required by :4.1.

CC-A3.3-4 (State space). The state description names the A.19 CharacteristicSpace, the combinations admitted by the model, and the information required by its law. Characteristics retain their meanings, units, Scales and comparability rules; topology, geometry or coordinate transformations are supplied when the use needs them. Use A.3.3.CC to construct the configuration description and :4.4.1 to complete the state-and-transition account.

CC-A3.3-5 (Transition law). The law states a relation, map, kernel, equation, rule, learned predictor or simulation rule for the declared time base. Its permitted alternatives, conditions selecting among them and any supplied probability law remain recoverable under :4.4.1.

CC-A3.3-6 (Observation relation). Evidence use states how Work-side facts when present and separately identified work records, telemetry, measurements, observation records, or source records become observed coordinates. Direct observation is declared rather than assumed.

CC-A3.3-7 (Constraints and applicability). Before prediction or gate use, state the constraints, invariants, operating region, approximation regime, parameter range, horizon and scale window on which that use depends.

CC-A3.3-8 (Control or planning procedure). When a reusable planning or control way uses the dynamics, identify that Method under A.3.1. Apply A.3.2 to an episteme claimed to describe it; the dynamics membership test remains :4.1.

CC-A3.3-9 (Observed facts and calibration). Attach resource actuals, timestamps and observations to the Work, measurement or source they describe. Relate them to the dynamics through :4.5. Apply its C.2.1 identity and edition conditions when calibration changes the model.

CC-A3.3-10 (Prediction use). Predicted Coordinates used for comparison or gating state the model edition, domain, horizon, currentness, error or uncertainty, and every observation, validation, sensitivity, stability, or normalization-composition condition required by that consumer’s policy. No universal non-expansiveness or commutation test substitutes for the direct decision rule.

CC-A3.3-11 (Temporal use). State temporal aspects through C.27.TA and establish the adequacy required of an authored temporal claim through C.27, as specified in :4.3.

CC-A3.3-12 (Representation transfer). Apply :4.7 when representation transfer changes the law’s permitted use, and carry the resulting conditions into the dynamics account.

CC-A3.3-13 (Source-label repair). Recover the relation asserted by an ambiguous source label under :4.8 before applying a membership predicate.

CC-A3.3-14 (Actual change). When an actual transformation is claimed, establish A.3.4’s occurrence basis specified in :4.3. A predicted or simulated trajectory describes change under the model’s premises.

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

Recognizable failureRepair
Inferring a transition law from procedure text or a workflow diagram’s layoutRecover the assertion under :4.8, then test for both a state space and a transition law under :4.1.
Treating telemetry as a lawDeclare the proposed law, derive the observed coordinates through :4.5 and compare its consequences with the telemetry.
Using dashboard labels as state coordinates without their meaningsRecover the characteristics, units, scales and comparability rules, and check whether the chosen coordinates retain the needed predictive information.
Treating a simulation as release approvalCheck its predicted result against the receiving decision’s conditions in :4.6, then obtain that decision.
Extrapolating beyond established model conditionsState the applicable region, source-currentness condition and the condition for narrowing or stopping reliance on the model; use :4.7 if the use requires transfer.
Relying on a learned prediction without its domain and error conditionsState its training domain, observation relation, error or uncertainty policy and applicability window before reliance.

A.3.3:9 - Consequences

An explicit state and transition law lets the practitioner calculate a possible trajectory and compare it with observations through a declared relation. A failed comparison can then change a particular state choice, parameter, observation account or applicability condition.

Constructing the model requires interpretable characteristics and a supported law. A bounded prediction may be sufficient; a more consequential use may require additional observation, calibration or validation under :4.6.

A.3.3:10 - Rationale

The needed prediction determines which state distinctions have to remain recoverable. The transition law expresses how those distinctions evolve, while the observation relation says which part of that state the available measurements reveal. Keeping these contributions explicit makes both successful prediction and a failure caused by lost information explainable, across different domain laws.

A.3.3:11 - SoTA-Echoing

Choose a predictive description for the question being asked. In :5.6 the available observation is the total mass, but the next total depends on its hidden composition. Compare the descriptions under the same fixed retention law and exact-reading premises:

Available descriptionWhat it answersAdded effort and limit
One present totalBounds the next total between one quarter and one half of the present total.Needs only the present total when that interval settles the question; it cannot select one exact next value under unequal retention.
The two component massesDetermines the next state and total directly.Requires observing or otherwise establishing the composition.
Two consecutive exact totalsRecovers the two masses, then predicts by the derived second-order recurrence.Replaces a composition observation with a second timed reading; noisy readings require an error account.

For a present total of 1 kg, the interval [0.25, 0.5] kg already settles whether the next total is at most 0.6 kg. It leaves an at-most-0.4 kg question unresolved. Acquire composition or a sufficiently informative history only when that remaining uncertainty matters. Equal retention restores a one-total transition law, so the extra state or reading becomes unnecessary.

Lin and Lu, §§2.1–2.2 supplies the methodological comparison line: selected observables can discard information that reappears as memory in a reduced description. Its projection identity requires closure choices for a usable reduced model; its statistical treatment uses a stationary-process setting.

The elementary calculation above is an authored construction. It selects the state–observation distinction in :4.1–:4.2 and the question-dependent choice in :5.6, with a measurable cost: additional coordinates or observations only when the cheaper description is insufficient.

Strengthen support when the use changes. For data-driven predictive control, de Jong and colleagues, §§I–IV, especially III and Theorem IV.2, compare iterated one-step lifted models with directly learned multi-step predictors. They choose the latter to avoid propagating one-step prediction errors across the horizon, at the cost of learning horizon-dependent prediction matrices and observables. Their constrained controller adds an interpolated initial state and terminal ingredients; recursive feasibility depends on the stated terminal-set assumption and a feasible preceding problem. These are contributions to a particular control problem.

Accordingly, :4.6 makes the intended consumer specify the prediction conditions and properties it relies on. A control decision that relies on recursive feasibility must establish the relevant model, constraints and feasibility conditions. An ordinary comparison can finish with the state, law, observation and applicability information sufficient for its question. The extra cost of a stronger guarantee is incurred by the use that needs it.

Reopen the chosen description when the observation error, retention law, horizon or question changes enough to defeat its information or error bound. Reopen a control use when its measured prediction errors or operating conditions defeat the assumptions supporting its selected guarantee.

Construct before reducing. Tong’s generalized-coordinate construction, §2.3 supplies a way to represent configurations satisfying constraints. His field-theory discussion, §1.1.2 shows that the interpretation and time order of a field law determine its initial data. Section :4.4.1 adopts the common sequence from participants and constraints to predictive information; the particular forces, field equations and solving Methods remain subject contributions. Retaining an implicit constraint can be preferable to eliminating it when the elimination obscures the relation being investigated.

The deterministic comparison in :5.6 and stochastic comparison in :5.8 ask which distinctions prediction needs. Long-run averaging answers a separate question about repeated evolution. In :5.9, a range over allowed executions is available before their probabilities are known. Choose the transition representation that answers the present question with the information available.

A.3.3:12 - Relations

C.2.1 supplies episteme identity, empirical-grounding and edition conditions. A.19 and C.16 supply characteristic and measurement construction; A.2.6 supplies a claim scope when the use relies on one.

A.3.3.CC constructs a description of configurations under constraints. It can return that result before a transition law is available; :4.4.1 then connects the configuration, additional state information and allowed continuations. A.3.3.TR constructs the rule relating states from the supplied interactions, operations and inputs. A.3.3.PI retains the information needed for a prediction, using additional state, history, uncertainty or a sufficient bound.

When an independently selected bounded-model-use structure or obtaining model-use relation changes the receiving use, A.1.1 supplies that account. The other conditional contributions are specified at :4.3; :4.7 governs mathematical transfer into a dynamics use.

A.3.3:End

A.3.3.CC - Construct a Configuration Description under Constraints

Type: Method pattern Status: Stable Normativity: Normative

A.3.3.CC:1 - Problem frame

Use this pattern when you need to describe how participants can be arranged, but choosing values for them separately admits combinations that the modeled situation excludes. A linkage joins its endpoints at a fixed distance; buffers share a fixed stock; a body must fit inside a container. The next calculation needs a description that preserves those connections.

First useful move. Name the participants, the question and one condition joining their values. For two buffers containing three jobs altogether, begin with “q1 and q2 are nonnegative integer job counts, and q1 + q2 = 3.” You can now recover the second count from the first and reject a proposed pair whose sum differs from three. Add buffer capacities when the question concerns which distributions fit.

The Method constructs an interpretable description of configurations: the retained arrangement or combination of participant values, expressed through variables and constraints. It can return an equation, a parametrization, a finite set or another usable representation. The arrangement being modeled and its description remain distinct. The examples assume elementary algebra and, for the linkage, the ordinary meaning of sine and cosine; the Solution explains the representation choices.

The practical gain is a basis for finding, comparing or rejecting configurations and for constructing a later model of change. If an available description already supplies the combinations and distinctions the question needs, use it directly. A prediction additionally needs the state information and law addressed by A.3.3.

A.3.3.CC:2 - Problem

Separate value ranges leave relations unstated. Each endpoint of a rigid link can have a position in a plane, yet most pairs of positions violate the link length. A software representation that permits every pair will include arrangements the intended physical model excludes.

A reduced description can fail in the opposite direction. One buffer count determines the other while total stock is fixed. After external arrivals become possible, keeping that same formula excludes distributions the new situation permits. Counts can also lose job order when the question changes from occupancy to which job is served next.

The construction must therefore retain the differences relevant to the question, express the constraints between them and provide a way to interpret the represented combinations. The choice of variables and the choice of constraints have to be made together.

A.3.3.CC:3 - Forces

ForceTension
Few coordinates and visible relationsEliminating a dependent coordinate can simplify calculation; retaining it can make a physical connection or consistency condition easier to understand.
Convenient notation and coverageOne parametrization may work locally while missing configurations or becoming singular elsewhere.
Compactness and retained distinctionsCounts or aggregate quantities are economical when they answer the question; identity, order or orientation can become consequential in another use.
Constraint fidelity and computational costExplicitly listing admissible combinations works for a small finite set; larger sets often need equations, predicates or a solver.
Present arrangement and possible changeA configuration can satisfy every positional constraint while a proposed motion violates the system’s operation or velocity rules.
Model usefulness and subject knowledgeA coherent constraint account can support a conditional calculation; deciding whether it describes the actual system may require additional subject knowledge or measurement.

A.3.3.CC:4 - Solution

Construct the description from the working question, then choose a representation in which the needed combinations can be expressed and used. If the calculation becomes inconvenient, reconsider the representation. If a premise changes, revisit the variables and constraints it affects.

A.3.3.CC:4.1 - Select the participants and retained differences

State what the reader must find: a fitting arrangement, a compatible assignment, a range of positions or the configurations to which a law will later apply. Identify the participants and the differences that can change this answer.

Give each variable a meaning and a value range. For a physical position, include the reference frame and unit needed to interpret it. For a relation, identify its participants: a distance needs the two endpoints; a job count needs the buffer. A.17 and A.18 supply the Characteristic and Scale vocabulary when the variables are declared as FPF characteristics.

Separate quantities held fixed in the present model from variables to be found. A link length may be a parameter in a rigid-body model and a changing quantity in an elastic model. The distinction follows the modeled use, so a later revision can change it.

Ask whether two arrangements described by the same values can require different answers to the current question. If they can, retain the missing distinction. For example, a pair of queue lengths suffices for occupancy but loses the order of differently treated jobs. State the needed order before attempting the receiving calculation.

A.3.3.CC:4.2 - Express compatible combinations

Start with the product of the separate value sets. Write the conditions selecting the combinations admitted by the model. In a finite problem this may be a table of allowed tuples. In an algebraic description it may use equalities, inequalities or other predicates.

In A.19 terms, CS = product_i ValueSet(Scale_i) is the CharacteristicSpace. A constraint predicate P selects a subset Q = {q in CS : P(q)} used as the represented configuration set. A point in CS supplies a value for every selected slot; membership in Q additionally satisfies the constraints. The same method can be used in ordinary mathematical notation.

Explain what each condition represents. Fixed distance, conserved stock, nonpenetration and an imposed operating limit can all constrain the calculation, but changing each condition changes a different premise. Keep a condition imposed by the intended use recognizable so that revising a preference does not appear to alter a physical law.

When time or an external parameter changes which combinations are admitted, make that dependence recoverable, for example Q(t; p). A moving wall changes a position constraint even before its interaction law is known.

Place restrictions on rates, operations or transitions with those relations. The car constraint in :5.4 limits instantaneous velocity; it leaves the corresponding configuration variables available. A.3.3 uses both kinds of restriction when constructing allowed continuations.

A.3.3.CC:4.3 - Choose a representation that supports the operation

Compare the following forms using the operation the reader needs.

FormHow to construct and use itWhen it becomes inconvenient
Variables with implicit constraintsKeep the participant values and equations or predicates between them. Test a proposed tuple by substitution.Finding a satisfying tuple can require solving coupled conditions.
ParametrizationChoose parameters u and a reconstruction q = f(u) that satisfies the constraints. Perform the calculation in u and reconstruct the required participant values.The chosen parameters may cover only part of the admitted set, repeat a configuration or become singular.
Explicit finite setGenerate candidate tuples, retain those satisfying the conditions and inspect or compare the resulting set.The product of value sets can become too large to enumerate.

For a parametrization, establish the coverage its use needs. If the task claims to represent every admitted configuration, explain how each can be obtained, possibly using several charts or cases. State when two parameter values represent the same configuration. A full turn of an angle repeats an orientation; treating its endpoints as unrelated can break a continuity calculation.

Keep redundant coordinates when they preserve useful structure or avoid a difficult elimination. If the task instead uses a local count of freely variable coordinates, establish independence and regularity of the active equality constraints before subtracting their number. A count alone supplies neither a parametrization nor its global coverage.

When replacing one representation with another, reconstruct the participant values and compare the receiving result. C.29.1 supplies a fuller transfer comparison when the replacement can change an operation or lose information. Group configurations as equivalent only when every member gives the same required answer and the required operations preserve that grouping. This mathematical construction is called a quotient. For an operation on the groups, check that choosing another member of the same group gives an equivalent result. Keep differently labeled endpoints distinct when exchanging them changes the answer.

A.3.3.CC:4.4 - Obtain the configuration result the question needs

Apply the description to the receiving question. If one fitting arrangement is enough, finding a satisfying tuple can finish the search. If the question asks for all arrangements, a range or impossibility, supply the corresponding enumeration, argument or solver result.

For a small finite product, generate a tuple, evaluate the conditions and retain it when they hold. A partial assignment can already be rejected when it violates a constraint whose participating values are known. Otherwise it may still have no satisfying completion: local checks leave the remaining constraints to be solved. For a large search, use a suitable constraint-solving Method; the explicit variables, domains and conditions provide its input.

For equations or inequalities, solve them to the extent needed and substitute the result into the retained relations. If numerical computation is used, interpret its tolerance against the modeled condition. A small residual has a different use from a proof of equality or an established margin from a collision boundary.

A configuration rejected by one condition identifies a premise to inspect. An empty admissible set under the chosen premises is also useful: it can return the task to a size, capacity, connection or requirement decision. Failure of an incomplete search to find a tuple leaves the existence question open.

A.3.3.CC:4.5 - Carry the result into use and revise it when needed

Return the participant meanings, chosen variables, constraints and interpretation needed to use the result. Keep the representation as small as the receiving operation allows. The equations beside a design or the meanings attached to solver input may already carry everything needed.

For a later prediction, recover the extra state information and transition rules under A.3.3. A linkage configuration may need velocities; an occupied-buffer configuration may need service or arrival information. An arrangement that fits now gives a starting point for planning, while reaching it from another arrangement needs an allowed-transition account.

When the question or premises change, revisit the affected part. A variable length replaces the fixed-length constraint; arrivals change a stock constraint; a job-order question needs more than counts. B.5.MPC.R coordinates a revision when that change also affects the physical interpretation, calculation or actual execution.

Recognition of the Method’s result concerns whether the description expresses the selected configurations and supports the receiving operation. Reliance on its physical accuracy uses the subject premises and whatever calibration or uncertainty account that decision needs. C.11.DUA helps decide whether obtaining further information can change the action enough to justify its cost.

A.3.3.CC:5 - Archetypal Grounding

A.3.3.CC:5.1 - A rigid link, then a variable length

Consider a freely placed link in a plane, with distinguishable endpoints A and B and fixed length 2 metres. Use one Cartesian reference frame. The implicit description is

q = (xA, yA, xB, yB), with (xB - xA)^2 + (yB - yA)^2 = 4.

The tuple (0, 0, 2, 0), in metres, satisfies the relation. The tuple (0, 0, 1, 0) fails it. Each endpoint separately has a valid position in the plane, but the second pair violates the modeled link.

For locating the endpoints, use parameters X, Y and orientation phi:

A = (X, Y); B = (X + 2 cos(phi), Y + 2 sin(phi)).

Every pair of endpoints at distance 2 has such a representation. Orientations differing by a full turn describe the same configuration. Reversing the direction while keeping A fixed changes B, so identifying opposite orientations would lose a distinction of this labeled-endpoint model.

Now allow the link to extend or contract with length 0 < r <= 3. Replace 2 by the variable r. The formerly rejected pair (0, 0, 1, 0) is admitted at r = 1. A later motion calculation needs a law for the changing length and whatever initial data that law requires. If the question concerns force carried by a rigid constraint, retaining its equation can help express the force calculation through a multiplier; eliminating the constraint from position coordinates has not answered that force question.

A.3.3.CC:5.2 - Buffer counts, external arrivals and job order

Two buffers each hold at most two jobs. Exactly three jobs are distributed between them. The product of count ranges is {0,1,2} x {0,1,2}; the stock condition is q1 + q2 = 3.

Testing the nine pairs leaves Q = {(1,2), (2,1)}. Equivalently, choose q1 from {1,2} and reconstruct q2 = 3 - q1. The description now supplies both possible occupancy arrangements.

An external arrival can raise the total to four. Keeping q2 = 3 - q1 would omit the possible arrangement (2,2). Retain both counts and use the total applicable to the new question, or include total N as a variable with q1 + q2 = N. Which arrival can occur, and when, comes from an arrival and transition account.

Suppose the next question asks which job a first-in-first-out buffer serves. The sequences [A,B] and [B,A] have the same count, yet they give different next jobs under that rule. Represent the ordered job identities in the relevant buffer. Counts remain recoverable as sequence lengths; the receiving operation gains the distinction it lacked.

A.3.3.CC:5.3 - A body must fit, not just its reference point

A rigid body occupies the one-dimensional interval [x-r, x+r]; x is its centre and r its half-length. It must lie wholly inside [0,L]. Contact with the endpoints is permitted in this model.

Containment gives x-r >= 0 and x+r <= L, hence r <= x <= L-r. For L = 3 and r = 1, the admissible centres are [1,2]. Centre x = 0.5 lies inside the container but places part of the body outside it, so a point-only test gives the wrong fitting answer.

If clearance is required, include the clearance in the inequalities. If L = 1.5 while r remains 1, the interval for x is empty. That conditional impossibility directs the next decision to the body size, container size or permitted deformation. It was obtained by connecting a physical extent, a mathematical inequality and a calculation; no motion simulation was needed.

A.3.3.CC:5.4 - A velocity restriction leaves a configuration question open

For an ideal car rolling in a plane without lateral wheel slip, let (x,y) be the point halfway between the rear wheels and theta the chassis orientation. Let v be this point’s velocity component along the chassis’s forward direction. Then

xdot = v cos(theta), ydot = v sin(theta),

so sin(theta) xdot - cos(theta) ydot = 0. At theta = 0 the rear reference point has ydot = 0.

This equation constrains a velocity at a configuration. It does not impose a fixed y coordinate: a stationary car at another y satisfies the same velocity condition with v = 0. Whether a car can reach a selected parking position from its current one also depends on steering, obstacles and an allowed sequence of motions. Preserve those as a planning question instead of deleting the position from the configuration description.

A.3.3.CC:6 - Bias-Annotation

A familiar coordinate system can make its convenient operations look like properties of the subject. The centre-only containment test in :5.3 demonstrates the loss: the representation retained a point while the fitting question concerned an extended body. Recover the modeled participants and required distinctions before transferring the result.

Minimal-coordinate preference can also hide a useful relation. In the linkage, fewer coordinates simplify position reconstruction, while the retained constraint equation is useful for a constraint-force question. Choose with that operation in view.

Make the interpretation recoverable to the next participant, including when a computation is delegated.

A.3.3.CC:7 - Conformance Checklist

  • Does the description name the arrangement question, participants and differences that can change its answer?
  • Can the reader interpret each variable, its value range and any quantity held fixed?
  • Do the constraints state which combinations are admitted and why those conditions apply to this model or use?
  • If a parametrization or reduced description is used, does it cover the required cases and preserve the distinctions used in the answer?
  • Can the receiving operation obtain its required tuple, set, range or conditional impossibility from the description? Is an unfinished search reported as unfinished?
  • Are restrictions on configurations distinguished from any rate or transition conditions used?
  • When the question changes, are newly relevant quantities, identities or order retained?
  • Is support for physical reliance supplied to the extent that the decision needs, with further inquiry chosen by its possible effect on that decision?

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

Observed or example-demonstrated failureRepair
Choosing valid values for each endpoint but violating the link between themTest the joint tuple against the distance constraint, or reconstruct both endpoints from parameters satisfying it.
Carrying a fixed-total reduction into a model with arrivalsMake the changed total explicit or retain the counts needed to express it.
Answering a job-order question from queue lengths aloneRetain the ordered identities used by the service rule.
Treating a small coordinate count as a global representationSupply coverage and equivalence information; use multiple charts or implicit constraints where needed.
Rejecting a parking position because immediate sideways motion is forbiddenKeep the position in the configuration description. Test a sequence of allowed motions under the relevant steering and obstacle conditions when the receiving question also asks about reachability.
Treating a failed search as impossibilityReturn the search limit, or obtain a complete argument or computation for the impossibility claim.

A.3.3.CC:9 - Consequences

The description makes compatibility usable: a solver can seek a fitting arrangement, a practitioner can locate the condition excluding one, and another participant can reconstruct the represented values. A later law of change starts from interpretable configurations.

Construction takes effort, particularly when constraints interact or a compact representation loses necessary detail. An implicit description may save modeling effort while making each computation harder; a parametrization may reverse that trade-off for the receiving operation. Reuse an adequate description until a changed operation, premise or required distinction defeats it.

A.3.3.CC:10 - Architectural Rationale

Constraint-based construction connects the subject’s arrangement to the mathematical and computational operations used on it. Separating value ranges from compatibility explains why independently valid coordinates can form an inadmissible combination. It also lets the same construction work with continuous positions, finite stocks and ordered data.

The result can be useful before a transition law exists. Keeping that stopping point allows division of work: one participant constructs the configuration description, another supplies interaction or operation rules, and another computes a receiving result. Their contributions remain connected through interpretable participant values and conditions.

Implicit descriptions, parametrizations and finite enumeration expose different operations. Treating one as universally preferable would make the Method fail on either constrained geometry or a small discrete problem. The representation can be refined at the scale its use needs. C.29.1 handles the more general transfer between accounts; here the construction specifically obtains compatible arrangements.

A.3.3.CC:11 - SoTA-Echoing

How should constraints determine the representation? Tong’s Classical Dynamics, section 2.3 develops generalized coordinates and the alternative of retaining constraints through multipliers. At comparable effort for the linkage, reduced coordinates make positions easy to reconstruct; the implicit relation keeps the connection available for a force calculation. Sections :4.2-:4.3 adopt this choice by the receiving question. Its mechanics supplies the physical interpretation of those constraints.

Lynch and Park’s Modern Robotics, section 2.3.2 compares explicit and implicit configuration representations, including singular coordinate descriptions of a sphere. Section :4.3 adopts the coverage and representation question instead of equating fewer coordinates with a better account. Their section 2.4 distinguishes holonomic configuration constraints from nonholonomic velocity restrictions. Section :5.4 carries that distinction into a small motion question. These are construction Methods; the robot geometry and kinematic assumptions must still be supplied for a new robot.

How does physical extent enter a computational configuration? LaValle’s Planning Algorithms, chapter 4, introduction and sections 4.2-4.3, constructs robot configurations, transformations and collision sets. Compared with checking a reference point alone, testing the transformed body’s intersection with obstacles preserves the extent that the fitting question needs. Sections :4.1-:4.2 and :5.3 adopt that connection and the need to state contact conditions. The one-dimensional containment calculation is an authored reduced case. Path planning and collision algorithms retain their own assumptions and costs.

When should a finite constraint set be solved by enumeration? Poole and Mackworth’s Artificial Intelligence: Foundations of Computational Agents, third edition, section 4.1 makes variables, value domains, assignments and constraints explicit. Their section 4.2 compares complete-assignment testing with search that rejects a partial assignment once a relevant constraint fails. Sections :4.2-:4.4 adopt those operational forms. For the two-buffer case, nine combinations make full enumeration inexpensive; a large product calls for a solving Method that exploits its constraints. Early rejection saves search without changing the satisfying set; the remaining search can still be costly.

Together these sources supply complementary ways to construct a configuration description. Reconsider the representation when the needed operation, configuration coverage, contact condition, participant distinctions or computational budget changes. A faster solver cannot recover a physical distinction omitted from its input.

A.3.3.CC:12 - Relations

  • A.3.3 connects configurations to state, transition rules, observation and the information required for prediction.
  • A.17, A.18 and A.19 supply characteristic meanings, value scales, the product space and predicates selecting admitted combinations.
  • B.5.FM constructs a first model for a working question; this Method supplies its configuration construction when compatibility is the difficulty.
  • C.29 and C.29.1 connect the subject with a mathematical representation and compare transfer to another account.
  • C.29.2 constructs a computational formulation when obtaining the configuration result requires a nontrivial computation.
  • A.6.3.RT makes the chosen notation usable under its interpretation scheme.
  • B.5.MPC and B.5.MPC.R coordinate the joint physical, mathematical and computational answer and its revision.
  • C.16 and C.11.DUA support a needed measurement relation and the decision whether additional information is worth obtaining.

A.3.3.CC:End

A.3.3.TR - Construct a Rule for State Change

Type: Method pattern Status: Stable Normativity: Normative

A.3.3.TR:1 - Problem frame

Use this pattern when you can describe a situation’s state but need to work out how it can change. A connection limits two bodies’ positions but leaves their acceleration to be determined. Each participant in a computation has a valid procedure, yet their interleaving can produce an unexpected result. A transformation preserves a mathematical property but can repeat forever.

First useful move. Choose one possible change and write which values it reads, which values it changes, what must hold for it to occur and which other values stay fixed during that step. For a participant that has saved a counter value r, its later write sets x’ = r + 1. It need not produce x’ = x + 1: another participant may have changed x since the read. This small rule exposes the lost-increment case in :5.1.

The Method constructs a rule relating states or describing their continuous evolution under stated inputs. “Allowed” means permitted by that model. The resulting rule can support a conditional calculation, reveal competing continuations or identify a missing interaction, operation or input. A.3.3 supplies the criteria for a U.Dynamics episteme and connects its state space, transition law and observation account.

The finite cases require ordinary arithmetic and conditions. The continuous case additionally uses derivatives and Newton’s equation for an ideal mechanical model. Subject laws and operation semantics supply the content that the common construction combines.

If a suitable state-change rule already answers the question, apply it directly. When only compatible arrangements are needed, A.3.3.CC can supply that result before a rule of change is available. Use the present Method to construct or revise the rule.

A.3.3.TR:2 - Problem

A state constraint and a transition rule answer different questions. Two connected carts may have to maintain a fixed separation; that condition permits many common accelerations. Forces and masses are needed to select one. Similarly, saying that a participant reads before it writes constrains local order but leaves several global execution orders possible.

A rule assembled from separately plausible statements can also be inconsistent or too permissive. An omitted unchanged value may become free to vary. Combining alternatives as if they had to occur together can eliminate legitimate behavior. Treating a desired invariant as an automatic filter can hide the failure the model was meant to investigate.

The practical problem is to construct a connected account from which the needed changes follow, while keeping visible the choices and missing information that affect the answer.

A.3.3.TR:3 - Forces

ForceTension
Observable change and hidden stepsA large modeled step is convenient; intermediate reads, interactions or events may change the result.
Local rules and joint behaviorEach participant can obey its own rule while their combination violates the intended whole result.
Simultaneous relations and execution orderCoupled equations constrain values together; a computation must choose how to obtain a solution.
Constraints and interaction lawsA constraint excludes combinations, but additional laws may be needed to determine rates or successors.
Possibility, progress and probabilityA rule can allow a result without guaranteeing eventual arrival or assigning its likelihood.
Detail and useful returnA complete model may be costly; one counterexample, conditional continuation or identified missing rule can already change the decision.

A.3.3.TR:4 - Solution

Construct the rule around the change that matters to the question. Recover the relevant subject operations or interactions, connect their effects and test the resulting continuation. Revise the state or step when that test reveals an omitted difference.

A.3.3.TR:4.1 - Choose the state, step and inputs

Name what changes and the result needed from that change. Recover the admitted states, using A.3.3.CC when their compatibility is unresolved. Separate changing values, parameters held fixed and inputs supplied from outside the model.

Choose what counts as one step. A step can be one instruction, one transaction, an event, an observation interval or an interval of physical evolution. Say which intermediate effects the model retains. Declaring a read-and-write pair atomic is a substantive assumption about interference, as :5.1 shows.

Retain the values needed to apply the rule. A saved read and an instruction position can matter even when neither is visible in the final output. A mechanical law can require velocities as well as positions. If two cases described by the same retained values require different continuations under the same inputs, return to the state choice or retain the unresolved alternatives. A.3.3 supplies the prediction-sufficiency comparison.

For an interval of evolution, specify the inputs over that interval. One initial input value determines a later result only under an assumption such as a held input or a supplied input law. Distinguish that condition from the initial state.

A.3.3.TR:4.2 - Write each contribution as a relation

For a discrete action, write its enabling condition and its relation between the values before and after the action. A prime can mark an after-value: x is the counter before a write, and x’ is its value after the write. State what remains unchanged when the action affects only part of the state.

An action may leave several after-values possible. Keep the relation broad enough to represent them. An expression x’ = f(x,u) is appropriate when the supplied state and input u determine that after-value; a relation R(x,x’,u) can retain several possibilities.

For continuous evolution, recover the subject laws relating quantities, rates and interactions. These may be written as differential equations, algebraic constraints and any event conditions needed by the model. Include the initial and boundary conditions that the selected law requires. With constrained bodies, identify the forces exchanged through their connection and combine the equations, as :5.2 demonstrates.

The form of an equation does not establish its physical applicability. Recover its domain meaning and conditions from the subject account. When that account is missing, name the missing relation and return the conditional result already obtainable.

A.3.3.TR:4.3 - Combine jointly active relations and alternative actions

Relations that must hold during the same modeled change are imposed together. For two coupled carts, both force equations and the fixed-separation condition hold together. The variables shared by those equations must keep the same meanings, reference frames and units.

Actions that provide alternative ways to take the next step are joined as alternatives. In the counter case, the next action can be an enabled read or write by either participant. Requiring every one of those actions in the same step would describe a different computation.

Check how participants interact through shared values. A local action’s condition and effect refer to the global state at the selected step. If actions occur together, define their joint effect or derive it from the governing relations; textual order alone supplies neither simultaneity nor a conflict-resolution rule.

For equation-based modeling, keep the coupled relations available while choosing a computation. A solver’s evaluation order is part of obtaining a solution. If the actual system has a communication delay, sequential update or other timing effect, represent that effect in the modeled rule. Modelica’s instantaneous event semantics is one explicit modeling convention; it requires modeled delays when those delays matter.

A.22.CGUS can help expose alternative continuations and their conditions when that is the working question. The present construction supplies the rules used to judge those alternatives. The jointly applicable equations can also determine a single continuation.

A.3.3.TR:4.3.1 - Combine continuous evolution with events

When the model mixes continuous evolution and discrete events, state the flow law in each mode, where that flow is permitted, each event’s condition and timing, and its reset relation. A reset specifies which values change and which remain continuous.

For a condition that triggers an immediate event, evolve only to its first occurrence. Stop the continuous segment, apply the event relations, and resume from the resulting state under the applicable law. Process an already-enabled immediate event before advancing time. If the reset enables another immediate event, resolve that event according to the model before resuming flow. Incompatible event relations or an unresolved sequence of instantaneous changes are reasons to return a model or computation limitation.

An event that is merely permitted has a different timing rule: retain the allowed waiting and choice. Where simultaneous events can conflict, supply their joint relation or a justified priority. The thermostat in :5.4 uses mandatory immediate switching and a reset that preserves temperature.

A.3.3.TR:4.4 - Derive a change and test the required property

Work one case far enough to obtain a successor, a rate, a short behavior or an obstruction. Substitute the resulting values into the jointly required relations. In a finite model, enumerate or explore enabled actions from an admitted start; in a continuous model, derive or compute the behavior needed by the question.

To establish that a property P holds throughout reachable behavior, one sufficient induction argument proves two obligations: P holds at the admitted starts, and every permitted step from any admitted state satisfying P preserves P. For continuous evolution, use the corresponding invariance argument for the selected law and domain.

If preservation fails, seek a reachable path to the failing transition or strengthen the assertion using properties of reachable states. A transition from an unreachable state can defeat this proof without exhibiting a behavior that violates P. A stronger assertion I closes the proof when the admitted starts satisfy I, every permitted step from a state satisfying I preserves I, and I implies P. If neither argument is available, return the unproved obligation. Keep the transition rule being investigated intact while repairing the argument.

For states {0,1,2}, start 0 and transitions 0->0, 1->2 and 2->2, P defined as x<=1 holds throughout reachable behavior. The transition 1->2 defeats direct preservation of P, but 1 is unreachable. The stronger assertion x=0 is preserved and establishes P. A path from an admitted start to a violation would instead be a counterexample to the claimed property.

A small test can find a violation; a claim covering all allowed behavior needs an argument or method covering that behavior.

Keep the intended property separate from the rule being examined. If the model is intended to reveal whether an implementation can overflow a buffer, silently clipping its successors to capacity removes that failure from the model. Derive a control rule that prevents overflow, model what happens at overflow, or narrow the claimed operating conditions with a stated reason.

When no successor is found, determine what that result establishes. A contradictory set of equations, a terminal state, a disabled action, a deadlock and an unsuccessful incomplete search call for different next moves. Return the missing conditions or demonstrated obstruction that matters to the present use.

A.3.3.TR:4.5 - Add selection, progress or probability only when needed

State what selects among remaining continuations: an input, a scheduler, a control choice, an unresolved environmental condition or a stochastic mechanism. If the current use needs only possibility or a counterexample, the alternative set may be sufficient.

For a progress question, supply the conditions needed to reach the intended result. An invariant can hold throughout an endless repetition. A decreasing nonnegative integer can establish termination for the Euclidean construction in :5.3; a concurrent protocol may instead require a scheduling or fairness condition. Describe what that condition demands of the participating system.

For a likelihood question, use a probability model over the relevant choices or behaviors. Counting alternatives alone gives a count. Different scheduler rules can assign different weights to the same six counter histories.

For a numerical calculation, name the approximation or update method used to obtain the model’s consequence. Check the result at the resolution and accuracy the question needs. A numerical step can introduce behavior absent from the subject law; C.29.2 supplies the broader construction and comparison of computations.

A.3.3.TR:4.6 - Return the usable rule or the missing contribution

Return the rule with the state meanings, applicable inputs and conditions needed for its next use. Depending on the question, the first useful result can be a permitted continuation, an impossible transition, a counterexample, a sufficient bound or an identified missing law. Use that result in the calculation, design or explanation for which it was constructed.

If a changed question requires previously hidden steps, forces, state information or observations, reopen those contributions and retain the unaffected ones. B.5.MPC.R coordinates revision across the physical, mathematical and computational accounts. C.11.DUA helps decide whether resolving a remaining uncertainty can improve the choice enough to justify the work.

A.3.3.TR:5 - Archetypal Grounding

A.3.3.TR:5.1 - Two correct local increments can lose a global increment

Participants A and B each read an integer counter and later write the saved value plus one. Individual reads and writes are atomic. Each participant reads before it writes. Initially x = 0.

Use the state x, positions pA and pB in the two local procedures, and saved values rA and rB after their reads. Positions 0, 1 and 2 mean before read, after read and finished. Initially pA = pB = 0 and rA = rB = 0; each participant overwrites its saved value before using it.

The four action rules are:

ActionEnabled whenChanged valuesOther values
ReadApA = 0rA’ = x; pA’ = 1x, pB and rB retain their values
WriteApA = 1x’ = rA + 1; pA’ = 2rA, pB and rB retain their values
ReadBpB = 0rB’ = x; pB’ = 1x, pA and rA retain their values
WriteBpB = 1x’ = rB + 1; pB’ = 2rB, pA and rA retain their values

The next step is any one enabled action. From pA = pB = 0, six complete histories respect the local orders. ReadA, WriteA, ReadB, WriteB and its A/B reversal finish at x = 2. In the other four, both reads precede either write; both saved values are zero, so the final value is one.

The result identifies how interference defeats the intended total. Serializing the two read-and-write pairs or supplying an indivisible increment changes the transition rule and removes these lost-increment histories. If serialization introduces waiting, a claim of eventual completion still needs its scheduling conditions.

The ordering rules already suffice to exhibit failure. If a scheduler chooses uniformly among enabled actions at each step, the two serialized histories each have probability 1/4 and the other four each have probability 1/8; the lost-increment probability is 1/2. Uniform choice among the six complete histories instead gives 2/3. Choose and justify a scheduler model when a likelihood estimate is needed.

A.3.3.TR:5.2 - A fixed connection and two force equations determine acceleration

Two carts move on an ideal frictionless straight track. A massless rigid connector keeps their positions q1 and q2 at q2 - q1 = L. Their positive masses are m1 and m2. Signed external forces along the track are F1 and F2. The connector exerts equal and opposite signed forces, written -lambda on cart 1 and +lambda on cart 2.

The positional constraint alone permits many common motions. Differentiating the constant-separation condition gives v2 = v1 and a2 = a1 = a for compatible motion. Newton’s equations for this ideal model give

m1*a = F1 - lambda
m2*a = F2 + lambda

Adding them obtains a = (F1 + F2)/(m1 + m2). Substituting back gives lambda = (m2*F1 - m1*F2)/(m1 + m2). The connection constraint and both interaction equations were needed to determine the common acceleration and exchanged force.

For m1 = 1 kg, m2 = 3 kg, F1 = 4 N and F2 = 0, the result is a = 1 m/s² and lambda = 3 N. Start with q1 = 0, q2 = L and both velocities zero. While the forces remain constant, q1(t) = t²/2 and q2(t) = L + t²/2 in metres when t is in seconds; both velocities are t metres/second.

These formulas provide a state-transition calculation for any chosen interval within those assumptions. If the forces vary, supply their time or state dependence before computing the motion. If the connector is elastic or has consequential mass, its constitutive and interaction account changes the rule. Choosing smaller numerical time steps cannot supply that missing physical relation.

The calculation combines the physical interaction account, mathematical constraints and an executable rule. It also shows why reducing to one position can simplify motion prediction while retaining the connector force lets a designer determine the load on the connection.

A.3.3.TR:5.3 - Preserving a value and making progress require different arguments

For nonnegative integers a and b with a >= b > 0, use integer division a = k*b + r, where k and r are integers and 0 <= r < b. Take the transition (a,b) -> (b,r). Every common divisor of a and b divides r = a - k*b; every common divisor of b and r divides a = k*b + r. The integer quotient makes both implications valid. The transition therefore preserves the common divisors and hence the greatest common divisor. At b = 0, stop and return a.

From (30,18), the successive states are (18,12), (12,6), (6,0). The terminal result is 6. The second component is a nonnegative integer and decreases at every nonterminal step, establishing termination.

By comparison, repeatedly swapping the two arguments also preserves their greatest common divisor but can alternate forever. Preservation alone did not establish progress. The Euclidean rule adds the remainder operation and a decreasing quantity.

This is a transition account for a mathematical construction. An implementation must supply integer operations with the assumed meanings; using a bounded machine representation introduces its own arithmetic conditions.

A.3.3.TR:5.4 - A switch changes the law within the prediction interval

Consider a temperature model with T in degrees Celsius and heater mode OFF or ON. While OFF, temperature falls at 1 degree/minute; while ON, it rises at 2 degrees/minute. OFF at T<=18 switches immediately to ON. ON at T>=20 switches immediately to OFF. A switch changes the mode and preserves T.

Start at T=19, OFF. The requested result is temperature and mode at 1.5 minutes. In OFF mode, flow is permitted while T>18. The trajectory T(t)=19-t reaches 18 at minute 1; the event then switches the mode to ON. The new law gives T(t)=18+2*(t-1) until T reaches 20. At 1.5 minutes the result is 19 degrees, ON.

At minute 2, the upper-threshold event switches to OFF; the next segment uses T(t)=20-(t-2). This continuation follows from retaining the mode and restarting the evolution after each event.

Keeping the initial OFF law through the whole first interval would give 17.5 degrees. Checking the switch only at the interval’s end describes a controller that samples at those times, with different behavior from the supplied immediate-event model. A real controller’s sampling or delay therefore belongs in its modeled timing.

A.3.3.TR:6 - Bias-Annotation

The continuous example uses an ideal Newtonian model with supplied masses, forces and constraints. Its simplicity makes the common construction visible; another phenomenon needs its own interaction account. The concurrent example assumes atomic reads and writes and makes interleaving observable at that scale. Choose the granularity from the interactions and intermediate effects that can change the answer.

Finite examples can make complete exploration look inexpensive. Large state sets and continuous systems may require abstraction, symbolic reasoning, approximation or a less detailed conclusion. The Method permits a useful conditional result before that larger work.

A.3.3.TR:7 - Conformance Checklist

  • CC-A3.3.TR-1 - Working change. The subject, needed result and modeled step are recoverable.
  • CC-A3.3.TR-2 - State and inputs. The rule retains the values it reads, separates held parameters and states input assumptions over the interval being modeled.
  • CC-A3.3.TR-3 - Connected effects. Jointly required relations share their variable meanings; alternatives remain alternatives; unchanged values are stated where omission would permit unintended changes.
  • CC-A3.3.TR-4 - Subject contribution. The physical interactions or operation semantics used by the rule are supplied, or their absence is the returned limitation.
  • CC-A3.3.TR-5 - Worked consequence. An application obtains a continuation, rate, behavior, obstruction or missing contribution relevant to the question.
  • CC-A3.3.TR-6 - Required property. A claimed invariant or progress property has the corresponding argument over the claimed cases. A failed induction step is distinguished from a reachable violation; testing and incomplete search retain their actual reach.
  • CC-A3.3.TR-7 - Choice and likelihood. A selection, progress or probability claim has its own needed conditions.
  • CC-A3.3.TR-8 - Changed use. A change to granularity, constraints, inputs or subject laws reopens the affected rule and its consequences.

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

FailureWhy it changes the resultRepair
Replace saved-value updates with updates of the current valueInterference between read and write disappears from the model.Retain the saved value and instruction position, or justify an atomic operation.
Conjoin alternative actionsThe model demands incompatible changes at once and can lose legitimate executions.State the alternatives and the condition enabling each one.
Leave a local action’s other state values freeA model can introduce changes no participant performs.State the unchanged values or the joint action that changes them.
Filter away violations of the property being investigatedThe model excludes the failure instead of explaining whether the implementation prevents it.Model the behavior or derive the prevention rule, then test the property.
Infer progress from preservationAn invariant can hold in a cycle with no useful completion.Supply a decreasing measure, scheduling condition or other relevant progress argument.
Repair a missing interaction law by changing a numerical settingThe computation still lacks the relation needed to determine the modeled change.Repair the subject account and then select a computation for it.

A.3.3.TR:9 - Consequences

The reader can obtain a connected rule from local contributions, expose interference or missing interactions, and choose a useful return before constructing a larger model. The same construction makes assumptions about step size, inputs, alternative selection and progress available for revision.

The result’s usefulness depends on the supplied subject account and the distinctions retained in the state. Extending the prediction horizon or changing what is observed can require more state information or a different approximation.

A.3.3.TR:10 - Architectural Rationale

The independently useful result is a rule for modeled change. Configuration construction establishes compatible arrangements; prediction sufficiency asks whether retained information supports the needed future distinction. Neither contribution by itself connects the interactions and operations that produce allowed continuations.

A relational description keeps joint constraints and unresolved alternatives available before a computation chooses how to solve or explore them. This supports physical, mathematical and computational reasoning together. It also lets a reader alter the inputs or seek a different unknown without discarding the already useful relations.

Atomic actions, continuous equations, event resets and stochastic transitions have different semantics and can use different temporal scales. Their shared construction requires explicit participating quantities and effects; their specialized solution and validation Methods retain the substantive differences.

A.3.3.TR:11 - SoTA-Echoing

How can local operations or physical interactions jointly determine a change? Keep their state relations available, combine jointly applicable relations, and retain alternative actions until the question or model selects among them. A directly executable update procedure with a fixed order can be used when its order and effects already describe the required behavior; :1 permits direct use of such an existing rule.

For the interference question in :5.1, choosing one execution order loses the alternative histories that can defeat the total. Retaining saved values and local instruction positions costs additional description and exploration, but a single lost-increment history already answers whether failure is possible. For the load question in :5.2, retaining the connection force makes that result calculable; eliminating it is useful when only motion is needed. The trade-off is to keep the relations and alternatives that can change the requested answer, and to stop at a sufficient result. Sections :4.1–:4.3 construct those contributions, :4.4 derives the consequence, and :4.5–:4.6 limit stronger claims and additional work.

Discrete operations and proof. Lamport’s Specifying Systems, chapters 2–3 and §5.7, supplies before/after actions, unchanged values and the distinction between reachable invariance and an inductive assertion. Sections :4.2–:4.4 and :5.1 use these constructions. TLA’s stuttering and fairness conventions serve their stated modeling purposes; choose progress assumptions for the use in :4.5.

Constrained interaction. Tong’s Classical Dynamics, §2.3 compares generalized coordinates and constraint-force treatment. The constraint-force treatment in :4.2 and :5.2 retains the exchanged force when it is needed. Reduced coordinates offer a simpler alternative for motion alone. The cart derivation is an authored Newtonian case with its idealizations stated; another physical theory must supply its own relations.

Coupled equations and events. The Modelica Language Specification 3.7, chapter 8 supplies simultaneously satisfied equations, event semantics and consistent initialization. Its DAE representation separates continuous evolution and event processing: halt at a detected event, resolve its relations and restart integration. Sections :4.2–:4.3 keep joint relations distinct from evaluation order; :4.3.1 and :5.4 teach the continuous/event passage. Modelica supplies one explicit instantaneous-event convention; actual delays enter the model when consequential.

Reconsider the construction if another one retains the same consequential continuations or interaction result at lower effort, or if an observed missing interaction, intermediate effect or event defeats the rule. Methods for efficient exploration, proof, differential-equation solution and protocol design can develop the result when the constructed rule requires that work.

A.3.3.TR:12 - Relations

  • A.3.3 - U.Dynamics identifies a supplied state-and-law account and compares retained information with the prediction being attempted.
  • A.3.3.CC constructs the compatible configuration description from which state-change work can begin.
  • B.5.FM constructs a first model for the working question; B.5.MPC connects the physical, mathematical and computational contributions.
  • B.5.MPC.R revises the affected contributions when the question or conditions change.
  • A.22.CGUS exposes alternatives and case conditions when continuation comparison is needed.
  • C.29.1 compares mathematical representations for the operations they preserve; C.29.2 constructs the computation that obtains the needed result.
  • C.11.DUA selects worthwhile additional information and support for the decision being made.

A.3.3.TR:End

A.3.3.PI - Retain the Information Needed for Prediction

Type: Method pattern Status: Stable Normativity: Normative

A.3.3.PI:1 - Problem frame

Use this pattern when a description of the present leaves a future result unresolved, or when you want to simplify a predictive account without losing an answer that matters. A total can hide components that change at different rates. A current readout can merge situations whose next outcomes have different probabilities. A summary adequate for the next output can lose information needed two steps later.

First useful move. Find two admitted situations that the proposed description treats as the same. Apply the supplied change rule under the same inputs and compare the future result needed by the question. If one kilogram of substance A becomes half a kilogram after treatment, while one kilogram of substance B becomes a quarter, the description “one kilogram remains” cannot determine the next total. It can still supply the range from a quarter to half a kilogram.

The Method constructs information sufficient for a stated prediction: additional state values, a usable history, a distribution over possible states or a bound that settles the question. Its result can also identify which missing distinction would change the answer. It connects the state, transition and observation contributions recognized by A.3.3.

The elementary cases require arithmetic, equations and conditional probabilities. More demanding models need their subject-specific estimation, reduction or computational Methods. The common task is to choose and use the retained information with the prediction it supports.

When an available prediction or bound already settles the working question, use it. When the missing contribution is a rule of change, A.3.3.TR helps construct that rule. The present Method applies when the retained information and the desired prediction need to be reconciled.

A.3.3.PI:2 - Problem

A description can correctly report the present while omitting what determines its continuation. Recovering every underlying detail is often impractical, and a useful future distinction may require only a small part of that detail.

Adding observations does not automatically solve the problem. Their timing, the actions taken between them, measurement error and the assumed law determine what can be inferred. A fitted predictor can also work for one interval and accumulate consequential error when repeatedly applied.

The practical problem is to retain enough information for the future question, and to know what result remains obtainable when the available information supports only a range, a conditional probability or a shorter horizon.

A.3.3.PI:3 - Forces

ForceTension
Compact description and predictive distinctionsAggregation simplifies a model but can merge states that evolve differently.
Observation and model stateA reading reports some aspect of the situation; a prediction may need an unobserved quantity or a distribution over possible values.
Present values and historyA past observation can recover a missing distinction, while a long history can make computation expensive.
One result and repeated predictionInformation can determine one requested output without supplying a state that can be updated indefinitely.
Ideal recovery and measurement errorAlgebra can reconstruct hidden values while amplifying errors in the readings used.
Additional information and usable uncertaintyA bound can settle a decision before identifying the actual underlying state.

A.3.3.PI:4 - Solution

Begin with the future distinction needed in the work. Compare the situations merged by the proposed description, construct a description or uncertainty account that retains the consequential differences, and use it at the required horizon.

A.3.3.PI:4.1 - Specify the future question and the available account

Name the quantity, event or choice being predicted, the horizon and the inputs over that horizon. Specify the accuracy or decision boundary when it changes what information is needed. Predicting a total after one treatment cycle, determining whether it will be below a limit, and estimating a long-run average can require different information.

Recover the rule of change, observation meanings, sampling times and available initial information. Separate uncertainty about the state from uncertainty about the rule or future input. A longer observation history cannot replace an unspecified intervention.

State what the proposed description retains: present readings, model coordinates, past inputs and outputs, derived features or weights over possible states. Where future actions are chosen by a controller, retain the action assumptions needed by the comparison.

A.3.3.PI:4.2 - Compare situations merged by the description

Construct two admitted states or histories with the same retained description. Keep the rule, input conditions and future question fixed. Derive their relevant continuations. A difference in the requested result identifies information lost by that description.

For a deterministic discrete model, let x be its state, u its input, F(x,u) the next state and z = r(x) the retained description. An update z’ = G(z,u) is well-defined when r(F(x,u)) has the same value for every admitted x having the same z, for each input covered by the claim. This condition says how to construct G: choose any compatible x, apply F and retain r of the result. All compatible choices must give the same answer. C.29.1 supplies the general comparison of operations under a representation change.

A prediction of one selected output at a fixed horizon may need less information than an update of the entire retained state. Compare the output that the question asks for. If the result will be used repeatedly, also determine how to update the information from which the next prediction is made.

For a probabilistic model, compare the distributions of the relevant future result under the merged states or histories. The current readout can conceal different next-event probabilities even when the full model is Markov, as :5.2 shows.

One divergent pair refutes sufficiency for a claim covering both cases. Matching a few pairs supports only those comparisons. A general sufficiency claim needs an argument or subject Method covering its stated class; a local counterexample or conditional forecast may already be enough for the present work.

A.3.3.PI:4.3 - Choose a useful repair by its contribution and cost

Use the missing distinction to choose a repair.

  • Retain additional state values. Keep component amounts, velocity, operating mode, pending input or another variable whose difference changes the result. Include a way to obtain or estimate it in the intended use.
  • Retain relevant history. Use observations and intervening actions to infer the missing state or construct a direct recurrence. Derive the needed history length from the rule and observation account where possible.
  • Retain an uncertainty account. Carry the admitted state set or a distribution over possible states and propagate it through the rule. Use probability weights when a probability model is supplied.
  • Answer a weaker question that still serves the work. A range, threshold decision or shorter-horizon result can be sufficient even when a unique future value remains unresolved.

Compare the available repairs by what they change in the decision and by their cost. C.11.DUA helps decide whether another measurement or calculation is worth obtaining. Use an already adequate bound directly.

A finite history can close some models, including the two-substance example. Other projections need a longer history, an approximate memory account or retained uncertainty. Choose the repair from the dynamics and the intended error, rather than assuming a fixed number of observations always reconstructs the state.

A.3.3.PI:4.4 - Construct the prediction and its update

For an algebraic reconstruction, solve the observation and change equations for the hidden values. Check the admitted domain and substitute the result back. Derive a recurrence if the next prediction will use a rolling history. Include how to discard old information and incorporate the next reading.

For a set of possible states, apply the change rule to that set under the admitted inputs, then use the observation relation to obtain possible outputs. A simpler enclosing interval can be enough for a threshold question. Keep the direction of the bound that makes the decision valid.

For a finite hidden-state probability model, let Pij be the probability of transition from state i to state j, and let pi be the current probability of state i given the observations and actions already used. First predict the next-state weights:

predicted_pj = sum_i(pi * Pij)

When a new observation y arrives, multiply each predicted weight by the observation likelihood Lj(y), then divide by the sum of those products. For a discrete readout, Lj(y) is the probability of y in state j. For a continuous readout with a modeled density, use that density at y. Under the Markov and observation assumptions, the normalized weights summarize the history for the next prediction. Use the transition probabilities for the action taken when actions affect the model.

Supply the initial weights and observation likelihoods from the selected model. If the normalizing sum is zero, this update cannot supply posterior weights. Check the observation account, initial possibilities and numerical calculation before proceeding. The weights describe the current uncertainty about the modeled state.

For example, two equally weighted hidden states have Gaussian observation densities with means 0 and 1 and variance 1. An observation y=0 gives likelihoods proportional to 1 and exp(-1/2), so the first state’s updated probability is 1/(1+exp(-1/2)), about 0.622. Using the probability of a single value would give zero for both continuous distributions and prevent this valid update. A learned predictor offers another construction. Train or select it for the output, horizon, inputs and error that matter. A direct prediction several steps ahead and repeated application of an approximate one-step model can behave differently. Evaluate the intended use, including how the predictor receives the information available at each step.

A.3.3.PI:4.5 - Test the horizon, error and changing conditions

Work a case through to the requested future result. Include a pair merged by the simpler description when one motivated the repair. Identify which retained information now changes the calculation.

When readings are imperfect, propagate their stated uncertainty far enough to determine whether it changes the result. A reconstruction can amplify observation error even when the underlying equations have a unique solution. Parameter and input uncertainty require their own treatment; changing a sampling interval can change the update rule.

Check repeated use at its claimed horizon. A universally valid closed update can be iterated while its domain and input assumptions hold. A good fit over one observed step does not provide that result for an approximate predictor. Check the errors or bounds relevant to its use and shorten the horizon or change the account when needed.

Keep forecast performance and aggregate statistics tied to their questions. A model can reproduce a long-run average yet lose the history that changes the next-event probability. Conversely, a useful short-horizon predictor may not reproduce long-run behavior.

A.3.3.PI:4.6 - Return the prediction with the information needed to reuse it

Return the prediction, bound or unresolved distinction in the work where it is needed. Keep its observation meanings, inputs, horizon and consequential assumptions available in the calculation or explanation.

If additional information is worthwhile, identify the measurement, state distinction or model contribution that would change the answer. A result can be useful while the actual hidden state remains unknown. Reopen the affected comparison when the input policy, law, observation scheme or question changes, using B.5.MPC.R where several accounts must change together.

A.3.3.PI:5 - Archetypal Grounding

A.3.3.PI:5.1 - Recover a treatment forecast from component masses or a short history

Let a_n and b_n be nonnegative masses in kilograms after n treatment cycles. Each cycle leaves half of the first substance and a quarter of the second, with no new material:

a_(n+1) = a_n/2
b_(n+1) = b_n/4
y_n = a_n + b_n

The instrument reports only y_n. States (a_0,b_0) = (1,0) and (0,1) both report y_0 = 1 kg but give next totals 1/2 kg and 1/4 kg. The aggregate has lost the composition needed for a unique next total.

One repair retains the two masses and updates them separately. Another uses two successive readings without measurement error. From y_0 = a_0 + b_0 and y_1 = a_0/2 + b_0/4,

a_0 = 4*y_1 - y_0
b_0 = 2*y_0 - 4*y_1
y_2 = (3/4)*y_1 - (1/8)*y_0

The recovered masses must be nonnegative, requiring y_0/4 <= y_1 <= y_0/2. For y_0 = 1 kg and y_1 = 0.35 kg, the masses are 0.4 kg and 0.6 kg, and y_2 = 0.1375 kg.

The recurrence applies at later cycles under the same law. A rolling pair (previous total, current total) can replace the hidden component values for predicting future totals. On receiving a new total, retain it and the former current total. If no new measurement arrives, the recurrence can propagate the pair as a conditional model prediction.

With only y_0, nonnegativity yields the bound

y_0/4^n <= y_n <= y_0/2^n, for integer n >= 0.

For y_0 = 1 kg, the next total is at most 0.5 kg. This settles a requirement at most 0.6 kg without learning the composition. A limit of 0.4 kg remains unresolved by that bound.

Now suppose the two readings each have absolute error at most epsilon kilograms while the retention law is fixed. The reconstructed a_0 can err by at most 5*epsilon, and b_0 by at most 6*epsilon. The formula for y_2 has error at most (7/8)*epsilon from those two reading errors: add the absolute contributions (3/4)*epsilon and (1/8)*epsilon. At epsilon = 0.01 kg this gives 0.00875 kg. A marginal threshold decision must account for that interval; a recovered negative mass calls for checking the measurement uncertainty and the model assumptions.

If both substances instead have the same fixed retention factor r, the total obeys y_(n+1) = r*y_n. Composition is then unnecessary for predicting totals under that law. The needed information changes with the operations and the question.

A.3.3.PI:5.2 - Preserve predictive memory under a coarse readout

A modeled device has hidden states A, B and C, with fixed transition probabilities:

Present stateNext ANext BNext C
A0.70.20.1
B0.10.20.7
C0.20.30.5

The readout is 0 in A or B and 1 in C. A current 0 leaves next-1 probabilities from 0.1 to 0.7, depending on the hidden state. A single value such as their unweighted mean would add an unsupported assumption about which state is present.

For this calculation, take the initial distribution to be the stationary distribution (19/54,13/54,22/54). After observing 1, the current state is C. Its next-state weights are (0.2,0.3,0.5). Observing 0 next removes C and gives current A/B weights (2/5,3/5). The probability of the following 1 is

(2/5)*0.1 + (3/5)*0.7 = 23/50 = 0.46.

For the history 0,0, the first 0 gives weights (19/32,13/32,0). Apply the matrix, retain A and B after the next 0, and normalize. Their weights become (73/105,32/105), giving

(73/105)*0.1 + (32/105)*0.7 = 99/350, about 0.283.

A decision that changes when next-1 probability exceeds 0.4 takes different actions after those histories. Keeping only the latest 0 with the stationary A/B mixture would give 11/32, about 0.344, and lose the relevant difference. The distribution conditioned on history is the useful retained information.

The same matrix also gives a long-run fraction of readout 1 equal to 22/54. This finite positive chain has the conditions for that ergodic average. The average answers an aggregate question; the conditional probabilities answer the next-event question.

Initial weights other than the stationary distribution can give different finite-history predictions. If only a current 0 is known and no mixture is justified, the range [0.1,0.7] remains available. A probabilistic estimate requires its initial and transition account.

A.3.3.PI:5.3 - Distinguish a next output from an updatable state

A processor emits and removes the head bit of a pending finite queue once per step. Two possible queues are (0,1) and (0,0). In both cases the next output is 0, so retaining the next bit answers the immediate output question.

After emitting that bit, the next outputs are respectively 1 and 0. The retained next bit cannot update itself without information about the remaining queue. To predict the next two outputs, retain both pending bits. To keep predicting after later steps and arrivals, retain the relevant queue and arrival account, or a summary proved adequate for the selected output question.

The difference is between knowing one output and carrying information that can be updated for further prediction. A description can be economical and sufficient for a short task. Increasing the horizon changes the information it must supply.

A.3.3.PI:6 - Bias-Annotation

The elementary cases use known change rules and small descriptions. A learned or partially known model can require a separate account of law uncertainty, data coverage and approximation error. A small hidden-state example makes probability updating easy to inspect; larger state spaces can require approximate filtering or bounds.

Observability and useful predictability can also diverge. Identifying every hidden quantity may be difficult while a required output remains tightly bounded. Choose the result from the working question and the information that can economically affect it.

A.3.3.PI:7 - Conformance Checklist

  • CC-A3.3.PI-1 - Future question. The output, event or decision, horizon and consequential input assumptions are recoverable.
  • CC-A3.3.PI-2 - Retained information. The description identifies the state values, observations, history, features or weights used in the prediction.
  • CC-A3.3.PI-3 - Lost distinction. The comparison keeps the rule and inputs fixed and identifies whether merged situations can change the requested result.
  • CC-A3.3.PI-4 - Usable construction. The additional state, recurrence, uncertainty propagation or weaker answer supplies the claimed prediction or identifies what remains unresolved.
  • CC-A3.3.PI-5 - Probabilistic account. A probability claim supplies the initial, transition and observation assumptions it uses.
  • CC-A3.3.PI-6 - Scope and error. A sufficiency or performance claim is supported over its stated cases and horizon, with consequential observation and approximation error accounted for.
  • CC-A3.3.PI-7 - Repeated use. Repeated prediction supplies an update of the retained information or a predictor covering the intended horizon.
  • CC-A3.3.PI-8 - Worthwhile return. The result supplies the information needed for the calculation or decision; further information is sought when its expected contribution warrants the work.

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

FailureWhy it mattersRepair
Use an aggregate as a predictive state without comparing its merged casesComponents or hidden modes can produce different continuations.Compare those cases and retain their relevant distinction or output range.
Substitute a long-run average for a history-conditioned forecastA decision about the next event can depend on recent observations.Condition on the available history or retain its predictive distribution.
Turn a recovered value into a measurement without carrying its assumptionsAlgebraic reconstruction can amplify errors and depends on the supplied law.Propagate the reading uncertainty and inspect the admitted domain.
Repeat a one-step predictor beyond its supported usePrediction error can accumulate, or the retained output may lack its own update.Construct an adequate state update or a predictor for the required horizon.
Keep a longer history without the intervening inputsSimilar observations can follow different actions and call for different forecasts.Retain the actions that enter the transition account.
Obtain a full hidden-state estimate after a bound has settled the questionThe extra work adds cost without changing the present choice.Use the bound and reopen the distinction when another question needs it.

A.3.3.PI:9 - Consequences

The reader can simplify a predictive account while preserving the relevant future distinction, recover missing information from history, or act using a useful bound. The construction also makes visible why a changed horizon, law or observation scheme can require a different description.

The result is relative to its supplied model, observations and use. More retained information can increase storage, estimation and computational cost, and reconstructed quantities can be sensitive to measurement error.

A.3.3.PI:10 - Architectural Rationale

The independently useful result is a description or uncertainty account that supports a prediction. Configuration construction determines compatible values; rule construction relates their changes. Prediction-information work asks which distinctions from those accounts must remain available for the future question.

That question is shared by physical measurement, mathematical reduction and computational state design. The common construction compares merged cases and repairs a consequential loss. Subject Methods supply physical laws, observability results, estimation techniques and efficient approximations.

A present model state, an observed value, a history and a distribution conditioned on observations carry different information. Keeping their roles explicit permits a compact predictor without claiming that its retained values identify every physical detail. A short-horizon output and an iteratively updated predictive state are also different useful results.

A.3.3.PI:11 - SoTA-Echoing

The working question is to obtain a useful future result from the available observations and change law. Retain the distinctions needed by that result, together with their update or uncertainty. An alternative is to reconstruct and carry the full model state. Full-state recovery supports a broader range of subsequent questions and is convenient when those values are already available. It can require extra measurement, estimation or storage when only an aggregate is observed.

Compare the alternatives for the same law, observations, inputs, horizon and decision, including the preparation needed to use each. In :5.1, a one-total upper bound already settles the 0.6 kg limit; reconstructing composition would require information that cannot improve that decision. For a unique forecast, two available totals support a rolling recurrence. In :5.2, a distribution over hidden states supports the history-dependent forecast without identifying the actual hidden state. That filter costs more than retaining the current readout alone, whose merged histories lose the decision-changing probability.

Reduction and memory. Lin and Lu’s Data-driven model reduction, Wiener projections, and the Koopman-Mori-Zwanzig formalism, §§2.1-2.3 separates forecasting from long-time statistics and exposes memory after projection. Sections :4.1-:4.3 fix the output and horizon, compare merged states, and choose retained state, history or uncertainty. The projection identity needs a closure construction to become an economical predictor; the elementary mixture and its bounds in :5.1 are authored.

Filtering a hidden state. Poole and Mackworth’s Artificial Intelligence: Foundations of Computational Agents, third edition, §§9.6.2-9.6.3 derives filtering under Markov transition and observation assumptions. Sections :4.4 and :5.2 propagate state weights, incorporate the observation likelihood and normalize. Section 9.1.1 distinguishes probability masses and densities; :4.4 keeps that distinction for discrete and continuous readouts. The resulting distribution summarizes the history for the supplied model. Learning the model or approximating a larger state space requires further Methods.

Finite-chain forecasts and averages. Cambridge’s Markov Chains notes, §§9-10 distinguish distribution convergence and ergodic averages. Sections :4.5 and :5.2 preserve their different questions. The three-state matrix, histories and threshold comparison are authored. Stationary initial weights are used only where stated; the positive finite chain supports the illustrated long-run average.

Prediction at the intended horizon. De Jong, Breschi, Schoukens and Lazar’s Koopman Data-Driven Predictive Control with Robust Stability and Recursive Feasibility Guarantees constructs multi-step predictors from past inputs and outputs and addresses errors from iterated approximate one-step dynamics. Sections :4.4-:4.5 compare the predictor at its intended horizon and input policy. The paper’s controller guarantees require its specialized construction; the present Method adopts the comparison question.

Reconsider the construction when another description or estimator answers the same question under the same available observations, reader preparation and acceptable error at lower cost, or when a changed law, input policy or consequential prediction failure exposes a distinction it lost. Delay reconstruction, observability, filtering, system identification and model reduction then supply alternative constructions.

A.3.3.PI:12 - Relations

  • A.3.3 - U.Dynamics distinguishes the state, transition and observation contributions used in this prediction.
  • A.3.3.CC constructs compatible configurations; A.3.3.TR constructs the rule of change used to compare their continuations.
  • C.29.1 compares operations across mathematical representations; C.29.2 constructs and judges computations at their intended use.
  • C.16 supplies the observation relation and consequential measurement uncertainty.
  • B.5.MPC connects physical, mathematical and computational contributions; B.5.MPC.R revises them when the question changes.
  • C.11.DUA selects additional information by what it can improve in the working decision.

A.3.3.PI:End

A.3.4 - U.Transformation: Actual Bounded Change Under Conditions

Type: Definitional pattern Status: Stable Normativity: Normative except where a section is explicitly informative

A.3.4:0 - Use This When

Use this pattern when a project must decide whether a change occurred and identify that one change. Ask: what continuing subject changed, where the change begins and ends, which facts differ before, during, and after it, and what rule makes this one occurrence rather than unrelated observations.

First useful move. Name the continuing subject and where the change begins and ends. Write the subject facts that hold before, during, and after that boundary, then state the boundary conditions and the continuity or reidentification rule that make this one occurrence. A desired state, method, plan or model alone leaves occurrence unresolved. Use records or observations for the facts they support.

Missing information about a neighboring claim leaves that claim unresolved; it neither disproves nor establishes the transformation.

Practical gain. Identify one actual change without first deciding whether finer changes are its parts. If no composition or holon claim is needed, continue with the neighboring-object guidance at 4.3. A positive composition claim requires the additional basis in 4.2.1; A.1 applies only after the proposed whole and its construction facts are independently supplied.

Not this pattern when.

  • If the issue is only a semantic way of doing, use A.3.1.
  • If the issue is a description of that way, use A.3.2.
  • If the issue is a state-space and transition-law episteme, use A.3.3.
  • If the issue is a law-governed operation algebra with admissibility predicates, use A.6.1 and E.20.
  • If the issue is planned or dated work, use A.15.2 or A.15.1.
  • If the issue is the selected compound transformation-flow structure, its locus, path, path slice, crossing, or flow valuation, use E.18.
  • If the issue is a mathematical expression used to describe that structure, use E.18.2 and C.29.
  • If the issue is a positive temporal aspect of an object or claim, use C.27.TA.
  • If the issue is adequacy or admissible use of a temporal claim, use C.27.
  • If the issue is holon recognition without a current actual-change identity or constructive transformation-parthood claim, use A.1.

A.3.4:1 - Problem Frame

FPF often needs to talk about change in physical systems, engineered artifacts, organizations, presentation carriers, constituent organizations, architectures, programs, regulatory situations, and research objects. A revised specification needs an early split: changed claim content identifies two C.2.1 epistemes, not one continuing changed episteme. Test the EpistemeEditionRelation when historical continuation between them is claimed.

Open A.3.4 only for a continuing carrier, constituent organization, or other subject with its own identity rule; if revision U.Work first creates the later episteme, use A.15.PROD for that first existence. When the source says process, editing, or construction, recover the changed object from the case.

For transformer constitution use A.3; for signatures and slot discipline use A.6.0 and A.6.5; for problem-to-work carry-through use E.18.1. Section 0 and sections 4.4–4.5 provide the other neighboring routes.

Identify the actual change, then open only the separate neighboring claim the practitioner is making.

A.3.4:2 - Problem

The following substitutions leave actual-change identity unestablished:

  1. Method as transformation. A way of doing is treated as if the change already happened or must happen.
  2. Mechanism as transformation. A law-governed operation algebra states how change may proceed; it does not establish the actual occurrence.
  3. Work as transformation law. A dated work occurrence or trace is treated as if it defined the law governing a reusable kind of change.
  4. Dynamics as permission. A state-space or transition-law episteme is used as if it authorized action, gate passage, or result acceptance.
  5. Temporal claim as transformation. A claim about rate, rhythm, recovery, delay, effort, inertia, freshness, or validity window is used as if it specified the whole change and its conditions.
  6. Formal construction as project-world work. A morphism, proof construction, or formal transformation inside a mathematical substrate is treated as a physical or organizational change without a realization or work relation.
  7. Publication as transformation. A report, dashboard, diagram, source span, or published specification is treated as if it were the changed object or the change event.

These errors are expensive because the wrong neighboring pattern then receives the claim. The project may seek evidence for a method when it needs a work trace, compare dynamics models when it needs a transformation boundary, or invoke temporal-claim adequacy when the real problem is the missing transformation relation.

A.3.4:3 - Forces

ForceTension
Generality and specificityThe same five identification questions must work for physical, biological, software, organizational, documentary, architectural, formal, and epistemic changes. Each domain keeps its own subject and relation patterns.
Possible, planned, actual, modeled, and claimed transformationA source may call a change possible, planned, enacted, observed, modeled, claimed, or published. Only the changed subject, boundary, before/during/after facts, and continuity rule establish an actual U.Transformation; the plan, work, observation, model, assertion, and publication remain separate claims.
Neighboring value competitionA method, mechanism, dynamics model, work occurrence, time claim, evidence item, or result can look like the thing that changed. Test the actual change first; use the separate pattern for each additional claim.
Time and orderMany transformations need a time window, cadence, duration, ordering relation, or refresh condition, but time wording alone does not define the transformation.
Mathematical strength and practical useA formal task, morphism, state space, constructor-theory account, or dynamics model can describe a transformation precisely. Permission, evidence, performed work, and responsibility remain separate questions answered by their own patterns.

A.3.4:4 - Solution

A.3.4:4.1 - Identify the actual bounded change

U.Transformation is the FPF ontic for one actual bounded change. Use the five checks below and keep only the facts needed to distinguish this occurrence:

  1. Changed subject. Name the continuing entity, selected structure, presentation carrier, constituent organization, characteristic-bearing referent, or formal object and apply its identity rule. If an episteme’s claim content differs across the boundary, identify two C.2.1 epistemes and test their EpistemeEditionRelation when historical continuation is claimed; do not call either one the continuing changed subject. Use A.3.4 only for another continuing subject, or use A.15.PROD when revision U.Work first constitutes the later episteme.
  2. Extent and boundary. State the temporal extent of the change, including only gaps admitted by its continuity rule, or state the ordering boundary in a declared formal substrate.
  3. Boundary conditions. State the conditions that delimit this change from adjacent persistence, work, or change occurrences.
  4. Actual change facts. Write the characteristic-state facts and relations that hold before, during, and after the boundary.
  5. Continuity or reidentification. If the subject varies internally, the change pauses, or several intervals are proposed, state the rule that says the subject and this occurrence continue across that variation.

Here, one means one occurrence at the resolution, subject, extent, and boundary needed for this use. It does not mean elementary, atomic, indivisible, or partless. Finer changes and their possible constructive relations require their own identification; sampling or subdividing time establishes neither.

Treat a possible, desired, planned, predicted, modeled, asserted, or published change as claim content until the occurrence facts above hold. A formal transformation can be actual within an admitted formal substrate, but its formula or proof term remains a C.29 representation of that independently identified formal change.

A.3.4:4.2 - First-use transformation basis

Use these questions to identify the occurrence and any additional claim the use needs:

QuestionWhat to writeStop condition
What changed?one continuing subject under its identity rulestop while that subject or its identity remains unresolved
Across which boundary?temporal extent or formal ordering boundarystop if before and after are merely two unrelated observations
What actual facts differ?the relations and characteristic-state facts that hold before, during, and after the boundarystop while the actual facts needed by 4.1 remain unestablished; a record or representation can supply support for those facts
What delimits one occurrence?boundary conditions and continuity or reidentification rulesplit or leave identity unresolved when the rule does not cover the gap
Which later claim or use, if any, relies on this change?name that claim and apply its pattern: for example dated U.Work, a safety evaluation, a publication assertion, or no neighboring usewrite only the relation needed by that branch; if no later use is being claimed, add nothing

Worked first use. For a reactor cooling loop, identify the cooling loop as the continuing changed subject, the thermal-power step and stabilization interval as the boundary, the measured temperature-profile facts before and after it, and the operating conditions that delimit the episode. These facts ground CoolingLoopTransformation-7 : U.Transformation. The revised operating method, control-law episteme, measurements, safety evaluation, and release decision remain separate objects. This short case identifies no dated adjustment U.Work occurrence.

Choose only the next claim that the use needs:

  • Work. Establish the A.13 basis and independently admit the dated U.Work occurrence under A.15.1; use F.6 afterward only for precise attribution to that same assignment. If both work and transformation participants are identified, apply the routes and stops in 4.2.4. The short reactor case has not identified that work occurrence, so it makes no work-to-change claim.
  • Safety evaluation. Use case-local evaluatesTransformation@PlantSafety-v4(SafetyEvaluation-7, CoolingLoopTransformation-7, CoolingLoopSafetyCriterion-v4) only when all three participants are identified and the predicate’s obtaining conditions hold. Identify a decision separately when one is claimed.
  • Publication. Use a C.2.1 assertion whose EntityOfConcern is CoolingLoopTransformation-7 and identify its E.24.PUB publication occurrence.

If none of these uses is being claimed, keep the identified transformation and add no neighboring relation.

If the result is one identified transformation and the use needs no positive composition or transformation-holon claim, continue at 4.3. Open 4.2.1 and 4.2.3 only for those additional claims.

A.3.4:4.2.1 - Keep proposed component and whole-configuration changes separate

Use component change and whole-configuration change for the respective proposed uses of actual U.Transformation occurrences already identified through A.3.4:4.1. Those descriptions alone establish no parthood relation.

Identify every proposed component change and the proposed whole-configuration change independently. Temporal inclusion, shared subject, neighboring flow positions or parts of a representation establish neither composition nor absence of finer parts.

The neighboring general patterns do not by themselves settle the composition question. A.22 can identify a selected structure whose relation organization changes; C.27.TA can identify temporal aspects; A.14 and C.13 define structural mereology and a Γ_m construction trace. None of those results by itself says that several actual changes compose one actual change. A materialized Γ_m.sum trace is a C.2.1 episteme about identified entity-part relations, assembly, and direct identity or reidentification conditions.

One independently identified change of a selected configuration can therefore remain a valid configuration transformation. If the use needs no positive composition or transformation-holon claim, continue with that transformation and the neighboring-object guidance in 4.3-4.8. If it does need such a claim, retain the identified changes and stop with missing transformation-composition governor; a proposed local compound claim also stops with missing derivation substrate when no admitted constructor semantics supplies it. Neither stop says that composition is false or that any change is partless.

A.3.4:4.2.3 - Apply A.1 only after composition is independently established

Membership in U.Transformation supplies no holonhood. To apply A.1 to one change as a whole, independently identify the candidate, constituents, constructive part relations and assembly under a governing construction rule. Recognition of an individual occurrence supplies none of those missing construction facts. This pattern defines no transformation-composition rule; where that needed governor or derivation substrate is absent, positive A.1 classification on that basis stops. The stop does not disprove the existence of a whole or its parts.

When an independently admitted construction supplies one whole transformation, apply A.1 without changing its test. A.1 requires the candidate, constituents, constructive part relations and assembly, reidentification rule, composition-grounded whole-level characteristic, and possible participation in a larger constructive assembly. Recover those facts from their governing patterns.

A.1 distinguishes satisfaction of its criterion from recognition, assertion, assurance and receiving-work disposition; use its account when those separate claims matter.

Apply that boundary to the proposed case:

  • a pressure increase may be identified as one U.Transformation at the resolution needed by the use; sampling or subdivision establishes neither constructive parts nor absence of such parts;
  • a switch transition may be treated as effectively instantaneous at the selected temporal resolution and identified as one U.Transformation; that resolution claim establishes neither indivisibility nor parts;
  • subintervals of continuous biological growth may each be independently identified as transformations, but this pattern does not decide whether they compose one change;
  • a formal transformation can be actual under a selected formal substrate, while its formula, morphism, or proof term remains a C.29 representation and supplies no holonhood;
  • mounting, wiring, connection, and whole-configuration changes may each be identified independently; a positive A.1 claim based on their composition requires the additional construction facts above.
A.3.4:4.2.4 - Keep work and production claims outside transformation identity

Do not infer a work-to-change connection from shared timing, a common affected subject, or the word successful. Once the U.Work and U.Transformation participants are identified, apply a matching current subject predicate or, when A.6.RCD disposition 2 permits it, state the local compound claim over named base facts and an admitted substrate. Preserve the applicable A.6.RCD result: missing-governor for an absent needed governing rule; missing-information for an unavailable fact needed by an existing test; factually unsupported when sufficient facts fail its positive test; that rule’s inapplicable result when applicability fails; or missing-substrate when the proposed derivation lacks admitted constructor semantics.

Production is a separate question. For a production claim, test production-work participation, first existence of an entity, and production completion separately. Apply A.15.PROD to the work, work part, subject-identity facts, completion criterion, and direct effect facts. A.3.4 contributes only the independently identified transformations.

Filled positive branch — result: C.2.1 assertion BuildWorkPopulatedStore-12 states the local connection between ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work and ArtifactStorePopulationTransformation_12 : U.Transformation. The BuildOps predicate BuildWorkPopulatedStore@BuildOps-v12(work, transformation) holds only when the storeWrite application performed as part of that work changes the same ArtifactStorePartition_12 across the same boundary. BuildApplication_12 supplies the performed application and its builtBinary -> ReleaseBinary_12 binding; the partition’s before/after artifact-presence facts ground the transformation. This is an A.6.RCD disposition-2 local compound claim, not a universal FPF work-to-change kind or occurrence.

Pump 14 — current result and earlier no-governor stage: A.3.4 identifies T-P14-PRESSURE-RISE : U.Transformation as the bounded change of continuing HydraulicLoop_P14; the loop’s discharge-pressure characteristic is belowBand at the opening boundary and inBand at the closing boundary. The current case record contains relation-declaration episteme P14-REL-2026, owned by Pump14OperationsRelations, which declares AdjustmentWorkCausesPressureRise for participants W-P14-ADJUST-1010-1020 : U.Work and T-P14-PRESSURE-RISE; a separately stated case fact satisfies its actual-causation predicate. Therefore write: W-P14-ADJUST-1010-1020 caused T-P14-PRESSURE-RISE.

In the earlier case record, P14-REL-2026 is absent; at that epistemic stage, keep the same Work and transformation, return missing-governor: work-to-change claim for <W-P14-ADJUST-1010-1020, T-P14-PRESSURE-RISE>, and route the missing declaration to Pump14OperationsRelations instead of asserting causation.

A.3.4:4.3 - Distinguish the change from claims and representations

When the use needs the following contributions, keep their different objects and criteria recoverable:

LayerObject to keep distinctWhere to check it
actual bounded changeone U.TransformationA.3.4 identifies the continuing subject, extent, boundary conditions, before/during/after facts, and continuity rule
facts about the changed subjectrelation occurrences and characteristic-state facts that holdeach subject pattern defines the participants, obtaining rule, and identity
reusable change semanticsone predicate-definition episteme when repeated use needs the same ruleA.3.4 or the subject pattern states how the listed base facts satisfy that predicate
transformation assertionone C.2.1 episteme asserting that the transformation or base facts obtainC.2.1 identifies claim content, EntityOfConcern, and effective reference scheme; scope and viewpoint remain neighboring relations
representationa representation of the identified change or subject, such as a formula, diagram, or traceC.29 governs correspondence to independently recovered objects
evidence or evaluation resultan episteme used to support or evaluate the assertionthe measurement, evaluation, evidence, provenance, or assurance pattern defines or constrains that use

A verbal predicate does not turn every obtaining relation occurrence into a transformation. Assignment, availability, installation, and temporal order can obtain without change. Conversely, one actual transformation may require several relation facts without being identical to any one of them.

Use an existing relation that states the needed fact. Otherwise apply A.6.RCD: a local compound claim is available only when its base facts and admitted substrate are present; preserve the applicable stop when a required basis is missing. Introduce reusable predicate-definition content when repeated uses need the same rule. A new durable relation kind needs its own obtaining and occurrence-identity law. A task, morphism, operation family and relation occurrence have different meanings and cannot occupy one generic transformationRelation field.

A.3.4:4.4 - Add neighboring objects only for the claim being made

For each neighboring claim, identify the object it needs and state that object’s relation to the transformation, changed subject, work, or later use.

Claim being madePattern and boundary
reusable semantic way of doingA.3.1 governs U.Method
claim-bearing account of that wayA.3.2 and C.2.1 govern U.MethodDescription
typed operation arguments or resultsA.6.1 governs the operation declaration and application binding; these are not generic transformation inputs or outputs
intended workA.15.2 governs U.WorkPlan
performed workA.15.1 governs dated U.Work occurrences; for the named work/transformation pair, apply the routes and stops in 4.2.4
transformation-flow location or compositionE.18 governs selected TransformationFlowStructure
mathematical expressionE.18.2 and C.29 govern representation
dynamics modelA.3.3 governs the episteme
evidence, measurement, evaluation, or assuranceapply the measurement, evaluation, evidence, provenance, or assurance pattern that states the support or judgment relation
description, view, publication, form, or carrierC.2.1, E.17, and E.24.PUB keep the episteme, view membership, publication occurrence, publication form, and carrier distinct
input, output, result, outcome, deliverable, or handoffname the participant and state the relation claimed, using its governing pattern. The source word by itself identifies neither a kind nor a universal transformation slot.

A declared post-state is part of a transformation description. An actual post-boundary state or changed entity is a fact about the subject. When wording such as result carries a separate claim, make its participants and relation recoverable from that use. Acceptance, delivery, publication, and downstream effect remain separate. U.Transformation has no generic ResultRef or OutputConditionOrPortRefs slot.

When the use needs an episteme about the transformation, identify it through C.2.1: claim content, the transformation or another subject as EntityOfConcern, and the effective reference scheme. Add scope, viewpoint, empirical grounding, edition, publication, or representation only when the use separately requires that relation.

A.3.4:4.5 - Temporal and problem-to-work questions

Claim being madePattern to use
positive temporal aspect or temporal-claim adequacyC.27.TA or C.27
problem-to-work carry-throughE.18.1; it carries the identified objects

A.3.4:4.6 - Description And Publication Boundary

A description or representation can convey a transformation or provide evidence for a use. Examples include a dynamics model, diagram, trace and proof.

Use the pattern for the represented claim or publication: for example A.3.2 for a MethodDescription, A.3.3 for a dynamics episteme, or E.24.PUB for a publication occurrence. Identify the transformation independently of that descriptive or publication relation.

A.3.4:4.7 - Formal Transformation And Project-World Realization

A morphism, constructive proof, or formal state transition can correspond to an actual transformation of a formal object within the selected formal substrate. The formula, morphism, or proof term is its C.29 representation.

For a physical, clinical, organizational, architectural, documentary, or epistemic change, a formal expression may specify, predict, constrain, or compare the change. First identify the changed subject, boundary, and before/during/after facts. If a later claim says that dated U.Work caused, realized, or participated in that transformation, apply the routes and stops in 4.2.4 to the named pair.

A.3.4:4.8 - Multi-reading source phrase

Use this example when one phrase seems to name method, mechanism, formal construction, work, evidence, and transformation at once:

“The workflow algorithm transforms the emergency-stop specification, and the proof shows the new plant boundary is safe.”

Keep these objects separate:

  • the workflow or algorithm may designate a U.Method or U.MethodDescription;

  • the proof is a claim-bearing episteme using a declared formal substrate;

  • when claim content changes, the earlier specification episteme and the later specification episteme are distinct C.2.1 identities; EpistemeEditionRelation relates them only when its historical-continuation predicate obtains;

  • dated editing or review is a U.Work occurrence admitted under A.15.1;

  • edition succession alone establishes no transformation of one continuing episteme. Open A.3.4 only for a separately continuing subject—such as a physical or digital carrier independently identified under its domain identity rule (with expression bearing governed by E.24.PUB) or a claim-bearing constituent organization—after naming its boundary, before/during/after facts, and continuity rule; otherwise stop without a transformation claim;

  • if revision U.Work first constitutes the later episteme, open a separate A.15.PROD first-existence question: name the productIdentitySpecification episteme, the named applicability predicate or filled local claim that applies it to the candidate basis, subject context, and boundary, the identityClosingWork, and the work-to-change and change-to-identity predicates or local compound claims.

    If the product-identity specification is claimed to continue an earlier identity-rule specification, test their separate C.2.1 EpistemeEditionRelation. When that relation is unestablished, leave continuity unresolved and evaluate the later identity-rule specification’s applicability independently; call it non-continuing only when the applicable continuity rule supports that conclusion.

    Return the applicable A.6.RCD stop for either named connection that lacks its required basis;

  • a plant change, safety evaluation, assurance claim, gate decision, and publication are separate objects and relations.

If only the proposed wording and proof are available, do not assert a project-world plant transformation. Different claim content gives two epistemes; test their EpistemeEditionRelation when historical continuation is claimed. Assert an A.3.4 specification-side transformation only for a separately continuing carrier or constituent organization with its boundary, before/during/after facts, and continuity rule.

If the question instead concerns the later episteme’s first existence, use A.15.PROD and stop when either direct connection lacks a basis.

The proof can support an assertion only through its evidence or derivation use.

A.3.4:5 - Archetypal Grounding

A.3.4:5.1 - Physical system change

A nuclear-plant team says that a revised operating method stabilized a temperature profile after a thermal-power change. Result: CoolingLoopTransformation-7 is identified from the continuing cooling loop, stabilization interval, operating conditions, and before/during/after temperature facts. The method is U.Method; the control-law model is an episteme; measurements and the safety decision use their own patterns. This short case names no dated adjustment U.Work occurrence or work-to-change predicate, so it makes no such connection. If that claim is later needed, name both participants and apply 4.2.4.

A.3.4:5.2 - Biological editing

A CRISPR project says that an editing protocol changed a DNA target while keeping off-target risk under a bound. Result: identify the biological transformation from the continuing DNA referent, edit interval, boundary conditions, and sequence facts. Keep the protocol description, biochemical mechanism, lab U.Work, sequence measurement, risk evaluation, acceptance verdict, and publication separate. This sketch names neither a lab-work/transformation pair nor a matching predicate, so it asserts no connection between them; apply 4.2.4 only if that later claim is needed. For phrases such as edited sequence, lab output, or accepted result, name the participant and relation needed by the receiving claim.

Spontaneous non-agentive case — result: SeedlingFirstLeafUnfolding-B17 : U.Transformation is an actual first-leaf unfolding without an actor, method, or work claim. The continuing subject is the already existing Seedling-B17. Its boundary runs from unfolding onset t0 to the first stable full-expansion state t1; leaf-configuration and exposed-surface facts before, during, and after distinguish the episode under the stated growth conditions. The same-seedling rule permits ordinary cellular turnover and growth but excludes division, grafting, death, or replacement.

At this resolution the case asserts neither finer transformation parts nor partlessness. If a later use asks for an actor, apply A.3; if it asks for work, apply A.15.1 and then 4.2.4. Otherwise keep the case non-agentive and do not open A.15.PROD.

A.3.4:5.3 - Specification repair

A safety specification is revised so that an emergency-stop boundary no longer permits two incompatible readings. First result: EmergencyStopSpec-E1 and EmergencyStopSpec-E2 are different C.2.1 epistemes because their claim content differs. EpistemeEditionRelation(EmergencyStopSpec-E1, EmergencyStopSpec-E2) may relate them when its historical-continuation predicate holds; neither is one continuing changed episteme.

A.3.4 may instead identify a change of EmergencyStopSpec-Carrier-17 : U.Entity if its physical or digital domain identifies the same carrier across the editing interval and the before/during/after expression-bearing facts under E.24.PUB plus the carrier-continuity rule are present. If the carrier identity, facts, or rule are missing, no carrier transformation follows.

If editing U.Work first constituted EmergencyStopSpec-E2, name that work and the transformation by which the later identity closed. Apply 4.2.4 to the work-to-change pair, then apply A.15.PROD to the change-to-identity pair. Each connection needs a matching predicate or valid local compound basis; preserve the applicable A.6.RCD stop for either pair that lacks its required basis. The repair method, ambiguity-removal assertion, review result, and publication of the later episteme remain separate.

A.3.4:5.4 - Formal construction

A proof constructs a formal object and shows that a morphism preserves an invariant. Result: the proof supplies a formal object and an invariant-preservation claim. To establish one formal transformation within the declared substrate, identify a continuing formal subject under its identity rule and the actual differing facts across the ordered boundary. The proof term and morphism expression are representations; publishing the proof is another relation. If a later claim says that dated work realized the transformation, apply the routes and stops in 4.2.4 to the named pair.

A.3.4:5.5 - Architecture change

An architecture team performs dated architecture U.Work. During the same interval, a selected structure undergoes a separately identified transformation: an interlevel conflict decreases while a key architecture characteristic stays within bounds. Result: the work and transformation are both present, but this sketch does not connect them. If that connection is needed, name both participants and apply the routes and stops in 4.2.4. Characteristic evaluation, decision, and publication remain separate.

A.3.4:5.6 - Functional transformer in a flow

When a sentence says that a system transforms input to output or implements an algorithm, recover the subject and the claim it makes. Identify the continuing changed subject for an actual-transformation claim. Use A.3 for an acting-system claim, and A.13 followed by A.15.1 for a dated Work claim. Identify participant, port or operation bindings when the sentence uses them, and use E.18 when it claims a position in a transformation flow. A Method or MethodDescription is needed only for the corresponding way-of-doing claim.

Examples:

  • A pump can be the acting system while the actual transformation is the bounded pressure change of an identified fluid volume. Inlet and outlet pressure facts are characteristic-state and port facts; the pump curve is a model episteme.
  • A warehouse can perform receiving U.Work while pallet-location and inventory-state changes occur. If a later use needs a work-to-change claim, name the pair and apply 4.2.4. Orders and pallets keep their work, transfer, resource, or affected-subject relations.
  • A neural-network block can participate in an activation transformation. Tensor-shape declarations, the attention method, dated inference work, benchmark evaluation, and architecture allocation stay separate and use their own patterns.

A.3.4:5.7 - Assembly changes before PumpSkid identity

Before asking whether PumpSkid 7 exists as one entity, identify the already existing base frame BF-7, pump unit PU-7, motor MU-7, junction enclosure JE-7, pipe spool PS-7, cable set CS-7, and their still-open mechanical, electrical, and fluid interfaces. AssemblyConfiguration-7 is the A.22 selected structure made from those referents and their actual attachment, terminal, and flange-connection organization during assembly. It is not another name for a future PumpSkid 7 entity.

The mounting transformation changes the frame-to-pump and frame-to-motor attachment facts. The wiring transformation changes cable-to-terminal connections. The fluid-connection transformation changes spool-to-flange and seal facts. Identify each independently through its subject, extent, boundary conditions, before/during/after facts, and continuity rule. The change of AssemblyConfiguration-7 can also be identified if those attachment, terminal, flange, and seal relations have declared participants and obtaining rules and the selected structure has its own boundary and continuity rule. Call that occurrence the configuration transformation. The other three changes do not become its components merely because they occur in the same assembly episode.

No current FPF relation in this case says that the mounting, wiring, fluid-connection, and configuration changes compose one transformation. Keep all four changes and stop before a part or whole-transformation claim. The result from 4.2.1 is missing transformation-composition governor; a proposed local compound claim also lacks an admitted derivation substrate.

Positive A.1 classification on that basis stops as well, because no accepted composition result supplies a whole candidate and all six constructive components required by A.1. The point at which a separate PumpSkid 7 identity rule first becomes true remains an entity-identity inception question; production completion, commissioning work, evidence, acceptance, and any B.2 whole-reidentification claim also remain separate.

A.3.4:6 - Bias-Annotation

A familiar representation can draw attention away from the actual subject and its continuity: a process diagram suggests work steps, while sampled time points suggest parts of a change. Return to the occurrence facts before inferring enactment or composition. The non-agentive seedling case also shows why identifying change need not begin with an acting system.

A.3.4:7 - Conformance Checklist

CheckConformance statement
CC-A34-1One continuing changed subject, temporal extent or formal ordering boundary, boundary conditions, before/during/after facts, and continuity or reidentification rule identify the transformation. Changed claim content instead yields two C.2.1 epistemes and a separate edition-relation question.
CC-A34-2Actuality and transformation identity require the complete basis in 4.1, even when a method, plan, model, representation, or individual relation fact is available.
CC-A34-3Every subject fact uses the pattern that defines its relation or characteristic; no union-valued transformationRelation field is used.
CC-A34-4Any additional method, operation, work, flow, representation, evidence, evaluation or publication claim retains its own objects and relations.
CC-A34-5A transformation assertion is a C.2.1 episteme about the actual transformation or base facts.
CC-A34-6Use C.27.TA for temporal aspects and C.27 when an unresolved adequacy question changes the receiving action; neither replaces transformation identity.
CC-A34-7Use E.18 for the selected flow structure and C.29 for mathematical representation; ground actual transformation and work claims separately through A.3.4 and A.15.1.
CC-A34-8Evidence, assurance, gate, acceptance, and decision authority are not inferred from the transformation or its description.
CC-A34-9input, output, result, outcome, deliverable, and handoff remain wording cues until the reader names the participant and relation being asserted.
CC-A34-10When performed U.Work is claimed to cause, realize, or participate in a transformation, the case applies an existing subject predicate, states one A.6.RCD disposition-2 local compound claim over named base facts, or preserves the applicable A.6.RCD stop for the pair. Co-occurrence and a shared subject are insufficient.
CC-A34-11Every proposed component change and whole-configuration change is identified independently. Shared timing, referent, work, flow position, or representation establishes neither composition nor partlessness.
CC-A34-12A positive transformation-composition claim requires a governing rule; preserve the missing-governor or missing-substrate result from 4.2.1 when its required basis is absent.
CC-A34-13Test a transformation under A.1 only after an independently admitted construction supplies the candidate and all six required construction facts. Recognition, assertion, assurance and receiving-work disposition remain separate.
CC-A34-14When a production claim is current, test production-work participation, entity-identity inception, and production completion separately under A.15.PROD, using the work, work part, subject-identity facts, completion criterion, and direct effect facts.

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

Anti-patternSymptomRepair
Method name as change“This method transforms X” is treated as an actual occurrence.Name the continuing changed subject, boundary, and before/during/after facts; keep the method under A.3.1.
Process diagram as workA workflow diagram is treated as enacted work.Recover what the workflow diagram represents; use E.18 for a claimed transformation-flow structure or A.3.2 for a MethodDescription claim, and A.15.1 to establish any claimed dated Work independently.
Dynamics model as permissionA transition law is used to approve action.Keep A.3.3 for the model. Determine whether the action is permitted under the applicable rule; obtain evidence or assurance when that rule or the decision requires it.
Temporal trend as interventionA rate or rhythm trend is treated as proof of changed behavior under an intervention.Use C.27.TA for the temporal aspect and C.27 when an unresolved adequacy question changes the receiving action. Identify the transformation independently; if the claim attributes it to intervention Work, apply 4.2.4.
Formal construction as workA morphism or proof construction is treated as work performed in a project-world object.Use C.29 or the direct formal pattern for the mathematical relation; name realization and work separately.
Publication as transformationA dashboard or report is treated as the changed state.Use publication or source patterns for that artifact; identify the changed subject separately.
Sliced trajectory as compositionSamples, subintervals, method steps, work parts, concurrent changes, or flow nodes are declared components of one transformation by containment or proximity.Identify each actual transformation independently and require the governing rule and derivation basis in 4.2.1 for a positive composition claim. Sampling or subdivision also supplies no evidence of indivisibility.
Resolution-level identification as partlessnessA change identified as one occurrence at the resolution chosen for the task is treated as necessarily atomic, indivisible, or partless, or as automatically composite and holonic.Keep the independently identified U.Transformation; infer neither presence nor absence of finer parts. Do not make a positive composition or A.1 claim without its independent construction basis.
Work-caused change as productionA change that follows U.Work is called a produced entity or completed production.First close the named work/transformation connection through 4.2.4 or keep its blocker; then separately test production-work participation, first existence of the subject, and the applicable production-completion criterion under A.15.PROD.

A.3.4:9 - Consequences

  • One bounded change can be identified at the needed resolution without settling its finer composition.
  • An independently grounded change of a selected configuration remains usable without asserting whether nearby changes compose it or are its parts.
  • A positive transformation-composition claim needs a governing rule and, for a local derived or compound claim, an admitted substrate. Return the missing basis identified in 4.2.1 when either is unavailable.
  • A.1 applies its six-part criterion after an independently admitted construction supplies the whole transformation and its construction facts.
  • Each subject pattern keeps its own change, U.Work, and production facts. A work/transformation connection uses the existing-predicate or local-compound branch in 4.2.4; otherwise preserve the applicable A.6.RCD stop for the named pair.
  • E.18 can arrange or locate transformation occurrences in a selected flow structure.
  • Ordinary result wording can express the relation needed by its use, while production, delivery and acceptance remain separately determined.

A.3.4:10 - Rationale

U.Transformation identifies one actual bounded change through the continuing subject, extent, boundary conditions, before/during/after facts, and continuity or reidentification rule. A description, planned operation or performed Work answers a different question and keeps its own identity.

An independently identified configuration transformation is not made into a whole with transformation parts merely because separately identified changes occur in the same episode or concern referents selected into that configuration. A positive composition claim needs its governing rule and, for a compound claim, admitted derivation semantics.

A.1 remains an independent test of the proposed whole and its construction facts. A whole or composite label and a trace supply no missing construction basis.

This separation also distinguishes change from production. A claim that U.Work caused or participated in a transformation needs the corresponding route in 4.2.4; even a positive work-to-change claim does not establish production. A post-boundary entity may be the same continuing entity rather than a newly constituted one. Production-work participation, first existence, production completion, delivery, acceptance, and downstream effect each need their own participants, relation, and criterion.

A.3.4:11 - SoTA-Echoing

Four source contributions address different questions about change.

Source and practice answerUse in A.3.4Contribution and limits
Marletto, Deutsch, and Vedral, “Tests of constructor theory”, 2026, arXiv edition 2606.07352v1, reviews the experimental-test branch of constructor theory in terms of possible and impossible tasks and constructors rather than ordinary program execution.A.3.4:4.1 and 4.7 require an independently grounded actual bounded change even when a constructor-theory task or formal transformation is used; case 5.4 keeps the proof term or morphism expression as representation.Use the task/constructor distinction to discipline possibility and governing conditions. A task, its description, a constructor label, or a formal expression does not establish the actual occurrence, project-world realization, evidence, or permission.
Deutsch and Marletto, “Constructor theory of time”, 2025, arXiv edition 2505.08692v3 revised in 2026, shows within that branch why duration and dynamics need an account distinct from task possibility.A.3.4:4.1 identifies the occurrence through its extent or formal ordering boundary and actual subject facts; 4.4-4.5 use C.27.TA for temporal aspects, C.27 for temporal-claim adequacy, and A.3.3 for dynamics; case 5.1 keeps the control-law episteme separate from the cooling-loop change.Preserve the separation among task, duration, dynamics, and actual occurrence without importing constructor theory as FPF temporal ontology. Duration, a dynamics model, or a task specification alone leaves actual occurrence identity unresolved.
Guizzardi, Benevides, Fonseca, Porello, Almeida, and Sales, “UFO: Unified Foundational Ontology”, 2022, develops the UFO account through distinct micro-theories that include events, situations, participation, causation, and change.A.3.4:4.1 and 4.3-4.5 keep actual-change identity, subject facts, participation or work-to-change facts, causation, assertion, and representation as separate questions; case 5.6 applies that split to a system in a flow.These distinctions help formulate separate participation, causation and change claims. Event mereology requires its own construction basis. Identify one U.Transformation at the resolution needed by the use; open participation, causation, work, or representation only through the pattern for that claim.
Borgo and Righetti, “Towards Applied Constructional Ontology”, 2025, argues that applied constructional ontology requires explicit choices about mereology, dependence, identity, and application concerns.A.3.4:4.2 and the PumpSkid case 5.7 independently identify the local changes, reject composition by timing or representation, and return the missing basis for a positive composition claim.Temporal inclusion, graph adjacency, a shared referent, a construction label, or a selected structure supplies neither transformation composition nor part identity.

A.3.4:12 - Relations

  • Builds on: A.1 for the independent holon criterion, A.6.RCD for the applicable relation-claim routes and stops, C.2.1 for blocker and assertion epistemes, and A.7 for category separation.
  • Coordinates with: A.3 when the use makes an acting-system claim; A.11 for parsimony; A.14 and C.13 for structural mereology without transformation-composition overread; A.22 for a selected changed structure; A.3.1, A.3.2, A.3.3, A.6.1, A.15.1, A.15.2, and A.15.PROD for method, dynamics, operation, work, and production questions; E.18, E.18.1, C.32.P2S, C.27.TA, C.27, C.29, A.10, B.3, G.11, and B.2; and the work-to-change, evidence, evaluation, gate, decision, source-use, production, delivery, acceptance, transfer, assurance, and publication patterns for those claims.

A.3.4:End

A.3.4.P - Transformation Wording Repair: Recover Objects and Claims

Type: A.3.4 precision-restoration child pattern Status: Stable Normativity: Normative unless a section is explicitly informative

Intent. Restore precision when wording about change hides the object or claim. Distinguish a bounded transformation and its changed referent from acting-System and influence claims, then identify the neighboring objects and their relations before rewriting.

Use this when. Use A.3.4.P when source or FPF-governed wording such as “pipeline”, “dataflow”, “flow”, “network”, “circuit”, “path”, “slice”, “workflow”, “process”, “operation”, “transformation”, or “change” seems to name the thing under concern, but the kind of object or claim meant by the passage remains unclear.

First useful move. State what the passage claims and about which subject. Recover the meaning of the ambiguous word and the conditions that change its use. Test an actual-change claim under A.3.4; open actor, influence and other neighboring questions only when the passage makes those claims. Then rewrite the affected wording, preserving its useful content. Keep a TransformationWordingRepair note only when the receiving use needs inspectable detail.

Not this pattern when.

  • If one bounded transformation is already identified and only its ordinary use continues, apply A.3.4 directly.
  • If the current claim is already a selected transformation-flow structure, use E.18.
  • If the current claim is a mathematical description, use E.18.2 and C.29.
  • If the current claim is only a semantic way of doing, method description, mechanism, work plan, dated work, evidence relation, publication relation, gate, decision, assurance, result, or temporal claim, use the subject pattern.
  • If the word is quoted source wording with no FPF-governed use, keep it quote-only.

A.3.4.P:1 - Problem frame

People talk about change with familiar labels—for example, a manufacturing process, refrigeration cycle, or team workflow. Recover the object and claim when that wording leaves an FPF-governed distinction unresolved.

The recurring defect is a second ontology by convenience. The same text may treat “process” as method, work occurrence, transformation-flow structure, mechanism, result evidence, and publication diagram. A graph path may become an action route. A network label may become a durable head beside TransformationFlowStructure. A function word may collapse functioning, mathematical function, software routine, module allocation, a system merely named as actor, and a differently typed influence source whose relation has not been recovered.

This pattern distinguishes the actual change, its description and any neighboring claims, then uses the subject pattern for each unresolved question.

A.3.4.P:2 - Problem

Without this repair:

  1. Source label becomes kind. “Pipeline”, “workflow”, “network”, “circuit”, or “process” is treated as the recovered FPF kind.
  2. Selected structure becomes one actual transformation. A flow, path, network, or circuit expression is treated as one actual U.Transformation or as proof of transformation composition without the changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis. Identifying one occurrence at the resolution needed by the current use establishes neither finer transformation parts nor partlessness.
  3. Method, mechanism, and work collapse. A method description, law-governed mechanism, work plan, dated work, or source diagram is selected by vocabulary rather than by current claim.
  4. Functional wording overreaches. A system, module, port, interface, signature, or function label is treated as the transformation or as proof of functioning.
  5. Mathematical expression becomes world-side ontology. A mathematical expression is treated as the project-world change.
  6. Description or evidence becomes transformation. A publication, dashboard, source span, proof, or evidence path is treated as the changed object or the change itself.

A.3.4.P:3 - Forces

ForceTension
Recognition and precisionSource labels help readers recognize a situation; an unresolved FPF claim needs its kind, participants, governing relation and applicable conditions recovered.
One actual transformation and selected flow structureU.Transformation identifies one independently grounded actual bounded change and establishes neither transformation parthood nor partlessness at the current resolution. TransformationFlowStructure positions, relates, or locates transformation loci and adjacent governed values; common structure membership establishes no transformation composition.
Acting System and influence sourceAn assignment occurrence alone does not prove performance, and generic transformation participation does not prove action. Any Work-to-change relation required by the claim remains separate. A non-Work actor needs its actor-side relation. Every influence source keeps its own kind and relation.
Formal and project-world changeA formal construction may be a transformation over a formal object, or it may be a mathematical description of project-world structure; the current object decides.
Repair and readabilityRecover enough ontology for the current use. Record a repair note only when the receiving use needs inspectable detail.

A.3.4.P:4 - Solution

Restore the change situation in this order.

  1. Name the working concern. State what the text is trying to do: identify a change, describe a flow, choose a method, claim evidence, compare architectures, describe functioning, or use a publication.
  2. Test an actual-change claim when one is made. Under A.3.4, identify the continuing changed subject, temporal extent or formal ordering boundary, boundary conditions, actual characteristic and relation facts, and continuity or reidentification rule. A plan, prediction or assertion alone leaves occurrence unresolved; its content can support occurrence facts when its evidence or derivation use warrants them.
  3. Separate an acting-System claim from influence when either is asserted. For dated Work, recover each performer’s A.13 core and independently admit the Work under A.15.1; add F.6 afterward only for attribution to that same assignment. Establish the Work-to-change relation required by the claim separately. A non-Work action needs the System and the participant, operation-application, functioning, causal or other actor-side relation defined by its subject pattern. An influence source keeps its own kind: for example, an organization, toolchain, selected structure or Method. Identify the architecture, Work, communication, constraint or other relation by which that source influences the subject; leave an unsupported claim unresolved.
  4. Recover the neighboring claims the passage needs. A way of doing, performed Work, a flow structure and evidence for a result require different objects and relations. Use the selection table in 4.2 for those questions.
  5. Use the governing relation for each neighboring value. A neighboring object keeps its own kind and governor; state its relation to the transformation, changed referent, work, architecture candidate, or receiving use instead of placing it inside a transformation record.
  6. Rewrite after kind and relation recovery. Keep ordinary domain wording when it conveys the recovered kind and relation unambiguously. Keep quoted source wording within its supported source use. Use F.19 to preserve the complete claim while removing unnecessary apparatus; an unresolved meaning leaves the dependent wording unresolved.
  7. Make the next use recoverable. The reader should be able to use the identified object or claim under its subject pattern, retain the bounded source use, or recognize the missing basis that limits the claim.

A.3.4.P:4.1 - TransformationWordingRepair note

Use this optional note when the receiving use needs an inspectable repair. Fill only the fields needed by that use; an ordinary wording repair can finish in the revised passage.

TransformationWordingRepair:
  EncounteredWording:
  WorkingConcern:
  RecoveredEntityOfConcern:
  ActualTransformationDisposition:
  TransformationOccurrenceBasis:
  ActingSystemDisposition:
  ArchitectureInfluenceDisposition:
  NeighboringClaimAndExactRelation:
  GoverningPattern:
  RetainedUse:
  StopOrReturnCondition:
  BlockedOverread?:
  RemainingReaderUse:

ActualTransformationDisposition is one of: actual bounded transformation recovered, not a transformation, not recovered, not current for this claim, quote-only source wording, or blocking missing value.

TransformationWordingRepair holds wording-repair information. RetainedUse identifies the use of the encountered wording that remains; RemainingReaderUse names the next action with the recovered object or claim. Include BlockedOverread? only for a mistaken interpretation with an independent local ground, a plausible intended reader and an effect on truth, understanding or use under F.19:4. The actor and influence fields describe the claims being examined; they introduce no kinds or relations.

Use the actor and influence tests in 4.4 only for the claims represented in those fields.

If an episteme asserts possible, intended, planned, modelled, predicted, or actual change, identify that episteme separately through C.2.1 when the passage concerns that assertion. Empirical grounding remains optional and, when used, has its own relation; neither the assertion nor its grounding relation substitutes for the actual transformation basis. Use the governing subject pattern’s requirements when creating a project record, gate decision, work plan, or work occurrence.

A.3.4.P:4.2 - Subject pattern selection

If recovery shows…Use this subject patternKeep this boundary
one actual bounded change under conditionsA.3.4A source label identifies no transformation until the changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis are recoverable.
selected structure over transformation loci and adjacent governed valuesE.18TransformationFlowStructure positions, relates, or locates those loci and values. Selection or common structure membership establishes neither an actual transformation occurrence nor transformation composition, parthood, or partlessness.
mathematical expression over a selected structure or formal objectE.18.2, C.29, A.6.0, or the direct formal patternRecover project-world work separately under A.15.1 when the current use also claims it.
semantic way of doingA.3.1Recover the semantic way of doing under A.3.1; identify dated work, mechanism, evidence, or transformation claims separately when current.
episteme describing a way of doingA.3.2For example, code, a protocol, a solver model, a proof script, a process model, or a diagram may describe a method.
law-governed operation algebra, laws, admissibility predicates, transport, audit, or mechanism-governing-definition assignmentA.6.1 and E.20Recover the mechanism’s defining content under A.6.1 and E.20.
planned or dated workA.15.2 or A.15.1Identify the plan or dated occurrence under its governing pattern; recover any Method, MethodDescription, transformation-flow structure, or evidence claim separately.
pattern-use recommendation, work-entry readiness, language-state move, architecture candidate use, or call-planning next actionThe applicable subject pattern; use E.10.MOVE when the move-like meaning remains unresolvedMove-like wording is not transformation wording unless the passage also concerns a bounded U.Transformation or a selected TransformationFlowStructure.
function-like wording inside a change situationA.3.4.P only to distinguish the actual transformation, selected TransformationFlowStructure, a System claimed to act under an actor-side relation, a differently typed influence source under its relation, boundary binding, or FunctioningRef?; use A.6.F for detailed function-kind discriminationFor an actual-transformation claim, recover its occurrence basis; for an actor claim, use the performed-Work or non-Work basis in 4.4.
state-space and transition-law epistemeA.3.3Dynamics can model possible or claimed change; recover any claimed actual occurrence independently under A.3.4.
a temporal aspect of an object or claimC.27.TA; use C.27 for temporal-claim adequacyC.27.TA supplies positive temporal subject matter; C.27 governs temporal-claim adequacy. Recover transformation identity under A.3.4 when that separate claim is current.
evidence, provenance, source, publication, dashboard, view, gate, decision, assurance, result, or release claimthe direct governing evidence, source, publication, gate, decision, assurance, result, or release patternRecover what the record or path states or represents, then apply the governing pattern’s conditions to the claim being made.

A.3.4.P:4.3 - Common source-label settlements

Source labelFirst recovery questionTypical admissible outcomes
pipeline or dataflowIs the current object one transformation, a compound transformation-flow structure, a method description, a work plan, or a publication diagram?A.3.4, E.18, A.3.2, A.15.2, C.2.P.DR, or quote-only source wording.
flowIs flow the selected structure, a mathematical expression, an actual material, energy, signal, or information flow, or an ordinary source label?E.18, E.18.2, C.29, direct subject pattern, or quote-only source wording.
network or circuitIs it a structure form, topology label, mathematical-expression family, functional structure, architecture-selected structure, or subject-domain system?E.18, E.18.2, C.29, C.30.ASV, A.6.F, or direct subject pattern.
path or sliceIs it graph path, PathSlice, evidence path, carrier path, mathematical path, source quote, or action-route metaphor?E.18, A.10, C.29, C.2.P.DR, carrier wording, source wording, or an explicit stop when the claim cannot be recovered.
workflow or processIs it method, method description, work plan, dated work, transformation-flow structure, mechanism, or source label?A.3.1, A.3.2, A.15.2, A.15.1, E.18, A.6.1 with E.20, or quote-only source wording.
algorithm, program, solver, or proofIs it method, method description, formal substrate, mathematical lens, mechanism, work occurrence, evidence, or proof publication?A.3.1, A.3.2, A.6.0, C.29, A.6.1 with E.20, A.15.1, A.10, C.2.1, or the governing publication pattern.
function, functional, or functioningDoes the passage claim an actual change, flow structure, action, influence or boundary relation, or does the function-like kind itself remain unresolved?Use the conditional tests in 4.4 for the claimed relations; use A.6.F for remaining function-kind discrimination.

A.3.4.P:4.4 - Functional change-situation settlement

When change-situation wording includes function, functional, functioning, transforms, or implements, use this pattern only to recover the claims being made:

  • Is one actual bounded U.Transformation established by changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification?
  • Is a selected TransformationFlowStructure at issue without being treated as the acting system or the change occurrence?
  • Is performed Work being attributed to a System? Recover each performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 only when assignment-bound attribution is being made, then state separately the realization, causal, production, or other Work-to-change relation required by the claim. An assignment occurrence, Work record, common timestamp, or generic transformation-participant fact does not prove performance.
  • Is a non-work functional or physical actor-side claim being made? Recover the system and the participant, operation-application, functioning, causal, or other actor-side relation supplied by its governor. If no actor-side governor is recoverable, leave the actor claim unresolved.
  • Is a distinct influence source claimed? Recover its kind and influence relation. An organization can be an admitted System, a selected structure remains a structure, and a Method or Method family is not made a holon by its label. Use the architecture, Work, communication, constraint or candidate-synthesis relation the claim needs. System membership and action require their own bases when those claims are made.
  • Does the passage concern participant, port, operation-application, relation-signature, or functioning relations at the boundary? Keep them under their governors; a transformation input or output requires its own relation.

After recovering the claim, apply A.6.F if the function-like kind or relation remains unresolved. Otherwise use the governing subject pattern directly.

A.3.4.P:4.5 - Description, publication, and evidence boundary

A diagram or report, for example, may describe a transformation, state a claim about it, provide evidence for that claim, or help compare transformations. When an actual transformation is claimed, recover its subject-side occurrence basis separately. For a description, assertion, or publication claim, use the episteme, publication, source, or declarative-representation pattern; C.2.1 empirical grounding remains an optional separate relation when the use requires it. For an actual-transformation claim, retain each description, assertion, publication, and evidence use as a neighboring claim.

A.3.4.P:5 - Archetypal Grounding

A.3.4.P:5.1 - Refrigerator functional diagram

Source wording says: “The refrigeration circuit moves heat through the cycle.”

Repair: recover whether the current claim is a refrigerator subsystem transformation, a TransformationFlowStructure over compressor, condenser, expansion, and evaporator transformations, a thermodynamic mechanism, a functional architecture view, or a schematic publication. The circuit label may stay as ordinary domain wording, but FPF use names the recovered object and the relation being asserted.

A.3.4.P:5.2 - Neural-network block

Source wording says: “The attention block transforms activations in the model pipeline.”

Repair: the block may be an architecture locus or module allocation. For a claimed action, apply the dated-Work or non-Work test in 4.4 and establish any Work-to-activation relation required by the use. A design organization, Method, toolchain or communication System that influenced the block keeps its own kind and influence relation. Activation and tensor-shape claims use their participant, port, operation-application or signature relations. An episteme describing an admitted attention Method may be a MethodDescription under A.3.2; C.29 governs a mathematical-representation use when one is made. The pipeline may be a transformation-flow structure. Use the applicable evidence or evaluation pattern when relying on a benchmark or ablation result.

A.3.4.P:5.3 - CRISPR editing workflow

Source wording says: “The guide-selection workflow changes the target gene.”

Repair: the target-gene edit is only a candidate U.Transformation until the biological referent, edit boundary, boundary conditions, actual sequence and direct-relation facts, and reidentification rule establish one occurrence. Guide selection may be method, method description, work plan, evidence-facing table, or performed lab work according to the current claim.

A.3.4.P:5.4 - Evidence path near a plant change

Source wording says: “The evidence path lets the valve-change flow proceed.”

Repair: identify the action meant by proceed and the condition the evidence is claimed to satisfy. Apply the governing rule to the available facts, and use A.22.CGUS if availability or ordering remains unclear. Preserve any established A.10 provenance relation for the named claim. Use A.3.4 only if an actual valve-change occurrence is also asserted.

A.3.4.P:5.5 - Filled minimal repair note

TransformationWordingRepair:
  EncounteredWording: "the refrigeration circuit moves heat through the cycle"
  WorkingConcern: recover whether the sentence is about one bounded heat-transfer change, a selected compound transformation-flow structure, a thermodynamic mechanism, a functional architecture view, or a schematic publication.
  RecoveredEntityOfConcern: `RefrigeratorHeatTransferFlowStructure-1`, the selected `TransformationFlowStructure` over the compressor, condenser, expansion, and evaporator transformation loci.
  ActualTransformationDisposition: no actual occurrence claim is made; the current object is the selected `RefrigeratorHeatTransferFlowStructure-1`.
  NeighboringClaimAndExactRelation: the four named loci are positions in `RefrigeratorHeatTransferFlowStructure-1`; bindings to actual transformation occurrences have not been established.
  GoverningPattern: `E.18` governs `RefrigeratorHeatTransferFlowStructure-1`; use `A.3.4` when a claim about an actual component occurrence needs its basis established.
  RetainedUse: "circuit" may remain ordinary domain wording for `RefrigeratorHeatTransferFlowStructure-1`; the source's heat-transfer claim remains unresolved.
  StopOrReturnCondition: use the selected structure for the recovered structural question; if the receiving use needs the heat-transfer claim, recover its participants and relation under the relevant subject rules. A later actual-occurrence claim still needs the A.3.4 occurrence basis.
  RemainingReaderUse: use `E.18` for `RefrigeratorHeatTransferFlowStructure-1`; open the applicable subject pattern when an additional claim is needed.

One rewrite for the recovered structural use is: “RefrigeratorHeatTransferFlowStructure-1 has four positions: compressor, condenser, expansion and evaporator. The relation asserted by ‘moves heat through the cycle’ remains to be recovered.”

A.3.4.P:6 - Bias-Annotation

Familiar domain words can bias kind selection before the claim being made is recovered. The refrigeration and attention examples show why the same label may describe a structure, mechanism or action. Start from the sentence’s participants and predicate, and retain an already adequate ordinary domain expression.

A.3.4.P:7 - Conformance Checklist

CheckConformance statement
CC-A34P-1The repair names the encountered wording and the working concern before selecting a replacement.
CC-A34P-2If one actual bounded transformation is current, the repair names or blocks its changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis.
CC-A34P-3Each neighboring object keeps its own kind; connect it to the transformation, changed referent, work, architecture candidate, or receiving use only by the relation recovered for this claim.
CC-A34P-4TransformationFlowStructure, graph mathematical description, path mathematical description, and subject-domain network or circuit wording are kept distinct. The selected structure positions, relates, or locates transformation loci and adjacent governed values; composition, parthood, and partlessness require their direct predicates.
CC-A34P-5Method, method description, mechanism, work plan, dated work, evidence, gate, decision, assurance, result, source, and publication claims remain with their subject patterns.
CC-A34P-6Function-like wording distinguishes the actual-change, action, influence and boundary claims that it makes; detailed function-kind discrimination remains governed by A.6.F.
CC-A34P-7The repaired wording preserves its needed use and makes any material stop or subject-pattern return recoverable. An optional warning meets the F.19:4 plausible-reader test.
CC-A34P-8F.19 handles ordinary precise-plain-language rewriting. For unresolved change-situation wording, E.10 supplies recognition cues, A.3.4.P restores the transformation ontic neighborhood, and neighboring patterns define or constrain recovered objects and relations.
CC-A34P-9For a performed-Work actor claim, recover each performer’s A.13 core and independently admit the Work under A.15.1; add F.6 afterward only when assignment-bound attribution is being made and separately name the Work-to-change relation required by the use. A non-Work actor claim names another actor-side relation.
CC-A34P-10Possible, intended, planned, modelled or predicted change remains the corresponding claim content. An assertion or its empirical grounding supports only what its evidence or derivation warrants; an actual-occurrence claim requires the A.3.4 basis.

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

Anti-patternSymptomRepair
Cue word as ontology“Pipeline”, “process”, “network”, or “circuit” is treated as the FPF kind.Recover the current object: U.Transformation, TransformationFlowStructure, mathematical description, method, work, publication, or direct subject pattern.
Replacement by smoother umbrella“Process” is replaced with “flow” or “operation” without recovered kind.Run the replacement through the same recovery. If the kind is still hidden, leave it unresolved.
Network head inflationFrequent network or circuit wording becomes a peer durable head.Use network or circuit as structure form, topology label, mathematical-expression family, domain label, or subject-domain system only when recovered by value.
Selected structure as transformation compositionCommon membership in one flow, path, network, circuit, or pipeline is treated as a composite transformation, transformation-part relation, or proof of indivisibility.Use E.18 only to position, relate, or locate transformation loci and adjacent governed values. Ground every actual U.Transformation independently under A.3.4; common structure membership establishes neither composition, parthood, nor partlessness.
Workflow as performed workA workflow diagram or process model is treated as dated work.Use C.2.P.DR to recover the diagram’s supported description or representation use; apply A.3.2 or E.18 only for the corresponding MethodDescription or selected-structure claim, and establish any claimed dated Work independently under A.15.1.
Function as proof of behaviorA module, port, participant, assignment occurrence, or “transformer” label is treated as proof of actual change or action.For an actual-change claim, recover its transformation basis. For an actor claim, use the performed-Work or non-Work test in 4.4, including any Work-to-change relation that the claim needs.
Architecture influence as actionA manufacturing or certification organization, design organization, Method or Method family, toolchain, communication System, selected structure, or other value is called the actor because it constrained or enabled a candidate.Recover the value’s kind first, then only its architecture, Work, communication, constraint, or candidate-synthesis relation. For an actor claim, apply the separate performed-Work or non-Work test in 4.4.
Publication as changeA diagram, proof, dashboard, or source span is treated as the changed object or change occurrence.Recover the cited object’s kind and use under its subject pattern; use A.3.4 for any claimed actual change.

A.3.4.P:9 - Consequences

  • The reader can keep a recognizable domain expression while making its object and relation unambiguous.
  • A.3.4 establishes the basis needed by an actual-change claim; other subject patterns answer the separate claims.
  • The ordinary result is the repaired wording and the needed stop or subject-pattern return; use a TransformationWordingRepair note only when the receiving use needs recoverable detail.

A.3.4.P:10 - Rationale

Words such as process and circuit are useful across several disciplines, but they can conceal different subjects and predicates. Recovering those differences lets the reader choose the appropriate occurrence test or construction without replacing every familiar word with a formal label.

A change description can concern an actual occurrence, an acting System, an influence source, a selected structure or a representation. Each has its own conditions. The conditional sequence therefore starts from the claim being made and restores only the distinctions needed to interpret and use it.

A.3.4.P:11 - SoTA-Echoing

A.3.4 supplies the actual-change criterion and its comparison with theories of change. E.18 distinguishes selected transformation-flow structure from occurrence, and C.29 supplies representation correspondence. This pattern connects ambiguous change-situation wording to those different tests. E.10 supplies recognition cues; F.19 governs the connected reading and rewrite. The function, method, Work and publication patterns supply the remaining subject distinctions when those claims are made.

A.3.4.P:12 - Relations

  • Builds on: A.3.4, E.10, E.10.ARCH, E.24, A.6.5, E.8, and F.19.
  • Coordinates with: E.18 for a selected structure that positions, relates, or locates transformation loci and adjacent governed values without establishing transformation composition, parthood, or partlessness; and with E.18.2, C.29, A.3.1, A.3.2, A.3.3, A.6.0, A.6.1, E.20, A.15.2, A.15.1, A.6.F, A.6.M, C.30.ASV, C.27.TA, C.27, A.10, C.2.P.DR, C.2.1, E.17, and direct gate, decision, assurance, result, source, publication, and release patterns when those claims are current.
  • Coordinates with: E.10.MOVE when source wording about a move, next action, pattern-use recommendation, work-entry readiness, language-state transition, architecture candidate use, or call-planning next action is not transformation wording.
  • Selected by: E.10 recognition row for change-situation wording when FPF wording repair needs transformation-ontic precision restoration.
  • Specializes: A.3.4 for wording-use precision restoration around situations of change.

A.3.4.P:End

A.4 - Compare a System’s Intended Design with Its Operating Conditions

Status: Stable

A.4:1 - Problem frame

Use this when a decision depends on whether an independently identified System’s operation matches a selected design account, and that comparison is unresolved. The account may state an intended operating condition, required result or predicted behavior. Select the account edition and its operative comparison criterion before diagnosing a discrepancy or choosing a change.

The first useful result is a fit, a discrepancy or the missing/incomparable basis. An engineer can obtain that answer without starting an adaptation loop or changing the System or its design.

Not this pattern when. Reuse a sufficient direct domain comparison. Use A.1.1 for an unresolved model-applicability question, C.2.1 for episteme identity and edition relations, A.3.4 for an actual change claim, and B.4 when repeated adaptation itself needs coordination. An unchanged theorem being cited is an episteme-use question, not a System design/operation comparison.

A.4:2 - Problem

FailurePractical consequence
A design account is treated as the actual System.Editing the account appears to improve a System whose operation has not changed.
An operating result is compared with an unspecified target or under different conditions.A reported pass or failure cannot guide the receiving decision.
A discrepancy automatically triggers design revision.A still-applicable target may be weakened merely to make the discrepancy disappear.
Measurement, its record and target change are conflated.A new observation is mistaken for a changed subject or a new System.

A.4:3 - Forces

ForceTension
Stable subject, changing accountsCompare the continuing System with the selected account without deriving System identity from document versions.
Intended result and actual factsPreserve a normative target while learning what is happening; a descriptive prediction can raise a different revision question.
Comparable evidence and effortObtain the facts needed by the criterion while reusing an adequate comparison or observation.
Diagnosis and authorityDiscover a discrepancy without presuming which participant may change the subject, account or receiving use.

A.4:4 - Solution - One Bounded Comparison

  1. Select the subject, account and use. Identify the System, the design account edition and the decision this comparison must inform. Keep the System’s identity under its own rule and the account’s identity under C.2.1. Choose the relevant account claim rather than treating the entire design as one test.

  2. Recover the operative criterion. State the target or expected behavior, relevant conditions, any units and tolerances required by the comparison, and the rule for comparing the account claim with actual facts. Identify what force the account claim has:

    Account claimWhat the comparison can establish
    Normative target, such as a required minimum flowWhether the actual operation meets that target under the rule. A miss does not by itself make the target inapplicable.
    Descriptive predictionAgreement or discrepancy between predicted and actual behavior under the prediction’s conditions. Model revision remains a separate decision.
    Applicability conditionWhether the named condition is met. Use A.1.1 when the question is the model’s applicability to this subject/use; do not substitute target conformance for that judgment.
  3. Obtain or reuse comparable facts. Recover the actual operating conditions and results required by the criterion. Check their temporal reference, units, tolerance, relevant configuration and measurement uncertainty when it affects the selected decision rule. If the design and observation concern different conditions, use an already justified translation only within its limits. Otherwise name the missing basis. Use C.27 when temporal adequacy is itself unresolved.

  4. Perform the comparison and return its boundary. State what meets the criterion, the discrepancy, or the missing or incomparable premise. Qualify the result to the named System, account claim, conditions and use. When a rule withholds acceptance because the evidence is too uncertain, distinguish that outcome from an established physical failure. A partial comparison can leave other requirements unexamined.

  5. Separate any response decision. Keeping the present use, qualifying reliance, changing the System and revising the account are different possible next decisions. Use their own authority and subject methods when needed; B.4 coordinates repeated adaptation. Do not replace the selected target with an easier one and report that as improved conformance. Stop at the comparison when it answers the working question.

A.4:4.1 - Observation, change and continuity

An observation may involve dated measurement Work. Recover that Work under A.13 and A.15.1 only when the receiving claim needs the occurrence; identify the result and its relied-on evidence under their own patterns. A new record does not establish a target change. A.3.4 governs any actual before/during/after change claim, and A.12 distinguishes actual acting and changed participants when internal action is asserted.

Changed account claim content identifies a different C.2.1 episteme. An obtaining edition relation is a further claim with its own conditions, including any actual branching. Neither an account edit nor overlapping operation and design work decides the System’s continuity. Practices may define design and operating regimes where useful.

A.4:5 - Archetypal Grounding

A.4:5.1 - One continuing pump, two selected design accounts

In this constructed case, Pump37 operates under condition set C. A justified domain comparison uses exact flow values in L/min under those matched conditions. The available observation is 105. Account D1 requires at least 100; account D2 requires at least 110.

Selected basisComparisonBounded result
D1, C, minimum 100 L/min105 ≥ 100This flow requirement is met.
D2, C, minimum 110 L/min105 < 110Flow misses this requirement by 5 L/min.
D2 under C, observation under C′, with no justified translationThe comparison premise is missing.Unresolved comparison, not a failed pump or a false design.

Selecting D2 changes the comparison basis; it does not physically change Pump37. Editing D1 into D2 changes the account’s claim content. Its historical edition relation, if claimed, must independently obtain. The discrepancy against D2 may justify a later response question, but supplies neither change authority nor a requirement to revise the design.

A.4:5.2 - Distinguish the actual event and its next use

Working situationCorrect exit
A pump circulates coolant while its CAD account is edited.Use the continuing pump and the selected CAD account claim in the comparison. Operating Work and editing Work concern different subjects; the edit establishes no physical pump change.
An author cites an unchanged theorem.Use the direct episteme-use rule for the citation; the cited theorem remains unchanged.
An unused pump weathers.A.3.4 can qualify the actual material change without invented Work. If later design conformance matters, compare the resulting condition with the selected criterion.
A sensor measurement produces a new observation record.Use the observation as warranted input to the comparison. Measurement and result do not by themselves establish target change.
A pump’s internal control System performs maintenance.A.12 distinguishes acting and changed participants. The System’s identity rule can preserve the same pump; compare its relevant resulting facts if the intended use requires it.

A.4:6 - Conformance Checklist

IDRequirementPurpose
CC-A.4.1Identify the System, selected account edition, account claim and receiving use.Fix the comparison’s subject and basis.
CC-A.4.2Distinguish normative target, descriptive prediction and applicability condition; recover the comparison rule.Prevent a failed target test from silently becoming an applicability or revision decision.
CC-A.4.3Use comparable actual facts with the required conditions, temporal reference, units and tolerances, or state the missing premise.Give fit and discrepancy their warranted scope.
CC-A.4.4Return the bounded comparison before any separately selected adaptation.Preserve a useful answer without compulsory change.
CC-A.4.5Keep account identity/edition, actual Work, target change, System continuity and response authority under their direct rules.Allow overlapping activity and branching accounts.

A.4:7 - Consequences

The practitioner can distinguish a changed System, changed knowledge of its operation and a changed design criterion. A discrepancy becomes actionable because it names the unmet condition or missing comparison basis. Reusing adequate facts and stopping at a sufficient answer keeps a simple comparison small.

The comparison costs the recovery of its account, criterion and relevant actual facts. It cannot supply missing domain law, resolve every uncertainty or decide who may alter a target. When repeated adaptation is warranted, B.4 consumes the result with the independently selected response and continuity rules.

A.4:8 - Rationale

The difference between intended design and actual operation is a relation between an account claim and facts about its subject. A pump may operate while engineers edit its description; an observation may change knowledge while the pump remains unchanged.

Selecting the criterion first makes the distinction useful. The same observed flow can meet one requirement and miss another, and unmatched conditions can leave both conclusions unsupported. Keeping the response separate preserves an applicable target and permits a justified decision to retain the current arrangement, qualify its use or investigate further.

Repeated adaptation remains available through B.4 when the work needs it. Apply the subject-specific continuity rule and the account’s actual edition relations.

A.4:9 - SoTA-Echoing

Practice question. How can an operating observation answer a design question while preserving the selected requirement, comparable conditions and a separate decision about what to change?

First identify what the comparison is meant to establish, then apply an explicit decision rule. The distinction in the NASA Systems Engineering Handbook, Rev. 2, NASA/SP-2016-6105, §2.4 is useful here: compliance with specified requirements and suitability for intended use in the intended environment answer different questions. This supports §4 steps 1–3: a passed flow requirement is not by itself proof of operational suitability. NASA’s wider life-cycle process is outside this bounded method; its source role here is the separation of comparison purposes.

For a quantitative requirement near a measurement limit, the competing answers are simple acceptance and guarded acceptance. JCGM 106:2012, §§8.2–8.3 supplies both: simple acceptance compares the measured value directly with the tolerance; guarded acceptance narrows the acceptance region to reduce false acceptance. The former is a suitable choice when the parties accept its risk and the measurement uncertainty is adequate for their purpose. The latter can cost more false rejections. Neither changes the specified tolerance itself.

Apply that comparison in §4 steps 2–4: retain the applicable rule and its uncertainty basis instead of silently treating every point estimate as decisive. Where the receiving use requires protection against false acceptance, guarded acceptance is the better answer at comparable effort when the uncertainty estimate is already available. Where that extra protection is unnecessary, reuse a sufficient simple comparison. Avoid automatically tightening the rule or weakening the requirement merely because the result is inconvenient.

The exact-value pump comparison in §5.1 needs no extra uncertainty calculation. In a separate constructed variant, the available estimate is 105 L/min, its justified coverage interval is 97–113 L/min, and the minimum requirement remains 100 L/min. Simple acceptance accepts the point value. A selected rule requiring the entire interval to satisfy the minimum withholds acceptance because 97 < 100. Both use the same observation; the second result does not establish that the pump delivers less than 100. This is why step 4 distinguishes an evidential limit from an established discrepancy, and step 5 leaves any response to its own authority.

Reopen the chosen rule if the uncertainty or condition-translation basis changes, or the receiving use changes the tolerated decision risk. If the selected account instead contains a descriptive prediction, return to step 2 and recover its prediction-comparison rule; a conformity-assessment source does not authorize recalibrating the prediction or revising a requirement.

A.4:End

A.5 - Open-Ended FPF Kernel and Extension Layering

Normativity: Informative. A.6.0 U.Signature and A.6.1 U.Mechanism govern declaration boundaries; E.5.3 constrains dependency direction and E.10 governs terminology.

Status: Stable

A.5:1 - Problem frame

Use this when adding or revising domain knowledge raises a question about what belongs in the shared Kernel, which assumptions belong in an extension, or which uses depend on a changed declaration.

First useful move. Name the contribution, its applicability and the declarations it relies on. Reuse an adequate existing contribution. For a new domain-specific assumption, keep its applicability with the extension rather than making every Kernel use depend on it.

FPF combines shared conceptual grounds with domain Methods by keeping the common commitments stable enough for reuse while allowing extensions to supply different assumptions and laws. Competing explanations can remain available under their respective conditions.

Different domains can require different assumptions and laws. Making a domain-specific assumption an unconditional Kernel commitment would impose it on uses where it may not hold and make those uses depend on its revision. Place domain-specific knowledge in extensions by default, with its applicability stated. Use A.8 to test a U-kind’s cross-domain contribution and A.11 to test whether a new ontological value is needed. The declaration rules in A.5:4 expose dependencies so that a changed declaration can be followed to the uses that rely on it.

A.5:2 - Problem

Admitting domain-specific primitives without their applicability boundaries can create two problems:

ProblemPractical effect
Kernel bloatUnnecessary root U-kinds or local type vocabularies can increase users’ learning effort and maintainers’ support work.
Conflicting assumptionsIncompatible axioms presented as unconditional commitments leave the reader unable to select an applicable explanation.

A.5:3 - Forces

ForceTension
Stability vs. EvolvabilityStable common commitments support reuse ↔ changed domain needs can require new or revised contributions.
Universality vs. SpecificitySingle kernel language ↔ disciplinary idioms.
Parsimony vs. CoverageFewer shared primitives can reduce learning and maintenance work ↔ domain uses need their applicable distinctions and laws.

A.5:4 - Solution

FPF pattern texts publish law-governed declarations—vocabulary, laws and applicability—that can be reused and specialized.

To keep the Kernel open‑ended, use the following boundary rules:

  1. Kernel minimality (C‑5). Domain knowledge stays outside the Kernel by default; it enters as extension vocabularies and laws.
  2. Boundary packaging via U.Signature (A.6.0). For reusable declaration bundles admitted as signatures under A.6.0, expose declaration dependencies in a SignatureManifest (imports, provides).
  3. Dependency vs specialisation are separate relations. imports forms a dependency DAG constrained by E.5.3; refinement/extension (⊑, ⊑⁺) is expressed separately (for mechanism declarations, see A.6.1:4.8; use C.29 when a mathematical morphism is claimed) and should not be conflated with imports.
  4. Registry references stay references. Registry identifiers, such as Bridge ids, policy‑ids and edition‑ids in Part F, are cited or pinned where needed, not treated as exported symbols in provides.

For example, an extension describes a cooling Method under specified fluid and operating-range assumptions. Keep those assumptions and its heat-transfer law with the extension. If its declaration bundle is admitted as a U.Signature, its manifest identifies the scale declaration it imports and the declarations it provides. A changed scale declaration directs attention to the cooling claims that depend on it. A changed fluid assumption instead requires reconsidering uses that rely on that applicability condition; it does not make the assumption a Kernel law. This connects a local revision to its affected uses while preserving unrelated contributions.

A.5:End