← all work

case-study / annotation-platform

Image annotation & QA platform

CONFIDENTIAL CLIENT · PRODUCTION · 2025–2026

Reference available under NDA.

CONSENSUS REVIEW FLOW · ANONYMISED

many reviewers → weighted consensus → one trusted label · ~1200×600

A model is only ever as good as the labels under it, and labels are where most computer-vision projects quietly fall apart. When dozens of people are tagging enormous sets of imagery, they disagree, they drift, and there's no defensible way to say which label is the true one. The dataset that's meant to train a model becomes the least trustworthy thing in the building.

I designed and built — solo, start to finish — the platform that fixes that: an enterprise image-annotation and quality-control system that takes raw imagery in and produces a clean, human-verified, model-ready dataset out. It went into real production use.

The interesting engineering isn't the annotation canvas. It's turning many fallible humans into one trustworthy answer.

TRUST MODEL · SOURCE vs VERIFIED · ANONYMISED

structural boundary · audit trail · provenance · ~1000×400

the trust model

  • Consensus as a first-class mechanism.

    Multiple reviewers tag the same image; the platform weighs their input and reconciles it into a single agreed label, rather than trusting whoever clicked last. Many opinions, one defensible result.

  • Disagreement treated as signal, not noise.

    When reviewers don't agree, the system quantifies it and surfaces the conflict automatically — so the hard cases get a human's attention instead of silently poisoning the dataset.

  • A hard line between what the system was told and what people verified.

    Source data and human-reviewed truth are kept structurally separate, so an upstream re-import can never quietly overwrite a reviewer's decision. Every label carries its history.

  • Audit-grade by construction.

    Role-based access, full change history, and provenance on every decision — because in a regulated setting a label isn't just data, it's evidence you may have to defend.

Underneath, it had to stay fast at a scale where you can't just load a folder, and it pushed its verified output straight into a training pipeline in standard ML formats — closing the loop from raw image to labelled dataset to model.

The judgment on offer here is the unglamorous half of applied AI that decides whether anything works: data trust, human-in-the-loop design, provenance, and the discipline to treat the labelling layer as a production system rather than a spreadsheet. It's the same discipline I bring when the deliverable is your model, not mine.

signal

build
solo · end to end
role
design · architecture · implementation
trust_model
weighted consensus · disagreement surfaced · full provenance
output
human-verified, model-ready datasets

tech

Next.js React TypeScript PostgreSQL cloud data pipeline SSO object storage

Want something like this built?

Thirty minutes. Bring the architecture diagram or the screenshot of the bug — whichever is closer to where you're stuck. I'll tell you what I'd build, what I wouldn't, and whether I'm the right person for it.