Forward evidence · Sealed before markets move

The Sealed Journal.

Every XAU/USD research call this desk issues is frozen into a document, hashed with SHA-256, and written to our tamper-evident audit ledger before its outcome can be known. When the horizon closes, the verdict is published against the original frozen text — hit or miss, exactly as sealed.

Why it is empty — on purpose.
The standard starts today. No past call is retroactively scored, because a record that cannot be audited from birth is marketing, not evidence. First verdicts unlock as each horizon completes.

Mechanics

How a call is sealed.

The workflow is deliberately mechanical. Human discretion ends the moment the seal is written; the ledger and the calendar do the rest.

Step 01Draft

A thesis is written with its direction, horizon (10–90 sessions) and invalidation level fixed in advance. No parameters may be edited after this point.

Step 02Seal

The frozen document is hashed (SHA-256) and the hash is published to the tamper-evident audit ledger with a timestamp.

Step 03Wait

The call stands untouched while the market does what it does. Anyone can recompute the hash at any time and confirm nothing changed.

Step 04Verdict

At horizon close the outcome is published against the frozen text — resolved or missed — and the rolling statistics update automatically.

Scoreboard

Rolling 90-session record.

0Sealed verdicts to date

n = 0Sample in evaluation window

SHA-256Seal primitive · ledger-anchored

LiveFirst seals begin today

Reading an empty scoreboard correctly: we show the count of verdicts (n) beside every statistic we will ever publish. Where n = 0, no claim is made. We will never display a hit-rate without its sample size, and we will never restate a horizon after the fact. When verdicts arrive, this page — and only this page — is where the numbers live.

Ledger

Open seals.

Calls currently inside their evaluation window. Each hash can be recomputed against the sealed document and matched to its ledger entry.

Sealed	Call class	Thesis (frozen)	Horizon	Seal hash	Status
—	—	No seals yet. The first forward calls are being drafted and sealed today.	—	—	Awaiting first seal

Resolved calls move to the audit ledger archive with their full frozen text and verdict — both preserved exactly as issued.

Standard

What gets sealed — and how it is judged.

Call class	Frozen at seal	Horizon	Verdict rule
Directional thesis	Direction, horizon, invalidation level	10–90 sessions	Resolved at horizon close against the frozen text; invalidated early if the level trades.
Level test	Exact level and touch/hold definition	Event-driven	Resolved on first defined touch, or expiry if untouched.
Scenario probability	Scenario set with explicit weights	Fixed calendar date	Graded against the realized distribution on the declared date.

Governance

The rules that cannot bend.

01No backfilling. A call that was not sealed before its outcome is never added, scored, or referenced.

02No edits. A sealed call is immutable; corrections appear only as new, separately sealed entries.

03No selective disclosure. Every verdict — hit or miss — publishes to the same page at the same time.

Independently verifiable today: the tamper-evident audit ledger records every internal committee decision, and the system status page shows live component health. The methodology explains how calls are formed before any of them is sealed.