# Show the delta when a requirement changes

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

---

## Show the delta when a requirement changes

ID: MHC-D-RESEARCH-0613 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/show-the-delta-when-a-requirement-changes

Change communication should reveal the change.

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

### Use when

- A thread says 'updated requirement' but readers must compare old and new text manually.

### Avoid when

- Keep formal change-control rules where required; a readable delta does not replace approvals or traceability.

### Explanation

State the previous rule, the new rule and why the change matters. For structured data, highlight changed fields rather than resending an unmarked full artifact. Name effective timing and whether previous work must be revised.

### Steps

1. A reader can identify what changed without diffing two long documents.

### Example

'Delivery block: blank → ZM for scope X; effective for Monday load; regenerate batch file only.'

### Check

A reader can identify what changed without diffing two long documents.

### Limits

- Keep formal change-control rules where required; a readable delta does not replace approvals or traceability.

### Evidence and sources

- supports: CDC clear-communication guidance recommends one obvious main message, placing it early and including a clear action for the audience. — RS-B843492FBF1442AD. Complex work can require several actions, but the communication still benefits from a dominant purpose. (Core items 1, 2 and 5)
- supports: CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize. — RS-B843492FBF1442AD. Very short messages may not need headings; structure should match complexity. (Core items 8 through 10)
- RS-B843492FBF1442AD: Description and Examples of Index Items — https://www.cdc.gov/ccindex/tool/description-examples-parta.html

No review details supplied.
