config-atlas/registry/capabilities/capability.infotech.config-surface-atlas.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance
capability.infotech.config-surface-atlas	Configuration Surface Atlas	Read-first, cross-kind map and evidence layer for configuration surfaces — what configures a system, who owns it, its scope, and where the source of truth lives.	config-atlas	draft	infotech	configuration registry control-plane effective-config evidence	discovery availability current target confidence rationale D5 D6 medium Intent, scope, layering model, competitive landscape, and a control-plane research digest are documented (INTENT, SCOPE, research/, wiki/, PRD, ArchitectureBlueprint). Boundaries vs sister repos are explicit. current target confidence rationale A0 A2 medium Markdown/YAML registry with a JSON Schema for entries; no runtime resolver or API (intentionally — resolution is delegated). Consumed informationally and by agents; a source-module validator exists under tools/.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C2 low scope_vs_intent_and_consumer_expectations configuration-surface entry schema (schemas/surface-entry.schema.json) scope/precedence/merge model (docs/configuration-surface-schema.md) canon mapping to InfoTechCanon (docs/canon-mapping.md) seed configuration surfaces (registry/surfaces/) runtime effective-value resolution configuration delivery or control execution secret value storage level confidence basis known_reliability_risks R2 low consumer_quality_signals schema and surface seed are early; coverage is partial ownership resolution to domain-tree not yet wired	intent includes excludes assumptions use_cases research_memos Make the distributed configuration surface of the ecosystem discoverable, explainable, and governable — map the territory before controlling it. configuration-surface registry and entry schema scope/layer ordering and explicit merge semantics cross-repo relationship and effective-config path modelling canon alignment and sister-repo boundary documentation runtime resolver, delivery, or control plane secret values or live configuration values feature-availability runtime control (feature-control owns it) downstream repos remain authoritative for their own config reuse-surface federation and the State Hub graph are available research/configuration-control-plane.md docs/configuration-surface-schema.md	current_level target_level current_artifacts consumption_modes A0 A2 registry/surfaces/ schemas/surface-entry.schema.json docs/configuration-surface-schema.md docs/canon-mapping.md tools/validate_registry.py informational source module	depends_on supports related_to capability.statehub.workstream-coordinate capability.registry.register	documentation tests INTENT.md SCOPE.md specs/ProductRequirementsDocument.md specs/ArchitectureBlueprint.md docs/ecosystem-boundaries.md tools/validate_registry.py	recommended_for not_recommended_for known_limitations discovering what configures a system and who owns it reasoning about defaults, precedence, and cross-repo config relationships storing or resolving live configuration values secret management or feature-flag runtime control early-stage schema and partial surface coverage effective-value resolution is out of scope by design

Configuration Surface Atlas

config-atlas indexes configuration surfaces — bounded, named places where configuration is defined, read, or overridden — as source-linked registry entries with ownership, kind, scope, and evidence. It is the read-first map and evidence layer of a configuration control plane; it does not resolve, deliver, or control configuration (see SCOPE.md, docs/ecosystem-boundaries.md).

See docs/configuration-surface-schema.md for the entry model and docs/canon-mapping.md for InfoTechCanon alignment.