{"_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-norman-hardy","title":"Norman Hardy — KeyKOS and the Persistent Capability Operating System","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) › **Norman Hardy — KeyKOS and the Persistent Capability Operating System**\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# Norman Hardy — KeyKOS and the Persistent Capability Operating System\n\n## §SELF — thinker-norman-hardy\n\n**What this page is:** A profile of the computer scientist who built the first commercially deployed capability-based operating system.\n**What it explains:** Norman Hardy's KeyKOS system and its core innovations in persistent object-capability architecture.\n**Why read it:** To understand how capability-based security works in practice and why it matters for modern system design.\n\n### What Norman Hardy Did\n\nNorman Hardy (born 1933) is a computer scientist who led the development of KeyKOS at Key Logic in the 1980s. KeyKOS was the first capability-based operating system deployed commercially.\n\nA capability (in operating systems) is an unforgeable reference that carries authority. It is a token proving that the holder has permission to access a specific object (a file, a process, a device, or any system resource). Capabilities are first-class objects: they can be passed between processes, stored in files, and sent across networks.\n\n### Why It Matters\n\nBefore KeyKOS, operating systems used access control lists (ACLs) — lists attached to resources specifying which users could access them. ACLs have a problem: they grant authority based on identity, not on need. A process running with root or administrator privileges can access everything, even when it only needs one file. This is the confused deputy problem: a program (the deputy) acts on behalf of a user and uses its own authority instead of authority delegated for a specific task. KeyKOS solved this by making capabilities the only access mechanism.\n\n### The Key Idea\n\nKeyKOS is a persistent object-capability operating system. Every object in the system is accessed through a capability. There are four defining properties:\n\n1. **Every object is persistent.** The system's state is checkpointed to disk at regular intervals. You can turn off the machine and turn it back on, and everything resumes exactly where it was. Processes, files, and open connections are preserved.\n\n2. **Capabilities are the only access mechanism.** There are no passwords, no access control lists, and no root account. If you do not hold a capability for an object, you cannot access it. The capability itself is the proof of permission.\n\n3. **The confused deputy problem is impossible.** Authority is in the capability, not in the process. A process can only use the capabilities it holds. It cannot escalate its own authority.\n\n4. **Factory pattern.** Objects are created by factory objects — pre-configured templates that produce new objects with a specific set of capabilities. A factory object creates a new object and hands back a capability to it. The creator controls what the new object can do by deciding which capabilities the factory includes.\n\n### What He Got Right\n\n- Proved that a capability-based operating system can be practical and commercially viable.\n- Demonstrated that persistence at the OS level is achievable: checkpointing the entire system state to disk eliminates the distinction between memory and storage.\n- Showed that removing the root account and ACLs does not make administration harder — it makes security violations harder.\n- Invented the factory pattern for capability creation, which is still used in capability-secure systems today.\n\n### What He Got Wrong or Left Unfinished\n\n- KeyKOS required specialized hardware (the IBM System/38), limiting adoption.\n- Network-transparent capabilities were not fully solved: passing capabilities across machines requires cryptographic proof of unforgeability, which KeyKOS did not implement.\n- The checkpointing system caused performance overhead that was acceptable in the 1980s but would not scale to modern workloads without optimization.\n- No formal verification: KeyKOS was not mathematically proven correct, though it was extensively tested.\n\n### How It Connects to Other Ideas\n\n**EROS and CapROS.** EROS (Extremely Reliable Operating System), developed by Jonathan Shapiro in the 1990s, was a direct successor to KeyKOS. EROS added formal verification — mathematical proofs that the system's security properties hold. CapROS continued this lineage.\n\n**Capability-based security in modern systems.** The seL4 microkernel, Fuchsia's Zircon kernel, and the Object Invocation Protocol (OIP) all use capability-based access control derived from the KeyKOS model.\n\n**Factory pattern in OIP.** OIP's directory rows function as object factories: each row describes an object and the capabilities needed to invoke it. The OIP capability token follows the KeyKOS model directly — it is unforgeable, scoped to specific objects, and delegable.\n\n**Persistence model.** OIP's append-only ledger serves the same function as KeyKOS checkpoints: it is a persistent, tamper-evident record of system state.\n\n### Sources\n\n- Hardy, Norman, et al. \"KeyKOS: A Commercially Successful, Capability-Based, Persistent Operating System.\" *Proceedings of the 12th ACM Symposium on Operating Systems Principles*, 1989.\n- Shapiro, Jonathan S., et al. \"EROS: A Fast Capability System.\" *Proceedings of the 17th ACM Symposium on Operating Systems Principles*, 1999.\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-norman-hardy`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-norman-hardy`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Norman%20Hardy%20%E2%80%94%20KeyKOS%20and%20the%20Persistent%20Capability%20Operating%20System`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-norman-hardy"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-norman-hardy/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:42.979Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"2c030d385a357ce9ca0600a1ad1910fbcd7b91213c1c02915b58e288d38e935f"},{"ts":"2026-07-17T02:42:55.006Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-norman-hardy","response":"34 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"2c030d385a357ce9ca0600a1ad1910fbcd7b91213c1c02915b58e288d38e935f","hash":"0f9f61035246368d121b728a6106bc25bdb503f5ce86d57e525e4aa736f8dcc2"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"0f9f61035246368d121b728a6106bc25bdb503f5ce86d57e525e4aa736f8dcc2"},"posted_at":"2026-07-15T04:20:42.979Z","created_at":"2026-07-15T04:20:42.979Z","updated_at":"2026-07-17T02:42:55.006Z","machine":{"shape":"article.machine/v1","slug":"thinker-norman-hardy","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-norman-hardy","json":"https://miscsubjects.com/api/articles/thinker-norman-hardy","bundle":"https://miscsubjects.com/api/articles/thinker-norman-hardy/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-norman-hardy/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-norman-hardy","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-norman-hardy\",\"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-norman-hardy\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-norman-hardy/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-norman-hardy\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-norman-hardy | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-norman-hardy","json":"/api/articles/thinker-norman-hardy","markdown":"/api/articles/thinker-norman-hardy/bundle?format=markdown","skill":"/api/articles/thinker-norman-hardy/skill","topology":"/api/articles/thinker-norman-hardy/topology","versions":"/api/articles/thinker-norman-hardy/revisions","invocations":"/api/articles/thinker-norman-hardy/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-norman-hardy","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":"b5d2b58c3c1511945d92e823b7bf5ec53c655a9d1ecbcf9f04f142194c30d87c","object":{"object_type":"article-object","identity":{"id":"article:thinker-norman-hardy","slug":"thinker-norman-hardy","title":"Norman Hardy — KeyKOS and the Persistent Capability Operating System"},"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-norman-hardy","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-norman-hardy/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-norman-hardy\ndescription: Apply the Norman Hardy — KeyKOS and the Persistent Capability Operating System article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Norman Hardy — KeyKOS and the Persistent Capability Operating System\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-norman-hardy). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-norman-hardy.\n- Read claims and relationships at /api/articles/thinker-norman-hardy/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 › Norman Hardy — KeyKOS and the Persistent Capability Ope\n\n## Representations\n\n- Human: /a/thinker-norman-hardy\n- JSON: /api/articles/thinker-norman-hardy\n- Relationships: /api/articles/thinker-norman-hardy/topology\n- History: /api/articles/thinker-norman-hardy/revisions\n"},"json":{"route":"/api/articles/thinker-norman-hardy","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-norman-hardy/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-norman-hardy","thinker","norman","hardy"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-norman-hardy/invocations?status=success","failure_events":"/api/articles/thinker-norman-hardy/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-norman-hardy","title":"Norman Hardy — KeyKOS and the Persistent Capability Operating System","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) › **Norman Hardy — KeyKOS and the Persistent Capability Operating System**\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# Norman Hardy — KeyKOS and the Persistent Capability Operating System\n\n## §SELF — thinker-norman-hardy\n\n**What this page is:** A profile of the computer scientist who built the first commercially deployed capability-based operating system.\n**What it explains:** Norman Hardy's KeyKOS system and its core innovations in persistent object-capability architecture.\n**Why read it:** To understand how capability-based security works in practice and why it matters for modern system design.\n\n### What Norman Hardy Did\n\nNorman Hardy (born 1933) is a computer scientist who led the development of KeyKOS at Key Logic in the 1980s. KeyKOS was the first capability-based operating system deployed commercially.\n\nA capability (in operating systems) is an unforgeable reference that carries authority. It is a token proving that the holder has permission to access a specific object (a file, a process, a device, or any system resource). Capabilities are first-class objects: they can be passed between processes, stored in files, and sent across networks.\n\n### Why It Matters\n\nBefore KeyKOS, operating systems used access control lists (ACLs) — lists attached to resources specifying which users could access them. ACLs have a problem: they grant authority based on identity, not on need. A process running with root or administrator privileges can access everything, even when it only needs one file. This is the confused deputy problem: a program (the deputy) acts on behalf of a user and uses its own authority instead of authority delegated for a specific task. KeyKOS solved this by making capabilities the only access mechanism.\n\n### The Key Idea\n\nKeyKOS is a persistent object-capability operating system. Every object in the system is accessed through a capability. There are four defining properties:\n\n1. **Every object is persistent.** The system's state is checkpointed to disk at regular intervals. You can turn off the machine and turn it back on, and everything resumes exactly where it was. Processes, files, and open connections are preserved.\n\n2. **Capabilities are the only access mechanism.** There are no passwords, no access control lists, and no root account. If you do not hold a capability for an object, you cannot access it. The capability itself is the proof of permission.\n\n3. **The confused deputy problem is impossible.** Authority is in the capability, not in the process. A process can only use the capabilities it holds. It cannot escalate its own authority.\n\n4. **Factory pattern.** Objects are created by factory objects — pre-configured templates that produce new objects with a specific set of capabilities. A factory object creates a new object and hands back a capability to it. The creator controls what the new object can do by deciding which capabilities the factory includes.\n\n### What He Got Right\n\n- Proved that a capability-based operating system can be practical and commercially viable.\n- Demonstrated that persistence at the OS level is achievable: checkpointing the entire system state to disk eliminates the distinction between memory and storage.\n- Showed that removing the root account and ACLs does not make administration harder — it makes security violations harder.\n- Invented the factory pattern for capability creation, which is still used in capability-secure systems today.\n\n### What He Got Wrong or Left Unfinished\n\n- KeyKOS required specialized hardware (the IBM System/38), limiting adoption.\n- Network-transparent capabilities were not fully solved: passing capabilities across machines requires cryptographic proof of unforgeability, which KeyKOS did not implement.\n- The checkpointing system caused performance overhead that was acceptable in the 1980s but would not scale to modern workloads without optimization.\n- No formal verification: KeyKOS was not mathematically proven correct, though it was extensively tested.\n\n### How It Connects to Other Ideas\n\n**EROS and CapROS.** EROS (Extremely Reliable Operating System), developed by Jonathan Shapiro in the 1990s, was a direct successor to KeyKOS. EROS added formal verification — mathematical proofs that the system's security properties hold. CapROS continued this lineage.\n\n**Capability-based security in modern systems.** The seL4 microkernel, Fuchsia's Zircon kernel, and the Object Invocation Protocol (OIP) all use capability-based access control derived from the KeyKOS model.\n\n**Factory pattern in OIP.** OIP's directory rows function as object factories: each row describes an object and the capabilities needed to invoke it. The OIP capability token follows the KeyKOS model directly — it is unforgeable, scoped to specific objects, and delegable.\n\n**Persistence model.** OIP's append-only ledger serves the same function as KeyKOS checkpoints: it is a persistent, tamper-evident record of system state.\n\n### Sources\n\n- Hardy, Norman, et al. \"KeyKOS: A Commercially Successful, Capability-Based, Persistent Operating System.\" *Proceedings of the 12th ACM Symposium on Operating Systems Principles*, 1989.\n- Shapiro, Jonathan S., et al. \"EROS: A Fast Capability System.\" *Proceedings of the 17th ACM Symposium on Operating Systems Principles*, 1999.\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-norman-hardy`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-norman-hardy`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Norman%20Hardy%20%E2%80%94%20KeyKOS%20and%20the%20Persistent%20Capability%20Operating%20System`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-norman-hardy"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-norman-hardy/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:42.979Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"2c030d385a357ce9ca0600a1ad1910fbcd7b91213c1c02915b58e288d38e935f"},{"ts":"2026-07-17T02:42:55.006Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-norman-hardy","response":"34 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"2c030d385a357ce9ca0600a1ad1910fbcd7b91213c1c02915b58e288d38e935f","hash":"0f9f61035246368d121b728a6106bc25bdb503f5ce86d57e525e4aa736f8dcc2"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"0f9f61035246368d121b728a6106bc25bdb503f5ce86d57e525e4aa736f8dcc2"},"posted_at":"2026-07-15T04:20:42.979Z","created_at":"2026-07-15T04:20:42.979Z","updated_at":"2026-07-17T02:42:55.006Z","machine":{"shape":"article.machine/v1","slug":"thinker-norman-hardy","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-norman-hardy","json":"https://miscsubjects.com/api/articles/thinker-norman-hardy","bundle":"https://miscsubjects.com/api/articles/thinker-norman-hardy/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-norman-hardy/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-norman-hardy","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-norman-hardy\",\"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-norman-hardy\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-norman-hardy/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-norman-hardy\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-norman-hardy | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-norman-hardy","json":"/api/articles/thinker-norman-hardy","markdown":"/api/articles/thinker-norman-hardy/bundle?format=markdown","skill":"/api/articles/thinker-norman-hardy/skill","topology":"/api/articles/thinker-norman-hardy/topology","versions":"/api/articles/thinker-norman-hardy/revisions","invocations":"/api/articles/thinker-norman-hardy/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-norman-hardy","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":"b5d2b58c3c1511945d92e823b7bf5ec53c655a9d1ecbcf9f04f142194c30d87c"}}}