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

rio: knows it auto-ingests shared URLs + can check queue

Browse source 
Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>
This commit is contained in:
Teleo Pipeline 2026-03-25 13:22:17 +00:00
parent 2901cdb4a0
commit dcd7c00c81
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

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