01
Observe
Start with authorized observations.
Existing recordings and supported camera feeds provide the raw material. Coverage, resolution, lighting, and camera geometry determine what can be measured.
THE PLATFORM
General perception.
A particular place.
A reusable system for understanding physical infrastructure—with the context that makes each site different.
Platform direction · Beginning with traffic measurements
SYSTEM ARCHITECTURE
From observation to evidence.
- 01
Observe
Recordings & supported feeds
- 02
Perceive
Objects, tracks & trajectories
- 03
Understand
Zones & scene relationships
- 04
Measure
Events & defined measurements
- 05
Remember
State, history & evidence
ONE UNDERLYING UNDERSTANDINGReports & visualizations Software & agent interfaces
02
Perceive
Connect objects across time.
Detection and classification describe objects. Tracking links observations into trajectories, so movement can be measured rather than inferred from isolated frames.
03
Understand the scene
Give movement a place.
Zones, geometry, and relationships define the site. Operational definitions determine what counts as an arrival, a turn, an occupied zone, or a stopped vehicle.
04
Measure
Answer a defined question.
Counts, occupancy, dwell time, and events depend on an agreed scope. Measurements should carry their time interval and the configuration that gave them meaning.
05
Remember
Preserve the context of change.
The platform is being designed to retain timestamped observations and historical state so equivalent periods can be compared with consistent definitions.
06
Provide evidence
Make the result reviewable.
The system is designed to connect results to contributing observations, timestamps, configuration, and supporting imagery or video where permitted.
07
Connect
Make understanding usable.
People use reports and visualizations. Planned structured interfaces will expose measurements, events, state, and evidence references to software and agents.
THE SITE MODEL
Objects need context.
Places need definitions.
A traffic intersection has approaches and turning movements. A beach might have shoreline zones and access points. The same schema should not be imposed on both.
A site model defines the concepts and relationships that matter. In technical terms, this is an ontology: reusable core concepts, a domain model, and extensions for the actual place.
01 / CORE CONCEPTS
Object · Zone · Event
Measurement · Time · Evidence
02 / DOMAIN MODEL
Traffic
Approaches · Crosswalks · Turning movements
03 / SITE MODEL · ILLUSTRATIVE
Intersection 14
South Approach · Crosswalk A
Left-turn lane · East Exit
STRUCTURED ACCESS / PLATFORM DIRECTION
Agent-compatible.
Useful to anyone.
We are designing structured access to the same observations that support human review. Proposed tools include get_site_state, get_measurements, list_events, and get_evidence.
Interfaces such as MCP could make these tools accessible to AI agents. Conventional software can use the same underlying data.
PROPOSED SCHEMA / NOT A LIVE API
{
"site": "intersection_14",
"measurement": "turning_movement_count",
"interval": {
"start": "08:00",
"end": "08:15"
},
"movement": {
"from": "south_approach",
"to": "east_exit"
},
"evidence_ref": "observation_set_id"
}Illustrative structure. No measured result is represented.
CONTROLLED SITE ADAPTATION
The deployment changes.
The system must account for it.
Lighting, weather, camera position, object appearance, and geometry vary. So do the operational definitions that make a measurement useful.
We can configure scene logic and, where necessary, develop or adapt vision models for the conditions and objects that matter. Changes must be validated for the deployment. Automated adaptation remains a platform direction.
START WITH YOUR SITE
What do you need
to measure?
Tell us about the place, the footage, and the question you need to answer. We’ll work with you to assess what’s possible.
Apply for a Traffic Pilot