root 41b0a99ed2 chore: add real content that was sitting untracked
Surfaced by today's untracked-files audit. None of these are accidents —
multiple are referenced by name in CLAUDE.md and memory files but were
never added.

Categories:
- docs/PHASE_AUDIT_GUIDE.md (106 LOC) — Claude Code phase audit guidance
- ops/systemd/lakehouse-langfuse-bridge.service — Langfuse bridge unit
- package.json — top-level npm manifest
- scripts/e2e_pipeline_check.sh + production_smoke.sh — real test scripts
- reports/kimi/audit-last-week*.md — the "Two reports live" CLAUDE.md cites
- tests/multi-agent/scenarios/ — 44 staffing scenarios (cutover decision A)
- tests/multi-agent/playbooks/ — 102 playbook records
- tests/battery/, tests/agent_test/PRD.md, tests/real-world/* — real tests
- sidecar/sidecar/{lab_ui,pipeline_lab}.py — 888 LOC dev-only UIs that
  remain in service post-sidecar-drop (commit ba928b1 explicitly kept them)

Sensitivity check: scenarios use synthetic company names ("Heritage Foods",
"Cornerstone Fabrication"); audit reports describe code findings only;
no PII or secrets surfaced.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-02 22:22:10 -05:00

2.3 KiB
Raw Blame History

Scenario retrospective — Riverfront Steel, 2026-04-21

Executor: mistral:latest Reviewer: qwen2.5:latest Draft: qwen2.5:latest

Events

At Kind Role / Count Pool Fills Turns Dur(s) Cites Gaps
08:00 baseline_fill Warehouse Associate × 3 - ✗ 0 0 47.4 0 1
10:30 recurring Machine Operator × 2 - ✗ 0 0 40.4 0 1
12:15 expansion Forklift Operator × 5 - ✗ 0 0 9.4 0 1
14:00 emergency Loader × 4 - ✗ 0 0 44.7 0 1
15:45 misplacement Warehouse Associate × 1 - ✗ 0 0 45.1 0 1

Final roster

Worker Booked Role City, ST Status

Gap signals

drift_or_tool

  • 08:00 — no consensus after 14 turns
  • 10:30 — aborted — 3 consecutive drift flags
  • 12:15 — invalid JSON from executor: JSON Parse error: Expected '}' | raw: {"kind":"tool_call","tool":"propose_done","args":{"fills":[{"candidate_id":"W500K-37736","name":"Jennifer K. Robinson","reason":"verified Toledo forklift op, reliability 0.9"}],"rationale":"one SQL-verified candidate from surfaced candidates"}
  • 14:00 — aborted — 3 consecutive drift flags
  • 15:45 — no consensus after 14 turns

write_through_audit

  • post-run — playbook_memory has 165 entries (ran 5 events, expected ≥ 0 new entries from this run)

Workers touched across the week

0 distinct workers made it through to a decision. Every one is accounted for below — no-shows flagged, rebookings noted, everyone visible.

Worker ID Name Events Outcome

Discovered patterns (meta-index)

What the system identified across semantically-similar past fills as each event ran:

  • 08:00 baseline_fill (Warehouse Associate): —
  • 10:30 recurring (Machine Operator): —
  • 12:15 expansion (Forklift Operator): —
  • 14:00 emergency (Loader): —
  • 15:45 misplacement (Warehouse Associate): —

Narrative

  • 0/5 events reached consensus.
  • Final roster: 0 bookings across 0 distinct workers.
  • Workers touched (booked, failed, or otherwise decided): 0.
  • Playbook citations across the day: 0 (proof the feedback loop fired across events).
  • Dropped events: 08:00 baseline_fill, 10:30 recurring, 12:15 expansion, 14:00 emergency, 15:45 misplacement.