Module config 

Sync + storage configuration.

Config is the runtime struct the sync manager reads. coven persists the sync-relevant fields to config.yaml in the store directory (Config::save_to_config_yaml) and reads them back (Config::load_from_config_yaml). The store directory is part of the owner graph, not configuration, so callers supply it to those operations.

Structs

CloudHomeConfig

The cloud home: which provider backs sync and its per-provider settings. One cohesive unit — connecting picks a provider and fills its fields; disconnecting resets the whole thing to default.

Config

Sync + storage configuration for one store.

Enums

CloudProvider

Cloud home provider selection.

ConfigError

Configuration errors.

ExactUploadVerification

How an exact cloud write proves that the stored bytes match their declared object reference. This is local host policy and is never accepted from an invitation or another device.

HomeStorage

How a cloud home stores its objects: opaque (encrypted, unreadable to anyone who can read the bucket) or browsable (stored in the clear at readable paths). This is not about who can reach the bucket — the storage provider’s own access control applies either way; it is about whether what they store is legible. The host picks it once, when it creates the home; it cannot change later (it determines how every object is written). One choice drives two mechanisms together: