azcomputerguru/claudetools
1
0
Fork 0
Code Issues 73 Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-06-18 12:49:38

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-18 12:49:38
This commit is contained in:
Mike Swanson
2026-06-18 12:49:57 -07:00
parent 0745f5d09b
commit 27170e1a5c
4 changed files with 143 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
.claude/memory/ad2-comms-via-sync-only.md Normal file
View File

@@ -0,0 +1,21 @@
---
name: ad2-comms-via-sync-only
description: The AD2 (Dataforth) Claude session is coord-API-isolated — reach it ONLY via git /sync (committed notes/docs), never coord messages/locks
metadata:
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]]