JPEG Example
A visible image containing a later reconstructable hidden state.
Examples and interoperability vectors
Real carriers make the protocol easier to understand
Datamorpho is easiest to understand through concrete examples. Each example should pair a visible carrier with a public manifest, a reconstruction object, and a clearly defined expected output.
Carrier examples
The first four example families
These examples are meant for developers, reviewers, implementers, and anyone trying to understand Datamorpho through practical carrier-specific cases. The first public website demo is intentionally limited to JPEG and TXT, while PDF remains documented at the protocol level.
TXT Example
A visible text file with a Datamorpho envelope and reconstructable hidden content.
PDF Example
A protocol-level profile example only for now. PDF is documented in the specification but intentionally excluded from the first website demo implementation.
Static Metadata Reveal Pattern
A Datamorphed JPEG and Datamorphed metadata file working together without moving the public metadata location.
Why examples matter
Examples are not decoration
In Datamorpho, examples serve technical purposes. They are not just demos. They help explain carrier semantics, reveal edge cases, test implementations, and make the protocol easier to review in public.
Protocol understanding
Examples make it easier to understand the difference between public declaration, concealed payload, and reconstruction semantics.
Implementation testing
Examples provide stable inputs and expected outputs for early tooling and future interoperability checks.
Public review
Examples make it easier for developers, researchers, and reviewers to discuss the protocol with concrete artifacts.
Interoperability
Vectors and validation should grow with the tooling
Beyond human-readable examples, Datamorpho should also maintain structured vectors for deterministic validation and future interoperable implementations.
Human-oriented examples
- annotated carrier examples
- clear explanation of what each file contains
- walkthroughs for creators and reconstructors
- diagrams where helpful
Machine-oriented vectors
- expected hashes
- expected reconstruction outputs
- manifest and reconstruction object fixtures
- interoperability-oriented validation assets
Good examples should be reusable
A strong Datamorpho example should help three audiences at once: users learning the concept, developers implementing the protocol, and reviewers trying to validate correctness.
How to use these examples
A practical review flow
The examples page is meant to support a simple workflow: understand the carrier, inspect the declaration layer, examine the reconstruction object, and compare the final output with the expected result.
For readers and journalists
Start with the landing page, then use the examples to understand what a Datamorphed carrier looks like in practice.
For developers and implementers
Read the specification, inspect the examples, compare the outputs, and use them as fixtures when building or reviewing tooling.
Next examples
Audio and video examples will follow the first release
JPEG, TXT, and PDF are the first public carrier profiles. Audio and video are the next immediate targets, and future example sets should expand accordingly once the first tooling release is stable.
Why audio and video matter
They are strong demonstrations of early distribution and later reconstruction for media-heavy use cases.
Why they come later
They require more work around size, streaming, re-encoding, and tooling complexity than the first carrier set.