feat(studio): /studio — publish the factory's record, and route the ledger to it - #25
Merged
Conversation
The `studios` monorepo carries the thickest technical description in the whole ledger and is invisible on the site: not featured, private so no repo link, no website, no screenshot. hasIndexablePage() therefore returns false and the thin-page filter drops it from the sitemap. The filter is right; the entry is all telling and no showing. This gives it something to show — but deliberately not a grid of generated images. In 2026 a wall of AI art proves nothing a subscription cannot buy, and reads as slop on a page adjacent to "hire me". What is not buyable is the factory: self-hosted models on one GPU, a machine gate, an agent that looks at the thumbnail and rules on it, and a verdict that lands in a database. So the page publishes the record rather than the picture. One real job laid open: four candidates, two approved, two rejected, with the model, asset id, seed, gate metrics and verdicts exactly as the studio wrote them. The two rejects ship with their reasons — a pipeline that only shows its hits is a gallery, not a pipeline. Every image is the review thumbnail the agent was actually handed, which is also the only thing the MCP layer hands back: the studio server runs on the other machine, so full-resolution assets never reach this repo. That constraint is what capped the walk at one modality; 3D and video both hit the 1800s idle timeout and their artifacts live on the laptop. The page says plainly that it opens one of five axes. The "already has a job" section closes it: the blog covers a reader has been looking at all along came from the same image-studio, the same krea2 model and the same verify_asset call (docs/media/hero-generation-report.md). Assets are hand-picked files committed under public/. Nothing here reads the studio library — no feed, no path import, no list_* call — because that library is private and a single automated pull would publish it. Not in the nav: it is already seven wide, and an eighth entry would undo last week's breakpoint fix. Discovery is the sitemap plus links from the project entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LaydoxAZ4eaqqPNKrmWLbt
/studio shipped with only one way in — the sitemap. The spec named three routes and built one, which leaves the page orphaned inside the site: a reader on /projects/studios, the one place someone goes looking for this work, had nowhere to go. PROJECT_SHOWCASE sits beside APP_CATEGORY for the same reason that map does: a slug conditional inlined in a page gets copied to the next call site and then the two disagree. The link renders first in the action row because for a private project with no website it is the only link on the page. It also un-thins the entry. hasIndexablePage exists to keep pages that are "a name, two lines of description and some tech chips — no image, nowhere to go" out of the sitemap, and `studios` was the clearest case: private, so the Private rule withholds its repo URL, and no public surface of any kind. That description stops being true once the page carries a link to a substantial page of its own, so the filter now counts a showcase the same way it counts a screenshot or a demo. /projects/studios is back in the sitemap on the merits rather than by exemption. The bare test fixture gained a slug chosen to have no showcase entry — with a real one it would satisfy the filter and every negative case would pass for the wrong reason. Verified by mutation: dropping the showcase clause, pointing it at a slug that does not exist, and swapping the fixture's slug each turn a distinct assertion red. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LaydoxAZ4eaqqPNKrmWLbt
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gives
studios— the thickest technical entry in the ledger and the least visible thing on the site — something to show, and a way in.Why not a gallery
The plan was an outputs gallery. A grid of generated images proves nothing a subscription cannot buy, and next to
/hireit reads as slop. What is not buyable is the factory: self-hosted models on one GPU, a machine gate, an agent that looks at the thumbnail and rules on it, a verdict that lands in SQLite.So the page publishes the record, not the picture. One real job laid open — four candidates, two approved, two rejected — with the model, asset id, seed, gate metrics and verdicts exactly as the studio wrote them. The two rejects ship with their reasons; a pipeline that only shows its hits is a gallery.
Every image is the review thumbnail the agent was actually handed. That is also the only artifact the MCP layer delivers to this machine — the studio server runs on the laptop, so full-resolution assets, GLB and MP4 never reach this repo. That constraint capped the walk at one modality, and the page says plainly that it opens one of five axes.
The closing section is the strongest claim on it: the blog covers a reader has been looking at all along came from the same image-studio, the same
krea2model, the sameverify_assetcall. Sourced indocs/media/hero-generation-report.md, gated bysrc/lib/hero-palette.ts.The second commit
/studioshipped with only the sitemap as a way in.PROJECT_SHOWCASEroutes/projects/studiosto it, andhasIndexablePagenow counts a showcase link the same way it counts a screenshot or a demo — "nowhere to go" stops being true when the page carries a link to a substantial page of its own./projects/studiosis back in the sitemap on the merits, not by exemption.Boundaries held
list_*. Assets are hand-picked files underpublic/.Project.screenshot; the type comment forbids it and the page labels its art as generated.studiosrepo URL — verified on the rendered page.md→lgbreakpoint fix.Verification
Type-check, lint, 169 tests, production build. Both locales 200, hreflang ko/en/x-default,
/studio+/en/studio+/projects/studiosin the sitemap, three.js absent from the page payload. New assertions mutation-tested — seven mutations, each turning a distinct assertion red.Not verified: narrow viewport, visually. Window resize did not reach the viewport; the grids use the same
sm:breakpoints as/hire.🤖 Generated with Claude Code
https://claude.ai/code/session_01LaydoxAZ4eaqqPNKrmWLbt