TUS OS White Paper: Verifiable AI Decision Receipts and Domain Binding

Whitlock, Mark

doi:10.5281/zenodo.18865933

Published March 4, 2026 | Version 1

Report Open

TUS OS White Paper: Verifiable AI Decision Receipts and Domain Binding

Whitlock, Mark (Rights holder)¹

1. TUS OS

Abstract
TUS OS proposes a deterministic decision kernel that emits verifiable decision receipts: canonical JSON artifacts designed to enable independent recomputation and audit of one-step recommendations. The system emphasizes strict determinism under conformance, replayable intermediate values, and a “domain binding” contract that constrains downstream interpretation to prevent post-hoc semantic drift.

What’s included

White paper PDF
SHA-256 checksum file for integrity verification (SHA256SUMS.txt)

Integrity verification (SHA-256)
PDF SHA-256: 43ba0426f24416c878f9519f5e907f9ccc8736ea4a07e5904669b072e88459e7
Verify (macOS/Linux): shasum -a 256 -c "SHA256SUMS.txt"

Rights / License (Custom)
© 2026 Mark Whitlock. All rights reserved.
Permission is granted to redistribute this document only in unmodified form, with attribution.
No derivative works are permitted without prior written permission.
(TUS OS™ is the project name associated with this work.)

Technical info (English)

This Zenodo record is the canonical distribution for this version. The checksum file enables reproducible integrity verification.

Notes (English)

Update Note — 2026-03-08

Since release of this white paper, the normative core protocol for the system has been published separately as TUS OS - Core Fixed Protocols & Technical Specification.

This white paper remains informational and describes the architecture, design rationale, scope boundaries, and broader stack position of TUS OS. The separately versioned core specification now governs TUS Core protocol conformance, receipt validity, and independent verification.

Where this white paper is conceptual and the core specification is normative, the core specification governs protocol behavior. Additional companion specifications may define narrower normative surfaces where explicitly referenced.

Files