114 lines
2.3 KiB
Markdown
114 lines
2.3 KiB
Markdown
# The Operator Charter (One Page)
|
|
|
|
*(v1.0)*
|
|
|
|
## I. 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.
|
|
|
|
## II. The Core
|
|
|
|
There is **one core of authority**.
|
|
|
|
- `op-core-vm` is the origin of action.
|
|
- It is disposable, but authoritative.
|
|
- No critical action occurs outside it.
|
|
|
|
The host is a console. The phone is a witness.
|
|
|
|
## III. Identity Law
|
|
|
|
Identity is finite.
|
|
|
|
- Roles over personalities.
|
|
- Least privilege, always.
|
|
- Devices receive leases, never permanence.
|
|
|
|
Anything that cannot be revoked cleanly is a liability.
|
|
|
|
## IV. Naming Is Reality
|
|
|
|
If it cannot be named correctly, it is not understood.
|
|
|
|
Format:
|
|
|
|
```
|
|
<role>-<scope>-<id>
|
|
```
|
|
|
|
No myth names. No ambiguity. Renaming precedes deletion.
|
|
|
|
## V. Infrastructure Doctrine
|
|
|
|
Infrastructure is **cattle, not pets**.
|
|
|
|
- Nodes are replaceable.
|
|
- Loss is expected.
|
|
- Rebuilds are boring.
|
|
|
|
Sentiment is reserved for people, not machines.
|
|
|
|
## VI. Separation of Meaning
|
|
|
|
Meaning and infrastructure never mix.
|
|
|
|
- Knowledge, media, philosophy → cold storage.
|
|
- Keys, infra, authority → clean core.
|
|
|
|
What matters must be portable. What operates must be disposable.
|
|
|
|
## VII. Backup Rule
|
|
|
|
Backups exist for **calm recovery**, not comfort.
|
|
|
|
- Encrypt before upload.
|
|
- Cloud storage is a vault, never a brain.
|
|
- No live sync for the core.
|
|
|
|
If losing a backup causes panic, it is wrongly scoped.
|
|
|
|
## VIII. The Nuke Test
|
|
|
|
Every system must answer:
|
|
|
|
> “If this disappears today, can I rebuild without panic?”
|
|
|
|
If not: reduce scope, split responsibility, document recovery, or remove it.
|
|
|
|
## IX. Tool Discipline
|
|
|
|
Every tool must earn its place.
|
|
|
|
- Fewer tools, deeper mastery.
|
|
- No duplicates without reason.
|
|
- No installs without intent.
|
|
|
|
Bloat is deferred failure.
|
|
|
|
## X. Drift Control
|
|
|
|
Entropy is natural. Drift is optional.
|
|
|
|
Regularly: audit identities, review devices, correct names, delete without regret.
|
|
|
|
Maintenance is freedom.
|
|
|
|
## XI. Authority Boundary
|
|
|
|
Critical actions occur only:
|
|
|
|
- from the core
|
|
- with intent
|
|
- with traceability
|
|
|
|
No shortcuts. No “just this once”.
|
|
|
|
## XII. Final Law
|
|
|
|
I build systems I am **not afraid to touch**.
|
|
|
|
If fear appears, I stop — not to hesitate, but to **restore clarity**.
|
|
|