Help

What this is

Casium Knowledge is the team's shared memory: decisions and why we took them, gotchas someone already hit once, and conventions for how we work. Each entry is a record in the team's database; every change is an event by the person who made it.

Developers and the owner record entries from Claude (casium_remember). The BA confirms business rules here on the web or from Claude (casium_confirm). Everyone's Claude reads the entries before answering about Casium (casium_recall, casium_context), so a confirmed rule reaches every session.

How to connect

Open your invite link once. It signs you in here and shows the Connect page with the exact command for Claude Code and the steps for claude.ai, Claude Desktop and Cowork. The MCP endpoint is https://knowledge.casium.tech/mcp. Your personal token is the last part of the invite link: keep it private.

The three types

gotcha: Something non-obvious that cost time once. Record it right after the debugging that found it. Example: “Test migrations on a throwaway database, never the shared dev DB”.
decision: An option chosen after weighing alternatives, with the reason. Record it when the choice is made. Example: “Prices are matched by country + visa + case type”.
convention: How we work. Record it when someone corrects you, so nobody has to say it twice. Example: “Code comments: 1-2 lines, the why only, never ticket ids”.

Tracks: business and tech

business: a product rule the BA can check against a source (billing, cases, SKUs, wording). The BA or the owner confirms it. tech: code, infrastructure and process. Only the owner confirms it; the BA can still comment or open a dispute.

The track defaults from the scope (scope business → track business, any other scope → tech). Entries recorded by the BA are always business and start confirmed.

Scopes

be: Backend: API, services, database schema.
fe: Frontend: portal UI, design tokens, feature flags in the browser.
infra: Deploys, CI, servers, databases as infrastructure.
process: How the team works: tickets, pull requests, reviews.
business: Product rules, the BA's area. Example: “Approving an invoice locks its line items”.

The life of an entry

A new entry from a developer or the owner is unverified.
The BA confirms business entries; the owner confirms any entry. Confirming is final.
Anyone can open a dispute: outdated (it was true, it is not any more), wrong (it was never true) or comment (a question or note for the owner). The entry stays visible, marked ⚠, until the owner closes the dispute.
The owner closes it. Accept supersedes the entry, optionally pointing at the entry that replaces it. Reject keeps the entry and records why in its Discussion. A comment dispute can only be closed with reject.
A superseded entry is never deleted: it stays readable so the reason we once did it differently survives. Searches hide it unless asked.

Every step is recorded as an event by the person who took it; the History table on each entry page lists them.

History. Every change is an event: nothing is edited or deleted. The History table on an entry page shows each event with who did it, when, and the note they left.

The marks

✔ confirmed by the BA or the owner, with who and when.
? unverified: recorded but nobody has checked it against its source yet.
⚠ under dispute: treat it as uncertain and verify against the code or the spec.

Claude sees the same marks and lists confirmed entries first, then unverified, then disputed.

Who can do what

Everyone can search and record entries. This table is generated from the same permission check the server uses, so it is always current.

Action	owner	dev	ba
Confirm an entry	yes	no	business only
Open a dispute	yes	yes	yes
Comment on an entry	yes	yes	yes
Close a dispute	yes	no	no
Supersede an entry	yes	tech, or own business	no
Propose a feature	yes	yes	yes
Support a proposal	yes	yes	yes
Comment on a proposal	yes	yes	yes
Set a proposal's status	yes	no	no

own = an entry you recorded yourself.

User management is owner-only, on the /users page.

Searching

The Entries page has two boxes. text is a plain match: an entry is listed when its title, body or a tag contains those characters. search is ranked search: every word you type must appear, and the best matches come first. The search option of casium_recall works the same way. Both boxes keep the other filters.

How to write a good entry

Title: one line that states the fact (“Approving an invoice locks its line items”), not a topic (“Invoices”).
Body: the fact first, then Why: (the reason or the incident), then How to apply: (what to do differently).
Source: something a reviewer can open: a ClickUp task or comment, a spec page, a pull request, a file:line. The BA confirms against it.
One fact per entry. Link related entries with [[entry-id]].
Never record task status (which PR is open) or secrets; a password or token is rejected.

Proposals

Proposals are wishes for this tool itself (Casium product knowledge goes into entries). Use Propose a feature in the header, or ask Claude to call casium_propose; Claude then shows similar proposals that already exist.

Everyone can support an open proposal (one vote per person, withdraw any time while it is open) and comment. The person who proposed it counts as its first supporter.
The owner sets the status: open, accepted, declined or done, with a note.
The list shows open proposals first, most supported on top; closed ones below.

FAQ

An entry is wrong. What do I do?: Open a dispute on its page (kind wrong, and say where you saw the truth). Do not record a second entry that contradicts it; the owner resolves the dispute and links the replacement.
I am the BA and I disagree with a tech entry.: You cannot confirm tech entries, but you can open a dispute or add a comment. A dispute shows ⚠ to everyone's Claude until the owner closes it, which is how a business concern reaches a technical direction.
I lost my invite link, or it leaked.: Ask the owner to rotate your link on the /users page. You get a new link; the old link, token, connectors and web sessions stop working at once.
Can I delete an entry?: No. Nothing is deleted; an entry that no longer holds is superseded, and its history stays.
My change was refused with “secret scan rejected the write”.: The text looked like a password, key or token. Remove it and try again; secrets never belong here.

Tóm tắt (tiếng Việt)

Casium Knowledge là nơi cả nhóm lưu những điều đã thống nhất về Casium: quyết định (decision), lỗi dễ gặp (gotcha) và quy ước làm việc (convention). Claude của mỗi người đọc và ghi vào đây.
Kết nối: mở link mời của bạn một lần, rồi làm theo trang Connect. Phần cuối của link là token cá nhân, không chia sẻ cho ai.
Mỗi mục có track: business là quy tắc nghiệp vụ, BA xác nhận; tech là kỹ thuật, chỉ owner xác nhận.
Dấu: ✔ đã xác nhận, ? chưa ai kiểm tra, ⚠ đang có tranh chấp, hãy kiểm tra lại với code hoặc tài liệu.
Thấy mục sai hoặc đã cũ: mở dispute (outdated, wrong hoặc comment). Chỉ owner đóng dispute. Không mục nào bị xoá; mục cũ được đánh dấu superseded.
Muốn công cụ có thêm tính năng: bấm “Propose a feature” hoặc nhờ Claude gọi casium_propose. Mọi người có thể ủng hộ (Support) và bình luận; owner quyết định trạng thái.
Mất link mời hoặc lộ link: nhờ owner đổi link trên trang /users để cấp link mới; link cũ ngừng hoạt động ngay.