Tessa is not a website.
It's your software - apps, data, pages, APIs, history and backups - as one private system you can reach, prove, change and restore. This page proves every claim against the live system, one dismissal at a time. Every button below calls this exact server.
The ladder
Each step is one undeniable artefact. Run them in order; by the end there is nothing left to dismiss.
It serves real pages.
Ten worlds, 300 articles each, every world a subdomain, every page an address. This is a real, navigable estate - below is a live article, served as-is.
"It's just a website." Keep going.
The page IS a coordinate - and one coordinate is both data and page.
The same address served as canonical JSON (the API) and as a structural HTML page. Not two endpoints - one document, two views. The HTML carries enough structure to turn back into the exact JSON, losslessly.
The state is content-addressed - the address IS the data.
An address resolves to a hash of its own content. Recall that hash with no address, no query, no table - and the exact bytes come back. The address is the data.
A whole world collapses to one hash.
An entire world - hundreds of coordinates and their objects
- folds to a single content address. Change one byte
anywhere and the hash changes. That one number is the
world's identity, and /pack is that world as a
portable, byte-exact seed.
The system can prove its own state.
There is no mutation. Every write is an appended, hash-chained record (a command and its result). The whole chain re-verifies on demand. This is the live log of every write that built this estate.
It finds the nearest match with no map.
Hand it an unknown, misspelled address. With no index lookup and no central map, the system returns the closest real address it holds, with a confidence score - the honest answer to a near miss, never a guess.
Change is a captured, replayable journey.
Take snapshot A. Make some changes. Take snapshot B. The change between them is recorded as one addressable journey - what was written, in what order, and whether it passed the checks. Then replay it and arrive at the exact same hash.
This is why deployment, migration, rollback and restore are the same operation here. A fresh server fed the same seed stands the identical world up in seconds, hash-for-hash - proven in the test suite (one box can't show two servers; the portable seed above is the proof you can carry).
The same move grows everything.
The wiki worlds, the journey world, a point-of-sale, a tenant admin - none are separate apps. They are the same system at different data. Adding a capability is a registration, not a rewrite. The write verbs available on this live system:
What this means for you
Each proof above is also a problem that disappears - in plain business terms:
| What you just saw | What it kills |
|---|---|
| One address is both data and page | One source of truth - no front-end/back-end versions to keep in sync, no API drifting from the UI |
| Every write is a verifiable, hash-linked record | A complete, tamper-evident audit for free - no bolt-on logging, no "who changed this and when?" |
| A whole world is one fingerprint + a portable seed | The system stands itself up on any fresh server in seconds; backup, staging clones, migration and disaster recovery stop being projects - they're one copy |
| Capture a change, replay it to the same hash | Deploy, migrate, roll back and restore are the same one-button operation - and "works on my machine" is gone |
The one-liner
What is proven · what is not
Proven, live, on this box
- One address → JSON and HTML views of one record
- The address is the data (recall by hash alone)
- A world = one content address; a portable seed
- Writes are a verifying hash-chained log (no mutation)
- Nearest-match lookup with no index and no map
- Capture → inspect → replay a change to the same hash
Not claimed here
- Restore onto a second server (single box; shown by the byte-exact rebuild test + the portable seed)
- A fully autonomous always-on "living" loop - the adaptive behaviour is proven in tests, not run as a live daemon here
- Business-system generation (a separate proof: generate → run → mutate → audit → restore a tenant)
Reproduce it yourself
Every claim above is one curl away, against this exact origin.