← Back to register

Data provenance

Where the figures on this register come from, and where they do not.

Status of the figures

The BEDROCK register is currently a seeded preview. Asset identifiers, sites, nameplate figures, delivered figures, signal values and evidence references are illustrative records constructed to exercise the deriver. They are not sourced from a live operator feed, and the page does not present them as one.

What is production, and what you are actually looking at when a badge appears, is the ruleset:

• The evidence tier hierarchy — paperwork, operator statement, external observation.
• The rule that an operator's own adverse report is capped at watch and cannot assert impairment.
• The rule that an external-only adverse signal resolves to disputed, never to a final negative.
• The freshness windows per class — 30 days for solar and storage, 45 for interconnect, 90 for water rights.
• The weakest-binds composite: score = round(min(signals) × 100), with no averaging and no smoothing.
• The classifier version stamped on every derived output.

Nothing is stored as a status

No record in the register carries a status or badge field. Badge, reason, binding document, evidence age and staleness are computed from the evidence bundle on each read and then discarded. This is deliberate: a stored status keeps being served after the document beneath it expires, and a register that does that is publishing a claim while appearing to publish a fact.

Seeded negative fixtures

Three of the six assets on the register are constructed to resolve negative, and are labelled as such on the pipeline section:

• WTR-0061 — a fresh operator-tier shortfall notice. Must resolve watch. If it resolves impaired, the operator-testimony ceiling has broken.
• STO-0143 — a paperwork-tier capacity certificate below the covenant floor. Must resolve impaired. If it resolves watch, paperwork-tier authority has broken.
• SOL-0129 — an entirely positive bundle whose freshest document is 47 days old against a 30-day window. Must resolve disputed. If it resolves performing, the freshness guard has broken.

A register on which everything reads performing demonstrates nothing about whether its deriver ran. These fixtures exist so the failure paths are observable from the outside.

What is not built

Operator ingestion adapters (SCADA, dispatch logs, BMS exports) are in progress. Paperwork custody with content hashing is not started, which means a cited reference on this preview cannot yet be checked against a stored file. A published dispute procedure is not started. These are listed openly in the state-of-build section rather than implied to exist.

Not an offer

Nothing on this site is investment advice, a solicitation, or an offer to sell securities or any instrument. $BDRK parameters shown are design parameters of the register's funding mechanism.