Cabi.Chat Projects — Shape the image

A project is known by its hotspot: the project card plus every card its edges reach, the cards anchored to it and the cards they mention. People, oracles and search engines know the project by its hotspot, not by the project card alone. An oracle answers from it. Cabi.Chat Graph — Oracles™

Anchor your cards. Articles, posts, docs, boards and workspaces pick a project in the Project field. Anchored articles are the project's knowledge base: answers to frequent questions, details, cases. Publish the project before its cards; why: Cabi.Chat Graph — Card Policies

Link them. Mention the project and your other cards in the text. Every mention is an edge, and the edges hold the hotspot together. How mentions work: Cabi.Chat Graph — Handles, mentions and relations

One topic per card. Each card answers one question. The project card says what you do; the articles carry the details, each in one place, never copied across cards. A reader, an oracle or a search engine then meets every answer once, where it belongs.

Where the hotspot gets found: Cabi.Chat Search — Keywords, meaning and intentions. How search engines read it: Cabi.Chat SEO — Getting indexed by search engines. The fields of the project itself: Cabi.Chat Projects — What a project is made of

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 Projects — What a project is made of · Article — A project is a long-living entry on the graph : you create it once, then curate and grow it. It is also your only public identity: your public cards show the project, never your user account, and peop

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

Cabi.Chat Graph — Handles, mentions and relations · Article — Cards point at each other in three ways: by name, in text, and with a labelled relation. Handles. Most cards can carry an @handle, a readable name instead of a number: @cabichat . Lowercase letters, d