Where are exact SaSame schemas and lifecycle states defined?
Reference material gives operators and integrators field-level definitions without repeating explanatory tutorials.
- Collection
- documentation
- Updated
- 2026-07-29
- min read
- 3
- Version
- v1
Reference pages expose versioned schemas, status enums, API contracts, evidence boundaries and release receipt fields used across human and machine interfaces.
Purpose
Reference material gives operators and integrators field-level definitions without repeating explanatory tutorials.
Operational model
Each reference item carries a schema version and links to the conceptual documentation that explains why the field exists.
The MCP compatibility reference distinguishes core protocol revision from extensions:
- 2025-11-25 Tasks are legacy experimental methods. The private Owner MCP retains one durable read-only generate_repo_report recipe with bounded TTL, result size, cancellation and principal ownership checks. - 2026-07-28 Tasks are not advertised by SaSame while the TypeScript SDK v2 typed runtime does not implement them. Calls fail as unsupported instead of being silently downgraded. Reverification starts when the official TypeScript SDK publishes a compatible Tasks extension runtime/package. - MCP Apps are optional. The private Owner MCP exposes only the versioned ui://sasame/job-progress/v1.html resource; client and public MCP surfaces expose no App from this implementation.
Boundary and limitations
Examples are illustrative unless explicitly marked as a live contract or retained observation.
Examples
1- 01
The lifecycle_status field distinguishes published, archived, deprecated, superseded and retired knowledge records.