AI Trust Forum - New York
About this Event
New York - AI Trust Forum
The AI Trust Forum is special.
It brings together brilliant thinkers, innovators, policymakers, and practitioners to learn, build relationships, and work together personally solving AI engineering, business, legal and ethical challenges at retreats held in cities around the world. That’s why we call it a “Forum”, not a “Conference”.
What happens at the Forum?
Keynotes
Visionary sessions from global leaders framing the most pressing engineering, business, legal, and ethic issues in AI to spark strategic insight and set the agenda.
Open Working Sessions
Small group collaboration tackling specific challenges in AI alongside leaders in the space. Participants ideate, whiteboard, and contribute to publicly shareable work.
Town Halls
Expert-led open discussion where attendees interrogate pressing topics, exchange diverse perspectives, and brainstorm possible courses of action.
Symposium Sessions
Presentation showcasing original research, innovative practice, or notable case studies that attendees can use in their work building Trustworthy AI back home.
See our website for more information about this event: AITrustForum
Click to register your interest, and secure your place at this unmissable forum.
Agenda is subject to change
Agenda
🕑: 09:00 AM - 10:30 AM
Opening Keynote
Host: Avishan Bodjnoud
🕑: 10:40 AM - 11:40 AM
AI Diligence in Transactions and Steady State
Host: To be announced
Info: AI diligence frameworks are now published and in active use. What will be asked is knowable in advance. Whether your organization can answer is not.
This session covers what serious questioners demand across proprietary AI, third-party AI, deployment, training data, and generative outputs. In a transaction, those answers move valuation, deal structure, and risk allocation. But the deal is only the most concentrated form of a pressure that never stops: procurement questionnaires, insurer underwriting, board fiduciary exposure, and the diligence every organization performs when it buys AI.
Two findings transfer everywhere. Absence of evidence is itself a finding. Interviews reveal more than documents. Everything a serious questioner asks for is either an artifact a well-run AI program produces, or evidence that no such program exists.
Leave with the questions you'll be asked, an honest read on what you can answer with evidence, and a structure for questioning your own vendors.
🕑: 11:50 AM - 12:50 PM
AI Strategy Trends from Real Orgs in 15+ Countries
Host: Andrew Welch
Info: Neither a market forecast nor a vendor's view of the world. This is what has actually been observed leading this work with organizations across more than fifteen countries and six sectors: where the money is going, where it is being wasted, which capabilities reliably separate the organizations pulling ahead, and how the picture differs by region and by sector. It draws on maturity assessments run against five pillars and twenty-five dimensions, so the patterns are measured rather than anecdotal.
Expect some uncomfortable findings, among them the averaged-score trap, where visible strength in a few dimensions conceals weakness in the ones carrying real weight. And expect the aggregate answer, which is that nearly every organization in the world still sits somewhere between reactive and proactive, whatever its press releases say.
What attendees leave with: a candid benchmark against peer organizations, and a sharper sense of which current investments are load-bearing.
🕑: 12:50 AM - 02:00 PM
Lunch and Networking
🕑: 01:50 PM - 02:50 PM
Stuck at Ten Agents: What Must be True Before you say "Yes"
Host: To be announced
Info: Building an agent is no longer the hard part. Letting it loose in the business, with real permissions and money on the line, is. Most organizations stall around ten: every new agent forces leaders to reason about the risk from first principles, and a team can only do that so many times.
A rule in a document cannot stop anything. It shapes design, but the moment an agent acts, something in the running system has to allow it, refuse it, or hand the decision to a person. Testing shows how a system behaved on cases someone wrote down. Runtime control governs the case nobody anticipated, at 3am.
Model capability will not constrain your AI portfolio next year, and neither will budget. The number of things you can allow will. Organizations that make approval reusable say yes in an afternoon; the rest say it in quarters.
Leave with what to require before approving an agent for production, and an answer for your next board meeting.
🕑: 03:00 PM - 04:00 PM
8 Symptoms, 1 Cause: Why your Estate, Not your Model, Decides What Agents Do
Host: To be announced
Info: The diagnosis, drawn from decades inside complex, regulated businesses, fits almost every estate: a new product needs a code release; pricing owners can't change pricing; work arrives as documents and leaves as typing; nobody can say who changed a record or whether it was allowed. Each is a fact about how the systems are arranged, not how the business is run. They share one cause. When systems can't talk to each other, each keeps its own copy of the rules.
Before an agent acts, it must ask whether it may. The question has no answer unless one place knows the entities and the authority rules, and one point enforces authorization and keeps an immutable record of every call. Systems of record, surfaces, and models can vary. The domain model and the gateway cannot.
The session closes on where human judgment should sit once software does the assembling, and which fix comes first.
Leave with your version of the eight symptoms, and a sequencing argument for your budget conversation.
🕑: 04:10 PM - 04:55 PM
Closing Keynote
Host: Dona Sarkar
Info: Microsoft's Director of Enterprise AI Advocacy closes the day on what she sees inside organizations: the ones that make the leap, the ones that stall, and the difference between them, which is rarely what leadership believes it is.
The second half is ask and answer. Put your real problem to the room, whatever the day has surfaced or failed to resolve. Often the answer turns out to be someone three seats away who solved it eighteen months ago, and those introductions are made deliberately and followed up after the event rather than left to the coffee queue. It is the part of the day the Forum takes most seriously. Published knowledge is durable, but a peer who will take your call next year is worth more.
What attendees leave with: a straight answer from someone who sees hundreds of these programs, at least one introduction worth having, and a next step that fits their organization.
Working Sessions
🕑: 11:00 AM - 01:30 PM
Working Session A - Getting and Keeping Agents in Production (at Scale)
Host: Chris Huntingford
Info: Building an agent is no longer the hard part. Keeping a population of them running inside a real organisation is. This session takes on the machinery that decides whether agents survive contact with the organisation's real work, and it stays deliberately platform-neutral: identity and permissions, ownership and who gets called at night, cost and consumption, observability, versioning and change control, retirement, and the problem of the agents nobody registered.
It is work rather than talk. Attendees put their own blockers on the table at the start, the group sorts them into the patterns that keep recurring, and the remainder of the time is spent building shared answers to the ones most of the room holds in common. The conversation stays at the level where it transfers, so that a bank or a public sector agency can use a version of the same answer, with each participant's specifics as the worked examples.
🕑: 12:50 PM - 01:50 PM
Lunch and Networking
🕑: 02:00 PM - 04:00 PM
Working Session B - Human Context Protocol and the AI Workforce of the Future
Host: To be announced
Info: Every organisation runs on context its people hold implicitly. Who decides what. What gets escalated, to whom, and how fast. What good work looks like. What is never done regardless of who asks. Almost none of it is written down, and agents inherit none of it. The Human Context Protocol is an open line of work on making that context explicit enough that mixed teams of people and agents can operate against it: leadership capabilities, decision rights, and the operating norms of teams whose members are not all human.
This is a drafting session. What is a role when part of it is performed by an agent? Where does accountability sit when the work was assembled by software and approved by a person? What must digital fluency mean now? What do regulators already expect an organisation to demonstrate about the competence of its people? The work stays at the level of the protocol rather than any one sector, with participants' own situations as the test cases.
Where is it happening?
Event Location & Nearby Stays:
GBP 0.00
