How does the human Observatory experience relate to the evidence runtime?

Protocol Observatory is the public inspection and longitudinal-evidence station inside the one SaSame MCP Factory. The Knowledge Platform owns the human-facing overview, server directory, bounded observation details, methodology and State of MCP report. The existing live-vps.sasame.online/observatory/* runtime owns signed evidence, readiness indexes, feeds, badges, certificates, claims and lookup endpoints. This separation avoids a second product identity while keeping externally cited machine URLs stable.

Use Observatory for the station overview, Server directory to search current observations, Methodology for measurement boundaries and State of MCP for the current declared-tool-surface report. These routes share the same SaSame navigation, design, SEO/AEO and accessibility system as the rest of the Knowledge Platform.

Raw JSON, Atom feeds, badges, certificates, claim receipts, lookup and other machine contracts remain on the stable live-vps Observatory origin. They are not replaced by human HTML redirects. A route migration map classifies old HTML pages separately from machine-preserved endpoints, and no redirect is activated before the final #2121 production cutover gate and rollback proof.

Observed means a dated outside-in measurement exists. Claimed means an operator completed a control-proof challenge. Certified is a higher bounded evidence state and is not implied by observation or claim alone. A claim proves control of an endpoint or record only; it is not KYC, legal identity verification, endorsement or a safety verdict.

The station measures externally observable protocol behavior, declared schema and annotation completeness, control-proof records and longitudinal change. It does not certify security, malware absence, tool-output correctness, vendor quality or suitability. Unknown remains unknown, and unavailable live data is omitted rather than replaced with fabricated values.