- 0:00–0:06
Identify the running system • Illustrative change record. • Ticket A • Runtime • Jobs
Ticket A stays fixed throughout the film. Two separate routes reach Runtime and Jobs cards with empty evidence slots. A reading marker stops at each slot; the actual installations remain unknown. Before the seam, the two records and their routes visibly withdraw without filling either slot.
- 0:06–0:12
If the fix must wait • Agree containment with the operator. • Ticket A • Containment • Decision • Owner
Ticket A stays fixed. A conditional route reaches Containment and stops at a closed decision bar beside an empty Owner field. No traffic is actually paused. If compromise is suspected, the responsible specialist must preserve and review evidence separately. The unanswered containment panel withdraws before the seam.
- 0:12–0:18
Prepare recovery • A backup still needs a restore plan. • Ticket A • Backup • Restore plan
Ticket A stays fixed. Backup and Restore plan move as whole cards along separate lanes into a recovery group. A route links them without ticks or results. Neither backup availability nor restoration is proved; the two-card group visibly withdraws before the seam.
- 0:18–0:24
Plan the compatible patch • Compatibility still needs testing. • Ticket A • Advisory • Patch plan • Compatibility test
Ticket A stays fixed. Advisory leads to Patch plan, whose route stops before a closed Compatibility test gate. This is a plan, not an applied patch or completed investigation. The complete proposal group visibly withdraws before the seam, with the test still unanswered.
- 0:24–0:30
Keep the closure decision open • Verification pending. • Ticket A • Close ticket • Pending • Runtime evidence • Function tests
Ticket A stays fixed. Runtime evidence and Function tests approach the closed Close ticket gate, marked Pending, along separate lanes. Both evidence slots remain empty. The change stays open, and any suspected-compromise investigation remains separate.
An illustrative PHP change record plans inventory, conditional containment, recovery and a compatible patch, leaving verification and any incident investigation open.
Read the article: PHP security update: check and fix your website