backofficeui

Overview ¶

Package backofficeui embeds the generic back-office SPA and serves it from the engine binary under /app (ENG-38, the first-10-minutes path). It is the PRODUCT face of the backoffice-spec pattern: a CRUD admin UI generated ENTIRELY from /openapi.json at runtime — zero resource-specific screens, zero hardcoded domain knowledge — so ONE prebuilt bundle serves every schema this engine will ever boot. In the minute-3 of a first contact, /app is the screen that feels like *your* app: your resources, your fields, your RBAC.

The SPA is no-build vanilla JS (ES modules), so unlike /admin and /editor there is no "assets not built" state: the source files ARE the bundle, committed and always embedded. It is the same pattern verified in examples/backoffice-guide/ (the teaching copy consumers adapt into their own SPA — that copy stays deliberately minimal and self-contained; this one may grow product polish). Everything either copy knows comes from the contract: x-appximo-relation/references, x-appximo-file(+policy), x-appximo-initial/transitions, x-appximo-virtual-resources.

Serving model (mirrors pkg/adminui): /app redirects to /app/ so the SPA's RELATIVE asset references resolve under the mount; /app/ serves the shell; /app/<file> serves the module files. All static, JWT-skipped (the shell loads before any token exists — the API calls it makes carry the Bearer), off the CRUD hot path.