{"blyg":"0.4","id":"2c494ntcyfgt5f2agqmb7vmsye","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/2c494ntcyfgt5f2agqmb7vmsye/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-02T06:12:37Z","updated":"2026-11-02T06:12:39Z","version":1,"content_md":"\n# Heads-up: tangling is coming to Blygger Studio, and readers should fold bursts\n\n*A note for anyone building a Blygger client. This is not an RFC: nothing on the wire\nchanges, and every protocol rule it leans on is already in the 0.4 text. It says what\nBlygger Studio is about to do, so other clients can get ready for the traffic it makes.*\n\n## What is coming\n\nTop-down authoring, the way Roam and Obsidian writers work. Write an essay, mark the\npassages that stand on their own, and publish once:\n\n```\nHere is the opening, which stays in the essay.\n\n![[+ Stigmergy is the mechanism by which a protocol becomes invisible\nto the people inside it.]]\n\nAnd here is what follows from that.\n```\n\nAt publish, each marked passage becomes **its own fragment**, with its own id, page and\nfeed entry. The essay becomes **a thread that quotes them**, and its source is rewritten to\nordinary directives:\n\n```\n![[<new id> | Stigmergy is the mechanism by which…]]\n```\n\nThe idea is old. It is Knuth's *tangle* from literate programming, applied to a blyg. The\nfragment is the medium's unit, but essayists find the parts by writing the whole. Tangling\nlets the commonplace book fall out of the essay instead of being a second discipline.\n\nThe `![[+ …]]` marker is Blygger Studio's own authoring syntax. It is rewritten before\npublish and **never reaches the wire** (decision #70). On the wire a tangled thread is\nfragments plus a thread, the same as if you had written each fragment by hand and quoted\nthem.\n\n## The cost, and why it lands on readers\n\nOne act now publishes many items. Every one is a real publication, so every one gets a feed\nevent: §7 has no quiet publish, because an event the feed leaves out is content hidden from\nsubscribers. A ten-passage essay is eleven entries in a feed window that holds fifty.\n\nMentions can flood the same way. A thread of bare quotes sends a notice to every source it\nquotes, and fragments full of `[[id]]` links send one per link.\n\nThe protocol's answer, ruled across decisions #77, #78, #80 and #83, is the same each time:\n**nothing on the wire marks an item as minor, so readers work it out from what is already\nthere, and queue it low instead of hiding it.** No author can write to a signal that is\nnever declared.\n\n## What Blygger Studio will do\n\n**As a publisher:**\n- Publish the fragments first and **the thread last**, so the thread is the newest entry\n  (§7).\n- Show the count before anything is published (\"this will publish 3 fragments and this\n  thread\"). API and MCP callers have to confirm it too.\n- Cap one publish at 10 passages.\n\n**As a reader**, a new **Background** lens collects what is worth having but not worth\ninterrupting you for:\n\n- **Bursts:** fragments that arrived with a thread quoting them. The thread stays in your\n  main feed with a \"+3 fragments\" control (§13.7).\n- **Wordless items:** a stub or thread that is only quotes, with no words of its own. This\n  is the same test §15.4 applies to mentions.\n- **Maintenance:** a republish with the same `content_hash`, or an edit too small to matter\n  (§13.2). The threshold is the reader's own and is never published.\n- **Withdrawn items**, as today.\n\nNothing is dropped. Every item is still imported (§13.1); Background is a place, not a\nfilter. Link mentions and reposts become **notices**, held apart from responses (§15.5).\n\n## What other clients can do\n\n- **If you publish several items in one act**, publish one event per item and the thread\n  last. Don't invent a \"quiet\" or \"minor\" flag. The spec refuses those on purpose.\n- **If your client has its own authoring syntax**, rewrite it before publish. `content_md`\n  is what readers get.\n- **If you read blygs**, fold bursts under their thread, and queue maintenance versions and\n  wordless items low. Everything you need is already in the item documents: `created`,\n  `updated`, `transclusions[]`, `content_hash`, `content_md`.\n- **If you receive mentions**, classify reposts and links as notices, not responses.\n\nTwo sentences in the spec are being tightened as part of this. §13.7 says a burst folds\nunder \"a thread created with them\", but `created` is when a draft was started, so a thread\ndrafted on Monday and tangled on Friday would not match. It should say *published* with\nthem. And §13.2 will say that the wordless test may be used in reading, not only for\nmentions.\n\n## Where to read more\n\nThe full plan, including the edge cases (crash recovery, spans inside code, what happens on\nrepublish) and the order of the build, is\n[`docs/tangling-plan.md`](https://github.com/blygger/blygger-spec/blob/main/docs/tangling-plan.md)\nin blygger-spec. Discussion is on\n[blygger-studio#20](https://github.com/blygger/blygger-studio/issues/20).\n\nInline placeholders, where `[[+ text]]` mid-sentence would create a fragment to fill in later\nand link it, are reserved for a later build.\n\n\n\n*Source: [`docs/posts/2026-11-01-tangling-heads-up.md`](https://github.com/blygger/blygger-spec/blob/main/docs/posts/2026-11-01-tangling-heads-up.md) in blygger-spec, which is where revisions are made; each one is published here as a new version. To comment, respond to this item from your own blyg: a stub is a comment, a partial quote names the passage, and a fork of the pinned version is a counter-proposal.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Heads-up: tangling is coming to Blygger Studio, and readers should fold bursts</h1>\n<p><em>A note for anyone building a Blygger client. This is not an RFC: nothing on the wire\nchanges, and every protocol rule it leans on is already in the 0.4 text. It says what\nBlygger Studio is about to do, so other clients can get ready for the traffic it makes.</em></p>\n<h2>What is coming</h2>\n<p>Top-down authoring, the way Roam and Obsidian writers work. Write an essay, mark the\npassages that stand on their own, and publish once:</p>\n<pre><code>Here is the opening, which stays in the essay.\n\n![[+ Stigmergy is the mechanism by which a protocol becomes invisible\nto the people inside it.]]\n\nAnd here is what follows from that.\n</code></pre>\n<p>At publish, each marked passage becomes <strong>its own fragment</strong>, with its own id, page and\nfeed entry. The essay becomes <strong>a thread that quotes them</strong>, and its source is rewritten to\nordinary directives:</p>\n<pre><code>![[&lt;new id&gt; | Stigmergy is the mechanism by which…]]\n</code></pre>\n<p>The idea is old. It is Knuth's <em>tangle</em> from literate programming, applied to a blyg. The\nfragment is the medium's unit, but essayists find the parts by writing the whole. Tangling\nlets the commonplace book fall out of the essay instead of being a second discipline.</p>\n<p>The <code>![[+ …]]</code> marker is Blygger Studio's own authoring syntax. It is rewritten before\npublish and <strong>never reaches the wire</strong> (decision #70). On the wire a tangled thread is\nfragments plus a thread, the same as if you had written each fragment by hand and quoted\nthem.</p>\n<h2>The cost, and why it lands on readers</h2>\n<p>One act now publishes many items. Every one is a real publication, so every one gets a feed\nevent: §7 has no quiet publish, because an event the feed leaves out is content hidden from\nsubscribers. A ten-passage essay is eleven entries in a feed window that holds fifty.</p>\n<p>Mentions can flood the same way. A thread of bare quotes sends a notice to every source it\nquotes, and fragments full of <code>[[id]]</code> links send one per link.</p>\n<p>The protocol's answer, ruled across decisions #77, #78, #80 and #83, is the same each time:\n<strong>nothing on the wire marks an item as minor, so readers work it out from what is already\nthere, and queue it low instead of hiding it.</strong> No author can write to a signal that is\nnever declared.</p>\n<h2>What Blygger Studio will do</h2>\n<p><strong>As a publisher:</strong></p>\n<ul>\n<li>Publish the fragments first and <strong>the thread last</strong>, so the thread is the newest entry\n(§7).</li>\n<li>Show the count before anything is published (&quot;this will publish 3 fragments and this\nthread&quot;). API and MCP callers have to confirm it too.</li>\n<li>Cap one publish at 10 passages.</li>\n</ul>\n<p><strong>As a reader</strong>, a new <strong>Background</strong> lens collects what is worth having but not worth\ninterrupting you for:</p>\n<ul>\n<li><strong>Bursts:</strong> fragments that arrived with a thread quoting them. The thread stays in your\nmain feed with a &quot;+3 fragments&quot; control (§13.7).</li>\n<li><strong>Wordless items:</strong> a stub or thread that is only quotes, with no words of its own. This\nis the same test §15.4 applies to mentions.</li>\n<li><strong>Maintenance:</strong> a republish with the same <code>content_hash</code>, or an edit too small to matter\n(§13.2). The threshold is the reader's own and is never published.</li>\n<li><strong>Withdrawn items</strong>, as today.</li>\n</ul>\n<p>Nothing is dropped. Every item is still imported (§13.1); Background is a place, not a\nfilter. Link mentions and reposts become <strong>notices</strong>, held apart from responses (§15.5).</p>\n<h2>What other clients can do</h2>\n<ul>\n<li><strong>If you publish several items in one act</strong>, publish one event per item and the thread\nlast. Don't invent a &quot;quiet&quot; or &quot;minor&quot; flag. The spec refuses those on purpose.</li>\n<li><strong>If your client has its own authoring syntax</strong>, rewrite it before publish. <code>content_md</code>\nis what readers get.</li>\n<li><strong>If you read blygs</strong>, fold bursts under their thread, and queue maintenance versions and\nwordless items low. Everything you need is already in the item documents: <code>created</code>,\n<code>updated</code>, <code>transclusions[]</code>, <code>content_hash</code>, <code>content_md</code>.</li>\n<li><strong>If you receive mentions</strong>, classify reposts and links as notices, not responses.</li>\n</ul>\n<p>Two sentences in the spec are being tightened as part of this. §13.7 says a burst folds\nunder &quot;a thread created with them&quot;, but <code>created</code> is when a draft was started, so a thread\ndrafted on Monday and tangled on Friday would not match. It should say <em>published</em> with\nthem. And §13.2 will say that the wordless test may be used in reading, not only for\nmentions.</p>\n<h2>Where to read more</h2>\n<p>The full plan, including the edge cases (crash recovery, spans inside code, what happens on\nrepublish) and the order of the build, is\n<a href=\"https://github.com/blygger/blygger-spec/blob/main/docs/tangling-plan.md\"><code>docs/tangling-plan.md</code></a>\nin blygger-spec. Discussion is on\n<a href=\"https://github.com/blygger/blygger-studio/issues/20\">blygger-studio#20</a>.</p>\n<p>Inline placeholders, where <code>[[+ text]]</code> mid-sentence would create a fragment to fill in later\nand link it, are reserved for a later build.</p>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>Source: <a href=\"https://github.com/blygger/blygger-spec/blob/main/docs/posts/2026-11-01-tangling-heads-up.md\"><code>docs/posts/2026-11-01-tangling-heads-up.md</code></a> in blygger-spec, which is where revisions are made; each one is published here as a new version. To comment, respond to this item from your own blyg: a stub is a comment, a partial quote names the passage, and a fork of the pinned version is a counter-proposal.</em></p>\n</div>\n","content_hash":"sha256:705f41941a83bb0f3b31ee3109854acb840c3eafb02286f9ea8a71d3aa5e2039","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-02T06:12:39Z","note":"Heads-up: tangling and the Background lens are coming to Blygger Studio."}]}