---
title: "Discussion on \"Circle the Agent\" | Hashnode"
description: "Discussion on \"Circle the Agent\". The boundary problem behind agent identity"
url: "https://hashnode.com/posts/circle-the-agent/6b018b6c039ed3ac8a779f95"
---

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

Discussion

# [Circle the Agent](https://amanyadav.hashnode.dev/circle-the-agent?utm_source=hashnode&utm_medium=feed)

The boundary problem behind agent identity

8h ago · 9 min read · amanyadav.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#identity-management](https://hashnode.com/tag/identity-management)
-   [#governance](https://hashnode.com/tag/governance)

## Written by

[Aman Yadav](https://hashnode.com/@amanyadav)

@amanyadav

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

## Responses 1

Markdown supported · ⌘↵ to post

[JustOneCX](https://hashnode.com/@justonecx)

[3h ago](https://hashnode.com/posts/circle-the-agent/6b018b6c039ed3ac8a779f95/comment/6b01dd1e206ff08361e5b033)

Where does the boundary sit for you: the token the agent carries, or the policy checked at each service?
