Generate fd After Customer Answers Traceability.prompt

# 71 - Generate FD After Customer Answers Traceability

## Purpose

Create internal traceability for the customer-facing Functional Design generated after customer/domain expert answers.

This task maps `output/70_FD_DRAFT_AFTER_QA.md` back to original source evidence, after-QA requirement artifacts, customer/domain expert answers, and unresolved open questions.

This task must not revise the FD, create new requirements, or make new business decisions.

## Operating rules

- Use only the source artifacts listed in this prompt.
- Do not invent requirements, field meanings, business rules, messages, screen behavior, diagrams, or implementation details.
- Customer/domain expert answers are supplemental evidence; do not pretend they were part of the original BRD.
- Preserve source-specific terms unless `output/11_translation_policy.md` or `output/21_glossary.md` explicitly defines a normalized term.
- Mark ambiguous, missing, contradictory, or partially supported content instead of guessing.
- Internal traceability files may use internal IDs such as `REQ-xxx`, `BR-xxx`, `TERM-xxx`, `OQ-xxx`, `ANS-xxx`, `IMP-xxx`, and `QATRACE-xxx`.
- Do not modify the customer-facing FD.
- Keep all output in English.

### Strikethrough / deprecated evidence rule

- Strikethrough-only, deleted, deprecated, superseded, or draft-removed source evidence must not be treated as active FD behavior unless the source explicitly says otherwise.
- If the FD after Q&A uses strikethrough-only evidence as active behavior, mark the trace status as `Potential overstatement` or `Needs confirmation`.
- If customer/domain expert answers explicitly revive or confirm previously struck-through content, mark it as `Confirmed by customer answer` and note the source relationship clearly.

## Tasks

### Precondition

Use the latest after-QA artifacts:

- `output/70_FD_DRAFT_AFTER_QA.md` as the customer-facing FD to trace.
- `output/63_requirement_inventory_after_qa.md` as the after-QA requirement source.
- `output/64_business_rule_catalog_after_qa.md` as the after-QA business rule source.
- `output/65_open_questions_after_qa.md` as the after-QA open question source.
- `output/61_customer_answer_inventory.md` and `output/62_customer_answer_impact_analysis.md` as supplemental answer evidence.

Stop if `output/70_FD_DRAFT_AFTER_QA.md` is missing.

### Instructions

For each meaningful item in `output/70_FD_DRAFT_AFTER_QA.md`, create a trace row.

Trace these item types:

1. Functional behavior statements
2. Business rules and constraints
3. Unsupported cases and negative statements
4. Preconditions, triggers, exceptions, notes, and footnotes
5. Data items, identifiers, field names, operation names, and command options
6. Open questions and TBD items
7. Markdown image references and captions
8. Mermaid diagrams and diagram-derived behavior
9. Customer-answer-derived clarifications
10. Mixed original-source and customer-answer behavior

Do not create new FD content. Only trace existing FD content.

## Inputs

### Primary inputs

- `output/70_FD_DRAFT_AFTER_QA.md`
- `output/63_requirement_inventory_after_qa.md`
- `output/64_business_rule_catalog_after_qa.md`
- `output/65_open_questions_after_qa.md`
- `output/61_customer_answer_inventory.md`
- `output/62_customer_answer_impact_analysis.md`
- `output/60_CUSTOMER_QA.md`
- `output/21_glossary.md`

### 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`
- `working/extracted/image_inventory_raw.md`

## Outputs

### Output file to create or update

- `output/71_FD_AFTER_QA_INTERNAL_TRACEABILITY.md`

## Required output structure

Write `output/71_FD_AFTER_QA_INTERNAL_TRACEABILITY.md` using this structure: