Why a channel coworker beats an onboarding wiki
Wikis rot. Channel memory doesn't — it is the record of what actually happened. Because Yasmine keeps per-channel memory, she remembers the pricing decision from March, the naming convention argument, where the launch checklist lives. A new hire asking "why do we invoice on the 15th?" gets the actual answer with the actual context — instantly, without interrupting anyone.
What the new hire hands her in week one
"Summarize what this team shipped in the last quarter."
"Where is the brand voice guide, and what are the three rules I'll get pinged for breaking?"
"Who owns the Stripe integration, and what's its current state?"
"Draft my intro post for #general in the team's tone."
What the manager hands her
"Build a 30-day onboarding plan for a new content marketer from what this channel knows."
"Every Friday, ask the new hire for blockers and post a digest to me."
"Create the checklist: accounts, tools, intro meetings — and track what's done."
Safe by construction
A new-hire-facing AI touches HR-ish territory, so the guardrails matter: each workspace runs in its own dedicated microVM, memory stays per channel (what #finance knows never leaks into #general), and anything that writes — sending, inviting, changing — waits behind per-tool approval. Runs on your keys or your Claude account; security details here.
Day-one context for every new hire. Free 7-day trial, no card.
TY
The Yasmine Team
Yasmine
