platphorm-therapy
Repository identity stays distinct from canonical site identity. This page reports only registry, route eligibility, MCP declaration, storage, and propagation evidence that Trace can support.
Canonical domain: No canonical domain mapping yet.
Route evidence: unknown
Manifest generated: 2026-07-20T19:59:37.259Z
- Register the product's canonical *.platphormnews.com domain in the root network graph.
- Add the canonical sitemap to the base sitemap index when the product is publicly crawlable.
- Implement the standard health, docs, discovery, trust, feed, and sitemap routes around the product's real purpose.
- Accept and propagate W3C and PlatPhorm trace headers, then ingest authenticated public-safe spans into Trace.
Evidence-backed checks
Unknown is not failure, and a declared capability is not counted as observed execution.
Repository identity is present in the refreshable platphorm-* workspace manifest.
Evidence sourceNo graph, sitemap, catalog, or unambiguous alias mapping provides a canonical trusted domain.
Route compliance cannot be tested until the repository has a canonical trusted domain.
Observability compliance cannot be correlated until the repository has a canonical trusted domain.
MCP support is not declared by the canonical registry; this does not imply failure when MCP is not applicable.
Trace storage is degraded or unavailable, so missing span counts are not treated as zero.
Evidence sourcePropagation evidence cannot be confirmed while Trace storage is degraded.