ADR-0002: Use a Universal Entity Platform

Date: 2026-06-06

Status: Accepted

Context

Eco Manager needs to model customers, sites, buildings, assets, credentials, tags, groups, and future concepts such as rooms or network zones.

Creating a custom table and custom CRUD workflow for every concept would slow development and make customization difficult.

The product needs to be flexible for developers and configurable for trusted users without becoming an uncontrolled low-code system.

Decision

Eco Manager will use a Universal Entity Platform.

Important concepts will be represented as entities with data-driven entity types, hierarchy, property groups, tags, groups, relationships, templates, and audit events.

Domain-specific modules may still exist for behavior-heavy features such as Vault, remote connectivity, audit, and external integrations.

Consequences

Positive

• New object types can be introduced with less schema churn.
• Developer-assisted dynamic forms and views become possible.
• Customers, sites, buildings, rooms, and assets can share infrastructure.
• Trusted-user customization becomes easier through Admin Studio.
• The system can grow into a richer technical operations platform.

Negative

• The metadata model must be carefully designed.
• Validation and permissions become more important.
• The system must avoid becoming too abstract for users to understand.