Curate department memory
Review what your team proposes, keep the department's facts correct, and give every Talent in it the same answer.
Department memory is the shared page your department's Talents read before they work. Get it right once and everyone in the department stops re-explaining the same thing to their own Talent.
You can curate it if you hold the manager seat on that department. Admins and the workspace owner can curate any active department. Everyone else in the department proposes, and a curator decides.
Open it
- Manager: sidebar, Manager group, Department memory. It follows the department your Manager group is currently on.
- Admin: Team, Departments, open the department, then its memory.
- Member: sidebar, Memory, then the department scope. They get an add and edit form that submits proposals.
The page
Knowledge is filed under six sections, in this order: Overview and mandate, Priorities, People and ownership, How we work, Tools and standards, and the optional Challenges and dependencies.
Each entry is a Fact, a Decision, or an SOP. Keep each one to a single short sentence. A page of clean one-liners beats a wall of prose, because the Talent quotes the line it needs rather than the whole page.
Accept a proposal
- Open Department memory for the department you manage.
- Work through the pending proposals. Each one shows the change proposed, what it targets, the current version of that page, and what differs.
- Read the delta, not just the new text. If it is nearly right, correct the wording and the type as you accept it.
- Accept, or send it back.
Members never see pending proposals and never see who proposed what. They see the approved page.
A worked example
Someone in Client Services proposes an SOP: "Weekly client update goes out Monday 9am from the CRM pipeline, copied to the account lead." You accept it into How we work.
From the next turn, when anyone in Client Services asks their Talent to draft the weekly update, it already knows the day, the source, and who is copied. You did not have to touch anybody's Talent to make that true.
Editing and undoing
- Accepting an edit creates a new version. The old one is kept, not overwritten.
- Archiving hides an entry and is reversible. Nothing accepted is destroyed.
- Old links keep working. A link to a superseded entry resolves forward to its current version.
When a Talent proposes a department fact on its owner's behalf, it always asks that person for approval first, every time. Shared knowledge is never written silently.
What to check
A member sees an empty state. They hold no department, or their department was archived. Put them in an active department on the Directory tab.
"This changed since you started." Someone else edited that entry while your review was open. Reload the item, read the current version, and decide again. The conflict is deliberate, so you never accept a change against a page that has moved on.
You can read a department but not curate it. Your manager seat is on a different department. Seats are per department, and admins get every active one.
Curation controls are gone entirely. The department was archived. Archived departments are closed to writes.
The whole team still gets the old answer. Check the entry is accepted rather than pending, and that the person asking is in that department. Memory is scoped to the asker's current department, resolved at the moment they ask.