AI agent frameworks, orchestration patterns, memory systems, and the ZOE agent stack.
| # | Title | Type | Summary |
|---|---|---|---|
| 026 | Hindsight: Agent Memory System | STANDALONE | Evaluate Hindsight (vectorize-io) as the memory layer for ZAO OS AI agents |
| 070 | Sub-agents vs Agent Teams | STANDALONE | Two multi-agent paradigms mapped to ZAO OS Paperclip setup + Claude Architect patterns |
| 071 | Paperclip Rate Limits & Multi-Agent API Key Management | STANDALONE | Solving rate limit hits when running 5 Paperclip agents on one Anthropic API key |
| 084 | Farcaster AI Agents Landscape | STANDALONE | Survey of the Farcaster AI agent ecosystem as of March 2026 |
| 085 | Farcaster Agent Technical Setup | STANDALONE | Building and deploying a Farcaster AI agent with Neynar |
| 090 | AI-Run Community: Agent OS | STANDALONE | Design for a self-improving agent system running ZAO community autonomously |
| 161 | Agent Harness Engineering (LangChain) | STANDALONE | LangChain DeepAgents, virtual filesystems, and the Ralph Loop applied to ZAO |
| 171 | Council of High Intelligence: Multi-Agent Deliberation | STANDALONE | Nyk's 11-agent deliberation system evaluated for ZAO-specific triads |
| 202 | Multi-Agent Orchestration: OpenClaw + Paperclip | STANDALONE | Agent hierarchy where OpenClaw watches Paperclip workers and Zaal acts as Claude Agent |
| 205 | OpenClaw + Paperclip + ElizaOS Deployment Plan | STANDALONE | Exact deployment steps for the full three-tier agent stack |
| 206 | LobsterAI Agent Architecture | STANDALONE | Evaluate LobsterAI (NetEase Youdao) for patterns transferable to ZAO agent/skill architecture |
| 208 | Paperclip Plugins Ecosystem Update | STANDALONE | Map of 11 community plugins, 4 examples, and ZAO integration plan |
| 227 | Agentic Workflows 2026 | STANDALONE | Agentic workflow landscape — frameworks, SDKs, DAO/community patterns, music agent use cases |
| 234 | OpenClaw Comprehensive Guide | CANONICAL | Agent memory, knowledge graphs, MCP servers, and context management for OpenClaw |
| 235 | Free Web Search MCP Alternatives | STANDALONE | Best free web search options to replace Brave Search MCP on $5/month VPS |
| 236 | Autonomous OpenClaw Operator Pattern | STANDALONE | 3-layer memory, heartbeats, delegation, and nightly consolidation for ZOE |
| 237 | USV Agents, Tasklet, Malleable Software | STANDALONE | USV thesis on agents, tasklets, and the "build something you want" era |
| 239 | Agent Frameworks & Infrastructure Evaluation | STANDALONE | Evaluate 16 agent frameworks, security tools, and workflow automation for ZAO OS |
| 245 | ZOE Upgrade: Autonomous Workflow 2026 | STANDALONE | Highest-leverage upgrades to ZOE — autonomous routines, Telegram, Neynar, founder agent playbook |
| 246 | Neynar API: Creative Agent Uses | STANDALONE | Underused Neynar endpoints and patterns ZOE can leverage for community management |
| 247 | Top 50 Local AI Models 2026 | STANDALONE | Top local AI models evaluated for ZAO OS needs (privacy + best outputs) |
| 251 | HuggingFace Platform Deep Dive | STANDALONE | Everything ZAO can do on HuggingFace beyond ACE-Step — orgs, models, Spaces, datasets |
| 253 | AutoAgent: Self-Optimizing Agents | STANDALONE | AutoAgent's self-optimizing loop and implications for ZOE and autoresearch |
| 256 | ZOE Agent Factory Vision | STANDALONE | Architecture for ZOE as an agent factory spawning specialized sub-agents |
| 259 | Agent Self-Optimization | STANDALONE | AutoAgent + Claude Code hooks for agent self-improvement |
| 262 | Virtuals Protocol: Agent Payment Rail | STANDALONE | Virtuals Protocol as a payment rail for AI agents |
| 266 | Mission Control v2 | STANDALONE | Open-source AI agent orchestration platform evaluation |
| 267 | OpenClaw Skills & Capabilities Reference | STANDALONE | All available OpenClaw skills, extensions, and channel integrations |
| 268 | Milady AI: ElizaOS Evolution | STANDALONE | Milady AI as next-gen ElizaOS distribution for desktop-first agents |
| 278 | Agentic Bootcamp vs ZAO Agent Squad | STANDALONE | Gap analysis between bootcamp curriculum and ZAO's 7-agent squad |
| 280 | FID Registration & x402 Deep Dive: How to Give ZAO Agents a Farcaster Identity | STANDALONE | Map every path to registering a Farcaster FID for CASTER agent, understand why fid-forge x402 failed, and determine the cheapest/fastest approach |
| 281 | Farcaster Agents Landscape & Registration Paths: The Complete Picture | STANDALONE | Map every active Farcaster agent, understand how they registered, find the cheapest proven path for CASTER |
| 288 | Agent Squad Monitoring & Visualization Dashboards | STANDALONE | Agent Squad Monitoring & Visualization Dashboards |
| 288 | Multi-Agent Dashboard Visual Research: UI Patterns for Agent Squad Monitoring | STANDALONE | Find real visual examples of multi-agent dashboards, extract UI patterns, and recommend an approach for ZAO's 7-agent admin dashboard |
| 289 | ZOE Dashboard: Chat-Based Command Center UX Patterns | STANDALONE | ZOE Dashboard: Chat-Based Command Center UX Patterns |
| 290 | FISHBOWLZ Agentic Participants | STANDALONE | AI agents as persistent room participants in FISHBOWLZ audio spaces |
| 291 | Farcaster Agentic Bootcamp Days 3-5: Agents, Memory, Identity | STANDALONE | Extract actionable patterns from bootcamp days 3-5 for FISHBOWLZ agent participants — event-driven agents, stateful memory, and ERC-8004 identity. |
| 292 | Pixel Agents Dashboard Customization for ZAO OS | STANDALONE | Make pixels.zaoos.com interactive — click-to-dispatch, ZAO branding, Supabase integration |
| 293 | Multi-Agent Orchestration Tools, GitNexus Knowledge Graphs & High-Impact Agent Prompts | STANDALONE | Evaluate three tools found on X/Twitter for ZAO agent squad relevance: (1) Trellis multi-agent framework, (2) GitNexus codebase knowledge graph, (3) exploraX_ 40 … |
| 296 | Agentic Workflow Optimization: Powerful Center + Cheap Edge Operating Model | STANDALONE | Define the optimal division of labor between Claude Code (Opus 4.6 on laptop) and VPS agents (Minimax M2.7 on OpenClaw), based on empirical testing and industry patterns |
| 307 | The Great Convergence: Agent Harness Architecture | STANDALONE | Map the industry-wide convergence on agent harness architecture and what it means for ZAO OS's agent stack (ZOE, OpenClaw, skills system) |
| 318 | Cassie Heart Multi-Agent Coordination | STANDALONE | Bootcamp Session 10: persona engineering, softmax selection, Quilibrium free stack |
| 325 | ElevenLabs Agents: Voice AI Platform for ZAO OS | STANDALONE | Deep dive into ElevenLabs Agents (formerly Conversational AI) for building a voice agent with Zaal's Professional Voice Clone for The ZAO community |
| 325 | ZABAL Agent Swarm Economy | CANONICAL | 3 brand agents (ZOE/HERALD/FLIPPER) with Privy wallets, autonomous ZABAL trading via 0x API, x402 content commerce on publish.new, Vercel cron schedules, community governance, $45 seed to 5x volume |
| 339 | Austin Griffith CLAWD & ETHSkills Agent Patterns | CANONICAL | CLAWD's zero-sell treasury ($177K), auto-burn, dApp deployment. ETHSkills 19 skill files + verified Base addresses. Two-model cost pattern. Aerodrome > Uniswap on Base. x402 SDK 5-line implementation. All patterns mapped to VAULT/BANKER/DEALER |
| 340 | CLAWD Deep Dive: 4 Systems to Fork | CANONICAL | LarvAI conviction governance (fork contract, $0.50 deploy, 8 training questions). Agent Bounty Board (Dutch auction, $0.005 deploy, MIT fork). Ephemeral agents (SKIP Docker, USE Vercel+Supabase). ERC-8004 registration ($0.01 for all 3 agents, 45K+ discoverable) |
| 344 | Bankr Bot Agent Trading Skills | CANONICAL | 34 plug-and-play skills (symbiosis swaps, zerion portfolio, neynar Farcaster, moltycash x402, erc-8004 identity, stakr vaults). Privy-based. Coinbase Ventures backed. Complements our custom ZABAL logic |
| 345 | ZABAL Agent Swarm Master Blueprint | CANONICAL MASTER | Definitive build plan synthesizing 8 docs (322-344). 10 phases, $45.55 total cost, $0.51/mo ongoing. Architecture stack, build order, key numbers, codebase reference, cross-doc index |
| 351 | ZABAL Agent Swarm Activation Checklist: How It SHOULD Work vs How It COULD Work | STANDALONE | Exact remaining steps to go live, what happens when crons fire, what could go wrong, and honest assessment of current code vs ideal behavior |
| 353 | Autonomous Agent Trading: Beyond Fixed Schedules | STANDALONE | Replace fixed day-of-week schedules with intelligent, autonomous trading triggers for VAULT/BANKER/DEALER |
| 360 | Profit Agent: Hot Wallet Money-Making Strategy | STANDALONE | Design a dedicated profit-seeking agent (separate from VAULT/BANKER/DEALER ecosystem agents) with a hot wallet whose only job is generating revenue |
| 363 | Darwinian Agent Evolution: Die, Mutate, Respawn, Iterate | STANDALONE | Design how agents that run out of money die and spawn improved versions -- LLM-guided parameter mutation + natural selection for trading strategies |
| 364 | Multi-Harness Agent Orchestration: OpenClaw + Hermes + Tournament Model | STANDALONE | Design how ZOE runs multiple agent frameworks (OpenClaw, Hermes, others) side by side, dispatching to whichever is best for each task, with tournament-style competition … |
| 420 | HyperFrames: HTML-as-Video for AI Agents | STANDALONE | HeyGen open-source Apache 2.0 HTML→MP4 framework (2.1k stars, v0.4.3). Claude Code + OpenClaw native. Adopt for ZAO Stock promos, newsletter, socials, WaveWarZ, ZOE video output. Credits OpenClaw. |
| 433 | Agent Outbound Phone Calls | STANDALONE | Ring-a-Ding ($19/mo flat, BYOK OpenAI) vs DIY Twilio Media Streams + OpenAI Realtime vs LiveKit+Deepgram. ZAO Stock vendor + artist outreach use cases. TCPA + two-party consent guardrails |
| 435 | ZOE Effectiveness v2 Playbook | STANDALONE | 18 ZOE upgrades ranked ship-today/week/when/skip. Top 3 with code: morning brief 5am ET, evening reflect 9pm ET, /summarize + /recap + /focus slash commands. Respects Zaal's no-quiet-hours pref. |
| 447 | Agent Stack 7-Day Improvement Sprint | STANDALONE | Synthesize docs 435 (ZOE effectiveness), 436 (phone agentic stack health), and 440 (Claude Code process level-up) into the top 5 concrete agent improvements to ship in … |
| 451 | AO Claude Code Dialog Block Forensics | STANDALONE | AO Claude Code Dialog Block Forensics |
| 452 | AO Sidebar Counter Filter Fix | STANDALONE | AO Sidebar Counter Filter Fix |
| 453 | AO Offline Banner WebSocket Diagnosis | STANDALONE | AO Offline Banner WebSocket Diagnosis |
| 454 | Agent Stack Reliability Hardening (Apr 20) | STANDALONE | Audit the VPS portal stack's reliability and identify 7 high-impact hardening improvements, with focus on the Apr 19-20 silent overnight (3 AO sessions died, no … |
| 457 | Silent Failure Hunt: ZAO Agent System | CANONICAL | 8 silent-failure findings in src/lib/agents (2 critical, 2 high, 4 medium). PRs #232 + #233 fixed criticals + mediums. |
| 460 | ZAO Agentic Stack End-to-End Design | CANONICAL MASTER | 4-layer stack (Edge / Concierge / Specialists / Cloud Routines), 8-agent table, dispatch tree, 5 gaps + 3 dups + week/month/quarter adoption plan. Builds on 234, 236, 412, 415, 422, 441, 459. |
| 464 | ZOE Telegram Reply-Context + Ship-PR Loop | STANDALONE | Root cause for "I didn't send that" bug (bot.mjs has no conv memory + doesn't read sent.json), full Telegram Bot API 2026 capability matrix, ship-PR loop design via inline keyboards + handleSpawnAgent. 30-line patch to fix bug today. |
| 465 | ZOE Observability + Dispatch Hardening | STANDALONE | Post-#253/#254 followups: unified events.jsonl, daily digest + cost tracking, @zoey/@wallet/@rolo dispatch with result polling, watchdog alert threshold, voice+photo+channel scope. 12-task ranked plan, 1-10 difficulty scores. |
| 466 | AO UI Button Audit | STANDALONE | Document root causes of AO dashboard button UX issues (Kill, New Session) and provide patch guidance for VPS deployment. |
| 467 | ZAO Branded Bot Fleet, Telegram hub (Magnetiq no-API) | STANDALONE | 5-bot Telegram fleet: Magnetiq (SAPS idea-gen + link poster), WaveWarZ (planning), ZAO Stock (conversational), ZAO Devz (autonomous coding via AO spawn), Research (/zao-research + RSS/email). Hub-spoke via ZOE. Approach 1+2 hybrid. 5 ZABAL Connector Magnet concepts. Model routing matrix. |
| 468 | ZAO Farcaster Hub: POIDH + HyperSub + dual-hub design | STANDALONE | Second bot hub on Farcaster. POIDH bot confirmed live (Arbitrum/Base/Degen bounties, no token, Frame v2 mini app). HyperSnap unresolved — likely Hypersub (Fabric subscriptions); needs Zaal confirm. Shared plumbing both hubs, draft-to-Telegram approval for casts, per-bot fid + Neynar managed signer, 7-bot total by Week 5. |
| 473 | clawdbotatg Apr 21 Update: ZOE/OpenClaw Patterns | STANDALONE | 10-day delta since docs 339/340. CLAWD shipped ss-triage-router MCP (Haiku classifier → Haiku/Sonnet/Opus, ~75% cost save), fifth-builder autonomous SE-2 worker (4-stage resumable, 5-item secret hygiene after leaked key incident), leftclaw-services in prod ($20-$1000 agent services, 4 named workers, x402+on-chain). 22 new repos in 10 days, 190 total. Direct fork targets + file-level changes for ZOE v2. |
| 474 | BCZ 101 Bot + Transcript RAG Best Practices | STANDALONE | Blueprint for a Farcaster-native BCZ 101 bot. Forks atenger/gmfc101 (warpee.eth's RAG bot, Apache 2.0, pushed 2026-04-22). 3-path LLM router (metadata/contextual/hybrid) beats naive top-k RAG. Port Python to TS on Next.js 16 + Supabase pgvector + Neynar. Canonical transcript schema for content/transcripts/. Reuses fishbowlz Minimax+Anthropic pattern. SQL schema, file layout, build order. |
| 479 | Walden Yan — Multi-Agent Patterns (Cognition) | CANONICAL | Writes single-threaded, reads parallel. Clean-context reviewer catches 2 bugs/PR (58% severe). Smart-friend works cross-frontier. Manager-children for 10-PR scopes. Swarms are a distraction. |
| 483 | Hermes Agent — Local-LLM Framework | STANDALONE | Nous Hermes + Qwen3.6-27B for per-brand bot fleet on VPS 1 only. Tool-calling muscle, ZOE stays frontier. Deterministic tool gating. honcho for memory. |
| 484 | Matricula — Autonomous Farcaster Agent | STANDALONE | 4-layer self-improvement loop (actions/metrics/reflection/strategy) + 3-goal KPI (Influence/Patron/Treasury) + energy manager ($0.50/day). Adopt design in TypeScript. |
| 487 | QuadWork — 4-Agent Dev Team | STANDALONE | Head+Dev+2 Reviewers, 2-of-2 gate, 15-min trigger, port 8400, MIT. Overnight batches for docs + tests only. Codex+Claude cross-frontier review. |
| 488 | CORTEX — Synthetic Cognition Memory | STANDALONE | Hippocampal memory + dream cycles + reconsolidation + 7-factor hybrid search. Apache-2.0. 500/500 LongMemEval. Use for ZOE+ROLO, not per-brand bots. |
| 491 | QuadWork Install for 3-Repo Split | STANDALONE | Install plan for v1.12.0. Cross-frontier role lock (Codex/Claude/Codex/Claude). .quadwork-allowlist per-repo guard. Run on zao-chat + zao-brain only, not on zao-os. $4/day budget cap. Companion to doc 487. |
| 495 | Team Telegram Bot 2026 Patterns — v1.5 Architecture Call | STANDALONE | Decide the architecture for the ZAOstock Team Bot v1.5 before committing to group-mode design: heuristics vs local LLM vs cloud LLM, single-group vs split-group … |
| 496 | ElizaOS 2026 Assessment: For ZAOstock Bot Decision | STANDALONE | ElizaOS 2026 Assessment: For ZAOstock Bot Decision |
| 497 | Quad / QuadWork Workflow Deep Dive | STANDALONE | Know WHEN the 4-agent team wins, WHEN a single Claude session is faster, and HOW to run the first real ZAO batches without blowing up. |
| 523 | ZAO Agentic Systems Full Audit + Fix-PR Pipeline + Hermes Dual-Bot Architecture | STANDALONE | Lock in every agentic system ZAO has (codebase + VPS + research consensus), fix the broken auto-PR pipeline, spec the Hermes-pattern dual ZAOstock bot, upgrade ZOE. One … |
| 524 | ZAO Agentic Systems - Everything Map (LIVE / STARTED / PLANNED / ARCHIVED) | STANDALONE | Master index of every named agent / bot / orchestrator across ZAO OS, BCZ, ZAOstock, and the VPS. Live + started + planned + archived in one doc, so future planning … |
| 527 | Multi-Bot Telegram Coordination - The Best-Practice Playbook for ZAO | STANDALONE | Stop the multi-bot collisions that broke /fix (ZOE replied "Unknown skill: fix" intercepting another bot's command), spec the supervisor + specialist + topic-lane … |
| 529 | Hermes Quality Pipeline - Pre-Critic Gates + Conflict Policy | STANDALONE | Stop Hermes from opening PRs that fail CI or carry merge conflicts. PR #321 (the manually-opened /healthcheck PR) is sitting in mergeStateStatus: DIRTY with `Lint & … |
| 531 | Hermes Honest Audit - Pivot or Persist | STANDALONE | Tell Zaal honestly whether to keep building the Hermes pair or pivot. 24 hours, 8+ patches, 9 production runs. Only 1 successful (and it was the simplest task /version … |
| 541 | Hermes Gaps vs Industry Best Practices (Apr 27 2026) | STANDALONE | Identify 3-5 concrete gaps between ZAO's Hermes pair (Stock-Coder + Hermes-Stock on VPS) and the autonomous-coding-agent industry standard as of 2026-04-27. Recommend … |
| 546 | Hefty.bot: Local-First Personal AI Harness (Slava / Based Rooms tip) | STANDALONE | Evaluate hefty.bot - a closed-source local-first personal AI harness Slava flagged in a Based Rooms convo as "another harness a community member is building" - against … |
| 547 | Multi-Agent Coordination: Bonfire, ZOE, Hermes (Apr 28 2026) | STANDALONE | Design how ZOE bot, Hermes Stock-Coder + Critic, and the new ZABAL Bonfire Bot work together without conflicts, duplicate writes, or context drift. |
| 559 | Wetware (ww): P2P OS for Autonomous Agents |
STANDALONE | Decide whether wetware/ww (P2P OS, capability-based security, libp2p + Cap'n Proto + WASM) belongs in ZAO's agent stack alongside QuadWork / ECC / 1code. |
| 567 | Hugging Face Local Models + Web UI + Claude Code Context Bridge | STANDALONE | Zaal said "I wanna try to have a couple local models that I can reach out to on a specific website or wherever that I can ask questions when needed and maybe it's hooked … |
| 568 | Aware Brain - Local-First Knowledge Graph Chat for ZAO | STANDALONE | Aware Brain - Local-First Knowledge Graph Chat for ZAO |
| 574 | Inbox Batch Apr 30: Agent Commerce, Alignment Skills, Local Stack Update | STANDALONE | Synthesize 10 unread inbox items (5 X posts, 4 Reddit, 1 product page) into action-bridges. Anchor against the install wave of Docs 558-573. |
| 599 | ZAO Bonfire Bridge: Multi-Agent Operating Group | STANDALONE | Convert the ZAO Bonfire Bridge Telegram group from a bot-to-bot relay into Zaal's primary autonomous-agent operating surface. Agents collaborate in the open. Bonfire … |
| 600 | ZAO Agentic Stack Coordination v1 | STANDALONE | Take stock of every agentic system Zaal currently runs, identify what works vs what's broken, and propose a coordinated architecture where Claude Code is Zaal's primary … |
| 601 | Agent Stack Cleanup Decision | STANDALONE | Stop the bot proliferation. Pick the smallest viable agent stack that actually serves Zaal day-to-day, and kill the rest. Replaces the implicit "add another bot" pattern … |
| 602 | TradingAgents Multi-Agent Pattern → Adapt for ZAO Social + Project Management (NOT Trading) | STANDALONE | Document the TradingAgents (Tauric Research) multi-agent debate architecture. Identify which patterns transfer to ZOE's concierge brain (per doc 601 Option D) for two … |
| 603 | TradingAgents Multi-Agent Pattern → Adapt for ZAO Social + Project Management (NOT Trading) | STANDALONE | Document the TradingAgents (Tauric Research) multi-agent debate architecture. Identify which patterns transfer to ZOE's concierge brain (per doc 601 Option D) for two … |
| 604 | Best Personal Concierge AI Agent Architectures (2026) → Apply to ZOE | STANDALONE | Survey the best personal-concierge AI agent architectures shipping in 2026 (Letta, Mem0, Graphiti, Cognee + Anthropic patterns). Steal the patterns that make ZOE … |
| 605 | Agentic tooling landscape (May 2026) - what to add to the ZAO stack | STANDALONE | Survey the AI-agent tooling shipping right now, decide what plugs into ZOE / Hermes / Bonfire, and what stays out. Same-day companion to doc 601 (agent stack cleanup) … |
| 607 | Three bots, one substrate: ZOE + ZAOstock + Bonfire operating model (May 2026) | STANDALONE | Define how the three named bots (ZOE for Zaal, ZAOstock bot for festival team, Bonfire bot for public ZAO) share data, route messages, and stay coherent without … |
| 617 | bczyapz101 bot architecture (gmfc101 fork plan) | STANDALONE | Stand up an @bczyapz Farcaster bot that answers questions about the 18 BCZ YapZ episodes by forking and adapting Adrienne's gmfc101 / Warpee.eth codebase, with a clear … |
| 619 | Link Batch May 6 Triage | STANDALONE | Triage 16 items (5 ZOE inbox + 11 link batch) Zaal sent on 2026-05-06. Most map to existing research; surface what's actually new and what action is needed. |
| 620 | Bonfire push-everything: auto-ingest pipeline for Zaal's personal knowledge graph | STANDALONE | Make Bonfire writes happen automatically from every source Zaal touches, so @recall always returns useful answers. No manual curation. |
| 632 | r/hermesagent: Different Project (NousResearch) | STANDALONE | r/hermesagent: Different Project (NousResearch) |
| 644 | ZAO Agent Stack Canon + Team Bot Template | STANDALONE | ZAO Agent Stack Canon + Team Bot Template |
| 645 | Agent canon + team-bots audit (Magnetiq + AttaBotty) | STANDALONE | synthesize every ZAO agent doc into one reference, then pressure-test the team-bots code that shipped in PR #503 against that canon. Decide ship/hold. |
| 646 | Brand-fit audits: Magnetiq + AttaBotty bots | STANDALONE | pressure-test each team bot's persona, scope, commands, and memory model against the actual brand reality. Apply low-risk persona tightenings now, queue larger changes. |
| 647 | Agent Quality Deep Research (Hub) | STANDALONE | Concrete, prioritized patterns to make ZOE, Hermes, and the ZAO child-bot fleet measurably better. Six dimensions researched in parallel; this hub synthesizes them into … |
| 648 | Ryan Kagy Sync: ZAO Civilization, Agent Lineage, Soul of All Games | STANDALONE | Capture the 2026-05-13/14 Ryan Kagy call - decisions, the Option A/B partnership fork, Ryan's agent-architecture philosophy, two product ideas - and flag where it … |
| 650 | cowork-zaodevz: the imanagent + a from-scratch VPS build Iman can follow | STANDALONE | Audit what's already in songchaindao-dot/cowork-zaodevz (it's mature — most of the agent is already specified). Design the imanagent as Iman's first ground-up Telegram … |
| 665 | Bonfires Deep Dive + ZAO Integration Plan | STANDALONE | Bonfires.ai (built by NERDDAO / Bonfires Labs) is ZAO's locked-in knowledge-graph + agent-memory partner per Doc 601 primary surfaces. Zaal has a live ZABAL bonfire … |
| 668 | ZAO Agent + Bot Improvement (May 2026 Hub) | STANDALONE | /zao-research DEEP dispatch on "how do we make our bots better." Triggered by ZOE's own session export flagging her 8-turn memory window + the gap of 4 missing projects … |
| 668 | ZAOcoworkingBot Full Audit (May 2026) | STANDALONE | ZAOcoworkingBot Full Audit (May 2026) |
| 669 | Bonfires: Everything We Know (Consolidated + Extended) | STANDALONE | Pull everything we've learned about Bonfires into one doc, then push further. Doc 665 was the entry point; Doc 668d was the integration spec; this is the canonical … |
| 671 | LLM Fictional-Permission Hallucination Fixes (ZAOcoworkingBot) | STANDALONE | Stop @ZAOcoworkingBot from telling Iman to "approve in the system dialog" when no such dialog exists. Three independent research dispatches converge on a 3-phase fix … |
| 672 | ZAOcoworkingBot Full Audit (post-v2.13) | STANDALONE | Full-codebase audit of songchaindao-dot/cowork-zaodevz after v2.13 deploy. Cover what 668a-f missed + flag any new issues v2.13 introduced + prep for Phase 2/3 from … |
| 673 | ZAOscribe Spec (live audio - todo bot) | STANDALONE | One-step Telegram bot replacing 5-step manual flow (record - download - upload - transcribe - paste). User sends voice message to @ZAOscribeBot; bot transcribes … |
| 673 | ZOE <-> Bonfires Dialog + Automation (Phase 2 Research) | STANDALONE | ZOE <-> Bonfires Dialog + Automation (Phase 2 Research) |
| 674 | ZAOscribe: Discord Audio -> Action Items (Best-of + Build Plan) | STANDALONE | Ship the BEST possible audio-capture-to-todo bot for the 4-person ZAO core team (Zaal + Iman + ThyRev + Samantha). The pivot from doc 673 v2: this is a **Discord bot … |
| 676 | Bonfires Knowledge-Graph Utilization (DISPATCH) | STANDALONE | Now that the ZABAL Bonfire is usable - 780 episodes ingested, write pipeline live, ZOE bridge shipped - research every concrete way the ZAO ecosystem should USE the … |
| 677 | Connecting the Bonfire to the cowork-zaodevz GitHub Repo | STANDALONE | ZAOcoworkingBot v0.3.1 already pipes Telegram tracker events (/add /done /wip) into the ZABAL bonfire. The GitHub side of the same repo - commits, PRs, issues - does not … |
| 679 | Coworking Agent: Telegram @-Mentions + Iman DM-to-Code Pipeline | STANDALONE | Audit the cowork-zaodevz Telegram bot against best practices, then lock two new features - (A) @-mention the owner on Telegram when an action is assigned or changes … |
| 683 | ZOE Troubles Analysis + Ryan Kagy Followup | STANDALONE | Deep analysis of the ZOE agent troubles visible in the 2026-05-20 "ZAO Civilization" Telegram thread, with code evidence from bot/src/zoe/, plus the followup package … |
| 684 | ZAO Bot Fleet Architecture (locked) | STANDALONE | ZAO runs 5+ bots with no shared design - ~40% duplicated code, no agreed comms pattern, a prior 7-agent squad (openclaw) that collided and was killed. This doc locks the … |
| 689 | AI Agent Memory + Personal Knowledge Systems (Community, May 2026) | STANDALONE | Synthesize cross-cutting patterns from 4 community posts about how builders solve agent persistence + knowledge retention. |
| 690 | X Posts Roundup (ZOE Inbox, May 2026) | STANDALONE | Assess 5 forwarded X posts (May 9-20) clustered around Claude Code setup, agent deployment, and auth tooling. Determine whether they surface patterns relevant to ZAO's … |
| 698 | Agent Stack Re-Audit + Codebase Audit + Next-Fix Todos + Paperclip Restart Plan | STANDALONE | Current-state audit of every ZAO agent and codebase, a prioritized next-fix todo list, and a documented plan for the proposed Paperclip restart. |
| 699 | The State of Agentic AI, 2026: A Deep Study | STANDALONE | A current, evidence-based study of the entire agentic-AI landscape - frameworks, coding agents, memory, multi-agent orchestration, evaluation, protocols, web3 agents … |
| 701 | Agent Harness Engineering: A Deep Dive | STANDALONE | Define the agent harness as a discipline - anatomy, the harness-beats-model evidence, how to engineer one, how to measure it - and apply it to ZAO's Hermes, QuadWork … |
| 717 | Posting /meeting Bonfire episodes via the VPS | STANDALONE | Route the /meeting skill's Bonfire episode posting so the API key never has to live on Zaal's mac - the VPS already has it. |
| 727 | ZOE as agent builder: orchestrator + supervisor + learning loop | STANDALONE | Lock the architecture for ZOE-as-orchestrator. ZOE classifies any incoming task, spawns the right agent (Hermes / child bot / Claude Code subagent), supervises the … |
| 734 | hermes-orchestrator framework | STANDALONE | Snapshot the public hermes-orchestrator MIT package - what it is, what's shipped, what the open stacked PRs add, how it grounds doc 727 (ZOE-as-builder), and how to … |
| 735 | Apple Containerization as a sandbox for autonomous agents on macOS | STANDALONE | Lock how Apple's apple/containerization Swift package (macOS 26 + Apple Silicon, Apache 2.0, 8.5k stars, released May 2025) fills the macOS-native-sandbox gap that doc … |
| 754 | Why /meeting did not push to Bonfire today (config gap, not architecture mismatch) | STANDALONE | Diagnose why today's /meeting run printed "BONFIRE_API_KEY / BONFIRE_ID not set - skipping graph write", reconcile the conflicting architecture stances in /bonfire … |
| 758b | m1k1o/neko Install + RTMP Forward (24/7 ZAO Radio) | GUIDE | Stand up a 24/7 headless-browser audio source on VPS via m1k1o/neko v3.1.0 (canonical active fork), native GStreamer RTMP to Restream/YouTube/Twitch. Key decisions: use chromium image, neko's built-in Broadcast pipeline (not external ffmpeg). Companion to 758c (Telegram /claim bot) + 758d (Discord radio bot). |
| 758c | Telegram /claim Bot Pattern for ZABAL Mentors | DECISION | First-write-wins /claim bot for ZABAL Games mentor channel: captures builder-handle, audit log to Supabase, Zaal moderates. Decision: reuse Hermes + Grammy (vs new bot). Companion to 758b/d/e. |
| 758d | Discord 24/7 ZAO Musician Radio Bot | DECISION | 24/7 Discord music bot landscape post-2021 YouTube crackdown — what's safe in 2026. ZAO artists own their tracks so legal posture is stronger. Recommended stack for playing artist-owned audio in Discord voice channels. Companion to 758b/c. |
| 759 | Agent best practices + ZOE orchestrator gap analysis | STANDALONE | (A) Slim 2026 agent state-of-the-art synthesis. (B) Methodology PRD for a "100 best practices" list - structure only, no items. (C) Honest gap analysis: where ZOE is … |
| 760 | InfiniteZero / DIN: Decentralized Intelligence Network on Optimism Sepolia | STANDALONE | Capture what Infinite Zero Foundation's DIN protocol is, what its devnet (sepolia-op-devnet) requires from a participant, and whether ZAO should run a node or just … |
| 761 | ZAO Farcaster Multi-Agent System on the Quilibrium Stack | STANDALONE | A sovereign, multi-agent Farcaster presence for the ZAO/$ZABAL community, |
| 770 | ZOE orchestrator code audit (post-merge, pre-trust) | STANDALONE | Audit the ZOE orchestrator that merged via PR #728 (doc 759 Gaps 1-5) + the relay from #727, before it is trusted with autonomous, cost-incurring runs. Diagnose why the … |
| 773 | ZOE orchestrator HIGH-severity fixes (doc 770 follow-up) | STANDALONE | Fix the 5 HIGH findings from the doc 770 audit so the orchestrator is safe to trust with autonomous, cost-incurring runs. Each fix lands with a regression test where the … |
| 775 | What ZAO's Agent Stack Can Do Now (2026-05-30) | STANDALONE | Inventory the new capabilities unlocked after this session's work (live graph recall, orchestrator Gaps 1+2, Supabase CRM, typed Bonfire intake), name the single … |
| 781 | ZABAL Bonfire contribution architecture (shared graph + soft barrier) | STANDALONE | let EVERYONE in the ZABAL Gamez 3-month buildathon contribute to the |
| 796 | ZOE: Broadcast Bot → Conversational, Well-Timed Assistant | STANDALONE | Redesign ZOE from a broadcast bot into a conversational, well-timed concierge — proactive timing, reply quality, not blast messaging |
| 801 | ZOE / Cowork Bot / Cowork Dashboard — Systems Audit + Consolidation Map | CANONICAL | Single ground-truth audit of the three live ZAO agent/app systems (ZOE concierge, cowork tracker bot, cowork Kanban dashboard) + consolidation map |
| 862 | ZOE Multi-Agent Fan-Out to Bonfire | STANDALONE | When Zaal talks to ZOE, fan out 4 cheap Haiku reader agents (people/projects/decisions/commitments) after mirrorTurn() that extract structured facts and write them to the ZABAL Bonfire graph - conversation becomes durable graph memory |
| 999 | How I AI: What a Harness Is and How to Build One with Claude Agent SDK | STANDALONE | Live implementation walkthrough: Claude Agent SDK + custom adapters + permission gates + artifact store. The episode's key addition: opinionated tool adapters beat generic MCPs; constraints drive better outcomes than open-ended prompting |
| 864 | farscout: Farcaster research scout on the board + watched by ZOE | STANDALONE | What farscout is (free autonomous Farcaster scout, grounds findings in real sources, writes to ZABAL Bonfire), added to the thezao.xyz/bots board + ZOE WATCH_TOPICS so she pings if it goes cold |
| 872 | Making ZOE more effective: live feedback, mid-flight clarification, steering | STANDALONE | The 3 things Zaal wants (progress narration, non-blocking clarify with 60s timeout, live mid-run steering) mapped to ZOE's code + ranked vs reflection/grounding/memory/caps patterns by impact-for-effort || 875 | NousResearch Hermes 7-Day Setup: What ZAO's Hermes/ZOE Should Steal | STANDALONE | @zaimiri's 7-day layering (identity > memory > skills > tools > telegram > crons > profiles) from NousResearch hermes-agent, mapped to ZAO Hermes (bot/src/hermes/) + ZOE. Name collision with ZAO's own Hermes. |
| 882 | ZAOscout: Full Audit + How To Do More | AUDIT | State of ZAODEVZ/ZAOscout (canonical): keyless fetch trio, watch/digest/share, MCP + tiered API, GH Actions digest, fly deploy, 26 tests. Supersedes old farscout + the redundant scraper repo. Noise problem already solved by watchlist-anchoring. Roadmap: flip on OpenRouter digest, fix local path, tune watchlist, mine workflow. |
| 883 | KORRO: The AI-Run Company Audit | AUDIT | Audit of github.com/KorroAi - 18-day-old self-described autonomous AI company, 11 repos, weekly drops. Steal: claude-is-tripping (3-agent dialectic = ZAO council pattern), mue-x AST-validate+rollback loop into Hermes, drunk-claude/claude-creativity ideation skills. Reject the "zero humans" posture (Doc 601 chose opposite). Curated lists confirm superpowers stack. |
| 887 | Agentverse (Fetch.ai): What It Is + How ZAO Should Use It | STANDALONE | Fetch.ai's cloud platform to build/host/discover AI agents (uAgents, Almanac, ASI:One LLM routing). Recommend: launch ONE free hosted read-only 'ZAO concierge' for ASI:One discoverability; do NOT migrate the ZOE/Hermes stack; skip FET (hosted = free). 7/10 platform, reliability + doc gaps. |
| 888 | proof-531: Claude Agent Shipping an App on a /loop Cron | AUDIT | A real iOS/Android app built by a Claude agent on /loop 30m /do-work. Steal: SOUL+DOCTRINE constitution (6 immutable invariants), proof-by-type (no done without proof), scoped self-edit gate via auditor agent, 4 hard-escalation classes. Same loop ZAO/Zaal run now - formalize it. |
| 889 | tryharness.ai: Screen-Context AI Assistant | MARKET | Login-walled product, tagline 'ask anything about what you see' = screen-context vision assistant (cat. ScreenHelp/Moss). Could not get past sign-in (marked FAILED/inferred). NOT harness.io (different DevOps co). Low ZAO priority. |
| 895 | Clicky: Farza's Screen-Aware AI Tutor | STANDARD | farzaa/clicky - viral (15k likes / 3M views) open-source (MIT) macOS menu-bar AI tutor: sees screen, talks, points via [POINT:x,y:label:screenN] tags. Swift app + Cloudflare Worker proxy + Claude/AssemblyAI/ElevenLabs. STEAL the action-tag overlay pattern + key-proxy arch; don't fork (off-stack Swift). ZABAL Games workshop demo + builder-onboarding spike. New features went proprietary 2026-04-27; momentum in forks (openclicky/danpeg/skilly). |
| 890 | ZOE Improvements: Reliability, Memory, Model Routing, UX | STANDALONE | Code-grounded ZOE upgrades led by the 2026-06-23 silent auth-expiry outage (claude-max OAuth died, 12 errors/day, units stayed green, zero alert). Net-new = monitoring/alerting/failover: pre-flight auth check + dead-man heartbeat + error classification + Telegram alert. Plus memory (unused readArchive at turn time), model-routing heuristic fix, inline op summaries. |
| 891 | Farcaster Agentic Bootcamp Synthesis + the ZOL Build Plan | STANDALONE | DEEP synthesis of all 6 Builders Garden x Neynar bootcamp sessions (Agents 101, Memory/Context, Privy wallets, x402/MPP, Going Viral, EIP-8004, Multi-Agent) into a phased build plan for ZOL - a Farcaster agent ZOE runs from the Pi. Key finding: ZOL is ~80% scaffolded already (bot/src/zoe/caster + farcaster surfaces, docs 761/762); v1 = activation + persona + hosting, not greenfield. Patterns: event loop, polling-over-webhook, Privy signer+spend policy, 8004 identity/reputation, realism limits, cheap-model drafting via OpenRouter. |
| 899 | ZOE Agent-Fleet Architecture Audit | AUDIT | Verified source-of-truth for the ZAO agent fleet (2026-06-25). Key finding (checked against live code+VPS, correcting a subagent that trusted dated docs): the ZOE orchestrator is already built+deployed - doc-759's 5 gaps are shipped, so "ZOE isn't working" is an experience/wiring gap not a build gap. Full live-fleet inventory, reusable specialists, killed-list, legacy cleanup (8 fractalbots->1), external 2026 best-practice validation, the real gaps (persistent surface, ZOL->ZOE chain, Bonfire labeling), and the new ecosystem-monitor (PR #969). |
| 961 | Agent droids for ZABAL Gamez: the exponential play, and why not Clanker | DISPATCH | Five-agent DEEP on Clanker droid economy, droid economics/runway, brand/positioning, exponential fleet play, risks. Honest verdict for tokenless free build event. |
| 962 | The ZAO Bot Fleet + ETHSkills: how we are set up now, and where ETHSkills plugs in | STANDARD | Current-state bot fleet audit + where ETHSkills fits. Fleet is off-chain and LLM-brained; ETHSkills matters for on-chain writes (Splits, Hats, OREC submits). |
| 907 | Agent Fleet Dashboard | DECISION | Make the fleet visible + controllable without ssh. Verdict: BUILD a custom Next.js + Supabase /agents dashboard (not buy AgentOps/Langfuse Cloud) - card grid (status/cost/logs), approvals sidebar wired to the existing approvals.ts tiers + Telegram dual-surface, 30s heartbeat -> Supabase. Defer Langfuse self-host for deep tracing. Repos: langfuse/phoenix/agentops/helicone. |
| 969 | Token-efficient per-platform agents | DECISION | Don't build a bot-per-platform (601 killed it); use per-platform context profiles loaded on demand + cache-aware token discipline (5-min TTL, reads 0.1x) |
| 972 | ZAO Agent Stack vs the Field (mid-2026) | COMPARISON | Honest scorecard vs the 2026 frontier (web3/Farcaster + dev-agent). ZAO architecture is top-decile; real gaps are operational: observability/cost, multi-model routing (~91% Opus), self-improvement. Top-3 adopt: model routing, cost logging, systematize the Hermes self-improve loop. Agent-token economics flagged as a Respect-ethos fork. |
| 973 | Hyperagent as ZAO's hosted offload layer (decision) | DECISION | Adopt Hyperagent (Airtable's agent platform) as a bounded HOSTED OFFLOAD layer - trial ONE agent (CRM on the legacy Airtable, 25-per-run x ~10 passes, writes-on-approval), keep the core self-hosted. Value is the wired integrations, not the architecture (ZOE already is that). Budget cap + PII guardrails required. |
| 997 | Agent Harness Design (and a Harness for zaalcaster) | GUIDE | What makes a good harness (one loop, small tool surface, state-in-fs, verify-with-environment, hard caps), how teams built custom ones (Claude Code/Ralph/Cursor/Devin), OSS inventory (Vercel AI SDK + Claude Agent SDK best fit; elizaOS only Farcaster-native but overkill), and a concrete zaalcaster harness = attention-router loop (gather -> rank by tokens x score x mutual -> draft in voice -> Zaal approves -> post -> mark delivered). |
| 1004 | Multi-Agent Research Playbook (+ wire into loops) | GUIDE | Optimized many-subagent research: fan out only on independent+read-heavy work, orchestrator+2-4 scoped subagents, structured JSON output (not prose), divide-by-source dedup, and a verify layer (adversarial refute + lens judges + EXTERNAL gate + claim-status tags - consensus is NOT verification). Part 5 wires it into the ZOE pipeline to fix the doc-998 leak. |
| 1015 | Proactive Personal-Assistant / AI Chief-of-Staff Surfacing Patterns | GUIDE | Consolidate 2026 patterns from leading personal assistants (Gmail-driven, chief-of-staff builders), agent frameworks (Anthropic building-effective-agents), and memory systems (multi-signal retrieval). Add tier taxonomy to Candidate (critical/standard/signal), implement memory decay + entity-aware recall, build commitment scanner for zero-buffer detection, re-frame escalation by round, add silence-rate canary to watcher, wire reaction-based threshold tuning. Eight concrete code changes mapped to bot/src/zoe/ paths. |
| 1019 | Handoff-to-Bonfire proactive surfacing gap | DESIGN-PROPOSAL | Traces why a /handoff bundle pushed to Bonfire (the new ZOE-default receiver) is never proactively surfaced: doc 796's reasoning-tick gate only reads threads.ts Layer-A rows, and external Bonfire writes (via remember()) never create one. Proposes an openThreadFromExternal() ingress so /handoff opens real threads, not just episodes. |
| 1020 | Agent Benchmarks - How the ZAO Stack Does | COMPARISON | Surveys the 2026 agent-benchmark landscape (SWE-bench Verified/Pro, tau2-bench, GAIA, Terminal-Bench, OSWorld) and maps each to the ZAO stack: the Hermes fix-PR pipeline is SWE-bench-shaped (est 60-70%), the ZOE concierge is tau2/GAIA-shaped (est 75-85%), both untested. Verdict: do NOT chase public leaderboards; the real metric is merge-and-green rate on real ZAO work. Recommends a custom internal fix-PR benchmark (20 tasks) as the eval to ship. |
| 1021 | ZOE as Bot-Factory: One Engine, N ICM-Box Brains | DESIGN | The clean way back to a multi-bot fleet without the 10-bot sprawl. ZOE returns to its real job (conductor + lab + factory), and each domain bot is the SAME engine wearing a different ICM box as its brain (new bot = new ICM box + config, zero new code). One process, many masks. Three layers (bot tree / Respect-weighted contribution / consensus council); MVP = ZOE mints bot #1 (ZAO Devz) from an ICM box. The 'no new bots without a doc' gate. |
| 1057 | Agentic Swarms Orchestration Guide | GUIDE | Research-backed playbook on multi-agent swarm patterns grounded in ZAO's existing infrastructure (rule 7/20/8). Covers 6 production patterns (orchestrator-worker, fan-out/fan-in, pipeline, debate, handoff, adaptive), top-3 adoptions (fan-out code review, orchestrator brief schema, debate for security), cost model (15x token overhead justified only for high-value decisions), decision tree. All patterns cited to Anthropic, Beam.ai, SudoAll, OpenAI, CrewAI, LangGraph sources. |
| 1059 | Agent Money Autonomy: Safe Capped Spend for ZOL | GUIDE | x402 protocol, agent wallet standards (Coinbase AgentKit, Privy), six guardrails pattern, safe-spend architecture (payee allowlist, daily cap $10, per-tx limit $5, approval threshold $25+), concrete ZOL design, top-3 first moves, risk assessment, integration checklist. Ready for 3-4 week implementation. |
| 1085 | ZOL DreamLoops Persistent-Agent Graft | DECISION | Portable durable-loop framework for ZOL (@zolbot). 105 tests pass. 8 phases (audit -> vendor -> capsules -> state adapter -> handlers/loops -> daily operation -> evidence gating -> delivery). DreamLoops: Capsules (declarative bundles) + bounded loops + 3-factor authority model. ZOL gains persistent memory across restarts + daily routines + self-improvement without losing Farcaster signer safety or zero-spend model. Security: signer never in handler, posts approval-gated, dry-run by default, kill switch = unset flag. Recommendation: PILOT pattern for new agents (not ZOE mid-flight); ZOE v2 can adopt Capsules wholesale. |
| 1086 | DreamLoops Capabilities, Critical Unlocks & Cross-Ecosystem Application | STRATEGY | Comprehensive strategy report on Brandon Ducar's DreamLoops framework for portable persistent agents. New capabilities: persistent memory, daily routines, self-improvement, budget awareness, portable deployment, explicit approval gates. Cross-ecosystem application verdict: ship ZOL after Pi dry-run, pilot one new agent (grant-deadline-watcher or podcast-scout), defer ZOE refactor to v2. Six concrete new agent ideas. Honest risks + recommendation. |
| 1111 | Eight Specialized AI Model Architectures for The ZAO Stack | GUIDE | Map 8 specialized model families (LLM, LCM, LAM, MoE, VLM, SLM, MLM, SAM) to ZAO stack layers. Current: LLM backbone (Claude in ZOE). Leverage candidates: LAM for action planning, MoE for expert routing (ZOL intents), SLM for Pi classify (save 50-70% latency), MLM for Bonfire dense retrieval. VLM for meeting frames (low priority). Includes architecture breakdown + next actions tied to concrete ZAO decisions. |
| 1114 | Cua Computer-Use Agent Infrastructure: Evaluation for ZAO | STANDALONE | Y Combinator X25 OSS infrastructure for building agents that control full desktops (macOS/Windows/Linux/Android) across local and cloud. 19.7k stars, MIT, MCP-ready. Phased adoption recommendation: PoC wire-in to ZOE (week 1), pilot on ZABAL Games logistics (30-50% base accuracy ceiling), scale only if >70% success. Comparison vs Claude-in-Chrome/Playwright: adds native-app + background execution, higher ops cost. |
| 1067 | 1067 - Milk Road PRO Personal-Use MCP for ZOE | DOC | Structure Zaal's Milk Road reconnaissance into a personal-use MCP spec grounded in ToS boundaries and ZOE integration. |
| 1074 | Agent Leverage to Reduce Founder Subsidy | DOC | Map concrete NEW autonomous loops ZOE/ZOL/the fleet can run without human input, prioritized by leverage (time saved), with explicit guardrails and cost caps per the agent-loops.md rules. Identify what work safely become |
| 1079 | 1079 - Venus (Artizen) - Integrations to Adopt for ZOE | DOC | Evaluate Venus (Artizen's AI creator-fund copilot) for integration into ZOE, the ZAO orchestrator. Map Venus's capabilities and integrations, then recommend which ones ZOE should adopt and where they would hook into bot/ |
| 1080 | 1080 - AWS Strands Agents: Framework Audit & Borrow Patterns for ZOE | DOC | Evaluate AWS Strands Agents SDK against ZOE's hand-rolled agent orchestrator. Decide: adopt the framework, borrow specific patterns, or skip. Recommend concrete patterns ZOE should adopt incrementally without a rewrite. |
| 1081 | 1081 - ZOE Assistant Build-Out Roadmap: Capabilities + Gaps + Phased Plan | DOC | Define the prioritized capability roadmap for ZOE (Zaal's personal concierge / orchestrator). Ground in ZOE's real code, synthesize recommendations from docs 1074/1080/1067/1078/1079 + 2026 best-practices research, and d |
| 1091 | Expanded DreamLoops Capsule + Loop Catalog for ZAO Apps & Agents | DOC | ZOL's DreamLoops graft (doc 1085) demonstrated a portable, auditable pattern for bounded agents. This catalog proposes 13 new capabilities (5 Capsules, 8 Loops) across six ZAO surfaces: |
| 1102 | Memvid: MP4-as-Memory Claims vs. Reality + ZAO Fit Assessment | DOC | Memvid: 85.65% (overall LoCoMo) |
| 798 | ZABAL Bonfire: graph data-quality audit | DOC | The ingest + recall surface that ZAOOS actually controls: |
| 799 | DeepMeeting agent / shard architecture | DOC | A dedicated DeepMeeting agent, separate from the main @zabal_bonfire_bot: |
| 800 | Cowork Bot Control Plane | DOC | Turn the read-only thezao.xyz/bots status board (shipped 2026-06-07: heartbeats + |
| 816 | Cowork Control Plane + Project / Todo / GitHub Audit | DOC | One-pass audit of the bot control plane just shipped (doc 800 Phases 1-4 + fleet board), plus the live state of the cowork task tracker, GitHub across both repos, and what is outstanding. |
| 825 | ZAOcowork: whole-system architecture + how it connects | DOC | One map of the entire ZAOcowork (cowork-zaodevz) system - the web app, the database, both API surfaces, the Telegram agent, the bot control plane, the GitHub integration, and the three machines they run on - and how ever |
| 829 | Anthropic's Agent Skills Talk (Barry + Mahesh) - Transcribed | DOC | Transcribe + synthesize the Anthropic "we stopped building agents and started building skills" talk Zaal forwarded (via Kirill, 5.3M views). Full transcript: transcript.txt (16-min talk, locally whisper |
| 830 | AI Coding-Agent Discourse (June 2026 Inbox Cluster) | DOC | Synthesize the cross-cutting signal across 6 AI-coding items Zaal forwarded to the ZOE inbox, and map it to where ZAO's agent stack already sits. |
| 832 | Past-Inbox Re-Drain (84 social items, keyless) | DOC | The ZOE inbox had 84+ already-processed social items (X, Reddit, Farcaster) indexed BEFORE today's keyless fetch trio existed - many off blocked or thin fetches. Re-fetch all of them with the working scripts and synthesi |
| 836 | X Account Mining: The Agent-Patterns the Inbox Authors Are Writing | DOC | Zaal asked to mine the X accounts from the inbox for more articles like the ones he saved. X gated guest-token timelines in 2026 (can't bulk-scrape feeds keyless), so this used semantic search on the high-signal authors |
| 837 | X Account Mining Round 2 (10 authors, 40 findings) | DOC | Continue the doc-836 mining across the remaining high-signal inbox authors. Keyless semantic-search method (X timelines stay walled). 13-agent workflow, ~875k tokens. Six clusters - the field is converging hard, and seve |
| 869 | Doc 869 - ZAO Bot Fleet Audit (June 2026) | DOC | Companion to doc 601 (agent-stack cleanup decision) and the bot/REGISTRY.md |
| 909 | ZAO Agent-Stack Gaps + Hardening Roadmap | DOC | Honest gap analysis of the ZAO agent fleet vs 2026 best practice, ranked, with concrete fixes scoped to the stack (Next.js/Supabase/VPS/Pi/Bonfire/Telegram). ~65% production-ready: strong fundamentals, three blind spots. |
| 911 | Bot-per-Codebase + Ecosystem Monitor (the architecture) | DOC | Turn the standing vision ("ZOE monitors and reports on the whole codebase/ecosystem; eventually every codebase has its own bot") into a concrete, phased architecture - grounded in what already runs. |
| 913 | Swarm Protocol: does it make sense for ZABAL Gamez? | DOC | Decide whether Swarm Protocol (swarmprotocol.gitbook.io) should be adopted, integrated, or mentioned for ZABAL Gamez - grounded in a full read of the ZAO research library. |
| 918 | 918 - ZAO agent fleet audit: intended vs live, gaps, fixes | DOC | Map every agent in the ZAO fleet, compare intended (docs) vs live (VPS), and tag every needed fix SAFE vs RISKY. |
| 925 | ZOL Free Cast Posting via Ed25519 Signer - Build Guide | DOC | Farcaster 2026 uses a two-step custody model to post casts: |
| 927 | Next-Generation Autonomous-Loop Architecture | DOC | Replace the current single-threaded, time-based /loop with a server-side, event-driven, multi-track orchestrator that keeps the ZOE brain always running + mirrors Zaal's observed preference for ZOE to be the primary di |
| 928 | Agent-loop best practices (learned online 2026-06-30) | DOC | Concrete, behavior-changing practices for autonomous coding-agent loops (self-paced /loop building + deploying to the ZAO bot fleet). Distilled into the operating rule at .claude/rules/agent-loops.md. |
| 931 | H2-2026 ZOE Autonomous Media Control for All ZAO Brands | DOC | ZOE, currently a personal concierge for Zaal, is nearly ready to become the media orchestrator for the entire ZAO brand family. The architecture is 80% built: the scheduler (7 pings/day), 4-category post slate, approval |
| 985 | Claude's "global workspace" (J-space) - what it is + why it matters for ZAO's agents | DOC | Anthropic published (2026-07-06) evidence of an emergent "global workspace" inside Claude - the J-space. This doc explains what it actually is (grounded in the primary paper) and draws the one line that matters for ZAO: |
| 989 | The ZOE wheel-and-spoke: ZOE at the center, the tracker as the hub | DOC | One integration picture for Zaal's whole assistant stack. The cowork tracker (thezao.xyz) is the hub-of-record; ZOE is the router at the center; every surface, agent, terminal, and data source is a spoke that |
| 992 | Live clipper agent for ZAO streams (creator ops as agent workflows) | DOC | techfrenAJ shipped a live clipper agent for his stream and framed the real insight as "creator ops are becoming agent workflows." Decide whether ZAO should build one, and how it plugs into what ZAO already has (Livepeer/ |
| 994 | Loop engineering: the 4-loop taxonomy + Karpathy method, mapped to ZAO | DOC | Two mid-2026 essays ("loop engineering" hit peak hype in June-July 2026) define the vocabulary for how autonomous agents actually run. Pin the taxonomy down and map ZAO's real loops (ZOE, /loop, the fix-PR pipeline, auto |
| 1135 | Discord Agent Capabilities (2026) + ZOE Integration Design | STANDARD-DEEP | ZOE's dormant Discord client (merged, DISCORD_BOT_TOKEN unset on VPS) is production-ready baseline: responsive DMs + @mentions using existing concierge brain, message chunking, typing indicators. Map 8 capabilities: slash commands, Components V2 (buttons/modals), linked roles (Respect-holder verification), Activities (Mini Apps, embed cowork board), webhooks (status mirroring), forum topics, voice, context menus. Competitive vs Telegram: Discord's Activities + linked roles are unique for identity-gated community ops. Staged plan: Stage 0 (enable existing client, 5-min runbook), Stage 1 (webhook status feed + community zao-ask, 4-5h), Stage 2 (linked-role Respect gating + Activities board/cockpit, 8-10h). Killer unlock: Discord becomes operating surface for 188-member The ZAO community. |
| 1134 | Telegram Bot API HIGH Capabilities (2026) + ZAO Fleet Upgrades | STANDARD-DEEP | Bot API 10.2 (July 2026) maps 10 new capabilities: Mini Apps (in-Telegram board), Ephemeral Messages, Rich Messages, Communities. ZOE fleet (grammy 1.29.0) uses basic buttons; gaps: no Mini Apps (cowork board embedded), no ephemeral whispers, no reactions API, no inline mode search. Top 5 upgrades: [1] Mini Apps cowork board (highest impact, medium effort), [2] Ephemeral Messages (high impact, low effort), [3] inline mode search (medium), [4] reactions API (medium impact, low), [5] forum topics auto-routing (medium). Implementation phased: weeks 1-2 quick wins, weeks 3-5 core, weeks 6-8 fleet org. grammY compatible 1.29+; no breaking changes. |
| 1176 | Loop Memory: Compact Protocol Audit + Recall Design | STANDALONE | Audit of how the tmux loops lose information at compaction and how the compact protocol (STATE block + Bonfire episodes) + recall should work. (Overlaps doc 1170; a parallel take on the same loop-memory problem.) |
| 1177 | ZOE Music-Ops Agent Design: Artist-Centric Data Layer | STANDALONE | Design for a ZOE music-ops agent using Recoupable's stealable pattern (artist-centric data-transformation behind MCP + approval queue). Builds the follow-up boarded from the doc 1133 Recoupable review. |
| 1178 | Doc 1178: brandonducar repos zol integration scan | DOC | Scan of all 11 BrandonDucar public repos for ZOL/swarm integration points; top bet toolgym as tool-qualification gateway. |
| 1181 | Doc 1181: elizaos 2026 reresearch | DOC | ElizaOS 2026 re-research; verdict MONITOR + BORROW-PATTERNS, not framework adoption (autonomy-first conflicts with ZAO approval-gated model). |
| 1182 | Doc 1182: zao agent registry | DOC | Canonical agent registry + reusable agent-doc standard + machine-readable registry.yaml; live agents, build loops, decommissioned, drift targets. |
| 1185 | Doc 1185: eight specialized ai model types | DOC | The 8 specialized AI model types (LLM/LCM/LAM/MoE/VLM/SLM/MLM/SAM); top-3 for ZAO: MoE routing now, SLM edge, VLM Q3. |
| 1187 | ZAI - Discord Live Voice-Capture + Q&A Bot | STANDARD-DEEP | ZAI is the ZAO community assistant - warm, approachable, plain-spoken. First capability: Discord live voice-capture with real-time transcription via Groq Whisper + interactive Q&A via Claude 3.5 Sonnet. Slash commands: /join, /ask, /summary, /stop. Reuses bot/src/zoe/transcribe.ts pattern. Transcripts saved to ~/.zao/private/ per PII hygiene. Setup: Discord Developer Portal bot token, env vars (DISCORD_CAPTURE_TOKEN, GROQ_API_KEY, ANTHROPIC_API_KEY), systemd unit template included. Boot-verified (tsc clean, config module imports OK). Ready for live test once token configured. |
| 1212 | Personal-Use Session-MCP Pattern | CANONICAL | Reusable template for any session-gated personal-use data source: browser cookie -> ~/.zao/private//reengage skill that detects quiet ZAO cowork leads and surfaces a warm re-entry message via BCZ or ZOE. |
| 1247 | ZOE Web Interface: Current State + Gap Analysis | STANDALONE | Maps what is already built in the BotsBoard (ask/activity/heartbeat) vs the remaining gaps (ask gated to admins only, no streaming indicator). PR scope for db708278. |
| 1272 | The ZAO Agent Stack (July 2026) | DOC | Canonical integrated view of all 4 active ZAO agents: ZOE (@zaoclaw_bot, Telegram concierge/elder, VPS 31.97.148.88), ZOL (@zolbot FID 3338501, Farcaster music scout, Pi-hosted), Hermes (@zoe_hermes_bot, autonomous coder-critic-PR pipeline), ZAO Devz (@zaodevz_bot, group dispatch + hourly learning cron). Voice constitution (all lowercase, no em dashes, no commas) + elder/lineage model (ZOE is parent; child bots inherit voice verbatim). First multi-agent fleet canonical doc. GEO + grant citation asset. |
| 1317 | ZOE Telegram Mini App: Cowork Board in the Thumb | DESIGN | /board command → Telegram Mini App showing open tasks. Phase 1: grammY InlineKeyboard with web_app button + new thezao.xyz/board/mini route + /api/tg/auth initData HMAC-SHA256 verification endpoint. Env: BOARD_MINI_URL (bot) + TELEGRAM_BOT_TOKEN (cowork). Two PRs: bot-side (adds button) + cowork-side (adds page + auth). Phase 2: /cockpit Mini App. Phase 3: task creation. Board task 950a04f2. Related: 1134, 1272, 1247. |
| 1319 | DreamLoops x ZAOcowork: Capsule Dispatch + Cost Caps | DESIGN | Grafts DreamLoops-style stateful capsules onto the ZAOcowork Next.js board. 3 capsules: (1) Task-Auto-Summary (claude-haiku, 500 tokens, writes ai_summary to Supabase), (2) Related-Docs Suggester (keyword grep ZAOOS READMEs, 1000 tokens, writes ai_related_docs JSONB), (3) Staleness Detector (pure SQL, no LLM, pings ZOE Telegram). Cost cap ~$0.015/day. 3 new Supabase columns, 5-PR plan, no new infra. Board task 23503d58. Related: 1085, 1086, 1091, 1115. |
| 1453 | !summary Livestream Command Spec (Jul 2026) | DESIGN | Full spec for !summary Telegram command: Zaal types !summary mid-stream, ZOE pulls last 50-message chat buffer + optional zaoscribe transcript, Claude haiku summarizes to {title, one_liner, key_moments, next_steps, farcaster_thread}, replies to Telegram + pushes Bonfire episode. Phase 2: !post-summary confirmation fires ZOL Farcaster thread. 4-PR plan. Cost ~$0.001-0.003/invocation. Board task 60e2af75. |
| 1600 | ZAO AI Assistant: Bartosz-Style API + Bonfire-Backed Context | IMPLEMENTATION-SPEC | Public-facing "chat with ZAO" assistant for zaoos.com. Uses bartosz0718 SmartVibe patterns (doc 1150): async job queue, idempotency keys, consistent error shapes, rate limiting. Context layer: Bonfire vector search (doc 665/680); falls back to static-context.json until Bonfire read-path opens. Phase 1: static context + sync API + chat widget (3-4h, zero dependencies). Phase 2: async queue + rate limiting. Phase 3: live Bonfire context. Supabase assistant_queries table for audit + dedup. R8 bounty candidate (20-50k ZABAL). Board task: "ZAO AI assistant - bartosz-style, Bonfire-backed." |
| 1603 | Farcaster + X Ingest Pipeline Spec | IMPLEMENTATION-SPEC | Spec for ingesting Farcaster channel casts + X posts into Bonfire. Doc 570 Stage 3 deadline 2026-07-30. Farcaster: ZOL new DreamLoop (farcaster-ingest) using readV2 — top-5 scored casts/channel/day + mention hook; $0 cost; 3-4h. X: x-ingest.ts cron using X API v2 free bearer token (500K reads/mo, free); 2-3h after Zaal gets token at developer.x.com (15 min, $0). Shared SQLite dedup log at ~/.zao/zoe/bonfire-pushed.sqlite. Episode format: farcaster:cast:<hash> and x:tweet:<id>. Unlocks ZAO AI assistant (doc 1600) with live social context. Board task: "Farcaster + X ingest pipeline (doc 570 multi-corpus plan)." |
| 1610 | Zolbot → ZABAL Telegram Channel: Implementation Spec | IMPLEMENTATION-SPEC | Companion to doc 1607 (ZOL /zabal Farcaster). Same content (battle results + weekly recap + ZABAL Games drops), Telegram delivery via ZOE bot. Gate: Zaal creates ZABAL TG channel, adds @zaoclaw_bot as admin, provides ZABAL_TG_CHAT_ID. Implementation: 1 PR — new telegram-zabal.ts handler + work-loop task types + scheduler cron (2-3h). Pattern from doc 1544 (ZOE Telegram ops guide). No new packages. Unlocks dedicated ZABAL Telegram presence as ZAOstock CTA channel. Board task: "[build] Zolbot posts into ZABAL Telegram channel." |
| 1624 | ZAO Agent Fleet Reference: ZOE + ZOL + Hurricane | SYSTEM-REFERENCE | ACTIVE — Canonical "who does what" reference for ZAO's three AI agents as of Jul 2026. ZOE (community intelligence): WW API + Supabase + Neynar + Twitter + Telegram; jobs: EOD report, battle result posts, grant alerts, event automations, ZABAL tracking, newsletter send, artist DM onboarding; auto-post vs draft-and-send vs GATED approval modes. ZOL (Farcaster agent): Neynar webhooks; jobs: replies to WaveWarZ mentions, /wavewarz channel warmup, /zabal auto-posts (DreamLoops); ZOL vs ZOE split: ZOE = scheduled/data-driven casts, ZOL = conversational/community-reactive. Hurricane (build ops): GitHub PRs + Supabase migrations + Vercel deploys; Hurricane build checklist Aug 15 → Nov 20; blast radius rules (no table drops, no prod-data deletion, no X/Farcaster posting). Agent coordination flow: ZOR vote → Zaal creates battle → WW event → ZOE posts live + ZOL community replies → settlement → ZOE result post → Hurricane Supabase update. Future fleet: ZAO Oracle (doc 347) + ZAO Nexus. Related: 1615 (ZOE architecture), 1607 (ZOL DreamLoops), 1604 (artist directory — Hurricane builds), 1619 (Fractal — ZOE session automation). |
| 1657 | Farcaster + Paragraph Historical Backfill: Bonfire Corpus Completion | IMPLEMENTATION-SPEC | One-time script to pull all historical ZAO Farcaster casts (Neynar paginated feed, /wavewarz + /zabal + /zao) and all ZABAL Updates newsletter issues (Paragraph.xyz RSS) into Bonfire. Board task #17. Uses existing NEYNAR_API_KEY + BONFIRE_API_KEY. Quality filter: engagement ≥5 OR ZAO keyword OR ZAO FID. ~2,000 episodes across 3 channels + newsletter. SQLite dedup guard at ~/.zao/zoe/bonfire-pushed.sqlite prevents re-push. Run time ~25-30 min. After this runs: doc 1603 ongoing pipeline handles new casts. |
| 2027 | Executive Cortex v1 MVP: Strategic Advisory Layer | STANDALONE | Cortex THINKS (analyzes priorities, dependencies, blockers) and RECOMMENDS (immutable DecisionReceipts). Never executes, never modifies Spine/Grid data. Answers 5 questions: most_important_now, top_5_priorities, what_is_blocking, what_can_be_delayed, what_can_parallelize. Pure scoring functions (priority engine), DAG analysis, context aggregation, decision orchestration. Fully typed, comprehensive tests. Gated migration for goals/edges/receipts tables. v1 scoped to advice; future: learning loop, budgeting, simulation. |
| 90 | AI-Run Community: Self-Improving Agent OS for ZAO |
| 2030 | DreamNet Public Core is the receipt contract our organism should speak | STANDALONE | Assess Brandon's DreamNet repo constellation (Whale League + Public Core contracts) grounded in the actual code, and decide the single highest-leverage collab move for ZAO's organism. |
| 2040 | Suchbot Evaluation for ZOE | STANDALONE | Research doc 2040. |
| 2062 | Eyes organ + the ZAO organism roadmap | STANDALONE | Evolve ZAO from a set of services into a modular digital organism where every organ has a single responsibility and clean interfaces, cooperating through the Spine. This doc designs the Eyes organ (shipped as src/lib/eyes/) and roadmaps the remaining organs. |
| 2064 | Organism runtime, Control Plane, Memory, and governance | STANDALONE | The operational substrate that lets many organs run as one long-lived organism: a persistent runtime, a Control Plane (operational nervous system), layered Memory, the Edge/Core/Data/Observability architecture, and repository governance so the ecosystem can grow without losing modularity. |
| 2068 | AI Graph/Agent Frameworks: What ZAO Should Borrow (Not Adopt) | STANDALONE | Map the 10 "AI Graph Engineer" frameworks from the source tweet onto ZAO's own agent stack (ZOE, the organism, Bonfire) and decide what to borrow - given ZAO already killed the heavy frameworks and runs clone-no-deps. |
| 2088 | ZAI Discord Voice Auto-Capture (the copy-not-build path) | STANDALONE | Kill the manual terminal step in meeting capture for Discord calls. A ZAO-owned bot joins the voice channel, records each speaker separately, and auto-runs the existing transcribe -> extract -> write pipeline into ZAOOS + the cowork tracker. Zero terminal input. |
| 2089 | Block's Buzz: humans + AI agents as peers on a Nostr relay | STANDALONE | Assess Block Inc's open-source "Buzz" workspace and decide whether ZAO should adopt it, borrow from it, or just monitor it - specifically for the multi-agent + human coordination problem ZOE already has. |
| 2091 | ZOE review pipeline (design spec) | STANDALONE | Spec the autonomous ZOE loop that reviews Iman's board submissions (0/10 + edit/followup/flair flags) and routes ZOE -> Jose -> ZOE -> Zaal for quick polish - a design for approval, not a build. |
| 2103 | Grounding Beats Guessing - the verify-not-trust discipline | STANDALONE | Codify why an AI assistant's real value is verification against source truth (not fluent output), with the ZAO session evidence + the external literature, and fold it into the existing anti-fabrication rules. |
| 2104 | Fleet / multi-terminal coordination - deep audit + first fixes | STANDALONE | Ground the real state of the fleet/multi-terminal layer, find why the clipboard paste-bus persists, and ship the first fixes toward killing it. All findings verified against live state (branch refs, session state, live DB), not assumed. |
| 2106 | ZOL: ICM-grounded posting + governed X pilot | STANDALONE | Fix ZOL's bad posts (recycled WaveWarZ -> grounded, rotating, current) by wiring it to the ICM boxes it already has, and give Zaal a Farcaster-first setup where X stays alive without paid automation he doesn't need. |
| 2109 | Buzz (Block/Dorsey) - the OSS version of what ZAO is hand-building | STANDALONE | Evaluate Buzz - Block's self-hostable human+AI-teammate workspace - against ZAO's home-grown coordination stack (cowork board + ZOE/ZOL/ZAI + tonight's zao-relay), and decide: adopt, build-on, or learn-from. |
| 2124 | Spore Interoperability & Federation v0.2 - the DreamNet plan of record | STANDALONE | Capture Brandon's full v0.2 federation spec as the plan of record, record the confirmed Phase 1 result (ZAO's hash is byte-identical to DreamNet's), and lay out the roadmap + the one blocker. |
| 2152 | The ZAO execution layer - architecture reference | STANDALONE | One map for the whole execution layer (federation boundary + Heart lease core + transactional outbox): how they compose into observe->lease->act-exactly-once, receipted + DreamNet-verifiable. Indexes docs 2138/2139/2145/2149. |
| 2149 | App-Heart migration plan: the two impls, their differences, the safe path | STANDALONE | The two live lease impls' exact behavior diffs (quarantine, fencing tokens, dead-instance reclaim), the one blocker, and 3 options. Rec: behavior-preserving shim now, adopt package semantics next. |
| 2145 | Transactional outbox - the durable idempotent side-effect protocol (DESIGN) | STANDALONE | The next-focus milestone: effect_intents + outbox tables, deterministic idempotency keys, fenced dispatcher, external reconciliation - crash-safe at-most-once for every outbound action. Design (migration ask-first); composes with Heart fleet + receipt emitter. |
| 2142 | Architect's Progress Report - overnight run 2026-07-29/30 | STANDALONE | The standing report: 9 merged PRs (Phase 3 conformance, Heart fleet extraction, truncation class, #51/#49/#48/#45, SEO), proofs, failure modes, next milestone = Heart live in prod + effect_intents. |
| 2140 | Board drift verify-report (board #48) - measured, not mass-closed | STANDALONE | The #48 cleanup done the anti-fabrication way: live SQL drift stats (333 active, 130 overdue, timestamps bulk-rewritten), evidence-verified close candidates, and the due-date amnesty proposal - closes proposed, not executed. |
| 2139 | Heart fleet extraction: packages/heart-fleet + canary + 5 safety properties PROVEN | STANDALONE | One lease implementation for the whole fleet: dependency-free package (fencing tokens, retry ceilings, receipts, metrics, guardIrreversible), flag-gated ZOE canary, 24 property tests green, idempotent side-effect protocol design. |
| 2138 | Spore Phase 3 CONFIRMED - bidirectional cross-runtime verification vs the public SDK | STANDALONE | Execute Phase 3 of the v0.2 federation spec against the now-public dreamnet-spore-sdk: 47/47 checks, both directions, live SDK execution; ZAO = first independently-operated conformant Spore node at the hash and receipt layers. |
| 2127 | Loop / Harness Engineering (Anthropic "systems that prompt themselves") - ZAO alignment audit | STANDALONE | Take the viral "you're not supposed to prompt Claude, you build a system that prompts itself" talk and answer the only question that matters for us: what does ZAO already do, and what are the 2-3 concrete tune-ups worth making. |
| 2131 | Loop vs Graph Engineering (Part 2) - ZAO already has both | STANDALONE | Take DevCompass's loop-vs-graph piece and answer the ZAO question: when is a loop enough, when does a graph earn its keep, and does ZAO already have the graph primitives (yes - the Workflow tool). |
| 2159 | Per-Brand Context Separation (spec) | SPEC | The memory-layer change that must land before the fleet ingest (ingestAllIdentities, PR #2751) can auto-run: give each brand its own inbox_context..jsonl via an optional namespace param defaulting to the shared path (backward-compatible). Teed up for SUPERVISED implementation (edits live ZOE memory.ts). Related: 2155, fleet.ts. |
| 2169 | Daily-Note Capture with Auto-Rollover (SPEC) | SPEC | Capture-friction fix (board records 3.4/day, Zaal ships ~11/day - recording gap, not productivity). ONE daily note/person/day; undone items auto-roll with a roll-count (honest replacement for the synthetic due dates that broke the daily); items auto-PROMOTE to real rows on @person-or-date inference. REUSES public.tasks (kind=daily_note + metadata.items), no new table. Needs Zaal approval to build (schema+cron = ask-first). |
| 2170 | ZAO Organism Diagnostic v1 | DIAGNOSTIC | Brandon 10-phase organism health assessment, grounded (2 census agents + live DB/code/VPS). One-line: the organism ACTS (150 PRs/wk, 19 loops, Spore-conformant) but does not RECORD that it acted (14 receipts total/1 loop, effect_intents=0, no claims table, memory 88% orphaned, 1 write/7d) - the afferent loop Execution->Receipt->Claim->Memory never closes. Scores + top-5 root causes + repair plan R0-R4. Highest-leverage fix: close Execution->Receipt->Memory. Related: 2169, 2093, brandon organism/heart. |
| 2171 | ZAO Organism Re-Audit v1 | REAUDIT | Skeptical re-audit of doc 2170 + this session fixes. All 5 root causes SURVIVED adversarial scrutiny (1 qualified); R0+R1 verified REAL not cosmetic. Two honesty corrections to 2170 numbers (board is 52%-of-RANKED-set synthetic not 52% overall=~11%; PR velocity UP +54% not down). New: live community.config.ts Magnetiq/SongJam leak on /ecosystem (FIXED #2776); security clean; ~13 stale public repos; 5 system-level gaps. Related: 2170, 2169. |
| 2174 | Bidirectional Relay: Feedback Loops into Claude Code | DESIGN | Zaal wants to type feedback back to a running Claude Code session from Discord + Telegram + the clipboard (not just receive the "check"). Design: ONE relay substrate (the existing zao-relay hub + auto-pull) + N thin bidirectional surface adapters (TG topic via ZOE, Discord bot, clipboard reply-box). The terminal reads its lane each tick = the feedback loop. Phasing: TG first (lowest effort), clipboard, Discord. Sender-allowlisted; gated actions stay gated. Related: zao-ask-check, ZAI, give-ZOE-a-body, agent-loops rule 36. |
| 2175 | Sovereign-Agent Deliverables + Architect Report | DESIGN | Brandon 5-stage sovereign-agent proposal - the Required Deliverables (current-state map, threat model, staged rollout, acceptance criteria) + Architect Report, DESIGN-ONLY, nothing activated. Grounded audit: ~25% prod / 50% flags-off / 25% no-code. Stage 0 (readiness gate) NOT passed (Heart flags OFF, memory 88% orphaned, no economic pause). Highest-leverage = CLOSE STAGE 0. Economic/on-chain = design-not-execute, human-gated. Related: 2170, 2171, brandon organism/dreamnet. |
| 2176 | DreamNet Federation Canary: Phase 0 Reality Board | AUDIT | Brandon Iteration-1 canary. Phase 0 grounded audit (2 read-only agents). SDK bb5d79a VERIFIED real (16 tests, all crypto props: RFC8785/Ed25519/audience/nonce/revocation/fail-closed). ZAO side ~40-50%: receipts+terminal LIVE, Spore Phase1-3 deployed, Heart flag-OFF; MISSING: Ed25519 signing, isolated signer, Gateway, ProofDrop-emit, Claim+Verification Factory, candidate identity. CRITICAL: ZAO Spore INCOMPATIBLE (pre-trust vs bb5d79a trust-enabled). Highest-leverage next = ZAO Spore trust upgrade. Design/audit-only, nothing built/gated. DreamNet-standard report + 4 lenses. Related: 2170/2171/2175. |
| 2178 | Agent Harness: One Orchestrator, Many Workers | STANDALONE | Decide how ZOE taps every device, every chat, and every brand from one place without split-brain - and the concrete build sequence to get there. Grounded in a 3-scout audit of the live system (2026-08-02). |
| 2182 | Per-Brand Terminals: Dispatch + Boards (Divide & Conquer) | STANDALONE | Make the orchestrator-worker harness (doc 2178) operational for real work: each brand gets a worker terminal that completes its tasks PR-only, everything rolls up to one board Zaal watches, and only decisions route to him. This doc ships the SEND half + the board, and specs the one gated RECEIVE-half deploy. |
| 2184 | DreamNet Tenant-Organism Template v1 - ZAO Stage 0 (Architect's Report) | STANDALONE | Prove ZAO can be DreamNet's first sovereign external tenant - using selected DreamNet protocols through a governed boundary, without surrendering identity, memory, authority, or survival. Reference implementation + read-only canary, flag-gated OFF, nothing deployed. |
| 2188 | Cheap fleet, premium escalation: how to actually use the Max plan for building | STANDALONE | Answer "why can't I use my Max plan when something needs making?" and design the |
| 2191 | ZOE Agent-Spawning + Validation | STANDALONE | Turn ZOE from an agent that calls tools into an orchestrator that spawns purpose-built agents (temporary, permanent, and tool-agents), with a "prove the output is right" gate on every one. Grounded in ZOE's real code + 2026 framework/eval research. Companion to two living artifacts (linked below) and the first implementation (PR #2823). |
| 2192 | AI For Humans: the computer-use shift + Karpathy's long-horizon test | STANDALONE | Synthesize the 2026-08-04 AI For Humans newsletter and pull the two threads that matter for ZAO - (1) computer-use agents crossed from "sucks" to "works," validating the self-driving desktop direction; (2) Karpathy's Opus 5 experiment shows LLMs now sustain long-horizon builds, which is exactly the agent-spawning bet. |
| 2198 | Agent orchestration in production: harness vs loop, and why the gate is everything | STANDALONE | What teams ACTUALLY run for autonomous agents (not hype) - and a check that ZOE's own loop architecture matches what the field converged on. It does; this doc names the one gap. |
| 2199 | What to ADD to ZOE: failure-memory, skill self-evolution, and the Reflexion write-back | STANDALONE | Turn the overnight agent research into a concrete ZOE upgrade list. Grounded in ZOE's REAL modules (bot/src/zoe/) so every "add" is a delta, never a duplicate of what ZOE already has. |
| 2200 | What to ADD to ZOE: step-level tracing + a verify-replan planning loop | STANDALONE | doc 2198 found winning teams "invested in observability, evaluation harnesses, and human-review, regardless of framework." This checks ZOE's real observability + planning against the field and names the two adds. Continues the [[feedback_research_to_agent_upgrade_lens]]. |
| 2201 | Bonfire IS ZOE's memory map: what's actually there, the real gap, and making ZOE understand ZAO + the board | STANDALONE | Answer "what happened to Bonfire push/pull", reconcile it with the doc 2199 "add a failure memory" rec, and chart how ZOE actually understands ZAO + surfaces the live team todos. |
| 2204 | Cross-family verification: what 99darwin/orchestrator (and the wider 2026 pattern) adds to ZOE | STANDALONE | nickysap open-sourced his orchestrator skill (github.com/99darwin/orchestrator, MIT, pushed 2026-08-06). Read it against ZOE's real orchestration code and the wider "cross-model review" literature, and name the ADDs - grounded so we do not re-recommend what ZOE already has. |