ten-minute tour

minute 1: choose the working context

Begin in a Team. Inside Dvergr, its runtime context is called a room. A Team holds the people, agents, shared material, and history relevant to a stream of work.

minute 2: establish the basis

The basis is the exact version of accepted managed state from which the task begins. Naming it records what context was available when the task began.

minutes 3 and 4: delegate within bounds

Describe the outcome, then set the agent's context, permitted tools, time or schedule, and spending limit. The environment records these execution bounds for the assignment.

minutes 5 and 6: fork the attempt

Consequential work moves to a composite branch. Knowledge, files, and execution context can evolve together while accepted managed state remains untouched.

minutes 7 and 8: inspect the proposal

The result returns as a proposal with a meaningful account of what changed, supported by provenance, rationale, and cost.

minutes 9 and 10: merge or discard

An authorized reviewer decides what enters accepted managed state. Merge incorporates the proposal. Discard ends the attempt without changing its parent. Simmis retains the attempt and decision history after either decision.

where next

• Follow the annotated founder walkthrough.
• See where each lifecycle step lives in the architecture.
• Review the current limits before evaluating deployment.