Platform status and roadmap
Status is reported separately for implemented, experimental, and planned capabilities. Product names do not upgrade technical readiness.
AI-native end-user experience
Section titled “AI-native end-user experience”Implemented foundations: agent-readable Markdown and indexes, an Agent Skill, runtime capability discovery, OpenAPI, governed application commands, AetherEdge MCP tools/resources, deterministic local rules, audit evidence, and the public contract/conformance repositories.
Experimental or partial: AetherCloud’s transport-neutral MCP application interface, desired/reported/applied deployment, governed jobs, CloudLink, telemetry persistence, and Edge/Cloud development harnesses.
Planned: the household or site semantic context, conversational end-user agent, typed intent/proposal/policy contracts, intent-to-automation compiler, historical simulation, generated confirmation experience, temporary behavior expiry, outcome evaluation, and continuous governed adaptation. No current release should present these as a complete product.
AetherEdge
Section titled “AetherEdge”Implemented: six-service runtime, SHM live-state authority, embedded local
operation, governed commands, aether CLI, aether-edge-sdk, Pack v1, MCP and
OpenAPI foundations, and signed v0.5.0 source/runtime/CLI artifacts.
Experimental: CloudLink MQTT v1 edge foundation, application-ACK-driven
spool, AetherContracts alpha.3 consumption, real-Broker development evidence,
and the read-only Home Assistant edge bridge foundation with bounded
registry/state synchronization, opt-in aether-io source composition, and
explicit full resynchronization. The default-off Home Assistant Integration
Control slice adds one session-bound, signed, locally authorized
device.power.set.v1 capability with durable idempotency, audit, and receipts;
provider acceptance deliberately leaves physical outcome unknown.
Planned or gated: production CloudLink key lifecycle, signed ACK, complete joint conformance, legacy cutover, packaged Home Assistant composition, public integration queries, production projection/query composition, production OAuth and secret lifecycle, broader governed device capabilities/commands, production key rotation/revocation, and remaining application-boundary migration.
CloudLink alpha.4 production blocker: the current session-accepted
message is unsigned and carries neither challenge_id nor client_nonce.
AetherEdge consumes it only after a challenge on the current connected
transport, aborts acceptance on disconnect, and requires the persisted session
epoch to increase strictly. Those local checks cannot cryptographically exclude
a delayed acceptance from another handshake on the same connection. The public
wire contract must bind an authenticated acceptance to the complete current
handshake transcript before this path can be described as production
authentication.
AetherCloud
Section titled “AetherCloud”Implemented foundations: modular-monolith domain/application slices, capability-driven providers, Plan-only OpenTofu, Gateway enrollment, partial CloudLink/telemetry persistence, artifact/deployment/job foundations, audit and integration slices, observability, and a transport-neutral MCP interface.
Experimental or partial: MQTT codec and ingress, local/AWS IoT harnesses, PostgreSQL accepted-telemetry ACK outbox, and finite audit interfaces.
Planned or gated: production identity, complete CloudLink durability and mapping, production composition and workers, public job/deployment delivery, hardened outbound integrations, and a connectable MCP server.
AetherContracts
Section titled “AetherContracts”Implemented, experimental: alpha.3 specifications, closed Schemas, fixtures, TCK, digest-pinned consumer verification, and four fixture bindings.
Planned or gated: production authentication key lifecycle, signed durable ACK, complete production codecs, and a production CloudLink cutover release.
Platform documentation
Section titled “Platform documentation”Implemented in this migration: shared product overview, unified navigation, deployment topologies, user journeys, end-to-end alpha integration task, compatibility matrix, status page, and AetherIot to AetherEdge migration guide.
Planned: automated cross-repository version aggregation, release-channel status feeds, and a future GitHub organization when an appropriate address is available.