Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:40:20 UTC

E.4.FPF - FPF Edition Assembly: Publication Forms, Carriers and Access Routes

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative.

E.4.FPF:1 - Problem frame

Use this pattern when an FPF steward, framework author, reviewer, or AI agent must assemble, expose, or evaluate one FPF edition and distinguish it from its publication units, forms, presentation carriers, access routes, and domain or local dependents.

Primary EntityOfConcern: the scoped FPF edition (FirstPrinciplesFrameworkEdition) being assembled, exposed, or evaluated. The first useful output is a record for rebuilding that edition.

It names the first-principles scope, selected Core patterns, recurring cross-domain problems and reusable solution moves, selected publication units, particular expressions and reusable forms, independently identified publication- or access-facing carriers with actual expression-bearing relations, access routes, edition relations, and the applicable whole-FPF quality result from E.2.DA.

Add a reference identifying the competing reading only when it passes the F.19:4 test: independent local ground, plausibility for the intended reader, a change in truth, understanding, or use, and the smallest clear correction.

Use this pattern when the work changes FPF publication units or forms—such as the public opening, Readme, Architectural Reference, ToC, first-entry view, cards, or split pattern collection—or assembles the exact physical or digital carrier whose actual state or realization yields their particular expression, such as an all-in-one file, site snapshot, volume, or bundle.

Use it also when a skill-pack carrier or an MCP, retrieval, search, or assistant access route exposes the edition. When a public presentation carrier is in scope, use E.11.PFP for its common reader-facing form and this pattern for FPF-specific source selection and assembly.

Use E.4.DPF when the framework is a domain or local framework grounded in FPF. Use E.4 when the live question is only family placement and routing among framework members.

A reader can identify the FPF edition, the reader-facing units and forms that expose it, and the exact presentation carriers that bear them. The account also tells the reader how to reach the edition and where to evaluate whole-FPF adequacy. A DPF or local framework may depend on FPF Core while remaining its own framework edition.

E.4.FPF:2 - Problem

DPF and local-framework packages can have detailed rules for publication units, forms, carriers, relations, naming, quality, and refresh while authors leave FPF’s form unstated because they consider it “the main spec”.

That creates several failures:

  • an all-in-one file or site, one of its Readme, Architectural Reference, ToC, pattern-body, card, or first-entry units, a skill-pack bundle, or an MCP route is mistaken for the FPF edition itself;
  • FPF is described as one more DPF, losing the first-principles and transdisciplinary burden that makes DPFs possible;
  • whole-FPF quality is checked by local pattern scores, landing status, or DPF package scales instead of E.2.DA;
  • adoption units, forms, or access surfaces grow user-facing explanations that quietly become shadow authority beside subject patterns;
  • skill or MCP access makes FPF look like a callable service, tool permission layer, or runtime dependency rather than a framework edition reached through an access route or borne by an exact access-facing presentation carrier.

Use an FPF-specific form rule. FPF must keep first-principles distinctions usable across domains while allowing domain and local frameworks to grow from it; E.4.DPF governs those dependent frameworks.

E.4.FPF:3 - Forces

ForceTension
First principles vs domain knowledgeFPF must carry transdisciplinary ontology, epistemology, evidence, architecture, decision, work, publication, and improvement distinctions without becoming a doctrine of one domain.
Public adoption vs subject-pattern authorityReadme, Architectural Reference, examples, cards, skills, and MCP access must help new users without becoming a second spec.
Core stability vs evolutionDownstream DPFs need a stable basis in FPF, while FPF remains open to new patterns, better terminology, and source-front movement.
Pattern-set quality vs whole-framework qualityIndividual E.21 results matter, but they do not establish whether the whole FPF meets the Pillars.
Carrier plurality vs identityThe same FPF edition can use several publication units and forms, several exact presentation carriers, and several access routes; those different objects must not create competing FPFs or collapse into one another.
Access convenience vs architecture clarityA callable access route can make FPF easier to use while hiding edition, currentness, source, and authority boundaries.

E.4.FPF:4 - Solution

Treat FPF as a FirstPrinciplesFrameworkEdition: one transdisciplinary edition with a selected Core pattern set and a stated first-principles scope. Record its recurring cross-domain problems, reusable solution moves, edition relations, publication units and forms, exact presentation carriers, and access routes under their direct subjects and relations. Coordinate them within that edition.

Units and forms expose selected content; presentation carriers bear the selected forms; access routes help an audience or system reach them.

Use these local names:

Local nameKind and use
FirstPrinciplesFrameworkEditionOne scoped FPF edition carrying transdisciplinary first-principles distinctions and the Core pattern set that downstream frameworks depend on.
FPFCorePatternSetThe selected subject pattern set for the edition. Readme, Architectural Reference, ToC, publication form, presentation carrier, skill-pack bundle, and access route use the corresponding local names below.
FPFPublicationUnitLocal reference for one selected content unit of the FPF edition, such as its public opening, Readme, Architectural Reference, ToC, first-entry view, card set, or pattern-body collection. The unit keeps the kind and identity supplied by the source that defines it. An independently identified carrier that bears its particular expression is named separately as an FPFPublicationCarrier.
FPFPublicationCarrierLocal designation for one independently identified physical or digital entity whose actual state or realization yields a selected FPF publication expression. PublicationExpressionBearingRelation relates that carrier to the expression it yields. When the expression conforms to the selected reusable form, it also witnesses PublicationFormBearingRelation. A managed all-in-one file, PDF volume, website snapshot, or bundle may supply the carrier under its own domain identity rule. Readme, Architectural Reference, ToC, logical index, and pattern collection name publication units or forms; name the carrier separately.
FPFAccessCarrierLocal designation for one 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 FPF expression. Identify any selected reusable form and its conformance separately. Services, endpoints, retrieval routes, search functions, and assistant integrations use FPFAccessRoute; name a returned carrier separately.
FPFAccessRouteOne identified service, endpoint, retrieval, search, or assistant route through which a declared audience or system may obtain the selected edition or reach a named carrier. Actual access, availability, reliance, authority, and Work use their own direct predicates and evidence.
FPFEditionRebuildabilityRecordClaim-bearing record for one FPF edition. It names the exact sources, publication units and forms, presentation carriers, access routes, edition relations, projections, quality and currentness results, and refresh routes needed to reconstruct that edition’s public form. A blocked-overread reference is optional and must pass F.19’s grounded-contribution test.
FPFLevelAdequacyAssertionRefExact whole-FPF adequacy assertion under the predicate defined in E.2.DA. Individual pattern-quality assertions use E.21, and DRR-quality assertions use E.9.DA.

The progressive-minimum F.18 NameCard NC-FPF-EDITION-REBUILDABILITY-RECORD names the family of claim-bearing records defined by the FPFEditionRebuildabilityRecord row and declaration in E.4.FPF:4. That section is the record family’s subject-pattern locator. This is an ordinary record family. Keep each under its direct kind: an individual record, its Markdown carrier, the assembly Method, the Work that enacts it, and an E.10 Map (a mapping U.Method).

The NameCard uses FPFCoreReferenceScheme by value. In that scheme, FPFEditionRebuildabilityRecord designates only the record family whose instances concern one FPF edition and name the exact sources, publication units and forms, presentation carriers, access routes, relations, projections, quality and currentness results, and refresh routes needed to reconstruct its public form. No Bridge is claimed.

Use the Tech designation in edition and rebuildability records, maintainer diagnostics, and direct consumers; use the Plain designation “record for rebuilding one FPF edition” in ordinary practitioner explanation.

The name comparison covers FPFEditionRebuildabilityRecord, FPFEditionAssemblyRecord, FPFEditionSourceAndCarrierIndex, and the predecessor FPFFormMap: rebuildability-record, assembly-record, index, and mapping-Method readings.

AssemblyRecord is too narrow because the record also names relations, projections, quality, currentness, and refresh inputs. Assembly follows. SourceAndCarrierIndex is too narrow because the record must also keep publication units, forms, and access routes distinct. FormMap is retired rather than kept as an alias because E.10 reserves Map for a mapping U.Method.

Reopen this choice if the named family becomes such a Method, ceases to concern one edition’s reconstruction inputs and routes, FPFCoreReferenceScheme or the local-sense claim changes, a direct consumer needs another distinction, or a narrower admitted record kind covers every current field and use.

Current FPF practical-entry declaration. Apply E.11’s content test to every proposed example. The current English FPF Readme declaration is:

Semantic keySelected public form
NAMINGOrdinary practical entry
SYSTEM-RECOGNITIONOrdinary practical entry
TIMEOrdinary practical entry
CAUSAL-USEOrdinary practical entry
MEASUREMENTOrdinary practical entry
MATHEMATICAL-MODELINGOrdinary practical entry
LIVE-WORK-STEERINGOrdinary practical entry
METHOD-RECOVERYOrdinary practical entry
METHOD-CONSTRUCTIONOrdinary practical entry
WORK-OPPORTUNITYOrdinary practical entry
PROFESSIONAL-RESULTOrdinary practical entry
UNFAMILIAR-THEORYPractical-Use Card
PHYSICAL-RESULTPractical-Use Card
ARCHITECTUREPractical-Use Card
PRACTICE-ARCHITECTUREPractical-Use Card
WORKING-DOCUMENTSPractical-Use Card
COMMUNICATION-FOR-USEOrdinary practical entry
OPTION-COMPARISONPractical-Use Card
RESULT-TO-NEXT-MOVEOrdinary practical entry
ACTUAL-TEMPORAL-STRUCTUREOrdinary practical entry
CONSEQUENCE-BEARERSOrdinary practical entry
PROBLEM-SHAPINGPractical-Use Card
IMPROVEMENTPractical-Use Card
WORDINGPractical-Use Card
SOTA-PORTFOLIOPractical-Use Card
SYSTEM-DELIMITATIONPractical-Use Card

Use this declaration as the sole list of selectable keys and their ordinary-entry or card forms when authoring, assembling, or validating the Readme. The Readme must return a reader whose question fits no example to the Table of Contents, another finding aid, or the direct patterns. Any additional coverage correction follows E.11.PFP:4.3.

Four related questions can be recovered without a separate selectable entry for each: CAPABILITY-DEVELOPMENT is carried by PRACTICE-ARCHITECTURE and IMPROVEMENT; COSTLY-ACTION is carried by OPTION-COMPARISON; DESCRIPTION-USE is carried by WORKING-DOCUMENTS; and DPF-AUTHORING is carried by SOTA-PORTFOLIO.

UNFAMILIAR-THEORY connects recovering a construction and argument with transfer to the project’s representation. PHYSICAL-RESULT connects physical modeling, mathematics, computation and realization, including returns when one contribution changes. Their mantras retain those dependencies while the direct patterns supply the operations.

WORK-OPPORTUNITY starts at the first missing contribution and can end at a local result, an exact gap or continued work without advice. Follow each linked pattern when its condition arises. The route does not require all of them. The Readme presents WORK-OPPORTUNITY as an ordinary entry.

TIME, CAUSAL-USE, MEASUREMENT, and MATHEMATICAL-MODELING are ordinary examples because each starts with one direct pattern and can stop at its first useful result without a cross-pattern mantra. No MODELING-FOR-ACTION card joins them.

LIVE-WORK-STEERING and METHOD-RECOVERY are ordinary examples for the same reason: each begins at one direct pattern and may stop at its first useful result or blocker.

PROFESSIONAL-RESULT is also ordinary: it starts with A.15.9, tests an already-available result before any new request, and can stop at bounded reuse, the smallest missing-result request, or a blocker without a cross-pattern mantra.

COMMUNICATION-FOR-USE starts with the communication and its intended use. Its ordinary explanation distinguishes interpretation, response, later action and effect, then opens a wording, representation, evidence, causal or repair question only when that question is needed. The reader can stop at a supported use or an explicit blocker.

RESULT-TO-NEXT-MOVE starts with the obtained result and its direct pattern. Its ordinary explanation preserves the conditions for a later interpretation, reliance, characterization, comparison or live-choice question and stops before taking up a question that is not current for the result or its receiving use.

CONSEQUENCE-BEARERS starts with the bounded consequence account under A.1.CSD. Its ordinary explanation retains the boundary challenge, conditional systemhood check, separate obtaining and modal paths, each bearer’s changes and uncertainty, and the return when the receiving use changes.

ACTUAL-TEMPORAL-STRUCTURE starts with what the temporal claim concerns. Its ordinary explanation distinguishes actual subjects and obtaining relations, a selected structure and its account, and future specifications or representations. A coordination trial follows only when it can change the decision and warrants its burden; otherwise the reader stops at the supported answer or missing basis.

PUBLICATION-FORM and DPF-SUITE-REFERENCE point readers to E.11.PFP and E.11.DSG without adding selected examples. Those patterns supply the detailed content. The Readme carries only the recognition, cross-pattern dependency, and return needed for discoverability.

For every card row, keep the card and its practical-use guidance findable by the same key. The current English FPF counts whitespace-separated tokens and requires at most 80 for a card mantra and 220 for a complete compact card. Neither limit sets a minimum.

These token ceilings are calibrated publication limits for this English FPF, not psychometric thresholds or universal DPF, LPF, or translated-publication limits.

Reopen the smallest affected declaration row and consumer when a cold-reader replay loses a choice-changing distinction, a useful card cannot fit without copying direct-pattern apparatus, or either ceiling can be lowered without losing use value. The optional @FPFReadme support records may carry FPF links but do not define shared conformance.

Create the FPF edition rebuildability record with this shape when FPF is being assembled, republished, exposed, or evaluated:

FPFEditionRebuildabilityRecord:
  recordRef: <exact rebuildability-record identifier>
  firstPrinciplesFrameworkEditionRef: <FPF edition named by value>
  firstPrinciplesScopeRef: <transdisciplinary scope and non-domain boundary>
  selectedCorePatternSetRefs: <exact selected complete pattern-source refs or declared sections of an accepted source edition>
  selectedFirstPrinciplesProblemSituationRefs: <recurring cross-domain problem situations and forces rendered by the edition>
  selectedFirstPrinciplesSolutionMoveRefs: <reusable solution moves, consequences, and repair routes rendered by the edition>
  selectedPublicationUnitRefs: <selected FPF content-unit refs, for example: public opening | standalone Readme | Architectural Reference | ToC | pattern-body collection | card set>
  selectedPublicationFormRefs: <exact reusable formation or arrangement rules selected for named uses>
  selectedPublicationExpressionRefs: <independently identified expressions of the selected edition for those uses, with any selected-form conformance>
  selectedPublicationCarrierRefs: <U.EntityRefs to independently identified carriers whose actual states or realizations yield the selected public expressions, for example: all-in-one Markdown file | PDF volume | website snapshot | split-file bundle>
  selectedAccessCarrierRefs: <U.EntityRefs to independently identified carriers whose actual states or realizations yield access-facing expressions, for example: skill-pack bundle | retrieval-index file | response document>
  selectedAccessRouteRefs: <identified services or routes, for example: MCP service | retrieval route | search function | assistant integration>
  relationAndEditionRefs: <direct relation and edition assertions, including edition pins and dependency boundaries; E.4.PFR rows only for a named maintenance consumer>
  firstEntryAndProjectionRefs: <E.11.PFP, E.11, E.17, Readme, Architectural Reference, ToC, and other contribution or projection loci>
  publicationSelfRenderingRefs: <statements in selected publication units of reader, selected first-principles structures, deliberate coarsening, abstraction, omission or deferral, and return to subject patterns, for example: Readme | Architectural Reference | ToC>
  qualityAndImprovementRefs: <E.2.DA for FPF-level adequacy; E.21, E.23, and E.9.DA as evidence or local routes>
  currentnessAndRefreshRefs: <G.11 plus exact source-use and currentness records>
  blockedOverreadRefs: <optional exact refs to explanatory guards admitted by F.19:4's plausible-reader and grounded-contribution test>

firstPrinciplesFrameworkEditionRef resolves to the edition record for the selected FPF edition; relationAndEditionRefs resolves that edition’s status and dependency assertions. Keep DPF and LPF package records outside this record. The rebuildability record supplies reconstruction inputs. Base downstream assembly and use claims on their direct results and relations.

Use E.24.PUB to distinguish each expression from the reusable form whose rules it follows. Recovering the expression from the independently identified carrier supplies the basis for the expression-bearing claim. A continuing file, an immutable snapshot value and an individual copy have different identity rules. A route or filename alone settles none of them.

A form-mediated expression or bearing claim retains its existential expression witness, and combined availability requires the same witness.

Use these steps for the FPF edition:

  1. Identify the FPF edition or candidate by its stable designation and the record for that edition.

  2. State the first-principles scope: FPF supplies transdisciplinary distinctions that can be reused across domains. Domain doctrines remain with their DPFs; the declared scope sets the useful coverage boundary.

  3. Identify the selected Core pattern set and any companion or projection loci that expose it.

  4. When a public presentation carrier is being assembled or checked, use E.11.PFP for the common publication form. Keep a product-declared compact opening and separate exact title and Readme H1 values.

    Represent Readme and Architectural Reference in the product’s established ToC grammar before one logical pattern index. Keep one selected practical-entry set with E.11.PFP:4.3’s entry guidance and unmatched-question return, five-field ordinary examples, six-field selected cards, and one integrated source-hazard plus rendered-structure check.

    Apply E.11’s use test before assigning card form, and use the current FPF declaration above for every selected key and form plus the English reading-burden measure and two limits. Add another public cue only when a named reader decision or action needs it.

    For the established all-in-one FPF carrier, add Readme through the same non-pattern table grammar already used for Architectural Reference, preserve the compact pre-ToC shape, and keep the exact line-position and native-ToC assertions in the builder regression. Keep FPF-specific source selection, body order, and assembly here; the carrier and form remain separate from the FPF edition.

  5. Readme, Architectural Reference, ToC, the public opening, cards, and the pattern collection are publication units. Reusable rules for arranging them supply the publication form. Identify the particular expression of the selected edition that follows those rules.

    Name the physical or digital carrier—for example, a managed Markdown file, site snapshot, PDF volume, split-file bundle, skill-pack bundle, index file, or response document—under its own domain identity rule and establish that its actual state or realization yields that expression.

    Record an MCP service, retrieval route, search function, or assistant integration as an access route. Name any returned carrier separately. Record these units, expressions, forms, carriers, and routes as distinct subjects and relations for the FirstPrinciplesFrameworkEdition.

  6. State relation, dependency, edition, deprecation, supersession, publication, and access claims directly. Open an E.4.PFR row only for a named maintenance consumer.

  7. DPFs and local practice frameworks may depend on FPF Core. Incorporate an accepted transdisciplinary contribution through a deliberate Core amendment before Core uses it. The amended Core supplies that contribution without depending on the DPF or local framework.

  8. Complete the FPFEditionRebuildabilityRecord with exact selected source, publication-unit, publication-expression, publication-form, presentation-carrier, access-route, relation, practical-entry declaration, currentness, and refresh references. Use that one declaration of keys and card assignments for Readme assembly and its checks. Do not add a competing manifest or duplicate the rebuildability account.

  9. Assemble the all-in-one edition candidate from the exact predecessor, the selected edition record, the matching FPFEditionRebuildabilityRecord, and every selected complete pattern source. Give each replacement or insertion an explicit boundary. Derive the logical index and pattern bodies from the same selection, verify one index row per selected PatternID, report which source supplied each assembled unit, and verify that every unselected predecessor span is unchanged.

    A missing or duplicate record, unresolved ref, index/body mismatch, ambiguous boundary, source mismatch, or changed unselected span stops construction.

    The construction result reports the assembled candidate and source correspondence. Acceptance and publication require their separate decisions and relations. Keep repository paths, commands, helper options, template names, and insertion syntax in maintainer documentation or the selected tool’s help.

  10. When the assembled publication claims accepted-source integration or continuity with its predecessor, use E.4.PFIP for that comparison.

    For whole-FPF adequacy, use E.2.DA over the scoped FPF object and declared use. Use E.21 for individual pattern bodies, E.9.DA for a DRR, and E.4.DPF.DA only for DPF or local-framework packages.

  11. For first entry and reader-facing exposure, use E.11 and E.17. Keep the Readme and ToC concise enough for entry. Develop the Architectural Reference enough to explain the whole and the connections needed to select, combine and adapt its contributions. Definitions and separately selectable Methods retain their subject-pattern owners.

  12. In the FPF Readme, Architectural Reference, and ToC, state the reader and use they serve, which first-principles structures they foreground, what they deliberately coarsen, abstract, omit, or defer, and where the reader returns for subject-pattern detail.

    Use E.11.PFP for the common publication-form structure. Preserve the product-declared compact opening, put the direct Readme/Architectural Reference route before the logical pattern index, and keep source paths, digests, machine identity blocks, candidate records, and build instructions outside reader front matter.

  13. For source-front, currentness, and refresh claims, use the direct source and currentness assertions under G.2 and G.11. Publication units, forms, presentation carriers, and access routes contribute only their stated publication or access facts.

  14. For skill packs or MCP-backed access, expose edition identity, dependency boundary, and currentness or refusal conditions. Distinguish the exact skill-pack, index, or response carrier from the service or route that returns it.

    Use C.35 for generated candidate text intended for architecture use. Keep tool capability and Work claims separate, using the applicable tool pattern for the former and A.15 plus the pattern for the exact Work for the latter. Use the applicable patterns for assurance, evidence, and decision-authority claims.

Choose the pattern for your question:

Live questionUse
“What is the form of FPF, and how are publication units, forms, presentation carriers, and access routes separated from the framework edition?”E.4.FPF
“Which public title and edition cue, unit order, logical index, and practical Readme entry form should this FPF publication use?”E.11.PFP
“How is this all-in-one FPF edition candidate rebuilt from its selected sources without changing unselected predecessor content?”E.4.FPF; use E.4.PFIP when accepted-source integration or predecessor continuity is claimed
“Does this whole-FPF object realize the Pillars for a declared use?”E.2.DA
“How do FPF, a DPF, and a local framework depend on one another?”E.4. State the dependency. Use E.4.PFR only for a named maintenance consumer
“How do we author a domain or local framework grounded in FPF?”E.4.DPF
“Is this DPF package good enough for one declared domain or local use?”E.4.DPF.DA
“Is this individual pattern body good enough?”E.21
“How do new users find and read FPF?”E.11 and E.17

E.4.FPF:5 - Archetypal Grounding

Edition revision. A later FPF edition updates its public front, Readme, Architectural Reference, ToC, and several pattern bodies. The FPF edition rebuildability record names one scoped edition, lists its Core pattern set, publication units and forms, exact presentation carriers, and access routes, records which entry text is only a projection, and points to E.2.DA for whole-FPF adequacy. It records Readme and Architectural Reference as publication units. Naming a presentation carrier requires the PublicationExpressionBearingRelation to its expression. When that expression conforms to the selected form, it also witnesses PublicationFormBearingRelation.

Domain framework. A domain principle framework for one practice depends on FPF Core and may cite architecture, representation, precision, and improvement patterns from FPF. Its publication units, forms, exact presentation carriers, and access routes belong to that DPF edition. Use E.4.DPF.DA to assess that package. FPF Core retains its transdisciplinary scope and its own amendment route.

Skill-pack access. An FPF skill pack exposes pattern lookup, first-entry guidance, and short-use prompts. A versioned skill-pack bundle can supply an access-facing carrier when its independently identified actual state or realization yields the selected expression. The service, endpoint, or assistant integration that returns it is an access route. Their descriptions name the FPF edition they expose and its refresh condition. Authority claims return to the named subject pattern and edition.

E.4.FPF:5.1 - Rebuild an edition and catch a boundary error

A steward is preparing Cedar 2, a fictional FPF edition for engineers who start from a working question. Cedar 1 is its frozen predecessor. The example follows three changed bodies inside the full edition; all other bodies must carry forward unchanged.

The accepted complete sources are DUA-2 for C.11.DUA, PUR-2 for E.11.PUR, and Ways-1 for C.39. DUA-2 replaces DUA-1 and includes continuing without optional advice. PUR-2 replaces PUR-1 and distinguishes applicability from recommendation. Ways-1 adds the method-development contribution between the existing C.38 and C.40 bodies.

Readme R2 adds their practical entry. Architectural Reference P1 remains unchanged.

The first useful result is rebuildability record RC2, which gives the assembler the following inputs and boundaries:

Record contentFilled value
Edition and scopeCedar 2; transdisciplinary FPF Core for the same reader and use as Cedar 1
PredecessorThe complete Cedar 1 text, including Readme R1, Architectural Reference P1, index I1 and body collection K1
Selected complete sourcesDUA-2 replaces the whole C.11.DUA body; PUR-2 replaces the whole E.11.PUR body; Ways-1 inserts the whole C.39 body after C.38 and before C.40
Publication unitsOpening O2, Readme R2, unchanged Architectural Reference P1, derived index I2 and body collection K2
Publication formsA book arrangement: compact opening, contents and index, Readme, Architectural Reference, then bodies; a standalone Readme arrangement using R2
Particular expressions and carriersCedar-2-book-expression, the ordered Unicode text of the assembled Markdown, borne by managed file object Cedar-2-book-a; Cedar-2-readme-expression, the ordered Unicode text of the rendered HTML source, borne by managed file object Cedar-2-readme-a
Access carrier and routeNone selected for this assembly
Reader-facing scope accountO2 names engineers and their working questions; R2 offers starting examples and returns to the bodies; P1 explains the wider reasoning practice
Source and adequacy resultsQ-DUA-2, Q-PUR-2 and Q-Ways-1 cover the three accepted source editions. Cedar 1’s whole-edition assessment A1 does not assess Cedar 2
Reconsideration conditionA selected source, predecessor span, declared form or receiving use changes

Each carrier’s actual state yields its named expression. Each expression follows the corresponding reusable arrangement rules and expresses the selected content. Neither file is the edition itself. The standalone HTML expresses R2 without becoming another independently authored Readme. No access service has been selected.

Assembly replaces the two bounded bodies, inserts Ways-1, and derives I2 from that same membership. I2 must contain one row each for C.11.DUA, E.11.PUR and C.39, with no duplicate C.39 row. C.39 is the only addition to the body inventory. All other membership and order stay as in Cedar 1.

A first candidate has exact copies of DUA-2, PUR-2 and Ways-1 and the expected index, yet fails the predecessor comparison. The Readme replacement ended two sentences inside P1 instead of at its boundary. The lost predecessor text was: “Start from your working question. Stop when the answer is sufficient; the entry list is not a required sequence.” The candidate has lost useful stopping guidance although every selected body matches its source.

The complete predecessor comparison exposes that unselected deletion. Stop the assembly at this failed preservation condition. Correct the Readme boundary and restore both sentences from frozen P1. Do not rewrite the accepted pattern bodies. Rebuild and repeat source correspondence, the full inventory and the complete publication comparison.

In the repaired candidate, DUA-2, PUR-2 and Ways-1 match their selected sources, I2 and K2 agree, R2 appears in both selected carriers, and P1 and every other unselected predecessor span are unchanged. The remaining differences are the two declared body replacements, one insertion and index row, R2 and its opening references. That is a completed construction with a stated preservation result under E.4.PFIP. Acceptance, publication and whole-FPF adequacy require their own conclusions.

E.4.FPF:6 - Bias-Annotation

Scope: This pattern covers the publication units and forms, assembly, exact presentation carriers, access routes, and whole-framework evaluation route of an FPF edition. Repository layout, assembly tool, carrier split, and publication service remain implementation choices. A one-sentence repair that leaves these FPF-level values unchanged uses its direct wording and source route.

LensLikely driftRepair
GovA successful assembly or form check is read as acceptance, publication, availability, currentness, or adequacy.Keep construction results separate from the decisions and relations that establish those claims.
ArchThe current all-in-one layout, source tree, or helper is treated as the only possible FPF architecture.Preserve edition, selected Core, publication-unit/form, presentation-carrier, access-route, index/body, and unchanged-content invariants while allowing another repository, tool, carrier split, or publication service.
Onto-EpistThe edition, one publication unit, its particular expression, the form whose rules that expression follows, the presentation carrier bearing that expression, an access route, the rebuildability record, the assembly Method, and performed assembly Work collapse into one object.Name them separately where the distinction changes the claim. The record describes reconstruction inputs and routes. The assembly Work is the construction occurrence. The edition contains the coordinated framework content. An independently identified physical or digital carrier bears the particular expression.
PragEvery small source edit is forced through FPF-level assembly paperwork, or exact source return is omitted to save effort.Use this pattern only when FPF publication units, form, carriers, access routes, edition assembly, or whole-FPF evaluation are at issue. Keep the record minimal while retaining complete selected sources and unchanged-predecessor protection.
DidBuild apparatus meets the reader before a working question, or a smooth front hides where authoritative pattern content resumes.Apply E.11.PFP to the reader-facing opening and keep paths, commands, digests, and diagnostics in maintainer evidence or tool help.

E.4.FPF:7 - Conformance checklist

CheckPassing condition
CC-FPF.1 Edition namedThe scoped FPF edition or selected FPF object is named by value.
CC-FPF.2 First-principles scope explicitThe text states that FPF is transdisciplinary first-principles material, including cross-domain problem-situation and solution-move architecture. Domain and local framework subjects use their own editions.
CC-FPF.3 Core, units, forms, carriers, and routes separatedCore pattern set, publication units, publication expressions, reusable publication forms, exact physical or digital carrier entities, access routes, relation records, source and currentness records, and quality records remain distinct.
CC-FPF.4 Dependency direction protectedDPFs and local frameworks may depend on FPF Core. A transdisciplinary contribution enters through a deliberate Core amendment whose content no longer depends on the DPF or local framework.
CC-FPF.5 Quality route correctWhole-FPF adequacy uses E.2.DA. Use E.21 for individual patterns, E.4.DPF.DA for DPF packages and E.9.DA for DRRs.
CC-FPF.6 Publication purpose and authority preservedReadme, ToC and cards support entry. The Architectural Reference explains the whole and its connections. Each returns subject definitions and separately selectable Methods to their pattern owners. An independently identified carrier and an actual expression-bearing relation support each carrier claim.
CC-FPF.7 Access carrier and route boundedEach named access carrier is an independently identified physical or digital entity whose actual state or realization yields a particular access-facing expression; any selected reusable form constrains that expression separately. MCP services, retrieval and search routes, and assistant integrations are recorded separately and expose edition identity, currentness, and refusal conditions. Framework authority, runtime dependency, work permission, and actual access claims use their own direct predicates and evidence.
CC-FPF.8 Refresh relation visibleSource-front, edition, entry-use, currentness, and evaluation changes identify the affected assertion and exact subject pattern, such as G.2, G.11, E.2.DA, or E.21.
CC-FPF.9 Unit, form, and carrier boundary visibleEach Readme, Architectural Reference, ToC, or equivalent FPF publication unit states the reader and use, the first-principles route it foregrounds, what it coarsens or leaves out, and where subject-pattern detail resumes. The selected publication form constrains how an expression arranges those units; an independently identified all-in-one Markdown file or other carrier bears that expression without exposing build metadata as reader front matter.
CC-FPF.10 Common form reusedThe selected public form satisfies E.11.PFP for the compact product-declared opening, distinct exact title and Readme H1, Readme and Architectural Reference entries in the established ToC grammar, one logical index, practical entries, and any choice-relevant cue. This pattern retains FPF-specific sources, units, body order, carrier and route selection, and builder regressions for the established compact-front line shape and native ToC grammar.
CC-FPF.11 One rebuildability record sufficientOne FPFEditionRebuildabilityRecord carries the exact selected source, publication-unit, publication-form, presentation-carrier, access-route, relation, projection, and refresh references. Add another manifest, field, or record only after showing which FPF value is missing.
CC-FPF.12 Deterministic source assemblyThe all-in-one edition candidate uses the exact predecessor, selected edition record, matching FPFEditionRebuildabilityRecord, selected complete pattern sources, and explicit replacement or insertion boundaries. Use one selection for the index and bodies, report source correspondence, and preserve every unselected predecessor span. Any identity, source, index/body, boundary, or preservation mismatch stops construction before an acceptance or publication claim. Repository filenames, commands, helper options, and template syntax remain in maintainer documentation or tool help rather than this reusable rule.
CC-FPF.13 One practical-entry declarationOne current FPF declaration covers all selectable Readme examples, assigns each exactly one ordinary-entry or card form, and supplies the same calibrated 80-token mantra and 220-token compact-card whitespace guard to authoring, assembly, and validation. The Readme introduces the ordinary entries and cross-pattern cards selected by the declaration in §4, returns unmatched questions to a finding aid, and applies E.11.PFP:4.3 to any coverage correction. Every card passes E.11’s mnemonic-gain test, remains linked by key to its guidance and optional expansion, and returns to its direct patterns. Authoring, assembly, and validation consume this declaration as the sole source for key, card, and coverage assignments.

E.4.FPF:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhat failsRepair
FPF as one DPFFPF is treated as a domain package, so its first-principles and transdisciplinary burden disappears.Use E.4.FPF for FPF form and E.4.DPF only for domain or local dependents.
Unit, form, route, or carrier as FPFA Readme, Architectural Reference, ToC, logical index, publication form, all-in-one file or site, split-file bundle, skill-pack bundle, or MCP route is treated as the framework edition itself—or a publication unit or access route is called a carrier without an independently identified carrier and actual expression-bearing relation.Record units, forms, exact presentation carriers, and access routes in their separate FPFEditionRebuildabilityRecord fields; keep authoritative claims in the Core patterns and their edition relations.
Rival FPF manifestA DPF or LPF FrameworkPackageManifest or a duplicate unit, form, carrier, or route field is copied into FPF even though the rebuildability record already names the needed sources, publication units and forms, presentation carriers, access routes, projections, relations, and refresh route.Use the FPFEditionRebuildabilityRecord fields and the assembly result. Reopen this decision only when you can show which FPF value is missing.
Rival practical-entry declarationReadme authoring, assembly, and validation keep separate ordinary-entry, card, scope, or limit lists, so the same key can change form or disappear without one reviewable change.Consume the single current FPF declaration in E.4.FPF. Change it only after the E.11 reader-use comparison and propagate that one change to the places that use it.
Directly patched all-in-one carrierSelected sources are correct, but the assembled carrier is edited outside the declared source assembly, so a mismatch or lost predecessor span can be hidden.Assemble from the exact predecessor and complete selected sources with explicit replacement or insertion boundaries; stop on any source, index/body, boundary, or preservation mismatch.
Repository recipe as framework lawOne helper, path layout, template set, insertion syntax, or campaign identifier becomes part of the public FPF Method.State the semantic assembly invariants here; keep the current implementation recipe and examples in maintainer documentation or tool help.
Invisible FPF entry routeReadme or Architectural Reference helps adoption but never says what first-principles structures it foregrounds, what it leaves to the pattern bodies, or who it is written for.Add a publication-unit structure account with the explanation needed for its reader’s use, preserving subject-pattern authority and keeping form and carrier claims separate.
Build apparatus as FPF front doorGenerated-source comments, candidate records, digests, source paths, or machine identity fields appear before the reader can find a working question, or a new profile shifts an established compact ToC merely to display them.Preserve the compact reader opening and direct Readme-first route; keep reproducibility and exact edition evidence in maintainer or package records, and project another cue only when its possible values change a named reader action.
Whole-FPF quality by local scoreGood E.21 values or successful landing are treated as whole-FPF adequacy.Run E.2.DA for the scoped FPF object and declared use; use local results only as evidence loci.
DPF reverse dependencyA good DPF discovery is treated as a hidden Core dependency.Propose a Core amendment that establishes the transdisciplinary contribution in Core, and update the affected Core patterns and edition relations while preserving dependency direction.
Access route as authorityA skill, MCP endpoint, retrieval index, or assistant integration is read as source, decision, work, or currentness authority, or the route is silently treated as the carrier it returns.Record an exact skill-pack, index, or response carrier only when one exists; keep the service or route separate and route generated text, tool work, evidence, assurance, and refresh claims to their subject patterns.

E.4.FPF:9 - Consequences

Authors can reproduce an FPF publication by building its Readme, Architectural Reference, ToC and pattern-body units, arranging them in all-in-one or split forms, and publishing them through identified files, sites, volumes or bundles. Skill, MCP, search or retrieval access can expose that publication while keeping edition, publication and access claims distinct. The same declaration keeps FPF’s few direct and cross-pattern examples, their forms, and the two reading-burden limits aligned across authoring, assembly, and validation. The selected examples show how to use the pattern language, while the unmatched-question return keeps further discovery available.

Stewards face an extra distinction: whole-FPF form differs from DPF authoring, package adequacy, individual pattern quality, and first-entry publication. The extra work is justified because those problems require different evidence and can fail in different ways.

E.4.FPF:10 - Rationale

FPF carries transdisciplinary first-principles distinctions that can seed and discipline many domain and local frameworks. Those frameworks supply their domain or local subjects and practices.

These cross-domain uses make FPF form an architecture concern. Separate publication units, forms, exact presentation carriers, access routes, and the framework edition so adoption work returns authority to the subject patterns. E.4.DPF.DA answers the DPF package question. Use E.21 for individual patterns and E.2.DA for whole-FPF adequacy.

E.4.FPF:11 - SoTA-Echoing

Practice questionBest-known lineSerious alternative or defaultDefect overcome and E.4.FPF mutationSource roles and limitsReopen condition
How can one authoritative framework-edition source produce several publication versions and access forms without identity drift or tool-specific framework law?RFC 9720, RFC Formats and Versions (2025), is the best-known-line candidate for this narrow publication-version question because one operating publication series distinguishes a definitive semantic version from rendered publication versions, seeks to preserve semantic content as fully as practicable while managing risk, and keeps controlled reissues and archives recoverable.Independently editing split and all-in-one publications, or treating Antora component-version and Sphinx toctree configuration as the framework’s identity and law.Separate editing drifts content and order; tool-defined identity hides the edition, publication unit, form, carrier, and route distinctions. Adapt: FPFEditionRebuildabilityRecord, the ordinary assembly method, Grounding, and CC-FPF.9–12 require exact source membership, one logical order, several forms, semantic-preservation checks, duplicate or mismatch stops, and recoverable prior versions. Reject: RFCXML, Antora component ontology, Sphinx toctree, repository conventions, and any production tool as universal FPF machinery.RFC 9720 qualifies as a candidate because it distinguishes definitive and rendered versions and aims to preserve content while managing risk. RFC status alone would not supply that ground. The linked Antora and Sphinx documentation are popular tool comparators only. Their release or maintenance status supplies no SoTA rank. The selected transfer does not prove unchanged content or whole-FPF adequacy.Reopen if a stronger current publication practice preserves exact source membership, index/body correspondence, semantic equivalence, and prior versions at lower reader or maintainer effort, or if an actual rebuild defeats this boundary.

The current practical-entry declaration and the internal FPF quality, dependency, carrier, and access-route rules are governed by the Solution, checks, and Relations. These internal rules do not supply external SoTA evidence about this pattern.

E.4.FPF:12 - Relations

  • Specializes: E.4 for work on the form of FPF.
  • Builds on: E.2 Pillars through E.2.DA for whole-FPF adequacy.
  • Coordinates with: E.4.PFR when a named maintenance consumer needs a reusable relation, edition, dependency, publication, access, deprecation, or supersession record. Otherwise state the relation.
  • Coordinates with: E.4.DPF and E.4.DPF.DA as sibling patterns for domain and local frameworks, not as FPF-level substitutes.
  • Coordinates with: E.11.PFP for the common framework publication form and with E.11, E.17 for first entry, projection, and publication or access use.
  • Coordinates with: G.2, G.11, C.33, C.34, and C.35 for source, currentness, structural preservation, and admission of generated or discovered results for architecture use.
  • Coordinates with: E.21, E.22, E.23, and E.9.DA when individual pattern quality, evaluation framing, improvement loops, or DRR adequacy provide evidence for FPF-level changes.

E.4.FPF:End

Referenced in the corpus

21 literal mentions in other sections. Read their context to establish the relation.