Back to Details

re0-work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Start over from what the previous cycle proved, not from what it happened to build.
从上个周期验证有效的内容重新开始，而非基于之前碰巧构建的产物。

Goal

目标

re0-work
is a controlled restart. It keeps earned knowledge and refuses to copy forward accidental architecture. Starting from scratch is not amnesia: contracts, schemas, vocabulary, real-surface tests, quality gates, and negative corpus survive when they earned it. Scaffold, explanatory UI, debug panels, shallow generated content, and code whose only value was learning what not to do do not.
re0-work
是一种可控的重启方式。它保留已积累的有效知识，拒绝沿用偶然形成的架构。从零开始并非全盘遗忘：契约、模式、术语、真实场景测试、质量准入标准和负面语料库，只要经过验证就会被保留。而脚手架、说明性UI、调试面板、表层生成内容，以及仅用于学习“不应做什么”的代码则会被舍弃。

Workflow

工作流程

  1. Read the current plan, any lessons or re0-memo notes, local domain notes, QA evidence, and any user complaint that triggered the restart.
  2. Identify what to preserve: contracts, schemas that survived QA, quality gates, vocabulary, reusable services, real-surface tests, and negative corpus.
  3. Identify what to discard: explanatory UI, debug panels, scaffold, shallow generated content, accidental abstractions, and code whose only value was learning what not to do.
  4. Name the first quality gate before planning code.
  5. Write a v0 skeleton plan with one complete vertical loop.
  6. Build only the first loop until it clears the gate.
  1. 阅读当前计划、所有经验总结或re0-memo笔记、本地领域文档、QA验证证据，以及触发重启的用户反馈。
  2. 确定需保留的内容：契约、通过QA验证的模式、质量准入标准、术语、可复用服务、真实场景测试和负面语料库。
  3. 确定需丢弃的内容：说明性UI、调试面板、脚手架、表层生成内容、偶然形成的抽象，以及仅用于学习“不应做什么”的代码。
  4. 在规划代码前，确定首个质量准入标准的名称。
  5. 编写包含完整垂直循环的v0框架计划。
  6. 仅构建首个循环，直至其通过准入标准。

Rules

规则

  • Starting from scratch means no copy-forward unless the artifact earned it.
  • One complete vertical loop beats many shallow surfaces.
  • Preserve provenance in local docs, not in the shipped product.
  • Do not rebuild around a vague lesson. Turn it into a gate or leave it out.
  • Do not delete negative corpus; archive or reference it where the next cycle will see it.
  • If a reusable module survives, name the contract that proved it survives.
  • 从零开始意味着除非工件经过验证，否则不得直接沿用旧内容。
  • 一个完整的垂直循环优于多个表层功能。
  • 在本地文档中保留来源信息，而非在交付产品中。
  • 不要围绕模糊的经验重新构建。将其转化为准入标准，或直接舍弃。
  • 不要删除负面语料库；将其归档或置于下一个周期可见的位置供参考。
  • 如果某个可复用模块被保留，需明确标注验证其有效性的契约。

Verification

验证

Before finishing:
  1. The preserve/discard split is explicit and evidence-backed.
  2. The new v0 plan has one complete vertical loop and a named first gate.
  3. No old architecture is copied forward merely because it exists.
  4. A fresh builder can start without rereading the failed codebase.
完成前需确认：
  1. 保留/丢弃的划分明确且有证据支持。
  2. 新的v0计划包含一个完整的垂直循环和已命名的首个准入标准。
  3. 不会仅因旧架构存在就直接沿用。
  4. 新的开发人员无需阅读失败的旧代码库即可开始工作。