You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The COBOL→Java path today generates a fixed Spring Boot scaffold, with Spring Boot 3.2.4, Java 17, Maven, PostgreSQL, Lombok, JPA and Batch all hardcoded, from the refactoring stage's schemas alone. The engine now extracts and verifies the whole CICS skeleton (#3445, #3489, #3575), but almost none of it reaches the Java side. This epic does two things:
makes the target configurable, via a YAML config;
makes the generator consume the verified skeleton, layer by layer.
It ends with proof that the generated code behaves like the COBOL.
Deterministic scaffolding; AI only for bounded business-logic tickets.
Every generated artifact traces to the fact it came from. Where a fact is unresolved or draft-tier, the generated code says so (a TODO naming the gap), and never guesses.
The COBOL→Java path today generates a fixed Spring Boot scaffold, with Spring Boot 3.2.4, Java 17, Maven, PostgreSQL, Lombok, JPA and Batch all hardcoded, from the refactoring stage's schemas alone. The engine now extracts and verifies the whole CICS skeleton (#3445, #3489, #3575), but almost none of it reaches the Java side. This epic does two things:
It ends with proof that the generated code behaves like the COBOL.
Order:
Principles:
🤖 Generated with Claude Code