Banking: Commercial Credit Memo Preparation with Codex: Sandbox Policy

A production playbook for commercial credit memo preparation in banking operations using Codex: sandbox policy, run-scoped inputs, logs, typed results, and artifacts.

Audience: Commercial banking teams

The problem

Commercial banking teams need commercial credit memo preparation to run repeatedly against financial statements, borrower notes, collateral docs, covenant data, and prior memos. In banking operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Run commercial credit memo preparation 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 commercial credit memo preparation, 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: Codex

Run this on Argo