pm-update

To update older decisions when newer evidence invalidates them, you can run a backward propagation process. This applies structured updates to status, meta_state, and cross-links, ensuring the decision graph stays consistent and up-to-date.

A backward pass in sprint-driven decision governance is a process that propagates changes across older decisions after a sprint. It aligns meta_state, status transitions, and references to maintain an auditable, consistent decision history.

You maintain an audit trail for decision register updates by applying structured updates with last_reviewed timestamps and audit notes. This records the context and reasoning for each status transition and cross-link modification.

Yes, this decision management process applies to cross-linking related decisions. It enforces graph governance by propagating meta_state and references across the decision register, keeping all linked nodes aligned.

You need to propagate meta_state changes across a decision graph when a sprint or documentation session introduces new evidence. This backward pass ensures older decisions are marked outdated or superseded, preventing inconsistencies.

You enforce guarded status transitions in a decision register by applying a structured backward pass. This workflow governance mechanism ensures status changes are validated, cross-linked, and recorded with last_reviewed timestamps and audit notes.