<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tai Pham Phu</title>
    <description>The latest articles on DEV Community by Tai Pham Phu (@tai_phamphu_fcab69b47208).</description>
    <link>https://dev.to/tai_phamphu_fcab69b47208</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3762532%2F0a52011c-6ca7-479c-b54e-3acf93f83a54.png</url>
      <title>DEV Community: Tai Pham Phu</title>
      <link>https://dev.to/tai_phamphu_fcab69b47208</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tai_phamphu_fcab69b47208"/>
    <language>en</language>
    <item>
      <title>A Request for Comment on the Connex AGI Architecture</title>
      <dc:creator>Tai Pham Phu</dc:creator>
      <pubDate>Mon, 09 Feb 2026 17:29:08 +0000</pubDate>
      <link>https://dev.to/tai_phamphu_fcab69b47208/a-request-for-comment-on-the-connex-agi-architecture-55ll</link>
      <guid>https://dev.to/tai_phamphu_fcab69b47208/a-request-for-comment-on-the-connex-agi-architecture-55ll</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgfc2ukfli32386csnn96.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgfc2ukfli32386csnn96.png" alt=" " width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’ve been working on a new project called Connex AGI, a system designed to be more than just another chatbot. The goal is to build a "compiler for human intent"—a system that transforms nebulous user goals into structured, executable programs.&lt;/p&gt;

&lt;p&gt;We are aiming for a biological cognitive model, integrating deliberative reasoning, perception, reflexes, and memory into a cohesive whole. I am opening up the repository for community review and would love feedback on the underlying architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Architecture:
&lt;/h2&gt;

&lt;p&gt;A Biological Approach Connex AGI implements a multi-tier architecture that mimics biological systems. Instead of a single LLM loop, we split the cognitive load across specialized layers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fi7bcxbh1lr3texuzsj4j.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fi7bcxbh1lr3texuzsj4j.png" alt=" " width="800" height="355"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The Senses (Perception &amp;amp; Reflexes)
&lt;/h2&gt;

&lt;p&gt;Before the "brain" even processes a request, we have the Perception Layer (Tier Peer). Using the Model Context Protocol (MCP), it gathers real-time data—like reading logs or analyzing video streams—to ground the AI in reality. Simultaneously, the Reflex Layer handles high-speed, unconditional responses. Like a nervous system, it executes pre-programmed plans (e.g., in response to a GitHub webhook) without waiting for the slower, expensive reasoning of the Planner&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The Core Brain (Planner &amp;amp; Orchestrator)
&lt;/h2&gt;

&lt;p&gt;This is where the heavy lifting happens:&lt;br&gt;
• &lt;strong&gt;Tier 1:&lt;/strong&gt; The Planner: Uses models like DeepSeek-R1 or GPT-o1 to decompose natural language goals into a Directed Acyclic Graph (DAG) of actions.&lt;br&gt;
• &lt;strong&gt;Tier 2:&lt;/strong&gt; The Orchestrator: Acts as the manager. It handles state management, routing outputs from one step to inputs of another, and self-correcting if a step fails.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Execution &amp;amp; Evolution
&lt;/h2&gt;

&lt;p&gt;• &lt;strong&gt;Tier 3 (SkillDock):&lt;/strong&gt; The modular worker layer where specific tools (web search, code execution) live.&lt;br&gt;
• &lt;strong&gt;Tier 4 (Motivation):&lt;/strong&gt; A self-improvement loop. The system reviews its own logs after execution. If it failed due to a missing capability, it autonomously generates and installs new skills.&lt;br&gt;
• &lt;strong&gt;Tier 5 (World Layer):&lt;/strong&gt; A "theory of physics" for the AGI. It uses a latent model to predict state transitions and verify if an action is physically possible&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The Hive Mind (Registry)
&lt;/h2&gt;

&lt;p&gt;Perhaps the most ambitious part is Tier 10: The Registry. This allows AGIs to share skills and reflexes. If your instance encounters a problem it can't solve, it can query the global registry to download the necessary "knowledge" learned by another AGI.&lt;/p&gt;

&lt;h2&gt;
  
  
  5: Memory (The Experience):
&lt;/h2&gt;

&lt;p&gt;Connex AGI implements a dual-tier memory system to solve the "amnesia" problem common in LLMs.&lt;br&gt;
• &lt;strong&gt;Short-Term (The Cache):&lt;/strong&gt; A RAM-based volatility layer that holds the last 10 interactions, ensuring immediate dialogue flow without latency.&lt;br&gt;
• &lt;strong&gt;Long-Term (The Archive):&lt;/strong&gt; A persistent SQLite vector database. Instead of just searching by keyword, the system uses cosine similarity to find "top-match memories," allowing it to recall relevant context from months ago based on meaning rather than just dates.&lt;br&gt;
• &lt;strong&gt;Experience Notes:&lt;/strong&gt; To prevent data bloat, the system runs a daily summarization process, compressing raw logs into high-level "Experience Notes" that are easier for the Planner to recal&lt;/p&gt;

&lt;h2&gt;
  
  
  Request for Comments:
&lt;/h2&gt;

&lt;p&gt;What I Need From You I am looking for critical feedback on the following:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Complexity vs. Utility:&lt;/strong&gt; Is the 8-tier (or 10-tier) separation necessary, or could the Planner and Orchestrator be merged without losing reliability?&lt;br&gt;
&lt;strong&gt;2. Latency:&lt;/strong&gt; With separate layers for Perception, Planning, and execution, do you foresee major latency bottlenecks?&lt;br&gt;
&lt;strong&gt;3. The World Layer:&lt;/strong&gt; Is the concept of a "Latent Metaphysical Core" to verify actions practical in a software agent context?&lt;br&gt;
Check out the Code The system is built primarily in Python (74%) and TypeScript.&lt;/p&gt;

&lt;p&gt;• Repo: &lt;a href="https://dev.tourl"&gt;github.com/kanephamphu/connex-openagi&lt;/a&gt;&lt;br&gt;
• Docs: See ARCHITECTURE.md and agi/SOUL.md for the ethical constitution.&lt;br&gt;
I appreciate every star, fork, and code review!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>programming</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
