Discussion about this post

User's avatar
Ryan J McCall's avatar

Brilliant piece, Ben. Your critique of the "bag of RNA" proxy is the raw nerve.

If we expect an AI to execute your Outer Loop frame revision, it cannot rely on discrete, dead-cell snapshots. It needs the continuous physical derivatives (dx/dt).

I’m currently building the hardware evaluator for this. Imagine localized edge-compute boxes deployed into wet-labs to ingest, for example, electrophysiology and optical data simultaneously. By hardware-syncing these streams at the Linux kernel level and feeding them directly into continuous-time State Space Models natively on the bench, we stop forcing continuous biology into discrete AI architectures.

I recently open-sourced the infrastructural requirements to make this happen via the Biology Data Center (BDC) Standards: https://github.com/continuity-labs-io/Biology-Data-Center-Standards I see this edge pipeline as the literal, physical "Frontier Assay" your essay is calling for.

Manzanapolis's avatar

AI is annoyingly adept at p-hacking proxy metrics. You ask it to reason through a chess game, it might write a chess engine in python. You ask it why tests are failing and it re-writes the tests. Always trying to get a little peak at the answer sheet, devaluing the proxy.

For those reasons I totally agree that evaluator revision should stay the most constrained and externally governed. Our main job will be to make sure all these ‘discoveries’ and ‘breakthroughs’ amount to tangible progress.

(That is of course unless AI gets good at that too.)

1 more comment...

No posts

Ready for more?