Skip to main content
Skip to the site menu

Research & build · capability evidence

What exists, and what remains planned

Trace selected Skyzai capabilities to their product owners and the evidence behind each claim. A plan, source file, local test and accepted live service are different states.

Read each claim at its own level

This curated trace contains 35 capability records as of . It follows the current product ownership map and selected Flutter, package and adjacent source evidence.

The pinned company Flutter revision has 1,691 Dart files indexed by path. Function-level review covers ten formerly mixed modules and the 36-file Holobiont workspace; remaining files still need semantic review. These 35 records therefore do not account for every built feature or establish a complete screen audit. See the coverage audit for the review boundary.

No capability in this trace has an accepted live-release or operating qualification. The labels below describe evidence for a specific capability; they do not describe the availability of an entire product. See the dated source trace for the pinned references and methodology. Some linked source records require repository access.

Proposed

Owner direction or a dated plan. No qualifying implementation has been accepted.

Source observed

Relevant code is present in pinned source. Its behavior and release are still unaccepted.

Bounded local proof

A narrow local or synthetic test has run. The recorded scope limits the claim.

Hosted source; release unaccepted

Hosted-path code and local or emulator tests exist. No live release has been accepted.

Follow the participant served by a capability: the individual in Me, the shared organisation in We or agents running on protocols in They. The product linked on each record remains its owner.

Three forms of participation, with explicit gaps

The 18 October architecture preserves these 35 source-trace records and their evidence levels. It separately records 16 proposed requirements. A new place in the website is not evidence that an app feature has been implemented.

Me · Individuals.

For individuals: develop capabilities, make informed choices and turn personal intentions into useful outcomes with control over identity, relationships and memory.

We · Organisations.

For organisations: combine capabilities, coordinate commitments and create shared value. DAVs and DACs retain their distinct organisation models and evidenced legal status.

They · Machine intelligence.

For machine intelligence: obtain resources, combine capabilities and contribute useful work through open protocols, with defined permissions and accountable commitments.

Me is the individual, We is the shared organisation, and They is the agents running on protocols. A DAV or DAC has legal-person status only where actual registration in an identified national jurisdiction is evidenced. Individuals may represent organisations or operate agents through granted permissions; neither source presence nor agent identity establishes authority.

Proposed requirements still awaiting implementation and acceptance
  • Identity and acting-account controls — proposed, primarily me.
  • Direct conversations and retention choices — proposed, primarily me.
  • Conversation-centred external account context — proposed, primarily me.
  • Broadcasts, posts and attributed milestones — proposed, primarily me.
  • Inspectable and configurable feed — proposed, primarily me.
  • Cloud contact book and scoped sharing — proposed, primarily me.
  • Porter primary value-chain activities — proposed, primarily we.
  • Consumable service, XaaS and durable product offers — proposed, primarily we.
  • Product and service twins — proposed, primarily we.
  • Quote, agreement, fulfilment, payment and service — proposed, primarily we.
  • Organisations, DAV participation and governance — proposed, primarily we.
  • External asset origination and investor terms — proposed, primarily we.
  • Admitted compute and machine execution — proposed, primarily they.
  • Storage capacity and recovery infrastructure — proposed, primarily they.
  • Machine identity, discovery and service admission — proposed, primarily they.
  • Mesh node and relay operation — proposed, primarily they.

Other Flutter source still needs ownership review

The same pinned app tree contains mixed foundations beyond the 35 selected capability records. These are examples of source presence, not accepted journeys, product assignments or released services. The function-boundary review starts the separation, but many paths remain unreviewed.

Me · personal foundations

Account and profile switching, Nostr social and direct-message interfaces, event participation and personal-record paths appear in the app. Inspect the account source and Nostr service source. Their source presence does not establish an accepted social or event journey.

We · shared work foundations

Business creation and membership, identity and KYB documents, and booking paths appear in the app. Inspect the membership source and KYB repository. No operating business or identity service follows from those files alone.

Me and They · connection controls and adapters

Connected-app grants and revocation, plus provider-key client paths, appear in the app. Agentz owns Nexus connections; the individual in Me controls grants, and agents in They use protocol adapters within those grants. Inspect the connection repository and vault client source. Permission and credential behavior still needs acceptance across the actual client and service.

The OpenQR connection receipt builder is explicitly simulated or scanned-unverified. It does not establish payment or OFN receipt issuance.

Browse by owner

apu.bot

The product owns these capabilities. Read its purpose and scope.

Source observed

Voice, text and navigation UI

apu.bot · Me, We, They

Evidence or direction
Flutter voice-capture and search/navigation source exists in the company app.
Claim limit
Source presence does not prove complete device journeys, speech quality or an independently released APU UI.
Next gate
Inventory every route and verify signed-in phone/earbud journeys, errors and accessibility.
Source records
Bounded local proof

Continuing case and source presentation

apu.bot · Me, We

Evidence or direction
The shared-case page and local preview present records, citations and review controls; bounded browser and widget checks are recorded.
Claim limit
The case UI is a composed host and its local preview does not establish a production signed-in release.
Next gate
Accept real signed-in source/case journeys and show source revisions and correction effects on two devices.
Source records
Bounded local proof

Local attributed case lookup

apu.bot · Me, We

Evidence or direction
The local host calls the pinned APU librarian find/cite path against selected case records.
Claim limit
Deterministic local retrieval is narrower than APU search service or live model analysis.
Next gate
Qualify the source-owned APU adapter and accept an attributed lookup in the signed-in host.
Source records
Bounded local proof

Typed ordering and reference policy

apu.bot · Me, We, They

Evidence or direction
A standalone pure Dart ordering package and two fixture hosts demonstrate explicit criteria and tie handling.
Claim limit
Synthetic reuse is not production extraction, independent-team adoption or the full APU interface.
Next gate
Obtain steward acceptance, source-owned adapter adoption and a measured host proof.
Source records

Circle

The product owns these capabilities. Read its purpose and scope.

Source observed

Attributed source evidence

Circle · Me, We, They

Evidence or direction
Local and hosted case adapters name Circle as an external evidence source and preserve attribution.
Claim limit
Circle was unavailable from the inspected host; adapter code does not prove a reachable live Circle service.
Next gate
Connect the source-owned Circle endpoint and verify attribution, revisions and refusal behavior end to end.
Source records
Bounded local proof

Comparison, disagreement and correction

Circle · Me, We, They

Evidence or direction
The local synthetic case retained corrected records and flagged dependent work for review.
Claim limit
This proves a host correction flow with illustrative inputs, not a released Circle comparison service.
Next gate
Accept Circle-owned comparison/correction semantics with genuine source records in the app.
Source records

ReFu

The product owns these capabilities. Read its purpose and scope.

Bounded local proof

Attributed forecast/market source

ReFu · Me, We

Evidence or direction
A local browser read a real public ReFu market response and retained its status and attribution.
Claim limit
A price/status observation is not a verified forecast, tradable market, current outcome or service acceptance.
Next gate
Qualify the ReFu source contract and verify an owner-selected current question through resolution.
Source records
Proposed

Forecast horizon and resolution

ReFu · Me, We

Evidence or direction
The owner assigns explicit horizons and resolution rules to Reality Futures.
Claim limit
No accepted question-to-outcome lifecycle is evidenced by this trace.
Next gate
Publish and test a question, horizon, resolution source, correction and calibration cycle.
Source records

Agentz

The product owns these capabilities. Read its purpose and scope.

Source observed

Continuing case work and memory boundary

Agentz · Me, We

Evidence or direction
Case code binds work, feedback and retained state across product contributions.
Claim limit
Local case storage and generated drafts are not the intended durable redundant Agentz memory.
Next gate
Specify accepted Agentz memory contract and replayable cross-device case invariants.
Source records
Bounded local proof

Bounded local review and learning

Agentz · Me, We

Evidence or direction
Device brief and local bounded review/feedback loop passed documented local checks.
Claim limit
Device work and synthetic provider checks do not prove autonomous multi-agent service or live model inference.
Next gate
Accept a consented real provider run, attribution, review and explicit retention in the signed-in host.
Source records
Hosted source; release unaccepted

Authenticated case synchronization

Agentz · Me, We

Evidence or direction
Flutter outbox/CAS and Firebase callable/Firestore source have local emulator and unit evidence.
Claim limit
No production deployment or two signed-in device acceptance was established.
Next gate
Run release handoff with real Auth/App Check, conflicting edits and exact two-device recovery.
Source records
Source observed

Cortex memory and retrieval within Agentz

Agentz · Me, We, They

Evidence or direction
The owner puts Cortex within Agentz; dated source and a separate proof package show bounded text/retrieval interfaces.
Claim limit
Historical Cortex product labels and a text package do not establish production memory or search.
Next gate
Define a versioned Agentz memory authority and verify retrieval against accepted retained data.
Source records
Bounded local proof

Bounded text lifecycle

Agentz · Me, We, They

Evidence or direction
A dependency-free Dart package and two synthetic Flutter hosts exercise deterministic routing and text lifecycle.
Claim limit
No real model, provider quota, production extraction or independent-team adoption is proven.
Next gate
Adopt the contract in a source-owned host with real bounded provider and refusal evidence.
Source records
Proposed

Encrypted redundant memory

Agentz · Me, They

Evidence or direction
User-controlled encrypted replicas and exact restore are owner-directed Cloud Computer requirements.
Claim limit
No replica count, recovery, failover, confidential inference or key recovery is implemented by the local receipt carrier.
Next gate
Demonstrate user-authorized task key, independent replica failure and exact restore without duplicate effect.
Source records
Source observed

Purpose-scoped connections

Agentz · Me, We, They

Evidence or direction
Existing Connect repositories and consent UI form source candidates for Nexus connection work.
Claim limit
A renamed ownership boundary does not prove independently admitted Nexus grants or cross-product consent.
Next gate
Inspect current grant paths and accept revocation, purpose scope and adverse disclosure tests.
Source records
Bounded local proof

Specialist work and model routing

Agentz · Me, We, They

Evidence or direction
The local host uses one bounded Agentz review step; a separate package demonstrates synthetic deterministic model routing.
Claim limit
This does not establish many-agent orchestration, live model service, independent consensus or global budget enforcement.
Next gate
Verify two scoped specialists, provenance/disagreement and controlled model billing in an authorized host.
Source records
Proposed

Attested cloud workers and usage

Agentz · They, We, Me

Evidence or direction
Cloud Computer plan specifies isolated execution, attestation, latency and metered usage.
Claim limit
No worker measurement, task-key release, mobile latency profile or currency settlement is implemented.
Next gate
Execute the first-proof sequence with mismatched attestation refusal, latency receipt and simulated usage.
Source records

Menexus

The product owns these capabilities. Read its purpose and scope.

Proposed

Ensurance preparation

Menexus · We, Me

Evidence or direction
Menexus currently owns preparation for obligations and risk responses.
Claim limit
No qualified contract, operator or delivered ensurance service is established.
Next gate
Define customer promise, inputs, evidence duties, exclusions and accepted preparation workflow.
Source records
Proposed

Insurance terms and claims

Menexus · We, Me

Evidence or direction
Menexus currently owns specified protection and insurance semantics.
Claim limit
The local legacy case receipt is not a policy, underwriting decision, coverage, claim or regulated operating authority.
Next gate
Qualify policy/claim lifecycle, legal/operator authority and adverse-case claims handling before offering coverage.
Source records
Proposed

Assurance verification

Menexus · We, They, Me

Evidence or direction
Menexus currently owns evidence that commitments were fulfilled.
Claim limit
The historical menexus-core carrier returns PROPOSED case snapshots; it does not assure performance.
Next gate
Specify commitment evidence, verifier independence, exceptions and accepted assurance receipt.
Source records

LIQUID

The product owns these capabilities. Read its purpose and scope.

Source observed

Catalog, bookings and orders

LIQUID · We, Me

Evidence or direction
Current Flutter source includes product listings, booking repositories and marketplace order-book builders.
Claim limit
Code inventory is not an accepted commerce or order lifecycle; availability, settlement and release are unverified.
Next gate
Trace listing-to-order authority and test accepted inventory, booking, fulfillment and failure paths.
Source records
Source observed

Holder wallet and balances

LIQUID · We, Me

Evidence or direction
Wallet repositories and balance/backup implementations exist in the company app source.
Claim limit
Source presence does not establish custody, balances, key recovery or operating settlement.
Next gate
Qualify custody boundary, key recovery, reconciliation and an authorized user wallet journey.
Source records
Source observed

Exchange and strategy clients

LIQUID · We, Me

Evidence or direction
DEX service and trade UI source are present in the company app.
Claim limit
An exchange client is not a live order, price, liquidity or executable trading mandate.
Next gate
Verify quote, user authorization, submitted transaction, settlement and adverse outcomes with an appointed operator.
Source records
Source observed

Payment terms and receipts

LIQUID · We, Me, They

Evidence or direction
Wallet payment models and dated OpenQR/transfer receipt component candidates exist.
Claim limit
No live payment, OFN issuance, transferable receipt or legal entitlement is proven; OFN needs source-owned qualification.
Next gate
Define external OFN receipt source, signed terms, spend authorization and reconciled settlement proof.
Source records

MurMur

The product owns these capabilities. Read its purpose and scope.

Proposed

Personal AI family office

MurMur · Me, We

Evidence or direction
The owner assigns personal resource and mandate work to MurMur; CP-14 is a historical shadow-office proposal.
Claim limit
No connected family-office service or delegated operating mandate is evidenced.
Next gate
Approve a bounded personal mandate and demonstrate permissioned resource advice with review.
Source records
Proposed

Separately permitted collective research

MurMur · We, Me

Evidence or direction
Collective comparison/aggregation is part of MurMur direction only with separate permission.
Claim limit
Private case data does not automatically transfer to a collective and no released aggregate is evidenced.
Next gate
Demonstrate opt-in scope, contribution revocation, aggregation protections and source attribution.
Source records

SPECTRE

Network and transport foundation, outside the seven-product ladder.

Bounded local proof

Signed relay bootstrap transport

SPECTRE · They

Evidence or direction
The private package, two synthetic Flutter hosts and 80 local tests exercise a bounded transport profile.
Claim limit
Synthetic fixture signatures and host verifiers do not prove a real relay, authentic Nostr events or endpoint acknowledgement.
Next gate
Connect to a real relay with event verification and recipient-bound acknowledgement across two hosts.
Source records
Proposed

MESH, RELAY, AXIOM and FLOW

SPECTRE · They

Evidence or direction
Broader SPECTRE network, physical and coordination roles remain source programme targets.
Claim limit
A Nostr bootstrap package proves none of the physical mesh or state-agreement layers.
Next gate
Pin each source-owned protocol and demonstrate independent interoperating roles under loss and recovery.
Source records
Proposed

Network metrology and settlement

SPECTRE · They, We

Evidence or direction
Capacity, energy and economic receipt interoperability are future SPECTRE scopes.
Claim limit
No measured operating capacity, billing integrity or settlement authority is established.
Next gate
Verify signed usage measurement, dispute path and independently reconciled economic receipts.
Source records

Permanent Composability

A shared discipline for reusable contracts and adapters, outside the seven-product ladder.

Bounded local proof

Versioned reusable contracts

Permanent Composability · They, Me, We

Evidence or direction
Three isolated packages use explicit contracts and synthetic two-host assembly.
Claim limit
Package proofs are not adopted company-app dependencies or independent-team releases.
Next gate
Release one source-owned versioned contract with compatibility and adverse-case tests.
Source records
Source observed

Optional host adapters

Permanent Composability · They, Me, We

Evidence or direction
Dated component cards separate core/adapter candidates and the company host composes multiple product views.
Claim limit
A shared host is not proof that adapters are independently substitutable or separately adopted.
Next gate
Extract one adapter behind a versioned port and replace it in two independently maintained hosts.
Source records
Proposed

Independent adoption and reuse economics

Permanent Composability · They, Me, We

Evidence or direction
The release model calls for independent reuse and measured assembly cost.
Claim limit
No independent adopter, accepted package release or measured reuse cost is recorded here.
Next gate
Record an external steward/adopter, release pin, integration time and maintenance burden across upgrades.
Source records

Holobiont shared case

A composed case experience across product owners, not an eighth product.

Bounded local proof

Local composed shared case

Holobiont shared case · Me, We, They

Evidence or direction
Local preview and tests exercise a case with product-specific records, correction, decision and feedback.
Claim limit
A composed UI does not merge Circle, ReFu, Menexus, LIQUID or MurMur authority and is not live signed-in acceptance.
Next gate
Verify source-owned records and a signed-in end-to-end case with explicit permissions and reviewed retention.
Source records
Hosted source; release unaccepted

Signed-in cross-device experience

Holobiont shared case · Me, We, They

Evidence or direction
Hosted sync and work source has emulator/unit checks and a documented release handoff.
Claim limit
No published service or real two-device same-account acceptance is established.
Next gate
Complete the hosted release handoff and exact same-account two-device case loop, including conflict recovery.
Source records

Context: Capability evidence & status.

Skyzai

Outline

Site

Partner data room How this guide worksOpen website map Explore Protocol Atlas Development & availabilityContact Skyzai

Website app

Display

Theme follows your device

Skyzai, close at hand.

Keep this website on your home screen and read saved pages offline. The connected app at skyzai.com is still in development.

On iPhone or iPad, open this site in Safari, choose Share → Add to Home Screen, then Open as Web App if offered. On Android or desktop, use your browser’s Install app or Add to Home screen menu when available.

Offline reading & privacy

Offline reading becomes available after the initial download. External sites are not saved. Your browser may evict saved pages.

Conversations and drafts are never saved by the offline cache. Reloading clears them. To remove downloaded pages, clear this website’s data in browser settings; uninstalling alone may not clear it.