← the journal 5 stops · in reading order the journal · a reading path
The trace family One recorded file, five jobs. Read the stops in order — each one stands alone, together they make the argument. The posts carry the same rail on their own pages.
00 5 stops in reading order 01 14 minutes end to end the whole path 02 1 path the journal keeps 03 33 posts in the journal the wider shelf 01 · evidence The run becomes evidence Every journal line now carries a hash chain: verify names the first broken link, reproduce classifies every task, and the journal attests which engine wrote it. Trust, but verify. Then verify. 02 · replay The trace you can replay Every run leaves a flight recorder: a deterministic AI audit trail you can replay like a film, never re-execute by accident. 03 · resume The resume story kill -9 a run mid-flight, then resume it: finished work never runs twice. Durability as a file property, shown from the real journal. 04 · forecast The forecast is local explain --forecast computes duration and cost priors from your own recorded runs: stats over .nika/traces/, honest ranges at two runs, percentiles at five. Never a model call, never the network. 05 · custody The chain of custody A recorded run is a text file, and text files can be edited. nika trace verify recomputes the hash chain: one changed word in history breaks every line after it, and the run's printed head closes the loop.