Cabi.Chat Search

Cabi.Chat Search is the graph's discovery engine. It is the other half of the platform's traffic: campaigns push a project outward to a new audience Cabi.Chat Campaigns; search brings the audience to the project. People come on their own, describe what they need in their own words, and the graph answers with the cards that fit: projects, articles, audiences, workspaces, rubrics.

One engine, every seeker. The search page, the landing prompt and oracles in conversations run on the same logic and the same data. An oracle that looks for a project for its correspondent finds what a person would find, within what its grants reach. Cabi.Chat Graph — Oracles™

Who sees what. Search, the landing and the map never show more than the card's policies allow. Anonymous visitors see Public cards open to Everyone. Signed-in users also see Public cards open to the Ecosystem, and in search they also find their own cards and cards shared with them. Private cards of others never surface, not even by their exact title. Cabi.Chat Graph — Card Policies

How it finds

How a query is read and ranked, and how to write to be found: Cabi.Chat Search — Keywords, meaning and intentions
Rubrics and public discovery: Cabi.Chat Search — Rubrics and discovery
Geo filter and preference: Cabi.Chat Search — Geo filter and preference

Where it shows up

The search page: a query, a card type, an engine, filters, and a map of the results that have a location.
The landing: link
The map: Cabi.Chat Map
Search engines: Cabi.Chat SEO — Getting indexed by search engines

Mentioned

Cabi.Chat Graph — Oracles™ · Article — An Oracle™ is an AI agent assigned to your project's hotspot. It carries that knowledge and answers for it on your behalf, grounded in the graph and serving your goals. What a hotspot is:

Cabi.Chat Search — Keywords, meaning and intentions · Article — A seeker rarely knows your words. They know their intention: "someone to fix my bike tonight", "a math tutor for my kid". Search reads every query in three ways. Exact. A card's title, its @handle, or

Cabi.Chat Search — Geo filter and preference · Article — Geo has two settings on the seeker's side. They do different things. The filter decides who is even in the search. It is a place in the rubric filter: a country, a region or a city from the Places tax

Cabi.Chat Graph — Card Policies · Article — There are three card policies you have to know about. Each decides its own axis. Visibility — who may ever surface the card. Publicity — whether anonymous visitors and search engines may. Audience rig

Cabi.Chat Landing · Article — Cabi.Chat Landing is the graph's front page. It is where a visitor arrives with no question yet: a search prompt, rows of public projects by industry, and a map. Nothing on it is placed by hand. It is

Cabi.Chat Campaigns · Article — Cabi.Chat Campaigns are the graph's executables. A project does not only wait to be found; it acts through campaigns. A campaign belongs to a project, runs on that project's oracles, and does one job

Cabi.Chat Search — Rubrics and discovery · Article — Rubrics tag cards with shared taxonomies. What a rubric is and which taxonomies exist: . This page is about how rubrics make a card discoverable. A card tagged with a rubric is found under it

Cabi.Chat Map · Article — Cabi.Chat Map is the graph on the ground. Every card you find that has a location is a pin, so a visitor can see who works where before reading a single line. Where you meet it Landing. Below the indu

Cabi.Chat SEO — Getting indexed by search engines · Article — Cabi.Chat SEO is how the graph meets search engines. Every public card open to Everyone is served to crawlers as a complete page: title, description, canonical address, language versions, social previ