policy-redraft

To redraft regulatory policy sections for a compliance gap, use a gap-driven workflow that produces a marked-up proposal of the smallest affected sections. It carries inline rationale and [verify] tags for each change, ensuring targeted edits without altering the approved source.

Yes, you can mark up policy fixes non-destructively. The workflow outputs a redlined draft saved as a new file named [policy-name]-proposed-redraft-[YYYY-MM-DD].md, ensuring the approved source policy remains completely unchanged for attorney review.

The best way to verify rule status before drafting policy changes is to use a rule-status verification guardrail. If verification fails, the system emits a clear warning banner and tags dates and citations as unverified in the marked-up memo.

To prepare a marked-up memo for attorney review, input the approved current policy text and relevant rule text alongside the identified gap. The system generates a proposed redraft containing only the smallest-possible edits with inline rationale for legal approval.

Yes, policy redrafting works directly with gap tracking and rule verification inputs. It consumes the gap and policy-diff inputs produced upstream, carrying through the provenance and verify tags to generate a version-safe proposed redraft.

If rule verification fails during a policy redraft, the system does not block the draft but emits a clear warning banner. It tags all affected dates and citations as unverified so the reviewing attorney knows which regulatory details require manual confirmation.