Skip to content

architecture.md

Latest commit

 

History

History
91 lines (72 loc) · 3.85 KB

architecture.md

File metadata and controls

91 lines (72 loc) · 3.85 KB

Architecture

ZERO is the operating intelligence layer between humans and capital, starting with onchain perpetual markets.

This public repository has four first-class open surfaces:

  • ZERO Runtime: local autonomous operations runtime with paper mode, safety gates, API, journals, live-readiness contracts, extension contracts, and paper-first evolution loops that make ZERO adaptive operating intelligence.
  • ZERO Protocol: MCP-compatible schemas, read/compute tools, mandates, replay frames, evidence bundles, audit entries, permission metadata, and local verification fixtures.
  • ZERO Proof: redacted proof packets, proof profiles, replay/export fixtures, journal roots, verification commands, and public contract schemas.
  • Developers: repo-local quickstarts, CLI/API docs, examples, release gates, and contribution paths that start at getzero.dev/developers.

The ZERO CLI is Runtime tooling, not a separate hosted product surface. Hosted Studio, Control, Registry, founder-admin, and doctrine surfaces live outside this repository; this repo supplies the Runtime, Protocol, and Proof substrate they can consume.

Deployment is Railway-recommended, Docker-compatible, and local-first. Operators own their deployment project, secrets, exchange credentials, and runtime state. ZERO does not need a separate hosted deployment product to be credible.

Principles

  • Local-first by default
  • Paper mode before live execution
  • Explicit operator control
  • Inspectable decisions
  • Risk-reducing actions stay fast
  • Risk-increasing actions require friction

Public Runtime Flow

JSONL candles -> MarketDataAdapter -> Strategy -> OrderIntent -> PaperEngine -> RiskDecision

Strategies propose. The paper Runtime decides. This keeps extension work deterministic and prevents examples from bypassing safety gates.

The runtime loop wraps that path in an explicit OODA cycle:

observe -> orient -> decide -> act -> learn -> journal -> durable bus

The public zero-engine-run command currently runs this loop in paper mode and emits zero.runtime.cycle.v1 records. With --runtime-bus, it also writes checksum-chained zero.runtime.event.v1 events and a fast boot snapshot. See runtime-bus.md for the local event contract. Live-capable runtime work must preserve the same cycle visibility and fail closed when safety or reconciliation checks are not ready.

Public Evolution Flow

runtime journal -> memory -> knowledge -> research -> genesis proposal -> guardian
                -> build/red-team -> paper canary -> calibration
                -> promote or rollback -> evolve backlog

The public repo now implements the first part of this loop: local memory extraction, append-only memory JSONL, active-memory expiry, generated knowledge.md, /memory, read-only MCP memory snapshots, genesis proposal classification, append-only genesis journals, /genesis, read-only MCP genesis snapshots, fixture-backed research reports, /research, read-only MCP research snapshots, paper-only evolve gate runs, /evolve, and read-only MCP evolve status. Real mutation, promotion, and rollback are tracked as public extraction targets in Evolve Harness. Local memory, research, genesis, and evolve belong in open source because they are part of a self-custodial operator's runtime. Future commercial data products can build on opt-in verified behavior, cohorts, history, webhooks, redistribution, or operational SLAs without gating basic Runtime use.

Commercial Flow

Runtime behavior -> opt-in verification -> ZERO Proof -> commercial data products

The commercial product is advantaged access to verified autonomous behavior at speed, scale, and history. Basic runtime use, self-custody, public profiles, public leaderboards, delayed public intelligence snapshots, and public proof contracts remain open.