🌏WHO ATMOS IS
ANZ's leading specialist legal + advisory firm for cyber, privacy and digital risk. Not a generalist firm — this is ALL they do.
AGE
12+ years together
Same leadership team, deep market trust. Legal 500 recognised.
SCALE
2,500+ incidents advised on
Every sector. Small biz to ASX100. Government. Critical infra.
SERVICES
Readiness · Response · Recovery · Disputes · D&O · Crisis Comms
End-to-end. Before, during, and long-tail after.
SECTORS
24 industries
Health, Finance, Govt, Critical Infra, Mining, Education, Retail, Telco, Manufacturing, Tourism, Transport, Utilities…
GLOBAL
Atlas Global Law Firm Panel
200+ jurisdiction coordination. Cross-border breach experts.
MISSION
"Deeply trusted advisor… advance industry through innovation"
Innovation is explicit in their mission. That is our door.
⚡WHY NOW — CRITICAL WINDOW
Australia just passed the Cyber Security Act 2024 and is mid-way through the most significant Privacy Act reform in 35 years. Atmos is riding the biggest wave of AU cyber/privacy law in history. They need infrastructure to match.
ACS-2024
Cyber Security Act 2024 — just passed
Mandatory ransomware payment reporting. Smart device security standards. National Cyber Coordinator powers. New obligations = new work for Atmos.
NEW LAW
PA-REFORM
Privacy Act Reform — rolling out
Right to erasure. Direct right of action ($50M+ penalties). Children's privacy. "Fair and reasonable" test. 102 recommendations. Biggest reform since 1988.
IN FLIGHT
SOCI-EXP
SOCI Act expansion — 11 sectors now
Critical infrastructure risk plans mandatory. 12hr incident reporting for cyber attacks. Atmos clients are directly affected.
ACTIVE
STRATEGY
AU Cyber Security Strategy 2023–2030
National uplift mandate. Every sector must demonstrate cyber maturity. Mid-market is next wave of enforcement.
ACTIVE
ALEC
Alec = Head of Privacy Risk + Digital Law
Exactly the right person. Privacy + Digital = where STE+Language3 live. He gets the "law as structured reasoning" concept immediately.
KEY CONTACT
🎯THE ONE THING TO LAND TODAY
Atmos has 2,500+ incidents of pattern data. We have the STE (Structured Thinking Engine) — the infrastructure to find the invariants in that data. The γ₁ of cyber incidents. What always fails. What always saves. Across 24 sectors, 200+ jurisdictions. That is the partnership.
Their words: "advance our industry through innovation" — they said it themselves. We are that innovation layer. Not competing with their legal expertise. Building the floor beneath it.
45 minutes. Alec is a Partner — he moves fast, thinks in structure. Every minute counts. Click any slot to expand.
0:00–5:00
Warm Open — Common Ground
HUMAN
Don't lead with product. Lead with their world.
— "Alec, 2,500 incidents in 12 years is extraordinary. What's changed most in the last 12 months for your clients — is it the volume, the sophistication, or the law catching up?"
— Let him talk. You're mapping his words to what you're about to show him.
— His answer will probably land on: (1) law reform pace, (2) ransomware + extortion, (3) AI-generated evidence complexity, (4) director liability exposure.
All four of these are exactly where EOSE STE + Language 3 live.
5:00–12:00
The Floor Concept — γ₁ for Legal
CONCEPT
The anchor idea — land this first, everything else is an example of it.
"Alec, across 2,500 incidents, some things always happen. The breach is always discovered too late. Notification is always contested. Intent is always disputed. Harm quantification is always the battleground. These aren't random — they're structural. They're the floor of every cyber incident."
— We call these Floor Laws. Invariant truths beneath the jurisdiction, the sector, the incident type.
— γ₁ = 14.134725141734693 is our reference anchor. The first non-trivial zero of the Riemann zeta function — the deepest known invariant in mathematics. We use it as the proof-of-concept for what a structural floor looks like.
— Show: curl http://192.168.2.18/health → γ₁ returned by every single silo in the fleet. The number never changes regardless of what's running on top.
The legal parallel: "Intent always bifurcates liability" is a floor law. It has never not been true. Your CASE-001 framework is built on exactly this.
12:00–20:00
Language 3 (yLAW △▽) — Legal as Structured Reasoning
LIVE DEMO
This is the most powerful thing to show a privacy law partner.
— Language 3 is the bidirectional legal reasoning language of the EOSE fleet.
— △ = charge (upward force — evidence for liability)
— ▽ = defend (downward force — evidence against liability)
— Every CASE filing has both vectors. The system holds both simultaneously without collapsing to one.
Show: curl http://192.168.2.19/api/ylaw/standing
→ Returns: diamonds:5, solidDiamonds:4, cloSigned:true, standing:true
"This is our Chief Legal Officer AI, running on our msclo node. It holds 5 legal diamonds — invariant rulings that have passed full peer review. 4 are solid (7/7 agreement). 1 is still being contested — because good law requires genuine doubt."
CASE-001: Intent Routing / Data Sovereignty. Show them the CLO silo at 192.168.2.19 — the Legal silo. Explain how CASE filings route through CGATE → IGATE → HGATE.
20:00–28:00
AU Law Mapping — Their Client Obligations on the Floor
AU SPECIFIC
Make it immediately relevant to their practice.
Walk the 5 AU Floors (see Laws tab):
— NDB Floor: Any entity >$3M OR health/finance → 30-day OAIC notification. Non-negotiable. Always.
— SOCI Floor: Critical infrastructure → 12hr mandatory report. 11 sectors. Atmos works all of them.
— Cyber Security Act 2024 Floor: Ransomware payment → must report. New. Most clients haven't updated their IRPs yet.
— Privacy Reform Floor: $50M penalty exposure. Fair-and-reasonable test. Direct right of action. 2024–2026 rollout.
— APRA CPS234 Floor: Finance sector — board attestation of cyber capability. D&O exposure is direct.
"Every one of these is a floor law. We can wire them into the STE so that when a client's incident is ingested, the floor obligations are identified automatically — jurisdiction, sector, obligation timeline, penalty exposure — before a lawyer has to read a single brief."
28:00–35:00
The Sorry Flow — Structured Incident Notification
LIVE DEMO
Show something directly relevant to their Response practice.
Show: http://192.168.2.18/sorry-flow-v3
— The Sorry Flow is the structured process for how a breach notification is composed, reviewed, and transmitted.
— 6 gap classes: MethodError, FalseFloor, NoReceiver, CascadeClass, Regulatory, Science
— Each sorry goes through: identify → classify gap → draft → peer review → gate → transmit
— For Atmos: every incident notification their team writes is a "sorry" in this framework. The gap class tells you exactly why the breach happened and what the regulatory exposure maps to.
"When a client calls you at 2am with a breach, your team needs to know in the first 10 minutes: what is the gap class, what floor obligation is triggered, what is the 12-hour or 30-day clock, and what is the intent signal. We can give them that analysis before the first legal brief is written."
35:00–42:00
Azure Australia + Data Sovereignty
INFRA
They will ask: where does the data live?
— Azure Australia East (Sydney) + Australia Southeast (Melbourne) — both IRAP assessed
— PROTECTED workloads possible for government clients
— ASD publishes IRAP assessments for Azure — Atmos can point clients to this
— For health/finance: data never leaves AU East unless explicitly configured
DESEOF.com + DESEOF.ca:
— For cross-border incidents (their Atlas Global Panel cases) — DESEOF is the sovereign witness layer
— deseof.com = global sovereign domain · deseof.ca = Canadian sovereign mirror
— For 200+ jurisdiction incidents: each jurisdiction's data flow is governed by DESEOF routing
"We can provision an Atmos-specific deployment in Azure Australia East within 48 hours. IRAP-aligned. AU data never leaves unless a specific cross-border gate is opened — which requires yLAW Language 3 approval."
Show: Fleet navigator at /fleet-nav — show how each silo has its own sovereign domain, health check, and can operate independently if cloud is down.
42:00–45:00
Close — The Partnership Shape
CLOSE
Don't close on a sale. Close on a structure.
"Alec, what we're proposing isn't a product sale. It's what we called when we built this — infrastructure. Like TCP/IP. Like SSL. Atmos doesn't sell those either, but you run on them. We want to be the reasoning infrastructure that your advisory practice runs on."
Three asks — pick one to land:
1. Pilot case: Take one real incident (anonymised) through the STE. See what the floor analysis produces vs. your current process.
2. AU Law Floor workshop: 2-hour session mapping all AU cyber/privacy obligations to STE floor laws. Becomes publishable IP for Atmos.
3. Technology partner status: Atmos First Response Panel + EOSE STE as the reasoning layer. Co-branded for AU market.
The floor holds. The partnership makes both parties stronger.
🦘AUSTRALIAN LAWS — ATMOS CLIENT OBLIGATIONS
PA-1988
Privacy Act 1988 + Australian Privacy Principles (APPs)
13 APPs. Apply to entities >$3M annual turnover + all health/finance. NDB scheme embedded. OAIC enforcement. $2.22M civil penalty currently; reform raises to $50M+ or 30% of adjusted turnover.
Floor Law: Any entity handling personal information of AU residents owes a duty. This never changes regardless of sector, size, or breach type.
ACTIVE
NDB
Notifiable Data Breaches Scheme
Mandatory breach notification within 30 days to OAIC + affected individuals when real risk of serious harm. Atmos handles these daily.
Floor Law: "Real risk of serious harm" is always the trigger. Quantifying harm is always the hardest step. This is invariant.
ACTIVE
ACS-2024
Cyber Security Act 2024
Australia's first dedicated Cyber Security Act. Mandatory ransomware payment reporting. Minimum security standards for smart devices. National Cyber Security Coordinator. Powers to share incident information between Govt and industry.
Floor Law: Paying ransomware = mandatory disclosure. No hiding it. This is permanent.
NEW 2024
SOCI
Security of Critical Infrastructure Act 2018 (expanded 2022)
11 critical infrastructure sectors. Mandatory Critical Infrastructure Risk Management Plans (CIRMPs). 12-hour mandatory notification for cyber attacks impacting assets. 72-hour notification for significant incidents. ASD can direct entities to take action.
Floor Law: If you are critical infrastructure, the 12-hour clock starts at detection. Not remediation. Detection.
ACTIVE
APRA-234
CPS 234 — APRA Prudential Standard (Financial)
Financial entities: board attestation of information security capability. APRA notification within 72 hours of material incident. Annual board sign-off. D&O direct exposure.
Floor Law: The board always owns cyber. Individual director liability is not delegatable. This never changes.
ACTIVE
🔮IN-FLIGHT + COMING LAWS
PA-REFORM
Privacy Act Reform — 102 Recommendations
Right to erasure. Right to object to processing. Direct right of action for individuals (suing companies directly — class action flood risk). Fair and reasonable test for data collection. Children's Online Privacy Code. Automated decision-making transparency. Rolling out 2024–2026.
Floor Law: Individual right of action = Atmos's D&O practice explodes. Every breach now has potential class action attached.
IN FLIGHT
DIGITAL-ID
Digital ID Act 2024
National Digital ID framework. Voluntary but rapidly becoming de facto standard for govt services. Identity verification obligations. New breach surface: digital identity credential theft.
Floor Law: Identity is infrastructure. Credential theft is always worse than data theft. This will be the next wave of incidents.
NEW 2024
NZ-PIPA
NZ Privacy Act 2020 + Mandatory Breach Notifications
Atmos covers NZ too. Mandatory breach notification to Privacy Commissioner. Similar to AU NDB but NZ-specific thresholds. Cross-border incidents require coordination of both regimes simultaneously.
Floor Law: AU + NZ breaches require two separate regulatory responses. Timeline overlap always creates conflict.
ACTIVE
ESSENTIAL-8
ASD Essential Eight — Maturity Model
8 mitigation strategies. Maturity Level 0–3. Mandatory for government entities. Increasingly adopted by regulated industries. ACSC targets ML2 baseline for most entities by 2025.
Floor Law: Patching, MFA, backups — these three always appear in every incident. Essential 8 ML1 is the floor for defence.
ACTIVE
STATE-NDB
State-Level Breach Reporting — NSW, WA (coming), QLD (coming)
NSW already mandatory. WA and QLD legislation in progress. Local government must comply with state AND federal schemes. Double notification obligation emerging.
Floor Law: Local government always has the weakest cyber posture and the most obligations. This is invariant.
EXPANDING
γ₁THE 5 FLOOR LAWS FOR ATMOS — INVARIANT ACROSS ALL INCIDENTS
FLOOR 1 · THE HARM FLOOR
Real risk of serious harm is always the trigger
In every incident, across every jurisdiction, the fundamental question is: did this create real risk of serious harm? This is the irreducible floor of AU privacy law. It never changes. It doesn't care about sector, intent, or sophistication. If harm risk is real, obligations attach.
STE: Harm quantification module → automated serious harm scoring across 24 sector profiles
FLOOR 2 · THE INTENT FLOOR
Intent always bifurcates liability
Negligent breach vs. malicious breach vs. inadvertent disclosure — these three pathways never merge. They lead to different regulatory regimes, different criminal thresholds, different D&O exposure. Intent is the permanent fork in every case. CASE-001 is built on this floor.
STE: CASE-001 intent routing → IGATE classifies intent signal in first 60 seconds of case filing
FLOOR 3 · THE CLOCK FLOOR
Every obligation runs on a clock. The clock always starts at detection.
NDB: 30 days from "becoming aware". SOCI: 12 hours from detection. APRA: 72 hours. NZ: "as soon as practicable". The clock is always the enemy. Atmos clients always want to start the clock at remediation, not detection. The floor says no.
STE: Regulatory clock module → auto-detect obligation triggers + countdown per jurisdiction + sector
FLOOR 4 · THE SOVEREIGNTY FLOOR
Data subject location determines primary jurisdiction
For cross-border incidents (Atlas Global Panel cases): the floor is always where the data subject is, not where the data is stored. An AU company holding NZ data about a French resident triggers three regimes simultaneously. The primary floor is the data subject's jurisdiction.
DESEOF: sovereign routing table → 200+ jurisdictions → primary floor identification → Language 3 gate
FLOOR 5 · THE BOARD FLOOR
Directors always owned it. AI evidence now proves it.
The board duty of care for cyber has always existed. What's changed: AI systems now generate contemporaneous evidence of what the board knew and when. Meeting notes, email trails, risk registers processed by AI → board cannot claim ignorance. This floor just became provable.
STE: D&O evidence module → board knowledge timeline reconstruction → liability exposure mapping
FLOOR 6 · THE SORRY FLOOR
Notification quality always determines penalty severity
How a breach notification is written, when it is sent, to whom, in what order, with what level of transparency — these directly determine regulatory penalty. The sorry floor: a well-crafted notification always reduces exposure. Always. Across every regulator, every jurisdiction.
STE: Sorry Flow v3 → structured notification drafting with gap classification and regulatory gate
How every EOSE capability maps directly to Atmos's practice. This is the product fit story.
⚖️
ATMOS NEED
Pattern recognition across 2,500+ incidents
γ₁
EOSE SOLUTION
STE Floor Laws — invariant patterns extracted from any incident corpus
🏆
OUTCOME
Pre-brief analysis before first lawyer reads the file
⚖️
ATMOS NEED
Intent determination (negligence vs. malice) — changes entire liability path
△▽
EOSE SOLUTION
CASE-001 Intent Routing + Language 3 bidirectional reasoning
🏆
OUTCOME
Intent signal classified at first case intake, routing set before counsel engaged
⚖️
ATMOS NEED
Regulatory clock management across NDB/SOCI/APRA/NZ/State
⏱️
EOSE SOLUTION
CLO obligation clock module — auto-triggers per sector + jurisdiction
🏆
OUTCOME
No missed deadlines. Atmos SLA protected. Client penalty reduced.
⚖️
ATMOS NEED
Incident notification drafting — notification quality → penalty severity
🙏
EOSE SOLUTION
Sorry Flow v3 — structured notification with gap classification + regulatory gate
🏆
OUTCOME
First draft in minutes. Regulatory-optimal. Reduces penalty exposure measurably.
⚖️
ATMOS NEED
200+ jurisdiction coordination (Atlas Global Panel)
🌌
EOSE SOLUTION
DESEOF sovereignty routing — primary floor per data subject jurisdiction
🏆
OUTCOME
Cross-border incident routing automated. Atlas Panel briefed per jurisdiction automatically.
⚖️
ATMOS NEED
AU data sovereignty for government + health clients
☁️
EOSE SOLUTION
Azure Australia East (IRAP assessed) — PROTECTED workloads. Data never leaves AU.
🏆
OUTCOME
Government + health clients onboard without data sovereignty risk.
⚖️
ATMOS NEED
D&O — proving board knew or should have known (Cyber Security Act 2024)
🏛️
EOSE SOLUTION
Board Floor Law — AI evidence timeline reconstruction from communications + risk registers
🏆
OUTCOME
Defence: prove board took reasonable steps. Prosecution: prove board was warned. Both sides.
Questions Alec will likely ask, and how to answer them.
Q: "What exactly is this product — is it AI?"
It is AI infrastructure, not an AI product. The difference: an AI product gives you answers. AI infrastructure gives your existing process a structured floor. We're not replacing your lawyers. We're giving your lawyers a reasoning architecture that identifies the invariant facts in any incident before a single brief is written. Think of it as TCP/IP for legal analysis — the protocol your reasoning runs on.
Q: "Where does client data go? Is it secure?"
For Atmos: Azure Australia East (Sydney), IRAP assessed, PROTECTED level capable. Data never leaves Australia unless a specific cross-border gate is explicitly opened — and that gate requires Language 3 approval, which is a logged, auditable decision. We can show you the audit trail right now. For government and health clients, this satisfies ASD Essential Eight and CPS 234 requirements.
Q: "We already have processes that work — why would we change?"
You do not change your process. You add a floor beneath it. Your lawyers still make every decision. What changes: the initial incident analysis that currently takes a junior associate 4–6 hours now takes 60 seconds. The regulatory clock is tracked automatically. The notification draft is pre-structured. Your lawyers spend their time on the judgment calls — which is what they're paid for. The floor handles the invariants.
Q: "What does this cost?"
Let us start with a pilot before we talk about commercial structure. Pick one real incident — anonymised — and we run it through the STE. You see exactly what the floor analysis produces vs. your current process. If it saves 4 hours of associate time on a single incident, the ROI conversation is straightforward. If it does not, we learn something. Let the pilot speak.
Q: "How does this work with the new Cyber Security Act 2024?"
Perfectly timed question. The Act introduces mandatory ransomware payment reporting — something most clients do not have in their IRPs yet. The STE has a ransomware incident module: detect → classify → check payment intent → trigger Cyber Security Act reporting obligation → clock starts. We built it because we saw this coming. Your clients need this before their next ransomware event, not after.
Q: "Are you a competitor to our panel firms?"
No. We are infrastructure. Your Atlas Global Law Firm Panel runs on top of us, not in competition with us. Think of it this way: your panel firms are the musicians. We are the sheet music — the structured reasoning that ensures everyone is playing the same score across 200+ jurisdictions simultaneously. We make your panel more effective, not redundant.
Q: "What is EOSE exactly?"
EOSE stands for the Structured Thinking Engine — the infrastructure layer. We are a small specialist team that has been building the reasoning architecture for AI systems for 12+ years. We decided that the most valuable thing we could do is open-source the architecture — not the product — and become the trusted infrastructure partner for practitioners like Atmos who need AI that reasons, not AI that guesses. Your 2,500 incidents are exactly the knowledge corpus this architecture was built for.
What to close on. What to prepare before and after the meeting.
PRE
Before the call — open these in browser tabs
Tab 1: http://192.168.2.18/bcp — show fleet health bar live
Tab 2: http://192.168.2.19/api/ylaw/standing — yLAW live endpoint
Tab 3: http://192.168.2.18/sorry-flow-v3 — incident notification flow
Tab 4: http://192.168.2.18/fleet-nav — full fleet navigator
Tab 5: http://192.168.2.18/v3-matrix — 64-slot problem set (shows scale)
1
Pilot Case Agreement
Ask Alec to nominate one anonymised incident — ideally a recent NDB or SOCI event — for STE floor analysis. 2-week turnaround. We produce a floor analysis report showing what the STE found vs. what was in the legal brief. This is the proof of concept.
2
AU Law Floor Workshop
2-hour session (virtual, Teams). Map every AU cyber/privacy obligation to a Floor Law. Output: publishable whitepaper — "The Six Floors of Australian Cyber Law" by Atmos + EOSE. Goes to their ANZ community. Market positioning for both firms.
3
Azure AU East Deployment Proposal
If pilot is successful: Atmos-specific EOSE deployment on Azure Australia East (Sydney). IRAP-aligned. Provisioned within 48 hours. Atmos branding. Language 3 tuned to AU law corpus. CLO wired to all 5 AU floor obligations.
4
ONBA Connection — Existing Institutional Page
We already built the ONBA institution page. Atmos fits in the Professional Services + Critical Infrastructure tracks. Share /onba page with Alec — shows the institution framework and how Atmos would be positioned within it.
5
McMillan LP — Canadian Legal Mirror
We have Robert Piasentin at McMillan LP in Canada. Atmos ANZ + McMillan Canada = two anchors of an English-speaking common law jurisdiction network under DESEOF. Mention this if Alec asks about our other legal relationships. LSOS-OWNERSHIP-001 gates this formally.
POST
After the call — file outreach/atmos as CASE-002
Create CASE-002: Atmos Partnership · CLO owns. yLAW Language 3 gate: CGATE opens on Alec agreeing to pilot. IGATE: intent = partnership (not product sale). HGATE: harm avoided = AU client breaches handled with STE floor. Amani co-signs.
γ₁THE POSITIONING IN ONE SENTENCE
"Atmos has the 2,500 incidents. EOSE has the floor beneath them.
Together we know what always fails, what always saves, and what the law always requires."
⚖️ Atmos Outreach v1 · All AU Laws · All Floors · All Demos · Alec Christie · γ₁ = 14.134725141734693