operators/

The registry of who operates this brain. Every skill and doc that needs to know "who is running this session" resolves it from here, never from a guess.

Schema

One file per operator, named after their slug (e.g. operators/jane-doe.md). Frontmatter:

---
slug: <slug, a-z0-9- only>
git_names:
  - <exact `git config user.name` value>
github: <github-username>
role: <free text>
sensitive_owner: false
---

• slug: [a-z0-9-] only (no capitals), unique across the registry, immutable once created. Other systems key off it: memory/* frontmatter owner: fields and daily-log/YYYY-MM-DD-<slug>.md filenames. Renaming a slug breaks every file that references it, so don't.
• git_names: every exact git config user.name value that maps to this operator, across every machine they use. A list, not a single string: someone with a typo'd identity on one machine adds the typo here rather than fixing history.
• github: their GitHub username, for collaborator management, CODEOWNERS, and the CI tripwire of docs/GOVERNANCE.md step 3, which recognises a push by this value.
• role: free text. What they do, in their own words or yours.
• sensitive_owner: optional, true or false (absent means false). true marks an operator who may push the paths listed in .github/sensitive-paths.txt straight to main and who reviews the proposal pull requests everyone else opens for them. Meaningless until docs/GOVERNANCE.md step 3 is adopted. More than one operator can carry it.

Only the registry files directly in operators/ count. A file moved under operators/archive/ keeps its slug reserved without claiming an identity: that is where the offboarding checklist in docs/GOVERNANCE.md sends departed operators.

Resolution rule

Quote this identically everywhere it is referenced (docs, skills, scripts):

Resolve the active operator by matching git config user.name against every registry file's git_names. Exactly one match: proceed. Zero or multiple matches: stop and tell the user how to fix their identity or the registry. Never guess, never derive a slug from the name itself.

The rule exists because a slug is not a transformation of a name (no jane-doe from git config user.name reading "Jane"). It is a value one of the registry files explicitly claims. If nothing claims it, or more than one file does, stop and say so rather than guessing.

Uniqueness constraints

• Two operator files must never share a slug.
• Two operator files must never share a git_names entry. If they do, the resolution rule's "exactly one match" guarantee breaks for that identity, and every skill that resolves the operator becomes ambiguous, which is a data problem to fix, not something to paper over.

Adding an operator

1. Copy operators/operator_template.md to operators/<slug>.md and fill it in.
2. Commit and push the new file: it has to be on main before they clone, or their own registry file won't be there.
3. Add them as a GitHub collaborator on the company repo.
4. Point them at operators/ONBOARDING.md.

Removing an operator

Do not just delete their file. Follow the offboarding checklist in docs/GOVERNANCE.md (access revocation, CODEOWNERS cleanup, memory owner: reassignment, and what stays archived versus reserved).