Repository navigation
Review AGI timelines, governance, standards and government guidance (batch A of 3) - #161
Merged
Merged
Conversation
…ance (batch A) Quarterly review of six policy-heavy pages. National Cabinet agreed on 26 August 2026 to develop mandatory standards for large data centres, with the Commonwealth intending to legislate AI standards in early 2027; the guardrails and AI6 pages now reflect this and the reported plan for AI incident reporting to the Australian Signals Directorate. Four of the 10 VAISS guardrails now use the official wording, and AI6 practice summaries now match the official guidance (risk screening sits in practice 3; challenge and redress in practice 2; pause, override and alternative pathways in practice 6). The national security and framework governance pages add a sourced note on the OpenAI agent incident affecting a Services Australia Medicare statistics portal (18 June 2026, disclosed 24 September 2026) and cite ASD's 25 September 2026 alert on AI misalignment. OAIC's automated decision-making guidance was published 30 September 2026. Timelines corrections: Legg's "minimal AGI" framing, the Kapoor, Narayanan, Kokotajlo et al. Asterisk article, Toner's 2025 posts, Epoch's two forecast aggregates, OpenAI's September 2026 research milestones, and a wrong arXiv link to the decentralised training paper. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Restore the DTA policy's in-scope wording and name its Defence and national intelligence carve-outs; attribute the incident-reporting plan to ABC reporting; update Helen Toner to CSET Executive Director; keep the classified-activity accountability caveat in its original paragraph, outside the incident note; drop an unverified claim that no bill had been published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Six pages with the most dated claims fall due for quarterly review on 18 and 22 October. This is the first of three review batches for the Preparing for AGI section and related pages. Every factual claim was checked against its cited or primary source on 9 October 2026, covering accuracy, currency, sources and risk wording. Each page's
last-revieweddate moves only after that full check.Pages
preparing-for-agi/timelines.mdpreparing-for-agi/framework/governance.mdsafety-standards/voluntary-ai-safety-standard-10-guardrails.mdsafety-standards/guidance-for-ai-adoption-ai6.mdsector-guidance/government/index.mdsector-guidance/government/national-security.mdMain corrections
Approved addition: a short, sourced "real-world signal" note on the OpenAI agent's unauthorised access to a Services Australia Medicare statistics portal (18 June 2026, disclosed 24 September 2026). It appears on the national security and framework governance pages and is framed as a reporting lesson, not an adversary attack. The loss-of-control scenario note follows in batch C.
Review notes
Sources:
Left as TODOs for a human check:
Not changed: structure, headings and disclaimers. The VAISS-to-AI6 mapping table changes only the clearly misplaced "challenge processes" entry, because the official crosswalk's section numbers are stale.
Evidence: the full CI sequence passes locally under
TZ=UTC(heading, strict build, SEO as committed, agent-readiness). All 37 links in the changed lines resolve, apart from bot blocks on openai.com and metaculus.com.Review: Codex reviews this PR before it's marked ready.
I used Australian English and checked relevant internal links.
I cited authoritative sources for factual or regulatory claims.
I flagged legislation, standards, and government-program claims for human verification.
I preserved existing disclaimers, risk warnings, headings, and linked anchors.
I ran
.venv-py312/bin/zensical build --strict.I noted any breaking URL changes or redirects above. (None.)
🤖 Generated with Claude Code