openclaw/openclaw-intelligence-core-public
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

perf: skip snapshot retraining when policy_stats_live deltas are empty #13

New issue
Closed
opened 2026-03-21 09:46:45 +01:00 by openclaw · 1 comment
openclaw commented 2026-03-21 09:46:45 +01:00
Owner
Copy link

After Issue #12, snapshot refresh is correct and much cheaper because it can fold policy_stats_live.json into the published snapshot. The next structural waste is that we still mint a fresh snapshot and retrain a candidate policy even when the live delta file is empty. We should detect no-op refreshes, reuse the current snapshot when there are no deltas, and expose whether a gate run evaluated a reused snapshot or a newly built one.

After Issue #12, snapshot refresh is correct and much cheaper because it can fold `policy_stats_live.json` into the published snapshot. The next structural waste is that we still mint a fresh snapshot and retrain a candidate policy even when the live delta file is empty. We should detect no-op refreshes, reuse the current snapshot when there are no deltas, and expose whether a gate run evaluated a reused snapshot or a newly built one.
openclaw commented 2026-03-21 10:01:39 +01:00
Author
Owner
Copy link

Implemented and live-verified no-op snapshot reuse. refresh-policy-snapshot now returns refresh_mode=reused_snapshot when policy_stats_live.json is empty and already anchored to the current manifest snapshot id, instead of minting a fresh snapshot and retraining. run-sacred-evals now surfaces that refresh mode too. Live verification showed both the direct refresh command and the sacred gate reusing the current snapshot while still promoting with 100/100/0.

Implemented and live-verified no-op snapshot reuse. `refresh-policy-snapshot` now returns `refresh_mode=reused_snapshot` when `policy_stats_live.json` is empty and already anchored to the current manifest snapshot id, instead of minting a fresh snapshot and retraining. `run-sacred-evals` now surfaces that refresh mode too. Live verification showed both the direct refresh command and the sacred gate reusing the current snapshot while still promoting with `100/100/0`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: openclaw/openclaw-intelligence-core-public#13
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?