Once you have successfully followed the Local Demo Runbook, you can use this checklist to experience the audited traceability workflow as a reviewer.
Select Scenario A (WAITING_FOR_REVIEW) from the Analysis list.
- The Analysis Workspace opens without errors.
- The raw requirement text ("When a booking is cancelled after payment...") is visible.
- Three impacted backend artifacts are listed:
BookingService,RefundController, andInventoryService. - "Review Progress" shows 0/3 (or similar incomplete state).
- Click on an impacted artifact (e.g.,
BookingService). - The Evidence Inspector opens.
- The Evidence Quality Table displays the exact synthetic code excerpt proving the impact (e.g.,
booking.service.ts: L45-60).
- Navigate to the Review Decisions panel.
- Set
BookingServiceto ACCEPTED. - Set
RefundControllerto ACCEPTED. - Set
InventoryServiceto NEEDS_MORE_EVIDENCE (or explicitly ACCEPTED). - Confirm the progress bar advances.
- Open the Final Review Gate panel.
- Confirm that if there are any
NEEDS_REVIEWlinks left, the "Take Snapshot" and "Download .md" buttons are appropriately blocked or disabled.
- Once all links have decisions, click Take Snapshot.
- A success message should appear.
- The Final Review Gate should now show 100% complete and unlock the export options.
Select Scenario B (COMPLETED) from the Analysis list.
- The Final Review Gate is fully unblocked (100% complete).
- Click View Final Reviewed Report.
- A read-only Markdown viewer appears.
- The Markdown content strictly reflects the locked snapshot decisions (e.g., 2 ACCEPTED, 1 REJECTED).
- Click Download .md.
- Your browser downloads a markdown file named similarly to
final-reviewed-report-<id>-<snapshot>.md. - Open the file locally to confirm the synthetic payload is preserved deterministically offline.