ExigoTech-Beno teaches Mike to read Australian case law

A new parallel backend bolts on around 90 Australian court and tribunal databases plus a privacy-law compliance checker, alongside a pivot to Microsoft's cloud.

searchcompliance

The fork adds a second backend service targeting Azure AI Foundry - Microsoft's hosted-agent platform - running alongside the upstream system rather than replacing it. The interesting layer for legal readers is the domain content: a hand-curated registry of Commonwealth, state, and territory courts and tribunals (High Court, Federal Court, AAT, Fair Work Commission, the major state administrative tribunals, plus consolidated acts and regulations) wired into AustLII, Australia's free legal research portal. A separate module encodes the 13 Australian Privacy Principles and a checker to flag compliance gaps.

Worth flagging: the AustLII integration leans on a browser-impersonation trick the fork's own notes call a grey area, and bulk commercial use would need a real conversation with AustLII before anyone shipped this to clients.

So what If you're building or buying Australian legal AI, this is the most concrete attempt yet to make Mike speak the local cases and statutes.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from ExigoTech-Beno/mikeoss, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

10b1c82e feat: Azure-native Python backend agent with AustLII integration Ben Opit 2026-05-07 ↗ GitHub

SHA	Subject	Author	Date
`10b1c82e`	feat: Azure-native Python backend agent with AustLII integration	Ben Opit	2026-05-07	↗ GitHub
commit body - Add backend-agent/ Python FastAPI app replacing TypeScript backend - Azure AI Foundry Hosted Agents (Responses + Invocations protocols) - Semantic Kernel with AzureChatCompletion - Entra External ID JWT auth middleware - asyncpg connection pool for Azure PostgreSQL - Azure Blob Storage layer replacing Cloudflare R2 - Full CRUD routes: chat, documents, projects, tabular, workflows, user, downloads - Add Australian legal plugins for Semantic Kernel - austlii.py: AustLII SINO search engine integration - 90+ database mask_path values (all courts/tribunals across 9 jurisdictions) - 21 known Commonwealth Acts with consol_act identifiers - search_austlii, get_austlii_document, browse_legislation, lookup_act tools - Correct sinosrch.cgi endpoint + browser User-Agent (required to avoid 403) - australian_legislation.py: All 13 APPs + legislation.gov.au + APP compliance checker - Add Dockerfile and agent.yaml for Foundry Hosted Agent deployment - Add azure-approval-request.html for Azure resource provisioning request Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

commit body

- Add backend-agent/ Python FastAPI app replacing TypeScript backend
  - Azure AI Foundry Hosted Agents (Responses + Invocations protocols)
  - Semantic Kernel with AzureChatCompletion
  - Entra External ID JWT auth middleware
  - asyncpg connection pool for Azure PostgreSQL
  - Azure Blob Storage layer replacing Cloudflare R2
  - Full CRUD routes: chat, documents, projects, tabular, workflows, user, downloads

- Add Australian legal plugins for Semantic Kernel
  - austlii.py: AustLII SINO search engine integration
    - 90+ database mask_path values (all courts/tribunals across 9 jurisdictions)
    - 21 known Commonwealth Acts with consol_act identifiers
    - search_austlii, get_austlii_document, browse_legislation, lookup_act tools
    - Correct sinosrch.cgi endpoint + browser User-Agent (required to avoid 403)
  - australian_legislation.py: All 13 APPs + legislation.gov.au + APP compliance checker

- Add Dockerfile and agent.yaml for Foundry Hosted Agent deployment
- Add azure-approval-request.html for Azure resource provisioning request

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-179.md from inside the repo you want the changes in.

⬇ Download capture-thread-179.md