Skip to main content

Operator Console

This page is the fast human entry into the current Office/Ops system.

Re-enter quickly​

  1. Open the latest valid Office generation, current published view, or explicit governed source relevant to the work.
  2. Read the smallest current surface: needs_you, ready pulls, exceptions, typed work, or another bounded view.
  3. Pick one concrete move.
  4. State expected evidence and a stop rule.
  5. Execute.
  6. Leave a next pointer if unfinished and return evidence for reentry.

Do not start by reconstructing the whole project universe.

If the input is raw​

Use capture/preparation motifs before forcing structure:

  • CaptureIntake
  • SessionCondense
  • NextPointerFromCapture

These are motifs, not required runtime states.

If the work is unclear​

Use VACChain and Endpoint reasoning:

  • What value are we trying to produce?
  • Which Endpoint should change?
  • What evidence would make that change credible?
  • Is the current move actually on that path?

If the work is ready​

Use the execution packet or current human pull.

A bounded move needs:

  • objective;
  • allowed powers;
  • first action;
  • evidence expected;
  • stop rule;
  • next pointer if incomplete.

See Execution Model.

If the work is blocked​

Prefer a bounded diagnostic or unlock move.

Typical motifs:

  • MinimalReproExtraction
  • RunSmoke
  • ContentValidationGate
  • ADRLite
  • EvidenceManifestWrite

See Motif Registries.

If you need timing​

Detailed timing, cadence, horizon, Mon/Wed/Fri carry touches, 14-day frames, dayparts, and weekly attention counts now live in Weekly Ops Governance, not in this execution doctrine.

This manual only requires bounded work and clear reentry.

If you are lost​

Use this spine:

  1. Start Here
  2. One Pager Spec
  3. Authority, State & Projection Model
  4. Office Compile
  5. Execution Model
  6. Checks and Runbooks

The current architecture is intentionally smaller than older Ops versions.