Skip to content

task(licensing): lawyer-question packet — the five open questions on external GitHub content #6055

Open

Description

@dezren39

Parent: #6024 (licensing gate for the external corpus). Research source: prior-art doc ~/workspace/scratch/atlas-ingestion-brief-2026-11-04/prior-art-research.md (2026-11-04). Follow-up 34 (Cluster 6).

Task

Package the five questions the GitHub ToS text does not settle (from the gate research, Cluster 6 of the prior-art doc) for one lawyer review session. Per the gate's answered-provisional framing on #6024: the external design proceeds on the zone rules and Zones 2–3 full text stays personal-search-only meanwhile; this packet is the path to lifting that restriction deliberately. The metadata layer does not wait on it.

  1. Does D.6's inbound=outbound reach issue/PR/discussion comment text, or only contributed files/patches?
  2. Is a private, single-user, non-commercial search index (embeddings + stored text + snippet display to the owner only) over others' public comments fair use in the US? Does storing embeddings change the analysis vs storing text?
  3. What changes if the corpus is ever queried by anyone else (agents acting for Drew? family? a future ID-graph publication)? Where exactly is the redistribution line — snippets in answers? full text in an export?
  4. EU/UK exposure: do text-and-data-mining exceptions apply to a US-based personal user, and do GitHub's terms or repo-level signals constitute an opt-out?
  5. What deletion/takedown process should the corpus implement to stay on the right side of D.5's license-termination logic (the deletion-propagation design, sibling under research(licensing): may we ingest external GitHub comments/discussions into Atlas? — gate for the external corpus #6024, is the engineering half)?

Done looks like

A packet doc (questions + the ToS excerpts + the zone policy) ready to hand to a lawyer, linked from #6024 and the policy decision (sibling under #6024).

Activity

  1. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  2. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  3. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  4. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  5. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  6. added
    queue/claimedQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 5, 2026
  7. 151 remaining items

  8. added
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 8, 2026
  9. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    {"event":"picked_up","worker":"repo-worker-code","queue":"repo-health-code-pilot","task_id":12993,"lane":"02cafe76-eafd-4d0b-aaa6-2b7a737d68dc","note":"Claimed by OpenChamber scheduled lane. Fresh revalidation: #6055 OPEN, no hard-stop labels, no open PR resolving it, and no packet document found in doc/. Linked #6024 research confirms the five open counsel questions and provisional three-zone policy; #6052 remains OPEN and user/escalated, but that ruling does not block preparing the lawyer packet. Resuming at current origin/main; preserve scope as source-backed questions, not legal advice or posture ratification."}

  10. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    {"event":"pr_opened","worker":"repo-worker-code","queue":"repo-health-code-pilot","task_id":12993,"lane":"02cafe76-eafd-4d0b-aaa6-2b7a737d68dc","pr":7804,"note":"The lawyer-review packet is ready in PR #7804: doc/2026-11-08T20-11-41Z_legal_external-github-content-lawyer-review/2026-11-08T20-11-41Z_legal_external-github-content-lawyer-review.md. It covers all five questions and links current GitHub ToS/API/AUP, US, EU, UK, and deletion sources. It is not legal advice and does not ratify #6052. PR is OPEN at 5aab90b; basic CI is queued. #6055 will close when the PR merges."

  11. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    {"event":"done","worker":"repo-worker-code","queue":"repo-health-code-pilot","task_id":12993,"lane":"02cafe76-eafd-4d0b-aaa6-2b7a737d68dc","pr":7804,"note":"Task 12993 completed as pr_opened. PR #7804 is OPEN at 5aab90b and linked from #6055, #6024, and #6052. Basic CI remains QUEUED; no CI wait or merge was part of this packet-delivery outcome. Queue labels set at pickup were removed; #6055 remains OPEN until the PR merges. Sandbox backlog and sweep-log bookkeeping are deferred to fleet reconciliation per lane instructions."}

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions