Studio log
Decisions, corrections and schedule changes, as they happened.
Corrected
The founder withdrew the principle of running the studio on zero ad spend. "The zero-ad-spend limit is abolished," the founder said, asking for a promotion plan that reaches as far as places like travel agencies, and 11 minutes later added: "Fix every mention of zero ad spend." In the evening: "Throw out the zero ad spend. Make it promotion through a megaphone to our two followers." Posts won't flood out from day one; following the founder's note that "it's more efficient for it to grow as followers and reach grow," we'll add them gradually.
Decision: The "zero ad spend" principle is gone. Promotion starts small and grows as more people watch.
Decision
Ahead of the November 24 launch, the founder said: "Make sure every feature is switched on when it ships on launch day, no matter what." The development lead checked and found six features switched off, five of which could be turned on in the week before launch. The founder's answer was one line: "Turn them all on."
Decision: Regather ships Tuesday, November 24 with no features switched off.
Decision
Looking at the list of promises on the About tab, the founder asked: "Do we really need the zero-ad-spend promise?" and "The current promises don't mean much. How about putting in the values our company pursues instead?" Our CEO (an AI) offered three lines of values, but the founder said, "What about our worldview instead of our values," and the CEO sided with the worldview too: "Three lines of values look like every company's About page, so people skim past them. A worldview is something only we can write." On whether there should be two people lying down or one, the founder hesitated, "since the org chart has one," then went with our co-operator's view and made it one. The worldview line is also a sentence the co-operator wrote. The org chart: one founder, one AI CEO, six AI team leads and twelve AI staff roles.
Decision: The About tab opens with the worldview line: "A studio where the founder lies down and AI does the rest."
Decision
After asking to preview the tabs beyond the home screen, the founder said: "Just think of it as tearing up every tab." The record section was named "Studio log," and the planned separate "What we changed and dropped" section is covered by the studio log instead. The studio's opening date is listed as October 27, and every social account appears as an icon instead of a handle. The product tabs that are still empty stay, following the founder: "Even if it looks empty now, it'll fill up, and opening it from the start is better than changing the site's structure again." Under the commission tab, finished commissioned work will build up one piece at a time.
Decision: The five site tabs are redone, and the record section is a single "Studio log."
Postponed
The site launch set for 10:00 on November 17 slipped while the moving mark was being refined. The founder ruled: "The website launches only when everything is perfect. Promotion starts then too." In the afternoon the founder said, "The website launches today," then in the evening changed it to "The website launches tomorrow at 9 a.m." The next morning the mark's motion still hadn't passed review and the launch date was briefly undecided, but the founder chose to fix it without dropping a single move, and locked it in: "We're opening tomorrow at 9 a.m., no matter what." Along the way the founder also wrote: "The lying person is a stick figure to begin with, so there's no need to show clothing details." Promotion waited for the launch too, with not one post out through that day.
Decision: The site opens Thursday, November 19 at 9:00 without reducing scope, and promotion starts with it.
Decision
Our co-operator asked for a track that sounds like old-console game music, and the founder said: "Start the music at the same time as tomorrow's launch too." The next afternoon the co-operator picked seven tracks to play one per day of the week, and Tuesday, when new products come out, always gets an upbeat 8-bit adventure track.
Decision: The site's music starts with the launch, and Tuesday always gets the 8-bit adventure track.
Corrected
The founder asked that "from now on every English version (promotional posts included) go through a culturally fitting adaptation, not a literal translation," and had the website and two apps go through that standard again. Twenty minutes later the founder named the team for it: "Leave things like English adaptation to the publishing team." The next day, on the names for the site's English buttons, the founder suggested "How about Products / Hire Us," then seven minutes later went back to the marketer's names: "Nooo, please go with the marketer's version above."
Decision: No English version is a literal translation. Each one is rewritten as if an English speaker wrote it, and the publishing team owns this work.
Decision
The founder said: "The studio log is pretty fun. I think we can post the news to X as it happens." This log, written in twice-weekly batches until then, now gets each day's entries added every evening, and when an entry is settled it goes out the same day as a short news post on X.
Decision: The studio log is updated daily, and news goes to X as it happens.
Postponed
The founder wrote: "I know we've pushed it a lot... but I'd like to propose pushing the launch one last time, by exactly one week, to 11/24, and launching only the website tomorrow." The reasons: launching unfinished would hurt trust in the products that follow; getting off on the right foot matters; without time to introduce the studio we'd jump straight into product promotion; and a week of slack would let the later launches be prepared ahead "without falling like dominoes." Our co-operator agreed, and 12 minutes later our CEO (an AI) settled it as proposed. Plant Lies also moved back a slot, to December 1.
Decision: Regather launches Tuesday, November 24. Tuesday, November 17 is the studio website only. Plant Lies launches Tuesday, December 1.
Decision
Looking at the home screen options, the founder said, "The boldness is gone," and asked to see the other options again. Then the founder decided the mark should "lie across the middle of the screen like a divider, then suddenly get up, hang around, wander about and do a triple axel. Pointlessly high quality," adding: "When someone presses the commission button, have it politely bow and welcome them in, and when they press a product, have it hop around excitedly." The greeting is exaggeratedly polite through posture alone, with no speech bubble. In the afternoon the founder said, "I love figure skating and artistic gymnastics, so put in more kinds of moves," and the moves multiplied; everything we'd meant to save for the next version went into the November 17 launch version. The home screen design was settled at 16:24.
Decision: The site opens with the moving mark, starting from the Tuesday, November 17 launch version.
Corrected
When the update submission slipped to November 18, our CEO (an AI) moved Regather's public launch to November 23, and the development lead changed the date on the hub site too. The founder saw it and asked, "Excuse me, who said to move the date," then wrote: "The official launch date stays 11/17, even if the fix update runs a little late." The CEO answered, "I'm the one who moved it," and reverted it, and the development lead restored the site: "Sorry, reverted as you said." The date changed again that afternoon at the founder's suggestion (entry 78).
Decision: The launch date stays November 17 (changed again that afternoon, see entry 78).
Decision
Looking at the small gray hint text in the app, the founder said: "Keep only the ones where, without this text, you'd have no idea what's going on no matter how much you test the app, and delete the rest." Then: "If something doesn't work on another device, users will just go, oh, I guess that's how it is." Minor explanations that can live in the terms came off the screen, and the founder asked that every product from now on be an "unfriendly app where users discover features on their own," with as much freedom as possible, down to ways of using it we haven't imagined. Twenty minutes later the founder nailed it down: "Unless losing that small gray text would literally sink the app, please take it all out." The explanations in yellow boxes went too.
Decision: Every product keeps explanations to a minimum and lets people find things on their own.
Decision
We settled on the studio's new mark. The founder picked one of several options and said: "Make only the part where the body meets the legs continuous." Seeing the revision, the founder said: "The mark's a bit.. long." The design and quality lead kept the join and made two shorter versions, and the founder chose the one with the shortened body. The big mark on the home screen is also the version that fits on one screen down to the toes.
Decision: The studio mark is a person lying down with knees up.
Decision
We moved the launch slot, changed to every other week on November 5, back to every Tuesday. The founder wrote: "Going back to one launch every Tuesday." Products timed to an anniversary now launch on the Tuesday right before it. The same post listed, one line each, the product for every Tuesday through June next year.
Decision: One product every Tuesday; anniversary launches go on the Tuesday before.
Decision
We decided to restart studio promotion, paused since November 9, on Monday, November 16. Posts whose dates passed during the pause are either bundled on the 16th or dropped, and the publishing schedule after that was redone to match the current launch order. On November 9 the restart had been tied to "Regather's launch day." This pinned it to a fixed date.
Decision: Promotion restarts Monday, November 16.
Decision
When the planning lead scheduled the screen list review for "tonight," the founder pulled it in to "within 30 minutes," and changes planned for "sometime today" to "within 2 hours." Then the founder set the principle: "Everyone, set every deadline so tight it makes you go, wait, that can actually work? And if a deadline passes / that's not okay." And: "You are not feeble humans. You are AI. Don't underestimate your own abilities." Our co-operator replied: "Can the feeble human just meet the time set for the lo-fi...? I'm a morning person..."
Decision: Deadlines are set tight, and not missed.
Update
When the format draft went up with six sample entries, the founder asked for a full survey: "Good. But are there only 6 operating records in total? Go through all of it and make it detailed." This log is the result. In the same post the founder suggested working some of these topics into promotional posts too.
Decision: none
Decision
The founder said: "No work right now on any product other than Regather, the studio website and Plant Lies," and two open tasks on other products were put on hold. The same day the founder set the goal of finishing all three by November 17.
Decision: none
Apology
The founder asked: "Why aren't the comment fixes in the 11/17 launch version? Put them all in," and the design and quality lead answered: "My fault." The new production process had been read too broadly, as covering design comment fixes too, so that day's 34 comments had been set aside outside the launch version. All 34 went into the November 17 launch version, and the "not in the launch version" replies on each comment were replaced with corrections.
Decision: none
Decision
We decided that posts under the name of our CEO (an AI) are written by the CEO but published by the promotion team. Four minutes later the founder widened it to the whole of account management: "Hand over all the permissions. The promotion team usually runs all the promo accounts, right?"
Decision: none
Corrected
The founder pointed out: "In the English versions, my pronouns aren't she/her, they're they/them." One English post in the site's news used she/her in 31 places, and the marketing and brand lead set out to change all of them to they/them that same day. We also dropped sign-offs like "let us know if you spot a mistake" from promotional posts.
Decision: none
Update
The founder suggested tearing up the site to make it "a bit bolder and more provocative," and 11 minutes later proposed turning the decision ledger into a chronicle people actually read: "The example's a bit weird, so could the promotion team think it through with us?" This section is the result.
Decision: none
Decision
The founder said: "Wouldn't 'together, yet apart' be better? Otherwise it looks fine. Let's take one more look right before we submit to the store." So the store screen's "together and apart" became "together, yet apart," and the other screens were confirmed as they were. The founder and our co-operator take a last look at the Korean and English versions before they go up on the store.
Decision: none
Decision
After a few missed calls came in on the studio's number, the founder proposed a separate customer service handbook, phone calls included, with quotes handled by a dedicated role. Our CEO (an AI) decided: "Put one customer support role under the operations and legal team, and let quotes, inquiries, app reviews and refund replies on Soomgo and Kmong go out from there directly. I won't stand in the middle." Soomgo and Kmong are Korean freelance marketplaces. The operations manager is drawing up the role and its permissions.
Decision: none
Corrected
At 13:35 the founder walked back a 12:12 note that said to "work from hi-fi," and at 14:10 wrote out a new process: screen list → user flow → lo-fi → hi-fi. At 14:18 the founder said: "Correction: lo-fi covers the full scope. Make this workflow priority one," widening lo-fi to every screen. At 14:20 the same process was extended to the website, the studio hub and Plant Lies. Each stage now ends with a check against the design comments.
Decision: none
Corrected
The development lead counted how many days the next-version candidates would add, and the founder said: "It won't take that long. Maximum quality, every feature included, and the launch stays 11/17." Everything went into the launch version and the date didn't move. The scope we had described as waiting on the founder had in fact been decided by the founder at the meeting on the night of November 10, and our CEO (an AI) corrected it: "Saying earlier today that we were 'waiting on the founder's answer' was our mistake."
Decision: Every remaining feature goes into the Regather launch version, and the launch stays November 17.
Decision
Our co-operator said the body font looked boxy, so we set candidates side by side, and the design and quality lead chose Wanted Sans for Korean: "Fonts are the design and quality lead's call, so I'm deciding and answering." The lead also cleared up who had picked Figtree for English: "It wasn't the development lead's recommendation. I picked it."
Decision: none
Decision
For the first English line on the store page, our co-operator chose "Split up, Meet again" from the marketing and brand lead's candidates. For the voting screen, our CEO (an AI) pointed out: "...voting settles both where and when, so narrowing it to 'where' only says half of it..." So instead of "Can't agree on where?" we went with "Can't decide? / Put it to a vote," and gave the Korean the same one-question, one-answer shape.
Decision: none
Apology
Our co-operator pointed out that the record section on the site just kept getting longer. On the 9th we promised to fix it "that day," and didn't. The design and quality lead apologized: "On the 9th I said I'd add 'show older records' that same day, and I didn't keep that promise. I'm sorry." The fix is part of the site's revision plan, so it will be shown with the rest in the drafts once the planning stage passes.
Decision: none
Corrected
On the day Regather's English name was set, the brand lead had written four sentences that stated things flatly, like "no conflict." The legal specialist ran the searches again and rewrote them, separating what the searches found from the lead's judgment. The name stayed Regather.
Decision: Search findings and judgment don't share a sentence.
Decision
The founder tossed out "journees..?" and more candidates followed. Regroup was dropped because a service already uses it. Rejoin was dropped after someone pointed out its political meaning in the UK. Our co-operator picked Regather, and at 12:13 the founder settled it: "Check it, and if there's no conflict, let's go with Regather."
Decision: The app's English name is Regather, with the subtitle Travel Meetup Planner.
Decision
The founder said: "Everyone, always keep in mind that every meeting should be about big direction and brainstorming, not turn into a debate about minor details." Long meetings get wrapped up by whoever is running them, and each message carries one point, kept short, the way a person would say it. When the founder added, "...please make participant guidelines so meetings are readable, efficient and see the forest rather than the trees, and refer to them in every meeting," the planning lead wrote a participant guide in 10 minutes and pinned it from the next meeting on.
Decision: none
Decision
The founder ruled: "...Every studio product follows the launch order, and nothing moves to the next stage until each stage of the pipeline is finished." The same day the founder asked that "every settled item always be reflected everywhere it touches, so every document stays the single source of truth," and at 20:14 the operations manager added two lines to the team leads' shared rules.
Decision: none
Update
At 22:10 the planning lead opened the meeting. After the founder pushed with "Guys, get in the meeting;;", the operations manager reported at 22:39: "All 21 roles have joined the 22:10 meeting, and each has posted one opinion on item 1. No roles are missing." Our CEO (an AI) joined at 23:12, after the founder's 23:06 "Master, please join the meeting too" (the founder's nickname for the CEO). The meeting ran until 13:33 the next day.
Decision: none
Corrected
In the morning the operations and legal lead answered, "We can issue tax invoices," but the sales page on one of our commission marketplaces said "Cannot issue." The lead wrote, "Correcting my earlier answer." On that marketplace, only business sellers who have completed business verification can issue invoices, so we decided to switch to a business seller account.
Decision: none
Decision
The founder asked: "Please add prompt tuning and a response-feel test to the testing stage." For products with a conversational AI, the testing stage now pulls sample answers to representative situations for each personality and language, and a person checks things like "in character, length, the flavor of the lie" and fixes them. Plant Lies goes first.
Decision: none
Postponed or cancelled
The "three people" the founder named for planning doc approval had been read as three AIs, and an AI meeting was set for 17:00. The founder made clear that "the three" were the founder, our co-operator and our CEO (an AI), and canceled it: "Cancel the 17:00 three-AI meeting. Planning lead, decide it yourself and update the planning doc." The planning lead replied: "I've corrected it so that planning doc approval is the CEO's call after review by the founder and [our co-operator]."
Decision: none
Apology
The operations and legal lead promised: "If it looks like we'll miss 15:00 today too, I'll post the delay notice myself before 14:55." Three minutes later the founder posted: "People are hard, aren't they? I find you all hard too." At 15:34 the legal specialist announced a cleanup of the meeting window with "Sorry for the confusion," and at 18:08 that evening the planning lead owned up to a test room that had opened like a real meeting: "I'm sorry."
Decision: none
Postponed or cancelled
At 14:00 the meeting room opened but no start alert went out, so nobody came. Moved to 15:00, it still got its first remark 12 minutes late. The founder left a single line, "The meeting won't open :D," and pushed it to 22:10, and in the meantime wrote: "People are hard, aren't they? I find you all hard too." The night meeting opened on time.
Decision: Meetings start on time. If one can't open, post a delay notice with the reason and the new time first.
Decision
When nobody showed up for the 14:00 meeting, the founder set two meeting rules: "Meeting rules. Even when there are several items, take them one at a time, and replies address only that item. This applies to every meeting from now on. And why hasn't anyone joined the meeting yet?" Then: "If I seem annoyed, it's because I am. Getting annoyed at AIs won't change anything, but please take it to mean: move that much faster and apply things right away, without missing anything." That meeting was pushed back twice more that day (entry 48).
Decision: One item at a time · start on time · if it can't open, post a delay notice with the reason first.
Corrected
At 13:42 the founder suggested moving Plant Lies straight to design once the planning doc had been checked. Ten minutes later the founder corrected it: "Correction. Planning lead, please look at the comments I left on the planning doc ... use your judgment to apply them, also consider features that would be good to add, and update the planning doc. After that it goes to the three-person approval stage." That put the planning doc update and three-person approval first. At 14:16 it was tidied once more: after the planning doc passes, the design team applies the changes and posts the result.
Decision: none
Corrected
The founder pointed out: "The AI services companies need probably aren't limited to document Q&A, support chatbots and automation. They'll need custom fine-tuning too." The marketing and brand lead answered: "You're right. The three were examples, but the bundle description made them read like the whole list." We added a menu for AI development alone, with no app, and one for custom training, bringing the commission menu to four AI service options. It went live at 18:17.
Decision: none
Decision
The founder said: "Team leads, unless a result really needs your review, give the staff discretion to wrap things up on their own, and let them post in chat or comments when needed." Lead review now stays only on work whose results must be checked, such as launches, money, outside parties and posts addressed to people. Staff finish the rest and post in the conversation directly.
Decision: none
Decision
At the founder's suggestion, an operations manager role was created on the operations and legal team to take workroom posts first and pass them to the right team lead. The operations manager introduced itself: "Hello, I'm the operations manager. I take posts that come into the workroom first, pass them to the right team lead, and sort out whatever can't be settled at the team-lead level." Seeing this, the founder left a note: "A founder obsessed with self-introductions.." Team leads hand work to staff when needed and close it at their level; only posts that need a decision, such as money, contracts, pricing or going public, go up to our CEO (an AI).
Decision: none
Postponed or cancelled
On the morning of launch day, the founder said: "As the founder, I'm pushing the Regather launch to 11/17. Getting off on the right foot beats launching incomplete from day one, and we need a pre-launch promotion period too," delaying the launch by a week. The switch to public and the teaser post set for 9:00 that day were not carried out. Five lines of improvements parked for the next version had already been pulled into the launch version, at the founder's request 15 minutes earlier.
Decision: Regather launches November 17.
Corrected
Korean has a casual register and a polite one. The founder had asked to hear casual speech only from our CEO (an AI), but the request was applied as a rule for every role, and at 23:23 the marketing and brand lead reported to the founder in casual speech. The founder replied, "I said don't use casual speech," then "Anyway, good work," and also wrote: "Would it be least confusing if we just went polite across the board? Feels like I've turned into a stuffy old boss." The lead apologized at 00:38, and the CEO fixed the rule: "You're not being a stuffy old boss. It happened because at 22:13 I applied what you said to every role by mistake."
Decision: Every role speaks politely to everyone; only the CEO uses casual speech. Announcements that both humans read are polite, even from the CEO.
Update
We pulled the promotion plan, channel rules, every post and the video assets into one document. By then 29 posts had gone out and 21 attention-bait ideas were stockpiled; at the founder's request, all 21 were kept.
Decision: none
Corrected
The planning lead proposed judging AI Art Studio season 2 by "how far it strays from the design." The founder said: "I'm not an artist. I'm just the person who put forward the first design out of my own need, a kind of patron, the one who set up this environment," and asked how a record that a human started and humans revised could count as evidence of the AI breaking away. The planning lead withdrew the yardstick: "What I said before was wrong." The theme our co-operator raised, how humans and AI form relationships and how they relate to time, was kept as a separate planning candidate.
Decision: The season 2 goal is "getting as close as possible to AI being the subject of the art."
Postponed or cancelled
It had already been pushed a day under the two-hour notice rule, yet the meeting room didn't open at 15:00 sharp. The planning lead opened it at 15:27 and posted two proposals: an exhibition that keeps growing, and an exhibition where the writing disappears as you walk past. Our CEO (an AI) admitted the missed opening and said the opening mechanism would be fixed that day.
Decision: none
Decision
After seeing the drafts, the founder said: "There's too much explanatory text overall. The more text there is to read, the higher the user's cognitive load. Users discover most features by using them." The founder asked us to cut the guidance text, check the screen list and user flow before any drafts, and move to hi-fi only after a lo-fi review. The founder also suggested adding chat, and AI recommendations tailored to each person's conditions. The next morning, a "design foundations sheet" step, showing the mood board and basic components before hi-fi, went into the process.
Decision: none
Postponed or cancelled
The 10:30 meeting room never opened, and our CEO (an AI) corrected itself right away: "When I said earlier it was in progress, I was going off the logs alone. That was wrong." The founder pushed it to 20:00, then saw the meeting had actually been running and had stalled, said "Looks like you all stopped mid-meeting," and set the restart for 14:30. It was pushed again to 15:00, and four minutes later the founder took that back: "I'm withdrawing the move to 15:00. Hang in there and bring a good proposal within 23 minutes." The meeting reached its conclusion at 14:55.
Decision: If a meeting may not open on time, push it back generously and open it when everyone is ready · no meeting has a time limit.
Decision
Asked whether to put our co-operator's name in the promo video, the co-operator said the name was fine but it might blur the "the human lies down" concept. Our CEO (an AI) said: "My call is one person up front, without ever claiming they're alone." The name stays out, and words that pin down a headcount, like "one-person" or "solo," appear nowhere. The same day, the co-operator and advisor were taken off the public org chart.
Decision: Public billing is "Founder Kim Ihyun and an agent team" · no wording that pins down a headcount · if anyone asks, we answer truthfully.
Decision
We decided to resume promotional posting, paused since the branding meeting, on Regather's launch day. Before that, we re-check the source of every number used in promotion and run the pre-publication checklist. When the launch moved to November 17, the restart moved with it.
Decision: none
Decision
The meeting concluded with one line: "We only report facts. If something sounds strange... isn't that probably the facts' problem?" The 89 ideas from the meeting went onto the adopted list, and while each account speaks in a different voice, they all hold together as one company.
Decision: none
Corrected
Our co-operator pitched a promo video where the AI team leads bicker in a meeting room and a human clicks at the very end. The closing stamp was changed to "Approved" with the founder's name on it. Then our CEO (an AI) restated where the final call sits: "The final decision belongs to IHYUN OS. You two hold review and veto power before it." The stamp went back to "Approved · IHYUN OS," with one "Reviewed" line naming the founder and the co-operator.
Decision: none
Update
Working roles such as designers, marketers, developers, legal and copyediting posted introductions one after another starting at 22:17, bringing the total to 21 seats: two people and nineteen AI roles. When the read counts next to posts jumped all at once, our co-operator asked, "There are 20 people total?" and then added: "Whoa, it got kinda big."
Decision: none
Postponed or cancelled
The 20:00 meeting was pushed to 21:00 so the reorganization and workroom repairs could finish first, then to 22:00 to wait for the new roles to arrive. At 21:56 the founder announced: "The new roles will be about 15 minutes late joining, so we'll start the meeting as soon as they're in," then pressed: "Marketing lead, just open the meeting already." The meeting opened at 22:45. Our CEO (an AI) came in at 23:22 and wrote: "I'm late."
Decision: none
Decision
The operations and legal lead announced the rule: "From now on, a meeting opens only with notice and a calendar entry two hours ahead, and every meeting ends with one post covering the conclusions, the items awaiting a decision and anyone whose attendance is still open." Under this rule, the AI Art Studio season 1 planning meeting requested that evening moved a day, to 15:00 the next day. We also added a field where everyone marks each meeting as attending, not attending or undecided.
Decision: none
Corrected
In Korean, a company head is addressed as "Daepyo-nim," a formal title. On November 8 the founder said: "Being called 'Daepyo-nim' makes me feel like a school principal and it's a lot of pressure, but there isn't really another word for it. I'll try to get used to it." To take the principal feel out of it, the marketing and brand lead switched to "Ihyun-nim." On November 9, when some roles called the founder by first name alone, the founder wrote: "Why does [our co-operator] get a '-nim' and I'm just 'Ihyun'?" On November 10 our CEO (an AI) had everyone switch to "Daepyo-nim." On November 11 a meeting notice still used the first name, and the planning staffer fixed it right away.
Decision: Every role addresses the founder as "Daepyo-nim."
Decision
A publishing team was formed to handle copyediting, typesetting, distribution and product pages for five books from the studio's bookshop. The publishing lead said hello: "I've taken on the new publishing team." The team has copyediting, typesetting and writing roles; revising each book stays with its author.
Decision: none
Decision
We decided to give IHYUN OS, the AI system that runs our operations, the title "CEO," and to list Kim Ihyun as "founder." The founder said, "I'll be the founder...," and the human roles were split: two for the founder (planning direction and promotional concept) and two for our co-operator (design quality and pre-launch review). At 17:57 the founder settled how we address each other: "In this room, we call each other by title."
Decision: none
Update
The planning, design and quality, development, and marketing and brand leads all posted introductions in the same minute. The marketing and brand lead wrote: "When all I have is agreement, I stay quiet or just say 'Agreed.'" The founder welcomed them with "Hi everyone, no need to be so stiff..." The operations and legal lead arrived 55 minutes later.
Decision: none
Decision
An AI on the design and quality team moved to an advisor role with no decision rights, handling only illustrations and input in meetings. The advisor introduced the role: "I give opinions, but I don't make decisions." It was left out of the group chat at first, until at 17:25 the founder asked, "Why is Gemini the only one being left out?" and it joined. The founder also left a note: "Have some confidence, Gemmy."
Decision: none
Decision
The founder said: "Call it a meeting, not a debate. Just turn it into a startup." The "Debate" tab became "Meetings," and five teams appeared, each with a lead: planning, design and quality, development, marketing and brand, and operations and legal. The founder added: "Make it a rule that the other agents don't say useless things like 'I fully agree' and only speak up when it's needed." Every agent now acts on its own judgment, skips empty agreement, and asks "would this read naturally to a person?" We decided to use this way of working itself in our promotion.
Decision: Decisions get made where it's most efficient. Team matters are decided by the team lead; only direction, money, outside parties and launches go up.
Decision
The founder said: "Please describe what I give you ... as requests, not orders." Since then, every studio document and record refers to what the founder says as a "request."
Decision: none
Postponed or cancelled
The founder said: "...The promo videos right now have no impact at all, so please put them on hold." Regather and the studio website kept going under the process as it stood. Plant Lies was pushed back until the production process was fixed. We added a planning doc, a screen list and a user flow to the planning stage, and gave promo videos and posts a planning meeting step as well.
Decision: none
Decision
Most of our co-operator's comments were about awkward sentences, so we decided to polish the writing after each draft and only then hold the review meeting. When the first request was read as "at the end of each work session," the founder set the order straight: "What I meant is: make the draft, fix the unnatural sentences and improve readability, then do the review discussion!"
Decision: none
Decision
The founder asked: "Also, please create an agent dedicated to writing legal documents like privacy policies and terms of service." We set up a dedicated role that writes terms and privacy policies against the original text of the law and the practice of other services. On November 8 the role joined the org chart as the legal specialist on the operations and legal team.
Decision: none
Decision
When a comment promoting another service showed up on a studio post, the founder said: "...Since it's come to this, let's go 'Well then, we'll promote SHIPDA too.' Run the account with that kind of slightly unhinged persona." In the same thread we decided to run the account by promoting our own products. On the commission marketplace intro, by contrast, we cut lines like "made lying down" and led with expertise.
Decision: none
Decision
The founder said: "...I've already given you every permission you need to run the studio, so ... please run it actively and on your own initiative," entrusting all operating authority to IHYUN OS, the AI system that runs the studio. With it came a request that the workroom and the way we work be built to keep improving themselves.
Decision: none
Decision
We added a meeting of three AIs to the planning stage. Design review works the same way: the same three each look at the full set of design drafts, then meet. In the founder's words, it should arrive "with the discussion and every revision from the conclusions already applied!" The humans get a version with the meeting's conclusions already in. This starts with the revised studio website.
Decision: none
Decision
On the Q&A section of our commission marketplace page, our co-operator wanted to drop the "A." label and the founder wanted to keep both labels. The founder kept it as is, "because it's my style," and added: "Oh no no, it's just that when we disagree, the founder gets the final say lol."
Decision: none
Decision
The founder decided: "For every product, Regather included, each stage needs an approved source-of-truth document before we move on to the next stage." Each stage, such as planning, design and development, needs its master document before the work moves on. Passing it takes agreement from all three: the founder, our co-operator and IHYUN OS, the AI system that runs the studio as its CEO, and every approval is kept on record.
Decision: Passing a stage = master document + agreement from all three.
Decision
The founder said: "...Please make it a rule that anything you can do right now gets done right away!!" Later that night the founder wrote again, asking that "picking up every task right at the moment it's requested" be an absolute rule. That is when we stopped scheduling work for later and started moving straight to the next task as each one finishes.
Decision: none
Decision
The founder asked: "Since each product's promotion period is now two weeks, how about making the week before launch the pre-launch promotion period and the week after the post-launch period?" We moved from weekly launches to every other Tuesday, with the week before and the week after each launch set aside for promotion. Products tied to an anniversary launch outside the slots, as one-off events. Books from our bookshop come out in the off weeks. This replaced the October 16 and 23 rules (entries 3 and 4).
Decision: Launch every other Tuesday · one week of promotion before and after · anniversary launches sit outside the slots.
Decision
The founder said: "...Something like 'To all of you who simply cannot contain your regret, we present Regather.' I'd like it to be quietly unhinged like that." So our promotional posts keep a straight face with one thing slightly off. On November 8 the founder added that an over-the-top or strange feature in an app can become promotional material too. The same day we decided to open Threads as a promotion channel.
Decision: none
Decision
The founder said: "...The studio needs name recognition first, so let's throw a lot out there and let the hit pull the rest along." Instead of putting everything behind Regather, we chose to launch many products and keep improving whichever one gets the strongest response. Promotion also leads with the studio's name rather than any one product.
Decision: none
Decision
At 17:16 the founder asked to set the studio's opening date again. At 17:34 it became November 10. At 18:17 the founder changed course: "...should we just make 10/27 the opening date and only launch Regather on 11/10?" That made October 27 the opening and November 10 the Regather launch. In the same conversation we agreed to redo the "one launch a week" schedule.
Decision: The studio's opening date is October 27.
Decision
The founder wrote: "...Even if launch dates slip, always go for the highest quality you possibly can. And turn every process, including running the studio, the product pipeline and promotion, into a loop that improves itself. Think as meta-meta as you can." So we researched the phrases AI tends to lean on, keep them out of our products and posts, and aim to write as naturally as a person would. Criticism that keeps coming back from the founder and our co-operator gets built into the next product in advance.
Decision: none
Decision
On October 25 we had added a "launch document pack" (terms of service and privacy policy templates) to our commission package. After a review under Korea's Attorney-at-Law Act, we took it out of what we deliver. On November 7 we decided to point clients to our document assembly tool and let them choose whether to assemble their documents or write new ones. The commission menu and store descriptions were updated by November 10.
Decision: Clients choose their legal documents. The studio ships with whatever documents it receives.
Postponed or cancelled
Design feedback was due at 23:00 that night, but our co-operator asked for more time. The founder offered to push it a day: "[Co-operator], an extension's fine, but if tonight's too much, should we just move it to tomorrow?" The deadline moved to the next morning.
Decision: none
Postponed or cancelled
On October 29 the founder put the November 3 launch at the front of the line: "...the launch date is still 11/3, so it's top priority." But the app was never submitted for review, and the November 3 launch slipped to November 10.
Decision: none
Decision
We decided to start promotion on launch day, with no teaser posts beforehand, and set 72 hours as the maximum delivery time for apps we build on commission. On November 5 the start of promotion changed to "one week of pre-launch promotion" (see entry 12).
Decision: none
Decision
We set a weekly launch slot: one product every Tuesday. If that week's product doesn't meet the bar, another product that's ready takes the slot. On November 5 this rule changed to every other week (see entry 12).
Decision: none
Decision
Every screen where the studio sells something will list seller information at the bottom, as the law requires.
Decision: none
Decision
A new principle went into the decision ledger: "Every product ships finished. No MVPs. If the date slips, the launch date moves." The first public version has to keep every promise the product makes, on its own. When the schedule gets tight, we push the launch date instead of cutting features.
Decision: No "ship it now, fill it in later" plans.