Cautilus User Workflow View
Cautilus helps users discover, evaluate, and improve behavior promises as prompts, agents, and app behavior change.
Use this page to answer four questions: is my repo ready, what promises did Cautilus find, can I evaluate behavior, and can I improve it safely? Each workflow page names the user job, the Cautilus surface, the expected outcome, and the available evidence.
Maintainer view: Contracts. Full spec entry: Cautilus Promise Specs. Cross-cutting rules and per-promise rule/contract map: Cross-Cutting Rules, Promise Ledger.
Workflow Stories
- Readiness: see which Cautilus workflow is ready, blocked, or missing setup before starting claim, eval, or improve work. Primary surfaces:
cautilus doctor,cautilus doctor status, and thecautilus-agentskill. - Claim Discovery: scan selected source docs into broad source-referenced candidates, curate false positives and likely missing promises, and turn the result into a reviewable next-work map. Primary surfaces:
cautilus discover claimsand thecautilus-agentskill. - Behavior Evaluation: evaluate behavior across
dev/repo,dev/skill,app/chat, andapp/promptsurfaces when deterministic tests alone do not explain the behavior. Primary surfaces:cautilus evaluateand thecautilus-agentskill. - Bounded Improvement: improve a selected behavior target while preserving intent, explicit budget, protected checks, held-out evidence, and reviewable revision artifacts. Primary surfaces:
cautilus improveand thecautilus-agentskill.
Read this index first when judging the product story.
The main stories are ordered by the user's workflow.
Shared concerns (reviewability, evidence gaps, ownership, freshness, resumability) are carried as governed-by:: edges on each promise leaf and mapped in the Promise Ledger.
| args_json | stdout_includes |
|---|---|
["doctor", "commands","--json"] | claim |
["doctor", "commands","--json"] | eval |
["doctor", "commands","--json"] | improve |
["doctor","--help"] | Usage: |
["doctor","--repo-root","."] | ready |