Product status: in development
Qronos is not yet available for deployment. This article introduces the product direction and questions worth preparing for. It does not announce a release date, a price or guaranteed feature availability.
Qronos is intended to assess an autonomous agent’s steps before execution and against the authorised task. Details and current status are available on the Qronos product page.
An answer and an action have different consequences
A person can edit an assistant’s draft. Once an agent sends a message, changes a record or runs an operation, the consequence has already occurred. Process design therefore needs to distinguish preparing material from having permission to change something.
Consider a fictional task: prepare an overview for the sales team. Reading approved data may be appropriate. Sending the entire export to a new external address is a separate decision. The original brief does not necessarily authorise it.
Decisions your organisation can make now
- Purpose: what should the agent produce, and for whom?
- Sources: which information and tools may it access?
- Boundaries: which steps may run independently, and which require approval?
- Exceptions: what happens when instructions are unclear or a check is unavailable?
- Accountability: who decides whether to continue, and who verifies the result?
These questions also help with simpler automations. Written answers support design, testing and training for the people who will operate the process.
How it relates to Corpilus Shield
Shield focuses on an application and its inputs, outputs and triggered actions. Qronos is being developed to check an agent’s behaviour throughout a task. They address different areas; Qronos is not a new name for Shield.
For your own project, map the path from the initial brief to the outcome. Mark where information enters, where a proposal is prepared and where a change is made. Then decide which checks you need and who will operate them.
Bring a scenario to the discussion
Start with one task described in plain language: input, expected result, permitted systems and the step a person must confirm. Add an example where the process should finish without taking action.
You can use that scenario in a consultation or AI training. It helps separate the value of automation from the permissions you want to grant it. If you are interested in Qronos development, contact us through the product page; availability will be confirmed separately.
