Skip to content

ADR-0003: Provide A Metadata-Driven Runtime CRUD API

Status

Accepted

Context

The platform should allow new entity types to become usable without writing bespoke CRUD code for every concept.

Decision

Implement a generic runtime CRUD API that uses the published entity model to validate entity creation, property updates, tag assignments, relationship changes, and queries.

Custom APIs will still be used for security-sensitive or workflow-heavy features.

Consequences

Positive:

  • Faster application development.
  • Consistent API behavior.
  • Entity types can be introduced without endpoint duplication.

Trade-offs:

  • Runtime validation must be robust.
  • Generic CRUD must not bypass sensitive workflow services such as Vault or remote connectivity.