Cabi.Chat Graph — Card Policies
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 rights — what a reader may do with it.
Visibility
- Private — yours only, absolutely. No access link, no shared workspace, no grant ever reveals a Private card, and no oracle's model ever reads one, not even your own oracle's. Your own campaigns can still use your Private cards; only what an oracle reads must be Unlisted or Public. Every card starts Private.
- Unlisted — shared privately. The card stays out of public search and listings, but reaches the people you choose: through a grant or an access link on the card itself, or on any workspace that contains it, at any depth Cabi.Chat Graph — Sharing with access links. A card's number alone, or a Public workspace around it, gives no reach. Use it for team material and for everything your oracles must read.
- Public — free to read and discover: by other users, by third-party oracles, by search engines.
Unlisted and Public cards must be anchored to a project, and a card is never more visible than its project: an Unlisted project cannot hold a Public card. Cabi.Chat Graph — Data types
Publicity fine-tunes your public exposure.
- Ecosystem (default) — only signed-in users see the card; anonymous visitors are denied, even with an access link. Reasonable for semi-sensitive content.
- Everyone — anonymous visitors too. Only in this mode can crawlers such as Google, Bing and Yandex index your content, and only in this mode does an anonymous visitor holding an access link see the card. How such cards get indexed: Cabi.Chat SEO — Getting indexed by search engines
Audience rights are three bits set per card, the way files have them.
- Read — a reader sees the whole card and may copy it. Without it a reachable card shows masked: title and teaser only, the rest stays closed.
- Write — a reader may edit and operate the card: content, settings, and starting or stopping an oracle or a campaign. Counts only on Unlisted cards and only for signed-in readers; on a Public card it never applies, so the open web cannot rewrite you.
- Execute — the card may be assigned into a field of another card, so the system uses it while that card works: groups as a campaign's sources, articles and workspaces as an oracle's instructions, endpoints as tools, agendas as the mind behind an oracle, a project as the anchor of a campaign or an oracle. Starting and stopping needs Write. A Public project never gives Execute; a project's Execute is shared only by grants and links.
What grants and links add: Cabi.Chat Graph — Sharing with access links
The owner's word is final. A share counts only when it comes from the card's owner: a shared workspace or an access link carries only the sharer's own cards. Place someone else's card into your workspace and share it, and that card does not travel with it: readers see it only if its owner already let them in. And no share, by containment or by link, ever reveals a Private card. Cabi.Chat Graph — Workspaces and containment