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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:05:05 UTC

G.6:4.1 - Subject-pattern map

Represented claim or objectSubject pattern before G.6 represents it
Reusable method, generic participants, parameters, effects, and conditionsA.3.1 for the exact U.Method; A.3.2 for its U.MethodDescription
Independently admitted dated Work and its exact actual performer refs; optional obtaining F.6 relation and assignment occurrence refs when the path expressly consumes attribution; enactment, resources, and direct participation or binding factsA.13 for each exact actual performer and A.15.1 for independent Work admission; F.6 and A.2.1 only when the path represents precise assignment-bound attribution; the exact direct participation or resource relation; and A.6.1 for operation-application bindings
Production or inception of an entity or epistemeone exact local A.15.PROD claim when its entry condition is met, or a direct subject predicate under its own pattern
Measurement result and its measurement-specific basisC.16
Acceptance-clause application or other runtime evaluation resultG.4 or the exact formal, conformance, diagnostic, causal, comparison, selection, gate, or decision governor
Work-resource aggregation resultB.1.6
Durable episteme that states a local resultC.2.1; it remains distinct from the domain result
Outcome, later action, acceptance, gate passage, permission, or decisionits exact work and domain governor, including C.11 or A.21 when applicable
Source publication, carrier, copy, extraction, or publication occurrenceE.17 for a source-backed face and source return; E.24.PUB for an obtaining publication occurrence; the direct rule for each copy, extraction or source relation
Representation correspondenceC.29
Bridge, congruence, loss, or cross-context transferF.9
Transformation-flow structure distinct from performed workE.18 and E.18.2
First evidence/status use, provenance and bounded reliance, currentness, or assuranceA.2.4, A.10, G.11, or B.3 respectively

G.6 does not substitute for any row. If the subject pattern or relation cannot be recovered, the path records an unresolved gap and cannot present that edge as obtaining.

Do not add a local U.EvidenceRole or turn proof, measurement, benchmark, source, or status labels into system-role kinds. For any claim that a producer, verifier, laboratory, issuer, or maintainer participates, recover the exact direct relation, the participants it declares, and the place each actual participant fills. Other nearby facts—for example, a local system-role kind, assignment, Work occurrence, responsibility, authority, or permission—are separate and may be cited only when they independently obtain; none establishes participation. Do not infer that a passive laboratory or produced entity performs Work merely because the path cites it.

Work recovery and compact citation. Before G.6 represents dated U.Work, its subject account must already recover each exact actual performer through A.13 and admit that Work independently under A.15.1. Include an assignment occurrence and obtaining F.6 relation only when the graph path or receiving use expressly consumes precise assignment-bound attribution; any present attribution must use the same obtaining A.13 assignment. If a required Work or performer ref is absent, record a Work gap. If an expressly consumed F.6 ref is absent or unresolved, retain the Work node and record an attribution gap rather than suppressing the Work. G.6 neither re-admits the Work nor retests assignment species, occurrence identity, holder, classification, predicate duration, or interval coverage. Merely listing an assignment beside Work establishes no relation between them.