---
id: DFMOD-C5-POS-006
title: "Historical compound data stays audit-able after modification"
product: mobile
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C5
  tsdScenario: C5.5
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C5.5; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-submitted-report-exists
tags:
  - mobile
  - digital-form
  - form-modification
  - compound
  - history
  - pk141
  - staging
---
## Objective
Verify submitted reports keep their old compound structure and answers after the compound changes.

## Preconditions
- See [[PRE-DF-submitted-report-exists]]
- And the report was submitted with an older compound structure

## Steps
1. Modify the compound afterwards
2. Re-open the old submitted report

## Expected Result
- Then the submitted report still shows the old structure and answers
- And historical data does not change due to system-data updates or a new compound version
- And system-linked option values in the historical answer remain original

## Source Traceability
- TSD: PK141
- Section: C5 - Runtime Safety
- Scenario: C5.5 - Historical compound data audit-able
- Acceptance Criteria: PRD M.6 Scenario 1-5

## Evidence Required
- Historical report stable across repeated opens after a compound change.

## Notes / Gaps
- No gap.