{"_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":"systems-design-the-premise","title":"The Premise","body":"The Premise\n\nSystems design is the highest calling because it is the act of externalizing, memorializing, and formalizing your ought — what you believe should be — into a structure that can be observed, tested, loaded, and judged.\nWhen you take issue with what is, a system should be your representation of what ought to be. What it says, what it does, its attack surface, its ability to hold under load — that is the measure of the designer, and of the designer under the load of it.\n---\n\nIn the miscsubjects build, this axiom is not abstract. The ledger is the remedy. Every turn, every tool call, every cost is recorded. The owner can see what the system did, why it did it, and what it cost. A system without a ledger is a system that traps the actor in opacity. The build does not do this. The build makes the capable actor — itself — transparent, so the trapped actor — the owner — can verify that remedy is being provided.\n\n---\n\n## Corpus map\n- Next: [Systems Design: a₁ — Polarity Is Required for Systems Integrity](/a/systems-design-axiom-1)\n- Series start: [Systems Design — The Premise](/a/systems-design-the-premise)\n- Kin: [Law VII — The Designer](/a/oip-the-designer) · [Axioms A0-A9](/a/oip-axiom-a0)","hero":null,"images":[],"style":{},"tags":["OIP","systems-design","philosophy"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/systems-design-the-premise/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":["Systems design is the highest calling because it is the act of externalizing, memorializing, and formalizing your ought into a structure that can be observed, tested, loaded, and judged.","When you take issue with what is, a system should be your representation of what ought to be; what it says, what it does, its attack surface, and its ability to hold under load measure the designer.","In the miscsubjects build, the ledger is the remedy — every turn, every tool call, and every cost is recorded, making the capable actor transparent so the trapped actor can verify that remedy is being provided."],"sources":[{"title":"Systems Design: a₁ — Polarity Is Required for Systems Integrity","url":"https://miscsubjects.com/a/systems-design-axiom-1"},{"title":"Book VII — The Designer","url":"https://miscsubjects.com/a/oip-the-designer"},{"title":"Axioms A0-A9","url":"https://miscsubjects.com/a/oip-axiom-a0"}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":null,"next":"systems-design-axiom-1","hub":"systems-design-the-premise","series":"systems-design","position":1,"of":14}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":5,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:07.215Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"b4c336eb17210effaa9416777564abc80ed77dc15fd6a63297811fadd4dd2e97"},{"ts":"2026-07-04T04:39:09.086Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"b4c336eb17210effaa9416777564abc80ed77dc15fd6a63297811fadd4dd2e97","hash":"a62fc0ce03f7d4c22071ab626f51ba1c8e63719bbe7597185c8d1f12bb070ffa"},{"ts":"2026-07-04T05:03:13.671Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"a62fc0ce03f7d4c22071ab626f51ba1c8e63719bbe7597185c8d1f12bb070ffa","hash":"6648cc47c57b8019d4ab494b3a2bfa13f10b4a1838ebd5dda6b8adc3c4ac8ad5"},{"ts":"2026-07-17T02:37:50.264Z","model":"owner","action":"voxel_divide","prompt":"","input":"systems-design-the-premise","response":"6 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"6648cc47c57b8019d4ab494b3a2bfa13f10b4a1838ebd5dda6b8adc3c4ac8ad5","hash":"82e0e96d0e6273ef210f05301fa48f9c86122e4d4567fbe47c9ff1af722a4d00"}],"energy":{"passes":4,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1},"head":"82e0e96d0e6273ef210f05301fa48f9c86122e4d4567fbe47c9ff1af722a4d00"},"posted_at":"2026-07-04T03:17:25.472Z","created_at":"2026-07-04T03:17:25.472Z","updated_at":"2026-07-17T02:37:50.264Z","machine":{"shape":"article.machine/v1","slug":"systems-design-the-premise","kind":"corpus","read":{"human":"https://miscsubjects.com/a/systems-design-the-premise","json":"https://miscsubjects.com/api/articles/systems-design-the-premise","bundle":"https://miscsubjects.com/api/articles/systems-design-the-premise/bundle?format=markdown"},"traversal":{"prev":null,"next":{"slug":"systems-design-axiom-1","human":"https://miscsubjects.com/a/systems-design-axiom-1","json":"https://miscsubjects.com/api/articles/systems-design-axiom-1"},"hub":{"slug":"systems-design-the-premise","human":"https://miscsubjects.com/a/systems-design-the-premise","json":"https://miscsubjects.com/api/articles/systems-design-the-premise"},"series":"systems-design","position":1,"of":14},"ledger":{"claims":3,"sources":3,"contributions":0,"revisions":5,"objections_url":"https://miscsubjects.com/api/articles/systems-design-the-premise/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=systems-design-the-premise","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":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"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\":\"systems-design-the-premise\",\"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\":\"systems-design-the-premise\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/systems-design-the-premise/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\":\"systems-design-the-premise\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/systems-design-the-premise | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/systems-design-the-premise","json":"/api/articles/systems-design-the-premise","markdown":"/api/articles/systems-design-the-premise/bundle?format=markdown","skill":"/api/articles/systems-design-the-premise/skill","topology":"/api/articles/systems-design-the-premise/topology","versions":"/api/articles/systems-design-the-premise/revisions","invocations":"/api/articles/systems-design-the-premise/invocations"},"editorial_review":null,"editorial_audit":{"slug":"systems-design-the-premise","ok":false,"issues":[{"code":"headline_quality","message":"headline is too short to orient a cold reader; name the subject and event: \"The Premise\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"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":"48c8666a8ca9b24ff47078ebbec88f75e2655378f6ad0950c08adc39088122b4","object":{"object_type":"article-object","identity":{"id":"article:systems-design-the-premise","slug":"systems-design-the-premise","title":"The Premise"},"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/systems-design-the-premise","role":"explain","audience":"human"},"skill":{"route":"/api/articles/systems-design-the-premise/skill","role":"direct behavior","audience":"model","content":"---\nname: systems-design-the-premise\ndescription: Apply the The Premise article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# The Premise\n\nThis Skill is the behavioral expression of [the canonical article](/a/systems-design-the-premise). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/systems-design-the-premise.\n- Read claims and relationships at /api/articles/systems-design-the-premise/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\nThe Premise Systems design is the highest calling because it is the act of externalizing, memorializing, and formalizing your ought — what you believe should be — into a structure that can be observed, tested, loaded, and judged. When you t\n\n## Representations\n\n- Human: /a/systems-design-the-premise\n- JSON: /api/articles/systems-design-the-premise\n- Relationships: /api/articles/systems-design-the-premise/topology\n- History: /api/articles/systems-design-the-premise/revisions\n"},"json":{"route":"/api/articles/systems-design-the-premise","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/systems-design-the-premise/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"}},{"key":"DESIGN_LAW","type":"http","method":"GET","category":"design","enabled":true,"contract":"# WHAT: Discover the canonical Laws of Design Knowledge-Action Object.\\n# WHEN_TO_USE: any design, rendering, navigation, editorial, graph, admin, source, SEO, readability, or article-skill decision.\\n# ARGS: none for the contract; follow representations.invoke with surface and task to apply it.\\n# EX: [DESIGN_LAW][/DESIGN_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/design-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/DESIGN_LAW","json":"/api/directory/DESIGN_LAW","skill":"/api/directory/DESIGN_LAW?format=skill","oip_contract":"/api/dispatch?key=DESIGN_LAW"}}]},"ontology":{"conformance_group":"article","inferred_from":["OIP","systems-design","philosophy","systems","design","the","premise"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/systems-design-the-premise/invocations?status=success","failure_events":"/api/articles/systems-design-the-premise/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":"systems-design-the-premise","title":"The Premise","body":"The Premise\n\nSystems design is the highest calling because it is the act of externalizing, memorializing, and formalizing your ought — what you believe should be — into a structure that can be observed, tested, loaded, and judged.\nWhen you take issue with what is, a system should be your representation of what ought to be. What it says, what it does, its attack surface, its ability to hold under load — that is the measure of the designer, and of the designer under the load of it.\n---\n\nIn the miscsubjects build, this axiom is not abstract. The ledger is the remedy. Every turn, every tool call, every cost is recorded. The owner can see what the system did, why it did it, and what it cost. A system without a ledger is a system that traps the actor in opacity. The build does not do this. The build makes the capable actor — itself — transparent, so the trapped actor — the owner — can verify that remedy is being provided.\n\n---\n\n## Corpus map\n- Next: [Systems Design: a₁ — Polarity Is Required for Systems Integrity](/a/systems-design-axiom-1)\n- Series start: [Systems Design — The Premise](/a/systems-design-the-premise)\n- Kin: [Law VII — The Designer](/a/oip-the-designer) · [Axioms A0-A9](/a/oip-axiom-a0)","hero":null,"images":[],"style":{},"tags":["OIP","systems-design","philosophy"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/systems-design-the-premise/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":["Systems design is the highest calling because it is the act of externalizing, memorializing, and formalizing your ought into a structure that can be observed, tested, loaded, and judged.","When you take issue with what is, a system should be your representation of what ought to be; what it says, what it does, its attack surface, and its ability to hold under load measure the designer.","In the miscsubjects build, the ledger is the remedy — every turn, every tool call, and every cost is recorded, making the capable actor transparent so the trapped actor can verify that remedy is being provided."],"sources":[{"title":"Systems Design: a₁ — Polarity Is Required for Systems Integrity","url":"https://miscsubjects.com/a/systems-design-axiom-1"},{"title":"Book VII — The Designer","url":"https://miscsubjects.com/a/oip-the-designer"},{"title":"Axioms A0-A9","url":"https://miscsubjects.com/a/oip-axiom-a0"}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":null,"next":"systems-design-axiom-1","hub":"systems-design-the-premise","series":"systems-design","position":1,"of":14}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":5,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:07.215Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"b4c336eb17210effaa9416777564abc80ed77dc15fd6a63297811fadd4dd2e97"},{"ts":"2026-07-04T04:39:09.086Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"b4c336eb17210effaa9416777564abc80ed77dc15fd6a63297811fadd4dd2e97","hash":"a62fc0ce03f7d4c22071ab626f51ba1c8e63719bbe7597185c8d1f12bb070ffa"},{"ts":"2026-07-04T05:03:13.671Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"a62fc0ce03f7d4c22071ab626f51ba1c8e63719bbe7597185c8d1f12bb070ffa","hash":"6648cc47c57b8019d4ab494b3a2bfa13f10b4a1838ebd5dda6b8adc3c4ac8ad5"},{"ts":"2026-07-17T02:37:50.264Z","model":"owner","action":"voxel_divide","prompt":"","input":"systems-design-the-premise","response":"6 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"6648cc47c57b8019d4ab494b3a2bfa13f10b4a1838ebd5dda6b8adc3c4ac8ad5","hash":"82e0e96d0e6273ef210f05301fa48f9c86122e4d4567fbe47c9ff1af722a4d00"}],"energy":{"passes":4,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1},"head":"82e0e96d0e6273ef210f05301fa48f9c86122e4d4567fbe47c9ff1af722a4d00"},"posted_at":"2026-07-04T03:17:25.472Z","created_at":"2026-07-04T03:17:25.472Z","updated_at":"2026-07-17T02:37:50.264Z","machine":{"shape":"article.machine/v1","slug":"systems-design-the-premise","kind":"corpus","read":{"human":"https://miscsubjects.com/a/systems-design-the-premise","json":"https://miscsubjects.com/api/articles/systems-design-the-premise","bundle":"https://miscsubjects.com/api/articles/systems-design-the-premise/bundle?format=markdown"},"traversal":{"prev":null,"next":{"slug":"systems-design-axiom-1","human":"https://miscsubjects.com/a/systems-design-axiom-1","json":"https://miscsubjects.com/api/articles/systems-design-axiom-1"},"hub":{"slug":"systems-design-the-premise","human":"https://miscsubjects.com/a/systems-design-the-premise","json":"https://miscsubjects.com/api/articles/systems-design-the-premise"},"series":"systems-design","position":1,"of":14},"ledger":{"claims":3,"sources":3,"contributions":0,"revisions":5,"objections_url":"https://miscsubjects.com/api/articles/systems-design-the-premise/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=systems-design-the-premise","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":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"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\":\"systems-design-the-premise\",\"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\":\"systems-design-the-premise\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/systems-design-the-premise/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\":\"systems-design-the-premise\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/systems-design-the-premise | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/systems-design-the-premise","json":"/api/articles/systems-design-the-premise","markdown":"/api/articles/systems-design-the-premise/bundle?format=markdown","skill":"/api/articles/systems-design-the-premise/skill","topology":"/api/articles/systems-design-the-premise/topology","versions":"/api/articles/systems-design-the-premise/revisions","invocations":"/api/articles/systems-design-the-premise/invocations"},"editorial_review":null,"editorial_audit":{"slug":"systems-design-the-premise","ok":false,"issues":[{"code":"headline_quality","message":"headline is too short to orient a cold reader; name the subject and event: \"The Premise\"","replacement":"Write a shorter literal headline naming the article subject and its central event or claim."},{"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":"48c8666a8ca9b24ff47078ebbec88f75e2655378f6ad0950c08adc39088122b4"}}}