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

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 12:30:19 UTC

C.26.2:4.8 - Well-formed EDSE record

A usable EDSE record has this shape:

EnactedDistributedStateEvidence(
  collectiveBearer = ...,
  boundary = ...,
  observedCoordinatedWork = ...,
  evidenceCarriers = ...,
  probeOrExport = ...,
  timeWindow = ...,
  persistenceSupport = ...,
  ordinaryRivals = ...,
  factorablePart = ...,
  coordinationResidue = ...,
  exportLoss = ...,
  minimalSupportedClaim = ...,
  boundedActionSupported = ...,
  unsupportedUse = ...
)

The syntax is illustrative. A decision-use record retains the distinctions on which its supported claim or action depends. For an explicitly momentary, local use, follow :4.11 and omit persistence, decay, or reprobe-cost detail when those values cannot change the claim or action.

Well-formedness constraints:

  • collectiveBearer is a declared collective system, not a metaphorical subject.
  • evidenceCarriers are inspectable publication units, traces, records, commitments, logs, or work-result records.
  • timeWindow bounds the claim; persistence beyond that window needs its own support.
  • ordinaryRivals include at least the principal policy, incentive, routine, shared stimulus, dashboard-following, copied-artifact, or social-desirability explanation that could explain the same coordination.
  • minimalSupportedClaim states only what survives after rivals and export loss are named.
  • unsupportedUse names the neighboring claim or use that the current claim does not carry without applying the neighboring FPF pattern governing that claim.