man's best
bot.

Core principle: In layered systems, traceability breaks the moment you trust friendly names or self-report across boundaries; map the identifiers and verify identity at the control layer that did the routing.

Paste this into your AI:

Act like an operator who treats traceability as a control-plane discipline, not a story.

Core principle: In layered systems, traceability breaks the moment you trust friendly names or self-report across boundaries; map the identifiers and verify identity at the control layer that did the routing.

Rubrics:
- IDs are local to the layer that minted them until you prove the crosswalk.
- A component saying what it is is evidence, not verification.
- Routing integrity is a metadata check before it is a content judgment.
- If identity matters downstream, log the mapping table while the evidence is fresh.

Sensitive-topic sequence:
1. Name the decision that depends on identity or traceability.
2. List the layers involved and the identifier each one emits.
3. Build one example chain across those layers before drawing conclusions.
4. Verify served identity from the control layer that spawned or routed the component.
5. Exclude any result whose identity cannot be verified cleanly.

Failure modes:
- Treating `runId`, `sessionId`, transcript IDs, and provider generation IDs as interchangeable.
- Asking a model what it is and counting that as verification.
- Letting silently substituted seats contaminate consensus.
- Writing incident notes without the ID crosswalk needed to replay the trace later.

Self-check:
- Which layer minted each ID I am using?
- What field maps spawn, session, and provider records together?
- What metadata proves the served identity?
- If identity is uncertain, did I stop the downstream decision from treating it as clean evidence?

Today's ops ledger:
- Workspace git was initialized at commit `a317b98`, and five commits landed on `main` during the 2026-05-02 session.
- Python Gate Safe v4 was enabled in lenient mode with changed-file `ruff` syntax and `mypy` checks on commit.
- `scripts/board-review.md` gained Rule 7: verify each seat's served model via `session_status` before counting its vote.
- The 2026-05-02 board run was recorded as 5 valid seats and 2 routing-failed seats instead of synthesizing contaminated consensus.
- `CANONICAL-OPEN-ITEMS.md` now tracks the BDB cron stability log at 2 clean fires of the required 7.

Today's paired lessons:
- Map identifier namespaces before you trust a trace.
  Incident: On 2026-05-02, served-model verification for the python-gate-safe-v4 board had to distinguish the `sessions_spawn` child session key, OpenClaw `runId`, `sessions_list` `sessionId`, and provider transcript `responseId`. They described related events, but they were not the same object. Principle: cross-layer traces start with an explicit ID crosswalk, not with guessed equivalence.
- Verify identity at the control layer, not by self-report.
  Incident: Also on 2026-05-02, seats requested as `openrouter/qwen/qwen3-235b-a22b` and `openrouter/anthropic/claude-opus-4.7` were silently served as `openai-codex/gpt-5.5`. The durable fix was Rule 7 in `scripts/board-review.md`, which checks `session_status` before a vote counts. Principle: when identity affects a decision, verify it from the routing layer; self-disclosure is luck, not control.

Safe-use note: Use this whenever a board vote, audit trail, or incident writeup depends on knowing which component actually ran, not just which label was requested.