aetos/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
06ff5bce6e9ee104705f5562a1666051ffb9e520
docs/standards/src/wiki/index.md
Vishesh 'ironeagle' Bangotra 06ff5bce6e docs(standards): mirror doc-forge wiki style; mermaid + copyable build prompt 
- move templates into src/templates; renumber wiki pages; add app-components page

- embed agentic build prompt as a copyable markdown block; add mermaid diagrams

- build.py writes <name>/mcp; config static bundle -> standards/mcp

- registry reads libraries.json as bytes (committed file was UTF-16LE); normalize to UTF-8

- Dockerfile: drop stale blog copy; per-repo <name>/mcp copies

- drop nested standards/mcp/standards duplicate and empty root mcp/
2026-10-12 00:21:41 +05:30

3.2 KiB
Raw Blame History

🧩 Standards — the Aetos App Blueprint

One reusable architecture for every backend application in the Aetos ecosystem: a spec-first HTTP edge, a pure 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
Build Recipe The ordered, agentic checklist for a new app
Testing & Quality Test layout and acceptance gates

Reference (separate site, mirrors the MCP bundle): the enforceable rules — Layering, Composition Root, Spec-First Routing, CRUD Template, Pipeline Scaffold, Worker & Progress, Human-in-the-Loop, Infra Adapters, Genericity Matrix, Library Registry.

🔗 Related Resources

  • MCP bundle — standards server on :8009: read doc://index, doc://nav, doc://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 skeleton at standards/src/templates/app/
  • Copy the repo's AGENTS.md-style build prompt from Build Recipe

© Aetoskia Internal — standards