This repository documents the current, implemented behavior of the Helianthus eBUS ecosystem:
helianthus-ebusgo(transport + protocol + data types)helianthus-ebusreg(registry + schema + vendor providers)helianthus-ebusgateway(runtime + GraphQL/MCP + projection browser/Portal surfaces)
Implementation-neutral references for the eBUS wire protocol and data types live under protocols/ and types/. Helianthus-specific architecture, APIs, and deployment notes live elsewhere in the tree.
Gateway HTTP entrypoints are split by role: /ui is the read-only projection browser, while /portal is the Portal shell and /portal/api/v1 is its versioned API surface.
- Developer path: architecture/overview.md → api/graphql.md → api/mcp.md → api/portal.md → development/contributing.md
- Operator path: deployment/full-stack.md → development/end-to-end-smoke.md → development/smoke-test.md
- Researcher path: protocols/ebus-services/ebus-overview.md → types/overview.md → architecture/vaillant.md
- Tier 1 (merge-blocking): changes to architecture, API surface, or runtime behavior must update docs in the same PR; see Trigger Matrix.
- Tier 2 (non-blocking): internal-only refactors with no external behavior change may skip doc edits, but must include a short rationale in the PR description; see Trigger Matrix.
- Author flow: classify the change, update required docs, and complete the PR Author Checklist.
- Reviewer flow: verify classification and documentation coverage using the Mandatory Gate Flow.
- Canonical policy: development/contributing.md#documentation-gate-doc-gate
Run:
./scripts/ci_local.shThis repository contains documentation under two licenses:
-
protocols/andtypes/– CC0-1.0 (public domain). These describe the eBUS wire protocol and data type formats as reverse-engineered from the bus. Anyone can use, modify, or republish this material without restriction. -
Everything else – AGPL-3.0. This documents the Helianthus implementation specifically. See the root LICENSE file for terms.