# Jack Dorsey

> 1976– · Entrepreneur, Co-founder of Twitter
>
> **Recorded contribution:** Co-founded Twitter; Square/Block

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Jack Dorsey co-founded Twitter and served in several leadership roles there; he also co-founded Square, later Block. His computing-history relevance lies in helping establish two public infrastructures: a short-message social network organized around follows and timelines, and developer-accessible payment hardware and software for small merchants.

## 2. The problem inherited

Mobile users lacked a simple public mechanism for broadcasting short status updates, while many small merchants faced high friction accepting card payments and integrating transactions into software.

## 3. The central contribution

Dorsey co-founded Twitter and Square/Block, shaping products that converted messages and payments into programmable network events.

## 4. Reconstruct the mechanism

1. Represent each post or transaction as a timestamped event with stable identities.
2. Route events through a social graph or payment network to authorized recipients.
3. Maintain durable records, ordering, and user-visible status under retries and partial failure.
4. Expose APIs and applications that let third parties build around the event stream.

## 5. What changed downstream

- Twitter became major infrastructure for real-time public communication, journalism, politics, and harassment alike.
- Square lowered the product and hardware barrier for some small merchants to accept digital payments.

## 6. Attribution, limits, and uncertainty

- Both companies were collective ventures with disputed or shared founding and product credit; executive visibility is not equivalent to sole technical authorship.
- Public feeds and payment networks concentrate governance power and create moderation, fraud, surveillance, labor, and financial-inclusion trade-offs.

## 7. Reconstruction lab

Specify an idempotent payment event and a public-post event. For each, trace identity, authorization, ordering, retry, moderation or dispute, and the durable audit record. Deliver duplicates and out-of-order events to both systems. Decide whether a repeated post is harmless while a repeated debit is catastrophic, and encode the difference. Add account compromise and specify recovery authority. Comparing the event models shows why a compact interface can hide radically different obligations: social publishing prioritizes audience, ranking, and speech governance, whereas payments require conservation of value, reconciliation, regulated identity, and reversible dispute processes. For both designs, state which facts must be immutable, which may be corrected, and who has authority to perform the correction when automated rules conflict with human claims.

## 8. Evidence trail

- [Twitter Form S-1](https://www.sec.gov/Archives/edgar/data/1418091/000119312513390321/d564001ds1.htm) — U.S. Securities and Exchange Commission
- [Block filings](https://www.sec.gov/edgar/browse/?CIK=1512673&owner=exclude) — U.S. Securities and Exchange Commission
- [Jack Dorsey](https://en.wikipedia.org/wiki/Jack_Dorsey) — Wikipedia contributors

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*