OpenCore MES Try the demo

Docs Integration 8

Appendix

On this page
Data integrity: where it stands, open findings, closed lately and the periodic review
Data integrity: changes made in the database itself, outside the platform, found, reported and acknowledged.
Data integrity: where it stands, open findings, closed lately and the periodic reviewData integrity: changes made in the database itself, outside the platform, found, reported and acknowledged.

8.1 Review checklist for a service change

#CheckOK
1Its identity is the least that works: its own role with only the roles it needs, or a user whose roles are known.
2Its callers name exactly who may call it.
3uses holds only the objects, operations, connections and transactions the script uses.
4Each connection allows only the requests the services send.
5Down (retry) and no (words) are told apart; refusals name the field.
6The other side is idempotent for triggers: the event's id is sent.
7Its test cases cover a good run, a refusal, and the other system down.
8No secret, address or credential is in the script or the design.
9runOn keeps it to nodes that can reach its systems, and some live node has that tag.

8.2 Where it is in the code

FileWhat
app/mes/server/integration.jsrunning services, the outbox worker, schedules, the /svc/v1 handler, the monitor
app/mes/client/definition.jsvalidateConnection, validateService, the footprint (who approves)
app/mes/client/schedule.jsthe schedule format, its checks, next runs
app/mes/server/script-runner.mjs, script-worker.mjswhere scripts run, and their limits
app/mes/server/fitness.jstest cases and the fitness test
app/mes/server/ai-api.jstokens, the /ai/v1 API
app/mes/db/token.mjsissuing an integration user's token
app/mes/test/integration.mjs, scheduler.mjsthe end-to-end proof
The integration monitor's Connections out: ERP's address, the services using it, its last request
Connections out: each connection's address, the services that use it, and how its requests went.
The integration monitor's Connections out: ERP's address, the services using it, its last requestConnections out: each connection's address, the services that use it, and how its requests went.

8.3 Revision history

RevisionDateWhat changed
A2026-10-02First issue: services and integration.
B2026-10-03Installing OpenCore MES: development, a server, upgrades, settings, scaling.
C2026-10-03A service's ctx.records.list(object, where) finds matching records among all of them, not only the 200 changed last.
E2026-10-06The guide applies to the platform as built.
F2026-10-06The data integrity review: INTEGRITY_KEY, the baseline after an upgrade, records written only through the platform.
G2026-10-06Setup: SETUP=1 for a new installation set up by its engineers (IN-03).
H2026-10-06A plant's own installation starts empty and is entered by its first administrator: reset --empty, opencore-mes admin (IN-01, IN-03).
I2026-10-10What is planned is the extension API and equipment data collection only: the contracts are built, the adapters come with the Equipment integration suite. The designer gives the design scopes, token.mjs the web ones; the suites store is not open yet; npm run dev watches app/mes only.
J2026-10-10PROD=1 does not start without SEAL_KEY and INTEGRITY_KEY; SIGN_IN_LIMIT, wrong sign-in tries per address; the HTTP APIs contract at 1.4.
K2026-10-10Languages and language packs: what a caller of the HTTP APIs reads (English), the language-pack contract and kit, a design's translations through /ai/v1 (POST /texts).
L2026-10-11Reading the model a part at a time through /ai/v1 (http-apis 1.8): POST /index, GET /designs/{kind}/{name}, POST /related, /search, /organization, /catalog (only), /runs.
M2026-10-11The design tools over MCP at /ai/v1/mcp (http-apis 1.9), and the command that adds them to Claude Code.
N2026-10-11Shapes kept: each operation's and tool's request and answer (http-apis 1.10), answers in the OpenAPI and as MCP outputSchema; a tool given notice.
O2026-10-11The copilot package and its contract (copilot-host 1.0): its kit, COPILOT_FROM for working on it.
P2026-10-17Executed by hand, then verified: an approved integration goes live when its executor presses Execute (DV-06); submit_change names the executor (http-apis 1.21), and the AI never executes or verifies.