Versions, locks and unlocking

Once a job is confirmed, its numbers are a promise to the client, so Flow starts protecting them. This page explains the locks — and the deliberate, audited ways to change things anyway.

🚧 Not written yet

This page is scaffolded — the outline below is what it will cover. Progress is tracked in gearflow#959.

What this page will cover

• The lock tiers in plain language: open → finance-locked (confirmed) → justify-to-edit (on site) → hard-locked (completed)
• What "finance-locked" actually blocks, and why new gear added to a confirmed job comes in at $0
• Unlock sessions: opening one with a written reason, making your changes, then Save & relock or Discard
• Versions: the snapshot taken at every confirmation and unlock, and the diff view that shows what changed between them
• Who can unlock, and what the audit trail records