- Own the AI governance and third-party AI risk framework, including the organisation's formal AI use policy
- Lead the enterprise Microsoft 365 Copilot rollout across licensing strategy, governance, agent adoption and training
- Built the Agent Risk Assessment register, colour-coded and risk-rated for executive review
- Policy work grounded in OVIC and OECD frameworks and aligned to the wider corporate policy suite
AnjaneyaTurai
Everyone can build it. Almost nobody can defend it.
Twelve weeks to a working pilot. Twelve months to an answer for the regulator.
I lead AI governance at a Victorian water utility, which means I sit at the point where an exciting demo meets a privacy commissioner, a procurement panel, a legal team, and a board that has to sign something. The interesting work is not getting the model to answer. It is being able to show, months later, who approved it, on what evidence, and what happens when it is wrong.
My route here ran through the build side. Data science degrees, a Master of Data Science at Melbourne, twelve granted patents in AI and cybersecurity, and years shipping models before governance was a job title anyone wanted. That matters, because governance written by people who have never deployed anything becomes paperwork, and paperwork gets routed around.
Alongside the utility work I run Novareck AI, an independent consultancy taking the same audit-ready approach to SMEs and regulated industries, and I teach and speak on AI governance to people who have to make these calls next quarter, not in theory.
Evidence, not assertion
A vendor claim is not a control. Every risk assessment I sign is grounded in the vendor's own published documentation, cited and dated, so the finding survives the vendor changing their marketing page.
Controls at design time
Retrofitting governance onto a live system means choosing between switching it off and accepting the risk. Constraints belong in the architecture review, not the incident review.
Registers that match reality
Most organisations have an application register and a shadow estate that ignores it. A register nobody can see into is a comfort object. Discovery has to be automatic or it is fiction.
Build first. Then govern.
Consulting, banking, insurance, legal, and now water. The regulated end of every one of them.
- Independent AI consultancy for SMEs and regulated industries, built on an audit-ready governance proposition
- AI and data science delivery, IT and tech consultancy, and applied ML for clients without an internal AI function
- Training and enablement across AI, data science and cyber
- Creation and deployment of AI solutions for clients, partners and stakeholders in a legally sensitive setting
- Internal AI infrastructure and operations, including confidentiality and privilege constraints on model use
- Built a recommendation system end to end, using film plotlines as the semantic basis for personalised suggestions
- Used the OpenAI API for data collection, streamlining acquisition and algorithm refinement in the same loop
- Document analysis: classifying document type and assessing quality using Laplacian, Canny and Sobel techniques
- Applied AWS Rekognition alongside custom deep learning models across the intake pipeline
- Removed downtime and lifted throughput through code and algorithm optimisation using Cython
- Worked on multi-object tracking pipelines including DeepSort
- Owned technology development and delivery for external customers, vendors and partners
- Ran internal IT operations alongside the product build
- Deloitte India — technology strategy and innovation, cloud computing and optimisation
- KPMG India — data cleaning, visualisation and executive presentation
- ANZ Bank — customer data analysis and insight generation
- Bachelor of Science, Data Science — Gold Medal, ranked first in cohort
- Associate Degree, AI in Healthcare — Stanford University
- Google certified data and analytics credentials
Delivered, not projected.
Hover any cell for where the number comes from.
What the register actually holds.
Context, approach, control, outcome. The four questions an auditor asks in that order.
Third-Party AI Risk Framework
- Context
- Every vendor in the stack shipped an AI feature at once. Procurement had no consistent basis to assess them, so decisions were being made on vendor marketing claims rather than evidence.
- Approach
- Built a full AI governance and risk assessment framework for third parties, formalised as organisational policy and sequenced into the existing procurement gates rather than bolted beside them.
- Control
- Findings are grounded exclusively in official vendor documentation — cited, dated, and re-checkable. A public AI fabrication case study sits in the framework as the worked example of what unverified output costs.
- Outcome
- 60+ vendor AI assessments completed against the framework. Repeatable by someone who is not me, which is the only real test of a framework.
Microsoft 365 Copilot — Early Adopter Programme
- Context
- Copilot inherits every permission the user already has. At enterprise scale that turns latent oversharing into a live data exposure question on day one.
- Approach
- Led the rollout across licensing strategy, governance, agent adoption and training as one programme, so entitlement decisions and control decisions were made by the same people at the same time.
- Control
- A structured acceptance-test register, a legal-reviewed early adopter acknowledgement, a delivery Gantt, kick-off materials, and an Agent Risk Assessment register colour-coded to the corporate risk rating scale.
- Outcome
- Org-wide release under a governance wrapper that legal signed and executives can read. Policy work aligned to OVIC and OECD frameworks and carried into the corporate policy suite.
Shadow AI Discovery Platform
- Context
- Organisations maintain application registers for cyber and AI risk. Meanwhile staff sign up to free tools and build agents that never appear in the register at all. The risk view is accurate and useless at the same time.
- Approach
- Entra ID application discovery under a multi-tenant OAuth architecture, surfacing what is actually connected rather than what was declared.
- Control
- A five-stage governance pipeline sits behind discovery — the defensible part, and the reason this is not another inventory tool.
- Outcome
- Targeting one dashboard across the low-code and agent estate: Copilot Studio agents, declarative agents from Agent Builder, Power Apps and Power Automate flows.
Azure-Native Voice Agent
- Context
- Voice agents are the fastest route to a governance problem: audio is personal information, and most reference architectures move it somewhere nobody assessed.
- Approach
- Built a working prototype on the Claude API with Azure-native STT, LLM and TTS components, keeping the data path inside assessed infrastructure.
- Control
- Produced a full SVG architecture diagram of the system so the data path is reviewable by security and privacy before anyone argues about the voice.
- Outcome
- A reference pattern for conversational AI that can survive a privacy impact assessment rather than one that has to be explained away after it.
Novareck AI
- Context
- Smaller organisations in regulated sectors carry the same obligations as large ones with none of the internal governance function to meet them.
- Approach
- An audit-ready proposition: AI and data science delivery, IT and tech consultancy, and web and software work, with the assurance artefacts produced as part of delivery rather than sold afterwards.
- Control
- Governance materials, risk registers and policy scaffolding are handed over with the build, so the client owns the evidence trail.
- Outcome
- Engagements spanning machine learning, analytics, AI enablement and training across Australian and international clients.
Twelve granted patents, and counting.
Filed across AI and cybersecurity in India and the United States, alongside published research and national awards.
What I actually use.
Governance instruments on the left, the things being governed on the right.
LLM & agent engineering
- Claude API tool use · MCP
- OpenAI & Azure OpenAI
- Function calling structured output
- Multi-agent orchestration
- LangChain · LangGraph
- Semantic Kernel
- Copilot Studio · Agent Builder
- Prompt versioning & caching
- Streaming & token budgeting
- Guardrails & refusal design
Retrieval & knowledge
- RAG hybrid · rerank
- Chunking & layout parsing
- Embeddings dense · sparse
- FAISS · Chroma · pgvector
- Azure AI Search
- GraphRAG entity linking
- Query rewriting & HyDE
- Groundedness scoring
- Citation & provenance tracking
Model ops & evaluation
- Fine-tuning LoRA · QLoRA · PEFT
- Quantisation GGUF · AWQ · INT8
- vLLM · Ollama · llama.cpp
- Hugging Face Transformers
- Eval harnesses LLM-as-judge
- Red teaming & jailbreak testing
- Drift & regression gating
- MLflow · Weights & Biases
- Latency & cost profiling
ML, speech & vision
- PyTorch · TensorFlow
- scikit-learn · XGBoost
- pandas · NumPy · spaCy
- Speech-to-text Azure · Whisper
- Text-to-speech & VAD
- Diarisation & streaming audio
- OpenCV Canny · Sobel · Laplacian
- DeepSort object tracking
- Recommender systems
- Cython optimisation
Platform & data
- Azure AI Foundry · Functions
- Key Vault & private endpoints
- AWS Rekognition · S3
- Google Cloud
- Docker · Kubernetes
- CI/CD & IaC
- Power BI DirectQuery
- Dataverse · Power Query M
- Entra ID app discovery
- Python · R · SQL · C/C++ · Java
Governance & assurance
- AI policy authoring
- Third-party AI risk assessment
- Agent risk registers exec-rated
- Privacy impact assessment
- OVIC · OECD principles
- ISO/IEC 42001 alignment
- NIST AI RMF
- Acceptance test registers
- Model & system documentation
- Executive risk reporting
Bring the hard one.
Governance questions, AI risk reviews, speaking, or consultancy work.
If you are standing up AI governance from nothing, trying to get a Copilot rollout past legal, or holding a vendor claim you cannot verify, that is the conversation I want.
I also take speaking and teaching work on AI governance for audiences who have to make real decisions, and consultancy engagements through Novareck AI.
Questions about data science, AI, ML, or guidance on research papers and patents are welcome too.