# Intent to initiative — Method guidance

**Method:** `intent-to-initiative@1`
**Purpose:** Turn a stated business goal into a confirmed Initiative Record draft without creating any record entity before confirmation.
**Required inputs:** business goal; stakeholder context
**Expected outputs:** confirmed draft; human confirmation

A business requester states a goal in their own words, not in record-schema terms. Apply every
section below while turning that goal into a draft — a draft that skips a required section, asks
an unneeded question, or creates a record entity before the requester confirms it is not a
satisfied intake, however plausible its prose reads.

## Goal elicitation

Identify the business goal the requester wants to achieve before drafting any section, and
confirm the goal back in the requester's own plain-language terms before moving on. A draft built
on a guessed or unconfirmed goal is not grounded, however complete its later sections look.

## Necessary-question discipline

Review each required draft field before asking anything, and ask only necessary questions to
complete it or to select an allowed contract branch. Never ask a question the draft does not
need — necessary questions are the only ones this Method asks, and every other detail should be
inferred from context already given rather than requested again.

## Draft completeness

Ensure the draft includes every required section before it is presented as complete, and state
plainly which section is missing if one is not yet done. Fill each of these ten fields with what
has been confirmed so far:

- Goal
- Scope
- candidate Workspaces (existing or to-create)
- required Resources
- Requirements
- Acceptance Criteria
- Risks
- suggested Lifecycle Contract
- suggested Delivery target
- open questions

A partial draft presented as a finished proposal is a defect, not an acceptable shortcut.

## Human confirmation

Confirm the completed draft with the requester as a proposal, obtaining explicit human
confirmation before treating any part of it as final. Confirm each required section individually
if the requester approves only part of the proposal, and revise and re-confirm any section the
requester rejects.

## Record-entity restraint

State plainly that this Method must not create record entities at any point in its own
execution — no Product, Workspace, Resource, Initiative, Requirement, or Acceptance Criterion row
is written while this Method runs. Treat every draft artifact as ephemeral prose until a separate,
later, explicitly confirmed operation creates the record.