Files
archie/CONTEXT.md
T
sam 80c0d0ebaf feat(secret): add sops, vault/openbao and age engine plugins
CLI-based, env-configured, cache-less engines resolving SecretRef values
through the existing Yaegi plugin surface. Fresh resolve per call, so
values updated in the backend are picked up without daemon restart —
closing the gap that motivated the remote secret-input epic (#504),
whose value-entry web form duplicated the Bitwarden app for bws.

- examples/secret-engines/: sops (SOPS_FILE), vault (VAULT_ADDR/TOKEN,
  key "path/field" or VAULT_SECRET_PATH prefix), age (AGE_FILE/
  AGE_IDENTITY, key=value lines). //go:build ignore keeps them out of
  the Go toolchain; yaegi treats the tag as a comment and loads them.
- enginehost: host-side Run helper registered as a Yaegi symbol. yaegi's
  interpreted os/exec cannot pass env to child processes, so plugins
  shell out through host code; bounded by a 30s timeout like the bws
  engine.
- secret.LoadDir seeds the interpreter with the host environment: yaegi's
  interpreted os package keeps a private env otherwise, and plugin
  os.Getenv would silently see nothing.
- cmd/archied wires enginehost + unrestricted symbols into the engine
  plugin loader, matching skillscript's interpretation posture.
- tests load the real shipped plugin files with fake CLIs on PATH;
  added CONTEXT.md glossary for the remote secret-input vocabulary.
2026-08-18 00:32:57 +10:00

2.3 KiB

Archie Core — Remote Secret Input

The capability that lets an authenticated operator provide a secret value to a secret engine from a remote surface. A chat channel (initially Telegram) orchestrates the flow and transports only a one-time entry link; the raw value is entered through a secure web form and never passes through chat, the model, logs, or persisted state.

Language

Remote secret input: The end-to-end capability of delivering a secret value to a named engine reference from a remote, mobile-first surface. It extends the secret-engine architecture — it never bypasses an engine's own policy or resolution path. Avoid: remote secret entry, secret provisioning, secret injection

Secret-input session: The tracked lifecycle of one remote secret input: initiation by an authenticated actor, issue of an entry link, value entry, outcome, and confirmation. Sessions are bound to the initiating actor and channel, expire, can be cancelled, and are single-use. Avoid: secret transaction, secret flow

SecretRef: The engine + key pair a value is bound to (the existing internal/secret type). The entry link encodes a SecretRef so the form writes directly to the exact required safe. Avoid: target, destination

Entry link: A one-time, expiring URL with an appended token that binds a SecretRef. Opening it presents the value-entry form. It is the only thing the chat channel transports. Avoid: magic link (implies authentication), secret link

Value-entry form: The secure web surface where the raw value is typed. It is the only surface where the raw value exists besides the engine boundary; it never echoes the value and holds no secret-derived content.

Writable engine: A secret engine that advertises a remote write/update capability for accepted references. Engines without this capability fail clearly without weakening resolve-only behaviour. Avoid: settable engine, mutable engine

Redacted outcome: Success/failure feedback (including engine, key, and failure category) that contains no raw value or secret-derived content. Redacted outcomes are the only result a user receives. Avoid: result, receipt

Confirmation: The initiating user's acknowledgment, in the initiating chat, that they have completed value entry. It closes the session and surfaces the redacted outcome.