Tier 0 · The Spine · Working Prototype

CONDUIT · Safe Gateway

A curated, mission-specific registry of the data feeds and APIs the global program is cleared to use — every source vetted, jurisdiction-scoped, and gated so nothing sensitive crosses a border it can't legally cross.

0Sources

0Vetted & open

0Gated / restricted

0Connected

✓

Rights confirmation on file. Written owner rights confirmed — the hard IP stop is lifted and the registry is cleared to run. Restricted feeds (child-safety hash lists, export-controlled OSINT) still gate individually on legal MOU and export screening below.

All sources

Cleared to connect Pending vetting Restricted — clearance required Connected

@bbg/ledger — safe-gateway · source connections · SHA-256 chain

Prototype. Connection logic is live — each connect is SHA-256-hashed and chained. Gating shown is the real policy: restricted feeds (child-safety hash lists, export-controlled OSINT) require a signed legal MOU and, for OSINT/crypto, export-control screening before any cross-border use; pending sources await source-vetting sign-off. Production wires each source through the shared @bbg ledger, holds provider keys in a server-side vault (never in the client), and records every grant signed with the gateway key. Product & provider names clear through McAuliffe; data-use & license terms through Olson.