番茄西红柿 · 小红书 RedNote UGC Work OS · v0.2 · 2026-11-19

番茄西红柿 · 小红书 RedNote UGC Work OS Product Spec

展开目录 / Contents

产品说明

产品定位

番茄西红柿是图文、视频笔记创作者、KOC与个人OPC使用的个人创作Agent工作台。围绕个人档案、素材、原帖与风格、创作、反馈、账号矩阵、经营和复盘形成连续工作流。内部运营协助第一批创作者,产品主体仍面向个人创作。

产品与用户案例分层

仓库主要交付是工作台前后端代码:server.py、workspace.html、workbench.js、workbench.css与通用提示词契约。首页是产品落地页。知之和EZ放在 data/cases 与 docs/cases 受众策略、案例和独立工作室数据层;不把创作者姓名、个人爱好和本机资料路径写成通用业务规则。

知之:家居、生活方式、良渚日常、玩偶、动手、书法与中医课;十年以上大厂设计师经历由用户提供,具体任职未经核验。她代表从真实生活内容到自主选品的用户案例。

EZ:知识付费、1v1服务案例。299元、60–90分钟、首批10个名额是原会话提案,未确认为在售、成交或效果。服务边界不包含心理诊断或治疗。

当前交付边界

v0.2是本机可运行的单用户工作台及SQLite后端,不是已上线的多租户SaaS。真实模型执行器已编写,但当前未配置模型密钥,没有完成真实生图或文本调用验收。社媒OAuth、自动发布、商家订单API、付款和完整视频渲染尚未接通。UI中的排期为计划记录,不是定时发布守护进程。

功能需求

十个一级功能

编号功能输入与实际行为确认与输出
F01建立创作者档案姓名、频道名、赛道、当前造型、兴趣与表达;新增工作室本人确认与AI推测分开,独立SQLite工作室
F02管理品牌与人物素材上传原图;按SHA256字节去重;导入已配置的旧素材库;白底、绿幕、透明、Logo、头像与封面任务原图保留,生成资产记录来源图和任务,人工批准主图;透明绿幕主用版本可分别保留
F03保存原帖并学习表达手动保存完整原文、网页日期、图序、指标;授权本机导入按原帖ID去重原文不改写;只发送选中原帖到风格任务;引用证据和缺口
F04策划与制作新内容图文或视频项目、简报、正文、拍摄清单、参考资产、14项提示词能力模型结果先待审阅;不复用旧经历;视频输出脚本与分镜,可用本机ffmpeg制作静音图片预览;动态视频另接服务
F05接受反馈并保留版本每次保存前记录稿件版本;恢复为新版本;反馈作用域为创作者、账号、项目或素材采纳、拒绝、确认长期规则;正文变化使审阅失效
F06管理账号与矩阵平台账号登记、定位、受众依据、未知粉丝数;母稿复制为独立账号版;排期、负责人、异常账号登记不等于授权;发布URL人工记录;各账号指标独立保存
F07关联好物与商户原帖和图片位置、商品关键词、链接或口令、店铺、日期价格、体验;商户条件、样品与授权记录普通收藏不等于分销;证据缺失保持未知;相似外观不等于已确认同款
F08经营服务与产品咨询、数字产品、实物方案;受众、价格、容量、交付、条款;八个赛道模板咨询询盘→适配→问卷→预约→沟通→总结→回访;关键阶段须交付依据;案例另需许可
F09导出并复盘结果创作包ZIP含HTML、Markdown、JSON与所引用素材;手动指标;订单CSV去重更新与退款未知归因不补猜;按净额生成NOT_PAID佣金审核草稿,不执行付款
F10连续执行Agent任务冻结档案、明确账号与项目、选中原帖和素材、已确认偏好、提示词版本与输入版本queued / blocked_configuration / running / needs_review / accepted / rejected / failed;保留请求ID、输出、审阅;不静默重试

AI 能力与执行协议

通用提示词注册表在 data/catalog.json,源生成器 scripts/build_catalog.py。能力包含原帖风格、选题、图文、视频脚本、反馈修订、白底、绿幕、透明、Logo、频道封面、好物识别、匹配分析、服务文案和复盘。

任务必须包含creator上下文、明确的账号和项目(允许明确不指定)、参考素材ID、原帖ID、输入版本、提示词版本及确认点。文本调用使用Responses API;用户勾选的参考图作为input_image发送。图片使用Images API生成或编辑。服务器环境变量提供密钥与模型名,浏览器不保存密钥。执行前须确认本次发送范围;未配置时只保存待配置任务,不返回模拟作品。

依据:Responses API、Images API。适配器尚未完成真实供应商调用验证,不应宣称可用的模型覆盖或效果。

UI布局

落地页

最新视觉参考为用户指定的蓝莓贝果。参考其浅灰白底、留白、分栏首页与清晰工作区;产品采用番茄红、浅红状态与少量叶绿,不复制蓝莓Logo或主视觉。此决定替代早期Rumi彩虹方向。首页输入想法后带到创作工作台。两种用户案例只是受众说明,实际产品可新增任意创作者。

工作台

左侧导航,中间项目与表单,右侧Agent建议。导航包含概览、档案、品牌素材、过往风格、创作项目、按当前创作者隔离的封面工作台、账号矩阵、好物商户、服务产品、数据复盘、反馈记忆和Agent任务。浅灰白底、白色卡片、番茄红主操作和当前项、少量叶绿状态。窄屏导航横向滚动,Agent移至正文下方。

主要控件

顶栏明确当前工作室与本机保存版本。搜索与素材/账号筛选位于内容上方,显示数量。表单有字段标签、未知提示与显式保存;业务失败保留输入并报告,409版本冲突不覆盖服务器。生成图片先展示待审阅,上传原图置于来源层。原帖长文与全部图片折叠,附独立好物行。主用原图、绿幕与透明版分别保存。

双语

落地页和工作台主要导航提供EN/中文切换,PRD、验收清单与案例页完整双语;原始笔记保持作者中文,不自动翻译改写。部分工作台业务表单当前仍为中文,完整界面国际化未完成。

用户使用流程

共用创作闭环

  1. 创建自己的工作室,填写频道与档案,上传本人或授权照片。
  2. 原图保持原样;创建白底、绿幕、透明或品牌任务,选参考与具体要求。
  3. 审阅真实结果,修改反馈并确认主图;未配置模型时任务等待配置。
  4. 导入原帖与指标,选择用于学习的证据;确认长期表达偏好。
  5. 新建图文或视频项目,从新素材策划、写稿、拆拍摄顺序。
  6. 保存版本、接收反馈、修订并确认事实;为明确目标账号创建版本。
  7. 记录排期、运营责任和异常,实际在平台发布后回填链接和指标。
  8. 导出创作包、按数据复盘,把确认的规则用于下一次任务。

好物创作者

知之案例从生活场景、家居、玩偶、挂画与动手记录中提出产品线索。必须保留原帖、图片序号、外观依据、候选型号、来源URL、商家、带日期报价与本人体验。淘宝/1688当前访问被浏览器安全策略阻断,不能通过换工具规避;未核信息保持待核。首次不强制合作申请,先收藏和分享,再走后续授权、样品、分销和履约。

服务型创作者

EZ案例从专业和服务边界出发,经内容引发有效询盘、问卷适配、预约、沟通、总结行动、回访。客户资料不默认发送到模型、不自动进入公开素材。案例内容需另有许可。无真实支付连接时不能标已收款。

其他赛道

宠物需适用对象、尺寸和实际使用;美妆穿搭需色号尺码及同条件素材;旅行户外需时间地点与装备归属;美食需到店时段及菜单时效;数字产品需版本、许可和支持范围。八个模板在data/catalog.json,流程可由档案选择,不改变底层创作与版本模型。

补充说明

数据模型与接口

每个工作室的profile、accounts、assets、archive、projects、variants、goods、merchants、offerings、deliveries、feedback、metrics、orders存入SQLite。jobs和audit独立表保存任务与操作版本。更新使用revision乐观锁,冲突HTTP409不自动覆盖。共享设备的单机使用者可以切换工作室,此隔离不是在线多租户鉴权。

接口作用
GET /api/bootstrap工作室、提示词、赛道与配置状态
POST /api/workspaces创建独立工作室
GET /api/w/:id读取工作室与版本
POST /api/w/:id/save校验后保存,需revision
POST /api/w/:id/assets8MB图像上传、哈希去重、来源记录
POST /api/w/:id/import-archive导入本机授权原帖
POST /api/w/:id/import-library导入已配置的原图和衍生素材
POST /api/w/:id/import-goods将观察线索关联已导入的原帖
POST /api/w/:id/import-drafts导入已有创作方向草稿
POST /api/w/:id/render-video用选中图片实际渲染静音分镜预览
POST /api/w/:id/jobs创建冻结上下文的任务
POST /api/w/:id/jobs/:job/run明确同意后执行一次,无静默重试
POST /api/w/:id/jobs/:job/review保存采纳或拒绝
GET /api/w/:id/export/:project导出可查看的ZIP创作包

运行与接入

在仓库根目录运行python3 server.py --port 4176。仅绑定127.0.0.1。私有数据库与文件位于.local并排除Git;原始归档与本机路径不随产品上传。生产上线需要独立的认证、授权、备份、密钥和任务执行治理,当前未部署。

服务端环境变量:KEAI_OPENAI_API_KEY、KEAI_TEXT_MODEL、KEAI_IMAGE_MODEL;可显式配置HTTPS的KEAI_OPENAI_BASE_URL。未配置不调用模型。不得把Codex会话的内置生图能力当作网站后端自动拥有的API。图片当前没有新调用;旧素材来源保留原记录。

验收状态与未完成接入

详见逐项覆盖与验收。已实现本地数据链路与表单交互,模型适配器真实API调用、平台OAuth与自动发布、商家实时订单与自动对账、付款、完整视频制作仍需接入与实测。不能把任务创建、账号登记、人工填表或结算草稿称作外部执行完成。

分阶段经营

第一阶段自主收藏、内容与服务方案;第二阶段明确授权的商户合作与分销;第三阶段可选的自有产品与履约。Branvas用于启发品牌素材与经营环节,不假定其供应商、用户或佣金能力已被本产品接通。

已确认权限规则

只有平台管理员 Ruby 可以查看和管理全部创作者。普通创作者账号只可访问自己的独立工作室;团队版在有效 seat 和明确工作室授权范围内切换。下拉框必须使用服务端过滤后的工作室列表,不能把所有人物信息发送给普通账号后再前端隐藏。

权限覆盖工作室、人物素材、媒体原文件、封面、原帖、项目、导出、任务和管理接口。新增账号不能按同名认领已有工作室;已有私人素材的归属由管理员显式绑定。团队资格与 seat 由服务端管理,客户端不能自行修改;撤销后下一次访问立即失效。

当前状态与验收边界

已从本机人物素材库接入 11 个独立工作室并核验 203 张素材,原始文件与衍生版本分别保留。已被否决的封面继续留在原库归档,不进入本次新增工作素材。导入来源在本机私有配置中,文件按内容哈希去重。

本机现有下拉切换仍是单机管理员管理方式,不等于已经实现云端登录与权限隔离。Ruby 要求本轮接入正式云端身份和权限;免费项目配额阻止创建新项目,指定暂停的旧项目又出现供应商状态冲突,控制台核对尚需完成。云端真实登录、越权接口与素材读取、团队 seat 授权和撤销均须实测后才能标为完成。

应用场景

知之:生活方式用户案例

输入新的家居照片与生活细节,引用已确认的表达规则起草细腻笔记;绿色转椅、猪玩偶或字画作为有图序证据的候选好物。原帖保持原样,不把相似款称同款,不虚构购买经历。受众策略详见知之案例。

EZ:知识付费案例

为一个有明确边界的1v1方案制作内容,从询盘到问卷、预约与交付保存依据。记录总结、7天行动、3至7天回访;客户记录留在私有工作室,未经单独许可不进入创作素材。

宠物示例 · 豆包的窝

选题是「这张垫子能让小狗伸直腿吗?」。记录试用犬的体型、伸腿身长和睡姿,量出垫子真正可躺的长宽。用一次午睡的全身照配尺寸图,让读者看见四只脚是否都在垫上,再判断自家狗是否适用。

美妆穿搭示例 · 栗子的试色间

用同一件白衬衫对比两支口红。给每张原片标注口红色号、衬衫尺码和试穿者肩宽,固定窗边位置、光线、曝光和白平衡。成稿将上唇照并排展示,读者可以在相同条件下比较妆效。

旅行户外示例 · 山羊的行路簿

做一篇雨天徒步装备复盘。在路线图标出日期、步道入口、出发与折返时刻,再按路段配现场照片。装备清单逐件标明自购、借用或品牌提供,写清在哪一段用过、哪些全程没有取出。

美食示例 · 小熊的午市手账

比较同一家店午市与晚市的供应。两次到店分别记录日期、点单时刻、当餐菜单、价格和上桌照片。把供应时段写进配图说明,季节菜标明店家确认的截止日期,未获确认时写「仅记录到店当天」。

新创作者首次使用

填写本人姓名、频道名、赛道并确认管理授权;上传原图,创建Logo和人物素材任务,批准后作为后续创作参考。新建用户无需修改任何通用代码。

运营协助账号矩阵

一份母稿形成多个账号版本,分别记录定位、排期、负责人、异常、实际发布链接和指标。保存来源、修改与执行版本;不会用默认账号静默归属历史记录。

已有原型数据与素材

v0.1浏览器原型保留在prototype-v1.html,原localStorage键未清空。旧原帖和素材库通过用户配置导入新后端。新的工作室不自动继承知之私人资料;原始图片与客户记录不进Git。

封面工作台与创作者试点

个人创作优先,运营提供协作,选品分销按需进入。封面工作台属于帮助博主个人创作的早期交付模块,不是独立的品牌侧运营系统。Ruby SoloTrip 是用户案例之一;知之、Dylan Su、EZ 和后续创作者各自拥有档案、素材、封面与排版设置。通用代码不得把 Ruby 的旅行身份、城市或具体外观当成所有创作者的默认值。

封面模块的交付路径

  1. 官网进入免登录体验,或通过登录入口打开本机工作室;注册页创建自己的创作者档案。
  2. 在工作台个人创作板块打开封面模块,先选人物,再选小红书、抖音、哔哩哔哩、YouTube 或其他已支持的平台。人物切换同步到当前工作室,避免串库。
  3. 复用 Ruby 原有的前端与控件:国家、城市、内容类别、搜索、进度、数量、放大、字体选择、倾斜、字号、行距、颜色与字体确认。所有人物显示同一套筛选控件,选项取自本人的作品;没有国家与城市资料时标为未填写。
  4. 小红书使用独立 3:4 信息流封面预览;抖音及通用竖版为 9:16;横版为 16:9。已导出的 PNG 保留原始像素;改变字体后的平台排版是预览,不冒充已重新导出或已同步 Canva。
  5. 新版人物封面从原始参考重新生成,使用独立的无字场景和文字层。点击「用于新项目」保存当前标题、平台、字体参数与源封面 ID;现有创作项目继续使用真实的本机存储和版本机制。
  6. 新创作者无需修改通用代码:建立工作室、上传授权原图并启动本人封面项目;已有案例不是注册条件。模型未配置时任务明确等待配置。

质量与失败案例

第一版被用户否决的封面单独归档,默认封面库、生成参考与新项目选材中排除;原始文件不删除。人物出现粗糙纹理、过度锐化、发型或身份漂移时,从原始照片与已认可参考重生。皮肤光滑细腻、柔和受光;牙齿需要提白时去黄,保留牙缝、单颗形状和自然明暗。逐张按原生尺寸检查。人物专属外观调整不推广到其他人。中文使用项目已确认字体单次排版,合成后不再回灌模型。

产品入口与经营边界

官网、免登录工作台、登录入口、注册页、价格页、双语 PRD 互相连接。当前登录选择本机已有工作室,注册创建本机档案,不是已经接通云端认证。免登录体验与本机工作室当前免费;运营协作的范围与价格待确认,不虚构收费方案。云端认证、生成服务订阅、付款和多人权限后续分别接入。

封面模块由仓库内的适配代码读取本机配置的原有前端与素材。私人照片、实际案例图和本机来源路径留在 .local 或原目录,不进入通用 Git 代码;其他环境须显式配置有权使用的界面资源和素材,不自动借用 Ruby 的私有图库。

试点验收围绕首张可用封面耗时、修改轮次、创作者本人采纳与重复使用。运营帮助整理参考、修改与验收;选品和分销只在作者有真实需要时进入,不挡住封面与内容创作。

原HTML与AI字形

封面工作台复用原HTML模块,默认入口为抖音 format=douyin 与 glyphs=custom。所有创作者共用21款字体和AI字形选项;字体、倾斜、字号、行距、颜色、试字、参数确认和下载按人物与平台分别保存。AI字形风格可复用,精确标题的字层必须另行制作;不得把Ruby的银川文字层套到他人标题。可创建透明字层任务,待模型接入、生成并逐字审阅后才作为成品。

Product overview

Positioning

番茄西红柿 · 小红书 RedNote UGC Work OS is a personal creative-agent workspace for photo/video-note creators, KOCs and solo operators. It connects identity, assets, original posts, voice, creation, feedback, accounts, commerce and review. Internal operators assist the pilot; personal creation remains the core.

Separate product from case studies

The repository primarily ships reusable frontend and backend code. Creator names, interests and local archive paths are case data, not hard-coded business rules. Zhizhi and EZ live under data/cases and docs/cases, and in separate local workspaces.

Zhizhi represents home/lifestyle content, Liangzhu life, toys, DIY and calligraphy. A decade-plus background as a large-company designer is user-provided, not an independently verified employment history. EZ represents knowledge services; the proposed ¥299, 60–90 minutes and ten initial slots are unconfirmed proposals, not sales or outcomes. No psychological diagnosis or treatment is offered.

Delivery boundary

Version 0.2 is a runnable local, single-owner workspace with SQLite. Real provider adapters are implemented, but credentials are not configured and live model calls have not passed acceptance. Social OAuth, automated publishing, merchant order APIs, payments and full video rendering remain unconnected. Schedules are records, not a publishing daemon.

Functional requirements

Ten top-level capabilities

IDCapabilityInput and behaviourConfirmation and output
F01Creator profileName, channel, vertical, appearance, interests, voice; create a workspaceConfirmed facts separate from inference; isolated SQLite state
F02Brand and identity assetsUpload originals, SHA256 byte deduplication, import a configured library; white/green/alpha/logo/cover tasksPreserve originals and provenance; approve before assigning a primary version
F03Original-post archive and voiceFull captions, displayed dates, ordered images and metrics; idempotent authorized local importDo not rewrite originals; selected posts only enter a style task
F04New content productionPhoto/video projects, briefs, copy, shots, references, fourteen prompt contractsReview model results; video supports script/storyboard and a real local silent image preview; generated motion remains unconnected
F05Feedback and versionsSave prior drafts, restore as a new version; creator/account/project/asset scopeAccept or reject; explicit confirmation for reusable preferences; edits invalidate review
F06Accounts and matrixAccount registration, positioning, audience evidence, unknown followers; independent variants and schedulesRegistration is not OAuth; record actual published URLs and account-specific metrics
F07Products and merchantsPost/image evidence, keywords, links/commands, shops, dated prices, experience, terms and samplesSaved links are not affiliate agreements; unknown stays unknown
F08Services and productsConsultation/digital/physical offers, audience, capacity, deliverables and terms; eight vertical templatesInquiry, fit, questionnaire, booking, delivery, summary, follow-up; receipts guard later stages
F09Export and reviewZIP with HTML/Markdown/JSON/assets; metric snapshots and idempotent order CSVPreserve unknown attribution; refunds affect NOT_PAID commission drafts; no payment
F10Traceable agent executionFrozen context, explicit account/project, selected posts/images, prompt/input versionsQueue/configuration block/run/review/accept/reject/failure with receipts; no silent retry

AI capabilities and execution protocol

Fourteen versioned prompt contracts cover voice, ideas, photo copy, video scripts, revisions, white/green/alpha portraits, logos, covers, product observations, fit, service copy and review. Text uses the Responses API with selected image inputs; images use the Images API. Keys and model names are server environment configuration. Each run requires confirmation of the selected context. Missing configuration creates a blocked task, never simulated output. Live provider execution has not been accepted.

Sources: Responses API, Images API.

UI layout

Landing

The latest user-specified visual reference is Blueberry Bagel: a neutral white/grey canvas, whitespace, split landing layout and structured workspace. Apply original tomato-red, pale-red and small leaf-green accents, without copying its logo or hero. This supersedes the earlier Rumi rainbow direction. A landing brief transfers into the workspace. Case studies illustrate audiences; they do not constrain new creator onboarding.

Workspace

Left navigation, central projects and forms, right agent rail. Modules cover overview, profile, brand assets, history/voice, projects, accounts, products/merchants, services, insights, feedback and tasks. White/grey with tomato-red actions and small leaf-green states; narrow screens move the agent below content.

Controls

Current creator and revision are explicit. Filters/search and counts sit above content. Forms label unknown fields and save explicitly. Conflict responses preserve server state. Generated images require review. Original captions/images fold independently of product associations. Primary original/green/alpha assets remain separate.

Language

Landing and main navigation offer English/Chinese; specification, coverage and case pages are bilingual. Original notes remain in the author's language. Some business form fields remain Chinese; full UI localization is not complete.

User journeys

Shared creative loop

  1. Create a workspace, enter channel/profile, upload authorized photos.
  2. Preserve originals and create white/green/alpha or brand tasks with selected references.
  3. Review real results, record revisions and approve primary assets; unconfigured providers leave tasks blocked.
  4. Import original posts/metrics and select voice evidence; confirm reusable preferences.
  5. Create photo/video projects from new material, drafts and shot plans.
  6. Save versions, incorporate feedback, verify facts, create explicit account variants.
  7. Record schedules, owners and exceptions; publish on the platform and record real URLs/metrics.
  8. Export and review; reuse confirmed learning in the next task.

Lifestyle/product journey

Use post/image evidence for furniture, toys, art and DIY product candidates. Preserve model uncertainty, source URL, merchant, dated price and actual experience. Taobao/1688 access is currently policy-blocked; no alternate tool may circumvent it. Begin with curation and sharing, then authorized sampling, merchant cooperation, distribution and fulfillment.

Knowledge-service journey

Clarify scope, generate qualified inquiries, assess fit, collect a questionnaire, book, deliver, summarize an action plan and follow up. Client details do not automatically enter model context or public assets. Cases require separate consent. Payment remains unconnected.

Other verticals

Pet products require size/use evidence; beauty/fashion require shade/fit and comparable images; travel/outdoor require dated context and ownership; food requires current venue/menu evidence; digital products require versions, licenses and support terms. Eight data-driven templates share the same creative model.

Implementation and constraints

Model and API

SQLite stores per-workspace profile, accounts, assets, archive, projects, variants, products, merchants, offerings, delivery, feedback, metrics and orders. Separate jobs/audit tables retain executions and revisions. Optimistic locking returns HTTP409 instead of overwriting. This is single-owner local isolation, not production multi-tenant authorization.

Core routes: GET /api/bootstrap, POST /api/workspaces, GET /api/w/:id, POST save/assets/import-archive/import-library/import-goods/jobs, POST jobs/:job/run and review, GET export/:project. Mutations validate references and versions. Asset uploads deduplicate by content hash; project ZIP includes readable documents and selected assets.

Running and configuration

Run python3 server.py --port 4176. Bind only to 127.0.0.1. Private data remains in .local, excluded from Git. Configure KEAI_OPENAI_API_KEY, KEAI_TEXT_MODEL and KEAI_IMAGE_MODEL on the server; an explicit HTTPS base URL is optional. No credential means no model invocation. In-chat tools are not automatically website APIs.

Verification and remaining integrations

See coverage and acceptance. Local state and form flows are implemented. Live model calls, social OAuth/auto-publishing, merchant order APIs, automatic reconciliation, payment and full motion-video production remain unaccepted or unconnected. Task creation, account registration and settlement drafts are not evidence of external execution.

Commerce stages

Stage one: independent curation, content and service proposals. Stage two: evidenced merchant cooperation and distribution. Stage three: optional own-brand products and fulfillment. Branvas informs the brand-kit/business flow; none of its supplier or commission infrastructure is assumed connected.

Confirmed access rules

Only the platform administrator Ruby may view and manage all creators. A creator account accesses its own independent workspace. Team subscriptions permit switching only within active seats and explicit workspace assignments. The selector consumes a server-filtered workspace list; sending all identities to clients and hiding them is insufficient.

Authorization covers workspaces, identity assets, media originals, covers, archives, projects, exports, jobs and administration endpoints. New users cannot claim existing studios by matching names. Administrators explicitly bind existing private assets to verified accounts. Team eligibility and seats are server-controlled; revoked access is denied on the next request.

Current state and acceptance limits

Eleven independent local workspaces and 203 image files were imported and hash-verified. Originals and derivatives remain separate. Rejected covers stay archived in the source library and are excluded from newly imported working assets. Import configuration is private and content hashes prevent duplicate files.

The current selector remains a single-owner local management interface, not completed cloud authentication or tenant isolation. Ruby requested formal cloud identity and authorization this round. Free-project quota blocked project creation and pausing the selected old project encountered a provider-state conflict. Dashboard verification remains pending. Real sign-in, cross-workspace API and media denial, team-seat grants and revocation require live verification before completion.

Scenarios

Zhizhi lifestyle case

Use new home photos and real details with approved voice rules. Link furniture, pig toys and art to image-level evidence. Preserve originals and distinguish similar candidates from confirmed purchases. See the case study.

EZ knowledge-service case

Produce content around a scoped 1v1 proposal. Retain receipts through inquiry, questionnaire, booking, delivery, written action plan and follow-up. Client data remains private; case reuse requires separate consent.

Pet example · Bean’s corner

Can my dog stretch out on this bed? Record the dog’s build, stretched length and sleeping position. Measure the usable cushion area and pair a dimensioned photo with a full-body nap shot. Readers can see where all four paws land and judge the fit for their own dog.

Beauty and style example · Calico’s swatch book

Pair two lipsticks with the same white shirt. Label each original photo with the shade number, shirt size and wearer’s shoulder width. Keep the window position, lighting, exposure and white balance consistent. Place the lip photos side by side so readers can compare the finishes.

Travel and outdoors example · Goat’s trail log

Document the gear used on a rainy hike. Mark the date, trailhead, start and turnaround times on a map, then attach photos to the relevant sections. Label each item as bought, borrowed or brand-supplied. Record where it was used and what stayed in the pack.

Food example · Bear’s lunch notebook

Compare lunch and dinner at the same restaurant. For each visit, record the date, order time, menu, price and a photo of the dish served. Caption each photo with the service hours. Give a seasonal end date when staff confirm it, or label the menu as observed on the day of the visit.

New-creator onboarding

Enter name/channel/vertical, confirm management authority, upload originals and create brand/portrait tasks. Approve outputs for reuse. No creator-specific code change is necessary.

Operator-assisted matrix

One parent draft creates independent account variants with positioning, schedules, owners, exceptions, real publication URLs and metrics. Preserve provenance and versions. Do not silently assign older records to a default account.

Existing data

The v0.1 localStorage prototype remains at prototype-v1.html without clearing its key. Configured local imports bring authorized archives and assets into the new backend. New creators do not inherit case-study private records.

Cover studio and creator pilot

Personal creation comes first; operations supports collaboration, and product selection or distribution is optional. The cover studio is an early deliverable within a creator's personal workflow. Ruby SoloTrip is one case, alongside Zhizhi, Dylan Su, EZ and future creators. Each keeps separate identity, assets, covers and typography settings. Ruby's travel topics and appearance are not universal product defaults.

Delivery flow

  1. Enter from the public homepage as a guest, open an existing local studio, or register a creator profile.
  2. Select a creator before choosing RedNote, Douyin, Bilibili, YouTube or another supported platform. Creator selection stays synchronized with the parent workspace.
  3. Reuse Ruby's original UI and controls: destination, category, search, progress, counts, enlarged previews, fonts, tilt, scale, spacing, colors and confirmation. Travel-only filters appear for the Ruby travel case.
  4. RedNote has an independently composed 3:4 feed preview; Douyin and general portrait use 9:16; landscape uses 16:9. Existing PNGs retain their original pixels. Edited platform layouts are previews, not claims of new exports or Canva synchronization.
  5. New presenter covers use fresh original-reference photographs with separate text. Using a cover in a project saves the current titles, platform, font parameters and source-cover ID through the existing local project and version workflow.
  6. New creators can create studios, upload authorized photos and begin their own cover projects without code changes. Unconfigured model tasks remain explicitly blocked by configuration.

Quality and rejected drafts

User-rejected first versions are archived and excluded from active covers, generation references and new-project selection. Original files remain. Restart from original photos and approved references when texture, sharpening, hair or identity fails. Require smooth fine skin and soft light. Requested whitening removes yellow teeth while preserving gaps, individual shapes and natural shading. Inspect faces at native resolution. Keep appearance adjustments person-specific. Apply the approved Chinese font once; never feed the composite back into generation.

Entry points and boundaries

Homepage, guest workspace, local access, registration, pricing and bilingual PRD are linked. Access selects an existing local studio; registration creates a local profile, not a connected cloud account. Guest and local studio use is currently free. Operations-assisted pilot scope and pricing remain unconfirmed. Cloud authentication, model subscriptions, payments and collaboration permissions require separate integrations.

Repository-owned module adapters read explicitly configured local UI and asset sources. Private photographs, actual case images and machine-specific paths stay in .local or their original folders, outside generic Git code. Other environments must configure authorized UI resources and assets rather than inheriting Ruby's private library.

Pilot evidence focuses on time to a usable cover, revision rounds, creator acceptance and repeat use. Operators assist references, revisions and review. Commerce enters only when needed and does not gate personal creation.

Canonical HTML and AI lettering

The studio reuses the canonical HTML with a Douyin format=douyin and glyphs=custom entry. Every creator can use the same 21 fonts and AI lettering option. Font, tilt, size, spacing, color, sample text, confirmation and parameter downloads remain scoped to creator and platform. Reuse the lettering style, but produce a separate layer for each exact title; Ruby’s existing Yinchuan text is not another creator’s title. Transparent lettering tasks require provider setup, actual generation and character-by-character review before acceptance.