SupportChain Protocol
[D] Pre-launch infrastructure design. This page specifies a proof protocol, not a buyer product. Nothing here is public, live, or evidenced as an operating network.
SupportChain is the canonical .org protocol for proving that a usable
artifact, process, or service was reused and that the second context avoided a
measured resource cost. The .com surface is only a Skyzai Work Cockpit
plugin or compatibility pointer; it does not become a third package or a
standalone product.
Proof gate
The protocol remains closed until two independent contexts produce complete, comparable receipts that show:
- what was reused;
- why the contexts are independent;
- the measured baseline and observed saving; and
- the method used to reconcile both receipts.
One demonstration, an internal transfer, or an estimated saving is not enough to open the surface. Until this gate is met, SupportChain may stage schemas, fixtures, and simulations only.
Authority boundary
Every public-DAV consequence requires a complete valid bound PRISM decision receipt in which at least two natural-person councilors bind that exact consequence. PRISM records and verifies the receipt only; it never signs, authorizes, acts, or executes. AI, agents, and software may deliberate, simulate, and stage unsigned proposals only. Constitution, membership, policy, or adoption may constrain a proposal but never authorizes a later consequence. The public DAV has no K2 runtime requirement, bootstrap, or fallback. Deterministic software may carry out only the exact consequence already bound by the valid receipt.
Current evidence
- Protocol status:
[D] - Canonical home:
skyzai.org - Commercial route: Cockpit plugin / compatibility pointer on
skyzai.com - Live proof: none