taodeng/memory-continuity
1
0
Fork 0
mirror of https://github.com/dtzp555-max/memory-continuity.git synced 2026-07-22 05:25:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Harden heartbeat into forced timeout updates

Browse Source
This commit is contained in:
taodeng
2026-03-09 12:58:54 +10:00
parent ea325f6bcb
commit aaa9c8cca8
3 changed files with 26 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HEARTBEAT.md
+1
View File
@@ -13,6 +13,7 @@
# 2) CURRENT_STATE.md # 2) CURRENT_STATE.md
# 3) known blockers (launch/model/auth/tool/path/scope/policy/external) # 3) known blockers (launch/model/auth/tool/path/scope/policy/external)
# - Then send a real user-visible status update (who / status / output / next). # - Then send a real user-visible status update (who / status / output / next).
# - IMPORTANT: if there is still no fresh evidence, you must still send a timeout update using plain truth (`blocked`, `launch failure`, `no change`, or the exact blocker). Do not stay silent waiting for a better answer.
# - After sending the update, treat the timer as reset from now. # - After sending the update, treat the timer as reset from now.
# - If the project state is `done`, `paused`, `failed`, or `cancelled`, do not send heartbeat progress nudges. # - If the project state is `done`, `paused`, `failed`, or `cancelled`, do not send heartbeat progress nudges.
# #
memory/project-heartbeat-state.json
+7 -6
View File
@@ -1,14 +1,15 @@
{ {
"version": 1, "version": 1,
"activeProject": { "activeProject": {
"name": "Geopolitical Turbulence Trapper restart", "name": "ACP + Codex smoke test",
"state": "armed", "state": "armed",
"timeoutMin": 10, "timeoutMin": 15,
"lastUserVisibleUpdateAt": "2026-03-09T07:04:00+10:00", "lastUserVisibleUpdateAt": "2026-03-09T12:58:00+10:00",
"lastCheckAt": "2026-03-09T07:04:00+10:00", "lastCheckAt": "2026-03-09T12:58:00+10:00",
"trackedWorkers": [ "trackedWorkers": [
"main" "main",
"codex (ACP)"
], ],
"notes": "Tao approved restarting the project at 07:04 under the new evidence-gated workflow. Restart begins in dispatching state, with main owning the Milestone 2 restart directly instead of pretending delegated workers are active. Upgrade only after fresh visible execution evidence appears; otherwise mark blocked on launch/stall rather than sending empty progress updates." "notes": "Tao approved trying a harder anti-silence rule. This project is now the active heartbeat test. If 15 minutes pass without fresh ACP execution evidence, main must still send a user-visible timeout update with blocked/no-change/plain blocker wording instead of staying silent. Current known blocker: acpx non-interactive permissions likely block writes/exec in ACP smoke tests."
} }
} }
skills/project-heartbeat/SKILL.md
+18
View File
@@ -67,6 +67,24 @@ If 10 minutes pass with no meaningful update while the project is active:
4. send a user-visible update 4. send a user-visible update
5. return to `armed` if still active, else `closed` 5. return to `armed` if still active, else `closed`
## Hard anti-silence rule
This is stricter than a reminder.
If the timeout window expires and there is still no fresh execution evidence, main must still send a user-visible update.
Allowed timeout updates when there is no new evidence:
- `blocked`
- `launch failure`
- `no change`
- `still waiting on <specific blocker>`
Disallowed timeout behavior:
- saying nothing
- waiting for a "more complete" answer before updating Tao
- reusing old optimistic wording like `in_progress` without fresh evidence
Silence after timeout is itself a process failure.
## Worker check order ## Worker check order
When timeout fires, check in this order: When timeout fires, check in this order:
1. worker session history / visible traces 1. worker session history / visible traces