Backed by Relevance Lab· previously known as Kaman.aiInsightsWhitepapersTrust centreCareersContactSign in
Try it now

Home / Whitepapers / Whitepaper

Whitepaper

Journey-driven development: proving software against user journeys with human-governed agent crews

The method Camaan uses to build Camaan. Each change starts as a written journey, is built by a coding agent, and is done only when an end-to-end test passes and its screenshots are attached for a person to review. Includes a case study of one repository's proof record.

  • A journey is a document written before the code; done means a passing end-to-end test plus the screenshots it took.
  • Pluggable coding agents work in separate worktrees and coordinate through an append-only journal.
  • Role limits are checked at the tool call, and a person who is not the author decides every merge.
  • 356 journeys, 351 with proof, and 1,780 proof screenshots in six months, with a plain account of what that cannot show.