SpatialDB · Spatial infrastructure
A shared spatial
foundation for AI.
Identity, coordinates, permissions and verifiable representations for applications that work with the physical and virtual world.
An AI application needs more than a plausible answer. It needs to know which entity it means, where that entity is, which source supports it and what the caller may access. SpatialDB makes those questions part of a dependable data contract.
Development infrastructure, October 2026. The packaged service and SDK preview is v0.3.0. Newer source integration adds immutable scene publication v2 and contract 0.1.0. Production application adoption remains a separate milestone. Repository access may be required.
Built on PostgreSQL. Designed for spatial context.
A Rust service gives applications typed, bounded PostgreSQL/PostGIS reads. .NET, TypeScript and Rust clients carry deadlines and cancellation. Existing applications retain their schemas, native authorization and atomic writes.
Publish once. Verify every representation.
An offline compiler produces spatial hierarchies, visual and collision geometry, materials, textures and representation descriptors. Immutable versions pin every asset by digest. External subtrees support reuse; texture ranges and detail budgets keep delivery selective.
Clear coordinates. Durable identity.
WGS84 placement, local frames, explicit units and double-precision transforms keep geometry interpretable. Proposed USAP addresses identify entities independently of their location. Navigation and world permissions remain with the services that own them.
Useful foundations for AI applications
- Grounded geographic facts instead of model-invented map features.
- Permission-aware retrieval and source geometry that survives integration.
- Stable entities connecting data, rendered geometry and inspectable provenance.
- Representation contracts that clients can validate independently.
From infrastructure to one working product
Finalverse Web and MutSea are the first integration targets. Actual-source adapter checks pass in isolated application copies, and authenticated SpatialDB-to-FinalStorm streaming passes on Apple M1 Metal. A subsequent read-only native proxy path also passes with two authenticated MutSea users and logout clearing. Full native application adoption, shared Lumi participation and the complete Living World journey are tracked independently.
Digital twins, scientific visualization and broader AI tools are future opportunities. SpatialDB does not claim to be a general tensor database, a molecular solver or a replacement for authoritative world state. Tetrahedral and other representations can be added through versioned contracts after their foundation and runtime support are validated.