turinglambdaai · Oct 22, 2026 · Oct 22, 2026 · Oct 22, 2026 · Oct 22, 2026 · Oct 22, 2026
diff --git a/AGENTS.md b/AGENTS.md
@@ -24,3 +24,7 @@ turinglambdaai 家族主站（jrtx.site）——纯静态 HTML/CSS 单页，零
 - 零依赖：不引外部 JS/CSS 框架；字体只走自托管（禁 Google Fonts，大陆阻塞首屏）。
 - 页面含 data-i18n 双语文案，改动须中英同步。
 - 头部不放版本号（版本信息只在各产品仓库/About 承载）。
+
+## 产品组合与交付治理
+
+组合归属以 `PORTFOLIO.md` 为准；交付基线见 `docs/PRODUCT-STANDARD.md`，本轮逐产品证据与 issue 入口见 `docs/PRODUCT-REVIEW-2026-10.md`，主页改版执行简报见 `docs/HOME-PAGE-PLAN.md`。库间依赖图仍以 Keel 的 `docs/family-architecture.md` 为准，不在主站另造协议或复制各仓实施队列。
diff --git a/PORTFOLIO.md b/PORTFOLIO.md
@@ -6,8 +6,10 @@
 **总原则：收费归属是前置决策，一开始就定死。** 哪些产品适合收费（轨道 1–3）、哪些
 永久免费（轨道 4），在进入推广阶段之前确定并随本档维护；推广开始后不再改结构。
 当前全部产品处于打磨期，尚未进入推广阶段，不急于变现。授权形态现在定型（避免后期
-反复），收费动作后置到产品稳定之后；commerce 部署后，所有付费形态统一走
-offer/policy/issuance，产品侧零改动。
+反复），收费动作后置到产品稳定之后；commerce 部署后，付费产品逐一接入统一
+offer/policy/issuance；每个产品仍需完成凭据导入/恢复、信任库、本地权益判断和更新资格验收，
+不能把服务部署当作产品接入完成。交付基线见 [PRODUCT-STANDARD](docs/PRODUCT-STANDARD.md)，
+逐产品差距与执行入口见 [本轮审查](docs/PRODUCT-REVIEW-2026-10.md)。
 
 ## 轨道与授权形态
 
@@ -33,7 +35,7 @@ offer/policy/issuance，产品侧零改动。
 | Booklight | AGPL-3.0 | 永久买断 + 更新窗 + 试用；模型自带 key，不自建托管 |
 | PodLens | AGPL-3.0 | 同 Booklight |
 | Payback | MIT（桌面） | **小额买断走量**：桌面端永久免费（口碑漏斗）；移动端（iOS/Android，等 rivet 移动宿主就绪）收一次性小额客户端费用——App Store 小工具买断是成熟走量档，源码仍开放、官方分发是便利收费 |
-| RegexMate | BUSL-1.1 → MIT（2030-10-22 或各版首发四周年） | 专业/团队向收费：个人使用永久免费（含 CI 与 agent 调用），团队/商业场景（CI 规模化、共享规则包、审计）走官方 Pro。换照 2026-10-22 完成（≤0.7.0 保持 MIT） |
+| RegexMate | BUSL-1.1 → MIT（2030-10-22 或各版首发四周年） | 专业/团队向收费：个人使用永久免费（含 CI 与 agent 调用），新增的团队协作便利（共享规则包、审计、官方支持）可设计为 Pro；现行 LICENSE Additional Use Grant 已允许内部生产、CI 和 agent 使用，不能按企业身份对这些既有权利追收费。换照 2026-10-22 完成（≤0.7.0 保持 MIT） |
 
 ### 3. 免费 + 托管 Pro — 只有真实服务成本才配收订阅
 
@@ -60,7 +62,9 @@ offer/policy/issuance，产品侧零改动。
 | Threadly | AGPL-3.0 | Racket 社区工具；保活，远期可移交社区 |
 | Pitboard | MIT | 内容站保活；若汽车线内容获客价值不成立，可归档 |
 
-RelayPilot：架构 Alpha、无公开仓库，网络工具敏感度高——私有观望，不进收费计划。
+RelayPilot：架构 Alpha，已有可访问源码仓库，但不授予开源许可；尚无可运行的 VPN 产品。维持实验观察，不进近期收费计划。
+
+Keepsake / Moonbeam：用户已确认仓库已删除，退出当前产品组合。清理主站残留卡片、进度入口和文档引用；不再安排源码补齐、恢复开发或商业化。
 
 ### 基础设施 — 全部开源，是产品线的放大器，不是利润中心
 
@@ -101,3 +105,7 @@ Racket 协议与数据格式库族（uds / isotp / dbc / crc / pcap / …）。
 - 三个检查面：主站卡片 ↔ 产品 README ↔ GitHub About，改文案必须三面核对。
 - 产品 README 必带 license badge；授权形态以本文档与产品站为准。
 - 价格只进产品仓库 `PRICING.md`，且在收费开始时（而非之前）发布。
+- 组合分类可在推广前基于证据调整；推广后不追溯收回已承诺的免费能力和已授予的许可。新付费能力明确标识，不以重写或换宿主重置承诺。
+- Payback 桌面永久免费是本组合决策；旧 PRICING/产品站的桌面 Pro 预告必须撤下，移动端官方商店分发收费另行验证商店权益，不预售未交付平台。
+- 暂不以移动端拉长每个产品的队列。保活产品只修兼容、安全、文档和基本交付问题。
+- 主站和产品站的改版依据 [主页规划](docs/HOME-PAGE-PLAN.md)，不把技术栈一致性当作终端用户卖点。
diff --git a/README.md b/README.md
@@ -83,3 +83,7 @@ turinglambdaai.github.io/
 185.199.110.153
 185.199.111.153
 ```
+
+## Maintainer map
+
+Product investment and commercial categories live in [PORTFOLIO.md](PORTFOLIO.md). The [delivery standard](docs/PRODUCT-STANDARD.md), [product review](docs/PRODUCT-REVIEW-2026-10.md), and [homepage brief](docs/HOME-PAGE-PLAN.md) route architecture and product work to its owning repository.
diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -83,3 +83,7 @@ turinglambdaai.github.io/
 185.199.110.153
 185.199.111.153
 ```
+
+## 维护导航
+
+产品投入和商业分类以 [PORTFOLIO.md](PORTFOLIO.md) 为准。[交付标准](docs/PRODUCT-STANDARD.md)、[逐产品审查](docs/PRODUCT-REVIEW-2026-10.md)和[主页规划](docs/HOME-PAGE-PLAN.md)将架构与产品工作路由到实际负责的仓库。
diff --git a/docs/HOME-PAGE-PLAN.md b/docs/HOME-PAGE-PLAN.md
@@ -0,0 +1,77 @@
+# Portfolio and product front doors / 主站与产品主页规划
+
+Status: implementation brief, 2026-10-23. Preserve the static, bilingual,
+self-hosted-font architecture. Implement separately from active product work.
+
+## jrtx.site information architecture
+
+The current page leads with the author and then presents a long technical
+catalog. Keep the writing/community identity, but give a visitor a faster route
+to a useful product. First screen: a concrete independent-software promise,
+one short author sentence, primary “Explore tools / 寻找工具” and secondary
+“Read the writing / 阅读文章”. Keep the Chinese WeChat path and English GitHub
+path as secondary community choices.
+
+Below it, show at most three featured product stories, initially Taskly,
+Fulcrum and Booklight when their linked release and primary flow are verified.
+Choose the actual featured set from readiness, not this list alone. Each story
+contains one user outcome, a real product screenshot, availability, current
+business model in words and one primary CTA. Automotive tools get a separate
+professional section. The complete catalog follows in compact categories:
+Productivity, Reading & Learning, Automotive, Community & Writing. Put
+experimental/unreleased products in a clearly labelled “In the lab” group.
+
+Do not give Alpha, maintenance, and released products identical “Download”
+weight. Released products link to their product site; unreleased products use
+“View progress”. Frameworks live in a separate “For builders” section, with the
+Rivet/Glaze choice and Keel/Permit/Commerce roles stated briefly. Framework
+names become secondary metadata on product cards, not the sales argument.
+
+## Product page template
+
+1. Hero: audience + job + outcome, real screenshot, platform/maturity line,
+   primary download/try CTA and secondary documentation/demo.
+2. Three short task stories with real inputs/results; show the core workflow.
+3. Platform and installation matrix: OS minimums, architecture, update behavior,
+   first-launch trust status, current verified release link.
+4. Privacy and AI: local data, what is transmitted, BYOK versus hosted, provider
+   choice, key storage and estimated usage controls.
+5. Commercial model: available Free/Pro differences, license/source link,
+   trial/update-window/renewal/refund/support terms when actually offered.
+   Before sales begin use current free availability and an honest roadmap;
+   no numeric teaser prices or dead Buy buttons.
+6. Trust footer: changelog, user guide, feedback, private security route,
+   backup/export help and source/license as applicable.
+
+Do not promise a support SLA without operational capacity. Do not copy
+competitor claims, old stack descriptions, platform counts or feature lists
+from previous rewrites. Every material claim has a source file/release/test
+owner and last-checked SHA in the implementation issue.
+
+## Visual and interaction rules
+
+Retain the warm editorial identity and generous spacing. Use a strong type
+hierarchy, concise labels, restrained motion and product-specific imagery.
+Reduce dense paragraphs in cards. Support light/dark mode, visible keyboard
+focus, semantic headings, meaningful image text, reduced motion, long Chinese
+and English labels, 320/375/768/1440 px widths and 200% zoom. No external fonts,
+analytics SDK, carousel, fake testimonial, fake usage counter or new framework
+is needed. The maintainer documents are not navigation for ordinary customers.
+
+## Release and verification
+
+Compare four surfaces: main-site card, product page, product README and GitHub
+About; current public release is the evidence anchor. Check both languages,
+all CTA targets, asset/OS mapping, empty/latest-release failure, HTML balance,
+keyboard navigation, overflow and image loading. Review representative mobile
+and desktop screenshots, including dark mode. A successful Pages deployment
+does not prove the content is correct; compare deployed HTML to the intended
+source SHA. Preserve the last deployed commit for rollback.
+
+First fix the observed gPTP Studio old GTK/WebView claims, Payback desktop-Pro
+promise and source/license wording conflicts. Then ship the main-site hierarchy,
+then the commercial/consumer canary product pages, then the remaining catalog.
+Keepsake and Moonbeam were confirmed deleted by the owner. Remove their
+remaining cards, progress CTAs, navigation and bilingual text from the main
+site and current product catalog. Do not retain them as upcoming products or
+create source-recovery work for them.