A real implementation model behind the visual graph.

Aether lets developers define the hardware contract once: pins, ports, modes, UI controls, dependencies, code blocks, Capsules, and generated Arduino output.

The story is a compile-ready contract.

Developer content now follows the Aether AI page structure: staged cards first, then one focused mode switch that shows how reusable definitions become upload-ready output.

Define

Write the component contract once: identity, pins, ports, modes, UI controls, dependencies, and metadata.

Resolve

Turn graph nodes, Capsule overrides, variables, and board mappings into concrete Arduino inputs.

Generate

Create includes, globals, setup, loop, readSense, readAct, branch logic, and helper functions.

Upload

Compile, install required libraries, flash the selected board, and keep progress visible in the workspace.

Two surfaces, one implementation contract.

Developers can work at the component level or follow the generated sketch path, while Aether keeps the same source of truth underneath.

Aether component contract editor

Everything reusable lives with the component.

Hardware requirements, UI templates, mode code blocks, helper functions, and dependency metadata stay together, so a node can be reused without losing implementation detail.

Aether generated Arduino upload flow

The graph remains visible all the way to upload.

Aether resolves ports, expands Capsules, generates the sketch, installs libraries, compiles with Arduino CLI, and reports upload progress inside the same workflow.

Each implementation hook exists because generated hardware work can fail.

Component definitions

Identity, hardware rules, code blocks, interface controls, dependencies, and profile metadata stay in one reusable contract.

Capsule expansion

Reusable graph modules unfold with project overrides, exposed ports, parameters, and recursion checks before generation.

Dependency planning

Arduino Index libraries, built-in support code, and custom source files travel with the component that needs them.

Validation first

Missing references, broken bindings, incompatible ports, and mode-specific gaps are surfaced before upload work begins.

Mode code blocks

Only mode-specific differences need to be written while shared setup and helpers stay on the base component.

AI-ready context

Profiles describe usage, wiring, and output data so future AI plans can recommend the component accurately.

Developer work Aether can keep structured

Start with a reusable hardware idea, then keep the contract, code, dependencies, and update path inspectable.

Create a distance sensor component with port rules, output data, and a preview control.

Package a custom RGB LED Act component with mode-specific code and Arduino dependencies.

Expand a Capsule into a project while preserving exposed parameters and hardware bindings.

Resolve a missing library before generating the final setup and loop code.

Compare a component commit before adopting changed pins in an existing project.

Build an AI profile so future graph plans understand the component's wiring context.

Create a distance sensor component with port rules, output data, and a preview control.

Package a custom RGB LED Act component with mode-specific code and Arduino dependencies.

Expand a Capsule into a project while preserving exposed parameters and hardware bindings.

Resolve a missing library before generating the final setup and loop code.

Compare a component commit before adopting changed pins in an existing project.

Build an AI profile so future graph plans understand the component's wiring context.