Skip to content

launch-issues.md

Latest commit

 

History

History
305 lines (204 loc) · 11.1 KB

launch-issues.md

File metadata and controls

305 lines (204 loc) · 11.1 KB

Launch Issues

These issues are the source-controlled seed for the public contribution board. They are intentionally small and scoped so a new contributor can land a useful first PR without private context.

The current live board is Contributor Issue Board.

Validate the seed issues locally:

just launch-issue-config-check

Maintainers can create missing GitHub issues after labels are synced:

just github-label-sync
just github-launch-issue-sync

The sync only creates missing issues with exact matching titles. It does not edit existing issues, reopen closed issues, or delete anything.

Good First Issue: Add a paper-only momentum strategy plugin

Labels: good first issue, good-first-strategy, strategy, examples, agent-eligible

GitHub: #18

Status: delivered in Paper Momentum Strategy Plugin.

Add a deterministic paper-only strategy plugin under examples/strategy-plugin/ or a new sibling example. The plugin should be easy for a new engineer to read and must never submit orders directly.

Acceptance:

  • The plugin declares StrategyPluginMetadata with paper_only=true.
  • The plugin returns StrategySignal or None; execution still flows through the paper engine.
  • The example runs without network access, exchange credentials, or live mode.
  • Tests or a smoke command cover one accepted signal and one rejected/no-signal path.

Good First Issue: Add a deterministic market-data adapter fixture

Labels: good first issue, market-data, examples, agent-eligible

GitHub: #19

Status: delivered in Market Data Adapter Example.

Add a market-data adapter example that reads a small local fixture and exposes chronological candles through the public adapter interface.

Acceptance:

  • The adapter declares MarketDataAdapterMetadata.
  • The adapter returns deterministic Candle objects in chronological order.
  • The example requires no secrets, network access, or exchange account.
  • Tests cover unknown symbol, positive limit validation, and latest.

Good First Issue: Add CLI doctor troubleshooting examples

Labels: good first issue, cli, docs, agent-eligible

GitHub: #20

Status: delivered in CLI Doctor Troubleshooting.

Improve the public CLI docs with copy-paste troubleshooting examples for common zero doctor warnings: missing API token, paper API not running, and live preflight refusing closed.

Acceptance:

  • The docs show exact commands and expected safe output snippets.
  • The examples do not imply live trading is ready by default.
  • The first-10-minutes path links to the new troubleshooting section.
  • just docs-check passes.

Good First Issue: Add a stale ZERO Network profile fixture

Labels: good first issue, network, examples, agent-eligible

GitHub: #21

Status: delivered in ZERO Network Stale Profile Fixture.

Add a deterministic public-safe fixture that shows how a ZERO Network profile looks when proof is valid but freshness has expired.

Acceptance:

  • The fixture contains no wallet material, raw trades, private notes, or raw exchange order IDs.
  • The generated page or JSON clearly separates proof validity from freshness.
  • Existing Network smoke tests still pass.
  • The docs explain that stale proof is archive evidence, not active operator status.

Good First Issue: Add proof-pack privacy regression fixtures

Labels: good first issue, proof-pack, security, agent-eligible

GitHub: #22

Status: delivered in Proof Privacy Regression Fixtures.

Add negative fixtures for the proof-pack verifier that demonstrate refusal when public proof artifacts contain private-looking fields.

Acceptance:

  • The negative fixtures are synthetic and contain no real secrets.
  • The verifier rejects at least one wallet-like field and one raw exchange ID field.
  • The docs explain why proof packs are proof-of-process, not custody or PnL proof.
  • just public-proof still passes for committed valid proof packs.

Help Wanted: Expand read-only MCP strategy resources

Labels: help wanted, mcp, docs, agent-eligible

GitHub: #23

Status: delivered in ZERO MCP Server.

Improve the read-only MCP resources so coding agents can discover strategy runner docs, strategy plugin docs, and market-data adapter docs without reading the entire repository.

Acceptance:

  • New resources are read-only and cannot change runtime state.
  • The MCP safety catalog still reports no risk-increasing tools.
  • The transcript fixture is updated and deterministic.
  • PYTHONPATH="$PWD/engine/src" scripts/mcp_transcript.py --check passes.

Help Wanted: Design public Network empty and stale states

Labels: help wanted, network, design, design-review

GitHub: #24

Status: delivered in ZERO Network Empty Profile Fixture, ZERO Network Stale Profile Fixture, and ZERO Network Profile Page Example.

Improve the generated public ZERO Network pages for empty, stale, and active states so viewers can understand what is verified, what is stale, and what is not claimed.

Acceptance:

  • Empty, stale, and active states are visually distinct.
  • Copy never implies PnL, guaranteed returns, hosted custody, or live trading by default.
  • The generated pages remain static, escaped, and public-safe.
  • scripts/network_pages_smoke.py passes.

Help Wanted: Add release evidence reader docs

Labels: help wanted, release, docs, packaging

GitHub: #25

Status: delivered in Release Verification Guide.

Add a short guide that explains how a user verifies a ZERO release from scratch: checksums, GitHub artifact attestations, SBOM/provenance metadata, Homebrew formula checks, and clean-download evidence.

Acceptance:

  • The guide starts from a fresh clone or a downloaded release asset.
  • It includes the exact gh attestation verify and checksum commands.
  • It explains what the Homebrew formula drift check proves.
  • It links to docs/releases/v0.1.1-evidence.md without claiming future releases have already been verified.

Good First Issue: Add a deterministic funding-rate adapter fixture

Labels: good first issue, market-data, examples, agent-eligible

GitHub: #26

Add a deterministic funding-rate market-data fixture under examples/ so contributors can model non-price venue data without using network access, exchange credentials, or live accounts.

Acceptance:

  • The fixture is local and synthetic.
  • The adapter exposes funding-rate rows in chronological order.
  • The example requires no secrets, network access, wallet material, or live mode.
  • Tests or a smoke command cover unknown symbol, positive limit validation, and latest funding lookup.

Good First Issue: Add a paper sizing policy example

Labels: good first issue, strategy, examples, safety, agent-eligible

GitHub: #27

Add a deterministic paper sizing policy example under examples/ that teaches contributors how ZERO sizes proposed paper orders before they reach execution.

Acceptance:

  • The example is paper-only and submits nothing directly.
  • The sizing policy caps notional, handles confidence thresholds, and preserves reduce-only behavior.
  • The example requires no network access, exchange credentials, wallet material, or live mode.
  • Tests or a smoke command cover capped size, rejected low-confidence setup, and reduce-only path.

Good First Issue: Add MCP client setup snippets

Labels: good first issue, mcp, docs, agent-eligible

GitHub: #28

Add short setup snippets showing how a contributor can point local agent tools at ZERO MCP resources without giving the agent mutation or live-trading privileges.

Acceptance:

  • The snippets are read-only and do not include secrets, tokens, wallets, or live execution setup.
  • The docs name the supported ZERO MCP resources a contributor should inspect first.
  • The safety catalog still reports no risk-increasing tools.
  • PYTHONPATH="$PWD/engine/src" scripts/mcp_transcript.py --check passes.

Help Wanted: Add a static ZERO Intelligence catalog page

Labels: help wanted, contracts, design, docs

Status: delivered in examples/intelligence-catalog-page.

GitHub: #29

Add a deterministic static page generated from contracts/intelligence/catalog.json so public readers can inspect the delayed-public and commercial boundary without needing a hosted service.

Acceptance:

  • The page is generated from committed public contracts, not hand-copied data.
  • Copy does not imply hosted realtime availability, guaranteed returns, custody, or live trading by default.
  • The page uses no remote assets, JavaScript, secrets, tokens, wallets, or private records.
  • A smoke check verifies escaping and local links.

Help Wanted: Add Homebrew rollback verification docs

Labels: help wanted, release, docs, packaging

Status: delivered in Release Process and Distribution Readiness.

GitHub: #30

Add a short Homebrew rollback verification section for operators who install ZERO from the public tap and need to return to the previous release.

Acceptance:

  • The docs show exact rollback or reinstall commands for the public tap path.
  • The docs explain what checksum and formula drift checks prove.
  • The docs name the published PyPI zero-engine package and do not claim crates.io or container registry publication.
  • just docs-check and scripts/homebrew_formula_check.py pass.

Completed Maintainer Tasks

These tasks are intentionally not part of the launch issue seed anymore because the public v0.1.1 release already exists and has clean-download evidence:

Completed Contributor Tasks

These tasks are no longer part of the launch issue seed: