From 3233770e54eca0737e7c536f9dd70f4b5f240fa5 Mon Sep 17 00:00:00 2001 From: "Alice (OpenClaw)" Date: Wed, 13 May 2026 11:17:02 +0800 Subject: [PATCH] =?UTF-8?q?docs:=20fix=20current=20status=20section=20/=20?= =?UTF-8?q?=E4=BF=AE=E6=AD=A3=20README=20=E7=9B=AE=E5=89=8D=E7=8B=80?= =?UTF-8?q?=E6=85=8B=E6=8F=8F=E8=BF=B0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c297f4e..a7b1853 100644 --- a/README.md +++ b/README.md @@ -130,7 +130,14 @@ Phase 1 可能至少需要以下幾層: - repo 已建立 - README 已補成正式雙語說明 -- 技術設計與實作尚未開始 +- 專案範圍已固定為 Telegram-only +- 核心設計文件已建立(state / policy / callback contract / OpenClaw adapter / PoC plan) +- Telegram + OpenClaw PoC 已成功打通: + - assistant 回覆可附按鈕 + - callback 可接收 + - state 可持久化 + - stop/continue 已能影響後續行為 +- 目前正往可維護、可重現的正式實作路徑收斂 --- @@ -261,3 +268,5 @@ Phase 1 will likely need at least these layers: - scope narrowed to Telegram-only - Telegram/OpenClaw PoC has succeeded - PoC success report: `reports/telegram-openclaw-poc-success.md` +- core design documents now exist (state / policy / callback contract / OpenClaw adapter / PoC plan) +- the current effort is focused on turning the successful PoC into a cleaner, maintainable implementation path