arXiv (All)
open access
The Compiler May Read It, the Agent May Not: Keeping Part of a Research Code Away from a Coding Agent
The 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. None of the three can tell which program
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- The Compiler May Read It, the Agent May Not: Keeping Part of a Research Code Away from a Coding Agent#1108601
- Learning When and How to Intervene: A Hindsight-Distilled Sentinel for Coding Agents#1145124
- Learning When and How to Intervene: A Hindsight-Distilled Sentinel for Coding Agents#1136889
- cfahlgren1/react-code-instructions#786933
- Leveraging Large Language Models to Obscure Code Stylometry: A Comparative Study of GPT-3.5 and GPT-4#300013
Record · ID 1130137
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive