#Bounded Model-Use Structure and DDD Bounded-Context Recovery

A.1.1 · Stable · Part A architectural ontology pattern · 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: Part A architectural ontology pattern Status: Stable Normativity: Normative unless marked informative

Working reader and current decision. This pattern is for a domain architect, systems engineer, or service owner deciding whether several facts about one model must be treated together for the next engineering move. The reader starts from that decision—change scope, release scope, ownership boundary, integration boundary, or whether two uses belong together—not from a team name, repository, diagram, or the word context.

#Relations

#Content

#Practitioner entry

Working reader and current decision. This pattern is for a domain architect, systems engineer, or service owner deciding whether several facts about one model must be treated together for the next engineering move. The reader starts from that decision—change scope, release scope, ownership boundary, integration boundary, or whether two uses belong together—not from a team name, repository, diagram, or the word context.

Governed object in plain language. A.1.1 governs the selected organization of where one exact model applies, how it is actually used in assigned Work, and whether concrete expressions still agree with it. The Tech name is BoundedModelUseStructure; the familiar Plain retrieval name is bounded context. It is a U.Structure, not a container for systems, teams, Work, documents, or publications.

First useful move — take the smallest branch.

1. Name one exact model edition and one exact place or thing about which it is used.
2. Ask what the present decision needs. If applicability alone answers it, recover ModelApplicabilityRelation and stop. If actual use is current, recover the exact actual performer through A.13 and let A.15.1 independently admit the performed Work; because ModelUseRelation expressly represents assignment-bound use, then establish F.6 through the same obtaining A.13 assignment and recover ModelUseRelation, then stop. If maintained expression content is current, recover the fixed model content, fixed expression content, declared coherence predicate, and comparison scheme, then decide ModelExpressionCoherenceRelation and stop.
3. Recover the remaining direct relations only when their joint organization changes the decision. Select BoundedModelUseStructure only then.
4. Keep every boundary crossing separate. A proposed source, target, direction, required fit, permitted loss, and claim scope is useful planning content, but it is not an occurrence and cannot identify either endpoint structure.

First-minute success case. A press-control team must decide whether a controller-code change may be handled as a local code edit or must enter the independently governed release review together with model applicability and operating use.

1. PressControlModel-5 is the exact claim-bearing model edition, Press-3 is the use locus, and the model applies within SafetyControlClaimScope; this is one ModelApplicabilityRelation occurrence.
2. A.13 first recovers Operator-12 : U.System as the exact actual performer through obtaining OperatorAssignment-8, and A.15.1 independently admits PressOperationWork-91 : U.Work. Because this actual-use claim expressly represents assignment-bound use, exact F.6 performedUnderAssignment(PressOperationWork-91, OperatorAssignment-8) then obtains. The already recovered performer actually uses PressControlModel-5 during that Work concerning Press-3; this is one ModelUseRelation occurrence.
3. ControllerImplementsControlModelPredicate checks the fixed contents of PressControlModel-5 and PressControllerCode-17 under PlantControlReferenceScheme. It returns true, so one ModelExpressionCoherenceRelation occurrence obtains. The predicate is the test value, not the occurrence or an evaluation procedure.
4. Because independently governed PlantReleaseRule-3 needs model applicability, operating use, and fixed-content coherence together when each is material, select their organization and present those three facts jointly to the release review. This selection supplies the review's subject matter; PlantReleaseRule-3 supplies the review obligation; release authority, if needed, is established separately.

This row names the selection-use frame reconstructed in the full assurance replay in section 5.1; the first-minute action does not require unpacking its A.22 identity proof. If the decision asked only whether the model applies to Press-3, stop after step 1. If PlantReleaseRule-3 were absent or did not require the three facts together, stop at the direct relations. No crossing is asserted.

Three quick recognition situations.

Short glosses. A model episteme is one exact claim-bearing model edition. A model-use holon is one already admitted system or other concrete whole about which the model applies or is used; it is not a context container. Work (U.Work) is one exact dated doing, not its method, plan, or result. A claim scope (U.ClaimScope) is the set-valued boundary of context slices for one claim. A relation occurrence is a world-side relation actually obtaining under its predicate. A reference scheme is the interpretation basis for claim content. A structure here is a selected organization of already governed constituents, obtaining relations, applied constraints, and one exact selection-use frame; it is not another whole.

Adoption test. After applying A.1.1, name the exact organization that changes the present decision and the condition for stopping or returning to its direct relations. If either is missing, stop at the direct relation or the pattern that defines or tests it. Use F.19:4's plausible-reader test for any optional explanatory guard.

Names for retrieval. The Plain label is bounded context and the Tech label is BoundedModelUseStructure. Use F.18 for designation settlement and lineage, and F.17 for the public terminology row and its refresh evidence; A.1.1 keeps only the names needed to apply this pattern. Authors MUST NOT publish U.BoundedContext as a U-kind.

#Problem frame

Use this when. Use this pattern when a current decision depends on the organization of three distinguishable facts about one exact model edition: where it applies, how it is actually used in assigned Work, and whether maintained expression content remains coherent with it. Physical location, team ownership, a document title, or the word context is not enough.

First useful move. State the decision, model, and use locus; recover only the direct relation that answers the question and stop when it suffices. Select the wider structure only when several already governed relations, applied constraints, and one exact selection-use frame together change the decision.

What goes wrong if missed. Systems, Work, epistemes, and publications are merged into a context-shaped proxy. One subsystem under two models is treated as one context by location, while one model used coherently across several loci is split by an implementation boundary. Local vocabulary, rules, units, status, or evidence use is also forced into a context object even when a direct semantic-locality pattern answers the question.

What this buys. Actual participants retain their identities. Applicability, use, and fixed-content coherence remain inspectable direct relations; their decision-relevant organization can be selected as U.Structure; and ordinary semantic locality is stated through its exact value and relation assertion, with the subject pattern kept only as a locator.

Not this pattern when. If only a term sense, local system-role-kind value, system-role-assignment occurrence, relation among system-role kinds, rule or invariant, admissible inference, unit or measurement basis, status, evidence use, claim scope, description, publication, or direct relation is current, use the A.1.1:4.4 triage and stop at that direct result. Do not select BoundedModelUseStructure unless the relation organization itself changes the decision.

#Problem

DDD bounded-context practice couples several real concerns: a model is defined and applicable within a boundary; actual systems in assigned roles use it; code and descriptions contain expressions of it; integration and maintenance work aims to keep those expressions consistent; and maps describe relationships among model uses. These are practical prompts to recover exact FPF claims, not evidence that maintenance caused coherence or that a described crossing obtains. Their objects are related, but they are not parts of one additional whole by that fact.

FPF needs this joint model-use relation organization selectable as U.Structure so it can serve as EntityOfConcern for comparison and maintenance work without becoming a heterogeneous holon, a description, or one universal semantic-locality reference.

#Forces

#Solution

Recover the Plain bounded context as one BoundedModelUseStructure, governed as a U.Structure. Identify it from one exact model episteme, exact already-admitted model-use holons, the selected organization of obtaining model-applicability, actual model-use, and fixed-content model-expression-coherence occurrences, exact applied constraint claims used by the selection judgment, and one exact selection-use frame. Each U.ClaimScope remains only a participant of its selected ModelApplicabilityRelation; a separate applied constraint claim may refer to that scope or its A.2.6 membership predicate. A bare scope, slice, membership outcome, boundary display, or carrier enters no A.22 discriminator. No boundary crossing participates in this identity. A later model edition has another C.2.1 episteme identity; continuity across it additionally requires exact EpistemeEditionRelation(earlierModelEpisteme, laterModelEpisteme) and the A.1.1 continuity rule.

#Select structure, not another holon

Use the four A.22 identity discriminators. The following sketch is a description of the selected organization, not the structure itself and not a relation signature:

BoundedModelUseStructure : U.Structure
  exact constituents:
    one selected model episteme
    exact admitted model-use holons
  exact selected obtaining relations:
    ModelApplicabilityRelation occurrences
    ModelUseRelation occurrences
    ModelExpressionCoherenceRelation occurrences
  exact applied constraint claims used by the selection judgment:
    one exact C.2.1 constraint proposition may refer to a U.ClaimScope or its A.2.6 membership predicate
    other exact applicability, coherence, release, or use-rule constraint propositions applied here
    no bare scope, slice, membership outcome, boundary display, or carrier episteme
  one named selection-use frame:
    exact question
    admissible action
    stop or return condition
  optional nearest non-admissible overread: explanatory only, subject to F.19:4's plausible-reader test

A selection-use frame is the exact plain value formed by the question, admissible action, and stop or return condition; it is not a new kind, card, or record. A phrase such as current use, appropriate structure, or bounded-model-use frame does not fill it. Changing one of those three values changes that identity discriminator. An optional nearest non-admissible overread may explain the use when it passes F.19:4's plausible-reader test; that explanation is outside the frame's identity.

The structure depends on its constituents and selected relation organization. It is not a holon whose parts are the substrate systems, Work, methods, or epistemes. Their identities, direct part relations, and any construction or whole-reidentification questions remain separately governed.

#Recover the direct relations

A.1.1 states each direct predicate and its occurrence-identity rule. An obtaining occurrence is an instance of a relation kind already admitted under U.Relation; its existence does not depend on a project deciding to expose it. A named receiving use may justify explicit individuation and reference under A.6.REL. A reusable RelationSignature episteme declares the participant SlotSpecs. An assertion or occurrence description may designate the actual participants by value or reference. Each table below is a readable presentation of one signature declaration.

The two named temporal-extent ValueKinds below are local to A.1.1, not U-kinds. They can type a temporal extent stated in an assertion or occurrence description; they are not participant ValueKinds in either RelationSignature. For ModelApplicabilityRelation and ModelUseRelation, the direct obtaining history determines the maximal continuous extent used by the occurrence-identity rule. A filled assertion may state an open or closed extent.

For these two temporally varying relation kinds, continued obtaining extends the same open occurrence; a demonstrated gap ends it, and later resumption begins another occurrence. ModelExpressionCoherenceRelation instead has the participant-determined identity declared below: it has no temporal-extent discriminator. Revising an assertion changes the episteme, not any world-side occurrence.

ModelApplicabilityRelation. Its participants are one model episteme, one exact holon, and one declared claim scope. Its predicate asks whether that model applies to that holon over the exact U.ContextSlice values delimited by that scope. The model episteme's C.2.1 effective reference scheme supplies the interpretation basis; it is not a fourth participant.

Well-formedness constraint WF-A1.1-APP. ModelApplicabilityRelation(M,H,S) obtains exactly when S is the model-declared applicability scope or scopeSubset(S, modelDeclaredScope(M)), both scope expressions are interpreted under effectiveReferenceScheme(M), and the model's declared applicability conditions hold for H over every slice x for which member(x,S) is true. coversSet(S,T) applies only when T is an exact finite ContextSliceSet.

When S imports a local sense from another semantic setting, the interpretation branch exists exactly when the source and receiving F.17 SchemeSenseCell values are resolved and an F.9 Bridge obtains in the source-to-model orientation. Different schemes, shared spelling, or a Bridge Card does not establish that branch.

Well-formedness constraint WF-A1.1-APP-USE. A positive applicability assertion or structure selection that relies on the imported branch is admissible only when a separate current C.2.1 claim affirmatively states that the Bridge is suitable for this named scope-comparison use, direction, rule, and loss tolerance. The same use must have an exact A.10 evidence-provenance path whose edges cite independently established direct relations. Ordinary reliance requires RelianceDisposition=pass. If an actual named assurance claim about that use is current, require its B.3 AssuranceResult for the same bounded use: only supported-for-use supports the attempted assurance use, while narrowed supports only its stated narrower use. A direct domain rule may require such a claim.

Use guidance. If the Bridge, bounded-use claim, or selected reliance branch is missing, return respectively missing claim-scope interpretation bridge, missing claim-scope interpretation use claim, or missing claim-scope interpretation reliance. These stops block the receiving assertion or selection; they do not make an otherwise obtaining Bridge false. Any membership judgment, operation application, assertion, or Work remains under A.2.6, A.6.1, C.2.1, or A.15.1.

The occurrence is reidentified from the actual identities of the model episteme, holon, and claim scope together with the derived maximal continuous ModelApplicabilityInterval. Repeating the model's effective scheme adds no independent discriminator. ModelUseRelation. Its participants are one exact system-role-assignment occurrence, one model episteme, one performed Work occurrence, and one exact use-locus holon. Its predicate is actual use of that model content by the assignment holder while that system performs the same Work concerning that holon.

Well-formedness constraint WF-A1.1-USE. ModelUseRelation(A,M,W,H) obtains exactly when F.6 performedUnderAssignment(W,A) obtains and HolderSystem(A) actually uses the content of M while performing W concerning H. The holder system is derived, not copied as a fifth participant. Any claimed enactment relation between W and a Method belongs to A.15.1; A.3.1 identifies that Method.

The occurrence is reidentified from the four participant identities and the derived maximal continuous ModelUseInterval. A useful counterfactual probe compares otherwise matching work situations that use model epistemes with different relevant content and asks whether that difference could change performance; availability or mention alone is not actual use. Scope delimitation is not another direct relation kind here. The U.ClaimScope participating in ModelApplicabilityRelation is a set-valued scope over U.ContextSlice; A.2.6 governs its primitive membership predicate. A membership assertion or an evaluation result is an episteme about that predicate.

Local predicate-value declaration. ModelExpressionCoherencePredicate is an A.1.1-local ValueKind, not a U-kind and not an evaluation procedure. A by-value candidate belongs to this kind only when it declares (1) the ordered model-content and expression-content input meanings, (2) the exact comparison domain and local senses, (3) a Boolean truth condition, (4) the treatment of required congruence and permitted loss, and (5) every dependency whose absence makes application stop rather than return false. Two predicate values are identical exactly when those five by-value components are identical. A changed input meaning, domain, truth condition, congruence or loss rule, or dependency identifies another predicate value; a changed label, evaluator, evidence set, result episteme, representation, or publication does not. A label or procedure lacking the complete five-part declaration is not a member.

ModelExpressionCoherenceRelation. Its participants are one exact model episteme, one exact expression episteme, one by-value criterion admitted as ModelExpressionCoherencePredicate, and one exact U.ReferenceScheme used as the comparison basis.

Well-formedness constraint WF-A1.1-COH. ModelExpressionCoherenceRelation(M,E,P,R) obtains exactly when either (a) R equals the C.2.1 effective schemes of both epistemes, or (b) P resolves every differing source and receiving F.17 SchemeSenseCell pair and names an obtaining F.9 Bridge for each required correspondence; and, after that semantic branch is established, the fixed predicate value P returns true for the fixed claim contents of M and E under R. An unresolved cell, missing Bridge, shared spelling, common label, Bridge Card, or mere interpretability establishes no bridged branch.

The Bridge profile carries relation semantics only. Comparison direction, use-specific rule, permitted loss, and reliance belong to the separate bounded-use claim and reliance path.

Well-formedness constraint WF-A1.1-COH-USE. A receiving assertion or structure selection that relies on a bridged coherence occurrence is admissible only when a separate current C.2.1 claim affirmatively states that the Bridge is suitable for this fixed-content comparison use, direction, rule, and loss tolerance compatible with P. The same use must have an exact A.10 evidence-provenance path whose edges cite independently established direct relations. Ordinary reliance requires RelianceDisposition=pass. If an actual named assurance claim about that use is current, require its B.3 AssuranceResult for the same bounded use: only supported-for-use supports the attempted assurance use, while narrowed supports only its stated narrower use. Establish any required authorization separately.

Use guidance. Return missing model-expression interpretation bridge, missing model-expression interpretation use claim, or missing model-expression interpretation reliance for the corresponding missing condition. A use stop does not make the Bridge or predicate false and does not erase or reidentify an otherwise obtaining coherence occurrence. Comparison Work, an assertion episteme, and an A.22 selection use remain separate.

One occurrence is participant-determined by <M,E,P,R>; it has no temporal-extent discriminator and no later recurrence for the same tuple. Changed claim content identifies another episteme and tuple. Changed predicate value or comparison scheme likewise changes the tuple. Changed evidence, bounded-use claim, reliance result, card, publication, evaluator, or timestamp does not. Maintenance remains one separate dated Work individual: recover each exact actual performer through A.13 and let A.15.1 independently admit the occurrence. Add F.6 through the same obtaining A.13 assignment only when the maintenance account or its receiving use expressly consumes precise assignment-bound attribution; F.6 identifies neither assignment nor performer, and missing or failed attribution leaves the Work intact. Its affected-referent, resource, parameter, premise, method-enactment, and operation-application facts use their direct relations or A.6.1 bindings. C.2.1 identifies any report or repaired episteme separately; only an exact A.15.PROD entity-inception claim may relate that episteme's first existence to the performed maintenance. An exact evaluator may separately be recovered through A.13 and perform independently admitted evaluation Work, with F.6 added only for a consumed precise attribution. C.2.1 identifies any result episteme asserting whether the coherence predicate holds, and only its exact A.15.PROD inception basis may relate its first existence to that performed Work. Neither that result episteme nor its provenance is the coherence occurrence. Failed maintenance work remains actual work even when the changed episteme tuple has no obtaining coherence occurrence.

BoundedModelUseStructure selects obtaining participant-determined ModelExpressionCoherenceRelation occurrences. Maintenance methods and Work remain separate objects even when they change the receiving decision; if their organization must itself be selected, that is a distinct A.22 structure and does not enter this bounded-model-use identity.

Coherence-work stress cases. Coherence can obtain before any selected maintenance episode. Successful maintenance that leaves both episteme identities fixed leaves the same participant tuple; maintenance that changes expression claim content gives another C.2.1 episteme and a different tuple to evaluate. Failed maintenance may leave a changed expression episteme and a separately identified evaluation result while the new tuple has no obtaining coherence occurrence. Automated integration work and non-software maintenance use the same separation among fixed-content correspondence, work, result, evaluation, evidence, and provenance.

Occurrence-identity stress case. Exact F.6 performedUnderAssignment(InspectionWork-42, InspectorAssignment-17) obtains, and its holder Robot-7 uses DefectModel-3 concerning Pump-6 during that work. An observation at 10:00 supports continued obtaining of the same occurrence whose ModelUseInterval began at 09:00 and remains open; it does not create another occurrence. If model use demonstrably stops at 10:15 and resumes at 10:30 during the same work occurrence and assignment attribution, the resumption begins a second model-use occurrence. Correcting an assertion's timestamp without evidence of a world-side gap changes only that assertion.

Use guidance — unsupported crossing. First identify both endpoint BoundedModelUseStructure values without the crossing and state source, target, direction, required fit, permitted loss, and claim scope. Well-formedness constraint WF-A1.1-CROSS. A positive cross-structure member exists only when a current direct pattern supplies compatible endpoint SlotKinds, an obtaining crossing predicate, an occurrence-identity rule, and all four A.22 discriminators; the proposal, F.9 sense Bridge, label, diagram, or card supplies none of them. Otherwise preserve the six-part proposal, omit it from both endpoint identities and every positive cross-structure member, and return missing CROSS-LOCALITY-BRIDGE governor.

A.1.1 is the subject pattern for these three relation kinds. A.6.0 governs their RelationSignature epistemes, A.6.5 governs the SlotSpecs inside those declarations, and A.6.REL governs progressive explicit individuation. A.2.6 separately governs claim-scope membership. BoundedModelUseStructure is the selected organization of the resulting occurrences under those scope values; no context record copies their participants.

#Use the settled public relation names

The direct definitions, SlotSpecs, obtaining constraints, and occurrence-identity rules above govern the three relation kinds. A.1.1 uses only the settled Tech labels and their shortest Plain relation sentences:

F.18 and F.17 carry candidate-name history, public-row state, lineage, and refresh evidence. ModelExpressionCoherencePredicate remains an A.1.1-local five-part criterion ValueKind; it has no public F.17 row unless a later durable naming use independently reopens F.18.

#Identify continuity through model use

At one observation time, the structure has the four A.22 discriminators:

1. exact independently identified constituents—the selected model episteme and admitted model-use holons;
2. exact selected obtaining applicability, use, and coherence occurrences;
3. exact applied constraint claims used by this selection, each with a recoverable proposition and C.2.1 identity; a claim may refer to one U.ClaimScope or its membership predicate, but the bare scope, membership outcome, boundary display, or carrier is not this discriminator; and
4. one exact named selection-use frame containing its question, admissible action, and stop or return condition. An optional explanatory guard follows F.19:4 and remains outside those four discriminators.

No crossing or proposed six-part crossing record enters those discriminators.

At a later observation time, reidentify the same structure only when every continuing constituent is reidentified under its direct rule; any replacement model is connected by exact C.2.1 EpistemeEditionRelation and admitted by the declared continuity rule; every continuing relation occurrence retains its direct identity; every replacement occurrence is explicitly admitted; and all four A.22 discriminators remain the same under that rule.

The continuity rule therefore compares the exact constituents, selected occurrence organization, exact applied constraint claims, and the complete question/action/stop-or-return selection-use frame. A changed constraint proposition reopens the third discriminator; changing only a membership assertion, boundary rendering, carrier, or evidence about an unchanged constraint claim does not. A changed question, action, or return condition reopens structure identity even when every substrate and relation occurrence remains unchanged. A changed explanatory guard alone reopens the affected use claim, not structure identity. If its changed content alters an applied constraint, question, action, or stop or return condition, compare that existing discriminator. A changed page, wording, rendering, carrier, description edition, or publication does not. File history, edition labels, publication order, a shared name, or membership in an edition collection establishes neither EpistemeEditionRelation nor bounded-model-use continuity; A.14 governs any separately selected collection of editions.

Missing evidence creates uncertainty about a continuity claim; it does not by itself end a world-side relation or structure. Any selected substrate holon may separately participate in a larger whole under A.14 and C.13; that is not parthood of BoundedModelUseStructure.

#Resolve semantic locality through direct values and relations

When the question is local meaning rather than joint model-use organization, recover the smallest direct result and stop:

For movement between local meanings, resolve the exact source and receiving F.17 sense cells and then apply F.9. An obtaining Bridge states correspondence between those readings; the separate bounded-use claim states direction, rule, and tolerance. A.10 handles ordinary reliance; B.3 adds a bounded result only when an actual named assurance claim is current. The Bridge is not the rule, unit, status use, inference, or receiving action.

If a subject pattern still asks for a generic U.BoundedContext or BoundedContextRef instead of the exact values above, do not fabricate that participant. Preserve the exact value or relation already recovered and stop at the unresolved interface in the subject pattern. The transfer is not complete merely because A.1.1 names a destination.

#Heterogeneous semantic-locality replays

Hospital operating-room replay. Recover direct values and relations.

This replay selects no BoundedModelUseStructure unless one exact model's applicability, assigned-Work use, fixed-content coherence, applied constraints, and selection-use frame also become current.

Two further retained uses.

#Keep descriptions and publications separate

A bounded-context description is a U.Episteme. Under its C.2.1 declaration, the description's entityOfConcernRef designates the exact EntityOfConcern named by the description's claims. EntityOfConcernSlot is the SlotKind in that declaration; it does not itself point to the world-side object. A meta-description designates that description episteme through ordinary C.2.1 recursion.

When a description claim needs empirical grounding, recover one exact C.2.1 EpistemeEmpiricalGroundingRelation between the description episteme and the admitted grounding holon. GroundingHolonSlot is only the signature-local participant meaning in that relation's declaration; a groundingHolonRef in a card or description designates the participant. The selected structure cannot fill that participant because it is not a holon. Viewpoint, claim scope, effective reference scheme, publication use, rendering, and presentation carrier remain separately governed.

A stale description has another episteme edition or an obsolete currentness claim. Neither condition by itself changes the model-use structure or its world-side relations.

#Recover DDD context mapping by direct object

Start with three questions: what reusable way of mapping was used, what work actually happened, and what claim-bearing product resulted? Identify that product under C.2.1. Call the same episteme a view only after it passes one exact E.17.0 viewpoint-conformance test. Keep the relation structure it describes and every diagram, page, or publication separate.

Code/schema split. Start from the exact claim, not the source phrase. Claim-bearing source-code or schema content such as PressControllerCode-18 is a C.2.1 episteme with an exact EntityOfConcern and effective scheme. A repository, file, publication form, or presentation carrier that bears that content remains under its direct representation/publication/carrier pattern. A deployed controller, database, or software organization remains an actual system or selected structure under its subject pattern. The phrase code base or database schema grants none of those identities and never supplies one universal kind.

Positive case: the fixed claims expressed by PressControllerCode-18 participate as the expression episteme in ModelExpressionCoherenceRelation. Near misses: PressControllerRepository-2 is only the repository or carrier being referred to, and DeployedPressDatabase-4 is the deployed database system or structure. Neither near miss may fill an episteme participant merely because source practice calls it a code base or schema.

This dispatch table is a reading aid for selecting the governing FPF object and pattern. Only that direct pattern supplies object identity, relation obtaining, or dependent-kind membership. If a separately current claim says that the candidate episteme first existed through the performed mapping Work, apply A.15.PROD only to that exact local inception claim. If an earlier episteme participates as source, use C.2.P to recover the exact source expression and route the source-use relation to its direct governor. Evaluation Work and any result episteme remain separate. None of those facts, and no product name, representation, rendering, publication occurrence, form, or carrier, grants U.View membership.

FPF Map remains the mapping-method head for mapping subjects to coordinates in a declared Space. The quoted DDD product name stays a retrieval cue; by itself it grants neither dependent U.View membership, the FPF Map reading, nor identity with the structure.

BoundedModelUseStructure and A.22's conditional cross-structure rule concern different structures. First identify every bounded model-use structure from its own model, admitted holons, three direct relation families—including each applicability occurrence's exact U.ClaimScope participant—exact applied constraint claims, and named frame. A scope or membership result is not copied into the constraint discriminator. Only then may a distinct A.22 structure select several such endpoints and independently governed obtaining crossings among them. Until those crossing occurrences and all four A.22 base discriminators exist, no member of that conditional specialization is asserted and its A.22-local label remains pending. Maintenance Work remains separate from both structures. A candidate context-mapping episteme may carry claims about a proposed crossing organization without designating an exact structure. Once the direct crossing and A.22 identity exist, a corresponding C.2.1 episteme may designate that exact cross-structure and its participants. Only an explicit C.29 representation may show the structure or proposal; the episteme is a U.View only after exact E.17.0 conformance obtains.

#Preserve the lightweight path

Most local claims need no bounded model-use structure declaration. Name the exact current participant, semantic-locality value, system-role-assignment occurrence, or direct relation occurrence under its subject pattern and stop.

Select and expose BoundedModelUseStructure only when the joint organization of independently governed model applicability, actual model use, fixed-content model-expression coherence, exact applied constraint claims, and the named frame changes the next engineering move. Keep each claim scope solely in its applicability occurrence unless a distinct applied constraint proposition refers to it. If a crossing matters, open the separate A.22 cross-structure question only after its direct governor makes that exact crossing obtain between already identified endpoint structures; never add it to either endpoint identity. Recognize an episteme as U.View only after exact E.17.0 conformance. Publish that already recognized view under E.24.PUB only when a declared audience and use need it.

#Archetypal Grounding

#Full control-model assurance replay

The first-minute case in section 0 is enough for ordinary entry. This longer replay checks the ontology and stop conditions without turning them into the first-use path. Any claim of authority over the Work in the filled cases below needs its own governing basis.

1. Applicability decision. ModelApplicabilityRelation obtains among model episteme PressControlModel-5, system Press-3, and claim scope SafetyControlClaimScope. C.2.1 fixes PlantControlReferenceScheme as the model episteme's effective scheme, so it supplies the interpretation basis without becoming a fourth participant. The derived ModelApplicabilityInterval remains open while the model's declared applicability conditions hold for Press-3 over the exact U.ContextSlice values admitted by member(slice, SafetyControlClaimScope) under that scheme.
2. Actual-use decision. A.13 first recovers Operator-12 : U.System as exact actual performer through obtaining OperatorAssignment-8, and A.15.1 independently admits PressOperationWork-91 : U.Work. Because this decision expressly represents assignment-bound model use, exact F.6 performedUnderAssignment(PressOperationWork-91, OperatorAssignment-8) then obtains. The already recovered performer actually uses PressControlModel-5 concerning Press-3 during that Work. Those four relation participants plus the derived maximal continuous ModelUseInterval reidentify one ModelUseRelation occurrence.
3. Scope boundary. Under the A.2.6 membership predicate, EmergencyStopContextSlice belongs to SafetyControlClaimScope. This membership claim explains part of the applicability boundary; it is not another relation occurrence selected into the structure.
4. Fixed-content coherence decision. ControllerImplementsControlModelPredicate is an admitted local predicate value. Its ordered inputs are the fixed claim contents of PressControlModel-5 and PressControllerCode-17; it returns true exactly when the code expresses every controller-command and feedback distinction required by the model, and false when a required distinction is missing. Both epistemes have PlantControlReferenceScheme as their C.2.1 effective scheme, so the relation-side comparison scheme is that same value and no Bridge is inferred. The predicate returns true for these participants, so their participant-determined ModelExpressionCoherenceRelation occurrence obtains before any selected maintenance episode.
5. Maintenance and change stay separate.
   • Work: Engineer-4 : U.System performs ControllerCoherenceWork-22 : U.Work under ControllerEngineerAssignment-7. First recover Engineer-4's A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the dated Work from its performance history, enacted ControllerAlignmentMethod-2, extent, and containing-System relation. Because this case explicitly attributes performance under ControllerEngineerAssignment-7, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Engineer-4 as holder, and covers the Work.
   • Transformation and later episteme: A.3.4 independently identifies PressControllerCodeCarrierChange-24 : U.Transformation as the bounded change of continuing PressControllerCodeCarrier-6 : U.PresentationCarrier, using the exact edit boundary, before-and-after code-expression facts, and the carrier-continuity rule. Changed claim content identifies later episteme PressControllerCode-18 under C.2.1.
   • Stop: No current FPF relation says that ControllerCoherenceWork-22 caused or realized PressControllerCodeCarrierChange-24, so return missing work-to-change governor; temporal overlap and a shared code referent do not supply it. A.15.PROD remains closed for a claim that the Work first constituted PressControllerCode-18 until its exact entity-inception basis, including that missing link, is governed.
6. Evaluation and result stay separate.
   • Evaluation Work: Evaluator-2 : U.System performs CoherenceEvaluationWork-23 : U.Work under CoherenceEvaluatorAssignment-5. First recover Evaluator-2's A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the dated Work from its performance history, enacted CoherenceEvaluationMethod-4, extent, and containing-System relation. Because this case explicitly attributes performance under CoherenceEvaluatorAssignment-5, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Evaluator-2 as holder, and covers the Work. State any needed operation application through its A.6.1 binding.
   • Result: C.2.1 separately identifies result episteme CoherenceEvaluation-23, which asserts whether the coherence predicate holds; only an exact A.15.PROD inception basis may relate that episteme's first existence to the evaluation Work. The result's assertion, evidence-use relation, and provenance remain distinct.
   • Next tuple: Because PressControllerCode-18 has different claim content, it forms another participant tuple with PressControlModel-5; predicate truth for that tuple decides whether another coherence occurrence obtains. Maintenance, method enactment, changed referent, evaluation, result, evidence, and provenance neither substitute for that truth nor enter the relation's participant set or identity.
7. Crossing stop. If a diagnostics crossing matters, first retain the independently identified source and target structures, then record direction, required fit, permitted loss, and claim scope. F.9 governs correspondence between local senses. Omit the proposed crossing from any positive cross-structure member and return missing CROSS-LOCALITY-BRIDGE governor. The already governed endpoint relations remain available for their own selections.

Filled A.22 basis for the press-control structure. Its exact constituents are model episteme PressControlModel-5 and use-locus system Press-3. Its selected occurrences are ModelApplicabilityRelation(PressControlModel-5, Press-3, SafetyControlClaimScope), ModelUseRelation(OperatorAssignment-8, PressControlModel-5, PressOperationWork-91, Press-3), and ModelExpressionCoherenceRelation(PressControlModel-5, PressControllerCode-17, ControllerImplementsControlModelPredicate, PlantControlReferenceScheme) as established in steps 1–4. OperatorAssignment-8 and PressOperationWork-91 remain actual participants used to establish the selected ModelUseRelation; they are not copied into the constituent plurality. Its exact applied constraint claims are PressSafetyScopeUseConstraintClaim, whose proposition says that every target slice used in the release judgment satisfies member(targetSlice, SafetyControlClaimScope); PressCommandFeedbackConstraintClaim, whose proposition says that the change preserves the model's command-versus-feedback distinction; and PlantJointReviewConstraintClaim, whose proposition says that, under independently governed PlantReleaseRule-3, all three selected occurrences are required inputs to the release review when each is material. SafetyControlClaimScope, any membership outcome, boundary rendering, and the claim carriers enter no discriminator by themselves. Its fourth discriminator is PressControlReleaseFrame from section 0: ask whether the change is code-only or jointly model/use/coherence-relevant; provide that joint subject matter to the release review; return to the three direct relations if PlantReleaseRule-3 is absent or does not require their joint review. Missing any discriminator leaves the direct relations in place but blocks this structure selection.

The relation sentences above assert direct world-side occurrences; the scope sentence states an A.2.6 membership claim. If the question is only whether the model applies to the press, stop at ModelApplicabilityRelation. Select BoundedModelUseStructure only when the selected applicability, operating-use, and expression-coherence occurrences plus the exact applied constraint claims and frame change the decision or Work plan.

One subsystem, one model. The press-control replay above is the filled case. The machine keeps its U.System identity; the selected structure uses the exact constituents, three obtaining relations, applied constraints, and PressControlReleaseFrame. Without that complete basis, stop at the direct relations. A diagram or later crossing is unnecessary for the positive selection.

One subsystem, two competing models. DeviceSubsystem-2 remains one system. Two structures are available only because each organization is independently complete:

An exact C.2.1 EpistemeEditionRelation may separately establish historical continuation; it does not merge simultaneous organizations. Near miss: if either side lacks its coherence occurrence, an applied constraint, or its complete frame, that side has useful applicability and use facts but no selected BoundedModelUseStructure yet.

One model, two use loci. ClinicalTerminologyModel-7 participates in two independently complete non-software structures:

Across these five filled structures, each expression episteme is a participant of the selected ModelExpressionCoherenceRelation. A replacement with different claim content gives another <M,E,P,R> tuple to evaluate and reopens the selected-occurrence discriminator (sections 4.2–4.3). Each assignment occurrence and dated Work stays only in its selected ModelUseRelation and in the evidence establishing that occurrence. Changing either one reopens that relation and therefore the selected-occurrence discriminator; it is not also an independent constituent replacement. One spanning structure is available only when one exact constituent plurality, relation-occurrence organization, applied-constraint set, and selection-use frame genuinely spans both uses. Shared model identity alone neither merges nor splits them. Near miss: exact diagnosis and billing Work plus a shared model, without one side's coherence occurrence or filled frame, supports only the direct facts on that side.

Published classification model. The published NAICS model is an episteme. Exact F.6 performedUnderAssignment(ClassificationWork-4, ClassificationAssignment-3) and actual use of that model content concerning an organization supply the use branch. A positive NAICSClassificationModelUseStructure additionally needs exact applicability with ClassificationClaimScope as that relation's scope participant, fixed-content coherence with the classification expression, exact applied constraint claims stating which edition and classification distinctions the judgment must preserve, and NAICSClassificationFrame: ask which NAICS edition and distinctions govern this classification; use the complete organization for the classification claim; without the complete basis, stop at publication availability or the direct relation that actually obtains. The bare scope or one membership result is not an applied constraint.

When a proposed directional dependency is called Conformist, retain its source, target, direction, required fit, permitted loss, and claim scope. Return missing CROSS-LOCALITY-BRIDGE governor until a compatible direct relation exists. Stale description. An already recognized Context Map view is six months old while the same already governed applicability, actual-use, and model-expression-coherence relations continue. Its currentness claim can become obsolete; revising the U.View episteme or publishing another rendering changes those epistemic and publication objects only. Reidentify each structure using all four discriminators and the continuity rule in section 4.3.

Context-mapping assurance case. This case tests the heavier method, product, view, and publication boundaries after the ordinary entry path has succeeded.

1. Method and Work. Architect-9 : U.System performs dated ContextMappingWork-14 : U.Work under ArchitectureAssignment-6. First recover Architect-9's A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the Work from its performance history, enacted ContextMappingMethod-3 : U.Method, extent, and containing-System relation. Because this case explicitly attributes performance under ArchitectureAssignment-6, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Architect-9 as holder, and covers the Work. The repeatable Method and this dated Work remain different objects.
2. Candidate product. C.2.1 independently identifies episteme ContextRelationsAnalysis-8. Its EntityOfConcern is the six-part proposed crossing organization: source, target, direction, required fit, permitted loss, and claim scope. The episteme is not the proposed organization.
3. Current stop. No independent direct governor currently makes the proposed crossing obtain. A.22 therefore lacks the relation-occurrence discriminator needed for base identity, and the candidate episteme does not designate an exact member of the conditional crossing-analysis specialization. Stop at the proposed organization.
4. Later positive route. Only if a future direct governor admits that exact crossing and all four A.22 discriminators are recovered may a corresponding C.2.1 episteme designate the resulting exact structure. Changing the EntityOfConcern remains subject to C.2.1 episteme identity.
5. Source use and inception. If a current claim says ContextRelationsAnalysis-8 first existed through the mapping Work, A.15.PROD governs only that exact local inception claim. If source episteme ContextNotes-7 participates, C.2.P recovers its exact source expression and routes the source-use relation to its direct governor.
6. View evaluation. Reviewer-6 : U.System performs ContextViewConformanceEvaluationWork-15 : U.Work under ContextViewReviewerAssignment-10. First recover Reviewer-6's A.13 core for this action, including the same obtaining assignment; A.15.1 then independently admits the Work from its performance history, enacted ContextViewConformanceEvaluationMethod-5, extent, and containing-System relation. Because this case explicitly attributes performance under ContextViewReviewerAssignment-10, F.6 afterward relates that already admitted Work to the assignment. The assignment obtains, names Reviewer-6 as holder, and covers the Work. Any result episteme and any A.15.PROD inception claim about that result remain separate. Under E.17.0, ContextRelationsAnalysis-8 becomes a U.View only when its declared conformance relation to ContextMappingViewpoint-4 obtains.
7. Representation and publication stop. The product name, mapping method, performed Work, source use, evaluation result, representation, rendering, publication occurrence, form, and carrier grant neither crossing-structure identity nor U.View membership and remain under their direct patterns.

#Bias-Annotation

This pattern has a DDD lineage bias because bounded context is the source term. Outside software, use A.1.1 only when the domain has one claim-bearing model edition, explicit applicability, actual use in assigned Work, fixed-content expression coherence, and a present decision changed by their joint organization. Industrial control, clinical or billing terminology, and published classifications can meet that test through different direct governors; a familiar context label cannot.

It has a structure-selection bias. The lightweight stop rule prevents mere local terminology, model mention, or implementation and organizational partition from becoming a structure without the required model-use relation organization.

It also has a model-coherence bias. Actual systems, work, methods, transformations, epistemes, and system-role-assignment occurrences keep their own identities and can remain the referents designated by receiving epistemes when the joint relation organization is not the subject of the receiving use.

#Conformance Checklist

1. A positive BoundedModelUseStructure exposes all four A.22 discriminators: exact constituents, exact selected obtaining applicability/use/coherence occurrences, exact applied constraints, and one named question/action/stop-or-return selection-use frame.
2. The three direct relation declarations satisfy WF-A1.1-APP, WF-A1.1-USE, and WF-A1.1-COH; any imported-sense receiving use additionally satisfies WF-A1.1-APP-USE or WF-A1.1-COH-USE. Missing conditions return the named stop rather than a positive assertion.
3. Every ModelExpressionCoherencePredicate value satisfies the local five-part membership and value-identity rule. Every ModelExpressionCoherenceRelation occurrence is participant-determined by <model episteme, expression episteme, predicate value, comparison scheme> and has no interval discriminator.
4. BoundedModelUseStructure is governed as U.Structure; its identity uses the four A.22 discriminators and their continuity rule.
5. Reidentification compares all four discriminators and then applies A.1.1:4.3. A changed applied constraint or changed question/action/stop-or-return frame reopens identity even when constituents and relation occurrences are unchanged; a changed optional explanatory guard alone reopens the use it protects; if it changes an applied constraint or frame value, compare that discriminator; a changed page, graph, rendering, or publication does not.
6. Semantic locality follows the direct-value triage in A.1.1:4.4. A local rule, inference, unit, evidence use, or status use remains at its exact subject pattern; a broad label or unrepaired generic-context field cannot manufacture the missing participant.
7. A description episteme designates its exact EntityOfConcern under C.2.1. When a description claim needs empirical grounding, recover one exact obtaining EpistemeEmpiricalGroundingRelation.
8. DDD Context Mapping is recovered as method, dated Work, claim-bearing product, proposed or obtaining crossing organization, view conformance, representation, and publication under their separate subject patterns. WF-A1.1-CROSS blocks a positive cross-structure member while the direct crossing governor or an A.22 discriminator is missing.
9. A code/schema cue is classified from the exact claim as claim-bearing episteme content, repository/file/form/carrier, or deployed system/structure; the cue itself supplies no common kind.
10. Two model uses over one subsystem yield two structures only when each independently supplies all three obtaining relation families, applied constraints, and its exact selection-use frame. Missing coherence or another discriminator leaves that side at its direct relations.
11. Use the structure only when its joint organization changes a receiving decision. The reader can name the admissible action and the stop or return condition; use F.19:4's plausible-reader test for any optional explanatory guard.

#Common Anti-Patterns and How to Avoid Them

#Consequences

Benefits. Teams can compare model-use boundaries without inventing an enclosing whole. Competing models over one subsystem and one model across several loci become expressible through complete structure bases. Local vocabulary, rules, inferences, units, evidence use, and status use remain recoverable through subject patterns rather than a context proxy.

Costs. A load-bearing structure claim must recover three direct relation families, exact applied constraints, and one question/action/stop-or-return frame. Semantic transfer sometimes stops at a subject pattern that still cannot express the claim without a generic context field; that stop preserves the known participants and relations while the missing predicate is repaired.

Limits. A.1.1 does not decide model truth, local system-role-kind classification, system-role-assignment occurrence or state, a relation among system-role kinds, rule validity, measurement, status, evidence, claim-scope membership, reference-scheme construction, system parthood, Work performance, release authority, or publication currentness. Its own predicates define model applicability, actual model use, and model-expression coherence; the joint organization is selected only when the required direct claims are available.

#Rationale

The selected object must survive two decisive tests. One subsystem under two models needs two bounded contexts without duplicating the subsystem. One model coherently used across several loci may need one bounded context without pretending those loci are parts of another whole. A dependent U.Structure over exact relations passes both tests.

The practical DDD lesson retained here is that boundaries matter because model applicability, actual use, expression consistency, and relationships can change engineering decisions. FPF does not copy that sentence as one ontology: it separates participant-determined fixed-content coherence from maintenance Work, identifies each bounded model-use structure without crossings, and includes an independently obtaining crossing only as a selected relation occurrence in a distinct A.22 structure over already identified endpoints.

#SoTA-Echoing

The source line is not one settled ontology. The 2015 reference defines a bounded context as a description of a boundary. The January 2026 worked case also uses the term for an actual system part and for use of the published NAICS model. FPF keeps those three readings distinct instead of choosing one of them as a universal context object.

Scoped FPF synthesis hypothesis and defeaters. This edition hypothesizes that, for the bounded uses declared here, the decision-relevant organization is one BoundedModelUseStructure over exactly the three direct relation kinds ModelApplicabilityRelation, ModelUseRelation, and ModelExpressionCoherenceRelation, its exact model-use substrate, exact applied constraint claims, and named frame. Each claim scope remains only the applicability-relation participant unless a distinct applied constraint proposition refers to it. Crossings belong only to a distinct A.22 structure over already identified bounded model-use structures. The hypothesis is usable only while each direct relation has coherent participant meanings, an obtaining rule, and an occurrence-identity rule, each applied constraint proposition is recoverable, and selecting their joint organization changes a concrete practitioner decision.

Fail this edition for the affected case, or reopen only the affected part of the synthesis, when:

1. any one of the three direct relations lacks coherent participant meanings, a coherent obtaining rule, or a coherent occurrence-identity rule;
2. a DDD case needs a materially different relation organization rather than this three-relation organization; or
3. selecting the joint organization changes no practitioner decision compared with stopping at the direct relations.

The external sources therefore change recognition and the tests applied to the working problem. Current FPF direct governors and the scoped, defeasible synthesis above supply the normative Solution. Constructional ontology tests a construction claim; it neither chooses the FPF kind nor proves the no-holon conclusion by citation.

#Relations

• A.1 governs constructive recognition of exact candidates under already admitted holon kinds and its locally declared U.System/U.Episteme distinctions. Direct identity patterns define or constrain candidate identity; E.24.UK governs public-kind admission; A.14 and direct part-relation patterns define or constrain parthood; C.13 governs constructive assembly.
• A.22 governs base U.Structure identity through exact constituents, selected obtaining relations, applied constraints, and one named selection-use frame. It also governs the conditional cross-structure question after a direct crossing governor exists.
• C.2.1 governs model, expression, rule, inference, and description episteme identity, effective reference schemes, exact EntityOfConcern and ClaimGraph content, EpistemeEditionRelation, and empirical grounding. It also identifies the separate bounded-use claim about an F.9 Bridge.
• A.2.6 governs U.ClaimScope, U.ContextSlice, and membership. C.16 governs measurement bases, readings, scales, units, and direct comparability. A.2.4 and A.10 govern evidence use; F.10 governs status family and status use; B.3 governs assurance.
• A.2 distinguishes local system-role kinds and their classifications. A.2.1 defines and tests U.SystemRoleAssignment species, occurrences, and states; A.2.7 defines and tests any separately needed relation among system-role kinds in model-use loci. E.10.ROLE routes any other technical use of role before one of these claims is selected.
• A.3.1, A.15.1, and E.18 govern Context Mapping method, performed mapping Work, and transformation-flow structures. A.15.PROD enters only for a separately needed local entity-inception claim.
• F.17 and F.18 govern sense cells, durable public labels, candidate-name history, public rows, lineage, and name refresh. A.1.1 consumes the settled names without copying their dossiers.
• F.9 defines an obtaining Bridge between exact F.17 SchemeSenseCell values. A Bridge carries relation semantics, not a receiving-use decision or a structure-to-structure crossing. A separate C.2.1 claim states bounded suitability. A.10 handles ordinary reliance; B.3 adds a bounded result only when an actual named assurance claim is current.
• E.17.0, E.24.PUB, and C.29 separately govern view conformance, publication occurrence and availability, representation, rendering, form, and carrier.
• C.2.P recovers an exact source expression and routes any source-use relation to its direct governor.
• A.6.0 and A.6.5 govern the RelationSignature and SlotSpecs declared here; A.6.REL governs progressive explicit individuation after the direct relation kind, obtaining condition, and occurrence-identity rule exist.
• F.19 tests whether an explanatory guard is justified for the intended reader.

#A.1.1:End

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