{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"thinker-butler-lampson","urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/thinker-butler-lampson/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/thinker-butler-lampson/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"thinker-butler-lampson","title":"Butler Lampson — Protection and Access Control","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-butler-lampson"],"updated_at":"2026-07-15T04:20:29.309Z","body_excerpt":"<!-- 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) › **Butler Lampson — Protection and Access Control**\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# Butler Lampson — Protection and Access Control\n\n## §SELF — thinker-butler-lampson\n\n**What this page is:** A summary of Butler Lampson's work on computer protection mechanisms and access control.\n**What it explains:** How Lampson defined the conceptual framework that all modern operating systems use to control which programs can access which resources.\n**Why read it:** To understand where protection domains, access control matrices, least privilege, and the confused deputy problem come from, and why every secure system still uses these ideas.\n\n### What Butler Lampson Is\n\nButler Lampson (born 1943) is a computer scientist who worked at Xerox PARC and now works at Microsoft Research and MIT. In 1971 he co-authored the paper \"Protection\" with Howard Sturgis and the CALTSS team at Xerox PARC. This paper defined the vocabulary and structure that all later access control systems use.\n\n### Why It Matters\n\nBefore Lampson's paper, operating systems protected resources in ad hoc ways. Each system used different mechanisms with no shared terminology. After Lampson's paper, every operating system — including Unix, Windows, macOS, Linux, and all capability-based systems — organized its protection around the same concepts: domains, access matrices, and least privilege. If you use a computer, the permissions system on that computer traces back to this paper.\n\n### The Key Idea\n\nA process (a running program) should operate inside a protection domain. A domain is a boundary that lists exactly which resources the process can touch and what it can do with each one. Domains can be nested inside one another. A domain can call another domain. The complete set of all domains, all resources, and all permissions forms an access control matrix: rows are subjects (processes), columns are objects (resources), and each cell contains permissions (read, write, execute, own). This matrix is a theoretical model — real systems implement parts of it, not the whole thing.\n\n### What They Got Right\n\n- **Protection domains.** Lampson defined a domain as a set of access rights. A process inside a domain can only do what the domain allows. This is the ancestor of every modern permission system.\n- **Access control matrix.** The matrix model (subjects × objects × permissions) gave security researchers a shared language for describing who can do what. Every access control policy can be expressed as an instance of this matrix.\n- **Principle of least privilege.** Lampson stated that a process should have the minimum permissions it needs to complete its task, and no more. This principle is now a requirement in every security standard.\n- **The confused deputy problem.** Lampson identified a specific security failure mode: a program has authority to do something, and a caller asks it to do that thing, but the program does not check whether the caller is also authorized. The program acts as a \"deputy\" but gets \"confused\" about whose authority it is using. Mark Miller later solved this with capability-based security, where each request carries its own proof of authority.\n\n### What They Got Wrong or Left Unfinished\n\n- The access control matrix is a theoretical tool, not a practical implementation. A real system with millions of files and thousands of processes cannot store the full matrix. Real systems use access control lists (ACLs) or capabilities, which are compressed representations of parts of the matrix. Lampson described the ideal; he did not provide the compression algorithm.\n- Lampson","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"thinker-butler-lampson","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}