Product design
Follow a question through the tools and inspect each product’s purpose, proposed services and starting measures.
Explore a piece of workResearch & build
An idea you can examine.
Explore the assumptions, inspect the interfaces and see what still needs to be established. A reference model is a way to ask better questions—not proof of a working economy.
Choose what you want to examine.
Integration
Understand contracts, permissions and the interfaces a product could connect.
Read the integration foundationsNetwork research
Inspect SPECTRE’s transport, routing and operating evidence.
Explore SPECTREMonetary research
Review accounting assumptions, open questions and the evidence still needed.
Inspect the monetary modelsMonetary models: what they do—and do not—show
The selected monetary documentation baseline is dated . It reconciles the roles of ZAI, SKY and the reference lending model. Selection settles which model this explanation describes; it does not establish production readiness or economic success.
Accounting model
Tracks ZAI inventory, stake, redistribution, SKY loan draws, interest and repayments under explicit assumptions. Conserved balances are a model invariant, not proof of recoverable collateral.
Market assumptions
Work weights and provider behaviour are inputs to investigate. Market prices, demand, liquidity and losses must be tested together; a quoted AMM price is not cash available for every exit.
Separate experiments
The micro accounting model, macro scenarios and network research are not one validated integrated economy. Passing one experiment does not close the others.
This website explains those models; it does not run a return calculator, issue assets or connect a simulated balance to a wallet. Historical documents retain their own dates and status rather than becoming current merely because they are linked.
Six gates remain open
These are acceptance questions, not a countdown to launch. Each needs evidence appropriate to the claim before the design can advance.
- Accounting closure. Do issuance, accrual, redistribution, repayments and losses reconcile, including edge cases and repeated events?
- Funded recovery and exit. Who supplies actual purchasing power when collateral is sold, liquidity dries up or participants leave?
- Incentives and work. Can work be measured credibly, and do fees and rewards withstand gaming rather than just balancing in a fixture?
- Coupled demand. What happens when payment demand, borrowing, liquidity and participant behaviour change together?
- Distributed validity. How are locks, release proofs, retries, agreement and recovery enforced across the common ledger and DAV domains?
- Rights and responsibilities. What precisely may a holder, borrower, provider or operator claim, authorise, recover or dispute?
How Skyzai fits together
For prospective manufacturers, the public partner data room introduces the robotics marketplace proposal, pilot scope and open commercial questions.
Seven products supply complementary capabilities. Emergentism guides the whole framework; SPECTRE supplies the protocol foundation. Markets composes selected economic capabilities across Me, We and They.
The capability record traces selected Flutter, web and local proof work to its responsible product and states what the evidence does and does not establish. Me, We and They show how those same capabilities could serve different participants.
Inspect capability evidenceExplore the systemOpen the website map
Integration guides
Permanent Composability makes independently usable contracts, components, adapters and host assembly a standing programme across the network and products. It is separate from SPECTRE and does not require one central runtime service.
Start with a particular purpose and the smallest context it requires. Identify the caller, permissions, expiry and revocation. A direct model call must not gain ambient access to someone’s Cortex memory.
Follow the existing interfaces and their evidence. Local prototypes and reference implementations are not promises of hosted APIs, supported SDKs or production credentials.
Protocol Atlas
Explore technical objects and their typed relationships, with source records and status. The Atlas is a protocol map; the website map is a reading guide. They describe different things and do not replace each other.
Complete documentation
Use the complete public outline to go deeper. Documents retain their dates, evidence definitions and development boundaries. A public page or a passing local test does not establish a deployed service.