Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- Proxy owns route and mTLS policy decisions, not secrets issuance, financial ownership or application authorization.
- Public and internal route ordering must reject accidental API fallthrough to static assets.
Verification still required
- Validate live TLS termination, configured peer identity, callback ingress and active upstream network paths in an authorized deployment.
- Cross-service certificate handshake and application-level authorization must both be checked; a healthy proxy is not business authorization.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.