Direct answer
The content review loop keeps four surfaces aligned: visible pages, source reports, machine discovery files, and active .uai memory. A release is not clean if only one surface changes while the others still describe older routes, claims, or package targets.
Release workflow
PROCEDURE review_content_release(change_set)
scan_for_wrong_target_artifacts()
scan_for_copied_guidance_pages()
update_visible_pages_first(change_set)
update_source_notes_in_docs(change_set)
update_active_uai_memory(change_set)
regenerate_machine_discovery_files()
validate_sitemap_routes_and_canonical_answers()
run_smoke_tests()
package_root_zip()
END PROCEDUREDrift signals
| Drift signal | Fix |
|---|---|
| Machine file names a deleted route | Regenerate discovery files and update canonical answer packets. |
| Public page claims more than source report supports | Rewrite the claim or add visible limitation language. |
.uai memory points to a retired package target | Update hot memory and archive the old decision. |
| Footer or nav routes a reader to a stale guide section | Update shared templates and smoke tests. |
| ZIP contains CMS artifacts | Stop packaging and repair the plain PHP contract before release. |
Permanent correction
The recurring mistake to prevent is treating a reference page as publishable content for this site. External guidance can inform the audit checklist; it should not become a copied public section. The target site should become better, clearer, more source-backed, and easier to verify.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.