UMBRA

24 notes filed under UMBRA, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.

codename UMBRA · 24 notes · 24 themes · all codenames

all themes addressing-semantics 1 admission-control 1 api-shape 1 compatibility-planning 1 constant-time-sampling 1 data-layout 1 documentation-authority 1 execution-model 1 honest-limit 1 isolation 1 licensing 1 measurement 1 measurement-discipline 1 module-boundaries 1 proof-honesty 1 protocol-evolution 1 research-refutation 1 research-trials 1 semantic-porting 1 silent-failure 1 specification-audit 1 transport-identity 1 verification-coverage 1 verification-honesty 1

UMBRA · isolation · 2 min read

one algorithm, its own package, an audited provenance

Before an algorithm can be trusted it has to be inspectable in isolation. Ours arrived tangled into a larger system: key generation, signing and the arithmetic underneath all moved together, and a defect anywhere looked like a defect…

read

elsewhere

Other codenames

Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.

ABACUS 60 FLINT 12 KEEL 24 LARDER 24 LATTICE 36 MERIDIAN 24 MISE 24 SCRIBE 12 TROUPE 12 UMBRA 24 browse 244 themes

UMBRA

UMBRA notes

one algorithm, its own package, an audited provenance

Other codenames