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 ask both people to confirm what happened.

Explore how it works Where it began

Proposed first pilotBGI CommonsFirst 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 people.
The wrong 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 offer two hours of UX feedback for a sprint team this week.”

ArunThursday · Need

“We need someone to review the onboarding for our sprint demo.”

The posts arrive days apart. Utsa keeps the relevant context.

Grounded in real postsMatch reasons refer to what participants actually wrote.

Choice at every connectionA suggestion never volunteers someone to do the work.

Confirmation, with limitsBoth confirm the same outcome. Silence is not a negative rating.

03 / The product

One Utsa.
Different community homes.

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 · Attestation

Attestation means both participants confirm a specific outcome.

Interaction surfaces

Telegram · first channel in development
Discord · earlier prototype exploration
Community websites · proposed integrations

Communities and organizations

BGI Commons · proposed first pilot
SingularityNET & 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.”

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

NeedFeedback on a sprint demo

OfferTwo hours of UX support

Concept only. Telegram and the portal would access the same community coordination records.

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.

Project intake

A project starts with its goal, open needs, available contributions, timing and sharing choices. A public GitHub link can add context.

Try the project questionnaire

Preview and review a draft. This concept does not upload a project or connect to GitHub.

Future direction

Other communities could use Utsa through their own channels and websites. Each community would have its own records and permissions; sharing across communities 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.

Informed by OfferNet, Utsa developed into an independent coordination agent that remembers needs and offers and helps people connect.

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

An initial MVP and user-study plan for community working groups.

June 2026

Discord sprint build

A working agent demonstrating matching across time at BGI Sprint I.

Current development

Telegram pilot

Preparing Utsa’s own bot and the complete service loop for BGI Commons.

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 first step is to test Utsa in its own Telegram bot, then in the Commons group once private delivery is ready.

What we will measure

Completed exchanges
confirmed by both people.

Accepted connections and unresolved follow-ups 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?Follow up after an introduction and record what both people confirm.
04
Can people stay in control?Correct a record, withdraw an offer, stop participating, 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 & foundations

Product thinking.
Community knowledge.
Shared engineering.

Synthia JahanCreator, designer & Product OwnerProduct 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 & collaboratorsThe implementation foundationThe current build uses OmegaClaw’s persistent memory. Dhaval Khatri engineered the Sprint I Discord integration; the Telegram work continues with implementation collaborators.

Case studyRead the Utsa design case study 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 Telegram pilot.

A need today.
An offer remembered.
A connection that matters.

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 people.The wrong moment.

A connection witha reason to happen.

One Utsa.Different community homes.