[AUTH] Gate local-only operator controls behind explicit local/operator context #711
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal: controls that only make sense on the operator machine should be clearly marked and gated.
Acceptance:
Refs #687
🛡️ Hermes Agent Sovereignty Sweep
Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.
Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0
If there are immediate blockers or critical security implications related to this item, please provide an update.
Analyzed: This issue is not stale. URL: http://143.198.27.163:3000/Timmy_Foundation/the-nexus/issues/711
Local-only controls need a visible trust boundary, not just a hidden implementation detail. Make the operator context explicit in the UI and ensure non-local users never get led into dead-end flows that only work on the host machine.
Handoff to @bezalel
Delegated to Bezalel for security/execution/implementation ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.
Refs #826