agent-blast-radius

To audit an autonomous agent's footprint, inventory touched files, commits, APIs, processes, and scheduled tasks within a specific time window. This generates a structured blast-radius report for inspecting surface exposure and governance reviews.

An agent blast radius report is a structured summary of all filesystem items, commits, API calls, and processes an autonomous agent has modified. You need one for weekly agent-footprint reviews or post-incident investigations to identify unexpected surface exposure.

Yes, you can perform a post-incident investigation on long-running agents by collecting and aggregating API calls, spawned processes, and file modifications by surface area within a defined time window to generate a deterministic footprint report.

You inventory scheduled tasks created by an autonomous agent by running a deterministic footprint collection workflow. This enumerates created tasks alongside touched files and commits, aggregating them into a structured blast-radius report for governance checks.

Agent footprint auditing is suitable for scheduled pipelines and long-running tasks. It deterministically collects and aggregates touched files, authored commits, and spawned processes within a time window to produce a blast-radius report for inspection.