Skip to content
Documentation
Roadmap

Roadmap

Roadmap

The source of truth for all gPTY features; past, present, and planned.

  • GitHub Issues will be used for user-reported bugs and discussions, not roadmap tracking.
  • Boundary rules and non-goals live in AGENTS.md under “ADE Architecture Boundary”.
  • The roadmap is a queue, not a diary. It is split into one page per release chain, and within a release rows are ordered by priority - the first unchecked row (⬜) of the earliest unfinished release is the immediate next implementation. Ordering is: data-loss and correctness first, then security with a reachable path, then the release’s own features, then robustness and tests, then low-reachability hardening, then polish, then work that can only happen at release time. Rows are never grouped by origin or by which release deferred them (the row text says that where it matters); completed rows stay under their release as the record, and the CHANGELOG carries the user-facing summary. A defect or follow-up found while working a row is added as its own row, in priority position, with enough detail to act on later. The Area column names the part of the project a row targets (TERM, GUI, IPC, CLI, SEC, PLUGIN, WIKI, CONCEPT, MEDIA, AGENT, CORE, BUILD, DOCS, PROJECT). Future holds ideas and evidence-gated work that is not scheduled.

Release chains