Two different actions that the build currently treats as one.
Status at ebf7cf0: Gap — the Order Cancel action calls the delete endpoint. The backend marks CANCELLED and sets deleted_at together, with no reason and no restore workflow, and nothing blocks it.
These are two separate actions. Ruled 14 September 2026, master § 6c.
Cancel is a status, never a delete.
cancel Job Outcome and a reason for office review.Delete is a separate restricted soft-delete action with its own confirmation and reason.
The August rule said "block"; OE's reply described a person deciding. Both intend that work, payment and posting get checked. The ruling is a system block, with the controlled-correction path for the rare case.
Evidence, 14 September 2026: the build soft-deletes on cancel with no check. On 10 September OE cancelled the wrong order and the developer restored it by hand in the database. The "person decides" reading had already happened once, and the person was the developer with a database console.
Story. As a Technician, I want to record cancel as the visit outcome with a reason, so that office staff can decide the Order action.
Acceptance. The Job Log ends, but the Order remains available for Indoor or OE review.
Story. As Indoor or OE, I want to cancel an eligible Order with a reason, so that cancellation preserves a searchable audit trail.
Acceptance. Direct cancellation is blocked after protected work, completion, payment or accounting posting exists.
Story. As a permitted Manager, I want restricted soft deletion and restoration separate from cancellation, so that cleanup does not erase business history.
Acceptance. Delete requires confirmation and reason; restore returns the same Order Number.
The order Cancel action calls the delete endpoint; the backend marks CANCELLED and sets deleted_at together, without a reason or a restore workflow, and with no protected-state block. This is one of the critical seven.
A delete button for wrongly keyed LG orders was requested. Order numbers are unique and a deleted number can never be reused, so editing is safer than deleting.
Recommendation: no delete — a void or cancelled state keeps the number and the audit trail while removing the order from the working list. Q13.
New to these terms? See the Glossary.