A.15.6 - Recover What Project, Process, or Case Wording Refers To
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
Reader. This pattern is for the FPF practitioner who must identify what project-, process-, or case-management wording refers to before relying on the claim, then open the pattern that defines or constrains that subject.
A.15.6:1 - Problem frame
Use this when. Use this pattern when project, process, case, program, initiative, or situation wording is about Work and change, but the claim does not yet reveal whether it concerns one performed Work whole, a reusable way, a selected structure, or another named subject or claim being followed to a closure decision.
Use it also when a team cannot keep its problem-development, solution-development, and development-platform questions connected. This branch recovers the selected subjects without collapsing them into one project object. When a systemic account is needed, A.1.STM supplies its project system-of-interest and intended-use basis; the local subjects may still be Methods, epistemes, Work, capabilities or other results.
Use it also when project system-of-interest wording leaves unclear whether the claim concerns the system whose use organizes the undertaking or the current local subject, whether an actual U.System or only a future holder is intended, or whether designation is being inferred from a role label.
A claim of locality to one actual project requires a direct relation to its performed project Work, as section 4.5 states; an @Project name supplies only a label.
First useful move. If the project focus is unresolved, state the sought outside difference, relying use, comparison-and-acceptance conditions and receiving decision. Include any conflicting interests, evidence horizon or uncertainty that can change the choice or qualify its use. Compare candidate project subjects and materially different solution forms before designating a project system-of-interest or Method-of-interest.
Otherwise ask what the next decision is about: the Work that happened, the reusable way of doing, the organization of Method-side objects and relations, a TransformationFlowStructure, the referent being changed, or the System whose change or later use organizes the project.
In the process branch, identify whether the question concerns U.Method, a U.Structure selected under A.22, or TransformationFlowStructure. Then choose any representation needed for that question.
In the system branch, distinguish the project’s system-of-interest from the current subject of inquiry or local work, and an actual holder from a future description. Keep designation, the participants’ working agreement, technical classification and assignment as separate claims.
Three short recognition cases. Use these before the full pump example.
- Project: a plan designates
PumpUnit-3for an upgrade. While work is only intended, use A.15.2 for theU.WorkPlanand stop there. After performance, use A.15.1 to identify the composite projectU.Work; add a work-to-pump or work-to-change relation only under its own predicate. Stop when the current plan or Work question is answered—the plan, Work, and pump are not one project object. - Process: several inspections use
BearingInspectionMethod-4. Use A.3.1 for that reusableU.Methodand stop when the way-of-doing question is answered. Open A.22 only when the organization of identified method-side objects and obtaining relations changes the next action, and E.18 only when transformation flow is the question. One inspection Work enacts the Method. - Case: a failed pressure test opens a closure question about
PumpUnit-3or about one readiness or acceptance claim. Use A.15.5 when the question is whether an intended performance in aU.WorkPlanor PlanItem can enter under its work-entry conditions. For equipment condition, product readiness or acceptance, use the predicate that defines that claim. Stop when the closure answer and its basis are known. Name later release or pumping use, when relevant, as outside the case closure.
What goes wrong if missed. A plan is counted as performed work, a temporary organization is identified with its project, one work occurrence is mistaken for a repeatable process, or a case record replaces the named subject or claim whose bounded closure is being managed. Parallel @Project, @Process, and @Case names then create apparent kinds without identity rules.
What this buys. Project Work receives one occurrence identity under A.15.1. Process improvement can select one reusable U.Method, one A.22 U.Structure, or one TransformationFlowStructure without collapsing them. Case Work stays oriented to the subject its claims concern.
Plans, organizations, Transformations, descriptions, publications, results, and evidence can then be related through the claims the decision needs. A responsibility assertion needs its own predicate and participants. Use an applicable existing rule or a sufficient local claim under A.6.RCD; return missing-governor only when a governing predicate, applicability condition, necessary occurrence rule or other required rule is absent.
Not this pattern when. Use A.15.1 when the subject is already known to be performed work, A.3.1 when it is already a reusable method, A.3.4 when it is already a bounded transformation, or E.18 when it is already a selected transformation-flow structure. This pattern recovers the subject from management wording; it does not replace those ontics or domain management methods.
Recover the subject from management wording. Project, process, case, program, initiative, and situation are useful Plain cues. Section 4 explains the positive recovery: an actual project may be composite U.Work; a process concern may select U.Method, an A.22-selected U.Structure, or TransformationFlowStructure; a case concern follows the named subject or claim to its closure. Plans, organizations, changes, descriptions, results, and evidence keep their own identities and relations.
A method-side structure may be called MethodRelationStructure locally after A.22 selects it for one question and use. Its identity comes from that selection, including its constituents, obtaining relations, constraints and use frame. For another needed claim, recover the participants and the rule that defines or tests it. A local claim can suffice without a dedicated pattern or relation kind. If its governor is absent, name the missing rule and use A.6.RCD’s lightest sufficient branch.
A.15.6:2 - Problem
The same happening can be approached through three legitimate concerns. A project manager may need the identity, cost, completion, or result of one Work whole, but a result or measure remains its own subject when that is what the claim asserts. A process engineer may need one reusable U.Method, one A.22-selected U.Structure whose organization changes the next question or action, or a TransformationFlowStructure. A case worker may need to follow one named subject or claim to a bounded closure while keeping any relevant downstream use outside that closure.
Treating these concerns as three views of one unspecified “project situation” loses the subjects. Treating them as three sibling kinds duplicates ontics already supplied by U.Work, U.Method, U.Transformation, selected structures, epistemes, characteristic bearers and assignments, relation occurrences, and continuing referents. The problem is to recover the subject or claim and its direct relations while keeping familiar Plain wording available for retrieval.
A.15.6:3 - Forces
| Force | Tension |
|---|---|
| Familiar management vocabulary vs kind precision | Project, process, and case are useful recognition words, but they do not by themselves provide FPF identity rules. |
| Unique occurrence vs repeatable way | One Work whole has a dated 4D identity under the full A.15.1:4.1 admission test. Precise assignment-bound attribution adds F.6 only when that claim is needed. A reusable Method may be enacted by many Work occurrences; each asserted enactment needs the obtaining A.15.1 relation between that Work and Method. Relations among method-side values remain direct until all four A.22 discriminators select a U.Structure; a TransformationFlowStructure separately organizes transformation flows. |
| Case subject or claim vs neighboring history | A case follows the named subject or claim in its closure question; Work, changes, editions, measurements, decisions, evidence, records, and downstream use remain separately defined. |
| Intention vs actuality | A charter, plan, authorization, or funded intention can establish intended work. Performed work needs its independently grounded occurrence basis. |
| Actual system vs intended future system | A plan can describe the system the work is meant to produce or use, but an intended future System cannot be treated as an existing U.System or assignment holder before its applicable identity-inception boundary. |
| Project designation vs system-role classification and assignment | A project may designate one System without classifying it under a local system-role kind or asserting a system-role assignment. Conversely, an A.2 classification under a local system-role kind, or even an assignment occurrence and its declared U.SystemRoleAssignment species, does not prove that the project designated the holder. |
| Expected target vs actual result | An objective or target guides work; an actual change, produced entity, evaluation, delivery, acceptance, or later use needs the pattern and facts that define its relation to the Work. |
| Temporary work vs temporary organization | A team or organization may change while the same work whole continues, or persist across several work wholes. |
| Description coherence vs subject identity | Shared source events tempt authors to call project, process, and case accounts views of one entity even when their descriptions concern different entities. |
| Continuity vs. organizational change | Recover the actual history first; use a Work-continuity policy when interruption, replacement, split or merge leaves an identity question for the receiving use. |
A.15.6:4 - Solution
Recover the subject selected by the working concern. Use the pattern whose Solution answers that subject question, then relate plans, Systems, Transformations, results, descriptions, and publications through their own obtaining relations.
A.15.6:4.0 - Recover the subject before adding management detail
- Read the working question, not the management label. Ask whether it is about one performed Work whole, a reusable way, an organization of already identified things and relations, a transformation flow, or a named subject or claim being followed to closure.
- Name that subject in ordinary language. Use
A.15.1for Work,A.3.1for a Method,A.22for a selectedU.Structure,E.18for a transformation-flow structure, or the applicable rule for another subject or claim. - Add only the plan, system, assignment, change, result, description, evidence, or publication relations needed by the question, using their governing predicates and obtaining facts.
- Stop when the subject and the claim needed now are clear. Continue to section 4.1 for actual-project qualification, 4.2 for a process concern, or 4.3 for case closure only when that further question remains current. If a needed rule is absent, return the participants and that
missing-governor; a sufficient local rule needs no dedicated pattern.
A.15.6:4.0a - Select or reopen one bounded project focus
Use this branch only while the next decision depends on selecting or reopening the problem, project subject, solution form, Method relation, or development-platform contribution. If one already identified Work, Method, System, transformation, structure, episteme, capability, population, relation, or other subject answers the current question, use its pattern and stop rather than completing a project template.
Project-focus decision is Plain wording for one C.11 ChoiceResult over a current OptionSet. If options are still being invented, expanded, or reframed, complete that work under the Method that governs the project question. If the rows are only labels or fragments and the question is several complete ways to obtain the same result, stop here and apply C.38. Use C.18 when candidate retention or a comparison front is the unresolved question. Return when a current OptionSet exists.
When the result needs a reference, identify its C.2.1 episteme through all three discriminators. Preserve a durable representation when later access requires it:
| C.2.1 discriminator | Project-focus value |
|---|---|
| claim content | the complete interpreted claims that state the current C.11 inventory and result together with the five project-focus content groups below (C.2.1:4.1.1) |
EntityOfConcern | the DecisionSubject whose current choice result is being recorded, at the declared DecisionSubjectGranularity |
| effective reference scheme | one named project-decision scheme and edition whose designation, interpretation, comparison, and evaluation rules give the C.11 terms, alternatives, focus content, and result their meaning |
This aboutness choice lets one chooser revise the selected problem. Authority, commitment, budget ownership, Agent status, and performed Work remain neighboring claims under their own governors; none changes the EntityOfConcern merely by appearing in the decision record. One chooser’s C.11 result also does not establish a shared understanding or agreement among project participants. When that common basis is at issue, use A.1.STM:4.1 to compare their project-system and use accounts and resolve the consequential differences.
The minimally useful result carries the full C.11 choice discipline through five connected content groups:
- the observed situation, sought outside difference, and available bounded problem options in the current
OptionSet; - affected entities and interests, materially relevant alternatives, and one comparison basis: a
PreferenceOrderorEvaluativeMeasure, plus the currentBeliefStateandOutcomeModeland any decision-relevant dependence layer; - the selected option’s direct-subject disposition: one System, Method, capability, Work, episteme, population, relation, arrangement, or other admitted subject when that choice changes the decision, or an unresolved-subject disposition;
- the identified
DecisionSubjectandDecisionSubjectGranularity, oneChoiceRule, and, when an inquiry alternative is live under C.11, its probe-worthiness account usingProbeActionSet,ProbeBudget,CostToProbe, and the applicableValueOfInformationorValueOfComputation; and - one
ChoiceResult—choose now,reject current set,probe again, orreroute—with the receiving decision or use and any limitation needed to interpret it. Name the next question when further work remains, and retain an evidence horizon, material uncertainty or reopen condition when the decision or its recipient needs it.
Keep any inquiry limitation or reason needed by the decision or its recipient in the same result; inactive inquiry adds no placeholder or omission account.
Apply the C.11 ChoiceRule to the available basis. choose now may retain a lawful tie-set, or select a bounded problem whose option leaves its later direct subject unresolved and names the next question. reject current set applies when the rule excludes every current option. probe again requires a named feasible probe within the remaining budget whose expected decision-changing contribution justifies its cost; reroute applies when the question changes.
Close as choose now only when no feasible next probe is expected to change the survivor relation enough to justify its cost; close as reject current set only when no such probe is expected to rescue an option. In both cases retain C.11’s stable-current-set and local-choice conditions.
If the facts needed for a lawful result remain unavailable and no such probe or reroute is warranted, leave that premise and the unfinished comparison unresolved; this is not a fifth ChoiceResult. If the current set needs reframing, return to option formation at the start of this branch.
Stop when the lawful ChoiceResult and the reason it is lawful are recoverable. Changing the selected problem, OptionSet, comparison or acceptance basis, direct-subject disposition, ChoiceRule, ChoiceResult, or receiving decision changes the identity-bearing claim content and therefore identifies another episteme even when the chooser remains the same. Another supporting item, evaluation, or publication does not reidentify the focus episteme unless claim content, EntityOfConcern, or effective scheme also changes.
Call a later focus episteme another edition only when a C.2.1 EpistemeEditionRelation obtains under the named project-focus continuation rule: the later episteme uses the earlier one as its revision source; preserves the DecisionSubject as EntityOfConcern, the receiving-use lineage, and the scheme features that keep the decision interpretable; records every deliberately changed focus-defining claim or permitted scheme feature; and is not a fork, translation, retargeting, or independent reconstruction.
Shared chooser, performers, organization, budget source, label, or calendar alone establishes neither episteme identity nor edition continuity. Focus succession decides no performed-Work identity question.
Proceed by logical dependency, not by a compulsory Work sequence:
- problematize the situation and comparison basis. B.5.PI can expose a consequential question through an ordinary work occasion or a suitable mantra before a difficulty is felt;
- recover the result or use that makes the decision matter. For a systemic project question, A.1.STM first follows intended receiving changes at the operating time, including a possible future use, and moves from the system boundary to the larger whole and the joint functioning of its parts. A non-system or non-project question retains its own subject and grounds;
- compare candidate subjects for the current decision. Distinguish the common product SoI from a local system-in-hand, including an organization being engineered. Distinct usable product supplies can have their own SoIs under A.1.STM:4.1; a separate organizational project retains the product-use basis. Then investigate construction and creation using that basis. Keep functioning, behaviour, interaction, causal participation, intended Work, actual Work, and Method enactment under their own governors;
- compare materially different solution forms, which may be Systems, Methods, epistemes, arrangements, or combinations;
- designate a project Method-of-interest only when that Method’s identity, architecture, comparison, enactment, development, or maintenance is the question; and
- recover the Methods and arrangements used to develop it and the other Methods whose change affects the selected problem or solution.
Inspect the account through the lightest optional view that changes the decision:
| View | Working question | First useful result | Boundary |
|---|---|---|---|
| Problem factory | Which problem merits attention and resources, for whom, and under what comparison and acceptance conditions? | A lawful C.11 ChoiceResult over bounded problem options. | A lawful problem choice may leave its later direct subject unresolved. |
| Solution factory | Which materially different System, Method, episteme, arrangement, or combined candidates should remain, be selected, or be rejected? | A ChoiceResult with the current alternatives and the grounds supporting the result; include evidence needs and a reopen condition when the choice or its receiving use requires them. | The result records the choice. Candidate realization, an actual selecting Work occurrence, and any Method claim each need their own grounds. |
| Factory of factories | Which provider Systems, Methods, capabilities, tools, assignments, organization arrangements, and cultural practices enable or distort the first two views? | One bounded platform or organization-change ChoiceResult and its receiving contribution claim. | A platform improvement is not project success without receiving contribution and outside consequence. |
The development lemniscate is a didactic view of recurrent dependency and feedback among these questions. For a mantra or diagram, state whether the order shown is teaching order, logical dependency, Method unfolding, planned Work order, observed Work order, or feedback. Establish each ordering from its own grounds.
Return ordinary prose and add a small map only when it changes the decision. The account may be distributed across existing artifacts and may remain partly unresolved. A missing chooser, granularity, current option set, comparison basis, lawful choice result, direct-subject disposition, or receiving decision is a named stop or reroute—not an invitation to fill a project template. A missing performer basis or authority claim leaves only a selected claim that depends on it unresolved. An actual project occurrence enters section 4.1 and receives its identity only as admitted composite U.Work.
A.15.6:4.1 - Recover an actual project as composite U.Work
In Plain use, actual project denotes one temporary composite U.Work occurrence: the performed work whole, with a start and a completion or termination condition. The performing organization or cooperating performer Systems remain distinct from the Work. Any claimed collective System needs its own A.1 recognition basis.
The intended work and result are described in a U.WorkPlan or other intention episteme; the system being created or changed has its own identity. A continuing organization can perform successive or overlapping projects and ongoing operational work. A project-focus decision, authorization, schedule, budget, dashboard or repository is a neighboring object or claim; none supplies another identity for the performed whole.
Admit the candidate composite under the full A.15.1:4.1 test, including the A.1:4.2 common construction of that same occurrence. While it is a candidate U.Entity, ground its construction and performance facts independently. Recover every actual performer’s A.13 core: the admitted System, local agential system-role kind and classification, obtaining assignment for the scope, working situation and window, evidence adequate for the local criterion and classification, and any characteristic profile consumed by a Grade, autonomy, criterion-dependent or assurance claim.
A.15.1:4.1 also governs the Method actually followed, temporal extent and complete-occurrence containment under a declared local rule; the containment facts precede the typed Work-containment assertion. Reuse an already established full admission result when it covers this occurrence.
Admit each included Work occurrence independently. After the composite is admitted as W : U.Work, assert its grounded typed enactment, containment and Work-part relations. An admitted part or a temporal inclusion alone does not admit the whole or establish Work parthood. If a common or Work-specific premise is unknown, leave the dependent admission unresolved; if a necessary condition fails, reject that proposed basis while retaining independently supported facts.
When precise assignment-bound attribution is current, use F.6 afterward to relate the admitted Work to each performer’s same obtaining A.13 assignment, preserving direct case support, holder equality, species, participants and coverage. A short attribution account may omit an unused identifier only when every required link remains recoverable. F.6 is not an admission premise. Apply these five project-specific qualification tests to the independently admitted Work:
- The composite work has a temporary or transient boundary with a start and a completion or termination condition.
- An accepted intention episteme states the intended objective and any intended product, service, result, or value. For this qualification, either an existing direct predicate connects its intended-performance designation to the admitted Work and obtains, or one local claim under A.15.2 or A.6.RCD names the plan or decision, designation, Work, applicable policy, and independently obtaining Work facts. An absent predicate, applicability condition or required occurrence rule returns
missing-governor; unavailable constructor semantics for a proposed local derivation returnmissing-substrateunder A.6.RCD. When the governor exists, preserve its inapplicable result or use test 5’s reason-specific result for the applicable test and available facts. Do not imply a generic plan-or-decision relation. - Apply A.15.1’s Work-part and identity rules. When interruption, resumption, split or merge leaves an identity question that the receiving use must resolve, use the applicable continuity policy to interpret the actual history.
- At least one independently admitted performed Work occurrence is connected to the composite Work by an obtaining work-part relation.
- For each claim used to qualify the project, name what the claim is about—the participating system, affected referent, transformation, result referent, or another subject actually asserted—and say how that subject matters to the Work. Choose a claim form whose rules fit that use: an obtaining direct relation; a typed
A.6.1binding for a reusable-operation application; a local production, inception or completion claim underA.15.PROD; or another local claim underA.6.RCD. If the claim cannot be asserted, preserve independently established facts and return the reason-specific outcome fromA.6.P.WMR. Distinguish a failed applicable test for the attempted polarity, missing deciding facts, an absent governing rule, known inapplicability and missing constructor semantics. A negative claim additionally needs its own non-obtaining criterion or complete closure basis and satisfying facts. A missing rule calls for the lightest sufficient contribution under A.6.RCD, not automatically a new relation kind or pattern.
No performed work means no actual project occurrence yet. A proposal, charter, authorization, schedule, budget decision, or funded intention can establish a U.WorkPlan and related commitments. It does not backdate performed work, a future system, an assignment, an actual change, or a result.
The project occurrence uses the identity, temporal extent, parts, episodes, continuity, and relation-specific aggregation defined in A.15.1. Project wording adds no second identity rule. When a reader asks for the project result, ask first: What is the result, and result of or for what? Keep that referent in the kind or claim already established for it, then apply test 5 to the proposed relation or claim.
A failed applicable test supports only non-assertability of the attempted polarity; a negative claim requires its own applicable non-obtaining criterion or complete closure basis and satisfying facts. Preserve any independently established actual subject and facts when the attempted result relation remains unsupported. Keep a merely intended target in the plan.
Whole-project roll-up requires obtaining work-parthood plus an aggregation policy defined for the one relation and measure being aggregated. Outputs, effects, verdicts, epistemes, deliveries, and uses do not become one result merely because they share the project label.
A.15.6:4.1a - Connect project work, the system-of-interest and the local subject
Start with the local work and its purpose in an ordinary sentence: this temporary work is intended to establish this result for this product use or other stated receiving purpose. Name the composite project U.Work when it has been performed; while it is only intended, name the U.WorkPlan. Recover the actual subject or intended-subject designator, the plan or decision that selected it, the change or use being pursued, and the next decision needing that account. For organizational work, distinguish the creator being engineered, its promised capability, the local result and the product use that gives them their reason.
The system-of-interest (SoI) is the product System that a particular extended enterprise is organized to create, change, sustain in use or retire. The extended enterprise is the organization System. Keep it distinct from performed work and work plans; section 4.1 supplies the conditions for admitting actual composite project Work. Agents acting for the participating organizations establish or accept the objectives and commitments. Several projects can serve the same SoI. The current subject of inquiry or local work answers what must be understood, obtained or changed now; for a system, use system-in-hand or our system with the relevant participant’s relation stated.
A product undertaking can supply a usable test rig to laboratories and have that instrument as its SoI. A project developing the pump-test laboratory engineers a creator whose capability is justified by the pumps’ qualification needs. A contract, performer or budget change for that same work does not change this distinction. Several products and other results can matter to one project; retain each use and the shared constraints relevant to the decision.
A.1.STM:4.0–4.3 develops this use basis. It follows receiving changes at the selected operating time and moves from the system boundary to the larger whole of which the system is, or is intended to be, a part. The joint functioning of that whole’s parts grounds the system’s required contribution before the reasoning turns inward to construction and backward to Methods and creator contributions. If that whole is unknown, the missing account must be investigated before relying on a dependent function or construction judgement.
A.1.STM:4.1.1 connects organizational design, provision and finite acceptance through the required product use and creator capability. The organization remains engineerable even when it is sold as a business. A new product supply requires its own use and bounded fitness obligations; an economic product label alone supplies neither. A local result can close while wider use remains open.
Research has its own epistemic acceptance, including a supported negative result; when it serves a capability decision, its fitness for that decision is an additional question. Keep a missing or contested system-and-use basis open only where the current systemic question needs it.
When the designated system already exists, identify that same entity under its admitted U.System kind. The plan or decision may say why it matters to the project. Links come from relations that obtain: a work-to-referent or work-to-change relation, one independently identified Transformation, a branch-local A.15.PROD production or inception claim, an evaluation, a participation or use relation, or another separately defined direct relation. Include only links used by the named decision.
When the System is only intended, agree the SoI role, required holder characteristics and intended use while keeping the holder’s designator inside the U.WorkPlan, decision, System description, or other claim episteme. Before its identity rule first holds, there is no future U.System, system-role-assignment holder, or Transformation of that not-yet-existing System. A.15.PROD may later state the identity-inception boundary.
After inception, relate the actual System to the earlier description through the applicable reference or identity claim, then test project designation, participation, local system-role classification, and any assignment at their own times.
For a series or family, keep the common requirements and the later individual holders distinct; a specification or collection does not become one System. A.1.STM:4.2 develops this case.
Project designation, local system-role classification, and system-role assignment are separate claims. The ordinary explanation is sufficient while participants only need to understand the system’s place in the cooperation. When classification matters, identify the local system-role kind and its feature criterion under A.2, then test the actual System against it. A local SystemOfInterestSystemRole using this Library meaning must express the named extended enterprise, its agreements for the product’s creation, change, sustaining in use or retirement, the intended use or withdrawal from use and designation grounds under A.1.STM:4.1. A criterion selecting whatever an observer investigates or engineers answers a different question. Calling an organization that kind does not replace the product SoI in organizational work.
When assignment identity or its window matters, select a declared U.SystemRoleAssignment species under A.2.1. Recover its holder position, declaration-local assigned-kind domain, predicate, applicability, additional participants and occurrence rule. Use a system-role kind value only if it belongs to that species’ declared domain, and assert an occurrence only when its obtaining facts satisfy the declaration. Classification is a prerequisite only if those rules consume it. An assignment can therefore be established without a separate holder-classification claim.
A missing declaration, required rule or deciding fact leaves the typed assignment unresolved. An inapplicable declaration or a failed obtaining test does not support that assignment claim. Retain an independently supported ordinary designation.
A patient record, damage claim, measurement result, or other non-System case subject can remain central to project Work but cannot be classified under a system-role kind or hold such an assignment.
When one project question spans operation or use of the project system-of-interest together with production, identity inception, later change, verification, feedback, or recursive builder questions, E.18.NET may select the relevant independently identified TFS or nested-network members. The selection must pass its four A.22 discriminators: direct members, obtaining cross-member relation occurrences, applied constraints, and one networkUseFrame; all endpoint bindings must resolve.
If a member or relation is ungrounded, keep a Plain proposed network explanation and name the missing member, governor, false or unresolved predicate, occurrence, or binding. The selected network is a non-agentive U.Structure. Work membership in a project requires obtaining A.15.1 work-parthood.
When the network-selection judgment needs a separate reference, identify the C.2.1 result episteme whose EntityOfConcern is the selected network and whose claim explains its use under the stated basis and qualification window. A durable representation may preserve access. Project Work, changes, case closure, production, evidence and decisions retain their own claims.
Use the lightest claim that answers the project-selection question. A plan or decision designation and every independently obtaining Work, change, production, evaluation, delivery, acceptance, or use fact remain usable. Often the ordinary sentence “this plan designates PumpUnit-3 as the system this upgrade is about” answers a local designation question; do not construct a conjunction around it. It does not by itself establish the participants’ common SoI, agreement or expected contribution. Keep the larger systemic question at its own scope through A.1.STM.
For one bounded decision that needs the combined truth, a C.2.1 local compound claim may cite the named plan or decision, composite Work, actual System, direct facts, applicability, and case facts. Its constructor semantics must be recoverable, but A.6.RCD does not require a separately materialized substrate document for a simple one-case claim. Name and pin the substrate when the derivation is nontrivial, intended for interoperability, used as proof, or reused.
Repeated parameterized use may justify a reusable predicate-definition episteme. Admit a relation kind only when a named receiver also needs distinguishable project-selection occurrences with their own identity.
Return missing-substrate[project-selection-conjunction] only when the stronger compound claim is needed and no substrate supplies the proposed operator semantics. The blocker stops that compound claim; it does not invalidate the plan designation or any direct fact.
For PumpUnit-3, the plan and upgrade decision designate the pump, while the admitted composite Work, Work parts, and pump-change facts remain supported independently by their defining patterns and facts. That answers the local designation and Work questions; the common SoI and use basis is supplied separately through A.1.STM. Open a compound local claim only for a decision that consumes the conjunction, and materialize or pin its substrate only under the conditions above.
A.15.6:4.2 - Recover a process concern through U.Method, a selected U.Structure, or TransformationFlowStructure
When the question is about repeatability, ordering, throughput, variation, control, or improvement, select the subject that the claim concerns:
U.Methodfor the reusable way of doing;- a
U.Structureselected underA.22when the organization of already identified method-side objects and relations changes the next question or admissible action; TransformationFlowStructurewhen the question concerns the organization of transformation flows.
Keep a measure, evaluation result, relation occurrence, event collection, or dated Work as its own subject when that is what the claim asserts.
For a method-side U.Structure, identify the constituents, the selected obtaining relations, the applied constraints, and the use frame: selection question, admissible action and stop or return condition. These are A.22’s four identity discriminators. Only then may MethodRelationStructure serve as a local designator. If any discriminator is absent, keep the direct relations unbundled. An explanatory warning may help a reader but is outside that identity unless it changes a constraint or the use frame.
A Work occurrence supports only facts grounded in its history and relations. For Method enactment, establish A.15.1 enactsMethod for that Work and Method. For an operation application, identify its A.6.1 declaration, application and argument/result bindings. A trace or record may supply evidence; a shared label, compatible result or record presence alone establishes neither predicate and does not retype Work as a Method or structure.
Do not force multi-object event data into one preselected case key or one flattened sequence. Preserve the relevant object and event relations, then select a process execution, grouping, query, or constraint only when the use needs it. The selection is a modeling decision.
Identify any selection-result episteme under C.2.1 from what its claim-bearing whole concerns: observed material, a selected structure, a rule or another independently identified subject. Its use as evidence requires an obtaining evidence-use relation. Method identity retains its own grounds. Stop when the reusable way, selected organization, or transformation-flow question has been answered.
A.15.6:4.3 - Recover a case concern through one named subject or claim
A case label is a cue to read the closure question. Recover:
- the named subject or claim and the rule that identifies or defines it;
- only the Work, changes, conditions, measurements, evidence, decisions, and references used by this closure question;
- the applicable rule and facts that define the closure basis;
- any later receiving use that matters to this closure or to the current receiving question, kept outside the closed case.
The subject need not be one continuing changed entity. It may be any independently identified thing or claim needed by the closure question—for example, a maintained System, patient, material batch, episteme edition thread, characteristic bearer or assignment, measurement or result episteme, relation occurrence, decision, Work occurrence, or selected edition-lineage structure. Each keeps its own identity rule. Changed claim content identifies another episteme; a measurement claim identifies its own bearer and value.
Do not infer the case subject from a log’s case key or from one record format. Object-centric evidence may connect several objects and several possible groupings. Select the grouping the closure question needs and state any information lost by flattening that limits that use or could mislead its reader. CMMN, DCR, Declare, and similar notations can help represent flexible case work. Evaluate their usefulness and ease of use for that representation task; establish the case subject, closure and any asserted Work from their own grounds.
When case claims need separate reference, identify their C.2.1 epistemes from the claim-bearing whole. Several independently identified participants may occur in one account with one truthful EntityOfConcern. Split the account when that concern would be untruthful or the combination would break the identity or comparison needed by the use.
A closure question may concern an independently identified grouping, query or result episteme. Select a structure under A.22 when a current or later use needs that organization and its four discriminators pass; otherwise keep the sufficient direct claims.
You may state the working boundary without asserting a new relation. If a later use requires a relation from the closed case to that use, recover its participants and apply an applicable predicate or sufficient local claim. Return missing-governor only for an absent rule needed to state or test that relation; distinguish missing deciding facts and a failed positive test under section 4.1.
Establish closure and change through the predicates and facts that define those claims. A Method or completed Work may contribute to their grounds, but neither alone supplies the closure or Transformation test.
A.15.6:4.4 - Do not force the three readings into one view family
Project, process, and case wording is only a cue to inspect the claim. Under C.2.1, each description is identified through its claim content, the EntityOfConcern recoverable from that content, and the effective reference scheme; a management topic does not assign that EntityOfConcern.
| Description wording | Recover the EntityOfConcern from what the claim says |
|---|---|
| project cost, completion, or result | Select the composite project U.Work only when cost, completion, or another predicate is asserted of that Work. If the claim is about a measure, transformation, produced entity, value, condition, verdict, decision, relation occurrence, or result episteme, select that named subject instead. |
| process repeatability, variation, throughput, or improvement | Select U.Method only when the claim concerns the reusable way; select an A.22 U.Structure or TransformationFlowStructure only when it concerns that admitted organization. Otherwise select the measure, evaluation result, obtaining relation, relation-bearing claim, or admitted collection-as-whole of occurrences asserted. |
| case condition, trajectory, closure, or next downstream use | Select the subject or claim named by the closure question: a continuing referent and its conditions, an episteme edition thread, characteristic bearer or assignment, measurement or result episteme, relation occurrence, Work, decision, or another identified subject. Name a downstream receiving use when the current question needs it, and keep it outside the closed case. |
One description keeps one truthful EntityOfConcern for its claim-bearing whole, including any independently identified relational participants. Use separate epistemes when combining the claims would make that concern untruthful or defeat the needed identity or comparison. When accounts must be related, keep their C.2.1 identities and state the correspondence relations required by their use.
If an account is claimed as a U.View, E.17.0 additionally tests its conformance to a viewpoint episteme’s concern and rules. Ordinary related accounts need no viewpoint-conformance claim. Shared source events alone establish neither that conformance nor the required correspondence.
If the description needs empirical grounding, identify the admitted grounding holon and the EpistemeEmpiricalGroundingRelation defined by C.2.1. GroundingHolonSlot belongs to that relation’s RelationSignature; it is not a slot of the description episteme. Project Work, U.Method, a selected method-side U.Structure, TransformationFlowStructure, transformation, and affected referent do not acquire episteme or grounding-relation slots from the account.
For process and case descriptions, readability, simulation support, and ease of use are properties of the representation in a stated use. They can change which representation a team chooses, but they do not identify the described subject, establish claim truth, close a case, or prove that Work occurred.
A.15.6:4.5 - State project-local relations
An existing @Project name is a compatibility and retrieval cue. It does not establish identity, parthood, authority, viewpoint, or locality.
When a record or relation is local to one actual project, identify the composite U.Work and the obtaining relation that makes it local. Use the following typed references when the chosen representation needs reference fields:
| Referenced object | Reference head |
|---|---|
| the selected composite project-work occurrence | projectWorkOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work |
| another work occurrence | workOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work |
| a repeatable method | methodRef : U.EntityRef, constrained to ValueKind U.Method |
| a selected method-side structure | methodRelationStructureRef : U.EntityRef, resolved to the U.Structure selected under A.22; the local designator MethodRelationStructure adds no kind or identity constraint |
| a transformation-flow structure | transformationFlowStructureRef : U.EntityRef, constrained to ValueKind U.Structure |
| the entity being changed | affectedReferentRef : U.EntityRef, narrowed to the ValueKind already admitted for that entity when the reference must carry that constraint |
Use projectWorkOccurrenceRef only for the identified project-work occurrence.
A.15.6:4.6 - Apply work continuity rather than label or focus continuity
Project-focus succession and actual-project Work continuity are different questions. A changed focus-defining claim, EntityOfConcern, or effective scheme identifies another C.2.1 episteme. It becomes another focus edition only through an obtaining EpistemeEditionRelation under the project-focus continuation rule in 4.0a; a same chooser or label is insufficient. Neither another focus episteme nor an edition relation continues or reidentifies performed Work. Conversely, one composite Work may continue under its declared A.15.1 policy while its focus episteme changes.
For interrupted, resumed, split, merged or performer-changing project Work, recover the actual history and apply A.15.1’s identity and Work-part rules. Use a continuity policy when the named use needs a boundary judgment:
- performer or team replacement changes participation and A.13/F.6 bases but need not change parent-Work identity;
- interruption and resumption may be episodes of one parent Work or later occurrences; establish their identities and the applicable part or locally declared resumption relation, using a continuity policy only for the remaining ambiguity;
- split and merge require independently identified Works and the obtaining Work-part or other direct relations claimed; predecessor or successor wording needs its own governed predicate;
- failed or terminated Work remains actual project Work even when its intended result is absent or adverse; and
- continuous operations qualify as a project only when one finite composite Work first passes independent A.15.1 admission and obtaining work-parthood, then passes the five project-specific qualifications; any precise assignment-bound performer attribution is a separate later F.6 result.
The organization performing or coordinating project Work is a neighboring U.System. Organization, project-focus, DecisionSubject, or label continuity does not decide project-Work continuity.
A.15.6:4.7 - Use the recovered subject and stop
Section 4.0 is the first pass. Sections 4.1–4.6 add only the branch detail needed by the current question. The worked cases below point back to those tests instead of restating them as new admission rules.
Stop when the subject, the required relation or claim, and its basis are clear. Continue to A.15.7 only when ongoing Work now needs a next-action choice. When observations or evidence about several performances support competing candidate ways, use A.3.1.MR. For a proposed way in documentary guidance, use A.3.1.DR when its source meaning or status needs recovery. Apply A.3.1 directly when a candidate way is ready for the Method identity test. A later decision, publication, evidence, or assurance question opens its own pattern rather than extending this recovery indefinitely.
A.15.6:5 - Archetypal Grounding
The following constructed cases illustrate the distinctions with stipulated admission and relation facts; they are not field observations. Whenever a case stipulates an admitted Work, that premise includes the full A.15.1:4.1 test for that occurrence, including its independently grounded A.1:4.2 common construction and complete-occurrence containment facts under a declared local rule. The Work-specific facts highlighted below explain the case; they are not a replacement admission test.
Integrated pump-modernization case: one project, several subjects. Before performance, PumpUpgradePlan-7 : U.WorkPlan describes intended upgrade Work, the existing PumpUnit-3, a proposed replacement controller, and expected later pumping use. At this point there is no actual project Work, no replacement-controller System, and no achieved vibration reduction.
The stipulated upgrade history runs from 08:00 UTC on 2026-07-20 to 16:00 UTC on 2026-07-23. The candidate composite occurrence has an independently established A.1:4.2 common construction. Its performers, MaintenanceTeam-4 and ControllerAssemblyCell-2, are independently admitted Systems. The local UpgradeCoordinatorRole and ControllerProductionPerformerRole criteria require respectively goal-directed upgrade coordination and condition-sensitive controller production; observations support those classifications. The declared UpgradeCoordinationAssignment and ControllerProductionAssignment species assign those kinds when the project designation and relevant control connection obtain. The stipulated designations and connections establish RA-Upgrade-Team4 and RA-Controller-Cell2 for the stated scope and window.
The performance history shows the composite following PumpUpgradeMethod-E7. Under the declared local containing-System predicate, the complete candidate history satisfies the boundary, window and other applicability conditions of admitted PlantMaintenanceService-3. These and the full admission premises stipulated above establish PumpUpgradeWork-7 : U.Work; the typed enactment and containing-System relations can then be asserted.
The diagnosis, bearing-replacement, controller-production-and-installation and qualification Works are independently admitted. Their assembly and performance facts, together with admission of the composite, support four obtaining Work-part relations. F.6 is checked separately when precise assignment-bound attribution through the same assignments is needed. A common timestamp or project label supplies no Work parthood.
The five project qualifications add only what this use needs. A local C.2.1 claim may record that the admitted composite Work fulfilled the intended-performance designation under the stated policy; the claim uses that local rule. MaintenanceTeam-4 and ControllerAssemblyCell-2 remain the performer Systems, with identities distinct from the project Work. A failed pump-qualification test may leave actual project Work while the intended result remains unachieved.
Apply section 4.1a to the project system-of-interest. The operator, controller supplier and maintenance organization have agreed the upgrade work and responsibilities, forming the extended enterprise for this alteration. Their plan and upgrade decision designate the already existing PumpUnit-3; direct Work-to-pump and Work-to-change facts separately say how the pump matters. Classification under a local SystemOfInterestSystemRole and any assignment occurrence require their own tests. A proposed controller remains plan content until its identity rule first holds; production completion, later operation, classification, and assignment are separate claims.
Apply section 4.3 separately to the pump, calibration, and controller-production cases. The pump case follows pump condition through repair and test while later pumping use stays outside closure. The calibration case follows TestRig-2 and the calibration facts used by qualification. The controller-production case closes only when the applicable Work, change, inception, completion or readiness, evidence, and decision facts support that result.
Any Work-realized change separately names the performer System with its A.13 basis, Work, changed referent, and the relation connecting Work to change, plus F.6 attribution only when the receiving question asks under which assignment the Work was performed.
Apply section 4.2 to the process question. BearingDiagnosisMethod-4 is the reusable way. An A.22-selected enactment-review structure may organize independently admitted Work and the obtaining relations that state which Method each occurrence enacts, but it neither composes the Methods nor proves pump change. If event data links the work order, pump, controller, test rig, measurements, and several Work occurrences, keep those object relations visible; select a grouping or query only for the question being answered.
Expected and actual results remain apart. A vibration target in the plan is intended. A pump Transformation, production result, evaluation episteme, delivery, acceptance, and later use each need their own pattern and facts. If result wording hides the relation, apply A.6.P.WMR and return its one applicable outcome. Whole-project roll-up requires an obtaining Work-part basis and one policy for the stated relation and measure.
After the project completes, PumpingRunWork-8 is separate Work unless an obtaining Work-part relation says otherwise. Likewise, controller-production and pump-test transformation-flow structures remain independent. Select an E.18.NET network only when the engineering question needs both and the required cross-boundary relation occurrences obtain. The selected network has its own A.22 structure identity.
Receiving decisions. A cost question requires the resource-use facts and accounting rule in addition to Work parthood; this case supplies no cost ledger, so the total remains open. To improve diagnosis across upgrades, the team compares outcomes of independently grounded BearingDiagnosisMethod-4 enactments under the same diagnosis criterion. To decide whether PumpUnit-3 may return to service, it applies the pump case’s acceptance and release conditions. If the final vibration test fails, that last use remains blocked while the performed upgrade and diagnosis observations remain available. Repair is planned from the failed condition; the failure does not erase earlier Work or establish a new Work-part relation.
Construction case: bricks become a wall. Vasya performs one bounded wall-building occurrence. For the project question, the stipulated full A.15.1:4.1 basis admits that occurrence as composite U.Work; its independently admitted parts and obtaining Work-part relations support the project qualifications in section 4.1. Keep the intended wall description, resources, completion condition, and any actual-change, identity-inception, or completion claim separate.
For the process question, select the repeatable bricklaying U.Method; use an A.22-selected U.Structure only when its four discriminators make method-side organization matter, or TransformationFlowStructure when transformation-flow organization matters. Vasya’s Work supports an enactment observation only when A.15.1 states that it enacts the Method. A declared operation application instead needs its A.6.1 declaration and typed binding.
For the case question, follow the subject named by closure: pre-existing bricks or other continuing materials for actual A.3.4 changes, a production or identity-inception claim while the wall comes to exist, or the continuing wall only after inception. Do not give a not-yet-existing wall a transformation history. These are related project, process, and case subjects, not three kinds of one object.
Medicine case: a patient episode. Consider a hospital improvement initiative whose composite occurrence passes the full A.15.1:4.1 test and whose independently admitted Work parts are connected by obtaining Work-part relations. It introduces and evaluates a new care arrangement; apply section 4.1’s five tests to qualify it as project Work.
The clinical-pathway concern selects U.Method, an A.22-selected U.Structure only when its four discriminators make care-method organization change the next action, or TransformationFlowStructure when the question concerns care-flow organization. Evaluation across Work occurrences uses only occurrences for which A.15.1 states the enacted Method, or for which a declared A.6.1 operation and typed application binding support the observed fact.
One patient’s changing condition is the case concern only when that is what the claim asserts; diagnostic claims, treatment Work, evidence, and decisions remain separate subjects and relations. The improvement plan, care team, patient record, and performed clinical Work likewise retain their own identities.
Learning case: a course redesign. The finite redesign effort is composite project Work when its occurrence passes the full A.15.1:4.1 admission test and section 4.1’s project qualifications, with independently admitted parts and obtaining Work-part relations.
The teaching U.Method, an A.22-selected U.Structure used only when its four discriminators make teaching-method organization change the next action, and TransformationFlowStructure for learning-flow organization are distinct possible process subjects tested across cohorts.
One learner’s changing mastery is a case concern only for claims about that learner or condition. Use C.2.1 and E.24.PUB to distinguish the epistemes and publications encountered through a syllabus, progress card, and course dashboard; none is the performed redesign, teaching Method, structure, or learner.
Research case: an experimental materials campaign. The finite campaign prepares alloy specimens, performs load tests, and analyzes measurements. Admit its composite occurrence under the full A.15.1:4.1 test, then assert the grounded relations to independently admitted preparation, testing and analysis Work parts and apply section 4.1’s five project qualifications.
Identify the reusable experimental U.Method separately from the protocol episteme; the latter is a MethodDescription only under A.3.2. The selected preparation-test-analysis organization is a transformation-flow structure only when that organization changes the research decision. Each specimen remains the affected referent followed through preparation and testing. Identify the claim-bearing epistemes under C.2.1, keeping the hypothesis, preregistration claims and measurement results distinguishable. Use E.24.PUB to identify their expression and publication uses, including the article. A surprising measurement becomes a Problem only when the C.22.PFR condition and applicability relations obtain.
Project progress, protocol improvement, specimen history, result interpretation and publication can therefore change independently.
A grounded result that rejects the proposed alloy hypothesis can meet the research acceptance criteria. If the campaign informs a product or creator-capability decision, assess that contribution separately; it establishes neither a usable product nor the capability itself.
Situation-wording contrast. The Plain word situation does not select one common kind.
- An operating pump configuration comprises the admitted
U.System, its parts, and state relations, plus Work or transformation only when the account asserts those facts. - A proof gap is carried by the proof episteme and the named unresolved-consequence and proof-acceptance applicability relations needed for the proof decision.
- A multi-party emergency comprises the participating Systems, actual Transformations, response Work, and relevant temporal or causal relations; an emergency description is a separate episteme.
- A future scenario is a
U.MethodDescriptiononly when the same episteme meets A.3.2’s criterion for describing one independently admitted Method. A possible-state description keeps its own claim content; describing a future state alone does not admit a MethodDescription.
Recover those subjects and relations.
Incident wording. Recover what the decision or action needs: the actual event or bounded change, responsive U.Work, participating Systems, obtaining relations, and any incident-description episteme or publication used. An incident record conveys claims about those subjects; establish their identities from the applicable rules and facts.
Planning-only boundary. A funded proposal with objective, schedule, assigned team, and charter can establish intended project work and a U.WorkPlan. An actual project requires a composite occurrence that passes the full A.15.1:4.1 admission test and section 4.1’s project qualifications, including independently admitted parts and obtaining Work-part relations. Until then, keep intended work and its estimates in the plan and leave dependent claims of actual project cost, result or completion unestablished. Retain independently supported facts about any performed part. F.6 may add precise assignment-bound attribution only after Work admission; the first task or its timestamp alone does not admit the composite.
A.15.6:6 - Bias-Annotation
This pattern has a project-recovery bias because project wording is widespread in FPF names. The process and case branches prevent that bias from making composite work the subject of every management claim.
It has a 4D work-occurrence bias for actual projects. The guard has an order: first A.13-qualified performer facts and A.15.1 Work admission with obtaining work-parthood; separately, F.6 attribution when a precise assignment-bound claim is current; apply the five project-specific qualifications to the independently admitted Work.
A temporary organization, plan, Transformation, product, dashboard, or time-contained occurrence remains a neighboring object unless the admission and qualification facts establish the composite Work and the claim is about it.
The examples include engineering, medicine, and learning to resist software-document bias. Working product is Plain recognition wording. Recover the entity under the pattern that defines or constrains it, then state the production-work, entity-identity-inception, changed-referent, measurement, evaluation, delivery, acceptance, or later-use claim that the decision needs. Keep the Plain wording only while the needed relation or claim remains recoverable.
A.15.6:7 - Conformance Checklist
- Start with section 4.0: read the claim and name the subject it concerns rather than interpreting the management label as a kind.
- For an actual project, apply A.15.1 to the composite
U.Work, then the five project qualifications in section 4.1. Planning material remains content of itsU.WorkPlanuntil Work occurs. - Use obtaining Work-part relations and A.15.1 identity rules; apply a continuity policy only for the boundary question the receiving use needs. A time interval, team, charter, repository, policy or label establishes neither parthood nor continuity.
- For a process concern, choose among
U.Method, an A.22-selectedU.Structure, andTransformationFlowStructureas section 4.2 states. Ground each evidence use in the claim it supports: Method enactment needs the A.15.1 relation; an operation-application result needs its A.6.1 declaration, application and bindings; a timing, cost or condition claim needs its own relevant evidence. A report of admitted Work keeps its full admission basis recoverable under A.15.1:4.4 without repeating all of it in each narrow claim. - Preserve multi-object evidence until the current use selects a grouping, query, or constraint. State omitted information when it limits that use or could mislead its reader. Identify the selection result from its claims under C.2.1; it can be a case subject when its independent identity and the closure question warrant that use. Method and Work claims retain their own admission grounds.
- For a case concern, name the subject or claim, the references used by closure and the closure basis. Name a downstream use when it matters to the current question and keep it outside that closure. Keep any case-record episteme under its own identity.
- Recover each description’s claim content, EntityOfConcern, and effective scheme under C.2.1. Treat notation readability or simulation support as a representation-use question, not as subject identity, claim truth, case closure, or performed Work.
- Recover the product, named extended enterprise and agreement basis for a SoI designation under section 4.1a, keeping the local system-in-hand and finite acceptance of organizational work distinct. System identity, designation, local system-role classification and any assignment occurrence remain separate in every direction. Do not backdate a future System.
- Use section 4.1a for a project-selection account. A direct designation may answer the ordinary case; a stronger compound claim needs recoverable constructor semantics, and
missing-substrateblocks only that stronger claim. - Keep performer, Work, change, result, success, acceptance, evidence, decision, description, publication, and later use as separate claims. Apply the pattern that defines or tests the current relation.
- For result wording, name the referent and say what it is a result of or for; then use the applicable A.6.P.WMR outcome. Whole-project aggregation also needs its Work-part basis and relation-and-measure policy.
- Use E.18.NET only for independently identified transformation-flow structures connected by obtaining cross-boundary relation occurrences. Work membership in a project requires obtaining A.15.1 work-parthood.
- For a Transformation, first identify the actual bounded change and continuing referent. Add an actor-side or Work-realization claim only when its own predicate and facts establish it.
- Reuse of one Method or transformation-flow structure elsewhere has its own enactment or selection facts and creates neither cross-project Work parthood nor cross-case identity.
A.15.6:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Charter-created project occurrence | Authorization or funding is counted as performed project work. | Keep the U.WorkPlan and any separately defined decision claim; admit actual project work only after the complete A.15.1 occurrence basis obtains. |
| Interval-made work part | An occurrence is called part of project Work because its timestamp lies inside the chosen project interval. | Admit the occurrence and composite Work independently, then state the obtaining work-part relation. Otherwise retain only the temporal relation. |
| Team-is-project | The temporary organization and the work it performs share one identity. | Identify the organization as U.System, the project as composite U.Work, and connect them through participation relations. |
| Occurrence-is-process | One successful or failed execution is treated as the repeatable Method, or a local structure label is treated as an admitted process object. | Select U.Method, an A.22-selected U.Structure, or TransformationFlowStructure according to the claim. Fill all four A.22 discriminators before locally calling the structure MethodRelationStructure; otherwise keep direct relations unbundled. Work supports a Method-enactment observation only when A.15.1 states which Method it enacts. An operation-application observation instead needs the declared A.6.1 operation and typed application binding. |
| Case-file or changed-entity substitution | A record replaces the subject, or every case is forced into one continuing affected entity. | Read the closure claim, select the EntityOfConcern it names, preserve episteme-edition, characteristic or measurement, relation, decision, result, and continuing-referent identity laws, and keep the case file as a separate episteme. |
| Three-view collapse | Project, process, and case topics assign subjects to descriptions and accounts with different subjects are published as one multi-view description. | Recover one truthful EntityOfConcern from each claim-bearing whole. Split only when combining claims would make that concern untruthful or defeat the needed identity or comparison. Add the correspondence required by the use; test viewpoint conformance only for a claimed View. |
| Suffix-provided locality | @Project or @BoundedContext is expected to establish identity, authority, or a selected structure. | Name the obtaining relation and referenced object; use a typed reference when the chosen representation needs one. For a method-side structure, fill A.22’s four discriminators; no suffix contributes locality or identity. |
| System-role-kind-by-label | A System is classified under SystemOfInterestSystemRole because someone called it the project system-of-interest. | Keep an ordinary project designation when sufficient. For classification, identify the local system-role kind and test its A.2 feature criterion. For assignment, independently select the A.2.1 species and test its declaration-local domain, predicate, applicability, participants and occurrence conditions. Require holder classification only when that declaration consumes it. |
| Assignment proves project designation | An obtaining system-role assignment is treated as proof that one project designated its holder. | Use the designation stated by the named plan or decision for the ordinary claim. If a named decision consumes a compound selection truth, use the lightest A.6.RCD disposition and keep assignment, Work, change, and use facts separate. |
| Backdating a future System | A planned controller or plant is treated as an admitted System, classified under a local system-role kind, or made an assignment holder before it exists. | Keep the designator and expected use in plan content; after identity inception, test designation, classification, and assignment separately. |
| Project-result field | Entities, values, conditions, choices, measurements, verdicts, decisions, relation occurrences, changed referents, and claim-bearing epistemes are grouped as one intrinsic result of the project. | Ask what the result is and what it is a result of or for. Keep that subject in the kind or claim already established for it, then choose one WMR outcome. If the attempted claim cannot be asserted, preserve independently established facts and return WMR’s reason-specific stop, including the rule’s inapplicable result or missing-substrate when applicable. An absent governing rule calls for A.6.RCD’s lightest sufficient contribution. |
| Network-is-project | A network of transformation-flow structures is treated as the project, workflow actor, or work-breakdown structure. | Keep the E.18.NET structure non-agentive and include Work in the project only through obtaining A.15.1 work-parthood. |
| Probe-is-constructor | The A.6.RCD:4.2 conjunction row or a reference scheme is treated as if it supplied constructor semantics. | A simple one-case claim may use recoverable constructor semantics without a separately materialized substrate document. Pin the substrate for nontrivial, interoperable, proof-bearing, or reusable derivation; otherwise return missing-substrate only for the stronger unavailable claim. |
| Actor invented or suppressed | Every Transformation is forced to have a Work performer, or project Work, a TFS or network, a Method, a record, or the changed subject is silently put in an acting position. | Ground the A.3.4 change first. Add a causal or interaction participant only when the applicable predicate and the case facts establish that position. For a Work-realized change, establish the performer System with its A.13 basis, Work, changed referent, and the relation that connects Work to the change, plus F.6 attribution only when the receiving question asks under which assignment the Work was performed; a short account may omit an unused assignment identifier. Otherwise invent no actor, assignment, Method, or Work. |
A.15.6:9 - Consequences
Benefits. Cost and completion claims can refer to one actual composite Work occurrence through their predicates. A responsibility assertion separately names its predicate and participants, then applies an existing or sufficient local rule; an absent required rule yields missing-governor. The project system-of-interest, selected project-relevant network, case subjects, system-role classifications and assignments, changed referents, produced entities, evaluations, deliveries, acceptance decisions, and downstream uses retain their own facts.
A team can name the temporary work, its local subject and intended result, the performing organization and the common product-use purpose without treating them as one object. It can also tell when a described System is only intended. Process evaluation can use Work observations whose A.15.1 relation states which Method was enacted, or operation-application observations supported by a declared A.6.1 operation and typed binding, without turning observed Work into a Method or structure. Case Work can close around a continuing entity, episteme edition, characteristic inquiry, relation, decision, or result while keeping any relevant downstream use outside closure.
Costs. Practitioners must distinguish intended from performed work and recover a continuity policy when an identity ambiguity requires it. A legacy @Project reference may need its actual relation made explicit; descriptions with different EntitiesOfConcern need separate identities rather than one project label.
Limits. This pattern does not supply project-management, process-management, or case-management methods. It does not decide success, acceptance, evidence strength, authority, or result semantics. It only recovers the FPF subject and relations those methods operate on.
A.15.6:10 - Rationale
Admit actual project Work through the full A.15.1:4.1 test for the same candidate occurrence, with every actual performer’s A.13 core and any conditionally required profile. Independently grounded common construction and Work-specific facts support membership; typed enactment, containment and Work-part assertions follow under their own predicates. Use F.6 afterward for any precise assignment-bound attribution. Add an episode, continuity or aggregation claim only when the project use needs it. A short project account may omit assignment identifiers or further valid boundaries its receiving claim does not use.
State resource use, Work-to-referent facts, change, production, evaluation, delivery, acceptance and later result use as separate claims, each under its predicate and case basis. The five project-specific tests qualify that admitted Work. This preserves the performed whole’s identity while keeping its plans, performing organizations, Transformations and descriptions distinguishable.
Repeatability belongs to U.Method; direct method-side relations remain unbundled until the structure’s constituents are identified independently, its selected relations obtain, its constraints are applied, and one use frame names the selection question, admissible action and stop or return condition. Only then select one U.Structure under A.22 and, if useful for that question, call it MethodRelationStructure. Transformation-flow organization belongs to TransformationFlowStructure. None is the unique dated Work occurrence.
A case remains centered on the subject or claim named by its closure question, even when several Methods, structures, Work occurrences, Systems, results, measures, and decisions are relevant. Recovery therefore preserves more information than a three-label hierarchy.
The common product SoI and local-subject distinctions follow the same economy. A plan or decision can designate a system; a shared systemic account additionally explains why that system’s intended use organizes the participants’ joint undertaking. A.1.STM develops that basis and the connection of local contributions to it, while A.2 separately answers whether an actual System is classified under a defined local system-role kind and U.SystemRoleAssignment answers which assignment occurrence obtains. Use that designation when it answers the question.
For a one-case compound claim, recover the constructor semantics and direct facts; materialize or pin a substrate only for nontrivial derivation, interoperability, proof, or reuse. Return missing-substrate only for a needed stronger claim whose operator semantics are unavailable.
An intended future System remains claim content until inception. Reopen A.6.RCD for a reusable predicate or relation kind only when a named receiver needs that stronger result.
A.15.6:11 - SoTA-Echoing
| Source contribution | What it contributes | FPF adoption |
|---|---|---|
| PMI, What Is a Project | Practice terminology emphasizes a temporary endeavor producing a unique product, service, or result through structured activities. | Adapt as vocabulary pressure. After A.13 and A.15.1 independently admit the actual referent as composite performed U.Work, qualify it as project Work; when precise assignment-bound attribution is current, add F.6 afterward. Keep intended product or result, task descriptions, and deliverables as related values rather than a project kind. |
| APM, What Is Project Management | Project practice describes a unique transient endeavor and discrete packages of work directed toward planned objectives. | Adopt the work selection. Use independently admitted transient composite Work and obtaining Work-part relations, while separating the temporary performing organization. |
| Winch, An Action Theory of the Project, 2025 issue | Distinguishes temporary organization, permanent organization, future-oriented action, intention, and intended future state. | Adapt. Keep organization, performed Work, plan or intention, affected referent, and intended state as related objects with different identities. |
| Sydow, Lundin, Ekstedt, and Braun, The theory of temporary organization three decades later, 2025 | Project plasticity and continuity persist across changing organizational arrangements. | Adopt as a continuity safeguard. Use A.15.1 identity and Work-part rules, and a continuity policy when needed for the boundary question; team identity or a project label is insufficient. |
| Adams et al., Defining Cases and Variants for Object-Centric Event Data, 2022, and Küsters and van der Aalst, OCPQ, 2025 | Real events may relate to several objects; one preselected case key or flattening can lose information, while object-centric queries and constraints select bounded answers. | Adopt for process and case recovery. Preserve object relations until a named use selects a grouping, query, or constraint. A selection-result episteme may serve as evidence through an independently obtaining evidence-use relation; it is not automatically a Method, Work occurrence, or case subject. |
| Jalali, Evaluating user acceptance of knowledge-intensive business process modeling languages, 2023 | In two studies of trained course participants, CMMN, DCR, and Declare received different perceived-usefulness and ease-of-use results; interactive simulation may influence learning and perceived usability. | Adapt as a representation-use boundary. A notation can help practitioners represent flexible case work. The case subject, closure and any asserted Work use their own rules and facts. Keep perceived ease of use and simulation support visible when selecting a description form. |
FPF uses these contributions to distinguish temporary organization, intended and performed work, and the subjects selected by process and case questions. Its own admission and relation rules then test those claims. The project, process and case accounts can inform one another without acquiring a shared identity.
A.15.6:12 - Relations
-
A.1supplies the common construction of the candidate occurrence and defines the identities of participating Systems, affected holons and description-grounding holons. -
A.3.1defines reusableU.Methodidentity and composition. ApplyA.22to select a method-sideU.Structure: identify its constituents, selected obtaining relations, applied constraints, and a use frame with the selection question, admissible action and stop or return condition. UseMethodRelationStructureonly as a local designator after that selection. -
Use
A.3.4for one actual bounded change of one continuing referent. State actor-side participants only when the applicable dynamics, interaction, participation, or causal-use predicate obtains; Work-facing performer, assignment, Work, and work-to-change claims remain separate. -
Apply
A.13to recover each actual performer’s local agential kind and criterion, classification, obtaining assignment, scope, working situation and window, with evidence adequate for those core claims; add a characteristic profile only when a Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use consumes it.Use the full
A.15.1:4.1admission test for the same candidate occurrence. It connects its common construction and Work-specific facts to membership, after which grounded typed Work relations can be asserted.F.6 adds precise assignment-bound attribution through the same assignment only when needed. Name another enacted Method, episode, continuity claim or relation-specific aggregation when the receiving use needs it. A short account may omit unused assignment identifiers or further valid boundaries. Project qualifications preserve that Work identity and require actual Work parthood.
-
Use
A.15.2for intended work andU.WorkPlanbefore and during performance; a merely intended future System remains plan content rather than an actual holder. -
Use
A.2to identify and classify local system-role kinds from their feature criteria. When assignment identity matters,A.2.1adds an assignment occurrence and its declaredU.SystemRoleAssignmentspecies. The species defines participant meanings and the predicate; the occurrence supplies the participants and extent for the case. Neither classification nor assignment grounds project designation. -
Use
A.15.PRODonly for the selected production-work, entity-identity-inception, or production-completion question. -
A.6.RCDdefines the economy among one-case claims, reusable predicates, and relation kinds. For project selection, use the plan or decision designation when sufficient. A one-case compound claim needs recoverable constructor semantics but no separately materialized substrate document unless nontrivial derivation, interoperability, proof, or reuse requires one;missing-substrateblocks only a stronger claim whose operator semantics are unavailable. -
Apply
A.6.P.WMRwhen result wording hides the relation. Choose one of four outcomes: obtaining direct relation, typed A.6.1 binding, local claim underA.15.PRODorA.6.RCD, or one non-assertability result. Preserve the corresponding WMR reason:factually unsupported,missing-information,missing-governor, an inapplicable result under the named rule, ormissing-substrate. Keep independently established facts. Use A.6.RCD’s lightest sufficient branch if the receiving question needs the missing rule or constructor basis. -
A.7restores the EntityOfConcern, description-episteme, and publication boundary before a project card, charter, repository, dashboard, or other record is related to the composite work occurrence. -
C.2.1defines description and record episteme identity through claim content, oneEntityOfConcernrecoverable from that content, and the effective reference scheme. Management topics assign no subject; empirical grounding, viewpoint membership, scope, edition, and publication remain separate relations. -
Use
E.17andE.24.PUBto publish project, process, and case accounts without replacing their subjects. -
E.18defines one selected transformation-flow structure.E.18.NETdefines a non-agentive network only when independently identified structures and obtaining cross-boundary relations are selected; its use frame can answer one named project question. Work membership in a project requires obtaining A.15.1 work-parthood. -
Use
A.6.RELwhen a Work, Method, Transformation, result, or correspondence relation occurrence must be identified because it participates in another relation. -
A.1.STMsupplies the project SoI and intended-use basis for a systemic project account, distinguishes that role from local attention, and connects local results and creator provision through the system-thinking long dependency. Its first-unsupported-dependency mode remains available when the shared basis is sufficient. UseE.10to recover project, process, case, and situation wording when source expressions remain ambiguous.