Promote To Product Knowledge

Promote To Product Knowledge

File every resolved requirement into its canonical home — as a draft. Promotion places the proposal where it will live; it does not make it approved truth.

Dispatch

One synchronous Agent-tool call, subagent_type: business-analyst, with documentation-steward named in the prompt as the supporting lens for canonical-ownership and metadata discipline.

Required inputs

• The requirement register with no draft or questioned rows remaining.

Required outputs (all mandatory)

• A created or updated file in the destination canonical folder (business rules, decisions, capabilities, user stories, or architecture) for every resolved row, written with draft (Requirements) lifecycle status — never Approved.
• The destination folder's README index updated to list each new or changed entry.
• Requirement-register rows marked promoted, each with a link to the filed document.

Rules — draft-state discipline

• A promoted-but-not-finalized document stays in draft (Requirements) status and the target stays in_progress. Nothing this action files may be reported as settled product knowledge — only finalize-promoted-knowledge (Solution Architect, with zero unresolved questions) flips draft to Approved.
• If a row's canonical destination folder cannot be determined, stop and ask — never invent a new owner or file the same fact in two places.

Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).