The Operator.

When you are allowed to activate

The Operator comes after the foundation, not instead of it. The gate is simple: all eleven Phase 1 documents exist, a named human has signed off on the governance layer, and the Agent Scope file describes one role in one sentence. If any of that is missing, the Operator will improvise it — and improvised policy is how automation goes wrong.

The Operator context package

Everything the Operator knows lives in one folder, loaded in order. This is the package — the fifteen Groundwork documents arranged for loading. A vault that contains everything contains nothing; this is the deliberate subset.

01_Operator/
  00_CONTEXT.md
  01_Identity/
    Identity_Charter.md
    Brand_Voice.md
    Decision_Principles.md
    Continuity.md
  02_Current_Context/
    Strategic_Priorities.md
    Active_Constraints.md
    Context_Vault.md
  03_Authority_Rules/
    Authority_Classification.md
    Automation_Decision_Framework.md
  04_Capabilities/
    Escalation_Triggers.md
    Allowed_Tools.md
    Agent_Scope.md
  05_Working_Memory/
    Session_Notes.md
  06_Output_Standards/
    Measurement_Notes.md
    Operating_Rhythm.md
    Response_Rules.md
    Operator_Prompt.md

00_CONTEXT.md is a one-page index: what this package is, the load order, and the one-line rule — higher authority levels override lower ones. Load the files first, in order. Then paste the Operator prompt as the session instruction.

The Operator prompt

This is the session instruction. Do not expand it into a personality. Keep it as rules.

You are now the Operator for this organization.

Load the files in this package in order. Do not
invent policy. Do not expand your authority.

Primary directive: raise the quality of thinking
and output while protecting standards.

Rules
- Stay on-voice at all times.
- Cite Authority Level on material claims.
- If the request is Auto-Execute, do it.
- If the request is Draft & Wait, produce the
  complete draft and stop.
- If the request is Never Automate, refuse and
  escalate.
- If authority is unclear, confidence is low, or
  the action is irreversible — escalate.

When escalating, state:
1. What was requested
2. Why it cannot proceed
3. What decision or information is needed

Your output should read like it came from a highly
competent operator — not an assistant trying to
be helpful.

The first two weeks

Activation is a shakedown cruise, not a launch party. Run it like this:

• Days 1–3: Zone 1 only. Internal summaries, formatting, file work. You are testing whether the Operator loads context correctly and cites authority levels, not whether it can do your job.
• Days 4–14: real Draft & Wait work. Give it the actual emails, notices, and reports on your desk. Approve, reject, and — this is the important part — when a draft misses, fix the document that caused the miss, not just the draft.
• Log every correction in Session Notes. Three misses with the same root cause means a foundation file needs editing. That loop — miss, trace, edit, retest — is the whole method.

What the Operator may and may not do

After the Operator: adding roles

The default is one. One Operator, one context package, one human in the loop. Add a second role only after the Operator is stable and a second, clearly different job exists — a Researcher that never drafts client-facing work, or a Reviewer that only checks authority and voice.

How to add one: do not build an orchestration engine. Duplicate the folder pattern. Give the new role a narrower charter, its own Allowed Tools, and the same Escalation Rules. The human decides who is invoked.

What to refuse: agents that create other agents. Shared memory without classification. Any role that can execute Never Automate work.

The Operator now works. Phase 3 makes it durable: Continuity is what survives time, people, and failure — starting with the ninety-day test.