Instructions, held as logic
Oier does not run your instructions as a script. It stores them as conditions, and a transfer goes through only when every condition is true.
One rule in the engine
spent(24h) + amount ≤ 1200
Typed as “Spend at most $1,200 a day”. Any transfer that would push the day's total past 1,200 is stopped.
Inside the engine
Your rules form a single true-or-false test applied to each transfer. A transfer passes when the test is true, and a new rule is accepted only if the test can still come out true for some transfer.
Under the hood
Each clause looks at one property of a transfer (payee, amount, spend so far, hour, asset, category, date, co-signatures) and compares it with a value. A rule joins clauses with “and”. Governance rules restrict edits to other rules.
Connectives
∧ and, ∨ or, ¬ not, → implies, ∈ member of, ⊥ never
What changes when rules are logic
Conflicts surface early
Contradictions are caught while you write the rule, long before a payment depends on it.
Nothing hidden between words and enforcement
The formula derived from your sentence is shown to you, and that formula is exactly what runs.
Amendments obey the rules
A rule may carry its own amendment policy, and every edit is measured against it.
Layered protection
Rules can refer to rules, so protection can be stacked as many levels deep as you need.
Three engine properties
Decidability
Every conflict is decided, never guessed
Each clause compares one property of a transfer with a fixed value. Because of that, the possible transfers fall into a finite number of groups the rules treat alike, and the checker can examine every group instead of sampling a few.
Checker result
Satisfiable
Some transfer still passes every rule in the set.
- Method
- One witness per threshold region
- On failure
- Rejected, with the clashing rules listed
Self-reference
Rules that point at rules
A governance rule names another rule and states what an edit to it requires: a number of approvals, a notice period, or nothing at all because edits are forbidden. Chains of these are checked like any other rule.
Governance rule
2 approvals, 7 days
Editing R1 requires two approvals and a week of notice.
- Controls
- Which edits are allowed
- Typical use
- Shared accounts, rule chains
Revision
Edits that cannot break the set
Adding a rule can only narrow what the account permits, so new rules are tested for contradiction and redundancy. Loosening means deleting a rule, which is precisely what governance rules regulate.
Edit path
test, then commit
An inconsistent edit never reaches the set.
- Tested for
- Contradiction, redundancy, unpayable payees
- Covers
- The set plus every rule guarding it
What it makes possible
Self-describing accounts
You can ask what a rule allows, whether an edit is safe, or whether two rules collide, and get a definite answer.
Guarantee: Definite within the supported clauses
Accounts owners can reshape
Owners change behaviour by adding requirements, and the policy for accepting changes lives inside the rule set itself.
Guarantee: Edits are accepted only when satisfiable
Assurance for everyday money
The kind of up-front checking used in safety-critical engineering, applied to a household wallet.
Guarantee: Settled before execution
Code versus a rule set
Three habits make the difference: describe conditions rather than steps, decide them rather than sample them, and test every edit before it lands.
| Aspect | Conventional code | An Oier rule set |
|---|---|---|
| You describe | Instructions to execute | Conditions to satisfy |
| Verification | Tests and audits over chosen scenarios | A decision covering every case the rules distinguish |
| Rule clashes | Discovered in production | Rejected at writing time, with the culprits named |
| Later edits | Patch and redeploy | Accepted only if the guarding rules allow |
| Meta-rules | Rare, usually one config value | Any rule can govern any other |
Try the engine
The Rule Studio runs this exact drafter and checker inside your browser. No API key, no server involved in the verdict. Enter two rules that contradict each other and the second is rejected with an explanation.
Grounded in research, clear about limits
- The approach draws on published work in decidable logic and boolean algebra, including specifications that can describe how they may be changed.
- The preview understands a fixed set of phrasings. A sentence it cannot fully read is rejected outright, never applied in part.
- On-chain, 24-hour caps are counted in hourly buckets and 7-day caps in daily buckets, so a window can start up to an hour (or a day) earlier than the exact moment.
- Richer conditions over time, like “until” or “since”, are still being researched.
Ready when your account is
We are opening accounts a few at a time. Put your name down and draft your first rules today.