The event contract
Name, trigger, required properties, owners, and a kill date. You rewrite one messy catalogue from a real (anonymised) SEA consumer app until a stranger can implement it.
Flagship course
Six modules for people who already ship product and still do not trust the live numbers. You work a synthetic generator on our floor in Bangrak, or join the remote mirror of the same lab.
Name, trigger, required properties, owners, and a kill date. You rewrite one messy catalogue from a real (anonymised) SEA consumer app until a stranger can implement it.
Push vs pull, batch windows, and what “exactly once” actually costs. The generator drops duplicates on purpose; you decide which layer is allowed to dedupe.
Head, tail, and identity-preserving sample rates. Payment and auth paths stay at 100%. You will break a dashboard by over-sampling, then repair it.
Where the queue lives on mobile, what blocks first paint, and how to prove a flush policy. We measure on a mid-range Android we keep in the studio.
Thresholds, quiet hours, flapping, and an escalation card. If the rule would wake a stranger for DAU wobble, it fails the room.
A twenty-minute defence: one contract page, one alert, one known limitation. Alumni often reuse this artefact in their own incident reviews.
Araya spent nine years on instrumentation for a regional super-app before opening the Bangrak studio. She still reviews alumni contracts on Thursdays. She will not debug your production cluster; she will make you write the page that would have prevented last quarter’s false page.
Signal Desk (one practitioner) is listed at ฿18,500. Gallery Pass (two seats plus a shared office-hour) is ฿48,000. Estate License seating for this flagship is quoted from the desk. There is no payment form here; invoices, if you proceed, go out by email from info@agent-gridhub.digital.
No. The live stream lab uses a synthetic event generator, not your production app. You will not leave with a drop-in SDK for your stack. You leave with a written instrumentation plan and a working sandbox pipeline. That limitation is deliberate: we will not take your keys, and we will not pretend a three-evening studio replaces an implementation team.
You should be able to read JSON and talk about a release train. SQL helps in module three; we do not assume you write native mobile code. Product and engineering pairs are the usual seating.
Same generator, same worksheets, same defence. You lose the mid-range Android we pass around the Bangrak table; we ship a measurement trace instead. Some people prefer that.
Module one will feel slow. Several alumni said so. Modules three and five still tend to change how they sample and page. Read the reviews if you are on the fence.
“We arrived with 214 names. The contract exercise was tedious and I almost skipped Thursday. By Friday the catalogue was 61 and the failed-transfer rule was the only thing allowed to ring. I would not call it pleasant. I would sit it again.”
Araya stopped me from alerting on DAU. Module four on flush latency was the piece I still quote in iOS planning. Three stars from my PM partner — they wanted more funnel storytelling, which lives in a different course.
Name, email, and a short note. We reply within two Bangkok business days.