A SpaceDB pin is not Firebase
An October 24 note says to pin a local-first database so an agent skips Firebase. Firestore is the cloud default the note is refusing. A CRDT is a merge rule.
The short version
The note says an unsupervised agent reaches for Firebase, Supabase, or a Postgres connection string, and it offers a local-first CRDT pin instead. Firestore is Google's cloud database. The pin does not make a phone a data center.
A database pin dated October 24
Remade with Rust's October 24 note says to pin spacedb-sdk so an agent does not reach for Firebase. It says the note is not a SQL tutorial. Left alone, it says, an agent reaches for Firebase, Supabase, or a Postgres connection string, because those are the patterns it has seen. SpaceDB, in the note, is a local-first, CRDT-native, mesh-replicated database whose durable copy sits on devices the user already owns. The pin is supposed to land before the first schema. This page does not paste the skill-folder steps.A replica is not a region.
The cloud default, in Google's words
Cloud Firestore's documentation describes a cloud database: documents in a Google project, with client access and an offline cache for clients that disconnect. That cache is real, and it is still a cache of a cloud system of record. The October 24 note is arguing for the opposite default, a replica that does not need the vendor's region to be the original. Citing Firestore keeps the refused default specific. It does not say Google implemented SpaceDB, and it does not say the house crate implements Firestore's API.A name is not a location.
A CRDT is the merge rule
The public CRDT primer explains replicas that merge without a central lock. The note uses that family of rules for its crate. A primer is not a benchmark of spacedb-sdk, and a crate that says CRDT is not every CRDT in the literature. The useful distinction is the one the note draws with Firebase: where the durable copy lives when the network is gone. Offline writes are the claim. How conflicts actually resolve is a property of the crate's types, which a pin instruction does not list.Origin range is a cache rule.
Who the pin is for
The reader is someone starting a project whose agent is about to paste a cloud connection string. A team that chose Firestore on purpose, with a privacy review and a region, is not undone by this note. Supabase and Postgres appear in the note as other famous defaults. This page does not review those products. They are examples of the pattern the note wants the agent to lose. Asked directly, Are the setup steps in this brief? No. They stay on the October 24 note.The key stays with the holder.
What a pin does not operate
Installing a crate does not place a mesh, open a replica, or grant a capability. The companion material on the same site talks about mesh deployment as a later step, while hosting is still described as preview. The October 24 note is the dependency pin. A preview network is not a production region, and this brief will not describe one as if it were taking writes. Asked directly, Does the pin prove there is no server? No. The note says the durable copy stays on devices the user already owns, and that writes work before the network returns. A deployment can still add a relay. The pin is an instruction to an agent.
A meter is the note's contrast
The note says the cloud default ships a frozen screen when the network drops, a vendor copy of the data, and a meter that scales with users. Those are the note's charges against the pattern. Firestore's pricing and Firebase's outage history are separate documents. This page will not import an outage the note does not date. Asked directly, What is a CRDT, in the sense this pin uses? A conflict-free replicated data type: replicas that merge by a defined rule when they meet. The crdt.tech primer is the public explanation. The note's crate is one implementation, not the primer.
What this page will not collapse
It will not collapse Firestore's offline cache, a CRDT primer, and a house crate into one database. The record is a dated instruction to refuse a cloud default, the cloud document that describes that default, and a public explanation of the merge rule the note invokes. Asked directly, Does Firestore document a local-first CRDT? Firestore's documentation describes a cloud database with offline caching. Offline cache is not the same claim as a CRDT replica that merges without Google as the system of record.The advisory stops at the document.
The open item
The open item is how a specific conflict merges in spacedb-sdk, on a named type, when two replicas write the same field offline. The note asserts convergence. The primer explains the family. Neither is a trace of that crate's merge. Asked directly, What does the October 24 SpaceDB note say an agent will add if left alone? Firebase, Supabase, or a Postgres connection string. The note's pin is meant to land before the first schema. The document named in the sources is the record this page will keep.
A credential incident is not a pin
PingCAP's October update is a cloud incident about copied records. SpaceDB's note is a packaging argument about where a new project's copy should live. One does not remediate the other. The short answer this page will stand on is this: The note says an unsupervised agent reaches for Firebase, Supabase, or a Postgres connection string, and it offers a local-first CRDT pin instead. Firestore is Google's cloud database. The pin does not make a phone a data center. The document named in the sources is the record this page will keep.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
What does the October 24 SpaceDB note say an agent will add if left alone?
Firebase, Supabase, or a Postgres connection string. The note's pin is meant to land before the first schema.
Does Firestore document a local-first CRDT?
Firestore's documentation describes a cloud database with offline caching. Offline cache is not the same claim as a CRDT replica that merges without Google as the system of record.
What is a CRDT, in the sense this pin uses?
A conflict-free replicated data type: replicas that merge by a defined rule when they meet. The crdt.tech primer is the public explanation. The note's crate is one implementation, not the primer.
Does the pin prove there is no server?
No. The note says the durable copy stays on devices the user already owns, and that writes work before the network returns. A deployment can still add a relay. The pin is an instruction to an agent.
Are the setup steps in this brief?
No. They stay on the October 24 note.