Pulse Path support has a ticket about subscription 301. A baseline observed starter on April 1; the next supplied update changes the plan to team on April 11 at 09:00. Build a clean source view, a timestamp snapshot, interval and integrity views, and support_evidence with the earlier plan, current plan, change boundary, and active-row count. Retain the snapshot in the final project. The source also contains a missing plan, multiple subscriptions for one user, and a row without an update clock.
Pulse Path support needs evidence for a disputed plan change. The current subscription table shows team, but the team also needs the earlier observed plan and the point where the two recorded intervals meet. You'll build the source view, record history, and deliver an evidence table from that history.
Each step keeps the files you completed in the previous step. From the second step onward, the exercise records the baseline and applies the same April 11 source update before your build. That makes the result reproducible without asking you to invent earlier records.
Inspect both versions, separate current rows from closed rows, and count active versions before handing off the support result.
The evidence establishes the states the snapshot observed. It can't establish another plan that changed between observations or determine whether an invoice was correct.