Historical synthetic snapshot
Decision Intelligence demo
Explore the real workspace components with fictional evidence. No account, customer records or scan requests.
At this point in the timeline, the newest completed scan has complete coverage. The absent credential is no longer detected; this does not claim an engine-verified fix.
Read the technical guidedemo-orders
CompletedJul 23, 2026, 09:00 AM · 60.0s · whitebox mode
Release decision
2 findings meet the configured fail-on threshold, so this release is blocked.
- Coverage
- Required coverage complete
- Policy
- 2.0.0
- Fails on
- HIGH and above
- Engine
- 3.7.0
- Scanned
- Jul 23, 2026, 09:00 AM
- Decided
- Jul 23, 2026, 09:01 AM(today)
- A newer scan of this target finished on Jul 23, 2026, 10:00 AM without a decision, so this remains the target's latest recorded decision.
- A newer scan of this target is running. This decision stands until that scan records one.
Blocking findings
Next steps
A release decision is a recommendation, not an approval. Your team stays accountable for the release.
Recommended next actions
Ordered by priority. Priority orders the work; it never changes the release decision.
No later completed scan of this target yet, so verification comes from linked issues only.
A newer scan is still running; it is not read as evidence until it completes.
3 active actions; none closed.
- P1: act firstState: RecommendedEvidence: Confirmed shared remediation point
Upgrade demo-package in requirements.txt (installed: 1.0.0)
Linked findings
Steps
- Review each advisoryAdvisories: DEMO-ADVISORY-1, DEMO-ADVISORY-2
- Check whether one version contains the fix for every listed advisory
- Update the lockfile and run the tests
Rank 1 of 3. Priority orders the work and never changes the release decision.
- Blocking findingsCount: 2
- Highest severitySeverity: CRITICAL
- Best confidence bandConfidence band: HIGH
- The release decision is BLOCK
The engine's fix text at scan time
Review each illustrative advisory before choosing an upgrade; no combined fixed version is asserted.
As listed when the scan ran on Jul 23, 2026, 09:00 AM.
For: DEMO-1
Review each illustrative advisory before choosing an upgrade; no combined fixed version is asserted.
As listed when the scan ran on Jul 23, 2026, 09:00 AM.
For: DEMO-2
How to validate the change
- Re-run the scan with the same settingsMode: whitebox
Analyzers: pip
Verification, finding by finding
Illustrative package advisory A
Later scan: No later scanNo tracked issue
Illustrative package advisory B
Later scan: No later scanNo tracked issue
- P2: nextState: RecommendedEvidence: Potential relationship
Investigate the related findings in app/orders.py
Linked findings
Steps
- Inspect the related findings togetherFile: app/orders.py
- Fix each finding on its own unless one change is shown to address several
Rank 2 of 3. Priority orders the work and never changes the release decision.
- Warning findingsCount: 2
- Highest severitySeverity: HIGH
- Best confidence bandConfidence band: MEDIUM
The engine's fix text at scan time
Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.
As listed when the scan ran on Jul 23, 2026, 09:00 AM.
For: DEMO-3
Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.
As listed when the scan ran on Jul 23, 2026, 09:00 AM.
For: DEMO-4
How to validate the change
- Re-run the scan with the same settingsMode: whitebox
What is uncertain
- Separate operations in one function
Analyzers: semgrep
Verification, finding by finding
Unsafe query in export
Later scan: No later scanNo tracked issue
Unsafe command in export
Later scan: No later scanNo tracked issue
- P2: nextState: RecommendedEvidence: One finding
Fix app/search.py line 30
Linked finding
Steps
- Apply the engine's guidanceFile: app/search.py
Rank 3 of 3. Priority orders the work and never changes the release decision.
- Warning findingsCount: 1
- Highest severitySeverity: HIGH
- Best confidence bandConfidence band: MEDIUM
The engine's fix text at scan time
Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.
As listed when the scan ran on Jul 23, 2026, 09:00 AM.
For: DEMO-6
How to validate the change
- Re-run the scan with the same settingsMode: whitebox
Analyzers: semgrep
Verification, finding by finding
New unsafe query in search
Later scan: No later scanNo tracked issue
Recommendations are deterministic and never change the release decision; nothing is changed in your code.
Coverage
5 findings
Each finding has its own decision. The release decision above is made once, for the whole scan.
- Confirmed shared remediation points
- 1 confirmed shared remediation point (2 findings)
- Potentially related groups
- 1 potentially related group (2 findings)
- Independent findings
- 1 independent finding
Confirmed shared remediation points
Direct evidence of a shared remediation point: the same package declaration, or the same operation on one line. It shows where one change would touch every finding in the group; it does not prove they share a cause, and only a later scan shows which findings a change removed. Check each group's limitations.
Potentially related
Proximity only: the evidence does not show that one change addresses them. Confirm before treating them as one fix.
What the evidence does not establish
- Separate operations in one function
Independent finding
No defensible relationship to another finding; each stands on its own.
DEMO-6HIGHFinding decision: WARNWhite-boxNew unsafe query in search
Finding decisionWARNConfidence-gated policy
Confidence: MEDIUM
Evidence
Synthetic evidence for product education; no customer record or credential.
Remediation
Review the illustrated evidence, apply the appropriate change, then re-scan with the same scope.