{"_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-saltzer-schroeder","title":"Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems","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) › **Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems**\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# Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems\n\n## §SELF — thinker-saltzer-schroeder\n\n**What this page is:** A summary of the eight security design principles defined by Saltzer and Schroeder in their 1974 paper.\n**What it explains:** How to design a computer system so that it protects information by default, and why eight specific principles make the difference between a secure system and an insecure one.\n**Why read it:** To understand the rules that every secure system follows, and to see how a single paper written in 1974 still defines security architecture today.\n\n### What Saltzer and Schroeder Is\n\nJerome Saltzer (born 1939) is a computer scientist at MIT. Michael Schroeder is a computer scientist at Xerox PARC and later at DEC Systems Research Center. In 1974 they published \"The Protection of Information in Computer Systems\" in the *Proceedings of the IEEE*. This paper is the most cited publication in the field of computer security. It lists eight design principles for building systems that protect information from unauthorized access.\n\n### Why It Matters\n\nEvery security breach that makes the news happens because one or more of these eight principles was violated. When a system defaults to allowing access, that is a violation of fail-safe defaults. When a system checks permission once and never again, that is a violation of complete mediation. When a system's security depends on keeping its source code secret, that is a violation of open design. Saltzer and Schroeder did not invent these principles out of nothing — they extracted them from studying which systems failed and which systems survived. Their paper is a checklist. Violate it at your own risk.\n\n### The Key Idea\n\nSecurity is not a feature you add to a system after you build it. Security is a property of how the system is designed. Saltzer and Schroeder distilled this into eight principles:\n\n1. **Economy of mechanism.** The security mechanism should be as simple and small as possible. A small mechanism has fewer bugs, is easier to verify, and is easier to understand. Complexity is the enemy of security.\n2. **Fail-safe defaults.** The default state of the system should be \"no access.\" Access should be granted only by explicit permission. If the permission check fails or is missing, the result should be denial, not access.\n3. **Complete mediation.** Every access to every resource must be checked for authorization. Not just the first access. Every access. If a program checks permission on Monday and never checks again, an attacker who gains access on Tuesday wins.\n4. **Open design.** The security of the system should not depend on the secrecy of its design or implementation. The design should be public. The keys should be secret, not the mechanism. This is the opposite of \"security through obscurity.\"\n5. **Separation of privilege.** Access to a sensitive resource should require more than one condition. For example, a bank vault should require two keys held by different people. A single compromised credential should not be enough.\n6. **Least privilege.** Every program and every user should operate using the minimum permissions needed to complete their task. No more. If a program is compromised while holding excess permissions, the attacker gets those excess permissions too.\n7. **Least common mechanism.** Minimize the amount of mechanism shared by different users. Shared mechanisms are single points of failure. If one user's action can affect a shared resource, that shared resource becomes a channel for attack.\n8. **Psychological acceptability.** Security mechanisms must be usable. If a security mechanism is too hard to use, people will bypass it. A perfect security system that nobody uses is an insecure system.\n\n### What They Got Right\n\n- They identified that security is a design problem, not an implementation problem. You cannot bolt security onto a badly designed system.\n- They proved that simplicity beats complexity. Economy of mechanism is the first principle for a reason.\n- They defined fail-safe defaults, which means the system is secure when it fails. This inverts the usual engineering assumption that a failure should produce a harmless output. In security, a failure should produce a denial.\n- They separated the secret (the key) from the mechanism (the design). Open design means the security community can audit the system. A secret mechanism cannot be audited.\n- They recognized that human behavior matters. Psychological acceptability acknowledges that security is a human problem as much as a technical one.\n\n### What They Got Wrong or Left Unfinished\n\n- The paper predates distributed systems, the internet, and cloud computing. The principles apply to distributed systems, but Saltzer and Schroeder did not address the specific problems of authentication across networks, key distribution, or Byzantine failures.\n- They did not address capabilities or object-capability security. Their model assumes an access control matrix or ACL model. Capability-based systems implement these principles differently — for example, least privilege in a capability system means holding only the capabilities you need, not having a broad identity with restricted permissions.\n- They did not provide a method for measuring or verifying whether a system follows the principles. The principles are guidelines, not formal specifications.\n\n### How It Connects to Other Ideas\n\n- **OIP (Open Invocation Protocol).** OIP implements all eight principles: (1) Economy: one dispatch door endpoint. (2) Fail-safe: default is no access; tokens grant explicitly. (3) Complete mediation: every invocation checks the token. (4) Open design: the OIP specification is public. (5) Separation: the owner gate requires both a valid token AND owner approval. (6) Least privilege: tokens are scoped to specific objects. (7) Least common: tenant isolation prevents shared mechanisms between users. (8) Psychological: Tap & Go requires one copy action.\n- **Butler Lampson's \"Protection.\"** Lampson (1971) provided the theoretical model of access control matrices and protection domains. Saltzer and Schroeder (1974) extracted the design principles that make those models work in practice. The two papers are complementary: Lampson described the what; Saltzer and Schroeder described the how.\n- **Capability-based security.** Capability systems implement least privilege by construction — a process can only use the capabilities it holds. Saltzer and Schroeder's principles are independent of any specific mechanism, but capability-based security is one of the cleanest implementations of them.\n\n### Sources\n\n- Saltzer, J. H. and Schroeder, M. D. \"The Protection of Information in Computer Systems.\" *Proceedings of the IEEE*, Vol. 63, No. 9, pp. 1278–1308, September 1974.\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-saltzer-schroeder`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-saltzer-schroeder`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Jerome%20Saltzer%20and%20Michael%20Schroeder%20%E2%80%94%20The%20Protection%20of%20Information%20in%20Computer%20Systems`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-saltzer-schroeder"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-saltzer-schroeder/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:46.587Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"f51632ab71d703c1d34d7c616feae2c081f8fcdc281e8fccc39146439292a63e"},{"ts":"2026-07-17T02:42:59.280Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-saltzer-schroeder","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"f51632ab71d703c1d34d7c616feae2c081f8fcdc281e8fccc39146439292a63e","hash":"dbdbff5d173356a06b42edeb64df43bbf73dd8910e96faae9d12676f2212fc9e"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"dbdbff5d173356a06b42edeb64df43bbf73dd8910e96faae9d12676f2212fc9e"},"posted_at":"2026-07-15T04:20:46.587Z","created_at":"2026-07-15T04:20:46.587Z","updated_at":"2026-07-17T02:42:59.280Z","machine":{"shape":"article.machine/v1","slug":"thinker-saltzer-schroeder","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-saltzer-schroeder","json":"https://miscsubjects.com/api/articles/thinker-saltzer-schroeder","bundle":"https://miscsubjects.com/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-saltzer-schroeder","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-saltzer-schroeder\",\"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-saltzer-schroeder\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-saltzer-schroeder | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-saltzer-schroeder","json":"/api/articles/thinker-saltzer-schroeder","markdown":"/api/articles/thinker-saltzer-schroeder/bundle?format=markdown","skill":"/api/articles/thinker-saltzer-schroeder/skill","topology":"/api/articles/thinker-saltzer-schroeder/topology","versions":"/api/articles/thinker-saltzer-schroeder/revisions","invocations":"/api/articles/thinker-saltzer-schroeder/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-saltzer-schroeder","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":"4dd14f0e9e5874e9861e524b761d5fd79378f66c5e5291509f40834aa612c20f","object":{"object_type":"article-object","identity":{"id":"article:thinker-saltzer-schroeder","slug":"thinker-saltzer-schroeder","title":"Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems"},"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-saltzer-schroeder","role":"explain","audience":"human"},"skill":{"route":"/api/articles/thinker-saltzer-schroeder/skill","role":"direct behavior","audience":"model","content":"---\nname: thinker-saltzer-schroeder\ndescription: Apply the Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems\n\nThis Skill is the behavioral expression of [the canonical article](/a/thinker-saltzer-schroeder). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/thinker-saltzer-schroeder.\n- Read claims and relationships at /api/articles/thinker-saltzer-schroeder/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 › Jerome Saltzer and Michael Schroeder — The Protection o\n\n## Representations\n\n- Human: /a/thinker-saltzer-schroeder\n- JSON: /api/articles/thinker-saltzer-schroeder\n- Relationships: /api/articles/thinker-saltzer-schroeder/topology\n- History: /api/articles/thinker-saltzer-schroeder/revisions\n"},"json":{"route":"/api/articles/thinker-saltzer-schroeder","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder","thinker","saltzer","schroeder"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/thinker-saltzer-schroeder/invocations?status=success","failure_events":"/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder","title":"Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems","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) › **Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems**\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# Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems\n\n## §SELF — thinker-saltzer-schroeder\n\n**What this page is:** A summary of the eight security design principles defined by Saltzer and Schroeder in their 1974 paper.\n**What it explains:** How to design a computer system so that it protects information by default, and why eight specific principles make the difference between a secure system and an insecure one.\n**Why read it:** To understand the rules that every secure system follows, and to see how a single paper written in 1974 still defines security architecture today.\n\n### What Saltzer and Schroeder Is\n\nJerome Saltzer (born 1939) is a computer scientist at MIT. Michael Schroeder is a computer scientist at Xerox PARC and later at DEC Systems Research Center. In 1974 they published \"The Protection of Information in Computer Systems\" in the *Proceedings of the IEEE*. This paper is the most cited publication in the field of computer security. It lists eight design principles for building systems that protect information from unauthorized access.\n\n### Why It Matters\n\nEvery security breach that makes the news happens because one or more of these eight principles was violated. When a system defaults to allowing access, that is a violation of fail-safe defaults. When a system checks permission once and never again, that is a violation of complete mediation. When a system's security depends on keeping its source code secret, that is a violation of open design. Saltzer and Schroeder did not invent these principles out of nothing — they extracted them from studying which systems failed and which systems survived. Their paper is a checklist. Violate it at your own risk.\n\n### The Key Idea\n\nSecurity is not a feature you add to a system after you build it. Security is a property of how the system is designed. Saltzer and Schroeder distilled this into eight principles:\n\n1. **Economy of mechanism.** The security mechanism should be as simple and small as possible. A small mechanism has fewer bugs, is easier to verify, and is easier to understand. Complexity is the enemy of security.\n2. **Fail-safe defaults.** The default state of the system should be \"no access.\" Access should be granted only by explicit permission. If the permission check fails or is missing, the result should be denial, not access.\n3. **Complete mediation.** Every access to every resource must be checked for authorization. Not just the first access. Every access. If a program checks permission on Monday and never checks again, an attacker who gains access on Tuesday wins.\n4. **Open design.** The security of the system should not depend on the secrecy of its design or implementation. The design should be public. The keys should be secret, not the mechanism. This is the opposite of \"security through obscurity.\"\n5. **Separation of privilege.** Access to a sensitive resource should require more than one condition. For example, a bank vault should require two keys held by different people. A single compromised credential should not be enough.\n6. **Least privilege.** Every program and every user should operate using the minimum permissions needed to complete their task. No more. If a program is compromised while holding excess permissions, the attacker gets those excess permissions too.\n7. **Least common mechanism.** Minimize the amount of mechanism shared by different users. Shared mechanisms are single points of failure. If one user's action can affect a shared resource, that shared resource becomes a channel for attack.\n8. **Psychological acceptability.** Security mechanisms must be usable. If a security mechanism is too hard to use, people will bypass it. A perfect security system that nobody uses is an insecure system.\n\n### What They Got Right\n\n- They identified that security is a design problem, not an implementation problem. You cannot bolt security onto a badly designed system.\n- They proved that simplicity beats complexity. Economy of mechanism is the first principle for a reason.\n- They defined fail-safe defaults, which means the system is secure when it fails. This inverts the usual engineering assumption that a failure should produce a harmless output. In security, a failure should produce a denial.\n- They separated the secret (the key) from the mechanism (the design). Open design means the security community can audit the system. A secret mechanism cannot be audited.\n- They recognized that human behavior matters. Psychological acceptability acknowledges that security is a human problem as much as a technical one.\n\n### What They Got Wrong or Left Unfinished\n\n- The paper predates distributed systems, the internet, and cloud computing. The principles apply to distributed systems, but Saltzer and Schroeder did not address the specific problems of authentication across networks, key distribution, or Byzantine failures.\n- They did not address capabilities or object-capability security. Their model assumes an access control matrix or ACL model. Capability-based systems implement these principles differently — for example, least privilege in a capability system means holding only the capabilities you need, not having a broad identity with restricted permissions.\n- They did not provide a method for measuring or verifying whether a system follows the principles. The principles are guidelines, not formal specifications.\n\n### How It Connects to Other Ideas\n\n- **OIP (Open Invocation Protocol).** OIP implements all eight principles: (1) Economy: one dispatch door endpoint. (2) Fail-safe: default is no access; tokens grant explicitly. (3) Complete mediation: every invocation checks the token. (4) Open design: the OIP specification is public. (5) Separation: the owner gate requires both a valid token AND owner approval. (6) Least privilege: tokens are scoped to specific objects. (7) Least common: tenant isolation prevents shared mechanisms between users. (8) Psychological: Tap & Go requires one copy action.\n- **Butler Lampson's \"Protection.\"** Lampson (1971) provided the theoretical model of access control matrices and protection domains. Saltzer and Schroeder (1974) extracted the design principles that make those models work in practice. The two papers are complementary: Lampson described the what; Saltzer and Schroeder described the how.\n- **Capability-based security.** Capability systems implement least privilege by construction — a process can only use the capabilities it holds. Saltzer and Schroeder's principles are independent of any specific mechanism, but capability-based security is one of the cleanest implementations of them.\n\n### Sources\n\n- Saltzer, J. H. and Schroeder, M. D. \"The Protection of Information in Computer Systems.\" *Proceedings of the IEEE*, Vol. 63, No. 9, pp. 1278–1308, September 1974.\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-saltzer-schroeder`\n- JSON article: `https://miscsubjects.com/api/articles/thinker-saltzer-schroeder`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Jerome%20Saltzer%20and%20Michael%20Schroeder%20%E2%80%94%20The%20Protection%20of%20Information%20in%20Computer%20Systems`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-saltzer-schroeder"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/thinker-saltzer-schroeder/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:46.587Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"f51632ab71d703c1d34d7c616feae2c081f8fcdc281e8fccc39146439292a63e"},{"ts":"2026-07-17T02:42:59.280Z","model":"owner","action":"voxel_divide","prompt":"","input":"thinker-saltzer-schroeder","response":"27 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"f51632ab71d703c1d34d7c616feae2c081f8fcdc281e8fccc39146439292a63e","hash":"dbdbff5d173356a06b42edeb64df43bbf73dd8910e96faae9d12676f2212fc9e"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"dbdbff5d173356a06b42edeb64df43bbf73dd8910e96faae9d12676f2212fc9e"},"posted_at":"2026-07-15T04:20:46.587Z","created_at":"2026-07-15T04:20:46.587Z","updated_at":"2026-07-17T02:42:59.280Z","machine":{"shape":"article.machine/v1","slug":"thinker-saltzer-schroeder","kind":"article","read":{"human":"https://miscsubjects.com/a/thinker-saltzer-schroeder","json":"https://miscsubjects.com/api/articles/thinker-saltzer-schroeder","bundle":"https://miscsubjects.com/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=thinker-saltzer-schroeder","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-saltzer-schroeder\",\"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-saltzer-schroeder\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/thinker-saltzer-schroeder/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-saltzer-schroeder\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/thinker-saltzer-schroeder | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/thinker-saltzer-schroeder","json":"/api/articles/thinker-saltzer-schroeder","markdown":"/api/articles/thinker-saltzer-schroeder/bundle?format=markdown","skill":"/api/articles/thinker-saltzer-schroeder/skill","topology":"/api/articles/thinker-saltzer-schroeder/topology","versions":"/api/articles/thinker-saltzer-schroeder/revisions","invocations":"/api/articles/thinker-saltzer-schroeder/invocations"},"editorial_review":null,"editorial_audit":{"slug":"thinker-saltzer-schroeder","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":"4dd14f0e9e5874e9861e524b761d5fd79378f66c5e5291509f40834aa612c20f"}}}