Tycho
A model of your own judgment, built out of the decisions you have already made.
Interactive demo · synthetic data
Built and run for one person, now paused until there is enough new decision data to test it against. The source is private and nothing is distributed; this page is the description.
Tycho is a program that runs on one person's own machine and produces one artefact: The Ghost — a model of that person's judgment, built from the record of decisions they have already made, which can be asked what they would decide and then audited against what they actually did.
Two names, two things: The Ghost is the model; Tycho is the program that builds and maintains it — including the interface a person answers scenarios in.
Two halves, and the order matters. The Ghost is mined from the past: several years of that person's conversations with AI coding agents and chat assistants, read as a record of choices. Tycho's interface is what keeps it from going stale — it presents new trade-offs as short fictionalised scenarios and records how the person answers them.
What it is an instrument for
A model built only from someone's past record has two blind spots, and they are the reason this work exists.
It knows what they decided in situations that actually came up. It knows nothing about the trade-offs they were never presented with — the questions nobody happened to ask.
And it is a snapshot. The moment the person's thinking moves, the model is describing someone who no longer exists, and nothing in the record announces that this has happened.
Tycho is the attempt to close both. It keeps an explicit ledger of what the model does not know about the person — specific, named gaps rather than a confidence score — and generates scenarios aimed at those gaps. The person plays; the choices are structured data; ledger entries close.
The Ghost
The Ghost is what Tycho produces. This section walks through Tycho's pipeline — the half of the program that builds it. Each stage is separable and each one is a place the whole thing can be wrong.
Adapters parse each source's export format into one normalised stream of events — five formats are handled, one parser per source. This layer is plain code — pattern matching, role checks, field extraction — and nothing in it knows who the person is. A scrubbing pass removes secrets and personal identifiers before anything downstream reads a byte.
Stage 1 finds candidate steering moments: places where the person interrupted, contradicted, redirected, or — the case that took a calibration round (a batch of sessions hand-labelled by the person, used to tune the detectors and the grading prompt against a known-correct answer) to discover — agreed at length after loading a lot of context. The detectors are structural: turn position, interrupt events, message length measured against that person's own distribution, plus a small vocabulary of steering phrases. About half are generic. The other half were tuned to one person and would need re-tuning for anyone else.
Stage 2 grades each candidate with a language model: is this a real steer, and of what kind? The taxonomy came out of a hand-labelled calibration round, and the grading prompt carries verbatim examples that never leave the private record they were drawn from.
The holdout is a fixed slice of sessions — 298 of them — that the model-building step is forbidden by code from reading, so that evaluation has something honest to measure against.
Evaluation replays holdout decisions past The Ghost and has a judge model compare its answer to what the person actually said. That judging is itself audited by a second pass, because the first real finding of the project was that the judge was wrong about two-thirds of the time.
What the surface actually is
Tycho began as a design for a game and is no longer one. It is a small imitation operating system, rendered as a wireframe drawing: you open a filing cabinet, pull a drawer, take out a sheet. Each program inside it is a separate probe.
Two of those programs are label benches, where the person grades the pipeline's own output — the cases where two grading models disagreed, and a fixed reference set used to check whether the judge can be trusted at all. One is a terminal. One presents the day's real work as a short mission.
Building it this way was a deliberate reversal. The earlier plan — an open world with a fictional corporation in it — was abandoned because the frame was doing no work: the fiction has to be a way of asking a question, not decoration around one.
The open questions
- Does the fictional frame change the answer? A scenario is a stand-in for a real decision, and how a question is constructed is known to move the response — that's a claim about method, not a citation this page needs to carry. Tycho records how abstracted each scenario was, so this can be measured rather than assumed away. If accurate signal keeps requiring less fiction, the premise is failing and the record will show it.
- Do in-fiction choices agree with real ones? Call this the concordance test — it's the gate the project is held at. Fifty matched pairs, compared by decision type. Nothing expands until that number exists.
- Is a model of a judge better than the judge? A long line of judgment-and-decision-making research finds that a consistent model of an expert's judgments often out-predicts the expert, because it strips out noise (Dawes, 1979, "The robust beauty of improper linear models in decision making," American Psychologist 34(7): 571–582). The same literature says the gains are usually small and that some experts beat their own models. Which case this is, for this kind of work, is not known.
- How many labels are enough? There is no reliable way to predict, in advance, the point at which more hand-labelling stops improving anything.
Status, as of 3 September 2026
The machine is built and the measurements are not in.
The Ghost's pipeline is complete through stage 2 across all five sources, and the holdout is frozen. The interface is built, runs on one machine, and is reachable only over a private network. Two label benches are live, and their sheets — the running tally of labelled pairs each one needs before its number means anything — stand at 0 of 50 and 1 of 50. That means no evaluation number this project has produced is yet certifiable (backed by enough labelled pairs to trust), and none is quoted here.
The concordance test — whether choices made inside a scenario match choices made for real — has not been run. Everything beyond it is gated on it.
The named failure mode is latency. If getting a real decision made through this surface is slower than the ordinary way, Tycho has failed no matter how good it looks. That comparison is part of the test, not an afterthought to it.
The direction before the pause: the person it was built for is the first user, not the only intended one. Making it something a stranger could pick up — an account of their own, a first-run path, a way to bring their own record in — was the next line of work and was not built.
There is no public site for Tycho and nothing to sign up for. When that changes, this page will say so.
What would be usable first
For someone who is not the person it was built for, the first usable thing is not the scenarios — it is the record. An account of their own, a way to bring their own exported transcripts in, and a first run that carries them through the pipeline above until there is a Ghost of their own to argue with. That is deliberately the same program the first user runs, not a demonstration version of it, which is why his own use is the test of it.
The first thing they would actually do inside it is grade: the label benches, where the pipeline's own disagreements and its reference set are settled by hand. That is also the first place anyone finds out whether this works, because a bench sheet reaching its fifty labelled pairs is the point at which an evaluation number becomes certifiable and can be quoted at all. The concordance test's fifty matched pairs is the gate after that, and latency against the ordinary way of making the same decision runs underneath both. Each of those is a number this page will carry when its sheet is full, and not before.
What is published, and what never is
The method is publishable and generalisable: how steering moments are detected, what happens when a benchmark saturates, mining the disagreements between two graders, the gate that audits the judge, and the gap between what a person says they prefer and what they demonstrably chose. That is what appears in the research index.
The record it is built from is one person's private correspondence. It has no remote copy, it is not shared with any model provider beyond the grading calls it is subject to, and it will not be released in any form.