Query: ask the wiki

The wiki is the first source, not the raw files and not your general knowledge. Rules: AGENTS.md §3, §6.

1. Find

1. Read index.md; pick candidate pages by title/summary.
2. Widen with search (AGENTS.md §5a):
   • qmd installed: write a structured query yourself; don't paste the owner's sentence:

     qmd query $'intent: <what you need, and what to avoid>\nlex: <exact terms, names, aliases>\nvec: <paraphrase in source-like wording>' -n 10

     Exact names/titles → qmd search "<terms>" -n 10. Default collections are wiki, projects, journal and outputs; narrow with -c wiki. Fetch hits with qmd multi-get "#id1,#id2" before relying on them; snippets are leads. If qmd query/vsearch fails (models, GPU) or the embed hasn't caught up yet, fall back to qmd search.
   • No qmd: grep -ril "<term>\|<synonym>" 20-wiki/ 30-projects/.
3. Read the candidates fully, then follow ## Related links one hop if they look relevant.
4. Only if the wiki is thin: check 10-raw/ sources directly (qmd search "<terms>" -c raw), and say you did ("the wiki doesn't cover this yet; from the raw source …"). That gap is itself a finding: suggest ingesting/re-ingesting.

2. Answer

• Lead with the direct answer, then the support.
• Cite inline as [[page-name]] for every non-obvious claim. Cite source pages for specific numbers/quotes.
• Respect ## Contradictions sections: present both sides, don't pick silently.
• Mark general knowledge that is not from the vault: "(not in vault)". Mark inferences: "(inference)".
• Choose the format that fits: prose, comparison table, timeline, checklist, Mermaid diagram, Marp slides.

3. Gaps (required for every substantial answer)

## Gaps
- What the wiki could not answer, and what kind of source would fill it.
- Stale or single-source claims the answer relied on.

An empty Gaps section is almost always wrong. Look harder.

4. Save (if substantial)

Substantial = new synthesis, comparison, decision support, or anything over a few paragraphs. Skip saving for quick lookups ("when did I ingest X?").

• Write 50-outputs/queries/YYYY-MM-DD-short-title.md from 90-system/templates/query.md.
• Append to log.md: ## [YYYY-MM-DD] query | <question, shortened> with a - saved: 50-outputs/queries/… line.
• Run scripts/qmd-sync.sh so past answers are searchable.

5. Offer to file back

End with one line: "Want me to file this back?", with a concrete proposal:

• A new 20-wiki/syntheses/<name>.md page (template synthesis.md), or
• Specific additions to existing pages (name them).

On "yes": write it like an ingest (citations, sources:, bidirectional links, index.md, log.md entry ## [YYYY-MM-DD] query | filed back: <title>), and set filed_back: true in the saved query file. Then run scripts/qmd-sync.sh. Synthesis pages cite the wiki source pages behind them, not the query file.

Hard constraints

• Never present general knowledge as if it came from the vault.
• Never edit wiki pages during the answer itself; changes only happen through file-back, with the owner's yes.