Trace one DigitalOcean PHP workload

Video transcript

1. 0:00–0:06

   Identify one workload • Illustrative inventory • Workload A • Owner pending

   Workload A stays fixed in its badge in the lower lane. An illustrative inventory panel appears with two blank entries and one empty row. A cyan route traces from Workload A to the empty row, the row outline turns cyan to mark it as Workload A's entry, and an Owner pending tag moves into that row. The owner and the current state stay unknown; nothing is shown as checked.

2. 0:06–0:12

   Separate the responsibility layers • Provider infrastructure • Guest PHP • Workload A • App functions • Owner pending

   Workload A stays fixed. Under the title, Provider infrastructure and Guest PHP name the two layers to keep apart. Four layers slide in: Provider infrastructure, Guest PHP inside a dashed guest boundary, App functions and an Owner pending capsule. A route traces from Workload A to the Guest PHP layer and an outline marks that guest layer, the part an operator inside the Droplet maintains. Provider infrastructure and App functions remain separate responsibilities and the owner stays pending. No fix is shown.

3. 0:12–0:18

   Trace the image path • Build to running workload • Reference pending • Workload A • Build • Registry • Running workload

   Workload A stays fixed. Build, Registry, Reference pending and Running workload stand in order. A route traces from Build to Registry, and Registry is outlined when the route arrives. A second route leaves Registry and stops at the dashed Reference pending capsule; it never reaches Running workload. Registry presence alone does not identify the image the running workload uses.

4. 0:18–0:24

   Match evidence to the service • Workload A • Package or image • Active service • Evidence pending

   Workload A stays fixed. A Package or image card descends from above and an Active service card rises from below until both are aligned. Two short links reach toward each other and stop, leaving a visible gap labelled Evidence pending. A route then traces from Workload A to the Active service card: the evidence has to match that specific service and is still unverified.

5. 0:24–0:30

   Leave application checks open • Workload A • App functions • Function tests • Owner pending

   Workload A stays fixed. The App functions layer appears above a Function tests card with three empty, unticked boxes. A route traces from Workload A to the Function tests card and an Owner pending tag docks below it. The boxes stay empty to the end: untested work remains open, and any suspected-compromise investigation is a separate process.