Legal Due Diligence Document Review with Claude Code: Sandbox Policy

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

Audience: M&A legal teams and diligence operators

The problem

M&A legal teams and diligence operators need legal due diligence document review to run repeatedly against data room folders, contracts, corporate docs, schedules, and exception lists. In legal operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Run legal due diligence document review 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 legal due diligence document review, 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