WebDAV path: /AI/ on host webdav.critchley.biz. There is a local davfs2 mount at /z/AI/ — do NOT write through it. The reason (previously recorded only as "flaky"): davfs2 caches writes locally and uploads them asynchronously, so a write can report success, and read back correctly through the same mount from cache, while nothing has reached the server. Data lands on flush/unmount, not on close. This applies to all of /z, not just /AI/ — see memory/john for the general rule.Existing files: envoy-phase-design.html, envoy-phase-design-v2.html, envoy-phase-owns-model.html, envoy-issues-2026-02-28.html, notes-map.svg, notes-graph.htmlStyle: Georgia serif, max-width 860–900px, h2 with left border. See any existing file for full CSS.
Always write to /z/AI/ via the webdav4 Python module, not direct file I/O:Credentials come from ~/.netrc — same as the notes system and webdav_deliver.py.Fallback: cadaver (CLI WebDAV client) also works reliably.
Envoy uses webdav_deliver.py to deliver emails to a WebDAV maildir (bypassing SMTP for certain recipients).Envoy has NO schema action for writing arbitrary HTML/files to WebDAV — models that claim to have done this are hallucinating.