Agriculture Certification Review with Claude Code: Sandbox Policy

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

Audience: Agriculture compliance teams

The problem

Agriculture compliance teams need agriculture certification review to run repeatedly against certificates, inspection reports, supplier docs, shipment records, and audit rules. In agriculture operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Run agriculture certification 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 agriculture certification 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