live-scheduler.md is accurate -- worker_count 32, result_capacity 4096, batch_size 50, batch_timeout 500 ms and the verify_queue_dropped_events_total counter all verified against ingest/pipeline.zig. Three things a reader cannot see from the text. Per-DID pending capacity is key_queue_capacity = worker_count * 2, so the "thirty-two workers" and "64 pending events" in the contract are the same constant. They read as independent knobs; changing worker_count silently moves the drop-oldest threshold. That bound is also the one the batch submit/consume deadlock turned on, so it carries two responsibilities. "Graceful cutover" here means the shutdown handover -- stop admission, drain, tear down workers. Everywhere else in docs/ cutover is the lifecycle phase transition out of merge where serving stops 503ing. Two unrelated events sharing a word, in a file about the path that runs after that transition. Flagged both senses. Also expands Atmos on first use, and notes the constants are matched to upstream rather than chosen here -- which is why they are not tunable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>