wiki-query: Wortlaut geführt in der Rohdatei nachlesen - neuer Schritt 4 über Seite, Source-Seite, raw_files: und Gliederung im Kopf der Ableitung bis zum Zeilenbereich, nie Suche in raw/; ohne Gliederung ganz unter der Längenschwelle, darüber Hinweis auf neue Ableitung; Zitat in Originalsprache mit Seitenzahl, Auszeichnungen nicht als Wortlaut, Gestrichenes benannt; Antwort nur in der Rohdatei benennt die Lücke. kb/CONTRACT.md: Qualitätsziel gilt der Substanz (#227); 10.1.0-beta.11

Files changed:
- CHANGES.md
- VERSION
- docs/explanation/pipeline-rationale.md
- docs/how-to/query-the-wiki.md
- instructions/wiki-query/SKILL.md
- kb/CONTRACT.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

docs/explanation/pipeline-rationale.md

@@ -52,6 +52,17 @@ file," the `kb/` layer would just be a pointer with extra steps, and the cost of
 would have bought nothing. A page that stands alone is what makes the corpus fast and
 consistent to query: the work of understanding is already sitting there, done.
 
+The bar is about substance, though, not wording. For a rulebook or a manual the question that
+comes back is often about the exact text - what a clause says word for word, which value a table
+gives - and a page that carried every such sentence would be the document again, with its own
+chance of copying one wrong. So a query may read the raw file for the wording, but only along a
+fixed route: from the page that carries the substance to its source page, to the outline in the
+derivation's header, and to the one passage's line range. A search over `raw/` would turn the
+raw layer back into the thing being queried, which is what compiling was meant to end; reaching
+it only through a page keeps every answer anchored in what was already understood. The line
+that does not move is that an answer standing in the raw file and on no page still shows a gap
+in `kb/` - the query names it rather than making that the normal way to answer.
+
 ## Why `reports/` doesn't need to be maintained
 
 [reports/CONTRACT.md](../../reports/CONTRACT.md) treats most of what lands in `reports/` -

docs/how-to/query-the-wiki.md

@@ -25,6 +25,28 @@ If an answer is worth keeping - a comparison you will want again, a synthesis ac
 the agent proposes filing it back as a page. It names the pages it would create before it creates
 any, and nothing is written unless you agree.
 
+## Asking for the exact wording
+
+Some questions are about the text itself - what a rule says word for word, which value stands in
+a table of a manual:
+
+```text
+What exactly does rule 16:3e say?
+Which torque does table 4 of the assembly manual give?
+```
+
+The agent still starts from a page. For the wording it follows that page to its source page, then
+to the outline in the header of the source's derived text, and reads only the passage's lines - it
+never searches `raw/`. The quote comes in the language of the original, with the source page and
+the page number. Markings the derivation added (bold, italic, highlighting) are left out of the
+quote, and struck-through text is said to be struck rather than quoted as if it were in force.
+
+Two answers point at work for later. If the derived text has no outline and is too long to read
+whole, the agent says the wording cannot be reached directly and names the way to change that: a
+new `raw derive` of the original, accepted with `raw accept --replaces`. If the answer stands in
+the source but on no page, the agent answers with the quote and names the page that is missing it,
+offering to complete it - it writes nothing on its own.
+
 ## Searching yourself
 
 The agent searches with the same command you can run:
@@ -47,4 +69,6 @@ a graph, see [Browse the wiki in Obsidian](browse-with-obsidian.md).
 ## Asking from another machine
 
 A consumer that is not a terminal on this machine can ask the same questions through the MCP read
-server and get the same answers: [Set up the MCP read server](set-up-the-mcp-server.md).
+server and get the same answers: [Set up the MCP read server](set-up-the-mcp-server.md). The one
+difference is the exact wording above: the read server serves pages only, never `raw/`, so a
+reader over MCP gets the wording only where a page carries it.