generated from coulomb/repo-seed
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>
research/
Deep-research notes backing ConfigAtlas — the configuration control plane for discovering, mapping, explaining, and governing the living configuration surface of fast-moving companies.
This directory is the evidence layer for the product thesis. It is not part of
the configuration surface registry (registry/); it is the reasoning and sourcing
behind the registry's design choices.
Contents
| File | What it is |
|---|---|
configuration-control-plane.md |
Main digest: what the configuration control plane is, why it matters, the layering and resolution model, adjacent topics, and where ConfigAtlas fits. |
sources.md |
Annotated bibliography — every cited source with a one-line note on why it matters. |
Related repo material
../wiki/ConfigLayering.md— the layering primer (scope model, precedence, merge rules, mutability classes).../wiki/CompetitiveLandscape.md— adjacent tool families and white space.../wiki/ProductVision.md/../wiki/BrandFrame.md— product framing.
Method
Synthesized 2026-06-26 from the repo's own wiki material plus web research across
vendor docs, primary-source engineering writing (Brian Grant / KRM, InfoQ, CUE),
and 2024–2026 outage retrospectives. Sources captured in sources.md; claims tied
to live behavior of tools are dated because this category is moving fast.