# Active Chats Inventory

Source of truth for which Claude.ai chats are alive, what each is for, and what state each is in. Lives in substrate so the inventory itself survives chat retirement.

**Naming convention:** `<kind>:<id> — <focus>` where `<kind>` is one of `equipment | customer | property | personal | meta` (per SESSION-PRELUDE.md) and `<id>` is the entity slug. Trailing focus disambiguates same-entity sessions.

**Lifecycle model:** ephemeral. Chats are session instances opened against substrate, not persistent domain experts. Retired when handoff is committed and no pending question requires that chat's context.

**Last updated:** 2026-04-28

---

## Active

| Chat name (new convention)                                  | Kind      | ID                       | Status                          | Blocked on / next trigger                              | Last touched |
|-------------------------------------------------------------|-----------|--------------------------|---------------------------------|--------------------------------------------------------|--------------|
| `equipment:fourwinns-h190 — battery diagnosis`              | equipment | fourwinns-h190           | active, v0.1 shipped            | parasitic-draw test results from Sam                   | 2026-04-28   |
| `equipment:seadoo-gtx-di-2001 — winterization + supercharger` | equipment | seadoo-gtx-di-2001     | active, behind on substrate     | substrate refresh send (METHODOLOGY v1.2 + SYS-DESIGN v1.3) tonight | 2026-04-28 |
| TBD — see "Pending kind/name resolution" below              | TBD       | llc-startup or manage-*  | active, ambiguous scope         | Sam confirms which thread is live (LLC formation vs Quick-Add modal vs both) | unknown |

## Retiring

| Chat name (current in claude.ai)                            | Kind      | ID                       | Pending wrap-up                                        | Target retire date |
|-------------------------------------------------------------|-----------|--------------------------|--------------------------------------------------------|--------------------|
| `Project handoff with logo fix priority`                    | (cross-domain, predates substrate) | — | none — close-and-delete; `conversation_search` is recovery backstop | 2026-04-28 (tonight) |
| `John Deere LT180 PTO and tires diagnostic + service guide` | equipment + meta | lt180 + substrate-stand-up | (1) `handoff-blocks/lt180-2026-04-28.md` (equipment); (2) `handoff-blocks/meta-substrate-stand-up-2026-04-28.md`; (3) WORKFLOW.md draft | 2026-04-29 |
| `Aceves home peak staining job`                             | customer  | aceves-home-stain-2026-04 | (1) `customer-jobs/aceves-home-stain-2026-04/closeout.md` (ad-hoc, template TBD); (2) `handoff-blocks/aceves-home-stain-2026-04-2026-04-28.md` | 2026-04-29 |

## Retired

_None yet. Add row here when retirement completes; include retired-date and pointer to substrate output that captured the chat's value._

| Chat name | Kind | ID | Retired date | Substrate output |
|-----------|------|----|--------------|------------------|

## Planned (chat does not exist yet)

| Chat name (new convention)              | Kind     | ID         | Trigger to open                                    |
|-----------------------------------------|----------|------------|----------------------------------------------------|
| `personal:brand-logo — v2 round-cap review` | personal | brand-logo | Sam routes the v2 SVG + recovery context to Downloads |
| `equipment:lt180 — brake job`           | equipment| lt180      | AM131445 brake kit + inner tubes arrive            |

---

## Pending kind/name resolution

- **`Starting a consulting and contracting LLC`** — current name describes a business phase, not a session. Live thread inside is Quick-Add modal architecture (per Sam's chat-strategy notes). Action: Sam identifies what's actually being shipped from this chat and renames per convention. Candidates: `meta:manage-quick-add — modal architecture`, or `personal:llc-formation — <focus>`, or split into two and retire the cross-cutting parent. Resolution gates the row's move from "Pending" to "Active."

---

## How to use this file

- **Routing a new question:** scan Active table for the matching `<kind>:<id>`. If no match, that's a signal to open a new chat with a fresh opener — not to dump the question into the nearest live chat.
- **Opening a chat:** add a row to Active with the convention-compliant name, kind, ID, and trigger. Chat name in claude.ai sidebar should match exactly.
- **Closing a chat:** verify the retirement test (handoff committed + no pending dependency), move the row from Active → Retiring with the pending wrap-up listed. When wrap-up artifacts land, move row Retiring → Retired with substrate-output pointer, then delete the chat in claude.ai.
- **This file is not load-bearing for session bootstrap** — sessions don't fetch it during their bootstrap sequence. It's a Sam-side routing aid. If it goes stale, sessions still work; routing just gets harder.