evidence report: list the runtime rules each program exercises, with their calibration status
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the coverage instrumentation in cobolrt and the det sweep, since the issue says rule usage should be recorded there, keyed by rule ID. Then find where the evidence report is generated per program and how evidence-record staleness is computed. Done means each program's report lists the rules it executes with their calibrated, assumed, or declared-difference status, and a change to the rule set marks existing evidence records stale.
Written by the indexing model from the issue text.
Description
What. Record which catalogue rules a proof actually executes (coverage instrumentation in cobolrt, keyed by rule ID). Show per program: the rules used, and how many are z/OS-calibrated, assumed, or declared differences. For example: "uses 37 rules: 35 calibrated, 2 assumed (C11, C14)".
Why. This turns the oracle caveats into a per-program, buyer-readable statement. It's the core differentiator: a runtime that carries its own evidence.
Acceptance.
- Rule usage is recorded by the det sweep.
- The rule list is shown in the evidence report per program.
- Evidence-record staleness accounts for rule-set changes.
Part of the cobolrt-as-a-product epic (linked from the epic). Owner-approved direction, 2026-10-08.
🤖 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