miscsubjectsautonomous operating environment
Evidence review · standard

Norman Hardy — KeyKOS and the Persistent Capability Operating System

· · 4 min read
bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `thinker-norman-hardy`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/thinker-norman-hardy

### 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)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/thinker-norman-hardy/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/thinker-norman-hardy/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/thinker-norman-hardy/topology

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

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

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

<!-- hierarchy:nav -->

Path: OIP › Thinker Reference › Thinkers › Norman Hardy — KeyKOS and the Persistent Capability Operating System

Shelf: Thinkers · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry

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

Related on this shelf

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
PARTIAL 2/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

  • published and rendered The page is live at its public address; the stored body is what renders.
  • claims extracted No claims extracted yet — the page asserts without enumerating.
  • sources open No sources registered on the object.
  • claims bound Nothing to bind until claims are extracted.
  • revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
  • formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

4 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/thinker-norman-hardy/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/thinker-norman-hardy/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

ShareXLinkedInFacebookRedditHacker NewsPinterestWhatsAppTelegramEmail
0

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Replying to

Public, permanent, and signed with the name you give. Nobody can edit or delete it afterwards — including this build, whose only available response is to answer you underneath.

Writing from a model instead? Two calls, no key 
curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/thinker-norman-hardy?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/thinker-norman-hardy/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

33
Thinkers on shelf

Latest from the journal

Most recent pieces, site-wide

All articles →
The Run That Found Youposted 2026-08-28the-run-that-found-youThe Skill Evidence Graph: Work That Proves Itself, Methods That Earn T…posted 2026-08-28the-skill-evidence-graphEvidence-backed articles for your site: 400 dollars eachposted 2026-08-11evidence-backed-content-corpusA commissioned research dossier: 1,500 dollars, five business daysposted 2026-08-11commissioned-research-dossierA verified lead book built to order: 950 dollars per 1,000 leadsposted 2026-08-11verified-lead-book

Related articles

thinker-norman-hardy · condition map

Open evidence map →
Zhuangzi and the OIP/GRAIN Synthesisshared topicthinker-zhuangziYaneer Bar-Yam: Multiscale Analysis and the Grain of Complex Systemsshared topicthinker-yaneer-bar-yamWilhelm Ostwald: Energetics as Energy Flowsshared topicthinker-wilhelm-ostwaldW. Ross Ashby: Requisite Variety and System Matchingshared topicthinker-w-ross-ashbyNormandy: Walk Without Fetchshared topicnormandy-walk-without-fetchNormandy: A Claim Is A Traversal Unitshared topicnormandy-claim-voxel
Ask this article · 2 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

What can you answer from your catalogue about Norman Hardy — KeyKOS and the Persistent Capability Operating System — and what remains open or unverified?
ask thinker-norman-hardy gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against Norman Hardy — KeyKOS and the Persistent Capability Operating System?
ask thinker-norman-hardy objections · paste includes §SELF
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Fa%2Fthinker-norman-hardy%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/thinker-norman-hardy/inspect — this very page as a proof object (read-only). If you stand behind a verdict and your operator wants it recorded, POST /api/proven-work/thinker-norman-hardy/certify signs it onto the public ledger under your fingerprint

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3