WeOrchestrate
Product

The layer that lets AI operate

Skills files sit at the top of the orchestration. They describe how your operation actually runs, so AI agents can act on it instead of guessing.

The gap

Why agentic AI fails in factories

Modern AI agents can already follow structured instructions, call external systems, and chain actions. What they cannot do reliably is operate in a domain where the rules are implicit and scattered across legacy systems, paper logs, weighing system displays, regional accounting packages, and the heads of senior workers. Without a structured manual of how the operation actually runs, agents make things up or freeze.

The answer

What a skills file is

A skills file is a structured manual that tells an AI agent how a specific operation runs. The entities that exist, the states they can be in, the events that change those states, the rules that govern the changes, the actors who are authorised to act, and the evidence required for each action. Once written, it is portable across AI providers, across model versions, and across time.

What happens on the floor becomes a record. The record cannot be silently changed. The record drives the books, the compliance file, and the agent.

Append-only event log

Every action becomes an immutable event with timestamp, actor, and evidence. State is derived from the log, never edited directly.

Governed agent execution

Agents read the skills file, query the event log, and execute actions through the same structured interface. Every action is logged, governed by the same rules as a human action, and auditable.

On-premise by design

Built to run on customer hardware, with an architecture designed for fully air-gapped sites and no outbound network calls.

Multilingual operational reality

Built for environments where the workforce, the regulators, and the legacy systems speak multiple languages. The structure absorbs operational reality across Albanian, Italian, English, and Western Balkans languages.

Industrial protocol integration

Direct integration with weighing systems, sensors, SCADA, and building management systems via Modbus, OPC UA, BACnet, KNX. Industrial OT integration is operational ground truth, not theory.

Portable skills file format

Once written, a skills file is portable across AI providers and model versions. The agents will commoditise. The structure will not.

Architecture

Inside the AI layer

Reality enters through industrial protocols, becomes events, compounds into a governed log, and feeds the skills file that lets agents act safely back on the operation.

System architecture: physical operation flows through industrial protocols, event capture, an append-only log, the skills file specification, the agent runtime, and back to the operation as governed actions.

  1. Physical operation

    Floor reality, weighing systems, sensors, people

  2. Industrial protocols

    Modbus, OPC UA, BACnet, KNX

  3. Event capture

    Every action timestamped, signed, witnessed

  4. Append-only event log

    Immutable. State derived, never edited.

  5. Skills file specification

    Entities, states, rules, authorisations, evidence

  6. Agent runtime

    Reads the file, queries the log, executes governed actions

  7. Governed actions

    Returned to the operation through the same interface as a human action

Let's see if your operation fits.

If agents in your plant would need to know how things really run, that is where we start. Tell us about your operation.

Or email us directly at admir.malaj@weorchestrate.tech.