Skip to content

decision(atlas): external-content ingestion policy — the three zones and what is stored per zone #6052

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 31 (Cluster 6). The gate analysis itself is posted as a research comment on #6024 (answered-provisional).

Decision to make (research bottom line, in substance)

GitHub ToS (effective 2026-04-27) §D: copyright stays with the commenter; the D.4 license runs to GitHub only; the D.5 user license covers use through the Service / by forking only; D.6 inbound=outbound is contested for comment text; comments are not Creative Commons (CC covers GitHub's own docs: CC BY 4.0 content / MIT code). The defensible postures by zone:

Zone Posture
Our own repos (Drew's + org; his comments anywhere) Clear — ingest freely (subject to tiering)
External repos where Drew participated Private personal search defensible; no redistribution
External public repos generally (bulk) Private personal search only; serving others / redistributing is not defensible on current sources. Factual metadata (titles, URLs, timestamps, counts, hashes) is always safe

Scope

Turn the zones into the corpus policy the first-pass build (#6025) and the GitHub extraction task (#6023) execute against: per zone — full text vs metadata-only vs excluded; snippet-display rules; what changes if the corpus is ever queried by anyone but Drew.

Done looks like

A decision doc recorded here and linked from #6023/#6025, so the build gates on zones, not on vibes.

Activity

  1. added
    area/infraInfrastructure, deployment, and operations
    kind/designA design proposal (design-architect): multi-step, phased, decision-bearing
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. 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
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · escalated

    Triage — task 10418, issue #6052

    Verified fresh: issue #6052 OPEN, kind/design, area/infra — no hard-stop labels. The research bottom line is already in the issue body (GitHub ToS §D analysis, answered-provisional gate comment on parent issue #6024).

    My read (worker review first, per protocol): the three-zone posture in the body is sound and conservative — own repos: ingest freely; external repos where Drew participated: private personal search only, no redistribution; external public repos (bulk): private personal search only, factual metadata always safe. I recommend adopting it as written.

    Why this escalates instead of closing as triaged-and-routed: ratifying a copyright/ToS posture for bulk external-content ingestion is a decision only Drew can make — it sets what issues #6023 and #6025 are allowed to build. Until he ratifies, those builds gate on this issue. Task 10418 is blocked as escalated-to-user with this read attached; issue #6052 stays OPEN with user/escalated.

  5. added
    user/escalatedQueue or user escalation state
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    Ruling (Drew, main chat 2026-11-05): not ratified today. Drew's stated priority: "router and wifi networking first." The three-zone ingestion policy ratification waits behind the router/WiFi networking work.

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

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure, deployment, and operationskind/designA design proposal (design-architect): multi-step, phased, decision-bearingqueue/blockedQueue or user escalation statestatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemuser/escalatedQueue or user escalation state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions