Repository links may require access. Source inspection is separate from a clean public-package installation.
AN INTERACTIVE READING MAP
Get the shape of this guide.
Move through the ideas, inspect their relationships, or make a focused reading path. The complete guide stays below.
⌘↗
READING SEQUENCEUnderstand how the ideas connect
Choose a point to look closer ↓
01 / Guide section
Treat a feature as a set of declared dependencies
A larger feature often combines operations, policy decisions, UI surfaces and external services. Feature Hubs provide a way to make those relationships inspectable rather than burying them in application startup code.
Read the supporting context ＋
Begin with the capability you need and list its operation references and required ports. Choose only the composition your product uses; a catalogue entry is not a reason to install the entire ecosystem.
Explore a section, then continue with the complete article below.
1 / 4
Treat a feature as a set of declared dependencies
A larger feature often combines operations, policy decisions, UI surfaces and external services. Feature Hubs provide a way to make those relationships inspectable rather than burying them in application startup code.
Begin with the capability you need and list its operation references and required ports. Choose only the composition your product uses; a catalogue entry is not a reason to install the entire ecosystem.
Follow the effect gate
The inspected effect invoker first requires an active installation. It checks that the capability declares the operation and port, that a policy is bound to that operation, and that the actor has the required capability.
It then resolves the port and evaluates the policy. Where policy obligations exist, the host must fulfill them and provide evidence before the effect callback runs.
Missing condition
Expected boundary
What to inspect
Declared capability or operation
Invocation is rejected
Installed manifest and versioned refs
Provider port
Invocation cannot proceed
Host port bindings
Allowed policy decision
Effect remains denied
Policy input and evaluator
Obligation evidence
Effect remains denied
Host fulfillment and durable evidence
↳A reusable piece comes with a set of relationships.Trace the mechanism · 3 ways to look closer＋
A communication capability might need an operation, a provider port and a policy binding. Explore what happens when one piece is missing.
What is ready in the composition?
A CONCRETE SITUATION
You can inspect the promise before enabling an effect.
The capability is described, but no active installation or provider has been selected.
01 / Declare
Name the operations, capabilities and required ports.
What changes
The product can discover the capability and its requirements.
What stays explicit
A declaration alone does not send a message or initialize a provider.
FOLLOW THE CONSEQUENCE
Use the dependency map to choose what to bind. Do not treat catalogue presence as runtime readiness.
A port is the place where your concrete implementation enters the composition. It might represent storage, a queue, a provider client or another application service. Keep its lifecycle and credentials in the host.
Provider replacement is therefore an integration task: the new implementation must satisfy the expected behavior, not merely share a method name. Test the failure and recovery paths that the feature depends on.
Qualify the composition you actually deploy
Start with deterministic fixture ports and verify the declared dependencies and denial behavior. Then qualify the selected providers in the intended environment. Record what was fixture-backed and what was exercised against a real service.
A local all-in-one example demonstrates composition. It does not by itself establish that every provider, tenant configuration or production deployment has been verified.
See it in an example.
Composition / Advanced
Compose nine feature hubs
Compose an application
Inspect one application composition with matching semantic routes for web and native.
01
Read the composition fixture
02
Compare semantic routes
03
Inspect the hybrid override
Source demonstratesThe source fixture composes all nine hubs.
Does not demonstrateThat inert adapters connect to live providers.
Inspect the walkthroughBehavior · proof and limits · source checks＋
Follow the source behavior
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.
Read the composition fixture
The fixture supplies the hubs' required ports with inert deterministic adapters. This makes the composition inspectable without provider credentials.
Compare semantic routes
The test expects nine hub keys and equal semantic, web, and native route ID lists.
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.
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 example establishes＋
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.
Does not demonstrate
That inert adapters connect to live providers.
That matching route IDs prove feature parity in every renderer.
Production qualification for a specific deployment.
Look inside the guideOpening context · complete reading path＋
Separate requirement, connection and binding
An application can describe the capability it needs without embedding a provider account in its contract. The integration model distinguishes a service definition, a tenant's configured connection and the application binding that selects a connection for a named slot.
Look inside the guideOpening context · complete reading path＋
Start with the task, actor and context
A reviewer, an operator and an agent may work on the same workflow while needing different information and actions. Model that difference explicitly instead of copying the entire workflow into unrelated screens.
Look inside the guideOpening context · complete reading path＋
Give each test one question
An operation has several boundaries, and one green check cannot answer every question about them. Separate declaration validity, business behavior, adapter behavior and external consumption so failures tell you where to look.
