ENGINEERING INDEX / ENTRY 04
CASE 04 / VISITOR ROUTE / SOURCE-INSPECTED
A guide should end in a guide.
James chose the roadmap and the beginner-relevant questions from his own stories and case notes. The Twilight Tech front desk can point visitors toward guides and freebies. The Guides page leads to roadmap, cheat-sheet, and homelab routes; those pages contain real download targets.
Can a visitor move from a question to a useful resource without the assistant pretending to be the business?
Where the handoffs happen.
The site keeps navigation deterministic. A lead form attempts a bounded submission, while the PDF remains available if that submission fails. That protects the visitor's access, but a revealed download is not proof that lead capture succeeded.
- 01Visitor question
- 02Guide route
- 03Resource page
- 04PDF link
What the record earns.
Three public resource pages and three PDFs responded successfully in a September 28 route check.
- Observed receipt
- Source inspection found the front-desk Guides route and three downloadable PDFs. On September 28, 2026, GET requests returned HTTP 200 for Guides, the three resource pages, and all three PDF URLs. The three live PDF responses matched the checked local copies by SHA-256. The public links below let a reader inspect the resources. No visitor-download or lead-delivery event was established.
- Source and scope
- Twilight Tech site front-desk routing, resource-page scripts and assets, plus read-only HTTP checks of public routes. This does not establish a J-Bot backend delivery event.
The linked pages and PDF responses were checked with HTTP GET. Open them yourself to inspect the visitor-facing route and downloadable files. The Roadmap PDF still needs a content correction before this case is public-ready.
- Guides, Roadmap, Cheat Sheet, Homelab Starter → HTTP 200 GET (HTML)
- Roadmap, Cheat Sheet, Homelab Starter PDFs → HTTP 200 GET (application/pdf)
- Source
- Public twilighttech.io GET responses; the three PDF bytes match the local Twilight Tech site copies. Front-desk route and resource-page source inspected separately. The deployed HTML revision is not identified by these checks.
- What it does not show
- A reachable file does not establish a completed download or lead submission. The Roadmap is advertised as five pages but the PDF has four physical pages and a placeholder link.
What this does not prove.
The page reveals its download even when lead submission fails. This inspection does not prove conversion, successful lead delivery, or a completed download. The linked Roadmap PDF is four physical pages despite its five-page label and still contains a placeholder link. James's content direction is confirmed from his account; exact implementation attribution and rights to republish each PDF still need review.
Where the work goes next.
Correct the Roadmap PDF and its page-count claim, then run a consented visitor check that records download and submission outcomes separately.