# Worker Contract: 2026-06-25-164017-b2sa

```yaml
worker_contract:
  task_id: "2026-06-25-164017-b2sa"
  origin_thread: "THR-125 - Breaker §2 self-traffic alert: self-authored Notion drops surfaced to Telegram"
  objective: |
    Inspect the Breaker §2 SELF_TRAFFIC CRITICAL burst from 2026-06-25, determine whether it was duplicate healthy self-authored Notion drops or an actual loop/bypass condition, and return a concrete operations recommendation with evidence.
  scope: |
    Read the THR-125 Notion Task Brief and local OpenClaw/router/breaker logs around 2026-06-25 22:45Z through 22:55Z. Group relevant Notion events by event ID, page ID, actor, action, decision, and reason. Determine whether the burst was tied to THR-123/THR-125 Notion page writes, Dorian dispatch/completion entries, or unrelated Notion webhook traffic. Evaluate whether Breaker §2 should distinguish healthy self-authored drops from actual self-authored loop-through. Produce a completion record and, if warranted, a narrowly scoped remediation proposal or patch draft. Do not send user-facing messages. Do not alter production breaker thresholds, suppress alerts, or change external notification routing without a separate explicit approval.
  constraints:
    - Treat this as an operations reliability investigation, not a purchase-sync failure.
    - Use evidence from local logs and Notion thread content; do not infer event identity without log support.
    - Preserve the distinction between healthy protective drops and forwarded/self-reprocessed events.
    - Do not re-process webhook events for worker-authored Notion updates.
    - If logs are missing, partial, rotated, or ambiguous, return a blocked or partial contract with exact missing paths/time ranges.
    - Keep any proposed code/config change reversible and minimally scoped.
  permissions:
    filesystem: write
    network: local
    notion: read-write
    telegram: none
    shell: full
    git: read
  model_recommendation: "openai/gpt-5.4-mini"
  rollback_required: false
  rollback_plan: |
    Investigation-only by default. If a local draft artifact is created, it can be removed. Any production breaker behavior change requires separate approval and is outside this contract.
  output: |
    Return a Worker Completion Contract. Also append a concise progress/completion entry to the THR-125 Notion Dialogue Log using the canonical header format. If an artifact is created, place it under /Users/openclaw/outputs/openclaw/breaker-self-traffic/ and include the path.
  done: |
    Work is complete when the worker has grouped the 22:45Z-22:55Z router/breaker events, identified the likely cause of the 26-drop burst, stated whether any self-authored event was forwarded or user-facing loop behavior occurred, recommended whether §2 severity/dampening should change, logged completion or blockage in the Notion thread, and returned a Completion or Failure Contract to Dorian.
```

## Source Thread

- Notion page: https://app.notion.com/p/Breaker-2-self-traffic-alert-self-authored-Notion-drops-surfaced-to-Telegram-38af8b3ef83d81f49285e19f80067118
- Thread ID: THR-125
- Execution Status at dispatch: Ready to Execute

## Required Notion Dispatch Receipt

After dispatch, Dorian will log the session reference and set the thread status to `In Progress`.