Skip to content
The first Verdict Network

Before a position, a verifiable verdict.

TrueAsset is building the contract that turns market, risk and structural evidence into explicit permission. Its target requires versioning, replay and verification outside our interface; today it remains SHADOW.

Authority: ignum-nodePublic contract v1State: SHADOW / calibration
A category defined by contract
Governance required

Schema and doctrine must be versioned before issuance.

Replay required

The same inputs must resolve to the same verdict.

Proof required

Evidence must survive outside the UI and provider.

01 · The distinction

A signal describes. A verdict commits.

Price, narrative and momentum may command attention. They do not grant risk. A Verdict Network binds evidence, vetoes, budget, invalidators and proof into one decision unit.

It is not

Another scored signal.

A ranking, social alert or unaudited prediction may inform. It is not a verdict.

It is

A decision under contract.

A typed output declaring what risk is permitted, why, under which version, and what invalidates it.

02 · The path

Evidence in. Proof out.

01 / INGEST

Evidence

Market, derivatives, on-chain, structure and auxiliary sources.

02 / CUTOFF

Frame

An as-of and knowledge cutoff freeze what could be known.

03 / GOVERN

Gates

Freshness, coverage, integrity, crowding and doctrine can veto.

04 / DECIDE

Verdict

Permission, budget, cap, reasons and invalidators.

05 / OUTPUT

Proof

Canonical preimage, hash, signature and ledger reference when active.

03 · Category contract

Five states. No implied permission.

States order how much risk may be considered. Radar prioritizes research; by itself it can never promote SIZE or CONVICTION.

V/00PERMISSION

BLOCKED

Evidence or a veto prevents risk from being opened.

V/01PERMISSION

WATCH_ONLY

There is a signal, but no position permission yet.

V/02PERMISSION

PROBE_ALLOWED

Only a bounded probe with explicit invalidators.

V/03PERMISSION

SIZE_ALLOWED

Risk sized within the declared budget and caps.

V/04PERMISSION

CONVICTION_ALLOWED

Highest doctrinal permission; never an automatic order.

Integrity rule

Missing evidence, stale data or failed verification may only preserve or reduce permission. Never increase it.

04 · Method

Three layers that cannot substitute for one another.

01 / EVIDENCE

What we know

Each source retains identity, timestamp, freshness and domain. Confluence never erases provenance.

  • Explicit knowledge cutoff
  • Visible coverage and degradation
  • Non-interchangeable sources
02 / PERMISSION

What we allow

Long and short resolve separately. Vetoes, budget and caps prevail over score.

  • Radar ≠ tactical permission
  • Fail-closed by default
  • Mandatory invalidators
03 / PROOF

What we can prove

The target contract binds schema, doctrine, canonical preimage, hash and signature for independent replay.

  • Versioned before issuance
  • Queryable hash
  • Append-only ledger target
05 · Proof state

SHADOW means not promoted yet.

The Public Ledger is active and retains signed alerts with outcomes, misses included. Category contract v1 remains a separate SHADOW surface: legacy records are not presented as conformant until replay, schema and promotion gates pass.

Deterministic replayREQUIRED

Promotion target: 100 frozen-preimage replays; not claimed as achieved.

Hard-case suiteREQUIRED

Promotion target: 28 governed edge cases; not claimed as achieved.

Signature and anchoringSHADOW

The public demo is deliberately NOT_VERIFIED and NOT_ANCHORED.

Forward trackingPENDING

Historical cases are not mixed with a prospective track record.

06 · Public surface

We do not ask you to trust the interface.

The contract and an explicitly unverified fixture are open to inspection. SHADOW is evidence, not decoration.

JSON Schema

Structural contract

Fields, types, enums and minimum verdict v1 relationships.

Open spec ↗
Demo fixture

SHADOW example

A research object with no valid signature or production anchor.

Open demo ↗
Doctrine

Public rules

Permission, degradation and state-promotion invariants.

Open doctrine ↗
07 · Sovereignty

Authority stays on the node.

Delivery and compute are separate layers. Cloudflare publishes; ignum-node retains execution and state authority.

Authority

ignum-node

Next.js runtime and TrueAsset services remain under first-party operational control.

Interface

Public Ledger v0.1

Signed records and public outcomes today; promotion to category contract v1 requires explicit gates.

Delivery

Cloudflare Tunnel

Edge transport. It does not decide, replace the ledger or become source of truth.

Governed access

Fewer signals. More accountability per decision.

No public tariff is currently in force. Admission is reserved for operators and teams able to evaluate the contract and its limits.