Skip to content
CoCoCo Knowledge Base
Back to Knowledge Base

Glossary

A reference of the core terms used across CoCoCo.

A

Section titled “A”

AI Adapter — A configured connection to an AI model provider (OpenAI, Claude, Apple Native, XGBoost). Stores credentials so Workflows and AI Agents can call the model without embedding API keys in code.

AI Agent — A configured AI assistant combining an AI Adapter with a defined role, goal, and backstory, plus optional tools. Invoked from Workflows.

API Token — A personal credential used to authenticate requests to the CoCoCo API. Tied to a user account and carries that user’s permissions.

B

Section titled “B”

Bot — A user type for automated service accounts. Has no login — only API access via a Token.

C

Section titled “C”

Capability — An attribute of a Work Center describing what it can do — job types it handles, media sizes it supports, etc. Used by planning tools to route jobs.

Config — A non-sensitive key-value entry in Tenant Config. The value remains visible in the UI after saving.

Controller — A bridge between a physical device network and CoCoCo, managing protocol translation and message routing.

Custom Action — A saved, reusable Lua function callable from a Workflow Custom Action node.

Custom App — A bespoke interface built on CoCoCo using Vue.js (Template), JavaScript (Script), and optional Lua (Server API). Appears as a Page, Dashboard tab, Kiosk, or Job View.

Custom Data Table — A user-defined database table inside CoCoCo for structured data that doesn’t fit the built-in data model.

D

Section titled “D”

Dashboard App — A Custom App kind appearing as a tab on the CoCoCo Dashboards screen.

DENY — An IAM Statement effect that blocks an action. DENY always overrides ALLOW, regardless of other Policies.

Device — A physical machine, sensor, or system registered in CoCoCo that sends data via MQTT, HTTP, JMF, or SQL.

Device Token — A credential tied to a specific Device (not a user) for authenticating device requests to CoCoCo.

E

Section titled “E”

Edge App — A program that runs on a Controller at the edge, using the bridge.* runtime to bridge local machines and protocols (MQTT, OPC-UA, Modbus) to CoCoCo.

Estimate — A commercial quotation sent to a customer for approval before an Order is created.

Execution — A single run of a Workflow, from trigger to completion or failure.

H

Section titled “H”

HITL — Human-in-the-Loop. A Workflow pattern where automation pauses for a person to complete a Task before continuing.

HTTP — A device protocol for connecting systems via web requests. Supports inbound and outbound communication.

I

Section titled “I”

IAM — Identity and Access Management. The system of Users, Policies, Statements, and Teams that controls who can do what in CoCoCo.

Incoming Webhook — A unique URL that external systems POST to in order to trigger a CoCoCo Workflow.

Integration — A packaged, server-side extension that connects external systems and devices, built with the ctx.integration.* runtime.

Invoice — A billing document. CoCoCo supports standard Invoices, Credit Notes, and Proformas.

J

Section titled “J”

JDF — Job Definition Format. An XML-based standard for passing job parameters to CIP4-compatible print machines.

JMF — Job Messaging Format. A messaging protocol for JDF-compatible equipment. Outbound only.

Job — The central production unit in CoCoCo — a piece of work moving through the production floor.

Job View App — A Custom App embedded in the Job detail panel.

K

Section titled “K”

Kiosk App — A full-screen Custom App for shared shopfloor terminals. Accessible only to Kiosk users.

Kiosk User — A user type for shared shopfloor terminals with a simplified interface and access only to Kiosk Apps.

L

Section titled “L”

Lua — The scripting language used for CoCoCo Scripts, Custom Actions, and Server API code.

M

Section titled “M”

MCP — Model Context Protocol. An open standard for connecting AI assistants to external tools. CoCoCo exposes an MCP server at /mcp.

Metric — A structured data point sent by a Device during production — machine state, speed, error codes, etc.

ML Model — A machine learning model trained inside CoCoCo using XGBoost. Supports regression and classification.

MQTT — A lightweight publish/subscribe protocol for real-time machine data. Supports inbound and outbound communication.

N

Section titled “N”

Network — A logical container for connected Devices, providing their communication channel.

Node — A single processing step in a Workflow — transformation, API call, condition, notification, etc.

Notification Group — A named list of recipients that Workflows can send messages to.

O

Section titled “O”

Order — A confirmed production request that creates a Job on the floor.

P

Section titled “P”

Page App — A Custom App appearing in the left sidebar as a standalone page.

Policy — A set of IAM Statements (ALLOW/DENY rules) attached to users or teams to control permissions.

Production Cell — A named group of Work Centers representing a functional area of the floor (e.g. Digital Printing).

Purchase Order (PO) — A document sent to a supplier to request goods or services.

S

Section titled “S”

Script — A saved, reusable Lua function. Roles: Script, JDF Template, JMF Template, ML Data Query.

Secret — A sensitive key-value entry in Tenant Config. Value is hidden after saving and cannot be read back.

Server API — The Lua component of a Custom App that runs server-side, used for privileged data operations.

Shift Definition — A schedule specifying when a Work Center is operational.

SQL — A protocol for connecting CoCoCo to external databases. Outbound only.

Statement — An IAM rule specifying an Effect (ALLOW or DENY), Actions, and Resources within a Policy.

T

Section titled “T”

Task — A human action item created by a HITL Workflow. Appears in the assignee’s My Tasks view.

Team — A named group of users who share Policies and permissions.

Template — In Custom Apps: the Vue.js HTML fragment defining the UI. Also refers to JDF/JMF Template Scripts for generating machine job tickets.

Tenant Config — A secure key-value store for platform-wide settings (Config) and credentials (Secrets).

Trigger — The starting event of a Workflow — Job Event, Device Metric, Schedule, Webhook, or Manual.

U

Section titled “U”

User — A person or service account with access to CoCoCo. Types: Human, Kiosk, Bot.

W

Section titled “W”

Work Center — Any production resource — machine, person, tool, or location — that performs or supports work.

Workflow — An automated process triggered by events, consisting of a Trigger and a sequence of Nodes.

X

Section titled “X”

XGBoost — The machine learning algorithm powering CoCoCo’s built-in ML Models. Supports regression and classification tasks.

Section titled “Related articles”