stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity
Files
981f4459a265d408e2ffbcb11d71d5f94e870c3c
git.stella-ops.org/src/Doctor/README.md
master 9393baf1ad feat(platform,binaryindex,doctor): runtime persistence cutover 
Sprint SPRINT_20260415_005_DOCS_platform_binaryindex_doctor_real_backend_cutover.

- Platform.WebService: AoC/quota compatibility endpoints, platform health
  service, setup wizard contracts/endpoints/service, release migrations
  058 (trust signing demo seed) + 067 (cleanup), context migration tests.
- BinaryIndex.WebService: golden-set controller + storage extensions,
  runtime persistence extensions, durable runtime + storage registration
  tests.
- Doctor: scheduler runtime guard, report storage extensions,
  scheduler + webservice registration tests.

Sub-sprints _006 (symbols truthful manifest) and _021 (doctor evidence
schema registry) land as follow-ups.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-19 14:37:20 +03:00

1.4 KiB
Raw Blame History

Doctor

Container(s): stellaops-doctor-web, stellaops-doctor-scheduler Slot: 26 (web), scheduler | Port: 8080 | Consumer Group: doctor, doctor-scheduler Resource Tier: light

Purpose

The Doctor service runs diagnostic health checks across the entire Stella Ops platform. It uses a plugin architecture covering core services, databases, service graphs, integrations, security, observability, Docker, attestation (Rekor/Cosign), verification (SBOM/VEX/signature/policy), release pipelines, environment health, scanner/reachability, compliance/evidence, binary analysis, and timestamping (eIDAS). The Doctor Scheduler automates periodic diagnostic runs with trend analysis and alerting.

API Surface

  • doctor (via Router) — diagnostic run execution, report retrieval, timestamping dashboard
  • doctor-scheduler (via Router) — schedule management for periodic doctor runs, trend queries

Storage

PostgreSQL-backed report storage in the web service (ConnectionStrings:StellaOps or Database:ConnectionString). Durable Doctor scheduling and trend ownership live in the Scheduler service's DoctorJobPlugin; the deprecated standalone doctor-scheduler now remains dev/test-only and fails fast outside Development/Testing.

Background Workers

  • DoctorScheduleWorker (scheduler service) — executes scheduled diagnostic runs via HTTP calls to Doctor API