Comply

An alert only when a rule change actually touches your own formulas.

Tamats raises a regulatory-watch alert only when a revision to the compiled compliance corpus changes an ingredient's status or limit in a way that touches an ingredient already in one of the organisation's own formulations, or a market or retailer standard the organisation watches. Each alert names the ingredient, exactly what moved — a status change, a new or tightened concentration limit, a rule added or removed — the region or retailer scope, the affected formula, and the primary source behind the change. An empty result is reported honestly and distinguishes no open alerts from the changelog holding only a baseline snapshot; it is never presented as a clean bill of health.

A general regulatory changelog is a feed nobody reads, because almost none of it is relevant to any one formula. The useful version of the same information is an alert scoped to what you actually make and sell into — which is a different, harder problem: it means matching every ruleset revision against your own ingredient list and your own watched markets, not just publishing what changed.

What you do with it

Scoped to your own formulations

An alert only fires when the changed rule matches an ingredient sitting in one of the organisation's actual formulations, or a market/retailer combination it watches — not every change to the compiled corpus.

Says exactly what moved

Each alert describes the concrete change — added to the ruleset, removed, a status change, a tightened or loosened concentration limit, or a citation update — rather than a generic 'something changed' notice.

Names the affected formula

The alert carries the formula name(s) the ingredient sits in, so the question 'does this affect me' is answered on the alert itself rather than requiring a separate cross-check.

An honest empty state

No open alerts is reported as exactly that, distinguished from a changelog that only holds a baseline snapshot with nothing to compare against yet — never rendered as a clearance.

What it computes over

• —A weekly diff of the compiled compliance ruleset against its previous snapshot
• —The organisation's own formulations and their ingredient lists
• —The organisation's own watched markets and retailer standards

Where it stops

• Alerts only fire on rules already compiled into the corpus — a market or retailer standard outside that compiled set produces no alert, silently or otherwise, because there is nothing to diff.
• This watches the compiled ruleset, not primary regulator publications directly — a change has to reach the corpus before it can raise an alert here.
• An alert is a notice to review, not a verdict — it does not itself reformulate or resubmit anything; a human still decides what the change means for the affected product.

Questions

Will I get an alert for every regulatory change, everywhere?

No — only for a change that actually touches an ingredient in one of your own formulations, or a market or retailer standard you're watching. A change to a rule with no bearing on anything you make doesn't raise a notice.

What does an alert actually tell me?

The ingredient, exactly what moved (a status change, a tightened limit, a rule added or removed), the region or retailer it applies to, which of your formulas it touches, and a link to the primary source behind the change — enough to decide whether it matters without a separate search.

Does an empty alert list mean my formulas are all clear?

Not necessarily — it's reported as exactly what it is: no open alerts right now, distinguished from the changelog only holding a starting snapshot with nothing yet to compare. It is never presented as a compliance clearance.