Q1 2026 extended AiMi's operational intelligence beyond change management and into incidents, while significantly broadening how notices are sourced and how much business context our agents can draw on. Managing operational risk in capital markets isn't only about changes — firms also need to track outages, service degradations, and planned maintenance and the value of that intelligence is only as strong as the breadth of sources it draws from and the specificity of the business context it applies.
Incident Management Workflow
Managing trading venue and vendor-related incidents is a time-critical operational challenges for trading and data operational teams who face a constant stream of outage alerts, delivery delays, service degradations, and maintenance updates. Each of these must be manually reconciled against their own operations to understand the source of the issue and the action required.
Our new Incident Management workflow provides a dedicated process for tracking issues, outages, and planned system maintenance, separate from changes, with a dedicated timeline, incident scope, and real-time status updates to provide a reliable and up-to-date reference point for these critical communications.
Application Inventory
As clients model increasingly complex capital markets infrastructure, the application library needed to capture more than direct relationships. Intermediary services, shared platforms, and indirect dependencies all shape whether a given change or incident actually impacts the business and who needs to act on it, and without them the agents lack the context to make accurate assessments.
Our upgraded Application Inventory evolves the existing application library into a more comprehensive inventory, supporting complex desk, application, and service relationships and the ability to define intermediary services that capture indirect infrastructure and data services, giving agents the context they need to determine whether a change or incident is impactful, what the downstream impact actually is, and who needs to be engaged.
Automated Outreach
Once an impactful change or incident has been identified, the next challenge is figuring out who inside the firm actually needs to act on it, and informing them. A technical change might require confirmation from specific application owners. A data set becoming fee-liable might require the teams consuming that data to confirm whether they still want the subscription. Firms spend significant time analysing usage and configuration data and manually coordinating outreach across application and data owners.
Combined with the expanded Application Inventory with our new agent email capability closes the loop from identification to action. AiMi uses the richer application inventory to automatically identify the specific owners impacted by each change, and then reaches out to them by email to request confirmation or action. What was previously a manual analysis and communication exercise now runs autonomously inside the platform.
Automatic Subscription Checks
Some changes are specific to a set of instruments or products, and if a firm doesn't trade or subscribe to those instruments then the change isn't relevant. Historically these still required manual review to analyse and confirm.
The Impact Agent now automatically checks instrument-related changes against defined subscriptions and sets non-impacting changes to pending close for final human verification, removing another manual step from the change review and analysis process.
Instructions
Agent context was previously split across source configuration and separate agent instructions, making it harder to understand what context the agent was acting on. Context is critical to how agents adapt to business requirements and therefore it’s important that our clients have a single, traceable record of the business knowledge that drives agent behaviour.
Our new instructions functionality consolidates existing source context and agent instructions into a single golden source of agent context. Natural language definitions allow users to describe in plain English how they want an agent to behave, either across sources or specific to a source, and this is converted into specific, traceable instructions that the agent executes.
Deep Linking
Notices frequently include attachments or link off to relevant documents and webpages with more information. Previously this supporting context stayed buried inside the original notice, making it harder to act on and easy to miss during review.
With deep linking, attachments and linked resources are extracted and surfaced directly on the notice itself, and our new change review agent maintains and updates these as the change evolves. Teams get faster, more seamless access to the full context of any notice without hunting through the source material.
Microsoft Graph Integration
Clients require transparent, clear insights into how notices are being sourced and from where. Shared and client-specific mailboxes have historically been harder to configure self-service, limiting visibility into the ingestion pipeline and creating friction when onboarding new sources.
Our Microsoft Graph integration allows for programmatic retrieval of emails, with configuration defined and managed directly within the platform. Graph enables more seamless and transparent self-service sourcing from AiMi's shared notice inbox, as well as supporting integration with clients' own mailboxes, giving teams full control over what flows into AiMi and confidence in how it got there.
Client-Specific Sources
AiMi's Service Catalogue covers a broad range of trading venues and service providers, but clients sometimes need to extend it with their own bespoke sources — whether internal platform providers or external bi-lateral relationships that sit outside the standard catalogue.
Our new client sources feature allows clients to dynamically extend the breadth and depth of coverage with bespoke sources, whilst still benefiting from a consistent and predictable set of defined services.
Telegram Integration
In the crypto and digital asset world particularly, critical notifications and circulars can be shared via Telegram channels rather than email or the web. Without native Telegram ingestion, firms trading digital assets had to manually monitor these channels or risk missing material notices entirely.
Our new Telegram integration allows these notifications to be ingested directly into AiMi alongside existing channels such as email, web monitors, and other APIs, providing a single, centralised, and comprehensive sourcing platform that covers both traditional and digital asset operations.
API Integration
Clients increasingly want to pull AiMi's intelligence into their own internal systems and workflows.
Our new RESTful API endpoints enable direct integration with internal and third-party platforms for seamless, composable workflows. Clients can connect directly to the API to pull a list of recently created or updated changes as well as the specific details of each associated change, making it easy to feed AiMi's structured outputs into any downstream process.
Looking Ahead
Q2 2026 builds on the foundations delivered in Q1 to provide more real-time insight and broader workflow coverage: a dedicated system management dashboard, a new projects view that combines related changes and incidents into an epic-style perspective, a centralised document repository to support spec-driven development, and a dedicated workflow for managing exchange corporate actions, streamlining one of the most critical and complex processes in capital markets operations.