# Lesson — 2026-09-19: Local vs Gitea vs Obsidian

**One line:** Do not triple-mirror the company. One truth (Gitea), many thin views.

## What we decided today
1. **Gitea `veripath`** is the master for OS paper, SOPs, decisions. **Gitea `veripath-operations`** is the master for the Issues queue.
2. **Local git clones** are working copies for the agent — pull from Gitea; never rewrite docs on disk as a "mirror OS."
3. **hermes workspace** holds only live job packs + STATUS.md (transient).
4. **Obsidian** is a THIN human map: primitives, the two laws, packet checklist, truth table, and lessons — each note links to the Gitea source instead of copying it.

## The trap
Copying SOP text into Obsidian (and a local mirror) creates three drifting copies. The fix is pointers: Obsidian notes say "see `docs/…` in Gitea," and the local clone stays a `git pull` away from truth.

## Rule of thumb
If a local/Obsidian file would be *the* statement of policy, it belongs in Gitea. Local files are views, caches, or links.

## Related
- [[04_projects/veripath/00 - OS Map|OS Map]]
- [[04_projects/veripath/02 - Where Truth Lives|Where Truth Lives]]