A.22.CGUS:4 - Solution
A.22.CGUS:4.1 - Ordinary branch
Write the smallest useful answer in domain language:
- name the decision or question;
- list the alternatives;
- state the condition for each alternative;
- state the facts known for this case;
- mark each alternative
available,blocked, orunknownunder 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.
| Alternative | Present facts | Result shown on the card |
|---|---|---|
| Accept the design | Thermal check failed; service check passed. | blocked — thermal check failed |
| Repair the design | A 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
| Decision | Passing basis | Lower result |
|---|---|---|
| A.22 identity and CGUS membership | The 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 case | Each 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 adequacy | The 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 claim | The 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.