Unified Spacetime Address Model
A coordinate system for reality. Space + Time + Plane + Authority. Everything that matters exists somewhere, sometime, in some plane, asserted by someone.
Philosophy
The foundational concepts that define the eVa™ addressing model
Every assertion is traceable to a source, time, and authority
Reconstruct any state at any point in time across planes
Plurality preserved; conflicts are data, not errors
Resolution happens via policy, not overwrite
Definition
The unified URI format for spacetime addressing
Canonical Format
eva://<DOMAIN>/<X>,<Y>,<Z>,<T>@<TimeAuthority>,<PLANE>[@<PlaneAuthority>][:<PlaneDimension>],<V>// Canonical URI Components:
<DOMAIN> ::= Namespace/scope identifier
<X>,<Y>,<Z> ::= Three spatial degrees of freedom (frame-agnostic)
<T> ::= Timestamp (ISO 8601)
@<TimeAuthority> ::= Clock source binding (required for authoritative time)
<PLANE> ::= Semantic coordinate (what kind of reality)
@<PlaneAuthority> ::= Data provenance within plane (optional)
:<PlaneDimension> ::= Layer/version within plane (optional)
<V> ::= Value/attribute at this address
// Full Example:
eva://CORE/33.457756,-111.987290,0,2026-04-12T14:32:10Z@UTC_GNSS,LOGICAL@MAP_OSM:ROADGRAPH_2026Q1,speed_limitSpace
Spatial coordinates are frame-agnostic; meaning comes from the XYZ Frame Registry
interface XYZFrameRegistry {
frameId: string; // Unique identifier (immutable)
frameType: 'Cartesian' | 'Geodetic' | 'Inertial' | 'Relative' | 'Logical';
origin: {
definition: string; // Origin point description
axisOrientation: string; // Axis alignment (ENU, NED, etc.)
};
temporalDependency: boolean; // Does frame change over time?
epoch?: string; // Reference epoch if time-dependent
units: {
linear: 'meters' | 'feet' | 'degrees';
angular?: 'radians' | 'degrees';
};
precision: number; // Decimal places of precision
uncertaintyModel?: string; // How uncertainty is characterized
}Time
Time is always bound to an authority. Timestamps without authority are estimates.
interface TimeAuthorityRegistry {
timeAuthorityId: string; // Unique clock/time source identifier
clockType: 'Atomic' | 'GNSS-disciplined' | 'MET' | 'System Oscillator' | 'Simulated' | 'Human-Reported';
epoch: string; // Reference point (Unix, J2000, mission start)
driftSpec: {
rate: number; // Expected drift rate
uncertainty: number; // Drift uncertainty bounds
};
leapSecondHandling: 'UTC' | 'TAI' | 'GPS' | 'none';
authoritativenessLevel: 'ground_truth' | 'derived' | 'estimated';
validDomains: string[]; // Where this authority is meaningful
validPlanes: string[]; // Planes where authority applies
}Semantics
Plane defines what kind of reality or meaning. No implicit planes — always explicit.
Composite Encoding
<PlaneID>[@<PlaneAuthorityID>][:<PlaneDimensionID>]| Plane Type | Description | Example Use Cases |
|---|---|---|
| PHYSICAL | Real-world, measurable reality | Sensor data, GPS positions, physical assets |
| PLAN | Intended or scheduled state | Flight plans, construction blueprints, routes |
| SIMULATION | Simulated or modeled reality | Digital twins, training scenarios, what-if analysis |
| LOGICAL | Semantic/conceptual associations | Map layers, road graphs, network topology |
| ORG | Organizational/administrative reality | Jurisdictions, ownership, responsibility zones |
| COMMAND | Command and control context | Mission orders, directives, operational overlays |
Defines provenance/producer within a plane. No implicit canonicalization — resolve at query time via policy.
Optional layer/version within a plane for data partitioning.
Specifications
Five registries define the complete eVa™ address space
Defines how XYZ coordinates are interpreted across reference frames
Defines clock sources and temporal reference systems
Defines semantic planes and cross-plane relationships
Defines data producers and provenance within planes
Defines position assertion sources and uncertainty models
Resolution
Plurality is preserved; conflicts are data. Resolution happens via policy, not overwrite.
| Mode | Description |
|---|---|
ALL | Return all matching assertions from all sources |
BEST | Return the highest-ranked assertion based on policy weights |
TOP-K | Return the top K assertions by ranking score |
CONSENSUS | Return result only if sources agree within threshold |
AUTHORITATIVE | Return only from designated authoritative sources |
TRACE | Return with full provenance chain for audit |
# eVa Resolution Policy Schema
policy:
id: string # Unique policy identifier
name: string # Human-readable name
version: string # Semantic version
mode: enum # ALL | BEST | TOP-K | CONSENSUS | AUTHORITATIVE | TRACE
# Source preferences (optional)
sources:
preferred: # Ordered list of preferred authorities
- authority_id: string
weight: number # 0.0 - 1.0
excluded: string[] # Authorities to exclude
# Fusion rules (optional)
fusion:
enabled: boolean
output_plane: string # Target plane for fused result
output_authority: string
algorithm: string # Fusion algorithm ID
# Constraints (optional)
constraints:
max_age_seconds: number
min_confidence: number
require_trace: booleanExamples
See how the same spatial coordinate carries different meanings through authority and plane variations
Road speed limit from OSM roadgraph, located via GPS
eva://CORE/33.457756,-111.987290,0,2026-04-12T14:32:10Z@UTC_GNSS,LOGICAL@MAP_OSM:ROADGRAPH_2026Q1,speed_limit| Component | Value |
|---|---|
| Domain | CORE |
| XYZ | 33.457756, -111.987290, 0 |
| Time | 2026-04-12T14:32:10Z |
| Time Authority | UTC_GNSS |
| Plane | LOGICAL |
| Plane Authority | MAP_OSM |
| Plane Dimension | ROADGRAPH_2026Q1 |
| Value | speed_limit |
Same location, different map provider
eva://CORE/33.457756,-111.987290,0,2026-04-12T14:32:10Z@UTC_GNSS,LOGICAL@MAP_GOOGLE:ROADGRAPH_2026Q1,speed_limitChanged: MAP_OSM → MAP_GOOGLE
Same observation, different clock
eva://CORE/33.457756,-111.987290,0,2026-04-12T14:32:10Z@SYSTEM_LOCAL,LOGICAL@MAP_OSM:ROADGRAPH_2026Q1,speed_limitChanged: UTC_GNSS → SYSTEM_LOCAL
Key Insight: The same XYZ coordinate can represent fundamentally different data depending on authority and plane. This is not ambiguity — it's plurality by design. Resolution happens at query time via policy.
API
RESTful API for eVa™ operations
GET /api/eva/parse?uri=eva://CORE/33.457,-111.987,0,2026-04-12T14:32:10Z@UTC_GNSS,LOGICAL@MAP_OSM:ROADGRAPH_2026Q1,speed_limit
// Response:
{
"uri": "eva://CORE/33.457,-111.987,0,...",
"parsed": {
"domain": "CORE",
"xyz": { "x": 33.457, "y": -111.987, "z": 0 },
"time": "2026-04-12T14:32:10Z",
"timeAuthority": "UTC_GNSS",
"plane": "LOGICAL",
"planeAuthority": "MAP_OSM",
"planeDimension": "ROADGRAPH_2026Q1",
"value": "speed_limit"
}
}POST /api/eva/resolve
{
"uri": "eva://CORE/33.457,-111.987,0",
"policy": "map.speed_limit.best",
"time": "2026-04-12T14:32:10Z"
}
// Response:
{
"resolved": true,
"mode": "BEST",
"results": [{
"value": 45,
"unit": "mph",
"authority": "MAP_HERE",
"confidence": 0.95,
"trace": { ... }
}]
}GET /api/eva/search?x=33.457&y=-111.987&z=0&radius=1000&plane=PHYSICAL
// Response: GeoJSON FeatureCollection
{
"type": "FeatureCollection",
"features": [...],
"total": 42,
"policy": "default",
"center": { "x": 33.457, "y": -111.987, "z": 0 },
"radiusMeters": 1000
}POST /api/eva/assert
{
"xyz": { "x": 33.457, "y": -111.987, "z": 0 },
"xyzFrame": "WGS84_GEODETIC",
"time": "2026-04-12T14:32:10Z",
"timeAuthority": "UTC_GNSS",
"plane": "PHYSICAL",
"planeAuthority": "SENSOR_GPS_001",
"locationAuthority": "LOC_GNSS",
"value": { "speed": 35.2, "heading": 270 },
"confidence": 0.92
}Security
Zero-trust access control for eVa™ addresses via spatial boundaries
Crossing XYZ boundaries can elevate or restrict access based on SoI policies.
Stack
Ops
OpenAPI Documentation
Auto-generated Swagger docs for all endpoints.
Provenance Audit Trail
Full trace of all assertions, resolutions, and fusions.
Health & Metrics
Registry health, query latency, fusion pipeline status.
Use the eVa™ API to create spatial-aware applications with multi-source truth, policy-based resolution, and full provenance tracking.