Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
84 79 88 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
Insufficient record: 2 predictions resolved, 5 needed for a score.
-
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 3 promises resolved, 5 needed for a score.
-
Guidance
A company's own figures for its results over a period, checked against what it then reported.
Insufficient record: 1 guidance claim resolved, 5 needed for a score.
All types combined: 84 (likely 79 to 88, high confidence), from 90 claims: 90 factual claims. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Jeff Bezos's claims
35 claims
“this approach was applied at Amazon long before SOA became a buzzword in the industry.”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Amazon applied service-oriented architecture long before SOA became an industry buzzword.
Mostly true True in substance, wrong in a detail.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
True: historical accounts (Amazon engineering talks or interviews, such as Werner Vogels's 2006 ACM Queue interview, or industry histories) show that Amazon had moved to a service-oriented architecture by the early 2000s or earlier, several years before 'SOA' became widely used as an industry buzzword (about the mid-2000s). Mostly true: Amazon adopted SOA early, but only slightly before, or at about the same time as, the term took off. Mixed: the timing is unclear or the evidence conflicts. Mostly false: Amazon adopted services at about the same time as or after the term became popular, with only small earlier experiments. False: the evidence shows Amazon adopted SOA well after it became a buzzword.
Evidence
- Tracing Amazon's Management Practices Back to Their Origins: Borrowed Ideas, Independently Reached Concepts, and Things They Keep Fixing Zenn (akring, individual author blog post) · 8 October 2026
“Vogels stated this was "long before service-oriented became a buzzword," and in the same conversation he also articulated the operational principle "You build it, you run it."”
- Tracing Amazon's Management Practices Back to Their Origins: Borrowed Ideas, Independently Reached Concepts, and Things They Keep Fixing Zenn (akring, individual author blog post) · 8 October 2026
“The widely known text of the mandate is not an official Amazon document.”
- Steve Yegge’s Google Platforms Rant University of Washington CSE 452 course archive (repost of Steve Yegge’s 2011 Google+ post) · 2011
“But on one occasion – back around 2002 I think, plus or minus a year – he issued a mandate that was so out there, so huge and eye-bulgingly ponderous,”
- Steve Yegge’s Google Platforms Rant University of Washington CSE 452 course archive (repost of Steve Yegge’s 2011 Google+ post) · 2011
“Over the next couple of years, Amazon transformed internally into a service-oriented architecture.”
Reasoning
Steve Yegge dates a mandate to about 2002, plus or minus a year (E3). He says Amazon became a service-oriented architecture internally over the next couple of years (E4), which puts the shift at roughly 2002–2004. E1 reports Werner Vogels saying this was "long before service-oriented became a buzzword", and E2 notes that the widely known text of the mandate is not an official Amazon document. The evidence shows Amazon adopted services early, but it ends at about the mid-2000s, when the criteria say the term took off. So it does not clearly show the "several years" gap that a full true verdict needs.
Cite this claim
Jeff Bezos, “Amazon applied service-oriented architecture long before SOA became an industry buzzword.” (said 2011). Verdict: mostly true. Reliability API, claim c_45debddd9a70, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_45debddd9a70
Claims without a verdict
Is a verdict here wrong, or do you speak for Jeff Bezos? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.