Shared scoring features
8
Four current-input and four prior-history features use the same offline and serving module. Implementation fact, not a quality score.
Validation notesCase study / Historical ML study + workbench
A transaction inspection workbench combining prior-only features, versioned model artifacts, tenant-scoped access, and exact saved-result retries.

Solo project; AI-assisted development.
Shared scoring features
8
Four current-input and four prior-history features use the same offline and serving module. Implementation fact, not a quality score.
Validation notesLocal scoring p95
16.77 ms
12 October 2026 client-inclusive measurement: 4,800 generated unlabeled scores over 120 seconds, four clients at 10 requests/s each, zero failures. Not saturation or production latency.
Validation notesPython checks passed
404
Dated hosted engineering baseline with zero failures, errors or skips. CI uses synthetic model fixtures; this does not establish fraud-model quality.
Validation notesThe idea
Evaluation and serving can disagree when features include future information or retries recalculate accepted transactions.
The implementation
Shared prior-only feature construction between offline and serving paths, then added atomic SQLite replay and role-controlled inspection.
10 October historical quality study, 12 October local operating workload and dated hosted engineering baseline remain separate. The repository and CI are not publicly accessible; receipt filenames and scope are listed above.