Connect a data source
The Huawei FusionSolar flow, plant binding, and fetch outcomes.
Connect and bind a plant
The provider flow uses server-managed credentials. Test the connection, choose a compatible mapping template, and bind the provider station code to the organization plant.
Keep passwords, tokens, and sensitive response content out of public documentation. Provider access and UCYield data access are separate scopes.
Fetch monthly data
Authorized users can trigger a fetch or configure a schedule. The worker fetches the source, maps metrics, normalizes values, and creates records; the current fetch flow supports automatic off-chain commit.
An empty response or a month without values must not become zero. Inspect fetch outcomes to distinguish missing data, authentication problems, rate limits, and schema errors.
Integration boundaries
Native Provider API, full source slicing/replay, and Huawei OAuth have separate specifications and plans. Publish them as usable features only after verifying their endpoints and interface flows.
This review inspected JSON upload and Huawei API-account fetch as the core paths. It does not certify a live provider connection or environment credentials.
Sources reviewed in the monorepo
Based on source code; live availability is stated separately.
apps/api/src/modules/shadow-ledger/api/shadow-ledger.controller.tsapps/api/src/modules/shadow-ledger/application/fetch-executor.service.tsdocs/shadow-ledger/08-dual-ingestion-runbook.mddocs/adr/ADR-0035-canonical-ingestion-formats-and-provider-contract.md
