Repository navigation
feat: a leg is told what its session left half done — read from what landed, said after the conversation (greenhouse decisions/0604) - #766
Merged
Conversation
…landed, said after the conversation Rule D of greenhouse decisions/0604, decided by Rod on 2026-10-08. A leg that inherits a fold knew the session's plan and its todos; that an operation stood scaffolded with its body to write was a fact nowhere. In the legs that followed one that ran out of window, 15 of 31 reads were of something an earlier leg had already read (evidence/1164). The house already knows which operation scaffolds stand: its closure refuses a capability while one does (decisions/0595). The leg is now told that same list — the files where `make what=operation` landed a scaffold that no later change that landed has written. There is one rule, the closure's; this reads it and says it. It rides with the locators of recorded results: read again from the record on every model call and written after the conversation. So it stays true inside the leg, and the beginning of the request does not move when the list changes. When nothing stands, not a byte is said. A first cut, kept as a draft, read the calls a session made and said it once at the start of a leg: it listed a scaffold whose trial was discarded, took one off for an authoring call that never landed, and went stale inside the leg. This reads only what landed, and reads it every time.
…what-stands-half-done
rodrigoteamx
added a commit
that referenced
this pull request
Oct 9, 2026
… its leg) One line clashed, in the return shape of HouseObservedClosure::of(): this branch adds what a capability's observation may carry once the house ran it, main adds the files where a scaffold still stands. Resolved by hand to the line that says both. AgentOperations.php, which both touch, merged by itself.
This was referenced Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A leg is told what its session left half done: the operations that stand scaffolded with their body to write. Rule D of greenhouse decisions/0604, decided by Rod on 2026-10-08.
Why
A leg that inherits a fold is told the session's plan and its todos, and of a past call only a few names. That an operation was scaffolded and its body never written was a fact nowhere: in the legs that followed one that ran out of window, 15 of 31 reads were of something an earlier leg had already read (greenhouse evidence/1164).
What it does
make what=operationstands one at the file it landed, and any other writer that lands that file takes it down. The leg is told that same list. There is one rule, the closure's;HouseObservedClosure::of()now returns it asstanding, andWhatStandsHalfDonereads it and says it.What changed from the draft
#762 was the first cut, kept as an experiment while the rule was undecided. It read the calls a session MADE and said the list once, at the start of a leg. A real run and its own notes showed three faults, and this removes each:
It supersedes #762.
Tests
Written red first.
WhatStandsHalfDoneIsReadFromTheRecordTest(13): what stands and what does not, the order, the bound, a file name that tries to close the section, the same declarations of what lasts as the closure, and that the list is the one the closure counts.ALegIsToldWhatStandsHalfDoneTest(4): legs the house itself assembles — the loop is handed the list after the conversation, a file leaves it inside the same leg the moment its writer lands, and the system prompt never says it.scripts/lab/half-done-1172/mutants.pyin greenhouse).Measured, with no model
A build walked by the scripted stand-in on a kept house, this branch laid over it inside the running container, each leg capped at ten steps so that legs end where a scaffold stands (greenhouse evidence/1172):
The files are read from the house, not from its record. Inside a leg the list grew and shrank four times as operations were scaffolded and written. The walk ends the same in both — the stand-in does not read what it is told — so this shows that the house says the truth, not what a resident does with it.
What it does not do