Chemenu kompiliert Rohnotizen zu einem verlinkten, quellengebundenen Wiki: raw/ -> types/ + tools/ -> kb/ -> reports/. Was mechanisch ist, macht tools/wikitool; was Urteil braucht, macht ein Agent unter Contracts, deren Grenzen in Code durchgesetzt sind statt im Prompt. Dieser Commit ist der Startpunkt der oeffentlichen Historie. Die vorherige Entwicklung fand in einer privaten Instanz statt und ist nicht Teil dieses Repositorys; ihre Erzaehlung steht vollstaendig in CHANGES.md, das mit 44 Eintraegen von 0.1.0 bis 2.1.0 erhalten geblieben ist. Der mitgelieferte Korpus ist ein Testbett und eine Demo: 170 Seiten ueber den Stack selbst - Gates, Lint, Versionierung, Suche, das Wiki-Muster. Er dokumentiert das Werkzeug mit den eigenen Mitteln des Werkzeugs. Lizenz: AGPL-3.0 fuer den Stack (tools/, types/), CC-BY-4.0 fuer die Inhalte. Die Grenze zwischen beiden ist der Dateiplan, den dist export berechnet - siehe NOTICE.
3.5 KiB
name, description
| name | description |
|---|---|
| wiki-query | Answer a question using the LLM wiki's compiled knowledge - read-only, cites sources, can file a valuable answer back as a new page. Use when the user asks a question about entities, projects, concepts, or anything the wiki might know, or says "query the wiki", "what do we know about X", "search the wiki". |
Wiki Query
Purpose: Answer a question using the wiki's compiled knowledge.
Trigger: User asks a question.
Hard rule: read-only with respect to wiki content. Never modify, hand-edit, or scaffold a
page while answering. Two exceptions, both mechanical: step 5 (filing a valuable answer through
wikitool new, never by hand) and step 6 (one audit entry via wikitool log append). If the
wiki has no confident source, say so - per AGENTS.md's "never file an unsourced answer"
invariant - rather than synthesizing a plausible-sounding answer from general knowledge.
Steps
-
Understand the question. Clarify intent if ambiguous.
-
Search. Do not read
kb/index.md; it is a map of counts and pointers, not a catalog, and reading the shards costs more than searching them.tools/wikitool search "<the user's terms>"Results carry kind, summary, confidence and modified date - enough to decide what is worth opening. Narrow with predicates when the question is structural rather than lexical:
tools/wikitool search "backup" --kind entity --subtype system tools/wikitool search --field entity_type=system --field 'confidence<0.6' --sort -modified tools/wikitool search --field tags=k8s --limit 30 tools/wikitool search "Longhorn" --matches # show the matching linessearchis read-only and exempt from the iteration budget, so searching again is always cheaper than reading more. -
Read only the pages the search points at, then follow their
related:andsources:entries. Checkkb/sources/when the question is about what a specific source said. -
Answer and cite. Name the wiki pages the answer came from, and the sources behind them. Hedge to the page's confidence: below 0.6 write "possibly"/"may"; below 0.4 write "uncertain"/"unconfirmed".
-
File it back, if it earns a page. Only when the answer required synthesis across several pages, revealed something not already written down, and will be asked again. Then scaffold it -
tools/wikitool new ...- and followwiki-manage. Never write the page by hand, and never file an answer no source backs. -
Log it.
tools/wikitool log append --op query --title "<question>" --body "<outcome>"
Decision points
- Nothing found? Try the structural query before concluding the wiki is silent - a page may exist under different words. Then say the wiki has no confident source, and offer to ingest one.
- Filed a page? Query does not auto-publish. Run
tools/wikitool publishonly if asked; the sequence is in publish-cycle.md. - Several answers filed at once? That can trip the Mass-Update Gate - see gates.md.
wikitool commands used
search, log append. If filing an answer back: new, xref add, sources rebuild-index,
index rebuild.
Output
An answer in chat, with citations. Occasionally a new page.
Example queries:
- "What projects use MQTT?"
- "Show me the architecture of ha-core"
- "Compare gdeploy and plugnburn-edl"
- "What decisions were made about E3DC integration?"