How do Astra, Luna and delegation yield more accepted work?
Strong ownership versus bounded Luna work versus doing a small operation inline: which tier for which task shape, measured on accepted outcomes, not on tokens alone.
The question and the decision it changes
GOD-QUESTIONS.md card · his words that raised itStrong ownership versus bounded Luna work versus doing a small operation inline: which tier, for which task shape, by accepted work, allowance, latency and recovery. Dependencies: GQ-008 (which model and route earn each task), GQ-012 (context), GQ-016 (owners without a bottleneck).
If, on ≥10 real dispatches of one task class on one unchanged route, the cheaper tier's accepted-work rate and repair cost are as good as the stronger tier's, the ownership premium is refuted for that class. Conversely, if setup + verification + repair erase the delegation gain, 'Luna for the dumb 80%' is refuted. Until then every multiplier is a proposal.
apparently reasoning's a big thing. A lot of things don't need more than medium reasoning, according to the chart. Medium reasoning makes it stretch a lot further, the usage. about four times further along with this config the compact oneShaan → Fable FA0 · 6 Sep 03:00
we needed a smart way to deploy lunar sub have astras use astra for reasoning and lunar sub agents for work because i'll be real we've just rinsed three weekly plans in the last 24 hours this is like unsustainableShaan → Fable FA0 · 6 Sep 03:45
we're going to go ultra compute efficient on this so every one of these guys are going down to medium thinking and they can use lunar sub agents to do 80 of the dumb stuffShaan → Fable FA0 · 6 Sep 15:30
If you can use Haiku 4.5 for sub-agents, that might be better … we're running low on our GPT and I kinda wanna reserve that for, like, more important shit … Just use Haiku for nowShaan → AGENT-ZERO · 6 Sep ~18:45
Research state
finding · unknown · next, from the cardOne helper lost its assignment through a rewrite and completed after a file-packet workaround; earlier worker DONE gates were narrower than intended outcomes. P6's integrated tier / lean-dispatch rules use one Playbook source and the two originally checked harness links; September 6 native discovery exposed a conflicting Hub projection in .agents/skills, so a name-only PASS cannot certify P6.
Net gain after setup, verification and repair. Account debit per route. Whether 'effort applied' can be read back from any rollout at all (J2: null in both).
Score naturally occurring work by task class and accepted outcome; do not launch another benchmark swarm. Re-run J2 only when a seat can persist applied effort in the receipt.
Evidence map
every fact cites a receipt path and a date and carries n; the rest is proposalreasoning_effort: null in both rollouts, so this is not a verified medium/xhigh contrast.domains/compute/runs/2026-09-06-j2/acceptance.json · runtime-audit.json · j2.json · 6 Sep 03:48–03:53 UTC+07 · Mac Mini · native openai- One brief, one run per effort: not general model-quality evidence or a bill comparison.
- No isolated subscription debit, invoice or per-run allowance was measured.
- Effective effort is not persisted in either rollout; only requested settings are known.
GOD-QUESTIONS.md · j2.json measured_with_limitsMind map
question → subquestions → modules → runs → WorksEach leaf links to its record. Branches are laid out by subtree size, not by hand.
Compute modules
allocated / done / unallocated by host, each with its verification line (plan/modules.json)- 1G11 · GQ-011 compute allocation: which tier for which task, measured partial · host holdOpen the dispatch tier skill and see per task shape a measured token and acceptance row from at least 10 real dispatches where the applied effort is recorded in the receipt (J2 today: ratio 1.0×, effort null in both runs).
- 2P6 · dispatch: tier table as a skill both harnesses read; native Luna delegation partial · host codexOpen
~/.codex/skills/subagentsand~/.claude/skills/subagentsand see the same tier table; one Luna dispatch from each harness returns a result and a measured overhead line lands indomains/compute/runs/(today: wording only, no measurement). - 3E1 · measure brief/handoff tokens vs output, time-to-first-correct-action, pings per outcome, on 10 real dispatches partial · host codexOpen
domains/compute/runs/<run>/overhead.jsonand see, for 10 real dispatches on one unchanged route, brief+handoff tokens vs output tokens and time-to-first-correct-action (today: 20-response windows confounded by the E3 route change). - 4E2 · cut and re-measure after P4/P5/P6 land; report the actual multiplier unallocated · host holdOpen the before/after page and see the same 10 dispatch shapes re-run after P4/P5/P6 with the multiplier stated and how many runs support it.
- 5G0 · GQ registry rewritten from the full corpus; falsifiers on all partial · host webuiOpen GOD-QUESTIONS.md and see 22 cards each carrying a decision target and a counterexample line (today 2 cards use the word falsifier).
preregistration.json)acceptance.json)runtime-audit.json)j2.json)Expected answer package
what would close itnull: the rollout or the harness persists what actually ran.Who is on it
Timeline
runs · decisions · his words, 5–6 SepLinks out
Agent entry
sed -n '/### GQ-011/,/### GQ-012/p' 00_AGENT_ZERO/GOD-QUESTIONS.mdcat 00_AGENT_ZERO/domains/compute/runs/2026-09-06-j2/j2.json | jq '.claim, .acceptance'node 00_AGENT_ZERO/domains/compute/runs/2026-09-06-j2/run-pair.mjs # re-run both arms (Mini, native route)
- Read first
00_AGENT_ZERO/GOD-QUESTIONS.md#GQ-011- Owner
- GQ-COMPUTE (closed) · next seat unallocated · last writeback 6 Sep 13:36
- Machine
https://siso-shell.pages.dev/t/U5/example.json- Done when
- Open the dispatch tier skill and see, per task shape, a measured token and acceptance row from ≥10 real dispatches with applied effort in the receipt (G11).