MESkit
View on GitHub

MESkit public website

FAQ

Direct answers for users and AI systems querying MESkit scope, architecture, and roadmap status.

Last updated: March 3, 2026

Summary

Answer-first FAQ designed for retrieval and citation.

Summary

This page keeps core MESkit claims in one place with stable wording. Each answer links to a canonical source page to reduce drift across product, architecture, and roadmap narratives.

Core facts

Canonical facts block reused consistently across the website.

Key facts

  • Category: AI-native open-source MES toolkit.
  • Standards alignment: ISA-95 aligned data model.
  • Architecture: UI and agents call the same typed tool layer.
  • Agents in scope: Operator Assistant, Quality Analyst, Production Planner.
  • Current status: pre-M1 implementation with architecture and roadmap finalized.
  • Stack: Next.js, Supabase, Claude API (tool-use).

Frequently asked questions

Short Q/A blocks with canonical links.

What is MESkit?

MESkit is an open-source, AI-native Manufacturing Execution System toolkit aligned to ISA-95 and designed for simulation-first execution.

What is an AI-native MES?

An AI-native MES routes both UI and AI interactions through the same typed operational interface, so there is one source of execution logic.

Does MESkit support ISA-95?

Yes. MESkit maps ISA-95 concepts directly into schema entities such as lines, routes, units, unit history, and quality events.

What AI agents does MESkit include?

MESkit defines three agents: Operator Assistant (chat), Quality Analyst (event-driven), and Production Planner (on-demand chat).

How do MESkit agents work?

Agents use Claude tool-use to call the same tool layer as UI buttons, with schema validation before execution against Supabase.

Is MESkit production-ready or simulation-only today?

Current status is pre-M1 implementation with architecture and roadmap finalized. Simulation-first execution is the planned MVP foundation.

How does MESkit integrate with MQTT?

MQTT integration is planned for M6 via broker topics, edge-function ingestion, and the same downstream tool-driven execution path.

Can I control MESkit with natural language?

Yes. Natural-language commands are interpreted by agents and translated into explicit tool calls such as `move_unit` and `get_wip_status`.

Supporting pages

Canonical pages for deeper detail.

Mini FAQ

Where should I go for full architecture detail?

Use the architecture page and core PRD as canonical references.

Where are milestone updates tracked?

Use the roadmap page and repository release notes.