Define remote secret-input contract, authorization, and lifecycle #965

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

Scope

Define the channel-neutral capability for initiating and completing a remote secret-input session. Model target engine/reference, authenticated actor, originating channel/session, challenge state, expiry, cancellation, one-time consumption, and redacted outcomes.

The flow must be separate from normal model-generated tool calls: the raw value must not enter the LLM prompt, tool transcript, ordinary event stream, or persistent chat record.

Acceptance criteria

  • Typed interfaces cover begin, inspect/choose target, submit, cancel, expire, and status/result.
  • Authorization is explicit and checked at initiation and submission; sessions are bound to actor and channel/session context.
  • Expiry, cancellation, replay, concurrent submission, and restart behaviour are defined and tested.
  • Secret-bearing data has a documented in-memory lifetime and is zeroed/released as far as Go semantics permit.
  • No raw value appears in errors, structured logs, metrics, traces, events, or persisted state.

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-1786748942345-10-50a04c62 · GitHub #505 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18

## Scope Define the channel-neutral capability for initiating and completing a remote secret-input session. Model target engine/reference, authenticated actor, originating channel/session, challenge state, expiry, cancellation, one-time consumption, and redacted outcomes. The flow must be separate from normal model-generated tool calls: the raw value must not enter the LLM prompt, tool transcript, ordinary event stream, or persistent chat record. ## Acceptance criteria - Typed interfaces cover begin, inspect/choose target, submit, cancel, expire, and status/result. - Authorization is explicit and checked at initiation and submission; sessions are bound to actor and channel/session context. - Expiry, cancellation, replay, concurrent submission, and restart behaviour are defined and tested. - Secret-bearing data has a documented in-memory lifetime and is zeroed/released as far as Go semantics permit. - No raw value appears in errors, structured logs, metrics, traces, events, or persisted state. ### 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-1786748942345-10-50a04c62` · GitHub #505 · 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#965