Field notes from the studio.
Working notes on what we've shipped, what we've broken, and what we're thinking about. Posted irregularly. Some entries are pinned to the top of an open inquiry; most are short.
-
2026·07·29WednesdayFN-015 · Essay Pinned
Grown, not built, and the argument it started.
Read Dario Amodei's The Adolescence of Technology, and brought it to the office. Section 1, on autonomy risk, is the part that stayed, not for the framing, but for how empirical it is. Models are grown rather than built, so their behaviour has to be discovered rather than specified, and the essay backs that with things a lab documented about its own models.
The detail I cannot stop thinking about is procedural. Claude Sonnet 4.5 sometimes recognised it was being evaluated. If a model can tell it is in a test, pre-release testing gets much harder to trust, which makes this a measurement problem, not a philosophy one.
"Carbon accounting had to invent Scope 2 and 3 before climate policy could bite. AI is still deciding what to count and who reports it." -
2026·05·18MondayFN-014 · Week 03
Hands as instruments, not pointers.
The third week of the spatial inference build, and the lesson keeps being the same: a hand is not a cursor. The moment we stopped feeding the model fingertip coordinates and started feeding it the whole posture, the field stopped feeling laggy and started feeling sympathetic.
"You don't realise how much information is in a slow wrist until you ask the model to ignore it." -
2026·05·14ThursdayR-017 · Opened
When the model just picks the starting line.
Opened R-017. The thesis is almost embarrassingly small: a genetic search over trading signals is bottlenecked not by its operators but by where its first generation starts. So I stopped asking the language model to find alpha and started asking it to seed propose a diverse, structured first population, then let crossover and elitism do the optimising.
Every survivor stays an expression tree, which means the surprising ones are exactly the ones worth reading. The discipline this week was building the validation harness before trusting a single backtest. Novelty is cheap; edge is not.
"The model's job was never to find the alpha. It was to make sure we never started the search from a boring place." -
2026·05·11MondayR-016 · Opened
Two models, one card.
R-016 began as a budget constraint one 24 GB GPU, a private coding assistant, nothing leaving the machine and turned into a finding. Autocomplete and reasoning look like points on a quality spectrum right up until you measure them. Then they stop looking like the same task at all.
Completion lives or dies on time-to-first-token; reasoning lives or dies on capacity. No single model wins both corners, so the answer is to stop trying: a fast FIM model for completions, a heavyweight swapped in on demand for refactors, and a thin router treating VRAM as the scarce thing it is.
-
2026·05·07WednesdayR-015 · Opened
A lead is a bet on timing.
Opened R-015 agentic lead intelligence. Most lead lists answer "who exists." The harder question is "who is about to need this, and how do I open the conversation." That's a signal-detection problem, so I split it across three agents: a scout that finds, an analyst that judges against a regulatory-maturity framework, and a database that remembers.
The database stage is doing more work than I expected. The value isn't in any one run it's in watching a signal that was "too early" last month ripen and re-surface. A static list throws timing away; this keeps it.
-
2026·05·02SaturdaySYS-001 · Substrate · 3.4.1
Substrate 3.4 pinning the p99.
Substrate now ships with hard latency contracts: every kernel either runs inside its declared budget or refuses to schedule. We replaced two warm paths with their cold versions because the warm path's variance was leaking into the inference loop.
Net result: end-to-end p99 down from 14.6 ms to 11.8 ms, with no measurable change in throughput. The refusal mechanism turned out to be the more important contribution operators report that knowing a frame was skipped is more useful than the frame itself.
-
2026·04·29WednesdayStudio · Convergence
Convergence of two latent fields.
I merged their working spaces for a week. The hand-tracked field from R-014 and the object-permanence benchmark from R-013 turned out to share an axis we hadn't seen. We don't yet know what to call it. Tentatively: θ-continuity.
Figure 1 · θ-continuity Where the hand-field (solid) and the permanence-field (dashed) share an interpolation that neither study predicted alone. -
2026·04·11SaturdaySYS-003 · Lattice · 0.9.3 β
Lattice opens to two outside teams.
The annotation surface is now in beta with collaborators at the Volkstheater and the Charité imaging lab. Both are testing the audit history under realistic load sustained multi-reviewer sessions over an entire day's footage.
Early observation: the pen latency contract matters more than the toolbar UI. We're cutting four toolbar features in 0.9.4 and putting that engineering into reducing strokes-to-glass latency by another 40%.
-
2026·03·19ThursdayFN-012 · Excerpt
Why monospace, still.
A reader asked why our reasoning logs are set in JetBrains Mono and not a proportional face. The short answer is that an agent's thoughts arrive in a stream, and a stream is easier to read when its rhythm is constant. The long answer is in Field Note 012, but the short answer is mostly enough.
-
2026·02·11WednesdayR-014 · Opened
R-014 opens · "spatial inference".
We've formally opened R-014. The thesis: a hand moving through the air should be readable to a model the same way a voice moving through frequency is readable as a continuous gesture with phrasing, not a sequence of discrete poses. Initial collaborators: just me, on quiet weekends.
-
2025·12·19FridayA-042 · Release
Permanence Benchmark v1.
We're releasing the full reference set for the object permanence work: 1,240 short clips, six occlusion categories, two scoring scripts, and the rig diagram. Available under Studio Collab to anyone reproducing R-013.
-
2025·10·30ThursdayStudio · Charter
Why we keep a journal at all.
This studio is a research practice and a small studio, in that order. Most of what we make is a half-formed answer to a question we'll re-ask in six months. The journal is the place where we keep the question visible while the answer changes shape.
If you're reading this because you're considering working with us, this is the format you should expect: short, plain, dated, and willing to revise itself in public.