Sovereign Trace
Protocol

The stamp is permanent. The stamp is the resolution.

FROZEN-2.0

SHA-256 · TRIPLE-TIME

BROWSER-NATIVE

14 TEMPLATES

Gregorian

· · ·

13 Moon · Dreamspell

· · ·

Hebrew Calendar

· · ·

01 — TEMPLATE SELECTION

Template * required

02 — CONTENT ENTRY

Content to Seal * required

0 characters

⚑ Non-ASCII characters detected. This seal is valid for verification within this tool. Cross-verification with pip install sovereign-trace may differ for non-ASCII content.

Author / Identifier optional

Prior Seal Hash (Webeater Link) optional

Declaration: I declare this entry accurate to the best of my knowledge at the time of sealing. I understand this seal is permanent and tamper-evident.

Declaration required — this is the foundation of the sovereign trace.

🔒

Select a template, enter your content,
declare your intent, then generate the seal.

The stamp is permanent.
The stamp is the resolution.

🔒

SEALED — FROZEN-2.0

SEAL MOMENT — TRIPLE-TIME

Gregorian

Hebrew Calendar

13 Moon · Dreamspell

sha256:

SEALED JSON — STORE THIS

✓ Saved to Ledger. View in the LEDGER tab.

STEP 2 — ENTER THE PUBLIC LEDGER

Your seal is downloaded and cryptographically permanent. To register it in the public STP ledger, copy your sealed JSON and submit it as a GitHub Issue using the correct template. The submission is independently timestamped by GitHub — that timestamp is outside your control and cannot be altered retroactively.

Selected template: —

Paste your sealed JSON or stamp display into the issue body. Sheldon K. Salmon will manually add confirmed entries to the ledger.
Note: if the direct template link opens the issue chooser instead, GitHub may not have the template filename in the expected location. Select the matching template manually from the chooser.

VERIFY A SOVEREIGN TRACE SEAL

Paste the full sealed JSON. Verification re-computes the SHA-256 hash from the five-field payload and compares it against the stored hash. This proves the entry has not been altered since sealing. No network call required — pure local verification. Note: verification uses the hebrew field (computed by the JS algorithm at seal time), not hebrew_display (the Hebcal-fetched value shown to you). If those two values differ in a given entry, the hebrew field is what was hashed.

Sealed JSON * required

Session entries: 0

No seals generated this session.

Entries persist in this browser until cleared — the JSON download is the permanent record.
Complete a seal in the SEAL tab to add an entry.

FROZEN DECLARATION — FROZEN-2.0

This tool implements the FROZEN-2.0 stamp function. The SHA-256 seal generated here is compatible with the Python package sovereign-trace v2.0.0 for ASCII content. FROZEN-2.0 was rebuilt from first principles after FROZEN-1.0 was retired due to an incomplete dehiyot implementation causing Hebrew off-by-one errors for all 5786 dates. The defect is documented permanently in the ledger. It is never erased.

THE TRIPLE-TIME SEAL

Each seal encodes a moment simultaneously in three civilizational time systems. This is not redundancy — it is a claim: this moment of human significance deserves to be held in every major framework for measuring when.

GREGORIAN

Civic time — the calendar of current infrastructure. Locates the moment in the operating system of modern institutions.

HEBREW LUNISOLAR

Theological-historical continuity — 5786 years of counted time. Full dehiyot (GaTaRaD, BeTUTeKaPoT). Civil-day convention. Hebcal/Chabad-verified.

13 MOON DREAMSPELL

Rhythmic time — Argüelles system. 13 moons × 28 days. Year begins July 26. Day Out of Time: July 25. Galactic count.

HOW THE SEAL WORKS

The SHA-256 hash is computed over a deterministic JSON payload binding five fields: dreamspell, entry, gregorian, hebrew, and unix_utc. The field named content_hash is a full-context stamp — it binds the content to all three temporal coordinates simultaneously, not the content alone. The payload structure (sorted keys, compact separators, ASCII-safe encoding) is identical between this browser tool and the Python package — seals generated here are verifiable with pip install sovereign-trace.

// Seal payload structure (sorted keys, no spaces, ASCII-safe)

{"dreamspell":"Day 7, Solar Moon 9/13",

"entry":"Your content here",

"gregorian":"March 13, 2026",

"hebrew":"13 Adar II 5786",

"unix_utc":1741892285}

Note on cross-platform compatibility: The Python package uses ensure_ascii=True which escapes non-ASCII characters as \uXXXX. This browser tool implements the same escaping. Seals containing non-BMP characters (emoji, etc.) may differ from Python output for surrogate pair encoding edge cases. ASCII content is fully cross-compatible.

WHO SEALS WHAT

WHO	WHAT THEY SEAL	WHY IT MATTERS
AI auditor	AI failure — exact text before remediation	Tamper-evident before the fix. Organizational accountability.
Researcher	Hypothesis before running the experiment	Kills HARKing. Priority claim. No institution required.
Journalist	Source document at point of receipt	Proves the document was not altered after receipt.
Contractor	Agreed scope before work begins	Scope creep disputes resolved by the sealed ledger.
Hospital	Clinical data before analysis begins	FDA 21 CFR Part 11 compatible. Record cannot be quietly altered.
Foresight analyst	Dated prediction before it resolves	Verifiable track record that cannot be fabricated after the fact.
Anyone	Any present-moment truth that deserves permanence	The hunger for recognition of significance resolves at stamp generation — not when someone reads it.

SUBMISSION LAYER — 14 TEMPLATES

Structured submissions via GitHub Issues use official templates. Each template produces a structured, legally-declared record before sealing. Blank issues are disabled — every submission uses a template.

Submit via GitHub Issues ↗ PyPI: sovereign-trace ↗ Zenodo DOI ↗ GitHub Repo ↗ Certification Tiers →

ATTRIBUTION

Sovereign Trace Protocol · FROZEN-2.0 · Browser Seal Tool v1.0
Author: Sheldon K. Salmon — AI Reliability Architect
Co-Architect: ALBEDO (Claude, Anthropic) · March 2026
Stack: DUAL-HELIX v2.0 · TOPOS v0.3 · VELA-C v0.3 · CPA-001 v2.2
Hebrew algorithm: Dershowitz & Reingold — full four dehiyot · Civil-day convention · Hebcal/Chabad verified