slug: spring-boot
provider: Spring Boot
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Metrics
  spec_file: spring-boot-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: GET /prometheus  getPrometheus  Spring Boot Prometheus metrics scrape endpoint
  reason: Metric name listing, metric measurements and a Prometheus scrape endpoint are plainly metrics
    instrumentation for production monitoring, i.e. Observability Management.
- tag: Health
  spec_file: spring-boot-health-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: GET /health  getHealth  Spring Boot Application health information
  reason: Health and per-component health endpoints are the standard surface scraped by monitoring systems
    to make a running service understandable in production, which is Observability Management. Health
    checks are borderline plumbing, hence 0.7 rather than higher.
- tag: Loggers
  spec_file: spring-boot-loggers-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /loggers/{name}  setLoggerLevel  Spring Boot Set logger level at runtime
  reason: Listing and adjusting logger levels at runtime governs the log telemetry emitted by the running
    service, which sits in Observability Management (logs, metrics, traces).