# Controlled CDC stop/resume evidence packet

Copyable worksheet. Blank fields are required observations, not passed checks. Keep source authoritative and target effects disabled. This file does not authorize operations.

## Blank run record

### Run identity and authority

- Run identity and packet immutable reference:
- Lead / source DBA / target DBA / DMS operator / observer / acceptance owner:
- Approved environment, action scope and window reference:
- Source-only writer and disabled target effects evidence:
- Exact source/target database versions, DMS engine, Region and topology:
- Excluded modes (including mid-full-load interruption, task recreation and crash):

### Configuration and baseline

- Task ARN/creation identity, source and target endpoint identities:
- Schema, mappings, endpoint attributes and task-settings content references:
- Target preparation mode and cached-change stop settings:
- Complete selected-table inventory and all-page statistics reference:
- Full-load/cached-change observations and baseline C0 definition:
- Paired C0 exports, query/projection/population and invariant result:
- Permission denials, coverage exclusions and unresolved evidence:

### Approved interruption

- Maximum stop interval, request/readback timeouts, monitoring interval and catch-up deadline:
- Source storage threshold, monitoring and abort owner:
- Retention planning reference and actual readable log range evidence:
- Stop request receipt / stable stopped readback / stop reason:
- Opaque recovery checkpoint and source log relation attested by DBA:
- T1/T2/T3 commit receipts and any unknown commit/retry outcome:
- C1 committed-cut definition and paused writer evidence:
- Pre-resume identity comparison, source log/storage/access recheck:

### Recovery and comparison

- Resume-processing request for preserved previously executed task:
- Observed status/log/table chronology and timeouts:
- Paired source/target C1 exports with complete population scope:
- Exact missing/extra/different-key report:
- Update, insert and delete results separately:
- Per-order line invariant, orphan result, counts and totals:
- DMS validation enabled/supported scope, statuses and collection time:
- Repair, target writer, configuration change or other intervention:

### Decision and restoration

- Disposition: accepted bounded run / failed / inconclusive:
- Evidence required but unknown, failed or excluded:
- Exact favorable claim and excluded failure modes:
- Owner/permission for writer restoration, access restoration and target disposal:
- Separate approval for any repair, reload, reseed or new failure-mode run:
- Evidence retention/access and task/checkpoint preservation:
- Observer and acceptance-owner decision references:

## Filled fictional planning packet R7

This is NOT EXECUTED. It deliberately cannot receive actual acceptance.

- Lead Mira; observer Dev; Source-A sole writer; Target-B non-authoritative. All are synthetic aliases, not authenticated resource identities.
- RDS MySQL8.0 instance source and target; actual complete versions, DMS version and Region UNKNOWN. Execution remains HOLD.
- Task-A / schema-S1 / mapping-M1 / settings-J1 represent unchanged expected identities. Actual content/version evidence absent. J1 proposes DO_NOTHING on empty preprepared target tables and both cached-change automatic stop flags false; actual settings must be collected and reconciled before execution.
- Fictional planning limits: stop interval at most8minutes; stable-stop and resume-request observation timeouts2minutes each; progress observation every10seconds; final comparison deadline30minutes after resume request. These are proposed limits for this tiny specimen, not measured performance or AWS recommendations. Source storage threshold and approved log budget remain UNKNOWN, which independently holds execution.
- Proposed C0: orders O101/100,O102/50; lines L1/O101/100,L2/O102/50. Two rows each, total150 each, no orphan.
- Proposed stop occurs only after reconciled full load and cached changes. Required stopped status, checkpoint, log coverage and storage readbacks NOT OBSERVED.
- T1 updates order101 and line1 to120; T2 inserts order103 and line3 for75; T3 deletes line2 and order102. All proposed commit receipts null.
- Proposed C1 after paused source writer: orders101/120,103/75; lines1/101/120,3/103/75; total195 each, two rows each;102 and2 absent.
- Resume action would be resume-processing on the preserved task, not reload-target. Actual action NOT EXECUTED.
- Actual paired exports, DMS validation, resource observations and timing UNKNOWN.
- Decision: no operational acceptance. Source authority retained. Any subsequent resume, repair, cleanup or reseed requires real owners and separate approved actions.

## Predeclared opposing observations

1. Same rows/totals but target contains102/75 instead of103/75: FAILED exact-key reconciliation.
2. Correct inserts/updates but line2 remains without order102: FAILED delete/orphan check.
3. Source commit status unknown after generator timeout: INCONCLUSIVE cut, no blind retry.
4. Saved checkpoint relation to available source history cannot be substantiated: HOLD resume approval, no guessed position.
5. Task running but validation pending at deadline: INCOMPLETE, not accepted.
6. Task recreated or mappings changed between baseline and target export: INCONCLUSIVE attribution, preserve old run.
7. Actual exact-key comparison and validation complete inside all approved limits with unchanged identities: candidate for bounded owner acceptance only, not application cutover or proof of untested outage modes.