A batch can add the expected pages and still be unsafe if unrelated routes disappear. A route-preservation check makes addition and removal separate, explicit decisions.
Capture the pre-build inventory
Export canonical Blog and Research routes from the currently deployed sitemap and source revision. Normalize hostnames and trailing slashes without merging genuinely different paths.
Build the candidate
Generate the candidate route inventory from the exact revision intended for deployment. Include legacy arrays, generated routes, and file-based collections—not just the newest directory.
Classify the diff
Expected additions should match the approved manifest. Any removal, family move, or canonical alias change needs its own authorization and redirect plan. A zero-removal result is the default acceptance condition for a daily batch.
Keep the evidence
Store both inventories, the normalized diff, and the candidate revision. After deployment, compare the public sitemap again. This evidence shows that cadence did not erase historical work.
