Roadmap
In order, without dates. Anything that runs today carries a chip on What it does; nothing here runs yet. A date we miss is a claim we broke, so there are none.
In order
- The desk you log into yourself. The queue, accept, edit or spike, and the approval as a recorded state, in a screen of your own. This ships first.
- A searchable spike log. So that "why did we not answer that one?" has an answer six months later.
- Several beats per customer, each with its own desk. A second market, a second product line, a competitor set. Separate queues, one file.
- Scheduled sweeps and a morning brief. The wire sorted before you sit down, with the reason each story is on your beat.
- Liveness monitoring of every archived source. A check that notices a page that changed or disappeared, and hands the decision to a person.
- Signed, timestamp-anchored manifests. So a capture stands up to somebody who does not trust us.
- The archive for your newsroom. Private to your own staff, hashed, and joined to your answers.
- Publishing connectors behind the same gate. Your site, a social schedule, a newsletter. A connector that cannot honour the gate does not ship.
- Editorial roles. Who may draft, who may edit, who may release, per desk.
- More languages. Each written as a twin, never as a translation pass.
- The own-hardware edition as a packaged release. Versioned packages, release notes, rollback, on your machine, operated by ATAILA.
Never on this list: an auto-publish switch
Remove the gate and this is spam, so there is no gate to remove. That is a product decision, and it will not change.