eedenOSpreviewECOSYSTEM ATLAS · PREVIEW
ENGINEERING · DEVELOPMENT · EXPLORATION · NATURE

One ecosystem.
Clearly connected.

Explore the EDEN platform, its software, hardware, specialist applications and shared capabilities — with definitions and status grounded in project canon.

Canon-led catalogueUnknown is not a pass.Local-first by design.
Recovery catalogue: source-backedThe catalogue is built from the 9 October 2026 recovery set. Each product page separates recovered definitions and features from implementation, testing and release evidence.
—catalogue entries
—top-level categories
Evidence-ledfeature and status labels
THE SYSTEM MODEL

Small core. Rich composition.

Each layer has a clear responsibility. Apps retain their domain ownership; integrations connect capabilities without becoming their owners.

EDENEngineering · Development · Exploration · Nature
AppDev → edenOSReusable platform and system layer
APPLICATION → EDEN / DOMAIN API → PLATFORM CORE → PLATFORM ADAPTER → DRIVER → HARDWARE
BROWSE THE ECOSYSTEM

Find a product, app, platform or capability.

Open a dedicated product page for its definition, capabilities, hierarchy, source trail and evidence status.

Loading catalogue…Choose an entry to open its dedicated page →
CANON & CONFIDENCE

Clarity over false certainty.

The catalogue separates what is defined from what is built, tested and released. A polished page is not proof that a feature exists.

01

Canon first

Use explicit owner decisions and authoritative project definitions. Do not silently reopen closed decisions.

02

Evidence is a separate field

Defined, implemented, tested, verified and released are distinct states. One does not imply the next.

03

Unknown stays visible

Unverified hardware details, integrations, versions and implementation claims are labelled rather than guessed.

04

Preserve boundaries

Apps own domain intent; shared capabilities own common contracts; providers and adapters connect external systems.