The problem
You are the source of truth, and it does not scale. Why on-call works the way it does. Who owns the payments service now. What the team decided about the migration and why. New engineers ask you. A new AI chat may lack that context. So the same context lives in your head, a few Slack threads, and one doc nobody can find.
Write the team's context down once, for people and their AI
Put decisions, process, ownership, and runbooks in a shared team space. Connect it to Claude or ChatGPT through MCP, and each engineer’s connected assistant can retrieve the same shared notes. The reasoning behind how your team works stops being tribal knowledge.
What an engineering manager keeps shared
- Decisions folder: why you chose X, what you tried and rejected, the tradeoffs behind past calls
- Process folder: on-call, releases, incident response, review expectations
- Ownership map: who owns which service, who is backup, escalation paths
- Onboarding folder: the unwritten context every new hire needs in week one
You stop being the bottleneck
A new engineer connects their own AI and asks how deploys work, why the team moved off Redis, or who owns a service. It can retrieve the relevant notes to help answer without interrupting a senior engineer. Personal notes stay personal; only what you put in the team space is shared, and per-folder roles decide who can edit what.
Your team's context lives in your head. It doesn't have to.
What engineering managers keep in Hjarni
- Decision logs: the reasoning behind architecture and process calls, so nobody relitigates them
- Runbooks and process: on-call, releases, incidents, and reviews the whole team follows
- Ownership and escalation: who owns what and who to reach when something breaks
- Onboarding context: the tribal knowledge that usually takes a new hire months to absorb
- Team AI instructions: folder-level rules every engineer's assistant inherits
A shared brain, not another wiki
Shared notes still need maintenance. Your team’s AI can read them when someone asks it to check, so current sources help people get useful answers. Put architecture, decisions, and runbooks in a shared team space and each engineer’s connected Claude or ChatGPT can retrieve the same source. See Hjarni for Teams, or the step-by-step set up your team guide.