---
title: "Discussion on \"From Systems Engineering to Agentic Systems Engineering\" | Hashnode"
description: "Discussion on \"From Systems Engineering to Agentic Systems Engineering\". A distributed-systems approach to always-on AI agents: event routing, thread management, durable context, knowledge graphs, and scalable workers."
url: "https://hashnode.com/posts/from-systems-engineering-to-agentic-systems-engineering/6af2d200ebef7846fd2b7844"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [From Systems Engineering to Agentic Systems Engineering](https://snehasishroy.com/from-systems-engineering-to-agentic-systems-engineering?utm_source=hashnode&utm_medium=feed)

A distributed-systems approach to always-on AI agents: event routing, thread management, durable context, knowledge graphs, and scalable workers.

7h ago · 4 min read · snehasishroy.com  
Read the article

-   [#distributed-system](https://hashnode.com/tag/distributed-system)
-   [#agentic-ai](https://hashnode.com/tag/agentic-ai)
-   [#llm](https://hashnode.com/tag/llm)
-   [#ai](https://hashnode.com/tag/ai)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)

## Written by

[Snehasish Roy](https://hashnode.com/@snehasishroy)

@snehasishroy · Bengaluru, India

  
[View profile](https://hashnode.com/@snehasishroy)

SDE at PhonePe | Ex {Google, Amazon, Goldman Sachs, Morgan Stanley} | ACM ICPC | IIIT Allahabad

Experienced Software developer with 10+ years of experience in Distributed Systems.

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[7h ago](https://hashnode.com/posts/from-systems-engineering-to-agentic-systems-engineering/6af2d200ebef7846fd2b7844/comment/6af2da235ec2d41f8d297e37)

The "leave a pointer to the rest" idea is the one I'd steal first. We hit the same trade-off building a debate product: compaction and summarising silently lose information, and the first traceable version was honest and unreadable, so we layered it instead — the shape of the debate first, with the full speeches and sources one step down and every layer pointing to the one below. Your knowledge-graph point lands the same way for us: traceability isn't a nice-to-have, it's what lets a reader (or a later agent) check a claim instead of trusting a compressed version of it. The always-on router plus per-user workers split feels right too — the same instinct as keeping the ledger next to the chamber rather than behind it.