fix: clarify runtime durability health contract
This commit is contained in:
@@ -177,6 +177,14 @@ non-durable until the schema, migration ledger, and read readiness gates are
|
||||
proven through the configured adapter. Documenting or testing this contract
|
||||
must not mutate runtime state or PROD.
|
||||
|
||||
`/health` and `/health/live` expose this split in `readiness.durability`.
|
||||
`dbLiveEvidenceObserved=true` with
|
||||
`dbLiveEvidenceIsDurabilityEvidence=false` means the DB TCP/live layer is
|
||||
separate from runtime persistence. If runtime durability is blocked,
|
||||
`blockedLayer` names the current adapter/auth/schema/migration/durability query
|
||||
layer, and `requiredEvidence` remains the durable adapter schema, migration,
|
||||
and read query contract.
|
||||
|
||||
## Runtime Substitution Ban
|
||||
|
||||
UniDesk services, provider-gateway, backend-core, microservice proxies, local
|
||||
|
||||
Reference in New Issue
Block a user