Take governed AI delivery to the mainframe core.
Integrators now show banks and insurers how to run AI as a governed engineering capability. The hardest place to apply that is the mainframe core: policy administration, billing and accounting systems that are thirty or more years old. Cobra is the specification library, AI harness and execution environment built for those systems. It works beside the conversion and transformation tooling you already use.
A governed model needs four things the core does not have.
A specification library
Agents with managed context
A harness that validates AI output
Knowledge that outlives individuals
The missing pieces, for core systems.
- Specification library
- Business rules written as decision tables. Each row is one rule, linked to its source line, with an automated test that proves it.
- Managed context
- The Dictionary: 90+ read-only tools that give any agent authoritative facts about programs, records, fields, call chains and data lineage.
- Skill registry
- A library of version-controlled agent skills that carry hard-won mainframe lessons from one program to the next.
- AI harness
- Gates in the delivery pipeline that measure the result, not the artefact. A test must check a value the real program computed. A test that cannot fail is rejected.
- Human on the loop
- Graded autonomy. At the lowest level agents take work to a human gate. At the highest, a rule-based controller merges work only when every check passes. Changes to test data always stop for a person.
- Evidence
- Every finding links to the line of code it came from. Results are labelled as measured or inferred. Data access is labelled by sensitivity and logged.
Three steps in a joint engagement.
Assessment
Pilot on one domain
Scale
| You | Filix and Cobra |
|---|---|
| Client relationship, operating model, role transformation | Core-system specification library and AI harness |
| Your delivery framework and governance | Mainframe execution environment and the Dictionary |
| Programme delivery at scale | Mainframe and insurance domain depth |
| Regulator engagement | Evidence that goes back to each line of code |
A joint pilot is the right way to take the platform into live delivery. For discussions about the intellectual property itself, see For acquirers.
What is proven, and what is not yet.
A supplier that tells you where the edge is can be checked. One that does not, cannot.
| Built and working | Yes | Everything described on this site runs today. |
|---|---|---|
| Proven against real client production code and data | Yes | Three client estates run under test every week. |
| Running a client’s live operation | Not yet | That is the next step, and we do not claim otherwise. |
- Scenario 2: An insurer wants billing off the mainframe first
- Scenario 3: A change in regulation arrives in the middle of the programme
Each compares the default approach with the Cobra approach.
Partner conversations come direct to Michael.
No sales queue. Tell us which client situation you have in mind and we will show you what Cobra would contribute. partners@filix-it.com
