COBOL doesn’t need a translator. It needs an agent loop.
COBOL doesn’t need a translator. It needs an agent loop. PRAXO-CORE is a native GnuCOBOL implementation of a governed agent contract. The point is not “AI for COBOL.” The point is keeping the execution boundary inside t
COBOL doesn’t need a translator. It needs an agent loop.
PRAXO-CORE is a native GnuCOBOL implementation of a governed agent contract. The point is not “AI for COBOL.” The point is keeping the execution boundary inside the runtime that already owns the work.
What is different
•63 normative vectors across 11 groups.
•Source tag cobol/v0.8.0; no package-registry claim.
•policy, tools, checkpoints, events, HITL.
What is not claimed
•JSON 32 KB / 512 nodes / 64 nesting; lexical path policy; email-only redaction; GnuCOBOL verified, IBM z/OS not claimed.
•Full Go parity, IBM z/OS, production readiness, a security certification.
A bridge or sidecar is often the right engineering choice. This post is about the trade-off, not a claim that every COBOL estate should embed a loop.
Read the full article
Canonical article: https://architect.pub/cobol-native-agent-praxo-core
Repo: https://github.com/axisvela/praxo-core Docs: https://axisvela.github.io/praxo-core/languages/cobol/
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.