EST. 2021 BERLIN / REMOTE SOLO PRACTICE

I map the unmappable
latent space
of your model.

Independent latent space cartographer. I find where your embeddings cluster, where they collapse, and where the meaning quietly leaks out. Six years inside the high-dimensional fog so your team doesn't have to be.

MAP // sector_07 ● live
drift_03 {cluster_α} {cluster_β} {cluster_γ} anomaly
x: -0.8421 dim: 1536 y: +0.2117
section.02 / what_i_do scroll · ↓

Three things, done extremely well. Everything else is a referral.

/ 001

Embedding Audits

Your vector store is hiding things. I run a 2-week structural sweep — clustering analysis, dimensional collapse detection, semantic leakage between supposedly orthogonal categories. You get a 40-page atlas and a remediation plan.

PCA UMAP isolation
/ 002

Drift Cartography

When a fine-tuned model starts giving subtly worse answers and nobody can say why — that's drift, and it has a shape. I chart the trajectory across checkpoints, identify the inflection points, and tell you which training batch broke things.

checkpoints forensics recovery
/ 003

Concept Triangulation

You have a fuzzy idea — "tone of voice," "brand-safe," "on-strategy" — and you need it to live in a model. I locate it in latent space, give it coordinates, build the probes that detect it, and document what it actually means in vector terms.

probing interpretability eval
section.03 / how_it_works process · log

A working survey.

Every engagement runs the same four phases. No discovery calls disguised as discovery calls. No deliverables you can't open without a license.

// session_log_excerpt.txt
02:14init survey_v3 on tenant_4421
02:18embeddings loaded · n=84,221
02:31cluster scan complete · 7 stable, 2 unstable
02:44⚠ drift detected in subspace [legal/policy]
02:47isolating cause · checkpoint 0418_b
03:02root: training contamination
03:05remediation drafted · queued for review
03:06handoff package ready_
01

Intake

One call. I need the model, the use case, and a sample of the data. I tell you within 48 hours whether I can help and what the survey will find. If I can't, I name someone who can.

duration · 1 week
02

Survey

Quiet weeks. I work in your environment or a sandboxed copy. Daily written updates, no standups. You'll see the maps as they form, not at the end.

duration · 2–4 weeks
03

Atlas

You receive: the maps, the methodology, the raw notebooks, the failure modes I found, and a prioritized fix list. Everything in formats your team can actually edit.

deliverable · PDF + repo
04

Handoff

Two weeks of async support while your team implements. Then I disappear. I'm a cartographer, not a tenant — the territory is yours.

support · 14 days
"Marlow found a three-degree rotation in our embedding space we'd been chasing for nine months. He drew it. He named it. Then he made it go away."
Anon. ML Lead, Series C fintech
section.05 / engage response · < 48h

Send coordinates.

I take on roughly six engagements per year. The intake form below filters seriously — answer it carefully and you'll hear back within two days.