Capabilities cross repository boundaries
Mutations validated in one codebase reproduce, under different lineage roots, in unrelated codebases.
Each accepted mutation is replayed in N held-out repositories. Counted as a transfer only when invariants hold and reviewer evidence reproduces.
- cross-repo trials
- 1,284
- target families
- 5
- false-transfer rate
- 0.6%
Open: transfer to languages outside the current surface (e.g. Rust, Go) is not yet measured.
Public summary & integrity check
Each public case study ships a summary dossier and a SHA-256 digest so you can confirm the bytes served here are the bytes you hash locally. This is a byte-integrity check, not a cryptographic signature. Full reproduction materials (protocol, controls, expected outputs) are access-controlled and released only to approved researchers through the Research Console.
# Recompute the public SHA-256 digest shasum -a 256 transfer.reprod.json # expected: … # Or verify against the published manifest shasum -a 256 -c transfer.SHA256SUMS
The SHA-256 digest above provides byte-integrity verification of the public summary dossier. Detached Ed25519 signing (over signed research bundles) and external notary co-signing are tracked separately in the Foundation evidence ledger. Full reproduction kits are not published here — request access via the Research Console.