simmisdocs
A practical guide to branches, proposals, accepted managed state, and the current limits of Simmis.
the model in four parts
Simmis separates attempts from accepted managed state. Work can multiply across branches, but only an authorized decision changes what becomes official.
chat is the interface
Conversation gives people one place to assign work, supply judgment, and inspect results.
shared memory is the substrate
Versioned context can persist across chats, sessions, and turnover, so each attempt can begin from the Team's existing knowledge.
agents work within assigned bounds
Managers can limit an agent's context, tools, schedule, and spending for each assignment.
review gates changes to accepted state
Consequential work happens on an isolated branch and returns as an inspectable proposal. An authorized reviewer decides what enters accepted managed state.
choose a reading path
CURRENT CAPABILITY GUIDE
Working now. Simmis includes persistent Teams, branchable managed state, proposal review, and queryable history. In progress. The team is building a supported public installation path, more precise permissions, and a unified management interface. Research. Standalone organizational simulation has not shipped. The roadmap is the current status record.