Documents
Documents is the project’s file and writing surface. It is also the mouth of the knowledge base: almost everything you add here is chunked and indexed so Ask and the assistant can cite it.
Open it from the project section nav. Tabs: Files · Briefs · Notes · Specs · Meetings · Decisions. Files is the default. Managers also see knowledge-gap notes (who asked, on which surface).
Upload into the shared tree, or into a managers tree for budget and pricing documents.
- Manager-only files are invisible to members.
- Manager-only files are not ingested. Ask will not cite a pricing PDF you hid on purpose.
- Folders nest (depth is capped). 25 MB per file.
- Each file shows an ingest status: pending, indexing, ready, skipped, or failed. The open folder lists the newest files first. Load more shows the older ones. The status on a file updates in place while it is indexing.
If a file stays on failed, open it and check the error. Password-protected PDFs and odd encodings are the usual cause.
Briefs
Section titled “Briefs”A brief is a file marked as the client brief. Keep one obvious live brief. Reviewed specs can become briefs.
Ask and the assistant weigh the brief. A folder of twelve “final_v7” files without a brief flag is how answers go vague.
Project notes for working memory. A note can be written by a person or compiled from an AI answer. Compiled notes are drafts until someone promotes them. They are searchable immediately.
Specs (Studio+)
Section titled “Specs (Studio+)”Generate a spec from the current knowledge, then review it. A draft is not trusted material. A reviewed spec is, and it can become a brief.
Do not generate a spec on an empty project. Add files or a transcript first.
Meetings
Section titled “Meetings”LiveKit call transcripts and pasted or uploaded notes from Meet, Zoom, Granola, or similar. Import is available on every plan. Live capture needs Team. See Meetings and transcripts.
Propose from knowledge
Section titled “Propose from knowledge”Files, notes, and transcripts here are what the pack reads. After they are indexed, a manager taps Propose from knowledge on Ask (not on Files).
InHive drafts features, tasks, and open decisions. Every proposal has to quote something actually in the knowledge. Ungrounded ideas are dropped. You approve what stays.
- Available on every plan (this path is how a messy kickoff becomes a board).
- Empty knowledge → error. Add material first.
- Cap is generous but finite; a huge dump may need a second pass.
This is not the Monday importer and not a live sync. It is “read what we have, propose a first pack.”