Institutional data room

Production inventory, sealed episodes, live credibility, and claim ceiling — indexed for CIO, quant, and counsel. Start with what's shipping; finish at the boundary.

Validation is product. Thermodynamic recipe stays under contract.

Walk the 2008 backtestData Room & x402 audit — machine-verifiable attestation

Data Room

At a glance

At a glance

Review the same artifacts we use in IC diligence — production inventory first, then proof, then claim boundaries.

  1. 01

    Production first

    Coverage inventory and live gate — what ships today.

  2. 02

    Pick your role

    CIO, quant, or counsel — start-here paths link each artifact.

  3. 03

    Proof and process

    Sealed episodes, room index, and validation architecture.

  4. 04

    Read the boundaries

    Disclosure table, IC checklist, FAQ, and claim ceiling.

This room is

  • Sealed backtests on GFC, Turkey, and Dotcom
  • Documented validation process and source discipline
  • Live monthly NII trail with flat-line checks
  • Published observation inventory, claim ceiling, and machine probe

This room is not

  • A substitute for legal, credit, or cyber due diligence
  • Full scoring formula, rubric weights, or prompts
  • Prediction, allocation, or hedge advice
  • Proof that live data retroactively validates 2008

Engine

V5-locked (1.19.0)

Crisis: 80–90 on the 0–100 NII scale; Collapse ≥90

Sources

26

19 live pipelines · 29 configured

Coverage

1,000

of 1,274 registered series with live data

Observations

333,023

stored indicator observations in production

Platform

360

Production HTTP handlers on one deploy — v1, portal, cron, operator consoles

Live credibility gate

Live monthly layer meets internal Wave-1 gate — safe for allocator diligence alongside sealed backtests.

Live gate · Open

Sep 2026

43.3/100

NII · 0–100 NII scale

Aug 2026

42.1/100

NII · 0–100 NII scale

Jul 2026

37.4/100

NII · 0–100 NII scale

Jun 2026

42.4/100

NII · 0–100 NII scale

  • Single canonical monthly pathpass

    Published NII is computeRII / V5-locked monthly_scores. Legacy dual-run engine_delta retired 2026-07-12.

  • No unexplained flat quarterpass

    No three-month identical NII plateau in recent trail.

  • Clean monthly cyclespass

    7 month-over-month moves since last flat streak (need 2 for Wave-1 live gate).

  • Published trail depthpass

    8 months in trail (latest Sep 2026).

Full live credibility gate →

Machine probe

Same room. One curl.

Unauthenticated attestation of the inventory and live gate on this page — plus claim ceiling and a SHA-256 pin. No key. No recipe. Entity scores stay on the keyed commercial API.

Schema · data-room.v1

GET /api/public/data-room
curl -sS "https://www.entropyindex.com/api/public/data-room"

Lexicon

Watch
Earliest Crisis signal on the instrument. Brief the room — not an allocate clock.
Act
Dual Crisis — system in Crisis and gap threshold met. Capital posture clock.
NII
Net Insecurity Index on the public 0–100 NII scale. Engine stores 0–5 internally.

Start here

Pick the job, not the whole room.

Three review paths — CIO, quant, and counsel. Each step links to the artifact.

Room index

Every artifact. One methodology.

Proof, process, live production, commercial entry, and technical surface — all on the same sealed instrument.

Sealed proof

Clocks on known breaks.

Deterministic replay under frozen physics. Watch = earliest Crisis. Act = dual Crisis. Team diligence PDF per episode.

Process as product

Validation is a product surface, not a back-office secret.

Sophisticated buyers stress-test process before they stress-test thermodynamics. This is how we score, freeze, attest, and bound claims.

  • 01

    Sealed V5-locked physics

    Buyer value · Same engine object in backtest and live watch — no retro-fit after the event.

    Frozen amp / κ / C under V5-locked (1.19.0). Watch and Act clocks are product objects, not post-hoc labels.

  • 02

    Point-in-time source discipline

    Buyer value · No future information in the month being scored.

    Multi-source, deterministic, source-traceable · vintage-honest ledgers per episode · lag policy documented per construct.

  • 03

    Triple-blind domain extraction

    Buyer value · LLM-assisted domains reconciled before the engine sees a single score.

    3 blind draws per period when models disagree; early exit when range < 0.5 on 0–5 scale. Opt-out via INDEX_TRIPLE_BLIND=0 for audits.

  • 04

    Immutable prediction ledger

    Buyer value · Dated divergence claims are facts, not screenshots.

    Published rows under immutability policy · daily chain anchor · Pulse calls timestamp third-party attestation.

  • 05

    Watch vs Act dual clocks

    Buyer value · Early signal and capital posture are different product clocks on purpose.

    Watch = earliest Crisis of any fashion. Act = dual Crisis (I_sys Crisis ∧ gap threshold). Dotcom explicitly discloses Watch ≠ Act.

  • 06

    Claim ceiling enforcement

    Buyer value · Public language cannot outrun Travis-signed packaging doctrine.

    Sealed case studies, mandate chips, and GTM copy pull from single canonical sources — no invented live clocks.

Triple-blind reconciliation ships in production extracts. Ledger policy documented in research records.

Production cadence

  • Monthly score publish

    Global NII + domain panels under V5-locked (1.19.0). Trail visible on live gate.

  • Source lag policy

    Documented per construct — vintage-honest ledgers in sealed episodes; live path uses as-of discipline on ingest.

  • Watch / Act transitions

    Instrument transitions written on phase threshold — same clock objects in backtest and desk.

  • Forward attestation

    Published divergence rows under immutability policy — daily chain anchor when ledger earns an instance.

Forward record

One dated divergence beats three logos.

Until the live record earns it, the forward slot stays blank — Desk Pilot is the instrument that produces a ledger-backed instance.

Divergence one-pager →

Disclosure boundary

Validation ships. Recipe stays protected.

We document how we score, freeze, and bound claims. Thermodynamic transforms remain trade secret under contract.

Disclosed in this roomProtected under contract
Validation process, PIT policy, sealed backtest outcomes, live gate checksFull NII formula, coefficient tuning, rubric weights, scoring prompts
Source inventory counts, series coverage, documented missing series, evidence tiersIngest recipes, panel fusion logic, proprietary normalizations
Published NII/FAI, Watch/Act clocks, sealed case PDFs, monthly trailRaw domain scores without contract, internal diagnostic runs
Divergence qualification rules, ledger immutability policy, blank slot honestyUnpublished forward calls until ledger row exists

IC review checklist

Packet-ready items — each links to the source artifact.

Diligence FAQ

Is this a prediction engine?
No. Structured early-warning and decision-support — Watch surfaces gap, Act requires dual Crisis. We sell measurement discipline, not forecast theater.
Does AI write the score?
One sealed formula on the live Index and every backtest — formulaic result, not narrative. Scoring is deterministic under sealed physics. Zero AI touching the engine: AI may structure evidence and read the face; it does not write the number.
Does live monthly data retroactively prove the GFC backtest?
No. Sealed episodes use frozen V5-locked physics and point-in-time sources. Live monthly NII is a separate production layer with its own credibility gate.
When is Watch enough vs Act?
Watch = earliest Crisis of any fashion (brief the room). Act = dual Crisis (I_sys Crisis ∧ gap threshold). Dotcom explicitly documents Watch ≠ Act.
What happens if monthly NII flat-lines?
Three identical consecutive prints trigger review — analytical note or RCA required before allocator diligence. Visible on the live credibility gate.
Why are some series missing?
We publish the observation inventory. Missing inputs reduce domain coverage — they are listed, not silently imputed. ACLED and several OECD constructs remain documented backlog.
Can we check production health without a call?
Yes. GET /api/public/data-room returns the same inventory and live-gate attestation shown in this room — no key. Entity scores and methodology stay under contract on /developers.
Can our quant team reproduce scores?
Under contract: entity API, score history, and domain panels. Methodology recipe remains trade secret — same as any institutional data vendor with proprietary transforms. The public probe attests inventory and credibility only.
Is Desk Pilot a discount World Index?
No. Bounded evaluation — weekly side-by-side memo, scoped watchlist, max two quarters. Renew at firm license or exit.

Alternatives

What we are not.

Three objects an IC already owns — priced fear, country ratings, narrative geo. The rest of the compare hub sits under them.

Fort Knox

Security posture — machine-audited, publicly verifiable.

Every deploy runs a Fort Knox audit that fails closed. Private keys never touch the production server. Key semantics are split so no single secret grants both payment bypass and monitoring access. The audit result is a public endpoint — verify it yourself.

Loading audit...

Security doctrine

  • Private keys never on production server

    Payer, minter, anchor, and ownership keys are local-only. Fort Knox machine audit fails closed if any appear on Vercel.

  • Split key semantics

    Edge proxy, monitoring, and attestation signing each use a separate secret. Compromise of one does not grant payment bypass.

  • Cash-settlement integrity

    Only on-chain tx_hash with settlement_status=success counts as revenue. Empty-tx facilitator calls are rejected.

  • SSRF-hardened webhook registration

    Webhook subscribers must prove wallet ownership via a recent cash-confirmed settle. URLs are validated against IP, metadata, and RFC1918 patterns.

  • Durable rate limiting

    Console login and public form routes use Supabase-backed rate limits that survive Vercel isolate rotation.

  • Row-level security on all operator tables

    Supabase anon and authenticated roles are revoked from every operator table. Service role only.

  • Timing-safe auth on every internal header

    All secret comparisons use constant-time equality. Session tokens are time-bucketed with HMAC-SHA256.

  • No trade-secret leakage to client bundle

    TVG cutoffs, engine thresholds, and internal key names never ship to the browser.

Live machine audit

Loading...

Verify it yourself

The Fort Knox audit runs on every request to the public endpoint. No login required.

curl -s https://www.entropyindex.com/api/v1/x402/fort-knox \ | python3 -m json.tool

Returns pass/fail for each check, total score, and a summary. No secrets, key values, or internal env names are exposed.

Claim ceiling

What we refuse to sell.

Public language cannot outrun signed packaging doctrine — read this before any pilot or firm license.

  • We do not claim live monthly scores retroactively prove pre-2008 positioning buckets.
  • We do not treat Watch (gap-alone) as Act / allocate.
  • We do not sell prediction — structured early-warning and decision-support only.
  • We do not hide validation process — it ships as product documentation.
  • We do not publish methodology recipe — validation yes, trade secret no.

Next step

Review the room. Then scope the desk.

Desk Pilot for bounded side-by-side evaluation — firm license when the IC packet clears.