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

Source changed 2026-11-19 22:26:44 UTC · snapshot created 2026-11-19 22:27:31 UTC · last check 2026-11-20 00:00:20 UTC

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.