Keep the Drupal update in two records

Video transcript

1. 0:00–0:06

   Identify one illustrative page • Page A • Review pending

   The heading lists Page A and Review pending. Page A, one illustrative page, is a pale tile fixed at the head of its own lane for the whole film. Two empty dashed record outlines arrive separately beside it and stop with a gap between them; a line then draws through that gap to show the two records stay apart. Neither outline holds evidence yet. A Review pending tag appears beside Page A: nothing is confirmed.

2. 0:06–0:12

   Keep the two records separate • Page A • Host PHP runtime • Drupal release record • Business review pending

   The heading lists Host PHP runtime and Drupal release record. Page A stays fixed. The two outlines fill with two separate record illustrations carrying those names, each with its own empty evidence field. A closed striped barrier sits on a panel reading Business review pending. A cyan route draws from each record to the barrier and stops just short of it: the host records runtime evidence, the Drupal maintainer records the application release, and both wait for one business review. The routes never cross the barrier, the records never merge, and an outline flashes around the barrier to show the decision is still closed.

3. 0:12–0:18

   Stop at reviewer decision • Page A • Author draft • Reviewer decision • Test page

   The heading lists Author draft and Reviewer decision. Page A stays fixed. An Author draft folder holds a separate Test page marker. A track draws from the folder to a closed striped barrier in front of an empty Reviewer decision panel. Only the Test page marker moves: it travels along the track and stops at the edge of the barrier, which is outlined to show it stays closed. The page is not shown as published and no reviewer decision is shown.

4. 0:18–0:24

   Keep both language checks open • Page A • English page • Arabic page

   The heading lists English page and Arabic page. Page A stays fixed. An English page marker and an Arabic page marker arrive separately beside it, and a line draws between them so the two language checks stay apart. Each marker gets its own empty check box, and both boxes stay empty: neither page has been observed, and the film claims no match between the languages and no successful publication.

5. 0:24–0:30

   Separate private-file access review • Page A • Private file • Role check pending • Author draft • Test page • Reviewer decision

   The heading lists Private file and Role check pending. Page A stays fixed. Above a dividing line, the editorial route returns unchanged: the Author draft folder, the Test page marker waiting at the closed barrier and the Reviewer decision panel. Below the line, a separate Private file marker leaves Page A's lane and travels along its own track to a second closed barrier in front of a dashed panel reading Role check pending, and stops there. The two routes never connect: the private-file role check is separate from editorial approval, and no allow or deny result is known.