Commercial Objectives And Job Closeoff Guardrails
Practical interpretation of commercial purpose, operational residue, and safe stale-job closeoff rules.
ActiveHuman Checked
This page exists to bridge the gap between business purpose and automation rules.
- Monolith should support profitable, well-controlled operational work rather than just preserve every stale record forever.
- Not every Synchroteam job is directly invoice-driving.
- Old jobs should only be auto-closed where the commercial risk is genuinely low.
Current starting interpretation:
- `Office activity` residue should be treated as administrative backlog, not field-work backlog.
- `Installs Surveyor` residue should be split between:
- tanker/vendor placeholders that are often safe to cancel
- survey/commission/service records that should stay review-first
The canonical working note is `docs/commercial_objectives_and_operational_guardrails.md`.