review-proposals

To review commercial playbook updates, you load a local pending proposals markdown file to render structured proposal frames, evaluate exact diffs, and apply changes only after explicit attorney confirmation. This ensures safe modifications to your legal practice profile.

High-impact legal areas like KVKK, liability, and TBK clauses are protected by guardrails that automatically flag risky or weakening changes. The workflow requires explicit attorney confirmation before any modifications to these sensitive commercial contract profiles are applied.

Yes, you can accept, reject, defer, or edit pending playbook update proposals on a proposal-by-proposal basis. The workflow logs all reject and defer decisions for auditability, summarizes outcomes after resolution, and archives the proposals file.

Diff approval works by displaying the exact proposed modifications to the commercial profile before any changes are committed. For acceptance or edits, the system renders the specific diff, ensuring attorneys see precisely what will change before granting explicit confirmation.

Yes, you need a local pending proposals markdown file generated by an upstream playbook-monitor agent. The system requires loading this file to render structured proposal frames, display exact diffs, and route updates through the attorney approval workflow.

You should use an attorney confirmation workflow whenever modifying Turkish-law commercial playbooks, especially for high-impact areas like FSEK/IP, forum selection, foreign law, dispute prerequisites, damga vergisi, and signature authority to prevent unauthorized profile changes.