Tamper-evident gate log + resource-budget gate kind
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by inspecting .chock/log/gate-events.jsonl and how the existing gate kinds record and evaluate decisions. The issue proposes both a tamper-evident hash chain and a rate_limit gate, with the latter relying on the former; done means both capabilities are implemented and the budget gate can enforce an operation count within a time window.
Written by the indexing model from the issue text.
Description
Two related upgrades to the evidence-and-limits story
1. Hash-chain the gate event log. .chock/log/gate-events.jsonl records every gate decision, but nothing makes it tamper-evident — an entry can be edited or deleted silently. Chaining each entry to the hash of the previous one (and periodically anchoring the head hash in a commit) turns the log into auditable evidence at near-zero cost. This closes the repudiation gap the threat-intel baseline tracks: the mechanism exists, the auditable claim about it does not.
2. A resource-budget gate kind. The baseline's resource-overload threat (runaway loops, cost blowups) is currently marked not-expressible: no gate kind can say 'no more than N of this operation per hour'. A declarative rate_limit gate kind (op pattern + count + window, evaluated against the hash-chained log above — which is what makes the counter trustworthy) would make circuit-breakers a policy an adopter can install rather than infrastructure they must build.
The two compose: the budget gate is only as honest as the log it counts, which is why the chain comes first.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 114
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 open-coder-ai/chock
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-coder-ai/chock#238 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-coder-ai/chock#231 ·
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 85/100
open-coder-ai/chock#133 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 3/5 Half a day Newbie friendliness 68/100
open-coder-ai/chock#132 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 5/5 Over a week Newbie friendliness 45/100
open-coder-ai/chock#131 ·
Maintainers usually reply within 1 day
All issues in open-coder-ai/chock
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
huggingface/smolagents#2976 ·
Maintainers usually reply within 1 day
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FuRongJun-1999/dsh-memory#170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgvector/pgvector-python#163 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#3940 ·