estate-crucible: era profiles -- era-tagged horrors with release-specific IBM citations, mixed-era strata, per-era scores

Open
  • Is something wrong?
#5,118 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
testing, tooling

Research direction

The first half of this work is a generator PR in the separate squid-protocol/estate-crucible repository, which the issue says to clone outside the home directory; the gitgalaxy part starts at tests/crucible_pins.toml and tests/tools/estate_crucible_gate.py. Done means per-era scores appear in the gate summary and baseline while the modern-strata ratchet stays unchanged. Scope is design work across two repositories and is not a first-timer task.

Written by the indexing model from the issue text.

Description

enhancement era:0 legacy-modernization needs:crucible priority: medium scope:frontier

What: give the estate crucible (squid-protocol/estate-crucible, the synthetic z/OS estate whose generator writes both the code and the answer key) an era profile: each planted construct ("horror") carries an era tag and cites the IBM manual for that CICS/COBOL release; add era-1 and era-0 strata (BLL cells, SERVICE RELOAD, HANDLE CONDITION flows, FCT/PCT/PPT/DCT macro tables, DL/I calls, macro-level programs) mixed into one estate with the modern strata -- the cross-era seams (a BLL program LINKing an ADDRESS OF program, COMMAREA passed between them) are the point. Then in gitgalaxy: bump the pin in tests/crucible_pins.toml and make tests/tools/estate_crucible_gate.py report a score per era next to the overall ratchet.

Where: the generator change is a PR on squid-protocol/estate-crucible (clone it under /srv/storage_16tb/projects/gitgalaxy-worktrees/, never under /home/joe/Projects); the pin + gate change is a gitgalaxy PR after it merges.

Acceptance: era-tagged horrors with release-specific IBM citations; per-era scores in the gate summary and baseline; existing ratchet unchanged for the modern strata.

Context (owner-approved 2026-10-14): our CICS corpus is almost all eras 3-4 (CardDemo, CBSA, GenApp are modern demos) on top of well-modelled old COBOL semantics. Real estates are layered: 1980s programs LINK 1990s ones that call 2010s Db2 code in one region. Era model used here (approximate; the scanner should cite evidence, not dates):

Era ~When CICS COBOL Tells
0 ~1969-80 macro level (DFHPC/DFHFC, CSA/TCA) ANS 68 DFHxx macro calls, no EXEC CICS
1 ~1978-88 CICS/VS 1.x command level OS/VS COBOL (74) BLL cells + SERVICE RELOAD, HANDLE CONDITION/AID, DL/I, FCT/PCT/PPT/DCT macro tables
2 ~1988-96 CICS/MVS 2.x, CICS/ESA 3-4 VS COBOL II / COBOL 85 ADDRESS OF / SET ADDRESS, RESP/RESP2, EXEC SQL, CSD (RDO), DPL
3 ~1996-2005 CICS TS 1-2 COBOL for MVS/OS390, LE MQ, EXCI, 3270 bridge, web
4 2005+ CICS TS 3+ Enterprise COBOL channels/containers, SOAP/JSON, async, named counters

Order: after the current CI work and CICS blocker work (owner). Siblings: the five "era" issues filed together.

🤖 Generated with Claude Code

Dominant language
Python
Stars
57
Forks
11
Avg merge
1h 35m
Merged PRs (30d)
975

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from squid-protocol/gitgalaxy

All issues in squid-protocol/gitgalaxy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.