the journal · a reading path
The trace family
One recorded file, five jobs. Follow the records in order. Each one stands alone; together they complete the argument.
- 005stopsin reading order
- 0114minutes end to endthe complete path
- 0249posts in the journalthe wider record
- 03evidence → custodythe arcfrom first record to last
sequencethe recordevidence
- Step 1 of 5: evidence. 01evidenceThe run becomes evidenceEvery 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.recollection3 minread →
- Step 2 of 5: replay. 02replayThe trace you can replayEvery run leaves a flight recorder: a deterministic AI audit trail you can replay like a film, never re-execute by accident.recollection2 minread →
- Step 3 of 5: resume. 03resumeThe resume storykill -9 a run mid-flight, then resume it: finished work never runs twice. Durability as a file property, shown from the real journal.recollection3 minread →
- Step 4 of 5: forecast. 04forecastThe forecast is localexplain --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.recollection3 minread →
- Step 5 of 5: custody. 05custodyThe chain of custodyA 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.recollection3 minread →