Method before interpretation
Every public record is produced by a particular physical, market, settlement, reporting, or institutional process. The record is real; what it can support depends on the relation that process actually records.
Preserve before interpreting
Archive the source payload before analytical transformation, together with its URL, retrieval time, requested window, response status, file hash and source licence.
Register the relation and source capability
For every channel, record the relation it can carry: what it refers to, which event and retrieved version it belongs to, its time grain, retrieval and revision behaviour, sign convention where relevant, coverage, blind spots, permitted comparisons and claim ceiling.
Freeze definitions
Specify windows, identity mappings, unit and sign conventions, normalisation, thresholds, and derived fields before reading the result.
Derive within the source boundary
Calculate only what the frozen source relation supports. A derived value does not inherit access to internal condition, causality or physical detail that the record did not contain.
Test cross-channel coherence and retrieval maturity
Test whether another public-record channel supports, limits or leaves the reading unresolved; whether identity and time bridges are strong enough; and whether retrieval maturity is sufficient for the stated evidence date. A later retrieval is not, by itself, a certified settlement revision.
Admit the claim before it enters a report
A reproducible calculation is not yet a reportable claim. Each admitted claim travels with its source, subject and time boundary, method version, recompute path, unresolved gaps, and what the record does not establish.
Core public-record channels
| Channel | Relation it may carry | What it does not establish |
|---|---|---|
| BOALF | An accepted BM action record: timing, instructed direction and level, and visible cadence. | All physical operation, service delivery, availability, or contracted activity outside BM acceptances. |
| B1610 | A settlement-period signed net quantity record against a B1610 bmUnit identifier. | Internal physical allocation, sub-settlement behaviour, service delivery, or asset condition. The record is lagged, revision-prone and temporally coarse. |
| MEL / MIL | A participant declaration of maximum export and import limits. | Actual availability, physical condition, or the cause of a declared limit. |
| PN / FPN | A participant-declared intended position. | Physical delivery, actual capability, or availability. |
| EAC / service records | A public same-name contract or service-scope record under an explicit matching rule. | All contracts, dispatch, delivery, revenue, or performance. |
| REMIT | A qualifying public disclosure found under the stated query and time window. | That no outage or issue existed when no matching disclosure was found. |
| REPD / registries | A public project status, capacity or geography record under a stated extract date and match rule. | Current operation, an authoritative asset-to-BMU identity, or physical condition. |
Source links, licences, and attribution are maintained on the Data Sources page.
From method to review
Public source record → relation and source-capability contract → identity and time alignment → frozen transformation → recomputable observation → cross-channel coherence under a separate relation contract, or an unresolved gap → claim-boundary gate → scoped report or evidence request.
Calculation is not claim admission, and page layout does not grant authority. The same path governs any scoped system, regional, portfolio or single-asset output. A released output states which relations and claims actually passed; unresolved parts remain questions or, where authorised, scoped evidence requests.
See how an evidence request is built Bring a question the record cannot answer