Align public repo with Runtime, Protocol, and Proof boundary

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)

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]

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.

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.