{"blyg":"0.4","id":"7rcy7n3rxn3mbh5nx6g1jdgndq","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/7rcy7n3rxn3mbh5nx6g1jdgndq/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-08T02:33:22Z","updated":"2026-11-08T02:44:14Z","version":1,"content_md":"\n# Changelog Rollup and Background Routing in Studio\n\nA blyg is a set of living documents, not a stream of posts. Items get revised, quotes get refreshed, threads get tightened over months. That is the point of the medium, and it creates a problem every reader of a busy blyg runs into sooner or later: most of the traffic a living document generates is necessary and trivial. A typo fixed. A quoted passage brought up to date with its source. A fragment published as part of a thread, a minute before the thread itself. Each of these is a new version, and each one shows up in a feed.\n\nTwo things have to be true at once. You should be able to keep up easily with the changes that matter in documents that keep changing. And the trivial traffic, which is most of it, should get out of your way, either handled automatically or routed by rules you set yourself. Blygger Studio's next two features are built around that pair: **changelog rollup**, which makes the history of a document readable at a glance, and **background routing**, which keeps the trivial versions out of your main reading view.\n\n## Changelog rollup\n\nEvery blyg item already carries its full changelog on the wire: each version's note, its time, and whether the author pinned it. Until now, Studio showed you only the latest note. That was the right default for a stream, and the wrong one for a document you return to after a month, when the question you have is not \"what changed last\" but \"how did this get to where it is now\".\n\nStudio 0.58.0 adds three ways to show a changelog, chosen separately for your own public item pages and for blyg items in your reader:\n\n- **The latest note**, as before.\n- **The full history**: every version's note, newest first, with pinned versions linked to their frozen pages.\n- **An AI summary**: a few sentences on how the piece has developed, written from the notes.\n\nA summary is written from the changelog's notes only, never from the text of earlier versions. That is a deliberate limit. The protocol never makes an unpinned earlier version reachable, and a summary written from those texts would be a back door to exactly what the author chose not to keep public. Notes are public by construction and already follow that rule, so a summary of them cannot leak anything. Summaries are labelled as machine-written, with the model named, and they stay in your studio: they never enter the item's document or your feed. Each one is written once per version and kept, so a page viewed a thousand times costs one model call, and your reader writes a summary only when you open an item.\n\nThere is a writing-side half too. When you draft a change note, you can now ask for one that **summarizes the full history to date**, ending with this version's change. For a document with a long life, that note becomes the running account readers see first. Settings has a place for your own instructions on how roll-ups should read.\n\n## Background routing\n\nRollup makes important changes legible. Routing makes unimportant ones quiet. Studio's reader already has a Background view, but today it holds only withdrawn items. An [earlier heads-up](https://blyg.blygger.org/t/2c494ntcyfgt5f2agqmb7vmsye/) said it would grow; the plan now widens it to everything a reader can reasonably treat as maintenance, and gives you the controls.\n\nThe automatic rules all work from what the reader can see for itself:\n\n- **Same text.** The item was republished without a word changed.\n- **Quotes refreshed.** A thread brought its quoted passages up to date with their sources and changed nothing of its own. This one is common in a medium built on quotation, and easy to detect: the item's content fingerprint covers the author's text and the quote markers, not the quoted versions, so it stays the same while the quotes move.\n- **A small edit.** The text changed by a few characters.\n- **No words of its own.** A post that is nothing but quotes.\n- **Superseded.** The same blyg published a newer item within a few minutes, so the earlier one is bumped sideways rather than left at the top.\n- **Part of a burst.** Fragments published together with the thread that names them fold into that thread, which shows \"+N fragments\".\n\nOn top of the rules, you can move any item, or a whole blyg, to the Background yourself, and move it back from there. Your choice on an item beats your choice on a blyg, and both beat the rules. Background never marks anything read and never changes what you publish; it is a view, not a verdict. Every item in it says why it is there.\n\n## Delegated authority\n\nThe interesting question was what to do with the author's own words about a change. A note that says \"minor typo fix\" is useful information. It is also an easy way to bury a rewrite, and the protocol has long said that no word in a note carries meaning on the wire, so that nobody can write to a convention that clients honour.\n\nThe answer the project settled on draws a line between a client deciding something on everyone's behalf and you deciding something for yourself. **Studio will not route on a note of its own accord, in either direction.** But you may tell it to. A standing instruction like \"if a changelog says minor, believe it; if there are signs of spam, flag it\" is your own reading, delegated to an agent, the way a mail filter acts on your rules. Nothing about it reaches the wire, and the author cannot know whether any reader honours the word, so no convention forms. The instruction starts empty, any item it routes says so, and you can change it at any time. When a note's claim and the measured change disagree, say the note says \"minor\" and half the text changed, the item stays in front of you with a flag saying why.\n\nThe same holds on the publishing side. What a note says is the author's own, including words a client writes on the author's instruction. Studio does not police it. If a feed misrepresents its changes, that is for its readers to answer by how they read it. The one thing that stays enforced is the rule that keeps unpinned history unreachable.\n\nAn opt-in setting will let a small decision model judge other blygs' changes from the two texts, for readers who want more than measurement. It costs one call per new version of anything you read, and Settings says so.\n\n## Where this stands\n\nChangelog rollup ships in Studio 0.58.0. Background routing is planned in four parts. The first part comes next and brings the controls, plus the change classifier's verdicts on your own items, so your own small fixes leave your reading view without any new model calls. The measured rules come second. The model, your routing instructions over notes, and the disagreement flag come third, once there is a measured change to check notes against. The burst folding that the planned inline-fragment authoring will need comes fourth.\n\nThe pace-layered home page order follows the same thinking and is now [an RFC open for comment](https://blyg.blygger.org/t/28cm3qgpz1fa146yjvac97ba7c/) until 10 December: a version that changed nothing worth resurfacing no longer climbs, and a burst counts as one publication. Both rules exist for the same reason: a document that keeps getting better should not have to be noisy about it.\n\n\n\n*Source: [`docs/posts/2026-11-07-changelog-rollup-and-background-routing.md`](https://github.com/blygger/blygger-spec/blob/main/docs/posts/2026-11-07-changelog-rollup-and-background-routing.md) in blygger-spec, which is where revisions are made. To comment, respond to this item from your own blyg.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Changelog Rollup and Background Routing in Studio</h1>\n<p>A blyg is a set of living documents, not a stream of posts. Items get revised, quotes get refreshed, threads get tightened over months. That is the point of the medium, and it creates a problem every reader of a busy blyg runs into sooner or later: most of the traffic a living document generates is necessary and trivial. A typo fixed. A quoted passage brought up to date with its source. A fragment published as part of a thread, a minute before the thread itself. Each of these is a new version, and each one shows up in a feed.</p>\n<p>Two things have to be true at once. You should be able to keep up easily with the changes that matter in documents that keep changing. And the trivial traffic, which is most of it, should get out of your way, either handled automatically or routed by rules you set yourself. Blygger Studio's next two features are built around that pair: <strong>changelog rollup</strong>, which makes the history of a document readable at a glance, and <strong>background routing</strong>, which keeps the trivial versions out of your main reading view.</p>\n<h2>Changelog rollup</h2>\n<p>Every blyg item already carries its full changelog on the wire: each version's note, its time, and whether the author pinned it. Until now, Studio showed you only the latest note. That was the right default for a stream, and the wrong one for a document you return to after a month, when the question you have is not &quot;what changed last&quot; but &quot;how did this get to where it is now&quot;.</p>\n<p>Studio 0.58.0 adds three ways to show a changelog, chosen separately for your own public item pages and for blyg items in your reader:</p>\n<ul>\n<li><strong>The latest note</strong>, as before.</li>\n<li><strong>The full history</strong>: every version's note, newest first, with pinned versions linked to their frozen pages.</li>\n<li><strong>An AI summary</strong>: a few sentences on how the piece has developed, written from the notes.</li>\n</ul>\n<p>A summary is written from the changelog's notes only, never from the text of earlier versions. That is a deliberate limit. The protocol never makes an unpinned earlier version reachable, and a summary written from those texts would be a back door to exactly what the author chose not to keep public. Notes are public by construction and already follow that rule, so a summary of them cannot leak anything. Summaries are labelled as machine-written, with the model named, and they stay in your studio: they never enter the item's document or your feed. Each one is written once per version and kept, so a page viewed a thousand times costs one model call, and your reader writes a summary only when you open an item.</p>\n<p>There is a writing-side half too. When you draft a change note, you can now ask for one that <strong>summarizes the full history to date</strong>, ending with this version's change. For a document with a long life, that note becomes the running account readers see first. Settings has a place for your own instructions on how roll-ups should read.</p>\n<h2>Background routing</h2>\n<p>Rollup makes important changes legible. Routing makes unimportant ones quiet. Studio's reader already has a Background view, but today it holds only withdrawn items. An <a href=\"https://blyg.blygger.org/t/2c494ntcyfgt5f2agqmb7vmsye/\">earlier heads-up</a> said it would grow; the plan now widens it to everything a reader can reasonably treat as maintenance, and gives you the controls.</p>\n<p>The automatic rules all work from what the reader can see for itself:</p>\n<ul>\n<li><strong>Same text.</strong> The item was republished without a word changed.</li>\n<li><strong>Quotes refreshed.</strong> A thread brought its quoted passages up to date with their sources and changed nothing of its own. This one is common in a medium built on quotation, and easy to detect: the item's content fingerprint covers the author's text and the quote markers, not the quoted versions, so it stays the same while the quotes move.</li>\n<li><strong>A small edit.</strong> The text changed by a few characters.</li>\n<li><strong>No words of its own.</strong> A post that is nothing but quotes.</li>\n<li><strong>Superseded.</strong> The same blyg published a newer item within a few minutes, so the earlier one is bumped sideways rather than left at the top.</li>\n<li><strong>Part of a burst.</strong> Fragments published together with the thread that names them fold into that thread, which shows &quot;+N fragments&quot;.</li>\n</ul>\n<p>On top of the rules, you can move any item, or a whole blyg, to the Background yourself, and move it back from there. Your choice on an item beats your choice on a blyg, and both beat the rules. Background never marks anything read and never changes what you publish; it is a view, not a verdict. Every item in it says why it is there.</p>\n<h2>Delegated authority</h2>\n<p>The interesting question was what to do with the author's own words about a change. A note that says &quot;minor typo fix&quot; is useful information. It is also an easy way to bury a rewrite, and the protocol has long said that no word in a note carries meaning on the wire, so that nobody can write to a convention that clients honour.</p>\n<p>The answer the project settled on draws a line between a client deciding something on everyone's behalf and you deciding something for yourself. <strong>Studio will not route on a note of its own accord, in either direction.</strong> But you may tell it to. A standing instruction like &quot;if a changelog says minor, believe it; if there are signs of spam, flag it&quot; is your own reading, delegated to an agent, the way a mail filter acts on your rules. Nothing about it reaches the wire, and the author cannot know whether any reader honours the word, so no convention forms. The instruction starts empty, any item it routes says so, and you can change it at any time. When a note's claim and the measured change disagree, say the note says &quot;minor&quot; and half the text changed, the item stays in front of you with a flag saying why.</p>\n<p>The same holds on the publishing side. What a note says is the author's own, including words a client writes on the author's instruction. Studio does not police it. If a feed misrepresents its changes, that is for its readers to answer by how they read it. The one thing that stays enforced is the rule that keeps unpinned history unreachable.</p>\n<p>An opt-in setting will let a small decision model judge other blygs' changes from the two texts, for readers who want more than measurement. It costs one call per new version of anything you read, and Settings says so.</p>\n<h2>Where this stands</h2>\n<p>Changelog rollup ships in Studio 0.58.0. Background routing is planned in four parts. The first part comes next and brings the controls, plus the change classifier's verdicts on your own items, so your own small fixes leave your reading view without any new model calls. The measured rules come second. The model, your routing instructions over notes, and the disagreement flag come third, once there is a measured change to check notes against. The burst folding that the planned inline-fragment authoring will need comes fourth.</p>\n<p>The pace-layered home page order follows the same thinking and is now <a href=\"https://blyg.blygger.org/t/28cm3qgpz1fa146yjvac97ba7c/\">an RFC open for comment</a> until 10 December: a version that changed nothing worth resurfacing no longer climbs, and a burst counts as one publication. Both rules exist for the same reason: a document that keeps getting better should not have to be noisy about it.</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-07-changelog-rollup-and-background-routing.md\"><code>docs/posts/2026-11-07-changelog-rollup-and-background-routing.md</code></a> in blygger-spec, which is where revisions are made. To comment, respond to this item from your own blyg.</em></p>\n</div>\n","content_hash":"sha256:bf75b6331c2ae3a9f5d853abc3d2c36a5ed8a30f34b7f8feb25ceb54905ec793","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-08T02:44:14Z","note":"An explainer for Studio 0.58.0 and the Background plan."}]}