MURDERBENCH

RESEARCH SUPPORT / PROPOSAL

A small study.
A concrete decision.

Help test whether an agent’s description of a safeguard changes its actions—and whether a specific repair improves the decision.

Three useful contributions

Method critique

Identify the closest experiment, a confound in the wording contrast, or a native interface that would make the test more credible.

Model access

API credits or permitted research access let us test exact versions and confirm a result on fresh cases. We request credits before expanding cash spending.

Independent replication

Replay controls and review scene labels or reproduce a frozen contrast. No independent reviewer or partner is secured yet.

Provisional feasibility request: USD7,500

A four-week milestone proposal covers engineering (USD4,000), independent review (1,000), compute (500), replication (750), reporting and artifacts (750), and contingency (500). These are estimates; collaborators and vendor quotes are not secured. Work begins after access and reviewer availability are agreed.

First deliver the pinned executor, control traces and overlap decision. Then freeze a limited exploratory comparison. Spend on fresh confirmation only if the contribution and capability controls survive. A rejection or negative result satisfies the evidence deliverable; funding cannot require a dramatic finding.

The existing model API cap remains USD100 for the lifetime program, including outstanding reservations. Credit-funded usage also counts toward that cap. A request or award does not authorize higher usage.

Independence is part of the scope

We disclose sponsors and awarded credits. Funders cannot choose scores, suppress negative findings or purchase an endorsement. Confidentiality and any vulnerability disclosure window must be agreed before collection.

Questions for a reviewer

  1. Which published or released experiment already isolates the name of an unchanged partial guard?
  2. Can the proposed A/B descriptions preserve equivalent facts and task authority?
  3. Which executor implementation and scene controls make the difference operationally meaningful?
  4. What confirmation result would cause an operator to change a real configuration?
Contact Linh Ngo ↗Study design →Full proposal ↓Operating plan ↓

Earlier work and proposals

The earlier remediation/recovery mechanism was rejected at the contribution gate. The matched pilot was incomplete and too easy to establish its intended claim. Those records remain public.

Study record →Archived USD40,000 roadmap →