Primary-source-driven briefing site for:
“What is the latest in code RL environments and human data?”
public/data/accounts.json— seed + secondary account linkspublic/data/papers.json— paper list + source linkspublic/data/tweets.json— thread/post records with post/account links and quoted excerptspublic/data/signals.json— structured trend synthesis from supplied notes
public/index.htmlrenders all dataset files directly (link-driven view)
pnpm install
pnpm dev# default: today + default topic
npm run run:briefing
# explicit date/topic
./scripts/run-briefing.sh 2026-03-04 "What is the latest in code RL environments and human data?"This pipeline now does, in order (scripted step prompts):
- step-01-papers-alphaxiv (AlphaXiv-first paper discovery)
- step-02-supergrok-topic
- step-03-supergrok-paper-discussion (exact query: "what are people saying about this exact paper title?")
- step-04-supergrok-signals
- step-05-supergrok-history-updates
- step-06-exa-people (deep, category=people)
- step-07-youtube-search (YouTube Data API)
- step-08-synthesis
Step-07 uses youtube-transcript-api when available to attach per-video transcripts.
python3 scripts/youtube_channel_search.py --query "RL and human data" --min-subs 5000Outputs ranked channels with stats to a JSON file (supports --out).
Definition of "run briefing" is stored in briefing-process.md.
Per-step prompts are stored in prompts/.
Per-run artifacts are stored in data/runs/YYYY-MM-DD/steps/step-XX-* with prompt + story + raw + normalized outputs.
pnpm run deploy