Released AI impact assessment
I released the platform's second capability, which shows which requirements a change touches so teams re-verify only what changed.
- Without it
- Teams would re-verify every requirement each release, whatever had changed.
- The call
- Build each capability on the same trace graph, one release at a time.
- What I did
- Shipped impact assessment as the second release, then built the third release on top of it.
- What changed
- Teams could see which requirements a change touched before deciding what to re-verify.