generated: '2026-07-27' method: derived source: review.yml note: >- Hydro One publishes no scope reference. This artifact records the NAESB ESPI function-block scope syntax observed on a live Green Button Connect My Data authorization request against Hydro One's authorization surface (recorded in review.yml during the 2026-07-27 review of a publicly indexed instance of https://www.hydroone.com/green-button-cmd-home). The individual function-block identifiers are defined by the NAESB REQ.21 ESPI standard, not by Hydro One, and Hydro One publishes no mapping of block id to meaning — so no per-block descriptions are asserted here. Values are recorded verbatim, unexpanded. scheme: green-button-cmd-oauth2 scope_model: naesb-espi-function-blocks syntax: 'FB=;historyLength=' standard: name: NAESB REQ.21 Energy Services Provider Interface (ESPI) version_required_in_ontario: '3.3' reference: https://www.greenbuttonalliance.org/ developer_guide: https://greenbuttonalliance.github.io/OpenESPI-GreenButton-API-Documentation/ observed_scope: raw: 'FB=1_3_4_5_13_15_16_31_37_39_51_53_54_55_56_57_58_59_60_64_65;historyLength=32148000' function_blocks: - '1' - '3' - '4' - '5' - '13' - '15' - '16' - '31' - '37' - '39' - '51' - '53' - '54' - '55' - '56' - '57' - '58' - '59' - '60' - '64' - '65' history_length_seconds: 32148000 observed_on: '2026-07-27' observed_at: https://www.hydroone.com/green-button-cmd-home confidence: medium confidence_note: >- Single observation of one onboarded third party's authorization request. It evidences the scope syntax Hydro One accepts; it is not a published list of the scopes Hydro One grants, and other vendors may be issued different function-block sets. scopes: [] scopes_note: >- No enumerated, documented scope list exists on any Hydro One surface. The function-block set a vendor receives is negotiated during onboarding. related: - authentication/hydro-one-authentication.yml - conformance/hydro-one-conformance.yml