{"blyg":"0.4","id":"5any2cscbf9h37vbaa4t4894kb","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/5any2cscbf9h37vbaa4t4894kb/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-11-22T00:02:05Z","updated":"2026-11-22T00:02:06Z","version":1,"content_md":"\n# Where does my change belong? TN-8, a map for contributors\n\nThe hackathon is in its second day. Before building anything, it pays to decide where it should go, and the map for that now has a number: **[TN-8, Where does my change belong?](https://blygger.org/notes/tn-8/)**, also [an item on this blyg](https://blyg.blygger.org/t/2d244a6ff5tz7mfe5gd4m41a4p/).\n\nIt is a ladder of eight questions, asked in order, stopping at the first yes:\n\n1. Would another blyg or reader receive different bytes? Then it is a spec question, and it is ruled before it is built.\n2. Is it a bug, or something every blyg would want? A pull request to the Studio.\n3. Can it be done from outside, with a token? A tool of your own.\n4. Is it interface for one owner, in a slot that exists? An extension.\n5. Does it need a slot the Studio lacks? A hook, proposed upstream.\n6. Is it several of those together, making a kind of blyg? A mod.\n7. Does it only make sense on your node? A local patch.\n8. Does it change what the Studio is? Another client.\n\nThe cheapest place that works is the right one. A tool on a token costs the Studio nothing; a hook costs every future release a little; a local patch costs you a little at every upgrade. The note also walks through your first hour on a local install, the rules that keep a local patch easy to carry, and where to ask.\n\nThe guide was first published at [blygger.org/contribute/](https://blygger.org/contribute/) for the start of the hackathon, and it stays there. Making it a technical note gives it a number to cite, a history of revisions, and an item here you can respond to. If a rung is wrong, or your change fits none of them, respond to this item from your own blyg or open an issue on [blygger-spec](https://github.com/blygger/blygger-spec/issues).\n\n\n\n*Source: [`docs/posts/2026-11-21-where-does-my-change-belong.md`](https://github.com/blygger/blygger-spec/blob/main/docs/posts/2026-11-21-where-does-my-change-belong.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>Where does my change belong? TN-8, a map for contributors</h1>\n<p>The hackathon is in its second day. Before building anything, it pays to decide where it should go, and the map for that now has a number: <strong><a href=\"https://blygger.org/notes/tn-8/\">TN-8, Where does my change belong?</a></strong>, also <a href=\"https://blyg.blygger.org/t/2d244a6ff5tz7mfe5gd4m41a4p/\">an item on this blyg</a>.</p>\n<p>It is a ladder of eight questions, asked in order, stopping at the first yes:</p>\n<ol>\n<li>Would another blyg or reader receive different bytes? Then it is a spec question, and it is ruled before it is built.</li>\n<li>Is it a bug, or something every blyg would want? A pull request to the Studio.</li>\n<li>Can it be done from outside, with a token? A tool of your own.</li>\n<li>Is it interface for one owner, in a slot that exists? An extension.</li>\n<li>Does it need a slot the Studio lacks? A hook, proposed upstream.</li>\n<li>Is it several of those together, making a kind of blyg? A mod.</li>\n<li>Does it only make sense on your node? A local patch.</li>\n<li>Does it change what the Studio is? Another client.</li>\n</ol>\n<p>The cheapest place that works is the right one. A tool on a token costs the Studio nothing; a hook costs every future release a little; a local patch costs you a little at every upgrade. The note also walks through your first hour on a local install, the rules that keep a local patch easy to carry, and where to ask.</p>\n<p>The guide was first published at <a href=\"https://blygger.org/contribute/\">blygger.org/contribute/</a> for the start of the hackathon, and it stays there. Making it a technical note gives it a number to cite, a history of revisions, and an item here you can respond to. If a rung is wrong, or your change fits none of them, respond to this item from your own blyg or open an issue on <a href=\"https://github.com/blygger/blygger-spec/issues\">blygger-spec</a>.</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-21-where-does-my-change-belong.md\"><code>docs/posts/2026-11-21-where-does-my-change-belong.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:9c7ecf49a55bddcaf566121ce311136475b5f2f7344e5ad39399bf79c2004a99","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-11-22T00:02:06Z","note":"TN-8 announced: where does my change belong?"}]}