C.26.2:4.9 - Carrier, probe, report, and state split
The pattern keeps four objects separate:
| Object | Role in the claim |
|---|---|
| Enacted work | What people, service-providing systems, or market participants actually did in coordination, including routine enactment and artifact use. |
| Evidence carrier | The log, trace, ticket, meeting note, deployment record, dashboard export, report, API response, or policy text that makes some part of the work inspectable. |
| Probe / approximation | The survey, dashboard query, interview, trace query, report request, metric, or publication act that frames the state reading. |
| Distributed-state reading | The minimal U.Episteme claim inferred from coordinated work or behavior under carriers, window, rivals, and export limits. |
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.