Roadmap

Nothing on this page is written by hand. It is generated from issues labeled roadmap on spotlight-spec and spotlight-tools, refreshed automatically. If an item is here, there is a public thread behind it that anyone can argue with.

That is deliberate, and it is the same argument the rest of this site makes about rules: a roadmap that only exists as prose is a claim; a roadmap that is generated from the work is an artifact. A hand-written roadmap tells you what somebody intends. This one tells you what is actually open, how far the conversation has got, and — once building starts — which pull request did it.

Two rules keep it honest:

1. An item earns its place by being an issue first. No item appears here that does not have a thread where the reasoning is visible and the objections are recorded.
2. One issue, one pull request. When an item moves into development, the pull request that implements it references the issue and only that issue, so the homework behind every roadmap item has provenance you can follow — from the argument, to the decision, to the diff.

How to read it

Label	What it means
roadmap	Proposed for the roadmap. Everything on this page carries it.
roadmap:approved	Approved for inclusion — the item is going to happen, whatever the sequencing.
roadmap:deferred	Considered and parked. Still visible, at the bottom, because a decision not to do something is also a decision.
maturity:raised	Raised. Little or no discussion yet — the cheapest moment to change its direction.
maturity:discussing	Active discussion, no rough consensus.
maturity:consensus	Rough consensus on what to do, not yet specified enough to build.
maturity:ready	Ready to implement. One issue, one pull request.

Maturity is about the conversation, not the code. An item can be ready and untouched, or discussing for months because the decision genuinely is hard. Nothing gets promoted by age.

---

Ready to implement

Specified enough that the next step is a pull request.

Rough consensus

Agreement on what to do. Still needs to be pinned down before anyone builds it.

Under discussion

Genuinely open. This is where arguing is worth the most.

Raised

Newly raised, barely discussed. Easiest to redirect.

---

Getting something onto it

Open an issue on the repository it belongs to — the format, the schema, or the specification on spotlight-spec, the engine, the CLI, or the packaging on spotlight-tools — and say what you want and why. If it belongs on the roadmap it gets labeled, and it shows up here on the next refresh.

Direction is welcome in the issue trackers now. That is a change from how this started: the naming question, the question of where the specification lives, and every other open decision are now issues with labels rather than buried in a single thread, precisely so that each one can be found, cited, and settled on its own terms.

Generated 2026-08-19T13:12:41Z from api-commons/spotlight-spec and api-commons/spotlight-tools.