ADR-0003: Build Metadata-Assisted UI, Not a Low-Code Builder

Status

Accepted

Context

The platform contains metadata such as property groups, property definitions, tag groups, templates, and entity types. This metadata can help render forms, detail sections, filters, and tables.

However, the product should not become a generic drag-and-drop low-code website builder in its initial architecture.

Decision

Use metadata to assist developer-built UI.

Developers still own:

• application routes,
• feature-level workflows,
• complex forms,
• business logic,
• integration behavior,
• custom UX,
• authorization-aware flows.

Metadata may drive:

• property sections,
• field rendering,
• tag selectors,
• table columns,
• filter options,
• template-backed forms.

Consequences

Positive

• Developers avoid repetitive CRUD code.
• UI stays consistent.
• Product remains maintainable.
• Future user-configurable logic remains possible.

Negative

• Some screens still require explicit development.
• Metadata model must not promise behavior it cannot safely enforce.

Trade-off

The architecture is future-proof without prematurely becoming a generic low-code platform.