Organization-level policy source for operator configuration
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading RFC-0001 September 2026 revision (#499) and RFC-0002 organization question inbox (#500), which this issue identifies as related. Work through the listed design questions: policy location and trust, precedence, allowed settings, and how org-scoped answers interact with policy. Done means those choices are specified, while user-level operator configuration remains out of scope.
由索引模型根据 Issue 内容生成。
描述
Summary
darnit is moving tool configuration (which checks and commands run, which plugins and MCP servers are trusted, storage backends, LLM budgets, policy for how project assertions are treated) out of the audited repository and into operator configuration: configuration owned by whoever runs darnit, starting at the user level.
This issue tracks the follow-on: an organization-level policy source that an operator can choose to trust, so an org can set shared policy once for every repository it audits.
Scope to design
- Where org policy lives (for example the org-level
.projectrepository) and how an operator declares that they trust it, including pinning to a reviewed revision. - Precedence: built-in defaults, then user-level operator configuration, then trusted org policy, then per-run flags. Nothing from an audited repository enters this chain.
- Which settings org policy may set (policy such as frameworks, levels, confirmation expiry, treatment of project assertions) versus settings that stay with the individual operator (credentials, local execution, budgets).
- How org-scoped answers (for example an org security contact) relate to org policy, so a question answered once applies across repositories.
Out of scope
User-level operator configuration itself, which is being specified first.
Related: RFC-0001 September 2026 revision (#499), RFC-0002 organization question inbox (#500).
- 主要语言
- Python
- 星标
- 22
- 派生
- 27
- 平均合并
- 1 天 20 小时
- 30 天内合并 PR
- 39
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
darnitdevorg/darnit 的其他 Issue
-
`darnit validate` crashes on openssf-baseline.toml summarising levels可能已有人在做 @i-am-paradox 于 2 天前认领。 未关闭needs triage
难度 2/5 1-3 小时 新手友好度 78/100
darnitdevorg/darnit#589 ·
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 83/100
darnitdevorg/darnit#587 ·
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 65/100
darnitdevorg/darnit#585 ·
维护者通常 1 天内回复
-
quality
难度 2/5 1-3 小时 新手友好度 66/100
darnitdevorg/darnit#523 ·
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 1-3 小时 新手友好度 76/100
darnitdevorg/darnit#516 ·
维护者通常 1 天内回复
查看 darnitdevorg/darnit 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
jbacalso24/mimry#291 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 1 小时以内 新手友好度 82/100
eli-alvarado/us-watchlist-alerts#14 ·
维护者通常 1 天内回复
-
from-review-extraction python severity:nit
难度 2/5 1-3 小时 新手友好度 80/100
LearningCircuit/local-deep-research#7462 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
cathrynlavery/diagram-design#441 ·
维护者通常 2 天内回复
-
[Cleanup] Include the public header in work_split.cpp可能已有人在做 @blozano-tt 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
tenstorrent/tt-metal#60850 ·
维护者通常 1 天内回复