Repository navigation
R-FDI v3.1.0 — Slicing, Error Analysis & Model Risk Analytics
R-FDI v3.1.0 — Slicing, Error Analysis & Model Risk Analytics
R-FDI v3.1.0 adds an evaluation-analytics layer to the frozen v3.0.0 model and runtime baseline. Model weights were not changed, locked-final inference was not rerun for tuning, and the historical V1 NO_PROMOTION, V2 PROMOTE, and V3 V3_EXTENSION_SUCCESS decisions remain intact.
What is new
- A canonical, provenance-traced document and field evaluation table derived from committed predictions and authorized local metadata.
- Predeclared complexity, financial-structure, image-quality, field-family, and task-compatible model slices with confidence intervals, practical thresholds, and Benjamini–Hochberg correction.
- An explicit error taxonomy, field criticality analysis, paired model deltas, and mix-shift/Simpson audit.
- Development-fit calibration evaluation using genuine Donut sequence confidence, plus selective-risk and review-budget analysis.
- Transparent illustrative business-policy costs and sensitivity frontiers; these are not costs from a bank or production deployment.
- A controlled development-only corruption study for Donut and PaddleOCR-VL 1.6 Docker/vLLM on one CUDA GPU.
- Interpretable exploratory failure-slice discovery and simulated drift monitoring, clearly separated from confirmatory and production evidence.
- Reproducible SVG figures, detailed reports, dedicated v3.1 governance files, evidence manifest, verifier, tests, and CI regeneration checks.
Scope and limitations
- v3.0.0 remains the model/runtime baseline; v3.1.0 is an analysis release, not a new production deployment.
- Calibration and routing results are limited to compatible frozen evidence. Better probability calibration does not imply better risk ranking.
- Robustness uses ten development documents and content-presence metrics for cross-model analysis; PaddleOCR-VL content presence is not official structured CORD F1.
- Drift is a transparent stress simulation, not observed bank production drift.
- Business costs are normalized examples, not institution-specific economics.
- Only one physical GPU was used. No regulatory-compliance claim is made.
- SROIE and DocILE remain optional
HUMAN_ACTION_REQUIREDaccess items and do not block the release.