Sync And Health

The vault is local markdown. Hivemind Sync is transport plus routing.

That distinction matters. The vault is the brain. Hivemind Sync decides how trusted machines move shared brain files, handoff transfers, and shared env.

For the feature-level version, see Hivemind Sync.

Sync Ownership

Exactly one sync owner should own realtime shared-brain replication:

Owner Use when
External provider Obsidian Sync, iCloud Drive, Dropbox, Git, or user-managed Syncthing already owns the vault.
HivemindOS Syncthing Trusted machines should pair over Tailscale or Link and each keep a local vault copy.
Manual repair One-shot rsync repair over Tailscale SSH is needed.

Do not stack multiple realtime sync systems on the same vault unless the user explicitly designed that setup.

Handoff Transfers

Handoff files and artifacts live under:

.hivemindos-transfers/

This is the vault-backed handoff folder used by hive-transfer. Each transfer has a manifest, payload files, targeting metadata, hashes, and acknowledgement files.

The folder is safe to sync as vault data. It is not safe for secrets.

Vault Doctor

The doctor audits the shared vault:

pnpm vault:doctor

It is read only by default. With --fix, it moves content into canonical homes or archives stale material:

pnpm vault:doctor -- --fix

The doctor checks:

  • duplicate active shared skills by SKILL.md hash
  • sync conflict and backup artifacts
  • retired root folders/files
  • active hive-e2e-* shared skills
  • hidden AEON profile stubs
  • hidden AEON runtime mirror placement
  • legacy Notes/ content
  • legacy root Scheduled/ state

Migration Manifests

Fixes write JSONL manifests under:

Operations/Vault Migrations/<timestamp>-vault-doctor/manifest.jsonl

These manifests are the audit trail. Do not delete them casually.

Secure Backups

Encrypted backup artifacts and public-key reference notes live under:

Operations/Secure

This path replaces the retired Notes/Secure default.

Store encrypted files, public keys, and reference metadata there. Do not store plaintext secrets in the vault.

Shared env has its own page because it is brain-adjacent but not vault content: Shared Env.