Development record
itd-59 says the autonomous worker leaves only an ephemeral, pruned log; the build brief says a runner's transcript lands in the history store
itd-59 says the autonomous worker leaves only an ephemeral, pruned log; the build brief says a runner's transcript lands in the history store
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-59-autonomous-worker-transcript-capture.md:19— "emits its instructions and reasoning only to an ephemeral per-pass log that run-dir hygiene prunes" - End B:
.abcd/development/brief/04-surfaces/34-build.md:499— "the runner's transcript lands in abcd's history store, keyed on the repository's root commit"
itd-59 aims to close a gap. Its premise is that the unattended worker writes its instructions and reasoning only to a per-pass log that run-dir hygiene prunes. The build chapter says the transcript of a runner the step verb starts lands in abcd's history store, keyed on the repository's root commit, and that the record verb stores the run's transcripts there at the end. If the build chapter is right, the gap itd-59 describes is already closed for the loop that ships.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 723.
Frontmatter
| id | iss-2610262037262122 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037262122-itd-59-says-the-autonomous-worker-leaves.md
open on GitHub ↗ · commit history ↗
References1
- itd-59Every Autonomous Run Pass Leaves the Same Durable, Queryable Transcript an Interactive Session Doesrelated
mentions2
- iss-2610262044057318itd-59 and itd-2609201916151817 both claim capturing the autonomous run's transcripts into the transcript store
- iss-2610262044255432The worker-transcript draft says autonomous passes leave only an ephemeral log, but the shipped runner captures every role's transcript into abcd's store