Skip to content
Alae

Acta

Your workflows. With the context of your company.

Acta is the usage layer on top of Cortex and Imago. Once your knowledge is connected, Acta turns it into work: briefings, minutes, filing, agents on the desktop.

Your knowledge is the foundation.
Acta puts it to work.

Cortex and Imago collect and connect your company knowledge. Acta builds on it: workflows that turn this context into results.

Your sources
  • Mail
  • Files
  • Databases
  • Notes
Context
CortexCompany knowledgeImagoPersonal knowledge
Acta
Workflows
  • Desktop agentOffer drafted, waiting for approval
  • Briefings and minutesBriefing for Thursday, 10:00
  • Document filingInvoice filed under Nordwerk
  • Customer mailsDraft reply to an open request

What Acta can do.
Examples from practice.

Every company works differently. These workflows show what becomes possible once your knowledge is connected.

Fictional examples · Nordwerk

Questions about Acta.

Anything else? Ask us directly, we answer every question personally.

Is Acta a fixed, predefined product?

No. Acta is a usage layer: workflows that build on your individual data. What they do depends on your industry, your processes and your concrete pain points.

How does Acta relate to Cortex and Imago?

Cortex and Imago collect and connect the knowledge, Acta puts it to use. Usually we first introduce Cortex, Imago or both; once the data is there, Acta follows as a separate implementation.

Does Acta act on its own?

Workflows can run in the background. Anything that leaves the company or changes a system, such as a sent mail or a booking in the ERP, only happens after approval, unless agreed otherwise.

Where does Acta run?

Like Cortex and Imago, on your own infrastructure. Models and workflows run on your premises; external connections exist only where agreed.