Defence supply-chain analysis
Try the workflow with your team.
Four roles. One verification. Nothing real.
Synthetic exercise
A gallium delay is reported. What should your team verify?
An exercise hypothesis, not a live alert. Invented platforms and parts; no company BOM needed.
Explain the dependency
Step 1 of 4 · Analyst
Open the sample, run the analysis, and reveal one captured chain from platform to material.
CheckName the platform, component and material from a stored row, and say why this is synthetic evidence, not a real BOM.
Before you start
Analysis needs a running graph service. Saving and role handoffs need configured SSO; the local rehearsal uses fixed synthetic accounts and does not validate your identity provider. This guide does not track case state or certify completion. Confirm each result in the saved case and audit.
Do not enter real programme details, supplier relationships, files, credentials or buyer evidence. Private access, hosting, retention, export controls and data transfer are agreed first.
Stress-test checklist: try to break the assumptions
Use synthetic records in a disposable environment. These are checks to perform, not claimed results.
- Can an analyst explain the chain and its limits without reading Cypher?
- Can a reviewer reach the exact stored row behind a claim?
- Are wrong-role actions disabled or refused?
- Does a failed graph request keep the existing capture?
- Does a second decision conflict instead of overwriting the first?
- Does a linked revision start pending and keep its parent finding?
Would this fit your team's process?
Agree who owns the disruption question, who may approve verification, what reference evidence to compare, and what makes a finding acceptable. Measure time and interpretation errors against your current process before setting a target.