Add fleet containment, session-coupled proxy policy, and audit-durability direction#48
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extend the roadmap direction with the fleet and observability bets: session behavioral containment (telemetry counters plus a deny-ratio circuit breaker keyed per session token, explicitly not spend metering), API-proxy policy coupled to session grants so brokered tools like helm and ansible are boxed inside the caller's grant, audit durability (level-independent audit sink, session tokens and exit codes on records, per-use secret audit, configurable history retention), and a docs split moving deep reference material out of the README.