Python Creator
Reference tooling to create Datamorphed JPEG and TXT carriers, public manifests, and reconstruction objects.
Free tools · Python reference now · Browser JS next
Create and reconstruct Datamorphed files
The first usable implementation path is the Python reference tooling. After it is fully tested, the public website tools will be implemented as browser-side JavaScript derived from that Python code, so the final public demo does not need to process user files on the web server.
Implementation path
Python first, JavaScript next
The website pages are being prepared now, but the real first implementation work happens in Python. Once the Python creator and reconstructor are stable and tested, they will be ported to front-end JavaScript so the public web demo can run without handing raw file-processing work to the server.
Python Reconstructor
Reference tooling to validate a Datamorphed carrier and reconstruct one target hidden state from a reconstruction object.
Browser JavaScript Layer
Planned next. The future website demo will use browser-side JavaScript derived from the tested Python implementation instead of sending raw file-processing work to the server.
Important
The protocol specification still documents JPEG, TXT, and PDF at the standard level. The first public implementation and website demo intentionally narrow the usable scope to JPEG and TXT so the code can be tested and controlled properly before any broader support is advertised.
Cryptography profiles
Two browser-compatible starting profiles
The reference implementation begins with two profiles chosen to map cleanly to browser-native cryptographic primitives later: a fast profile for practical personal use, and a stronger profile with wrapped fragment secrets for more demanding use.
simple
Alternates randomly by fragment between AES-256-GCM and AES-256-CTR+HMAC-SHA-256. This keeps the demo fast, clear, and aligned with the Datamorpho concept of heterogeneous fragment protection.
hardened
Alternates randomly by fragment between RSA-OAEP-4096+AES-256-GCM and RSA-OAEP-4096+AES-256-CTR+HMAC-SHA-256. The fragment payload is still encrypted only once; RSA wraps fragment secret material. This is envelope encryption, not payload double-encryption.
Important concept
In Datamorpho, different fragments of the same hidden state may use different suites. The demo should make that visible and explicit instead of pretending one state always uses one single algorithm.
Tool pages
Creator and Reconstructor pages are ready for future integration
The dedicated tool pages now expose the intended demo workflow, limits, legal/privacy warnings, and placeholder form layout so the later JavaScript integration can replace the placeholder blocks without redesigning the public pages.
Creator page
Carrier input, hidden-state inputs, suite selection, limits, policy acknowledgements, and a placeholder panel for the future browser workflow.
Reconstructor page
Carrier upload, reconstruction object upload, output expectations, demo logging notice, and a placeholder panel for the future browser workflow.
Planned next after Python validation
Port the tested creator and reconstructor flows to browser-side JavaScript, wire the public pages to those libraries, and only then enable the real interactive web demo.