The disclosure lane shows exactly which WordPress-managed surfaces are healthy, which are drifting, and which should block publication until the evidence and qualifier path is repaired.
Reviewer-first posture
Clear the model-assisted claims disclosure on pricing and comparison pages before the next regulated launch window, or buyer-facing copy will outrun approval posture.
| Surface | Disclosure package | Status | Owner | Risk | Next action |
|---|---|---|---|---|---|
| Homepage service hero Public web |
AI-assisted service promise | watch | Content ops | Buyer-visible copy can imply a broader automation scope than the reviewed operating model. | Mirror the reviewed qualifier in the hero footer and schema description before the next homepage push. |
| Comparison landing pages Search + answer engines |
Competitive claims pack | blocked | Growth engineering | Regulator or procurement review sees orphaned claim evidence and stale review provenance. | Rebuild the comparison disclosure packet and publish the updated manifest URL before relaunch. |
| Embedded product docs Docs hub |
Implementation disclosure card | healthy | Platform docs | Low, current route parity is intact. | Keep the docs card on the weekly evidence refresh rail. |
| Downloadable sales one-pagers Field collateral |
Commercial disclosure footer | watch | RevOps | Procurement reviewers can miss the live approval notes when downloading offline collateral. | Swap the PDF footer URL to the canonical disclosure endpoint and re-export the active pack. |
| Support knowledge base macros Agent-assisted support |
Operational guardrail note | healthy | Support systems | Low, support and public copy remain aligned. | No immediate action beyond monthly drift review. |