Comment by le-mark

I’ve witnessed two legacy migration projects, both failed. One was a source translation to Java, this one failed because they didn’t have the expertise to manage production Java applications and pulled the plug. The other was a rewrite that went over budget and was cancelled.

> HyperDocs ingests COBOL, JCL, and PL/I codebases to generate documentation, architecture diagrams, and dependency graphs.

Lots of tools available that do this already without AI.

> The goal is to build digital “twins” of the experts on how they debug, architect, and maintain these systems in practice.

That will be a neat trick, will the output be more than sparsely populated wiki?

My experience is there’s not a lot of Will or money to follow these things through.

Edit to add there was a lot of work around business rule extraction, automatic documentation, and static analysis of mainframe systems in 90s leading up to Y2K, but it all fizzled out after that. You all should search the literature if you haven’t.