Permanent Composability

Choose the parts. Keep the freedom.

Build an experience from the capabilities it needs. Keep their meaning clear, their adapters replaceable and the option to leave intact.

On this page

Contracts & adapters
Shared capabilities
Evidence of reuse
Direction & delivery

A permanent responsibility across Skyzai.

Composability supports SPECTRE, all seven products and the experiences built from them. It owns the discipline of independent reuse: versioned contracts, replaceable adapters and explicit assembly by each host app. It does not require a central daemon or become an eighth product.

Each product keeps the meaning of its own capabilities. SPECTRE carries messages and network state; Cortex owns accepted memory and reflection; Agentz specifies model routes. A generic adapter must not silently choose a model, accept a fact or change a product’s policy.

Me, We, They and Skyzai Markets can combine these capabilities for different customer jobs. Independent apps can use a qualified component without inheriting the entire Skyzai app.

The Flutter work has a home.

The recorded Flutter inventory covers 54 modules and 29 component/scope records. Two records preserve the deferred Gold catalogue and carbon demonstration; the count does not mean 29 active packages. Existing code provides a starting point; each extraction still needs its own contract, consumer and maintenance evidence.

Product capabilities: Purpose, sources and tasks in APU; attributed feeds and comparison in Circle; scenarios in ReFu; coordination in Agentz; continuity and permissioned context in Cortex; exchange and commerce in LIQUID; personal AI family offices in MurMur.
Protocol capabilities: Keys, relays and message carriage belong to SPECTRE. Identity disclosure belongs to Nexus. A shared login widget does not become either service.
Reusable kits: OpenQR, verification interfaces, key-storage adapters, safety interfaces and shared UI can be independently consumed where their contracts fit. Product-specific payment, permission and receipt semantics stay with their owners.

Profiles, social communication, events and business operations follow the customer job and service boundary. A calendar, payroll workflow or message transport need not be forced into the same package simply because it appeared in one app.

Reuse must earn its place.

A bounded local transport demonstration already connects two independently composed Flutter apps through a reusable package. This is evidence for that contract and those consumers. Live relay interoperability, cryptographic verification and independent adoption remain open.

A further bounded local proof exercises the minimum Cortex text contract in two separately built Flutter hosts using synthetic adapters. Both hosts were authored in the same session; this does not establish independent-team adoption, real-model inference or customer usefulness. OpenQR can proceed independently.

Further qualification needs separately maintained consumers and task-specific evidence. For every extraction, compare correct workflows and the total cost of integration, substitution and maintenance with the existing coupled implementation. Keep a capability together when extraction offers no demonstrated benefit.

Working evidence and current limits

These documents require access to the private GitHub repositories. Builds and tests establish bounded engineering results; customer benefit, operating readiness and broad reuse require separate observations.

Direction and delivery · VMOSK-A

This is a proposed programme of work. It does not qualify every component for release or appoint an operator.

Vision: Our products and other apps can assemble dependable, replaceable components while retaining control over domain meaning, data and exit.
Mission: Make selected product and protocol capabilities independently consumable through versioned contracts, replaceable adapters and explicit host assembly, preserving semantic ownership, data control and exit across SPECTRE, the seven products and their experiences.
Objectives: Qualify independent consumers, substitute optional adapters, record adoption responsibilities and demonstrate reuse benefit against the coupled alternative.
Strategies: Separate domain contracts, presentation, platform adapters and host wiring. Keep one semantic steward per contract and evaluate each extraction on a declared workflow.
Measures & triggers: Correct workflows, independent builds, adapter substitution, complete adoption evidence and total extraction, integration and maintenance effort. Comparative benefit remains unmeasured.
Agents & skills: Product stewards, package engineers, consumer maintainers and independent reviewers. Delivery appointments and operating capacity remain unassigned.