Deep Engineering Tour

TODO:

• [ ] Add page-specific notes for portfolio-evidence/reader-paths/deep-engineering-tour.md after inspecting the real project files.
• [ ] Cross-link Deep Engineering Tour to 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.
• [ ] Define which readers this path serves: public visitors, builders, technical reviewers, or future collaborators.
• [ ] Keep the checklist focused on fast navigation through proof, not private notes.
• [ ] Add the exact source path, artifact path, or hardware component name.
• [ ] Add the command or procedure needed to reproduce the result.
• [ ] Add expected inputs and outputs.