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

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:13 - Bundle Anatomy and Member Discipline

A viewpoint-bundle library becomes thin and reusable only when the bundle itself stays stable while the member viewpoints remain explicit enough to review independently. The bundle therefore has two simultaneous obligations: coherence at the family level and clarity at the member level.

E.17.1:13.1 - What a viewpoint member should make explicit

Each U.ViewpointRef member inside a reusable bundle resolves to one exact viewpoint episteme edition whose claim content makes explicit at least:

  • the concern family it brings into focus,
  • exact stakeholder or audience referents only when they change the concerns,
  • the exact target-kind criterion it carries and the compatibility condition under which this family can reuse it,
  • the independently admitted episteme kinds whose exact membership rules allow candidates under that viewpoint,
  • any bundle-specific conformance notes later users must retain, plus an exact reference that resolves to the comparison claim or F.9 Bridge when either has independently been established; a note or reference creates no correspondence.

E.17.1 does not redefine the internals of U.Viewpoint. It states what must remain visible if a viewpoint is to be reused as part of a bundle rather than as an undocumented local label.

E.17.1:13.2 - Bundle-level coherence

A bundle is not just a bag of viewpoints with one shared prefix. A coherent bundle should answer a recognizable family-level question, such as:

  • which engineering concerns are standard for holon description?
  • which governance perspectives are required for a service review?
  • which research-method viewpoints recur across inquiry reports?

If the member viewpoints do not share that family-level purpose, the result is not one bundle but an uncurated catalogue fragment.

E.17.1:13.3 - Thin bundles, rich annexes

E.17.1 intentionally allows bundles to stay thin. Rich companion material such as:

  • lexical discipline notes,
  • bridge overlays,
  • A.16 move-publication notes,
  • worked examples,
  • or SoTA references

may be linked through references that resolve under their applicable schemes to exact annex assets, with each reference’s local role stated. This preserves a stable declaration claim block while still letting reuse packages carry enough didactic material and review help.