Skip to main content
This directory contains target-family notes that sit below the RFCs and above implementation tasks. They are meant to be edited as research turns into code. Related: Documentation index, RFC 0002, Implementation backlog, Design decisions.

Target Lifecycle

Stage Exit Criteria

  • Research exits only when a target profile draft, required-tool list, and minimal spike acceptance criteria are documented.
  • Spike exits only when a reproducible local command or script exists and the target note records the result.
  • Experimental exits only when SDK/build/smoke coverage exists for a narrow capability set and docs name artifact metadata, CI or optional CI, capability support, and examples.
  • Supported requires stable CLI, artifact metadata, CI, docs, and at least one shared scenario test.
Experimental does not mean “broken” — EVM has CI and Foundry smoke but lacks target registry and portable IR integration.

Portfolio Scheduling Boundary

The table below is an inventory of target notes, not a scheduling authority. The current product implementation backlog is constrained by the primary-chain completion covenant (D-045): finish solana-sbpf-asm, evm, and wasm-near to production-grade quality, in that order, before any additional chain advances beyond docs-only research or frozen spike maintenance. Existing non-primary entries such as psy-dpn, aleo-leo, and wasm-cloudflare-workers may receive CI stability, security, or documentation maintenance, but they must not expand registry stage, capability surface, testkit coverage, or product scope until Gate P0 closes.

Current Target Status

Documents