# Map dependencies, plan migration, review packages and drift

**Recorded synthetic examples; computer-generated narration.** These lessons document the implemented evaluation console, not production accreditation, vendor commands or compliance attestation.

## 1. Understand relationship uncertainty

**Chapter:** 00:00:00.000

This lesson builds a reviewable migration plan without executing changes. Step one. Open Dependencies. Inspect observed, user-confirmed and inferred relationship labels and confidence. The graph displays supplied edges; it is not measured discovery and may be incomplete.

## 2. Choose a purpose-appropriate target

**Chapter:** 00:00:20.667

Step two. Open Migration. Select the synthetic signing HSM and choose ML-DSA as an illustrative signature planning target. ML-KEM is for key establishment, not signatures; AES is a symmetric cipher. A menu choice is not proof of vendor compatibility.

## 3. Generate and inspect a scenario

**Chapter:** 00:00:42.400

Step three. Select Generate planning package. Read affected services, prerequisites, evidence gaps, validation, rollback and residual risk. Execution remains false. The model is a dependency-based planning aid, not a measured digital simulation or change authorization.

## 4. Create a finding-linked package

**Chapter:** 00:01:04.133

Step four. Open a finding and select Create remediation package. The package keeps the finding's rationale and evidence with a proposed target state. This action creates a review record only; no key, HSM or application is changed.

## 5. Assign an owner and request review

**Chapter:** 00:01:23.467

Step five. Return to Migration and load packages. Assign the responsible team, select In review and save. Analysts cannot approve. An administrator may select Approved only after reviewing the package; this approval covers the plan, not operational execution or risk acceptance.

## 6. Verify the review state

**Chapter:** 00:01:45.533

Step six. Confirm the stored Approved state for this synthetic example. Before real change work, obtain separate change authority, exact-version documentation, compatibility tests and operator-owned rollback. Sentinel does not perform those changes.

## 7. Compare snapshot drift

**Chapter:** 00:02:04.333

Step seven. With two comparable snapshots loaded, choose a baseline and select Compare snapshot drift. Inspect added, removed and changed metadata fields. This example changes a synthetic owner. Differences are between supplied snapshots, not observed live-device drift.