docs(osapi): clarify when key enforcement begins - #133
Merged
Merged
Conversation
FR-009 asked what happens to an agent with no stored key, which today is every agent. Answer: enforcement is something the operator turns on per side, never a side effect of upgrading, and once on a message from an agent with no stored key is refused there. Adds SC-007 for the staged rollout that implies: enable one side, see who would be refused, re-enrol them, finish without the fleet stopping at a moment nobody chose. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c
|
Thank you for contributing to this project! 😊🕹️ |
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c
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.
Clarify session on
002-agent-key-store, one question.Q: When the controller holds no key for an agent — today, every agent — must it refuse that agent's messages, or accept them until re-enrolment?
A: Refuse, but only once the operator enables enforcement for that side, with the fleet view showing who still lacks a key so re-enrolment can be staged.
FR-009 rewritten from a question into that rule, and SC-007 added for the rollout it implies. Matches the fail-closed choice already shipped in the other direction, where an agent without a cached controller key refuses jobs.
Next: plan, then tasks.
🤖 Generated with Claude Code