@eristack/ai-knowledge
backseat-then-backend
46 linesSource
Backseat-first ERP mockup (Horizon A) then derive Drizzle backend (Horizon B): document/cost-sheet/job-order products without stock/GL spine. Skill order, atomic writes, wall lists, qups lines — one canonical guide.
Backseat-first ERP, then derive backend
Stop. Load this skill once. Full guide: knowledge/backseat-then-backend.md. Not an ERP spine — no @eristack/feature-*, no procurement compose.
When to use
Job order, cost sheet, invoice, forwarding, service ERP mockup, "derive backend", Horizon A → B. Not warehouse GL, FIFO, procurement PO→GR unless explicitly scoped.
shell
pnpm dlx @tanstack/intent@latest load @eristack/ai-knowledge#backseat-then-backendHorizon A skill order
- @eristack/ai-knowledge#package-relationships when composing many packages
- backseat-then-backend (this)
- @eristack/backseat#backseat-core
- @eristack/qups#qups-line
- @eristack/money#money-amounts, #money-ledger
- @eristack/doc-number#doc-number-core
- @eristack/data-grid#data-grid-core
- @eristack/rbac#rbac-core, @eristack/abac#abac-core, @eristack/pbac#pbac-core
- @eristack/timestamp#timestamp-core, @eristack/epoch#epoch-core
Horizon B
Same HTTP paths — flip stores to Drizzle. Load @eristack/ai-knowledge#upgrading-eristack §3 for adapter matrix.
Do not default-recommend
stock-movement, valuations, financial-ledger, ERP spine recipes — add only when product needs inventory/accounting.