Source ledger and claim boundaries
5 min read
Lesson objectives
- Build a source ledger with authority, version, and claim boundaries.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A short technical sentence can make several claims: a button label, the condition that enables it, the resulting state, and when that state takes effect. A broad link at the end of the page does not make every claim accurate. Keep a compact source ledger that connects each consequential claim to a verifiable location. Record the proposed wording, source and publisher, edition or date, supporting passage, applicability to the release being documented, and review status. A reviewer can then challenge “the appointment becomes final” without reopening the whole document.
Authority matters, but it is not one rigid ranking for every question. An approved product specification for the intended release may establish interface behavior. A support article may reveal the situations readers ask about. A chat message may alert the team to a change that has not shipped. Rank sources for the claim at hand, not just the writer’s job title. A field specification does not prove that readers understand a field; a user test does not prove that the label will survive release. Each question needs suitable evidence. When materials conflict, record both sides, versions, and the exact difference instead of choosing the one that looks newest.
Read the source passage, not merely its title or search snippet. If a draft says “you can edit a request after submission,” look for the relevant permission, state, and exception. A specification may allow editing only after a supervisor reopens a request. Removing that condition makes the sentence misleading even though the word “edit” appears in the source. Limit the claim: “After a reviewer reopens a request needing correction, the applicant can edit the specified fields.” If the source does not establish who may act, leave that as an open question. Do not turn one publisher’s editorial advice into universal law or another service’s operating rule.
Give each source a status:
- applicable to the current release
- foundational guidance about method rather than current interface behavior
- superseded by a later release
- or unverified
An older foundational guide may remain useful for explaining clear steps; age alone does not defeat it. A field name or timing policy, however, must match the version readers actually use. “Opened the link” differs from “checked the paragraph that supports this claim.” Record the actual check date and passage. If access fails, do not write “verified.” Remove an unnecessary claim or hold it until suitable evidence is available instead of attaching a nearby source that does not support it.
At final review, test the ledger backward: choose each high-impact sentence, follow its source pointer, read the surrounding qualification, and compare the version. Test it forward as well: where is each listed source used, and why? Extra sources do not increase reader confidence. Separate a fictional example created to teach reasoning from a fact about a place or organization. Mark the former as hypothetical; provide appropriate support for a professional rule attributed to a publisher. Traceability is a means to correct copy, not decoration in the notes.
In the ledger, rate how directly a source supports the claim rather than relying on publisher reputation alone. An official document may prove that a control exists in release 4 but say nothing about whether every role can see it. Read adjacent notes and tables for role or environment qualifications. A stable URL may host changing content; record its release or update date and recheck a consequential claim before publication. If a sentence invokes both product behavior and writing method, separate the support. The product specification establishes an error label; a style guide can support how to present it, but cannot prove the product displays it.
Lesson summary
Build a source ledger with authority, version, and claim boundaries.