Atlas Evidence Boundary Review
A public benchmark-style review of whether Atlas-related pages keep observed facts, derived labels, provider gaps, and recommendations separate.
Methodology
Inspect public route metadata, static fallback text, JSON-LD, robots policy, llms.txt, and artifact pages for claim-boundary language and crawlable evidence structure.
Version: 2026-06-26
Inputs
- Canonical routes and aliases in src/seo/routes.ts.
- Visible ledger records in src/content/technicalLedger.ts.
- Proof artifacts in src/content/proofArtifacts.ts.
- robots.txt, llms.txt, sitemap output, and static HTML fallback.
Outputs
- Automated contract checks through npm test.
- Static route output through npm run build.
- Human-readable benchmark page with caveats and related project links.
Caveats
- This review does not verify Google, Bing, ChatGPT, Claude, Perplexity, or DuckDuckGo index coverage.
- This review does not claim ranking lift, AI citations, or public video availability.
- Private client evidence and operator-only Atlas records are intentionally excluded.
Results
| Metric | Value | Method |
|---|---|---|
| Route taxonomy | Project, competition, dataset, video, benchmark, and tag classes are represented by crawlable routes. | Canonical route contract in npm test. |
| Structured data | Project and dataset pages expose JSON-LD appropriate to public evidence. | Schema contract and static build output. |
| Inference safety | Pages include explicit what-to-infer and not-to-infer language where claims could be overstated. | Visible route copy and static fallback content. |
Related pages
- Atlas Crawl Evidence: Project page being reviewed.
- Technical ledger dataset: Downloadable public index used by the review.
- AI-search topic: Source hygiene and retrieval clarity topic page.