Files
approved-plan-continuity-ha…/README.md

80 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Approved Plan Continuity Hard Gate
## 中文說明
這個 repo 是從較大的 OpenClaw workspace 中抽出的焦點工作流成果,主題是:
- **approved plan continuity hard-gate**
- **dispatch receipt binding**
- **anti-blackhole / completion-delivery watchdog groundwork**
目標是避免兩類問題持續發生:
1. **continuity failure / auto-next break**
2. **subagent anti-blackhole / fake timeout**
## 目前已完成
### A. Continuity hard-gate
- continuity evaluator
- dispatch receipt binding groundwork
- `derivedAction` continuity binding
- `dry_run_dispatch` 不得冒充真 receipt
- fake receipt authority 最小收緊
- hook integration 已接入
### B. Anti-blackhole watchdog recovery
- watchdog status recompute
- 最小 recovery decision 閉環:
- `fetch_history`
- `respawn`
- `blocked`
- owner-visible reporting payload
- scenario matrix tests
## 目前限制
- continuity 仍偏 prompt-level hard-gate integration
- watchdog recovery 目前驗收的是 decision / reporting / test slice不是 live integration
## 下一步建議
1. continuity runtime enforcement hardening
2. watchdog live recovery integration
3. escalation / receipt contract hardening
---
## English Description
This repository is a focused export from a larger OpenClaw workspace covering:
- **approved plan continuity hard-gate**
- **anti-blackhole / completion-delivery watchdog recovery**
## Current State
### A. Continuity hard-gate
- continuity evaluator
- dispatch receipt binding groundwork
- `derivedAction` continuity binding
- `dry_run_dispatch` no longer accepted as a real receipt
- fake receipt authority tightened
- hook integration present
### B. Anti-blackhole watchdog recovery
- watchdog status recompute
- minimal recovery-decision loop:
- `fetch_history`
- `respawn`
- `blocked`
- owner-visible reporting payload
- scenario matrix tests
## Current Limitations
- continuity remains prompt-level rather than engine-level
- watchdog recovery is validated as a decision/reporting/test slice, not live execution integration
## Suggested Next Steps
1. continuity runtime enforcement hardening
2. watchdog live recovery integration
3. escalation / receipt contract hardening