Authority at execution
Define who has authority over a workflow, data use, system action, or escalation point.
Pilot discussions
OBEXGATE is working with early pilot partners to test how governance rules, authority boundaries, and audit controls can operate where AI and data actions are actually executed.
OBEXGATE is opening selected pilot discussions with organisations that need AI governance to move beyond policies, PDFs, and static checklists.
The focus is applied governance: how authority, consent, documentation, and escalation controls operate at the point where AI systems, agents, data workflows, or automated decisions are executed.
Many organisations already have AI policies. The harder question is whether those rules can be enforced when systems are acting, routing, classifying, approving, denying, transcribing, summarising, escalating, or sharing data.
Define who has authority over a workflow, data use, system action, or escalation point.
Test when an AI or data action should be allowed, warned, held, blocked, or stopped.
Produce structured records showing what rule applied, what action was requested, what control was triggered, and what human review occurred.
Use synthetic or controlled scenarios to test governance behaviour before live operational exposure.
Help teams understand how governance works in practice, not only how it is described in policy.
OBEXGATE has secured an initial pilot partner in New Zealand focused on Indigenous data governance and applied AI governance.
The pilot examines how authority, consent, provenance, AI transcription, synthetic clinical data, and secondary research use can be governed through operational controls rather than policy language alone.
Additional company agreements are awaiting signature before the partner can be named publicly.
The New Zealand pilot is focused on a clinical patient use case using synthetic data. The scenario examines how information captured in a clinical context may later move through AI transcription, data handling, research preparation, secondary analysis, or external use.
OBEXGATE is being used to test how governance boundaries can travel with the workflow and trigger the appropriate control when a proposed action exceeds the permitted authority.
A controlled clinical scenario for testing governance at the execution layer.
Synthetic data enables governance testing without exposing private or live sensitive data.
AI transcription governance can be tested before operational use creates avoidable exposure.
Controls can evaluate provenance, consent, authority, escalation, and secondary research use.
OBEXGATE also has a US university pilot pathway in discussion, focused on applied governance education for students.
The goal is to help students understand how AI governance operates in practice: how decisions are classified, what authority applies, when documentation is needed, when escalation is warranted, and how governance controls can be tested before systems are deployed.
A university pilot can expose students to practical governance problems using structured scenarios, synthetic data, and operational decision controls. This creates a bridge between AI policy education and the real-world systems organisations are now deploying.
The pathway is in discussion and will only be described publicly in more detail after appropriate agreements are signed.
Test how rules apply when data moves across systems, teams, models, vendors, or use contexts.
Define who can approve, deny, escalate, or override a proposed AI or data action.
Examine whether a proposed use remains within the original permitted purpose or requires additional review.
Test governance controls around clinical, educational, administrative, or operational transcription workflows.
Use synthetic data and controlled scenarios to validate governance logic before production deployment.
Produce structured evidence showing what happened, what rule applied, and what decision path was followed.
Translate AI governance from abstract policy into repeatable operational judgement.
OBEXGATE is designed around operational control states. A pilot can test how governance rules behave when a system action is proposed.
The action is within the approved boundary and can proceed.
The action can proceed, but the user must be notified of governance risk or required documentation.
The action requires review, acknowledgement, or additional context before proceeding.
The action is outside the permitted boundary and should not proceed.
The action requires a hard stop because authority, consent, safety, or legal constraints are materially implicated.
Observer mode can be used where an organisation wants to identify governance issues without interrupting operations during early testing.
OBEXGATE pilots are best suited for organisations that need to test AI governance in real workflows, not only write governance language.
Student training, research governance, and practical scenario testing.
Clinical workflows, transcription, prior authorisation, patient data handling, secondary research use, and audit controls.
Authority, provenance, consent, local control, and secondary-use governance.
Agentic workflows, internal AI tools, shadow AI, AI-assisted decisions, and governance escalation.
Governance-aware data movement, evidence trails, authority controls, and operational oversight.
AI adoption, service delivery, accountability, escalation, and public-interest governance.
A pilot is not a legal certification, a compliance guarantee, or a substitute for legal advice. It is a structured way to test how governance requirements, authority boundaries, and operational controls behave in realistic AI and data workflows.
A pilot does not certify legal or regulatory compliance.
A pilot does not guarantee a regulatory outcome.
Legal interpretation remains with qualified legal advisers.
Production use, public naming, and case-study publication require separate agreement.
Pilots can use synthetic data or controlled scenarios where appropriate.
Define the workflow, system action, data movement, or decision pathway to be tested.
Identify the relevant governance issues: authority, consent, documentation, escalation, safety, auditability, or secondary use.
Use synthetic data or controlled scenarios to test governance behaviour.
Review where controls triggered, where ambiguity appeared, and where escalation was needed.
Determine whether the pilot should move into a deeper implementation, educational programme, research collaboration, or strategic partnership.
A local clinical encounter or controlled workflow is the starting point for the governance test.
OBEXGATE evaluates whether AI transcription, synthetic data handling, or secondary use remains within the approved boundary.
The pilot tests whether governance decisions can produce structured records of action, control, review, and outcome.
Proposed actions can be evaluated through operational control states rather than policy text alone.
We are currently prioritising pilot discussions where governance risk is operational, cross-system, or difficult to resolve through policy alone.
Suitable pilots may involve AI transcription, agentic workflows, synthetic data, student training, healthcare governance, Indigenous data governance, research use, authority boundaries, or enterprise AI controls.