Pathway card
From three readers to check roles
The home page names three readers — the source, the person and the third reader. Why is that enough to design a check method, and what has to change before a check can run?
A pathway card shows where a practice starts, where it can get to, what does not change on the way, and the steps from one to the other. The path from before to after
The short answer
The three readers are placeholders: they show in minutes who has a stake in a value. A check rule, though, has to name a unit, a role, a value and an owner. So each placeholder opens into roles — the source into writing and deciding, the person into using with qualification and authority, the third reader into compiling, using and writing back.
For: Technical writers, technical project managers and documentation systems developers
Key points
- The source, the person and the third reader are placeholders, not roles.
- Placeholders are enough to design a check method; they are not enough to run a check.
- The source opens into writing and deciding: who formulated a value, who released it, which system holds it.
- The person opens into using, with qualification, authority and situation.
- The third reader opens into compiling, using and writing back — an answer function compiles, it doesn't read.
Before and after
Before
Three placeholders
- The source, the person and the third reader stand for everyone with a stake in a value.
- Only the third reader is opened, into ten roles that are all called readers.
- A check can only say “the third reader” — not which system, which role, which owner.
After
Roles a check rule can name
- All three placeholders are opened: the source, the person and the third reader.
- The roles are ordered by activity family: writing, deciding, compiling, using, writing back.
- Each role becomes a unit a check rule can name, with a value, an owner and a trigger.
Side by side
Each row names how far the control is as of the review date.
| Aspect | Before | After | Maturity |
|---|---|---|---|
| The source | The first reader | Writing and deciding: who formulated, who released, which system holds it | Building block available Release and ownership |
| The person | The second reader | Using, with qualification, authority and situation | Building block available Established qualification terms |
| The third reader | Ten roles, all readers | Compiling, using and writing back | Building block available The role grammar |
| The check | Asked of a placeholder | A rule with unit, role, value, condition, evidence, owner and trigger | Building block available The check rule grammar |
The path from before to after
Each step names who does it and what it leaves as evidence.
Start with the lens
Name, for one value, the source, the person and what lies between them.- Who
- Technical project manager
- Evidence
- Three placeholders per value
Open the placeholders
Replace each placeholder with the roles it stands for and their activity family.- Who
- Technical writer
- Evidence
- Role table
Name the units
For each role, name the system, subsystem or function that plays it.- Who
- Documentation systems developers
- Evidence
- Unit list
Write the check rules
Write one check rule per role with value, condition, evidence, owner and trigger.- Who
- Technical project manager
- Evidence
- Check rules
Limits and residual risk
Roles and check rules don't decide who owns a value — the company does. A check rule never verifies a safety function.
The context
The simplification
The matrix “What we cover” on the home page looks at documentation through three placeholders: the source, the person and the third reader — everything that meets the information between the two. That is a useful lens: it shows in minutes who has a stake in a value.
Where it becomes too coarse
A check rule can't name a placeholder. It has to say which unit it checks, which role the unit plays for one value, and who owns the answer. “The third reader” hides that some systems decide a value (a system of record, a golden record), some compile a new text from it, some show it (a system of engagement) and some write it back. And the first two placeholders hide as much: the source doesn't read — its writers and the release decision make it count —, and the person is an instructed person or a skilled person, with different authority.
The check strategy
The check strategy Who decides which value counts opens all three placeholders and orders the roles by the five activity families of the role grammar: writing, deciding, compiling, using and writing back. Writing and deciding need a data owner; compiling needs data lineage; writing back needs a gate. The method tool The check rule grammar turns each role into a check rule. The test question stays: who may change it here — and how does the next system know which value counts?
Questions readers ask next
- Are the three readers on the home page wrong?
- No. They are a lens, and a useful one: they show who has a stake in a value. They only stop where a check has to name something it can check.
Sources
- Saina Veigel, Who decides which value counts: roles of product information from source to answer (check strategy) — knowledge.aitechdoc.world, November 11, 2026
- Saina Veigel, The check rule grammar (method tool) — knowledge.aitechdoc.world, November 11, 2026
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.