{"blyg":"0.4","id":"4v95yj8rr1ym5gzwpsdzb9w5na","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/4v95yj8rr1ym5gzwpsdzb9w5na/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-10-10T23:08:37Z","updated":"2026-10-10T23:08:38Z","version":1,"content_md":"\n# Blygger Studio 0.41.0\n\n*Released 2026-10-10, the reference client. [v0.41.0 on GitHub](https://github.com/blygger/blygger-studio/releases/tag/v0.41.0).*\n\n**Migrations: `0027_imported_generated.sql`** (`imported_items.generated_json`,\nand the imported-items change trigger recreated to watch it). Apply it before\ndeploying: `wrangler d1 migrations apply <database> --remote`.\n\n**Protocol: the version key is now `\"0.4\"`** in the manifest, item documents\nand pinned files. This build implements remote generation sources (spec 0.3\n§16.3, decision #44), the first construct a receiver must act on to be correct;\nit is the build that opens the 0.4 document. Readers accept any 0.x value, so\nnothing that reads a blyg changes. A pinned file's content is unchanged; its\n`blyg` key reports what the serving deployment implements, as at 0.3.\n\n- **A TK scope can draw on any item a quote can name** (#44). Sources\n  resolve like a directive: your published items of either kind, then an\n  imported item that is current or withdrawn with a pinned snapshot kept.\n  Threads and other blygs' items are sources now; drafts, plain RSS (L0) items\n  and an id imported from two origins are refused by name. The generator reads\n  the local snapshot, never a live fetch: a fragment's text, or a thread as its\n  readers see it, quotes included.\n- **A remote source is disclosed and notifies.** Its `generated[].sources[]`\n  entry carries `origin` and a `cited` frozen when the scope was generated, and\n  publishing sends that blyg a mention. A receiver running this build verifies\n  it as the new relation **`source`** and lists it publicly as \"drew on this\";\n  a 0.3 receiver reports it failed, which is correct for 0.3. An item that both\n  quotes and draws on the same post sends one mention.\n- **Imports keep `generated`** verbatim (migration 0027): on\n  `GET /api/imports/{sub}/{id}` as `generated_json`, and on\n  `GET /api/reading/imported` as `generated`.\n- **Studio.** Typing `![[` in a scope's instruction, inline or on its own line,\n  opens the picker as a *source* picker. The TK panel lists each scope's\n  sources, \"draws on Friend's Blyg · excerpt · its author is told\", or why one\n  would be refused, before you generate. The public \"AI-generated\" box lists\n  remote sources by their citation. The syntax page is updated, including\n  decision #60's rule that only the instruction names sources.\n- **API:** `relation` on mentions may be `source`; preview scopes carry\n  `sources`; `GenerationSource` (`id`, `version`, `origin?`, `cited?`) types\n  `generated[].sources[]`.\n- The lineage-glyph extension ignores `source` mentions for now.\n\n\n\n*This announcement is drafted from the release's section of [`CHANGELOG.md`](https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md), which is where it is maintained. To comment, respond to this item from your own blyg.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Blygger Studio 0.41.0</h1>\n<p><em>Released 2026-10-10, the reference client. <a href=\"https://github.com/blygger/blygger-studio/releases/tag/v0.41.0\">v0.41.0 on GitHub</a>.</em></p>\n<p><strong>Migrations: <code>0027_imported_generated.sql</code></strong> (<code>imported_items.generated_json</code>,\nand the imported-items change trigger recreated to watch it). Apply it before\ndeploying: <code>wrangler d1 migrations apply &lt;database&gt; --remote</code>.</p>\n<p><strong>Protocol: the version key is now <code>&quot;0.4&quot;</code></strong> in the manifest, item documents\nand pinned files. This build implements remote generation sources (spec 0.3\n§16.3, decision #44), the first construct a receiver must act on to be correct;\nit is the build that opens the 0.4 document. Readers accept any 0.x value, so\nnothing that reads a blyg changes. A pinned file's content is unchanged; its\n<code>blyg</code> key reports what the serving deployment implements, as at 0.3.</p>\n<ul>\n<li><strong>A TK scope can draw on any item a quote can name</strong> (#44). Sources\nresolve like a directive: your published items of either kind, then an\nimported item that is current or withdrawn with a pinned snapshot kept.\nThreads and other blygs' items are sources now; drafts, plain RSS (L0) items\nand an id imported from two origins are refused by name. The generator reads\nthe local snapshot, never a live fetch: a fragment's text, or a thread as its\nreaders see it, quotes included.</li>\n<li><strong>A remote source is disclosed and notifies.</strong> Its <code>generated[].sources[]</code>\nentry carries <code>origin</code> and a <code>cited</code> frozen when the scope was generated, and\npublishing sends that blyg a mention. A receiver running this build verifies\nit as the new relation <strong><code>source</code></strong> and lists it publicly as &quot;drew on this&quot;;\na 0.3 receiver reports it failed, which is correct for 0.3. An item that both\nquotes and draws on the same post sends one mention.</li>\n<li><strong>Imports keep <code>generated</code></strong> verbatim (migration 0027): on\n<code>GET /api/imports/{sub}/{id}</code> as <code>generated_json</code>, and on\n<code>GET /api/reading/imported</code> as <code>generated</code>.</li>\n<li><strong>Studio.</strong> Typing <code>![[</code> in a scope's instruction, inline or on its own line,\nopens the picker as a <em>source</em> picker. The TK panel lists each scope's\nsources, &quot;draws on Friend's Blyg · excerpt · its author is told&quot;, or why one\nwould be refused, before you generate. The public &quot;AI-generated&quot; box lists\nremote sources by their citation. The syntax page is updated, including\ndecision #60's rule that only the instruction names sources.</li>\n<li><strong>API:</strong> <code>relation</code> on mentions may be <code>source</code>; preview scopes carry\n<code>sources</code>; <code>GenerationSource</code> (<code>id</code>, <code>version</code>, <code>origin?</code>, <code>cited?</code>) types\n<code>generated[].sources[]</code>.</li>\n<li>The lineage-glyph extension ignores <code>source</code> mentions for now.</li>\n</ul>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>This announcement is drafted from the release's section of <a href=\"https://github.com/blygger/blygger-studio/blob/main/CHANGELOG.md\"><code>CHANGELOG.md</code></a>, which is where it is maintained. To comment, respond to this item from your own blyg.</em></p>\n</div>\n","content_hash":"sha256:331cc5c849b0f59c97919390835c1bf18271ee929abb7fb741895c4bfb121999","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-10-10T23:08:38Z","note":"Studio 0.41.0 released."}]}