FPF Reference

    Governing-position lookup table

    Preface node heading:governing-position-lookup-table:23327

    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 patterns 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, acting holder, work-performing system, or agent, RoleAssignmentRef when role-conditioned authority is 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, role-state effect, credential-status effect, cue, or advice, use the pattern that carries that kind named by value.
    • role-assignment, role-state, credential-status, or context-state reliance: cite A.2.1, U.RoleAssignment, a state-changing U.SpeechAct, a governing context-state record, a credential proof or credential-status result under A.10, or an A.21 GateDecision when the state 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 intended work or reliance.
    • 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.
    • Flow constraint-validity 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 relation, currentness relation, and relation-governed or blocked use.
    • assurance, 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. If the word ready names full-kit or work-entry readiness, use A.15.5; if it names a gate decision, use A.21.
    • 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 effect, role-state change, credential-status change, evidence relation, assurance claim, or work occurrence.

    Recovered governing pattern outputs for A.15.4 closure:

    Governing pattern or relation usedRecovered output for this A.15.4 repairA.15.4-local use
    A.6 or A.6.BTyped claim IDs (L-*, A-*, D-*, and E-*) plus the pattern that governs the current boundary claim or the current effect-bearing claim.Use for wording, boundary, API, schema, or use-boundary recovery before intended work or reliance.
    A.10Claim-bound evidence relation, 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 work or reliance claim 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 flow constraint-validity reliance.
    A.2.9SpeechActRef with act type, acting holder, work-performing system, or agent, RoleAssignmentRef when role-conditioned authority is 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 holder, work-performing system, or agent, RoleAssignmentRef when role-conditioned accountability is claimed, referents, modality, scope, effective window, and instituting SpeechActRef or source relation 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 the U.EpistemePublication exposing that source relation.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, role-state-claim-bearing, credential-status-claim-bearing, gate-bearing, compliance-bearing, safety-bearing, delegated, contested, or assurance-bearing claim or effect - may guide work only for the acting holder, work-performing system, or agent, the RoleAssignmentRef when role-conditioned capacity or attribution is current, the 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-side source relation, evidence relation, gate decision, or assurance claim is recoverable. Cue-only, source-finding, learning, and bounded reversible probes stay lightweight and do not require a full evidence, currentness, or provenance dossier. Quick dispositions:

    Encountered caseFirst A.15.4 disposition
    Release dashboard tile exposing a source relationIf 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 relation, it may carry gate-passage reliance for that release and environment.
    Release dashboard tile without current gate or evidence relationUse the tile only for display or source-finding until the current A.21 GateDecision or DecisionLogRef, release scope or work target, environment or scope, time window, gate profile, gate version, and A.10 evidence relation are recoverable. Open B.3 only when an assurance claim is being made.
    Copied review summary or copied approvalCopied wording and copied-currentness cue at most; approval, authorization, deontic permission, commitment, or work occurrence needs the original A.2.9 SpeechActRef, A.21 decision, A.2.8 commitment, or dated A.15.1 work occurrence plus A.10 evidence or provenance relation.
    Delegation chain with forwarded approvalEach link names delegator, delegatee, delegated operation or work class, affected work target, affected resource, affected claim, scope, window, the delegation record or relation permitting delegation, subdelegation allowance if any, revocation relation, currentness relation, and evidence relation. A forwarded approval is not delegated authority by copy alone.
    Role-assignment, revocation, role-state, or credential-status displayResolve to role assignment, state-changing speech act, context-state record, credential proof or credential-status result, or gate decision with freshness field, revocation relation, or revocation record; visual display cannot defeat a higher-priority revocation or supersession relation.
    Conflicting source relationsDo not resolve by color, visual salience, copied wording, or apparent recency. Name source-relation order, governing decision record, 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 credential-status viewUse the display as a publication of a credential record, credential-status record, or role-state record, not the record or relation itself. Find the governing credential-status register, role-state register, or issuer, trust root, holder binding or subject binding, verifier context, relying context, proof or credential-status result, revocation, freshness, and effective window. If the governing register entry itself creates or changes role assignment, role-state, deontic permission, duty, or gate effect in the bounded context, cite that register or status record named by value and the A.2.1, A.2.8, A.2.9, A.6.B, or A.21 governing relation 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 source U.EpistemePublication refs, claim-bound source relations, or governing pattern positions; 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 intended work or reliance only when the cited publication carrier carries that relied-on claim named by value in the relying context under A.10.
    Extracted source publication, rewrite, representation shift, explanation, then gate or release claimReturn to the source U.EpistemePublication, source-bearing relation, transform record, evidence relation, explanation relation, or governing pattern position at the first lossy or non-commutative transformation operation; the gate claim or release claim waits for the required transform record, evidence relation, 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 claim-bound source relations 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-07-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)