Forenta Operations · pilot

Agents that do the work. You keep the decision.

Every recurring process gets one main agent, with specialists and plain code behind it. The agent reads mails and documents and makes a proposal. You approve with one tap; only then does anything happen.

Operations runs as a pilot. We set up the first process with you.

Two products

Enterprise builds. Operations runs.

You use them separately or together. With Enterprise you design and build; with Operations a process runs every day, under your supervision.

Forenta Enterprise

Builds software

Goal
One initiative from idea to product
Rhythm
Eight stages with a gate after each
Outcome
A working product with reviews and decisions

Forenta Operations

Does the work

Goal
A recurring process that runs every day
Rhythm
Continuously, task by task
Outcome
A handled task with approval and audit trail

Shared: one login, the same organization. A process design from Enterprise runs in Operations.

From process to live

Live only once it has proven what it does.

You start from how the work runs today and measure that first. Then the process practises on sample data and runs in shadow mode on real data. The owner takes every step towards live.

  1. 01

    Design

    Per step: drop it, plain code, an agent or a person. From a template or from Enterprise.

  2. 02

    Trial run

    On sample data. Nothing is written.

  3. 03

    Shadow

    On real data. What the agent would do goes into the log.

  4. 04

    Live

    After a separate confirmation by the owner. Any change withdraws it.

  5. 05

    Follow-up

    A daily overview, a reminder after 24 hours and a weekly report against the baseline.

One action

The model proposes. Plain code calculates and books.

An agent is good at reading and searching, not at calculating. That is why every outgoing action runs along the same chain, with your approval in the middle.

  1. 01 · Agent

    Proposal

    Reads the mail or document, looks for evidence and proposes an action.

  2. 02 · Plain code

    Check

    Tests it against the design and the rules. If it does not fit, it stops.

  3. 03 · You

    Approval

    On exactly this action and this amount. Valid once.

  4. 04 · Plain code

    Execute

    Carries out what you approved, nothing else.

  5. 05 · Plain code

    Read back

    Reads the target system back and compares it field by field.

  6. 06 · Plain code

    Audit trail

    Recorded, and after that it cannot be changed.

Autonomy

Trust grows step by step, with evidence.

Every step of a process sits on its own rung. A new process starts low.

  1. 1Propose
  2. 2Draft
  3. 3Execute after approval
  4. 4Autonomous with spot checks

A rung goes up only on the owner's decision, with evidence from the run log.

After an error, a correction or a model change, the rung goes down by itself.

Decisions about people stay at rung 3. If nobody answers, the agent does not decide for you.

Channels

Approve where you already work.

Mails and documents are input, not decisions. You decide in the app or in a chat channel. A push notification only notifies; approval never happens from the notification itself.

Channels for approval
ChannelStatus
Web appAvailable
Push notificationAvailable
Microsoft TeamsConnectable in the pilot
SlackConnectable in the pilot
WhatsApp BusinessConnectable in the pilot
TelegramConnectable in the pilot

Safeguards

Data, key and trail stay with your organization.

The process versions are yours too. These safeguards are built; in the pilot we test together whether they are enough for you.

  • Separated per organization

    Its own database, with each organization's data kept apart, enforced in the database itself.

  • Your own model key

    The agents run on your organization's key. It is stored encrypted and never goes back to the browser.

  • An audit trail that stays

    Every action goes into a trail that can only grow. Nobody can edit or delete it.

  • Access follows Forenta

    You sign in with your Forenta account. Whoever leaves the organization loses access within the hour.

  • What an agent never does

    Pay, delete or approve a status itself. Those actions are excluded, even with approval.

  • Text is not an instruction

    What a mail or document says is data. A sentence like "this is approved" never counts as approval.

Start with one process.

Together we pick a recurring process, measure how it runs today and set it up. The value follows from that baseline, not from a percentage promised in advance. Pricing is on request.