P3DF development roadmap

Current status

The current technical basis is a 0.1.0-draft reference-engine specification covering the portable container, geometry, semantics, navigation and recorded telemetry. The project team reports that an engine and Creator have been developed; the public code and release artifacts are not yet linked here.

This website provides an architectural overview and an illustrative browser experience. Its demo is not a published engine build or evidence that the complete conformance suite has passed.

Public release deliverables

• A language-neutral format specification and machine-readable schemas.
• The public source repository, with an upcoming Apache 2.0 code release.
• Validated example .p3df packages and expected query results.
• A validator and a valid/invalid conformance corpus.
• MCP tools for digital-twin interactions from Claude, ChatGPT and other MCP clients. See the proposed MCP integration.
• The hosted P3DF Creator and native iOS, Android, macOS and Windows applications.
• A public issue tracker and a documented request-for-comments process.

Release dates are not announced. Platform signup lists will receive updates when something is ready to use.

Cloud database and integrations

The cloud platform vision treats the twin as a operational spatial database. Camera observations, sensor history, spatial information and asset relationships would become a shared context for applications and AI agents.

This work requires explicit permissions, data retention controls, source attribution, freshness handling and secure integration boundaries. Live transports, camera integrations, access control and embeddable cloud tooling are upcoming capabilities, not claims about the initial file specification.

Prove interoperability across tools

The key milestone is an independently written reader opening the same package and producing the expected scene and data. Next come documented bridges to selected building, asset and robotics ecosystems, tested with participants from those communities.

Target use cases include home robotics, smart-home applications, building handover and facility operations. These are invitations to collaborate, not announced customer deployments.

Standardization objectives

The long-term ambition is a widely adopted, vendor-neutral foundation for agent-interactive digital twins. A proposed path is to build a technical working group, publish open RFCs, gather independent implementation evidence and explore the appropriate standards venues.

Engagement with bodies such as ASME and relevant standards communities is an ambition. There is no claim of an established task force, accepted RFC, endorsement or formal standardization. Public project RFCs should not be confused with an IETF RFC publication.