Wiki Query

Step 4: Read raw sources only if needed

• Escalate to docs/raw/ only when the wiki is missing evidence, incomplete, or ambiguous
• Keep any raw-source use narrow and specific to the gap
• Do not reopen lower-level telemetry, eval, workflow, or red-team artifacts when a maintained compiled page already answers the question unless that page is stale or superseded

Step 5: Distinguish answering from promotion

• Finish the answer before deciding whether any wiki update is needed
• Keep the recommendation separate so a correct answer does not automatically imply promotion

Step 6: Classify whether the answer is ephemeral or durable

• Treat the answer as durable when it is likely to be asked again
• Treat the answer as durable when it explains a decision, process, or recurring pattern
• Treat the answer as durable when it synthesizes multiple sources into a stable conclusion
• Treat one-off troubleshooting notes as ephemeral by default; add them to docs/wiki/log.md rather than forcing a formal page

Step 7: Recommend the promotion target only for durable answers

• Suggest concept for stable definitions or recurring patterns
• Suggest decision for rationale or tradeoff records
• Suggest report for synthesized findings or investigations
• Suggest process for repeatable operational steps

Step 8: Create candidate updates when a durable answer still needs review

• Log a candidate update instead of forcing an immediate canonical edit when evidence is promising but confidence is incomplete
• Capture enough rationale so later promotion work can review the durable answer cleanly

Output

• Direct answer to the question
• Wiki pages used as evidence
• Raw sources consulted, if any
• Answer classification: ephemeral or durable
• Suggested wiki promotion only when the answer has lasting value

Rules

• Always read docs/wiki/index.md first
• Prefer the minimum relevant wiki pages over broad wiki scans
• Candidate memory is a lower-priority fallback than canonical wiki memory
• Cite wiki pages used in the answer
• Read raw sources only to close evidence gaps or resolve ambiguity
• Separate answering the question from deciding whether to promote the result
• Log durable-answer candidates for later promotion when immediate canonical edits would be premature
• Suggest promotion only when useful knowledge is not yet durable in the wiki

Query Order

1. Read docs/wiki/index.md
2. Prefer compiled report or process pages when present and not marked stale or superseded
3. Check local candidate draft memory only when canonical wiki memory is missing or incomplete
4. Answer from wiki evidence first
5. Read raw sources only when the wiki is missing or ambiguous
6. Suggest promotion only if the answer adds durable project knowledge

Promotion Heuristics

Promotion is appropriate when the answer:

• is likely to be asked again
• explains a decision, process, or recurring pattern
• synthesizes multiple sources into a stable conclusion

Ephemeral one-off troubleshooting notes should go to docs/wiki/log.md, not necessarily a formal wiki page.

Related

• Wiki Query Command
• Wiki Ingestion Skill
• Wiki Lint Skill