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

Skyzai.ORG — Quick Start

Technical orientation snapshot only. Do not treat this page as a guaranteed fresh-clone success path or as a blanket deployability claim.

Public reader entry

This is contributor orientation, not a public install path. Private registers and proof lanes below require approved repository access; they are not prerequisites to reading this site. Public readers can start with Introduction, current status and the public protocol map.

Read This First

Before running anything, separate:

• code that exists
• local proof paths that have been receipted
• claims about public/runtime deployment

Use:

1. The code-only P-scores register (private, unpublished)
2. The runtime-truth boundary document (private, unpublished)
3. The uplink orientation index (private, unpublished)

Practical Local Entry Points

1. Uplink orientation

These are private, unpublished orientation documents, not reproduced here.

2. TheCircle local proof lane

TheCircle now has a real-source local proof path that emits canonical packet artifacts. Use the organ-local receipts to find the currently proven path before trying to generalize to live relay operation.

3. APU local proof lane

APU has the strongest executable code surface and a bounded local proof from canonical packet intake to Skyzai F4 acceptance. Treat that as the best current developer proof lane for inter-organ closure.

4. Skyzai local proof lane

Skyzai has:

• a self-booting local F4 bridge proof path
• a Flutter web build proof

Those are the cleanest current ACT entry points.

What This Page Is Not Saying

This page is not saying:

• every subsystem will boot from a clean clone without environment work
• every public deployment claim is current
• every contract or payment surface is already live

It is saying the repository contains meaningful executable surfaces, and the best way in is through the currently receipted proof lanes rather than through older launch-language snapshots.

Short Route

If you only want the smallest honest developer path:

1. orient through Uplink
2. inspect the current runtime truth
3. run the proven local proof lane you actually care about
4. avoid treating public wiki language as stronger than the owning source

---