Milestones

List view

• M10 — Portfolio polish

  README, code elegance, IP review, and the testing pyramid — the things a reviewer judges.

  No due date

  •5/9 issues closed
  55% complete4 open5 closed

• M9 — Bench UX

  The workbench as an instrument: studios, chips, cards, mobile, and explaining what each dimension means.

  No due date

  •26/32 issues closed
  81% complete6 open26 closed

• M8 — Data completeness

  Names, properties, chip coverage, and one base table everything reads from.

  No due date

  •13/15 issues closed
  86% complete2 open13 closed

• M7 — Model quality & honesty

  Head calibration, precision, generalization, and the model-side work that makes a claim trustworthy.

  No due date

  •12/20 issues closed
  60% complete8 open12 closed

• M6 — Ship: pilot-ready

  Auth, licensing, analytics, and the demo script for a real pilot.

  No due date

  •1/5 issues closed
  20% complete4 open1 closed

• M5 — Ship: packaging & deployment

  Docker, Postgres/pgvector, and a clean-machine first run.

  No due date

  •5/5 issues closed
  100% complete0 open5 closed

• M3 — Track B: React workbench

  React front end against the JSON contract. The workbench that ships today is the Python/FastAPI one; this is the Track-B port.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• M2 — Track B: .NET API + ONNX serving

  The second track — a C#/.NET service over the same ONNX heads. Parallel to the shipping Python service, not a replacement for it.

  No due date

  •2/6 issues closed
  33% complete4 open2 closed