Module-aware
Changelog
Every entry names the module it affects, how it is classified, and the documentation it changes — so the changelog is a way into the docs rather than a log nobody reads.
Released changes
No published releases
The changelog starts at general availability. There are no entries yet.
We have deliberately not backfilled this page with invented history. A changelog is one of the few surfaces a technical evaluator reads closely, and a fabricated one is worse than an empty one.
Ask what is shipping nowHow entries are written
What each release will carry
The contract every entry follows, published now so you know what to expect.
- Feature
- New capability that was not there before.
- Improvement
- Existing capability made better or faster.
- Fix
- Behaviour corrected to match what was documented.
- Security
- A change with a security consequence, stated plainly.
Modules an entry can name
- Platform
- Command Center
- Virtual Sites
- Detection
- Response
- Live Operations
- ChatVRTK
- AI Intel
- Communication
- Training & Simulation
- Analytics
- Mobile Operations
- Team
Cross-cutting changes are filed under Platform. Anything else names the module it actually affects, so a team can follow only the parts they operate.