docs(claude-config): GitHub AUP verdict — GitHub-sourced cold email retired
- research/github-aup-lead-pipeline.md: verbatim AUP §7 + ToS §H, why the lead_pull → Brevo pipeline is the named act, what stays legal - decisions: 23:55 entry; INDEX row; context.md credit figure corrected to 8.55 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X9iCzmxK2zbb8H1Ld3f8AN
This commit is contained in:
Backtalk6858
@@ -1,8 +1,8 @@
|
||||
# Claude & Claude Code — Research & Config Home — Context
|
||||
|
||||
> **NEXT SESSION PLAN — CURRENT VALUE (rewritten 2026-09-08 23:45, Fable 5.1, supersedes the 23:05 block, now history).** Fable credits ~$16 used (expire 2026-09-19). Research track for tonight is COMPLETE; everything below is decided and recorded.
|
||||
> **NEXT SESSION PLAN — CURRENT VALUE (rewritten 2026-09-08 23:45, Fable 5.1, supersedes the 23:05 block, now history).** Fable credits **$38.55 used** per user 23:49 (my ~$16 estimate was wrong; expire 2026-09-19). Research track for tonight is COMPLETE; everything below is decided and recorded.
|
||||
> 1. **Harness track CLOSED** (`decisions/DECISIONS.md` 22:50, 23:20, 23:32 entries). Baseline wins: keep Claude Code + our layer; LifeOS/jcode/all OSS executors rejected (Anthropic legal page confines Pro OAuth to the unmodified Claude Code binary, enforced since 2026-04-04); no trial; voice = locked bespoke plan; **user: stay on Claude Code until hybrid brain + trained local brain + affordable claude -p/API, and only move if skills/processes port.** Sonnet 5 = native 1M on Pro (verified) → row 245 window-aware hook, LOW priority. Steal rows 242–244 (Doctor check, keyword→skill injector, MEMORY.md defrag). Open-source/open-core: rows 241 (parked), 246 (design the OSS-first evaluation pipeline), business_ideas 28 (parked).
|
||||
> 2. **HyperAgent ABANDONED** (23:42 entry; business row 41 closed). **NEW Horizon-A priority:** business_projects 42 (GitHub AUP §7 vs lead_pull — priority 1) then the **marketing-system overhaul row** (all digital businesses; user is not a salesman) — do both in the API Idea conversation; write the channel-research prompt into `config/prompts/` + Obsidian `Resources/Prompts/`.
|
||||
> 2. **HyperAgent ABANDONED** (23:42 entry; business row 41 closed). **NEW Horizon-A priority:** business_projects 42 DONE 23:55 (verdict NO — GitHub cold email retired, `research/github-aup-lead-pipeline.md`) → the **marketing-system overhaul row** (all digital businesses; user is not a salesman) — do both in the API Idea conversation; write the channel-research prompt into `config/prompts/` + Obsidian `Resources/Prompts/`.
|
||||
> 3. **agent-wrap skill + SubagentStop hook built 23:05** (`/opt/appdata/docker/.claude/skills/agent-wrap`, `hooks/subagent-wrap-reminder.py`, settings.json backup .bak.20260908; hook fires from next session). Three runs logged in `/opt/appdata/docker/.claude/logs/agent_runs.jsonl`; anti-pattern added (corrections go INTO the report as a banner). **/opt/appdata/docker has UNCOMMITTED hook/skill edits** (automation-detector.py, session-start.sh, subagent-wrap-reminder.py, skills/agent-wrap/) — commit at that repo's checklist.
|
||||
> 4. **Reports:** `research/ai-harness-layer-research.md` (banner: "/recall broken" claim was FALSE), `research/jcode-vs-claude-code.md`, `research/hyperagent-marketing-fit.md`; INDEX rows present. Skills track (rows 223–237) unchanged; Opus 4.8 executes GAMEPLAN Step 0 + skills 223→224→210→225 later.
|
||||
|
||||
|
||||
@@ -15,6 +15,13 @@ entry links back to the research that drove it, so the reasoning survives.
|
||||
|
||||
---
|
||||
|
||||
## 2026-09-08 — DECIDED (23:55): GitHub-sourced cold email RETIRED (business_projects 42)
|
||||
- **Decision:** the lead pipeline may NOT resume as designed. GitHub AUP §7 forbids using information from the Service "(whether scraped, collected through our API, or obtained otherwise) ... for the purposes of sending unsolicited emails to users"; ToS §H repeats it for the API and threatens account/API suspension. Our pipeline collects emails via the GraphQL API and cold-emails them = the named act. Personalization and low volume do not cure "unsolicited."
|
||||
- **Why:** verbatim policy text fetched 2026-09-08; the old approach also yielded only 4 free-tier subscribers.
|
||||
- **Research:** [../research/github-aup-lead-pipeline.md](../research/github-aup-lead-pipeline.md)
|
||||
- **Implementation:** N8N workflow 4fuzFJAclba2Syy7 stays PAUSED permanently in its current form; lead_pull GraphQL email lookup is not to be run again. Replacement = business_projects 43 (marketing overhaul: RapidAPI listing/SEO, content/docs, opt-in channels).
|
||||
- **Revisit when:** never for cold email from GitHub data; opt-in contact only.
|
||||
|
||||
## 2026-09-08 — DECIDED (23:42): HyperAgent ABANDONED; marketing system to be overhauled
|
||||
- **Decision:** REJECT HyperAgent for all three jobs (API clients, KDP, Etsy). The marketing product is Howie Liu's closed cloud hyperagent.com (~$20 base + $4–35/task, pricing UNVERIFIED: page 403); the OSS namesake (@hyperbrowser/agent, AGPL, last real commit 2026-02-13) needs a headless patch and unverified Ollama. Logged-in automation of Amazon/Etsy/LinkedIn is banned by their terms. User: "too expensive too fast, and the same legal issue will recur on most platforms." If a public-page browser agent is ever wanted: evaluate browser-use, not HyperAgent.
|
||||
- **Consequence (user):** the GitHub-scrape → cold-email pipeline is the core of API-business marketing (from the purchased course) but produced 4 free-tier subscribers and may violate GitHub AUP §7 → business_projects 42 (priority 1) + **new business_projects row: overhaul the marketing system for all digital businesses** — user is not a salesman; needs customer acquisition that does not depend on cold sales. This is Horizon A work (the revenue job).
|
||||
|
||||
@@ -13,6 +13,8 @@ re-verify versions, repos, and Linux support before acting on anything.
|
||||
| **jcode vs Claude Code** — tests the two jcode hopes (bigger context; "CLAUDE.md size limit") and ranks executors (Claude Code, jcode, OpenCode, Aider, Goose, Cline, OpenHands, Gemini CLI) under R1 Pro-OAuth / R2 hooks+skills / R3 FOSS | [jcode-vs-claude-code.md](jcode-vs-claude-code.md) | Scored 2026-09-08 (Fable 5.1) | **Claude Code stays (14/18).** Every OSS executor DQ on R1 for Claude (jcode spoofs the Claude Code client; OpenCode removed Pro/Max under legal request). "Bigger window" = model property: Sonnet 5 is 1M free on Pro, Opus 1M = paid credits. Pain (b) is the 25 KB MEMORY.md *index* cap, not CLAUDE.md. Gemini CLI = optional non-Claude secondary for long reads. |
|
||||
| **HyperAgent marketing fit** — disambiguation (Airtable Hyperagent vs Hyperbrowser OSS vs FSoft paper), constraints, per-job fit for API-clients / KDP / Etsy, ToS risk, OSS alternatives | [hyperagent-marketing-fit.md](hyperagent-marketing-fit.md) | Assessed 2026-09-08 (Fable 5.1) | **Reject all three jobs.** User likely heard of closed-source hyperagent.com (credit-metered, $4–35/task). OSS HyperAgent has `baseURL` for Ollama but hard-codes `headless:false`; KDP/Etsy/LinkedIn browser automation = ban risk. Only fragment worth anything = plain Playwright enrichment under N8N; browser-use beats it if a trial is ever wanted. |
|
||||
|
||||
| **GitHub policy vs lead pipeline** — may the GitHub-sourced cold-email outreach resume? | [github-aup-lead-pipeline.md](github-aup-lead-pipeline.md) | Verdict 2026-09-08 | **NO** — AUP §7 + ToS §H forbid unsolicited email from API-collected data (verbatim quotes in file). Sourcing + contact move to the marketing overhaul (business_projects 43). |
|
||||
|
||||
### Where the prior infrastructure research lives (memory corpus)
|
||||
Not duplicated here — cited in [infrastructure-synthesis.md](infrastructure-synthesis.md). Key files:
|
||||
`project_two_horizon_operating_model` (governing filter), `project_ai_infrastructure_vision`
|
||||
|
||||
@@ -0,0 +1,16 @@
|
||||
# GitHub policy vs the API-business lead pipeline — verdict 2026-09-08
|
||||
|
||||
**Question (business_projects 42):** may `lead_pull.py` (GitHub repo search → GraphQL `user { email }` lookup → Brevo cold email via N8N) resume as is?
|
||||
|
||||
**Verdict: NO. The pipeline is non-compliant as designed.** Both governing texts, fetched 2026-09-08 23:50:
|
||||
|
||||
- GitHub Acceptable Use Policies §7 "Information Usage Restrictions" (https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies):
|
||||
> "You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards. Your use of information from the Service must comply with the GitHub Privacy Statement."
|
||||
- GitHub Terms of Service §H "API Terms" (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#h-api-terms):
|
||||
> "You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information..." — "Abuse ... may result in the temporary or permanent suspension of your Account's access to the API."
|
||||
|
||||
**Why it applies:** the pipeline collects user emails **through the API** (GraphQL batch lookup, `lead_pull.py` step 4) and sends **unsolicited email** to those users. §7 names exactly that act and explicitly covers API-collected data. Personalization (the Claude message review) and low volume (7/day) do not change "unsolicited." The exposure is the GitHub account/token that runs the searches, and Brevo deliverability if recipients report spam. The only AUP-permitted uses of collected information are research (open-access publication) and archival.
|
||||
|
||||
**What stays legal from the current stack:** using GitHub *search* to understand who builds with dividend/finance data (market research), engaging publicly (issues/discussions where relevant and non-promotional, per AUP §10), and any contact where the user opted in (RapidAPI subscribers, mailing-list signups, replies).
|
||||
|
||||
**Decision:** cold email to GitHub-sourced addresses is retired. Lead *sourcing* and *contact* both move to the marketing-overhaul design (business_projects 43): RapidAPI marketplace listing/SEO, docs + content, opt-in channels. Result of the old approach: 4 free-tier subscribers total — the compliance problem and the yield problem point the same way.
|
||||
Reference in New Issue
Block a user