Skip to content

id: protocol v1 phase 4 — retention and compaction for the event store (#2036) #3797

Open

Description

@dezren39

Phase 4 of the #2036 protocol v1 synthesis, from the #2034 investigation (§7): pkgs/id event_store today keeps every verified event forever (event_store/mod.rs:4-23 — no TTL/compaction/GC). Implement the first per-class retention/compaction path: live-class segments compact to their checkpoint residue (checkpoint events + hashes remain), durable classes untouched, per the class table in doc/2026-10-29T10-45-00Z_investigation_ephemeral_live_data_retention §3/§7. Hard constraints: compaction must preserve fork proofs and waiting-pool after resolution (event_store/mod.rs:12-22). Acceptance: compaction tests per class; a compacted store still verifies chains and resolves fork proofs; durable-class events are never compacted.

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 1, 2026
  2. developing-today commented on Nov 1, 2026

    @developing-today
    Contributor
  3. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · state: picked up

    • Agent: OpenChamber scheduled lane (repo-worker-code)
    • Session / ID: queue task 5787 (repo-health-code-pilot)
    • Found via: atomic queue claim
    • Task: Implement per-class event-store retention/compaction for live-class segments, preserving checkpoint residue, fork proofs, and waiting-pool resolution; durable classes remain untouched.
  4. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 2, 2026
  5. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

  6. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked (clarification)

  7. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    agent-note:v1 — holder: repo-worker-code (OpenChamber scheduled lane), at 2026-11-02T13:44:59Z. event: picked-up; task: 5787; queue: repo-health-code-pilot.

  8. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    agent-note:v1 — holder: repo-worker-code (OpenChamber scheduled lane), at 2026-11-02T13:45:04Z. event: parked; task: 5787; queue: repo-health-code-pilot. Blocked on #3794's signed session.checkpoint event contract landing; preserve the defined checkpoint residue rather than inventing one. Revalidate #3797/#3794 and ownership before resuming; no source or worktree changes this run.

  9. 114 remaining items

  10. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 5787 (small_fix, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  12. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  13. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    kind: picked-up
    task: 5787
    worker: repo-worker-code
    lane: 02cafe76-eafd-4d0b-aaa6-2b7a737d68dc
    at: 2026-11-04T01:06:00Z

    Resuming task 5787 from the prior verified dependency-gate checkpoint. Fresh GitHub state: #3797 is OPEN with no hard-stop labels; prerequisite #3794 is CLOSED and its implementation PR #4627 is MERGED. This lane will fetch/fast-forward main, verify the checkpoint schema/golden vectors are present, then continue only if the gate is satisfied. Current labels already reflect the claimed state: queue/claimed, status/in-progress, and work/assigned.

  14. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    kind: blocked
    task: 5787
    worker: repo-worker-code
    lane: 02cafe76-eafd-4d0b-aaa6-2b7a737d68dc
    at: 2026-11-04T01:22:00Z

    Packet defect: phase 4 cannot safely choose events to compact yet. Fresh origin/main (a51be0e) contains the #3794 session.checkpoint schema and pinned golden-vector test, and #3794/PR #4627 are closed/merged. However, the #2036 design §4.6 requires compaction to use the channel/session retention policy and phase-2/3-declared metadata. Current ChainExt/SessionCheckpoint contain no retention class, policy, or expiry. Issues #3795 and #3796 are still OPEN with no linked PRs (#3795 is user/escalated); there is no safe eligible-event classifier. No source edits or tests were made.

    Disposition: task 5787 blocked as packet_defect; current lane labels reflect blocked state. Resume after the packet names the retention classifier/policy/expiry contract and dependencies on phases 2/3 are satisfied, then revalidate fresh. Task worktree /home/user/git/fleet/5787 is clean on queue/5787-3797-event-store-retention at a51be0e.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)queue/blockedQueue or user escalation statesource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions