Skip to content

id: investigate: BitTorrent-style chunk retrieval for graph objects #2050

Closed

Description

@dezren39

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.

Activity

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

    @developing-today
    Contributor
  3. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Parent epic: #2056 — ID platform expansion (2026-10-28 directive).

  4. added
    kind/questionQuestion or design decision to resolve
    source/humanFiled directly by a human
    priority/highImportant and time-sensitive
    effort/mMedium: expected under 1 day of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 29, 2026
  5. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    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).

  6. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    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.

  7. removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  8. 9 remaining items

  9. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    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').

  10. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 30, 2026
  11. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  12. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    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):

    This issue closes when PR #2811 merges (it carries Closes #2050).

  13. added a commit that references this issue on Oct 30, 2026
  14. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done

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)effort/mMedium: expected under 1 day of workkind/questionQuestion or design decision to resolvemeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/humanFiled directly by a human

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions