Fact on one rail. Analysis on another.

The official commencement notification divides Act provisions into publication-date, one-year and eighteen-month tranches.

Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision.

Rule 4 is notified to commence one year after Gazette publication; its exact scope should be read in the corrected final text.

Interoperability, receipt semantics, revocation reliability and minimised identity binding deserve design attention before integration claims are made.

The Act and Rules notifications name different groups of provisions and different commencement offsets.

Status should be computed from verified publication metadata and provision groups, while the original source and calculation basis remain visible.

Rights-related provisions are included in the phased commencement notification rather than being safely described by a framework-wide status.

A case workflow should expose missing system acknowledgements and unresolved risk instead of equating a sent response with completed work.

The official framework uses phased implementation; applicability still depends on the organisation and processing facts.

A small organisation can begin with named owners, a compact inventory and a few tested lifecycle paths while avoiding unsupported readiness claims.

No checklist or score on this independent preview is a regulator decision, certification or legal opinion.

Assessment interfaces should separate requirement applicability, control design, implementation evidence and test confidence before summarising results.