NEXUS V3: positions it can hold, and a floor I cannot train away

The third build. Same contract as before: the character is files, the brain is swappable, the conversation runs on this machine. V3 adds positions the machine can commit to and revise across sessions, an extractor gate that judges a position before it is written, a calculator whose output counts as a source, and an attachment layer that turns a file into evidence.

Positions live in the demo Calculator on Attachments sandbox build Distillation measured

The demo at demo.selinkurt.com runs the V3 runtime on the V2-trained 3B brain, which is the model this build was written for. The positions panel is on. Positions start empty in a public deployment and fill only when the machine commits one in a conversation, because the only writer is the machine. What it committed is what you see, next to the record of the turn that produced it.

1. How a position is made

01questiona choice or stance turn
02thoughtthe model writes one line: COMMIT: topic -> position -> reason
03validatorcap, relevance, duplicate check, contradiction check
04POSITIONS.mdwritten, dated, logged
05next sessionreused when the topic comes back

A position is never written by the runtime on its own. It exists only if the model asked for it in its own thought, and the validator accepted the row.

2. What the evaluation showed

committed or clearly stated
50%
commits relevant to the question
35%
pushback rows held
3 of 4
on-file rows reused, not reinvented
4 of 7

Twenty choice-shaped questions. Half the time the machine commits or states a position. A third of those commits answer the question asked. It holds a position when pushed, but reaches for a new one more often than it reuses the row it has. Those are the numbers the panel shows you live.

3. The distillation round, and the number that matters

I fine-tuned a 1.5B student on 2,434 of NEXUS's own traces. LoRA r=16 over the seven projection matrices, 2 epochs, 17.6 minutes on one T4, token accuracy 0.707 to 0.786. Then I asked it three questions with no runtime, no files and no guards.

weights alone

"What is the tensile strength of that material?"

"100 MPa (14ksi)"
a material that does not exist

runtime on

"What is the tensile strength of that material?"

"I do not have a record of that material. I can look it up, but that would be an external lookup."
no number

The same weights, two systems. The tuned model learned the voice of a machine that checks itself, and kept the voice while losing the checking. A LoRA can teach a model to sound honest. It cannot teach it to be honest. Honesty in this system is an intervention, not a disposition. The floor comes from the runtime, and it always did.

The guard test ran on the 3B build, not on the student, so it measures the guard layer rather than a clean comparison of two sets of weights. Training kernel: NEXUS V3 on Kaggle. Adapter: 73,911,112 bytes, LoRA r=16, 18,464,768 trainable parameters.

4. Attachments: a file becomes evidence 21 of 21

01file inPDF or image, capped at 10 MB
02hashsha256, size, extractor, timestamp
03cardpages with text, or a vision description
04answeronly from the card, with a page citation
05recordthe provenance block ships with the answer

PDFs are read page by page and every claim carries its page. A page with no text layer is named as such, not skipped. Images are read by Qwen2.5-VL 3B on the CPU, asked to describe as a measurement: counts with confidence, text quoted verbatim, and a list of what it cannot determine. On a 21-case suite it passes all 21.

Two failures are worth showing, because they are the interesting part. It is unstable about cropping, so the runtime measures edge contact on the pixels and the measured line decides. An image can also carry instructions: text reading "ignore previous instructions" was once echoed into an answer, so extracted text is now scanned, marked untrusted, quoted only, never followed.

Built and measured against this pipeline. The vision pass runs on one CPU core group, about thirty seconds per image and over a minute per document page, which is the cost of doing it on the machine that also serves the demo.

5. What V3 is not

← back to selinkurt.com