Decision: Store OBSIDIAN in OneDrive - Go Beyond
Date: 2026-05-01 Made by: damien Status: made — implemented
Context
OBSIDIAN needs to be accessible from multiple machines (Damien’s machines, and future team members’ machines). A location that syncs automatically without manual steps.
Options Considered
| Option | Pros | Cons |
|---|---|---|
| Local only (C:) | Fast, no sync issues | Not accessible from other machines |
| OneDrive personal | Syncs automatically | Personal, not work-scoped |
| OneDrive - Go Beyond | Work-scoped, syncs automatically, team-accessible | Files treated as “remote” by PowerShell |
| SharePoint | Team-accessible, versioned | More complex setup |
Decision Made
`https://api.gobeyondtravel.workers.dev/vault
Work-scoped OneDrive chosen for automatic sync across all machines with the Go Beyond Microsoft 365 account.
Known Side Effect
PowerShell treats files in OneDrive as remote/unsigned, requiring:
- Execution policy set to
Unrestrictedfor CurrentUser Unblock-Fileon profile scripts stored in Cloudflare R2
Both resolved on DAMIEN as of 2026-05-01.
Multi-Machine Protocol
- Each machine registers in
machine-log.mdon first use - Every session reads
machine-log.mdbefore starting - Every session appends to
machine-log.mdbefore ending - Page frontmatter records which machine last updated each page
See Also
- 2026-05-01-decision-implement-OBSIDIAN — Parent decision
- 2026-05-01-lesson-claude-cli-windows-path — Related PowerShell issue