Skip to content
Almathal Handbook

ADR-0023: CRUD Admin Tool as MVP Archetype #2

Accepted

Date: 2026-06-10

Context

A single Archetype doesn’t validate the platform’s generality. The second Archetype should exercise different parts of the architecture and provide simpler verification — confirming the platform works on stable, well-understood territory.

Decision

MVP Archetype #2 is an internal CRUD admin tool (Java backend + React frontend). It generates:

  • Spring Boot backend via JHipster
  • PostgreSQL persistence with Liquibase migrations
  • JWT-based authentication with RBAC
  • React frontend with shadcn/ui components, generated list and form views per entity
  • Containerized deployment via docker-compose
  • Basic observability (Prometheus metrics endpoint)

This Archetype follows MVP Archetype #1 (RAG chatbot — ADR-0022) immediately, ideally within the same MVP release.

Rationale

  • Mature scaffolders (JHipster) handle most of the work, so this Archetype is faster to ship.
  • Verification is straightforward: does CRUD work, does auth work, does deploy work.
  • Provides a sales-demo asset for enterprise prospects skeptical of the AI-first first Archetype.
  • Exercises a different language slice (mostly Java + TS, minimal Python) — proving Composer’s flexibility.
  • Same Adapters and Modules (Auth Module, PostgreSQL Adapter, React stack) get exercised across two Archetypes — validating reuse.

Consequences

  • JHipster integration is a key dependency for the Composer.
  • The “internal admin tool” market overlaps with Retool’s space; positioning differentiates on trust and provenance.
  • The Auth Module’s design is exercised by both MVP Archetypes — gets validated early.
  • Customers can self-serve admin tools without writing code; demo strength.

References