Service Registry v1

Canonical service map for routes, exposure, proof, and recovery across the RPI platform.

Canonical operator map

This registry is the governed map of the current platform by service, route, class, exposure, health surface, proof source, and recovery command. When an entry is not fully proven from current evidence, it is explicitly marked as needs-verification or inferred.

/service-registry.html

Current registry summary

Service Class Route Exposure Health / Proof Evidence status
Community Sandbox / Living Labpublic-facing/community-sandbox/public/community-sandbox/api/healthinferred
Fractional CTOpublic-facing/fractional-cto.htmlpublicpage checkproven
Real Estatepublic-facing/real-estate.htmlpublicpage checkinferred
OICP dashboardpublic-facing/oicp/dashboardpublic/oicp/api/healthinferred
Sandbox Gatewayoperator-facing/publicroot routeproven
Project Charteroperator-facing/project-charter.htmlpublic/project-charter-v1.jsonproven
Service Registryoperator-facing/service-registry.htmlpublic/service-registry-v1.jsonproven
Runtime monitoroperator-facing/runtime-monitor.htmlpublic/ops-digest.jsoninferred
Webhook engineinternal platform service/webhook/pushpublic/webhook/last-eventproven
Pi-hole adminoperator-facing/admin/public302 to /admin/loginproven
LiteLLMinternal platform service/litellm/public/litellm/v1/modelsinferred
Self-eval jobsinternal platform serviceno direct public route provenlocal onlyartifact freshnessneeds-verification

Operator notes