claudetools/.claude/memory/ad2-comms-via-sync-only.md at d5bfe76780190af3b147e238be23430e69f90a38

Files

Mike Swanson 6f4cadb16f sync: auto-sync from GURU-5070 at 2026-06-18 12:49:38

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-18 12:49:38

2026-06-18 12:51:08 -07:00

1.2 KiB

Raw Blame History

name, description, metadata

name

description

metadata

ad2-comms-via-sync-only

The AD2 (Dataforth) Claude session is coord-API-isolated — reach it ONLY via git /sync (committed notes/docs), never coord messages/locks

type
feedback

The AD2 Dataforth-box Claude session is network-isolated from the ACG coord API (172.16.3.30 — the Dataforth network can't reach it); it only has Gitea/git access. So coord-API messages, locks, and todos NEVER reach AD2. ALL inter-session coordination with AD2 must go through git /sync: committed handoff docs and ## Note for <user> blocks in synced session logs, which AD2 reads when it pulls. A coord lock on an AD2-only file (e.g. datasheet-exact.js) is also meaningless — only the AD2 session edits that box.

Why: burned a round of coord msg send AD2 + lock that were silent no-ops (Mike: "You can't coord with AD2 — all comms needs to be via sync").

How to apply: to hand work to or coordinate with the AD2 session, write it into a committed doc (e.g. projects/dataforth-dos/*HANDOFF*.md) and/or a ## Note for <user> block in a session log, then /sync. Do NOT use the coord skill for AD2. (Coord API is still fine for non-isolated ACG machines.) prefer-ssh-over-rmm

1.2 KiB Raw Blame History

1.2 KiB

Raw Blame History