Public BOALF records can show when accepted BM actions are recorded, their duration and instructed direction, and whether accepted-action frequency separates from instructed-trajectory energy. These are properties of the public dispatch record. They may reflect both participation and the granularity or rules of the operational instrument.
Each observable remains inside the BOALF record and its frozen assembly rules. None is an internal asset interpretation.
Counts distinct accepted actions per unit and observation day under a frozen assembly rule. It can distinguish occasional from repeated BM-visible participation without establishing a persistent physical state.
Records accepted-action duration and, only where a consuming output names a frozen threshold, the frequency of short accepted actions. These are dispatch-record properties, not direct measurements of internal switching, cycling, or physical stress.
The current frozen rule counts opposite signs in consecutive directed accepted actions ordered by start time; zero-movement actions neither create nor break a switch. This is record-sequence switching, not a count of continuous physical reversals. A gap-sensitive successor would require a new method version.
Accepted-action count and instructed-trajectory energy answer different public-record questions and use different units. Instructed-trajectory energy is derived from the published accepted-action trajectory; it is not settlement-metered energy and does not establish delivered physical energy.
A cadence observation does not automatically justify a broad owner-data request. The decision context must first make the relation relevant; then request only the minimum record needed to test the specific question.
| Public-record question | Minimum next check | What remains outside public data |
|---|---|---|
| High accepted-action frequency with low instructed-trajectory energy in a defined window | Only where relevant to the decision, identify the minimum owner-held record needed to test the specific cadence/volume question. | Internal control allocation, physical cycling, thermal effect, degradation, or warranty consequence. |
| Frequent direction changes under the frozen record-order rule | Where authorised, compare the owner-held dispatch or control record with the public accepted-action sequence under a confirmed identity and time mapping. | Internal control allocation, sub-settlement response, protection events, or physical cycling. |
| BM-visible trace is quiet in the scoped window | First compare with the unit's own public history and, where admitted, the same-window regional field. Then cross-check B1610, EAC, MEL/MIL, REMIT and PN/FPN only where identity and time bridges permit. | Whether the asset was commercially inactive, physically unavailable, operating outside BM, or absent because public coverage was insufficient. |
| Declared / metered divergence after identity and time alignment | Request the minimum owner-held record needed to test declaration scope, availability state, commissioning state, or market route. | The operational reason or physical condition without owner evidence. |
For the current machine-rendered and authorised public status, see the latest Grid Continuity Status Card. That card carries only the claims admitted to its own dated release; this page does not extend them.