Skip to main content
Skip to the site menu

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

Pipeline API Contracts — F1 through F4

Current canonical packet spine — 2026-07-25​

The current cross-organ contract is longer than the historical four-packet illustration below because authority, execution, outcome, and adoption are non-substitutable states:

SignalPacket -> ForecastPacket -> DecisionDocket -> ProposalEnvelope
  -> ExactConsequence -> AuthorizationReference -> ExecutionIntent
  -> ExecutionReceipt -> OutcomeReceipt -> GenomeAdoptionProposal

Circle owns SignalPacket; RealityFutures owns the external ForecastPacket; Agentz compiles DecisionDocket and unsigned ProposalEnvelope; applicable external authority binds only one ExactConsequence; Skyzai may execute only that consequence. An execution receipt is not an outcome receipt, and an outcome may propose genome adoption but cannot mutate the active genome.

Missing probability, warrant, model/oracle/resolution metadata, or freshness produces UNKNOWN/HOLD, never an imputed 0.5. These repository contracts and local fixtures do not establish live packet flow, authority, execution, settlement, or world evidence.

Historical F1–F4 illustrative contract body — preserved for provenance

Overview​

The organs communicate through typed, versioned JSON interfaces. Each interface is a one-way data contract. No organ reads another organ's internal state. All inter-organ communication passes through exactly one of these four channels.

Circle ──F1──> ReFu ──F2──> APU ──F3──> Skyzai ──F4──> Circle

F1: Circle -> RealityFutures (SignalPacket)​

Circle publishes verified OSINT signals. ReFu consumes them as market inputs.

{
  "schema": "skyzai.signal.v1",
  "signal_id": "sig_a1b2c3d4",
  "timestamp": "2026-04-12T14:32:00Z",
  "source": {
    "source_id": "src_reuters_feed",
    "eigentrust_score": 0.87,
    "source_type": "news_api"
  },
  "claim": {
    "text": "ECB signals rate hold through Q3 2026",
    "category": "monetary_policy",
    "entities": ["ECB", "EUR"],
    "geo": "EU"
  },
  "evidence_tier": "E",
  "watchman_score": 0.82,
  "corroboration": {
    "independent_sources": 3,
    "cross_ref_ids": ["sig_x1", "sig_x2", "sig_x3"]
  },
  "nostr_event_id": "note1abc...",
  "k0_ledger_seal": "ar://tx_hash_abc123"
}

F2: RealityFutures -> APU (ProbabilityBundle)​

ReFu outputs priced probabilities. APU consumes them as decision inputs.

{
  "schema": "skyzai.probability.v1",
  "market_id": "mkt_ecb_q3_hold",
  "question": "ECB holds rates through Q3 2026",
  "timestamp": "2026-04-12T14:35:00Z",
  "lmsr_price": 0.74,
  "ensemble_estimate": 0.71,
  "confidence_interval": {
    "lower_95": 0.62,
    "upper_95": 0.83
  },
  "market_depth": {
    "volume_24h_sky": 12450.0,
    "total_liquidity_sky": 89200.0,
    "num_traders": 847
  },
  "resolution_date": "2026-10-01T00:00:00Z",
  "related_axioms": ["axm_ecb_q1_hold", "axm_ecb_q2_hold"],
  "input_signals": ["sig_a1b2c3d4"],
  "model_weights": {
    "timesfm": 0.45,
    "chronos": 0.35,
    "domain_specialist": 0.20
  }
}

F3: Agentz -> Skyzai (ProposalEnvelope)​

APU outputs an unsigned proposal and never signs or executes a consequence. The v1 path described here is public-DAV only. A future private Natural-Person adapter may accept only that Person's exact signed instruction. For the public DAV, 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 only.

This is a [D] target contract, not proof of a live authority or settlement runtime. proposal_hash is SHA-256 over the RFC 8785 JSON Canonicalization Scheme (JCS) encoding of the complete F3 object, excluding only the proposal_hash field itself.

{
  "schema": "skyzai.prism.proposal_envelope.v1",
  "envelope_id": "env_d4e5f6g7",
  "hash_algorithm": "SHA-256",
  "canonicalization": "RFC8785-JCS",
  "proposal_hash": "sha256:proposal_hash...",
  "timestamp": "2026-04-12T14:38:00Z",
  "action": {
    "type": "rebalance",
    "asset": "EUR_HOLD_Q3",
    "direction": "long",
    "size_sky": 500.0,
    "position_sizing": {
      "method": "lx_optimal",
      "lx_value": 2.85,
      "kelly_fraction": 0.12
    }
  },
  "council_deliberation": {
    "intelligence": {"vote": "proceed", "confidence": 0.82},
    "strategy": {"vote": "proceed", "edge": 0.08},
    "legal": {"vote": "proceed", "k_violations": []},
    "treasury": {"vote": "proceed", "exposure_after": 0.15},
    "chief_of_staff": "PROCEED"
  },
  "risk_parameters": {
    "stop_loss_pct": 0.05,
    "max_drawdown_pct": 0.10,
    "correlation_flag": false
  },
  "phi_split": {
    "lp100_pct": 61.8,
    "operations_pct": 38.2
  },
  "authority_status": "gated_pending_complete_valid_bound_receipt",
  "input_bundles": ["mkt_ecb_q3_hold"]
}

Authorization Transition: Proposal -> AuthorityReceipt​

F3 never becomes executable by changing its own status. A separate authority receipt must bind the exact proposal hash. For a public DAV, the validator must establish the signer(s) required by applicable law, the entity's governing instrument, or a valid competent mandate and reject AI/caste signatures. Missing, mismatched, replayed, or undersized authority fails closed; F4 is not emitted.

authority_mode MUST equal public_dav_prism in v1. The private_natural_person is deferred to a later versioned receipt schema; v1 adapters must reject it and every other value rather than translate an unknown mode through an implicit alias.

Before reading any F3 content field, the adapter MUST recompute SHA-256 over the RFC 8785/JCS encoding of the complete F3 object excluding only proposal_hash. Both proposal.proposal_hash and authority_receipt.proposal_hash MUST equal that recomputed digest, and the receipt's proposal_envelope_id MUST equal the proposal's envelope_id. Tampering with an action while retaining the old carried hash therefore fails closed before deliberation or execution.

If the recomputed F3 proposal is HOLD, the adapter returns a non-F4 ProposalDisposition.no_action; no authority or execution receipt is emitted. For every non-HOLD proposal, a missing authority receipt fails closed before F4.

{
  "schema": "skyzai.authority_receipt.v1",
  "receipt_id": "authrcpt_prism_001",
  "authority_mode": "public_dav_prism",
  "decision_id": "decision_prism_001",
  "proposal_envelope_id": "env_d4e5f6g7",
  "proposal_hash": "sha256:proposal_hash...",
  "natural_person_councilors": [
    {"councilor_id": "npub1...", "signature": "sig_1..."},
    {"councilor_id": "npub2...", "signature": "sig_2..."}
  ],
  "ai_signatures": [],
  "validation_status": "valid",
  "validated_at": "2026-04-12T14:39:00Z"
}

F4: Skyzai -> Circle (SettlementReceipt)​

Skyzai broadcasts execution results only after validating the bound authority receipt. The F4 envelope embeds the full receipt and a hash of its canonical JSON encoding, carrying the signer entries for later verification rather than making validation_status the proof. Independent cryptographic verification remains gated until the signature scheme, key registry/encoding, and domain-separated signed payload are specified. The nested authority_receipt.proposal_envelope_id MUST equal the F4 envelope_id; any hash, identity, signature, mode, or envelope mismatch fails closed. authority_receipt_hash is SHA-256 over the RFC 8785/JCS encoding of the full nested authority_receipt; the top-level hash metadata and hash field are not part of that nested object. Circle ingests the settlement and authority trace as new observations.

{
  "schema": "skyzai.receipt.v1",
  "receipt_id": "rcpt_h8i9j0k1",
  "timestamp": "2026-04-12T14:39:12Z",
  "envelope_id": "env_d4e5f6g7",
  "authority_receipt_hash": "sha256:canonical_authority_receipt_hash...",
  "authority_receipt_hash_algorithm": "SHA-256",
  "authority_receipt_canonicalization": "RFC8785-JCS",
  "authority_receipt": {
    "schema": "skyzai.authority_receipt.v1",
    "receipt_id": "authrcpt_prism_001",
    "authority_mode": "public_dav_prism",
    "decision_id": "decision_prism_001",
    "proposal_envelope_id": "env_d4e5f6g7",
    "proposal_hash": "sha256:proposal_hash...",
    "natural_person_councilors": [
      {"councilor_id": "npub1...", "signature": "sig_1..."},
      {"councilor_id": "npub2...", "signature": "sig_2..."}
    ],
    "ai_signatures": [],
    "validation_status": "valid",
    "validated_at": "2026-04-12T14:39:00Z"
  },
  "execution": {
    "status": "settled",
    "asset": "EUR_HOLD_Q3",
    "filled_size_sky": 500.0,
    "avg_price": 0.74,
    "settlement_tx": "0.0.12345@1681234567.000000000"
  },
  "k0_receipt": {
    "arweave_tx": "ar://tx_hash_def456",
    "schema_version": "skyzai.transfer_receipt.v1"
  },
  "relay_broadcast": {
    "nostr_event_id": "note1def...",
    "relay_urls": ["wss://relay.skyzai.com", "wss://relay.damus.io"]
  },
  "phi_split_applied": {
    "to_lp100": 309.0,
    "to_operations": 191.0
  }
}

Versioning​

All schemas use semantic versioning (v1, v2, etc.). Breaking changes increment the major version. Organs must support the current version and one version back. Schema definitions are published at schemas.skyzai.com.

Context: Pipeline API Contracts.

Skyzai

Outline

Site

Partner data room How this guide worksOpen website map Explore Protocol Atlas Development & availabilityContact Skyzai

Website app

Display

Theme follows your device

Skyzai, close at hand.

Keep this website on your home screen and read saved pages offline. The connected app at skyzai.com is still in development.

On iPhone or iPad, open this site in Safari, choose Share → Add to Home Screen, then Open as Web App if offered. On Android or desktop, use your browser’s Install app or Add to Home screen menu when available.

Offline reading & privacy

Offline reading becomes available after the initial download. External sites are not saved. Your browser may evict saved pages.

Conversations and drafts are never saved by the offline cache. Reloading clears them. To remove downloaded pages, clear this website’s data in browser settings; uninstalling alone may not clear it.