Factimonious®

Documentation

Guides for evidence-first engineering

Why Factimonious is different, how it compares to adjacent tools, and quick agent habits that keep AI-assisted delivery reviewable. Connect repositories and queue runs in the app after you sign up.

Quick start

Copy or adapt these one-liners so coding agents default to traceable, review-friendly habits—aligned with evidence-first workflows. Full page: Agent habits.

  • Git commits

    Add a line to your AGENTS.md (or team agent instructions) like:

    Git commits: Always include: [FEATURE/BUG-xxx] + one-line behavior change + evidence files + "why it matters" intent.
  • Claims and conclusions

    Keep agents grounded in repository facts:

    When you state a conclusion, cite the file path (and line range or commit) it came from; if you cannot cite evidence, say what is unknown.
  • Wrapping up a task

    Make completion auditable for standups and retros:

    Before marking work complete: run the relevant tests or build, note the command, and summarize pass/fail with a short excerpt from the output.

Product docs in the app

Repository install, webhook auto-runs, Slack schedules, tier limits, and command reference live in the signed-in product docs after login—not on this public site.