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
53 claims
“Our technologies are almost exclusively implemented as services”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Amazon's technologies are almost exclusively implemented as services with hardened interfaces as the only access to functionality.
Resolved true The record shows it happened or was so.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
Judged as of 2011. The claim is qualitative: 'almost exclusively' means that nearly all of Amazon's technology was built as services reached through service interfaces/APIs (a service-oriented architecture). True: credible descriptions from around 2011 (Amazon engineering accounts, CTO talks, technical papers, documented internal mandates) show that Amazon's systems were overwhelmingly structured as services reached only through interfaces. Mostly true: a services architecture predominated, with notable but limited exceptions. Mixed: services were a major part, but much of the technology stayed monolithic or was reached directly. Mostly false: services were a minority approach. False: Amazon did not use a service-oriented architecture.
Evidence
- Amazon Architecture - High Scalability High Scalability · 18 September 2007
“The databases were split into small parts and around each part and created a services interface that was the only way to access the data.”
- Amazon Architecture - High Scalability High Scalability · 18 September 2007
“Internally it's a service oriented architecture. You can only access the data via the interface.”
- I was at Amazon for about six and a half years, and now I' ... sriramk.com (hosted copy of a former Amazon engineer's essay) · 9 August 2026
“Over the next couple of years, Amazon transformed internally into a serviceoriented architecture.”
- Modern applications at AWS All Things Distributed (Werner Vogels, Amazon CTO) · 28 August 2019 Own record
“With this manifesto, we began restructuring our application into smaller pieces called "services" that enabled us to scale Amazon dramatically.”
Reasoning
A 2007 independent article on Amazon's architecture describes Amazon's internal architecture as service-oriented [E1][E2]. It says databases were split up, with a services interface that was the only way to access the data (E1, E2). A former Amazon engineer's essay says the company transformed internally into a service-oriented architecture over a couple of years (E3). The CTO's own later account of restructuring the application into services (E4) agrees with this. Together these sources describe Amazon's internal architecture as service-oriented, with data reached only through service interfaces, though none of them gives a figure for how much of its technology was built this way.
Cite this claim
Jeff Bezos, “Amazon's technologies are almost exclusively implemented as services with hardened interfaces as the only access to functionality.” (said 2011). Verdict: resolved true. Reliability API, claim c_81228092beba, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_81228092beba
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.