UK DUAA right to complain enforces in -- days · 19 June 2026 EU AI Act high-risk enforces in -- days · 2 August 2026

Pilot discussions

Pilot discussions for applied AI governance

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.

Why pilot with OBEXGATE?

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.

Authority

Authority at execution

Define who has authority over a workflow, data use, system action, or escalation point.

Controls

Operational governance controls

Test when an AI or data action should be allowed, warned, held, blocked, or stopped.

Evidence

Audit-ready evidence

Produce structured records showing what rule applied, what action was requested, what control was triggered, and what human review occurred.

Testing

Real-world workflow testing

Use synthetic or controlled scenarios to test governance behaviour before live operational exposure.

Learning

Applied learning

Help teams understand how governance works in practice, not only how it is described in policy.

Current pilot traction

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.

Status: pilot partner secured, public naming pending

New Zealand pilot focus

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.

Clinical

Clinical patient use case

A controlled clinical scenario for testing governance at the execution layer.

Synthetic

Synthetic data

Synthetic data enables governance testing without exposing private or live sensitive data.

Transcription

AI transcription

AI transcription governance can be tested before operational use creates avoidable exposure.

Authority

Consent and authority boundaries

Controls can evaluate provenance, consent, authority, escalation, and secondary research use.

University pilot pathway

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.

Education

Applied governance for students

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.

Status

Pilot awaiting signed agreements

The pathway is in discussion and will only be described publicly in more detail after appropriate agreements are signed.

What an OBEXGATE pilot can test

Workflow

AI and data workflow governance

Test how rules apply when data moves across systems, teams, models, vendors, or use contexts.

Authority

Authority boundaries

Define who can approve, deny, escalate, or override a proposed AI or data action.

Consent

Consent and secondary use

Examine whether a proposed use remains within the original permitted purpose or requires additional review.

Transcription

AI transcription and summarisation

Test governance controls around clinical, educational, administrative, or operational transcription workflows.

Synthetic

Synthetic scenario testing

Use synthetic data and controlled scenarios to validate governance logic before production deployment.

Audit

Audit and evidence trails

Produce structured evidence showing what happened, what rule applied, and what decision path was followed.

Education

Student or workforce education

Translate AI governance from abstract policy into repeatable operational judgement.

From policy to control

OBEXGATE is designed around operational control states. A pilot can test how governance rules behave when a system action is proposed.

Allow

Within the approved boundary

The action is within the approved boundary and can proceed.

Warn

Proceed with governance notice

The action can proceed, but the user must be notified of governance risk or required documentation.

Hold

Review before proceeding

The action requires review, acknowledgement, or additional context before proceeding.

Block

Outside the permitted boundary

The action is outside the permitted boundary and should not proceed.

Stop

Hard stop required

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.

Who should discuss a pilot

OBEXGATE pilots are best suited for organisations that need to test AI governance in real workflows, not only write governance language.

Universities

Applied AI governance education

Student training, research governance, and practical scenario testing.

Healthcare

Healthcare and life sciences

Clinical workflows, transcription, prior authorisation, patient data handling, secondary research use, and audit controls.

Indigenous data

Indigenous data governance organisations

Authority, provenance, consent, local control, and secondary-use governance.

Enterprise

Enterprise AI teams

Agentic workflows, internal AI tools, shadow AI, AI-assisted decisions, and governance escalation.

Platforms

Data infrastructure and platform companies

Governance-aware data movement, evidence trails, authority controls, and operational oversight.

Public sector

Public sector and civic institutions

AI adoption, service delivery, accountability, escalation, and public-interest governance.

What a pilot is not

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.

Not certification

Not a legal certification

A pilot does not certify legal or regulatory compliance.

Not guarantee

Not a compliance guarantee

A pilot does not guarantee a regulatory outcome.

Not legal advice

Not a replacement for legal counsel

Legal interpretation remains with qualified legal advisers.

Not deployment

Not a production deployment unless separately agreed

Production use, public naming, and case-study publication require separate agreement.

Controlled data

Not dependent on private live data

Pilots can use synthetic data or controlled scenarios where appropriate.

How a pilot discussion works

01

Scope

Define the workflow, system action, data movement, or decision pathway to be tested.

02

Classify

Identify the relevant governance issues: authority, consent, documentation, escalation, safety, auditability, or secondary use.

03

Simulate

Use synthetic data or controlled scenarios to test governance behaviour.

04

Evaluate

Review where controls triggered, where ambiguity appeared, and where escalation was needed.

05

Decide

Determine whether the pilot should move into a deeper implementation, educational programme, research collaboration, or strategic partnership.

Pilot governance model

Local clinical use

Workflow context

A local clinical encounter or controlled workflow is the starting point for the governance test.

Execution boundary

Authority and consent checks

OBEXGATE evaluates whether AI transcription, synthetic data handling, or secondary use remains within the approved boundary.

Evidence

Provenance record and audit trail

The pilot tests whether governance decisions can produce structured records of action, control, review, and outcome.

Control states

Allow, Warn, Hold, Block, Stop

Proposed actions can be evaluated through operational control states rather than policy text alone.

Discuss a pilot with OBEXGATE

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.

OBEXGATE pilots are designed to support governance testing, documentation, and operational control design. They do not provide legal advice, legal certification, or a guarantee of regulatory compliance.