Contract library
Every document Kenny can answer from. Reading a contract makes it searchable (chat can quote it immediately); costing rules are drafted per paystub on the Verification tab, and a clause only counts as live once a person has approved the rule drawn from it.
Reading a large contract takes a few minutes: every page is parsed for its text, its tables, and the exact position of each clause.
Verification — start here
Each card is a known answer. The four shipped here are analyst-derived: worked out by hand from the contract, not taken from payroll. A rule can go live only if it fires in a known answer and the library then reproduces it. To cover a scenario nothing answers yet, press Draft the rules for this scenario: Kenny pulls only the clauses that answer it, drafts the handful of rules they need, and checks the total.
Review queue
Rules Kenny drafted for a specific known paystub (from the Verification tab), waiting for your approval. None affect an answer yet. Only the handful a real scenario needs — not the whole contract — so each is quick to check against its clause (View source highlights it on the page). Approve the ones that match.
Rule library
The contract, as Kenny executes it — in three honest parts: what computes (approved rules, each naming its clause and approver), what Kenny declined to model (clauses that pay on a dimension your classification table doesn't have — with the dimension that would unlock them), and everything else, which is answered by quoting the contract, never computing. This is the page to hand an auditor.
Skeptic reviews
An agent that read each rule's clause and the pages around it, listed what the rule ignores, and ran its counter-examples through the deterministic engine. It never computes and never approves: every number below came from the engine, and approval stays with the human.
Audit trail
Every action — each question asked, each document chosen, each calculation step, each approval — in a tamper-evident record. Altering any entry breaks the chain and is detected. Prove it below: the test runs on a scratch copy, never on the record itself.