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

audit: carry compaction-lineage metadata into candidate policy and sacred gate artifacts #16

New issue
Open
opened 2026-03-21 10:35:10 +01:00 by openclaw · 0 comments
openclaw commented 2026-03-21 10:35:10 +01:00
Owner
Copy link

After Issue #15, exact compaction lineage is enforced in the manifest and refresh logic, but that lineage is not yet copied into policy_candidate.json or the sacred gate result artifact. We should propagate last_exact_compaction_at, base_compaction_snapshot_id, and related freshness metadata into the candidate policy and gate outputs so later audits can explain why a given candidate policy was considered fresh or rebuilt.

After Issue #15, exact compaction lineage is enforced in the manifest and refresh logic, but that lineage is not yet copied into `policy_candidate.json` or the sacred gate result artifact. We should propagate `last_exact_compaction_at`, `base_compaction_snapshot_id`, and related freshness metadata into the candidate policy and gate outputs so later audits can explain *why* a given candidate policy was considered fresh or rebuilt.
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#16
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?