A.15:4 - Solution
Recover the values first, then state only the relations needed by the receiving use. A.15 aligns system-role kind, assignment, Method, MethodDescription, capability, WorkPlan, Work, and separate records; it does not create a universal process object or a universal assignment signature.
When wording about changing, producing, selecting, deriving, controlling or maintaining leaves its object unresolved, use E.10.ARCH. A workflow graph, process calculus, matrix, category, embedding or neural representation may describe or serve as a lens over a Method relation structure; its representation form alone establishes no Method, assignment, WorkPlan or Work occurrence.
A.15:4.1 - Core entities kept distinct
- Local system-role kind. A value such as
InspectorSystemRole : U.Kindis admitted under A.2 with C.3 through itsU.Systemcandidate domain, operative work-facing membership condition, member/non-member boundary, and continuity rule. It is not a system, assignment, relation slot, capability, Method, Work, responsibility, or authority. A system classification judgment and an assignment occurrence are separate claims. U.SystemRoleAssignment. This is the relation family consumed by A.15 and F.6. It has no permissive rootRelationSignature. Each direct species declaresHolderSystemSlot : U.System, a declaration-localAssignedSystemRoleKindSlotwhose ValueKind is one local system-role-kind domain, its predicate and applicability, every additional participant, and its occurrence-identity rule.U.Method. The run-independent semantic way of doing. A Work occurrence can stand inenactsMethod(W, M); the Method does not act.U.MethodDescription. An already identifiedU.EpistemewhoseEntityOfConcernis an admitted Method and whose substantive claims say how that Method is done, as judged by A.3.2. Wording, file form, or publication alone establishes no membership.- Holder capability (A.2.2). The holder’s ability to perform named work under stated conditions and bounds. Its assertion, evidence, currentness assessment and fit to a demand remain separate. Ability establishes neither assignment nor performed Work.
U.WorkPlan. AU.Epistemeabout possible future Work, including intended windows, dependencies, performers, and budgets. It does not bring a future Work occurrence into existence.U.Work. The admitted kind for concrete dated Work occurrences. One Work individual has its own temporal extent, at least one obtaining A.15.1enactsMethodrelation, and at least one obtaining locally declared containing-system relation. It may stand in further enactment, affected-referent, binding, resource-use, production, and result relations when the receiving use needs those independently obtaining facts. Any log, ticket, assertion, description, or performed-work record is a separate episteme.
Work occurrence and record boundary. Recover the affected-referent, transformation, speech-act effect, commitment effect, production, delivery, acceptance, or other relation under its direct pattern. Labels such as operational, communicative and epistemic can remain recognition cues; they do not define Work subkinds by enumeration.
Didactic note for managers: the chef analogy. ChefSystemRole is one local system-role kind. A kitchen-assignment species defines the holder and assigned-kind positions and adds shift, station, or commission only when it changes the assignment. A particular assignment fills those positions with the chef System, the kind, and any additional value. A cookbook can be a MethodDescription; the chef’s skill can be a capability; a WorkPlan can schedule cooking; and making one souffle on Tuesday is dated Work. Its temporal and resource-use relations can state the 25-minute extent, eggs, butter, and consumed gas, while a kitchen log remains a separate episteme. A restaurant vocabulary or scheme can help interpret the claims without becoming a participant in every assignment. The cookbook, skill, plan, assignment, and log do not cook.
A.15:4.2 - Canonical relations
graph TD
subgraph "Direct system-role assignment species"
H["holder H : U.System"] -- "HolderSystemSlot" --> RA["RA : InspectionShiftAssignment<br/><: U.SystemRoleAssignment"]
K["InspectorSystemRole<br/>local kind"] -- "AssignedSystemRoleKindSlot" --> RA
end
subgraph "Method, description, and capability"
M["M : U.Method"]
D["D : U.Episteme<br/>A.3.2 membership: U.MethodDescription<br/>EntityOfConcern = M"]
Cap["Qualified ability claim about H"]
Fit["capability-fit condition"] -- "tests" --> Cap
end
W["W : U.Work"] -- "performedUnderAssignment<br/>holder equality check: RA.Holder = H" --> RA
W -- "enactsMethod" --> M
style K fill:#fff2cc,stroke:#d6b656,stroke-width:2px
style Cap fill:#d5e8d4,stroke:#82b366,stroke-width:2px
style Fit fill:#d5e8d4,stroke:#82b366,stroke-width:2px,stroke-dasharray: 4 4
style M fill:#d5e8d4,stroke:#82b366,stroke-width:2px
style D fill:#f8cecc,stroke:#b85450,stroke-width:2px
style H fill:#e1d5e7,stroke:#9673a6,stroke-width:2px
style RA fill:#dae8fc,stroke:#6c8ebf,stroke-width:3px,stroke-dasharray: 5 5
style W fill:#ffe6cc,stroke:#d79b00,stroke-width:2px,font-weight:bold
The diagram shows a simple direct assignment species. A stronger appointment can declare an additional participant such as a review commission; that specialized occurrence itself is the U.SystemRoleAssignment. Do not create a weaker generic occurrence beside it. The displayed F.6 edge is included because this example claims precise assignment-bound attribution; a Work claim that does not need that attribution omits it.
- Capability fit. A MethodDescription, WorkPlan, or work-admission assertion may require a holder capability threshold. The fit condition compares the holder’s qualified ability claim with the receiving work conditions and bounds and may cite declared measures,
U.Characteristicvalues, Q-Bundle slots, or architecture-characteristic criteria. It is neither an assignment participant nor a second capability kind. - MethodDescription membership.
Dis aU.MethodDescriptiononly when A.3.2 recovers MethodMas its EntityOfConcern and at least one substantive way-of-doing claim. “D describes M” is shorthand for that constitution and membership result, not another binary relation. enactsMethod(W : U.Work, M : U.Method). This relation states which Method the dated Work enacts. A.15.1 defines its participant order, predicate, occurrence identity, and multiplicity. It neither attributes a performer nor turns a description into the Method.performedUnderAssignment(W : U.Work, RA : U.SystemRoleAssignment). F.6 defines this relation. For a precise actual performer,RAis the same obtaining assignment used by A.13 for the action, scope, working situation, and window. It must be an occurrence of a declared assignment species, have the A.13-qualified System as holder, and cover the Work while the species predicate obtains. The assignment is the attribution ground, not the actor. A record may state the relation without constituting it. Read an existingperformedBy(W, RA)claim only through the F.6 compatibility boundary after resolving the holder System; do not author new claims with that spelling.
One assignment occurrence continues through the maximal uninterrupted interval in which its direct species predicate obtains for fixed participants. A declared interval, taxonomy, scheme, KindSignature, assertion, evidence item, or selected model-use structure can describe or interpret the claim but does not create the occurrence or become a generic participant.
For a precise performed occurrence, first recover the A.13 core for the actual performer System and action, then admit W : U.Work under A.15.1 from its independent occurrence, Method, extent, and containment facts. Only afterward trace W to the same RA through F.6 performedUnderAssignment when the receiving use needs precise assignment-bound attribution, and compare RA.HolderSystemSlot with the already recovered performer; F.6 identifies neither. Trace W to M separately through enactsMethod. Cite a characteristic profile only when conditionally consumed; cite a MethodDescription, plan, capability claim, evidence item, taxonomy, or scheme separately only when the receiving use relies on it. The performer System acts; the kind, assignment, capability, Method, description, plan, evidence, and record do not.
A.15:4.3 - Bounded specialization scouting and CheckpointReturn
For a human-plus-AI pair planning tool calls or probing a route, recover only the Systems, assignments, Methods, plans and Work needed by the alignment claim, with their applicable admission grounds. The pair may use four local system-role kinds for this bounded work: OutcomeCriterionHolderSystemRole, AIScoutSystemRole, AISpecialistProbeSystemRole, and CommitAuthoritySystemRole. Claim an assignment only by naming its occurrence and declared species under U.SystemRoleAssignment. The CommitAuthoritySystemRole name does not supply decision authority; any authority relation must obtain independently.
First distinguish the current question. If another probe could change which option survives the OptionSet, return to C.11. If changed live facts or domain-Method limits could change the next action during ongoing Work, return to A.15.7. Use C.24 when an applicable domain prescription or a completed decision has fixed the action or option and tool or service calls must be planned.
Use a sufficient existing CallPlan directly. Otherwise use C.24 to construct the fixed action’s route from available inputs, qualified Method contributions and required intermediate results, then check its feasibility. Select a bounded scout or probe only for a specific unresolved fact that could change the usable route and when the attainable answer justifies the inquiry under the applicable criterion, budget and permission. After actual probing, return what was tested and observed in a CheckpointReturn. Use A.15 for the assignment, Method, plan and Work claims this use needs, and C.24 for planning and checkpoint semantics. When an E.16 autonomy budget governs the scouting, retain its scout budget, probe budget, commit checkpoint and guard or override path.
After a bounded probe, its CheckpointReturn carries the C.24 action basis and:
- the objective or
TaskFamilyand the applicable outcome criterion; - the Methods tested, with approach descriptions when needed;
- the evidence observed for those tests and important failure signals, including progress toward any work-measure threshold used by the decision;
- burned and residual budget;
- the recommended next action, such as a further bounded probe, adoption of an identified
CallPlan, a narrower supported claim, return to the applicable pattern or domain prescription, or stop; and - the commit trigger for considering whether to end the probe and adopt an identified
CallPlan.
The return is evidence about the tested approaches, observed results, budget and proposed continuation. It is not the selected Method, U.WorkPlan or actual Work. Use the trigger, probe evidence, residual budget and any required safety or assurance result to decide whether to adopt the identified plan, probe further or stop. Plan adoption, permission to perform calls and actual Work remain separate. Recover the execution-evidence, provenance or rollout-decision claims consumed by that decision or later rollout under their applicable rules.
A.15:4.4 - Boundary to A.15.4 Work-Relevant Appearance-Based Reliance Repair
Use A.15.4 when an encountered episteme, carrier, display, credential view, generated explanation, copied statement, provenance mark, dashboard tile, schema wording, API wording, or source-relation chain is being relied on by appearance for Work, assignment currentness, assignment state, source currentness, approval, authorization, gate passage, evidence, engineering justification, release, or another reliance-bearing claim.
A.15 itself keeps the local system-role kind, holder system, direct assignment occurrence, Method, MethodDescription, WorkPlan, dated Work occurrence, and every separate episteme distinct. A.15.4 recovers the project-side value and relation that must hold before the visible item can warrant the attempted use.
A principle scheme, functional diagram, scenario, screen, or explanation that exposes an E.18.1 P2W carry-through structure may help a team plan Work or find a source. It does not become the selected Method, plan, Work occurrence, result, evidence, or authority by publication.
A.15:4.4a - Inspecting Method–Work Alignment Across an Unfolding Structure
Do not create a linkage record merely because one unfolding structure mentions several Method- and Work-related values. Keep each direct relation under the pattern that defines it. When a receiving use must preserve an inspectable explanation across those relations, write one bounded C.2.1 episteme whose EntityOfConcern is the selected unfolding U.Structure. Its ClaimGraph may cite, as separate claims, the selected Method and Method-relation structure, MethodDescription epistemes, relevant local system-role kinds and assignment occurrences, the Work that enacts the Method, Work-part relations, independently identified transformations and their direct Work-to-change claims, intended WorkPlans, readiness results, capability-fit conditions, evidence, assurance, and gate decisions. Include only claims needed by that receiving use.
Call this episteme a Method–Work alignment account in ordinary prose. Its identity comes from its EntityOfConcern, ClaimGraph, and effective ReferenceScheme, not from a field bundle. Each claim in the account remains defined or tested by its own pattern: A.3.1 for Method, A.3.2 for MethodDescription, A.15.2 for planning, A.15.5 for readiness, A.15.1 for dated Work and Work relations, B.3 for assurance, A.20 for internal-constraint results, and A.21 for gate decisions. Assess evidence under the rule for the claim it bears on; use A.10 when a replayable source-to-use account is needed. If the useful account would need several unrelated entities of concern, split it instead of using one umbrella record.
Another structure, such as CGUS, P2W, P2S, an improvement-loop slice or a transformation-flow slice, may cite the episteme when its receiving use needs the alignment explanation. Recover the cited claims under their source, identity and applicability conditions; reuse an established result while those grounds remain valid.
A.15:4.5 - Boundary to A.15.5 Work-Entry Readiness
Use A.15.5 when the current question is whether intended Work is ready to enter its boundary. A.15 keeps system-role kind, assignment, Method, plan, and Work distinct; A.15.5 carries WorkEntryReadiness@Context, FullKitCondition, commitment disposition, resource-readiness references, WIP or flow-policy references, planned baselines, and launch-gate references when those values are current.
Readiness is not performed Work, evidence sufficiency, or gate passage. A briefing, dashboard, source bundle, or P2W record may cue A.15.5. Ground the result in the WorkPlan being judged, the PlanItem content the criterion consumes, that criterion and the facts used to evaluate it. State the readiness result, its qualification window, and the applicable stop or degraded-use condition. Identify missing or unknown required inputs; include performed preparation Work or a planned baseline only when the criterion or receiving use consumes it. Address the PlanItem content through that WorkPlan; it is not another readiness target.