Kebiki · Use cases
Kebiki is for the decisions where the rule is already written down, the answer moves money, and someone will one day ask why. Three problems, one shape.
What they have in common
Eligibility, claims and tax look like different businesses. As decisions they are the same decision, and the part that makes them expensive is never the arithmetic.
A statute, a policy wording, a plan document, a rate table. The authority exists and someone maintains it. It simply is not executable, so it gets translated into code by hand — once, and then never again in step.
A payment is made or withheld. Someone is covered or is not. This is not a recommendation a person reviews; it is the decision, and something downstream acts on it immediately.
The rule that applies is the one in force on the date of the event, not the one in force today. A system that knows only the current rules answers last year’s question wrongly, and confidently.
An appeal, an examination, an audit, a dispute. Years later, and rarely the person who decided. The answer has to be reproduced rather than remembered or reconstructed.
Application code handles the first two well and the last two not at all. That is the whole argument for compiling the rule into a versioned package instead: the date and the audit become properties of the artifact rather than features somebody has to remember to build.
Decision problems
Each is a family rather than a single rule: one compiled package per jurisdiction, product or programme, called by whatever system needs the answer.
Benefits, coverage and programme eligibility. Deterministic determinations, structured requests for the evidence that is missing rather than a guess at it, and a signed trace for every appeal.
Government · Healthcare · Insurance
Coverage, limit and authorisation checks, with every approval or denial carrying reason codes that cite the clause that produced it rather than paraphrasing it.
Insurance · Healthcare
Credits, indirect tax and withholding, computed against the code in force for the period rather than the period you are computing in, and reproducible in any examination.
Government · Banking
By industry
The same decision problems, under the regimes that decide what an answer has to be able to show.
Prior authorisation, formulary rules and billing compliance, enforced before a claim leaves your system.
Underwriting triage, claims adjudication, and rate and eligibility rules across jurisdictions.
Credit decisioning, KYC and AML enforcement, and rate and fee rules with examiner-ready trails.
Benefits, licensing and grant eligibility, with reason codes linked to statute and defensible on appeal.
Send us the rule as it is written and one determination you have had to explain after the fact. We will compile the rule, run the case, and show you the citation and the trace it produces.
