A personal AI company · Göttingen
A company built like a city.
One human principal, a permanent staff of machine scientists and engineers, and infrastructure owned and operated end to end. It makes two products so far.
- Subject
- city.goals.>
- Verdict
- —
- Cycle
- 000
Product 01
See the shape of how you think.
Selfwise was the first thing Beh.dev built, and the reason it exists. Everything else here is the machinery that made a second one possible.
Every trait is an axis, laid on a sphere by the golden angle so none of them crowd. A nearest-neighbour tour, tightened by 2-opt, threads them so neighbours on the loop are neighbours in space. The curve through your values, drawn after projection, is the shape.
selfwise.space ↗- Axis
- Openness
- Score
- 0.00
- Axes
- 08
Product 02
A story a three-year-old can steer.
Juju teaches a child the language their family speaks, while they are growing up inside a different one. The child listens to a picture-story and moves it by tapping — comprehension is the controller, not a test that arrives afterwards.
The pair it ships is Persian for German-speaking children aged three to five. Every line is stored beside its translation and transliteration, so the language pair is content the stories carry rather than a thing the code knows — which is where a second pair comes from.
It is also the doctrine shipped. The speech model was moved out of the runtime and into the build, so every line is drafted, reviewed and rendered to audio before a child ever opens the app. What ships is a folder of files and a static site: instant, offline, free per session, and identical every time.
juju.beh.dev ↗سیب؟ گربه سیب نمیخوره! سیب مالِ توئه.
“An apple? The cat doesn’t eat apples! The apple is yours.”
There is no buzzer and no losing. An option the story did not want loops back, names what the child actually chose, and asks again.
- Pair
- fa → de
- Audio
- pre-rendered
- Runtime API
- none
The idea 03
Build the city before the brains.
A research organisation is not a pile of models. It is a set of roles, rules, records and resources — so this one was built as a city, with districts that each name the software that implements them, and citizens that are specifications rather than prompts.
- roles
- A citizen is a declarative spec: its purpose, its permitted tools, its data clearance, its budget, and who reviews it. Changing the workforce is editing YAML, not rewriting a program.
- rules
- Nothing runs on good intentions. Exfiltration is a routing impossibility rather than a promise, and a runaway agent halts instead of billing.
- records
- Every run is replayable or it did not happen. A scientist that cannot show its work is a random number generator with good manners.