#U.Work: Dated Performed Work Occurrence

A.15.1 · Stable · Architectural (A) · Normative unless marked informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

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

At a glance. Use U.Work for one world-side dated occurrence only after each claimed performer is an admitted U.System with the current A.13 core basis for the exact action: one local agential system-role kind and its criterion, classification of that System under the kind, one obtaining assignment of that kind, and the scope, working situation, and window needed by the use. Evidence must support those core claims. Admit the occurrence in A.15.1 only when its performance history, at least one Method actually followed, temporal extent, and at least one obtaining locally declared containing-System relation are independently grounded. This membership closes before and does not depend on F.6 performedUnderAssignment; apply F.6 afterward only when the receiving use makes a precise assignment-bound performer attribution. Add an agency-characteristic profile only when the receiving claim consumes a Grade, autonomy or profile result, when the local criterion itself explicitly depends on such a characteristic, or when an assurance use requires it. A WorkPlan, MethodDescription, log, dashboard, assertion, or record is a different object and does not make the Work occur. Start with the ordinary sentence in the compact example below; open the technical relation path only when the receiving claim needs it.

Use this when. Use this pattern when a plan, MethodDescription, schedule, log, telemetry stream, dashboard, approval-looking cue, publication face, result statement, or evidence relation is being treated as if performed Work; or when the exact dated action, A.13-qualified performer basis, Method, interval, or containing-System relation needed for Work admission is missing. Use F.6 separately after admission when a precise claim about the assignment under which the Work was performed is current.

Primary reader. Engineers, operators, process owners, modelers, auditors, and FPF authors who need to say what actually happened without turning plans, descriptions, logs, outputs, measurements, or changes into Work.

First useful object and short-account rule. Name one independently identified dated candidate action, each actual performer System and its A.13 local agential kind, criterion, classification, obtaining assignment, scope, working situation, and window, the Method actually followed, when the action occurred, and one declared relation to a System whose stated boundary contains the complete occurrence. Keep evidence for those facts recoverable; add a characteristic profile only under the conditional branch above. When those facts pass A.15.1, admit the occurrence as W : U.Work. Only afterward, if precise assignment-bound attribution is current, let F.6 test performedUnderAssignment(W, RA) using the same obtaining A.13 assignment and the direct case fact for the exact pair. A Work-only account may stop after admission; a short attribution account may omit an unused identifier only when every required link remains recoverable. Add another enacted Method, containing-System relation, direct Work-to-referent relation, binding, resource-use relation, profile, or assurance result only when the receiving claim needs it. If the next sentence reports a result, change, production, delivery, or judgment, use the matching section 4.6 row; do not make it a Work field.

Use the following route:

1. 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.
2. Identify the candidate performer as an exact System under A.1 without using the candidate Work to prove systemhood.
3. For every precise Agent claim, recover the A.13 core basis in section 4.0 before using actual performance as evidence; open the characteristic-profile branch only under its stated receiving-use condition.
4. Test the actual bounded candidate action, every actual performer's A.13 core, at least one Method actually followed, the interval, and one declared Work-to-System relation whose stated boundary contains the complete occurrence. On pass, admit W : U.Work and its A.15.1-owned relations.
5. 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.
6. 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. 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 exact 09:00–09:20 inspection history, TurbineInspectionMethod, and the declared containment within InspectionService-A independently 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. This example's assurance use also compares obstacle response, policy choice, persistence, and operational closure, so it cites the corresponding A.13 profile evidence; Work admission itself consumes no such profile unless its criterion or receiving use requires one.

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. Until the A.13 performer basis and performed occurrence can be recovered, do not call either one Work.

Recognition check. First, can the team point to one exact dated action, every actual performer System with its A.13 core, at least one Method actually followed, the extent, and one exact containing-System relation? If not, do not admit U.Work. Second, if precise assignment-bound attribution is current, can it point from that already admitted Work to the same obtaining A.13 assignment through the direct F.6 case fact, holder equality, declared species, and coverage? If not, retain the Work and leave only that attribution unresolved.

Stop condition. Stop the admission branch once the candidate is either admitted as one U.Work individual at the needed granularity from the A.13-qualified performer, occurrence, Method, extent, and containing-System facts, or lowered to a truthful neighboring claim. If precise assignment-bound attribution is current, continue only until F.6 establishes or rejects the exact Work-assignment relation. Missing or rejected F.6 attribution never revokes independently established Work membership; it lowers only the assignment-bound attribution. A missing optional profile blocks only the Grade, autonomy, profile, criterion-dependent, or assurance claim that requires it.

What changes in practice. A team no longer promotes a plan, log, output, state change, or assignment into Work. It identifies one occurrence and its actual performer basis first, then adds only the result, change, resource, or evidence relations that the current decision consumes.

What this buys. One independently admitted dated Work identity whose A.13-qualified actual performer Systems, enacted Methods, temporal extent, and required containing-System relations remain inspectable, plus a separately decidable F.6 relation whenever a receiving use needs exact assignment-bound attribution, together with only the direct neighboring relations and conditional profile or assurance claims used by the current decision.

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).

After we have separated which system-role assignment obtains (via U.SystemRoleAssignment), what capability is being relied on (via U.Capability), how in principle the Work is done (the exact U.Method), and which claim-bearing episteme, if selected, describes that Method (U.MethodDescription), we still need a precise concept for what happened as performed Work in real time and space.

#Aliases

• U.Work

#Keywords

• independent U.Work admission
• world-side dated occurrence
• exact performance history
• A.13-qualified actual performer U.System
• enacted Method
• temporal extent
• containing System
• F.6 only after admission for precise assignment-bound attribution
• optional direct bindings and resource use
• separate result or consequence
• conditional agency profile.

#Relations

#Content

#Problem Frame

After we have separated which system-role assignment obtains (via U.SystemRoleAssignment), what capability is being relied on (via U.Capability), how in principle the Work is done (the exact U.Method), and which claim-bearing episteme, if selected, describes that Method (U.MethodDescription), we still need a precise 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 exact 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 may designate that individual and state the relations, but the episteme neither creates the relations nor becomes the Work occurrence.

#Problem (what breaks without a clean notion of Work)

1. 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.
2. 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.
3. Who and when leakage. People and calendars are baked into method descriptions; reuse and staffing agility collapse.
4. Resource dishonesty. Energy, money, and tool wear are represented as fields or booked to Methods, local system-role kinds, or assignments instead of being stated through separately obtaining resource-use relations involving exact Work individuals; costing and sustainability measures drift.
5. Mereology muddle. Teams hand-wave over work parts, retries, overlaps, or long-running episodes; roll-ups double-count or miss work.

#Forces (what the definition must balance)

#Solution — admit dated Work occurrences under U.Work

#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 exact admitted U.System, one exact 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:

1. admit the exact candidate performer S as U.System under A.1 without using the candidate Work, assignment, capability, or actor-like name to establish systemhood;
2. state the proposed action, relevant objective or norm, conditions, System boundary, scope, working situation, and window without calling the occurrence Work;
3. recover an exact local agential system-role kind K under 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;
4. establish with appropriate evidence that S satisfies that criterion and is classified under K;
5. recover one direct A.2.1 assignment species that assigns K and one obtaining occurrence RA whose holder is S, assigned-kind value is K, predicate and participants pass, and extent covers the scope, situation, and window; and
6. 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. This preserves A.13's agency spectrum without turning that optional characterization layer into a universal Work precondition.

Only then use section 4.1 to test the actual bounded candidate action, Method followed, time, containing-System relation, and other facts used by the Work claim. On pass, A.15.1 admits W : U.Work without assuming an F.6 conclusion. After that admission, F.6 may attribute W through the same obtaining RA; actual performance cannot be used to bootstrap the A.13 classification or assignment, and F.6 cannot be used to bootstrap Work membership. A profile cannot substitute for the local criterion, classification, or obtaining assignment.

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 exact 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.

#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 the exact 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 at least one locally declared Work-to-System relation places the complete occurrence inside an exact System boundary. 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.

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 leaves W : U.Work intact and leaves only 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. The canonical F.6 relation performedUnderAssignment(W, RA) is checked only after W is admitted and attributes that exact Work occurrence to one exact 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 the independently admitted Work and do not assert that sentence. 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 exact 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 method description, continuity policy, or criterion an edition only when an exact C.2.1 EpistemeEditionRelation connects it to the earlier episteme and obtains. Otherwise name the selected episteme, or say that one episteme is a non-continuing replacement for another.

#Direct Work relations used by this pattern

These relations are world-side facts, not fields stored in Work. For each A.15.1-owned relation below, both participants must already be independently admitted under the stated kinds. 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.

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 A.15.1 occurrence basis includes 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 create another Work-containment relation. If the use needs one and none is declared and grounded, return missing-governor[work-containment]. 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.

Ordinary interval relations are not an A.15.1 synonym list. 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 actual 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).

#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; it neither creates another Work occurrence nor changes Work that has already occurred. 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:

1. 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.
2. Performer System and agency basis — for admission, name every actual performer U.System and 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.
3. Enacted method — actual enactsMethod -> U.Method. Cite methodDescriptionRef -> U.MethodDescription only when the receiving claim depends on that exact description episteme; the description is not enacted.
4. Containing Systems — name at least one locally declared Work-to-System predicate, its actual Work and U.System participants, 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.
5. 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 affected field establishes no such relation. If the use needs the relation but no predicate governs it, keep the Work and referent and return missing-governor[work-to-referent]. An obtaining work-to-referent fact does not by itself assert change, production, delivery, or acceptance.
6. 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-governor result rather than asserting it. A MethodDescription field, plan row, type-compatible value, or log token establishes none of them.
7. 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.
8. Continuity policy for an unresolved segmentation — when a named identity, episode, retry, resumption, or aggregation use has more than one defensible segmentation, cite workContinuityPolicyRef to the exact C.2.1 episteme whose claims state the branch criterion and tolerances for that use, and interpret those claims under its effective U.ReferenceScheme. If the criterion or its applicability cannot be recovered, leave that segmentation unresolved. The episteme is a U.MethodDescription only if it independently satisfies A.3.2's method-description criterion. A simple uninterrupted occurrence needs no continuity-policy reference; the policy supports a judgment about the occurrence and neither constitutes nor rewrites it.
9. Work mereology and temporal relations — exact parent, part, predecessor, successor, overlap, retry, or resumption relations only when their predicates obtain.
10. 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.
11. 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.
12. 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.

#Clear distinctions in a Work claim

#Publication-use boundary for U.Work

A publication about one Work occurrence projects an already declared assertion or description episteme; it does not create the world-side occurrence, add performed-occurrence facts, or make a plan, source reconstruction, dashboard, publication face, or carrier count as performed work.

Preparation is classifiable as one Work individual under U.Work only after it actually occurs and 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.

#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 reliance through the applicable A.10 account of independently established evidence-use relations or the B.3 assurance result, and state any penalty only under its separate policy; none of these facts changes the Work occurrence's identity.

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.

#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. An absent row stays absent; the table is not a result record to fill.

Three-question result check. (1) Did the work occur? Name W, every actual performer's A.13 basis, the grounded performance history, enacted Method, time, and at least one declared relation to a containing System under an exact boundary. If the use also needs exact assignment-bound attribution, run F.6 only after that admission and name its separate result. (2) What separate result or consequence is claimed? Name the exact returned value, entity, change, production claim, or transfer and use its row above. (3) Who judged or accepted what, by which criterion and evidence? Name the evaluation work, result, evidence relation, and acceptance relation separately. Stop after the last current question.

#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 exact locally declared containing-system relations needed by the use, any direct work-to-referent relations, actual bindings, resource use, and exact 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 distinct actual work-entry after an established completion or termination identifies a later occurrence; a proper work part and its parent are distinct individuals; independently grounded concurrent performances are distinct. A record, trace, policy episteme, or later judgment creates none of them.

#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 of TemporalPartOf_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 exact workContinuityPolicyRef only 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 exact C.2.1 episteme whose claims state the named use, boundary events, tolerated variation, and branch criterion. Interpret those claims under that episteme's effective U.ReferenceScheme. Add a U.ClaimScope, temporal qualification window, or model-use structure only when changing it changes the segmentation assertion; otherwise omit it. The policy episteme supports classification of the already existing history for that use. A later or competing policy episteme can support another identity or segmentation assertion. Call it an edition only when an exact C.2.1 EpistemeEditionRelation obtains between the exact earlier and later epistemes; without that relation it is a non-continuing replacement. Either way, the policy neither becomes a U.MethodDescription by policy form nor changes the occurrence, its parts, or their actual facts.

• Operational-part (OperationalPartOf_work). A work-part occurrence that may enact a factor of a recovered U.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 referenced U.MethodDescription is not enacted. If no U.Method factor is recovered, keep the material as the work part, evidence segment, telemetry segment, mechanism material, system-component behavior, or missing-source-relation note that was 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_work is not introduced as a primitive work-part relation.

Naming threshold. Do not mint a durable public U-kind or durable named work object, or infer a separate work occurrence for every interval, telemetry segment, pause, or episode-looking wording. Use a derivative part relation for an independently admitted Work part; give that part a durable name only when downstream use needs its own resources, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return use. In other cases keep the temporal relation, evidence slice, telemetry segment, method-description constituent, missing-source-relation note, or other concrete neighboring object that the task actually needs.

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_work only 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 workContinuityPolicyRef only when interruption, resumption, switch, replacement, or pause leaves the grouping ambiguous for that use; then use EpisodeOf_work only when its direct predicate is satisfied.
• Ask "which performed sub-occurrence has its own actual performer System with an A.13 basis, temporal extent, enacted Method, affected referent, bindings, resource use, or separately consumed place in an aggregation?" If that is current, use OperationalPartOf_work or another declared Work-part relation. When precise assignment-bound attribution is also current, check the separate F.6 relation only after admitting the sub-occurrence. A neighboring evaluation or effect claim does not establish Work parthood by itself.
• Ask "which way-of-doing part is being composed?" If the answer needs preconditions, effects, interface, and whole-method relation, recover a U.Method submethod under A.3.1 and B.1.5; do not make the work part itself carry the method identity.

#Key relations among Work

Temporal order and overlap. A.15.1 supplies each Work occurrence and its exact extent; it does not declare precedes, happensBefore, overlaps, contains, and within as interchangeable relation names. 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.

#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, open B.1.4. Its recovered ContextTemporalAggregation@Context, coverage and non-overlap conditions, aggregation policy, and optional Gamma_time notation govern union, hull, or another admitted temporal aggregate. The work intervals remain A.15.1 facts.
• Resource aggregation. When a receiving use needs a total over materials, energy, time, money, tool wear, or another performed resource value, open B.1.6. Its recovered WorkResourceAggregation@Context, typed resource-accounting basis, evidence refs, overlap or deduplication policy, ledger, aggregation rule, and optional Gamma_work notation govern the aggregate. Each contributing performed resource-use relation obtains separately with its exact Work occurrence as a participant; any ledger or assertion about that relation is a separate episteme.

Manager's tip: cite the exact 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.

#Before A Timetable Becomes Architecture Evidence

A timetable, workflow row, or architecture table can help locate candidate Work. It does not establish a Work occurrence, whole, part, overlap, or order. Before relying on such rows in an architecture decision:

1. identify each Work occurrence from 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;
2. 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;
3. if two occurrences are claimed to overlap or follow one another, state their actual intervals and the exact C.27.TA temporal relation; and
4. 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.

#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 actually 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 of the same actual start, open end, or completed end can refine the assertion without changing the occurrence. 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 an interruption, resumption, method or mode switch, performer replacement, retune, rework, referent or binding change, or composite boundary stays inside one parent, 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 exact C.2.1 EpistemeEditionRelation obtains, and otherwise treat it as a non-continuing replacement. Neither branch retroactively changes what occurred.

#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 retryOf remains 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 EpistemeEditionRelation obtains.
• Rework: identify the later performance independently. Relate it as another occurrence, episode, or operational part only after the applicable direct predicate and any genuinely 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 that distinction is actually current. Otherwise retain the direct occurrence facts and stop; do not add policy apparatus to a simple uninterrupted case.

#Work mereology does not compose effects or transformations

A parent Work can have exact 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 exact 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.

#Archetypal grounding (parallel domains)

#Change without Work and self-directed Work

• Change without Work: LunarTideRise-2026-07-27 may be identified under A.3.4 as a Transformation of the exact water body over the stated interval. The fixture supplies no actual performer U.System with an A.13 agency basis for a tidal action, no Method that such a performer followed, and no containing-System relation for a performed occurrence, so A.15.1 does not admit Work. A causal explanation, assignment-like label, or hypothetical F.6 link supplies none of those missing admission facts.
• Self-directed Work: in the rehabilitation case, the current model admits MotorControlRightArmSystem-7 : U.System and Person-7 : U.System; A.14 ComponentOf(MotorControlRightArmSystem-7, Person-7) and ComponentOf(LeftArm-7, Person-7) obtain, so the mover and the affected limb are distinct parts of one person. SelfCarePerformerSystemRole is a declared local agential kind for the stated stretch action; the case gives its target-relative membership criterion, classifies MotorControlRightArmSystem-7 under it, makes SelfCarePerformerAssignment-7 obtain for the scope and window, and cites evidence that the System satisfies that local criterion; this case makes no Grade or autonomy-profile claim. MotorControlRightArmSystem-7 then performs LeftArmStretchWork-7 from 2026-07-27T07:30:00+03:00 to 2026-07-27T07:35:00+03:00 under that assignment; F.6 performedUnderAssignment obtains and the Work enacts AssistedLeftArmStretchMethod-E1. Clinic relation specification ClinicRehabRelations@Clinic-E1 declares RehabWorkOccursWithinPersonBoundary@Clinic-E1(work, system) for the stated person delimitation and five-minute window, and the case facts make it obtain for that Work and Person-7. The same specification declares RehabWorkStretchesLimb@Clinic-E1(work, limb, interval), which obtains for that Work, LeftArm-7, and the five-minute interval. Separately, A.6.1 application AssistedStretchApplication-7 binds its declared AffectedLimbArgument to LeftArm-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 at least one obtaining local Work-to-System containment relation ground A.15.1 admission; 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.

Each case below is presented as readable content of a separate assertion or description episteme. Arrow notation abbreviates independently obtaining world-side relations involving the named Work individual; methodDescriptionRef and continuity-policy references cite separate epistemes. The bullet layout declares no slots or fields on the Work individual.

#Surgical case (overlap and episodes)

• 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 in SurgicalServiceWorkBoundaryRelations@Hospital-8472.
• Patient and administered dose: project relation specification MED-ADM-2026, owned by ClinicalAdministrationRelations@Hospital-8472, declares ClinicalWorkAdministersDoseToPatient(dose, patient, clinicalWork, interval). The stipulated administration facts make it obtain for MedicineDose_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 return missing-governor[SURGERY-RESOURCE-USE] and do not enter Work identity.
• methodDescriptionRef: Appendectomy_v5.
• A.13 Agent basis, performer System, and assignment: SurgicalTeamSystemRole is a declared local agential kind for coordinated operative action; its criterion requires goal-directed, condition-sensitive regulation of the stated surgical action, the fixture classifies OR_Team_A : U.System under it, and cited evidence supports that local criterion and classification for the surgery scope and window; no Grade or autonomy-profile claim is used. SurgicalTeamAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. OR_Team_A_SurgicalTeamAssignment_2025-08-10 is the obtaining occurrence: its holder is OR_Team_A, its assigned kind is SurgicalTeamSystemRole, and its extent covers the surgery. F.6 states that OR_Team_A performed this Work under that occurrence. The team System acts; the kind, species, and occurrence do not.
• 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 under Hospital-Operating-Scheme-2025; its stated 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-8472 uses union under ORUtilizationUnionPolicy-2025; SurgeryPatientLeadTimeAggregation-8472 uses hull under PatientLeadTimeHullPolicy-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 fixture 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.

#ETL pipeline (parallelism and retries)

• 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 in ETLWorkBoundaryRelations@WarehousePlatform.
• Dataset participation; resource stop: relation specification ETL-DATA-REL-2025, owned by ETLDataUseRelations@WarehousePlatform, declares SourceDatasetParticipatesInETLWork(dataset, work, extent) and DestinationDatasetParticipatesInETLWork(dataset, work, extent). The stipulated job facts make the first obtain for RawOrders_2025-08-11, ETL_Nightly_2025-08-11T01:00-01:47, and its extent, and the second for WarehouseOrders_2025-08-11 with 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 return missing-governor[ETL-RESOURCE-USE].
• Actual change, no connection yet: A.3.4 identifies WarehouseOrders_LoadTransformation_2025-08-11 as 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 lacks AcceptedOrdersRowSet_2025-08-11; after it, the project data-state relation to that row set obtains. This fixture 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 returns missing-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_Runtime is independently admitted as the exact running System. BatchExecutionControllerSystemRole is 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. TransformerRuntimeAssignment is the direct assignment species; ETL_Runtime_TransformerAssignment_2025-08-11 is the obtaining occurrence with holder ETL_Runtime, assigned-kind value BatchExecutionControllerSystemRole, 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; Transform starts when either completes (overlap).
• Retry: WarehouseWriteAttempt-1 ended at 01:36 without satisfying WarehousePartitionWriteComplete@ETL-2025; WarehouseWriteAttempt-2 then entered to satisfy that same condition for the same dated partition and source snapshot with a smaller batch. Local declaration ETLRetryRelations@WarehousePlatform defines RetriesWarehousePartitionWrite(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 generic retryOf token is not used.
• B.1.4 temporal roll-up: ETLSLACoverageAggregation-2025 uses hull under ETLSLAHullPolicy-2025; ETLClusterUtilizationAggregation-2025 uses union under ETLClusterUnionPolicy-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.

#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 fixture 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 exact human operator, controller runtime, or coordinated team, 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.

#Claim handling (episodes versus monitoring slices)

• 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 in ClaimsWorkBoundaryRelations@InsuranceOps-2026.
• Claim and resource stop: this fixture names Claim_8142, handler-time intervals, and ClaimsPlatform_A, but supplies no admitted Work-to-claim, handler-time-use, or case-system-time-use predicate. Keep the grounded claim-handling Work and return missing-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.
• A.13 Agent basis, performer System, and assignment: ClaimsHandlerSystemRole is a declared local agential kind for claim-resolution action; its criterion requires goal-directed, condition-sensitive regulation of the stated handling action, the fixture classifies ClaimsTeam_A : U.System under it, and cited evidence supports that local criterion and classification for the claim scope and window; no Grade or autonomy-profile claim is used. ClaimsHandlerAssignment is the directly declared assignment species whose signature gives the holder and assigned-kind participant meanings. ClaimsTeam_A_HandlerAssignment_2026-06-03 is the obtaining occurrence: its holder is ClaimsTeam_A, its assigned kind is ClaimsHandlerSystemRole, and its extent covers the claims Work. F.6 states that ClaimsTeam_A performed this Work under that occurrence. The team System acts; the kind, species, and occurrence do not.
• Episode policy: InitialReviewEpisodeWork-8142 and ResumedResolutionEpisodeWork-8142 are 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 applies ClaimsWorkContinuityPolicy_v7, a C.2.1 policy episteme interpreted under Claims-Handling-Scheme-2026. Its stated under-one-hour callback criterion supports assertion ClaimsSegmentation-v7-8142 that the two named Work individuals stand in EpisodeOf_work relations to ClaimHandling_Case_8142_2026-06-03. The policy supports the ambiguous grouping; it does not create either episode Work or relation.
• Nearest non-continuing replacement: competing episteme ClaimsWorkContinuityPolicy_15min-Alt, interpreted under the same reference scheme, states a fifteen-minute callback threshold. Applied to the same 29-minute gap, it supports assertion ClaimsSegmentation-15min-8142 that the resumed performance is a later Work occurrence rather than an episode under the first parent. No EpistemeEditionRelation between the exact v7 and 15-minute policy epistemes is established, so the second is a non-continuing replacement, not an edition. Either assertion may govern its named receiving use; switching the selected policy changes the use-local segmentation judgment, not either interval's actual history. Only if C.2.1's historical-continuation predicate is separately satisfied may the later policy be called an edition.
• Temporal monitoring slice: MonitoringSlice_09:15-09:20 is a C.27.TA temporal aspect used for queue-latency evidence. It is not a TemporalPartOf_work participant 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; under ClaimsSegmentation-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.

#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 fixture 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 exact operator, controller runtime, or coordinated team, 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.

#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.

#Classification work without result collapse

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 fixture declares RecognitionEvaluatorSystemRole as a local agential kind, gives its evaluation-action membership criterion, classifies RecognitionEvaluator_A under it, and cites 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. Exact 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 fixture 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 from 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.

#Filled result route: build, verify, transfer, accept

BuildRunnerAssignment is a directly declared species whose signature uses the local BuildRunnerSystemRole domain. The fixture declares BuildRunnerSystemRole as a local agential kind, gives its build-action membership criterion, classifies BuildRunner_A : U.System under it, and cites evidence that the System satisfies that local 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 exact action history, Method, extent, and BuildWorkOccursWithinServiceBoundary fact first admit ReleaseBinary12_BuildWork_2026-07-21T0900_0912 : U.Work. F.6 then separately states that BuildRunner_A performed that Work under the same assignment. 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.

The readable report is therefore: the build Work occurred; a different entity was returned and produced; BuildWorkPopulatedStore-12 states the positive local W-to-T claim; separate verification Work returned a verdict supported by evidence; and the entity was transferred to staging (ArtifactTransferToStaging_12). Acceptance remains at missing-governor[STAGING-ACCEPTANCE]. Removing any non-current row does not alter the identity of the build Work.

#Bias-Annotation

#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 workContinuityPolicyRef and its effective U.ReferenceScheme 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 clean, actionable notion of occurrence with an A.13 agency basis for every actual performer U.System, an independently grounded performance history, an obtaining enactsMethod relation, 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 declared U.SystemRoleAssignment species. 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.

#Conformance Checklist (admission checks)

CC-A15.1-1 (Strict distinction). 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 exact 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. 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 exact 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 U.ReferenceScheme, 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 reliance through the applicable A.10 account of independently established evidence-use relations or the B.3 assurance result. 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 only the attribution, or establish a retroactive occurrence 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 and is tested by a named A.2.2 capability-fit predicate against each performer system's capability instance for the work interval or declared checkpoints. Name that predicate, the capability instance, 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 selected criterion episteme or comparator specification, its applicable scope and window, the evaluation or acceptance work that applied it, its returned value or result episteme, and the declared acceptance predicate with all actual participants. If the claim relies on historical continuity with an earlier criterion episteme, name the exact C.2.1 EpistemeEditionRelation; a version label alone is not enough. If no acceptance predicate governs the claim, return missing-governor[acceptance]. Success class, quality measurement, comparison result, and acceptance verdict remain distinct; no verdict is an intrinsic field of the Work occurrence or a condition of U.Work membership. CC-A15.1-9 (Resource honesty). 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 U.Capability. If no predicate governs the needed use, return missing-governor[resource-use]; estimates remain in Method descriptions or plans. 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 names the exact Work refs, aggregation concern, time window, coverage and non-overlap conditions, and policy selecting union, convex hull, or another admitted result. 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 names the exact Work refs, typed resource basis, units, evidence, delimitation and time window, overlap or deduplication policy, ledger, and aggregation rule. A.15.1 supplies performed resource-use facts but does not own the aggregate ledger.

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 an exact 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 without rewriting the occurrence. 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. A list of familiar interval words supplies no relation declaration, and 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 its own effective reference scheme, claim scope, criterion, qualification window, evaluation work, and result episteme. 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, apply that use's exact continuity-policy criterion. 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 it is a non-continuing replacement. Neither changes the occurrence. 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 from its own 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 (Logs are evidence, not work by themselves). Logs and telemetry support a claim about Work only through an exact evidence-use relation that identifies the candidate action, 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. Those facts may support A.15.1 admission but the log creates none of them. When a precise assignment-bound attribution is also current, support its separate F.6 assertion without making the log or evidence constitute the 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 independently ground A.15.1 admission. Any precise assignment-bound attribution is then checked separately through F.6. Apply the paired first-use probe to natural change and self-directed action; 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 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). Exact 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. Numeric or comparable content names unit, scale, reference-plane, and EditionId pins; work-publication views do not use "signature" for these publication pins.

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. They do not encode aggregation semantics in prose or imply defaults. Optional Gamma notation lives with its recovered Part B aggregation claim; the view carries only pinned references needed by the publication use.

CC-A15.1-26 (No input-output re-listing). Publication views do not restate method-description input and output lists; they publish presence pins and source references only under the publication-use pattern governing that view.

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 lowers hidden scalarization or ordinal-mean claims.

CC-A15.1-28 (Comparator and transport pins). Numeric or comparable acceptance or KPI claims on a publication view about Work pin ComparatorSet.edition, comparator-spec edition, and, where conversions occur, TransportRegistry.edition with 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. Penalties affect the reliability relation only.

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). Do not create a durable named work part for every interval, telemetry segment, pause, event-log row, engine stroke label, detector component, or encountered wording. Name a work part only when downstream use needs its own resources, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return use. Otherwise retain the temporal relation, evidence slice, telemetry segment, method-description constituent, missing-source-relation note, or other direct neighboring object actually available without adding a durable work-part name.

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 keep it as the work part, method-description node, evidence segment, mechanism material, or system-component behavior actually identified.

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 from 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.

#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, ledger, and result. Neither becomes a Work field.

#Temporal aggregation return

For utilization, lead time, cycle time, phase coverage, or another temporal roll-up, use B.1.4. Name the exact work refs, carrier or aggregation concern, time window, coverage and non-overlap conditions, aggregation policy, and admissible use there. Union, convex hull, and optional Gamma_time notation are properties of that recovered temporal aggregation, not fields or identity invariants of a Work occurrence.

When the exact 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.

#Resource aggregation return

For a total or ledger over performed resource-use facts, use B.1.6. Name the exact work refs, typed resource-accounting basis, units, measurement or evidence refs, holon delimitation, time window, overlap or deduplication policy, aggregation rule, and admissible use there. Additivity, allocation, traceability, the aggregate ledger, and optional Gamma_work notation belong to that recovered resource-aggregation claim, not to 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 an exact 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 exact 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.

#Work-claim interpretation checks

When another decision relies on a work occurrence, perform three quick checks:

1. Method-description interpretation. Does methodDescriptionRef resolve to the selected U.MethodDescription episteme under the effective U.ReferenceScheme used by the receiving claim? If the claim also says this is an edition of an earlier description, does the exact C.2.1 EpistemeEditionRelation obtain? 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.
2. Performer and conditional assignment coverage. For every admitted U.System named 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 occurrence RA already recovered through A.2.1 and A.13, and does F.6 obtain for the already admitted Work and that RA? Does RA carry 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, retain the Work and performer and repair or reject only the assignment occurrence or F.6 attribution that failed.
3. Evaluation boundary. Has separately performed evaluation or acceptance work applied the selected criterion episteme to the independently obtaining relations involving the Work occurrence, changed subject, measurement results, or delivered entity that the criterion actually requires? If not, no acceptance verdict follows. If yes, keep the evaluation work, result episteme, verdict content, evidence, and acceptance relation separate. Claim edition continuity only when the exact C.2.1 relation obtains.

These checks tell the reader which description, assignment, criterion, evaluation, and relation to cite. They neither create one judgment-context object nor make acceptance part of work identity.

#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 each receiving criterion, evaluation work, and result episteme. Assert acceptance only through that use's declared predicate and actual participants; otherwise return missing-governor[acceptance]. 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. Only when an accompanying actual history change creates an identity question for a named use should its continuity-policy criterion be applied; the policy revises the judgment, not the occurrence. Call the descriptions editions only when their exact C.2.1 relation obtains.
• Budget on the method or system-role object. Charging costs to a Method, local system-role kind, or assignment -> Attribute performed resource use only through exact relations involving Work individuals; keep estimates in Method descriptions or plans.
• Part ambiguity. Mixing retries, episodes, and operational parts with no declared relation → Choose and declare the part relation.
• 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_work or EpisodeOf_work only 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. Apply exact workContinuityPolicyRef only when a named use must decide the grouping; otherwise return unresolved segmentation rather than forcing either answer.
• 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 -> Recover the current object: U.Method factor, U.MethodDescription constituent, TemporalPartOf_work, OperationalPartOf_work, evidence segment, mechanism material, system-component behavior, or missing-source-relation note.
• Granularity inflation. Every interval or trace row receives a durable work-part name -> Name the work part only when a current resource, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return use hangs on it.
• Union-hull confusion. Changing KPI coverage silently between reports -> recover the exact B.1.4 temporal aggregation and cite its policy per KPI.
• Double-count in overlaps. Summing child and parent resource facts as one ledger -> recover the B.1.6 aggregation claim and apply its exact overlap or deduplication policy.

#Existing work-log repair applications

1. Recover occurrence assertions. For existing logs, first recover the exact candidate action, every actual performer System's A.13 basis, at least one Method actually followed, the extent, and at least one obtaining locally declared containing-system relation; admit the Work only from those independent facts. If precise assignment-bound attribution is current, then recover the same covering assignment occurrence and its separate F.6 relation. Add optional methodDescriptionRef and 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.
2. 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.
3. Record a continuity policy only for an actual ambiguity. Cite exact workContinuityPolicyRef and 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.
4. 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_work only between independently admitted Work individuals when the proper temporal-sub-occurrence predicate passes; use EpisodeOf_work only for an independently admitted event-bounded Work sub-occurrence; and use OperationalPartOf_work only for an independently admitted performed constituent of the whole. Recover any Method factor separately.
5. Name only useful work parts. If no named resource, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return claim depends on the candidate part, retain the independently established relation, evidence slice, or telemetry slice without adding a durable work-part name.
6. Use B.1.4 for temporal roll-up. Cite the exact temporal aggregation and its union, hull, coverage, and non-overlap policy in the KPI rather than recreating it on Work.
7. Use B.1.6 for resource roll-up. Recover the typed resource ledger, evidence basis, allocation, and overlap or deduplication policy there; each contributing performed resource-use relation remains independently obtaining with an exact Work occurrence as a participant.
8. Pull plans out. Keep calendars and planned fillings in exact U.WorkPlan content; establish performed values only through direct relations in which the Work occurrence participates and through exact A.6.1 bindings.
9. 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.

#Consequences

#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 from that performer basis plus 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 does not revoke Work membership. Add direct Work-to-referent, binding, resource-use, or change facts only when their own relations obtain.

#SoTA-Echoing

SoTA alignment rule. A source tradition counts here only when it preserves the local separations: U.Work is the admitted kind; one Work individual is a world-side dated occurrence; each actual performer is an admitted U.System with an A.13 agency basis for the action, scope, and window; and A.15.1 independently admits the Work from that performer basis plus its history, enacted Method, temporal extent, and locally declared containing-System relation. F.6 enters only when the receiving use also consumes precise assignment-bound attribution through the same obtaining A.13 assignment; a missing or failed F.6 relation leaves W : U.Work intact. An assertion or description about the occurrence is a separate U.Episteme. Several containing Systems may be valid under different stated boundaries. Work-to-referent, binding, and resource-use relations are added only when they independently obtain. Neighboring change, evaluation, evidence, production, delivery, acceptance, and responsibility claims remain separate.

Qualification and smallest reopen. A newer source reopens this table only when it changes an admission fact or a relation used by a receiving Work claim. Revise the affected row and its matching admission, example, checklist, or public cue; do not rewrite unrelated Work identity content merely because a source version advanced.

#Relations

• Builds on: A.1 for exact 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 for U.MethodDescription; C.2.1 for episteme editions and effective U.ReferenceScheme; 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.WorkPlan claims with independently identified Work occurrences.

#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 exact 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.

#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 identify the exact candidate action, Method actually followed, extent, and at least one obtaining locally declared containing-System relation, and admit one Work individual under U.Work. 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.

#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. Do not lower an independently admitted Work merely because F.6 is missing, unresolved, uses another assignment, or fails holder or coverage checks; lower only the precise performedUnderAssignment and assignment-bound performer claim. 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.

Refresh before cross-context model use, aggregation, comparison, measurement, acceptance, release reliance, gate use, evidence use, assurance use, QD or OEE archive use, or P2W carry-through use. If the claim being made after refresh is no longer about performed work, use the direct pattern for that object or relation and retain a Work-occurrence reference only when the receiving claim actually depends on that occurrence.

#A.15.1:End

---

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)