Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:45:04 UTC

E.17.AUD:4.4 - Kind and boundary

Treat one publication unit as a readable unit. Do not identify it automatically with:

  • the U.Episteme or episteme species whose claims the unit carries, quotes, or describes;
  • an EpistemePublicationRelation occurrence, publication form, or carrier involved in making that selected episteme available;
  • the primary subject, including the exact EntityOfConcern when applicable;
  • a generic publication face or MVPK face under E.17 constraints;
  • a carrier or evidence carrier;
  • proof, evidence record, assurance claim, or release admissibility;
  • a view or viewpoint;
  • an engineering-process stage;
  • a downstream decision, gate, work, or reliance publication.

Those objects may matter, but mentioning them in the same note, sheet, or screen does not make them the current publication-unit problem.

Publication-unit boundary choice. A PublicationUnit boundary is valid when a careful reader would naturally inspect that bounded item as carrying one primary publication move over one primary subject, with one visible outside boundary to work, work planning, decision, gate, reliance claim, or neighboring pattern application. Choose the bounded item that carries the claim being made or effect being repaired. Do not choose a smaller boundary merely to hide a downstream overclaim, and do not choose a larger boundary merely to absorb several primary subjects into one unit. A table row may be the unit when that row carries the claim; the whole table may be the unit when the table-level caption or comparison frame carries the claim. A dashboard tile, note, card, sheet, or screen block may be the unit only when that bounded item, not the whole carrier or interface, carries the live publication move.

Publication-unit snapshot identity. A PublicationUnit may remain the same bounded unit while its carrier rendering, export format, screenshot, or layout changes. It does not remain the same stabilized interpretation by visual or file continuity alone. If a revision, refresh, translation, regeneration, or dashboard update changes the primary subject, carried publication move, outside boundary, source pins, or admissible use, rerun the four-part interpretation for the new snapshot before the unit is used for comparison, explanation, evidence, gate, decision, work, or reliance claims.