City ops
Corridor: ___ . Worst clock: ___ . Sensors: OSM only / loops / cameras. Goal: forecast board / routing pilot / student demo.
Compiling the hour
Contact
Tell us the corridor, the clock you are failing, and whether you have cameras, loops, or only OSM. We answer like a lab: short, technical, on parchment.
Also
Studios
Thiruvananthapuram, Kerala
South Park adjacent, San Francisco
A human reads the brief. If it is a fit, you get a datasheet and a time to walk the graph. If it is not, you get a sentence, not a drip campaign. Ember is for actions that complete.
Press and awards desks: the visual system is documented in the CSS theme as named variants. Please do not screenshot a dark band and call the brand black. It is graphite. The paper is bone.
City or campus name. One corridor that fails today (example: Airport → Secretariat at 9:00 under rain). Whether you have cameras, loop counts, or only OSM. Whether you need a student demo, a research collaboration, or an operator pilot. Expected timeline. We would rather get five clear sentences than a twenty-page deck with no clock.
Before writing, open Predict with a Thiruvananthapuram place pair, generate a Map under rain, and load Influence near that place. Tell us what surprised you. That is more useful than a generic “AI traffic” request.
Brief templates
Corridor: ___ . Worst clock: ___ . Sensors: OSM only / loops / cameras. Goal: forecast board / routing pilot / student demo.
We want to compare hybrid vs LSTM on ___ graph. Need: edge CSV format, evaluation split notes, PPO reward definition.
Daily runs between ___ and ___ . Pain: ___ minutes surprise delay. Willing to share anonymized traces: yes/no.
Course: ___ . We forked traffic-app. Blocker: ___ . Asking for: architecture review / dataset tips / demo script.
Common questions
Start with a corridor brief. Many partners want the lab loop and honesty about demo vs live data first.
Yes — ask for theme tokens (bone, parchment, ember) and the Thiruvananthapuram case paragraph, not a neon screenshot.