Legal Register
Visual Infographic
I-03 Timelines & Rules 👤 Legal/Privacy Counsel & Architects

The Two Clocks Reconciled

Act Commencement vs Subordinate Rules Activation: The Later Date Rule

Every enterprise compliance obligation requires the simultaneous alignment of two separate clocks: (Clock A) the Act Section Commencement Order, and (Clock B) the Subordinate Rule Commencement Notification. A duty is only legally actionable when both clocks have fired. If an Act section is commenced but the corresponding rule prescribing the format is delayed, the general statutory duty applies within reasonableness boundaries; if a rule is published but the parent section is uncommenced, the rule remains inchoate.

Statutory Source: Ch. 2 §3.3
Archetype: dual clock
I-03 DiagramArchetype: DUAL CLOCK

The Two Clocks Reconciled

CLOCK APrimary Act

Act Section Clock (Clock A)

Controls substantive legal liability and statutory penalty ceilings.
Source: Act s.1(2) Gazette Notifications
CLOCK BSubordinate Rules

Subordinate Rule Clock (Clock B)

Controls technical forms, timelines, schedules, and procedural prescriptions.
Source: Rule 1(2) Gazette Notifications
⚖️ Reconciliation Rule: Enforceability = MAX(Clock A, Clock B). The later date dictates operational go-live.
Obligation & ScopeAct ClockRule ClockOperational Verdict
Notice Content (s.5 + r.3)13 May 202713 May 2027Synchronized go-live on 13 May 2027
Breach Technical Report (s.8(6) + r.7)13 May 202713 May 202772-hour detailed form mandatory from 13 May 2027
Consent Manager Registration (s.6(7) + r.11)13 May 202713 May 2027Interoperable CM API required by 13 May 2027

💡 Core Architectural Insights & Takeaways

Key technical and regulatory takeaways established by this architecture diagram.

Never analyze a statutory section in isolation from its implementing rule commencement date.
If the parent section is inactive, rule forms have no independent force of law.
Where both are active, technical rule specifications become mandatory invariants.

📜 Statutory Grounding & Legal Perimeter

Primary Act and subordinate Rule provisions establishing the enforceable legal mandate for this diagram.

Enforceable Provisions:
Section 1(2)Section 6(1)Section 8(6)Rule 3Rule 11

🏗️ Target Architecture & Impacted Systems

Enterprise nodes and store topologies impacted by this architectural pattern.

View Complete Topology (SYS-001..014) →

⚙️ Associated Operational Controls

Control Master Matrix obligations enforcing the standards illustrated in this infographic.

Open Control Matrix →

🛠️ Implementation Guidance & Traps

Recommended technical sequencing and operational failure modes to avoid.

Recommended Implementation Sequence

  1. Tag every row in the enterprise legal register with both Act and Rule commencement dates.
  2. Configure architectural milestones to target the synchronized go-live date.
  3. Audit API contracts against final published rule schemas rather than preliminary draft notes.

Enterprise Traps & Failure Modes

  • ⚠️ Building against draft rule parameters before commencement confirmation.
  • ⚠️ Assuming delayed rules suspend primary fiduciary liability for data security.

📁 Verifiable Evidence Artifacts Vault

Required evidentiary workpapers for regulatory inspections and SDF audits.

📄 Obligations Register Clock Crosswalk (CANONICAL_PROVISION_REGISTER.json)
📄 API Schema Conformance Audit Report