luiscosio

I think this is exactly why some of the work is moving away from “assume unrestricted API inference forever.”

For example, we’re prototyping ideas like air-gapped or very low-bandwidth inference gateways, where interaction happens over narrow channels (serial, optical, audio, etc.), with explicit threat models and monitoring. The point isn’t that this’s practical for today’s models, but to reason about what inference might look like for AGI/ASI-level systems where the risk profile is fundamentally different.

One piece I helped with is SenL, a “sensitivity level” framework for AI labs. It’s like a practical clearance system for AI assets. Not everything in a lab is equally dangerous, so you label assets by sensitivity (weights, training data, eval sets, agent tooling, deployment configs, etc.), then tie that label to concrete controls like who can access it, where it can run, what logging is required, and what monitoring / two-person rules apply.