Search words, quoted phrases, and exact IDs across the current corpus.
By default, all meaningful words must match the same source passage, in its text or titles. Matching ignores letter case. Ordinary word queries skip common English function words such as the, and and or; quotes keep a phrase, and uppercase operators control matching.
| Example | What it does |
|---|---|
controlled variation | Requires both meaningful words; their order may differ. |
"controlled variation" | Requires adjacent words in that order. |
SYSE.24:4 | Prioritizes the exact named section. Pattern IDs also work. |
engineering OR management | Matches either alternative. Write OR and AND in uppercase. |
engineering AND (research OR management) | Requires engineering together with either grouped alternative. |
engineering -management | Excludes passages that match management. |
title:"controlled variation"body:"controlled variation" | Restricts the phrase to section/publication titles, or to source text. A field prefix applies to the following term or phrase. |
"controlled variation"~1 | Allows one intervening word in the phrase. |
"controlled vari"* | Requires adjacent words, with the last word as a prefix. |
engineering^2 OR management | Gives engineering matches more ranking weight. |
The Publication, Suite and Type filters narrow the same query. Results are source passages, not generated answers. Search does not translate, expand synonyms or automatically correct spelling. For a task expressed in another language, try English terms and read the context. Press / to focus the search field.
A.1.1 - Bounded Model-Use Structure: Applicability, Use and Expression Coherence (DDD Bounded Context) Type: Part A architectural ontology pattern Status: Stable Normativity: Normative unless marked informative…
In C.26.1 - Probe-Coupled Boundary Interaction
This worked use slice is not a standalone pattern. It tests DDD and bounded-context work when the context cut is not only discovered but also changes meaning, coordination, export validity, or viability. Ask: was the bounded-context cut merely discovered, or…
In A.6.3.CR - ConservativeRetextualization: EntityOfConcern-Preserving Textual Re-Expression
A case under ConservativeRetextualization preserves the same resolved EntityOfConcern, the declared bounded context, and the already available claim-bearing source while changing wording, register, language, ordering, or density. It states what remains…
In E.10.D1 - Recovering What “Context” Means in Use
E.10.D1:8 - Common Anti-Patterns and How to Avoid Them Anti-pattern What fails Repair Universal Context proxy One entity stands for source scheme, scope, situation, architecture, and model-use boundary. Select the branch and name the direct value or relation.…
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…
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…
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…
In G.6 - Evidence Graph and Provenance Ledger: Citable Evidence-Provenance Paths
A PathId identifies one claim-local path inside an EvidenceGraph. A PathSliceId identifies the same path under a declared time window, reference plane, bounded context, edition, bridge, policy, or selected object/relation subset. Use this compact record:…
In F.9 - Relate Local Meanings across Contexts (Alignment and Bridge)
Start with the two exact local senses, not with a context object, mapping table, or card. Resolve each endpoint as an F.17 SchemeSenseCell coordinate: For F.9, semantic bounded context is a Plain practice name for the local interpretation basis recovered from…
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 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…
In C.26.1 - Probe-Coupled Boundary Interaction
… notes. Context-word drift Context hides source-local meaning, a selected model-use organization, ClaimScope, a probe frame, or a measurement setup. Name the actual value. Retain bounded context only when using the established DDD term. Relation token…
In E.10.D1 - Recovering What “Context” Means in Use
E.10.D1 defines no U.BoundedContext, generic Context, universal ContextId, or two-part SenseCell(Context, LocalSense). A source or subject pattern may define a value whose established designation contains context; keep that designation and its defined…
In A.6.H - Wholeness Language Unpacking — RPR-WHOLE
… or what belongs under the collection’s own rule, an acting system, system-role assignments, and a selected collection structure; context, environment, discipline as a whole — name the actual bounded context, episteme family, community, organization, or other…
In
… ToC row, bounded-context label, system, team, subsystem, view, diagram, publication, or named use is treated as if it created a base U.Structure identity or specialization membership. Declaration and representation elements become U-kinds. A participant…