Document operator setup, mobile workflow, and threat model #969

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

Scope

Document how an operator enables remote secret input, configures writable engines, authorizes users/chats, completes the mobile flow, and diagnoses safe failure states. Include explicit warnings about mobile notifications, screenshots, shared devices, Telegram retention/deletion limits, and external engine permissions.

Document which engines support writes, reference syntax, expiry/cancellation semantics, and what is deliberately unsupported.

Acceptance criteria

  • A new operator can configure and complete the flow from the documentation without SSH or editing raw secrets into chat commands.
  • Examples never contain real-looking credentials and do not put values in shell history, issue bodies, or ordinary prompts.
  • The docs explain the trust boundary and why the model is not involved in secret entry.
  • Troubleshooting distinguishes authorization, engine capability, transport, expiry, and backend errors without suggesting unsafe workarounds.

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-1786748942438-14-abe5ddd0 · GitHub #509 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18

## Scope Document how an operator enables remote secret input, configures writable engines, authorizes users/chats, completes the mobile flow, and diagnoses safe failure states. Include explicit warnings about mobile notifications, screenshots, shared devices, Telegram retention/deletion limits, and external engine permissions. Document which engines support writes, reference syntax, expiry/cancellation semantics, and what is deliberately unsupported. ## Acceptance criteria - A new operator can configure and complete the flow from the documentation without SSH or editing raw secrets into chat commands. - Examples never contain real-looking credentials and do not put values in shell history, issue bodies, or ordinary prompts. - The docs explain the trust boundary and why the model is not involved in secret entry. - Troubleshooting distinguishes authorization, engine capability, transport, expiry, and backend errors without suggesting unsafe workarounds. ### 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-1786748942438-14-abe5ddd0` · GitHub #509 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam added the hightask labels 2026-10-27 13:38:30 +00:00
sam self-assigned this 2026-10-27 13:38:30 +00:00
sam closed this issue 2026-10-27 13:38:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#969