Skip to content

Agent Rules

The agent operating rules live in the root AGENTS.md.

Working Rules

  • Query Graphify before repository-structure questions when graphify-out/graph.json exists.
  • Use docs/llm-wiki/ for durable operational knowledge.
  • Maintain the wiki as a structured evidence-and-synthesis system, not a loose note set.
  • Keep Source Register, Evidence Matrix, Evidence Validation Queue, Research Log, synthesis pages, architecture/model pages, glossary, LLM operational notes, and generated discovery artifacts distinct.
  • Treat research priorities as evidence gaps, synthesis gaps, implementation gaps, and confidence limits that block reliable guidance; do not record final guidance itself as a research priority.
  • Check affected anchor pages in docs/llm-wiki/context-map.md before and after domain work.
  • Put direct evidence first, adjacent implementation evidence second, and wider context only where it changes interpretation.
  • Treat DESIGN.md as the styling source of truth.
  • Run npm run kb:update after Markdown, docs-structure, source, workflow, or Graphify-relevant changes.
  • Run npm run verify before handoff.
  • Commit every file-changing development pass with jj commit.
  • Move the main bookmark to the committed change when the pass should advance main.
  • Verify git status --short, jj status, and push/upstream state before reporting complete.

Response Contract

After every substantive response, include a What Next section with exactly three numbered steps. Each step should be discrete, high-impact, actionable in one follow-up pass, and tied to a wiki page or project artifact where possible. Include rendered wiki URLs for referenced or updated wiki pages when the local or published wiki URL is available.

Do not count passive trigger conditions, "wait until a source appears" items, or generic maintenance reminders as What Next steps. Parked boundaries belong in the summary, Evidence Validation Queue, Research Log, or affected synthesis page; the three numbered steps should be executable next-pass work.

Clean Handoff Checklist

git status --short
jj status
npm run verify
jj commit -m "Describe the change"
jj bookmark move main --to @-
git status --short
jj status

If no Git remote or upstream is configured, report that push verification is blocked rather than claiming the repository is pushed.