Unica · Governance of AI agents

Every act of an AI agent, under the authorization of a person.

Unica records every act of an agent under the authorization of an identified person. Every record is signed: a later alteration breaks the signature. Unica is installed in the organization’s own cloud account.

Talk to us about a pilotHow it worksWhat Unica is
Illustrative example

Signed record

Act
Payment plan approved
Agent
Collections agent
Authorized by
Collections manager, an identified person
Authorization
In force; revocable at once
Signature
Valid: the record was not altered

The problem

When an agent acts, someone will ask who authorized it.

AI agents will act inside each organization’s own systems: approve an application, close a complaint, negotiate a payment plan, move a person’s data.

The supervisor, the auditor or the board will then ask the same question a person is asked today: who authorized it, under which rule, and how it is proven. If the answer depends on the model provider’s logs, it is not enough.

How it works

Four steps, all with a signed record.

  1. Authorization

    An identified person authorizes the agent. That authorization is revoked with immediate effect.

    Today

  2. Agent act

    The agent acts under that authorization, and each act stays tied to the person who gave it. Refusal of acts outside that authority comes in 2027.

    Today2027

  3. Signed record

    Who acted, under whose authorization, and when. Every record is signed: a later alteration breaks the signature.

    Today

  4. Verification

    Today, internal audit, the external auditor or the supervisor reviews the signed record: who acted, under whose authorization, and when. Verification on one’s own machine, without access to Unica, comes with the verifiable evidence package: as a service in 2027 and as a product in 2028.

    2027 service · 2028 product

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

Five advantages

Each advantage answers a question someone will ask sooner or later.

The examples are typical cases, not customers or deployments.

  1. Accountability for every 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.

    Illustrative example

    A collections agent negotiates payment plans under a manager’s authorization. When she leaves the post, her authorization is revoked and the record shows the date.

  2. Proof that does not depend on the provider

    • Today

      Every record is signed and stays in the organization’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 organization, Teipsum or the model provider.

    Illustrative example

    The external auditor asks for the file of a quarter’s approvals in which an agent took part. With the evidence package, they receive a verifiable file, not screenshots or access to production.

  3. A faithful reconstruction of what happened

    • 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.

    Illustrative example

    A person complains about a decision made eight months ago. From 2028, the data and the rules of that day are rebuilt, not today’s.

  4. Rules turned into controls

    • 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.

    Illustrative example

    With the evidence package, compliance documents its control of automated decisions with the system’s record, article by article, and not with a report written by hand.

  5. Lower cost of audit and supervision

    • 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 supervisor verify the record instead of reading reports: preparing a review goes from weeks of gathering to one signed export.

    Illustrative example

    With the evidence package, the second line of defence reviews the agents of three areas with the same signed record, instead of three quarterly reports prepared by hand.

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

Why now

The rules already have dates.

  • December 2026

    Ley 21.719, Chile

    Chile updates its personal data protection law, published on 13 December 2024: automated decisions, the right to an explanation, and portability. It applies from December 2026, unless the pending postponement passes. An agent that decides about a person will have to prove what it did and why.

  • 2 December 2027

    The EU AI Act

    From 2 December 2027 the obligations for high-risk systems apply, credit scoring among them: event logging, human oversight and explanation. A European group’s policies extend them to its subsidiaries outside Europe.

  • 2023–24

    The OAS guidelines

    The OAS publishes the Inter-American guidelines on data and AI governance. A guideline does not verify itself: it takes a record that proves it.

Where we are today

What is available today, and what comes next with its year.

  1. Available today

    • Authorization per person
    • Signed traceability
    • Immediate revocation
    • Installation in the customer’s own cloud

  2. 2027

    • Refusal of acts outside authority
    • Proven erasure
    • Model neutrality
    • Installation by a local consultant
    • First client with real data: 2027

  3. 2027 service · 2028 product

    • Verifiable evidence package
    • Contractual data residency
    • Neutral witness of third-party agents

  4. From 2028

    • Reconstruction and explanations for affected people
    • Partner operation in two jurisdictions

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

Two limits today

  • Model residency

    Strict model residency in Chile is not available today: the latest models are served from São Paulo. The data does stay in the customer’s cloud account.

  • Team size

    Teipsum is a team of four people. Delivery is through local partners.

First step

A 90-day pilot, in 2027.

Limited to one function: a credit line, a collections queue, a compliance process, an administrative function or a supervision case.

With authorization per person and signed traceability from the first day, in the organization’s own cloud account. Planned start: 2027.

What we ask in return

  1. A person from risk or innovation as the owner of the pilot.
  2. Information security and internal audit taking part from the design.
  3. A reference at the close of the pilot: private before your supervisor and, with your consent, public.

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

Let’s talk about a focused pilot.

Tell us which function you would hand to Unica first.

Talk to us about a pilot