tegwick 2f33349609 docs: add ArchitectureBlueprint for establishing config-atlas
Practical, efficiency-first blueprint: bound config-atlas to the map and
evidence layers, define the configuration-surface entry schema (modeled
on the existing capability-entry format), a read-only connector
discovery pipeline, CI validation, State Hub reuse for the config graph,
and a phased roadmap (Canon -> seed -> connectors -> explain) with a
build-vs-reuse table.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-26 19:54:35 +02:00
2026-06-26 13:44:08 +00:00
2026-06-26 13:44:08 +00:00
2026-06-26 13:44:08 +00:00
2026-06-26 13:44:08 +00:00
2026-06-26 13:44:08 +00:00

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)
Description
Configuration Control Plane for discovering, mapping, and governing the living configuration surface of fast-moving companies.
Readme MIT-0 240 KiB
Languages
Python 94.7%
Makefile 5.3%