How should someone contact SaSame?
Structured context helps a question reach the correct Factory station without collecting unnecessary personal data.
- Collection
- company
- Updated
- 2026-07-30
- min read
- 3
- Version
- v1
Use the published company contact path for technical, research, ownership-verification or commercial questions and include the relevant endpoint, repository, DOI or knowledge URL.
Purpose
Structured context helps a question reach the correct Factory station without collecting unnecessary personal data.
Operational model
Technical reports should include reproducible steps and observation time. Ownership questions should use the control-proof flow. Commercial questions should reference a current plan or fulfillment path.
Boundary and limitations
Contact does not create a contract, guarantee a response time or authorize disclosure of credentials and private customer data.
Real public channels
SaSame currently maintains exactly one live social profile and a small set of public source repositories — no other social network profile is currently live, and none should be assumed to exist. X: @SRLsasame. Source: sasame-mcp (main MCP implementation), mcp-readiness (the open-source readiness CLI), sasame-mcp-observatory (Observatory evidence data) and gold-rush-town.
Examples
1- 01
A maintainer reporting an observation mismatch can provide the endpoint, timestamp and expected behavior without sharing a secret token.