What is design information verification, and where does satellite monitoring fit?

Design Information Verification is the IAEA's term for confirming that a nuclear facility matches what the state declared about it. When a facility comes under safeguards, the state submits design information: layout, process flow, containment structures, the full technical picture. DIV is the inspection activity that checks the facility on the ground against that paperwork, first at declaration, again once construction starts, again at commissioning, and periodically through the facility's operating life.
None of that happens continuously. DIV visits sit on a schedule tied to the facility's lifecycle stage and the safeguards agreement covering it. A facility freshly declared and under construction gets more frequent DIV activity; an operating facility further along the inspection cycle might go a year or more between visits. That gap is where things can move without anyone outside the state knowing until the next scheduled check.
What changes between DIV visits
Construction doesn't wait for an inspection calendar. A footing poured in March, a new structure under roof by June, a section of overburden stripped for a planned extension: by the time a DIV team is back on-site, a lot of that is already built or already backfilled. None of it is necessarily a violation. States update design information for legitimate reasons all the time. An analyst reconciling declared design information against the facility on the ground needs to know when and where ground moved, within the week, so it can be checked against what the state submitted, rather than knowing only that something changed sometime in the past year.
The traditional way to catch that is pulling archive imagery and comparing it against the last known layout by eye, tile by tile, looking for a wall that wasn't there before or a spoil pile that's grown. It works. It also only gets done when someone remembers to run it, which usually means right before a scheduled visit, not continuously in the months between.
Where weekly monitoring fits around the cycle
This is the gap a standing watch on the site covers. Weekly very high resolution imagery over a named facility catches new construction, fresh excavation, and hardening work as they happen, rather than months later when someone finally runs the comparison. A volumetric read turns excavation into a cubic-metre figure, and a footprint read gives any new structure a size and shape an analyst can work with instead of a flagged pixel.
That's a monitoring input, not a verification activity in its own right. It doesn't replace a DIV visit and it isn't a form of safeguards verification under any agreement. What it does is narrow the question a DIV team walks in with. Instead of "has anything changed since last time," the question becomes "we flagged a new slab poured in week 14 and a cut that kept growing through week 22, does the updated design information account for that." That's a sharper starting point for a visit than a blank slate, and it means less gets missed in the stretch between scheduled checks.
For an analyst carrying a watch list of named sites, the practical version of this is simple: weekly VHR passes over the facility, annotated against the last known site plan, flagged the week something new goes into the ground rather than discovered at the next reconciliation. Facility Expansion runs that watch as a standing weekly check rather than a one-off archive pull.
If a site on your list is coming up for its next design information update, it's worth seeing what's already changed on the ground since the last one.