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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:55:20 UTC

A.22.CGUS - Which Continuations Are Available? — Constraint-Governed Unfolding Structure (CGUS)

Type: A.22 specialization of U.Structure Status: Stable Normativity: Normative unless marked informative

A.22.CGUS:0 - Use This When

Use this pattern when a diagram or explanation shows several possible next actions, but readers may mistake one displayed path for the required work sequence. Start with one ordinary question:

Which alternatives are available now, and what condition blocks each one?

Name the decision or question, the visible alternatives, the condition for each alternative, and the facts available now. If a missing fact or rule could change the answer, mark that alternative unknown. An established blocking condition may already settle it as unavailable. Stop when this answers the practical question. A useful explanation need not first become a formal record or an admitted structure.

Open the formal branch when a named use needs the identity and qualification of the unfolding organization as a CGUS. A ConstraintGovernedUnfoldingStructure (CGUS) is one A.22 U.Structure whose locally named loci, constituents, obtaining relations, and constraints define at least two potential continuations across the cases allowed by those constraints. A separate result says which alternatives are enabled, disabled, unknown, or error for one case and time window.

Do not use CGUS merely because a card, graph, table, narrative, prompt path, or README line looks route-shaped. A single recommendation or displayed sequence is not enough. The structure may branch, join, cycle through subject relations, remain partially ordered, or leave several alternatives live at once. A result with zero or one enabled alternative can still concern that same branching structure.

What changes in practice. Practitioners correct the visible alternatives and their conditions before completing formal fields. They keep potential structure separate from the result for the present case, and they mark an alternative unknown when an unresolved fact or rule prevents deciding it. Display order alone neither prescribes nor performs Work.

A.22.CGUS:1 - Problem Frame

FPF often needs to explain how several identified things and relations constrain what may follow without turning that explanation into a workflow. The shared object is one A.22 structure. CGUS adds local loci and a membership test for potential branching; a continuation judgement then evaluates one case.

Descriptions, publication forms, evidence, assurance, authorization, work plans, performed Work, architecture claims, and mathematical models can be used alongside that structure. They remain separate objects and claims under the patterns that define or test them.

A.22.CGUS:2 - Problem

A route-shaped explanation can hide the relations and constraints that make an alternative available. Readers then follow the displayed order as if it were a required procedure, or they treat a condition label as proof that the condition is true now.

The opposite repair is also harmful: authors replace the simple decision question with a large admission, replay, publication, and assurance package. The formal package becomes harder to use than the misleading card it was meant to correct.

A.22.CGUS:3 - Forces

ForceTension
Useful explanation vs workflow overreadA visible path helps a reader, but Work may be nonlinear, interrupted, iterative, or arranged by another Method or plan.
Potential structure vs present resultThe structure can retain several possible branches while the present case enables none, one, or several.
Plain entry vs formal replayAn ordinary correction should be cheap; qualification and replay still need enough identity and relation detail to be checked later.
Description vs described structureA card, graph, table, or narrative can describe a structure without creating it.
Reuse vs copied mini-patternsCGUS needs exits to relation, transformation-flow, work, publication, and assurance patterns without copying their architectures.

A.22.CGUS:4 - Solution

A.22.CGUS:4.1 - Ordinary branch

Write the smallest useful answer in domain language:

  1. name the decision or question;
  2. list the alternatives;
  3. state the condition for each alternative;
  4. state the facts known for this case;
  5. mark each alternative available, blocked, or unknown under its condition, and name any gap that prevents deciding it. If the evaluation itself failed, state that error rather than treating it as a domain fact.

For example, a design review has two alternatives: accept the design or repair it. Acceptance needs both checks to pass. Repair needs at least one failed check and a repair proposal that concerns this design.

AlternativePresent factsResult shown on the card
Accept the designThermal check failed; service check passed.blocked — thermal check failed
Repair the designA check failed and a repair proposal exists, but the proposal-to-design relation has not been established.unknown — proposal target not established

That corrected card is already useful. It keeps both potential alternatives visible and refuses to invent the missing relation. Retain the rules, facts, and result when the ordinary answer must be reconsidered or compared later. Continue into formal qualification only when a named use depends on the organization’s CGUS identity or membership.

When retaining or handing over this card separately, include the two rules above or a usable return to them so the recipient can reconsider availability after the facts change.

A.22.CGUS:4.1.1 - Conditions through constituent and encompassing work

When a continuation is a way of performing work, recover the constituent–whole relations in the relevant Method and Work structures that can change availability. Ask what constituent actions must be performable and what encompassing work is being done through them. B.1.5.EW supplies that recovery; knowing a Method’s description does not supply the capability or resources to perform it.

Distinguish conditions needed at entry, conditions that must remain satisfied during combined performance, and the result required by the encompassing use. In particular:

  • a constituent may be individually performable but fail in the needed coordination;
  • adequate local resources may be insufficient when constituents share them;
  • a constituent result may satisfy its own postcondition while leaving the whole’s result unresolved.

For each relevant condition, state what it concerns and how it affects this continuation. Reuse an understood connection or adequate existing basis. A missing condition blocks or leaves unknown the dependent alternative; it need not block an independent way to learn, obtain support or change the arrangement. Capability belongs to its performer and conditions under A.2.2; prospective resources and support remain prospective until available.

In the formal branch, express these dependencies with the existing constituents, selected relations, applied constraints and continuation judgements. A temporal edge alone cannot express that one action constitutes part of another ongoing work. Nor does a nested flow position establish Method or Work parthood. A diagram may show the relations together when their meanings remain recoverable.

A constituent’s postcondition supports the encompassing conclusion only through the relevant composition and result-use conditions. An expected postcondition is not an observed result. If the displayed account omits conditions needed to perform the whole, state the narrower question it answers. A constituent hierarchy without potential alternatives does not require CGUS qualification.

A.22.CGUS:4.2 - Formal qualification branch

Use the four A.22 discriminators to identify one U.Structure:

  • its constituent references;
  • the obtaining relation occurrences it selects;
  • the applied constraint claims;
  • the named selection-use frame: the question, admissible action, and stop or return condition. Any optional explanatory overread follows F.19:4 and remains outside the identity basis.

CGUS membership adds locally declared loci and bindings that expose how those constituents matter to the unfolding question. The selected relations and constraints must define at least two potential continuation candidates across allowed cases. The current continuation result, a description, or a publication field adds no structure-identity discriminator.

selectedCGUSRef: one A.22 U.Structure
A22IdentityBasis:
  selectedConstituentRefs[]
  selectedObtainingRelationOccurrenceRefs[]
  appliedConstraintClaimRefs[]
  namedSelectionUseFrame:
    questionOrAction: selection question
    admissibleAction
    stopOrReturnCondition
forbiddenOverread?: optional explanation outside A22IdentityBasis
constraintGovernedProfileBasis:
  locusBindingRows[]:
    locusRef: <selectedCGUSRef, locusId>
    locusMeaning: why this constituent matters to this question
    selectedConstituentRef
  potentialContinuationRows[2..*]:
    continuationCandidateRef
    constrainingRelationOccurrenceRefs[]
    appliedConstraintClaimRefs[]

forbiddenOverread? and groundedForbiddenOverread? name the same optional explanation. Use F.19:4’s plausible-reader test to decide whether it is useful here.

A CGUS locus belongs to this structure, not to a reusable relation declaration:

CGUSLocusRef := <selectedCGUSRef, locusId>
CGUSLocusBinding := <selectedCGUSRef, locusId, locusMeaning, selectedConstituentRef>

The constituent must already belong to the A.22 identity basis. A locus binding neither changes that constituent’s kind nor creates a relation. Do not use an A.6.5 SlotSpec as a free-standing structure position.

When replay must identify one participant in a relation occurrence, retain the relation definition, the occurrence, the participant order, and the participant binding:

RelationParticipantLocator := <relationDefinitionRef, relationOccurrenceRef, participantOrder, participantRef, relationSignatureRef?, slotSpecRef?>

Add a RelationSignature and its declaration-local SlotSpec together only when an existing reusable declaration is needed for replay. Neither declaration value substitutes for the obtaining occurrence. The CGUS has no ambient context field.

Judge each continuation separately. An immediate local use may keep the following values in the explanation; persistence or replay may place them in an ordinary C.2.1 result episteme.

ContinuationJudgementResult:
  selectedCGUSRef
  continuationCandidateRef
  basisRows[]:
    basisKind: conditionEvaluation | obtainingRelation
    conditionEvaluation?:
      conditionPredicateOrTestRef
      applicabilityResult
      caseInputRefs[]
      currentFactOrEvidenceRefs[]
      requiredPolarity
      observedOutcome: satisfied | notSatisfied | unknown | error
    obtainingRelation?:
      relationDefinitionRef
      relationOccurrenceRef
      participantRefsInPredicateOrder[]
      currentFactOrEvidenceRefs[]
    dependentSelectedRelationOccurrenceRefs[]
  qualificationWindow
  result: enabled | disabled | unknown | error
  reason

CurrentContinuationSetResult:
  selectedCGUSRef
  caseInputRefs[]
  qualificationWindow
  judgementResultRefs[]
  enabledContinuationCandidateRefs[]
  disabledContinuationCandidateRefs[]
  unknownContinuationCandidateRefs[]
  errorContinuationCandidateRefs[]
  stopOrNextAction
  recheckConditions[]

A claim reference identifies the claim being applied; it does not show that the test applies or that its condition is satisfied. An obtaining relation is not a condition claim. Keep these two basis branches distinct and derive the case result only from completed judgements. Apply the candidate’s condition logic: for example, one false required conjunct can establish disabled despite another unknown conjunct. Retain that unknown basis value; it is not thereby satisfied. An evaluation failure yields error under the applicable test, not an invented fact about the candidate.

The membership test concerns potential topology. Changed facts, evidence, test outcomes, or time windows normally change a judgement and the current set, not the structure. Reidentify the A.22 structure when a constituent, selected obtaining relation occurrence, applied constraint, or named use frame changes. Reapply CGUS membership when a locus binding or potential-continuation row changes.

A.22.CGUS:4.3 - Four separate decisions

DecisionPassing basisLower result
A.22 identity and CGUS membershipThe four A.22 discriminators identify one structure; its local loci, relations, and constraints define at least two potential continuations across allowed cases.Name the missing discriminator, binding, relation, constraint, or candidate. Keep the artifact as an explanation.
Continuation result for this caseEach candidate retains its condition-evaluation and obtaining-relation basis rows as applicable. A condition-evaluation row keeps the test, applicability, inputs, required polarity, and observed outcome; an obtaining-relation row keeps the definition, occurrence, and ordered participants. Keep the relevant facts or evidence, time window, and an enabled, disabled, unknown, or error result.Mark the affected candidate unknown when the gap prevents deciding its condition; retain an independently established disabled result. Do not revoke an independently established structure.
Description or demonstrative-slice adequacyThe description says what it shows and omits for its declared use. Use C.33 only when a carrier’s loss affects a declared architecture use within C.33’s scope.Narrow or correct the description. Missing publication or loss material does not deny the structure.
A stronger neighboring claimThe method, Work, evidence, assurance, gate, architecture, publication, currentness, or mathematical claim passes its own definition or test.Stop only that stronger use and name its missing rule or basis.

Potential branches and joins remain part of the structure even when the present case enables one or none. A linear teaching slice neither removes the other topology nor fixes the order of performed Work.

A.22.CGUS:4.4 - Explanations, descriptions, and the non-workflow boundary

An ordinary explanation keeps the subject designated by its claims. When its episteme identity matters, recover that independently identified EntityOfConcern under C.2.1. It may already be an A.22 structure whose CGUS membership is unresolved. An assertion of CGUS membership still requires its qualification basis.

After qualification, a whole-structure description may describe loci, bindings, relations, constraints, potential branches, case results, and relevant omissions. A separate demonstrative slice may show one traversal for a declared teaching or comparison use. That slice is a C.2.1 episteme: its claim content, the qualified CGUS as EntityOfConcern, and its effective reference scheme jointly recover its identity. DemonstrativeUnfoldingSlice@Context is readable lineage for this possibility, not a U.Kind or a slice by itself. The slice neither creates nor reidentifies the structure. Use C.33 only when hidden or lost structure in its carrier matters to a declared architecture use within C.33’s scope.

Where a slice shows one selected pattern use, it may recall the difficulty through the pattern’s Problem frame or Problem, or recall the way of addressing it through the Solution. To show that same use in either form, preserve the selected pattern, working subject and question or proposed use, current conditions, expected result, stop or continuation, and relevant locus bindings. Changing between those formulations changes only the description when the selected pattern use and the qualified structure remain the same. A.22 structure identity still depends on its constituents, selected obtaining relations, applied constraints and named selection-use frame; CGUS membership additionally depends on its locus bindings and at least two potential continuations. Question or action labels establish neither.

Displayed words such as move, next, and path remain ordinary language unless a stronger claim requires another kind. A proposed action, a plan item, a U.WorkPlan, dated U.Work, and an actual U.Transformation are different values. Use E.10.MOVE, A.15, and A.3 only when that distinction changes the claim; a display performs and authorizes nothing.

For a transformation-flow use, apply E.18.3. It owns the choice among one TFS, one parent-relative SubflowRef, or an E.18.NET network and the corresponding position and demonstration locators. CGUS keeps only its local locus bindings and potential topology; it does not copy the network’s members, positions, valuations, Work, transformations, or tags.

Cite another pattern only when its content supplies a needed definition, constraint, test, method, evidence rule, or assurance rule. For example, use C.30 for an architecture claim and C.32 for architecture-candidate synthesis, E.23 for repeated quality improvement under a declared evaluation, G.11 for source currentness, C.29 for a mathematical-lens claim, A.10 when the source-to-use account is implicit or must remain replayable, or B.3 for a named assurance claim.

If a durable name or a relation between local senses is the question, use F.17, F.18, or F.9 after the value has been recovered. Do not copy their naming or Bridge procedures into this pattern. Entry cards and publication faces remain under E.11 and E.17.

A.22.CGUS:4.5 - Replay and change localization

Replay structure identity from the four A.22 discriminators. Replay CGUS membership from the local locus bindings and potential topology. Replay the case result from each candidate’s basis rows, retaining the values required by each applicable condition-evaluation or obtaining-relation branch in 4.2, the relevant case inputs and facts or evidence, dependent occurrences, time window, continuation result, and reason.

Localize change before reopening wider work. A changed constituent, selected occurrence, constraint, or use frame can reidentify the A.22 structure. A changed locus binding or potential-continuation row reopens CGUS membership. A changed fact, evidence item, test result, or time window normally reopens only the affected judgement and current set. A changed omission reopens the affected description use. A changed neighboring claim stays with the pattern that defines or tests it.

A.22.CGUS:5 - Complete Worked Case

Return to the design review from 4.1. The team now needs to determine whether reviews across editions use the same qualified unfolding structure or a different one. Recover the formal basis below for that comparison.

selectedCGUSRef: DesignReviewAlternatives@DR-27
A22IdentityBasis:
  selectedConstituentRefs[]:
    DesignCandidate-A
    RepairProposal-A
    AcceptCandidate-Continuation
    RepairCandidate-Continuation
  selectedObtainingRelationOccurrenceRefs[]:
    RepairProposalTargetsCandidate@DR-27
  relationOccurrenceRecoveryRows[]:
    - relationOccurrenceRef: RepairProposalTargetsCandidate@DR-27
      predicateDefinitionRef: RepairProposalTargetsDesignCandidatePredicate
      participantRefsInPredicateOrder[]: [RepairProposal-A, DesignCandidate-A]
  appliedConstraintClaimRefs[]:
    AcceptIfBothChecksSatisfied
    RepairIfAnyCheckViolatedAndProposalTargetsCandidate
  namedSelectionUseFrame:
    questionOrAction: which review continuations satisfy the two-check rule for DesignCandidate-A?
    admissibleAction: show enabled, disabled, unknown or error results for the current case
    stopOrReturnCondition: recheck a case when its result inputs or window change; reidentify the structure when its selected basis changes
forbiddenOverread?: displayed order as performed Work, or an available branch as authorization
constraintGovernedProfileBasis:
  locusBindingRows[]:
    - <DesignReviewAlternatives@DR-27, candidate, design under review, DesignCandidate-A>
    - <DesignReviewAlternatives@DR-27, repair-proposal, proposed repair, RepairProposal-A>
    - <DesignReviewAlternatives@DR-27, accept, accept continuation, AcceptCandidate-Continuation>
    - <DesignReviewAlternatives@DR-27, repair, repair continuation, RepairCandidate-Continuation>
  potentialContinuationRows[]:
    - AcceptCandidate-Continuation, constrained by AcceptIfBothChecksSatisfied
    - RepairCandidate-Continuation, constrained by RepairIfAnyCheckViolatedAndProposalTargetsCandidate
caseBasis:
  checkResultRefs: [ThermalCheckResult-A, ServiceCheckResult-A]
  resultAboutCandidateOccurrences:
    - <ThermalCheckAboutCandidate@DR-27, CheckResultAboutDesignCandidatePredicate, [ThermalCheckResult-A, DesignCandidate-A]>
    - <ServiceCheckAboutCandidate@DR-27, CheckResultAboutDesignCandidatePredicate, [ServiceCheckResult-A, DesignCandidate-A]>
continuationJudgements[]:
  - candidate: AcceptCandidate-Continuation
    basisKind: conditionEvaluation
    predicateOrTest: AcceptIfBothChecksSatisfied
    applicability: both named results concern DesignCandidate-A
    caseInputs: [ThermalCheckResult-A, ServiceCheckResult-A]
    currentFacts: [thermal violated, service satisfied]
    requiredPolarity: both satisfied
    observedOutcome: notSatisfied
    dependentOccurrences: [ThermalCheckAboutCandidate@DR-27, ServiceCheckAboutCandidate@DR-27]
    window: ReviewWindow-DR-27
    result: disabled
    reason: thermal check is violated
  - candidate: RepairCandidate-Continuation
    basisKind: conditionEvaluation
    predicateOrTest: RepairIfAnyCheckViolatedAndProposalTargetsCandidate
    applicability: the proposal concerns DesignCandidate-A
    caseInputs: [ThermalCheckResult-A, ServiceCheckResult-A, RepairProposal-A]
    currentFacts: [thermal violated, service satisfied, RepairProposalTargetsCandidate@DR-27 obtains]
    requiredPolarity: at least one violation and the targeting relation obtains
    observedOutcome: satisfied
    dependentOccurrences: [ThermalCheckAboutCandidate@DR-27, ServiceCheckAboutCandidate@DR-27, RepairProposalTargetsCandidate@DR-27]
    window: ReviewWindow-DR-27
    result: enabled
    reason: one check is violated and the repair proposal concerns this design
currentContinuationSet: enabled [RepairCandidate-Continuation]; disabled [AcceptCandidate-Continuation]; unknown []; error []
stopOrNextAction: show repair as available; recheck when the case results or window change

The structure has two potential continuations although this case enables only repair. The selected proposal-to-design relation belongs to its identity basis. Thermal and service result epistemes, and their about-candidate relations, belong to the current case basis; they are not constituents or selected relation occurrences of this structure.

If the proposal-to-design relation cannot be established, this formal structure claim remains provisional. The ordinary explanation can still report repair as unknown. Do not treat an unknown identity-bearing relation as an established constituent of a qualified CGUS.

A later passing thermal check is a different result episteme and supplies a new case input. With service still satisfied, acceptance becomes enabled and repair becomes disabled. The selected design, proposal, continuation candidates, proposal-to-design relation, constraints, use frame, loci and potential topology are unchanged, so the same CGUS remains available for that new case.

A.22.CGUS:5.1 - A missing intermediate capability changes the continuation

In this constructed learning case, a dancer has the strength and static axis control needed by a figure and can recall its sequence. The known limitation is maintaining balance during its required rotation. The figure’s continuation depends on that coordinated performance, not just on adequate strength and memory.

AlternativeRelevant conditions in this casePresent result
Perform the complete figure under its intended conditions.The required balance during rotation cannot yet be sustained.Unavailable for the intended performance; naming the figure or its steps does not remove the gap.
Practise the rotational coordination under a suitable reduced demand.A domain-appropriate exercise, suitable space and the needed support are available in the stipulated case.Available as practice of the intermediate performance. It does not establish ability to perform the full figure.

During the rotation, balance coordination would constitute part of turning; that turn would constitute part of the figure. These are connections through performance, not three successive tasks. The practice alternative can exercise the first connection without already performing the intended figure.

When the coordination can be sustained, return to the encompassing figure and vary the relevant conditions before drawing a broader capability conclusion. The case condition and its continuation judgement can change without changing the potential alternatives. The subject’s training Method supplies the exercise and assessment; CGUS makes their effect on the available continuation explicit.

A.22.CGUS:6 - Bias-Annotation

Bias riskMitigation
Workflow biasAsk about alternatives and conditions; use work and method patterns only for work-order or way-of-doing claims.
Display biasTreat cards, graphs, tables, narratives, and entry lines as explanations or descriptions, not as the structure.
Formality biasStart with the ordinary decision answer and open formal qualification only for a named later use.
Consumer biasKeep transformation-flow, architecture, improvement, currentness, evidence, and publication details in their patterns.
Lexical biasWords such as route, path, loop, workflow, graph, or sequence establish no CGUS by themselves.

A.22.CGUS:7 - Conformance Checklist

IDPassing conditionFailed-check repair
CC-CGUS-1 Identity and profile.The four A.22 discriminators identify one U.Structure; local locus bindings, relations, and constraints define at least two potential continuations across allowed cases.Recover the missing value or keep the artifact as an explanation.
CC-CGUS-2 Local loci and relation participants.Every CGUSLocusBinding uses a locus declared inside this CGUS and binds one constituent for a stated meaning. A needed relation participant retains its definition, occurrence, order, and binding; RelationSignature and SlotSpec appear together only for declaration-level replay.Restore the locus or complete relation-participant basis. Never use a free-standing SlotSpec as a structure position.
CC-CGUS-3 Explanation and description separation.An ordinary or persisted provisional explanation concerns the subject of its claims; this may be an already identified A.22 structure whose CGUS membership remains unresolved. Post-qualification descriptions and slices concern the CGUS. None is the structure or a membership condition.Restore the right EntityOfConcern or keep the explanation ordinary.
CC-CGUS-4 Current continuation result.Each judgement retains its basis rows with the values required by each applicable condition-evaluation or obtaining-relation branch in 4.2, the relevant case inputs and facts or evidence, dependent occurrences, window, continuation result, and reason. The enabled set may contain zero, one, or several alternatives.Apply the candidate’s condition logic; mark it unknown only when the missing value prevents deciding the result, and retain evaluation errors separately.
CC-CGUS-5 Separate decisions.Identity and membership, case result, description adequacy, and each neighboring claim are judged separately.Reopen only the affected decision.
CC-CGUS-6 Work-order boundary.The selected structure and display expose branches and conditions.Put any prescribed or performed Work order under the Method, work-plan, or Work pattern that establishes it.
CC-CGUS-7 Graph-shaped coverage.Branches, joins, cycles, partial order, and live alternatives are preserved or explicitly omitted for the declared use.Keep a chain provisional or state what its demonstrative slice omits.

A.22.CGUS:8 - Common Anti-Patterns And Repairs

Anti-patternSymptomRepair
Pretty route as ontologyA card or graph is treated as the structure.Keep it as an explanation; qualify the structure independently.
Condition label as resultA label or claim reference is treated as proof that a continuation is enabled.Apply the test or recover the obtaining relation and facts. Mark the continuation unknown when the missing basis prevents deciding it.
One enabled branch as one-branch structureThe present result erases other potential continuations.Keep potential topology and the case result separate.
Formal package or field count firstA simple correction requires replay fields, or authors add references merely to raise schema completion.Use the ordinary branch and stop when it answers the question. In formal use, retain only fields consumed by qualification or replay and test whether readers recover the right alternatives and smallest repair.
Displayed order as WorkA teaching slice becomes a project procedure or authorization.Use the applicable Method, work-plan, or Work pattern for work order, A.21 for a gate decision, and the permission or authority rule for authorization, only when that claim is made.
Consumer architecture copied inwardCGUS repeats transformation-flow locators, naming procedures, or catalogs of neighboring claims.Keep the local structural rule and exit to the pattern that defines or tests the other claim.

A.22.CGUS:9 - Consequences

CGUS preserves the usefulness of a route-shaped explanation without making it a workflow. Ordinary use is cheap: decision, alternatives, conditions, facts, result, and stop. Formal use costs more because structure identity, CGUS membership, the case result, and any description or neighboring claim must remain separately checkable.

This separation prevents a changed fact from reidentifying a stable structure and prevents a missing publication, evidence, or assurance value from erasing a useful ordinary answer.

A.22.CGUS:10 - Rationale

The recurring object is a thin specialization of A.22 U.Structure, not a new root kind. The cited constraint-based, object-centric, artifact-centric and acausal approaches provide different ways to express relations and constraints beyond one displayed execution path. CGUS uses this design question while retaining its own A.22 identity and continuation tests.

The same distinction appears in acausal engineering models: component relations and constraints can be stated before an analysis chooses a calculation direction. FPF adopts only that general separation. Mathematical models, analyses, executions, results, and publications keep their own kinds and rules.

A.22.CGUS:11 - SoTA-Echoing

Source or practice anchorFPF adoptionBoundary
Aaron Küsters and Wil M.P. van der Aalst, “OCPQ: Object-Centric Process Querying & Constraints”, 2025Comparison for queries and constraint checks over typed objects and events, including linked instances and their qualified relationships in the cited 2025 work.A query or result is not the CGUS.
JuliaHub, Dyad Components and Reuse and Analyses documentationEngineering comparison for reusable equation-based component models and connections, separately defined analyses, and their solution objects.FPF imports neither Dyad ontology nor its tools. Modelica 3.7 is retained only as historical acausal-modeling lineage.
Declare/MP-Declare, DCR, artifact-centric/GSM, and CMMN workLineage for declarative constraints, live alternatives, stages, guards, and weakly structured case work.These are not current authority for a universal FPF process calculus; their notation and workflow ontology are not imported.
FPF pattern-language practiceOrdinary explanations may precede qualification; descriptions and demonstrative slices may follow it.Publication form alone supplies neither CGUS qualification grounds nor specification force.

A.22.CGUS:12 - Relations

Specializes: one A.22 U.Structure whose local locus bindings, obtaining relations, and constraints define at least two potential continuations across allowed cases. Continuation judgements, descriptions, slices, loss notes, and neighboring claims are separate results or uses.

Specialized by: E.18.3 when the same structure also satisfies its transformation-flow condition. Local applications include architecture, abduction, improvement, narrative, grounding, currentness, and first-entry uses only when their own constituents, relations, constraints, and use frames are recoverable.

Coordinates with: A.6.P and A.6.5 for relation occurrence and reusable declaration precision; E.18, E.18.NET, and E.18.3 for transformation-flow substrates; A.3 and A.15 for Method, plan, Work, and Transformation claims; A.10 for claim-bound evidence reliance, B.3 for a named assurance claim, A.20 for internal-constraint validity, and A.21 for gate decisions; C.30 for architecture claims and C.32 for architecture-candidate synthesis; E.23 for repeated quality improvement under a declared evaluation; G.11 for currentness; C.29 for mathematical-lens use; C.33 for description loss that affects a declared architecture use; E.11 for entry, E.17 for a source-backed reader face, and E.24.PUB for publication occurrence, form, carrier, audience, bounded use, and availability; and F.17, F.18, and F.9 for source-local sense, durable naming, and Bridge claims.

Does not replace any pattern that supplies the definition, constraint, test, method, evidence rule, or assurance rule for a neighboring claim.

Use F.19 for ordinary precise-plain-language repair and the plausible-reader test for an optional explanatory overread.

A.22.CGUS:End

Referenced in the corpus

144 literal mentions in other sections. Read their context to establish the relation.