Skip to content

Add AgentPass action-boundary infographic #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dinpd merged 1 commit into from
Jul 29, 2026
Merged

Add AgentPass action-boundary infographic #66

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,8 @@ public observability roadmap evolves that foundation into a two-plane design:
Trace data supplies correlation and operational context; it does not replace
the durable evidence used for authorization, replay protection, or assessment.

![AgentPass action boundary showing the current stateful runtime-control and intent-assurance planes plus the causal-observability roadmap](docs/agentpass-action-boundary-overview.png)

RBAC can say which identity may access a tool. Prompts can suggest how an agent
should behave. AgentPass answers the runtime execution question:

Expand Down
Binary file added docs/agentpass-action-boundary-overview.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading