the journal · by tag
Engine
Every post filed under Engine, newest first — one register of 7 the journal keeps. The shelf lens on the journal filters the same set in place.
- 0014postsin this register
- 017tagsthe journal keeps
- 0233posts in the journalall registers together
- 032026-07-14latestnewest first below
14The registry re-proves everythingA workflow registry where nothing is taken on faith: every entry is content-pinned to an exact source revision and re-proven by CI (hash, certificate, advisories). The npm-of-workflows, minus the trust-me.13The MCP server you didn't have to buildEveryone is learning how to build an MCP server. For your workflows, skip the tutorial: the nika binary already is one. Read-only tools let any agent audit a plan and learn the language from the thing that enforces it.12The 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.11The 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.10The run that waits for youThe approval gate is a task in the file, not a Slack thread: a plan fails closed on nika:prompt, and the human's answer rides the resume.09The 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.08The one-task re-runRegenerate one block without re-running the world: --task scopes a fresh run to a task and its upstream, --from re-rolls what the hashes cannot see.07The 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.06Time travel, for realEvery debugger replays the past by re-running it. Nika's past is a file, so stepping backward is free, breakpoints live in your YAML, and F5 debugs a run that already happened.05The editor tells the truthA green badge is a claim. We audited the editor extension against the engine the way you'd audit a client against a server, and found the badge lying. Here is the contract that keeps it honest now.04Media are workflow citizensImages and speech now render inside workflows under the same discipline as everything else: permit-gated saves, sha256 provenance, honest warnings, real cost on the ledger, and the sovereign path first.03The 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.02The cost lineThe audit prices every token before it is spent: ceilings on generations, budgets on loops, and a $0.00 that means it.01The plan you get for freeThe wiring is all you write: with: for data, after: for order. The plan falls out of the file: parallel waves, drawn before anything runs.