Shared-team projection

Named ownership required

A shared vault can be projected to a server that feeds other tools. The projection does not transfer decision authority.

Role model

• Gold writer: the single owner authorized by the initiative's accepted Score.
• Silver proposer: may create isolated proposals or evidence under a separately approved path.
• Reader: may read the projected files without write permission.
• Recovery owner: owns backup and conflict resolution.

Do not promote a reader or agent to writer because the files are locally writable. Read back shared-vault entitlement and remote identity without secrets, and make the conflict strategy an explicit approved decision.

Safe sequence

1. Back up the authoritative source.
2. Read remote/local inventories after approved interactive authentication.
3. Confirm one Sync method per device and the exact local filesystem allowlist.
4. Stop for exact approval before setup, mode, scope, device, or continuous-process changes.
5. Run a canary and verify it from a second device by exact content and SHA-256.
6. Check conflicts, deletions, and unexpected files.
7. Enable only the approved reader/Silver-writer permissions and supervision.

Authority boundary

Obsidian Sync and Headless are transports or projections. They are not Agent HQ, an accepted Score, or trusted-wiki Gold. Exact accepted proposal hashes remain authoritative when the initiative requires them. Never copy a live writable SQLite database between devices.

Source: Headless Sync, retrieved 2026-08-29 EDT.