E.4.DPF - Domain and Local Principle Frameworks: Whether and How to Author and Publish
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative.
E.4.DPF:1 - Problem frame
Use this pattern when a group needs to create a domain principle framework or local practice framework grounded in FPF: for example a hydroponic-cucumber framework, a neural-network architecture framework, or a Codex-process framework.
This pattern explains how to author or revise an FPF-grounded framework. Start by writing one paragraph that names the intended reader, the domain or local situation, the first useful action, and the ordinary stop or wrong-turn return. Add a non-use boundary only when an independently grounded competing use is plausible for that reader and changes action. That paragraph is enough to enter the first-hour route before the framework architecture, durable names, or publication package are settled.
Use this pattern when the work creates or revises the framework. Use E.11 or E.17 when an existing framework remains unchanged and the work only changes how readers or agents find or access it.
E.4.DPF:2 - Problem
Domain and local framework authors often have strong source material and urgent local needs, yet three errors can undermine their use of FPF. They copy FPF terms without settling the domain ontology. They publish a framework carrier before deciding the framework architecture. Or they produce a useful checklist that is local process guidance but not yet an FPF-grounded pattern framework.
A working framework needs more than a good table of contents. It needs source-grounded pattern selection, architecture decisions, direct assertions of material relations, names, worked cases, quality evaluation, and refresh conditions. Include the relation or edition records a current maintenance use requires, for example for dependency, compatibility, migration, deprecation or supersession.
A DPF gives its intended users a source-grounded pattern language for recognizing typical problem situations in the domain, avoiding known failure modes, and applying SoTA solution moves with visible boundaries and refresh conditions. Its ontology and vocabulary support those moves. Known failure modes include beginner mistakes and experienced-practitioner failures caused by stale, local-only, or non-SoTA practice.
E.4.DPF:3 - Forces
| Force | Tension |
|---|---|
| Domain urgency | The local team needs usable guidance soon, but premature durable names and pattern heads freeze poor ontology. |
| Source richness | Domain traditions provide valuable methods and examples, but source summaries can hide rival traditions and lost evidence. |
| Problem-solving primacy | A DPF may need terms and ontology, but those are supports for recognizing recurring domain problems and choosing SoTA solution moves, not the framework’s payoff by themselves. |
| FPF reuse | FPF Core gives strong authoring, relation, and quality patterns, but direct copying can mask domain-specific concerns. |
| Publication need | A framework publication carrier helps readers, but it can hide relation, dependency, and currentness records. |
| Evolution | Domain and local frameworks change and improve as sources, uses, relied-on framework editions, and the required Core claims change. |
E.4.DPF:4 - Solution
Use the first-hour route to help a reader new to the framework decide whether authoring should begin. This route answers that question before asking for proposal, dependency, naming, quality or publication material.
- Name the intended reader, recurring working problem and useful result. Identify the user by the work they need the framework for. Follow E.8:4.2.3 when the distinction between doing the work and assisting with it changes whose decision or capability the result demonstrates.
- Recover candidate contributions from that problem and its sources before fitting them to the current Library: recurring practitioner problems, reusable moves or Methods, first useful results, ordinary stops or wrong-turn returns, and source or refresh boundaries. When the use spans several problem families, recover their consequential connections and the practice field or fields they serve. A field can include known Methods as well as missing ones; novelty of elementary operations is not its identity test.
- Inspect what FPF Core, existing domain or local frameworks, and current sources provide.
- Treat a role or competence account, several independently reusable contributions, a Card or mantra spanning material relations, a plausible field and refresh boundary, a representative use across contributions, or visible action or result loss under one broad owner as a cue to compare, not as proof of a DPF.
- In one recognizable situation, compare each contribution with the exact current FPF or admitted-DPF action, first useful result, stop or wrong-turn return, and source or refresh obligation. Include a non-use boundary only when
F.19’s grounded-contribution test admits it. Preserve whether it is carried by an exact current owner, supplied by an exact external result, an action-bearing remainder, or unresolved. A shared topic, role label, carrier form, missing product name, or missing PatternIDs cannot close the question. - When the receiving use depends on connected Methods, establish what the intended reader receives as a whole under E.4.CM:4.4 before treating the constituent suppliers as a complete answer. A remainder can be a connection, a Method, a whole field or several fields. Keep the framework question open when exact ownership is unresolved or closure would erase a material relation, field or refresh responsibility.
- Distinguish content reuse from the architecture answer. Existing coverage establishes what can be retained; it does not freeze the boundaries of the frameworks carrying it. When the recovered families or changed uses put those boundaries in question, compare their current organization with a revised distribution of existing and new contributions under E.4.PFAD:4.2. A new or revised DPF can inherit or receive existing Methods. Several fields can warrant a Suite; one large pattern, an application or an umbrella title does not settle their organization.
- Test a cheaper search, curated reading route, access-only result or stop against the same receiving use. Take it when the comparison closes every contribution and no later-used field, edition, relation, direct-subject, publication or access decision remains. A sufficient narrow result needs no survey of unrelated fields.
- If a reusable problem-solution language still looks useful, state its field promise, connected problem families, material relations and representative first use. Compare new and revised frameworks with contribution to an existing one; use the field-scale test in :4.0. Retain a narrow useful result as a seed, contribution, guide, direct source use or another result whose kind fits its use when that test does not support a framework.
- Sketch provisional pattern candidates at the scale of the recovered problems. One to four can be enough to test a small proposal; neither that range nor the size of one carrier limits the number of Methods or fields to recognize. Keep independently reusable problem–move–result contributions and their whole-use relations visible before choosing their publication grouping.
- Consider five outcomes: a new or revised framework, a contribution to an existing framework, a non-framework product, a thinner publication or access route, or no new maintained product now. Would the choice settle an edition, dependency, initial pattern placement or relation, direct-subject identity or change rule, or publication or access decision that later work will use and whose rationale another author or reviewer needs?
- If no, take the useful contribution, thinner route, other result, or stop without a DRR. If yes, use
E.4.PFADto state which of the same five outcomes was selected and its framework-specific consequences in oneE.9DRR.
The five architecture outcomes are alternatives, not successive stages. A separate organization-design proposal is useful only when a named review use needs candidate organization claims. A separate dependency description is useful only when a named next authoring use needs a stable account of dependency availability and relevance. Neither is a prerequisite for recognizing or answering the architecture question.
When a DPF answer is selected and authoring begins, grow the seed only as far as the next use requires: a source-pack stub; provisional public names; the first pattern candidates through E.8; ordinary assertions of the material relations among them; optional E.4.PFR rows for a named maintenance use; a publication or access consequence; and the first quality and currentness route. Add the effective ReferenceScheme, ClaimScope, qualification window, or a selected BoundedModelUseStructure only when those distinctions change interpretation for the receiving use.
Stop at the first useful result. A cheap route or stop needs no seed package. A rough DPF seed is inspectable when its reader, problem, useful move, source basis, provisional patterns and relations, edition/dependency boundary, publication or access consequence, and reopen condition are visible. Do not present it as a reliance-bearing DPF until the decision account is adequate for the intended authoring use, the pattern bodies are usable as normal FPF patterns, and the package is evaluated through E.4.DPF.DA.
Precision and object boundary after the first route. The first-hour route is Plain application guidance for one run-independent framework-authoring U.Method. This E.4.DPF episteme is a U.MethodDescription only because its EntityOfConcern is that independently admitted Method and its claims substantively describe how to carry it out under A.3.2. E.8 does not grant that membership. The Method, this description episteme, any U.WorkPlan, every dated authoring U.Work, and every result remain different objects.
If this account separately claims dated authoring or project U.Work, recover every precise performer’s A.13 core and independently admit that Work through A.15.1. Cite F.6 only when the account also needs precise assignment-bound attribution through the same obtaining A.13 assignment. The complete tests remain in those patterns. The first-hour and complete authoring routes require neither a Work claim nor performer or assignment evidence.
The Work may use this description through an identified A.6.1 application and bindings. Recover any local system-role classification, capability, authority, responsibility, maintenance, access, Method, Work, or result claim through the pattern that defines it.
The first useful output closes the immediate question. It may be one of the following:
- a cheap route or stop with no DRR
- one
E.9framework-architecture answer selecting one of the five outcomes in steps 8–9 - an optional organization-design proposal whose candidate claims need separate review
- a post-existence architecture-description use
- an optional dependency description needed by a named next authoring use.
These results are selected by their conditions, not by list order, and they do not form a mandatory lifecycle.
Choose the source route from the current question and the result it needs.
| Source situation | Authoring move | Boundary |
|---|---|---|
| One identified source claim answers the question | Record direct source reliance and carry the claim, edition, Context, and limits into the subject pattern. | Do not open semantic synthesis or a SoTA pack merely to repeat one sufficient source. |
| A maintained synthesis or guide already maps the field | Use it as the starting conceptual map. Recover each occurrence that can change the DPF decision, follow its cited sources where a load-bearing distinction depends on them, and inspect current rivals that could change the answer. | The maintained synthesis does not independently confirm the claims it integrates. |
| Several source ontologies can change one pattern contribution | Use the light route F.0.2 → F.0.1 → F.1 → F.0.2. Return a provisional synthesis claim, contrast claim, or unresolved-inquiry claim before the later DPF content decision accepts, changes, rejects, or reopens it. | The reusable method is in FPF; the resulting domain claim stays in the DPF subject pattern. |
A CG-Frame needs broad, refreshable SoTA harvesting and G.3-G.5 handoffs | Use G.2 to build the SoTA Synthesis Pack. A later F.0.2 comparison may consume identified claims, editions, alignment records, and provenance from that pack. | Pack conformance, coverage readings, and fusion records do not establish the receiving DPF claim. |
| An earlier DPF supplies a useful pattern or claim | Reuse its current edition through an explicit dependency when its subject, Context, use, and limits fit. Otherwise keep the result local to the receiving DPF, or return a transdisciplinary improvement proposal through an FPF amendment decision. | An earlier DPF is precedent and source material, not ecosystem law. |
| A search index, generated crosswalk, or other derived lookup proposes contributions | Resolve each useful result to the authoritative pattern or source body and edition. Report partial coverage and unresolved returns; widen the lookup when a known contribution is missing. | A derived hit aids discovery, and a miss does not show that the contribution is absent. |
Choose the constructive route by the missing result. C.39 supplies general construction, connection, explanation and change of Methods for a receiving use. E.4.CM applies that way to the framework author’s public account of one composite Method or several independently usable Methods. F.0.2 compares source ontologies for a semantic result.
Developing the Method can expose a missing distinction, and comparing source ontologies can change the proposed action. The work need not follow a fixed sequence from a complete ontology to a complete methodology.
E.4.DPF:4.0 - Establish framework scale before edition authoring
Run the candidate-recognition move in E.4.DPF:4 before a public product name, PatternID, pattern body, or pattern count is available. One Card, file, admitted MethodDescription, role account, or absent PatternIDs neither proves nor disproves framework scale; each can only supply evidence for the same semantic test below.
Do not infer a new DPF or LPF edition from the current authoring slice. One useful pattern is usually a seed, candidate, or contribution, so pattern_count = 1 is a strong diagnostic: ask whether the candidate supplies a connected pattern language rather than one useful result under a broad name. A few related patterns around one problem family may likewise form a useful selected problem-family pattern set inside an existing framework. In FPF, pattern nest remains the separate E.8 name for a publication and specialization placement grouping.
Run the same semantic test at every pattern count. A new edition needs a pattern language broad enough for its declared field or practice: a coverage map, selected problem-family pattern sets and material relations, a representative application, an internally usable first-edition set, an account of what the edition omits and where to return to its sources, and a credible edition, change, and refresh boundary.
Fail a candidate when those contributions are missing or do not work together for the named first use, not because its index has one row. Adding a second thin pattern does not cure that failure, while an unusually compact candidate still has to pass every part of the same test.
Develop the account of the field that the selected pattern language must explain. From the intended work and the relevant subject treatments, recover the characteristic entities, relations and operations, the grounds on which claims about them hold, and how practitioners obtain or revise them. Where the declared practice includes constructing its descriptions, units or operations, explain that construction instead of assuming it has already been supplied in the task data. Explain how knowledge constrains the choice and construction of a way, and how its use can challenge that knowledge; use C.20 when the framework describes a discipline.
Bring this account back to the proposed repertoire. Show why its grounds select, connect or change the contributions when a consequential condition changes. Use the result to retain or revise the problem families, pattern allocation and external reliance below. Publish the explanation through the account required by E.11.PFP:4.7 and its actual suppliers. It may be concise, distributed or interleaved with worked reasoning; it need not be one composite Method, a compulsory workflow or a separate ontology.
A successful application of the selected patterns supplies its bounded evidence, not the unexplained field account. Reuse an adequate current account and qualified source comparison rather than reconstructing them merely for a new edition.
Before authoring a new edition, the E.4.PFAD architecture answer states:
- what field or practice the public name promises to cover, the intended reader, the first use, and the ordinary stop or wrong-turn return;
- the recurring problem families, characteristic failures, and useful result families that the first edition includes or deliberately leaves outside;
- the candidate selected problem-family pattern sets and the material relations among their patterns;
- one representative application that crosses the patterns and problem-family sets needed for the first use;
- the selected first-edition patterns, every same-framework prerequisite needed for that use, and every relied-on external edition;
- what the sources and evidence support, including whether each load-bearing claim is actual, proposed, or still untested, and what must be realized or tested before a stronger claim is made; and
- where each contribution goes: into the new edition, back to an existing FPF or DPF, into an LPF or another available result, with its kind and supplying product identified, into direct source use, or into an explained decision to add no new maintained product now, together with the observation that would reopen the question.
During source comparison, recover useful wholes and their consequential joins as well as constituent operations. Source-coverage evidence answers what the sources contributed; it does not by itself establish recurrence, audience need or worthwhile public inclusion. Carry a missing composite, a meaningful variant or an anticipated use as a contribution to compare, rather than removing it because its parts already exist or publishing every source construction.
When audience preparation, the cost of learning and continued application, or a shared change boundary alters the framework answer, use E.4.PFAD:4.1.1. Its selected arrangement can include a method account for competent readers, pedagogical companions and short-use routes; E.8:4.2.1.1 keeps their content responsibilities distinct. An unwritten companion does not supply the learning it promises.
Before placing a proposed narrower contribution, apply E.8:4.1.3 to it and the broader available contribution in one recognizable situation. Keep or merge a warranted difference that changes the reader’s action or result; omit or merge a true duplicate; repair or reject an unwarranted difference.
If something else answers the question, distinguish an available result from a MethodDescription, direct-source evidence, and an unavailable result; state maintenance only when it changes that use. This decides one contribution, not whether the package covers its public promise.
The first-edition set is internally usable only when it contains every selected pattern and every prerequisite from the same framework needed for the named first use. Keep relied-on results from an FPF, DPF, LPF, or separate non-framework product external when they are not members of this framework.
For each external result, identify the result and the content relied on, and state the result’s direct kind, supplying product, edition or current state, receiving use, discovery route, and any currentness or availability condition that can change the use; say that it remains external. When the receiving use also needs a separate availability or compatibility result, identify that result and the basis on which it applies. When an edition dependency obtains, also name its direction, reason, and refresh condition.
If these facts are missing or the result does not answer the promised use, keep the family as a gap or omission; do not hide it behind the word closed.
When a keep, merge, removal, profile move, or external reliance materially changes the stable set for a promised problem family, obtain a current E.4.DPF.DA D12DomainProblemFamilyCoverageAdequacy result for the resulting exact DPF or LPF edition. Reuse a matching current result when that edition and its basis are unchanged; authoring history is not part of the D12 result.
Several sources may describe related Methods, their performance, support and development through structures that do not line up one-for-one—for example Method composition, Work order, model use, provider capability and cultural transmission. When those differences affect the framework architecture, use C.32.MWA to produce one readable synthesis for the E.4.PFAD answer; that synthesis does not choose whether to create a DPF or another result.
Use E.23.CDI only when the selected architecture includes developing capability for a named Work family, and use its result instead of copying its action sequence here.
When the DPF promises professional Method coverage, consume one exact accepted E.4.PFAD answer before treating a source list or pattern list as the authoring boundary. The five connected claim groups are a projection of that compact eight-part answer. E.4.DPF uses the projection without creating a second input record. Keep the accepted answer, its accepting decision, the E.9 DRR, the later framework edition, and any publication carrier distinct.
The five groups remain recoverable by value, filled only to the grain that changes the declared first use:
- Practice claims and first use: every bounded practice claim or promised contribution names its subject and scope, distinguishes existing practice from a proposal, and states what is supported, refuted or unresolved. Recover the practitioner, difficulty, sought result, first use, stop or wrong-turn return, qualification window, and receiving decision. Include only non-use boundaries admitted by
F.19’s grounded-contribution test. Qualify each claim separately. - Project and Method positions: direct project subjects, use and environment, materially different solution forms, and Methods under their actual operational, system-change, solution, Method-of-interest, or Method-development relations. Incumbent Work, development or trial Work, candidate-practice Work, and intended Work keep different identities and truth status.
- Selected structures and correspondences: only the Method, Work, subject, transformation-flow, capability/provider, description, contribution, Method-development, and cultural structures whose correspondence, conflict, or non-isomorphism changes the answer.
- Pressures and evidence: constraints, conflicts, failures, environment or interest changes, and observed, source-supported, estimated, contradicted, and missing links remain distinct from causal history and temporal unfolding.
- Contribution, subtraction, gaps, and reopen: what current FPF and admitted DPFs already supply, each receiving pattern and domain filling still needed, exact external results, what is omitted or missing, and the observation that reopens the architecture.
One accepted answer may carry supported incumbent-practice claims, unresolved or refuted claims about existing practice, and candidate-practice proposals. Every selected question and resulting authoring disposition points to the bounded claims it consumes.
Independently obtaining A.13 agency claims and actual incumbent, development or trial Work keep their status; they support candidate-practice coverage only through the required relation and evidence. Public coverage is asserted separately at the scope supported by the exact edition and its evaluation.
For an obtaining practice claim, name actual recurring difficulties and representative actual Work. When the claim relies on a precise Agent performer, recover the A.13 core: exact admitted System, local agential kind and criterion, classification, obtaining assignment, and needed scope, working situation, and window. Add an agency-characteristic profile only when a Grade, autonomy or profile claim, a criterion-dependent characteristic, or a named assurance use consumes it.
A.15.1 then independently admits actual Work from its performance history, Method, extent, and containment; only after admission does F.6 add any precise assignment-bound attribution through that same assignment. A missing F.6 relation leaves Work membership intact and the attribution unresolved. State the evidence limits.
For a proposed practice, recover intended use, any incumbent Work or Method and available problem evidence, candidate Methods and architecture, and realization conditions. Reuse construction, source, derivation or validation grounds that suffice for the claimed use. Where required support is missing, either obtain the needed domain result at justified cost or retain the exact unresolved claim; binding requirements still limit use.
Plan a representative trial only when it is required or its attainable contribution justifies the full burden, retaining acceptance, failure and reopen conditions. A supported prospective design can be published as such; actual candidate-practice Work, Agents and practice coverage require their own grounds.
Turn the accepted input into one bounded authoring disposition for every selected question. Name the receiving pattern, the exact bounded practice claim or claims consumed, and the domain Method, evidence, constraint, direct relation claim, obtaining case, or planned trial still needed; or return a seed, external result, gap, omission, or reopened architecture question.
If the PFAD answer omits a required group or claim-to-question binding at the grain needed by first use, return that bounded PFAD gap instead of inventing the value. One clear question stays with its subject pattern. Use C.32.MWA only when correspondences or conflicts among several selected structures change the answer, and use its completed result rather than copying its action sequence.
E.4.DPF.DA evaluates the resulting edition once. D1DomainScopeAndUseAdequacy preserves the reader, first use, stop or return, qualification window, truth boundary, and any locally warranted non-use boundary of every public practice contribution. D4CoreDependencyAndDomainBoundaryAdequacy tests FPF subtraction, domain filling, and exact external dependencies. D5PackageFormLayeringAndRelationAdequacy keeps answer, accepting decision, DRR, edition, package, publication, and carrier separate.
D7PracticeUtilityAndProblemResolutionAdequacy uses the recognizable difficulty, practical move, and receiving result for each bounded claim without upgrading observed, planned, or missing evidence. D8HeterogeneousCaseAndTransferAdequacy uses representative cases, demonstrations or justified trials appropriate to the claimed use and preserves their support and transfer boundaries. D11DomainSoTAAlignmentAdequacy uses current domain sources, pressure evidence, limits, and reopen triggers.
D12DomainProblemFamilyCoverageAdequacy alone integrates the exact edition’s several bounded public promises while retaining their different truth status; it cannot turn a prospective contribution into current practice coverage or erase an obtaining incumbent contribution.
The same case or source may support several coordinates, but each coordinate is judged once in the D1-D12 aggregate. Do not add a second project-Method architecture checklist, proof-of-revisit requirement, or second pass over the same evidence.
The input can be compact prose and a few selected structures. It is not a universal record schema, fixed view set, mandatory diagram count, source-chapter destination map, project lifecycle, or proof that a Method works or transfers. If no accepted answer identifies which practice questions change first use, or a required domain filling is missing, keep the affected contribution as a seed, gap, or omission and return to the exact E.4.PFAD or domain-source question. Do not infer Method parthood from a required contribution, transformation, Work enactment, capability, provider contribution, or cultural change merely because a source lists them together.
Keep the mapped objects distinct. A Method may be described by a MethodDescription, and a pattern may contain such a description only when A.3.2 applies. Selected patterns and their material relations make up the pattern language; a framework edition contains one version of that language; an independently identified physical or digital carrier may yield a particular publication or access-facing expression under E.24.PUB, with any reusable form constraining that expression separately; and an access route may help a reader or System reach the edition or a named carrier. Publication, availability, and actual access remain separate claims.
Semantic synthesis can support proposed claims and distinctions in the architecture. Methodological synthesis constructs the proposed ways of acting and their connections. Neither construction by itself establishes that a Method works or transfers.
Use product here only as 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.
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 exact episteme. Treat its Readme, architectural reference, ToC, pattern bodies, 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.
A registry, guide, evidence package, companion, catalogue, tool reference, access service, programme, or another direct subject may justify that boundary; the label does not settle the subject kind.
When the direct subject is independently used or changed, keep it separate and point from the framework to its exact edition or current state. 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.
When programme is used, start with what continues. If a subject pattern admits the programme as a System or another exact 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 remain 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.
A combined presentation carrier stays neutral. 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 exact constituents. Apply E.11.PFP only to FPF, DPF, or LPF constituents. An adjacent non-framework result uses the form and indexing discipline selected for its direct kind. DRRs, build manifests, quality runs, digests, logs, and campaign state remain process or maintainer evidence unless a selected reader use gives a direct subject its own product identity and publication or availability route.
When recurring domain wording prevents reliable use of the DPF patterns, apply the shared restoration method in E.10.ARCH and keep the domain entry beside the patterns that use it. Identify a separate local profile only when several entries have a named maintained use. A filled table can express the profile. Its reusable layout rules supply the publication form. A DPF with no demonstrated recurring wording problem needs neither.
Use E.4.DPF for the authoring route and its optional proposal or dependency branches, E.4.PFAD for framework-decision content, E.8 to author patterns, and E.4.PFR only when a named maintenance use needs a relation or edition record. Use E.11.PFP for the common framework publication form, E.24.PUB for publication occurrence, form, carrier, audience, bounded use, availability, and access, E.11 for practical entry, and E.17 for a source-backed publication face. Use E.4.DPF.DA and E.21 for package and pattern evaluation, E.23 for improvement, and G.11 for currentness. Each result or relation follows the predicate and evidence in its owning pattern.
If one receiving use needs reusable conditional unfolding, select one exact A.22.CGUS ConstraintGovernedUnfoldingStructure separately from this MethodDescription. Recover its A.22 identity, separately identified constituents and obtaining relations, applied constraints, more than one admissible continuation, and explicit stops or returns; keep any demonstrative walkthrough as a separate C.2.1 episteme. Otherwise keep the route Plain.
When separately admitted dated authoring Work first constitutes a framework episteme or a revised framework episteme, recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is also current. Recover the local inception claim separately through A.15.PROD.
C.2.1 identifies each authored framework episteme by its ClaimGraph, EntityOfConcern, and effective ReferenceScheme. An obtaining EpistemeEditionRelation, the authoring change or inception claim, the package architecture, and any EpistemePublicationRelation remain separately revisable. Publication occurrence, publication form, presentation carrier, framework truth, edition continuity, and package membership use their direct predicates and evidence.
The complete authoring account keeps the domain or local use frame, source basis, selected architecture, names, pattern drafts, direct assertions of material relations, publication or access, quality, improvement, and currentness returns recoverable. Keep any relation or edition records required by a named maintenance use recoverable too, without turning their order into another object.
When the selected architecture answer is to create or revise a DPF and authoring begins, keep claim-bearing epistemes, particular expressions, reusable publication forms, presentation carriers, and access routes separate.
Keep the accepted answer in a developer decision carrier written with the E.9 decision-record method and checked by E.9.DA. It carries the source basis, selected architecture answer guided by E.4.PFAD, initial pattern split and direct assertions of the material relations among those patterns, publication or access consequence, alternatives, rationale, consequences, first action, and reopen condition.
Publish the user-facing framework through a carrier named for the individual framework, as one assembled expression or as expressions of a split set of publication units. An exact access-facing artifact supplies the carrier only when its independently identified actual state or realization yields the selected expression; identify the service or route through which readers reach it separately.
Keep a source pack, E.4.PFR record, quality result, package evaluation, access manifest, or service description separate when its independent use and change require that boundary. C.2.1 framework-episteme identity, EpistemeEditionRelation, package architecture, E.24.PUB publication occurrence, expression, form, presentation carrier, access route, and actual access or use remain distinct; process state remains outside the user carrier.
A cheap route or stop remains outside this arrangement. Its result is the route or stop.
Plain vocabulary for adoption:
| Public phrase | Use it for |
|---|---|
principle framework | The general public phrase for an FPF-grounded framework of patterns, decisions, direct relation assertions, source basis, publication, quality, and refresh. Add relation or edition records only when a named maintenance use requires them. |
Domain Principle Framework | A principle framework for a domain such as greenhouse cucumbers, neural-network architecture, or safety certification practice. |
Local Practice Framework | A principle framework for one bounded local practice setting—for example an organization, project, team, workflow, tool, practitioner position, or audience. Recover ambiguous role wording through E.10.ROLE; add a local system-role kind, a separate System-classification judgment, or an exact assignment occurrence only when the framework claim independently uses it. |
domain or local use frame (bounded context in ordinary domain language) | The Plain description of where and for whom the framework meanings are intended to hold. Recover the effective ReferenceScheme, A.2.6 ClaimScope, intended reader/use, qualification window, and optional independently selected BoundedModelUseStructure separately when those distinctions are current; the word context supplies none of them by itself. |
framework edition | One exact authored framework episteme at a selected edition boundary, with any obtaining C.2.1 EpistemeEditionRelation, E.4.PFR dependency/compatibility records, publication uses, quality result, and refresh route kept separately recoverable. A version label or package path alone establishes no edition continuity. |
framework publication carrier | An independently identified physical or digital entity, such as a managed all-in-one Markdown file, PDF volume, site snapshot, or split-file bundle, whose actual state or realization yields one particular framework publication expression under E.24.PUB. The selected reusable form may constrain the arrangement of a Readme, architectural reference, table of contents, pattern-body collection, support maps, relation records, and refresh route as publication units; those units are not carriers by label. The carrier is not the framework episteme, edition relation, package architecture, publication occurrence, expression, or publication form. |
framework access-facing carrier | An independently identified physical or digital entity, such as a versioned skill-pack bundle, retrieval-index file, or response document, whose actual state or realization yields a particular access-facing expression. Any selected reusable form constrains that expression separately. Bearing establishes neither actual access nor framework authority, currentness, or Work. |
framework access route | An identified service, endpoint, retrieval or search route, or assistant integration through which a reader or System may reach the edition or a named carrier. Returning a carrier does not establish that the route bears the expression. |
local monolith | Workspace and editorial shorthand for one all-in-one framework publication carrier. Do not use it as the public framework name, and do not treat it as the framework architecture. |
The labels SPF, TPF and xPF, and the strings FoundationalPrinciplePatternSet and ZPF, remain source aliases until F.18 settles a durable public name and any admissible short form. Use the full descriptive phrase “foundational principle pattern set” when that subject must be described before naming is settled. If an alias suggests a different framework identity, open the F.18 naming question before public use.
Keep the authoring apparatus proportional to the next receiving use. A first exploration may stop with a cheap route or no-framework answer and no decision record when it settles no later-used framework boundary.
A compact reliance-bearing framework may keep its Readme, architectural reference, pattern bodies, relation rows, source-use account, and quality route in one carrier when the same readers and stewards maintain them together. Split source packs, decision records, relation records, pattern files, quality results, skills, or access services only when independent editioning, confidentiality, transfer, automation, delayed feedback, expensive reversal, or another named reliance makes their identity separately useful.
Create an organization proposal only when candidate organization claims need separate review; create an authoring-dependency description only when a named next use needs stable dependency availability and relevance. More files or records do not make the framework more mature.
Prompt-shaped starter for SoTA harvesting and first candidate generation:
Help draft a first FPF-grounded principle-framework candidate.
Domain or local situation and semantic boundary: effective ReferenceScheme, ClaimScope, qualification window, and optional selected BoundedModelUseStructure only when interpretation depends on it:
Intended reader and first use:
Independently grounded non-use boundary, only when the full F.19:4 test warrants it: a plausible intended reading, changed truth, understanding, or use, and the smallest clear correction:
Selected source basis and why it fits this question: direct source | maintained synthesis or guide | bounded F.1/F.0.2 route | existing G.2 pack | earlier DPF | derived lookup
Source traditions to inspect:
Rival traditions or schools not to lose:
Local examples or internal sources:
Earlier DPF pattern or claim reused, kept local, or proposed as an FPF improvement:
Derived-lookup coverage, authoritative return, and unresolved source needs:
Adopted source payload to carry into pattern solutions:
Rejected source payload and why rejected:
Recurring domain wording whose repeated misreading needs a local E.10.ARCH entry, if any:
Recurring domain or local problem situations and forces:
Reusable solution moves and consequences:
Candidate first patterns, each with problem frame, positive solution, worked slice, and local anti-pattern:
Field or practice promised by the public name, intended reader, first use, stop or wrong-turn return, qualification window, and any independently grounded non-use boundary:
Recurring problem families, characteristic failures, useful result families, selected problem-family pattern sets, material relations, and what the framework omits:
Representative application crossing the patterns and problem-family sets needed for first use:
Professional Method coverage, when it changes the answer: the practice questions selected by `E.4.PFAD`, the pattern used for each, the domain content needed, and whether `C.32.MWA` is required because several structures do not line up one-for-one:
Whether capability development for a named Work family makes `E.23.CDI` current:
Patterns included in the first edition and same-framework prerequisites needed for first use:
For a candidate framework, identify each external result it relies on and the content used. Say whether the result is that content or identifies it.
Give the result's direct kind, supplying product, edition or current state, receiving use, discovery route and material currentness or availability conditions. State that the result remains external to the framework.
For any separately required availability or compatibility result, identify that result, what must be available or which objects must be compatible for the receiving use, and the basis on which the result applies.
Which load-bearing claims are actual, proposed, or untested, and what must be realized or tested before stronger use:
Destination or source return for every contribution not selected into the framework edition or another named result:
Candidate relation functions among the patterns:
Current first result and selection condition: cheap route or stop with no DRR | one open architecture question answered by a new or revised framework, a contribution to an existing framework, a non-framework product, a thinner publication or access route, or no new maintained product now in an E.9 DRR | optional organization-design proposal | post-existence architecture-description use | optional authoring-dependency description
State a framework-edition dependency under `E.4.PFR:3.4` only when the dependent edition's current content or result for the named use requires the relied-on content: removing it or changing it in a way relevant to the use would invalidate the dependent content/result or require that use to be reopened. Identify the dependent edition, relied-on FPF or domain-framework edition, direction, reason and refresh condition, referring to the relied-on content identified above. For an optional authoring-dependency description, use `E.4.DPF:4.5`:
Publication form and exact presentation carrier for first use; access route if one is needed:
Quality route: which first drafts should be evaluated and improved:
Refresh triggers: source change, relied-on FPF or domain-framework edition change, material change to relied-on Core claims, local-use telemetry, or policy change:
Return the current result and only the adjacent source, naming, pattern-draft, relation, publication or access, quality, and currentness notes that its receiving use needs. If the result is a cheap route or stop, create no framework-decision record. If the requester wants a ready DPF rather than a seed, keep the E.9 DRR or decision carrier separate from the user DPF publication form, exact presentation carrier, and any access route, then name which `E.21`, `E.4.DPF.DA`, and currentness checks remain before reliance.
Do not present generated text as authoritative. Before relying on it, name the unresolved claims and the contribution still needed: direct source return; a relevance-based source cut through `F.1`; a bounded semantic-synthesis result through `F.0.2`; general construction, connection, explanation or change of Methods through `C.39`; their framework-authoring application through `E.4.CM`; an optional broad `G.2` pack; authoritative return and partial-failure handling for a derived lookup; identifying the generated or discovered result, establishing its kind and status, and determining admission for its intended architecture use through `C.35`; framework-decision profiling from `E.4.PFAD`; an optional relation or edition representation from `E.4.PFR`; local wording restoration through `E.10.ARCH`; naming from `F.18`; quality evaluation from `E.21`; or a currentness check from `G.11`.
-
Domain or local use-frame declaration. State the intended reader, first use, stop or wrong-turn return, effective ReferenceScheme, ClaimScope, qualification window, and any non-use boundary admitted by
F.19’s grounded-contribution test. Select a BoundedModelUseStructure only when its exact organization changes interpretation for this receiving use. Record each of these values through its direct pattern and predicate. -
Source basis and synthesis route. Select the applicable branch above. Use direct source reliance when one claim is enough;
F.1when source selection alone is current;F.0.2for one bounded comparison across source ontologies; andG.2only for the broadCG-Framepack and its downstream handoffs. Resolve derived lookups to authoritative editions, treat non-return as partial coverage, and classify earlier-DPF material as direct reuse, a receiving-DPF claim, or a proposed FPF improvement. Record adopted and rejected source payload, examples, currentness, and reopen conditions in the DPF source-use account. -
Cheap exit, optional proposal, or architecture answer. First test whether current FPF and sources close the immediate use through a cheaper route or stop without settling a later-used framework boundary. If so, stop without a DRR. Create the C.2.1 organization-design proposal described in 4.2–4.4 only when a named review use needs candidate organization claims.
When a later-used boundary makes the architecture question current, use
E.4.PFADto profile oneE.9DRR and select one of the five outcomes named in the first-hour route. If the answer selects a new or revised framework, state what field it promises to cover, its coverage map, representative application, first-edition set, external dependencies, omissions and returns, and which load-bearing claims are actual, proposed, or untested.Treat a one-pattern candidate as a strong warning and run the same framework-scale test used at every count. If the candidate lacks connected problem-family coverage, material pattern relations, a representative application, an internally usable first use, or a credible edition, change, and refresh boundary, keep it as a seed or contribution; the count itself does not decide. Keep the selected answer, acceptance, DRR, package architecture, direct relation assertions, any relation or edition records required by a named maintenance use, edition dependencies, authoring, and any ADR-like publication distinct.
-
Name and wording preparation. Use
E.10for kind discipline andF.18for durable names before public pattern heads or abbreviations stabilize. When a recurring domain wording failure blocks use, applyE.10.ARCHto write a local entry beside the affected DPF patterns. Create a separate profile only for a named maintained multi-entry use. A table can present its entries in a reusable layout. -
Architecture-use preparation. Before relying on all-in-one carriers, tables of contents, relation graphs, source summaries, search outputs, transformed views, or generated candidates as architecture evidence, apply
C.33to selected-structure recovery orC.34to structure-preservation comparison when that question is current. For an exact generated or discovered result intended to inform architecture work, useC.35to establish what kind of result it is, the organization concerned and the status of the actual or proposed claim, including any unresolved basis, next-use condition, and limit and return. -
Pattern drafting. Draft patterns with
E.8: recognition text, positive solution, worked cases, boundary, local anti-patterns, SoTA-Echoing, conformance checks, and relations. E.8 supplies authoring and publication-form rules; it does not make every pattern episteme aU.MethodDescription. Apply A.3.2 only when the episteme has one independently admitted Method as its EntityOfConcern and substantively describes how that Method is carried out.In a DPF, the pattern bodies render selected domain or local problem-situation architecture and solution-move architecture. When repeated first use benefits from an attentional aid, write a Plain local mantra by compressing that pattern’s Solution without dropping the distinction that makes the move work or the stop, return, or redirect condition. Keep an established local name such as
mnemonic,watchword, orheuristicwhen it explains the aid better.Use
A.22.CGUSonly when an independently selectedConstraintGovernedUnfoldingStructurehas exact constituents, obtaining relations, constraints, admissible continuations, and stops; keep its demonstration separate. A thin skeleton, prompt seed, compressed design note, or memorable slogan detached from the Solution remains a pattern seed until anE.21evaluation finds the pattern adequate for the declared DPF use. -
Relation and edition discipline. State each material relation directly with its defining predicate. Use
E.4.PFRfor a relation or edition record only when a named maintenance use needs that representation. When dependency, compatibility, migration, deprecation, or supersession is current, keep the corresponding record recoverable. -
Quality cycle. Use
E.22to frame the evaluation purpose, quality floor, trade-off question, and expected improvement proposal when that frame is not already scoped. UseE.4.DPF.DAto evaluate the package as a DPF or local-framework package,E.21to evaluate individual pattern quality,E.23for repeated improvement, andE.19for selected admission or refresh questions, including affected-use replay underE.19:4.3.3when the candidate changes materially.If an evaluation result needs a carrier, publish or refresh that carrier through the pattern that defines its publication or currentness relation rather than through
E.22. -
Admission review. Use
E.19when the local process asks whether a pattern or framework slice is ready for admission. -
Support-unit and adjacent-product boundary. Use product only as the Plain management umbrella defined in
E.4:4.1. Group framework publication units only when they share the framework edition, declared readers and use, edition boundary, access, and change rule.For every proposed adjacent result, name its direct subject and test independent use and change, identity or current state, an intensional rule for what belongs, access, any later-review or retirement rule that changes use, and cross-framework reliance. State maintenance separately when it obtains.
Keep ordinary framework material as a support publication unit; keep an independently useful subject separate and point to its exact edition or state. Treat shared use and a combined carrier only as boundary probes.
-
Framework publication-carrier assembly and access-route check. Expose the selected framework episteme edition through exact publication and access relations. An independently identified physical or digital artifact supplies a publication- or access-facing carrier when its actual state or realization yields the selected expression; identify the service or route through which readers reach it separately and name any returned carrier.
When a Markdown carrier bears a publication containing the full
E.8pattern bodies, useE.11.PFPfor the common reader-facing title and edition cue, one logical index, and one practical-entry set with five-field ordinary entries and six-field selected cards. Show authorship, date, dependency, language, access, or a product-declared maintenance status, support window, or currentness window in the opening only when a product-specific publication rule names the reader decision or action they change.Keep the FPF heading hierarchy in that publication: the framework title and major publication units or Parts are H1, each PatternID and pattern title is H2, each canonical
E.8section is H3, and each nested section is exactly one level deeper. Navigation may surround a body, but it must not demote the body or merge two source heading levels.Keep the publication functions recognizable: in English use
Table of Contentsfor finding,<framework name> Readmefor short practical entry, and<framework name> Architectural Referencefor the full account of the language underE.11.DSGandE.11.PFP:4.7; translate them consistently in another publication language. Keep the account’s declared section key separate from its displayed title. Do not create a parallelPattern Indexfor the same ToC function or rename the ReadmeReader Guide.Generated-source comments, source paths, source-set digests, machine identity blocks, build commands, and
do not editmarkers remain builder, package, manifest, or maintainer evidence rather than reader front matter. A compact card or summary remains entry guidance, while a distinct index remains a finding aid. Each returns to the ToC or Readme that locates its full pattern body, or directly to that body; do not present it as that body.After assembly and before calling the carrier released, current, or ready for its declared use, inspect the assembled carrier rather than only its sources: use the
E.11practical-use carry-through check for the public entries andE.4.DPF.DAfor package form, preservation of the published pattern bodies, and declared use. A successful build run shows that generation succeeded; it does not show that the published hierarchy, entry route, or pattern content survived. When the assembled publication claims accepted-source integration or continuity with its predecessor, useE.4.PFIPfor that comparison.Under E.24.PUB keep publication occurrence, selected episteme edition, audience declaration, bounded-use declaration, particular expression, any selected reusable publication form, and presentation carrier distinct; use the direct access pattern for actual access or use. Framework identity, package membership, truth, Work authority, and landing use their direct predicates and evidence. Domain or local frameworks publish through their own selected carriers.
-
Currentness route. Use
G.11for refresh plans, edition pins, source decay, deprecation, and supersession conditions.
Localize each repair before returning to wider framework architecture. A changed source payload first reopens the direct source use, F.1 source cut, F.0.2 comparison or G.2 pack used for that payload. Then reopen only the dependent assertions, examples or relations. A change to a relied-on FPF or domain-framework edition, or a material change to the Core claims used, first reopens the affected E.4.PFR dependency, compatibility, and migration relations.
Repeated misuse of one pattern first reopens that pattern’s E.21 result and its E.23 improvement loop; a repeated domain wording failure may also reopen its local E.10.ARCH entry. A failed publication or access route first requires E.11, E.17, or the carrier relation that exposed it. A local mantra that no longer preserves its pattern Solution requires comparison with the exact Solution in that pattern body; A.22.CGUS becomes current only if the repaired aid must present a wider conditional unfolding.
Use E.4.PFAD only when the evidence changes selected framework-family, pattern-split, relation-structure, publication-form, presentation-carrier or access-route architecture, or dependency-boundary decisions. Use G.11 when edition currentness, source decay, telemetry, deprecation, or supersession must be orchestrated across those local repairs.
For an all-in-one DPF publication carrier, assemble the content in a reproducible order. This order is a publication shape, not a new framework kind.
In an all-in-one Markdown publication that contains the full pattern bodies, the framework title and major publication units or Parts use H1, pattern bodies begin at H2, and their canonical sections begin at H3. The framework name and publication language may vary with the domain and readers; E.11.PFP’s reader-facing sequence, pattern-row profile, publication-unit jobs, and the heading hierarchy do not. In English label those functions Table of Contents, <framework name> Readme, and <framework name> Architectural Reference; use one consistent translation in another language:
-
Public framework title: use a domain- or practice-specific framework name such as
<DomainOrPractice> Principles Framework;Principles Frameworkalone is only the head or kind phrase, not an individual framework name. Do not putlocal monolith,draft, process status, or file-layout slang in the public title. -
Short public edition line directly under the title: name the stable public edition designation and a public edition-record locator. Add a dependency, language, access, product-declared maintenance status, support window, currentness window, or other short cue there only when the product-specific publication rule names the reader decision or action it changes. Do not create a separate edition H1 or put a machine identity block, source digest, source path, or build marker before the ToC; keep detailed edition and relation records after the pattern bodies or in maintainer evidence.
-
Table of contents: place one search-oriented overview before the body collection and use
E.11.PFP’s five-position pattern-row profile. Every pattern row exposes its PatternID and title and gives at least one recognizable working-question cue inKeywords & Search Queries. State the DPF’s declared reference code and local-locator form where a reader can disambiguate citations.Keep the displayed
§position separate from PatternID; the current row order may be non-ascending by PatternID but must match the body order. UseStatusandDependenciesfor values that can change the reader’s choice; do not copy first move, result, and boundary into additional mini-method columns. Pattern bodies remain the main language of use; support maps and any relation or edition records required by current maintenance remain reachable without becoming a universal first inspection sequence or prescribed use order. -
Framework Readme: for the intended reader, present recognizable first-entry situations and practical questions, the first useful result or blocker, the direct pattern or small plausible set, the ordinary stop or wrong-turn return, and any non-use boundary admitted by
F.19’s grounded-contribution test. State briefly which selected domain or local structures this carrier exposes. -
Framework Architectural Reference: the full public account required by
E.11.PFP:4.7andE.11.DSG, embedded here in the all-in-one carrier. Explain the whole’s purpose, constituent Methods and their connections, shared conditions, architectural reasons, source synthesis, serious alternatives, limits and worked use, including the structure families the carrier foregrounds, coarsens, defers or returns to sources and pattern bodies. Give this one account the qualified public title and theReferencesection key defined by E.11.PFP:4.7.1. A separate preface or independently managed account is not required, and readers can enter a known pattern directly. -
Package carrier structure-account: intended reader and use, selected source-structure denominator, recurring problem-situation structures, reusable solution-move structures, captured structure, deliberately coarsened, abstracted, omitted, or lost structure, source-return condition, and quality or epiplexity route. Integrate this explanation into the architectural reference, with a short Readme cue where it changes first entry; it does not require a second account.
-
Package boundary and subject-pattern routing: Core subject patterns reused, local terms bounded, and source, evidence, assurance, publication, and refresh exits named.
-
Pattern bodies: each drafted through
E.8, with its PatternID and title at H2, canonical sections at H3, and deeper sections retaining their relative levels; each carries recognition text, positive solution, worked cases, local anti-patterns, SoTA-Echoing, conformance checks, and relations, and each is evaluated or marked as a seed underE.21before the package is claimed for public, teaching, enterprise, or reliance-bearing use. -
Heterogeneous acceptance cases or transfer probes: examples that force the pattern set to work across unlike uses rather than only repeating the motivating case.
-
Support maps or appendices: detailed architecture-bridge, source-use, precision or package-name lookup material placed after pattern bodies unless a short first-entry trigger table is needed. Figures and tables needed to understand the architectural reference remain with that explanation.
-
Source use and refresh map: source rows with adopted payload, rejected or bounded readings, the conditions that reopen a direct source use, F.1 source cut, F.0.2 comparison, or optional G.2 pack, and the conditions under which source currentness or refresh must be reconsidered with
G.11. -
Conditional relation and edition records: add
E.4.PFRrows only when a named maintenance use needs a stable representation of dependency, specialization, publication, source reuse, evaluation, generated-carrier, teaching publication-carrier, ethics, deprecation, supersession, or edition effects. Otherwise keep the direct assertion. -
Refresh dependencies: which source-use, pattern-quality, package-adequacy, edition-dependency, or publication-carrier claim must be reopened when sources, relied-on framework editions or Core claims, local use, telemetry, or evaluation change.
Every DPF publication or access-facing carrier named here is independently identified under its domain identity rule and bears a particular expression; any selected reusable form constrains that expression separately; an access route may help a reader or System reach the edition or a named carrier, but the route alone establishes neither expression bearing nor availability or actual access.
In an all-in-one publication carrier, the Readme gives the short practical entry and the architectural reference gives the full explanatory account, sometimes using a narrative rendering of the domain. Their representation relation remains inspectable when they say what they are telling, for whom, which structures they foreground, which structures are deliberately coarsened, abstracted, omitted, or left to source return, and where a reader returns for fuller pattern, source, evidence, or relation detail.
The return can go beyond summarizing one text in another. Its source may be actual or possible holon structure, an architecture description, a view, a source pack, a model, a graph, or a pattern set. In architecture-mediated narrative-rendering use, read the return chain as narrative rendering borne by an exact presentation carrier -> architecture description or view -> architecture as selected structures under its exact use frame -> wider source structures. When no narrative rendering is present, read the first step as selected publication expression borne by an exact presentation carrier -> selected source structures.
If entry begins at an access route, name the first expression-bearing carrier or response reached and follow the same chain. Each step states selected structure, captured structure, coarsening, abstraction, omission, loss, and return conditions. An architecture description is often already a coarsened representation of selected real, expected, candidate, or actual structures, so the DPF carrier keeps that second-step loss visible. This does not make every DPF a literary narrative or every carrier a narrative.
When a sequential narrative rendering is load-bearing, use A.6.3.NAR; when the publication expression deliberately keeps only a narrower-use coarsened rendering, use A.6.3.CSC; for structure capture and loss, use C.33; for same-enough or preservation claims, use C.34; for practical-use publication and access, use E.11, E.17, and the direct publication or access pattern; for package adequacy, use E.4.DPF.DA.
Keep process and build state out of the carrier. DRR text about the current version’s development, handoff notes, ledger rows, review status, helper state, admission blockers, landing evidence, generated-source comments, source paths, source-set digests, and build instructions may shape or identify the package, but the publication carrier should contain only durable user-facing package content, source-use boundaries, relation records, quality routes, and refresh conditions.
A short source-use or relation record may appear in the user carrier when it helps readers and maintainers use the DPF; a DRR argument about the current version’s development, review transcript, quality proof, or build manifest does not.
Publish durable architectural reasons that help readers understand, select, combine, or adapt the Methods and profiles, with the necessary explanation and source return, under E.8:4.2.3; retain the dated decision and its evidence in the development record.
For access-facing carriers and routes, keep the same framework edition identity, direct relation assertions, and any relation or edition records required by current maintenance visible. An exact artifact supplies the carrier when its independently identified actual state or realization yields the selected access-facing expression. Distinguish a continuing file object, an immutable snapshot value and an individual copy under E.24.PUB’s carrier-domain rule; a service address does not settle their continuity. A service or other access route names any returned carrier separately.
When an implementation uses a skill pack, MCP service, endpoint, retrieval or search route, or assistant integration, classify it through those same predicates. If the route returns a generated or discovered result for architecture use, apply C.35 to that result; if it performs Work or triggers tools, use A.15 and the pattern that defines the local tool or Work relation; if it claims currentness, evidence, assurance, or decision authority, retain the direct rule and grounds for that claim.
Use G.11 for currentness, A.10 for an implicit or required-replayable source-to-use account, B.3 for a named assurance claim, and E.9 for a decision that needs its rationale record. Take the DPF architecture from the accepted architecture answer and the framework episteme. Use E.4.PFR only when a named maintenance use needs a stable relation representation.
Starter evaluation characteristics for a principle-framework improvement loop:
| Characteristic question | Subject pattern to use |
|---|---|
| Discoverability | Can the intended reader find the first useful entry and subject pattern? Use E.11, then evaluate the pattern or projection through the applicable evaluation pattern. |
| Source fidelity | Are adopted and rejected source payloads recoverable through the source route used and in the receiving solutions, boundaries, and examples? Return to that direct source use, F.1 selection, F.0.2 comparison, or G.2 pack. Use C.33 for a needed structure-recovery result and C.34 for a needed preservation comparison, then use the results in the affected pattern-quality judgement. |
| Ontology clarity | Are Core, domain, local, publication, source, decision, relation, quality, and refresh claims kept as different kinds? Use E.10, F.18, F.19, and the pattern that defines or constrains the claim. |
| Relation typedness | Are pattern-use, specialization, dependency, publication, preservation, quality, and source-use relations separated? Use E.4.PFR. |
| Compatibility impact | Can maintainers see which structures or claims break and which migrations become current when FPF, domain, or local editions, or the Core claims used, change? Use E.4.PFR, E.5.3, and G.11. |
| Refreshability | Are source decay, edition pins, local-use telemetry, and supersession conditions actionable? Use G.11. |
| Package navigability | Can the selected pattern set, direct relation assertions, any current relation or edition records, source packs, decision records, quality evidence, and practical-use publication or access-facing carrier and any access route be found without treating the package as runtime machinery? Use E.11 to repair discovery of already adequate contents. Use E.4.PFR when the missing contribution is a relation or edition account, and G.5 only when the use needs a registry, dispatch or selected-set result; return that result to the package use. |
| Adoption telemetry | Are repeated reader errors, skipped records, stale sources, and local-use failures made an explicit refresh or improvement trigger? Use G.11 and E.23. |
| Didactic first use | Can a first-time domain or local author write the first useful output without prior FPF developer knowledge? Use E.11, E.12, E.21, and E.23. |
These are evaluation characteristics for selecting and framing improvement Work. They are not measurement programs by themselves. If the pass needs a DPF package adequacy result, use the predicate defined in E.4.DPF.DA; if it needs individual pattern quality, use E.21. For DRR adequacy, FPF-level Pillar adequacy, measurement, or architecture-characteristic evaluation, state the exact subject assertion under E.9.DA, E.2.DA, C.16, or the relevant architecture-characteristic pattern.
For evidence use, retain the relied-on claim, its independently established sources and support relations, and the conditions of bounded reliance. Use A.10 when that source-to-use account remains implicit or must remain replayable; assess currentness when it can change the use. Keep each local result under the pattern that defines or tests it.
This episteme’s A.3.2 MethodDescription use and its result-and-use account are sufficient only when a reader can answer all eight questions.
- Which framework episteme edition is being authored?
- What problem-and-solution architecture does it render?
- Which sources and decisions shaped it?
- Which patterns and material direct relations were selected?
- Which relation or edition records does a current maintenance use require?
- Which publication occurrence, form, carrier or access relation exposes it?
- How does its quality improve?
- When does it return for refresh or repair?
If the account also claims dated Work or a result relation, identify that claim through its direct pattern; E.4.DPF requires neither claim merely to describe the authoring Method.
E.4.DPF:4.0.1 - Author a Suite from its composite discipline
A DPF Suite is a larger DPF describing a composite discipline. Use the accepted E.4:4.2 and E.4.PFAD answer and C.20 to determine the constituent subdisciplines and their frameworks. Recover what those disciplines explain and make possible, and what must be understood or constructed at the encompassing scale. Develop the field account required by :4.0 for that composite subject. Explain the consequential relations among the constituents’ knowledge and practices, including any shared distinctions, objects, operations or conditions that their separate accounts do not determine on their own.
Obtain the needed joint construction and return it to the constituents. Show how a changed whole-level condition changes the selection, interpretation or combination of their contributions, and how a constituent result can revise the encompassing explanation. Retain the constituent DPFs’ own problem families, grounds, sources, cases, limits and assurance. Explain where one constituent can be used directly and where the composite work needs more; not every application requires every constituent.
Supply separately selectable missing Methods as complete E.8 patterns in their appropriate framework. The Suite account makes the composition understandable; its publication or a list of dependencies does not create that composition.
Return a proposed change of field boundary, part relation or architecture to E.4.PFAD. Reuse, a common audience and a guide entry do not by themselves justify moving a whole DPF into the Suite. General transdisciplinary Methods may belong in Core; an independent supplier remains a direct dependency or use. A specialized contribution keeps the conditions that distinguish its field. Reconsider existing allocations when new synthesis changes these distinctions.
The Suite edition identifies the constituent editions it describes and assembles. State what coverage is incomplete and which contributions are unavailable. Keep one unambiguous current home for each full Method; replace maintained links when that home changes. For a dependency or compatibility claim, name the editions, relied-on contribution, receiving use, conditions and reopen fact under E.4.PFR. Publication, availability, framework-series continuity and maintenance do not establish disciplinary parthood.
E.4.DPF:4.0.2 - Select practical examples for the product
Before shaping a DPF or LPF Readme, distinguish three jobs. A compact locator points to a direct pattern when retrieval is enough. An ordinary practical entry shows how one direct pattern or one bounded direct route can answer a comparatively simple difficulty without a mantra. A Practical-Use Card is selected only for a recurring complex difficulty when a repeatable formula materially helps the reader retain a useful path through several direct pattern contributions, checks, and returns.
Apply the E.11 comparison to the same truthful content with and without a mantra. If the reader can choose, obtain the first result or blocker, and return just as reliably without it, keep the locator or ordinary entry. Do not infer card form from pattern count, heading depth, phrase length, an inherited label, or a desired quota. Do not avoid the comparison by calling a rich cross-pattern example ordinary.
Keep one declaration for the product. It assigns every selectable example key exactly one ordinary-entry or card form. When the product selects cards, the declaration gives one measurable reading-burden rule plus mantra and compact-card maxima. Authors, builders, and validators use that same declaration and the shared visible grammar from E.11.PFP. A product may select no cards when locators, ordinary entries, or direct guide answers already support reliable choice and return; it then carries no card-form burden.
Use examples selected for that product’s readers and recurring questions. Return unmatched questions to the product’s index, guide, search, or direct patterns. Use F.19:4.4 to decide whether the reader also needs an explicit correction of a catalogue or coverage-boundary reading. When both simple direct use and extended cross-pattern use matter to adoption, show representative examples of both without turning every useful topic or pattern set into an entry.
Do not copy the FPF key inventory, card count, whitespace-token limits, or optional @FPFReadme records, and do not create a rival local card grammar or second key registry.
Keep a pattern-local mantra used to recall one pattern’s Solution, a Readme card mantra used to retain a longer cross-pattern path, and an independently admitted CGUS demonstration distinct. Claims about a Method, performed Work, project result, or stronger relation use their direct patterns and evidence.
E.4.DPF:4.0.3 - Keep pattern addresses stable while publication order changes
Before public references accumulate, declare a short, stable code for the DPF and assign one local locator to each pattern. Together the DPF code and local locator form the PatternID. Within that DPF, each PatternID is unique. The code is only a short reference to that named DPF; it need not be globally unique and does not identify an edition. Settle a new durable public abbreviation through F.18.
If the public DPF code later changes while the same DPF continues, preserve old references through an explicit F.13/F.18 rename or alias relation and a reader return; otherwise say where old-code use stops. Do not silently rewrite old citations. Do not assign the old code to another framework where readers may encounter both sets of citations without the full framework name.
A PatternID lets readers refer to a pattern carried forward across editions. The identifier does not prove that two bodies are the same pattern and does not define the pattern’s claims. Keep it while the recurring problem, distinguishing working move, useful result, and ordinary conditions for use, stopping, or returning still describe the same practical answer. A title, wording, Part, publication position, or authoring work package may change while that answer continues.
A PlannedCatalogEntry may reserve an unused locator, but it is not yet an addressable PatternRef or evidence that a continuing pattern exists. When a complete pattern is admitted and published, its author may adopt that locator as the pattern’s PatternID. The publication may use it as a PatternRef only after the complete body exists and the continuity judgment has been made; the reservation alone establishes neither identity nor addressability.
When the practical answer no longer continues, decide the split, merge, replacement, or retirement explicitly. Keep an earlier PatternID only for the answer that continues. Give each new pattern a new unused PatternID, and never reuse a retired PatternID for unrelated content.
If readers still use an old public reference, publish one maintained migration assertion. It names the earlier PatternID, any current PatternID or PatternIDs, whether the practical answer continued, split, merged, was replaced, or was retired, the uses covered, and where readers continue or stop. Add a structured E.4.PFR row only when a named maintenance use needs it; otherwise the readable assertion is enough. If no migration assertion is maintained, say where use must stop.
The local locator may use the numeric or mnemonic segments allowed by E.8. Prefer a numeric locator when it mainly needs to remain a durable address among many peers. Use a mnemonic segment only when it names an enduring distinction likely to outlast the title and publication position and materially helps recognition. A mnemonic is an address aid, not a compressed definition. Do not restyle established PatternIDs merely to make the set look uniform.
Keep current publication order separate. The ToC and body collection use the same Parts and the same within-Part order, while a § or position field shows that order separately from PatternID. Non-ascending PatternIDs are valid. State dependencies, Method relations, use order, and replacement relations in their own claims; do not infer them from identifiers, adjacency, Parts, or authoring work packages.
To refer to a pattern, retain its complete PatternID and enough context to identify the DPF. The full address may already identify that framework within the selected publication set; add a framework name only when needed. A citation intended to select the body published in one edition also names that framework edition.
For a reference that must travel beyond its present context, apply E.8 H-10 and E.11.PFP:4.2: preserve the complete PatternID or SectionRef and restore any identifying context that will be lost. Declaring the existing DPF code as a document qualifier does not change its PatternIDs or make that code globally unique.
E.4.DPF:4.1 - Select the current first result
Select the result whose condition is true now:
- Cheap route or stop. Existing FPF or source material closes the immediate use and no later author or reviewer needs a settled edition, dependency, initial pattern-placement or relation, or publication/access boundary. Use the route or stop without
E.4.PFADor anE.9DRR. - Framework-architecture answer. A choice among the five outcomes in steps 8–9 must settle a later-used boundary. Use the
E.4.PFADprofile and record the selected answer, including relations among initial patterns that change the architecture, in oneE.9DRR. PFAD supplies no separate result or relation. - Organization-design proposal. Candidate organization claims need their own review before an architecture answer is selected. Use the C.2.1 proposal episteme locally called
FrameworkOrganizationDesignProposal. The proposal is optional and is not a prerequisite for the architecture question. - Architecture-description use. The framework entity, architecture relation, and selected structures already exist, and the immediate question is how an architecture description may be used. Use
C.30.AD; itsArchitectureDescriptionUseCard@Projectname is retrieval-only. When project locality depends on a composite projectU.Work, identify that Work underA.15.6, recover every precise performer’s A.13 core, and use A.15.1 for independent Work admission. Add F.6 only when precise assignment-bound attribution is also current. Keep the description-use relation separate. - Authoring-dependency description. A named next authoring use needs a stable account of dependency availability and relevance. Use the C.2.1 episteme locally called
FrameworkAuthoringDependencyDescription. It may cite the accepted answer and itsE.9DRR when that basis matters, but it is neither a prerequisite nor an automatic result of the architecture answer.
The condition, predicate, and receiving use of each result determine when it exists. The five results are alternatives rather than stages.
E.4.DPF:4.2 - Make the intended result reviewable when a separate organization proposal is needed
First make the design target present. IntendedFrameworkResultDescription is an ordinary local use name for one exact current C.2.1 U.Episteme, not a root kind or card kind. C.2.1 identifies it by:
<exact intended-result ClaimGraph,
current DPF-authoring U.WorkPlan as EntityOfConcern,
effective ReferenceScheme>
The current A.15.2 WorkPlan declares coordination claims for possible future DPF-authoring Work, the intended framework-result kind, and its acceptance target. The WorkPlan exists now. A dated occurrence of the authoring Work and the framework result may still lie in the future.
The intended-result ClaimGraph states the domain or local use frame, readers, first uses, purpose, declared relation-family coverage constraints, intended-result constraints, and acceptance conditions. The effective ReferenceScheme interprets those claims. One exact A.2.6 ClaimScope separately bounds which claims and uses are current; changing scope does not substitute for changing the C.2.1 identity triple.
Keep use qualification and empirical grounding in their defined neighboring relations. If interpretation for the receiving use depends on an independently selected BoundedModelUseStructure, cite that A.1.1 and A.22 structure as an optional neighboring use qualification; effective ReferenceScheme and ClaimScope retain their positions in the account.
If empirical grounding is current, state a separate C.2.1 EpistemeEmpiricalGroundingRelation to one A.1-admitted holon and the covered claim subgraph. The grounding relation, its evidence, the WorkPlan, any separately claimed dated authoring Work, any separately claimed composite project Work, and the description episteme remain distinct. Each precise performer has an A.13 core; Work claims use independent A.15.1 admission, A.15.6 when composite, and F.6 only for current precise assignment-bound attribution.
Each declared relation-family coverage constraint is one FrameworkOrganizationCandidateClaimNode with claimNodeKind=constraint. Its coveredRelationFamilyRefKindPairs[1..*] identifies each covered relation-family value together with its exact kind; admittedFrameworkUseDescriptionRef names the use for which that coverage matters; and coverageCriterionDescriptionRef states how satisfaction of this coverage constraint is judged. A current A.15.2 WorkPlan acceptance target remains a different position: cite it through designBasisRefs[] or its direct acceptance-target relation. It neither replaces the coverage criterion nor shares one union field with it.
E.4.DPF:4.3 - Create one C.2.1 proposal episteme
The organization proposal uses the present intended-result description as its one EntityOfConcern:
FrameworkOrganizationDesignProposal:
C2_1Identity:
entityOfConcernRef: U.EpistemeRef
= current IntendedFrameworkResultDescription episteme
claimGraph: NonemptyClaimContent
effectiveReferenceScheme: EpistemeInterpretationScheme
claimScopeRef: ClaimScopeRef defined by A.2.6
intendedReaderDescriptionRef: U.EpistemeRef
intendedFirstUseDescriptionRef: U.EpistemeRef
modelUseStructureRef?: SelectedStructureReference
only when one selected BoundedModelUseStructure changes interpretation for this use
empiricalGroundingRelationRefs?: FinSet(U.RelationRef)
only for separately obtaining C.2.1 empirical-grounding relations
FrameworkOrganizationDesignProposal is a local use label for that C.2.1 episteme, not a second U-kind. Its one EntityOfConcern, one constituting ClaimGraph, and one effective ReferenceScheme supply episteme identity. ClaimScope, reader and use descriptions, optional model-use structure, empirical-grounding relations, A.7 provenance, F.15 proposal-status assertions when current, publication, and edition continuity are neighboring claims or relations; none is another identity slot.
A changed ClaimGraph, EntityOfConcern, or effective scheme identifies another episteme. A changed grounding relation alone changes that relation, not the proposal identity.
The proposal and dependency-description schemas use the C.2.1:4.1.2 ranges for their complete interpreted claim content and operative interpretation rules. Their narrower content requirements remain those stated in this section and :4.5. A graph encoding expresses those claims through a recoverable correspondence; graph shape or a nonempty file does not satisfy the content range. A partial scheme can satisfy its range while leaving a proposed relation, modal status or dependency condition uninterpreted; resolve that gap before the dependent use.
Use F.9 for an exact cross-context local-sense translation with its own endpoints and predicate. Candidate organization claims are expressed by the local node form below, with logical, alternative, refinement, dependency, support, conflict, and answer-to-question relations as current. The claims and their semantic relations constitute the proposal’s ClaimGraph; its encoding has separate node and edge identities.
Each candidate organization claim node makes the subject-level proposal recoverable:
FrameworkOrganizationCandidateClaimNode:
claimNodeKey: semantic key unique within claimGraph
claimNodeKind: FrameworkOrganizationClaimNodeKindValue
claimStatus: FrameworkOrganizationClaimStatusValue
intendedResultAspect: FrameworkOrganizationAspectValue
describedPositionKinds[1..*]: U.Kind
proposedSubjectRelationSignatures[0..*]: RelationSignature
proposedConstraintDescriptionRefs[0..*]: U.EpistemeRef
coveredRelationFamilyRefKindPairs[0..*]: FrameworkRelationFamilyRefKindPair; cardinality [1..*] for a relation-family coverage constraint node
admittedFrameworkUseDescriptionRef?: U.EpistemeRef; exactly one for a relation-family coverage constraint node
coverageCriterionDescriptionRef?: U.EpistemeRef; exactly one for a relation-family coverage constraint node
proposedInvariantDescriptionRefs[0..*]: U.EpistemeRef
proposedDependencyDirectionDescriptionRefs[0..*]: U.EpistemeRef
alternativeGroupKey?: semantic key unique within claimGraph
designBasisRefs[1..*]: U.EpistemeRef
designQuestionRefs[1..*]: U.EpistemeRef
frameworkArchitectureSettlementConditionRef?: U.EpistemeRef
FrameworkRelationFamilyRefKindPair:
relationFamilyRef: U.EntityRef
relationFamilyKindRef: U.KindRef
FrameworkOrganizationCandidateClaimNode is a local ClaimGraph node form, not a U-kind and not an episteme. FrameworkOrganizationClaimNodeKindValue is the local C.2.1-compatible enumeration definition | constraint | property | assumption. A node with claimNodeKind=constraint classifies a proposed constraint claim; its proposedConstraintDescriptionRefs[] identify the exact constraint descriptions that the node asserts, while a non-constraint node may cite those refs only when they qualify that definition, property, or assumption.
A relation-family coverage constraint node also has non-empty coveredRelationFamilyRefKindPairs[], one admittedFrameworkUseDescriptionRef, and one coverageCriterionDescriptionRef; other claim nodes leave all three coverage positions absent. Each pair identifies one relation-family value and its exact kind without a union field or untyped companion list. A WorkPlan acceptance target, when current, is cited separately through designBasisRefs[] or its direct acceptance-target relation. Both constraint positions describe the proposed organization.
If an obligation, recommendation-as-duty, or prohibition is current, use A.2.8 -> U.Commitment with its actual duty bearer, direct predicate, modality, referents, scope, validity, and instituting basis. A system-role kind or assignment may be an applicability ground; the commitment names the duty bearer.
If a permission, exercise, non-violation, or permission-conflict claim is current, use the exact A.2.8.PER result with the participants, references, constructive ground, and qualifiers required by that selected object.
FrameworkOrganizationClaimStatusValue is the local enumeration candidateProposed | rejectedAlternative | unresolved. FrameworkOrganizationAspectValue is the local enumeration frameworkFamily | component | dependency | patternRelation | publication | access; a domain extension adds another value only together with its exact interpretation rule in the proposal’s effective ReferenceScheme.
Proposedness is claim modality: it says that a relation signature, position, constraint, invariant, or dependency direction is being proposed for the intended result. Actual relation occurrences and actual U.Structure values use their direct admission predicates; a pattern-use boundary condition remains a separate position.
The proposal’s effective ReferenceScheme maps each organization-aspect value, described position kind, and proposed relation signature to claims about the intended result described by the EntityOfConcern; distinguishes ClaimGraph edges from the subject relations those claims propose; declares how basis and design-question refs qualify each claim; and states that claim status is modal rather than actual.
For example, a claim node can propose that one pattern family depends on Core, that publication and access remain separate positions, or that one relation invariant is preserved, without asserting that the future framework or those relations already exist.
E.4.DPF:4.4 - Preserve proposal, answer, structure, and architecture boundaries
Keep the two result positions separate. If reliance-bearing E.11.PUA support materializes an exact expected-result support object for this E.4.DPF application, its expected result kind is the C.2.1 proposal episteme locally called FrameworkOrganizationDesignProposal. The intended later framework edition is described inside the separate IntendedFrameworkResultDescription and the proposal’s ClaimGraph. One expectation support object never denotes both results, and neither object says the result was produced without the exact current work/result or inception claim.
Return to a framework-architecture question is separate from claim modality. When a reliance-bearing use needs an addressable return condition, E.11.PUA boundary support may name E.4.PFAD as the pattern for the next question and state which candidate claim, alternative, unresolved position, constraint, or dependency makes the downstream-used architecture boundary current. That support is adjacent to use of the proposal; it is not a proposal component and creates no PFAD result.
Subject organization is recovered from the candidate claim nodes, proposed subject relation signatures, described position kinds, constraints, invariants, dependency directions, alternatives, basis, questions, and framework-architecture settlement conditions. An A.22 U.Structure over the proposal ClaimGraph is optional and admissible only when the organization of the proposal episteme itself is a separate current EntityOfConcern. A selected BoundedModelUseStructure is a separate optional use qualification, admitted only when that exact organization changes interpretation for the receiving claim.
Proposal admission depends on the proposal identity and required claim content; the optional structures describe the proposal or qualify its use. The proposal is reviewable when it contains candidate organization claims and proposed subject relation content; headings, topics, and ClaimGraph organization arrange that content.
Before realization, C.33 notes compare proposal content with a declared current comparator: design questions, present basis epistemes, candidate alternatives, a relation-family coverage constraint claim node for an admitted framework use, or an earlier existing framework edition. When coverage is the comparator, C.33 cites the exact candidate claim node and reads its covered family ref-kind pairs, admitted use, and coverage criterion. A separate WorkPlan acceptance target may appear in designBasisRefs[] or through its direct relation; the coverage criterion remains the comparator for the coverage claim.
The notes may report represented, omitted, hidden, or unresolved candidate organization content relative to that basis. Comparison with actual framework structures starts after the framework entity and relevant structures exist.
Architecture-description and viewpoint use begins after the framework entity and relevant architecture relations exist. Later E.9 answers guided by E.4.PFAD, plus any C.32, C.30, and C.30.AD results, use their direct patterns and admission conditions; the proposal, intended-result description, and optional meta-structure keep their original types.
C.30.AD’s ArchitectureDescriptionUseCard@Project remains a retrieval cue. Actual project locality additionally requires one composite project U.Work under A.15.6 when such Work is claimed. Recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is also current, and keep its description-use relation separate.
E.4.DPF:4.5 - Describe authoring dependencies when a named next use needs them
The dependency description is optional, minimal, and status-bearing. It records current dependency positions while later authoring results retain their actual status:
FrameworkAuthoringDependencyDescription:
C2_1Identity:
entityOfConcernRef: U.EpistemeRef
= current DPF-authoring U.WorkPlan
claimGraph: NonemptyClaimContent
= dependency-position claims and their availability, relevance, value,
subject-pattern, acquisition-condition, and next-use-boundary claims
effectiveReferenceScheme: EpistemeInterpretationScheme
= interpretation of those claims for the declared next authoring use
claimScopeRef: ClaimScopeRef defined by A.2.6
intendedReaderDescriptionRef: U.EpistemeRef
intendedFirstUseDescriptionRef: U.EpistemeRef
dependencyPositions[2..*]: FrameworkAuthoringDependencyPosition
nextAuthoringUseBoundaryDescriptionRef: U.EpistemeRef
modelUseStructureRef?: SelectedStructureReference
only when one selected BoundedModelUseStructure changes interpretation for this use
empiricalGroundingRelationRefs?: FinSet(U.RelationRef)
only for separately obtaining C.2.1 empirical-grounding relations
FrameworkAuthoringDependencyPosition:
dependencyPositionKey: semantic key unique within claimGraph
dependencyKind: FrameworkAuthoringDependencyKindValue
dependencyAvailability: FrameworkAuthoringDependencyAvailabilityValue
dependencyUseRelevance: FrameworkAuthoringDependencyUseRelevanceValue
dependencyValueRef?: U.EntityRef
dependencyValueKindRef?: U.KindRef
dependencyPatternLocator: PatternID, a non-semantic locator for the pattern whose content defines, constrains, or tests this dependency
dependencyAcquisitionConditionDescriptionRef?: U.EpistemeRef
FrameworkAuthoringDependencyDescription is a local use label for one C.2.1 episteme, and each FrameworkAuthoringDependencyPosition is a local ClaimGraph node form. Only the enclosing description is the episteme; each position is part of its ClaimGraph. The current authoring WorkPlan, one ClaimGraph, and effective ReferenceScheme supply the description’s identity. ClaimScope, reader and use descriptions, optional model-use structure, empirical grounding, provenance, assessment status, publication, and edition continuity remain separate.
dependencyPatternLocator is an ordinary non-semantic PatternID that identifies the pattern whose content defines, constrains, or tests the dependency. A dependency that is also a MethodDescription identifies its episteme and the admitted Method it describes separately and applies the full A.3.2 test.
FrameworkAuthoringDependencyKindValue is fpfEdition | sourceBasis | frameworkArchitectureAnswer | nameRoute | patternDraftSet | relationAndEditionRecords | publicationOrAccess | packageQuality | improvement | currentness. FrameworkAuthoringDependencyAvailabilityValue is available | missing. FrameworkAuthoringDependencyUseRelevanceValue is currentForNextAuthoringUse | retainedForLaterUse | relevanceUnsettled.
The minimum positions are one fpfEdition and one sourceBasis. For an available fpfEdition position, dependencyValueRef identifies the selected FPF edition; the next-use boundary names the Core claims required for the declared authoring use. A change to that edition or a material change to those claims reopens the affected use.
Add another dependency kind only when the declared next authoring use relies on it or deliberately retains it for a named later use. A frameworkArchitectureAnswer position is optional: include it only when that use needs the accepted answer or its rationale, and point to the accepted answer and E.9 DRR rather than to a PFAD relation or record.
When dependencyAvailability=available, the exact dependency value and kind refs are present and the acquisition-condition description is absent. When dependencyAvailability=missing, those refs are absent and the acquisition-condition description is present.
Relevance remains independent: missing + currentForNextAuthoringUse blocks the next use and opens the stated return, while missing + retainedForLaterUse does not block current work. Record a condition on using an available dependency in the pattern that defines the dependency or in the next-use boundary, not in the acquisition position.
As authoring proceeds, a dependency description may refer to an accepted framework-architecture answer and its E.9 DRR; E.4.PFR relation records and edition dependencies; G.2 source packs; subject-home NameCards; E.8 pattern drafts; E.24.PUB, E.11, or E.17 publication and access uses; E.4.DPF.DA evaluation results; E.23 improvement results; and G.11 currentness relations.
Identify each dependency value, relation occurrence, evaluation result, edition relation, and receiving use separately, and apply the pattern that defines or constrains that object or use. The framework edition, package architecture, publication occurrence, publication form, carrier, dated authoring Work, and each dependency value retain their direct identities.
E.4.DPF:5 - Archetypal Grounding
A hydroponic-cucumber framework begins with crop-production concerns, horticulture and greenhouse-control sources, local examples, and a dependency on a selected FPF edition for named Core claims used in its explanations and revision guidance. Its first all-in-one publication carrier is for domain users, while relation records, source packs, and quality evaluations remain separately recoverable.
A neural-network architecture framework may draw on dataflow architecture, model components, training and inference concerns, evaluation practice, and recent architecture-analysis work. The framework can describe layers, blocks, flows, optimization constraints, and interpretability concerns. For each resulting pattern, choose the smallest source route that preserves the relied claims and limits; use G.2 only when the framework needs a broad, refreshable SoTA pack and downstream Part G handoffs. Draft the pattern with E.8, and record material relations with E.4.PFR when a named use needs them.
A workspace-specific Codex process framework can contain prelanding and baton-handoff patterns. It should state its local context, the selected FPF edition and the Core claims required for its named process uses, process sources, local carriers, and refresh route. A useful local checklist keeps that status until it has source grounding, pattern bodies, direct assertions of material relations, and quality evaluation. Add a relation or edition record only when a named maintenance use needs it.
An enterprise local practice framework for architecture review starts from the organization’s review setting, internal policies, proprietary examples, and approval path. It can depend on a selected FPF edition for required Core claims and on a domain-framework edition for its required content, but its confidential evidence, any local records about exact system-role classifications or assignment occurrences, training plan, and rollout telemetry stay local. Access, custody, maintenance, responsibility, authority, and approval remain separate direct claims.
Enterprise local-practice slice:
| Output | Enterprise question |
|---|---|
| Local setting | Which organization, product line, team, practitioner or audience position, and decision class are in scope? When a claim depends on a local system-role kind, classification, assignment occurrence, or another direct relation, state that claim separately through E.10.ROLE and its direct pattern. |
| Internal sources | Which policies, standards, review records, incidents, templates, and examples are adopted or rejected? |
| Constraints | Which regulatory, confidentiality, intellectual-property, tool-access, and security boundaries constrain publication? |
| Stewardship and maintenance | Which Systems perform any framework-authoring, source-pack maintenance, relation-record maintenance, publication or access, or refresh occurrence that this account claims as U.Work? For each such claim, recover every precise performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 only when this account also needs precise assignment-bound attribution. Which separate local system-role classification, maintenance, responsibility, authority, access, or source-custody relation obtains, and which direct-rule result or applicable A.6.RCD blocker applies when a required relation cannot be established? |
| Approval route | Which management, engineering, safety, legal, or assurance reviews are needed before local use? |
| Rollout and training | Which intended practitioners or audience groups need first-use examples, training material, or migration support? Identify any separately claimed training Work, system-role classification, assignment, responsibility, or authority through its direct pattern. |
| Dependency | Which FPF and domain-framework editions does this framework depend on? For each dependency, name the content relied on, direction, receiving use, material availability or compatibility condition, and reopen fact. Identify the required Core claims within the selected FPF edition. |
| Migration | What changes after a relied-on FPF or domain-framework edition changes, a relied-on Core claim changes materially, a policy changes, or local misuse recurs? |
| Adoption telemetry | Which reader errors, skipped relation records, stale source packs, or quality regressions trigger G.11 refresh? |
Replayable authoring slice:
| Authoring output | Filled slice |
|---|---|
| Domain or local use-frame declaration | GreenhouseCropDomain; effective scheme and ClaimScope named; intended reader: crop-system architect and senior grower; first use: decide the first pattern set for cucumber-production guidance; stop or wrong-turn return and qualification window explicit |
| Selected source basis and synthesis route | G.2 pack selected because the four-pattern framework needs a broad, refreshable source basis: greenhouse climate-control sources, crop nutrition sources, and local production logs; rejected source: generic gardening advice without controlled-environment evidence |
| Architecture answer | One E.9 DRR guided by E.4.PFAD records the field promised by the public name, the connected problem families and selected problem-family pattern sets, four candidate first patterns and their material relations, one representative application, the omissions and their source returns, and the one-way dependency on FPF@C1 for the two claims and uses named in the relation-and-edition row below; no PFAD relation or mandatory PFR row is created. |
| Framework-scale boundary | The four patterns count as a candidate first-edition language only if their coverage map, material relations, representative application, and edition, change, and refresh boundary make a new DPF edition more useful than contributing them to an existing framework, using FPF and the sources directly, publishing a guide, or adding no new maintained product now. One useful pattern would trigger the same test and would usually remain a seed or contribution. |
| Several-structure synthesis | Greenhouse Work, control Methods, crop and equipment subjects, descriptions and models, provider capabilities, and production-practice change do not line up one-for-one. C.32.MWA therefore supplies one architecture synthesis for those Methods and their use without choosing whether to create a DPF or another result. E.23.CDI is used only if the selected architecture includes capability development for a named Work family. |
| First-use closure | Every selected Hydroponic Cucumber pattern and same-framework prerequisite needed for the grower’s first use is included. The selected FPF edition and relied-on Core content remain external and are named with their use, direction, reason, refresh condition, and any required availability or compatibility result. A missing required result blocks first use. |
| Contribution destinations and claim strength | Each adopted or rejected source contribution has one stated outcome: it enters a DPF pattern, returns to an existing FPF or DPF, stays in a maintained guide or source result, is used directly from its source, or is deliberately not maintained together with an observation that would reopen the choice. Semantic synthesis can support a proposed architecture claim; methodological synthesis develops the proposed ways and their connections. Neither is reported as demonstrated effectiveness or transfer. |
| Naming route | provisional HydroponicCucumberPrincipleFramework; the public abbreviation remains provisional until an F.18 NameCard is current |
| First pattern draft | HC.NutrientMonitoring drafted with E.8: problem frame, solution, worked greenhouse slice, SoTA row, conformance checks |
| Relation and edition record | PFR-HC-source-reuse links the nutrient pattern to the source pack. Using E.4:5’s illustrative editions, HydroponicCucumberPF@2026Q3 depends on FPF@C1: A.3.1:4.3 supplies the Method/MethodDescription/Work distinction for the monitoring explanation; E.8:4.1.2, item 6, supplies the direct-consumer repair requirement for pattern revision. The dependency record names FPF@C1 as reliedOnEditionRef and those two claims as reliedOnContentRefs. |
| Quality cycle | E.22 frames evaluation purpose; E.21 scores first draft; E.23 records the next improvement loop |
| Local publication or access | One all-in-one carrier contains the short Hydroponic Cucumber Readme, search-oriented ToC, full Hydroponic Cucumber Principle Framework Architectural Reference, and pattern bodies. The account explains their connections and source-dependent limits; supporting source maps remain reachable after the bodies. Any access route is named separately. |
| Refresh route | G.11 refresh when the source pack, selected FPF@C1 edition, either relied-on Core claim, or greenhouse-control practice changes; reopen the explanations and uses affected by the change. |
E.4.DPF:5.1 - Pattern-address and reorder slice
A Systems Engineering DPF edition gives SYSE.22 a stable address and places it after SYSE.2 because that order helps its readers. A later edition may move SYSE.22 without renaming it when its recurring problem and working answer continue; the ToC and body order change together, while old citations still resolve through the same PatternID.
If a later repair splits that working answer, only the continuing answer keeps SYSE.22; the other answer receives a new unused PatternID, and readers of the old reference get a short migration assertion or an explicit stop.
E.4.DPF:5.2 - Local-mantra authoring slice
After the HC.NutrientMonitoring Solution is stable, its authors use the local mantra: Name the crop stage and root-zone condition; establish that the measurement is usable in its current calibration range; compare it with the stage-specific range; change the control setting only within the declared operating boundary; return when crop stage, sensor validity, or operating boundary changes. The formula helps a grower or crop-system architect keep the pattern’s operative distinctions and return condition in attention. It remains Plain wording inside HC.NutrientMonitoring.
If a seminar instead needs to show alternative continuations for invalid measurement, out-of-range nutrient condition, control saturation, and crop-stage transition through one named wider unfolding structure, the authors open A.22.CGUS and build a demonstrative walkthrough. They do not obtain that structure merely by extending or repeating the local mantra.
E.4.DPF:5.3 - Optional organization-proposal slice
A team intends a new clinical-method DPF, and a named review use needs candidate organization claims before an architecture answer is selected. It creates one current U.WorkPlan for possible future DPF-authoring Work, then one C.2.1 IntendedFrameworkResultDescription whose identity is its exact intended-result ClaimGraph, that WorkPlan as EntityOfConcern, and its effective ReferenceScheme; ClaimScope remains separate.
FrameworkOrganizationDesignProposal uses that description as its EntityOfConcern and proposes candidate pattern-family, dependency, publication, and access relations in one ClaimGraph. The proposal is the current result. No future framework entity, actual architecture, architecture description, dated Work, or production relation is asserted.
E.4.DPF:5.4 - Coverage and acceptance slice
The proposal’s medication-review coverage criterion names the pattern families whose representation is necessary for that declared use. One constraint claim node names the covered relation-family refs with exact kinds, that admitted use, and the coverage criterion. The authoring WorkPlan separately cites an acceptance target for review completion. C.33 uses the coverage node as comparator when evaluating proposal coverage; the WorkPlan target does not replace the criterion.
E.4.DPF:5.5 - Empirical-grounding and use-frame stress slice
The intended-result description has a separately obtaining EpistemeEmpiricalGroundingRelation to MedicationReviewTeam@Hospital-A, an A.1-admitted holon, covering the exact supported claim subgraph. The holon is not an episteme identity slot.
A request to rely instead on a consortium first rechecks the empirical-grounding relation and evidence, effective ReferenceScheme, ClaimScope, and any independently selected BoundedModelUseStructure. Changing only the empirical ground changes that relation; changing the ClaimGraph, EntityOfConcern, or effective scheme identifies another episteme. F.9 opens only if an exact cross-context local-sense translation is current, not merely because the maintaining organization changed.
E.4.DPF:5.6 - Optional authoring-dependency slice
A named next authoring use needs a stable dependency account. The selected FPF edition is available and relevant now, so its fpfEdition position has exact value and kind refs and no acquisition condition. The next-use boundary names the Core claims needed for that authoring use. The accepted architecture answer is cited through its E.9 DRR because this use needs that rationale; it is not a mandatory PFAD dependency position.
A publication carrier is missing but retained for later use, so its position has no value refs, has an acquisition-condition description, and does not block current pattern drafting. A missing source pack marked currentForNextAuthoringUse blocks the next use and opens the stated return. Availability never stands for relevance.
E.4.DPF:5.7 - Framework-evolution slice
A new controlled-environment study changes the admissible nutrient range used only by HC.NutrientMonitoring. Because this example selected a broad, refreshable G.2 pack, first revise that pack and preserve the displaced source reading. Use E.4.PFR to identify the nutrient pattern, its source-reuse relation, and its dependent examples as the affected set; use E.21 to evaluate the revised pattern body; use E.23 for repeated improvement of that pattern edition; and use G.11 for currentness, telemetry, and deprecation or supersession of exposed editions.
Unaffected climate-control and harvest-feedback patterns remain current. E.4.PFAD stays closed while framework family, pattern split, relation structure, publication-form, presentation-carrier or access-route architecture, and dependency boundary remain unchanged; a change to one of those decisions makes PFAD current again.
E.4.DPF:6 - Bias-Annotation
Scope: Use this pattern to select, author, assemble, and refresh FPF-grounded DPF or LPF editions and their first-use publication forms, presentation carriers, and access routes. Lifecycle, product-ontology, research-method, and general publication questions return to their owning patterns.
| Lens | Likely drift | Repair |
|---|---|---|
| Gov | A framework name, package form, or authoring step is read as acceptance, authority, currentness, or maintenance responsibility. | State acceptance, authority, currentness, and maintenance through their own decisions and direct relations. |
| Arch | The current authoring slice, file layout, carrier, or pattern count becomes the framework boundary. | Decide the field, connected problem families, material pattern relations, first use, support units, adjacent subjects, and edition/change boundary by content. |
| Epist (Epistemological and Ontological) | Methods, descriptions, Work, patterns, editions, carriers, programmes, services, and product wording collapse into one convenient object. | Name only the direct subjects and relations used by the current decision; keep product Plain and return an unresolved kind as a question. |
| Prag | Source, quality, relation, and publication apparatus grows before it changes a practitioner decision, or a thin extra pattern is added to satisfy a count. | Choose the smallest source and assurance route that closes the use; apply the same semantic framework-scale test at every count. |
| Did | Ontological precision or package machinery displaces the recognizable domain problem, useful move, worked case, and stop or return. | Keep the first-hour route and pattern bodies in precise plain language; place heavier architecture and assurance after recognition and only where use needs them. |
The first recurring drift is source-summary confidence: a summary feels sufficient because it names the right domain terms. Choose the smallest route that keeps the relied claims, rejected readings, limits, and source editions recoverable, then carry them into pattern Solutions and examples. Use a G.2 pack only when the question needs its broad, refreshable source frame and downstream handoffs.
The second recurring drift is publication-carrier-first authoring. Publish after the architecture decision, direct assertions of material relations, and source-return notes are recoverable, together with any relation or edition records required by a current maintenance use.
E.4.DPF:7 - Conformance Checklist
| Check | Passing condition |
|---|---|
| CC-DPF.1 Use frame declared | Intended reader, first use, stop or wrong-turn return, effective ReferenceScheme, ClaimScope, and qualification window are named. Any non-use boundary passes F.19’s grounded-contribution test; an optional BoundedModelUseStructure appears only when its organization changes interpretation. |
| CC-DPF.2 Source basis and synthesis route | The DPF names the source situation and uses the smallest route that returns the needed result: direct reliance, a maintained synthesis or guide, F.1, F.0.2, an optional G.2 pack, an earlier DPF, or a derived lookup. Adopted and rejected payload, source roles, examples, currentness, partial lookup limits, and reopen conditions are recoverable. Pack conformance, source counts, and lookup misses are not treated as domain-claim evidence. |
| CC-DPF.3 Architecture answer when needed | A cheap route or stop closes without a DRR when it settles no later-used framework decision. Otherwise one E.9 DRR guided by E.4.PFAD records one of five outcomes: a new or revised framework, a contribution to an existing framework, a non-framework product, a thinner publication or access route, or no new maintained product now. For a framework answer it also records the field and practice promised by the public name; coverage, representative application, edition and dependency decisions, initial pattern placement and material relations; publication or access consequence; alternatives; action; and reopen condition. Answer, acceptance, DRR, relation records, edition dependencies, package architecture, authoring, and publications remain separate. |
| CC-DPF.3a Framework scale and singleton diagnostic | pattern_count = 1 is reported as a strong diagnostic, and the same semantic test is run at every count. A new first edition supplies an adequate pattern language for its declared field or practice: a coverage map, selected problem-family pattern sets and material relations, a representative application, an internally usable first-edition set, an account of omissions and where to return to the sources, and a credible edition, change, and refresh boundary. A candidate fails when these contributions are missing or do not work together, not because of its count. |
| CC-DPF.3b Internal and external first-use closure | The first-edition set includes every selected pattern and same-framework prerequisite needed for the named first use. Before keeping, merging, removing, profiling, reusing, externally supplying, or omitting a narrower contribution, apply E.8:4.1.3 and distinguish an available result and supplying product, a MethodDescription, direct-source evidence, and a named unavailable result. Keep external results outside the framework. Identify each result and the content relied on. State the result’s direct kind, supplying product, edition or current state, receiving use, discovery route, material currentness or availability condition, and externality. State maintenance separately only when it changes that use. For the receiving use, the external result is either the content relied on or identifies that content. If that use also requires a separate availability or compatibility result, identify that result and the basis on which it applies. An edition dependency adds direction, reason, and refresh only when that relation obtains. A missing required result is a first-use blocker. After a material promised-family change, obtain the current E.4.DPF.DA D12DomainProblemFamilyCoverageAdequacy result for the resulting DPF or LPF edition; reuse it only while the edition and basis remain unchanged, without requiring proof of a revisit. |
| CC-DPF.3c Accepted practice-architecture input | When professional Method coverage changes the architecture answer, one exact accepted E.4.PFAD answer projects five connected claim groups from its compact answer rather than creating a second record. Each bounded practice claim or promised contribution distinguishes existing practice from a proposal and states its supported, refuted or unresolved content; different statuses may coexist, and every selected question and DPF disposition names the claim or claims it consumes. Incumbent Work, development or trial Work, candidate-practice Work, A.13 agency claims, and public coverage retain separate status. For an obtaining Agent-performer claim, use A.13’s core. A.15.1 independently admits actual Work. F.6 follows only for precise attribution through the same assignment. Require a characteristic profile only for a consumed Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use. A proposed-practice branch names any incumbent Work or Method, intended use, realization conditions and grounds appropriate to its claim. It plans a trial only when required or justified by a material evidence gap and attainable contribution; actual candidate-practice Work, Agents and coverage retain their separate admission and support conditions. A missing required group or binding returns a PFAD gap before authoring. C.32.MWA is used only for decision-relevant non-isomorphic structures. D1, D7, D8, and D12 preserve each claim’s truth boundary; the same evidence enters the D1–D12 aggregate once, and D12 alone owns integrated coverage. Compact prose can pass, but a source map, fixed schema, fixed view set, second record, or second checklist cannot substitute for practice architecture, domain evidence, or package evaluation. |
| CC-DPF.3d Support and adjacent-product decision | Product remains Plain management wording. Units kept inside the framework share its edition, declared readers and use, edition boundary, access, and change rule. Every separate adjacent result names its direct subject, exact edition or current state, independent use, intensional rule for what belongs, access, and any later-review or retirement condition that changes use. Any maintenance relation is stated only when it separately obtains and changes use. Programme wording names the arrangement or description, any provider System, maintenance relation, accepted commitment, or admitted service state that obtains; bounded Work and result epistemes remain separate. When a use requires one of these direct relations and it cannot be established, record the exact result under its governing rule or the applicable A.6.RCD blocker; reserve missing-governor for a missing governing rule. |
| CC-DPF.3e Suite authoring | A Suite follows the composite-discipline architecture established through C.20, E.4:4.2 and E.4.PFAD. Its entrance and whole-level patterns explain actual connections between independently usable constituent DPFs, while external suppliers remain direct uses. The edition names its constituent editions and coverage limits. A Reference supports selection and return. It leaves any unwritten Method visible as a gap. Changes of field boundary or part relation reopen the architecture rather than being effected by a file move or local declaration. |
| CC-DPF.3f Practical examples and card declaration | The product’s one declaration assigns every selectable Readme example key one ordinary-entry or card form and one selectable occurrence. The Readme returns unmatched questions to the index, guide, search, or direct patterns and applies §4.0.2 to any additional coverage correction. Each card passes E.11’s same-content-without-mantra test, preserves a real path through several direct pattern contributions, uses the product’s measurable mantra/card guard, applies E.11.PFP, and returns to the direct patterns. A plausible direct entry is checked under the same test. Locators, local reminders, Readme card mantras, expansions, and CGUS demonstrations remain distinct, and no FPF example set or limits are copied as the common rule. |
| CC-DPF.3g Pattern address and publication order separate | The DPF declares its stable reference code and local PatternID plan before public references accumulate. The same PatternID is retained only while the recurring problem, distinguishing working move, useful result, and ordinary conditions for use, stopping, or returning still describe the same practical answer. Numeric or mnemonic locators follow the stated use test. ToC and body order agree, current position is shown separately, and dependencies, Method relations, Parts, and work packages are not inferred from the identifier or its position. A planned row remains a non-addressable PlannedCatalogEntry until a complete pattern is admitted. A split, merge, replacement, retirement, or DPF-code rename gives readers either an accurate, maintained statement of where an old reference leads or an explicit stop; new patterns receive new unused PatternIDs. |
| CC-DPF.4 Names prepared | Durable public names and abbreviations have F.18 name-card work or are explicitly provisional source aliases. |
| CC-DPF.5 Carriers and routes classified | For an architecture-evidence use, apply C.33 to selected-structure recovery and C.34 to an asserted structure-preservation comparison when each question is current. Apply C.35 to the exact generated or discovered result intended to inform architecture work, stating what is established about its kind, the organization concerned and the status of the actual or proposed claim, including any unresolved basis, next-use condition, and limit and return. Each access route is identified separately from any artifact it returns and from actual access or use. Concrete implementations such as generated views, skill packs, services, endpoints, retrieval or search routes, and assistant integrations use the same distinction. |
| CC-DPF.6 Patterns drafted through E.8 | Pattern bodies carry recognition text for recurring domain or local problem situations, positive SoTA-informed solution moves, worked cases, known failure modes or local anti-patterns, checklist, SoTA-Echoing, and relations. Skeletons, prompt seeds, and compressed design notes are named as seeds rather than treated as normal DPF patterns. |
| CC-DPF.7 Quality and refresh routes present | E.22 frames evaluation purpose when needed; E.4.DPF.DA package adequacy, E.21 pattern quality, E.23 improvement, and G.11 refresh routes are named with edition or refresh conditions. Source or depended-on edition changes, repeated reader errors, compatibility impact, deprecation, and supersession return through those routes at the smallest affected scope. Public, teaching, enterprise, or reliance-bearing DPF publication names the checked pattern-quality basis or remains seedOnly. |
| CC-DPF.8 Carrier structure-account visible | The architectural reference, reached from the Readme or an equivalent practical entry, says which domain or local problem-and-solution structures the framework exposes, for whom, what is foregrounded, deliberately coarsened, abstracted, omitted, deferred, or lost, and where source, pattern, evidence, or relation return happens. |
| CC-DPF.9 Problem-solving primacy | The DPF tells which typical domain or local problems it helps solve, which known failure modes it blocks, and which source-grounded SoTA solution moves it offers. |
| CC-DPF.10 Current first result | The selected result is a cheap route or stop with no DRR; one of the same five architecture outcomes in an E.9 DRR when a later-used boundary is open; an optional C.2.1 organization proposal; a post-existence C.30.AD description use; or an optional C.2.1 authoring-dependency description. Each result has its own entry condition, result kind, and receiving use; list order creates no lifecycle. |
| CC-DPF.11 C.2.1 proposal constitution | Intended-result description identity is its exact ClaimGraph, current A.15.2 WorkPlan EntityOfConcern, and effective ReferenceScheme; proposal identity is its exact ClaimGraph, that description EntityOfConcern, and effective ReferenceScheme. ClaimScope, empirical grounding, model-use structure, provenance, publication, and edition relations remain separate. |
| CC-DPF.12 Subject organization | Candidate organization is recoverable from typed claim nodes and proposed subject relations; no future entity, episteme-per-claim wrapper, or proposal-document meta-structure substitutes for it. |
| CC-DPF.13 Coverage distinction | A coverage constraint node has family ref-kind pairs, one admitted use, and one criterion; any WorkPlan acceptance target remains separate. |
| CC-DPF.14 Architecture and project-use boundary | C.33 compares with a declared present comparator; C.30.AD starts only after the framework entity, exact architecture relation, and selected structures exist. ArchitectureDescriptionUseCard@Project is retrieval-only. Actual project locality names one composite project U.Work under A.15.6 only when that Work is claimed. Every precise performer has an A.13 core; A.15.1 independently supplies Work identity; F.6 supplies a later relation only when precise assignment-bound attribution is current; and the description-use relation obtains separately. |
| CC-DPF.15 Dependency description and branches | The description exists only for a named next authoring use. Its identity is the dependency ClaimGraph, current authoring WorkPlan EntityOfConcern, and effective ReferenceScheme; ClaimScope and optional model-use or grounding relations remain separate. Its minimum positions are FPF edition and source basis. The FPF position identifies the edition, and the next-use boundary identifies the Core claims required for the named authoring use. An optional framework-architecture-answer position cites the accepted answer and E.9 DRR only when that use needs them; no PFAD relation or record is required. Availability, acquisition condition, and next-use relevance follow the independent branches in 4.5. |
| CC-DPF.16 Method, Work, result, edition, and publication separation | The authoring Method and this independently qualified MethodDescription, WorkPlan, each separately claimed dated authoring U.Work, every precise performer’s A.13 core, independent A.15.1 admission, any current later F.6 attribution, any A.6.1 application, every result entity or direct relation and receiving use, framework episteme editions, EpistemeEditionRelation, package architecture, publication occurrence, form, carrier, and access use are independently recoverable through their defining predicates and evidence. |
| CC-DPF.17 CGUS restraint | The numbered routes remain Plain guidance. Any claimed A.22.CGUS has independently recovered identity, constituents, obtaining relations, constraints, multiple admissible continuations, stops/returns, and a separate demonstrative episteme; imperative prose or a mantra is insufficient. |
| CC-DPF.18 Assembled carrier checked | Before a carrier is called released, current, or ready for its declared use, the assembled publication follows the common framework publication form defined by E.11.PFP, agrees with the product’s declaration of practical-example keys, forms, reading-burden measure and two limits, carries the entry guidance and unmatched-question return selected under §4.0.2, passes the E.11 practical-use carry-through check, and passes the applicable E.4.DPF.DA package checks. An all-in-one Markdown publication exposes no build metadata as reader front matter, keeps major units or Parts at H1, pattern titles with PatternIDs at H2, canonical E.8 sections at H3, and every deeper source distinction at a distinct deeper level. Source-body conformance and a successful build run do not substitute for checking the assembled carrier. |
| CC-DPF.19 Claim placement and local wording | Apply F.19 to the whole span for generic precise plain language. Domain claims, examples, role-shaped wording, Method claims, and refresh lines stay in the DPF patterns that use them. E.10.ROLE recovers any load-bearing role sense without choosing a system-role kind, assignment, or position from the word alone. A proposed transdisciplinary improvement returns through an FPF amendment decision. A domain wording entry uses the shared E.10.ARCH method and stays beside the affected DPF patterns. A separate profile is a claim-bearing episteme with a named maintained multi-entry use. If the profile is published in a table, the filled table expresses it and the reusable layout rules supply the publication form. |
E.4.DPF:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | What fails | Repair |
|---|---|---|
| Checklist promoted to framework | Local tips are published as a principle framework without source, pattern, relation, or quality work. | Keep the checklist as local process text until the selected source route, E.8 pattern work, material relation assertions, and E.21 evaluation support a DPF. |
| Source summary as SoTA | A literature narrative replaces adopted and rejected source payload and never returns a domain move. | Choose the smallest source route, recover load-bearing claims and limits, and carry them into a pattern Solution, boundary, worked case, contrast, or unresolved inquiry. |
| Chapter-complete map as practice coverage | Every source chapter has a pattern destination, but the package has no decision-bearing account of recurring difficulties, receiving results, project and Method positions, several structures, pressure evidence, subtraction, or reopenable gaps. | Return to the accepted E.4.PFAD practice-architecture input, organize domain fillings by practitioner situation and receiving use, and leave a missing filling as a seed, gap, or omission. Source provenance remains evidence input rather than the coverage criterion. |
| Earlier DPF as ecosystem law | A useful precedent is copied into another DPF or FPF without checking its subject, Context, edition, use, and transfer limits. | Reuse it through an explicit dependency when those fit; otherwise keep the new claim local or submit a separately reviewed FPF improvement. |
| Lookup miss as absence | A search index or generated crosswalk returns nothing, so the author concludes that FPF, a DPF, or the literature has no relevant contribution. | Report partial coverage, return useful hits to authoritative bodies and editions, and widen the lookup when a known contribution is missing. |
| Wording profile by default | Every DPF receives a trigger registry or profile although no recurring domain wording failure or maintained multi-entry use has been shown. | Write only the local entries needed by affected patterns. Identify a separate profile only for a named maintained multi-entry use. A filled table can present those entries. |
| Ontology catalog as framework | The package classifies the domain or defines terms, but it does not tell a practitioner what typical problem is live or what SoTA solution move avoids a known failure. | Keep ontology as support material; draft or repair DPF patterns around problem frames, positive solution moves, worked cases, anti-patterns, and refresh. |
| Outside the pattern set means another product | An architectural reference, coverage account, registry snapshot, or refresh note is split or absorbed by file location rather than shared edition, reader use, access, and change rule. | Keep units that share those facts together. Keep an independently useful adjacent subject separate and point to its exact edition or current state; state maintenance separately when it obtains and state later-review or retirement conditions when they change use. |
| Combined carrier merges products | A DPF and an adjacent catalogue, guide, evidence package, service, or programme receive one framework identity or index. | Keep the outer carrier neutral, apply E.11.PFP only to framework constituents, and retain each adjacent direct subject’s identity or state, form, access, change rule, and any separately established maintenance relation. |
| Publication carrier as architecture | Publication occurrence, form, presentation carrier, package boundary, or access route is treated as framework episteme, edition continuity, package architecture, relation membership, or truth. | Recover E.4.PFAD architecture decisions, E.4.PFR relations and dependencies, C.2.1 framework identity, and E.24.PUB publication occurrence, form, and carrier separately before relying on the exposed content. |
| Invisible framework story | A DPF carrier reads as a neutral list of principles, but the reader cannot tell what source or domain structures were selected, why this route is for them, what was deliberately coarsened, abstracted, omitted, or left to source return, or whether the carrier is a second-step coarsening after an architecture description or view. | Make the carrier’s structure selection and loss explicit in the architectural reference and its entry cue, then evaluate it through E.4.DPF.DA rather than scattering explanation into every pattern body. |
| Generated candidate authority | Search or LLM output becomes the framework because it is fluent. | Use C.35 for admission, then decide candidate selection through E.4.PFAD or C.32. |
| Skeleton carrier as DPF | A file has a ToC, headings, and very short pattern-shaped sections, but readers still cannot apply the patterns without reconstructing the missing guidance from the DRR or source notes. | Keep it as seedOnly; harden each DPF pattern through E.8, evaluate through E.21, and only then assemble the user publication carrier. |
| Singleton authoring slice as edition | One useful pattern or one narrow authoring slice receives a broad framework name because it is the material currently being written or reviewed. | Report the singleton as a strong diagnostic and run the same framework-scale test used at every count. Keep it as a seed, candidate, or existing-framework contribution when connected problem-family coverage, material pattern relations, a representative application, an internally usable first-edition set, an account of omissions and where to return to the sources, or a credible edition, change, and refresh boundary are missing; do not fail or pass it by count. |
| File inclusion manufactures disciplinary membership | A DPF author treats a guide entry, shared use or added file as proof that a discipline is a constituent of the Suite’s field. | Recover C.20’s direct part relation and whole construction; return a changed architecture to E.4.PFAD. Preserve a useful external result as a use or dependency without absorbing its whole DPF. |
| Card-per-pattern fanout | Every DPF pattern or locator receives a mantra because the card form exists, increasing burden without changing first use. | Apply the E.11 same-content-without-mantra comparison; keep locators and ordinary entries when they already support reliable choice and return. |
| FPF card application copied or declaration avoided | The DPF copies FPF keys, card count, whitespace-token measure, numeric limits, or @FPFReadme records, or labels every rich entry ordinary so no card declaration is needed. | Keep one product-native example declaration, reading-burden measure, and two limits; reuse the shared field grammar from E.11.PFP, and check both selected cards and plausible non-card entries through E.11. |
| External dependency hidden as closure | A first-edition set omits a needed same-framework prerequisite or silently assumes an FPF, DPF, or LPF edition, availability result, or compatibility result. | Include every same-framework prerequisite needed for the first use. For each external dependency, identify the result and relied-on content, edition or current state, receiving use, direction, reason, refresh condition, and any required availability or compatibility result with the basis on which it applies; return a missing requirement as a first-use blocker. |
| Access route or returned artifact as framework | An access-facing artifact or route is treated as the framework because it is what a reader or System calls or sees. | Identify the exact artifact under its physical or digital domain and establish that its actual state or realization yields the selected expression. Recover any form conformance separately, and identify the service or other route. Use E.24.PUB and the direct access or use pattern for publication, availability, actual access, and use; expose the exact framework edition and currentness return. Concrete implementations such as skill packs, endpoints, retrieval or search routes, and assistant integrations use the same distinction. Use E.4.PFR only when a named maintenance use needs a stable relation representation. |
| Future framework fabricated | An optional organization proposal points to the absent framework or claims its actual structures. | Create a current intended-result description and one proposal episteme; wait for an accepted E.9 framework-architecture answer and later realization before architecture-description use. |
| Claim wrapper collection | Every candidate organization claim becomes another episteme. | Keep typed claim nodes in the proposal’s one ClaimGraph unless a separately grounded claim episteme has its own EoC and use. |
| Proposal layout as subject organization | Headings or ClaimGraph organization are treated as the proposed framework organization. | Recover described position kinds, proposed subject relation signatures, constraints, invariants, dependency directions, alternatives, basis, and questions. |
| Coverage and acceptance union | One field mixes coverage criterion with WorkPlan acceptance target. | Keep the coverage node complete and cite the plan target separately. |
| Availability as relevance | A missing dependency is assumed blocking, or an available dependency is assumed current for next use. | Fill availability and use relevance independently; only the combined state determines the next-use consequence. |
| Grounding or context as identity | A grounding holon, organization, project label, package boundary, or bare context word is inserted into episteme identity or used to force sameness. | Keep C.2.1 identity at ClaimGraph, EntityOfConcern, and effective ReferenceScheme; use separate empirical-grounding, ClaimScope, model-use, project-Work, and exact cross-context translation relations only when their predicates obtain. |
| Authoring order as Method, Work, result, or CGUS | Numbered guidance, arrows, coordination rows, or document order is used as proof that a Method, Work occurrence, result relation, or conditional structure exists. | Recover the authoring Method and qualify a MethodDescription only through A.3.2. When dated Work is claimed, recover every precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is also current. Identify any A.6.1 application, direct result or use relation, or independently selected A.22.CGUS separately. Otherwise keep the sequence Plain. |
| PatternID used as position or definition | Inserting or moving a pattern causes renumbering, or a mnemonic is treated as a title, dependency, Method relation, or compressed claim. | Keep the public address stable while the practical answer continues, show the current position separately, and state titles and relations in their own fields. Decide splits, merges, replacements, and retirements from content rather than identifier shape. |
| Build manifest as public framework prose | An all-in-one carrier opens with generated comments, source paths, digests, machine identity fields, or builder warnings, so reproducibility apparatus displaces the working-question route. | Keep those values in builder output, package evidence, or a separately justified manifest; expose E.11.PFP’s short public edition line and only those additional cues whose selected reader use requires them before the ToC. |
E.4.DPF:9 - Consequences
Using the exact authoring Method and MethodDescription while keeping dated Work, results, receiving uses, editions, relations, package architecture, and publication objects explicit adds overhead before a local framework becomes durable. In return, the source basis, Core change impact, relation semantics, production and membership claims, and currentness debt become reviewable at their own boundaries.
The pattern also makes local publication more useful. Readers get a coherent publication or practical-use carrier, while maintainers can still inspect the framework edition, source pack, relation records, decision records, and quality route.
E.4.DPF:10 - Rationale
Domain and local frameworks are FPF-grounded framework editions for declared domain or local use frames. They need domain source work, FPF authoring discipline, architecture decisions, direct relation assertions, quality loops, and refresh routes. Add the relation or edition records needed for a current maintenance use; a direct assertion closes the task when no such representation is needed.
Its contribution is one framework-authoring Method plus Plain selection and branching guidance. This episteme qualifies as its A.3.2 U.MethodDescription because it describes that admitted Method as its EntityOfConcern. E.8 supplies the pattern-authoring and publication-form discipline; A.3.2 supplies MethodDescription qualification. When an A.22.CGUS is current, admit it separately with exact conditions, continuations, stops, and demonstration. Every produced or selected result needs a receiving use and the pattern that defines, constrains, or tests that result or use relation.
E.4.DPF:11 - SoTA-Echoing
| Practice question | Best-known line | Alternative or default | Defect overcome and E.4.DPF mutation | Source roles and limits | Reopen condition |
|---|---|---|---|---|---|
| How should a DPF or LPF keep a stable public pattern reference while editions are rearranged or rebuilt? | The best-known line for this bounded identity problem combines persistent public locators with an explicit distinction among the continuing framework or product series, local PatternID, current position, and edition-specific body. A split or merge is decided from content and use rather than from path, heading, or number. | Repository paths, ToC position, section numbers, and heading text are cheap to publish and easy to mistake for identity. | Those defaults silently reassign old references when a body moves and can treat editorial rearrangement as a new pattern or a substantive split as continuity. Adapt: section 4.0.3 and its display, citation, migration, and conformance rules preserve the stable designation and make edition/body position explicit. Reject: path identity, numeric-order identity, a global registry requirement, and identifier syntax as evidence of pattern continuity. | W3C Data on the Web Best Practices and its URI persistence policy supply a best-known-line candidate for persistent locators and series/version separation. They do not define FPF pattern identity, require a global registry, or prove that two bodies are the same pattern. Current FPF identity and edition patterns supply the selected receiving boundary. | Reopen if a real cross-framework reference cannot recover the intended body with framework designation, PatternID, and edition where needed, or if a lower-effort identity practice preserves old references and content continuity more reliably. |
| What is the lightest authoring route that can turn a domain or local question into a usable framework edition without collapsing source work, architecture, patterns, relations, publication, evaluation, and currentness into one lifecycle? | The best-known current line is the bounded FPF composition used in section 4: choose the smallest adequate source route, settle only the architecture decisions the next use needs, draft patterns through E.8, assert material relations directly, add relation records only for a named maintenance use, assemble a truthful carrier, and return separately from package quality, improvement, and currentness. | A template-first monolith or one imported software-product-line lifecycle. It promises a complete sequence and common/variable machinery before the actual domain use, source burden, or product boundary is known. | The default either hides missing evidence behind completed sections or imports software-product, feature, tool, and lifecycle ontology that does not answer an arbitrary DPF question. Adapt: the source-basis branches, proportional-apparatus ladder, MethodDescription and method steps, local repair map, direct relation assertions, carrier boundaries, and separate quality/currentness exits. Reject: one compulsory external lifecycle, automatic broad synthesis, package adjacency as relation evidence, and generated text as authority. | Current F.0.1, F.1, F.0.2, G.2, E.4.PFAD, E.8, E.4.PFR, E.11.PFP, E.4.DPF.DA, E.21, E.23, and G.11 are the direct internal owners of the selected line. The 2022 systematic review of software-product-line scoping is a bounded rival for family scoping because it compares 41 approaches and exposes technical and organizational variation; it does not supply the whole DPF route or make software-product ontology portable. | Reopen if a serious current authoring approach gives the same source honesty, object separation, usable first edition, migration path, publication boundary, and local repairability at lower practitioner or maintainer effort, or if an actual DPF cannot proceed through the bounded branches. |
| When is a domain-specific pattern set adequate to claim a field-serving framework rather than a seed, loose catalogue, or well-formed carrier? | The best-known line combines action-changing pattern evidence with explicit family scope: name the public field promise, test how the selected problem-family sets and their material relations serve a representative cross-problem use, include every pattern required for the first use, expose relied-on external results and important omissions, and reopen D12DomainProblemFamilyCoverageAdequacy after a material promised-family change. | Name specificity, component count, section presence, a rule of three, and a successful form or build check. A full software-product-line process is the heavier alternative. | The cheap defaults can certify an empty or disconnected package; the heavy alternative adds feature and product machinery before domain value is known. Adapt: E.4.DPF:4.0, the E.8:4.1.3 same-situation action test, representative cases, first-use completeness, external-result return, seed-versus-reliance boundary, E.4.DPF.DA D12 route, and exact-basis reuse. Reject: numeric pattern thresholds, form-only adequacy, title-only specialization, and proof that a revisit occurred. | Riehle, Harutyunyan, and Barcomb’s pattern discovery and validation method is a best-known-line candidate for explicit claims, qualitative survey, action research, cases, and evidence limits. The 2022 scoping review is the bounded family-scope comparator. Chuprina et al.’s domain-specific requirements-pattern approach is bounded proof-of-concept evidence; transfer beyond its evaluated setting remains untested. Current FPF rules adapt these contributions into the DPF-specific first-use and externality boundary. | Reopen if comparative validation or field use changes the evidence needed for a separate pattern or framework, if a representative use defeats the selected set, or if a stronger approach exposes a lower-effort way to test family coverage without the rejected proxy or software-specific machinery. |
Source identity and currentness support replay and targeted refresh only. A later publication date, maintained repository, institutional status, or wider adoption cannot raise these comparisons; G.11 reopens only the smallest receiving rule when changed evidence can alter the selected answer.
E.4.DPF:12 - Relations
- Uses for methodological construction: C.39 for general construction, connection, explanation and change; E.4.CM for applying that way to the framework’s developed public account of Methods.
- Uses: direct source reliance when one source closes the question;
F.0.1for source-local meaning;F.1for a relevance-based source cut;F.0.2for one bounded semantic-synthesis result; andG.2only for the broad, refreshableCG-Framepack. Identified pack claims and provenance may enter F.0.2, but the pack does not establish its result. - Uses:
A.3.1for the framework-authoring Method andA.3.2for this independently qualified MethodDescription; A.13 for every precise performer’s core and same obtaining assignment;A.15.1for independently admitted dated authoring Work;F.6only for a current precise assignment-bound attribution;A.15.PRODfor any local inception or production-completion claim;A.6.1for an actual application and its bindings;E.8,E.10, andF.18for pattern drafting, wording discipline, and names; andE.10.ARCHfor local domain wording restoration when a recurring problem has been shown. - Coordinates with:
E.4for family membership and the proportional support-unit/adjacent-product boundary, andE.4.PFADfor architecture decisions; usesC.32.MWAwhen several practice structures need one synthesis andE.23.CDIonly when capability development for a named Work family is current. - Coordinates with:
C.2.1andA.2.6for framework/result episteme identity, effective ReferenceScheme, empirical-grounding relations, and ClaimScope;A.1.1/A.22only for an independently selected model-use structure;A.22.CGUSonly for an admitted conditional unfolding;E.4.PFRfor separately identified relation records and for dependency, edition, compatibility, deprecation, and supersession effects;C.30.ADfor post-existence architecture-description use and its retrieval-only project card name; andE.24.PUBfor publication occurrence, form, and carrier. - Coordinates with:
C.33for recovery of selected architecture-relevant structure,C.34for use-bounded structure preservation, andC.35to identify the generated or discovered result, establish its kind and status, and determine admission for its intended architecture use. - Coordinates with:
E.22for quality-evaluation framing when needed,E.4.DPF.DAfor DPF package adequacy,E.21for pattern-quality evaluation,E.23for repeated improvement,E.19for selected admission or refresh questions and material-edition affected-use replay, andG.11for currentness. - Use next when current:
E.11.PFPfor the common framework publication form,E.11for practical-use discoverability,E.11.DSGfor the full architectural reference of the framework and its relations to Suite or Library accounts, andE.17for publication discoverability rather than framework authoring.