People who build the builders
Agent harnesses, code generation, program analysis, verification, developer tooling.
for collaborators
For people improving how machines design, build and evaluate software. Especially people who will tell us we are wrong.
who this is for
Agent harnesses, code generation, program analysis, verification, developer tooling.
How do you know a change was an improvement? Our hardest question.
A position with a cost beats an introduction.
open lines of work
| line of work | state |
|---|---|
| saying what is true about a system once | running |
| rules that refuse rather than rules remembered | running |
| more than one independent reading of a hard question | running |
| judging a change to how we work | building |
| quality read from the source | building |
| knowledge you can actually reach | ambition |
so nobody has to ask
the next step
And what you are working on. An argument with a position in it is worth more to us than an introduction.
Contact routes publish at launch.