Companion data set · August 2026

Geostore comparative archive: 10,936 declarations, 2024 next to 2026

The 2026 binary answers the question "which values?". The March 2024 documentation answers "what does it mean?". This archive puts the two side by side: on one side the structure read in the binary, on the other the 2024 prose when it exists, and the tags removed from the client scope rendered as numbered holes rather than hidden.

loading the index...

Download everything Read the full study

Terms are combined with AND. Prefix a term with - to exclude it, wrap it in quotes for an exact phrase, or aim it at one field:

name:rankthe declared name only
parent:FeatureProtothe owning message or enumeration
pkg:geostorethe protobuf package
file:feature.protothe schema file
type:stringthe declared type of the field
doc:"edit resistance"the March 2024 prose only
tag:42an exact field or value number
kind:typetype, attribute or signal
status:added_2026one of the six states
is:documentedhas 2024 prose attached
is:deprecatedmarked deprecated
is:reservedtag removed from the client scope

0 entries

unpacking the index...

Take the whole thing and dig on your own

The archive is served from one file, and that file is downloadable. No account, no form, no API key. Everything the page displays is in the dump, in the same shape: one object per declaration, plus a meta block with the counters.

Everything, one archive

ZIP · 567 KB

JSON and CSV together, plus a README that documents every column and every state. This is the one to take if you are not sure which format you want.

Download the ZIP

JSON

JSON · 4.2 MB

The full data set, indented, one object per declaration. Load it in a notebook, a script or a graph database and keep the parent / child structure intact.

Download the JSON

CSV

CSV · 2.2 MB

The same rows, flattened, semicolon separated, UTF-8 with BOM so Excel opens it without mangling the accents. Sort, pivot, filter.

Download the CSV

What each column holds

kind	`type` for a message or an enumeration, `attribute` for a field, `signal` for an enumeration value.
subkind	message, enum, enum_value, optional, repeated, required, reserved, leak_model, leak_field.
name / parent	the declared name, and the message or enumeration that owns it.
package / file	the protobuf package and the schema file the declaration belongs to.
tag	the field number, or the number of the enumeration value. It is the stable identifier, not the name.
type	the declared type of the field, dotted names pointing at other messages of the corpus.
status	one of the six states described in the left column of the explorer.
model_2024	name of the matching 2024 model when the two sides could be paired.
doc_2024	the March 2024 prose, verbatim, never rewritten.

The corpus is declarative. It describes what the schema declares, not what the system does. A field that exists is not a field that is populated, and a signal that is declared is not a signal that is weighted. Enumeration values carry binary_only by construction: the 2024 documentation describes models and fields, not enumeration values.

Other sources and studies

August 2026 Google Map dissected: 72 ranking signals and the architecture linking the Web, places and AI July 2026 What ChatGPT pulls, what it shows, what it cites July 2026 ChatGPT experiments tracker: what OpenAI tests before rollout July 2026 How your Google phone tracks you to "serve you better" June 2026 3,729,456 Google internal URLs, without opening a single one June 2026 What Google is really building June 2026 Inside Pinterest's algorithm June 2026 How Chrome classifies websites internally May 2026 Tomorrow's AI phone, seen from inside a Google APK May 2026 Ranking of the top Google Preferred Sources More stuffs...