Back to corpus
architecturetechnical paper candidatescore 18

Stage 0: Research Brief — Feed-Hub Flow Architecture

**Generated:** 2026-03-07 **Method:** Evolution³ Stage 0 — Pure Fact-Gathering **Topic:** Feed-Hub flow architecture evolution

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Generated:** 2026-03-07 **Method:** Evolution³ Stage 0 — Pure Fact-Gathering **Topic:** Feed-Hub flow architecture evolution ### Scale - **71 Python files**, 28,134 lines of code - **64 Prefect flows**, 7 standalone scripts/libs - **35 deployments** via single `serve()` call in `deploy_feed_flows.py` - **29 Supabase tables** accessed across all flows - **5 embedded Prometheus servers** (:9122, :9125, :9126, :9127, :9128) ### Flow Domains (8 groups) | Domain | Flows | Lines | |--------|-------|-------| | Infrastructure/Monitoring | 12 | ~5,500 | | Serenity Soother (ss_*) | 19 | ~6,200 | | Memory/Knowledge | 6 | ~2,700 | | Noosphere/Dream/Creative | 9 | ~2,500 | | Intelligence/Analysis | 6 | ~3,400 | | Operational/Reporting | 6 | ~1,800 | | Design Pipeline | 4 | ~1,300 | | FirstDate App | 2 | ~520 | | Shared libs + CLI tools | 7 | ~2,900 | ### Deployment Architecture - **Mac1**: Primary host, runs Prefect via LaunchAgent - **Cloud VM**: Prefect server at :4200 (systemd service), but **broken** — `cross_pollination_crawler.py` crashes import chain - **Mac5**: Only `command_executor.py` (polls Supabase `command_queue`) - **Scheduling**: 2min→monthly range. 35 Prefect deployments, all `serve()` pattern (single process) ### External Dependencies (12+ services) Supabase (primary), Discord webhooks (9 channels), Gemini API, Prefect, Apify, Prometheus, YouTube API/Analytics, NUMU FARE (:8500), Noosphere MCP, EvoFlow TIE, GCS, Orbit, ab-browser

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.