R-FDI v3.0.0 — Reliable Financial Document Intelligence

R-FDI v3.0.0 — Reliable Financial Document Intelligence

R-FDI v3.0.0 completes a three-stage, evidence-governed research program for
financial document intelligence. The release decision is V3_EXTENSION_SUCCESS.
This is a production-style research simulation, not a live bank deployment or a
regulatory-certification claim.

Research lineage

• V1 — governance foundation: validated fail-closed workflow, evidence, risk,
  routing, and audit mechanics. Its historical NO_PROMOTION decision is retained.
• V2 — real-document and CUDA study: evaluated fixed model families on
  authorized public documents. The offline research candidate earned PROMOTE
  after all ten frozen gates passed.
• V3 — production hardening: executed runtime, persistence, reviewer, load,
  recovery, security, Docker GPU, and accelerated-serving studies. All eight
  frozen extension requirements passed.

Measured highlights

• Donut CORD locked-test leaf F1: 0.8372; total exact: 0.9895.
• PP-OCRv5 + rules CORD total exact: 0.4632.
• Paired total-exact gain: +0.5263, bootstrap 95% CI [+0.4316, +0.6211].
• LayoutLMv3 FUNSD locked-test macro-F1: 0.7009.
• PaddleOCR-VL on the same 20 CORD development documents: native mean latency
  20.403603 s versus Docker/vLLM 10.726820 s, or 1.902111x mean
  speedup. Served content-presence recall was 0.917128.

Runtime and reliability evidence

• Real Compose services verified for API, worker, reviewer, Redis, PostgreSQL,
  MinIO, and MLflow.
• MLflow metadata persisted in PostgreSQL and its matching artifact in MinIO.
• API/reviewer behavior passed 7/7 checks.
• Local executable fault study passed 7/7; infrastructure stop/restart recovery
  passed 3/3 for Redis, PostgreSQL, and MinIO.
• Docker exposed one RTX 4090 Laptop GPU; the bounded PaddleOCR-VL server retained
  at least 35.51% observed VRAM headroom.
• The 24-case adversarial benchmark preserved all boundaries and capability
  isolation. Detector misses and benign activations remain explicit.

Explicit limitations

PaddleOCR-VL figures are development content-presence measurements, not official
structured CORD F1 or locked-final results. The application uses a SQLite durable
queue and filesystem object store; Redis is not yet the active job transport.
DocILE and REFinD require human-authorized access. Textract was skipped without a
positive AWS budget and valid credentials. Compose credentials are local defaults.
No paid cloud, production-bank, regulatory-compliance, or multi-GPU claim is made.

See the V3 final report, V2 technical report, and reproduction guide.