Skip to content

public-upgrade.md

Latest commit

 

History

History
190 lines (150 loc) · 7.83 KB

public-upgrade.md

File metadata and controls

190 lines (150 loc) · 7.83 KB

Public Upgrade Plan

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 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;
  • live-capable behavior fails closed until custody, risk, reconciliation, and emergency controls are coherent;
  • 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.
  • Keep the public repo built from a positive allowlist.
  • Keep paper mode as the default first-run path.
  • Keep public examples secret-free and deterministic.
  • Keep live execution self-custodial and explicit.
  • Keep future commercial data products outside this open Runtime/Protocol/Proof repo until they have an explicit public contract boundary.
  • Keep local memory, research, genesis, evolve, guardian review, paper canary, and calibration loops open because they are part of the self-custodial runtime. Local memory is already open in Memory Core, and genesis proposal classification is open in Genesis. Paper-only research is open in Research Command Chain. The lens/layer/modifier decision stack is open in Decision Stack. Production parity OODA reporting is open in Runtime Bus. Paper-only evolve gates plus local sandbox promotion, explicit local apply, and rollback execution are open in Evolve Harness.
  • Do not imply guaranteed returns, hosted custody, or unattended live safety.

Public Launch Surface

Surface Public launch requirement
Runtime Paper engine, local API, durable journal, runtime bus, production-parity OODA reports, strategy runners, safety gates, read-only Hyperliquid data, and live-readiness contracts.
Protocol MCP-compatible schemas, read/compute tools, mandates, evidence bundles, replay frames, audit entries, and permission tiers.
CLI Doctor, status, risk, replay, Runtime control packets, and friction-preserving risk controls.
Evolution Local memory, research command chain, decision-stack review, production-parity OODA reporting, genesis proposal core, paper-first evolve gates, sandbox candidate mutation, promotion plans, explicit local apply, rollback receipts, and promotion verification now exist; protected live-code evolution remains human-reviewed.
Proof Redacted local proof packets, public contract schemas, replay exports, journal roots, and verification fixtures.
Developers Links to getzero.dev/developers and getzero.dev/proof, plus repo-local quickstarts and contribution boundaries.
Contribution Agent guide, scoped backlog, issue forms, PR template, safety review path, and one-command gates.

Upgrade Cycles

Cycle A: Public Truth Pass

Goal: make the public repo impossible to misunderstand.

  • 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 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, stale product framing, and generated binary/runtime files.

Exit gate:

just public-readiness
just docs-check

Cycle B: Real Runtime Publicization

Goal: move the real Runtime capabilities into the public runtime without private state, private deployment topology, or commercial data.

Publicize:

  • OODA loop controller interfaces;
  • strategy/lens runner interfaces;
  • risk and immune gates;
  • live-readiness and reconciliation contracts;
  • hash-only signed live evidence bundles;
  • local journals and runtime bus;
  • Hyperliquid venue adapter interfaces;
  • paper/live separation tests;
  • operator-safe CLI workflows, including friction-gated engine-backed /execute <coin> <buy|sell> <size>.

Keep private:

  • private operator state;
  • production wallets, addresses, keys, journals, and fills;
  • private deployment topology;
  • proprietary datasets, calibrations, and hosted scoring feeds;
  • commercial fleet management, billing, and customer operations.

Exit gate:

just ci
just public-readiness

Current progress: /live/evidence now packages preflight, cockpit, live execution receipts, reconciliation, immune, certification, audit, deployment claim, and deployment heartbeat hashes into zero.live_evidence.v1, with optional local HMAC-SHA256 signing via ZERO_LIVE_EVIDENCE_SIGNING_KEY. The repo also commits zero.live_trading_evidence.v1, a redacted proof bridge generated from private operator Hyperliquid fills, trades, and live decisions. It proves live execution evidence exists without publishing raw venue records, wallet addresses, private journals, or custody material.

Cycle C: Launch Proof

Goal: produce the evidence a serious engineer expects before starring, installing, or contributing.

  • Fresh-clone demo transcript.
  • Fresh source-tree rehearsal in CI, proving the public gates and paper API work outside the maintainer checkout.
  • Published v0.1.1 clean-download release evidence with checksums, executable attestations, release verifier output, and Homebrew formula rendering.
  • Railway paper deployment evidence.
  • Release rehearsal evidence.
  • OpenSSF Scorecard enabled.
  • CodeQL, secret scan, Dependabot, and release attestations green.
  • At least five scoped good first issue candidates in launch issues.
  • At least three help wanted issues for serious contributors in launch issues.

Exit gate:

just release-rehearsal
just draft-release-rehearsal
just release-evidence v0.1.2
just fresh-clone-rehearsal
just public-readiness

Cycle D: Self-Evolution Publicization

Goal: expose the adaptive loop that makes ZERO operating intelligence improve under review, without publishing private operator data or commercial intelligence.

Publicize:

  • memory taxonomy and append-only knowledge extraction, now implemented as the first open component;
  • genesis proposal schema, journal, and guardian policy;
  • research reports for hunt, edge, convergence, thesis, score, meta, and sharpen;
  • builder, red-team, paper canary, calibration, and local promotion gates;
  • expanded read-only MCP/API surfaces for runtime status, health, journal, rejection audit, memory, genesis, research, decision-stack review, evolve gates, immune state, backtest summaries, evidence bundles, and safety classification.

Keep private:

  • private journals, production trades, production wallets, private deployment details, proprietary datasets, and hosted aggregate intelligence.

Exit gate:

just ci
just public-readiness

Launch Score

Use two scores, always:

  • Public repo readiness: how ready this repository is for engineers and contributors.
  • 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 contribution while raw exchange disclosure, external review, and hosted infrastructure remain separate product work.