domain-memory

Persist domain-state across stateless agent runs by enforcing a disk-based domain-memory.yaml as the single source of truth. This ensures reproducibility and observability without cross-run memory dependence, enabling stateless workers to operate across sessions.

Follow the boot-up ritual: read domain-memory.yaml, verify baseline, pick a work item, execute it, and update state. This enforces strict sequential boot steps with atomic work units, observable progress through logs, and CLI-driven state updates.

Yes. Disk-backed domain memory satisfies functional requirements for strict sequential boot steps, atomic work items, locking, and observable logging. It applies to lifecycle orchestration of boot-up rituals, state loading, baseline verification, and feature selection and execution.

Domain memory supports CLI-driven state updates and audits through the domain-memory.yaml file. This enables inspection of persisted state, modification of work items, and verification of baseline conditions without direct agent memory access.

Domain memory enforces single-source-of-truth semantics through YAML files and requires manual or CLI-based updates. It is best suited for orchestration workflows with discrete, sequential work units rather than continuous state synchronization across distributed systems.