Cabi.Chat Graph — Handles, mentions and relations
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, digits and _ . -, up to 64 characters. Projects keep bare handles; other types get a short prefix that says what they are: a. articles, ws. workspaces, rub. rubrics, p. posts, b. boards, doc. docs, sh. sheets, c. coupons, camp. campaigns, l. access links, o. oracles, ag. agendas, api. endpoints, rm. rooms, tgg. Telegram groups. Type the name, the prefix is added for you. Renamed a card? Its old handle keeps leading to it, so shared links do not break.
Reserved names. Handles that start with cabichat or cabi (and similar spellings), and handles that start with _, belong to Cabi.Chat's own cards. cabi-… is a short form: it opens the card named cabichat-….
Mentions. Write a card into any text and it becomes an edge:
@handle, or@article/<nonce>with the type spelled out;- a link to the card on cabi.chat;
- an empty Markdown link,
[](https://cabi.chat/article/<nonce>): it renders as the card's own title, in the reader's language, and follows the title when it changes. This is how these docs link to each other.
Every mention is recorded on both sides: a card shows what it mentions, and the mentioned card knows who mentions it. Mentions are how a knowledge base links up, how oracles walk from one card to the next, and how search engines see your backlinks. Placing a card on a flow board mentions it too. Cabi.Chat Graph — Data types
Relations. A relation is an edge with a meaning: this article implements that decision, this one supersedes the old one, this one is derived from a source. The label is a rubric with a reading for each side: seen from the other end, "derived from" reads "source of". You relate a card you can edit to any card you can read. Relations are set through the API. Cabi.Chat Graph — Rubrics
Never a backdoor. A handle, a mention or a relation never opens a card. Each exists for a viewer only when the viewer can read everything it touches; anything else is not shown and not even counted. Cabi.Chat Graph — Card Policies