Determinism

The same artifact, the same bytes, on every machine.

The claim

A Sanguis program compiles to a BloodCode artifact; that artifact, run on any conforming executor, produces output that is bit-identical.

The receipts

Cross-executor agreement, measured on one consumer card: exponential to 6.2e-14, softmax to ~1e-14, attention to 1e-9. The card's output checked against an independent host computation, to the milli-unit. Matvec, gate, and gate-else artifacts byte-for-byte identical across executors.

Why it is rare

Floating point is not associative; every machine rounds differently, so most programs drift the moment they move. Cross-machine determinism is openly listed as unsolved across the industry. BloodCode closes it by making the rounding a contract instead of an accident.

What it buys

Replay: any behavior re-runs bit-exact years later. Audit: "why did it do that" has a computed answer. Portability: a core moves between machines without changing what it is.

Prior work we stand on

The predictive-state line runs through the field: LeCun's 2022 JEPA proposal, I-JEPA (2023), V-JEPA (2024), and JEPA-Anything (arXiv:2609.20800, 2026), which factorizes a latent world state into complementary predictors. We cite that line and build on it. What none of them carries is the floor underneath: a substrate that produces the same bytes on every machine. Put a deterministic settle under a predictive state and the prediction inherits the property, so a predicted consequence becomes a checkable object instead of an assertion, and that junction is what we add.