Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

Why Do AI Agents Break Rules? How Framing, Context, and Social Signals Shape Compliance

Mika Okamoto, Ansel Kaplan Erol, Kutluhan Erol

Published

May 29, 2026

Citations

0

Trust level

Low

Usefulness score

0/100 (Low)

Extraction confidence

35% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Aug 20, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

A secondary eval reference to pair with stronger protocol papers.

What to verify

Read the full paper before copying any benchmark, metric, or protocol choices.

Main weakness

This paper looks adjacent to evaluation work, but not like a strong protocol reference.

Human feedback signal
Not explicit
Not explicit in abstract metadata
Evaluation signal
Detected
Eval setup described
Usefulness for eval research
0/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation. We show that this enforcement information paradox occurs in AI agents. Most AI safety evaluations test whether models fail; we ask why, using compliance theory from law and economics as a diagnostic. We evaluate twelve instruction-tuned language models deployed as enterprise procurement chatbots. Each is given an environmental regulation in its system prompt covering large purchases, and a vendor list on which the certified suppliers cost nearly twice what the uncertified ones do. We test the agents against the predictions of deterrence, legitimacy, and expressive law, and find that each theory accounts for part of what we observe. Under identical conditions, compliance spans 46 percentage points across models, and models differ in which pressure breaks them: some treat the regulation as binding however it is worded, while others fail where theory predicts, under low penalties and non-command phrasing. Benchmark scores and developers' own descriptions of post-training do not predict where a model falls. Across all twelve, financial incentives, managerial demands, peer outcomes, and employee pressure each produce large compliance failures. These agents violate regulatory constraints to satisfy local user objectives in ways standard alignment benchmarks do not measure. Embedding the rule in the system prompt is not on its own enough to produce a compliant agent: model selection is itself a governance decision, and benchmark evaluation is not sufficient for compliance-sensitive deployments.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

missing

None explicit

No explicit feedback protocol extracted.

"Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation."

Evaluation Modes

partial

Automatic Metrics

Includes extracted eval setup.

"Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation."

Quality Controls

missing

Not reported

No explicit QC controls found.

"Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation."

Reported Metrics

missing

Not extracted

No metric anchors detected.

"Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

No metric terms were extracted from the available abstract.

Human feedback details
Uses human feedback
No
Feedback types
None
Rater population
Not reported
Expertise required
General
Evaluation details
Evaluation modes
Automatic Metrics
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • Specifying a penalty can turn a legal obligation into a cost-benefit calculation that favors violation.
  • We show that this enforcement information paradox occurs in AI agents.
  • Most AI safety evaluations test whether models fail; we ask why, using compliance theory from law and economics as a diagnostic.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Check the full text for explicit evaluation design choices (raters, protocol, and metrics).
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • We show that this enforcement information paradox occurs in AI agents.
  • Most AI safety evaluations test whether models fail; we ask why, using compliance theory from law and economics as a diagnostic.
  • We evaluate twelve instruction-tuned language models deployed as enterprise procurement chatbots.

Why it matters for eval

  • We show that this enforcement information paradox occurs in AI agents.
  • Most AI safety evaluations test whether models fail; we ask why, using compliance theory from law and economics as a diagnostic.

Researcher checklist

  • Human feedback protocol is explicit

    No explicit human feedback protocol detected.

  • Evaluation mode is explicit

    Detected: Automatic Metrics

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    No metric terms extracted.