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.
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.
Per-unit matched-context support can be shown under the contract tolerances, with the registry’s disclosed contract-gap and data-quality caveats.
Under matched charge allocation, the audited sentence is a FREEZE_AS_NULL above a disclosed detection floor; below the floor remains unobserved.
The response sentence reads the unit-terminal composite only. It attributes nothing separately to the battery string versus inverter/control.



outputs/m5bat/m5bat_sentence_registry.yaml — canonical wording ledger.outputs/m5bat/m5bat_v4_build_manifest.json — build manifest and provenance.outputs/m5bat/nulls_v4/m5bat_v4_freeze_verdicts.json — response-face verdicts.outputs/m5bat/nulls_v2/m5bat_v2_bearer_readjudication.json — bearer-face re-adjudication.These build records are internal artifacts, available for inspection under a review authorisation; the underlying dataset is public (M5BAT project).