Principle

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.

Work through the ideaIllustrative example

A working link can still point to the wrong edition.

A review checked a particular draft, while a “latest” link can lead to a changed one.

Blank cream letter sheets and a dark binder clip in a mustard envelopeA draft you can inspect

“The latest file passed review.”

The reader cannot tell which content the review covered.

The latest room plan passed review. See the folder.
What does a version-specific link solve?

It identifies the content behind the claim; the relationship between that content and the claim still needs checking.

Exact identity does not prove truth, delivery or permission. Retention and approved access still apply.

VedokrokKeep the idea. Try the next move.

Before you use it

Use when
  • A message ends with a pile of links and screenshots whose purpose is unclear.

Keep this limit in mind

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

Current editorial reading

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.

Take it with you

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.

Sources and evidence (1)

What we checked

Supports

GitHub file links that specify a commit identify the exact version in that commit; the Y shortcut creates such a permalink.

Official documentation inspected on 2026-10-05. The proposed run/log identity practice is an editorial application, not a documented GitHub runtime guarantee.

Getting permanent links to files · 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.

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.

Getting permanent links to files · File views show the latest version on a branch

Editorial sources (1)

Editorial version 1.0.0 · Evidence checked 2026-10-05

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingPoint to the evidence version you actually checked

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize.

Very short messages may not need headings; structure should match complexity.

Description and Examples of Index Items · 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.

Regulated or audit-heavy work may require context that feels redundant to the immediate reader.

Writing and editing: Plain language · Put users' needs first; titles and headings; be concise

All sources (2)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details