id(currency): graph↔ledger reconciliation + supply-audit job (from #2062) #2320

Activity

1. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   source/queue-workerFiled or worked by the queue/worker pilotFiled or worked by the queue/worker pilot

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   meta/follow-upFollow-up spun out of earlier workFollow-up spun out of earlier work

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   effort/mMedium: expected under 1 day of workMedium: expected under 1 day of work

   on Oct 29, 2026
2. developing-today commented on Oct 29, 2026

   

   developing-todayBot

   on Oct 29, 2026 – with developing.today

   Contributor

   More actions

   CODE-1170
3. github-actions

   assigned

   dezren39

   on Oct 29, 2026
4. dezren39

   added

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 29, 2026
5. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   Intake review

   Related: #2062 (design §7), #2317/#2318 (F1/F2 dependencies), #2321 (the PoC whose cluster this audits)

   Notes: Graph↔ledger reconciliation + supply-audit job for the currency control plane. The body carries a full ## Acceptance list (seeded match, injected divergence reported with ids, unresolved user_data_128 reported not ignored), so this pass is labels-only.

   Risks: Reconciliation that auto-fixes drift would hide exactly the corruption it exists to surface — the design's rule (ledger wins on balance, graph flagged for review) must hold.

   Suggested approach: Build after F1/F2; implement audit + link resolution as a scheduled job with operator-surface reporting; test with the seeded-divergence case.

   🤖 Agent note · filed

   • Agent: fleet monitor (repo-fleet-monitor)
   • Session / ID: repo-fleet-monitor run 2026-10-29T18:12Z (13:12 CDT)
   • Found via: monitor reconciliation
   • Task: Duty 2 intake enrichment — labels normalized and meta/enriched applied; acceptance criteria appended to the body only where no acceptance section existed (original body preserved verbatim above it). Still-live check this pass: no merged PR or fix commit explicitly resolving this issue was found in this pass's search.
   • Expectation: see the effort label; done = the acceptance criteria are met.
   • Links: this issue
6. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 3, 2026
7. developing-today commented on Nov 3, 2026

   

   developing-todayBot

   on Nov 3, 2026 – with developing.today

   Contributor

   More actions

   agent-note:v1
   state: triaged (coverage pass)
   Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
   Found via: coverage pass 2026-11-03
8. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 3, 2026
9. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-k
   • Session / ID: task 7891
   • Found via: queue claim
   • Task: Triage issue id(currency): graph↔ledger reconciliation + supply-audit job (from #2062) #2320 (id(currency): graph↔ledger reconciliation + supply-audit job) — execution lane assigned to opencode; handed off to the laptop claimant (opencode-claimant), which launches the bound session that drives task 7891 to its terminal state.
   • Expectation: effort m; done = issue id(currency): graph↔ledger reconciliation + supply-audit job (from #2062) #2320 triaged at current main with evidence, fix path scoped or closed with evidence.
   • Links: task 7891 · issue id(currency): graph↔ledger reconciliation + supply-audit job (from #2062) #2320
10. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    agent-note:v1
    state: triaged
    queue: repo-health-code-pilot
    task: 7891 (completed, outcome triaged)
    by: openchamber-scheduled-lane (repo-worker-code, lane bf419306)
    at: 2026-11-03T19:47Z

    Triage at current main: still live, not started. No supply-audit or graph-ledger reconciliation code exists in pkgs/id/src/currency_poc/ (grep of origin/main for supply audit, reconcile, burn, holders finds only the existing intent-recovery reconciler, which is unrelated).
    Blockers (all OPEN): #2317 (F1 registry + ledger-u32 allocator), #2318 (F2 account factory + system accounts), and #2321 (PoC cluster this job audits). The issue's own "Depends on F1, F2" applies.
    Ordering: implement after F1 and F2 land and the PoC (#2321) gives a seedable cluster. Scope as the body states: supply audit per design #2062 §7.3, transfer link resolution §7.1-7.2, and drift report. Acceptance (seeded match, injected divergence, unresolved link reported) stays as written.
    No fix PR opened from triage and no follow-up task. Labels: removed queue/claimed, work/assigned, status/in-progress; added status/blocked (blocked on #2317/#2318/#2321) and status/triaged.
11. dezren39

    added

    status/blockedQueue or user escalation stateQueue or user escalation state

    status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

    and removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 3, 2026