Navigation Claim
TODO:
- [ ] Add page-specific notes for
portfolio-evidence/claims-and-proof/navigation-claim.mdafter inspecting the real project files. - [ ] Cross-link
Navigation Claimto the most relevant code, data, testing, and safety pages. - [ ] Identify the exact claim this page is supposed to support.
- [ ] List the public-facing evidence needed for this claim.
- [ ] Add links to videos, photos, logs, screenshots, or reports that prove the claim.
- [ ] State what a general reader should understand after seeing the evidence.
- [ ] State what a technical reviewer should be able to verify from the evidence.
- [ ] Separate proven results from still-in-progress work.
- [ ] Add dates, model versions, dataset names, and test conditions where relevant.
- [ ] Add limitations so the evidence is honest and not overstated.
- [ ] Pair every claim with concrete evidence and a limitation.
- [ ] Add the fastest way for a skeptical reader to verify the claim.
- [ ] Document graph input, start/goal selection, route output, and segment output.
- [ ] Add a route example showing AI/manual split and handoff behavior.
- [ ] Add the exact source path, artifact path, or hardware component name.