MESkit
Try MESkitView on GitHub

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 7, 2026

Summary

Current state and direction.

Summary

MESkit roadmap starts from a completed architecture baseline (pre-M1) and advances through M1-M6. M1 (scaffold + tool layer) is complete. M2 (Build Mode + Ask MESkit) is in progress with shop floor tools and the natural language interface functional via chat. Each milestone adds production capability while preserving the same tool-layer contract for UI and smart features.

Milestone timeline

Explicit statuses with feature 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

Completed

Next.js shell, Supabase setup, auth, chat panel, Zustand stores, tool-layer architecture with stubs, agent runtime with streaming, and ISA-95 database schema — all complete.

M2: Build mode + Ask MESkit

In progress

Shop floor tools (lines, workstations, machines) and natural language interface are functional via chat. Build Mode UI with CRUD panels and Realtime sync is next.

M3: Configure mode

Planned

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

M4: Run mode + Quality Monitor

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 + Machine Health Monitor

Planned

Broker bridge, validated device ingestion, and sensor anomaly detection for predictive maintenance.

Feature progression

How smart features evolve across milestones.

Progression path

  • M1: runtime scaffolding — done.
  • M2: Ask MESkit — active.
  • M4: Quality Monitor active.
  • M5: Production Planner active.
  • M6: Machine Health Monitor planned.

Why this order

The roadmap introduces execution-first smart feature 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.
  • Feature progression: M2 Ask MESkit, M4 Quality Monitor, M5 Planner, M6 Machine Health Monitor.
  • M1 is complete. M2 is in progress — shop floor tools and Ask MESkit are functional.
  • Architecture and PRD are canonical references for scope checks.

Mini FAQ

Which milestone introduces chat-driven operations?

M2 with Ask MESkit 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.