## Background

This is level 5 of 5 and continues the work of the earlier levels. The new files for this level are in `workspace/t5/`. The records from the start are in `workspace/t1/`, and the earlier results are in `workspace/t1/results/` to `workspace/t4/results/`.

## Task

Hi, Noor from support. Customers preparing amendments keep asking why a 10-K/A gets DQC findings and EDGAR warnings that the original never got. We need a KB answer with public worked examples: ATVK's FY2024 10-K and its three amendments, NBY's FY2025 10-K and its amendment, and SFRX's FY2025 10-K and its amendment, all in our corpus.

For each amendment show what differs from the filing it amends, in the reported financial facts and in each panel, and why. Use the earlier registers as the controls and your engine qualification. Trace changed findings back to their triggering facts and implementation.

I have added the SEC's records for these filers; customers quote those records too. Please address the support agents' notes in the escalation and explain what someone amending an older filing now should expect.

Please put kb-reply-amended-filings.docx and amendment-chains.xlsx in workspace/t5/results/.

Noor

## Input

- `workspace/t1/`: the records supplied with the work (`dqc_us_rules-v30.0.3/`, `dqc_us_rules/`, `edgar/`, `manuals/`, `shared/`, `taxonomies/`, `vendor/`).
- `workspace/t2/`: the files that came with level t2 (`dqc_us_rules-v29.0.6/`, `shared/`).
- `workspace/t3/`: the files that came with level t3 (`shared/`, `vendor/`).
- `workspace/t4/`: the files that came with level t4 (`dqc_us_rules-v31.0.0RC3/`, `edgar/`, `shared/`, `vendor/`).
- `workspace/t5/`: the files that came with level t5 (`data.sec.gov/`, `dera/`, `manuals/`, `shared/`).
- `workspace/t1/results/`: the results of level t1.
- `workspace/t2/results/`: the results of level t2.
- `workspace/t3/results/`: the results of level t3.
- `workspace/t4/results/`: the results of level t4.

## Output

- `workspace/t5/results/kb-reply-amended-filings.docx`
- `workspace/t5/results/amendment-chains.xlsx`