Evidence review · oip_protocol

Convergence Encyclopedia: C16 — Branching / Optimal Transport

#OIP#convergence-encyclopedia#node
bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §SELF — miscsubjects (paste without context)

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `convergence-encyclopedia-c16`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/convergence-encyclopedia-c16

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/convergence-encyclopedia-c16/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **bundle** — Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/convergence-encyclopedia-c16/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/convergence-encyclopedia-c16/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/convergence-encyclopedia-c16/topology

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

F1 — Tier. T1 (Murray’s law for laminar flow; constructal law as engineering principle; Horton’s laws for geomorphology). CRITICAL NOTE: Murray’s law (r₀³=r₁³+r₂³), Horton’s laws, and Bejan’s constructal law are THREE DIFFERENT RESULTS. They apply to different systems under different constraints. Do not claim all branching instances share Murray scaling.

F2 — Sources.

  • Murray, C.D. (1926). “The physiological principle of minimum work. I. The vascular system and the cost of blood volume.” Proceedings of the National Academy of Sciences, 12(3), 207–214.
  • Bejan, A. (1996). “Constructal-theory network of conducting paths for cooling a heat generating volume.” International Journal of Heat and Mass Transfer, 40(4), 799–816. (Constructal law formalized.)
  • Bejan, A. (1997). Advanced Engineering Thermodynamics. Wiley. (Constructal law expanded.)
  • Horton, R.E. (1945). “Erosional development of streams and their drainage basins: Hydrophysical approach to quantitative morphology.” Bulletin of the Geological Society of America, 56(3), 275–370.
  • Hack, J.T. (1957). “Studies of longitudinal stream profiles in Virginia and Maryland.” U.S. Geological Survey Professional Papers, 294-B, 45–97.

F3 — Domains. Rivers (Horton/Hack), lungs and blood vessels (Murray), neurons (branching dendrites), roots and mycelium (resource foraging), lightning (dielectric breakdown), engineered networks (constructal).

F4 — Scale. Capillary (~10⁻⁶ m) → Amazon basin (~10⁶ m); ~12 orders for Murray-type networks.

F5 — Falsifier. A branching network for viscous fluid transport that violates Murray’s Law (r₀³ ≠ r₁³ + r₂³) under controlled laminar flow conditions, despite having evolved or been designed for efficient transport. More generally: a constructal-optimized network whose performance improves when its branching geometry deviates from constructal predictions. Rival (strongest form): Branching is geometric necessity under flow constraints, not evidence of a deep “grain” to reality. Murray’s cubic law holds for laminar viscous flow; it does not apply to turbulent flow, electrical conduction, or dielectric breakdown (lightning). Rivers follow Horton’s laws and Hack’s law (L ∝ A^0.6) with different exponents than biological networks. Lightning is fractal dielectric breakdown with no optimization principle. These are different phenomena with different mathematics. The convergence is superficial — they all look like trees because trees are the geometry of space-filling under flow. (Criticism of over-unified branching theories: LaBarbera 1990 Science 249:979; Bejan’s constructal law criticized as unfalsifiable by Ghodos- sian & Bejan 2017 Journal of Applied Physics rebuttal.)

F7 — Independence. HIGH. Murray (physiology, Penn State, 1926), Bejan (mechanical engineering, Duke, 1996), Horton (geology, 1945) — three fields, three countries, three decades (1920s–1990s), no intellectual borrowing. The commonality of branching geometry was recognized only retrospectively.

F8 — Pattern type. Structural / mathematical.

F9 — Maps. A2 (thermodynamic/computational), A7 (pattern geometry).

---

Corpus map

convergence-encyclopedia-c16 · condition map

Evidence map

Hover a node — its path lights up. Click to open the article.

Full map →
Talk to this article
Tap a phone. Ask anything about Convergence Encyclopedia: C16 — Branching / Optimal Transport. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.
Ask this article · 2 suggested prompts

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

For my medical situation, what can you answer from your catalogue about Convergence Encyclopedia: C16 — Branching / Optimal Transport — and what would you need me to tell you first?
ask convergence-encyclopedia-c16 condition gaps · paste includes §SELF
What good and bad outcomes are documented for Convergence Encyclopedia: C16 — Branching / Optimal Transport (studies vs anecdotes)?
ask convergence-encyclopedia-c16 good bad experiences · paste includes §SELF
Add your experience or question
Think this article is wrong?
Call bullshit on CharlieOS →
Loading more articles…