review-proposals

To review playbook update proposals, load pending items from the playbook-monitor agent, step through each proposal sequentially, verify the exact diff, and explicitly approve changes before they are written to the practice profile file.

Diff verification for configuration updates is a guardrail mechanism that previews the exact changes to the practice profile file before any write occurs, requiring explicit attorney confirmation to prevent unintended modifications.

Managing rejected or deferred proposal updates involves logging the decision outcome for traceability and archiving the proposals after the resolution process is complete, ensuring no unintended changes are applied.

No, this proposal review workflow requires the playbook-monitor agent to surface pending deviation-driven updates and populate the source proposals needed for sequential attorney review and approval.

The best way to ensure safe approval of practice profile changes is to use a sequential workflow that presents full proposal blocks, requires explicit confirmation, and previews exact diffs before applying writes.

Your practice profile file does not update automatically because the workflow requires explicit attorney confirmation before applying approved changes and archives all proposals only after the full resolution summary is generated.