Planning form intake

Same shape as a web form — but instead of producing a brief, the planning intake produces an initiative. An initiative is a planning artefact: a problem statement, a proposed approach, and a tree of child briefs that get spawned once the initiative is accepted.

When to use this

Use a planning form when the work doesn't fit in a single brief. Typical examples: "build out SSO", "redesign the onboarding flow", "GDPR audit". The PM (or any submitter) describes the problem and a proposed approach; an AI pass refines and structures it; a human reviewer accepts it; child briefs are then created from the structured plan.

Mappable fields

mapTo	Initiative field
title	title
problem	problem — the user / business problem being solved
proposed_approach	proposed_approach — how you'd tackle it
submitter_email	Stored on the initiative for follow-up

Initiative lifecycle (separate from briefs)

Once an initiative reaches accepted, child briefs become claimable. The initiative tracks rollup status (how many child briefs are done / in progress / open) and closes itself when the last child brief lands.