Bidda Obligation Deltas ======================= JS-free text mirror for AI crawlers. Canonical page: https://bidda.com/obligation-deltas Last updated: 2026-08-04 REVIEW CYCLES FILTERED TO WHAT YOU OWN What moved since you last looked. Every review cycle starts with the same question and the same week of work: what actually changed since last time. The obligation change feed answers it in one call, already mapped to the obligations affected and scoped to the area you own. Source changes and withdrawn obligations, filtered by date, pillar, or your own list. START FREE TRIAL → SEE PUBLIC CHANGES → WHY IT MATTERS Most teams find out a rule moved by reading a newsletter, or by not finding out at all. Watching raw sources is worse, because a source diff does not tell you which of your obligations it touches. Mapping the change to the obligation is the part that turns monitoring into work you can actually schedule. How the feed works One call at the start of a cycle, scoped so the answer is short enough to act on. 01 Say when you last reviewed Pass the date of your last review cycle. Everything older than that is filtered out, so you are not reading the same changes twice. 02 Narrow it to what you own Filter to a pillar, or to a specific list of obligations. A team that only owns financial-services obligations does not need to read what moved in food safety. 03 Read the obligations, not the diffs Source changes are already mapped to the obligations they affect, and withdrawn obligations are marked. You get the list of what to re-review, not a pile of raw source diffs to triage. Three ways to narrow it Combine them freely. The point is to get the list down to what your team actually owns. SINCE Since your last review An ISO timestamp. Only changes newer than that point come back, which makes the feed line up with your actual review cycle rather than an arbitrary window. PILLAR Only the domain you own Scope the feed to one of the sovereign pillars, so a team sees movement in its own area and nothing else. NODES Only the obligations on your list Pass a specific set of obligations and get changes for exactly those. This is the one to use when you have a control mapping to keep current. WHAT THE FEED IS NOT The feed reports that a primary source changed or that an obligation was withdrawn, and which obligations are affected. It does not interpret the change, assess what it means for your organisation, or recommend a response. Every obligation stays cited to its primary source so a qualified reviewer can read the change at the source and decide what it requires. Call it from anywhere Available as an MCP tool and a REST endpoint. A free trial counts. MCP TOOL obligation_deltas Call it directly from an agent framework that speaks MCP. REST ENDPOINT GET /api/v1/obligation-deltas Accepts since, pillar, nodes and limit. Want to hear about a change as it lands rather than at the next cycle? Add push-based change alerts. CHANGE ALERTS → COMMON QUESTIONS What is the obligation change feed? It answers the question "what obligations changed since I last reviewed?". Primary sources whose content changed, and obligations the registry has marked withdrawn, mapped to the obligation nodes they affect, filterable by time, by pillar, or by a specific list of obligations. How is this different from change alerts? Change alerts push you a message when a source moves for something you subscribe to. The obligation change feed is a pull you run on your own schedule, usually at the start of a review cycle, to get everything that moved since a date you choose. Teams often use alerts to hear early and this feed to work through the backlog. How is this different from drift check? Drift check answers a narrow question about copies you hold: are the specific versions my agent cached still current. The obligation change feed is broader and time-based: show me everything in my area that moved since a date, whether or not I had cached it. Where do the changes come from? Primary sources behind the registry are fingerprinted on a weekly cycle, recording a content hash and the certificate fingerprint of the source. When a fingerprint moves, that change is mapped to the obligations that cite the source. Withdrawn obligations are marked separately. Does the feed tell me what to do about a change? No. It reports that a source moved or an obligation was withdrawn, and which obligations are affected. It does not interpret the change, assess its impact on your organisation, or advise on a response. That review stays with a qualified professional, and every obligation stays cited to its primary source so it can be checked directly. How do I call it? The feed is available as the obligation_deltas tool over MCP and as a REST endpoint accepting since, pillar, nodes and limit parameters. Pass your Bidda key as api_key. A free trial counts. Start the cycle knowing what moved. The obligation change feed is included with every subscription and a free trial counts. One call replaces the week you spend working out where to start. START FREE TRIAL → DRIFT CHECK →