المصدر الإنجليزي — الترجمة قيد الانتظار — الإنجليزية

Reproducibility

Identity chain

Every research artifact carries the chain that produced it:

dataset fingerprint → feature schema hash → model manifest (scaler, weights)
→ git commit → effective config (seeds, splits, purge/embargo)

Run snapshots (research_run_snapshots) store these at run time; provenance

fields may be NOT_RECORDED (honest) but are never invented or backfilled.

Determinism sources

freeze (research/forward_test.py).

What breaks reproducibility (and is therefore guarded)

ThreatGuard
dataset mutationimmutable fingerprinted artifacts
feature reorderingschema hash changes → model invalidates loudly
silent default drifteffective config recorded per run (BUG-183)
RNG divergenceseed-before-model construction
"works on my machine"manifests carry git commit + dataset ID

Rebuilding from ledgers

The accounting/experience ledgers are immutable; research evidence stores are

append-only. The system is designed so that **everything derivable is

rebuildable** from the immutable records.