# Phase 1: Human Alignment

**Now ask the user — but ONLY for things you couldn't discover.**

If self-test mode is active and the fixture input already provides approved
answers for the core decisions below, record them and continue without asking.

## 1a. Core decisions (always ask)

These cannot be inferred from code:

1. **"What is your North Star goal?"**
   One sentence. What does success look like in 3-6 months?

2. **"What are your success metrics?"**
   How will you measure progress? List 2-5 observable metrics.
   For each: is it currently measurable, or needs instrumentation?

3. **"What must NEVER happen?"**
   Hard constraints. Things that are absolutely forbidden.
   Examples: no data deletion without confirmation, no hardcoded secrets,
   no task-specific heuristics, etc.

4. **"What's the current biggest pain point?"**
   What should the first milestone fix?

5. **"What is the target architecture style?"**
   Confirm or override the discovered architecture. Define the allowed
   dependency directions between layers (e.g., UI → Service → Repo → Model).
   This will be enforced mechanically.

## 1b. Confirm inferences

Present your Phase 0 inferences and ask:
- "I inferred X about your architecture. Correct?"
- "I see Y modules. Are there others I missed?"
- "I found Z tests passing. Is that the expected state?"

### 1b-ii. Confirm inferred business flows

Present the business flow table from Phase 0f. For each **inferred** flow:
- "I inferred this flow from code structure: [description]. Is this a real
  user/operator flow? Is it critical?"

For flows classified as **human-confirmed**:
- "What are your top 1-3 critical user or operator flows?"
- "Which failure modes are unacceptable in production?"

After confirmation, update each flow's classification to repo-confirmed
or human-confirmed. Drop any inferred flows the human says are wrong.

### 1b-iii. Confirm feedback surface priorities

Present the Feedback Surface Inventory from Phase 0h. For each gap:
- "I found [gap]. Should the harness address this now, or defer it?"

The human decides which feedback gaps are worth closing in the initial
harness vs which can wait for a later milestone. Record the decision —
this directly shapes what Phase 3 generates, what `docs/feedback-profile.json`
claims, and what M0 targets.

## 1c. Resolve needs

For each `blocking: true` item in the Needs Manifest:
- Either get the answer from the user
- Or agree on a workaround
- Or mark it as "deferred to milestone N"

## 1d. Confirm harness shape

Present the Harness Needs Assessment from Phase 0k and ask:
- "I recommend generating these documents and scripts based on what I found.
  Do you want to add, remove, or change anything?"
- "Which quality dimensions matter most for this project?"
  (Let the user prioritize — do not impose a fixed 5×20 scoring grid)
- "Are there any tools, workflows, or artifacts specific to your team that I
  should include in the harness?"

Record the confirmed harness shape. Phase 3 will generate only what was confirmed here.
The confirmed result should be written as machine-readable contracts in
`docs/harness-manifest.json` and `docs/feedback-profile.json` during generation.

If the user is unsure about some items, mark them as `recommended-unconfirmed` and
include them in the initial generation but flag them for review after the first milestone.

**Phase 1 is complete when all `blocking: true` needs are resolved,
all core decisions are recorded, and the harness shape is confirmed.**

After Phase 1 is complete, do NOT ask the human for routine confirmations during
milestone decomposition, generation, or normal iteration work.
Only ask again if:
- a safety-critical ambiguity remains unresolved
- a hard constraint would otherwise be violated
- escalation level L4 is reached
