Participants: durgadas, rafa (UTC+1), NicolasCero, Timber, Sachin, Matthew Bright UTC-7, Javier Chavez / UTC -6, Andre Comeau

The session had two overlapping strands that were, unfortunately, largely spoken over each other in the recording: (1) a group discussion of the "Standardization of Time" article as part of an ongoing theme on how technologies get socially adopted and how that relates to protocol development and ossification (last week's session covered QWERTY), and (2) two show-and-tell presentations — durgadas on his "proof of coordination" standards work and NicolasCero on a web-app tool for co-creating AI-adoption protocols for cultural organizations. The transcript is heavily interleaved (multiple speakers overlapping), so some points are fragmentary; those are flagged below.

  • **Rafa** framed the recurring theme: understanding social adoption processes of technologies (currently happening with AI) and how adoption relates to protocol development and ossification.
  • **Sachin:** Noted a coming change (~2030) in how a second is defined via atomic clocks — further subdivision — but argued there's no implication for *human* perception of time (humans don't sense below ~1 second; ~1/10 second visual limit). Suggested finer division is "more advantageous for machines."
  • **Sachin:** Drew the article's parallel that time was socialized through institutions (telegraph, railway) and factories imposing working hours; workers then argued for better-defined hours (ten-hour day ~1848, later eight-hour day). Once adopted, standards become invisible "reality."
  • **Sachin:** Contrasted this with newer tech like LLMs, where top-down institutional mandates on adoption have largely failed or met political opposition; people can't even agree on defining terms like AGI. Noted media increasingly use "superintelligence" as an unverifiable, pre-emptive socialization of an idea.
  • **Rafa:** Was disappointed the paper didn't speculate about where time-standardization is heading beyond time zones. Argued the paper underestimates the "centrality of the *now*" — a *present-local* (not geographically local) mode of coordinating actions relative to the present moment, exemplified by constant chat-based "in five minutes?" negotiation. Acknowledged this view may be biased by living online.
  • **Matthew:** Connected the reading to David Landes' *Revolution in Time*. Argued time reckoning is still not settled across cultures (e.g., Arizona not adopting daylight saving; possible political moves to revoke DST). Enjoyed the paper's opening on alternative ways to reckon time (cited a Kurt Vonnegut line about measuring a life in wives/cigarettes/quarts of booze; also sports measuring by periods/sets, or weight). For AI, the most obvious non-standard time reckoning is **token usage** — quantified by cost or imposed as rate limits — plus recurring qualitative "capability jump" moments (ChatGPT launch, the "DeepSeek moment," and model releases he called "Fable" and "Mythos"). Raised the management question of when to update AI models/workflows.

Reading: "The Standardization of Time" (linked in the session chat; author not stated in the transcript). From the discussion it appears to be a historical/sociological article — participants noted it was likely published in the 1980s and covers time zones, the telegraph and railways, and atomic clocks. Matthew connects it to David Landes' book *Revolution in Time* on the Swiss watch industry as roughly contemporary material.

The session had two overlapping strands that were, unfortunately, largely spoken over each other in the recording: (1) a group discussion of the "Standardization of Time" article as part of an ongoing theme on how technologies get socially adopted and how that relates to protocol development and ossification (last week's session covered QWERTY), and (2) two show-and-tell presentations — durgadas on his "proof of coordination" standards work and NicolasCero on a web-app tool for co-creating AI-adoption protocols for cultural organizations. The transcript is heavily interleaved (multiple speakers overlapping), so some points are fragmentary; those are flagged below.

  • **Rafa** framed the recurring theme: understanding social adoption processes of technologies (currently happening with AI) and how adoption relates to protocol development and ossification.
  • **Sachin:** Noted a coming change (~2030) in how a second is defined via atomic clocks — further subdivision — but argued there's no implication for *human* perception of time (humans don't sense below ~1 second; ~1/10 second visual limit). Suggested finer division is "more advantageous for machines."
  • **Sachin:** Drew the article's parallel that time was socialized through institutions (telegraph, railway) and factories imposing working hours; workers then argued for better-defined hours (ten-hour day ~1848, later eight-hour day). Once adopted, standards become invisible "reality."
  • **Sachin:** Contrasted this with newer tech like LLMs, where top-down institutional mandates on adoption have largely failed or met political opposition; people can't even agree on defining terms like AGI. Noted media increasingly use "superintelligence" as an unverifiable, pre-emptive socialization of an idea.
  • **Rafa:** Was disappointed the paper didn't speculate about where time-standardization is heading beyond time zones. Argued the paper underestimates the "centrality of the *now*" — a *present-local* (not geographically local) mode of coordinating actions relative to the present moment, exemplified by constant chat-based "in five minutes?" negotiation. Acknowledged this view may be biased by living online.
  • **Matthew:** Connected the reading to David Landes' *Revolution in Time*. Argued time reckoning is still not settled across cultures (e.g., Arizona not adopting daylight saving; possible political moves to revoke DST). Enjoyed the paper's opening on alternative ways to reckon time (cited a Kurt Vonnegut line about measuring a life in wives/cigarettes/quarts of booze; also sports measuring by periods/sets, or weight). For AI, the most obvious non-standard time reckoning is **token usage** — quantified by cost or imposed as rate limits — plus recurring qualitative "capability jump" moments (ChatGPT launch, the "DeepSeek moment," and model releases he called "Fable" and "Mythos"). Raised the management question of when to update AI models/workflows.

Questions & Disagreements: - **Is time standardization "already done"?** Raised by (per Sachin) "Bert." Responses diverged: Sachin pointed to atomic-clock re-definition but said human perception is unaffected; Matthew argued it's *not* settled culturally (DST, cross-cultural reckoning); Javier said practical value is maxed out and only well-being would drive change. - **Machine vs. human time:** Sachin, Andre, and Matthew (

Participants: durgadas, rafa (UTC+1), NicolasCero, Timber, Sachin, Matthew Bright UTC-7, Javier Chavez / UTC -6, Andre Comeau