Compatibility Evidence
What does MCP compatibility evidence mean?
It means a stated client or protocol check passed or failed under a defined method at a defined time.
Search the graph
Find current SaSame knowledge.
Current company, Factory, documentation, research, evidence, product and API records are searched by default. Historical records are available only when you explicitly include them.
Refine
Clear filtersCollections
Include historical recordsHistorical records are visible and explicitly labelled as not current.
Return to current recordsResults
All · #evidence · history included6 knowledge records
Evidence
What does SaSame evidence prove?
Evidence now includes the CP3 receipt chain: Factory Orders executed selected Mission survivors through registered stations and returned inspection/observation receipts without creating payment, demand or North-Star credit.
Incident Reports
What belongs in a SaSame incident report?
An incident report records impact, detection, timeline, affected components, evidence, containment, recovery, verification and unresolved risk.
Mission
What is SaSame trying to accomplish?
SaSame aims to make MCP production and operation reproducible, observable and evidence-backed while creators retain ownership of code, credentials, data rights and support.
Registry and Runtime Evidence
Why are registry and runtime records separate?
A registry record describes a declared identity or capability; runtime evidence records what an endpoint returned when observed.
Mission Control
What does Mission Control manage?
The standalone public Mission Control dashboard is superseded by Observatory. The underlying Mission Control contract still represents deterministic launch/kill/complete transitions, closeout knowledge inheritance, successor Missions and read-only portfolio capacity without turning a killed business shape into a company pivot. Its still-useful public operations evidence now appears inside Observatory; internal Mission Control execution machinery and historical records remain unchanged.