How we workaudience: the team that owns itcan recall
Financeconfidentialrefused
Step 1
Choose what a new hire can see
Audience access decides which collections reach new starters. Sensitive ones stay with the people who need them.
Audience accessUse cases/By team/Onboarding
New hires ask the memory,not the busiest person on the team.
The answers a new starter needs are spread across years of threads, docs and decisions. MeshTale lets them ask, shows the source, and keeps sensitive material out of reach.
Free tier, no card required.
Delivery team/How we workpeople + AI
- GOps meeting: move reports to Thursdayby
Dana·Granola call 
Reporting process v2by 
Marco·Confluence
#delivery: report timing questionby 
Priya·Slack thread
New starter FAQ, draftedby Muse·drafted summary
Financenot searchedLeadershipnot searched
Claudenew starter accessAsks
- Scope: Delivery team only
- Audience and sensitivity checks passed
- 2 memories cited, other workspaces not searched
Delivery team only
Reports moved to Thursday so clients have them before their Friday planning. It was decided in an ops meeting and written into the reporting process.
1GOps meeting: move reports to Thursdayby Dana
2Reporting process v2by Marco
Reporting process v2by MarcoDelivery team workspace · every memory keeps its author, human or AIIllustrative product animation
The problem
Every new starter asks why.The answer is usually in a thread.
A new hire’s first weeks are a stream of why questions, and the answers sit in old threads, docs and meeting notes. Either they interrupt someone senior, or they guess.
An example (fictional)
Sam joins the delivery team and asks why client reports go out on Thursdays. Three people give three answers, the original decision is in an old meeting note, and the newest version of the process doc contradicts it.
Where the answer wasExample data
A process docthat contradicts itselfThree different answersin three threadsGThe meeting where it was decidednever linked
Everyone was helpful. Nobody had the source.
Start with one team,then widen it when it works.
Three steps, each one a real part of the product. You keep working in the tools you already use.
G
Delivery team workspaceStep 2
Connect where decisions live
Bring in the wiki, the team channels and the meeting notes where the reasons were actually given.
ConnectorsTwo memories disagree. Which is accurate?
DanaThe newer noteby DanaKeepThe older documentsupersededOutdated
Step 3
Let them ask
Answers cite the thread or note they came from. When two sources disagree, a person is asked to decide which one stands.
Conflict alertsQuestions people actually ask,answered from the right place.
Ask it like a colleague
From any connected assistant. Every answer comes back cited.
- Why do we do it this way?
- Who decided this, and when?
- Where is the current version of this process?
- What should I read before my first client call?
Starts with the tools you have
Sources this usually begins with. Connect only what belongs in the workspace.
ConfluenceNotionSlackMicrosoft TeamsGoogle DriveGGranola
Jira
OneNoteAssistants and agents that can recall it
Claude
Gemini
CodexMuseWhen you may not need MeshTale
If your team is small enough that everyone sits together and the docs are current, asking a colleague may be the better tool.
Questions
They see what their access allows. Audience access and sensitivity labels decide which memories reach which people and assistants.
Older versions of the same source are superseded, citations say when something is outdated or not yet approved, and when two sources disagree a person is asked to decide.
No. Keep the handbook. MeshTale makes it, and everything around it, answerable with a citation.
Give every team its own memory,and every assistant the right one.
Start with one team. Free tier, no card required.
Free tier, no card required.