Route Evidence Engine

Prove every public route works.

Discover services, crawl routes, validate sitemaps, check robots, verify feeds, inspect llms, test OpenAPI and MCP, find dead links, publish route evidence, and keep SearchOps, TrustOps, AgentOps, and the root PlatPhorm graph aligned.

Services discovered
365

Source: Root graph + base sitemap

Sitemap entries
363

Source: Base sitemap index

Public contract routes
72

Source: SitemapOps route standard

Operator Actions

Public views are dry-run and source-backed. Full crawls, publishing, persistence, and registry mutation require PLATPHORM_API_KEY.

Source-backed discovery
SitemapOps is the route evidence engine for PlatPhormNews: it validates public routes, sitemaps, robots files, feeds, llms files, OpenAPI specs, MCP manifests, well-known policy files, canonicals, and source packets for SearchOps, TrustOps, AgentOps, and the root graph.
Public/protected boundary
Everything public-safe is readable. Mutations and publishing use the shared platform key only.
PLATPHORM_API_KEY
No fake coverage
Unavailable crawls, publishers, and stores are reported as degraded instead of successful.

How does SitemapOps verify a site?

SitemapOps combines the canonical PlatPhorm network graph with the base sitemap index, then performs bounded, robots-aware checks. It preserves HTTP status, redirects, canonical targets, indexability, lastmod quality, source URLs, and trace identifiers so downstream scanners can audit every conclusion.

  1. Discover trusted services from the canonical network graph.
  2. Compare those services with the base sitemap index and each origin's robots declarations.
  3. Crawl a bounded route sample, classify evidence honestly, and publish source-linked packets for AnswerReady, SearchOps, TrustOps, and AgentOps.
Evidence freshness
Public contracts and methodology last reviewed by the PlatPhorm News publisher.

Updated by Michael Barbine.

Unavailable providers, historical correlation, and protected execution remain explicitly degraded or unknown; SitemapOps never fills those gaps with synthetic success.