FPF Reference

    Governing-source lookup table

    Preface node heading:governing-source-lookup-table:21833

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    Governing sources by required claim or effect kind:

    • cue-only orientation: use only for attention, learning, source-finding, or a reversible local probe trigger; stay with A.16, A.16.1, or A.6.A when those claims are being made.
    • issuing, approval, authorization, delegation, or revocation act: cite A.2.9 U.SpeechAct or SpeechActRef, including act type, actor and role assignment if claimed, affected work target or claim, judgement context, window, publication-carrier reference, evidence reference when currentness matters, and instituted effects if claimed. Because U.SpeechAct <: U.Work, it can evidence only that communicative act.
    • deontic permission, obligation, prohibition, or recommendation-as-duty: cite A.2.8 U.Commitment and the instituting SpeechActRef when provenance matters. If the word instead names claimed use boundary, gate passage, authorization act, role-assignment effect, status effect, credential status, cue, or advice, use the pattern that carries that kind named by value.
    • role-assignment or status reliance: cite A.2.1, U.RoleAssignment, a status-changing U.SpeechAct, a governing context-state record, a credential proof or status result under A.10, or an A.21 GateDecision when the status is gate-governed.
    • boundary, policy, API, schema, "allowed", "authorized", "approved", "recommended", or "guaranteed" wording: split the statement through A.6 or A.6.B; use A.6.C, A.2.3, A.2.8, and A.2.9 for agreement-like guarantee, SLA, or promise wording before work use or reliance use.
    • gate decision or gate passage: cite A.21 OperationalGate(profile), GateDecision, GateDecisionRationale, DecisionLogRef, gate profile, gate version, check set, scope, window, and replay or freshness pins.
    • U.Flow.ConstraintValidity witness: cite A.20 ConstraintValidity status, witness, GateCheckRef.aspect = ConstraintValidity, PathId or PathSliceId when applicable, window, sentinel, and pins when those fields are needed for the claim.
    • release, deployment, repair, inspection, or rollback work occurrence: cite A.15.1 dated U.Work occurrence and the A.10 evidence or provenance relation when reliance on occurrence is needed.
    • evidence, provenance, authenticity, currentness, copied-source, or generated-source relation: apply A.10 and name the claim-bound evidence path, currentness path, and relation-governed or blocked use.
    • assurance, readiness, safety, compliance, trust, release confidence, or R, F, G, or CL increase: apply B.3 and name the typed assurance claim plus its limitations and reopen condition.
    • generated explanation: use E.17.EFP for explanation faithfulness or source-finding relation, then require A.10 claim-bound source relation for every operative claim that will be relied on.
    • ambiguous approval, permission, or authorization wording: choose among the rows above named by value by asking what effect is claimed now: speech act, commitment, claimed use boundary, gate passage, role-assignment or status change, credential status, evidence relation, assurance claim, or work occurrence.

    Recovered source outputs for A.15.4 closure:

    Governing source relation usedRecovered output for this A.15.4 restorationA.15.4-local use
    A.6 or A.6.BTyped claim IDs (L-*, A-*, D-*, and E-*) plus the pattern that governs the claim being made or effect and the governing source for that claim or effect.Use for wording, boundary, API, schema, or use-boundary recovery before work or reliance use.
    A.10Claim-bound evidence path, freshness field, currentness field, and relation-governed or blocked use for the attempted claim.Use for evidence, provenance, authenticity, credential-currentness, copied-source, or generated-source recovery.
    B.3Typed assurance claim, no-assurance-use disposition, or rejected or downgraded assurance claim.Use only when the project move under repair relies on a typed assurance claim.
    A.21OperationalGate(profile), GateDecision, DecisionLogRef, gate profile, gate version, scope, window, and replay or freshness pins.Use for gate-passage reliance in the named scope and window.
    A.20ConstraintValidity status, witness, PathId or PathSliceId when applicable, window, sentinel, and pins when those fields are needed for the claim.Use for U.Flow.ConstraintValidity reliance.
    A.2.9SpeechActRef with act type, actor and role assignment if claimed, affected work target or claim, judgement context, window, and instituted effects if claimed.Use for issued acts and, where needed, dated occurrence of that communicative act.
    A.2.8U.Commitment deontic relation with accountable role assignment, agent, referents, modality, scope, effective window, and instituting source when needed.Use for deontic permission, obligation, prohibition, or recommendation-as-duty.
    A.15.1Dated U.Work occurrence plus A.10 evidence or provenance relation when relied on.Use for reliance on performed work.
    E.17.EFPExplanation class, source-finding relation, and faithfulness relation over the source U.Episteme or source U.EpistemePublication.Use for generated-explanation faithfulness and source-finding before operative reliance.

    High-impact work or reliance - especially external-impact, irreversible, release-bearing, role-assignment-bearing, status-claim-bearing, gate-bearing, compliance-bearing, safety-bearing, delegated, contested, or assurance-bearing claim or effect - may guide work only for the actor and role assignment, work or reliance claim under repair, work-relevant P2W claim under repair, P2W chain position under repair, affected work target or claim, audience, scope, environment, version, policy context, operational mode, and time window for which the required FPF-governed project source, relation, evidence path, gate decision, or assurance claim is recoverable. Cue-only, source-finding, learning, and bounded reversible probes stay lightweight and do not require a full source dossier. Quick dispositions:

    Encountered caseFirst A.15.4 disposition
    Source-backed release dashboard tileIf the tile is a current dashboard view of A.21 GateDecision or DecisionLogRef plus release scope or work target, environment, scope, window, gate profile, gate version, and A.10 evidence path, it may carry gate-passage reliance for that release and environment.
    Unsourced or stale release dashboard tileDisplay or source-finding only until the current GateDecision or DecisionLogRef, release scope or work target, scope, window, gate profile, gate version, and A.10 evidence path are recoverable; use B.3 only if an assurance claim is being made.
    Copied review summary or copied approvalCopied wording and copied-currentness cue at most; approval, authorization, permission, commitment, or work occurrence needs the original A.2.9 SpeechActRef, A.21 decision, A.2.8 commitment, or A.15.1 work source plus A.10 evidence.
    Delegation chain with forwarded approvalEach link names delegator, delegatee, delegated operation or work class, affected work target, affected resource, affected claim, scope, window, source permitting delegation, subdelegation allowance if any, revocation source, currentness source or currentness path, and evidence path. A forwarded approval is not delegated authority by copy alone.
    Role-assignment, revocation, or status displayResolve to role assignment, status-changing speech act, context-state record, credential proof or status result, or gate decision with freshness field, revocation source, or revocation record; visual status cannot defeat a higher-priority revocation or supersession source.
    Conflicting sourcesDo not resolve by color, visual salience, copied wording, or apparent recency. Name source order, governing decision source, freshness policy, and supersession rule; the work claim, reliance claim, or effect is contested until resolved, while source-finding and bounded reversible probes remain available.
    Credential badge or register-backed status viewUse the display as a publication of a credential source or status source, not the source itself. Find the governing status register or issuer, trust root, holder binding or subject binding, verifier context, relying context, proof or status result, revocation, freshness, and effective window. If the governing register entry itself creates or changes role assignment, status, permission, duty, or gate effect in the bounded context, cite that register or status-source entry named by value and the A.2.1, A.2.8, A.2.9, A.6.B, or A.21 source it depends on. Otherwise rely only on credential-currentness for that holder and context.
    Rollback command-like cueTreat as cue or A.6.A-governed invitation unless command record, authorization, work occurrence, performed-work result, or gate decision is recoverable.
    Generated explanation says "authorized"Explanation may help find sources; it does not issue, approve, revoke, commit, authorize, pass a gate, provide evidence for performed work, or raise assurance. A citation or source mention inside the explanation guides work use or reliance use only when the cited publication carrier carries that relied-on claim named by value in the relying context under A.10.
    Extracted source, rewrite, representation shift, explanation, then gate or release claimReopen the governing source at the first lossy or non-commutative transform step; the gate claim or release claim waits for the required transform record, evidence path, explanation relation, gate decision, or assurance claim.
    Repeated green-tile failures without recoverable source relationTreat recurrence as upstream source-relation repair work: expose decision refs, fix dashboard semantics, add source links and currentness, revise boundary wording, or add review cues so the acting user is not repeatedly forced to reconstruct missing source relation.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)