πŸ“‹ Todo Report

Generated: 2026-02-12 17:42:48

πŸ“š Commands Cheatsheet β–Ό

Regenerate report:

python tools/todos/generate_report.py

Enrich todos with LLM metadata (priority/difficulty/utility):

python tools/todos/enrich.py          # Run enrichment
python tools/todos/enrich.py --dry-run # Preview only

Impact analysis (multi-model consensus on highest-impact items):

python tools/todos/analyze.py              # maxthink preset (Opus, GPT-Pro, Grok, Gemini)
python tools/todos/analyze.py -c fast      # Fast/cheap models
python tools/todos/analyze.py --top 5      # Top 5 instead of 3

After enrichment: Report will show colored priority badges (P1-P5), difficulty levels, and utility descriptions.

Open file in editor: Click file location to select, copy (Cmd+C), then Cmd+P in VS Code and paste.

515
Total Items
473
Open
42
Completed
3
Projects

πŸ’° investor

Investor Replication (2 open)

☐ Replicate top investor frameworks
replication/ β€” Acquire content, extract structured thesis elements, build company timelines, operationalize into scoring. Three targets: Reeves/Infuse (Substack + letters), Druckenmiller (interviews + 13F), Tepper (interviews + 13F). Start with Reeves β€” most written content, existing principles in research/infuse_principles.md.
☐ Bond covenant analysis
covenants/ β€” Extract structured covenants from EDGAR indentures, compute headroom, track amendments. EBITDA definition resolution is the hard part.

Phase 0: Brain Demo (Now) (14 open)

β–Ά

Phase 1: Foundation (3 open)

☐ Price ingestion pipeline
  • Historical data backfill (daily OHLCV)
  • On-demand fetch for analysis
  • Store in SQLite or Redis timeseries
☐ Source Hub integration
  • Connect to existing source MCP server
  • Define source types: filings, transcripts, news, social
  • Basic ingestion β†’ extraction β†’ storage flow
☐ Monitoring scaffold
  • Define watchlist table (names, theses, broad themes)
  • Cron or daemon skeleton for periodic checks
  • Simple "new content detected" alerts

Phase 2: Assimilation Engine (3 open)

☐ Relevance filtering
  • Given new content, classify by watchlist item
  • LLM-based relevance scoring
  • Route to appropriate name/thesis
☐ Extraction pipeline
  • Facts, claims, variable updates from content
  • Structured JSON output (per vision doc)
  • Append to evidence ledger
☐ Executive summary generation
  • Per-name and per-thesis summaries
  • "What's changed since last update?"
  • Highlight thesis-altering signals

Phase 3: Sentiment (4 open)

☐ Research existing tools
  • What APIs exist? (Twitter, Reddit, StockTwits, YouTube)
  • What sentiment libraries work well?
  • Academic papers on sentiment-price relationships
☐ Build sentiment tracker
  • Ingest social mentions per symbol
  • Compute sentiment score (simple first: positive/negative/neutral)
  • Track volume and sentiment over time
☐ Divergence detection
  • Compare sentiment trend vs price trend
  • Flag: "price up, sentiment flat/down" and vice versa
  • Backtest: do divergences predict continuation?
☐ Dashboard widget
  • Social din chart per symbol
  • Highlight divergence periods
  • Quick sentiment snapshot

Phase 4: Research Mode (3 open)

☐ Historical analysis toolkit
  • Given an event, find earliest mentions
  • Timeline reconstruction
  • "Who called it?" search
☐ Present analysis framework
  • Structured prompts for thinking through news
  • Second-order effects template
  • Confirm/refute checklist
☐ Case study format
  • Narrative + structured data output
  • Lessons learned extraction
  • Feed back into monitoring rules

Phase 5: Causal Learning (3 open)

☐ Forecast grading system
  • Track predictions with timestamps
  • Auto-grade when horizon passes
  • Aggregate accuracy metrics
☐ Causal graph experiments
  • Prototype: how to represent causal chains?
  • Options: neo4j, embeddings, rules engine
  • Start with manual curation, then automate
☐ Feedback loops
  • Graded forecasts β†’ update priors
  • Successful patterns β†’ monitoring rules
  • Failed predictions β†’ post-mortems

Ideas / Backlog (6 open)

β–Ά

🌊 rivus

People β€” This Week (2 open)

☐ Connect with SMAI
Figure out dates, schedule for this coming week (week of Feb 10)
☐ Connect with SMAI
Figure out dates, schedule for this coming week (week of Feb 10)

Priority (36 open)

β–Ά

Review with User (4 open)

β–Ά

Investor Replication & Covenant Analysis (4 open)

☐ Investor replication system
~/all-code/investor/replication/ β€” Extract analytical frameworks from top investors (Reeves/Infuse, Druckenmiller, Tepper) by acquiring their content (Substack, interviews, letters, 13F), extracting structured thesis elements per document, building company timelines, and operationalizing into scoring/screening. Design task: tasks/design/investment_philosophy_extraction.md
☐ Bond covenant analysis
~/all-code/investor/covenants/ β€” Extract structured covenants from EDGAR indentures/credit agreements, compute headroom vs current financials, track amendments over time. Key challenge: resolving nested EBITDA definitions and cross-references.
☐ Investor replication system
~/all-code/investor/replication/ β€” Extract analytical frameworks from top investors (Reeves/Infuse, Druckenmiller, Tepper) by acquiring their content (Substack, interviews, letters, 13F), extracting structured thesis elements per document, building company timelines, and operationalizing into scoring/screening. Design task: tasks/design/investment_philosophy_extraction.md
☐ Bond covenant analysis
~/all-code/investor/covenants/ β€” Extract structured covenants from EDGAR indentures/credit agreements, compute headroom vs current financials, track amendments over time. Key challenge: resolving nested EBITDA definitions and cross-references.

Learning (8 open)

β–Ά

Newsflow: CEO Interviews & Podcasts (10 open)

β–Ά

LLM Tools (2 open)

☐ fetch tool for lib/llm tool registry
lib/llm/tools.py β€” LLM can fetch URLs from search results. Needs: brain's fetch_escalate with smart proxy escalation, BrightData unlocker/JS rendering for paywalled/dynamic content. High-volume JS fetching may need existing browser service or BrightData Browser CDP endpoint. Design considerations: mode param (auto/js/unlocker), rate limiting, content truncation for token efficiency.
☐ fetch tool for lib/llm tool registry
lib/llm/tools.py β€” LLM can fetch URLs from search results. Needs: brain's fetch_escalate with smart proxy escalation, BrightData unlocker/JS rendering for paywalled/dynamic content. High-volume JS fetching may need existing browser service or BrightData Browser CDP endpoint. Design considerations: mode param (auto/js/unlocker), rate limiting, content truncation for token efficiency.

Transcription (6 open)

β–Ά

KB & Self-Learning (6 open)

β–Ά

Visual TODO (2 open)

☐ Explore Gradio themes - https://www.gradio.app/guides/theming-guide
  • Built-in: gr.themes.Glass(), gr.themes.Ocean(), gr.themes.Citrus()
  • Pick one consistent theme for all rivus Gradio apps
☐ Explore Gradio themes - https://www.gradio.app/guides/theming-guide
  • Built-in: gr.themes.Glass(), gr.themes.Ocean(), gr.themes.Citrus()
  • Pick one consistent theme for all rivus Gradio apps

System (2 open)

☐ Background hook - Hook to check if hooks need updating (meta-hook for hook maintenance)
☐ Background hook - Hook to check if hooks need updating (meta-hook for hook maintenance)

Writing / Substack (4 open)

☐ Parallel & Speculative Development - Write up patterns for developing with cheap parallel workers
  • Speculative execution, fork-and-verify, test assumptions in background, design for parallel dev
  • Real examples from rivus: vario pipeline, background agents, fork-to-check-history
  • Key insight: copies of workers are cheap, waiting is expensive
  • This is a genuine contribution β€” most dev practices assume serial work
☐ Decide where writeups live - writing/ or design/writing/ in rivus?
  • Substack drafts, learnings, patterns worth sharing
  • Separate from design/drafts (which are LLM review outputs)
  • Should be git-tracked, easy to preview as markdown
☐ Parallel & Speculative Development - Write up patterns for developing with cheap parallel workers
  • Speculative execution, fork-and-verify, test assumptions in background, design for parallel dev
  • Real examples from rivus: vario pipeline, background agents, fork-to-check-history
  • Key insight: copies of workers are cheap, waiting is expensive
  • This is a genuine contribution β€” most dev practices assume serial work
☐ Decide where writeups live - writing/ or design/writing/ in rivus?
  • Substack drafts, learnings, patterns worth sharing
  • Separate from design/drafts (which are LLM review outputs)
  • Should be git-tracked, easy to preview as markdown

Trading / Investor (2 open)

☐ Portfolio news monitoring - Monitor news about portfolio companies, assess market reaction and implications
  • Track news events (earnings, product launches, regulatory, macro) for held positions
  • Assess: how is the market reacting? how should we be reacting?
  • Compare market reaction vs our fundamental view β€” find mismatches (overreaction, underreaction)
  • Feed into position sizing / exit decisions in moneygun
☐ Portfolio news monitoring - Monitor news about portfolio companies, assess market reaction and implications
  • Track news events (earnings, product launches, regulatory, macro) for held positions
  • Assess: how is the market reacting? how should we be reacting?
  • Compare market reaction vs our fundamental view β€” find mismatches (overreaction, underreaction)
  • Feed into position sizing / exit decisions in moneygun

Self-Learning & Iteration (vario/geneval direction) (10 open)

β–Ά

Refactoring (2 open)

☐ Move smart-fetch logic to browser project - brain/fetcher.py + refusal.py (~400 lines) should move to browser
  • browser exposes /smart-fetch endpoint with JS retry, refusal detection
  • brain just calls browser, handles caching + LLM analysis
☐ Move smart-fetch logic to browser project - brain/fetcher.py + refusal.py (~400 lines) should move to browser
  • browser exposes /smart-fetch endpoint with JS retry, refusal detection
  • brain just calls browser, handles caching + LLM analysis

Long-term (4 open)

☐ πŸ”΄ Rapid takeoff company sketch πŸ”΄
What would a rapid-takeoff AI-native company look like? Sketch out:
  • Mission & focus: What problem, what wedge, what makes it defensible
  • Funding: How much, what stages, what milestones unlock each round
  • Team & roles: Who to hire first (and last), what each role's mission/focus looks like individually β€” not just titles but what each person should be obsessing over in months 1-6 vs 6-18
  • Velocity model: What enables rapid iteration β€” small team, AI leverage, tight feedback loops, what's automated vs human-judgment
  • Anti-patterns: What slows down takeoff (premature scaling, wrong hires, too much process, consensus culture)
  • Calibration: Study real rapid-takeoff examples (Midjourney: 11 people β†’ $200M ARR, Cursor, Perplexity early days, Instagram pre-acquisition) β€” what did the org chart actually look like?
☐ πŸ”΄ Rapid takeoff company sketch πŸ”΄
What would a rapid-takeoff AI-native company look like? Sketch out:
  • Mission & focus: What problem, what wedge, what makes it defensible
  • Funding: How much, what stages, what milestones unlock each round
  • Team & roles: Who to hire first (and last), what each role's mission/focus looks like individually β€” not just titles but what each person should be obsessing over in months 1-6 vs 6-18
  • Velocity model: What enables rapid iteration β€” small team, AI leverage, tight feedback loops, what's automated vs human-judgment
  • Anti-patterns: What slows down takeoff (premature scaling, wrong hires, too much process, consensus culture)
  • Calibration: Study real rapid-takeoff examples (Midjourney: 11 people β†’ $200M ARR, Cursor, Perplexity early days, Instagram pre-acquisition) β€” what did the org chart actually look like?
Reproduce PhD research/results
☐ Repro my PhD
Reproduce PhD research/results

Phase 1: Search fallback (4 open)

☐ If input isn't URL/event/question β†’ browser search β†’ fetch top result
☐ If input isn't URL/event/question β†’ browser search β†’ fetch top result
☐ Add brain search "query" CLI command
☐ Add brain search "query" CLI command

Phase 2: Multi-result analysis (vario integration) (8 open)

β–Ά

Unified NL input (CLI + UI) (10 open)

β–Ά

Active Development (6 open)

β–Ά

Research Queries (2 open)

☐ Develop research-oriented precursors (research_* in query_precursors.yaml)
  • These may be better as reusable analysis patterns than one-off prompts
  • Consider: composable prompt fragments vs monolithic prompts
☐ Develop research-oriented precursors (research_* in query_precursors.yaml)
  • These may be better as reusable analysis patterns than one-off prompts
  • Consider: composable prompt fragments vs monolithic prompts

Infrastructure (4 open)

☐ Add CLI command to list precursors by status
☐ Add CLI command to list precursors by status
☐ Add test harness: run prompt against sample docs, compare outputs
☐ Add test harness: run prompt against sample docs, compare outputs

Automation / Integration (8 open)

β–Ά

Top Level (4 open)

☐ Streaming coalesce / incremental synthesis - Coalesce information as it arrives (fetches, LLM streams, chunks):
  • Real-time doc updates as data comes in (e.g., person search β†’ update profile as each source fetched)
  • Line numbers + content hashes for addressing ranges, detecting overlap
  • N LLMs propose content β†’ shuffle lines into place β†’ edit/unify in real-time
  • Use case: parallel research streams merge into single evolving document
  • Think: collaborative doc where each source/model contributes lines, system detects redundancy and merges
☐ Streaming coalesce / incremental synthesis - Coalesce information as it arrives (fetches, LLM streams, chunks):
  • Real-time doc updates as data comes in (e.g., person search β†’ update profile as each source fetched)
  • Line numbers + content hashes for addressing ranges, detecting overlap
  • N LLMs propose content β†’ shuffle lines into place β†’ edit/unify in real-time
  • Use case: parallel research streams merge into single evolving document
  • Think: collaborative doc where each source/model contributes lines, system detects redundancy and merges
☐ Live audio analysis for Tesla call - Real-time audio stream analysis for today's Tesla earnings call
☐ Live audio analysis for Tesla call - Real-time audio stream analysis for today's Tesla earnings call

Next (2 open)

☐ Try judging pipeline - Test the new --each flag end-to-end:
☐ Try judging pipeline - Test the new --each flag end-to-end:

Features (12 open)

β–Ά

Polish (2 open)

☐ Syntax highlighting theme for YAML (CodeMirror CSS overrides)
☐ Syntax highlighting theme for YAML (CodeMirror CSS overrides)

Explore (2 open)

☐ Collapsible messages in chat - Use Gradio's reasoning_tags or similar for collapsible system prompt display. See https://www.gradio.app/docs/gradio/chatbot#param-chatbot-reasoning-tags and https://www.gradio.app/docs/gradio/chatbot#examples
☐ Collapsible messages in chat - Use Gradio's reasoning_tags or similar for collapsible system prompt display. See https://www.gradio.app/docs/gradio/chatbot#param-chatbot-reasoning-tags and https://www.gradio.app/docs/gradio/chatbot#examples

Completed (0 open)

β–Ά

Ready to Test (8 open)

β–Ά

Auto-Create Ingestion Wisdom (6 open)

β–Ά

Verification Execution Engine (24 open)

β–Ά

Questions to Resolve (6 open)

β–Ά

Implementation (10 open)

β–Ά

Free-Signup Paywall Sites (2 open)

Biotech/pharma news. Free signup gets limited articles. Test URL: https://endpoints.news/roivants-dealmaker-lands-81m-cash-bonus-following-drug-sale-to-roche/
  • Signup flow: email + password β†’ limited free articles
  • Strategy: create account once, persist session cookies, reuse across fetches
  • Ties into Session & Login Management below
☐ endpoints.news
Biotech/pharma news. Free signup gets limited articles. Test URL: https://endpoints.news/roivants-dealmaker-lands-81m-cash-bonus-following-drug-sale-to-roche/
  • Signup flow: email + password β†’ limited free articles
  • Strategy: create account once, persist session cookies, reuse across fetches
  • Ties into Session & Login Management below

Tasks (10 open)

β–Ά

Automation Mode Enhancements (6 open)

β–Ά

Agent Quality (6 open)

β–Ά

Testing (6 open)

β–Ά

Implemented (0 open)

β–Ά

Visual Verification (Priority) (34 open)

β–Ά

Reference Appearance Screenshots (8 open)

β–Ά

Top Priority (2 open)

Scrape and collect all Section 351 ETFs. Research what's involved: tax-free exchange mechanism, which ETFs use it, fund structures, eligible securities, investor requirements. Build a comprehensive dataset of 351 ETFs with their holdings, launch dates, and conversion details.
☐ Section 351 ETFs
Scrape and collect all Section 351 ETFs. Research what's involved: tax-free exchange mechanism, which ETFs use it, fund structures, eligible securities, investor requirements. Build a comprehensive dataset of 351 ETFs with their holdings, launch dates, and conversion details.

VIC Cached Content Improvements (2 open)

☐ VIC styling in cached viewer
Static server serves cached VIC HTML but CSS/JS assets don't load (require VIC authentication). Options: (1) Extract description content only, serve in clean wrapper with basic styling, (2) Use VIC cookies to fetch/cache CSS/JS assets, (3) Inline critical styles directly in cached HTML. Current state: content is readable but unstyled. Related: static/server.py asset caching, jobs/data/vic_ideas/.share base_path config.
☐ VIC styling in cached viewer
Static server serves cached VIC HTML but CSS/JS assets don't load (require VIC authentication). Options: (1) Extract description content only, serve in clean wrapper with basic styling, (2) Use VIC cookies to fetch/cache CSS/JS assets, (3) Inline critical styles directly in cached HTML. Current state: content is readable but unstyled. Related: static/server.py asset caching, jobs/data/vic_ideas/.share base_path config.

Dashboard Improvements (2 open)

☐ Paginate items in large jobs
Jobs with 500+ items are slow to load and unwieldy. Add pagination (page size ~50) to Pending/Done/Failed tabs in the detail view, with next/prev controls and item count display.
☐ Paginate items in large jobs
Jobs with 500+ items are slow to load and unwieldy. Add pagination (page size ~50) to Pending/Done/Failed tabs in the detail view, with next/prev controls and item count display.

Runner Improvements (10 open)

β–Ά

Job Event Log (Changelog) (8 open)

β–Ά

Validator Stage Role (10 open)

β–Ά

Success-Rate Circuit Breaker (2 open)

☐ Low success rate CB
Track success/fail ratio over a sliding window (last N items, default 20). Auto-pause when success rate drops below threshold (e.g., success_rate_min: 0.50). Catches intermittent failures that never cluster enough to trip the consecutive CB. Config per-stage in YAML:
☐ Low success rate CB
Track success/fail ratio over a sliding window (last N items, default 20). Auto-pause when success rate drops below threshold (e.g., success_rate_min: 0.50). Catches intermittent failures that never cluster enough to trip the consecutive CB. Config per-stage in YAML:

Validation Circuit Breaker (6 open)

β–Ά

Repair Workflow (6 open)

β–Ά

New Job Ideas (6 open)

β–Ά

Investment Research (2 open)

☐ Cheap power / US solar production
Research investment opportunities in cheap electricity and US-based solar manufacturing. Source: https://youtu.be/BYXbuik3dgA?si=6KqftryUmoChEqQa
☐ Cheap power / US solar production
Research investment opportunities in cheap electricity and US-based solar manufacturing. Source: https://youtu.be/BYXbuik3dgA?si=6KqftryUmoChEqQa

New Sources (2 open)

☐ **Local & Municipal Data
LLM-based Scrape**:
  • Goal: Extract structured data from local/municipal government sites (permits, zoning, property records, council minutes, budgets, public notices).
  • Why: Municipal data is high-value but poorly structured β€” PDFs, inconsistent HTML, no APIs. LLM extraction can normalize it into queryable knowledge.
  • Approach: Browser automation (rivus/browser) + LLM extraction (brain/extract). Same pipeline as VIC/supplychain but pointed at gov sites.
  • Examples: Building permits, zoning changes, city council agendas, public budget documents, property assessment records.
☐ **Local & Municipal Data
LLM-based Scrape**:
  • Goal: Extract structured data from local/municipal government sites (permits, zoning, property records, council minutes, budgets, public notices).
  • Why: Municipal data is high-value but poorly structured β€” PDFs, inconsistent HTML, no APIs. LLM extraction can normalize it into queryable knowledge.
  • Approach: Browser automation (rivus/browser) + LLM extraction (brain/extract). Same pipeline as VIC/supplychain but pointed at gov sites.
  • Examples: Building permits, zoning changes, city council agendas, public budget documents, property assessment records.

Cost Control (2 open)

☐ Multiple Max accounts in envs
rotate/split API usage across accounts
☐ Multiple Max accounts in envs
rotate/split API usage across accounts

Measure & Validate (2 open)

☐ Measure initial-only variant value: Does "T. Lastname" find any unique URLs that "Timothy Lastname" and "Tim Lastname" don't? Run 5-10 names, compare candidate URLs per variant. If initial-only never adds unique results, drop it to save Serper credits.
☐ Measure initial-only variant value: Does "T. Lastname" find any unique URLs that "Timothy Lastname" and "Tim Lastname" don't? Run 5-10 names, compare candidate URLs per variant. If initial-only never adds unique results, drop it to save Serper credits.

Future Phases (16 open)

β–Ά

Data Sources (4 open)

thorough list of semiconductor/supply chain publications
  • Rank by quality
  • Note cost vs free access
  • Categories: news, research, analyst reports, trade journals
  • Examples to evaluate: SemiEngineering, EETimes, DigiTimes, Semiconductor Digest, SEMI reports, TrendForce, IC Insights, Yole, etc.
☐ Industry publications list
thorough list of semiconductor/supply chain publications
  • Rank by quality
  • Note cost vs free access
  • Categories: news, research, analyst reports, trade journals
  • Examples to evaluate: SemiEngineering, EETimes, DigiTimes, Semiconductor Digest, SEMI reports, TrendForce, IC Insights, Yole, etc.
what's available only via subscription/enterprise
  • Capital IQ (S&P) β€” supply chain relationships, financials, private company data
  • Refinitiv/LSEG β€” supply chain data, ownership, estimates
  • Bloomberg Terminal β€” supply chain module (SPLC)
  • FactSet β€” supply chain relationships
  • Pitchbook β€” private company valuations
  • Gartner/IDC β€” market share reports
  • SEMI β€” industry reports, fab capacity data
  • Evaluate: coverage, cost tiers, API access, data freshness
☐ Paid data sources research
what's available only via subscription/enterprise
  • Capital IQ (S&P) β€” supply chain relationships, financials, private company data
  • Refinitiv/LSEG β€” supply chain data, ownership, estimates
  • Bloomberg Terminal β€” supply chain module (SPLC)
  • FactSet β€” supply chain relationships
  • Pitchbook β€” private company valuations
  • Gartner/IDC β€” market share reports
  • SEMI β€” industry reports, fab capacity data
  • Evaluate: coverage, cost tiers, API access, data freshness

Data Quality (6 open)

β–Ά

Viewer Improvements (2 open)

☐ Add market cap data for seed companies (via finnhub or discover.py)
☐ Add market cap data for seed companies (via finnhub or discover.py)

Transcript Analysis (6 open)

β–Ά

Dash Explorer (6 open)

β–Ά

Data Pipeline (8 open)

β–Ά

High Priority (8 open)

β–Ά

Medium Priority (6 open)

β–Ά

Low Priority (6 open)

β–Ά

Translation (4 open)

☐ Real-time WebSocket translation
Use OpenAI Realtime API for streaming transcription/translation during video playback. Would show live subtitles as video plays.
☐ Real-time WebSocket translation
Use OpenAI Realtime API for streaming transcription/translation during video playback. Would show live subtitles as video plays.
OCR on-screen text (signs, subtitles burned into video) and translate. Could use Tesseract or cloud vision APIs.
☐ Screen text translation
OCR on-screen text (signs, subtitles burned into video) and translate. Could use Tesseract or cloud vision APIs.

TODO: Fetchability Matrix Validation (LLM URL Tool Input) (3 open)

☐ Maintain fetchability contract for mode=auto|js|unlocker and escalation evidence
  • Gym spec: learning/gyms/fetchability/docs/FETCHABILITY_MATRIX_SPEC.md
  • Machine-readable matrix: learning/gyms/fetchability/tests/fixtures/fetchability_matrix.yaml
  • Parameterized tests: learning/gyms/fetchability/tests/test_fetchability_matrix.py
☐ Run live matrix probes with real paid URLs (Substack + Patreon) and record required means
  • Required env: BROWSER_TEST_SUBSTACK_PAID_URL, BROWSER_TEST_PATREON_PAID_URL
  • Optional auth flags: BROWSER_TEST_SUBSTACK_PAID_AUTH=1, BROWSER_TEST_PATREON_PAID_AUTH=1
☐ Capture baseline latency/cost for each first-success mode before wiring into lib/llm/tools.py

πŸ“Š timdata

To Do (4 open)

☐ Become AI advisor to 10110: Explore advisory/consulting relationship with 10110 on AI strategy.
☐ Create a Family Data MCP Server:
  • Goal: Build a Model Context Protocol (MCP) server to act as a relay for family information.
  • Features:
  • Authentication: Implement secure authentication (likely OAuth 2.0 for Google services).
  • Relay: Provide requested information to the LLM.
  • Data Filling: If information is missing, make a note for the user to provide it later to fill in the blanks and store it in this repository.
  • Integrations: Hook up to Google Calendar (investigate existing MCP servers or build custom using Google Workspace APIs).
☐ Food Automation:
  • Goal: Check whether food ordering can be automated through an API with an LLM assistant.
  • APIs to Check: Uber Eats API, DoorDash Drive API.
☐ Home Monitoring Automation:
  • Goal: Investigate if the Ring camera can be accessed via API (likely unofficial/community-maintained like ring-mqtt or Node-based wrappers).
  • Use Case: Detect and track Tara's morning walks for better routine management.