Arkive/arkive
1
0
Fork 0
Code Issues 18 Pull requests 1 Projects Releases Packages Wiki Activity Actions

[Duplicate] Define jurisdiction and target eligibility rules for user-side acquisition #35

New issue
Closed
opened 2026-07-31 01:21:13 -04:00 by JackFrostbyte · 1 comment
JackFrostbyte commented 2026-07-31 01:21:13 -04:00
Owner
Copy link

Goal

Turn Issue #34's architecture decision into an operational eligibility policy for
user-side acquisition targets.

Required policy dimensions

Evaluate each target independently across these dimensions:

  • redistribution permission;
  • lawful user acquisition path;
  • permission or defensible legal basis for local copying and processing;
  • automation permission;
  • website, API, account, subscription, or purchase terms;
  • authentication and technical access controls;
  • reviewed jurisdiction or jurisdictions;
  • evidence, reviewer, review date, expiry/recheck date, and withdrawal status.

Do not treat “personal use,” “purchased,” “freely accessible,” or “not bundleable”
as blanket permission.

Required source states

Define at least:

  1. bundleable;
  2. catalog_only;
  3. user_acquirable;
  4. prohibited_or_withdrawn.

A source may be catalog_only when Arkive can preserve metadata but cannot provide
or automate an acquisition route.

Hard boundaries

  • No DRM, paywall, CAPTCHA, authentication, or other access-control circumvention.
  • No credential collection in recipes.
  • No use of unauthorized mirrors or known infringing copies.
  • Terms-of-service and contract review remain separate from copyright review.
  • Disclaimers explain risk and responsibility but do not create permission.
  • Paid or account-bound sources default to manual user import unless an official,
    reviewed API or download mechanism expressly supports automation.

Deliverables

  • Policy document under governance/ or docs/.
  • Review checklist and evidence requirements.
  • Jurisdiction-handling rules, including how unsupported jurisdictions fail closed.
  • Re-review and emergency-withdrawal procedure.
  • A statement identifying which questions require qualified legal review before
    Arkive publishes a production recipe catalogue.

Acceptance criteria

  • Eligibility is decided per target, not by source class alone.
  • Copyright, contract/terms, automation, and access controls are separate checks.
  • Unknown or expired evidence fails closed.
  • Manual import and automated acquisition have distinct eligibility rules.
  • Withdrawal stops future acquisition without claiming Arkive can delete users'
    existing local copies.
  • The policy does not claim that a disclaimer makes an otherwise unauthorized
    action lawful.

Out of scope

  • Implementing fetchers.
  • Selecting the first production target list.
  • Providing legal advice to end users.
## Goal Turn Issue #34's architecture decision into an operational eligibility policy for user-side acquisition targets. ## Required policy dimensions Evaluate each target independently across these dimensions: - redistribution permission; - lawful user acquisition path; - permission or defensible legal basis for local copying and processing; - automation permission; - website, API, account, subscription, or purchase terms; - authentication and technical access controls; - reviewed jurisdiction or jurisdictions; - evidence, reviewer, review date, expiry/recheck date, and withdrawal status. Do not treat “personal use,” “purchased,” “freely accessible,” or “not bundleable” as blanket permission. ## Required source states Define at least: 1. `bundleable`; 2. `catalog_only`; 3. `user_acquirable`; 4. `prohibited_or_withdrawn`. A source may be `catalog_only` when Arkive can preserve metadata but cannot provide or automate an acquisition route. ## Hard boundaries - No DRM, paywall, CAPTCHA, authentication, or other access-control circumvention. - No credential collection in recipes. - No use of unauthorized mirrors or known infringing copies. - Terms-of-service and contract review remain separate from copyright review. - Disclaimers explain risk and responsibility but do not create permission. - Paid or account-bound sources default to manual user import unless an official, reviewed API or download mechanism expressly supports automation. ## Deliverables - Policy document under `governance/` or `docs/`. - Review checklist and evidence requirements. - Jurisdiction-handling rules, including how unsupported jurisdictions fail closed. - Re-review and emergency-withdrawal procedure. - A statement identifying which questions require qualified legal review before Arkive publishes a production recipe catalogue. ## Acceptance criteria - [ ] Eligibility is decided per target, not by source class alone. - [ ] Copyright, contract/terms, automation, and access controls are separate checks. - [ ] Unknown or expired evidence fails closed. - [ ] Manual import and automated acquisition have distinct eligibility rules. - [ ] Withdrawal stops future acquisition without claiming Arkive can delete users' existing local copies. - [ ] The policy does not claim that a disclaimer makes an otherwise unauthorized action lawful. ## Out of scope - Implementing fetchers. - Selecting the first production target list. - Providing legal advice to end users.
JackFrostbyte commented 2026-07-31 01:31:38 -04:00
Author
Owner
Copy link

Closing this issue as a duplicate of #43.

Issues #35 and #43 were created with the same roadmap
content during recovery from an interrupted automation run. The later set
#43–#50 is canonical because Issue #34's finalized roadmap body, comment, and
dependency graph reference that set.

No implementation work was completed in this duplicate issue.

<!-- arkive-roadmap-duplicate-cleanup-v1 --> Closing this issue as a duplicate of #43. Issues #35 and #43 were created with the same roadmap content during recovery from an interrupted automation run. The later set #43–#50 is canonical because Issue #34's finalized roadmap body, comment, and dependency graph reference that set. No implementation work was completed in this duplicate issue.
JackFrostbyte changed title from Define jurisdiction and target eligibility rules for user-side acquisition to [Duplicate] Define jurisdiction and target eligibility rules for user-side acquisition 2026-07-31 01:31:38 -04:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/issue-17-reproducibility-tests
develop
No results found.
Labels
Clear labels
  
area/deployment
Portable packaging and constrained-environment validation

  
area/governance
Project rules, policies, contributor workflow

  
area/metadata
Schemas, manifests, validation contracts

  
area/pipeline
Import, extraction, normalization, chunking

  
area/search
Indexing, retrieval, citation resolution

  
type/data
Source selection, metadata, fixtures, and corpus work

  
type/design
Architecture, policy, contracts, and ADR work

  
type/implementation
Production code or tooling

  
type/testing
Reproducibility, integration, evaluation, and benchmark work

No labels
area/deployment
area/governance
area/metadata
area/pipeline
area/search
type/data
type/design
type/implementation
type/testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Arkive/arkive#35
No description provided.