habitat

Habitat is a visible boundary between people, meaning and models.

Models now sit inside the rooms where records are kept — the documents, the datasets, the files someone has to stand behind. Until now, nothing held what a model does apart from what a person does. Every tool on offer makes the model's voice part of the record it touches, and every record becomes, a little, the model's.

Habitat is instrument, not interpretation.

What your documents say stays yours.

Your highlights, your notes, your reading build your own record, and nothing rewrites them. When a community asked that nothing ever learn from their documents, the architecture could enforce it rather than promise it.

See how that held →

What the model said stays the model's.

A model can read beside you and speak about what it sees. It cannot write into your record. That is a wall in the architecture, not a policy.

The place where you can watch that wall tested isn't built yet. This note stays until it is.

What happened is what happened.

Records here only grow; nothing is revised in place. Every number published reproduces from its own bytes, on your machine. When we have been wrong, the withdrawal is printed where the claim was.

Read the corrections, dated →

Three public records.

Three kinds of material, one unadjusted instrument. Every number below reproduces from its own bytes.

Text reading

A region reads its climate.

Twenty-seven documents from one cape: the town and its agencies, the people who live here, working life, the marsh and fisheries, and the study of what may come. Habitat reads how far each voice bends from the room they share — and every one of the five is more tangled on its own than the room is.

the Cape Ann reading →
Quantitative receipt

Get a receipt when data changes.

On a public survey, dropping the rows that produce a finding moves the reading 32 times further than an innocent change of the same size — and that ratio holds whichever way you measure the data's own churn. It says the step moved the finding. It does not say the finding was wrong.

the worked case →
Recompute

See when a lending record changed shape.

Seventeen thousand public mortgage filings. Reorder every row: the file's hash flips, the reading holds byte for byte. Change a single value: the file barely moves, the reading does. A checksum reports both of those backwards.

recompute it below →

Read a mortgage record.

Seventeen thousand mortgage filings enter. Habitat reads their shape and publishes one number. Recompute it here, from the bytes this page serves — nothing is sent.

the readingin your tab · nothing sent

Reorder the rows and the reading holds, byte for byte, while the raw-bytes hash moves. That difference is the whole claim — and a checksum cannot make it.

Habitat reads history.

164 letters between John Adams and Thomas Jefferson, 1812–1826. Choose a passage and the field hands back the passages it couples to, each carrying the words that admitted it. Your margin notes persist. The letters never change.

A letter, read.
A reader's comment, kept as theirs.
The field's answer.
Three readers, one margin.

A user-composition can be read, highlighted, composed into, reviewed as a living document, and commented on, wholly intact.

An agent reading the user-document can speak about what it sees, but it cannot write into the record.

Why a visible boundary.

The world has, at present, two so-called boundary tools. A watermark: the generator marks its own output, and the mark travels with the artifact without provenance. A classifier: trained to answer is this generated? — a question that gets harder every month. Both interrogate an artifact that can be endlessly remade.

Habitat hands you a receipt.

Apparatus

withdrawn 2026-07-15 does it localize — a third test we published: when the geometry moves, does it independently name the coupling the operation touched. Circular. The control drops the rows that produce the coupling it then measures; a decoy coupling crowns itself the same way. No rank is published. Whether a non-circular version holds is untested and unclaimed.
corrected 2026-07-15 “byte-for-byte on any machine” — false as written. Corrected to: on any engine that follows the published canonicalization. The cross-platform matrix is written and has not run.
died on the bench the reader-relative reading — as shipped it moves with a constant we chose, and its asymmetry is broken by our own one-sided conditioning, not spoken by the corpus. It stays a door until a pre-registered bench clears it.
open one shipped kit decides a published verdict through a chosen cut (3.0). Under review; the two affected rating plates are withheld until it resolves.
the anchor checked besides us: one recomputation run blind from shipped bytes, in a separate session, artifacts frozen at lock, the executor’s conflict stated on its face. Where it is weak: the fingerprint you check against is printed on a page we control, the signing key is a development key, and there is no transparency log.