MESkit public website

Roadmap

Public milestone path from foundation to MQTT-enabled operations. Scope and timing follow the core PRD and roadmap documents.

Last updated: March 3, 2026

Summary

Current state and direction.

Summary

MESkit roadmap starts from a completed architecture baseline (pre-M1) and advances through M1-M6. Each milestone adds production capability while preserving the same tool-layer contract for UI and agents.

Milestone timeline

Explicit statuses with agent deliverables highlighted.

Pre-M1: Architecture and PRD baseline

Completed

Core PRD, data model, tool catalog, and architecture decisions finalized as the baseline for execution.

M1: Project scaffold + tool layer

Planned

Next.js shell, Supabase setup, auth, chat panel scaffold, and typed tool-layer foundations.

M2: Build mode + Operator Assistant

Planned

CRUD for lines/workstations/machines via UI and chat, with realtime sync across clients.

M3: Configure mode

Planned

Part numbers, BOM, routes, and serial algorithm workflows available through both UI and chat.

M4: Run mode + Quality Analyst

Planned

Unit generation, movement, quality events, and event-driven yield/defect monitoring alerts.

M5: Monitor mode + Production Planner

Planned

Live dashboards, traceability, and on-demand capacity planning through planner tool-use.

M6: MQTT interface + Anomaly Monitor

Planned

Broker bridge, validated device ingestion, and sensor anomaly detection agent activation.

Agent progression

How AI capabilities evolve across milestones.

Progression path

  • M1: runtime scaffolding only.
  • M2: Operator Assistant active.
  • M4: Quality Analyst active.
  • M5: Production Planner active.
  • M6: Anomaly Monitor planned.

Why this order

The roadmap introduces execution-first agent support before predictive workflows. This keeps operational trust anchored to explicit tool outcomes and measurable production metrics.

Key facts and mini FAQ

Answer-ready timeline context.

Key facts

  • Roadmap covers six milestones plus a completed pre-M1 baseline phase.
  • Agent progression: M2 Operator Assistant, M4 Quality Analyst, M5 Planner, M6 Anomaly Monitor.
  • Current public status is pre-M1 completed; M1-M6 are planned.
  • Architecture and PRD are canonical references for scope checks.

Mini FAQ

Which milestone introduces chat-driven operations?

M2 with the Operator Assistant integrated into Build Mode workflows.

When does MQTT ingestion arrive?

M6 introduces MQTT broker integration and edge-function bridging.

Where can I follow changes?

Use the roadmap, docs entry page, and repository changelog when releases are published.

Canonical links

Roadmap support references.