Skip to Main Content

Interlock: no plant change is signed off until every document agrees, and the numbers still work. THE PROBLEM Before a process plant changes anything (run a second pump, resize a line, drop a spare), an engineer must approve it. The design lives in hundreds of pages: scope of supply, data sheets, P&ID drawings, design-basis tables. One piece of equipment appears in many of them under different names, the pages often disagree, and the engineer finds every page and does the math by hand. It takes weeks per change, and errors still get through. A REAL EXAMPLE In a public BHEL tender (5 PDFs, 851 pages), the same pumps are "1 working + 1 standby" on the scope page and "2 working" on the data sheet and the P&ID, under three different names. WHAT INTERLOCK DOES The engineer uploads the plant's documents (a folder or files) and types a change in plain English. Interlock: - understands the change with Gemini 4 Neon; - finds every page about the item under all its names: an Argon long read over all 851 pages, code search, and the Decisions API's same-item check; - pulls each value with an exact quote; code checks the quote is on its page, or the value never reaches the rules; - boxes the equipment on the real P&ID with Argon vision; code confirms the printed label sits inside the box and belongs to this item, not its Unit-2 look-alike; - runs the engineering math in code, not in the model: pipe velocity against the plant's own design table, standby, sump cycle (relief valve, design pressure and dosing built and tested); - gives a verdict: BLOCK, REVIEW, or "no conflicts found in N pages read". Never "PASS". Carbon explains disagreements; Hydrogen writes headlines. THE MANAGED AGENT: IT PROPOSES, THE SERVER PROVES A Gemini Managed Agent (Antigravity, Neon) gets one persistent sandbox per plant with the real rule engine mounted. It tries candidate fixes (line sizes, added pumps), runs the rules on each, and proposes the smallest fix or refuses with reasons. The server rebuilds the case, adds the fix and re-runs every rule and the register check on its own code before showing "Proven by the server". The engineer must tick each document disagreement as resolved before approving, and the plant's register then blocks any later change that undoes it. On the BHEL example it blocked "go to 2 working + 1 standby" (the change needs 3 pumps installed; the documents show 2), and the agent's fix, a third pump, was proven by the server.

Team

2221

More from Gemini 4 NYC Hackathon

We design an agentic system to automatically create + manage intelligent AI opponents/NPCs in video games. The suite of agents analyzes user gameplay…

Adaptive NPCs project preview

Manually routing PCBs is time-consuming and cost-inefficient. Current best algorithms (freerouting, PCBRouter) score very low on PCBWorld's hardest PCB…

routr project preview

Heliocam is a camera app where Gemini controls the camera. It watches what you're pointing at, sets the ISO, shutter, focus, white balance and zoom for you…

heliocam project preview

Repairs and assembly fail because manuals are lost, vague, missing, or nonexistent, so people break things or throw them out. KLIK turns a photo of any object…

Klik project preview

Iron Pulse turns your laptop into a 3D boxing ring. Fight an adaptive AI rival in real time using just your webcam. Throw real punches and lean to dodge…

Iron Pulse Arena project preview

Text your raw footage to an iMessage number and get a finished, trend-informed Reel back in the same thread.

Sticky project preview