# Attach the source next to the claim it supports

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

---

## Attach the source next to the claim it supports

ID: MHC-D-RESEARCH-0611 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/attach-the-source-next-to-the-claim-it-supports

A source is most useful where the reader needs to verify the statement.

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

### Use when

- A message ends with a pile of links and screenshots whose purpose is unclear.

### Avoid when

- Links can rot and permissions can fail; preserve required evidence according to the system's retention rules.

### Explanation

Place the relevant link, log, document section or screenshot beside the claim or action it supports. Add a short label describing what to inspect. This reduces hunting and makes unsupported statements visible.

### Example

Instead of 'logs attached,' write 'Activation completed at 10:42 — see SLG1 screenshot, row 3.'

### Check

A reviewer can move from an important claim to its evidence in one step.

### Limits

- Links can rot and permissions can fail; preserve required evidence according to the system's retention rules.

### Evidence and sources

- 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)
- 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

### Vedokrok editorial review

Point to the evidence version you actually checked

Putting a link beside a claim saves a search, but a working link can still lead to a different version. Make it clear which artifact or run supports the statement.

#### Pin the relevant evidence

For code on GitHub, link the reviewed commit and relevant lines instead of relying on a moving branch URL. On a file page, pressing Y changes the URL to the commit-specific version. For operational evidence, identify the relevant run or object and the observation time alongside the log or result. Those workflow details are an editorial extension of the same version-binding principle.

#### Keep identity separate from proof

For example: “The parser at this commit rejects an empty key; see these lines and the matching test result.” That does not establish which build is deployed. Check the connection between the evidence and the claim separately, and confirm the intended recipient can open it. Preserve required records through approved retention procedures; a precise link does not expand sharing permission or guarantee permanent access. Keep a separate current-state link when readers need the latest guidance; label the evidence snapshot as historical.

**Editorial takeaway:** A reviewer should reach the exact evidence behind the claim and see its limits. For changing content, include the version or run identity, not just a clickable location.

#### Editorial evidence

- supports: GitHub file links that specify a commit identify the exact version in that commit; the Y shortcut creates such a permalink. — EA-GITHUB-PERMANENT-FILE-LINKS. Official documentation inspected on 2026-10-05. The proposed run/log identity practice is an editorial application, not a documented GitHub runtime guarantee. (Press Y to permalink to a file in a specific commit)
- limits: A normal file URL using a branch name can show different content after new commits change that branch. — EA-GITHUB-PERMANENT-FILE-LINKS. Limits the original link-placement advice: a reachable branch link alone does not preserve what the author inspected. No deployed build or account permissions were tested. (File views show the latest version on a branch)
- EA-GITHUB-PERMANENT-FILE-LINKS: Getting permanent links to files — https://docs.github.com/en/repositories/working-with-files/using-files/getting-permanent-links-to-files

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

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/show-the-delta-when-a-requirement-changes
