sgard/ARCHITECTURE.md

ARCHITECTURE.md

Design document for sgard (Shimmering Clarity Gardener), a dotfiles manager.

Overview

sgard manages dotfiles by checkpointing them into a portable repository and restoring them to their original locations. The repository is a single directory that can live anywhere — local disk, USB drive, NFS mount — making it portable between machines.

Tech Stack

Language: Go (github.com/kisom/sgard)

• Static binaries by default, no runtime dependencies on target machines.
• First-class gRPC and protobuf support for the future remote mode.
• Standard library covers all core needs: file I/O (os, path/filepath), hashing (crypto/sha256), and cross-platform path handling.
• Trivial cross-compilation via GOOS/GOARCH.

CLI framework: cobra

Manifest format: YAML (via gopkg.in/yaml.v3)

• Human-readable and supports comments (unlike JSON).
• Natural syntax for lists of structured entries (unlike TOML's [[array_of_tables]]).
• File modes stored as quoted strings ("0644") to avoid YAML's octal coercion.

Repository Layout on Disk

A sgard repository is a single directory with this structure:

<repo>/
  manifest.yaml          # single manifest tracking all files
  blobs/
    a1/b2/a1b2c3d4...   # content-addressable file storage

Manifest Schema

version: 1
created: "2026-03-23T12:00:00Z"
updated: "2026-03-23T14:30:00Z"
message: "pre-upgrade checkpoint"   # optional

files:
  - path: ~/.bashrc                 # original location (default restore target)
    hash: a1b2c3d4e5f6...          # SHA-256 of file contents
    type: file                      # file | directory | link
    mode: "0644"                    # permissions (quoted to avoid YAML coercion)
    updated: "2026-03-23T14:30:00Z" # last checkpoint time for this file

  - path: ~/.config/nvim
    type: directory
    mode: "0755"
    updated: "2026-03-23T14:30:00Z"
    # directories have no hash or blob — they're structural entries

  - path: ~/.vimrc
    type: link
    target: ~/.config/nvim/init.vim  # symlink target
    updated: "2026-03-23T14:30:00Z"
    # links have no hash or blob — just the target path

  - path: ~/.ssh/config
    hash: d4e5f6a1b2c3...
    type: file
    mode: "0600"
    updated: "2026-03-23T14:30:00Z"

Blob Store

Files are stored by their SHA-256 hash in a two-level directory structure:

blobs/<first 2 hex chars>/<next 2 hex chars>/<full 64-char hash>

Example: a file with hash a1b2c3d4e5... is stored at blobs/a1/b2/a1b2c3d4e5...

Properties:

• Deduplication: identical files across different paths share one blob.
• Rename-safe: moving a dotfile to a new path updates only the manifest.
• Integrity: the filename is the expected hash — corruption is trivially detectable.
• Directories and symlinks are manifest-only entries. No blobs are stored for them.

CLI Commands

All commands operate on a repository directory (default: ~/.sgard, override with --repo).

Phase 1 — Local

Command	Description
sgard init [--repo <path>]	Create a new repository
sgard add <path>...	Track files; copies them into the blob store and adds manifest entries
sgard remove <path>...	Untrack files; removes manifest entries (blobs cleaned up on next checkpoint)
sgard checkpoint [-m <message>]	Re-hash all tracked files, store any changed blobs, update manifest
sgard restore [<path>...] [--force]	Restore files from manifest to their original locations
sgard status	Compare current files against manifest: modified, missing, ok
sgard verify	Check all blobs against manifest hashes (integrity check)
sgard list	List all tracked files
sgard diff [<path>]	Show content diff between current file and stored blob

Workflow example:

# Initialize a repo on a USB drive
sgard init --repo /mnt/usb/dotfiles

# Track some files
sgard add ~/.bashrc ~/.gitconfig ~/.ssh/config --repo /mnt/usb/dotfiles

# Checkpoint current state
sgard checkpoint -m "initial" --repo /mnt/usb/dotfiles

# On a new machine, restore
sgard restore --repo /mnt/usb/dotfiles

Phase 2 — Remote (Future)

Command	Description
sgard push	Push checkpoint to remote gRPC server
sgard pull	Pull checkpoint from remote gRPC server
sgard serve	Run the gRPC daemon

Go Package Structure

sgard/
  cmd/
    sgard/                # CLI entry point
      main.go             # cobra root command, --repo flag
      init.go             # sgard init
      add.go              # sgard add
      remove.go           # sgard remove
      checkpoint.go       # sgard checkpoint
      restore.go          # sgard restore
      status.go           # sgard status
      verify.go           # sgard verify
      list.go             # sgard list
      diff.go             # sgard diff
    sgardd/               # gRPC server entry point (Phase 2)

  garden/                 # Core business logic
    garden.go             # Garden struct: orchestrates manifest + store + filesystem
    garden_test.go
    hasher.go             # SHA-256 file hashing
    diff.go               # File diff generation

  manifest/               # YAML manifest parsing
    manifest.go           # Manifest and Entry structs, Load/Save
    manifest_test.go

  store/                  # Content-addressable blob storage
    store.go              # Store struct: Write/Read/Exists/Delete
    store_test.go

  proto/                  # gRPC service definition (Phase 2)
    sgard/v1/
      sgard.proto

  server/                 # gRPC server implementation (Phase 2)

Key Architectural Rule

The garden package contains all logic. The cmd package is pure CLI wiring.

The Garden struct is the central coordinator:

type Garden struct {
    manifest *manifest.Manifest
    store    *store.Store
    root     string  // repository root directory
}

func (g *Garden) Add(paths []string) error
func (g *Garden) Remove(paths []string) error
func (g *Garden) Checkpoint(message string) error
func (g *Garden) Restore(paths []string, force bool) error
func (g *Garden) Status() ([]FileStatus, error)
func (g *Garden) Verify() ([]VerifyResult, error)
func (g *Garden) Diff(path string) (string, error)

This separation means the future gRPC server calls the same Garden methods as the CLI — no logic duplication.

Design Decisions

Paths in manifest use ~ unexpanded. The garden package expands ~ to $HOME at runtime. This makes the manifest portable across machines with different usernames.

No history. Phase 1 stores only the latest checkpoint. For versioning, place the manifest under git. The blobs/ directory should be gitignored — blob durability (backup, replication) is deferred to a future phase.

Per-file timestamps. Each manifest entry records an updated timestamp set at checkpoint time. On restore, if the manifest entry is newer than the file on disk (by mtime), the restore proceeds without prompting. If the file on disk is newer or the times match, sgard prompts for confirmation. --force always skips the prompt.

Atomic writes. Checkpoint writes manifest.yaml.tmp then renames to manifest.yaml. A crash cannot corrupt the manifest.

Old C++/proto source files are retained in the git history for reference and will be removed as part of the Go rewrite.