A change waits for the people who have to see it first.
An approval flow drawn on a canvas — who approves, how many of them, in what order, under what conditions — and enforced where it counts: a submitted change is held from the team until it is approved, and the item is frozen for everyone, the author included. Locks for the hours someone needs a component to themselves. A merge that only argues about the fields both sides touched.
The nodes
Submitted, frozen, approved, merged. Nothing slips past.
A flow sits on a project, a folder or a request, and the nearest one wins. A change under it goes up as a submission — the exact proposed content and the revision it is based on — and the item is frozen for everyone until the flow has spoken, the originator too. The backend refuses a save, a publish or a conflict resolution on it, whoever asks.
Approved, it is merged against its base field by field and publishes through the approval path alone. If the store moved on and the merge is not clean, it goes back as stale. Below it, an edit lock: one member's edits only, for the hours the work needs.
Signed and sealed in the team storeScoped, frozen, enforced.
A flow on a project, a folder or a request; the nearest one wins.
The submission carries the change and what it was based on.
The exact proposed content and the revision it is based on. The approver sees a field-level diff. The item is frozen for everyone while it is open — the originator too — and the lock is visible in the tree and the editor.
No way around it.
A manual save, a manual publish and a conflict resolution cannot bypass approval. An approved change publishes through the approval path alone. Resubmission restarts the full review. The originator can withdraw; an administrator can void.
When the store moved on, never half-right.
An approved change is merged against its base. An unclean merge goes back to the originator as stale, never published half-right. A guest division's changes to a shared workspace wait for the home administrators.
The rest of working together without stepping on each other.
Each one signed and sealed like everything else in the store. A merge argues only about the fields both sides touched: everything else settles itself, and a difference in how a file was written is not a difference at all.
Beside it, an approved change meeting a store that moved on. Everything merges but one field — so it goes back to the originator as stale, and nothing is published half-right.