Browse by topic
Trust
15 posts and patterns
Cedar Verifies Who Can Access What. Who Verifies What Decision Gets Made?
Cedar brought formal verification to authorization policy with Lean and automated reasoning. Some rule engines check decision tables, but none of the engines reviewed on 2026-09-30 documents a proof over business rules. Why proving things about a discount, a loan decision, or a fraud threshold is the harder problem, and where LexQ actually stands on it.
Why Business Decisions Need Formal Verification
Tests and simulation answer what happened on inputs you already have. They cannot answer what happens on inputs nobody has sent yet. Unreachable rules, silent conflicts, and uncovered gaps live in that difference, and closing it takes proof, not sampling.
Screening Insurance Eligibility by Age and Region with BLOCK Rules
A filing change lands in one version instead of three codebases, and a declined application names the screen that stopped it.
Feature Entitlement & Plan Limits: Stop Hardcoding Your Pricing Tiers
Plan tiers hardcoded across services turn every pricing change into a deploy. Feature flags are the wrong home for entitlement, and a new plan tier should be a rule change, not a deploy.
Deciding Subscription Proration with a Time-Travel Audit
Proration treatments move into versioned rules, so a disputed charge is proven against the policy in force that day.
The Audit Trail Problem: Proving Which Rule Made Which Decision
A blocked transfer leaves one log line. Months later, an auditor asks why, and git can't answer, because it versions your code, not your decisions. What a real decision audit trail records, and why it has to be immutable.
What Is a Decision Operations Platform? (And When Your Team Needs One)
Pricing, eligibility, and fraud rules change constantly but live trapped in application code. A Decision Operations Platform gives business decisions their own lifecycle. What the category is, and when you need one.
Centralizing Plan-Tier Feature Entitlement with BLOCK Rules
One entitlement decision per feature, asked by every gate, so a denial names the tier that feature requires.
Rule Engine for Fintech: Limits, Underwriting, and Approval Decisions
Fintech limits, underwriting thresholds, and approval decisions change with every regulation and every risk model, and break when they're buried in service code. The deadline comes from a regulator, the threshold belongs to risk, and an auditor will ask which one was in force on a given day.
Adjudicating Credit Applications with a Priority-Ordered Mutex Group
A pattern that routes each credit application to one of approve, decline, or refer, and records which rule produced the decision.
Rule Engine for E-Commerce: Discounts, Promotions, and Eligibility
E-commerce discounts, promotions, and eligibility multiply faster than any other logic, and break in checkout code. Where these rules should live, why the hardcoded version fails, and how to ship promotions without margin surprises.
Enforcing KYC-Tiered Transfer Limits with BLOCK Rules
One limit per verification level, in force on every transfer path, with the reason recorded the moment a transfer is stopped.
Resolving VIP Tier Discount Stacking with a Mutex Group
A pattern that guarantees exactly one discount applies when tier discounts and seasonal campaigns collide.
Managing Business Rules with AI Agents: What MCP Changes
AI agents can now create, test, and deploy business rules autonomously. Here's how the Model Context Protocol(MCP) makes it possible, and why it matters for engineering teams.
GoRules vs Nected vs LexQ: Choosing the Right Rule Engine in 2026
A practical comparison of three modern rule engines: architecture, simulation, pricing, and AI integration. No fluff, just what matters for your decision.