One project. Four ways to inspect it.
Take a self-guided tour through a real public repository snapshot. Start with the story, follow one requirement and see what the analysis can—and cannot—establish.
The included case study requires no personal repository. Its workspace is read-only and uses captured evidence. Viewing it does not make a model request. This is a self-guided product tour; live booking is not configured.
- 01
Understand the captured project.
Start with the Nano ID story: the review question, immutable source revision and analyst-derived checklist. Its maintainers have not endorsed the study.
What to look forFind the capture date and the limits of the study.Read the case study - 02
Trace a custom-alphabet requirement.
Open NANO-003. Read its acceptance criteria, inspect the customAlphabet source and follow matching named tests. The drawer keeps the score beside its supporting records.
What to look forDistinguish a candidate match from an approved criterion.Open NANO-003 evidence - 03
Inspect CI and the release report.
See why passing recorded CI still leaves this study under review. Use “Export report” in the workspace header to save the requirements, evidence and review reasons.
What to look forKeep commit-level CI separate from individual test outcomes.Open release evidence - 04
Ask for a cited explanation.
In Copilot, ask “What is incomplete for NANO-003?” Then open a citation to inspect the supporting record. Answers use deterministic evidence retrieval in this demo.
What to look forCheck the explanation against the same source snapshot.Open evidence Copilot