{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"thinker-eric-brewer","title":"Eric Brewer — The CAP Theorem","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Eric Brewer — The CAP Theorem**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Eric Brewer — The CAP Theorem\n\n## §SELF — thinker-eric-brewer\n\n**What this page is:** An explanation of a theorem that governs all distributed computer systems.\n**What it explains:** The CAP theorem and why distributed systems must choose between consistency and availability.\n**Why read it:** To understand why no distributed database can be fully consistent and fully available at the same time.\n\n### What the CAP Theorem Is\n\nThe CAP theorem was proposed by Eric Brewer (born 1965), a computer scientist at UC Berkeley and Google, in a keynote address in 2000. It was formally proved in 2002 by Seth Gilbert and Nancy Lynch of MIT.\n\nCAP names three properties of a distributed data store (a system where data is stored across multiple connected computers):\n\n- **Consistency (C):** Every read receives the most recent write. All nodes (individual computers in the system) see the same data at the same time.\n- **Availability (A):** Every request receives a non-error response. The system responds to every query, even if the data is not the most recent.\n- **Partition tolerance (P):** The system continues to operate despite network partitions — situations where messages between nodes are lost or delayed.\n\nThe theorem states: in a distributed data store, you can guarantee at most two of the three properties.\n\n### Why It Matters\n\nThe theorem matters because network partitions (P) are inevitable in real systems. Cables fail. Routers reboot. Data centers lose connectivity. If a partition occurs, the system must choose: either preserve consistency (C) by refusing some requests, or preserve availability (A) by serving possibly stale data.\n\nThis is not a technological limitation that better engineering will solve. It is a logical limit proved by the Gilbert-Lynch proof.\n\n### The Key Idea: The Trade-off\n\nIf the network partitions (P), you must choose between consistency (C) and availability (A). You cannot have both.\n\n- Choose CP: The system blocks writes until consistency is restored. Some requests fail. The system is consistent but not fully available.\n- Choose AP: The system accepts all writes and serves all reads. Some responses contain stale data. The system is available but not fully consistent.\n\nMost real-world distributed systems choose AP and handle consistency asynchronously (in the background). They accept that different nodes may see different data for a short period, and they resolve differences later.\n\n### What Brewer Got Right\n\n- Identified the three properties that matter in distributed systems design.\n- Showed that the choice between them is a logical necessity, not an engineering failure.\n- Forced system designers to be explicit about which properties they prioritize.\n\n### What Brewer Got Wrong or Left Unfinished\n\n- The theorem is often stated as \"pick two of three,\" which implies you could build a system that is CA (consistent and available) but not partition-tolerant. In practice, network partitions are unavoidable, so every real system must tolerate partitions. The actual choice is between CP and AP, not among all three pairs.\n- The theorem does not quantify the trade-off. It does not say how much consistency you lose for a given gain in availability.\n- Brewer later noted that the theorem describes a binary at partition time, but real systems operate on a spectrum between strong consistency and eventual consistency.\n\n### How It Connects to Other Ideas\n\n- **ACID vs. BASE:** ACID (Atomicity, Consistency, Isolation, Durability) describes the properties of traditional relational databases, which prioritize consistency. BASE (Basically Available, Soft state, Eventual consistency) describes the properties of many distributed databases, which prioritize availability. CAP explains why BASE exists.\n- **Consensus protocols (Paxos, Raft):** These algorithms achieve strong consistency in distributed systems by requiring a majority of nodes to agree before committing a write. They implement the CP choice. CAP explains why these protocols are necessary and why they add latency.\n\n### Sources\n\n- Brewer, Eric. \"Towards Robust Distributed Systems\" (keynote, PODC 2000).\n- Gilbert, Seth, and Nancy Lynch. \"Brewer's Conjecture and the Feasibility of Consistent, Available, Partition-Tolerant Web Services.\" *ACM SIGACT News* 33, no. 2 (2002): 51–59.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-eric-brewer`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-eric-brewer`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Eric%20Brewer%20%E2%80%94%20The%20CAP%20Theorem`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-eric-brewer"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-eric-brewer/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:33.005Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"8bf3f68c51344dee05049a7f9a91576984f4c6f69560641486f5be08aff13605"},{"ts":"2026-07-17T02:42:38.618Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-eric-brewer","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"8bf3f68c51344dee05049a7f9a91576984f4c6f69560641486f5be08aff13605","hash":"c90a68e84a01ea55e9e56b194ce6ad203cc59e19cd7b4687caf6d04852659c21"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"c90a68e84a01ea55e9e56b194ce6ad203cc59e19cd7b4687caf6d04852659c21"},"posted_at":"2026-07-15T04:20:33.005Z","created_at":"2026-07-15T04:20:33.005Z","updated_at":"2026-07-17T02:42:38.618Z","machine":{"shape":"article.machine/v1","slug":"thinker-eric-brewer","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-eric-brewer","json":"https://miscsubjects.com/api/articles/thinker-eric-brewer","bundle":"https://miscsubjects.com/api/articles/thinker-eric-brewer/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-eric-brewer/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-eric-brewer","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-eric-brewer\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-eric-brewer\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-eric-brewer/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-eric-brewer\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-eric-brewer | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-eric-brewer","json":"/api/articles/thinker-eric-brewer","markdown":"/api/articles/thinker-eric-brewer/bundle?format=markdown","skill":"/api/articles/thinker-eric-brewer/skill","topology":"/api/articles/thinker-eric-brewer/topology","versions":"/api/articles/thinker-eric-brewer/revisions","invocations":"/api/articles/thinker-eric-brewer/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-eric-brewer","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"05b379a8e3d9bcff9f055df41398956167113bd912ed61e26052dfd5b9931032","object":{"object_type":"article-object","identity":{"id":"article:thinker-eric-brewer","slug":"thinker-eric-brewer","title":"Eric Brewer — The CAP Theorem"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/thinker-eric-brewer","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-eric-brewer/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-eric-brewer\ndescription: Apply the Eric Brewer — The CAP Theorem article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Eric Brewer — The CAP Theorem\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-eric-brewer). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-eric-brewer.\n- Read claims and relationships at /api/articles/thinker-eric-brewer/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- hierarchy:nav -- Path: OIP https://miscsubjects.com/a/oip › Thinker Reference https://miscsubjects.com/a/oip-thinker-reference › Thinkers https://miscsubjects.com/a/oip-thinkers › Eric Brewer — The CAP Theorem Shelf: Thinkers · Travers\n\n## Representations\n\n- Human: /a/thinker-eric-brewer\n- JSON: /api/articles/thinker-eric-brewer\n- Relationships: /api/articles/thinker-eric-brewer/topology\n- History: /api/articles/thinker-eric-brewer/revisions\n"},"json":{"route":"/api/articles/thinker-eric-brewer","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-eric-brewer/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-eric-brewer","thinker","eric","brewer"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-eric-brewer/invocations?status=success","failure_events":"/api/articles/thinker-eric-brewer/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"thinker-eric-brewer","title":"Eric Brewer — The CAP Theorem","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Eric Brewer — The CAP Theorem**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Eric Brewer — The CAP Theorem\n\n## §SELF — thinker-eric-brewer\n\n**What this page is:** An explanation of a theorem that governs all distributed computer systems.\n**What it explains:** The CAP theorem and why distributed systems must choose between consistency and availability.\n**Why read it:** To understand why no distributed database can be fully consistent and fully available at the same time.\n\n### What the CAP Theorem Is\n\nThe CAP theorem was proposed by Eric Brewer (born 1965), a computer scientist at UC Berkeley and Google, in a keynote address in 2000. It was formally proved in 2002 by Seth Gilbert and Nancy Lynch of MIT.\n\nCAP names three properties of a distributed data store (a system where data is stored across multiple connected computers):\n\n- **Consistency (C):** Every read receives the most recent write. All nodes (individual computers in the system) see the same data at the same time.\n- **Availability (A):** Every request receives a non-error response. The system responds to every query, even if the data is not the most recent.\n- **Partition tolerance (P):** The system continues to operate despite network partitions — situations where messages between nodes are lost or delayed.\n\nThe theorem states: in a distributed data store, you can guarantee at most two of the three properties.\n\n### Why It Matters\n\nThe theorem matters because network partitions (P) are inevitable in real systems. Cables fail. Routers reboot. Data centers lose connectivity. If a partition occurs, the system must choose: either preserve consistency (C) by refusing some requests, or preserve availability (A) by serving possibly stale data.\n\nThis is not a technological limitation that better engineering will solve. It is a logical limit proved by the Gilbert-Lynch proof.\n\n### The Key Idea: The Trade-off\n\nIf the network partitions (P), you must choose between consistency (C) and availability (A). You cannot have both.\n\n- Choose CP: The system blocks writes until consistency is restored. Some requests fail. The system is consistent but not fully available.\n- Choose AP: The system accepts all writes and serves all reads. Some responses contain stale data. The system is available but not fully consistent.\n\nMost real-world distributed systems choose AP and handle consistency asynchronously (in the background). They accept that different nodes may see different data for a short period, and they resolve differences later.\n\n### What Brewer Got Right\n\n- Identified the three properties that matter in distributed systems design.\n- Showed that the choice between them is a logical necessity, not an engineering failure.\n- Forced system designers to be explicit about which properties they prioritize.\n\n### What Brewer Got Wrong or Left Unfinished\n\n- The theorem is often stated as \"pick two of three,\" which implies you could build a system that is CA (consistent and available) but not partition-tolerant. In practice, network partitions are unavoidable, so every real system must tolerate partitions. The actual choice is between CP and AP, not among all three pairs.\n- The theorem does not quantify the trade-off. It does not say how much consistency you lose for a given gain in availability.\n- Brewer later noted that the theorem describes a binary at partition time, but real systems operate on a spectrum between strong consistency and eventual consistency.\n\n### How It Connects to Other Ideas\n\n- **ACID vs. BASE:** ACID (Atomicity, Consistency, Isolation, Durability) describes the properties of traditional relational databases, which prioritize consistency. BASE (Basically Available, Soft state, Eventual consistency) describes the properties of many distributed databases, which prioritize availability. CAP explains why BASE exists.\n- **Consensus protocols (Paxos, Raft):** These algorithms achieve strong consistency in distributed systems by requiring a majority of nodes to agree before committing a write. They implement the CP choice. CAP explains why these protocols are necessary and why they add latency.\n\n### Sources\n\n- Brewer, Eric. \"Towards Robust Distributed Systems\" (keynote, PODC 2000).\n- Gilbert, Seth, and Nancy Lynch. \"Brewer's Conjecture and the Feasibility of Consistent, Available, Partition-Tolerant Web Services.\" *ACM SIGACT News* 33, no. 2 (2002): 51–59.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)\n- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)\n- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)\n- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)\n- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)\n- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)\n- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)\n- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/thinker-eric-brewer`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-eric-brewer`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Eric%20Brewer%20%E2%80%94%20The%20CAP%20Theorem`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-eric-brewer"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-eric-brewer/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Thinkers (oip-thinkers). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":33,"label":"Thinkers on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:33.005Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"8bf3f68c51344dee05049a7f9a91576984f4c6f69560641486f5be08aff13605"},{"ts":"2026-07-17T02:42:38.618Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-eric-brewer","response":"32 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"8bf3f68c51344dee05049a7f9a91576984f4c6f69560641486f5be08aff13605","hash":"c90a68e84a01ea55e9e56b194ce6ad203cc59e19cd7b4687caf6d04852659c21"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"c90a68e84a01ea55e9e56b194ce6ad203cc59e19cd7b4687caf6d04852659c21"},"posted_at":"2026-07-15T04:20:33.005Z","created_at":"2026-07-15T04:20:33.005Z","updated_at":"2026-07-17T02:42:38.618Z","machine":{"shape":"article.machine/v1","slug":"thinker-eric-brewer","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-eric-brewer","json":"https://miscsubjects.com/api/articles/thinker-eric-brewer","bundle":"https://miscsubjects.com/api/articles/thinker-eric-brewer/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/thinker-eric-brewer/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-eric-brewer","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-eric-brewer\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"thinker-eric-brewer\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-eric-brewer/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"thinker-eric-brewer\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-eric-brewer | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-eric-brewer","json":"/api/articles/thinker-eric-brewer","markdown":"/api/articles/thinker-eric-brewer/bundle?format=markdown","skill":"/api/articles/thinker-eric-brewer/skill","topology":"/api/articles/thinker-eric-brewer/topology","versions":"/api/articles/thinker-eric-brewer/revisions","invocations":"/api/articles/thinker-eric-brewer/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-eric-brewer","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"05b379a8e3d9bcff9f055df41398956167113bd912ed61e26052dfd5b9931032"}}}