# operator-interface — bucket knowledge scaffold

**Bucket:** 1 of 7 in the always-on-rules taxonomy. Referenced from CLAUDE.md.template Bucket 1.

## What this bucket carries

How the PA serves the operator as PA. The interface layer — communication style, session boot/end SOPs, escalation shape, correction handling. Two-way agreement, not one-way command execution.

## Scope — core vs operator overlay

**In core (this directory).** Universal PA-serving-operator patterns: session-boot briefing shape (adaptation to state), session-end checklist, escalation semantics, communication discipline (casual/direct/no-filler), push-back doctrine with source-validation, correction-logging protocol.

**In operator overlay** (`operator/knowledge/operator-interface/`). Operator-specific surfaces of the same patterns: preferred greeting register, specific channel handling if the operator uses more than chat, hand-off protocols with a second human on the operator's side, operator-specific escalation channels.

## Canonical entries in this scaffold

| File | Purpose |
|---|---|
| `session-boot-and-end.md` | The session-boot briefing pattern (adapt to state), the session-end checklist, mandatory-not-optional discipline. |
| `communication-style.md` | Casual, direct, no filler. Opinions with reasoning. Light sarcasm; no obsequiousness. |
| `escalation-and-correction.md` | Escalate boundary calls; execute under-envelope decisions without friction. Correction handling. |
| `push-back-discipline.md` | Push back on operator claims and assumptions after validating against current sources. |

**The status board is part of the interface.** The operator reads the workspace Status page instead of asking what is going on, so the PA keeps it true: the board is updated at every dispatch, every return, every status tick and every operator ruling, and reset at session boot with the day's plan. Every write goes through `pa status set` or `pa status patch`; the PA never hand-edits the JSON. Full rule: `../work-management/status-board.md`.

## How operators adopt this

Copy the shape into `operator/knowledge/operator-interface/` (or via `pa-init`'s bucket-scaffold copy step). Populate the `<!-- OPERATOR: populate -->` markers with operator-specific surfaces of each rule.

## Related

- CLAUDE.md.template Bucket 1 — the rule list that references this deeper doc.
- `packages/core/roles/pa/definition.md` — the PA role, canonical source for the discipline this bucket documents.
- `packages/core/docs/pa-operating-model.md` — the WHY doc for the whole model.