Every recording on this page is a scripted run of real commands, regenerated when the code changes. The .tape link on each is the script that produced it. Nothing here is staged to look better than what the command actually does.
RECORDING FORTHCOMING: full QEMU boot — MMU/cache init, GIC, scheduler, first timer interrupt, CSPRNG, every subsystem's init step, boot-to-service handoff, banner, service loop ticking
What this shows: The exact command sequence CI already runs on every push, ending on the service loop visibly ticking. What it doesn’t show: Hardware bring-up on the physical AGM M7 — that stays open regardless of what the recording shows.
kanon · lint --fix, then gate · run against the public aletheia repo
RECORDING FORTHCOMING: kanon lint finds a violation (seeded, labeled on-screen as SEEDED VIOLATION — LABELED IN-CAST) → kanon lint --fix clears the mechanical class → kanon gate runs clean
What this shows: The standards engine finding and fixing a real violation class, then passing a clean gate — against a public repo. What it doesn’t show: kanon's own source. Private by choice, not by necessity.
aletheia · memory recall across turns · local model, no cloud key
RECORDING FORTHCOMING: TUI session — state a fact in turn 1, ask something unrelated in turn 2, ask for recall in turn 3, agent cites the turn-1 fact back correctly
What this shows: A fact stated in turn 1, recalled correctly and cited back in turn 3, against a local model with no cloud API key. What it doesn’t show: The desktop app — a v1.0-target preview, not the default onboarding path this recording uses.
logismos · CPU golden-fixture parity test · phase_3_stella_parity, against a committed fixture
RECORDING FORTHCOMING: cargo test -p logismos --test phase_3_stella_parity passing against the committed CPU baseline fixture
What this shows: The correctness harness passing on CPU, against a fixture committed to the repo. What it doesn’t show: Any GPU run. Phase 4 is hardware-blocked; this recording won't stage one.
harmonia · server boot, health check, library scan · seeded sample media only
RECORDING FORTHCOMING: harmonia serve boots → a health check answers → a library scan triggers → its import queue populates
What this shows: A real server boot, a health check answering, and a library scan populating an import queue. What it doesn’t show: The two HTTP-layer resolvers still stubbed for metadata resolution and curation.
hamma · handshake + control-protocol type tests · hamma-core, dictyon
RECORDING FORTHCOMING: cargo test -p hamma-core && cargo test -p dictyon — the Noise-handshake and control-protocol-type tests passing
What this shows: The Noise-handshake and control-protocol-type tests passing — modest, explicitly test-suite-shaped. What it doesn’t show: Two peers joining a tailnet. That moment doesn't exist yet.