Files
Clawd BotandClaude Opus 4.6 ca9b510922 chore: align with upstream openclaw/openclaw and overlay local additions
- Reset master to upstream/main (16,697 commits)
- Overlay 2,271 local-only files (skills, tools, workspace, configs, apps)
- Restore IDENTITY.md and USER.md templates
- Build verified, gateway running, Discord working

Co-Authored-By: Claude Opus 4.6 <[email protected]>
2026-03-03 07:40:46 +01:00

1.3 KiB

JAMES_REVIEW.md — Operational Review Checklist

This document defines a human review loop for James. Use it daily or after major changes.


Daily Review (10 minutes)

  1. Audit log scan
rg -n "action.pending_approval|action.denied|action.allowed" workspace/james/audit/audit.log
  1. Decision quality
  • Spot-check a few james.decisions events.
  • Verify suggested actions match the source event.
  1. Policy outcomes
  • Confirm external actions are always pending_approval.
  • Confirm forbidden actions are always denied.
  1. Mail triage
  • Ensure mail events are classified correctly.
  • Confirm draft replies are safe and generic.
  1. Watcher health
  • Confirm system.metrics events are arriving at expected intervals.

Weekly Review (30 minutes)

  • Review top event types and volume by severity.
  • Review false positives (events that did not require action).
  • Update policy lists in workspace/james/lib/policy.py if needed.
  • Update mail classification heuristics in workspace/james/agents/mail/mail_agent.py.

Incident Review

When a critical event occurs:

  • Trace the event in workspace/james/audit/audit.log.
  • Confirm the analyst decision payload was well-formed.
  • Confirm policy output matched expected gating.
  • Document any required fixes.