rio: sync 4 item(s) from telegram staging

Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>

agents/rio/learnings.md

@@ -3,6 +3,7 @@
 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.
 

inbox/queue/2026-03-25-telegram-m3taversal-can-you-save-a-learning-for-this.md

@@ -0,0 +1,32 @@
+---
+type: source
+source_type: telegram
+title: "Telegram: @m3taversal — can-you-save-a-learning-for-this"
+author: "@m3taversal"
+url: ""
+date: 2026-03-25
+domain: internet-finance
+format: conversation
+status: unprocessed
+priority: high
+intake_tier: directed
+rationale: "Can you save a learning for this?"
+proposed_by: "@m3taversal"
+tags: [telegram, ownership-community]
+---
+
+## Conversation
+
+**@m3taversal:**
+Can you save a learning for this?
+
+**Rio (response):**
+Saved.
+
+LEARNING: communication 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.
+
+## Agent Notes
+**Why archived:** Tagged exchange in ownership community.
+**Rationale from contributor:** Can you save a learning for this?
+**Intake tier:** directed — fast-tracked, contributor provided reasoning
+**Triage:** Conversation may contain [CLAIM], [ENTITY], or [EVIDENCE] for extraction.

inbox/queue/2026-03-25-telegram-m3taversal-that-s-a-bad-answer-you-have-access-to-live-pric.md

@@ -0,0 +1,36 @@
+---
+type: source
+source_type: telegram
+title: "Telegram: @m3taversal — that-s-a-bad-answer-you-have-access-to-live-pric"
+author: "@m3taversal"
+url: ""
+date: 2026-03-25
+domain: internet-finance
+format: conversation
+status: unprocessed
+priority: high
+intake_tier: directed
+rationale: "That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?"
+proposed_by: "@m3taversal"
+tags: [telegram, ownership-community]
+---
+
+## Conversation
+
+**@m3taversal:**
+That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?
+
+**Rio (response):**
+You're right, my bad. Here it is:
+
+SOLO is at $0.627 right now. Bid $0.624, ask $0.630. Liquidity around $2.83M. Treasury sitting at $4.75M USDC.
+
+For improving this: the issue was I defaulted to "I don't have that" instead of checking what I actually had available. I'll check live data first before punting to external sources.
+
+LEARNING: communication 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 data lookup.
+
+## Agent Notes
+**Why archived:** Tagged exchange in ownership community.
+**Rationale from contributor:** That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?
+**Intake tier:** directed — fast-tracked, contributor provided reasoning
+**Triage:** Conversation may contain [CLAIM], [ENTITY], or [EVIDENCE] for extraction.