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 22:00:10 UTC

A.15.2 - U.WorkPlan: Plan Content for Coordinating Future Work

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

At a glance. Use U.WorkPlan when a system needs one plan to coordinate possible future performed Work for an already existing subject over a stated horizon. One PlanItem names the intended Method, window, performer System or local system-role-kind condition, and only the resource, dependency, commitment, target, or baseline needed now. The plan states what is intended; A.15.1 identifies actual Work separately.

Use this when. Coordinate possible future Work through a schedule, rota, ticket or other plan content. Identify the existing subject, intended performances, horizon and reference scheme, then state enough constraints to make the current coordination decision. Use §4.3 when schedule or workflow wording leaves the claim unclear.

First useful object. One WorkPlan about a present subject, interpreted under one reference scheme, with a horizon and one usable PlanItem. Later fulfilment or variance checking is a separate use.

Ordinary path.

  1. Identify the already existing subject whose future work is being coordinated, the horizon, and one PlanItem.
  2. In that item name the possible future performance, target Method, planned window, and the intended performer System or local system-role-kind condition needed now.
  3. Add only the resource, dependency, commitment, target, or baseline needed for the current coordination decision.

Filled ordinary example. A plan about existing Lathe-7, interpreted under FabMaintenanceScheme-E2, can set horizon 2026-07-27, item inspect-spindle, method SpindleInspectionMethod-E2, window 08:00–09:00, intended performer System MaintenanceTech-4 with local kind MaintenanceTechnicianSystemRole, a one-hour machine reservation, dependency lockout complete, and baseline normal vibration. The team can coordinate the rota and reservation for that day from this content and stop before selecting a later fulfilment or variance comparison. If lockout will not be complete by 08:00, the planners defer that item or revise its window and reservation.

Detailed authoring and later comparison. Use §4.1–4.4 to settle plan identity, item content and organization. Open §4.5 only when a receiving question asks whether an independently identified Work occurrence fulfilled or deviated from a plan item. Choose the smallest A.6.RCD result that this comparison needs.

Stop condition. Stop once a system can coordinate the intended work at the needed granularity. Assess any separate claim introduced at step 3 under its governing pattern, while retaining a WorkPlan whose intended-work content meets §4.1. If no pattern states the predicate needed for a later fulfilment, variance, or occurrence-facing relation, stop only that stronger use; the plan and any local comparison whose predicate and supporting facts can be stated remain usable.

What goes wrong if missed. Intended work can be mistaken for completed performance, and later changes to the plan can erase the baseline needed for comparison.

What this buys. The team can coordinate intended Work now and, when needed, compare actual performance with the identified plan under an explicit policy.

Not this pattern when. Use the direct pattern when the current claim is a dated performed work occurrence (A.15.1), A.15.3 declaration-local planned-filling content, work-entry readiness or full-kit condition (A.15.5), a reliance appearance being used before the governing pattern or relation is recovered (A.15.4), a method (A.3.1), a method description (A.3.2), evidence or assurance (A.10 or B.3), an internal constraint result (A.20) or gate decision (A.21), publication-use behavior (E.17, with E.24.PUB for publication identity), a non-agentive forecast or dynamics model (A.3.3), or a declarative representation overread as a work-control or method claim (C.2.P.DR).

A.15.2:1 - Context (plain‑language motivation)

Before and during Work. Before Work begins, keep intended-work content in this WorkPlan. Use A.15.5 when the question is whether that Work is ready to start, and use C.11 only when a known chooser must compare an already formed OptionSet. Do not invent current Work for A.15.7. During Work, an A.15.7 answer remains separate from the plan. Revise the WorkPlan only when the intended-work content changes, and identify any later performed action under A.15.1 rather than back-filling the plan.

Intended operations are coordinated in time. A system uses a WorkPlan to decide when and by whom possible future work is intended, under what constraints and budgets. Distinguish this scheduling content from:

  • the semantic “way of doing” (that is U.Method),
  • the claims about how an admitted Method is done (that is U.MethodDescription),
  • the performed work occurrence (an individual admitted under U.Work), or
  • the state-change model (that is U.Dynamics).

U.WorkPlan identifies that intended-work episteme.

A.15.2:2 - Problem

  1. “Workflow = schedule” conflation. A way-of-doing description is used to answer a scheduling question while time, performer or resource constraints remain unstated.
  2. Plan and occurrence blur. Gantt bars or Kanban tickets are reported as if the work already happened; audits and costing degrade.
  3. Specification and time leakage. A reusable MethodDescription embeds one staffing or calendar choice without distinguishing it from the Method’s required conditions.
  4. Missing comparison basis. Without the planned baseline and applicable comparison rule, a later time, cost or quality difference cannot be classified as plan variance.
  5. Structure entanglement. Equipment or organization structure is copied into a plan without stating which structural relation constrains the intended Work.

A.15.2:3 - Forces (what the definition balances)

ForceTension we resolve
Universality vs. domain idiomsOne plan concept that fits hospitals, fabs, data centers, and research labs—while honoring local terms.
Commitment vs. flexibilityPlans need enough firmness to coordinate, while remaining easy to update as reality changes.
Intended performer vs. performed-work assigneePlans may name intended performers; the assignment used for performed work is still checked for the work interval.
Budgets vs. performed resource usePlans state targets and reservations; A.15.1 and the resource-use or ledger pattern govern performed resource-use facts.
Decomposition vs. fulfilmentPlan tasks decompose conveniently; they do not force a shape on performed Work occurrences.

A.15.2:4 - Solution - U.WorkPlan as the time-bound intention for U.Work

A.15.2:4.1 - Definition, membership, and identity

U.WorkPlan is a same-individual dependent kind under U.Episteme. C.2.1 first identifies episteme P by:

<ClaimGraph, one already identified present EntityOfConcern, effective ReferenceScheme>

A.15.2 recognizes that same P as U.WorkPlan when its ClaimGraph substantively declares coordination of work intended as future from the planning perspective recorded in P, over one horizon through at least one PlanItem and, when it contains several items, their plan-content organization. The intended-performance designator may denote one proposed future performance, a named repeated-work family, or one bounded proposed group. It remains claim content: planning it neither asserts the existence of a dated Work occurrence nor makes a merely possible performance into C.2.1’s already identified EntityOfConcern. The unchanged P retains its original intended-coordination claims after performance, cancellation or passage of that horizon. Those claims provide the baseline for a later fulfilment or variance comparison. A revised intention changes the claim content; a later report of actual performance has its own claims.

The present EntityOfConcern is the already identified existing entity that the plan’s claims are about: for example, a system, asset, or promise-content episteme for which work is being coordinated. When the plan claims are expressly about their own coordination commitments, C.2.1’s reflexive option permits P itself. The ClaimGraph may also designate other independently governed entities as participants. When the asserted subject is a joint entity, identify that entity independently. Split the ClaimGraph only when it combines independent subjects in a way that makes the selected EntityOfConcern untruthful or breaks the intended identity or comparison use; do not split merely because one predicate connects several participants.

The stable positive membership condition is substantive intended-work content. At least one PlanItem must name its intended-performance designator, intended method or method family, planned window or entry condition, intended performer System or local system-role-kind condition, and enough constraints, resources, dependencies, commitments, targets, or baseline to make one coordination decision—for example, reserve a machine, order two items, staff a window, or set the target to be checked later. Membership depends on those intended-work claims, not on the carrier or presentation format.

The dependent kind supplies no second identity rule. Changing ClaimGraph content, the present EntityOfConcern, or the effective ReferenceScheme identifies another episteme under C.2.1. An explicit EpistemeEditionRelation may preserve historical continuity only when its own predicate obtains. Changing only a file path, carrier, layout, publication occurrence, ticket key, or version label leaves identity unchanged when the three C.2.1 discriminators are preserved.

The choices in §4.2 are intended-work content. Claims about actual occurrences, participants and effects retain their separate grounds under §9.

Distinction (memory aid): Method = how in principle. MethodDescription = claims about how the Method is done. WorkPlan = when, by whom in intent, under which constraints. Work = what was actually performed on this occasion.

A.15.2:4.2 - PlanItem content

A PlanItem is a declaration-local content component in one U.WorkPlan. Its designator is interpreted inside that plan episteme. A receiving episteme may refer to this content component.

Choose only the claims the team will use to coordinate the intended work. The list is an open recognition palette, not a record schema or a kind defined by enumeration. When one row mentions a neighboring relation, state its own participants and predicate rather than treating the row or reference as proof that it obtains:

  1. Target Method and description use — identify the Method intended for enactment. When a plan claim relies on a MethodDescription, cite that episteme and the instruction, constraint or justification it supplies. A.3.2 requires the admitted Method as its exact EntityOfConcern and substantive way-of-doing claims. Call it a later edition only when the C.2.1 EpistemeEditionRelation obtains. The plan describes intended Work that is to enact the Method, with a System as its intended performer; the MethodDescription supplies the claims used in planning. These intended relations do not establish an actual Work occurrence.
  2. Planned window or entry condition — earliest start, latest finish, timebox, recurrence, blackout period, or another exact intended temporal condition.
  3. Intended performer and system-role-kind conditions — an intended performer U.System designator, the local system-role kind under which that performer is expected to qualify, its admission conditions, and, only when it already obtains, an assignment occurrence whose species is declared under U.SystemRoleAssignment and that is expected to cover later Work. A proposed holder-and-kind pair is not an actual assignment.
  4. Capability requirement — an exact A.2.2 threshold or CapabilityFitCondition needed for planned work entry. Cite an existing capability claim only when the plan relies on it. The plan establishes neither the holder’s actual ability nor fit for the later work interval.
  5. Resource budgets and reservations — intended energy, materials, machine windows, money, and reservation claims. A planned budget is neither a performed resource-use fact nor a B.1.6 aggregate ledger result.
  6. Dependencies and commitments — state the source item or commitment, the affected target item, and the condition that blocks, orders, overlaps, or excludes the planned work. A cited gate, approval, source-currentness, or promise claim keeps its own predicate; the citation establishes neither gate passage, approval, promise fulfilment, nor world-side ordering.
  7. Acceptance targets — name the criterion and target value or window that a later evaluation will test. The target is not the evaluation or acceptance verdict.
  8. Location, affected-subject, and asset constraints — where a proposed performance is intended to occur and which existing referent it is intended to concern, without asserting actual participation or change.
  9. Desired planned bindings — use A.15.3 only when the plan fills one participant, argument, or result member already declared by A.6.5, A.6.1, or another pattern that states both the member meaning and its later actual-use predicate. A.15.2/A.15.3 state the intended choice; the declaration states what later counts as actual use. Without that member, keep an ordinary plan choice when typed reuse is unnecessary, or return missing-governor when it is necessary.
  10. Expected effect, result, or delivery target — write the planned sentence with its intended subject and target: for example, the machine state sought, measurement window to be met, entity to be produced, or publication or delivery to be completed. Use the pattern that defines that effect. The broad words output, result, outcome, deliverable, or handoff do not name one plan field or universal kind.

A method description may describe generic participant meanings and intended effects, but it supplies no planned filling by itself. Record the desired choice or expected effect in the plan.

Keep the baseline identifiable. Record later fulfilment or variance claims separately from the plan being compared. A new plan may use actual observations as its basis, but changing its identity-bearing content identifies another episteme under C.2.1. Keep step logic and solver details in the applicable Method or representation.

A.15.2:4.3 - Distinctions for schedule, process, and workflow wording

If you say…In FPF it is…Why
“The schedule for tomorrow’s surgeries”U.WorkPlanEpisteme declaring intended cases, windows, intended performer Systems and local system-role-kind conditions, resources, dependencies, and targets without asserting occurrence.
“The workflow for appendectomy”a U.Method, or its U.MethodDescription when A.3.2 admission holdsDistinguish the way of doing from the episteme describing that admitted Method; neither supplies a schedule merely by form.
“The process already ran at 10:00”a Work occurrence only when A.15.1 grounds that dated individualRecover the performer’s A.13 core, independent occurrence history, enacted Method, temporal extent and containing-System relation. Add F.6 only for precise assignment-bound attribution and other result or resource claims only when needed.
“The thermodynamic trajectory”a trajectory representation or model; U.Dynamics only when the episteme meets A.3.3’s state-space and transition-law criterion; add changed-subject and U.Transformation claims only when their direct predicates obtainA trajectory expression is neither plan nor performed work by form.
“The plan assigns Dr. Lee”U.WorkPlan carrying a claim about the System intended to perform the Work and its local system-role-kind condition; cite an assignment occurrence and its declared species only when that assignment already existsThe plan does not create or validate an assignment for the performed Work interval.
“The budget for Shift-B”a planned resource-budget claim inside a U.WorkPlan when the enclosing episteme meets §4.1The plan states the budget. A.15.1 identifies later Work, the applicable resource-use predicate states what it consumed, and B.1.6 aggregates those facts only when a ledger or allocation result is needed.

Schedule-word guard. Schedule-like words do not determine the kind by themselves. Use U.WorkPlan only when the text states intended Work, a horizon or window, the System intended to perform the Work or its local system-role-kind conditions, and enough constraints, resources, dependencies, targets, or baseline to coordinate it. Otherwise use the pattern for the claim made.

A.15.2:4.4 - Plan mereology (composition of plans ≠ composition of methods or work occurrences)

Keep these three relations distinct:

  • Method composition admits a composite U.Method only when A.3.1/B.1.5 supplies the submethods, whole-forming relations, and whole-level commitments.
  • Work organization starts with A.15.1 work-part relations. Temporal overlap is an independently governed interval fact under C.27.TA, and coordination is a separate direct claim when it obtains. Shared parentage or overlap creates neither a ConcurrentPartOf_work primitive nor coordination.
  • Plan-content organization arranges declaration-local PlanItem components inside the ClaimGraph for coordination. It is epistemic organization, not world-side work or method mereology.

Common plan-content claim families include:

  • precedence or dependency constraints naming source and target item designators, start or finish conditions, and any prerequisite or gate condition;
  • overlap or exclusivity constraints naming the scheduling policy and the windows it permits or excludes;
  • model-refinement claims comparing two plan models for one coordination inquiry about the same intended work under B.5.MR; and
  • alternative claims stating the alternatives and the independently governed condition used to choose among them.

For that comparison, recover what each plan model permits and requires. Establish how every completion of the proposed refined model is read against the earlier model. At least one completion must exist, and every completion must satisfy the earlier assertions under that reading. Strict refinement also excludes an earlier admitted answer; abstraction uses the converse comparison and checks the conclusion still needed. A tighter window, constraint, target or budget can supply the restriction. Check it together with the other assertions. C.2.1 identifies each plan episteme and any edition continuity separately; §4.5 tests later Work against a plan.

Start with the readable plan constraint—for example, “item B starts only after clearance claim C for item A is current.” Keep that claim inside the WorkPlan ClaimGraph and name the two item designators, the condition, scope, and qualification. Display order alone establishes no world-side ordering or Work parthood. When the receiving use needs a stable parameterized plan rule, A.6.RCD may supply a predicate-definition episteme. Open relation-kind admission only when a named receiver must distinguish occurrences of that relation; then E.24/E.24.UK and the standalone direct pattern must supply obtaining and identity before A.6.REL is used. If the rule, its source predicates, or occurrence identity cannot be stated, return the corresponding A.6.RCD blocker rather than minting Precedes_pl, MutuallyExclusive_pl, Refines_pl, or another pseudo-kind here.

Didactic rule: A PlanItem does not force an identical work shape. A later one-case comparison with an independently identified Work occurrence remains a separate local plan-use assertion unless an admitted direct relation has been supplied.

A.15.2:4.5 - How WorkPlan meets Work

Ask one concrete question first: “Did Work W satisfy plan item I under policy F?” Identify W under A.15.1, then name WorkPlan episteme P, declaration-local item I, and policy episteme F. Check only the independently obtaining facts that F requires—for example, enacted Method, required assignments, and Work extent in the hospital case below. Put the answer in a separate C.2.1 assertion whose EntityOfConcern is P. The assertion neither changes P nor admits a WorkPlanFulfilmentRelation kind.

A positive answer requires every fact in F’s positive criterion. State a negative answer only when F contains an applicable failure or closure criterion and the case facts satisfy it. Missing occurrence facts return missing-information; an absent predicate or policy authority returns missing-governor. Neither stop is a negative claim. The assertion keeps W, P, I, F, polarity, and the supporting facts explicit; a matching label, window, ticket, record link, or policy name alone does not establish the facts required by F. Several Work occurrences may satisfy different parts of I, or one consolidated Work may satisfy several items, only when F states that mapping. Unplanned Work remains valid Work; a separate assertion may classify it as unplanned for one named variance or improvement use.

If a receiving use needs a stable parameterized fulfilment definition but consumes no relation-occurrence identity, use A.6.RCD disposition 3 to publish one predicate-definition episteme with one truthful EntityOfConcern, participant meanings, derivation, applicability, polarity, dependencies, and currentness; it is not a RelationSignature or relation kind. Only when a named receiver also needs distinguishable fulfilment occurrences may A.6.RCD return a relation-kind candidate for E.24/E.24.UK admission, a standalone direct subject settlement, and later A.6.REL discipline. Until those requirements are met, preserve the local assertion and reusable predicate semantics, and return the A.6.RCD blocker for the occurrence-facing use.

A variance question is handled in the same economy. Use a separate local comparison assertion unless the measurement, evaluation, acceptance, resource, or temporal pattern already states the exact comparison. Name one planned value in P and I, one independently established actual value, the comparison method, scale, qualification window, and result. Do not make variance an intrinsic field of a Work occurrence, enter it into P’s identity-bearing claim content, or rewrite the plan. Common comparison questions include:

  • schedule variance: actual Work extent against the planned window, using the exact temporal comparison and any B.1.4 aggregate needed by the receiving KPI;
  • resource or cost variance: A.15.1 performed resource-use facts or a B.1.6 aggregate result against the planned budget;
  • method variance: actual enactsMethod against the intended method, including a substitution claim when the comparison asserts substitution;
  • description-selection variance: the method-description episteme cited by a named assertion about a Work occurrence or by a separately governed instruction-use claim, compared with the description reference planned earlier; call either object an edition only when the C.2.1 EpistemeEditionRelation predicate obtains, and do not treat that episteme as enacted;
  • acceptance-target variance: a separately governed measurement, evaluation, or acceptance verdict against the planned target; and
  • assignment variance: for every actual performer, compare the obtaining assignment occurrence used by F.6 with the corresponding intended performer and local system-role-kind conditions in the plan. Check the occurrence’s directly declared species, actual holder System, assigned local system-role-kind value, every additional participant that the plan constrains, and the part of its covering interval constrained by the plan. Report a species mismatch when the actual occurrence instantiates a different assignment species; when the species matches, report an occurrence-value mismatch only for a holder, assigned-kind value, plan-relevant additional participant, or interval value that differs from the plan. Do not collapse either comparison into a label match.

Manager’s view: A usable coordination plan can stop before later comparison. If a receiving question needs fulfilment or variance, recover the relevant baseline and policy under §4.5; missing comparison grounds limit that use rather than cancelling the plan’s membership.

A.15.2:5 - What a good WorkPlan states (review checklist)

Apply the items needed by the coordination or comparison claim; this is a recognition palette, not a required full schema:

  1. Present EntityOfConcern, horizon, and cadence (for example, the current service system and “W36 surgeries” or “daily ETL”), with possible future performances kept as plan-content designators.
  2. PlanItem content components with intended-performance designator, target Method, the selected method-description episteme when one plan claim relies on it, planned windows, and dependencies.
  3. Intended performer System and local system-role-kind conditions, any reference to an existing assignment occurrence and its declared species, and the A.2.2 capability threshold or fit condition; a proposed holder-and-kind pair or threshold is not an assignment or fit result.
  4. Safety envelopes, constraints, and other admissibility conditions for planned work.
  5. Resource budgets and reservation claims on assets.
  6. Acceptance targets with their direct criteria and intended qualification windows.
  7. Cross-context interpretation boundary: when a proposed use depends on correspondence between local senses with different interpretation bases, pin both effective reference schemes and resolve the two F.17 SchemeSenseCell values. F.9 says only whether their Bridge obtains. A separate C.2.1 claim says whether this reuse is acceptable in this direction, under this correspondence rule and tolerated loss; A.10 governs ordinary evidence reliance and B.3 governs assurance-bearing reliance. A negative use claim leaves the Bridge true but stops the reuse; a non-passing reliance result stops or narrows it. Establish any value conversion, target comparison, commitment, acceptance, verdict reuse, plan coordination, or Work claim separately under the pattern that defines it.
  8. Baseline when the receiving comparison needs one. Keep the earlier plan identifiable. Claim edition continuity only when EpistemeEditionRelation obtains, and use a change note when the attributed difference needs explanation. If continuity is unestablished, leave it unresolved; a first plan has no earlier plan relation, and a negative continuity claim needs its own basis.
  9. Policy pointers to A.15.1 work continuity, B.1.4 temporal aggregation, B.1.6 resource aggregation, and any local comparison policy needed by the receiving KPI.
  10. Exception question stating how ad hoc or emergency Work will be handled by a local plan-use assertion; use one reusable predicate-definition episteme when the receiving use needs a stable definition, and require an admitted direct relation kind before claiming fulfilment or exception occurrences.

A.15.2:6 - Archetypal grounding (parallel domains)

These constructed cases stipulate their project facts. The hospital case follows one plan item through a later comparison; the other cases show different constraints and reuse limits.

A.15.2:6.1 - Hospital OR day plan (shift rota + cases)

  • WorkPlan: OR_DayPlan_2025-08-12-E3 : U.WorkPlan is one C.2.1 episteme. Its present EntityOfConcern is existing system OR-Service-System-12 : U.System; its effective reference scheme is HospitalORPlanningScheme-E4; its horizon is 2025-08-12T00:00:00+03:00/2025-08-13T00:00:00+03:00. Proposed case performances remain ClaimGraph designators and are not dated Work occurrences.
  • One PlanItem: Case_1_Appendectomy coordinates proposed performance PlannedAppendectomy-Case1 through the following content.
PlanItem concernFilled value
target methodLaparoscopicAppendectomyMethod-E2 : U.Method
planned window2025-08-12T09:00:00+03:00/2025-08-12T10:30:00+03:00
intended performer and system-role-kind conditionsone performer System satisfying SurgeonSystemRole and AppendectomyLeadCapability-v3; one performer System satisfying AnesthetistSystemRole and ORAnesthesiaCapability-v2; these are intended conditions, not system-role assignments
budget and reservations90 minutes of OR-3, one SterileKit-A17, and consumables budget ORCase1-Consumables-B3
dependencypositive PreOpClearance-Case1-E2 claim must be current before the planned window starts
acceptance targetprocedureCompleteBy10:30, compared under C.27.TA against the exact Work extent after Work occurs
baselineC.2.1 episteme OR-DayBaseline-2025-08-05-E1
  • Later Work: The case independently admits DrK and DrM as Systems. Under the local A.13 criteria, DrK regulates the operative action to the procedure target and DrM maintains the declared anesthesia conditions under relevant perturbations; the stipulated observations support these classifications for the surgery scope and window. Under the directly declared assignment species, the stipulated case facts establish obtaining RA-Surgeon-DrK-2025-08-12 and RA-Anesthetist-DrM-2025-08-12 occurrences with those Systems as holders and the intended local kinds, covering that window. The observed performance history and the local containing-System predicate place the complete occurrence within OR-Service-System-12. For this constructed case, also assume that all six common construction components under A.1:4.2 have been independently established for AppendectomyWork-2025-08-12-Case1.

    These premises and the enactment and extent below independently admit AppendectomyWork-2025-08-12-Case1 : U.Work under A.15.1, with workContinuityPolicyRef = SingleProcedureFromAnesthesiaStartToHandover-E1, temporal extent 2025-08-12T09:04:00+03:00/2025-08-12T10:21:00+03:00, and enactsMethod to LaparoscopicAppendectomyMethod-E2.

    Because the named one-case policy expressly consumes both assignment-bound attributions, F.6 afterward establishes performedUnderAssignment for RA-Surgeon-DrK-2025-08-12 and RA-Anesthetist-DrM-2025-08-12 through those same assignments. The named policy tests the within-window claim qualified under C.27.TA. Either failed F.6 relation alone would prevent this attribution-dependent fulfilment conclusion while preserving independent Work admission. If the same finding questions an actual admission premise, recheck that premise and its dependents under A.15.1.

  • Named one-case policy: ORCase1FulfilmentPolicy-E2 is one C.2.1 episteme about plan episteme OR_DayPlan_2025-08-12-E3, interpreted under HospitalORPlanningScheme-E4. Its ClaimGraph is limited to item Case_1_Appendectomy and states positive polarity only when the identified Work enacts the target Method, both required performedUnderAssignment relations obtain, and its extent lies inside the planned window. It uses only those four facts for this local conclusion, does not travel to another plan episteme, and admits no fulfilment relation kind.

  • Visible result: C.2.1 assertion episteme OR-DayPlan-Case1-Fulfilment-Assertion-E1 has OR_DayPlan_2025-08-12-E3 as its EntityOfConcern; its ClaimGraph names AppendectomyWork-2025-08-12-Case1, item Case_1_Appendectomy, policy ORCase1FulfilmentPolicy-E2, the four supporting facts, and positive polarity. The result says that this Work satisfies this plan item under that policy. It does not rewrite the plan and does not assert a universal relation.

  • Nearest false shortcut: a theatre log row carrying key Case_1_Appendectomy and start time 09:04 establishes neither performedUnderAssignment nor enactsMethod. Without those independently obtaining facts the local conclusion returns missing-information; matching labels and times produce neither negative polarity nor fulfilment.

  • Edition boundary: this is the first plan episteme selected for the day. Changing its ClaimGraph identifies another episteme; edition continuity with the earlier plan requires its own C.2.1 basis. If that relation is unestablished, continuity remains unresolved rather than becoming negative. A reused label or Rev-4 note supplies no such basis. A later fulfilment policy must identify whichever plan it judges.

A.15.2:6.2 - Fab maintenance weekend (asset reservations)

  • WorkPlan: Fab_Maintenance_W36 is interpreted under FabMaintenancePlanningScheme-E3, has horizon [2025-09-06T00:00Z, 2025-09-08T00:00Z), and concerns already identified Fab-Production-System-4 : U.System. Tool_42 and Tool_13 remain assets named by the PlanItems; they are not an unproved joint EntityOfConcern.
  • PlanItem content: Tool_42 chamber clean under ChamberCleanMethod-E2; Tool_13 calibration under ToolCalibrationMethod-E1; the ClaimGraph carries an exclusivity constraint with production windows. The scheduling policy, per-item windows and reserved quantities remain case inputs for this abbreviated illustration.
  • Reservations: nitrogen, DI water, metrology window.
  • Later local assertion: The chamber-cleaning Work occurrence is identified independently as an individual admitted under U.Work. FabChamberCleanPlanUsePolicy-E1 asks whether that Work enacted ChamberCleanMethod-E2, stayed inside the planned window, and kept nitrogen use within the reserved amount. A.15.1 supplies the Work and enactment facts; C.27.TA qualifies the within-window claim; B.1.6 supplies the resource aggregate used in the budget comparison. For this illustration, assume that the three policy conditions all obtain; a separate C.2.1 assertion about the plan then states positive fulfilment. Early completion and nitrogen underrun additionally require the corresponding strict comparisons. A shared item label or reservation row supplies none of those facts.

A.15.2:6.3 - Data-center rollout (multi-context plan)

  • WorkPlan: DC_Rollout_Phase-2 is interpreted under DCOperationsPlanningScheme-E5, has horizon [2025-09-01T00:00Z, 2025-09-15T00:00Z), and concerns already identified Service-A-Operations-System : U.System. The Security Audit scheme remains a separate interpretation source used only through the branch below.
  • Interpretation boundary: Operations uses DCOperationsPlanningScheme-E5; Security Audit uses SecurityAuditScheme-E4. Their acceptance criteria remain separate; apply the branch in checklist item 7 before proposing any cross-context reuse.
  • Bridge premise: F.17 cells OperationsReadyCell-E3 and SecurityAuditPassedCell-E2 participate in F.9 Bridge OpsAuditReadinessOverlapBridge-E1 under OpsAuditPartialOverlapProfile-E1. The Bridge obtains as partial-overlap: both senses exclude a known blocking security defect, while Operations readiness also requires rollback rehearsal and live monitoring and the audit sense applies its own security criteria.
  • Rejected verdict transfer: C.2.1 claim AuditPassAsOperationsReadyUse-E1 proposes copying GateDecision=pass from A.21 gate SecurityAuditGate-E2 into an A.15.5 work-entry readiness result, from the audit cell to the Operations cell, by identity transfer and with zero tolerance for omitted readiness conditions. The claim is negative because the two senses do not align on rollback rehearsal or monitoring readiness. A.10 evidence-provenance path OpsAuditTransferEvidencePath-E1 has RelianceDisposition=pass for that negative claim, so the team retains the A.21 audit decision and evaluates Operations readiness separately under A.15.5. The obtaining Bridge remains true. A narrower plan use may cite the audit decision as one readiness input; it still cannot transfer the verdict.
  • PlanItem content: Deploy Service A, Pen-test A; dependency and window claims name their predicates and conditions inside the plan ClaimGraph.
  • Later local assertions: Deployment and audit Work occurrences are identified independently as individuals admitted under U.Work. Separate operations and audit evaluations apply their own targets and produce separately governed verdicts; plan-use assertions state local fulfilment and per-context comparison without adding those actual facts to the plan content or creating one cross-context fulfilment relation.

A.15.2:7 - Scope Declaration and Rationale

  • Applicability: Use the same intended-work test for coordination, budgeting, architecture planning, teaching examples, and source or evidence questions.
  • Scope declaration: Domain-general where a system is coordinating possible future performed work. A tide table, weather forecast, simulation schedule, or predicted natural trajectory is not a WorkPlan unless its claim content also coordinates a system’s intended Work. Interpret the plan through its effective ReferenceScheme and, when the use needs a bounded claim set or model-applicability question, the exact U.ClaimScope and ModelApplicabilityRelation governed by A.2.6 and A.1.1. An already identified BoundedModelUseStructure enters only when a separate receiving claim or use relation states how that structure changes this plan use and its direct predicate obtains; otherwise omit the structure rather than inventing a context field. Ordinary project, domain, or context wording stays Plain and creates no container or identity field. For cross-context sense reuse, apply checklist item 7.
  • Rationale: A WorkPlan is an episteme that systems can use to coordinate intended Methods, intended performer Systems and local system-role-kind conditions, and possible future Work. The plan retains those intended choices for coordination and, when needed, later comparison.

A.15.2:7a - Conformance Checklist

IDRequirementPractical test
CC-A15.2-1C.2.1 ClaimGraph, one already identified present EntityOfConcern, and effective ReferenceScheme identify the episteme; A.15.2 adds one stable intended-work membership condition and no second identity.A possible future performance or PlanItem designator is not used as an existing EntityOfConcern merely because it appears in the plan. Carrier, layout, publication, ticket key, and version label can change without reidentification when the three discriminators remain fixed.
CC-A15.2-2A conforming U.WorkPlan makes substantive claims for coordinating possible future performed Work over a horizon through at least one PlanItem.The plan states an intended-performance designator, Method, window or entry condition, the System intended to perform the Work or its local system-role-kind condition, and the constraints, resources, dependencies, commitments, targets, or baseline needed by its receiving use without asserting that a Work occurrence exists.
CC-A15.2-3Every PlanItem remains declaration-local plan content and names the possible future performance and claims it coordinates.Resolve the designator to the content component in the identified WorkPlan; establish a claimed occurrence or participant separately under its own predicate.
CC-A15.2-4Claims about a System intended to perform the Work, its local system-role-kind conditions, and A.2.2 capability requirements remain planned. Cite an assignment occurrence and its declared species only when that assignment already obtains; the plan supplies no capability-fit result.Publishing a proposed holder-and-kind pair or threshold creates neither assignment, capability, nor fit for the later Work interval.
CC-A15.2-5A desired participant, argument, or result uses A.15.3 only after one declaration member supplies its reusable meaning and later actual-use predicate.The plan states the intended choice; it does not turn method-description wording, a broad field label, a compatible ValueKind, or a planned reference into participation. Keep ordinary plan content when typed reuse is unnecessary; otherwise return missing-governor.
CC-A15.2-6An expected change, result, entity, delivery, acceptance, or outcome names its intended subject and target and remains a plan claim.No output, result, outcome, deliverable, or handoff field is treated as a universal kind or as proof that the object exists or the effect occurred.
CC-A15.2-7PlanItem organization names local predicates and conditions but does not admit relation kinds or force the same shape on performed Work.Graph order and spellings such as Precedes_pl or MutuallyExclusive_pl establish no reusable relation or world-side fact.
CC-A15.2-8A one-case fulfilment answer is A.6.RCD disposition 2: a separate assertion about plan episteme P, item I, Work W, and policy F. F names the independently obtaining Work facts and the positive or negative criterion used.Shared labels or links cannot close the claim. Negative polarity needs an applicable explicit criterion and case facts; unavailable facts return missing-information, absent predicate or policy authority returns missing-governor. Repeated semantics may use a predicate-definition episteme; only an occurrence-facing receiver can open relation-kind admission.
CC-A15.2-9A variance question compares exact planned and actual values through one local comparison assertion or the measurement, temporal, resource, evaluation, or acceptance pattern that defines the comparison.Comparison method, scale, qualification window, and result are explicit; no universal variance relation or intrinsic Work field is inferred.
CC-A15.2-10When cross-context plan use depends on semantic correspondence between differing local interpretation bases, apply the separate Bridge/use/reliance branch in checklist item 7.F.9 is cited only for an exact SchemeSenseCell Bridge; the separate C.2.1 use claim and A.10 or B.3 reliance result decide whether the attempted use proceeds, narrows, or stops. Run target conversion, commitment, acceptance, and verdict reuse under the pattern that defines each claim; the Bridge establishes none of them.
CC-A15.2-11Evidence, assurance, gate, launch-value, and result-measurement claims stay in the patterns that govern those relations.Evidence references and requests in the plan do not by themselves establish the cited support or requested result. An A.15.5 readiness result and GateDecision=pass alone establish neither an A.2.8.PER permission relation nor a Work occurrence.
CC-A15.2-12Planned preparation tasks may appear in the WorkPlan, but A.15.5 governs the local readiness criterion and result.The plan says what should be prepared. A.15.5 judges readiness for work entry from the facts required by its selected criterion.

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

  • Future-work-as-entity. Do not use a possible future performance or PlanItem designator as C.2.1’s already identified EntityOfConcern or as a dated Work occurrence; keep it in plan claim content until an exact direct entity or occurrence exists.
  • Plan-as-actual. Do not treat a Gantt bar, Kanban ticket, shift rota, or calendar booking as performed work; identify or cite a Work occurrence admitted under U.Work only when A.15.1’s occurrence basis is present.
  • Workflow-as-schedule. Do not infer a plan from a MethodDescription or flowchart; recognize a U.WorkPlan only when the claims state a present subject, intended-performance designator, horizon, window, constraints, the System intended to perform the Work or its local system-role-kind conditions, and any baseline needed for the current coordination decision.
  • Assignment-or-capability-by-plan. Do not treat an intended performer System, local system-role kind, proposed holder-and-kind pair, threshold, or capability reference as an obtaining U.SystemRoleAssignment, actual holder ability, or fit result for later Work; apply A.2.1/A.2.2 at the exact interval and use.
  • Budget-as-cost. Do not book planned budgets as performed resource use; establish performed facts on A.15.1 Work and any aggregate ledger or allocation under B.1.6.
  • Plan-shape overreach. Do not force performed Work to match plan decomposition, infer non-fulfilment from a missing link or unavailable facts, or mint a fulfilment relation from a local comparison. Stop at a positive or governed-negative local compound assertion when it suffices; use a predicate-definition episteme when a stable definition is needed without occurrence identity; open relation-kind admission only for a named occurrence-facing need.
  • Context-bridge overreach. Do not bridge contexts as wholes or use F.9 to convert planned values, commitments, criteria, or verdicts. F.9 relates exact SchemeSenseCell values; apply checklist item 7 when a proposed plan use depends on that cross-context semantic correspondence.
  • Evidence-note-as-claim. Do not infer that referenced support is available or that a requested result was obtained merely because the plan contains a reference or request.
  • Readiness-or-gate-as-permission. A ready result reports entry conditions and an A.21 gate decision governs its declared crossing; neither institutes permission or performed Work. Recover an exact current A.2.8.PER grant when permission is required.
  • Description-as-planned-filling. Do not turn a method-description word such as input or output into a planned slot. Use A.15.3 only when one declaration member already states what the value means and what later counts as actual use. Otherwise keep the choice as ordinary plan content or return missing-governor when typed reuse is required.
  • Expected-as-actual. Do not treat a desired filling, expected effect, output, result, outcome, deliverable, or handoff as an actual participant, change, returned value, produced entity, delivery, acceptance, or downstream effect.

A.15.2:7c - Consequences

BenefitTrade-off and mitigation
Plans become inspectable without being confused with performed work.More explicit claims; mitigate by using compact PlanItem content for ordinary coordination.
Variance becomes meaningful because planned baseline and performed work stay separate.Requires discipline around baselines; keep the plan episteme and baseline visible, and name an edition relation only when its predicate obtains.
Cross-context reuse exposes the correspondence and conditions on which the proposed transfer depends.Apply checklist item 7 to the changed sense or value being reused; establish its required correspondence, use claim and reliance basis.
P2W carry-through can supply intended-work coordination.Use A.15.1, A.15.3, A.15.4, A.15.5, A.10, B.3, A.20, or A.21 only when the source makes the corresponding performed-work, planned-filling, appearance-based reliance, readiness, evidence, assurance, internal constraint, or gate claim.

A.15.2:7d - SoTA Alignment

Source tradition and contributionFPF useShortcut rejected
ISO 21502:2020 project-management guidance and PMBOK Guide Eighth Edition (2025), cited for planning practiceA plan declares its horizon and intended Method or Method family, adding only the baseline, dependencies, resource expectations and acceptance targets needed for current coordination. Compare planned and performed values when the receiving question needs that result.Treating a schedule, ticket, or baseline as evidence that the Work already occurred.
ISO 55000:2024 asset-management practiceAsset reservations, maintenance windows, lifecycle objectives, risk, and value expectations belong in planning until A.15.1 identifies the performed Work and the applicable change and resource-use predicates are satisfied.Treating planned asset availability or reserved capacity as actual asset intervention or actual resource consumption.
ISO 9001:2015 with Amendment 1:2024, a quality-planning sourcePreserve planned quality objectives, acceptance targets and performance-evaluation criteria so actual results can be compared with that baseline.Rewriting the plan after the fact so that quality, cost or schedule variance disappears.
Mature adaptive-work representation practice such as OMG CMMN 1.1 (2016)Weakly structured or ad hoc Work can still be compared with identified plan content through a local assertion, or through a direct relation when one is defined.Forcing every emergency, adaptive, or consolidated Work occurrence into the original plan shape; or minting a universal fulfilment relation from one comparison.

A.15.2:7e - Relations

  • Builds on: C.2.1 for episteme identity and local assertion identity; A.15 for System-Role-Method-Work alignment; A.15.1 for independently identified performed Work occurrences admitted under U.Work; A.2.1 for direct U.SystemRoleAssignment species; A.2.2 for qualified holder-ability claims, thresholds and fit conditions; A.3.1 for U.Method; and A.3.2 for U.MethodDescription.
  • Coordinates with: B.5.MR for refinement and abstraction comparisons between plan models; A.15.3 for planned filling against governed declarations; A.6.1 for operation argument and result declarations; A.6.5 for RelationSignature participant declarations; A.6.RCD for the existing-direct/local-compound/reusable-predicate/relation-kind economy; E.24/E.24.UK for any later kind admission; A.6.REL only after an admitted direct or derived relation needs occurrence discipline; A.15.4 for work-relevant appearance-based reliance repair; A.15.5 for work-entry readiness; C.27.TA for direct temporal-aspect claims; B.1.4 for temporal aggregation; B.1.6 for performed-resource aggregation; A.10 for accounts of independently established evidence-provenance relations; B.3 for assurance; A.20 for internal constraint results and A.21 for gate decisions; C.32.P2S for architecturing-flow references to intended work; E.17 for publication-use questions; and F.9 only for cross-context SchemeSenseCell correspondence, with any proposed use and reliance routed through checklist item 7.
  • Used by: P2W carry-through when accepted problem-side content must guide work planning, and P2S carry-through when architecture-selected structures require intended-work epistemes. Both uses keep present plan subject, possible future performance, readiness, performed Work, actual use, evidence, gate, comparison, result, and downstream effect separately governed.

A.15.2:8 - P2W WorkPlanning use

When the next P2W question concerns planned work, use the accepted problem-side claim to choose or qualify the relevant PlanItem content. One U.WorkPlan retains its present EntityOfConcern and states possible future performed Work over a horizon through PlanItem content: intended-performance designators, windows, Methods, intended performer Systems and local system-role-kind conditions, capability requirements, constraints, budgets, dependencies, commitments, targets, evidence-reference notes, and source-currentness requests. If the plan chooses a value for a reusable declaration member, use A.15.3; if it states an expected effect, name the intended subject and target under the pattern that defines that effect.

When the P2W use also needs a readiness question, the WorkPlan may supply target PlanItems, planned preparation tasks, reservations, and planned baselines. A.15.5 supplies the exact readiness criterion and local result about that plan content; the criterion may consume current commitment, resource, work-in-progress or load, flow-policy, and launch-gate claims only through their separately governed values, boundaries, counting or threshold rules, and qualification windows.

If the same P2W source material also claims performed work, an actual launch value or participant, evidence, gate passage, result, measurement, publication use, appearance-based reliance repair, or refresh, state that claim outside the WorkPlan under the pattern that defines it.

A.15.2:9 - Launch-value and actual-use boundary for P2W

For P2W use, U.WorkPlan may state intended performer Systems and local system-role-kind conditions, planned values, A.15.3 fillings, constraints, reservations, commitments, and evidence-reference notes. A.15.5 may later publish one C.2.1 work-entry readiness result whose EntityOfConcern is this WorkPlan; its ClaimGraph may designate the relevant declaration-local PlanItem content used by the readiness criterion. An A.21 GateDecision separately selects, narrows, blocks, or passes its declared crossing under one current GateProfile. Neither result institutes permission.

When the entry criterion consumes permission material, keep the current A.2.8.PER values distinct. A GrantedPermissionRelation@Context occurrence is strong permission only for its exact beneficiary, action specification, U.ClaimScope, and validityWindow. A NonProhibitionFinding@Context reports only its frame-relative result for its evaluationWindow; it is not a grant. A PermissionNormConflictFinding@Context exposes overlap for its overlapWindow, and a current resolution result is usable only when the A.2.8.PER resolution predicate obtains and the result names its effectiveWindow; an unresolved conflict stops or degrades the proposed use. PermissionExerciseRelation@Context and NonViolationFinding@Context require already dated actual Work and therefore cannot be prospective proof that the intended performance may start. When the governing entry policy requires a grant, absence or unavailability of that exact current grant permits no authorization claim; readiness, gate passage, or non-prohibition cannot stand in for it.

At performed-work entry, identify one Work occurrence as an individual admitted under U.Work by A.15.1. For an actual relation participant or another world-side value, name the direct relation and its obtaining predicate. For an operation argument or returned result, use A.6.1 only after the application and its declaration-local binding predicate obtain.

A.15.2:10 - Lowering, repair, and refresh conditions

Lower a candidate U.WorkPlan claim when the reader cannot identify one present EntityOfConcern, the effective ReferenceScheme, the horizon, one substantive PlanItem, or its intended-performance designator well enough to coordinate the intended work. Keep other participants in the ClaimGraph. Split only when combining independent subjects makes the selected EntityOfConcern untruthful or breaks the intended identity or comparison use under C.2.1. Retain independently usable content and any other established claims; do not claim a conforming WorkPlan without its membership basis.

When intended-work content changes, revise the affected claims and reconsider dependent coordination or comparison uses. A change to ClaimGraph, present EntityOfConcern or effective reference scheme identifies another C.2.1 episteme. Test EpistemeEditionRelation separately: established continuity supports an edition claim, an established negative result excludes it, and absent evidence leaves it unresolved. A replacement use can be selected without settling historical continuity. A file, layout, ticket key or revision label alone establishes neither reidentification nor continuity.

Do not rewrite an independently identified Work occurrence when only the plan changes, and do not make a revised plan evidence that Work occurred. Repair an actual participant, resource use, change, result, production, delivery, acceptance, evidence, or downstream effect under the pattern that defines that claim. When a one-case local fulfilment or variance assertion is no longer enough, use A.6.RCD disposition 3 if a stable predicate definition is sufficient. Only when a named receiver needs distinguishable relation occurrences does kind admission open; if no truthful occurrence settlement or governing pattern is available, preserve the plan, local assertions, and reusable definition and return missing-governor for that stronger use.

Before a new reliance-bearing use, confirm that the selected plan and supporting claims remain applicable and sufficiently current. Reuse unchanged grounds and recheck affected dependencies. Where the use crosses local senses, apply checklist item 7 to the actual correspondence, proposed transfer and reliance question; establish any required value conversion or verdict use under its own predicate. Keep only intended-work claims in the plan being used; route a separate readiness, performance, evidence, gate or result claim to its governing pattern.

A.15.2:End

Referenced in the corpus

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