Standing policy from instruction files, behind an explicit trust step
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by tracing the classifier gate and the ungated write path, then review the user-level ~/.omp/agent/AGENTS.md and repository AGENTS.md trust boundaries. The /classifier trust-policy flow should pin user-file hashes, exclude repo-local authorization, and require gate-measured facts for conditional rules; done means policies cannot authorize destinations or delete targets.
Written by the indexing model from the issue text.
Description
Standing approvals in instruction files ("keep merging when green", deploy rules per repo) authorized 29 of the 119 intent false positives in the week the plan (#70) measured, and the gate never reads them.
Reading them naively is a forgery channel: the agent can edit ~/.omp/agent/AGENTS.md or a repo AGENTS.md with the ungated write tool, and session N+1 would snapshot the edit as user policy. Conditional rules ("merge when CI is green") also can not be checked by the judge.
Sketch:
/classifier trust-policypins a hash of the user-level files; only a pinned hash is read.- Repo-local instruction files never authorize.
- Policy can authorize an action class, never an egress destination or a delete target.
- A conditional rule authorizes only when a gate-measured fact confirms the condition.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2h 10m
- Merged PRs (30d)
- 64
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 STRML/omp-classifier
-
Decide whether a coordinator may lift a headless worker's refusal (the trust boundary #68 defers)Openenhancement ready-for-human
Difficulty 5/5 Over a week Newbie friendliness 25/100
STRML/omp-classifier#142 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-human
Difficulty 4/5 3-5 days Newbie friendliness 45/100
STRML/omp-classifier#116 · 7 comments ·
Maintainers usually reply within 1 day
-
enhancement ready-for-human
Difficulty 5/5 Over a week Newbie friendliness 35/100
STRML/omp-classifier#13 · 6 comments ·
Maintainers usually reply within 1 day
All issues in STRML/omp-classifier
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day