Epic: estate readiness scanner — a deployable scan that tells each customer what GitGalaxy can translate and prove, and what it must learn
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
Research direction
This is a tracking epic with no code change of its own. Start with the charter in #4722, which needs owner review before the children begin, then read the existing pieces it builds on: the engine scan, cics_census, fact_crosscheck, and the rule catalogue in #4711. Done means the epic's six child issues are closed, and the readiness report is produced offline for a sample estate.
Written by the indexing model from the issue text.
Description
Goal. One deployable scan that, run on a customer's mainframe code, answers:
- what their system uses;
- what GitGalaxy can already translate and prove;
- what it would refuse;
- what it must learn for them, ranked by programs unlocked.
It also measures each estate against our definition of done (#4722).
Why.
- It turns "is this big?" into a per-customer, measurable gap list.
- It works as a pre-sales assessment (offline, no source leaves).
- Aggregated across customers, it lets demand decide what we build next.
Builds on what exists:
- the engine scan;
cics_census;- the blockers ranking (#4587);
- translate-only refusals;
fact_crosscheck;- evidence records and levels;
- the rule catalogue (#4711);
- options intake (#4704 / #4709).
Issues
- #4722 Charter: definition of done
- #4723 feature inventory extractor
- #4724 support matrix (inventory × rule catalogue × refusals)
- #4725 readiness report + ranked rules-to-learn
- #4726 deployable offline package (no source leaves)
- #4727 cross-customer feedback loop
Suggested order. #4722 (charter, owner review) → #4723 → #4724 (benefits from #4711) → #4725 → #4726 → #4727.
Related.
- #4710: cobolrt as a product.
- #4702: IBM reference and z/OS calibration.
- #4704 / #4709: options and intake.
- #4703: evidence report.
- #4270: CICS breadth.
🤖 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