Resources
Roadmap
What we are building now, what is next, and what we are still exploring. Without dates we cannot commit to.
No dates on this page
Not because they are secret. Because a quarter attached to work nobody has committed to is a promise made on your behalf, and it is the thing a roadmap page most often gets wrong.
Work started
2
Dates given
0
Where this list comes from
Every item here is a gap this site already admits somewhere else.
A roadmap is usually a wish list with quarters attached, and both halves are inventions. This one is assembled from the tables elsewhere on this site that name what OpsAI cannot do yet — so nothing on it can be aspirational, because each item is checkable against the page that admits it.
- The integration catalogue
- 4 of 37 targets are not fully available, and each one says so on its own page with what specifically is missing. Check it.
- The control mapping
- 3 obligations are evidenced partially and 1 not at all, stated in the same table as the ones that are. Check it.
- The trust center
- No certifications held, across 5 frameworks, with no audit under way. Check it.
- What this constrains
- Adding an item here requires admitting a gap somewhere a reader can verify. Closing one removes it from this page automatically. Neither is possible to fake.
Started
2
work under way
Not started
2
named, not scheduled
Evidence gaps
4
from the control mapping
Dates on this page
0
deliberately
Work has started
In progress, with the gap named.
These are partially usable today, and each entry says what specifically does not work yet rather than describing the finished state.
- SAPin progress
- Document posting and master-data changes. The action vocabulary is large and being worked through module by module.
- BigQueryin progress
- Reads work today; the residency metadata that a data-protection review asks for is still being wired.
Named, not scheduled
Not started, and on the page anyway.
These are the gaps most worth closing next as far as we can tell. Listing them without a date is the honest version — and it is also what lets somebody tell us we have the order wrong.
- Microsoft Dynamicsnot yet
- Not started. Reachable today only through a generic HTTP connection, which governs the call but not the action semantics.
- Databricksnot yet
- Not started. A notebook that calls a model and writes a table is squarely in scope, and this is the gap most worth closing next.
IllustrativeDerived from the illustrative integration catalogue. Where each target stands.
The harder half
Control obligations the record cannot fully answer.
These are not integration work and some of them are not work at all — one is a record OpsAI has no business holding. They are on the roadmap because a reader planning a compliance programme needs to know which of them might change and which will not.
- Inventory of AI systemspartial
- Completeness cannot be proven, only evidenced. Discovery reads the systems you already run, and it names what each source is blind to.
- Personal data handlingpartial
- Whether consent was validly obtained upstream is not something a control plane can observe. OpsAI evidences what was read and where it went, not the lawful basis for holding it.
- Model provenance and documentationpartial
- Training-data provenance and the accuracy of a provider’s model card are the provider’s to substantiate. OpsAI records what you were told and when, not whether it was true.
- Workforce competence and trainingnone
- This is an HR record. It appears here because a mapping that silently omitted it would be implying coverage OpsAI does not have.
Where to go
If one of these blocks you, that is the most useful thing you can tell us.
The order on this page is a guess. A specific blocker from a specific estate beats a guess, and it is the only input that reliably changes what gets built next.