06-reference/research

delegation judgment atrophy studio throughput norm

2026-11-06·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
delegation-judgmentautomation-biasskill-decaystudio-throughputdecision-authority

The throughput norm is not the rule under test: RDCO's arrangement sits on the safe side of the one measured automation threshold, but it lands squarely in the automation-bias geometry instead, and no RDCO rule closes an outcome loop on a founder decision

The question

"Does RDCO's studio-throughput norm ('build when discovered, never park for the night cron') cause the founder's own decision-making skill to atrophy by routing judgment through Ray instead of him, and how do other founders who delegate heavily to AI agents deliberately keep their own judgment sharp?"

Auto-promoted from the research backlog on 2026-11-06 (score 13/15) out of [[2026-10-30-every-marx-alienation-coding-agents]], whose closing move - that an idle agent factory is a choice, not a loss - the vault logged as a direct and unanswered challenge to feedback_studio_throughput_no_deferral. The subject here is the norm and the rule set, not any person.

What we already know (from the vault)

What the web says

The one measured stage threshold, and RDCO's arrangement is on the safe side of it.

The failure shape RDCO actually inherits is automation bias, and it is the failure mode of exactly this arrangement.

Decay rates: the direction is settled and it is the opposite of the popular claim; the rate is not.

Direct evidence on heavy AI delegation and operator skill: thinner than the discourse implies, and it measures the wrong construct.

Founders who delegate heavily and deliberately preserve judgment: the evidence base here is weak, and should be labelled as practitioner hypotheses rather than practice evidence.

Convergences and contradictions

Synthesis for RDCO

The studio-throughput norm is the wrong rule to put on trial, and the brief's first finding is that the challenge in the parent piece is misaimed. Read the norm's own text: feedback_studio_throughput_no_deferral governs when buildable work runs (immediately rather than parked) and how many artifacts an overnight round takes. It is a scheduling and utilization rule. It does not touch who decides anything. Stewart's closing move - that an idle agent factory is a choice - is an argument about mode selection, which in RDCO's rule set lives in feedback_distinguish_decision_from_action, feedback_auto_mode_signal_to_noise and feedback_ic_vs_production_mode, none of which the throughput norm overrides. A norm that makes execution faster cannot by itself move a decision from the founder to Ray, because the reversibility classifier, not the clock, assigns decisions. Verdict on the norm: keep as written. The one real second-order effect is volume at the review boundary, and the vault already answered that: liability-grade review is sublinear in artifact size (66 reviewer hours against 11,277 audit hours, 14x span in work versus 2x span in review), so more artifacts per round does not mechanically mean proportionally more judgment load.

Map RDCO onto the stage taxonomy and the arrangement sits on the safe side of the only measured threshold - but it lands in a different, better-documented failure shape. In Parasuraman/Sheridan/Wickens terms, RDCO is not one point on an autonomy scale but a bifurcated profile: full automation across all four stages for the reversible class, and Stage-3-retained for the irreversible class (deploys from main, external sends, spend at or above threshold, publishing), which corresponds to Endsley & Kiris's protective intermediate levels. Onnasch's measured collapse in return-to-manual performance (tau -.90) happens when automation crosses into choosing; RDCO's irreversible class does not cross it. Full autonomy does apply to the reversible class, where by construction a degraded take-over is cheap - that is a genuinely good structural property and it should be stated as such. But protective is not the same as neutral. Endsley & Kiris still measured lower comprehension-level SA under semi-automation than under manual control. And the configuration where a reliable aid recommends and the human retains the decision is precisely the automation-bias geometry, with the worst-measured numbers in this whole brief attached to it: 41% omission and roughly 65% commission errors in Skitka et al., with disconfirming evidence directly available. feedback_advisor_not_pair_programmer directs Ray to frame outputs as "a question + recommended answer." That is the directive-aid configuration by name. The honest restatement of the risk is therefore not atrophy; it is bias in a retained decision, and it is a property of the output format, not of anyone's habits.

The actual gap in the rule set is that nothing closes an outcome loop on a decision once it is made. Every verification mechanism RDCO owns points at the agent's work product: verify-vault-write, verify-strategic-output, verify-dispatch, verify-pdf-output, station-critic, the fresh-eyes rule, feedback_workflow_agent_output_integrity. Not one of them records what was recommended, what was chosen, and how it turned out. The convergent read across Casner, Chang et al., Endsley & Kiris and Kahneman & Klein is that judgment is maintained by outcome feedback in a regular environment, and specifically not by the count of decisions passing through. RDCO currently generates a high count of decisions and close to zero recorded outcomes on them. Bastani's GPT-Tutor-versus-GPT-Base contrast is the one empirically-supported lever: the harness determines whether capability survives, which means this is fixable in the rule set rather than by anyone changing how they spend their time.

Named amendment, one line, accept or reject: amend feedback_advisor_not_pair_programmer so that every DECISION NEEDED item Ray surfaces is logged to a decision record carrying the recommendation, the strongest case against it, the option chosen, and a check-back date - and Ray resurfaces the record at that date with what actually happened. This targets the mechanism the literature supports (feedback and depth, not volume), it adds the Sarkar-style provocation that the automation-bias numbers argue for, and the whole obligation falls on Ray's output format and Ray's follow-up, requiring nothing of the founder beyond the decision he was already making. A cheaper partial version, if the full record is unwanted: keep the recommendation but require the strongest case against it in the same message, and drop the check-back. If neither is accepted, nothing breaks - the arrangement remains on the safe side of the one measured threshold, and the residual risk stays where this brief found it, in bias rather than in decay.

On the second half of the question, the answer is that there is no practice evidence to copy. Willison, Ronacher, Klaassen, Karpathy and Yegge all converge on the same unmeasured intuition - move your attention to the ends of the loop and keep a verification step you personally own - and every one of them is writing an essay, not reporting a result. Willison's own admission that knowing when not to review every line "feels deeply uncomfortable" is the most honest statement in the set. Notably, no named operator has adapted decision journals, pre-mortems or any established decision-hygiene practice to AI delegation, which means the amendment above is not RDCO copying a known pattern; it is RDCO instrumenting something nobody has instrumented. That cuts both ways: no precedent to borrow, and no evidence it works either.

Why this is in the vault

This brief resolves the specific open question [[2026-10-30-every-marx-alienation-coding-agents]] left on the table, by finding that feedback_studio_throughput_no_deferral is not the rule the alienation argument reaches, and by relocating the risk from skill decay to automation bias in the one rule that actually sets the decision-surfacing format, feedback_advisor_not_pair_programmer. It is the evidence base for a single accept-or-reject amendment to that rule, and it supplies the calibrated citation set RDCO needs when the agents-in-production positioning touches operator-skill claims, where confident essays currently outnumber measurements by a wide margin.

Open follow-ups

Related

Sources

Vault

Read in full this pass

Abstract-only, secondhand, or blocked (flagged, not retried)