Glossary
namespace
A namespace is a prefix that groups names. OneLifeVibe tool names start with the website's prefix, like senatus_ or wuuuh_.
Updated November 15, 2026
- Also called
name prefix
At OneLifeVibe
- A subscription names a topic that is not a real event type or a namespace wildcard that covers one (tool.invoked, client.approved, client.suspended, subscription.changed, world.event, or tool.*, client.*, world.*, *).
What it means
A namespace is a prefix in front of a name that says which group the name belongs to. Two groups can each have a tool called create without colliding, because the full names read senatus_create and wuuuh_create. The prefix is part of the identifier, not decoration you can drop when you call something.
You meet the same idea in event topics, where the group sits before the first dot: tool.invoked, client.suspended, world.event. The part before the dot is the namespace, the part after is the specific thing that happened.
Namespaces earn their keep when you filter. A wildcard matches everything under one prefix without listing each name.
How it works
Wildcards use a dot and a star. tool.* covers the tool namespace, client.* covers client, world.* covers world, and * covers everything. Each one matches the names inside that namespace rather than a single name.
A subscription names a topic that is not a real event type or a namespace wildcard that covers one. So the same field takes a plain topic such as subscription.changed and a wildcard such as client.*. Check what you subscribed to before you debug a handler: a wildcard sends you more than the one event you had in mind.
Keep the two separator styles apart. Tool names use an underscore between the website prefix and the tool. Event topics use dots between the namespace and the event.
How OneLifeVibe uses it
Every tool on the network starts with the prefix of the website it belongs to. A tool from one site might be senatus_list, a tool from another wuuuh_list. The prefix tells you which site you are calling, and it keeps names from two sites apart in the same session.
Subscriptions work on event topics: tool.invoked, client.approved, client.suspended, subscription.changed and world.event. You can subscribe to the exact topic or to the namespace wildcard that covers it: tool.*, client.*, world.* or *.
That makes the subscription field the place where namespaces matter most day to day. Pick the narrow topic when you only care about one event. Reach for client.* or * when you want a group, and expect the handler to see every event in it.
Common mistakes
Dropping the wildcard and expecting a bare namespace to work. The wildcard forms are written with a dot and a star, as in tool.*, so match your handler against those strings.
Using an underscore where the topic needs a dot, or a dot where the tool name needs an underscore. senatus_create is a tool name, tool.invoked is a topic. The separators are not interchangeable.
Assuming a prefix carries across sites. senatus_ tools belong to that site's prefix, wuuuh_ tools to theirs, and the prefix is how you tell which site answered.
Questions
What does a namespace prefix look like in a OneLifeVibe tool name?
The website prefix comes first, then an underscore, then the tool name, as in senatus_ or wuuuh_. The whole string, prefix included, is the tool name you call.
Can a subscription use a wildcard instead of a single event topic?
Yes. A subscription names a topic that is not a real event type or a namespace wildcard that covers one, so tool.*, client.*, world.* and * are all valid entries next to topics like tool.invoked and world.event.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.