ZITRANX AI
Understand the system nobody left documentation for, then move it without breaking it.
Most modernisation programmes fail at the first step: nobody can say with confidence what the current system actually does. ZITRANX reads the estate — COBOL, PL/SQL, JCL, stored procedures, the monolith everyone is afraid of — and produces behaviour documentation, a dependency map and a characterisation test suite before a single line is rewritten.
Understand first. Translate second. Prove it throughout.
Every stage produces an artefact you can review independently. You can stop after any of them and still be better off than when you started.
Static analysis across source, copybooks, JCL, schedules and database schemas builds a complete call graph and data-lineage map — including the paths that have not executed in a decade.
Agents extract the business rules the code actually implements and write them in prose your domain experts can dispute. Every rule cites the lines it came from.
Production traffic is sampled into a characterisation test suite that pins current behaviour, including the bugs downstream systems now depend on.
Target services are generated subsystem by subsystem, run in parallel against live traffic, and only promoted when the equivalence suite passes clean.
The rewrite is never the hard part.
Nothing cuts over until the behaviour matches.
Translated code is run in parallel against production traffic, and every divergence is a ticket. The characterisation suite generated during the understanding phase is the contract — not a developer's reading of what the COBOL was probably for.
How ZNYX governs the agents→What architects ask first.
Most estates start with a two-week assessment on a single subsystem. You get the dependency map and the honest verdict on feasibility whether or not you continue.
Book an estate assessment→No. A single subsystem with its copybooks and job control is enough for the two-week assessment. Analysis is read-only and can run inside your environment.
Most commonly Java or C# services, and Python where the workload suits it. The target is a decision made after the assessment, not before — sometimes the honest answer is to leave a subsystem where it is.
It is idiomatic code structured around the recovered domain rules, with the characterisation suite as its regression tests. If your engineers cannot read it, we have not finished.
We will say so. Some subsystems should be encapsulated behind an API and left alone, and some should be retired rather than moved. The assessment tells you which.
ZITRANX runs as a set of GuideLite agents, and every step those agents take is evaluated by ZNYX against your policy. The governance is the same one the rest of the suite inherits.
Works with
Point us at the subsystem nobody wants to touch.
Two weeks, one subsystem, read-only. You get the dependency map, the behaviour documentation and an honest verdict on whether translation is the right answer at all.
Book an estate assessment→