An approved version to compare against
Every governed term has an approved definition in the SynkBase library: the wording, the formula, the owner and the version. Every connected copy is compared with that version.
Detect
A formula edited in one Jira ticket. A threshold updated in one Confluence page. SynkBase notices, and tells the people who depend on it before the next report runs.
In development with design partnersA business definition usually lives in several places at once. "Scrap rate", "active customer" or "net exposure" is written down in a requirements ticket, implemented in a pipeline, explained on a wiki page and reproduced in a dashboard. Each copy is owned by a different team.
When one copy changes, nothing tells the others. The mismatch is usually found weeks later, by someone reconciling two numbers that should agree.
Every governed term has an approved definition in the SynkBase library: the wording, the formula, the owner and the version. Every connected copy is compared with that version.
Connectors read the systems where definitions are written and implemented. When a connected value differs from the approved version, SynkBase records a drift event with both values side by side.
Each drift event shows the approved definition, the changed one and where the change came from. The owner can accept it into a new version, reject it, or escalate it through the approval workflow.
A drift event can be deferred, but only with a reason and an expiry date. When the date passes, it comes back. Nothing is closed by one click and forgotten.
Design partner programme
We are working with a small number of organisations that live with this problem every quarter. Design partners get early access, direct influence on what we build first, and founder-level attention.