INDUSTRIES · WEB3 AND CRYPTO
Connect Web3 AI tools to project docs, governance posts and community knowledge. Keep private contributor material within its intended audience.
What did governance decide on the treasury proposal?
The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote. 1
Governance decisions
What's our Vesting schedule?
The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change. 1
Tokenomics
Can contributors access our private core-team plans?
Public documentation is available to contributors. Private core-team planning remains restricted. 1
Core-team docs withheld
Can our community agent answer from public docs only?
The community agent's key is limited to the public documentation collection. It cannot retrieve the core-team folder. 1
A community agent on public docs only
Your core teams and DAOs share answers with sources.
Core teams
What did governance decide on the treasury proposal?
On request
Which discussion and vote support the revised reporting schedule?
Before deciding
Source answer: The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote.
Sources: Governance decisions (Google Drive); Fern Collective · Supporting notes (Notion).
DAOs
What's our Vesting schedule?
Weekly
Which approved change affects the vesting schedule?
Before deciding
Source answer: The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change.
Sources: Tokenomics (Notion); Fern Collective · Supporting notes (Google Drive).
Community managers
Can contributors access our private core-team plans?
On request
Which public documentation can contributors read without core-team planning?
Before deciding
Source answer: Public documentation is available to contributors. Private core-team planning remains restricted.
Sources: Core-team docs withheld (Google Drive); Fern Collective · Supporting notes (Notion).
Agents
Can our community agent answer from public docs only?
Weekly
Which sources are outside the community agent’s permitted collection?
Before deciding
Source answer: The community agent's key is limited to the public documentation collection. It cannot retrieve the core-team folder.
Sources: A community agent on public docs only (Notion); Fern Collective · Supporting notes (Google Drive).
Core teams
Where can new contributors find our roadmap and working agreements?
On request
Who owns the roadmap, governance process and working agreements?
Before deciding
Source answer: The contributor guide links the roadmap, governance process and working agreements. Each section names its owner.
Sources: Contributor onboarding (Google Drive); Fern Collective · Supporting notes (Notion).
DAOs
Which sources did this agent access?
Weekly
Which agent scope should we compare with the recorded source accesses?
Before deciding
Source answer: The access record identifies each agent and the sources it touched. Review the request against the agent’s permitted knowledge scope.
Sources: The access record (Notion); Fern Collective · Supporting notes (Google Drive).
Read the governance record, original discussion and vote separately to reconstruct the treasury proposal decision.
Find the approved proposal and revised reporting schedule, with links to the original discussion and vote.
Search the tokenomics document and governance note to check vesting dates against the latest approved change.
Find the vesting schedule and dates in the tokenomics document, alongside the latest approved change in the governance note.
Check contributor access to public documentation separately from private core-team planning.
Use the public documentation available to contributors while private core-team planning remains restricted.
Check the community agent’s key scope before asking it for documents outside the public collection.
Find the key limited to public documentation, with the core-team folder unavailable to the community agent.
ONE CONNECTED BRAIN
Bring Google Drive, Notion and your uploads into one cited answer.
FOLLOW THE SOURCE
Open the citation. Read the original wording and surrounding detail.
PERMISSIONS IN EVERY ANSWER
Same question, different permissions. Review the request and sources in the access record.
Answers respect source access.
Set its scope. Revoke its key.
Review requesters, sources and access decisions.
Check provider data use and retention.
Connect your model to governed knowledge.
Review data handling, providers and international transfers.
Read the privacy policyLESS CONTEXT. LOWER COST.
HeyBrain sends only the context a task needs.
FAQ
The governance record approved the proposal with a revised reporting schedule. The decision links the original discussion and vote. Ask follow-ups in the same conversation and open each citation to check the surrounding detail, then share the source with colleagues who can access the same collection.
The tokenomics document contains the vesting schedule and dates. The governance note records the latest approved change. Connect the relevant Drive folder or Notion pages, or upload documents, then follow citations to their original passages from the AI tools your colleagues already use.
Connect Google Drive, Notion and document uploads; Claude, Cursor and Codex ask your company knowledge through HeyBrain MCP. Keep decisions and references available where your team works. HeyBrain supplies knowledge; agents use their own tools for actions requested by the user.
People and agents receive answers from sources they can open. Workspace rules restrict the audience; each agent has its own key and scope. Administrators review requesters, times and source references in activity records alongside workspace membership and source access rules.
Connect your team’s current brief, decision notes and working guide, invite the people who need them and ask a familiar question. Open its source citations before expanding the collection. Align workspace membership and individual agent scopes with each team’s responsibilities.
HeyBrain sends only the context a task needs instead of repeatedly passing whole documents to your AI tool. Use the context calculator to compare the amount you send and your input price. Your team shares the same connected knowledge across tools, so every new conversation can start with the relevant passages and their sources.
/ Get started today
