# Probe the boundary between two components

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Probe the boundary between two components

ID: MHC-D-RESEARCH-0294 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/probe-the-boundary-between-two-components

Do not interrogate the whole chain when one boundary can answer where the bad value first appears.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Several services, interfaces or processing steps could plausibly own the same symptom.

### Avoid when

- A boundary check can be misleading when retries, caches, asynchronous queues or hidden transformations change the path.

### Explanation

Choose a boundary with a defined input and output. Send a known test input or inspect one real transaction on both sides. If the input is correct and the output is wrong, the search moves inward; if the boundary already receives bad data, move upstream. Repeat until the failure domain is small enough to inspect directly.

### Steps

1. The probe removes at least one component or interface from the active hypothesis set.

### Example

Capture the outbound payload from middleware and the inbound payload accepted by the target before debugging either application's entire data model.

### Check

The probe removes at least one component or interface from the active hypothesis set.

### Limits

- A boundary check can be misleading when retries, caches, asynchronous queues or hidden transformations change the path.

### Evidence and sources

- supports: Google SRE recommends examining well-defined component interfaces and injecting known test data to check expected transformations. — RS-A4A16C807A94C9D8. Interface probes can disturb stateful systems; use safe inputs and preserve context needed to interpret the result. (Simplify and reduce)
- RS-A4A16C807A94C9D8: Effective Troubleshooting — https://sre.google/sre-book/effective-troubleshooting/

### Vedokrok editorial review

Trace one transaction across a component boundary

A correct value in the sender’s log does not show what the receiver received. Compare the same transaction on both sides of one boundary.

#### Capture a useful comparison

Name the two components, the input, the expected transformation and the observed output. Prefer an existing trace; if a new probe is needed, use authorized, safe test data. For example, compare a queued job’s sent payload with the payload consumed downstream, keeping the transaction identifier and relevant timestamps together.

#### Let the result narrow the next question

If the input is already wrong, investigate upstream. If a correct input becomes wrong, inspect the transformation. First check that caches, retries or asynchronous processing have not made you compare different attempts. Record an inconclusive result when they have. A single successful probe cannot clear a component of an intermittent fault.

**Editorial takeaway:** Leave a small record of the boundary, input, expected and observed result, and next test. Useful progress can be a narrower question; it need not eliminate a suspect.

#### Editorial evidence

- supports: Google SRE recommends examining component interfaces and testing expected transformations. — RS-A4A16C807A94C9D8. Selected official passages inspected on 2026-10-04. The transaction record is an editorial adaptation. (Simplify and reduce)
- limits: Operational tests can change state, be confounded, or provide only suggestive evidence. — RS-A4A16C807A94C9D8. This limits the original card’s requirement that every probe eliminate a component. No system was probed during this review. (Test and Treat; test-design considerations)
- RS-A4A16C807A94C9D8: Effective Troubleshooting — https://sre.google/sre-book/effective-troubleshooting/

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (alternative): https://vedokrok.com/knowledge/bisect-a-large-failure-domain
