nx_seat_meter_beat.nx

nx_seat_meter_beat.nx -- ES1 of /compare/engineshift: THE SCOREBOARD'S PRODUCER (laptop-local, 2026-09-02). nx_seat shift (F831) grades the engine shift from knowledge/status/token_efficiency.log, and every row that log has ever held was appended BY HAND: 16 rows, the last dated 2026-08-05, no hook, clock row or organ names `nx_seat meter`. A gauge whose rows are hand-appended is a diary, not a gauge -- it stops the day the hand stops and reads as "no movement" forever (the local column read ZERO for 44 days and was quoted twice as a finding about the estate). This organ is the producer. It rides the SessionStart hook beside nx_crashwin. WHAT IT MEASURES. Every Claude Code transcript (<sessions>/*.jsonl) carries one line per assistant content block, and EVERY block of one message repeats that message's usage object (measured 2026-09-02: 367 assistant lines for 58 distinct message ids in one transcript). So usage is counted ONCE PER MESSAGE ID, never per line; a naive sum overcounts about six-fold. Per complete UTC day and model family it sums output_tokens, cache_read_input_tokens and cache_creation_input_tokens, counts messages, and counts the transcripts active that day (the row's `sessions` column). A line is an assistant line when it carries a raw "type":"assistant" (tool results are escaped strings and cannot); the message's OWN model, id and usage are the DEPTH-1 children of "message":{ -- a tool_use input is raw JSON and may carry model and id fields of its own, so position on the line decides nothing (neg-controls in the gate). Harness API-error lines (model "<synthetic>") are their own bucket. nx_seat_meter_beat scan <sessions-dir> [--now <epoch>] [--days N] prints one DAY row per (day, family) inside the window and a METERBEAT summary; writes nothing. nx_seat_meter_beat beat <sessions-dir> <state-dir> <mcp-elf> <base-url> <cap-file> [--now <epoch>] [--days N] [--dry] [--json] for every COMPLETE day (strictly before today, UTC) in the window whose (day, family) is not yet in <state-dir>/meterbeat.days, forks <mcp-elf> (nx_mcp_call) to run `nx_seat meter` on the estate and, on the reply "METERED row appended", records the marker -- idempotent by day marker: a second run appends nothing. --dry plans and prints, forks nothing, marks nothing. --json wraps the digest as a SessionStart hook envelope and exits 0 (the hook framework parses stdout only on exit 0). Today is NEVER pushed: an incomplete day would be re-summed tomorrow and the marker would make it final. Window: --days N (default MB_DAYS_DEFAULT) complete days; transcripts whose mtime predates the window start are not read (they cannot carry a newer day), so a session-start run touches only recent files. A transcript whose last line has no newline is counted PARTIAL: its complete lines count, the tail does not, and the summary says so -- a truncated file is never read as zero. Exit: 0 GREEN | 1 RED (a push was refused or answered without the METERED receipt) | 2 usage | 3 UNOBSERVABLE (the sessions dir cannot be opened). verdict= is the LAST token of the last line. license_tier: ORIGINAL. Writes only <state-dir>/meterbeat.days. No hw writes (Rule 26).