Roadmap
Milestones M0 to M6, in order, each with the gate that ends it. Every date is a proposal, not a promise, and none is confirmed. Status is as of October 2026.
Milestones
| Milestone | Name and window | What it covers | Exit gate | Status |
|---|---|---|---|---|
| M0 | Foundations Proposed: Now to the end of October 2026 | Reserve the names on package registries and GitHub. Choose the license (proposed: Apache-2.0). Run a trademark search. Close the gaps in the usage record. | Names held, license chosen, usage record complete to date, trademark flags written up. | In progress |
| M1 | Prove the dangerous tiers, fix the confirm gate Proposed: November to December 2026 | Real-hardware runs of the input, media and power tiers on the Comet, each with the operator present. The out-of-band approval step is built and mock-tested. Still open: a demonstration in a real client and the hardware runs. Finish the stale-frame gate. Run the Comet checklist: boot-menu catch over twenty or more runs, typing at short and long lengths, unplug recovery, firmware-update regression. | Checklist lines pass or are published as failures. An MCP session is driven end to end on hardware. A real client run shows a person saw the approval prompt. | In progress |
| M2 | Public preview Proposed: From late November 2026, once the checklist is met | Publish the repository with a security policy, a software bill of materials and signed releases where tooling allows. Input, media and power tiers ship as experimental and off by default. State the confirm-gate weakness on the threat model page. List the MCP server in the official registry. Behaviour-test kvm-pilot and glkvm-mcp read-only and publish what we measured, never their code. | The repository is public. Install from the package index works on a clean machine on Linux, Windows, macOS and Raspberry Pi. The threat model is live. No page uses a held-back word. | Not started |
| M3 | Benchmarks Proposed: January to March next year | A wider OCR and vision bake-off on real boot, BIOS, bootloader, UEFI and installer frames, with frames and scorer published. Stage one of the hardware-in-the-loop benchmark. JUnit or TAP output, a CI example and a target selector. A head-to-head with openQA needles on the install task only. | The stage one pass bar is met or the misses are published. The benchmark page is live. | Not started |
| M4 | More channels and drivers Proposed: As hardware arrives, in parallel with M3 | Serial console, then HID-only input with mandatory live observation. PiKVM and NanoKVM drivers first, JetKVM next. Comet X support only after asking its maker. Camera only after the privacy gates. | Each driver is at rung three or higher of the claim ladder before the supported table says more than Untested. | Not started |
| M5 | Design partners and pilots Proposed: From February next year | Two design partners, offered a free pilot in return for a published record with their consent. A first paid pilot after M1 and M2. | Two published partner records and one invoice or signed paid pilot. | Not started |
| M6 | Governed layer and assurance Proposed: Second half of next year | A per-target layer for policy, audit export and change-ticket approvals, on-premises first. An independent penetration test. A control mapping reviewed by an outside party. An off-host anchor for the audit log. | A pilot customer passes its security review, with the report. | Not started |
Order matters. Hours are working time, set out in the project plan. A milestone is done when its exit gate is met, or when the misses are published. These are goals, described further on where this is going.
Dates we are watching
These are dates on our calendar. They are not applications, and nothing here says we applied, were accepted or will apply.
| Item | Date | Note |
|---|---|---|
| NLnet open call | Third of November 2026 | Watching. The call page states a position on projects made with AI. |
| NSF SBIR Phase I | Fourth of November 2026 and early March next year | Watching. A project pitch invitation comes first. |
| GitHub Secure Open Source Fund | Rolling | Watching. It needs a public project, so after M2. |
| KubeCon Europe call for papers | Closed in October 2026 | Missed. |
| DEF CON | Early August next year | Watching. Call dates not yet posted. |
| Open Source Summit North America | May next year | Watching. Call dates not yet posted. |
| OCP Summit | Early October next year | Watching. It fits M6. |