Skip to content

Readiness scanner: feature inventory extractor — every COBOL/CICS/SQL feature, data type and option an estate uses, with program counts #4723

Closed

Description

@squid-protocol

What. From an estate's sources (plus JCL and bind cards where present), produce a structured inventory of what the estate uses, each with how many and which programs use it:

  • statement forms;
  • data types and PICTURE features (P-scaling, COMP-1/2, national, edited);
  • CICS commands and options;
  • SQL forms (static/dynamic, cursors, WHENEVER, …);
  • intrinsic functions;
  • compile options (from CBL/PROCESS cards and JCL PARM);
  • copybook resolution gaps.

Builds on: the engine scan, cics_census (CICS/SQL command counts), det source.py / layout.py / stmt.py parsing, and fact_crosscheck.

Acceptance.

  • A deterministic JSON inventory with a schema.
  • Run on all burned estates and committed as fixtures.
  • Unknown or unparsed constructs are counted explicitly, not dropped.

Part of the estate readiness scanner epic (linked from the epic). Owner-approved direction, 2026-10-08.

🤖 Generated with Claude Code

Activity

  1. added
    enhancementNew feature, sensor, or structural signature
    legacy-modernizationCOBOL refractor, dead-code extraction, and JCL forging
    priority: highCore feature broken, but workarounds exist
    on Oct 8, 2026
  2. added a commit that references this issue on Oct 9, 2026
    e25d7f4
  3. added
    scope:coreBlocks a burned-estate program's next evidence rung, or the 4th-estate one-shot trial
    on Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature, sensor, or structural signaturelegacy-modernizationCOBOL refractor, dead-code extraction, and JCL forgingpriority: highCore feature broken, but workarounds existscope:coreBlocks a burned-estate program's next evidence rung, or the 4th-estate one-shot trial

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions