C.26.2 - Enacted Distributed State Evidence

Type: Architectural pattern Status: Stable Normativity: Normative unless explicitly marked informative

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.

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.

C.26.2:2 - Problem

Teams often need to talk about latent alignment, readiness, market posture, service-mesh behavior, or an enacted “we already decided” before one explicit representation exists. Without a pattern, they oscillate between two bad options.

One option is unsupported collective-state language: “the organization knows”, “the culture decided”, “the market wants”, or “the service mesh understands”, used as if the wording established the state. The other option is false reduction: a survey answer, policy sentence, dashboard, or report is treated as the whole state.

Both fail. Coordinated behavior may evidence a real working state, but it does not automatically identify a durable mind, internal representation, causal mechanism, or faithful-enough export for the intended use.

C.26.2:3 - Forces

C.26.2:4 - Solution

Model the claim as evidence-bound U.Episteme over a declared collective U.System. Do not make the distributed state a bearer-independent thing. Do not treat a survey, dashboard, report, or API response as the state itself.

If the proposed bearer is a market slice or service mesh, declare whether it is a collective U.System, delivery system, trace population, or evidence set. Continue with EDSE only when a collective U.System bearer is established; otherwise retain any supported trace-population or evidence-set claim. Do not infer systemhood from coordinated-looking traces alone.

The primary evidence family is coordinated work, service behavior, market participant traces, work traces, and socio-technical evidence. Distributed cognition, routine dynamics, and team cognition supply the primary interpretive grounding. QL enters only when probe, frame, export, incompatible read, or carrier/export structure that is not faithful enough for the declared use changes the admissible state reading.

The canonical EDSE move is to separate the factorable part from the coordination residue before making the minimal state reading:

1. state what ordinary routines, policies, incentives, shared stimuli, dashboard-following, or copied artifacts explain;
2. state what the carriers show;
3. state what residue remains as a minimal state reading;
4. state what action this residue supports.

Start with this recognition note:

Use the fuller EDSE record below when the receiving claim or action needs distinctions that the recognition note does not retain. Reuse adequate existing content; publication, reuse, or leaving the immediate discussion alone does not require a fuller record.

Full EDSE record:

C.26.2:4.1 - Minimal claim principle

Preferred wording stays close to observed work:

• “During window W, the incident-response organization acted consistently with a rollback-readiness posture, evidenced by release timing, escalation criteria, and shared trace use.”
• “The service mesh exhibited a coordinated throttling regime under policy P, evidenced by route changes and saturation traces.”
• “Market traces support an expectation-shift claim under probe Q, with media amplification still a rival explanation.”

Avoid wording that asserts a heavier claim, such as “the organization decided”, “the market knows”, or “the team has a distributed mind”, unless another FPF pattern and evidence requirement independently support it.

C.26.2:4.2 - Finish conditions

Finish with one of these results:

C.26.2:4.3 - Rival explanation rule

Before using this pattern, name the principal ordinary rivals:

C.26.2:4.4 - Export-loss discipline

The phrase “not faithfully exportable under current probe and bridge conditions” is supported only when the text says:

• what export was attempted;
• what would have counted as faithful enough for the current decision;
• what state, coordination, evidence path, timing, role alignment, option structure, survivor relation, or use limit was lost;
• whether the loss comes from bridge, measurement, representation, audience, timing, state change, or another cause;
• whether a more discriminating probe, bridge, representation, or time window could produce a higher-fidelity export.

C.26.2:4.5 - Compound-state decomposition card

When the distributed-state reading is load-bearing, state the decomposition explicitly. Its practical purpose is the canonical EDSE move: ordinary rivals first, carriers second, coordination residue third, admissible use or action invitation fourth.

C.26.2:4.6 - Evidence-bound state reading and claim floor

The evidence-bound state reading is an evidence-bound U.Episteme reading over coordinated work, behavior, or trace patterns by a declared collective U.System. The pattern does not govern an inner group entity, a culture substance, a market mind, a hidden service intelligence, or a reusable kernel state kind.

The minimal state-reading move is to turn coordinated work, behavior, or trace patterns into the minimal useful state reading while keeping the reading bound to:

• the collective bearer and its boundary;
• the observed work and evidence carriers;
• the time window and persistence support;
• the probe or export conditions;
• the ordinary rival explanations;
• the current export loss and higher-fidelity export possibility;
• the next neighboring FPF pattern if a claim requiring additional evidence is needed.

This pattern is useful because many real work states are enacted before they are articulable. A team may behave as if a release freeze exists before any single person states it cleanly. A service mesh may exhibit one routing posture before any one dashboard carries the whole situation. A market may shift expectations before any one survey faithfully exports the shift. The pattern lets FPF say that much, and no more, without pretending that one carrier is the state.

C.26.2:4.7 - Operational evidence sequence

Operational evidence sequence:

1. Name the collective bearer as a declared U.System and state its boundary; a bare social label does not establish that System.
2. Name the coordinated work, behavior, or trace pattern being read: actions, routines, commitments, role-work, service behavior, market participant traces, artifacts, or timing. For a precise Work claim, use the A.15 alignment route through A.13 and independent A.15.1 admission; add F.6 only when the receiving use needs precise assignment-bound attribution through the same obtaining assignment.
3. Name the evidence carriers through A.10 so the reading is inspectable.
4. State the time window, persistence support, decay/refresh condition, reprobe cost, and ordinary rival explanations.
5. Name the candidate state reading only as a minimal evidence-bound U.Episteme reading.
6. State the attempted export and what it lost.
7. State the minimal supported claim, the supported action or use it carries now, and the other uses that remain unsupported by this reading.
8. Add B.3 assurance only when an actual named assurance claim is current; QLP-3 requires that claim and a B.3 assurance result for the named QL target claim and receiving use. Consequence level, audit, release, or accountability use may also impose a direct domain requirement for that claim.

Required output: produce a minimal evidence-bound distributed-state reading, the time window that bounds it, the live rival explanations, and the supported bounded action or use that follows from that reading.

The pass is complete only when the resulting sentence states the collective-state claim supported by its named evidence. A good output sounds like:

During incident window W, the incident-response organization acted consistently with rollback-readiness posture P, evidenced by deployment queue changes, escalation messages, rollback artifacts, and support-routing changes; this reading is not faithfully exported by survey S because S loses timing, role-work, and trace linkage.

That sentence is narrower than “the organization decided”, but it is much more useful. It supports adjusting incident communication and release-triage posture during window W; it does not support a durable culture claim or release-readiness assurance claim.

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.

C.26.2:4.9 - Carrier, probe, report, and state split

The pattern keeps four objects separate:

A survey can be an evidence carrier and a probe. It is not the distributed state. A policy can be a carrier or a routine explanation. It is not automatically evidence that everyone shares one state. A dashboard can be a carrier, a probe, and a behavior-changing instrument. It is not automatically faithful enough for the intended use.

C.26.2:4.10 - Case bank and near misses

C.26.2:4.11 - Evidence posture and confidence

EDSE claims become useful when the text says how much consequence the evidence can carry.

Publication or reuse under unchanged assumptions does not by itself raise the evidence posture. Select additional support from the receiving conclusion under C.26:12b.

For QLP-0 or low-consequence QLP-1, do not force persistence, decay, or reprobe-cost fields when the claim is explicitly momentary and the bounded action is local. Name the bearer, carriers, window, minimal reading, rival, practical change, and local stop; add the fuller temporal fields only when reuse, contest, or consequence makes them load-bearing.

The ordinary EDSE claim is minimal but actionable. It says: “this coordinated work or behavior supports this bounded reading for this use.” It does not say: “the collective has one hidden durable state that a report can copy.”

C.26.2:5 - Archetypal Grounding

Tell: During an incident, several teams independently stop non-critical releases, reroute support, and prepare rollback evidence before any single manager issues a written decision. Later, a survey asks whether “we had decided to freeze release”, and answers conflict.

Show, System side: the collective bearer is the incident-response organization during a declared incident window. Its carriers include deployment logs, meeting records, escalation messages, rollback preparation, support routing, and release queue changes.

Show, Episteme side: the supported claim is minimal. The organization acted consistently with a release-freeze readiness posture during window W. The claim does not say every participant knew the same proposition or that the coordination exists apart from the declared evidence carriers. A management directive, playbook, or dashboard effect remains a rival unless evidence narrows it.

C.26.2:6 - Bias-Annotation

This pattern biases authors toward minimal evidence-bound claims and explicit evidence. That may feel conservative, but it makes distributed-state language usable.

It also biases authors to keep primary grounding in distributed cognition, team cognition, organizational routines, socio-technical work, and evidence practice. The QL lens is secondary and only becomes active when probing, exporting, or comparing the state changes or loses load-bearing structure.

C.26.2:7 - Conformance Checklist

C.26.2:8 - Common Anti-Patterns and How to Avoid Them

C.26.2:9 - Consequences

This pattern lets FPF discuss enacted collective states. It gives authors a disciplined way to use traces, routines, coordinated work, and export loss in one minimal claim.

The cost is that many attractive claims become narrower. Minimal evidence-bound claims are often more useful than confident but ungrounded stories.

C.26.2:10 - Rationale

Existing FPF patterns can carry parts of the support requirement, but no single ordinary pattern makes the combined minimal distributed-state claim easy to write. A.15 carries Work alignment, A.10 carries source-to-use evidence accounts, B.3 carries actual named assurance claims, F.9 carries cross-context semantic Bridge loss, and C.16 carries formal measurement. C.26.2 coordinates those neighboring-pattern applications for the specific case where coordinated work evidences a non-articulated state.

C.26.2:11 - SoTA-Echoing

Worked-slice discipline from these rows:

• ground the claim in coordinated work before QL vocabulary appears;
• state the evidence carriers and time window before stating the state reading;
• name rivals before retaining a distributed-state claim;
• treat survey/report/dashboard outputs as carriers or as instruments of a stated probe, not as the state;
• escalate to measurement, evidence, assurance, or authority patterns when the use requires measurement, evidence, assurance, or authority support.

C.26.2:12 - Relations

• Builds on: C.26, A.15, A.10, B.3, F.9, C.16, E.17.EFP, C.11.
• Coordinates with: C.26.1 when the probe changes the state being evidenced and its output is being used as a passive read; C.26.3 when the coordinated state is part of viability-envelope regulation.
• Does not mint: U.DistributedState, a bearer-independent group entity, or a durable state beyond declared evidence and time window.
• Name posture: Enacted Distributed State Evidence names an evidence-bound U.Episteme reading over work carriers.

C.26.2:End