ABOVE ALL DATA MODEL IS KEY AND THEN THE INTENT ROUTING MECHANISM AS ALGORITHM CAN BE CHANGED
the repo: https://github.com/feynon/poc-intent-router
ideally should be
unternet kernel is the middleware that makes the intent router and data model work, but a very good way to hedge on top of mcp and other api systems: https://github.com/unternet-co/client/tree/main/kernel
anthropic subagents architecture design, from amp people
on memory management stack: Mem0: Technical Analysis Report
caveat for tool calls: rag is good for retrieval but not tool calls: mcpn repo + mcp-rag paper brief
security
future quests for ultimate moat in training on reasoning traces
Use of primopt + dspy for context and prompt design and programming
vision for the future on device intent router
ui: https://www.lukew.com/ff/entry.asp?2105
algorithm ui link TikTok : background autonomous processes, responsive software