---
id: ATLAS-WP-0002
type: workplan
title: "Configuration atlas registry foundation"
domain: infotech
repo: config-atlas
status: ready
owner: codex
topic_slug: custodian
created: "2026-06-26"
updated: "2026-06-26"
state_hub_workstream_id: "27b42720-1bd7-4755-ab2f-59a6d095a2c3"
---

# Configuration atlas registry foundation

Replace inherited `repo-seed` template artifacts with config-atlas-specific
registry scaffold and establish the configuration surface model.

## Define configuration surface schema

```task
id: ATLAS-WP-0002-T01
status: todo
priority: high
state_hub_task_id: "125a4ad3-ddd4-4aee-bb94-9433a5fa4651"
```

Document the configuration surface model: required fields (id, name, owner,
source path, scope, validation), naming conventions, and index file layout.
Add schema docs under `registry/` (e.g. `registry/README.md` expansion and a
`docs/configuration-surface-schema.md` reference).

## Replace inherited template registry

```task
id: ATLAS-WP-0002-T02
status: todo
priority: high
state_hub_task_id: "2d8e41e9-ba93-4a1a-862b-993da03df1f9"
```

Remove `capability.infotech.repo-template` and other repo-seed artifacts from
`registry/`. Add the config-atlas capability entry and update
`registry/indexes/capabilities.yaml`. Remove or relocate inherited template
consumer docs (`docs/template-validation-checklist.md`,
`docs/statehub-register.md`) — those belong in `repo-seed`.

## Seed initial configuration surfaces

```task
id: ATLAS-WP-0002-T03
status: todo
priority: medium
state_hub_task_id: "9b8bb1c2-a6ee-4b6e-91a4-2cd902fb52ff"
```

Index 3–5 high-value configuration surfaces already present in the ecosystem
(e.g. State Hub API config, warden routing catalog, reuse-surface registry
layout). Each entry must link to canonical source files, not duplicate values.

After workplan file updates, run from `~/state-hub`:

```bash
make fix-consistency REPO=config-atlas
```