Framework architecture
The RC is a set of composable APIs, not a single mandatory application bootstrap. Use the public entry-point guide to choose the runtime surface.
Application composition
- Load metadata support before decorated application classes.
- Create/register application providers in a
Container. - Compose pipelines, controllers, pages, jobs and event handlers explicitly.
- Configure request/tenant isolation and external resources.
- Start the application only after its required startup checks pass.
- Stop workers, subscriptions, listeners and owned resources during shutdown.
The quick start demonstrates the pipeline, DI and store APIs without depending on internal module bootstrapping.
Major areas
- Pipeline: typed contexts, composition, built-in middleware and result envelopes.
- DI: explicit providers, lifetime control and child containers.
- State: reducers, subscriptions, observable state and optional persistence.
- Web/server: typed pages, Express adapters, request scope and HTTP helpers.
- Integrations: databases, jobs, events, agents, telemetry and sandbox clients.
- Browser: selected state/UI APIs and micro-frontend integration.
These areas can share dependencies; the repository is not a strict dependency stack with every subsystem depending only on the layer immediately below it.
Modules and declarations
The public Module decorator records DI grouping metadata. It does not
automatically register/load an application's entire graph. The internal
ModuleRegistry / ModuleLoader declarations exposed from the root are
type-only. See module composition.
Runtime boundaries
Root and Node/server entry points are not guaranteed browser-safe.
Use browser-specific imports and verify bundles. Development tooling is not
automatically removed merely because NODE_ENV is production or an export map
exists; use separate development entry points and inspect production output.
APIs range from stable candidates to experimental. Generated scaffolding, the internal unified builder and CLI/provider paths have limitations; review support levels before deployment.