Section is ready
The same shapes as the Overview: one Section, three
Requirements. Two are evidenced (glowing green). The third —
DR plan — is ready but the user's response hasn't yet been folded into a Document
(amber). The Section's draftability flips to draftable_with_gaps.
draft-composer is invited in.
Draft v1
The composer reads the Section, its Requirements, the Evidence supporting each, and the user responses on any Questions in scope. Then it writes prose.
Every paragraph carries a covered_requirements entry: which Requirement
does this paragraph address, and is the coverage substantive or a placeholder?
The DR plan paragraph is honest — it's a placeholder, marked as such. Nothing pretends
to be more solid than it is.
User redlines
The CFO and the Compliance lead open the draft. They mark up changes in Word — a corrected figure, a missing cross-link. DraftFeedback captures the diff and the extracted COMMENT blocks.
Nothing is silently accepted. Each comment lands as an addressable item the composer will see on the next round.
Draft v2
Next round, draft-composer reads the feedback alongside the original Requirements. It produces v2. The corrected capital figure is in — and the concern is flagged inline, so the regulator-facing prose admits what the Evidence row already says.
The cross-link to §1.2 is in. The DR plan placeholder is now substantive — a Question on DR was answered in the same round, and the composer absorbed the answer into the prose.
Approved
The team reviews v2. No new feedback. Status flips to approved. Until
something upstream changes — a Requirement re-interpreted, an Evidence flagged stale,
a user response retracted — this Draft is the Section's prose. The slot in the
regulator's template is filled.
If something does change, the loop simply starts again. v3 will exist before the application ships.