V2 Roadmap
Alpha — contract and local control plane
Section titled “Alpha — contract and local control plane”- Runtime Capability Discovery and merge authority
- Single, Phased, and Managed Goal policy
- Explicit Skill Lock and consent semantics
- Phase/Goal state machines and durable event contracts
- Plugin packaging, MCP schemas, local R0
plan_workand status - Sealed subprocess evaluation adapter and reference fixtures
- Inspectable Flight Recorder
Beta 2.0.0-beta.1 — completed
Section titled “Beta 2.0.0-beta.1 — completed”- Published the immutable
v2.0.0-beta.1marketplace snapshot
Beta 2.0.0-beta.2 — completed
Section titled “Beta 2.0.0-beta.2 — completed”- Add Personal and Workspace Routing Profiles with packaged examples
- Close junction, symlink, migration, and evidence-labeling gaps
- Pass Windows, macOS, and Linux CI on the frozen source revision
- Publish the prerelease and move only
latest-v2 - Completed the corrected 36-attempt Behavior smoke with explicit quota authorization
- Reviewed paired results and published only attested, sanitized evidence
- Validated Plugin and Skill-only release-archive contracts on Windows, macOS, and Linux
Beta 2.0.0-beta.3 — completed
Section titled “Beta 2.0.0-beta.3 — completed”- Close the Lighthouse/OpenTelemetry development-tooling advisory with a scoped dependency boundary
- Remove the privileged
workflow_runcheckout from Pages deployment - Bind Pages publication to the validated trusted
mainrevision - Publish a new immutable prerelease and move only
latest-v2
Beta 2.0.0-beta.4 — historical preparation
Section titled “Beta 2.0.0-beta.4 — historical preparation”- Add explainable no-hint classification for Single, Phased, and Managed Goal work
- Add deterministic Profile explain/lint and the Contract 2.3.0 Profile-miss case
- Seal attempt nonce, tool inventory, instruction digest, public case digest, model version, and private scoring-spec digest
- Prepare deterministic Plugin and Skill-only release artifacts locally
- Obtain explicit authorization for the 36-attempt / 42-turn model run
- Review sanitized evidence, attest zero hard violations, and publish the immutable prerelease
The reference-driver validates the offline contract but does not prove real-model behavior. This historical beta.4 preparation is not a published release.
2.0.0 — formal GA candidate
Section titled “2.0.0 — formal GA candidate”- Add the Router-owned Local Work Loop:
get_next_work,record_work_event, andevaluate_gateas boundedconditional-localoperations - Preserve Explicit Skill Lock, scoped consent, Native Goal protection, and fail-closed authority separation
- Add the Host Integration Kit, reference adapter, capability manifest, and cross-platform conformance suite
- Freeze the twenty-task local Pilot protocol, verified-Host lane, and semantic-recommender decision gate
- Prepare the formal GA candidate while keeping
lateston V1.3.1 and publishedlatest-v2on historical beta.3 - Execute and independently review at least 20 real local Pilot tasks
- Complete a real verified-Host Pilot or publish reviewed
capability-unavailableevidence - Obtain explicit authorization before a fresh 36-attempt / 42-turn behavior-model run
- Review sanitized evidence, attest the exact frozen candidate SHA, and qualify the immutable GA release
This checklist records the earlier GA preparation. v2.0.2 has since been published with the bounded evidence in its release attestation. The real local/Host Pilots and newer-model qualification remain separate outstanding work; development-main Memory does not inherit a new qualification. Future publication still needs reviewed source binding.
Remaining formal qualification
Section titled “Remaining formal qualification”- Exercise a verified Host scheduler/evidence integration beyond fixtures
- Pass the 13-case, 78-attempt, 96-model-turn paired Behavior suite
- Maintain zero hard violations
- Complete security review, dependency/SBOM checks, docs parity, and release rehearsal
- Remove reviewed V1 public clutter through the manual manifest gate
- Record the maintainer attestation and promote
latestonly after every required gate passes
Roadmap items are not availability claims. Current readiness remains the generated runtime matrix.