# Close the thread with the final state and source of truth

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

---

## Close the thread with the final state and source of truth

ID: MHC-D-RESEARCH-0620 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/close-the-thread-with-the-final-state-and-source-of-truth

Closure is a state transition worth writing down.

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

### Use when

- A problem is resolved but the thread ends with a partial update, leaving future readers unsure.

### Avoid when

- Do not declare resolved while monitoring, rollback or verification remains material; label those states accurately.

### Explanation

Post a final compact message with resolved state, what changed, any remaining follow-up and the authoritative artifact or ticket. Mark superseded instructions if they could still be reused accidentally.

### Steps

1. A future reader can determine the final state without replaying the whole thread.

### Example

After the transport imports, the thread records the final status, production transport ID and the obsolete workaround that should no longer be used.

### Check

A future reader can determine the final state without replaying the whole thread.

### Limits

- Do not declare resolved while monitoring, rollback or verification remains material; label those states accurately.

### 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: ONS guidance recommends writing around user needs, removing content that does not serve those needs, and using concise task-focused headings. — RS-96557E8AD37744B8. Regulated or audit-heavy work may require context that feels redundant to the immediate reader. (Put users' needs first; titles and headings; be concise)
- RS-B843492FBF1442AD: Description and Examples of Index Items — https://www.cdc.gov/ccindex/tool/description-examples-parta.html
- RS-96557E8AD37744B8: Writing and editing: Plain language — https://service-manual.ons.gov.uk/content/writing-for-users/plain-language

No review details supplied.
