A.15.1 - U.Work: Dated Performed Work Occurrence
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
At a glance. Identify a dated action, its performer Systems, the Methods they followed and the interval of performance. Apply the full §4.1 test to admit that occurrence as U.Work. Its results, resource use and other relations need their own grounds. Plans and logs are epistemes describing intended and reported work.
Use this when. Use this pattern to identify a dated performed occurrence and establish its admission basis. It also resolves cases where a representation—for example, a plan, log or result statement—has been mistaken for the occurrence or leaves that basis unclear. Use F.6 separately after admission when a precise claim about the assignment under which Work was performed is current.
Primary reader. Engineers, operators, process owners, modelers, auditors, and FPF authors who need to establish what happened as performed Work and which claims the available evidence supports.
First useful object and short-account rule. Name the candidate dated action and keep the evidence needed by §4.1 recoverable. A Work-only account may stop after admission. Add another enactment, containment, attribution or neighboring claim only when the receiving use needs it; §4.6 routes result, change, production, delivery and judgment claims.
Use the following route:
- Recover the direct subject first. If the question is only about a Method, plan, capability, result, change, resource, evidence item, or publication, use that subject’s pattern and stop.
- Identify the candidate performer as a System under A.1 without using the candidate Work to prove systemhood.
- For every precise Agent claim, recover the A.13 core in §4.0 under independently stated criteria. Observed behavior may supply evidence; assuming that the candidate is already Work may not supply the proof. Open the characteristic-profile branch only under its stated receiving-use condition.
- Apply the full §4.1 test, including the occurrence’s A.1:4.2 construction and its Work-specific factual premises. Follow its candidate-facts-to-claims explanation to admit
W : U.Workand then assert its obtaining typed relations. - Only after admission, and only when precise assignment-bound attribution is current, use F.6 with the same obtaining A.13 assignment for each performer.
- Add direct Work-to-referent, operation-binding, resource-use, result, change, production, delivery, evaluation, or acceptance claims only when their own predicates and case facts obtain.
Compact positive example. On 27 July 2026, Robot-7 performed the 09:00–09:20 inspection in InspectionService-A, following TurbineInspectionMethod under InspectionAssignment-17.
Basis of this example. Before inspection, Robot-7 is independently admitted as a System. InspectionControllerSystemRole has a declared A.2 membership criterion for goal-directed, condition-sensitive regulation of the inspection action; evidence shows that Robot-7 satisfies it. InspectionAssignment-17 is an obtaining direct assignment of that kind for the service scope, working situation, and window. The same candidate inspection occurrence satisfies the six common constructive components in A.1:4.2. Together with the established construction and performer bases, the 09:00–09:20 inspection history on 2026-07-27, TurbineInspectionMethod, and the declared containment within InspectionService-A satisfy the A.15.1 occurrence test, so first admit InspectionWork-17 : U.Work.
Then separately use the direct case fact for the pair to establish F.6 performedUnderAssignment(InspectionWork-17, InspectionAssignment-17) and say: Robot-7 performed InspectionWork-17 under InspectionAssignment-17.
A separate assurance use can evaluate obstacle response, policy choice, persistence or operational closure under its declared criteria. Cite A.13 characteristic-profile values only when that use consumes those characteristics; the core Work claim needs no profile here.
Nearest non-use example. A dashboard says inspection complete but exposes only a schedule row and a copied log. Keep the schedule as WorkPlan content and the log as possible evidence. Inspect the log for the facts it supports; leave Work admission unresolved until the A.13 performer basis and all occurrence premises can be recovered.
Recognition check. Can the team recover the full §4.1 basis for one dated occurrence? When precise assignment-bound attribution is needed, can it also establish the separate F.6 relation under the conditions stated there?
Stop condition. Stop the admission branch once the candidate is admitted under §4.1 as one U.Work at the needed granularity, or the account has been limited to the independently supported neighboring claim. Keep an unresolved admission distinct from a failed proposed admission basis. If precise assignment-bound attribution is current, resolve that separate F.6 claim; missing or rejected attribution alone leaves established Work intact. Recheck an admission premise only when the same finding questions it under §4.1. A missing optional profile blocks only the Grade, autonomy, profile, criterion-dependent or assurance claim that requires it.
What changes in practice. A team establishes one occurrence and its actual performer basis from the available evidence, then adds only the result, change, resource, or evidence relations that the current decision consumes.
What this buys. An inspectable identity for one dated Work occurrence, with its admission basis recoverable and its attribution and neighboring claims judged separately when needed.
Not this pattern when. Use the direct pattern when the current question concerns agency (A.13), a Method (A.3.1), MethodDescription (A.3.2), plan or schedule (A.15.2), readiness (A.15.5), appearance-based reliance (A.15.4), evidence or assurance (A.10 or B.3), publication-use behavior (E.17, with E.24.PUB for publication identity), or a declarative representation (C.2.P.DR).
A.15.1:1 - Problem Frame
After we have separated which system-role assignment obtains (via U.SystemRoleAssignment), what capability is being relied on (through an A.2.2 qualified holder-ability claim), how in principle the Work is done (the U.Method), and which claim-bearing episteme, if selected, describes that Method (U.MethodDescription), we still need a concept for what happened as performed Work in real time and space.
Every Work individual has an A.13 core basis for every claimed actual performer System, an independently grounded performance history, at least one enacted Method, temporal extent, and at least one locally declared containing-system relation. Several such relations may obtain under different system boundaries. The A.13 core already contains one obtaining assignment for its scope, situation, and window; an F.6 relation may later use that same occurrence but is not a Work-membership premise. A Work stands in a direct work-to-referent, binding, or resource-use relation only when that relation obtains world-side; none is a field stored in the occurrence. A separate assertion or description episteme designates that individual and states the independently obtaining relations. Judge its evidence against the occurrence or relation claim being made.
A.15.1:2 - Problem (what breaks without a notion of Work)
- Plan and occurrence confusion. Schedules and diagrams get mistaken for performed work, so audits and KPIs attach to plans or representations instead of dated occurrences.
- Method-description and work conflation. A method description, code artifact, or SOP is reported as if it were performed work; conversely, logs are treated as recipes.
- Who and when leakage. People and calendars are baked into method descriptions; reuse and staffing agility collapse.
- Resource misattribution. Performed energy, material, time or cost use is booked to a Method or assignment as though it occurred there. State the actual resource-use relation involving the dated Work; keep estimates and derived Method-level statistics separate under their accounting rules.
- Mereology muddle. Teams hand-wave over work parts, retries, overlaps, or long-running episodes; roll-ups double-count or miss work.
A.15.1:3 - Forces (what the definition must balance)
| Force | Tension we resolve |
|---|---|
| Universality vs. domain detail | One Work notion for surgery, welding, ETL, proofs, lab cycles—while letting each keep its vocabulary. |
| Granularity vs. aggregation | Selected-grain occurrences vs. composite Work; we need roll-up without presuming partlessness or letting Work parthood create another object’s composition. |
| Concurrency vs. order | Parallel or overlapped activities need clear part and overlap semantics. |
| Identity vs. retries | A failed attempt, a retry, and a resumed episode—what is “the same” work? |
| Time realism vs. simplicity | We need intervals and coverage but cannot bury users in temporal logic notation. |
A.15.1:4 - Solution — admit dated Work occurrences under U.Work
A.15.1:4.0 - Recover the A.13 agency basis before claiming an Agent performer
This pattern does not define another kind of Agent and does not infer agency from Work. In precise FPF prose, Agent is shorthand for the A.13 core result about one admitted U.System, one local agential system-role kind and its membership criterion, classification of that System under the kind, one obtaining assignment of that kind, and the claim scope, working situation, and time window needed by the use. Evidence must support each asserted core fact. An agency-characteristic profile is a separate conditional result, not a universal member of that core.
Before concluding that a candidate occurrence is Work:
- admit the candidate performer
SasU.Systemunder A.1 without using the candidate Work, assignment, capability, or actor-like name to establish systemhood; - state the proposed action, relevant objective or norm, conditions, System boundary, scope, working situation, and window without calling the occurrence Work;
- recover a local agential system-role kind
Kunder A.2 whose independently stated membership criterion names the stable work-facing contribution and the minimum goal-directed, condition-sensitive regulation required at this grain; - establish with appropriate evidence that
Ssatisfies that criterion and is classified underK; - recover one direct A.2.1 assignment species that assigns
Kand one obtaining occurrenceRAwhose holder isS, assigned-kind value isK, predicate and participants pass, and extent covers the scope, situation, and window; and - open A.13’s agency-characteristic profile only when the receiving claim asserts a Grade, autonomy, or profile value, the local membership criterion explicitly consumes one of its characteristics, or a named assurance use requires it. Then cite only the characteristic values, evidence, and qualification limits that use consumes. Otherwise the core basis stops at item 5 plus the evidence needed to establish items 1–5.
The local membership criterion is the positive discriminator. It may require selection or regulation among admissible continuations, or maintaining or returning to a declared target under relevant perturbation. Initiating, continuing, redirecting, regulating, pausing, and stopping are possible evidence, not a universal checklist. A closed loop can pass a narrow Grade-free regulation role and fail a broader inspection, diagnosis, or project-decision role. A separately asserted Grade still requires the auditable profile specified by A.13.
Only then test the candidate action, Method followed, time, containment facts under the declared local rule and other needed facts under §4.1. On pass, admit W : U.Work without assuming an F.6 conclusion. F.6 may then attribute W through the same obtaining RA. Underlying observations of the action can support the independently defined A.13 criterion; the assumption that it is already Work cannot establish agency or assignment. Test assignment under its own species rule, and do not use F.6 to establish Work membership. A profile substitutes for none of these tests.
Do not infer agency from systemhood, acting eligibility, an actor-like product name, assignment alone, capability, causal power, physical change, participation, containment, being the project system-of-interest, or one irrelevant feedback loop. If the local kind or its criterion, classification, obtaining assignment, required scope, situation, or window fit is missing, lower the sentence to functioning, behaviour, interaction, causal participation, transformation, or an unresolved performer claim as the available evidence warrants. If only a conditionally required profile or assurance basis is missing, retain any independently grounded core agency and Work claims and lower only that stronger profile, Grade, autonomy, or assurance claim.
A.15.1:4.1 - Definition and occurrence identity
U.Work is the admitted U-kind for dated 4D occurrence holons. One Work individual is one independently identified performed occurrence with its own temporal extent. Admit a candidate when its construction satisfies the six common components in A.1:4.2; the performance history is grounded; every claimed actual performer is an admitted U.System with a current A.13 core basis under section 4.0 for the exact action, scope, working situation, and window; the action actually follows at least one exact Method; its extent is known; and the complete occurrence lies inside an exact System boundary under the delimitation and qualification conditions declared for at least one local Work-to-System relation.
On admission, state the obtaining enactsMethod and containing-System relations. A.15.1 neither assumes nor requires F.6 performedUnderAssignment to establish W : U.Work.
From candidate facts to typed claims. A.1:4.1 permits reference to the independently identified occurrence as a U.Entity while its Work membership is unsettled. Use A.1:4.2 for the six common constructive components of that same occurrence. In addition to identifying the candidate, recover its constituents, constructive part relations and assembly, reidentification rule, composition-grounded whole-level characteristic, and possible participation in a larger constructive assembly, under that pattern’s conditions.
Recover the facts required by each constructive part predicate and assembly rule. Make a resulting Work-typed part assertion after the participating Work individuals have been admitted. Where those facts cannot be established independently of the proposed Work classification, leave the common premise unresolved. Reuse an established common-criterion result when its candidate and grounds are unchanged. Combine these construction premises with the Work-specific factual premises in §§4.0–4.1.
Establish the exact Method and containing System under their own patterns. Check the candidate’s performed history against the Method at the extent claimed for enactment. For containment, recover the local relation’s participant meanings, applicability and obtaining condition, then check its factual conditions on the complete candidate occurrence, including the declared System delimitation and qualification window. The Work participant’s kind is established by the admission judgement that follows.
When all required admission premises are grounded, admit that same occurrence as W : U.Work. For each typed assertion, combine that membership with the other participant’s independently admitted kind and the previously checked facts required by its predicate. These grounds support enactsMethod(W, M) and the declared containing-System relation. Keep each claim tied to the occurrence, participants, extent and qualifications whose facts were checked.
If a required fact is unresolved, retain the supported claims and leave the dependent Work-admission conclusion unresolved. If the facts establish that a required condition fails, that proposed admission basis fails. A missing containment rule returns missing-governor[work-containment]; missing evidence for an available rule instead leaves its factual test unresolved. Facts satisfying another declared containment rule may supply the containment premise. A.6.REL governs the resulting relation assertions and any later need to distinguish their occurrences.
Worked admission case. In a constructed variation of the entry’s Robot-7 example, retain the same occurrence’s established A.1:4.2 construction, performer basis, inspection history, TurbineInspectionMethod and 09:00–09:20 extent. Let Cell-3 be an independently admitted System. The local predicate workOccursWithinCellBoundary(work, system) requires the complete performed occurrence to lie inside that System’s declared physical boundary throughout the relevant window. The checked inspection history places all performed content inside Cell-3’s boundary during 09:00–09:20. Together with the other admission premises, this supports InspectionWork-17 : U.Work; the same history and participant identities support enactsMethod(InspectionWork-17, TurbineInspectionMethod) and workOccursWithinCellBoundary(InspectionWork-17, Cell-3). If the 09:10–09:15 location history is missing, this containment basis remains unresolved. If it shows inspection outside Cell-3, this particular containment claim fails; facts satisfying the containment rule for another independently admitted System may still supply the required premise. In either variation, retain the inspection facts already established and return to the missing or failed premise.
Use records for the claims they support. Identify the candidate action and the claim supported by each source, using the A.2.4 evidence-use relation or the A.10 evidence-provenance account required by that use. A trace linked to the Robot-7 inspection can support its 09:00–09:20 interval while other sources establish the performer’s A.13 basis, Method followed and containment. Work admission requires all the §4.0–4.1 premises to be grounded across the sources used. If only the interval is supported, retain that timing claim and leave Work admission unresolved. For an already admitted Work, evidence for a later claim about its interval need not repeat the admission evidence; keep the admission basis recoverable.
Elsewhere in FPF, a complete A.13/A.15.1/F.6 basis is the combined post-admission basis used only when a receiving claim needs both admitted Work and precise assignment-bound performer attribution. Its order is fixed: section 4.0 supplies the A.13 core and evidence for every performer; A.15.1 independently admits one dated Work occurrence with at least one obtaining enactsMethod relation, its temporal extent, and at least one obtaining locally declared Work-to-System relation whose stated boundary contains the complete occurrence; only then does F.6 test the link through the same covering A.13 assignment occurrence for every precisely attributed performer. This combined basis is not the A.15.1 admission test. A missing F.6 link alone leaves W : U.Work intact and the exact assignment-bound attribution unresolved. Add an A.13 characteristic profile only when the receiving claim consumes a Grade, autonomy or profile result, a criterion-dependent characteristic, or an assurance result.
A failed F.6 test alone leaves independent Work admission intact. If the same finding also invalidates a premise consumed by the A.13 or A.15.1 admission, recheck that premise and its dependent conclusions. Preserve independently grounded history and relations; an unresolved attribution is neither proof of no performance nor proof of success.
The canonical F.6 relation performedUnderAssignment(W, RA) is checked only after W is admitted and attributes that Work occurrence to one assignment occurrence. For an obtaining attribution, its attribution-facing holder projection is S = attributedPerformerSystem(W, RA) = RA.HolderSystemSlot; this projection does not discover S, and the direct case fact must establish that the System already recovered through A.13 performed W under RA. The assignment must also cover the attributed extent. In practitioner prose name both objects: S performed W under RA. If the relation is unresolved, retain independently grounded Work and do not assert that sentence; apply the preceding premise-recheck rule if needed. The legacy spelling performedBy(W, RA) is a deprecated compatibility alias only; do not author new claims with it, and never say that RA performed W.
One or more enactsMethod relations connect the Work individual to the U.Method values actually enacted. At least one locally declared Work-to-System relation locates the complete occurrence under an exact containing-system boundary; several may obtain under different valid boundaries. Direct work-to-referent, binding, and performed resource-use relations are recovered independently only when they obtain and the current claim needs them. An occurrence designator permits reference but does not identify work by label, ticket, trace, record, or storage convention; an assertion or description about the occurrence is a separate U.Episteme.
The actual enactsMethod relation obtains between the Work occurrence and the exact U.Method; it is not a field of either participant. An exact U.MethodDescription may be cited when its claims identify, constrain, or justify that method for the receiving use; the description is not enacted and its fields do not become actual work bindings. A selected model-use structure likewise enters only through the exact receiving relation whose interpretation it changes.
Call a selected MethodDescription, continuity policy or criterion a later edition only when the C.2.1 EpistemeEditionRelation to the earlier episteme is established. Otherwise identify the separate episteme and leave that continuity claim open. A replacement use and a negative continuity claim each need their own basis; missing evidence for an edition establishes neither.
A.15.1:4.1a - Direct Work relations used by this pattern
These relations are world-side facts, not fields stored in Work. Before asserting an A.15.1-owned relation below, independently admit both participants under the stated kinds. For a Work participant, use the candidate-facts-to-claims route in §4.1. The exact relation kind plus the ordered participant pair identifies the relation occurrence for ordinary use; if a later claim must distinguish its history or compare two occurrences, use A.6.REL. A changed participant pair identifies another occurrence. State a relation only when its predicate passes.
| Relation and participant order | When it obtains and where it applies | Identity, multiplicity, and boundary |
|---|---|---|
enactsMethod(work, method) with <U.Work, U.Method> | The performed occurrence actually follows that exact way of doing over the stated Work extent or an explicitly named performed part. A plan, MethodDescription, label, or intended use does not establish it. | Identity is this relation kind plus the ordered Work–Method pair. Every Work enacts at least one Method. Several may obtain when each Method is actually enacted and its covered extent or performed part is stated. |
TemporalPartOf_work(part, whole) with <U.Work, U.Work> | The first Work is a proper temporal sub-occurrence of the second: its exact extent is strictly inside the whole’s extent and all of its performed content belongs to that same occurrence history. It applies only when the slice is itself useful as an independently admitted Work individual. | Identity is this relation kind plus the ordered part–whole pair. A part may belong to several larger Work occurrences when the predicate passes for each; no unique parent is assumed. An interval, telemetry segment, or record is not thereby a Work part. |
EpisodeOf_work(episode, whole) with <U.Work, U.Work> | The first Work is an independently admitted event-bounded sub-occurrence of the second. Actual start and end events and the performed content must establish both the episode boundary and its inclusion in the whole. A named use selects which already grounded episode matters. | Identity is this relation kind plus the ordered episode–whole pair. Several episodes and several larger wholes are allowed when each predicate passes. If boundary facts permit more than one grouping, apply the cited continuity-policy episteme’s criterion to those facts to support the assertion. The relation participants remain the episode and whole Work. |
OperationalPartOf_work(part, whole) with <U.Work, U.Work> | The first Work is an independently admitted performed sub-occurrence whose performed content is a constitutive part of the whole occurrence at the stated operational grain. Mere overlap, a Method factor, schedule row, interval, or result label does not establish it. | Identity is this relation kind plus the ordered part–whole pair. Several parts and several containing Work occurrences are allowed when each predicate passes. State any Method-factor relation separately. |
To recover these connections in practice, B.1.5.EW starts with an action and asks what encompassing work is under way through it. Adding a value can be part of computing a total while report preparation is ongoing. This does not make the report complete, create a separate occurrence for every description, or count the same resource use several times. Independently claimed Work parts still satisfy the predicates above.
Containing Systems. Current assertions do not use bare executedWithin. Declare a direct local predicate such as workOccursWithinPlantBoundary(work, system) with participant order <U.Work, U.System>. Its predicate must say which exact system delimitation and qualification window make the complete Work occurrence lie within that System for the stated use, and must route that delimitation to A.1, A.14, or the applicable domain pattern. Its ordinary occurrence identity is the exact local relation kind plus the ordered Work–System pair. The §4.1 admission test first establishes the required containment facts; the admitted Work account states at least one such obtaining relation.
The same Work may stand in several true containing-System relations at different valid boundaries; no universal uniqueness or automatic “immediate” System is assumed. A part relation between Systems, organizational accountability, colocation, or a diagram does not by itself establish another Work-containment relation.
If no applicable local containment predicate is declared, return missing-governor[work-containment]. With a declared predicate, use §4.1 to distinguish missing factual support from a failed condition and to test another available containment basis. Historical executedWithin is only a route cue to recover this local relation; do not author a new current claim with it.
Retries and resumptions. Bare retryOf and resumptionOf are likewise route cues, not complete universal relation names. A domain that needs either relation declares a local two-participant species over <U.Work, U.Work>. A retry predicate states which earlier Work ended without satisfying which independently named completion condition, which target remains current, and which facts make the later Work another attempt rather than mere repetition. A resumption predicate states the earlier unfinished Work, the interruption boundary, and the direct continuity facts that make the later Work continue it rather than start another attempt. For either species, the exact local relation kind plus its ordered later–earlier pair identifies the ordinary occurrence; the declaration states applicability and whether more than one predecessor is allowed. A repeated label, shared Method, or temporal adjacency establishes neither relation. A continuity-policy episteme may support an ambiguous judgment but is not a participant and cannot replace the local predicate.
When a Work use needs overlap, precedence, containment, or another interval relation, use C.27.TA to name the temporal bearer, reference, intervals, direct temporal predicate, and the use that needs it; use B.1.4 only when those already recovered relations are aggregated. These declarations also do not replace F.6 performedUnderAssignment or a domain-specific Work-to-referent predicate. A consumer names the relation and participants rather than citing “the Work record.”
If the receiving sentence says that a referent changed, identify one exact U.Transformation independently under A.3.4. If a declared domain predicate relates exact Work W and transformation T, name that predicate, its participant order, and the facts that make it obtain. If no one direct predicate suffices but a one-case compound claim does, use A.6.RCD disposition 2 only when the substrate-admitted constructor, governed base predicates, actual participants, and case facts are recoverable; the result is C.2.1 claim content, not a relation kind or occurrence. Otherwise retain W and T separately and return missing-governor[work-to-change], or A.6.RCD’s missing-substrate result when the proposed constructor itself has no current semantics. Shared time, referent, or wording does not establish that Work-to-change claim. A morphism, delta expression, state-plane trace, pre-state, or post-state may represent or support the neighboring change claim; none is a Work field or identity discriminator.
Memory aid: Work = “how it went this time” (dated, resourced, attributable).
A.15.1:4.2 - Core occurrence references and neighboring links
When current Work also uses live steering. One current Work occurrence may enact both its domain Method and the A.15.7 steering Method, but only if each enactsMethod relation is independently grounded. Merely consulting the pattern or a MethodDescription, or admitting the steering Method as a submethod of a composite Method, proves neither enactment. The next-action answer says what should happen next. Treat choosing as a smaller Work occurrence only when its own A.15.1 basis and its relation to the larger Work are both needed and grounded.
When a separate assertion or description episteme describes one Work occurrence, recover the following content at the granularity required by the current use. Each item names an occurrence designator, a world-side relation or temporal fact, or a reference to another episteme; the list is not a slot or field schema for the Work individual:
- Occurrence and extent — one occurrence designator plus exact start and end, or an explicitly open end for in-flight work; add location only when the work claim depends on it.
- Performer System and agency basis — for admission, name every actual performer
U.Systemand its A.13 core, including the obtaining assignment for the action, scope, situation, and window. After Work admission, use F.6 only when the receiving claim needs the exact assignment under which that System performed the Work; keep the declared species, holder, other participants, and coverage recoverable. - Enacted method — actual
enactsMethod -> U.Method. CitemethodDescriptionRef -> U.MethodDescriptiononly when the receiving claim depends on that exact description episteme; the description is not enacted. - Containing Systems — name at least one locally declared Work-to-System predicate, its actual Work and
U.Systemparticipants, and the exact system boundary and qualification window that make it obtain. Name several when different valid boundaries matter to the receiving use. A System’s part relation to a larger holon does not by itself establish another Work-containment relation. - Work-to-referent relation used by the claim — name the declared domain predicate, its participant order, and the actual Work and referent participants only when that predicate obtains and the receiving claim uses it. “Work on X”, shared timing, a record mention, or a convenient
affectedfield establishes no such relation. If the use needs the relation but no predicate governs it, keep the Work and referent and returnmissing-governor[work-to-referent]. An obtaining work-to-referent fact does not by itself assert change, production, delivery, or acceptance. - Actual participation and bindings — for an operation argument or result, name one identified A.6.1 application and its exact declaration-local binding. For another participant, parameter, supplied constituent, premise, or reference use, name the declared subject predicate, participant order, and actual values. If the required route is absent, name the missing relation or binding in the
missing-governorresult rather than asserting it. A MethodDescription field, plan row, type-compatible value, or log token establishes none of them. - Performed resource use — name the declared resource-use predicate and its actual Work, resource, amount, unit, and extent participants at the boundary needed by costing or sustainability use. If no predicate governs the needed use, return
missing-governor[resource-use]; do not infer use from colocation, timing, or a plan estimate. - Continuity policy for an unresolved segmentation — when a named identity, episode, retry, resumption, or aggregation use has more than one defensible segmentation, cite
workContinuityPolicyRefto the exact C.2.1 episteme whose claims state the branch criterion and tolerances for that use, and interpret those claims under its effective reference scheme. If the criterion or its applicability cannot be recovered, leave that segmentation unresolved. The episteme is aU.MethodDescriptiononly if it independently satisfies A.3.2’s method-description criterion. A simple uninterrupted occurrence needs no continuity-policy reference; use the policy to judge the ambiguous segmentation against the performance history. - Work mereology and temporal relations — exact parent, part, predecessor, successor, overlap, retry, or resumption relations only when their predicates obtain.
- Actual change and production claims — identify each actual transformation independently under A.3.4; connect it to Work only through a declared domain predicate with its exact Work and transformation participants or a filled A.6.RCD disposition-2 claim with recoverable constructor, base predicates, participants, and case facts. Otherwise return
missing-governor[work-to-change]. Keep the current A.15.PROD production-work, entity-identity-inception, and production-completion claims separate. None follows from work identity or parthood. - Evaluation and downstream claims — use the one matching §4.6 row for evaluation work and result, evidence use, delivery or transfer, and acceptance; omit every row that is not current.
- Evidence, publication, and model use — cite only the exact evidence-use, publication-use, currentness, claim-scope, reference-plane, bridge, or selected model-use relation needed by the receiving claim.
Capability for a required contribution. When a capability condition matters to a Work claim or receiving decision, recover the contribution it requires and the holder to which it applies. Under A.2.2, compare that holder’s qualified ability with the Method-side demand for the work interval or declared checkpoints; reuse an adequate current fit. A collective ability claim concerns the independently identified System in its stated configuration. Conditions on individual contributions apply to the corresponding performers. A condition imposed on every performer still requires every performer to satisfy it. When performance depends on help or coordination, retain those conditions and the evidence for the combined contribution.
Report the fit, mismatch or named unresolved premise; stop when that answer suffices for the receiving decision. If a selected continuation still requires a positive fit, obtain the missing basis or arrange a permitted way to supply the required contribution, as the unresolved premise or failed test warrants; recheck the affected fit after any selected action. Before entry, use A.15.5’s actual readiness criterion, including any allowed gap. During Work, use A.15.7 to choose a supported continuation or stop under the domain Method. When loss or replacement of a performer or support makes the configuration uncertain, A.15.8 identifies and tests the relation to repair. Preserve independently grounded performance history, and recheck any Work-admission premise that the finding also challenges.
Example. The department in A.2.2:6.3 can close books for eight legal entities under IFRS with ERP v12, at least six qualified staff and a duration below five business days. In a constructed variation, reconciliation and consolidation are assigned to different performers, and the Method requires each performer to detect duplicate entries. Compare each performer’s qualified ability with its contribution’s requirement and with the Method’s shared duplicate-detection condition. Losing the sole consolidation specialist leaves that contribution unsupported even if reconciliation is finished. Recover qualified support or revise the continuation under the Method’s limits, and recheck the affected individual and department-level claims.
A.15.1:4.3 - Clear distinctions in a Work claim
| You are pointing at… | The right FPF concept | Litmus |
|---|---|---|
| A claim-bearing episteme expressed through a recipe, code artifact, or diagram and substantively about one admitted method | U.MethodDescription | Does the same episteme meet A.3.2’s membership threshold? Otherwise retain the claim-bearing episteme and any representation, publication, or formal-substrate object independently identified by its own pattern; do not call the episteme a MethodDescription. |
| The semantic “way of doing” | U.Method | Does the referent meet A.3.1’s conditions for a reusable way of doing under stated applicability? When comparing descriptions or notations, test semantic identity under A.3.1:4.7. |
| The assignment (which admitted System is assigned under which local system-role kind in this case) | one obtaining occurrence of one directly declared species under U.SystemRoleAssignment | Does the direct A.2.1 species’ assignment predicate obtain for its actual participants, including the admitted holder System and an assigned kind from that species’ declared domain? Identify the occurrence under A.2.1:4.3. |
| The ability (“can do within bounds”) | Qualified holder ability (A.2.2) | Does the claim state what an independently admitted holder System can do or produce, under which conditions and attained bounds, with the support and currentness required by A.2.2 for this use? |
| The dated occurrence with logs and resource-use evidence | One Work individual admitted under U.Work | Does the occurrence satisfy the full §4.1 test, including its A.1:4.2 construction, actual action during the stated extent, every actual performer’s A.13 core, at least one Method actually followed, and containment under at least one declared local rule? If precise assignment-bound attribution is also claimed, does a separate F.6 relation obtain for the already admitted Work? Are any claimed binding, work-to-referent, or resource-use facts independently obtaining? |
| The actual state change associated with this occurrence | U.Transformation plus a named domain predicate, or a C.2.1 local compound claim under A.6.RCD disposition 2 | Is the change independently grounded under A.3.4? Does the direct predicate obtain for exact W and T, or does the local claim expose its constructor, governed bases, participants, and case facts? If neither route is present, retain both objects and return missing-governor[work-to-change]. |
A.15.1:4.4 - Publication-use boundary for U.Work
A publication about one Work occurrence projects claims from an already declared assertion or description episteme. Preserve the source’s evidence basis and qualifications for the claims used from the publication. A completion-looking dashboard requires the same occurrence evidence as any other claim that the work happened.
Preparation is classifiable as one Work individual under U.Work only after it actually occurs and, under the full §4.1 test, its A.1:4.2 construction, its performer’s A.13 basis, at least one enacted Method, temporal extent, and at least one obtaining locally declared Work-to-System containment relation are independently grounded. After that admission, establish the covering assignment’s F.6 attribution separately only when the receiving preparation claim needs precise assignment-bound performer attribution. Add a Work-to-referent, binding, or resource-use fact only through its own obtaining relation when the receiving claim needs it. WorkEntryReadiness@Context under A.15.5 asks whether intended Work is ready to enter a Work boundary; a readiness label, full-kit checklist, or launch-looking cue is not a performed occurrence.
| Publication-use pressure | Work-local rule |
|---|---|
| PlainView, TechCard, InteropCard, or AssuranceLane presents work material | Project the claims and work-occurrence references used by that view. For an occurrence presented as admitted Work, keep its full §4.1 admission basis recoverable: its A.1:4.2 construction, independently grounded performance history, temporal extent, every actual performer System and its A.13 basis, enacted Method, and at least one obtaining local containing-system relation. Keep the assignment and F.6 attribution recoverable when the receiving claim uses their identity, and any separately established binding, resource-use, or Work-to-referent relation on which the view relies. Following E.17, provide an accessible source return or carry the source-attributed content needed for use without that access. A narrower view may expose only its selected claim and supporting references. Project a neighboring result, change, production, delivery, evidence, or judgment through its matching §4.6 row. |
| a numerical observation, comparison, aggregation, or benchmark result is published | State what the value describes and retain the source basis needed to interpret it. Use C.16 for measurement, A.19.CPM and its CG-Spec for comparison, and B.1.4 or B.1.6 for temporal or resource aggregation. Preserve the selected operation’s rule, material editions and any required conversion or reference-plane relation. Make any scalarization explicit. |
| publication cites method-description, work-plan, or cross-context material | Keep the Work occurrence as the dated performed individual admitted under U.Work. Cite the exact selected method-description or work-plan episteme. For a semantic crossing, cite an obtaining F.9 Bridge between two exact SchemeSenseCell values and state the proposed action, direction, correspondence rule, and tolerated loss in a separate bounded-use claim. Cite a UTS, reference-plane, or edition relation only when its own predicate obtains. |
| reconstructed records look like a performed occurrence | Distinguish what the records establish from what remains unresolved. Cite an occurrence as admitted Work only when its complete occurrence basis is grounded; a reconstruction that supports only a narrower claim remains usable for that claim. |
Publication example. A report of 12 kWh consumed by one stated Work occurrence keeps its C.16 measurement basis recoverable. Reporting a total for two occurrences adds the B.1.6 inclusion and shared-use policy. Saying that one run consumed less than another adds the A.19.CPM comparison basis. Each publication carries the source content needed to interpret its own claim, through E.17’s accessible source return or source-attributed content.
A.15.1:4.5 - Crossing visibility for work publications
When a work publication relies on another selected method-description episteme, name that episteme and the relation the publication actually uses; do not infer an edition from a version label or later date. For a semantic crossing, name the two F.17 sense cells and test the F.9 Bridge predicate profile, then state the proposed action, direction, rule, and tolerated loss in a separate C.2.1 bounded-use claim. For a reference-scheme, claim-scope, model-use, reference-plane, unit, or publication change, cite the direct relation that the publication actually uses. State ordinary evidence reliance through the applicable A.10 account of independently established evidence-use relations, including the same-use RelianceDisposition required by F.9:4.2 for reliance on an affirmative Bridge-use claim. Add a B.3 assurance result only when an actual named assurance claim is current.
When a Work assessment applies a penalty, cite the applicable rule, the conditions under which it applies, and the assessment value it changes. For a calculated adjustment, retain the value’s bearer, characteristic, scale and applicable unit, the required calibration or calculation, and the resulting value. Use B.3:4.3–4.4 when an assurance argument consumes that calculation. If its required rule or calibration is unavailable, report the available inputs and leave the adjustment unresolved. These assessments concern the same independently admitted Work occurrence.
A claim that a planned, gate-selected, or launch-labelled value was actually used requires a named direct predicate with its actual participants to obtain, or an exact A.6.1 operation-application binding to connect one identified application to that value. If the required predicate or binding rule is undefined, keep the planned designation and return missing-governor[actual-use]. If the rule exists but its positive test fails or lacks a deciding fact, keep the planned designation and return factually unsupported or missing-information, respectively. Do not back-fill a plan or infer an actual binding from shared wording. Pre-state and post-state references remain with an independently governed transformation or comparison claim; bracketing the Work interval does not bind them to the occurrence.
A.15.1:4.6 - Route a result or consequence without folding it into Work
Start with the ordinary sentence the reader needs, then select exactly one row for each separate claim. The table is not a result record to fill.
| Reader’s sentence | What to identify | Stop / non-inference |
|---|---|---|
| This work happened. | A.15.1: W : U.Work, every actual performer’s A.13 basis, independently grounded performance history, enacted Method, extent, and at least one locally declared containing-system relation with its boundary | the presence or form of a log, plan, output or verdict does not establish W; inspect its evidence content. F.6 alone is not the admission basis |
| S performed W under RA. | F.6 after Work admission: the same obtaining A.13 assignment, declared species and participants, direct case fact for the exact pair, holder equality, and interval coverage | a covering assignment or admitted Work alone does not establish performedUnderAssignment |
| The application returned X or X is a result of W. | for an application return, the exact A.6.1 application and result binding; for a Work-to-result claim, its already declared domain predicate, exact W and X participants, and obtaining facts. If the required Work-to-result predicate is absent, retain any independently established application binding and return missing-governor[work-to-result]. Use A.6.P.WMR when the source wording hides which route is intended | a result binding is not production, delivery, acceptance, or a universal work-result relation |
| This referent changed through W. | A.3.4: one exact U.Transformation; then name the declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with its substrate-admitted constructor, governed base predicates, actual participants, and case facts. Without either, return missing-governor[work-to-change] and keep W and T separately usable | temporal overlap, a delta picture, or common referent does not connect the change to W |
| W produced X, X first existed through changes attributed to W, or production completed. | the one current A.15.PROD branch: production-work participation, entity-identity inception, or production completion, each with its own criterion and boundary | one branch establishes neither of the other two nor delivery or acceptance |
| Evaluation found V. | identify the evaluation application and result binding or direct evaluation-result relation. Admit a separate evaluation U.Work only when that dated occurrence is claimed; identify a C.2.1 evaluation-result episteme when the result content needs its own reference | a performed evaluation, returned value and result episteme remain different objects; a value claim alone requires no additional Work identity |
| These observations support the claim. | A.10 account of the independently established evidence-provenance relations supporting the named claim, or A.2.4 for the lighter episteme evidence-use relation | identify the claim supported and the bounded use; a Work-admission conclusion requires the complete §4.0–4.1 basis across the sources used |
| X was delivered or transferred. | name the declared delivery or transfer predicate, its exact source, destination, transferred X, and any required occurrence or interval participants. Use A.2.3 for a separately current promise-content claim; if no delivery or transfer predicate governs the claimed transfer, return missing-governor[delivery-or-transfer] | production, a package, or a handoff label does not establish transfer |
| X was accepted. | name the criterion, verdict and declared acceptance predicate with its actual participants. Identify evaluation or acceptance Work separately when that occurrence claim is needed. Use A.2.3 only for a current promise-content claim; if no predicate governs the asserted acceptance, return missing-governor[acceptance] | delivery, a passing evaluation value or evidence alone does not establish acceptance |
Three-question result check. (1) Did the Work occur? Recover its §4.0–4.1 admission basis; add F.6 only for the separate assignment-bound claim. (2) What result or consequence is claimed? Identify the returned value, entity, change, production claim or transfer through its §4.6 row. (3) Who judged or accepted what, by which criterion and evidence? Keep the judgment, returned value, evidence and acceptance relation distinct; add a dated evaluation Work identity only when that claim is needed. Stop after the last current question.
A.15.1:5 - Work mereology (how occurrences form holarchies)
Work identity is occurrence-grounded and 4D. Start from the actual performance history: work-entry and end events, occupied spatiotemporal extent, actual performer Systems with their A.13 bases, enacted Methods, the locally declared containing-system relations needed by the use, any direct work-to-referent relations, actual bindings, resource use, and work-part or temporal relations. A separately asserted F.6 relation relates the Work to the obtaining assignment under which it was performed; it neither admits nor reidentifies the Work.
A.15.1:5.1 - Parts and wholes of Work (occurrence facts)
- Temporal-part (
TemporalPartOf_work). Both participants are independently admitted Work individuals. The first is a proper temporal sub-occurrence of the second under the §4.1a predicate, with its own exact extent and performed content. Use it when a later resource, evidence, KPI, acceptance, repair, or aggregation claim needs that Work part as an individual. A bare interval, telemetry window, or evidence slice stays a C.27.TA temporal aspect or its direct domain object; it is not the first participant ofTemporalPartOf_work. - Episode-part (
EpisodeOf_work). Both participants are independently admitted Work individuals. The first is an event-bounded performed sub-occurrence of the second under the §4.1a predicate. Entry, resumption, mode switch, switch-to-method, interruption, switch-away, completion, or a declared pause may supply candidate boundary events. Cite an exactworkContinuityPolicyRefonly when direct facts permit more than one grouping for the named use; timestamps, a policy, or an episode-looking label alone establish no episode relation.
workContinuityPolicyRef designates the C.2.1 episteme stating the named use, boundary events, tolerated variation and branch criterion. Interpret it under its effective reference scheme. Add claim scope, qualification window or model-use structure only when it changes the segmentation assertion. The policy supports classification of the existing history for that use; another policy can support a competing assertion. Apply §4.1’s edition rule: unestablished continuity remains unresolved, rather than becoming a negative continuity claim. A policy is a U.MethodDescription only after A.3.2 admission.
- Operational-part (
OperationalPartOf_work). A work-part occurrence that may enact a factor of a recoveredU.Method, for example, an incision occurrence within an appendectomy occurrence, possibly overlapping with others in time. If a method-description reference is used, it identifies, describes, constrains, or evidences that method factor; the referencedU.MethodDescriptionis not enacted. If noU.Methodfactor is recovered, retain the object actually identified; do not infer a Method factor from its label. - Concurrent work parts (derived use-side reading; no fourth parthood relation). First state each exact work-part relation to the same parent. Then use C.27.TA to state the exact temporal-overlap predicate, reference, intervals, and use. If a claim also says that the parts were coordinated, name its declared coordination predicate and actual participants. Shared parentage and overlap do not by themselves establish coordination, and
ConcurrentPartOf_workis not introduced as a primitive work-part relation.
Naming threshold. First identify the actual Work part under its occurrence and relation rules. Give it a stable name when a current or later use needs a distinct reference—for example for resources, evidence, KPI, acceptance, repair or aggregation. Otherwise retain the interval, evidence slice, telemetry or other object actually needed. A proposed new U-kind has its separate admission test.
Didactic rule: Method composition is not proof of Work decomposition, and Work decomposition is not proof of method composition. A temporal work part may enact the same whole method during a slice. An episode may continue one method or mode, span several operational parts, or repeat the same method fragment; an evidence policy may support a finer segmentation claim without changing method identity. An operational part may correspond to a method factor only when that factor is recovered as U.Method.
Quick choice test.
- Ask “do I need only an interval or aspect, or an independently admitted Work sub-occurrence?” Use C.27.TA or the direct temporal object for the first. Use
TemporalPartOf_workonly for the second, after its proper-sub-occurrence predicate passes. - Ask “does this named use need an event-bounded fragment of the parent?” If yes, recover the candidate boundary events. Cite
workContinuityPolicyRefonly when interruption, resumption, switch, replacement, or pause leaves the grouping ambiguous for that use; then useEpisodeOf_workonly when its direct predicate is satisfied. - For two independently admitted Work occurrences, ask “is the performed content of the proposed part a constitutive part of the whole occurrence at the stated operational grain?” Assert
OperationalPartOf_workwhen the §4.1a predicate holds. Use another Work-part relation only when its own predicate holds. When precise assignment-bound attribution is also current, check the separate F.6 relation only after admitting the sub-occurrence. - Ask “which way-of-doing part is being composed?” If the answer needs preconditions, effects, interface, and whole-method relation, recover a
U.Methodsubmethod underA.3.1andB.1.5; do not make the work part itself carry the method identity.
A.15.1:5.2 - Key relations among Work
Temporal order and overlap. A.15.1 supplies each Work occurrence and its exact extent. Use C.27.TA to name the temporal bearer, reference, exact intervals, direct temporal predicate, and use that needs it. A differently named predicate is used only when its own declaration gives the same participant meanings and law. Use B.1.4 after those temporal facts are recovered when the task asks for a roll-up.
Retry and resumption. Use only a locally declared retry or resumption species that passes §4.1a. Name that predicate and the actual later–earlier Work pair. Bare retryOf or resumptionOf wording is a prompt to recover the local relation, not a positive claim.
Causal use. If one Work occurrence is claimed to explain, trigger, or cause another, keep the Work-to-Work relation separate from the causal-use claim. Use C.28 or the pattern that defines and tests that causal use.
A.15.1:5.3 - Work-occurrence relations used by Part B roll-ups
A.15.1 supplies the identity of each independently identified Work occurrence or Work part and makes its exact temporal and performed resource-use relations recoverable. It does not itself return a temporal aggregate or resource ledger.
- Temporal coverage. When a receiving use needs utilization, elapsed time, phase coverage or another roll-up over Work intervals, apply
B.1.4to those intervals and the selected combining rule. Preserve the temporal inputs, coverage and overlap conditions consumed by that rule. An adequate ordinary account can state the result; use a separate record or optionalGamma_timenotation when the receiving use needs it. The Work intervals remain A.15.1 facts. - Resource aggregation. When a receiving use needs a total over performed resource values, apply
B.1.6to the attributed inputs, included subjects, accounting scope, time basis and operative rule. Preserve the value-attribution grounds and any overlap, allocation or deduplication conditions used by that account. An adequate statement or existing ledger can convey the result; a separate record and optionalGamma_worknotation are chosen by the receiving use. Each contributing performed resource-use relation obtains separately with its Work occurrence as a participant; an assertion about that relation remains distinct from the relation.
Manager’s tip: cite the B.1.4 or B.1.6 aggregation result and policy beside the KPI. A Work-part list, shared parent, or operator spelling supplies neither the aggregate nor its policy.
A.15.1:5.3a - Before A Timetable Becomes Architecture Evidence
A timetable, workflow row or architecture table can help locate candidate Work and may contain evidence. Its presence or layout alone establishes no Work occurrence, part, overlap or order. Before relying on its content in an architecture decision:
- identify each Work occurrence under the full §4.1 test from its A.1:4.2 construction, every actual performer’s A.13 basis, independently grounded performance history, enacted Method, actual interval, and an obtaining relation to a containing System; when precise assignment-bound attribution is current, apply F.6 separately after admission;
- if several rows are claimed as parts of one Work whole, identify that whole and every part independently, then state the exact Work-part relation that holds;
- if two occurrences are claimed to overlap or follow one another, state their actual intervals and the exact C.27.TA temporal relation; and
- state coordination, participation, resource use, result, or acceptance only through its own obtaining relation when the architecture decision needs it.
Two activities with similar names or one planned time window can still be distinct Work, and a schedule row may remain only plan content. If the actual occurrence or required relation is missing, preserve the plan, description, interval, or separately grounded Work that is available and stop the stronger architecture claim.
A.15.1:5.4 - Identity and reidentification of Work
Two descriptions, assertions, records, or traces resolve to the same Work occurrence only when they designate the same actual world-side performance history, not merely the same name, policy label, similar policy content, or later date. First compare the direct facts at the selected grain:
- the same actual work-entry or start and compatible occupied spatiotemporal extent;
- the same performance history, with each actual performer System’s A.13 basis, enacted Method, and the locally declared containing-system relations used by the identity claim, plus every obtaining work-to-referent, binding, and resource-use fact used by that claim, placed at the interval where it obtains; any separately asserted F.6 relation remains an attribution fact rather than a Work-identity discriminator;
- compatible work-part and temporal relations; and
- no fact that already identifies distinct individuals: a proper part versus its parent, independently grounded concurrent performances, or a later work-entry after the first occurrence’s established completion or termination.
A corrected or later description can refine the assertion about the same actual start, open end, or completed end. A change of performer, assignment, enacted Method, referent, binding, resource use, or obtaining containing-system relation during an otherwise unended performance history is an actual change to state explicitly; that change alone neither splits nor preserves the Work occurrence.
When a named receiving use must decide whether the performance history stays inside one parent, examine the direct facts first. If more than one grouping remains defensible, cite the exact continuity-policy episteme, its effective reference scheme, applicable scope and window, and the branch criterion it applies to those facts. The selected policy can support one identity or segmentation assertion for that use. A later or competing policy episteme may support another assertion; call it a later edition only when the C.2.1 EpistemeEditionRelation is established. Otherwise retain the separately identified policy and any supported replacement-use claim without inferring non-continuity.
A.15.1:5.5 - Interruptions, retries, resumptions, and description changes
- Established end and later entry: identify a later Work occurrence when the first occurrence has actually completed or terminated and another work-entry occurs. A larger composite Work may contain both only through explicit work-part relations.
- Retry: identify the later Work occurrence independently. Add a retry relation only through a locally declared species whose exact predicate connects it to the ended attempt and whose participant meanings, identity, cardinality, and applicability are stated; bare
retryOfremains only a route cue. - Ambiguous interruption or resumption: preserve the actual boundary events and facts. If a named use must decide same-parent versus separate-occurrence grouping, apply its exact
workContinuityPolicyRef; without that criterion, return an unresolved segmentation rather than making the policy implicit. - Performer, assignment, method, referent, binding, retune, or mode change: state the actual change where it occurs. Split or retain the parent only when the direct facts already decide the boundary or a policy current to the named identity, episode, retry, resumption, or aggregation use supplies the criterion.
- Method-description episteme change: record the newly selected description episteme separately. That selection neither splits nor preserves Work by itself; only an accompanying actual occurrence change enters the boundary judgment. Call the two descriptions editions only when their exact C.2.1
EpistemeEditionRelationobtains. - Rework: identify the later performance independently. Relate it as another occurrence, episode, or operational part only after the applicable direct predicate and any needed boundary policy are satisfied. Keep causal attribution with the governing causal-use pattern.
These rules answer Work-occurrence identity and segmentation. When the current question is instead whether exact performer, support, and continuation-state relations let the admitted occurrence continue or recover under interruption, handoff, or degraded support, use the actual-Work branch of A.15.8. It neither splits nor preserves the Work occurrence; return every identity, retry, or resumption claim here.
Plans, costs, quality statistics, telemetry evidence, and method-reliance claims may depend on whether the selected history is a temporal part, event-bounded episode, operational part, or later occurrence. Name a continuity-policy episteme, effective reference scheme, scope, and qualification window only when direct occurrence facts leave more than one defensible grouping for the current claim. When those facts already establish the needed grouping, use them directly.
A.15.1:5.6 - Work mereology does not compose effects or transformations
A parent Work can have work parts without having one composite effect or composite transformation. Any temporal aggregate uses B.1.4; any performed-resource aggregate uses B.1.6; each names its own concern, policy, evidence, and result. Identify every actual transformation independently under A.3.4. Connect one to Work only through a named domain predicate and exact participants, or a C.2.1 local compound claim under A.6.RCD disposition 2 with its constructor, governed bases, participants, and case facts recoverable; otherwise return missing-governor[work-to-change].
Work parthood, method parthood, temporal inclusion, a common affected referent, a list of changed characteristics, or adjacent plan items establishes neither transformation parthood nor a composite transformation. If a production or effect claim needs transformation composition, name the declared composition predicate, its participants, and the facts that make it obtain. If none is available, retain the Work and independently identified transformations and return missing-governor[transformation-composition]. A.15.PROD may still recover any independent production-work, entity-inception, or completion claim that does not depend on that missing composition.
A.15.1:6 - Archetypal grounding (parallel domains)
The following constructed cases use stipulated project facts and the full §4.1 admission premises, including the six common A.1:4.2 constructive components for every occurrence named as admitted Work. They illustrate Work admission and the separately grounded claims described here; they do not report observed practice. Each is presented as readable content of an assertion or description episteme. Arrow notation abbreviates the stated world-side relations; MethodDescription and policy references identify separate epistemes. The bullet layout declares no fields on Work.
A.15.1:6.0 - Work admission in two change cases
- Transformation with unresolved Work admission:
LunarTideRise-2026-07-27may be identified under A.3.4 as a Transformation of the exact water body over the stated interval. The supplied account leaves Work admission unresolved: it has not established an actual performerU.Systemwith an A.13 agency basis for the tidal action, a Method that the performer followed, or containment of the complete occurrence under a declared local Work-to-System rule. If Work recognition matters to the receiving use, return to the missing premises under the full §4.1 admission test. Keep any independently supported Transformation claim. - Self-directed Work: in this rehabilitation model, Person-7’s right-arm motor-control system stretches the left arm for five minutes. The current model admits
MotorControlRightArmSystem-7 : U.SystemandPerson-7 : U.System; A.14ComponentOf(MotorControlRightArmSystem-7, Person-7)andComponentOf(LeftArm-7, Person-7)obtain, so the mover and the affected limb are distinct parts of one person.SelfCarePerformerSystemRoleis a declared local agential kind for the stated stretch action; the case stipulates its target-relative membership criterion, classification ofMotorControlRightArmSystem-7under it, an obtainingSelfCarePerformerAssignment-7for the scope and window, and adequate evidence that the System satisfies that local criterion; this case makes no Grade or autonomy-profile claim.MotorControlRightArmSystem-7then performsLeftArmStretchWork-7from2026-07-27T07:30:00+03:00to2026-07-27T07:35:00+03:00under that assignment; F.6performedUnderAssignmentobtains and the Work enactsAssistedLeftArmStretchMethod-E1. Clinic relation specificationClinicRehabRelations@Clinic-E1declaresRehabWorkOccursWithinPersonBoundary@Clinic-E1(work, system)for the stated person delimitation and five-minute window, and the case facts make it obtain for that Work andPerson-7. The same specification declaresRehabWorkStretchesLimb@Clinic-E1(work, limb, interval), which obtains for that Work,LeftArm-7, and the five-minute interval. Separately, A.6.1 applicationAssistedStretchApplication-7binds its declaredAffectedLimbArgumenttoLeftArm-7. The first Work-to-limb fact and the operation binding remain different; neither is a primitive self-relation, and this case-specific decomposition is not a required anatomy for every self-directed action.
These branches test admitted facts, not human resemblance. A non-human or molecular-scale System can perform Work when its A.1 admission, A.13 local kind and criterion, classification, obtaining assignment for the scope, working situation, and window, evidence adequate for those core claims, exact performance history, actual enacted Method, extent, and containment facts under at least one declared local Work-to-System rule combine with the occurrence’s A.1:4.2 construction to satisfy the full §4.1 test; unfamiliar agency is not a reason to reject it. If a receiving use also claims the exact assignment under which that Work was performed, check F.6 separately after admission. Add an A.13 characteristic profile only for a Grade, autonomy or profile claim, a criterion-dependent characteristic, or a named assurance use.
A.15.1:6.1 - Surgical case (overlap and episodes)
OR_Team_A performs an appendectomy from 09:05 to 11:42 on 10 August 2025. Exploration overlaps monitoring, and a power dip interrupts performance for five minutes.
- Top work occurrence:
Appendectomy_Case_2025-08-10T0905_1142. - Actual method and containing-system relation:
enactsMethod -> Appendectomy@Hospital-2025;SurgicalWorkOccursWithinServiceBoundary@Hospital-8472(Appendectomy_Case_2025-08-10T0905_1142, SurgicalService_A)obtains under the service delimitation declared inSurgicalServiceWorkBoundaryRelations@Hospital-8472. - Patient and administered dose: project relation specification
MED-ADM-2026, owned byClinicalAdministrationRelations@Hospital-8472, declaresClinicalWorkAdministersDoseToPatient(dose, patient, clinicalWork, interval). The stipulated administration facts make it obtain forMedicineDose_8472,Patient_8472,Appendectomy_Case_2025-08-10T0905_1142, and the surgery interval. This relation establishes only that administration claim. The case names no admitted predicates for theatre, consumables, or staff-time resource use, so those optional claims returnmissing-governor[SURGERY-RESOURCE-USE]and do not enter Work identity. methodDescriptionRef:Appendectomy_v5, an episteme whose exact EntityOfConcern is admittedAppendectomy@Hospital-2025and whose substantive claims describe its operative steps under A.3.2.- A.13 Agent basis, performer System, and assignment:
SurgicalTeamSystemRoleis a declared local agential kind for coordinated operative action; its criterion requires goal-directed, condition-sensitive regulation of the stated surgical action, the case stipulates classification ofOR_Team_A : U.Systemunder it and adequate evidence for that local criterion and classification for the surgery scope and window; no Grade or autonomy-profile claim is used.SurgicalTeamAssignmentis the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings.OR_Team_A_SurgicalTeamAssignment_2025-08-10is the obtaining occurrence: its holder isOR_Team_A, its assigned kind isSurgicalTeamSystemRole, and its extent covers the surgery. The stated facts establish F.6performedUnderAssignmentfor this Work and that occurrence. - Operational parts:
Incision(09:15–09:22),Exploration(overlaps with monitoring),Closure(11:10–11:35). - Episode: a brief power dip occurs from 10:02 to 10:07. The named surgery-continuity use applies
HospitalWorkContinuityPolicy_2025, a C.2.1 policy episteme interpreted underHospital-Operating-Scheme-2025; the case stipulates that its pause-and-resumption criterion keeps both event-bounded fragments under the same parent Work. The power dip alone would not decide that grouping. - B.1.4 temporal roll-up:
SurgeryORUtilizationAggregation-8472uses union underORUtilizationUnionPolicy-2025;SurgeryPatientLeadTimeAggregation-8472uses hull underPatientLeadTimeHullPolicy-2025. Both consume the named surgery and part intervals; neither supplies a resource-use or acceptance relation. - B.1.6 resource roll-up: no positive aggregate is asserted in this case because the direct theatre-, consumables-, and staff-time resource-use predicates are absent. Preserve the Work and the administration relation and return
missing-governor[SURGERY-RESOURCE-USE]; open B.1.6 only after the project declares those predicates and supplies their actual participants and facts.
A.15.1:6.2 - ETL pipeline (parallelism and retries)
ETL_Runtime performs the nightly ETL from 01:00 to 01:47 on 11 August 2025. The two extractions run in parallel; Transform starts when either finishes, and a failed warehouse write is retried with a smaller batch.
- Top work occurrence:
ETL_Nightly_2025-08-11T01:00-01:47. - Actual method and containing-system relation:
enactsMethod -> Nightly_ETL_Load@DataOps-2025;ETLWorkOccursWithinPlatformBoundary@WarehousePlatform(ETL_Nightly_2025-08-11T01:00-01:47, DataPlatform_Prod)obtains under the platform delimitation declared inETLWorkBoundaryRelations@WarehousePlatform. - Dataset participation; resource stop: relation specification
ETL-DATA-REL-2025, owned byETLDataUseRelations@WarehousePlatform, declaresSourceDatasetParticipatesInETLWork(dataset, work, extent)andDestinationDatasetParticipatesInETLWork(dataset, work, extent). The stipulated job facts make the first obtain forRawOrders_2025-08-11,ETL_Nightly_2025-08-11T01:00-01:47, and its extent, and the second forWarehouseOrders_2025-08-11with the same Work and extent. Neither predicate means later analytics use or dataset transformation. The case names no direct cluster-time or storage-use predicate, so those optional claims returnmissing-governor[ETL-RESOURCE-USE]. - Actual change, no connection yet: A.3.4 identifies
WarehouseOrders_LoadTransformation_2025-08-11as the bounded change of the exact dated warehouse partition across 01:00–01:47 under the declared source-snapshot and partition-write conditions. Before that boundary the partition lacksAcceptedOrdersRowSet_2025-08-11; after it, the project data-state relation to that row set obtains. This case declares neither a direct W-to-T predicate nor a complete A.6.RCD disposition-2 claim with a constructor, governed base predicates, participants, and case facts, so it returnsmissing-governor[ETL-WORK-TO-CHANGE]. Keep the Work, transformation, and dataset-participation facts; shared time, destination label, and post-state do not connect W to T. - A.13 Agent basis, performer System, and assignment:
ETL_Runtimeis independently admitted as the exact running System.BatchExecutionControllerSystemRoleis a declared local agential kind whose membership criterion requires condition-sensitive regulation of the stated batch action against the batch completion and failure policy. The runtime’s scheduler, authoritative state, policy branches, retry/redirect behavior, and stop conditions support its classification under that local criterion at this grain; no Grade or autonomy-profile claim is used.TransformerRuntimeAssignmentis the direct assignment species;ETL_Runtime_TransformerAssignment_2025-08-11is the obtaining occurrence with holderETL_Runtime, assigned-kind valueBatchExecutionControllerSystemRole, and an extent covering the ETL interval. Actual trace facts then support the dated ETL action and Method enactment; F.6 relates that Work to the same assignment. Code, a model artifact, the assignment alone, or a successful output does not supply agency or Work. - Parallel parts:
Extract_A‖Extract_B;Transformstarts when either completes (overlap). - Retry:
WarehouseWriteAttempt-1ended at 01:36 without satisfyingWarehousePartitionWriteComplete@ETL-2025;WarehouseWriteAttempt-2then entered to satisfy that same condition for the same dated partition and source snapshot with a smaller batch. Local declarationETLRetryRelations@WarehousePlatformdefinesRetriesWarehousePartitionWrite(later, earlier)over<U.Work, U.Work>by exactly those facts and permits one immediate failed predecessor. The relation obtains for the two named attempts; a genericretryOftoken is not used. - B.1.4 temporal roll-up:
ETLSLACoverageAggregation-2025uses hull underETLSLAHullPolicy-2025;ETLClusterUtilizationAggregation-2025uses union underETLClusterUnionPolicy-2025. They consume the named Work-part intervals and do not establish dataset participation, resource use, or change. - B.1.6 resource roll-up: no compute or storage aggregate is asserted until the ETL project declares cluster-time and storage-use predicates and supplies the exact Work, resource, value, unit, and extent participants. Until then return
missing-governor[ETL-RESOURCE-USE]; the two dataset-participation relations remain valid.
A.15.1:6.3 - Thermodynamic cycle without a whole-rig performer shortcut
Carnot_Cycle_Run_2025-08-09T1300_1306 is a candidate Work designator, and Carnot_Cycle_Operation@ThermoLab is the proposed enacted Method. A state-plane trace can support thermodynamic state and Transformation claims, while a declared ThermoWorkOccursWithinRigBoundary@ThermoLab relation can locate an independently admitted Work occurrence inside LabRig_7.
The current case admits LabRig_7 as a System and supports its containment and thermodynamic participation, but it does not independently declare a local agential kind for the rig whole, classify the rig under it, establish an obtaining assignment, or supply evidence that the rig whole satisfies such a criterion for the proposed cycle action. Do not invent whole-rig initiation, redirection, or stop facts. Recover the actual performer System, its A.13 core, and the independently grounded occurrence, Method, extent, and containment facts before admitting the candidate as performed Work. Only after admission may a precise assignment-bound claim add F.6.
Until then, retain the supported System functioning, thermodynamic change, Method proposal, state-plane representation, and evidence claims. Lower only the unsupported Agent, performer, U.Work, and F.6 claims. A containing System, controlled apparatus, MethodDescription, or trace does not perform by being the locus or evidence of the cycle.
A.15.1:6.4 - Claim handling (episodes versus monitoring slices)
ClaimsTeam_A performs claim handling on 3 June 2026, with a 29-minute gap between initial review and resumed resolution. The one-hour callback criterion supports treating the resumed performance as an episode of the same Work; the fifteen-minute alternative supports treating it as a later occurrence.
- Top work occurrence:
ClaimHandling_Case_8142_2026-06-03. - Actual method and containing-system relation:
enactsMethod -> ClaimHandling@InsuranceOps-2026;ClaimWorkOccursWithinOperationsBoundary@InsuranceOps(ClaimHandling_Case_8142_2026-06-03, ClaimsOperations_A)obtains under the operations delimitation declared inClaimsWorkBoundaryRelations@InsuranceOps-2026. - Claim and resource stop: this case names
Claim_8142, handler-time intervals, andClaimsPlatform_A, but supplies no admitted Work-to-claim, handler-time-use, or case-system-time-use predicate. Keep the grounded claim-handling Work and returnmissing-governor[CLAIM-REFERENT-AND-RESOURCE-USE]for those optional relations. Callback and monitoring records remain neighboring evidence or telemetry, not occurrence constituents. methodDescriptionRef:Claims_Method_v7, an episteme whose exact EntityOfConcern is admittedClaimHandling@InsuranceOps-2026and whose substantive claims describe its handling procedure under A.3.2.- A.13 Agent basis, performer System, and assignment:
ClaimsHandlerSystemRoleis a declared local agential kind for claim-resolution action; its criterion requires goal-directed, condition-sensitive regulation of the stated handling action, the case stipulates classification ofClaimsTeam_A : U.Systemunder it and adequate evidence for that local criterion and classification for the claim scope and window; no Grade or autonomy-profile claim is used.ClaimsHandlerAssignmentis the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings.ClaimsTeam_A_HandlerAssignment_2026-06-03is the obtaining occurrence: its holder isClaimsTeam_A, its assigned kind isClaimsHandlerSystemRole, and its extent covers the claims Work. The stated facts establish F.6performedUnderAssignmentfor this Work and that occurrence. - Episode policy:
InitialReviewEpisodeWork-8142andResumedResolutionEpisodeWork-8142are first independently admitted as Work individuals with their own A.13-qualified actual performers, performance histories, enacted Methods, extents, and containing-System relations. Any precise assignment-bound attribution for either episode is checked separately through F.6 after admission. The named claims-handling continuity use then appliesClaimsWorkContinuityPolicy_v7, a C.2.1 policy episteme interpreted underClaims-Handling-Scheme-2026. Its stated under-one-hour callback criterion supports assertionClaimsSegmentation-v7-8142that the two named Work individuals stand inEpisodeOf_workrelations toClaimHandling_Case_8142_2026-06-03. The policy supports the ambiguous grouping. - Competing policy with unresolved edition continuity:
ClaimsWorkContinuityPolicy_15min-Alt, interpreted under the same reference scheme, states a fifteen-minute callback threshold. Applied to the same 29-minute gap, it supports assertionClaimsSegmentation-15min-8142that the resumed performance is a later Work occurrence rather than an episode under the first parent. The case establishes neither positive nor negative C.2.1 edition continuity between the two policies. The receiver can select the alternative for this use while retaining that uncertainty. Switching policy supports a different use-local segmentation judgment of the same interval history. A claim that it is a later edition requires C.2.1’s historical-continuation predicate to be established. - Temporal monitoring slice:
MonitoringSlice_09:15-09:20is a C.27.TA temporal aspect used for queue-latency evidence. It is not aTemporalPartOf_workparticipant or an episode. If a later use needs an independently admitted Work sub-occurrence with its own performed content and exact extent, identify that Work first and test the applicable §4.1a part predicate. - Method relation: under
ClaimsSegmentation-v7-8142, both episodes enact the same claim-handling method; underClaimsSegmentation-15min-8142, each of the two Work occurrences enacts that method. The segmentation choice changes neither enactment fact. The five-minute slice does not prove a submethod.
A.15.1:6.5 - Internal-combustion engine without cell-whole performerhood
EngineRun_Cell7_2026-06-03T1300_1330 is a candidate Work designator and FourStrokeEngineOperation@TestBench-2026 is the proposed Method. Engine_Cell7 may be an admitted containing System, and EngineUnderTest_7 may exhibit functioning, behaviour, causal participation, state change, and resource use under separately governed claims.
Those facts do not classify the cell whole or engine-under-test under a local agential kind. This case supplies no independent A.13 local-kind criterion, cell-whole classification, obtaining agential assignment, or evidence that the cell whole satisfies such a criterion. Recover the actual performer System, its A.13 core, and the independently grounded test action, Method, extent, and containment facts before admitting performed test Work. Only afterward may a precise assignment-bound attribution add F.6. If the admission basis is absent, keep the engine-cycle, telemetry, Method-factor, Transformation, and resource claims and leave the performer and Work unresolved.
Crank-angle intervals and one-second telemetry windows remain C.27.TA temporal aspects unless a receiving use first identifies an independently admitted performed Work sub-occurrence and the TemporalPartOf_work predicate passes. Intake, compression, combustion-expansion, and exhaust are Method factors only when A.3.1/B.1.5 establish their Method identities and whole-Method relation; physical strokes and traces do not become submethods or Work parts by label.
A.15.1:6.6 - Detector receiver: narrow control agency versus broad reception Work
Receiver_Rx42 is an admitted System whose components can function and interact with RF_TestSignal_42_2115. A named automatic-gain-control loop may support a narrow A.13 claim only if a local GainRegulationControllerSystemRole has an independent target-relative membership criterion, the exact controller System satisfies it, an assignment obtains for the relevant window, and evidence shows that the System satisfies that criterion; add a characteristic profile only if the receiving use consumes one. That narrow claim does not make the receiver whole an Agent for envelope detection, diagnosis, or a broader reception service.
Admit ReceiverReception_Rx42_2026-06-03T2115_2120 as Work only after the exact performer System, its complete A.13 basis, actual performance history, enactsMethod fact for EnvelopeDetection@RadioLab-2026, temporal extent, and containing-System relation independently pass A.15.1. Only after that admission may a precise assignment-bound claim add F.6. Otherwise retain receiver functioning, component behavior, waveform interaction, retuning trace, and Method proposal without a Work assertion.
A one-second reception slice remains a C.27.TA temporal aspect unless an independently admitted performed Work sub-occurrence and the direct part predicate are established. Tuning, rectification, smoothing, and acoustic output may be Method factors, component behaviors, mechanism material, evidence traces, or operational Work parts only under the pattern that defines the claimed relation; an AGC loop or detector component does not settle those identities.
A.15.1:6.7 - Classification work without result collapse
RecognitionEvaluator_A evaluates Pump_37 from 10:15 to 10:22 on 20 July 2026. The evaluation application returns unknown; the occurrence of evaluation and the candidate’s recognition judgment remain separate claims.
Pump37_RecognitionWork_2026-07-20T1015_1022 is one Work individual admitted under U.Work, with temporal extent 10:15–10:22. RecognitionEvaluatorAssignment is a directly declared species whose signature uses the local RecognitionEvaluatorSystemRole domain. The case stipulates RecognitionEvaluatorSystemRole as a declared local agential kind with an evaluation-action membership criterion, classification of RecognitionEvaluator_A under it, and adequate evidence that the System satisfies that local criterion for the scope and window; no Grade or autonomy-profile claim is used. Pump37_EvaluatorAssignment_2026-07-20 is its obtaining occurrence, with RecognitionEvaluator_A as holder and an extent covering the Work. F.6 performedUnderAssignment and enactsMethod(Pump37_RecognitionWork_2026-07-20T1015_1022, HolonRecognitionEvaluation@FPF) obtain. FPFRecognitionWorkBoundaryRelations declares RecognitionWorkOccursWithinServiceBoundary(work, system); under its stated service delimitation and 10:15–10:22 window, the relation obtains for this Work and FPF_Recognition_Service_A. A.6.1 application Pump37_RecognitionApplication_2026-07-20T1017 has obtaining candidateArgument -> Pump_37 and judgmentResult -> unknown bindings, so candidate participation and returned value need no generic affected-referent or Work-result relation. This case supplies no admitted evaluator-time or runner-compute resource-use predicate; return missing-governor[PUMP37-RESOURCE-USE] for those optional claims without lowering the Work or application bindings.
The returned unknown value remains the A.6.1 result binding. No U.Transformation of Pump_37 or of a classification record is asserted. This evaluation Work remains admitted under the full §4.1 test from its stipulated A.1:4.2 construction, the stated performer’s A.13 basis, independently grounded performance history, enacted Method, extent, and the obtaining service-boundary relation just stated; its covering assignment and F.6 attribution remain separate obtaining facts. The application binding is another separate fact, and the absent optional resource-use predicates do not lower the Work. No pre-state, post-state, or delta is needed. Candidate-side criterion satisfaction remains under A.1; evidence and assurance remain neighboring relations; and any materialized classification assertion or evaluation-result episteme remains under C.2.1.
A.15.1:6.7.1 - Filled result route: build, verify, transfer, accept
BuildRunner_A builds ReleaseBinary_12 during 09:00–09:12 on 21 July 2026 and populates ArtifactStorePartition_12. Separate verification takes place during 09:13–09:18. Its application returns pass, supported by checksums and test logs. The binary moves from ArtifactStorePartition_12 to StagingSystem_A; acceptance remains unresolved because the case supplies no acceptance predicate relating that verification verdict to the binary.
BuildRunnerAssignment is a directly declared species whose signature uses the local BuildRunnerSystemRole domain. The case takes as premises the declaration of BuildRunnerSystemRole as a local agential kind with a specified build-action membership criterion, classification of BuildRunner_A : U.System under it, and adequate evidence that the System satisfies that criterion for the scope and window; no Grade or autonomy-profile claim is used. BuildRunnerAssignment_2026-07-21 is its obtaining occurrence, with that System as holder and an extent covering 09:00–09:12. The stipulated A.1:4.2 construction, action history, enacted Method ReproducibleBuild@BuildOps-v12, extent, and containment facts under BuildWorkOccursWithinServiceBoundary for BuildService_A support the §4.1 admission of ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work. The separate F.6 test establishes attribution of that Work to the same assignment with BuildRunner_A as holder. Those facts establish distinct Work and attribution results.
The rows below add only the result and consequence claims that are current in this case. Every additional verification, evaluation, or acceptance Work named in a row needs its own A.15.1 admission basis; any precise assignment-bound attribution for it needs its own later F.6 check. It does not inherit BuildRunner_A or the build assignment.
| Current case claim | Object or relation | Kept separate from |
|---|---|---|
| build application returned the binary | A.6.1 application BuildApplication_12 of declared operation storeWrite@BuildOps-v12, with argument binding storeTarget -> ArtifactStorePartition_12 and result binding builtBinary -> ReleaseBinary_12 | entity inception, production completion, delivery, acceptance |
| subject practice also needs a direct result relation | case-local occurrence BuildRunReturnedBinary_12 under already declared predicate BuildRunReturnedBinary@BuildOps-v12, relating the build Work to ReleaseBinary_12; if that declaration were absent, this row would be omitted and the A.6.1 binding retained | a universal WorkResultRelation |
| the artifact-store partition changed | A.3.4 identifies ArtifactStorePopulationTransformation_12. BuildOps relation specification BuildOpsWorkChangeRelations-v12 declares the direct predicate BuildWorkPopulatedStore@BuildOps-v12(work, transformation) with participant order <work, transformation>. Its test requires the named Work to be the performed process that, through storeWrite@BuildOps-v12 application BuildApplication_12 and its storeTarget -> ArtifactStorePartition_12 binding, brings about the independently identified population transformation of that same partition. The stipulated Work, application, target binding, and transformation facts make the predicate obtain for ReleaseBinary12_BuildWork_2026-07-21T0900_0912 and ArtifactStorePopulationTransformation_12; C.2.1 assertion BuildWorkPopulatedStore-12 states that positive claim | the application remains an independently identified occurrence used by the predicate test; shared time, artifact label, or returned binary cannot establish the direct W-to-T claim |
| this was production, the binary first existed, and production completed | three separate A.15.PROD local claims: whole-production-work participation for the build Work; inception of ReleaseBinary_12 at 09:11 under ReleaseBinaryIdentitySpec_v12; completion at 09:12 under BuildCompletionCriterion_v12 | one omnibus production/result record |
verification returned pass | separate ReleaseBinary12_VerificationWork_2026-07-21T0913_0918 : U.Work, A.6.1 application VerifyApplication_12, result binding verdict -> pass, and C.2.1 episteme BinaryVerificationResult_12 when the verdict content needs its own reference | acceptance and the build Work’s result binding |
| checksums and test logs support that verdict claim | A.10 account citing evidence-provenance relation BinaryVerificationEvidenceUse_12, bounded to the verification claim and staging decision | truth by carrier presence or acceptance |
| the binary moved to staging | relation occurrence ArtifactTransferToStaging_12 under declared predicate ArtifactTransferredToStaging@BuildOps-v12, with participants ReleaseBinary_12 and StagingSystem_A, establishes transfer from the declaration’s fixed source ArtifactStorePartition_12 to that staging System | production, verification, acceptance |
| staging accepted the binary | StagingAcceptanceWork_12 and StagingAcceptanceCriterion_v12 are identified. VerifyApplication_12 returned pass through the binding verdict -> pass. This case declares no acceptance predicate relating that verification verdict to ReleaseBinary_12 under the criterion; return missing-governor[STAGING-ACCEPTANCE] and do not assert acceptance | transfer, evidence, or a bare pass value cannot fill the missing relation |
For a narrower report, keep only the rows its claims need and retain access to their grounds under §4.4.
A.15.1:6.8 - Bias-Annotation
| Bias | How A.15.1 prevents it |
|---|---|
| Plan-as-work bias | U.WorkPlan, schedules, method descriptions, and intended parameter bindings stay separate from the dated occurrence. |
| Log-as-work bias | Telemetry, dashboards, provenance rows, and work publications can evidence or describe a work occurrence; they do not become the occurrence. |
| Method-as-occurrence bias | U.Method and U.MethodDescription identify or describe the way of doing; an independently grounded assertion that one Work individual is admitted under U.Work designates the dated performed occurrence. |
| Evidence-as-authority bias | Evidence, assurance, gate, release, and causal-use claims keep their subject patterns and do not follow from a work record by appearance. |
| Record-handling-as-transformation bias | Copying, formatting, evaluating, or publishing records can be grounded as Work occurrences admitted under U.Work without an automatic change claim. Any claimed record or dataset transformation still needs independent A.3.4 identity plus a declared predicate with the exact Work and transformation participants, or a filled C.2.1 local compound claim under A.6.RCD disposition 2; otherwise return missing-governor[work-to-change]. |
A.15.1:7 - Scope Declaration and Rationale
- Applicability: Use the same occurrence test for pragmatic costing, architecture use, teaching examples, and source or evidence questions; when the current claim is only about a description, publication, source, or evidence relation, apply the direct pattern for that claim.
- Scope declaration: The occurrence head is universal. Temporal semantics use the declared temporal reference. A simple uninterrupted occurrence needs no continuity-policy episteme; identity, episode, retry, resumption, or aggregation claims cite
workContinuityPolicyRefand its effective reference scheme only when the named use must resolve an ambiguous boundary. Add claim scope, a qualification window, model-use structure, evidence use, or source-currentness assessment only when changing that neighboring fact would change the receiving assertion or reliance; otherwise omit it. - Rationale: Gives FPF a notion of occurrence with an A.13 agency basis for every actual performer
U.System, an independently grounded performance history, an obtainingenactsMethodrelation, temporal extent, and containment. When precise assignment-bound attribution is current, a separately checked F.6 relation uses the covering occurrence of the exact directly declaredU.SystemRoleAssignmentspecies. Costing, quality, and audit then rest on independently identified Work occurrences rather than plans, recipes, assignments made to act, or a generic role-enactment fact.
A.15.1:8 - Conformance Checklist (admission checks)
CC-A15.1-1 (Distinct objects).
U.Work is the admitted kind for dated performed Work occurrences. Each Work individual is world-side; it is not a U.Method (reusable way), U.MethodDescription (description), local system-role kind, System-classification judgment, U.SystemRoleAssignment (assignment), U.WorkPlan (plan or schedule), or assertion, record, log, or publication about Work.
CC-A15.1-2 (Required occurrence basis).
A conforming world-side Work account starts with one dated candidate action and every actual performer U.System with its A.13 local kind and criterion, classification, obtaining assignment, scope, working situation, and window, plus evidence adequate for those core claims and any characteristic profile conditionally consumed by the receiving use. Apply A.1:4.2 to the candidate occurrence’s construction and the full §4.1 test to its admission. It establishes that the action actually followed at least one Method, has a temporal extent, and lies inside at least one locally declared Work-to-System boundary; on that independent basis A.15.1 admits the occurrence under U.Work and states its owned relations. F.6 is not an admission condition. When the receiving claim also needs precise assignment-bound performer attribution, apply F.6 afterward to the already admitted Work and the same obtaining A.13 assignment. The account also names every declared Work-to-referent, participation, or resource-use predicate used by the receiving claim, or returns the missing governor instead of inventing a relation.
CC-A15.1-3 (Time window).
A conforming assertion or description about one Work occurrence designates a world-side individual with a closed temporal extent [t_start, t_end], or an explicitly open end while the occurrence is in flight. The episteme states or designates that extent and, where relevant, location or asset; neither an interval field nor the presence of the record creates the occurrence.
CC-A15.1-4 (Interpretation and policy basis).
A load-bearing work claim names direct occurrence facts first. It cites workContinuityPolicyRef, its effective reference scheme, and applicable scope or qualification window only when a named identity, episode, retry, resumption, or aggregation use must resolve an ambiguous segmentation. Any selected method-description episteme, aggregation-policy episteme, selected model-use structure, acceptance criterion, evaluation work, result episteme, and evidence use remains a neighboring claim rather than a work-identity field.
If two local senses must be related, F.9 receives two exact SchemeSenseCell endpoints and one BridgePredicateProfile; a Bridge is positive only when that profile’s predicate obtains. State the proposed comparison, substitution, translation, or publication separately in a C.2.1 bounded-use claim, with its action, direction, correspondence rule, and tolerated loss. State ordinary evidence reliance through the applicable A.10 account of independently established evidence-use relations, including the same-use RelianceDisposition required by F.9:4.2 for reliance on an affirmative Bridge-use claim. Add a B.3 assurance result only when an actual named assurance claim is current. A different reference scheme, system-role assignment, selected description episteme, or model-use structure alone establishes none of these facts.
CC-A15.1-4b (No mandatory state-plane or delta).
A Work claim needs no StatePlaneRef, pre-state, post-state, or delta merely to establish occurrence identity. If the receiving claim says that a referent changed, A.3.4 identifies the transformation and its state or boundary facts. Connect it to Work only through a declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with a recoverable constructor, governed base predicates, actual participants, and case facts; otherwise return missing-governor[work-to-change].
CC-A15.1-5 (SystemRoleAssignment interval coverage).
Every obtaining F.6 performedUnderAssignment(W, RA) attribution cites two assignment identities already recovered through A.2.1 and the performer’s A.13 core: the exact directly declared species and the same obtaining occurrence RA of that species. The species supplies the signature, participant meanings, predicate, and applicability. The occurrence supplies the actual participant values, including the holder System, and has an extent covering the Work or exact performed part. The holder equals the exact admitted U.System already recovered as actual performer through A.13. If holder equality or coverage fails, keep the Work occurrence, performer claim, assignment occurrence, and attribution separate; repair or reject the attribution, also rechecking any A.13 or A.15.1 admission premise that the same finding challenges. A retroactive occurrence may be established only under A.2.1’s exact rule for its directly declared species. F.6 discovers neither identity nor performer.
CC-A15.1-6 (Actual participant and operation binding).
For an operation argument or result, name one identified A.6.1 application and its exact declaration-local binding. For any other actual parameter, participant, premise, constituent, reference use, resource, or work-to-referent claim, name the declared subject predicate, participant order, and actual participant values. If the required route is absent, name the missing relation or binding in the missing-governor result and do not assert it. A MethodDescription declaration, default, A.15.3 planned filling, gate selection, compatible ValueKind, or stored token establishes no actual binding.
CC-A15.1-7 (Capability check).
Any capability threshold relied on for a Work occurrence is the declared bound in the selected Method-side claim. Test it by a named A.2.2 capability-fit predicate against the qualified ability of the holder named by that condition for the required contribution, for the work interval or declared checkpoints. Apply a collective condition to the collective holder, an individual condition to its performer, and a condition required of every performer to each performer, as explained in §4.2. Name the predicate, holder and ability claim, required contribution, threshold, work need and result. If the fit predicate is absent, return missing-governor[capability-fit] and assert neither fit nor failed fit. A U.Method or U.MethodDescription may cite or describe the threshold but creates neither capability nor fit. State a failed fit in its evaluation-result episteme or direct characteristic/evaluation relation, never as an intrinsic work outcome.
CC-A15.1-8 (Acceptance criteria).
An acceptance claim names the criterion episteme or comparator specification, applicable conditions, returned verdict and declared acceptance predicate with its actual participants. Identify the evaluation or acceptance Work when its occurrence is claimed; the verdict alone does not require an additional Work identity. A claim of historical criterion continuity needs the C.2.1 EpistemeEditionRelation; a version label is insufficient. If no predicate governs acceptance, return missing-governor[acceptance]. Success class, measurement, comparison result and acceptance verdict remain distinct; none is a Work field or a condition of Work membership.
CC-A15.1-9 (Resource attribution).
Performed resource-use facts (energy, materials, machine-time, money, tool wear) are attributed through declared predicates that name the particular Work, resource, amount, unit, and extent participants, not to U.Method, U.MethodDescription, a system-role kind or assignment, or an assertion of holder ability. If no predicate governs the needed performed-use claim, return missing-governor[resource-use]; keep any separately warranted estimates or derived values with their source values, model and conditions. Any aggregate ledger, unit conversion, allocation, or overlap and deduplication result belongs to B.1.6 and cites the contributing Work occurrences and resource-use facts.
CC-A15.1-10 (Mereology declared). When exact work-part relations obtain among Work individuals, declare each relation: temporal-part, episode-part, operational-part, or another relation with its own predicate. Ambiguous mixtures lower aggregation and identity claims. Each A.15.1 work-part relation uses two independently admitted Work participants and the predicate and identity rule in §4.1a. A bare interval stays with C.27.TA or its direct domain object. Concurrency adds a separately declared temporal-overlap claim through C.27.TA. If the reader also claims coordination, name its declared predicate and actual participants; overlap alone does not establish it.
CC-A15.1-11 (Temporal coverage selection).
For a temporal roll-up, B.1.4 identifies the participating Work occurrences, their intervals, temporal reference and time window, aggregation concern, selected combining rule, coverage and overlap conditions consumed by that rule, and admissible use. A.15.1 supplies the occurrence intervals but does not own the aggregate.
CC-A15.1-12 (Resource aggregation).
For a resource roll-up, B.1.6 identifies the contributing Work occurrences, typed resource values with applicable units and attribution grounds, accounting scope and time basis, aggregation rule and admissible use. Preserve the delimitation, overlap, allocation or deduplication conditions consumed by that account; an adequate statement or existing ledger can convey the result. A.15.1 supplies performed resource-use facts but does not own the aggregate.
CC-A15.1-13 (Identity and retries).
A distinct actual work-entry after an established completion or termination identifies a later Work occurrence; a proper work part and its parent and independently grounded concurrent performances are also distinct individuals. Add an EpisodeOf_work relation only when its §4.1a predicate holds. Add a retry or resumption relation only under a locally declared species whose participant meanings, predicate, identity, cardinality, and applicability pass §4.1a; bare retryOf and resumptionOf are route cues only. An interruption, performer or assignment replacement, method or mode switch, retune, rework, affected-referent change, or binding change is stated as direct history and neither splits nor preserves the parent by itself. Cite workContinuityPolicyRef only when a named use needs a branch criterion for that ambiguity. A changed MethodDescription or another policy episteme alone revises at most the dependent description or segmentation judgment. Call the policy an edition only when an exact C.2.1 EpistemeEditionRelation obtains; a non-continuing replacement can support a different judgment about the same performance history.
CC-A15.1-14 (Concurrency and ordering).
Overlaps and precedences among Work occurrences use C.27.TA with an exact temporal bearer, reference, intervals, and declared predicate. Implicit “step order” is not performed-work evidence.
CC-A15.1-15 (Cross-locality evaluation).
A work occurrence keeps one identity when several receiving uses evaluate it. Each use names the reference scheme, claim scope, criterion, qualification window and result basis it needs; a separate evaluation Work is identified only when that occurrence claim is current. When two local senses must be related, test the exact F.9 Bridge, then state the proposed comparison or substitution, direction, rule, and tolerated loss in a separate bounded-use claim and check reliance under A.10 or B.3. A shared work name, record, or Bridge carries no acceptance across uses.
CC-A15.1-16 (Method-description changes do not decide Work identity).
If the selected MethodDescription episteme changes during the occurrence, state the description-selection or override claim separately. That selection change alone neither splits nor preserves Work. When an accompanying actual performer-system, covering-assignment, enacted-method, binding, affected-referent, mode, or extent change creates a boundary question for a named use, first use the direct occurrence facts. Apply that use’s exact continuity-policy criterion only if those facts leave the grouping ambiguous. A later or competing policy episteme may support another judgment; it is a later edition only when its exact C.2.1 EpistemeEditionRelation to the earlier policy obtains. Otherwise retain the separately identified policy and leave edition continuity unresolved unless a negative result is independently established.
CC-A15.1-17 (Distributed performers).
If multiple admitted U.Systems jointly perform the same top-level Work occurrence, name every actual performer and recover its A.13 basis before A.15.1 admission. If precise assignment-bound attribution is current, use F.6 after admission to check the exact assignment for each System. If the use instead needs a parent Work with child occurrences, admit every child independently under the full §4.1 test from its own A.1:4.2 construction, performer basis, history, Method, extent, and containment, then add any needed F.6 attribution and Work-part relation. A lead, responsibility, or coordination claim remains separate and cannot substitute for the actual performer set.
CC-A15.1-18 (Evidence for the claim and complete Work-admission grounds). For logs and telemetry, identify the candidate action, the claim supported, and the applicable evidence-use relation under §4.6. One source may support only part of the occurrence account. To admit the occurrence as Work, ground the complete §4.1 basis across the sources relied on: its A.1:4.2 construction, performance history, every actual performer System with its A.13 basis, at least one Method actually followed, temporal extent, and at least one obtaining local Work-to-System containment relation. Keep that admission basis recoverable when a later source supports a narrower claim about admitted Work. When precise assignment-bound attribution is also current, support its separate F.6 assertion through the evidence relevant to that relation.
CC-A15.1-19 (Affected referent and work scope).
Each assertion or description about a Work occurrence designates the exact Work individual and states a direct work-to-referent relation only when the receiving use needs one. That relation must obtain independently; naming the referent in the episteme establishes neither actual change, production, delivery, acceptance, nor a universal affected relation. When the receiving use needs no such relation, omit it without lowering the Work occurrence.
CC-A15.1-20 (Actual change stays neighboring).
When the receiving claim needs actual change, identify an exact U.Transformation under A.3.4. Connect it to Work only through a declared domain predicate with exact W and T participants, or one C.2.1 local compound claim under A.6.RCD disposition 2 with a recoverable constructor, defined base predicates, actual participants, and case facts; otherwise retain both objects and return missing-governor[work-to-change]. Work can occur without a current transformation claim, and a no-op, evaluation, inspection, communication, or record-handling occurrence is not forced into a delta schema. The inverse also holds: an accompanying occurrence is admitted as Work only when every actual performer System has an A.13 basis and the exact performance history, enacted Method, temporal extent, and at least one obtaining local containing-system relation satisfy the full §4.1 test together with the occurrence’s A.1:4.2 construction. Any precise assignment-bound attribution is then checked separately through F.6. Do not invent an assignment for a causal participant, reject a non-human performer by resemblance, or collapse internal performer and affected positions into a primitive self-relation.
CC-A15.1-21 (Record handling remains Work without automatic transformation).
Copying, formatting, evaluating, or publishing records can be admitted as U.Work under the full §4.1 test, including the occurrence’s A.1:4.2 construction, when every actual performer System has an A.13 basis and the exact action history, at least one obtaining enactsMethod relation, extent, and at least one obtaining local containing-system relation are grounded. A precise assignment-bound attribution is a separate later F.6 result. State an affected referent, binding, or resource-use fact only through its independently obtaining relation when the receiving claim uses it. Identify any actual record or dataset transformation separately under A.3.4; a label, output record, or post-state picture does not establish it.
CC-A15.1-22 (Containing-System relation declared).
Each Work occurrence has at least one obtaining locally declared Work-to-System relation whose predicate names the exact system delimitation and qualification window that contain the complete occurrence. Name several when distinct valid boundaries matter; none is inferred from a System part relation, accountability, colocation, or a diagram. Keep every containing System distinct from the affected referent. If the receiving claim relates Work to that referent or to a Transformation, name the separate declared predicate, actual participants, and obtaining facts; containment and shared timing establish neither. Bare executedWithin is a historical route cue, not a current positive relation.
CC-A15.1-23 (No transformation composition from Work mereology).
Work parts support only their declared work-part facts and provide inputs to separately recovered B.1.4 or B.1.6 aggregation claims. They establish neither component transformations, transformation parthood, a composite transformation, nor a parent effect. Recover each actual transformation independently; when a production or effect claim needs unavailable transformation composition, return missing-governor[transformation-composition].
CC-A15.1-24 (No new claims on publication views).
MVPK views about Work project the declared assertion or description of the Work occurrence; they do not add properties or claims. For a displayed measurement or comparable value, name the Characteristic and the unit, scale, reference-plane and EditionId pins needed to interpret it under its source definition. Apply E.17’s PC-field requirements when its formal publication profile is selected. Use “signature” only for a signature under its defining pattern.
CC-A15.1-25 (No Gamma leakage).
Publication views cite exact B.1.4 temporal-aggregation or B.1.6 work-resource-aggregation results and policies when showing aggregates. An explanation of the calculation preserves the cited definition, policy, edition and qualifications; any defaults come from that declared basis. Optional Gamma notation remains with the recovered Part B aggregation claim. The view may carry the source-attributed explanation and references needed by its use.
CC-A15.1-26 (Input and output declarations on publication views). In E.17’s optional morphism profile, keep the signature-side declarations authoritative. Provide an accessible source return, or carry the needed source-attributed declarations and material pins when the face must support use without that access. A readable explanation may restate the source content needed by its use while preserving the source’s input and output declarations.
CC-A15.1-27 (Comparator ordering and return sets).
Across-occurrence comparison presented on a publication view about Work uses a declared ComparatorSet (map-then-compare), returns sets when order is partial, and rejects hidden scalarization or means that the ordinal Scale does not admit.
CC-A15.1-28 (Comparator and transport pins).
When an acceptance or KPI claim uses a comparison, pin the selected ComparatorSet.edition and comparator-spec edition. Retain the rule and edition for any conversion used by that claim; where a TransportRegistry governs it, pin TransportRegistry.edition and the selected transport policy ids. When two local senses must be related, cite the exact obtaining F.9 Bridge only as the correspondence premise, state the proposed bounded reuse in a separate C.2.1 claim, and check reliance under A.10 or B.3. A selected reference-plane change remains with CHR and its direct relation; the Bridge transfers neither reuse nor a plane value. For a claimed penalty, identify the rule and affected assessment as described in §4.5.
CC-A15.1-29 (Telemetry-reference pins, when applicable). If a work occurrence feeds G.11 or QD and OEE portfolios, the evidence relation cites the telemetry, archive, and policy references declared by the governing comparison, archive, evidence, or refresh pattern. Illumination remains report-only telemetry unless a governing comparison, archive, or selection pattern promotes that use.
CC-A15.1-30 (Part naming parsimony). Give an independently admitted Work part a stable name only when a current or later use needs to identify it distinctly. An interval, telemetry segment, pause, event-log row, engine-stroke label or detector component does not become a Work part by naming. Use §5.1’s occurrence and naming tests; retain a sufficient temporal, evidence or other neighboring object.
CC-A15.1-31 (Method and work granularity are coupled but not isomorphic).
A work part may enact a recovered submethod, but the correspondence is not automatic. A temporal work part usually enacts the same whole method during a slice. An episode may continue under one method or mode, span several operational parts, or repeat the same method fragment; an evidence policy may support a finer segmentation claim without changing method identity. An operational work part corresponds to a method factor only when that factor is recovered as U.Method under A.3.1 and B.1.5; otherwise retain the object actually identified without asserting that Method-factor correspondence.
CC-A15.1-32 (Work rows do not create architecture). Before a timetable, workflow, or architecture row supports a Work whole, part, overlap, or order claim, every Work occurrence is independently admitted under the full §4.1 test from its A.1:4.2 construction, each actual performer System’s A.13 basis, grounded action history, enacted Method, actual interval, and required containing-System relation; every whole, part, and temporal relation is then established separately. Apply F.6 afterward only for a precise assignment-bound attribution. Similar labels, shared rows, or planned co-occurrence establish none of these facts.
A.15.1:9 - Work-to-aggregation interface
A.15.1 makes the occurrence-side inputs recoverable without storing them in the occurrence: a separate assertion or description episteme designates exact Work individuals or work parts and states their temporal extents and the separately obtaining resource-use relations selected for aggregation. B.1.4 identifies the temporal-aggregation claim and result; B.1.6 identifies the resource-aggregation claim and result; a ledger may convey that account. These aggregation accounts remain distinct from Work-occurrence identity.
A.15.1:9.1 - Temporal aggregation return
For utilization, lead time, cycle time, phase coverage or another temporal roll-up, use B.1.4. Recover the Work intervals, aggregation concern, time basis, selected combining rule, conditions it consumes and admissible use. An adequate ordinary account can state the result; a separate record is needed only by its receiving use. Union, convex hull and optional Gamma_time notation concern that temporal aggregation, not Work-occurrence identity.
When the B.1.4 result selects the Work-interval profile, retain these use-specific choices:
- Union of intervals for utilization or availability: preserve every covered instant and do not count overlap twice.
- Convex hull
[min t_start, max t_end]for lead time or cycle time: preserve elapsed span from first start to last end, including gaps. - Declared algebraic behavior: for either exact set-based policy, duplicate input is idempotent, input order is irrelevant, and adding intervals cannot shrink the union or hull. If another policy lacks those properties, name it rather than borrowing the union/hull result.
Never switch union and hull silently between KPIs. The formulas above profile a recovered B.1.4 aggregation over Work intervals; the selected B.1.4 claim, not A.15.1, states the temporal result.
A.15.1:9.2 - Resource aggregation return
For a total or ledger over performed resource-use facts, use B.1.6. Recover the Work participants, typed resource values with applicable units and attribution grounds, accounting scope, time basis, aggregation rule and admissible use. Establish any holon-delimitation, overlap, allocation or deduplication facts used by the account. An adequate existing statement or ledger can suffice. Additivity, allocation, traceability and optional Gamma_work notation concern the resource aggregate, not Work-occurrence identity.
Filled heterogeneous BuildOps route. Published case-local specification BuildOpsResourceUseRelations-v12 declares BuildWorkUsesResource@BuildOps-v12(work, resource, amount, unit, extent) with participant order <work, resource, amount, unit, extent>. Its test requires the named Work actually to occupy or consume the named resource during that extent, with the amount measured in the named unit. Separate case facts state that ReleaseBinary12_BuildWork_2026-07-21T0900_0912 occupied BuildPoolCPU_A for 24 runner-core-minute during 09:00-09:12, and consumed 0.84 kWh of GridElectricity_BuildZone3 within BuildService_A_Delimitation-v12 during the same extent. Those facts make relation occurrences BuildRunUsedCPU_12 and BuildRunUsedElectricity_12 obtain with those exact participant tuples. BuildRunnerAllocationEvidence_12 and BuildZone3EnergyMeasurement_12 support the facts; neither record is the resource use, and neither relation is a field of the Work.
B.1.6 result BuildResourceAggregation_12 : WorkResourceAggregation@Context names concern Build12MeasuredResourceUse, bounded context BuildOps-v12, that exact Work, and the two relation occurrences. It uses typed basis BuildComputeAndElectricityBasis-v12, measures BuildRunnerCoreMinuteMeasure_12 and BuildZone3KWhMeasure_12, evidence refs BuildRunnerAllocationEvidence_12 and BuildZone3EnergyMeasurement_12, holon delimitation BuildService_A_Delimitation-v12, and window 09:00-09:12. Policy BuildResourceRelationDedup-v12 counts each exact relation occurrence once across repeated evidence or a parent/child view. Rule BuildTypedResourceVectorSum-v12 adds only entries of the same resource type and unit. Ledger BuildResourceLedger_12 contributes <BuildRunUsedCPU_12, 24 runner-core-minute> and <BuildRunUsedElectricity_12, 0.84 kWh> and returns Build12MeasuredResourceVector = <24 runner-core-minute, 0.84 kWh> without summing or converting its unlike components. Its admissible use is the measured resource-disclosure input for Build 12; it proves no Work identity, production result, efficiency, cost, sustainability verdict, or acceptance.
When a B.1.6 aggregation must allocate shared or overlapping resource use, retain these non-default policy examples:
- Parent attribution: book a declared shared fixed value once at the parent and independently measured variable values at children.
- Pro rata by wall time: divide a declared shared value by relative durations only when that driver is admissible for the resource basis.
- Driver based: allocate by a measured driver such as CPU share, weight, or priority and state the allocation rule that uses it.
Whichever policy is selected, add only disjoint or explicitly deduplicated values and keep every aggregate figure traceable to its contributing Work refs and evidence. A policy label alone establishes neither allocation nor ledger value.
A Work publication or KPI may cite either result through the E.17 publication face that projects that exact result. It may not recreate an unselected operator, infer an aggregate from parthood, or turn an aggregation record into a Work occurrence.
A.15.1:10 - Work-claim interpretation checks
When another decision relies on Work, apply only the following checks that its claims consume; reuse an established result while its basis remains applicable:
- Method-description interpretation, when used. Does
methodDescriptionRefresolve to the selectedU.MethodDescriptionepisteme under the effective reference scheme used by the receiving claim? If the claim also says this is an edition of an earlier description, does the exact C.2.1EpistemeEditionRelationobtain? If two local senses must be related, test an F.9 Bridge and state the bounded use separately rather than treating the reference change as a Bridge. - Performer and conditional assignment coverage. For every admitted
U.Systemnamed as performer, does section 4.0 recover its A.13 basis? If this receiving check expressly consumes precise assignment-bound attribution, does the account also cite the exact directly declared assignment species and the same obtaining occurrenceRAalready recovered through A.2.1 and A.13, and does F.6 obtain for the already admitted Work and thatRA? DoesRAcarry the actual participant values, have that System as holder, and cover the Work or exact performed part? If no attribution is current, stop after the performer and Work checks. If the conditional attribution branch fails, repair or reject the unsupported attribution. Retain independently grounded Work and performer claims; under §4.1, recheck any admission premise also affected by that finding. - Evaluation or acceptance, when claimed. Identify the criterion, its application to the required subject facts, returned value and evidence. Assert acceptance only under its own predicate and actual participants. Identify evaluation Work separately when its dated occurrence is claimed; keep result content and acceptance distinct. Historical criterion continuity requires the C.2.1 relation.
These checks tell the reader which description, assignment, criterion, evaluation, and relation to cite. They do not make acceptance part of work identity.
A.15.1:11 - Common Anti-Patterns and How to Avoid Them
- “The log is the performed occurrence.” Dumping telemetry without recoverable candidate-action facts—every actual performer System’s A.13 basis, at least one Method actually followed, time window, and at least one obtaining local containing-system relation, plus any other relation the receiving claim uses—does not establish Work. Recover and admit the occurrence independently, keep the log as evidence, and add F.6 only afterward when precise assignment-bound attribution is current.
- Record-handling-as-transformation. ETL, copying, formatting, evaluation, or publication work is treated as proof that a record or dataset changed -> Keep the grounded Work occurrence, but assert actual change only after A.3.4 identifies the transformation and either a declared domain predicate with the exact Work and transformation participants obtains or a C.2.1 local compound claim under A.6.RCD disposition 2 exposes its substrate-admitted constructor, governed base predicates, actual participants, and case facts; otherwise return
missing-governor[work-to-change]. - Silent cross-locality acceptance. “Ops accepted it, so audit accepts it.” -> Name the criterion and verdict for each receiving use. Assert acceptance only through that use’s declared predicate and actual participants. If no predicate governs the asserted acceptance, return
missing-governor[acceptance]. Identify evaluation or acceptance Work separately when that occurrence claim is needed; identify a C.2.1 evaluation-result episteme when the result content needs its own reference. If the criteria use different local senses, test the F.9 Bridge, state the proposed cross-local comparison or substitution in a separate bounded-use claim, and check reliance; the Bridge itself transfers no acceptance. - Description-change-as-occurrence-change. Selecting another MethodDescription episteme is treated as automatically splitting or preserving Work -> State the description-selection change separately. For an identity question raised by an actual history change, first use the direct facts. Apply the named use’s continuity-policy criterion only if the grouping remains ambiguous; the policy revises the judgment, not the occurrence. Call the descriptions editions only when their exact C.2.1 relation obtains.
- Performed cost and estimate collapse. Treating an estimate or Method-level statistic as actual resource use -> recover the dated Work and its resource-use relations. Keep forecasts, allocation and derived statistics under their own accounting rules.
- Part ambiguity. Mixing retries, episodes, and operational parts with no declared relation → Independently admit the participating Work occurrences, then assert the relation whose §4.1a predicate holds. For a retry claim, use the locally declared species required by §5.2.
- Timetable-as-Work-architecture. Rows with similar labels or one planned window are treated as one Work whole, its parts, or overlapping Work → Recover every actual Work occurrence first; then establish each Work-part and temporal relation separately. Keep an unperformed or ungrounded row as plan or description content.
- Slice-as-episode. A monitoring interval, telemetry window, crank-angle segment, or one-second reception trace is called an episode only because it has timestamps -> Keep it as a C.27.TA temporal aspect, evidence relation, or telemetry relation. Use
TemporalPartOf_workorEpisodeOf_workonly after the first participant is independently admitted as Work and the corresponding §4.1a predicate passes; add a continuity policy only if direct boundary facts leave its grouping ambiguous. - Episode-as-new-work by habit. A pause, retune, or interruption is always recorded as either a new occurrence or the same one -> Preserve the boundary events first. Use direct facts when they settle the grouping. If a named use still has more than one defensible grouping, apply its
workContinuityPolicyRef; without the needed criterion, leave that segmentation unresolved. - Method-factor-as-work-part by label. A step, stroke, receiver component, graph node, or method-description section is treated as a work part or submethod by name -> Identify the actual object and any claimed Method-factor or Work-part relation, including the relation’s participants; use the pattern that defines that relation.
- Granularity inflation. Every interval or trace row receives a durable Work-part name -> admit the Work part independently and name it only when the receiving use needs a distinct reference under §5.1.
- Union-hull confusion. Changing KPI coverage silently between reports -> recover the
B.1.4temporal aggregation and cite its policy per KPI. - Double-count in overlaps. Summing child and parent resource facts as one ledger -> recover the
B.1.6aggregation claim and apply its overlap or deduplication policy.
A.15.1:12 - Existing work-log repair applications
- Recover occurrence assertions. For existing logs, apply the full §4.1 test: recover the exact candidate action and its A.1:4.2 construction, every actual performer System’s A.13 basis, at least one Method actually followed, the extent, and containment facts under at least one declared local rule. Admit the Work from those independent facts, then assert the typed relations. If precise assignment-bound attribution is current, then recover the same covering assignment occurrence and its separate F.6 relation. Add optional
methodDescriptionRefand only those independently obtaining work-to-referent, binding, and resource-use relations on which the receiving claim relies. Do not create Work by creating a record. - Recover the work-judgment basis. Name the direct occurrence facts first. Add exact
workContinuityPolicyRef, effective reference scheme, scope, or qualification window only when the identity, episode, retry, resumption, or aggregation judgment has more than one defensible branch. Keep any selected MethodDescription episteme, aggregation policy, criterion, and evidence-use relation outside the Work. - Record a continuity policy only for an actual ambiguity. Cite exact
workContinuityPolicyRefand its named use when an interruption, resumption, replacement, switch, or composite boundary could support more than one segmentation. If direct facts already close a simple uninterrupted case, omit the policy. - Separate temporal aspect, temporal Work part, episode, and operational part. Keep a bare interval or aspect with C.27.TA or its direct domain object. Use
TemporalPartOf_workonly between independently admitted Work individuals when the proper temporal-sub-occurrence predicate passes; useEpisodeOf_workonly for an independently admitted event-bounded Work sub-occurrence; and useOperationalPartOf_workonly for an independently admitted performed constituent of the whole. Recover any Method factor separately. - Name only useful Work parts. Apply §5.1’s threshold to the current or later use. Preserve the independently established relation, evidence or telemetry slice when it is sufficient, without adding a Work-part identity.
- Use B.1.4 for temporal roll-up. Cite the temporal aggregation’s result and selected combining rule, including the coverage and overlap conditions it uses, in the KPI; keep that account separate from Work.
- Use B.1.6 for resource roll-up. Recover the typed resource result, its attribution basis and the aggregation rule, with any allocation, overlap or deduplication conditions used by that account; an adequate statement or existing ledger can suffice. Each contributing performed resource-use relation remains independently obtaining with a Work occurrence as a participant.
- Pull plans out. Keep calendars and planned fillings in exact
U.WorkPlancontent; establish performed values only through direct relations in which the Work occurrence participates and through exact A.6.1 bindings. - Bind actual values directly. For an operation argument or result, name the identified A.6.1 application and its exact binding. For any other participant or parameter, name the declared subject predicate, participant order, and actual values; return the matching missing-governor result when that predicate is absent. Retain MethodDescription defaults and WorkPlan choices as non-actual neighbors.
A.15.1:13 - Consequences
| Benefits | Trade-offs and mitigations |
|---|---|
| Auditable occurrence claims. Cost, time and quality accounts can refer to independently identified Work through their governing relations. | Identify the occurrence separately from the assertion or description; record creation is not occurrence creation. |
| Sound roll-up inputs. Work refs, intervals, parts, and performed resource-use facts make temporal and resource aggregation replayable. | Separate aggregation. Recover temporal aggregation in B.1.4 and work-resource aggregation in B.1.6; cite their policies and results rather than copying Gamma semantics into Work. |
| Cross-locality clarity. Method-description, scheme, scope, criterion, evaluation, and acceptance relations prevent silent meaning drift. | Bridge upkeep. Maintain F.9 Bridges only for exact local-sense crossings that a receiving use actually needs. |
| Explicit occurrence identity. Distinct parts, overlaps and retries provide the inputs needed to detect double-counting and identity errors. | Their correct use still requires the applicable identity, temporal and accounting rules. |
A.15.1:13.0 - Rationale
U.Work is retained as the admitted kind for dated Work occurrences because performer System, local system-role kind, system-role assignment, Method, MethodDescription, WorkPlan, affected entity, actual change, evaluation-result episteme, delivered entity, and downstream effect are different FPF objects. One Work individual is the world-side occurrence. Every actual performer is an admitted U.System with an A.13 agency basis for the action, scope, and window. A.15.1 admits the occurrence under the full §4.1 test from its A.1:4.2 construction, that performer basis and independently grounded history, Method, extent, and containment. Only when precise assignment-bound attribution is current may F.6 then relate that already admitted Work to the same obtaining assignment already recovered through A.13; it identifies neither. An assertion or description about the Work is a separate episteme. Missing assignment attribution alone does not revoke Work membership; a finding against a separate admission premise requires its own recheck under §4.1. Add direct Work-to-referent, binding, resource-use, or change facts only when their own relations obtain.
A.15.1:13.1 - SoTA-Echoing
| Source tradition | Source reference and contribution | FPF use | Shortcut rejected |
|---|---|---|---|
| Occurrent and 4D occurrence ontology | BFO 2020, standardized in ISO/IEC 21838-2:2021, distinguishes occurrents and temporal parthood; Partridge and de Cesare’s 2013 BORO account supplies the historical lineage of identifying individuals by spatiotemporal extent. | U.Work admits dated occurrence holons; each Work individual has its own temporal extent and participates in separately obtaining occurrence relations, while assertions and records about it remain separate epistemes. Parts, retries, resumptions, and overlaps stay explicit. | Treating a Method factor, diagram, system-role label, log entry, or record schema as the performed occurrence. |
| Object-centric event logging and process mining | The OCEL 2.0 metamodel represents typed events, qualified event–object and object–object relations, and changing object attributes. The OCEL 2.1 prerelease adds single-file CSV and bundled CSV/Parquet serializations. | For an event record, identify the candidate action and the claim its content supports. Several sources may jointly ground Work admission; the complete §4.1 basis must make the occurrence’s A.1:4.2 construction, performance history, every actual performer’s A.13 basis, enacted Method, temporal extent and local containing-system relation recoverable. Recover any relied-on object, binding, resource-use, interpretation or policy relation when the receiving claim needs it. Any precise assignment-bound attribution remains a separate later F.6 result. These admission conditions apply across serialization formats. | Treating the existence of telemetry or event rows as sufficient grounds for U.Work admission without inspecting the claims they support. |
| Observability and telemetry practice | OpenTelemetry Specification 1.62.0 for trace, metric and log representation. | Telemetry can support, replay, measure, or diagnose a claim about Work, but the occurrence still needs every actual performer’s A.13 basis, independently grounded history, enacted Method, temporal extent, and local containing-system relation. Add F.6 only for a separately claimed precise assignment-bound attribution, and add another enactment, affected-referent, binding, or resource-use fact only when the receiving claim uses it. | Counting trace, metric, or log existence as the performed Work, a result, or dominance evidence without the direct evidence, comparison, or archive relation. |
| Provenance and evidence-provenance practice | W3C PROV-O is a 2013 Recommendation; the 2025 PROV-O and BFO alignment is a later interoperability contribution. | Assertions or descriptions about Work cite the evidence-provenance relations and currentness notes their use needs without letting evidence, assurance, gate, or provenance claims replace the occurrence. | Using a provenance relation, assurance statement, or gate result as if it were the performed Work. |
| Temporal-interval reasoning | Allen’s interval algebra (1983) supplies qualitative relations among intervals; W3C OWL-Time (2017 Recommendation, §§3.1–3.4) represents these relations together with interval boundaries, durations and temporal reference systems. | A.15.1 supplies identified Work intervals, parts, and performed resource-use facts; use B.1.4 for temporal aggregation and B.1.6 for work-resource aggregation, each with its stated policy and admissible use. | Mixing union, hull, parent cost, child cost, and ordinal comparison on the Work object without a recovered Part B aggregation claim. |
A.15.1:14 - Relations
- Builds on: A.1 for the candidate occurrence’s common constructive criterion and System admission; A.2 for local agential system-role kinds and classification; A.2.1 for direct assignment species and occurrences; A.13 for the precise agency claim, characteristic profile, scope, window, and evidence; A.3.1 for
U.Method; A.3.2 forU.MethodDescription; C.2.1 for episteme editions and effective reference scheme; A.2.6 for claim scope; and C.27.TA for temporal qualification. - Coordinates with: F.6 for attribution through the same obtaining A.13 assignment; A.15 for alignment; A.6.1 for actual bindings; A.3.4 for actual Transformations; A.15.PROD for production and inception; B.1.4 and B.1.6 for aggregation; E.10/E.10.ROLE for Agent, performer, and role wording; A.10, B.3, E.17, and A.15.4 for evidence, assurance, publication-use, and appearance-based reliance; A.15.5 for readiness; and C.32.P2S for carry-through. Permission, gate, result, production, delivery, and acceptance remain independent of Work identity.
- Informs: reporting and KPI patterns, assurance and evidence patterns that use Work as the reference occurrence, and planning patterns that compare exact
U.WorkPlanclaims with independently identified Work occurrences.
A.15.1:15 - Didactic quick cards
- What is Work? How it went this time → dated, attributable, and actually enacted.
- Performer chain: Who performs? An admitted System with an A.13 agency basis at this grain. Did dated performance occur? A.15.1 independently admits Work. When precise assignment-bound attribution is current, under which assignment? The same obtaining A.13 assignment later tested by F.6; otherwise stop at admitted Work. Can? Capability. How? Method. Intended? WorkPlan.
- Three-question result check: Did the Work occur? What separate result or consequence is claimed? Who judged or accepted what, by which criterion and evidence? Use section 4.6 and stop after the last current question.
- Passive stop: Containing equipment, affected subjects, causal participants, actor-like labels, and assignments do not perform by implication.
- Roll-ups: A.15.1 supplies Work references, intervals, parts, and performed resource-use facts; cite B.1.4 for temporal aggregates and B.1.6 for resource ledgers, each with its declared policy.
- Episodes vs retries: record end, interruption, resumption, and later work-entry facts first; add a continuity policy only when a named use still has more than one defensible grouping.
A.15.1:15a - P2W Performed-Work Use Relation
When E.18.1 reaches performed Work, first recover each actual performer System’s A.13 local kind and criterion, classification, obtaining assignment, scope, working situation, and window, with evidence adequate for those core claims and a characteristic profile only when conditionally consumed. Then apply the full §4.1 test to the exact candidate action: establish its A.1:4.2 construction, Method actually followed, extent, and containment facts under at least one declared local rule. Admit the same occurrence under U.Work, then assert its typed relations. Only after admission, if precise assignment-bound attribution is current, use F.6 to relate that Work to the same assignment. Add only the actual operation binding, resource use, or Work-to-referent relation on which the receiving sentence relies. Planning may name intended performer conditions but does not backdate an A.13 assignment, agency claim, or Work occurrence.
A Work occurrence may be designated by an episteme that also cites a U.WorkPlan, exact A.15.3 planned-filling claim, or prior readiness claim as a baseline. For an operation argument or result, cite one identified A.6.1 application and its exact binding. For another participant, premise, resource use, or work-to-referent claim, name the declared predicate, participant order, and actual values; if that predicate is absent, return the corresponding missing-governor result. Do not copy a result or consequence into Work; follow the concrete §4.6 route.
A.15.1:16 - Lowering, Repair, and Refresh Conditions
Lower a candidate Work assertion when any claimed actual performer lacks the complete A.13 basis for the action, scope, and window, or when the exact candidate-action history, occurrence designator, temporal extent, at least one Method actually followed, or one required locally declared containing-System relation cannot be recovered. A missing, unresolved or failed F.6 relation lowers the precise performedUnderAssignment and assignment-bound performer claim. Preserve independent Work admission; if that finding also questions an actual admission premise, recheck it and its dependents under §4.1. Lower an additional enactment, Work-to-referent, operation binding, or resource-use claim separately when its direct basis is missing. Do not lower supported System functioning, behaviour, causal participation, Transformation, plan, Method, evidence, or telemetry claims merely because the Agent, Work, or attribution branch fails.
Repair the Work assertion or description when a subsequent source changes the resolved temporal extent, actual performance history, an actual performer System’s A.13 basis, enacted Method, selected method-description reference, direct binding, resource-use claim, work-to-referent relation, obtaining containing-system relation, or work-part relation. Repair the separate F.6 attribution when the covering assignment, direct pair fact, holder equality, species, participants, or coverage changes; do not rewrite Work membership merely because attribution changes. Reidentify only when the direct A.15.1 boundary rules decide the change or the selected policy’s branch criterion applies to a named ambiguous use. Repair a result or consequence through the matching §4.6 row rather than editing Work.
Before a new receiving use, confirm that the occurrence and related results still have the meaning, applicability and currentness that use requires. Reuse a result with unchanged grounds; recheck changed, missing or expired dependencies, using A.10.1 when a changed relied-on source affects several uses. If the question is no longer about performed Work, apply its direct pattern and keep a Work reference only when the claim depends on that occurrence.