Milestones

On 22 August 2026 GlobSynk adopted a written governance rule covering how existing platform capability may be changed. The short version: capability is preserved by default, and the fact that something looks unused is not a reason to remove it.

It sounds like a small administrative matter. In practice it is the rule that decides whether a platform stays coherent as it grows. Software teams remove things constantly — a field with no obvious caller, a route nobody seems to hit, an older path that a newer one appears to replace. Most of the time that is tidy and correct. Occasionally it removes something a customer, an integration or a future product depended on, and the cost only becomes visible much later, when the reasoning behind the original decision is gone.

The rule requires that a removal be explained before it happens: what the thing does today, what depends on it, what stops working, whether the change can be undone, and what the alternatives to removing it are. If that case cannot be made, the capability stays. Where two instructions conflict and the conflict is unresolved, the default is to preserve and escalate rather than to pick the more convenient reading.

We are recording it publicly because it is a commitment about how we treat things other people may be relying on, and a commitment that is only made internally is easy to quietly drop.