What the in-the-wild note says is already deployed

What the note claims is live

The Remade field note on mata.network in the wild says the site is the live Digital Freedom toolkit and Disco Party mesh, and that identity, SpaceDB, codecs, and the related crates are deployed as product. This page files that sentence and does not paste the rest of the note. The dependency is whether the system of record the toolkit points at is a named mesh a reader is told is running, rather than a white paper. The mesh the note names is mata.network.

What the database note says is deployed

A figure that is not in those pages is not in this brief. The SpaceDB note calls the database local-first and CRDT-native, with replicas near the user. The in-the-wild note says that database is part of what is deployed. One note is the kind of store. The other is the claim that the store is in the running toolkit. A content address is what a content address is.

What the essay does not prove

The Ink and Switch local-first essay argues that software can keep its data on the user's machines. It does not mention this mesh, and it cannot confirm that a particular site is up. The essay is the meaning of the adjective. The field note is the claim that a named network is live. The desk is Distributed Cloud.

Why it matters on this desk

The dependency is a control plane a reader is told already exists, as opposed to a replica design that might be built later. If the note is right, the toolkit is a place, not a plan. If the note is only a catalog, the word live is doing too much work, and this page would be overselling a brochure. The page treats it as a claim, sourced, not as an audit. A partition is what a partition does to a write.

What this page will not merge

The dependency stays the one those sources actually support, including the limit they state. Canonical's October 8 website disruption is a different operator and a different set of names. A reader who lost ubuntu.com did not, on these documents, lose this mesh, and a reader who can open the toolkit has not proved Canonical's status. Those briefs stay separate. The October 8 status is what Canonical's October 8 statement says was down.

Where the documents split

The in-the-wild note says deployed. The SpaceDB note says what the database is. The essay says what local-first has meant in public. None of the three is a status page with an error budget. The overlap is the architecture's vocabulary. The live claim is only in the field note. Read together, the filed pages are the record, and a later paraphrase would not replace them. The front of the paper is Futureweb.

What to watch next

A status incident on the named mesh would turn the live sentence into a dated claim with an exception. A note that walks back deployed would replace the sentence outright. The essay will not be the document that does either. It was never a monitor. Live is the word that makes the field note a place rather than a catalog. The note says identity, SpaceDB, codecs, and the related crates are deployed as product on the Disco Party mesh. The SpaceDB note says what kind of database that name refers to: local-first, converging without a data center. The Ink and Switch essay says what local-first has meant in public, and it does not ping the site. This page does not add a user count or an error budget the note did not print. Canonical's October 8 outage is a different operator. Losing ubuntu.com does not, on these documents, say anything about this mesh, and opening the toolkit does not repair Canonical's status. If the note later calls the toolkit a preview, the word live has to leave. Until then the claim stands as a claim, sourced, and unaudited. Deployed as product is a stronger sentence than a repository badge. The note used the stronger sentence. This page repeats it as the note's claim and does not add a census, a latency figure, or a list of cities. The essay cannot confirm it. The database note can only say what kind of store the name points at.

What would change the record

If the field note is revised to call the toolkit a preview, the word live has to leave this brief. If SpaceDB's description changes, the kind-of-database sentence changes and the deployed claim might remain. The documents are allowed to move separately. This page will not use one to launder the other.

What stays a claim of a place

What stays specific is a field note that calls mata.network the live toolkit and Disco Party mesh, with identity, SpaceDB, codecs, and the related crates deployed as product. The SpaceDB note says the database is local-first and converges without a data center. The local-first essay is the public argument, not a heartbeat. This page does not paste the note, does not invent a user count, and does not treat a Canonical outage as this network's outage. The dependency is the place: a named mesh the note says is already running, holding the sort of replica the database note describes. A white paper would not need the word live. The note used it. That word, and no extra census, is the brief.