generated from coulomb/repo-seed
tegwick
dd5b405300
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>
config-atlas
Federated configuration atlas for the Coulomb ecosystem — cataloging configuration surfaces, schemas, defaults, ownership, and cross-repo relationships.
Orient
cat INTENT.md
cat SCOPE.md
cat .custodian-brief.md
ls workplans/
Registry
Configuration surface entries live under registry/. After registry or workplan
edits, sync with State Hub:
cd ~/state-hub && make fix-consistency REPO=config-atlas
Validate registry structure (from a reuse-surface checkout):
reuse-surface validate --root /home/worsch/config-atlas
Governance
- INTENT.md — why the atlas exists and core principles
- SCOPE.md — in/out scope and current state
- AGENTS.md — agent session protocol and workplan conventions
- workplans/ — canonical work items (ADR-001)