Administrative Document Filing with Claude Code: Sandbox Policy

A production playbook for administrative document filing in administrative operations using Claude Code: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.

Audience: Operations teams filing repetitive documents

The problem

Operations teams filing repetitive documents need administrative document filing to run repeatedly against PDFs, forms, folders, metadata rules, and destination systems. In administrative operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Run administrative document filing in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.

Tradeoffs and failure modes

A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. For administrative document filing, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Runtime boundary

filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Claude Code

Run this on Argo