Evidence record / paperclip

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-paperclip-canary-encrypts-sensitive-approvals-and-binds-retry-identity-to-actor-and-key-custody

Canary encrypts sensitive approvals and binds retry identity to actor and key custody. New sensitive tool-approval payloads encrypt arguments such as secretValue using the instance tool-action signing secret. Existing signed approvals are not rewritten. Sensitive request identities use the same key rather than guessable secret hashes. Default retry keys are versioned and actor-scoped; unverifiable old requests require reconciliation instead of replay. The configured signing secret takes precedence over a derived key from the persisted secrets master key. The October 23 implementation is absent from stable and beta but present in the October 24 canary and matching nightly source.

Channel: preview-or-beta. Half: both. Date: 2026-10-24.

Operator consequence: For 2026.1024.0-canary.7, back up and share the configured signing key or master-key fallback with the database and all serving processes. Plan for rotation invalidating retry matching, and inspect an old request’s prior effect before intentionally issuing a new explicit key. This improves custody for new records without retroactively rewriting history; no historical secret compromise is alleged.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-paperclip-canary-encrypts-sensitive-approvals-and-binds-retry-identity-to-actor-and-key-custody

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact