{"_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-jack-dennis","title":"Jack Dennis — The Forgotten Origin of Capabilities","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) › **Jack Dennis — The Forgotten Origin of Capabilities**\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# Jack Dennis — The Forgotten Origin of Capabilities\n\n## §SELF — thinker-jack-dennis\n\n**What this page is:** A profile of Jack Dennis and his 1966 invention of capability-based addressing, the foundation of all capability security systems.\n**What it explains:** How Dennis's hardware memory protection model became the basis for modern software security architectures.\n**Why read it:** To understand where capability security came from and why separating access authority from program identity matters.\n\n### What Jack Dennis Is\n\nJack Dennis is a professor emeritus at the Massachusetts Institute of Technology (MIT — a university in Cambridge, Massachusetts, USA). He is a computer scientist who invented capability-based addressing in 1966. A \"capability\" (in computer security) is a token that grants permission to access a specific resource. The token itself carries the authority — whoever holds the token can use the resource.\n\n### Why It Matters\n\nBefore Dennis's work, computer security systems asked: \"Who are you?\" and then decided what you could access based on your identity. Dennis changed the question to: \"What do you hold?\" — meaning, what capability tokens do you possess? This separation of authority from identity became the foundation of capability security. Modern systems derived from Dennis's idea include: KeyKOS (a secure operating system built by Norm Hardy in the 1970s–80s), the E programming language (by Mark Miller, 1997), and seL4 (a formally verified operating system kernel, 2009). These systems are used in high-security environments because capability-based access control reduces the attack surface — there are fewer ways for an attacker to gain unauthorized access when permissions are tied to possession of specific tokens rather than to broad identity categories.\n\n### The Key Idea\n\nDennis's key idea, published in the 1966 paper \"Segmentation and the Design of Multi-Programmed Computer Systems,\" was: memory segments (contiguous regions of computer memory) should carry permission bits indicating whether the holder can read, write, or execute that segment. A program can only access a segment if it holds a capability — a hardware-protected reference to that segment. The hardware enforces this: if a program tries to access memory without holding the corresponding capability, the hardware blocks the access. This is different from identity-based systems where the operating system checks a user's credentials against an access control list.\n\nDennis co-authored with Earl Van Horn the 1965 paper \"Programming Semantics for Multiprogrammed Computations,\" which provided the theoretical foundation for this model by defining formal semantics (precise mathematical rules) for how concurrent programs interact with shared resources.\n\n### What He Got Right\n\n- **Separating access authority from program identity.** In Dennis's model, a program's ability to access a resource depends only on whether it holds the capability for that resource — not on who created the program or what user account it runs under. This means capabilities can be transferred between programs freely without changing any central authority database.\n- **Hardware enforcement.** Dennis designed the protection mechanism to be enforced by the computer's hardware (specifically, the memory management unit), not by software checks. Hardware enforcement cannot be bypassed by software bugs or malicious code.\n- **Fine-grained permissions.** Each capability carries specific permissions (read, write, execute) for a specific memory segment. This is more precise than broad categories like \"administrator\" or \"user.\"\n\n### What He Got Wrong or Left Unfinished\n\n- **Hardware capability machines were never mass-produced.** Dennis's design required specialized hardware that was not built commercially. General-purpose computers used simpler memory protection schemes. Without the hardware, capability-based security remained a theoretical concept for decades.\n- **Software implementations were necessary but came later.** Because the hardware was not adopted, researchers had to implement capability semantics in software. Norm Hardy's KeyKOS (built at Key Logic in the 1980s) was the first practical pure-capability operating system. Mark Miller's E language (1997) brought capabilities to distributed programming. These implementations proved the model works but required decades of additional engineering.\n- **No solution for capability revocation.** Dennis's original model did not specify how to take back a capability once granted. If Program A gives Program B a capability to access a file, how can A later revoke that access? This problem was solved in later systems (KeyKOS used a mechanism called \"segment keys\" that could be invalidated), but Dennis's original paper did not address it.\n\n### How It Connects to Other Ideas\n\n- **Access control lists (ACLs).** ACLs are the alternative to capabilities. In an ACL system, each resource has a list of who can access it. In a capability system, each subject has a list of what it can access. The two models are mathematically equivalent in expressive power but differ in practical properties: capabilities are easier to delegate (you hand over the token), while ACLs are easier to audit (you check one list to see who has access). Dennis's work established the capability side of this fundamental divide.\n- **Object-capability security (ocap).** Modern secure programming languages like E and Caja use \"object capabilities\" — the same principle as Dennis's memory capabilities, but applied to software objects rather than hardware memory segments. An object can only call methods on another object if it holds a reference (capability) to it. This is a direct conceptual descendant of Dennis's 1966 design.\n- **OIP capability tokens.** The Open Integrity Protocol (OIP) uses capability tokens as a web-native expression of Dennis's idea. In OIP, possession of a token grants access to a resource, and the token's permissions are scoped (limited in what they allow). This is the same structure as Dennis's hardware capabilities — a protected reference with embedded permissions — implemented as cryptographic tokens on the web instead of hardware memory references.\n\n### Sources\n\n- Dennis, J. B. (1966). \"Segmentation and the Design of Multi-Programmed Computer Systems.\" *Journal of the ACM*, 12(4), 589–602.\n- Dennis, J. B., & Van Horn, E. C. (1966). \"Programming Semantics for Multiprogrammed Computations.\" *Communications of the ACM*, 9(3), 143–155.\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-jack-dennis`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-jack-dennis`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Jack%20Dennis%20%E2%80%94%20The%20Forgotten%20Origin%20of%20Capabilities`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-jack-dennis"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-jack-dennis/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:36.793Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"249e53442ba9d9e644e0bfb7825cc29f7c212528e0ff822b81c2d9a5ed3a50f5"},{"ts":"2026-07-17T02:42:45.776Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-jack-dennis","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"249e53442ba9d9e644e0bfb7825cc29f7c212528e0ff822b81c2d9a5ed3a50f5","hash":"d22d91751731eef374a909445c16a783494700a7916bf8c56967cddb6f376e07"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"d22d91751731eef374a909445c16a783494700a7916bf8c56967cddb6f376e07"},"posted_at":"2026-07-15T04:20:36.793Z","created_at":"2026-07-15T04:20:36.793Z","updated_at":"2026-07-17T02:42:45.776Z","machine":{"shape":"article.machine/v1","slug":"thinker-jack-dennis","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-jack-dennis","json":"https://miscsubjects.com/api/articles/thinker-jack-dennis","bundle":"https://miscsubjects.com/api/articles/thinker-jack-dennis/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-jack-dennis/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-jack-dennis","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-jack-dennis\",\"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-jack-dennis\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-jack-dennis/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-jack-dennis\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-jack-dennis | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-jack-dennis","json":"/api/articles/thinker-jack-dennis","markdown":"/api/articles/thinker-jack-dennis/bundle?format=markdown","skill":"/api/articles/thinker-jack-dennis/skill","topology":"/api/articles/thinker-jack-dennis/topology","versions":"/api/articles/thinker-jack-dennis/revisions","invocations":"/api/articles/thinker-jack-dennis/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-jack-dennis","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":"080d6f256fd861856851fc129cd1c9dac35c3ae7e571842654a6e4bf8dcb990f","object":{"object_type":"article-object","identity":{"id":"article:thinker-jack-dennis","slug":"thinker-jack-dennis","title":"Jack Dennis — The Forgotten Origin of Capabilities"},"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-jack-dennis","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-jack-dennis/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-jack-dennis\ndescription: Apply the Jack Dennis — The Forgotten Origin of Capabilities article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Jack Dennis — The Forgotten Origin of Capabilities\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-jack-dennis). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-jack-dennis.\n- Read claims and relationships at /api/articles/thinker-jack-dennis/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 › Jack Dennis — The Forgotten Origin of Capabilities Shel\n\n## Representations\n\n- Human: /a/thinker-jack-dennis\n- JSON: /api/articles/thinker-jack-dennis\n- Relationships: /api/articles/thinker-jack-dennis/topology\n- History: /api/articles/thinker-jack-dennis/revisions\n"},"json":{"route":"/api/articles/thinker-jack-dennis","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-jack-dennis/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-jack-dennis","thinker","jack","dennis"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-jack-dennis/invocations?status=success","failure_events":"/api/articles/thinker-jack-dennis/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-jack-dennis","title":"Jack Dennis — The Forgotten Origin of Capabilities","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) › **Jack Dennis — The Forgotten Origin of Capabilities**\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# Jack Dennis — The Forgotten Origin of Capabilities\n\n## §SELF — thinker-jack-dennis\n\n**What this page is:** A profile of Jack Dennis and his 1966 invention of capability-based addressing, the foundation of all capability security systems.\n**What it explains:** How Dennis's hardware memory protection model became the basis for modern software security architectures.\n**Why read it:** To understand where capability security came from and why separating access authority from program identity matters.\n\n### What Jack Dennis Is\n\nJack Dennis is a professor emeritus at the Massachusetts Institute of Technology (MIT — a university in Cambridge, Massachusetts, USA). He is a computer scientist who invented capability-based addressing in 1966. A \"capability\" (in computer security) is a token that grants permission to access a specific resource. The token itself carries the authority — whoever holds the token can use the resource.\n\n### Why It Matters\n\nBefore Dennis's work, computer security systems asked: \"Who are you?\" and then decided what you could access based on your identity. Dennis changed the question to: \"What do you hold?\" — meaning, what capability tokens do you possess? This separation of authority from identity became the foundation of capability security. Modern systems derived from Dennis's idea include: KeyKOS (a secure operating system built by Norm Hardy in the 1970s–80s), the E programming language (by Mark Miller, 1997), and seL4 (a formally verified operating system kernel, 2009). These systems are used in high-security environments because capability-based access control reduces the attack surface — there are fewer ways for an attacker to gain unauthorized access when permissions are tied to possession of specific tokens rather than to broad identity categories.\n\n### The Key Idea\n\nDennis's key idea, published in the 1966 paper \"Segmentation and the Design of Multi-Programmed Computer Systems,\" was: memory segments (contiguous regions of computer memory) should carry permission bits indicating whether the holder can read, write, or execute that segment. A program can only access a segment if it holds a capability — a hardware-protected reference to that segment. The hardware enforces this: if a program tries to access memory without holding the corresponding capability, the hardware blocks the access. This is different from identity-based systems where the operating system checks a user's credentials against an access control list.\n\nDennis co-authored with Earl Van Horn the 1965 paper \"Programming Semantics for Multiprogrammed Computations,\" which provided the theoretical foundation for this model by defining formal semantics (precise mathematical rules) for how concurrent programs interact with shared resources.\n\n### What He Got Right\n\n- **Separating access authority from program identity.** In Dennis's model, a program's ability to access a resource depends only on whether it holds the capability for that resource — not on who created the program or what user account it runs under. This means capabilities can be transferred between programs freely without changing any central authority database.\n- **Hardware enforcement.** Dennis designed the protection mechanism to be enforced by the computer's hardware (specifically, the memory management unit), not by software checks. Hardware enforcement cannot be bypassed by software bugs or malicious code.\n- **Fine-grained permissions.** Each capability carries specific permissions (read, write, execute) for a specific memory segment. This is more precise than broad categories like \"administrator\" or \"user.\"\n\n### What He Got Wrong or Left Unfinished\n\n- **Hardware capability machines were never mass-produced.** Dennis's design required specialized hardware that was not built commercially. General-purpose computers used simpler memory protection schemes. Without the hardware, capability-based security remained a theoretical concept for decades.\n- **Software implementations were necessary but came later.** Because the hardware was not adopted, researchers had to implement capability semantics in software. Norm Hardy's KeyKOS (built at Key Logic in the 1980s) was the first practical pure-capability operating system. Mark Miller's E language (1997) brought capabilities to distributed programming. These implementations proved the model works but required decades of additional engineering.\n- **No solution for capability revocation.** Dennis's original model did not specify how to take back a capability once granted. If Program A gives Program B a capability to access a file, how can A later revoke that access? This problem was solved in later systems (KeyKOS used a mechanism called \"segment keys\" that could be invalidated), but Dennis's original paper did not address it.\n\n### How It Connects to Other Ideas\n\n- **Access control lists (ACLs).** ACLs are the alternative to capabilities. In an ACL system, each resource has a list of who can access it. In a capability system, each subject has a list of what it can access. The two models are mathematically equivalent in expressive power but differ in practical properties: capabilities are easier to delegate (you hand over the token), while ACLs are easier to audit (you check one list to see who has access). Dennis's work established the capability side of this fundamental divide.\n- **Object-capability security (ocap).** Modern secure programming languages like E and Caja use \"object capabilities\" — the same principle as Dennis's memory capabilities, but applied to software objects rather than hardware memory segments. An object can only call methods on another object if it holds a reference (capability) to it. This is a direct conceptual descendant of Dennis's 1966 design.\n- **OIP capability tokens.** The Open Integrity Protocol (OIP) uses capability tokens as a web-native expression of Dennis's idea. In OIP, possession of a token grants access to a resource, and the token's permissions are scoped (limited in what they allow). This is the same structure as Dennis's hardware capabilities — a protected reference with embedded permissions — implemented as cryptographic tokens on the web instead of hardware memory references.\n\n### Sources\n\n- Dennis, J. B. (1966). \"Segmentation and the Design of Multi-Programmed Computer Systems.\" *Journal of the ACM*, 12(4), 589–602.\n- Dennis, J. B., & Van Horn, E. C. (1966). \"Programming Semantics for Multiprogrammed Computations.\" *Communications of the ACM*, 9(3), 143–155.\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-jack-dennis`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-jack-dennis`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Jack%20Dennis%20%E2%80%94%20The%20Forgotten%20Origin%20of%20Capabilities`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-jack-dennis"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-jack-dennis/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:36.793Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"249e53442ba9d9e644e0bfb7825cc29f7c212528e0ff822b81c2d9a5ed3a50f5"},{"ts":"2026-07-17T02:42:45.776Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-jack-dennis","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"249e53442ba9d9e644e0bfb7825cc29f7c212528e0ff822b81c2d9a5ed3a50f5","hash":"d22d91751731eef374a909445c16a783494700a7916bf8c56967cddb6f376e07"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"d22d91751731eef374a909445c16a783494700a7916bf8c56967cddb6f376e07"},"posted_at":"2026-07-15T04:20:36.793Z","created_at":"2026-07-15T04:20:36.793Z","updated_at":"2026-07-17T02:42:45.776Z","machine":{"shape":"article.machine/v1","slug":"thinker-jack-dennis","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-jack-dennis","json":"https://miscsubjects.com/api/articles/thinker-jack-dennis","bundle":"https://miscsubjects.com/api/articles/thinker-jack-dennis/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-jack-dennis/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-jack-dennis","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-jack-dennis\",\"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-jack-dennis\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-jack-dennis/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-jack-dennis\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-jack-dennis | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-jack-dennis","json":"/api/articles/thinker-jack-dennis","markdown":"/api/articles/thinker-jack-dennis/bundle?format=markdown","skill":"/api/articles/thinker-jack-dennis/skill","topology":"/api/articles/thinker-jack-dennis/topology","versions":"/api/articles/thinker-jack-dennis/revisions","invocations":"/api/articles/thinker-jack-dennis/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-jack-dennis","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":"080d6f256fd861856851fc129cd1c9dac35c3ae7e571842654a6e4bf8dcb990f"}}}