The Compiler May Read It, the Agent May Not: Keeping Part of a Research Code Away from a Coding Agent
Isolation controls cannot tell compilers from coding agents, so protected research modules remain readable.
A security note asks how to keep intellectual property in a physics-based research solver away from a coding agent while still letting the compiler read required modules. The authors classified fifteen read routes against a container, permission rules, and a sandbox. None of those controls can tell which program is reading, so the harness does not enforce the intended rule.
- Compiler must read modules a physics solver cannot build without.
- Coding agents must not read that same intellectual property.
- Fifteen read routes were tested against three isolation controls.
- Container, permissions, and sandbox cannot tell which program reads.
From the original article
1 min read at arxiv.orgThe compiler must read modules a physics-based solver cannot build without; the coding agent must not read that intellectual property. The harness does not ship that rule. We classified fifteen read routes against a container, permission rules and a sandbox.
By Shobhan Roy · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.