Reset public Runtime doctrine

.github/copilot-instructions.md

@@ -3,9 +3,9 @@
 Read and follow `AGENTS.md`; it is the canonical operating guide for coding and
 design agents in this repository.
 
-ZERO is an autonomous operating system for self-custodial onchain operations.
-Keep the public runtime paper-first, local-first, and useful without hosted ZERO
-infrastructure.
+ZERO is the operating intelligence layer between humans and capital. Keep the
+public Runtime, Protocol, and Proof substrate paper-first, local-first, and
+useful without hosted ZERO infrastructure.
 
 When suggesting code:
 

AGENTS.md

@@ -52,7 +52,8 @@ Before editing, read:
 
 ## Product Boundary
 
-ZERO is an autonomous operating system for self-custodial onchain operations.
+ZERO is the operating intelligence layer between humans and capital. This public
+repo is the open Runtime, Protocol, and Proof substrate.
 
 Open runtime work belongs in this repo:
 

README.md

@@ -4,21 +4,24 @@
 [![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)
 
-**Open ZERO Runtime, Protocol, and Proof for self-custodial onchain
+**Open ZERO Runtime, Protocol, and Proof for self-custodial capital
 operations.**
 
-This repository is the open ZERO Runtime, ZERO Protocol, and ZERO Proof
-substrate. 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. It does not host the
+ZERO is the operating intelligence layer between humans and capital. This
+repository is the open substrate beneath that product: runnable Runtime,
+Protocol, and Proof software for engineers and self-custodial operators. 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 executable trust: paper-first execution, safety
+gates, local journals, Hyperliquid read-only/live boundaries, MCP-compatible
+readouts, public proof packets, and verification contracts. It does not host the
 customer app, founder admin, doctrine portal, or internal design system.
 
-> Not another trading bot. ZERO is Runtime plus Proof for autonomous onchain
-> operations that must stay inspectable, interruptible, and self-custodial.
+> Not entry automation, a custody service, or an opaque agent. ZERO is operating
+> intelligence; this repo is the open Runtime, Protocol, and Proof layer that
+> keeps capital operations inspectable, interruptible, and self-custodial.
 
 ![ZERO paper runtime terminal proof](docs/assets/readme-terminal.svg)
 
@@ -109,8 +112,8 @@ service or an unattended live-capital promise.
 
 ## Launch Status
 
-This repository is the open Runtime, Protocol, and Proof engineering home for
-ZERO. It is launch-ready for paper runtime work, operator CLI development,
+This repository is the open ZERO Runtime, ZERO Protocol, and ZERO Proof
+engineering home. 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.
 
@@ -137,7 +140,7 @@ stack asks operators to stitch together dashboards, alerts, exchange tabs,
 copy-trading feeds, scripts, and private spreadsheets, then somehow stay
 disciplined under stress.
 
-ZERO turns that workflow into an explicit operating system:
+ZERO turns that workflow into an explicit operating-intelligence loop:
 
 - A runtime that evaluates, rejects, executes, and records decisions.
 - A CLI and local control packet that keep the operator in control.
@@ -248,15 +251,16 @@ flowchart LR
 - Deploy the paper runtime on Railway or Docker.
 - Generate public-safe Proof profile, replay, and contract artifacts.
 
-The public-safe self-evolution loop is part of the local Runtime: local memory,
-genesis proposal classification, paper-only research, public decision-stack
-review, production-parity OODA reports, sandbox candidate mutation,
-promotion/rollback evidence, explicit local apply, rollback receipts, and
-paper-first evolve gates exist. Protected live-code evolution remains
-human-reviewed. See [Memory Core](docs/memory-core.md),
-[Genesis](docs/genesis.md), [Research Command Chain](docs/research.md),
-[Decision Stack](docs/decision-stack.md), and
-[Evolve Harness](docs/evolve.md).
+The self-evolving loop that makes ZERO adaptive operating intelligence is now
+implemented as a public-safe local Runtime subsystem: local memory, genesis
+proposal classification, paper-only research, public decision-stack review,
+production-parity OODA reports, sandbox candidate mutation, promotion/rollback
+evidence, explicit local apply, rollback receipts, and paper-first evolve gates
+exist. Protected live-code evolution remains human-reviewed. See
+[Memory Core](docs/memory-core.md), [Genesis](docs/genesis.md),
+[Research Command Chain](docs/research.md), [Decision Stack](docs/decision-stack.md),
+[Evolve Harness](docs/evolve.md), and
+[Private Engine Capability Gap Audit](docs/private-engine-capability-gap-audit.md).
 
 ## Operator Proof Path
 

contracts/distribution/mcp-registry.json

@@ -57,7 +57,7 @@
         ]
       }
     },
-    "description": "Read-only MCP inspection for ZERO paper autonomous onchain operations.",
+    "description": "Read-only MCP inspection for the open ZERO Runtime, Protocol, and Proof substrate.",
     "name": "io.github.zero-intel/zero",
     "packages": [
       {

docs/agent-architecture.md

@@ -1,8 +1,8 @@
 # Agent Architecture
 
-ZERO is an autonomous operating system for self-custodial onchain operations.
-This document defines what the agentic loop can do, what it cannot do, and
-where humans remain mandatory.
+ZERO is the operating intelligence layer between humans and capital. This
+document defines what the public-runtime agentic loop can do, what it cannot do,
+and where humans remain mandatory.
 
 ## Authority Model
 

docs/architecture.md

@@ -1,13 +1,13 @@
 # Architecture
 
-ZERO is an autonomous operating system for self-custodial onchain operations,
-starting with onchain perpetual markets.
+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.
+  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.
@@ -22,9 +22,10 @@ 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-first, 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.
+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
 
@@ -86,4 +87,5 @@ Runtime behavior -> opt-in verification -> ZERO Proof -> commercial data product
 
 The commercial product is advantaged access to verified autonomous behavior at
 speed, scale, and history. Basic runtime use, self-custody, public profiles,
-and public proof contracts remain open.
+public leaderboards, delayed public intelligence snapshots, and public proof
+contracts remain open.

docs/launch-scorecard.md

@@ -1,24 +1,24 @@
 # Launch Scorecard
 
-This scorecard keeps the public repo honest before launch. It separates what is
-ready for open-source contributors from what is paper-only or intentionally
-reserved for ZERO Intelligence.
+This scorecard keeps the public repo honest before launch. It scores only the
+open ZERO Runtime, Protocol, and Proof substrate. It does not score the hosted
+retail product, production wallets, raw exchange records, or commercial
+Intelligence service operation.
 
 ## Current Launch Repository Score
 
 **100/100**
 
-## Current Autonomous Trust Score
+## Current Operating-Intelligence Trust Score
 
 **100/100**
 
-The launch repository is ready for serious contributors. The stricter
-autonomous-systems trust bar now has the public MCP server listed after
-`zero-engine` PyPI publication. Journal-head anchor
-packets now have a periodic operation that attaches trusted external receipts,
-fails closed when live evidence requires a receipt, and verifies cadence state.
-Bounded property-based coverage exists for the core safety gates and documented
-malformed-input paths.
+The launch repository is ready for serious contributors when the public
+readiness gate passes with current doctrine. ZERO product truth is explicit:
+ZERO is the operating intelligence layer between humans and capital; this public
+repo is the open Runtime, Protocol, and Proof substrate. The stricter trust bar
+requires runnable software, redacted evidence, clear custody boundaries, and
+gates that reject stale category claims.
 
 ## Ready
 
@@ -75,8 +75,9 @@ malformed-input paths.
 - MCP Registry publication workflow with GitHub OIDC and live listing verifier
 - Package dry-run gate for Python artifacts and the Rust crate graph
 - Shared paper API contract fixtures pinned by Python API tests and Rust client tests
-- First-class GitHub product page with category narrative, above-the-fold
-  terminal proof artifact, quickstart, safety model, open-core boundary,
+- First-class GitHub product page with operating-intelligence narrative,
+  above-the-fold terminal proof artifact, quickstart, safety model,
+  open-core boundary,
   live-operation boundary, capability boundary, operator proof path, and
   contributor paths
 - First-10-minutes guide and reproducible terminal demo capture for source and