Initialize ops repository

00-doctrine/personal-operating-doctrine.md

@@ -0,0 +1,111 @@
+# Personal Operating Doctrine — Operator Edition
+
+*(v1.0)*
+
+## 1. Prime Directive
+
+I do not optimize for convenience. I optimize for **clarity, recoverability, and sovereignty**.
+
+If a system cannot be understood, rebuilt, or revoked, it does not belong.
+
+## 2. The Core
+
+There exists **one core** from which all authority flows:
+
+- `op-core-vm` is the origin of action.
+- It is disposable, but authoritative.
+- Nothing touches critical infrastructure unless it originates here.
+
+The host machine is a **console**, not a source of trust. The phone is a **witness**, not a workstation.
+
+## 3. Identity Law
+
+Identity is finite.
+
+- I operate through **roles**, not personalities.
+- Each role has minimal scope and clear purpose.
+- Devices hold **leases**, never permanent identity.
+
+Anything that cannot be cleanly revoked is a liability.
+
+## 4. Naming Is Reality
+
+If I cannot name it correctly, I do not understand it.
+
+All systems are named by:
+
+```
+<role>-<scope>-<id>
+```
+
+No myth names. No vibes. No ambiguity.
+
+Renaming precedes deletion. Deletion follows clarity.
+
+## 5. Infrastructure Is Cattle
+
+No machine is sacred.
+
+- All nodes are replaceable.
+- Rebuilds are expected.
+- Loss is boring, not catastrophic.
+
+Sentiment is reserved for people and meaning — never machines.
+
+## 6. Separation of Concerns
+
+Meaning and infrastructure do not mix.
+
+- Knowledge, media, philosophy → cold storage.
+- Keys, infra, authority → clean core.
+
+What matters must be portable. What operates must be disposable.
+
+## 7. Backup Doctrine
+
+Backups exist to enable **calm recovery**, not comfort.
+
+- All backups are encrypted **before** leaving the system.
+- Cloud storage is a **vault**, never a brain.
+- No live sync for core systems.
+
+If a backup cannot be lost safely, it is incorrectly scoped.
+
+## 8. The Nuke Test
+
+Any system must pass this test:
+
+> “If this disappears today, can I rebuild without panic?”
+
+If the answer is no: reduce scope, split responsibility, document recovery, or remove it entirely.
+
+## 9. Tool Minimalism
+
+Every tool must earn its place.
+
+- Fewer tools, deeper mastery.
+- No duplicates without reason.
+- No installs without intent.
+
+Bloat is deferred failure.
+
+## 10. Drift Control
+
+Entropy is inevitable. Drift is optional.
+
+I perform regular identity audits, device reviews, naming corrections, and deletion passes.
+
+Maintenance is a form of freedom.
+
+## 11. Authority Boundary
+
+Critical actions happen only from `op-core-vm`, with intent, awareness, and traceability.
+
+No “just this once”. No shortcuts.
+
+## 12. Final Rule
+
+I build systems I am **not afraid to touch**.
+
+If fear appears, I stop — not to hesitate, but to **restore clarity**.
+