What's coming.

A public roadmap and changelog for framework-pack coverage, integrations, and core platform features — transparency here is part of the trust argument this whole section makes.

What the roadmap covers

Three tracks, updated in the open. Framework-pack coverage: which regulations and standards get packs next, and what each pack release changes when a transposition or revision moves. Integrations: which connector categories and specific tools are being built, in what order. Core features: what the platform itself gains — and just as deliberately, what it won't, because a roadmap that only lists additions is a marketing page wearing a roadmap's clothes.

Alongside the forward view sits the changelog: what shipped, when, and what it changed. Releases are dated, entries are specific, and nothing is quietly removed from the record.

Honest status

Community Edition is in its final porting phase; the roadmap publishes with the release, seeded from the work that brought it here. What you read on day one will already show its first slips and reorders — that is what a real roadmap looks like, and the point of publishing it.

If a specific pack or connector is the deciding factor for your adoption, say so through the community channels — the loudest signal in the queue is a named organization waiting on a named artifact, and the roadmap ordering listens.

And the inverse commitment holds too: features that were explored and dropped say so on the record, with the reason. A roadmap you can audit backwards is the only kind worth planning forwards against.