three-way-file-duplicity-creates-unacceptable-drift-risk
Maintaining three copies of the same artifact (live runtime + local clone + remote backup) creates the identical drift failure mode as the dual ~/.claude.json divergence pattern documented as CRITICAL. The correct model is exactly two authoritative sources: live runtime (/root/.claude/skills/) for execution + remote GitHub for disaster recovery. A local intermediate clone adds zero unique value and must be removed immediately after its creation purpose (initial push) is served.
Related
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- helix-skill-deployed-vs-backup-path-distinction
- openclaw
- notebooklm
- ephemeral-tmp-pattern-for-zero-drift-github-sync
- docker-build-cache-accumulates-indefinitely-without-cron
three-source-skill-duplicity-creates-drift-risk(archived)three-source-skill-duplicity-creates-unacceptable-drift-risk(archived)- three-source-model-for-skills-creates-drift-risk
- docker-build-cache-accumulates-without-cron-prune
- matej-marjanovic-seo-fork-is-redundant
- helix-skills-live-outside-aj-workspace-git
- helix-backup-vs-live-audit-method
- helix-backup-audit-methodology-via-temp-clone
- helix-backup-audit-byte-level-diff-methodology