Product · Step 3

Screens built from your rules.

Operome Apps are the working screens built from your operome, your rulebook compiled so that a machine executes it exactly: input forms, a rule board, test scenarios and a receipt for every decision. When the rules change, the screens change with them. Included with the runtime.

Four screens

Input forms

Every fact the rules need becomes a form field with its type, its wording from the source text and an unknown state. Nothing is free text that a rule cannot read.

Rule board

The rules as they settle on the facts in front of you: which fired, which blocked, which wait on an unknown. Each one is a click from its clause.

Scenarios

The delivered test cases, ready to run. Change a fact and watch the verdict change. Replay a case the reviewer signed off.

Receipts

Each decision as a paper: the inputs, the verdict, the clauses behind it and a hash over the run. An auditor recomputes it instead of trusting a log.

See it live

Every screen and paper here comes from the rules: the org chart, the order, each paper with its checks for content, timing and issuing authority, and the refusal with its rule. Fictional units, Spanish interface. Sign in ↗

Operome Universe

sign in on operome.dev

Five hotel pre-opening manuals, compiled and queried on these screens. Sign in on operome.dev to run it. Sign in ↗

Why the screens are built from the rules

A screen designed by hand drifts away from the rules it was meant to serve. A screen built from the operome cannot. When the operome changes, the forms, the board and the receipts change with it. The apps come with the Operome Runtime; there is no separate application to build or to keep in step.

The public operomes at operome.dev run on these screens. See them live.

Talk to us ↗