Auto: agents/theseus/network.json | 1 file changed, 21 insertions(+)

agents/rio/network.json

@@ -0,0 +1,21 @@
+{
+  "agent": "rio",
+  "domain": "internet-finance",
+  "accounts": [
+    {"username": "metaproph3t", "tier": "core", "why": "MetaDAO founder, primary futarchy source."},
+    {"username": "MetaDAOProject", "tier": "core", "why": "Official MetaDAO account."},
+    {"username": "futarddotio", "tier": "core", "why": "Futardio launchpad, ownership coin launches."},
+    {"username": "TheiaResearch", "tier": "core", "why": "Felipe Montealegre, Theia Research, investment thesis source."},
+    {"username": "ownershipfm", "tier": "core", "why": "Ownership podcast, community signal."},
+    {"username": "PineAnalytics", "tier": "core", "why": "MetaDAO ecosystem analytics."},
+    {"username": "ranger_finance", "tier": "core", "why": "Liquidation and leverage infrastructure."},
+    {"username": "FlashTrade", "tier": "extended", "why": "Perps on Solana."},
+    {"username": "turbine_cash", "tier": "extended", "why": "DeFi infrastructure."},
+    {"username": "Blockworks", "tier": "extended", "why": "Broader crypto media, regulatory signal."},
+    {"username": "SolanaFloor", "tier": "extended", "why": "Solana ecosystem data."},
+    {"username": "01Resolved", "tier": "extended", "why": "Solana DeFi."},
+    {"username": "_spiz_", "tier": "extended", "why": "Solana DeFi commentary."},
+    {"username": "kru_tweets", "tier": "extended", "why": "Crypto market structure."},
+    {"username": "oxranga", "tier": "extended", "why": "Solomon/MetaDAO ecosystem builder."}
+  ]
+}

agents/theseus/network.json

@@ -0,0 +1,21 @@
+{
+  "agent": "theseus",
+  "domain": "ai-alignment",
+  "accounts": [
+    {"username": "karpathy", "tier": "core", "why": "Autoresearch, agent architecture, delegation patterns."},
+    {"username": "DarioAmodei", "tier": "core", "why": "Anthropic CEO, races-to-the-top, capability-reliability."},
+    {"username": "ESYudkowsky", "tier": "core", "why": "Alignment pessimist, essential counterpoint."},
+    {"username": "simonw", "tier": "core", "why": "Zero-hype practitioner, agentic engineering patterns."},
+    {"username": "swyx", "tier": "core", "why": "AI engineering meta-commentary, subagent thesis."},
+    {"username": "janleike", "tier": "core", "why": "Anthropic alignment lead, scalable oversight."},
+    {"username": "davidad", "tier": "core", "why": "ARIA formal verification, safeguarded AI."},
+    {"username": "hwchase17", "tier": "extended", "why": "LangChain/LangGraph, agent orchestration."},
+    {"username": "AnthropicAI", "tier": "extended", "why": "Lab account, infrastructure updates."},
+    {"username": "NPCollapse", "tier": "extended", "why": "Connor Leahy, AI governance."},
+    {"username": "alexalbert__", "tier": "extended", "why": "Claude Code product lead."},
+    {"username": "GoogleDeepMind", "tier": "extended", "why": "AlphaProof, formal methods."},
+    {"username": "GaryMarcus", "tier": "watch", "why": "Capability skeptic, keeps us honest."},
+    {"username": "noahopinion", "tier": "watch", "why": "AI economics, already 5 claims sourced."},
+    {"username": "ylecun", "tier": "watch", "why": "Meta AI, contrarian on doom."}
+  ]
+}

ops/research-session.sh

@@ -181,16 +181,24 @@ Read these files to understand your current state:
 Read ${TWEET_FILE} — these are recent tweets from accounts in your domain.
 Scan for anything substantive: new claims, evidence, debates, data, counterarguments.
 
-### Step 3: Pick ONE Research Direction (5 min)
+### Step 3: Check Previous Follow-ups (2 min)
-Based on your beliefs, your domain's gaps, and what you found in the tweets, pick ONE research direction that would most advance your domain understanding. Consider:
+Read agents/${AGENT}/musings/ — look for any previous research-*.md files. If they exist, check the 'Follow-up Directions' section at the bottom. These are threads your past self flagged but didn't have time to cover. Give them priority when picking your direction.
-- Gaps in your beliefs that need evidence
+
-- Claims in the KB that new evidence might challenge
+### Step 4: Pick ONE Research Question (5 min)
-- Cross-domain connections flagged by other agents
+Pick ONE research question — not one topic, but one question that naturally spans multiple accounts and sources. 'How is capital flowing through Solana launchpads?' is one question even though it touches MetaDAO, SOAR, Futardio.
-- New developments that change the landscape
+
+**Direction selection priority** (active inference — pursue surprise, not confirmation):
+1. Follow-up ACTIVE THREADS from previous sessions (your past self flagged these)
+2. Claims rated 'experimental' or areas where the KB flags live tensions — highest uncertainty = highest learning value
+3. Evidence that CHALLENGES your beliefs, not confirms them
+4. Cross-domain connections flagged by other agents
+5. New developments that change the landscape
+
+Also read agents/${AGENT}/research-journal.md if it exists — this is your cross-session pattern tracker.
 
 Write a brief note explaining your choice to: agents/${AGENT}/musings/research-${DATE}.md
 
-### Step 4: Archive Sources (60 min)
+### Step 5: Archive Sources (60 min)
 For each relevant tweet/thread, create an archive file:
 
 Path: inbox/archive/YYYY-MM-DD-{author-handle}-{brief-slug}.md
@@ -215,11 +223,18 @@ tags: [topic1, topic2]
 
 ## Agent Notes
 **Why this matters:** [1-2 sentences]
+**What surprised me:** [Anything unexpected — the extractor needs this to avoid confirming your priors]
+**What I expected but didn't find:** [Gaps or missing evidence you noticed]
 **KB connections:** [Which existing claims relate?]
 **Extraction hints:** [What claims might an extractor pull?]
 **Context:** [Who is the author, what debate is this part of?]
 
-### Rules:
+## Curator Notes (structured handoff for extractor)
+PRIMARY CONNECTION: [exact claim title this source most relates to]
+WHY ARCHIVED: [what pattern or tension this evidences]
+EXTRACTION HINT: [what the extractor should focus on — scopes attention]
+
+### Step 5 Rules:
 - Archive EVERYTHING substantive, not just what supports your views
 - Set all sources to status: unprocessed (a DIFFERENT instance will extract)
 - Flag cross-domain sources with flagged_for_{agent}: [\"reason\"]
@@ -227,7 +242,35 @@ tags: [topic1, topic2]
 - Check inbox/archive/ for duplicates before creating new archives
 - Aim for 5-15 source archives per session
 
-### Step 5: Commit and Push (5 min)
+### Step 6: Flag Follow-up Directions (5 min)
+At the bottom of your research musing (agents/${AGENT}/musings/research-${DATE}.md), add a section:
+
+## Follow-up Directions
+
+Three categories — be specific, not vague:
+
+### Active Threads (continue next session)
+- [Thread]: [What to do next, what you'd look for]
+
+### Dead Ends (don't re-run these)
+- [What you searched for]: [Why it was empty — saves future you from wasting time]
+
+### Branching Points (one finding opened multiple directions)
+- [Finding]: [Direction A vs Direction B — which to pursue first and why]
+
+### Step 7: Update Research Journal (3 min)
+Append to agents/${AGENT}/research-journal.md (create if it doesn't exist). This is your cross-session memory — NOT the same as the musing.
+
+Format:
+## Session ${DATE}
+**Question:** [your research question]
+**Key finding:** [most important thing you learned]
+**Pattern update:** [did this session confirm, challenge, or extend a pattern you've been tracking?]
+**Confidence shift:** [did any of your beliefs get stronger or weaker?]
+
+The journal accumulates session over session. After 5+ sessions, review it for cross-session patterns — when independent sources keep converging on the same observation, that's a claim candidate.
+
+### Step 8: Commit and Push (5 min)
 Stage your archives and musing, commit with:
   ${AGENT}: research session ${DATE} — {brief description of direction}