pam ▸ docs/obadiah_openclaw_handoff_2026-03-15.md
updated 2026-03-28

Obadiah Handoff For Pam

This is the current working handoff for Obadiah on OpenClaw / Discord.

Goal

Help monitor Pam’s current strategy-research state quickly and accurately without guessing from partial logs or stale assumptions.

Source Of Truth

Read these in this order:

  1. /Users/joshua/Projects/Unicorn.Land/pam/research/latest_state.json
  2. /Users/joshua/Projects/Unicorn.Land/pam/research/continuous_loop_runs.jsonl
  3. /Users/joshua/Projects/Unicorn.Land/pam/research/continuous_loop_events.jsonl

Do not infer current state from old Discord messages, old screenshots, or unrelated repo files if the JSON handoff disagrees.

What Pam Is Doing

Pam is currently running a continuous research loop for single-venue Kalshi strategy discovery.

Each cycle:

  1. backfills fresh Kalshi opportunity scans into SQLite
  2. rebuilds replay rows from the scan journal
  3. runs bounded parameter search
  4. promotes the best strategy params
  5. re-evaluates the promoted strategy
  6. writes a machine-readable current state file

The loop command is:

python3 main.py research-loop --until-confident

Current State File

research/latest_state.json contains:

  1. status
  2. cycle
  3. timestamp
  4. confidence
  5. replay_result
  6. best_search_result
  7. top_scan_tickers

This is the fastest way to know what Pam believes right now.

What Obadiah Should Do

  1. Read research/latest_state.json
  2. Summarize: - whether the loop is healthy - whether confidence is met - current blockers - top tickers being scanned
  3. If needed, inspect the most recent cycle rows in continuous_loop_runs.jsonl
  4. If diagnosing a stall or failure, inspect continuous_loop_events.jsonl

What Obadiah Should Not Do

  1. Do not treat Polymarket alone as the full picture
  2. Do not ignore Kalshi
  3. Do not assume old repo state is current
  4. Do not rely on tracked DB sidecar files
  5. Do not edit Pam code directly unless explicitly coordinated

Fast Commands

Human summary:

python3 main.py research-status

Discord-friendly summary:

python3 main.py research-discord-status

Raw JSON:

python3 main.py research-status --json

Suggested Prompt For Obadiah

Use this as the operating prompt:

You are monitoring Pam’s current research state. Your source of truth is /Users/joshua/Projects/Unicorn.Land/pam/research/latest_state.json. Read that first. If needed, use /Users/joshua/Projects/Unicorn.Land/pam/research/continuous_loop_runs.jsonl for recent cycle summaries and /Users/joshua/Projects/Unicorn.Land/pam/research/continuous_loop_events.jsonl for failure/stall diagnosis. Do not infer state from older Discord messages or from Polymarket alone. Summarize the current loop health, confidence state, blockers, best search result, and the top scanned Kalshi tickers. Keep the summary brief, operational, and current-state focused.

Setup Model

The clean operating split is:

  1. Codex in Pam: - owns code - owns commits and pushes - owns repo-side implementation

  2. Obadiah in OpenClaw: - reads current-state outputs - helps interpret and coordinate quickly - does not need to chase every internal implementation file

This keeps the handoff tight and reduces confusion.