Files
manage/openspec/changes/archive/observability-service-registry/.pi-map.md
T
Developer 38b2de54ff chore: archive observability-service-registry, track pi-map artifacts
- Archive the completed observability-service-registry SDD change into
  openspec/changes/archive/ (delivered across 5 slices; only
  jellyfin-service-registry remains active).
- Stop ignoring .pi-map.md / .pi-map.index.md so the navigation maps are
  versioned alongside the code, and add the regenerated map pairs repo-wide.
2026-06-24 13:28:23 +00:00

1.3 KiB

openspec/changes/archive/observability-service-registry

dir: openspec/changes/archive/observability-service-registry

index: openspec/changes/archive/observability-service-registry/.pi-map.index.md

role

Proposal and design documentation package detailing the migration of observability services from environment-variable configuration to a dynamic service registry model.

files

  • design.md | Design document describing the migration of observability services from environment-variable configuration to a dynamic service registry model.
  • proposal.md | This file is a technical proposal document outlining changes to migrate observability services (Alertmanager, Grafana, Prometheus) from environment variables to a first-class service registry.
  • tasks.md | Task breakdown document detailing a 5-slice implementation plan for migrating observability services (Alertmanager, Grafana, Prometheus) to a service registry pattern with UI-based configuration.

arch

OpenSpec change-documentation pattern consisting of three structured Markdown artifacts: a proposal (intent), a design (technical approach), and tasks (implementation breakdown).

tags

design, document, observability, services, service, registry, proposal, environment

symbols

workflows

dirty