C.26.1:4 - Solution

Before accepting a passive read or unjustified lossless-transfer reading, ask whether the probe or interaction changed what the output may admissibly mean.

C.26.1 is active only when the interaction both participates in the represented state and its output is being used as evidence, export, comparison input, or decision input as if it were passive. Mere behavior change, ordinary feedback, or ordinary influence is not enough.

A probe-coupled interaction may be useful and intentionally state-shaping. The repair is not to avoid it; the repair is to stop using its output as if it were a neutral pre-probe read.

Start with this recognition note:

Use the fuller decision-bearing record below when the boundary result will be reused, contested, used as evidence, or used to change an architecture decision.

Full decision-bearing record:

C.26.1:4.1 - Activation boundary

This pattern is active only when the interaction both participates in the represented state and its output is being used as evidence, export, comparison input, or decision input as if it were passive. A passive-read, unjustified lossless-transfer, one-way-message, or ordinary-bridge treatment must be materially false for the current decision.

Ordinary influence is not enough. A meeting that changes attention is ordinary work unless the meeting output is later used as a passive reading of alignment. An API call that is a mutating operation by its interface semantics is ordinary service/API semantics unless the call result is used as a neutral state export. A feature flag that changes behavior is ordinary intervention unless the flag readout is being used as evidence of the state it changes.

Performative prediction is also an important ordinary rival. If a prediction, score, or metric changes behavior because people act on it, but no incompatible probe frame, order-sensitive reading, contextual-probability cue, or instrument-like state/export support load remains, try performative-prediction analysis first; use C.16 for measurement, A.10 for source recovery and bounded reliance, and B.3 only for an actual named assurance claim. Keep C.26.1 only for the residual probe admissibility question.

C.26.1:4.2 - Finish conditions

The pattern emits one of these results:

C.26.1:4.3 - Probe-coupled context-cut worked use slice

This worked use slice is not a standalone pattern. It tests DDD and bounded-context work when the context cut is not only discovered but also changes meaning, coordination, export validity, or viability.

Ask: was the bounded-context cut merely discovered, or did the workshop, dashboard, API extraction, bridge, split, merge, or orchestration change alignment, ownership, vocabulary, export validity, or viability?

C.26.1:4.4 - Boundary interaction under concern and operational sequence

The boundary interaction under concern is a boundary interaction used as evidence, export, comparison input, or architecture decision input. The interaction may be a meeting, question sequence, dashboard, metric, API read, survey, workshop, event stream, canary, test harness, service split, bridge, message, or management review. The pattern is active only when that interaction participates in the represented state enough that passive-read wording or unjustified lossless boundary-to-decision inference would change the decision.

The pattern governs one move: convert an apparently passive boundary read into a typed probe-coupled boundary decision. That decision says what the interaction read, what it changed, what the output can support, what it cannot support, and which neighboring FPF pattern takes over if the question is really bridge, measurement, evidence, work, decision, or viability.

Operational sequence:

1. Name the boundary or relation being crossed.
2. Name the probe lane, including the concrete artifact or work act that produced the output.
3. State the false passive reading: what the team would have assumed if the probe were only a window.
4. State the pre-probe hypothesis and the observed or inferred post-probe state.
5. State the evidence carriers and uncertainty posture.
6. State the export loss, memory, order effect, or frame effect that makes the output not faithful enough for the declared use.
7. Choose the finish result: keep boundary with probe note, redesign probe, order, or frame, redesign bridge or export, change the split, merge, or orchestration, or apply a neighboring FPF pattern.

Required output: produce a probe-coupled interaction reading, a corrected use of the output, and, when it would reduce the problem, a redesign or decoupling move for the probe, order, frame, bridge, metric, dashboard, API read, or boundary interaction.

This sequence is deliberately small. It is the boundary analogue of the C.11 local choice pass: the pattern should end with a usable result, not with a richer vocabulary label.

C.26.1:4.5 - Well-formed probe-coupled boundary state

A probe-coupled boundary decision is usable only when the record states all of the following:

• the boundary, context bridge, service interface, team boundary, role relation, authority relation, or system edge involved;
• the probe lane and output carrier;
• the state reading before the interaction and the state reading after the interaction;
• the state-change evidence, including traces, changed labels, changed priorities, changed timings, changed routines, changed bridge fields, or changed downstream decisions;
• the local stop condition: which use the output does not support without another pattern;
• the neighboring FPF pattern that would carry the other claim.

The record is unfinished when any of these remains true:

• the output is named, but the operation that produced it is hidden;
• the operation is named, but the state that changed is not named;
• the state changed, but the decision that changes because of that fact is not named;
• the bridge/export loss is stated only as a vague warning rather than as a concrete non-admissible use;
• the same interaction is alternately treated as evidence, command, measurement, and bridge without role split.

The minimal admissible output is often enough: “this dashboard value is probe-coupled evidence for readiness behavior under window W”; “this workshop work changed alignment and therefore the workshop note cannot be treated as passive discovery”; “this API read is a non-neutral observation under these interface semantics”; “this context cut needs both F.9 bridge loss and C.26.1 probe-coupling treatment.”

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.

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.

C.26.1:4.7 - Reroute and disambiguation guide

Use this guide when a draft says that a boundary, system, team, or service is “coupled”, “aligned”, “interacting”, “measured”, “exported”, “synchronized”, or “read”.

When relation wording is load-bearing, do not mint a relation token here. Use A.6.P if the relation or participants remain unclear; use the direct relation pattern when they are already known. Keep local explanatory prose unless the settled relation needs a reusable name under F.18.

C.26.1:4.8 - Positive examples and near misses

The positive examples establish probe-coupled interaction readings. Use those results without QL wording when the ordinary subject patterns carry the case, as CC-C26.1.4 permits. Retain QL only when the additional C.26 activation test establishes one named contextual-model obstruction that survives those patterns and changes the admissible inference or action.

C.26.1:4.9 - Evidence posture for probe-coupled claims

Use the least-committing evidence posture that still supports the intended use.

Do not make QLP-3 the ordinary entry cost. Recognition or local working use may remain at QLP-0 or QLP-1 when its account is sufficient. Select additional support from the receiving conclusion under C.26:12b; publication, reuse, or formal wording alone does not require escalation or recollection of adequate evidence.