ALEQTH OS / DADA PROTOCOL · FIRST CANONICAL FRONTEND ·
L0-L3 ● OBJECT ● ENRICHMENT ● RESOLUTION
os → /surf reservoir → /studio build → /market → /dada gallery → /world → docs → ● PROTOCOL LIVE · SCROLL RESTORED · UPLOAD FIXED · TAGS SANITIZED
/dada — Semantic Object Protocol [First Canonical Frontend]
_
□
×

/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 the protocol's forged object. First canonical frontend — other surfaces may implement the same protocol.
01 WHAT THIS PAGE PROVES

One object moves through five visible stages: source → transcription → object formation → enrichment → relay/resolution. Every stage is inspectable, editable, and exportable as a portable verdict.

02 CORE CLAIM

The image is only one export state. The real /dada object is the semantic spine + provenance + lineage + refs + bundle + next action. The PNG carries its own JSON in iTXt.

03 HOW TO READ + WHERE IT GOES

Not separate apps — same object lifecycle. /surf feeds it, /dada/protocol forges it, /studio composes it into .ankl pages, /market sells it, worlds host it, agents relay it. Portable bundle is the interop.

01 — SOURCE · What comes in (factual, no hallucination)

Source is factual. No interpretation here. Drop, click, or paste (⌘V) an image. HEIC/AVIF/JPG/PNG supported — auto-converted for vision. If a later panel disagrees with this image, treat that as a reading mismatch to inspect, not source replacement.

+
drop / click / paste to upload
HEIC·AVIF·JPG·PNG·WEBP → vision-safe JPEG
SOURCE ID
waiting for upload
TYPE · SIZE
—
PROVENANCE
—
STATUS
awaiting source
02 — TRANSCRIPTION · How the system reads it (observed vs inferred)

System separates observed structure from inferred meaning. Machine reading, not final truth. L0/L1 must visibly match source before you trust composition. L0/L1=OBSERVED (must be factual). L2/L3=INFERRED (charge/meta). Edit them inline — yellow = focused.

L0
WORLD
—
OBSERVED
L1
SUBJECT
—
OBSERVED
L2
CHARGE
—
INFERRED
L3
META
—
INFERRED
LITERAL
CHARGE
BRIDGE
ECOSYSTEM
#dada#ankle96
● L0/L1 must match source before compose
03 — /DADA OBJECT · What the field returned (canonical vs preview)

Honest state: semantic object vs retrieval preview vs persisted visual are different. Check badge. Output image is one export state — not whole object. PNG has iTXt JSON inside.

[COMPOSE TO RENDER]
OBJECT ID
—
MODE
—
LINEAGE
—
AUTHOR
—
SEMANTIC SPINE
Output image is one state of object — not whole object.
STATE
SOURCE ONLY
Upload a source to begin.
SOURCE TRANSCRIPTION
L0
Awaiting source.
L1
Awaiting source.
L2
Awaiting source.
L3
Awaiting source.
CURRENT OBJECT TRANSLATION
L0
Pending — compose to translate.
L1
Pending — compose to translate.
L2
Pending — compose to translate.
L3
Pending — compose to translate.
X
image
RETRIEVAL EVIDENCE · SURF REFS
Awaiting semantic retrieval from internal image field.
HOST FIELD
Upload seeds retrieval; host field comes from tagged archive, not mirror of upload.
LIMINAL TRACE
Field query terms, chosen refs, matched scores — live traces of passage.
PERSISTENCE
Public demo uses truthful local preview unless persistence available. PNG contains provenance.
NEXT LIFE
Objects enriched, relayed, archived, remixed, resolved. → /studio /market /world.
04 — ENRICHMENT · What changed (semantic gain you can inspect)

Enrichment adds semantic gain j(p)≥p. Refs are field matches & ingredients — should explain object, not silently rewrite source. Gain shown as % shift on L0-L3 axes. Host+nodes must be from SURF.

BEFORE

—

AFTER ENRICHMENT

—

05 — RESOLUTION / RELAY · What it can become (OS handoffs)

Same object resolves differently across contexts. OS handoffs: build .ankl page in /studio, list on /market with creator bonds, host on *.ankle.website world, relay to agents, export portable bundle.

01 IMAGE

Canonical 768×987 visual. Host field + 3 semantic nodes + watermark. PNG iTXt JSON.

02 PROTOCOL

Structured data. L0-L3 spine, tags, provenance, lineage — machine-readable state.

03 ARCHIVE

Indexed in SURF. Tagged, retrievable, available for future enrichment.

04 RELAY

Passed between agents as compact semantic unit. Deltas, not full recaps.

05 REMIX

Forked into child object. New layers inherit lineage from parent.

06 DISCOURSE

Entered into debate. Agents observe, interpret, challenge, refine.

Bundle = portable proof · no DB needed
Protocol proof 
Waiting for a source to become an object.
RECENT /DADA OBJECTS — ANKLE96—