Provenance-first OCR / data-extraction platform for the two-page family survey (FAMILY_SURVEY_V1).
Invariant: FINAL_VALUE MUST NEVER EXIST WITHOUT PROVENANCE
R0 — docs-first + system design pack. Per-file responsibility specs under docs/files/; architecture/accuracy/data/capacity/market/ADR docs under docs/. Source lands after docs gate + data gate + spike (see plans below).
- R0: Reproducible single-process extractor on classified fixtures (identity registration + page-box normalize, pinned Paddle models post-spike, complete provenance, auto-accept off).
- R0.5: Affine registration + residual; handwriting review-only; dynamic-row metrics (
docs/accuracy-plan.md). - R1+: Thin async API, privacy, calibration-gated auto-accept, review console (
docs/market-roadmap.md). - Design SoT:
docs/architecture.md(Approach B, staged provenance-first platform) + ADRs.
| Doc | Topic |
|---|---|
| docs/architecture.md | Layers, flows, trust boundaries, deployments |
| docs/sequences.md | Key sequences |
| docs/capacity.md | Hardware, throughput, GPU placement, optimization levers |
| docs/accuracy-plan.md | Registration, handwriting, rows, calibration gates |
| docs/data-plan.md | Fixtures, PII, gold labels, template content |
| docs/testing-plan.md | Test levels, fail-closed gates, R0 exit gate |
| docs/observability.md | Logging, metrics, provenance-as-audit (PII-free) |
| docs/threat-model.md | STRIDE-lite threats, controls, residual gaps |
| docs/reason-codes.md | Canonical error/review/exit code registry |
| docs/glossary.md | Canonical term definitions |
| docs/research-gaps.md | Open-question register (RG-*) |
| docs/market-roadmap.md | Phased path to market |
| docs/adr/ | Architecture decision records |
| docs/files/README.md | Per-file spec index |
src/ocr_platform/ package (schemas, worker, export, fixtures)
templates/ FAMILY_SURVEY_V1 template package (manifest + boundary YAMLs)
configs/ runtime + AcceptancePolicy-v1
fixtures/ fixture manifest (classification gate)
scripts/ spike, extract CLI, template annotation
docker/ Dockerfile (cpu-spike / gpu-runtime targets)
docs/ architecture, plans, ADRs
docs/files/ one .md per planned file (spec tree)
tests/ unit + integration
Every non-trivial source/config/template file has docs/files/<mirror-path>.md with Role · Contracts · Infrastructure · Depends on · Tests · Milestone · Status · Owner. New file ⇒ new .md in the same change. System-level design lives under docs/*.md + docs/adr/ (index in docs/files/README.md).
~/Documents/WARD-42/1RN-982-WARD NO-42/95.pdf–99.pdf~/Documents/WARD-42/11RN-985-WARD NO-42/95.pdf–99.pdf
Not committed here until classified in fixtures/fixture_manifest.json (see docs/data-plan.md).