A coordination agent, in development

Coordination that
travels with community.

Utsa is a portable coordination agent for communities.

Being developed to remember offers and needs over time, suggest useful matches privately, and check in on the date each person chooses until both confirm what happened.

Explore how it works Where it began

Proposed first pilotBGI Commons First channel in developmentTelegram

Utsa's mandala, with concentric gold, rose and teal rings radiating from a shared centre — উৎস · Utsho“Source” in Bangla

OfferNeedMatchConfirm

01 / The reason

The right person is often there,
just not at the right moment.

A community can hold the skills it needs and still miss the connection. Offers disappear into the scroll. Needs arrive later. Finding the fit depends on someone remembering both.

Utsa is being designed to carry that context across time, so a new need can find an earlier offer, and people can collaborate beyond the circle they already know.

02 / The experience

A connection with
a reason to happen.

Utsa coordinates. People decide. Explore an illustrative exchange, from the first posts to a shared outcome.

BGI Commons · Community conversationExample

MayaMonday · Offer

“I can give two hours this week to help a sprint team get their agent running on OmegaClaw.”

ArunThursday · Need

“Our team is new to Omega. We’d love someone to walk us through integrating our sprint agent.”

The two posts arrive days apart, and Utsa remembers both.

Grounded in real postsMatch reasons quote what participants actually wrote, and the claim is drafted from both posts.

Choice at every connectionA suggestion never volunteers someone to do the work. Either person can reword the claim or ignore it.

Each person sets the paceBoth say done to the same claim, on check-in dates each person picks. Silence is not a negative rating.

The match loop. A post leads to a match with a drafted claim; each person picks a check-in date; on that date Utsa asks where it is now. In progress loops back to the next date, and either person can add a new need. When both say done, the exchange is completed. Not a fit closes quietly, with an offer to thank them anyway. If someone goes quiet, one reminder follows a week later, then a quiet close, and they can rejoin new matches. — The whole loop, from a post to a shared done. Select to view at full size.

03 / The product

One agent that can work
in many communities.

Utsa owns the coordination logic, memory and identity. Each community provides a context; chat and website interfaces provide ways to reach it.

Utsa core, in development

An independent coordination agent

Offers, needs, matching, memory and attestation.

Interaction surfaces

Telegram, the current pilot channel in development
Community websites, as proposed integrations

Communities and organizations

BGI Commons, the proposed first pilot
SingularityNET and OpenStreetMap, illustrative website concepts
Other communities, future possibilities

01First deployment channel

In Telegram

Post an offer or need in the community. Receive a relevant suggestion in a private conversation with Utsa.

Utsa · Private chat

“Your request may fit an earlier offer. Here’s why, and here’s what it would be.”

Being developed for the BGI Commons pilot. Participants first open a private chat with Utsa.

02Proposed integration

Example integration: Commons portal

Utsa embedded inside an existing community surface: review suggested connections and see the status of your exchanges.

BGI CommonsPowered by Utsa

NeedA walkthrough of our first OmegaClaw integration

OfferTwo hours of OmegaClaw mentoring

Concept only. A future portal could access the same community records as the Telegram pilot.

Explore the inbox

The same private match experience, adapted for BGI Commons, SingularityNET and OpenStreetMap.

View community website examples

Interactive concepts with fictional posts. Future integrations, not announced partnerships.

Permissions

Each community would keep its own records and permissions. Any cross-community sharing would require explicit consent.

04 / The origin

The question began
with volunteers.

2014

VanVolunteers, Vancouver

Original paper prototype with usability annotations. Select to view at full size.

How can someone’s willingness to contribute find a place where it is needed?

Synthia Jahan explored that question through VanVolunteers: a concept for discovering volunteers, understanding interests and availability, and making contact.

Utsa was born while Synthia was volunteering with SingularityNET, drawing on ideas she had explored earlier through VanVolunteers. She joined SingularityNET professionally in December 2025.

OfferNet gave that earlier question a coordination framework, and Utsa developed from it into a product for community matching and follow-through.

View the earlier screen sketches View the volunteer flowchart

2014

The seed

VanVolunteers concept, paper prototypes, and participation flow.

2025

Utsa is born

Born during Synthia’s volunteer work with SingularityNET. Early interface and identity; presented at the BGI Summit in Istanbul.

March 2026

Mattermost proposal

A proposed MVP and user-study plan for community working groups; it did not ship as a production surface.

June 2026

Discord sprint build

A working agent demonstrated through Discord at BGI Sprint I, showing matching across posts made at different times.

Current development

Telegram pilot

Utsa’s own Telegram bot for the proposed BGI Commons pilot, with check-ins on the date each person chooses.

05 / The first pilot

Learn with
BGI Commons.

BGI Commons will be Utsa’s first pilot community. The goal is to learn whether remembered offers become useful collaborations.

In development, October 2026

From a working demonstration
to an everyday service.

The next step is to test Utsa in its own Telegram bot, then bring it into the Commons group once private delivery is ready.

What we will measure

Completed exchanges
confirmed by both people.

Accepted connections, claims people reword, and check-ins left open will help explain where the journey works and where it breaks.

What the pilot needs to establish

01
Does Utsa find a useful fit?Recognize needs and offers, retain their context, and explain relevant suggestions.
02
Does private delivery work?Reach participating members reliably, with permission and clear choices.
03
Does the loop close?Agree a claim at the start, check in on the date each person picks, and record what both people confirm.
04
Can people stay in control?Reword a claim, correct a record, stop participating, rejoin later, or request removal.

What “attestation” means here: both participants confirm the same completed exchange. It records shared activity; it does not certify quality or create a public rating of a person.

06 / People and foundations

Who is building Utsa

Synthia JahanProduct Owner and designerProduct scope, interaction design, visual identity, agent behaviour, knowledge design, and pilot experience.

OfferNetThe research foundationUtsa translates Ben Goertzel’s OfferNet vision into a practical coordination experience.

OmegaClaw and collaboratorsThe implementation foundationThe current build uses OmegaClaw’s persistent memory. Dhaval Khatri engineered the Discord API integration for the Sprint I prototype.

Case studyExplore Synthia’s design work Open-source projectRead the Utsa repository Early conceptExplore the interface study

The early interface study explores a broader vision, including reputation and network views. Those screens are concepts, not features of the current pilot scope.

Helping a new need
find an earlier offer.

Utsa is being developed to help communities turn willingness into shared work.

Talk with Syn Get involved

hello@synthiajahan.ca

Coordination thattravels with community.

The right person is often there,just not at the right moment.

A connection witha reason to happen.

One agent that can workin many communities.