Simmissimmis inspect the source

how an agent attempt becomes accepted work.

Simmis gives an agent a known basis, a separate branch, and a review gate before its changes enter shared state.

The control foundations run today. Supported public installation and production operating guarantees remain incomplete.

familiar controls in one integrated stack.

Start with tools you already know. See how Simmis combines familiar controls inside one stack for organizational work.

Listed entities/products are illustrative references, not dependencies. Simmis is independent and is not affiliated with or endorsed by these companies.

Our underlying replikativ stack and Simmis form one vertically integrated Clojure/ClojureScript system.

GitHub

change model
working now
PROVEN IDEA

Make change on a branch, inspect the diff, request review, and merge deliberately.

THE SIMMIS MOVE

Apply that control model to structured data, files, execution context, and decisions in managed organizational state.

BUILT INTO
DatahikeYggdrasilSpindelSimmis
where Simmis differs

GitHub versions repositories. Simmis also coordinates structured organizational facts and the registered execution context that changes them.

the governed work loop.

Simmis lets agents attempt changes without making them official. It branches the task’s managed state, bounds the work, and turns the result into a proposal you can merge or discard.

THE WHOLE LOOP One managed attempt, end to end.

A task leaves accepted state on a managed branch. Only accepted work returns.

ACCEPTED STATE CHANGES ONLY ON ACCEPTANCE
  • BLUE MEMORY
  • GREEN BRANCH
  • AMBER WORK
  • CORAL REVIEW
  • INK COMMIT
  1. 01 Basis: The task begins from an exact accepted version of shared state. Datahike + Konserve · versioned knowledge.
  2. 02 Branch: Any authorized participant can fork managed state at any time, including from another branch, without changing accepted state. Dvergr coordinates · Yggdrasil + Spindel fork.
  3. 03 Work: People and agents share the room. Nested branches keep parallel attempts apart. Tools, budgets, and checkpoints bound agent work. Dvergr + Yggdrasil · rooms, nested branches, bounded work.
  4. 04 Review: Semantic changes and conflicts are shown before anything lands. Simmis + Yggdrasil · proposals and conflict handling.
  5. 05 Decide: Merge reconciled work or discard the attempt. Simmis + Yggdrasil + Datahike · decision and history.

Branching contains state managed by Simmis. External actions still require their own controls.

five responsibilities. one system.

The stack assigns each part of the work loop to a specific component. Together, those components carry an assignment from its starting state to an accepted or discarded result.

deeper foundations and inference as a design influence.

Simmis draws on research into immutable systems, reactive computation, and probabilistic programming. These influences explain why state is treated as a value and why a branch records only what changes.

The component role map explains the practical design. Readers interested in the research can watch the talk below.