Choose the parts. Keep the freedom.

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 defines network and protocol contracts; Agentz supports continuity through Cortex memory, Nexus permissions and specialist work; Menexus designs ensurance, insurance and assurance. A generic adapter must not silently choose a model, accept a fact or change a product’s policy.

Skyzai Personal and Skyzai Work are planned app packages. Me explains individuals, We organisations, and They machine intelligence participating through protocols within the shared Marketsphere; Holobiont is a continuing case experience composed from separately owned capabilities. Skyzai Markets combines commerce contributions for a different customer job. Independent apps can use a qualified component without inheriting the entire Skyzai app. Across the proposed Marketsphere, composability lets participants combine and replace capabilities without one provider owning the whole undertaking. Useful coordination and continued renewal still need outcome evidence.

The seven apps are intended to run on compatible cloud infrastructure without requiring a Skyzai node. Over time, qualified workloads could move to Spectre nodes and mesh capacity through replaceable adapters. Execution, storage, transport, security and recovery each need acceptance evidence before migration; this is a staged design target, not seven operating hosted services.

Before a host adopts a component, its maintainer needs an inspectable adoption record. The semantic steward keeps the domain contract; changing an adapter does not change what an event, permission or payment means.

Contract and version

Pin the package and contract versions, schema, supported inputs, rejected or missing inputs, error states and compatibility policy. Name the steward and consumer maintainer.

Licence and terms

Record the exact licence, notices, dependencies, model or content rights, permitted redistribution and provider terms. Open source does not grant every data, hosting or commercial right; unresolved rights hold adoption.

Permission and portability

Export only the data and context the participant may disclose, in a named versioned format. Keep credentials and keys under their own custody rules. Permission to export is not permission for a new provider to use every retained record.

Failure and recovery

Test revocation, expiry, missing inputs, duplicate requests and partial failure. Restore permitted data into a compatible consumer, reconcile pending effects, retain correction history and qualify rollback before switching. Delivered copies cannot be recalled by merely removing a local adapter.

For example, replace a relay adapter while retaining the addressed-event contract. Compare relay rejection, endpoint acknowledgement, offline expiry and duplicate handling with the prior adapter. If a provider refuses or permission expires, show that state and hold affected work; a fallback must not broaden disclosure. Adoption follows accepted parity and a tested return path. This is a qualification example, not a completed live migration.

Candidate Carbon exchange integrations and the proposed native SKY/ZAI system require separate acceptance. Replacing an adapter creates no bridge, custody migration or automatic conversion. A synthetic local receipt does not establish OFN issuance.

Check the infrastructure and monetary dependencies · Dated contract/adoption proposal. Its earlier product roster retains its date; current product ownership is described above.

The October 9 Flutter extraction proposal counted 54 top-level feature modules and 29 component/scope records. Those are historical candidates, not 29 released packages. The pinned October 17 comparison accounts for 1,691 current Dart files and finds 35 capability leaves for review. It assigns no present owner from an old folder label alone. Existing code is a starting point; each extraction still needs its own contract, consumer and maintenance evidence.

Product capabilities

Voice, text, navigation and case presentation in APU; attributed feeds and comparison in Circle; scenarios in ReFu; work coordination, memory and permissioned context in Agentz; ensurance, insurance and assurance in Menexus; exchange and commerce in LIQUID; personal AI family offices in MurMur.

Protocol capabilities

Network keys, relay contracts and message carriage belong to SPECTRE. Wallet transaction and payment semantics belong to LIQUID; purpose-limited context disclosure belongs to Nexus within Agentz. A shared login widget does not become any of those services.

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.

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.

The current trace marks capabilities as proposed, source-observed, bounded-local or hosted-source-unaccepted. None is verified as an operating service. A case memory record is not an insurance promise, an OpenQR endpoint is not a settled payment, and a synthetic receipt is not OFN issuance.

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.

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

VVision

Our products and other apps can assemble dependable, replaceable components while retaining control over domain meaning, data and exit.

MMission

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.

OObjectives

Qualify independent consumers, substitute optional adapters, record adoption responsibilities and demonstrate reuse benefit against the coupled alternative.

SStrategies

Separate domain contracts, presentation, platform adapters and host wiring. Keep one semantic steward per contract and evaluate each extraction on a declared workflow.

KMeasures & triggers

Correct workflows, independent builds, adapter substitution, complete adoption evidence and total extraction, integration and maintenance effort. Comparative benefit remains unmeasured.

AAgents & skills

Product stewards, package engineers, consumer maintainers and independent reviewers. Delivery appointments and operating capacity remain unassigned.