canvas-sync

# Canvas Sync ## When to Use - Starting a new session (pull latest canvas) - Ending a session (commit canvas changes) - After team discussion that changes product direction - When canvas conflicts arise from parallel work ## Workflow ### Pull Latest ``` git pull origin main ``` Then run `/mycelium:diamond-assess` to see what changed. ### Commit Changes ``` git add .claude/canvas/ .claude/harness/decision-log.md .claude/memory/ git commit -m "canvas: [brief description of what changed and why]" ``` ### Conflict Resolution - Different canvas files: auto-merges (no conflict) - Same file, different sections: usually auto-merges - Same field conflicting: the person with more evidence wins — a *manual* resolution heuristic for the team, not an automated merge. No tooling evaluates evidence weight; `Gated by:` a `/canvas-merge` procedure (read both versions, compare provenance depth on overlapping entries, recommend) — not yet built. - When uncertain: discuss as team, log decision ### GitOps Principle The canvas system IS GitOps for product knowledge — git is the single source of truth, changes are declarative (YAML), and updates flow through version control with review. For infrastructure GitOps (ArgoCD, Flux), see JiT tooling detection for Kubernetes/infrastructure-as-code projects.