Analyze Customer Answer Impact.prompt

# 62 - Analyze Customer Answer Impact

## Purpose

Analyze how normalized customer/domain expert answers affect terminology, requirements, business rules, open questions, FD content, visual interpretation, and traceability.

This task only determines impact and recommends the next rerun/update path. It must not directly update requirements, business rules, glossary, FD, or traceability.

## Operating rules

- Use only the source artifacts listed in this prompt.
- Treat customer answers as supplemental evidence, not original BRD evidence.
- Do not invent changes not supported by customer answers.
- Do not automatically apply customer answers to unrelated requirements or rules.
- Do not silently override BRD/source evidence. If an answer contradicts the source, mark the contradiction and recommend human/domain decision.
- Preserve product-specific terms, command names, option names, field names, acronyms, and code-like identifiers exactly.
- Follow `output/21_glossary.md` and `output/11_translation_policy.md`.
- Respect strikethrough/deprecated evidence rules from the pipeline:
  - strikethrough-only source evidence must not be treated as active behavior unless explicitly re-confirmed by customer/domain expert.
  - if customer answers reactivate, reject, or clarify strikethrough/deprecated content, mark it as a high-attention impact.
- Internal IDs may be used in this analysis for traceability.
- Write outputs in English unless source values must remain unchanged.

## Tasks

### Precondition

Use `output/61_customer_answer_inventory.md` as the normalized answer source.

Use the latest available FD/review context in this order:

1. `output/55_FD_PATCHED_REVIEW_REPORT.md`, if available
2. `output/52_FD_REVISED_REVIEW_REPORT.md`, if available
3. `output/42_FD_REVIEW_REPORT.md`, if available

Use the latest available customer-facing FD in this order:

1. `output/53_FD_DRAFT_REVISED_PATCHED.md`, if available
2. `output/50_FD_DRAFT_REVISED.md`, if available
3. `output/40_FD_DRAFT.md`, if available

Use the latest available traceability in this order:

1. `output/54_FD_PATCHED_INTERNAL_TRACEABILITY.md`, if available
2. `output/51_FD_REVISED_INTERNAL_TRACEABILITY.md`, if available
3. `output/41_FD_INTERNAL_TRACEABILITY.md`, if available

### Instructions

For each normalized customer answer:

1. Identify the affected source-derived item(s):
   - glossary term(s)
   - requirement(s)
   - business rule(s)
   - open question(s)
   - image/diagram interpretation
   - FD section(s)
   - traceability row(s)
2. Classify the impact type.
3. Determine whether the answer confirms, clarifies, supplements, contradicts, or fails to answer the source ambiguity.
4. Determine required action.
5. Recommend the earliest safe rerun/update step.
6. Identify risk and whether human/domain decision is required.
7. Do not directly update downstream artifacts.

## Inputs

### Primary inputs

- `output/61_customer_answer_inventory.md`
- `output/60_CUSTOMER_QA.md`
- `output/32_open_questions.md`
- `output/30_requirement_inventory.md`
- `output/31_business_rule_catalog.md`
- `output/21_glossary.md`

### Latest FD/review context, use available files

- `output/55_FD_PATCHED_REVIEW_REPORT.md`, if available
- `output/54_FD_PATCHED_INTERNAL_TRACEABILITY.md`, if available
- `output/53_FD_DRAFT_REVISED_PATCHED.md`, if available
- `output/52_FD_REVISED_REVIEW_REPORT.md`, if available
- `output/51_FD_REVISED_INTERNAL_TRACEABILITY.md`, if available
- `output/50_FD_DRAFT_REVISED.md`, if available
- `output/42_FD_REVIEW_REPORT.md`, if available
- `output/41_FD_INTERNAL_TRACEABILITY.md`, if available
- `output/40_FD_DRAFT.md`, if available

### Supporting inputs, open only when needed

- `output/20_image_analysis.md`
- `output/12_normalized_evidence.md`
- `output/11_translation_policy.md`
- `output/10_document_inventory.md`
- `working/extracted/document_text.md`
- `working/extracted/tables.md`

## Outputs

### Output file to create or update

Create:

- `output/62_customer_answer_impact_analysis.md`

## Required output structure

Write `output/62_customer_answer_impact_analysis.md` using this structure: