The register to keep
This example shows a document that the The register to keep magik would produce. The lab does not exist yet: Mojo builds it the moment you click, with your hours, your prices and your tone. What you read below was invented for this page.
The register to keepThe register to keep
One line per system, kept up to date, produced on request
An inspection asks for this before it asks for anything else. Kept as a living file, not rebuilt the week it is asked for.
CV sorter, high risk
| FieldField | EntryEntry |
|---|---|
| Purpose | Ranks applications for the two open roles |
| Supplier | Named in the contract, version recorded |
| Human review | Head of HR, reads the full pile, records the override |
| Logs kept | 6 months, on the supplier's side, exportable |
| Last review | 11 August, by the HR lead |
Support chatbot, limited risk
| FieldField | EntryEntry |
|---|---|
| Obligation | Tell the user they are talking to an AI |
| Where it is said | First message and footer of the widget |
| Last check | 11 August, wording unchanged since June |
What goes wrong with registers
They are written once and never touched again. Put the review date in it, and review when the supplier ships a version, when the purpose changes, and once a year regardless. A register whose last line is eighteen months old says more against you than no register at all.
This lab can be yours, with your data where this example stands.
Mojo builds it during the customize session. Small companies using AI: that is who this one is for.