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

  • 9th September 2026

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.

Read more →
  • 18th August 2026

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.

Read more →
  • 4th August 2026

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.

Read more →
  • 29th June 2026

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.

Read more →
  • 25th June 2026

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.

Read more →