Project Info
Inspiration
Three researchers walked into TreeHacks and picked the hardest problem we could find: predict the future. Not metaphorically. Literally. We wanted to build a system that watches the physical world and knows what's about to go wrong — before it happens. Every year, preventable accidents in warehouses, factories, and autonomous systems cost lives and billions of dollars. The technology to prevent them exists — it's just trapped inside massive research models that are too slow to matter. We decided to fix that.
What it does
Sentinel.AI is a predictive safety engine for the physical world. It takes live video from any environment — a warehouse floor, a construction site, an autonomous vehicle's feed — and forecasts hazards seconds into the future. When danger is forming, Gemini-powered agents take real, grounded actions: slowing robots, rerouting vehicles, alerting humans. Current systems react. Sentinel prevents.
How we built it
We forked NVIDIA Cosmos — a state-of-the-art world model — and did something NVIDIA hasn't done yet: we made it fast enough to save lives. The original Cosmos pipeline generates full future video. Beautiful, but 30 minutes per inference on DGX Spark (We call him Sparky✨). Useless for real-time safety. Our breakthrough: we ripped out the video generation head entirely. The model's internal representations — its compressed understanding of physics, motion, and spatial relationships — already contain everything needed to predict danger. We don't need to see the future. We just need to understand it. We attached a lightweight XGBoost classifier directly onto these future-aware embeddings. Then we connected Gemini agents as the decision layer — taking the predicted risk and choosing world-grounded actions: stop, slow, reroute, alert. End-to-end latency: under 1 second. Down from 30 minutes on Sparky.
Challenges we ran into
Cosmos was never designed for real-time inference. Making a research-grade world model run at edge speed meant rethinking the entire pipeline — not fine-tuning it, restructuring it. We also had to prove that embeddings alone (without generated video) retain enough predictive signal to classify risk accurately. THEY DO! Cross-domain generalization was another battle. We trained and tested on automotive collision data and deployed on warehouse scenarios — two very different visual worlds. Getting the representations to transfer required careful temporal feature design.
Accomplishments we're proud of
30 minutes → under 1 second. That's not optimization. That's a paradigm shift. We proved that world models — the most powerful spatial reasoning systems in AI — can run on edge GPUs for safety-critical decisions. And we showed that Gemini agents can take those predictions and act on them in the real world, not just narrate what they see.
What we learned
The most expensive part of a world model — generating pixels — is also the part you don't need. Representations are the product. This insight applies far beyond safety: any application where you need fast, physics-aware reasoning (robotics, autonomous driving, industrial automation) can benefit from this pattern. We also learned that the gap between a research breakthrough and a deployable system is an engineering problem — and sometimes, the best engineering is knowing what to throw away.
What's next
This isn't a warehouse tool. It's infrastructure for any system that operates in the physical world. Autonomous vehicles. Robotic fleets. Construction sites. Surgical robots. Anywhere humans and machines share space, Sentinel can predict what's about to go wrong and prevent it. The future of safety isn't faster reactions. It's prediction.
Demo is here: https://timsinashok.github.io/Sentinel-AI/
FYI This project was submitted by Ashok, Nils, and Parth for Tree Hacks 2026 (Feb 13 -16, Stanford)
Sponsors Used:
- NVIDIA
- Gemini AI
Backend Available at: https://github.com/timsinashok/cosmos-predict2.5
Sentinel AI
Predicting hazards before they happen.
Sentinel AI is a future-aware safety system built on top of NVIDIA Cosmos. Instead of labeling the current frame as safe/unsafe, it uses predictive world modeling to reason about future states of the environment and produce an early risk score — enabling proactive mitigation (alerts, slowdowns, reroutes, kill-switches) before a near-miss becomes an incident.
Major contribution: we optimized the NVIDIA Cosmos world-model-based hazard predictor and increased inference efficiency by ~1800x compared to the base Cosmos pipeline by operating entirely in representation space and removing pixel-level generation.
Safety shift: reactive perception → predictive prevention
What’s in this repo
This repository contains an interactive web demo UI (Vite + React) that shows the Sentinel AI operator experience:
- Without Sentinel: the system only “understands” what happened after the event (reactive VLM-style explanation).
- With Sentinel: the system surfaces an early warning (time-to-hazard + severity) and a sequence of mitigation actions before the collision.
The demo is driven by a short clip (/0.0-14.0.mp4) plus a lightweight simulation timeline that illustrates the intended end-to-end behavior.
High-level idea (the real system)
Most industrial safety stacks today do:
- Vision / VLM → classify current frame as safe/unsafe
Sentinel AI instead aims to do:
- World model (Cosmos) → encode dynamics and forecast future states
- Extract future-aware latent representations
- Early hazard classification in representation space
Conceptual pipeline:
video → latent embeddings (future-aware) → classifier → risk score + confidence → mitigation
What we engineered (systems thinking)
Sentinel AI is designed as a systems-level optimization, not a pixel-generation demo.
1) Representation-only inference
We keep the predictive signal but skip expensive pixel synthesis:
- Encode frames/clips using Cosmos tokenizer / VAE
encode() - No diffusion head
- No future video decoding
2) Fast, reusable embeddings
Latents are pooled into compact vectors that can be:
- Fed into lightweight classifiers (LogReg / SVM / MLP / XGBoost)
- Cached and reused to reduce repeated compute
This supports model saving and reuse, and enables near-real-time deployment on edge-class GPUs.
3) Temporal signal without full video generation
Temporal context comes from short snippets (e.g., last 3–5 seconds at low FPS), aggregated directly in embedding space to learn risk trajectories.
Tradeoff (intentional):
- Less fidelity
- Much lower latency
- More actionable output
Why this is systems thinking
Sentinel AI makes an explicit engineering tradeoff: we spend compute on predictive risk scoring (the part that triggers mitigation) instead of generating pixels.
This makes world models deployable for safety, not just compelling for demos.
Run the demo locally
Prerequisites
- Node.js (recommended: 18+)
Install
npm install
Start dev server
npm run dev
Then open http://localhost:3000.
Production build
npm run build
npm run preview
Assets (video + logo)
- Video: the demo expects the clip to be available at
/0.0-14.0.mp4.- For Vite, the simplest approach is to place it in
public/0.0-14.0.mp4so it’s copied into the build output.
- For Vite, the simplest approach is to place it in
- Logo: the header loads
/logo.png(place inpublic/logo.png).
Repository layout
App.tsx: main UI + “With/Without Sentinel” mode logiccomponents/ScenePanel.tsx: video stage + overlays and analysis pause behaviorcomponents/RiskSummary.tsx: risk level + time-to-hazard displaycomponents/AgentActionPanel.tsx: mitigation action timelineconstants.ts: demo timings + initial entitiestypes.ts: shared types and enums
Why this matters
Predicting hazards before they happen can:
- Reduce near-misses and injuries
- Improve human–robot / forklift–pedestrian safety
- Extend from warehouses to factories, construction sites, and autonomous environments
Sentinel AI demonstrates how world models can be adapted into deployable, safety-critical decision systems by prioritizing low-latency risk scoring over pixel generation.
Acknowledgements
- Built for TreeHacks as a prototype UI + systems concept.
- Inspired by NVIDIA Cosmos and the broader world-modeling ecosystem.
Analysis
View
Metric
- 5
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- HTMLIn code
- ReactIn code
- TypeScriptIn code
- Google GeminiClaimed
4 of 5 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
54 KB
Source files
16
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
timsinashok/Sentinel-AI
27 files · 2.3 MB · @ 58cd8b3
Structure
Interface
8 files · 30%Screens, components and styles rendered to the user.
Application logic
5 files · 19%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript79%
- HTML10%
- Markdown9%
- YAML2%
- CSS0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 7- lucide-react
- react
- react-dom
- +4 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.