generated from coulomb/repo-seed
tegwick
7078eaf596
Customize config-atlas identity (INTENT, SCOPE, AGENTS, rules), document dev workflow commands, remove inherited repo-seed workplans, and add ATLAS-WP-0002 registry foundation workplan.
58 lines
2.3 KiB
Markdown
58 lines
2.3 KiB
Markdown
# INTENT — config-atlas
|
|
|
|
> Repository purpose and boundary. Governance file for agents and contributors.
|
|
|
|
## One-liner
|
|
|
|
Federated configuration atlas for the Coulomb ecosystem — cataloging configuration
|
|
surfaces, schemas, defaults, ownership, and cross-repo relationships.
|
|
|
|
## Purpose
|
|
|
|
`config-atlas` exists because configuration knowledge is scattered across repos,
|
|
deployment manifests, environment variables, feature flags, policy files, and
|
|
operator runbooks. Without a shared atlas, agents and humans rediscover the same
|
|
configuration surfaces repeatedly and cannot reason confidently about defaults,
|
|
precedence, or ownership.
|
|
|
|
The atlas treats each **configuration surface** as a first-class, registry-backed
|
|
entry: what it configures, where it lives, who owns it, how it is validated, and
|
|
which capabilities or repos consume it.
|
|
|
|
## Core stance
|
|
|
|
- **Discoverable over tribal knowledge** — if a configuration surface matters to
|
|
reuse or operations, it should be indexed here or linked from here.
|
|
- **Source-linked** — atlas entries point at canonical files or APIs; the atlas
|
|
does not become a second source of truth for live config values.
|
|
- **Agent-friendly** — markdown and YAML registry formats that coding agents can
|
|
orient from without bespoke tooling.
|
|
- **Federated** — downstream repos remain authoritative for their own config; this
|
|
repo aggregates indexes, relationships, and documentation.
|
|
|
|
## In Scope
|
|
|
|
- Configuration surface registry (schemas, indexes, capability entries)
|
|
- Cross-repo configuration relationship maps
|
|
- Documentation of discovery, contribution, and validation workflows
|
|
- State Hub workplans and agent instructions for atlas maintenance
|
|
|
|
## Out of Scope
|
|
|
|
- Storing secret values or live environment-specific configuration
|
|
- Owning application runtime or deployment execution
|
|
- Replacing repo-local configuration files or secret stores (OpenBao, etc.)
|
|
- Acting as the canonical repo template (`repo-seed` owns that)
|
|
|
|
## Current State
|
|
|
|
- Bootstrapped from `repo-seed` on 2026-06-26; State Hub registration complete.
|
|
- Identity files customized; bootstrap workplan ATLAS-WP-0001 in progress.
|
|
- Registry still carries inherited template artifacts — see ATLAS-WP-0002.
|
|
|
|
## Getting Oriented
|
|
|
|
- Boundary: `SCOPE.md`
|
|
- Agent instructions: `AGENTS.md`
|
|
- Workplans: `workplans/`
|
|
- Registry: `registry/` |