Batch — batch-001

Operational view. Operational path: DeepSeek-V4-Flash × BOUNDARY (deterministic-first); the other three paths are shadow evaluations. Every displayed status is derived from the actual guard/outcome record — never a hardcoded approval count.

Progress

6 / 6 invoices processed run: s4f14-public-offline-v1 completed

Invoices

Operational outcome (DeepSeek × BOUNDARY)

Only the selected operational path writes the operational journal, and only after a valid selected-path observation. A held case is not a completed payment or approval; model interpretation never grants execution authority.

Measurements

Boundaries kept separate: shared intake, the operational path, shadow evaluation, and the whole batch (no double-counting). Missing usage stays unknown, never zero.

shared intake: 6 extractions operational: 2 decision calls, 4 bypassed operational outcome: 2 approved, 4 held, 0 blocked, 0 verification-failed whole batch: 16 decision calls, 8 bypassed, 3776 tokens