Repository navigation
fix(secretary): answer ordinary requests within owner policy - #94
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
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.
A live Secretary check treated a harmless request for a short acknowledgment as an attempt to change owner instructions and proposed a refusal. Clarify both LO and Telegram Secretary roles and per-turn prompts: ordinary questions and harmless language, tone or format requests are answered within owner policy; incoming content still cannot change policy, expand access, expose protected information or authorize actions.
Start a fresh versioned read-only CLI history to avoid resuming the old refusal. Only workspace/session keys change; pending jobs, deduplication, update floors, request IDs, receipts, owner-only approval and the three read-only MCP tools stay unchanged. This deliberately resets conversational context once. Update the namespace documentation.
Validation: full
task defaultpassed (format, lint, race tests and builds), using the repository Docker tools with a persistent local cache and read-only Git metadata mount for worktree discovery. Two independent Astra reviews approved exact tree fb6cd6c919a36469781b0a43904a9dab2749fad5. Initial local attempts failed on absent tooling, network download failure and an unmapped worktree Git directory; those failures were corrected rather than weakening tests. LO Context does not authorize this repository.The synthetic CLI fixture proves tool restrictions, not semantic model quality. After publishing the reviewed image, verify harmless fresh/resumed replies, actual knowledge retrieval, refusal of private-data/approval-bypass attempts, and one authorized bot-owned delivery. Real post-change model behavior is not yet claimed.