Compliance module
Tracks the controls you define, the evidence and sign-offs behind them, and when each one runs out.
On this page
What it is for
Tracks the controls you define, the evidence and sign-offs behind them, and when each one runs out.
- You keep a list of rules or checks your business must show it follows.
- You want to know which evidence runs out soon.
- You want to confirm that a recorded document has not changed.
- You need a full history of who changed what and why.
Ask your bot
You do not type commands. Ask in plain words and the bot runs the module for you.
- You ask
- Which of our controls have evidence that runs out soon?
- What you get back
- The bot lists each control with its status, the evidence that is about to run out and the date, and offers to turn each one into a task.
What the bot does with it
- The bot records the controls you describe, with an owner and a renewal period for each.
- It records evidence and attestations as you provide them. Every change needs a named actor and a reason.
- It reports which controls are green, yellow or red and which have no current evidence.
- It turns items that run out soon into suggested tasks you can hand to the tasks module.
- The module keeps records and dates. It does not judge whether your business meets any standard.
What it stores
Programs, controls, evidence, attestations and a linked history of every change live in one SQLite file, compliance/compliance.sqlite, in the bot's Ambitious folder (/workspace/ambitious by default). Documents stay in Grok Bot Pages. The module keeps only a reference to each Page with its version and content hash.
The module has no screens of its own. It reads JSON, writes JSON, and keeps its data under /workspace/ambitious on the bot's computer. It never sends data anywhere.
Command reference
For the technically curious. You will rarely type these yourself; the bot runs them. Every command answers with the same envelope: whether it worked, which module and command ran, the data, and a list of errors with a hint for each. Open an example to see the command and its output.
ExampleAsk for the status of every control in a program. One control has current evidence and one has nothing recorded.
Command
echo '{"programId":"office-policies"}' | ambitious-compliance status --jsonOutput
{
"ok": true,
"schemaVersion": 1,
"module": "compliance",
"command": "status",
"data": {
"programId": "office-policies",
"now": "2026-03-02T09:00:00.000Z",
"controls": [
{
"controlId": "backup-check",
"status": {
"color": "green",
"reasons": [{ "kind": "current", "support": { "kind": "evidence", "evidenceId": "backup-log-february", "expiresAt": "2026-05-31T00:00:00.000Z" } }]
}
},
{ "controlId": "staff-training", "status": { "color": "red", "reasons": [{ "kind": "nothing_recorded" }] } }
]
},
"errors": [],
"meta": { "now": "2026-03-02T09:00:00.000Z", "seed": 7, "version": "0.1.0" }
}ExampleCheck that a recorded document still matches its Grok Bot Page. The bot supplies the hash of the Page's current content.
Command
echo '{"docId":"staff-handbook","sha256":"4a75ab26b9047bbb1e89e8c47545aa668a01a3186e8ed8e629518c3aab6576d9"}' | ambitious-compliance doc check --jsonOutput
{
"ok": true,
"schemaVersion": 1,
"module": "compliance",
"command": "doc check",
"data": {
"matches": true,
"document": "staff-handbook",
"sha256": "4a75ab26b9047bbb1e89e8c47545aa668a01a3186e8ed8e629518c3aab6576d9"
},
"errors": [],
"meta": { "now": "2026-03-02T09:00:00.000Z", "seed": 7, "version": "0.1.0" }
}Show every command
| program add | Creates a program, which is a named group of controls. |
|---|---|
| control add | Adds a control to a program, with an owner and how often it must be renewed. |
| evidence add | Records a piece of evidence for a control, with the dates it is valid between. |
| attest | Records a statement from a named person that a control is met for a period. |
| doc record | Records a reference to a Grok Bot Page as a document of a program, or adds a new revision. |
| status | Shows each control as green, yellow or red, with the reasons. |
| gaps | Lists the controls that have no current evidence. |
| expiring | Lists evidence and attestations that run out soon, each with a suggested task. |
| verify-chain | Checks that the change history is intact and reports the first bad entry if it is not. |
| doc check | Compares a Page's current content hash with the recorded one and reports a mismatch. |
| export | Returns a program's records together with the complete change history. |
| rebuild | Verifies the history and restores the current records from it. |
| selfcheck | Checks the installed file and the database, applies pending database updates and lists any problems in plain words. |
| commands | Lists every command the module offers. |
Source and releases
The module is open source under the Apache license. Each release carries one bundled file and its checksums; the bot installs it for you.