M5BAT / Duty context observer

A grid-duty battery system read through context support and terminal response.

This lens connects battery observation to public-grid cadence work: duty can be measured without turning it into an internal asset-health conclusion. The April 2023 window supports matched-context and terminal composite response readings, with several explicit unobserved-context boundaries.

Claim boundary. April 2023 only. Terminal composite means battery string plus inverter/control path. Observation layer only: not SOH, RUL, safety, fault, remaining-life, warranty, underwriting, investment, or degradation evidence.
What can be shown

Duty exposure is an evidence request entry point, not a verdict.

Context support

Matched duty contexts recur

Per-unit matched-context support can be shown under the contract tolerances, with the registry’s disclosed contract-gap and data-quality caveats.

Bearer face

No stable LMO most-stressed bearer resolved

Under matched charge allocation, the audited sentence is a FREEZE_AS_NULL above a disclosed detection floor; below the floor remains unobserved.

Response face

Terminal composite response

The response sentence reads the unit-terminal composite only. It attributes nothing separately to the battery string versus inverter/control.

Figures

Existing source figures.

M5BAT P trace figure
Event-locked terminal composite response figure from the v4 build.
M5BAT rank sweep figure
Rank sweep figure; ordering language remains limited by the audited verdict table.
M5BAT injection recovery figure
Injection/recovery figure used to show the demonstrated floor, not internal degradation.
Evidence path

Files behind this page.

These build records are internal artifacts, available for inspection under a review authorisation; the underlying dataset is public (M5BAT project).