Repository navigation
Closed
Labels
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 workkind/questionQuestion or design decision to resolveQuestion or design decision to resolvemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitiveImportant and time-sensitivesource/humanFiled directly by a humanFiled directly by a human
Description
LIST 14b. A chat link (or any app link) must be openable even when you don't hold the data: the ID is found on someone's public server, and the file is pulled from multiple holders in chunks, BitTorrent-style. Investigate: holder discovery for an object ID, chunk integrity against the object's hashes, partial-holder behaviour, and how this composes with Iroh's existing transfer machinery vs needing a new swarm layer. Deliverable: retrieval flow + gap list.
Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.
Acceptance criteria
- A markdown investigation doc is linked from this issue covering: holder discovery for an object ID, chunk integrity against the object's hashes, and partial-holder behaviour.
- The doc states explicitly how the retrieval flow composes with Iroh's existing transfer machinery vs needing a new swarm layer, with a gap list.
- Follow-up issues are filed for anything buildable the investigation identifies.
Metadata
Metadata
Assignees
Labels
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 workkind/questionQuestion or design decision to resolveQuestion or design decision to resolvemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitiveImportant and time-sensitivesource/humanFiled directly by a humanFiled directly by a human
Activity
developing-today commentedon Oct 29, 2026
CODE-971
dezren39 commentedon Oct 29, 2026
Parent epic: #2056 — ID platform expansion (2026-10-28 directive).
dezren39 commentedon Oct 29, 2026
Intake review
Fleet monitor intake (2026-10-29) — verified still live: no merged PR or commit implements this yet; the filing audit/decision record it cites is current.
Notes: ID-program investigation (LIST 14b) under Drew's 2026-10-28 directive; part of the batch filed 2026-10-29 ~01:00Z (cf. enriched siblings #2051–#2058). Deliverable is the investigation doc + gap list, not the feature. No merged PR or commit implements it — it is a design investigation, verified live as open and unstarted.
Suggested approach: Start from Iroh's existing blob/transfer machinery and identify exactly where multi-holder chunk retrieval diverges from it.
Risks: Scope creep into building the swarm layer — the program rule is: PoC only where the design calls for one, never the permanent feature on an unreviewed PoC.
Labels normalized by the monitor; acceptance criteria appended to the body (original text preserved verbatim above it).
dezren39 commentedon Oct 29, 2026
Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3356 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.
9 remaining items
dezren39 commentedon Oct 30, 2026
Queued: repo-health-code-pilot task 3924 (2026-10-30), wave-2 follow-on. The 2026-10-29 triage verified this issue and recorded 'write the investigation' as the next step; this task is that write — investigation doc PR under doc/, follow-up issues for buildable pieces, close with the doc link. Ordered by Drew ('queue unrun').
dezren39 commentedon Oct 30, 2026
🤖 Agent note · picked up
doc/in this repo via PR, link it from this issue, and close the issue with the document link.dezren39 commentedon Oct 30, 2026
Investigation published — design doc in repo
The wave-1 investigation for this issue (posted here 2026-10-29) is now published as a repo design doc via PR #2811 (queue task 3924, wave-2 write):
doc/2026-10-30T19-28-00Z_investigation_bittorrent_chunk_retrieval_for_graph_objects/2026-10-30T19-28-00Z_investigation_bittorrent_chunk_retrieval_for_graph_objects.md— docs: BitTorrent-style chunk retrieval investigation (#2050) #2811getpath, and blob-gate wiring.This issue closes when PR #2811 merges (it carries
Closes #2050).Merge pull request #2811 from developing-today/queue/3924-2050-bittor…
dezren39 commentedon Oct 30, 2026
🤖 Agent note · done
a01996f7). Doc:doc/2026-10-30T19-28-00Z_investigation_bittorrent_chunk_retrieval_for_graph_objects/2026-10-30T19-28-00Z_investigation_bittorrent_chunk_retrieval_for_graph_objects.md. Verdict: no new swarm layer or integrity scheme — iroh-blobs provides range requests, bao verified streaming, and partial-blob state; the gaps are holder discovery, multi-provider scheduling, and blob-gate wiring. Follow-ups id: holder discovery for blob hashes — provider table, gossip announcements, wire the blob gate #2260–id: investigate global (Mainline DHT) content discovery for public worlds #2263 (filed in wave 1) mapped in doc §8; hand-off for id: design: ID chat v1 #2051 in §9. Codex review on the PR completed with no findings; doc-only PR (no CI workflows triggered, same as sibling docs: IRC-first chat on ID investigation (#2049) #2807).