Protobuf fields
an int32 field is a contract with every reader, in every language generated from the .proto
Answers
POST /v1/snapshots returns the quote; POST /v1/questions asks, two at a time per account. GET /v1/answers/{id} returns the JSON, also a readable document, as Markdown or PDF.
The answer opens on the question, the commit and three counts. Then each place by service, with its file, its line and why it was listed.
The figures are from the order-id scenario, not from a customer.


Each top-level directory is a block sized by its tokens. Every lit hop is a place on the list.
Each one is its own change, owned by a different team and shipped on a different day.
an int32 field is a contract with every reader, in every language generated from the .proto
pa.int32() sits in the declaration, and nothing fails until the first row past the limit is written
the 32 bits live in a loader's type map, or in a partner's importer outside the repository
compiled against their own copy of the DTO, out of sight of the next service's checker
cast to int and formatted into a string, where no type system follows
CAST(order_id AS INT) in a warehouse where INT is 32 bits, failing only when it runs

Each re-ask reads the new commit in full. If the reader's version changed in between, the answer says so.
Send the new commit with reask_of set. Every place comes back changed, unchanged, new or gone since the last answer.
Six weeks in - 24 now 64-bit, 7 still 32-bit, 1 new
Eleven weeks in - 31 changed, 1 still 32-bit, none new
Marked not this value - off the list until its line changes