# What's next: the roadmap

runward is a local, open-source CLI that frames agent-generated delivery: the AI harness writes the code, and runward holds a deterministic, zero-LLM, zero-network gate over the decisions and evidence around it. This page answers "what is next" honestly: it points at the records that stay current (the CHANGELOG, the release news, ROADMAP.md) and explains how the roadmap moves — on triggers, with no dates promised, every structural choice traced as an ADR with its rejected alternatives on the record.

This page is deliberately evergreen: it tells you **where the live answers are** and **how the roadmap works**, rather than snapshotting a state that would rot between releases.

## Where to read what shipped

Three surfaces, all tied to the released package — never to this page's memory:

- **[CHANGELOG.md](https://github.com/stranxik/runward/blob/main/CHANGELOG.md)** — the canonical record: every release, newest first, with the ADRs it lands and the alternatives it rejected.
- **[The news section](/news/)** — each release gets an article explaining what changed and why it matters, in plain words.
- **This documentation itself** — the reference pages (the 64 rules, the commands, the ADR journal) are regenerated from the released package on every release, with a fail-loud drift guard: if the docs and the published version ever disagree, the build refuses. What you read here matches what `npx runward` installs.

## How the roadmap works

runward's own decision discipline applies to its roadmap. **No dates are promised; gates are crossed on proof.** Evolution follows evidence: a capability enters the codebase when an objective trigger justifies it, and every structural change lands as a dated ADR with its rejected alternatives on the record — you can audit not just what shipped, but what was declined and why. Recent examples live in the [ADR journal](https://runward.dev/docs/en/reference/adr/) and each release's news article.

## What is ahead

The live list is **[ROADMAP.md](https://github.com/stranxik/runward/blob/main/ROADMAP.md)** in the repository — deliberately short, because shipped work moves to the CHANGELOG and speculative work stays out until it has a trigger. At a glance it tracks: an English pass on the reference floor's documentation, community workflow extensions, more tool profiles (contributions welcome), a legal review of the licence split (tooling MIT, doctrine CC BY-ND), and — someday, as a separate commercial track — certification and training.

If something you need is missing, [open an issue](https://github.com/stranxik/runward/issues): the roadmap moves on real triggers, and a named need is one.

## See also

- [Compliance evidence for the system you deliver](https://runward.dev/docs/en/compliance/evidence/)
- [Adopting runward in a regulated organisation](https://runward.dev/docs/en/compliance/regulated-adoption/)
- [ADRs / decisions](https://runward.dev/docs/en/reference/adr/)
- [Architecture & rationale](https://runward.dev/docs/en/concepts/architecture/)