## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `thinker-norman-hardy`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/thinker-norman-hardy/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/thinker-norman-hardy/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/thinker-norman-hardy/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/thinker-norman-hardy/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/thinker-norman-hardy/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/thinker-norman-hardy/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## Article
- **slug:** `thinker-norman-hardy`
- **title:** Norman Hardy — KeyKOS and the Persistent Capability Operating System
- **url:** https://miscsubjects.com/a/thinker-norman-hardy
- **register:** standard
- **updated:** 2026-07-15T04:20:42.979Z
- **tags:** oip, kimi-import, self-explaining, voxel, thinkers, thinker-norman-hardy

## Body

<!-- 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 Operating System**
>
> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready
> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)

# Norman Hardy — KeyKOS and the Persistent Capability Operating System

## §SELF — thinker-norman-hardy

**What this page is:** A profile of the computer scientist who built the first commercially deployed capability-based operating system.
**What it explains:** Norman Hardy's KeyKOS system and its core innovations in persistent object-capability architecture.
**Why read it:** To understand how capability-based security works in practice and why it matters for modern system design.

### What Norman Hardy Did

Norman 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.

A 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.

### Why It Matters

Before 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.

### The Key Idea

KeyKOS is a persistent object-capability operating system. Every object in the system is accessed through a capability. There are four defining properties:

1. **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.

2. **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.

3. **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.

4. **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.

### What He Got Right

- Proved that a capability-based operating system can be practical and commercially viable.
- Demonstrated that persistence at the OS level is achievable: checkpointing the entire system state to disk eliminates the distinction between memory and storage.
- Showed that removing the root account and ACLs does not make administration harder — it makes security violations harder.
- Invented the factory pattern for capability creation, which is still used in capability-secure systems today.

### What He Got Wrong or Left Unfinished

- KeyKOS required specialized hardware (the IBM System/38), limiting adoption.
- Network-transparent capabilities were not fully solved: passing capabilities across machines requires cryptographic proof of unforgeability, which KeyKOS did not implement.
- The checkpointing system caused performance overhead that was acceptable in the 1980s but would not scale to modern workloads without optimization.
- No formal verification: KeyKOS was not mathematically proven correct, though it was extensively tested.

### How It Connects to Other Ideas

**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.

**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.

**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.

**Persistence model.** OIP's append-only ledger serves the same function as KeyKOS checkpoints: it is a persistent, tamper-evident record of system state.

### Sources

- Hardy, Norman, et al. "KeyKOS: A Commercially Successful, Capability-Based, Persistent Operating System." *Proceedings of the 12th ACM Symposium on Operating Systems Principles*, 1989.
- Shapiro, Jonathan S., et al. "EROS: A Fast Capability System." *Proceedings of the 17th ACM Symposium on Operating Systems Principles*, 1999.

---

## Up the tree

- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry
- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map
- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf
- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels
- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)

## Related on this shelf

- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)
- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)
- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)
- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)
- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)
- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)
- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)
- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)

## Machine surfaces

- Public page: `https://miscsubjects.com/a/thinker-norman-hardy`
- JSON article: `https://miscsubjects.com/api/articles/thinker-norman-hardy`
- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Norman%20Hardy%20%E2%80%94%20KeyKOS%20and%20the%20Persistent%20Capability%20Operating%20System`


## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/thinker-norman-hardy/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (1 model passes)
- chain valid: yes · head: `2c030d385a357ce9`

- write · kimi-agent-import · 2026-07-15T04:20 · hash `2c030d385a35`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/thinker-norman-hardy/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/thinker-norman-hardy/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"thinker-norman-hardy","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest thinker-norman-hardy|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim thinker-norman-hardy|tier|assertion`
- **iMessage ask:** `thinker-norman-hardy|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `thinker-norman-hardy`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/thinker-norman-hardy/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/thinker-norman-hardy/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*