T04: add docs/canon-mapping.md mapping config-atlas concepts to InfoTechCanon
(itc-gov/data/devsecops/land/org/access/sec/tag) and sibling repos with
consume/reference/align/own ownership, plus gaps, validation hooks, and
extension candidates. Resolves the (planned) refs in PRD and ecosystem-boundaries.
T01: add schemas/surface-entry.schema.json (Draft 2020-12, additionalProperties
false to forbid inline values/secrets), docs/configuration-surface-schema.md
(fields, kind taxonomy, L0-L9 ordering, explicit merge rules), a validating seed
entry (surface.infotech.state-hub.api-config), and expand registry/README.md.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Realign ATLAS-WP-0002 to ArchitectureBlueprint Phase 0-1 and the PRD MVP:
add context/exit-condition/sequencing, refine the three existing tasks
with acceptance criteria, and extend with three new tasks (T04 canon
mapping, T05 surface.* namespace + reuse-surface federation, T06 CI
validation). Existing task ids and state_hub_task_ids preserved.
Archive finished ATLAS-WP-0001 to workplans/archived/ with date prefix
per the workplan convention.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add specs/ProductRequirementsDocument.md: hybrid product PRD (sister-repo
skeleton plus the template's Formal Standards / Related Concepts /
Appendix sections), heavy FR/NFR with Requirement/Details/Acceptance
triplets, Canon Alignment, 12 functional + 8 non-functional requirements,
conceptual model, MVP, roadmap, risks, and orientation-map appendix.
Substance traces to INTENT, ArchitectureBlueprint, ecosystem-boundaries,
and the research digest; no scope invented beyond repo-boundary.
Fix relative links broken by the ArchitectureBlueprint.md move into
specs/ (its own INTENT/SCOPE/research links and the ecosystem-boundaries
back-reference).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add docs/ecosystem-boundaries.md: per-repo boundary table, overlap
hotspots and resolutions (control-plane/scope/resolver vs
feature-control, vocabulary vs info-tech-canon, connectors vs
repo-scoping, ownership vs domain-tree, schema/federation vs
reuse-surface), and concrete reuse actions mapped to the blueprint
roadmap.
Tighten .claude/rules/repo-boundary.md to name all five sister repos
with their consume/reuse/reference/link relationships and scope
config-atlas to its novel core.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Practical, efficiency-first blueprint: bound config-atlas to the map and
evidence layers, define the configuration-surface entry schema (modeled
on the existing capability-entry format), a read-only connector
discovery pipeline, CI validation, State Hub reuse for the config graph,
and a phased roadmap (Canon -> seed -> connectors -> explain) with a
build-vs-reuse table.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Harmonize the federated-registry framing with the now-articulated
control-plane north star. Add a North star section scoping this repo to
the map and evidence layers (not resolution/delivery/control), two core
stances (effective-configuration goal, map-before-control), sharpen
in/out of scope, and record the wiki mirror, research digest, and
ATLAS-WP-0001 completion.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Mirror the five Gitea wiki pages into wiki/ (Home, ProductVision,
BrandFrame, ConfigLayering, CompetitiveLandscape) as a verbatim in-repo
copy.
Add research/ digest on configuration layering and the configuration
control plane: the resolution/merge model, the 2024-2026 config-outage
case, adjacent tool families (config-as-data, GitOps drift, feature
flags + AI config, secrets, policy-as-code, CMDB/portals/SSPM), a
reference architecture, and an annotated bibliography of 17 sources.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
