The live claim
A live board may say “this session is doing X now.” It may not say “this is the day’s conversion” unless you have stated sampling, late events, and retries in the same breath.
Live Atlas
A map for usage that has not sat still.
Real-Time Usage Analytics is not a faster dashboard. It is a different reading: the product is still mid-sentence. Live Atlas is our public sketch of that reading — what the socket may claim, what it must not, and where a Bangkok team usually goes wrong before lunch.
The lag cousins
Producer retry, consumer backlog, and warehouse land time look identical on a red chip. Atlas trains the habit of naming which cousin you are looking at before anyone pages.
The local path
PromptPay confirmations, COD hand-offs, and dual-SIM session splits are not edge cases in Thailand. They are the main text. A live atlas that ignores them is a postcard.
How we use the Atlas inside the studio
On the first evening of the Live Usage Lab, pairs pin their current live board against three Atlas questions: What is this number allowed to mean? What arrives late on purpose? Which Thai payment hop is invisible? Most boards fail at least two. That is not a humiliation ritual; it is how we decide which module to weight.
The Atlas is also how Floor Cohort chooses a shared ledger. Eight people cannot “align on real-time” in the abstract. They can agree that checkout_paid fires only after the PromptPay callback, and that the live chip must show “intent” until then. Agreement is a sentence, not a vibe.
If you only want the map without the lab, read the journal essays on sampling and session inflation, then write to us with a screenshot of one chip you no longer trust. We would rather answer that email than sell you a metaphor.