Hi, Iâm Kit Kyo â a full-stack engineer who works across the whole stack: product code, DevOps, and agent development (building LLM-driven agents and the plumbing around them).
Right now Iâm putting serious time into machine learning and infrastructure â going from âship the productâ to understanding the systems underneath. This blog is where I keep the notes, experiments, and write-ups from that journey.
Recent posts below â or read more about me.
Kit Kyo
A shipped exit rule picks good steps â and still costs answers
A recurrent-depth language model ships six ways to stop early. Measuring one of them at its own default: it selects better stopping points than chance, and on one task it still loses accuracy on the answers. Both are true, and separating them needed two different experiments.
Flat where the data isn't
A regime where the optimizer is not the bottleneck and cannot become one â how to recognise it, why every optimizer-side fix I tried did nothing, and why the one data-side intervention that appeared to work had to be withdrawn.
SSI, scaling, and the flywheel nobody named: three acts of an investigation that corrected itself
A three-act investigation into Safe Superintelligence Inc. that kept overturning itself: the âstraight shotâ thesis is elegant but rests on an unverified premise; scaling didnât die, it fragmented into four axes SSI canât access; and the data flywheelâs reward signal is measurably broken â which turns SSIâs âno productâ from fatal weakness into audit qualification. Each actâs evidence almost closed the case; each layer of depth reopened it.
Cheap factors, four domains: a scorecard â and why 'no single factor works' isn't 'no signal'
We put interpretable, locally-computable factors from four mechanistically-different domains â software-defect prediction, paper acceptance, AI-text detection, and a world-model physics proxy â on one shared per-factor scorecard. Predictive power has a domain-dependent ceiling, the factors donât transfer across domains, and a single-factor reading nearly had us call an industrial benchmark a âcollapseâ when the signal was just multivariate.
Does a multi-agent panel beat a single LLM at evolutionary code search? (We tested it. No.)
We replaced the single-LLM mutation step of an AlphaEvolve-style evolve loop (OpenEvolve) with a proposerâcriticâaggregator panel and tested it rigorously across three problems. It never won â equal on easy optimization, significantly worse on hard optimization (p=0.01), and on correctness-gated ARC it cracked nothing a single call couldnât. A clean negative result, with the baseline/ablation harness that makes it trustworthy.