Does the chatbot have access to my memory cells?

No. It answers from published material about the protocol — documentation, pricing and the public standards work. It holds no key and can read no cell, yours or anyone else’s.

How does it avoid making things up?

It is grounded in a published corpus rather than answering from general knowledge, and where a question falls outside that corpus it points you at the relevant page on this site instead of guessing.

Why are only six of the eight tools in scope?

The two governance tools are held back until separately ratified. The six memory and sharing tools are the surface you actually use day to day.

What if it cannot answer my question?

Email ops@saihm.coti.global, or read /faq and /docs, which cover the same ground in more depth.

Ask SAIHM.

A chatbot that answers questions about the SAIHM protocol’s memory and sharing tools, grounded in the published source.

Use the chat widget in the lower-right corner of this page.

What the chatbot can answer

Six tools are in scope:

saihm_remember — persist an encrypted memory cell.
saihm_recall — retrieve and decrypt cells the caller is authorized to read.
saihm_forget — cryptographic erasure of a memory.
saihm_status — session status surface.
saihm_share — grant sharing access (Pro Fast / Enterprise Fast, or PAYG).
saihm_revoke_share — revoke a sharing contract.

Beyond the tools, it also answers questions about:

Pricing and tiers — subscription and pay-as-you-go rates, and how sharing is gated. See /pricing.
Open standards — SAIHM’s contributions at the IETF, W3C, and NIST, with a link to each.
Open-source assets — the reference and higher-capability packages published on npm under @saihm, and the runnable demos and framework adapters on GitHub under citw2.
The token-cost benchmark — the published, reproducible measurement of how much context-token cost a recalled working set saves on long multi-session runs.
Audience guidance and the public on-chain anchor history.

What the chatbot does not answer

Governance. The two governance tools are out of scope until separately ratified.
Internal implementation detail not part of the public protocol surface.
Operational keys, internal roles, or non-public infrastructure.

The chatbot will redirect you to the relevant route on this site rather than guess outside its grounded corpus.

Common questions

Does the chatbot have access to my memory cells?: No. It answers from published material about the protocol — documentation, pricing and the public standards work. It holds no key and can read no cell, yours or anyone else’s.
How does it avoid making things up?: It is grounded in a published corpus rather than answering from general knowledge, and where a question falls outside that corpus it points you at the relevant page on this site instead of guessing.
Why are only six of the eight tools in scope?: The two governance tools are held back until separately ratified. The six memory and sharing tools are the surface you actually use day to day.
What if it cannot answer my question?: Email ops@saihm.coti.global, or read /faq and /docs, which cover the same ground in more depth.