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
@@ -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/` -
|
||||
|
||||
Reference in new issue
Block a user