Design /rollback [number] filesystem checkpoints, /stop background process termination, /approve and /deny for dangerous commands. /approve is RESERVED exclusively for dangerous-command approval; it must not be interpreted as task approval. The pending-command UX is inline selection buttons: Approve this time, Approve Permanently, Deny. Define the exact policy scope/lifetime for permanent approval, callback authorization, expiry, audit persistence, and cancellation. Requires a real sandbox/process/checkpoint authority; do not create commands that claim control over host processes or filesystem state Archie does not own.
Acceptance Criteria
For every pending dangerous command, Telegram renders authorized inline buttons exactly representing Approve this time, Approve Permanently, and Deny. Callbacks are recipient-bound, expiring, single-use, auditable, and cannot authorize a changed command. Permanent approval scope/lifetime is explicit. /approve exclusively controls this policy; /deny controls the same policy. Authority boundaries match actual sandbox/process ownership; tests cover authorization, expiry, replay, denial, and failure.
Imported from beads archie-core-1786637498650-335-ab2a80b5 · GitHub #356 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08
Design /rollback [number] filesystem checkpoints, /stop background process termination, /approve and /deny for dangerous commands. /approve is RESERVED exclusively for dangerous-command approval; it must not be interpreted as task approval. The pending-command UX is inline selection buttons: Approve this time, Approve Permanently, Deny. Define the exact policy scope/lifetime for permanent approval, callback authorization, expiry, audit persistence, and cancellation. Requires a real sandbox/process/checkpoint authority; do not create commands that claim control over host processes or filesystem state Archie does not own.
### Acceptance Criteria
For every pending dangerous command, Telegram renders authorized inline buttons exactly representing Approve this time, Approve Permanently, and Deny. Callbacks are recipient-bound, expiring, single-use, auditable, and cannot authorize a changed command. Permanent approval scope/lifetime is explicit. /approve exclusively controls this policy; /deny controls the same policy. Authority boundaries match actual sandbox/process ownership; tests cover authorization, expiry, replay, denial, and failure.
---
_Imported from beads `archie-core-1786637498650-335-ab2a80b5` · GitHub #356 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design /rollback [number] filesystem checkpoints, /stop background process termination, /approve and /deny for dangerous commands. /approve is RESERVED exclusively for dangerous-command approval; it must not be interpreted as task approval. The pending-command UX is inline selection buttons: Approve this time, Approve Permanently, Deny. Define the exact policy scope/lifetime for permanent approval, callback authorization, expiry, audit persistence, and cancellation. Requires a real sandbox/process/checkpoint authority; do not create commands that claim control over host processes or filesystem state Archie does not own.
Acceptance Criteria
For every pending dangerous command, Telegram renders authorized inline buttons exactly representing Approve this time, Approve Permanently, and Deny. Callbacks are recipient-bound, expiring, single-use, auditable, and cannot authorize a changed command. Permanent approval scope/lifetime is explicit. /approve exclusively controls this policy; /deny controls the same policy. Authority boundaries match actual sandbox/process ownership; tests cover authorization, expiry, replay, denial, and failure.
Imported from beads
archie-core-1786637498650-335-ab2a80b5· GitHub #356 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08