rlm-workflow-acp

Sequential phase gates are enforced by validating a strict lock chain from repository artifacts, ensuring only one active phase runs at a time and preventing context rot. This lock validation maintains traceability throughout the run.

Automating requirement implementation is achieved by triggering a run with a specific run-id, which initiates Phase 0 and orchestrates the end-to-end workflow using a canonical, repository-only source of truth for artifact tracking.

Yes, bounded implementation tasks can be delegated to Kimi via acpx. This optional ACP delegation operates within the workflow's strict phase gates while maintaining the locked artifact traceability.

To resume a requirement after manual QA, trigger the resume command to continue the workflow. The system reads local artifacts, verifies existing locks, and enforces the lock chain to safely proceed to the next active phase.

Strict phase gates and locked artifacts are needed to prevent context rot and maintain a canonical source of truth. This sequential lock validation ensures TODO discipline and provides auditability across the entire workflow lifecycle.

Yes, bootstrap and verification utilities are provided to keep runs auditable. These tools read and apply local artifacts, verify the lock chain integrity, and support addenda to maintain strict phase discipline.