Generate fd After Customer Answers.prompt

# 70 - Generate FD After Customer Answers

## Purpose

Generate a clean customer-facing Functional Design after customer/domain expert answers have been normalized, impact-analyzed, and incorporated into after-QA internal requirement artifacts.

This task creates the customer-facing FD after Q&A. It must not expose internal artifacts, internal IDs, or pipeline terminology.

## Operating rules

- Use only the source artifacts listed in this prompt.
- Treat customer/domain expert answers as supplemental clarification evidence, not as if they were part of the original BRD.
- Do not invent requirements, field meanings, business rules, messages, screen behavior, diagrams, or design decisions.
- Preserve source-supported and customer-confirmed conditions, exceptions, negative statements, unsupported behavior, notes, and footnotes.
- Preserve command names, option names, field names, product-specific terms, acronyms, and code-like identifiers exactly.
- Follow `output/21_glossary.md` and `output/11_translation_policy.md`.
- Respect strikethrough/deprecated evidence rules:
  - strikethrough-only source content must not appear as active FD behavior unless explicitly confirmed by accepted customer answer.
- Use `TBD` when required details are missing.
- Use `Requires confirmation` when business meaning remains uncertain.
- Do not expose internal artifact names or internal IDs such as `QID`, `ANS`, `IMP`, `REQ`, `BR`, `TERM`, `OQ`, `FIG`, `TRACE`, `RTRACE`, or `PTRACE` identifiers in the customer-facing FD body.
- Write the FD in professional English.

## Tasks

### Precondition

Use the latest customer-answer impact and after-QA artifacts:

- `output/62_customer_answer_impact_analysis.md`
- `output/63_requirement_inventory_after_qa.md`
- `output/64_business_rule_catalog_after_qa.md`
- `output/65_open_questions_after_qa.md`

Continue only if one of these is true:

- step 62 recommended proceeding directly to step 70, or
- step 63 has generated the after-QA requirement/rule/open-question artifacts.

If step 62 recommends follow-up Q&A or human decision and no accepted after-QA artifacts exist, stop and report `No-Go`.

### Instructions

1. Use `63/64/65` as the primary internal source for FD content after Q&A.
2. Use `61/62/60` only to understand how customer answers were applied and to avoid overstating supplemental answers.
3. Use `21/20/12` as supporting source-bound context when needed.
4. Optionally use the latest prior FD (`53`, `50`, or `40`) as a structural reference, but do not copy unsupported or previously rejected content.
5. Generate a full customer-facing FD, not a diff.
6. Do not mention internal review reports, traceability files, requirement inventory, business rule catalog, glossary, image analysis, impact analysis, or Q&A IDs.
7. If a customer answer contradicts the original source and the contradiction remains unresolved, do not write it as confirmed behavior. Put it in Open Questions or Source/Supplemental Clarification Notes.
8. Include visual content only when source-supported or customer-confirmed and still useful to the FD.
9. Do not generate DD, implementation design, or code design.

## Inputs

### Primary inputs

- `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`

### Optional prior FD inputs for structure only

Use the latest available prior FD as a structure/style reference only:

- `output/53_FD_DRAFT_REVISED_PATCHED.md`
- `output/50_FD_DRAFT_REVISED.md`
- `output/40_FD_DRAFT.md`

Do not copy prior FD content that was rejected, untraced, overstated, or superseded by customer answers.

## Outputs

### Output file to create or update

- `output/70_FD_DRAFT_AFTER_QA.md`

## Required output structure

Write `output/70_FD_DRAFT_AFTER_QA.md` using this structure: