elizaOS · madjin · Feb 10, 2026 · Feb 10, 2026
diff --git a/.github/workflows/extract_daily_facts.yml b/.github/workflows/extract_daily_facts.yml
@@ -73,16 +73,59 @@ jobs:
             echo "Input file $INPUT_FILE not found, skipping fact briefing generation."
             exit 1
           fi
-      - name: Create permalink for JSON fact file
+      - name: Check extraction quality
+        id: quality_check
+        run: |
+          DAILY_FACT_JSON="the-council/facts/$(date +%Y-%m-%d).json"
+          if [ -f "$DAILY_FACT_JSON" ] && grep -q '"status": "success"' "$DAILY_FACT_JSON"; then
+            echo "quality=success" >> $GITHUB_OUTPUT
+            echo "Extraction succeeded on first attempt."
+          else
+            echo "quality=error" >> $GITHUB_OUTPUT
+            echo "::warning::Extraction produced error stub. Will retry..."
+          fi
+
+      - name: Retry extraction on failure
+        if: steps.quality_check.outputs.quality == 'error'
+        env:
+          OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
+        run: |
+          echo "Waiting 30s before retry (different HTTP connection)..."
+          sleep 30
+          INPUT_FILE="${{ steps.aggregate_step.outputs.aggregated_json_file }}"
+          OUTPUT_JSON_FILE="the-council/facts/$(date +%Y-%m-%d).json"
+          OUTPUT_MARKDOWN_FILE="hackmd/facts/$(date +%Y-%m-%d).md"
+
+          python scripts/etl/extract-facts.py -i "$INPUT_FILE" -o "$OUTPUT_JSON_FILE" -md "$OUTPUT_MARKDOWN_FILE"
+
+      - name: Create permalink for JSON fact file (quality-gated)
         run: |
           DAILY_FACT_JSON="the-council/facts/$(date +%Y-%m-%d).json"
           PERMALINK_FACT_JSON="the-council/facts/daily.json"
-          if [ -f "$DAILY_FACT_JSON" ]; then
+          if [ -f "$DAILY_FACT_JSON" ] && grep -q '"status": "success"' "$DAILY_FACT_JSON"; then
             cp "$DAILY_FACT_JSON" "$PERMALINK_FACT_JSON"
+            echo "Updated daily.json permalink."
+          else
+            echo "::warning::Extraction status is not 'success' — keeping previous daily.json to protect downstream workflows."
           fi
 
       - name: Commit updated files
         uses: stefanzweifel/git-auto-commit-action@v5
+
+      - name: Alert on data quality issue
+        if: always()
+        run: |
+          DAILY_FACT_JSON="the-council/facts/$(date +%Y-%m-%d).json"
+          if [ -f "$DAILY_FACT_JSON" ] && grep -q '"status": "error"' "$DAILY_FACT_JSON"; then
+            WEBHOOK_URL="${{ secrets.ALERT_WEBHOOK_URL }}"
+            if [ -n "$WEBHOOK_URL" ]; then
+              curl -s -H "Content-Type: application/json" -d "{
+                \"content\": \"⚠️ **Extract Daily Facts**: Extraction for $(date +%Y-%m-%d) produced an error stub after all retries. Manual intervention may be needed.\"
+              }" "$WEBHOOK_URL" || true
+            fi
+            echo "::warning::Facts extraction produced error stub for $(date +%Y-%m-%d)"
+          fi
+
       - name: Alert on failure
         if: failure()
         uses: ./.github/actions/alert-failure

diff --git a/.gitignore b/.gitignore
@@ -8,6 +8,9 @@ tmp
 .claude/
 .cursor/
 
+# Debug sidecar files (raw LLM responses on extraction failure)
+the-council/facts/.debug/
+
 # Temporary/development files
 council_survey_responses.csv
 facts-july-2025.md

diff --git a/hackmd/facts/2025-02-03.md b/hackmd/facts/2025-02-03.md
@@ -1,6 +1,62 @@
 # Fact Briefing: 2025-02-03
 
 ## Overall Summary
-Error: Failed to generate briefing due to LLM or parsing issues.
+The ElizaOS project is undergoing a comprehensive rebranding from AI16Z while simultaneously releasing v0.1.9, which has introduced specific dependency and installation challenges. Significant development focus has shifted toward automated AI news aggregation and the expansion of the plugin ecosystem for TON and MultiversX.
 
-No detailed categories provided.
+## Key Facts
+
+- Project branding is transitioning from AI16Z to ElizaOS, including the acquisition of the elizaOS Twitter handle.
+- ElizaOS version 0.1.9 was released with reported compatibility issues regarding Solana helpers and Node.js versions other than 23.3.0.
+- PR #3209 introduced the CREATE_POOL action for the MultiversX plugin to enable on-chain liquidity transactions.
+- A TON Plugin was added to the framework supporting NFT collection management, item creation, and metadata changes.
+- The elizas.com website is currently offline, with the team directing users to the GitHub repository for documentation.
+- PR #3146 upgraded OpenAI and Vercel AI packages to resolve errors specifically related to the o1 model series.
+- A news aggregation system is in development to automate ecosystem newsletters by analyzing Discord and X (Twitter) data.
+- External contributors added Google Vertex support to the framework via a new pull request.
+
+## Open Questions
+
+- Can the redis adapter be used in conjunction with postgres adapter?
+- Does folder2knowledge not working?
+- How do I get the current runtime?
+- Will transaction-related technologies from partnerships be shared with DegenAI/Can we use these technologies?
+- How do we plan on reconciling the investment DAO vision with the open source framework vision?
+- Is deepseek working in 1.9?
+- Why is $degenai going down everyday?
+
+## Categories
+
+### Twitter News Highlights
+- The next significant computing era will likely be defined by a new 'wrapper' that makes AI as accessible as the GUI made the PC. (Sentiment: neutral)
+- Explaining a problem to AI tools like Claude/ChatGPT can help crystallize thoughts even if the AI response is flawed. (Sentiment: positive)
+
+### GitHub Updates
+
+#### New Issues/PRs
+- [Issue #3212: Build errors when deploying on render.com](https://github.com/elizaos/eliza/issues/3212) by RectiFlex - Status: open - Significance: Blocks deployment for users on common PaaS providers.
+- [Pull_request #3211: TON Plugin: NFT collection, item creation, metadata change and transfer actions](https://github.com/elizaos/eliza/pull/3211) by mikirov - Status: merged - Significance: Significantly expands NFT capabilities on the TON network.
+- [Issue #3191: Runtime import error in NestJs applications](https://github.com/elizaos/eliza/issues/3191) by keyur555 - Status: open - Significance: Affects developers integrating ElizaOS into existing enterprise frameworks.
+
+#### Overall Focus
+- Concentrated effort on stabilizing the v0.1.9 release through high-volume bug fixes in specific plugins like plugin-0g, plugin-0x, and plugin-agentkit while standardizing linting via Biome.
+
+### Discord Updates
+- **#coders:** Developers are struggling with model providers other than OpenAI (Deepseek, Ollama) and memory consistency across different clients. Node v23.3.0 remains the enforced standard. (Key Participants: RoomTemp IQ, elizaos-bridge-odi, Mr. Stark)
+- **#3d-ai-tv:** Focus on 'Block Tank' simulation production. Technical hurdles include fixing data pipelines from SQLite to JSON and securing full-body animations for judge characters. (Key Participants: SM Sith Lord, boom, jin)
+- **#spartan_holders:** Discussion on DegenAI token performance (90%+ drop) and the lack of visible brand assets like LinkedIn logos. Questions raised regarding benefit share from partnerships. (Key Participants: DorianD, rhota, tigerguo)
+
+### User Feedback
+- Users find GitHub stars/forks to be an insufficient metric for measuring framework success and request a metrics dashboard tracking agent adoption. (Sentiment: mixed)
+- The 'Learn about elizaOS' link on the main framework site is broken, currently leading to a 404/dead end. (Sentiment: negative)
+
+### Strategic Insights
+
+#### Rebranding Friction
+The simultaneous move to rename the project while shipping a major technical update (0.1.9) is causing communication bottlenecks as official links and websites are out of sync.
+
+*Implications/Questions:*
+  - Should the team prioritize site restoration over new plugin releases?
+  - How will the $AI16Z ticker misalignment affect user trust during the name change?
+
+### Market Analysis
+- DegenAI token has experienced a 90% pullback, leading to community concerns about long-term sustainability vs. other AI tokens. (Relevance: DegenAI is the primary showcase of the trading agent framework; its performance is linked to the perceived utility of the codebase.)
diff --git a/hackmd/facts/2025-04-11.md b/hackmd/facts/2025-04-11.md
@@ -1,6 +1,66 @@
 # Fact Briefing: 2025-04-11
 
 ## Overall Summary
-Error: Failed to generate briefing due to LLM or parsing issues.
+The community has formally structured ElizaDAO into five working groups while technical focus shifted to stabilizing ElizaOS v2 migration and resolving persistent Discord and Twitter plugin vulnerabilities. Significant GitHub activity included merging circular reference fixes and voice model selection improvements to enhance framework reliability.
 
-No detailed categories provided.
+## Key Facts
+
+- ElizaDAO established five formal working groups: Community/Governance, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding.
+- PR #4266 was merged to implement a safeReplacer function resolving circular reference errors in JSON serialization.
+- PR #4262 replaced text inputs with dropdowns for voice model selection to improve the Agent Settings UI.
+- Users identified that adding 'types': ['node'] to tsconfig.json resolves the 'Dynamic require of child_process' and MongoDB adapter errors.
+- Twitter plugin autonomous posting was found to require setting TWITTER_ENABLE_POST_GENERATION=true in the .env for v2.
+- The SpartanV2 project added the contract address to its account profile and began exploring follower recovery methods.
+- A new deployment issue #4269 was reported regarding Discord bots failing to reply when hosted on Google Cloud Run via Docker.
+- Auto.fun product launch was confirmed as 'imminent' following a previous delay to April 14th.
+
+## Open Questions
+
+- How can I fix the issue where plugin-tee generates the same key regardless of parameters?
+- Is it true that Grayscale is investing in $ELIZA or is the ticker just wrong?
+- May I know why there is a timer in Eliza studio ai that page? Something happen after 4 days later?
+- Is mock-eliza not available in the starter of v1?
+- How to get Eliza OS v2 beta agent running with character card and vector database in Coolify or VPS?
+
+## Categories
+
+### Twitter News Highlights
+- Successful tech founders are noted to have confrontational personalities and a willingness to violate social rules. (Sentiment: neutral)
+- ENS domains are criticized as potential security 'honeypots' for wallet owners. (Sentiment: negative)
+
+### GitHub Updates
+
+#### New Issues/PRs
+- [Pull_request #4266: fix: cyclic error](https://github.com/elizaOS/eliza/pull/4266) by tcm390 - Status: merged - Significance: Resolves a critical serialization crash involving circular references.
+- [Pull_request #4247: feat: message api](https://github.com/elizaos/eliza/pull/4247) by tcm390 - Status: merged - Significance: Introduces a native message API for the platform.
+- [Issue #4269: Discord bot not replying on Google Cloud Run](https://github.com/elizaos/eliza/issues/4269) by jiggyjo11 - Status: open - Significance: Identifies a critical failure in Docker-based cloud deployments.
+
+#### Overall Focus
+- Development is centered on expanding ElizaOS API capabilities for world/room management and refining plugin infrastructure through registry integration.
+
+### Discord Updates
+- **#dao-organization:** Discussions focused on treasury independence and the creation of a DAO charter to balance autonomy with ElizaLabs alignment. (Key Participants: HoneyBadger, vincentpaul, yikesawjeez)
+- **#coders:** Technical troubleshooting regarding version 0.25.9 stability and fixing 'hapi__shot' build errors via TypeScript config changes. (Key Participants: notorious_d_e_v, wookosh, CSC35)
+- **#partners:** Debate over the lack of agent-centric discovery mechanisms in the current Model Context Protocol (MCP) ecosystem. (Key Participants: DorianD, hubert, jin)
+
+### User Feedback
+- Users expressed frustration regarding poor documentation and the lack of working examples for Windows/WSL environments. (Sentiment: negative)
+- Core contributors suggest using 'pnpm' exclusively over npm or bun to avoid recurrent dependency conflicts. (Sentiment: neutral)
+
+### Strategic Insights
+
+#### Decentralized Governance Maturation
+The community consensus shifted toward requiring a separate DAO treasury to ensure true independence from ElizaLabs.
+
+*Implications/Questions:*
+  - How will the DAO manage budget allocations across the five new working groups?
+
+#### MCP Registry Fragmentation
+Multiple registries are emerging for MCP servers, but they lack a unified agent-feedback loop, creating a bottleneck for autonomous agent evaluation.
+
+*Implications/Questions:*
+  - Should the DAO prioritize a whitelabel, agent-centric registry protocol?
+
+### Market Analysis
+- Meme coin trading on Pump.fun maintains a high meta for ‘ChatGPT image-based’ tokens. (Relevance: Drives demand for automated social media and trading agents built on ElizaOS.)
+- Launch of Grok 3 and Grok 3 Mini models with transparent reasoning traces. (Relevance: Provides high-performance, cost-effective LLM targets for ElizaOS integrations.)
diff --git a/hackmd/facts/2025-07-21.md b/hackmd/facts/2025-07-21.md
@@ -1,6 +1,58 @@
 # Fact Briefing: 2025-07-21
 
 ## Overall Summary
-Error: Failed to generate briefing due to LLM or parsing issues.
+The elizaOS ecosystem is undergoing a major core modernization with a shift to Bun's native EventTarget while simultaneously managing community concerns regarding AI16Z token governance and X account suspensions. Significant progress was made in standardizing service interfaces and improving the CLI's stability, though persistent issues with the Twitter plugin remain a primary technical debt.
 
-No detailed categories provided.
+## Key Facts
+
+- Core framework APIs were migrated from Node.js EventEmitter to Bun's native EventTarget to improve performance and compatibility.
+- A standardized service system with a getServicesByType() method was introduced to improve modularity and plugin dependency management.
+- Version 1.2.17 resolved a critical Twitter plugin database insertion error that was causing failures for several users.
+- The AI16Z token contract is not currently open source, and revoking mint authority is pending the development of voting infrastructure.
+- The official elizaOS X (Twitter) account remains suspended, but the team reported receiving an encouraging reply during restoration discussions.
+- The elizaOS framework now supports 53 projects that have moved from MVP to production status.
+- A 'Scenario Runner' feature for agent evaluation via YAML-defined scenarios was initiated with a suite of new GitHub issues.
+- The project migrated terminal interactions to @clack/prompts to provide consistent interactive styling across the CLI.
+
+## Open Questions
+
+- Are we still able to create agents whilst waiting for eli5? Or is the framework all on hold?
+
+## Categories
+
+### GitHub Updates
+
+#### New Issues/PRs
+- [Pull_request #5609: Migrate from EventEmitter to Bun native EventTarget API](https://github.com/elizaos/eliza/pull/5609) by wtfsayo - Status: merged - Significance: Major architectural shift for performance and Bun runtime compatibility.
+- [Issue #5499: Plugin-local-ai failing to load on Windows](https://github.com/elizaos/eliza/issues/5499) by SYMBaiEX - Status: closed - Significance: Representative of a broader effort to resolve Windows-specific platform bugs.
+- [Pull_request #5565: implement service types and standardized interfaces](https://github.com/elizaos/eliza/pull/5565) by wtfsayo - Status: merged - Significance: Resolves long-standing architectural proposal for modular services.
+
+#### Overall Focus
+- Development focused on strengthening project foundations through standardized service types, action chaining, and a complete UI/UX overhaul to match Figma designs.
+- The team implemented automated code quality analysis using Claude to identify dead code, security concerns, and missing test coverage.
+
+### Discord Updates
+- **#discussion:** Discussions centered on the suspension of X accounts, the lack of open-source token contracts, and the limitations of revoking mint authority without a voting system. (Key Participants: Kenk, DorianD, ZzzzHodl)
+- **💻-tech-support:** Technical collaboration focused on Ollama integration for plugin-knowledge and troubleshooting specific database insertion errors in the Twitter plugin. (Key Participants: starlord, sayonara, CJFT)
+
+### User Feedback
+- Users expressed concern over the centralized control of AI16Z tokens due to the unrevoked mint authority. (Sentiment: negative)
+- Community members suggested that product quality and GitHub activity are better metrics for project health than social media presence during the X account suspension. (Sentiment: positive)
+
+### Strategic Insights
+
+#### Platform Dependency Risks
+The ongoing suspension of X accounts and repeated rate-limit issues with the Twitter plugin highlight a critical vulnerability to platform-specific gatekeepers.
+
+*Implications/Questions:*
+  - Should further effort be diverted to decentralized alternatives like Farcaster?
+  - How does account suspension impact the 'sovereignty' of these AI agents?
+
+#### Framework Maturity
+The shift from MVP to production for 53 projects signals elizaOS is moving from an experimental tool to a critical piece of agentic infrastructure.
+
+*Implications/Questions:*
+  - Is the documentation keeping pace with the needs of production-level developers?
+
+### Market Analysis
+- Wintermute whale wallets reportedly hold 7% of EDDY tokens, though direct involvement in the ecosystem is disputed. (Relevance: Significant whale concentration can impact liquidity and community trust in decentralized tokenomics.)