Pre-M1: Architecture and PRD baseline
CompletedCore PRD, data model, tool catalog, and architecture decisions finalized as the baseline for execution.
MESkit public website
Public milestone path from foundation to MQTT-enabled operations. Scope and timing follow the core PRD and roadmap documents.
Last updated: March 3, 2026
Current state and direction.
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.
Explicit statuses with agent deliverables highlighted.
Core PRD, data model, tool catalog, and architecture decisions finalized as the baseline for execution.
Next.js shell, Supabase setup, auth, chat panel scaffold, and typed tool-layer foundations.
CRUD for lines/workstations/machines via UI and chat, with realtime sync across clients.
Part numbers, BOM, routes, and serial algorithm workflows available through both UI and chat.
Unit generation, movement, quality events, and event-driven yield/defect monitoring alerts.
Live dashboards, traceability, and on-demand capacity planning through planner tool-use.
Broker bridge, validated device ingestion, and sensor anomaly detection agent activation.
How AI capabilities evolve across milestones.
M1: runtime scaffolding only.M2: Operator Assistant active.M4: Quality Analyst active.M5: Production Planner active.M6: Anomaly Monitor planned.The roadmap introduces execution-first agent support before predictive workflows. This keeps operational trust anchored to explicit tool outcomes and measurable production metrics.
Answer-ready timeline context.
M2 with the Operator Assistant integrated into Build Mode workflows.
M6 introduces MQTT broker integration and edge-function bridging.
Use the roadmap, docs entry page, and repository changelog when releases are published.
Roadmap support references.