doocus improvemnts

doocus/README.md

@@ -40,7 +40,34 @@ docs-output/
 
 Node **modes**: `extracted` (docx/pdf/pptx/xlsx → text sidecar) · `meeting`
 (mp4/mkv/... → belongs to meetus, not a doc) · `link` (everything else → original
-is the artifact, nothing duplicated).
+is the artifact, nothing duplicated). Every node also carries `created` (birth
+time, falling back to mtime) so docs and meetings sort by creation date coherently.
+
+## Meetings
+
+Videos are `meeting` nodes — doocus does **not** transcribe them; meetus does. To
+keep everything in one coherent, searchable tree, run meetus over **only** the
+meetings doocus found and write each into a `<file>.meetus/` sidecar right next to
+its `<file>.doocus/`-style neighbours:
+
+```bash
+# 1. index the drive → docs-output/{index.json, meetings.txt}
+uv run make docs IN="/mnt/drive"
+
+# 2. meetus over ONLY the listed meetings, re-rooted at the mount, into
+#    <file>.meetus/ sidecars (matches the pointer doocus already wrote):
+make batch IN="/mnt/drive" OUT=docs-output \
+     LIST=docs-output/meetings.txt \
+     OUT_FORMAT="{name}.meetus"
+```
+
+- `meetings.txt` holds **relative** paths only — mount the drive anywhere and the
+  `-l/--list` re-roots them under `-i`, so this machine reads only the meetings.
+- `OUT_FORMAT="{name}.meetus"` is meetus's new `--out-format` (tokens `{date}
+  {run} {stem} {name}`; default keeps `YYYYMMDD-NNN-<stem>`). Omitting `{run}`
+  makes the folder deterministic, so it matches the `out`/`transcript` pointer the
+  indexer set on each `meeting` node — no relink step.
+- Frames land in `<file>.meetus/frames/` for now (unchanged).
 
 ## Supported types