What is SaSame becoming?
The Institution view separates SaSame identity from any one current product. MCP Factory remains a mature capability station inside a larger Research-Mission-Capability-Reality loop.
- Collection
- company
- Updated
- 2026-08-13
- min read
- 4
SaSame is a self-evolving Research and Execution institution; CP5 now treats executor residue, parked Issues, dependency PRs and stale worktrees as first-class loop inputs that must be absorbed, preserved, archived or scheduled.
Identity
SaSame is not only an AI company, a Factory, or an executor. It is a closed-loop institution for learning from reality: Observatory senses change, Research creates hypotheses, Simulation filters variants, Missions expose only bounded survivors to reality, HOCR chooses capabilities, Factory acts, Evidence records selection pressure, and Knowledge preserves reusable traits.
Three loops
Reality Loop: Mission -> Factory -> Reality -> Evidence. Learning Loop: Evidence -> Finding -> Trait -> Recipe -> Rule -> Capability -> Next Mission. Meta-Evolution Loop: multiple generations of evidence -> evolution analysis -> search, simulation, routing and topology updates.
Commercial boundary
Commercial offers are the outer layer of mature capabilities and Mission results, not the company identity. The current Factory plan ladder remains the commercial SSoT until a newer owner-approved decision changes it.
Immutable boundaries
Self-evolution may change search methods, simulation order, Mission variants, HOCR routes and capability composition. It may not rewrite owner authority, prohibited acts, North Star meaning, commercial truth, legal boundaries or evidence honesty.
CP5 executor and hygiene convergence
The CP5 projection closes the loose operational loop around persistent executors, parked issues, stale branches and worktrees. It does not delete or mutate runtime state directly: clean current convergence work can be absorbed, external dependency PRs remain isolated, dirty worktrees are preserved, and production/test/dependency gaps are scheduled with explicit next actions.
Examples
3- 01
An MCP improvement can run as one Mission while SaSame keeps its broader institution identity.
- 02
A stale recipe returns to Research when its validity horizon expires instead of being treated as permanent truth.
- 03
A red historical test or stale worktree is not ignored; it becomes either a current contract, a preserved artifact, an archive candidate, or a scheduled repair item.