g-skl-pcac-sync

When to Use

@g-pcac-sync command. When a shared contract with a sibling needs updating, or when responding to a SYNC item in INBOX.md.

Key Principle

Peer syncs are advisory. Neither sibling has authority over the other. Work in this project proceeds regardless. The sync surfaces as an advisory in @g-status until resolved.

Steps

Initiating a Sync (I changed a contract)

1. Read .galdr/linking/link_topology.md — get siblings list
2. Select target sibling and contract
3. Update local peer copy at .galdr/linking/peers/{sibling_name}.md:
   • Bump version number
   • Update content (the spec that changed)
   • Update last_synced date
   • Set sync_status: current on your copy
4. Include capabilities snapshot — also copy this project's capabilities.md to sibling's .galdr/linking/peers/{this_project_slug}_capabilities.md:
   • Read .galdr/linking/capabilities.md
   • Write a copy to sibling/.galdr/linking/peers/{this_slug}_capabilities.md
   • If sibling path not accessible: note in the INBOX notification that capabilities are attached
5. Write to sibling/.galdr/linking/INBOX.md (if path accessible):

   markdown
   1## [OPEN] SYNC-XXX — from: [this project] — YYYY-MM-DD
   2**Type:** peer_sync
   3**Contract:** [contract_name]
   4**Version:** [old] → [new]
   5**Change:** [brief description of what changed and why]
   6**Capabilities snapshot:** .galdr/linking/peers/[this_slug]_capabilities.md (written)
   7**Your action:** Update your copy at `.galdr/linking/peers/[name].md`
   8**Canonical spec path:** [this project]/.galdr/linking/peers/[name].md
   9**Status:** action_needed

6. Create task in sibling's .galdr/ (if path accessible):

   yaml
   1title: '[Peer Sync] Update [contract_name] from [this project] — v[new]'
   2delegation_type: peer_sync
   3peer_sync_partner: [this project_id]
   4peer_sync_status: action_needed

7. Create local task tracking that sync was initiated:

   yaml
   1title: '[Peer Sync] Notified [sibling] of [contract_name] change — awaiting ack'
   2delegation_type: peer_sync
   3peer_sync_partner: [sibling_id]
   4peer_sync_status: pending_partner

8. If sibling path not accessible: stage the notification at .galdr/linking/pending_requests/sync_[sibling].md

Responding to a Sync (Sibling notified me)

1. Read INBOX item (SYNC-XXX in INBOX.md) or check the created task
2. Read their updated contract (if path accessible) at sibling/.galdr/linking/peers/{name}.md
3. Check for capabilities snapshot — if sibling/.galdr/linking/peers/{this_slug}_capabilities.md was written (or attached in INBOX), read it and confirm our local peer snapshot is current
4. Update local peer copy at .galdr/linking/peers/{sibling_name}.md:
   • Match their version number
   • Update content to match canonical
   • Set sync_status: current
5. Close the local peer_sync task: status → completed
6. Mark INBOX item [DONE]
7. If sibling path accessible: update their INBOX entry to note your sync is complete

Report (both directions)

Peer sync complete:
- Contract: [name] — v[new]
- Local peer copy updated: .galdr/linking/peers/[sibling_name].md ✅
- Sibling notified/confirmed: [sibling_id] ✅
- Tasks created/closed ✅