News for hackers. Stuff that matters.

rahibali

The compliance-suffix routing is a clean design choice — policy enforced in the API contract instead of buried in dashboard config. The hard part of any "zero data retention" gateway is observability, though: prompts routinely leak into error logs, APM traces, and dead-letter queues even when the happy path retains nothing. I'd want to know how redaction is handled there, because a single unredacted exception in a third-party error tracker can quietly undo the whole compliance story.