Implement mobile-first secret-input UX in Telegram #966

Closed
opened 2026-10-27 13:38:29 +00:00 by sam · 0 comments
Owner

Scope

Implement the first mobile channel adapter for the remote secret-input flow using the existing Telegram command/conversation patterns. The UX should work on a phone with short prompts, explicit target selection, a sensitive-entry step, confirmation, cancellation, and expiry.

Use Telegram-specific message controls where available to reduce persistence and accidental disclosure, but do not treat client-side deletion as the sole security boundary. Never echo or quote the submitted value.

Acceptance criteria

  • A mobile user can initiate the flow, choose an allowed engine/reference, submit a value, and get a redacted result without model involvement.
  • The value-entry step is clearly marked sensitive and supports /cancel, timeout, and safe recovery from invalid input.
  • Only the initiating authorized user can continue the session; another user/chat cannot hijack it.
  • Success/failure messages contain no raw value, secret-derived content, or unsafe backend detail.
  • Telegram adapter tests cover happy path, wrong user/chat, cancellation, expiry, duplicate messages, malformed input, and delivery failure.

Close reason

Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.


Imported from beads archie-core-1786748942364-11-47ec9e60 · GitHub #507 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18

## Scope Implement the first mobile channel adapter for the remote secret-input flow using the existing Telegram command/conversation patterns. The UX should work on a phone with short prompts, explicit target selection, a sensitive-entry step, confirmation, cancellation, and expiry. Use Telegram-specific message controls where available to reduce persistence and accidental disclosure, but do not treat client-side deletion as the sole security boundary. Never echo or quote the submitted value. ## Acceptance criteria - A mobile user can initiate the flow, choose an allowed engine/reference, submit a value, and get a redacted result without model involvement. - The value-entry step is clearly marked sensitive and supports `/cancel`, timeout, and safe recovery from invalid input. - Only the initiating authorized user can continue the session; another user/chat cannot hijack it. - Success/failure messages contain no raw value, secret-derived content, or unsafe backend detail. - Telegram adapter tests cover happy path, wrong user/chat, cancellation, expiry, duplicate messages, malformed input, and delivery failure. ### Close reason Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic. --- _Imported from beads `archie-core-1786748942364-11-47ec9e60` · GitHub #507 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam added the hightask labels 2026-10-27 13:38:29 +00:00
sam self-assigned this 2026-10-27 13:38:29 +00:00
sam closed this issue 2026-10-27 13:38:29 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#966