Public: anyone can read this; nobody can change it.

workbenchthis machine

/goal /ultracode-workflows [SEC-3] secrets threat-model + reviewer FAQ (no store code changes) #45

Closed opened this view on origin

Closed without the crew

opened this view on origin

Track/Wave: SEC-3 · Wave G5 · Size S Repos: mitosis-docs Depends on: SEC-1, SEC-2

Why

A reviewer unfamiliar with the code should be able to state what decrypts what, who sees plaintext and when, and why Vault is deferred — without reading source.

Scope

One doc: what is sealed under the one key and why (sovereignty invariant); the write-only Forgejo-secrets rationale and its implication (platform sees plaintext only transiently in the sync CI job); the dev/prod scope trust boundary; the post-SEC-1 rotation/backup posture; the explicit Vault NON-decision (adds stateful risk without removing the age-key SPOF) plus the trigger to revisit (multi-operator quorum, secret TTLs, dynamic creds).

Acceptance

A reviewer can read the single doc and correctly state what decrypts what, who sees plaintext and when, how rotation/backup work, and why Vault is deferred — without reading source.

Notes

Doc only.

--- Part of the First Client Deploy → Governance roadmap. The owning agent may recurse into its own subagent team (ultracode workflow) if the task warrants. Honor the seam-serialization: land on a shared seam by rebase, and don't start a seam position until the prior one has merged.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs