Evidence rail · marketing landing LIVE · not a mill
From a COBOL copybook to signed evidence — not a bond
Banks and insurers modernizing legacy COBOL still need lineage they can show a supervisor. The migration can emit that lineage. This on-ramp describes a pathway — cobolbridge.ai apex is HTTP 200 as a marketing landing (not a mill, not MEASURED). Read SPEC.md. Council of AI turns published lineage into an independent, Ed25519-signed measurement pack when a signed card exists. This is not a tokenized market and not a rating. We do not certify.
1 · the problem
Legacy COBOL still runs the core — and the evidence burden is growing
Widely reported (per Communications of the ACM): around $3 trillion of daily commerce flows through COBOL systems, roughly 40% of US banking systems run on it, and an estimated 220 billion lines remain in active use. These are external figures — a description of the landscape, not a Council of AI measurement.
Modernizing that core now runs straight into a widening set of duties that all ask the same thing: show the lineage, and show the controls held across the change.
Fully applicable since 17 January 2025. ICT risk management, resilience testing, and a register of critical functions — all needing traceability through a migration.
Principles for effective risk-data aggregation and reporting: complete, accurate, and traceable data lineage across the systems being modernized.
Controls and traceability over financial reporting — which a change to the core ledger systems must not silently break.
Member States transpose by January 2027. Governance and data-quality expectations for insurers, reaching into the legacy systems that hold the book.
2 · the bridge
Lineage out of the migration — mill not MEASURED yet
Instead of a rewrite that loses the paper trail, the intended mill instruments every mapping and transformation as data, so the lineage a supervisor asks for falls out of the work rather than being reconstructed after the fact. That mill is not MEASURED (no signed card). Domain cobolbridge.ai apex is HTTP 200 as a marketing landing — do not demo it as a live mill.
Field-level mapping from COBOL copybooks to modern schemas, captured as data — not left implicit in a rewrite.
A record of what moved where: source record, transformation, destination — the lineage regulators ask for during a migration.
Each transformation step is traceable, so control continuity can be shown across the cutover rather than asserted.
CICS, IMS, JCL and VSAM surfaced as documented, callable interfaces — the boundary the evidence is drawn around.
3 · the on-ramp to signed measurement
Lineage in, a signed measurement pack out — and it keeps running
The lineage and evidence a migration produces is the raw material for an independent Council of AI measurement pack: Ed25519-signed, three-state (UNMEASURED / measured / refused), and reproducible from a published method. A one-off migration becomes continuous measurement snapshots — re-run the measurement on a schedule and keep the signed snapshots. Not certification.
4 · the honest boundary
What this is — and what it is not
- ◆We measure and attest. We do not certify. A signed Council of AI measurement is independent evidence, never a conformity mark or a pass/fail badge.
- ◆cobolbridge.ai apex is HTTP 200 as a marketing landing (not a mill). The Council of AI measurement is independent of it — a signed card is about the evidence, not an endorsement of a migration, and none exists yet.
- ◆The determination of compliance stays with the competent authorities — supervisors and regulators. Our pack is an input they can verify, not their decision.
Bring us your migration
If you are modernizing a COBOL core under DORA, Basel III/IV, SOX or Solvency II, the lineage you have to produce anyway can become continuous measurement snapshots. Talk to us about the on-ramp. Verify is free; a grade is never sold; there are no public prices. We do not certify.
