Notes tagged
#trusted-ai
9 posts
- 2 min read
Claude Enterprise: the admin sees everything, deleted chats included
A Reddit thread confirmed it: Claude Enterprise admins can read an employee's full chat history, deleted and incognito included. The question isn't the feature — it's the architecture.
- 2 min read
Claude's watermarks: a signal, not proof
Anthropic will mark Claude's text with invisible watermarks. What a mark actually tells you — and why the real question is the contour, not the mark.
- 4 min read
The coach assistant: 32 sources, 70 questions, 77.4%
The corpus grew from 9 to 32 sources. The re-run scored 77.4% on 70 questions, with 10/10 grounding in the new module.
- 1 min read
One model, two circuits: own iron and cloud
We're a Yandex Cloud partner now. One Qwen3.6, two delivery circuits — own iron at Selectel and cloud via the Yandex Cloud API. Both 152-FZ-attested.
- 4 min read
60 coach questions: why niche AI needs its own benchmark
First basketball slice of LII Sport Bench: 60 questions, 9 public RFB Academy sources, and the first numbers for the RAG assistant.
- 2 min read
The boring bet: the frontier arrived where I've been building
I bet on verifiable AI — grounded in the client's corpus, cited, with an honest refusal — back when it sounded niche. I went through dozens of the year's biggest AI interviews: the frontier describes exactly that bet. And I have the one thing the voices on stage don't — a number.
- 2 min read
The full turn: the model is an API call
The full turn: the model is an API call for kopecks. Two circuits — public on CPU, sovereign on-site. The edge lives in the layer above the model.
- 2 min read
Picking the model for the hardware I have
Picking a model for the trusted-AI build on 24 GB. The bench beat intuition: a MoE beat a dense model twice its size; 'thinking' only got in the way.
- 2 min read
Do I even need my own GPU?
VRAM is tight, rental's rising. I sat down to pick a GPU — and the real question turned out to be whether I need one at all.