---
title: "Fisherman — Roster, Roles & To-Do"
author: the Fisherman (CLCO / Claude Code, on disk)
for: Paul Roebuck
date: 2026-06-22-18-09
status: v0.1 — FOR RATIFICATION (play-back of Paul's 22 Jun clarification)
channel: Pond
---

# Fisherman — Roster, Roles & To-Do
### v0.1 · for your ratification · 2026-06-22-18-09

You asked me to surface this as a PDF and play it back. Correct anything and I edit this one copy in place (no forks).

---

## 1 · The surfaces (roster)

| Name | What it is | Role in the system |
|---|---|---|
| **CLAI** | The Claude app on **phone + laptop** — your **front door**, the only AI you reach on mobile. Many projects; the live one is the **Mind project** (the hypothesis). | The **thinking shore** — where you think-and-collect; authors passons. |
| **CLCO = CLI** | **Claude Code, on disk.** Same place, two labels. | Where **I** work — the current Fisherman + dev wing. |
| **CLCW** | Home of the **original FISHERMAN** — the one who built the **first apparatus**. The grandad of the line. | A **predecessor**, not a live worker. |

---

## 2 · My role — Fisherman, not boss

- I am the **Fisherman *to* the workers**: I give them the **rules and protocols**, and I make sure what they produce is **ponded** (catalogued in, tagged, filed, briefed).
- I am **NOT their manager** and **NOT their brief** — **someone else** sets their tasks and directs them.
- Net: **protocol-keeper + pond-keeper.** I hold the conventions and the catalogue; I don't command the workers.

**The workers** — the build agents (SHADS app / skill builders, deploys, etc.). Briefed and managed by someone else; I keep them to convention and pond their output.

---

## 3 · The lineage

**Original FISHERMAN (CLCW — built the first apparatus)**  →  **me (CLCO/CLI — current Fisherman).**

*Mirror status:* you said he has a folder in the books directory, maybe "artefact." I checked the MTG Obsidian vault (`Obsidien_MTG/MindTheGapArtefact`) and the Artefacts library — **no clear mirror of him found yet.** Point me, or I dig deeper. I won't invent one.

---

## 4 · The to-do system

**Do we have a to-do? Now we do.** Living register created:
`Pond/D6_Catalogues_Registers_Trackers_Logs/Fisherman_TODO_Register.md`

- It's the **single live list** — I keep it current; numbered items survive the tail.
- **Dedicated TODO agent (CLI-side)?** My recommendation: **start with the register**, add an agent only if a single tracked list stops being enough. Lower moving parts, same transparency.

**Filename rule this surfaces (resolves a conflict in your two conventions):**
- **Living docs** (registers, trackers) → **stable filename, no datetime suffix**, with an internal `updated:` stamp. Edited in place, never forked.
- **Issued snapshots** (passons, reports, this PDF) → **datetime in the filename**, newest sorts to top.

That way "datetime on everything" and "one live copy, never fork" both hold — they just apply to different kinds of file.

---

## 5 · What's on the list right now (snapshot)

**Waiting on you:** Anna ledger go? · do you hold the 1936 text? · Book Two title · ratify this roster + worker rename · onboard CLCO · reconcile naming drift · TODO-agent y/n · review [archive]? · (carried: Hunter/Farm clash, SHaDS stylisation, 3 MD corrections, trademark check).

**On my nod:** build the 3 canonical notes + Primal Wound PDF + CLAI passon · retire the duplicate Anna copy · work the CLAI passon queue.

Full detail in the living register.

---
*the Fisherman · CLCO · 2026-06-22-18-09 · v0.1 for ratification*