Deployment
How are SaSame components deployed safely?
Deployments bind an immutable source SHA to a component release, health checks, external verification and a rollback target before traffic changes.
Search the graph
Find knowledge, not pages.
Search across questions, summaries, sections, tags and lifecycle states.
Refine
Clear filtersCollections
Relevant record
All · #documentation9 knowledge records
Factory
How does the SaSame MCP Factory lifecycle work?
The Factory connects entry, blueprint, build, inspection, shipment, observation, repair and reverification through one evidence-backed lifecycle.
Guided Build
How does BYO-LLM Guided Build actually work, step by step?
The creator's own LLM does the building from fixed instructions SaSame serves; SaSame runs zero LLM calls and deterministically verifies the artifacts the creator submits back — string/regex/length checks, never a fuzzy AI judgment.
Knowledge Publishing Workflow
How do documents enter the SaSame Knowledge Platform?
Documents enter through reviewed CMS edits, provider-neutral AI drafts or controlled migrations, then pass validation, CAS versioning, Markdown projection and receipt generation before public release.
Monitoring
What does Factory monitoring measure?
Monitoring records time-bounded reachability, protocol behavior, declared capabilities and selected compatibility checks with provenance and history.
Observatory
How does the human Observatory experience relate to the evidence runtime?
The Knowledge Platform is the canonical human interface for the Observatory Factory station, while live-vps preserves signed JSON, feeds, badges, certificates, lookup and longitudinal evidence URLs.
Owner Verification
What does owner verification prove?
Owner verification proves control of a defined MCP identity or related resource through a bounded control-proof method at a stated time.
Reference
Where are exact SaSame schemas and lifecycle states defined?
Reference pages expose versioned schemas, status enums, API contracts, evidence boundaries and release receipt fields used across human and machine interfaces.
Repair and Reverification
When a shipped MCP breaks, what happens and who fixes it?
Observation detects drift and produces a scoped Repair Blueprint with hypotheses, not confirmed causes; the creator always applies the actual fix; SaSame never edits creator code; a successful fix is reverified under the same test contract and automatically reshipped.