Skip to content
ContractSpec
Start here

Composition · Advanced · runnable fixture source

Compose nine feature hubs

Inspect one application composition with matching semantic routes for web and native.

@lssm-tech/example.feature-hub-composition · Fixture source inspected · evidence as of 2026-10-27

Source context

Fixture source inspected · b67c376f

Pinned source links require repository access; publication and anonymous package availability were not checked for this example.

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.

AN INTERACTIVE READING MAP

Walk through this example.

Step through the maintained source review, inspect its evidence boundaries, or assemble an adaptation packet.

SOURCE WALKTHROUGH

Read the operation in its authored order

01 / IN FOCUS

Read the composition fixture

The fixture supplies the hubs' required ports with inert deterministic adapters. This makes the composition inspectable without provider credentials.

1 / 4

0 points in your packet

Walk through the source

  1. Read the composition fixture. The fixture supplies the hubs' required ports with inert deterministic adapters. This makes the composition inspectable without provider credentials.
  2. Compare semantic routes. The test expects nine hub keys and equal semantic, web, and native route ID lists.
  3. 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.
  4. 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 this review establishes

  • 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.

Not established

  • That inert adapters connect to live providers.
  • That matching route IDs prove feature parity in every renderer.
  • Production qualification for a specific deployment.

Before adapting

  • 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.

Adapt the pattern

  • 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.
declaredStability
Not recorded
registry
Source package exists; absent from inspected generated registry
inlinePreview
Not registered
execution
Not rerun
production
Candidate