Guide
Build on real rendering, data, security and service owners.
Build one boundary at a time#
- Rendering and SSR ownership: authored components, explicit adapters, assets and hydration limits.
- Request lifecycle: generation/request cleanup and response commitment.
- Configuration handbook: actual consumers versus optional standalone factories.
- Database queries: named connectors and driver-specific transaction capabilities.
- Tenant data: verified identity at each data boundary.
- Route-data cache: explicit policy, invalidation and private defaults.
- Localization: request locale, inert text and RTL boundaries.
Find a package contract#
The API directory contains one authored guide per public package, including optional adapters. Imports never imply provider activation, consent or authorization. Required host callbacks, resource shutdown and missing live prerequisites are part of each guide.
From a complete example#
Use the renderer/data/queue example to connect selected owners explicitly. Keep future roadmap tasks separate from this implemented contract.