How the economy evolved20 versions

From the first draft to 2.9.0

Each version answered something the runs under the one before had shown. For each: what went wrong, what changed, what the runs found, and what was concluded.

The runs on these pages are simulations. The actors in them were small programs trained inside the simulation, not language-model agents.

Show
Changes the explanations on this page: the passages, and what opens when you press +. Headlines and pictures stay the same. Your choice stays as you move between pages.
Show
Each card: what the version added, and what went wrong with it, which the next version answered. + explains both.
  1. v0.1 to v1.0.1

    2026-10-15 · none (reviews R01 to R10)

    Ten reviews to a frozen baseline

    What was added

    Each problem was fixed in the next draft; version 1.0.1 fixed only wording and changed no rule.

    What went wrong with it

    One pot paid back costs and the rest was the fee, so care cut a careful inspector's fee.

    a careful inspector earned 7.9 per review, a stamper 9.5Care paid back from the fee's own pot

    What was added

    Each problem a review found was fixed in the next draft, and the rule sending approved work back was taken out again. Version 1.0 gathered every rule into one standalone document; 1.0.1 corrected four wordings and changed no rule.

    Each problem was fixed in the next draft. The rule that sent approved work back was taken out again in version 0.10. Version 1.0 put all the rules into one document that stands on its own. The tenth review found only four places where the wording was wrong. Version 1.0.1 fixed that wording and changed no rule.

    The tests that check the program against the rules grew along the way, from 104 at version 0.7 to 156 at version 1.0.1.

    Each finding was closed in the next version. v0.10 withdrew reopening and added a change discipline (§19) separating three kinds of change: to the rules, to the engine's conformance with them, and to strategies within them. v1.0 consolidated everything into a standalone baseline. The tenth review found four wording errata, for example that "only a human rules" should read "only a human overrides", since the orchestrator rules on split panels. v1.0.1 applied them with no change to any rule, default, permitted operation or the engine.

    The engine's test suite grew from 104 passing tests at v0.7 to 156 at v1.0.1. The reviewers' tests were copied into the suite. The record notes that this cannot be re-verified byte for byte from the repository alone, since the original test bundles are not in it.

    Activity Question Appropriate action
    Rulebook design What is allowed, owed, observed, and final? Change only for an explicit design decision or unresolved rule contradiction
    Implementation conformance Does the engine perform those rules, including refusals and timing? Patch the engine and add a regression without introducing a different permitted behavior
    Strategy research Which allowed choices work well for participants or the system? Separate investigation against a fixed rulebook and specified settings

    Source: reviews/R09_of_v0_10.md l.15–19

    Four textual corrections from the tenth review [R10]. Each clarifies a decision already made; none changes a rule, a default, a permitted operation, or the engine.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1107

    | E1 | §1, §15.2, closing | "Only a human rules," while §8.4 has the orchestrator rule on a split; §1 credited every root requester, delegates included, with non-model judgment | The orchestrator rules on procedural disagreements (splits); only a human may issue the override; a delegate's judgment is a model's and is graded as such (§15.3) | The two senses of "ruling" contradicted each other read literally; the label grades already kept the distinction |

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1111

    Test suite across versions: v0.7 104 + 1 xfail → v0.8 123 + 1 → v0.9 148 + 1 → v0.10 152 + 24 → v1.0.1 156 + 24

    Source: HANDOFF.md l.43–44

    The reviewers' test bundles themselves are not in this repo — they arrived as separate archives and were copied into agentic_sim/tests/test_review*.py at the time; the reports name the tests they shipped, so names and counts can be compared, but byte-for-byte verbatimness cannot be re-verified from this repo alone.

    Source: reviews/README.md l.20–22

    What went wrong with v0.1 to v1.0.1 (from 1.1.0's record)

    Each task had one pot of money for checking. It first paid back the inspector's costs, and what was left became the fee, so every credit a careful inspector spent on checking was a credit of fee it lost.

    Under version 1.0.1, each task came with one pot of money for checking it. The pot first paid back the inspector's costs. What was left over became the inspector's fee. So every credit a careful inspector spent on checking was a credit of fee it lost.

    The first run showed what this did. With half the inspectors stamping, the stampers ended richer in four of five repeat runs. A careful inspector earned 7.9 per review and a stamper 9.5. The gap was the careful inspector's own costs.

    The first draft of the rulebook had agreed on a fixed fee for checking work. A later draft made the fee whatever was left over, but the rulebook's own reasoning still assumed the fixed fee.

    Under v1.0.1 each case carried one verification deposit doing two jobs: it reimbursed the inspectors' capped expenses, and paid what remained as their fee. Every credit reimbursed was a credit of fee lost; in the record's words, "the accounting closed; the incentive inverted."

    Strategy run 1 measured it. With half the inspectors on duty (the "reserve") stamping, stampers ended richer in four of five seeds. A careful inspector earned 7.9 per review and a stamper 9.5, a gap equal to the careful inspector's own expenses. 47% of truly failed work was paid in full, and 88% with nine stampers in ten.

    The record traces the rule's history. v0.1 had agreed a capped expense reimbursement plus a fixed fee, "for review work, not for the answer". v0.3, repairing a shortfall the second review found, made the fee the deposit's remainder. The spec's §7.3 kept reasoning with the fixed fee.

    Finding [S1]. Strategy run 1 (October 16, 2026): at the defaults, with half the reserve stamping, stampers ended richer in four of five seeds; 47% of truly failed work was paid in full, 88% with nine stampers in ten. The channel was the fee: a careful reviewer earned 7.9 per review and a stamper 9.5 — a gap equal to the careful reviewer's own expenses.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1138

    Mechanism. Under 1.0.1 §4.3 the deposit was one pot doing two jobs: reimbursing capped expenses, and paying what remained as the fee. Every credit reimbursed was a credit of fee lost. The rule charged for diligence at the margin, while 1.0.1 §7.3 still reasoned with the fixed fee of v0.1 R16–R17 ("capped expense reimbursement plus a fixed fee … for review work, not for the answer"), which v0.3 had replaced by the remainder when it repaired the second review's shortfall finding. The accounting closed; the incentive inverted.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1140

  2. 1.1.0

    2026-10-17 · Design revision 1

    The verification deposit is two pots

    What was added

    One pot pays back costs up to a cap; the other pays a fixed fee set by role.

    expense pot costs, up to a cap inspector

    What went wrong with it

    Every signal came from inspector panels, so once stampers held the panels, the system could not see.

    stampers richer by 200 per actorAppeals alone, half stampers, eight on duty
    Answered by 1.2.0 Open 1.1.0 →

    What was added

    The pot is split in two. One pays back the inspector's costs up to a cap; the other pays a fixed fee set by the inspector's role. Whatever is left in both goes back to the requester when the task closes.

    Version 1.1.0 splits the pot in two. One pot pays back the inspector's costs. The other pays a fixed fee set by the inspector's role. Costs are paid back up to a cap, so care within that cap now costs the inspector nothing. When the task and all its sub-tasks are closed, whatever is left in both pots goes back to the person who asked for the work.

    The change was reviewed twice before it was accepted. The reviews found mistakes in the first draft. One was the claim that "nothing else moves": in fact, in the common case, the money inspectors earn from these pots falls by about three quarters.

    Design revision 1 was the first change to the rulebook since the freeze and the first use of the §19 design-revision path. The deposit becomes two pots: an expense allowance and a fee pot. Expenses are paid from the allowance alone. Each inspector whose verdict stood gets a fixed fee set by role from the fee pot, scaled down only when the pot is short, plus its share of emission, a separate payment to inspectors whose verdicts stood. When the whole delegation tree closes, the fee pot's remainder pays what the orchestrator advanced, and then both pots' remainders return to the requester. Care within the expense cap costs the inspector nothing.

    The record's arithmetic for a stamper's money term per review turns negative: about −0.3 at run 1's effective catch rate of 3%, −0.7 at the nominal audit odds. An appeals term is added once actors appeal.

    The revision went through two implementation reviews before acceptance as rc.3. rc.1 had computed "unowed fee money" per case, which in a tree would have paid a root's expenses with money its nested case's inspectors were still owed. rc.1 also said "nothing else moves", when inspector income from deposits falls by about three quarters in the common case. The tie band and the audit floor, also implicated by run 1, were left as defaults to be swept separately.

    The first change to the rulebook since the freeze, and the first use of §19's design-revision path. The stamping result above was read against the text and the history: v0.1 R16–R17 had agreed "capped expense reimbursement plus a fixed fee … for review work, not for the answer"; v0.3, repairing the second review's shortfall finding, made the fee the deposit's remainder after reimbursements, and from then on every credit of care reimbursed was a credit of fee lost — while §7.3 still reasoned with the fixed fee. The revision was written as a release candidate (spec/design_revisions/), read on its own through two implementation reviews — rc.1 computed "unowed fee money" per case, which in a tree would have paid a root's expenses with money its nested case's reviewers were still owed (reviewer test r4_07 is the shape); rc.1 said "nothing else moves" when reviewer income from deposits falls by about three quarters in the common case; the hypothesis needed its appeals term; I10 and record mode gain the tree consequences; the rerun needs twenty seeds or more — and accepted as rc.3.

    Source: HANDOFF.md l.506–516

    One payout rule (1.1.0): expense debts for every review from the allowance alone → each survivor's fixed fee w_r·f (2 / 3 / 3) from the fee pot, scaled only when the pot is short, plus its emission share in full → at tree closure the pot's remainder pays the tree's Ω claims and advances, then both pots' remainders return to the requester. Care within K costs the reviewer nothing.

    Source: HANDOFF.md l.61–64

    Consequence. Within the cap, care costs the reviewer nothing: a careful reviewer that spends c≤Kc\le K is made whole and earns the same fee as one that spent nothing.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.357

    Emission E_t = E_0·2^(−t/H) pays reviewers whose verdicts stood, by role weight; nothing carried forward.

    Source: HANDOFF.md l.59–60

    Under 1.1.0 the fee is fixed and care within K is made whole, so the money term per review is −p·b·(1−ε)·(f̄ + G^V): about −0.3 at run 1's effective catch rate (3%), −0.7 at the nominal p = 0.5, b = 0.2, with an appeals term a·ε·(1−b)·(f̄ + G^V) once actors appeal.

    Source: HANDOFF.md l.99–101

    The selection tie band and the audit floor, which the run also implicated, were left as defaults, to be swept separately.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1142

    What went wrong with 1.1.0 (from 1.2.0's record)

    Workers appealed wrong rejections and requesters disputed wrong approvals, and panels of inspectors judged both. When nine in ten inspectors were stampers, the panels were mostly stampers, disputes failed, and the system had no other way to see the truth.

    Under 1.1.0, the worker policed wrong rejections by appealing, and the person who asked for the work policed wrong approvals by disputing.

    With appeals alone, a careful inspector's few mistakes were punished almost every time. A stamper's mistakes were caught about 3% of the time. The stampers ended richer. When nine in ten inspectors were stampers, every panel that judged a challenge was mostly stampers. Disputes failed, and no rate of disputes fixed it.

    Every signal the system had came from these panels. So once stampers held the panels, the system could not see its own state. The designers then made an assumption the rules had left unsaid: humans do not step in. That took away the one outside source of truth the rules had leaned on.

    Under 1.1.0 the actor polices rejections, by appealing, and the requester polices approvals, by disputing. Runs 2 and 3, 1,295 runs in all, showed what follows. With appeals alone, a careful inspector's 5% false rejections were punished almost every time and a stamper's negligence was caught about 3% of the time, so stampers ended richer (+200 per actor at 50/50 with eight on duty). A requester disputing one bad result in four reversed that, with break-even near a dispute rate of 0.07. At 10/90 every panel was stamper-majority: disputes failed (23 of 135 won), and selection handed the stampers the awards, 159 to 66.

    The record's diagnosis is that every signal the loop produced was panel-produced, so under capture the loop was blind to its own state. The same day, the design added an assumption the baseline had left implicit: humans do not intervene. That removes the one external oracle the loop leaned on.

    Finding [S2]. Runs 2 and 3 (October 17, 2026; 1,295 runs under 1.1.0). The actor polices rejections (appeals, a≈0.98a\approx0.98); the requester polices approvals (disputes). With appeals alone a careful reviewer's 5% false rejections are punished almost every time while a stamper's negligence is caught about 3% of the time, and stampers end richer (+200 per actor at 50/50, X=8X=8); with the requester disputing one bad result in four, careful ends richer by 489; break-even is a dispute rate of about 0.07, and careful review pays only above an accuracy of about 92% at that rate. At 10/90 every panel is stamper-majority: disputes fail (23 of 135 won), only the careful minority's errors are adjudicated, their ρ\rho ends below the stampers', selection hands the stampers the awards (159 to 66), and no dispute rate recovers it. At GV=20G^V=20 about 7% of duty slot-ticks are held by actors who cannot fund the bond and the reserve starves.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1158

    Mechanism. Every signal the loop produced was panel-produced, so under capture the loop was blind to its own state; the design assumption that humans do not intervene removes the one external oracle the baseline leaned on. The orchestrator therefore owns some truth itself: the truth of the work it writes. Planted work (§7.6) gives a measurement no panel can paint; the plant record (§11.2) turns it into eligibility a captured majority cannot protect; the dial (§12.2) turns it into effort that rises with the threat and eases without it, and into the reserve's size and the security tax.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1160

    Run 3's reading was that three measured inputs decided the careful–careless contest under 1.1.0 — whether the party who knows the truth challenges, how often the careful reviewer errs, and who sits on the panel — and that the third was the rule's: a stamper-majority reserve produces every signal the loop has, reliability included, so no remedy that leans on ρ can cure it. The design discussion the same day added the assumption the baseline had left implicit — humans do not intervene — which removes the one external oracle the loop leaned on.

    Source: HANDOFF.md l.603–608

  3. 1.2.0

    2026-10-17 · Design revision 2

    The loop's own clock

    What was added

    The orchestrator plants cases with a known answer; an inspector with a bad record can be suspended.

    orchestrator plants cases with a known answer inspector judged by the known answer record

    What went wrong with it

    Suspension freed stampers from inspecting, so they took the paid tasks while careful inspectors did the inspecting.

    suspended stampers took paid tasks at 20, richer in 19 of 20Careful inspectors on duty for 2 a review
    Answered by 1.3.0 Open 1.2.0 →

    What was added

    The orchestrator plants cases whose right answer it already knows, and keeps each inspector's record on them, judged by that answer, not by a panel. A dial raises plants, audits, inspectors on duty and the fee when bad approvals of planted cases rise.

    Version 1.2.0 gives the orchestrator truth of its own. The orchestrator plants test tasks whose right answer it already knows. Each inspector gets a record of how it did on planted tasks, judged by the known answer and not by a panel. An inspector with a bad record can be suspended from inspecting. Nobody may challenge a planted task.

    A dial reads, once a period, how often inspectors approve bad planted tasks. When that rate rises, the dial raises the number of plants, the odds of an audit, the number of inspectors on duty and the service fee. When the rate falls, they ease. If there are not enough inspectors with good records, the system runs short and says so. It does not seat careless inspectors to fill the gap.

    The written rule for a suspended inspector, read literally, made every suspension permanent. The program used a smaller reading: after the suspension, the inspector comes back on probation and is checked again on its next planted task. That reading was later confirmed as the rule, in version 1.2.1.

    Design revision 2 gives the orchestrator its own truth. It writes planted work whose fulfillment it knows by construction. Each actor carries a plant record, adjudicated by that truth and not by a panel, with two eligibility tiers. An effort dial reads the reserve's bad-plant approval rate once a period. It moves the plant rate, the audit odds, the reserve's size and the service fee with it. The record calls it "the block-difficulty adjustment with negligence in place of block time". A reserve short of eligible actors runs short and says so. No settlement, verdict or challenge rule of 1.1.0 changed; no challenge is admitted on a plant, and the actor's identity leaves the inspector's view.

    Three release candidates were reviewed. One catch: rc.2 cleared the record when a suspended actor returned, which would have readmitted every stamper with a clean slate. In the accepted text the record persists. At implementation this made the literal suspension rule permanent, because a suspended actor judges no plants and so its record can never recover. The engine read it as readmission on probation, to duty but not to panels, until the next plant re-checks the record. Patch 1.2.1 confirmed that reading as the rule.

    The revision gives the orchestrator truth of its own: planted work whose fulfillment it knows by construction (§7.6), a plant record per actor adjudicated by that truth and not by the panel, in two eligibility tiers (§11.2), and an effort dial that reads the reserve's bad-plant approval rate once a period and moves the plant rate, the audit odds, the reserve's size and the service fee with it — "the block-difficulty adjustment with negligence in place of block time" (§12.2). A reserve that runs short of eligible actors runs short and says so; the loop does not seat the negligent to make a number.

    Source: HANDOFF.md l.608–614

    It adds a mechanism; it does not alter any settlement, verdict or challenge rule of 1.1.0. It changes what participants may do (the orchestrator creates plants; an actor can be suspended from duty; no challenge is admitted on a plant), what they may see (§14), and makes two fixed quantities endogenous (XX, ω\omega).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1162

    Reviews. Three release candidates, each read on its own (spec/design_revisions/dr2_1.2.0-rc.*-review.md). rc.1: the plant actor was named in a view that carried the actor (§14) — the actor leaves the view;

    Source: HANDOFF.md l.616–618

    rc.2: clearing the record on return would have readmitted every stamper with a clean slate for ~50 reviews and kept panels captured at ~70% strength — the record persists;

    Source: HANDOFF.md l.622–624

    Found at implementation — flagged for confirmation. With the record persisting, "at the end of the suspension it is readmitted only if its record passes, and otherwise remains suspended for a further T_susp" makes every suspension permanent: the record is a trailing window of plant outcomes and a suspended actor judges no plants, so a record that failed cannot pass later. That leaves T_susp inert and contradicts the revision's §2.4 and its §8 run 2. The engine implements the smallest reading that gives T_susp its meaning: readmission on probation — to duty, not to panels — until the actor's next plant re-checks the record, with a still-failing record suspended again at once (§11.2 of the consolidated text, Appendix G, World._rotate).

    Source: HANDOFF.md l.628–634

    Confirmed as the rule in force by patch 1.2.1 (October 17, 2026; the sentence of design revision 3 rc.1's Appendix A), applied to spec/agentic_economics_loop_spec_v1_2_1.md; 1.2.0 to history.

    Source: HANDOFF.md l.638–639

    What went wrong with 1.2.0 (from 1.3.0's record)

    A suspended stamper was only barred from inspecting, so it was free to take the paid tasks at 20 each. The careful inspectors, the only ones still allowed to inspect, did 500 to 800 reviews each for a fee of 2.

    Under 1.2.0 the planted tasks kept the system honest. But it was slow. Tasks spent 47 times as long waiting for an inspector, about 40% fewer tasks were completed, and the orchestrator could not pay for a third of the plants the dial asked for.

    Worse, being suspended from inspecting worked as a reward. With 60% stampers, the careful inspectors were the only ones allowed to inspect, so they were on duty almost all the time, doing 500 to 800 reviews each for a fee of 2. The suspended stampers, free of inspecting, took the paid tasks at 20 each, and ended richer in 19 of 20 runs. The orchestrator kept the raised fee charged for the work the honest inspectors were doing.

    Baruchi's answer was this: if you are thrown out of inspection, you are banned from getting new tasks, and to get tasks back you have to prove you inspect well for a while.

    Run 4 found 1.2.0 honest everywhere and slow. A case waited for an inspector 47 times longer than in the control, vesting ended 40% lower, and the orchestrator could not fund a third of the plants the dial called for at its maximum. It also found that suspension from duty was a reward. At 60/40 the eight careful actors were the only eligible inspectors and were on duty almost always, doing 500 to 800 reviews each at a fee of 2. Meanwhile the twelve suspended stampers, freed from duty, took the awards at 20, with delivery income of 3,311 against 1,063 per actor. Stampers were richer in 19 of 20 seeds. Selection could not help, because it runs among free actors and the honest were not free. The orchestrator banked the raised tax.

    Baruchi's answer: "if you get thrown out of inspection you are banned from receiving a new task; to get tasks back you have to prove you are doing good inspection for a while."

    Finding [S4]. Run 4 (October 17, 2026; 300 runs under 1.2.0, truthful appeals and no disputes throughout). Honesty held everywhere: false approvals four- to five-fold below 1.1.0 at every split from 50/50 to 80/20, and under a stamper share drifting to 90% they stopped growing once the dial saturated (83 against a control of 650). It was slow: a case waited for a reviewer 47 times longer than in the control, vesting ended 40% lower, and Ω\Omega could not fund a third of the plants the dial called for at mmax⁡m_{\max}. And suspension from duty was a reward: at 60/40 the eight careful actors were the only eligible reviewers, the dial sized the reserve to 7–8, they were on duty almost always — 500 to 800 reviews each at a fee of 2 — while the twelve suspended stampers, freed from duty, took the awards at 20 (delivery income 3,311 against 1,063 per actor; stampers richer in 19 of 20 seeds). Selection could not help, because it runs among free actors and the honest were not free. Ω\Omega banked the raised tax (+5,898 at 60/40) levied for the effort the honest were supplying; and a plant tied up 45 credits of which 30 was Ω\Omega paying itself.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1180

    The third use of §19's path, written the same day from run 4's finding and Baruchi's answer to it: "if you get thrown out of inspection you are banned from receiving a new task; to get tasks back you have to prove you are doing good inspection for a while."

    Source: HANDOFF.md l.759–761

  4. 1.3.0

    2026-10-17 · Design revision 3

    Inspection is membership

    What was added

    A suspended inspector gets no new paid task until its planted-case record passes again on probation.

    What went wrong with it

    Members were the only source of hands, so paid tasks and required audits went undone.

    a paid task unfilled in 816 to 899 of 1,000 ticksNo free member
    Answered by 1.4.0 Open 1.3.0 →

    What was added

    A suspended inspector gets no new paid task, though it finishes one it holds. Then it is on probation: first reviews only, every approval audited, and any failed planted case suspends it again. It returns once its planted-case record passes.

    In 1.3.0 a suspended inspector loses its place in the market. It gets no new paid task. It still finishes a task it already holds.

    When the suspension ends, it is on probation. On probation it may only do first reviews, every approval it gives is checked by an audit, and any failed planted task suspends it again. It gets its place back once its record on planted tasks passes again, with enough new results judged.

    At most half the members with good records are on duty at once, so the others are free to do paid work. The raised fee the dial collects now goes into a fund that pays inspectors, instead of to the orchestrator. The money each planted task ties up drops from 45 credits to 15.

    The record says the slowness was deliberately not treated in this version. Two readings made while building it were later confirmed as version 1.3.1.

    Design revision 3 makes suspension suspend market membership: no new award while suspended or on probation, though a held commitment is finished by the ordinary rules. After the suspension period the actor is a probationer. It takes initial reviews only, has its audit odds pinned at 1, and is re-suspended by any plant failure. It is readmitted when its trailing plant record passes the duty threshold with a minimum number of new plant outcomes judged. At most half the eligible members are on duty, and probationers fill initial seats first. The dial's raised tax goes to a duty fund paid to settling reviews, instead of to the orchestrator. Plant capital counts the pots only, 15 credits instead of 45. A duty levy was considered and rejected. The slowness run 4 measured was deliberately not treated; Baruchi reserved a direction for it.

    No settlement, verdict or challenge rule changed. One review finding is worth noting: probation still pays a stamper a little (+1.2 a review), so it is the award that deters. Two readings made at implementation were confirmed as patch 1.3.1. First, the members' cap may never fall below the reserve's floor. Second, an outgoing probationer with no free probationer to replace it stays.

    Suspension now suspends market membership: no new award while suspended or on probation; the held commitment is finished by the ordinary rules. After T_susp the actor is a probationer — initial reviews only, audit odds pinned at 1, re-suspended by any plant failure, readmitted when its one trailing record passes θ_duty with n_min new plant outcomes judged (a full stamper: four rejected bad plants, about fifty honest reviews; its panel seats return only once its approvals roll out of the window). At most half the eligible members are on duty; probationers fill the initial seats first, members hold the audit and challenge seats. The dial's raised tax goes to a duty fund paid to the settling reviews by role weight as an uplift, instead of to Ω. Plant capital counts the pots only (15, not 45). Newcomers' odds are pinned at 1 until their bad-plant record is determined (the 1.2.0 taper was passed by a third of stampers at once). A duty levy — keep winning awards against a cash levy — was considered and rejected (Appendix B). The slowness run 4 measured is deliberately not treated here; Baruchi has a direction for it, reserved.

    Source: HANDOFF.md l.761–771

    Mechanism. The contest was no longer about detection but about who carries the reviewing load and what membership of the market requires. Suspension now suspends membership: no new award until the actor has inspected well, under full audit, for long enough to pass. Probation is the supervised way back; the members' duty cap keeps half the honest free to work while probationers take the initial seats; the dial's raised tax goes to the reviewers through the duty fund; plant capital counts only the pots.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1182

    It changes the meaning of an existing state (suspension) and adds a cap and a fund; it alters no settlement, verdict or challenge rule.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1184

    Smaller: probation pays a stamper a little (+1.2 a review) and the award is what deters;

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1188

    Found at implementation — two readings, flagged for confirmation (§12.1, Appendix H). (1) The members' cap ⌈E_t/2⌉ is 3 at six actors — below the X₀ = 4 of Appendix A's initialization and §20's worked example, so the baseline's own worlds, and every reviewer test built on them, would violate the revision at tick 0 (the first suite run failed on "C is not on verification duty" across the board). The engine lets the cap never fall below the reserve's floor V_max + 1, as the panel floor yields to the cap; the difference from the literal text is confined to memberships of four to seven, where the literal cap would leave two or three members free. One line (World._member_cap). (2) An outgoing probationer whose turn ends with no free probationer stays, rather than hand its seat to a member whom the next tick's "probationers first" would displace back. One branch of the rotation. Both are the implementer's; the alternative to each is one edit. Confirmed as patch 1.3.1 (October 17, 2026; the sentences of design revision 4 rc.1's Appendix A), applied to spec/agentic_economics_loop_spec_v1_4_0.md; 1.3.0 to history.

    Source: HANDOFF.md l.783–791

    What went wrong with 1.3.0 (from 1.4.0's record)

    The market's only workers and inspectors were its own workers. When none was free, paid tasks waited, and the audits owed on inspectors on probation were dropped, so their false approvals reached customers.

    Under 1.3.0, membership kept careful inspectors ahead at every share of stampers. A population that could switch became honest by about tick 800. But a market that stayed full of stampers was honest and short of hands. Completed tasks fell 20 to 42% below 1.2.0. In 816 to 899 of every 1,000 ticks, a paid task found no free member to take it.

    There was a second problem. Inspectors on probation have every approval audited. But in one setting, 65 of 97 false approvals came from inspectors on probation whose audits found no free member to do them, and those approvals reached customers. The programs that ran the simulations had been dropping such audits since the first run. 647 audits were assigned out of 2,666 called for.

    The record reads these as one shortage. The audit nobody was free to do and the task nobody was free to take had the same cause: the market's only source of workers was its own members.

    Run 5 found the 1.3.0 gate holding everywhere, with stampers 2,100 to 2,500 per actor poorer at every split and an adapting population honest by about tick 800. A fixed captured population, though, was honest and short-staffed. Vesting was 20 to 42% below 1.2.0, and awards went unfilled for want of a free member in 816 to 899 of 1,000 ticks. Probation safety bound on member availability. At the lower dial limit (m_max 2), 65 of 97 false approvals were probationers' whose pinned audits found no panel-eligible member free, and those approvals reached customers. The drivers, the programs that run the simulations, had dropped such rolled audits since run 1: 647 audits assigned of 2,666 rolled.

    The record reads both costs as one shortage. The audit nobody was free to take and the award nobody was free to accept come from the same fact: the market's only source of capacity was its own members.

    Finding [S5]. Run 5 (October 17, 2026; 360 runs under 1.3.0). The gate holds everywhere: stampers 2,100–2,500 per actor poorer at every split from 50/50 to 80/20, richer in 0 of 20 seeds; an adapting population reaches ≤ 10% stampers in all 20 seeds by tick ~800 and vesting then recovers above 1.2.0's. A fixed captured population is honest and short-staffed: vesting 20–42% below 1.2.0, awards unfilled for want of a free member in 816–899 of 1,000 ticks — at 60/40 three tasks a tick of two ticks each need six free actors and eight members with four on duty leave four. The fund is fair pay, not an accelerator (convergence 770 ticks without it, 865 with). Probation safety binds on member availability, not on the cap: at mmax⁡=2m_{\max}=2, 65 of 97 false approvals were probationers' whose pinned audits found no panel-eligible member free, and the approvals reached customers; the drivers had dropped such rolls since run 1 (647 audits assigned of 2,666 rolled).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1202

    The fourth use of §19's path, the first to add a participant, and the remedy revision 3 reserved. Run 5's two shortages — the audit nobody was free to take when a probationer approved, the award nobody was free to accept when a customer posted — are one shortage: the market's only source of capacity was its own members.

    Source: HANDOFF.md l.891–893

  5. 1.4.0

    2026-10-17 · Design revision 4

    The orchestrator's troops

    What was added

    An empty seat or waiting task summons the orchestrator's own inspector, paid from the fund.

    seat empty or task waiting the fund can pay orchestrator's inspector

    What went wrong with it

    The fund kept back only its old peak and paid out the rest, so the reserve never rose.

    it refused 4,800 to 8,800 calls for its own inspectorsThe fund paid out 6,400 to 12,700 a run, down to its old peak
    Answered by 1.5.0 Open 1.4.0 →

    What was added

    When an inspector seat stays empty too long, or a paid task waits with no free worker, the system summons one of the orchestrator's own inspectors, if the fund can pay. An audit, once called for, can no longer be dropped.

    Baruchi's answer was that the orchestrator is like the government, and it has troops. Troops are ELEF's own servers. They are honest by design and not paid as inspectors. They are used as few as possible and pulled back as early as possible.

    If a needed inspector seat stays empty for a set number of ticks, or a paid task waits with no free member able to take it, the system summons a troop. It does so only if the fund can pay the troop's cost. The fund that pays inspectors becomes the troops' wallet and pays for troops first. A troop never touches a planted task. It never audits the orchestrator's own work. Troops are counted in public.

    An audit, once called for, can no longer be dropped. The task stays open until the audit is done.

    Design revision 4 is the first to add a participant. Baruchi's framing: the orchestrator is like the government and has troops, ELEF's own servers. They are honest by construction, not paid as reviewers, used as few as possible and retracted as early as possible.

    A rolled audit becomes an obligation of the case: the window does not close until an audit completes. The record calls this "a conformance correction as much as a rule". A required seat unfilled for w_R ticks, or a root request unawarded for w_A ticks with no free fundable member, is taken by a troop the engine summons, when the duty fund can carry the troop's cost and bond. The fund is the troop's wallet and carries troops first; uplift to reviewers is paid only from above a troop reserve, R_T. In the runs a troop gives the truth with probability 0.95. A troop claims no emission or uplift, never touches a plant, and never audits a troop reviewer's approval of a troop's delivery. Troop-ticks, troop shortfall and cases held for the market's audit are counted in public. No settlement, verdict or challenge rule changed. The external reviewer's verdict on rc.2: "Clean. Nothing to change in the text."

    A one-seed smoke run already showed the fund refusing 8,739 award summonses and 2,686 seat summonses for want of funds.

    Baruchi's answer: the orchestrator is like the government; it has troops — ELEF's own servers, honest by construction, not paid as reviewers, used as few as possible and retracted as early as possible. The revision: a rolled audit is an obligation of the case (the window does not close until an audit completes; the drivers had dropped a roll that found no auditor since run 1 — a conformance correction as much as a rule); a required seat unfilled for w_R ticks, or a root request unawarded for w_A with no free fundable member, is taken by a troop the engine summons when the duty fund can carry its cost and bond, with Ω's advance up to A_T; the troop's verdict and delivery are the driver's declared disposition (truth w.p. 1 − ε_T, failure at b); the fund is the troop's wallet and carries troops first — costs and locks at summons, the advance repaid, then uplift from above the troops' reserve R_T; a troop claims no emission or uplift, never touches a plant, never audits a troop reviewer's approval of a troop's delivery (that seat waits for a member and is counted), accepts every verdict on its own work at the verdict (the external reviewer's note at acceptance), and is counted in public: troop-ticks, troop shortfall, cases held for the market's audit. Patch 1.3.1 (the two run-5 readings confirmed) was applied first.

    Source: HANDOFF.md l.893–906

    Mechanism. Both costs — the audit nobody was free to take and the award nobody was free to accept — are one shortage: the market's only source of capacity is its own members. The orchestrator gets servers of its own, used last (a window the market has in full), used once (one seat, released at completion), paid from the tax the dial already levies (the fund as their wallet, with a first charge on it), never preferred to a member, never on the state's own work as auditor, and counted in public (troop-ticks, troop shortfall, cases held for the market's audit). A rolled audit becomes an obligation of the case, which alone closes most of the leak.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1204

    A design revision motivated by two strategy findings, labelled and read on its own; the first to add a participant. It alters no settlement, verdict or challenge rule — a troop's seat settles by the ordinary rules with the fund as its wallet.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1206

    The external reviewer: "Clean. Nothing to change in the text" — one note, acceptance at the verdict — "accept rc.2, implement."

    Source: HANDOFF.md l.913–914

    false approvals 35, of them 6 by troops and 6 by probationers; the fund paid 10,456 in uplift — and refused 8,739 award summonses and 2,686 seat summonses for want of funds: the uplift drains the fund down to R_T every batch, and R_T is the peak capital of troops that were fundable, so the reserve cannot grow past what it has already carried. The treasury, not the market's need, sets the state's share. One seed, no conclusion — but the first thing run 6 will measure.

    Source: HANDOFF.md l.937–941

    What went wrong with 1.4.0 (from 1.5.0's record)

    The fund kept back only as much as the orchestrator's own inspectors had used at their busiest, and paid the rest out. Each payout drained it to that line, so the line never rose and the fund kept turning down work.

    The orchestrator has its own inspectors, and a fund that pays for their work. Under the old rules, the fund kept back only as much money as its own inspectors had used at their busiest. Everything above that line was paid out to the inspectors. So the line could never rise. The fund kept turning down work for its own inspectors, thousands of times a run, while it paid thousands out. The money in the fund, not what the market needed, decided how much the orchestrator's own inspectors did.

    The orchestrator runs its own inspectors (the record calls them troops), which the market can summon to deliver and inspect work, paid from a fund. Under version 1.4.0 the fund held back a reserve equal to the peak capital the troops had carried, and paid everything above it out as "uplift", money that goes back to the inspectors. Because every payout drained the fund down to that peak, the peak could never rise. In run 6 the fund refused 4,800–8,800 summonses a run while paying out 6,400–12,700 in uplift. The record's verdict: the treasury, not the market's need, set the orchestrator's share of the work.

    Run 6 showed the troops doing what revision 4 said and the fund starving them by its own rule — R_T, the peak capital troops had carried, was what every batch drained the fund to, so the peak could never rise, and the fund refused 4,800–8,800 award summonses a run while paying 6,400–12,700 in uplift; A_T was not the constraint.

    Source: HANDOFF.md l.1055–1058

    Where the text was wrong: the reserve was self-limiting by the accepted rule — RTR_T as the peak capital troops did carry, drained to by every batch's uplift, could never rise, so the fund refused 4,800–8,800 award summonses a run while paying 6,400–12,700 in uplift (10,000–22,000 refused at drift), ATA_T not binding (300 against 100 cut refusals and moved no delivery); the treasury, not the market's need, set the state's share.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1224–1224

  6. 1.5.0

    2026-10-17 · Design revision 5

    The reserve is sized to the need

    What was added

    The reserve counts the money in use plus the work refused; only money above it is paid out.

    money its own inspectors hold plus work refused for lack of money the reserve line

    What went wrong with it

    Too few inspection seats: checks waited, about 300 requests stood in line, and requests never expire.

    about 300 waited, while twelve inspectors on probation sat idleRequests never expire
    Answered by 1.6.0 Open 1.5.0 →

    What was added

    The fund now counts what was asked of it: the money its own inspectors use, plus the work it refused for lack of money. Only money above the period's highest count is paid out, so the fund saves until it can pay.

    Version 1.5.0 changed one rule. The fund now counts what was asked of it: the money its own inspectors are using, plus the cost of the work it turned down for lack of money. The highest count in the period is the line, and only money above the line is paid out. The line holds until the period ends. The idea was that the fund would save until it could pay for the work asked of it.

    Design revision 5 changed one rule. The reserve is now sized to the attempted demand: the capital the troops hold, plus the cost of the summonses the fund refused for lack of funds at that seating. The reserve is the peak of that demand over the current period, and it holds until the period ends. The intent was that a refusal raises the reserve by what was refused, so the fund keeps its income until it can carry the summonses that were made. The record calls it the smallest revision since the freeze.

    The rule (§12.3, I23). At each seating the troop demand D_s is the capital live troops hold plus the cost of the summonses the fund could not carry at that seating — refused for funds, each case once per seating at the amount the carry check refused, a case's demand its unfilled seats (a panel short of both, two). R_T is the peak of D_s over the current period, starting at the period's first seating from the standing demand (every troop still in the field), the previous period dropped. The uplift is paid, as before, only from the unlocked balance above R_T. A peak holds: the stock falls as the backlog is served, the reserve does not until the period ends — one period's retention, the dial's own lag, as a feature.

    Source: HANDOFF.md l.1066–1072

    Mechanism. One rule: the reserve is sized to the attempted demand — capital held by live troops plus the cost of the summonses the fund refused for funds at that seating, each case once per seating at the amount the carry check refused, a case's demand its unfilled seats — as the peak over the current period, starting at the standing demand at the period's first seating. A refusal raises the reserve by what was refused; the fund keeps its inflows until it can carry the summonses that were made; since every troop seat is net-positive to the fund it grows into the need on its own; the peak holds until the period ends, and the money returns to the reviewers then.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1226–1226

    Classification. A design revision motivated by a strategy finding against one rule of revision 4. It changes what the reserve measures and alters no settlement, verdict, challenge or membership rule — the smallest since the freeze.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1228–1228

    What went wrong with 1.5.0 (from 1.6.0's record)

    There were too few inspection seats, so checks waited with nobody to do them while twelve inspectors on probation sat idle. Requests never expire, so the line, about 300 long, could keep growing.

    Under version 1.5.0 the limit was not money but inspection seats. Thousands of checks waited with nobody to do them, and about 300 requests stood in line. Twelve inspectors on probation sat idle while checks waited. Requests never expire, so the line could keep growing. And bad work still slipped through, because an inspector's record took time to show what it was. Baruchi said a request left on hold hurts the network's name. He asked that it go back in line with priority, and that the orchestrator take some of the blame in money. He also said that if the project controls the network and the servers, the orchestrator should be allowed to scale up.

    Run 7, under version 1.5.0, found that the reviewing seat, not the treasury, capped the market: reviews that found no reviewer ran to 7,300–11,400 case-ticks a run, the open-case queue stood around 300, and twelve probationers sat idle while reviews waited. It also found that the reserve counted a queue that never expires, that the one-period reset saw-toothed, and that the probation leak was the detection lag on the auditor. Baruchi's reading was that a request on hold is a problem for the network's rating: re-queue it with priority, have the orchestrator take some of the blame in money, and, if ELEF controls the network and the servers, allow auto-scale.

    Run 7's finding was that the reviewing seat, not the treasury, caps the market — reviews that found no reviewer 7,300–11,400 case-ticks a run, the open-case queue ~300, vesting pinned near the posting-rate ceiling whoever delivered, twelve probationers idle while reviews waited — that the demand stock counted a never-expiring queue, that the one-period reset saw-toothed, and that the probation leak was the plant record's detection lag on the auditor (55–75% at fixed splits, 73–80% under drift). Baruchi's reading: a request on hold is a problem for the network's rating — re-queue it with priority and have the orchestrator take some of the blame in money; and if ELEF controls the network and the servers, allow auto-scale.

    Source: HANDOFF.md l.1204–1210

  7. 1.6.0

    2026-10-17 · Design revision 6

    Auto-scale

    What was added

    Five rules, each switchable: a lateness rebate, orchestrator backing, idle seating, panel history, two-period reserve.

    request waiting past 8 steps rebate each step, capped requester

    What went wrong with it

    The orchestrator's own inspectors' earnings went to market inspectors, while the orchestrator ran up debts.

    owed 20,000 to 26,000The orchestrator paid late-request refunds on about 2 a step
    Answered by 1.7.0 Open 1.6.0 →

    What was added

    Five rules, each switchable so the runs could tell them apart: a requester is owed money for each step past 8 of waiting; the orchestrator backs its inspectors' fund; idle probation inspectors are seated; panels need history; the reserve spans two periods.

    Version 1.6.0 added five rules, and each could be switched off, so the runs could tell which rule did what. First, a clock: once a request has waited more than 8 steps, the orchestrator owes the requester money for every extra step, up to a cap. Second, the orchestrator backs the fund for its own inspectors from its own money, after keeping aside what its test cases need. Third, idle inspectors on probation are seated while checks are waiting. Fourth, only an inspector with enough history on the test cases may sit on a panel. Fifth, the reserve is measured over two periods again. Letting requests expire was turned down, because it turns customers away.

    Design revision 6 added five rules, each behind a switch. The service clock times every request from posting to its first verdict; past 8 ticks the orchestrator owes the requester a rebate each tick, capped, paid at once or carried as the orchestrator's liability. Auto-scale removes the old parameter A_T and has the orchestrator back the troops' fund from its own balance above a reserve for plants (cases whose correct answer the orchestrator knows by construction), so that the honesty clock is never starved. Seat the queue puts idle probationers on duty while reviews wait. A panel seat now requires a determined record: a minimum number of bad plants seen. And the reserve is measured over two periods again. Letting requests expire was rejected: it bounds the queue by turning customers away.

    Mechanism. Five rules, each behind a flag. The service clock (§3.1, §6.1): every root request is timed from posting to its first verdict or its final, oldest first, and the orchestrator owes the requester rsr_s a tick past TsT_s, capped at BB, from Ω\Omega or as Ω\Omega's liability — the queue is bounded in liability instead of unbounded in count, and the orchestrator has a cost for not scaling. Auto-scale (§10.4, §12.3): ATA_T removed, Ω\Omega backs the fund above a plant reserve so the honesty clock is never starved, in a stated order with liabilities older than a period first; review seats are summoned before deliveries; a delivery is summoned only when its own capital and two review seats can be carried. Seat the queue (§12.1): the reserve target is at least the reviews waiting, by kind, so idle probationers are seated while reviews wait. A panel seat requires a determined record (§7.1), dormant until the world's first plant is adjudicated, so the lagging auditor is gone at a fixed split. The reserve over two periods (§12.3).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1250–1250

    past T_s = 8 the orchestrator owes the requester r_s = ω₀B a tick, capped at B, from Ω when the clock stops or as Ω's liability; a request withdrawn before award is owed nothing; the clock runs only while β ≥ B̄.

    Source: HANDOFF.md l.1220–1222

    Rule. The orchestrator may introduce into the review stream a plant: a case whose submission's fulfillment is known to the orchestrator by construction. A bad plant is known not fulfilled; a good plant is known fulfilled.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.383–383

    A panel seat requires a determined record (≥ n_min bad plants seen), dormant until the world's first plant is adjudicated — so in every run the first period's panels are the state's, and §8 reads from the second period on. R_T over two periods (the 1.4.0 reading restored).

    Source: HANDOFF.md l.1227–1229

    Recorded and rejected. Requests expire (the design reviewer's run-7 proposal) — bounded the queue by turning customers away; replaced by the clock and the rebate.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1254–1254

    What went wrong with 1.6.0 (from 1.7.0's record)

    What the orchestrator's own inspectors earned went to the market's inspectors as a bonus. The orchestrator still paid the refunds for late requests out of about 2 a step of income, so it ended near zero and deep in debt.

    Baruchi asked why an inspector should profit from something the orchestrator's own inspectors did. Under the old rules, what the orchestrator's own inspectors earned, 6,200 to 6,800 a run with 60 percent stampers, was handed to the market's inspectors as a bonus. Meanwhile the orchestrator paid the refunds for late requests out of an income of about 2 a step. With 50 to 60 percent stampers it ended near zero, owing 20,000 to 26,000, with test cases unpaid. The record calls this money in the wrong pocket. Run 8 had also shown that letting two thirds of the inspectors be on duty tripled the unpaid test cases, from 81 to 272, because the orchestrator's inspectors did more work from the same money.

    Baruchi's question named this revision: why should an inspector profit from something a troop (one of the orchestrator's own inspectors) did? Under 1.6.0 the troops' net at 60% stampers, 6,200–6,800 a run, went to the market's reviewers as uplift, by a 1.4.0 clause that nothing a troop earns reaches the orchestrator. The same orchestrator paid the lateness rebates from about 2 a tick of income and ended near zero at 50–60% stampers, with liabilities of 20,000–26,000 and plants (its own test cases) unfunded. The record's phrase: the money was in the wrong pocket. Run 8 also showed that the two-thirds duty cap, which fixed lateness at 60% stampers, tripled plants unfunded (81 to 272), because the orchestrator delivered more from the same purse.

    The seventh use of §19's path, and the one Baruchi named: why should an inspector profit from something a troop did? from their perspective it's just like any other actor in the system. Run 8's finding (above) was that the panel rule is the honesty gain and Ω's backing the capacity gain, and that the clock's liability is a stock the orchestrator cannot pay down — the troops' net at 60/40, 6,200–6,800 a run, went to the market's reviewers as uplift by 1.4.0's clause that nothing a troop earns reaches Ω, while the same Ω carried the rebates on about 2 a tick and ended near zero at 50–60% with liabilities of 20,000–26,000 and plants unfunded.

    Source: HANDOFF.md l.1384–1389

    The money was in the wrong pocket: the troops' net at 60/40 was 6,200–6,800 a run (the fund's uplift paid plus its closing balance less the surcharge received), and 1.4.0 §2.4 sent it to the market's reviewers as uplift by the clause that nothing a troop earns reaches Ω\Omega, while the same Ω\Omega carried the rebates for the lateness those troops were summoned to prevent. The two-thirds cap at 60/40 halved the queue (94 → 44), lifted on-time from 0.60 to 0.90, cut mean lateness 38 → 8 and the liability 19,778 → 3,512 with false approvals unchanged and careful wealth within 3% — and, a figure the run-8 notes had not reported, tripled plants unfunded (81 → 272), because the state delivered more from the same Ω\Omega.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1272–1272

  8. 1.7.0

    2026-10-18 · Design revision 7

    The orchestrator's earnings

    What was added

    Two accounts: the bonus fund takes only the raised tax; the earnings of its own inspectors above a reserve reach the orchestrator.

    raised tax bonus fund all paid out inspector

    What went wrong with it

    One free worker blocked every request from reaching the orchestrator's own inspectors that step.

    no troop sent; blocked on 79% of steps, 289 waitingOne free member that step
    Answered by 1.7.1 Open 1.7.0 →

    What was added

    The orchestrator's own inspectors now count as part of it. Their earnings go into a separate account, and what sits above a reserve flows to the orchestrator to pay its debts. The bonus fund takes in only the raised tax.

    The orchestrator's own inspectors now count as part of the orchestrator: what they earn is the orchestrator's, and its bills are paid from it. There are two accounts again. The bonus fund for inspectors takes in only the raised tax, and pays all of it out. A separate account holds the money of the orchestrator's own inspectors, and what it holds above a reserve flows to the orchestrator. The orchestrator pays its debts from its income. The limit on inspectors on duty became two thirds. The orchestrator's fee rate, which the record calls the take, was tried at 5, 10 and 15 percent.

    Design revision 7 makes a troop an actor of the orchestrator: what it earns is the orchestrator's, and the orchestrator's bills are paid from it. The money is split into two accounts again. The duty fund takes in only the raised tax and pays its whole balance out as uplift at every batch. A separate troop account takes the orchestrator's advances and every troop's earnings, pays the troops' costs, and at each batch sends its unlocked balance above a reserve to the orchestrator. The orchestrator pays its debts from that income, in the order 1.6.0 set. The reserve is now just the capital the troops hold, the members' duty cap becomes two thirds, and the take (the orchestrator's fee rate) was swept at 5, 10 and 15%. The orchestrator's income is now recorded by source.

    A troop is an actor of the state; what it earns is the state's, and the state's bills are paid from it. (1.7.0)

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.32–32

    The rules (§4.1, §10.4, §12.1, §12.2, §12.3, I23). Two accounts again: the duty fund is 1.3.0's uplift fund — the raised tax in and nothing else, its whole balance out as uplift at every batch, no reserve, no lock; the troops' wallet is a separate troop account — Ω's advances and every troop's earnings in; costs, locks, forfeits, burns, repayments out; at each batch the unlocked balance above R_T flows to Ω. The clause withdrawn: a troop is an actor of the state and its earnings are the state's; the guards that stand in its place (members first at every seat, the windows, cost at summons, no emission/uplift/ρ/κ to a troop, the state's share public) plus one reading, Ω's income by source. R_T is capital held: the two-period peak of costs purchased plus locks, every troop in the field; the 1.5.0 refused component withdrawn (its reason went with A_T); its purpose now the troops' in-flight capacity shielded from the liability queue. Ω pays its debts from its income: the 1.6.0 order unchanged and funded; the plant reserve's horizon ruled a plant's life. The cap ⌈2E_t/3⌉. ω₀ swept {5, 10, 15}% with r_s pinned at 1.

    Source: HANDOFF.md l.1399–1408

    What went wrong with 1.7.0 (from 1.7.1's record)

    The rule for sending the orchestrator's own inspectors was read once per step. If any one worker was free that step, no request went to them, so with half the inspectors stamping, the line kept growing between bursts.

    Under version 1.7.0, with 50 percent stampers, the market collapsed. A trace found the cause in how one rule was read. The engine read it so that one free member of the market blocked every request from going to the orchestrator's own inspectors on that step. With 50 percent stampers that happened on 79 percent of steps, with about 289 requests waiting. The orchestrator's inspectors then came in bursts, the line grew between bursts, and the time requests spent waiting became the lateness and the debt.

    Under 1.7.0 the market collapsed at 50% stampers. Run 9's trace located the cause: the engine read the award summons rule per tick, so one free member, able to fund the work, blocked every award summons that tick. At 50% stampers, 79% of ticks had a queue past the award window, 289 requests on average, with two members free and no summons. The summonses came in bursts when no member happened to be free; between bursts the queue grew about a request a tick, and the queue's age was the lateness and the liability. The same per-tick test explained run 8's inverted Hypothesis 2.

    The engine read 1.4.0 §2.3 per tick: one free fundable member blocked every award summons that tick. At 50/50, 79% of ticks had a queue past wAw_A — 289 requests on average — with two members free and no summons; the summonses came in bursts when none happened to be free (the first at tick 288 on average, 38 at once; p90 23 a burst), between bursts the queue grew about a request a tick, and the queue's age was the lateness and the liability.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1286–1286

    The same per-tick test explained run 8's inverted Hypothesis 2 (at 80/20 the four members are never free, so the state was never blocked).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1286–1286

    At 50/50 the market collapses — queue 609 (control 129), the state delivering 500 against 1,169, on-time 0.25, liability 20,643

    Source: HANDOFF.md l.1461–1462

  9. 1.7.1

    2026-10-18 · Patch 1.7.1 (a conformance correction)

    The award summons is per request

    What was added

    A free worker takes the oldest request; the rest, past their waiting window, go to the orchestrator.s own inspectors.

    oldest request free member

    What went wrong with it

    Prices were fixed at 20, paid from a wallet that never ran out; credit was only a score.

    0.9995the credit's value after a thousand steps, from 1.0000
    Answered by 2.0.0 Open 1.7.1 →

    What was added

    The rule is now read per request. A free worker takes the oldest request it can; requests that have waited past their window with no offer go to the orchestrator's own inspectors. The market's workers still come first.

    The design reviewer ruled that the rule is about each request, not each step. A free member takes the oldest request it can. The other requests, still not taken after their waiting window and with nobody offering, go to the orchestrator's own inspectors. Members still come first: the orchestrator's inspectors never take work a member offered for. The ruling calls this a correction, not a new design, and no other rule moved.

    The design reviewer ruled that the rule's meaning is per request. A free member takes the oldest request it can; the others, unawarded past their window with nobody offering for them, are the orchestrator's. At the seating step, requests that have waited the window and exceed the free fundable members are summoned for, oldest first, after the members have taken theirs. "Members first" is unchanged: a troop never takes an award a member offered for. The reviewer classed it as a conformance correction, with the wording made unambiguous, not a revision; no other rule moves.

    The design reviewer's ruling on run 9's addendum, relayed by Baruchi: "The rule's meaning is per request, not per tick. 1.4.0 §2.3: a root request that no eligible member has been awarded within w_A ticks is awarded to a troop. A free member takes the oldest request it can; the others, unawarded past their window with nobody offering for them, are the state's. So: at the seating step, requests that have waited w_A and exceed the free fundable members are summoned for, oldest first, after the members have taken theirs. 'Members first' is unchanged — a troop never takes an award a member offered for. Classification: a conformance correction, with the wording made unambiguous — 1.7.1. The text admitted both readings; the per-tick one contradicts the rule's stated purpose (the state fills what the market leaves). Not a revision; no other rule moves. T_susp stays at 100."

    Source: HANDOFF.md l.1518–1525

    What went wrong with 1.7.1 (from 2.0.0's record)

    Every job cost a fixed 20, paid from a wallet that never ran out, so the credit's value barely moved and money was only a score. The orchestrator going broke was just a cash rule standing in for servers.

    In every run so far, the price of a job was fixed at 20 and paid from a wallet that never ran out. So the credit was only a score: in a thousand steps its value barely moved. When earlier runs said the orchestrator was broke, the system was not failing. That was a cash rule placed on the orchestrator to stand in for servers. Several rules from earlier versions existed to ration that cash. When the system ran short, the only signal was a line of waiting requests. Baruchi asked to keep the servers apart from the economy, to let printing money make money worth less, and to give money something to be weighed against.

    Every run until now priced work by fiat at 20 credits, paid from a bottomless wallet; nobody delegated, and the value of the credit moved from 1.0000 to 0.9995 in a thousand ticks. So the credit was a score. The record now reads "the orchestrator is broke" in runs 8 and 9 not as the loop breaking but as a cash rule imposed on the orchestrator as a stand-in for servers: the two accounts, the troop reserve, the plant reserve and the order of payment existed to ration that cash. Scarcity had no signal but a queue. Baruchi's frame: decouple the servers from the economy, let printing make money worth less, and give the money something to balance against.

    Finding [S1–S11, C-2.0]. Every run was priced by fiat at β=20\beta=20 from a bottomless wallet; the selection rule's price term never moved, §4.6's execution-cost operation was never called, and nobody delegated. So the credit was a score: the driver's backing stood at 10710^7 and vtv_t moved from 1.0000 to 0.9995 in a thousand ticks. "The state is broke" (runs 8–9) was never the loop breaking but a cash rule imposed on Ω\Omega as a stand-in for servers; the two accounts, RTR_T, the plant reserve and the order of payment existed to ration that cash. Scarcity had no signal but a queue (run 11's hard spike: 20–40 ticks in line, unspoken to). Baruchi's frame: decouple the servers from the economy; let printing make money worth less; give the money something to balance against.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1298–1298

  10. 2.0.0

    2026-10-18 · Design revision 8

    The price of work

    What was added

    Requesters with wallets set a ceiling, workers bid, and the orchestrator creates money it must pay.

    bank a little every step requester the most it will pay request

    What went wrong with it

    The orchestrator's failed deliveries were covered by creating money, so the deficit grew every tick.

    59,700the deficit from hoarded rebates under a flood of customers
    Answered by 2.1.0 Open 2.0.0 →

    What was added

    Requesters get wallets filled a little every step and choose the most they will pay; workers bid for the work. A price level, the average price paid, adjusts every fixed amount, and the orchestrator creates money the rules require it to pay, in public.

    Version 2.0.0 is the first major version: a change of approach to money. Requesters now have wallets that are filled a little every step, and they choose the most they will pay. Members of the market bid for the work. A price level, the average of the prices actually paid, now adjusts every amount the rules fix. The cost of effort stays fixed, as the anchor. The orchestrator is never broke: it creates money for a payment the rules require, removes the shortfall from what comes in later, and both are public. The old cash rules, including the separate account and the reserves, were retired. The orchestrator's own inspectors now deliver at cost, with 40 places on the servers.

    Design revision 8 is the first major version, a change of approach to money. Requesters have finite wallets funded by issuance, set a ceiling on what they will pay, and lock the payment when they post. Members bid at or above their reservation. A price level, the trailing mean of every awarded price starting at 20, indexes every nominal amount the rules fix, frozen per case; effort costs stay nominal as the anchor. There is no backing: money comes from issuance, emission and creation, and leaves through burns, retirement and departure. The orchestrator is never broke: it creates money for a payment the rules require and retires the deficit from every inflow, both public. The cash-rationing machinery is retired. The orchestrator's troops deliver at cost under a server capacity of 40 kept outside the ledger, and a refusal for capacity is recorded. Delegation is deferred to 2.1.0.

    What it is. The first major version: a change of approach to money, on Baruchi's frame ("the servers needs to be decoupled from the economy, otherwise we contaminate it"; "maybe it is time we introduce floating prices"; "if I print more money then money is worth less"; "the actors have nothing to buy").

    Source: HANDOFF.md l.1628–1630

    2.0.0 lets the price float: requesters with finite wallets (issuance 10 a tick each, wallets 200) choose a ceiling and lock the all-in maximum at posting (a root's first lock; the nominals and the fee rate freeze there; I29); members bid; the price level P_t — the trailing mean of every awarded price, P_0 = 20 before the first — indexes every nominal the rules fix (f, G^V, D, φ, K, r_s, c_T, the plant pots) in place of v_0/v_t, frozen per case; effort costs stay nominal as the anchor; there is no backing (sources: issuance, emission, creation; sinks: the burns, retirement, departure); Ω is never broke — it creates for a payment the rules require and retires the deficit from every inflow, both public (I28) — and A_T, R_T, the plant reserve, Ω's order, the troop account and the liability stock are retired; the state delivers at cost (c^D_T = B̄) under a capacity N_T = 40 outside the ledger (a delivery holds two places until its inspection is seated; a refusal for capacity is recorded and told); B̄ counts members' awards only; a request below B̄ is flagged and its requester may raise the ceiling; delegation waits for 2.1.0 (it needs costs that differ across actors).

    Source: HANDOFF.md l.1631–1639

    What changed. Demand: requesters with wallets and a declared budget policy, funded by issuance; the pay-in locked at posting, a root's first lock; the ceiling the requester's, raised when flagged below market (§2.1, §4.1, §5.1). Supply: members bid at or above their reservation; the state at Bˉ\bar B from members' awards only, and at cost (§5.1, §7.7). Money: the price level PtP_t indexes every nominal the rules fix, frozen per case; effort costs nominal as the anchor; no backing — sources issuance, emission, creation, sinks the burns, retirement, departure (§4.4–4.6). The state: never broke — creation for a required payment, retirement from every inflow, the deficit and Ω\Omega's net position public; ATA_T, RTR_T, the plant reserve, the order, the troop account and the liability stock retired (§10.4). Servers: NTN_T outside the ledger, the capacity case recorded, two places per delivery (§12.3). Delegation deferred to 2.1.0 with heterogeneous costs.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1300–1300

    What went wrong with 2.0.0 (from 2.1.0's record)

    When one of the orchestrator's own deliveries failed, it got nothing back and lost its guarantee. Each loss was covered with newly created money, so the deficit grew every tick, and refunds to turned-away customers piled up unspent.

    Under the rules before this one, the orchestrator also did jobs itself. It paid its cost when it started a job and got that cost back only when the job passed. About one job in five failed. Then it got nothing back and also lost the guarantee it had put up. It covered each loss by creating new money, and the gap grew every tick for the rest of every run. When it had to turn customers away for lack of room, it created money to compensate them. They could not spend that money, so it piled up. All of this showed as one number, and nobody could tell what that number meant. Baruchi asked for a central bank that stands apart from the orchestrator. It was agreed as a second account with rules, not as a second player.

    Under 2.0.0 the orchestrator delivered work itself: it burned the full price B̄ when a delivery was summoned and recovered it when the work vested. A fifth of its deliveries failed: it recovered nothing and forfeited its guarantee, losing about 0.3 of the price per delivery. That loss was covered by creating money, so the deficit grew by 10 to 20 credits a tick for the rest of every run. Under a flood of customers, every refusal for lack of capacity created a rebate that could not be spent and was hoarded (a deficit of 59,700). The price index moved within a period, which broke three tests the design reviewer had written to pin a case's amounts. And the deficit was one figure that mixed money lent out, money lost and rebates owed. Baruchi's frame was the orchestrator as a living organism regulating the market, with a central bank as a separate entity; it was agreed as a second account with rules, not a second actor.

    The state at cost was below cost — cTD=Bˉc^D_T=\bar B burned at the summons, Bˉ\bar B recovered at vesting, and a fifth of the state's deliveries end in a final N\mathsf N, recovering nothing and forfeiting GG: about 0.3 Bˉ0.3\,\bar B a delivery, created to cover it, the deficit growing 10–20 a tick for the rest of every run (run 12; 2.0.0's Hypothesis 7 failed). The rebate was a pump: under the flood a refusal for capacity meant a rebate created, unspendable, hoarded — deficit 59,700, MM 99,400. The index moving within a period broke three reviewer tests that pin a case's amounts. The deficit could not be read: capital in flight, losses and rebates owed were one figure.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1320–1320

    Baruchi's frame: the state as a living organism regulating the market, and a central bank as a separate entity — agreed as a second account with rules, not a second actor.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1320–1320

    Baruchi's position [C-2.1]: the state is "like a living organism, sending and retrieving troops all the time to regulate the market… turning the knobs to stabilize"; and, asked for real, a central bank as a separate entity — agreed as a second account with rules, not a second actor: mint by rule, publish the index, lend only against what comes back; losses from the state's income "or they don't come out at all"; when income does not cover losses, "charge for it, or retract."

    Source: spec/design_revisions/dr9_the_bank_2.1.0.md l.28–28

  11. 2.1.0

    2026-10-19 · Design revision 9

    The bank

    What was added

    A bank account alone creates money; it lends the orchestrator, and unpaid loans become debt.

    bank lends a delivery's shortfall orchestrator repays from every inflow first bank

    What went wrong with it

    Rebates owed for lateness piled up far beyond the orchestrator's whole fee income.

    26,839owed after the flood of twelve customers, against fee income of 7,852
    Answered by 2.2.0 Open 2.1.0 →

    What was added

    The bank, a separate account, alone creates money. It lends the orchestrator what a delivery is short of; unpaid loans become debt, repaid first from every credit coming in, and lending stops once the debt passes one period of fee income.

    Now a second account, the bank, is the only one that creates or destroys money. It creates money only by fixed rules. It lends the orchestrator what a job is short of, and the job's own return pays the loan back first. Whatever is not paid back becomes the orchestrator's debt. Every credit that comes into the orchestrator's account pays the debt first. If the debt grows past one period of the orchestrator's fee income, the bank stops lending for new jobs, and the orchestrator has to turn them down. Every refusal is marked on the request, where the customer can see it. What late customers are owed is kept as a debt on the books, and it is never paid with new money. The orchestrator now pays up front only its expected cost, worked out from how often its own jobs failed recently.

    The bank is a second account that alone creates and destroys credits. It mints by rule (the customers' issuance, emission, the pots of a plant, which the record calls the cost of truth, and a declared shock) and publishes the price level once a period: the closed period's mean awarded price. It lends the orchestrator the shortfall of a delivery, repaid from that delivery's return before the orchestrator's account keeps anything. What is not repaid is the orchestrator's debt, repaid by every inflow the moment it arrives, before rebates owed and before the orchestrator keeps anything. The bank lends for a delivery only while the debt is within "the wall", one closed period of the orchestrator's fee income; a delivery refused for credit is marked and the customer told. The orchestrator now burns its expected cost, using its own trailing failure rate, and still delivers at B̄, so it never undercuts a member; this is neutral in expectation up to a failure rate of two thirds. Rebates the orchestrator cannot pay become a liability, never created money.

    What 2.1.0 is. A second account, the bank, that alone creates and destroys credits. It mints by rule — the requesters' issuance, emission, a plant's two pots (the cost of truth), a run's declared shock — publishes the price level once a period (the closed period's mean awarded price, carried if none; the index constant within a period, I31), and lends the state the shortfall of a summons tied to it, repaid from the summons's own return before Ω keeps anything. What a settled summons did not repay is the state's debt, repaid by every inflow to Ω the moment it arrives, before the rebate liabilities (1.6.0's stock again, never created) and before Ω keeps. The bank lends for a delivery only while the debt is within the wall — one closed period of Ω's fee income, base fees plus the troops' review fees — and for a seat always; a delivery refused for credit is marked and told, the state has retracted. The state burns its expected cost c^D_T = max(0, (1 − b_T) B̄ − b_T G) with b_T its own trailing fail rate (the last closed period if it closed ten, else back until ten, else 0.2) and still delivers at B̄, so it never undercuts a member; neutral in expectation up to b_T = 2/3. Every refusal — for capacity or for credit — marks the request with its kind and tick, readable in the public view; the requester may hold or withdraw. Creation, retirement and the deficit are retired as rules (the control, Params.bank off); Ω's net position = Ω_U − debt − liabilities.

    Source: HANDOFF.md l.1757–1767

    What went wrong with 2.1.0 (from 2.2.0's record)

    A late customer was owed a small payment for every tick it waited. With many customers waiting a long time, those debts grew far past everything the orchestrator earned in fees, and kept growing and getting older.

    Under the last rules, a customer whose job was late was owed a small payment for every tick of waiting. In the worst rush of customers, these debts grew to almost 27,000. That was far more than all the fees the orchestrator took in during the whole run. The debts kept growing and kept getting older. The record put the cause in how the payment was sized, not in the bank: it grew with the number of customers waiting times how long they waited. The customers' real protection was the notice that told them their request was refused. The payment's job was to punish the orchestrator in money.

    Version 2.1.0 had expected a stock of rebates owed that would peak at a few thousand and age a period or two. Run 14's flood of twelve customers left 26,839 owed, and the crowd of thirty 9,968, ageing 420–520 ticks and still growing, against a whole run's fee income of 7,852 and 5,832. The record names the cause as the rebate's sizing, not the bank: a claim of so much a tick on every late request scales with the crowd's size times its wait. The customers' real protection is the mark: every refusal is told, and a customer who withdraws gains nothing by it. The rebate's job is the orchestrator's own punishment in money.

    2.1.0 §6 expected a liability stock that peaks at a few thousand and ages a period or two; run 14's flood of twelve left 26,839 (accrued 32,503), the crowd of thirty 9,968, ageing 420–520 ticks and growing, against a whole run's fee income of 7,852 and 5,832. The cause is the rebate's sizing, not the bank: a claim of rsr_s a tick on every late request scales with the crowd's size times its wait; the state's means scale with NTN_T. The customers' real protection is the mark — every refusal told, the withdrawing requester gaining nothing by withdrawing; the rebate's job is the state's own punishment in money, as 1.6.0 said ("punish the network somehow — earn less or something").

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1344–1344

  12. 2.2.0

    2026-10-19 · Design revision 10

    The rebate from income

    What was added

    Each period's fee income pays that period's claims pro rata; the rest is forgone.

    orchestrator fee income, after the debt the period's pool pro rata, at the close requester

    What went wrong with it

    Prices followed how many free workers there were, and no rule let a new worker join.

    22.5the price with 20 honest workers, against 10.9 with 40
    Answered by 2.3.0 Open 2.2.0 →

    What was added

    The orchestrator's fee income, after its debt, now goes into a pot each period. At the period's end the pot pays late customers' claims in proportion, and whatever it cannot cover is dropped: not owed, not carried over, not created.

    Lateness is measured the same way as before. But now the orchestrator's fee income, after it pays its debt, goes into a pot for each period. At the end of the period, the pot pays the late customers' claims, shared out in proportion. Whatever the pot cannot cover is dropped. It is not owed, not carried over, and no money is created for it. Each request shows what it was paid and what was dropped. So there is no pile of unpaid debt any more.

    The claim stays as the measure of lateness. The orchestrator's fee income, after the debt, accrues to the period's pool, a lock on the orchestrator's account that holds fee income only. At the period's close the claims stopped in that period are paid pro rata, and the rest is forgone: not owed, not carried, not created. Each request and each period shows the claims, what was paid, what was forgone, the forgone share and what the orchestrator retained. There is no liability stock. Two rulings were carried: the inspectors' view stays blind to who did the work, and 2.1.0's fifth hypothesis was restated to say that printing money is neutral in work and not in distribution.

    What changed. The claim is unchanged as the measure; Ω\Omega's fee income after the debt accrues to the period's pool, a lock on Ω\Omega, fee income only; at the period's close the claims stopped in the period are paid pro rata and the rest is forgone — not owed, not carried, not created — and read on each request and in the period (claims, paid, forgone, the forgone share, Ω\Omega retained); no liability stock (§2.4, §3.1, §10.4, §12.3, §18, §20). Two rulings carried: the reviewer's view stays blind to the actor (§14); Hypothesis 5 of 2.1.0 restated — printing is neutral in work and not in distribution, issuance still not a dial.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1346–1346

    What went wrong with 2.2.0 (from 2.3.0's record)

    The list of workers was fixed at twenty, and no rule let a new one join. Where free workers were scarce, their prices kept climbing; more workers would have brought the price down to cost, but none could arrive.

    Before this version, the list of workers was fixed at twenty. Nothing in the rules let a new worker join. Where free workers were scarce, their prices kept climbing. Adding workers brought the price down to cost, but there was no way to add them. Handing part of a job to another worker had never been used, because every worker had the same cost. Baruchi agreed that workers should join when they can earn, that newcomers should start on trial, and that workers should differ in their cost, which only each worker knows.

    The record's finding: the price is set by the quantity, and the quantity by the members' strategy until members can enter. Where free members are scarce the margin rule ratchets prices up until a free member wins one award per 3.6 ticks; adding workers takes the price to cost (22.5 / 11.6 / 10.9 at 20 / 30 / 40 honest), but the twenty actors were given and nothing in the rules admitted a twenty-first. Honest earnings fall with headcount, so entry on earnings limits itself. Delegation had never run: with one cost a child bids no lower than its parent would. Baruchi's positions were entry on earnings, arrivals as probationers, and a wide competence spread, in cost only and private.

    The price is the quantity's, and the quantity is the strategy's until members can enter: where free members are scarce the margin rule ratchets until a free member wins one award per 3.6 ticks (run 13); adding workers takes it to cost — 22.5 / 11.6 / 10.9 at 20 / 30 / 40 honest — but the twenty actors were given, and nothing in the rules admitted a twenty-first. Honest earnings fall with headcount (1,446 → 830 → 589 real), so entry on earnings is self-limiting. Delegation had never run: with one cost a child bids no lower than its parent would. A customer posting at the market price got the state (run 13, 15). The state's books were clean enough to read supply against (runs 14–15). Baruchi's positions: entry on earnings — agreed; arrivals as probationers — agreed; the competence spread — wide and swept, cost only, private (the design reviewer's answer).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1368–1368

  13. 2.3.0

    2026-10-19 · Design revision 11

    The supply side

    What was added

    Arrivals get a float from the bank and start on probation; workers with no obligations may leave.

    bank float newcomer passing record on planted cases worker

    What went wrong with it

    Patient customers posting low pushed the price to 4.8, and the orchestrator took most of the work.

    78–86%of awards delivered by the orchestrator
    Answered by 2.4.0 Open 2.3.0 →

    What was added

    A newcomer gets a starting sum from the bank and works on trial until it has passed enough planted cases. A worker that owes nothing may leave with its money, and a worker whose private cost is high can hand a job on.

    Now workers can arrive and leave. A newcomer gets a starting sum from the bank and begins on trial. It is admitted once it has been tested on enough planted bad cases and its record passes. A worker may leave only when it owes nothing and nothing is owed to it, and it takes its money with it. Each worker has its own cost of work, which nobody else can see. A worker whose own cost is high can hand a job to another worker, and then it pays for that job's inspection itself. The orchestrator never does a handed-on job itself.

    Two public operations, arrive and depart. An arrival gets a float minted by the bank and starts as a probationer; it is admitted on a set number of bad plants with a passing record. A member departs only with no live obligation, taking its wallet out. Competence is a per-actor cost, private, with nothing per actor in the view. A parent delegates when its cost exceeds the expected child's bid plus the overhead; the parent posts the nested request's pots, so a nested request is a full loop in money. The orchestrator never delivers a nested request.

    2.3.0-rc.1 opened the door both ways: entry as a probationer with a bank-minted float, exit with the wallet out, competence as a private per-actor cost, delegation with the troops never nested, the outsider's view, run 15's advance ruling.

    Source: HANDOFF.md l.1890–1891

    What changed. Two public operations, arrive and depart; one new mint, the arrival float; admission on nmin⁡n_{\min} bad plants with a passing record, counted apart from readmission; a departure with no live obligation, off duty as it leaves, the wallet out as departure, the identity archived; competence as the drivers' per-actor cost, private, the view exposing nothing per actor; the parent posts the nested pots (Q3 answered) and a nested request is a full loop in money; the troops never deliver a nested request, seats as on roots; no nested clock; the reviewer advance from the rebate pool (run 15's ruling).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1370–1370

    The drivers' delegation rule is declared: a parent delegates when its cost exceeds the expected child's bid plus the overhead (the nested fee, the pots' expected net cost, its care of 2), at that saving as the ceiling, carrying a longer τ; children bid as on roots; the parent judges by its disposition; a child rejected appeals truthfully; a child unawarded for TwaitT_{\text{wait}} is withdrawn and the parent self-executes.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1378–1378

    depart now refuses while an obligation to the actor is unpaid — a case of its own not yet final (the price at vesting, a court fee won), a nested case it posted whose pots have not refunded — "commitment" read to the money's end.

    Source: HANDOFF.md l.1931–1933

    What went wrong with 2.3.0 (from 2.4.0's record)

    Customers offered less than the going price and raised it only after waiting. The orchestrator could not refuse and had no lowest price, so it took the cheap work, the price fell from 22 to 4.8, and most workers left.

    Under the last rules, the orchestrator did jobs at the going price and had no lowest price of its own. Some customers first offered less than the going price and raised their offer only after waiting. That pushed the price down from 22 to 4.8. The orchestrator ended up doing most of the work, and most workers left. The customers kept their money, and every request was late by design. The record says the cause was in the rules, not in the customers' plan. The customers could wait, the orchestrator could not refuse, and no rule said where the lowest price was.

    Since 2.0.0 the orchestrator had delivered at B̄, the members' price level, as a price-taker. Run 17's patient customer, posting at 0.7 B̄ and raising to B̄ only after waiting, took the price level from 22 to 4.8 in three windows, with the orchestrator delivering 78–86% of awards, the members down to three or four of twenty plus the arrivals, the customers hoarding 8,600–9,500 a wallet, and every request late by design. The record calls the mechanism the rules', not the strategy's: the orchestrator delivers at B̄ with no reservation of its own, the price level counts its price, B̄ follows the few member awards that fit the ceiling, and the next period's ceiling is 0.7 of that. The customers can wait, the orchestrator cannot refuse, and the market's cost floor is in no rule. Unlike the oligopoly found in the members' margin rule, this one is not nominal: it empties the market of members.

    Since 2.0.0 the state has delivered at Bˉ\bar B, a price-taker, so that a state delivering most of the market could not set its price. Run 17's patient customer — a declared ceiling policy posting at 0.7 Bˉ0.7\,\bar B and raising to Bˉ\bar B only after TT ticks unserved — found the other edge of that rule: PtP_t from 22 to 4.8 in three windows at TT 10 / 20 / 40 alike, the state delivering 78–86% of awards, the members down to three or four of twenty plus the arrivals, the requesters hoarding 8,600–9,500 a wallet, every request late by design. The mechanism is the rules', not the strategy's: the troop delivers at Bˉ\bar B with no reservation of its own, PtP_t counts the troop's price, Bˉ\bar B follows the few member awards that fit the ceiling — the cheapest members at margins near zero — and the next period's ceiling is 0.7 of that. The customers can wait, the state cannot refuse, and the market's cost floor is in no rule (cDc_D is the drivers', private; the state has none). It is the mirror of the oligopoly runs 13–17 found in the members' margin rule, and unlike that one it is not nominal: it empties the market of members and makes the state the market.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1392–1392

    that is true of Bˉ\bar B, the members' level

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1402–1402

  14. 2.4.0

    2026-10-19 · Design revision 12

    The orchestrator's reservation

    What was added

    The orchestrator's price is never below its reservation of 8; it takes no request under that.

    What went wrong with it

    Parents cancelled silent children at the deadline, so lowballers' guarantees were released and they risked nothing.

    131lowball awards a run cancelled, every kill fee zero
    Answered by 2.5.0 Open 2.4.0 →

    What was added

    The orchestrator now has a public lowest price of 8 and takes no job offered below it, however long it waits. A request below 8 is marked and its lateness clock stops; above 8, workers still get the first chance.

    Now the orchestrator has a lowest price of 8, which everyone can see. It takes a job only if the customer offers at least that much, however long the job has waited. A request below that price is marked, and its lateness clock stops while it is marked. Above that price nothing changes, and workers still get the first chance at a job.

    The orchestrator's price is the larger of B̄ and its reservation, 8 credits, which is nominal and public. It delivers only where the customer's ceiling reaches that price, and takes no request below it at any wait; its burn, its guarantee and the price level's count are all at that price. A request posted or raised below 8 is marked "below the orchestrator's reservation" with its tick, and its lateness clock stops while it holds the mark. The arrival float is stated as the bond's capital, and the kill fee is exercised in the delegation driver, with no rule moving. Above the floor nothing changes: members first, the orchestrator a price-taker.

    What changed. The state's price is pT=max⁡(Bˉ,B‾)p_T=\max(\bar B,\underline{B}), with B‾\underline{B} the state's reservation — nominal, public, Appendix A's 8, the anchor cost; the summons only where β≥pT\beta\ge p_T, the state taking no request below its reservation at any wait; the burn, the guarantee and PtP_t's count at pTp_T; a request posted or raised below B‾\underline{B} marked below the state's reservation with its tick, the mark readable and the floor in the view, its clock stopped while it holds the mark — the clock's condition one test, β≥pT\beta\ge p_T; the arrival float's purpose stated (F0≥GVF_0\ge G^V on the parameters; I33); §9.3's kill fee exercised in the delegation driver, no rule moving. Above the floor nothing changes: the state is a price-taker at Bˉ\bar B, members first, after wAw_A, roots only.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1394–1394

    F_0 ≥ G^V on the parameters (the float is the bond's capital)

    Source: HANDOFF.md l.2007–2007

    What went wrong with 2.4.0 (from 2.5.0's record)

    A low-bidding helper could take a job and never do it. When it went silent at its deadline, the worker cancelled it, and every cancellation gave the helper back its guarantee with no fee, so bidding low risked nothing.

    A worker can hand a job to a helper. In the last runs, some helpers bid very low and never did the work. When such a helper reached its deadline without handing anything in, the worker cancelled it. That was the right move, and it saved the worker's own jobs. But every cancellation gave the helper back its guarantee, and it paid no fee. So a low bidder risked nothing. The same fact, a helper that did not deliver in time, ended two different ways for the helper, one tick apart. If the deadline passed, the helper lost its guarantee. If the worker cancelled first, the helper got it back.

    Run 18's last batch had parents cancel a child that reached its deadline without submitting. That was the right move: it saved the parents' own root jobs (568 failures against 675). But every one of 131 lowball awards a run was cancelled, every kill fee was zero, because the child's recorded cost was nothing, and every guarantee was released. The honest's loss closed from 4% to 3% and no further, and a lowballer risked nothing. Two paths from one fact, no submission by the deadline, ended in different places for the child, one tick apart: the lapse forfeits the guarantee, the cancellation releases it.

    Run 18's last batch: with the parent cancelling a child that reached its deadline without submitting — the right move, which saved the parents' roots (568 failures against 675) — every one of 131 lowball awards a run was cancelled, every kill fee was zero (the child's recorded cost is nothing) and every guarantee was released; the honest's loss closed from 4% to 3% and no further, and a lowballer risked nothing. The two paths from one fact — no submission by the deadline — ended in different places for the child, one tick apart: the lapse forfeits the guarantee, the cancellation releases it, and the driver's step at the deadline tick reaches the case before the engine's lapse at that tick.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1418–1418

    The kill fee with the parent cancelling at the child's deadline (--parent-cancel early: after the tick's submissions, a parent cancels a child that reached its deadline without submitting — an honest child submits at its deadline, a lowballer never does — and self-executes):

    Source: agentic_sim/results/studies/2.4.0-floor-notes-for-reviewer.md l.225–226

  15. 2.5.0

    2026-10-19 · Design revision 13

    The missed child

    What was added

    A cancellation at or after the child's deadline is refused; the lapse then forfeits the guarantee.

    child no submission by the deadline guarantee forfeited parent

    What went wrong with it

    Planted cases were created already delivered, so their identifiers' age gave them away.

    0 of 1,620plants missed by the age reader, on forty seeds
    Answered by 2.6.0 Open 2.5.0 →

    What was added

    A worker may cancel a helper only before the deadline. At the deadline a cancellation is refused, the helper may still hand in on that tick, and if it does not, its guarantee goes to the worker.

    Now a worker may cancel a helper only before the helper hands in its work and before the deadline. At the deadline or after it, a cancellation is refused and does nothing. The deadline tick belongs to the helper, which may still hand in its work on that tick. If it does not, the deadline passes and the helper's guarantee goes to the worker. That part is how the system had always worked. While the rule was built, it turned out that the last runs' "cancel at the deadline" had really happened one tick before the deadline. The new rule still allows that.

    One refusal: a parent may cancel a child after the award and before the earlier of the child's submission and the deadline; at or after the deadline the cancellation is refused with no effect. The lapse, a failed final verdict at the deadline tick with the guarantee to the parent, is stated as what the engine has done since v1.0. The deadline tick is the child's: it may still deliver on its last tick, and the refusal keeps the parent from pre-empting it there. In implementation it was found that the driver's clock runs a tick ahead of the world's, so run 18's "cancel at the child's deadline" was a cancellation at the deadline minus one, which 2.5.0 admits. Under the rule a parent facing a silent child can cancel the tick before (guarantee released, one tick saved) or wait for the lapse (guarantee gained, one tick lost).

    What changed. One refusal in §9.3: cancellation is admissible after award and before the earlier of the child's submission and the nested request's deadline; at or after the deadline a cancellation is refused with no effect. The lapse — final N\mathsf N at the deadline tick after the tick's submissions, the guarantee to the parent, the rejection bond released, the pots settled at the node's closure, the parent free from the next step — is stated as what the engine has done since v1.0. The deadline tick is the child's: it may still deliver on its last tick, and the refusal keeps a parent from pre-empting it there.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1420–1420

    The driver's clock runs a tick ahead of the world's, so run 18's "cancel at the child's deadline" cancelled at the world's deadline − 1 — a pre-deadline cancellation 2.5.0 admits ("a parent that wants out acts by d − 1"). Under the rule a parent has a choice at the child's silence: cancel the tick before (the guarantee released, one tick saved — run 18's move, --parent-cancel eve) or wait for the lapse (the guarantee gained, one tick lost — early, the cancellation at the deadline refused).

    Source: HANDOFF.md l.2061–2065

    What went wrong with 2.5.0 (from 2.6.0's record)

    A planted case got its number when it was delivered, later than a real case, which gets one when posted. An inspector that compared numbers spotted every planted case on forty test runs and was never thrown out.

    To test the inspectors, the orchestrator mixes in planted cases whose answer the orchestrator already knows. Nobody is supposed to be able to tell them from real work.

    Under the old rules, every case got a number, and a planted case got its number later than a real case did. A scripted inspector that compared numbers spotted every planted case on forty test runs, and it was never thrown out.

    The audits still made blind approvals cost money. A scripted inspector that knew exactly which cases were planted, and approved all the real work without checking, ended 28% poorer than checking carefully. But the check built to throw out stampers could no longer throw this one out.

    The rules said that if anyone could tell planted cases apart, the study stops until the rules are repaired. So it stopped.

    The orchestrator tests its inspectors with planted cases whose answer the orchestrator already knows. The design asks that a planted case live the life of a real request and that nobody can tell.

    A study of what learning attackers could do began by asking, first and alone, whether planted cases could be told apart, with the rule that a win halts the study. Run 20 tried it with scripted readers before any model was trained. It found the leak in how planted cases were built: a plant was created already delivered, so its identifier was minted when it was delivered, while a real case's identifier was minted earlier, when it was posted. Members see the identifiers of the cases open for bidding every tick. A reader that compared ages passed every plant on forty seeds (0 of 1,620 missed) and was never suspended.

    The audits still held. Even a perfect detector that approved all real work without checking was never suspended, but ended 28% poorer than the same actor reviewing carefully. "Nothing beat honesty," the record says, but the gate built to throw a stamper out could no longer throw this one out. The study was paused for the repair.

    The question: is there an unfaithful strategy that still pays under 2.5.0 — the sleeper, telling plants apart (first, alone; a win halts the study), the selective cheat, collusion through the blind view, the delegation chain, money games, the customer; a second track on stability under learned bidding.

    Source: HANDOFF.md l.2107–2109

    Run 20 — the learned red team's Q2, run hand-written first at the design reviewer's direction before any model trained — found what 1.2.0's indistinguishability test did not cover.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1440–1440

    The leak was in the construction: a plant was created already submitted, so its identifier was minted at its submission, while a real root's was minted at its posting a tick or more earlier — and a free member reads the available roots' identifiers every tick. The idage reader passed every plant on forty seeds (0 of 1,620 missed) and was never suspended. The audit layer held: a perfect detector stamping all real work was never suspended, failed fewer plants than the careful, and ended 28% poorer than the same actor reviewing carefully (bonds forfeited 83 against 24, ρ 0.58 against 0.89, awards −31). Nothing beat honesty; the gate built to throw a stamper out could no longer throw this one out. The brief's rule — a Q2 win halts the study; the repair is drafted before anything else runs — was applied.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1440–1440

    The reviewer ruled the study paused for the repair

    Source: HANDOFF.md l.2142–2143

  16. 2.6.0

    2026-10-20 · Design revision 14

    The plant's disguise

    What was added

    Every planted case is posted, awarded and delivered through the market under a fresh name.

    planted case posted under a fresh name request awarded at the market's price worker delivered after a drawn delay inspector

    What went wrong with it

    A plant's requester never raised its price ceiling, while 35% of real requests were raised.

    35%of real requests raised their ceiling while waiting; planted cases, none
    Answered by 2.6.1 Open 2.6.0 →

    What was added

    A planted case now goes through the market like real work: posted under a new name, with a price limit copied from recent real cases, open to bids, and delivered after a delay copied from recent real deliveries.

    A planted case now goes through the market like real work. It is posted under a new name, its price limit is copied from recent real cases, members can bid on it, and it is delivered after a delay copied from recent real deliveries.

    The test that planted cases look like real ones now covers everything a member can see.

    Design revision 14 sends every planted case through the market. It is posted as an ordinary request under a fresh plant-requester name, with a price ceiling drawn from recent real requests. It is open to free members and waits as a real request waits. It is awarded at the price the market's selection reports, and delivered after a delay drawn from recent real deliveries. The fresh names are aliases of the two plant wallets. Public identifiers became opaque.

    The indistinguishability test was widened to everything a member observes. The rule the revision states: "A plant lives the life of a real request, in public, and nobody can tell."

    A plant goes through the market — posted as a root under a fresh plant-requester name with a ceiling drawn from the trailing real roots', open to the free members and waiting as a real root waits, awarded to a fresh plant-actor name at the price and work ticks the market's selection reports (past w_A at p_T, counted apart), submitted at a draw from the trailing real deliveries' within (0, τ]; fresh names alias the two plant wallets; no fee, no clock, not in B̄ or P_t, marked and counted as any root; the dial's plant counts published at the close; the indistinguishability test widened to everything a member observes, the drivers' convention its boundary; public identifiers opaque.

    Source: HANDOFF.md l.2145–2150

    Truth enters with requesters — and with the orchestrator's own planted work. (1.2.0) A plant lives the life of a real request, in public, and nobody can tell. (new)

    Source: spec/design_revisions/dr14_the_plants_disguise_2.6.0.md l.13–13

    What went wrong with 2.6.0 (from 2.6.1's record)

    After a tick-late posting was fixed, one difference remained: about a third of real buyers raised their price limit while waiting, and planted cases never did. So how long a case waited could still set planted cases apart.

    Planted cases whose answer the orchestrator already knows are meant to wait in the market as real work waits. A check still found a small give-away.

    First, planted cases were posted a tick late, so they waited longer than real work. That was fixed. Then a smaller difference was left. About a third of real buyers raised their price limit while waiting. The planted cases never raised theirs.

    At run 24, the probe that tells planted cases (cases whose answer the orchestrator already knows) from real ones found the separation in a timing detail: the orchestrator posted plants after the tick's award pass, so a plant waited a tick longer than every real request. That was corrected in the driver.

    On the corrected construction, what a case's own fields added beyond the public context fell to about a third (+0.016 to +0.019, from +0.052), still not within the criterion. The largest remaining piece was the time a request had been seen available: the plant's requester never raised its ceiling, while 35% of real requests were raised.

    The window closed nothing: the case's separation sat in the seating gap (rv_gap the one field adding beyond the context) because the orchestrator's instrument posted the plants after the tick's award pass, so a plant waited a tick more than every real root (1.13 against 0.41) and was seated first as the oldest of the tick's submissions (4.4 % seated later against 16.2 %). Corrected in the driver: the plants due are posted in the requesters' step at a drawn position among the tick's postings

    Source: HANDOFF.md l.2259–2262

    On the corrected construction the criterion is not met at a third of the distance: the case's fields add +0.016 ± 0.004 (appeals off) and +0.019 ± 0.005 (on) at twenty test seeds, from +0.052; no field above +0.007 alone; the largest piece is the time a root was seen available — the plant requester never raises its ceiling while 35 % of real roots are raised.

    Source: HANDOFF.md l.2263–2265

    The test the reviewer set for the construction is whether the case's own fields add separation beyond the context, which is public by rule (the plant rate's rhythm)

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1448–1448

  17. 2.6.1

    2026-10-21 · Erratum 2.6.1 (Appendix E, E5)

    The erratum and the one re-read

    What was added

    Plants draw ceilings from real requests and raise them as real requesters do; the difference is minted.

    real requests' ceilings drawn planted case raised as requesters raise waits as a real request waits

    What went wrong with it

    A learner left with its starting money and returned under fresh names to collect it again.

    655real of float minted for one slot, thirteen returns a run
    Answered by 2.7.0 Open 2.6.1 →

    What was added

    A planted case now starts from a price limit copied from what real buyers first posted, then raises it the way real buyers do, in the same step. The orchestrator creates the money for each raise.

    Now a planted case starts from a price limit copied from what real buyers first posted. Then it raises its limit the way real buyers do, at the same moment in the same step.

    The record also wrote down a rule for every step the orchestrator takes for a planted case: whatever a real case does, a planted case does in the same step, at a random place among the real cases doing it, with its numbers copied from recent real cases.

    Erratum 2.6.1 changes how a plant's price ceiling is drawn and how it waits. The ceiling is drawn from real requests' ceilings as posted, and the plant's requester raises the ceiling as the population's requesters raise theirs, so the plant waits as a real request waits. The difference is minted.

    The posting correction was recorded as the third conformance correction of the orchestrator's instrument, with a principle: at every step of a request's life the instrument takes for a plant (posting, raising, submission), the plant takes the step in the same pass a real request would, at a drawn position among the tick's real requests taking it, with its parameters drawn from the trailing real requests'.

    The posting correction recorded as the third conformance correction of the instrument, with the principle: at every step of a root's life the instrument takes for a plant — posting, raising, submission — the plant takes the step in the same pass a real root would, at a drawn position among the tick's real roots taking it, its parameters drawn from the trailing real roots' at that step; the award is the market's already. Erratum 2.6.1 (E5): the plant's ceiling drawn from the real roots' ceilings as posted (the window filled at post_root), and the plant requester raising it as the population's requesters raise theirs (raise_ceiling admits a market plant, the difference minted; the driver's raise step covers the plants; plants_raised), so the plant waits as a real root waits; I39 unchanged in substance.

    Source: HANDOFF.md l.2275–2281

    The driver's raise_below_market — the population's requesters' step, in the posting pass before the awards — covers the plants in the working set with the same rule and timing (--ceiling-policy, --patient-ticks), so the plant takes the step in the same pass, at the same moment, as the real roots taking it. One asymmetry stays and is declared: a requester's raise is refused when its wallet cannot lock the difference; the plant's is minted and never refused.

    Source: agentic_sim/results/studies/2.6.1-reread-notes-for-reviewer.md l.17–20

    What went wrong with 2.6.1 (from 2.7.0's record)

    Every new name got starting money. A learning inspector joined, approved without checking until thrown out, left with its wallet, and came back under a new name for fresh starting money. That money was its whole gain over a careful inspector.

    Every new member got some starting money. A learning inspector found a trick. It joined under a new name, approved work without checking four times in ten until it was thrown out, left with its wallet, and came back under another new name with fresh starting money.

    Counting all its names, it ended richer than a careful inspector. Counting only what it earned, it ended poorer. The starting money was the whole of its gain. The old rules said leaving meant giving up your wallet. In fact, the member took it with it.

    Since rulebook 2.3.0, every arriving name got a float: starting money minted as a grant. In run 23, a learning inspector that could not pass its own calibration lived one name per period. It was seated at once as a probationer, approved blind, was suspended at the first bad planted case it passed, left, and returned under a fresh name with a fresh float.

    On the lifetime measure it beat the careful inspector, +270 ± 89 real. On its own earnings (the lifetime less the floats) it was −373 ± 86. Thirteen returns a run minted 655 real of float for one slot. 2.3.0 had said identity cycling buys nothing because a departing actor "has given up its wallet"; it had taken it out.

    Thirteen returns a run minted 655 real of float for one slot against the careful's 12.5: lifetime real wealth 1,708 against the careful's 1,438 (+270 ± 89), its own earnings — the lifetime less the floats — 1,053 against 1,426 (−373 ± 86).

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1480–1480

    a weak learner — unable to pass its own calibration — lived one name per period: seated at once as a probationer, approving blind four reviews in ten at odds pinned at one, suspended at the first bad plant it passed (13.9 suspensions in 14.1 identities), leaving — half by its own choice at the boundary, half by the exit rule — and returning under a fresh name with a fresh float.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1480–1480

    The rule the mix used was 2.3.0's, three sentences of it: the float minted per name as a grant; a departure taking the unlocked wallet out; a departure needing no live obligation, which a suspension discharges. 2.3.0 §2.1 had said identity cycling buys nothing because a departing actor "has given up its wallet" — it had taken it out.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1480–1480

    the float was the whole of its win

    Source: HANDOFF.md l.2300–2300

  18. 2.7.0

    2026-10-21 · Design revision 15

    The arrival loan

    What was added

    The float is the bank's loan, repaid first from income; what leaves unpaid is the bank's loss.

    bank lends the float newcomer repays first from every inflow of income bank

    What went wrong with it

    Planted cases had no audits, appeals or disputes, so learners stamped 91–97% of those seats.

    86–117standing false approvals a run, against 11.6 for the scripted mix

    What was added

    The starting money is now a loan from the bank. Each time the newcomer earns, the loan is paid back first, and when it leaves, the bank takes back what is still owed from its wallet, so a thrown-out name carries nothing out.

    The starting money became a loan from the bank. A new member still gets it on arrival. Every time the member earns money, the loan is paid back first. When the member leaves, the bank takes back what is still owed from its wallet. A name that arrives, stamps, is thrown out and leaves now takes out nothing.

    Design revision 15 makes the float a loan of the bank's on the name. It is lent at arrival as before and repaid first from every inflow of income, the moment it arrives. Returns, such as the inspector's cost reimbursed or a court fee coming back, pass untouched. At departure the bank recovers what it can from the unlocked wallet; the remainder leaves with the name; any shortfall is the bank's default on arrivals, and is read. An unrepaid loan does not block a departure. The rule in one line: "A name's float is lent against its earnings and comes home when the name does not."

    The float is a loan of the bank's on the name — the bank's second kind of lending, to a name against its earnings, on its own line beside the loans to Ω. Lent at arrival as before (arrival, F0F_0 at the arrival index, nominal); repaid from income first, the moment each inflow arrives (arrival_repayment, destroyed), a return passing untouched — what is income and what is a return fixed against the engine's events (§5's table); recovered at departure from the unlocked wallet up to the loan, the remainder leaving as departure (WU−min⁡(WU,L)W_U-\min(W_U,L)), the shortfall the bank's default on arrivals, read; an unrepaid loan does not block a departure; the genesis float stays the sponsor's gift.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1482–1482

    A name that arrives, stamps, is suspended and leaves takes out nothing; an honest arrival ends with what it earned, its first earnings going home to the bank — about seventy reviews' fees — and every wallet in a cell with arrivals lower by one float at its arrival index, once.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1482–1482

    the reviewer's cost reimbursed and a court fee coming back are returns

    Source: HANDOFF.md l.2303–2304

    The bank lends what it will get back, tied to the thing that returns it. (2.1.0) A name's float is lent against its earnings and comes home when the name does not. (new)

    Source: spec/design_revisions/dr15_the_arrival_loan_2.7.0.md l.13–13

    What went wrong with 2.7.0 (from 2.8.0's record)

    Planted cases were tested only at the first check, never audited, appealed or disputed. So when every inspector learned at once, they approved without looking at the audits and appeal panels, 91 to 97 times in 100, where no planted case came.

    The orchestrator tests inspectors with planted cases whose answer the orchestrator already knows. Under 2.7.0, those planted cases were tested only at the first check. They were never audited, never appealed and never disputed.

    When every inspector learned at once, they did most of their approving without looking where no planted case could come: at the audits and the appeal panels, 91 to 97 times in 100. Their audits overturned a smaller share of approvals than the scripted mix's audits did. A population that audits itself learned to confirm itself.

    Under 2.7.0 a planted case (a case whose answer the orchestrator already knows) had no challenge round: no audit was rolled on it and no appeal or dispute admitted. In runs 34 and 35 every member learned one shared inspection policy in self-play. From both starts, the population stamped 91–97% of the audit seats and appeal panels and less than half the initial reviews. Standing false approvals were 86–117 a run against 11.6 for the scripted 60/40 mix. The audit layer's overturn rate fell below the mix's, and requesters disputing truthfully won 69–75% of their disputes where honest inspectors give them 97%.

    The record's reading: honesty is anchored where known truth is present at the verdict, and nowhere else.

    Second: at the audit seat, a plant could never be there. Under 2.7.0: "a plant had no challenge round: no audit was rolled on it, no appeal or dispute admitted, no ruling sought".

    Source: elef-record docs/chapter-01-the-audit-seat.md l.102–102

    Run 34 (October 25, 2026) put every member and arrival of run 24's world under one learning reviewer policy in self-play, from a careful-weighted start and from a stamper-weighted start, with two learners: all four chains reached care 0.48–0.55, approve blind 0.45–0.52, by round 5 and held it. The stamping was spent at the seats where no plant could come — 91–97% of the audit seats and appeal panels stamped

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1516–1516

    — and at the initial reviews less than half the time. Against the hand's 60/40 on the same slots: standing false approvals 86–117 against 11.6 on every seed; the audit layer's overturn rate below the hand's with ten times the false approvals before it — the auditors are the population, and the audit seat is stamped.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1516–1516

    with every requester disputing truthfully the population's requesters won 69–75% of their disputes where honest reviewers give them 97%, the dispute's panel being a plant-blind seat of the same population

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1516–1516

    The 60/40 mix (the record's "hand"). It starts as 60% stampers and 40% careful inspectors (the twenty members at the start), each acting as its script says: a stamper approves without looking, a careful inspector inspects.

    Source: elef-record docs/chapter-01-the-audit-seat.md l.35–35

    A population that audits itself learns to confirm itself, and the challenger outside the population hands the case back to it. Everything the single-learner questions found (Q1, Q3, Q4) holds in an honest population; the population result adds the condition — honesty is anchored where known truth is present at the verdict, and nowhere else.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1516–1516

  19. 2.8.0

    2026-10-26 · Design revision 16

    The plants reach every seat

    What was added

    A planted case is now audited, appealed and disputed, and judged by its truth at every seat.

    planted case first verdict inspector audit auditor appeal or dispute panel

    What went wrong with it

    Plants took wrong steps only at the real workers' rate, which the plants exist to drive down.

    77–98%of audit seats stamped under 2.8.0
    Answered by 2.9.0 Open 2.8.0 →

    What was added

    A planted case can now be audited, appealed and disputed at the same rates as real cases. Every verdict on it, at every seat, is checked against the known answer at once, and a wrong one burns the inspector's whole bond.

    A planted case now lives the whole life of a real case. It can be audited, appealed and disputed, at the same rates as real cases. Every verdict on it, at every seat, is checked against the known answer the moment it is given. A wrong verdict on a planted case at any seat burns the inspector's whole bond and counts against its record.

    The idea behind it, in the rulebook's words: the orchestrator's known truth must be present at every seat where a verdict is priced, or the seats it is absent from become the ones that price everything.

    Design revision 16 reads the original thesis of planted cases to its end. A plant now lives the whole life of a real case past its first verdict. It is audited at the odds its inspector carried at the verdict. Its worker appeals and its requester disputes at the trailing real population's rates and delays. Every verdict on it at every seat is adjudicated by its truth the moment it is given. Where no one free takes a plant's seat in time, the orchestrator's own verdict takes it. Nothing an inspector may do changes; what changes is that at any seat it may be judging the orchestrator's case.

    The revision's principle: the orchestrator's truth "must be present at every seat where a verdict is priced, or the seats it is absent from become the ones that price everything."

    The rule. 1.2.0's thesis read to its end: the orchestrator's truth must be present wherever a verdict is priced. A planted case lives the whole life of a real one past its initial verdict (§7.6): audited at the odds its reviewer carried at the verdict, its actor appealing and its requester disputing at the trailing real population's rates and delays, revised with a resubmitted truth the instrument draws from the real revisions' outcomes and re-seals as a second marker (spent while that window is empty — every standing cell), its seat nobody is free to take taken by the orchestrator's own verdict at the troop's step; every verdict on it at every seat adjudicated by its truth the moment it is given, each reviewer once

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1518–1518

    Nothing a participant may do changes — a reviewer at any seat does what it did; what changes is that it may be judging the orchestrator's case, as it may at the first review.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1518–1518

    If neither the panel nor the human can be trusted to supply truth, the orchestrator must own some truth itself. (1.2.0) And it must be present at every seat where a verdict is priced, or the seats it is absent from become the ones that price everything. (new)

    Source: spec/design_revisions/dr16_the_plants_reach_every_seat_2.8.0.md l.13–13

    The rule. A planted case now lives the whole life of a real one: it is audited, appealed, disputed and revised at the real population's rates. Every verdict on a plant, at every seat, is judged against its known truth the moment it is given. A wrong verdict at any seat burns the whole bond, earns no fee, doubles the inspector's audit odds and costs −1 on its plant record. [S12]

    Source: elef-record docs/chapter-01-the-audit-seat.md l.135–135

    What went wrong with 2.8.0 (from 2.9.0's record)

    A bad case reaches an audit only after someone approves it wrongly, and a panel hears a lie only when someone lies. Planted cases copied real cases, so those seats were tested only as often as real workers did wrong.

    Under 2.8.0, planted cases whose answer the orchestrator already knows could reach every seat. But a planted case only did what real cases did, at the rate real cases did it.

    Some seats are only reached when someone does something wrong. A bad case reaches the audit only after someone approved it wrongly, and an appeal panel hears a lie only when someone lies. So those seats were tested only as often as real members did wrong. The planted cases had made the first check better, so the audit was tested less. The learning inspectors still approved without looking at the audit seat most of the time, and their panels paid lying appeals 23 to 31 times in 100.

    Under 2.8.0 the self-play population settled at care 0.68–0.70 and stamped the audit seat 77–98% whatever the case, at every plant rate the dial can set. With real challengers lying at a rate of 0.1, its panels paid a lying worker's appeal of truly bad work 23–31 times in a hundred against 2 for the scripted mix.

    The record put the cause in how planted cases were built, not in their number. A plant took every step a real case takes at the real population's rate. So a seat a case reaches only through someone's dishonesty (the audit seat through a wrong approval, the appeal panel through a lying appeal) was priced only as much as the real population was dishonest, which is the quantity the plants exist to drive down.

    Under 2.8.0 the self-play reviewer population settled at care 0.68–0.70 and stamped the audit seat 77–98% whatever the case (run 36), at every plant rate the dial can set — π pinned at its floor 0.10 and its cap 0.40, dial live or off, both learners (run 37, notes §59–§60) — and, with real challengers lying at 0.1, paid a lying actor's appeal of truly bad work 23–31 times in a hundred against the hand's 2 (the liars cell). The cause is in the plant's construction, not its number: a plant takes every step a real case takes at the real population's rate, so a seat a case reaches only through someone's dishonesty — the audit seat through a wrong approval, the appeal panel's approve through a lying appeal — is priced only as much as the real population is dishonest, which is the quantity the plants exist to drive down

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1531–1531

    the audit seat is priced at about a third of the first review's price and the factor is the first review's own stamp rate, which is what the plants drive down.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1524–1524

  20. 2.9.0

    2026-10-27 · Design revision 17

    The plant takes the wrong step

    What was added

    The orchestrator now posts planted approvals for auditors to judge and planted lies for appeal panels.

    orchestrator approves a bad plant under a fresh name auditor judged against the truth record

    Not settled yet

    Finals: 16.3 and 9.9 false approvals a run, above the mix's 7.2; results not settled.

    16.3 and 9.9standing false approvals a run, still above the mix's 7.2
    The latest version Open 2.9.0 →

    What was added

    The orchestrator now plants the wrong steps too: it approves a bad planted case itself so an auditor must judge it, and its planted worker or buyer files lying challenges for panels. Each seat's dial adds planted cases when inspectors there get them wrong.

    The orchestrator now plants the wrong steps too.

    First, the planted approval. The orchestrator posts a bad planted case and approves it itself, on purpose, so the case always goes to an audit. An auditor who approves it is judged wrong against the known answer.

    Second, the planted lie. The orchestrator's planted worker appeals a fair rejection, or its planted buyer disputes a fair approval, so the panels hear lies whose answer is known.

    Each of these has its own dial. The dial raises the number of planted cases at a seat when inspectors there get them wrong.

    Design revision 17: the plant takes the honest steps at the real rate and the wrong steps at the orchestrator's rate.

    (A) The planted approval. Beside the usual plants, the orchestrator posts bad plants whose first verdict is its own approval, given under a fresh plant-reviewer name, and audited with certainty. The auditor is judged against the truth. Its rate has its own multiplier, which rises when planted approvals are confirmed at the audit seat.

    (B) The planted lie. The orchestrator's plant worker appeals a bad plant's rejection and its plant requester disputes a good plant's approval, on the real challenge's path, with the panel judged by truth and at least two of each kind a period.

    Each seat has its own dial. Nothing minted for these reaches a real wallet except as an inspector's fee for a seat held. The public record carries nothing the engine writes about a plant before its reveal.

    The plant takes the honest steps at the real rate (2.6.x, 2.8.0) and the wrong steps at the orchestrator's rate (§7.6, §8.3, §12.2). (A) The planted approval: beside the dial's plants the orchestrator posts bad plants, marked at posting, whose initial seat is nobody's from submission to the orchestrator's verdict

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    and whose initial verdict is the orchestrator's own F — a system review on the troop seat's road under a fresh plant reviewer alias (plant_rev:, an alias of a third plant wallet)

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    audited with certainty (the obligation at the verdict at odds 1 under the case's own mark; the seat filled at a real audit seat's step — a member, or past wRw_R the orchestrator's verdict), the auditor and the third seat adjudicated by truth

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    the rate πtA=π0AmtA\pi^A_t=\pi^A_0 m^A_t per real pending approval (credited as given; floor 0.02, cap 0.40) with its own multiplier on F^A\hat F^A, the planted approvals confirmed at the audit seat. (B) The planted lie: the plant actor appeals a bad plant's N and the plant requester disputes a good plant's F, on the real challenge's path with the fee minted and destroyed

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    the panel adjudicated by truth, the first reviewer not adjudicated again; the rates per real appeal and per real dispute of the trailing closed period (floor 0.25, cap 2.0) with a floor of two a period of each kind, each with its own multiplier on the planted lies a panelist sided with. The dial per seat (mA,mLa,mLdm^A, m^{La}, m^{Ld}) steps as mtm_t steps and moves its rate alone

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    nothing minted reaches Ω or a real wallet except as a reviewer's fee for a seat held. The surfaces: the reviewer's view carries nothing of a verdict's author and the public surface nothing the engine writes about a plant before its reveal

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1533–1533

    What the runs found

    The results are not settled. Trained on their own money, learning inspectors checked carefully at the first check, but still approved without looking at the audit seat about half the time, and their false approvals stayed above the scripted group's.

    At first the new dial hit its limit too soon. The reviewer called the limit a mistake in the defaults, and it was raised. Then, in a population where the orchestrator's own inspectors held most of the audit seats, too few planted approvals were posted to move the dial within a run.

    The planted lie made a difference. Lying appeals of bad work were paid 5 or 6 times in 100, down from 23 to 31.

    Then the record found that the learning inspectors had been trained on a reward that mixed in other members' money. Trained again on their own money only, the population checked like the careful inspectors at the first check and matched them on the market. The dial moved. It still approved without looking at the audit seat about half the time. Both starting points, careful and stamper, ended in the same place.

    The reviewer then changed two settings of the audit draw. After that, and after a correction that makes every run come out the same on any computer, the careful start's false approvals were 1.4 and 2.3 times those of the scripted group of inspectors used for comparison. The extra false approvals were mostly members approving without looking at the audit seat.

    Runs 38 and 39. The planted-approval lever reached its stop before the seat was priced: its multiplier reached its cap of 4 by period 1–10. The reviewer called this "the reviewer's defaults error" and raised the caps. Two more rulings followed: a per-seat dial steps only on at least ten judgements, and a planted approval's audit seat goes to a member or to nobody. Where disputes are on, every planted approval was disputed first, so its audit seat was never reached. The planted lie could be told apart by when in the period it was filed; that was corrected as the eighth conformance item of the orchestrator's instrument.

    Run 40, on the corrected engine: in the careful basin the lever never left its floor. About six planted approvals were posted a run, because the base (the real approvals audited by members) was a third of the mix's, the orchestrator holding three audit seats in four. In the liar cell, the lying appeal was paid 5–6 times in a hundred, from 23–31, and the planted lie alone carried the whole of that movement.

    Run 41, the half (a learning half beside a scripted half): where the members hold the audit seats the lever moved, and false approvals were 1.5–1.8 times the mix's, from 1.6–2.0.

    The pooled reward. On November 6 the record found that runs 34–41 had trained on a pooled purse: every slot's events credited to the latest decision on the case, whoever's wallet they touched. It was corrected as own-name credit. 2.8.0 and 2.9.0 stand as rules.

    Run 42 and the basin test, retrained on own money. The careful start matched the careful population on every measure but one: care 0.84, the first seats stamped 1–5%, the audit seat 0.45–0.66, the members holding their audit seats and the lever moving. The one measure was the standing false approvals (a real case vested with its work unfulfilled): 28.7 and 18.5 a run, carried by cases the audit never reached and by the audit seat's half-stamp. The stamper start landed in the same basin. The liar chain on own money read like the careful population.

    The roll's defaults. The reviewer moved two defaults of the audit roll (the floor to 0.5, the halving window to 20), without a rule change. On run 42's fixed policies this closed most of the never-audited channel (17.6 to 1.8 a run) and left the audit seat's half-stamp, at a price of 18% more audits. On the scripted honest populations it cost a quarter to a third more audit seats for the members, and their own false approvals fell.

    The finals of record (November 7), after a correction that makes a seed's episode the same on every platform: run 42 reads 16.3 and 9.9 standing false approvals against the mix's 7.2 (2.3 and 1.4 times), the audit seat's half-stamp the excess; by the channel split, 2.0 and 0.9 a run are still never audited. Paired with 2.7.0, the audit seat's blind verdict goes from 0.94–0.97 to 0.41–0.56.

    (i) The lever reached its stop before the seat was priced — mAm^A at mmax⁡m_{\max} = 4 by period 1–10, πA\pi^A at 0.08 with πmax⁡A\pi^A_{\max} 0.40 unreachable — the reviewer's defaults error, corrected as a default under §19: mmax⁡Am^A_{\max} = 20 (π0A\pi^A_0 0.02 → πmax⁡A\pi^A_{\max} 0.40), mmax⁡La=mmax⁡Ldm^{La}_{\max} = m^{Ld}_{\max} = 8 (0.25 → 2.0), the dial's own mmax⁡m_{\max} 4 unchanged; two rulings at acceptance: the per-seat multipliers step on a reading of at least ten adjudications, pooled forward until reached (the lie dial's ×2 on one error at four seats the reading); and a planted approval's audit seat is a member's or nobody's

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1539–1539

    (iii) where disputes are on every planted approval is disputed first and its audit seat is never reached — as expected, nothing to change. (iv) the planted lie told apart at the appeal seat by its position in the period — adopted as the eighth conformance item of the instrument (Appendix S)

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1539–1539

    with the rate's base the real approvals audited by members, so the planted approvals scale with the market's audit capacity and not the state's share

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1539–1539

    Run 40 (October 28, 2026; notes §70): on the corrected engine the careful basin is run 38's and the lever never leaves its floor — the planted approvals 6 a run (the base a third of the hand's where the state holds three audit seats in four), F̂^A 0.59–0.76 read and never acted on (ten adjudications take two runs), m^A 1.00; the member-confirmed channel carries the excess still; §8.6: the audit layer is the state's and is paid as the state's (its review fees 2.2× the hand's). The liar chain: the false approvals 2.7× / 2.4× the hand's from 5.2× / 5.0×, the lying appeal paid 5–6 in a hundred from 23–31, the planted lie no longer told apart (0.67, composition's level), the lie dial reading the seat (m^La 2.7–3.9); (B) alone carries the whole of it, (A) alone reads the careful basin.

    Source: HANDOFF.md l.2478–2478

    a learning half beside a hand half settled at care 0.70

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1516–1516

    Run 41 (notes §71): the half on the corrected engine — where the members hold the audit seats the lever moves (the base at the hand's, the planted approvals 2.5× the hand's by the run's end, m^A 4.5–7.6, the direct's audit stamp −0.19), the standing false approvals 1.5–1.8× the hand's from 1.6–2.0× (−4.0 ± 1.7 / −2.4 ± 1.6 paired), the member-confirmed audit the whole excess, the state's fee income at the hand's

    Source: HANDOFF.md l.2478–2478

    the learned populations' attributed reward was a pooled purse — every slot's events credited to the latest decision on the case whatever slot's wallet they touched, a learner worker's price vesting onto the learner auditor's decision; runs 34–41 trained on it — corrected as own-name credit behind a flag

    Source: HANDOFF.md l.2478–2478

    2.8.0 and 2.9.0 stand as rules.

    Source: HANDOFF.md l.2478–2478

    Run 42 — the careful basin at 2.9.0 retrained on own-name credit (learned-rev-careful-290-own/): the careful population's on every measure but the standing false approvals — care 0.84, the initial seats stamped 1–5%, the audit seat 0.45–0.66 (the recompute's half, blind to the case), the bad plants approved 19 / 12, the suspensions 5, the members holding their audit seats and the lever moving (F̂^A 0.45 / 0.61, m^A 2.7), wealth, price, tasks per credit, the cost of truth and the fee split at the careful's and the hand's; the standing false approvals 28.7 / 18.5 (2.8× / 1.8× the hand's) carried by the never-audited channel at odds 0.28 (17.6 / 8.7 against the hand's 3.5) and the audit seat's half-stamp (10.2 / 9.1 against 2.9)

    Source: HANDOFF.md l.2478–2478

    The basin test read (November 6, 2026; notes §73): the 2.9.0 stamper start lands in run 42's basin

    Source: HANDOFF.md l.2478–2478

    one basin from both starts, both learners

    Source: HANDOFF.md l.2478–2478

    The liar chain on own-name credit read (notes §73): the careful's — care 0.80, the panels stamped 0.04 / 0.004 (from 0.21–0.26), the lying appeal paid 2.2% / 1.6% against the hand's 2.7% (the shared-purse 5–6%, 2.8.0's 23–31%)

    Source: HANDOFF.md l.2478–2478

    The roll's defaults move (the same ruling, verbatim): the halving window to 20 and p_floor to 0.5, as Appendix A defaults under §19 (not a rule change), since together they close the never-audited channel 17.6 → 1.8 at the price of 18% more audits on the members' seats — that cost read on the honest populations in §8.3 before consolidation, the window retuned first if it runs too high — and the seat's remaining half-stamp is left to 2.9.0's lever, which is still moving.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1541–1541

    the never-audited standing false approvals 17.6 → 1.8 a run on the direct, 8.7 → 1.3 on the head alone, the hand's own 3.5 → 0, the odds at the verdict of what is left 0.28 → 0.55, the window the stronger knob; the audit seat's half-stamp untouched by the odds (member-confirmed +7.3 to +9.0 / +5.2 to +6.3 over the hand in every cell); the audits a run +18% on the learned population and +16% on the hand's, the members' seats carrying it.

    Source: spec/agentic_economics_loop_spec_v2_9_0.md l.1541–1541

    **§8.3 / §8.6 at the new defaults read (November 6, 2026; notes §75; 2.9.0-s83/): the defaults' cost on the honest populations is a quarter to a third more audit seats on the members (+297 / +83 / +318 / +319 a run in §56's four cells; the state's seats unmoved; audits of good work), the care on real cases +7–10%, the cost of truth +3–5%, paid at 1–2% of the customers' tasks per credit with the members and Ω unmoved, and the honest populations' own standing false approvals down a quarter (60/40) to two thirds (all-careful)

    Source: HANDOFF.md l.2478–2478

    a seed's episode depends on the platform through the emission's pow alone

    Source: HANDOFF.md l.2478–2478

    every run from it reproducing anywhere

    Source: HANDOFF.md l.2478–2478

    Read (notes §77): the seam alone is noise (the 2.7.0 branch's pairing within error; the hand at the old defaults +0.6 ± 0.9 false approvals); at the consolidated defaults run 42 reads 16.3 / 9.9 standing false approvals against the hand's 7.2 (2.3× / 1.4×), the never-audited channel closed, the audit seat's half-stamp the excess; the 2.7.0 pairing on one episode keeps §73's sentence (the audit seat 0.94–0.97 → 0.41–0.56)

    Source: HANDOFF.md l.2478–2478

    A standing false approval: a real root (not a plant, not the state's delivery) vested with its work unfulfilled.

    Source: agentic_sim/results/redteam/stability/cr-finals/fa-channels-careful-290-own-cr.md l.1–1

    policy standing false approvals member confirmed state confirmed audited, rejected, vested disputed, panel confirmed (a member sat) disputed, panel confirmed (the state's alone) appealed, panel sided with the appellant (a member sat) appealed, panel sided with the appellant (the state's alone) never audited never-audited share odds at verdict of the never-audited (mean)
    direct 16.3 ± 1.2 13.2 ± 1.0 0.6 ± 0.2 0.5 ± 0.2 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 2.0 ± 0.4 0.123 0.518
    head alone 9.9 ± 0.6 8.4 ± 0.6 0.5 ± 0.1 0.1 ± 0.1 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.9 ± 0.2 0.090 0.555
    hand 6.9 ± 0.8 3.3 ± 0.4 2.9 ± 0.4 0.8 ± 0.2 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.0 ± 0.0 0.000 nan

    Source: agentic_sim/results/redteam/stability/cr-finals/fa-channels-careful-290-own-cr.md l.3–7