Align public repo with Runtime, Protocol, and Proof surfaces

README.md

@@ -4,16 +4,19 @@
 [![OpenSSF Scorecard](https://github.com/zero-intel/zero/actions/workflows/scorecard.yml/badge.svg)](https://github.com/zero-intel/zero/actions/workflows/scorecard.yml)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
 
-**Autonomous operating system for self-custodial onchain operations.**
+**Autonomous operating system for self-custodial onchain operations: open ZERO
+Runtime, Protocol, and Proof.**
 
-ZERO is an open-source runtime and operator terminal for running autonomous
-capital operations without giving up custody. It starts with onchain perpetual
-markets: paper-first execution, safety gates, local journals, Hyperliquid
-read-only/live boundaries, self-evolution loops, public proof packets, and
-intelligence contracts.
+This repository is the open Runtime, Protocol, and Proof substrate for ZERO.
+The hosted product surfaces live at [getzero.dev](https://getzero.dev),
+[app.getzero.dev](https://app.getzero.dev), and the public developer entrypoint
+at [getzero.dev/developers](https://getzero.dev/developers). This repo stays
+focused on runnable software: paper-first execution, safety gates, local
+journals, Hyperliquid read-only/live boundaries, MCP-compatible readouts,
+public proof packets, and verification contracts.
 
-> Not another trading bot. ZERO is the control plane that makes autonomous
-> onchain operations inspectable, interruptible, and self-custodial.
+> Not another trading bot. ZERO is Runtime plus Proof for autonomous onchain
+> operations that must stay inspectable, interruptible, and self-custodial.
 
 ![ZERO paper runtime terminal proof](docs/assets/readme-terminal.svg)
 
@@ -56,7 +59,7 @@ scripts/railway_doctor.py https://zero-production-5214.up.railway.app
 
 ZERO has three non-negotiable product rules:
 
-- The engine is open source and useful without a hosted ZERO control plane.
+- The Runtime is open source and useful without a hosted ZERO app account.
 - Operators keep custody; live-capital paths are local, explicit, and gated.
 - Public reputation is built from redacted proof, not screenshots or claims.
 
@@ -79,11 +82,13 @@ cd zero/cli
 cargo run -q -p zero-os -- --api http://127.0.0.1:8765
 ```
 
-Inside the terminal, press `Ctrl+5` or run `/cockpit-mode` for the live
-cockpit. In paper/default mode it should refuse live risk and show the reason:
+Inside the terminal, press `Ctrl+5` or run `/cockpit-mode` for the read-only
+Runtime control packet. The command name is legacy CLI language; public product
+copy should call the surface ZERO Control. In paper/default mode it should
+refuse live risk and show the reason:
 
 ```text
-live cockpit
+runtime control
 live_mode=refused  ready=false  risk_allowed=false  controls_ready=false
 next: fix preflight check live_executor: live executor not configured
 
@@ -102,10 +107,10 @@ service or an unattended live-capital promise.
 
 ## Launch Status
 
-This repository is the public product page and open-core engineering home for
-ZERO. It is launch-ready for paper runtime work, operator-terminal development,
-safety-gate design, public proof contracts, self-evolution workflows, ZERO
-Network contracts, and ZERO Intelligence API contracts.
+This repository is the open Runtime, Protocol, and Proof engineering home for
+ZERO. It is launch-ready for paper runtime work, operator CLI development,
+safety-gate design, public proof contracts, self-evolution workflows, MCP
+contracts, and verification tooling.
 
 For live capital, the public stance is exact: ZERO is a self-custodial local
 runtime, not a hosted custody service. Operators bring their own wallet,
@@ -133,11 +138,12 @@ disciplined under stress.
 ZERO turns that workflow into an explicit operating system:
 
 - A runtime that evaluates, rejects, executes, and records decisions.
-- A terminal that keeps the operator in control.
+- A CLI and local control packet that keep the operator in control.
 - A safety model that makes risk-reducing actions fast and risk-increasing
   actions deliberate.
-- A public proof surface for profiles, leaderboards, and verification.
-- A free growth-mode intelligence layer built from verified autonomous behavior.
+- A public Proof surface for profiles, replay, and verification.
+- Protocol contracts that apps and agents can inspect without reading private
+  product doctrine.
 
 The default mode is paper. Live operation is self-custodial, explicit, and
 guarded by preflight checks.
@@ -147,32 +153,32 @@ guarded by preflight checks.
 | Surface | Role | Public status |
 | --- | --- | --- |
 | ZERO Runtime | Python engine for paper execution, production-parity OODA reports, live-readiness contracts, journals, safety gates, strategy adapters, venue adapter interfaces, local evolution gates, and canary evidence. | Open source |
-| ZERO Terminal | Rust CLI/TUI for setup, diagnostics, state inspection, replay, live cockpit views, and supervised actions. | Open source |
-| ZERO Evolution | Local memory, genesis proposals, research reports, decision-stack review, guardian review, red-team, paper canaries, calibration, promotion plans, local apply receipts, rollback receipts, and evolve loops that let ZERO improve under review. | Memory, genesis, research, decision stack, paper-first evolve gates, local apply, and rollback execution open; protected promotion remains human-reviewed |
-| ZERO Network | Public-safe profiles, empty/active/stale page states, leaderboards, verification badges, profile verification, and deterministic proof-chain packets. | Open source contracts |
-| ZERO Intelligence | Delayed public snapshots plus growth-mode free realtime APIs, history, cohorts, webhooks, exports, and future SLAs built from verified autonomous behavior. | Open contracts + free operator-growth access |
+| ZERO Protocol | MCP-compatible schemas, tool permissions, mandates, evidence bundles, replay frames, audit entries, and local verification fixtures. | Open source |
+| ZERO Proof | Redacted proof packets, replay/export fixtures, journal roots, verification commands, and public contract schemas. | Open source |
+| ZERO CLI | Rust CLI/TUI for setup, diagnostics, state inspection, replay, read-only Runtime control packets, and supervised local actions. | Open source |
+| ZERO Evolution | Local memory, genesis proposals, research reports, decision-stack review, guardian review, red-team, paper canaries, calibration, promotion plans, local apply receipts, rollback receipts, and evolve loops that let ZERO improve under review. | Open where secret-free and human-reviewed |
 
 ## Capability Boundary
 
 | Capability | Public repo state |
 | --- | --- |
-| Paper engine | Runnable now with deterministic fixtures, local API, CLI, Docker, and Railway paths. |
+| Paper Runtime | Runnable now with deterministic fixtures, local API, CLI, Docker, and Railway paths. |
 | Live market data | Runnable now through read-only Hyperliquid public info calls when enabled. |
 | Live readiness | Runnable now as local preflight, cockpit, certification, reconciliation, immune, receipt, evidence, and canary-policy contracts. |
 | Live execution | Private operator deployments have live Hyperliquid execution evidence represented by the redacted public packet. New live capital remains operator-owned, self-custodial, and gated by local custody, preflight, journal, kill-switch, reconciliation, and canary policy. |
 | Self-evolution | Local memory, genesis proposal core, research command chain, decision-stack lenses/layers/modifiers, production-parity OODA reporting, and paper-first evolve gates exist now with redacted extraction, append-only journals, guardian classification, hunt/edge/convergence/thesis/score/meta/sharpen reports, public evaluation surfaces, live-shadow fail-closed parity, red-team review, sandbox candidate mutation, paper canary, calibration, promotion plan, rollback plan, promotion verification, explicit local apply, rollback receipts, API readouts, and expanded read-only MCP snapshots for runtime status, parity, health, journal, rejection audit, memory stats, immune state, backtest summary, evidence bundle, and safety catalog. Protected live-code evolution remains human-reviewed. |
-| Public proof | Runnable now through deterministic demo proof packs, redacted Network contracts, deterministic Network proof packs, `zero.live_trading_evidence.v1`, canary bundles, exchange-evidence normalization, recursive checksums, and operator report verification. |
-| Intelligence API | Contracted now as ZERO Intelligence; growth-mode realtime access is free to increase operator density. Future commercial work is higher scale, retention, redistribution, managed persistence, warehouse history, and SLAs. |
+| Public Proof | Runnable now through deterministic demo proof packs, redacted contracts, `zero.live_trading_evidence.v1`, canary bundles, exchange-evidence normalization, recursive checksums, and operator report verification. |
+| Developers | Public docs start at [getzero.dev/developers](https://getzero.dev/developers); Proof starts at [getzero.dev/proof](https://getzero.dev/proof). |
 
 ```mermaid
 flowchart LR
   A["Market data and strategy inputs"] --> B["ZERO Runtime"]
   B --> C["Safety gates and risk policy"]
   C --> D["Paper or self-custodial live execution"]
-  B --> E["ZERO Terminal"]
+  B --> E["ZERO CLI"]
   B --> F["Audit journal"]
-  F --> G["ZERO Network proof"]
-  G --> H["ZERO Intelligence"]
+  F --> G["ZERO Proof"]
+  G --> H["Public verification"]
 ```
 
 ## What You Can Run Today
@@ -202,8 +208,9 @@ flowchart LR
 - Query Hyperliquid read-only market data without exposing funds.
 - Exercise live-readiness, immune, reconciliation, and certification contracts
   without placing capital at risk.
-- Keep the full-screen terminal cockpit open with Ctrl+5 or `/cockpit-mode`
-  while the read-only `/live/cockpit` packet is polled from the engine.
+- Keep the full-screen Runtime control packet open with Ctrl+5 or
+  `/cockpit-mode` while the read-only `/live/cockpit` packet is polled from the
+  Runtime.
 - Inspect public-safe local live execution receipts from the operator CLI,
   including accepted/refused/exchange-error counts and hash-only receipt proof.
 - Capture signed, public-safe live evidence packets for supervised canary
@@ -223,12 +230,11 @@ flowchart LR
   verify it against ZERO live receipts without exposing raw venue payloads.
 - Run and verify a one-command live canary operator workflow that collects,
   attaches, verifies, checksums, and reports public-safe evidence.
-- Capture a read-only live cockpit drill bundle for preflight, immune,
+- Capture a read-only Runtime control drill bundle for preflight, immune,
   reconciliation, certification, receipt, evidence, metrics, and audit packets.
 - Package release assets with checksums.
 - Deploy the paper runtime on Railway or Docker.
-- Generate public-safe Network index, profile pages, leaderboard pages, and
-  Intelligence contract artifacts.
+- Generate public-safe Proof profile, replay, and contract artifacts.
 
 The self-evolving loop that makes ZERO a complete autonomous operating system
 is now implemented as a public-safe control plane: local memory, genesis
@@ -246,15 +252,15 @@ exist. Protected live-code evolution remains human-reviewed. See
 ZERO should earn trust through behavior that another engineer can verify:
 
 1. Run paper mode locally or on Railway.
-2. Run `just public-proof` to verify the demo proof pack, Network proof chain,
+2. Run `just public-proof` to verify the demo proof pack, Proof chain,
    redacted live trading evidence, read-only MCP server, and committed MCP
    transcript together.
 3. Verify `docs/proof/network/network-proof-pack.json` against its profile,
    leaderboard, deployment identity, and ingestion artifacts.
 4. Generate a signed journal root from local JSONL streams with
    `zero-journal-root`, attach anchor metadata with `zero-journal-anchor`, and
    export a redacted proof pack with `zero-journal-proof`.
-5. Inspect runtime, risk, live cockpit, immune, account, and reconciliation
+5. Inspect runtime, risk, Runtime control, immune, account, and reconciliation
    packets through the CLI/API.
 6. Rehearse a live canary in fail-closed mode.
 7. Attach public-safe exchange-side evidence when an operator-owned live canary
@@ -359,13 +365,13 @@ $ scripts/live_canary_operator_verify.py artifacts/live-canary-operator/...
 zero live canary operator verify: ok=True checks=... fail=0
 
 $ scripts/live_cockpit_drill.py http://127.0.0.1:8765
-zero live cockpit drill: ok=True ready=False risk_allowed=False fail=0 output=artifacts/live-cockpit-drill/...
+zero Runtime control drill: ok=True ready=False risk_allowed=False fail=0 output=artifacts/live-cockpit-drill/...
 
 $ scripts/live_cockpit_drill_verify.py artifacts/live-cockpit-drill/...
-zero live cockpit drill verify: ok=True checks=... fail=0
+zero Runtime control drill verify: ok=True checks=... fail=0
 
 $ scripts/live_cockpit_drill_tamper_rehearsal.py artifacts/live-cockpit-drill/...
-zero live cockpit drill tamper rehearsal: ok=True checks=3 fail=0
+zero Runtime control drill tamper rehearsal: ok=True checks=3 fail=0
 
 $ curl -fsS http://127.0.0.1:8765/immune
 {"schema_version": "zero.immune.v1", "risk_increasing_allowed": false}
@@ -591,12 +597,12 @@ Good first contribution areas:
 - Strategy plugins that return signals but leave execution and risk checks to
   ZERO.
 - Market data adapters with deterministic tests.
-- ZERO Network index, profile, and leaderboard pages over redacted public
+- Public Proof profiles, replay, and contract examples over redacted public
   contracts.
 - CLI diagnostics and replay views.
 - Safety gate tests.
 - Documentation and runbook improvements.
-- Public Network and Intelligence contract examples.
+- Public Protocol and Proof contract examples.
 
 Before opening a pull request:
 
@@ -670,8 +676,6 @@ Machine-readable entrypoints:
 - [Strategy Plugins](docs/strategy-plugins.md)
 - [Market Data Adapters](docs/market-data-adapters.md)
 - [Hyperliquid Read-only](docs/hyperliquid-readonly.md)
-- [ZERO Network](docs/zero-network.md)
-- [ZERO Intelligence](docs/zero-intelligence.md)
 - [Model Gateway](docs/model-gateway.md)
 - [Production Readiness](docs/production-readiness.md)
 - [QA Onboarding Checklist](docs/qa-onboarding-checklist.md)

docs/architecture.md

@@ -7,7 +7,7 @@ ZERO has five product surfaces:
 
 - ZERO Runtime: local autonomous operations engine with paper mode, safety
   gates, API, journals, and extension contracts.
-- ZERO Terminal: operator CLI for setup, diagnostics, state inspection, replay,
+- ZERO CLI: operator CLI for setup, diagnostics, state inspection, replay,
   and supervised actions.
 - ZERO Evolution: local memory, genesis proposals, research reports, guardian
   review, red-team, paper canaries, calibration, and evolve loops that let the

docs/autonomous-os-plan.md

@@ -48,7 +48,7 @@ ZERO reaches 100/100 when a serious operator can:
 Open:
 
 - ZERO Runtime
-- ZERO Terminal
+- ZERO CLI
 - paper trading
 - venue adapters needed for self-custodial operation
 - local journals and audit exports