Skip to main content
Start with what you need to know: a fact from the repository, whether an approach should proceed, or whether the work is actually done.

​
Answer a repository question

Use Ask for facts about the current repository:
A grounded result has this shape:
The wording varies by model. The citation and grounding result tell you whether the answer is supported. If Navi asks for a deeper read, run the --deep command it prints before treating the answer as settled.

​
Make a grounded decision

Use Founder for a product, design, or implementation decision tied to a real artifact:
Founder returns one of three verdicts:
  • GO — proceed as scoped.
  • REFINE — bring back the missing grounding, then run it again.
  • REJECT — stop this approach.
The human result starts with the verdict and its take:
The full result also carries the repository evidence, the rule that decided the question, and traps to avoid. A REFINE result includes a continuation command for the same session.

​
Verify a completion claim

Use Check before saying work is done. Include the claim and the evidence you already have:
When more work is required, Navi names one action and the evidence to return:
Replace <new evidence> and run the continuation unchanged. The -t value keeps the result in the same session. See Sessions for continuation and history. For JSON output, structured edge-walk input, and process exits, use the Automation reference.