diff --git a/README.md b/README.md index 34d0b7d..94e5bb7 100644 --- a/README.md +++ b/README.md @@ -4,16 +4,18 @@ [![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: open ZERO -Runtime, Protocol, and Proof.** - -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 +**Open ZERO Runtime, Protocol, and Proof for self-custodial onchain +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. +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. @@ -83,9 +85,9 @@ 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 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: +Runtime control packet. The `/cockpit-mode` command remains supported, but the +preferred product term is Runtime control packet. In paper/default mode it +should refuse live risk and show the reason: ```text runtime control @@ -148,15 +150,25 @@ ZERO turns that workflow into an explicit operating system: The default mode is paper. Live operation is self-custodial, explicit, and guarded by preflight checks. -## Product Surfaces +## Open Repository Surfaces | 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 Runtime | Python runtime for paper execution, production-parity OODA reports, live-readiness contracts, journals, safety gates, strategy adapters, venue adapter interfaces, CLI/TUI tooling, local evolution gates, and canary evidence. | Open source | | 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 | +| Developers | Repo-local quickstarts, CLI/API docs, examples, release gates, contribution paths, and public education that starts at [getzero.dev/developers](https://getzero.dev/developers). | Open source | + +The ZERO CLI is Runtime tooling, and ZERO Evolution is a local Runtime subsystem +covering 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. They are not separate +hosted public surfaces. + +Hosted ZERO Studio, ZERO Control, and ZERO Registry are product surfaces outside +this repository. This repo supplies their runnable Runtime, Protocol, and Proof +contracts; it should not turn hosted UI, founder-admin, or doctrine machinery +into public repo scope. ## Capability Boundary @@ -236,16 +248,15 @@ flowchart LR - Deploy the paper runtime on Railway or Docker. - 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 -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). +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). ## Operator Proof Path @@ -680,8 +691,8 @@ Machine-readable entrypoints: - [Production Readiness](docs/production-readiness.md) - [QA Onboarding Checklist](docs/qa-onboarding-checklist.md) - [Public Upgrade Plan](docs/public-upgrade.md) -- [Autonomous OS Plan](docs/autonomous-os-plan.md) -- [Capability Gap Audit](docs/private-engine-capability-gap-audit.md) +- [Historical Autonomous OS Plan](docs/autonomous-os-plan.md) +- [Runtime Capability Boundary Audit](docs/private-engine-capability-gap-audit.md) - [Agentic Contribution](docs/agentic-contribution.md) - [Contributor Issue Board](docs/contributor-issue-board.md) - [Launch Scorecard](docs/launch-scorecard.md) diff --git a/cli/Cargo.toml b/cli/Cargo.toml index 15864f2..f385c3d 100644 --- a/cli/Cargo.toml +++ b/cli/Cargo.toml @@ -23,7 +23,7 @@ repository = "https://github.com/zero-intel/zero" homepage = "https://getzero.dev" documentation = "https://github.com/zero-intel/zero/tree/main/docs" authors = ["zero-intel"] -keywords = ["zero", "onchain", "terminal", "automation", "trading"] +keywords = ["zero", "onchain", "terminal", "runtime", "proof"] categories = ["command-line-utilities"] [workspace.dependencies] diff --git a/docs/architecture.md b/docs/architecture.md index 15e5d83..afcb7d7 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -3,19 +3,24 @@ ZERO is an autonomous operating system for self-custodial onchain operations, starting with onchain perpetual markets. -ZERO has five product surfaces: - -- ZERO Runtime: local autonomous operations engine with paper mode, safety - gates, API, journals, and extension contracts. -- 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 - system improve under evidence and review. -- ZERO Network: public profiles, leaderboards, verification badges, and public decision-flow proof. -- ZERO Intelligence: delayed public snapshots plus a commercial API and - subscription layer for realtime intelligence, history, cohorts, webhooks, and - enterprise support. +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. +- 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](https://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-first, Docker-compatible, and local-first. Operators own their deployment project, secrets, exchange credentials, and runtime state. @@ -30,13 +35,13 @@ ZERO does not need a separate hosted deployment product to be credible. - Risk-reducing actions stay fast - Risk-increasing actions require friction -## Public Engine Flow +## Public Runtime Flow ```text JSONL candles -> MarketDataAdapter -> Strategy -> OrderIntent -> PaperEngine -> RiskDecision ``` -Strategies propose. The paper engine decides. This keeps extension work +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: @@ -67,20 +72,18 @@ 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 -[Private Engine Capability Gap Audit](private-engine-capability-gap-audit.md). -Local memory, research, genesis, and evolve belong in open source because they -are part of a self-custodial operator's runtime. Commercial ZERO Intelligence -begins when many verified runtimes opt into aggregate realtime behavior, -cohorts, history, webhooks, redistribution, or operational SLAs. +extraction targets in [Evolve Harness](evolve.md). 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 ```text -Runtime behavior -> opt-in verification -> public network proof -> ZERO Intelligence API +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, and -public leaderboards, and delayed public intelligence snapshots remain public -surfaces. +speed, scale, and history. Basic runtime use, self-custody, public profiles, +and public proof contracts remain open. diff --git a/docs/autonomous-os-plan.md b/docs/autonomous-os-plan.md index 9dbd2df..e52ba36 100644 --- a/docs/autonomous-os-plan.md +++ b/docs/autonomous-os-plan.md @@ -1,5 +1,10 @@ # ZERO Autonomous OS Completion Plan +Status: historical publicization roadmap. The canonical public repo surfaces +are ZERO Runtime, ZERO Protocol, ZERO Proof, and Developers. Hosted Studio, +Control, Registry, founder-admin, and doctrine surfaces live outside this +repository. + This plan defines the path from the current open-source launch repository to a complete ZERO autonomous operating system for self-custodial onchain operations. diff --git a/docs/llms-full.txt b/docs/llms-full.txt index e116ddb..434fb8a 100644 --- a/docs/llms-full.txt +++ b/docs/llms-full.txt @@ -68,16 +68,18 @@ 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) -**Autonomous operating system for self-custodial onchain operations: open ZERO -Runtime, Protocol, and Proof.** - -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 +**Open ZERO Runtime, Protocol, and Proof for self-custodial onchain +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. +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. @@ -147,9 +149,9 @@ 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 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: +Runtime control packet. The `/cockpit-mode` command remains supported, but the +preferred product term is Runtime control packet. In paper/default mode it +should refuse live risk and show the reason: ```text runtime control @@ -212,15 +214,25 @@ ZERO turns that workflow into an explicit operating system: The default mode is paper. Live operation is self-custodial, explicit, and guarded by preflight checks. -## Product Surfaces +## Open Repository Surfaces | 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 Runtime | Python runtime for paper execution, production-parity OODA reports, live-readiness contracts, journals, safety gates, strategy adapters, venue adapter interfaces, CLI/TUI tooling, local evolution gates, and canary evidence. | Open source | | 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 | +| Developers | Repo-local quickstarts, CLI/API docs, examples, release gates, contribution paths, and public education that starts at [getzero.dev/developers](https://getzero.dev/developers). | Open source | + +The ZERO CLI is Runtime tooling, and ZERO Evolution is a local Runtime subsystem +covering 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. They are not separate +hosted public surfaces. + +Hosted ZERO Studio, ZERO Control, and ZERO Registry are product surfaces outside +this repository. This repo supplies their runnable Runtime, Protocol, and Proof +contracts; it should not turn hosted UI, founder-admin, or doctrine machinery +into public repo scope. ## Capability Boundary @@ -300,16 +312,15 @@ flowchart LR - Deploy the paper runtime on Railway or Docker. - 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 -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). +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). ## Operator Proof Path @@ -744,8 +755,8 @@ Machine-readable entrypoints: - [Production Readiness](docs/production-readiness.md) - [QA Onboarding Checklist](docs/qa-onboarding-checklist.md) - [Public Upgrade Plan](docs/public-upgrade.md) -- [Autonomous OS Plan](docs/autonomous-os-plan.md) -- [Capability Gap Audit](docs/private-engine-capability-gap-audit.md) +- [Historical Autonomous OS Plan](docs/autonomous-os-plan.md) +- [Runtime Capability Boundary Audit](docs/private-engine-capability-gap-audit.md) - [Agentic Contribution](docs/agentic-contribution.md) - [Contributor Issue Board](docs/contributor-issue-board.md) - [Launch Scorecard](docs/launch-scorecard.md) @@ -1207,8 +1218,9 @@ Out of scope: # ZERO Docs > ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is paper-first, local-first, Apache-2.0, and structured for -> human and agent contributors. +> 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. ## Start @@ -1225,8 +1237,8 @@ Out of scope: - [Open-Core Boundary](open-core-boundary.md) - [Production Readiness](production-readiness.md) - [Public Upgrade Plan](public-upgrade.md) -- [Autonomous OS Plan](autonomous-os-plan.md) -- [Capability Gap Audit](private-engine-capability-gap-audit.md) +- [Historical Autonomous OS Plan](autonomous-os-plan.md) +- [Runtime Capability Boundary Audit](private-engine-capability-gap-audit.md) - [Roadmap](roadmap.md) ## Build And Run @@ -1777,19 +1789,24 @@ Until those inputs exist, `live_correlation.status` must remain `unavailable`. ZERO is an autonomous operating system for self-custodial onchain operations, starting with onchain perpetual markets. -ZERO has five product surfaces: - -- ZERO Runtime: local autonomous operations engine with paper mode, safety - gates, API, journals, and extension contracts. -- 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 - system improve under evidence and review. -- ZERO Network: public profiles, leaderboards, verification badges, and public decision-flow proof. -- ZERO Intelligence: delayed public snapshots plus a commercial API and - subscription layer for realtime intelligence, history, cohorts, webhooks, and - enterprise support. +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. +- 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](https://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-first, Docker-compatible, and local-first. Operators own their deployment project, secrets, exchange credentials, and runtime state. @@ -1804,13 +1821,13 @@ ZERO does not need a separate hosted deployment product to be credible. - Risk-reducing actions stay fast - Risk-increasing actions require friction -## Public Engine Flow +## Public Runtime Flow ```text JSONL candles -> MarketDataAdapter -> Strategy -> OrderIntent -> PaperEngine -> RiskDecision ``` -Strategies propose. The paper engine decides. This keeps extension work +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: @@ -1841,23 +1858,21 @@ 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 -[Private Engine Capability Gap Audit](private-engine-capability-gap-audit.md). -Local memory, research, genesis, and evolve belong in open source because they -are part of a self-custodial operator's runtime. Commercial ZERO Intelligence -begins when many verified runtimes opt into aggregate realtime behavior, -cohorts, history, webhooks, redistribution, or operational SLAs. +extraction targets in [Evolve Harness](evolve.md). 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 ```text -Runtime behavior -> opt-in verification -> public network proof -> ZERO Intelligence API +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, and -public leaderboards, and delayed public intelligence snapshots remain public -surfaces. +speed, scale, and history. Basic runtime use, self-custody, public profiles, +and public proof contracts remain open. ```` @@ -4724,7 +4739,8 @@ YYYY-MM-DD-short-slug.md ````markdown # Open Runtime Boundary -ZERO is an open autonomous operating system plus growth-mode free intelligence. +ZERO is an open autonomous operating system plus public Runtime, Protocol, and +Proof contracts. This public repository contains the local-first runtime, operator terminal, public proof contracts, and deployment paths that engineers can run, inspect, @@ -4732,10 +4748,12 @@ test, and extend locally. Deployment should be Railway-first and self-custodial: operators own their Railway project, environment variables, exchange credentials, and runtime state. -ZERO Intelligence is currently free for verified operators so ZERO can grow the -operator network and produce better verified behavior. The future commercial -product sells advantaged scale, retention, redistribution, datasets, webhooks, -benchmarks, reliability commitments, and enterprise support. +Hosted ZERO Studio, ZERO Control, ZERO Registry, founder-admin, and doctrine +surfaces stay outside this repository. The public repo should remain useful +without a ZERO-hosted app account. The future commercial product can sell +advantaged scale, retention, redistribution, datasets, webhooks, benchmarks, +reliability commitments, and enterprise support without gating basic runtime +operation. ## Open Source @@ -4750,12 +4768,12 @@ benchmarks, reliability commitments, and enterprise support. - Contributor tests and CI - Documentation needed to understand, build, and modify the runtime -## Growth-Mode Free +## Public Contracts -- Realtime ZERO Intelligence API -- Operator onboarding credits -- Public profiles and leaderboards +- Redacted Proof packets +- Public profile and leaderboard contracts - Delayed public snapshots +- Protocol schemas and read-only MCP surfaces ## Future Commercial @@ -5306,6 +5324,10 @@ marketing copy. The first public impression should be: - the open-core boundary is obvious; - agentic contributors can find safe, scoped work immediately. +Hosted Studio, Control, Registry, founder-admin, and doctrine surfaces are not +public-repo surfaces. This repo owns the open Runtime, Protocol, Proof, CLI, +and verification substrate those products can consume. + ## Non-Negotiables - Do not publish this private monorepo wholesale. @@ -5481,6 +5503,11 @@ infrastructure remain separate product work. ````markdown # ZERO Autonomous OS Completion Plan +Status: historical publicization roadmap. The canonical public repo surfaces +are ZERO Runtime, ZERO Protocol, ZERO Proof, and Developers. Hosted Studio, +Control, Registry, founder-admin, and doctrine surfaces live outside this +repository. + This plan defines the path from the current open-source launch repository to a complete ZERO autonomous operating system for self-custodial onchain operations. @@ -6174,6 +6201,11 @@ external trust. ````markdown # Private Engine Capability Gap Audit +Status: historical extraction audit. Public-facing repo language should treat +this as a Runtime capability-boundary document; internal engine/source names are +preserved here only to explain the extraction path from private implementation +to open Runtime, Protocol, and Proof contracts. + This audit translates ZERO's existing internal engine capabilities into a public-safe extraction plan. It is intentionally capability-level only: it does not publish private deployment topology, private journals, production wallets, diff --git a/docs/llms.txt b/docs/llms.txt index 4d9c468..88dd137 100644 --- a/docs/llms.txt +++ b/docs/llms.txt @@ -1,8 +1,9 @@ # ZERO Docs > ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is paper-first, local-first, Apache-2.0, and structured for -> human and agent contributors. +> 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. ## Start @@ -19,8 +20,8 @@ - [Open-Core Boundary](open-core-boundary.md) - [Production Readiness](production-readiness.md) - [Public Upgrade Plan](public-upgrade.md) -- [Autonomous OS Plan](autonomous-os-plan.md) -- [Capability Gap Audit](private-engine-capability-gap-audit.md) +- [Historical Autonomous OS Plan](autonomous-os-plan.md) +- [Runtime Capability Boundary Audit](private-engine-capability-gap-audit.md) - [Roadmap](roadmap.md) ## Build And Run diff --git a/docs/open-core-boundary.md b/docs/open-core-boundary.md index da4aa95..c653ff7 100644 --- a/docs/open-core-boundary.md +++ b/docs/open-core-boundary.md @@ -1,6 +1,7 @@ # Open Runtime Boundary -ZERO is an open autonomous operating system plus growth-mode free intelligence. +ZERO is an open autonomous operating system plus public Runtime, Protocol, and +Proof contracts. This public repository contains the local-first runtime, operator terminal, public proof contracts, and deployment paths that engineers can run, inspect, @@ -8,10 +9,12 @@ test, and extend locally. Deployment should be Railway-first and self-custodial: operators own their Railway project, environment variables, exchange credentials, and runtime state. -ZERO Intelligence is currently free for verified operators so ZERO can grow the -operator network and produce better verified behavior. The future commercial -product sells advantaged scale, retention, redistribution, datasets, webhooks, -benchmarks, reliability commitments, and enterprise support. +Hosted ZERO Studio, ZERO Control, ZERO Registry, founder-admin, and doctrine +surfaces stay outside this repository. The public repo should remain useful +without a ZERO-hosted app account. The future commercial product can sell +advantaged scale, retention, redistribution, datasets, webhooks, benchmarks, +reliability commitments, and enterprise support without gating basic runtime +operation. ## Open Source @@ -26,12 +29,12 @@ benchmarks, reliability commitments, and enterprise support. - Contributor tests and CI - Documentation needed to understand, build, and modify the runtime -## Growth-Mode Free +## Public Contracts -- Realtime ZERO Intelligence API -- Operator onboarding credits -- Public profiles and leaderboards +- Redacted Proof packets +- Public profile and leaderboard contracts - Delayed public snapshots +- Protocol schemas and read-only MCP surfaces ## Future Commercial diff --git a/docs/positioning.md b/docs/positioning.md index c4db5fb..66c769b 100644 --- a/docs/positioning.md +++ b/docs/positioning.md @@ -54,15 +54,27 @@ Attention-driven onchain infrastructure: - Commercial value based on speed, scale, history, reliability, and verified intelligence. -## Surfaces +## Public Repo Boundary -- ZERO Runtime: the local engine for autonomous operations. -- ZERO CLI: the operator interface for state, diagnostics, replay, and - supervised actions. -- ZERO Network: public profiles, leaderboards, verification badges, and proof - packets. -- ZERO Intelligence: public snapshots plus commercial realtime APIs, history, - cohorts, webhooks, exports, and support. +This repository is the open ZERO Runtime, ZERO Protocol, ZERO Proof, and +Developers substrate. + +Hosted ZERO Studio, ZERO Control, and ZERO Registry are product surfaces outside +this repository; the public repo supplies the software and contracts those +surfaces can consume. + +- ZERO Runtime: the local runtime for autonomous operations, including CLI/TUI + tooling, local memory, genesis, research, paper canaries, and evolution gates. +- ZERO Protocol: MCP-compatible schemas, tool permissions, mandates, replay + frames, evidence bundles, audit entries, and local verification fixtures. +- ZERO Proof: redacted proof packets, replay/export fixtures, journal roots, + verification commands, and public contract schemas. +- Developers: public education starts at + [getzero.dev/developers](https://getzero.dev/developers); repo-local docs stay + focused on running and verifying the open Runtime/Protocol/Proof substrate. + +The ZERO CLI is Runtime tooling, and ZERO Evolution is a local Runtime +subsystem. They are not separate hosted public surfaces. ## Recommended Copy @@ -77,7 +89,7 @@ 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 commercial intelligence contracts. +and Protocol contracts. ``` What to avoid: diff --git a/docs/private-engine-capability-gap-audit.md b/docs/private-engine-capability-gap-audit.md index f0de435..8b0b430 100644 --- a/docs/private-engine-capability-gap-audit.md +++ b/docs/private-engine-capability-gap-audit.md @@ -1,5 +1,10 @@ # Private Engine Capability Gap Audit +Status: historical extraction audit. Public-facing repo language should treat +this as a Runtime capability-boundary document; internal engine/source names are +preserved here only to explain the extraction path from private implementation +to open Runtime, Protocol, and Proof contracts. + This audit translates ZERO's existing internal engine capabilities into a public-safe extraction plan. It is intentionally capability-level only: it does not publish private deployment topology, private journals, production wallets, diff --git a/docs/public-upgrade.md b/docs/public-upgrade.md index e95ea04..c49806f 100644 --- a/docs/public-upgrade.md +++ b/docs/public-upgrade.md @@ -15,6 +15,10 @@ marketing copy. The first public impression should be: - the open-core boundary is obvious; - agentic contributors can find safe, scoped work immediately. +Hosted Studio, Control, Registry, founder-admin, and doctrine surfaces are not +public-repo surfaces. This repo owns the open Runtime, Protocol, Proof, CLI, +and verification substrate those products can consume. + ## Non-Negotiables - Do not publish this private monorepo wholesale. diff --git a/engine/pyproject.toml b/engine/pyproject.toml index db24dd2..0a48af9 100644 --- a/engine/pyproject.toml +++ b/engine/pyproject.toml @@ -1,7 +1,7 @@ [project] name = "zero-engine" version = "0.1.5" -description = "Paper-first runtime for ZERO's self-custodial onchain operations system" +description = "Paper-first ZERO Runtime for self-custodial onchain operations" readme = "README.md" requires-python = ">=3.11" license = "Apache-2.0" diff --git a/llms.txt b/llms.txt index 99ed170..81a1aa8 100644 --- a/llms.txt +++ b/llms.txt @@ -1,8 +1,9 @@ # ZERO > ZERO is an autonomous operating system for self-custodial onchain operations. -> The public repo is paper-first, local-first, Apache-2.0, and structured for -> human and agent contributors. +> 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. ## Docs For Agents diff --git a/scripts/public_readiness_gate.sh b/scripts/public_readiness_gate.sh index 65afd56..c87f7de 100755 --- a/scripts/public_readiness_gate.sh +++ b/scripts/public_readiness_gate.sh @@ -192,6 +192,13 @@ else status=1 fi +echo "-- generated LLM context" +if scripts/generate_llms_full.py --check; then + echo "ok" +else + status=1 +fi + echo "-- review ownership" if scripts/codeowners_check.py; then echo "ok" @@ -207,9 +214,20 @@ else fi echo "-- public product honesty" -file_contains "Autonomous operating system for self-custodial onchain operations" README.md +file_contains "Open ZERO Runtime, Protocol, and Proof for self-custodial onchain" 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 +file_contains "Hosted ZERO Studio, ZERO Control, and ZERO Registry are product surfaces outside" README.md +file_contains "This public repository has four first-class open surfaces" docs/architecture.md +file_contains "ZERO Protocol: MCP-compatible schemas" docs/architecture.md +file_contains "ZERO Proof: redacted proof packets" docs/architecture.md +file_contains "Public Repo Boundary" docs/positioning.md +file_contains "Hosted ZERO Studio, ZERO Control, and ZERO Registry are product" docs/positioning.md +file_contains "Hosted Studio, Control, Registry, founder-admin, and doctrine surfaces are not" docs/public-upgrade.md +file_contains "Status: historical publicization roadmap" docs/autonomous-os-plan.md +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 status=1