ExigoTech-Beno wires Mike into Australia's case law

A fork built to answer Australian legal questions from primary sources - and to run inside a Microsoft enterprise tenant.

searchcompliance

ExigoTech-Beno has taught Mike to search AustLII, the free public database of Australian case law and legislation, reaching across roughly ninety courts and tribunals - the High Court, the Federal Court, fair-work and privacy bodies, and state tribunals like NCAT and VCAT - plus consolidated acts and regulations for each jurisdiction. On top of that sits a compliance layer built around the thirteen Australian Privacy Principles, with a checker to flag where a matter brushes up against them.

The same body of work rebuilds Mike's plumbing to run on Microsoft's Azure cloud and sign-in stack, clearly aimed at an enterprise that already lives in that ecosystem. That part is a work in progress - the old backend is still running alongside the new one - but the Australian legal grounding is the reusable prize, and it travels regardless of which cloud you host on.

So what Worth a look for any Australian firm or legal-ops team that wants an AI assistant grounded in real local authority rather than generic training data.

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