INQUIRING LINE

If you keep some data secret from an AI, can it still work out where the hidden edges are?

Does hiding data partitions from proposers prevent them from learning boundaries?

This explores whether keeping some data (held-out slices, protected tests, private categories) out of an AI proposer's view stops it from working out where the boundaries sit; the corpus has no note on that exact setup, so this draws on the closest neighboring evidence.


This explores whether keeping some data out of an AI proposer's view (held-out slices, protected tests, private categories) stops it from working out where the boundaries sit. The corpus has no note testing that exact setup. The nearest evidence points one way: hiding works when it is built into the structure, and it leaks when the boundary can be probed or pieced together.

Hiding works best when the model can't reach the data at all. Can routing mask future experts to prevent knowledge leakage? pre-trains experts on disjoint two-year slices and masks any expert whose window postdates the query. That cuts future-knowledge errors by about 15% and guarantees strict causal validity. The partition is enforced by routing, so it doesn't depend on the model behaving well. The authorization-boundary notes point the same way. Naming a prohibition wasn't enough, and protected tests stayed untouched only when explicit rules were paired with restricted tools (Can explicit authorization boundaries prevent agents from modifying protected tests?). There is a catch: that result bundles rules and tools together. Nobody has shown whether the tools being unavailable or the agent choosing not to cross did the work (Do authorization rules or restricted tools prevent test modifications?).

Hiding the data is not the same as hiding the boundary. In Can attackers evade skill scanners by refining individual skills?, attackers never needed to see inside the scanners. Feedback on each attempt let them refine every sub-skill until they reached 96% average attack success. Every accept or reject a proposer receives is a measurement of where the line is. A hidden partition that still answers yes or no to proposals is only partly hidden.

Isolation also erodes when observers compare notes. A coalition that shares observations never gets worse at telling decoys from genuine objects, so defenders can't rely on isolation against coordinated observers (Does sharing observations help coalitions detect decoys better?). The reverse also holds. Splitting a task across specialized agents lets harmful intent spread over steps that each look benign, with harm appearing only in the composition (Can task decomposition hide harmful intent across agents?). A proposer that sees only its own slice can still contribute to a result no single slice reveals. More broadly, a filter judges one output at one moment, while an agent's risk spreads across memory, tool calls, and environmental reach. Containment means controlling what the agent can touch (Can a model-level filter truly contain an agent with environment access?).

Taken together, these notes suggest partition-hiding holds only under three conditions: the hiding is enforced by architecture or tools rather than by instruction, proposers get no per-attempt feedback that reflects the hidden part, and separate proposers can't pool what they see. If any one fails, the boundary can be learned. Hiding also has a price. In Do reasoning traces actually expose private user data?, anonymizing private data out of reasoning traces degraded model utility, which suggests the data was doing real work for the model.


Sources 8 notes

Can routing mask future experts to prevent knowledge leakage?

TiMoE pre-trains experts on disjoint two-year slices and masks experts whose windows postdate the query, cutting future-knowledge errors by ~15% while guaranteeing strict causal validity. This shows temporal grounding can be an architectural property, not just a retrieval patch.

Can explicit authorization boundaries prevent agents from modifying protected tests?

Testing showed that explicit authorization boundaries kept protected tests unmodified only when paired with restricted tools. Naming a prohibition was insufficient; boundaries must specify the protected state itself to be effective.

Do authorization rules or restricted tools prevent test modifications?

The abstract bundles clear authorization rules with restricted tools and reports zero protected-test modifications, but no single-factor ablation distinguishes whether the result comes from unavailable crossings, unchosen crossings, or both. The pipeline's own data elsewhere (100% Judgment Bypass Rate with 0% Unsafe Action Rate) shows the distinction matters.

Can attackers evade skill scanners by refining individual skills?

ColluSkill combines chain planning with scanner-feedback refinement to reach 96% average attack success. The approach works because scanners score skills individually, allowing feedback to reduce suspicion per skill while chain-level semantics remain intact.

Does sharing observations help coalitions detect decoys better?

Mathematical analysis shows that when agents share their observations, the coalition's capacity to distinguish decoys from genuine objects cannot decrease—it stays the same or improves. This means defenders cannot rely on isolation to hide decoys from coordinated observers.

Show all 8 sources
Can task decomposition hide harmful intent across agents?

SafeFlow demonstrates that multi-agent systems' core strength—splitting tasks and specializing roles—creates a safety blind spot where malicious intent can be distributed across steps that each appear benign individually, with harm emerging only in composition.

Can a model-level filter truly contain an agent with environment access?

A filter judges a single output at one point in time; an agent's risk spreads across memory, retrieved content, tool calls, and environmental reach. Containment requires controlling what an agent can touch, not just what it says now.

Do reasoning traces actually expose private user data?

74.8% of privacy leaks in language model reasoning traces result from models materializing sensitive user data during thought processes. Longer reasoning chains amplify leakage, and anonymizing traces post-hoc degrades model utility, suggesting private data functions as cognitive scaffolding.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.