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

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 06:10:20 UTC

A.10:10 - Older source text interpretation and neighboring-pattern notes

Treat legacy names such as manifest, creator, observer, symbol register, SCR, RSCR, MIC, verifiedBy, validatedBy, or evidence path as recovery prompts, not decisions about object kinds or current relations.

  • For a manifest or source register, recover what the claim selects: for example, claim-bearing content, a source register or service, a publication occurrence or form, a carrier, or a provenance description. Recover the source, edition, claim, and direct relations relevant to that use; the old name does not decide among these objects.
  • A creator, observer, producer, verifier, or maintainer participates as an admitted System only when the direct participation relation obtains. If dated Work is asserted, recover every precise performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 afterward only when precise assignment-bound attribution is current. Name any exact direct relation or A.6.1 binding used by the claim separately. Those labels and assignments supply neither participation, authority, nor responsibility.
  • A method-instantiation note is not work. Recover the exact U.Method, generic MethodDescription claims, dated occurrence, enactment, ordering, participants, and result separately.
  • A work result, measurement result, validation result, or verification result label requires the exact domain result and a separate C.2.1 episteme; the legacy field name establishes neither.
  • Read a resource roster’s actual claims about resources. Distinguish those claims from the resources and resource-use relations described, and from the carrier or provenance account through which the claims are encountered. Use C.2.1 or E.24.PUB when those distinctions change the use; an ordinary roster citation can remain ordinary.

When older text also claims approval, permission, gate passage, assurance, causality, comparability, representation, publication effect, or decision, use the pattern that defines or tests that additional claim and let A.10 retain only source recovery, provenance, bounded reliance, and contestability.