← Interconnection Collateral Monitor
Synthetic · redacted demonstration

See the event-feed shape before sharing a real document.

These files use invented project identifiers, balances and document locators. The current primary proof is a factual-only source-linked handoff designed to map into an existing system; legacy credit/collateral decision exports are not current commercial deliverables. No customer, borrower, lender or prospect information is included.

Interconnection Factual Evidence Review

Start with the buyer-facing review: scope, exception queue, changed-item re-performance, supporting evidence, and the explicit outside-scope boundary.

Open synthetic verification review Download review JSON

Factual-only handoff table

Compact factual rows for an existing finance/project system: stable IDs, source-supported balance, source/rule lineage, evidence gaps and exception codes. No lender eligibility, haircut or borrowing-base decision is included.

Download factual-only CSV

Canonical factual handoff record

Machine-readable provenance behind a row: rule/source IDs, source hashes, instrument evidence locator/hash, missing-evidence state, factual exception codes and explicit scope boundary.

Download factual-only JSON

Refresh diff

See how a documented security event changes the factual balance while an unresolved facility-specific term stays fail-closed. The diff preserves before/after values, the event evidence locator and digest, changed fields, and the exception that prevents a favorable inference.

Download synthetic refresh diff

What a buyer should compare

A useful pilot is measured against the existing workpaper, not against a demo impression. Compare reviewer time per facility, refresh turnaround, material exceptions found, false favorable assumptions prevented, independent reproducibility from cited evidence, and manual re-keying into the existing lender system.

Commercial gate: if the current internal process is faster, equally reproducible and cheaper, the product should fail the comparison rather than force a deployment.

Seven-gate zero-data worksheet

Use this blank worksheet for a first process conversation before any document or project data is requested. It tests category binding, authoritative factual control, recurrence, downstream re-performance, bounded factual scope, a possible future buyer-controlled data path, and whether measurement is worth doing.

No buyer data is needed to fill the first pass. Unknown answers stay unknown; the worksheet does not create pilot readiness, value, price or permission to request documents.

Download seven-gate zero-data worksheet

Pilot comparison worksheet

Use the blank worksheet to capture baseline versus Monitor-assisted process metrics before judging a paid operating verification shadow. Start with non-confidential process metrics only; do not place project, borrower, lender, agreement, security or personal data in this public template.

Download pilot comparison worksheet

Example exception

project_id: SYNTH-DEMO-002
provider_stack: ERCOT-ONCOR-2026
source_supported_balance: $1,800,000
provider_fact: project_document_required
facility_terms: missing_for_demo
result: FAIL CLOSED
factual_exception: MISSING_FACILITY_SPECIFIC_REFUNDABILITY_TERMS
credit_or_eligibility_decision: NOT_PRODUCED

Do not send confidential project data through the public site. A workflow comparison starts with this synthetic/redacted output and a conversation about your existing process.

Request a workflow comparison

Event Transition Ledger

See the synthetic event-first evidence chain beneath the annex, including before/after balances, transition provenance and fail-closed facility-term exceptions.

Open synthetic event ledger · Blank event-cadence worksheet

Downstream disposition measurement

Temporal / as-of boundary

This synthetic demonstration does not prove currentness. A real bounded delivery must pass DW: dynamic current-state values require an observation at, or authoritative validity through, the locked as-of cutoff; otherwise the workpaper emits an explicit unknown/exception or historical fact.

Economic-object identity boundary

This synthetic demonstration does not prove target identity continuity. Real facility-level facts require DX binding across financed project, provider/project identifier, facility membership, capital instrument, and material ownership/entity changes.

Borrower funding-event pack

See the same synthetic evidence reframed for a borrower-side draw/addition/refresh workflow. It fails closed when facility-specific terms are missing.

Open the synthetic funding-event evidence pack

Interconnection Evidence Annex

Supporting reviewer view over the event chain; no longer the primary commercial unit.

View the synthetic annex

Dual-control annex

See the prepared annex and independent re-performance receipt as separate control states on one synthetic evidence chain.

Open dual-control sample

Control economics

See why borrower preparation and lender control do not automatically create two value claims.

Open the synthetic control-economics model

Interconnection Evidence Event Feed

Current commercial proof: vendor-neutral, source-bound interconnection transitions designed for the finance system you already use—not another dashboard or borrowing-base engine.

Open the synthetic integration feed

Source-admission control

Production-like provider events block when the authoritative source is known stale or freshness is unresolved.

See the source-admission control

Coverage readiness

See what market-core coverage means, where provider extensions begin, and why New York is not currently claimed as production-ready.

Read coverage readiness

Source-Control Reperformance Receipt v7

For sophisticated finance teams, the event feed is evidence substrate—not another portfolio workflow. A bounded five-procedure receipt reports source admission, envelope/provenance integrity, balance-chain continuity, facility-document completeness and preserved exceptions while existing systems retain borrowing-base calculations, dashboards, approvals and credit decisions. It is not an audit, attestation, assurance engagement or AUP.

View synthetic source-control receipt

Source Integrity Control

See how canonical current-source observation blocks stale admission, preserves historical receipts, and separates upstream revision detection from billable customer control work.

View synthetic source-integrity control

Control integrity regression evidence

See the synthetic corruption corpus that blocked receipt v2 and gates receipt v7.

Open control-integrity evidence

Procedure applicability

Receipt v7 distinguishes required controls from structurally inapplicable checks and measures reviewer effort by applicable procedure/event.

View procedure scope

Pilot evidence modes

Separate a narrow technical-control proof from the multi-event workflow evidence required before claiming recurring economics.

See pilot evidence modes

Retained public-source integrity

Receipt v7 requires hardened canonical public sources to be frozen and byte-verified against the observed asset digest; this is reproducibility evidence, not source-origin authentication.

See public-source integrity

Pilot unit economics

Historical price/scope stress tests are retained, but DE requires 3–5 completed same-family events for serviceability measurement; 1–2 events are falsification only, with no live financing effect and no established price.

See the internal scope gate

Process-scope admission

Market overlap is not enough. A production event must match the specific interconnection process for which its source was admitted. For example, current MISO DPP coverage does not imply MISO ERAS coverage.

Earned process expansion

See why ERCOT Batch Zero ranks first for expansion demand but remains discovery-only until a purchasable control gap is observed.

View expansion gate

Private evidence control

Receipt v7 separates exact-byte verification from document-content review and origin authentication; matching bytes alone cannot satisfy SCR-04.

See private-evidence control

Pre-reperformance anchor

Receipt v7 can detect later whole-envelope replacement only when the original buyer-controlled manifest is retained outside the re-performance service.

See anchor/control-separation boundary

Use the buyer's existing repository

Receipt v7 exports a small anchor package for retention in the buyer's governed VDR/DMS. The product does not need to become another document vault.

See anchor-retention compatibility

Control-owner route

Where a formal Independent Engineer or Lender Technical Adviser owns draw-support review, use the v7 controls upstream as a borrower Source-Control Preflight Workpaper or as a bounded adviser input—not a parallel independent reviewer.

View synthetic borrower preflight

Economic proof gate

Downstream acceptance does not become savings without a documented baseline. Price exists only if measured buyer-value ceiling overlaps the measured delivery-margin floor.

See the counterfactual and price gate

Retrospective economics experiment

Economic proof may start with 1–2 completed same-family events for cheap falsification, but productization measurement requires 3–5 completed events from one provider/process/form family. No live financing intervention is allowed in the first economics test.

See the staged experiment gate