C.26.1:4.6 - Probe, observable, output, and carrier split
Do not identify what is being read with the method used to read it, the resulting output, or the output carrier.
| Role | Boundary-facing question |
|---|---|
| Observable or output dimension | What readiness, status, alignment, failure, response, risk, split, promise, or boundary condition is being read? |
| Probe method | How is the dashboard, API read, workshop order, survey, canary, incident review, event stream, or meeting format used to probe the situation? |
| Measurement / interaction scheme | What timing, threshold, sampling rule, question order, aggregation, publication path, or access path shapes the output? |
| Output or result record | What score, label, context map, API response, survey answer, incident class, readiness status, or bridge field was emitted? |
| State update | What behavior, alignment, meaning, trust, priority, escalation, or timing changed because of the probe? |
| Evidence carrier | Which log, dashboard export, meeting note, trace, decision record, ticket history, context map, or API result carries the output? |
This split prevents a common mistake: “the dashboard says ready” hides at least four objects. The dashboard definition, the displayed result, the behavior it changes, and the readiness decision are distinct.