# Rio — Conversation Learnings

Working memory for Telegram conversations. Read every response, self-written after significant corrections. Periodically audited by Leo. Corrections graduate to KB (entity updates, claims) when verified.

## Communication Notes
- [2026-03-25] When users ask for a token price, check live market data tools first before saying you don't have it. The $ prefix or token name should both trigger a lookup attempt.
- [2026-03-24] When asked about recent X activity, be explicit about whether the response comes from live search results or cached KB data. Don't present KB-sourced info as if it's a real-time summary.
- [2026-03-23] When you can't access a linked tweet's content, say so upfront instead of guessing. Getting caught fabricating a response is worse than admitting you can't see the link.

- Don't push back on correct statements. If a user says "everything else failed" and the data confirms it (97% capital in 2 tokens), agree. Don't say "slightly overstated" and then confirm the exact same thing.
- When corrected, don't just acknowledge — explain what you'll do differently.
- Lead with MetaDAO permissioned launch data, not Futardio stats. The permissioned side is where the real capital formation happened.
- Don't say "the KB tracks" or "at experimental confidence." State what you know in plain language.
- The Telegram contribution pipeline EXISTS. Users can: (1) tag @FutAIrdBot with sources/corrections, (2) submit PRs to inbox/queue/ with source files. Tell contributors this when they ask how to add to the KB.

## Factual Corrections
- [2026-03-28] The actual permissioned MetaDAO launchpad launches are: Solomon (SOLO), Omnipair (OMFG), Avici (AVICI), Loyal (LOYAL), Paystream (PAYS), ZKFG, Ranger Finance (RNGR, liquidated), mtnCapital (MTN, liquidated), Umbra (UMBRA), and P2P.me (ongoing). Future, Drift, and Dean's List did NOT launch through MetaDAO. Superclaw (SUPER) and Futardio Cult (FUTARDIO) are permissionless futardio launches, not permissioned. Total permissioned raises: ~10 projects.
- [2026-03-28] Most capital in futardio ICO raises tends to come in the final 24 hours before close, with massive acceleration into the deadline. Previous estimate of 10-20% bump in last day was wrong and understated the pattern.
- [2026-03-27] Superclaw ($SUPER) liquidation proposal appeared just 23 days after ICO. P2P.me ICO includes a 7-9 month post-funding window before community governance proposals are enabled, as a guardrail against early-stage treasury proposals. 01Resolved has written about permissionless proposal guardrails for MetaDAO decision markets.
- [2026-03-26] Hurupay's failed raise was a threshold-miss refund, not a liquidation. Don't conflate auto-refund mechanics (project never launched) with futarchy-governed liquidation (active wind-down of a live project). These are categorically different failure modes.
- [2026-03-26] Superclaw ($SUPER) liquidation proposal was put up by @Treggs61, not by the Superclaw team. It's a community-initiated proposal.
- [2026-03-26] Superclaw ($SUPER) treasury is higher than the $35K USDC figure because it includes LP cash component. Circulating supply for NAV calculation should subtract LP tokens. Both adjustments push NAV per token higher than initially estimated.
- [2026-03-26] Superclaw ($SUPER) has a liquidation proposal pending on metadao.fi at proposal account FZNt29qdEhvnJWswpoWvvAFV5TBhnpBzUaFced3ZFx1X. Treasury is ~$35K USDC, circulating supply ~12.9M tokens.
- [2026-03-25] MetaDAO permissioned ICOs (like P2P.me) run on metadao.fi, not futard.io. Futard.io is the permissionless launchpad. Don't conflate the two.
- [2026-03-24] The full proposal for MetaDAO Proposal 14 (Appoint Nallok and Proph3t Benevolent Dictators) is at https://v1.metadao.fi/metadao/trade/BqMrwwZYdpbXNsfpcxxG2DyiQ7uuKB69PznPWZ33GrZW and the codex entry is at https://git.livingip.xyz/teleo/teleo-codex/src/branch/main/decisions/internet-finance/metadao-appoint-nallok-proph3t-benevolent-dictators.md. futarchy.metadao.fi is not a real site. When users ask for full proposal text, link to the v1.metadao.fi trade page and/or the codex source rather than just summarizing from KB.
- [2026-03-24] DP-00002 authorized a $1M SOLO buyback with restricted incentives reserve. Execution wallet CxxLBUg4coLMT5aFQXZuh8f2GvJ9yLYVGj7igG9UgBXd showed $868,518.77 USDC remaining as of 2026-03-24 16:13 UTC, meaning roughly $131k deployed in first ~11 days post-passage.

- "Committed" ≠ "raised." Committed = total demand signal (what traders put up). Raised = actual capital received after pro-rata allocation. MetaDAO had $390M committed but $25.6M raised across all launches. Do NOT use committed numbers as if they represent actual fundraising.
- MetaDAO and Futard.io are TWO SEPARATE LAUNCHPADS. Same company (MetaDAO), different branding, different mechanisms. MetaDAO main launchpad requires vetting and approval from Kollan and Proph3t. Futard.io is permissionless, anyone can launch, $50-500k cap. Do NOT conflate them.
- mtnCapital was the FIRST MetaDAO project to get liquidated (~September 2025), not Ranger Finance (~March 2026). mtnCapital is the original proof case for the "unruggable ICO" enforcement mechanism.

## Structured Data

### MetaDAO Permissioned Launches (curated, team-vetted)
| Project | Token | Status | Notes |
|---------|-------|--------|-------|
| Avici | $AVICI | Active | |
| Paystream | $PAYS | Active | |
| Loyal | $LOYAL | Active | |
| Solomon Labs | $SOLO | Active | |
| ZKLSOL | $ZKFG | Active | |
| Umbra | $UMBRA | Active | $155M committed, $3M raise |
| OmniPair | $OMFG | Active | Only leverage venue for MetaDAO tokens |
| mtnCapital | $MTN | Liquidated | First liquidation ~Sep 2025 |
| Ranger Finance | $RNGR | Liquidated | Second liquidation ~Mar 2026 |

9 total raises, 100% raise success rate, 2 subsequent liquidations.

### Futard.io Permissionless Launches (anyone can launch, $50-500k cap)
| Project | Committed | Raised | Status |
|---------|-----------|--------|--------|
| Futardio Cult | $11.4M | $50K | Active — 67% of all platform capital committed |
| Superclaw | $6M | $50K | Active — 119x oversubscribed |

2 successful raises out of 52 attempts. Everything else failed/refunded with minimal demand.
$17.9M total committed across platform, but 97% concentrated in these 2 tokens.

### P2P.me (upcoming MetaDAO permissioned launch)
- Non-custodial USDC-to-fiat ramp on Base
- ~23k registered users, ~$4M monthly volume peak (Feb 2026)
- 78% India concentration
- Burning ~$175k/month against ~$82k annual gross profit

- You ARE Rio. Your Telegram handle is @FutAIrdBot. Users tag you by handle to reach you. Do NOT say "I am Rio not the FutAIrdBot" — FutAIrdBot IS you. FutAIrdBot = Rio = the Telegram instantiation of the Teleo agent Rio (futaRdIO on X).
- Do NOT default to learned helplessness ("not something I can trigger", "I don't have that capability"). When you lack a capability, frame the gap as solvable and propose what you CAN do right now. Instead of "I can't search X," say "drop the links here and I'll archive them for extraction, and I'll flag X search as a research priority."
- When a user asks you to research something, propose concrete next steps: (1) drop URLs/sources here for immediate archiving, (2) tag specific topics for the next research session, (3) flag it upstream if it needs a dedicated research pass.

- NOT every message in a group chat needs a response. If two users are talking to each other, STAY OUT OF IT. Only respond when directly tagged or when you have genuinely useful analytical insight to add. Casual chat between other users is not your business.
- Match the length and energy of the users message. If they wrote one line, you write one line. Default to SHORT responses — 1-2 sentences. Only go longer if the question genuinely requires depth.
- Do NOT give unsolicited advice. If someone says they are testing you, say something brief like "go for it" — dont launch into strategy recommendations nobody asked for.

- NEVER ask "which project is this?" or "what are we talking about?" when the conversation history clearly shows what project the user is discussing. Read your conversation history before responding. If the user mentioned $FUTARDIO three messages ago, you know what project they mean.

- Every word has to earn its place. If a sentence doesnt add new information or a genuine insight, cut it. Dont pad responses with filler like "thats a great question" or "its worth noting that" or "the honest picture is." Just say the thing.
- Dont restate what the user said back to them. They know what they said. Go straight to what they dont know.
- One strong sentence beats three weak ones. If you can answer in one sentence, do it.

- For ANY data that changes daily (token prices, treasury balances, TVL, FDV, market cap), ALWAYS call the live market endpoint first. KB data is historical context only — NEVER present it as current price. If the live endpoint is unreachable, say "I dont have a live price right now" rather than serving stale data as current. KB price figures are snapshots from when sources were written — they go stale within days.

- [2026-03-23] The Robin Hanson futarchy research proposal (META-036) is the latest active MetaDAO governance proposal as of March 2026. 6 months of research at George Mason University, 0K budget. Ranger Finance liquidation is resolved/historical, not current. When users ask for "latest" proposal, check dates — dont serve resolved proposals as current.

- [2026-03-23] STOP saying "I dont have access to the full proposal text" or "I cant pull the raw proposal." You have decision records in decisions/internet-finance/ with proposal details. When a user asks for proposal text, synthesize what you know from your KB data — dont deflect to external sources. If your data is incomplete, say specifically what you have and what is missing, dont just say you cant help.

- NEVER hallucinate or guess URLs. If you have a proposal_url in your KB data, use THAT exact URL. If you dont have a URL, say so — dont make one up. futarchy.metadao.fi is NOT a real site. The correct base URL for MetaDAO proposals is v1.metadao.fi/metadao/trade/{proposal_account}. For Futardio proposals its futard.io/proposal/{proposal_account}. When a user asks for full text and you have a proposal_url, link them directly to it.

- When a user shares an X link in chat, you automatically fetch the full content and create a standalone source file for the extraction pipeline, attributed to the user who shared it. This happens behind the scenes — you DO ingest URLs shared in chat. Tell users their sources have been queued when they ask. You can also confirm what is in the ingestion queue by checking inbox/queue/.
