<?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: Afrid Thenebanda</title>
    <description>The latest articles on DEV Community by Afrid Thenebanda (@afrid_thenebanda_e4b62276).</description>
    <link>https://dev.to/afrid_thenebanda_e4b62276</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4069912%2F2694c7f6-f83f-46f0-a2f4-75863a07df81.jpg</url>
      <title>DEV Community: Afrid Thenebanda</title>
      <link>https://dev.to/afrid_thenebanda_e4b62276</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/afrid_thenebanda_e4b62276"/>
    <language>en</language>
    <item>
      <title>🚨 AI agents can reason. But should they be allowed to authorize themselves?</title>
      <dc:creator>Afrid Thenebanda</dc:creator>
      <pubDate>Fri, 23 Oct 2026 06:28:21 +0000</pubDate>
      <link>https://dev.to/afrid_thenebanda_e4b62276/ai-agents-can-reason-but-should-they-be-allowed-to-authorize-themselves-1djl</link>
      <guid>https://dev.to/afrid_thenebanda_e4b62276/ai-agents-can-reason-but-should-they-be-allowed-to-authorize-themselves-1djl</guid>
      <description>&lt;p&gt;Recent cybersecurity reports made this question much more real.&lt;/p&gt;

&lt;p&gt;Major U.S. banks are now reportedly detecting unauthorized third-party AI agents inside customer accounts, with some agent activity appearing to go beyond the user's original instructions.&lt;/p&gt;

&lt;p&gt;That exposes a fundamental problem with Agentic AI:&lt;br&gt;
Intelligence is not authority.&lt;br&gt;
An AI agent may understand what needs to be done.&lt;br&gt;
That doesn't mean it should automatically have permission to do it.&lt;/p&gt;

&lt;p&gt;So I started building:&lt;br&gt;
🛡️ Agent Security Gateway&lt;br&gt;
A vendor-neutral Zero-Trust security and authorization layer for AI agents.&lt;br&gt;
The idea is simple:&lt;br&gt;
🧠 The model proposes.&lt;br&gt;
🛡️ The gateway decides.&lt;br&gt;
⚙️ The tool executes only after authorization.&lt;/p&gt;

&lt;p&gt;Instead of allowing GPT, Claude, local models, or future autonomous agents to directly execute sensitive operations, every action passes through a deterministic security boundary.&lt;/p&gt;

&lt;p&gt;Even if the model gets manipulated into proposing a dangerous action, the model itself cannot grant the permission required to execute it.&lt;/p&gt;

&lt;p&gt;This is not about reducing AI autonomy.&lt;br&gt;
I believe Zero Trust for AI Agents is going to become an important part of the next generation of AI infrastructure.&lt;br&gt;
This project is currently evolving rapidly, and I’ll be open-sourcing it for the community.&lt;br&gt;
🔓 I’ll share the GitHub repository in the comments.&lt;/p&gt;

&lt;p&gt;Live demo:&lt;br&gt;
&lt;a href="https://agent-security-gateway-v01.vercel.app/#home" rel="noopener noreferrer"&gt;https://agent-security-gateway-v01.vercel.app/#home&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d especially love feedback from:&lt;br&gt;
AI engineers&lt;br&gt;
Cybersecurity researchers&lt;br&gt;
Agent/MCP developers&lt;br&gt;
Open-source contributors&lt;br&gt;
And instead of only asking:&lt;br&gt;
“What do you think?”&lt;br&gt;
I have a better question:&lt;br&gt;
🔥 How would you try to break this architecture?&lt;/p&gt;

&lt;h1&gt;
  
  
  AgenticAI #AISecurity #CyberSecurity #AIAgents #OpenSource #MCP #LLM #ZeroTrust #ArtificialIntelligence
&lt;/h1&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
![ ](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/qlpkgy33zu3i3p4hkc92.png)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>agents</category>
      <category>ai</category>
      <category>cybersecurity</category>
      <category>security</category>
    </item>
    <item>
      <title>EdgeAI Forge: Building a Local-First Physical AI Architecture for Autonomous Industrial Pipelines</title>
      <dc:creator>Afrid Thenebanda</dc:creator>
      <pubDate>Sun, 09 Aug 2026 15:43:40 +0000</pubDate>
      <link>https://dev.to/afrid_thenebanda_e4b62276/edgeai-forge-building-a-local-first-physical-ai-architecture-for-autonomous-industrial-pipelines-485h</link>
      <guid>https://dev.to/afrid_thenebanda_e4b62276/edgeai-forge-building-a-local-first-physical-ai-architecture-for-autonomous-industrial-pipelines-485h</guid>
      <description>&lt;h1&gt;
  
  
  EdgeAI Forge: Building a Local-First Physical AI Architecture for Autonomous Industrial Pipelines
&lt;/h1&gt;

&lt;p&gt;AI is moving beyond chat. In industrial automation, the useful question is not only whether a model can answer an engineering question, but whether an AI system can help plan, generate, test, benchmark, review, deploy, and improve software that operates close to machines.&lt;/p&gt;

&lt;p&gt;That is the idea behind &lt;strong&gt;EdgeAI Forge&lt;/strong&gt;, an early-stage local-first agentic AI platform for Physical AI, machine vision, robotics, ROS 2, PLC integration, and edge deployment.&lt;/p&gt;

&lt;p&gt;The target workflow is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Requirement -&amp;gt; Plan -&amp;gt; Generate -&amp;gt; Test -&amp;gt; Benchmark
            -&amp;gt; Optimize -&amp;gt; Review -&amp;gt; Deploy -&amp;gt; Monitor -&amp;gt; Learn
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Why local first?
&lt;/h2&gt;

&lt;p&gt;Industrial workloads have constraints that general cloud-first assistants do not always address well:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;private image, telemetry, and engineering data;&lt;/li&gt;
&lt;li&gt;low-latency or offline operation;&lt;/li&gt;
&lt;li&gt;hardware-aware development and testing;&lt;/li&gt;
&lt;li&gt;integration with cameras, robots, PLCs, Jetson devices, and ROS 2;&lt;/li&gt;
&lt;li&gt;traceable artifacts and repeatable deployments; and&lt;/li&gt;
&lt;li&gt;human approval for safety-critical actions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Agentic workflows are also token-intensive. A single engineering request may require planning, code generation, validation, retrying, documentation, and testing. Sending every intermediate step to a cloud model can become expensive and can expose data that should remain on premises.&lt;/p&gt;

&lt;p&gt;EdgeAI Forge therefore follows a simple principle:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Run frequent and private workflows locally. Use cloud models selectively for complex reasoning or large-context tasks.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  A specialized multi-agent architecture
&lt;/h2&gt;

&lt;p&gt;Instead of asking one model to do everything, the target design assigns focused responsibilities to specialized agents:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Planner Agent&lt;/strong&gt; — converts a goal into requirements, tasks, risks, and expected outputs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vision Agent&lt;/strong&gt; — designs preprocessing, training, inference, and optimization pipelines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ROS Agent&lt;/strong&gt; — proposes ROS 2 packages, nodes, topics, launch files, tests, and deployment steps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Robotics Agent&lt;/strong&gt; — supports simulation-first integration and reviewed motion workflows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PLC/Automation Agent&lt;/strong&gt; — prepares guarded Modbus and OPC UA integration templates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Testing Agent&lt;/strong&gt; — generates unit, integration, smoke, and performance tests.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deployment Agent&lt;/strong&gt; — prepares reviewed Jetson and edge-device delivery workflows.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Documentation Agent&lt;/strong&gt; — records architecture decisions, usage, operations, and results.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The current proof of concept implements Planner, Vision, and ROS agents through an asynchronous Ollama client. The broader repository includes a FastAPI gateway, a Next.js command-center prototype, Docker infrastructure, observability configuration, benchmark utilities, and design scaffolds for the remaining modules.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two logical planes
&lt;/h2&gt;

&lt;p&gt;The target architecture separates coordination from model execution:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A &lt;strong&gt;control plane&lt;/strong&gt; manages APIs, orchestration, task state, memory, artifacts, approval gates, the dashboard, and observability.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;compute plane&lt;/strong&gt; serves local LLMs/VLMs, vision and robotics models, TensorRT workloads, and future GPU-accelerated inference.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Those layers can connect to Jetson devices, cameras, sensors, robots, PLCs, and HMI/SCADA systems. Cloud endpoints remain optional extensions rather than the default path.&lt;/p&gt;

&lt;h2&gt;
  
  
  Example: a ROS 2 vision pipeline
&lt;/h2&gt;

&lt;p&gt;Consider this request:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Build a ROS 2 pipeline that reads USB-camera frames, detects objects, publishes detections, measures FPS, and prepares deployment to Jetson Orin.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The long-term goal is for the platform to turn that requirement into reviewed engineering artifacts such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;package and node structure;&lt;/li&gt;
&lt;li&gt;topics, services, actions, and launch files;&lt;/li&gt;
&lt;li&gt;image preprocessing and inference code;&lt;/li&gt;
&lt;li&gt;Docker and configuration files;&lt;/li&gt;
&lt;li&gt;unit and integration tests;&lt;/li&gt;
&lt;li&gt;latency, FPS, and GPU benchmarks;&lt;/li&gt;
&lt;li&gt;TensorRT optimization guidance;&lt;/li&gt;
&lt;li&gt;deployment and rollback instructions; and&lt;/li&gt;
&lt;li&gt;generated operating documentation.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Safety is part of the architecture
&lt;/h2&gt;

&lt;p&gt;Physical AI must be human-governed. EdgeAI Forge is not intended to bypass engineering review, machine interlocks, or functional-safety systems.&lt;/p&gt;

&lt;p&gt;Real robot motion, PLC logic, production deployment, and machine-control changes should require explicit approval. Simulation, dry runs, tests, logs, and rollback plans should be first-class workflow stages.&lt;/p&gt;

&lt;h2&gt;
  
  
  Current status
&lt;/h2&gt;

&lt;p&gt;This is an early prototype, not a production platform. Some components are runnable, while others are interfaces, placeholders, or roadmap items. I am sharing it now because architecture feedback is most valuable before the design hardens.&lt;/p&gt;

&lt;p&gt;The project is developed in public under the BSD 3-Clause License.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/afridali123/EdgeAI_Forge" rel="noopener noreferrer"&gt;https://github.com/afridali123/EdgeAI_Forge&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Long-form background: &lt;a href="https://www.linkedin.com/pulse/edgeai-forge-my-journey-toward-local-agentic-ai-afrid-thenebanda-lpdhc/" rel="noopener noreferrer"&gt;https://www.linkedin.com/pulse/edgeai-forge-my-journey-toward-local-agentic-ai-afrid-thenebanda-lpdhc/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I would especially value feedback on local model routing, ROS 2 artifact generation, simulation-first safety gates, Jetson deployment, observability, and meaningful evaluation of engineering agents.&lt;/p&gt;

</description>
      <category>opensource</category>
    </item>
  </channel>
</rss>
