config-atlas/registry
tegwick 4620244f39 feat(explain): complete ATLAS-WP-0004 — graph edges, blast-radius, determinism tests
T05: tests/test_effective_config.py (6 tests) — order-independence, most-specific
winner, no value/secret leak; wired into make validate + CI.
T04: tools/blast_radius.py + make blast-radius — consumers, transitive dependents
(cycle-safe), secret refs, fan-out risk band.
T03: tools/config_graph.py + make graph/graph-query — emit config-typed edges to
registry/indexes/graph.yaml (queryable by surface id); staleness check in the gate.

WP-0004 finished (5/5). Read-first control-plane MVP complete: explain, graph,
and blast-radius over the seeded surfaces.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-27 00:16:58 +02:00
..
capabilities feat(registry): complete ATLAS-WP-0002 T02, T03, T06 2026-06-26 23:19:18 +02:00
indexes feat(explain): complete ATLAS-WP-0004 — graph edges, blast-radius, determinism tests 2026-06-27 00:16:58 +02:00
surfaces feat(registry): complete ATLAS-WP-0002 T02, T03, T06 2026-06-26 23:19:18 +02:00
README.md feat(registry): complete ATLAS-WP-0002 T04 (canon mapping) + T01 (surface schema) 2026-06-26 22:47:40 +02:00

Registry

Markdown-first registry for config-atlas. Two entry families:

Surfaces store the map only — never live configuration values, never secret values.

Capability Registry

Markdown-first capability index for federation and reuse planning.

Authoring

  1. Copy a capability entry template (see reuse-surface templates/capability-entry.template.md).
  2. Add the row to indexes/capabilities.yaml.
  3. Run reuse-surface validate from a checkout with the CLI installed.
  4. Merge to main and verify publish with reuse-surface establish --publish-check.

Federation contract: reuse-surface docs/RegistryFederation.md.