Projects Sync — Shared Tool

# Projects Sync — Shared Tool

> **Purpose:** Keeps the `projects/` portfolio layer in sync with the engine (`agents/`, `shared/planner/`). Runs automatically at the end of every session where artifacts were created or modified.
>
> **Who runs this:** Any agent at session end, or the session-end protocol in `copilot-instructions.md`. This is a shared tool, not an agent — no cadence, no Clerk tracking.

---

## When to Run

| Trigger | Action |
|---------|--------|
| **New project created** (new thesis in `theses.json`, new plan in Planner, new idea promoted from backlog) | Create project folder + README using the template below |
| **Artifact produced** (Writer outputs a draft, Builder completes assets, Scout delivers signals) | Copy to the correct project's `build/`, `references/`, or `media/` folder |
| **State change** (project moves stages, gets published, gets killed) | Update project README metadata + master `projects/README.md` |
| **Session end** (any session where state changed) | Run the full sync checklist below |

---

## Project Folder Creation Protocol

When a new project is identified, create the folder immediately:

### Step 1: Assign Type + ID

| Type | Prefix | When to use |
|------|--------|-------------|
| Thesis | `THS` | Research → write → publish → distribute |
| Event | `EVT` | Sessions, talks, demos |
| Program | `PRG` | Multi-session programs |
| Strategy | `STR` | Career/brand strategic initiatives |
| System | `SYS` | Agent Prime internal improvements |
| Toolkit | `TLK` | Reusable methodologies |
| Exploration | `EXP` | Undefined — could become any type |
| Build | `BLD` | Product/code builds |

**Next available IDs:** Check `projects/README.md` for the latest numbers per type.

### Step 2: Create Folder Structure