Skip to content

Sync & Versioning

An artifact you deploy today can drift from its source tomorrow — someone edits the upstream repo, someone edits the deployed copy, or both. SkillMeat keeps every artifact's collection copy, upstream source, and deployed instances comparable, versioned, and reversible.

Who it's for: anyone maintaining artifacts over time, and team leads who need proof that a "golden path" hasn't silently drifted across the projects it was deployed into.

The web app and CLI read and write through the same source of truth: your filesystem collection, mirrored into a local database cache for fast querying. Writes go to the filesystem first, then fan out to the cache — so what you see in the web app always reflects what's actually on disk.

How to read the tags

Local — shipped in the local edition, no flag needed. Enterprise — shipped in enterprise, no launch-blocking gate. Gated — shipped, but behind a feature flag, auth wall, or readiness gate (see the caveat in each row). Future — roadmap only; not available today.

What you can do today

Capability Availability Learn more
Three-scope diff comparison — source vs. collection, collection vs. project, source vs. project Local Syncing Changes, Sync System Quick Reference
Upstream tracking with a configurable pin policy (snapshot-on-change, track-latest-release, track-tags, or manual pin) and webhook-driven refresh Local Pin Policy Reference, Webhook Subscriptions
Collection snapshots, refresh, and rollback Local Managing Collections
Full version history with restore to any prior version Local Version History & Restore
Update artifacts safely with a review-before-apply flow Local Updating Safely, Sync Version Rollback
DAG branching and merge-back for parallel artifact edits Local DAG Branching & Merge-Back
Scheduled artifact reconciliation — periodic drift detection that proposes changes for you to accept or reject; it never writes on its own Gated — behind reconciliation_enabled, default OFF Scheduled Artifact Reconciliation

Go deeper