coulomb/config-atlas
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: tighten sister-repo boundaries and reuse decisions

Browse Source 
Add docs/ecosystem-boundaries.md: per-repo boundary table, overlap
hotspots and resolutions (control-plane/scope/resolver vs
feature-control, vocabulary vs info-tech-canon, connectors vs
repo-scoping, ownership vs domain-tree, schema/federation vs
reuse-surface), and concrete reuse actions mapped to the blueprint
roadmap.

Tighten .claude/rules/repo-boundary.md to name all five sister repos
with their consume/reuse/reference/link relationships and scope
config-atlas to its novel core.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-06-26 21:08:20 +02:00
parent 2f33349609
commit dd5b405300
3 changed files with 157 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
.claude/rules/repo-boundary.md
View File

@@ -1,11 +1,21 @@
## Repo boundary
This repo owns **config-atlas** only — the federated configuration surface
registry and its documentation. It does not own:
This repo owns the **read-only, cross-kind configuration map and evidence layer** —
the federated configuration surface registry and its documentation. Its novel core
is the cross-kind surface classification, the layering order, and effective-config
*path* rendering. Everything else is referenced, not owned.
It does **not** own (sister repo → relationship):
- Configuration *vocabulary* / concepts (`info-tech-canon`) — **map, don't redefine**
- Repository *scanning / candidate / approval* machinery (`repo-scoping`) — **reuse**
- *Domain placement & ownership identity* (`domain-tree`) — **reference**
- The *registry schema & federation hub* (`reuse-surface`) — **federate under it**
- *Runtime resolution & control* of feature availability, incl. resolver and kill
switches (`feature-control`) — **link, never re-derive**
- Repo template bootstrap (`repo-seed`)
- Capability reuse registry (`reuse-surface`)
- Secret storage or live config values (`railiance-platform` / OpenBao)
- Feature flag control plane (`feature-control`)
- State Hub implementation (`state-hub`)
- Deployment and infrastructure execution (`railiance-infra`, `ops-bridge`)
- Secret *values* / live config (`railiance-platform` / OpenBao) — reference only
- State Hub graph/identity store (`state-hub`) — contribute config-typed edges
- Deployment and infrastructure execution (`railiance-infra`, `ops-bridge`)
See `docs/ecosystem-boundaries.md` for the full boundary-and-reuse analysis.