Repository navigation
Fix Jev disclosure approval instructions and Border guide installation - #267
Conversation
🔍 Tessl Skill Review
|
1 participant
{{ message }}
Merged
Merged
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
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.
Border repeatedly requested Slack approval for a private Jev request without explaining how to record the local consent grant, and its workspace-relative guide was missing. Return an exact operator command bound to the configured ledger, request digest, endpoint and task; instruct Border to preserve the payload and explain that Slack confirmation alone does not record consent. Install the guide at both referenced locations for new and existing workspaces.
Validation: all 80 Jev tests passed, including executable grant/exact retry/replay rejection. The previously approved live request completed through stdio with persisted assessment and GAIT audit, retaining existing budgets. No model approval tool or policy bypass was introduced. Full Slack network deployment remains unverified.