Configuration Control Plane for discovering, mapping, and governing the living configuration surface of fast-moving companies.
tegwick
6d6f99d5ea
Mirror the five Gitea wiki pages into wiki/ (Home, ProductVision, BrandFrame, ConfigLayering, CompetitiveLandscape) as a verbatim in-repo copy. Add research/ digest on configuration layering and the configuration control plane: the resolution/merge model, the 2024-2026 config-outage case, adjacent tool families (config-as-data, GitOps drift, feature flags + AI config, secrets, policy-as-code, CMDB/portals/SSPM), a reference architecture, and an annotated bibliography of 17 sources. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| docs | ||
| registry | ||
| research | ||
| wiki | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| README.md | ||
| SCOPE.md | ||
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)