Skip to content
Imagio Labs

Work / 05 AI Orchestration / Agent Intelligence

SONJA

The assistant meets you in the work

One assistant, defined once, given a door in every place the work already happens.

SONJA · In development

01 The engagement

Sonja is an AI orchestration module for property operations and the ORB ecosystem. Designed as a manager and agent-handling assistant, Sonja can operate through multiple interfaces including Telegram and native ORB chat, helping connect conversations, decisions and actions across the system.

02 The surface

SONJA — signal to action

GENERATED COMPOSITION · NO APPROVED SCREENSHOT EXISTS, AND NONE HAS BEEN INVENTED

In development. This case study is complete when the work is.

03 The problem
and the idea

The problem. An assistant that lives in one chat window becomes one more place to go. It is asked a question where the work is not, the answer arrives where the work is, and the person has to carry it across. The deeper problem is that an assistant designed per surface drifts: two front ends built separately become two assistants with two ideas of what they are allowed to do.

The idea. Assistance should not be trapped inside a single chat window. Sonja is defined once — what it may do, what it reports, what a manager must be able to keep legible — before it is given a single door.

04 The work

What we did,
in order.

SignalIntelligenceAction

01 · The capability comes before the interfaceWhat the assistant is allowed to do, what it reports back, and what a person supervising the work has to be able to keep legible at a glance. Those three answers are what every surface is then built to express, so the surfaces cannot disagree with each other.
02 · Reports, not narrationThe assistant reports what has changed — work moved, work waiting, work finished — rather than narrating continuously. A stream of activity is interesting for a moment and unusable after it; a report can be scanned, acted on and come back to later, which is what an operations context actually requires.
03 · Surfaces inherit, they do not decideEach interface gets its own density, its own register and its own idea of when to speak, but it may not change what the assistant is for. Keeping that boundary explicit is what stops an orchestration layer decaying into a collection of chat integrations.

05 Craft & sequencing

The decisions,
and why.

Why orchestration is the productThe hard part of an assistant that spans interfaces is not the answering; it is deciding what is in scope and reporting it consistently from more than one place. So the module, not the chat window, is the thing being designed.
Why there is no face on it hereThe brief forbids a robot face, a glowing brain, a circuit board and generic AI stock, and it is right to: none of those depict an orchestration module. A single signal that enters, is handled, and leaves as one action is a truer picture of what the thing does than a head is.
Why this case is unfinished, and says soSonja is still being built. Publishing a study of it now would be publishing a claim about work that has not been tested, so the copy describes the design and stops there. The full study appears when the work is ready to share.

06 The scope

The part we held

Concept and system design; orchestration experience; assistant interaction design; multi-interface planning; agent and manager workflow structure.

ClientFlatr — internal
StatusIn development
PublicationInternal — no public link and no public screenshot exist for this system

07 Through the method

Observe. Think.
Imagine. Launch.

OBSERVEAn assistant that lives in one chat window becomes one more place to go — asked where the work is, it answers where it is not.
THINKAn assistant defined per surface drifts: two front ends become two assistants with two different ideas of what it is allowed to do.
IMAGINEDefine Sonja once — what it may do, what it reports, what a manager must be able to keep legible — before giving it a single door.
DESIGNThe capability before the interface. Surfaces inherit the definition rather than each deciding it.
BUILDReports rather than narration, written to be scanned in the seconds a manager actually has.
TESTWhy this case is unfinished, and says so — the published route speaks and works; the onboarding does not exist yet.
LAUNCHIn development. Reachable through Telegram and native ORB chat when it ships.

In development. This case study is complete when the work is.

← ORBXTRA →All engagements