4a2e39be86
A PO's site was whatever the uploader or email picked, and process-batch
never re-checked it. Every MEGA PO line starts its cost code with the
project code ("C26/09, MC-SEW" is The Hills), which agreed with the filed
site on every live PO whose code is a site in the app.
After OCR, process-batch now reads those codes:
- all lines name the filed site -> confirmed
- all lines name one other site, nothing booked yet -> PO moves there and
waiting deliveries are queued at the new site
- mixed projects, an unknown code, or receipts already booked -> flagged
in raw_ocr_data.site_check, filed site kept
The check is never fatal: if the site list can't be read the PO is still
filed on the uploaded site.
Nellmapius Ext 25's code was corrected from 001 to C26/27 in the data;
the intake runbook is updated to match.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| audits | ||
| handoffs | ||
| n8n | ||
| research | ||
| reviews | ||
| setup | ||
| superpowers | ||
| api-reference.md | ||
| architecture.md | ||
| ask-architecture.md | ||
| clock-daily-exceptions-rollout.md | ||
| cooler-env.template | ||
| data-flows.md | ||
| data-model.md | ||
| map3-notes.md | ||
| minimax-multi-site-audit-prompt.md | ||
| modules.md | ||
| multi-site-assessment.md | ||
| operations.md | ||
| pwa-install-verification.md | ||
| workforce-employers.md | ||