Pathway card
The machine is a network, not a monster
When an AI answer is wrong, why is “the machine got it wrong” no diagnosis?
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
Because “the machine” is a metaphor for a web of systems that do different things with the information: an index holds it, a retrieval selects it, a language model composes a new text from it, an agent acts on it — each with its own owner and its own kind of error. Naming the part and its role tells you what to correct.
For: Technical writers, technical project managers and documentation systems developers
Key points
- The machine is a metaphor, not one actor.
- Its parts hold, select, compose and act — different roles, different errors.
- The levels say who decides; the roles say what each part does.
- A diagnosis names the part and its owner.
Before and after
Before
The machine as one actor
- “The machine” answers, decides and errs.
- A wrong answer is reported as “the AI was wrong”.
- Nobody can say which part to correct.
After
The machine as a network of roles
- Each part is named with its activity and its owner.
- A wrong answer is traced to the part it came from.
- The correction goes to the source or the part, then reaches every answer.
Side by side
Each row names how far the control is as of the review date.
| Aspect | Before | After | Maturity |
|---|---|---|---|
| Unit of diagnosis | The machine | The part and its role | Building block available A naming decision |
| Index and retrieval | Invisible | Named with the revisions they hold and select | Product-specific Search and retrieval logs |
| Model | “The AI” | A compiling function with rules | Building block available Configuration |
| Agent | Part of the AI | A role that writes back, with a gate | Product-specific Approval gates vary by tool |
The path from before to after
Each step names who does it and what it leaves as evidence.
List the parts
List the parts between the released documentation and the answer: index, retrieval, model, agent.- Who
- Documentation systems developers
- Evidence
- Parts list
Name roles and owners
Give each part its activity family and an owner.- Who
- Technical project manager
- Evidence
- Role and owner table
Trace an error
For a wrong answer, find the part and the revision it came from.- Who
- Documentation systems developers
- Evidence
- Error record with lineage
Correct at the source
Correct the source or the part, never only the answer.- Who
- Technical writer
- Evidence
- Change record
Limits and residual risk
A parts list is a snapshot: the web changes faster than any description of it. Naming the parts makes errors traceable; it doesn’t prevent them.
The context
The simplification
The blueprint “AI-enabled information systems for technical writers” and the blog post on why the author calls it “the machine” use one word for everything behind an AI answer — deliberately, to make the assembly visible. The image of one big machine helps to see that there is an assembly at all.
Where it becomes too coarse
When an answer at the operator panel of DS-3 names the old test interval, “the machine got it wrong” doesn’t say what to correct. The index may hold an old revision; the retrieval may have selected the wrong variant; the language model may have combined two revisions; an agent may have written a value back. Each part plays a different role and has a different owner. The blueprint “AI systems and the machine: levels and boundaries” says where the company decides about them; it doesn’t say what each part does with the information.
The role grammar
The actor axis names each part — rule-based system, AI function, AI agent — and the activity families say what it does: holding (deciding or passing on), selecting and composing (compiling), acting (writing back). The lineage of a value — data lineage and answer provenance — shows which part an error came from.
Questions readers ask next
- Is “the machine” then the wrong word?
- No. It stays the metaphor for the whole web, as defined in the earlier blueprints. The role grammar adds the names of the parts where a decision or a correction needs them.
- Does every company need to map all parts?
- No. It needs to name the parts that its documentation reaches — and their owners — where an answer can go wrong.
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.