Hono HTTP server for the Vana Personal Server — routes, middleware, composition root

Delivery-workflow engine for the Agent Architecture Board (execution, bootstrap, pipelines, board, boardScan, requirements, and composition root).

Babel macro to define application composition root

Server-side composition root for Course Builder

Memorix production service composition root — one versioned API over accepted packages.

Polpo Node.js runtime — orchestrator wiring, adapters, server assembly, runner entry. The composition root behind the polpo-ai package.

The browserflow binary — composition root.

A compact composition root for HTTP routes, middleware, and errors.

Composition root: wires the @rynx-ai/runtime host to channel plugins (injected by the daemon) and exposes a liveness HTTP probe.

Canonical home of the agent-workflow planning methodology — the Plan→Phase→Step vocabulary, plan lifecycle, queue.md series index, and mandatory Cleanup phase, consumed by the kit (composition root). The methodology engine of the agent-workflow family.

AI-first TypeScript/Bun framework. Modular, SOLID, zero magic. The AI reads the composition root and knows everything.

Composition root wiring core, consensus, and mempool into a runnable validator node

v0.3.0 composition root (design §1 principle 1): wireMemory/wireContinuity/wireWiki construct the memory fabric's stores, register its tools, and return runChatLoop-ready seams — one stable call replacing per-emitter memory codegen.

Build-time codegen CLI for Model City front-end projects: emits route shims, the composition root and the Tailwind source manifest for the modules selected in modules.config.mjs.

RivetOS composition root — config loading, plugin wiring, lifecycle

LOCAL/single-node production-style boot entrypoint + AppDeps composition root. Pre-external-hardening (no RLS/KMS/per-tenant isolate/DPoP) — NOT internet-facing. Assembles the platform from env, applies the committed migration chain via the real programma

GPU-free CarbonEngineJS composition root and runtime service registry.

The tenant-scoped data layer. Request-path and run-core code only ever hold a **`TenantDb`** (obtained via `forTenant`) — the raw, unscoped database handle stays at the composition root. Postgres-backed, with tenant isolation as a construction-time guaran

オープン会計 embedded backend composition root — runs openkk-server in-process (same JS runtime as the client). Inject any OpenkkDbPort (file / memory / etc.).

The **Codemation command-line** package: parse arguments, wire a small composition root, and run **build**, **dev**, **serve**, and **user** subcommands against a **consumer project** (your app that defines `codemation.config.ts` and workflows).