Roadmap
What is next
Ordered by what is actually being worked on, not by quarter. Each item says why it is on the list, which is the part a roadmap usually leaves out.
No dates on purpose
A roadmap with dates is wrong within a month and then quietly stops being updated, which is less useful than one that is honest about ordering. What shipped, and when, is in the changelog — most recently "Well-Formed, an XML game".Decided, not started
A command-line client
One binary that validates, converts and compares locally, reading the same policy revisions the API does.
Why: Every endpoint now has a tool and a documented shape, which is the prerequisite. A CLI is the form CI actually wants — no key handling in a shell script, no curl and jq to read a verdict — and it can run the WebAssembly engines locally without a request at all.
Shareable results
A link that reopens a tool with the document and options that produced a result.
Why: The tools are stateless, which is the right default and makes a result impossible to send to a colleague. The handoff between tools already carries a document within a tab; this is the same idea pointed outward, and it needs a retention and privacy answer before it can exist.
Still a question
Health pages for the reference corpus
Publish what the nightly crawl already knows about each public source: whether it still parses, when it last changed, and how often it breaks.
Why: The directory is snapshotted daily and only the current state is shown. The history is the interesting part and nobody else has it — but a page asserting that somebody's feed is broken is a claim about their site, and that deserves a deliberate decision rather than a deploy.
Policy sharing and expected artifact paths
Extend private policy revisions with team sharing and expected CI artifact paths.
Why: Immutable revisions provide a repeatable contract; team ownership and path enforcement need their own permission and workflow design.
Quiet windows for monitoring
Add timezone-aware quiet windows to the existing cadence, delivery history and retention controls.
Why: Delivery retries and source cadence now have durable scheduling. Quiet windows should preserve urgent alerts while respecting each team's working hours.
Something you need that is not here? Tell us what breaks for you
Get started
Bring order to the XML your team can't afford to ignore.
Create a free account and get a private workspace to search, validate, diff, and monitor your XML feeds, sitemaps, schemas, and vendor integrations.