# End-to-End primary references and source roles

Accessed: 25 October 2026. Supports: the selected hash/Merkle/signature/provider primitives below, with their documented limits. Limitations: the D30 framing, eleven-layer policy, control inventory, resource limits, chronology and diagnostics are authored choices; neither these sources nor a local test certify a bank, provider, source ledger or this tutorial.

| Primary source | Directly read version / role | Boundary |
|---|---|---|
| [NIST FIPS180-4 publication status](https://csrc.nist.gov/pubs/fips/180-4/upd1/final) | August2015 final, March2023 revision-planning note; SHA-256 context | Revision planning is not a withdrawal claim; using SHA-256 is not FIPS/CAVP certification |
| [RFC9162 §2.1](https://www.rfc-editor.org/rfc/rfc9162.html#section-2.1) | December2021 Experimental; selected empty/leaf/internal hashes, split and exact inclusion proof | CT protocol context; this is authored ledger framing, not CT protocol conformance, consistency proof or financial completeness |
| [RFC8032](https://www.rfc-editor.org/rfc/rfc8032.html) | January2017 Informational; pure Ed25519 and §7.1 test vectors | Signature authenticates bytes under a key, not key authority, business intent or source truth |
| [W3C Web Cryptography Level2](https://www.w3.org/TR/webcrypto/) |22April2025 First Public Working Draft §25 Ed25519 plus noted point-validation differences | Draft status and runtime support retained; actual native operations are tested, no weaker green fallback |
| [PyNaCl1.6.2 official release](https://github.com/pyca/pynacl/releases/tag/1.6.2) and [libsodium maintainer fix](https://00f.net/2025/12/30/libsodium-vulnerability/) | Patched libsodium1.0.20-stable2025-12-31 valid-point mixed-order fix | Pinned actual Python profile, not vulnerable unpatched1.0.20; no custom curve arithmetic |
| [noble-curves2.4.0 release](https://github.com/paulmillr/noble-curves/releases/tag/2.4.0) and [versioned API documentation](https://github.com/paulmillr/noble-curves/blob/2.4.0/README.md) | Strict point parsing/subgroup/small-order and zip215:false verification, combined with actual WebCrypto | Upstream audit is not an audit of our orchestrator; declared dependency/provenance must accompany downloads |
| [AWS S3 Object Lock](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html) | Current version-specific retention/mode/legal-hold behavior, directly read25October2026 | The selected adapter is a synthetic fixed-COMPLIANCE model; no live observation, cloud request, retention setup or legal-sufficiency claim |
| [Python3.11 hashlib](https://docs.python.org/3.11/library/hashlib.html) | Native SHA-256 interface used by pinned child kernels | Primitive availability differs from trusted expectation/source authenticity; unavailable native operation must not imply pass |

Financial/accounting invariants are the exact previously frozen historical D30 contract, rather than a new recognition rule. The function directly executes Event-Sourced Balance Fold, Hash-Chained Journal, Merkle-Batched Journal Commitment, Signed Ledger Checkpoint and selected External WORM/Blockchain Anchor. It rechecks historical balanced-journal and exact-correction invariants through that validator. The other20 earlier algorithms are not executed in this function. Separate local SQL/reconciliation/close integration is separately evidenced; its archived observation is not a fresh database query or cloud-provider receipt.

Historical example: **not useful** without complete reusable journals, account and projection histories, authentic independent retained commitments, key-policy history and provider evidence. The public RFC vectors and both Cedar branches are explicitly synthetic/authored fixtures. No invented named-bank incident or full copyrighted specification is reproduced.