Knowledge and Ask

Where the activity log records what happened, the knowledge base records what was said and written: files, notes, features, decisions, reviewed specs, public chat archives, and transcripts.

It is scoped to the project. Asking on project A cannot see project B. That is a tenancy rule, not a preference.

What gets in

Source	When it is indexed
Shared files and notes	After upload / save
Features and decisions	When they change
Reviewed specs	After review
Public project chat	Archived incrementally (Studio+, because chat is Studio+)
Call and imported transcripts	After the meeting is indexed

Stays out: private chat, manager-only files, draft specs, hidden assistant sittings.

Ingest status on a file is the truth. Ready means Ask can cite it. Pending / indexing means wait. Skipped / failed means it will not appear in answers until you fix it.

Ask (Studio+)

On a project, open Ask. If the hive set an AI display name in AI settings, that name is what you see; otherwise it is just Ask. In Chat, Ask sits under that project’s channel; the project name in the conversation bar opens the project.

Shared org procedures and information (how you deploy, review, invoice; rate cards and definitions) live under the avatar menu → {hive name} knowledge. Switch lists in the top bar, then search or filter by category. Everyone may add general entries and maintain their own. Admins and selected people may also add and search restricted entries. Each row shows whether it is general or restricted. Connected agents can list and read those entries with list_org_documents / get_org_document, and file new typed entries with create_org_document, under those same rules. Search hits stay short excerpts; get_org_document is the full body.

In Chat, org Ask sits under Team channels and answers from the shelf the asker may see. Project Ask also uses that shelf as background: hive procedures and information can be cited next to project files. Project sources win when they speak to this client; hive sources answer how the hive works. Restricted entries stay hidden unless you can see them on the shelf.

Who may add and search restricted entries is set in Organization settings → Org knowledge (admins).

Ask in plain language: “What did we decide about the CMS?” “What is still unknown on checkout?”

Answers cite sources. Treat citations as the product. If there is no source, the answer is a guess — do not ship it.
Tap useful / not useful under an answer. That is how the hive learns which retrieval helped. Managers can see ask quality on the memory-health tile in settings.
Ask does not command. It does not create tasks or change status. For writes, use the assistant.

If Ask keeps missing, the usual cause is not the model: the brief is not in Documents, the decision is only in someone’s head, or the file is manager-only.

Save this answer (compiled memory)

A good answer can become a compiled note or a proposed decision.

The draft is searchable immediately and tagged as needing review.
Promote when a human agrees. Only then does it become an agent rule (a compiled note becomes an ordinary human note; a proposed decision becomes accepted).
Auto-compile (Team, off by default) writes the same kind of draft. It never promotes.

Sittings of the assistant are not memory. If it should last, save it.

Specs (Studio+)

From Documents → Specs, generate a spec from the current knowledge, then review it. Reviewed specs feed the next ask, the next handoff, and agents.

A spec in generating or failed is not knowledge yet.

Handoff (Studio+)

Handoff on a project writes current state, next steps, risks, and open decisions — from the activity log and the ontology, not a chat dump. Use it when someone else is taking the week, or when an agent needs a briefing.

Documents · Assistant · AI settings · Features and decisions