Frontier 2026 Multi-Forum Compliance Router for Melbourne In-House Counsel: Stop Saying Different Things to Different Forums by Accident
You’re in-house counsel for a Melbourne-listed entity. The same underlying fact pattern — say, a customer complaint that surfaces a suspicious transaction — needs to be characterised one way in a board paper, another way in an ASIC continuous-disclosure decision tree, a third way in an AUSTRAC suspicious matter report you cannot tell the client about, and a fourth way if it ever reaches a courtroom where you owe candour. Each of those forums has its own rule set, its own tipping-off or non-disclosure constraint, and its own update cycle. The Frontier 2026 Multi-Forum Compliance Router is the vision-stage capability we’re scoping to keep those positions consistent — or to flag when they cannot be.
Why it matters now
The Australian Solicitors’ Conduct Rules apply to in-house solicitors as much as to private-practice solicitors. The Law Council describes the ASCR as derived from solicitors’ duties as officers of the court, the common law, equity, legislation and “the collective judgment of the legal profession.” Rule 3 (paramount duty to the court and administration of justice), Rule 4 (other fundamental ethical duties, including honesty), and the candour rules in Rule 19 do not pause when you’re working inside a corporate. They sit on top of every disclosure obligation imposed by federal and state statute.
From 1 July 2026, the Law Council is consulting on amendments to the ASCR and a new legal practice rule responding to the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth) regime as it extends to solicitors providing “designated services.” The Law Council’s consultation paper makes the structural problem explicit: solicitors who must file a suspicious matter report face a prohibition on “tipping off” the client or any other unauthorised person — and similar tipping-off and non-disclosure constraints already arise under other federal, state and territory legislation. The proposals are described as being “of general application to solicitors, rather than AML/CTF Act specific.” In other words: cross-forum disclosure inconsistency stops being an edge case and becomes a routine governance problem for in-house teams.
The 5-minute view
- Cross-forum disclosure inconsistency is the risk of telling one forum (a regulator, a court, the board, the market) something that is in tension with what you’ve said — or are obliged to say or withhold — in another forum
- The ASCR (Rules 3, 4 and 19 in particular) constrain in-house solicitors regardless of which forum is being addressed
- The 2026 ASCR review explicitly recognises that tipping-off and non-disclosure obligations now sit alongside duties of candour and client communication, and that the resulting tensions are “of general application”
- Manual reconciliation across AML/CTF, ASIC continuous disclosure, OAIC notification, court filings and internal governance papers is fragile at the speed in-house teams actually work
- The Frontier 2026 Multi-Forum Compliance Router is the vision-stage Exegesis capability designed to hold one canonical fact ledger and route each forum’s required disclosure through its own rule set — with real-time rule-drift sensing when underlying rules change
- T3 (“frontier”) means this is on the roadmap, not in beta — the waitlist exists to shape the scope
What Exegesis is building
The Frontier 2026 Multi-Forum Compliance Router is the T3 vision-level capability documented at 03_Agentic_Solutions/Frontier_2026_Multi_Forum_Compliance_Router.md. The architecture sketch: a single canonical fact ledger for a matter (what happened, when, what is known, what is contested), a forum-registry that encodes each disclosure regime as a deterministic rule set, and a routing layer that produces forum-specific outputs from the same source facts — board paper, regulator notification, suspicious matter report, court filing — while flagging where two forums’ obligations cannot be simultaneously satisfied without escalation. The “real-time rule-drift sensing” element watches authoritative rule sources (the ASCR review process, regulator guidance updates) and flags affected matters when a rule changes. Like RuleCheck, the design intent is local-first and deterministic at the rule-evaluation layer; generative components are scoped to drafting assistance, not to deciding what gets disclosed.
The deliverable
- A canonical matter ledger that holds the underlying facts once
- Forum-specific disclosure outputs generated deterministically from that ledger (board, ASIC, AUSTRAC, OAIC, court, internal counsel file)
- Conflict flags where two forums’ obligations are in tension — surfaced for human decision, never resolved silently
- Rule-drift alerts when an underlying rule set (e.g., a finalised ASCR amendment) changes and previously-cleared matters need re-review
- Audit log per forum, per output, for governance and professional-conduct evidencing
- Vision-stage capability: scope, pricing and delivery model are being shaped through waitlist conversations
CTA
This is a T3 frontier capability. We’re not selling it yet — we’re scoping it with the in-house counsel who feel the cross-forum problem most sharply. Join the waitlist and we’ll bring you into the design conversation, share what we learn from the 2026 ASCR review process as it lands, and let you know when a working version is available to pilot.
Sources
- Law Council of Australia — Australian Solicitors’ Conduct Rules (including the 2026 review and consultation on AML/CTF-related amendments): https://lawcouncil.au/policy-agenda/regulation-of-the-profession-and-ethics/australian-solicitors-conduct-rules
Exegesis capability references:
Schema
```json { “@context”: “https://schema.org”, “@type”: “TechArticle”, “headline”: “Frontier 2026 Multi-Forum Compliance Router for Melbourne In-House Counsel”, “about”: [ {“@type”: “DefinedTerm”, “name”: “Cross-Forum Disclosure Inconsistency”, “in