Your people, applications and AI. Working together.

00 · The request

It all starts with one sentence.

Someone describes what they need. Follow that request: it travels through Cosmos, Genesis and Orbit, meets an access boundary, then comes back as a result.

01 · Context — Cosmos

Start with the work you want to get done.

Work with available models and assistants in Cosmos. Use accessible documents and tools to prepare an answer grounded in the task at hand.

In this example, an invoice statement attached to the conversation is the source. Each part of the answer points back to the line that supports it.

Illustration: the request in Cosmos, a statement of three invoices and a contact record, connected to an answer in progress.

02 · Role — Genesis

Give your AI coworker a defined role.

Set its responsibility, instructions and available tools. Genesis helps you create specialized coworkers and organize them into teams where enabled.

The “Billing follow-up” role receives read tools: invoices, contacts, financial summary. You configure it, then decide when to hand it a task.

Illustration: a Genesis configuration sheet with the role, responsibility, instructions and read-only tools.

03 · Execution — Orbit

Delegate a task. Follow it through.

Start work, check its progress and return to the result. Orbit brings together autonomous tasks, schedules, memories and your AI coworkers’ capabilities.

The task moves from “Queued” to “Running” to “Completed”. A recurrence can be added as a scheduled trigger, if you configure one.

Illustration: an Orbit task assigned to the Billing follow-up role, with three steps and an optional recurrence.

04 · Access — Permissions

Define the scope of action.

Disable a tool category, allow read access or configure access to write actions. Available review mechanisms complement those settings according to your deployment.

Here, Business management is set to “Ask first”. Reads run. The proposed invoice creation is not executed: it stays pending approval, and the summary carries on.

Illustration: a proposed “Create invoice” action stopped at the access boundary while reading continues.

05 · Result

A result you can review.

The work comes back as a briefing: the invoices involved, the amounts and the points to check. The next decision stays with you.

Every amount in the briefing can be recomputed from the three invoices in the example.

06 · Applications

Applications for real work.

Three distinct use cases in one environment.