Status: pre-launch. This page describes target design; nothing on skyzai.org is live yet.

DEV-07 — Private-DAV Reference: K2 Envelope Flow

Source: a private pipeline module (k2_inbox.py); its repository path is not reproduced here.

Scope

This page documents the legacy/private-DAV K2 inbox and is reference doctrine, not the active public-DAV authority path. Public-DAV AI/caste seats stage an unsigned ProposalEnvelope only. Any consequence requires a complete valid bound PRISM decision receipt from at least two natural-person councilors binding the exact consequence; PRISM records and verifies only. Constitution, membership, or policy adoption does not authorize a later consequence. Skyzai fails closed before receipt validity; deterministic software carries out only that exact bound consequence.

Local Inbox Shape

Today the inbox scans heterogeneous JSON envelopes in a private execution-log directory (not reproduced here).

The query layer normalizes:

• status: any status beginning with PENDING is pending;
• type: type, then action_type, then the legacy private-DAV reference k2_envelope field if a chain trace exists;
• timestamp: timestamp, then signed_at, then created_at.

CLI

From within the private pipeline directory (not reproduced here), the k2_inbox module accepts flags for pending items, grouping by type or by day, the most stale entries, a named item, or a time window.

--quiet emits JSON and is safe for automated checks.

Legacy Private-DAV Flow

model / agent / runtime proposes the Natural Person's private act
  -> pipeline creates legacy private envelope
  -> execution_log stores k2_*.json
  -> k2_inbox summarizes pending state
  -> that Natural Person reviews
  -> the Natural Person accepts or refuses their own private act
  -> execution surface acts only after that private signature

Current Public-DAV Target Flow

AI / caste seat stages unsigned ProposalEnvelope
  -> at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt
  -> PRISM records and verifies only; it never signs or produces the receipt
  -> authority validator checks exact proposal/consequence binding and receipt completeness
  -> missing, mismatched, AI-signed, or undersized receipt fails closed
  -> deterministic executor carries out only that exact bound consequence and returns an execution receipt

Developer Guard

No agent should bypass execution_log for consequential actions. If an action touches money, identity, public communication, memory lineage, deployment, or legal posture, it stages an envelope.