---
name: operator-table
description: "Complete operator table — all 10 operators, what they measure, output coordinates, plain read address, and source researchers"
metadata: 
  node_type: memory
  type: project
  originSessionId: f5945f14-247b-4322-875b-74fa52e72aff
---

## Operator table (2026-05-28)

Full pipeline: field item → logos_operator.py (8 operators) → conflict_operator.py → plain_read

| Operator | Measures | Output coordinates | Plain read addresses | Source |
|---|---|---|---|---|
| act_type | Speech act type | assertive / directive / commissive / expressive / declaration | What is this trying to do? | Austin, Searle |
| cooperative | Maxim compliance | honored / violated(which) / suspended | Is this being straight? | Grice |
| transmission | How it travels | broadcast / leak / rumor / direct / archive | How did this reach us and why? | — |
| resonance | Emotional field | harmony / friction / illusion | Does this feel like it sounds? | Machin |
| authority | Authority structure | institutional / tribal / occult / peer | Who is speaking and from what standing? | — |
| utility | What it's for | narrative / currency / positioning / maintenance | What is this actually doing for the sender? | — |
| social_field | Social space | grid + group + quadrant | What social environment shaped this? | Douglas |
| structural | Social layer | self → dyad → small group → institution → global | Where in social structure? | Dunbar |
| conflict | Conflict conditions | schema / behavior / terrain / window / escalation | What conditions present, where do they point? | Granovetter, Glasl, Durkheim, Bandura |
| plain_read | All coordinates → language | one calibrated sentence | What is happening here, toward restoration? | — |

## Notes

- Operators 1–8 run inside `logos_operator.py` (one chain, domain-agnostic)
- `conflict_operator.py` runs separately after logos_operator.py completes — reads `inference["logos"]`, writes `inference["conflict"]`
- `plain_read` (formerly `logos_narrative.py` → rename pending to `logos_plain_read.py`) reads conflict coordinates before writing — output calibrated to terrain; `window=open` inferences need more careful framing than `window=closed`
- Governing principle: **describe the vector not the wound** — surface what points toward restoration, not the damage inventory

## Wikiversity use

Wikiversity content is human-written only (agentic content banned). The operator table serves as the scaffold for writing plain-language explanations of what each operator does and why. `wholesystemsmodel.org/index.html` stays JSON-LD/agentic (indexing layer), Wikiversity is the human-authored educational layer.

**Why:** Human-written content has higher E-E-A-T value per SEO research; Wikiversity platform requires it; operators need plain-language explanations for practitioners who won't read code.

**How to apply:** When writing Wikiversity content, use this table as the structure. Each operator = one section. Include the "plain read addresses" column as the organizing question for each section — practitioners understand questions better than coordinates.