fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 94146–94177

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:35:20 UTC

E.17.1:16 - Authoring and Review Guidance

E.17.1:16.1 - For bundle authors

Bundle authors should ask:

  • what recurring family is being named,
  • which viewpoints truly belong together in that family,
  • what local didactic publications or examples belong in annexes instead of the bundle core,
  • and whether the bundle is stable enough to deserve a reusable family designator.

A good bundle is not maximal. It is coherent, reviewable, and reusable.

E.17.1:16.2 - For reviewers

Reviewers should inspect both levels:

  • member level - are the included viewpoints individually explicit enough to be reused?
  • bundle level - do they actually form one coherent family rather than one convenient list?

They should also check whether a local project has silently forked the bundle while still using the inherited family designator.

E.17.1:16.3 - For integrators and librarians

Integrators should keep libraries small, curated, and editioned. Publish only the smallest declaration set the current reuse needs:

  • one stable core declaration when a recurring family is established,
  • one explicit local extension only when local membership or meaning changes,
  • and one clear subset declaration only when the current use imports a subset.

Do not create all three by default. Library sprawl destroys the cognitive advantage that reusable bundles are supposed to provide.