From 728b94fee492202179dd2e27ccc1b458a24d433c Mon Sep 17 00:00:00 2001 From: Igor Pugachevsky Date: Thu, 21 May 2026 19:03:22 +0700 Subject: [PATCH] Reset public runtime doctrine --- .github/copilot-instructions.md | 6 +- AGENTS.md | 3 +- README.md | 50 ++++---- contracts/distribution/mcp-registry.json | 2 +- docs/agent-architecture.md | 6 +- docs/architecture.md | 16 +-- docs/launch-scorecard.md | 27 ++-- docs/llms-full.txt | 152 ++++++++++++----------- docs/llms.txt | 7 +- docs/open-core-boundary.md | 19 +-- docs/positioning.md | 47 +++---- docs/production-readiness.md | 10 +- docs/public-upgrade.md | 22 ++-- docs/railway-partner.md | 17 +-- docs/railway-template.md | 19 +-- engine/pyproject.toml | 4 +- llms.txt | 7 +- scripts/hardening_gate.sh | 2 +- scripts/mcp_registry_packet.py | 2 +- scripts/public_readiness_gate.sh | 37 +++++- server.json | 2 +- 21 files changed, 258 insertions(+), 199 deletions(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index cccadcd..8a7085b 100644 --- a/.github/copilot-instructions.md +++ b/.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: diff --git a/AGENTS.md b/AGENTS.md index 835cfbb..3547c70 100644 --- a/AGENTS.md +++ b/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: diff --git a/README.md b/README.md index 94e5bb7..47aacb2 100644 --- a/README.md +++ b/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 diff --git a/contracts/distribution/mcp-registry.json b/contracts/distribution/mcp-registry.json index 6c5fd2d..be4a3af 100644 --- a/contracts/distribution/mcp-registry.json +++ b/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": [ { diff --git a/docs/agent-architecture.md b/docs/agent-architecture.md index 60c4a4e..046247e 100644 --- a/docs/agent-architecture.md +++ b/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 diff --git a/docs/architecture.md b/docs/architecture.md index afcb7d7..5e34c34 100644 --- a/docs/architecture.md +++ b/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. diff --git a/docs/launch-scorecard.md b/docs/launch-scorecard.md index 09e697d..5f9bf5e 100644 --- a/docs/launch-scorecard.md +++ b/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 diff --git a/docs/llms-full.txt b/docs/llms-full.txt index 434fb8a..b895a5b 100644 --- a/docs/llms-full.txt +++ b/docs/llms-full.txt @@ -68,21 +68,24 @@ Use this bundle for retrieval and coding agents. It is not evidence of live trad [![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) @@ -173,8 +176,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. @@ -201,7 +204,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. @@ -312,15 +315,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 @@ -826,7 +830,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: @@ -1217,10 +1222,9 @@ Out of scope: ````markdown # ZERO Docs -> ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is the open ZERO Runtime, Protocol, and Proof substrate: -> paper-first, local-first, Apache-2.0, and structured for human and agent -> contributors. +> ZERO is the operating intelligence layer between humans and capital. This +> public repo is the open Runtime, Protocol, and Proof substrate: paper-first, +> local-first, Apache-2.0, and structured for human and agent contributors. ## Start @@ -1786,14 +1790,14 @@ Until those inputs exist, `live_correlation.status` must remain `unavailable`. ````markdown # 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. @@ -1808,9 +1812,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 @@ -1872,7 +1877,8 @@ 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. ```` @@ -1881,9 +1887,9 @@ and public proof contracts remain open. ````markdown # 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 @@ -2254,11 +2260,11 @@ asserts that live mode still refuses by default. ````markdown # Deploy and Host ZERO with Railway -ZERO is an autonomous operating system for self-custodial onchain operations. -This Railway template runs the public paper runtime: live Hyperliquid prices are -read-only, execution is simulated, journals are durable, and live-risk endpoints -fail closed unless an operator-owned local live executor is configured outside -the template. +ZERO is the operating intelligence layer between humans and capital. This +Railway template runs the public paper runtime from the open ZERO Runtime, +Protocol, and Proof substrate: live Hyperliquid prices are read-only, execution +is simulated, journals are durable, and live-risk endpoints fail closed unless +an operator-owned local live executor is configured outside the template. ## About Hosting ZERO @@ -2331,10 +2337,11 @@ recommended H1/H2 structure and should stay in sync with this page. ```md # Deploy and Host ZERO with Railway -ZERO is an autonomous operating system for self-custodial onchain operations. -This template runs the public paper runtime: live Hyperliquid prices are -read-only, execution is simulated, journals persist on a Railway volume, and -live-risk endpoints fail closed by default. +ZERO is the operating intelligence layer between humans and capital. This +template runs the public paper runtime from the open ZERO Runtime, Protocol, and +Proof substrate: live Hyperliquid prices are read-only, execution is simulated, +journals persist on a Railway volume, and live-risk endpoints fail closed by +default. ## About Hosting ZERO @@ -4739,14 +4746,17 @@ YYYY-MM-DD-short-slug.md ````markdown # Open Runtime Boundary -ZERO is an open autonomous operating system plus public Runtime, Protocol, and -Proof contracts. +ZERO is the operating intelligence layer between humans and capital. This public +repository is the open Runtime, Protocol, and Proof substrate beneath the hosted +ZERO product. -This public repository contains the local-first runtime, operator terminal, -public proof contracts, and deployment paths that engineers can run, inspect, -test, and extend locally. Deployment should be Railway-first and -self-custodial: operators own their Railway project, environment variables, -exchange credentials, and runtime state. +This repository contains the local-first runtime, operator terminal, public +proof contracts, MCP readouts, and deployment paths that engineers can run, +inspect, test, and extend locally. Railway is the recommended hosted path, but +it is optional: the public Runtime, Protocol, and Proof substrate remains +paper-first and locally usable without hosted ZERO infrastructure. Operators own +their Railway project, environment variables, exchange credentials, and runtime +state. Hosted ZERO Studio, ZERO Control, ZERO Registry, founder-admin, and doctrine surfaces stay outside this repository. The public repo should remain useful @@ -4758,7 +4768,7 @@ operation. ## Open Source - Local ZERO Runtime -- Paper-trading adapter +- Paper execution adapter - Safety and risk primitives - Operator CLI - Local API contracts @@ -4825,7 +4835,7 @@ repository. It deliberately keeps two scores separate: - **Public repo readiness:** whether the repository is good enough for serious engineers to run, inspect, and contribute to. -- **Full operating-system readiness:** whether ZERO has the runtime contracts, +- **Full operating-intelligence readiness:** whether ZERO has the runtime contracts, operator controls, and evidence paths needed for self-custodial live capital. The public repository is launch-ready for contributors. The private/operator @@ -4839,7 +4849,7 @@ for local wallet control, preflight, kill-switches, reconciliation, and review. | Dimension | Score | Status | |---|---:|---| | Public repo hygiene | 100 | Strong CI, release artifacts, governance, docs, clean boundaries, first-class GitHub product page, first-10-minutes guide, reproducible demo capture, fresh source-tree rehearsal, threat model, incident runbooks, distribution policy, hardening gate, and public-readiness gate. | -| Product narrative | 100 | Clear category around autonomous operating systems for self-custodial onchain operations, with public runtime, terminal, evolution, network, intelligence, live-operation boundary, capability boundary, and operator proof path separated cleanly. | +| Product narrative | 100 | Clear category around ZERO as the operating intelligence layer between humans and capital, with this repository scoped to open Runtime, Protocol, and Proof. Hosted product, live-operation boundary, capability boundary, and operator proof path are separated cleanly. | | CLI readiness | 100 | Mature Rust terminal, doctor, five-mode TUI, full-screen live cockpit, friction gates, tests, release binary path, recovery-aware status output, live-preflight diagnostics, `/live-cockpit`, `/live-certify`, `/live-receipts`, `/live-canary`, `/runtime-parity`, `/immune`, friction-gated `/resume-entries`, friction-gated engine-backed `/execute` with receipt-hash rendering, operator-context audit headers, operator-local runtime partitions, a one-command live canary operator evidence workflow, canary policy renderer, and a verified read-only live cockpit drill bundle exist. Raw canary records remain operator-owned external proof, not a public-runtime CLI gap. | | Engine runtime | 100 | Deterministic paper runtime, bounded OODA cycle records, strategy runner SDK, declarative paper strategies, public lens/layer/modifier decision stack, process-serialized append-only decision journal, durable runtime bus contracts, restart replay, read-only Hyperliquid info adapter, live-mid paper execution, traceable audit export, production-parity OODA reports, disabled live-shadow fail-closed evidence, rejection/execution-quality feedback, live custody preflight, account reconciliation, dry-run live certification, immune breaker packets, live execution receipt packets, maintained live canary rehearsal collector, verifier, exchange-evidence normalizer, live canary policy lifecycle, operator report workflow, operator report verifier, redacted private live evidence packet (`zero.live_trading_evidence.v1`: 30 fills, 437 trades, 188 live decisions), public-safe signed live evidence packets, fail-closed model gateway plumbing, and live-executor interfaces exist. Raw exchange canary proof remains operator-owned external evidence. | | Self-evolution loop | 100 | Local memory, genesis proposal core, paper-only research command chain, public decision-stack review, production-parity OODA reports, and paper-first evolve gates are implemented with typed public-safe entries, append-only JSONL journals, generated `knowledge.md`, `/memory`, `/genesis`, `/research`, `/runtime/parity`, `/decision/stack`, `/evolve`, fixture-backed CLI extraction/classification/research/decision-stack/parity output, guardian sample floors, protected path escalation, hunt/edge/convergence/thesis/score/meta/sharpen reports, lenses/layers/modifiers, red-team review, sandbox candidate mutation, deterministic paper canary, calibration, promotion plan, rollback plan, promotion verification, exact-phrase local apply, apply receipts, rollback receipts, and expanded read-only MCP status/parity/health/journal/rejection/memory/immune/backtest/evidence/safety surfaces. Protected live-code evolution remains human-reviewed by design. | @@ -4865,7 +4875,7 @@ feedback from at least one serious engineer, and optional raw exchange disclosure for parties that need custody proof beyond the public redacted packet. -**Full ZERO operating-system contract readiness: 100/100.** +**Full ZERO operating-intelligence contract readiness: 100/100.** **Autonomous trust readiness: 100/100.** @@ -4900,7 +4910,7 @@ evidence. What it does not include is a hosted custody service or raw exchange records. For the public repo target, ZERO now has the executable contracts expected from -a complete autonomous operating-system launch artifact: paper runtime, +a complete operating-intelligence launch artifact: paper runtime, production-parity OODA proof, live-readiness gates, live-shadow fail-closed evidence, local evolution gates, release evidence, and agentic contribution surfaces. Hosted Network persistence, paid Intelligence billing/warehouse @@ -4950,7 +4960,7 @@ ZERO is 100/100 when a new serious operator can: ## Execution Cycles Forecast after Cycle 46: **0 major public-repo product cycles remain before the -repo can be treated as a complete ZERO autonomous operating-system launch +repo can be treated as a complete ZERO operating-intelligence launch artifact.** External work still includes third-party review, hosted Network, growth-mode Intelligence production deployment, and optional raw exchange disclosure for commercial diligence. @@ -5313,9 +5323,9 @@ This document is the launch control plan for turning the public repository into the open ZERO Runtime, Protocol, and Proof surface. The customer-facing product surface stays on getzero.dev and app.getzero.dev. -ZERO is an autonomous operating system for self-custodial onchain operations. -The public repo must prove that category through runnable software, not -marketing copy. The first public impression should be: +ZERO is the operating intelligence layer between humans and capital. The public +repo must prove its part of that system through runnable software, not marketing +copy. The first public impression should be: - a serious engineer can run paper mode in minutes; - the Runtime, Protocol, CLI, and Proof contracts are real, testable, and inspectable; @@ -5366,14 +5376,15 @@ and verification substrate those products can consume. Goal: make the public repo impossible to misunderstand. -- Root README states the category, current runnable surface, safety defaults, - open-core boundary, and current live-capital limitations. +- Root README states the product truth, repo boundary, current runnable surface, + safety defaults, open-core boundary, and current live-capital limitations. - `docs/production-readiness.md` separates public launch readiness from full - autonomous-capital readiness. + hosted-product and live-capital readiness. - `docs/open-core-boundary.md` defines what stays open and what becomes ZERO Intelligence. - `scripts/public_readiness_gate.sh` rejects cache artifacts, private markers, - private infrastructure, and generated binary/runtime files. + private infrastructure, stale product framing, and generated binary/runtime + files. Exit gate: @@ -5456,8 +5467,9 @@ just public-readiness ### Cycle D: Self-Evolution Publicization -Goal: expose the adaptive loop that makes ZERO a complete autonomous operating -system, without publishing private operator data or commercial intelligence. +Goal: expose the adaptive loop that makes ZERO operating intelligence improve +under review, without publishing private operator data or commercial +intelligence. Publicize: @@ -5489,7 +5501,7 @@ Use two scores, always: - **Public repo readiness:** how ready this repository is for engineers and contributors. -- **Full ZERO operating-system readiness:** how close the public runtime is to +- **Full ZERO operating-intelligence readiness:** how close the public runtime is to the complete autonomous live-capital system. Do not collapse those into one number. A repo can be excellent for public diff --git a/docs/llms.txt b/docs/llms.txt index 88dd137..c912749 100644 --- a/docs/llms.txt +++ b/docs/llms.txt @@ -1,9 +1,8 @@ # ZERO Docs -> ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is the open ZERO Runtime, Protocol, and Proof substrate: -> paper-first, local-first, Apache-2.0, and structured for human and agent -> contributors. +> ZERO is the operating intelligence layer between humans and capital. This +> public repo is the open Runtime, Protocol, and Proof substrate: paper-first, +> local-first, Apache-2.0, and structured for human and agent contributors. ## Start diff --git a/docs/open-core-boundary.md b/docs/open-core-boundary.md index c653ff7..3bd9fca 100644 --- a/docs/open-core-boundary.md +++ b/docs/open-core-boundary.md @@ -1,13 +1,16 @@ # Open Runtime Boundary -ZERO is an open autonomous operating system plus public Runtime, Protocol, and -Proof contracts. +ZERO is the operating intelligence layer between humans and capital. This public +repository is the open Runtime, Protocol, and Proof substrate beneath the hosted +ZERO product. -This public repository contains the local-first runtime, operator terminal, -public proof contracts, and deployment paths that engineers can run, inspect, -test, and extend locally. Deployment should be Railway-first and -self-custodial: operators own their Railway project, environment variables, -exchange credentials, and runtime state. +This repository contains the local-first runtime, operator terminal, public +proof contracts, MCP readouts, and deployment paths that engineers can run, +inspect, test, and extend locally. Railway is the recommended hosted path, but +it is optional: the public Runtime, Protocol, and Proof substrate remains +paper-first and locally usable without hosted ZERO infrastructure. Operators own +their Railway project, environment variables, exchange credentials, and runtime +state. Hosted ZERO Studio, ZERO Control, ZERO Registry, founder-admin, and doctrine surfaces stay outside this repository. The public repo should remain useful @@ -19,7 +22,7 @@ operation. ## Open Source - Local ZERO Runtime -- Paper-trading adapter +- Paper execution adapter - Safety and risk primitives - Operator CLI - Local API contracts diff --git a/docs/positioning.md b/docs/positioning.md index 66c769b..7855792 100644 --- a/docs/positioning.md +++ b/docs/positioning.md @@ -1,24 +1,28 @@ # Positioning -ZERO is the autonomous operating system for self-custodial onchain operations. +ZERO is the operating intelligence layer between humans and capital. -The first wedge is onchain perpetual markets. The broader product is a control -plane for autonomous capital operations: runtime, terminal, safety model, public -proof, and verified intelligence. +The first wedge is onchain perpetual markets. The broader product turns +fragmented capital state, manual monitoring, opaque agents, weak intervention, +and stale proof into an inspectable operating layer: intent, agent network, +capital state, governance, and proof. + +This public repository is not the whole hosted product. It is the open Runtime, +Protocol, and Proof substrate that engineers can run, inspect, verify, and +extend without custody or a hosted ZERO account. ## Category -Autonomous operating system for self-custodial onchain operations. +Operating intelligence for self-custodial capital operations. -This category is broader than "trading bot" and more precise than "AI agent." -It says what ZERO operates, who keeps control, and why the product can expand -from Hyperliquid-first execution into treasury, hedging, multi-venue routing, -and verified intelligence. +This category is broader than execution software and more concrete than a +generic AI agent. It says what ZERO coordinates, who keeps control, and why the +product can expand from Hyperliquid-first execution into treasury, hedging, +multi-venue routing, and verified intelligence. ## One-liner -ZERO makes autonomous onchain operations inspectable, interruptible, and -self-custodial. +ZERO makes capital operations inspectable, interruptible, and self-custodial. ## Narrative @@ -27,11 +31,11 @@ operator failure is not caused by missing another signal; it comes from inconsistent execution, unmanaged risk drift, unclear state, and manual intervention at the wrong time. -ZERO starts from a different premise: autonomous systems need an operating -system, not another alert feed. The runtime evaluates opportunities, rejects weak -actions, records decisions, and enforces safety policy. The terminal gives the -operator state, replay, and supervised control. The network exposes public-safe -proof. The intelligence layer turns verified behavior into a data product. +ZERO starts from a different premise: capital needs operating intelligence, not +another alert feed. The runtime evaluates opportunities, rejects weak actions, +records decisions, and enforces safety policy. The operator surfaces show state, +replay, and supervised intervention. The proof layer exposes public-safe +evidence. The intelligence layer turns verified behavior into a data product. The operator keeps custody. ZERO provides the discipline layer. @@ -81,20 +85,21 @@ subsystem. They are not separate hosted public surfaces. Short GitHub description: ```text -Autonomous operating system for self-custodial onchain operations. +Open ZERO Runtime, Protocol, and Proof for self-custodial capital operations. ``` Extended description: ```text -ZERO is an open-source runtime and operator terminal for autonomous onchain -operations: paper-first execution, safety gates, local journals, public proof, -and Protocol contracts. +ZERO is the operating intelligence layer between humans and capital. This public +repo contains the open Runtime, Protocol, and Proof substrate: paper-first +execution, safety gates, local journals, MCP readouts, public proof packets, and +self-custodial live-operation boundaries. ``` What to avoid: -- "AI trading bot" +- "AI entry bot" - "Guaranteed yield" - "Hosted custody" - "Fully trustless AI trader" diff --git a/docs/production-readiness.md b/docs/production-readiness.md index e857cb6..e951d4b 100644 --- a/docs/production-readiness.md +++ b/docs/production-readiness.md @@ -5,7 +5,7 @@ repository. It deliberately keeps two scores separate: - **Public repo readiness:** whether the repository is good enough for serious engineers to run, inspect, and contribute to. -- **Full operating-system readiness:** whether ZERO has the runtime contracts, +- **Full operating-intelligence readiness:** whether ZERO has the runtime contracts, operator controls, and evidence paths needed for self-custodial live capital. The public repository is launch-ready for contributors. The private/operator @@ -19,7 +19,7 @@ for local wallet control, preflight, kill-switches, reconciliation, and review. | Dimension | Score | Status | |---|---:|---| | Public repo hygiene | 100 | Strong CI, release artifacts, governance, docs, clean boundaries, first-class GitHub product page, first-10-minutes guide, reproducible demo capture, fresh source-tree rehearsal, threat model, incident runbooks, distribution policy, hardening gate, and public-readiness gate. | -| Product narrative | 100 | Clear category around autonomous operating systems for self-custodial onchain operations, with public runtime, terminal, evolution, network, intelligence, live-operation boundary, capability boundary, and operator proof path separated cleanly. | +| Product narrative | 100 | Clear category around ZERO as the operating intelligence layer between humans and capital, with this repository scoped to open Runtime, Protocol, and Proof. Hosted product, live-operation boundary, capability boundary, and operator proof path are separated cleanly. | | CLI readiness | 100 | Mature Rust terminal, doctor, five-mode TUI, full-screen live cockpit, friction gates, tests, release binary path, recovery-aware status output, live-preflight diagnostics, `/live-cockpit`, `/live-certify`, `/live-receipts`, `/live-canary`, `/runtime-parity`, `/immune`, friction-gated `/resume-entries`, friction-gated engine-backed `/execute` with receipt-hash rendering, operator-context audit headers, operator-local runtime partitions, a one-command live canary operator evidence workflow, canary policy renderer, and a verified read-only live cockpit drill bundle exist. Raw canary records remain operator-owned external proof, not a public-runtime CLI gap. | | Engine runtime | 100 | Deterministic paper runtime, bounded OODA cycle records, strategy runner SDK, declarative paper strategies, public lens/layer/modifier decision stack, process-serialized append-only decision journal, durable runtime bus contracts, restart replay, read-only Hyperliquid info adapter, live-mid paper execution, traceable audit export, production-parity OODA reports, disabled live-shadow fail-closed evidence, rejection/execution-quality feedback, live custody preflight, account reconciliation, dry-run live certification, immune breaker packets, live execution receipt packets, maintained live canary rehearsal collector, verifier, exchange-evidence normalizer, live canary policy lifecycle, operator report workflow, operator report verifier, redacted private live evidence packet (`zero.live_trading_evidence.v1`: 30 fills, 437 trades, 188 live decisions), public-safe signed live evidence packets, fail-closed model gateway plumbing, and live-executor interfaces exist. Raw exchange canary proof remains operator-owned external evidence. | | Self-evolution loop | 100 | Local memory, genesis proposal core, paper-only research command chain, public decision-stack review, production-parity OODA reports, and paper-first evolve gates are implemented with typed public-safe entries, append-only JSONL journals, generated `knowledge.md`, `/memory`, `/genesis`, `/research`, `/runtime/parity`, `/decision/stack`, `/evolve`, fixture-backed CLI extraction/classification/research/decision-stack/parity output, guardian sample floors, protected path escalation, hunt/edge/convergence/thesis/score/meta/sharpen reports, lenses/layers/modifiers, red-team review, sandbox candidate mutation, deterministic paper canary, calibration, promotion plan, rollback plan, promotion verification, exact-phrase local apply, apply receipts, rollback receipts, and expanded read-only MCP status/parity/health/journal/rejection/memory/immune/backtest/evidence/safety surfaces. Protected live-code evolution remains human-reviewed by design. | @@ -45,7 +45,7 @@ feedback from at least one serious engineer, and optional raw exchange disclosure for parties that need custody proof beyond the public redacted packet. -**Full ZERO operating-system contract readiness: 100/100.** +**Full ZERO operating-intelligence contract readiness: 100/100.** **Autonomous trust readiness: 100/100.** @@ -80,7 +80,7 @@ evidence. What it does not include is a hosted custody service or raw exchange records. For the public repo target, ZERO now has the executable contracts expected from -a complete autonomous operating-system launch artifact: paper runtime, +a complete operating-intelligence launch artifact: paper runtime, production-parity OODA proof, live-readiness gates, live-shadow fail-closed evidence, local evolution gates, release evidence, and agentic contribution surfaces. Hosted Network persistence, paid Intelligence billing/warehouse @@ -130,7 +130,7 @@ ZERO is 100/100 when a new serious operator can: ## Execution Cycles Forecast after Cycle 46: **0 major public-repo product cycles remain before the -repo can be treated as a complete ZERO autonomous operating-system launch +repo can be treated as a complete ZERO operating-intelligence launch artifact.** External work still includes third-party review, hosted Network, growth-mode Intelligence production deployment, and optional raw exchange disclosure for commercial diligence. diff --git a/docs/public-upgrade.md b/docs/public-upgrade.md index c49806f..bc949dc 100644 --- a/docs/public-upgrade.md +++ b/docs/public-upgrade.md @@ -4,9 +4,9 @@ This document is the launch control plan for turning the public repository into the open ZERO Runtime, Protocol, and Proof surface. The customer-facing product surface stays on getzero.dev and app.getzero.dev. -ZERO is an autonomous operating system for self-custodial onchain operations. -The public repo must prove that category through runnable software, not -marketing copy. The first public impression should be: +ZERO is the operating intelligence layer between humans and capital. The public +repo must prove its part of that system through runnable software, not marketing +copy. The first public impression should be: - a serious engineer can run paper mode in minutes; - the Runtime, Protocol, CLI, and Proof contracts are real, testable, and inspectable; @@ -57,14 +57,15 @@ and verification substrate those products can consume. Goal: make the public repo impossible to misunderstand. -- Root README states the category, current runnable surface, safety defaults, - open-core boundary, and current live-capital limitations. +- Root README states the product truth, repo boundary, current runnable surface, + safety defaults, open-core boundary, and current live-capital limitations. - `docs/production-readiness.md` separates public launch readiness from full - autonomous-capital readiness. + hosted-product and live-capital readiness. - `docs/open-core-boundary.md` defines what stays open and what becomes ZERO Intelligence. - `scripts/public_readiness_gate.sh` rejects cache artifacts, private markers, - private infrastructure, and generated binary/runtime files. + private infrastructure, stale product framing, and generated binary/runtime + files. Exit gate: @@ -147,8 +148,9 @@ just public-readiness ### Cycle D: Self-Evolution Publicization -Goal: expose the adaptive loop that makes ZERO a complete autonomous operating -system, without publishing private operator data or commercial intelligence. +Goal: expose the adaptive loop that makes ZERO operating intelligence improve +under review, without publishing private operator data or commercial +intelligence. Publicize: @@ -180,7 +182,7 @@ Use two scores, always: - **Public repo readiness:** how ready this repository is for engineers and contributors. -- **Full ZERO operating-system readiness:** how close the public runtime is to +- **Full ZERO operating-intelligence readiness:** how close the public runtime is to the complete autonomous live-capital system. Do not collapse those into one number. A repo can be excellent for public diff --git a/docs/railway-partner.md b/docs/railway-partner.md index bd23b64..6827208 100644 --- a/docs/railway-partner.md +++ b/docs/railway-partner.md @@ -25,11 +25,12 @@ stateful, and useful without exchange keys. ## Partner Summary -ZERO is an autonomous operating system for self-custodial onchain operations. -The Railway template deploys the public paper runtime: live Hyperliquid prices -are read-only, execution is simulated, journals persist on a Railway volume, and -live-risk endpoints fail closed unless an operator configures a separate local -live executor outside the template. +ZERO is the operating intelligence layer between humans and capital. The Railway +template deploys the public paper runtime from the open ZERO Runtime, Protocol, +and Proof substrate: live Hyperliquid prices are read-only, execution is +simulated, journals persist on a Railway volume, and live-risk endpoints fail +closed unless an operator configures a separate local live executor outside the +template. The template is useful for operator onboarding, public proof capture, coding agent development, and first-run demos. It does not custody funds, does not @@ -77,9 +78,9 @@ Railway update notifications work for operators. ## Submission Message ```text -ZERO is an open-source autonomous operating system for self-custodial onchain -operations. We want Railway to be the one-click paper-runtime path for new -operators and contributors. +ZERO is the operating intelligence layer between humans and capital. We want +Railway to be the one-click paper-runtime path for new operators and +contributors to the open ZERO Runtime, Protocol, and Proof substrate. The template deploys ZERO Paper Runtime from github.com/zero-intel/zero. It uses Dockerfile build, /health health checks, a /data volume for the append-only diff --git a/docs/railway-template.md b/docs/railway-template.md index 52ce968..07b0421 100644 --- a/docs/railway-template.md +++ b/docs/railway-template.md @@ -1,10 +1,10 @@ # Deploy and Host ZERO with Railway -ZERO is an autonomous operating system for self-custodial onchain operations. -This Railway template runs the public paper runtime: live Hyperliquid prices are -read-only, execution is simulated, journals are durable, and live-risk endpoints -fail closed unless an operator-owned local live executor is configured outside -the template. +ZERO is the operating intelligence layer between humans and capital. This +Railway template runs the public paper runtime from the open ZERO Runtime, +Protocol, and Proof substrate: live Hyperliquid prices are read-only, execution +is simulated, journals are durable, and live-risk endpoints fail closed unless +an operator-owned local live executor is configured outside the template. ## About Hosting ZERO @@ -77,10 +77,11 @@ recommended H1/H2 structure and should stay in sync with this page. ```md # Deploy and Host ZERO with Railway -ZERO is an autonomous operating system for self-custodial onchain operations. -This template runs the public paper runtime: live Hyperliquid prices are -read-only, execution is simulated, journals persist on a Railway volume, and -live-risk endpoints fail closed by default. +ZERO is the operating intelligence layer between humans and capital. This +template runs the public paper runtime from the open ZERO Runtime, Protocol, and +Proof substrate: live Hyperliquid prices are read-only, execution is simulated, +journals persist on a Railway volume, and live-risk endpoints fail closed by +default. ## About Hosting ZERO diff --git a/engine/pyproject.toml b/engine/pyproject.toml index 0a48af9..3246e59 100644 --- a/engine/pyproject.toml +++ b/engine/pyproject.toml @@ -1,7 +1,7 @@ [project] name = "zero-engine" version = "0.1.5" -description = "Paper-first ZERO Runtime for self-custodial onchain operations" +description = "Paper-first runtime for the open ZERO Runtime, Protocol, and Proof substrate" readme = "README.md" requires-python = ">=3.11" license = "Apache-2.0" @@ -9,7 +9,7 @@ authors = [{ name = "ZERO contributors" }] keywords = [ "autonomous-operations", "onchain", - "paper-trading", + "paper-execution", "risk-operations", "zero", ] diff --git a/llms.txt b/llms.txt index 81a1aa8..4d6ef43 100644 --- a/llms.txt +++ b/llms.txt @@ -1,9 +1,8 @@ # ZERO -> ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is the open ZERO Runtime, Protocol, and Proof substrate: -> paper-first, local-first, Apache-2.0, and structured for human and agent -> contributors. +> ZERO is the operating intelligence layer between humans and capital. This +> public repo is the open Runtime, Protocol, and Proof substrate: paper-first, +> local-first, Apache-2.0, and structured for human and agent contributors. ## Docs For Agents diff --git a/scripts/hardening_gate.sh b/scripts/hardening_gate.sh index 021e29d..1c27bce 100755 --- a/scripts/hardening_gate.sh +++ b/scripts/hardening_gate.sh @@ -188,7 +188,7 @@ contains "draft release rehearsal" docs/release.md contains "threat model" docs/production-readiness.md contains "incident runbooks" docs/production-readiness.md contains "Public repo readiness" docs/public-upgrade.md -contains "Full ZERO operating-system readiness" docs/public-upgrade.md +contains "Full ZERO operating-intelligence readiness" docs/public-upgrade.md contains "Private Engine Capability Gap Audit" docs/private-engine-capability-gap-audit.md contains "Cycle 28: Memory Core" docs/private-engine-capability-gap-audit.md contains "Cycle 29: Genesis Proposal Core" docs/private-engine-capability-gap-audit.md diff --git a/scripts/mcp_registry_packet.py b/scripts/mcp_registry_packet.py index 18e2308..68b67be 100755 --- a/scripts/mcp_registry_packet.py +++ b/scripts/mcp_registry_packet.py @@ -55,7 +55,7 @@ def build_server_json() -> dict[str, Any]: ], } }, - "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": SERVER_NAME, "packages": [ { diff --git a/scripts/public_readiness_gate.sh b/scripts/public_readiness_gate.sh index c87f7de..9e1d101 100755 --- a/scripts/public_readiness_gate.sh +++ b/scripts/public_readiness_gate.sh @@ -33,10 +33,21 @@ current_surface_search() { local paths=( README.md AGENTS.md + CLAUDE.md + GEMINI.md + .github/copilot-instructions.md docs/positioning.md docs/open-core-boundary.md + docs/public-upgrade.md + docs/architecture.md + docs/agent-architecture.md + docs/launch-scorecard.md + docs/production-readiness.md + docs/railway-template.md + docs/railway-partner.md docs/llms.txt docs/llms-full.txt + llms.txt ) local existing=() local path @@ -78,6 +89,21 @@ file_contains() { grep -Eq "$pattern" "$path" } +assert_agent_guide_symlink() { + local path="$1" + + if [[ ! -L "$path" ]]; then + echo "expected $path to be a symlink to AGENTS.md" >&2 + status=1 + return + fi + + if [[ "$(readlink "$path")" != "AGENTS.md" ]]; then + echo "expected $path to point to AGENTS.md" >&2 + status=1 + fi +} + echo "-- community health files" required=( README.md @@ -214,7 +240,10 @@ else fi echo "-- public product honesty" -file_contains "Open ZERO Runtime, Protocol, and Proof for self-custodial onchain" README.md +assert_agent_guide_symlink CLAUDE.md +assert_agent_guide_symlink GEMINI.md +file_contains "ZERO is the operating intelligence layer between humans and capital" README.md +file_contains "open Runtime, Protocol, and Proof" README.md file_contains "https://getzero.dev/developers" README.md file_contains "https://getzero.dev/proof" README.md file_contains "open ZERO Runtime, ZERO Protocol, and ZERO Proof" README.md @@ -229,7 +258,7 @@ file_contains "Status: historical publicization roadmap" docs/autonomous-os-plan file_contains "Status: historical extraction audit" docs/private-engine-capability-gap-audit.md file_contains "Runtime Capability Boundary Audit" docs/llms.txt file_contains "paper mode" README.md -if current_surface_search 'public product page|ZERO-hosted control plane|hosted ZERO control plane|The engine is open source'; then +if current_surface_search 'Autonomous Capital OS|Autonomous operating system for self-custodial onchain operations|autonomous operating system for self-custodial onchain operations|autonomous operating systems for self-custodial onchain operations|public product page|ZERO-hosted control plane|hosted ZERO control plane|The engine is open source'; then status=1 else rc=$? @@ -238,8 +267,8 @@ else fi fi file_contains "Self-evolution" docs/private-engine-capability-gap-audit.md -file_contains "Full ZERO operating-system contract readiness: 100/100" docs/production-readiness.md -file_contains "Autonomous trust readiness: 100/100" docs/production-readiness.md +file_contains "Full ZERO operating-intelligence contract readiness: 100/100" docs/production-readiness.md +file_contains "Operating-Intelligence Trust Score" docs/launch-scorecard.md file_contains "Failure Modes Of The Autonomous Loop" docs/failure-modes-autonomous-loop.md file_contains "FM-AUTO-004" docs/failure-modes-autonomous-loop.md file_contains "zero.decision_journal.entry.v1" docs/journal-integrity.md diff --git a/server.json b/server.json index 0bc192d..0dee7f9 100644 --- a/server.json +++ b/server.json @@ -14,7 +14,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": [ {