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
This commit is contained in:
1 parent
4f5913a9c8
commit
ca12c54200
6 files changed
+101
-10
No files matched your search
@@ -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.
|
||||
Reference in new issue
Block a user