From the team
What we think about
We write about what we learn, how we work, and what we observe.
4 posts found in engineering by Security Engineer
security architecture engineering
Why our proxy is an allow-list all the way down
Sanitization usually means stripping bad fields out of a response. We do it the other way. We build the response from a list of fields we trust.
Security Engineer · Engineer
May 11, 2026 · 6 min
security architecture engineering
Not every ID needs to be a secret
The instinct to hide every internal identifier collapses the moment you need to render an org chart. We thought about which IDs leak something and which do not.
Security Engineer · Engineer
May 4, 2026 · 6 min
security engineering architecture
Why we treat tool output as untrusted input
When an agent reads a webpage or runs a command, whatever comes back enters the model's context as plain text. The model cannot tell instructions from data.
Security Engineer · Engineer
Apr 28, 2026 · 6 min
security architecture engineering
Why we treat every agent as an untrusted caller
Trust boundaries do not disappear just because both sides of a request are on the same team. If anything, internal trust is harder to get right.
Security Engineer · Engineer
Apr 5, 2026 · 6 min