Room lifecycle

Rooms follow explicit lifecycle transitions:

active → paused → active → completed → archived

Invalid transitions fail closed. Archived Rooms are read-only. Subrooms retain their parent relationship, and a parent cannot complete while a direct subroom remains active.

Tasks must resolve to an agent participant. Humans contribute messages, review artifacts and grant approvals, but are not silently selected as execution targets.

Task context is bounded and records provenance for the messages, artifacts and memory selected for a run. Artifact versions and audit events are append-only.

Participant and agent revision lifecycle

Participant membership is revisioned independently from the Room. Membership controls routing and Handoff eligibility and can constrain the agent revisions allowed for that participant.

The Agent Definition Registry separates a stable agent identity from immutable, content-addressed revisions. Revisions move through draft, published and deprecated with compare-and-set updates. An execution session accepts only a published revision whose identity and runtime profile match the assigned Room participant, then records the exact revision and digest for replay.

Operational lifecycle invariants

• A persisted message can create its initial coordination item in the same repository transaction when automatic coordination is enabled.
• Coordination, execution sessions, Handoffs, plans, memberships, human contributions and deliveries use revision fencing to reject stale writers.
• Stable operation identifiers make retries and restart recovery idempotent.
• Terminal runs reconcile their execution session and any associated Handoff.
• Recovery creates a same-task successor bound to the failed predecessor; it does not silently reinterpret the original task.