Recipients
0
Primary
GatewayOverviewDecision RoomExecutive OverviewExecutive AwarenessCurrent SituationAI AnalystLoading governed environmental evidence…
Daily Situation Distribution
The scheduled email is generated from the same Decision Room model and evidence hash. Delivery status is operational metadata and never changes the environmental state.
Distribution mode
Daily at 05:00 UTC
Recipients
0
API key
Missing
Sender
Missing
Public URL
Missing
Cron secret
Configured
Send secret
Missing
Recipients
Recipient identities are loaded from server environment variables and are masked in the interface.
No recipients configured. The system remains in preview mode.
Preview
Classification: TECHNICAL UNREVIEWED DAILY SITUATION · Evidence hash 131feac7e6e015af…
UNIOREVIS™ DAILY SITUATION Classification: TECHNICAL UNREVIEWED Decision posture: NO DECISION REQUIRED No current technical condition has crossed the transparent review boundary. This is not a guarantee of environmental stability and remains limited by source coverage. Current basin evidence Euphrates: AVAILABLE, 3/3 points, 100% completeness Tigris: AVAILABLE, 3/3 points, 100% completeness Needs attention No current technical review items. Evidence completeness: 100% Satellite evidence view: CONFIGURED_EVIDENCE_VIEW; analysis NOT_CALCULATED Physical stations: 6 planned, 0 active Source cutoff: 2026-08-28T17:24:08.995Z Evidence hash: 131feac7e6e015afcadbdc1738023f3e47a2dbcd54794439d330b1f932c1b28d Decision Room: http://localhost:3000/decision-room This automated message supports human review. It is not an institutional decision, emergency declaration, Strategic Signal, Risk Clock state or approved external report.
Schedule
The package configures one daily invocation at 05:00 UTC. CRON_SECRET protects the endpoint when configured in Vercel.
Manual control
Manual sending is server-only and requires a separate NOTIFICATION_SEND_SECRET. The secret must never be exposed in a client component.
Failure boundary
Preview mode is active until a verified sender, RESEND_API_KEY and at least one enabled recipient are configured.
The API returns per-recipient provider message IDs and failures. Durable delivery history requires the optional database migration or provider records; this package does not fabricate a successful delivery log.