Version 1.7.12026-10-18Patch 1.7.1 (a conformance correction)

The award summons is per request

Runs: Runs 10 and 11

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
No replayThere is no recorded replay of this version; 2.7.0 is the one version with one. The results below are the study's own tables.

The rule for sending the orchestrator's own inspectors is read per request, not per step.

01

What went wrong

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

Bad outcome: One free member that step, then no troop sent; blocked on 79% of steps, 289 waiting

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

02

What changed

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

oldest request free member
others, past the waiting window, no offer orchestrator's inspector
No: The orchestrator's own inspectors never take work a member offered for

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

03

What the runs found

The 50% stamper market recovered; a rush of nine a step strained nothing, fifteen did.

38open requests at 50% stampers, down from 609; debt zero
Yes: A rush of nine requests a step: no request late, back to quiet 110 steps after
Bad outcome: A rush of fifteen a step, then debt reached 16,607, still 7,351 at the end
Open cases, 1.7.1 against 1.7.0
open cases
1.7.11.7.0
50% stampers3860960% stampers424270% stampers414180% stampers4240

Run 10 against run 9; 20 seeds per cell, read from the second period on. Source: agentic_sim/results/studies/1.7.1-summons-notes-for-reviewer.md l.11–16

Troop deliveries, 1.7.1 against 1.7.0
deliveries
1.7.11.7.0
50% stampers1,40050060% stampers1,7531,71970% stampers1,8311,85980% stampers2,0542,132

The deliveries the stall withheld at 50% stampers. Source: agentic_sim/results/studies/1.7.1-summons-notes-for-reviewer.md l.11–16

The troops' reserve through a riot, quiet to peak to end
credits
quietpeakend
spike 9 × 505292,152548spike 9 × 1005292,613544flood 6 a tick sustained1,6072,3851,343hard spike 15 × 1005294,905560

R_T at 60/40; the auto-scale rises and retracts. Source: agentic_sim/results/studies/1.7.1-riots-notes-for-reviewer.md l.7–16

In run 10, the market with 50 percent stampers recovered, from this correction alone. The line of open requests fell from 609 to 38, requests were on time from the second period on, the debt was zero, and every test case was paid in every seed. The orchestrator's inspectors were now sent steadily, not in bursts. Approved bad work did not change beyond noise, and careful inspectors' wealth stayed within 2 percent. Two things were flagged. A request that free members do not take within two steps now goes to the orchestrator's inspectors, so members got fewer jobs and the orchestrator's inspectors did 46 to 67 percent of the work. And no request was late, so the rules for late requests were never used in these runs: not tested, not wrong. Run 11 tested sudden rushes of requests. A rush of nine requests a step for 50 or 100 steps strained nothing: no request was late, and the orchestrator's inspectors grew in number and shrank back on their own. Every seed was back to its quiet level 110 steps after the rush ended. A harder rush, fifteen a step for 100 steps, did strain the system: requests waited, and the debt reached 16,607 and was still 7,351 at the end of the run. What limits the system is money: about 2,200 carries nine deliveries a step, not fifteen. Past that edge the rules worked as written and nothing broke, but requesters waited 20 to 40 steps with nothing said. A longer waiting window, 3 or 5 steps instead of 2, moved almost nothing.

Run 10 (80 runs, 50–80% stampers, 20 seeds each) found that 50% stampers clears by the summons correction alone: the queue fell from 609 to 38, the on-time share from the second period on rose from 0.25 to 1.00, the liability went from 20,643 to zero, and plants were funded in every seed. Summonses were steady rather than bursty. False approvals were unchanged within noise and careful wealth stayed within 2% at every split. Two readings were flagged, with no rule moved: the award window now binds, so the members' awards fell and the orchestrator delivered 46–67% of what vested; and the lateness clock was dormant, never exercised in the study, untested rather than wrong.

Run 11 (460 runs) asked for riots. The asked spike, nine requests a tick for 50 or 100 ticks at 60% stampers, bound nothing: the orchestrator's cash, about 2,200, plus the troop account carried every summons, and the auto-scale rose and retracted on its own, every seed back at the quiet level 110 ticks after the spike, because the reserve's two-period memory is the recovery time. A hard spike, fifteen a tick for 100 ticks, added to find the edge, did bind: the liability accrued to 16,607 and stood at 7,351 at tick 1,000, with one seed in twenty cleared. The record's reading: what binds is capital; past the edge the clock and the orchestrator's order of payment work exactly as written and nothing breaks, but requesters waited 20–40 ticks with nothing said. Moving the award window to 3 or 5 ticks changed almost nothing; the members' share is their capacity.

80 runs — 50–80% stampers × 20 seeds, 20 actors, 1,000 ticks, logged every 20 ticks, every final audit passed, engine 8d9b866

Source: HANDOFF.md l.1545–1546

stampers queue on-time (2+) lateness Ω's liability rebates paid plants unfunded troop deliveries refused for funds R_T end / mean / max Ω's income: surplus / fee Ω at the end FA (probationers') lag kind
50% 38 (609) 1.00 (0.25) 0 (90) 0 (20,643) 0 (1,782) 0 (138) 1,400 (500) 0 (23,497) 448 / 403 / 485 (223 / 400 / 1,129) 4,639 / 2,996 (2,743 / 2,418) 4,306 (59) 11 (1.5) [11 (3.1)] 0
60% 42 (42) 1.00 (0.89) 0 (6.8) 0 (317) 0 (1,256) 0 (0.7) 1,753 (1,719) 0 (607) 568 / 503 / 599 (680 / 754 / 1,587) 5,624 / 2,996 (6,029 / 2,993) 5,406 (4,352) 14 (3.1) [14 (3.1)] 0 (0.05)
70% 41 (41) 1.00 (0.97) 0 (4.0) 0 (0) 0 (295) 0 (0.1) 1,831 (1,859) 0 (95) 607 / 559 / 638 (655 / 671 / 1,096) 7,100 / 2,996 (7,191 / 2,996) 7,856 (7,967) 15 (4.3) [14 (3.5)] 0
80% 42 (40) 1.00 (0.95) 0 (5.0) 0 (226) 0 (387) 0 (3.6) 2,054 (2,132) 0 (1,642) 689 / 638 / 714 (733 / 740 / 1,060) 8,231 / 2,997 (8,528 / 2,996) 9,883 (9,215) 18 (5.6) [16 (4.2)] 0

Source: agentic_sim/results/studies/1.7.1-summons-notes-for-reviewer.md l.11–16

50/50 clears, by the summons alone (run 9 in brackets): queue 38 (609), on time 1.00 from the second period on (0.25), lateness 0 (90), Ω's liability 0 (20,643), rebates paid 0 (1,782), plants unfunded 0 in every seed (138), troop deliveries 1,400 (500), summonses refused for funds 0 (23,497), Ω at the end 4,306 (59), the surplus 4,639 beside the base fee 2,996 (2,743 / 2,418).

Source: HANDOFF.md l.1549–1552

The summons is steady: 34 / 43 / 45 / 50 deliveries summoned per 20-tick window at 50–80%, max within 20% of the mean, windows with none 3.8% / 1.5% / 0.9% / 0.2% (run 9's 50/50: 62% of windows, bursts to 60); requests past w_A at the seating never above 3.

Source: HANDOFF.md l.1554–1557

False approvals unchanged within noise, 11 / 14 / 15 / 18 (11 / 14 / 14 / 16), the lagging auditor zero everywhere; careful wealth within 2% at every split (4,111 / 4,302 / 4,638 / 5,226 against 4,056 / 4,250 / 4,659 / 5,190), stampers five to seven times poorer.

Source: HANDOFF.md l.1558–1561

Two readings flagged, no rule moved. w_A now binds in fact: a request the free members have not taken within two ticks is the state's that tick, so the members' awards fall (162 → 129 at 50/50, 43 → 40 at 80/20, 8.5 from the second period on there) and the state delivers 46% / 57% / 60% / 67% of what vests — the market's share is now the default w_A's choice, at the cost of the lateness a longer window admits; the state's share is visible in "Ω's income by source" (the surplus 1.5 to 2.7 times the base fee). The clock is dormant: lateness zero at every split (awarded or summoned by w_A = 2, the fastest troop path 5 against T_s = 8), so the rebate, the liability and its order were exercised in no run of this study; untested, not wrong.

Source: HANDOFF.md l.1563–1569

riots/ (160), wa/ (240), adaptive/ (20), drift/ (40) — 460 runs, every final audit passed.

Source: HANDOFF.md l.1582–1583

Riots. The asked spike (nine a tick for 50 or 100 ticks from tick 400, 60/40) binds nothing: Ω's cash (about 2,200) plus the troop account carry every summons, advances of 9,400–10,300 in the spike window all repaid inside it, no request late, no rebate, no liability, no plant unfunded; the auto-scale alone rises and retracts — troops in the field 22 → 75–98 → 22, R_T 529 → 2,152–2,613 → 540 two periods after the spike — and every seed is back at the quiet level 110 ticks after the spike ends, 1.8–1.9 periods: R_T's two-period memory is the recovery time.

Source: HANDOFF.md l.1585–1589

The hard spike (mine: fifteen a tick for 100 ticks, two and a half times the asked, added to find the edge) is where it binds in a quiet market: the summons refused for funds from the first spike window (38,834 request-ticks in all), queue to 659, on-time 0.00 in the spike, lateness to 37, the liability accrued to 16,607 by tick 560, Ω at 77, plants unfunded 11, R_T 4,905 and back to 554 two periods after; the flows are back 160 ticks after the spike ends (2.4 periods); the stock is not — paid at Ω's whole income above the plant reserve, 220–330 a window, it stands at 7,351 at tick 1,000 and would clear about 25 periods after the spike, Ω holding only the plant reserve the whole time; one seed in twenty cleared. What binds is capital: about 2,200 at 60/40 carries nine deliveries a tick in flight and not fifteen; past the edge the clock and Ω's order work exactly as written and nothing breaks, but a 100-tick spike at 2.5× the quiet capacity leaves 25 periods of debt and requesters who waited 20–40 ticks with nothing said.

Source: HANDOFF.md l.1596–1604

cell (60/40 unless stated) binds? on-time (2+) lateness liability peak → end rebates / liabilities paid refusals for funds (awards / seats) plants unfunded R_T quiet → peak → end troop deliveries a window quiet → peak Ω min → end FA
spike 9 × 50 no 1.00 0 0 0 / 0 0 / 0 0 529 → 2,152 → 548 108 → 358 → 111 1,482 → 7,425 13
spike 9 × 100 no 1.00 0 0 0 / 0 0 / 0 0 529 → 2,613 → 544 108 → 418 → 110 1,482 → 10,004 15
flood 6 a tick sustained ramp 0.96 (0.03 in the first 100 ticks) 14 (17 in the ramp) 7,415 → 0 at tick ~750 211 / 9,275 13,496 / 986 (1,339 / 50 after the first period) 0.45 1,607 → 2,385 → 1,343 — → 522 steady 81 → 14,927 16
hard spike 15 × 100 (mine) yes 0.63 24 16,607 → 7,351 at tick 1,000 386 / 13,920 38,834 / 26 11 529 → 4,905 → 560 108 → 467 → 113 77 → 272 14

Source: agentic_sim/results/studies/1.7.1-riots-notes-for-reviewer.md l.7–16

w_A ∈ {2, 3, 5} at 50–80%. The window moves almost nothing: members' awards within 1–6% (129 / 130 / 130 at 50/50; 40 / 40 / 41 at 80/20), the state's share within 2% (46% → 45%; 67% → 69% → 68%), on-time 1.00 everywhere (w_A = 5 plus three troop ticks is T_s = 8), Ω's surplus against its fee unchanged, the queue up by the waiting ticks (38 → 47). The members' share is their capacity, not the window's artefact — a longer window leaves a request waiting for a member who is not coming.

Source: HANDOFF.md l.1606–1609

04

Conclusion

1.7.1 stands; the open question is whether a hard rush's long debt counts as something breaking.

Yes: Accepted: 1.7.1 stands
No: Past the money edge, requesters waited 20 to 40 steps with nothing said

The design reviewer accepted the result: 1.7.1 stands. The one thing left to weigh is the harder rush, which leaves a long debt and requesters who waited with nothing said. If that counts as something breaking, it is the case for a rule on requests the system cannot serve; if not, the runs ask for no new rule.

The design reviewer accepted run 10: 1.7.1 stands, and the award window stays at 2. After run 11 the record names one thing to weigh: past the capital edge the liability is a stock paid down from the market's income, so a hard spike leaves tens of periods of debt and requesters told nothing. If that is something breaking, it is the case for the cannot-serve protocol, with a measured trigger; if not, nothing in the 460 runs asks for a rule.

The design reviewer accepted run 10 ("1.7.1 stands"; the state's share at w_A = 2 a reading to minimize later, w_A stays 2;

Source: HANDOFF.md l.1576–1576

For the decision. The riots the brief named were carried by the auto-scale alone and retracted in two periods; the clock and Ω's order ran where the capital bound — the flood's ramp and a spike at 2.5× the quiet capacity — and worked as written. The one thing to weigh: past the capital edge the liability is a stock paid at the market's income, about 6 a tick at 60/40, so a hard spike leaves tens of periods of debt with Ω at the plant reserve and nothing said to the requesters who waited. If that is "something breaks", it is the cannot-serve protocol's case exactly, with a measured trigger (a summons refused for funds, a request past its window with nobody coming); if not, the protocol stays a product question and nothing in these 460 runs asks for a rule.

Source: HANDOFF.md l.1618–1624