Impact Analysis
What the change touches, and how far the effect travels.
- Blast radius built from typed relationships.
- Each impacted object keeps a path back to its source.
- Severity is qualitative and explainable.
Decision Intelligence
A change request becomes a decision you can defend.
Readiness is computed from signals you can inspect, not from a private score. Every impact carries its source, its relationship path and its confidence.
Demo content is synthetic sample data only.
What this covers
Unknowns
What is missing stays visible rather than being averaged away.
- Missing artefacts are listed as unknowns.
- An unknown lowers readiness instead of being ignored.
- Closing an unknown updates the next analysis, not the past one.
Evidence
Every claim points back to the artefact that supports it.
- Provenance to source artefact and source location.
- Evidence chain readable by someone who was not in the room.
- No claim without a trace.
Decision Pack
One document a steering group can actually read.
- Recommendation, conditions and open risks.
- Approvals with separation of duties.
- Exportable and kept as an immutable record.
Synthetic example
Northstar Labs, Project Atlas, Phase 2
- Proposed change: extend the Billing API invoice schema.
- Impacted: Invoice Record, Event Queue, Payment Processor.
- Unknown: the Customer Profile Service contract has no current artefact.
- Outcome: conditional approval, with the missing contract as a blocking condition.