Skyzai Protocol Atlas

The Protocol Atlas is a source-linked map of Skyzai's doctrine, organs, schemas, protocols, mechanisms, substrates, and proposed systems. It does not call every object a protocol.

Open the synchronized atlas interface →

Prototype boundary: the interface uses a static generated registry. It is not a live Circle feed, deployment monitor, authority surface, market, settlement rail, or proof of public operation.

Claim ceiling: Pre-launch architecture and locally evidenced components only. The registry proves no public deployment, Layer-1, settlement, market, ad placement, affiliate payout, legal clearance, authority, or DAV birth.

How to read it

• The left outline answers where an object is easiest to find.
• The center mind map answers how selected objects relate.
• The right update feed answers what changed in this source-linked atlas and when.
• The 00–07 domains are functional navigation, not Rosetta L1–L7.
• Every object keeps separate spec, implementation, runtime, deployment, and external-verification status.
• Every node has may_sign=false and may_authorize=false.

The eight domains · 47 typed objects

00 · Orientation & Constitutional Root

What constrains every protocol before it can operate?

• 5 + 7 constitutional fences · constraint-suite · [S/I] declared constitution — Five output fences and seven alignment disciplines preserve non-extraction, history, exit, evidence tiers, direction, and per-station integrity.
• DAV Canon · formation-standard · [S] source contract — Fail-closed rules separating an organ, product, document, DAC, or candidate from a born DAV.
• Emergentism · doctrine · [S] source role; [I] atlas placement — The orientation layer of the holobiont; it orients and does not operate.
• Rosetta / Soul Loop · dispatch-grammar · [S] route grammar — The seven-station reasoning and dispatch grammar; L1-L4 are deployable mixed-sign moves and L5-L7 are non-deployable witnesses.

01 · Context, Identity & Consent

Whose context may be disclosed, to whom, for what purpose, and for how long?

• Connect · protocol-capability · [S/D] source and reconciliation — Binds identity, scoped grants, consent, expiry, revocation, and principal continuity without transferring authority.
• Cortex · organ · [S/B] bounded source and local checks — Principal-owned memory and context records; it remembers but does not reason, recommend, sign, or advertise on the owner.
• Nexus · protocol-suite · [S/D] source plus staged anatomy — Connects parties through transport, disclosure shapes, and typed objects; it transmits purpose-bound views and does not remember, reason, sign, or authorize.
• NexusContextView · schema · [S/B] schema and local fixtures — A derived, purpose-bound disclosure object that references source records without carrying raw Cortex memory.
• Organization Intelligence Connection · context-connection-pattern · [S] repository source; [D] operating hypothesis — Defines a Skyzai-side target that connects selected source and operational evidence through apu.bot's L1 intake/source map and Menexus typed context to compatible model consumers while systems of record remain authoritative.

02 · Observation, Forecast & Deliberation

How does IS become COULD and then an unsigned SHOULD?

• Agentz · organ · [S/B] source and local checks — Combines admitted IS and COULD inputs into an unsigned SHOULD proposal with an exact consequence and stop conditions.
• Agentz proposal guard · capability · [D/B] blueprint and local checks — The SHOULD-NOT and inoculation polarity that can surface refusal, constraint, and counterargument inside the Agentz proposal process; its former APU label is retained only as routing provenance.
• apu.bot · organ · [B] apu.bot architecture description; [S] active naming source — At L1, its intake/librarian function maps selected sources, lineage, freshness observations, and source-owner rights references into cited bundles. At L5, it consumes a valid NexusContextView and emits non-authoritative reasoning artifacts while retaining uncertainty and counterarguments.
• Circle · organ · [S/D] normative source; UI prototype only — Terminates observation in a sourced SignalPacket / IS: who asserted what, from which source, when, and on what basis.
• ForecastPacket · schema · [S/B] schema and local evidence — A probability/scenario packet that preserves uncertainty and may refuse assessment.
• RealityFutures · organ · [S/B] source and local checks — Transforms admitted observations into uncertainty-bearing COULD scenarios or ForecastPacket objects.
• SignalPacket · schema · [S/B] contract and local fixtures — The terminal observation packet for Circle's IS boundary, with source, provenance, freshness, correction, and uncertainty fields.

03 · Network, Routing & Topology

How do typed objects move without transport becoming authority?

• AXIOM · routing-shape · [S/D] topology source and candidate primitive — An N:1 convergence, adjudication, and candidate market/truth-settlement topology over SPECTRE.
• FLOW · routing-shape · [S/D] topology source and routing skeleton — A 1:1 bilateral channel and direct-settlement topology over SPECTRE; endpoint authorities remain local.
• MESH · routing-shape · [S/D] topology source and routing skeleton — The N:N mycelial route fabric for gossip, peer discovery, telemetry, congestion sensing, and path adaptation inside SPECTRE.
• RELAY · routing-shape · [S/D] topology source and candidate primitive — A 1:N sovereign publication and delivery-receipt topology over SPECTRE.
• Skyzai Layer-1 DAG · substrate-program · [D/C] programme design — A future aBFT/DAG settlement substrate intended to model network topology while separating routing observation from consensus and finality.
• SPECTRE transport ground · network-substrate · [S/D] source boundary — The routing, gossip, telemetry, and topology skeleton beneath the four disclosure shapes.

04 · Evidence, Authority & Consequence

What may cross from proposal into an exact-bound consequence?

• AuthorityWeave · schema · [S/B] schema and fixtures — References actual mandates, persons, thresholds, scope, expiry, revocation, and the exact consequence hash without creating authority.
• Exact-Bound Execution Rail · execution-interface · [S/B] contract and local checks — Permits deterministic software to perform only the already-authorized consequence whose hash and limits match the authority weave.
• ExecutionReceipt · schema · [S/B] schema and fixture — Records execution or settlement activity tied to the exact proposal, authority reference, and rail.
• OFN Receipt Standard · receipt-standard-draft · [D/B] draft plus bounded adapter tests — Drafts typed OFNReceipt and kernel ReceiptPacket alignment for economic-event certification, replay, lineage, and export.
• OutcomeEvidence · evidence-object · [S/D] contract — Independent provenance that can evaluate what actually happened after execution and return it as a new observation.
• PRISM · verification-protocol · [S/B] active contract and local checks — Verifies externally created authority evidence, exact-consequence bindings, and execution receipts.
• SkyzaiConstraintDisposition · constraint-disposition · [S] active route contract — Evaluates an exact Agentz proposal and emits HOLD, RETURN, or non-authorizing PASS before any external authority handoff.

05 · Economy, Markets & Settlement

How is value accounted, offered, matched, and settled without hiding the rail?

• SKY · economic-asset-design · [C/D] design — A proposed energy-linked credit role inside the future Skyzai monetary design.
• Skyzai DEX application · reusable-product-definition · [S] repository source; [D] application target — Defines reusable evidence-backed listings, buyer and supplier intents, agent negotiation proposals, recommendations, exact consequence handoffs, and receipt views, including market and limit intents.
• SoResFi · protocol-suite · [D] draft synthesis — Accounts, moves, escrows, streams, collateralizes, allocates, and proves economic events for an institution without owning that institution.
• ZAI · economic-asset-design · [C/D] design — A proposed economic asset role inside the future Skyzai monetary design.

06 · Commerce, Growth & Service

How does a maker offer become a receipted sale, fulfilment, and service loop?

• Affiliate Link Attribution · marketing-mechanism · [D] design — Attributes a disclosed referral route to a maker offer and pays only after a matching DEX sale receipt.
• Golden-Ratio Affiliate Cascade · allocation-design · [D] mathematical design — A bounded recursive-upline allocation design using golden-ratio weights, caps, loop refusal, disclosure, and an explicit remainder.
• Maker-Controlled Distributed Fulfilment · commerce-protocol-design · [D] owner direction — Lets a producer register contracted retailers, distributors, service centers, and inventory locations, then first notify an eligible nearby node after sale.
• Product Service AI · service-pattern · [D] owner direction — A product-specific AI post-trained or grounded on maker-approved twin content to answer service questions and route warranty or remedy cases.
• Serial Registration & Warranty Service · commerce-protocol-design · [D] owner direction — Binds a buyer-presented serial number to maker records and a product twin for service, warranty, recall, and remedy routing.
• Skyzai Commerce Interface · protocol-suite · [D] design — A shared commerce loop spanning product evidence, maker offer, eligibility, match, authorization, settlement, fulfilment, service, receipt, and review.
• Third-Party AI Sponsored Offer Distribution · advertising-protocol-design · [D] owner direction — Distributes clearly labelled sponsored DEX maker offers to third-party AI systems and optimizes against attributed sale receipts.
• User-Owned Intent Advertising · advertising-protocol-design · [D] owner direction — Lets the user's own Cortex identify an in-market moment locally and disclose only a minimal expiring intent token through Nexus for eligible sponsored maker offers.
• Virtual Product Twin · commerce-standard · [D] design — A versioned digital representation of a real product, its maker declarations, documentation, service facts, and evidence lineage.

07 · DAV Formation, Evolution & Exit

How can the organism reproduce, correct itself, and remain leaveable?

• DAV Factory · protocol-suite · [S/D] source suite — Provides fail-closed formation, charter, evidence, lifecycle, and dissolution patterns for candidate distributed augmented valuechains.
• Evolutionary Network · guardian-system · [S/B] source and local checks — Refuses, quarantines, reviews, preserves, recovers, and stages bounded genome-adoption proposals after evidenced outcomes.
• Grace Exit · constitutional-mechanism · [S/I] constitutional constraint — Requires documented withdrawal of legitimate or redeemable property, data, keys, receipts, and history without doctrinal punishment.
• LQID DEX · layer-2-dav-target · [S] source organization; [D] runtime and market design — The first concrete Layer-2 DAV target on Skyzai, intended to keep a future ZAI bond role, full-node role, and versioned instance of the reusable DEX application distinct.
• SupportChain Protocol · protocol-suite · [S/D] source route — Routes reusable support assets across at least two DAV contexts without converting a route into a live shared-services claim.

Source and update discipline

The editable source is 00_CONTROL/atlas/SKYZAI_PROTOCOL_REGISTRY_V1.json. The outline, OPML, mind maps, wiki page, and browser data are generated together and checked for drift. A feed item records an atlas update; it does not establish deployment or external effect.