feat: renumber lib reference into 4-pillar anatomy
Renumber the 15 reference docs into pillar groups (recipe -> anatomy): - 01 Build Recipe (entry), 02 Composition Root - domains: 10 Layering Rules - contract: 20 Spec-First Routing, 21 CRUD Template, 22 Auth Integration - interfaces/infra: 30 Infra Adapters - UI: 40 UI: Auto-Rendered Admin & Custom Pages (new; @aetoskia packages, client template, x- catalog via react-openapi MCP module) - pipelines: 50 Pipeline Scaffold, 51 Worker & Progress, 52 Human-in-the-Loop - delivery/meta: 90 Drone Pipelines, 91 Versioning & Changelog, 92 Genericity Matrix, 93 Library Registry, 94 Repository Inventory MCP module names are unchanged (NN_ prefix stripped); all cross-references (wiki, templates, hooks, registry) updated; lib index rewritten pillar-first; build recipe bootstraps the client template. Bundle + HTML sites regenerated.
This commit is contained in:
@@ -3,26 +3,56 @@
|
||||
The reference half of the Standards description: the enforceable rules,
|
||||
patterns, and the internal library catalog that agents consult while coding.
|
||||
|
||||
- **Build Recipe** — the ordered, agentic checklist for a new app.
|
||||
The reference is organized as an **anatomy** — one entry checklist and four
|
||||
pillars describing what an application is made of, plus delivery/meta pages
|
||||
and an optional pipelines layer.
|
||||
|
||||
## Anatomy
|
||||
|
||||
- **Build Recipe** — the ordered, agentic checklist for a new app; the entry
|
||||
point that walks the whole anatomy.
|
||||
|
||||
## Pillar 1 — Domains
|
||||
|
||||
- **Layering Rules** — the strict request → domain → repository layering and
|
||||
the rules that enforce it.
|
||||
|
||||
## Pillar 2 — OpenAPI Spec (the contract)
|
||||
|
||||
- **Composition Root** — a single composition point wiring the whole app.
|
||||
- **Spec-First Routing** — the OpenAPI contract as the routing source of truth.
|
||||
- **CRUD Template** — the standardized generic resource endpoint scaffold.
|
||||
- **Auth Integration** — consuming the shared auth-server service (spec-driven,
|
||||
no auth code).
|
||||
|
||||
## Pillar 3 — Interfaces & Infra
|
||||
|
||||
- **Infra Adapters** — how infrastructure connects without leaking into domain.
|
||||
|
||||
## Pillar 4 — UI
|
||||
|
||||
- **UI: Auto-Rendered Admin & Custom Pages** — the `@aetoskia/react-openapi`
|
||||
admin rendered from the spec's x- extensions, and `@aetoskia/react-auth`
|
||||
for auth pages; the client template scaffold.
|
||||
|
||||
## Pipelines (optional layer)
|
||||
|
||||
- **Pipeline Scaffold** — the deterministic pipeline skeleton for multi-stage
|
||||
jobs.
|
||||
- **Worker & Progress** — queued work, progress reporting, and visibility.
|
||||
- **Human-in-the-Loop** — guardrails and approvals inside automations.
|
||||
- **Infra Adapters** — how infrastructure connects without leaking into domain.
|
||||
- **Drone Pipelines** — the two CI shapes: a PyPI package or a Docker deployment.
|
||||
- **Versioning & Changelog** — SemVer, the tag↔version contract, and the release
|
||||
changelog.
|
||||
|
||||
## Delivery & Meta
|
||||
|
||||
- **Drone Pipelines** — the two CI shapes: a PyPI/npm package or a Docker
|
||||
deployment.
|
||||
- **Versioning & Changelog** — SemVer, the tag↔version contract, and the
|
||||
release changelog.
|
||||
- **Repository Inventory** — every covered repo, its type, version source, and
|
||||
Drone shape.
|
||||
- **Genericity Matrix** — what is library-backed, template-provided, or authored.
|
||||
- **Auth Integration** — consuming the shared auth-server service (spec-driven,
|
||||
no auth code).
|
||||
- **Genericity Matrix** — what is library-backed, template-provided, or
|
||||
authored.
|
||||
- **Library Registry** — the catalog of internal libraries behind all of it.
|
||||
|
||||
Read the **Wiki** for the philosophy and rationale; these pages are the
|
||||
reference that mirrors the `standards` MCP bundle.
|
||||
reference that mirrors the `standards` MCP bundle.
|
||||
|
||||
Reference in New Issue
Block a user