Interconnection Evidence Event Feed

Synthetic/redacted sample. This is a vendor-neutral, source-admitted domain event feed for an existing finance system, not a borrowing-base engine or system of record.

V2: thin core + extensions

The universal core carries event/project identity, effective date, instrument and documented balance transition when observed, effective provider-rule identity, source-digest provenance, source-admission status, exception/control state and idempotency. Provider- or facility-specific facts stay in typed extensions.

Refundability is not forced into the core

The refundability extension can be source_supported, facility_document_required, or unresolved. A missing facility-specific fact remains missing rather than becoming a favorable collateral assumption.

Current-source admission

A production event should emit only when the authoritative provider source is admitted as current. Known-stale or freshness-unresolved source states block emission. Synthetic examples self-identify as SYNTHETIC.

What the buyer's existing system keeps

Storage, approvals, audit/user history, alerts, dashboards, borrower document workflow, borrowing-base calculations, eligibility, advance rates, and all legal/credit decisions.

Provider-minimal first shadow

Start with the one or two provider stacks actually represented in live material events. Six-provider coverage is not a default pilot feature; adapter/source-maintenance cost must be justified by buyer value or shared recurring demand.

Download synthetic machine-readable feed · See the source-admission control