Skip to content

vault slice 1: production-ready runtime behind TRIOS_VAULT=on (store, signed leases, run, import, dedup, export) #1765

Open

Description

@gHashTag

Part of #1759. Specs: Trinity-S-AI-DNA/t27#8761.

What

The vault runtime on vault-mvp. It is production-ready behind TRIOS_VAULT=on and off by default. Every decision is a call into the vendored cards: specs/vault/policy.wasm, audit.wasm and merge.wasm, plus the t27c gen-ts constants.

  • Store. Postgres (queen_vault_store, one row, optimistic version) in the server. A file store serves the owner's local mode. Each row is an age file sealed to the vault's identity and to the owner's recovery recipient.
  • Crypto. The reference age tool (X25519, ChaCha20-Poly1305), started as a process. No crypto is written here. The Dockerfile installs age.
  • Workload auth. An Ed25519-signed request carries a time and a nonce, and the replay window comes from the spec. There is no bearer token.
  • Endpoints. POST /vault/<op> for lease, renew, revoke, names, put, rotate, import, export, grant, audit, break-glass, dedup, merge, class and bind. With the flag off, every one answers 503 and no table is created.
  • Audit. Each act is an event on the existing events bus (queen_event_log, stream vault), carrying names, scopes and hashes only.
  • CLI. trios-vault, covering init, key, grant, put, rotate, import --stdin --format dotenv|railway-kv|vault, dedup [--apply], export, run --scope S -- cmd and serve.
  • Runbook. trios/agent-server/docs/vault.md.

Done when

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions