TODO: Move cross-cutting conventions from pal-e-docs to pal-e-agency

todo-move-conventions-to-agency Todo

todo done

Project

Problem

Several conventions are filed under the pal-e-docs project but are actually cross-cutting agency concerns — they define how agents and humans work across the entire platform, not specific to the pal-e-docs codebase.

Candidates for Move

Slug	Current Project	Why it's agency
<code>note-conventions</code>	pal-e-docs	Defines note_type, status, decomposition rules used by all projects
<code>mermaid-authoring</code>	pal-e-docs	Borderline — content format but followed by all agents
<code>html-style-guide</code>	pal-e-docs	Borderline — content format but followed by all agents

tagging-conventions is deprecated — leave in place.

Project Responsibility Model

pal-e-agency — SOPs, conventions, agent definitions, workflow docs (how we work)
pal-e-config — hooks, agent spawn configs, enforcement (making SOPs executable)
pal-e-docs — the app itself (API, DB, frontend, MCP tools)
pal-e-platform — infrastructure (k3s, Terraform, Helm)

Fix

Update project field on each convention note from pal-e-docs to pal-e-agency. No content changes needed.