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:45:05 UTC

E.4:1 - Problem frame

This pattern helps FPF users, framework authors and stewards answer any of these questions as they create, extend or use an FPF-grounded pattern ecosystem. What belongs to FPF itself, to the FPF Core or to a domain or local framework? Which records carry relation and edition claims? Which patterns define publication, access, naming, source, currentness and quality work?

Primary EntityOfConcern: the FPF-grounded pattern ecosystem for one named ecosystem question. For a first answer, name the question and classify the likely case. Point to the pattern that addresses it, or state which distinction is missing. Open a complete ecosystem-architecture record only when the answer must settle durable architecture or support later reliance.

The distinction determines the next contribution: E.4.FPF handles the form of FPF itself; E.11 and E.17 handle first entry and publication; E.4.DPF handles domain or local framework authorship. Use §4.2 for a proposed Suite and §4.1 for support units and adjacent products.