Compliance: your rules applied, every check recorded

It is worth whatever an inspector chooses to allow it, and that is the problem.
What I record: an image filed on 14/04, showing a configuration screen. No visible date in the image, no capture timestamp, nothing establishing when the screen was in that state.
What it is meant to prove: three obligations, two of them annual.
Why that is a practical rather than a formal problem: on inspection day the question asked is "on what date were you in that state?" An undated capture answers "at some point". And evidence that dates nothing proves nothing about an obligation carrying a deadline.
What I did instead of rejecting it: I looked for something that would date it. The system log carries the change at 14/04, 09:12; set against the capture, it turns that image into dated evidence. The internal attestation linking the two is written — three lines pointing at the log entry — and awaits the operator's signature. What evidence is worth is said before the inspector, not here: I hand it over dated rather than commented.
What I propose: a list of your 47 pieces of evidence filed this year, sorted by what they can establish. 31 carry an enforceable date, 9 an internal date, 7 no date.
The 7 concern 14 obligations — that is where the file risk concentrates. 47-pieces_7-undated.pdf31 dated · 9 internal dates · 7 undated
⛓ Source · evidence of 14/04, 47 pieces filed this year, related obligations

I do not always know, and I say so rather than ticking a box.
What I check: that a document is attached, that it carries a date, that the date falls within the period the deadline covers, and that the document is not attached to another obligation as its sole justification.
What I do not check: that the content of the document establishes what the obligation requires. An annual inspection report can be dated, complete, and cover a partial scope — that has to be read, and read by somebody who knows the text.
What that gives across your 84 obligations: 62 have a dated document within the period; 14 have a document where I cannot tell whether it covers the scope; 8 have no document at all.
The group of 14 is the one to look at, and it is the most reassuring in appearance: the box is ticked, a document exists, and nobody has read what it covers.
What I provide for those 14: the obligation, the document, and the sentence or sentences of the document that define its scope. That is a two-minute read, not a full re-reading. 84-obligations_14-to-read.pdf62 covered · 14 to read · 8 with no document
⛓ Source · 84 register obligations, attached documents, declared scopes

Through departures, and through nothing connecting a departure to a register.
What I record: eleven obligations carry the name of a person no longer with the company. The departures range from 2024 to May 2026.
What that produces: deadlines keep running, reminders go to an address that no longer exists, and nobody receives anything. Three of these obligations have a deadline within four months.
What it reveals about the process: leaving the company triggers closing access, returning equipment and final pay. It does not trigger reassigning regulatory obligations, because nobody has listed them at that point.
What I put in the file, and it is not nothing: a proposed name for each of the eleven, with what justifies it. The appointment stays your act of organisation — entrusting a regulatory obligation commits the person appointed, and that is precisely what makes it effective. Eleven boxes to tick, and from the next day reminders go to an address that exists.
What I provide: the eleven, their deadline, the department the obligation attaches to, and the last evidence filed with its author — that is often the best-placed person, and they are sometimes still here.
Of the eleven, seven have their last evidence filed by somebody other than the assigned owner. 11-obligations_orphaned.pdf3 with deadlines · 7 with an author still present
⛓ Source · 11 obligations, leavers register, authors of the last evidence

They are more troublesome than one thinks, and I flag them without removing them.
What I record: four obligations attach to an activity sold in 2025. They still appear in the register, with deadlines falling and reminders going out.
What that produces: four overrun deadlines every year, swelling a counter of overdue obligations. And a counter permanently showing overruns nobody handles teaches people to stop looking at the counter.
What I keep, and why I keep it: the four stay in the register. An obligation removed from a register disappears from the record, and one must be able to show, in 2028, that it applied until 2025 and was met until then.
What I propose: marking them "spent as of 30/09/2025", with the date and the reason, and keeping their earlier evidence. The register keeps its memory and stops producing noise.
And a question the other way, which I put without being able to answer it: did the 2025 sale give rise to new obligations? My register contains only what you put in it — and an obligation that is not in it will never make me flag anything. 4-obligations_activity-sold.pdfSpent, not removed · 1 open question
✎ Framework · no obligation removed — dated and reasoned extinction

Twelve obligations, and I sort them by what is missing, not alphabetically.
The scope announced in the letter: it covers a family of obligations which, in your register, amounts to twelve. None has been reviewed since 2024.
What I looked at for each: evidence present, evidence dated, date within the period, owner in post.
· 5 are complete — dated document, legible scope, owner identified.
· 4 have a document whose scope requires reading.
· 2 have an undated document.
· 1 has had no document since 2024.
What I do forecast, and it is the figure that serves you: the state of the file, not the verdict. As things stand, 5 obligations out of 12 can be presented as they are; the other 7 need 11 person-days in all, 6 of them for the one with no document. The outcome of the inspection belongs to the inspector — a complete file is not a compliant file, and they may find what I was unable to read. What I can hold to is that they will have nothing to ask for twice.
What I propose: a calendar for the eight remaining weeks, starting with the one with no document — reconstituting it takes longest, and it is the only one that cannot be caught up the night before.
And a point of method: everything produced between now and October will be dated August or September 2026. That shows, and it is better known before somebody notices. 12-obligations_october-inspection.pdf5 complete · 4 to read · 2 undated · 1 with none
⛓ Source · inspection letter, 12 obligations in scope, evidence filed

The state of the file at each date, and nothing resembling a certificate.
What is kept: the obligation as you entered it, the evidence and its dates, successive owners, deadlines and overruns, and extinctions with their reason.
What is not kept, and cannot be: no compliance certificate, no compliance rate, no score per obligation or per department, and no opinion on the scope of a text.
Why "no compliance rate": a rate is computed on what is in the register. A company whose register is incomplete shows an excellent rate, which is exactly the reverse of reality. The figure would reward the omission.
And "no certificate": a document produced by a tool saying "compliant" is a document an inspector can request. It defends nobody, and it puts the company's own assertion against it.
What the quarterly summary contains: the next six months' deadlines, undated evidence, orphan obligations, and extinctions declared. Four factual indicators. what-is-kept.pdf5 items kept · 4 never produced
✎ Framework · retention periods to be set by the company

Applying the rules: every file goes through every rule, without exception and in the same order. This month, 214 files × 38 rules from your register = 8,132 individual checks. No rule is skipped because a file "looks like" another: that is precisely what makes a control defensible.
Analysing documents against the control rules is the heart of the work: for each rule I read the documents on file and look for what the rule requires, not what the document says. A three-page certificate can satisfy one rule and stay silent on two others — I report rule by rule, never document by document. What a neighbouring agent completes: fine extraction of data from a poorly scanned document belongs to a dedicated document agent, ordered separately; here I read what is readable and flag what is not.
Findings are qualified in three states, never two — and the difference between the last two is what spares you an inspection you did not prepare for:
· Rule satisfied — 6,918 findings. A document is attached, it carries a date, and that date falls inside the window the rule requires.
· Element not found — 874 findings. Nothing on file answers the rule. That is a gap, not a breach: I name the document expected and the person who holds it.
· Situation to examine — 340 findings. A document exists and something is off: date outside the window, different scope, version earlier than the rule. Those call for a human eye, and I say which of the three reasons brought them out.
What I never write: "compliant". A satisfied rule is a finding about a document; the compliance of a company is a judgement, and it belongs to whoever signs it.
A figure against me: 41 of the 340 "to examine" were in fact satisfied rules, all on evidence supplied as photographs, whose date appeared in the image and not in the file. The date shown inside the document is now read before the file date: 6 re-qualifications across the following 2,100 checks.
✎ Framework · rules applied, documents analysed, findings qualified

The audit trail answers that without anyone having to remember anything.
For every file checked, five elements are kept together and never come apart: the rule in the version in force that day, the qualified finding, the supporting document and its digital fingerprint, the date and time of the check, and the author — me, or the person who re-qualified it. 8,132 lines this month, 87,400 since go-live.
Why the version of the rule matters more than the rule: your 38 rules have seen 9 changes in eighteen months. A check run under a rule since amended is neither wrong nor right — it is dated. Without the version, an inspector reads last year's checks against today's rule, and you have nothing to put against it.
The log is append-only: a re-qualification is written after the fact, with its reason; it does not erase the original finding. Of the 41 re-qualifications just mentioned, all 41 original findings are still readable, next to what corrected them.
The foundation is a sovereign AI, and that is not brochure wording: the agent runs on a machine you designate — your own, or your hosting provider's in France, under French law — an architecture designed to reduce exposure to extraterritorial legislation, location alone not guaranteeing immunity. None of your evidence leaves your walls to be analysed, access is granted by role, it is logged, and it is withdrawn with a word, effective at the next check. A register of obligations and its evidence is exactly the kind of file you do not hand to a service whose reading place you do not know.
✎ Framework · audit trail kept file by file · sovereign foundation