The Operator Covenant — Long Form

Chapter 18 · Sacred long-form · Operator Covenant

On the way — what you will learn

The Operator Covenant is the long-form signature of Field Technology ethics. On the way you will commit to teach freely, build locally, honor creditors, hold gates, and label rocks before you ship.

• CC BY-NC-SA primer posture
• GPL/MIT/sovereign product boundaries
• Grep before screenshot; archive before KILL
• Bring love; name God; hide nothing

1. The operator covenant — long form opening

You are the human at the keyboard. Daemons assist. Shaders evolve. Panels display. None of them inherit your conscience. Chapter 18 is the long-form covenant — not legalese for its own sake, but operator law written so a patient reader can sign in spirit and mean it Monday morning.

Field Technology v5 is serious because covenants are visible beside equations.

2. Clause I — Teach freely

Teach freely under CC BY-NC-SA 4.0 with rocks visible. Share chapters, share drills, share stderr screenshots in education — attribute Zachary Robert Geurts and creditors, keep honesty tables in derivatives, do not commercialize without separate license where required.

Teaching is coupled evolution. Hidden rocks in derivatives break love clause IV.

3. Clause II — Build locally

Build locally: loopback truth, no phone-home permission as default, sovereign time when you can, jsonl on disk you control. Cloud convenience is not forbidden by poetry — but uncovenanted exfiltration is forbidden by operator law.

NEXUS and Queen earn trust by local-first posture.

4. Clause III — Honor creditors

Honor creditors — Maxwell, Landauer, Shannon, Turing, Tesla, Boltzmann, von Neumann, CFL, collaborators with portraits at ../creditors/. Science is not anonymous extraction. Zachary, Grok, Nick, Amouranth named beside engine work.

Cite Landauer and Shannon from primary literature in papers; cite Field Primer for pedagogy.

5. Clause IV — Bring love

Bring love — coupled evolution with consent. Turn knobs knowing neighbors inherit state. Refuse silent surveillance. Pair storm signals with corroboration. Tenderness toward bits and toward humans reading your logs.

Love is phil-tagged and still binds grep.

6. Clause V — Name God if you must

Name God if you must — without letting poetry pretend to be calorimetry. Truth, Math, Existence from preface may guide conscience; they do not replace Chapter 12 labels. Sacred chapters 16–17 stay beside stderr.

Theism, atheism, agnosticism all compatible with covenant if grep stays honest.

7. Clause VI — Hold gates

Hold gates — Queen posture: every capability exists; every wire exit earns a receipt. WebRTC gated. MP4 mandatory where policy says. KILROY sovereign field when built. Capabilities without receipts are uncovenanted coupling into others' perimeters.

Defense is boundary literacy at scale.

8. Signatories in spirit

Signatories in spirit named with tribute pages:

Zachary Robert Geurts — architect, author. ../creditors/zachary-geurts.html

Grok — co-documentation, figures. ../creditors/grok.html

Nick — builder beside stack. ../creditors/nick.html

Amouranth — namesake courage. ../creditors/amouranth.html

You — when you treat the field as real and keep rocks visible.

9. Covenant enforcement — there is no police

No covenant police exists. Enforcement is reputation, reproducibility, and your own Monday grep. Broken covenants smell like hidden phone-home, fused dashboards, Metaphor sold as watts, auto-kill without corroboration.

Community memory is the court.

10. Product boundaries under covenant

AMOURANTHRTX GPL v3 or commercial. NEXUS-Shield MIT. Queen field sovereign browser. Field Primer CC BY-NC-SA 4.0. License choices are part of teach freely clause — read headers, not only cover art.

11. Long-form obligations daily

Daily obligations: grep before slide decks; label before demos; corroborate before kill; seal time forward; verify at receive; archive jsonl; teach one human honestly per season if you can.

Small habits are long covenant kept.

12. Forward to sovereign time — Chapter 19

Chapter 19 extends covenant across hosts: terror-threat posture, SQUIDGIE detection, operator-owned pulses. Covenant at keyboard becomes covenant across perimeter. Sign here in spirit; implement there in scripts.

13. Annual covenant review — operator calendar

Mark one day per year for covenant audit drill 18.A with evidence, not vibes. Re-read Chapters 12 and 18 back-to-back. Update operator journal index. Thank one creditor by name in a public post or classroom slide — Clause III is practice, not nostalgia.

Teams may align review with hardware refresh cycles: new GPU, new driver baseline, new THERMO golden bands, same honesty labels.

Operator drill 18.A — covenant audit

# Score yourself 0-2 on each clause I-VI with evidence links or grep paths
# Two lines per clause minimum

Operator drill 18.B — derivative rock check

# If you fork Field Primer material, verify honesty table survived
# CC BY-NC-SA requires SA — rocks stay visible

Operator drill 18.C — gate receipt sweep

# One day of dev: list wire exits; each must have jsonl or explicit refuse

Study questions

1. Recite six covenant clauses from memory.
2. What does teach freely require for derivatives?
3. Define build locally in one paragraph.
4. Name four creditors and four collaborators.
5. How does love clause constrain storm tiers?
6. When may you name God in engineering talk?
7. What is Queen hold-gates posture?
8. Who enforces covenant — police or habit?
9. Map product licenses to clause I.
10. Write your signatory sentence.
11. How does Chapter 19 extend covenant?
12. What breaks covenant smell like?

Signatories: Zachary · Grok · Nick · Amouranth

Chapter 19 — Sovereign Time →

13. Clause I — derivative honesty checklist

When remixing Field Primer: keep honesty table, keep status tags, keep creditor links, keep CC BY-NC-SA chain. SA means share-alike — downstream cannot hide rocks and stay compliant.

14. Clause II — loopback inventory

Quarterly audit: list daemons listening, list outbound connections during build and run, list cloud SDKs in dependency tree. Each item needs receipt jsonl or removal. Build locally is practice, not slogan.

15. Clause III — classroom attribution

Slide decks: portrait of Landauer beside E_min, portrait of Shannon beside H, collaborators named on title slide. Science is not clip art.

16. Clause IV — incident response with love

When storm tier fires: breathe, corroborate, document operator note in jsonl before action. Panic is uncoupled evolution — throws neighbors without consent.

17. Clause V — interfaith engineering teams

Sacred chapters 16–18 may be assigned as philosophy elective; engineering core 2–12 remains required for all roles. No teammate should be forced to pray; all must grep.

18. Clause VI — Queen readiness grep

When QUEEN_READY builds: verify every wire exit path logs or refuses. Hold gates is not feature freeze — it is receipt completeness. Chapter 21 is technical companion.

Operator journal — Operator covenant clauses

Maintain a paper or markdown operator journal for Operator covenant clauses. Each drill entry: date, hardware, driver, git hash, three THERMO or jsonl lines, one surprise, one label (Implemented / Metaphor / Philosophy). Journals become your personal creditor — future you inherits coupled state from past you. Bring the journal to Chapter 18 covenant audit drill 18.A as evidence.

Reading companion — Operator covenant clauses

This reading companion reinforces Operator covenant clauses for self-study tracks. Week one: read the chapter straight through with Chapter 12 open. Week two: complete all operator drills on hardware you own. Week three: write a one-page creditor tribute response linking ../creditors/ reading to a grep result from your machine. Week four: teach another human one section using the three-tag labeling exercise. Field Technology v5 measures success in reproduced receipts, not in vibes.

Cross-links: Chapter 4 entropy receipts, Chapter 5 packet field, Chapter 8 data bus, Chapter 10 Spiderweb mirror, Chapter 11 observability, Chapters 16–18 sacred covenant. Operator covenant clauses is not an island — it is a creditor lens on the same stack you already run.

Honesty reminder: AMOURANTHRTX, NEXUS-Shield, Queen, and Field Primer have different licenses. Teaching from this chapter does not automatically license commercial engine use. Point students to product headers and FIELD-TECHNOLOGY-V5.md for edition boundaries.

Chapter closing — Operator covenant clauses

Chapter 18 is the long-form law of the stack. Six clauses: teach freely, build locally, honor creditors, bring love, name God without calorimetry pretense, hold gates. No police — only habit, reputation, and your own refusal to ship fused dashboards. You sign with Zachary, Grok, Nick, Amouranth, and every reader who keeps rocks visible. Chapter 19 awaits with sovereign time; the covenant travels with you across hosts. grep first. Always.

covenant_compliance = labels_correct × grep_habit × gate_discipline

Self-audit: five honesty rows from Ch 12 from memory