Public grid records are incomplete. They are not imaginary.
Each public-record channel carries a limited relation: instruction, declaration, metering, contract, disclosure, registry, frequency, or system context. We keep those limits visible, then test where channels support one another, diverge, remain not comparable, or leave a question unresolved.
Different records answer different questions.
The system card, the anonymous fleet mirror and the fixed monthly editions each keep their own population, window, definitions and limits.
Grid Continuity Status Card
Read the dated card's measures, sources and stated limits.
Open the 24 September card →Storage Fleet Duty Mirror
Compare three public-record distributions for one defined BM-unit group. No named units and no asset conclusion.
Open the 24 September mirror →GB Grid Relations
Read the October edition, including its sources and stated limits.
Open October 2026 →GB Grid Relations
Open the fixed September edition to read its measures, sources and stated limits.
Open September 2026 →GB Grid Relations
Open the fixed August edition to read its measures, sources and stated limits.
Open August 2026 →How LFR tests the path
Preserve what arrived. Test the bridge. Declare the transformation. Qualify the claim.
Read the method →How a public-record channel may support a claim
Relation and source capability, retrieval maturity, frozen transformation, recomputation, and claim admission.
Read the grid method →Terms that carry their limits
Each definition says what the term can establish and what it must not be used to imply.
Open the lexicon →When an open question justifies an evidence request
Check comparability, public context, decision relevance, and the minimum owner-held record needed to test what remains unresolved.
See the workflow →Accepted-Action Cadence
How accepted-action frequency, duration, record-sequence switching, and instructed-trajectory energy separation become bounded evidence questions.
Read the cadence method →What the public record cannot see
Not represented, source-insufficient, and unobserved remain different outcomes.
Open boundaries →Questions before conclusions
What is a public-record duty profile?
The time-structured external footprint visible across admitted public-record relations.
Evidence Request Admission
Not every public gap justifies asking an owner to open internal records.
Bring a question the record cannot answer
Start with what happened, the records, the claim, where the relation becomes unclear, and the consequence; authorisation comes later.
Is a public-duty review the right fit?
Coverage, naming, blind spots, available outputs, authorisation, and pilot scope are set out separately from the evidence index.
A small, defensible vocabulary
The lexicon defines what each term means, what data can support it, and what it must not be used to imply.