Skip to content
Vareon

A stale skill removed, its dependants checked.

A stale or wrong skill is removed, and what depended on it is checked again.

Persistent intelligence. It runs On an authorised request.

The template changed. The old skill goes, and what used it is checked.

A skill writes release notes in last year’s template, and two things depend on it.

Step 1 of 4: In use

The next release notes use the new template.

With the stale skill gone, nothing goes out in last year’s style. The notes go to your AI with the new template until a new skill is proven.

Step 1 of 3: Release 4.2

Release 4.2 needs its notes.

From the day it went stale to the day it was replaced.

A skill can go stale without failing outright. Once someone notices, it is removed, and what depended on it is checked straight away.

Step 1 of 5: Proven

In January, the release-notes skill is proven and starts writing every release’s notes.

Each thing that relied on it is checked on its own.

Everything that used the skill is checked again: what still holds carries on, and what relied on the old style waits for a new skill.

Step 1 of 3: The changelog

The monthly changelog never needed the old style, so it carries on unchanged.

See it on your own work.

From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.