Signals
What is happening now
Traffic counts, heat, water flow, permits, service demand, budgets, and other approved data — the readings the city already collects.
Smart-city systems tell us what is happening. The Universal Developmental Interface helps us understand how conditions are changing, which pressures are combining, and what may happen next.
A traffic counter gives a number. A smart-city dashboard shows that number on a map. UDI asks the developmental question the dashboard cannot: is this condition stable, improving, or building toward a problem?
It works like a weather forecast for the city. We do not only read today's temperature — we study the direction of change, the forces producing it, and several possible next conditions.
From individual readings to developmental understanding. Each layer builds on approved city data the department already governs.
Traffic counts, heat, water flow, permits, service demand, budgets, and other approved data — the readings the city already collects.
The direction and speed of change across time or place: where a condition is rising, falling, spreading, or accelerating.
Heat, growth, traffic, cost, age, and limited capacity can reinforce one another. The field shows where they overlap and compound.
If these gradients continue, and if the city does or does not intervene, these outcomes become more or less likely.
A sketch of how a pressure map reads at a glance: not a status board of today, but the direction each city system is heading and where the strain is combining.
Demand and permitting are climbing faster than added supply across the selected district.
Corridor pressure is forming before the corridor locks up; two limits are within reach.
Shared constraints are narrowing where water and transit systems depend on one another.
Do not replace the city's existing initiative. Select one district and one real decision — flooding, traffic, heat, housing growth, or infrastructure failure — connect data the city already governs, and produce a pressure map with testable forecasts.
Measure of success: did the forecast give staff earlier, clearer, and more testable warning than the existing dashboard alone?
One district, one decision, on data the city already holds. Every step states its uncertainty and leaves an accountable trail.
Begin with a question the city already needs to answer, tied to a district and a budget.
Calculate how the relevant conditions are changing across time and place.
Layer forces, constraints, dependencies, and thresholds into a single pressure field.
Compare no action with practical interventions the city could actually fund.
Compare predictions with what happened and improve the model on the record.
A prediction is only worth acting on if the city can see how it was made. Keep the sensors, keep the systems, and add a developmental layer that has to show its work.
The ledger records the evidence trail: which governed data entered the model, how it was transformed, which assumptions produced a forecast, what officials saw, and what later happened. Transfer keys let that developmental history move responsibly between departments or public bodies.
Every application begins with a public decision, uses governed data, states its uncertainty, and leaves an accountable ledger trail — so a plain-language council brief can always be traced back to the reading it came from.
See how results are recorded →