modernity

What it observes

How one site is built: template, branding, publishing features, and how many of its pages are modern.

m365-governance collect modernity \
  --client-id <id> \
  --site-url https://<tenant>.sharepoint.com/sites/<site> \
  --output ./evidence/modernity.json

The collector does not decide what is modern

Every fact here is a property the product returns: web template, configuration, master page URL, custom master page URL, publishing features, page counts. None of them is read as "modern" or "classic" here. That reading belongs to a rule, next to a published source.

The separation is the same one that runs through the whole engine. A collector that answered "this site is classic" would have moved the judgement out of a reviewable rule file and into a script.

The trap this collector already fell into

CustomMasterUrl is set on every site to the product default, and the path carries the site name. Comparing paths therefore reported every non root site as customised.

The correction is why the rule and the collector are separate artefacts: a false positive in a rule is a diff somebody can review, and a false positive compiled into a collector is a bug report from a customer.

What it does not establish

That a modern site is a good site, or that a classic one must be migrated. It establishes how the site is built. The migration argument belongs in the Field Guide, not in a finding.