Open Source · Decision guide
Use RuleOak where authority and effect certainty both matter.
RuleOak is strongest when an automated action can change durable external state, the action crosses a boundary you control, and a timeout or retry can create a second effect.
Three questions
- Can the action cause durable external change?Files, deployments, infrastructure, issues, webhooks and similar operations are typical candidates.
- Can you force it through a cooperating boundary?If the action bypasses RuleOak, RuleOak cannot govern it.
- Can you define useful postcondition evidence?Strong effect verification needs bounded, reviewed semantics for the actual route.
Fit matrix
| Situation | Fit | Why |
|---|---|---|
| Timeout could duplicate a durable action | Strong | One-use authority + effect evidence + retry disposition address the failure directly. |
| Need policy/approval but postcondition is weak | Partial | Keep the route policy-only; do not overclaim effect certainty. |
| Need OS sandboxing or malware isolation | Poor | That authority belongs below the application layer. |
| Need enterprise identity federation | Complementary | Use an identity system; RuleOak can consume explicit application authority. |
| Action cannot be intercepted | Poor | No cooperating boundary means no enforcement. |
Minimum adoption target
Protect one consequential route. Prove deny prevents execution, replay is rejected, response loss becomes unresolved state, and reconciliation does not replay the operation. Expand only after those properties are understood.