Skip to content
AIAssuranceLabs
Menu

Tool logic

The tools run from five JSON files kept in the repository and bundled at build: the classifier questions and rules, the obligation profiles by role and tier, and the column and export definitions of the tracker, the checklist and the traceability matrix. Each file is published here in full, rendered as tables and as the file itself, with its version. A tool result can be traced to the rule that produced it, and a rule can be checked against the article it cites and the regulation data In force it renders dates from.

The files

How a change reaches the tools

A file changes only through a commit that raises its version. The classifier rules derive from PR-CLS v1.0; the profiles name the regulation entry behind every date, so a change to the regulation data through the change log reaches every tool at the next build without a rule edit. The obligation elements that the tracker, the checklist and the matrix expand come from the records behind /obligations/, which the protocols cite. No file is fetched at runtime and nothing a user enters leaves the browser.