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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:25:20 UTC

G.11:4.4.2 - GPatternExtension — G.11:Ext.DecayAndDebt

PatternScopeId: G.11:Ext.DecayAndDebt GPatternExtensionId: DecayAndDebt GPatternExtensionKind: DisciplineSpecific GoverningPatternId: B.3.4 (use-qualified currentness and interpreted planning debt) Uses: {B.3.4, G.6} ⊑ and ⊑⁺: ∅ Required pins, edition pins, and policy pins (minimum):

  • The receiving claim/use and the changed premise or applicable review condition, with source references where published.
  • FreshnessWindowDeclRef?, DecayPolicyIdRef? or EpistemicDebtBudgetRef? only when the adopted window, deterioration model or planning measure is used. Their source supplies the meaning; no default expiry or debt budget is required.
  • Exact dependent claims and uses actually affected, expressed as PatternScopeId for nongraph scope or PathSliceId[] for graph scope. Retain graph pins when an independently applicable profile requires them; carrier age alone does not select every use of that carrier.

RSCRTriggerKindIds: {RSCRTriggerKindId.FreshnessOrDecayEvent, RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.BaselineBindingEdit} Notes (wiring-only): B.3.4 determines what the trigger means for the use. Continue, narrow, refresh, suspend or an authorized exception remain available where warranted; no Refresh/Deprecate/Waive triad or automatic downgrade is introduced here. Currentness is not assurance of the underlying claim. Budget and priority logic apply only when their interpreted policies are used.