quorumquorum studio
Draft, check and commission a rulebook, in one app.
For Windows, macOS and Linux. It carries the same compiler and tools the test suite runs, and works entirely on your computer.
The app
Everything without installing a compiler
- Open a rulebook, import a worksheet, or draft one from a manual
- Check every situation, and see the situation that breaks a refused rulebook
- Write the chip image for a Pico 2 or an Uno R4, and the firmware the first time
- Print the commissioning sheet, and test a connected board against it
AI drafting
An AI drafts. A person approves.
A model drafts a rulebook from an equipment manual, with a model on your own computer (Ollama) or a hosted one. Every rule it keeps must quote the manual word for word, and mistakes and failed checks are sent back to it.
The draft is marked unapproved, and no chip image can be built from it until a named person approves it. The review lists first everything that could stop the safe action.
In a test on four regulations no model had seen, scored against answers written down before any run, drafts got 116 of 135 checks (86%). They still missed a manual shutdown device and a monitoring exception in most runs, which is why a person approves.
How the test was run| Regulation | Score |
|---|---|
| Gas turbine shutdowns (46 CFR 58.10-15) | 40 / 50 |
| Steering gear alarms (46 CFR 58.25-25) | 39 / 40 |
| Boiler controls (46 CFR 63) | 17 / 20 |
| Mine CO warning (30 CFR 75.1103-5) | 20 / 25 |
| Total, five drafts each | 116 / 135 |
Commissioning
The check proves the rules. The sheet checks the wiring.
No amount of checking can see whether a reading comes from the right instrument. So after a passing check the studio prints a loop-check sheet: for each reading, what it must cause on its own, and with which other readings, with a column to sign off.
Test the board drives a connected board over Modbus through every line of the sheet and reports any line that differs. On a Raspberry Pi Pico 2, 41 of 41 states matched. A rulebook with timed readings is tested through time instead, on the board's test clock: 19 of 19 checks matched on a Pico 2, in seconds.
The commissioning guideat rest continue set this alone with then bearing_temp_high continue vib_high shutdown suction_low continue vib_high maintain near_critical continue vib_high shutdown + vib_1x calib_overdue continue vib_high continue + vib_1x (was maintain) checked by ________ date ______
Refusals
A refusal says what to fix
A refused rulebook comes with the exact situation that breaks it. The most common refusal in drafts is a conclusion nothing can argue against: a rule that trusts its sensors completely.
For that one the studio offers a repair in one click. It adds a failed-sensor check for each reading the rule relies on, each marked for an engineer to confirm.
# TODO: confirm the device can tell when the # low_oil instrument has failed, and that # alarm_machinery is the right response then. observe low_oil_failed "the instrument behind low_oil has failed or is disconnected" doubt low_oil_untrusted "low_oil is not trusted" needs low_oil_failed low_oil_untrusted undercuts low_oil_level claim low_oil_blind needs low_oil_failed