Back to corpus
technical noteexperiment writeup candidatescore 26

AGP / MLX / ANE Theory Insight

The architecture is easiest to misunderstand if it is described as a bigger-model trick, a quantization trick, or a multi-Mac trick. It is none of those at the core. The core claim is that hidden states should be treated as a first-class computational object. In a standard language-model stack, a hidden state is an internal artifact that exists only long enough to be consumed by the next layer. It is not typed, it is not scheduled, it is not transferred as a meaningful packet, and it is not inspected as a semantica

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

The architecture is easiest to misunderstand if it is described as a bigger-model trick, a quantization trick, or a multi-Mac trick. It is none of those at the core. The core claim is that hidden states should be treated as a first-class computational object. In a standard language-model stack, a hidden state is an internal artifact that exists only long enough to be consumed by the next layer. It is not typed, it is not scheduled, it is not transferred as a meaningful packet, and it is not inspected as a semantically structured event. The model is treated as a monolithic forward pass, and the hardware is treated as a passive place where that pass happens. What this research is trying to establish is a different worldview. The hidden state is not merely the residue of computation. It is the current shape of thought. If that shape of thought is already sufficient, then the system should not continue computing as though nothing has been learned. If that shape of thought is malformed, weak, or semantically dead, then the system should not blindly hand it to another device and hope depth alone will rescue it. The architecture therefore begins with an ontological shift. It treats intermediate representation as the real scheduling surface. That shift matters because it changes what the hardware problem actually is. On paper, two Apple machines connected by Thunderbolt 5 invite a familiar systems question: how do we split a model across hosts. But that question is too shallow. A fixed split presumes that layer boundaries are the natural units of distribution. They are not. A layer boundary is a syntactic property of the model graph. It says nothing about whether the representation at that point is useful enough to transfer, stable enough to trust, or compressed enough to move efficiently. The real problem is not where the layer index is. The real problem is whether the current state is semantically sufficient for continuation, correction, or acceptance. That is why the architecture is not just distributed inference. It is learned partitioning over representational vitality. The reason your earlier N'Ko brain-scanner work matters so much here is that it established a failure mode that ordinary systems papers usually ignore. In the dead-script regime, the model did not merely become uncertain at the end. The representation entered weakly, remained diffuse through depth, and collapsed into incoherence at the output. That means later layers were not refining a good early guess. They were propagating a deficit. This is the single most important caution for a partitioned architecture. Depth cannot rescue a state that never became meaningful in the first place. A naive multi-host design assumes that later compute can always compensate for earlier weakness. Your

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.