concept reference

core vocabulary

Basis: The exact version of accepted managed state from which a task or branch begins.
Branch: Isolated, copy-on-write state that can diverge from its basis without changing the parent.
Composite branch: A branch that coordinates versioned knowledge, files, and relevant execution context from one basis.
Team and room: A Team is the persistent product context for people, agents, shared material, and history. A room is its Dvergr runtime context.
Accepted managed state / main: The currently accepted state managed by Simmis. Developer interfaces may call the branch main.
Proposal: A branch packaged for review with its changes, rationale, provenance, and cost.
Semantic diff: A description for reviewers of what meaningfully changed across facts, files, or outputs.
Provenance: The chain connecting an output to its basis, agent, tools, sources, and run history.
Merge and discard: The review decision determines whether to merge a proposal into accepted managed state or discard the attempt without changing its parent.

Component	Responsibility	Plain language outcome
Simmis	Product, shared work, proposals, review	Attempts remain separate from accepted managed state until an authorized decision makes them official.
Spindel	Reactive interface and execution context	Live work keeps the context needed to explain and resume it.
Dvergr	Rooms, agents, tools, schedules, budgets	An agent works inside explicit operational bounds.
Kabel + Yggdrasil	Synchronization and composite branching	An attempt can diverge without quietly changing its parent.
Datahike + Konserve	Versioned knowledge and durable storage	Shared memory keeps history instead of overwriting it.

Working now means the capability exists in the current system, although documented limits may remain.
In progress means active product work. Do not plan as though it has shipped.
Planned means intended work that is not yet in active delivery.
Research explains design intent, not a product commitment.