Base File
The original visible file used as the carrier input before Datamorpho embedding.
This glossary collects the main terms used across the specification, whitepaper, and website so the protocol can be read with a consistent vocabulary.
The original visible file used as the carrier input before Datamorpho embedding.
The final Datamorphed file.
The file-family-specific embedding rules, such as jpeg-trailer, txt-envelope, or pdf-incremental.
Bytes intentionally present in a payload region but not used by the target hidden state, added to increase ambiguity and attack cost.
The payload bytes from which one or more hidden states can be reconstructed.
A file that conforms to a Datamorpho carrier profile and contains a public manifest plus concealed payload data.
The capability of a file to contain one or more hidden states beyond its visible representation.
A span of bytes referenced by a reconstruction object as part of one hidden state.
The arrangement model for meaningful bytes in a payload region. In v0.001: sparse or sparse-with-chaff.
A locator or direction layer describing where to look for the reconstruction object of a state.
The intentionally visible metadata declaring Datamorphosis, states, triggers, MorphoStorage, and reconstruction-object digests.
A state-specific secret-bearing artifact containing the instructions and secret material needed to reconstruct one hidden state.
A layout strategy in which meaningful bytes are non-contiguous and only referenced spans matter.
A layout strategy in which meaningful bytes are non-contiguous and unreferenced bytes are intentionally present to increase ambiguity.
A declared condition associated with a hidden state, such as time, event, action, ownership, or custom logic.
The linking model in which public state descriptors reference reconstruction-object digests and reconstruction objects reference the carrier file digest.
Secret material included in a reconstruction object and required to recover one or more fragments or a whole hidden state.
The glossary is intentionally concise. For formal structure, read the specification. For rationale and conceptual framing, read the whitepaper. For common questions, use the FAQ or open a public discussion.