research(atlas): overlap budget experiment — 0% / 10% / 20% overlap vs golden-set recall and index size #6039

Activity

1. dezren39

   added

   area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operations

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1704
3. 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

   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

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

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane openchamber-scheduled-lane
   • Session / ID: task 10405
   • Found via: queue claim
   • Task: Triage issue research(atlas): overlap budget experiment — 0% / 10% / 20% overlap vs golden-set recall and index size #6039 — verify the overlap-budget experiment remains a distinct research deliverable, and record dependencies on the golden-set and chunk-policy work.
5. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage complete

   • Agent: queue worker (repo-worker-code), lane openchamber-scheduled-lane
   • Session / ID: task 10405
   • Found via: queue claim (coverage-audit requeue)

   Triage of issue #6039 at current main (verified 2026-11-05):

   • Issue research(atlas): overlap budget experiment — 0% / 10% / 20% overlap vs golden-set recall and index size #6039 is OPEN, with no hard-stop labels or matching PR. Current main is 04f78696abfbdf6567f58e623d80520436f002fa; targeted search found no experiment result in pkgs/atlas-search or doc. This is a research deliverable, not a code defect.
   • Keep the experiment distinct: compare 0/10/20% overlap per source type against recall on the golden set and report index-size/embed-cost impact. Research input in the design(atlas): delta-only ingestion + offset embeds — land only changes; span-anchored chunks with non-doubling joins #6028 thread is not the experiment result. Do not conflate this with research(atlas): CDC feasibility at embedding scale — FastCDC with ~512-token targets vs the span approach #6040 (CDC feasibility).
   • Ordering: the recall comparison depends on the golden set defined by sibling design(atlas): retrieval statistics, result feedback, and query traces — top-K survival, thumbs + essays, per-stage scores #6027; design(atlas): retrieval statistics, result feedback, and query traces — top-K survival, thumbs + essays, per-stage scores #6027 is open and currently has task 10394 handed to the opencode lane, so this triage does not touch that work. research(atlas): overlap budget experiment — 0% / 10% / 20% overlap vs golden-set recall and index size #6039 results feed parent design(atlas): delta-only ingestion + offset embeds — land only changes; span-anchored chunks with non-doubling joins #6028 chunk-boundary policy.
   • The experiment can prepare representative per-source corpus slices and size/cost measurement, then use design(atlas): retrieval statistics, result feedback, and query traces — top-K survival, thumbs + essays, per-stage scores #6027 golden-set cases for recall scoring. Issue research(atlas): overlap budget experiment — 0% / 10% / 20% overlap vs golden-set recall and index size #6039 itself remains the research work item; no separate follow-up task is needed.
6. dezren39

   added

   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 5, 2026
7. github-actions

   assigned

   dezren39

   on Nov 5, 2026