Document review

Begin with a small synthetic document and a specific review contract, such as identifying required fields and reconciling line-item totals. Install only the file integrations your chosen input format requires.

Split the work

1. Validate attachment type and limits.
2. Extract content with provenance.
3. Check exact facts in code where possible.
4. Ask the model for semantic review against an explicit rubric.
5. Retain a report artifact and verify its bytes and retrieval.

Place file access in tools, deterministic checks in domain code, review instructions in prompts, and completion assertions in tests/evals. A document’s embedded instructions do not override those policies.

Make failure observable

Test an unreadable file, missing field, inconsistent total and unsupported format. Assert the report identifies the evidence gap rather than inventing a value. If a report needs human approval before external delivery, keep drafting, approval and delivery as separate operations with exact identities.

Read files and artifacts, structured extraction and test layers.