A library system for shared hardware work.

Aether gives teams a controlled way to turn local hardware experiments into reusable Components, Capsules, and package commits without pretending the canvas is live multiplayer.

The story is deliberate publishing, not live multiplayer.

Team collaboration in Aether works like staged source control for physical assets: draft locally, commit intentionally, review the change, and adopt it only when the project is ready.

Draft

Build Components, Capsules, dependencies, and hardware defaults locally before anything becomes shared.

Commit

Capture reusable asset changes as explicit Component, Capsule, or library package states.

Review

Compare refs, dependencies, ports, and exposed parameters before a project adopts an update.

Adopt

Choose when to update, keep a local copy, stay read-only, or continue with the current snapshot.

Move between local work and the shared library.

The page follows Aether AI's rhythm: one focused mode switch, one product image, and a clear explanation beside it.

Aether local reusable node workflow

Work locally until the asset is ready.

Editors can experiment with Components, Capsules, custom libraries, and hardware defaults before anything becomes shared.

Aether team cloud library workflow

Publish deliberate package states.

Library commits carry structure, categories, dependencies, stable refs, and update choices as an explicit team package.

Every team control exists to keep adoption explicit.

Owner

Manage members, publish library structure, and publish Component or Capsule commits.

Editor

Create and publish reusable assets while keeping membership and package ownership controlled.

Viewer

Inspect shared libraries and use assets without writing back to the team package.

Package commits

Publish membership, ordering, categories, dependencies, and stable refs as one deliberate library state.

Draft protection

A local uncommitted asset is never silently replaced by a remote version.

Detached snapshots

Projects can keep loading a Capsule even if the original library commit is gone.

Team examples that match the real product model

Use cases now stay in the same prompt-card language as Aether AI.

Publish a classroom-ready sensor kit with locked defaults and editable project-level parameters.

Share a Capsule that wraps gesture input, LED output, and media triggers into one explainable interaction block.

Review a component update before every project using that component adopts a new pin or dependency.

Keep a viewer's library state read-only while still letting them inspect component structure and code.

Resolve a remote update after a local draft has diverged from the published component version.

Bundle `.aetherlib` packages with Components, Capsules, custom libraries, and history references.

Publish a classroom-ready sensor kit with locked defaults and editable project-level parameters.

Share a Capsule that wraps gesture input, LED output, and media triggers into one explainable interaction block.

Review a component update before every project using that component adopts a new pin or dependency.

Keep a viewer's library state read-only while still letting them inspect component structure and code.

Resolve a remote update after a local draft has diverged from the published component version.

Bundle `.aetherlib` packages with Components, Capsules, custom libraries, and history references.