Pragmatos Decisions

Every decision on the record: who, on what evidence, and what happened next.

Holds, releases, re-measures and approvals land on one tamper-evident ledger, with the evidence attached and the outcome checked later. Orbis proposes, a person decides, Decisions keeps the proof.

A quality office beside a machining hall: two people at a desk with a thick ring binder, looking through the window at a pallet of turned parts held behind striped tape next to a lathe
1A pallet on holdwho held it, and why
2The paper trailwhich sheet belongs to that pallet
Which sheet belongs to that pallet. A held lot, a binder and a question nobody can answer from paper: who decided, on what evidence, and what happened next.
Six record cards in a row, each joined to the one before by a chain link and a seal; the newest card on the right is highlighted
1Each row sealed to the one beforechange one and the chain shows it
2The newest rowa release with two signatures
Chain verified · 6 rows
Every decision on one chain. Each decision is a row with its evidence, its role and its time, sealed to the row before. The check runs on screen.
A loop around a machine hall: a milling machine, a screen of status dots, a person approving on a tablet, a technician changing a tool, a calm trend line, and a notebook feeding back to the start
1Orbis proposeswith its evidence attached
2A person decidesthe role allowed to sign, signs
3The outcome is confirmedand feeds the next proposal
Outcomes teach the next proposal. What happened after the decision is checked against what was expected. Confirmed outcomes go back to Orbis.

The last step of the loop: the proof

Loom connects the machines, Pragmatos Live shows them, Pulse reads their condition, Orbis proposes what to do and Flow turns an approved decision into work. Decisions keeps the record of all of it: who decided, on which evidence, and what happened after. What it learns goes back to the start.

  1. ConnectLoom
  2. SeeLive
  3. AnalyzePulse
  4. DecideOrbis
  5. ActFlow
  6. ProveDecisions

Confirmed outcomes return to Orbis, so the next proposal starts from what worked.

2signatures to release a held lot
1chain: every decision sealed to the one before
5people at least in any group the works council view shows
28languages on screen, German included

The ledger: every decision, its evidence and its signature

Decisions

Each decision is one row: what was decided, the evidence it rests on, the role that signed, the time, and whether a model proposed it and with what confidence. Each row is hashed together with the row before it. The database role the application uses can add rows and cannot change them, so the ledger is tamper-evident: change a row anywhere else and the chain shows it.

Evidence attaches when the proposal is made, not after the decision. Approving a proposal raises its work order; rejecting it closes the proposal, and both go on the record.

TimeDecisionEvidenceRoleOriginSeal
06:14Hold lot 4471 (Sperren)Bore drift on lathe 3, trend attachedQualitätssicherungOrbis proposal41c7 → 9f3a
07:30Re-measure twenty parts (Nachmessen)Sample plan for the measuring machineQualitätssicherungPerson9f3a → b20e
07:52Rework 2, release 238 (Freigeben)Measuring results: 18 inside, 2 near the limitQualitätssicherung and SchichtleiterPersonb20e → 6d14
08:05Change the insert on lathe 3Approved proposal, work order raised in FlowInstandhaltungOrbis proposal6d14 → c58b
Chain verified · 4 rowsEach seal is a hash of the row and the seal before it.Example rows.
Pragmatos decision register: columns for when, decision type, model, confidence, approver and rationale
The register as the product shows it: when, which decision, which model, its confidence, who approved and why.
Pragmatos approval queue: two proposals, each with a panel on what it is based on and a work order line
The queue: each proposal shows what it is based on before anyone signs.
Pragmatos approval screen for a quality proposal, with the readings it rests on listed below
An approval with its evidence: the readings the proposal rests on.
A queue per decision familyQuality, maintenance and production calls each go to the roles that sign them.
Two-person sign-offWhere a decision needs two signatures, the second signer sees what the first saw.
Escalation to deputiesAn open decision moves to a deputy, and the ledger records who took it.
A link per decisionEach decision has its own link, so a mail or a shift note points at the record itself.

No measured basis recorded. When a proposal has no measurement behind it, it says so in those words, and the person deciding sees the gap before signing.

Each role opens Decisions on its own day screen: what waits for its signature, what it held, what is overdue. The screens run in 28 languages.

Containment: hold, re-measure, release

Decisions

When a lot is in doubt, one role holds it. The parts go back to the measuring room, and the results attach to the hold. Two people sign the release. Every step is a row on the chain, so the question of which sheet belongs to which pallet has one answer.

A quality approval asks for an explicit disposition. Orbis proposes one, and the person signing picks it:

  • Adjust the offset
  • Hold
  • Rework
  • Inspect
  • Route to scrap

Routing parts to scrap is only ever a person's choice.

Illustration: a pallet of flanges held behind a chain with an orange tag, a measuring machine probing one flange while two people watch, and a released pallet with a green tag
Held, re-measured, released: three steps, three rows on the chain.
  1. 1
    Hold (Sperren)One role holds the lot. The hold, its reason and its evidence go on the ledger at once.
  2. 2
    Re-measure (Nachmessen)The parts go back to the measuring room. The results attach to the same decision.
  3. 3
    Release (Freigeben)Two people sign the release. Each signature is its own row on the chain.

Outcomes: what happened after the decision

Decisions

A decision is not finished when it is signed. Decisions follows it: the effect screen (Wirksamkeit) sets what was expected against what happened, machine by machine.

A person confirms the outcome. Confirmed outcomes go back to Orbis, so its next proposal for that machine starts from what worked and what did not.

The model never decides. Orbis proposes, a person with the right role decides, and Fabric sends only work a person approved to your ERP.

Illustration: the same machining centre on two days, on the left a technician fitting a new spindle part beside a jagged chart, on the right the machine running with a green light and an even chart, a dotted line returning to a small network above
Expected against actual, and the confirmed outcome sent back to Orbis.

The works council: a read-only view of what is recorded

Decisions

Under §87(1) No. 6 BetrVG the works council (Betriebsrat) has a say in systems that can watch performance. Decisions gives it its own read-only view: which personal data the system holds, every switch of the person-linkage mode, the role assignments and the list of reports.

Groups smaller than five people are not shown by default, and people appear under pseudonyms. There is no ranking of named individuals, and alarm mails never name who acknowledged them.

Linking records to a person stays off until a works agreement (Betriebsvereinbarung) reference is entered. The works council is notified first, and the switch itself goes on the ledger. Your works agreement sets the rules; Decisions records which rules are in force.

Illustration: four people at a meeting table facing a wall screen of grouped person symbols and a struck-through eye, with a press visible through the glass wall
Groups, not names: the works council sees what is recorded and how.
Pragmatos mode change history: each switch of the person-linkage mode with its date and note
Mode change history: every switch of the person-linkage mode, with its date and its note.
Pragmatos screen in German telling a user that a view belongs to another role, with a button back to the start page
A screen outside your role stays closed, here in German as the product shows it.

Audit: export the record, check the chain

Decisions

An auditor asks for one machine, one period or one company, and gets that export with its chain head. The verify screen recomputes the chain from the first row, and the badge reads Chain verified with the number of rows checked.

The audit query answers the two questions an AI audit starts with: which decisions did a model influence, and which role approved them.

Decisions keeps the record, designed for the EU AI Act's human-oversight and logging requirements. Part records follow your retention policy, aligned with IATF 16949: the life of the part plus one year, up to fifteen years.

Illustration: a server rack in the plant sends a stack of sealed folders to an auditor's desk, where a magnifying glass rests on a chain with one broken red link
One broken link in the chain is enough to show a change.
Export by machine, period or companyWith the chain head, so the auditor checks the file against the ledger.
A verify screenIt recomputes the chain and shows how many rows it checked.
An audit query for AIWhich decisions a model influenced, and which role approved them.
No direct identifierThe ledger holds roles and pseudonyms, not names.

One morning on the record: a hold, start to finish

Decisions

An example of how one drift on one lathe moves through Pragmatos, and what the ledger holds at the end of it.

  1. Pulse flags a driftThe bore on lathe 3 is drifting toward its limit. Lot 4471, 240 flanges, is on the pallet.
  2. Orbis proposesHold the lot, re-measure twenty parts, adjust the offset. The proposal carries the trend it rests on.
  3. The head of quality holds the lotOne signature, one row. The pallet is held on screen and on the floor.
  4. Twenty parts re-measuredEighteen inside the tolerance, two near the limit. The results attach to the hold.
  5. Rework two, release 238The head of quality signs, the shift lead (Schichtleiter) signs second. Two signatures, two rows, one decision.
  6. Maintenance changes the insertThe approved proposal becomes a work order in Flow. Maintenance (Instandhaltung) closes it at the machine.
  7. The outcome is confirmedThe bore holds its size. Expected and actual sit side by side, and the confirmed outcome goes back to Orbis.
  8. The auditor asksA period export for lathe 3 goes out with its chain head. The verify screen reads Chain verified.

Who it's for: what changes on Monday

Decisions

Pick a role to see what changes on Monday. The plant manager is open to start.

Plant manager (Werkleiter)

If you run the plant and answer for what leaves it:

  • Every hold, release and re-measure sits on one screen, with who signed it and when.
  • An open decision does not wait for a person on leave: it moves to the deputy.
  • When a customer asks about a lot, the answer is a link, not a search through binders.

Quality (Qualitätssicherung)

If you sign off holds and releases:

  • The hold, the measuring results and both signatures belong to one decision.
  • A quality approval asks for an explicit disposition, and scrap is only ever a person's choice.
  • The period export for an audit comes from the ledger, not from a spreadsheet built for the day.

Works council (Betriebsrat)

If you represent the people on the floor:

  • You get a read-only view of which personal data the system holds and every switch of the person-linkage mode.
  • Groups smaller than five stay hidden by default, and people appear under pseudonyms.
  • Person-linkage stays off until your works agreement reference is entered, and you hear first.

Owner and CFO (Geschäftsführung)

If you own the plant and carry its liability:

  • Every call on the floor has a role, a signature and its evidence, so a claim is answered from the record.
  • Outcomes are checked against what was expected, so you see which decisions paid off.
  • The record stays in your installation, under your own retention policy.

IT and auditors (IT und Auditoren)

If you look after the systems or check them:

  • The ledger is append-only and hashed row by row, and the verify screen recomputes the chain.
  • The audit query answers which decisions a model influenced and which role approved them.
  • Exports go out by machine, by period or by company, with the chain head to check them against.

Maintenance (Instandhaltung)

If you keep the machines running:

  • A work order arrives with the decision behind it and the evidence it rests on.
  • When the job is done, the outcome is checked, so the next proposal for that machine starts from what worked.
  • No order starts from a model alone: a person approved it first.

Shift lead (Schichtleiter)

If you run the shift:

  • Your day screen shows what waits for your signature, and nothing else.
  • A second signature on a release is two taps, with the first signer's evidence in front of you.
  • The next shift sees what was held, why, and who held it.

Bring IT, quality and the works council. We walk them through the ledger.

Pragmatos reads, people act. Orbis proposes, a person with the right role decides, and Decisions keeps the proof.

A walkthrough for the people who sign off: the ledger, the containment flow, the works council view and an audit export.

Book a walkthrough

Where Decisions connects

Get new articles by email

One shop-floor problem at a time.

Questions quality, IT and the works council ask

An alarm from a machine, shown on a phone
No. The ledger is append-only: the database role the application runs under cannot update or delete a row, and each row carries a hash of the row before it. A row changed outside the application no longer matches the exported chain head, and the verify screen recomputes the chain on request.
No. Orbis proposes, with its evidence attached, and a person with the right role decides. Fabric sends only work a person approved to your ERP, and the ledger records which decisions a model influenced and which role approved them.
Decisions is designed for the EU AI Act's human-oversight and logging requirements: a named role approves, and every decision keeps its evidence, its AI origin and its time. Whether your use meets the Act is for you and your advisers to assess.
A read-only view: which personal data the system holds, the history of the person-linkage switch, the role assignments and the list of reports. Groups smaller than five are not shown by default, and people appear under pseudonyms.
No. There is no ranking of named individuals, and alarm mails never name who acknowledged them. Linking records to a person stays off until a works agreement (Betriebsvereinbarung) reference is entered, and the works council is notified before the switch.
As long as your retention policy says. For part records under IATF 16949 that is the life of the part plus one year, up to fifteen years, and the chain stays verifiable for all of it.
Where the rest of Pragmatos runs. On premise in your plant, in your own cloud, or both: you choose. In a hybrid set-up, the edge computer in each plant reads the machines, buffers through a network drop and sends on only the data you choose. The ledger holds no direct identifier of a person.
The proposal says so in words: No measured basis recorded. It still goes to a person, who sees what is missing before deciding.