Datamorpho is currently in the open specification and first tooling phase. The roadmap is intentionally staged so the protocol can mature through documentation, examples, tooling, public review, and future carrier expansion.
Phases
These phases reflect the public plan already introduced on the landing page. They are meant to be practical, sequential enough to guide work, and open enough to evolve with public review.
Establish the public foundation of the project: the normative specification, the whitepaper, the repository structure, the glossary, FAQ, roadmap, and the first example set.
Release the first reference tooling for creating Datamorphed files and reconstructing hidden states with protocol-correct outputs and deterministic behavior.
Build the browser-compatible layer for detection, validation, and practical reconstruction workflows, especially for carriers that fit well in web environments.
Offer free web tooling for users who want to work with Datamorpho without installing local code first, while keeping the protocol itself open and inspectable.
Add full PDF carrier support to both the reference tooling and the web tools. PDF is already defined at the protocol level in v0.001; this phase delivers the production implementation.
Build the MorphoStorage layer for hosting, discovery, and retrieval of reconstruction-related data, including IPFS-aligned flows and decentralized storage options.
Expand beyond JPEG, TXT, and PDF into media-heavy carriers that strongly benefit from early distribution and later reconstruction.
Strengthen public infrastructure, improve interoperability vectors, refine documentation, and move toward broader open standards discussion as the protocol matures.
Near-term priorities
Not every roadmap item has the same urgency. The current priority is to stabilize the public protocol layer and the first implementation wave.
Specification quality, language precision, and internal consistency remain foundational.
Python creator and reconstructor flows should become reliable before larger expansion.
Examples and vectors must grow alongside tooling to support review and interoperability.
Why audio and video come later
Audio and video are the next immediate targets after the first release, but they require more careful engineering than the first carrier set.
Future infrastructure
The protocol roadmap is not only about new carriers. It is also about making the ecosystem around the protocol stronger and easier to use.
Future support for secure public or semi-public reconstruction-related retrieval flows where appropriate.
More examples, vectors, validation notes, and reusable fixtures for future implementations.
Free Datamorpho.io tools for creation, reconstruction, and future protocol education.
Datamorpho is intended to grow as reusable open infrastructure: not only a specification, but also a tooling stack, public service layer, and documentation ecosystem.
Open review
The roadmap is a public working direction, not a closed promise. It should evolve through implementation experience, public critique, developer feedback, and future carrier research.
sequencing, implementation detail, carrier order, and infrastructure priorities may all evolve as the project matures.
the core Datamorpho philosophy: declared latent states, reconstruction semantics, open documentation, and reusable public infrastructure.