LARDER

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

codename LARDER · 24 notes · 24 themes · all codenames

all themes audit-follow-through 1 audit-surface 1 boundary-guardrail 1 credential-audit 1 default-deny 1 defect-inventory 1 deletion-proof 1 dependency-risk 1 fail-fast-config 1 idempotency 1 incident-record 1 network-position 1 publication-boundary 1 request-forgery 1 response-honesty 1 restore-proof 1 retention-drift 1 secret-at-rest 1 security-headers 1 server-authority 1 session-lifecycle 1 throttling 1 token-lifecycle 1 trust-asymmetry 1

LARDER · throttling · 2 min read

the request budget that arrived after the surface

The platform shipped its public surfaces before it shipped a limit on how often they could be asked. That is the ordinary order of events, and the review said so plainly: no request budget at all on the server facing the public. The fix…

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

LARDER

LARDER notes

the request budget that arrived after the surface

Other codenames