From a public trace to a better evidence request
The pack does not infer internal asset state from public records. It identifies a bounded inconsistency or unusual public role, then specifies which owner-held evidence could resolve it.
A question rate is not a problem rate
In the private demonstration pack, 69 high-confidence storage units were checked across seven public lenses. Fifty-nine were publicly coherent or explained, three remained lens-insufficient, and seven retained an open question. Those seven were folded into two anonymous operator cohorts and two anonymous single-unit signatures before requesting owner evidence.
No further claim was created from the public lenses.
A reason to request evidence, not a count of problem assets.
Freeze the observation window
Record source URLs, retrieval timestamps, raw files, hashes, revisions, and each lens's publication delay.
Build the public duty profile
Separate accepted actions, metering, declared capability, physical intention, service scope, outage disclosure, registry, and context.
Test source correction
Ask which lens corrects which possible misread. A missing BOALF trace, for example, must be checked against metering and non-BM service scope.
State the unresolved tension
Describe only the public records that do not align. Do not supply a cause that the records do not reveal.
Request the minimum resolving evidence
Request only the BMS, PCS, thermal, availability, maintenance, optimiser, contract, or commissioning records needed to test the unresolved question.
Example request logic
| Public trigger | Owner evidence requested | Question being tested |
|---|---|---|
| High accepted-action cadence with frequent direction switching | PCS event logs, BMS throughput, thermal traces, maintenance and availability records | Whether the public cadence corresponds to a materially different internal operating profile. |
| Declared capability differs from metered activity | Availability declarations, outage scope, operating restrictions, commissioning or maintenance evidence | Whether the difference is operational, commercial, temporal, or a public-data identity effect. |
| Public registry and physical traces disagree | Energisation, commissioning, project identity, meter mapping, and registry-update evidence | Whether the registry is stale, the unit is commissioning, or the public identity match is wrong. |
The same public residual creates different review questions
What changed since the risk was first described?
Public duty, capability, absence, restoration, and correlated exposure questions.
Do public operating traces still fit model assumptions?
Duty intensity, availability assumptions, restoration time, and residual-value evidence questions.
Can identity, operation, capability, and service scope be reconciled?
A source-by-source evidence checklist before technical conclusions.
Which public traces require direct clarification?
Bounded reconciliation questions before relying on a public interpretation.
Discuss an authorised review
Send the asset scope and review purpose. LFR will confirm public-source availability, identity confidence, data maturity, and the claim boundary before work begins.
info@lfrfrequency.com →