Configuration
Organisation supersede policy
What each of the three values gains you, and what it gives up.
org.supersede_policy chooses how an organisation wants a future supersede condition
presented. The engine validates and retains the choice now, before merge enforcement is
introduced; in this release it does not change merge behaviour.
| Value | What you gain | What you give up |
|---|---|---|
flag | Work can continue while the supersede condition is made visible for follow-up. | The merge is not stopped, so the organisation accepts that flagged work may land before anyone resolves the condition. |
refuse-merge | The strongest automatic protection: a merge cannot proceed while the condition remains. | Availability and throughput are traded for safety; even an understood or harmless condition blocks until it is resolved under the future enforcement step. |
owner-decides | No irreversible action is taken automatically; the owner makes the case-specific call. This is the explicit default when the key is absent. | Progress waits for a human decision, so unattended flows can pause instead of flagging or refusing automatically. |
Any other value—including ignore—is refused while the file loads as
config-unknown-supersede-policy, and the refusal names all three reachable choices.