EXAMPLE / Composition
Compose nine feature hubs
Inspect one application composition with matching semantic routes for web and native.
Follow the pattern. Inspect its limits.
Explore the source walkthrough, its evidence and the choices you would make in your own application.
Read the composition fixture
The fixture supplies the hubs' required ports with inert deterministic adapters. This makes the composition inspectable without provider credentials.
An exploration of the inspected source; no example is executed here.
The situation.
A reference application composes Integration, Agent System, Agent Network, Workflow, Auth User, Auth Admin, Communication, CompanyOS, and Social Media hubs with deterministic adapters. It compares web and native route projections and applies an integration settings override.
What you will learn
- Compose nine feature hubs through explicit ports.
- Keep semantic routes consistent across host projections.
- Apply an override while preserving the composition's qualification status.
Follow the operation.
- 01
Read the composition fixture
The fixture supplies the hubs' required ports with inert deterministic adapters. This makes the composition inspectable without provider credentials.
- 02
Compare semantic routes
The test expects nine hub keys and equal semantic, web, and native route ID lists.
- 03
Inspect the hybrid override
The reference imports a granular Integration Hub view model and uses a hybrid route/component override with the /settings/apps alias.
- 04
Plan host qualification
The result remains candidate. Replace fixture ports with your own integrations and qualify the deployed topology, including storage, queues, scheduling, recovery, and authorization.
What the source demonstrates.
- The source fixture composes all nine hubs.
- The inspected test asserts semantic route parity between web and native projections.
- The reference explicitly retains candidate readiness.
What it does not establish.
- That inert adapters connect to live providers.
- That matching route IDs prove feature parity in every renderer.
- Production qualification for a specific deployment.
Bring it into your environment.
Use the exact source context and prerequisites below. A source walkthrough is not a verified public-package installation recipe.
- Access to the inspected source repository and a checkout at the cited revision.
- The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.
Working directory: examples/feature-hub-composition
bun run example
bun test src/run.test.tsThe fixture produces composition evidence, route parity, /settings/apps, and candidate readiness.
Commands and tests inspected; not executed here.
Read the related guide →Make the pattern your own.
- Adopt one hub when that is enough; full composition is an advanced reference.
- Bind actual ports at the host boundary.
- Preserve qualification gaps in the output until the exact deployment is tested.
Inspect the evidence.
Reviewed 2026-10-27 · b67c376f
Pinned source links require repository access; publication and anonymous package availability were not checked for this example.
- Declared maturity
- Not declared
- Catalogue registration
- Source package exists; absent from inspected generated registry
- Inline preview
- Not registered
- Execution in this review
- Not rerun
- Production qualification
- Candidate