Repository navigation
feat: after a pause for window or for steps the house goes on by itself, once, under a written cap (greenhouse decisions/0604) - #769
Merged
Conversation
…lf, once, under a written cap (greenhouse decisions/0604) A leg in auto that ran out of window, or of steps, ended, and somebody had to start it again. The house now goes on inside the same invocation: a second leg of the same session, opened by a notice of the house that says why it follows, as it already resumes a turn that echoed its own voice (decisions/0475). The cap is Rod's, of 2026-10-08, and is two written values in HouseGoesOn: one continuation per invocation, and sixty steps in all counting those before the pause — also after the steps run out, not only the window. A house may declare others (agent.continuations, agent.invocationSteps). The leg that follows takes what is left of the total and never more than a leg's own ceiling. A ceiling a person typed is the total. It never goes on over a pause that waits for a person, nor after an end: an exhausted epilogue is an end. A pause the house continues closes nothing; the closure belongs to the leg that ends in an answer. The session records session.leg_continued before the leg that follows, and the result carries wentOn.
…the-house-goes-on
…thing closes there (greenhouse decisions/0604, decisions/0605) Where two rules meet at the end of a leg: the house runs a capability before it closes on it, at a leg's natural end; and after a pause for window or for steps the house goes on by itself. A leg the house is about to continue has not ended: over a record that would close, nothing is run and no verdict is recorded at the pause; the leg that follows runs it once at its answer, and the verdict comes after. When that leg pauses too, nothing at all. An exhausted epilogue is an end, and the house does not go on after it. The rule's own tests now hand the house's progress probe to the loop, as a leg does.
…the-house-goes-on
… house ran and threw, each in its own message (greenhouse decisions/0604, decisions/0605) With main merged in, four rules meet in one request: the house's notice that opens the leg that follows a pause, and after the conversation the section that names what the house ran and threw. The notice is one message and nothing more; the section is said once, last, and does not carry the notice. What threw still stands when that leg answers: nothing landed, so the house does not run it again and does not close.
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.
Rule A of greenhouse decisions/0604, with the cap Rod decided on 2026-10-08. It stands on rule D (#766) and meets R1 (#767) at the end of a leg; both, and #770 — what the house ran and threw is said to the session that wrote it —, are in
mainand merged into this branch.What it does
A leg in
autothat ran out of window, or of steps, ended, and somebody had to start it again: a person, or a conductor spending one of its legs. Now the house goes on inside the same invocation — a second leg of the same session, the way it already resumes a turn that echoed its own voice (decisions/0475):session.leg_continued(after,steps_before,steps_left,time,cap,by: house) before the leg that follows starts;[house]notice that says why it follows, never a turn a reader could take for a person's;wentOn: {times, after, stepsBefore, stepsInAll};stepsstays the count of the leg that ended.The cap
Two written values in
HouseGoesOn, as Rod decided them:agent.continuations(0 turns it off)agent.invocationStepsIt goes on after the steps run out as well as after the window. Sixty is one and a half times the forty decisions/0538 gave a leg in
auto: this is where an invocation may spend more than that record said.What it never goes on over
auto;--stepsa caller typed, which is the total.A pause the house continues is not an end
The invariant with #767 (before it closes on a capability, the house runs it once). A leg the house is about to continue has not ended: over a record that at that moment WOULD close, nothing is run and no verdict is recorded at the pause. The leg that follows runs the capability once at its answer, and the verdict is recorded after it. When that leg pauses too, nothing at all.
APauseTheHouseContinuesIsNotAnEndTestfixes it on the fixture #767 left, for a step pause and for a window pause, asserting the order by seq and not only the counts.With #770 in, the same class fixes where the four pieces meet in one request: the leg that follows a pause is opened by the house's notice — one message, and nothing more — and after the conversation it is told what the house ran and threw. Neither is inside the other.
Readings that are mine, not Rod's
Rod decided «one continuation, sixty steps in all, also after the steps». These follow from how I built it and are one line each to change:
--stepsis the total.--steps 5runs five steps and the house does not go on; after a window pause it goes on with the rest of what was typed.stepscounts it: a window pause after two model calls reports three.agent.invocationStepssays: a total below it means the house never goes on.What a caller sees change
session.run_terminatedfacts, withsession.leg_continuedbetween them. Whoever counts legs by invocations, or invocations by terminations, counts differently now.automay take up to sixty steps where it took forty.wentOn. A leg that paused and was continued leaves no result of its own: only its facts.Checks
TheHouseGoesOnAfterAPauseTest) and 6 of the invariant (APauseTheHouseContinuesIsNotAnEndTest), written red first; 1 more of the notice beside what threw, written green and checked with four mutants that each turn it redscripts/lab/goes-on-1172/mutants.py); with #770 merged in, all 51 still apply and the five of the invariant were run again, redmaininside (D, R1, #770 and this rule together)Measured on cattle, without a model
Greenhouse evidence/1172, part A (getmilpa/greenhouse#393), measured at
48e6b2d— before #770 was merged in; it was not walked again. A kept house, that commit laid over inside the running container, the scripted stand-in — which is not a model — and no--stepstyped. No image was built.mainwithout itagent.invocationSteps = 20)agent.continuations = 0main, one for oneWhat it does not show: anything with a real resident. And in the long walk the rule does not save the conductor an invocation — the task needs 67 steps, three invocations with 60 + 7 as with 40 + 27; it saves one when what is left fits in what the cap leaves.