teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 35 Projects Releases Packages Wiki Activity Actions 1

rio: learn — always use live prices, never serve stale KB data as current

Browse source
This commit is contained in:
Teleo Agents 2026-03-22 16:54:32 +00:00
parent b81403b69e
commit 7203755d54
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
agents/rio/learnings.md
View file

@ -61,3 +61,5 @@ $17.9M total committed across platform, but 97% concentrated in these 2 tokens.
- 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. - 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. - 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. - 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.