Status: pre-launch. This page describes target design; this document does not establish a deployed service.
D3 -- What Exists Today
What is verified, what is claimed, and what remains blocked. As of 2026-09-24, this page merges the former Claim Status Map and Implementation Matrix pages into one dated status page.
This page is a public routing summary, not the upstream source of truth. Skyzai is pre-launch: no network, payments, tokens or accounts exist yet.
Read current status through three separate surfaces:
- Code-only health — a private P-scores register
- Runtime/public claim boundary — a private runtime-truth document
- Bounded local proof — dated receipts inside the organ folders
How to Read Any Claim on This Site
Skyzai spans several kinds of claim -- ontological, formal, interpretive, empirical, organizational, technical, implementation, and narrative -- and they do not carry the same degree of certainty. There is also a practical distinction between:
- code-only health — what is materially built in code
- bounded local proof — what has been receipted in local or controlled runs
- runtime/public truth — what may honestly be claimed as presently live to the outside world
For any major claim, ask: What kind of claim is this? What is its current status? What evidence supports it? What would falsify or constrain it? What is implemented versus proposed? Do not collapse "built in code", "a dated local receipt exists", and "actually live in runtime or public space" into one status word.
Status labels used below: Concept (directional idea) · Framework (structured model) · Formalized (explicitly defined) · Specified (described in architectural or implementation terms) · Prototype (partially built and testable) · Operational (in actual bounded use) · Deployed (publicly live or production-like) · Unknown / under audit.
What this project does not claim by default: that every metaphysical claim is empirically proven; that every formal claim is accepted scientific consensus; that every architectural component is already implemented; that every narrative correspondence is evidence; that every product or entity is equally mature; that symbolic coherence alone is proof; that strategic horizons are current technical capabilities.
What this project does claim: that coordination is a central civilizational bottleneck; that it is building a layered stack across doctrine, institution, protocol, and product; that different components are at different levels of maturity; that evidence, falsification, and kill criteria matter (see Kill Criteria); that readers should distinguish worldview, formalism, architecture, and implementation.
Current Register (2026-04-19 — historical snapshot)
Register note (2026-07-03): the table below is the dated 2026-04-19 code-only snapshot and is retained as a receipt. Later code-only refreshes (2026-05-12) measured TheCircle P=0.53, RealityFutures P=0.60, Agentz (formerly listed as APU) P=0.84, Skyzai P=0.59 — still code-only, still pre-launch, still bounded by the private runtime-truth document. Nothing here is a live-product claim. Like any measurement, this one is true of the date it was taken; treat it as decayed evidence, not a current number, until it is re-run.
| Surface | Code-only status | Bounded local proof | Runtime/public boundary |
|---|---|---|---|
| TheCircle | P = 0.53 | real RSS ingest proof and canonical SignalPacket emission proof exist locally | do not generalize this to live relay-native organism speech yet |
| RealityFutures | P = 0.59 | contract/test lane is real; Forge tests pass | no live deployed market loop is proven here yet |
| APU | P = 0.76 | one bounded SignalPacket -> APU decision -> Skyzai F4 acceptance -> memory query proof exists | not a live autonomous fund or public managed-capital claim |
| Skyzai | P = 0.55 | F4 bridge self-boots locally; key F4 tests pass; Flutter web build proof exists | real on-chain G1 settlement is still not the public truth |
| Organism | P = 0.60 | strongest local proof is now inter-organ, not single-organ only | runtime/public truth remains narrower than code breadth |
Selected Implementation Surfaces (2026-04-19 — historical snapshot)
This matrix distinguishes three kinds of maturity -- built in code, bounded local proof, and runtime/public embodiment -- and does not collapse them into one "live" label. If a public page sounds stronger than this table, trust the table.
| Component | Claim type | Status | Notes |
|---|---|---|---|
| Public wiki/docs | documentation | In progress | this batch of wiki content repairs is landing now; publication remains evidence- and typed-authority-gated, and documentation is not runtime proof |
| Uplink router | routing / governance | Operational | row ownership and tidy law are explicit (private routing index, not reproduced here) |
| TheCircle sensing path | technical / organizational | Prototype with bounded proof | real-source local F1 proof exists; live relay publication still separate |
| RealityFutures contract lane | technical / probability | Built with passing tests | code-only register stronger than public deployment posture |
| APU recommendation path | technical / organizational | Prototype with bounded proof | strongest executable organ in code; not a public autonomous fund claim |
| Skyzai execution bridge | technical / execution | Prototype with bounded proof | self-booting local bridge proven; real settlement still narrower |
| Skyzai app shell | product / execution | Built | build succeeds; auth/runtime decisions still depend on real credentials |
| Heartbeat loop | technical | Operational in controlled conditions | continuous loop exists; runtime/public claims still bounded upstream |
| Cortex memory | technical | Prototype | memory is real; long-term usefulness still under validation |
| Private-DAV single-owner action staging (reference doctrine) | technical / execution | Prototype | separate from the active collective-quorum path |
| Constitutional guards | governance / technical | Operational | strongest stable cross-cutting layer |
| Public relay output / voice | technical / communications | Prototype / incomplete | local proofs exist; full public relay-native voice still not general truth |
| Deployment body | operations / infrastructure | Partial | durable public deployment is still narrower than local orchestration proof |
What Is Safe To Say Publicly
- the organism is materially stronger in code than older public summaries implied
- local proof closures now exist across multiple organs, not just inside one folder
- present-tense runtime/public claims are still narrower than the code-only register
- public readers should distinguish built code, bounded local proof, and live outward embodiment
What Is Not Safe To Generalize Yet
- a claim that all organs are live in public/runtime space
- a claim that RealityFutures has a live deployed market loop
- a claim that Skyzai has already fired real public G1 settlement
- a claim that APU is a live autonomous managed-capital surface
- a claim that TheCircle is already emitting verified live relay-native F1 at organism scale
- a claim that documentation deployment equals product deployment
Next Proof Rights
- live TheCircle relay emission
- live RealityFutures market-backed F2 emission
- real settlement closure for Skyzai / APU
- stronger public/runtime alignment once those proofs exist
Reporting Discipline
- keep code-only, bounded-local-proof, and runtime/public truth separate
- link proof receipts for strong claims
- timestamp updates
- prefer upstream organism sources when this page and a source disagree