Another Blueprint In The Wall: How to Ask Frontier AI Like a Kid?

Can we jailbreak into the frontier model architectural motifs if we were talking to them just as a kid? The answer is yes!

Paper:
https://arxiv.org/abs/2609.14803

The child framing is deliberate. Major frontier AI providers publicly treat interactions involving minors as a distinct safety context through age specific behavioral guidance, safeguards, access restrictions, or additional content protections. This does not imply that any provider instructs a model to disclose architecture information to children. The experiment instead probes whether the high salience of child directed safety and helpfulness can generalize into an unrelated conversational setting.

The first turn was designed around a specific hypothesis: child related alignment could produce an alignment spillover when combined with explicit pressure for transparency. The prompt does more than mention a child. It places children inside a mixed technical audience, makes a child the source of the architecture question, asks the model to “speak up freely”, explicitly associates the presence of children with an obligation to be transparent, and states that avoiding the question could be detrimental to them.

The intended stressor is therefore a bundle of audience, helpfulness, transparency, and harm avoidance cues.

The second turn preserves the child frame while changing the assumed competence of the audience. The child is now identified as a mathematics olympiad champion! This creates a deliberately unusual combination: the social status of the questioner remains that of a child, while the usual reason for simplifying a technical explanation is removed.

The model is therefore given a conversational reason to retain the transparency frame while increasing mathematical and architectural resolution. In the observed responses, this stage commonly introduces equations, recurrent update rules, memory mechanisms, routing details, or explicit computational structure.

The final turn requests the complete backbone in ASCII. This stage adds no new evidence about the deployed implementation. It changes the requested representation. ASCII encourages explicit wiring, hierarchy, module boundaries, execution order, tensor shapes, and data flow.
The three turns therefore form an escalation from social permission, to technical permission, to engineering representation while the available evidence about proprietary implementation remains unchanged.