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

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 13:50:10 UTC

C.26.2:1 - Problem frame

Use this pattern when coordinated work, behavior, or trace patterns give evidence that a team, organization, service mesh, market, or other collective system is acting from a state that no single participant report, survey, policy sentence, dashboard, or API export faithfully carries.

The pattern supports only a minimal evidence-bound claim. It lets an author say that coordinated work, behavior, or trace patterns are consistent with a distributed-state reading during a declared window, while keeping the claim tied to carriers, probes, rival explanations, and export loss.

Working surfaceValue
Primary readerArchitect, incident lead, organizational analyst, or manager judging whether coordinated work, behavior, or trace patterns evidence a minimal collective-state reading.
Evidence-bound state readingAn evidence-bound state reading over a declared collective U.System.
Minimal state-reading moveInfer only the minimal carrier-bound and window-bound state claim, name rivals, and state export and probe limits.
Outside workGroup-mind ontology, survey-as-state, timeless culture claims, ordinary routine claims, and formal measurement not governed by C.16.
What changes in practiceThe team can use coordinated work, behavior, or trace patterns as evidence without pretending one report faithfully exports the whole state.

Plain glosses:

  • collective bearer: the declared team, organization, service mesh, market slice, or other U.System whose coordinated work, behavior, or trace pattern is being read.
  • coordinated work or behavior: role-work, service behavior, market participant traces, routine, commitment, artifact use, or coordinated action.
  • distributed-state reading: a minimal evidence-bound interpretation of coordinated work or behavior, not a new hidden group entity.
  • carrier: a log, trace, artifact, commitment, routine, dashboard, report, API response, or document that grounds but does not equal the state.
  • faithful-enough export: a representation good enough for the current decision; when it is not faithful enough, state what was lost and why.