Hatteria Labs

AI & machine learning research

Research that survives its own controls.

Hatteria Labs studies how language models work from the inside. We publish what we find — including the results that failed — and build products on the parts that hold up.

We measure

Empirical work on model internals: memory compression, weight structure, quantisation, hybrid architectures. Every claim carries a null control it has to beat.

We publish

Methods, thresholds and negative results, in the open. A rejected hypothesis is a finding — it is where most of the value in this work actually sits.

We ship

Three products in production, built and run by the same two people who do the research. What we learn goes into software people pay for.

Research

What we are working on

Our current line of work asks how much of a transformer is redundant — and answers it by trying to remove things and measuring what breaks.

All publications →
QuantizationKV cache

KV Cache Quantization Asymmetry

KV cache quantization is the only pain-free memory saving the project found for long context. A sweep over bits, granularity, and the K/V ratio on GPT-2 showed that keys need more bits than values. Porting the test to Qwen3.5 exposed a measurement-location artifact and showed the asymmetry is regime-dependent, not universal: keys win decisively below ~4 effective bits, while above ~5 the choice is domain-dependent.

GPT-2 small · Qwen3.5

Model compressionTransformers

Shared Functional Bases Across Transformer Layers

A nine-step chain of tests asked whether GPT-2's transformer layers share enough parametric structure to store one common basis with a cheap per-layer description of the deviation. Sharing in raw weights did not hold; sharing in the functional space of input activations did, but only through fine-tuning, never through analytic projection. Attention matrices tolerate compression well (9.6x at a recoverable cost), while MLP layers structurally resist it.

GPT-2 small · GPT-2 medium

Products

Software we build and run

Each product is live, paid for by its own users, and operated on our own infrastructure. They fund the research and keep it honest about what works outside a benchmark.

More about the products →

torumata.com

An audit for the era of AI search — see how language models actually read your site.

What it does

  • A readability score for AI, broken down by category, so progress is measurable rather than felt
  • An analysis of which questions the site can actually answer, run through a language model
  • A site tree with flags marking the pages where the problem sits

For: Site owners and marketing teams whose traffic is moving from search results to chatbot answers.

AIDJ

Live

aidj.cloud

The DJ that runs your party on autopilot.

What it does

  • Guests request a track from their own phone after scanning a QR code, with nothing to install
  • A spoken DJ introduces the track in its own synthesised voice and crossfades into the next one
  • When requests dry up, the queue keeps filling itself from the mood of the event, so the room never falls silent

For: Weddings, company parties, bars and clubs, birthdays and school events — anywhere the music matters and nobody wants to babysit a playlist.

slidify.cloud

Your guests' photos, live on the screen.

What it does

  • Guests scan a QR code and upload from a mobile browser — no app, no account, nothing to explain
  • Photos reach the projector or television within seconds of being taken
  • The slideshow skips what it has just shown and favours pictures nobody has seen yet

For: Anyone hosting a wedding, a celebration or a company event who would rather collect the evening's photographs than chase them afterwards.

How we work

Rigour is the product

Most of what looks like a result in machine learning is a measurement artefact. Our process is built around catching our own.

Every number has a null beside it
An observation is printed next to the control that randomises the structure it claims to depend on. If the null keeps up, the claim is dead — and it gets written down anyway.
Thresholds are set before the measurement
Decision criteria go into the docstring ahead of the run, as named booleans rather than prose. A verdict written after seeing the data is not a verdict.
Corrections stay visible
When a later replication overturns an earlier conclusion, the correction is published next to the original. Two of our own findings have been reversed this way.
The end-to-end effect is the only score
Captured variance, reconstruction error and attribution scores all mislead. We measure what the change does to the model itself, on held-out data.

Working on something adjacent?

We take on a small number of research and engineering engagements alongside our own products — mostly where a question needs measuring properly before anyone builds on the answer.

Get in touch