Skip to content

repos: env-defs 申报入图——环境期望态定义仓 L0（W1-C2） #428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
randypanding merged 1 commit into from
Aug 29, 2026
Merged

repos: env-defs 申报入图——环境期望态定义仓 L0（W1-C2） #428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions governance/REPOS.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,6 +179,17 @@ repos:
key_paths: [accounts.yaml, cnb_pool.py, work-inbox.yaml, REMOVAL.md]
entry_protocol: true # ADR-0095：协议块 v2 全仓下发（drift §17 逐字节对账）

- name: env-defs
layer: L0
Comment on lines +182 to +183

@qodo-code-review qodo-code-review Bot Aug 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. L0 onboarding map stays stale 🐞 Bug ⚙ Maintainability

Adding env-defs as L0 leaves the PM Playbook’s explicit “L0 governance repositories” count and
list without the new repository, so onboarding readers receive a contradictory layer map instead of
the newly declared topology. That same sentence already misclassifies archive as L0 even though
the registry declares it L1, and this change is the appropriate point to synchronize the sibling
enumeration.
Agent Prompt 
## Issue description
The new L0 `env-defs` declaration makes the PM Playbook’s hard-coded L0 repository count/list stale, while that list also incorrectly places `archive` in L0.

## Issue Context
`governance/REPOS.yaml` is the organization-map source of truth. The onboarding summary should either match it or avoid maintaining a duplicate exhaustive enumeration.

## Fix Focus Areas
- governance/REPOS.yaml[182-183]
- docs/pm/PLAYBOOK.md[31-34]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

visibility: public
status: active
role: 环境期望态定义仓（三面分离声明面载体，IR-0006 W1-C2 / ADR-0103 决策 5）——
environments/*.yaml 声明云内网 dev/staging 期望态（topology/allowlist/Vault
引用/tenant）；reports/ 为漂移快照落点（W4-R1 泛化 drift 对账引擎消费）；
secret 只记引用名值永不进 git（INV-04）
key_paths: [environments/, reports/]
entry_protocol: true # ADR-0095：协议块 v2 全仓下发（drift §17 逐字节对账）


# 上游依赖（ADR-0085：openjiuwen 双上游随编排框架退役停止消费；未来引入新上游时
# 恢复本节声明——部署渲染 pin tag 的治理方式不变）
Expand Down