Disclaimer
LFR observation surfaces are designed to make relational structure, cadence, concentration, and continuity candidates visible. They are not instructions, predictions, regulated advice, or professional certification.
Last updated: 11 June 2026
Observation only
Unless a separate written engagement says otherwise, outputs on this website are observational demonstrations. They may show candidate patterns such as cadence persistence, support-role concentration, path narrowing, derating type, boundary-context exposure, or continuation support. These are not final determinations.
Energy, grid, BESS, and infrastructure
- Public-data grid and BESS pages do not assess grid stability, system reliability, asset safety, fault causation, delivery quality, or compliance.
- BM Unit and accepted-action analyses read public balancing-market records. They do not diagnose internal asset condition, degradation, warranty liability, or fatigue.
- Demonstrated-energy, derating, cadence, revenue-at-risk, and support-role outputs are candidate observations that should be reviewed with internal BMS, PCS, SCADA, thermal, metered, maintenance, contractual, and warranty records before operational use.
- No page should be treated as a dispatch instruction, control strategy, safety alert, engineering design, grid-code compliance opinion, or operational approval.
Finance and markets
- Finance pages are not forecasts, trading signals, personal recommendations, investment research, or financial promotions.
- LFR Resonance Systems LTD is not authorised or regulated by the Financial Conduct Authority.
- Nothing on this website is investment advice, credit advice, underwriting advice, insurance advice, legal advice, tax advice, or accounting advice.
Third-party assets and identified units
Some observation surfaces and example reports reference publicly identifiable assets, BM Units, or operating organisations using public identifiers from official sources. Any flag, status, score, ranking, or candidate marker attached to an identified unit describes a pattern in public records under a stated method. It is not a statement about the conduct, competence, solvency, or internal condition of any operator, owner, optimiser, or counterparty, and it is not an allegation of fault or wrongdoing.
Patterns in public data can have benign explanations, including planned maintenance, augmentation or repowering works, commissioning ramp-up, metering conventions, strategy changes, or reporting effects that public records do not distinguish.
Corrections and context. If you are an asset owner, operator, or optimiser and believe an observation relating to your asset rests on a data error, or omits material public context, contact info@lfrfrequency.com. We will review promptly and correct, annotate, or remove the observation where appropriate.
Not credit ratings or regulated assessments
Watchlist statuses, flags, screening scores, and exposure classes are observation-prioritisation outputs. They are not credit ratings within the meaning of the UK Credit Rating Agencies Regulation, not credit assessments, not probability-of-default models, not insurance ratings, and not regulated benchmarks. They must not be used as the sole basis for any credit, investment, underwriting, or contractual decision.
Backtested and screening statistics
Where pages or reports quote hit rates, precision, recall, lift, lead times, or other backtested statistics, these are historical screening statistics computed on limited samples over specific past windows with stated method versions. Sample sizes may be small, confidence intervals wide, and threshold choices method-dependent. Historical screening performance is not a promise of future performance and may not repeat under different market, weather, fleet, or reporting conditions.
Public data limitations
Public data can be delayed, revised, incomplete, unavailable, or affected by reporting conventions. Source terms and schemas can change. LFR derived observations may change when source data, code, labels, windows, or methods are updated.
Client and internal-data work
Where a customer provides non-public data, the scope, permitted use, confidentiality, retention, delivery format, liability, insurance requirements, and claim boundaries should be agreed in writing before work begins. Website examples do not create those terms.
Use of outputs
You are responsible for decisions made using any website content or report output. Before acting on an observation, seek appropriate professional, technical, financial, legal, insurance, or engineering advice for your circumstances.