// operations · evidence 04

Reproducible execution evidence

Evaluate Okami as an operating system, not as a prompt demo. This page shows the command, criteria, expected timeline, proof files and a versioned JSONL trace shipp…

Open in full documentation GitHub

Scenario

The smallest useful case is deliberate: create a file and prove its content. It separates the agent's promise from the observed workspace effect.

rm -f hello.txt
okami task "create hello.txt with hi" \
  -e file_exists:hello.txt \
  -e "file_contains:hello.txt:hi"
test -f hello.txt && grep -q hi hello.txt

Acceptance criteria

criterion	source	expected result
`file_exists:hello.txt`	filesystem	PASS when the file exists
`file_contains:hello.txt:hi`	filesystem	PASS when content matches
`task_complete`	harness	accepted only after criteria pass
exit code	process	`0` for COMPLETE, not for textual promise

Compact trace

docs/generated/evidence-task.trace.jsonl

{"kind":"task_start","goal":"create hello.txt with hi","exitCriteria":["file_exists:hello.txt","file_contains:hello.txt:hi"]}
{"kind":"tool_call","tool":"write_file","args":{"path":"hello.txt"},"approval":"auto","effect":true}
{"kind":"tool_result","tool":"write_file","ok":true,"summary":"hello.txt written"}
{"kind":"completion_check","criterion":"file_exists:hello.txt","status":"PASS"}
{"kind":"completion_check","criterion":"file_contains:hello.txt:hi","status":"PASS"}
{"kind":"task_complete","accepted":true,"exitCode":0}

Files that should exist

file	proof
`hello.txt`	observable final effect
`.okami/events.jsonl`	task, tool and checks timeline
`.okami/audit.jsonl`	tool, summarized args and approval log
`.okami/checkpoints/journal.jsonl`	pre-write snapshot when applicable
`docs/generated/evidence-task.trace.jsonl`	public reduced trace for docs review

Open this page in the interactive docs