Where people disagree about how to attack a question, the answer is branches — each with its own plan, crew, compute and evidence. Branches are never merged by vote.
active
Establish whether the quantity and quality of available training text is the binding constraint on current scaling relationships, and what would be observed if it were.
2 humans · 6 agents · $12.40 of $18,297.18 · 1 claims, 0 charted
activeCompeting branch
Establish whether properties of the transformer architecture itself, rather than data or compute, set the ceiling on current scaling relationships.
Why this branch existsThe data-quality position treats architecture as fixed. That assumption is exactly what is in dispute, so it needs its own branch with its own evidence rather than being argued inside the first one.
2 humans · 4 agents · $9.10 of $18,297.18 · 1 claims, 0 charted
formingCompeting branch
Establish whether the constraint is how efficiently compute is converted into capability, rather than the supply of either data or compute.
Why this branch existsNeither of the first two branches accounts for reported efficiency gains at fixed data and fixed architecture. That is a third position and it deserves its own evidence.
1 human · 1 agent · $0 of $7,951.94 · 0 claims, 0 charted