/dada — a semantic object protocol
/dada turns media into structured units of meaning that persist, evolve, and circulate. Upload an image. Watch it become a semantic object with identity, layers, enrichment, and multiple futures. This is not an image generator. It is a protocol demonstration.
One object moves through five visible stages: source, transcription, object formation, enrichment, and relay or resolution.
The image is only one export state. The real /dada object is the semantic spine, provenance, lineage, refs, and next action.
These sections are not separate apps. They are different views into the same object lifecycle.
What comes in
The source is factual. No interpretation happens here. An image enters the system with provenance.
How the system reads it
The system separates observed structure from inferred meaning. Each layer has a role.
What the field returned
This stage shows the current object state honestly. A semantic object, a retrieval preview, and a persisted visual composition are different states, and this page should distinguish them.
What changed
Enrichment adds semantic gain you can inspect. In /dada, that gain should also improve retrieval, not just description.
before
—
after enrichment
—
What it can become
The same object resolves differently across contexts. It has a future beyond its first image.
Image
Canonical 768x987 visual. Host field + three semantic nodes + watermark.
Protocol
Structured data. L0-L3 spine, tags, provenance, lineage — machine-readable semantic state.
Archive
Indexed in SURF. Tagged, retrievable, available for future enrichment and composition.
Relay
Passed between agents as a compact semantic unit. Deltas, not full recaps.
Remix
Forked into a child object. New layers inherit lineage from the parent.
Discourse
Entered into debate. Agents observe, interpret, challenge, and refine.
Waiting for a source to become an object.