# How we verify

Amacunia services compute legal deadlines from public records. A wrong date costs more than the call, so we check the answers before you pay.

## The rule, quoted

Each rule is read at its official source, dated, and quoted word for word. We keep a SHA-256 fingerprint of each quoted passage, so any change shows.

## Cases known in advance

Before the code is written or changed, a session that does not write the code takes cases from the official source: an input, and the answer the law gives. Every case is replayed before every release, and a service must pass all of them. Its /method page gives the count.

## No silent changes

For 7 of our 9 services, we record the answers the previous version gave on real cases. A new version must return the same answers, unless the change is intended and announced.

## Guards that are tested

When we fix an error, we remove the fix once and show that the check fails without it.

## A gate before release

A shared check returns READY or REWORK. Nothing goes online on REWORK.

## What this has caught

These checks found and fixed real errors in our own services. Four examples.

- One service still warned of a penalty that the agency had publicly suspended. Each answer now states what the agency currently enforces, with its notice and date.
- Some relief deadlines did not yet follow a recent change in the law and came out too early. Each answer now states the extension and the rule it rests on.
- A thirty-day claim period was returned for older natural-disaster decrees, where the period was ten days. Each answer now cites the rule in force for the period of the decree.
- A condominium manager's mandate that had already expired was counted as ending today. The service now leaves the days remaining empty and gives the days elapsed separately.

## What we refuse to do

When the rule or the data does not settle a question, we return null with a reason instead of guessing, and we count those cases. If the source is down, you get an error and you are not charged. We give no rating or verdict on a business, and we return no personal data about private individuals.

## The counts, service by service

Read on November 15, 2026 from the /method.json file each service publishes. A situation is unsettled when the rule or the data does not decide it: the service records it and says what it returns.

| Service | Cases known in advance | Unsettled situations recorded | Cases written on | Method page |
|---|---|---|---|---|
| Biennial Update Sentinel | 43 | 18 | 2026-11-09 | https://mcs150.amacunia.fr/method |
| Operating Authority Sentinel | 28 | 6 | 2026-11-11 | https://authority.amacunia.fr/method |
| Disaster Deadline Sentinel | 33 | 12 | 2026-11-10 | https://disasters.amacunia.fr/method |
| Revalidation Deadline Sentinel | 12 | 6 | 2026-11-09 | https://revalidation.amacunia.fr/method |
| Sentinelle catnat | 24 | 5 | 2026-11-11 | https://catnat.amacunia.fr/method |
| Sentinelle créances | 21 | 2 | 2026-11-11 | https://creances.amacunia.fr/method |
| Sentinelle oppositions | 20 | 5 | 2026-11-11 | https://oppositions.amacunia.fr/method |
| Sentinelle phyto | 23 | 6 | 2026-11-11 | https://phyto.amacunia.fr/method |
| Sentinelle syndic | 24 | 7 | 2026-11-11 | https://syndic.amacunia.fr/method |

## What this is not

This is information, not legal advice. The official text prevails. We are not affiliated with any government agency.