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>
878 B
Cross-day lesson — Riverline Logistics — Nashville Downtown Build-Out, 2026-05-01
Generated by gpt-oss:120b in 3.5s. Based on 5 events + 2 mid-day checkpoints.
When multiple fills target the same city, the pool’s “turns” metric can mask imminent double‑booking; always cross‑reference each candidate’s current assignment before confirming a new fill. Pre‑load a secondary candidate list from the nearest bonus‑eligible city (e.g., Murfreesboro, TN ≈ 35 mi) for every role that has already been placed twice in Nashville. If a worker appears in the “cites” count for a role more than once, automatically switch that fill to the Murfreesboro list to preserve the local $4/hr bonus and avoid conflicts. Finally, log each assignment’s turn number and gap count in a shared spreadsheet so the next shift can spot repeat usage at a glance.