04 — Evidence Docket
The Evidence Docket
Everything RTFCT produces is designed to be handed to a regulator, an auditor, or a court without translation. The docket is where those artifacts and their specifications live.
Proof Pack
The downloadable artifact set an auditor or opposing counsel would ask for: the ledger specification, the retention anchor, and the sample contractual record below.
Ledger Specification
SHA3-256 signing and chaining over every captured inference event, producing court-ready artifacts whose integrity is verifiable without RTFCT.
Retention Anchor
A mandatory 1,095-day (three-year) immutable retention window on every record, matching the longest common discovery horizon across covered jurisdictions.
Jurisdiction Mapping
Each policy wave states which obligations it satisfies, so a record can be traced from an inference call to the specific rule it evidences.
Contract documents
Master services, service level, and white label agreements are issued directly during onboarding rather than published here. Start with a plan.
Enforcement analysis lives in the Docket: Statutory Autopsies of actual AI enforcement actions, with the log structure that would have answered the examiner.
Vault specifications are documented on the VLT product page.