Turn scattered signals into a reviewable decision.
Inspect original imageSentinelMesh brings maritime, energy-market, cyber, weather, and news signals into one crisis-intelligence interface. The public project connects a Next.js command center, Gemini-backed specialist agents, a Cloud Run gateway, and Supabase Edge services, with a separate citizen briefing view.
Signals from a shipping corridor, port technology, and fuel markets arrive in different forms. The system needs to assemble their evidence, distinguish live information from fallback content, and give an operator a reviewable decision before turning it into public guidance.
I built SentinelMesh solo, from the Next.js operator interface and citizen briefing view to the specialist-agent workflow, deployment gateway, and Supabase integration. I defined the source/fallback boundaries and the human approval step for consequential actions.
Source Watchtower gathers evidence, Corridor Sentinel examines route exposure, and Cyber Guard assesses infrastructure risk. Policy Gate and Citizen Brief handle approval and communication. This separation makes the documented workflow easier to inspect than one undifferentiated model response.
The policy gate requires human review for market-moving decisions. The system can assemble evidence and draft guidance while keeping that decision boundary visible to the operator.
The documented architecture sends frontend API traffic through Cloud Run to Supabase Edge. Firebase uses method-preserving 307 redirects for those requests, so a POST keeps its method when reaching the gateway. Supabase can persist source snapshots, agent runs, and mission briefs.
Public sources include energy references, weather information, and vulnerability intelligence. When fully open vessel data is insufficient, the demo uses simulated movement. That distinction matters when reading the globe and risk panels: a complete-looking interface is not proof that every displayed signal is live.
Collect the available public maritime, market, weather, news, and cyber signals, with fallbacks for unavailable sources.
Route the evidence through the documented corridor-risk and cyber-risk agent stages.
Apply the policy gate and require human approval for consequential decisions.
Present the reasoning to operators and translate it into the simpler citizen briefing interface.
The visual evidence is the repository-published dashboard in demo mode. It demonstrates the interface and agent workflow; it is not a record of an operational crisis response.
Some sources need credentials, exact cargo information is constrained by data access, and vessel movement can be simulated. The Nasiko integration is an adapter and registration path; the broader native orchestration features described in the roadmap are not all implemented. The app can run without database persistence, so an available interface alone does not establish a durable audit record.