Canon first
Use explicit owner decisions and authoritative project definitions. Do not silently reopen closed decisions.
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.
Inventory coverage: partialSource reconciliation is in progress. Listed projects and features are not a complete or release-certified inventory.
—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
BIFROSTConnect & keepHEIMDALLOrganize & understandCONDUCTOROrchestrate actionSpecialist appsBrowse domain applications
APPLICATION → EDEN / DOMAIN API → PLATFORM CORE → PLATFORM ADAPTER → DRIVER → HARDWARE
BROWSE THE ECOSYSTEM
Find a system, product or capability.
Open any entry for its definition, hierarchy, feature inventory, dependencies and evidence status.
Loading catalogue…Choose an entry to open its dedicated page →
No entries match these filters. Try another term or clear the filters.
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.
Evidence is a separate field
Defined, implemented, tested, verified and released are distinct states. One does not imply the next.
Unknown stays visible
Unverified hardware details, integrations, versions and implementation claims are labelled rather than guessed.
Preserve boundaries
Apps own domain intent; shared capabilities own common contracts; providers and adapters connect external systems.