Learn · Rulebooks
What a logic rulebook holds
Exact checks over incoming data, written by you and kept private.
Checked against the product on · written for people writing code
A logic rulebook is your own set of exact checks over incoming events. You write the checks; the platform runs them and gives the same answer every time. Nothing about them is a matter of judgement.
Reach for one when you can state the test yourself: this address is outside our range, this amount is over the limit, this field is missing, this code matches this pattern. Reach for a rule pack when the signal lives in language and needs reading.
| Compare | Rule pack | Logic rulebook |
|---|---|---|
| What it carries | Warning labels and the teaching text that explains each one. | Checks over the fields on an event. |
| Who decides a match | The platform reads the event and decides whether a label applies. | The check runs as written. |
| Steadiness | Measured across repeated runs and published as a grade. | The same input gives the same answer, every run. |
| Where it lives | The public library. Anyone can install a published pack. | Your account only. It is never listed publicly. |
| Good for | Coercion, disclosure, tone, intent — anything that needs reading. | Ranges, patterns, addresses, counts, missing fields. |
Yours stays yours
A logic rulebook is private by construction. There is no cross-account listing to appear in, installing one requires the same account that wrote it, and the check for that lives in the platform behind the screen, so a direct API call cannot get around it.
Versions are frozen
A published version keeps its content for good. New work goes into the next version, and a work area stays on the version it installed until you move it. Every version is checked when you publish it, so a rulebook that cannot compile is refused at that moment.