# Specify the interface where responsibility changes hands

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

---

## Specify the interface where responsibility changes hands

ID: MHC-D-RESEARCH-0785 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/specify-the-interface-where-responsibility-changes-hands

Many ambiguous requirements live in the space between two owners.

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

### Use when

- Each component looks correct in isolation but failures occur at handoffs between teams, systems or process steps.

### Avoid when

- Interface detail should match risk; do not create heavyweight documents for trivial internal calls that are already governed by stable contracts.

### Explanation

For each important interface, name the producer, consumer, object transferred, trigger, format or contract, timing, error signal, retry or fallback, and who owns a failed handoff. Treat the boundary as a requirement surface, not invisible plumbing.

### Checklist

- Producer and consumer
- Data/object/event transferred
- Trigger and timing
- Format or contract
- Acknowledgement or success signal
- Failure/retry behavior
- Owner when the handoff fails

### Example

An outbound IDoc interface specifies who sends it, message type, trigger, acknowledgement, retry behavior and which team owns an unprocessed message.

### Check

A handoff failure can be assigned and diagnosed without first debating where one component ends and the next begins.

### Limits

- Interface detail should match risk; do not create heavyweight documents for trivial internal calls that are already governed by stable contracts.

### Evidence and sources

- supports: NASA's requirements checklist emphasizes clarity, one thought per requirement, completeness, explicit assumptions, consistency, traceability, feasibility and verifiability. — RS-A059268EF3F10749. The checklist is for systems engineering; smaller tasks can apply the principles proportionally. (Requirements validation checklist)
- RS-A059268EF3F10749: Appendix C: How to Write a Good Requirement — https://www.nasa.gov/reference/appendix-c-how-to-write-a-good-requirement/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/specify-what-happens-when-the-happy-path-cannot-complete
