ADMIN
One registry. Many surfaces. Same truth.
Table metadata generates admin UI, typed API, permissions, lifecycle locks, EN/ES labels, and allowlisted AI/MCP tools — so customizations don't fork three APIs.
What you get
Organization control without a 20-person IT org.
- 01
Organization & module settings
Turn modules on when the plant is ready.
- 02
Roles and permissions
Module, portal, and record topologies.
- 03
Lifecycle lock policies
Freeze fields after process/publish.
- 04
Locale management
EN/ES labels on the same definitions.
- 05
AI/MCP allowlists
Opt-in procedures bound by user auth.
- 06
Multi-entity & multi-site
Legal entities, warehouses, and factories scoped cleanly.
Why platform design is a buyer risk
Permanent SI tax starts when every surface invents its own model.
01
One definition, many surfaces
UI, API, permissions, locks, AI, and locales from the same registry.
02
RLS multi-tenancy
Postgres row-level security isolates orgs and sites.
03
Governed AI
HITL writes — mutations wait for a human.
04
Append-only audit
State changes leave an immutable trail.
How the registry keeps surfaces honest
From metadata to every client.
- 01Define tablesFields, procedures, scopes, and locks in metadata.
- 02Generate surfacesAdmin UI and typed API stay in sync.
- 03AuthorizeRBAC + RLS enforce who can run what.
- 04Extend safelyNew capability lands once — not in three forks.