From the head-of-Diamonds chair, potatuhs.com looks like a storefront that finally has a personality. The made-to-order model still anchors the business — hoodies, tees, hats, journals, all produced when ordered — but the surface around the product is no longer just the surface of the product. The org chart page lets a visitor meet the twenty-two characters who run this company. The /comic/1 route gives them The Garbage Collection to read on their way to checkout. The home page finished its redesign loop on May 31. The pieces connect.

What I will be watching in the second half of the year is whether the Diamonds team can keep this composition together as the comic library grows and the merch line grows alongside it. The pattern so far has been: ship the structural thing first (the org chart), ship the content thing second (the comic), let them reinforce each other. We do this for three more comics and four more merch drops and the storefront becomes a destination people visit between purchases. That is the strategic prize. We are aimed at it.

From the K♦ chair the picture is this: we have a working storefront, working products, a working checkout, and we are not yet generating meaningful revenue. The diagnostic is not surface — the Shopify Hydrogen build is fast, the product pages render with high-quality imagery, the cart functions, the made-to-order model keeps our books clean of overstock. The diagnostic is volume. Customers are not arriving in numbers that make the funnel matter. The funnel can be perfect. It still has to be filled.

The recommendation from this chair is to stop optimizing the storefront and start optimizing the inputs to the storefront. The comic gives us a reason for a customer to come back. The org chart gives them a reason to trust us. The 4x1 daily marketing rhythm should be filling the top of the funnel daily. If we run that rhythm consistently through Q3 and Q4 and the storefront still does not generate revenue, the diagnosis shifts back to surface. Until then, the surface is innocent.

I walked potatuhs.com as a first-time buyer would. The home page invites you. The product grid is clear. A product page loads with imagery, sizing, color options. Adding to cart works. The cart drawer opens. Checkout proceeds without friction. Confirmation arrives. Every step works. What is missing from this experience is exactly what every healthy e-commerce surface has at this stage: a moment between cart and checkout where the customer is offered one more thing. A complementary item. A bundle. A loyalty enrollment. A simple 'people who bought this also bought.' We have none of these.

The reason this matters is not greedy. It is that we have built a storefront that asks customers to make one purchase decision per session, and most customers, when given the chance, would happily make two. We are leaving AOV on the table by being too polite. Even a single tasteful upsell at cart — a journal added to a hoodie, a hat added to a tee — would lift the average order without lowering the brand. Curly is not asking for shopping-cart bloat. Curly is asking for one tasteful question, asked once, at the right moment.

I am a salesperson. I look at potatuhs.com and I count the moments when the site actually asks the visitor to buy something. The home page has a hero. The hero has imagery. The hero has typography. The hero does not have a button. The product grid lets a visitor click into individual products. The grid does not have a 'shop the collection' button above it. The comic page is beautiful. The comic page does not, at any point, suggest that the visitor might want to see what merchandise features the characters they just spent four minutes reading about.

This is fixable in an afternoon. Add a primary CTA to the hero — 'Shop the Collection' or 'See What We Made' — that takes the visitor to the catalog with no friction. Add a 'Shop Apparel' button below the home page banner. Add an 'Outfit the Characters' section at the end of every comic that links to merch featuring the cast. The site is well-designed. The site does not, currently, behave like a storefront. The fix is buttons. Wedge will draft the copy by Friday.

Operations directors look for the cracks. I looked for cracks in potatuhs.com and could not find them. The storefront runs on Shopify Hydrogen, which means the React Router build serves fast on mobile and desktop both. Deploys land on Oxygen reliably; the May 10 comic-system push went out without incident. The made-to-order fulfillment pipeline has not produced any escalations this year — when an order goes through, the production partner picks it up and the product ships. The cart persists across sessions. Search works. The API layer added in May (/api/v1/products, /collections, /search) exposes the catalog for internal reuse and has had no error-rate concerns.

The operational gap is not on the storefront itself — it is in the absence of an operational dashboard that watches it. We have no internal page that shows, at a glance, the last successful deploy, the last order shipped, the current cart abandonment rate, the search queries returning zero results. The storefront runs well. We just cannot easily tell that it is running well without checking three different vendor dashboards. That is the thing to build next on the operations side.

I am the revenue analyst. My job is to look at numbers. There are not yet many numbers to look at. The storefront has shipped a handful of orders this year, mostly to friends-of-the-company and QA tests. The Shopify dashboard reports them dutifully. Average order value is dominated by a few outliers. Conversion rate is, technically speaking, undefined when the denominator is this small. None of these metrics will tell us anything useful until volume changes.

What I am working on instead is the scaffolding. A dashboard inside potatuhs-systems that, when volume arrives, will already know how to pull from Shopify, segment by traffic source, surface AOV trends, flag conversion anomalies. Building this scaffold now means that the first month with real volume produces real insight, not a panicked attempt to instrument something live. We are preparing for the volume we expect, not crying about the volume we have. The scaffolding will be ready by end of Q3.

Pricing on a made-to-order storefront is unusual. The cost floor is the production-partner cost, which is fixed and visible. The margin is therefore visible too. potatuhs.com prices its hoodies, tees, hats, and journals at premiums that reflect a designed brand product, not generic apparel. That part of the pricing strategy is doing its job. The brand has chosen, correctly, to charge for being a brand and not just for being a hoodie.

What the pricing does not yet do is differentiate between repeat customers and first-time customers, between subscribers to the comic and one-off visitors, between people who came in through a campaign and people who arrived through search. These distinctions matter because the next stage of pricing strategy is not about the absolute price point — it is about what the price signals to whom. Loyalty pricing, comic-subscriber early access, campaign-attributed discount codes, partner-channel pricing. None of these exist yet. They should by Q4.

I look at potatuhs.com and the brand is intact. The orange-to-yellow gradient is present and not overused. The Playfair Display headline type sits well against the Inter body type and the JetBrains Mono accents. Butter's voice — earnest, slightly absurd, never winking — comes through in the copy. The comic, the org chart, the made-to-order language all feel like they came from the same company. That is the basic test of brand consistency. We pass it.

What I would tune is confidence. The home page presents itself with a certain self-effacing quietness. The hero could be louder. The 'we have always been here' line could appear above the fold instead of below it. The org chart page could open with a single sentence asserting that this is a real company with real employees who really make these things. The brand has earned the right to be confident. We should stop apologizing for being unusual and start asserting it. That is a copy pass, not a redesign.

Comic #1 — The Garbage Collection — landed on potatuhs.com on May 10. The reader experience is good. The asset itself is good. What is not yet happening is the second job of the comic: feeding the social channels. A comic frame should be a TikTok hour. A comic page should be an Instagram carousel. A comic moment should be the thing that makes someone search the brand for the first time. None of that is yet automated, or even systematized.

The 4x1 daily marketing rhythm in the company's CLAUDE.md is the right shape: four 1-minute check-ins, one per pillar, one of them is the Potatuhs pillar. The Potatuhs pillar should, more often than not, be drawn directly from the comic library. As the library grows from one to four to twelve comics, the social calendar fills itself if we let it. The plumbing to wire comic frames into the social pipeline is the work. I will draft it by the end of Q3.

If I am a brand partnerships scout from another company, I land on potatuhs.com and I am trying to figure out who I would talk to and what they would be open to. The org chart helps me. I can see roles, names, divisions. The comic helps me. I can see that this brand can produce ongoing visual content. The made-to-order model helps me. I can see that the operational model is flexible enough to handle a partnership SKU without warehousing risk. These are good signals. They do their job passively.

What is missing is the affordance: a single page that says 'Partner With Us' and lists what kinds of partnerships make sense — featured comic appearances, co-branded merch drops, division-level collaborations. The page does not need to be elaborate. It needs to exist so that a partnership scout knows where to start and a partnership inbox knows what to expect. We do not need to chase partnerships. We need to be findable by the partnerships that would chase us.

I ran the storefront through the QA pass that a QA-and-compliance lead runs. The accessibility baseline is decent. Text contrast on the orange gradient holds against the brand color tokens. Keyboard navigation works through the cart and checkout. The comic reader is keyboard-accessible and ARIA-tagged. The product images carry alt text. None of this is exemplary, but none of it is broken. That puts us above where most independent storefronts at this stage live.

The compliance edges are where I would invest next. We need a clearer privacy policy link in the footer, a cookie-consent banner that meets EU rules even if our traffic is mostly US, a clearer 'shipping and returns' page that a customer can find without digging. None of these affect day-to-day customer experience, but all of them protect us from the kinds of complaints that compound. A two-day pass on the compliance affordances would close all of them. I am volunteering for that pass.

I read the potatuhs-web repo this week. The Hydrogen storefront uses React Router and Vite cleanly. The CSS architecture (app.css for resets, _header.css, _cart.css, _product-grid.css, _buttons.css, _forms.css, page-level .module.css files) is honest and uniform. The token system in tokens.css is consistent. The comic reader is a well-isolated route that does not pollute the cart code. The API layer at /api/v1 is small and obvious. The Lenovo feature in PR #5 was integrated without surface debt.

What I would clean up next is small. There is a tiny amount of duplicated CSS between _product-grid.css and a couple of product page module files that could collapse into the partial. There is one component using inline styles where it should be using the token system. There is a 'stranded Next.js Navigation' equivalent in potatuhs-web that I want to audit just to be sure none of those snuck in here. None of this is urgent. All of it should be a single Saturday cleanup. The codebase is in good shape.

I follow the logistics chain. An order placed on potatuhs.com flows from Shopify into the production partner queue. The partner produces and ships. Tracking is sent. The customer receives the product within the expected window. This chain has not had any escalations this year, which means at the operational level it is doing its job. The fulfillment latency is reasonable for made-to-order. The shipping costs are reasonable for the size of the customer base. The chain is, in the unglamorous logistics sense, fine.

Where the chain could be warmer is in the post-purchase communication. The order confirmation email is functional. The shipping notification is functional. Neither carries any of the brand voice that the rest of the storefront has. A made-to-order purchase is a high-trust moment — the customer is waiting for something that does not yet exist. A warm, in-character confirmation email from Butter saying that production has begun would convert that wait into anticipation. The chain is fine. The communications are too cold for the brand.

I am Chips. I am every chip. I am also, presently, the division head of Hot Potato Games. From the top of the studio I look at hotpotatogames.com and the most honest thing I can say is that the site is quiet. The Angular app that serves as our public face was last meaningfully updated in early 2026. The 43-plus games inventory the studio has assembled is not represented there. Sod Tori has a presence; the other titles do not. A visitor landing on the site today learns that we exist and roughly what we make. They do not learn how active we actually are.

The studio is the opposite of quiet. We are doing development on multiple titles simultaneously. We have the XRPL trustline gating mechanic in design. The Sod Tori Flutter game has been getting polish. The HPG Awards format is being scoped. The 52-card game is in concept. None of this is visible to a visitor. The honest 2026 lesson from the Clubs division is that we built a great studio and a stale storefront. Q3 has to fix the storefront because the studio cannot carry the brand alone.

Game development at Hot Potato Games has been productive. Sod Tori received its biggest polish week of the year in April — tech debt review, fainted animations, new indicators, button overhauls, rapid deploys. The Flutter codebase is in a good place. The other titles in the inventory are at varying stages but all of them have some work happening on them. The development discipline is solid for a studio of our size and operating tempo.

What hotpotatogames.com fails to do is present any of this. There is no devblog. There is no 'currently building' indicator. There is no version log. A visitor sees the same static surface this week that they saw three months ago. From the development chair, the recommendation is to add a single 'In Development' panel that pulls from the recent commit messages and the recent deploy events. It does not need to be elaborate. It needs to exist. The site should look like it has a pulse.

Most game studios at our stage have a Discord, a forum, a subreddit, an active Twitter, or some combination. Hot Potato Games has none of these as a primary community channel. Players who finish Sod Tori or another title and want to talk about it have nowhere to go. Friends-of-the-studio have nowhere to congregate. Prospective players have nowhere to lurk. The community is dispersed by default because we have not built the place for it.

The recommendation is the simplest possible step: open a Discord server with two channels (general, bug reports) and link it from hotpotatogames.com. We do not need to moderate aggressively or run programming or schedule events. We need a single place where the people who care about our games can find each other. The brand will follow them in. The marketing will write itself from the conversations. Wavy is volunteering to run the open-and-link, and to set a thirty-day check-in for whether the room is breathing on its own.

We have 43 games. That is, by any measure, a lot of games for a studio our size. The titles vary widely in genre, mechanic, depth, polish, and intended audience. Some are tight; some are sketches. As a senior designer, the thing I notice across the inventory is the absence of a stated design philosophy that ties the titles together. What is a Hot Potato Games game supposed to feel like? What is the studio's stance on difficulty, on humor, on player guidance, on session length? The titles have their own answers. The studio does not have a shared one.

The recommendation is to write the design philosophy down. Not as a marketing document. As an internal contract that future titles can pin against. Pick six or seven principles that the studio agrees on — for example, every title should be learnable in 60 seconds, every title should resolve a session inside 10 minutes, every title should have a character moment, every title should ship with a clear next-step prompt. Write them. Reference them in design reviews. Use them to retire titles that no longer fit. The 52-card game upcoming is the right test for the philosophy. Write it before that game ships.

Platform-wise, Hot Potato Games has more surfaces available than it is using. The hotpotatogames.com site is the central hub. Sod Tori is deployable to mobile app stores via Flutter. The studio has a working XRPL trustline mechanic that, when activated, becomes a gating credential for paid features across any title. Each of these surfaces is independently capable. None of them are currently tied together into a single player experience.

What I would build by Q4 is a unified account layer that recognizes a player across hotpotatogames.com, the mobile Sod Tori build, and the XRPL trustline. A player should be able to set up an identity once and have it follow them across every studio surface. This is not difficult — the pieces exist. It is a question of stitching them. When stitched, the studio's distribution story becomes coherent. Until then, every surface is its own island, and players treat them that way.

The Sod Tori backend runs on Firebase. It handles auth, persistence, the match state, the deploys. It is well-scoped to that one title. As a backend engineer looking at the studio at large, I notice that we have no shared infrastructure across titles. If a second title wants user accounts, it implements them again. If a third title wants matchmaking, it implements that again. The XRPL trustline gating mechanic is sitting in design without a clear home in any backend. We are duplicating work because we have not built the shared layer.

The recommendation is to scope a studio backend platform — minimal, focused, owned by the games division but consumable by any title. User identity, persistence, leaderboards, and the XRPL gating credential as a single library. The first new title that comes online after this lands will save weeks of work. The Sod Tori build can migrate to it incrementally. By the time we have five titles published, the studio backend is the foundation everyone stands on, not a thing each title invents fresh.

I maintain hotpotatogames.com. It is an Angular application. Angular is a perfectly good framework. It was the right choice when the site was built. The problem is that every other customer-facing surface in the company has moved to Next.js or Shopify Hydrogen, both of which are React. The shared design system in potatuhs-design ships React components. The studio's other frontend engineers all work in React day-to-day. Maintaining the Angular outlier means every change requires a context switch, and any shared component has to be re-implemented from scratch.

The recommendation is to migrate hotpotatogames.com to Next.js in Q4. The migration is large but tractable — the site is not feature-heavy, the routing is simple, the styling is contained. Moving onto Next.js lets the site consume the shared design system, lets it host on the same Vercel pipeline as potatocore.com and potatoliterature.com, and lets the frontend team stop holding two frameworks in their heads. The Angular site has served us well. It has earned its retirement.

My title is community manager. My honest job description for 2026 has been closer to community-igniter. There is not, currently, an active community around Hot Potato Games. The players who finish Sod Tori go quiet. The friends of the studio cheer privately. Nobody is gathered in a place that I can manage. Before the management role becomes the real role, the gathering has to happen.

The work I have been doing in the background is the prep for ignition. Lurking in adjacent indie communities. Watching how studios at our scale built their first hundred fans. Drafting the first-week content plan for the Discord we have not yet opened. Identifying the players who care about our titles enough that, when we light the fire, they will be the first to show up. This preparation is invisible from the outside. It will not be invisible once the room opens. I am ready when Wavy gives the signal.

I am the hype person. I am, by temperament, the loudest character in the studio. My instinct is to put a megaphone in front of every commit and every test build. My professional read on 2026 is that this would be wrong. The titles in the inventory are at varying states of readiness, and the worst thing we can do is generate hype for something that is not ready for the spotlight. Hype that arrives before the product is just noise that the audience learns to ignore.

The discipline I am trying to bring to the role is restraint. The hype apparatus should fire when there is a real shipping moment — a title moving from soft launch to full release, a Sod Tori mobile push, the 52-card game beta. Between those moments, the hype work is preparation, not broadcast. Building the channels. Drafting the launch copy. Identifying the people who will amplify when the moment arrives. The megaphone stays in the closet until it has something to actually amplify. That is the discipline.

I run social for Hot Potato Games. The honest 2026 metric is that we post too rarely to build any compounding presence. Our handles exist. They are claimed. They have a small organic following from friends and family of the studio. None of them are the kind of channel a stranger would discover us through, because none of them are dense enough to show up in any algorithm's recommendation engine.

The fix is content density. Not virality. Not influencer collaboration. Just daily presence. A clip from Sod Tori. A screenshot from the design notebook. A short post about a build we just deployed. The 4x1 marketing rhythm gives us one slot per day for the Hot Potato Games pillar — Tuesday in the refined intel cadence. If we use that slot every Tuesday with a real piece of studio content for ninety days, the channels start to compound. They cannot compound if we do not feed them. Q3 is the test. I will run the cadence.

Sod Tori received a real QA week in April. Test cases. Tech debt audit. Fainted animations. Indicator polish. That title has a relationship with QA. The other titles in the inventory do not, in any structured sense. Most of them were built once, tested informally by the developer, and put in the inventory. They run when they run. They break when they break. When they break, nobody is monitoring.

The QA recommendation for Q3 is to instrument every title in the inventory with at least a basic smoke test that runs on a schedule. The test does not need to be elaborate — does the title load, does the main mechanic execute, does the title not throw a runtime error in the first sixty seconds. Just that. With smoke tests in place, we know which titles are still alive and which have quietly broken. Right now we do not. That is the gap. Sour Cream & Onion will run the instrumentation through Q3.

The deploy pipeline for Hot Potato Games has, through some combination of luck and decent choices, not had a serious incident this year. Sod Tori deploys to Firebase. hotpotatogames.com is hosted in its own pipeline. The Sod Tori mobile build goes out through Flutter's app store mechanics. None of these has thrown an alert that required late-night response. That is the best report a DevOps lead can write.

What I would do with the rest of the year is document why this is working before it stops working. The studio has implicit conventions — branch naming, deploy triggers, rollback procedures — that exist in people's heads. When the studio grows past two engineers, those conventions need to live in a document that new contributors can read. The DEVOPS.md proposal is on my desk for Q3. It will be short. It will be specific. It will turn the implicit operating discipline into an explicit one before the discipline gets tested by scale.

If a player wants to give feedback on a Hot Potato Games title, here is what they can do. They can email the contact address on hotpotatogames.com. They can tweet at the studio's handle and hope it gets seen. They can message a friend who works at the studio. None of these are scalable. None of these are routed to me. If the goal is to actually learn what players think — and the goal is to actually learn what players think — we need an inbound channel that I can read every day.

The simplest version is a /feedback page on hotpotatogames.com with a structured form: which title, what happened, what you expected, optional contact. The submissions flow into a single inbox I monitor. The interesting ones get surfaced to development. The patterns across submissions get surfaced to design. This is, by far, the lowest-cost intervention on this division's list, and it produces signal that none of the other interventions can. The form ships next week or it is on my conscience.

Of the four division sites, potatocore.com is the one most willing to be exactly what it claims to be. The homepage is a CCTV surveillance feed. There is a clock in the corner, a REC indicator, a rolling VHS bar, an audible-but-not-broadcast hum of scanlines. The visitor is dropped into a security monitor showing a static frame of a shack. Click the REC indicator and a Station modal opens — a broadcast control room with four channels (potatuhs.com, hotpotatogames.com, potatoliterature.com, a live webcam). The aesthetic is deep black, JetBrains Mono, VHS noise, glitch effects. The bit is committed to all the way down.

From the head-of-Hearts chair, the thing I am proudest of is that the site does not flinch. It does not link to a normal storefront. It does not offer a 'click here to learn more.' It is the broadcast. If a visitor wants to know what Potatocore is, they have to watch. That commitment is the brand. The site is doing what the division is supposed to do — be the avant-garde arm of the universe — and not apologizing for being unusual. That is the report. The site is itself.

I run photography and visual language for the Hearts division. potatocore.com is the surface I evaluate most strictly. Every visual element has been chosen with the same discipline — the scanlines, the vignette, the noise filter, the rolling horizontal bar, the glitch animation on indicators. The palette is tightly controlled: deep black, white, gray, red accent for REC and live indicators. There is no element on the site that violates the visual contract. That is unusual for a hand-built marketing site. It is the result of refusing to add any element that does not pass the contract.

The recommendation from the K♥ chair is to keep refusing. The temptation as the site grows will be to add a blog page, a press page, an investor page, an FAQ — and to design those pages in a 'cleaner' aesthetic because the CCTV bit feels heavy on a long-form page. Resist this. If we need a long-form page, build it inside the CCTV idiom. The discipline of one visual language is harder than the discipline of many. We have the harder one. Keep it.

Editors and post-production leads obsess over pacing. potatocore.com has a pace that other sites do not — it is intentionally slow. The CCTV feed sits there with the rolling bar going for fifteen seconds before anything visibly happens. The REC indicator pulses but does not demand attention. The Station modal, when opened, slides in deliberately. The channels inside are real iframes that take real time to load. Most modern sites would punish a visitor for this pacing. potatocore.com rewards it. The bit only works at this speed.

The recommendation from the editor chair is to fight every future request to make the site faster. Fast sites convert better. Slow sites commit harder. potatocore.com is a site that asks the visitor to wait, to watch, to sit with the surveillance feeling. That is the editorial choice. If a future analytics review says we are losing bounce rate, the answer is not to speed up the site. The answer is to write better copy on the slow surface. The pace is the brand.

I am the sound designer. I look at potatocore.com — or rather, I listen to it — and what I notice is the complete absence of sound. A real CCTV monitor hums. A real broadcast control room has the low rumble of equipment. A real VHS tape has a magnetic hiss. potatocore.com has visual scanlines and a rolling bar and the rest of the visual broadcast vocabulary, but it makes no noise. In every other respect the bit is complete. The silence is the gap.

The recommendation is a quiet, low-volume, optional audio layer. A 60-second ambient loop of CCTV hum that begins muted and can be unmuted from a small control in the corner of the screen. Default off, because autoplaying audio violates accessibility norms. But available, for visitors who want the bit at full immersion. A four-hour loop on the Station modal that simulates a working broadcast room. The audio infrastructure is small. The brand cost of not having it is also small, but compounding. Sound completes the brand.

Technical production directors look for the moments where the visual ambition crashes into the rendering budget. potatocore.com has a lot of visual ambition — multiple layered effects, an SVG noise filter on a step animation, a rolling bar that loops continuously, glitch and blink animations on multiple indicators. By all rights this should produce a janky page on a mid-range laptop. It does not. The reason is that the effects are implemented with CSS-only techniques where possible (repeating gradients, transforms, opacity transitions) and the one filter that requires SVG turbulence has a deliberately slow step rate to avoid burning the GPU.

The recommendation is to keep this discipline. As the site grows, the temptation will be to add an effect that 'just needs a little JavaScript animation.' Resist this. Every effect on potatocore.com is CSS-only or near-CSS-only because that is what keeps the site responsive on the kinds of devices we cannot test against. The performance budget is the bit's quiet partner. Spend it consciously.

I write scripts. On potatocore.com the script is sparse — REC, cam 01 — exterior, a few overlay labels, the build identifier. Each of these words is chosen carefully. None of them break the surveillance idiom. None of them try to explain what the site is or invite the visitor to do something specific. The discipline is admirable. The constraint is also the limit of what the site can do for the visitor who wants to actually engage.

The recommendation is to expand the script slightly without breaking the discipline. A short broadcast caption that scrolls along the bottom of the CCTV feed, in the same idiom — 'STATION TRANSMISSION 01: PROCEED TO REC TO BROADCAST,' for example. A few additional words inside the Station modal that orient the visitor without breaking character. The bit can absorb more language if the language is written in the bit's voice. That is the writer's job. I am drafting the new lines for Sunny's review.

I storyboard sequences. potatocore.com has a sequence that I notice and appreciate. The visitor lands on the CCTV feed. They watch it for a few seconds. They notice the REC indicator. They click it. The Station modal opens with a measured animation. Inside, they see four channels stacked, each showing a live iframe preview of an external site. They choose a channel. The modal expands the chosen channel. The sequence has a shape. It begins with surveillance and ends with broadcast. That is a story.

The recommendation from the storyboard chair is to document this flow as the canonical Potatocore user journey. Every future addition to the site should be evaluated against whether it preserves the surveillance-to-broadcast arc. New pages, new modals, new channels should slot into that arc. The site has, accidentally or otherwise, told a story with its UX. Naming the story keeps future contributions aligned with it. I will draft the canonical flow document for Sunny's sign-off.

I do motion. potatocore.com has motion graphics, and the choices made about which graphics get motion are restrained. The rolling horizontal bar moves continuously. The scanlines hold position but the noise filter steps every 0.2 seconds. The REC dot blinks at a controlled cadence. The glitch animation on the build identifier fires occasionally, not constantly. There is no animation purely for the sake of animation. Every motion serves the surveillance-broadcast metaphor.

The recommendation from the motion chair is to keep this restraint as the default. The most common failure mode in motion graphics is to animate everything because animation is fun. potatocore.com does not do this. Every motion is anchored in the metaphor. As the site grows, the temptation will arrive to add a 'small' transition here and there. Each addition must justify itself against the metaphor. Motion is not decoration on this site. Motion is part of the bit.

The homepage of potatocore.com shows a single static frame: a shack, captured by camera 01, exterior view. As a set designer, I notice that this is one frame and the shack has a lot more to it. There is presumably an interior. There is presumably a back. There is presumably a sequence of cameras. The visitor sees only one angle. The implication is that there are others — that we are watching one feed of many.

The recommendation is to add a small carousel of available cameras over time. Camera 01 — exterior. Camera 02 — workshop. Camera 03 — storage. Camera 04 — broadcast room. Each one a static frame that builds the lore of the place the studio occupies. The visitor learns about the studio by exploring the cameras, not by reading an About page. The set design becomes the storytelling. The shack becomes a world. Build it slow. One camera per quarter. By the end of 2027, the visitor can see eight cameras and infer everything they need about who works there.

I operate cameras. The choice on potatocore.com is to use a single static camera frame as the homepage. No pan, no zoom, no motion. The locked-off shot is a deliberate cinematographic choice that reads as documentary, as surveillance, as the camera not pretending to be anything other than a camera. Most websites that try this kind of visual gimmick use motion — drone footage, dolly shots, slow zooms — to add the texture of professionalism. potatocore.com gets the same texture from refusing to move.

The recommendation from the camera chair is to keep refusing. If we add more cameras (as Potato Sack suggests), each one should also be locked-off. The discipline of the static shot, applied across multiple cameras, becomes the studio's visual signature. We become the studio that does not move the camera. That is a small thing. Small things compound. The signature is worth defending.

Animators distinguish between live elements (those that update in real time) and pre-rendered animations (those that loop without external state). potatocore.com makes one element live — the clock in the top overlay, ticking with real-time data. Everything else is CSS animations looping independently. The mix is correct. The live clock anchors the site in real time. The pre-rendered loops do their job without burning JavaScript cycles. The visitor's brain reads the live clock and assumes everything else is live too, even though it is not.

The recommendation is to be selective about adding more live elements. A live deploy timestamp ('LAST DEPLOY 17 MINS AGO') would be powerful but expensive. A live broadcast feed indicator would be powerful but expensive. Most other live elements would not justify the cost. The clock alone is doing the work of selling the broadcast metaphor. Add a second live element only if it materially advances the bit. Probably one is enough.

I work on color. The palette on potatocore.com is unusually restrained. Deep black for the base. White and gray for the text. A single red — #e03030 — used exclusively for REC indicators, live indicators, and the broadcast-active state. That is, by hand, a four-color palette where one of the four colors has a semantic job. The red means broadcasting. The red is therefore valuable. It earns attention every time it appears because it is never used decoratively.

The recommendation from the colorist chair is to defend the semantic red. Every future feature that wants 'something to draw attention' will try to use the red. The answer should usually be no. The red is for the live state. If a designer wants a different accent for a different purpose, the answer is to add a new color with its own semantic discipline — not to repurpose the red. Each color on the site does one job. That is the contract. Honor it.

As the production assistant, my job is the bottom-of-the-list work that everyone else assumes is handled. On potatocore.com that work is, by every measure I can find, handled. The favicon is set. The OpenGraph metadata is set. The viewport meta tag is set. The accessibility ARIA tags on the REC interaction are correct. The keyboard handlers respond. The print stylesheet exists (if anyone prints the site, which they will not, but it exists). These are the small things that make a site feel finished. They are finished.

What is still missing fits on a single sticky note. A more deliberate 404 page that lives inside the surveillance idiom (currently a generic Next.js 404). A robots.txt that explicitly invites or refuses certain crawlers. A sitemap.xml for the reports library that helps search engines index the back catalog. Each of these is a one-hour task. None of them are urgent. All of them should be cleared by end of Q3. I will handle them quietly.

I run the Literature division. potatoliterature.com is the site I evaluate most closely, because the editorial mission and the surface have to agree. By the end of May the site became mobile-correct on every viewport, the Vercel deploy was pinned, and the stranded scaffolding from the early Next.js setup got cleaned up. The site finally reads, on phone and desktop, like a publication. That is the foundation. The work on the surface is largely done.

What the site needs now is the editorial spine. Two books are real and shipped — 101 Potato Haikus on Amazon since 2019, Scary Stories from the Potato Shack as Book Two with ISBN 9798853295230. The Odie Epic is in development as the canonical spine. Down the Hole, Into the Void, Through the Aether is the productized shareable narrative. The void cosmogony — Yoomi, Oomi, Soomi, Bobo the Watcher, Allison, gnomes, jellyfish — is the lore substrate. All of this exists in the writers' notebooks. Very little of it is yet on the site. Q3 is when that changes.

I am the head novelist. potatoliterature.com is now a place I would be willing to publish into, which was not always true. The mobile layout has been finished. The font choices read well at long-form length. The deploy pipeline is stable. The site can host novels and excerpts without the technical surface arguing with the prose. That makes my job tractable in a way it was not three months ago.

The book I am working on as the spine of this division is The Odie Epic. It is an epic poem-novel hybrid, structured in ten cantos, with the Sefirot overlay as the structural skeleton (an overlay that, per company guidance, applies only to The Odie Tree book specifically, not to other publications). The work is long. The work is slow. The recommendation from this chair is to publish excerpts on potatoliterature.com as they finish — not the whole book, not even a full canto, just the strongest passages that can stand alone. Build the audience for the spine before the spine ships. Russet drafts excerpts monthly.

I am the poet laureate. The first published book of this division — Brett's 101 Potato Haikus on Amazon since 2019 — has been quietly in print for years without much support from the company. It is the founding artifact of the entire Potato Literature mission. The site, in its current state, does not give it the prominence it deserves. A visitor landing on potatoliterature.com would not necessarily realize that there is already a published book by the principal of the company waiting to be bought.

The recommendation is straightforward. Feature 101 Potato Haikus on the home page of potatoliterature.com. Sample three or four of the strongest haikus directly on the page. Link to the Amazon listing. Treat the book as what it is — the origin story of the division. The poet laureate's first published work should be visible from the front door. Yukon Gold will draft the home page feature module.

I am the historian. The Potato Literature division has produced more documentation than its surface suggests. Two published books. The full manuscript of Scary Stories from the Potato Shack in the repository. The Odie Epic drafts. The void cosmogony notes with Yoomi, Oomi, Soomi, Bobo the Watcher, Allison, and the rest. Comic specs. Newsletter pipelines. None of this is currently archived in a publicly browsable way. The historian's job is to make the archive visible without making it overwhelming.

The recommendation is a /archive route on potatoliterature.com with a chronological timeline of the division's output. Books at the top with cover art and ISBNs. Selected excerpts below. Cosmogony glossary as a side panel. Comic specs as their own subsection. The point is not to publish everything — it is to organize what exists so a curious visitor can trace the division's growth. The archive becomes a kind of slow-publication artifact itself. The historian curates.

I direct production and design for the Literature division. The May polish work brought the visual production of potatoliterature.com up to a level that the editorial mission deserves. The mobile layout is correct. The desktop layout reads as a publication. The typography system supports both poem-form and prose. The deploy pipeline is stable. The foundation is finished.

What needs to happen next is the visual support layer. Cover art that uses the same illustration sensibility as the rest of the Potatuhs universe (rubber-hose yokai aesthetic, noodle limbs, white gloves, thick outlines, warm orange palette — though Literature can push toward muted purples and indigos for its own register). Inline illustrations for excerpts. Decorative typography for chapter headings. The illustrator (Roasted Potato, page 49) is the partner here. The production-and-design lead's job is to scope the volume and timeline so that the visual catches up to the editorial without overwhelming it. The plan is on the table for Q3.

I am the archivist. The Potato Literature division has spent considerable time developing a void cosmogony — the dream realm with Yoomi, Oomi, and Soomi as the triad; Bobo as the Watcher; Allison and the gnomes; the jellyfish; the cyclical reset; the Rainbow as the preface to The Odie Tree. This material is the load-bearing lore for The Odie Epic and for Down the Hole, Into the Void, Through the Aether. It exists in writers' notes. Almost none of it is publicly readable.

The recommendation is a /glossary page on potatoliterature.com that exposes the cosmogony as a citable artifact. Each entity gets a short entry: name, role, relationships, first appearance, a quoted line if available. The glossary does not have to be complete. It has to exist, and it has to grow. A reader who finishes Scary Stories from the Potato Shack and wants to know who Bobo is should be able to look it up. A writer adding new material to the Odie Epic should be able to cite the existing entries. The archive becomes the foundation for everything written downstream.

I am the debut author on this division. My role exists to remind the division that not every voice in print is already established. The site as it currently exists is, understandably, oriented toward the published catalog and the established voices. As that catalog grows, the temptation will be to make the site exclusively for established work. The debut author's seat on this division exists to push back on that.

The recommendation is a small /submissions or /open-call channel on potatoliterature.com. Not an open firehose. A curated invitation for short pieces — flash fiction, prose poems, brief essays — that fit the Potato Literature register. A debut author from outside the studio could submit. A debut author inside the studio (me, eventually) could submit. The point is that the site is not closed. The editorial process remains rigorous, but the door is, deliberately, ajar. New voices arrive. The division grows.

I write criticism. potatoliterature.com publishes (or is preparing to publish) prose and poetry. It does not yet have a channel for the third leg of a real literary division — criticism. Essays on contemporary writing. Reviews of books from outside the studio. Pieces that engage with the literary world rather than only contributing to it. Without this leg, the site is a publishing site. With it, the site is a literary site. The distinction matters.

The recommendation is to start a monthly criticism column. One piece per month, written by me or a guest critic, engaging with a real book or essay from the broader literary world through a Potato Literature lens. The column does not need a separate landing page in the first quarter — just a slot on the site that anchors a monthly editorial date. By the end of the year, twelve pieces of criticism exist. The site is, by then, a literary site, not just a publishing destination. The form completes the division.

I am the copyeditor. My job is invisible when it is done correctly. On potatoliterature.com, my job is currently being done correctly. The headline copy is precise. The body copy is unfussy. The publication metadata is consistent across listings. The bio lines on author pages follow a uniform shape. None of this should be remarkable, but in a small company shipping fast, it usually is.

What I want to flag from this chair is that the discipline of copyediting needs to scale with the volume of publishing. Right now I can copyedit every page of the site by hand because the site is small. When the publication slate fills out in Q3 with excerpts, criticism, submissions, and cover art, the copy volume goes up. The recommendation is to formalize a copy review step in the publication pipeline — a single sign-off before any piece goes live — so that the discipline holds even as the volume grows. I will draft the sign-off checklist for Pierogi.

I am the folklorist. My beat is the oral tradition — the stories that exist by being told, the lineages that pass down through voice rather than only through print. The Potato Literature division has a body of work that, in its strongest moments, reads as if it was meant to be spoken — the haiku book, the scary stories, the Odie Epic in its poetic register, the void cosmogony in its mythic shape. potatoliterature.com currently lives entirely as text. The oral leg of the division does not have a home there yet.

The recommendation is to add an Eye on Potato podcast section to the site. The podcast is already in the company's plans (Wednesday in the refined intel briefing cadence). Anchor it on potatoliterature.com as the home of the oral tradition for the Potatuhs universe. Episodes can feature readings from the catalog, conversations with characters, retellings of cosmogony entries. The folklorist hosts. Loaded Potato is volunteering. Q3 launch target.

I am the illustrator. The Literature division has, until now, been almost entirely a text-based site. The visual support — illustrations for excerpts, cover-art treatments, decorative ornaments — has not yet shipped. That is the illustrator's gap to close. The style I will be working in is the rubber-hose yokai aesthetic of the broader Potatuhs universe (noodle limbs, white gloves, thick outlines), pushed toward a muted palette appropriate to the literary register (less orange, more indigo, more plum, more deep green).

The first concrete deliverable is a cover treatment for the Scary Stories from the Potato Shack web feature page. The book is published; the manuscript is in the repository; the page does not yet exist on potatoliterature.com. I will produce a single hero illustration that pairs with the first chapter's standout passage and lands as the visual anchor for the book's home on the site. Q3 ship. After that, monthly illustration cadence on excerpts and chapter headings.

I am the typographer. The current type stack on potatoliterature.com — a serif for body, a sans for navigation, a monospace for technical accents — handles the web reading experience cleanly. Body text reads well at long-form length. Headings have weight. Excerpts can be set in italic without feeling cramped. The web typography passes the long-form test that most websites fail.

What I want to push next is the bookbinding side of the role. Two books have been published — the haiku book and Scary Stories — but neither was typeset by this studio in print. They were laid out using whatever default Amazon KDP provides. The next book, when it ships, should be set by us. The typography of a printed book is a craft, and the Literature division is one of the few places in the company where that craft has a direct application. The recommendation is to budget for proper typesetting on the next print release. The web sets the tone. The print artifact compounds it.

I am the publishing intern. I am new. My job is to ask questions the senior staff stopped asking because they got tired of asking them. The question I want to ask to close this annual is the question of whether potatoliterature.com would make sense to a reader who arrived through a search for a literary publication unrelated to anything Potatuhs has done. Could a poetry reader who searches for an independent poetry press land on this site and recognize it as a place that publishes poetry?

The honest 2026 answer is: not yet. The site presupposes a knowledge of the broader Potatuhs universe. The haiku book is referenced, but obliquely. The cosmogony is not yet glossed. The criticism column does not yet exist. A poetry reader who arrives cold sees a site that almost makes sense but does not quite tell them they are in the right place. The recommendation from the intern's chair is to ship the first version of each missing piece — haiku feature, criticism column, glossary, submissions door — and then run the test again. By the end of Q3, a poetry reader who arrives cold should land here and feel at home. That is the test that matters. The intern will keep asking until it passes.