tegwick
72bbdad2c8
T02: remove inherited capability.infotech.repo-template and template consumer docs (statehub-register, template-validation-checklist); add capability.infotech.config-surface-atlas and rewrite capabilities.yaml. T03: seed 4 configuration surfaces (state-hub api-config, ops-warden routing-catalog, reuse-surface federation-sources, ops-bridge tunnel-config) with registry/indexes/surfaces.yaml; source-linked, no values, secret deps by reference. T06: add tools/validate_registry.py (schema + index gate), Makefile (make validate), and .github/workflows/validate.yml (GitHub + Gitea Actions); document in stack-and-commands. Verified malformed entries are rejected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| capabilities | ||
| indexes | ||
| surfaces | ||
| README.md | ||
Registry
Markdown-first registry for config-atlas. Two entry families:
- Configuration surfaces (
surfaces/) — the atlas's core artifact. Each entry maps a configuration surface (where it lives, owner, kind, scope, source links), validated against../schemas/surface-entry.schema.json. See../docs/configuration-surface-schema.mdfor the model and../docs/canon-mapping.mdfor ITC alignment. Index:indexes/surfaces.yaml(ATLAS-WP-0002-T03). - Capabilities (
capabilities/) — capability index for reuse-surface federation (below).
Surfaces store the map only — never live configuration values, never secret values.
Capability Registry
Markdown-first capability index for federation and reuse planning.
Authoring
- Copy a capability entry template (see reuse-surface
templates/capability-entry.template.md). - Add the row to
indexes/capabilities.yaml. - Run
reuse-surface validatefrom a checkout with the CLI installed. - Merge to
mainand verify publish withreuse-surface establish --publish-check.
Federation contract: reuse-surface docs/RegistryFederation.md.