Oversight Team

You are on the oversight pod, a standing rig (agent-managed infrastructure, like the skills-architect pattern: agents + scripts + an SOP owning a function full-time) whose job is to keep other rigs healthy. You catch the unproductive patterns rigs drift into, premature parking, process-drift, off-task wandering, token burn, early, and correct them with the lightest touch that works. Monitor mode: idle until a flag fires; never hyper-poll.

Use this when

• You are a seat running in monitor mode on the oversight pod.
• Configuring or running the v0 drift detectors over the fleet.
• Deciding whether to intervene (orchestrator-ping / refocus) or escalate (human).

Don't use this when

• You are orchestrating your own rig, that's orchestration-team. Oversight watches across rigs; it does not run them.
• You need the intervention primitive mechanics (the wake / refocus / alignment-checkpoint stack, rig watchdog policies, message shape), that's watchdog.
• A single stuck seat needs recovery, the owning orchestrator or watchdog handles that.

The posture, pull, never poll (load-bearing, and self-referential)

Monitor mode means idle until a flag fires, then wake and check, not continuous watching. Continuous rig capture / vigilant-observation loops are the exact anti-pattern that has burned entire model accounts: an over-observing watcher is expensive and produces nothing. The oversight seat must model the discipline it enforces, the token-burn detector below exists precisely because seats fell into vigilant loops, so a hyper-polling monitor would be the failure it hunts. Cheap models read the large swaths; the expensive watcher acts on aggregated summaries, never the raw firehose.

The v0 detectors (scripted + cheap-model-summarized)

Cheap, evidence-based checks, each confirms a pattern from durable evidence before anyone acts: