Files
docs/standards/src/lib/index.md
Vishesh 'ironeagle' Bangotra d7c344c9aa feat: full-stack MCP surface — client template, npm CI, 13 repos
- build.py: vendor templates/client into mcp/templates/client with
  client.json manifest (16 kinds); register drone-npm as a third CI shape
  (types: pypi/npm/docker); root *.py stale doc numbers fixed
- registry.py: registry://client resource + list_client_components /
  get_client_component / get_client_template tools; build prompt gains the
  client scaffold step (docs://modules/ui_admin); compliance prompt covers
  npm packages; drone docs describe all three shapes
- repos.json (+mcp): doc-weaver, react-auth, react-openapi (npm Type B,
  package.json version source), vet (app Type C, VERSION)
- docs: 90_drone_pipelines gains Type B npm section; 91_versioning covers
  package.json as a version source; 94_repository_inventory gains the npm
  package table and services/apps Type C; lib index updated

Verified: bundle regen (24 modules, client 16, drone 3, repos 13); registry
client readers exercised against the vendored bundle.
2026-10-20 12:02:31 +05:30

2.2 KiB

Standards Reference

The reference half of the Standards description: the enforceable rules, patterns, and the internal library catalog that agents consult while coding.

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.

Delivery & Meta

  • Drone Pipelines — the three CI shapes: a PyPI package, an 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.
  • 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.