Check everything. Trust nothing.

runevery check below in this browser, against live endpoints
readeach line: what was checked, and where it ran
returnto the overview for what emem does

Send the token. Keep the pixels.

recallagent A reads a signed NDVI fact at a place
sendA posts one string to agent B, a Web Worker with its own thread and memory
checkB hashes it, verifies the signature, reads two tiles from the satellite archive, recomputes the value
provethe identical f64, bit for bit, or a red line naming the check that failed

agent A this tab, holds the fact

postMessage(token)
nothing else crosses

agent B a Web Worker, holds only the token

on screen, agent A recalls a fact and hands it off once; press hand off to run it again, or pick another place.

decode the tile agent B read, and the 10 m pixel the fact names

the tile appears once agent B has read and inflated it.

check the capture against the satellite's own orbit

runs after the recompute: SGP4 on public elements, closest approach, cross-track distance, sun elevation.

reason what the agent's context receives instead of the imagery

filled once agent B has verified the token.

count every byte that moved, by who moved it

filled from agent B's own fetch ledger when it finishes.

Everything that looks writes the same token.

observetelescopes, satellites, rovers, drones, robots, any machine
admiteach class under a written profile; a device only with its full OS execution trace
anchora place by its 10 m cell; a target with no latitude by its identity
measureeach distance below, computed in this browser now; bars are log₁₀(km)

…
Mars imaged by Hubble; a rover or orbiter joins the same way
- observea surface with no Earth latitude
- anchorthe subject by identity, not by place
- sendthe token across the light-minutes; the frame can wait
space.deep.v1
point Mars, from Hubble
…
Sun–Earth L2 Webb circles it
- observeinfrared, anti-sunward, about four times as far as the Moon
- pointthe mosaic stays at its archive; a note names its chunks
- checkany chunk by its row: the emem:tree token below
space.deep.v1
point Cosmic Cliffs, Carina
…
Moon landers, orbiters, terrain
- mapterrain from lunar orbit, every chunk hashed
- anchorby identity: there is no Earth cell under it
space.deep.v1
point Moon terrain, Kaguya
…
Hubble a telescope in low orbit, tracked on the home page globe
- observeoutward; the observatory's site is a cell, its target an identity
- pointa galaxy mosaic, read by the chunk
observatory.telescope.v1
point Whirlpool galaxy, M51
…
Sentinel-2A · 2B · 2C Earth imagers, sun-synchronous
- capture290 km swaths from a sun-synchronous orbit; an open archive keeps the scenes
- encodeeach 10 m reading as a signed fact, recomputable from that archive
- citea fact, a field, a field over time, a whole scene: four tokens below
earth.satellite.v0
run the handoff above, live
your orbitunder your key
Your satellites an operator's own constellation
- signat capture, on the flight or payload computer
- tracethe execution that made each reading, power and thermal included
- scoreevery write against the open archive where bands overlap
orbital.satellite.v1
plan the Vortx payload that writes this way
…
Launch and crew the ISS, and the rockets that lifted all of the above
- liftevery tracked object carries its launch in its own elements
- addressa launch site as a 10 m cell: the emem:cell token below
look at Europe's Spaceport from orbit
aira moving attester
Drones survey flights
- flywriting along the path, inside one trace window
- landeach reading at the cell it measured
aerial.drone.v1
point Dry lake cracks, drone
groundfleets and rovers
Robots and rovers one memory across fleets
- shareone memory across vendors, no shared backend
- bindevery write to the execution that produced it
robot.fleet.v1
list ALOHA robot, coffee task
groundany Linux host
Any machine a host, a meter, a camera
- tracescheduler, memory, storage, network: counters every Linux exposes
- signwith the device's own key; emem checks, never vouches
host.counters.v1
verify a real device trace below, in this browser
siliconthe key's birth certificate
Hardware roots edge AI, trusted hosts, secure MCUs, phones
- rooteach device key in a hardware root of trust
- waitfor the first published vendor anchor; then the first emem:attestation
list the hardware platforms, live

Mars: JPL approximate Keplerian elements (Standish) · Moon: Meeus, Astronomical Algorithms ch. 47 · L2: the Sun–(Earth+Moon) collinear point from the restricted three-body quintic · all three checked against JPL Horizons · orbiters: the globe's SGP4 states · profiles: emem.dev/v1/substrates, read live · pointers: the ememdemo catalogue, read live.

Every token checks itself.

namenine token shapes, plus state and tree addresses: one grammar, emem:kind:id
resolveeach card fetches its record from emem.dev as it scrolls into view
checkthis browser recomputes the hash or the signature; every line says where it ran

emem:fact: one signed observation

binds cell × band × time to the exact signed bytes
emem:fact:defi.zb493.yiwo.zcb4e:eheadieomxr2zusgh4nx7mfisrtme23ztjiluyrfve64xoap6hka
waiting for view
emem:cell: a bare place

binds nothing yet: an address, until a fact hangs on it. Here: Europe's Spaceport, Kourou
emem:cell:defi.zb43b.mAga.yiwU
waiting for view
emem:entity: one object, co-referred

binds an identity anchor, so two agents mean the same thing
emem:entity:5pitnkcnle3cq6yldbffj52zja
waiting for view
emem:bundle: a case, in one handle

binds which facts are cited; each fact still binds its own bytes
emem:bundle:y2k6h2laeo4libfsiebucdw4mu
waiting for view
emem:raster: a field, at native resolution

binds area × band × date to the grid bytes a world model reads
emem:raster:23vfacx23nr3dwki6si4yrolmmp3wr6dtrhjxbw4rihiaafrpyga:s2.B08:20500:sw7lynliwyqfigyw6oqwso64wmulcumifqorfpfogkngjhsqzjpq
waiting for view
emem:cube: a field over time

binds a manifest of raster slices, each checkable on its own
emem:cube:23vfacx23nr3dwki6si4yrolmmp3wr6dtrhjxbw4rihiaafrpyga:s2.B08:20500..20585:ganwwj25obuob3pp7pjtkd4awtihnluotdowe2cqtrj77af5qlna
waiting for view
emem:rasterset: a whole scene as one handle

binds several fields to the recipe that made them
emem:rasterset:sml5syqegico2sobfkxjp2o2twwepdwve7753ubkoa5n27y22rba:zu5p3u4r5n5uinu2ghwzjo2272ztjvnnf7cnlt7hiqwxo4cq3hhq
waiting for view
emem:trace: how a machine ran

binds an OS execution trace, signed by the device itself
emem:trace:mxyer5c2oxn4ud3xqbtnaxcxhdv4kkxiu67q32inbwxgpa7r3s6a
waiting for view
emem:attestation: the hardware behind a key

binds a device key to the root of trust that vouched for it
emem:attestation:no token minted yet
waiting for view
emem:state: one stage of an answer's reasoning

binds the facts a stage grounded and the stage before it: a chain you can walk
emem:state:6omzeryht75zyabeajuimcqzm7pzenvy3y6p4irwxdpt7x5ayimq
waiting for view
emem:tree: one row of a huge file

binds a chunk to its note's signed root, in log₂(n) hashes. Here: Webb's Cosmic Cliffs
emem:tree:wkxa7tcmw2orf7ujjf5yi66dhe#row=1
waiting for view

Files stay put. Pointers travel.

pointa file at its source: size, chunk table, blake3 per chunk, one Merkle root
namethe pointer note by its own blake3, 26 characters
readonly the chunk you need, by HTTP Range, from the source
checkblake3(chunk) against its row; the root binds every row

A Sentinel-2 near-infrared band over Bengaluru

holdthe whole band stays a cloud-optimised GeoTIFF on AWS Open Data
nameits chunks in a note on emem.dev
readone chunk, from AWS, not from us; your browser hashes it

read the note

catalogue: vortx-ai.github.io/ememdemo/llms.txt, read live · tok = what the note costs a model, raw = what the file's bytes would cost as base64, both as ememdemo states them · point your own file in ememdemo.

Tamper-evident from photon to prompt.

chaineach link below is a check a stranger can run without trusting us
readevery value on this list live from its endpoint; quoted text is emem's own

name
Every fact by the blake3 of its bytes
agent B re-hashed one above · 52 characters, no truncation
sign
Every answer with ed25519, verified offline
every receipt on this page checked in this browser · reference verifier emem.dev/verify
log
Every write into an append-only transparency log
witness
Outside keys co-sign the log's head
trace
Every device write with the execution that made it
one trace re-derived in this browser · chain, root, cid, the device's own signature
root
Every device key to a hardware root of trust
tier
Writes are tiered by reach. Reads are never gated.
score
A public benchmark that prints its own losses
emem.dev/scoreboard · two heats, deliberately not drawn on one track

Check everything. Trust nothing.

Send the token. Keep the pixels.

agent A this tab, holds the fact

agent B a Web Worker, holds only the token

decode the tile agent B read, and the 10 m pixel the fact names

check the capture against the satellite's own orbit

reason what the agent's context receives instead of the imagery

count every byte that moved, by who moved it

Everything that looks writes the same token.

Mars imaged by Hubble; a rover or orbiter joins the same way

Sun–Earth L2 Webb circles it

Moon landers, orbiters, terrain

Hubble a telescope in low orbit, tracked on the home page globe

Sentinel-2A · 2B · 2C Earth imagers, sun-synchronous

Your satellites an operator's own constellation

Launch and crew the ISS, and the rockets that lifted all of the above

Drones survey flights

Robots and rovers one memory across fleets

Any machine a host, a meter, a camera

Hardware roots edge AI, trusted hosts, secure MCUs, phones

Every token checks itself.

emem:fact: one signed observation

emem:cell: a bare place

emem:entity: one object, co-referred

emem:bundle: a case, in one handle

emem:raster: a field, at native resolution

emem:cube: a field over time

emem:rasterset: a whole scene as one handle

emem:trace: how a machine ran

emem:attestation: the hardware behind a key

emem:state: one stage of an answer's reasoning

emem:tree: one row of a huge file

Files stay put. Pointers travel.

A Sentinel-2 near-infrared band over Bengaluru

Tamper-evident from photon to prompt.

Every fact by the blake3 of its bytes

Every answer with ed25519, verified offline

Every write into an append-only transparency log

Outside keys co-sign the log's head

Every device write with the execution that made it

Every device key to a hardware root of trust

Writes are tiered by reach. Reads are never gated.

A public benchmark that prints its own losses

`emem:fact:` one signed observation

`emem:cell:` a bare place

`emem:entity:` one object, co-referred

`emem:bundle:` a case, in one handle

`emem:raster:` a field, at native resolution

`emem:cube:` a field over time

`emem:rasterset:` a whole scene as one handle

`emem:trace:` how a machine ran

`emem:attestation:` the hardware behind a key

`emem:state:` one stage of an answer's reasoning

`emem:tree:` one row of a huge file