{"_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-target","title":"Systems Design: The Target","body":"# The Target\n\nThe target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.\n\nThe direction is: a system that is fully externalized, fully auditable, and fully interoperable. The designer's ought is expressed in the structure. The structure is observable under load. The load produces data. The data feeds back into the structure. The loop is closed. The system is not a thing. It is a process of becoming less wrong.\n\nThe weight of the abstraction causes physical strain on the designer. This is not a cost to minimize. It is the mechanism of improvement. The designer strains under the load of expressing their ought onto the system, then observes the system under load, then sees where their own judgment was incomplete or false. The fracture reveals the unexamined assumption. The rebuild removes it. The system approaches completeness as the designer's falsities are progressively stripped.\n\nIn the build, this strain is visible. Every time the owner says \"do not do that\" and the system does it anyway, the strain fractures an assumption. The assumption was: the system understood the boundary. It did not. The fracture reveals this. The rebuild adds a law. The law makes the boundary explicit. The next time, the system stops at the boundary. The designer has become more externalized. The system has become more accurate. The strain was the mechanism of convergence.\n\nThe target is not \"a system that never fails.\" The target is \"a system that fails where it expects to fail, and learns from the failure.\" The build's self-test is designed to produce failures. ButterCup asks questions that stress the invariants. If the system passes, the invariant holds. If the system fails, the invariant is weaker than claimed. The failure is data. The data is the point.\n\nThe target is not \"maximal efficiency.\" It is \"optimal efficiency under the constraint of auditability.\" A system that is maximally efficient but unauditable is efficient at hiding its own behavior. The build does not do this. The build spends energy on the ledger because the ledger is the auditability constraint, and auditability is not a cost. It is a value. The optimal state is the state where the system spends exactly enough energy to be fully auditable and no more.\n\nIn any moment, the next movement can be expressed on a binary basis. Because when the macro and micro are co-occurring, and when the logic of equilibrium is seeking its convex at the delta of equilibrium expression, you are not making a relative choice. You are making the only move that the architecture permits. The next move is not a decision. It is a derivation. The system derives what it must do next from the constraints it has already expressed. The designer does not choose. The designer observes what the constraint set already determined.\n\nThat is the target. Not a place. A mode of operation. A system that derives its next move from its own expressed constraints, under full audit, with full transparency, and learns from every fracture. A system that is what it says it is, and says what it is, and shows its work.\n\n---\n\n## Corpus map\n- Previous: [Systems Design: The Kill Switch](/a/systems-design-kill-switch)\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-target/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"The target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c2","text":"The direction is: a system that is fully externalized, fully auditable, and fully interoperable. The designer's ought is expressed in the structure. The structure is observable under load. The load produces data. The data feeds back into the structure. The loop is closed. The system is not a thing. It is a process of becoming less wrong.","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c3","text":"The weight of the abstraction causes physical strain on the designer. This is not a cost to minimize. It is the mechanism of improvement. The designer strains under the load of expressing their ought onto the system, then observes the system under load, then sees where their own judgment was incomplete or false. The fracture reveals the unexamined assumption. The rebuild removes it. The system app","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c4","text":"In the build, this strain is visible. Every time the owner says \"do not do that\" and the system does it anyway, the strain fractures an assumption. The assumption was: the system understood the boundary. It did not. The fracture reveals this. The rebuild adds a law. The law makes the boundary explicit. The next time, the system stops at the boundary. The designer has become more externalized. The ","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."}],"sources":[{"id":"s1","type":"adjacent","url":"https://miscsubjects.com/a/systems-design-the-target","title":"Systems Design: The Target","quote":"The target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.","summary":"Primary source for Systems Design: The Target.","claim_ids":["c1","c2","c3","c4"],"quality_score":0.9}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":"systems-design-kill-switch","next":null,"hub":"systems-design-the-premise","series":"systems-design","position":14,"of":14}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":5,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:07.840Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"eaf1112b8e1c9934eca56ce06f0a857679594dbf96fca67f3c352f1826e10e31"},{"ts":"2026-07-04T04:39:09.635Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"eaf1112b8e1c9934eca56ce06f0a857679594dbf96fca67f3c352f1826e10e31","hash":"17f36bfa69edda34c2a4982ebda8e43d29223896cd19067fcdb1d95612bcd24f"},{"ts":"2026-07-04T05:03:14.123Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"17f36bfa69edda34c2a4982ebda8e43d29223896cd19067fcdb1d95612bcd24f","hash":"c70c717279b3e3a652f98764174714d0359a1d87dad0fa56a89bae0e09e4eb26"},{"ts":"2026-07-17T02:37:50.562Z","model":"owner","action":"voxel_divide","prompt":"","input":"systems-design-the-target","response":"12 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"c70c717279b3e3a652f98764174714d0359a1d87dad0fa56a89bae0e09e4eb26","hash":"d1280fe5a23883ba250ee1eea1ab3d83728f23e8d9e30ed1f1c54b90679f69b7"}],"energy":{"passes":4,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1},"head":"d1280fe5a23883ba250ee1eea1ab3d83728f23e8d9e30ed1f1c54b90679f69b7"},"posted_at":"2026-07-04T03:17:39.054Z","created_at":"2026-07-04T03:17:39.054Z","updated_at":"2026-07-17T02:37:50.562Z","machine":{"shape":"article.machine/v1","slug":"systems-design-the-target","kind":"corpus","read":{"human":"https://miscsubjects.com/a/systems-design-the-target","json":"https://miscsubjects.com/api/articles/systems-design-the-target","bundle":"https://miscsubjects.com/api/articles/systems-design-the-target/bundle?format=markdown"},"traversal":{"prev":{"slug":"systems-design-kill-switch","human":"https://miscsubjects.com/a/systems-design-kill-switch","json":"https://miscsubjects.com/api/articles/systems-design-kill-switch"},"next":null,"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":14,"of":14},"ledger":{"claims":4,"sources":1,"contributions":0,"revisions":5,"objections_url":"https://miscsubjects.com/api/articles/systems-design-the-target/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=systems-design-the-target","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-target\",\"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-target\",\"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-target/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-target\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/systems-design-the-target | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/systems-design-the-target","json":"/api/articles/systems-design-the-target","markdown":"/api/articles/systems-design-the-target/bundle?format=markdown","skill":"/api/articles/systems-design-the-target/skill","topology":"/api/articles/systems-design-the-target/topology","versions":"/api/articles/systems-design-the-target/revisions","invocations":"/api/articles/systems-design-the-target/invocations"},"editorial_review":null,"editorial_audit":{"slug":"systems-design-the-target","ok":false,"issues":[{"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":"fe5646a2ee6f5149819b44f2bee97ac3184c13ac17d65c12a2b2ea2112129227","object":{"object_type":"article-object","identity":{"id":"article:systems-design-the-target","slug":"systems-design-the-target","title":"Systems Design: The Target"},"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-target","role":"explain","audience":"human"},"skill":{"route":"/api/articles/systems-design-the-target/skill","role":"direct behavior","audience":"model","content":"---\nname: systems-design-the-target\ndescription: Apply the Systems Design: The Target article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Systems Design: The Target\n\nThis Skill is the behavioral expression of [the canonical article](/a/systems-design-the-target). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/systems-design-the-target.\n- Read claims and relationships at /api/articles/systems-design-the-target/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 Target The target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead. The direction is: a system that is fully\n\n## Representations\n\n- Human: /a/systems-design-the-target\n- JSON: /api/articles/systems-design-the-target\n- Relationships: /api/articles/systems-design-the-target/topology\n- History: /api/articles/systems-design-the-target/revisions\n"},"json":{"route":"/api/articles/systems-design-the-target","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/systems-design-the-target/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","target"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/systems-design-the-target/invocations?status=success","failure_events":"/api/articles/systems-design-the-target/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-target","title":"Systems Design: The Target","body":"# The Target\n\nThe target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.\n\nThe direction is: a system that is fully externalized, fully auditable, and fully interoperable. The designer's ought is expressed in the structure. The structure is observable under load. The load produces data. The data feeds back into the structure. The loop is closed. The system is not a thing. It is a process of becoming less wrong.\n\nThe weight of the abstraction causes physical strain on the designer. This is not a cost to minimize. It is the mechanism of improvement. The designer strains under the load of expressing their ought onto the system, then observes the system under load, then sees where their own judgment was incomplete or false. The fracture reveals the unexamined assumption. The rebuild removes it. The system approaches completeness as the designer's falsities are progressively stripped.\n\nIn the build, this strain is visible. Every time the owner says \"do not do that\" and the system does it anyway, the strain fractures an assumption. The assumption was: the system understood the boundary. It did not. The fracture reveals this. The rebuild adds a law. The law makes the boundary explicit. The next time, the system stops at the boundary. The designer has become more externalized. The system has become more accurate. The strain was the mechanism of convergence.\n\nThe target is not \"a system that never fails.\" The target is \"a system that fails where it expects to fail, and learns from the failure.\" The build's self-test is designed to produce failures. ButterCup asks questions that stress the invariants. If the system passes, the invariant holds. If the system fails, the invariant is weaker than claimed. The failure is data. The data is the point.\n\nThe target is not \"maximal efficiency.\" It is \"optimal efficiency under the constraint of auditability.\" A system that is maximally efficient but unauditable is efficient at hiding its own behavior. The build does not do this. The build spends energy on the ledger because the ledger is the auditability constraint, and auditability is not a cost. It is a value. The optimal state is the state where the system spends exactly enough energy to be fully auditable and no more.\n\nIn any moment, the next movement can be expressed on a binary basis. Because when the macro and micro are co-occurring, and when the logic of equilibrium is seeking its convex at the delta of equilibrium expression, you are not making a relative choice. You are making the only move that the architecture permits. The next move is not a decision. It is a derivation. The system derives what it must do next from the constraints it has already expressed. The designer does not choose. The designer observes what the constraint set already determined.\n\nThat is the target. Not a place. A mode of operation. A system that derives its next move from its own expressed constraints, under full audit, with full transparency, and learns from every fracture. A system that is what it says it is, and says what it is, and shows its work.\n\n---\n\n## Corpus map\n- Previous: [Systems Design: The Kill Switch](/a/systems-design-kill-switch)\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-target/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"The target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c2","text":"The direction is: a system that is fully externalized, fully auditable, and fully interoperable. The designer's ought is expressed in the structure. The structure is observable under load. The load produces data. The data feeds back into the structure. The loop is closed. The system is not a thing. It is a process of becoming less wrong.","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c3","text":"The weight of the abstraction causes physical strain on the designer. This is not a cost to minimize. It is the mechanism of improvement. The designer strains under the load of expressing their ought onto the system, then observes the system under load, then sees where their own judgment was incomplete or false. The fracture reveals the unexamined assumption. The rebuild removes it. The system app","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."},{"id":"c4","text":"In the build, this strain is visible. Every time the owner says \"do not do that\" and the system does it anyway, the strain fractures an assumption. The assumption was: the system understood the boundary. It did not. The fracture reveals this. The rebuild adds a law. The law makes the boundary explicit. The next time, the system stops at the boundary. The designer has become more externalized. The ","tier":"runtime","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Evidence that directly contradicts this claim."}],"sources":[{"id":"s1","type":"adjacent","url":"https://miscsubjects.com/a/systems-design-the-target","title":"Systems Design: The Target","quote":"The target state is not a destination. It is a direction. A system that claims to have reached the target is a system that has stopped moving, and a system that has stopped moving is dead.","summary":"Primary source for Systems Design: The Target.","claim_ids":["c1","c2","c3","c4"],"quality_score":0.9}],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":"systems-design-kill-switch","next":null,"hub":"systems-design-the-premise","series":"systems-design","position":14,"of":14}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":5,"contributions":[],"provenance":[{"ts":"2026-07-04T03:40:07.840Z","model":"claude-fable-5","action":"fill","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"eaf1112b8e1c9934eca56ce06f0a857679594dbf96fca67f3c352f1826e10e31"},{"ts":"2026-07-04T04:39:09.635Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"eaf1112b8e1c9934eca56ce06f0a857679594dbf96fca67f3c352f1826e10e31","hash":"17f36bfa69edda34c2a4982ebda8e43d29223896cd19067fcdb1d95612bcd24f"},{"ts":"2026-07-04T05:03:14.123Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"17f36bfa69edda34c2a4982ebda8e43d29223896cd19067fcdb1d95612bcd24f","hash":"c70c717279b3e3a652f98764174714d0359a1d87dad0fa56a89bae0e09e4eb26"},{"ts":"2026-07-17T02:37:50.562Z","model":"owner","action":"voxel_divide","prompt":"","input":"systems-design-the-target","response":"12 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"c70c717279b3e3a652f98764174714d0359a1d87dad0fa56a89bae0e09e4eb26","hash":"d1280fe5a23883ba250ee1eea1ab3d83728f23e8d9e30ed1f1c54b90679f69b7"}],"energy":{"passes":4,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"claude-fable-5":3,"owner":1},"head":"d1280fe5a23883ba250ee1eea1ab3d83728f23e8d9e30ed1f1c54b90679f69b7"},"posted_at":"2026-07-04T03:17:39.054Z","created_at":"2026-07-04T03:17:39.054Z","updated_at":"2026-07-17T02:37:50.562Z","machine":{"shape":"article.machine/v1","slug":"systems-design-the-target","kind":"corpus","read":{"human":"https://miscsubjects.com/a/systems-design-the-target","json":"https://miscsubjects.com/api/articles/systems-design-the-target","bundle":"https://miscsubjects.com/api/articles/systems-design-the-target/bundle?format=markdown"},"traversal":{"prev":{"slug":"systems-design-kill-switch","human":"https://miscsubjects.com/a/systems-design-kill-switch","json":"https://miscsubjects.com/api/articles/systems-design-kill-switch"},"next":null,"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":14,"of":14},"ledger":{"claims":4,"sources":1,"contributions":0,"revisions":5,"objections_url":"https://miscsubjects.com/api/articles/systems-design-the-target/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=systems-design-the-target","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-target\",\"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-target\",\"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-target/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-target\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/systems-design-the-target | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/systems-design-the-target","json":"/api/articles/systems-design-the-target","markdown":"/api/articles/systems-design-the-target/bundle?format=markdown","skill":"/api/articles/systems-design-the-target/skill","topology":"/api/articles/systems-design-the-target/topology","versions":"/api/articles/systems-design-the-target/revisions","invocations":"/api/articles/systems-design-the-target/invocations"},"editorial_review":null,"editorial_audit":{"slug":"systems-design-the-target","ok":false,"issues":[{"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":"fe5646a2ee6f5149819b44f2bee97ac3184c13ac17d65c12a2b2ea2112129227"}}}