# GridLock

- **Event:** [Agents in Context Toronto: a MongoDB Hackathon](https://cerebralvalley.ai/e/mongodb-toronto-hackathon)
- **When:** Sat, Nov 14 at 9:00 AM – 9:00 PM (EST)
- **Where:** Toronto, Canada
- **Team:** [Tanish Srikakolapu](https://cerebralvalley.ai/u/Hello123), [Shakoor Shaik](https://cerebralvalley.ai/u/shakoors), [Aryan Desai](https://cerebralvalley.ai/u/a1desai), [Kevin Upadhyay](https://cerebralvalley.ai/u/kevin1)
- **GitHub:** https://github.com/a1desai/MongoDB-Hackathon
- **Demo video:** https://drive.google.com/file/d/1QYy-ABKmH9gPRFoylExS0on-JEWFwb6O/view?usp=drive_link
- **Gallery:** https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery
- **Page:** https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/70

Gridlock is a power-grid simulation that explores a difficult question: when AI helps decide whose electricity use gets reduced during a crisis, how do we keep those decisions accountable?

During a heat wave, electricity demand rises as households run their air conditioning. If a generator suddenly fails, grid operators need to respond quickly. They could dispatch batteries, pause EV charging, adjust participating households’ thermostats, or temporarily interrupt power. But each choice affects people differently, and the fastest way to reduce demand isn’t always an acceptable one.

Gridlock gives operators an interactive map with Ontario-wide exploration and a Toronto-focused simulation using synthetic households and fictional control systems. AI agents forecast demand and propose coordinated responses. Operators can introduce a generator failure or a public message impersonating a supervisor, then inspect how the system handles the situation.

Built for Problem Statement 1: Agents You Can Audit, Gridlock separates an agent’s proposal from its permission to act. Every proposed action passes through a deterministic policy gate with sixteen rules covering consent, authority, temperature limits, protected households, outage duration, rotation, and human approval. Actions can be allowed, denied, partially allowed, or held for supervisor review.

An executor coordinates five mock systems representing thermostats, EV chargers, batteries, messaging, and feeder controls. It checks authority before execution, uses idempotency keys to avoid duplicate commands, and reads system state back to verify whether an action actually took effect. Operators can halt the agents and request eligible rollbacks.

## More from Agents in Context Toronto: a MongoDB Hackathon

- [StockFighter](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/67)
- [Second-Voice](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/68)
- [Team Senders](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/69)
- [Murder Mystery](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/71)
- [Swarmtect](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/72)
- [HandOver](https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/73)

---

Markdown version of https://cerebralvalley.ai/e/mongodb-toronto-hackathon/hackathon/gallery/70. Site index for agents: https://cerebralvalley.ai/llms.txt · full text: https://cerebralvalley.ai/llms-full.txt