Roadmap #

This roadmap is a direction, not a promise. Each milestone is a vertical slice that ends in verified evidence; a feature is not complete because a command succeeded. Items are recorded here instead of being partially implemented in the core. The authoritative product decision is DEVELOPER_PLATFORM_VISION.md.

Done #

These slices are implemented and, where noted, physically accepted. The run records are preserved in acceptance history.

CLI-driven development core: build, artifact validation, mailbox events, and immutable evidence for fake, VICE 3.8, and one identity-pinned C64 Ultimate.
Cooperative crash, stopped-heartbeat hang, and advancing-heartbeat timeout classification with bounded crash-state evidence.
Opt-in UTX2 exact-site resolution with verified source provenance.
Screen-observation onboarding for existing projects, including a manifest- declared REU image contract.
Symbol resolution, build budgets, and run comparison.
Diagnostic reports (runs report / runs report-items) and the read-only integrity verifier.
Productized 6510 debug-stream capture and the source-linked timeline.
Trusted volatile U64-II RISC-V path with launch intents, exact stock recovery, and the shared experimental runtime.

Next checkpoint: the frozen-memory checkpoint fixture #

Manifest schema 11 and run schema 13 support the bounded memory_checkpoint_capture contract (frozen_post_terminal_v1). Typed raw proof, comparisons, durable pair records and client views are implemented; compatibility and fail-stop gate behavior remain under implementation review.
The reviewed checkpoint fixture (fixtures/checkpoint-demo) runs through the separate VICE source-execution acceptance scenario. Its physical comparison is pending and not authorized; emulator repeatability is not physical proof. See checkpoint comparison.
Diagnostic reports distinguish verified memory captures from unavailable or invalid attempts; workflow checkpoint prose remains a separate detail section.

Pending release and distribution work #

These depend on human review and are not claimed as complete:

Public release environment. The repository is public; a reviewed release tag, artifact downloads and hosted CI results are separate pending gates.
Isolated release qualification. A local development package passed an offline extracted-source rebuild and a compiler-free Ubuntu runtime test. Those observations qualify only their recorded archive hashes; a changed release candidate must be checked again.
Public pipeline. Public CI, artifact publication, and public hosting are pending human review and a privacy pass over the packaged file set.

Human and media gates #

Checkpoint physical acceptance. Requires a fresh read-only probe and exact separately counted permissions for the corrected comparison and health run. No HDMI/audio/keyboard/raster certification is added by this milestone.
First-use session. A new participant must complete the install, local demo, evidence interpretation and external-project tasks; tutorial tests alone do not prove usability. See preview readiness.
Presentation assets. A reviewed demo video and public screenshots do not exist yet and will be added only when real ones can be committed; the front page carries no placeholder or broken image reference.
Video gate. Any published demo video requires separate review and is not part of the current recorded evidence.

Later candidates #

Kept here rather than implemented early. See ULTIMATE_CAPABILITY_RESEARCH.md for the candidate list and AGENTS.md for scope control. Broad editor integrations, multi-device CI, general remote-console features, and polished dashboards that duplicate unfinished core behavior stay out of the core until they directly support a validated development workflow.