Labels

The audit trail and its sink: what a record carries, and whether it reaches anyone

Something isn't working

Build, test or release pipeline; not phase work

the hand-rolled streaming client for one vendor's API

what a gate is asked and what it is told; no policy

the provider key: which source it comes from, and the file it is kept in

argv parsing and the five subcommand bodies

which prefix of a history may be withheld, and the measurement that decides it

sandboxing; the only crate allowed to spawn a subprocess

the vocabulary a streamed turn is spoken in: one event per thing that arrived, and why it ended

the --allow-… flags, the policy they describe, and the directories a no-flag run refuses

the test-only helper binary and the enforcement suite that drives it

what the enforcement suite needs to start a sandboxed command, read its trail, and probe the host

the one tracing subscriber, and the hold the screen takes

what a model is asked for, in no API's vocabulary: the request shapes, carrying no Serialize

the provider seam: the stream a client hands back, and the error it can fail with

a pty pair for tests that drive a real terminal

the screen one turn is drawn on, and putting the terminal back

the translation between the stored transcript shapes and the provider's request shapes

why a session operation did not happen

a session's name, and the one rule that makes it safe in a path

the five shapes a transcript line is made of

where transcripts live: $XDG_STATE_HOME, else $HOME, never the working directory

the on-disk transcript: append-only JSONL under whatever root it is handed

Server-Sent Events framing over a byte stream, in no API's vocabulary

the one denylist of what model text may not carry to a terminal

the seven built-in tools, each confined by core

the keys that stop a turn, and what a hangup means

what the screen shows: the event fold, and the layout it is drawn in

the turn loop