Generate fd Traceability.prompt

# 41 - Generate FD Internal Traceability

## Purpose

Create an internal traceability file that maps the customer-facing Functional Design draft back to the source-bound evidence produced by the BRD-to-FD pipeline.

This task is for internal review only. It must not modify the customer-facing FD and must not introduce new FD behavior.

## Operating rules

- Use only the source artifacts listed in this prompt.
- Do not invent requirements, business rules, validations, command behavior, UI/API behavior, diagrams, or design decisions.
- Do not rewrite `output/40_FD_DRAFT.md`.
- Do not create new requirements or business rules.
- Do not hide untraced FD statements, visual items, Mermaid diagrams, assumptions, TBDs, or open questions.
- Internal IDs are allowed in this traceability file.
- Customer-facing content cleanliness is reviewed later in step 42.
- Preserve source-specific terms unless `output/11_translation_policy.md` or `output/21_glossary.md` explicitly defines a normalized rendering.
- Preserve command names, option names, parameters, field names, product terms, acronyms, state names, and code-like identifiers exactly.
- Respect strikethrough rules from the pipeline:
  - Strikethrough-only content is inactive / deleted / deprecated / superseded evidence by default.
  - Do not trace active FD behavior to strikethrough-only evidence unless the source explicitly says the strikethrough content remains active.
  - If FD behavior appears to depend on strikethrough-only evidence, mark the trace status as `Potential overstatement` or `Needs confirmation`.
- Write the output in English.

## Tasks

### Precondition

Use the latest effective upstream gates:

- Translation gate:
  - If `output/15_translation_review_followup_report.md` exists, use it as the latest translation gate.
  - Otherwise, use `output/13_translation_review_report.md`.
- Feature understanding gate:
  - Use `output/34_FEATURE_UNDERSTANDING_REVIEW.md` if it exists.

Continue only if the latest applicable gates are `Go`, `Go with warnings`, or `Go with minor notes`.

Stop if any latest applicable gate is `No-Go`.

If a gate is `Fix required`, continue only if the FD draft explicitly reflects the required fixes; otherwise mark the traceability recommendation as `No-Go`.

### Instructions

For each meaningful item in `output/40_FD_DRAFT.md`, create a trace row. Meaningful items include:

1. Scope statements.
2. Out-of-scope statements.
3. Functional behavior.
4. Main flow steps.
5. Alternative or exception behavior.
6. Business rules and constraints.
7. Unsupported cases.
8. Data items.
9. Error, warning, or status handling.
10. Data mapping or naming rules.
11. Assumptions.
12. Open questions.
13. Embedded Markdown image references.
14. Mermaid diagrams.
15. Figure-derived scenarios.
16. Source notes that may affect interpretation.

For each item:

1. Identify the related requirement, business rule, glossary term, open question, figure/image evidence, and normalized evidence source.
2. Classify the evidence type.
3. Determine trace confidence and meaning risk.
4. Mark unsupported, partially supported, overstated, or uncertain content clearly.
5. Do not fix the FD in this step. Provide traceability notes only.

## Inputs

### Primary inputs

- `output/40_FD_DRAFT.md`
- `output/30_requirement_inventory.md`
- `output/31_business_rule_catalog.md`
- `output/32_open_questions.md`
- `output/21_glossary.md`
- `output/20_image_analysis.md`
- `output/12_normalized_evidence.md`

### Gate / context inputs

- `output/13_translation_review_report.md`
- `output/15_translation_review_followup_report.md` if available
- `output/34_FEATURE_UNDERSTANDING_REVIEW.md` if available
- `output/33_FEATURE_UNDERSTANDING_BRIEF.md` if available

### Supporting inputs, open only when needed

- `output/11_translation_policy.md`
- `output/10_document_inventory.md`
- `working/extracted/image_inventory_raw.md`
- `working/extracted/formatting_inventory.md` if available
- `working/extracted/document_text.md`
- `working/extracted/tables.md`

## Outputs

### Output file to create or update

Create or overwrite:

- `output/41_FD_INTERNAL_TRACEABILITY.md`

## Required output structure

Write `output/41_FD_INTERNAL_TRACEABILITY.md` using this structure: