Status: pre-launch. This page describes target design; this document does not establish a deployed service.

Skyzai (Authorized Execution) — The Organism's Body

Domain: skyzai.com | Action-Control Stage: EXECUTE / RECEIPT after typed authority. Under applicable law, a Natural Person authorizes their own exact typed private act. A Legal Person requires lawful external authority plus the executors required by jurisdiction, with counsel conditional. For a public-DAV consequence, software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate binding that exact consequence. PRISM records and verifies that receipt only.

What Skyzai Does

Skyzai is the authorized-execution surface. It is where signed or governed intent is supposed to become state change, receipts, and outward consequence.

Read that in three layers:

• code-only register: P = 0.55
• bounded local proof: F4 bridge tests pass, the bridge self-boots locally, and the Flutter web shell has a clean build proof
• runtime/public boundary: the strongest public settlement and “fully live hands” claims remain narrower than the local execution proof lane

Current Evidence Note (2026-04-19)

• key F4 modules compile and run locally
• the F4 bridge accepts a local submission and returns stored decision memory
• a bounded local SignalPacket -> APU decision -> Skyzai F4 acceptance proof exists
• the Flutter web app builds cleanly and boots to routing
• real public on-chain G1 settlement is still not the claim this page should make

The Five Core Systems

1. Membrane

The membrane validates typed authority: a Natural Person authorizes their own typed private act using device-held keys; a Legal Person requires lawful external authority plus the executors required by jurisdiction, with counsel conditional; or the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate bind the exact public-DAV consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; deterministic software carries out only that exact bound consequence.

2. Execution Bridge

The F4 bridge is the most concrete current execution proof surface. Its current code accepts legacy private-DAV single-owner-shaped submissions, persists decision memory, and provides the cleanest local handoff from recommendation to stored execution artifact. That compatibility shape is not public-DAV authority or proof of a wired PRISM adapter.

3. Receipt Layer

Skyzai is supposed to make receipts first-class. That means execution should leave a durable, typed trace rather than only a UI effect. Receipt doctrine is stronger than final settlement closure right now.

4. Relay / Broadcast Path

The body is also where outward consequence becomes public state. The relay path exists architecturally and in partial local proof form, but it should still be spoken about carefully until the strongest public/runtime route is receipted.

5. App Shell

The Flutter app is the user-facing shell of the body. It now has a real clean web build proof, which moves this lane out of pure specification and into demonstrated executable code.

Architecture Direction

Skyzai is still the place where the following are meant to converge:

• signer and wallet root
• acceptance modes
• receipt generation
• settlement logic
• outward broadcast

That direction is real in code and partially proven locally. It is not yet a license to collapse “execution substrate exists” into “all public hands are live.”

Constitutional Constraint

Skyzai does not observe, price, or recommend.

It acts only on signed instruction and within constitutional bounds.

One-Line Truth

Skyzai is no longer just a design for execution, but its strongest present truth is still local proof of execution infrastructure, not the fully public final body.

---