adding-project-context-workspace

# Adding a project-context workspace A workspace exists when a named person keeps an area current. The failure this prevents is a folder nobody owns: it fills up, goes stale, and becomes something readers cannot trust and will not delete. ## Procedure **Step 1 — Locate the knowledge base.** Read `${CLAUDE_PLUGIN_ROOT}/shared/locating-project-context.md` and resolve **KB**, then read `KB/conventions/ownership.md`. It owns the rules below and wins on any conflict. **Step 2 — Check it is really a new workspace.** Read `KB/docs/README.md`. If an existing workspace's scope covers the topic — including under another name, `qa` for `quality`, `infra` for `platform` — the answer is a document there, not a new folder: say so and stop. A workspace is warranted when the area has its own standing content **and** its own owner. **Step 3 — Get the owner.** Exactly one person, full name and e-mail. **Ask if it is not given; never infer it** from git history or from who is talking. One person may own several workspaces. If nobody can be named yet, stop: create the workspace when somebody can. **Step 4 — Create the folder** under `KB/docs/<name>/`, kebab-case, with two files matching the shape in `ownership.md` and the wording of its neighbours: - `README.md` — what the space holds, and what it does not with a pointer to where that lives instead. - `CLAUDE.md` — the owner as default reviewer, scope, the rules a newcomer would get wrong, and where to start. **Step 5 — Add the row to the area map** in `KB/docs/README.md`, in the right table: project workspaces or layer workspaces. **This is the step that gets forgotten, and a workspace missing from the map is invisible.** **Step 6 — Verify and report.** Run both checker scripts from KB, then report the files created, the row added, and the owner. ## Rules | Severity | Rule | | --- | --- | | MUST | Exactly one owner, named with full name and e-mail. Never two, never inferred. | | NEVER | Create the folder without both `README.md` and `CLAUDE.md`. | | MUST | Add the area-map row in the same change as the folder. | | NEVER | Create a `decisions/` folder inside the workspace. Records live in `KB/docs/decisions/` and carry this workspace's name in their `Scope`. | | NEVER | Restate the root `CLAUDE.md` in the workspace file, or put a directory listing there — the `README.md` is the index. | | MUST | Move existing documents into the new workspace in the same change when it is being split out of another, and fix every link that pointed at them. |