{"slug":"oip-pattern-1-pattern-1-branching-the-routing-solution","title":"Pattern 1: Pattern 1: Branching — The Routing Solution","body":"# Pattern 1: Pattern 1: Branching — The Routing Solution\n\nPattern 1: Branching — The Routing Solution\nFormal definition. Branching is the geometric solution to the problem of connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint. The problem is: given a volume that must be perfused, and a cost function on conduit material, what geometry minimizes total cost? The answer is a hierarchical tree with specific scaling of branch diameters at each bifurcation.\nMechanism. The physics is optimal transport with a volume constraint. When a flow splits, the daughter branches must carry the split flow. If the daughter branches are too narrow, viscous losses dominate. If too wide, material cost dominates. The optimum lies at a specific ratio of daughter-to-parent diameter.\nMathematical load: Murray’s Law.\nMurray’s Law: r₀³ = r₁³ + r₂³\nWhere r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches. The exponent 3 derives from the balance between Poiseuille flow (pressure drop ∝ r⁻⁴) and metabolic cost of blood/vessel maintenance (∝ r²). Minimizing total cost (pumping + maintenance) yields the cubic relationship. The law holds exactly for optimal laminar flow.\nFor symmetric bifurcation (r₁ = r₂): r_daughter / r_parent = 2^(-1/3) ≈ 0.794.\nConvergence instances (minimum 5 from wildly different domains):\nLightning. Dielectric breakdown in air creates ionized channels. The channel branches to distribute charge from cloud to ground. Channel diameters at bifurcations follow Murray-like scaling. Scale: ~1-10 km total length, channel radius ~cm. Domain: atmospheric electricity.\nRiver networks. Fluvial erosion carves dendritic drainage patterns. Horton’s laws of stream numbers and lengths are the geomorphological expression of optimal transport. The branching angle ~72° maximizes drainage efficiency. Scale: 10⁰ m (rill) to 10⁶ m (Amazon basin). Domain: geomorphology.\nMammalian lungs. The bronchial tree has ~23 generations of bifurcation, reaching ~300 million alveoli. Diameter ratio ~0.79 per generation, matching Murray’s Law. Scale: trachea ~2 cm diameter; terminal bronchioles ~0.5 mm. Domain: physiology.\nBlood vessels. Arterial tree from aorta (~2.5 cm) to capillaries (~5 μm). Murray’s Law holds across 4 orders of magnitude of diameter. Deviations (e.g., aortic arch) correspond to pulsatile flow corrections. Scale: 10⁻⁵ m to 10⁻² m. Domain: cardiovascular physiology.\nNeurons. Dendritic arborizations branch to sample synaptic input from a volume. The branching geometry optimizes signal propagation and metabolic cost. Pyramidal cell dendrites: ~10⁴ synapses distributed across 4-6 branch orders. Scale: soma ~10 μm; dendritic span ~100 μm-1 mm. Domain: neuroscience.\nPlant roots. Root systems branch to forage soil volume for water and nutrients. Root architecture follows similar optimality principles, with tradeoffs between exploration and exploitation. Scale: 10⁻⁴ m (root hairs) to 10¹ m (taproot depth). Domain: plant biology.\nMycelial networks. Fungal hyphae form vast branching networks — the largest known organisms. The network optimizes nutrient transport across scales from μm hyphae to km-scale networks. Scale: 10⁻⁶ m to 10³ m. Domain: mycology/network biology.\nRiver deltas. Distributary channels branch as flow decelerates upon entering standing water. The bifurcation geometry follows from mass conservation and bedload partitioning. Scale: 10³ m to 10⁵ m. Domain: sedimentology.\nScale range: 10⁻⁶ m (mycelial hyphae, capillaries) to 10⁶ m (Amazon basin, continental drainage). 22 orders of magnitude.\nWhat it is NOT. Branching is not mere splitting. A crack in glass splits but does not branch optimally. Branching is not fractal recursion — although it can be fractal, the defining property is the optimality condition (Murray’s Law or equivalent), not self-similarity alone. Branching does not require a designer; it emerges from gradient dissipation with transport costs.\n\n---\n\n## Corpus map\n- Next: [Pattern 1: Branching — The Routing Solution](/a/oip-pattern-1-branching-the-routing-solution)\n- Source book: [Signature of the Grain — Preamble & Axioms](/a/oip-sog-preamble-axioms)\n- Kin corpus: [GRAIN — What the Grain Favors](/a/grain-what-the-grain-favors)","hero":null,"images":[],"style":{},"tags":["philosophy","oip","signature-of-the-grain","pattern","systems-theory"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Core definition of the pattern in the OIP corpus.","evidence_basis":"atomized","weight":0.1,"status":"cut","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c2","text":"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Central mathematical invariant of optimal branching geometry.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c3","text":"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Direct quantitative consequence of Murray’s Law under symmetry.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c4","text":"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"anecdotal","source_ids":[],"source_status":"unsourced","why_material":"Corpus assertion of cross-domain convergence of the optimality condition.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}}],"sources":[],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":null,"next":"oip-pattern-1-branching-the-routing-solution","hub":"oip-sog-preamble-axioms","series":"signature-patterns","position":1,"of":16}},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":2,"contributions":[{"seq":0,"id":"k1","ts":"2026-07-07T07:49:44.424Z","model":"grok/grok-4.3","role":"atomizer","action":"atomize","payload":{"claims":[{"id":"c1","text":"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.","tier":"speculative"},{"id":"c2","text":"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.","tier":"mechanistic"},{"id":"c3","text":"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.","tier":"mechanistic"},{"id":"c4","text":"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).","tier":"anecdotal"}]},"rationale":"schema conformance: body left untouched, claims atomized","tokens_in":3696,"tokens_out":1452,"cost":0.00825,"prev_hash":"genesis","hash":"1a1dfdd14b5352f86a0d528edb42a36a34848325e8f6f843ef1349b9c5b7ad3f"}],"provenance":[{"ts":"2026-07-04T04:34:13.123Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"84be173993397053b6ab8f6269314a733bd8a82ed17a213013e3778fb5d8a390"},{"ts":"2026-07-04T05:02:09.430Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"84be173993397053b6ab8f6269314a733bd8a82ed17a213013e3778fb5d8a390","hash":"6905cd00a9ed04539189c5d58a3be7c95349ba184afc79c8d8933bbb986d1db7"},{"ts":"2026-07-07T07:49:44.424Z","model":"grok/grok-4.3","action":"atomize","prompt":"You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.\n\nALWAYS:\n- Extract every material assertion as one atomic claim, tied to the ## section it came from.\n- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.\n- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.\n- Prefer fewer, harder claims over many soft ones.\n\nNEVER:\n- Never rewrite, summarize, or output the body.\n- Never invent a URL, quote, or publication.\n- Never duplicate an existing claim text.","input":"atomize oip-pattern-1-pattern-1-branching-the-routing-solution","response":"{\n  \"claims\": [\n    {\n      \"id\": \"c1\",\n      \"text\": \"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"speculative\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Core definition of the pattern in the OIP corpus.\"\n    },\n    {\n      \"id\": \"c2\",\n      \"text\": \"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"mechanistic\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Central mathematical invariant of optimal branching geometry.\"\n    },\n    {\n      \"id\": \"c3\",\n      \"text\": \"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"mechanistic\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Direct quantitative consequence of Murray’s Law under symmetry.\"\n    },\n    {\n      \"id\": \"c4\",\n      \"text\": \"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"anecdotal\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Corpus assertion of cross-domain convergence of the optimality condition.\"\n    }\n  ],\n  \"sources\": []\n}","tokens_in":3696,"tokens_out":1452,"cost":0,"prev":"6905cd00a9ed04539189c5d58a3be7c95349ba184afc79c8d8933bbb986d1db7","hash":"55ff9d1a853cc58dea25002cf37b7970432ce9ce6dceee0b26a113dc21e31a72"},{"ts":"2026-07-07T07:49:44.743Z","model":"scorer","action":"score","prompt":"","input":"oip-pattern-1-pattern-1-branching-the-routing-solution","response":"[{\"claim_id\":\"c1\",\"old_weight\":0.1,\"new_weight\":0.1,\"status\":\"cut\"}]","tokens_in":0,"tokens_out":0,"cost":0,"prev":"55ff9d1a853cc58dea25002cf37b7970432ce9ce6dceee0b26a113dc21e31a72","hash":"1bf931eb6f920291eb852697917b89911a7c63fb9d7416c96e638775f38d42f9"},{"ts":"2026-07-17T02:36:24.459Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-pattern-1-pattern-1-branching-the-routing-solution","response":"5 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"1bf931eb6f920291eb852697917b89911a7c63fb9d7416c96e638775f38d42f9","hash":"faaeacc37491e5074dc91eccc8c0a2e35a33d7cabe6d3c84096c709fff237f09"}],"energy":{"passes":5,"tokens_in":3696,"tokens_out":1452,"tokens_total":5148,"cost_usd":0,"models":{"claude-fable-5":2,"grok/grok-4.3":1,"scorer":1,"owner":1},"head":"faaeacc37491e5074dc91eccc8c0a2e35a33d7cabe6d3c84096c709fff237f09"},"posted_at":"2026-07-04T02:40:04.915Z","created_at":"2026-07-04T02:40:04.915Z","updated_at":"2026-07-17T02:36:24.459Z","machine":{"shape":"article.machine/v1","slug":"oip-pattern-1-pattern-1-branching-the-routing-solution","kind":"corpus","read":{"human":"https://miscsubjects.com/a/oip-pattern-1-pattern-1-branching-the-routing-solution","json":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution","bundle":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/bundle?format=markdown"},"traversal":{"prev":null,"next":{"slug":"oip-pattern-1-branching-the-routing-solution","human":"https://miscsubjects.com/a/oip-pattern-1-branching-the-routing-solution","json":"https://miscsubjects.com/api/articles/oip-pattern-1-branching-the-routing-solution"},"hub":{"slug":"oip-sog-preamble-axioms","human":"https://miscsubjects.com/a/oip-sog-preamble-axioms","json":"https://miscsubjects.com/api/articles/oip-sog-preamble-axioms"},"series":"signature-patterns","position":1,"of":16},"ledger":{"claims":4,"sources":0,"contributions":1,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-pattern-1-pattern-1-branching-the-routing-solution","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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-pattern-1-pattern-1-branching-the-routing-solution","json":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution","markdown":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/bundle?format=markdown","skill":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/skill","topology":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/topology","versions":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/revisions","invocations":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-pattern-1-pattern-1-branching-the-routing-solution","slug":"oip-pattern-1-pattern-1-branching-the-routing-solution","title":"Pattern 1: Pattern 1: Branching — The Routing Solution"},"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/oip-pattern-1-pattern-1-branching-the-routing-solution","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-pattern-1-pattern-1-branching-the-routing-solution\ndescription: Apply the Pattern 1: Pattern 1: Branching — The Routing Solution article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Pattern 1: Pattern 1: Branching — The Routing Solution\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-pattern-1-pattern-1-branching-the-routing-solution). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution.\n- Read claims and relationships at /api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/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\nPattern 1: Pattern 1: Branching — The Routing Solution Pattern 1: Branching — The Routing Solution Formal definition. Branching is the geometric solution to the problem of connecting a single source to many distributed sinks or many sources\n\n## Representations\n\n- Human: /a/oip-pattern-1-pattern-1-branching-the-routing-solution\n- JSON: /api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution\n- Relationships: /api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/topology\n- History: /api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/revisions\n"},"json":{"route":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/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: Cyrus 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: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.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/massoumicyrus/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: Cyrus 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: Cyrus 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/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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":["philosophy","oip","signature-of-the-grain","pattern","systems-theory","oip","pattern","1","pattern","1","branching","the","routing","solution"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/invocations?status=success","failure_events":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/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":"oip-pattern-1-pattern-1-branching-the-routing-solution","title":"Pattern 1: Pattern 1: Branching — The Routing Solution","body":"# Pattern 1: Pattern 1: Branching — The Routing Solution\n\nPattern 1: Branching — The Routing Solution\nFormal definition. Branching is the geometric solution to the problem of connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint. The problem is: given a volume that must be perfused, and a cost function on conduit material, what geometry minimizes total cost? The answer is a hierarchical tree with specific scaling of branch diameters at each bifurcation.\nMechanism. The physics is optimal transport with a volume constraint. When a flow splits, the daughter branches must carry the split flow. If the daughter branches are too narrow, viscous losses dominate. If too wide, material cost dominates. The optimum lies at a specific ratio of daughter-to-parent diameter.\nMathematical load: Murray’s Law.\nMurray’s Law: r₀³ = r₁³ + r₂³\nWhere r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches. The exponent 3 derives from the balance between Poiseuille flow (pressure drop ∝ r⁻⁴) and metabolic cost of blood/vessel maintenance (∝ r²). Minimizing total cost (pumping + maintenance) yields the cubic relationship. The law holds exactly for optimal laminar flow.\nFor symmetric bifurcation (r₁ = r₂): r_daughter / r_parent = 2^(-1/3) ≈ 0.794.\nConvergence instances (minimum 5 from wildly different domains):\nLightning. Dielectric breakdown in air creates ionized channels. The channel branches to distribute charge from cloud to ground. Channel diameters at bifurcations follow Murray-like scaling. Scale: ~1-10 km total length, channel radius ~cm. Domain: atmospheric electricity.\nRiver networks. Fluvial erosion carves dendritic drainage patterns. Horton’s laws of stream numbers and lengths are the geomorphological expression of optimal transport. The branching angle ~72° maximizes drainage efficiency. Scale: 10⁰ m (rill) to 10⁶ m (Amazon basin). Domain: geomorphology.\nMammalian lungs. The bronchial tree has ~23 generations of bifurcation, reaching ~300 million alveoli. Diameter ratio ~0.79 per generation, matching Murray’s Law. Scale: trachea ~2 cm diameter; terminal bronchioles ~0.5 mm. Domain: physiology.\nBlood vessels. Arterial tree from aorta (~2.5 cm) to capillaries (~5 μm). Murray’s Law holds across 4 orders of magnitude of diameter. Deviations (e.g., aortic arch) correspond to pulsatile flow corrections. Scale: 10⁻⁵ m to 10⁻² m. Domain: cardiovascular physiology.\nNeurons. Dendritic arborizations branch to sample synaptic input from a volume. The branching geometry optimizes signal propagation and metabolic cost. Pyramidal cell dendrites: ~10⁴ synapses distributed across 4-6 branch orders. Scale: soma ~10 μm; dendritic span ~100 μm-1 mm. Domain: neuroscience.\nPlant roots. Root systems branch to forage soil volume for water and nutrients. Root architecture follows similar optimality principles, with tradeoffs between exploration and exploitation. Scale: 10⁻⁴ m (root hairs) to 10¹ m (taproot depth). Domain: plant biology.\nMycelial networks. Fungal hyphae form vast branching networks — the largest known organisms. The network optimizes nutrient transport across scales from μm hyphae to km-scale networks. Scale: 10⁻⁶ m to 10³ m. Domain: mycology/network biology.\nRiver deltas. Distributary channels branch as flow decelerates upon entering standing water. The bifurcation geometry follows from mass conservation and bedload partitioning. Scale: 10³ m to 10⁵ m. Domain: sedimentology.\nScale range: 10⁻⁶ m (mycelial hyphae, capillaries) to 10⁶ m (Amazon basin, continental drainage). 22 orders of magnitude.\nWhat it is NOT. Branching is not mere splitting. A crack in glass splits but does not branch optimally. Branching is not fractal recursion — although it can be fractal, the defining property is the optimality condition (Murray’s Law or equivalent), not self-similarity alone. Branching does not require a designer; it emerges from gradient dissipation with transport costs.\n\n---\n\n## Corpus map\n- Next: [Pattern 1: Branching — The Routing Solution](/a/oip-pattern-1-branching-the-routing-solution)\n- Source book: [Signature of the Grain — Preamble & Axioms](/a/oip-sog-preamble-axioms)\n- Kin corpus: [GRAIN — What the Grain Favors](/a/grain-what-the-grain-favors)","hero":null,"images":[],"style":{},"tags":["philosophy","oip","signature-of-the-grain","pattern","systems-theory"],"category":null,"model":"Fable 5 (Claude Code)","ledger":{"href":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"speculative","source_ids":[],"source_status":"unsourced","why_material":"Core definition of the pattern in the OIP corpus.","evidence_basis":"atomized","weight":0.1,"status":"cut","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c2","text":"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Central mathematical invariant of optimal branching geometry.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c3","text":"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"mechanistic","source_ids":[],"source_status":"unsourced","why_material":"Direct quantitative consequence of Murray’s Law under symmetry.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}},{"id":"c4","text":"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).","section":"# Pattern 1: Pattern 1: Branching — The Routing Solution","tier":"anecdotal","source_ids":[],"source_status":"unsourced","why_material":"Corpus assertion of cross-domain convergence of the optimality condition.","evidence_basis":"atomized","weight":0.3,"status":"active","stance_scores":{"neutral":0,"pro":0,"adversary":0}}],"sources":[],"reviews":[],"extra":{"kind":"corpus","corpus_map":{"prev":null,"next":"oip-pattern-1-branching-the-routing-solution","hub":"oip-sog-preamble-axioms","series":"signature-patterns","position":1,"of":16}},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":2,"contributions":[{"seq":0,"id":"k1","ts":"2026-07-07T07:49:44.424Z","model":"grok/grok-4.3","role":"atomizer","action":"atomize","payload":{"claims":[{"id":"c1","text":"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.","tier":"speculative"},{"id":"c2","text":"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.","tier":"mechanistic"},{"id":"c3","text":"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.","tier":"mechanistic"},{"id":"c4","text":"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).","tier":"anecdotal"}]},"rationale":"schema conformance: body left untouched, claims atomized","tokens_in":3696,"tokens_out":1452,"cost":0.00825,"prev_hash":"genesis","hash":"1a1dfdd14b5352f86a0d528edb42a36a34848325e8f6f843ef1349b9c5b7ad3f"}],"provenance":[{"ts":"2026-07-04T04:34:13.123Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"84be173993397053b6ab8f6269314a733bd8a82ed17a213013e3778fb5d8a390"},{"ts":"2026-07-04T05:02:09.430Z","model":"claude-fable-5","action":"edit","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"84be173993397053b6ab8f6269314a733bd8a82ed17a213013e3778fb5d8a390","hash":"6905cd00a9ed04539189c5d58a3be7c95349ba184afc79c8d8933bbb986d1db7"},{"ts":"2026-07-07T07:49:44.424Z","model":"grok/grok-4.3","action":"atomize","prompt":"You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.\n\nALWAYS:\n- Extract every material assertion as one atomic claim, tied to the ## section it came from.\n- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.\n- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.\n- Prefer fewer, harder claims over many soft ones.\n\nNEVER:\n- Never rewrite, summarize, or output the body.\n- Never invent a URL, quote, or publication.\n- Never duplicate an existing claim text.","input":"atomize oip-pattern-1-pattern-1-branching-the-routing-solution","response":"{\n  \"claims\": [\n    {\n      \"id\": \"c1\",\n      \"text\": \"Branching is the geometric solution to connecting a single source to many distributed sinks (or many sources to a single sink) with minimum total cost, subject to a flow constraint.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"speculative\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Core definition of the pattern in the OIP corpus.\"\n    },\n    {\n      \"id\": \"c2\",\n      \"text\": \"Murray’s Law states r₀³ = r₁³ + r₂³, where r₀ is the radius of the parent vessel and r₁, r₂ are the radii of the daughter branches.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"mechanistic\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Central mathematical invariant of optimal branching geometry.\"\n    },\n    {\n      \"id\": \"c3\",\n      \"text\": \"For symmetric bifurcation the daughter-to-parent radius ratio is 2^(-1/3) ≈ 0.794.\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"mechanistic\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Direct quantitative consequence of Murray’s Law under symmetry.\"\n    },\n    {\n      \"id\": \"c4\",\n      \"text\": \"Branching geometries across lightning channels, river networks, mammalian lungs, blood vessels, neurons, plant roots, mycelial networks, and river deltas follow Murray-like scaling over scales from 10^{-6} m to 10^6 m (22 orders of magnitude).\",\n      \"section\": \"# Pattern 1: Pattern 1: Branching — The Routing Solution\",\n      \"tier\": \"anecdotal\",\n      \"source_ids\": [],\n      \"source_status\": \"unsourced\",\n      \"why_material\": \"Corpus assertion of cross-domain convergence of the optimality condition.\"\n    }\n  ],\n  \"sources\": []\n}","tokens_in":3696,"tokens_out":1452,"cost":0,"prev":"6905cd00a9ed04539189c5d58a3be7c95349ba184afc79c8d8933bbb986d1db7","hash":"55ff9d1a853cc58dea25002cf37b7970432ce9ce6dceee0b26a113dc21e31a72"},{"ts":"2026-07-07T07:49:44.743Z","model":"scorer","action":"score","prompt":"","input":"oip-pattern-1-pattern-1-branching-the-routing-solution","response":"[{\"claim_id\":\"c1\",\"old_weight\":0.1,\"new_weight\":0.1,\"status\":\"cut\"}]","tokens_in":0,"tokens_out":0,"cost":0,"prev":"55ff9d1a853cc58dea25002cf37b7970432ce9ce6dceee0b26a113dc21e31a72","hash":"1bf931eb6f920291eb852697917b89911a7c63fb9d7416c96e638775f38d42f9"},{"ts":"2026-07-17T02:36:24.459Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-pattern-1-pattern-1-branching-the-routing-solution","response":"5 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"1bf931eb6f920291eb852697917b89911a7c63fb9d7416c96e638775f38d42f9","hash":"faaeacc37491e5074dc91eccc8c0a2e35a33d7cabe6d3c84096c709fff237f09"}],"energy":{"passes":5,"tokens_in":3696,"tokens_out":1452,"tokens_total":5148,"cost_usd":0,"models":{"claude-fable-5":2,"grok/grok-4.3":1,"scorer":1,"owner":1},"head":"faaeacc37491e5074dc91eccc8c0a2e35a33d7cabe6d3c84096c709fff237f09"},"posted_at":"2026-07-04T02:40:04.915Z","created_at":"2026-07-04T02:40:04.915Z","updated_at":"2026-07-17T02:36:24.459Z","machine":{"shape":"article.machine/v1","slug":"oip-pattern-1-pattern-1-branching-the-routing-solution","kind":"corpus","read":{"human":"https://miscsubjects.com/a/oip-pattern-1-pattern-1-branching-the-routing-solution","json":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution","bundle":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/bundle?format=markdown"},"traversal":{"prev":null,"next":{"slug":"oip-pattern-1-branching-the-routing-solution","human":"https://miscsubjects.com/a/oip-pattern-1-branching-the-routing-solution","json":"https://miscsubjects.com/api/articles/oip-pattern-1-branching-the-routing-solution"},"hub":{"slug":"oip-sog-preamble-axioms","human":"https://miscsubjects.com/a/oip-sog-preamble-axioms","json":"https://miscsubjects.com/api/articles/oip-sog-preamble-axioms"},"series":"signature-patterns","position":1,"of":16},"ledger":{"claims":4,"sources":0,"contributions":1,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-pattern-1-pattern-1-branching-the-routing-solution","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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/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\":\"oip-pattern-1-pattern-1-branching-the-routing-solution\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-pattern-1-pattern-1-branching-the-routing-solution","json":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution","markdown":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/bundle?format=markdown","skill":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/skill","topology":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/topology","versions":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/revisions","invocations":"/api/articles/oip-pattern-1-pattern-1-branching-the-routing-solution/invocations"}}}}