E.4:4 - Solution
Describe an FPF-grounded pattern ecosystem as a family of framework editions and publication and access-facing presentation carriers, plus access routes, over selected structures. For each durable ecosystem-architecture claim, or technical claim on which later work will rely, state the exact subject and relation and cite the defining or constraining ClaimGraph in its subject pattern. The smallest route below needs no ClaimGraph citation when ordinary guidance or a stop already answers the question.
A principle framework edition renders a selected architecture in pattern-language form for a declared reader and use. That architecture covers recurring problem situations, forces, known failure modes, reusable SoTA solution moves, consequences, cases, relation records, evaluation methods, and refresh conditions. Known failure modes include beginner mistakes and experienced-practitioner failures caused by stale, local-only, or non-SoTA practice.
Start with the smallest route that answers the current question:
-
Name the ecosystem question and who needs the answer.
-
Classify the likely case: a framework-family boundary, an adjacent result or service, a publication carrier, access-facing presentation carrier, or access route, a DPF-suite question, or another relation that an existing pattern addresses.
-
Point to the pattern that addresses the case and state the next useful move, or stop with the missing distinction.
-
Open the complete ecosystem-architecture record only when the answer must persist as ecosystem architecture or later work must rely on the selected structures and relations.
This route is ordinary guidance, not a new record or package. A supplying pattern or stop is a complete first result when no durable ecosystem-architecture record is needed.
When the available methods are insufficient for the needed result under the relevant conditions, use C.39 to find or develop a missing operation or connection. When a method and its connections need a reusable explanation in a framework, use E.4.CM to develop that explanation, choose its placement and provide a reader entry. An adequate available method can be used directly.
Create an ecosystem-architecture record only if the answer must settle durable architecture or support later reliance. Use the fields the claim needs:
FPFEcosystemArchitectureRecord@Context:
ecosystemScopeRef
intendedArchitectureUse
claimScopeRef?
sourceRefs?
patternHostRefs?
selectedArchitectureStructureRefs?
publicationRelationRefs?
boundedModelUseStructureRef?
frameworkFamilyMembers
selectedPatternSetRefs
selectedProblemSituationStructureRefs
selectedKnownFailureModeRefs
selectedSoTASolutionMoveRefs
selectedSolutionMoveStructureRefs
selectedRelationRecordRefs
frameworkCarrierRenderingRefs
selectedDependencyAndEditionRefs
selectedPublicationOrAccessCarrierRefs
selectedSourcePackRefs
selectedDecisionRefs
qualityAndImprovementRefs
currentnessAndRefreshRefs
blockedOverreadRefs?
dependentUsePatternLocators
This record answers the declared ecosystem question for its intended use. Include blockedOverreadRefs only when F.19’s grounded-contribution test admits them; otherwise omit the field. The record carries a contextual ecosystem answer; the subject claims and patterns it cites remain its content sources and semantic loci.
Classify the family members as follows:
Conceptual Core names FPF’s general conceptual content within the existing Core, Tooling Reference and Pedagogical Companion family partition. An FPF edition is an identified body of framework content. Its publication units present that content, and readers obtain them through available access routes. The FPF Core pattern set consists of the selected Core subject patterns in that FPF edition. A framework-edition dependency names the relied-on FPF edition and the Core claims required for its use.
The Kernel is the subset of Core content that defines admitted universal meta-concepts and the rules for their meanings and relations. Membership follows that defining content, wherever it occurs in the patterns. Other Core content explains reusable methods, states their conditions and grounds, or governs the framework. All eleven E.2 pillars remain constitutional first principles outside the Kernel subset; they govern both Kernel and other Core content.
Readers obtain the relevant content from an FPF publication and use the supplying patterns for the question at hand. A pattern can contain both a definition and an explanation of its application. A Part heading, file boundary or selected rendering therefore does not define the Kernel’s membership or constitute a separate Kernel edition. The Architectural Reference explains the framework as a whole; the pattern bodies retain the definitions, conditions and methods on which a use relies.
A domain or local framework identifies the Core content and edition on which it relies. That content may include a Kernel definition, a general method or a constitutional authoring requirement. The dependent framework supplies its domain or local problems, methods, sources and use conditions. Authors can revise those contributions while preserving the relied-on meanings and obligations; a change to a supplying claim reopens the uses that depend on it. A shared publication carrier supplies access to these frameworks without merging their content or edition boundaries.
| Family member | Architecture contribution | Authoritative content loci |
|---|---|---|
| Conceptual Core | Core FPF distinctions, rules, and patterns that other FPF-grounded frameworks depend on. | E.4, E.5.3, and the subject patterns containing the defining ClaimGraphs |
| Tooling Reference | Optional tools, schemas, scripts, machine checks, or helper publications that inspect or support FPF use. | Use E.17 for a source-backed publication face and return to source, E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability, and relevant tool patterns for their declared tool functions; use G.5 only for a selector-facing selected-tool-set result declaration. |
| Pedagogical Companion | Tutorials, playbooks, worked examples, and learning material that teach FPF without changing Core meaning. | E.17, didactic patterns |
| Foundational principle pattern set | Foundational threshold material or principle patterns that may support FPF-grounded use but need settled names and dependency boundaries. | F.18, E.4.PFR |
| First Principles Framework edition | The scoped FPF framework edition as a transdisciplinary first-principles framework with Core pattern set, publication and access-facing presentation carriers, access routes, relation records, and whole-FPF adequacy route. | E.4.FPF, E.2.DA, E.4.PFR, E.11, E.17, G.11 |
| FPF Core pattern set | The selected Core subject patterns in a named FPF edition. Framework dependencies identify that FPF edition and the relied-on Core claims. | E.4.FPF:4, E.4.PFR:3.4, E.5.3, and the cited Core subject-pattern claims |
| Domain principle framework | A framework grounded in FPF and domain SoTA; a DPF Suite describes a composite discipline through constituent DPFs and justified whole-level patterns. | C.20, E.4.DPF, G.2, E.4.PFAD, E.4.PFR |
| Local practice framework | A framework for one bounded local practice setting—for example a project, organization, workflow, tool, practitioner position, or audience—grounded in FPF and often in a domain framework. Add a local system-role kind, a separate System-classification judgment, or an assignment occurrence only when the framework claim independently uses it; recover ambiguous role wording through E.10.ROLE. | E.4.DPF, E.4.PFAD, E.4.PFR, G.11 |
E.4:4.1 - Place support units and adjacent products
In this pattern, product is Plain management wording for a deliberately identified result or service boundary. It helps a team state intended use, identity or current state, access, later change and retirement rules, and any maintenance that obtains. It is not one FPF technical kind and it creates no U.Product.
Before making a product-boundary claim, name the direct subject—the thing the claim is about—and the relation that carries its identity, edition, current state, provision, publication, availability, or maintenance. The subject may be, for example, a framework-edition episteme, an evidence-package episteme, an admitted System, an admitted service arrangement, a Method, a programme-description episteme, or another result already admitted by its subject pattern.
Constitution or publication establishes only the claims made by those acts; maintenance and future Work need their own evidence. If the direct kind or relation is not settled, keep the management boundary as a proposal and return that question instead of inventing a common object kind.
A framework edition is an episteme. Treat its Readme, architectural reference, table of contents, pattern-body collection, framework-scale structure or coverage account, relation or edition note, and refresh route as named publication units in the same managed boundary when they share the edition’s declared readers and use, edition boundary, access, and change rule. Being outside the pattern set or in another file does not by itself create another product or a maintenance claim.
Make a separate adjacent product only when people need to change, cite, or use its direct subject independently. Look for an independently useful identity, edition or current state, named users and use, an intensional rule for what belongs, access, a later-review or retirement rule, or cross-framework reuse or reliance. A separately established maintenance relation may also matter, but product identity does not require it. Examples include a registry, MethodDescription collection, evidence package, guide, tool reference, access service, or inquiry programme; other direct subjects may also justify a separate boundary.
The label does not settle the kind: a guide or evidence package may be an editioned episteme; a tool reference may identify an episteme, a tool System, or both; and an access service needs its own service and provider-System claims. File location does not decide the boundary.
When the direct subject is independently used or changed, keep it separate and point from the framework to the edition or current state being used. An annex may carry a declared snapshot or projection, but it returns to the authoritative subject and does not fork it. When no independent boundary is useful and ordinary framework use needs the material, keep it as a named support publication unit of the framework edition.
An architectural reference is the public account of how a named method language is assembled and why that arrangement helps its intended users. It explains the whole’s purpose, constituents, relations, shared conditions, alternatives and limits, with the rationale and source synthesis needed to understand and adapt it. Give the unit the full public name <name of the explained whole> Architectural Reference, for example FPF Library Architectural Reference, Engineering Suite Architectural Reference or Method Engineering Principle Framework Architectural Reference. A shorter mention is sufficient once the explained whole is unambiguous. The qualified name identifies the account’s subject; it does not select a filename, section key or independent product boundary.
Provide this account at each level of language assembly: patterns in a framework, constituent frameworks in a Suite, and Core, Suites and standalone frameworks in FPF Library. Each account explains the connections added at its level and returns to the full constituent accounts and patterns. That descriptive assembly does not make every Method part of one composite Method or every described discipline part of one discipline. A Suite’s disciplinary composition still needs C.20; a library-wide connection can instead be use, specialization, shared terminology or another stated relation.
The account belongs to the explained language. In a one-file framework it can be embedded; in a multi-file assembly it has a discoverable unit at that assembly level, which can be carried separately. Keep its relation to the whole explicit in either form. Source hosts, directories, generated pages and site slices do not create further language levels merely by dividing files. Do not duplicate an account for each carrier, and do not require it before a known pattern can be used directly.
One presentation carrier may expose several managed products without merging their subjects. Each constituent keeps its identity, edition or state, form, access, later-change and retirement rules, and any separately established maintenance relation; the outer navigation names the constituents and stays neutral. A result reused by several DPFs may therefore be managed as an ecosystem companion or service product. Shared use does not make it a parent DPF. Open another DPF only when its field-boundary assessment finds recurring practitioner problems, constructive Methods, an independently useful first cut, evidence practice, and its own edition and change boundary.
When programme is used, start with what continues. An inquiry programme may be managed as a continuing programme or service product, but neither label says what persists. If a subject pattern admits the programme as a System or another arrangement, name it. Otherwise name the current programme-description episteme and any provider System, maintenance relation, accepted commitment, or service state that independently obtains.
Bounded inquiry projects require independent A.15.1 admission as separate Work occurrences, and their results remain separate epistemes. A maintained inquiry evidence package is its own editioned episteme. The management boundary may coordinate these subjects and relations, but it does not turn them into one indefinitely continuing U.Work or one generic Product. If the persisting arrangement is still unclear, return that architecture question.
DRRs, build manifests, quality runs, digests, logs, and campaign state remain development or process evidence by default. Publish the architectural reasons that affect use in the language’s architectural reference or the relevant pattern, so readers need not reconstruct them from those records. The dated development, review and release history stays in its records. A selected public use can give a record its own product identity and publication route; ordinary understanding of the language does not require that separate publication.
Use these tests in order:
- Name the intended managed boundary and ordinary use.
- Identify every subject the decision makes a claim about, its kind and the identity or current-state relation the decision uses for that subject.
- Group only publication units that share the framework edition, readers, access and change rule.
- Test a proposed adjacent subject for independent use and change.
- Select the smallest useful boundary.
- Record exact pointers to those subjects, the return from each snapshot and the navigation from the neutral carrier.
Establish maintenance only when a maintained claim is made. If a needed kind or relation remains unresolved, record that question and stop short of the technical product claim.
E.4:4.2 - Describe a composite discipline with a DPF Suite
Use this branch when a proposed field contains several subdisciplines and the reader needs both their own Methods and the Methods that connect their contributions. First establish the discipline and its composition through C.20. Then describe that whole in a DPF Suite. A convenient selection of publications, several suppliers to one project, or a common audience can justify a reading route without establishing a composite discipline.
A DPF Suite is a domain principle framework for a composite discipline, assembled from the frameworks of its constituent subdisciplines and any justified whole-level patterns. It is a larger DPF, not another ontological kind of field and not a collection constituted merely by a publisher’s inclusion decision. The described discipline is a U.Discipline; a Suite edition is a U.Episteme about that discipline. The constituent DPF editions describe its subdisciplines. A directory, website or combined file presents those descriptions. None of these is identical to the discipline.
E.4:4.2.1 - Recover the field before arranging its descriptions
State the field’s recurring questions, objects of inquiry or intervention, characteristic results, knowledge and reusable practices. Use F.18 for a name that makes that field recognizable. A university subject, profession, conference or community is useful evidence of an established field; it does not by itself establish either the field’s exact boundary or a constructive part relation.
For each proposed subdiscipline, recover the C.20 construction:
- the knowledge-bearing and reusable-practice contributions it makes to the larger field;
- the relations by which those contributions constrain, enable, test or revise other required contributions;
- the whole-forming arrangement, including admitted alternatives and how a part can be replaced without losing the field;
- the field’s identity through changes to theories, Methods, instruments and institutions;
- a whole characteristic that the composition produces or sustains, with its grounds; and
- how this whole can participate in a larger disciplinary assembly.
Explain the coupling in practice. For example, an account of ground behaviour constrains a foundation design; the design identifies what site evidence is needed; observations and failure investigations can revise the account and design Methods. A bibliography listing geotechnics and structural engineering supplies neither this coupling nor a framework that teaches it. Nor does every construction project need to use every branch of those fields.
Use this field construction to reconsider the current Suite architecture. An intake may justify a new Suite, a split or merger of existing Suites, or a change to their boundaries; inclusion in an existing Suite is one possible outcome.
A Suite may describe a bounded, explicitly incomplete portion of a recognized composite discipline. State which constituent subdisciplines and whole-level problems it currently covers, which are outside that coverage, and what the reader can obtain. Partial coverage must not be presented as a complete account of the field. A planned constituent with no usable description is a gap, not an available DPF.
A first Suite edition may contain only one available constituent DPF when the composite field, its other constituents and their whole-forming relations are already established. The common account must offer a present use: for example, explaining where the available contribution applies, which connections it relies on and which needed results the edition cannot yet supply. Compare this benefit with keeping the DPF standalone until a common assembly is useful. One DPF plus an unspecified intention to add more frameworks does not establish a Suite.
E.4:4.2.2 - Distinguish composition, specialization and use
Do not infer one relation from another:
| Relation | What must be established | Publication consequence |
|---|---|---|
| A subdiscipline is part of a composite discipline. | C.20’s direct part relation and whole construction, including knowledge-practice coupling and continuity. | Its DPF is a constituent description in the Suite; the Suite explains the connection to the whole. |
| One Method or field is a specialization of another. | The inherited construction or constraints and the added subject-specific conditions. Specialization alone does not establish disciplinary parthood. | Retain the general supplier and develop the specialized contribution where its assumptions belong. |
| Work in one field uses a result from another. | The required result, supplying Method, receiving use and relevant conditions. | Give a direct use or dependency link. Do not include the supplier’s entire DPF merely because that result is useful. |
| Several publications answer one question together. | Their contributions and the conditions for combining them. Use G.5-6 DeclareSetResult only when the already justified joint inclusion must be declared as a JointUseSet. | Supply a cross-framework entry or composition. This need not create a Suite. |
| A publication supports navigation or access. | Its information need, answer, source return and availability. | Keep it as a support publication or independently useful reference; it is not a subdiscipline. |
An engineering decision may need finance, research, mathematical modelling and ethical judgement. Their use does not make their entire disciplines parts of Engineering. Conversely, a subject-specific engineering branch does not become an external supplier merely because its Methods are used in only some projects. Test its participation in the continuing field assembly, not the participant list of one Work occurrence.
Do not force the discipline structure into a tree for filing convenience. If multiple parthood is proposed, establish each direct relation and explain the shared contribution, whole-forming couplings and consequences of change in each assembly.
First test whether the apparent overlap is a general Core Method, an independent supplier, specialization or two different subject-specific contributions. If it is, publish that distinction instead of duplicating whole DPFs. If shared constituency remains, identify one current constituent description and explicitly assemble it into the affected Suite editions; a casual hyperlink or an unqualified second copy cannot carry that claim.
E.4:4.2.3 - Build the larger pattern language
Develop the Suite as a framework under E.4.DPF and E.8. Its entrance explains the composite field, the contribution of each constituent and the important relations between them. A long mantra can help a practitioner retain a connected Method, but neither that phrase nor a Reference substitutes for the Methods it recalls.
Give a whole-level Method its own pattern when it removes a recurring difficulty that the constituent Methods do not independently solve. State its problem frame, problem, forces, construction, limits and cases. The construction may consume results from several DPFs and return questions to them. If a contribution is transdisciplinary, develop it in Core instead of hiding it in a Suite introduction. If the missing work is specific to one subdiscipline, develop it there. If it reveals another field, reopen the field architecture rather than stretching a pattern or an appendix around it.
Expose enough of the language for a reader to select constituent Methods, understand their contributions, combine them where justified and retain their separate assurance obligations. Preserve alternative configurations; a Suite is not a mandatory sequence through every DPF. Use E.11.PFP for the Suite’s framework entrance and constituent frameworks. Use E.11.DSG to develop the Suite’s architectural reference, including useful problem-led entries. It covers the whole’s architecture and can return both constituent and external contributions, labelled by their relation.
An additional explanation of already described Methods belongs in the relevant pattern or architectural reference. A useful new operation or composition needs its own complete E.8 pattern; a mantra or reference entry cannot hide its missing construction.
A teaching course or Guide with a separate learning purpose is a pedagogical companion, while explanations and cases needed to use or adapt the language remain with that language.
E.4:4.2.4 - Make the publication reflect the architecture
Give each current full Method description and constituent DPF an unambiguous authoritative home. Assemble the Suite’s publication from its selected constituent editions and its own framework-level explanation; make that composition and the editions used recoverable. A Suite directory can be a convenient physical assembly of the complete constituent publications. A standalone DPF needs no artificial Suite. The FPF Library Architectural Reference explains their library-wide connections and boundaries; the library index locates the publications. Neither the index nor that account establishes another discipline above them.
Keep four kinds of change distinct:
- A change in the discipline’s knowledge, practice or composition is judged through C.20’s identity and part relations.
- A change to the framework description produces or revises a framework edition under C.2.1 and C.2.P.
- A change to files, layout or access can preserve that edition while changing its presentation or availability.
- A change in publication or maintenance responsibility changes those relations. That change alone does not change the described field.
An editorial decision can select what a Suite edition describes. It cannot make a non-constituent field become a subdiscipline, and it cannot preserve an unsupported part claim until someone formally removes it. Correct the description when its claim is false; qualify incompleteness or uncertainty when the evidence is insufficient. Conversely, an unavailable file or retired framework publication does not erase a discipline.
For a release or reproducible use, identify the Suite edition and the constituent editions it assembles. An optional configuration description can pin those selections; it remains an episteme about the assembly, not the assembly’s disciplinary subject. A separately maintained Reference can evolve independently while preserving its source returns. Apply E.4.PFIP when reconstructing publications: preserve useful Methods and their conditions, correct erroneous architecture, and update maintained links to the current full explanations.
E.4:4.2.5 - Keep edition series separate from disciplinary structure
When a use needs continuity across releases, a framework product series is a continuing collection of edition epistemes. A constitution decision starts it by identifying at least one existing edition, its intended readers and use, content-selection and edition-admission rules, a reidentification rule, and later-review and retirement conditions. When that decision takes effect, the series begins and the first edition is admitted. The decision Work and its record remain separate from the series and the edition’s belonging to it. Publication, maintenance and future availability require their own claims.
A later edition joins only when its source-edition relation and the series rule hold and a further admission decision takes effect. A fork or translation is not admitted by provenance alone.
The series need not have one total version order. Supersession, unavailability, non-currentness or edition retirement does not end the edition’s belonging while the same series continues, and a return to availability does not create a new occurrence.
If the series ends or is reidentified as another series, current belonging to the old series ends; the past fact remains. Another series needs its own admission decision. If a claimed earlier admission never satisfied the rule, correct the false claim instead of preserving it as historical truth.
The same publishing arrangement can be used for a constituent DPF, a Suite framework or an independently managed Reference. It describes their publication continuity, not DisciplinePartOfRelation. A series may end while the described discipline continues, and a revised Suite edition may correct its account of that discipline. Establish publication, availability and maintenance separately through E.17, E.24.PUB, C.2.P and G.11 when those claims matter. Do not make a routine reader reconstruct admission decisions merely to use a current Method.
E.4:4.3 - State the ecosystem architecture for the declared use
For a durable ecosystem-architecture answer, use the following operations as their conditions apply:
- Declare the ecosystem scope and intended architecture use. Cite the exact source, pattern host, selected architecture structure, publication relation, or bounded model-use structure only when the record relies on it.
- Name the family member being created, used, or changed.
- Name only the fields from
FPFEcosystemArchitectureRecord@Contextthat this architecture claim uses. For PF work, the pattern-language publication carrier exposes a reader-facing expression of the selected problem-and-solution architecture. - If the family member is FPF itself as a framework edition, open
E.4.FPFfor form, presentation carriers, access routes, and whole-FPF adequacy routing. - Apply
E.5.3: dependencies point toward more stable framework editions. FPF Core does not depend on domain or local frameworks. - State publication and first-entry claims using
E.11andE.17; state framework-carrier structure-account assertions usingE.4.FPFfor FPF itself orE.4.DPF/E.4.DPF.DAfor domain and local frameworks. - State pattern-use recommendation claims using
E.11.PUR. - When a framework-architecture question is open, record the selected answer in one
E.9DRR and useE.4.PFADto profile its framework-specific content. UseC.32.PADonly for a project architecture decision andC.32.ADRonly to project such a decision into an ADR-like publication. - State relation, dependency, compatibility, deprecation, and edition claims using
E.4.PFRonly when its named maintenance use requires that representation; otherwise use the direct subject assertion. - Settle names using
F.18. - Ground source-use claims in the relevant source content. Apply
E.8:11to a SoTA comparison. Reuse a sufficient direct source answer; useG.2when a broadCG-Framesource pack and its downstream handoffs are needed. - State currentness, refresh, and edition-change claims using
G.11, the exact edition values, and their source/currentness assertions. - Before using a carrier or transformed or generated view as evidence, state the exact source-return or preservation assertion under the predicate defined in
C.33,C.34, orC.35. - Evaluate whole-FPF adequacy through
E.2.DA, DPF or local-framework package adequacy throughE.4.DPF.DA, individual pattern quality throughE.21, improve throughE.23, and useE.19for a selected admission, refresh, or return-for-repair question.
When placing a foundational contribution, identify what would settle a disagreement about it. Give a Core rule the premises its users need. If several Core definitions depend on one commitment and their separate passages cannot reliably keep it consistent, state it once in Core and refer to it from those definitions. Put a method of deriving those premises or testing their physical interpretation with the discipline that can correct it. A separate edition earns its place when independent consumers must adopt the same commitments and check compatibility as they change. A reading order can be supplied in the Reference. Use B.5.MR when the claim concerns refinement or abstraction between models.
Core, DPFs and LPFs can supply models at several levels. When each pair passes the B.5.MR comparison for the same inquiry, read the chain from a formal construction through a transdisciplinary principle, a disciplinary model and a local model towards an individual model as levels of model refinement. In reverse, read levels of model abstraction. A DPF can carry a foundational construction as well as a disciplinary model. A method for testing a physical interpretation belongs with the discipline that can correct it, even when its result supplies a premise for Core.
Use this routing table when a proposed change is ambiguous. Its rows are common routes, not a closed taxonomy:
| Proposed work | Route to | Decision boundary |
|---|---|---|
| The form of FPF itself changes: README, Architectural Reference, ToC, monolith, host set, skill pack, MCP-backed access, or whole-FPF publication/access route. | E.4.FPF, with E.2.DA for whole-FPF adequacy; state relation or edition claims directly and open E.4.PFR only for its named maintenance consumer. | FPF uses the whole-FPF route, E.4.DPF.DA remains the package route for domain or local frameworks, and the carrier exposes the framework edition as a separate subject. |
| Accepted changes are being assembled into an FPF, DPF, or LPF publication, or continuity with a predecessor publication is claimed. | E.4.PFIP for the accepted-source and predecessor-preservation comparisons. | Require both PFIP conclusions when both claims are made. Source parity, build success, carrier continuity, and package adequacy answer narrower questions. |
| A distinction or rule is intended to constrain ordinary FPF use across many domains and downstream frameworks depend on it. | An accepted FPF Core amendment decision under E.9, followed by the subject patterns whose assertions change. | Core admission requires the transdomain constraint and accepted amendment decision; local and domain guidance stays in its framework edition. |
| A reusable principle supports FPF-grounded work but is not a general Core rule for all domains. | Give the foundational principle pattern set or other named framework edition its own identity; state its dependency directly and open E.4.PFR only for its named maintenance consumer. | The framework edition and dependency boundary stay visible outside the Core table of contents. |
| A source tradition or professional domain needs FPF-shaped patterns. | Domain principle framework through E.4.DPF, G.2, and E.4.PFAD; state dependencies directly and open E.4.PFR only for its named maintenance consumer. | The framework adds recurring domain problems, SoTA solution moves, cases, and use conditions to its source account. |
| One bounded local practice setting—for example a project, organization, workflow, tool, practitioner position, or audience—needs guidance. | Local practice framework through E.4.DPF; keep local source, publication, quality, and refresh records, and state separately any direct relation used for maintenance, responsibility, authority, assignment, or contact. If a load-bearing owner label has no current direct relation, return missing-governor instead of inventing one. | The named local setting bounds the guidance; a general FPF rule requires its own Core-amendment grounds. |
| Material needed for ordinary framework use shares the framework edition, readers, access, and change rule. | Keep it as a named support publication unit of that framework edition and expose it through the edition’s carrier route. | Another managed product needs an independent use or change rule. |
| A registry, guide, evidence package, service, programme, or other result has an independently useful identity or state, users and use, content rule, access, or later-review and retirement rule. | Name its direct subject and the relevant relation, keep it as a separate product, and point to the edition or current state being used; any embedded snapshot returns to that source. State maintenance only when it separately obtains. | Keep direct subjects separate under shared use, co-location, or one outer carrier; an unresolved kind remains a proposed product and an open question. |
| One carrier exposes several managed products. | Keep the outer carrier neutral and retain each subject’s form, identity, access, change rule, and any separately established maintenance relation. Use E.11.PFP only for FPF, DPF, or LPF constituents. | The neutral carrier exposes those subjects; framework-family fields apply only to framework constituents. |
| Several fields appear to form one larger discipline. | Use C.20 and E.4:4.2 to distinguish constituent subdisciplines from specialization, external use and publication grouping. Use E.4.PFAD to decide the framework architecture and E.4.DPF to develop the composite pattern language. | A Suite describes the established disciplinary composition. Its edition assembles constituent DPF descriptions; a Reference supports use, and neither a folder nor an inclusion decision establishes disciplinary parthood. |
| Existing material is hard to find, teach, or publish. | Use E.11 for discovery, the relevant didactic pattern for teaching, E.17 for a source-backed publication face and return to source, and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability. Use G.5 only when the missing value is a selected-set result declaration. | Treat findability, teaching, and publication as their repair questions; architecture repair requires an architecture claim. |
| A cross-reference claims use, specialization, dependency, publication, source reuse, preservation, quality, deprecation, or supersession. | State the relation function and edition effect; open E.4.PFR only for its named maintenance consumer. | The link label remains a locator; the predicate states the relation meaning. |
| A framework split, dependency boundary, presentation-carrier or access-route choice, or adoption consequence must be decided. | Record one selected answer in an E.9 DRR, using E.4.PFAD for its framework-specific content. Use C.32.PAD only when the decision is a project architecture decision and C.32.ADR only to project such a decision into an ADR-like publication. | The DRR carries the selected answer; diagrams, folders, manifests, PFAD relations, and project-specific projections may expose only what each of them directly states or shows. |
| A source, search result, transformed view, or generated carrier supplies candidate material. | G.2, C.33, C.34, or C.35 before architecture use. | Use the admitted source or preservation claim as authority for the declared contribution. |
| Whole-FPF adequacy, DPF package adequacy, individual pattern quality, repeated improvement, admission gating, or currentness is the live problem. | E.2.DA, E.4.DPF.DA, E.21, E.23, E.19, and G.11 according to the claim. | Use the evaluation or refresh route for the live question; package and whole-FPF conclusions remain distinct from aggregated pattern scores. |
This pattern should leave the reader able to state the architecture directly. Name the family member and selected pattern-language architecture, then state its dependency editions, publication or access carriers, preserved structures, and each neighboring claim under its exact predicate with the subject pattern as locator.