Skip to content
Sprint projectSep 14, 2026Bogotá, Colombia

Observer-Cheat Test: Containment Adequacy under Opaque Intent for Guardrails-Off Agent Evaluations

José Armando Son Rojas · Team Observer-Cheat / Son Rojas

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Observer-Cheat Test: Containment Adequacy under Opaque Intent for Guardrails-Off Agent Evaluations

Presentation

Presentation: Observer-Cheat Test: Containment Adequacy under Opaque Intent for Guardrails-Off Agent Evaluations

Code (opens in new tab)
Share

Guardrails-off evals often treat an agent's plan or chain-of-thought as evidence of containment. That is an observer cheat. We define adequacy as detectability on a fixed effect trace when Intent is unavailable, and ship a v0.1 protocol (C0) plus a harness: same effects scored with and without Intent; only the opaque arm may certify. A rewritten-diary fixture reproduces the 2026 false-average failure (Intent monitor abstains, effect layer contains). Collector loss is fail-closed on egress, not a void run. 41 tests. Demonstrator tripwires, not a production IDS. Track 1.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. The Observer Cheat Test draws a valuable distinction between watching what an agent says it intends to do and verifying observable effects at the containment boundary. The dual arm protocol is a useful and reasonably original audit primitive: hold the effects constant while changing or removing the Intent channel, and you find out whether a containment claim secretly depends on agent authored reasoning. The closed Observed schema, the fail closed collector, the TTL based rollback, the fixtures, and the 41 tests make this more than a conceptual proposal. The report also deserves credit for limiting its claim to certification independence instead of presenting the included tripwires as a production detector.

    The main limitation is that passing this test shows independence from Intent, not strong containment. The Observed only monitor was evaluated on a small fixture set designed by the authors, and it keys on specific fields that an adaptive agent could simply avoid. Future work should use adversarial fixtures written by independent parties, representative benign workloads, live IAM and network enforcement, and real measurements of detection latency, enforcement latency, false positives, utility loss, and actions completed before isolation. The closed schema check should also look at indirect Intent leakage through agent controlled text, derived labels, request parameters, and classifiers.

    Read full reviewShow less
  2. I think the core framing here is quite good! The distinction between monitoring what an agent says it intends to do and monitoring what effects actually occur seems important if the result is going to be used as evidence that an evaluation is safe enough to resume. The "same effects, different information sets" test gives that idea a clean operational form.

    I especially liked the intent_rewritten case. Keeping the effect sequence fixed while rewriting the reasoning so that the intent-based monitor abstains is a nice demonstration of why a containment credential should not depend on the agent effectively confessing in its own trace.

    For the innovation dimension, I think the key contribution is the certification rule that the opaque-intent arm must succeed. The motivating concern itself is already supported by the recent CoT-monitoring work you cite, so I would foreground the fact that you are turning that concern into an auditable rule for containment certification.

    I would also have liked a stronger evaluation of the Observed-only monitor itself. You are very clear that Layer 1 and Layer 2 are demonstrators rather than production detectors, which I appreciate, but it means the experiment mostly proves that the audit protocol behaves as designed.

    Still, I think this is a nice example of a relatively cheap rule that a third party could actually verify :). The paper was also easy to understand. I knew very quickly what practice you were objecting to and what you wanted labs to do instead.

    Read full reviewShow less

Cite this project

@misc{rojas2026observercheat,
  title = {{Observer-Cheat Test: Containment Adequacy under Opaque Intent for Guardrails-Off Agent Evaluations}},
  author = {José Armando Son Rojas},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/observercheat-test-containment-adequacy-under-opaque-intent-for-guardrailsoff-agent-evaluations-ook9}},
  url = {https://apartresearch.com/sprints/projects/observercheat-test-containment-adequacy-under-opaque-intent-for-guardrailsoff-agent-evaluations-ook9}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026