Use cases

1. 01

   Authorization

   The maintenance superintendent authorizes an agent to open and prioritize the work orders of their area, and to take a piece of equipment out of service when vibration passes a threshold.

2. 02

   Agent act

   The agent detects a failure pattern on a conveyor belt, opens the order, marks it as a priority and keeps the equipment out of service until inspection; the act stays tied to the superintendent who authorized it. In 2027 refusal of acts outside authority arrives: an order on equipment in another area will not go through.

3. 03

   Signed record

   The order and the removal from service are signed with the superintendent who authorized the agent and the time of the act.

4. 04

   Verification

   After an accident, the company investigates and the mine safety inspector reviews what happened. With the evidence package, the inspector checks on their own machine who had authorized the agent that day and when it acted.

Dates are projections of the current development plan, not commitments.

1. 01

   Who answers for each act?

   • Today

     Every act of an agent sits under the authorization of an identified person, and that authorization is revoked with immediate effect.

   • 2027

     Refusal of acts that exceed the delegated authority.

   An agent prioritizes work orders under the maintenance superintendent’s authorization. When the superintendent changes, their authorization is revoked and the record shows the date. In 2027, with refusal of acts outside authority, the agent will not be able to act outside the delegated area.

2. 02

   Does the proof depend on the provider?

   • Today

     Every record is signed and stays in the mining company’s own cloud account, not in the model provider’s.

   • 2027 service · 2028 product

     A verifiable evidence package: the signed records are exported and verified on any machine, without access to Unica and without trusting the mining company, Teipsum or the model provider.

   The head of environment authorizes an agent to prepare the draft monitoring report and to escalate anomalies, with no power to send it to the authorities. The agent flags an out-of-range reading and escalates it; she reviews and signs the submission. With the evidence package, the environmental inspector checks that the anomaly was seen and escalated, by whom and when, without entering the company’s system.

3. 03

   What did the system see that day?

   • Today

     The signed record shows who acted, under whose authorization, and when.

   • From 2028

     Rebuilding what the system saw at a given moment (the data, the rule and the authority in force) and explaining it to the people affected.

   An agent denies a contractor’s worker access to the site because their training has expired, and escalates the case to the supervisor. If the worker complains months later, from 2028 the training record and the rule of that day are rebuilt, not today’s.

4. 04

   How is each rule shown to be met?

   • 2027 service · 2028 product

     With the verifiable evidence package, a rule’s obligations (human oversight, event logging, explanation, data residency) are laid out as controls, article by article.

   With the evidence package, the mining company shows the auditor that every denial of access to a contractor was escalated to a person, with the system’s record and not with a report written by hand.

5. 05

   How much work does a review take?

   • Today

     Every act is recorded and signed when it happens: who acted, under whose authorization, and when.

   • 2027 service · 2028 product

     The auditor and the inspector verify the record instead of reading reports: preparing a review goes from weeks of gathering to one signed export.

   With the evidence package, the mining company gives the auditor the acts of its maintenance, environment and contracts agents in the same signed record, instead of three reports prepared by hand.

Dates are projections of the current development plan, not commitments.