“It depends” has a shelf life.
Compliance, regulatory, and legal teams deal with questions whose answers are only as good as the last time someone checked.
Products change, policies change, and compliance changes with them. Are we compliant? Is this position still sound? What changed, and do we care?
The moment a regulation is amended, guidance is reissued, or new code ships, regulatory conclusions get stale. Everyone is adopting AI to help, but humans remain accountable because a model can’t be fired, interviewed, or subpoenaed.
Exeges tracks what each conclusion depends on, flags those affected by a change in the evidence, and puts it in front of the person accountable.
Assess. Monitor. Answer for it.
Assess.
Aster Biologics is validating a new system. Its compliance team works with a consultancy, and together they flag five requirements that apply.
An Exeges agent reads each requirement and drafts an interpretation, pinning the requirement as well as the Aster records that answer it. The consultant reviews the drafts, corrects two, and accepts them.
The team and consultant disagree on one requirement. Aster holds that FDA’s enforcement discretion makes a paper-log alternative adequate; the consultant holds that discretion doesn’t settle adequacy. Exeges records both readings, reasons and citations, and marks the requirement unresolved.
Monitor.
Aster’s document control issues revision 6 of its distribution procedure. The wording that one accepted judgment relied on has been removed.
In Exeges, four positions stand. The fifth is listed in doubt, with the agent’s read of what changed and whether the position survives.
The team reviews revision 6 and records a new judgment pinned to it. The old judgment stays on the record as the previous version.
Answer for it.
Fourteen months later, an FDA investigator asks why that requirement was marked supported. Aster has run forty validations since; nobody remembers offhand.
The team pulls up the requirement: the original determination, the revision it was read against, the disagreement and what was decided, who signed, when, and why.
Built for the process you already have
Workflows don’t usually live in one system. Exeges doesn’t ask anyone to change tools, their output is a source like any other: versioned with anchored references.
Underneath it all, one portable record
“Why did we decide that five years ago, and why did it change three years later?”
-
Nothing enters it unverified. Every reference quotes the passage it cites and is checked against the source before it is written. An agent cannot cite text that isn’t there. The gate
-
Anchored to the line, not the title. A position names the clause, the cell, or the second of a transcript, in the version it was read in. When that line changes, the positions resting on it are already listed. The grid · A new version arrives
-
It leaves the building intact. An auditor or a discovery team loads the record on their own installation and sees everything the original team saw, including what it skimmed or skipped. The record compounds
Where the reasoning lives today
None of these go away. Each is missing the same layer: the reasoning, anchored to the version of the sources it was based on.
| What it does well | What it can’t tell you | |
|---|---|---|
| GRC and document-management platforms | The system of record most compliance teams already own. Controls mapped to frameworks, policies under version control, attestations signed, evidence attached, changes logged. | They record status and sign-off, not reasoning or the impact of change. The regulation is a label on a mapping, not a versioned text, so a change feed can say the rule was updated but not which of your positions was based on the changed clause. |
| Legal and regulatory research services | The subscription your team searches first. They hold the current text of the rules, send the alert when one changes, and tell you whether a rule or a case you cited is still in force. | They know the rules. They don’t know your positions. When a clause moves, they can say the rule changed; they can’t say which of the positions your team signed last year rested on the sentence that went. |
| The memo, the spreadsheet, the shared drive | Where the reasoning actually lives: the memo that made the call, whether in-house or outside counsel wrote it, the tracker that lists the obligations, the folder with the signed copy. Familiar, searchable, and right on the day it was written. | A memo with the rule attached is a printed spreadsheet: right on the day you printed it, formulas gone. Nobody recorded which sentence of the rule each conclusion rested on, so when the rule changes you reread the memos. Your people still make every call; they should start from the few positions the change touches, not from the whole drive. |
| The AI assistant, sanctioned or not | The fastest analyst the team has ever had, and often right. | The sources it names were never checked against the text, nobody else can open the conversation it came from, and a year on all you have is the answer. |
See it
Demos are running now. We’re also happy to start from your material: bring a few of your team’s standing conclusions, memos, determinations, filed analyses, and we’ll show you how they are managed in Exeges.
Get in touch to set one up.
More: how it works · use cases · about Exeges · posts