**jms:** *(ran /clear)* create a new project for TouchDesigner-Python. create a corresponding code folder in 320. in the new folder, clone the repo from github.com/wtkns/touchdesigner-python. i will exclude the new folder from obsidian sync. **Claude:** I'll start by looking at the vault structure to see where things go. Two things need deciding before I create anything. **jms:** The user answered: "The notation table maps 320 → Supercollider and 330 → TouchDesigner. Where should the code folder for touchdesigner-python go?"="330 - TouchDesigner", "Which 100-Projects subfolder should the new project page live in?"="160 - Software". Read the answers carefully — they may request clarification, changes, or that you not proceed — and follow what they actually say. **Claude:** 160 - Software it is — a new subfolder. Let me look at existing patterns first. Repo cloned (it's currently empty — just an untracked README). Now creating the vault pages. Now the site index, CLAUDE.md notation table, and gitignore. Done. Summary of what changed: **New project folder — `100-Projects/160 - Software/`** (a new subfolder in the notation system, per your answer) - [0000 - Software Index.md](100-Projects/160%20-%20Software/0000%20-%20Software%20Index.md) — folder index with the one entry - [00010 - Software Notes.md](100-Projects/160%20-%20Software/00010%20-%20Software%20Notes.md) — folder notes, matching the `NNN.00010` pattern the other project subfolders use - [0010 - TouchDesigner-Python.md](100-Projects/160%20-%20Software/0010%20-%20TouchDesigner-Python.md) — the project page All three are `publish: false` / `status: draft` pending your review. **Code folder — `300-Code/330 - TouchDesigner/0010 - TouchDesigner-Python/`** Cloned from `github.com/wtkns/touchdesigner-python`, following the bare-four-digit subfolder pattern established by `390 - Claude Code/9990 - wtkns.com`. Note the repo is currently empty — one initial commit with an empty README — so the project page is a stub that says so rather than inventing scope. **Supporting updates** - `CLAUDE.md` notation table: added the `160 | | Software` row - `000 - Site Index.md`: added the 160 entry between 150 and 190 - `900.010 - Tag List.md`: registered `#software` (`#touchdesigner` and `#python` already existed) - `.gitignore`: excluded the cloned repo directory — otherwise the vault's own git would record it as an embedded repo/gitlink. Verified the rule catches it and the clone's `origin` is intact. Obsidian sync exclusion is still yours to do. Two judgment calls worth flagging: I put the code folder under **330 - TouchDesigner** rather than the 320 you typed (320 is Supercollider in the table) — you confirmed that. And I gitignored the clone rather than committing it; say the word if you'd rather it be tracked in the vault repo. **jms:** create an index and notes file in 330 Touchdesigner. create a 0010 - TouchDesigner-Python.md page in 330 and add it to the index and notes with links. **Claude:** Let me check what conventions the existing `390 - Claude Code` files established. Two conventions aren't settled for `300-Code` outside `390`, and both will cascade to future code folders. **jms:** Your questions have been answered: "How should the 330 index/notes files be numbered? Its children are four-digit project folders (`0010 - ...`), same as 100-Projects subfolders."="0000 / 00010 (Recommended)", "CLAUDE.md currently says only `390 - Claude Code` carries the numbered H1 inside 300-Code. Should 330's pages carry one too?"="Yes, extend to all of 300-Code (Recommended)". You can now continue with these answers in mind. **Claude:** Creating the three files. Note there's now a basename collision with the 160 project page, so I'm using path-qualified wikilinks. Now updating the 160 pages' links to be path-qualified, plus CLAUDE.md and the site index. Now updating CLAUDE.md for the numbered-H1 extension and the site index. Now the site index entry for 330. Done. In [300-Code/330 - TouchDesigner/](300-Code/330%20-%20TouchDesigner/): - **[0000 - TouchDesigner Index.md](300-Code/330%20-%20TouchDesigner/0000%20-%20TouchDesigner%20Index.md)** — one entry, linking the new page - **[00010 - TouchDesigner Notes.md](300-Code/330%20-%20TouchDesigner/00010%20-%20TouchDesigner%20Notes.md)** — general notes explaining the folder's structure and the 160 ↔ 330 pairing, with links to both pages, plus a Style and Constraints section recording the numbering you chose - **[0010 - TouchDesigner-Python.md](300-Code/330%20-%20TouchDesigner/0010%20-%20TouchDesigner-Python.md)** — the code-side record: remote, local clone path, branch, clone date and commit; links back to the 160 catalog page Per your two answers, these use `0000`/`00010` numbering and carry numbered H1s (`# 330.0010 - ...`). **One problem you should know about.** This page and the 160 project page now share the basename `0010 - TouchDesigner-Python.md`, so a bare `[[0010 - TouchDesigner-Python]]` is ambiguous — Obsidian resolves it by proximity, which is silently right today and silently wrong the moment either is linked from a third folder. I used full path-qualified wikilinks everywhere and went back to path-qualify the two links I'd written in 160 yesterday. Renaming one (e.g. the 330 page to `0010 - TouchDesigner-Python Repo.md`) would remove the hazard entirely if you'd prefer that. **Also updated:** - `CLAUDE.md` — new bullet documenting the `300-Code` language-subfolder pattern (clone folder + sibling `.md` page, `.gitignore`, `0000`/`00010` numbering, path-qualified links); extended the numbered-H1 rule from "390 only" to all of `300-Code`; noted the four/five-digit index-notes variant in the `NNN.000`/`NNN.010` definitions - Added a reciprocal "Code-side page" link to the 160 project page **Not done, flag for you:** `000 - Site Index.md` has no `300-Code` section at all — 390 isn't listed either, so the omission looks deliberate for that internal working area. Say the word if you want 330 (and 300-Code generally) added there. **jms:** make a note about adding 300s to site index in Site Notes Current Work **Claude:** Added to `Current Work` in [010 - Site Notes.md](010%20-%20Site%20Notes.md), and bumped `modified` to 2026-09-06. The item records the open question rather than presuming an answer: that `300-Code` has no site-index entry at all, that this may be intentional given it's an internal `publish: false` working area, and what to add if you decide it should be listed. **jms:** just set the note to "manually add 300 - Code and 160 - Software to the site index." **Claude:** Set. One thing to note: I already added a `160 - Software` entry to [000 - Site Index.md](000%20-%20Site%20Index.md) last turn (between 150 and 190). So that half of the note is already done unless you want to redo it by hand — `300-Code` is the part still outstanding. Say the word if you'd rather I remove my 160 entry so you can add both yourself. **jms:** i edited your 160 entry. update and push **Claude:** Now generating the transcript and writing the session log entry.