Write the decision before changing the system
This guide is a planning exercise for an application operator. It does not represent a PrivacyNodes deployment, support action or measured customer result. Decide whether the endpoint answers liveness, readiness or a bounded dependency check; do not blur those purposes into a large diagnostic page. Return a small status without configuration, customer identifiers or dependency credentials.
Rehearse the change with controlled inputs
Use an unauthenticated response only when the routing design requires it. Test an authorized application path separately, because a health response cannot prove business permissions, migrations or worker completion.
Use synthetic requests and test identities while checking the change. Do not expose secrets or customer data in a command, log excerpt or support note.
Verify the outcome and record the remaining limit
During a dependency failure, verify that the response changes in the documented way without amplifying load. Record which monitor or maintainer owns the next action.
Capture UTC time, artifact or configuration revision, redacted symptoms and the next owner.
Official reference
This source was reviewed for the technical boundary in this guide; it does not document a PrivacyNodes test or provider capability.