Skip to content

🧩 Standards — the Aetos App Blueprint

One reusable architecture for every backend application in the Aetos ecosystem: a spec-first HTTP edge, a framework-free domain core, a pluggable infrastructure layer, and a single composition root.

Fill in two axes only and a new app is done: your resource model, and (if needed) your pipeline family. The blueprint itself never names a business domain — expenses, health metrics, inventory, and analytics are all the same shape underneath.

Doc model: this wiki is written for humans — how-to guides, the build recipe, and quality gates. The enforceable rules (layering, composition root, CRUD template, pipeline scaffold) and the library registry live in the reference pages, mirrored by the machine-readable standards MCP bundle. Query find_library before writing any infrastructure.

🚀 Key Features

  • 🧭 Spec-first routing — the OpenAPI document, not decorator routers, is the source of truth (operationId lookup)
  • 🏗️ One-way layering — interfaces → domain → infra, enforced
  • 🔌 Single composition root — every dependency is wired in exactly one place
  • 🧩 Generic, not app-specific — reusable rules versus two authoring axes
  • 📚 Library-backed — DB, DI, pipelines, ingestion, auth, and docs come from internal libraries, never hand-written
  • 🚦 Explicit state machines — durable job statuses, progress, and human-in-the-loop pauses

📁 Documentation Structure

Section Description
Overview Philosophy, the one-way dependency rule, architecture
App Components The component model and how the pieces wire together
Start an App The entry point: gather the two axes, then build
Reference App The runnable vet sample — server, pipelines, client
Testing & Quality Test layout and acceptance gates

Reference (separate site, mirrors the MCP bundle): the enforceable anatomy — start at the Build Recipe, then the pillars: domains (Layering), the OpenAPI contract (Composition Root, Spec-First Routing, CRUD Template, Auth Integration), interfaces & infra (Infra Adapters), UI (Auto-Rendered Admin), the optional pipelines layer (Pipeline Scaffold, Worker & Progress, Human-in-the-Loop), and delivery/meta (Genericity Matrix, Library Registry).

  • MCP bundle — standards server on :8009: read docs://index, docs://nav, docs://modules/{module}; call find_library(capability)
  • Library registry — the catalog of internal libraries behind every app (libraries.json, served as registry://libraries)
  • Template — the runnable sample at standards/src/templates/app/ (server) and standards/src/templates/client/ (React admin); walkthrough in the Reference App
  • Start a build — invoke the start_app prompt on the standards server, or read the Start an App guide

© Aetoskia Internal — standards