Skip to content

Add a public roadmap to 1.0 - #179

Merged
brightbeamarsalan merged 1 commit into
mainfrom
docs/roadmap-to-1.0
Oct 2, 2026
Merged

brightbeamarsalan merged 1 commit into
mainfrom
docs/roadmap-to-1.0

Conversation

@brightbeamarsalan

Copy link
Copy Markdown
Member

What this adds

A public roadmap from 0.2 to 1.0 in ROADMAP.md, with six figures in docs/img/roadmap-*.svg.

  • What 1.0 will promise, and the test that shows each promise holds.
  • The known gaps, each under the milestone that closes it.
  • The milestones in order, each with its goal, its work and the checks that finish it. The milestones carry no dates.
  • How parts of CHAP mature, version numbers, the six tracks of work, how decisions are made, and where CHAP fits beside MCP, A2A, AG-UI and SCITT.
  • Open questions, with the maintainers' current leaning and the milestone that settles each one.

The README links to the roadmap from its stability paragraph, and the changelog lists it under Unreleased.

Around the merge

The roadmap sends readers to GitHub milestones 0.3 to 1.0 and to the labels track:protocol, track:engineering, track:conformance, track:security, track:governance, track:ecosystem and 1.0-blocker. They need to exist when the roadmap goes live.

ROADMAP.md sets out what 1.0 will promise and how each promise is checked, the known gaps grouped by the milestone that closes them, the milestones in order with their finish checks, how parts of CHAP mature, version numbers, the tracks of work, how decisions are made, where CHAP fits and the open questions. Six figures in docs/img/roadmap-*.svg. The README points to it, and the changelog lists it under Unreleased.
@brightbeamarsalan
brightbeamarsalan merged commit 2bf78a2 into main Oct 2, 2026
7 checks passed
@brightbeamarsalan
brightbeamarsalan deleted the docs/roadmap-to-1.0 branch October 2, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant