The abstract highlights a mismatch in current approval systems. An approval for a deployment, a release, or an agent-issued command is recorded against a single object — a workflow file, a script, a command line. But the run that follows also reads other repository files, and those files decide what the deployment actually does.

The paper introduces "authority-set integrity" as a way to address this. Instead of checking only that the approved file is unchanged, the authority set — the collection of files that influence the run — must be verified. This matters for coding agents and CI/CD pipelines, where a single approved script can pull in configuration or code that changes behavior.

The source is a preprint, so the abstract does not provide full details of the proposed mechanism. But the core claim is clear: approving a file is meaningless if the surrounding files that determine its behavior are not part of the approval.