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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:35:20 UTC

A.6.C:4.5 — A.6.B Claim Register additions (recommended)

When stable reuse, decision, audit, dispute, or cross-face projection needs a record, use the A.6.B Claim Register (IDs, statements, quadrant, and canonical location). A one-off local repair ends with the repaired atomic prose. When the register is needed, add only the current A.6.C fields below without minting another record or ontology kind:

  • bundleId (optional local ID grouping atomic claims discussed together)
  • questionRef (optional pointer Q1, Q2, Q3, or Q4 to the four questions above; it selects no kind, subject predicate, or quadrant)
  • directObjectDesignation (use U.RelationRef constrained to the exact relation family for a relation occurrence, the applicable U.EpistemeRef for a whole episteme, or the admitted reference kind for another independently identified entity. When one claim inside an episteme is the direct object, use C.2.1 ClaimAddress: exact episteme-edition reference plus intrinsic claim identity declared by that edition’s ClaimGraph. The entity-reference branches designate independently identified objects; the claim branch designates content inside the named edition. Neither carries the designated content.)
  • directObjectPatternLocator (the exact pattern-description locator for the ClaimGraph that defines or constrains that direct object; it asserts no ownership relation)
  • faceRefs (optional mapping from PlainView, TechCard, InteropCard, or AssuranceLane to where this same claim is rendered)

Each row still uses the A.6.B fields for one exact statement, claim ID, quadrant, and canonical location. Do not create a second boundary-language record or a Permission, Utterance, WorkEvidence, or result-or-evidence umbrella kind.