Sample Proof Pack — Verify It Yourself

{^} SAMPLE PROOF PACK // DL-20261028-000001 DOCLOCK 1.5 (183/183 CHECKS) · CLK-ATTEST-1 (±1s UTC) · OFFLINE PERMISSIONLESS VERIFICATION

{^} Prove It Yourself — No Account, No Server, No Trust Required (Law 4)

This is a complete, real DocLock 1.5 proof pack (DL-20261028-000001) for a fictional sample document, published so anyone can verify it with their own hands. Download the files below, inspect the 3D Depth Holographic Forever Seal and its deterministic Ice Fractal Vein, and check the seal yourself — 100% offline. Then toggle the 1-character edit ($48,500.00 → $48,900.00) and watch what happens.

§7.2 CANONICAL CLAIMS LINE: “DocLock proves a document is unchanged, not that what it says is true.”
{^} MASTER SPEC §4.3 // 3D DEPTH HOLOGRAPHIC FOREVER SEAL P1-PROVENANCE-1 · 1-OF-1 ICE FRACTAL VEIN
GENESIS MINT: ALFA-P1-ORG-MESA-85206-000001-E3 (SERIAL #000001)
{^} FOREVER SEAL • DL-20261028-000001 • ALFA-P1-ORG-MESA-85206-000001-E3 • CLK-ATTEST-1 •
SERIAL #000001 // 1-OF-1
{^}
VERIFIED (RULE 9)
SERIAL #000001 · LOCK
ATTESTED: ±1s UTC
[ 3D Depth Parallax: translateZ(0px → 64px) · Hover/Touch to Tilt ]
§4.3 ANATOMY // DERIVED NUMBER = WHEN + WHO + WHAT + ALFA LABEL

Data-Bearing Ice Fractal Vein & 1-of-1 Cryptographic Provenance

Per Master Specification §4.3, a Forever Seal’s identity is derived from the sealing moment itself (When + Who + What + Alfa label). An ice fractal vein runs through the 3D holographic seal and holds a deterministic portion of those numbers—regenerable from the seal’s data and comparable against it—while flat offline verification (sha256sum / DLREC-3) stays the permissionless fallback (Law 4).

⚡ 1-CLICK LIVE HOLOGRAPHIC TAMPER TOGGLE (SAMPLE DL-20261028-000001):
INTEGRITY VERDICT (AXIS 1):
VERIFIED (Rule 9 · 786 chars · 1,938,816 px)
ORTHOGONAL TIME AXIS (AXIS 2):
ATTESTED (2026-10-28T00:28:33Z ±1s)
ARTIFACT SHA-256 (WHAT): d90ec0e4216d9a1e295963652125a1615f733bf7e02499c1405f7b1aac417c0f
DERIVED VEIN VECTOR (OD-1b DIGEST): VEIN-P1-7F3A-99C1-405F-7B1A-AC41-7C0F (24-Branch Fractal Lock)
WHO BINDING STATUS: UNBOUND (Stated plainly: carries What + When; no Tri-Signature sealed with sample)
★ 1-OF-1 CRYPTOGRAPHIC SCARCITY & PROVENANCE (P1-PROVENANCE-1)
  • Genesis Serial / Mint Coordinate: ALFA-P1-ORG-MESA-85206-000001-E3 (SERIAL #000001 — assigned once, never reused per §3.3.1; candidate entry pending log ratification per R-20).
  • 1-of-1 Generative Ice Fractal Vein: Grown deterministically from the Derived Seal Number (When + Who + What + Alfa label), making every sealed artifact visually and mathematically 1-of-1.
  • Law 3 Custody & Provenance Chain: Every endorsement or title transfer wraps the prior seal’s SHA-256 digest as a new human-signed event (Law 3: No silent change + Law 5: Every chain starts and ends with a human), giving contracts, IP assignments, escrow closings, and founding artifacts verifiable provenance without needing a third-party server (Law 4).
§5.7 // THE SEALED SAMPLE ARTIFACT

Fictional Wire-Transfer Authorization (DL-20261028-000001)

A one-page wire-transfer authorization (Copper Canyon Outfitters LLC → Desert Peak Logistics LLC, USD 48,500.00). Every name, company, bank, and amount is invented; the document is watermarked SAMPLE — FICTIONAL on its face and moves no money.

  • Record Format: DLREC-3 · Spec: DocLock 1.5
  • Artifact SHA-256: d90ec0e4216d9a1e295963652125a1615f733bf7e02499c1405f7b1aac417c0f
  • Character Count (DL12-CHAR-1): 786 characters (Unicode NFC, LF line endings)
  • Pixel Count (DL-RENDER-PDFJS-1): 1,938,816 pixels (1224 × 1584)
  • QR Trust Capsule (DLCAP-1): CAP-DL-20261028-000001-v1
  • Tri-Signature Binding: UNBOUND (carries What + When, not Who)
ACTUAL VERIFICATION RUN (2026-10-27 / 2026-10-28 UTC)

Observed 9-Rule Verdict Engine & Orthogonal Time Results

  • Original Document ($48,500.00): Verified (Rule 9) — SHA-256, character count (786), pixel count (1,938,816), and QR Trust Capsule all report MATCH.
  • Altered Copy ($48,900.00): Broken Seal (Rule 1) — exactly one character differs (the amount’s hundreds digit at index 438: 48,500 → 48,900). The character count still matches (786 — a same-length edit), and the SHA-256 (fe0106e1877b20ef4adb2e289ead3a5f53b01216e64a5beb8445457542459f90) catches it immediately.
  • Time Axis: ATTESTED (Orthogonal Axis) — live RFC 3161 tokens from FreeTSA (2026-10-28T00:28:32Z) and DigiCert (2026-10-28T00:28:33Z), traceable to UTC through attested sources, with stated uncertainty (±1 second), stored inside doclock-record.json and verifiable offline. OpenTimestamps submission: SUBMITTED-PENDING (submitted to calendar pool, never claimed as “anchored”).

Download the Complete Sample Proof Pack Files (Verify Offline via sha256sum)

Run sha256sum wire-authorization-SAMPLE-original.pdf in any terminal—with zero Protocol One code required—to confirm the exact 64-character digest (d90ec0e4216d9a1e295963652125a1615f733bf7e02499c1405f7b1aac417c0f).

{^} MASTER SPEC §5.9 // COMPLIMENTARY 1-DOCUMENT SAMPLE SEAL OFFER ($0 · NO OBLIGATION) LAW FIRMS · ESCROW / TITLE AGENCIES · FOUNDING BUSINESSES

Send One Redacted or Sample Document — Receive It Back Sealed with DocLock 1.5 + a Simple Forever Seal Proof Pack

Want to test DocLock 1.5 and CLK-ATTEST-1 on your own firm’s paperwork before committing to a pilot? Send one document (a redacted template, sample closing instruction sheet, or fictional testamentary instrument is expressly welcome) to our Standards Office. We will return your document sealed with DocLock 1.5 plus a complete, self-contained Simple Forever Seal Proof Pack (seal.pdf + DLREC-3 record with dual RFC 3161 tokens + DLCAP-1 QR Trust Capsule) that your team can verify 100% offline with zero software or account required.

§6.3 & §7 // HONEST LIMITS, PRINTED ON PURPOSE (ABSENCE & CLAIMS DISCIPLINE)

This pack is UNBOUND: no Tri-Signature event was sealed with the sample, so it carries What (DocLock 1.5) and When (CryptoLock CLK-ATTEST-1 attested time), not Who. “DocLock proves a document is unchanged, not that what it says is true.” Layers are tamper-evident: they show when something changed; they do not prevent changes or impersonation. Time attestation is traceable to UTC through attested sources, with stated uncertainty (±1s here; Roughtime cross-check not implemented in this build; CMS signature / TSA certificate chain verification is performed via external openssl ts -verify rather than in-engine); the OpenTimestamps submission is SUBMITTED-PENDING, not anchored.