Vea Ops Intelligence

The Business Problem

A repeated service failure can sit in a spreadsheet without an owner, a deadline, or a note of what was already tried. This prototype demonstrates that workflow. It has not been validated as a production operations system.

Verified Capabilities

• Issue register

  Create an issue with severity, owner, channel, region, an affected-customer estimate, a loss estimate, and an SLA target. Search and filter by status. The sample organisation is Meridian Connect.

• CSV import and export

  Rows can be imported from a CSV in the browser and exported back out. A sample file is included with the application.

• Investigations and corrective actions

  A case keeps root-cause notes, status, and severity. Actions have an owner, a due date, and a completion toggle.

• Deadlines on the browser clock

  Open issues are labelled overdue when the due time is earlier than the browser clock. Deadlines can be edited. No email, SMS, or scheduled escalation is sent.

• Impact arithmetic, shown as arithmetic

  Unresolved exposure is the sum of estimated loss on issues that are not resolved. Affected customers are a sum and may overlap. Resolution rate is resolved records divided by all records. These are not booked loss, recovered revenue, or a forecast.

• Sentinel control checks

  Sentinel is a screen inside this application, not a separate product. It runs five explicit rules on the current browser records: overdue issues, estimated exposure at or above ₦1,000,000, investigations missing notes, resolved issues that still have open actions, and a category that appears more than once. A result is pass or attention. It is not an AI score, and the demo does not save an immutable control-run ledger.

• Local automation preview

  Rule switches live in the browser. A simulated incoming event can open or correlate an investigation, a failing control can create a finding, and an overdue scan can stage a local flag. The screen states that no email and no external system are contacted.

• Event API scaffold

  POST /api/v1/events checks a server-side ingest token and the payload shape, then returns the normalised event. A 202 means validated only. The event is not stored and no automation runs.

Who It Is For

• Someone reviewing the operations demo
• The fictional Meridian Connect workspace in the prototype

Scope & Technical Boundaries

• Prototype v0.2. The application’s own readme says it is not production-ready enterprise software.
• Issues, rules, and the automation log are stored in the browser’s localStorage. There is no login, and role names on the settings screen are illustrative.
• Meridian Connect and its issue records are synthetic. Do not type confidential, personal, or regulated data into the demo.
• CSV import works in the demo. Microsoft Graph, Jira Cloud, and ServiceNow are labelled as planned adapters. The CRM card is marked for discovery. None of those are connected.
• Sentinel reads only the records already in that browser. It does not query banking systems, network infrastructure, or another product.
• Storage runs in the browser demo session; database adapters and server-side RLS can be connected for enterprise multi-tenancy.
• The business intelligence screen inside VeaPay is a different product. It reads that money application’s own demo books.