TZUR Impact — Synthetic Demonstration Guide

1. Choose network exposure, identity boundary or evidence visibility. All entities and sources are fictional.
2. Inspect before/after: HTTPS source range expands; federation trust metadata changes; or an application audit stream becomes unavailable.
3. Run analysis. The guided demo calls the same /api/analyze deterministic service as the workspace. An unavailable API is reported as an error, not substituted with fabricated results.
4. Inspect dependency paths, connected systems, mission relationships and supplied owner mappings. Missing mappings cannot be inferred.
5. Examine mapped controls and baseline/current evidence deltas. A mapping or flag does not prove a failed control, incident or outage.
6. Inspect normalized source evidence, graph/input/evidence hashes and export JSON.
7. Open /workspace to inspect model assumptions, add local review notes, save on this device and download an evidence pack. Reviewer priority adjustments remain separate from model output. Optional server cases require authentication. Human review does not authorize deployment.
8. Restart to compare another fictional change.
Timing: no measured customer latency or investigation-time reduction is established. The interface runs an analysis on request; setup and real-world review depend on data and scope.
Do not submit CUI, classified data, credentials or real operational configurations.