COMMISSIONED · AGREED SCOPE
Research & validation
Bounded research on system behaviour, incidents or evidence methods. Externally directed work requires a funded agreement.
Explore Applied Research →PARTNERSHIPS
Explore a funded project or a clearly governed contribution that strengthens operational AI assurance. Start with the question, the available record and the permissions needed to examine it.
A relationship does not determine a finding. Externally directed technical work requires an agreed paid scope.
Discuss a collaboration →WHY COLLABORATE
A collaboration should produce a defined output: a documented method, authorised dataset, interface specification, control mapping, bounded examination result or research insight. Agree its intended use, confidentiality, ownership and publication rights at the outset.
BEFORE TECHNICAL WORK
Initial discussions establish fit and commercial scope. Technical analysis, study design, validation and advisory work begin only under an agreed paid scope, after independence and data-handling checks and payment.
Please do not send confidential records, personal datasets or credentials with your first enquiry.
Exploring alignment does not authorise joint technical work or use of ODA3 Institute’s methods, marks or findings.
WORKING PATHWAYS
A pathway is chosen for the work, not for a partner designation.
COMMISSIONED · AGREED SCOPE
Bounded research on system behaviour, incidents or evidence methods. Externally directed work requires a funded agreement.
Explore Applied Research →EXPLORATORY · IN DEVELOPMENT
Research into provenance and traceability across governance, engineering and operational systems. No operating connector or API is promised.
Explore the interoperability direction →COMMISSIONED · AGREED SCOPE
Mappings, terminology, control specifications and evidence requirements, with publication status and limitations explicit.
Explore Standards Development services →EXPLORATORY
Translate established methods into exercises and learning. External training collaboration has separate readiness and commercial terms.
Discuss practitioner collaboration →ENGAGEMENT METHOD
Confirm competence, conflicts, authority, funding and data permissions. Agree outputs, ownership and publication rights before examination.
Agree the system, claim, records, access, exclusions and acceptance basis.
Document provenance, criteria, supported findings, conflicting evidence and unresolved limits.
Reuse methods, interfaces or publications only within the agreed rights.
CURRENT QUESTIONS
These are research interests, not claims of operating products, established partners or completed projects. Structures and tooling remain in development.
INDEPENDENCE & DISCLOSURE
Funding, system access and collaboration do not establish endorsement or assurance. Preserve missing, conflicting and negative results alongside supported findings.
Operational records may inform reusable methods only under expressly agreed authorisation, confidentiality, privacy and publication terms.
START A COLLABORATION
A useful first note identifies the system or method, the specific question, the available non-confidential record, your authority to engage and the intended funded output.
This establishes fit and scope; technical analysis begins under a paid agreement.