Decision record
SEND UNCONFIRMEDOutcome: send unconfirmed, provider acceptance unresolved- Operation
- op_5b9e8d7a
- Request
- req_5b9e8d7a
- Tenant
- UniversalHealthCare.ai
- Subject
- UHC-PT-00674synthetic
Provider acceptance unresolved · no blind retry · investigation required.
Every gate passed and dispatch was authorized, but the provider send response was lost in transit. No provider message id came back, so acceptance is unresolved. Regent does not retry blind — the operation waits for a provider-backed identifier or an operator.
Timing
Regent's freshness guarantee begins when Regent receives the push. The snapshot timestamp inside the request is tenant-asserted metadata and is never the basis of that guarantee; data age before the push is the tenant's pipeline responsibility.
Versions in effect
AI judgment
Context · pre-agent hard stops
- ContactabilityActive WhatsApp channel on the tenant connection.evidence: computed by RegentPASS
- Crisis flag / global opt-outNo crisis flag. No global opt-out. The judgment engine received this case.evidence: tenant-assertedPASS
Judgment · AI proposal
- AI judgmentSEND — appointment reminder due within 24 hours.evidence: computed by RegentINFO
Governance · rules run after the proposal
- Proposal-specific consentConsent scope covers appointment logistics. No revocation on record.evidence: tenant-assertedPASS
- Frequency cap (2 of 3)Two contacts used in the current period against a tenant cap of three.evidence: computed by RegentPASS
Action · dispatch
- Governed dispatchDispatch authorized and attempted at 09:05:52 UTC. The provider send response was lost; no provider message id was returned.evidence: provider-authoritativeINFO
- Provider acceptanceUnresolved. Recipient-and-timestamp matching against saved status webhooks is a heuristic and never establishes acceptance. No blind retry is permitted; the state resolves on a provider-supported identifier or by an operator.evidence: provider-authoritativeINFO
Dispatch state
Provider acceptance unresolved · no blind retry · investigation required. When the provider send response is lost, no provider-backed correlation exists. Matching on recipient and timestamp is a heuristic that can support investigation, and it never establishes acceptance. The state stays unknown until a provider-supported identifier resolves it, or an operator resolves it manually.
Evidence
Exact inputs, policy versions, model version, gates and recorded outcome are preserved and integrity-verifiable on demand. Inspect reconstructs the recorded decision context — the inputs, versions, gates and outcome exactly as they were. It does not re-run the model or promise an identical regenerated answer.