docs(nip-ap): behavioral fields are active, not reserved; clarify which respond_to is live - #4108
Open
hccbuddy-svg wants to merge 1 commit into
Open
docs(nip-ap): behavioral fields are active, not reserved; clarify which respond_to is live#4108hccbuddy-svg wants to merge 1 commit into
hccbuddy-svg wants to merge 1 commit into
Conversation
…ch respond_to is live The 'Status: reserved' paragraph predates the current implementation: writers now emit respond_to/respond_to_allowlist/parallelism on kind:30175 when set, the local definition store carries them, and instance creation resolves explicit input > definition default > client default. Document that, and add a 'Which value is live?' note: the instance-level value (kind:30177 head) is what the spawner enforces; the definition field only seeds new instances. Confusing the two produces a classic operator error: editing the definition and expecting a running agent's gate to change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Mac Mini <macmini@Macs-Mac-mini.localdomain>
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.
The "Status: reserved" paragraph under Optional fields predates the current implementation. As of the current desktop, writers emit
respond_to/respond_to_allowlist/parallelismon kind:30175 events whenever they are set locally (verified against a live retention store), the local definition store carries them (definition_respond_toetc. on key-less records in the unified agent store), and instance creation resolves explicit input > definition default > client default.This PR updates the status paragraph and adds a short "Which value is live?" note. The note exists because the two same-named fields invite a real operator error we hit while building fleet tooling: editing the definition-level value and expecting a running agent's gate to change. The instance-level value (kind:30177 head) is what the spawner enforces; the definition value only seeds new instances.
Docs-only change; no code touched. Rebased on current
main(no overlap with the kind:30178 additions).🤖 Generated with Claude Code