41b0a99ed2
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>
912 B
Cross-day lesson — Riverline Logistics — Nashville Downtown Build-Out, 2026-04-22
Generated by gpt-oss:120b in 5.9s. Based on 5 events + 2 mid-day checkpoints.
Before each shift, cross‑check the current roster against the upcoming fill list to catch any worker already scheduled; if a conflict appears, immediately pull a qualified alternate from the local pool (e.g., another Packaging Operator from Nashville) or shift the conflicted worker to a later slot. Keep a standby list of at least two extra candidates per role within the 75‑mi bonus radius (e.g., Murfreesboro for Shipping Clerks) so you can pivot without losing the $4/hr bonus. When an emergency or misplacement request arrives, lock the needed slots first, then verify that no worker appears in two concurrent assignments. Update the roster in real time and confirm each assignment with the system before moving to the next event.