THE CONNECTED RECORD
Find the question. Follow the work. Return to the source.
4 THREAD · 4 SYSTEMS · 31 NOTEBOOK ENTRIES · 2 QUESTIONS · 242 FILMS · 239 CHAPTERS
Search the authored text, its questions and refusals, and the films around it. Drafts keep their status. Chapters identify a topic and a time; only the 2 indexed transcripts provide spoken passages, and their automatic captions are unreviewed. This edition retrieves sources rather than generating an answer. Explore what is connected ↗
2 RESULTS FOR “My CI has to undo my coding agent.”
EDITORIAL DRAFT · ONGOING · V0.1
A short visual note about a coding agent adding generated-attribution metadata after being told not to. LARQL’s required pull-request check cannot edit immutable commits; it rejects Claude co-author trailers, session metadata, generator credit lines and session URLs until the affected metadata is rewritten. The mundane disagreement exposes the real question: which instruction is allowed to decide?
READ THIS DRAFT ↗EDITORIAL DRAFT / OBSERVATION · ONGOING · V0.1
01 / WHAT HAPPENED. I tell the coding agent not to add generated attribution. The session adds it anyway. By the time the contribution reaches a pull request, the repository has to restate the boundary as executable policy. The check does not erase an immutable commit in place; it refuses the contribution until its metadata is rewritten.
READ THIS DRAFT ↗