Build a company brain your team owns.
Open-source operating workspace for Claude Cowork: decisions, state, next steps, and routines in team-governed files.
/plugin marketplace add yempik-ai/cowork-os/plugin marketplace addyempik-ai/cowork-osStandardize how we take important decisions. Improve clarity, traceability, and execution speed.
2026-07-14
See: context/goals.md, processes/decision_process.md
Create a decision log for decisions already taken
A team does not only need to know what happened. It needs to know what is open, who decides, and which rule applies.
| Native memory | Operating workspace |
|---|---|
| Useful for preferences and recurring facts. | Files readable by people and agents. |
| Hard to govern as a team. | Decisions and routines with one source of truth. |
| Does not show process, owner, and due dates. | Versionable, portable, controllable. |
Memory remembers preferences, people, and patterns. cowork-os does not try to remember more: it puts state, decisions, owners, and reviews into files the team can govern.
Remembers preferences, people, and patterns already seen.
Keeps state, decisions, processes, and next actions on files.
Reviews, approves, and owns the company brain.
Reads the files and works from explicit criteria.
A starting structure opinionated enough to move, simple enough to stay yours.
| 01 | /context | Identity and goals | Company, team, principles, boundaries, and current goals. | goals.md |
| 02 | /decisions | Decisions with a lifecycle | Candidates, active decisions, and a weekly Decision Radar: status, owner, and review date. | decision_radar.md |
| 03 | /signals | Capture where they happen | Daily sweeps read email and Slack and extract the decisions and commitments made there, ready to confirm. Private, never committed. | signals/sync-state.md |
| 04 | /processes | How work happens | Process index, recurring flows, and operating standards. | decision_process.md |
| 05 | /routines | Continuous updates | Weekly review, memory update, and maintenance routines. | weekly_review.md |
| 06 | /pipeline | Sales layer | Sales rules, follow-up templates in your voice, and a deal radar that feeds the brief. Drafts stay drafts. | pipeline/rules.md |
| 07 | /skills | Reusable skills | Instructions for recurring work the team performs. | senior_strategy_architect.md |
| 08 | /knowledge-transfer | Tacit knowledge | Interviews, notes, and transformation of knowledge into files. | interview_notes.md |
Install the plugin, answer a few questions, and get a first structure to correct instead of invent.
/plugin marketplace addyempik-ai/cowork-osAdd cowork-os from the Claude Cowork marketplace.
Describe company, team, processes, and recurring decisions.
The workspace creates folders, templates, and first instructions.
Routines keep the company brain alive over time.
The value is not saving files. It is turning a messy request into a traceable decision.
Should we change the process or add an agent?
Proposed decision with criteria, trade-offs, what not to do, and next action.
cowork-os comes from how Yempik runs its own company brain: markdown files, explicit decisions, and maintenance routines.
“The important thing is not remembering more. It is leaving the team a system that can be read, discussed, and improved.”
| source | first | owned |
|---|---|---|
| open | file | team |
No. cowork-os is the open-source project. This page explains what it does and points to the repo. Company Brain Starter remains the offer page.
The plugin is designed for Claude Cowork. The file structure stays readable and reusable outside the plugin too.
No. Memory remains useful for recall and preferences. cowork-os is for team-governed operational work.
In your workspace files. The point is to make the company brain portable, inspectable, and not locked inside a black box.
Start from the open-source kit and adapt it to how your team decides, works, and updates context.