ADR-0006: Add Admin Studio As A Separate App
Date: 2026-06-08
Status: Accepted
Context
Eco Manager's Universal Entity Platform is powerful enough to support entity types, entities, hierarchy, properties, tags, groups, templates, relationships, and saved views.
Developers and trusted super users need a safe way to inspect and manage this model without directly editing the database or building one-off admin screens for every metadata concept.
The normal engineer-facing frontend should remain focused on operational workflows, not platform administration.
Decision
Eco Manager will include a separate apps/admin frontend application called Admin Studio.
Admin Studio will provide a Notion/Obsidian-style super-user workspace for CRUD and configuration across the Universal Entity Platform.
Admin Studio will communicate only through backend APIs and shared contracts. It will not access the database directly.
Consequences
Positive
- Keeps admin/super-user workflows separate from normal engineer workflows.
- Gives developers and implementation users a powerful configuration surface.
- Reduces need for one-off metadata CRUD pages.
- Makes the Universal Entity Platform visible and manageable.
- Supports future advanced features such as bulk operations and configuration previews.
Negative
- Adds another frontend app to maintain.
- Requires careful permission design.
- Dangerous operations need strong guardrails and audit logging.
Trade-offs
Admin Studio increases product surface area, but it unlocks the practical power of the entity platform and improves developer velocity.