Bounded official-record check closed on 9 September 2026. This is a status packet, not a fresh interpretation of the crisis protocol's operational powers.
The strongest current public evidence located still schedules the wider Additional Safety Measures statement for autumn 2026. No final disposition of CMA's creator/advertiser checks or pre-monetization review was located in the finite official search. That is a qualified acquisition result, not proof that no decision exists or that every proposal remains substantively undecided.
| Item | Status established by inspected records | What is not established |
|---|---|---|
| Remaining Additional Safety Measures | Ofcom's roadmap, updated 28 July, says it is considering responses and will publish its statement by autumn. Its compliance milestones, updated 24 August, still list autumn publication with the statement link to be confirmed. | A final decision accepting/rejecting CMA's identity checks or pre-monetization review; an implementation date for those proposals. |
| Crisis-response amendments | June decision; draft submitted to the Secretary of State on 12 June and laid on 18 June. Parliamentary scrutiny and subsequent Ofcom issue precede the stated 21-day commencement period. | A completed issue notice and exact date these crisis amendments entered, or will enter, force. |
| Intimate-image hash matching | The 9 September official enforcement announcement expressly sets 30 September 2026 as the new measures' start date. The current regulatory index lists issued but not-yet-in-force illegal-content code amendments. | That this separate commencement also applies to crisis measures or the wider CMA proposals. |
Remaining measures: a current schedule, not a completed decision
The [Ofcom implementation roadmap](http[local research file] displayed updated 28 July 2026, places the wider Additional Safety Measures statement in autumn (reader lines200–202). The [compliance milestones](http[local research file] displayed updated 24 August 2026, repeats that schedule (line197) and warns that dates may change (line141). These are newer affirmative scheduling records than the June crisis statement's forecast or the consultation's stale aggregate pending label.
The roadmap separately reports two consultations opened on 10 July: one on Category 1 duties including identity verification, and another on fraudulent advertising for Categories 1/2a (lines188–197). This does not establish adoption of CMA's monetizing-creator/advertiser proposal. This lane did not read those separate consultation instruments and does not collapse their identity provisions into CMA's request.
The accepted CMA packet remains the source for the proposal itself: submission-findings.md. Its verification subjects include monetizing creators and advertisers; that can affect pseudonymity without constituting universal viewer ID. The June crisis response explicitly declining specific monetization practices remains a disposition of that part of CMA's request, not a blanket rejection of its other proposals.
Crisis: actual parliamentary step located, commencement still unverified
[HCWS124, 18 June 2026](http[local research file] by the Minister for AI and Online Safety, states that draft crisis amendments are being laid that day and describes the 40-day parliamentary period followed by force 21 days after code issue (reader lines27–33). The statement also distinguishes existing duties and voluntary early implementation from the amended code's start. It does not certify that the scrutiny and issue steps have already finished.
The [GOV.UK children's-code draft](http[local research file] published 18 June, records submission to the Secretary of State on 12 June. Its preamble 1.1–1.6 contains anticipated completed-process wording, but the document is expressly a draft, its commencement remains bracketed and its signature name, position and date are placeholders. Those features prevent using preamble 1.4 as proof that scrutiny concluded or 1.5 as a dated commencement notice. Original HTML retained as status-draft-childrens-amendments.html; locally extracted text is separately available.
The accepted statement's cover date is 9 June; the current Ofcom roadmap and regulatory index call the crisis announcement/publication 18 June, while government records establish laying 18 June. These dates are retained as source-specific metadata and procedural events, not silently normalized into one date. This packet does not establish the reason for the publication-label difference.
What changed on 9 September
The [current regulatory-document index](http[local research file] updated 9 September, lists upcoming user-to-user and search Illegal Content Codes as issued 9 September and not yet in force, with amendments taking effect 21 days after issue (lines129–141). Opening the new user-to-user code link 44 through the reader returned Internal Error. A subsequent ordinary GET of the index returned 403 and could not supply the target URL for a direct-code substitute. The route was closed; the new PDF's contents were not inspected. Consequently, this packet does not infer from the index whether that PDF contains crisis amendments.
The [9 September NCII enforcement record](http[local research file] lines129–156, independently names 30 September for the hash-matching measures. Its [same-day news account](http[local research file] lines131–138, also preserves an alternative route using equally effective systems/processes. This establishes a specific upcoming measure and enforcement programme, not that every platform must purchase one named tool. The news also announces an SWGfL information/expertise/evidence partnership and recommends StopNCII; no partnership terms or procurement were acquired in this status lane.
Reading and closure boundary
status-reader-scopes.txt retains selected successful official-reader passages. These are derivatives, not original HTML or PDF bytes. disposition-captures.json records exact scopes, queries, files, hashes and failures. The only substantive new original acquired here is the GOV.UK draft HTML. The ordinary parliamentary GET returned 403, but the successful official reader supplied the full substantive HCWS124 statement. Earlier failed submission and crisis-PDF transports were not retried.
The next discriminating record is a completed, dated Ofcom issue notice/consolidated crisis code and a final statement specifically disposing of CMA's verification/review proposals. The bounded check did not obtain either. Do not calculate a crisis start date by simply adding 40 and 21 calendar days to 18 June, or treat absence from search results as proof of non-publication. No further branch was opened.