Epic: cobolrt as a product — a COBOL runtime for Java that carries its own evidence
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 6/100
Research direction
This is a tracking epic with no files or tests named, so there is no single starting point. Begin with the principles it links (#4702 for the IBM reference and z/OS calibration, #4704 for compile and runtime options) and with the first child issue, #4711, the rule catalogue. The epic is done when every checklist item is closed, and each item needs its own scoped issue before anyone starts work.
Written by the indexing model from the issue text.
Description
Goal. Make cobolrt, the Java runtime that gives translated code COBOL's exact behaviour, a distinctive product. It's faithful to IBM z/OS under each estate's options, it carries its own evidence, it produces maintainable Java, and it offers customers an exit route instead of lock-in.
Why. Translation fidelity is almost entirely the runtime's job: nearly every correctness bug fixed on 2026-10-07/08 was a runtime rule. Competitors ship proprietary runtimes that customers must trust and license forever. Ours can be provable, customer-owned and option-aware.
Principles.
- IBM is the reference; GnuCOBOL is the instrument (#4702).
- Options are a first-class input (#4704).
- Fail loudly, never silently.
Issues
- #4711 rule catalogue: an ID, IBM reference, options and register status per rule
- #4712 rules as data: generate code, vectors and docs (first family)
- #4713 evidence report: the rules each program exercises, with calibration status
- #4714 per-estate options profile in the runtime (builds on #4704)
- #4715 more readable Java: provably-safe lifting
- #4716 exit route: production quirk telemetry, then a simplification report
- #4717 performance benchmark plus proven fast paths
- #4718 runtime as a shippable product: API, versioning, licence, docs, fail-loudly audit
Related.
- #4702: IBM reference and z/OS calibration.
- #4704: compile and runtime options.
- #4601 / #4703: evidence report.
- #4628: det-port mutation (L5).
Suggested order. 4711 → 4712 (with #4702 calibration) → 4713 and 4714 → 4717 → 4715 / 4716 → 4718 (the licence question runs in parallel with counsel).
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day